UE and RAN nodes

Abstract

An exemplary embodiment of the present disclosure relates to an effective mechanism for dealing with panel-related information. In this solution, a terminal device sends a correspondence report to a network device, indicating a first correspondence between at least one first capability value set and at least one first RS. The terminal device further communicates with the network device according to a feedback status of the correspondence report, and the feedback status is ACK or NACK. Thus, misalignment between the network device and the terminal device is avoided.

Description

[Technical Field]

[0001] FIELD Exemplary embodiments of the present disclosure relate generally to the field of communications technology, and more particularly to methods, apparatus, and media for handling panel-related information. [Background technology]

[0002] To meet the increasing demand for wireless data traffic, several schemes have been proposed and implemented, with Multiple Input Multiple Output (MIMO) technology being considered as a powerful scheme for achieving high data throughput in communication systems. MIMO includes a feature that facilitates the use of multiple antenna elements in network devices (e.g., base stations, BSs) for both sub-6 GHz and above-6 GHz frequency bands.

[0003] Furthermore, it has been proposed that terminal equipment (e.g., user equipment) may be deployed with multiple antenna elements (sometimes referred to as panels). (registered trademark) In the IEEE 3rd-generation partnership project (3rd-generation partnership project) Release 17 (Rel-17), it is agreed that terminal devices and network devices may exchange panel-related information. Specifically, a list of capability parameter sets (sometimes referred to as "UE#" or "capability value sets") may be reported to the network device. It is also proposed that the terminal device transmits a correspondence report (e.g., a beam report) to the network device indicating the correspondence between each reported reference signal (RS) index and one of the capability parameter sets in the reported list, so that the terminal device can perform a user equipment (UE)-initiated panel activation and selection procedure. However, further details for handling panel-related information (e.g., configuration, reporting, and feedback) still need to be explained. Summary of the Invention [Problem to be solved by the invention]

[0004] Overall, the exemplary embodiments of the present disclosure provide a solution for handling panel-related information. Non-claimed embodiments (if any) are to be construed as examples useful for understanding various embodiments of the present disclosure. [Means for solving the problem]

[0005] In a first aspect, a method of communication is provided, the method including: transmitting, in a terminal device, a correspondence report indicating a first correspondence between at least one first capability value set and at least one first RS to a network device; and communicating with the network device according to a feedback status of the correspondence report, the feedback status being one of an acknowledgement (ACK) or a negative-acknowledgement (NACK).

[0006] In a second aspect, a method of communication is provided, the method including performing, in a terminal device, at least one of: determining a default capability value set; and performing initial transmission with a network device by applying the default capability value set; or, if a fallback condition is met, falling back to applying the default capability value set after sending a correspondence report to the network device, wherein the correspondence report indicates a correspondence between a capability value set and an RS to the network device.

[0007] In a third aspect, a method of communication is provided, the method including: receiving, in a network device, a correspondence report from a terminal device, the correspondence report indicating a first correspondence between at least one first capability value set and at least one first RS; and communicating with the terminal device according to a feedback status of the correspondence report, the feedback status being one of ACK or NACK.

[0008] In a fourth aspect, a method of communication is provided, the method including performing, in a network device, at least one of: determining a default capability value set; and performing initial transmission with a terminal device by applying the default capability value set; or, if a fallback condition is met, falling back to applying the default capability value set after receiving a correspondence report from the terminal device, the correspondence report indicating a correspondence between a capability value set and an RS from the terminal device.

[0009] In a fifth aspect, there is provided a terminal device comprising: a processing unit; and a memory coupled to the processing unit and storing instructions, the instructions, when executed by the processing unit, causing the terminal device to perform the method of the first aspect.

[0010] In a sixth aspect, there is provided a terminal device comprising: a processing unit; and a memory coupled to the processing unit and storing instructions, the instructions, when executed by the processing unit, causing the terminal device to perform the method of the second aspect.

[0011] In a seventh aspect, there is provided a network device comprising: a processing unit; and a memory coupled to the processing unit and storing instructions, the instructions, when executed by the processing unit, causing the terminal device to perform the method of the third aspect.

[0012] In an eighth aspect, there is provided a network device comprising: a processing unit; and a memory coupled to the processing unit and storing instructions, the instructions, when executed by the processing unit, causing the terminal device to perform the method of the fourth aspect.

[0013] In a ninth aspect, there is provided a computer-readable medium storing instructions which, when executed on at least one processor, cause the at least one processor to perform a method according to any one of the first to fourth aspects above.

[0014] It should be understood that this Summary of the Invention is not intended to identify key or essential features of the embodiments of the present disclosure, nor to limit the scope of the present disclosure. Other features of the present disclosure will be readily apparent from the following description. [Brief explanation of the drawings]

[0015] The above and other objects, features and advantages of the present disclosure will become more apparent from the following detailed description of some exemplary embodiments of the present disclosure in the accompanying drawings.

[0016] [Figure 1] FIG. 1 shows an interaction timing 100 between a network device and a terminal device in a related solution.

[0017] [Figure 2] FIG. 1 illustrates an exemplary communication environment in which exemplary embodiments of the present disclosure may be implemented.

[0018] [Figure 3] FIG. 1 is a signaling diagram illustrating a process for communication in accordance with some embodiments of the present disclosure.

[0019] [Figure 4] FIG. 10 illustrates an exemplary interaction timing, in accordance with some embodiments of the present disclosure.

[0020] [Figure 5] FIG. 10 illustrates an exemplary interaction timing, in accordance with some embodiments of the present disclosure.

[0021] [Figure 6A]FIG. 10 illustrates an exemplary interaction timing, in accordance with some embodiments of the present disclosure. [Figure 6B] FIG. 10 illustrates an exemplary interaction timing, in accordance with some embodiments of the present disclosure.

[0022] [Figure 7] FIG. 1 illustrates an exemplary method performed by a terminal device, according to some embodiments of the present disclosure.

[0023] [Figure 8] FIG. 1 illustrates an exemplary method performed by a terminal device, according to some embodiments of the present disclosure.

[0024] [Figure 9] FIG. 2 illustrates an exemplary method performed by a network device, in accordance with some embodiments of the present disclosure.

[0025] [Figure 10] FIG. 2 illustrates an exemplary method performed by a network device, in accordance with some embodiments of the present disclosure.

[0026] [Figure 11] FIG. 1 is a schematic block diagram of a device suitable for implementing exemplary embodiments of the present disclosure.

[0027] In the drawings, the same or similar reference numbers represent the same or similar elements. DETAILED DESCRIPTION OF THE INVENTION

[0028] The principles of the present disclosure will now be described with reference to some exemplary embodiments. It should be understood that these embodiments are provided for illustrative purposes only to aid those skilled in the art in understanding and practicing the present disclosure, and do not imply any limitation on the scope of the present disclosure. The embodiments described herein can be implemented in various ways different from those described below.

[0029] In the following description and claims, unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure pertains.

[0030] References in this disclosure to "one embodiment," "embodiment," "exemplary embodiment," etc., indicate that the described embodiment may include a particular feature, structure, or characteristic, but do not necessarily mean that each embodiment includes the particular feature, structure, or characteristic. Moreover, such phrases do not necessarily refer to the same embodiment. Furthermore, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is believed to be within the knowledge of one of ordinary skill in the art to affect such feature, structure, or characteristic in connection with other embodiments, whether or not explicitly described.

[0031] While the terms "first," "second," and the like may be used herein to describe various elements, it should be understood that these elements should not be limited by these terms. These terms are used only to distinguish one element from another. For example, a first element may be termed a second element, and similarly, a second element may be termed a first element, without departing from the scope of the exemplary embodiments. As used herein, the term "and / or" includes any and all combinations of one or more of the listed terms.

[0032] The terminology used herein is used only for the purpose of describing particular embodiments and is not intended to limit example embodiments. As used herein, the singular forms "a," "an," and "said" include the plural forms unless the context clearly indicates otherwise. It should be further understood that, as used herein, the terms "comprise," "include," "have," "comprise," "comprises," and / or "have" specify the presence of stated features, elements, and / or components, etc., but do not exclude the presence or addition of one or more other features, elements, components, and / or combinations thereof.

[0033] In some instances, values, procedures, or devices are referred to as "best," "lowest," "highest," "minimum," "maximum," etc. It should be understood that such descriptions are intended to illustrate that choices may be made from among many functional alternatives used, and that such choices are not necessarily better, smaller, higher, or otherwise more preferred than other choices.

[0034] As used herein, the term "communications network" includes New Radio (NR), Long Term Evolution (LTE), LTE-Advanced (LTE-A), Wideband Code Division Multiple Access (WCDMA), and other communications networks. (registered trademark) The term "network" refers to a network conforming to any suitable communication standard, such as Wideband Code Division Multiple Access (Wideband Code Division Multiple Access), High-Speed ​​Packet Access (HSPA), Narrow Band Internet of Things (NB-IoT), etc. Furthermore, communication between terminal devices and network devices in a communication network may be realized according to any suitable generation of communication protocol, including, but not limited to, first generation (1G), second generation (2G), 2.5G, 2.75G, third generation (3G), fourth generation (4G), 4.5G, fifth generation (5G), 5.5G, 5G-Advanced network, or sixth generation (6G) communication protocol, and / or any other protocol currently known or developed in the future. Embodiments of the present disclosure may be applied to various communication systems. Given the rapid development of communications, there will naturally be future types of communication technologies and systems in which the present disclosure can be embodied. This should not be deemed to limit the scope of the present disclosure to only the aforementioned systems.

[0035] As used herein, the term "terminal device" refers to any device with wireless or wired communication capabilities. Examples of terminal devices include UE, personal computers, desktops, mobile phones, cellular phones, smartphones, personal digital assistants (PDAs), portable computers, tablets, wearable devices, Internet of Things (IoT) devices, Ultra-Reliable Low Latency Communications (URLLC) devices, Internet of Everything (IoE) devices, machine type communication (MTC) devices, vehicle-mounted devices for V2X communications where X stands for pedestrian, vehicle, or infrastructure / network, devices for integrated access and integrated access and backhaul (IAB), satellite- or airborne vehicles in a non-terrestrial network (NTN) including High Altitude Platforms (HAPs) which encompass satellites and Unmanned Aircraft Systems (UASs), extended reality (XR) devices including different types of reality such as augmented reality (AR), mixed reality (MR), virtual reality (VR), unmanned aerial vehicles (UAVs), which are aircraft without a human pilot and are commonly referred to as drones, high speed trains (HSTs), and the like. This includes, but is not limited to, devices on a train, image capture devices such as digital cameras, sensor gaming devices, music storage and playback devices, or internet appliances that enable wireless or wired internet access and browsing. A "terminal device" may also have "multicast / broadcast" capabilities to support public safety and mission-critical V2X applications, transparent IPv4 / IPv6 multicast distribution, IPTV, smart TV, wireless services, over-the-air software distribution, group communication, and IoT applications. It may also incorporate one or more subscriber identity modules (SIMs), known as multi-SIMs.The term "terminal equipment" may be used interchangeably with UE, mobile station, subscriber station, mobile terminal, user terminal, or wireless device.

[0036] As used herein, the term "network device" refers to a device capable of providing or hosting a cell or coverage area over which terminal devices can communicate. Examples of network devices include, but are not limited to, a satellite, an unmanned aerial systems (UAS) platform, a Node B (Node B or NB), an evolved Node B (eNode B or eNB), a next generation Node B (gNB), a transmit / receive point (TRP), a remote radio unit (RRU), a radio head (RH), a remote radio head (RRH), an IAB node, a femto node, a pico node, and a low-power node such as a reconfigurable intelligent surface (RIS).

[0037] The terminal device or network device may have artificial intelligence (AI) or machine learning capabilities, which generally include a model trained from a large amount of data collected for a specific function and can be used to predict some information.

[0038] The terminal device or network device may operate over several frequency ranges, such as FR1 (410 MHz to 7125 MHz), FR2 (24.25 GHz to 71 GHz), frequency bands greater than 100 GHz, and Terahertz (THz). It can also operate over licensed, unlicensed, and shared spectrum. The terminal device may have two or more connections with the network device under a Multi-Radio Dual Connectivity (MR-DC) application scenario. The terminal device or network device can operate in full duplex, flexible duplex, and cross-division duplex modes.

[0039] Embodiments of the present disclosure may be implemented in test equipment, such as, for example, a signal generator, a signal analyzer, a spectrum analyzer, a network analyzer, a test terminal device, a test network device, a channel emulator, and the like.

[0040] Embodiments of the present disclosure may be performed in accordance with any currently known or future developed generation of communication protocols, including, but not limited to, first generation (1G), second generation (2G), 2.5G, 2.75G, third generation (3G), fourth generation (4G), 4.5G, fifth generation (5G) communication protocols, 5.5G, 5G-Advanced networks, or sixth generation (6G) networks.

[0041] As used herein, the term "circuitry" may refer to a hardware circuit and / or a combination of a hardware circuit and software. For example, a circuit may be a combination of analog and / or digital hardware circuitry and software / firmware. As yet another example, a circuit may be any portion of a hardware processor with software, including a digital signal processor, software, and one or more memories, that cooperate to cause a device, such as a terminal device or a network device, to perform various functions. In yet another example, a circuit may be a hardware circuit and / or a processor, such as a microprocessor or portion thereof, that requires software / firmware for operation, although the software may not be present if not necessary for operation. As used herein, the term "circuitry" also includes an implementation of a hardware circuit or one or more processors only, or a hardware circuit or portion of one or more processors and its / their accompanying software and / or firmware.

[0042] As mentioned above, it is proposed that a terminal device may be deployed with multiple antenna elements (sometimes referred to as panels). Furthermore, it is agreed that the terminal device may communicate panel-related information to the network device. However, further details for handling panel-related information (e.g., configuration, reporting, and feedback) need to be explained.

[0043]

[0023] Please refer to Fig. 1, which shows an interaction timing 100 between a network device and a terminal device in a related solution. In the specific example of Fig. 1, the terminal device is configured to have two panels, Panel #1 and Panel #2 (indexed as Panel #1 and Panel #2), which correspond to UE capability value sets #1 and #2, respectively. Furthermore, UE capability value set #1 is associated with beams #1 and #2 and supports a two-port sounding reference signal (SRS), and UE capability value set #2 is associated with beams #3 and #4 and supports a four-port SRS.

[0044] In operation, the terminal device determines which beams can be used for uplink transmission for different panels, for example, by measuring downlink RS, and the terminal device may expose some of its panel capabilities and structures to the network device. As shown in Figure 1, at time T1, the terminal device may report a list of UE capability value sets (110), for example, via RRC signaling. However, it is still open as to which parameters should be included in the UE capability value sets.

[0045] Furthermore, it has been agreed that a correspondence report indicating the correspondence between each reported RS index and one of the UE capability value sets will be transmitted to the network device. As shown in Fig. 1, at time T2, the terminal device transmits a correspondence report associated with panel #2 (i.e., UE capability value set #2) to the network device (120), and transmits another correspondence report associated with panel #1 (i.e., UE capability value set #1) (130). However, the format of the correspondence report and how to configure the reporting of the correspondence report are still undecided.

