Method and apparatus for channel state information(CSI) and calibration reporting in a wireless communication system

Abstract

The disclosure relates to a 5G or 6G communication system for supporting a higher data transmission rate. According to an embodiment of the present disclosure, a method performed by a user equipment (UE) in a wireless communication system is provided. The method comprise receiving, from a base station (BS), first configuration information on a first channel state information (CSI) report with a report quantity set to a cjtc-Dd and second configuration information for a second CSI report with a codebook type set to a typeII-CJT-r18, wherein the cjtc-DD represents a coherent joint transmission calibration (CJTC) of delay offset and the first configuration information includes a higher layer parameter configuring the first CSI report to be linked to the second CSI report, and receiving, from the BS, first CSI-RS resources for the first CSI report and second CSI-RS resources for the second CSI report, wherein the number of the first CSI-RS resources and the number of the second CSI-RS resources are the same as the number of transmission and reception points (TRPs).

Description

METHOD AND APPARATUS FOR CHANNEL STATE INFORMATION(CSI) AND CALIBRATION REPORTING IN A WIRELESS COMMUNICATION SYSTEM

[0001] The present disclosure relates generally to wireless communication systems and, more specifically, the present disclosure relates to method and apparatus for channel state information (CSI) and calibration reporting in a wireless communication system.

[0002] 5G mobile communication technologies define broad frequency bands such that high transmission rates and new services are possible, and can be implemented not only in “Sub 6GHz” bands such as 3.5GHz, but also in “Above 6GHz” bands referred to as mmWave including 28GHz and 39GHz. In addition, it has been considered to implement 6G mobile communication technologies (referred to as Beyond 5G systems) in terahertz (THz) bands (for example, 95GHz to 3THz bands) in order to accomplish transmission rates fifty times faster than 5G mobile communication technologies and ultra-low latencies one-tenth of 5G mobile communication technologies.

[0003] At the beginning of the development of 5G mobile communication technologies, in order to support services and to satisfy performance requirements in connection with enhanced Mobile BroadBand (eMBB), Ultra Reliable Low Latency Communications (URLLC), and massive Machine-Type Communications (mMTC), there has been ongoing standardization regarding beamforming and massive MIMO for mitigating radio-wave path loss and increasing radio-wave transmission distances in mmWave, supporting numerologies (for example, operating multiple subcarrier spacings) for efficiently utilizing mmWave resources and dynamic operation of slot formats, initial access technologies for supporting multi-beam transmission and broadbands, definition and operation of BWP (BandWidth Part), new channel coding methods such as a LDPC (Low Density Parity Check) code for large amount of data transmission and a polar code for highly reliable transmission of control information, L2 pre-processing, and network slicing for providing a dedicated network specialized to a specific service.

[0004] Currently, there are ongoing discussions regarding improvement and performance enhancement of initial 5G mobile communication technologies in view of services to be supported by 5G mobile communication technologies, and there has been physical layer standardization regarding technologies such as V2X (Vehicle-to-everything) for aiding driving determination by autonomous vehicles based on information regarding positions and states of vehicles transmitted by the vehicles and for enhancing user convenience, NR-U (New Radio Unlicensed) aimed at system operations conforming to various regulation-related requirements in unlicensed bands, NR UE Power Saving, Non-Terrestrial Network (NTN) which is UE-satellite direct communication for providing coverage in an area in which communication with terrestrial networks is unavailable, and positioning.

[0005] Moreover, there has been ongoing standardization in air interface architecture / protocol regarding technologies such as Industrial Internet of Things (IIoT) for supporting new services through interworking and convergence with other industries, IAB (Integrated Access and Backhaul) for providing a node for network service area expansion by supporting a wireless backhaul link and an access link in an integrated manner, mobility enhancement including conditional handover and DAPS (Dual Active Protocol Stack) handover, and two-step random access for simplifying random access procedures (2-step RACH for NR). There also has been ongoing standardization in system architecture / service regarding a 5G baseline architecture (for example, service based architecture or service based interface) for combining Network Functions Virtualization (NFV) and Software-Defined Networking (SDN) technologies, and Mobile Edge Computing (MEC) for receiving services based on UE positions.

[0006] As 5G mobile communication systems are commercialized, connected devices that have been exponentially increasing will be connected to communication networks, and it is accordingly expected that enhanced functions and performances of 5G mobile communication systems and integrated operations of connected devices will be necessary. To this end, new research is scheduled in connection with eXtended Reality (XR) for efficiently supporting AR (Augmented Reality), VR (Virtual Reality), MR (Mixed Reality) and the like, 5G performance improvement and complexity reduction by utilizing Artificial Intelligence (AI) and Machine Learning (ML), AI service support, metaverse service support, and drone communication.

[0007] Furthermore, such development of 5G mobile communication systems will serve as a basis for developing not only new waveforms for providing coverage in terahertz bands of 6G mobile communication technologies, multi-antenna transmission technologies such as Full Dimensional MIMO (FD-MIMO), array antennas and large-scale antennas, metamaterial-based lenses and antennas for improving coverage of terahertz band signals, high-dimensional space multiplexing technology using OAM (Orbital Angular Momentum), and RIS (Reconfigurable Intelligent Surface), but also full-duplex technology for increasing frequency efficiency of 6G mobile communication technologies and improving system networks, AI-based communication technology for implementing system optimization by utilizing satellites and AI (Artificial Intelligence) from the design stage and internalizing end-to-end AI support functions, and next-generation distributed computing technology for implementing services at levels of complexity exceeding the limit of UE operation capability by utilizing ultra-high-performance communication and computing resources.

[0008] The present disclosure relates generally to wireless communication systems and, more specifically, the present disclosure relates to method and apparatus for channel state information (CSI) and calibration reporting in a wireless communication system.

[0009] According to an aspect of an exemplary embodiment, there is provided a communication method in a wireless communication system.

[0010] According to an embodiment of the present disclosure, a method performed by a user equipment (UE) in a wireless communication system comprises, receiving, from a base station (BS), first configuration information on a first channel state information (CSI) report with a report quantity set to a cjtc-Dd and second configuration information for a second CSI report with a codebook type set to a typeII-CJT-r18, wherein the cjtc-DD represents a coherent joint transmission calibration (CJTC) of delay offset and the first configuration information includes a higher layer parameter configuring the first CSI report to be linked to the second CSI report, and receiving, from the BS, first CSI-RS resources for the first CSI report and second CSI-RS resources for the second CSI report, wherein the number of the first CSI-RS resources and the number of the second CSI-RS resources are the same as the number of transmission and reception points (TRPs).

[0011] According to an embodiment of the present disclosure, a method performed by a base station (BS) in a wireless communication system, comprises, transmitting, to a user equipment (UE), first configuration information on a first channel state information (CSI) report with a report quantity set to a cjtc-Dd and second configuration information for a second CSI report with a codebook type set to a typeII-CJT-r18, wherein the cjtc-DD represents a coherent joint transmission calibration (CJTC) of delay offset and the first configuration information includes a higher layer parameter configuring the first CSI report to be linked to the second CSI report, and transmitting, to the UE, first CSI-RS resources for the first CSI report and second CSI-RS resources for the second CSI report, wherein the number of the first CSI-RS resources and the number of the second CSI-RS resources are the same as the number of transmission and reception points (TRPs).

[0012] According to an embodiment of the present disclosure, a user equipment (UE) comprises, at least one transceiver, at least one processor communicatively coupled to the at least one transceiver, and at least one memory, communicatively coupled to the at least one processor, storing instructions executable by the at least one processor individually or in any combination to cause the UE to, receive, from a base station (BS), first configuration information on a first channel state information (CSI) report with a report quantity set to a cjtc-Dd and second configuration information for a second CSI report with a codebook type set to a typeII-CJT-r18, wherein the cjtc-DD represents a coherent joint transmission calibration (CJTC) of delay offset and the first configuration information includes a higher layer parameter configuring the first CSI report to be linked to the second CSI report, and receive, from the BS, first CSI-RS resources for the first CSI report and second CSI-RS resources for the second CSI report, wherein the number of the first CSI-RS resources and the number of the second CSI-RS resources are the same as the number of transmission and reception points (TRPs).

[0013] According to an embodiment of the present disclosure, a base station (BS) comprises, at least one transceiver, at least one processor communicatively coupled to the at least one transceiver, and at least one memory, communicatively coupled to the at least one processor, storing instructions executable by the at least one processor individually or in any combination to cause the BS to, transmit, to a user equipment (UE), first configuration information on a first channel state information (CSI) report with a report quantity set to a cjtc-Dd and second configuration information for a second CSI report with a codebook type set to a typeII-CJT-r18, wherein the cjtc-DD represents a coherent joint transmission calibration (CJTC) of delay offset and the first configuration information includes a higher layer parameter configuring the first CSI report to be linked to the second CSI report, and transmit, to the UE, first CSI-RS resources for the first CSI report and second CSI-RS resources for the second CSI report, wherein the number of the first CSI-RS resources and the number of the second CSI-RS resources are the same as the number of transmission and reception points (TRPs).

[0014] Aspects of the present disclosure provide efficient communication methods in a wireless communication system.

[0015] For a more complete understanding of the present disclosure and its advantages, reference is now made to the following description taken in conjunction with the accompanying drawings, in which like reference numerals represent like parts:

[0016] FIG. 1 illustrates an example wireless network according to embodiments of the present disclosure;

[0017] FIG. 2 illustrates an example gNodeB (gNB) according to embodiments of the present disclosure;

[0018] FIG. 3 illustrates an example UE according to embodiments of the present disclosure;

[0019] FIG. 4A and 4B illustrate an example of a wireless transmit and receive paths according to embodiments of the present disclosure;

[0020] FIG. 5 illustrates an example of a transmitter structure for beamforming according to embodiments of the present disclosure;

[0021] FIG. 6 illustrates an example of a transmitter structure for physical downlink shared channel (PDSCH) in a subframe according to embodiments of the present disclosure;

[0022] FIG. 7 illustrates an example of a receiver structure for PDSCH in a subframe according to embodiments of the present disclosure;

[0023] FIG. 8 illustrates an example of a transmitter structure for physical uplink shared channel (PUSCH) in a subframe according to embodiments of the present disclosure;

[0024] FIG. 9 illustrates an example of a receiver structure for a PUSCH in a subframe according to embodiments of the present disclosure;

[0025] FIG. 10 illustrates an example antenna port layout according to embodiments of the present disclosure;

[0026] FIG. 11 illustrates examples of a UE moving on a trajectory with antenna groups (AGs) of the BS co-located and distributed a UE moving on a trajectory located in co-located and distributed according to embodiments of the present disclosure;

[0027] FIG. 12 illustrates a signal flow of an example procedure for CSI reporting according to embodiments of the present disclosure;

[0028] FIG. 13 illustrates an example method performed by a UE in a wireless communication system according to embodiments of the present disclosure;

[0029] FIG. 14 is a block diagram of a terminal or user equipment (UE) according to an embodiment of the disclosure;

[0030] FIG. 15 is a block diagram of a base station (BS) according to an embodiment of the disclosure; and

[0031] FIG. 16 is a block diagram of a network entity according to an embodiment of the disclosure.

[0032] The present application claims priority under 35 U.S.C. § 119(e) to U.S. Provisional Patent Application No. 63 / 691,138 filed on September 5, 2024; U.S. Provisional Patent Application No.　63 / 694,608 filed on September 13, 2024; U.S. Provisional Patent Application No. 63 / 697,279 filed on September 20, 2024; U.S. Provisional Patent Application No. 63 / 701,906 filed on October　1,　2024; U.S. Provisional Patent Application No. 63 / 707,537; and U.S Non-Provisional Patent Application No. 19 / 298,096 filed on October 15, 2024, which are hereby incorporated by reference in their entirety.

[0033] Hereinafter, embodiments of the disclosure will be described in detail with reference to the accompanying drawings.

[0034] In describing the embodiments, descriptions related to technical contents well-known in the art and not associated directly with the disclosure will be omitted. Such an omission of unnecessary descriptions is intended to prevent obscuring of the main idea of the disclosure and more clearly transfer the main idea.

[0035] For the same reason, in the accompanying drawings, some elements may be exaggerated, omitted, or schematically illustrated. Further, the size of each element does not completely reflect the actual size. In the drawings, identical or corresponding elements are provided with identical reference numerals or different reference numerals.

[0036] The advantages and features of the disclosure and ways to achieve them will be apparent by making reference to embodiments as described below in detail in conjunction with the accompanying drawings. However, the disclosure is not limited to the embodiments set forth below, but may be implemented in various different forms. The following embodiments are provided only to completely disclose the disclosure and inform those skilled in the art of the scope of the disclosure, and the disclosure is defined only by the scope of the appended claims. Throughout the specification, the same or like reference numerals designate the same or like elements. Furthermore, in describing the disclosure, a detailed description of known functions or constitution incorporated herein will be omitted in the case that it is determined that the description may make the subject matter of the disclosure unnecessarily unclear. The terms which will be described below are terms defined in consideration of the functions in the disclosure, and may be different according to users, intentions of the operators, or customs. Therefore, the definitions of the terms should be made based on the contents throughout the specification.

[0037] Herein, it will be understood that each block of the flowchart illustrations, and combinations of blocks in the flowchart illustrations, may be performed based on computer program instructions. These computer program instructions may be loaded collectively onto at least one processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which perform through any one of, or in any combination of, the at least one processor of the computer or other programmable data processing apparatus, create means for performing the functions specified in the flowchart block(s). These computer program instructions may also be stored in a non-transitory computer usable or computer-readable memory that may 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 perform the function specified in the flowchart block(s). 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 data processing apparatus to produce a computer executed process such that the instructions that perform on the computer or other programmable data processing apparatus provide steps for executing the functions specified in the flowchart block(s).

[0038] Further, each block may represent a module, segment, or portion of code, which includes one or more executable instructions for executing the specified logical function(s). It should also be noted that in some alternative implementations, the functions noted in the blocks may occur out of the order. For example, two blocks(or functions) shown in succession may in fact be performed substantially concurrently or the blocks may sometimes be performed in the reverse order, depending upon the functionality involved.

[0039] As used in embodiments of the disclosure, a “~unit” may refer to a software element or a hardware element, such as a field programmable gate array (FPGA) or an application specific integrated circuit (ASIC), which performs a predetermined function. However, the term including the word “~unit” does not always have a meaning limited to software or hardware. The “~unit” may be constructed either to be stored in an addressable storage medium or to execute one or more processors. Therefore, the “~unit” includes, for example, software elements, object-oriented software elements, components such as class elements and task elements, processes, functions, properties, procedures, sub-routines, segments of a program code, drivers, firmware, micro-codes, circuits, data, database, data structures, tables, arrays, and parameters. The components and functions provided by the “~unit” may be either combined into a smaller number of components and a “~unit,” or divided into additional components and a “~unit.” Moreover, the components and “~units” may be implemented to reproduce one or more central processing units (CPUs) within a device or a security multimedia card. Further, in the embodiments, the “~unit” may include one or more processors.

[0040] It should be appreciated that the blocks in each flowchart and combinations of the flowcharts may be performed by one or more computer programs which include instructions. The entirety of the one or more computer programs may be stored in a single memory device or the one or more computer programs may be divided with different portions stored in different multiple memory devices.

[0041] Any of the functions or operations described herein can be processed by one processor or a combination of processors. The one processor or the combination of processors is circuitry performing processing and includes circuitry like an application processor (AP, e.g. a CPU), a communication processor (CP, e.g., a modem), a graphics processing unit (GPU), a neural processing unit (NPU) (e.g., an artificial intelligence (AI) chip), a Wi-Fi chip, a Bluetooth® chip, a global positioning system (GPS) chip, a near field communication (NFC) chip, connectivity chips, a sensor controller, a touch controller, a finger-print sensor controller, a display driver integrated circuit (IC), an audio CODEC chip, a universal serial bus (USB) controller, a camera controller, an image processing IC, a microprocessor unit (MPU), a system on chip (SoC), an IC, or the like.

[0042] It will be appreciated that various embodiments of the disclosure according to the claims and description in the specification can be realized in the form of hardware, software or a combination of hardware and software.

[0043] Any such software may be stored in non-transitory computer readable storage media. The non-transitory computer readable storage media store one or more computer programs (software modules), the one or more computer programs include computer-executable instructions that, when executed by one or more processors of an electronic device individually or collectively, cause the electronic device to perform a method of the disclosure.

[0044] Any such software may be stored in the form of volatile or non-volatile storage such as, for example, a storage device like read only memory (ROM), whether erasable or rewritable or not, or in the form of memory such as, for example, random access memory (RAM), memory chips, device or integrated circuits or on an optically or magnetically readable medium such as, for example, a compact disk (CD), digital versatile disc (DVD), magnetic disk or magnetic tape or the like. It will be appreciated that the storage devices and storage media are various embodiments of non-transitory machine-readable storage that are suitable for storing a computer program or computer programs comprising instructions that, when executed, implement various embodiments of the disclosure. Accordingly, various embodiments of the present disclosure may provide a program comprising code for implementing apparatus or a method as claimed in any one of the claims of this specification and a non-transitory machine-readable storage storing such a program.

[0045] Hereinafter, the determination of priority between A and B in the present disclosure may refer to various actions such as selecting the one having a higher priority based on a predefined priority rule and performing an operation corresponding thereto, or omitting or dropping an operation corresponding to the one having a lower priority.

[0046] Hereinafter, "A or B" as described in the present disclosure may be understood as "A and / or B," which may include A, or B, or both A and B.

[0047] In addition, "at least one of A, B, and C" as described in the present disclosure may be understood to include A, or B, or C, or any combination of A, B, and C.

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

[0049] Furthermore, "A / B" as described in the present disclosure may be understood as "A and / or B," which may include A, or B, or both A and B.

[0050] Furthermore, "A, B" as described in the present disclosure may be understood as "A and / or B," which may include A, or B, or both A and B.

[0051] Furthermore, "A and B" as described in the present disclosure may be understood as "A and / or B," which may include A, or B, or both A and B.

[0052] Furthermore, “if condition A and condition B are satisfied,” as described in the present disclosure, may not be limited to a case where both condition A and condition B are satisfied, but may be understood to include a case where either condition A or condition B is individually satisfied, both condition A and condition B are satisfied, or one or more additional conditions are satisfied in combination.

[0053] Furthermore, throughout this disclosure, ordinal terms such as "first," "second," "third," etc., (and similar qualifiers) are used merely to distinguish between different instances, occurrences, configurations, messages, stages, or aspects of elements, operations, or information as described herein. Unless the context clearly dictates otherwise, the use of such ordinal terms does not itself require that the elements, operations, or information distinguished by these terms be structurally different, numerically distinct, or substantively dissimilar. For example, a "first signal" and a "second signal" may refer to instances of the same signal transmitted at different times or containing the same core information despite minor variations, or they may refer to signals with different content or characteristics, depending on the specific context. Similarly, a "first value" and a "second value" may represent the same magnitude but measured or applied in different circumstances, or they may represent different magnitudes. The interpretation should be guided by the specific technical context, function, and relationship described in the relevant portion of the specification and claims.

[0054] Furthermore, the terms “first ~”, “second ~”, etc., as described in the present disclosure with respect to various elements (e.g., information, objects, operation, sequences, or the like), should not limit those elements. These terms may only be intended to distinguish one element from another, and may not be intended to indicate a specific order. For example, a first element could be termed a second element, and, similarly, a second element could be termed a first element.

[0055] Furthermore, even if “first ~” and “second ~” are described in the present disclosure, it may be understood that element(s) referred to by “first ~” and “second ~” may be the same or different. For example, in case of element(s) being information, first information and second information may both be same information and, in some cases, are separate and different information.

[0056] In addition, the terms “if ~” and “in case that ~” as used in the disclosure or claims may be interpreted to include the meanings of “when (or upon) ~,” “in response to ~,” “based on ~,” or “according to ~,” and may be used interchangeably with these expressions. In addition, expressions other than those exemplified herein may also be used, as long as they have substantially the same meaning and do not impair the technical features of the present disclosure.

[0057] For example, the physical layer signaling may be referred to as Layer 1 (L1) signaling and may include downlink control information (DCI). In addition, the higher layer signaling may include a medium access control (MAC) control message, a radio resource control (RRC) signaling message, a non-access stratum (NAS) signaling message, or an application layer message. The RRC signaling message may be referred to as L3 (layer 3) signaling. It should be noted, however, that the higher layer signaling is not limited to the aforementioned examples.

[0058] In addition, the term "not perform" as used in the present disclosure or claims may, in context, be understood to mean that the corresponding step is omitted or skipped. Such a term may be replaced with other terms having the same or substantially equivalent meaning.

[0059] In addition, "transmitting a message including A and B" as described in the present disclosure, may be understood as encompassing both (i) transmitting A and B in a single message, and (ii) transmitting A and B separately via multiple messages (e.g., transmitting a first message including A and a second message including B). This interpretation may also apply to messages that include two or more items (e.g., A, B, C), transmitted either together or separately.

[0060] In addition, "transmitting a message including A and transmitting a message including B" may also be interpreted as transmitting a message including A and B in a single message.

[0061] In the specific embodiments of the present disclosure described below, terms or components included in the disclosure may be expressed in singular or plural form depending on the specific embodiments presented. However, such singular or plural expressions are selected appropriately for convenience of description, and the present disclosure is not limited to a singular or plural number of components. A component expressed in the plural form may be implemented as a single component, and a component expressed in the singular form may be implemented as multiple components.

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

[0063] The methods and apparatuses proposed in the embodiments of the present disclosure are not limited to each embodiment individually, but may also be applied in combination of all or some of the embodiments proposed in the disclosure. Therefore, the embodiments of the present disclosure may be modified and applied without significantly departing from the scope of the present disclosure, as would be understood by those skilled in the art.

[0064] In this case, even if certain wordings are described differently across embodiments, they may be used interchangeably or in substitution or in combination if their underlying concepts are equivalent. For example, for the same or equivalent concept, even if one embodiment uses the expression "A" and another embodiment uses the expression "B", such expressions may be understood interchangeably, in substitution, or in combination.

[0065] The terms used in the following description to refer to access nodes, network entities, messages, interfaces between network entities, various types of identification information, and the like, are provided merely for the convenience of explanation by way of example. Therefore, the present disclosure is not limited to the terms described below, and other terms having equivalent technical meanings may also be used. Such terms may also be interchangeable with terms defined in any 3rd generation partnership project (3GPP) technical specifications (TS) where appropriate.

[0066] Hereinafter, a base station is an entity that allocates resources to terminals, and may be at least one of a gNode B, an eNode B, a Node B, a base station (BS), a wireless access unit, a BS controller, or a node on a network.

[0067] Furthermore, the base station of the present disclosure may include a split architecture comprising a central unit (CU) and a distributed unit (DU). In this structure, the CU is configured to process the higher layers of the control and user planes, while the DU is configured to process lower-layer radio resource functions. The embodiments of the present disclosure may be equally applicable to 5G base station architectures in which such CU and DU functional splits are implemented.

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

[0069] In the disclosure, a downlink (DL) refers to a radio link through which a BS transmits a signal to a UE, and an uplink (UL) refers to a radio link through which a UE transmits a signal to a BS.

[0070] Furthermore, hereinafter, 5th generation (5G) mobile communication technologies (e.g., 5G new radio (NR)), 6th generation (6G) mobile communication technologies may be described by way of example, but the embodiments of the present disclosure may also be applied to other communication systems having similar technical backgrounds or channel types. For example, newly evolved mobile communication systems developed after 5G and 6G may be included. Furthermore, based on determinations by those skilled in the art, the embodiments of the present disclosure may also be applied to other communication systems (e.g., Wi-Fi systems) through some modifications without significantly departing from the scope of the present disclosure

[0071] In the following description, the terms physical channel and signal may be used interchangeably with data or control signal. For example, the term physical downlink shared channel (PDSCH) refers to a physical channel through which data is transmitted, but the term PDSCH may also be used to refer to the data itself. That is, in the present disclosure, the expression "transmit a physical channel" may be interpreted as being equivalent to the expression "transmit data or a signal via a physical channel."

[0072] Hereinafter, in the context of the present disclosure, higher layer signaling may refer to signaling corresponding to at least one or any combination of the following: master information block (MIB), system information block (SIB) or SIB M (M = 1, 2, ...), radio resource control (RRC), or medium access control (MAC) control element (CE), or a non-access stratum (NAS) signaling message, or an application layer message. The RRC signaling message may be referred to as L3 (layer 3) signaling.

[0073] In addition, L1 signaling may refer to signaling corresponding to at least one or any combination of signaling techniques using the at least one or any combination of the following physical layer channels or signaling: physical downlink control channel (PDCCH), downlink control information (DCI), user equipment (UE)-specific DCI, group-common DCI, common DCI, scheduling DCI (e.g., DCI used for scheduling downlink or uplink data), non-scheduling DCI (e.g., DCI not used for scheduling downlink or uplink data) physical uplink control channel (PUCCH), or uplink control information (UCI). The L1 signaling message may be referred to as a physical layer signaling.

[0074] Hereinafter, the expression that information is configured by the BS, as used in the present disclosure or claims, may, in context, be understood to mean that the terminal receives the corresponding information from the BS via a physical layer signaling or a higher layer signaling. Such an expression may be replaced with other terms having the same or substantially equivalent meaning.

[0075] Hereinafter, the operational principle of the present disclosure will be described in detail with reference to the accompanying drawings.

[0076] Wireless communication has been one of the most successful innovations in modern history. Recently, the number of subscribers to wireless communication services exceeded five billion and continues to grow quickly. The demand of wireless data traffic is rapidly increasing due to the growing popularity among consumers and businesses of smart phones and other mobile data devices, such as tablets, “note pad” computers, net books, eBook readers, and machine type of devices. In order to meet the high growth in mobile data traffic and support new applications and deployments, improvements in radio interface efficiency and coverage are of paramount importance. To meet the demand for wireless data traffic having increased since deployment of 4G communication systems, and to enable various vertical applications, 5G communication systems have been developed and are currently being deployed.

[0077] The present disclosure relates to for CSI and calibration reporting.

[0078] In one embodiment, a user equipment (UE) is provided. The UE includes a transceiver configured to receive information related to first and second CSI reports. The information for the first CSI report indicatesNTRPCSI reference signal (CSI-RS) resource sets,NTRP> 1, and a report quantity set to 'cjtc-Dd'. The information for the second CSI report indicatesNTRPCSI-RS resources, a report quantity set to 'cri-RI-PMI-CQI', and a codebook type set to 'typeII-CJT-r18'. The first CSI report is linked to the second CSI report via a radio resource control (RRC) parameter. The UE further includes a processor operably coupled to the transceiver. The processor is configured to determine, based on the information, a CSI for the second CSI report. The transceiver is further configured to transmit the second CSI report including the CSI.

[0079] In another embodiment, a base station (BS) is provided. The BS includes a processor and a transceiver operably coupled to the processor. The transceiver is configured to transmit, to a UE, information related to first and second CSI reports and receive, from the UE, the second CSI report including a CSI that is based on the information. The information for the first CSI report indicatesNTRPCSI-RS resource sets withNTRP> 1 and a report quantity set to 'cjtc-Dd'. The information for the second CSI report indicatesNTRPCSI-RS resources, a report quantity set to 'cri-RI-PMI-CQI', and a codebook type set to 'typeII-CJT-r18'. The first CSI report is linked to the second CSI report via a RRC parameter.

