Method and device for receiving and transmitting information

The method optimizes SBFD operations by configuring distinct time domain resources for SRS sets and PUSCH, addressing inefficiencies in existing systems and enhancing scheduling efficiency and reducing interference.

WO2026071812A1PCT designated stage Publication Date: 2026-04-02SAMSUNG ELECTRONICS CO LTD
View PDF 1 Cites 0 Cited by

Patent Information

Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Filing Date
2025-09-29
Publication Date
2026-04-02

AI Technical Summary

Technical Problem

Existing wireless communication systems face challenges in efficiently managing subband non-overlapping full duplex (SBFD) operations, particularly in configuring and scheduling physical uplink shared channels (PUSCH) and sounding reference signals (SRS) to optimize transmission and reduce interference.

Method used

A method and apparatus for configuring and scheduling SBFD operations by defining distinct time domain resources for SRS resource sets, using SRI fields to indicate specific SRS resource sets based on conditions and configurations, ensuring efficient transmission of PUSCH and SRS resources without overlap.

Benefits of technology

Enhances scheduling efficiency and reduces interference in wireless communication systems by optimizing the use of time domain resources for PUSCH and SRS, thereby improving overall system performance.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure KR2025015339_02042026_PF_FP_ABST
    Figure KR2025015339_02042026_PF_FP_ABST
Patent Text Reader

Abstract

The disclosure relates to a 5G or 6G communication system for supporting a higher data transmission rate. The disclosure provides a method and device for receiving, from a base station (BS), information related to subband non-overlapping full duplex (SBFD); based on the information, identifying a type of symbol for symbols related to a Type 2 configured grant (CG) physical uplink shared channel (PUSCH) transmission associated with a latest activation downlink control information (DCI); performing the Type 2 CG PUSCH transmission in the symbols related to the type of symbol.
Need to check novelty before this filing date? Find Prior Art

Description

METHOD AND DEVICE FOR RECEIVING AND TRANSMITTING INFORMATION

[0001] The present application relates to the technical field of wireless communication, and more specifically, to a method and device for receiving and transmitting information.

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

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

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

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

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

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

[0008] In order to meet the increasing demand for wireless data communication services since the deployment of 4G communication systems, efforts have been made to develop improved 5G or pre-5G communication systems. Therefore, 5G or pre-5G communication systems are also called "Beyond 4G networks" or "Post-LTE systems".

[0009] In order to achieve a higher data rate, 5G communication systems are implemented in higher frequency (millimeter, mmWave) bands, e.g., 60 GHz bands. In order to reduce propagation loss of radio waves and increase a transmission distance, technologies such as beamforming, massive multiple-input multiple-output (MIMO), full-dimensional MIMO (FD-MIMO), array antenna, analog beamforming and large-scale antenna are discussed in 5G communication systems.

[0010] In addition, in 5G communication systems, developments of system network improvement are underway based on advanced small cell, cloud radio access network (RAN), ultra-dense network, device-to-device (D2D) communication, wireless backhaul, mobile network, cooperative communication, coordinated multi-points (CoMP), reception-end interference cancellation, etc.

[0011] In 5G systems, hybrid FSK and QAM modulation (FQAM) and sliding window superposition coding (SWSC) as advanced coding modulation (ACM), and filter bank multicarrier (FBMC), non-orthogonal multiple access (NOMA) and sparse code multiple access (SCMA) as advanced access technologies have been developed.

[0012] Embodiments of the present disclosure is to provide an apparatus and method for effectively providing a service in a wireless communication system.

[0013] An aspect of the disclosure provides a method performed by a user Equipment UE in a wireless communication system, the method includes receiving configuration information for subband non-overlapping full duplex SBFD, wherein the configuration information for SBFD indicates a first type time domain resource for SBFD; receiving configuration information for a sounding reference signal SRS resource set; obtaining an SRS resource indicator SRI and transmitting a physical uplink shared channel PUSCH based on the SRI; wherein when the SRI is indicated by downlink control information DCI scheduling the PUSCH, and the configuration information for the SRS resource set configures a first SRS resource set associated with the first type time domain resource and a second SRS resource set associated with the second type time domain resource, the DCI includes a first SRI field for indicating the first SRS resource set or the second SRS resource set and a second SRI for field indicating the second SRS resource set, and the second type time domain resource is a resource other than the first type time domain resource, wherein when a first condition is satisfied, a bitwidth of the second SRI field is determined based on a number of SRS resources in the second SRS resource set; and / or when a second condition is satisfied, the bitwidth of the second SRI field is 0; wherein the first condition includes at least one of the followings: in configuration information for the PUSCH, a second type configuration is configured; in one of one or more configured grant configuration information, a second type configuration is configured; the second condition includes at least one of the followings: in the configuration information for the PUSCH, a first type configuration is configured; in each of the one or more configured grant configuration information, a first type configuration is configured; wherein when the first type configuration is configured, the PUSCH is transmitted only on the same type of time domain resources; and / or when the second type configuration is configured, the PUSCH is transmitted on the same type or different types of time domain resources.

[0014] In an example, when the first condition is satisfied, the first SRI field indicates an SRS resource in the first SRS resource set; and / or when the second condition is satisfied, the SRS resource set indicated by the first SRI field is determined based on the type of the time domain resource where the PUSCH is located.

[0015] In an example, when the second condition is satisfied and the transmission of the PUSCH is in the first type time domain resource, the first SRI field indicates the first SRS resource set; and / or when the second condition is satisfied and the transmission of the PUSCH is in the second type time domain resource, the first SRI field indicates the second SRS resource set.

[0016] In an example, when the first condition is satisfied and the PUSCH is transmitted only in one type of time domain resources, the SRI field corresponding to the other type of time domain resources is ignored.

[0017] In an example, the SRI includes a first SRI and a second SRI, wherein the first SRI is indicated by the first SRI field and the second SRI is indicated by the second SRI field; wherein the SRI is associated with the transmission of an SRS resource in the SRS resource set indicated by the corresponding SRI field, wherein the transmission of the SRS resource is in the same type of time domain resource as those associated with the corresponding SRS resource set, and the transmission of the SRS resource is the latest transmission, and the transmission of the SRS resource is before a physical downlink control channel PDCCH carrying the SRI.

[0018] In an example, when the first SRS resource set is periodic or semi-persistent, an SRS resource in the first SRS resource set is transmitted in the first type time domain resource, and / or the SRS resource in the first SRS resource set is not transmitted in the second type time domain resource; or when the first SRS resource set is aperiodic, the UE expects the transmission of the SRS resource in the first SRS resource set to be in the first type time domain resource; and / or when the second SRS resource set is periodic or semi-persistent, an SRS resource in the second SRS resource set is transmitted in the second type time domain resource, or the SRS resource in the second SRS resource set is not transmitted in the first type time domain resource; and / or when the second SRS resource set is aperiodic, the UE expects the transmission of the SRS resource in the second SRS resource set to be in the second type time domain resource.

[0019] In an example, the method further includes receiving the configuration information for the physical uplink shared channel PUSCH, wherein the PUSCH is transmitted based on the configured grant configuration information, and in case that the configuration information for the PUSCH includes the configured grant configuration information indicating a Type 1 PUSCH, when the configured grant configuration information is configured with a type configuration parameter and the type configuration parameter indicates the first type time domain resource, the configured grant configuration information is configured for indicating the SRI, wherein the SRI indicates a resource in the first SRS resource set; or when the configured grant configuration information is configured with the type configuration parameter and the type configuration parameter indicates the second type time domain resource, the configured grant configuration information is configured for indicating the SRI, wherein the SRI indicates a resource in the second SRS resource set; or when the configured grant configuration information is not configured with the type configuration parameter, the SRI includes a first SRI and a second SRI, and the configured grant configuration information is configured for indicating the first SRI and for indicating the second SRI, wherein the first SRI indicates a resource in the first SRS resource set and the second SRI indicates a resource of the second SRS resource set, the type configuration parameter is used for indicating the type of the time domain resource allowed for uplink transmission.

[0020] In an example, in case that the configuration information for the PUSCH includes the configured grant configuration information indicating a Type 2 PUSCH, the SRI includes the first SRI and the second SRI, and the configured grant configuration information is configured with first information indicating the first SRI and second information indicating the second SRI, wherein the first information indicates the resource in the first SRS resource set and the second information indicates the resource in the second SRS resource set, wherein when the transmission of the PUSCH is in the first type time domain resource, the transmission of the PUSCH is determined based on the first information; and / or when the transmission of the PUSCH is in the second type time domain resource, the transmission of the PUSCH is determined based on the second information.

[0021] In an example, when the first type configuration is configured or the second type configuration is configured and the PUSCH is in only one type of time domain resources, the SRI is associated with the transmission of the SRS resource in the SRS resource set; wherein the transmission of the SRS resource is the latest transmission.

[0022] In an example, when the second type configuration is configured and the PUSCH is in two types of time domain resources, the SRI is associated with a first transmission and a second transmission of the SRS resource in the SRS resource set; wherein the first transmission is in the first type time domain resource, and the first transmission is the latest transmission; and the second transmission is in the second type time domain resource, and the second transmission is the latest transmission.

[0023] In an example, the SRS resource set is for non-codebook-based transmission or for codebook-based transmission.

[0024] In an example, when the SRS resource set is for the non-codebook-based transmission, the SRS resource set is associated with a channel state information reference signal CSI-RS resource for calculating a precoder for the transmission of the SRS; when the CSI-RS resource is periodic or semi-persistent, the precoder for the transmission of the SRS resource is determined based on the reception of the CSI-RS resource in the same type of time domain resource as the time domain resource where the transmission of the SRS resource is located; and / or when the CSI-RS resource is aperiodic and the SRS resource is aperiodic, determine whether to update the precoder for the transmission of the SRS resource based on the type of the time domain resource where the transmission of the SRS resource is located and the type of the time domain resource where the CSI-RS resource is located.

[0025] In an example, when the transmission of the SRS resource and the reception of the CSI-RS resource are in different types of time domain resources and the first type configuration is configured, the precoder for the transmission of the SRS resource is not updated based on the CSI-RS resource; and / or when the transmission of the SRS resource and the reception of the CSI-RS resource are in the same type of time domain resources, the precoder for the transmission of the SRS resource is updated based on the CSI-RS resource.

[0026] Another aspect of the disclosure provides a method performed by a base station in a wireless communication system, the method includes transmitting configuration information for subband non-overlapping full duplex SBFD, wherein the configuration information for SBFD indicates a first type time domain resource for SBFD; transmitting configuration information for a sounding reference signal SRS resource set; transmitting an SRS resource indicator SRI and receiving a PUSCH based on the SRI; wherein when the SRI is indicated by downlink control information DCI scheduling the PUSCH, and the configuration information for the SRS resource set configures a first SRS resource set associated with the first type time domain resource and a second SRS resource set associated with the second type time domain resource, the DCI includes a first SRI field for indicating the first SRS resource set or the second SRS resource set and a second SRI for field indicating the second SRS resource set, and the second type time domain resource is a resource other than the first type time domain resource, wherein when a first condition is satisfied, a bitwidth of the second SRI field is determined based on a number of SRS resources in the second SRS resource set; and / or when a second condition is satisfied, the bitwidth of the second SRI field is 0; wherein the first condition includes at least one of the followings: in configuration information for the PUSCH, a second type configuration is configured; in one of one or more configured grant configuration information, a second type configuration is configured; the second condition includes at least one of the followings: in the configuration information for the PUSCH, a first type configuration is configured; in each of the one or more configured grant configuration information, a first type configuration is configured; wherein when the first type configuration is configured, the PUSCH is transmitted only on the same type of time domain resources; and / or when the second type configuration is configured, the PUSCH is transmitted on the same type or different types of time domain resources.

[0027] In an example, when the first condition is satisfied, the first SRI field indicates an SRS resource in the first SRS resource set; and / or when the second condition is satisfied, the SRS resource set indicated by the first SRI field is determined based on the type of the time domain resource where the PUSCH is located.

[0028] In an example, when the second condition is satisfied and the transmission of the PUSCH is in the first type time domain resource, the first SRI field indicates the first SRS resource set; and / or when the second condition is satisfied and the transmission of the PUSCH is in the second type time domain resource, the first SRI field indicates the second SRS resource set.

[0029] In an example, when the first condition is satisfied and the PUSCH is transmitted only in one type of time domain resources, the SRI field corresponding to the other type of time domain resources is ignored.

[0030] In an example, the SRI includes a first SRI and a second SRI, wherein the first SRI is indicated by the first SRI field and the second SRI is indicated by the second SRI field; wherein the SRI is associated with the transmission of an SRS resource in the SRS resource set indicated by the corresponding SRI field, wherein the transmission of the SRS resource is in the same type of time domain resource as those associated with the corresponding SRS resource set, and the transmission of the SRS resource is the latest transmission, and the transmission of the SRS resource is before a physical downlink control channel PDCCH carrying the SRI.

[0031] In an example, when the first SRS resource set is periodic or semi-persistent, an SRS resource in the first SRS resource set is transmitted in the first type time domain resource, and / or the SRS resource in the first SRS resource set is not transmitted in the second type time domain resource; or when the first SRS resource set is aperiodic, the UE expects the transmission of the SRS resource in the first SRS resource set to be in the first type time domain resource; and / or when the second SRS resource set is periodic or semi-persistent, an SRS resource in the second SRS resource set is transmitted in the second type time domain resource, or the SRS resource in the second SRS resource set is not transmitted in the first type time domain resource; and / or when the second SRS resource set is aperiodic, the UE expects the transmission of the SRS resource in the second SRS resource set to be in the second type time domain resource.

[0032] In an example, the method further includes transmitting the configuration information for the physical uplink shared channel PUSCH, wherein the PUSCH is transmitted based on the configured grant configuration information, and in case that the configuration information for the PUSCH includes the configured grant configuration information indicating a Type 1 PUSCH, when the configured grant configuration information is configured with a type configuration parameter and the type configuration parameter indicates the first type time domain resource, the configured grant configuration information is configured for indicating the SRI, wherein the SRI indicates a resource in the first SRS resource set; or when the configured grant configuration information is configured with the type configuration parameter and the type configuration parameter indicates the second type time domain resource, the configured grant configuration information is configured for indicating the SRI, wherein the SRI indicates a resource in the second SRS resource set; or when the configured grant configuration information is not configured with the type configuration parameter, the SRI includes a first SRI and a second SRI, and the configured grant configuration information is configured for indicating the first SRI and for indicating the second SRI, wherein the first SRI indicates a resource in the first SRS resource set and the second SRI indicates a resource of the second SRS resource set, the type configuration parameter is used for indicating the type of the time domain resource allowed for uplink transmission.

[0033] In an example, in case that the configuration information for the PUSCH includes the configured grant configuration information indicating a Type 2 PUSCH, the SRI includes the first SRI and the second SRI, and the configured grant configuration information is configured with first information indicating the first SRI and second information indicating the second SRI, wherein the first information indicates the resource in the first SRS resource set and the second information indicates the resource in the second SRS resource set, wherein when the transmission of the PUSCH is in the first type time domain resource, the transmission of the PUSCH is determined based on the first information; and / or when the transmission of the PUSCH is in the second type time domain resource, the transmission of the PUSCH is determined based on the second information.

[0034] In an example, when the first type configuration is configured or the second type configuration is configured and the PUSCH is in only one type of time domain resources, the SRI is associated with the transmission of the SRS resource in the SRS resource set; wherein the transmission of the SRS resource is the latest transmission.

[0035] In an example, when the second type configuration is configured and the PUSCH is in two types of time domain resources, the SRI is associated with a first transmission and a second transmission of the SRS resource in the SRS resource set; wherein the first transmission is in the first type time domain resource, and the first transmission is the latest transmission; and the second transmission is in the second type time domain resource, and the second transmission is the latest transmission.

[0036] In an example, the SRS resource set is for non-codebook-based transmission or for codebook-based transmission.

[0037] In an example, when the SRS resource set is for the non-codebook-based transmission, the SRS resource set is associated with a channel state information reference signal CSI-RS resource for calculating a precoder for the transmission of the SRS; when the CSI-RS resource is periodic or semi-persistent, the precoder for the transmission of the SRS resource is determined based on the reception of the CSI-RS resource in the same type of time domain resource as the time domain resource where the transmission of the SRS resource is located; and / or when the CSI-RS resource is aperiodic and the SRS resource is aperiodic, determine whether to update the precoder for the transmission of the SRS resource based on the type of the time domain resource where the transmission of the SRS resource is located and the type of the time domain resource where the CSI-RS resource is located.

[0038] In an example, when the transmission of the SRS resource and the reception of the CSI-RS resource are in different types of time domain resources and the first type configuration is configured, the precoder for the transmission of the SRS resource is not updated based on the CSI-RS resource; and / or when the transmission of the SRS resource and the reception of the CSI-RS resource are in the same type of time domain resources, the precoder for the transmission of the SRS resource is updated based on the CSI-RS resource.

[0039] Another aspect of the disclosure provides a user equipment including a transceiver; and a controller coupled with the transceiver and configured to perform the above methods which may be performed by the user equipment.

[0040] Yet another aspect of the disclosure provides a base station including a transceiver; and a controller coupled with the transceiver and configured to perform the above methods which may be performed by the controller.

[0041] The method provided by the application improves the transceiver performance of terminal devices served by the base station adopting SBFD operations, thereby improving the scheduling efficiency of the communication system

[0042] Embodiments of the present disclosure is to provide an apparatus and method for effectively providing a service in a wireless communication system.

[0043] The above and other aspects, features, and advantages of the disclosure will become more apparent from the following Detailed Description when taken in conjunction with the accompanying drawings.

[0044] FIG. 1 illustrates an overall structure of an example wireless communication network according to various embodiments of the disclosure;

[0045] FIG. 2a respectively illustrates a transmission path 200 in a wireless communication network according to various embodiments of the disclosure;

[0046] FIG. 2b respectively illustrates a reception path 250 in a wireless communication network according to various embodiments of the disclosure;

[0047] FIG. 3a respectively illustrates a structure of a user equipment in a wireless communication network according to various embodiments of the disclosure;

[0048] FIG. 3b respectively illustrates a structure of a a base station in a wireless communication network according to various embodiments of the disclosure;

[0049] FIG. 4 illustrates a method 400 performed by a user equipment (UE) according to various embodiments of the disclosure;

[0050] FIG. 5 illustrates a method performed by a base station according to various embodiments of the disclosure;

[0051] FIG. 6 illustrates a structure 600 of a user equipment according to various embodiments of the disclosure;

[0052] FIG. 7 illustrates a structure 700 of a base station according to various embodiments of the disclosure.

[0053] The following description with reference to the accompanying drawings is provided to assist in a comprehensive understanding of various embodiments of the disclosure as defined by the claims and their equivalents. It includes various specific details to assist in that understanding but these are to be regarded as merely exemplary. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the various embodiments described herein can be made without departing from the scope and spirit of the disclosure. In addition, descriptions of well-known functions and constructions may be omitted for clarity and conciseness.

[0054] The terms and words used in the following description and claims are not limited to the bibliographical meanings, but, are merely used by the inventor to enable a clear and consistent understanding of the disclosure. Accordingly, it should be apparent to those skilled in the art that the following description of various embodiments of the disclosure is provided for illustration purpose only and not for the purpose of limiting the disclosure as defined by the appended claims and their equivalents.

[0055] It is to be understood that the singular forms "a," "an," and "the" include plural referents unless the context clearly dictates otherwise. Thus, for example, reference to "a component surface" includes reference to one or more of such surfaces.

[0056] The term "include" or "may include" refers to the existence of a corresponding disclosed function, operation or component which can be used in various embodiments of the disclosure and does not limit one or more additional functions, operations, or components. The terms such as "include" and / or "have" may be construed to denote a certain characteristic, number, step, operation, constituent element, component or a combination thereof, but may not be construed to exclude the existence of or a possibility of addition of one or more other characteristics, numbers, steps, operations, constituent elements, components or combinations thereof.

[0057] The term "or" used in various embodiments of the disclosure includes any or all of combinations of listed words. For example, the expression "A or B" may include A, may include B, or may include both A and B.

[0058] Unless defined differently, all terms used herein, which include technical terminologies or scientific terminologies, have the same meaning as that understood by a person skilled in the art to which the disclosure belongs. Such terms as those defined in a generally used dictionary are to be interpreted to have the meanings equal to the contextual meanings in the relevant field of art, and are not to be interpreted to have ideal or excessively formal meanings unless clearly defined in the disclosure.

[0059] The various embodiments of the disclosure can be applied to various communication systems, such as: global system for mobile communications (GSM) system, code division multiple access (CDMA) system, broadband code division multiple access (WCDMA) system, general packet radio service (GPRS), long term evolution (LTE) system Frequency division duplex (FDD) systems, time division duplex (TDD) systems, universal mobile telecommunications systems (UMTS), global interoperability for microwave access (WiMAX) communication systems, fifth generation (5G) systems or new wireless (NR) systems, etc. In addition, the various embodiments of the disclosure can be applied to future oriented communication technologies.

[0060] FIG. 1 illustrates an example wireless networK100 according to various embodiments of the disclosure. The embodiment of the wireless networK100 shown in FIG. 1 is for illustration only. Other embodiments of the wireless networK100 can be used without departing from the scope of the disclosure.

[0061] The wireless networK100 includes a gNodeB (gNB) 101, a gNB 102, and a gNB 103. gNB 101 communicates with gNB 102 and gNB 103. gNB 101 also communicates with at least one Internet Protocol (IP) networK130, such as the Internet, a private IP network, or other data networks.

[0062] Depending on a type of the network, other well-known terms such as "base station" or "access point" can be used instead of "gNodeB" or "gNB". For convenience, the terms "gNodeB" and "gNB" are used in this patent document to refer to network infrastructure components that provide wireless access for remote terminals. And depending on the type of the network, other well-known terms such as "mobile station", "user station", "remote terminal", "wireless terminal" or "user apparatus" can be used instead of "user equipment" or "UE". For convenience, the terms "user equipment" and "UE" are used in this patent document to refer to remote wireless devices that wirelessly access the gNB, no matter whether the UE is a mobile device (such as a mobile phone or a smart phone) or a fixed device (such as a desktop computer or a vending machine).

[0063] gNB 102 provides wireless broadband access to the networK130 for a first plurality of User Equipments (UEs) within a coverage area 120 of gNB 102. The first plurality of UEs include a UE 111, which may be located in a Small Business (SB); a UE 112, which may be located in an enterprise (E); a UE 113, which may be located in a WiFi Hotspot (HS); a UE 114, which may be located in a first residence (R); a UE 115, which may be located in a second residence (R); a UE 116, which may be a mobile device (M), such as a cellular phone, a wireless laptop computer, a wireless PDA, etc. GNB 103 provides wireless broadband access to networK130 for a second plurality of UEs within a coverage area 125 of gNB 103. The second plurality of UEs include a UE 115 and a UE 116. In some embodiments, one or more of gNBs 101-103 can communicate with each other and with UEs 111-116 using 5G, Long Term Evolution (LTE), LTE-A, WiMAX or other advanced wireless communication technologies.