[0046] Furthermore, due to complex communication environments, it is not always guaranteed that the transmission of a correspondence report will be successful. As shown in FIG. 1, the transmission of another correspondence report fails. In this case, after transmitting the other correspondence report, the terminal device may consider applying UE capability value set #1, but the network device continues to apply UE capability value set #2. Therefore, the failure to transmit the other correspondence report causes misalignment of uplink transmission capabilities between the network device and the terminal device. In the specific example of FIG. 1, after time T3, the network device may request the terminal device to transmit SRS / Physical Uplink Shared Channel (PUSCH) on four antenna ports, which cannot be supported by the terminal device. Additionally, the network device may schedule the terminal device to transmit on beams #3 and #4, but the terminal device only supports transmission on beams #1 and #2. In short, the misalignment between the network device and the terminal device prevents communication between the network device and the terminal device from continuing normally.

[0047] Therefore, a feedback mechanism for correspondence reporting appears to be needed. This can be solved by introducing a new message / signaling, including a new Radio Network Temporary Identifier (RNTI) or a new Downlink Control Information (DCI) format or field, for correspondence reporting feedback. However, introducing a new message / signaling may cause undesirable additional overhead and complexity. In this case, it is necessary to further explain how to realize the correspondence reporting feedback mechanism.

[0048] Furthermore, the correspondence report may cause a switch / change between different panels / UE capability value sets / RSs / beams. Such a switch / change needs to be coordinated between the network device and the terminal device. Therefore, the switching operation in the network device and the terminal device during the feedback procedure should also be specified in detail.

[0049] As can be seen with reference to Figure 1, during the period between time T1 and time T2, there is no correspondence report transmitted to the network device, so both the network device and the terminal device do not know which panel / UE capability value set / RS / beam should be applied. Therefore, it is also desirable to propose a solution on how to perform initial transmission between the network device and the terminal device.

[0050] Additionally, fallback procedures are usually required during communication procedures. Currently, the fallback procedures after sending the correspondence report are still open.

[0051] In addition to the above, there are still other open issues, including but not limited to whether the UE capability value set can be common across all bandwidth parts (BWPs) / component carriers (CCs) within the same band or band combination, or whether / how to perform downlink-only panel-related information reporting, how to configure the time domain behavior of correspondence reporting, etc.

[0052] Some of the embodiments solve at least some of the outstanding problems identified above. It should be understood that the above-illustrated problems are provided for illustrative purposes only and no limitations are implied. Neither these outstanding problems nor the problems solved by the present disclosure are limited to the above-illustrated problems.

[0053] Generally speaking, a panel as described herein refers to one or more antenna elements deployed in an area of ​​a terminal device, and in this regard, the terms "panel," "antenna element," "antenna array," "transmit / receive point," "TRP" (and their equivalents) may be used interchangeably.

[0054] In some embodiments, a terminal device may be configured to have a list of transmission configuration indicator (TCI) state (e.g., up to M TCI states) configurations with tci-StateId. Each TCI state includes a quasi-co-located RS (QCL) for a demodulation reference signal (DM-RS) of a physical downlink shared channel (PDSCH) and a DM-RS of a physical downlink control channel (PDCCH) within a component carrier (CC), a reference for providing a CSI-RS, and (if applicable) a reference for determining unlink TX spatial filters for dynamic grant and configured grant-based physical uplink shared channel (PUSCH) and physical uplink control channel (PUCCH) resources, and parameters for providing an SRS. The quasi-co-located relationship is configured by the higher layer parameter qcl-Type1 of the first RS and (if configured) the qcl-Type2 of the second RS. The quasi-co-location type corresponding to each DL RS is given by the higher layer parameter qcl-Type in QCL-Info and can be one of the following values: - "typeA": {Doppler shift, Doppler spread, average delay, delay spread} - "type B": {Doppler shift, Doppler spread} - "typeC": {Doppler shift, average delay} - "typeD": {spatial receiving parameters}

[0055] The terms "TCI", "TCI state", "TCI identity", "TCI ID", and "TCI state ID" may be used interchangeably.

[0056] The terms "capability parameter set," "capability value set," and "UE capability value set" may be used interchangeably.

[0057] Additionally, in this specification, the terms "CC identity / index," "cell identity / index," and "serving cell identity / index" (and their equivalents) may be used interchangeably.

[0058] In some embodiments, the terms "RS," "beam," "set of QCL parameters," "TCI state," "QCL type," "QCL type D," "spatial receive parameters," "spatial domain parameters," "spatial domain filter," "spatial domain transmit filter," "spatial domain receive filter," "spatial receive parameters," and "spatial relationship information" have similar meanings and may be used interchangeably.

[0059] In some embodiments, a panel / capability set may refer to a downlink panel / capability set, an uplink panel / capability set, a panel / capability set with a reserved / specific state, a panel / capability set type, a panel / capability set state, an RS resource, an RS resource set, an antenna port, an antenna port group, a beam, or a beam group.

[0060] In some embodiments, the panel identity information may refer to a panel index / identity, a downlink panel index / identity, an uplink panel index / identity, a panel type indication, a panel state indication, a capability value set index, an RS resource set index / identity, an antenna port index / identity, an antenna port group index / identity, or a beam group index / identity. Example environment

[0061] FIG. 2 illustrates an exemplary communications environment 200 in which exemplary embodiments of the present disclosure may be practiced.

[0062] Communication environment 200 includes network device 210 and terminal device 220, and network device 210 is capable of communicating with terminal device 220 via a physical communication channel or link. Additionally, network device 210 may provide more than one serving area. In the example of FIG. 2, network device 210 provides (serving) cell 260.

[0063] In the exemplary communication environment 200, the link from terminal device 220 to network device 210 is referred to as the uplink, and the link from network device 210 to terminal device 220 is referred to as the downlink. Furthermore, the communication environment supports MIMO such that network device 210 and terminal device 220 communicate via different beams to enable directional communication. In the downlink, network device 210 is a transmitting (TX) device (or transmitter) and terminal device 220 is a receiving (RX) device (or receiver), and network device 210 may send downlink transmissions to terminal device 220 via one or more beams. As shown in FIG. 2, network device 210 sends downlink transmissions to terminal device 210 via beams 240-1 through 240-3.

[0064] Accordingly, in the uplink, network device 210 is an RX device (or receiver), terminal device 220 is a TX device (or transmitter), and terminal device 210 may send uplink transmissions to network device 220 via one or more beams. As shown in Figure 2, terminal device 220 sends uplink transmissions to network device 210 via beams 230-1 through 230-3. For purposes of explanation, beams 230-1 through 230-3 or beams 240-1 through 240-3 will be referred to collectively or individually as beams 230 or beams 240, respectively.

[0065] Additionally, terminal device 220 may be configured with two or more panels. As shown in Figure 2, terminal device 220 is configured with panels 250-1 and 250-2. Hereinafter, panels 150-1 and 250-2 may be referred to as first panel 250-1 and second panel 250-2, respectively. In some embodiments, panels 250-1 and 250-2 may each correspond to a different set of capability parameters.

[0066] In some embodiments, a panel may be associated with one or more RSs / beams, and thus terminal device 220 may use a particular panel to transmit a directional signal to network device 210 via a particular beam associated with the RS.

[0067] In some embodiments, different panels correspond to different panel types / capability sets. For example, panels 250-1 and 250-2 may correspond to different numbers of SRS ports, frequency resources (frequency bands, CCs, beams, etc.), and any other suitable capability parameters (e.g., capability sets).

[0068] Furthermore, in the embodiment of Fig. 2, the exchange of panel-related information is supported. Specifically, in the embodiment of Fig. 2, the network device 210 and the terminal device 220 may exchange capability-related information and related settings, and the terminal device 220 may report a correspondence relationship report to the network device 210.

[0069] In some embodiments, terminal device 220 may perform UE-initiated panel activation and selection via reporting a list of UE capability value sets.

[0070] In some embodiments, one or more RSs (e.g., synchronization signal / physical broadcast channel (SS / PBCH) blocks, SSBs, sounding reference signals, SRSs, CSI-RSs, etc.) may be associated with a beam. Terminal device 220 may measure on the beams / RSs and transmit the measurement results to network device 210, for example, via a correspondence report.

[0071] In addition, the correspondence between each reported CSI-RS and / or SSB resource index and one capability parameter in the capability parameter set in the reported list is determined by the terminal device 220 / set by the network device 210 and notified to the network device 210 in the beam report instance.

[0072] In some embodiments, the index of the corresponding capability parameter is reported in the uplink control information for beam reporting together with the SSB resource indicator (RI) / CSI-RS resource indicator (CRI) and L1-RSRP / SINR pairs (up to four pairs, with 7-bit absolute values ​​and 4-bit differential values).

[0073] Additionally, terminal device 220 may report one index for all CRI / SSB RIs reported in one beam report. Alternatively, terminal device 220 may report one index for each CRI / SSB RI reported in one beam report.

[0074] In some embodiments, DL-only reporting is supported, which is described in the following text.

[0075] In some embodiments, the network device 210 provides configurations for correspondence reporting (e.g., time-domain behavior of correspondence reporting, format of correspondence reporting) and resources (e.g., physical uplink control channel (PUCCH) / physical uplink shared channel (PUSCH) resources, beams, RSs, etc.), which also indicate when, how, and where to report the correspondence report.

[0076] In some embodiments, correspondence reporting may be configured to have any suitable time-domain behavior. One example of time-domain behavior is periodic. Another example of time-domain behavior is semi-persistent. Yet another example of time-domain behavior is aperiodic.

[0077] Communications in communication environment 200 may conform to any suitable standard, including, but not limited to, Long Term Evolution (LTE), LTE-Evolution, LTE-Advanced (LTE-A), Wideband Code Division Multiple Access (WCDMA), Code Division Multiple Access (CDMA), and Global System for Mobile Communications (GSM). Furthermore, communications may be performed according to any currently known or future-developed generation of communications protocols. Examples of communications protocols include, but are not limited to, first generation (1G), second generation (2G), 2.5G, 2.75G, third generation (3G), fourth generation (4G), 4.5G, fifth generation (5G), 5.5G, 5G-Advanced networks, or sixth generation (6G) communications protocols.

[0078] It should be understood that the number of network devices, terminal devices, panels, and cells, and their interrelationships, are used for illustrative purposes only and do not imply any limitations. Communication environment 200 may include any appropriate network devices, terminal devices, panels, and cells suitable for implementing embodiments of the present disclosure. Furthermore, it should be understood that one or more additional terminal devices may be located within each cell.

[0079] It should also be understood that in some instances, communication environment 200 may include only homogeneous network deployments or only heterogeneous network deployments. Process Example

[0080] Although features / operations are described separately in particular exemplary embodiments, it should be understood that, unless expressly indicated to the contrary, these features / operations described in different exemplary embodiments may be used in any suitable combination.

[0081] Additionally, in the following description, several interactions (e.g., exchange of capability-related information, configuration, etc.) are performed between terminal device 220 and network device 210. It should be understood that the interactions may be realized in one signaling / message or multiple signaling / messages, including system information, RRC messages, DCI messages, uplink control information (UCI) messages, media access control (MAC) control elements (CEs), etc. The present disclosure is not limited in this respect.

[0082] Hereinafter, layer 1-reference signal received power (L1-RSRP) and L1 / L1-signal to interference and noise ratio (L1-SINR) are used as example signal measurements to describe certain exemplary embodiments of the present disclosure. Note that the exemplary embodiments described with respect to L1-RSRP / L1-SINR are equally applicable to other types of signal measurements, including, but not limited to, L3-RSRP, L3-SINR, L1 / L3 received signal strength indicator (RSSI), L1 / L3 reference signal received quality (RSRQ), etc. The present disclosure is not limited in this respect.

[0083] Furthermore, it should be understood that operations at the terminal device 220 and the network device 210 should be coordinated. In other words, the network device 210 and the terminal device 220 should have a common understanding of settings, states, parameters, etc. Such a common understanding may be achieved through any suitable interaction between the network device 210 and the terminal device 220, or by both the network device 210 and the terminal device 220 applying the same rules / policies. In the following, some operations are described from the perspective of the terminal device 220, but it should be understood that the corresponding operations should be performed by the network device 210. Similarly, some operations are described from the perspective of the network device 210, but it should be understood that the corresponding operations should be performed by the terminal device 220. For brevity, some identical or similar content will be omitted herein.

[0084] The principles and embodiments of the present disclosure will now be described in detail with reference to Figure 3, which shows a signaling chart illustrating a communication process 300 according to some embodiments of the present disclosure. For illustrative purposes, the process 300 will be described with reference to Figure 2. The process 300 may involve a terminal device 220 and a network device 210.

[0085] Additionally, terminal device 220 may be configured with more than one panel (e.g., panel 250-1 and panel 250-2) and support more than one capability set. Both panels and capability sets may be indexed in ascending or descending order. Exemplary Process for Exchanging Capability-Related Information

[0086] Optionally, the terminal device 220 and the network device 210 may communicate capability-related information and related settings to enable related functions according to the present disclosure, which will be described below. During this interactive procedure, certain rules for configuring and reporting correspondence reports may be defined, and related redefined / newly introduced parameters may be exchanged between the terminal device 220 and the network device 210. Additionally, the network device 210 may enable or disable related functions according to the present disclosure.

[0087] 3, terminal device 220 transmits capability-related information to network device 210 (310). According to some embodiments of the present disclosure, more fields indicating the panel capabilities of terminal device 220 are included in the capability-related information (e.g., via one or more capability reports). In this way, better alignment of panel capabilities and panel structures between network device 210 and terminal device 220 can be achieved.

[0088] Additionally, capability related information and related settings may be carried in any suitable signaling / messages, including but not limited to RRC messages, DCI messages, MAC CEs, etc. In this way, existing signaling structures may be reused and updated to accommodate reporting of CSI reports associated with capability parameter sets.

[0089] In some embodiments, the capability-related information may indicate capability-related information indicating multiple capability value sets (e.g., L capability value sets, where the value of L may be a positive integer) supported by the terminal device 220.

[0090] In some embodiments, one capability value set may be associated with one or more RSs (e.g., SSB resource indicator, SSBRI, CSI-RS resource indicator, CRI), and one RS may also be associated with one or more capability value sets. In other words, the correspondence between capability value sets and RSs may be one-to-one, one-to-many, many-to-one, or many-to-many.

[0091] Furthermore, the capability value set may include multiple capability parameters. One capability parameter included in the set is the maximum number of SRS ports (represented as “Nx”). The maximum number of SRS ports Nx refers to Nx radio frequency (RF) chains for uplink transmission and Nx layers for PUSCH.

[0092] Alternatively or additionally, other ability parameters included in the set are: ● Identity information for the ability score set; ● Maximum number of SRS ports, ● Maximum number of SRS resources, ● Maximum number of SRS resource sets, ● Coherence type (e.g., fully coherent, partially coherent, noncoherent, and combinations thereof); ● Maximum number of uplink layers, ● Maximum number of downlink layers, ● Maximum number of RS (e.g. CSI-RS) ports, ● The maximum number of codewords, or ● Maximum number of MIMO layers, The parameter may be any suitable parameter, including but not limited to:

[0093] By reporting more capability parameters within each capability value set to the network device 210, the network device 210 can better understand the capabilities of the terminal device 220 and facilitate better scheduling for the terminal device 220.