[0080] In yet another embodiment, a method performed by a UE is provided. The method includes receiving information related to first and second CSI reports. The information for the first CSI report indicatesNTRPCSI-RS resource sets withNTRP> 1 and a report quantity set to 'cjtc-Dd'. The information for the second CSI report indicatesNTRPCSI-RS resources, a report quantity set to 'cri-RI-PMI-CQI', and a codebook type set to 'typeII-CJT-r18'. The first CSI report is linked to the second CSI report via a RRC parameter. The method further includes determining, based on the information, a CSI for the second CSI report and transmitting the second CSI report including the CSI.

[0081] Other technical features may be readily apparent to one skilled in the art from the following figures, descriptions, and claims.

[0082] Before undertaking the DETAILED DESCRIPTION below, it may be advantageous to set forth definitions of certain words and phrases used throughout this patent document. The term “couple” and its derivatives refer to any direct or indirect communication between two or more elements, whether or not those elements are in physical contact with one another. The terms “transmit,” “receive,” and “communicate,” as well as derivatives thereof, encompass both direct and indirect communication. The terms “include” and “comprise,” as well as derivatives thereof, mean inclusion without limitation. The term “or” is inclusive, meaning and / or. The phrase “associated with,” as well as derivatives thereof, means to include, be included within, interconnect with, contain, be contained within, connect to or with, couple to or with, be communicable with, cooperate with, interleave, juxtapose, be proximate to, be bound to or with, have, have a property of, have a relationship to or with, or the like. The term “controller” means any device, system, or part thereof that controls at least one operation. Such a controller may be implemented in hardware or a combination of hardware and software and / or firmware. The functionality associated with any particular controller may be centralized or distributed, whether locally or remotely. The phrase “at least one of,” when used with a list of items, means that different combinations of one or more of the listed items may be used, and only one item in the list may be needed. For example, “at least one of: A, B, and C” includes any of the following combinations: A, B, C, A and B, A and C, B and C, and A and B and C.

[0083] Moreover, various functions described below can 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. A “non-transitory” computer readable medium excludes wired, wireless, optical, or other communication links that transport transitory electrical or other signals. A non-transitory computer readable medium includes media where data can be permanently stored and media where data can be stored and later overwritten, such as a rewritable optical disc or an erasable memory device.

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

[0085] FIGS. 1-13 discussed below, and the various, non-limiting 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 understand that the principles of the present disclosure may be implemented in any suitably arranged system or device.

[0086] To meet the demand for wireless data traffic having increased since deployment of 4G communication systems, and to enable various vertical applications, 5G / NR communication systems have been developed and are currently being deployed. The 5G / NR communication system is implemented in higher frequency (mmWave) bands, e.g., 28 GHz or 60GHz bands, so as to accomplish higher data rates or in lower frequency bands, such as 6 GHz, to enable robust coverage and mobility support. To decrease propagation loss of the radio waves and increase the transmission distance, the beamforming, massive multiple-input multiple-output (MIMO), full dimensional MIMO (FD-MIMO), array antenna, an analog beam forming, large scale antenna techniques are discussed in 5G / NR communication systems.

[0087] In addition, in 5G / NR communication systems, development for system network improvement is under way based on advanced small cells, cloud radio access networks (RANs), ultra-dense networks, device-to-device (D2D) communication, wireless backhaul, moving network, cooperative communication, coordinated multi-points (CoMP), reception-end interference cancelation and the like.

[0088] The discussion of 5G systems and frequency bands associated therewith is for reference as certain embodiments of the present disclosure may be implemented in 5G systems.　 However, the present disclosure is not limited to 5G systems, or the frequency bands associated therewith, and embodiments of the present disclosure may be utilized in connection with any frequency band. For example, aspects of the present disclosure may also be applied to deployment of 5G communication systems, 6G, or even later releases which may use terahertz (THz) bands.

[0089] The following documents and standards descriptions are hereby incorporated by reference into the present disclosure as if fully set forth herein: [REF 1] 3GPP TS 36.211 v18.0.1, “E-UTRA, Physical channels and modulation;” [REF 2] 3GPP TS 36.212 v18.0.0, “E-UTRA, Multiplexing and Channel coding;” [REF 3] 3GPP TS 36.213 v18.2.0, “E-UTRA, Physical Layer Procedures;” [REF 4] 3GPP TS 36.321 v18.2.0, “E-UTRA, Medium Access Control (MAC) protocol specification;” [REF　5] 3GPP TS 36.331 v18.2.0, “E-UTRA, Radio Resource Control (RRC) Protocol Specification;” [REF　6] 3GPP TR 22.891 v1.2.0; [REF 7-8] 3GPP TS 38.212 v18.2.0- v18.3.0, “E-UTRA, NR, Multiplexing and Channel coding;” [REF 9-10] 3GPP TS 38.214 v18.2.0-v18.3.0, “E-UTRA, NR, Physical layer procedures for data;” [REF 11-12] 3GPP TS 38.211 v18.2.0-v18.3.0, “E-UTRA, NR, Physical channels and modulation;” [REF 13] 3GPP TS 38.213 v18.3.0, “E-UTRA, NR; Physical layer procedures for control;” and [REF 14] 3GPP TS 38.331 v18.2.0, “E-UTRA, NR; Radio Resource Control (RRC); Protocol specification.”

[0090] FIGS. 1-12 below describe various embodiments implemented in wireless communications systems and with the use of orthogonal frequency division multiplexing (OFDM) or orthogonal frequency division multiple access (OFDMA) communication techniques. The descriptions of FIGS. 1-3 are not meant to imply physical or architectural limitations to how different embodiments may be implemented. Different embodiments of the present disclosure may be implemented in any suitably arranged communications system.

[0091] FIG. 1 illustrates an example wireless network 100 according to embodiments of the present disclosure. The embodiment of the wireless network 100 shown in FIG. 1 is for illustration only. Other embodiments of the wireless network 100 could be used without departing from the scope of the present disclosure.

[0092] As shown in FIG. 1, the wireless network 100 includes a gNB 101 (e.g., base station, BS), a gNB 102, and a gNB 103. The gNB 101 communicates with the gNB 102 and the gNB 103. The gNB 101 also communicates with at least one network 130, such as the Internet, a proprietary Internet Protocol (IP) network, or other data network.

[0093] The gNB 102 provides wireless broadband access to the network 130 for a first plurality of user equipments (UEs) within a coverage area 120 of the gNB 102. The first plurality of UEs includes a UE 111, which may be located in a small business; a UE 112, which may be located in an enterprise; a UE 113, which may be a WiFi hotspot; a UE 114, which may be located in a first residence; a UE 115, which may be located in a second residence; and a UE 116, which may be a mobile device, such as a cell phone, a wireless laptop, a wireless PDA, or the like. The gNB 103 provides wireless broadband access to the network 130 for a second plurality of UEs within a coverage area 125 of the gNB 103. The second plurality of UEs includes the UE 115 and the UE 116. In some embodiments, one or more of the gNBs 101-103 may communicate with each other and with the UEs 111-116 using 5G / NR, long term evolution (LTE), long term evolution-advanced (LTE-A), WiMAX, WiFi, or other wireless communication techniques.

[0094] Depending on the network type, the term “base station” or “BS” can refer to any component (or collection of components) configured to provide wireless access to a network, such as transmit point (TP), transmit-receive point (TRP), an enhanced base station (eNodeB or eNB), a 5G / NR base station (gNB), a macrocell, a femtocell, a WiFi access point (AP), or other wirelessly enabled devices. Base stations may provide wireless access in accordance with one or more wireless communication protocols, e.g., 5G / NR 3rdgeneration partnership project (3GPP) NR, long term evolution (LTE), LTE advanced (LTE-A), high speed packet access (HSPA), Wi-Fi 802.11a / b / g / n / ac, etc. For the sake of convenience, the terms “BS” and “TRP” are used interchangeably in this patent document to refer to network infrastructure components that provide wireless access to remote terminals. Also, depending on the network type, the term “user equipment” or “UE” can refer to any component such as “mobile station,” “subscriber station,” “remote terminal,” “wireless terminal,” “receive point,” or “user device.” For the sake of convenience, the terms “user equipment” and “UE” are used in this patent document to refer to remote wireless equipment that wirelessly accesses a BS, whether the UE is a mobile device (such as a mobile telephone or smartphone) or is normally considered a stationary device (such as a desktop computer or vending machine).

[0095] The dotted lines show the approximate extents of the coverage areas 120 and 125, which are shown as approximately circular for the purposes of illustration and explanation only. It should be clearly understood that the coverage areas associated with gNBs, such as the coverage areas 120 and 125, may have other shapes, including irregular shapes, depending upon the configuration of the gNBs and variations in the radio environment associated with natural and man-made obstructions.

[0096] As described in more detail below, one or more of the UEs 111-116 include circuitry, programing, or a combination thereof for performing CSI and calibration reporting. In certain embodiments, one or more of the BSs 101-103 include circuitry, programing, or a combination thereof to support CSI and calibration reporting.

[0097] Although FIG. 1 illustrates one example of a wireless network, various changes may be made to FIG. 1. For example, the wireless network 100 could include any number of gNBs and any number of UEs in any suitable arrangement. Also, the gNB 101 could communicate directly with any number of UEs and provide those UEs with wireless broadband access to the network 130. Similarly, each gNB 102-103 could communicate directly with the network 130 and provide UEs with direct wireless broadband access to the network 130. Further, the gNBs 101, 102, and / or 103 could provide access to other or additional external networks, such as external telephone networks or other types of data networks.

[0098] FIG. 2 illustrates an example gNB 102 according to embodiments of the present disclosure. The embodiment of the gNB 102 illustrated in FIG. 2 is for illustration only, and the gNBs 101 and 103 of FIG. 1 could have the same or similar configuration. However, gNBs come in a wide variety of configurations, and FIG. 2 does not limit the scope of the present disclosure to any particular implementation of a gNB.

[0099] As shown in FIG. 2, the gNB 102 includes multiple antennas 205a-205n, multiple transceivers 210a-210n, a controller / processor 225, a memory 230, and a backhaul or network interface 235.

[0100] The transceivers 210a-210n receive, from the antennas 205a-205n, incoming radio frequency (RF) signals, such as signals transmitted by UEs in the wireless network 100. The transceivers 210a-210n down-convert the incoming RF signals to generate IF or baseband signals. The IF or baseband signals are processed by receive (RX) processing circuitry in the transceivers 210a-210n and / or controller / processor 225, which generates processed baseband signals by filtering, decoding, and / or digitizing the baseband or IF signals. The controller / processor 225 may further process the baseband signals.

[0101] Transmit (TX) processing circuitry in the transceivers 210a-210n and / or controller / processor 225 receives analog or digital data (such as voice data, web data, e-mail, or interactive video game data) from the controller / processor 225. The TX processing circuitry encodes, multiplexes, and / or digitizes the outgoing baseband data to generate processed baseband or IF signals. The transceivers 210a-210n up-converts the baseband or IF signals to RF signals that are transmitted via the antennas 205a-205n.

[0102] The controller / processor 225 can include one or more processors or other processing devices that control the overall operation of the gNB 102. For example, the controller / processor 225 could control the reception of uplink (UL) channel signals and the transmission of downlink (DL) channel signals by the transceivers 210a-210n in accordance with well-known principles. The controller / processor 225 could support additional functions as well, such as more advanced wireless communication functions. For instance, the controller / processor 225 could support beam forming or directional routing operations in which outgoing / incoming signals from / to multiple antennas 205a-205n are weighted differently to effectively steer the outgoing signals in a desired direction. As another example, the controller / processor 225 could support methods for CSI and calibration reporting. Any of a wide variety of other functions could be supported in the gNB 102 by the controller / processor 225.

[0103] The controller / processor 225 is also capable of executing programs and other processes resident in the memory 230, such as processes to support CSI and calibration reporting. The controller / processor 225 can move data into or out of the memory 230 as required by an executing process.

[0104] The controller / processor 225 is also coupled to the backhaul or network interface 235. The backhaul or network interface 235 allows the gNB 102 to communicate with other devices or systems over a backhaul connection or over a network. The interface 235 could support communications over any suitable wired or wireless connection(s). For example, when the gNB 102 is implemented as part of a cellular communication system (such as one supporting 5G / NR, LTE, or LTE-A), the interface 235 could allow the gNB 102 to communicate with other gNBs over a wired or wireless backhaul connection. When the gNB 102 is implemented as an access point, the interface 235 could allow the gNB 102 to communicate over a wired or wireless local area network or over a wired or wireless connection to a larger network (such as the Internet). The interface 235 includes any suitable structure supporting communications over a wired or wireless connection, such as an Ethernet or transceiver.

[0105] The memory 230 is coupled to the controller / processor 225. Part of the memory 230 could include a RAM, and another part of the memory 230 could include a Flash memory or other ROM.

[0106] Although FIG. 2 illustrates one example of gNB 102, various changes may be made to FIG. 2. For example, the gNB 102 could include any number of each component shown in FIG. 2. Also, various components in FIG. 2 could be combined, further subdivided, or omitted and additional components could be added according to particular needs.

[0107] FIG. 3 illustrates an example UE 116 according to embodiments of the present disclosure. The embodiment of the UE 116 illustrated in FIG. 3 is for illustration only, and the UEs 111-115 of FIG. 1 could have the same or similar configuration. However, UEs come in a wide variety of configurations, and FIG. 3 does not limit the scope of the present disclosure to any particular implementation of a UE.

[0108] As shown in FIG. 3, the UE　116 includes antenna(s) 305, a transceiver(s) 310, and a microphone 320. The UE　116 also includes a speaker 330, a processor 340, an input / output (I / O) interface (IF) 345, an input 350, a display 355, and a memory 360. The memory 360 includes an operating system (OS) 361 and one or more applications 362.

[0109] The transceiver(s) 310 receives from the antenna(s) 305, an incoming RF signal transmitted by a gNB of the wireless network 100. The transceiver(s) 310 down-converts the incoming RF signal to generate an intermediate frequency (IF) or baseband signal. The IF or baseband signal is processed by RX processing circuitry in the transceiver(s) 310 and / or processor 340, which generates a processed baseband signal by filtering, decoding, and / or digitizing the baseband or IF signal. The RX processing circuitry sends the processed baseband signal to the speaker 330 (such as for voice data) or is processed by the processor 340 (such as for web browsing data).

[0110] TX processing circuitry in the transceiver(s) 310 and / or processor 340 receives analog or digital voice data from the microphone 320 or other outgoing baseband data (such as web data, e-mail, or interactive video game data) from the processor 340. The TX processing circuitry encodes, multiplexes, and / or digitizes the outgoing baseband data to generate a processed baseband or IF signal. The transceiver(s) 310 up-converts the baseband or IF signal to an RF signal that is transmitted via the antenna(s) 305.

[0111] The processor 340 can include one or more processors or other processing devices and execute the OS 361 stored in the memory 360 in order to control the overall operation of the UE 116. For example, the processor 340 could control the reception of DL channel signals and the transmission of UL channel signals by the transceiver(s) 310 in accordance with well-known principles. In some embodiments, the processor 340 includes at least one microprocessor or microcontroller.

[0112] The processor 340 is also capable of executing other processes and programs resident in the memory 360. For example, the processor 340 may execute processes for CSI and calibration reporting as described in embodiments of the present disclosure. The processor 340 can move data into or out of the memory 360 as required by an executing process. In some embodiments, the processor 340 is configured to execute the applications 362 based on the OS 361 or in response to signals received from gNBs or an operator. The processor 340 is also coupled to the I / O interface 345, which provides the UE 116 with the ability to connect to other devices, such as laptop computers and handheld computers. The I / O interface 345 is the communication path between these accessories and the processor 340.

[0113] The processor 340 is also coupled to the input 350, which includes, for example, a touchscreen, keypad, etc., and the display 355. The operator of the UE 116 can use the input 350 to enter data into the UE 116. The display 355 may be a liquid crystal display, light emitting diode display, or other display capable of rendering text and / or at least limited graphics, such as from web sites.

[0114] The memory 360 is coupled to the processor 340. Part of the memory 360 could include a random-access memory (RAM), and another part of the memory 360 could include a Flash memory or other read-only memory (ROM).

[0115] Although FIG. 3 illustrates one example of UE 116, various changes may be made to FIG. 3. For example, various components in FIG. 3 could be combined, further subdivided, or omitted and additional components could be added according to particular needs. As a particular example, the processor 340 could be divided into multiple processors, such as one or more central processing units (CPUs) and one or more graphics processing units (GPUs). In another example, the transceiver(s) 310 may include any number of transceivers and signal processing chains and may be connected to any number of antennas. Also, while FIG. 3 illustrates the UE 116 configured as a mobile telephone or smartphone, UEs could be configured to operate as other types of mobile or stationary devices.

[0116] FIG. 4A and FIG. 4B illustrate an example of wireless transmit and receive paths 400 and 450, respectively, according to embodiments of the present disclosure. For example, a transmit path 400 may be described as being implemented in a gNB (such as gNB 102), while a receive path 450 may be described as being implemented in a UE (such as UE 116). However, it will be understood that the receive path 450 can be implemented in a gNB and that the transmit path 400 can be implemented in a UE. In some embodiments, the transmit path 400 is configured for CSI and calibration reporting as described in embodiments of the present disclosure. In some embodiments, the receive path 450 is configured for CSI and calibration reporting as described in embodiments of the present disclosure.

[0117] As illustrated in FIG. 4A, the transmit path 400 includes a channel coding and modulation block 405, a serial-to-parallel (S-to-P) block 410, a size N Inverse Fast Fourier Transform (IFFT) block 415, a parallel-to-serial (P-to-S) block 420, an add cyclic prefix block 425, and an up-converter (UC) 430. The receive path 450 includes a down-converter (DC) 455, a remove cyclic prefix block 460, a S-to-P block 465, a size N Fast Fourier Transform (FFT) block 470, a parallel-to-serial (P-to-S) block 475, and a channel decoding and demodulation block 480.

[0118] In the transmit path 400, the channel coding and modulation block 405 receives a set of information bits, applies coding (such as a low-density parity check (LDPC) coding), and modulates the input bits (such as with Quadrature Phase Shift Keying (QPSK) or Quadrature Amplitude Modulation (QAM)) to generate a sequence of frequency-domain modulation symbols. The serial-to-parallel block 410 converts (such as de-multiplexes) the serial modulated symbols to parallel data in order to generate N parallel symbol streams, where N is the IFFT / FFT size used in the gNB and the UE. The size N IFFT block 415 performs an IFFT operation on the N parallel symbol streams to generate time-domain output signals. The parallel-to-serial block 420 converts (such as multiplexes) the parallel time-domain output symbols from the size N IFFT block 415 in order to generate a serial time-domain signal. The add cyclic prefix block 425 inserts a cyclic prefix to the time-domain signal. The up-converter 430 modulates (such as up-converts) the output of the add cyclic prefix block 425 to a RF frequency for transmission via a wireless channel. The signal may also be filtered at a baseband before conversion to the RF frequency.

[0119] As illustrated in FIG. 4B, the down-converter 455 down-converts the received signal to a baseband frequency, and the remove cyclic prefix block 460 removes the cyclic prefix to generate a serial time-domain baseband signal. The serial-to-parallel block 465 converts the time-domain baseband signal to parallel time-domain signals. The size N FFT block 470 performs an FFT algorithm to generate N parallel frequency-domain signals. The (P-to-S) block 475 converts the parallel frequency-domain signals to a sequence of modulated data symbols. The channel decoding and demodulation block 480 demodulates and decodes the modulated symbols to recover the original input data stream.

[0120] Each of the gNBs 101-103 may implement a transmit path 400 that is analogous to transmitting in the downlink to UEs 111-116 and may implement a receive path 450 that is analogous to receiving in the uplink from UEs 111-116. Similarly, each of UEs 111-116 may implement a transmit path 400 for transmitting in the uplink to gNBs 101-103 and may implement a receive path 450 for receiving in the downlink from gNBs 101-103.

[0121] Each of the components in FIGS. 4A and 4B can be implemented using only hardware or using a combination of hardware and software / firmware. As a particular example, at least some of the components in FIGS. 4A and 4B may be implemented in software, while other components may be implemented by configurable hardware or a mixture of software and configurable hardware. For instance, the FFT block 470 and the IFFT block 415 may be implemented as configurable software algorithms, where the value of size N may be modified according to the implementation.

[0122] Furthermore, although described as using FFT and IFFT, this is by way of illustration only and should not be construed to limit the scope of the present disclosure. Other types of transforms, such as Discrete Fourier Transform (DFT) and Inverse Discrete Fourier Transform (IDFT) functions, can be used. It will be appreciated that the value of the variable N may be any integer number (such as 1, 2, 3, 4, or the like) for DFT and IDFT functions, while the value of the variable N may be any integer number that is a power of two (such as 1, 2, 4, 8, 16, or the like) for FFT and IFFT functions.

[0123] Although FIGS. 4A and 4B illustrate examples of wireless transmit and receive paths 400 and 450, respectively, various changes may be made to FIGS. 4A and 4B. For example, various components in FIGS. 4A and 4B can be combined, further subdivided, or omitted and additional components can be added according to particular needs. Also, FIGS. 4A and 4B are meant to illustrate examples of the types of transmit and receive paths that can be used in a wireless network. Any other suitable architectures can be used to support wireless communications in a wireless network.

[0124] FIG. 5 illustrates an example of a transmitter structure 500 for beamforming according to embodiments of the present disclosure. In certain embodiments, one or more of gNB 102 or UE 116 includes the transmitter structure 500. For example, one or more of antenna 205 and its associated systems or antenna 305 and its associated systems can be included in transmitter structure 500. This example is for illustration only and other embodiments can be used without departing from the scope of the present disclosure.

[0125] Accordingly, embodiments of the present disclosure recognize that Rel-14 LTE and Rel-15 NR support up to 32 CSI reference signal (CSI-RS) antenna ports which enable an eNB or a gNB to be equipped with a large number of antenna elements (such as 64 or 128). A plurality of antenna elements can then be mapped onto one CSI-RS port. For mmWave bands, although a number of antenna elements can be larger for a given form factor, a number of CSI-RS ports, that can correspond to the number of digitally precoded ports, can be limited due to hardware constraints (such as the feasibility to install a large number of analog-to-digital converters (ADCs) / digital-to-analog converters (DACs) at mmWave frequencies) as illustrated in FIG. 5. Then, one CSI-RS port can be mapped onto a large number of antenna elements that can be controlled by a bank of analog phase shifters 501. One CSI-RS port can then correspond to one sub-array which produces a narrow analog beam through analog beamforming 505. This analog beam can be configured to sweep across a wider range of angles 520 by varying the phase shifter bank across symbols or slots / subframes. The number of sub-arrays (equal to the number of RF chains) is the same as the number of CSI-RS portsNCSI-PORT. A digital beamforming unit 510 performs a linear combination acrossNCSI-PORTanalog beams to further increase a precoding gain. While analog beams are wideband (hence not frequency-selective), digital precoding can be varied across frequency sub-bands or resource blocks. Receiver operation can be conceived analogously.

[0126] Since the transmitter structure 500 of FIG. 5 utilizes multiple analog beams for transmission and reception (wherein one or a small number of analog beams are selected out of a large number, for instance, after a training duration that is occasionally or periodically performed), the term “multi-beam operation” is used to refer to the overall system aspect. This includes, for the purpose of illustration, indicating the assigned DL or UL TX beam (also termed “beam indication”), measuring at least one reference signal for calculating and performing beam reporting (also termed “beam measurement” and “beam reporting”, respectively), and receiving a DL or UL transmission via a selection of a corresponding RX beam. The system of FIG. 5 is also applicable to higher frequency bands such as >52.6GHz (also termed frequency range 4 or FR4). In this case, the system can employ only analog beams. Due to the O2 absorption loss around 60 GHz frequency (~10 dB additional loss per 100 m distance), a larger number and narrower analog beams (hence a larger number of radiators in the array) are essential to compensate for the additional path loss.

[0127] FIG. 6 illustrates an example of a transmitter structure 600 for PDSCH in a subframe according to embodiments of the present disclosure. For example, transmitter structure 600 can be implemented in gNB 102 of FIG. 1. This example is for illustration only and other embodiments can be used without departing from the scope of the present disclosure.

[0128] As illustrated in FIG. 6, information bits 610 are encoded by encoder 620, such as a turbo encoder, and modulated by modulator 630, for example using Quadrature Phase Shift Keying (QPSK) modulation. A Serial to Parallel (S / P) converter 640 generates M modulation symbols that are subsequently provided to a mapper 650 to be mapped to REs selected by a transmission BW selection unit 655 for an assigned PDSCH transmission BW, unit 660 applies an Inverse Fast Fourier Transform (IFFT), the output is then serialized by a Parallel to Serial (P / S) converter 670 to create a time domain signal, filtering is applied by filter 680, and a signal transmitted 690. Additional functionalities, such as data scrambling, cyclic prefix insertion, time windowing, interleaving, and others are well known in the art and are not shown for brevity.

[0129] FIG. 7 illustrates an example of a receiver structure 700 for PDSCH in a subframe according to embodiments of the present disclosure. For example, receiver structure 700 can be implemented by any of the UEs 111-116 of FIG. 1. This example is for illustration only and other embodiments can be used without departing from the scope of the present disclosure.

[0130] With reference to FIG. 7, a received signal 710 is filtered by filter 720, REs 730 for an assigned reception BW are selected by BW selector 735, unit 740 applies a Fast Fourier Transform (FFT), and an output is serialized by a parallel-to-serial converter 750. Subsequently, a demodulator 760 coherently demodulates data symbols by applying a channel estimate obtained from a demodulation reference signal　(DMRS) or a CRS (not shown), and a decoder 770, such as a turbo decoder, decodes the demodulated data to provide an estimate of the information data bits 780. Additional functionalities such as time-windowing, cyclic prefix removal, de-scrambling, channel estimation, and de-interleaving are not shown for brevity.

[0131] FIG. 8 illustrates an example of a transmitter structure 800 for PUSCH in a subframe according to embodiments of the present disclosure. For example, transmitter structure 800 can be implemented in gNB 103 of FIG. 1. This example is for illustration only and other embodiments can be used without departing from the scope of the present disclosure.

[0132] As illustrated in FIG. 8, information data bits 810 are encoded by encoder 820, such as a turbo encoder, and modulated by modulator 830. A Discrete Fourier Transform (DFT) unit 840 applies a DFT on the modulated data bits, REs 850 corresponding to an assigned PUSCH transmission BW are selected by transmission BW selection unit 855, unit 860 applies an IFFT and, after a cyclic prefix insertion (not shown), filtering is applied by filter 870 and a signal transmitted 880.

[0133] FIG. 9 illustrates an example of a receiver structure 900 for a PUSCH in a subframe according to embodiments of the present disclosure; For example, receiver structure 900 can be implemented by the UE 116 of FIG. 3. This example is for illustration only and other embodiments can be used without departing from the scope of the present disclosure.

[0134] As illustrated in FIG. 9, a received signal 910 is filtered by filter 920. Subsequently, after a cyclic prefix is removed (not shown), unit 930 applies a FFT, REs 940 corresponding to an assigned PUSCH reception BW are selected by a reception BW selector 945, unit 950 applies an Inverse DFT (IDFT), a demodulator 960 coherently demodulates data symbols by applying a channel estimate obtained from a DMRS (not shown), a decoder 970, such as a turbo decoder, decodes the demodulated data to provide an estimate of the information data bits 980.