[0064] The dashed lines show approximate ranges of the coverage areas 120 and 125, and the ranges are shown as approximate circles merely for illustration and explanation purposes. It should be clearly understood that the coverage areas associated with the gNBs, such as the coverage areas 120 and 125, may have other shapes, including irregular shapes, depending on configurations of the gNBs and changes in the radio environment associated with natural obstacles and man-made obstacles.

[0065] As will be described in more detail below, one or more of gNB 101, gNB 102, and gNB 103 include a 2D antenna array as described in embodiments of the disclosure. In some embodiments, one or more of gNB 101, gNB 102, and gNB 103 support codebook designs and structures for systems with 2D antenna arrays.

[0066] Although FIG. 1 illustrates an example of the wireless networK100, various changes can be made to FIG. 1. The wireless networK100 can include any number of gNBs and any number of UEs in any suitable arrangement, for example. Furthermore, gNB 101 can directly communicate with any number of UEs and provide wireless broadband access to the networK130 for those UEs. Similarly, each gNB 102-103 can directly communicate with the networK130 and provide direct wireless broadband access to the networK130 for the UEs. In addition, gNB 101, 102 and / or 103 can provide access to other or additional external networks, such as external telephone networks or other types of data networks.

[0067] FIGs. 2a and 2b illustrate example wireless transmission and reception paths according to the disclosure. In the following description, the transmission path 200 can be described as being implemented in a gNB, such as gNB 102, and the reception path 250 can be described as being implemented in a UE, such as UE 116. However, it should be understood that the reception path 250 can be implemented in a gNB and the transmission path 200 can be implemented in a UE. In some embodiments, the reception path 250 is configured to support codebook designs and structures for systems with 2D antenna arrays as described in embodiments of the disclosure.

[0068] The transmission path 200 includes a channel coding and modulation block 205, a Serial-to-Parallel (S-to-P) block 210, a size N Inverse Fast Fourier Transform (IFFT) block 215, a Parallel-to-Serial (P-to-S) block 220, a cyclic prefix addition block 225, and an up-converter (UC) 230. The reception path 250 includes a down-converter (DC) 255, a cyclic prefix removal block 260, a Serial-to-Parallel (S-to-P) block 265, a size N Fast Fourier Transform (FFT) block 270, a Parallel-to-Serial (P-to-S) block 275, and a channel decoding and demodulation block 280.

[0069] In the transmission path 200, the channel coding and modulation block 205 receives a set of information bits, applies coding (such as Low Density Parity Check (LDPC) coding), and modulates the input bits (such as using Quadrature Phase Shift Keying (QPSK) or Quadrature Amplitude Modulation (QAM)) to generate a sequence of frequency-domain modulated symbols. The Serial-to-Parallel (S-to-P) block 210 converts (such as demultiplexes) serial modulated symbols into parallel data to generate N parallel symbol streams, where N is a size of the IFFT / FFT used in gNB 102 and UE 116. The size N IFFT block 215 performs IFFT operations on the N parallel symbol streams to generate a time domain output signal. The Parallel-to-Serial block 220 converts (such as multiplexes) parallel time domain output symbols from the Size N IFFT block 215 to generate a serial time domain signal. The cyclic prefix addition block 225 inserts a cyclic prefix into the time domain signal. The up-converter 230 modulates (such as up-converts) the output of the cyclic prefix addition block 225 to an RF frequency for transmission via a wireless channel. The signal can also be filtered at a baseband before switching to the RF frequency.

[0070] The RF signal transmitted from gNB 102 arrives at UE 116 after passing through the wireless channel, and operations in reverse to those at gNB 102 are performed at UE 116. The down-converter 255 down-converts the received signal to a baseband frequency, and the cyclic prefix removal block 260 removes the cyclic prefix to generate a serial time domain baseband signal. The Serial-to-Parallel block 265 converts the time domain baseband signal into a parallel time domain signal. The Size N FFT block 270 performs an FFT algorithm to generate N parallel frequency-domain signals. The Parallel-to-Serial block 275 converts the parallel frequency-domain signal into a sequence of modulated data symbols. The channel decoding and demodulation block 280 demodulates and decodes the modulated symbols to recover the original input data stream.

[0071] Each of gNBs 101-103 may implement a transmission path 200 similar to that for transmitting to UEs 111-116 in the downlink, and may implement a reception path 250 similar to that for receiving from UEs 111-116 in the uplink. Similarly, each of UEs 111-116 may implement a transmission path 200 for transmitting to gNBs 101-103 in the uplink, and may implement a reception path 250 for receiving from gNBs 101-103 in the downlink.

[0072] Each of the components in FIGs. 2a and 2b can be implemented using only hardware, or using a combination of hardware and software / firmware. As a specific example, at least some of the components in FIGs. 2a and 2b may be implemented in software, while other components may be implemented in configurable hardware or a combination of software and configurable hardware. For example, the FFT block 270 and IFFT block 215 may be implemented as configurable software algorithms, in which the value of the size N may be modified according to the implementation.

[0073] Furthermore, although described as using FFT and IFFT, this is only illustrative and should not be interpreted as limiting the scope of the disclosure. Other types of transforms can be used, such as Discrete Fourier transform (DFT) and Inverse Discrete Fourier Transform (IDFT) functions. It should be understood that for DFT and IDFT functions, the value of variable N may be any integer (such as 1, 2, 3, 4, etc.), while for FFT and IFFT functions, the value of variable N may be any integer which is a power of 2 (such as 1, 2, 4, 8, 16, etc.)

[0074] Although FIGs. 2a and 2b illustrate examples of wireless transmission and reception paths, various changes may be made to FIGs. 2a and 2b. For example, various components in FIGs. 2a and 2b can be combined, further subdivided or omitted, and additional components can be added according to specific requirements. Furthermore, FIGs. 2a and 2b are intended to illustrate examples of types of transmission and reception paths that can be used in a wireless network. Any other suitable architecture can be used to support wireless communication in a wireless network.

[0075] FIG. 3a illustrates an example UE 116 according to the disclosure. The embodiment of UE 116 shown in FIG. 3a is for illustration only, and UEs 111-115 of FIG. 1 can have the same or similar configuration. However, a UE has various configurations, and FIG. 3a does not limit the scope of the disclosure to any specific implementation of the UE.

[0076] UE 116 includes an antenna 301, a radio frequency (RF) transceiver 302, a transmission (TX) processing circuit 303, a microphone 304, and a reception (RX) processing circuit 305. UE 116 also includes a speaker 306, a controller / processor 307, an input / output (I / O) interface 308, an input device(s) 309, a display 310, and a memory 311. The memory 311 includes an operating system (OS) 312 and one or more applications 313.

[0077] The RF transceiver 302 receives an incoming RF signal transmitted by a gNB of the wireless networK100 from the antenna 301. The RF transceiver 302 down-converts the incoming RF signal to generate an intermediate frequency (IF) or baseband signal. The IF or baseband signal is transmitted to the RX processing circuit 305, where the RX processing circuit 305 generates a processed baseband signal by filtering, decoding and / or digitizing the baseband or IF signal. The RX processing circuit 305 transmits the processed baseband signal to speaker 306 (such as for voice data) or to controller / processor 307 for further processing (such as for web browsing data).

[0078] The TX processing circuit 303 receives analog or digital voice data from microphone 304 or other outgoing baseband data (such as network data, email or interactive video game data) from controller / processor 307. The TX processing circuit 303 encodes, multiplexes, and / or digitizes the outgoing baseband data to generate a processed baseband or IF signal. The RF transceiver 302 receives the outgoing processed baseband or IF signal from the TX processing circuit 303 and up-converts the baseband or IF signal into an RF signal transmitted via the antenna 301.

[0079] The controller / processor 307 can include one or more processors or other processing devices and execute an OS 312 stored in the memory 311 in order to control the overall operation of UE 116. For example, the controller / processor 307 can control the reception of forward channel signals and the transmission of backward channel signals through the RF transceiver 302, the RX processing circuit 305 and the TX processing circuit 303 according to well-known principles. In some embodiments, the controller / processor 307 includes at least one microprocessor or microcontroller.

[0080] The controller / processor 307 is also capable of executing other processes and programs residing in the memory 311, such as operations for channel quality measurement and reporting for systems with 2D antenna arrays as described in embodiments of the disclosure. The controller / processor 307 can move data into or out of the memory 311 as required by an execution process. In some embodiments, the controller / processor 307 is configured to execute the application 313 based on the OS 312 or in response to signals received from the gNB or the operator. The controller / processor 307 is also coupled to an I / O interface 308, where the I / O interface 308 provides UE 116 with the ability to connect to other devices such as laptop computers and handheld computers. I / O interface 308 is a communication path between these accessories and the controller / processor 307.

[0081] The controller / processor 307 is also coupled to the input device(s) 309 and the display 310. An operator of UE 116 can input data into UE 116 using the input device(s) 309. The display 310 may be a liquid crystal display or other display capable of presenting text and / or at least limited graphics (such as from a website). The memory 311 is coupled to the controller / processor 307. A part of the memory 311 can include a random access memory (RAM), while another part of the memory 311 can include a flash memory or other read-only memory (ROM).

[0082] Although FIG. 3a illustrates an example of UE 116, various changes can be made to FIG. 3a. For example, various components in FIG. 3a can be combined, further subdivided or omitted, and additional components can be added according to specific requirements. As a specific example, the controller / processor 307 can be divided into a plurality of processors, such as one or more central processing units (CPUs) and one or more graphics processing units (GPUs). Furthermore, although FIG. 3a illustrates that the UE 116 is configured as a mobile phone or a smart phone, UEs can be configured to operate as other types of mobile or fixed devices.

[0083] FIG. 3b illustrates an example gNB 102 according to the disclosure. The embodiment of gNB 102 shown in FIG. 3b is for illustration only, and other gNBs of FIG. 1 can have the same or similar configuration. However, a gNB has various configurations, and FIG. 3b does not limit the scope of the disclosure to any specific implementation of a gNB. It should be noted that gNB 101 and gNB 103 can include the same or similar structures as gNB 102.

[0084] As shown in FIG. 3b, gNB 102 includes a plurality of antennas 370a-370n, a plurality of RF transceivers 372a-372n, a transmission (TX) processing circuit 374, and a reception (RX) processing circuit 376. In certain embodiments, one or more of the plurality of antennas 370a-370n include a 2D antenna array. gNB 102 also includes a controller / processor 378, a memory 380, and a backhaul or network interface 382.

[0085] RF transceivers 372a-372n receive an incoming RF signal from antennas 370a-370n, such as a signal transmitted by UEs or other gNBs. RF transceivers 372a-372n down-convert the incoming RF signal to generate an IF or baseband signal. The IF or baseband signal is transmitted to the RX processing circuit 376, where the RX processing circuit 376 generates a processed baseband signal by filtering, decoding and / or digitizing the baseband or IF signal. RX processing circuit 376 transmits the processed baseband signal to controller / processor 378 for further processing.

[0086] The TX processing circuit 374 receives analog or digital data (such as voice data, network data, email or interactive video game data) from the controller / processor 378. TX processing circuit 374 encodes, multiplexes and / or digitizes outgoing baseband data to generate a processed baseband or IF signal. RF transceivers 372a-372n receive the outgoing processed baseband or IF signal from TX processing circuit 374 and up-convert the baseband or IF signal into an RF signal transmitted via antennas 370a-370n.

[0087] The controller / processor 378 can include one or more processors or other processing devices that control the overall operation of gNB 102. For example, the controller / processor 378 can control the reception of forward channel signals and the transmission of backward channel signals through the RF transceivers 372a-372n, the RX processing circuit 376 and the TX processing circuit 374 according to well-known principles. The controller / processor 378 can also support additional functions, such as higher layer wireless communication functions. For example, the controller / processor 378 can perform a Blind Interference Sensing (BIS) process such as that performed through a BIS algorithm, and decode a received signal from which an interference signal is subtracted. A controller / processor 378 may support any of a variety of other functions in gNB 102. In some embodiments, the controller / processor 378 includes at least one microprocessor or microcontroller.

[0088] The controller / processor 378 is also capable of executing programs and other processes residing in the memory 380, such as a basic OS. The controller / processor 378 can also support channel quality measurement and reporting for systems with 2D antenna arrays as described in embodiments of the disclosure. In some embodiments, the controller / processor 378 supports communication between entities such as web RTCs. The controller / processor 378 can move data into or out of the memory 380 as required by an execution process.

[0089] The controller / processor 378 is also coupled to the backhaul or network interface 382. The backhaul or network interface 382 allows gNB 102 to communicate with other devices or systems through a backhaul connection or through a network. The backhaul or network interface 382 can support communication over any suitable wired or wireless connection(s). For example, when gNB 102 is implemented as a part of a cellular communication system, such as a cellular communication system supporting 5G or new radio access technology or NR, LTE or LTE-A, the backhaul or network interface 382 can allow gNB 102 to communicate with other gNBs through wired or wireless backhaul connections. When gNB 102 is implemented as an access point, the backhaul or network interface 382 can allow gNB 102 to communicate with a larger network, such as the Internet, through a wired or wireless local area network or through a wired or wireless connection. The backhaul or network interface 382 includes any suitable structure that supports communication through a wired or wireless connection, such as an Ethernet or an RF transceiver.

[0090] The memory 380 is coupled to the controller / processor 378. A part of the memory 380 can include an RAM, while another part of the memory 380 can include a flash memory or other ROMs. In certain embodiments, a plurality of instructions, such as the BIS algorithm, are stored in the memory. The plurality of instructions are configured to cause the controller / processor 378 to execute the BIS process and decode the received signal after subtracting at least one interference signal determined by the BIS algorithm.

[0091] As will be described in more detail below, the transmission and reception paths of gNB 102 (implemented using RF transceivers 372a-372n, TX processing circuit 374 and / or RX processing circuit 376) support aggregated communication with FDD cells and TDD cells.

[0092] Although FIG. 3b illustrates an example of gNB 102, various changes may be made to FIG. 3b. For example, gNB 102 can include any number of each component shown in FIG. 3a. As a specific example, the access point can include many backhaul or network interfaces 382, and the controller / processor 378 can support routing functions to route data between different network addresses. As another specific example, although shown as including a single instance of the TX processing circuit 374 and a single instance of the RX processing circuit 376, gNB 102 can include multiple instances of each (such as one for each RF transceiver).

[0093] In the disclosure, the term "channel state information (CSI)" may be used interchangeably with the terms "CSI parameter" or "CSI quantity".

[0094] In the disclosure, CSI may include at least one of the followings: CSI reference signal (CSI-RS) resource indicator (CRI), rank indicator (RI), precoding matrix indicator (PMI), channel quality indicator (CQI), layer indicator (LI), synchronization signal (SS) / physical broadcast channel (PBCH) block resource indicator (SSBRI), layer 1-reference signal received power (L1-RSRP), layer 1-single to interference noise ratio (L1-SINR), CapabilityIndex.

[0095] In the disclosure, the term "CSI reporting configuration" may be used interchangeably with the terms "CSI reporting configuration information" or "information for CSI reporting configuration" or "information for configuring CSI report".

[0096] In the disclosure, the CSI may be the CSI reported by the UE in a report, or in a report instance.

[0097] In the disclosure, the term "reference signal" may be used interchangeably with the term "reference signal resource".