[0094] Furthermore, in addition to a list of capability value sets, more capability-related information may be communicated to the network device 210, as described below.

[0095] In some embodiments, one capability value set corresponds to a panel (a physical or logical entity) deployed in terminal device 220. In other words, each capability value set corresponds to one panel. In this case, the values ​​of capability parameters included in different capability value sets may be the same.

[0096] Alternatively or additionally, in some embodiments, one capability value set may correspond to a particular panel type, where different capability value sets include different (or at least partially different) values ​​for the capability parameters. In one exemplary embodiment, panel types may be defined by the number of SRS ports they support, e.g., Type #1 corresponds to a 1-port SRS, Type #2 corresponds to a 2-port SRS, Type #3 corresponds to a 4-port SRS, etc.

[0097] Also, in some embodiments, the capability-related information indicates whether a symmetric antenna structure (i.e., a symmetric panel) or an asymmetric antenna structure (i.e., an asymmetric panel) is deployed in the terminal device. Alternatively or additionally, in some embodiments, the capability-related information indicates the respective numbers of capability value sets corresponding to each particular type of capability value set.

[0098] In one specific exemplary embodiment, the capability-related information indicates capability value set #1 (including capability values ​​for 2-port SRS) each having the number 2, which means that terminal device 220 is equipped with two panels and both panels can support 2-port SRS. In another specific exemplary embodiment, if terminal device 220 is equipped with two panels, the capability-related information indicates capability value set #2 (including capability values ​​for 4-port SRS) and a symmetric antenna structure, which means that terminal device 220 is equipped with two panels and both panels can support 4-port SRS. For brevity, other exemplary embodiments will not be described one by one.

[0099] Alternatively or additionally, in some embodiments, one set of capability scores may correspond to a particular panel state. In one exemplary embodiment, a panel state may be defined by the number of activated panels, e.g., State #1 corresponds to single-panel transmission, State #2 corresponds to two-panel simultaneous transmission, State #3 corresponds to four-panel simultaneous transmission, etc. This exemplary embodiment is particularly suited to scenarios in which multiple-panel simultaneous transmission is supported.

[0100] In one exemplary embodiment, the capability-related information further indicates an associative relationship between the plurality of capability value sets. In some embodiments, the capability-related information indicates whether one capability value of the reported capability value sets is a subset of another reported capability value set.

[0101] In one particular exemplary embodiment, the capability-related information indicates whether a reported capability value set (e.g., ID information) having a smaller value is a subset of a reported capability value set having a larger value. In other words, a reported capability value set having a larger value indicates a simultaneous multi-panel state, and a reported capability value set having a smaller value indicates a single-panel state.

[0102] For example, the capability-related information indicates capability value set #1 (including capability values ​​for 2-port SRS) and capability value set #2 (including capability values ​​for 2-port SRS), and indicates that capability value set #1 having 2-port SRS is a subset of capability value set #2 having 4-port SRS. Such capability-related information means that terminal device 220 can transmit up to 4-port SRS in simultaneous multi-panel and up to 2-port SRS in single-panel.

[0103] Alternatively or additionally, in some embodiments, the capability-related information may indicate whether terminal device 220 supports the parallel application of two or more capability value sets. Additionally, the capability-related information may further indicate the number of capability value sets supported to be parallel applied by terminal device 220. For example, the capability-related information indicates capability value set #1 (including capability values ​​for a 2-port SRS) and capability value set #2 (including capability values ​​for a 4-port SRS), and capability value sets #1 and #2 can be used simultaneously, which means that terminal device 220 can support a maximum of 6-port SRS.

[0104] Additionally, the concept of a capability value set status may be introduced. Specifically, the capability value set status may indicate whether the capability value set is used for uplink transmission or whether the capability value set is used for downlink transmission. Additionally, the capability value set status may indicate some reserved status, such as a capability value set application status indicating whether the capability value set has already been applied or will be applied. Alternatively or additionally, in some embodiments, the capability value set status may indicate whether the applied capability value set has been changed or will be changed. In one specific exemplary embodiment, the capability value set status may indicate one of the capability value set used for the uplink, the capability value set used for the downlink (i.e., for the downlink panel only / not associated with the uplink panel), the capability value set not suitable for uplink transmission (i.e., the terminal device 220 cannot use the reported capability value set for uplink transmission), whether the applied capability value set has been changed or will be changed, etc.

[0105] By incorporating the concept of capability value set status, in some embodiments, capability-related information may also indicate whether terminal device 220 supports reporting correspondence reports for downlink transmissions. Additionally, capability-related information may also indicate whether terminal device 220 supports reporting the status of reserved capability value sets.

[0106] As described above, identity information of a capability value set may be included in the capability value set, and thus the identity information may be used to identify / index the capability value set.

[0107] Furthermore, the identity information of the capability value set may be indicated either explicitly or implicitly. Specifically, the terminal device may report explicit identity information (e.g., number / index) of the capability value set to the network device 210. Alternatively, for an implicit approach, the identity information of the capability value set is not necessarily included in the capability-related information. In this case, the number / index of the associated capability value set may be implicit. In one specific exemplary embodiment, the number / index of the capability value set is determined in ascending or descending order based on the number of SRS ports associated with the capability value set. In another specific exemplary embodiment, the number / index of the capability value set is determined in ascending or descending order based on the reporting order of the capability value set.

[0108] In some embodiments, the number / index of the capability value set to be reported / determined may be represented as a bit sequence (e.g., a panel information field) in the correspondence report so that the capability value set may be indicated / reported to the network device 210. The bit size of the bit sequence included in the correspondence report is determined based on the first number, i.e., L, of capability-related parameter sets supported by the terminal device 220. Specifically, the bit size is calculated as ceil(log2(L)).

[0109] Alternatively or additionally, in some embodiments, the bit size of the bit sequence included in the correspondence report is determined based on a second number of states of the capability set supported by terminal device 220. In one particular exemplary embodiment, one or more specific indexes / identities, for example, N, may be assigned to indicate that the capability set is used for downlink, where N may be "1" or another positive integer. Considering such specific indexes, the bit size of the bit sequence included in the correspondence report may be calculated as ceil(log2(L+N)).

[0110] In another particular exemplary embodiment, one or more specific index / identity information values, e.g., M, may be assigned to indicate that a capability value set is to be used for a reserved state, where M may be "1" or other positive integer. Considering such specific indexes, the bit size of the bit sequence included in the correspondence report may be calculated as ceil(log2(L+M)).

[0111] It should be understood that such an indexing mechanism may be used to index any interaction procedure between the network device 210 and the terminal device 220, for example, a capability value set included in a correspondence report as described below.

[0112] Alternatively or additionally, in some embodiments, the capability-related information may indicate other capabilities of the terminal device 220, including, but not limited to, whether the terminal device 220 supports determining the feedback status of a correspondence relationship report, whether the terminal device 220 supports reporting the status of a capability value set, whether the terminal device 220 supports obtaining the correspondence relationship with a time limit, or the number of capability value sets included in a correspondence relationship report supported by the terminal device 220.

[0113] It should be understood that the above exemplary capability-related information is provided for illustrative purposes only and no limitation is to be implied. In some other exemplary embodiments, any suitable capability-related information may be used.

[0114] Continuing with reference to FIG. 3, the network device 210 sends 320 one or more settings to the terminal device 220.

[0115] In one exemplary embodiment, the one or more configurations may be generated based on capability-related information received from terminal device 220. In another exemplary embodiment, the measurement configurations are generated independently of the capability-related information.

[0116] In one exemplary embodiment, the one or more settings indicate an associative relationship between at least one transmission parameter and a set of capability values.

[0117] An example of a transmission parameter is a resource for transmitting an SRS, such as an SRS resource set and an SRS resource. Specifically, at least one of an SRS resource set, an SRS resource, and an SRS port may be associated with a capability value set. For example, the one or more settings associate an SRS resource set #1 with a capability value set #1, and the number of ports of the SRS resource in the SRS resource set #1 is less than the number of SRS ports reported in the capability value set #1.

[0118] Additionally, in one exemplary embodiment, terminal device 220 performs SRS transmission based on both the at least one setting and one or more capability value sets currently applied in terminal device 220. In other words, terminal device 220 is not expected to transmit all configured SRS resources, but can select SRS resources according to its current panel state (i.e., the currently applied panel).

[0119] Another example of the transmission parameter is a resource for transmitting the PUCCH. Specifically, at least one of a PUCCH resource, a PUCCH resource set, and a PUCCH resource group may be associated with a capability value set.

[0120] Other examples of transmission parameters are the TCI state and resources for transmitting the downlink RS. Specifically, the TCI state, the downlink RS resource / resource set / port may also be associated with a capability value set.

[0121] Table 1 below shows an exemplary association relationship between transmission parameters and two capability value sets. Table 1. Exemplary association relationships TIFF0007747221000001.tif85158

[0122] Alternatively or additionally, in some embodiments, the one or more settings indicate a reporting volume of the correspondence report. In other words, the network device 210 may configure the content to be included in the correspondence report. By indicating the reporting volume, the network device 210 may instruct the terminal device 220 to report panel information, such as the identification information of the capability value set, SSBRI / CRI, RSRP / SINR, associated correspondence, etc., as described above.

[0123] Alternatively or additionally, in some embodiments, the one or more settings indicate a time domain behavior of the correspondence reporting.

[0124] In one specific embodiment, the one or more settings indicate that the correspondence report is a periodic report. Additionally, the period of the correspondence report can be linked to other periodic beam reports without panel information reports. For example, the correspondence report is configured to have a first period by the at least one setting, and further, the first period is aligned with a second period of the beam report, and the first period is a multiple of the second period. In other words, if the beam report is configured to have a period T, which is N times (i.e., N*T) the period set for the beam report without panel information (e.g., SSBRI / CRI-RSRP / SINR), every N*T beam reports (SSBRI / CRI-RSRP / SINR) can be replaced with a panel information beam report (i.e., a correspondence report).

[0125] In some embodiments, semi-persistent and / or aperiodic time domain behaviors may be configured to be associated with periodic time domain behaviors. Specifically, in some embodiments, triggering of semi-persistent time domain behaviors and aperiodic time domain behaviors is conditional. In some embodiments, semi-persistent time domain behaviors and / or aperiodic time domain behaviors are triggered / enabled only if periodic time domain behaviors are configured. Additionally, in some embodiments, aperiodic time domain behaviors are triggered / enabled only if semi-persistent time domain behaviors are configured.

[0126] It should be understood that the association / setting restrictions between periodic, semi-persistent and aperiodic time-correlated reports may be indicated either in an explicit manner (e.g., indicating links between different reports) or in an implicit manner.

[0127] Alternatively or additionally, the one or more settings indicate information regarding a time limit for obtaining a correspondence report. Alternatively or additionally, the one or more settings indicate the number of capability value sets associated with one correspondence report. Other information indicated by the one or more settings may be described in the following text.

[0128] It should be understood that the above illustrated interaction procedures are provided for illustrative purposes only and do not imply any limitations. In some other embodiments, any other suitable interaction procedures may be performed. Exemplary Process for Initial Transmission

[0129] As described above, if the correspondence report is not sent to the network device 210, both the network device 210 and the terminal device 220 do not know which panel / capability value set / beam should be applied. In the following embodiment, this outstanding issue can be well addressed.

[0130] According to some embodiments of the present disclosure, the initial transmission comprises: at least a period of time between reporting a set of capability values ​​and sending said first correspondence report; the period of time between the initial access and the transmission of said first correspondence report; the period between the initial configuration and the sending of said first correspondence report; or the period between the initial setup and the sending of said first correspondence report.

[0131] It should be understood that the above time periods are given for illustrative purposes only and no limitation is implied. In some other embodiments, the initial transmission may occur within a suitable time period during which network device 210 and terminal device 220 are unaware of the transmission parameters (e.g., panel, capability value set, beam, RS, etc.). The present disclosure is not limited in this respect.

[0132] In the particular exemplary embodiment of FIG. 3, during period 370 (i.e., at least the period between reporting the capability value set and transmitting the first correspondence report), terminal device 220 and network device 210 may communicate with each other using a default capability value set 330, which may be referred to as an initial transmission.

[0133] In this way, because network device 210 and terminal device 220 have a common understanding of communication parameters (i.e., capability value set / panel), network device 210 and terminal device 220 can communicate with each other even if a correspondence relationship report has not been sent to network device 210.

[0134] The default capability parameter set may be determined by any suitable policy / rule. In one exemplary embodiment, the capability parameter set with the smallest / largest / pre-set index value may be used as the default capability parameter set. Alternatively, in another embodiment, the capability parameter set with the smallest / largest number of SRS ports may be used as the default capability parameter set. Alternatively, in another embodiment, the capability parameter set with the lower or lowest index value may be used as the default capability parameter set.

[0135] An example of a default ability score set is: ● A set of ability scores with lower abilities; ● Ability score sets with higher abilities; - the capability set with the lower capability set index; ● The ability set with the higher ability set index; ● The last used ability score set, ● A predefined set of ability scores, a set of capability values ​​set by either the terminal device 220 or the network device 210; is shown as:

[0136] It should be understood that the above-mentioned default capability value set is provided for illustrative purposes only and does not imply any limitation. In some other exemplary embodiments, any suitable policy / rule may be applied to determine the default capability parameter set. In other words, it may be any predefined rule known by both the network device 210 and the terminal device 220, or may be signaled to each other by the network device 210 / terminal device 220 via signaling (e.g., configuration / capability-related signaling).

[0137] In some embodiments, terminal device 220 transmits information about the default capability set during a random access (RA) procedure. Specifically, the information about the default capability set is carried on one physical random access channel (PRACH). In one exemplary embodiment, the information about the default capability set is included in message 3 during a four-step RA. Alternatively, in another exemplary embodiment, the information about the default capability set is included in message A during a two-step RA.

[0138] In some embodiments, network device 210 may generate a scheduling message that is generated according to a default capability set, and in response, terminal device 220 may transmit uplink transmissions to network device 220 by applying the default capability set.

[0139] In some embodiments, the scheduling message / uplink transmission is associated with an SRS transmission. Specifically, only SRS resource sets / resources / ports associated with the default capability set are scheduled / used / assumed. For example, if terminal device 220 reports two capability sets, namely, capability set #1 corresponding to SRS with up to two ports and capability set #2 corresponding to SRS with up to four ports, if the capability set with the lower capability is assumed as the default capability set, the SRS resources for four ports are not scheduled / transmitted during the initial transmission. In other words, terminal device 220 does not (or is not) expected to transmit SRS with more than two ports.

[0140] Alternatively or additionally, in some embodiments, scheduling messages / uplink transmissions are associated with PUSCH transmissions, specifically, only SRS resource sets / resources / ports associated with the default capability set are scheduled / used / assumed.

[0141] For example, if terminal device 220 reports two capability value sets, i.e., capability value set #1 corresponding to a PUSCH with up to two layers and capability value set #2 corresponding to a PUSCH with up to four layers, and if the capability value set with the lower capability is assumed as the default capability value set, then during initial transmission, network device 210 should not schedule PUSCH transmission with a layer count greater than the lower reported value (i.e., two layers), and terminal device 220 does not (or is not) expected to transmit PUSCH with more than two layers.