[0135] The present disclosure relates generally to wireless communication systems and, more specifically, toantenna calibration and CSI reporting.

[0136] A communication system includes a DownLink (DL) that conveys signals from transmission points such as Base Stations (BSs) or NodeBs to User Equipments (UEs) and an UpLink (UL) that conveys signals from UEs to reception points such as NodeBs. A UE, also commonly referred to as a terminal or a mobile station, may be fixed or mobile and may be a cellular phone, a personal computer device, or an automated device. An eNodeB (eNB) or gNodeB (gNB), which is generally a fixed station, may also be referred to as an access point or other equivalent terminology. For LTE systems, a NodeB is often referred as an eNodeB. For NR systems, a NodeB is often referred as an gNodeB.

[0137] In a communication system, such as NR or LTE, DL signals can include data signals conveying information content, control signals conveying DL Control Information (DCI), and Reference Signals (RS) that are also known as pilot signals. An eNodeB transmits data information through a Physical DL Shared CHannel (PDSCH). An eNB / gNB transmits DCI through a Physical DL Control CHannel (PDCCH). An eNB / gNB transmits one or more of multiple types of RS including a Channel State Information RS (CSI-RS), or a DeModulation RS (DMRS). An eNB / gNB may transmit a CSI-RS for time / frequency tracking (aka CRS in LTE or tracking reference signal (TRS) in NR), for CSI reporting. DMRS can be transmitted only in the BW of a respective PDSCH and a UE can use the DMRS to demodulate data or control information in a PDSCH or a PDCCH, respectively. A transmission time interval for DL channels is referred to as a subframe or slot and can have, for example, duration of 1 millisecond or a value depending on the subcarrier-spacing (SCS).

[0138] DL signals also include transmission of a logical channel that carries system control information. A broadcast control channel (BCCH) is mapped to either a transport channel referred to as a Broadcast CHannel (BCH) when it conveys a Master Information Block (MIB) or to a DL Shared CHannel (DL-SCH) when it conveys a System Information Block (SIB) - see also REF3 and REF 5. Most system information is included in different SIBs that are transmitted using DL-SCH. A presence of system information on a DL-SCH in a subframe (or slot) can be indicated by a transmission of a corresponding PDCCH conveying a codeword with a cyclic redundancy check (CRC) scrambled with a special System Information radio network temporary identifier (SI-RNTI). Alternatively, scheduling information for a SIB transmission can be provided in an earlier SIB and scheduling information for the first SIB (SIB-1) can be provided by the MIB.

[0139] DL resource allocation is performed in a unit of subframe (or slot) and a group of Physical resource blocks (PRBs). A transmission BW includes frequency resource units referred to as Resource Blocks (RBs). Each RB includes sub-carriers, or Resource Elements (REs), such as 12 REs. A unit of one RB over one subframe (or slot) is referred to as a PRB. A UE can be allocated RBs for a total of REs for the PDSCH transmission BW.

[0140] UL signals can include data signals conveying data information, control signals conveying UL Control Information (UCI), and UL RS. UL RS includes DMRS and Sounding RS (SRS). A UE transmits DMRS only in a BW of a respective PUSCH or PUCCH. An eNB / gNB can use a DMRS to demodulate data signals or UCI signals. A UE transmits SRS to provide an eNB / gNB with an UL CSI. A UE transmits data information or UCI through a respective Physical UL Shared CHannel (PUSCH) or a Physical UL Control CHannel (PUCCH). If a UE needs to transmit data information and UCI in a same UL subframe (or slot), it may multiplex both in a PUSCH. UCI includes Hybrid Automatic Repeat reQuest ACKnowledgement (HARQ-ACK) information, indicating correct (ACK) or incorrect (NACK) detection for a data TB in a PDSCH or absence of a PDCCH detection (DTX), Scheduling Request (SR) indicating whether a UE has data in its buffer, and Channel State Information (CSI) enabling an eNB / gNB to perform link adaptation for PDSCH transmissions to a UE. HARQ-ACK information is also transmitted by a UE in response to a detection of a PDCCH indicating a release of semi-persistently scheduled PDSCH (see also REF 3).

[0141] An UL subframe (or slot) includes two slots. Each slot includes symbols for transmitting data information, UCI, DMRS, or SRS. A frequency resource unit of an UL system BW is a RB. A UE is allocated RBs for a total of REs for a transmission BW. A last few subframe (or slot) symbols can be used to multiplex SRS transmissions from one or more UEs.

[0142] There are two types of frequency range (FR) defined in 3GPP 5G NR specifications. The sub-6 GHz range is called frequency range 1 (FR1) and millimeter wave range is called frequency range 2 (FR2). An example of the frequency range for FR1 and FR2 is shown herein.

[0143]

[0144] For MIMO in FR1, up to 32 CSI-RS antenna ports in one CSI-RS resource is supported, and in FR2, up to 8 CSI-RS antenna ports in one CSI-RS resource is supported. A (spatial or digital) precoding / beamforming can be used across these large number of antenna ports in order to achieve MIMO gains. Depending on the carrier frequency, and the feasibility of RF / HW-related components, the (spatial) precoding / beamforming can be fully digital or hybrid analog-digital.

[0145] In fully digital beamforming, there can be one-to-one mapping between an antenna port and an antenna element, or a 'static / fixed' virtualization of multiple antenna elements to one antenna port can be used. Each antenna port can be digitally controlled. Hence, a spatial multiplexing across antenna ports is provided.

[0146] In next generation cellular standards (e.g. 6G), in addition to FR1 and FR2, new carrier frequency bands can be provided, e.g., FR4 (>52.6GHz), terahertz (>100GHz) and upper mid-band (10-15GHz). The number of CSI-RS ports that can be supported for these new bands is likely to be different from FR1 and FR2. In particular, for 10-15GHz band, the max number of CSI-RS antenna ports is likely to be more than FR1, due to smaller antenna form factors, and feasibility of fully digital beamforming (as in FR1) at these frequencies. For instance, the number of CSI-RS antenna ports can grow up to 128. Besides, the NW deployment / topology at these frequencies is also expected to be denser / distributed, for example, antenna ports distributed at multiple (non-co-located, hence geographically separated) TRPs within a cellular region can be the main scenario of interest, due to which the number of CSI-RS antenna ports for MIMO can be even larger (e.g. up to 256).

[0147] Likewise, for a cellular system operating in low carrier frequency in general, a sub-1GHz frequency range (e.g. less than 1 GHz) as an example, supporting large number of CSI-RS antenna ports (e.g. 32) or many antenna elements at a single location or remote radio head (RRH) or TRP is challenging due to a larger antenna form factor size needed taking into account carrier frequency wavelength than a system operating at a higher frequency such as 2 GHz or 4 GHz. At such low frequencies, the maximum number of CSI-RS antenna ports that can be co-located at a site (or RRH or TRP) can be limited, for example to 8. This limits the spectral efficiency of such systems. In particular, the MU-MIMO spatial multiplexing gains offered due to large number of CSI-RS antenna ports (such as 32) can't be achieved due to the antenna form factor limitation. One plausible way to operate a system with large number of CSI-RS antenna ports at low carrier frequency is to distribute the physical antenna ports to different panels / RRHs / TRPs, which can be non-collocated. The multiple sites or panels / RRHs / TRPs can still be connected to a single (common) base unit forming a single antenna system, hence the signal transmitted / received via multiple distributed RRHs / TRPs can still be processed at a centralized location.

[0148] As described herein, for low (FR1), high (FR2 and beyond), or mid (6-15GHz) band, the NW topology / architecture is likely to be more and more distributed in future due to reasons explained herein (e.g. use cases, HW requirements, antenna form factors, mobility etc.). In this disclosure, such a distributed system is referred to as a DMIMO or multiple TRP (mTRP) system (multiple antenna port groups, which can be non-co-located). The transmission in such a system can be coherent joint transmission (CJT), i.e., a layer can be transmitted across / using multiple TRPs, or non-coherent joint transmission (NCJT). Embodiments of the present disclosure recognize that due to distributed nature of operation, the groups of antenna ports (or TRPs) need to be calibrated / synchronized by compensating for the non-idealities such as time / frequency / phase offsets non-ideal backhaul across TRPs, due to HW impairments, different delay profiles, and Doppler profile (in high-speed scenarios) associated with different TRPs.

[0149] In a wireless communication system, MIMO is often identified as an essential feature in order to achieve high system throughput requirements. One of the key components of a MIMO transmission scheme is the accurate CSI acquisition at the eNB (or gNB) (or TRP). For MU-MIMO, in particular, the availability of accurate CSI is necessary in order to guarantee high MU performance. For time division duplexing (TDD) systems, the CSI can be acquired using the SRS transmission relying on the channel reciprocity. For frequency division duplexing (FDD) systems, on the other hand, it can be acquired using the CSI-RS transmission from eNB (or gNB), and CSI acquisition and feedback from UE.

[0150] In 5G or NR systems [REF7, REF8], both low- (aka Type I) and high-resolution (aka Type II) CSI reporting mechanisms are supported. In addition, to reduce Type II CSI reporting, a frequency domain (FD) compression based Type II CSI is also supported, which is based on (a) spatial domain (SD) basis (b) FD basis and (c) coefficients 　 that linearly combine SD and FD bases. For a (full TDD or partial FDD) reciprocity, CSI-RS ports can be beamformed (using SRS measurements, expecting UL-DL channel reciprocity in angular / delay), and the SD basis corresponds to a port selection basis.

[0151] In Rel.18, the FD-compression-based Type II CSI is further enhanced for the use case of CJT across up to 4 TRPs, under the idealistic assumptions such as perfectly time and frequency synchronized mTRPs, phase-coherent antenna ports and ideal backhaul links. In practice, however, these assumptions are not valid, and calibration / synchronization across TRPs is necessary in order to make CJT feasible.

[0152] Massive MIMO base stations or TRPs use an on-board coupling network and calibration circuits, referred to as the on-board calibration for brevity, to measure the gain and phase differences among transceivers in the same radio frequency (RF) unit in order to maintain the reciprocity between DL and UL channels, in the TDD system in particular. For the on-board calibration, one RF chain corresponding to one antenna port serves as a reference to other RF chains for other antenna ports. In the case of the mTRP system, such reference transceiver's signal needs to be shared between distributed RRHs / panels / modules / TRPs, which are physically far apart or non-co-located. Using RF cables to distribute the reference is not preferable as it limits the deployment scenarios. In addition, the use of different local oscillators (LOs) between distributed antenna modules imposes even more challenges in achieving calibration as the phase of LOs could drift. Periodic calibration is needed to compensate for the phase drift as well.

[0153] Issue 1: In one example, the timing offset can be expressed as where is due to timing difference between (distributed, non-co-located) TRPs or / and different propagation delays from different TRPs, which amounts to increased frequency-selectivity of the composite channel. The min freq. granularity (supported in NR) is 2 RBs (for precoding matrix indicator (PMI)) and 4 RBs (CQI), which correspond to a max delay spread 2.8 and 1.4 micro second for SCS = 15 and 30 kHz, respectively. This delay spread decreases further with increasing freq. granularity (due to timing offset). For large delay spread, the required freq. granularity for CJT (across TRPs) will be smaller than 2 RBs.

[0154]

[0155] Issue 2: In one example, the frequency offset can be expressed as where is due to non-ideal (and different) local oscillators or crystal types at different TRPs, which results in frequency differences between TRPs. As shown herein, the min freq. error = 0.05ppm, according to TS 38.104. The phase change due to freq. error can be significant, especially at higher carrier frequencies.

[0156] In general, the combined (time-frequency) T-F offset can be expressed as For CJT feasibility, needs to be calibrated for frequently.

[0157] Issue 3: non-ideal backhaul links between TRPs, especially when the backhaul links are not fiber-optic cables.

[0158] Issue 4: phase-coherency across antenna ports, both intra-TRP (within each TRP) and inter-TRP (across TRPs).

[0159] In this disclosure, the mechanism are procedures are provided for Issue 1 and 2, which are more severe than Issue 3 and 4.

[0160] In one example, a TRP or RRH can be functionally equivalent to (hence can be replaced with) or is interchangeable with one of more of the following: an antenna, or an antenna group (multiple antennae), an antenna port, an antenna port group (multiple ports), a CSI-RS resource, multiple CSI-RS resources, a CSI-RS resource set, multiple CSI-RS resource sets, an antenna panel, multiple antenna panels, a Tx-Rx entity, a (analog) beam, a (analog) beam group, a cell, a cell group.

[0161] This disclosure provides CSI reporting based on calibration-related information (CLI). The calibration-related information such as delay-offset and / or frequency offset values can be reported via a new feature being developed in Rel-19 CJT calibration reporting on PUSCH. This disclosure provides a framework to report CSI for CJT, where the CSI is computed / determined with expecting pre-compensation (at the UE side) utilizing the calibration-related information. The provided aspects as follows:

[0162] - Separate reporting of CSI and CLI, and gNB confirmation to indicate ACK / NACK regarding the CLI reporting.

[0163] - Handling the case of gNB confirming as NACK

[0164] Although the focus of this disclosure is on 3GPP 5G NR communication systems, various embodiments may apply in general to UEs operating with other RATs and / or standards, such as different releases / generations of 3GPP standards (including beyond 5G, 6G, and so on), IEEE standards (such as 802.16 WiMAX and 802.11 Wi-Fi), and so on.

[0165] In the following, for brevity, both FDD and TDD are regarded as the duplex method for both DL and UL signaling.

[0166] Although exemplary descriptions and embodiments to follow expect orthogonal frequency division multiplexing (OFDM) or orthogonal frequency division multiple access (OFDMA), this disclosure can be extended to other OFDM-based transmission waveforms or multiple access schemes such as filtered OFDM (F-OFDM).

[0167] This disclosure covers several components which can be used in conjunction or in combination with one another, or can operate as standalone schemes.

[0168] All the following components and embodiments are applicable for UL transmission with CP-OFDM (cyclic prefix OFDM) waveform as well as DFT-SOFDM (DFT-spread OFDM) and SC-FDMA (single-carrier FDMA) waveforms. Furthermore, the following components and embodiments are applicable for UL transmission when the scheduling unit in time is either one subframe (which can include one or multiple slots) or one slot.

[0169] In the present disclosure, the frequency resolution (reporting granularity) and span (reporting bandwidth) of CSI or calibration coefficient reporting can be defined in terms of frequency “subbands” and “CSI reporting band” (CRB), respectively.

[0170] A subband for CSI or calibration coefficient reporting is defined as a set of contiguous PRBs which represents the smallest frequency unit for CSI or calibration coefficient reporting. The number of PRBs in a subband can be fixed for a given value of DL system bandwidth, configured either semi-statically via higher-layer / RRC signaling, or dynamically via L1 DL control signaling or MAC control element (MAC CE). The number of PRBs in a subband can be included in CSI or calibration coefficient reporting setting.

[0171] “CSI or calibration coefficient reporting band” is defined as a set / collection of subbands, either contiguous or non-contiguous, wherein CSI or calibration coefficient reporting is performed. For example, CSI or calibration coefficient reporting band can include the subbands within the DL system bandwidth. This can also be termed “full-band”. Alternatively, CSI or calibration coefficient reporting band can include only a collection of subbands within the DL system bandwidth. This can also be termed “partial band”.

[0172] The term “CSI or calibration coefficient reporting band” is used only as an example for representing a function. Other terms such as “CSI or calibration coefficient reporting subband set” or “CSI or calibration coefficient reporting bandwidth” can also be used.

[0173] In terms of UE configuration, a UE ( e.g., the UE 116) can be configured with at least one CSI or calibration coefficient reporting band. This configuration can be semi-static (via higher-layer signaling or RRC) or dynamic (via MAC CE or L1 DL control signaling). When configured with multiple (N) CSI or calibration coefficient reporting bands (e.g. via RRC signaling), a UE can report CSI associated withn≤NCSI reporting bands. For instance, >6GHz, large system bandwidth may require multiple CSI or calibration coefficient reporting bands. The value of n can either be configured semi-statically (via higher-layer signaling or RRC) or dynamically (via MAC CE or L1 DL control signaling). Alternatively, the UE can report a recommended value ofnvia an UL channel.

[0174] Therefore, CSI parameter frequency granularity can be defined per CSI reporting band as follows. A CSI parameter is configured with “single” reporting for the CSI reporting band withMnsubbands when one CSI parameter for theMnsubbands within the CSI reporting band. A CSI parameter is configured with “subband” for the CSI reporting band withMnsubbands when one CSI parameter is reported for each of theMnsubbands within the CSI reporting band.

[0175] FIG. 10 illustrates an example antenna port layout 1000 according to embodiments of the present disclosure. For example, antenna port layout 1000 can be implemented by the BS 102 of FIGURE 2. This example is for illustration only and can be used without departing from the scope of the present disclosure.

[0176] In the following,N1andN2are the number of antenna ports with the same polarization in the first and second dimensions, respectively. For 2D antenna port layouts,N1> 1,N2> 1, and for 1D antenna port layoutsN1> 1 andN2= 1 (orN1= 1 andN2> 1). For a single-polarized (or co-polarized) antenna port layout, the total number of antenna ports is And, for a dual-polarized antenna port layout, the total number of antenna ports is An illustration is shown in FIG. 10 where “X” represents two antenna polarizations. In this disclosure, the term “polarization” refers to a group of antenna ports with the same polarization. For example, antenna ports comprise a first antenna polarization, and antenna ports comprise a second antenna polarization, where is a number of CSI-RS antenna ports and is a starting antenna port number (e.g. then antenna ports are 3000, 3001, 3002, ...). Dual-polarized antenna payouts are provided in this disclosure. The embodiments (and examples) in this disclosure however are general and are applicable to single-polarized antenna layouts as well.

[0177] Let be a number of antenna groups (AGs). When there are multiple antenna groups ( ), each group ( ) comprises dual-polarized antenna ports with and ports in two dimensions. This is illustrated in FIG. 10. Note that the antenna port layouts may be the same ( and ) in different antenna groups, or they can be different across antenna groups. For group the number of antenna ports is or (for co-polarized or dual-polarized respectively).

[0178] In one example, an antenna group corresponds to an antenna panel. In one example, an antenna group corresponds to a TRP. In one example, an antenna group corresponds to an RRH. In one example, an antenna group corresponds to CSI-RS antenna ports of a non-zero power (NZP) CSI-RS resource. In one example, an antenna group corresponds to a subset of CSI-RS antenna ports of a NZP CSI-RS resource (comprising multiple antenna groups). In one example, an antenna group corresponds to CSI-RS antenna ports of multiple NZP CSI-RS resources (e.g. comprising a CSI-RS resource set).

[0179] In one example, an antenna group corresponds to a reconfigurable intelligent surface (RIS) in which the antenna group can be (re-)configured more dynamically (e.g. via MAC CE or / and DCI). For example, the number of antenna ports associated with the antenna group can be changed dynamically.

[0180] FIG. 11 illustrates examples of a UE moving on a trajectory 1100 with AGs of the BS co-located and distributed according to embodiments of the present disclosure. For example, trajectory 1100 with AGs of the BS co-located and distributed can be implemented by any of the UEs 111-116 of FIG. 1. This example is for illustration only and can be used without departing from the scope of the present disclosure.

[0181] In one example scenario, multiple AGs can be co-located or distributed, and can serve static (non-mobile) or moving UEs. An illustration of AGs serving a moving UE is shown in FIG. 11. While the UE moves from a location A to another location B, the UE measures the channel, e.g. via NZP CSI-RS resources, (may also measure the interference, e.g. via CSI-IM resources or CSI-RS resources for interference measurement), uses the measurement to determine / report CSI or calibration-related information considering joint transmission from multiple AGs.