[0098] In the disclosure, the reference signal may include at least one of the followings: a reference signal for synchronization, a reference signal for demodulation (e.g., a demodulation reference signal (DM-RS), a reference signal for obtaining of the channel state, a reference signal for phase tracking (e.g., phase tracking reference signal (PT-RS)), a reference signal for mobility, a reference signal for positioning, a reference signal for channel measurement, a reference signal for interference measurement, a reference signal for sounding. Optionally, the reference signal for synchronization includes at least one of the followings: a primary synchronization signal (PSS), a secondary synchronization signal (SSS). Optionally, the reference signal for synchronization may include a synchronization signal / physical broadcast channel block (SS / PBCH block, SSB). Optionally, the reference signal for demodulation may include at least one of the followings: a reference signal for data channel demodulation and a reference signal for control channel demodulation. Optionally, the data channel may include at least one of the followings: a physical downlink shared channel (PDSCH) and a physical uplink shared channel (PUSCH). Optionally, the control channel may include at least one of the followings: a physical downlink control channel (PDCCH) and a physical uplink control channel (PUCCH). Optionally, the reference signal for obtaining of the channel state may include at least one of the followings: a reference signal for tracking, a reference signal for CSI acquisition, and a reference signal for beam management. Optionally, the reference signal for beam management includes at least one of the followings: a reference signal for obtaining L1-RSRP, a reference signal for obtaining L1-SINR. Optionally, obtaining L1-RSRP may be computing L1-RSRP. Optionally, obtaining L1-SINR may be computing L1-SINR. In the disclosure, the "reference signal for sounding" may be referred as a sounding reference signal (SRS).

[0099] In the disclosure, the term "beam" may include at least one of the followings: "quasi co-location (QCL) parameter", "transmission configuration indication (TCI) state", "spatial domain filter", "antenna port", "transmission and reception point (TRP)", "reference signal", "beam information", "beam index". Optionally, a beam and another beam being the same may be a beam and another beam being quasi co-located.

[0100] In the disclosure, an antenna port can be defined such that the channel over which a symbol on the antenna port is conveyed can be inferred from the channel over which another symbol on the same antenna port is conveyed.

[0101] In the disclosure, two antenna ports are said to be quasi co-located if the large-scale properties of the channel over which a symbol on one antenna port is conveyed can be inferred from the channel over which a symbol on the other antenna port is conveyed. Optionally, the large-scale properties include one or more of delay spread, Doppler spread, Doppler shift, average gain, average delay, and spatial Rx parameters.

[0102] In the disclosure, the term "QCL parameter" may be used interchangeably with the terms "QCL information", "QCL assumption", "QCL configuration", "QCL configuration and / or QCL type". Optionally, the QCL parameter may include / represent at least one of the followings: Doppler shift, Doppler spread, average delay, delay spread, spatial reception parameter. The spatial reception parameter may be a parameter for spatial reception. Optionally, the QCL parameter may include a combination of different types of parameters. For example, the QCL parameter may include Doppler shift, Doppler spread, average delay and delay spread, and such QCL parameter may be referred as QCL parameter type A. For example, the QCL parameter may include Doppler shift and Doppler spread, and such QCL parameter may be referred as QCL parameter type B. For example, the QCL parameter may include Doppler shift and average delay, and such QCL parameter may be referred as QCL parameter type C. For example, the QCL parameter may include spatial reception parameter, and such QCL parameter may be referred as QCL parameter type D. For example, two antenna ports are said to be quasi co-located if the large-scale properties of the channel over which a symbol on one antenna port is conveyed can be inferred from the channel over which a symbol on the other antenna port is conveyed. Optionally, the large-scale properties include one or more of delay spread, Doppler spread, Doppler shift, average gain, average delay, and spatial Rx parameters. For example, two antenna ports are said to be quasi co-located subject to QCL parameter type D if spatial Rx parameters of the channel over which a symbol on one antenna port is conveyed can be inferred from the channel over which a symbol on the other antenna port is conveyed.

[0103] In the disclosure, the term "TCI state" may be used interchangeably with the terms "TCI state configuration" or "TCI state configuration information" or "information for configuring the TCI state" or "information for indicating the TCI state". Optionally, the TCI state may be a unified TCI state. Optionally, the TCI state may be at least one of an uplink TCI state (UL TCI state), a downlink TCI state (DL TCI state), a joint TCI state. Optionally, the unified TCI state may be an uplink TCI state (UL TCI state) and a downlink TCI state (DL TCI state), or a joint TCI state.

[0104] Optionally, a TCI state may include parameters configuring quasi co-location relation, these parameters configure the relation between the reference signal (e.g., one or two reference signals, or one or two downlink reference signals) and at least one of the followings: a demodulation reference signal (DM-RS) port of the PDSCH, a DM-RS port of the PDCCH, a CSI-RS port of a CSI-RS resource. Optionally, a quasi co-location relation is configured by a higher layer parameter (e.g., qcl-Type1) for the first downlink reference signal. Optionally, a quasi co-location relation is configured by a higher layer parameter (e.g., qcl-Type2) for the second downlink reference signal. In case of two downlink reference signals, the QCL types are not the same, regardless of whether the references are to the same DL RS or different DL RSs.

[0105] In the disclosure, the term "spatial domain filter" may be used interchangeably with the terms "spatial filter" or "uplink transmission spatial domain filter" or "spatial domain filter for uplink transmission" or "spatial domain filter for downlink reception".

[0106] In the disclosure, the term "transmission occasion of reference signal resource" may be used interchangeably with the term "occasion of reference signal resource" or "reception occasion of reference signal resource" or "transmission occasion of reference signal" or "occasion of reference signal" or "reception occasion of reference signal".

[0107] In the disclosure, the term "UE capability" may be used interchangeably with the terms "UE feature" or "UE feature group" or "UE capability parameter" or "reported UE capability" or "UE capability signaling" or "reported UE capability parameter".

[0108] In the disclosure, a time domain resource may include / correspond to several time domain units.

[0109] In the disclosure, a time domain unit may be one of: a frame, a subframe, a slot, a sub-slot, a symbol. Optionally, the sub-slot may be a subset of a slot in time domain. For example, symbols included in the sub-slot are a subset of symbols included in the slot. Optionally, in the disclosure, the time domain unit may be one of: a second, a millisecond, a microsecond, a nanosecond, and a sample.

[0110] In the disclosure, a frequency domain resource may include / correspond to several frequency domain units.

[0111] In the disclosure, a frequency domain unit may be at least one of a band a subband a component carrier (CC), a bandwidth part (BWP), a resource block, a resource block group (RBG), a subcarrier, a carrier, a frequency band a frequency range, a cell, a serving cell. The resource block may be a physical resource block (PRB) or a common resource block (CRB). The frequency range may be frequency range 1, frequency range 2 (e.g., frequency range 2-1 and / or frequency range 2-2).

[0112] In the disclosure, a time-frequency unit may be one of: a resource element (RE), a resource element group (REG). The resource element group may include one or more resource elements. For example, the resource element group may include 6 or 12 resource elements.

[0113] In the disclosure, the starting time domain position of a channel or signal or resource is an earlier position in time domain, and the ending time domain position of a channel or signal or resource is a later position in time domain.

[0114] In the disclosure, the starting frequency domain position of a channel or signal or resource is a lower position in frequency domain, and the ending frequency domain position of a channel or signal or resource is a higher position in frequency domain.

[0115] In the disclosure, the term "PDCCH" may be used interchangeably with the terms "downlink control channel" or "control channel for downlink transmission" or "control channel for downlink".

[0116] In the disclosure, the term "PDCCH" may be used interchangeably with the term "PDCCH candidate".

[0117] In the disclosure, the term "PDSCH" may be used interchangeably with the terms "downlink data channel" or "data channel for downlink transmission" or "data channel for downlink".

[0118] In the disclosure, the term "PUCCH" may be used interchangeably with the terms "uplink control channel" or "control channel for uplink transmission" or "control channel for uplink".

[0119] In the disclosure, the term "PUSCH" may be used interchangeably with the terms "uplink data channel" or "data channel for uplink transmission" or "data channel for uplink".

[0120] In the disclosure, the term "downlink control information (DCI)" may be used interchangeably with the terms "DCI format" or "control information for downlink".

[0121] In the disclosure, the term "uplink control information (UCI)" may be used interchangeably with the term "control information for uplink".

[0122] In the disclosure, detecting DCI includes: receiving and / or decoding DCI.

[0123] In the disclosure, the term "information bits of DCI / UCI" may be used interchangeably with the terms "information bits associated with DCI / UCI" or "information bits included in DCI / UCI" or "information bits corresponding to DCI / UCI". Optionally, the information bits associated with DCI / UCI may include information bits of the DCI / UCI and check bits (for example, cyclic redundancy check (CRC) bits) corresponding to the DCI / UCI. Optionally, the information bits associated with DCI / UCI may include information bits of the DCI / UCI and bits (for example, cyclic redundancy check (CRC) bits) for checking the DCI / UCI.

[0124] In the disclosure, the term "information bits of PDSCH / PUSCH" may be used interchangeably with the term "information bits associated with PDSCH / PUSCH" or "information bits carried by PDSCH / PUSCH" or "information bits of TB included in PDSCH / PUSCH" or "information bits of TB carried by PDSCH / PUSCH". Optionally, the information bits associated with the information bits carried by PDSCH / PUSCH may include the information bits of TB carried by PDSCH / PUSCH and the check bits (for example, cyclic redundancy check (CRC) bits) corresponding to the TB. Optionally, the information bits associated with PDSCH / PUSCH may include information bits of PDSCH / PUSCH and bits (for example, cyclic redundancy check (CRC) bits) for checking the TB carried by the PDSCH / PUSCH.

[0125] In the disclosure, the term "size of information field" may be used interchangeably with the terms "bitwidth of information field" or "number of information bits in information field".

[0126] In the disclosure, the information bits of the DCI may be the information bits included in the DCI, or the information bits associated with the DCI, or the payload of the DCI.

[0127] In the disclosure, the existence of an information field may be that the size of the information field is greater than 0 bit. The absence of an information field may be that the size of the information field is equal to 0 bit.

[0128] In the disclosure, the value x of an information field may correspond to the (x+1)-th codepoint of the information field, x 0. The term "value of an information field" may be interchangeable with the term "codepoint of an information field". The term "value x of an information field" may be interchangeable with the term "(x+1)-th codepoint of an information field", where x≥0.

[0129] In the disclosure, the term "control resource set (CORESET)" may be used interchangeably with the terms "control resource" or "resource for receiving control information" or "resource for monitoring PDCCH" or "resource for detecting control information".

[0130] In the disclosure, the term "search space" may be used interchangeably with the terms "PDCCH search space" or "PDCCH search space set" or "PDCCH candidate search space" or "PDCCH candidate search space set" or "search space for searching PDCCH" or "search space for searching PDCCH candidate" or "search space set for searching PDCCH candidate" or "search space set for searching PDCCH candidate". Optionally, the search space may be a common search space (CSS) or a UE-specific search space (USS). Optionally, the search space may be used for detecting DCI. Optionally, the search space may be used for detecting DCI format.

[0131] In the disclosure, the term "PDCCH candidate associated with search space" may be used interchangeably with the term "PDCCH candidate in search space".

[0132] In the disclosure, the modulation scheme associated with the PDCCH candidate may be the modulation scheme used by the corresponding PDCCH candidate. The aggregation level associated with the PDCCH candidate may be the aggregation level of the corresponding PDCCH candidate.

[0133] In the disclosure, the UE may monitor the PDCCH (or monitor the PDCCH candidate) in PDCCH monitoring occasion(s). Optionally, the PDCCH monitoring occasion may be one or more (consecutive) time domain units. Optionally, the PDCCH monitoring occasion may be an occasion for monitoring the PDCCH, or an occasion for monitoring the PDCCH candidate.

[0134] In the disclosure, monitoring the PDCCH candidate may be receiving the PDCCH candidate and / or decoding according to the monitored DCI format.

[0135] In the disclosure, the DCI format may be at least one of the followings: DCI format 0_0, DCI format 0_1, DCI format 0_2, DCI format 0_3, DCI format 1_0, DCI format 1_1, DCI format 1_2, and DCI format 1_3. In the disclosure, the type of the DCI format may be one of the followings: DCI format 0_0, DCI format 0_1, DCI format 0_2, DCI format 0_3, DCI format 1_0, DCI format 1_1, DCI format 1_2, DCI format 1_3.

[0136] In the disclosure, hybrid automatic repeat request (HARQ) information may be hybrid automatic repeat request-acknowledgement (HARQ-ACK) information.

[0137] In the disclosure, the PDCCH may carry the DCI and / or the CRC corresponding to the DCI, or the DCI and / or the CRC corresponding to the DCI may be in the PDCCH. Optionally, the CRC may be scrambled in a specific manner. For example, optionally, the CRC may be scrambled based on a radio network temporary identifier (RNTI). Two PDCCHs having the same scrambling may be these two PDCCHs being scrambled by the same RNTI. Optionally, the RNTI may be one of a cell radio network temporary identifier (C-RNTI), a configured scheduling radio network temporary identifier (CS-RNTI).

[0138] In the disclosure, the term "transport block (TB) is a retransmission" may be used interchangeably with the terms "TB is not a new transmission" or "TB is a retransmission TB" or "PUSCH is a PUSCH retransmission" or "new data indicator (NDI) toggles" or "NDI=1". In the disclosure, the term "TB is a new transmission" may be used interchangeably with the terms "TB is not a retransmission" or "TB is a new transmission TB" or "PUSCH is a PUSCH new transmission / initial transmission" or "NDI does not toggle" or "NDI=0". The NDI may be NDI of TB, or NDI of HARQ process, or NDI in DCI, or NDI in DCI format. The NDI toggling may be the NDI provided in the associated HARQ information has been toggled compared to the value in the previous transmission of this TB of this HARQ process. In the disclosure, "NDI=0" may be DCI in PDCCH with CRC scrambled by CS-RNTI with NDI=0. In the disclosure, "NDI=1" may be DCI in PDCCH with CRC scrambled by CS-RNTI with NDI=1.

[0139] In the disclosure, the term "initial transmission of data channel" may be used interchangeably with the terms "new transmission of transport block TB" or "new transmission of transport block TB in data channel" or "NDI=0" or "NDI toggles". Optionally, the new transmission of the data channel may be a data channel scheduled by a DCI format, where the "new data indicator (NDI)" in the DCI format toggles. When the new transmission of the data channel corresponds to the configured grant PUSCH (or semi-Persistent scheduling (SPS) PDSCH) or when the CRC of the scheduling DCI for the data channel is CS-RNTI scrambled, NDI in the DCI format scheduling the data channel=0. The new transmission and retransmission of the TB correspond to the same HARQ process. In the disclosure, "NDI=0" may be DCI in PDCCH with CRC scrambled by CS-RNTI with NDI=0.

[0140] In the disclosure, the term "retransmission of data channel" may be used interchangeably with the terms "retransmission of transport block TB" or "retransmission of transport block TB in data channel" or "NDI=1" or "NDI does not toggle". When the new transmission corresponding to the retransmission of the data channel is dynamically scheduled, the retransmission of the data channel refers to the data channel scheduled by DCI format, where the "new data indicator (NDI)" in the DCI format does not toggle. The NDI toggling may be the value of the NDI provided in the associated HARQ information has been toggled compared to the value in the previous transmission of this TB of this HARQ process. When the new transmission corresponding to the retransmission of the data channel is the configured grant PUSCH (or SPS PDSCH), or when the CRC of the scheduling DCI for the data channel is CS-RNTI scrambled, the retransmission of the data channel may be a data channel scheduled by a DCI format, where NDI in the DCI format=1. The new transmission and retransmission of the TB correspond to the same HARQ process. In the disclosure, "NDI=0" may be DCI in PDCCH with CRC scrambled by CS-RNTI with NDI=0. In the disclosure, "NDI=1" may be DCI in PDCCH with CRC scrambled by CS-RNTI with NDI=1.

[0141] In the disclosure, a higher layer parameter includes at least one of a radio resource control (RRC) parameter, a media access control (MAC)-control element (CE) (MAC-CE) parameter. The RRC parameter may be a parameter configured / indicated by RRC signaling. The MAC-CE parameter may be a parameter indicated / activated by MAC-CE signaling. Optionally, information being configured by a higher layer parameter may be the information being indicated / activated by the higher layer parameter.

[0142] In the disclosure, higher layer signaling includes at least one of the RRC parameter and the parameter indicated by MAC-CE; or the higher layer signaling may include at least one of RRC signaling and MAC-CE signaling. Optionally, information being configured by higher layer signaling may be the information being indicated / activated by the higher layer signaling.

[0143] In the disclosure, the UE obtaining configuration information may be the UE receiving / being configured with the configuration information. In the disclosure, "obtaining configuration information" may be used interchangeably with the terms "receiving configuration information" or "being configured with configuration information".

[0144] In the disclosure, a cell includes at least one of the followings: a serving cell, a candidate cell, a primary cell, a secondary cell, and a special cell.

[0145] In the disclosure, when the DCI schedules a channel or signal, a cell receiving or transmitting the channel or signal may be referred as a scheduled cell. A cell where the DCI is detected or a cell where the DCI is monitored / received may be referred as a scheduling cell.

[0146] In the disclosure, when the DCI schedules a channel or signal, a BWP receiving or transmitting the channel or signal may be referred as a scheduled BWP. A BWP where the DCI is detected, or a BWP where the PDCCH associated with the DCI is monitored / received may be referred as a scheduling BWP.

[0147] In some cases, the base station may enhance the coverage of the communication system or reduce the delay through duplex. Duplex may include subband non-overlapping full duplex (SBFD). For example, a subband non-overlapping full duplex mode may be adopted in a time division duplex (TDD) frequency band (for example, in an unpaired spectrum). Subband non-overlapping full duplex may refer to dividing the bandwidth (e.g., carrier bandwidth) of a communication node (e.g., a base station) into more than one subband (e.g., without overlapping between subbands), and uplink and downlink communication may be performed simultaneously on different subbands.

[0148] In the disclosure, the term "time division duplex (TDD) configuration information" may be used interchangeably with the terms "TDD uplink / downlink configuration information" or "information for configuring slot format".

[0149] In the disclosure, the term "SBFD configuration information" may be used interchangeably with the terms "configuration information used for SBFD" or "configuration information for the SBFD" or "configuration information for the SBFD operation" or "configuration information for the SBFD operation of base station".

[0150] In the disclosure, the term "subband non-overlapping full duplex" may be used interchangeably with "subband full duplex".

[0151] In the disclosure, the term "uplink subband" may be used interchangeably with the terms "frequency domain resource corresponding to uplink subband" or "frequency domain position corresponding to uplink subband" or "frequency domain resource of uplink subband" or "frequency domain resource for uplink" or "frequency domain position for uplink" or "frequency domain resource for uplink transmission" or "frequency domain position for uplink transmission".

[0152] In the disclosure, the term "downlink subband" may be used interchangeably with the terms "frequency domain resource corresponding to downlink subband" or "frequency domain position corresponding to downlink subband" or "frequency domain resource of downlink subband" or "frequency domain resource for downlink" or "frequency domain position for downlink" or "frequency domain resource for downlink reception" or "frequency domain position for downlink reception".

[0153] In the disclosure, the term "frequency domain resource corresponding to guardband" may be used interchangeably with the terms "frequency domain position corresponding to guardband" or "frequency domain resource of guardband" or "frequency domain resource between (boundaries of) uplink subband and downlink subband" or "frequency domain position between (boundaries of) uplink subband and downlink subband" or "frequency domain resource for protecting / isolating uplink subband and downlink subband".

[0154] In the disclosure, the term "SBFD cell" may be used interchangeably with the term "first cell", but the name of "SBFD cell" is not limited by the disclosure.

[0155] In the disclosure, "determining measurement" may be determining the result of the measurement, or obtaining the result of the measurement, or obtaining the measurement based on the reference signal, or obtaining the measurement based on measurement resource(s), or obtaining the measurement for determining CSI.

[0156] In the disclosure, "determining channel measurement" may be determining the result of the channel measurement, or obtaining the result of the channel measurement, or obtaining the channel measurement based on the reference signal, or obtaining the channel measurement based on measurement resource(s), or obtaining the channel measurement for determining CSI.

[0157] In the disclosure, "determining interference measurement" may be determining the result of the interference measurement, or obtaining the result of the interference measurement, or obtaining the interference measurement based on the reference signal, or obtaining the interference measurement based on measurement resource(s), or obtaining the interference measurement for determining CSI.

[0158] In the disclosure, the term "uplink channel associated with CSI report" may be used interchangeably with the terms "uplink channel corresponding to CSI report" or "uplink channel carrying CSI report".

[0159] In the disclosure, the term "SBFD cell" may be used interchangeably with "SBFD serving cell".

[0160] Exemplary embodiments of the disclosure are further described below in conjunction with the accompanying drawings.

[0161] In order to enhance the scheduling efficiency of wireless communication systems, a base station needs to use non-overlapping subband full duplex (SBFD) operation to simultaneously transmit and receive for multiple terminal devices on different frequency domain resources. However, how to further enhance the transceiver performance of terminal devices served by the base station adopting SBFD operations is a problem to be solved.

[0162] FIG. 4 illustrates a method 400 performed by a user equipment (UE) according to various embodiments of the disclosure. The method 400 includes: at 401, the UE receives configuration information for subband non-overlapping full duplex (SBFD), wherein the configuration information for the SBFD indicates an SBFD time domain resource, the SBFD time domain resource is a first type time domain resource, and a resource other than the SBFD time domain resource is a second type time domain resource; at 402, the UE receives configuration information for configuring a sounding reference signal (SRS) resource set; at 403, the UE obtains an SRS resource indicator (SRI) and transmits a PUSCH based on the SRI, wherein the SRI is used for determining an SRS resource in the SRS resource set, wherein the type of the time domain resource where the transmission of the SRS resource associated with the SRI is located is the same as the type of the time domain resource where the transmission of the PUSCH is located. Each step in the method 400 shown in FIG. 4 is described in detail below.

[0163] In some cases, the UE may obtain / receive / be configured with SBFD configuration information. Optionally, the UE may receive / obtain / be configured with the SBFD configuration information via common signaling (e.g., common RRC signaling) or dedicated signaling (e.g., dedicated RRC signaling). Optionally, the SBFD configuration information may be configuration information associated with the SBFD. For example, the SBFD configuration information may be configuration information for the SBFD. For example, the SBFD configuration information may be configuration information associated with SBFD operation (of the base station). For example, the SBFD configuration information may be configuration information for indicating a time domain resource and / or a frequency domain resource associated with the SBFD operation. Optionally, the UE receives the SBFD configuration information in RRC_CONNECTED state. Optionally, the UE may receive the SBFD configuration information in RRC_IDLE / RRC_INACTIVE state.

[0164] * Optionally, a cell (e.g., serving cell) corresponding to / associated with the SBFD configuration information / where the SBFD configuration information is located / for may be referred to as an SBFD cell.

[0165] ** Optionally, the cell corresponding to / associated with the SBFD configuration information may be a cell that performs the SBFD operation associated with the SBFD configuration. Optionally, the cell corresponding to / associated with the SBFD configuration information may be a primary cell (e.g., PCell) or a special cell (e.g., a SpCell). Optionally, the cell corresponding to / associated with the SBFD configuration information may be a secondary cell (e.g., SCell). Optionally, the cell corresponding to / associated with the SBFD configuration information may be a cell where the time domain resource and / or the frequency domain resource associated with the SBFD configuration information are located / correspond to. Optionally, the cell corresponding to / associated with the SBFD configuration information may be a cell where the time domain resource and / or the frequency domain resource associated with the SBFD configuration information are applied / used. Optionally, the cell corresponding to / associated with the SBFD configuration information may be the cell where the SBFD configuration information is received, or the cell where the SBFD configuration information is configured.

[0166] * Optionally, the SBFD configuration information may indicate / correspond to / be associated with the frequency domain resource and / or the (corresponding / associated) time domain resource. Optionally, the time domain resource corresponding to / associated with the frequency domain resource refer to the time domain resource on which the frequency domain resource configured by the SBFD configuration information is applicable / effective / workable. Optionally, the time domain resource corresponding to / associated with the frequency domain resource refers to the time domain resource on which the frequency domain resource configured by the SBFD configuration information is applied / used (by the UE).

[0167] ** Optionally, the SBFD configuration information may indicate the frequency domain resource (associated with / corresponding to the SBFD time domain resource). The frequency domain resource indicated by / configured by / associated with the SBFD configuration information may be referred as the SBFD frequency domain resource. Optionally, the SBFD configuration information may indicate at least one of a frequency domain resource corresponding to an uplink subband, a frequency domain resource corresponding to a downlink subband and a frequency domain resource corresponding to a guardband. Optionally, the SBFD frequency domain resource may include at least one of the frequency domain resource corresponding to the uplink subband the frequency domain resource corresponding to the downlink subband and the frequency domain resource corresponding to the guardband. The frequency domain units included in the frequency domain resource are described below by taking PRB as an example. Optionally, the frequency domain resource corresponding to the uplink subband may include one or more consecutive PRBs, or a group of consecutive PRBs. Optionally, the frequency domain resource corresponding to the downlink subband may include one or more PRBs, or one or two groups of consecutive PRBs. Optionally, the frequency domain resource corresponding to the guardband may include one PRB or a group of consecutive PRBs or two groups of consecutive PRBs. Optionally, the uplink subband may be a subband for uplink (e.g., uplink transmission). Optionally, the uplink subband may be a frequency domain resource for uplink (e.g., uplink transmission). Optionally, the downlink subband may be a subband for downlink (e.g., downlink reception). Optionally, the downlink subband may be a frequency domain resource for downlink (e.g., downlink reception). Optionally, the frequency domain resource corresponding to the guardband may be determined based on the frequency domain resource corresponding to the uplink subband and / or the frequency domain resource corresponding to the downlink subband (and the carrier bandwidth of the SBFD cell). Optionally, the frequency domain resource corresponding to the downlink subband may be determined based on the frequency domain resource corresponding to the uplink subband and / or the frequency domain resource corresponding to the guardband (and the carrier bandwidth of the SBFD cell). Optionally, the frequency domain resource corresponding to the downlink subband may include one or more PRBs, or one or two groups of consecutive PRBs.

[0168] *** Optionally, the SBFD frequency domain resource is determined based on the SBFD configuration information and a reference subcarrier spacing parameter indicated by the TDD configuration information (e.g., the reference subcarrier spacing parameter referenceSubcarrierSpacing included in the TDD configuration information) (for the cell). For example, the SBFD frequency domain resource is determined based on (the parameter associated with the frequency domain indicated by) the SBFD configuration information and the reference subcarrier spacing parameter (e.g., referenceSubcarrierSpacing) included in the TDD configuration information (for the cell). The method may reuse the parameter indicated by the TDD configuration information to determine the SBFD frequency domain resource, saving signaling overhead and improving the efficiency of the communication system.

[0169] *** Optionally, the SBFD frequency domain resource is determined based on the reference subcarrier spacing parameter indicated by the SBFD configuration information (e.g., the reference subcarrier spacing parameter referenceSubcarrierSpacing included in the SBFD configuration information). For example, the SBFD time domain resource is determined based on the reference subcarrier spacing parameter (e.g., referenceSubcarrierSpacing) included in the SBFD configuration information. The method may utilize the SBFD configuration information to determine the SBFD frequency domain resource, which facilitates the base station to flexibly perform the SBFD operation, improving the efficiency of the communication system.

[0170] *** Optionally, on the SBFD frequency domain resource, the part of the uplink BWP within the frequency domain resource corresponding to the uplink subband associated with the SBFD frequency domain resource may be / is allowed for uplink transmission. Optionally, on the SBFD time domain resource, the part of the uplink BWP not within the frequency domain resource corresponding to the uplink subband associated with the SBFD frequency domain resource may not be / is not allowed for uplink transmission. The method defines the scheduling restriction based on the SBFD configuration, which facilitates the base station to schedule flexibly, improving the efficiency of the communication system.

[0171] *** Optionally, on the SBFD frequency domain resource, the part of the downlink BWP within the frequency domain resource corresponding to the downlink subband associated with the SBFD frequency domain resource may be / is allowed for downlink reception. Optionally, on the SBFD time domain resource, the part of the downlink BWP not within the frequency domain resource corresponding to the downlink subband associated with the SBFD frequency domain resource may not be / is not allowed for downlink reception. The method defines the scheduling restriction based on the SBFD configuration, which facilitates the base station to schedule flexibly, improving the efficiency of the communication system.

[0172] ** Optionally, the SBFD configuration information may indicate / configure / be associated with time domain resource. The time domain resource indicated by / configured by / associated with the SBFD configuration information may be referred as the SBFD time domain resource. In the disclosure, the time domain resource indicated by / configured by / associated with the SBFD configuration information may be referred as a first type time domain resource, and the name of the time domain resource indicated by / configured by / associated with the SBFD configuration information is not limited by the present application. The time domain resource other than the SBFD time domain resource (or a part of the time domain resource other than the SBFD time domain resource) may be referred as a non-SBFD time domain resource; or the time domain resource that is not the SBFD time domain resource may be referred as the non-SBFD time domain resource; or the time domain resource outside the SBFD time domain resource and within the downlink slot / downlink symbol and / or flexible slot / flexible symbol indicated / configured by the base station are referred as the non-SBFD time domain resource, or the time domain resource within the uplink slot / uplink symbol indicated / configured by the base station are referred as the non-SBFD time domain resource. In the disclosure, the non-SBFD time domain resource may be referred as a second type time domain resource, and the name of the non-SBFD time domain resource is not limited by the present application. The SBFD time domain resource may include several time domain units. Optionally, the SBFD time domain resource is not on the uplink slot and / or uplink symbol indicated by common information. Optionally, the SBFD time domain resource is on the downlink slot and / or downlink symbol indicated by the base station, and / or the SBFD time domain resource is on the flexible slot and / or flexible symbol indicated / configured by the base station. Optionally, the non-SBFD time domain resource is not on the uplink slot or uplink symbol indicated by the common information. Optionally, the non-SBFD time domain resource is on the downlink slot and / or downlink symbol indicated by the base station, and / or the non-SBFD time domain resource is on the flexible slot and / or flexible symbol indicated / configured by the base station. Optionally, the UE may obtain at least one of the uplink symbol, the uplink slot, the downlink symbol, the downlink slot, the flexible symbol, and the flexible slot indicated by the base station via the TDD configuration information. The TDD configuration information includes the TDD configuration information for the cell (e.g., TDD-UL-DL-ConfigurationCommon) and / or the TDD configuration information for the UE (tdd-UL-DL-ConfigurationDedicated). In the disclosure, the SBFD time domain resource and the non-SBFD time domain resource may be referred as two types of the time domain resource, i.e., the first type time domain resource and the second type time domain resource described above. For uplink (or uplink transmission, transmission of the uplink channel / uplink signal), the non-SBFD time domain resource may be an uplink time domain resource (for example, an uplink symbol and / or an uplink slot indicated by the TDD configuration information). For downlink (or downlink reception, reception of the downlink channel / downlink signal), the non-SBFD time domain resource may be a downlink time domain resource (for example, a downlink symbol and / or a downlink slot indicated by the TDD configuration information). If one time domain resource is in the SBFD time domain resource and the other time domain resource is in the non-SBFD time domain resource, it is considered that these two time domain resources are of different types. If one time domain resource is in the SBFD time domain resource and the other time domain resource is also in the SBFD time domain resource, it is considered that these two time domain resources are of the same type. If one time domain resource is in the non-SBFD time domain resource and the other time domain resource is also in the non-SBFD time domain resource, it is considered that these two time domain resources are of the same type.

[0173] *** Optionally, the SBFD time domain resource is determined based on the SBFD configuration information and the reference subcarrier spacing parameter indicated by the TDD configuration information (e.g., the reference subcarrier spacing parameter referenceSubcarrierSpacing included in the TDD configuration information) (for the cell). For example, the SBFD time domain resource is determined based on (the parameter associated with the time domain resource indicated by) the SBFD configuration information and the reference subcarrier spacing parameter (e.g., referenceSubcarrierSpacing) included in the TDD configuration information (for the cell). The method may reuse the parameter indicated by the TDD configuration information to determine the SBFD time domain resource, saving signaling overhead and improving the efficiency of the communication system.

[0174] *** Optionally, the SBFD time domain resource is determined based on the reference subcarrier spacing parameter indicated by the SBFD configuration information (e.g., the reference subcarrier spacing parameter referenceSubcarrierSpacing included in the SBFD configuration information). For example, the SBFD time domain resource is determined based on the reference subcarrier spacing parameter (e.g., referenceSubcarrierSpacing) included in the SBFD configuration information. The method may utilize the SBFD configuration information to determine the SBFD time domain resource, which facilitates the base station to flexibly perform the SBFD operation, improving the efficiency of the communication system.

[0175] *** Optionally, on the BWP, if a symbol / slot partially overlaps with the SBFD time domain resource, the symbol / slot may not be / is not allowed for transmission / reception. Optionally, on the BWP, if a symbol / slot fully overlaps with the SBFD time domain resource, the symbol / slot may be / is allowed for transmission / reception. The method defines the scheduling restriction based on the SBFD configuration, which facilitates the base station to schedule flexibly, improving the efficiency of the communication system.

[0176] Optionally, the UE may receive a first type configuration and / or a second type configuration. The first type configuration and the second type configuration may be referred to as first type configuration information and second type configuration information, respectively. In the disclosure, names of the "first type configuration" and the "second type configuration" are not limited. Optionally, the UE may be indicated / configured with the first type configuration and / or the second type configuration. Optionally, the first type configuration is used for uplink transmission and / or downlink reception. Optionally, the second type configuration is used for uplink transmission and / or downlink reception. Optionally, the uplink transmission includes transmission of an uplink channel and / or transmission of an uplink signal. Optionally, the uplink channel includes at least one of PUSCH, PUCCH, and physical random access channel (PRACH). Optionally, the uplink signal includes at least one of DM-RS, PT-RS, and SRS. Optionally, the downlink reception includes reception of a downlink channel and / or reception of a downlink signal. Optionally, the downlink channel includes at least one of PDSCH, PDCCH, and PBCH. Optionally, the downlink signal includes at least one of DM-RS, PT-RS, CSI-RS, positioning reference signal (PRS), PSS, and SSS.

[0177] Optionally, for the first type configuration, the uplink transmission and / or the downlink reception are restricted to be only in the first type time domain resource or only in the second type time domain resource. Optionally, for the first type configuration, the uplink transmission and / or the downlink reception are restricted to be only in a dedicated type of time domain resource. Optionally, for the first type configuration, the uplink transmission and / or the downlink reception are allowed to be only in the first type time domain resource or only in the second type time domain resource. Optionally, for the first type configuration, the uplink transmission and / or the downlink reception are in the dedicated type of time domain resource. Optionally, for the first type configuration, the UE performs the uplink transmission and / or the downlink reception on the dedicated type of time domain resource. Optionally, for the first type configuration, the UE is allowed to perform the uplink transmission and / or the downlink reception on the dedicated type of time domain resource. Here, performing the uplink transmission may be transmitting uplink transmission, or transmitting the uplink channel / uplink signal. Here, performing the downlink reception may be receiving downlink reception, or receiving the downlink channel / downlink signal. Optionally, for the first type configuration, the uplink transmission and / or the downlink reception are not in a non-dedicated type of time domain resource. Optionally, for the first type configuration, in the non-dedicated type of time domain resource, the uplink transmission is dropped / canceled, or the downlink reception is dropped / canceled. Optionally, for the first type configuration, in the non-dedicated type of time domain resource, the UE does not perform the uplink transmission and / or does not perform the downlink reception. Optionally, for the first type configuration, in the non-dedicated type of time domain resource, the UE cancels / drops the uplink transmission, and / or the UE cancels / drops the downlink reception. Optionally, the dedicated type of time domain resource may be the first type time domain resource or the second type time domain resource. Optionally, the dedicated type of time domain resource may be determined / indicated as one of the first type time domain resource or the second type time domain resource. In the disclosure, the dedicated type of time domain resource may be referred to as a valid time domain resource, or a valid time domain resource type, or a valid symbol type, or a valid slot type. The dedicated type of time domain resource may be determined by the followings.

[0178] * Optionally, for semi-statically configured (or without activation DCI or without corresponding activation DCI) uplink transmission and / or downlink reception, the dedicated type of time domain resource is indicated by the base station, for example, explicitly configured via RRC signaling. Optionally, the semi-statically configured uplink transmission may include transmission of configured grant PUSCH, transmission of PUCCH, and transmission of configured grant periodic SRS. Optionally, the semi-statically configured downlink reception may include reception of SPS PDSCH, reception of PDCCH, and reception of periodic CSI-RS. Optionally, the configured grant PUSCH may include Type 1 configured grant PUSCH, and / or Type 2 configured grant PUSCH. In the disclosure, "Type 1 configured grant PUSCH" may be used interchangeably with "Type 1 configured grant PUSCH transmission", "Configured grant Type 1 PUSCH", or "Configured grant Type 1 PUSCH transmission", and "Type 2 configured grant PUSCH" may be used interchangeably with "Type 2 configured grant PUSCH transmission", "Configured grant Type 2 PUSCH",or "Configured grant Type 2 PUSCH transmission", and their names are not limited in the disclosure. The "Type 1 configured grant PUSCH", and "Type 2 configured grant PUSCH", will be described in detail below.

[0179] * Optionally, for dynamically scheduled (for example, DCI format indicated / scheduled / triggered / activated) uplink transmission or downlink reception, the dedicated type of time domain resource is determined based on the (first / earliest) uplink transmission / downlink reception (the type of the time domain resource where the (first / earliest) uplink transmission / downlink reception is located). Optionally, when the uplink transmission / downlink reception includes one or more repetitions, the dedicated type is determined based on the first / earliest repetition of the one or more repetitions (the type of the time domain resource where the first / earliest repetition of the one or more repetitions is located). Optionally, when the uplink transmission / downlink reception includes one or more channels (for example, PUSCH / PDSCH), the dedicated type is determined based on the first / earliest channel of the one or more channels (the type of the time domain resource where the first / earliest channel of the one or more channels is located). Optionally, the transmission / reception of the one or more repetitions included in the uplink transmission / downlink reception indicated / scheduled / triggered / activated by the same DCI format is determined based on the dedicated type of the first repetition of the one or more repetitions. Optionally, the transmission / reception of the one or more channels included in the uplink transmission / downlink reception indicated / scheduled / triggered / activated by the same DCI format is determined based on the dedicated type of the first channel of the one or more channels. Optionally, the uplink transmission / downlink reception indicated / scheduled / triggered / activated by the same DCI format includes one or more channels, and the transmission / reception of the one or more repetitions included in each channel is of the dedicated type determined based on the first repetition of the one or more repetitions of the one or more channels. Optionally, the dynamically scheduled uplink transmission may be the PUSCH scheduled / indicated / triggered by DCI. Optionally, the dynamically scheduled uplink transmission may be the transmission of the retransmission of the PUSCH. Optionally, the dynamically scheduled uplink transmission may be the transmission of PUCCH scheduled / indicated / triggered by DCI. Optionally, the dynamically scheduled uplink transmission may be the transmission of the PUCCH carrying HARQ-ACK information for feeding back the PDSCH scheduled by DCI. Optionally, the dynamically scheduled uplink transmission may be the transmission of the PUCCH triggered by DCI for updating the TCI state (for example, joint TCI state) (for example, the PUCCH carries HARQ-ACK information corresponding to the DCI). Optionally, the DCI is used for indicating deactivation of SPS or configured grant configuration, and the DCI triggers the transmission of PUCCH (for example, the PUCCH carries HARQ-ACK information corresponding to the DCI). Optionally, the dynamically scheduled downlink transmission may be the PDSCH scheduled / indicated / triggered by DCI. Optionally, dynamically scheduled downlink reception may be the reception of the retransmission of the PDSCH.

[0180] * Optionally, for semi-persistent uplink transmission / downlink reception, the dedicated type of time domain resource is determined based on the first uplink transmission / downlink reception after activation. Optionally, the first uplink transmission / downlink reception refers to the corresponding first semi-persistent uplink transmission / downlink reception. Optionally, for semi-persistent uplink transmission / downlink reception, the dedicated type of time domain resource is determined based on the first uplink transmission / downlink reception after the latest activation. Optionally, for semi-persistent uplink transmission / downlink reception, the dedicated type of time domain resource is determined based on the first uplink transmission / downlink reception associated with activation signaling. Optionally, for semi-persistent uplink transmission / downlink reception, the dedicated type of time domain resource is determined based on the first uplink transmission / downlink reception associated with the latest activation signaling. Optionally, the first uplink transmission / downlink reception associated with activation signaling refers to the first uplink transmission / downlink reception after the activation signaling. Optionally, the first uplink transmission / downlink reception associated with the activation signaling refers to the first uplink transmission / downlink reception indicated / scheduled by the activation signaling. Optionally, the activation signaling may be activation MAC-CE or activation DCI. For example, the dedicated type of time domain resource corresponding to the uplink channel / uplink signal or the repetition of the uplink channel / uplink signal in time domain unit n is determined based on the activation (or activation DCI) closest from time domain unit n. For example, the dedicated type of time domain resource corresponding to the downlink channel / downlink signal or the repetition of the downlink channel / downlink signal in time domain unit n is determined based on the activation (or activation DCI) closest from time domain unit n. The semi-persistent uplink transmission / downlink reception may be activated multiple times. Therefore, determining the dedicated type of time domain resource based on the latest activation signaling may enable the dedicated type of time domain resource to be adjusted at each activation, improving the flexibility of the communication system. Here, the term "latest" may be used interchangeably with the term "Corresponding to uplink transmission / downlink reception", or "for activating corresponding uplink transmission / downlink reception".

[0181] * Optionally, for semi-persistent CSI report (on PUCCH / PUSCH), the dedicated type of time domain resource is determined based on the first PUCCH / PUSCH transmission after activation (the type of the time domain resource where the first PUCCH / PUSCH transmission after activation is located). Optionally, for semi-persistent CSI report (on PUCCH / PUSCH), the dedicated type of time domain resource is determined based on the first corresponding PUCCH / PUSCH transmission after activation (the type of the time domain resource where the first corresponding PUCCH / PUSCH transmission after activation is located). Optionally, for semi-persistent CSI report (on PUCCH / PUSCH), the dedicated type of time domain resource is (explicitly) configured by the corresponding CSI reporting configuration (e.g., CSI-ReportConfig). Here, the first PUCCH / PUSCH transmission after activation refers to the first (corresponding) PUCCH / PUSCH transmission after the latest activation. Optionally, the PUCCH / PUSCH refers to the PUCCH / PUSCH associated with the same semi-persistent CSI report corresponding to a configuration parameter CSI-ReportConfig. Optionally, the PUCCH / PUSCH transmission refers to the PUCCH / PUSCH transmission corresponds to the same CSI reporting configuration. The above method allows the UE and the base station to have the same understanding of which PUCCH / PUSCH transmissions may be used for determining the dedicated type of time domain resource, improving the reliability of the communication system.

[0182] * Optionally, for Type 2 configured grant PUSCH, the dedicated type of time domain resource is determined based on the transmission of the first configured grant PUSCH associated with the activation DCI (the type of the time domain resource where the transmission of the first configured grant PUSCH associated with the activation DCI is located). Optionally, for Type 2 configured grant PUSCH, the dedicated type of time domain resource is determined based on the transmission of the first configured grant PUSCH associated with the latest activation DCI (the type of the time domain resource where the transmission of the first configured grant PUSCH associated with the latest activation DCI is located). Optionally, for Type 2 configured grant PUSCH, the dedicated type of time domain resource is determined based on the transmission of the first configured grant PUSCH after activation (the type of the time domain resource where the transmission of the first configured grant PUSCH after activation is located). Optionally, for Type 2 configured grant PUSCH, the dedicated type of time domain resource is determined based on the transmission of the first configured grant PUSCH after the latest activation (the type of the time domain resource where the transmission of the first configured grant PUSCH after the latest activation is located). Optionally, the first configured grant PUSCH associated with the activation DCI may be the first configured grant PUSCH scheduled by / corresponding to / triggered by / indicated by the activation DCI. Optionally, for Type 2 configured grant PUSCH, the dedicated type of time domain resource is configured by the corresponding configured grant configuration information (e.g., ConfiguredGrantConfig). Optionally, the PUSCH transmission refers to the configured grant PUSCH transmission corresponding to the same configured grant configuration information. The above method allows the UE and the base station to have the same understanding of which configured grant PUSCH transmissions may be used for determining the dedicated type of time domain resource, improving the reliability of the communication system.

[0183] * Optionally, for SPS PDSCH, the dedicated type of time domain resource is determined based on the first PDSCH reception after activation (the type of the time domain resource where the first PDSCH reception after activation is located). Optionally, for SPS PDSCH, the dedicated type of time domain resource is determined based on the first SPS PDSCH reception after the latest activation (the type of the time domain resource where the first SPS PDSCH reception after the latest activation is located). Optionally, for SPS PDSCH, the dedicated type of time domain resource is determined based on the first SPS PDSCH reception associated with the activation DCI (the type of the time domain resource where the first SPS PDSCH reception associated with the activation DCI is located). Optionally, for SPS PDSCH, the dedicated type of time domain resource is determined based on the first PDSCH reception associated with the latest activation DCI (the type of the time domain resource where the first PDSCH reception associated with the latest activation DCI is located). Optionally, the first SPS PDSCH associated with the activation DCI may be the first SPS PDSCH scheduled by / corresponding to / triggered by / indicated by the activation DCI. Optionally, for SPS PDSCH, the dedicated type of time domain resource is configured by the corresponding SPS configuration information (e.g. SPS-Config). Optionally, the SPS PDSCH reception refers to the SPS PDSCH reception corresponding to the same SPS configuration information. The above method allows the UE and the base station to have the same understanding of which SPS PDSCH receptions may be used for determining the dedicated type of time domain resource, improving the reliability of the communication system.

[0184] * Optionally, for semi-persistent SRS, the dedicated type of time domain resource is determined based on the transmission of the first SRS after activation (the type of the time domain resource where the transmission of the first SRS after activation is located). Optionally, for semi-persistent SRS, the dedicated type of time domain resource is determined based on the transmission of the first SRS after the latest activation (the type of the time domain resource where the transmission of the first SRS after the latest activation is located). Optionally, for semi-persistent SRS, the dedicated type of time domain resource is configured by the corresponding SRS configuration information (e.g., SRS-Config) or the configuration information for the SRS resource set (e.g., SRS-ResourceSet) or the configuration information for the SRS resource (e.g., SRS-Resource). Optionally, the SRS transmission may refer to the SRS transmission corresponding to the same SRS configuration information. Optionally, the SRS transmission may refer to the SRS transmission corresponding to the same SRS resource set. Optionally, the SRS transmission may refer to the SRS transmission corresponding to the SRS resource sets of the same usage. Optionally, the SRS transmission may refer to the SRS transmission corresponding to the same SRS resource. Optionally, when the configuration information (for example, SRS-Config, SRS-ResourceSet, SRS-ResourceSet) is configured with the first type configuration, the SRS transmission refers to the SRS corresponding to / configured by the configuration information. Optionally, when the SRS configuration information is configured with the first type configuration, the SRS transmission refers to SRS transmission corresponding to the same SRS resource set. Optionally, when the SRS configuration information is configured with the first type configuration, the SRS transmission refers to the SRS transmission corresponding to the SRS resource sets of the same usage. Optionally, when the configuration information for the SRS resource set is configured with the first type configuration, the SRS transmission refers to the SRS transmission corresponding to the same SRS resource in the SRS resource set. The above method allows the UE and the base station to have the same understanding of which SRS transmissions may be used for determining the dedicated type of time domain resource, improving the reliability of the communication system.

[0185] Optionally, the second type configuration being configured may refer to the first type configuration not being configured. Optionally, for the second type configuration, the uplink transmission or the downlink reception may be in the first type time domain resource and / or in the second type time domain resource. Optionally, for the second type configuration, the UE may perform the uplink transmission or the downlink reception in the first type time domain resource and / or in the second type time domain resource. Optionally, for the second type configuration, the uplink transmission or the downlink reception is not restricted to be only in the first type time domain resource or only in the second type time domain resource. Optionally, for the second type configuration, the UE does not drop / cancel the uplink transmission or the downlink reception in the first type time domain resource and / or in the second type time domain resource. Optionally, if the second type is configured, the corresponding uplink transmission and / or downlink reception are not restricted by the time domain resource type. Optionally, if the second type is configured, the corresponding uplink transmission and / or downlink reception ignores the time domain resource type. Optionally, if the second type is configured, the corresponding uplink transmission and / or downlink reception ignores the restriction of the time domain resource type.

[0186] The UE behavior (or restriction) associated with the first type configuration / the second type configuration is described above. Here, the restriction may be a transmission restriction and / or a reception restriction. Optionally, the uplink transmission and / or downlink reception being applicable to the first type configuration / the second type configuration refers to the uplink transmission and / or downlink reception applying / using the above UE behavior and / or the transmission restriction and / or the reception restriction. Optionally, the uplink transmission and / or downlink reception being applicable to the first type configuration / the second type configuration refers to the configuration information for uplink transmission and / or downlink reception being configured with the first type configuration / the second type configuration. Optionally, the uplink transmission and / or the downlink reception being applicable to the first type configuration / the second type configuration refers to the first type configuration / the second type configuration being configured in the configuration information for uplink transmission and / or downlink reception. Optionally, the uplink transmission and / or the downlink reception being applicable to the first type configuration / the second type configuration refers to the behavior of uplink transmission and / or downlink reception being in reference with the above description of the first type configuration / the second type configuration. Optionally, the uplink transmission and / or the downlink reception being applicable to the first type configuration / the second type configuration refers to the behavior of the uplink transmission and / or downlink reception being in reference with the above UE behavior corresponding to the first type configuration / the second type configuration.

[0187] The configuration method of the first type configuration / the second type configuration is discussed below. The first type configuration / the second type configuration may be configured by the configuration parameter for indicating the configuration type. In the disclosure, the configuration parameter for indicating the configuration type may be referred to as a type configuration parameter, and its name is not limited by the disclosure. Optionally, the type configuration parameter may be configured when the SBFD configuration information is configured. Optionally, the type configuration parameter is applicable when the SBFD configuration information is configured. Optionally, the type configuration parameter may be used for indicating the type of the time domain resource allowed for uplink transmission or downlink reception. Optionally, the type configuration parameter may be used as the parameter for indicating the restriction on uplink reception or the restriction on downlink transmission. Optionally, the type configuration parameter may be used for indicating the parameter of the method of uplink reception or downlink transmission. Optionally, the type configuration parameter may indicate a first state or a second state, where the first state corresponds to the first type configuration, and the second state corresponds to the second type configuration. Optionally, in some cases, the first state may indicate the dedicated type of time domain resource. Optionally, the first state may indicate a third state or a fourth state, where the third state indicates that the dedicated type of time domain resource is the first type time domain resource, and the fourth state indicates that the dedicated type of time domain resource is the second type time domain resource. Optionally, the second type configuration may also be indicated implicitly. For example, the second type configuration may be considered / assumed to be configured when the type configuration parameter is not configured. Optionally, the first type configuration / the second type configuration being configured may be considered as the type configuration parameter being configured.

[0188] * Optionally, the first type configuration / the second type configuration may be configured for uplink and downlink, respectively. For example, when uplink and downlink are configured with the first type configuration / the second type configuration, respectively, the uplink transmission and downlink reception apply corresponding types of configurations, respectively. Optionally, when the uplink transmission is configured with the first type configuration, the UE transmits only on the first type time domain resource or transmits only on the second type time domain resource. Optionally, when the downlink reception is configured with the second type configuration, the UE may perform downlink reception on the first type time domain resource and / or the second type time domain resource. Optionally, the uplink BWP may be configured with the first type configuration / the second type configuration. For example, the configuration information for configuring uplink BWP parameter (BWP-UplinkDedicated) is configured with the first type configuration / the second type configuration. For example, the configuration information may or may not include the type configuration parameter. Optionally, the first type configuration / the second type configuration is applicable to uplink transmission on the uplink BWP. Optionally, the first type configuration / the second type configuration is applicable to at least one of PUSCH, PUCCH, and SRS. Optionally, the first type configuration / the second type configuration is applicable to PUSCH / PUCCH / SRS triggered / activated / scheduled by PDCCH (or detected DCI format) in USS and / or type 3 PDCCH CSS. Optionally, the first type configuration / the second type configuration is applicable to the configured grant PUSCH and / or (UE-specific or dedicated) PUCCH and / or periodic SRS. Optionally, when the third state or the fourth state is indicated, (the indication of) the third state or the fourth state is applicable to the configured grant PUSCH and / or (UE-specific or dedicated) PUCCH and / or periodic SRS. The above method defines the applicable range of the type configuration parameter, so that the UE and the base station may have the same understanding of the UE behavior of uplink transmission. Optionally, the downlink BWP may be configured with the first type configuration / the second type configuration. For example, the configuration information for configuring the downlink BWP parameter (BWP-DownlinkDedicated) is configured with the first type configuration / the second type configuration. For example, the configuration information may or may not include the type configuration parameter. Optionally, the first type configuration / the second type configuration is applicable to downlink reception on the downlink BWP. Optionally, the first type configuration / the second type configuration is applicable to at least one of PDSCH, PDCCH, and CSI-RS. Optionally, the first type configuration / the second type configuration is applicable to PDSCH / CSI-RS triggered / activated / scheduled by PDCCH (or detected DCI format) in USS and / or type 3 PDCCH CSS. Optionally, the first type configuration / the second type configuration is applicable to SPS PDSCH and / or PDCCH and / or periodic CSI-RS. Optionally, when the third state or the fourth state is indicated, (the indication of) the third state or the fourth state is applicable to the SPS PDSCH and periodic CSI-RS. The above method defines the applicable range of the type configuration parameter, so that the UE and the base station may have the same understanding of the UE behavior of downlink reception.

[0189] * Optionally, the first type configuration / the second type configuration may be configured for different uplink channels / uplink signals, respectively. For example, for PUSCH, PUCCH, and SRS, the first type configuration / the second type configuration may be configured, respectively. Optionally, if the uplink channel / uplink signal is configured with the first type configuration / the second type configuration, the same type of uplink channel / uplink signal reception is applicable to the same first type configuration / second type configuration. Optionally, the PUSCH configuration information (e.g., PUSCH-Config) may be configured with the first type configuration / the second type configuration. Optionally, the PUCCH configuration information (e.g., PUCCH-Config) may be configured with the first type configuration / the second type configuration. Optionally, the PUCCH configuration information is used for configuring the UE-specific PUCCH parameter. Optionally, the SRS configuration information and / or the information for configuring the SRS resource set and / or the configuration information for configuring the SRS resource may be configured with the first type configuration / the second type configuration. Optionally, the SRS resource set may be configured with the first type configuration / the second type configuration. Optionally, the SRS resource sets of the same usage may be configured with the first type configuration / the second type configuration.

[0190] * Optionally, the first type configuration / the second type configuration may be configured for different downlink channels / downlink, signals respectively. For example, for PDSCH, PDCCH, and CSI-RS, the first type configuration / the second type configuration may be configured, respectively. Optionally, if the downlink channel / downlink signal is configured with the first type configuration / the second type configuration, the same type of downlink channel / downlink signal reception is applicable to the same first type configuration / second type configuration. Optionally, the first type configuration / the second type configuration may be configured for different triggering methods, respectively. The first type configuration / the second type configuration may be configured for different downlink channels / downlink signals, respectively. The first type configuration / the second type configuration may be configured for downlink channels / downlink signals of different triggering methods, respectively. It may be considered that dynamically scheduled downlink channel / downlink signal and semi-statically configured downlink channel / downlink signal are different triggering methods. It may be considered that the triggering methods of dynamically scheduled PDSCH and configured grant PUSCH are different. Optionally, the PDSCH configuration information (e.g. PDSCH-Config) may be configured with the first type configuration / the second type configuration. Optionally, the PDSCH configuration information is used for configuring the UE-specific PDSCH parameter. Optionally, the PDCCH configuration information (e.g., PDCCH-Config) may be configured with the first type configuration / the second type configuration. Optionally, the PDCCH configuration information is used for configuring the UE-specific PDCCH parameter. Optionally, the CSI-RS configuration information (e.g., NZP-CSI-RS-Resource) and / or information for configuring the CSI-RS resource set (e.g., NZP-CSI-RS-ResourceSet) and / or configuration information for configuring one or more CSI-RS resource sets (e.g., CSI-ResourceConfig) may be configured with the first type configuration / the second type configuration. If the configuration information associated with the CSI-RS is configured with the first type configuration / the second type configuration, the CSI-RS resource indicated by / corresponding to the configuration information is applicable to the first type configuration / the second type configuration.

[0191] * Optionally, the PUSCH configuration information (e.g., PUSCH-Config) may be configured with the first type configuration / the second type configuration. Optionally, the configured grant configuration information (e.g., ConfiguredGrantConfig) may be configured with the first type configuration / the second type configuration. Optionally, the configured grant configuration information is used for configuring uplink transmission without dynamic grant.

[0192] * Optionally, the PDSCH configuration information (e.g. PDSCH-Config) may be configured with the first type configuration / the second type configuration. The SPS configuration information (e.g. SPS-Config) may be configured with the first type configuration / the second type configuration.

[0193] * Optionally, the first type configuration / the second type configuration may be configured for different DCI formats, respectively. Optionally, the first type configuration / the second type configuration may be configured for different DCI format types, respectively. For example, DCI format 0_1 and / or DCI format 0_2 and / or DCI format 0_3 may be configured with the first type configuration / the second type configuration, respectively. For example, DCI format 1_1 and / or DCI format 1_2 and / or DCI format 1_3 is configured with the first type configuration / the second type configuration, respectively. If one type of DCI format is configured with the first type configuration / the second type configuration, the uplink transmission or downlink reception scheduled / indicated / triggered by the same type of DCI format is applicable to the first type configuration / the second type configuration. Optionally, for PUSCH, the first type configuration / the second type configuration may be configured for different DCI formats, respectively, in the PUSCH configuration information. Optionally, the first type configuration / the second type configuration may be configured for DCI format 0_1 and / or DCI format 0_2 and / or DCI format 0_3, respectively, in the PUSCH configuration information. For example, when the first type configuration / the second type configuration for DCI format 0_1 is configured in the PUSCH configuration information, the PUSCH scheduled / indicated / triggered by DCI format 0_1 is applicable to the first type configuration / the second type configuration.

[0194] In some cases, the UE may transmit the retransmission of the PUSCH. Several methods are provided below so that new transmission and retransmission of the PUSCH may be within the same type of time domain resources, thereby reducing the complexity of the base station receiver. Optionally, PUSCH is used for retransmission of the TB. Optionally, (the UE expects that) the type of the time domain resource where the retransmission of the PUSCH is located is the same as the type of the time domain resource where the initial transmission of the PUSCH is located. Optionally, (the UE expects that) the type of the time domain resource where the retransmission of the PUSCH is located is the same as the type of the time domain resource where the PUSCH in which the TB initial transmission carried by the PUSCH is located is located. Optionally, the type of the time domain resource where the retransmission of the PUSCH is located is determined based on the type of the time domain resource where the initial transmission of the PUSCH is located (for example, the types are the same). Optionally, the type of the time domain resource where the retransmission of the PUSCH is located is determined based on the type of the time domain resource where the PUSCH in which the TB initial transmission carried by the PUSCH is located is located (for example, the types are the same). Optionally, (the UE expects that) the dedicated type of the time domain resource applicable to the retransmission of the PUSCH is of the same type as the dedicated type of the time domain resource applicable to the initial transmission of the PUSCH. Optionally, (the UE expects that) the dedicated type of the time domain resource applicable to the retransmission of the PUSCH is of the same type as the dedicated type of the time domain resource applicable to the PUSCH where the TB initial transmission carried by the PUSCH is located. Optionally, the type of the dedicated type of the time domain resource applicable to the retransmission of the PUSCH is determined based on the type of the dedicated type of the time domain resource applicable to the initial transmission of the PUSCH (for example, the types are the same). Optionally, the type of the dedicated type of the time domain resource applicable to the retransmission of the PUSCH is determined based on the type of the dedicated type of the time domain resource applicable to the PUSCH where the TB initial transmission carried by the PUSCH is located (for example, the types are the same). For example, when the dedicated type of the time domain resource applicable to the PUSCH where the TB initial transmission carried by the PUSCH is located is the first type time domain resource, the dedicated type of the time domain resource applicable to the retransmission of the PUSCH is the first type time domain resource. For example, when the time domain resource where the PUSCH in which the TB initial transmission carried by the PUSCH is located is located is the first type time domain resource, the time domain resource where the retransmission of the PUSCH is located is the first type time domain resource. For example, when the dedicated type of the time domain resource applicable to the PUSCH where the TB initial transmission carried by the PUSCH is located is the second type time domain resource, the dedicated type of the time domain resource applicable to the retransmission of the PUSCH is the second type time domain resource. For example, when the time domain resource where the PUSCH in which the TB initial transmission carried by the PUSCH is located is located is the second type time domain resource, the time domain resource where the retransmission of the PUSCH is located is the second type time domain resource. Optionally, the above restriction / operations associated with the retransmission of the PUSCH should satisfy at least one of the following conditions:

[0195] * The retransmission of the PUSCH is the (Type 1 or Type 2) configured grant PUSCH. For example, the retransmission of the PUSCH is determined based on the configured grant configuration information;

[0196] * The retransmission of the PUSCH is configured with the first type configuration;

[0197] * The PUSCH configuration information is configured with the type configuration parameter, and the type configuration parameter indicates the first state. For example, the PUSCH configuration information of the BWP where the transmission of the PUSCH is located is configured with the type configuration parameter, and the type configuration parameter indicates the first state;

[0198] * The retransmission of the PUSCH is based on the configured grant configuration information, and the configured grant configuration information is configured with the type configuration parameter, and the type configuration parameter indicates the second state;

[0199] * The SBFD configuration information is configured.

[0200] In some cases, the UE may receive the retransmission of the PDSCH. Several methods are provided below so that new transmission and retransmission of the PDSCH may be within the same type of time domain resources, thereby reducing the complexity of the UE receiver. Optionally, PDSCH is used for retransmission of the TB. Optionally, (the UE expects that) the type of the time domain resource where the retransmission of the PDSCH is located is the same as the type of the time domain resource where the initial transmission of the PDSCH is located. Optionally, (the UE expects that) the type of the time domain resource where the retransmission of the PDSCH is located is the same as the type of the time domain resource where the PDSCH in which the TB initial transmission carried by the PDSCH is located is located. Optionally, the type of the time domain resource where the retransmission of the PDSCH is located is determined based on the type of the time domain resource where the initial transmission of the PDSCH is located (for example, the types are the same). Optionally, the type of the time domain resource where the transmission of the PDSCH is located is determined based on the type of the time domain resource where the PDSCH in which the TB initial transmission carried by the PDSCH is located is located (for example, the types are the same). Optionally, (the UE expects that) the dedicated type of the time domain resource applicable to the retransmission of the PDSCH is of the same type as the dedicated type of the time domain resource applicable to the initial transmission of the PDSCH. Optionally, (the UE expects that) the dedicated type of the time domain resource applicable to the retransmission of the PDSCH is of the same type as the dedicated type of the time domain resource applicable to the PDSCH where the TB initial transmission carried by the PDSCH is located. Optionally, the type of the dedicated type of the time domain resource applicable to the retransmission of the PDSCH is determined based on the type of the dedicated type of the time domain resource applicable to the initial transmission of the PDSCH (for example, the types are the same). Optionally, the type of the dedicated type of the time domain resource applicable to the retransmission of the PDSCH is determined based on the type of the dedicated type of the time domain resource applicable to the PDSCH where the TB initial transmission carried by the PDSCH is located (for example, the types are the same). For example, when the dedicated type of the time domain resource applicable to the PDSCH where the TB initial transmission carried by the PDSCH is located is the first type time domain resource, the dedicated type of the time domain resource applicable to the retransmission of the PDSCH is the first type time domain resource. For example, when the time domain resource where the PDSCH in which the TB initial transmission carried by the PDSCH is located is located is the first type time domain resource, the time domain resource where the retransmission of the PDSCH is located is the first type time domain resource. For example, when the dedicated type of the time domain resource applicable to the PDSCH where the TB initial transmission carried by the PDSCH is located is the second type time domain resource, the dedicated type of the time domain resource applicable to the retransmission of the PDSCH is the second type time domain resource. For example, when the time domain resource where the PDSCH in which the TB initial transmission carried by the PDSCH is located is located is the second type time domain resource, the time domain resource where the retransmission of the PDSCH is located is the second type time domain resource. Optionally, the above restriction / operations associated with the PDSCH retransmission should satisfy at least one of the following conditions:

[0201] * The retransmission of the PDSCH is SPS PDSCH. For example, the retransmission of the PDSCH is determined based on the SPS configuration information;

[0202] * The retransmission of the PDSCH is configured with the first type configuration;

[0203] * The PDSCH configuration information is configured with the type configuration parameter, and the type configuration parameter indicates the first state. For example, the PDSCH configuration information of the BWP where the transmission of the PDSCH is located is configured with the type configuration parameter, and the type configuration parameter indicates the first state;

[0204] * The retransmission of the PDSCH is based on the SPS configuration information, and the SPS configuration information is configured with the type configuration parameter, and the type configuration parameter indicates the second state;

[0205] * The SBFD configuration information is configured.

[0206] Optionally, the UE receives the SRS configuration information (e.g., SRS-Config). Optionally, the SRS configuration information is used for configuring the transmission of SRS. Optionally, the SRS configuration information may include information for configuring SRS resource set. Optionally, the information for configuring the SRS resource set may include configuration information indicating one or more SRS resource sets (e.g., parameter srs-ResourceSetToAddModList). Optionally, the information for configuring the SRS resource set may include configuration information indicating one or more SRS resource sets for DCI format 0_2 (for example, parameter srs-ResourceSetToAddModListDCI-0-2). The UE may be configured with one or more SRS resource sets as configured by the higher layer parameter e.g., SRS-ResourceSet. Optionally, one / each SRS resource set may be configured with a set identification (ID) (e.g., srs-ResourceSetId). For each SRS resource set configured by SRS-ResourceSet, the UE may be configured with K (K ) SRS resources (via higher layer parameter SRS-Resource), where the maximum value of K is indicated by the UE capability. Optionally, The SRS resource set applicability is configured by the usage parameter (e.g., higher layer parameter usage) in SRS-ResourceSet. Optionally, the usage parameter may indicate the SRS resource set is used for beam management, codebook-based transmission, non-codebook-based transmission, or antenna switching. When the usage parameter of an SRS resource set is set to "Codebook", it may be considered that the usage of the SRS resource set is set to codebook-based transmission, or the SRS resource set is used for codebook-based transmission. When the usage parameter of an SRS resource set is set to "nonCodebook", it may be considered that the usage of the SRS resource set is set to non-codebook-based transmission, or the SRS resource set is for non-codebook-based transmission. An SRS resource (or the SRS-Resource corresponding to an SRS) may be configured (via higher layer parameter resourceType) with time domain behavior of the SRS resource configuration. Optionally, the time domain behavior may be periodic, semi-persistent, or aperiodic. Optionally, in the same resource set, the time domain behavior of the SRS resources are the same.

[0207] Optionally, the UE receives configuration information for the PUSCH. Optionally, the UE may receive uplink BWP configuration information, where the uplink BWP configuration information includes the configuration information for the PUSCH. Optionally, the configuration information for the PUSCH may include configuration information for configuring the PUSCH parameter (e.g., PUSCH-Config). The configuration information for configuring the PUSCH parameter may be referred to as the PUSCH configuration information. Optionally, the configuration information for the PUSCH may include one or more configured grant configuration information. Optionally, the configured grant configuration information may be the configuration information for configuring uplink transmission without dynamic grant (for example, ConfiguredGrantConfig). Optionally, the configured grant configuration information may indicate / correspond to / configure Type 1 or Type 2. Optionally, Type 1 refers to Type 1 configured grant PUSCH transmission, configured grant Type 1 PUSCH transmission. Optionally, Type 2 refers to Type 2 configured grant PUSCH transmission, or configured grant Type 2 PUSCH transmission. Optionally, The configured grant Type 1 PUSCH transmission is semi-statically configured to operate upon the reception of higher layer parameter of configuredGrantConfig including rrc-ConfiguredUplinkGrant without the detection of an UL grant in a DCI. Optionally, The configured grant Type 2 PUSCH transmission is semi-persistently scheduled by an UL grant in a valid activation DCI after the reception of higher layer parameter configuredGrantConfig not including rrc-ConfiguredUplinkGrant. If the field of the DCI format is set to a predefined value, the validity of the DCI format may be confirmed. For example, if the HARQ process number field of the DCI format is set to all 0s, and / or the redundancy version field of the DCI format is set to all 0s, the DCI format may be considered to be a valid activation DCI.

[0208] Optionally, the PUSCH transmission may be dynamically scheduled. For example, the PUSCH transmission may be dynamically scheduled by an UL grant in a DCI. Optionally, the PUSCH transmission may correspond to a configured grant. Optionally, the configured grant may be configured grant Type 1, or configured grant Type 2. Optionally, the parameter for transmission of the dynamically scheduled PUSCH transmission is determined based on the configuration information for configuring the PUSCH parameter (e.g., PUSCH-Config). For example, the parameter in the configuration information for configuring the PUSCH parameter (e.g., PUSCH-Config) is applicable to the dynamically scheduled PUSCH transmission. Optionally, the parameter for transmission of the PUSCH transmission corresponding to the configured grant is determined based on the configuration information for configuring the PUSCH parameter (e.g., PUSCH-Config) and / or the configured grant configuration information (e.g., ConfiguredGrantConfig). For example, the parameter in the configuration information for configuring the PUSCH parameter and / or the configured grant configuration information is applicable to the PUSCH transmission corresponding to the configured grant.

[0209] In order to monitor / detect DCI corresponding to the dynamically scheduled PUSCH, the UE may be configured with associated information of the control channel in order to receive the DCI. Optionally, the UE may be configured with the PDCCH configuration information. Optionally, the PDCCH configuration information may be information for configuring the (UE-specific) PDCCH parameter. For example, the PDCCH configuration information may be PDCCH-Config. Optionally, the UE may monitor the PDCCH and / or detect the DCI corresponding to the PDCCH based on the parameter in the PDCCH configuration information. Optionally, the UE may monitor the PDCCH in the search space. Optionally, the UE may detect the DCI format by monitoring the PDCCH. Here, the DCI format may be carried by the PDCCH.

[0210] Optionally, two transmission schemes can be supported for PUSCH: codebook-based transmission and non-codebook-based transmission. The UE is configured with codebook-based transmission when transmission configuration information (e.g., txConfig in pusch-Config) is set to "codebook". The UE is configured with non-codebook-based transmission when the transmission configuration information (e.g., txConfig in pusch-Config) is set to "nonCodebook". Optionally, the transmission configuration information is used for indicating the UE uses codebook-based or non-codebook-based transmission. If the transmission configuration information is not configured, the UE is not expected to be scheduled by DCI format 0_1 or DCI format 0_2 or DCI format 0_3. If the transmission configuration information is not configured, the UE may be scheduled with PUSCH by DCI format 0_0. If PUSCH is scheduled by DCI format 0_0, the PUSCH transmission is based on a single antenna port.

[0211] Optionally, the UE obtains SRI. Optionally, the UE may obtain the SRI through the detected DCI format or the configured grant configuration information. Optionally, the UE may transmit PUSCH based on the obtained SRI. Optionally, the PUSCH transmission precoder for the PUSCH may be determined based on the SRI. Optionally, the UE transmits PUSCH based on / using the precoder determined by the SRI. Optionally, the SRI may be used for determining the SRS resource in the SRS resource set. Optionally, the SRI may indicate one or more SRS resources in the (corresponding) SRS resource set. Optionally, the transmission of the SRS resource associated with the SRI is of the same type as the time domain resource where the transmission of the PUSCH is located. The base station may perform uplink channel estimation through the measurement of the SRS, and use the corresponding channel estimation result to adjust the parameter of the receiver to receive PUSCH. The channel correlation of the same type of time domain resources is higher. Due to different received interference, the channel correlation of different types of time domain resources is lower. Restricting the transmission of the SRS and the PUSCH to the same type of time domain resources may improve the performance of demodulation based on the SRS and the PUSCH, improving the communication performance. In the disclosure, a PUSCH may be one or more PUSCHs. For example, a PUSCH may be one or more PUSCHs scheduled / triggered / activated by a DCI. For example, a PUSCH may be one or more PUSCHs corresponding to a configured grant. For example, a PUSCH may be the PUSCH in one or more PUSCHs transmission occasions corresponding to a configured grant. For example, a PUSCH may be one or more PUSCH repetitions. For example, a PUSCH may be one or more PUSCH repetitions scheduled / triggered / activated by a DCI.

[0212] * Optionally, for codebook-based transmission, PUSCH can be scheduled by DCI or semi-statically configured. Here, the semi-statically configured PUSCH may be the configured grant PUSCH. Optionally, the DCI may be DCI format 0_0, DCI format 0_1, DCI format 0_2 or DCI format 0_3. Optionally, if the PUSCH is scheduled by DCI or semi-statically configured, the UE may determine its PUSCH precoder based on the SRI and / or TPMI and / or the transmission rank. Optionally, the SRI may include a first SRI and / or a second SRI. Optionally, the SRI may be indicated by DCI. For example, the SRI may be indicated by the SRI field included in the DCI. For example, the first SRI or the second SRI may be indicated by an SRI field of the DCI. For example, the first SRI and the second SRI may be respectively indicated by two SRI fields of the DCI. For example, the SRI may be indicated by a parameter for indicating the SRI in the configured grant configuration information. For example, the first SRI or the second SRI may be indicated by the parameter for indicating the SRI. For example, the first SRI and the second SRI may be respectively indicated by two parameters for indicating the SRI. For example, the SRI may be indicated by one or two parameters for indicating the SRS resource in the configured grant configuration information. Optionally, the TPMI and / or transmission rank may be indicated by DCI. For example, the TPMI and / or transmission rank is indicated by one or two precoding information and number of layers fields of the DCI. For example, the TPMI and / or the transmission rank may be indicated by one or two parameters for indicating the precoder and the number of layers in the configured grant configuration information. Optionally, in the information for configuring the SRS resource set (e.g., SRS-ResourceSetToAddModList or SRS-ResourceSetToAddModListDCI-0-2), only one or two SRS resource sets for codebook-based transmission may be configured. Optionally, when the SRS resource set is configured with multiple SRS resources, the TPMI is the precoder for indicating the SRS resource selected by the SRI (from the SRS resource set). Optionally, when the SRS resource set is configured with an SRS resource, the TPMI is the precoder for indicating the SRS resource.

[0213] * Optionally, for non-codebook-based uplink transmission, PUSCH can be scheduled by DCI or semi-statically configured. Here, the semi-statically configured PUSCH may be the configured grant PUSCH. Optionally, the DCI may be DCI format 0_0, DCI format 0_1, DCI format 0_2 or DCI format 0_3. Optionally, if the PUSCH is scheduled by DCI or semi-statically configured, the UE can determine its PUSCH precoder and / or transmission rank based on the SRI (when multiple SRS resources are configured). Optionally, the SRI may include the first SRI and / or the second SRI. Optionally, the SRI may be indicated by DCI. For example, the SRI may be indicated by one or two SRI fields of the DCI. For example, the SRI may be indicated by one or two SRS resource indicators in the DCI. For example, the first SRI and the second SRI may be respectively indicated by two SRI fields of the DCI. For example, the SRI may be indicated by a parameter for indicating the SRI or two parameters for indicating the SRI in the configured grant configuration information. For example, the first SRI and the second SRI may be respectively indicated by two parameters for indicating the SRI. For example, the SRI may be indicated by one or two parameters for indicating the SRS resource in the configured grant configuration information. Optionally, in the information for configuring the SRS resource set (e.g., SRS-ResourceSetToAddModList or SRS-ResourceSetToAddModListDCI-0-2), only one or two SRS resource sets with its usage set to non-codebook-based transmission may be configured. Optionally, the UE may use one or more SRS resources for SRS transmission.

[0214] Optionally, an SRS resource set may be associated with a CSI-RS resource. For non-codebook uplink transmission, the UE may calculate the precoder for the transmission of SRS based on measurement of the associated CSI-RS resource. Optionally, the CSI-RS may be a non-zero power (NZP) CSI-RS. Optionally, for an SRS resource set for non-codebook-based transmission, the UE may be configured with an NZP CSI-RS resource. For example, when the SRS resource set is configured as periodic or semi-persistent, the CSI-RS resource may be configured by the parameter associatedCSI-RS. For example, when the SRS resource set is aperiodic, the CSI-RS resource may be configured by the parameter csi-RS.

[0215] Optionally, an SRS resource set may be associated with two CSI-RS resources. Optionally, an SRS resource set may be associated with two semi-persistent / periodic CSI-RS resources. Optionally, an SRS resource set for non-codebook-based transmission may be associated with two CSI-RS resources. For non-codebook uplink transmission, the UE may calculate the precoder used for the transmission of SRS based on measurement of the associated CSI-RS resources. For the first type time domain resource and the second type time domain resource, two CSI-RS resources may be associated with an SRS resource set, and the two CSI-RS resources may respectively be for different types of time domain resources, so that the UE uses different CSI-RS resources to calculate the precoder for different types of uplink transmissions, thereby optimizing the uplink transmission performance on different types of time domain resources. Optionally, the two CSI-RS resources include a first CSI-RS resource and a second CSI-RS resource. Optionally, the first CSI-RS resource is associated with the first type time domain resource. Optionally, the second CSI-RS resource is associated with the second type time domain resource. Optionally, the first CSI-RS resource and the second CSI-RS resource are determined based on a configured CSI-RS resource ID (e.g., NZP-CSI-RS-ResourceId). Optionally, the first CSI-RS resource and the second CSI-RS resource are determined based on a configured order. For example, the first CSI-RS resource and the second CSI-RS resource are respectively resources with lower and higher ID of the two CSI-RS resources. For example, the first CSI-RS resource and the second CSI-RS resource are respectively the first configured CSI-RS resource and the second configured CSI-RS resource of the two CSI-RS resources. Optionally, when the two CSI-RS resources are configured, (the UE may assume that) both the first CSI-RS resource and the second CSI-RS resource are applicable to the first type configuration. Optionally, (the UE may assume that) the dedicated type of the time domain resource applicable to the first CSI-RS resource is the first type time domain resource. Optionally, the UE may assume that the dedicated type of the time domain resource applicable to the second CSI-RS resource is the second type time domain resource. Optionally, when the first CSI-RS resource and the second CSI-RS resource are configured, (the UE expects that) both the first CSI-RS resource and the second CSI-RS resource are configured with the first type configuration. Optionally, (the UE expects that) the dedicated type of time domain resource with which the first CSI-RS resource is configured is the first type time domain resource. Optionally, (the UE expects that) the dedicated type of time domain resource with which the second CSI-RS resource is configured is the second type time domain resource. Optionally, the first CSI-RS resource is associated with the first type time domain resource. Optionally, the precoder and / or uplink power control parameter of the SRS transmitted on the first type time domain resource are determined based on the first CSI-RS resource. Optionally, the precoder and / or the uplink power control parameter of the SRS are determined based on the reception of the CSI-RS resource in the same type of time domain resources. Optionally, the precoder and / or the uplink power control parameter of the SRS transmitted on the first type time domain resource are determined based on the reception of the first CSI-RS resource in the first type time domain resource. In the disclosure, the reception of the CSI-RS resource may be understood as the reception of the CSI-RS corresponding to the CSI-RS resource. Optionally, the first CSI-RS resource and / or the second CSI-RS resource are periodic or semi-persistent. Optionally, when the first CSI-RS resource is periodic or semi-persistent, the dedicated type of time domain resource associated with the reception of the first CSI-RS resource is the first type time domain resource. Optionally, when the first CSI-RS resource is periodic or semi-persistent, the first CSI-RS resource is received in the first type time domain resource, and / or the first CSI-RS resource is not received in the second type time domain resource. Optionally, when the first CSI-RS resource is aperiodic, (the UE expects that) the reception of the first CSI-RS resource is in the first type time domain resource. Optionally, the second CSI-RS resource is associated with the second type time domain resource. Optionally, the precoder and / or the uplink power control parameter of the SRS transmitted on the second type time domain resource are determined based on the second CSI-RS resource. Optionally, the precoder and / or the uplink power control parameter of the SRS transmitted on the second type time domain resource are determined based on the reception of the second CSI-RS resource in the second type time domain resource. Optionally, when the second CSI-RS resource is periodic or semi-persistent, the dedicated type of time domain resource associated with the reception of the second CSI-RS resource is the second type time domain resource. Optionally, when the second CSI-RS resource is periodic or semi-persistent, the second CSI-RS resource is received in the second type time domain resource, and / or the second CSI-RS resource is not received in the first type time domain resource. Optionally, when the second CSI-RS resource is aperiodic, (the UE expects that) the reception of the second CSI-RS resource is in the second type time domain resource. If the SRS resource set is aperiodic, and / or the CSI-RS resource associated with the SRS resource set is aperiodic, (the UE expects / determines that) the SRS resource set is associated with (only) a CSI-RS resource.

[0216] In some cases, the UE may be configured with an SRS resource set. Optionally, the UE receives first power control configuration information for configuring an SRS power control parameter and second power control configuration information for configuring the SRS power control parameter, where the power control parameter of the SRS transmission (for example, the transmission of the SRS resource in the SRS resource set) is determined based on the type of the time domain resource where the SRS is located. For example, when the SRS is transmitted in the first type time domain resource, the first power control configuration information is used. For example, when the SRS is transmitted in the second type time domain resource, the second power control configuration information is used. Optionally, the UE receives third power control configuration information for configuring a PUSCH power control parameter and fourth power control configuration information for configuring the PUSCH power control parameter, where the power control parameter of the PUSCH transmission is determined based on the type of the time domain resource where the PUSCH is located. For example, when the SRS is transmitted in the first type time domain resource, the third power control configuration information is used. For example, when the SRS is transmitted in the second type time domain resource, the fourth power control configuration information is used.

[0217] In some cases, the UE may be configured with two SRS resource sets. Optionally, the two SRS resource sets may be two SRS resource sets for codebook-based transmission. Optionally, the two SRS resource sets may be two SRS resource sets for non-codebook-based transmission. In the disclosure, the two SRS resource sets may be replaced with two SRS resource subsets, where the two SRS resource subsets may each include one or more SRS resources. Optionally, the SRS resources associated with the two SRS resource subsets are in the same SRS resource set (for codebook-based transmission or for non-codebook-based transmission). The description of the SRS resource set is applicable to the SRS resource subset.

[0218] For the first type time domain resource and the second type time domain resource, two SRS resource sets may be configured, the two SRS resource sets may be respectively for different types of time domain resources, so that uplink parameter may be set specifically, thereby optimizing the uplink transmission performance on different types of time domain resources. Optionally, when the two SRS resource sets are configured and / or the SBFD configuration information is configured, the two SRS resource sets include a first SRS resource set and a second SRS resource set. Optionally, the first SRS resource set is associated with the first type time domain resource. Optionally, the second SRS resource set is associated with the second type time domain resource. Optionally, the first SRS resource set and the second SRS resource set are determined based on a configured SRS resource set ID (e.g., srs-ResourceSetId). Optionally, the first SRS resource set and the second SRS resource set are determined based on a configured order. For example, the first SRS resource set and the second SRS resource set are respectively the resource sets with lower and higher srs-ResourceSetId of the two SRS resource sets. For example, the first SRS resource set and the second SRS resource set are respectively the first configured SRS resource set and the second configured SRS resource set of the two SRS resource sets.

[0219] Optionally, when the first SRS resource set and the second SRS resource set are configured and / or the SBFD configuration information is configured, (the UE may assume that) both the first SRS resource set and the second SRS resource set are applicable to the first type configuration. Optionally, (the UE may assume that) the dedicated type of the time domain resource applicable to the first SRS resource set is the first type time domain resource. Optionally, the UE may assume that the dedicated type of time domain resource applicable to the second SRS resource set is the second type time domain resource. Optionally, when the first SRS resource set and the second SRS resource set are configured, (the UE expects that) both the first SRS resource set and the second SRS resource set are configured with the first type configuration. Optionally, (the UE expects that) the dedicated type of time domain resource with which the first SRS resource set is configured is the first type time domain resource. Optionally, the UE may assume that the dedicated type of time domain resource with which the second SRS resource set is configured is the second type time domain resource. Here, the SRS resource set may be understood as the SRS resources in the SRS resource set. Here, the description of the SRS resource set is also applicable to the CSI-RS resource associated with the SRS resource set.

[0220] Optionally, the first SRS resource set is associated with the first type time domain resource. Optionally, the transmission precoder and / or the uplink power control parameter of the PUSCH transmitted on the first type time domain resource are determined based on the first SRS resource set. Optionally, the transmission precoder and / or the uplink power control parameter of the PUSCH transmitted on the first type time domain resource are determined based on the transmission of the SRS resource in the first SRS resource set in the first type time domain resource. Optionally, when the first SRS resource set is periodic or semi-persistent, the dedicated type of time domain resource associated with the transmission of the SRS resource in the first SRS resource set is the first type time domain resource. Optionally, when the first SRS resource set is periodic or semi-persistent, the SRS resource in the first SRS resource set is transmitted in the first type time domain resource, and / or the SRS resource in the first SRS resource set is not transmitted in the second type time domain resource. Optionally, when the first SRS resource set is aperiodic, (the UE expects that) the transmission of the SRS resource in the first SRS resource set is in the first type time domain resource. Here, the description of the SRS resource in the first SRS resource set may be used for describing the CSI-RS resource associated with the first SRS resource set. Accordingly, the transmission of the resource may be replaced with the reception of the resource.

[0221] Optionally, the second SRS resource set is associated with the second type time domain resource. Optionally, the transmission precoder and / or the uplink power control parameter of the PUSCH transmitted on the second type time domain resource are determined based on the second SRS resource set. Optionally, the transmission precoder and / or the uplink power control parameter of the PUSCH transmitted on the second type time domain resource are determined based on the transmission of the SRS resource in the second SRS resource set in the second type time domain resource. Optionally, when the second SRS resource set is periodic or semi-persistent, the dedicated type of time domain resource associated with the transmission of the SRS resource in the second SRS resource set is the second type time domain resource. Optionally, when the second SRS resource set is periodic or semi-persistent, the SRS resource in the second SRS resource set is transmitted in the second type time domain resource, and / or the SRS resource in the second SRS resource set is not transmitted in the first type time domain resource. Optionally, when the second SRS resource set is aperiodic, (the UE expects that) the SRS resource in the second SRS resource set is transmitted in the second type time domain resource. Here, the description of the SRS resource in the second SRS resource set may be used for describing the CSI-RS resource associated with the second SRS resource set. Accordingly, the transmission of the resource may be replaced with the reception of the resource.

[0222] The above method describes the transmission behavior or transmission restriction associated with the first SRS resource set and the second SRS resource set, so that the resource in the SRS resource set are only transmitted in corresponding type of time domain resources, avoiding the transmission in different types of time domain resources, saving the energy consumption of the UE and improving the efficiency of the communication system.

[0223] Optionally, when the first SRS resource set and the second SRS resource set are configured and / or the SBFD configuration information is configured, the SRI may include the first SRI and / or the second SRI. Optionally, the SRI may include only the first SRI or only the second SRI, or the SRI may include the first SRI and the second SRI. Optionally, the first SRI is associated with the first SRS resource set. Optionally, the first SRI indicates the SRS resource in the first SRS resource set. Optionally, the second SRI is associated with the second SRS resource set. Optionally, the second SRI indicates the SRS resource in the second SRS resource set. In the disclosure, the SRI including the first SRI may refer to the SRI including only the first SRI. The SRI including the second SRI may refer to the SRI including only the second SRI.

[0224] In case where the SRI is indicated by the configured grant configuration information, the SRI may include the first SRI or the second SRI, or the SRI may include the first SRI and the second SRI. Optionally, the configured grant configuration information may be configured with a first SRI parameter and / or a second SRI parameter, where the first SRI parameter is used for indicating the first SRI and / or the second SRI parameter is used for indicating the second SRI. Here, the PUSCH is transmitted based on the configured grant configuration information. Optionally, the configured grant configuration information indicates Type 1. Optionally, the PUSCH corresponds to Type 1 configured grant configuration. Optionally, the PUSCH is the Type 1 configured grant PUSCH. Optionally, when the configured grant configuration information is configured with the type configuration parameter, and the type configuration parameter indicates the first state, the SRI includes the first SRI, or the SRI includes the second SRI. When the configured grant configuration information is configured with the type configuration parameter, and the type configuration parameter indicates the first state, and the first state indicates the third state, the SRI includes the first SRI. When the configured grant configuration information is configured with the type configuration parameter, and the type configuration parameter indicates the first state, and the first state indicates the fourth state, the SRI includes the second SRI. When the configured grant configuration information is configured with the type configuration parameter, and the type configuration parameter indicates the second state, the SRI includes the first SRI and the second SRI. Here, the term "the SRI may include the first SRI" may be used interchangeably with the term "the configured grant configuration information is configured with the first SRI parameter". Here, the term "the SRI may include the second SRI" may be used interchangeably with the term "the configured grant configuration information is configured with the second SRI parameter". Here, the term "the SRI may include the first SRI and the second SRI" may be used interchangeably with the term "the configured grant configuration information is configured with the first SRI parameter and the second SRI parameter". Optionally, when the configured grant configuration information corresponds to / indicates Type 1 configured grant configuration, the above method for the SRI and the configured grant configuration information can be used. Optionally, when the configured grant configuration information corresponds to / indicates Type 1 configured grant configuration, and the configured grant configuration information is not configured with the type configuration parameter, in the above method for the SRI and the configured grant configuration information, "configured grant configuration information is configured with the type configuration parameter" may be replaced with "PDSCH configuration information is configured with the type configuration parameter". The above method may facilitate the UE to obtain the parameter for indicating the SRI when the PUSCH corresponds to Type 1 configured grant configuration and the first type configuration or the second type configuration is configured, avoid errors in parameter indication, thereby improving the reliability of the communication system.

[0225] The configured grant configuration information may be configured with the first SRI parameter and / or the second SRI parameter, where the first SRI parameter is associated with the first SRS resource set and / or the second SRI parameter is associated with the second SRS resource set. Optionally, the first SRI parameter is used for indicating the SRI (e.g., the first SRI). Optionally, the first SRI parameter indicates the SRS resource in the first SRS resource set. Optionally, the second SRI parameter is used for indicating the SRI (e.g., the second SRI). Optionally, the second SRI parameter indicates the SRS resource in the second SRS resource set. Optionally, the configured grant configuration information may indicate Type 2. Optionally, the configured grant configuration information corresponds to Type 2 configured grant. Optionally, when the transmission of the PUSCH is in the first type time domain resource, the transmission of the PUSCH is determined based on the first SRI parameter. Optionally, when the transmission of the PUSCH is in the second type time domain resource, the transmission of the PUSCH is determined based on the second SRI parameter. Here, the first SRI parameter may be referred to as first information. The second SRI parameter may be referred to as second information. In the disclosure, the names of the "first SRI parameter" and the "second SRI parameter" are not limited. The above method may facilitate the UE to obtain the parameter for indicating the SRI when the PUSCH corresponds to Type 2 configured grant configuration and the first type configuration or the second type configuration is configured, avoid errors in parameter indication, thereby improving the reliability of the reliability of the communication system.

[0226] Optionally, the UE may obtain DCI from the base station. Optionally, the UE detects the DCI format. Optionally, the DCI format schedules / indicates / triggers / activates the PUSCH. Optionally, the DCI format schedules / indicates / triggers / activates the transmission of the PUSCH. Optionally, the DCI format indicates the SRI. Optionally, the DCI format may include one SRI field, or two SRI fields. Optionally, the DCI format may include a first SRI field and / or a second SRI field. When the two SRS resource sets are configured, the DCI includes the first SRI field, or the DCI format includes the first SRI field and the second SRI field. The DCI including the first SRI field may be the DCI including only the first SRI field. The following method defines the method of determining the size of the DCI field under the condition associated with the first type configuration and / or the second type configuration. In the scenario associated with the first type configuration information, each PUSCH scheduled based on the DCI format is transmitted only in the first type time domain resource or only in the second type time domain resource. Therefore, the bitwidth size of the second SRI field is 0. The overhead of downlink control signaling may be saved and the efficiency of the communication system is improved. If a DCI format is used for scheduling the PUSCH associated with the second type configuration, the DCI format needs two SRI fields to respectively indicate the SRS resources in the two SRS resource sets.

[0227] The method for determining whether one SRI field or two SRI fields are included in the DCI format is discussed below. Optionally, when the DCI includes one SRI field, the DCI format includes the first SRI field. Optionally, when the DCI includes two SRI fields, the DCI format includes the first SRI field and / or the second SRI field. Optionally, the second SRI field may or may not exist. The second SRI field existing refers to the bitwidth (or the number of bits) of the second SRI field being greater than 0, or the bitwidth of the second SRI field being determined based on . The second SRI field not existing refers to the bitwidth of the second SRI field being equal to 0. When a first condition is satisfied, the bitwidth of the second SRI field is determined based on . Here, refers to the number of the SRS resources in the SRS resource set, or refers to the number of the SRS resources in the first SRS resource set, or refers to the number of the SRS resources in the second SRS resource set. When a second condition is satisfied, the bitwidth of the second SRI field is 0. Optionally, the first condition and the second condition may be complementary sets of each other. For example, when the first condition is satisfied, the second condition is not satisfied; or, when the second condition is satisfied, the first condition is not satisfied.

[0228] Here, the first condition includes at least one of the followings:

[0229] * In the PUSCH configuration information, the second type configuration is configured for the type of the first DCI format. Optionally, the first DCI format is of the same type as the DCI format indicating the SRI; refer above for the description of configuring the first type configuration or the second type configuration for the type of a specific DCI format;

[0230] * In the PUSCH configuration information, the second type configuration is configured; and / or at least one of the one or more configured grant configuration information is configured with the second type configuration. Optionally, the configured grant configuration information corresponds to Type 2 configured grant PUSCH transmission;

[0231] * The configured grant configuration information and the PUSCH configuration information are in the same uplink BWP configuration information.

[0232] Here, the second condition includes at least one of the followings:

[0233] * In the PUSCH configuration information, the first type configuration is configured for the type of the first DCI format. Optionally, the first DCI format is of the same type as the DCI format indicating the SRI; refer above for the description of configuring the first type configuration or the second type configuration for the type of a specific DCI format;

[0234] * In the PUSCH configuration information, the first type configuration is configured; and / or at least one (or each) of the one or more configured grant configuration information is configured with the first type configuration. Optionally, the configured grant configuration information corresponds to Type 2 configured grant PUSCH transmission;

[0235] * The configured grant configuration information and the PUSCH configuration information are in the same uplink BWP configuration information.

[0236] The method of determining the bitwidth of the first SRS field and / or the bitwidth of the second SRS field is discussed below. Optionally, the bitwidth of the first SRS field may be determined by Equation (1) or Equation (2). Equation (1) is , where refers to the maximum number of layers for PUSCH, refers to the number of the resources in the SRS resource set. Equation (2) is , where refers to the number of the resources in the SRS resource set.

[0237] Optionally, Equation (1) is for non-codebook-based transmission. For example, when txConfig is set to non-codebook, the UE uses Equation (1). Optionally, Equation (2) is for codebook-based transmission. For example, when txConfig is set to codebook, the UE uses Equation (2). Optionally, refers to the number of the resources in the SRS resource set associated with the first SRS field. Optionally, refers to the maximum value of the number of the resources in the first SRS resource set and the number of the resources in the second SRS resource set. Optionally, when the second condition is satisfied, refers to the maximum value of the number of the resources in the first SRS resource set and the number of the resources in the second SRS resource set. When the second condition is satisfied, the first SRI field may be used for indicating the first SRS resource set and the second SRS resource set. Therefore, the size of the first SRI field needs to be determined based on the larger value of the numbers of the resources in these two sets, so that sufficient bits may be used for indicating either of these two SRS resource sets, improving the flexibility of the communication system. Optionally, when the second condition is satisfied, the number of the resources in the first SRS resource set and the number of the resources in the second SRS resource set are the same. This configuration restriction avoids the situation where the number of the resources in the first SRS resource set and the number of the resources in the second SRS resource set are different, simplifying the operation of the UE.

[0238] Optionally, the bitwidth of the second SRS field may be determined by Equation (3), Equation (4), or Equation (5). Equation (3) is , where refers to the maximum number of layers for PUSCH, refers to the number of the resources in the SRS resource set. Equation (4) is , where refers to the number of the resources in the SRS resource set. Equation (5) is , where refers to the maximum number of layers for PUSCH, refers to the number of the resources in the SRS resource set.

[0239] Optionally, Equation (3) and / or Equation (5) are for non-codebook-based transmission. For example, when txConfig is set to non-codebook, the UE uses Equation (3) or Equation (5). Optionally, Equation (4) is for codebook-based transmission. For example, when txConfig is set to codebook, the UE uses Equation (4). Optionally, refers to the number of the resources in the SRS resource set associated with the first SRS field. Optionally, refers to the number of the resources in the second SRS resource set. If the number of layers indicated by the second SRI resource field is determined based on the number of layers indicated by the first SRI resource field, Equation (5) is used. Optionally, if the condition that the number of layers indicated by the second SRI resource field is determined based on the number of layers indicated by the first SRI resource field is not satisfied, Equation (3) is used. The number of layers indicated by the second SRI resource field being determined based on the number of layers indicated by the first SRI resource field may be the number of layers indicated by the second SRI resource field being equal to the number of layers indicated by the first SRI resource field.

[0240] Optionally, the DCI format may indicate one or two SRIs. Optionally, the DCI format detected by the UE may indicate one or two SRIs. Optionally, the DCI format may indicate the first SRI and / or the second SRI. Optionally, the first SRI is indicated by the first SRI field. Optionally, the second SRI is indicated by the second SRI field. When the bitwidth of the second SRI field in the DCI format is 0, it may be considered that the second SRI does not exist, or it may be considered that the second SRI is not indicated by the DCI format.

[0241] When the first condition is satisfied, and / or the DCI format indicates two SRIs, and / or the DCI format includes two SRI fields, and / or the sizes of both SRI fields are not 0, and / or the size of the second SRI field is not 0, the first SRI field is associated with the first SRS resource set, and / or the second SRI field is associated with the second SRS resource set. When the first condition is satisfied, and / or the DCI format indicates two SRIs, and / or the DCI format includes two SRI fields, and / or the sizes of both SRI fields is not 0, and / or the size of the second SRI field is not 0, the first SRI field indicates the SRS resource in the first SRS resource set, and / or the second SRI field indicates the SRS resource in the second SRS resource set.

[0242] When the second condition is satisfied, and / or the DCI format indicates one SRI, and / or the DCI format includes one SRI field, and / or the size of the second SRI field is 0, and / or the size of the first SRI field is not 0, the SRS resource set associated with the first SRI field is determined based on the type of the time domain resource where the PUSCH is located. When the second condition is satisfied, and / or the DCI format indicates one SRI, and / or the DCI format includes one SRI field, and / or the size of the second SRI field is 0, and / or the size of the first SRI field is not 0, the SRS resource set indicated by the first SRI field is determined based on the type of the time domain resource where the PUSCH is located. When the second condition is satisfied, and / or the DCI format indicates one SRI, and / or the DCI format includes one SRI field, and / or the size of the second SRI field is 0, and / or the size of the first SRI field is not 0, and / or the transmission of the PUSCH is in the first type time domain resource, the first SRI field is associated with the first SRS resource set. Optionally, when the second condition is satisfied, and / or the DCI format indicates one SRI, and / or the DCI format includes one SRI field, and / or the size of the second SRI field is 0, and / or the size of the first SRI field is not 0, and / or the transmission of the PUSCH is in the second type time domain resource, the first SRI field is associated with the second SRS resource set. Here, the SRS resource set associated with the SRI field refers to the SRS resource set indicated by the SRI field, or the resources in the SRS resource set indicated by the SRI field.

[0243] When the first condition is satisfied, and / or the DCI format indicates two SRIs, and / or the DCI format includes two SRI fields, and / or the sizes of both SRI fields are not 0, and / or the size of the second SRI field is not 0, and / or the PUSCH is not transmitted in one type of time domain resource, the UE ignores / drops the SRI indication corresponding to the type of the time domain resource and / or the SRI field corresponding to the type of the time domain resource. For example, when the PUSCH is not transmitted in the first type time domain resource, the UE ignores the SRI corresponding to the first type time domain resource (for example, the first SRI), and / or the SRI field corresponding to the first type time domain resource (for example, the first SRI field). For example, when the PUSCH is not transmitted in the second type time domain resource, the UE ignores the SRI corresponding to the second type time domain resource (for example, the second SRI), and / or the UE ignores the SRI field corresponding to the second type time domain resource (for example, the second SRI field).

[0244] When the first condition is satisfied, and / or the DCI format indicates two SRIs, and / or the DCI format includes two SRI fields, and / or the sizes of both SRI fields are not 0, and / or the size of the second SRI field is not 0, and / or the PUSCH is transmitted only in one type of time domain resource, the UE ignores / drops the SRI indication corresponding to the other type of time domain resources and / or the SRI field corresponding to the other type of time domain resource. For example, when the PUSCH is transmitted only in the first type time domain resource, the UE ignores the SRI corresponding to the second type time domain resource (for example, the second SRI), and / or the UE ignores the SRI field corresponding to the second type time domain resource (for example, the second SRI field). For example, when the PUSCH is transmitted only in the second type time domain resource, the UE ignores the SRI corresponding to the first type time domain resource (for example, the first SRI), and / or the UE ignores the SRI field corresponding to the first type time domain resource (for example, the first SRI field).

[0245] For uplink reception by the base station, a PUSCH transmission needs to be decoded based on the measurement result of its associated SRS transmission. Optionally, the UE determines the PUSCH transmission precoder for the PUSCH based on the transmission of the SRS resource associated with the SRI. The method of determining the transmission of the SRS resource associated with the SRI (the time domain resource where the transmission of the SRS resource associated with the SRI is located) is discussed below. Optionally, the type of the time domain resource where the transmission of the SRS resource associated with the SRI is located is of the same type as the time domain resource where the transmission of the PUSCH is located. Here, the types of time domain resources are the first type of the first type time domain resource and the second type of the second type time domain resource described above. For example, the transmission of the SRS resource associated with the SRI and the transmission of the corresponding PUSCH are both in the first type time domain resource, or both in the second type time domain resource, or both in the first type time domain resource and the second type time domain resource. Optionally, the SRI is associated with the transmission of the SRS resource in the SRS resource set indicated by the corresponding SRI field, where the transmission of the SRS resource is in the same type of time domain resource as the time domain resource associated with the corresponding SRS resource set, and the transmission of the SRS resource is the latest transmission, and the transmission of the SRS resource is before the PDCCH carrying the SRI. Optionally, the first SRI is associated with the transmission of the SRS resource in the SRS resource set indicated by the first SRI field, where the transmission of the SRS resource is in the same type of time domain resource as the time domain resource associated with the corresponding SRS resource set, and the transmission of the SRS resource is the latest transmission, and the transmission of the SRS resource is before the physical downlink control channel PDCCH carrying the SRI. Optionally, the second SRI is associated with the transmission of the SRS resource in the SRS resource set indicated by the second SRI field, where the transmission of the SRS resource is in the same type of time domain resource as the time domain resource associated with the corresponding SRS resource set, and the transmission of the SRS resource is the latest transmission, and the transmission of the SRS resource is before the physical downlink control channel PDCCH carrying the SRI. Optionally, the SRS resource set corresponding to the SRS may be understood as the SRS resource set where the SRS resource is located. The above transmission restrictions may allow for the PUSCH transmission to be based on the SRS transmission transmitted on the same type of time domain resource when the SBFD configuration information is configured, so that the base station can decode accordingly, thereby improving the reliability of the communication system.

[0246] Optionally, when the two SRS resource sets are configured and / or the SBFD configuration information is configured, the SRI includes one SRI or two SRIs. Optionally, each SRI may be associated with the transmission of an SRS resource. Optionally, the SRI is associated with the transmission of the SRS resource in the SRS resource set indicated by the SRI, where the transmission of the SRS resource is in the same type of time domain resource as the time domain resource associated with the SRI, and / or the transmission of the SRS resource is the latest transmission; and / or the transmission of the SRS resource is before the PDCCH carrying the SRI. Here, the SRS resource set indicated by the SRI may be the SRS resource set associated with the SRI. Optionally, the time domain resource associated with the SRI may be the time domain resource associated with the SRS resource set indicated by the SRI. Optionally, the time domain resource associated with the SRI may be the time domain resource where the PUSCH transmission associated with / indicated by the SRI. For example, when the SRI is associated with the first type time domain resource, the SRI is associated with the latest transmission of the SRS resource in the first type time domain resource that is earlier than the PDCCH carrying the SRI. For example, when the SRS resource set indicated by the SRI is associated with the first type time domain resource, the SRI is associated with the latest transmission of the SRS resource in the first type time domain resource that is earlier than the PDCCH carrying the SRI. Here, the SRI may be the first SRI and / or the second SRI. The above method defines the relation between the SRI and the transmission of the associated SRS resource, allows for the PUSCH transmission to be based on the SRS transmission transmitted on the same type of time domain resource when the SBFD configuration information is configured, so that the base station can decode accordingly, thereby improving the reliability of the communication system.

[0247] Optionally, when an SRS resource set is configured and / or the SBFD configuration information is configured, the SRI may include one SRI. Optionally, the SRI is used for indicating the resource in the SRS resource set. Optionally, the SRI may be associated with the transmission of one or two SRS resources. Optionally, the method for determining the transmission of the SRS resource associated with the SRI may be enabled or disabled by a higher layer parameter. The higher layer parameter may be configured, for example, when the SBFD configuration information is configured. Optionally, the higher layer parameter may indicate enabling or disabling. Optionally, the method for determining the transmission of the SRS resource associated with the SRI may be enabled or disabled by the UE capability. For example, the UE may or may not report UE capability signaling. Optionally, the method is enabled when the UE capability is reported. Optionally, the method is disabled when the UE capability is not reported. Optionally, the UE capability signaling indicates that the UE supports the UE to determine the transmission of the SRS resource associated with the SRI based on the type of the time domain resource. For example, when disabled, the SRI is associated with the latest transmission of the SRS resource identified by the SRI. Optionally, the SRS resource is before to the PDCCH carrying the SRI. For example, when enabled, the UE determines the transmission of the SRS resource associated with the SRI using the following method.

[0248] * When the PUSCH is applicable to the first type configuration, the SRI is associated with the transmission of an SRS resource. When the first type configuration is configured, the SRI is associated with the transmission of an SRS resource. When the PUSCH is applicable to the second type configuration and the PUSCH is only in one type of time domain resource, the SRI is associated with the transmission of an SRS resource. When the second type configuration is configured and the PUSCH is only in one type of time domain resource, the SRI is associated with the transmission of an SRS resource. Optionally, the SRI is associated with the transmission of the SRS resource indicated by the SRI in the SRS resource set, where the transmission of the SRS resource is in the same time domain resource type as the time domain resource associated with the SRI, and / or the transmission of the SRS resource is the latest transmission; and / or the transmission of the SRS resource is before the PDCCH carrying the SRI. Optionally, the time domain resource associated with the SRI may be the time domain resource where the PUSCH transmission associated with / indicated by the SRI. Optionally, the time domain resource associated with the SRI may be the time domain resource where the PUSCH associated with / indicated by the SRI is transmitted. For example, when the PUSCH is transmitted in the first type time domain resource, the SRI is associated with the latest transmission of the SRS resource in the first type time domain resource that is earlier than the PDCCH carrying the SRI. The method defines under what circumstances the SRI is associated with the transmission of an SRS, allows for the PUSCH transmission to be precoded using the SRS transmission on the same type of time domain resource, improving the performance of the communication system.

[0249] * When the PUSCH is applicable to the second type configuration and the PUSCH is in two types of time domain resources, the SRI is associated with the transmission of two SRS resources. When the second type configuration is configured and the PUSCH is in two types of time domain resources, the SRI is associated with the transmission of two SRS resources. When the PUSCH is transmitted in two types of time domain resources, the SRI is associated with the transmission of two SRS resources. Optionally, the PUSCH being in two types of time domain resources may be that the PUSCH is across two types of time domain resources, or the transmission occasions of the PUSCH is in two types of time domain resources, or the transmission occasions of the PUSCH is across two types of time domain resources. Here, the PUSCH may be the transmission of the PUSCH. Optionally, the SRI is associated with two transmissions (e.g., a first transmission and a second transmission) of the SRS resource indicated by the SRI in the SRS resource set. Optionally, the first transmission is in the first type time domain resource, and / or the first transmission is the latest transmission; and / or the first transmission is before the PDCCH carrying the SRI. Optionally, the second transmission is in the second type time domain resource, and / or the second transmission is the latest transmission; and / or the second transmission is before the PDCCH carrying the SRI. Optionally, the method may be used when the SRS resource set is periodic / semi-persistent. Optionally, the method may be used when the SRS resource in the SRS resource set is periodic / semi-persistent. The method defines under what circumstances the SRI is associated with the transmission of two SRSs, allows for the PUSCH transmission in two types of time domain resources to be precoded using the SRS transmission on different types of time domain resources, improving the performance of the communication system performance.

[0250] In the disclosure, the latest transmission may be the latest transmission relative to slot n, where slot n refers to the slot where the indicated SRI is located. The latest transmission may be the latest transmission before slot n. The latest transmission may be the latest transmission no later than slot n. In the disclosure, "the transmission of the SRS resource is before the PDCCH carrying the SRI" may be replaced with "the SRS resource is before the PDCCH carrying the SRI". In the disclosure, the SRS resource indicated by the SRI may be the SRS resource identified by the SRI.

[0251] Optionally, the UE may be configured with the SRS resource set for non-codebook-based transmission. Optionally, the SRS resource set is associated with a CSI-RS resource. Optionally, the CSI-RS resource is used for calculating the precoder for the transmission of the SRS. The transmission of the SRS may be the transmission of the SRS resource. Optionally, the transmission of the SRS resource (or the precoder for the transmission of the SRS resource) is determined based on the reception of the CSI-RS resource in the time domain resource of the same type as the time domain resource where the transmission of the SRS resource is located. Optionally, when the CSI-RS resource is periodic or semi-persistent and / or the SRS resource is periodic or semi-persistent, the transmission of the SRS resource (or the precoder for the transmission of the SRS resource) is determined based on the reception of the CSI-RS resource in the time domain resource of the same type as the time domain resource where the transmission of the SRS resource is located. For example, when the transmission of the SRS resource is in the first type time domain resource, the precoder for the transmission of the SRS resource is determined based on the reception of the associated CSI-RS resource in the first type time domain resource. Optionally, the transmission of the SRS resource (or the precoder for the transmission of SRS resources, or the precoder used by the transmission of the SRS resource) is determined based on the reception / measurement of the CSI-RS resource in the time domain resource of the same type as the time domain resource associated with the SRS resource set associated with the CSI-RS resource. Optionally, this method is applicable for the case that the CSI-RS resource is periodic or semi-persistent. Optionally, this method is applicable for the case that the SRS resource is periodic or semi-persistent. Optionally, when the CSI-RS resource is periodic or semi-persistent, and / or the SRS resources is periodic or semi-persistent, the transmission of the SRS resource (or the precoder for the transmission of the SRS resource, or the precoder used by the transmission of the SRS resource) is determined based on the reception / measurement of the CSI-RS resource in the time domain resource of the same type as the time domain resource associated with the SRS resource set associated with the CSI-RS resource. For example, when the SRS resource set is associated with the first type time domain resource, the precoder used by the transmission of the SRS is determined based on the reception / measurement of the CSI-RS resource associated with the SRS resource set in the first type time domain resource. For example, when the SRS resource set is associated with the second type time domain resource, the precoder used by the transmission of the SRS is determined based on the reception / measurement of the CSI-RS resource associated with the SRS resource set in the second type time domain resource. In the disclosure, the reception of the CSI-RS resource may be the reception of the occasion of the CSI-RS resource, or the reception of the transmission occasion of the CSI-RS resource, or the measurement of the CSI-RS resource, or the measurement of the occasion of the CSI-RS resource, or the measurement of the transmission occasion of the CSI-RS resource. In case where the UE is configured with the SBFD configuration information, the time domain resources may be divided into two types (refer above for the definition of the two types), and in some cases, interference conditions and / or spatial parameters corresponding to the two types of time domain resources may be different. For example, in the SBFD time domain resource, since the base station also performs downlink transmission during uplink reception, in the SBFD time domain resource, the uplink experiences greater interference compared to the non-SBFD time domain resource. For example, the antenna panel used by the base station in the SBFD time domain resource is different from the antenna panel used by the base station in the non-SBFD time domain resource. For non-codebook-based transmission, the calculation of the precoder for the SRS is determined by the measurement of the CSI-RS based on channel reciprocity. The above method may enable the UE to use the CSI-RS received in the same type of time domain resource to determine the transmission of the SRS / precoder for the SRS, thereby ensuring the accuracy of the SRS transmission and improving the performance of the communication system. Optionally, the method may be enabled and disabled by the higher layer parameter or the UE capability signaling. Refer above for description of enabling and disabling specific method by the higher layer parameter or the UE capability signaling. Optionally, the method is performed when the first type configuration is configured. For example, the method is performed when the PUSCH configuration information is configured with the first type configuration. For example, the method is performed when the configuration information for configuring the SRS resource set is configured with the first type configuration. Optionally, in the above, "the time domain resource where the transmission of the SRS resource is located" may be replaced with "the time domain resource where the transmission of the PUSCH is located".

[0252] In some cases, when the aperiodic SRS resource set is configured, the associated NZP CSI-RS is indicated by an SRS request field in the DCI. Optionally, If the UE is configured with aperiodic SRS associated with aperiodic NZP CSI-RS resource, the presence of the associated CSI-RS is indicated by the SRS request field if the value of the SRS request field is not '00'. Optionally, the CSI-RS is located in the same slot as the SRS request field. Optionally, the CSI-RS and the DCI where the SRS request field is located are in the same slot. Here, the UE behaviors or restrictions related to the types of time domain resources where the transmission of the (aperiodic) SRS is located and the types of time domain resources where the reception of the (aperiodic) CSI-RS is located need to be defined in order to utilize channel reciprocity, improving the performance of the communication system.

[0253] * Optionally, the UE determines whether to update the precoder for the SRS based on the SRS and the associated CSI-RS. Optionally, the UE determines whether to update the precoder for the SRS based on whether the type of the time domain resource where the SRS is located and the type of the time domain resource where the associated CSI-RS is located are the same. In the disclosure, the term "time domain resource where SRS is located" may be used interchangeably with the term "time domain resource associated with SRS resource set associated with SRS" or "time domain resources associated with SRS resource set". In the disclosure, the term "type of time domain resource where SRS is located" may be used interchangeably with the term "type of time domain resource associated with SRS resource set associated with SRS" or "type of time domain resource associated with SRS resource set". Optionally, the precoder for the SRS may be the precoding information of the SRS. Optionally, the precoder for the SRS is determined based on the SRS and the associated CSI-RS. Optionally, the SRS and the associated CSI-RS refer to (the type of) the time domain resource where the SRS is located and (the type of) the time domain resource where the associated CSI-RS is located. Optionally, the time domain resource where the SRS is located may be the time domain resource where the transmission of the SRS is located. Optionally, the time domain resource where the CSI-RS is located may be the time domain resource where the reception of the CSI-RS is located. Optionally, when the SRS and the associated CSI-RS are in the same type of time domain resource and / or a third condition is satisfied, the precoder for the SRS is updated, or the UE updates the precoder for the SRS, or the UE is expected to update the precoder for the SRS, or the UE updates the precoder for the SRS based on the CSI-RS. Optionally, the precoder for the SRS is updated based on the CSI-RS. Optionally, when the SRS and the associated CSI-RS are in different types of time domain resources and / or a fourth condition is satisfied, the precoder for the SRS is not updated, or the UE does not update the precoder for the SRS, or the UE is not expected to update the precoder for the SRS, or the UE does not update the precoder for the SRS based on the CSI-RS. Optionally, the precoder for the SRS is not updated based on the CSI-RS. Optionally, the precoder for the SRS is not expected to be updated based on the CSI-RS. Optionally, the UE does not update (or is not expected to update) the precoder for the SRS. Optionally, the UE is not (or is not expected to) update the precoder for the SRS based on the CSI-RS. Here, the CSI-RS may be a CSI-RS resource or reception of the CSI-RS resource. Here, the SRS may be an SRS resource.

[0254] * Optionally, the SRS and / or the associated CSI-RS and / or the associated PUSCH are located in the same type of time domain resources. Optionally, when the third condition is satisfied, the types of the time domain resource where the SRS is located and / or the time domain resource where the associated CSI-RS is located and / or the time domain resource where the associated PUSCH is located are the same. Optionally, the UE expects the types of the time domain resource where the SRS is located and / or the time domain resource where the associated CSI-RS is located and / or the time domain resource where the associated PUSCH is located to be the same. Optionally, when the third condition is satisfied, the UE expects the types of the time domain resource where the SRS is located and / or the time domain resource where the associated CSI-RS is located and / or the time domain resource where the associated PUSCH is located to be the same. Optionally, the UE does not expect the types of the time domain resource where the SRS is located and / or the time domain resource where the associated CSI-RS is located and / or the time domain resource where the associated PUSCH is located to be different. Optionally, when the third condition is satisfied, the UE does not expect the types of the time domain resource where the SRS is located and / or the time domain resource where the associated CSI-RS is located and / or the time domain resource where the associated PUSCH is located to be different. Optionally, the time domain resource where the SRS is located may be the time domain resource where the transmission of the SRS is located. Optionally, the time domain resource where the CSI-RS is located may be the time domain resource where the reception of the CSI-RS is located. Optionally, the time domain resource where the PUSCH is located may be the time domain resource where the transmission of the PUSCH is located. Optionally, the PUSCH associated with the SRS refers that the PUSCH is scheduled / indicated by a DCI format, and the DCI format indicates the SRS. Optionally, the types of the time domain resource where the SRS is located and / or the time domain resource where the associated CSI-RS is located and / or the time domain resource where the associated PUSCH is located are determined based on the PUSCH. Being determined based on the PUSCH refers to being determined based on the type of the time domain resource where the PUSCH is located. Optionally, the types of the time domain resource where the SRS is located and / or the time domain resource where the associated CSI-RS is located and / or the time domain resource where the associated PUSCH is located are determined based on the first transmission (or the earliest transmission) associated with the PUSCH. For example, when the PUSCH includes one or more PUSCHs, the types of the time domain resources are determined based on the first / earliest PUSCH of the one or more PUSCHs. For example, when the PUSCH includes one or more PUSCH repetitions, the types of the time domain resources are determined based on the first / earliest PUSCH repetition of the one or more PUSCH repetitions. The restriction can ensure that the SRS and / or the associated CSI-RS and / or the associated PUSCH are in the same type of time domain resources, ensuring the reciprocity between uplink and downlink and improving the performance of the communication system. Here, the CSI-RS may be a CSI-RS resource or reception of the CSI-RS resource. Here, the SRS may be an SRS resource.

[0255] * Optionally, the time domain resource (for example, slot) where the associated aperiodic CSI-RS is located is determined based on the time domain resource where the associated PUSCH transmission is located. Optionally, the time domain resource (for example, slot) where the associated aperiodic CSI-RS is located is determined based on the type of the time domain resource where the associated PUSCH transmission is located. Optionally, the time domain resource (e.g., slot) where the associated aperiodic CSI-RS is located is determined based on the type of the time domain resource where the associated PUSCH transmission is located and / or the time resource where the DCI (e.g., the DCI indicating the PUSCH) is located. Optionally, the associated PUSCH refers to the PUSCH transmission indicated by the DCI. Optionally, the associated PUSCH refers to the PUSCH transmission indicated by the SRI (e.g., the SRI indicated by the SRI field) in the DCI. Optionally, the time domain resource where the associated aperiodic CSI-RS is located is the earliest second slot that is no earlier than a first slot (or later than the first slot). Optionally, when the type of the time domain resource where DCI (or PDCCH corresponding to DCI) is located is the same as the type of the time domain resource where the associated PUSCH is located, the time domain resource where the associated aperiodic CSI-RS is located is the first slot. Optionally, when the type of the time domain resource where DCI (or the PDCCH corresponding to DCI) is located is different from the type of the time domain resource where the associated PUSCH is located, the time domain resource where the associated aperiodic CSI-RS is located is the earliest second slot after the first slot. Optionally, the second slot may be referred to as a valid slot. Optionally, the first slot is the slot where the DCI is located (or the slot where the SRI field is located). Optionally, the type of the time domain resource (for example, symbol) in the second slot is the same as the type of the time domain resource where the associated PUSCH transmission is located. Optionally, the type of all symbols (or at least one symbol) in the second slot are the same as the type of the time domain resource where the associated PUSCH transmission is located. Optionally, the type of the time domain resource occupied by the CSI-RS in the second slot is the same as the type of the time domain resource where the associated PUSCH transmission is located. Optionally, the type of (all) symbols occupied by the CSI-RS in the second slot are the same as the type of the symbol where the associated PUSCH transmission is located. For example, when the type of the time domain resource where the associated PUSCH transmission is located is an SBFD symbol, the symbol occupied by the CSI-RS in the second slot is an SBFD symbol. For example, when the type of the time domain resource where the associated PUSCH transmission is located is a non-SBFD symbol, the symbol occupied by the CSI-RS in the second slot is a non-SBFD symbol. Optionally, the second slot includes downlink symbols and / or flexible symbols. Optionally, the second slot only includes downlink symbols and / or flexible symbols. Optionally, all symbols in the second slot are downlink symbols and / or flexible symbols. Optionally, the second slot does not include uplink symbols. Optionally, at least one of the symbols occupied by CSI-RS in the second slot is a downlink symbol and / or a flexible symbol. Optionally, all symbols occupied by CSI-RS in the second slot are downlink symbols and / or flexible symbols. Optionally, the symbol occupied by CSI-RS in the second slot is not an uplink symbol. Optionally, the uplink symbols and / or downlink symbols and / or flexible symbols may be indicated by higher layer signaling (for example, RRC signaling and / or MAC-CE signaling). Optionally, the second slot is not in a measurement gap. Optionally, at least one of the symbols occupied by CSI-RS in the second slot is not in the measurement gap. Optionally, all symbols occupied by CSI-RS in the second slot are not in the measurement gap. Optionally, the method is applicable when the third condition is satisfied. The method may allow for DCI and the associated aperiodic CSI-RS to be used on different types of time domain resources, improving the flexibility of the communication system scheduling. The method allows for the associated CSI-RS to be postponed so that the PUSCH and the associated CSI-RS are in the same time domain type when the slot where the DCI is located and the type of the time domain resource where the PUSCH transmission is located are different, facilitates the measurement of the UE using the aperiodic CSI-RS, improving the reliability of the communication system scheduling. Optionally, the DCI may indicate one or more PUSCHs (or repetitions of the PUSCH), where the one or more PUSCHs (or repetitions of the PUSCH) are respectively in different types of time domain resources. Optionally, the UE may transmit the one or more PUSCHs (or repetitions of the PUSCH). Optionally, the DCI may trigger / indicate two aperiodic CSI-RSs, where the two aperiodic CSI-RSs are associated with different types of time domain resources. These two aperiodic CSI-RSs may be associated with the transmission of SRS and / or PUSCH (repetition of PUSCH) on the corresponding types of time domain resources, respectively. The time domain resources (e.g., slots) where the two aperiodic CSI-RSs are located may be determined by the above method respectively. In the disclosure, the term "time domain resource where the associated PUSCH transmission is located" may be used interchangeably with "time domain resource associated with SRS resource set associated with CSI-RS". In the disclosure, the term "the type of time domain resource where the associated PUSCH transmission is located" may be used interchangeably with "the type of time domain resource associated with SRS resource set associated with CSI-RS". In the disclosure, the term "symbol where the associated PUSCH transmission is located" may be used interchangeably with "symbol associated with SRS resource set associated with CSI-RS". In the disclosure, the term "type of symbol where the associated PUSCH transmission is located" may be used interchangeably with "type of symbol associated with SRS resource set associated with CSI-RS".

[0256] * Optionally, the time domain resource (for example, slot) where the associated aperiodic CSI-RS is located is determined based on the time domain resource where the associated PUSCH transmission is located. Optionally, the time domain resource (e.g., slot) where the associated aperiodic CSI-RS is located is determined based on the type of the time domain resource where the associated PUSCH transmission is located and / or the time resource where the DCI (e.g., the DCI indicating the PUSCH) is located. Optionally, the associated PUSCH refers to the PUSCH transmission indicated by DCI. Optionally, the associated PUSCH refers to the PUSCH transmission indicated by the SRI indicated by the SRI field in the DCI. Optionally, when the type of the symbol included in the slot where the DCI is located is of the same type of the symbol where the PUSCH transmission is located, the slot where the CSI-RS is located is the same as the slot where the DCI is located. Optionally, when the type of the symbol included in the slot where the DCI is located is different from the type of symbol where the PUSCH transmission is located, the slot where the CSI-RS is located is postponed. Optionally, when the type of the symbol included in the slot where the DCI is located is different from the type of symbol where the transmission of the PUSCH is located, the slot where the CSI-RS is located is the earliest third slot that is no earlier (or later) than the slot where the DCI is located. Optionally, the type of the symbol included in the third slot is of the same type as the symbol where the PUSCH transmission is located. Optionally, the type of the symbol included in the slot where the DCI is located refers to the type of (all) symbols of the CSI-RS in the slot where the DCI is located. Optionally, the type of the symbol included in the slot where the DCI is located refers to the type of all symbols (or at least one symbol) included in the slot where the DCI is located. Optionally, the type of the symbol included in the slot where DCI is located refers to the type of the symbol where the PDCCH corresponding to DCI is located. Optionally, the type of the symbol included in the third slot refers to the type of (all) symbols of the CSI-RS in the third slot. Optionally, the type of the symbol included in the third slot refers to the type of all symbols included in the third slot. The type of the symbol may be an SBFD symbol or a non-SBFD symbol. Optionally, the third slot includes downlink symbols and / or flexible symbols. Optionally, the third slot only includes downlink symbols and / or flexible symbols. Optionally, all symbols in the third slot are downlink symbols and / or flexible symbols. Optionally, the third slot does not include uplink symbols. Optionally, at least one of the symbols occupied by CSI-RS in the third slot is a downlink symbol and / or a flexible symbol. Optionally, all symbols occupied by CSI-RS in the third slot are downlink symbols and / or flexible symbols. Optionally, the symbol occupied by CSI-RS in the third slot is not an uplink symbol. Optionally, the uplink symbols and / or downlink symbols and / or flexible symbols may be indicated by higher layer signaling (for example, RRC signaling and / or MAC-CE signaling). Optionally, the third slot is not in a measurement gap. Optionally, at least one of the symbols occupied by CSI-RS in the third slot is not in the measurement gap. Optionally, all symbols occupied by CSI-RS in the third slot are not in the measurement gap. Optionally, the method is applicable when the third condition is satisfied. The method may allow for DCI and the associated aperiodic CSI-RS to be used on different types of time domain resources, improving the flexibility of the communication system scheduling. The method allows for the associated CSI-RS to be postponed so that the PUSCH and the associated CSI-RS are in the same time domain type when the slot where the DCI is located and the type of the time domain resource where the PUSCH transmission is located are different, facilitates the measurement of the UE using the aperiodic CSI-RS, improving the reliability of the communication system scheduling. Optionally, the DCI may indicate one or more PUSCHs (or repetitions of the PUSCH), where the one or more PUSCHs (or repetitions of the PUSCH) are respectively in different types of time domain resources. Optionally, the UE may transmit the one or more PUSCHs (or repetitions of the PUSCH). Optionally, the DCI may trigger / indicate two aperiodic CSI-RSs, where the two aperiodic CSI-RSs are associated with different types of time domain resources. These two aperiodic CSI-RSs may be associated with the transmission of SRS and / or PUSCH (repetition of PUSCH) on corresponding types of time domain resources, respectively. The time domain resources (e.g., slots) where the two aperiodic CSI-RSs are located may be determined by the above method respectively. In the disclosure, the term "time domain resource where the associated PUSCH transmission is located" may be used interchangeably with "time domain resource associated with SRS resource set associated with CSI-RS". In the disclosure, the term "the type of time domain resource where the associated PUSCH transmission is located" may be used interchangeably with "the type of time domain resource associated with SRS resource set associated with CSI-RS". In the disclosure, the term "symbol where the associated PUSCH transmission is located" may be used interchangeably with "symbol associated with SRS resource set associated with CSI-RS". In the disclosure, the term "type of symbol where the associated PUSCH transmission is located" may be used interchangeably with "type of symbol associated with SRS resource set associated with CSI-RS".

[0257] * Optionally, the symbol occupied by the CSI-RS may be referred to as the symbol of the CSI-RS. Optionally, the symbol occupied by the CSI-RS may be referred to as the symbol where the CSI-RS is located. Optionally, in a slot, the symbol occupied by the CSI-RS may be determined by the parameter resourceMapping associated with / corresponding to the CSI-RS.

[0258] * The third condition includes at least one of the followings:

[0259] ** The SBFD configuration information is configured;

[0260] ** The SRS is aperiodic and / or the CSI-RS is aperiodic;

[0261] ** The PUSCH is associated with the first type configuration, or the PUSCH is not associated with the second type configuration, or the PUSCH is applicable to the first type configuration, or the PUSCH is configured with the first type configuration. For example, the DCI format indicates the SRS and / or the CSI-RS, and the DCI format indicates the PUSCH. Optionally, the PUSCH is associated with the first type configuration, or the PUSCH is not associated with the second type configuration. Optionally, (the transmission of) the PUSCH is determined based on the PUSCH configuration information. Optionally, the PUSCH configuration information is configured with the first type configuration. Optionally, the PUSCH configuration information is not configured with the second type configuration;

[0262] ** The SRS is associated with the first type configuration, or the SRS is not associated with the second type configuration, or the SRS is applicable to the first type configuration, or the SRS is configured with the first type configuration. Optionally, the SRS is determined based on the configuration information indicating the SRS resource set (or based on the SRS configuration information). Optionally, the configuration information of the SRS resource set (or the SRS configuration information) is configured with the first type configuration. Optionally, the configuration information of the SRS resource set (or the SRS configuration information) is not configured with the second type configuration;

[0263] ** The CSI-RS is associated with the first type configuration, or the CSI-RS is not associated with the second type configuration, or the CSI-RS is applicable to the first type configuration, or the CSI-RS is configured with the first type configuration. Optionally, the CSI-RS resource corresponding to the CSI-RS is configured with the first type configuration, and / or the CSI-RS resource group where the CSI-RS resource corresponding to the CSI-RS is located is configured with the first type configuration. Optionally, the CSI-RS resource corresponding to the CSI-RS is not configured with the second type configuration, and / or the CSI-RS resource group where the CSI-RS resource corresponding to the CSI-RS is located is not configured with the second type configuration;

[0264] ** The gap from the last symbol of the reception of the CSI-RS resource and the first symbol of the SRS transmission is no less than 42 OFDM symbols, where the SCS configurationμis the smallest SCS configuration between the CSI-RS resource and the SRS transmission. Optionally, the CSI-RS in the second slot satisfies the above description (for example, the time domain relation between CSI-RS and SRS). Optionally, the CSI-RS in the third slot satisfies the above description (for example, the time domain relation between CSI-RS and SRS). This method may allow the UE to have enough time to update the transmitted precoder on the earliest second slot or the earliest third slot, improving the uplink transmission performance of the UE.

[0265] * The fourth condition includes at least one of the followings:

[0266] ** The SBFD configuration information is configured;

[0267] ** The SRS is aperiodic and / or CSI-RS is aperiodic;

[0268] ** The PUSCH is associated with the second type configuration, or the PUSCH is not associated with the first type configuration, or the PUSCH is applicable to the second type configuration, or the PUSCH is configured with the second type configuration. For example, the DCI format indicates the SRS and / or the CSI-RS, and the DCI format indicates the PUSCH. Optionally, the PUSCH is associated with the second type configuration, or the PUSCH is not associated with the first type configuration. Optionally, (the transmission of) the PUSCH is determined based on the PUSCH configuration information. Optionally, the PUSCH configuration information is configured with the second type configuration. Optionally, the PUSCH configuration information is not configured with the first type configuration;

[0269] ** The SRS is associated with the second type configuration, or the SRS is not associated with the first type configuration, or the SRS is applicable to the second type configuration, or the SRS is configured with the second type configuration. Optionally, the SRS is determined based on the configuration information indicating the SRS resource set (or based on the SRS configuration information). Optionally, the configuration information of the SRS resource set (or the SRS configuration information) is configured with the second type configuration. Optionally, the configuration information of the SRS resource set (or the SRS configuration information) is not configured with the first type configuration;

[0270] ** The CSI-RS is associated with the second type configuration, or the CSI-RS is not associated with the first type configuration, or the CSI-RS is applicable to the second type configuration, or the CSI-RS is configured with the second type configuration. Optionally, the CSI-RS resource corresponding to the CSI-RS is configured with the second type configuration, and / or the CSI-RS resource group where the CSI-RS resource corresponding to the CSI-RS is located is configured with the second type configuration. Optionally, the CSI-RS resource corresponding to the CSI-RS is not configured with the first type configuration, and / or the CSI-RS resource group where the CSI-RS resource corresponding to the CSI-RS is located is not configured with the first type configuration;

[0271] ** The gap from the last symbol of the reception of the CSI-RS resource and the first symbol of the SRS transmission is less than 42 OFDM symbols, where the SCS configurationμis the smallest SCS configuration between the CSI-RS resource and the SRS transmission. Optionally, the CSI-RS in the second slot satisfies the above description (for example, the time domain relation between CSI-RS and SRS). Optionally, the CSI-RS in the third slot satisfies the above description (for example, the time domain relation between CSI-RS and SRS). This method may allow the UE to have enough time to update the transmitted precoder on the earliest second slot or the earliest third slot, improving the uplink transmission performance of the UE.

[0272] FIG. 5 illustrates a method 500 performed by a base station according to various embodiments of the disclosure. The method 500 includes: at 501, the base station transmits configuration information for subband non-overlapping full duplex (SBFD), wherein the configuration information for the SBFD indicates an SBFD time domain resource, the SBFD time domain resource is a first type time domain resource, and a resource other than the SBFD time domain resource is a second type time domain resource; at 502, the base station receives configuration information for configuring a sounding reference signal (SRS) resource set; at 503, the base station transmits configuration information or DCI for PUSCH; and at 504, the base station receives a PUSCH, the PUSCH is based on an SRI determined by the configuration information or DCI for PUSCH, wherein the SRI is used for determining an SRS resource in the SRS resource set configured by the configuration information for configuring the SRS resource set, wherein the type of the time domain resource where the reception of the SRS resource associated with the SRI is located is the same as the type of the time domain resource where the reception of the PUSCH is located.

[0273] FIG. 6 illustrates a structure 600 of a user equipment according to various embodiments of the disclosure. As shown in FIG. 6, the user equipment 600 includes a controller 610 and a transceiver 620, where the controller 610 is configured to perform various methods disclosed herein as performed by the user equipment, and the transceiver 620 is configured to transmit and receive channels or signals.

[0274] FIG. 7 illustrates a structure 700 of a base station according to various embodiments of the disclosure. As shown in FIG. 7, the network device 700 includes a controller 710 and a transceiver 720, where the controller 710 is configured to perform various methods disclosed herein as performed by the network device, and the transceiver 720 is configured to transmit and receive channels or signals.

[0275] Furthermore, "at least one entry / at least one" described in the disclosure includes any and / or all possible combinations of the listed items, and various embodiments and various examples of the embodiments described in the disclosure may be used in any appropriate form changes and combinations, and " / " described in the disclosure means "or".

[0276] The various illustrative logical blocks, modules, and circuits described in the disclosure may be implemented or performed with a general purpose processor a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general-purpose processor may be a microprocessor but in the alternative, the processor may be any conventional processor controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.

[0277] The steps of a method or algorithm described in the disclosure may be embodied directly in hardware, in a software module executed by a processor in a combination of the two. A software module may reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, a removable disk, or any other form of storage medium known in the art. An exemplary storage medium is coupled to the processor such that the processor can read information from, and write information to, the storage medium. In the alternative, the storage medium may be integral to the processor. The processor and the storage medium may reside in an ASIC. The ASIC may reside in a user terminal. In the alternative, the processor and the storage medium may reside as discrete components in a user terminal.

[0278] In one or more exemplary designs, the functions described may be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, the functions may be stored or transmitted over as one or more instructions or code on a computer-readable medium. Computer-readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. Storage media may be any available media that can be accessed by a general purpose or special purpose computer.

[0279] The description set forth herein, in connection with the appended drawings, describes example configurations, methods, and apparatuses and does not represent all the examples that may be implemented or that are within the scope of the claims. The term "example" used herein means "serving as an example, instance, or illustration" and not "preferred" or "advantageous over other examples". The detailed description includes specific details for the purpose of providing an understanding of the described techniques. These techniques, however, may be practiced without these specific details. In some instances, well-known structures and devices are shown in block diagram form in order to avoid obscuring the concepts of the described examples.

[0280] While this specification contains many specific implementation details, these should not be construed as limitations on the scope of any inventions or of what may be claimed, but rather as descriptions of features specific to particular embodiments of particular inventions. Certain features that are described in this specification in the context of separate embodiments can also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment can also be implemented in multiple embodiments separately or in any suitable subcombination. Moreover, although features may be described above as acting in certain combinations and even initially claimed as such, one or more features from a claimed combination can in some cases be excised from the combination, and the claimed combination may be directed to a subcombination or variant of a subcombination.

[0281] It is to be understood that the specific order or hierarchy of steps in the methods of the disclosure is an illustration of exemplary processes. Based upon design preferences, it is understood that the specific order or hierarchy of steps in the methods may be rearranged to achieve the functions and effects disclosed herein. The accompanying method claims present elements of the various steps in a sample order, and are not meant to be limited to the specific order or hierarchy presented unless specifically recited therein. Furthermore, although elements may be described or claimed in the singular, the plural is contemplated unless limitation to the singular is explicitly stated. Accordingly, the disclosure is not limited to illustrated examples and any means for performing the functionality described herein are included in aspects of the disclosure.

[0282] The text and drawings are provided as examples only to help readers understand the disclosure. They are not intended and should not be interpreted as limiting the scope of the disclosure in any way. Although certain embodiments and examples have been provided, based on the content disclosed herein, it is obvious to those skilled in the art that modifications to the illustrated embodiments and examples can be made without departing from the scope of the disclosure.

Claims

A method performed by a user equipment (UE) in a communication system, the method comprising:receiving, from a base station (BS), information related to subband non-overlapping full duplex (SBFD);based on the information, identifying a type of symbol for symbols related to a Type 2 configured grant (CG) physical uplink shared channel (PUSCH) transmission associated with a latest activation downlink control information (DCI);performing the Type 2 CG PUSCH transmission in the symbols related to the type of symbol,wherein the type of symbol is a valid symbol type,wherein the valid symbol type is based on first transmission of the Type 2 CG PUSCH after the latest activation DCI.The method of claim 1,wherein the Type 2 CG PUSCH transmission is in SBFD symbols in case that the first transmission of the Type 2 CG PUSCH after the latest activation DCI is in SBFD symbols,wherein the Type 2 CG PUSCH transmission is in non-SBFD symbols in case that the first transmission of the Type 2 CG PUSCH after the latest activation DCI is in non-SBFD symbol.The method of claim 1, further comprising:receiving, from the BS, information for sounding reference signal (SRS) resource sets;identifying a SRS resource set related to the valid symbol type based on the information,wherein a SRI for the Type 2 CG PUSCH is associated with the most recent transmission of a SRS resource in the SRS resource set,wherein the most recent transmission of the SRS resource is prior to a physical downlink control channel (PDCCH) carrying the SRS resource indicator (SRI).The method of claim 3,wherein the SRS resource set is associated with a channel state information - reference signal (CSI-RS) in case that the Type 2 CG PUSCH is transmitted based on non-codebook,wherein, in case that resources of the CSI-RS are set to periodic or semi-persistent, the CSI-RS related to the valid symbol type is used to calculate the precoder for the transmission of the SRS resource.A method performed by a base station (BS) in a communication system, the method comprising:transmitting, to a user equipment (UE), information related to subband non-overlapping full duplex (SBFD);receiving, from the UE, a Type 2 CG PUSCH transmission in the symbols related to a type of symbol,wherein the type of symbol for symbols related to the Type 2 configured grant (CG) physical uplink shared channel (PUSCH) transmission associated with a latest activation downlink control information (DCI) is identified based on the information,wherein the type of symbol is a valid symbol type,wherein the valid symbol type is based on first transmission of the Type 2 CG PUSCH after the latest activation DCI.The method of claim 5,wherein the Type 2 CG PUSCH transmission is in SBFD symbols in case that the type of symbol related to first transmission of the Type 2 CG PUSCH after the latest activation DCI is SBFD symbol,wherein the Type 2 CG PUSCH transmission is in non-SBFD symbols in case that the type of symbol related to first transmission of the Type 2 CG PUSCH after the latest activation DCI is non-SBFD symbol.The method of claim 5, further comprising:transmitting, to the UE, information for sounding reference signal (SRS) resource setswherein a SRS resource set related to the valid symbol type is identified based on the information,wherein a SRI for the Type 2 CG PUSCH is associated with the most recent transmission of a SRS resource in the SRS resource set,wherein the most recent transmission of the SRS resource is prior to a physical downlink control channel (PDCCH) carrying the SRS resource indicator (SRI).The method of claim 7,wherein the SRS resource set is associated with a channel state information - reference signal (CSI-RS) in case that the Type 2 CG PUSCH is transmitted based on non-codebook,wherein, in case that resources of the CSI-RS are set to periodic or semi-persistent, the CSI-RS related to the valid symbol type is used to calculate the precoder for the transmission of the SRS resource.A user equipment (UE) in a wireless communication system, comprising:a transceiver; anda controller coupled to the transceiver and configured to:receive, from a base station (BS), information related to subband non-overlapping full duplex (SBFD);based on the information, identify a type of symbol for symbols related to a Type 2 configured grant (CG) physical uplink shared channel (PUSCH) transmission associated with a latest activation downlink control information (DCI);perform the Type 2 CG PUSCH transmission in the symbols related to the first type of symbol,wherein the type of symbol is a valid symbol type,wherein the valid symbol type is based on first transmission of the Type 2 CG PUSCH after the latest activation DCI.The UE of claim 9,wherein the Type 2 CG PUSCH transmission is in SBFD symbols in case that the first transmission of the Type 2 CG PUSCH after the latest activation DCI is in SBFD symbols,wherein the Type 2 CG PUSCH transmission is in non-SBFD symbols in case that the first transmission of the Type 2 CG PUSCH after the latest activation DCI is in non-SBFD symbol.The UE of claim 9, the controller is further configured to:receive, from the BS, information for a sounding reference signal (SRS) resource sets,identify a SRS resource set related to the valid symbol type based on the information,wherein a SRI for the Type 2 CG PUSCH is associated with the most recent transmission of a SRS resource in the SRS resource set,wherein the most recent transmission of the SRS resource is prior to a physical downlink control channel (PDCCH) carrying the SRS resource indicator (SRI).The UE of claim 11,wherein the SRS resource set is associated with a channel state information - reference signal (CSI-RS) in case that the Type 2 CG PUSCH is transmitted based on non-codebook,wherein, in case that resources of the CSI-RS are set to periodic or semi-persistent, the CSI-RS related to the valid symbol type is used to calculate the precoder for the transmission of the SRS resource.A base station (BS) in a wireless communication system, comprising:a transceiver; anda controller coupled to the transceiver and configured to:transmit, to a user equipment (UE), information related to subband non-overlapping full duplex (SBFD);receive, from the UE, a Type 2 CG PUSCH transmission in the symbols related to a type of symbol,wherein the type of symbol for symbols related to the Type 2 configured grant (CG) physical uplink shared channel (PUSCH) transmission associated with a latest activation downlink control information (DCI) is identified based on the information,wherein the type of symbol is a valid symbol type,wherein the valid symbol type is based on first transmission of the Type 2 CG PUSCH after the latest activation DCI.The BS of claim 13,wherein the Type 2 CG PUSCH transmission is in SBFD symbols in case that the first transmission of the Type 2 CG PUSCH after the latest activation DCI is in SBFD symbols,wherein the Type 2 CG PUSCH transmission is in non-SBFD symbols in case that the first transmission of the Type 2 CG PUSCH after the latest activation DCI is in non-SBFD symbol.The BS of claim 13, the controller is further configured to:transmit, to the UE, information for a sounding reference signal (SRS) resource set related to the valid symbol type,wherein a SRS resource set related to the valid symbol type is identified based on the information,wherein a SRI for the Type 2 CG PUSCH is associated with the most recent transmission of a SRS resource in the SRS resource set,wherein the most recent transmission of the SRS resource is prior to a physical downlink control channel (PDCCH) carrying the SRS resource indicator (SRI).

Citation Information

Patent Citations

  • Method and apparatus for power headroom reporting in a full-duplex system

    WO2024144157A1