[0142] Additionally, in some embodiments, during initial transmission, uplink transmission / scheduling may be performed using a spatial domain transmit filter associated with the assumed RS, where the assumed RS should be associated with a default capability value set. In other words, the uplink transmit beam for SRS / PUCCH / PUSCH should be associated with a default capability value set.

[0143] Examples of possible RSs include the last PRACH beam / RS, the RS / beam used for initial access, etc.

[0144] In this way, the original transmission between the terminal device 220 and the network device 210 is well taken care of. Exemplary Process for Obtaining Correspondence Reports

[0145] The terminal device 220 may measure the signal quality of the RS, such as RSRP, SINR, coupling loss, path loss, UL transmit power, etc., which may be configured by the network device 210 or depending on the UE implementation. The terminal device 220 may then include such measurement results in a correspondence report. To select a more appropriate panel / capability value set and avoid out-of-date correspondence report issues, a time limit for obtaining the measurement results / correspondence report may be introduced.

[0146] As previously mentioned, capability-related information and settings regarding time limits may be exchanged between the terminal device 220 and the network device 210 .

[0147] Specifically, network device 210 may transmit information regarding a time limit for obtaining a correspondence report to terminal device 220. In one exemplary embodiment, this time limit may be set by a newly introduced upper layer parameter (represented as timeRestrictionForPanelCorrespondence). Alternatively, in another exemplary embodiment, the time limit may be set by reusing conventional parameters (e.g., timeRestrictionForChannelMeasurements, timeRestrictionForInterferenceMeasurements). In some embodiments, terminal device 220 may report whether a time limit was applied when obtaining the correspondence report. Specifically, the correspondence report may include one additional bit to indicate whether a time limit was applied when obtaining the correspondence report and whether the reported correspondence report was obtained based on the time limit.

[0148] Using information about the time limit set by network device 210, terminal device 220 may acquire / derive a correspondence report accordingly. Specifically, if terminal device 220 is not configured to have a time limit, terminal device 220 should acquire / derive a correspondence report by measuring multiple RSs (e.g., CSI-RS or SSB). Correspondingly, if terminal device 220 is configured to have a time limit, terminal device 220 should acquire / derive a correspondence report by measuring only the last RS (the most recent CSI-RS or SSB). Additionally, the RS used to acquire / derive a correspondence report should be earlier than the reference resource.

[0149] In some embodiments, the reference resource is the RS (denoted as P) transmitted at the transmission opportunity. In some embodiments, P=P-T, where T is predefined or configured by the network device 210 and can have different values ​​depending on the downlink or uplink numerology, carrier aggregation configuration, time domain behavior configuration, time restriction configuration, etc.

[0150] Reference is now made to FIG. 4, which illustrates interaction timing 400 according to some embodiments of the present disclosure. As shown in FIG. 4, a transmission opportunity (i.e., Pn) for transmitting a correspondence report is preceded by multiple transmission opportunities (i.e., Pf as shown in FIG. 4) for receiving RSs before the reference resource. If terminal device 220 is not configured to have a time limit, terminal device 220 may obtain / derive the correspondence report based on multiple RSs (i.e., RSs transmitted at transmission opportunities P0 through Pm). Accordingly, if terminal device 220 is configured to have a time limit, terminal device 220 may obtain / derive the correspondence report by measuring only the last RS (i.e., RS transmitted at transmission opportunity Pm).

[0151] In some embodiments, when measuring signal quality, terminal device 220 may apply two capability value sets (i.e., the currently used capability value set and the new capability value set) and, based on the measurement results, decide whether to report a correspondence report associated with the new capability value set.

[0152] In one particular exemplary embodiment, the terminal device 220 is currently applying the one or more capability value sets (referred to as old capability value sets) and anticipates switching to one or more other capability value sets (referred to as new capability value sets). When measuring RS, the terminal device 220 may activate / apply both the new capability value sets and the old capability value sets. The terminal device 220 then compares the measurement results on both the new capability value sets and the old capability value sets and determines whether to report the correspondence associated with the new capability value sets.

[0153] Alternatively, the terminal device 220 may apply a new capability value set when measuring the RS, in which case the terminal device 220 compares the measurement results with previous measurement results associated with the old capability value set.

[0154] Additionally, comparison of measurements may be achieved based on criteria related to RSRP, SINR, coupling loss, path loss, unlink transmit power, and the like. Exemplary Process for Generating and Indexing Correspondence Reports

[0155] As described above, the terminal device 220 may send a correspondence report to the network device 210. According to some embodiments of the present disclosure, the correspondence report may include more fields and indicate more information. Furthermore, the identity information may be redefined so that new capability value set states may be introduced. The following text provides more details about the correspondence report.

[0156] In some embodiments, the correspondence report includes identity information for each of the capability value sets indicated in the correspondence report.

[0157] As described above, each capability set may correspond to a panel (physical entity) deployed in the terminal device, a specific panel type, and the status of the capability set. When reporting capability-related information, the capability set may be indexed by identity information, where the identity information may be an index of the capability set, an index of a panel deployed in the terminal device 220, or the status of the capability set. The indexing mechanism used to report capability-related information as described above can also be used when reporting correspondence reports. For brevity, similar content is omitted, and some additional features are described below.

[0158] Additionally, the status of a capability value set may have more diverse definitions. Specifically, the status of a capability value set may indicate that the capability value set is used for the uplink or that the capability value set is used for the downlink. Additionally, the status of a capability value set may indicate some reserved status, for example, an application status of the capability value set indicating whether the capability value set has already been applied or will be applied. Alternatively or additionally, in some embodiments, the status of a capability value setting may indicate whether the applied capability value set has been changed or will be changed. In one particular exemplary embodiment, the status of the capability value set may indicate one of the following: a capability value set being used for the uplink, a capability value set being used for the downlink (i.e., for the downlink panel only / not associated with the uplink panel), a capability value set not suitable for uplink transmission (e.g., the terminal device 220 cannot use the reported beam for uplink transmission), whether the (activated / applied) uplink capability value set / panel has changed or whether the (activated / applied) uplink capability value set / panel will change, whether the applied capability value set has changed or will change, etc.

[0159] In short, the correspondence report may include a panel information field (i.e., identity information), and further, some values ​​of the panel information field may be reserved and used to indicate newly defined / introduced downlink-only states and some reserved states.

[0160] Additionally, the bit size of the panel information field included in the correspondence report may be determined based on at least one of the number of capability value sets, the number of panels deployed in the terminal device 220, and the number of states of the capability value set. In one specific exemplary embodiment, the bit size of the panel information field is determined based on either or both of the number of reserved states and the number of capability value sets.

[0161] Additionally, the reserved states may be selectively reported and configured. Specifically, the terminal device 220 may report which reserved states are supported by the terminal device 220. In response, the network device 210 may enable / disable some of the reserved states.

[0162] In some embodiments, the reserved states may be presented in ascending / descending order.

[0163] In some embodiments, the number of capability value sets associated with one correspondence report may be configurable. In one particular exemplary embodiment, one correspondence report is associated with one capability value set. Alternatively, one correspondence report is associated with two or more capability value sets.

[0164] In some embodiments, the number of RSs / beams associated with a capability set may also be configured. In one particular exemplary embodiment, in the correspondence report, each RS / beam corresponds to one capability set.

[0165] In short, terminal device 220 may generate a correspondence report in an appropriate format. Table 2 below shows four possible formats for the correspondence report. Table 2 shows four possible formats for correspondence reporting. TIFF0007747221000002.tif97162

[0166] In the above Table 2, "Panel Information" refers to the identification information of the capability value set, "SSBRI / CRI" refers to the information of the RS / beam, and "RSRP / SINR" refers to the measurement result of the corresponding RS / beam. Additionally or alternatively, the first RSRP / SINR is a 7-bit value, and each of the remaining RSRP / SINRs is represented by a 4-bit differential RSRP / SINR value calculated with reference to the first RSRP / SINR.

[0167] In some embodiments, as can be seen from Format 1 / 2 above, one capability value set corresponds to one RS / beam (i.e., one panel per SSBRI / CRI). By using Format 1 / 2, terminal device 220 may report different uplink RS / beam selections for different panels.

[0168] In some embodiments, one correspondence report corresponds to one capability value set, as can be seen from Format 3. Using Format 3, terminal device 220 indicates that all reported SSBRI / CRI (i.e., RS / beams) are usable as uplink RS / beams when terminal device 220 uses this panel for uplink transmission.

[0169] In some embodiments, the network device 210 may set the number of capability sets (represented as "X", where X<the number of capability sets configured to be reported) to be included in a correspondence report. For each reported capability set, one or more RSs / beams may be reported. Additionally, the remaining RSs / beams may be used for the downlink. Format 4 above indicates that the number of capability sets included in one correspondence report is "2".

[0170] In some embodiments, the content or format of the correspondence report may be determined based on a time limit setting. Specifically, if a time limit is applied, only the most recent RS can be used to obtain the correspondence report. In particular, for a terminal device 220 that cannot support multiple simultaneous active panels, only one panel can be used to obtain / derive the correspondence report. In one specific exemplary embodiment, if a time limit is applied when obtaining the correspondence report, the terminal device 220 transmits the correspondence report with one capability value set index, regardless of the configured number of capability value set indexes. In another specific example, if a time limit is applied, the terminal device 220 transmits a correspondence report corresponding to one capability value set (e.g., format 3); if a time limit is not applied, the terminal device 220 transmits a correspondence report in which one capability value set corresponds to one RS / beam (e.g., format 1 / 2) or includes the configured number of capability value sets (e.g., format 4).

[0171] In addition to the above, the network device 210 may transmit a configuration indicating RS resources to the terminal device 220 in an "RS resource set" information element (IE). Furthermore, a "repetition" parameter may be included in the "RS resource set" IE. If the "repetition" parameter is enabled (i.e., the value of the repetition parameter is "on"), the network device 210 transmits all CSI-RS resources on the same Tx beam. In other words, there is only one beam for downlink transmission, and information about that one beam is known to the network device 210. In this case, there is no need to report RS / beam information to the network device 210. Therefore, some other improvements may be performed by either the network device 210 or the terminal device 220.

[0172] In some embodiments, terminal device 220 is not expected to be configured to report a correspondence report when the "repetition" parameter included in the RS resource set is enabled / "on." For example, the "report quantity" parameter included in the configuration is used to indicate to terminal device 220 to report a correspondence report including identity information of the capability value set. In this case, the parameter (report quantity) indicating to report identity information of the capability value set and "repetition" set as "on" are not enabled / configured to terminal device 220 at the same time.

[0173] According to some embodiments of the present disclosure, even if the terminal device 220 is configured to report correspondence reports when the “repetition” parameter included in the RS resource set is enabled / “on”, the terminal device 220 can still successfully handle such scenarios as described below.

[0174] In some embodiments, if the value of the repetition parameter included in the RS resource set is "on", terminal device 220 disables reporting of correspondence reports.

[0175] Alternatively or additionally, in some embodiments, if the value of the repetition parameter included in the RS resource set is "on", terminal device 220 transmits a correspondence report associated with one RS.

[0176] Alternatively or additionally, in some embodiments, if the value of the repeat parameter included in the RS resource set is "on", the terminal device 220 transmits a correspondence report with one capability value set index regardless of the number of capability value set indexes set.

[0177] Alternatively or additionally, in some embodiments, if the value of the repetition parameter included in the RS resource set is "on", terminal device 220 transmits a correspondence report without including information about the RS.

[0178] Additionally, the correspondence report may include other information / fields. In some embodiments, terminal device 220 may indicate whether the correspondence was obtained based on a time limit. In one particular exemplary embodiment, the correspondence report includes an indication having one bit, where the indication indicates whether the correspondence report was determined based only on the most recent downlink RS.

[0179] Terminal device 220 may then generate a correspondence report and transmit the correspondence report to network device 210 (340). Example process of the feedback mechanism

[0180] As mentioned above, the correspondence report may cause a change / switch of the panel / beam / RS / capability value set. Therefore, the transmission status of the correspondence report should be aligned between the network device 210 and the terminal device 220. As a result, a feedback mechanism for the correspondence report is needed.

[0181] According to some embodiments of the present disclosure, the terminal device 220 and the network device 210 communicate 350 with each other according to a correspondence report feedback status, where the feedback status may be ACK or NACK. Alternatively, the feedback status may be ACK, NACK, or "not transmitted / detected" (i.e., no ACK / NACK). It should be understood that if a feedback mechanism for correspondence reports is implemented, the absence of an ACK / NACK should be interpreted as a "NACK."

[0182] In order to avoid introducing any new messages / signaling (including new Radio Network Temporary Identifiers RNTI for feedback on correspondence reporting or new Downlink Control Information DCI), some existing messages / signaling (hereinafter referred to as feedback messages) may be used to indicate the feedback status.

[0183] An example of a feedback message is a TCI activation command or a TCI indication. Specifically, if the TCI activation command or the TCI indication includes information about a TCI state at least partially associated with at least one RS indicated by the correspondence report, the feedback status of the correspondence report is ACK. Correspondingly, if the TCI activation command or the TCI indication includes information about a TCI state unrelated to the RS indicated by the correspondence report, the feedback status of the correspondence report is NACK. Alternatively, if the TCI activation command or the TCI indication includes information about a TCI state associated with at least one RS having more ports than the maximum SRS port of the capability value set in the correspondence report, the feedback status of the correspondence report is NACK. Additionally, the TCI activation command or the TCI indication is the first one received immediately after the transmission of the correspondence report. Alternatively, the TCI activation command or the TCI indication is the first one received within a certain period after the transmission of the correspondence report. In some embodiments, the TCI activation command or the TCI indication is conveyed via MAC CE signaling or DCI. In some embodiments, the TCI activation command or TCI indication includes combined TCI states for both uplink and downlink, or uplink-only TCI states. In some embodiments, the TCI activation command or TCI indication includes TCI states that apply to all physical channels / signals including PDCCH, PDSCH, PUCCH, PUSCH, or that apply only to a subset of physical channels / signals, for example, PUSCH.

[0184] Another example of a feedback message is a DCI message for scheduling a PUSCH, the DCI message including an SRS resource indicator (SRI). In some embodiments, if the SRI indicates an SRS resource with more ports than the maximum SRS port associated with the capability set in the correspondence report, the feedback status of the correspondence report is NACK; otherwise, the feedback status is ACK. In some other embodiments, if the SRI indicates an SRS resource with a number of ports that does not match the maximum SRS port associated with the capability set in the correspondence report, the feedback status of the correspondence report is NACK; otherwise, the feedback status is ACK.

[0185] Another example of the feedback message is a DCI message for scheduling a PUSCH, the DCI message including a transmit precoding matrix indicator (TPMI) in the DCI for scheduling the PUSCH. In some embodiments, if the TPMI indicates a number of layers greater than the maximum number of SRS ports corresponding to the capability value set in the correspondence report, the feedback status of the correspondence report is NACK; otherwise, the feedback status is ACK. Additionally, the DCI for scheduling the PUSCH is the first one received immediately after transmission of the correspondence report. Alternatively, the DCI for scheduling the PUSCH is the first one received within a certain period after transmission of the correspondence report.