[0182] In one example, the antenna architecture of the MIMO system is structured. For example, the antenna structure at each AG is dual-polarized (single or multi-panel as shown in FIG. 10. The antenna structure at each AG can be the same. Or, the antenna structure at an AG can be different from another AG. Likewise, the number of ports at each AG can be the same. Or, the number of ports at one AG can be different from another AG.

[0183] In another example, the antenna architecture of the MIMO system is unstructured. For example, the antenna structure at one AG can be different from another AG.

[0184] A structured antenna architecture is provided in the rest of the disclosure. For simplicity, each AG is equivalent to a panel (cf. FIG. 10), although, an AG can have multiple panels in practice. The disclosure however is not restrictive to a single panel assumption at each AG, and can easily be extended (covers) the case when an AG has multiple antenna panels.

[0185] In one embodiment, an AG constitutes (or corresponds to or is equivalent to) at least one of the following:

[0186] - In one example, an AG corresponds to a TRP.

[0187] - In one example, an AG corresponds to a CSI-RS resource. A UE is configured with non-zero-power (NZP) CSI-RS resources, and a CSI reporting is configured to be across multiple CSI-RS resources. This is similar to Class B, K > 1 configuration in Rel. 14 LTE. The NZP CSI-RS resources can belong to a CSI-RS resource set or multiple CSI-RS resource sets (e.g. resource sets each comprising one CSI-RS resource). The details are as explained herein in this disclosure.

[0188] - In one example, an AG corresponds to a CSI-RS resource group, where a group comprises one or multiple NZP CSI-RS resources. A UE is configured with non-zero-power (NZP) CSI-RS resources, and a CSI reporting is configured to be across multiple CSI-RS resources from resource groups. This is similar to Class B, K > 1 configuration in Rel. 14 LTE. The NZP CSI-RS resources can belong to a CSI-RS resource set or multiple CSI-RS resource sets (e.g. resource sets each comprising one CSI-RS resource). The details are as explained herein in this disclosure. In particular, the CSI-RS resources can be partitioned into resource groups. The information about the resource grouping can be provided together with the CSI-RS resource setting / configuration, or with the CSI reporting setting / configuration, or with the CSI-RS resource configuration.

[0189] - In one example, an AG corresponds to a subset (or a group) of CSI-RS ports. A UE is configured with at least one NZP CSI-RS resource comprising (or associated with) CSI-RS ports that can be grouped (or partitioned) multiple subsets / groups / parts of antenna ports, each corresponding to (or constituting) an AG. The information about the subsets of ports or grouping of ports can be provided together with the CSI-RS resource setting / configuration, or with the CSI reporting setting / configuration, or with the CSI-RS resource configuration.

[0190] - In one example, an AG corresponds to one or more examples described herein depending on a configuration. For example, this configuration can be explicit via a parameter (e.g. an RRC parameter). Or, it can be implicit.

[0191] -- In one example, when implicit, it could be based on the value of For example, when CSI-RS resources, an AG corresponds to one or more examples described herein, and when CSI-RS resource, an AG corresponds to one or more examples described herein.

[0192] -- In another example, the configuration could be based on the configured codebook. For example, an AG corresponds to a CSI-RS resource (according to one or more examples described herein) or resource group (according to one or more examples described herein) when the codebook corresponds to a decoupled codebook (modular or separate codebook for each AG), and an AG corresponds to a subset (or a group) of CSI-RS ports (according to one or more examples described herein) when codebook corresponds to a coupled (joint or coherent) codebook (one joint codebook across AGs).

[0193] In one example, when AG maps (or corresponds to) a CSI-RS resource or resource group (according to one or more examples described herein), and a UE can select a subset of AGs (resources or resource groups) and report the CSI or calibration-related information for the selected AGs (resources or resource groups), the selected AGs can be reported via an indicator (e.g. via UCI part 1 of a two-part UCI). For example, the indicator can be a channel quality indicator (CQI) report interval (CRI) or a PMI (component) or a new indicator (e.g. a bitmap).

[0194] In one example, when AG maps (or corresponds to) a CSI-RS port group (according to one or more examples described herein), and a UE can select a subset of AGs (port groups) and report the CSI or calibration-related information for the selected AGs (port groups), the selected AGs can be reported via an indicator (e.g. via UCI part 1 of a two-part UCI). For example, the indicator can be a CRI or a PMI (component) or a new indicator (e.g. a bitmap).

[0195] In one example, CSI-RS herein in this disclosure comprises at least one or a combination of the following: CSI-RS for tracking (TRS), CSI-RS for CSI, CSI-RS for beam management (BM), CSI-RS for mobility or NZP CSI-RS resource for IMR (interference measurement) or a new type / usage of CSI-RS, namely, CSI-RS for calibration.

[0196] In one embodiment, a UE is configured with a calibration mechanism, wherein the UE is configured to perform one or more UL RS transmission(s), or / and to perform one or more DL RS reception(s) / measurement(s), and / or to report calibration-related information (e.g., for calibration coefficient for each TRP).

[0197] This configuration can be performed via higher-layer (RRC) signaling.

[0198] - In one example, this configuration corresponds to a CSI resource setting configured via a higher layer IE CSI-ResourceConfig.

[0199] - In one example, this configuration corresponds to a CSI resource set configured via a higher layer IE NZP-CSIRSResourceSet.

[0200] - In one example, this configuration corresponds to a NZP CSI resource configured via a higher layer IE NZP-CSIRSResource.

[0201] - In one example, this configuration corresponds to a CSI report setting configured via a higher layer IE CSI-ReportConfig.

[0202] In one example, the DL RS(s) can be one of or multiple of CSI-RS for CSI reporting, CSI-RS for tracking (TRS), CSI-RS for beam reporting, DL DMRS, or synchronization signal / physical broadcast channel (SSB / PBCH) or a new type / usage of CSI-RS, namely, CSI-RS for calibration. In one example, DL RS can be a dedicated or new DL RS (for calibration purpose).

[0203] In one example, the UL RS(s) can be one of or multiple of SRS with usage=CB, SRS with usage=non-CB, SRS with usage=beamManagement, SRS with usage=AntennaSwitching, or UL DMRS. In one example, UL RS can be a dedicated or new UL RS (for calibration purpose).

[0204] In one example, the DL RS(s) can be aperiodic (AP) only.

[0205] In one example, the DL RS(s) can be AP or semi-persistent (SP).

[0206] In one example, the DL RS(s) can be AP or periodic (P).

[0207] In one example, the DL RS(s) can be SP or P.

[0208] In one example, the DL RS(s) can be AP or SP or P.

[0209] In one example, the UL RS(s) can be aperiodic (AP) only.

[0210] In one example, the UL RS(s) can be AP or semi-persistent (SP).

[0211] In one example, the UL RS(s) can be AP or periodic (P).

[0212] In one example, the UL RS(s) can be SP or P.

[0213] In one example, the UL RS(s) can be AP or SP or P.

[0214] In one example, the reporting can only be AP. In this case, the reporting can be triggered via a DCI (e.g. a CSI request field in UL-DCI).

[0215] In one example, the reporting can either be AP or SP. For AP, the reporting can be triggered via a DCI (e.g. a CSI request field in UL-DCI), and for SP, it can be triggered via MAC CE or DCI.

[0216] In one example, the reporting can only be UE-initiated (or UE-triggered). In this case, the reporting can be triggered via UL MAC CE (e.g. MAC CE for power headroom report (PHR) reporting) or via a pre-notification message sent by the UE, where this message can be sent via SR (scheduling request) or via UCI (a pre-configured PUCCH or a PUSCH).

[0217] The term 'precoder' in this disclosure can be replaced with a spatial information (or transmission configuration indication (TCI) state, orspatialRelationInfo) or source RS or spatial filter, beamformer, beamforming vectors / matrices, precoding vector / matrices, or any other functionally equivalent quantity, that can be used for DL / UL RS reception / transmission.

[0218] In one embodiment, a UE is configured with a measurement and a report (e.g. CSI or calibration report) including calibration-related information (CLI) to enable / facilitate calibration / synchronization across TRPs or AGs or CSI-RS resources. In one example, the measurement can be configured via higher layer IE CSI-ResourceConfig indicating sets of NZP CSI-RS resources. In one example, the measurement can be configured via higher layer IENZP-CSIRS-ResourceSetindicating a set of NZP CSI-RS resources. In one example, the measurement can be configured via higher layer IEMeasObj. In one example, the report can be configured via higher layer parameter CSI-ReportConfig withreportTypeset to a new value, e.g. 'calibration' or 'cjt-calibration'.

[0219] Let be the measurement associated with -th TRP (or CSI-RS resource or DL RS), where and be the composite / aggregated channel at a T-F unit and be the offsets associated with TRPs.

[0220] As described in this disclosure, one of the TRPs can be a reference, whose offset can be fixed, e.g. to zero. Without loss generality, the reference TRP (resource) corresponds to (the 1stTRP) for which i.e.,

[0221] In one example, values of based on the measurement, can be used to determine the report.

[0222] In one example, a low-pass or a window-based approach can be used for the report. In one example, the window corresponds to value of that are around the reference. For instance, and / or where ( corresponds to the window length or max value of that can be used for the report, ( can be fixed, or configured, or reported by the UE.

[0223] In one example, the unit of CLI reporting is at least one of the following examples:

[0224] - In one example, for time offset, the unit can be based on the CP length, or the symbol duration, or the slot duration. For example, values within a window / interval, [0, x], x=CP length, min measurement interval. In one example, sec or sec. In one example, sec or sec where

[0225] - In one example, for time offset, the unit can be based on a fractional factor (between 0 and 1) of a TD unit. For example, values within a window / interval, [0, x], x=TD unit length.

[0226] - In one example, For frequency error (in ppm), the unit can be based on the window / interval, [0, x] or x= freq. error value specified in 38.104 (from RAN4). For example, values within a window / interval, [0, x] or x=FD unit length. In one example, ppm (parts per million).

[0227] - In one example, for time offset, the unit can be based on the normalized CP length, or the symbol duration, or the slot duration. For example, values within a window / interval, [0, 1], 1 corresponds to CP length, min measurement interval. In one example, the CP length sec or sec. In one example, the CP length sec or sec where

[0228] - In one example, for time offset, the unit can be based on a normalized fractional factor (between 0 and 1) of a TD unit. For example, values within a window / interval, [0, 1], 1 corresponds to TD unit length.

[0229] - In one example, for frequency error (in ppm), the unit can be based on the normalized window / interval, [0, 1] or 1 corresponds to freq. error value, e.g., specified in 38.104 (from RAN4). For example, values within a window / interval, [0, 1] or x=FD unit length. In one example, ppm (parts per million).

[0230] Note that CP length can be also expressed as CP= where is subcarrier spacing, e.g., (or etc) kHz. Or CP length can also be expressed as normal CP length or extended CP length, i.e., normal CP length = and extended CP length = In this disclosure, CP length can be replaced by or or an approximated CP length or an extended CP length

[0231] In one example, the CLI corresponds to at least one indicator indicating a measurement RS. For instance, the indicator can be CRI or SSBRI or other DL RS indicator when the measurement RS is NZP CSI-RS or SSB / PBCH block, or another DL RS. The at least one indicator can provide an implicit information about the offsets.

[0232] In one example, the CLI corresponds to the set of values of or pairs or indicator(s) indicating (quantized) values of At least one of the following examples of alphabet set is used for quantizing

[0233] - In one example, the alphabet set corresponds to a uniform quantizer in linear scale.

[0234] -- In one example, includes values, uniformly / equally spaced / separated in where is the number of bits for quantization and is the max value. In one example, the values include 0 or / and

[0235] --- In one example, for time, where is the CP length, and is a scaling. In one example,

[0236] --- In one example, for time, where is the slot duration, and is a scaling. In one example,

[0237] --- In one example, for frequency, where is the min requirement on the frequency error, e.g. in parts per million (ppm).

[0238] -- In one example, includes values, uniformly / equally spaced / separated in where is the number of bits for quantization, is the min value, and is the max value. In one example, the values include or / and

[0239] -- In one example, includes values, uniformly / equally spaced / separated in

[0240] - In one example, the alphabet set corresponds to a uniform quantizer in logarithmic scale.

[0241] - In one example, the alphabet set corresponds to a non-uniform (e.g. exponential) quantizer

[0242] -- In one example, includes Rel.15 3-bit amplitude alphabet set (Table A).

[0243] -- In one example, includes Rel.16 3-bit or 4-bit amplitude alphabet set (Table B, Table C).

[0244] -- In one example, includes Rel.18 amplitude alphabet set for time-domain channel property (TDCP) report (Table D).

[0245]

[0246]

[0247]

[0248]

[0249] In one example, for delay reporting, the alphabet set includes at least one value corresponding to a value larger than the CP length.

[0250] - In one example, the alphabet set includes values in where and here is the CP length, as described herein.

[0251] - In one example, the alphabet set includes values in (normalized by the CP length) where and here corresponds to the CP length, as described herein.

[0252] - In one example, the alphabet set includes values in where and here is the CP length, as described herein.

[0253] - In one example, the alphabet set includes values in (normalized by the CP length) where and here corresponds to the CP length, as described herein.

[0254] In one example, for delay reporting, the alphabet set includes values corresponding to values larger than the CP length.

[0255] - In one example, the alphabet set includes values in where and here is the CP length, as described herein.

[0256] - In one example, the alphabet set includes values in (normalized by the CP length) where and here corresponds to the CP length, as described herein.

[0257] - In one example, the alphabet set includes values in where and here is the CP length, as described herein.

[0258] - In one example, the alphabet set includes values in (normalized by the CP length) where and here corresponds to the CP length, as described herein.

[0259] In one example, for delay reporting, the alphabet set includes at least one code point indicating that delay value is larger than the CP length or corresponds to a value larger than the CP length.

[0260] - In one example, the alphabet set includes values in where is the CP length, as described herein. The code point indicates In one example, corresponds to NULL, Invalid, or a fixed value larger than x, or out-of-range.

[0261] - In one example, the alphabet set includes values in (normalized by the CP length) where corresponds to the CP length, as described herein. The code point indicates In one example, corresponds to NULL, Invalid, or a fixed value larger than x or out-of-range.

[0262] - In one example, the alphabet set includes values in where is the CP length, as described herein. The code point indicates In one example, corresponds to NULL, Invalid, or a fixed value larger than x or out-of-range.

[0263] - In one example, the alphabet set includes values in (normalized by the CP length) where corresponds to the CP length, as described herein. The code point indicates In one example, corresponds to NULL, Invalid, or a fixed value larger than x or out-of-range.

[0264] In one example, for delay reporting, the alphabet set includes at least one code point indicating that delay value is larger than the CP length or corresponds to a value larger than the CP length, or / and includes values corresponding to values larger than the CP length.

[0265] - In one example, the alphabet set includes values in where is the CP length and as described herein. The code point indicates In one example, corresponds to NULL, Invalid, or a fixed value larger than x or out-of-range.

[0266] - In one example, the alphabet set includes values in (normalized by the CP length) where corresponds to the CP length and as described herein. The code point indicates In one example, corresponds to NULL, Invalid, or a fixed value larger than x or out-of-range.

[0267] - In one example, the alphabet set includes values in where is the CP length and as described herein. The code point indicates In one example, corresponds to NULL, Invalid, or a fixed value larger than x or out-of-range.

[0268] - In one example, the alphabet set includes values in (normalized by the CP length) where corresponds to the CP length and as described herein. The code point indicates In one example, corresponds to NULL, Invalid, or a fixed value larger than x or out-of-range.

[0269] In one example, is fixed (e.g. 1). In one example, is configured (e.g. RRC). In one example, is reported by the UE.

[0270] In one example, and is fixed (e.g. and is an integer), is configured (e.g. RRC), is reported by the UE.

[0271] In one example, and is fixed (e.g. and is an integer), is configured (e.g. RRC), is reported by the UE.

[0272] In one example, for frequency error reporting, the alphabet set includes at least one value corresponding to a value larger than the frequency error ( ).

[0273] - In one example, the alphabet set includes values in or where and here is the frequency error, as described herein.

[0274] - In one example, the alphabet set includes values in or (normalized by the the frequency error) where and here corresponds to the frequency error, as described herein.

[0275] - In one example, the alphabet set includes values in where and here is the frequency error, as described herein.

[0276] - In one example, the alphabet set includes values in (normalized by the the frequency error) where and here corresponds to the frequency error, as described herein.

[0277] In one example, for frequency error reporting, the alphabet set includes values corresponding to values larger than the frequency error.

[0278] - In one example, the alphabet set includes values in where and here is the CP length, as described herein.

[0279] - In one example, the alphabet set includes values in (normalized by the Frequency error) where and here corresponds to the Frequency error, as described herein.

[0280] - In one example, the alphabet set includes values in where and here is the Frequency error, as described herein.

[0281] - In one example, the alphabet set includes values in (normalized by the Frequency error) where and here corresponds to the Frequency error, as described herein.

[0282] In one example, for frequency error reporting, the alphabet set includes at least one code point indicating that delay value is larger than the Frequency error or corresponds to a value larger than the Frequency error.

[0283] - In one example, the alphabet set includes values in where is the Frequency error, as described herein. The code point indicates In one example, corresponds to NULL, Invalid, or a fixed value larger than x.

[0284] - In one example, the alphabet set includes values in (normalized by the Frequency error) where corresponds to the Frequency error, as described herein. The code point indicates In one example, corresponds to NULL, Invalid, or a fixed value larger than x.

[0285] - In one example, the alphabet set includes values in where is the Frequency error, as described herein. The code point indicates In one example, corresponds to NULL, Invalid, or a fixed value larger than x.

[0286] - In one example, the alphabet set includes values in (normalized by the Frequency error) where corresponds to the Frequency error, as described herein. The code point indicates In one example, corresponds to NULL, Invalid, or a fixed value larger than x.

[0287] In one example, for frequency error reporting, the alphabet set includes at least one code point indicating that delay value is larger than the Frequency error or corresponds to a value larger than the Frequency error, or / and includes values corresponding to values larger than the Frequency error.

[0288] - In one example, the alphabet set includes values in where is the Frequency error and as described herein. The code point indicates In one example, corresponds to NULL, Invalid, or a fixed value larger than x.

[0289] - In one example, the alphabet set includes values in (normalized by the Frequency error) where corresponds to the Frequency error and as described herein. The code point indicates In one example, corresponds to NULL, Invalid, or a fixed value larger than x.

[0290] - In one example, the alphabet set includes values in where is the Frequency error and as described herein. The code point indicates In one example, corresponds to NULL, Invalid, or a fixed value larger than x.

[0291] - In one example, the alphabet set includes values in (normalized by the Frequency error) where corresponds to the Frequency error and as described herein. The code point indicates In one example, corresponds to NULL, Invalid, or a fixed value larger than x.

[0292] In one example, is fixed (e.g. 1). In one example, is configured (e.g. RRC). In one example, is reported by the UE.

[0293] In one example, and is fixed (e.g. and is an integer), is configured (e.g. RRC), is reported by the UE.

[0294] In one example, and is fixed (e.g. and is an integer), is configured (e.g. RRC), is reported by the UE.

[0295] In one example, the CLI corresponds to the set of values of phases associated with (or due to) or indicator(s) indicating (quantized) values of In one example, At least one of the following examples of the alphabet set is used for quantizing In one example, the alphabet set corresponds bit alphabet set.

[0296] - In one example, The 2 values correspond to BPSK

[0297] - In one example, The 4 values correspond to QPSK

[0298] - In one example, The 8 values correspond to 8PSK

[0299] - In one example, The 16 values correspond to 16PSK

[0300] - In one example, is configured via higher layer signaling, e.g. from {3,4}.

[0301] In one example, the UE ( e.g., the UE 116) also reports (indices indicating) the values of associated with the reported In one example, the UE is configured with (indices indicating) the values of

[0302] In one example, the CLI can also include amplitude in addition to phase, i.e.,

[0303] At least one of the following examples is used / configured regarding the reporting / calculation.

[0304] In one example, the reporting is absolute, i.e., each of values is determined / reported independently from other values.

[0305] In one example, the reporting is differential (relative) w.r.t. a base or reference. In one example, the based or reference is the 1stTRP (resource). That is, the offset value corresponding to is reported / determined w.r.t. to the same corresponding to In one example, the reference can be fixed (e.g. 0), or configured (e.g. via higher layer) or reported by the UE (as part of the CSI report, either via part 1 or part 2 of a two-part UCI). In one example, the normalized value of the reference can also be reported by the UE.

[0306] - In one example, the differential / relative offset value is determined as The UE reports correlation for and for

[0307] - In one example, the differential / relative offset is determined as The UE reports offset for and for

[0308] - In one example, or

[0309] - In one example, or

[0310] In one example, the report is a standalone / separate report (similar to Rel.18 time-domain channel property, TDCP), and doesn't include any other parameters. The report can be reported via a layer 1 (physical) UL channel such as PUCCH or / and PUSCH. In this case, the report can be multiplexed with other UCI parameters such as HARQ-ACK parameters. Alternatively, the report can be reported via a layer 2 (MAC) UL channel such as UL MAC CE. In this case, the report can be multiplexed with other MAC parameters such as PHR parameters.

[0311] In one example, the report is a non-standalone / joint report and can include other parameters such as CSI parameters (e.g. rank indicator (RI), precoding matrix indicator (PMI), channel quality indicator (CQI), CQI report interval (CRI), layer index (LI)) or / and beam-related parameters (e.g. L1-reference signal received power (RSRP),L1-signal-to-interference-plus-noise ratio (SINR), CRI, SSB resource indicator (SSBRI)). In this case, the (calibration) report is a component (or part of) out of multiple components (or parts of) the CSI / beam report.

[0312] In one example, the CLI can be included as a component of (part of an alphabet set), e.g. Rel.18 Type II CJT alphabet set, and the corresponding configuration can be codebookMode = mode 3 (in addition to mode 1 and mode 2 in Rel.18).

[0313] In one example, a metric to obtain / derive / obtain the CLI is based on auto-( / cross-) correlation or / and power spectrum or power spectrum density of the measurement.

[0314] In one example, the measurement and reporting for T-F offset is decoupled / separate, i.e., one of the two separate mechanisms can be configured / used.

[0315] - For time offset ( ), the measurement corresponds to multiple (a burst of) time occasions, where two consecutive time occasions can be separated by symbols or slots.

[0316] - For frequency offset ( ), the measurement corresponds to multiple (a burst of) frequency occasions, where two consecutive frequency occasions can be separated by subcarriers or PRBs or SBs.

[0317] In one example, the measurement and reporting for T-F offset is coupled / joint, i.e., one joint mechanism is used / configured for a 2D measurement and reporting for

[0318] At least one of the following examples is used / configured regarding the frequency domain granularity of the reporting / calculation of offset value(s).

[0319] - In one example, the reporting / calculation of offset value(s) is in a wideband (WB) manner, i.e., offset values are reported common for the entire CSI reporting band.

[0320] - In one example, the reporting / calculation of offset value(s) is in a subband (SB) manner, i.e., offset values are reported for each SB in the CSI reporting band. In addition, a reference (WB) offset can also be reported such that Sub-band offset level (s) = sub-band offset index (s) - wideband offset index.

[0321] Likewise, at least one of the following examples is used / configured regarding the time domain granularity of the reporting / calculation of offset value(s).

[0322] - In one example, the reporting / calculation of offset value(s) is in a wide-time (WT) manner, i.e., offset values are reported common for the entire time window or duration (in which the report is expected to be valid).

[0323] - In one example, the reporting / calculation of offset value(s) is in a sub-time (ST) manner, i.e., offset values are reported for each ST in the time duration (in which the report is expected to be valid). In addition, a reference (WT) offset can also be reported such that ST offset level (s) = ST offset index (s) - WT offset index.

[0324] In one example, the report includes one value for each TRP ( values when including the reference or values when excluding the reference). For time / delay offsets ( delay values sorted in increasing order)

[0325] - In one example, the one value corresponds to the 1stdelay

[0326] - In one example, the one value corresponds to the last delay

[0327] - In one example, the one value corresponds to the max of

[0328] - In one example, the one value corresponds to the Delay spread

[0329] Likewise, for frequency offsets ( values sorted in increasing order)

[0330] - In one example, the one value corresponds to the 1stfrequency

[0331] - In one example, the one value corresponds to the last frequency

[0332] - In one example, the one value corresponds to the max of

[0333] - In one example, the one value corresponds to the Frequency spread

[0334] In one example, the report includes two values for each TRP. For time / delay offsets ( delay values sorted in increasing order),

[0335] - In one example, the two values can correspond to the 1stand the last values and

[0336] - In one example, the two values can correspond to the max and the min of

[0337] - In one example, the two values can correspond to the two largest values of

[0338] Likewise, For frequency offsets ( values sorted in increasing order),

[0339] - In one example, the two values can correspond to the 1stand the last values and

[0340] - In one example, the two values can correspond to the max and the min of

[0341] - In one example, the two values can correspond to the two largest values of

[0342] In one example, the report includes two values for each TRP.

[0343] In one example, the report includes two values for TRPs (excluding the reference TRP).

[0344] In one example, the report includes one value for the reference TRP, and two values for remaining TRPs, i.e., the two values for the reference are 0 and

[0345] In one example, the report further includes a recommendation about coherency (CJT or NCJT) across TRPs. In one example, it can be implicit via one value, or explicit via an indicator (e.g. 1-bit), or via an -bit or -bit bitmap indicator, where when the bitmap is '0' or '1' then it indicates NCJT and when at least two '1's or '0's then it indicates CJT.

[0346] In one embodiment, a CLI reporting (according to one or more embodiments described herein) is according to at least one of the following examples.

[0347] In one example, the CLI reporting includes one CRI (or DL RS indicator) to indicate a reference CSI-RS resource.

[0348] In one example, the CSI reporting does not include any CRI information.

[0349] - In one example, a reference CSI-RS resource can be configured by the NW, via higher-layer signaling (i.e., RRC).

[0350] - In one example, a reference CSI-RS resource is fixed, e.g., the lowest (or highest) index of CSI-RS resources.

[0351] - In one example, a reference CSI-RS resource is not indicated / reported / specified / used.

[0352] In one example, the CLI reporting includes a -bit bitmap indicator (or -bit bitmap indicator) to indicate one or multiple CSI-RS resources.

[0353] In one embodiment, for (inter-TRP-)delay reporting (of a CLI reporting described in an example of one or more embodiments herein), an alphabet set for quantizing delay values is according to at least one of the following examples.

[0354] In one example, the alphabet set includes 0 value or a codepoint mapping to 0 value.

[0355] In one example, the alphabet set does not include 0 value or a codepoint mapping to 0 value.

[0356] In one example, the alphabet set includes values or codepoints for a range of in unit of CP length, where can be fixed, e.g., 1, or can be configured by the NW via higher-layer signaling (i.e., RRC), or can be determined by the UE, and where is a maximum value of the range (e.g., ) and it can be fixed, configured by the NW, or determined by the UE.

[0357] - In one example, is fixed. In another example, can be configured by the NW. In another example, can be determined by the UE and reported as a part of the reporting.

[0358] - In one example, the values (or codepoints) are values in in unit of CP length.

[0359] - In one example, the values (or codepoints) are values in in unit of CP length.

[0360] - In one example, the values (or codepoints) includes 0 value.

[0361] - In one example, the values (or codepoints) includes a reserved value, e.g., NULL, out-of-range, etc.

[0362] In one example, more specifically, the alphabet set includes codepoints where codepoints correspond to intervals in in unit of CP length (where ) and 1 codepoint corresponds to a reserved value (e.g., out-of-range, invalid state, NULL, etc.). In one example, each codepoint of the codepoints corresponds to an interval (or or ), where is uniformly spaced between 0 and for The reserved value (e.g., out-of-range) can represent

[0363] In one example, each codepoint of the (or M-2) codepoints corresponds to an interval (or or ), where is uniformly spaced between 0 and for The reserved value (e.g., out-of-range) can represent

[0364] In one example, the alphabet set includes values or codepoints for a range of in (absolute) time unit, where can be fixed, e.g., , or can be configured by the NW via higher-layer signaling (i.e., RRC), or can be determined by the UE, and where is a maximum value of the range (e.g., ), and it can be fixed, configured by the NW, or determined by the UE.

[0365] - In one example, is fixed. In another example, can be configured by the NW. In another example, can be determined by the UE and reported as a part of the reporting.

[0366] - In one example, the values (or codepoints) are values in in (absolute) time unit.

[0367] - In one example, the values (or codepoints) are values in in (absolute) time unit

[0368] - In one example, the values (or codepoints) includes 0 value.

[0369] - In one example, the values (or codepoints) includes a reserved value, e.g., NULL, out-of-range, etc.

[0370] In one example, more specifically, the alphabet set includes codepoints where codepoints correspond to intervals in in (absolute) time unit (where ) and 1 codepoint corresponds to a reserved value (e.g., out-of-range, invalid state, NULL, etc). In one example, each codepoint of the codepoints corresponds to an interval (or or ), where is uniformly spaced between 0 and for The reserved value (e.g., out-of-range) can represent (or ).

[0371] In one example, each codepoint of the (or M-2) codepoints corresponds to an interval (or or ), where is uniformly spaced between 0 and for The reserved value (e.g., out-of-range) can represent

[0372] In one embodiment, for delay reporting (of a CLI reporting according to one or more embodiments described herein), one or multiple delay values for each of (or ) CSI-RS resource or each of (or ) CSI-RS resources are reported as a part of CLI reporting.

[0373] In one embodiment, one delay value for CSI-RS resource is quantized using at least one of the schemes described in one or more embodiments herein.

[0374] - In one example, one delay value for each of (or ) CSI-RS resources is quantized and indicated by a (separate) per-TRP (i.e., per-CSI-RS resource) indicator.

[0375] - In one example, one delay value for each of (or ) CSI-RS resources is quantized and indicated by a (separate) per-TRP (i.e., per-CSI-RS resource) indicator.

[0376] - In one example, one delay value for each of (or ) CSI-RS resources is quantized and the delay values are indicated by a joint indicator.

[0377] - In one example, one delay value for each of (or ) CSI-RS resources is quantized and the delay values are indicated by a joint indicator.

[0378] In one embodiment, each of two delay values (e.g., first delay tap and last delay tap) for CSI-RS resource is quantized using at least one of the schemes described in one or more embodiments herein.

[0379] - In one example, each of two delay values for each of (or ) CSI-RS resources is quantized and indicated via a (separate) per-TRP (i.e., per-CSI-RS resource) indicator.

[0380] - In one example, each of two delay values for each of (or ) CSI-RS resources is quantized and indicated via a (separate) per-TRP (i.e., per-CSI-RS resource) indicator.

[0381] - In one example, each of two delay values for each of (or ) CSI-RS resources is quantized and the delay values are indicated via a joint indicator.

[0382] - In one example, each of two delay values for each of (or ) CSI-RS resources is quantized and the delay values are indicated via a joint indicator.

[0383] In one example, for the two delay values, and (where ), for CSI-RS resource alphabet sets and for the two delay values are the same, i.e., and are quantized using a same alphabet set, where the alphabet set is one of the examples described in one or more embodiments herein.

[0384] In one example, for the two delay values, and (where ), for CSI-RS resource alphabet sets and for the two delay values can be different, i.e., and are quantized using different alphabet sets and respectively, where each of the alphabet sets is one of the examples described in one or more embodiments herein.

[0385] In one example, the number of bits for alphabet sets and can be the same, but the alphabet sets and can be different.

[0386] In one example, the number of bits for alphabet sets and can be different, where and are the numbers of bits for alphabet sets and respectively, and

[0387] - In one example, and where is quantized / indicated using alphabet set with bits and is indicated by an 1-bit indicator, whether (which can correspond to delay spread) is exceeding CP length or not, or exceeding a threshold value or not, or out-of-range or not, or ON or OFF, etc.

[0388] - In one example, and where is quantized / indicated using alphabet set with bits and is indicated / quantized using alphabet set with 1-bit, e.g., having and values.

[0389] - In one example, and where is quantized / indicated using alphabet set with bits and is indicated / quantized using alphabet set with bits.

[0390] In one example, the number of bits for alphabet sets and can be different, where and are the numbers of bits for alphabet sets and respectively, and

[0391] - In one example, and where is quantized / indicated using alphabet set with bits and is indicated by an 1-bit indicator, whether (which can correspond to delay spread) is exceeding CP length or not, or exceeding a threshold value or not, or out-of-range or not, or ON or OFF, etc.

[0392] - In one example, and where is quantized / indicated using alphabet set with bits and is indicated / quantized using alphabet set with 1-bit, e.g., having and values.

[0393] - In one example, and where is quantized / indicated using alphabet set with bits and is indicated / quantized using alphabet set with bits.

[0394] In examples herein for the two delay values, and can be referring to at least one of the following examples.

[0395] - In one example, corresponds to a first delay tap / offset and corresponds to a last delay tap / offset.

[0396] - In one example, corresponds to a first delay tap / offset and corresponds to differential / relative delay value to the first delay tap. In this case, a last delay tap / offset can be expressed as

[0397] - In one example, corresponds to a first delay tap / offset and corresponds to delay spread. In this case, a last delay tap / offset can be expressed as

[0398] - In one example, corresponds to a last delay tap / offset and corresponds to delay spread. In this case, a first delay tap / offset can be expressed as

[0399] - In one example, and are represented in the unit of CP length (i.e., normalized by CP length).

[0400] - In one example, and are represented in absolute time unit (without normalization).

[0401] - In one example, and are represented in the unit of OFDM-symbol / slot time unit (normalized by OFDM symbol / slot duration).

[0402] In one embodiment, each of delay values for CSI-RS resource is quantized using at least one of the schemes described in one or more embodiments herein.

[0403] - In one example, each of delay values for each of (or ) CSI-RS resources is quantized and indicated via a (separate) per-TRP (i.e., per-CSI-RS resource) indicator.

[0404] - In one example, each of delay values for each of (or ) CSI-RS resources is quantized and indicated via a (separate) per-TRP (i.e., per-CSI-RS resource) indicator.

[0405] - In one example, each of delay values for each of (or ) CSI-RS resources is quantized and the delay values are indicated via a joint indicator.

[0406] - In one example, each of delay values for each of (or ) CSI-RS resources is quantized and the delay values are indicated via a joint indicator.

[0407] In one example, for the delay values, (where ), for CSI-RS resource alphabet sets for the delay values are the same, i.e., are quantized using a same alphabet set, where the alphabet set is according to one or more embodiments described herein.

[0408] In one example, for the delay values, (where ), for CSI-RS resource alphabet sets for the delay values can be different, i.e., are quantized using different alphabet sets respectively, where each of the alphabet sets is according to one or more embodiments described herein.

[0409] In one example, the number of bits for alphabet sets can be the same, but the alphabet sets can be different.

[0410] In one example, the number of bits for alphabet sets can be different, where are the numbers of bits for alphabet sets respectively.

[0411] In embodiment, the number of bits for alphabet set as described in this disclosure, can be according to at least one of the following examples.

[0412] In one example, (or ) is CSI-RS-resource-common, i.e., a same bit is used across configured CSI-RS resources.

[0413] In one example, (or ) is CSI-RS-resource-specific, i.e., a different / independent bit is used across for each configured CSI-RS resourcer.

[0414] In one example, depends on the number of CSI-RS resources, i.e., (or N). For example, with a scaling value of

[0415] In one example, is fixed or configured by NW, or determined by UE and reported as a part of reporting.

[0416] In one embodiment, a UE can be configured with a range value of and / or a number of quantization states (or a number of bits for quantization states (where )) for CJT delay reporting (or frequency reporting, or phase offset reporting or other joint reporting). Here, the CJT delay reporting can be a delay reporting scheme designed based on an example according to one or more embodiments described herein. In one example, andM(or B) can be designed at least one of the following examples.

[0417] In one example, can be configurable by NW via RRC signaling (or MAC-CE or DCI).

[0418] In one example, (orB) can be configurable by NW via RRC signaling (or MAC-CE or DCI).

[0419] In one example, and (orB)can be separately indicated / configured with separate parameters.

[0420] In one example, and (orB)can be jointly indicated / configured with separate parameters.

[0421] In one example, the number of supported values of is In one example, In one example, In one example, In one example, In one example,

[0422] In one example, the number of supported values of (orB) is In one example, In one example, In one example, In one example,

[0423] In one example, the number of supported values of ) or ) is In one example, In one example, In one example, In one example,

[0424] In one example, one of the configurable values of corresponds to CP length.

[0425] In one example, one of the configurable values of corresponds to a value smaller than CP length. In one example, corresponds to where c<1 e.g., c=0.5 or 0.3 or 1 / 3.

[0426] In one example, one of the configurable values of corresponds to a value larger than CP length. In one example, corresponds to where c>1 e.g., c=1.5 or 1.8 or 2.

[0427] In one example, one of the configurable values of (or ) corresponds to 32 (i.e., B=5bits).

[0428] In one example, one of the configurable values of (or ) corresponds to a value smaller than 32. In one example, corresponds to 16 or 8 or 4 or 2.

[0429] In one example, one of the configurable values of (or ) corresponds to a value larger than 32. In one example, corresponds to 64 or 128 or 256.

[0430] In one example, one of the configurable values of (or ) corresponds to (CP length, 32).

[0431] In one example, one of the configurable values of (or ) corresponds to (CP length, X), where X corresponds to a value smaller than 32.

[0432] In one example, one of the configurable values of (or ) corresponds to (CP length, X), where X corresponds to a value larger than 32.

[0433] In one example, one of the configurable values of (or ) corresponds to (c CP length, 16), where c<1, e.g., c=0.5 or 0.3 or 1 / 3.

[0434] In one example, one of the configurable values of (or ) corresponds to (c CP length, X), where c<1, e.g., c=0.5 or 0.3 or 1 / 3, and X corresponds to a value larger than 16.

[0435] In one example, one of the configurable values of (or ) corresponds to (c CP length, X), where c<1, e.g., c=0.5 or 0.3 or 1 / 3, and X corresponds to a value smaller than 16.

[0436] In one example, one of the configurable values of (or ) corresponds to (c CP length, 32), where c>1, e.g., c=1.5 or 1.8 or 2.

[0437] In one example, one of the configurable values of (or ) corresponds to (c CP length, X), where c>1, e.g., c=1.5 or 1.8 or 2, and X corresponds to a value larger than 32.

[0438] In one example, one of the configurable values of (or ) corresponds to (c CP length, X), where c>1, e.g., c=1.5 or 1.8 or 2, and X corresponds to a value smaller than 32.

[0439] In one example, CP length described in this disclosure corresponds to or or or where is subcarrier spacing (e.g., 15, 30, 60, 120, 240 kHz) and

[0440] In one example, one of the configurable values of corresponds to a function of a PMI subband size (e.g., where the PMI subband size can be calculated based on the number of RBs per PMI subband, e.g., where is the number of RBs per CQI subband, is the number of subcarriers per RB, is subcarrier spacing, and R is the number of precoding matrix (PMIs) per CQI subband.

[0441] - In one example, each example shown herein with replacing the CP by a function of a PMI subband size can be another example.

[0442] - In one example, the maximum (configurable) value of (or ) can be determined based on the maximum configurable value (up to 38) and (in {1,4}), e.g., is up to 152. For example, M (or B) does not exceed 256 (or 8 bits).

[0443] In one example, one of the configurable values of corresponds to a function of reference signal spacing (RS frequency density) in frequency-domain (e.g., or RB size or subcarrier spacing.

[0444] In one example, each example shown herein with replacing the CP by a function of reference signal spacing in frequency-domain or RB size or subcarrier spacing can be another example. (e.g., )

[0445] In one example, can be determined based on a value of multiples of a step size, where the step size can be determined by a configured band-width-part (BWP) (in associated CSI-RS resource / resource set measurement), and the multiples can be given by (i.e., M-1).

[0446] In one example, a range value of can be implicitly configured by NW via RS configuration for measurement and a number of quantization states (or a number of bits for quantization states (where )) is only configured.

[0447] In one example, a UE is not expected to be configured with where the value of exceeds a measurable delay value from associated CSI-RS resource / resource set. The measurement delay value can be determined RS density in frequency (spacing between two resource allocation of the RS (e.g., TRS RE density, such as 1 RE / RB / port, 3 RE / RB / port).

[0448] In one embodiment, a UE ( e.g., the UE 116) is configured (via higher-layer signaling or MAC-CE or DCI) with a report including CSI for TRPs or AGs or CSI-RS resources, where the CSI (e.g., RI / PMI / CQI) is calculated / determined based on a calibration-related information (CLI). In one example, the report can be configured via higher-layer parameterCSI-ReportConfigwithcodebookConfigset to'codebookConfig-r18'(e.g., Rel-18 CJT Type-II CSI). In one example, the report can be configured via higher-layer parameterCSI-ReportConfigwithcodebookConfigset to a new value (i.e., a quantity relevant to CSI). In one example, the CLI includes information in one of the examples described in this disclosure (e.g., according to one or more embodiments described herein). For example, the information includes quantities of the calibration reporting described in one of the examples in this disclosure (e.g., according to one or more embodiments described herein). In one example, the CLI corresponds to (or includes) the information that the UE reports for a configured calibration reporting described in one of the examples described in this disclosure.

[0449] The CSI can be calculated / determined at the UE assuming pre-compensation based on the CLI information (e.g., delay offset, when ReportQuantity set to 'cjtc-Dd'). This can facilitate UE-specific delay offset pre-compensation at the NW (or gNB) since it can avoid UE-specific CSI-RS transmission (which incurs CSI-RS overhead).

[0450] In one embodiment, the CLI for determining / calculating the CSI can be either implicitly or explicitly configured.

[0451] In one example, the CLI for determining / calculating the CSI includes information that the UE is configured to report for a calibration reporting (e.g., reportQuantity set to 'cjtc-Dd' or 'cjtc-F', 'cjtc-Dd-F'). For example, the CSI is calculated / determined assuming (delay / frequency offset) pre-compensation utilizing the information that UE is configured to report (or reported) for the calibration reporting.

[0452] In one example, the information is associated with (or corresponds to) a latest calibration reporting. In this case, the CSI can be calculated / determined using the information that the UE reported in the latest calibration reporting from the time that the UE receives CSI-RS resource(s) (or DL RS(s)) for the CSI reporting.

[0453] In one example, the information is associated with (or corresponds to) a latest calibration reporting. In this case, the CSI can be calculated / determined using the information that the UE reported in the latest calibration reporting from the time that the UE reports the CSI.

[0454] In one example, linking information of the CLI reporting (e.g., CJT-C reporting) and the CSI reporting (e.g., Rel-18 CJT Type-II CSI reporting) can be configured by higher-layer signaling (i.e., RRC). In another example, linking information of the CLI reporting and the CSI reporting (e.g., Rel-18 CJT Type-II CSI reporting) can be configured by MAC-CE or DCI.

[0455] In one example, a linked CLI reporting in a report configuration of CSI reporting can be configured via higher-layers signaling (i.e., RRC) or MAC-CE, DCI.

[0456] In one embodiment, the UE is configured (or triggered via DCI or MAC-CE or higher-layer signaling) to (jointly)report the CSI and CLI, (i.e., the report includes both the CSI and CLI), where the CSI and CLI are multiplexed and reported in a same slot (i.e., a same PUSCH) (or different slots).

[0457] In one example, the CSI is determined / calculated assuming pre-compensation (at the UE) utilizing the CLI that is multiplex with the CSI and reported in a same slot (a same PUSCH).

[0458] In one example, the CSI report and the CLI report (e.g., a joint report of them) are triggered by a (same) trigger state via DCI in a aperiodic manner (or a semi-persistent or periodic manner), where the CSI report and CSI report are associated with the trigger state.

[0459] In one example, the joint report of the CSI and CLI can be configured (or triggered) only when delay offset reporting is configured for the CLI reporting (e.g., reportQuantity is set to 'cjtc-Dd').

[0460] In one example, the joint report of the CSI and CLI can be configured (or triggered) only when frequency offset reporting is configured for the CLI reporting (e.g., reportQuantity is set to 'cjtc-F').

[0461] In one example, the joint report of the CSI and CLI can be configured (or triggered) only when delay offset reporting or joint reporting of delay-offset and frequency-offset is configured for the CLI reporting (e.g., reportQuantity is set to 'cjtc-Dd' or 'cjtc-Dd-F').

[0462] In one example, when the delay offset reporting is configured for the CLI reporting (e.g., reportQuantity is set to 'cjtc-Dd' or 'cjtc-Dd-F'), the CSI part 1 does not include TRP selection indicator (i.e., -bit bitmap indicator in CSI Part 1 for CJT CSI reporting, cf) Rel-18 CJT CSI), regardless ofrestrictedCMR-selectionset to enabled or not. For example, this is because delay offset reporting already contains TRP selection information.

[0463] In one example, when the frequency offset reporting is configured for the CLI reporting (e.g., reportQuantity is set to 'cjtc-Dd' or 'cjtc-Dd-F'), the CSI part 1 does not include TRP selection indicator (i.e., -bit bitmap indicator in CSI Part 1 for CJT CSI reporting, cf) Rel-18 CJT CSI), regardless ofrestrictedCMR-selectionset to enabled or not. For example, when 'invalid' state is indicated for a TRS set(s) (TRPs) for the CLI reporting, the corresponding TRP(s) or CSI-RS resource(s) can be regarded as not selected TRPs.

[0464] In another example, when the joint report of the CSI and CLI is configured, the UE is not expected to be configured with enabling TRP selection (e.g.,restrictedCMR-selection) for the CSI reporting.

[0465] In another example, when the joint report of the CSI and CLI is configured, the UE follows the configured information on enabling TRP selection(e.g., restrictedCMR-selection)for the CSI reporting.

[0466] In one example, the joint report of the CSI and CLI is conveyed in a single CSI report.

[0467] In one example, the joint report of the CSI and CLI is conveyed in a separate CSI report, respectively.

[0468] In one example, the CLI for determining / calculating the CSI can be configured by NW, and the UE calculates / determines the CSI based on the configured CLI. In one example, delay offset and / or frequency offset values for each of the TRPs (or AGs or CSI-RS resources) are explicitly configured to the UE for the CSI report (e.g., Rel-18 CJT CSI reporting).

[0469] In one example, a set of configurable delay offset values is the same as a set of possible reported delay offset values from calibration reporting (e.g., when reportQuantity set to 'cjtc-Dd' or 'cjtc-Dd-F').

[0470] In one example, a set of configurable delay offset values is different from a set of possible reported delay offset values from calibration reporting (e.g., when reportQuantity set to 'cjtc-Dd' or 'cjtc-Dd-F').

[0471] In one example, a set of configurable frequency offset values is the same as a set of possible reported frequency offset values from calibration reporting (i.e., when reportQuantity set to 'cjtc-F' or 'cjtc-Dd-F').

[0472] In one example, a set of configurable frequency offset values is different from a set of possible reported frequency offset values from calibration reporting (i.e., when reportQuantity set to 'cjtc-F' or 'cjtc-Dd-F').

[0473] In one embodiment, CSI-RS resources for the CSI reporting and CSI-RS resource sets for the CLI reporting follow a pre-defined mapping rule or an implicitly configured rule, or an explicitly configured rule.

[0474] In one example, the lowest index of CSI-RS resource configured for the CSI reporting corresponds to the lowest index of CSI-RS resource set configured for the CLI reporting, and the second lowest index of CSI-RS resource configured for the CSI reporting corresponds to the second lowest index of CSI-RS resource set configured for the CLI reporting, and so on.

[0475] In one embodiment, the report includes TRP (CSI-RS resource) selection indicator via -bit (or )-bit) bitmap to indicate the TRP or CSI-RS resource for which the UE is not able to perform pre-compensation utilizing the CLI.

[0476] In one example, the report includes the indicator regardless ofrestrictedCMR-Selectionset to enabled or not.

[0477] In one embodiment, there is restriction for configuring the CSI reporting. In one example, the UE is not expected to be configured with the CSI reporting, associated with the CLI reporting, where a dynamic range of delay offset is configured to a certain value. For example, the dynamic range of AD<x CP can be configurable. For example, x=1. For example, the UE is not expected to be configured with dynamic range of AD=1 CP or dynamic range of AD>1 CP.

[0478] In one embodiment, a CSI reporting based on a CLI reporting can be configured according to UE capability.

[0479] In one example, the capability of a joint triggering to trigger CSI report and CLI report (e.g., 'cjtc-Dd', 'cjtc-F', 'cjtc-Dd-F', or others) multiplexed in a same PUSCH (or in a same PUSCH slot) is a separate UE Group feature based on a UE capability. In one example, the capability of a joint triggering is an optional feature of UE capability. In another example, the capability of a joint triggering is a basic feature of UE capability.

[0480] In one example, the capability of linking CSI report (e.g., according to one or more embodiments described herein) with CLI report (e.g., 'cjtc-Dd', 'cjtc-F', 'cjtc-Dd-F', or others) is a separate UE Group feature based on a UE capability. In one example, the capability of linking CSI report is an optional feature of UE capability. In another example, the capability of linking CSI report is a basic feature of UE capability.

[0481] In one example, the capability of CSI report with configuring explicit delay / frequency offset values (e.g., according to one or more embodiments described herein) is a separate UE Group feature based on a UE capability. In one example, the capability of CSI report with configuring explicit delay / frequency offset values is an optional feature of UE capability. In another example, the capability of CSI report with configuring explicit delay / frequency offset values is a basic feature of UE capability.

[0482] In one embodiment, time-domain behavior of a CSI-RS resource setting or a CSI report setting for a CSI reporting based on a CLI reporting can be according to at least one of the following examples.

[0483] In one example, aperiodic (AP) CSI-RS can (only) be configured in the CSI-RS resource setting for measurement.

[0484] In one example, AP / semi-persistent (SP) CSI-RS can (only) be configured in the CSI-RS resource setting for measurement.

[0485] In one example, AP / SP / periodic (P) CSI-RS can (only) be configured in the CSI-RS resource setting for measurement.

[0486] In one example, SP / P CSI-RS can (only) be configured in the CSI-RS resource setting for measurement.

[0487] In one example, AP CSI reporting can (only) be triggered or configured to perform for the CSI reporting.

[0488] In one example, AP / SP CSI reporting can (only) be triggered or configured to perform for the CSI reporting.

[0489] In one example, AP / SP / P CSI reporting can (only) be triggered or configured to perform for the CSI reporting.

[0490] In one example, SP / P CSI reporting can (only) be triggered or configured to perform for the CSI reporting.

[0491] In one embodiment, an indicator(s) is included in a CSI report (e.g., according to one or more embodiments described herein), where the indicator is associated with a CLI report (one example described in this disclosure).

[0492] In one example, an indicator is a 1-bit (or X-bit, where X>1) indicator to indicate whether the CSI is calculated based on the associated CLI report or not. For example, the indicator has '0' indicating the CSI is calculated without using the associated CLI report, and '1' indicating the CSI is calculated based on the associated CLI report, or vice-versa.

[0493] In one example, an indicator is a 1-bit (or X-bit, where X>1) indicator to indicate whether the CSI cannot be (or is difficult to be, or is not) calculated based on the associated CLI report or not. For example, when there are delay offset values exceeding CP length, it is difficult to obtain the accurate CSI associated with the CLI report. In this case, the indicator can indicate the situation.

[0494] In one example, an indicator or a joint indicator (>1 bit) of indicating the above in the examples can be included in the CSI report. For example, the indicator has at least three states (e.g., at least 2bit is needed) that state 1 indicates the CSI is calculated based on the associated CLI report, state 2 indicates the CSI is calculated without using the associated CLI report, and state 3 indicates the CSI can't be calculated using the associated CLI report.

[0495] In one embodiment, a UE can be configured with a first CSI report and a second CSI report via higher-layer signaling (e.g., RRC), where the second CSI report is determined based on content of the first CSI report (called 'linkage' between two CSI reports), and the first CSI report is associated with a first CSI report setting and a first CSI resource setting, and the second CSI report is associated with a second CSI report setting and a second CSI resource setting. In one example, the first CSI report and the second CSI report are jointly triggered via DCI (or MAC-CE or RRC) to report on a same PUSCH slot or instance. In another example, the first CSI report and the second CSI report are separately triggered via DCI (or MAC-CE or RRC) to separately report.

[0496] In one example, the first CSI report corresponds to CJT calibration reporting (CLI reporting), e.g., with report quantity set to 'cjtc-Dd' or 'cjtc-F' or 'cjtc-Dd-F', and the second CSI report corresponds to (Rel-18) CJT CSI reporting, e.g., with codebookType set to 'typeII-CJT-r18'.

[0497] In one example, the first CSI report corresponds to CJT calibration reporting (CLI reporting) e.g., with RRC parameter 'reportQuantity' set to 'cjtc-Dd' (Delay offset reporting).

[0498] In one example, the first CSI report corresponds to CJT calibration reporting (CLI reporting) e.g., with RRC parameter 'reportQuantity' set to 'cjtc-F' (frequency-offset reporting).

[0499] In one example, the first CSI report corresponds to CJT calibration reporting (CLI reporting) e.g., with RRC parameter 'reportQuantity' set to 'cjtc-Dd-F' (Delay-offset and frequency-offset reporting).

[0500] In one example, the second CSI report corresponds to (Rel-18) CJT CSI reporting e.g., with RRC parameter 'codebookType' set to 'typeII-CJT-r18' (Rel-18 CJT CSI reporting).

[0501] In one example, the second CSI report corresponds to (Rel-19) Type-I multi-panel CSI reporting.

[0502] In one example, when the first CSI report corresponds to CJT calibration reporting with 'reportQuantity' set to 'cjtc-Dd' and the second CSI report corresponds to Rel-18 CJT CSI reporting with 'codebookType' set to 'typeII-CJT-r18', the UE determines PMI for the Rel-18 eType-II CJT CSI report assuming pre-compensation using the UE reported delay offset of the first CSI report.

[0503] In one example, when the first CSI report corresponds to CJT calibration reporting with 'reportQuantity' set to 'cjtc-F' and the second CSI report corresponds to Rel-18 CJT CSI reporting with 'codebookType' set to 'typeII-CJT-r18', the UE determines PMI for the Rel-18 eType-II CJT CSI report assuming pre-compensation using the UE reported frequency offset of the first CSI report.

[0504] In one embodiment, for a case corresponding that the first and second CSI reports are separately triggered via DCI, gNB (NW) sends / transmits information regarding ACK / NACK for the first CSI report to the UE to indicate that whether gNB successfully decodes the first CSI report or not. It guarantees the UE and gNB (e.g., the BS 102) have the same understanding regarding the first CSI report, which is to be used for computing the second CSI report. In one example, the information regarding ACK / NACK for the first CSI report can be according to at least one of the following examples.

[0505] In one example, the DCI (DCI 0_1, 0_2, 0_3) triggering to perform the second CSI report (e.g., Rel-18 eType-II CJT CSI report) includes the information regarding ACK / NACK.

[0506] In one example, the CSI request field of the DCI includes extra 1-bit (or >1bit) to contain the information. In one example, the payload of the CSI request can be 2,3,4,5,6,or 7 bits (i.e., up to 7bits (=6+1)), which contains the bits determined byreportTriggerSizeand the extra 1-bit.

[0507] - In one example, the extra 1-bit is included only when the linkage between two CSI reports is (RRC) configured. In another example, the extra 1-bit is not included when the linkage is not configured.

[0508] In one example, the CSI request field of the DCI includes extra 1-bit (or >1bit) to contain the information, but the maximum payload of the CSI request is still the same, i.e., 6 bits. In this case, the maximum number of trigger states is reduced to where is the number of bits for the CSI request field determined byreportTriggerSize.

[0509] - In one example, the extra 1-bit is included only when the linkage between two CSI reports is (RRC) configured. In another example, the extra 1-bit is not included when the linkage is not configured.

[0510] In one example, a new field of the DCI is used to indicate the information with 1-bit (or >1bit).

[0511] - In one example, the new field can be 0-bit if the linkage is not configured.

[0512] In one example, a reserved bit(s) of the DCI is used to indicate the information with 1-bit (or >1bit).

[0513] - In one example, the reserved bit(s) can be reserved bit if the linkage is not configured.

[0514] In one embodiment, when NACK information is indicated to the UE, the UE determines the second CSI report according to at least one of the following examples.

[0515] In one example, the UE determines the second CSI report without considering (i.e., not based on) the content of the first CSI report. In one example, the UE determines the PMI for the Rel-18 eType-II CJT CSI report not assuming the pre-compensation of delay offset or frequency offset value(s) of the first CSI report.

[0516] In one example, the UE determines the second CSI report with considering (i.e., based on) the content of the first CSI report. In one example, the UE determines the PMI for the Rel-18 eType-II CJT CSI report assuming the pre-compensation of delay offset or frequency offset value(s) of the first CSI report.

[0517] In one example, the UE determines the second CSI report with considering (i.e., based on) the content of the first CSI report, and the first CSI report is reported (jointly) together with the second CSI report in the same PUSCH instance (like a joint-triggered case). In one example, the UE determines the PMI for the Rel-18 eType-II CJT CSI report assuming the pre-compensation of delay offset or frequency offset value(s) of the first CSI report, and both of the CSI reports are reported jointly in the same PUSCH instance.

[0518] In one example, the UE does not determine the second CSI report, and instead of reporting the second CSI report, the UE sends / transmits / reports the first CSI report.

[0519] In one example, the UE does not determine the second CSI report, and omits performing the second CSI reporting.

[0520] In one embodiment, for a case corresponding that the first and second CSI reports are separately triggered via DCI, an expiration time interval for UE to store the content of the first CSI report for computing the second CSI report based on the content of the first CSI report is according to at least one of the following examples.

[0521] In one example, the expiration time interval starts from the slot n corresponding to the first CSI reporting instance to n+k slots, where k is according to or subject to a UE capability. In one example, at least one of the supported values for k exceeds m, e.g., m=10, 50, 100, or 1000.

[0522] This disclosure provides CSI reporting based on calibration-related information (CLI). The calibration-related information such as delay-offset and / or frequency offset values can be reported via a new feature being developed in Rel-19 CJT calibration reporting on PUSCH. This disclosure provides a framework to report CSI for CJT, where the CSI is computed / determined with expecting pre-compensation (at the UE side) utilizing the calibration-related information. The provided aspects as follows:

[0523] - Separate reporting of CLI (a first CSI report) and CJT CSI (a second CSI report), and gNB confirmation to indicate ACK regarding the CLI reporting when requesting / triggering the CJT CSI report, so that the UE can compute the CJT CSI report assuming the pre-compensation of the reported CLI.

[0524] - Methods on how to confirm on the reception of the first CSI report: via reserved bit(s) / codepoints of existing DCI fields, via repurposing existing DCI fields, via introducing extra 1-bit on existing DCI field or new DCI field.

[0525] FIG. 12 illustrates a signal flow 1200 of an example procedure for CSI reporting according to embodiments of the present disclosure. For example, signal flow 1200 can be performed by the UE 116 and the gNB 102 and / or network 130 in the wireless network 100 of FIG. 1. This example is for illustration only and other embodiments can be used without departing from the scope of the present disclosure.

[0526] The procedure begins in 1210, a gNB (NW) transmits configured information about a first CSI reporting (e.g., R19 CJT calibration report), a second CSI reporting (e.g., R18 Type-II CJT CSI report), and a linkage between the two reporting to a UE. In 1220, the gNB (NW) transits a trigger to perform the first CSI reporting to the UE. In 1230, the UE performs the first CSI reporting and transmits the first CSI reporting to the gNB (NW). In 1240, the gNB (NW) decodes the first CSI. In 1250, the gNB (NW) transmits a trigger to perform the second CSI reporting, along with acknowledge (ACK) information indicating that the first CSI is successfully decoded. In 1260, the UE determines the second CSI, where the second CSI is determined based on the first CSI. In 1270, the UE performs the second CSI reporting and transmits the second CSI reporting to the gNB (NW).

[0527] In one embodiment, a UE can be configured with a first CSI report (e.g., Rel-19 CJT calibration (CLI) report) and a second CSI report (e.g., Rel-18 CJT Type-II CSI report) via higher-layer signaling (e.g., RRC), where the second CSI report is determined based on at least one content (or report quantity) of the first CSI report (called 'linkage' between two CSI reports), and the first CSI report is associated with a first CSI report setting (e.g., a higher-layer IE CSI-ReportConfig ID I1) and a first CSI resource setting (e.g. a higher layer IE CSI-ResourceConfig ID J1), and the second CSI report is associated with a second CSI report setting (e.g. a higher layer IE CSI-ReportConfig ID I2) and a second CSI resource setting (e.g. a higher layer IE CSI-ResourceConfig ID J2). In one example, the first CSI report and the second CSI report are jointly triggered via DCI (or MAC-CE or RRC) to report on a same PUSCH slot or instance, e.g. a code point of a CSI request field indicating either a joint CSI trigger state for I = (I1,I2) or a pair of CSI trigger states I1,I2. In another example, the first CSI report and the second CSI report are separately triggered via DCI (or MAC-CE or RRC) to separately perform reporting, e.g. two separate code points or CSI request fields on one DCI or two DCIs.

[0528] In one example, the first CSI report corresponds to CJT calibration reporting (CLI reporting), e.g., with report quantity set to 'cjtc-Dd' or 'cjtc-F' or 'cjtc-Dd-F' or 'cjtc-P', and the second CSI report corresponds to (Rel-18) CJT CSI reporting, e.g., with codebookType set to 'typeII-CJT-r18'.

[0529] In one example, the first CSI report corresponds to CJT calibration reporting (CLI reporting) e.g., with RRC parameter 'reportQuantity' set to 'cjtc-Dd' (Delay offset reporting).

[0530] In one example, the first CSI report corresponds to CJT calibration reporting (CLI reporting) e.g., with RRC parameter 'reportQuantity' set to 'cjtc-F' (frequency-offset reporting).

[0531] In one example, the first CSI report corresponds to CJT calibration reporting (CLI reporting) e.g., with RRC parameter 'reportQuantity' set to 'cjtc-P' (phase-offset reporting).

[0532] In one example, the first CSI report corresponds to CJT calibration reporting (CLI reporting) e.g., with RRC parameter 'reportQuantity' set to 'cjtc-Dd-F' (Delay-offset and frequency-offset reporting).

[0533] In one example, the second CSI report corresponds to (Rel-18) CJT CSI reporting e.g., with RRC parameter 'codebookType' set to 'typeII-CJT-r18' (Rel-18 CJT CSI reporting).

[0534] In one example, the second CSI report corresponds to (Rel-19) Type-I multi-panel (MP) CSI reporting.

[0535] In one example, the first CSI report corresponds to CJT calibration reporting (CLI reporting), e.g., with report quantity set to 'cjtc-Dd' or 'cjtc-F' or 'cjtc-Dd-F' or 'cjtc-P', and the second CSI report corresponds to a PMI-based CSI report with reportQuantity = RI / PMI / CQI or LI / RI / PMI / CQI or CRI / RI / PMI / CQI or CRI / LI / RI / PMI / CQI.

[0536] In one example, the first CSI report corresponds to CJT calibration reporting (CLI reporting), e.g., with report quantity set to 'cjtc-Dd' or 'cjtc-F' or 'cjtc-Dd-F' or 'cjtc-P', and the second CSI report corresponds to a non-PMI-based CSI report with reportQuantity = RI / CQI or LI / RI / CQI or CRI / RI / CQI or CRI / LI / RI / CQI.

[0537] In one example, the first CSI report corresponds to a first portion of a CSI report, and the second CSI report corresponds to a second portion of the CSI report, where the CSI report has a reportQuantity = RI / PMI / CQI or LI / RI / PMI / CQI or CRI / RI / PMI / CQI or CRI / LI / RI / PMI / CQI or RI / CQI or LI / RI / CQI or CRI / RI / CQI or CRI / LI / RI / CQI.

[0538] In one example, when the first CSI report corresponds to CJT calibration reporting with 'reportQuantity' set to 'cjtc-Dd' and the second CSI report corresponds to Rel-18 CJT CSI reporting with 'codebookType' set to 'typeII-CJT-r18', the UE determines PMI for the Rel-18 eType-II CJT CSI report assuming pre-compensation using the UE reported delay offset of the first CSI report.

[0539] In one example, when the first CSI report corresponds to CJT calibration reporting with 'reportQuantity' set to 'cjtc-F' and the second CSI report corresponds to Rel-18 CJT CSI reporting with 'codebookType' set to 'typeII-CJT-r18', the UE ( e.g., the UE 116) determines PMI for the Rel-18 eType-II CJT CSI report assuming pre-compensation using the UE reported frequency offset of the first CSI report.

[0540] In one example, when the first CSI report corresponds to CJT calibration reporting with 'reportQuantity' set to 'cjtc-Dd' and the second CSI report corresponds to (Rel-19) Type-I MP CSI reporting with 'codebookType' set to 'typeI-MultiPanel-r19', the UE determines PMI for the (Rel-19) Type-I MP CSI report assuming pre-compensation using the UE reported delay offset of the first CSI report.

[0541] In one example, when the first CSI report corresponds to CJT calibration reporting with 'reportQuantity' set to 'cjtc-F' and the second CSI report corresponds to (Rel-19) Type-I MP CSI reporting with 'codebookType' set to 'typeI-MultiPanel-r19', the UE determines PMI for the (Rel-19) Type-I MP CSI report assuming pre-compensation using the UE reported frequency offset of the first CSI report.

[0542] In one example, the overall operation procedure of the embodiment is described in FIG. 12.

[0543] Although in this disclosure, terms such as 'ACK' or 'NACK' are used, the terms can be written or described or utilized in another way. For example, 'ACK' is associated with a hypothesis and 'NACK' is associated with another hypothesis, where the hypotheses are described in each example of this disclosure. In another example, 'ACK' is associated with an indication and 'NACK' is associated with another indication, where the meaning of indications is described in each example of this disclosure.

[0544] In one embodiment, for a case when the first and second CSI reports are separately triggered via DCI, as described herein, gNB (NW) sends / transmits information regarding acknowledge (ACK) information for the first CSI report to the UE to indicate that gNB successfully decoded and received the first CSI report. Note that it guarantees the UE and gNB have the same understanding regarding the first CSI report, which is to be used for determining the second CSI report. In one example, the information regarding ACK information for the first CSI report can be according to at least one of the following examples / embodiments.

[0545] In one example, ACK information for the first CSI report is implicitly indicated via a CSI request for the second CSI report. In other words, a CSI request for the second CSI report can be regarded as an implicit ACK for the first CSI report.

[0546] In one embodiment, the DCI (e.g., UL DCI format 0_1, 0_2, 0_3) triggering to perform the second CSI report on PUSCH (e.g., Rel-18 eType-II CJT CSI report) includes the information regarding ACK.

[0547] In one embodiment, the ACK information is indicated via a reserved bit(s) and / or reserved codepoints of at least one of the existing DCI fields. In this case, since reserved bit / reserved codepoints of the existing DCI fields are used to indicate the ACK information, no additional bit / codepoint needs to be used (for the ACK) when the reserved bit / codepoints are used.

[0548] The existing DCI fields that have reserved bit(s) and / or reserved codepoints for DCI format 0_1, 0_2, and 0_3 are as follows [7].

[0549] DCI format 0_1 / 0_2 / 0_3:

[0550] - DCI fields having reserved bit(s): Carrier indicator, downlink feedback information (DFI) flag, Transform precoder indicator, DMRS sequence initialization

[0551] - DCI fields having reserved codepoints: Precoding information and number of layers, Second precoding information, Antenna ports, SRI (SRS resource indicator) indication, Second SRI indication, SRS resource set indication, SRS offset indication

[0552] In one example, the ACK information is indicated via reserved bit / codepoints according to at least one of the following examples.

[0553] In one example, one of the reserved bits of the DCI field of Carrier indicator is used when this format is carried by PDCCH on the primary cell and the UE is configured for scheduling on the primary cell from an SCell (secondary cell), with the same number of bits as that in this format carried by PDCCH on the SCell for scheduling on the primary cell.

[0554] In one example, one bit of the DCI field of DFI flag is used when the bit is reserved, i.e., for a DCI format 0_1 with CRC scrambled by cell RNTI (C-RNTI) / semi-persistent (SP)-CSI-RNTI / modulation and coding scheme (MCS)-C-RNTI and for operation in a cell with shared spectrum channel access.

[0555] In one example, one bit of the DCI field of Transform precoder indicator is used when the bit is reserved, i.e., for a DCI format 0_1 with CRC scrambled by CS-RNTI and the value indicated by new data indicator field is 0, or for a DCI format 0_1 with CRC scrambled by SP-CSI-RNTI.

[0556] In one example, one bit of the DCI field of DMRS sequence initialization is used when the bit is reserved, i.e., if the Transform precoder indicator field is present and set to '0'.

[0557] In one example, reserved codepoints of the DCI field of Precoding information and number of layers are used for cases that the number of reserved codepoints is sufficient to indicate the ACK information (e.g., it has at least an amount of 1-bit payload-size or using at least one reserved codepoint for ACK does not increase the payload of the DCI field.)

[0558] In one example, reserved codepoints of the DCI field of Second precoding information are used for cases that the number of reserved codepoints is sufficient to indicate the ACK information (e.g., it has at least an amount of 1-bit payload-size or using at least one reserved codepoint for ACK does not increase the payload of the DCI field.)

[0559] In one example, reserved codepoints of the DCI field of Antenna ports are used for cases that the number of reserved codepoints is sufficient to indicate the ACK information (e.g., it has at least an amount of 1-bit payload or using at least one reserved codepoint for ACK does not increase the payload of the DCI field.)

[0560] In one example, reserved codepoints of the DCI field of SRI indication are used for cases that the number of reserved codepoints is sufficient to indicate the ACK information (e.g., it has at least an amount of 1-bit payload or using at least one reserved codepoint for ACK does not increase the payload of the DCI field.)

[0561] In one example, reserved codepoints of the DCI field of second SRI indication are used for cases that the number of reserved codepoints is sufficient to indicate the ACK information (e.g., it has at least an amount of 1-bit payload or using at least one reserved codepoint for ACK does not increase the payload of the DCI field.)

[0562] In one example, reserved codepoints of the DCI field of SRS resource set indication are used for cases that the number of reserved codepoints is sufficient to indicate the ACK information (e.g., it has at least an amount of 1-bit payload or using at least one reserved codepoint for ACK does not increase the payload of the DCI field.)

[0563] In one example, reserved codepoints of the DCI field of SRS offset indication are used for cases that the number of reserved codepoints is sufficient to indicate the ACK information (e.g., it has at least an amount of 1-bit payload or using at least one reserved codepoint for ACK does not increase the payload of the DCI field.)

[0564] In one example, reserved codepoints of a DCI field other than the DCI fields described herein are used for cases that the number of reserved codepoints is sufficient to indicate the ACK information (e.g., it has at least an amount of 1-bit payload-size or using at least one reserved codepoint for ACK does not increase the payload of the DCI field.)

[0565] In one example, regarding how to assign the ACK information using reserved codepoints for a DCI field, at least one of the following examples can be applied.

[0566] - In one example (Ex-a), the most significant bit of the DCI field (e.g., set to '1') can be used to indicate the ACK information, while the other bits of the DCI field are used to indicate the original intention / information. In one example, a first of reserved codepoint(s) can be used.

[0567] - In another example (Ex-b), another significant bit (second significant bit, or the least significant bit whose index larger than or equal to the number of used codepoints) instead of the most significant bit, (e.g., set to '1') can be used to indicate the ACK information, while the other bits of the DCI field are used to indicate the original intention / information. In one example, a first of reserved codepoint(s) can be used.

[0568] - In one example (Ex-c), starting from the lowest indexkfor reserved codepoints, the ACK information is assigned one-by-one for each of the used codepoints, until the index 2k-1, wherekis the number of used codepoints.

[0569] In one example, reserved codepoints of the DCI field of Antenna ports are used to indicate the ACK information if transform precoder is disabled and rank>x, e.g., x=2 (or another value, e.g., 1 or 3). In one example, the associated tables for the cases that transform precoder is disabled and rank>2 are tables 7.3.1.1.2-10 / 10A / 11 / 14 / 14A / 15 / 15A / 15B / 15C / 15D / 18 / 18A / 19 / 19A / 19B / 22 / 22A / 23 / 23A / 23B / 23C / 23D / 40 / 40A / 41 / 42 / 43 / 44 / 45 / 48 / 48A / 49 / 50 / 51 / 52 / 53 / 56 / 56A / 57 / 58 / 59 / 60 / 61 / 64 / 64A / 65 / 66 / 67 / 68 / 69 [7].

[0570] As an example, using the table 7.3.1.1.2-22 of [7], (this can be applicable to another table example) there are codepoints used for Antenna ports when the codepoint index corresponds to value 0-5, but there are reserved codepoints from 6 to 31. In this case, the ACK information can be indicated via using the codepoints as shown in the following examples:

[0571] - (Ex-a): codepoints 16, 17, 18, 19, 20, and 21 indicate the ACK information and the information corresponding to codepoints 0, 1, 2, 3, 4, 5, and 6, respectively. The other reserved codepoints remain the same.

[0572] - (Ex-b) (shown herein example): codepoints 8, 9, 10, 11, 12, and 13 indicate the ACK information and the information corresponding to codepoints 0, 1, 2, 3, 4, 5, and 6, respectively. The other reserved codepoints remain the same.

[0573] - (Ex-c) (shown herein example): codepoints 7, 8, 9, 10, 11, and 12 indicate the ACK information and the information corresponding to codepoints 0, 1, 2, 3, 4, 5, and 6, respectively. The other reserved codepoints remain the same.

[0574]

[0575] In one example, the associated tables for the cases that transform precoder is disabled and rank>3 are Tables 7.3.1.1.2-11 / 15 / 15A / 15B / 15C / 15D / 19 / 19A / 19B / 23 / 23A / 23B / 23C / 23D / 41 / 42 / 43 / 44 / 45 / 49 / 50 / 51 / 52 / 53 / 57 / 58 / 59 / 60 / 61 / 66 / 67 / 68 / 69 [7].

[0576] In one example, when the number of reserved codepoints are not sufficient (i.e., not as much as 1-bit amount of the reserved codepoints), a first half of the whole codepoints is used for the original codepoints' information, and a second half of the whole codepoints is used for the ACK information and the information corresponding to the codepoints for the first half.

[0577] As an example, using the table 7.3.1.1.2-49 of [7] (this can be applicable to another table example) there are codepoints used for Antenna ports when the codepoint index corresponds to value 0-16, but there are reserved codepoints from 17 to 31. In this case, the number of reserved codepoints is not sufficient to indicate the ACK information along with indicating the original information. Thus, in one example, a first half of the whole codepoints, e.g.,, codepoint 0 to 15, is used for the original codepoints' information, and a second half of the whole, e.g., codepoint 16 to 31, is used to indicate the ACK information and the information corresponding to the codepoint 0 to 15 for the first half, as shown in Table 1.

[0578]

[0579]

[0580]

[0581] In one example, any combination of the examples herein regarding reserved bit / codepoints of DCI fields can be used to indicate the ACK information. In one example, reserved codepoints of the DCI field of Antenna ports are used to indicate the ACK information if transform precoder is disabled and rank>x, e.g., x=2, and one bit of the DCI field of DMRS sequence initialization is used when the bit is reserved if the Transform precoder indicator field is present and set to '0'.

[0582] In one example, NACK information can be indicated via codepoints that are not used for ACK.

[0583] In one embodiment, the ACK information is indicated via an existing DCI field or a combination of existing DCI fields that are not used or not allowed when requesting / triggering the (second) CSI report. In one example, the DCI fields can be at least one of the following DCI fields: Carrier indicator, DFI flag, HARQ-ACK bitmap, transmit power control (TPC) command for scheduled PUSCH, UL / SUL indicator, Bandwidth part indicator, Frequency domain resource assignment, Time domain resource assignment, Frequency hopping flag, Modulation and coding scheme, New data indicator, Redundancy version, Transform precoder indicator, HARQ process number, 1stdownlink assignment index, 2nddownlink assignment index, 3rddownlink assignment index, Second TPC command for scheduled PUSCH, SRS resource set indicator, SRS resource indicator, Second SRS resource indicator, Precoding information and number of layers, Second precoding information, Antenna ports, SRS request, SRS offset indicator, code block group (CBG) transmission information, phase tracking reference signal (PTRS)-DMRS association, Second PTRS-DMRS, beta_offset indicator, DMRS sequence initialization, UL-SCH indicator, ChannelAccess-CPext-CAPC, Open-loop power control parameter set indication, Priority indicator, Invalid symbol pattern indicator, Minimum applicable scheduling offset indicator, SCell dormancy indication, Sidelink assignment index, PDCCH monitoring adaptation indication.

[0584] In one embodiment, a DCI field or multiple DCI fields (that is not used when requesting / triggering the (second) CSI report) can be present if a condition is satisfied or met. The DCI field(s) is used to indicate the ACK information (e.g., via one bit or a codepoint) when requesting / triggering the (second) CSI report. In one example, the condition can be according to at least one of the following examples.

[0585] - In one example, the condition includes that a linkage between the two reports is configured (e.g., via higher-layer IElinkedCJTCReport).

[0586] - In one example, the condition includes that a linkage between the two reports is configured (e.g., higher-layer IElinkedCJTCReport) and separate triggering for the two reports is configured (e.g., higher-layer IEseparateTriggering).

[0587] - In one example, the condition includes that separate triggering for the two reports is configured (e.g., higher-layer IEseparateTriggering).

[0588] In one example, one or multiple DCI fields can be present and used to indicate the ACK information (e.g., via one-bit or one-bit amount of codepoints or a codepoint), according to at least one of the following examples.

[0589] In one example, the DCI field of Carrier indicator is present and used to indicate the ACK information (e.g., via one bit or one-bit amount of codepoints or a codepoint), if the condition is satisfied or met.

[0590] In one example, the DCI field of DFI flag is present and used to indicate the ACK information (e.g., via one bit or one-bit amount of codepoints or a codepoint), if the condition is satisfied or met.

[0591] In one example, the DCI field of HARQ-ACK bitmap is present and used to indicate the ACK information (e.g., via one bit or one-bit amount of codepoints or a codepoint), if the condition is satisfied or met.

[0592] In one example, the DCI field of TPC command for scheduled PUSCH is present and used to indicate the ACK information (e.g., via one bit or one-bit amount of codepoints or a codepoint), if the condition is satisfied or met.

[0593] In one example, the DCI field of UL / SUL indicator is present and used to indicate the ACK information (e.g., via one bit or one-bit amount of codepoints or a codepoint), if the condition is satisfied or met.

[0594] In one example, the DCI field of Bandwidth part indicator is present and used to indicate the ACK information (e.g., via one bit or one-bit amount of codepoints or a codepoint), if the condition is satisfied or met.

[0595] In one example, the DCI field of Frequency domain resource assignment is present and used to indicate the ACK information (e.g., via one bit or one-bit amount of codepoints or a codepoint), if the condition is satisfied or met.

[0596] In one example, the DCI field of Time domain resource assignment is present and used to indicate the ACK information (e.g., via one bit or one-bit amount of codepoints or a codepoint), if the condition is satisfied or met.

[0597] In one example, the DCI field of Frequency hopping flag is present and used to indicate the ACK information (e.g., via one bit or one-bit amount of codepoints or a codepoint), if the condition is satisfied or met.

[0598] In one example, the DCI field of Modulation and coding scheme is present and used to indicate the ACK information (e.g., via one bit or one-bit amount of codepoints or a codepoint), if the condition is satisfied or met.

[0599] In one example, the DCI field of New data indicator is present and used to indicate the ACK information (e.g., via one bit or one-bit amount of codepoints or a codepoint), if the condition is satisfied or met.

[0600] In one example, the DCI field of Redundancy version is present and used to indicate the ACK information (e.g., via one bit or one-bit amount of codepoints or a codepoint), if the condition is satisfied or met.

[0601] In one example, the DCI field of Transform precoder indicator is present and used to indicate the ACK information (e.g., via one bit or one-bit amount of codepoints or a codepoint), if the condition is satisfied or met.

[0602] In one example, the DCI field of HARQ process number is present and used to indicate the ACK information (e.g., via one bit or one-bit amount of codepoints or a codepoint), if the condition is satisfied or met.

[0603] In one example, the DCI field of 1stdownlink assignment index is present and used to indicate the ACK information (e.g., via one bit or one-bit amount of codepoints or a codepoint), if the condition is satisfied or met.

[0604] In one example, the DCI field of 2nddownlink assignment index is present and used to indicate the ACK information (e.g., via one bit or one-bit amount of codepoints or a codepoint), if the condition is satisfied or met.

[0605] In one example, the DCI field of 3rddownlink assignment index is present and used to indicate the ACK information (e.g., via one bit or one-bit amount of codepoints or a codepoint), if the condition is satisfied or met.

[0606] In one example, the DCI field of Second TPC command for scheduled PUSCH is present and used to indicate the ACK information (e.g., via one bit or one-bit amount of codepoints or a codepoint), if the condition is satisfied or met.

[0607] In one example, the DCI field of SRS resource set indicator is present and used to indicate the ACK information (e.g., via one bit or one-bit amount of codepoints or a codepoint), if the condition is satisfied or met.

[0608] In one example, the DCI field of SRS resource indicator is present and used to indicate the ACK information (e.g., via one bit or one-bit amount of codepoints or a codepoint), if the condition is satisfied or met.

[0609] In one example, the DCI field of Second SRS resource indicator is present and used to indicate the ACK information (e.g., via one bit or one-bit amount of codepoints or a codepoint), if the condition is satisfied or met.

[0610] In one example, the DCI field of Precoding information and number of layers is present and used to indicate the ACK information (e.g., via one bit or one-bit amount of codepoints or a codepoint), if the condition is satisfied or met.

[0611] In one example, the DCI field of Second precoding information is present and used to indicate the ACK information (e.g., via one bit or one-bit amount of codepoints or a codepoint), if the condition is satisfied or met.

[0612] In one example, the DCI field of Antenna ports is present and used to indicate the ACK information (e.g., via one bit or one-bit amount of codepoints or a codepoint), if the condition is satisfied or met.

[0613] In one example, the DCI field of SRS request is present and used to indicate the ACK information (e.g., via one bit), if the condition is satisfied or met.

[0614] In one example, the DCI field of SRS offset indicator is present and used to indicate the ACK information (e.g., via one bit or one-bit amount of codepoints or a codepoint), if the condition is satisfied or met.

[0615] In one example, the DCI field of CBG transmission information is present and used to indicate the ACK information (e.g., via one bit or one-bit amount of codepoints or a codepoint), if the condition is satisfied or met.

[0616] In one example, the DCI field of PTRS-DMRS association is present and used to indicate the ACK information (e.g., via one bit or one-bit amount of codepoints or a codepoint), if the condition is satisfied or met.

[0617] In one example, the DCI field of Second PTRS-DMRS is present and used to indicate the ACK information (e.g., via one bit or one-bit amount of codepoints or a codepoint), if the condition is satisfied or met.

[0618] In one example, the DCI field of beta_offset indicator is present and used to indicate the ACK information (e.g., via one bit or one-bit amount of codepoints or a codepoint), if the condition is satisfied or met.

[0619] In one example, the DCI field of DMRS sequence initialization is present and used to indicate the ACK information (e.g., via one bit or one-bit amount of codepoints or a codepoint), if the condition is satisfied or met.

[0620] In one example, the DCI field of UL-SCH indicator is present and used to indicate the ACK information (e.g., via one bit or one-bit amount of codepoints or a codepoint), if the condition is satisfied or met.

[0621] In one example, the DCI field of ChannelAccess-CPext-CAPC is present and used to indicate the ACK information (e.g., via one bit or one-bit amount of codepoints or a codepoint), if the condition is satisfied or met.

[0622] In one example, the DCI field of Open-loop power control parameter set indication is present and used to indicate the ACK information (e.g., via one bit or one-bit amount of codepoints or a codepoint), if the condition is satisfied or met.

[0623] In one example, the DCI field of SCell dormancy indication is present and used to indicate the ACK information (e.g., via one bit or one-bit amount of codepoints or a codepoint), if the condition is satisfied or met.

[0624] In one example, the DCI field of Sidelink assignment index is present and used to indicate the ACK information (e.g., via one bit or one-bit amount of codepoints or a codepoint), if the condition is satisfied or met.

[0625] In one example, the DCI field of Priority indicator is present and used to indicate the ACK information (e.g., via one bit or one-bit amount of codepoints or a codepoint), if the condition is satisfied or met.

[0626] In one example, the DCI field of Invalid symbol pattern indicator is present and used to indicate the ACK information (e.g., via one bit or one-bit amount of codepoints or a codepoint), if the condition is satisfied or met.

[0627] In one example, the DCI field of Minimum applicable scheduling offset indicator is present and used to indicate the ACK information (e.g., via one bit or one-bit amount of codepoints or a codepoint), if the condition is satisfied or met.

[0628] In one example, the DCI field of PDCCH monitoring adaption indication is present and used to indicate the ACK information (e.g., via one bit or one-bit amount of codepoints or a codepoint), if the condition is satisfied or met.

[0629] In one example, NACK information can be indicated via codepoints that are not used for ACK.

[0630] In one embodiment, the ACK information is indicated via an existing DCI field or a combination of existing DCI fields that can be used when requesting / triggering the (second) CSI report. In one example, the DCI fields can be at least one of the following DCI fields: Carrier indicator, DFI flag, HARQ-ACK bitmap, TPC command for scheduled PUSCH, UL / SUL indicator, Bandwidth part indicator, Frequency domain resource assignment, Time domain resource assignment, Frequency hopping flag, Modulation and coding scheme, New data indicator, Redundancy version, Transform precoder indicator, HARQ process number, 1stdownlink assignment index, 2nddownlink assignment index, 3rddownlink assignment index, Second TPC command for scheduled PUSCH, SRS resource set indicator, SRS resource indicator, Second SRS resource indicator, Precoding information and number of layers, Second precoding information, Antenna ports, SRS request, SRS offset indicator, CBG transmission information, PTRS-DMRS association, Second PTRS-DMRS, beta_offset indicator, DMRS sequence initialization, UL-SCH indicator, ChannelAccess-CPext-CAPC, Open-loop power control parameter set indication, Priority indicator, Invalid symbol pattern indicator, Minimum applicable scheduling offset indicator, SCell dormancy indication, Sidelink assignment index, PDCCH monitoring adaptation indication, CSI request.

[0631] In one embodiment, one-bit (or one-bit amount of codepoints or a codepoint or multiple codepoints less or larger than one-bit amount codepoints) of a DCI field or multiple DCI fields (that can be used when requesting / triggering the (second) CSI report) can be used to indicate the ACK information if a condition is satisfied or met. In this case, since one-bit amount of codepoints are used to the ACK information, the codepoints to use for the original purpose of the DCI field is decreased to a half of the total number of original bits / codepoints. In one example, the condition can be according to at least one of the following examples.

[0632] - In one example, the condition includes that a linkage between the two reports is configured (e.g., via higher-layer IElinkedCJTCReport).

[0633] - In one example, the condition includes that a linkage between the two reports is configured (e.g., via higher-layer IElinkedCJTCReport) and separate triggering for the two reports is configured (e.g., via higher-layer IEseparateTriggering).

[0634] - In one example, the condition includes that separate triggering for the two reports is configured (e.g., via higher-layer IEseparateTriggering).

[0635] In one example, one-bit or one-bit amount of codepoints or multiple codepoints less or larger than one-bit amount codepoints of one or multiple DCI fields can be used to indicate the ACK information, according to at least one of the following examples.

[0636] In one example, one-bit (or one-bit amount of codepoints or a codepoint or multiple codepoints less or larger than one-bit amount codepoints) of the DCI field of Carrier indicator is used to indicate the ACK information, if the condition is satisfied or met.

[0637] In one example, one-bit (or one-bit amount of codepoints or a codepoint) of the DCI field of DFI flag is used to indicate the ACK information, if the condition is satisfied or met.

[0638] In one example, one-bit (or one-bit amount of codepoints or a codepoint or multiple codepoints less or larger than one-bit amount codepoints) of the DCI field of HARQ-ACK bitmap is used to indicate the ACK information, if the condition is satisfied or met.

[0639] In one example, one-bit (or one-bit amount of codepoints or a codepoint or multiple codepoints less or larger than one-bit amount codepoints) of the DCI field of TPC command for scheduled PUSCH is used to indicate the ACK information, if the condition is satisfied or met.

[0640] In one example, one-bit (or one-bit amount of codepoints or a codepoint or multiple codepoints less or larger than one-bit amount codepoints) of the DCI field of UL / SUL indicator is used to indicate the ACK information, if the condition is satisfied or met.

[0641] In one example, one-bit (or one-bit amount of codepoints or a codepoint or multiple codepoints less or larger than one-bit amount codepoints) of the DCI field of Bandwidth part indicator is used to indicate the ACK information, if the condition is satisfied or met.

[0642] In one example, one-bit (or one-bit amount of codepoints or a codepoint or multiple codepoints less or larger than one-bit amount codepoints) of the DCI field of Frequency domain resource assignment is used to indicate the ACK information, if the condition is satisfied or met.

[0643] In one example, one-bit (or one-bit amount of codepoints or a codepoint or multiple codepoints less or larger than one-bit amount codepoints) of the DCI field of Time domain resource assignment is used to indicate the ACK information, if the condition is satisfied or met.

[0644] In one example, one-bit (or one-bit amount of codepoints or a codepoint or multiple codepoints less or larger than one-bit amount codepoints) of the DCI field of Frequency hopping flag is used to indicate the ACK information, if the condition is satisfied or met.

[0645] In one example, one-bit (or one-bit amount of codepoints or a codepoint or multiple codepoints less or larger than one-bit amount codepoints) of the DCI field of Modulation and coding scheme is used to indicate the ACK information, if the condition is satisfied or met.

[0646] In one example, one-bit (or one-bit amount of codepoints or a codepoint or multiple codepoints less or larger than one-bit amount codepoints) of the DCI field of New data indicator is used to indicate the ACK information, if the condition is satisfied or met.

[0647] In one example, one-bit (or one-bit amount of codepoints or a codepoint or multiple codepoints less or larger than one-bit amount codepoints) of the DCI field of Redundancy version is used to indicate the ACK information, if the condition is satisfied or met.

[0648] In one example, one-bit (or one-bit amount of codepoints or a codepoint or multiple codepoints less or larger than one-bit amount codepoints) of the DCI field of Transform precoder indicator is used to indicate the ACK information, if the condition is satisfied or met.

[0649] In one example, one-bit (or one-bit amount of codepoints or a codepoint or multiple codepoints less or larger than one-bit amount codepoints) of the DCI field of HARQ process number is used to indicate the ACK information, if the condition is satisfied or met.

[0650] In one example, one-bit (or one-bit amount of codepoints or a codepoint or multiple codepoints less or larger than one-bit amount codepoints) of the DCI field of 1stdownlink assignment index is used to indicate the ACK information, if the condition is satisfied or met.

[0651] In one example, one-bit (or one-bit amount of codepoints or a codepoint or multiple codepoints less or larger than one-bit amount codepoints) of the DCI field of 2nddownlink assignment index is used to indicate the ACK information, if the condition is satisfied or met.

[0652] In one example, one-bit (or one-bit amount of codepoints or a codepoint or multiple codepoints less or larger than one-bit amount codepoints) of the DCI field of 3rddownlink assignment index is used to indicate the ACK information, if the condition is satisfied or met.

[0653] In one example, one-bit (or one-bit amount of codepoints or a codepoint or multiple codepoints less or larger than one-bit amount codepoints) of the DCI field of Second TPC command for scheduled PUSCH is used to indicate the ACK information, if the condition is satisfied or met.

[0654] In one example, one-bit (or one-bit amount of codepoints or a codepoint or multiple codepoints less or larger than one-bit amount codepoints) of the DCI field of SRS resource set indicator is used to indicate the ACK information, if the condition is satisfied or met.

[0655] In one example, one-bit (or one-bit amount of codepoints or a codepoint or multiple codepoints less or larger than one-bit amount codepoints) of the DCI field of SRS resource indicator is used to indicate the ACK information, if the condition is satisfied or met.

[0656] In one example, one-bit (or one-bit amount of codepoints or a codepoint or multiple codepoints less or larger than one-bit amount codepoints) of the DCI field of Second SRS resource indicator is used to indicate the ACK information, if the condition is satisfied or met.

[0657] In one example, one-bit (or one-bit amount of codepoints or a codepoint or multiple codepoints less or larger than one-bit amount codepoints) of the DCI field of Precoding information and number of layers is used to indicate the ACK information, if the condition is satisfied or met.

[0658] In one example, one-bit (or one-bit amount of codepoints or a codepoint or multiple codepoints less or larger than one-bit amount codepoints) of the DCI field of Second precoding is used to indicate the ACK information, if the condition is satisfied or met.

[0659] In one example, one-bit (or one-bit amount of codepoints or a codepoint or multiple codepoints less or larger than one-bit amount codepoints) of the DCI field of Antenna ports is used to indicate the ACK information, if the condition is satisfied or met.

[0660] In one example, one-bit (or one-bit amount of codepoints or a codepoint or multiple codepoints less or larger than one-bit amount codepoints) of the DCI field of SRS request is used to indicate the ACK information, if the condition is satisfied or met.

[0661] In one example, one-bit (or one-bit amount of codepoints or a codepoint or multiple codepoints less or larger than one-bit amount codepoints) of the DCI field of SRS offset indicator is used to indicate the ACK information, if the condition is satisfied or met.

[0662] In one example, one-bit (or one-bit amount of codepoints or a codepoint or multiple codepoints less or larger than one-bit amount codepoints) of the DCI field of cell broadcast service (CBS) transmission information is used to indicate the ACK information, if the condition is satisfied or met.

[0663] In one example, one-bit (or one-bit amount of codepoints or a codepoint or multiple codepoints less or larger than one-bit amount codepoints) of the DCI field of PTRS-DMRS association is used to indicate the ACK information, if the condition is satisfied or met.

[0664] In one example, one-bit (or one-bit amount of codepoints or a codepoint or multiple codepoints less or larger than one-bit amount codepoints) of the DCI field of Second PTRS-DMRS is used to indicate the ACK information, if the condition is satisfied or met.

[0665] In one example, one-bit (or one-bit amount of codepoints or a codepoint or multiple codepoints less or larger than one-bit amount codepoints) of the DCI field of beta_offset indicator is used to indicate the ACK information, if the condition is satisfied or met.

[0666] In one example, one-bit (or one-bit amount of codepoints or a codepoint or multiple codepoints less or larger than one-bit amount codepoints) of the DCI field of DMRS sequence initialization is used to indicate the ACK information, if the condition is satisfied or met.

[0667] In one example, one-bit (or one-bit amount of codepoints or a codepoint or multiple codepoints less or larger than one-bit amount codepoints) of the DCI field of UL-SCH indicator is used to indicate the ACK information, if the condition is satisfied or met.

[0668] In one example, one-bit (or one-bit amount of codepoints or a codepoint or multiple codepoints less or larger than one-bit amount codepoints) of the DCI field of ChannelAccess-CPext-CAPC is used to indicate the ACK information, if the condition is satisfied or met.

[0669] In one example, one-bit (or one-bit amount of codepoints or a codepoint or multiple codepoints less or larger than one-bit amount codepoints) of the DCI field of Open-loop power control parameter set indication is used to indicate the ACK information, if the condition is satisfied or met.

[0670] In one example, one-bit (or one-bit amount of codepoints or a codepoint or multiple codepoints less or larger than one-bit amount codepoints) of the DCI field of Priority indicator is used to indicate the ACK information, if the condition is satisfied or met.

[0671] In one example, one-bit (or one-bit amount of codepoints or a codepoint or multiple codepoints less or larger than one-bit amount codepoints) of the DCI field of Invalid symbol pattern indicator is used to indicate the ACK information, if the condition is satisfied or met.

[0672] In one example, one-bit (or one-bit amount of codepoints or a codepoint or multiple codepoints less or larger than one-bit amount codepoints) of the DCI field of Minimum applicable scheduling offset indicator is used to indicate the ACK information, if the condition is satisfied or met.

[0673] In one example, one-bit (or one-bit amount of codepoints or a codepoint or multiple codepoints less or larger than one-bit amount codepoints) of the DCI field of SCell dormancy indication is used to indicate the ACK information, if the condition is satisfied or met.

[0674] In one example, one-bit (or one-bit amount of codepoints or a codepoint or multiple codepoints less or larger than one-bit amount codepoints) of the DCI field of Sidelink assignment index is used to indicate the ACK information, if the condition is satisfied or met.

[0675] In one example, one-bit (or one-bit amount of codepoints or a codepoint or multiple codepoints less or larger than one-bit amount codepoints) of the DCI field of PDCCH monitoring adaptation indication is used to indicate the ACK information, if the condition is satisfied or met.

[0676] In one example, one-bit (or one-bit amount of codepoints or a codepoint or multiple codepoints less or larger than one-bit amount codepoints) of the DCI field of CSI request is used to indicate the ACK information, if the condition is satisfied or met.

[0677] - In one example, the CSI request field of the DCI includes extra 1-bit (or >1bit or <1bit) to contain the information, but the maximum payload of the CSI request is still the same, i.e., 6 bits. In this case, the maximum number of trigger states is reduced to where is the number of bits for the CSI request field determined byreportTriggerSize.

[0678] - In one example (C1), AP CSI trigger state can be configured in a manner that 1) an ID of a first CSI report is associated with a first trigger state, and 2) an ID of a first CSI report and an ID of second CSI report are associated with a second trigger stage. For example, Ap-CSI Trigger State 1 = {ID of a second CSI report}, Ap-CSI Trigger State 2 = {ID of a second CSI report + ID of a first CSI report}. In this case, when AP-CSI Trigger State 2 is triggered, the UE ( e.g., the UE 116) can determine the second CSI report based on the first CSI report, assuming the first CSI report is successfully decoded at the NW. Thus, by either indicating AP-CSI Trigger State 2 or AP-CSI Trigger State 1, the UE can assume whether the first CSI report is used to determine the second CSI report or not.