[0186] Another example of a feedback message is a PDCCH order for triggering an RA / RACH procedure. Specifically, since the RA procedure may be used for timing alignment of a capability value set / panel associated with a reported correspondence report, a PDCCH order may be used to indicate that the status of the correspondence report is ACK. Additionally, after receiving the PDCCH order, the terminal device 220 transmits a RACH together with the reported panel in the correspondence report. Additionally, the PDCCH order may be the first one received immediately after the transmission of the correspondence report. Alternatively, the PDCCH order may be the first one received within a certain period after the transmission of the correspondence report.

[0187] Another example of a feedback message is signaling for controlling the transmit power of the terminal device 220. Specifically, the signaling for controlling the transmit power may be used to indicate that the status of the correspondence report is ACK. In one particular exemplary embodiment, the signaling for controlling the transmit power includes a transmit power control (TPC) field for TPC for SRS / PUCCH / PUSCH that triggers power adjustment for the panel / capability value set associated with the correspondence report. Additionally, in some embodiments, the signaling for controlling the transmit power is a DCI message having format 2-2 or 2-3 for TPC without an uplink grant. Additionally, the signaling for controlling the transmit power is the first signal received immediately after transmission of the correspondence report. Alternatively, the signaling for controlling the transmit power is the first signal received within a certain period after transmission of the correspondence report.

[0188] Another example of a feedback message is a message that triggers the terminal device 220 to report a correspondence report. In one particular exemplary embodiment, the message used to trigger activation of aperiodic correspondence reporting or semi-persistent correspondence reporting is used to indicate that the status of the correspondence report is NACK. For example, periodic correspondence reporting is configured, but the network device 210 fails to receive the expected periodic correspondence report. Therefore, the network device 210 may send a message that triggers the terminal device 220 to report an aperiodic correspondence report or semi-persistent correspondence report. Thus, the message implies a failed transmission of the periodic correspondence report, indicating a NACK state.

[0189] Another example of a feedback message is a message for activating SRS transmission. Specifically, aperiodic or semi-persistent SRS transmissions associated with a capability value set may be used to train an uplink codebook, a precoder used for non-codebook-based uplink transmissions, or an uplink beam for the capability value set associated with the correspondence report. In some embodiments, the SRS transmission may be an SRS resource set / resource / port associated with the corresponding capability value set, as shown in Table 1. Therefore, the message for activating SRS transmission may be used to indicate an ACK status.

[0190] Another example of a feedback message is a message for activating CSI report transmission. Specifically, aperiodic or semi-persistent CSI reporting may be used to train a downlink receive beam associated with a capability value set. Additionally, the triggered / activated CSI reporting may be configured to disable reporting of identity information of the capability value set (i.e., the parameter of "report quantity" is set to "none") and the parameter of repetition within resource set is set to "on". In some embodiments, the CSI report transmission may be based on the downlink RS resources associated with the corresponding capability value set, as shown in Table 1.

[0191] To reduce signaling overhead, the correspondence report may be conditionally transmitted / received, i.e., in some scenarios, the terminal device 220 does not expect to receive a feedback message, and the network device 210 does not transmit a feedback message.

[0192] In some embodiments, a feedback message is sent / received only if the reported correspondence report is at least partially different from the previous correspondence report, in other words, the reported correspondence report may update the previous correspondence report.

[0193] In one particular exemplary embodiment, a correspondence report indicating a correspondence between at least one first set of capability values ​​and at least one first RS is reported from terminal device 220 to network device 210. In some embodiments, a feedback message is sent / received when the at least one correspondence is at least partially different from a second correspondence, the second correspondence being currently applied at terminal device 220 or associated with the last correspondence report.

[0194] Alternatively or additionally, in some other embodiments, the feedback message is sent / received when at least one first capability value set associated with the correspondence report is at least partially different from at least one second capability value set, which is currently applied in the terminal device 220 or associated with the last correspondence report.

[0195] Alternatively or additionally, in some other embodiments, the feedback message is transmitted / received when at least one first RS associated with the correspondence report is at least partially different from at least one second RS, the at least one second RS being currently used in the terminal device 220 or associated with the last correspondence report.

[0196] Furthermore, two or more second correspondence reports may be taken into consideration when determining whether to send / receive a feedback message, where the second correspondence report may refer to one or more correspondence reports sent within a certain time interval.

[0197] Alternatively or additionally, in some other embodiments, a feedback message is transmitted / received when correspondence reporting is configured to have a specific time-domain behavior. In other words, a feedback message is not transmitted / received when correspondence reporting is configured to have a specific time-domain behavior. Specifically, periodic feedback is not preferred due to the larger signaling overhead it may cause. In some embodiments, a feedback message is not transmitted / received when correspondence reporting is periodic. In some embodiments, when both periodic correspondence reporting and aperiodic / semi-persistent correspondence reporting are configured, a feedback message is not transmitted / received for periodic correspondence reporting.

[0198] In some embodiments, update / override rules may be defined when determining whether to send / receive a feedback message.

[0199] In one particular exemplary embodiment, the comparison of the correspondence report with the at least one second correspondence report (e.g., the currently applied correspondence report, the last correspondence report, or a correspondence report sent within a certain time interval) is performed only if the correspondence report and the at least one second correspondence report are configured to have the same time domain behavior (e.g., periodic, aperiodic, and semi-persistent).

[0200] Alternatively or additionally, in another particular exemplary embodiment, whether to send / receive a feedback message may be determined based on a priority of the time-domain behavior. One example of a priority is aperiodic time-domain behavior, semi-persistent time-domain behavior / periodic time-domain behavior. Another example of a priority is periodic time-domain behavior, aperiodic time-domain behavior / semi-persistent time-domain behavior. Another example of a priority is aperiodic time-domain behavior, semi-persistent time-domain behavior, and periodic time-domain behavior. Another example of a priority is periodic time-domain behavior, aperiodic time-domain behavior, and semi-persistent time-domain behavior. In other embodiments, other priorities may apply.

[0201] Alternatively or additionally, in some other embodiments, whether to send / receive a feedback message is determined based on identity information of the capability set associated with the correspondence report. Specifically, the feedback message is sent / received if the identity information indicates a status of a particular capability set. In one particular exemplary embodiment, the feedback message is sent / received if the identity information indicates that the capability set is being used for the uplink. Alternatively, in another particular exemplary embodiment, the feedback message is sent / received if the identity information indicates that the capability set is not being used for the downlink. Alternatively, in another particular exemplary embodiment, the feedback message is sent / received if the identity information indicates an unreserved status.

[0202] In some embodiments, the message is sent / received within a certain period after the correspondence report is sent. In other words, if terminal device 220 fails to receive the feedback message within a certain period after sending the correspondence report, terminal device 220 determines the feedback status to be NACK.

[0203] In this way, the signaling overhead caused by the feedback mechanism is minimized.

[0204] In addition to the above, operations on a newly reported capability set should be aligned in both the terminal device 220 and the network device 210 .

[0205] In some embodiments, the operation of applying the newly reported capability value set is controlled by the network device 210 .

[0206] In one particular exemplary embodiment, the newly reported capability set is applied in response to sending a feedback message about the correspondence report.

[0207] Alternatively, in another particular exemplary embodiment, the newly reported capability value set is applied in response to an SRS transmission from terminal device 220 to network device 210 after receiving the feedback message.

[0208] Alternatively, in some embodiments, operations on the newly reported capability set are controlled by terminal device 220 .

[0209] In one particular exemplary embodiment, in response to sending a correspondence report, a newly reported set of capability values ​​is applied.

[0210] Alternatively, in another particular exemplary embodiment, the newly reported set of capability values ​​is applied depending on the time since sending the correspondence report exceeding a preset period of time.

[0211] Additionally, in some embodiments, when there are multiple RSs indicated by the first correspondence relationship, the terminal device 220 transmits uplink transmissions using a spatial domain transmit filter associated with the RS having the best signal quality among the multiple RSs.

[0212] Additionally, if the operation of applying the newly reported capability value set is controlled by the terminal device 220 and a failed transmission of the correspondence report occurs, the terminal device 220 should fall back to the previous operation state. Specifically, if the terminal device 220 fails to receive a feedback message indicating an ACK for the correspondence report or a feedback message indicating a NACK for the correspondence report, the terminal device 220 disables application of the newly reported capability value set.

[0213] In addition to the above, the operations for the currently used capability set (also referred to as the second capability set) should also be aligned in both the terminal device 220 and the network device 210 .

[0214] In some embodiments, the second set of capability scores continues to be applied after a period of time following the sending of the correspondence report.

[0215] Alternatively, in some other embodiments, the second set of capability values ​​continues to be applied until a message indicating an ACK for the correspondence report is received from the network device 210 .

[0216] Alternatively, in some other embodiments, the second set of capability values ​​continues to be applied until a message indicating an ACK for the correspondence report is received from the network device 210 .

[0217] Alternatively, in some other embodiments, the second capability value set continues to apply until the next transmission opportunity for the correspondence report, or in other words, until another correspondence report is transmitted to network device 210.

[0218] Additionally, the transmit power of terminal device 220 is controlled by network device 210. Specifically, the transmit power of terminal device 220 may operate in an accumulation mode, in which terminal device 220 maintains an accumulated power control adjustment state and adjusts the transmit power according to TPC commands from network device 210.

[0219] According to some embodiments of the present disclosure, terminal device 220 resets its accumulation of power control adjustment states in response to applying the newly reported correspondence.

[0220] For better understanding, some exemplary operations will be described with reference to the following two specific embodiments and FIG. 5, where FIG. 5 illustrates interaction timing 500 according to some embodiments of the present disclosure. Some exemplary operations for one particular exemplary embodiment

[0221] In this particular exemplary embodiment, the operation of applying the newly reported capability value set is controlled by the network device 210 .

[0222] 5, first, the terminal device 220 and the network device 210 apply the second capability value set. Then, the terminal device 220 transmits a correspondence report to the network device 210 at time T1 and receives a feedback message at time T2. Furthermore, time T3 indicates the first transmission opportunity for the SRS after receiving the feedback message.

[0223] In some embodiments, after sending the correspondence report to the network device 210 at time T1, the terminal device 220 keeps the newly reported one activated for a while so that the terminal device 220 can switch to the newly reported one.

[0224] In some embodiments, terminal device 220 keeps the newly reported correspondence report activated for a pre-configured period of time after sending it.

[0225] Alternatively, in some embodiments, the terminal device 220 keeps the newly reported one activated until the next transmission opportunity for the correspondence report, which includes a periodic correspondence report, an aperiodic correspondence report, or a semi-persistent correspondence report.

[0226] Alternatively, in some embodiments, terminal device 220 keeps the newly reported one activated until sending a feedback message. As shown in FIG. 5, terminal device 220 keeps the newly reported one activated until time T2.

[0227] In the example of FIG. 5, the operation of applying the newly reported capability value set is controlled by the network device 210 .

[0228] In some embodiments, terminal device 220 and network device 210 apply the newly reported capability value set after transmitting the feedback message. As shown in FIG. 5, terminal device 220 and network device 210 start applying the newly reported capability value set from time T2. Additionally, an offset (e.g., X time units) may be applied. In other words, the start time for applying the newly reported capability value set is X time units after time T2.

[0229] In some embodiments, terminal device 220 resets the accumulation of power control adjustment states in response to applying a newly reported capability value set. Specifically, when a newly reported capability value set is applied (i.e., immediately after an uplink panel switch), TPC controls should not be accumulated regardless of the power setting. In one specific exemplary embodiment, terminal device 220 resets the accumulation of PUSCH / PUCCH / SRS power control adjustment state 1 or all states or a subset of states associated with the newly reported capability value set. Optionally, the instruction in the TPC command field may represent an absolute value or an accumulated value. In one specific exemplary embodiment, a 0 in the TPC command field may represent an absolute value of -4 dB and an accumulated value of -1 dB. In another specific embodiment, terminal device 220 applies the absolute value according to the instruction in the TPC command field regardless of the power setting. In other words, terminal device 220 does not apply an accumulated value according to the instruction in the TPC command field regardless of the power setting.

[0230] The operation for the second ability score set currently in use is described below.

[0231] In some embodiments, terminal device 220 and network device 210 continue to apply the second set of capability values ​​until they apply the newly reported set of capability values. Additionally, an offset (e.g., X time units) may be considered.

[0232] Furthermore, the SRS is used to train the uplink beam / precoder / codebook associated with the newly reported capability value set. Before obtaining the trained results, terminal device 220 may not be able to use the newly reported capability value set. Therefore, in some embodiments, terminal device 220 and network device 210 continue to apply the second capability value set until the first SRS transmission (i.e., time T3). Alternatively, in some embodiments, after the feedback message is received, a different panel / beam assumption is applied to the PUCCH / PUSCH transmission before the first SRS transmission (i.e., time T3).

[0233] Additionally, the triggering / activation of SRS transmission is conditional. Specifically, if the feedback message indicates NACK, the terminal device 220 does not trigger / activate SRS transmission (i.e., does not trigger / activate SRS transmission at time T3). Some exemplary operations for another specific exemplary embodiment

[0234] 5, first, the terminal device 220 and the network device 210 apply the second capability value set, and then the terminal device 220 sends a correspondence report to the network device 210 at time T1 and receives a feedback message at time T2.

[0235] In some embodiments, terminal device 220 receives a feedback message using a downlink panel corresponding to the newly reported capability set, and if the feedback message is a TCI activation command, terminal device 220 applies the reported capability set using the indicated TCI.

[0236] In this particular exemplary embodiment, the operation of applying the newly reported capability value set is controlled by terminal device 220, which means that the newly reported capability value set is applied before time T2.

[0237] Additionally, terminal device 220 may report RS / beam information (e.g., reported SSBRI / CRI for uplink transmission) to apply the newly reported capability value set.

[0238] Alternatively, the assumed RS / beam may be used when applying a newly reported capability value set. In one specific exemplary embodiment, when two or more SSBRI / CRI (RS / beam information) are reported, some rules for selecting the RS / beam may be predefined. For example, it may be specified that the SSBRI / CRI with the best reported RSRP / SINR should always be applied.

[0239] In some embodiments, terminal device 220 and network device 210 apply the newly reported capability value set when transmitting the correspondence report. As shown in FIG. 5, terminal device 220 and network device 210 start applying the newly reported capability value set from time T1. Additionally, an offset (e.g., X time units) may be applied. In other words, the start time for applying the newly reported capability value set is X time units after time T1.

[0240] The operation for the second ability score set currently in use is described below.

[0241] In some embodiments, the terminal device is required to keep the currently used second set of capability values ​​activated for a period of time (eg, a predefined period of time).

[0242] In some embodiments, terminal device 220 and network device 210 continue to apply the second set of capability values ​​until they apply the newly reported set of capability values. Additionally, an offset (e.g., X time units) may be considered.

[0243] Furthermore, a power control operation is performed in terminal device 220. Specifically, terminal device 220 resets the accumulation of power control adjustment states in response to applying the newly reported capability value set. Specifically, when the newly reported capability value set is applied (i.e., immediately after an uplink panel switch), TPC control should not be accumulated regardless of the power setting. In one specific exemplary embodiment, terminal device 220 resets the accumulation of PUSCH / PUCCH / SRS power control adjustment state 1 or all states or a subset of states associated with the newly reported capability value set.

[0244] Additionally, as described above, if the terminal device 220 fails to receive a feedback message indicating an ACK for the correspondence report or a feedback message indicating a NACK for the correspondence report, the terminal device 200 disables application of the newly reported capability value set. In this case, TPC commands should not be accumulated by the terminal device 220.

[0245] Optionally, the instruction in the TPC command field may represent an absolute value or a cumulative value. In one particular exemplary embodiment, a 0 in the TPC command field may represent an absolute value of -4 db and a cumulative value of -1 db. In another specific embodiment, terminal device 220 applies the absolute value according to the instruction in the TPC command field regardless of the power setting. In other words, terminal device 220 does not apply the cumulative value according to the instruction in the TPC command field regardless of the power setting. Example process of the feedback mechanism

[0246] As mentioned above, after sending the correspondence report, in some specific scenarios, the terminal device 220 and the network device 210 may need to communicate with each other using a default set of capability values.

[0247] Continuing to refer to FIG. 3, if the fallback condition is met, the terminal device 220 and the network device 210 fall back to applying a default set of capability values ​​(360).

[0248] 6A and 6B, some detailed operations will be described. In the example of FIG. 6A and 6B, T1 indicates a time point for sending a correspondence report, and T2 indicates an expected time point for receiving a feedback message about the correspondence report. It should be understood that the fallback operation does not depend on the feedback mechanism described above.

[0249] According to this disclosure, the time for applying the default capability score set may be defined by any suitable fallback condition.

[0250] In some embodiments, terminal device 220 determines that a fallback condition is met if the time since transmitting the correspondence report exceeds a predefined time period. In other words, terminal device 220 and network device 210 fall back to applying a default capability value set after a certain period (time interval 610 as shown in FIG. 6B) since terminal device 220 transmitted the correspondence report. As shown in FIG. 6A, terminal device 220 and network device 210 fall back to applying a default capability value set at time T3. As can be seen, the implementation of this embodiment is independent of the feedback mechanism.

[0251] Alternatively, in some embodiments, the terminal device 220 determines that the fallback condition is met if the terminal device 220 fails to receive a message indicating an ACK for the correspondence report after a certain period of time has passed since sending the correspondence report.

[0252] Alternatively, in some embodiments, terminal device 220 determines that the fallback condition is met if, after a certain period of time (time interval 660 as shown in FIG. 6B ) since transmitting a correspondence report, terminal device 220 fails to receive a message indicating an ACK for the correspondence report at a transmission opportunity for receiving the message. As shown in FIG. 6B , terminal device 220 and network device 210 fall back to applying the default capability value set at time T4.

[0253] Alternatively, in some embodiments, terminal device 220 determines that the fallback condition is met if terminal device 220 receives a message indicating a NACK on the correspondence report.

[0254] Alternatively, in some embodiments, terminal device 220 determines that the fallback condition is met if the capability value set associated with the correspondence report is set to have a higher capability.

[0255] Alternatively, in some embodiments, terminal device 220 determines that the fallback condition is met if the correspondence reports are aperiodic.

[0256] Alternatively, in some embodiments, terminal device 220 determines that a fallback condition is met when a BWP switch, a CC switch, a secondary cell activation, and cross cell scheduling occur.

[0257] Alternatively, in some embodiments, terminal device 220 determines that the fallback condition is met when terminal device 220 operates in a power saving mode (eg, DRX mode).

[0258] Alternatively, in some embodiments, terminal device 220 determines that the fallback condition is met if a new capability value set / RS / beam is reported by a correspondence report.

[0259] It should be understood that the above examples for determining whether a fallback condition is met can be used separately or in combination. Furthermore, in some other embodiments, any suitable rules and factors may be used to determine whether a fallback condition is met.

[0260] Additionally, the definition of the default capability set (i.e., which capability set may be used as the default capability set) is the same as that described for the initial transmission in this disclosure. For the sake of brevity, some details are omitted here. Example method

[0261] 7 is a flowchart of an example method 700 according to some embodiments of the present disclosure. For example, the method 700 may be implemented in the terminal device 220 shown in FIG.

[0262] At block 710, terminal device 220 transmits a correspondence report to network device 210 indicating a first correspondence between at least one first set of capability values ​​and at least one first RS.

[0263] In block 720, the terminal device 220 communicates with the network device 210 according to the feedback status of the correspondence report, where the feedback status is one of ACK or NACK.

[0264] In some embodiments, terminal device 220 receives a message from network device 210. The message indicates a feedback status of a correspondence report and is at least one of a TCI activation command associated at least in part with at least one RS indicated by the correspondence report, a PDCCH order for triggering an RA procedure, signaling for controlling transmit power of terminal device 220, a message for triggering terminal device 220 to report a correspondence report, a message for activating SRS transmission, and a message for activating CSI report transmission.

[0265] In some embodiments, the terminal device 220 detects that the at least one first correspondence relationship between at least one first capability value set and at least one first RS associated with the correspondence report is at least partially different from at least one second correspondence relationship applied in the terminal device 220, that the at least one first correspondence relationship between at least one first capability value set and at least one first RS associated with the correspondence report is at least partially different from at least one second correspondence relationship associated with a last correspondence report, and that the at least one first capability value set associated with the correspondence report is at least partially different from at least one second correspondence relationship applied in the terminal device 220. The message indicating the feedback state of the correspondence report is expected to be received if at least one of the following conditions is met: the set of capability values ​​is at least partially different from at least one second RS currently applied in the terminal device 220, the at least one first RS associated with the correspondence report is at least partially different from at least one second RS applied in the terminal device 220, the correspondence report is configured to have a specific time domain behavior, or identity information of a capability value set among the at least one capability value set indicates a specific capability value set state.

[0266] In some embodiments, the status of the capability set is one of the capability set being used for the uplink, the capability set being used for the downlink, or an application status of the capability set indicating whether the capability set has already been applied or will be applied.

[0267] In some embodiments, the terminal device 220 determines that the feedback status of the correspondence report is NACK in response to failing to receive a message indicating the feedback status of the correspondence report within a certain period of time after transmitting the correspondence report, or receiving a message that triggers the terminal device 220 to report an aperiodic correspondence report or a semi-persistent correspondence report after transmitting the correspondence report.

[0268] In some embodiments, the terminal device 220 applies at least one first capability value set associated with the first correspondence in response to one of receiving a message from the network device 210 indicating an ACK for the correspondence report or transmitting an SRS after receiving a message from the network device 210 indicating an ACK.

[0269] In some embodiments, the terminal device 220 applies at least one first capability value set associated with the first correspondence in response to one of sending a correspondence report or the time period since sending the correspondence report exceeds a preset time period.

[0270] In some embodiments, when there are multiple RSs indicated by the first correspondence relationship, the terminal device 220 transmits an uplink transmission using a spatial domain transmit filter associated with the RS having the best signal quality among the multiple RSs.

[0271] In some embodiments, if the terminal device 220 fails to receive a message indicating the feedback status of the correspondence report within a certain period of time after sending the correspondence report, or if it receives a message indicating a NACK for the correspondence report, it disables the application of the at least one first capability value set associated with the first correspondence.

[0272] In some embodiments, the terminal device 220 communicates with the network device 210 by applying at least one second set of capability values ​​associated with a second correspondence relationship, and continues to apply the at least one second set of capability values ​​associated with the second correspondence relationship after a certain period of time has passed since sending the correspondence relationship report.

[0273] In some embodiments, terminal device 220 communicates with network device 210 by applying at least one second capability value set associated with a second correspondence relationship, and continues to apply the at least one second capability value set associated with the second correspondence relationship until one of: after sending the correspondence relationship report, it receives a message from network device 210 indicating an ACK for the correspondence relationship report; or after sending the correspondence relationship report, it sends another correspondence relationship report to network device 210.

[0274] In some embodiments, terminal device 220 resets the accumulation of power control adjustment states in response to applying the first correspondence relationship.

[0275] In some embodiments, terminal device 220 generates the correspondence report based on a parameter set by network device 210 of a time limit for obtaining the first correspondence.

[0276] In some embodiments, the correspondence report further indicates identity information for each of the capability value sets indicated in the correspondence report.

[0277] In some embodiments, the identity information indicates at least one of an index of a capability set, an index of a panel deployed on terminal device 220 and associated with the capability set, or a state of the capability set.

[0278] In some embodiments, the bit size of the identity information is determined based on at least one of a first number of capability value sets supported by the terminal device 220 or a second number of states of the capability value sets supported by the terminal device 220.

[0279] In some embodiments, terminal device 220 transmits capability-related information of terminal device 220 to network device 210. The capability-related information indicates a plurality of capability value sets, and a capability value set among the plurality of capability value sets includes at least one of identity information of the capability value set, a maximum number of sounding reference signal (SRS) ports, a coherence type, a maximum number of uplink layers, a maximum number of downlink layers, a maximum number of RS ports, a maximum number of codewords, or a maximum number of MIMO layers.

[0280] In some embodiments, each of the plurality of capability value sets corresponds to a particular type of capability value set, and the capability-related information further indicates at least one of whether a symmetric antenna structure or an asymmetric antenna structure is deployed in the terminal device 220, or the respective number of capability value sets corresponding to each particular type of capability value set.

[0281] In some embodiments, the capability-related information further indicates an associative relationship between the plurality of capability value sets.

[0282] In some embodiments, the capability-related information further indicates at least one of whether the terminal device 220 supports applying two or more capability value sets in parallel, or the number of capability value sets supported to be applied in parallel by the terminal device 220.

[0283] In some embodiments, the capability-related information further indicates at least one of whether the terminal device 220 supports determining the feedback status of a correspondence report, whether the terminal device 220 supports reporting a correspondence report for downlink transmission, whether the terminal device 220 supports reporting the status of a capability value set, whether the terminal device 220 supports obtaining the first correspondence with a time limit, or the number of capability value sets included in a correspondence report supported by the terminal device 220.

[0284] In some embodiments, terminal device 220 receives from network device 210 at least one setting used by terminal device 220, the at least one setting indicating at least one of an association relationship between at least one transmission parameter and a capability value set, a time domain behavior of the correspondence relationship report, information regarding a time limit for obtaining the first correspondence relationship, a reporting amount, or the number of capability value sets associated with one correspondence relationship report.

[0285] In some embodiments, the at least one transmission parameter includes at least one of a resource for transmitting an SRS, a resource for transmitting a PUCCH, a transmission configuration indicator status, or a resource for transmitting a downlink RS.

[0286] In some embodiments, terminal device 220 performs SRS transmission based on both the at least one setting and one or more sets of capability values ​​currently applied at terminal device 220.

[0287] In some embodiments, when the value of the repetition parameter included in the RS resource set is on, the terminal device 220 performs at least one of the following: disable reporting of the correspondence report, or send the correspondence report associated with one RS; send the first correspondence report with one capability value set index regardless of the configured number of capability value set indexes; or send the correspondence report without including information about the RS.

[0288] 8 is a flowchart of an example method 800 according to some embodiments of the present disclosure. For example, the method 800 may be implemented in the terminal device 220 shown in FIG.

[0289] In block 810, terminal device 220 determines a default set of capability values.

[0290] In block 820, the terminal device 220 performs at least one of performing an initial transmission with the network device 210 by applying a default capability value set, or, if a fallback condition is met, falling back to applying the default capability value set after sending a correspondence report to the network device 210, the correspondence report indicating the correspondence between the capability value set and the RS to the network device 210.

[0291] In some embodiments, the default value set is one of a capability value set with a lower capability, a capability value set with a higher capability, a capability value set with a lower capability value set index, a capability value set with a higher capability value set index, a last used capability value set, a predefined capability value set, or a capability value set set by either terminal device 220 or network device 210.

[0292] In some embodiments, terminal device 220 performs an initial transmission at least during the period between reporting the configuration of the capability set and transmitting the first correspondence report.

[0293] In some embodiments, the terminal device 220 performing the initial transmission with the network device includes at least one of receiving a scheduling message generated according to a default capability value set from the network device 210, or sending an uplink transmission with the network device 210 by applying the default capability value set.

[0294] In some embodiments, terminal device 220 transmits information regarding a default capability set during the RA procedure.

[0295] In some embodiments, the terminal device 220 determines that the fallback condition is met if the terminal device 220 fails to receive a message indicating an ACK for the correspondence report after a certain period of time has passed since sending the correspondence report.

[0296] In some embodiments, the terminal device 220 determines that the fallback condition is met if, a certain period of time after transmitting the correspondence report, the terminal device 220 receives a message indicating an ACK for the correspondence report at a transmission opportunity for receiving the message.

[0297] In some embodiments, terminal device 220 determines that the fallback condition is met if terminal device 220 receives a message indicating a NACK on the correspondence report.

[0298] In some embodiments, terminal device 220 determines that a fallback condition is met if the time since sending a correspondence report exceeds a predefined time period.

[0299] In some embodiments, terminal device 220 determines that a fallback condition is met if the capability value set associated with the correspondence report is set to have a higher capability.

[0300] In some embodiments, terminal device 220 determines that a fallback condition is met if the correspondence reports are aperiodic.

[0301] In some embodiments, terminal device 220 determines that a fallback condition is met if a BWP switch, a CC switch, a secondary cell activation, or cross cell scheduling occurs.

[0302] In some embodiments, terminal device 220 determines that a fallback condition is met if terminal device 220 operates in DRX mode.

[0303] 9 is a flowchart of an example method 900 according to some embodiments of the present disclosure. For example, the method 900 may be implemented in the network device 210 shown in FIG.

[0304] At block 910, terminal device 210 receives a correspondence report from terminal device 220 indicating a first correspondence between at least one first set of capability values ​​and at least one first RS.

[0305] In block 920, terminal device 210 communicates with terminal device 220 according to the feedback status of the correspondence report, where the feedback status is one of ACK or NACK.

[0306] In some embodiments, network device 210 transmits a message to terminal device 220 indicating a feedback status of the correspondence report and being at least one of a TCI activation command associated at least in part with at least one RS indicated by the report, a PDCCH order for triggering an RA procedure, signaling for controlling the transmit power of terminal device 220, a message for triggering terminal device 220 to report the correspondence report, a message for activating SRS transmission, and a message for activating CSI report transmission.

[0307] In some embodiments, network device 210 detects that the at least one first correspondence between at least one first capability value set and at least one first RS associated with the correspondence report is at least partially different from at least one second correspondence applied in terminal device 220, that the at least one first correspondence between at least one first capability value set and at least one first RS associated with the correspondence report is at least partially different from at least one second correspondence applied in a last correspondence report, and that the at least one first correspondence between at least one first capability value set and at least one first RS associated with the correspondence report is at least partially different from at least one second correspondence applied in a last correspondence report. If at least one of the following conditions is met: one capability value set is at least partially different from at least one second capability value set currently applied in the terminal device 220; the at least one first RS associated with the correspondence report is at least partially different from at least one second RS applied in the terminal device 220; the correspondence report is configured to have a specific time-domain behavior; or the identity information of a capability value set among the at least one capability value set indicates a specific capability value set state, the message indicating the feedback state of the correspondence report is sent.