[0679] In one example, NACK information can be indicated via codepoints that are not used for ACK.

[0680] Regarding example (C1), in another example on how to configure CSI trigger state with ACK (a first hypothesis) or NACK (a second hypothesis), a new 1-bit RRC parameter is introduced / specified per CSI trigger state (e.g.,CSI-AperiodicTriggerState or e.g., CSI-AssociatedReportConfigInfo). In other words, if explained along with example (C1), a trigger state with an ID of a second CSI report of (C1) corresponds to a trigger state of a second CSI report configured with 1-bit RRC parameter 'enabled' (or a state) and a trigger state with {an ID of a second CSI report + ID of a first CSI report} corresponds to a trigger state of the second CSI report configured with 1-bit RRC parameter 'disabled' (or the other state).

[0681] For example, the configured CSI trigger state with the 1-bit RRC parameter 'enabled' (or a state) can be regarded as CSI reporting performed with / under ACK (or a first hypothesis), and the configured CSI trigger state with the 1-bit RRC parameter 'disabled (or the other state) can be regarded as CSI reporting performed with / under NACK (or a second hypothesis).

[0682] For example, the configured CSI trigger state with the 1-bit RRC parameter 'enabled' (or a state) can be regarded as CSI reporting performed with / under NACK (or a second hypothesis), and the configured CSI trigger state with the 1-bit RRC parameter 'disabled (or the other state) can be regarded as CSI reporting performed with / under ACK (or a first hypothesis).