[0308] In some embodiments, the status of the capability value set is one of the capability value set being used for the uplink, the capability value set being used for the downlink, or an application status of the capability value set indicating whether the capability value set has already been applied or will be applied.

[0309] In some embodiments, if network device 210 determines that the feedback status of the correspondence report is NACK, network device 210 sends a message to terminal device 220. This message triggers terminal device 220 to report an aperiodic correspondence report or a semi-persistent correspondence report after receiving the correspondence report.

[0310] In some embodiments, the network device 210 applies at least one first capability value set associated with the first correspondence in response to one of sending a message to the terminal device 220 indicating an ACK for the correspondence report or receiving an SRS after sending a message indicating an ACK to the terminal device 220.

[0311] In some embodiments, the network device 210 applies at least one first set of capability values ​​associated with the first correspondence in response to one of receiving the correspondence report or the time period since receiving the correspondence report exceeds a preset time period.

[0312] In some embodiments, if there are multiple RSs indicated by the first correspondence relationship, the network device 210 receives the uplink transmission with a spatial domain transmit filter associated with the RS among the multiple RSs that has the best signal quality.

[0313] In some embodiments, the network device 210 disables application of the at least one first capability value set associated with the first correspondence relationship in accordance with a determination that the feedback status of the first correspondence relationship report is NACK.

[0314] In some embodiments, network device 210 communicates with terminal device 220 by applying at least one second set of capability values ​​associated with a second correspondence relationship, and continues to apply the at least one second set of capability values ​​associated with the second correspondence relationship after a certain period of time has passed since receiving the first correspondence relationship report.

[0315] In some embodiments, network device 210 communicates with terminal device 220 by applying at least one second capability value set associated with a second correspondence relationship, and continues to apply the at least one second capability value set associated with the second correspondence relationship until one of: after receiving the first correspondence relationship report, sending a message to terminal device 220 indicating an ACK for the correspondence relationship report, or after receiving the correspondence relationship report, receiving another correspondence relationship report from terminal device 220.

[0316] In some embodiments, the correspondence report further indicates identity information for each of the capability value sets indicated in the correspondence report.

[0317] In some embodiments, the identity information indicates at least one of an index of a capability set, an index of a panel deployed on terminal device 220 and associated with the capability set, or a state of the capability set.

[0318] In some embodiments, the bit size of the identity information is determined based on at least one of a first number of capability value sets supported by the terminal device 220 or a second number of states of the capability value sets supported by the terminal device 220.

[0319] In some embodiments, network device 210 receives capability-related information of terminal device 220 from terminal device 220. The capability-related information indicates a plurality of capability value sets, and a capability value set among the plurality of capability value sets includes at least one of identity information of the capability parameter set, a maximum number of sounding reference signal (SRS) ports, a coherence type, a maximum number of uplink layers, a maximum number of downlink layers, a maximum number of RS ports, a maximum number of codewords, or a maximum number of MIMO layers.

[0320] In some embodiments, each of the plurality of capability value sets corresponds to a particular type of capability value set, and the capability-related information further indicates at least one of whether a symmetric antenna structure or an asymmetric antenna structure is deployed in the terminal device 220, or the respective number of capability value sets corresponding to each particular type of capability value set.

[0321] In some embodiments, the capability-related information further indicates an associative relationship between the plurality of capability value sets.

[0322] In some embodiments, the capability-related information further indicates at least one of whether the terminal device 220 supports applying two or more capability value sets in parallel, or the number of capability value sets supported to be applied in parallel by the terminal device 220.

[0323] In some embodiments, the capability-related information further indicates at least one of whether the terminal device 220 supports determining the feedback status of a correspondence report, whether the terminal device 220 supports reporting a correspondence report for downlink transmission, whether the terminal device 220 supports reporting the status of a capability value set, whether the terminal device 220 supports obtaining the first correspondence with a time-limited requirement, or the number of capability value sets included in a correspondence report supported by the terminal device 220.

[0324] In some embodiments, network device 210 transmits at least one configuration to terminal device 220 for use by terminal device 220, wherein the at least one configuration indicates at least one of an association relationship between at least one transmission parameter and a capability value set, a time domain behavior of the correspondence report, information on a time limit for obtaining the first correspondence, or the number of capability value sets associated with one correspondence report.

[0325] In some embodiments, the at least one transmission parameter includes at least one of a resource for transmitting an SRS, a resource for transmitting a PUCCH, a transmission configuration indicator status, or a resource for transmitting a downlink RS.

[0326] In some embodiments, the correspondence reports are configured by the at least one setting to have a first period, the first period being aligned with a second period of the beam reports, and the first period being a multiple of the second period.

[0327] 10 is a flowchart of an example method 1000 according to some embodiments of the present disclosure. For example, the method 1000 may be implemented in the network device 210 shown in FIG.

[0328] In block 1010, terminal device 220 determines a default set of capability values.

[0329] In block 1020, the terminal device 220 performs at least one of performing an initial transmission with the terminal device 220 by applying a default capability value set, or, if a fallback condition is met, falling back to applying the default capability value set after receiving a correspondence relationship report from the terminal device 220, the correspondence relationship report indicating the correspondence relationship between the capability value set and the RS from the terminal device 220.

[0330] In some embodiments, the default value set is one of a capability value set with a lower capability, a capability value set with a higher capability, a capability value set with a lower capability value set index, a capability value set with a higher capability value set index, a last used capability value set, a predefined capability value set, or a capability value set set by either terminal device 220 or network device 210.

[0331] In some embodiments, the network device 210 performs the initial transmission at least during the period between reporting the configuration of the capability value set and transmitting the first correspondence report.

[0332] In some embodiments, the network device 210 performing the initial transmission with the terminal device 220 includes at least one of transmitting a scheduling message to the terminal device 220 that is generated according to a default capability value set, or receiving an uplink transmission from the terminal device 220 that is transmitted by applying the default capability value set.

[0333] In some embodiments, the network device 210 receives information regarding a default set of capability values ​​during the RA procedure.

[0334] In some embodiments, the network device 210 determines that the fallback condition is met if one of the following applies: the time since receiving the correspondence report exceeds a predefined time period; the capability value set associated with the correspondence report is set to have a higher capability; the correspondence report is aperiodic; one of a BWP switch, a CC switch, secondary cell activation, and cross-cell scheduling has occurred; or the terminal device 220 is operating in DRX mode. Equipment example

[0335] In some exemplary embodiments, terminal device 220 comprises circuitry configured to send a correspondence report to network device 210 indicating a first correspondence between at least one first capability value set and at least one first RS, and to communicate with network device 210 according to a feedback status of the correspondence report, wherein the feedback status is one of ACK or NACK.

[0336] In some embodiments, the circuitry is further configured to receive a message from the network device 210, the message indicating the feedback status of the correspondence report and being at least one of a TCI activation command associated at least in part with at least one RS indicated by the correspondence report, a PDCCH order for triggering an RA procedure, signaling for controlling transmit power of the terminal device 220, a message for triggering the terminal device 220 to report a correspondence report, a message for activating SRS transmission, and a message for activating CSI report transmission.

[0337] In some embodiments, the circuitry further detects that the at least one first correspondence between at least one first capability value set and at least one first RS associated with the correspondence report is at least partially different from at least one second correspondence applied in the terminal device 220, that the at least one first correspondence between at least one first capability value set and at least one first RS associated with the correspondence report is at least partially different from at least one second correspondence applied in a last correspondence report, and that the at least one first capability value set associated with the correspondence report is at least partially different from at least one second correspondence applied in the terminal device 220. The communication device is configured to expect to receive the message indicating the feedback state of the correspondence report when at least one of the following conditions is met: the correspondence report is at least partially different from at least one second capability value set currently applied in the terminal device 220, the at least one first RS associated with the correspondence report is at least partially different from at least one second RS applied in the terminal device 220, the correspondence report is configured to have a specific time domain behavior, or the identity information of a capability value set among the at least one capability value set indicates a specific capability value set state.

[0338] In some embodiments, the status of the capability set is one of the capability set being used for the uplink, the capability set being used for the downlink, or an application status of the capability set indicating whether the capability set has already been applied or will be applied.

[0339] In some embodiments, the circuitry is configured to determine that the feedback status of the correspondence report is NACK in response to failing to receive a message indicating the feedback status of the correspondence report within a certain period of time after transmitting the correspondence report, or receiving a message triggering the terminal device to report an aperiodic correspondence report or a semi-persistent correspondence report after transmitting the correspondence report.

[0340] In some embodiments, the circuitry is configured to apply at least one first capability value set associated with a first correspondence in response to one of receiving a message from network device 210 indicating an ACK for the correspondence report or transmitting an SRS after receiving a message from network device 210 indicating an ACK.

[0341] In some embodiments, the circuitry is further configured to apply the at least one first set of capability values ​​associated with the first correspondence in response to one of sending the correspondence report or a time period since sending the correspondence report exceeding a preset time period.

[0342] In some embodiments, if there are multiple RSs indicated by the first correspondence relationship, the circuitry is further configured to transmit the uplink transmission with a spatial domain transmit filter associated with an RS having a best signal quality among the multiple RSs.

[0343] In some embodiments, the circuitry is further configured to disable application of the at least one first capability value set associated with the first correspondence if, within a certain period of time after transmitting the correspondence report, it fails to receive a message indicating the feedback status of the correspondence report or if it receives a message indicating a NACK for the correspondence report.

[0344] In some embodiments, terminal device 220 communicates with network device 210 by applying at least one second set of capability values ​​associated with a second correspondence relationship, and the circuitry is further configured to continue applying the at least one second set of capability values ​​associated with the second correspondence relationship after a period of time following sending the correspondence relationship report.

[0345] In some embodiments, terminal device 220 communicates with network device 210 by applying at least one second capability value set associated with a second correspondence relationship. The circuitry is further configured to, after transmitting the correspondence relationship report, continue to apply the at least one second capability value set associated with the second correspondence relationship until one of receiving a message from network device 210 indicating an ACKnowledgment for the correspondence relationship report or transmitting another correspondence relationship report to network device 210 after transmitting the correspondence relationship report.

[0346] In some embodiments, the circuitry is further configured to reset an accumulation of power control adjustment states in response to applying the first correspondence.

[0347] In some embodiments, the circuitry is further configured to generate the correspondence report based on a time limit parameter set by the network device 210 for obtaining the first correspondence.

[0348] In some embodiments, the correspondence report further indicates identity information for each of the capability value sets indicated in the correspondence report.

[0349] In some embodiments, the identity information indicates at least one of an index of a capability set, an index of a panel deployed on terminal device 220 and associated with the capability set, or a state of the capability set.

[0350] In some embodiments, the bit size of the identity information is determined based on at least one of a first number of capability value sets supported by the terminal device 220 or a second number of states of the capability value sets supported by the terminal device 220.

[0351] In some embodiments, the circuitry is further configured to transmit capability-related information of terminal device 220 to network device 210. The capability-related information indicates a plurality of capability value sets, and a capability value set among the plurality of capability value sets includes at least one of identity information of the capability value set, a maximum number of sounding reference signal (SRS) ports, a coherence type, a maximum number of uplink layers, a maximum number of downlink layers, a maximum number of RS ports, a maximum number of codewords, or a maximum number of MIMO layers.

[0352] In some embodiments, each of the plurality of capability value sets corresponds to a particular type of capability value set, and the capability-related information further indicates at least one of whether a symmetric antenna structure or an asymmetric antenna structure is deployed in the terminal device 220, or the respective number of capability value sets corresponding to each particular type of capability value set.

[0353] In some embodiments, the capability-related information further indicates an associative relationship between the plurality of capability value sets.

[0354] In some embodiments, the capability-related information further indicates at least one of whether the terminal device 220 supports applying two or more capability value sets in parallel, or the number of capability value sets supported to be applied in parallel by the terminal device 220.

[0355] In some embodiments, the capability-related information further indicates at least one of whether the terminal device 220 supports determining the feedback status of a correspondence report, whether the terminal device 220 supports reporting a correspondence report for downlink transmission, whether the terminal device 220 supports reporting the status of a capability value set, whether the terminal device 220 supports obtaining the first correspondence with a time limit, or the number of capability value sets included in a correspondence report supported by the terminal device 220.

[0356] In some embodiments, the circuitry is further configured to receive from the network device 210 at least one setting used by the terminal device 220, the at least one setting indicating at least one of an association relationship between at least one transmission parameter and a capability value set, a time domain behavior of the correspondence report, information regarding a time limit for obtaining the first correspondence, a reporting amount, or the number of capability value sets associated with one correspondence report.

[0357] In some embodiments, the at least one transmission parameter includes at least one of a resource for transmitting an SRS, a resource for transmitting a PUCCH, a transmission configuration indicator status, or a resource for transmitting a downlink RS.

[0358] In some embodiments, the circuitry is further configured to perform SRS transmission based on both the at least one setting currently applied in the terminal device 220 and one or more sets of capability values.

[0359] In some embodiments, when a value of a recurrence parameter included in an RS resource set is on, the circuitry is further configured to perform at least one of: disabling reporting of the correspondence report, or sending the correspondence report associated with one RS; sending the first correspondence report with one capability value set index regardless of the configured number of capability value set indexes; or sending the correspondence report without including information about an RS.

[0360] In some exemplary embodiments, terminal device 220 comprises circuitry configured to perform at least one of determining a default capability value set and performing an initial transmission with network device 210 by applying the default capability value set, or, if a fallback condition is met, falling back to applying the default capability value set after sending a correspondence report to network device 210, the correspondence report indicating the correspondence between the capability value set and the RS to network device 210.

[0361] In some embodiments, the default value set is one of a capability value set with a lower capability, a capability value set with a higher capability, a capability value set with a lower capability value set index, a capability value set with a higher capability value set index, a last used capability value set, a predefined capability value set, or a capability value set set by either terminal device 220 or network device 210.

[0362] In some embodiments, the circuitry is further configured to perform the initial transmission at least during a period between reporting the configuration of the capability set and transmitting the first correspondence report.

[0363] In some embodiments, the circuitry is further configured such that performing the initial transmission with the network device includes at least one of receiving a scheduling message from network device 210 generated according to a default capability value set, or sending an uplink transmission with network device 210 by applying a default capability value set.

[0364] In some embodiments, the circuitry is further configured to transmit information regarding the default performance score set during an RA procedure.

[0365] In some embodiments, the circuitry is further configured to determine that the fallback condition is met if the terminal device 220 fails to receive a message indicating an ACK for the correspondence report after a certain period of time has passed since the correspondence report was sent.

[0366] In some embodiments, the circuitry is further configured to determine that the fallback condition is met if, a certain period of time after transmitting the correspondence report, the terminal device 220 receives a message indicating an ACK for the correspondence report at a transmission opportunity for receiving the message.

[0367] In some embodiments, the circuitry is further configured to determine that a fallback condition is met if terminal device 220 receives a message indicating a NACK on the correspondence report.

[0368] In some embodiments, the circuitry is further configured to determine that a fallback condition is met if the period since transmitting the correspondence report exceeds a predefined period.

[0369] In some embodiments, the circuitry is further configured to determine that a fallback condition is met if the capability value set associated with the correspondence report is set to have a higher capability.