[0683] In one example, for codepoints of the CSI request field, the codepoints includes codepoints associated with trigger states configured with the 1-bit RRC parameters with a state, and codepoints associated with trigger states configured with the 1-bit RRC parameters with the other state. In this case, when a trigger state of the CSI request field is triggered via DCI, the UE computes / reports the CSI with / under ACK (a first hypothesis) or NACK (a second hypothesis) depending on the configuration (i.e., along with the 1bit RRC parameters).

[0684] In one embodiment, the ACK information is indicated via an existing DCI field with an extra / additional 1-bit or additional codepoint(s), a via new DCI field with at least one bit / codepoint for the ACK. In one example, the existing DCI field can be at least one of the following DCI field: Carrier indicator, DFI flag, HARQ-ACK bitmap, TPC command for scheduled PUSCH, UL / SUL indicator, Bandwidth part indicator, Frequency domain resource assignment, Time domain resource assignment, Frequency hopping flag, Modulation and coding scheme, New data indicator, Redundancy version, Transform precoder indicator, HARQ process number, 1stdownlink assignment index, 2nddownlink assignment index, 3rddownlink assignment index, Second TPC command for scheduled PUSCH, SRS resource set indicator, SRS resource indicator, Second SRS resource indicator, Precoding information and number of layers, Second precoding information, Antenna ports, SRS request, SRS offset indicator, CBG transmission information, PTRS-DMRS association, Second PTRS-DMRS, beta_offset indicator, DMRS sequence initialization, UL-SCH indicator, ChannelAccess-CPext-CAPC, Open-loop power control parameter set indication, Priority indicator, Invalid symbol pattern indicator, Minimum applicable scheduling offset indicator, SCell dormancy indication, Sidelink assignment index, PDCCH monitoring adaptation indication, CSI request.