[0370] In some embodiments, the circuitry is further configured to determine that the fallback condition is met if the correspondence reports are aperiodic.

[0371] In some embodiments, the circuitry is further configured to determine that a fallback condition is met when a BWP switch, a CC switch, secondary cell activation, or cross cell scheduling occurs.

[0372] In some embodiments, the circuitry is further configured to determine that a fallback condition is met if terminal device 220 operates in DRX mode.

[0373] In some exemplary embodiments, network device 210 comprises circuitry configured to receive from terminal device 220 a correspondence report indicating a first correspondence between at least one first capability value set and at least one first RS, and to communicate with terminal device 220 according to a feedback status of the correspondence report, wherein the feedback status is one of ACK or NACK.

[0374] In some embodiments, the circuitry is further configured to transmit a message to terminal device 220, the message indicating the feedback status of the correspondence report and being at least one of a TCI activation command associated at least in part with the at least one RS indicated by the report, a PDCCH order for triggering an RA procedure, signaling for controlling transmit power of terminal device 220, a message triggering terminal device 220 to report a correspondence report, a message for activating SRS transmission, and a message for activating CSI report transmission.

[0375] In some embodiments, the circuitry further detects that the at least one first correspondence between at least one first capability value set and at least one first RS associated with the correspondence report is at least partially different from at least one second correspondence applied in the terminal device 220, that the at least one first correspondence between at least one first capability value set and at least one first RS associated with the correspondence report is at least partially different from at least one second correspondence applied in a last correspondence report, and that the at least one first capability value set associated with the correspondence report is at least partially different from at least one second correspondence applied in a last correspondence report. the correspondence report is configured to transmit the message indicating the feedback state of the correspondence report when at least one of the following applies: the at least one first RS associated with the correspondence report is at least partially different from at least one second RS currently applied in the terminal device 220; the at least one first RS is at least partially different from at least one second RS applied in the terminal device 220; the correspondence report is configured to have a specific time-domain behavior; or identity information of a capability value set among the at least one capability value set indicates a specific capability value set state.

[0376] In some embodiments, the status of the capability value set is one of the capability value set being used for the uplink, the capability value set being used for the downlink, or an application status of the capability value set indicating whether the capability value set has already been applied or will be applied.

[0377] In some embodiments, if network device 210 determines that the feedback status before the correspondence report is NACK, the circuitry is further configured to send a message to terminal device 220 that triggers terminal device 220 to report an aperiodic correspondence report or a semi-persistent correspondence report after receiving the correspondence report.

[0378] In some embodiments, the circuitry is configured to apply at least one first capability value set associated with a first correspondence in response to one of sending a message to the terminal device 220 indicating an ACK for the correspondence report or receiving an SRS after sending a message indicating an ACK to the terminal device 220.

[0379] In some embodiments, the circuitry is further configured to apply the at least one first set of capability values ​​associated with the first correspondence in response to one of receiving the correspondence report or a time period since receiving the correspondence report exceeding a preset time period.

[0380] In some embodiments, if there are multiple RSs indicated by the first correspondence relationship, the circuitry is further configured to receive the uplink transmission with a spatial domain transmit filter associated with an RS having a best signal quality among the multiple RSs.

[0381] In some embodiments, the circuitry is further configured to disable application of the at least one first capability value set associated with the first correspondence in accordance with a determination that the feedback status of the first correspondence report is NACK.

[0382] In some embodiments, network device 210 communicates with terminal device 220 by applying at least one second set of capability values ​​associated with a second correspondence relationship, and the circuitry is further configured to continue applying the at least one second set of capability values ​​associated with the second correspondence relationship after a period of time following receipt of the first correspondence relationship report.

[0383] In some embodiments, network device 210 communicates with terminal device 220 by applying at least one second capability value set associated with a second correspondence relationship. The circuitry is further configured to, after receiving the first correspondence relationship report, continue to apply the at least one second capability value set associated with the second correspondence relationship until one of: sending a message to terminal device 220 indicating an ACKnowledgment for the correspondence relationship report; or receiving another correspondence relationship report from terminal device 220 after receiving the correspondence relationship report.

[0384] In some embodiments, the correspondence report further indicates identity information for each of the capability value sets indicated in the correspondence report.

[0385] In some embodiments, the identity information indicates at least one of an index of a capability set, an index of a panel deployed on terminal device 220 and associated with the capability set, or a state of the capability set.

[0386] In some embodiments, the bit size of the identity information is determined based on at least one of a first number of capability value sets supported by the terminal device 220 or a second number of states of the capability value sets supported by the terminal device 220.

[0387] In some embodiments, the circuitry is further configured to receive capability-related information of terminal device 220 from terminal device 220. The capability-related information indicates a plurality of capability value sets, and a capability value set among the plurality of capability value sets includes at least one of identity information of the capability parameter set, a maximum number of sounding reference signal (SRS) ports, a coherence type, a maximum number of uplink layers, a maximum number of downlink layers, a maximum number of RS ports, a maximum number of codewords, or a maximum number of MIMO layers.

[0388] In some embodiments, each of the plurality of capability value sets corresponds to a particular type of capability value set, and the capability-related information further indicates at least one of whether a symmetric antenna structure or an asymmetric antenna structure is deployed in the terminal device 220, or the respective number of capability value sets corresponding to each particular type of capability value set.

[0389] In some embodiments, the capability-related information further indicates an associative relationship between the plurality of capability value sets.

[0390] In some embodiments, the capability-related information further indicates at least one of whether the terminal device 220 supports applying two or more capability value sets in parallel, or the number of capability value sets supported to be applied in parallel by the terminal device 220.

[0391] In some embodiments, the capability-related information further indicates at least one of whether the terminal device 220 supports determining the feedback status of a correspondence report, whether the terminal device 220 supports reporting a correspondence report for downlink transmission, whether the terminal device 220 supports reporting the status of a capability value set, whether the terminal device 220 supports obtaining the first correspondence with a time-limited requirement, or the number of capability value sets included in a correspondence report supported by the terminal device 220.

[0392] In some embodiments, the circuitry is further configured to transmit at least one setting to the terminal device 220 for use by the terminal device 220. The at least one setting indicates at least one of an association relationship between at least one transmission parameter and a capability value set, a time domain behavior of the correspondence report, information regarding a time limit for obtaining the first correspondence, or the number of capability value sets associated with one correspondence report.

[0393] In some embodiments, the at least one transmission parameter includes at least one of a resource for transmitting an SRS, a resource for transmitting a PUCCH, a transmission configuration indicator status, or a resource for transmitting a downlink RS.

[0394] In some embodiments, the correspondence reports are configured by the at least one setting to have a first period, the first period being aligned with a second period of the beam reports, and the first period being a multiple of the second period.

[0395] In some exemplary embodiments, the network device 220 comprises circuitry configured to perform at least one of determining a default capability value set and performing an initial transmission with the terminal device 220 by applying the default capability value set, or, if a fallback condition is met, falling back to applying the default capability value set after receiving a correspondence report from the terminal device 220, the correspondence report indicating a correspondence between a capability value set and an RS from the terminal device 220.

[0396] In some embodiments, the default value set is one of a capability value set with a lower capability, a capability value set with a higher capability, a capability value set with a lower capability value set index, a capability value set with a higher capability value set index, a last used capability value set, a predefined capability value set, or a capability value set set by either terminal device 220 or network device 210.

[0397] In some embodiments, the circuitry is further configured to perform the initial transmission at least during a period between reporting the configuration of the capability set and transmitting the first correspondence report.

[0398] In some embodiments, the circuitry is further configured such that performing the initial transmission with the terminal device 220 includes at least one of transmitting to the terminal device 220 a scheduling message generated according to a default capability value set, or receiving an uplink transmission from the terminal device 220 transmitted by applying a default capability value set.

[0399] In some embodiments, the circuitry is further configured to receive information regarding the default performance score set during an RA procedure.

[0400] In some embodiments, the circuitry is further configured to determine that the fallback condition is met if one of the following applies: a period since receiving the correspondence report exceeds a predefined period; the capability value set associated with the correspondence report is set to have a higher capability; the correspondence report is aperiodic; one of a BWP switch, a CC switch, secondary cell activation, and cross-cell scheduling has occurred; or the terminal device 220 has operated in a DRX mode.

[0401] 11 is a schematic block diagram of an apparatus 1100 suitable for implementing embodiments of the present disclosure. The apparatus 1100 may be considered as another exemplary implementation of the terminal 220 and the network device 210 shown in FIG. 2. Accordingly, the apparatus 1100 may be implemented in the terminal 220 and the network device 210, or as at least a part thereof.

[0402] As shown, the apparatus 1100 comprises a processor 1111, a memory 1120 coupled to the processor 1110, a suitable transmitter (TX) and receiver (RX) 1140 coupled to the processor 1110, and a communication interface coupled to the TX / RX 1140. The memory 1120 stores at least a portion of a program 1130. The TX / RX 1140 is used for bidirectional communication. The TX / RX 1140 has at least one antenna to facilitate communication, although the access nodes referred to herein may actually have multiple antennas. The communication interface may represent any interface required for communication with other network elements, such as an X2 interface for bidirectional communication between eNBs, an S1 interface for communication between a mobility management entity (MME) / serving gateway (S-GW) and an eNB, a Un interface for communication between an eNB and a relay node (RN), or a Uu interface for communication between an eNB and a terminal device.

[0403] The program 1130 is assumed to include program instructions that, when executed by the associated processor 1110, enable the device 1100 to operate according to embodiments of the present disclosure, as described herein with reference to Figures 2-10. The embodiments herein may be implemented by computer software executable by the processor 1110 of the device 1100, by hardware, or by a combination of software and hardware. The processor 1110 may be configured to implement various embodiments of the present disclosure. Furthermore, the combination of the processor 1110 and the memory 1120 may form a processing means 1150 suitable for implementing various embodiments of the present disclosure.

[0404] Memory 1120 may be of any type suitable for a local technology network and may be implemented using any suitable data storage technology, including, by way of non-limiting example, non-transitory computer-readable storage media, semiconductor-based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory, and removable memory. While only one memory 1120 is shown in device 1100, several physically distinct memory modules may be present within device 1100. Processor 1110 may be of any type suitable for a local technology network and may include, by way of non-limiting example, one or more of a general-purpose computer, a special-purpose computer, a microprocessor, a digital signal processor (DSP), and a processor based on a multi-core processor architecture. Device 1100 may have multiple processors, for example, application-specific integrated circuit chips time-slaved to a clock that synchronizes the main processor.

[0405] Overall, various embodiments of the present disclosure may be implemented in hardware or special purpose circuits, software, logic, or any combination thereof. Some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software executable by a controller, microprocessor, or other computing device. While various aspects of embodiments of the present disclosure have been illustrated and described using block diagrams, flowcharts, or other pictorial representations, it should be understood that the blocks, devices, systems, techniques, or methods described herein may be implemented, by way of non-limiting example, in hardware, software, firmware, special purpose circuits or logic, general purpose hardware or controller or other computing device, or any combination thereof.

[0406] The present disclosure also provides at least one computer program product tangibly stored on a non-transitory computer-readable storage medium. The computer program product includes computer-executable instructions, such as instructions included in program modules, that execute in a device on a target real or virtual processor to perform the processes or methods described above with reference to FIGS. 2 through 10. Generally, program modules include routines, programs, libraries, objects, classes, components, data structures, etc. that perform particular tasks or implement particular abstract data types. In various embodiments, the functionality of the program modules may be combined or split between program modules as desired. The machine-executable instructions of the program modules may be executed in local or distributed devices. In a distributed device, program modules may be located in both local and remote storage media.

[0407] Program code for carrying out the methods of the present disclosure may be written in any combination of one or more programming languages. These program codes may be provided to a processor or controller of a general-purpose computer, a special-purpose computer, or other programmable data processing device, and when executed by the processor or controller, cause the program code to implement the functions / acts specified in the flowcharts and / or block diagrams. The program code may run entirely on the machine, partially on the machine, as a separate software package, partially on the machine and partially on a remote machine, or entirely on a remote machine or server.

[0408] The above-described program code may be embodied on a machine-readable medium, which may be any tangible medium that can contain or store a program used by or associated with an instruction execution system, apparatus, or device. The machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. The machine-readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the aforementioned media. More specific examples of a machine-readable storage medium may include an electrical connection having one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above.

[0409] It should be noted that, although operations have been described in a particular order, it should not be understood that performing such operations in the particular order shown, or in any sequential order, or performing all of the operations described, is required to achieve desirable results. In some cases, multitasking and parallel processing may be advantageous. Similarly, while several specific implementation details are included in the above discussion, these should not be construed as limitations on the scope of the disclosure, but rather as descriptions of features that may be specific to particular embodiments. Some features that are described in the context of individual embodiments may also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment may also be implemented in multiple embodiments separately or in any suitable subcombination.

[0410] Although the present disclosure has been described in language specific to structural features and / or methodological acts, it should be understood that the present disclosure, as defined in the appended claims, is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims.

Claims

1. A user equipment (UE), means for transmitting a report regarding a Channel State Information (CSI) report to a network, the report including at least first information and second information corresponding to the first information, the first information including a CSI-RS Resource Indicator (CRI) or an SS / PBCH Block Resource Indicator (SSBRI), the second information including an index of a UE capability value set, the UE capability value set indicating a maximum number of supported Sounding Reference Signal (SRS) antenna ports, and the first information not being reported if a repetition parameter for a reference signal resource set is set to on; means for transmitting a first Radio Resource Control (RRC) message to the network, the first Radio Resource Control (RRC) message including capability information, the capability information including the UE capability value set indicating the maximum number of SRS antenna ports; means for receiving a second RRC message from the network, the second RRC message including configuration information, the configuration information including a report amount for the report. UE.

2. The report includes third information corresponding to the first information, and the third information includes Reference Signal Received Power (RSRP) or Signal to Interference and Noise Ratio (SINR); The UE of claim 1.

3. The configuration information includes time domain behavior related to the report.

3. The UE according to claim 1 or 2.

4. The time domain behavior is periodic, semi-persistent, or aperiodic. The UE of claim 3.

5. A receiving means for receiving a report on a Channel State Information (CSI) report from a user equipment (UE), the report including at least first information and second information corresponding to the first information, the first information including a CSI-RS Resource Indicator (CRI) or an SS / PBCH Block Resource Indicator (SSBRI), the second information including an index of a UE capability value set, the UE capability value set indicating a maximum number of supported Sounding Reference Signal (SRS) antenna ports, and the first information not being reported if a repetition parameter for a reference signal resource set is set to on; means for receiving a first Radio Resource Control (RRC) message from the UE, the first Radio Resource Control (RRC) message including capability information, the capability information including the UE capability value set indicating the maximum number of SRS antenna ports; means for transmitting a second RRC message including configuration information to the UE, the configuration information including a reporting amount of the report; RAN node.

6. The report includes third information corresponding to the first information, and the third information includes Reference Signal Received Power (RSRP) or Signal to Interference and Noise Ratio (SINR).

6. The RAN node of claim 5.

7. The configuration information includes time domain behavior related to the report.

7. A RAN node according to claim 5 or 6.

8. The time domain behavior is periodic, semi-persistent, or aperiodic.

8. The RAN node of claim 7.

Images