[0685] In one example, this extra / additional bit / codepoint is present (in a second DCI triggering the second CSI report) only when the first CSI report has been triggered by NW (a first DCI) and reported by UE, i.e., the first CSI report has been triggered / reported in an earlier slot.

[0686] In one embodiment, an extra bit / additional bit or additional codepoint(s) of an existing DCI field (that may be used or may not be used when requesting / triggering the (second) CSI report) is used to indicate the ACK information if a condition is satisfied or met. In one example, the condition can be according to at least one of the following examples.

[0687] - In one example, the condition includes that a linkage between the two reports is configured (e.g., via higher-layer IElinkedCJTCReport).

[0688] - In one example, the condition includes that a linkage between the two reports is configured (e.g., via higher-layer IElinkedCJTCReport) and separate triggering for the two reports is configured (e.g., via higher-layer IEseparateTriggering).

[0689] - In one example, the condition includes that separate triggering for the two reports is configured (e.g., via higher-layer IEseparateTriggering).

[0690] In one example, an extra bit / additional bit or additional codepoint(s) of an existing DCI field can be used to indicate the ACK information, according to at least one of the following examples.

[0691] In one example, an extra bit / additional bit or additional codepoint(s) of the DCI field of Carrier indicator is used to indicate the ACK information, if the condition is satisfied or met.

[0692] In one example, an extra bit / additional bit or additional codepoint(s) of the DCI field of DFI flag is used to indicate the ACK information, if the condition is satisfied or met.

[0693] In one example, an extra bit / additional bit or additional codepoint(s) of the DCI field of HARQ-ACK bitmap is used to indicate the ACK information, if the condition is satisfied or met.

[0694] In one example, an extra bit / additional bit or additional codepoint(s) of the DCI field of TPC command for scheduled PUSCH is used to indicate the ACK information, if the condition is satisfied or met.

[0695] In one example, an extra bit / additional bit or additional codepoint(s) of the DCI field of UL / SUL indicator is used to indicate the ACK information, if the condition is satisfied or met.

[0696] In one example, an extra bit / additional bit or additional codepoint(s) of the DCI field of Bandwidth part indicator is used to indicate the ACK information, if the condition is satisfied or met.

[0697] In one example, an extra bit / additional bit or additional codepoint(s) of the DCI field of Frequency domain resource assignment is used to indicate the ACK information, if the condition is satisfied or met.

[0698] In one example, an extra bit / additional bit or additional codepoint(s) of the DCI field of Time domain resource assignment is used to indicate the ACK information, if the condition is satisfied or met.

[0699] In one example, an extra bit / additional bit or additional codepoint(s) of the DCI field of Frequency hopping flag is used to indicate the ACK information, if the condition is satisfied or met.

[0700] In one example, an extra bit / additional bit or additional codepoint(s) of the DCI field of Modulation and coding scheme is used to indicate the ACK information, if the condition is satisfied or met.

[0701] In one example, an extra bit / additional bit or additional codepoint(s) of the DCI field of New data indicator is used to indicate the ACK information, if the condition is satisfied or met.

[0702] In one example, an extra bit / additional bit or additional codepoint(s) of the DCI field of Redundancy version is used to indicate the ACK information, if the condition is satisfied or met.

[0703] In one example, an extra bit / additional bit or additional codepoint(s) of the DCI field of Transform precoder indicator is used to indicate the ACK information, if the condition is satisfied or met.

[0704] In one example, an extra bit / additional bit or additional codepoint(s) of the DCI field of HARQ process number is used to indicate the ACK information, if the condition is satisfied or met.

[0705] In one example, an extra bit / additional bit or additional codepoint(s) of the DCI field of 1stdownlink assignment index is used to indicate the ACK information, if the condition is satisfied or met.

[0706] In one example, an extra bit / additional bit or additional codepoint(s) of the DCI field of 2nddownlink assignment index is used to indicate the ACK information, if the condition is satisfied or met.

[0707] In one example, an extra bit / additional bit or additional codepoint(s) of the DCI field of 3rddownlink assignment index is used to indicate the ACK information, if the condition is satisfied or met.

[0708] In one example, an extra bit / additional bit or additional codepoint(s) of the DCI field of Second TPC command for scheduled PUSCH is used to indicate the ACK information, if the condition is satisfied or met.

[0709] In one example, an extra bit / additional bit or additional codepoint(s) of the DCI field of SRS resource set indicator is used to indicate the ACK information, if the condition is satisfied or met.

[0710] In one example, an extra bit / additional bit or additional codepoint(s) of the DCI field of SRS resource indicator is used to indicate the ACK information, if the condition is satisfied or met.

[0711] In one example, an extra bit / additional bit or additional codepoint(s) of the DCI field of Second SRS resource indicator is used to indicate the ACK information, if the condition is satisfied or met.

[0712] In one example, an extra bit / additional bit or additional codepoint(s) of the DCI field of Precoding information and number of layers is used to indicate the ACK information, if the condition is satisfied or met.

[0713] In one example, an extra bit / additional bit or additional codepoint(s) of the DCI field of Second precoding is used to indicate the ACK information, if the condition is satisfied or met.

[0714] In one example, an extra bit / additional bit or additional codepoint(s) of the DCI field of Antenna ports is used to indicate the ACK information, if the condition is satisfied or met.

[0715] In one example, an extra bit / additional bit or additional codepoint(s) of the DCI field of SRS request is used to indicate the ACK information, if the condition is satisfied or met.

[0716] In one example, an extra bit / additional bit or additional codepoint(s) of the DCI field of SRS offset indicator is used to indicate the ACK information, if the condition is satisfied or met.

[0717] In one example, an extra bit / additional bit or additional codepoint(s) of the DCI field of CBS transmission information is used to indicate the ACK information, if the condition is satisfied or met.

[0718] In one example, an extra bit / additional bit or additional codepoint(s) of the DCI field of PTRS-DMRS association is used to indicate the ACK information, if the condition is satisfied or met.

[0719] In one example, an extra bit / additional bit or additional codepoint(s) of the DCI field of Second PTRS-DMRS is used to indicate the ACK information, if the condition is satisfied or met.

[0720] In one example, an extra bit / additional bit or additional codepoint(s) of the DCI field of beta_offset indicator is used to indicate the ACK information, if the condition is satisfied or met.

[0721] In one example, an extra bit / additional bit or additional codepoint(s) of the DCI field of DMRS sequence initialization is used to indicate the ACK information, if the condition is satisfied or met.

[0722] In one example, an extra bit / additional bit or additional codepoint(s) of the DCI field of UL-SCH indicator is used to indicate the ACK information, if the condition is satisfied or met.

[0723] In one example, an extra bit / additional bit or additional codepoint(s) of the DCI field of ChannelAccess-CPext-CAPC is used to indicate the ACK information, if the condition is satisfied or met.

[0724] In one example, an extra bit of the DCI field of Open-loop power control parameter set indication is used to indicate the ACK information, if the condition is satisfied or met.

[0725] In one example, an extra bit / additional bit or additional codepoint(s) the DCI field of Priority indicator is used to indicate the ACK information, if the condition is satisfied or met.

[0726] In one example, an extra bit / additional bit or additional codepoint(s) of the DCI field of Invalid symbol pattern indicator is used to indicate the ACK information, if the condition is satisfied or met.

[0727] In one example, an extra bit / additional bit or additional codepoint(s) of the DCI field of Minimum applicable scheduling offset indicator is used to indicate the ACK information, if the condition is satisfied or met.

[0728] In one example, an extra bit / additional bit or additional codepoint(s) of the DCI field of SCell dormancy indication is used to indicate the ACK information, if the condition is satisfied or met.

[0729] In one example, an extra bit / additional bit or additional codepoint(s) of the DCI field of Sidelink assignment index is used to indicate the ACK information, if the condition is satisfied or met.

[0730] In one example, an extra bit / additional bit or additional codepoint(s) of the DCI field of PDCCH monitoring adaptation indication is used to indicate the ACK information, if the condition is satisfied or met.

[0731] In one example, an extra bit / additional bit or additional codepoint(s) of the DCI field of CSI request is used to indicate the ACK information, if the condition is satisfied or met.

[0732] - In one example, the CSI request field of the DCI includes extra 1-bit (or >1bit or <1bit) to contain the information. In one example, the payload of the CSI request can be 2,3,4,5,6,or 7 bits (i.e., up to 7bits (=6+1)), which contains the bits determined byreportTriggerSizeand the extra 1-bit.

[0733] In one example, NACK information can be indicated via codepoints that are not used for ACK.

[0734] In one embodiment, a new DCI field is used to indicate the ACK information if a condition is satisfied or met. The DCI field has 1-bit payload when it is present. In one example, the condition can be according to at least one of the following examples.

[0735] - In one example, the condition includes that a linkage between the two reports is configured (e.g.,linkedCJTCReport).

[0736] - In one example, the condition includes that a linkage between the two reports is configured (e.g.,linkedCJTCReport) and separate triggering for the two reports is configured (e.g.,separateTriggering).

[0737] - In one example, the condition includes that separate triggering for the two reports is configured (e.g.,separateTriggering).

[0738] In one example, NACK information can be indicated via codepoints that are not used for ACK.

[0739] In one embodiment, the ACK information can be indicated by utilizing a combination of examples / embodiments according to one or more embodiments described herein.

[0740] In one embodiment, the ACK information can be indicated by utilizing a combination of an example according to one or more examples described herein and an example according to one or more examples described herein, where

[0741] In one example, (the case of X=1, Y=2) reserved bit(s) or reserved codepoints of one or multiple DCI fields are used to indicate the ACK information if the reserved bit(s) or reserved codepoints can be present. If the reserved bit(s) or reserved codepoints can't be present, an (or multiple) existing DCI field(s) that is not used when requesting / triggering the CSI report is used to indicate the ACK information via one bit or one-bit amount of the codepoints.

[0742] In one example, (the case of X=1, Y=3) reserved bit(s) or reserved codepoints of one or multiple DCI fields are used to indicate the ACK information if the reserved bit(s) or reserved codepoints can be present. If the reserved bit(s) or reserved codepoints can't be present, an (or multiple) existing DCI field(s) that is used when requesting / triggering the CSI report is used to indicate the ACK information via one bit or one-bit amount of the codepoints by reducing the number of the codepoints for the original purpose to a half (or 1-bit reduction).

[0743] In one example, (the case of X=1, Y=4) reserved bit(s) or reserved codepoints of one or multiple DCI fields are used to indicate the ACK information if the reserved bit(s) or reserved codepoints can be present. If the reserved bit(s) or reserved codepoints can't be present, an (or multiple) existing DCI field(s) with an extra bit or a new DCI field with 1-bit payload that can be used when requesting / triggering the CSI report is used to indicate the ACK information via the extra bit or one-bit amount of the codepoints.

[0744] In one embodiment, when NACK information (i.e., not ACK information is indicated) of a DCI for a first CSI report (according to one or more examples described herein) is indicated to the UE, the UE determines CSI report according to at least one of the following examples.

[0745] In one example, when the NACK information is indicated along with CSI request for a second CSI report, the UE determines the second CSI report without considering (i.e., not based on) the content of the first CSI report, and transmits / reports the second CSI report. In one example, the UE determines the PMI for the Rel-18 eType-II CJT CSI report not assuming the pre-compensation of delay offset or frequency offset value(s) of the first CSI report.

[0746] In one example, when the NACK information is indicated along with CSI request for a second CSI report, the UE determines the second CSI report with considering the content of the first CSI report, and transmits / report the second CSI report together with the first CSI report again (that the UE previously reported). In one example, the UE determines the PMI for the Rel-18 eType-II CJT CSI report assuming the pre-compensation of delay offset or frequency offset value(s) of the first CSI report.

[0747] In one example, when the NACK information is indicated without CSI request, the UE uses the previously-calculated first report, and reports it again. In this case, in one example, NACK information can be indicated via DCI with a small DCI format, e.g., (0_0). In one example, NACK information can be indicated via DCI with a same DCI format associated with CSI request, e.g., (0_0, 0_1, 0_2, 0_3).

[0748] In one example, when the NACK information is indicated without CSI request, the UE just receives the NACK information without any subsequent operation pertaining to the indication. In one example, the UE just understands the first CSI report that the UE previously reported is not successfully decoded at the NW.

[0749] In one example, the NACK information is indicated along with CSI request for a second CSI report, the UE determines the second CSI report with considering (i.e., based on) the content of the first CSI report (regardless of NACK / ACK). In one example, the UE determines the PMI for the Rel-18 eType-II CJT CSI report assuming the pre-compensation of delay offset or frequency offset value(s) of the first CSI report.

[0750] In one example, when the NACK information is indicated along with CSI request for the first CSI report, the UE uses the previously-calculated first report, and reports it again.

[0751] In one example, when the NACK information is indicated along with CSI request for the first CSI report, depending on the UE's decision, the UE can report a new first CSI report or the previously-calculated first report again.

[0752] In one example, the NACK information is indicated along with CSI request for a second CSI report, the UE determines the second CSI report with considering (i.e., based on) the content of the first CSI report, and the first CSI report is reported (jointly) together with the second CSI report in the same PUSCH instance (like a joint-triggered case). In one example, the UE determines the PMI for the Rel-18 eType-II CJT CSI report assuming the pre-compensation of delay offset or frequency offset value(s) of the first CSI report, and both of the CSI reports are reported jointly in the same PUSCH instance.

[0753] In one example, the ACK / NACK information can be indicated only with CSI request for a second CSI report (e.g., Rel-18 CJT CSI reporting).

[0754] In one embodiment, the UE can be indicated with ACK / NACK (or hypotheses or indications) information explicitly / implicitly, (according to one or more examples described herein) to perform at least of the following examples.

[0755] In one example, when ACK information (or hypothesis 1 or indication 1) is signaled with a CSI request for the second CSI report, the UE reports the second CSI report considering (or based on) the content (at least one of the contents) of previously-reported first-CSI report.

[0756] In one example, ACK is implicitly signaled, e.g., via a CSI request for the second CSI report, which is regarded as an ACK for the first CSI report, and the UE reports the second CSI report considering (or based on) the content (at least one of the contents) of previously-reported first-CSI report.

[0757] In one example, when NACK information (or hypothesis 2 or indication 2) is signaled with a CSI request for the second CSI report, the UE ( e.g., the UE 116) reports the second CSI report without considering (or based on) the content (at least one of the contents) of previously-reported first-CSI report.

[0758] In one example, when NACK information (or hypothesis 2 or indication 2) is signaled with a CSI request for the second CSI report, the UE reports the second CSI report considering (or based on) the content (at least one of the contents) of previously-reported first-CSI report.

[0759] In one example, when NACK information (or hypothesis 2 or indication 2) is signaled with a CSI request for the second CSI report, the UE reports the second CSI report considering (or based on) the content (at least one of the contents) of previously-reported first-CSI report along with the previously reported first-CSI report.

[0760] In one example, when NACK information (or hypothesis 2 or indication 2) is signaled with a CSI request for the first CSI report, the UE reports a new first CSI report (or previously reported first-CSI report).

[0761] In one example, when NACK information (or hypothesis 2 or indication 2) is signaled without a CSI request, the UE reports previously reported first-CSI report (or reports a new first CSI report).

[0762] In one example, when NACK information (or hypothesis 2 or indication 2) is signaled without a CSI request, the UE just receives the NACK information that the previously reported first-CSI report is not successfully decoded / transmitted.

[0763] FIG. 13 illustrates an example method 1300 performed by a UE in a wireless communication system according to embodiments of the present disclosure. The method 1300 of FIG. 13 can be performed by any of the UEs 111-116 of FIG. 1, such as the UE 116 of FIG. 3, and a corresponding method can be performed by any of the BSs 101-103 of FIG. 1, such as BS 102 of FIG. 2. The method 1300 is for illustration only and other embodiments can be used without departing from the scope of the present disclosure.

[0764] The method begins with the UE receiving information related to a first and a second CSI report (1310). For example, in 1310, the information for the first CSI report indicatesNTRPCSI-RS resource sets withNTRP> 1 and a report quantity set to 'cjtc-Dd'. The information for the second CSI report indicatesNTRPCSI-RS resources, a report quantity set to 'cri-RI-PMI-CQI', and a codebook type set to 'typeII-CJT-r18'. The first CSI report is linked to the second CSI report via a RRC parameter. In various embodiments, the RRC parameter is configured based on a capability of the UE, which is an optional UE feature. In various embodiments, theNTRPCSI-RS resources are configured as aperiodic CSI-RS. In various embodiments, the CSI-RS resource sets correspond to the CSI-RS resources such that an i-th resource set index corresponds to an i-th resource index.

[0765] The UE then determines a CSI for the second CSI report based on the information (1320). In various embodiments, a CSI aperiodic trigger state is associated with the second CSI report. When a 1-bit RRC parameter is configured with 'enabled', the CSI is determined by compensating for delay offset values. The delay offset values are reported values in a latest report for the first CSI report. In one example, the 1-bit RRC parameter is included in an information element (IE) of 'CSI-AperiodicTriggerState'and the 1-bit RRC parameter is configured based on a capability of the UE. In various embodiments, when a 1-bit RRC parameter is not configured, the CSI for the second CSI report is determined independent of delay offset values. The UE then transmits the second CSI report including the CSI (1330).

[0766] FIG. 14 is a block diagram of a terminal or user equipment (UE) 1400 according to an embodiment of the disclosure.

[0767] The terminal is an electronic device capable of wireless communication, may include a User Equipment (UE), a portable phone, a smartphone, a tablet, an Internet of things (IoT) device, etc., having various form factors, and may perform wireless communication with a base station (BS) through a wireless channel.

[0768] Referring to FIG. 14, the UE 1400 may include at least one transceiver (hereinafter, referred to as simply “transceiver”) 1401, at least one processor (hereinafter, referred to as simply “processor”) 1402, and at least one memory (hereinafter, referred to as simply “memory”) 1403. According to at least one or a combination of methods corresponding to the embodiments described in the present disclosure, the transceiver 1401, the processor 1402, and the memory 1403 of the UE 1400 may operate. However, components of the UE 1400 are not limited to the exemplary components illustrated in FIG. 14. In another embodiment, the UE 1400 may further include additional components in addition to the above-mentioned components, or some components may be omitted. Further, in some embodiments, any combination of the transceiver 1401, the processor 1402, or the memory 1403 may be integrated in the form of one component. Furthermore, the UE of FIG. 14 corresponds to the UE of FIG. 1 and FIG. 3.

[0769] The transceiver 1401 may be a communication circuit or communication circuitry that enables the UE 1400 to perform wireless communication with a node or an entity of a network. For example, the transceiver 1401 may enable the UE 1400 to transmit or receive a signal to or from a BS through cellular communication, or to transmit or receive a signal to or from another UE through cellular communication. For example, the transceiver 1401 may support at least one of various cellular communication technologies including 3rd generation (3G), 4thgeneration (4G), long term evolution (LTE), 5th generation (5G) NR, 6thgeneration (6G), and various cellular wireless communication technologies supported by the transceiver (1401) may include all subsequent generations of evolved wireless communications.

[0770] According to an embodiment, the UE 1400 may include a plurality of transceivers. For example, in the case of supporting evolved-universal terrestrial radio access-new radio (E-UTRA-NR) sual connectivity (EN-DC), the UE 1400 may include a first transceiver supporting the 4G LTE wireless communication and a second transceiver supporting the 5G NR wireless communication. According to another embodiment, in the case of supporting NR-dual connectivity (NR-DC), the UE 1400 may include a plurality of transceivers supporting the 5G NR wireless communication. According to still another embodiment, in the case of supporting near field wireless communication, the UE 1400 may separately include a transceiver supporting at least one standard in the group of wireless communication protocol standards as defined in the protocol standards for Bluetooth®, wireless local area network (WLAN) network (including institute of electrical and electronics engineers (IEEE) 802.11-2016 standard or its amendments, e.g., 802.11ah, 802.11ad, 802.11ay, 802.11ax, 802.11az, 802.11ba, and 802.11be, without being limited thereto).

[0771] According to an embodiment, the transceiver 1401 may include various circuit structures used to transmit or receive signals to or from a BS through a wireless channel. The signals may include control information and data. For example, the transceiver 1401 may include a radio frequency (RF) transmitter for up-converting and amplifying the frequency of a transmitted signal and an RF receiver for low-noise-amplifying a received signal and down-converting the frequency thereof. The transceiver 1401 may output a signal received through a wireless channel to the processor 1402 and may transmit, through a wireless channel, a signal output from the processor 1402.

[0772] The processor 1402 may control general operations of the UE 1400 according to embodiments of the disclosure. The processor 1402 may be implemented by one or more integrated circuit (or circuitry) (IC) chips and may execute various data processings. The processor 1402 may include at least one electric circuit, and may execute instructions (or a program, codes, data, etc.) stored in the memory 1403, individually, collectively or in any combination thereof. Further, the processor 1402 may include a single-core processor or multi-core processor, and may include a processor assembly including a plurality of processing circuits (circuitry) according to a specific implementation scheme.

[0773] The processor 1402 may be electrically, operatively, or communicatively coupled to the transceiver 1401 to control the transceiver 1401.

[0774] The processor 1402 may include at least one processor (or processing circuitry), and the at least one processor may perform the following operations individually, collectively or in any combination thereof. For example, the processor 1402 may include a communication processor (CP) configured to control communication operations and an application processor (AP) configured to control execution of an upper layer (for example, an application layer) . In a specific embodiment, at least a part of the processor 1402 may be included in one chip and the other part of the processor 1402 may be included in another chip. Otherwise, at least one processor may be included in another component, for example, the transceiver 1401 or the memory 1403.

[0775] The processor 1402 may perform or control or cause an operation of the UE 1400 for executing at least one or a combination of methods according to embodiments of the disclosure. For example, the processor 1402 may control operations of the UE 1400 for processing a downlink signal received from a BS or generating and transmitting an uplink signal to a BS. To this end, the processor 1402 may execute a computer program, codes, or instructions stored in the memory 1403, so as to control other components of the UE 1400 to enable execution of various operations.

[0776] The memory 1403 corresponds to a hardware storage device capable of temporarily or permanently storing information and may include one or more storage media. For example, the memory 1403 may include a memory assembly including one or more storage media. For example, the one or more storage media may include permanent memory, such as a hard drive, flash memory, or read-only memory (ROM), semipermanent memory, such as random access memory (RAM), cache memory, or a combination thereof.

[0777] The memory 1403 may be electrically, operatively, or communicatively coupled to the processor 1402 and may be accessed by the processor 1402.

[0778] The memory 1403 may store a computer program, codes, or instructions executable by the processor 1402. According to an embodiment, a computer program, codes, or instructions executable by the processor 1402 may be either stored in a single memory device or separated and distributedly stored in two or more memory devices. By executing the instructions stored in the memory 1403, the processor 1402 may perform various functions according to an embodiment of the disclosure.

[0779] According to an embodiment of the disclosure, operations of the UE 1400 may be caused to be performed based on execution of instructions (or a computer program or codes) stored in the memory 1403 by at least one processor (or processing circuitry) configured to execute the same individually, collectively, or in any combination thereof, based on processing circuitry that is not configured to execute instructions, and / or based on components of processing circuitry that is not configured to execute instructions.

[0780] FIG. 15 is a block diagram of a base station (BS) 1500 according to an embodiment of the disclosure.

[0781] The BS 1500 may perform wireless communication with at least one user equipment (UE) located within the area of the BS 1500 through a wireless channel.

[0782] Referring to FIG. 15, the BS 1500 may include at least one transceiver (hereinafter, referred to as simply “transceiver”) 1501, at least one processor (hereinafter, referred to as simply “processor”) 1502, and at least one memory (hereinafter, referred to as simply “memory”) 1503. According to at least one or a combination of methods corresponding to the embodiments described in the present disclosure, the transceiver 1501, the processor 1502, and the memory 1503 of the BS 1500 may operate. However, components of the BS 1500 are not limited to the exemplary components illustrated in FIG. 15. In another embodiment, the BS 1500 may further include additional components in addition to the above-mentioned components, or some components may be omitted. Further, in some embodiments, any combination of the transceiver 1501, the processor 1502, or the memory 1503 may be integrated in the form of one component. Furthermore, the BS of FIG. 15 corresponds to the UE of FIG. 1 and FIG. 2.

[0783] The transceiver 1501 may be a communication circuit or communication circuitry that enables the BS 1500 to perform wireless communication with a node or an entity of a network. For example, the transceiver 1501 may enable the BS 1500 to transmit or receive a signal to or from the UE X00 through cellular communication, or to transmit or receive a signal to or from another network entity through wireless communication. For example, the transceiver 1501 may support various cellular communication technologies including 3rd generation (3G), 4thgeneration (4G), long term evolution (LTE), 5th generation (5G) NR, 6thgeneration (6G), and various cellular wireless communication technologies supported by the transceiver (1501) may include all subsequent generations of evolved wireless communications.. According to an embodiment, the transceiver 1501 may include various circuit structures used to transmit or receive signals to or from a UE through a wireless channel. The signals may include control information and data. For example, the transceiver 1501 may include a radio frequency (RF) transmitter for up-converting and amplifying the frequency of a transmitted signal and an RF receiver for low-noise-amplifying a received signal and down-converting the frequency thereof. The transceiver 1501 may output a signal received through a wireless channel to the processor 1502 and may transmit, through a wireless channel, a signal output from the processor 1502.

[0784] Meanwhile, according to an embodiment of the present disclosure, the BS 1500 may perform communication with a node or an entity of a network through wired or wireless communication. For example, the BS 1500 may perform wired or wireless communication with an adjacent BS, or a node or an entity of a core network through a backhaul network. Although not illustrated in FIG. 15, when the BS 1500 performs wired communication, the BS 1500 may further include a separate network interface for wired communication in addition to the transceiver 1501. The network interface may be referred to as network interface circuitry or communication interface circuitry.

[0785] The processor 1502 may control general operations of the BS 1500 according to embodiments of the disclosure. The processor 1502 may be implemented by one or more integrated circuit (or circuitry) (IC) chips and may execute various data processings. The processor 1502 may include at least one electric circuit, and may execute instructions (or a program, codes, data, etc.) stored in the memory 1503, individually, collectively or in any combination thereof. Further, the processor 1502 may include a single-core processor or multi-core processor, and may include a processor assembly including a plurality of processing circuits (circuitry) according to a specific implementation scheme.

[0786] The processor 1502 may be electrically, operatively, or communicatively coupled to the transceiver 1501 to control the transceiver 1501.

[0787] The processor 1502 may include at least one processor (or processing circuitry), and the at least one processor may perform the following operations individually, collectively or in any combination thereof. In a specific embodiment, at least a part of the processor 1502 may be included in one chip and the other part of the processor 1502 may be included in another chip. Otherwise, at least one processor may be included in another component, for example, the transceiver 1501 or the memory 1503.

[0788] The processor 1502 may perform or control or cause an operation of the BS 1500 for executing at least one or a combination of methods according to embodiments of the disclosure. For example, the processor 1502 may control operations of the BS 1500 for generating and transmitting a downlink signal to a UE or processing an uplink signal received from a UE. Otherwise, the BS 1500 may transmit or receive a signal to or from a neighboring BS, transfer a signal received from a UE to an upper node of the network, or transmit a signal transferred from an upper node of the network to a UE. To this end, the processor 1502 may execute a computer program, codes, or instructions stored in the memory 1503, so as to control other components of the BS 1500 to enable execution of various operations.

[0789] The memory 1503 corresponds to a hardware storage device capable of temporarily or permanently storing information and may include one or more storage media. For example, the memory 1503 may include a memory assembly including one or more storage media. For example, the one or more storage media may include permanent memory, such as a hard drive, flash memory, or read-only memory (ROM), semipermanent memory, such as random access memory (RAM), cache memory, or a combination thereof.

[0790] The memory 1503 may be electrically, operatively, or communicatively coupled to the processor 1502 and may be accessed by the processor 1502.

[0791] The memory 1503 may store a computer program, codes, or instructions executable by the processor 1502. According to an embodiment, a computer program, codes, or instructions executable by the processor 1502 may be either stored in a single memory device or separated and distributedly stored in two or more memory devices. By executing the instructions stored in the memory 1503, the processor 1502 may perform various functions according to an embodiment of the disclosure.

[0792] According to an embodiment of the disclosure, operations of the BS 1500 may be caused to be performed based on execution of instructions (or a computer program or codes) stored in the memory 1503 by at least one processor (or processing circuitry) configured to execute the same individually, collectively, or in any combination thereof, based on processing circuitry that is not configured to execute instructions, and / or based on components of processing circuitry that is not configured to execute instructions.

[0793] The UE or the base station may perform various communication procedures related to the control plane or the user plane by cooperating with one or more network entities based on wireless communication. For example, the UE may communicate with network entity such as an Access and Mobility Management Function (AMF) or a Session Management Function (SMF) via the base station, or the base station may perform at least one communication procedure by directly transmitting and receiving signals to / from, or relaying signals between, the network entities.

[0794] The structure of the above-described network entity will be described in more detail with reference to the drawings.

[0795] FIG. 16 is a block diagram of a network entity 1600 according to an embodiment of the disclosure.

[0796] The network entity 1600 may include an entity (apparatus, device, or server, etc.) that performs one or more network functions (NFs) or a part of a network function constituting a core network (e.g., a 5th generation (5G) core (5GC)) in a communication system. In this case, multiple NFs may be implemented within a single network entity, or a single NF may be distributed and implemented across a plurality of network entities. In addition, when an NF is implemented within the network entity, the NF may be implemented in the form of software, and in such a case, a program for operating the NF may be stored in memory of the network entity 1600.

[0797] A single NF may be implemented by one or more instances, which may be deployed on the same network entity or distributed across multiple network entities to operate. The instance may be a software unit that logically executes a specific network function, and may be implemented in a form that is decoupled from physical hardware resources. Further, one or more NFs may be implemented in the form of one network slice to operate to satisfy specifications required by a particular service.

[0798] The NF may include at least one of an access and mobility management function (AMF), a session management function (SMF), a local session management function (L-SMF), a user plane function (UPF), a local user plane function (L-UPF), a policy control function (PCF), a unified data management (UDM), a unified data repository (UDR), a network exposure function (NEF), a network repository function (NRF), an application function (AF), a network slice selection function (NSSF), a network data analytics function (NWDAF), a network slice admission control function (NSACF), an authentication server function (AUSF), or a data network (DN).

[0799] Referring to FIG. 16, the network entity 1600 may include at least one network interface 1601, at least one processor 1602 (hereinafter, “processor”), and at least one memory 1603 (hereinafter, “memory”). As described above, a NF may be implemented in the form of a physical device such as the network entity 1600, or may be virtualized and executed in the form of an instance. When implemented as an instance, the NF need not necessarily include physical components as illustrated in FIG. 16. In such a case, the instance may be logically represented as comprising one or more logical functional elements. Furthermore, the network entity of FIG. 16 corresponds to a network entity in the network of FIG. 1.

[0800] According to at least one or a combination of methods corresponding to the embodiments described in the present disclosure, the network interface 1601, the processor 1602, and the memory 1603 of the network entity 1600 may operate. However, components of the network entity 1600 are not limited to the exemplary components illustrated in FIG. 16. In another embodiment, the network entity 1600 may further include additional components in addition to the above-mentioned components, or some components may be omitted. Further, in an embodiment, the network interface 1601, the processor 1602, or the memory 1603 may be integrated in the form of one component.

[0801] The network interface 1601 is a collective term for a transmitter part of the network entity 1600 and a receiver part of the network entity 1600, and may be a communication circuit for transmitting or receiving a signal to or from a user equipment (UE), a base station (BS), or another network entity. Here, the communication circuit may include both a communication circuit for wireless communication and a communication circuit for a wired communication. For example, the network interface 1601 may include a circuit, logic, hardware, etc., configured to exchange a control plane message or a user plane message with a UE, a BS, or other core network entities through wireless communication or wired communication. The network interface 1601 may operate using various protocols (e.g., non-access stratum (NAS) protocol). The network interface 1601 may also be referred to, for convenience of description or depending on implementation, as communication circuitry, network interface circuitry, or a communication interface circuitry.

[0802] The processor 1602 may control general operations of the network entity 1600 according to embodiments of the disclosure. The processor 1602 may be implemented by one or more integrated circuit (or circuitry) (IC) chips and may execute various data processings. The processor 1602 may include at least one electric circuit, and may execute instructions (or a program, codes, data, etc.) stored in the memory 1603, individually, collectively or in any combination thereof. Further, the processor 1602 may include a single-core processor or multi-core processor, and may include a processor assembly including a plurality of processing circuits (circuitry) according to a specific implementation scheme. Further, it should be noted that, according to another embodiment, in a case where NF is implemented in the form of an instance, the network function may be not necessarily configured by physical hardware.

[0803] According to an embodiment, the processor 1602 may be electrically, operatively, or communicatively coupled to the network interface 1601 to control the network interface 1601.

[0804] The processor 1602 may include at least one processor (or processing circuitry), and the at least one processor may perform the following operations individually, collectively or in any combination thereof. In a specific embodiment, at least a part of the processor 1602 may be included in one chip and the other part of the processor 1602 may be included in another chip. Otherwise, at least one processor may be included in another component, for example, the network interface 1601 or the memory 1603.

[0805] The processor 1602 may perform or control or cause an operation of the network entity 1600 for executing at least one or a combination of methods according to embodiments of the disclosure. For example, the processor 1602 may control operations of the network entity 1600 for exchanging a control plane message or a user plane message with a UE, a BS, or other core network entities through wireless or wired communication, using various protocols (e.g., NAS protocol). To this end, the processor 1602 may execute a computer program, codes, or instructions stored in the memory 1603, so as to control other components of the network entity 1600 to enable execution of various operations.

[0806] The memory 1603 corresponds to a hardware storage device capable of temporarily or permanently storing information and may include one or more storage media. For example, the memory 1603 may include a memory assembly including one or more storage media. For example, the one or more storage media may include permanent memory, such as a hard drive, flash memory, or read-only memory (ROM), semipermanent memory, such as random access memory (RAM), cache memory, or a combination thereof.

[0807] The memory 1603 may be electrically, operatively, or communicatively coupled to the processor 1602 and may be accessed by the processor 1602.

[0808] The memory 1603 may store a computer program, codes, or instructions executable by the processor 1602. According to an embodiment, a computer program, codes, or instructions executable by the processor 1602 may be either stored in a single memory device or separated and distributedly stored in two or more memory devices. By executing the instructions stored in the memory 1603, the processor 1602 may perform various functions according to an embodiment of the disclosure.

[0809] According to an embodiment of the disclosure, operations of the network entity 1600 may be caused to be performed based on execution of instructions (or a computer program or codes) stored in the memory 1603 by at least one processor (or processing circuitry) configured to execute the same individually, collectively, or in any combination thereof, based on processing circuitry that is not configured to execute instructions, and / or based on components of processing circuitry that is not configured to execute instructions.

[0810] Any of the above variation embodiments can be utilized independently or in combination with at least one other variation embodiment. The above flowchart(s) illustrate example methods that can be implemented in accordance with the principles of the present disclosure and various changes could be made to the methods illustrated in the flowcharts herein. For example, while shown as a series of steps, various steps in each figure could overlap, occur in parallel, occur in a different order, or occur multiple times. In another example, steps may be omitted or replaced by other steps.

[0811] Although the figures illustrate different examples of user equipment, various changes may be made to the figures. For example, the user equipment can include any number of each component in any suitable arrangement. In general, the figures do not limit the scope of the present disclosure to any particular configuration(s). Moreover, while figures illustrate operational environments in which various user equipment features disclosed in this patent document can be used, these features can be used in any other suitable system.

[0812] Although the present disclosure has been described with exemplary embodiments, various changes and modifications may be suggested to one skilled in the art. It is intended that the present disclosure encompass such changes and modifications as fall within the scope of the appended claims. None of the descriptions in this application should be read as implying that any particular element, step, or function is an essential element that must be included in the claims scope. The scope of patented subject matter is defined by the claims.

[0813] Meanwhile, although specific embodiments of the present disclosure have been described in detail, various modifications may be made without departing from the scope of the present disclosure. Therefore, the scope of the present disclosure should not be limited to the described embodiments, but should be defined by the claims and equivalents thereof.

Claims

1.A method performed by a user equipment (UE) in a wireless communication system, the method comprising:receiving, from a base station (BS), first configuration information on a first channel state information (CSI) report with a report quantity set to a cjtc-Dd and second configuration information for a second CSI report with a codebook type set to a typeII-CJT-r18, wherein the cjtc-DD represents a coherent joint transmission calibration (CJTC) of delay offset and the first configuration information includes a higher layer parameter configuring the first CSI report to be linked to the second CSI report; andreceiving, from the BS, first CSI-RS resources for the first CSI report and second CSI-RS resources for the second CSI report, wherein the number of the first CSI-RS resources and the number of the second CSI-RS resources are the same as the number of transmission and reception points (TRPs).2.The method of claim 1,wherein the second configuration information includes a report quantity set to a cri-RI-PMI-CQI,wherein the cri-RI-PMI-CQI represents a cri (CSI-reference signal (RS) reference indicator) - RI (rank indicator) - PMI (precoding matrix indicator) - CQI (channel quality indicator).3.The method of claim 1,wherein the higher layer parameter is configured based on a capability of the UE,wherein the second CSI-RS resources for the second CSI report are aperiodic,wherein indexes of the first CSI-RS resources configured for the first CSI report correspond to indexes of the second CSI-RS resources configured for the second CSI report in a sequential order.4.The method of claim 1,wherein, if the first CSI report and the second CSI report are separately triggered, the second configuration information further includes an indicator for indicating whether to perform a compensation of the delay offset for the second CSI report,wherein the delay offset is reported in a latest report for the first CSI report.5.A method performed by a base station (BS) in a wireless communication system, the method comprising:transmitting, to a user equipment (UE), first configuration information on a first channel state information (CSI) report with a report quantity set to a cjtc-Dd and second configuration information for a second CSI report with a codebook type set to a typeII-CJT-r18, wherein the cjtc-DD represents a coherent joint transmission calibration (CJTC) of delay offset and the first configuration information includes a higher layer parameter configuring the first CSI report to be linked to the second CSI report; andtransmitting, to the UE, first CSI-RS resources for the first CSI report and second CSI-RS resources for the second CSI report, wherein the number of the first CSI-RS resources and the number of the second CSI-RS resources are the same as the number of transmission and reception points (TRPs).6.The method of claim 5,wherein the second configuration information includes a report quantity set to a cri-RI-PMI-CQI,wherein the cri-RI-PMI-CQI represents a cri (CSI-reference signal (RS) reference indicator) - RI (rank indicator) - PMI (precoding matrix indicator) - CQI (channel quality indicator).7.The method of claim 5,wherein the higher layer parameter is configured based on a capability of the UE,wherein the second CSI-RS resources for the second CSI report are aperiodic,wherein indexes of the first CSI-RS resources configured for the first CSI report correspond to indexes of the second CSI-RS resources configured for the second CSI report in a sequential order.8.The method of claim 7, further comprising:wherein, if the first CSI report and the second CSI report are separately triggered, the second configuration information further includes an indicator for indicating whether to perform a compensation of the delay offset for the second CSI report,wherein the delay offset is reported in a latest report for the first CSI report.9.A user equipment (UE) comprising:at least one transceiver;at least one processor communicatively coupled to the at least one transceiver; andat least one memory, communicatively coupled to the at least one processor, storing instructions executable by the at least one processor individually or in any combination to cause the UE to:receive, from a base station (BS), first configuration information on a first channel state information (CSI) report with a report quantity set to a cjtc-Dd and second configuration information for a second CSI report with a codebook type set to a typeII-CJT-r18, wherein the cjtc-DD represents a coherent joint transmission calibration (CJTC) of delay offset and the first configuration information includes a higher layer parameter configuring the first CSI report to be linked to the second CSI report; andreceive, from the BS, first CSI-RS resources for the first CSI report and second CSI-RS resources for the second CSI report, wherein the number of the first CSI-RS resources and the number of the second CSI-RS resources are the same as the number of transmission and reception points (TRPs).10.The UE of claim 9,wherein the second configuration information includes a report quantity set to a cri-RI-PMI-CQI,wherein the cri-RI-PMI-CQI represents a cri (CSI-reference signal (RS) reference indicator) - RI (rank indicator) - PMI (precoding matrix indicator) - CQI (channel quality indicator).11.The UE of claim 9,wherein the higher layer parameter is configured based on a capability of the UE,wherein the second CSI-RS resources for the second CSI report are aperiodic,wherein indexes of the first CSI-RS resources configured for the first CSI report correspond to indexes of the second CSI-RS resources configured for the second CSI report in a sequential order.12.The UE of claim 9,wherein, if the first CSI report and the second CSI report are separately triggered, the second configuration information further includes an indicator for indicating whether to perform a compensation of the delay offset for the second CSI report,wherein the delay offset is reported in a latest report for the first CSI report.13.A base station (BS) comprising:at least one transceiver;at least one processor communicatively coupled to the at least one transceiver; andat least one memory, communicatively coupled to the at least one processor, storing instructions executable by the at least one processor individually or in any combination to cause the BS to:transmit, to a user equipment (UE), first configuration information on a first channel state information (CSI) report with a report quantity set to a cjtc-Dd and second configuration information for a second CSI report with a codebook type set to a typeII-CJT-r18, wherein the cjtc-DD represents a coherent joint transmission calibration (CJTC) of delay offset and the first configuration information includes a higher layer parameter configuring the first CSI report to be linked to the second CSI report; andtransmit, to the UE, first CSI-RS resources for the first CSI report and second CSI-RS resources for the second CSI report, wherein the number of the first CSI-RS resources and the number of the second CSI-RS resources are the same as the number of transmission and reception points (TRPs).14.The BS of claim 13,wherein the second configuration information includes a report quantity set to a cri-RI-PMI-CQI,wherein the cri-RI-PMI-CQI represents a cri (CSI-reference signal (RS) reference indicator) - RI (rank indicator) - PMI (precoding matrix indicator) - CQI (channel quality indicator).15.The BS of claim 13,wherein the higher layer parameter is configured based on a capability of the UE,wherein the second CSI-RS resources for the second CSI report are aperiodic,wherein indexes of the first CSI-RS resources configured for the first CSI report correspond to indexes of the second CSI-RS resources configured for the second CSI report in a sequential order.

Images