CSI reporting method and apparatus, CSI receiving method and apparatus, and communication system

Abstract

Embodiments of the present application provide a CSI reporting method and apparatus, a CSI receiving method and apparatus, and a communication system. The CSI reporting method comprises: a terminal device receiving downlink control information (DCI) used for activating a semi-persistent CSI trigger state; and performing semi-persistent CSI reporting over PUSCHs. Among the PUSCHs, a PUSCH overlapping a first time domain resource is not used for the semi-persistent CSI reporting, or a PUSCH overlapping a second time domain resource is not used for the semi-persistent CSI reporting, or both the PUSCH overlapping the first time domain resource and the PUSCH overlapping the second time domain resource are used for the semi-persistent CSI reporting.

Description

CSI reporting and receiving method, apparatus and communication system TECHNICAL FIELD

[0001] The present application relates to the field of communication technology. BACKGROUND

[0002] In the prior art, for a time division duplex (TDD) frequency band, uplink transmission can only occur in an uplink time period. When a limited or small uplink time period is allocated, there will be problems of small coverage, capacity and large delay of uplink.

[0003] It should be noted that the above introduction to the technical background is only for the convenience of clearly and completely describing the technical solutions of the present application and facilitating the understanding of those skilled in the art. The above technical solutions cannot be considered as known to those skilled in the art merely because they are described in the background section of the present application.

[0004] SUMMARY

[0005] In order to improve the capacity and coverage of uplink transmission and reduce the delay of uplink transmission, in a TDD frequency band, a network device can work in a full duplex mode at certain time positions, for example, at the time positions, the network device simultaneously receives and transmits in different frequency domain resources in the corresponding carrier of the TDD frequency band. This working mode is referred to as sub-band non-overlapping full duplex (SBFD) for example, but is not limited thereto.

[0006] On the other hand, a semi-persistent channel state information (CSI) triggering state can be activated by downlink control information (DCI), and then the UE can perform corresponding semi-persistent CSI reporting on the corresponding physical uplink shared channel (PUSCH). However, in the case of supporting the above working mode, there is currently no solution for how to transmit / receive these PUSCHs carrying CSI.

[0007] To solve at least one of the above problems, embodiments of the present application provide a CSI reporting and receiving method, apparatus and communication system.

[0008] According to an aspect of embodiments of the present application, a CSI reporting method is provided, comprising:

[0009] receiving, by a terminal device, downlink control information (DCI) for activating a semi-persistent CSI triggering state; and

[0010] reporting, by the terminal device, semi-persistent CSI on a PUSCH.

[0011] wherein, in the PUSCH: the PUSCH overlapping with the first time domain resource is not used for the semi-persistent CSI reporting, or the PUSCH overlapping with the second time domain resource is not used for the semi-persistent CSI reporting, or both the PUSCH overlapping with the first time domain resource and the PUSCH overlapping with the second time domain resource are used for the semi-persistent CSI reporting; in the first time domain resource, a first frequency domain resource is used for uplink and a second frequency domain resource is used for downlink, and the second time domain resource is outside the first time domain resource.

[0012] According to another aspect of the embodiments of the present application, a CSI reporting device is provided, comprising:

[0013] a receiver configured to receive a downlink control information (DCI) for activating a semi-persistent CSI trigger state; and a transmitter configured to perform semi-persistent CSI reporting on a PUSCH;

[0014] wherein, in the PUSCH: the PUSCH overlapping with the first time domain resource is not used for the semi-persistent CSI reporting, or the PUSCH overlapping with the second time domain resource is not used for the semi-persistent CSI reporting, or both the PUSCH overlapping with the first time domain resource and the PUSCH overlapping with the second time domain resource are used for the semi-persistent CSI reporting; in the first time domain resource, a first frequency domain resource is used for uplink and a second frequency domain resource is used for downlink, and the second time domain resource is outside the first time domain resource.

[0015] According to another aspect of the embodiments of the present application, a CSI reporting method is provided, comprising:

[0016] a network device configured to send a downlink control information (DCI) for activating a semi-persistent CSI trigger state; and

[0017] the network device configured to receive semi-persistent CSI reporting on a PUSCH;

[0018] wherein, in the PUSCH: the PUSCH overlapping with the first time domain resource is not used for the semi-persistent CSI reporting, or the PUSCH overlapping with the second time domain resource is not used for the semi-persistent CSI reporting, or both the PUSCH overlapping with the first time domain resource and the PUSCH overlapping with the second time domain resource are used for the semi-persistent CSI reporting; in the first time domain resource, a first frequency domain resource is used for uplink and a second frequency domain resource is used for downlink, and the second time domain resource is outside the first time domain resource.

[0019] According to another aspect of the embodiments of the present application, a CSI receiving device is provided, comprising:

[0020] a transmitter that transmits a downlink control information (DCI) for activating a semi-persistent CSI triggering state; and

[0021] a receiver that receives a semi-persistent CSI reporting on a PUSCH;

[0022] wherein, in the PUSCH: the PUSCH overlapping with a first time domain resource is not used for the semi-persistent CSI reporting, or the PUSCH overlapping with a second time domain resource is not used for the semi-persistent CSI reporting, or both the PUSCH overlapping with the first time domain resource and the PUSCH overlapping with the second time domain resource are used for the semi-persistent CSI reporting; in the first time domain resource, a first frequency domain resource is used for uplink and a second frequency domain resource is used for downlink, and the second time domain resource is out of the first time domain resource.

[0023] According to another aspect of the embodiments of the present application, a communication system is provided, comprising:

[0024] a network device that transmits a downlink control information (DCI) for activating a semi-persistent CSI triggering state; and receives a semi-persistent CSI reporting on a PUSCH;

[0025] a terminal device that receives a downlink control information (DCI) for activating a semi-persistent CSI triggering state; and performs a semi-persistent CSI reporting on a PUSCH;

[0026] wherein, in the PUSCH: the PUSCH overlapping with a first time domain resource is not used for the semi-persistent CSI reporting, or the PUSCH overlapping with a second time domain resource is not used for the semi-persistent CSI reporting, or both the PUSCH overlapping with the first time domain resource and the PUSCH overlapping with the second time domain resource are used for the semi-persistent CSI reporting; in the first time domain resource, a first frequency domain resource is used for uplink and a second frequency domain resource is used for downlink, and the second time domain resource is out of the first time domain resource.

[0027] One of the beneficial effects of the embodiments of the present application is that the terminal device receives a downlink control information (DCI) for activating a semi-persistent CSI triggering state; and performs a semi-persistent CSI reporting on a PUSCH. Thus, the network device can work in a full duplex mode (simultaneous receiving and transmitting), and the terminal device can also utilize the corresponding resources to transceive signals when the network device works in the full duplex mode, which can improve the capacity and coverage of uplink transmission, reduce the latency of uplink transmission, and improve the resource allocation flexibility and resource utilization.

[0028] The particular implementations of the application described in detail below are illustrative only and are not intended to limit the scope of the application. Numerous variations and modifications can be made to the embodiments of the application described and illustrated without departing from the spirit and scope of the application. Accordingly, the scope of the application is not intended to be limited to the particular embodiments described in the specification. The application is based on and claims the benefit of U.S. Provisional Patent Application No. 62 / 692, 1 10, filed on June 28, 2018, which is incorporated by reference in its entirety for all purposes as if fully set forth herein.

[0029] Features described and / or illustrated with respect to one implementation can be used in one or more other implementations in the same or similar manner, in combination with or in place of features in the other implementations.

[0030] It should be emphasized that the term "comprises / comprising" when used in this specification is taken to mean the presence of stated features, integers, steps or components but does not preclude the presence or addition of one or more other features, integers, steps, components or groups thereof. BRIEF DESCRIPTION OF DRAWINGS

[0031] Elements and features of one or more embodiments described in the specification and / or one or more figures can be combined with elements and features of one or more other embodiments or figures in any manner within the scope of the application. Additionally, elements and features of the disclosure described can apply to any specific embodiment and / or figure of the application where such elements and features are not mutually exclusive.

[0032] The accompanying drawings are included to provide a further understanding of embodiments of the application and are incorporated in and constitute a part of the specification, illustrate embodiments of the application and, together with the description, serve to explain the principles of the application. It is to be understood that the drawings are for purposes of illustration only and are not necessarily drawn to scale, that the dimensions of the various features in the drawings can have been exaggerated for clarity, and that the drawings are merely illustrative based on a design scheme set forth in the description and the conception of the present application held by the inventor(s). In the drawings:

[0033] FIG. 1 is a schematic diagram of a communication system according to an embodiment of the application;

[0034] FIG. 2 is a schematic diagram of a CSI reporting method according to an embodiment of the application;

[0035] FIG. 3 is an example diagram of time domain resources according to an embodiment of the application;

[0036] FIG. 4 is an example diagram of uplink available PRBs according to an embodiment of the application;

[0037] FIG. 5 is an example diagram of downlink available PRBs according to an embodiment of the application;

[0038] FIG. 6 is a schematic diagram of a CSI receiving method according to an embodiment of the application;

[0039] FIG. 7 is a schematic diagram of a CSI reporting apparatus according to an embodiment of the application;

[0040] FIG. 8 is a schematic diagram of a CSI receiving apparatus according to an embodiment of the present application;

[0041] FIG. 9 is a schematic diagram of a network device according to an embodiment of the present application;

[0042] FIG. 10 is a schematic diagram of a terminal device according to an embodiment of the present application. DETAILED DESCRIPTION

[0043] The foregoing and other features of the present application will become apparent to those skilled in the art upon consideration of the following description of specific embodiments of the present application, taken in conjunction with the accompanying drawings. In the description of embodiments of the application, specific terminology is employed for the sake of clarity. However, the application is not intended to be limited to the specific embodiments described, but rather, is intended to include all modifications, equivalents, and alternatives that fall within the scope of the appended claims.

[0044] In the embodiments of the present application, the terms "first", "second", and the like are used to distinguish different elements from one another, but do not indicate spatial arrangement or temporal order of the elements, and the elements should not be limited by these terms. The term "and / or" includes any one and all combinations of the associated listed terms. The terms "comprise", "include", "have", and the like, mean the presence of the stated feature, element, component, or assembly, but do not exclude the presence or addition of one or more other features, elements, components, or assemblies.

[0045] In the embodiments of the present application, the singular forms "a", "an", and "the" include plural referents unless the context clearly dictates otherwise. The term "the" should be construed to mean "at least one" or "one or more" unless the context clearly indicates otherwise. In addition, the term "based on" should be interpreted as "based, at least in part, on" and the term "based upon" should be interpreted as "based, at least in part, upon" unless the context clearly indicates otherwise.

[0046] In the embodiments of the present application, the term "communication network" or "wireless communication network" can refer to a network that complies with any communication standard, such as Long Term Evolution (LTE), LTE-Advanced (LTE-A), Wideband Code Division Multiple Access (WCDMA), High-Speed Packet Access (HSPA), and the like.

[0047] Also, communication between devices in a communication system can be in accordance with communication protocols of any stage, for example, can include but is not limited to the following communication protocols: 1G (generation), 2G, 2.5G, 2.75G, 3G, 4G, 4.5G, and future 5G, New Radio (NR), 6G, etc., and / or other currently known or to be developed communication protocols.

[0048] In embodiments of the present application, the term "network device" refers to, for example, a device that accesses a terminal device to a communication network and provides services for the terminal device in a communication system. The network device can include but is not limited to the following devices: base station (BS), access point (AP), transmission reception point (TRP), broadcast transmitter, mobile management entity (MME), gateway, server, radio network controller (RNC), base station controller (BSC), etc.

[0049] The base station can include but is not limited to: Node B (NodeB or NB), evolved Node B (eNodeB or eNB), and 5G base station (gNB), IAB donor, etc., and can also include remote radio head (RRH), remote radio unit (RRU), relay, or low-power node (such as femto, pico, etc.). Also, the term "base station" can include some or all functions thereof, and each base station can provide communication coverage for a specific geographic area. The term "cell" can refer to a base station and / or its coverage area, depending on the context in which the term is used.

[0050] In embodiments of the present application, the term "user equipment" (UE) refers to, for example, a device that accesses a communication network through a network device and receives network services, which can also be referred to as "terminal equipment" (TE). The terminal equipment can be fixed or mobile, and can also be referred to as a mobile station (MS), a terminal, a user, a subscriber station (SS), an access terminal (AT), a station, a mobile terminal (MT), etc.

[0051] The terminal device can include, but is not limited to, the following devices: cellular phone, personal digital assistant (PDA), wireless modem, wireless communication device, handheld device, machine type communication device, laptop computer, cordless phone, smartphone, smartwatch, digital camera, and the like.

[0052] For another example, in scenarios such as Internet of Things (IoT), the terminal device can also be a machine or apparatus that performs monitoring or measurement, for example, can include but is not limited to: machine type communication (MTC) terminal, vehicle-mounted communication terminal, device to device (D2D) terminal, machine to machine (M2M) terminal, and the like.

[0053] In addition, the term "network side" or "network device side" refers to the side of the network, which can be a certain base station, or can include one or more network devices as described above. The term "user side" or "terminal side" or "terminal device side" refers to the side of the user or terminal, which can be a certain UE, or can include one or more terminal devices as described above. In this article, "device" can refer to network device or terminal device without special indication.

[0054] In the following description, the terms "uplink control signal" and "uplink control information (UCI)" or "physical uplink control channel (PUCCH)" can be interchangeable without causing confusion, and the terms "uplink data signal" and "uplink data information" or "physical uplink shared channel (PUSCH)" can be interchangeable;

[0055] The terms "downlink control signal" and "downlink control information (DCI)" or "physical downlink control channel (PDCCH)" can be interchangeable.

[0056] In addition, the uplink signal can include an uplink data signal and / or an uplink control signal and / or a PRACH and / or an SRS, etc., and can also be referred to as an uplink transmission (UL transmission) or uplink information or an uplink channel. Transmitting / receiving the uplink transmission on the uplink resource can be understood as transmitting / receiving the uplink transmission using the uplink resource. The downlink signal can include a downlink data signal and / or a downlink control signal and / or a synchronization signal (SS, for example, PSS / SSS) and / or a broadcast channel (PBCH) and / or an SSB (SS / PBCH block, including PSS, SSS, and PBCH and its DMRS) and / or a CSI-RS, etc., and can also be referred to as a downlink transmission (DL transmission) or downlink information or a downlink channel. Transmitting / receiving the downlink transmission on the downlink resource can be understood as transmitting / receiving the downlink transmission using the downlink resource.

[0057] In the embodiments of the present application, the higher layer signaling can be, for example, radio resource control (RRC) signaling; the RRC signaling can include, for example, an RRC message, such as a broadcast / common RRC message / signaling (for example, a master information block (MIB), system information), a dedicated RRC message / signaling; or an RRC information element (RRC IE); or information fields included in the RRC message or the RRC information element (or information fields included in the information fields). The higher layer signaling can also be, for example, medium access control (MAC) signaling; or a MAC control element (MAC CE). However, the present application is not limited thereto. The names of the signaling (such as the RRC message, the information element, the information field, the higher layer parameter, etc.) used in the embodiments of the present application are only examples, and other names can also be used, and the embodiments of the present application are not limited thereto.

[0058] In the embodiments of the present application, multiple means at least two, or two or more.

[0059] In the embodiments of the present application, predefined means defined by a protocol or determined according to a rule defined by a protocol, without additional configuration. Configuration / indication means direct or indirect configuration / indication by a network device through higher layer signaling and / or physical layer signaling. The configuration / indication can be configured / indicated by introducing a higher layer parameter in the higher layer signaling, and the higher layer parameter means information fields and / or information elements / units / elements (IEs) in the higher layer signaling, etc. The physical layer signaling can be, for example, control information (DCI) carried by a physical downlink control channel or control information carried by a sequence, but is not limited thereto.

[0060] For ease of description, the following describes a base station as an example of an access network device. In the following description, “if”, “in the case of” and “when” can be used interchangeably without causing confusion. For resources in the frequency domain, “carrier” and “resource grid” can be interchangeable, “subcarrier spacing configuration (SCS) μ” and “subcarrier spacing (SCS) Δf” can be interchangeable. “Subcarrier spacing” and “numerology” can be interchangeable. “Resource block”, “RB” and “PRB”, “physical resource block”, “common resource block (CRB)” can be interchangeable. “Configure / indicate / provide / given” can be interchangeable. “Index” and “ID” can be interchangeable.

[0061] The following describes scenarios of embodiments of the present application by way of examples, but the present application is not limited thereto.

[0062] FIG. 1 is a schematic diagram of a communication system according to an embodiment of the present application, which schematically illustrates a case taking a terminal device and a network device as examples. As shown in FIG. 1, the communication system 100 can include a network device 101 and terminal devices 102 and 103. For simplicity, FIG. 1 illustrates only two terminal devices and one network device as examples, but embodiments of the present application are not limited thereto.

[0063] In embodiments of the present application, the network device 101 and the terminal devices 102 and 103 can perform existing services or future implementable services transmission. For example, these services can include, but are not limited to, enhanced mobile broadband (eMBB), massive machine type communication (mMTC) and ultra-reliable and low-latency communication (URLLC), etc.

[0064] Among them, the terminal device 102 can send data to the network device 101, for example, using a licensed or unlicensed transmission mode. The network device 101 can receive data sent by one or more terminal devices 102, and feed back information to the terminal device 102, such as acknowledgement (ACK) / non-acknowledgement (NACK) information, etc., so that the terminal device 102 can confirm the end of the transmission process, or can further perform new data transmission, or can perform data retransmission.

[0065] The network device 101 can transmit data to the terminal device 102 and / or the terminal device 103 in a unicast or multicast or broadcast manner. The terminal device 102 can receive data transmitted by one or more network devices (for example, dual connectivity or multi-connectivity) through a downlink or the terminal device 103 through a sidelink.

[0066] It is worth noting that FIG. 1 shows that both terminal devices 102 and 103 are within the coverage of the network device 101, but the present application is not limited thereto. Both terminal devices 102 and 103 can be outside the coverage of the network device 101, or one terminal device 102 is within the coverage of the network device 101 and the other terminal device 103 is outside the coverage of the network device 101.

[0067] In the following description, transmitting or receiving a PDCCH can be understood as transmitting or receiving downlink control information carried by the PDCCH.

[0068] In addition, the content in the brackets indicates that it is explanatory or exemplary or optional, for example, the expression or limitation in the brackets can be added in some embodiments, or the expression or limitation in the brackets can be ignored in other embodiments, " / " represents "and / or", and the present application is not limited thereto. The various embodiments of the embodiments of the present application will be described below in conjunction with the accompanying drawings. These embodiments are only exemplary and not limiting.

[0069] Embodiments of the first aspect

[0070] The embodiments of the present application provide a CSI reporting method, which is described from the side of the terminal device.

[0071] FIG. 2 is a schematic diagram of a CSI reporting method according to an embodiment of the present application. As shown in FIG. 2, the method comprises:

[0072] 201. The terminal device receives downlink control information (DCI) for activating a semi-persistent CSI triggering state;

[0073] 202. The terminal device performs semi-persistent CSI reporting on a PUSCH;

[0074] In the PUSCH, the PUSCH overlapping with the first time domain resource is not used for the semi-persistent CSI reporting (or the PUSCH overlapping with the first time domain resource is not transmitted), or the PUSCH overlapping with the second time domain resource is not used for the semi-persistent CSI reporting (or the PUSCH overlapping with the second time domain resource is not transmitted), or both the PUSCH overlapping with the first time domain resource and the PUSCH overlapping with the second time domain resource are used for the semi-persistent CSI reporting; in the first time domain resource, the first frequency domain resource is used for uplink and the second frequency domain resource is used for downlink, and the second time domain resource is outside the first time domain resource.

[0075] It is worth noting that the above Figure 2 only schematically illustrates the embodiments of the present application, but the present application is not limited thereto. For example, the execution order between the operations can be appropriately adjusted, and in addition, some operations can be added or some operations can be reduced. Those skilled in the art can make appropriate modifications based on the above description, and the present application is not limited to the description of the above Figure 2.

[0076] In some embodiments, the terminal device can be an SBFD-aware device; the present application is not limited thereto. For example, in the initial access procedure (from RRC_IDLE to RRC_Connected state, including CBRA) and / or in the random access procedure (such as CBRA) and / or in the RRCSetupComplete message and / or in the capability information, the terminal device indicates to the network device that the terminal device is an SBFD-aware device (SBFD-aware UE).

[0077] For example, in the random access procedure, the terminal device is indicated to be an SBFD-aware device through the RO for transmitting the preamble and / or the transmitted preamble and / or Msg3. For example, when some ROs and / or preambles are available only for SBFD-aware devices, thereby, when the UE uses these ROs and / or preambles, it can be known that the UE is an SBFD-aware device. For example, in the Msg3 and / or RRCSetupComplete message and / or capability information, information for indicating that the UE is an SBFD-aware device is included.

[0078] For example, the SBFD-aware UE has an ability related to SBFD operation, including one or more of the following: being able to obtain SBFD configuration, such as the following first time domain resource and / or second time domain resource and / or first frequency domain resource and / or second frequency domain resource configuration; being able to transmit and receive signals according to the SBFD configuration; being able to transmit uplink signals in (DL) SBFD symbols.

[0079] The time domain resource related to the embodiments of the present application is described below.

[0080] In some embodiments, for one cell or carrier, in the first time domain resource, different frequency domain resources are respectively (only) used for (receiving) uplink (e.g., corresponding to the first frequency domain resource described below) and (only) used for (transmitting) downlink (e.g., corresponding to the second frequency domain resource described below), for example, the network device can simultaneously receive (uplink signals) on the (only) uplink frequency domain resource and transmit (downlink signals) on the (only) downlink frequency domain resource; the second time domain resource is outside the first time domain resource, for example, in the second time domain resource, different frequency domain resources are used for uplink or downlink, that is, the frequency domain resources are not divided into (only) uplink and (only) downlink frequency domain resources, and the network device does not simultaneously receive and transmit.

[0081] In some embodiments, the first time domain resource includes, for example, SBFD slots and / or SBFD symbols, and the second time domain resource includes, for example, non-SBFD slots and / or non-SBFD symbols. Among them, the SBFD slot refers to a slot in which all symbols are SBFD symbols, and the non-SBFD slot refers to a slot in which all symbols are non-SBFD symbols. For ease of description, SBFD symbols and non-SBFD symbols are used for description below.

[0082] In some embodiments, the information for configuring SBFD symbols and / or non-SBFD symbols is provided by high layer signaling. For example, the high layer parameter for configuring SBFD symbols is optionally present in SIB1 and / or SIB Common Serving Cell Configuration (ServingCellConfigCommonSIB) IE and / or Common Serving Cell Configuration (ServingCellConfigCommon) IE (in Common TDD Uplink-Downlink Configuration (TDD-UL-DL-ConfigCommon) IE (in TDD Uplink-Downlink Pattern (TDD-UL-DL-Pattern) IE)), and / or the high layer parameter for configuring SBFD symbols is optionally present in Serving Cell Configuration (ServingCellConfig).

[0083] In some embodiments, one or more (e.g., two) TDD uplink-downlink patterns can be configured for a cell / carrier. When multiple patterns are configured, different patterns have or do not have corresponding SBFD symbols, and different patterns are independently configured with corresponding SBFD symbols.

[0084] For example, for each pattern with SBFD symbols, the SBFD symbols are consecutive in the period corresponding to the pattern. The above-mentioned higher layer parameter for configuring SBFD symbols, for example, includes one or more parameters for configuring SBFD symbols in the period, for example: a starting slot index, a starting symbol index (in the starting slot), an ending slot index, an ending symbol index (in the ending slot).

[0085] For example, the starting and ending slots are the first and last slots including SBFD symbols, respectively, and the starting and ending symbols are the first and last SBFD symbols in the starting and ending slots, respectively, and the SBFD symbols are from the starting symbol of the starting slot to the ending symbol of the ending slot. The slot index is the number of the slot included in the period, which is, for example, sequentially increased by 1 starting from 0 or 1. For example, when the starting slot index is 0, the starting slot is the first slot in the period, and when the starting slot index is 1, the starting slot is the second slot in the period, and so on. Similarly, the symbol index is the number of the symbol in the slot. Among them, the above-mentioned slot / symbol is configured with the SCS of the reference subcarrier spacing (reference SubcarrierSpacing) field of the common TDD uplink-downlink configuration (TDD-UL-DL-Config Common) IE.

[0086] For example, each / different pattern is independently configured with a period, for example, respectively configured by dl-UL-TransmissionPeriodicity in the corresponding (TDD-UL-DL-Pattern) IE. Among them, when only one pattern is configured, the period of the SBFD symbol is the same as the period corresponding to the pattern, and when multiple (for example, 2) patterns are configured, the period of the SBFD symbol is the same as the sum of the periods corresponding to all patterns.

[0087] In some embodiments, the downlink symbol is, for example, a symbol indicated as downlink (downlink) by the first uplink-downlink configuration, the uplink symbol is, for example, a symbol indicated as uplink (uplink) by the first uplink-downlink configuration, the flexible symbol (Flexible symbol) is, for example, a symbol neither indicated as downlink nor indicated as uplink by the first uplink-downlink configuration, or a symbol indicated as flexible by the configuration. Among them, the first uplink-downlink configuration is used to provide a cell-specific uplink-downlink configuration, for example, tdd-UL-DL-ConfigurationCommon or common TDD uplink-downlink configuration (TDD-UL-DL-Config Common) IE or (TDD-UL-DL-Pattern) IE, not limited thereto.

[0088] In some embodiments, the UE determines the DL / UL / Flexible symbols corresponding to the BWP according to the DL / UL / Flexible symbols configured based on the referenceSubcarrierSpacing (and assuming NCP). For example, it determines the DL / UL / Flexible symbols corresponding to the BWP according to the referenceSubcarrierSpacing and the SCS and / or CP type (NCP or ECP) of the BWP.

[0089] In some embodiments, the DL / UL / Flexible symbols refer to the DL / UL / Flexible symbols configured based on the referenceSubcarrierSpacing or the DL / UL / Flexible symbols corresponding to the BWP.

[0090] In some embodiments, the UE determines the SBFD / non-SBFD symbols corresponding to the BWP according to the SBFD / non-SBFD symbols configured based on the referenceSubcarrierSpacing (and assuming NCP). For example, it determines the SBFD / non-SBFD symbols corresponding to the BWP according to the referenceSubcarrierSpacing and the SCS and / or CP type (NCP or ECP) of the BWP.

[0091] In some embodiments, the SBFD / non-SBFD symbols refer to the SBFD / non-SBFD symbols configured based on the referenceSubcarrierSpacing or the SBFD / non-SBFD symbols corresponding to the BWP.

[0092] In some embodiments, the UE does not expect the CP type of the BWP to be ECP.

[0093] In some embodiments, the UE does not expect the SBFD symbols configured by the above-mentioned higher layer parameter to overlap with the uplink symbols, or if the SBFD symbols configured by the above-mentioned higher layer parameter overlap with the uplink symbols, the UE considers the SBFD symbols overlapping with the uplink symbols to be non-SBFD symbols in practice.

[0094] In some embodiments, the SBFD symbols overlap with the downlink symbols or the flexible symbols, or in other words, the SBFD symbols are configured within the range of the downlink symbols and / or the flexible symbols.

[0095] In some embodiments, the SBFD symbol includes a DL SBFD symbol and / or a Flexible SBFD symbol, and the non-SBFD symbol includes a Full-DL symbol and / or a Full-Flexible symbol and / or a Full-UL symbol (or UL symbol), and the symbols can also be represented in other ways, which are not limited thereto.

[0096] FIG. 3 is an example diagram of time domain resources according to embodiments of the present disclosure. As shown in FIG. 3, a period can include a plurality of different symbols. Among them, the SBFD symbol is within the range of downlink symbols and flexible symbols, the SBFD symbol overlapping with the downlink symbol is denoted as a DL SBFD symbol, the SBFD symbol overlapping with the flexible symbol is denoted as a Flexible SBFD symbol, the downlink symbol not overlapping with the SBFD symbol is denoted as a Full-DL symbol, the flexible symbol not overlapping with the SBFD symbol is denoted as a Full-Flexible symbol, and the UL symbol not overlapping with the SBFD symbol is denoted as a Full-UL symbol (assuming that the UL symbol cannot be used as the SBFD symbol, and the Full-UL symbol is equivalent to the UL symbol). FIG. 3 exemplarily illustrates the time domain resources according to embodiments of the present disclosure, but is not limited thereto.

[0097] The frequency domain resources according to embodiments of the present disclosure are further exemplarily described below.

[0098] For a cell and / or a carrier, in the first time domain resource, the first frequency domain resource is (only) used for uplink and the second frequency domain resource is (only) used for downlink, that is, the frequency domain resources are divided into the first frequency domain resource (only) used for uplink and the second frequency domain resource (only) used for downlink. The second time domain resource is outside the first time domain resource, that is, in the second time domain resource, the frequency domain resources are not divided as described above.

[0099] For example, the first frequency domain resource includes an uplink subband (UL subband) and / or uplink available PRBs, and the second frequency domain resource includes a downlink subband (DL subband) and / or downlink available PRBs, and other names can also be used, which are not limited thereto.

[0100] In some embodiments, the UE receives information for configuring the UL subband and the DL subband. For example, the uplink subband and the downlink subband respectively include an integer number of PRBs, and the information for configuring the UL subband and the DL subband respectively includes information for indicating the corresponding starting PRB and bandwidth.

[0101] In some embodiments, the information for configuring the UL subband and the DL subband is provided by high layer signaling.

[0102] For example, the higher layer parameters for configuring DL subband are optionally present in SIB1 (in SIB Common Serving Cell Configuration (ServingCellConfigCommonSIB) IE (in SIB Common Downlink Configuration (DownlinkConfigCommonSIB) IE (in SIB Downlink Frequency Info (FrequencyInfoDL-SIB) IE (in SCS-Specific Carrier (SCS-SpecificCarrier) IE))), the inclusion relationship of the above parameters can be represented as: SIB1>ServingCellConfigCommonSIB>DownlinkConfigCommonSIB>FrequencyInfoDL-SIB>SCS-SpecificCarrier; and / or,

[0103] The higher layer parameters for configuring DL subband are optionally present in Common Serving Cell Configuration (ServingCellConfigCommon) IE (in Common Downlink Configuration (DownlinkConfigCommon) IE (in Downlink Frequency Info (FrequencyInfoDL) IE (in SCS-Specific Carrier (SCS-SpecificCarrier) IE))), the inclusion relationship of the above parameters can be represented as: ServingCellConfigCommon>DownlinkConfigCommon>FrequencyInfoDL>SCS-SpecificCarrier, and / or, optionally present in Serving Cell Configuration (ServingCellConfig). That is, the higher layer parameters for configuring DL subband can be optionally present in one or more of the above parameters.

[0104] For example, the high layer parameters for configuring UL subband are optionally present in SIB1 (in SIB Common Serving Cell Config (ServingCellConfigCommonSIB) IE (in SIB Common Uplink Config (UplinkConfigCommonSIB) IE (in SIB Uplink Frequency Info (FrequencyInfoUL-SIB) IE (in SCS-SpecificCarrier IE))), and the inclusion relationship of the above parameters can be represented as: SIB1 > ServingCellConfigCommonSIB > UplinkConfigCommonSIB > FrequencyInfoUL-SIB > SCS-SpecificCarrier, and / or,

[0105] The high layer parameters for configuring UL subband are optionally present in Common Serving Cell Config (ServingCellConfigCommon) IE (in Common Uplink Config (UplinkConfigCommon) IE (in Uplink Frequency Info (FrequencyInfoUL) IE (in SCS-SpecificCarrier IE))), and the inclusion relationship of the above parameters can be represented as: ServingCellConfigCommon > UplinkConfigCommon > FrequencyInfoUL > SCS-SpecificCarrier, and / or, optionally present in Serving Cell Config (ServingCellConfig). That is, the high layer parameters for configuring UL subband can optionally be present in one or more of the above parameters.

[0106] In some embodiments, the high layer parameters for configuring UL subband and the high layer parameters for configuring DL subband include one or more parameters for providing resource indication value (RIV) and / or SCS (corresponding to UL / DL subband), that is, respectively indicating the starting RB (RB start ) and bandwidth (including the number of RBs, L RBs ) of UL subband and DL subband based on RIV.

[0107] For example, the resource indication value can be defined as in Table 1 below.

[0108] Table 1

[0109] For example, for DL / UL subband: assuming the following in Table 1 In addition, the first PRB ( The minimum value (0 or 1) corresponding to the PRB can be determined as follows: The first PRB is the PRB determined by the corresponding subcarrierSpacing and offsetToCarrier in ServingCellConfig Common / ServingCellConfig CommonSIB (configured in the corresponding SCS-Specific Carrier in FrequencyInfoDL (for DL ​​subband) / RequencyInfoUL (for UL subband) / Fequency InfoUL-SIB (for UL subband) / HequencyInfoDL-SIB (for DL ​​subband)).

[0110] In some embodiments, within a cell, the scs-SpecificCarrierList of UL and DL may each include one or more SCS-SpecificCarrier IEs, and each SCS-SpecificCarrier IE corresponds to / includes one SCS configuration (subcarrierSpacing). That is, the scs-SpecificCarrierList of UL and DL may each include one or more SCS configurations.

[0111] For example, each SCS configuration in the UL scs-SpecificCarrierList is configured with one UL subband, or in other words, each corresponds to one UL subband, for example, each corresponds to the independent high-level parameters mentioned above for configuring the UL subband. Each SCS configuration in the DL scs-SpecificCarrierList is configured with one or more (e.g., two) DL subbands, or in other words, each corresponds to one or more DL subbands, for example, each corresponds to the independent high-level parameters mentioned above for configuring the DL subband. If an SCS configuration is configured with multiple DL subbands, then the corresponding high-level parameters for configuring the DL subbands include multiple RIVs mentioned above.

[0112] In some embodiments, the UE does not expect the DL subband and UL subband (in the frequency domain) to overlap.

[0113] In some embodiments, the uplink usable PRBs include PRBs in the intersection between (PRBs in) the (activated) UL BWP and (PRBs in) the (corresponding) UL subband. For example, for one UL BWP, the intersection is determined according to the uplink subband corresponding to the SCS of the UL BWP. For example, if the SCS of one UL BWP is 15 kHz, then the corresponding UL usable PRBs are the intersection between the UL BWP and the uplink subband corresponding to SCS = 15 kHz. If the SCS of one UL BWP is 30 kHz, then the corresponding UL usable PRBs are the intersection between the UL BWP and the uplink subband corresponding to SCS = 15 kHz.

[0114] Figure 4 is an example diagram of uplink usable PRBs according to embodiments of the present application. As shown in Figure 4, the UL BWP and the UL subband overlap, and the UL usable PRBs are the intersection between the two. The UL subband therein may, for example, represent the uplink subband corresponding to the SCS of the UL BWP, but the present application is not limited thereto.

[0115] In some embodiments, the downlink usable PRBs include PRBs in the intersection between the (activated) DL BWP and the (corresponding) DL subband. For example, for one DL BWP, the intersection is determined according to the downlink subband corresponding to the SCS of the DL BWP. For example, if the SCS of one DL BWP is 15 kHz, then the corresponding DL usable PRBs are the intersection between the DL BWP and the downlink subband corresponding to SCS = 15 kHz. If the SCS of one DL BWP is 30 kHz, then the corresponding DL usable PRBs are the intersection between the DL BWP and the uplink subband corresponding to SCS = 15 kHz.

[0116] Figure 5 is an example diagram of downlink usable PRBs according to embodiments of the present application. As shown in Figure 5, the DL BWP and the DL subband overlap, and the DL usable PRBs are the intersection between the two. The DL subband therein may, for example, represent the downlink subband corresponding to the SCS of the DL BWP, but the present application is not limited thereto.

[0117] The above describes the time-frequency resources in a schematic manner. The following describes embodiments of the present application in a schematic manner.

[0118] In embodiments of the present application, for PUSCH, one (of the N*K slots) (of the allocated symbols) in one (for Type B: nominal / actual) repetition or multiple (N*K) slots can also be referred to as / correspond to one PUSCH transmission (opportunity).

[0119] In the embodiments of the present application, the overlapping with the first time domain resource includes partial overlapping (i.e., part of the overlapping is within the first time domain resource, and another part is within the second time domain resource) and / or complete overlapping (at this time, it can also be said that the overlapping is within the first time domain resource). The overlapping with the second time domain resource includes partial overlapping (i.e., part of the overlapping is within the second time domain resource, and another part is within the first time domain resource) and / or complete overlapping (at this time, it can also be said that the overlapping is within the second time domain resource).

[0120] In some embodiments, the overlapping with the first time domain resource and the overlapping with the second time domain resource do not include the above-mentioned partial overlapping at the same time, for example, if the overlapping with the first time domain resource includes partial overlapping, the overlapping with the second time domain resource does not include partial overlapping, and vice versa; the present application is not limited to this.

[0121] In some embodiments, downlink control information (DCI) can be used to activate a semi-persistent CSI triggering state.

[0122] For example, for semi-persistent reporting of PUSCH, a set of triggering states is configured by CSI-SemiPersistentOnPUSCH-TriggerStateList, and the CSI request field in the DCI scrambled by the SP-CSI-RNTI can activate one triggering state.

[0123] In some embodiments, (the reporting setting CSI-ReportConfig does not contain a sub-configuration list provided by the high-layer parameter CSI-ReportSubConfigToAddModList), one triggering state indicates / associates one or more reporting configurations CSI-ReportConfig.

[0124] In some embodiments, the reporting setting CSI-ReportConfig can contain a sub-configuration list provided by the high-layer parameter CSI-ReportSubConfigToAddModList, and each of one or more triggering states can be configured to indicate one or more sub-configurations.

[0125] For another example, when successfully decoding the DCI format 0_1 or DCI format 0_2 that activates the semi-persistent CSI triggering state (SP-CSI triggering state), the terminal device performs semi-persistent CSI reporting on the PUSCH. The DCI format 0_1 and the DCI format 0_2 contain a CSI request field, which indicates to activate or deactivate the semi-persistent CSI triggering state.

[0126] For example, the codepoint of the CSI request field in DCI is mapped to the SP-CSI trigger state according to the order of the position of the trigger state configured in CSI-SemiPersistentOnPUSCH-TriggerStateList, e.g. codepoint “0” is mapped to the trigger state in the first position.

[0127] In some embodiments, the PUSCH does not carry uplink data (TB).

[0128] For example, the PUSCH has no transport block (TB) and has a CSI report. When the terminal device is scheduled to transmit the PUSCH without transport block and with the CSI report carried by the CSI request field of the DCI, the value m of the “time domain resource allocation” field of the DCI provides the row index m+1 (in the pre-defined allocation table). The index row defines the start and length indicator SLIV, or directly defines the start symbol S and the allocation length L, as well as the PUSCH mapping type and K2 value applied in the PUSCH transmission, where Y j is the corresponding list entry of the higher layer parameter.

[0129] In some embodiments, the trigger state associated CSI report configuration associated CSI-RS is restricted in the first time domain resource or the second time domain resource.

[0130] In some embodiments, the CSI report configuration includes information indicating that the associated CSI-RS is restricted in the first time domain resource or the second time domain resource, and / or, the CSI resource configuration corresponding to the CSI-RS includes information indicating that the CSI-RS is restricted in the first time domain resource or the second time domain resource.

[0131] For example, the CSI report configuration can refer to Table 2, and the periodicity can refer to Table 3:

[0132] Table 2

[0133] Table 3

[0134] The following is described for SP-CSI report on PUSCH, for example, including SP-CSI report on PUSCH in case of repetition type A, SP-CSI report on PUSCH in case of repetition type B.

[0135] In embodiments of the present application, one or more semi-persistent CSI (SP-CSI) configurations can be provided to a terminal device, each of which can independently provide time-frequency domain resource allocation to semi-persistently schedule a PUSCH, and the present application is not limited thereto.

[0136] In some embodiments, the SP-CSI is activated by a DCI or is provided with an UL assignment by an activating DCI. The activating DCI is, for example, a DCI format 0_1 / 0_2 / 0_3, but the present application is not limited thereto.

[0137] In some embodiments, the PUSCH corresponds to one SLIV, one mapping type, and one slot offset.

[0138] In some embodiments, the PUSCH has repetition.

[0139] In some embodiments, the repetition includes a first repetition type and / or a second repetition type. The first repetition type is, for example, a PUSCH repetition type A, and the second repetition type is, for example, a PUSCH repetition type B, but the present application is not limited thereto.

[0140] In some embodiments, PUSCHs scheduled by different DCI formats correspond to independent repetition type configurations, and the corresponding repetition types can be determined accordingly. For example, for a PUSCH scheduled by a DCI format 0_1 or a DCI format 0_2, if a higher layer parameter pusch-RepTypeIndicatorDCI-0-1 (corresponding to the DCI format 0_1) or pusch-RepTypeIndicatorDCI-0-2 (corresponding to the DCI format 0_2) is set to 'pusch-RepTypeB', the UE applies a PUSCH repetition type B procedure, otherwise the UE applies a PUSCH repetition type A procedure. The above-mentioned higher layer parameter is, for example, present in a PUSCH-Config IE, but the present application is not limited thereto.

[0141] In some embodiments, the frequency domain resources indicated by (the FDRA field in) the DCI include PRBs indicated / allocated by the FDRA field in the DCI, e.g., these PRBs can be referred to as assigned / allocated PRBs. The frequency domain resources indicated by (the FDRA field in) the DCI within the first frequency domain resources include / are determined as the intersection (of PRBs) between the frequency domain resources indicated by (the FDRA field in) the DCI and the first frequency domain resources, e.g., these PRBs can be referred to as assigned / allocated PRBs within UL usable PRBs (or UL subband). Where the first frequency domain resources refer to UL subband, the UL subband corresponding to the SCS of the PUSCH scheduled by the DCI shall be used, e.g., the SCS of the PUSCH is / equals the SCS of the UL BWP where the PUSCH is located, but not limited thereto.

[0142] In some embodiments, for PUSCH, the resource allocation type includes a first resource allocation type (resource allocation type 0) or a second resource allocation type (resource allocation type 1).

[0143] For example, in resource allocation type 0, the FDRA field (or referred to as resource block assignment information) in the DCI includes a bitmap indicating RBGs, the bitmap is of size N RBG bits with one bitmap bit per RBG such that each RBG is addressable. The RBGs shall be indexed in the order of increasing frequency of the bandwidth part and starting at the lowest frequency. The order of RBG bitmap is such that RBG 0 to RBG N RBG-1are mapped from MSB to LSB of the bitmap. The RBG is allocated to the UE if the corresponding bit value in the bitmap is 1, the RBG is not allocated to the UE otherwise. wherein, N RBG is the number of RBGs in the UL BWP.

[0144] For example, in resource allocation type 1, the FDRA field (or referred to as resource block assignment information) in DCI includes a resource indication value (RIV) indicating a set of contiguously allocated non-interleaved virtual resource blocks within the active bandwidth part. For example, the RIV corresponds to a starting virtual resource block (RB start ) and a length in terms of contiguously allocated resource blocks L RBs , wherein the definition of RIV is as previously described, for PUSCH scheduling, is the number of PRBs in the (active) UL BWP.

[0145] For another example, for PUSCH scheduled by DCI format 0_2, the RIV corresponds to a starting resource block group RBG start = 0, 1, …, N RBG -1and a length in terms of virtually contiguously allocated resource block groups L RBGs = 1, …, N RBG , wherein the definition of RIV is as follows:

[0146] Table 4

[0147] wherein, for RIV and the bitmap above, NRBG have the same or different values. For example, for RIV and the above bitmap, the parameter P is determined by the same higher layer parameter. For example, for DCI format 0_2 and 0_3, the parameter P is determined by different higher layer parameters. RBG For example, for DCI format 0_2 and 0_3, the parameter P is determined by different higher layer parameters. RBG For example, for DCI format 0_2 and 0_3, the parameter P is determined by different higher layer parameters.

[0148] In some embodiments, the (TDRA field of the) activation DCI indicates a row from the (time domain) resource allocation table, which corresponds to one SLIV or directly the start symbol S and the allocation length L (corresponding to symbol allocation), one (PUSCH) mapping type, one slot offset K2. The time domain resources indicated by the activation DCI for example include the allocated symbols in the slot (e.g., referred to as the first slot) determined by the slot offset K2.

[0149] In some embodiments, the slot determined by the slot offset K2 for example includes the slot

[0150] (where K offset is a parameter configured by higher layer,and where is the subcarrier spacing configuration for K offset with a value of 0 for frequency range 1and for FR2-NTN,n is the slot with the scheduling DCI,K2 is based on the numerology of PUSCH,and μ PUSCH and μ PDCCH are the subcarrier spacing configurations for PUSCH and PDCCH,respectively)。

[0151] In some embodiments, the first PUSCH is for example the PUSCH in the slot determined by the slot offset K2. The first PUSCH can also be referred to as the PUSCH scheduled by the corresponding activation DCI or the (first) PUSCH associated with the corresponding activation DCI.

[0152] In some embodiments, for SP-CSI, after UL assignment is configured / provided, the UE determines the (first) slot where PUSCH is located according to the periodicity provided in the SP-CSI configuration (in one period).

[0153] For example, Table 5 shows one example:

[0154] Table 5

[0155] In some embodiments, in one period, PUSCH is only in one slot (PUSCH without repetition).

[0156] In some embodiments, (in one period, ) PUSCH is repeated (PUSCH with repetition) in multiple consecutive slots (starting from the above-mentioned first slot), the same symbol allocation / SLIV is applied to the multiple slots, different repetitions (or referred to as transmission opportunities) correspond, for example, to different redundancy versions, but not limited to this. The number of repetitions or the number of slots included in the above-mentioned multiple slots is determined by pusch-AggregationFactor (in SP-CSI configuration or in PUSCH configuration) or repetitionNumber (corresponding to the row indicated by the TDRA field of the activating DCI).

[0157] For example, for PUSCH activated by DCI format 0_1 or DCI format 0_2 (or the PUSCH scheduled by the activating DCI), if pusch-AggregationFactor is included in the SP-CSI configuration, the number is determined by pusch-AggregationFactor in the SP-CSI configuration, otherwise, it is determined by pusch-Aggregation Factor in the PUSCH configuration (pusch-config) (for example, equal to the number of pusch-AggregationFactor configuration).

[0158] In some embodiments, in the case of repetition (PUSCH with repetition), (in one period, ) PUSCH includes multiple repetitions, i.e. repetitions in different slots in multiple slots are considered as one PUSCH.

[0159] In some embodiments, in the case of repetition (PUSCH with repetition), (in one period, one PUSCH includes one repetition, i.e. repetitions in different slots in multiple slots are respectively considered as one PUSCH.

[0160] In some embodiments, one repetition can also be referred to / correspond to one PUSCH transmission (occasion) for PUSCH.

[0161] In some embodiments, repetition and PUSCH can be interchangeable. For example, PUSCH can be replaced by repetition “repetition”, and accordingly, the case applicable to repetition is explained.

[0162] In some embodiments, the allocated frequency domain resources include the PRBs indicated / allocated by the FDRA field in the activation DCI, which can be referred to as assigned / allocated PRBs for short. The frequency domain resources allocated within the first frequency domain resources include / are determined as the intersection (of PRBs) between the above-mentioned allocated frequency domain resources and the first frequency domain resources, which can be referred to as assigned / allocated PRBs within UL usable PRBs (or UL subband) for short. Wherein, when the first frequency domain resources refer to UL subband, the UL subband corresponding to the SCS of the scheduled PUSCH is used, and the SCS of the PUSCH is, for example, equal to / equal to the SCS of the UL BWP where the PUSCH is located, but not limited thereto.

[0163] In the embodiments of the present application, for the PUSCH corresponding to one (one / a) SP-CSI configuration in at least one SP-CSI configuration (or for one SP-CSI configuration): the PUSCH / repetition overlapping with the first time domain resource is not transmitted (dropped), or the PUSCH / repetition overlapping with the second time domain resource is not transmitted, or for the PUSCH / repetition overlapping with the first time domain resource, the frequency domain resources (PRBs) within the (only) first frequency domain resources allocated are valid (the frequency domain resources outside the allocated first frequency domain resources are invalid).

[0164] In this way, the PUSCH / repetition selected by the terminal device does not exist PUSCH / repetition overlapping with the invalid time domain resource type, which can avoid selecting PUSCH / repetition overlapping with the invalid time domain resource type, and for the PUSCH overlapping with the SBFD symbol, the frequency domain resources used for downlink can be avoided, thereby improving the data transmission rate.

[0165] In some embodiments, for the PUSCH corresponding to one (one / a) SP-CSI configuration in at least one SP-CSI configuration (or for one SP-CSI configuration):

[0166] When SBFD symbols are invalid time domain resource type (or, when (only) non-SBFD symbols are valid time domain resource type), PUSCH (for PUSCH without repetition or with repetition) / repetition (for PUSCH with repetition) overlapping with SBFD symbols is not transmitted (dropped); and / or,

[0167] When non-SBFD symbols are invalid time domain resource type (or, when (only) SBFD symbols are valid time domain resource type), PUSCH (for PUSCH without repetition or with repetition) / repetition (for PUSCH with repetition) overlapping with non-SBFD symbols is not transmitted; and / or,

[0168] When SBFD symbols are not invalid time domain resource type, for PUSCH (for PUSCH without repetition or with repetition) / repetition (for PUSCH with repetition) overlapping with SBFD symbols, frequency domain resources within (only) non-SBFD symbols are valid.

[0169] For example, for the first resource allocation type, when case 1-1 and one allocated RBG overlaps with subband boundary, only PRBs within UL usable PRBs are considered valid for PUSCH transmission. UE is not expected to be allocated RBG for PDSCH outside of DL usable PRBs, or RBG for PUSCH outside of UL usable PRBs.

[0170] For example, for the second resource allocation type, when valid symbol type is SBFD symbol, only PRBs within allocated UL usable PRBs are considered valid for PUSCH. PRBs outside of allocated UL usable PRBs are considered invalid and not used for PUSCH resource mapping.

[0171] In some embodiments, each PUSCH / (for Reptition Type B: nominal / actual) repetition is within SBFD symbols or non-SBFD symbols, respectively, or has full SBFD symbols or full non-SBFD symbols, respectively, e.g., the UE does not expect any of the (DCI scheduled) PUSCH / (for Reptition Type B: nominal / actual) repetitions to overlap with both SBFD symbols and non-SBFD symbols. Or, the first PUSCH / first (for Reptition Type B: nominal / actual) repetition / reference PUSCH / third reference (for Reptition Type B: nominal / actual) repetition / fourth reference (for Reptition Type B: nominal / actual) repetition is within SBFD symbols or non-SBFD symbols, or has full SBFD symbols or full non-SBFD symbols, e.g., the UE does not expect the first PUSCH / first (for Reptition Type B: nominal / actual) repetition / reference PUSCH / third reference (for Reptition Type B: nominal / actual) repetition / fourth reference (for Reptition Type B: nominal / actual) repetition to overlap with both SBFD symbols and non-SBFD symbols.

[0172] In some embodiments, the time-domain resource type, e.g., includes slot type and / or symbol type, e.g., divides the time-domain resources into 2 types, the SBFD symbols and non-SBFD symbols.

[0173] - case 1: with invalid time-domain resource type, e.g., one of the SBFD symbols and non-SBFD symbols is invalid, and the other is valid.

[0174] - case 1-1: the SBFD symbols are the invalid time-domain resource type, or the invalid time-domain resource type is SBFD symbols (e.g., the invalid symbol type is SBFD symbols, or SBFD symbols are invalid), and the non-SBFD symbols are the valid time-domain resource type, or the valid time-domain resource type is non-SBFD symbols (e.g., the valid symbol type is non-SBFD symbols, or non-SBFD symbols are valid).

[0175] --case 1-2: the valid symbol type is SBFD symbols, or SBFD symbols are valid, the invalid symbol type is non-SBFD symbols, or non-SBFD symbols are invalid.

[0176] --case 2: no invalid symbol type, e.g. both SBFD symbols and non-SBFD symbols are valid.

[0177] In some embodiments, for PUSCH, corresponding to case 1, it can also be said that PUSCH transmission is limited to SBFD symbols (when SBFD symbols are valid, non-SBFD symbols are invalid, case 1-2) or limited to non-SBFD symbols (when non-SBFD symbols are valid, SBFD symbols are invalid, case 1-1). For PUSCH with repetition, only the repetition(s) overlapping with SBFD symbols (for repetition Type B: actual) are transmitted or only the repetition(s) overlapping with non-SBFD symbols (for repetition Type B: actual) are transmitted.

[0178] In some embodiments, for PUSCH, corresponding to case 2, it can also be said that PUSCH transmission can be across SBFD symbols and non-SBFD symbols. For PUSCH in multiple PUSCHs, both PUSCHs overlapping with SBFD symbols or non-SBFD symbols can be received. For PUSCH with repetition, both the repetition(s) overlapping with SBFD symbols or non-SBFD symbols (for repetition Type B: actual) can be transmitted.

[0179] The following further describes how to configure and determine the invalid symbol type and / or the valid symbol type.

[0180] In some embodiments, the invalid symbol type and / or the valid symbol type is determined based on the first information and / or the second information and / or the time domain resource indicated by the first reference PUSCH (e.g. the first PUSCH scheduled by the DCI) and / or the corresponding activation DCI (in the TDRA field).

[0181] For example, the first information is used to determine which one of case 1 and case 2 corresponds. For example, the first information is used to indicate that there is no invalid time domain resource type (i.e., case 2) and / or to indicate that there is invalid time domain resource type (i.e., case 1).

[0182] For example, (when the first information is only used to indicate case 2, or the first information is used to indicate case 1 is also used to indicate case 2,) if the first information indicates Case 2, or, (when the first information is only used to indicate case 1,) if the first information is not provided, or, (when the first information is only used to indicate case 2,) if the first information is provided: it is case 2.

[0183] For example, (when the first information is only used to indicate case 1, or the first information is used to indicate case 1 is also used to indicate case 2,) if the first information indicates Case 1, or, (when the first information is only used to indicate case 2,) if the first information is not provided, or, (when the first information is only used to indicate case 1,) if the first information is provided: it is case 1.

[0184] The UE determines whether it is Case 1-1 or Case 1-2 according to the second information and / or the second reference repetition and / or the allocated symbols in the second slot. The second information is included in the DCI, for example, but not limited thereto.

[0185] For example, the first reference PUSCH is the first PUSCH scheduled by the DCI or the first PUSCH meeting the first condition, and / or, the second reference repetition is the first repetition scheduled by the DCI or the first repetition meeting the first condition, and / or, the second slot is the slot corresponding to the first PUSCH or the first repetition or the reference PUSCH or the second reference repetition or the slot determined by the slot offset indicated by the DCI. Wherein, for the PUSCH with the second type of repetition: the repetition includes nominal repetition and / or actual repetition.

[0186] For example, the first condition includes but is not limited to: not overlapping with non-SBFD symbols indicated as downlink, and / or, not overlapping with SSB, and / or, not overlapping with both SBFD symbols and non-SBFD symbols. The downlink can be indicated by the first uplink-downlink configuration and / or the second uplink-downlink configuration.

[0187] For example, the second uplink-downlink configuration is used to provide a UE-specific / dedicated uplink-downlink configuration, e.g., tdd-UL-DL-ConfigurationDedicated, without limitation. For example, the third uplink-downlink configuration is dedicated to indicate the uplink-downlink of SBFD symbols, which is different from the first / second uplink-downlink configuration.

[0188] In some embodiments, the second reference repetition is the same as the first reference repetition, e.g., the first condition is the same (thus, corresponding to the same repetition) for the first reference repetition and the second reference repetition. In other embodiments, the first reference repetition is different from the second reference repetition, e.g., the first conditions corresponding to the two are different (thus, possibly corresponding to the same or different repetition).

[0189] For example, the first condition is that neither overlaps with non-SBFD symbols indicated as downlink for the first reference repetition and the second reference repetition. For another example, the first condition is that neither overlaps with SBFD symbols nor non-SBFD symbols for the first reference repetition and the second reference repetition.

[0190] For another example, the first condition is that neither overlaps with non-SBFD symbols indicated as downlink for the first reference repetition; and the first condition is that neither overlaps with SBFD symbols nor non-SBFD symbols for the second reference repetition. For yet another example, the first condition is that neither overlaps with SBFD symbols nor non-SBFD symbols for the first reference repetition; and the first condition is that neither overlaps with non-SBFD symbols indicated as downlink for the second reference repetition.

[0191] In some embodiments, the first time slot and the second time slot are the same. In other embodiments, the first time slot and the second time slot are different.

[0192] In some embodiments, the first information is used to indicate that there is no invalid time domain resource type and / or is used to indicate that there is an invalid time domain resource type (e.g., at least one of the first time domain resource and the second time domain resource is an invalid time domain resource type);

[0193] The first information is (optionally) present outside of the SP-CSI configuration (e.g., included in PUSCH-Config or PUSCH-ConfigCommon), and the first information applies to all or part of the SP-CSI configuration, or the first information is (optionally) present in the SP-CSI configuration, and the first information applies to the SP-CSI configuration in which the first information is present.

[0194] In some embodiments, the first information is also applied to other PUSCH scheduling (e.g., DCI scheduling multiple PUSCHs and / or DCI scheduling PUSCH repetition).

[0195] In some embodiments, the second information is used to indicate an invalid time domain resource type and / or a valid time domain resource type (e.g., the second information is used to indicate that the first time domain resource is an invalid time domain resource type and / or used to indicate that the second time domain resource is an invalid time domain resource type, or, the second information is used to indicate that the first time domain resource is a valid time domain resource type and / or used to indicate that the second time domain resource is a valid time domain resource type); the second information (optionally) exists in a SP-CSI configuration, and the second information is applied to the SP-CSI configuration where the second information exists.

[0196] In some embodiments, the invalid time domain resource type and / or the valid time domain resource type is determined based on a first reference PUSCH, including:

[0197] The valid time domain resource type is a time domain resource type of the first reference PUSCH;

[0198] wherein, if the first reference PUSCH overlaps with only the first time domain resource, the valid time domain resource type is the first time domain resource, if the first reference PUSCH overlaps with only the second time domain resource, the valid time domain resource type is the second time domain resource, or, the terminal device does not expect the first reference PUSCH to overlap with both the first time domain resource and the second time domain resource.

[0199] In some embodiments, in the case of repetition, the terminal device expects all repetitions of the first reference PUSCH to overlap with only the first time domain resource or to overlap with only the second time domain resource, or, the valid time domain resource type or the time domain resource type of the first reference PUSCH is a time domain resource type of a first reference repetition of the first reference PUSCH.

[0200] In some embodiments, the invalid time domain resource type and / or the valid time domain resource type is determined based on a time domain resource indicated by an activation DCI, including:

[0201] if the time domain resource indicated by the activation DCI overlaps with only the first time domain resource, the valid time domain resource type is the first time domain resource, and / or, the invalid time domain resource type is the second time domain resource;

[0202] if the time domain resource indicated by the activation DCI overlaps with only the second time domain resource, the valid time domain resource type is the second time domain resource, and / or, the invalid time domain resource type is the first time domain resource.

[0203] In some embodiments, when the first information (only) indicates that there is no invalid time-domain resource type:

[0204] The first information and the second information do not exist at the same time (when the first information exists, the second information does not exist, and vice versa); or,

[0205] When the first information and the second information exist at the same time, the first information is not applied to the SP-CSI configuration including the second information, and / or, is applied to the SP-CSI configuration not including the second information.

[0206] In some embodiments, when the terminal device is not provided with the first information or when the first information indicates that there is an invalid time-domain resource type, the second information is (must) included in the SP-CSI configuration; or,

[0207] For the SP-CSI configuration not including the second information:

[0208] The terminal device determines the invalid time-domain resource type and / or the valid time-domain resource type based on the first reference PUSCH or the time-domain resource indicated by the activation DCI, or the terminal device considers that the first time-domain resource or the second time-domain resource is the invalid time-domain resource type.

[0209] In some embodiments, for the PUSCH with the first type of repetition, or the PUSCH with the second type of repetition, without being configured with available slot counting (or without being enabled with available slot counting):

[0210] When the SBFD symbol is the invalid time-domain resource type, the PUSCH or (for repetition Type B: nominal / actual) repetition overlapping with the SBFD symbol is not transmitted (dropped), and when the non-SBFD symbol is the invalid time-domain resource type, the PUSCH or (for repetition Type B: nominal / actual) repetition overlapping with the non-SBFD symbol is not transmitted (dropped).

[0211] In some embodiments, for PUSCH with PUSCH repetition Type B or for PUSCH repetition Type B, the above repetitions include nominal repetition(s) and / or actual repetition(s), that is, when SBFD symbol is the invalid time domain resource type, nominal repetition(s) overlapping with SBFD symbol is not transmitted (dropped), when non-SBFD symbol is the invalid time domain resource type, nominal repetition(s) overlapping with non-SBFD symbol is not transmitted (dropped), or, when SBFD symbol is the invalid time domain resource type, actual repetition(s) overlapping with SBFD symbol is not transmitted (dropped), when non-SBFD symbol is the invalid time domain resource type, actual repetition(s) overlapping with non-SBFD symbol is not transmitted (dropped).

[0212] In some embodiments, for repetition Type B, the number of nominal repetitions is provided by numberOfRepetitions (corresponding to the row of TDRA field in DCI), for example, as described in Table 6 below:

[0213] Table 6

[0214] In some embodiments, the UE determines actual repetition(s) according to nominal repetition(s), and the following is illustratively described how to determine actual repetition(s).

[0215] In some embodiments, for PUSCH with PUSCH repetition Type B or for PUSCH repetition Type B:

[0216] According to the first time domain resource and / or the second time domain resource and / or the invalid time domain resource type and / or the valid time domain resource type and / or the uplink-downlink configuration (e.g., the first uplink-downlink configuration and / or the second uplink-downlink configuration and / or the third uplink-downlink configuration) and / or the SSB, the actual repetition is determined. For example, according to the first time domain resource and / or the second time domain resource and / or the invalid time domain resource type and / or the valid time domain resource type and / or the uplink-downlink configuration (e.g., the first uplink-downlink configuration and / or the second uplink-downlink configuration and / or the third uplink-downlink configuration) and / or the SSB, invalid symbols are determined, and the remaining / other symbols are considered as (potential) valid symbols, from which the actual repetition is determined (e.g., in the manner shown in Table 7).

[0217] Table 7

[0218] In some embodiments, the UE determines a symbol that meets a first condition as an invalid symbol. For example, the first condition includes, but is not limited to: a non-SBFD symbol indicated as downlink by (the first uplink-downlink configuration and / or the second uplink-downlink configuration) (for / applicable to case 1-1 / case 1-2 / case 2), and / or, a symbol indicated as downlink by (the first uplink-downlink configuration and / or the second uplink-downlink configuration) (for case 1-1), and / or, a SBFD symbol indicated as downlink by (the second uplink-downlink configuration and / or the third uplink-downlink configuration) (for case 1-2 / 2), and / or, a symbol (for receiving) an SSB (for case 1-1 / 1-2 / 2), and / or, a SBFD symbol (for case 1-1), and / or, a non-SBFD symbol (for case 1-2).

[0219] For example, for case 1-1, the first condition includes, but is not limited to: a non-SBFD symbol indicated as downlink by (the first uplink-downlink configuration and / or the second uplink-downlink configuration), and / or, a symbol indicated as downlink by (the first uplink-downlink configuration and / or the second uplink-downlink configuration), and / or, a symbol (for receiving) an SSB, and / or, a SBFD symbol (for case 1-1).

[0220] For another example, for case 1-2, the first condition includes, but is not limited to: a non-SBFD symbol indicated as downlink by (the first uplink-downlink configuration and / or the second uplink-downlink configuration), and / or, a SBFD symbol indicated as downlink by (the second uplink-downlink configuration and / or the third uplink-downlink configuration), and / or, a symbol (for receiving) an SSB, and / or, a SBFD symbol (for case 1-1), and / or, a non-SBFD symbol.

[0221] For example, for case 1, the first condition includes but is not limited to: a non-SBFD symbol (indicated as downlink by the (first and / or second uplink-downlink configuration)), and / or a SBFD symbol (indicated as downlink by the (second and / or third uplink-downlink configuration)), and / or a symbol of a (received) SSB.

[0222] In some embodiments, (when the SBFD symbol and the non-SBFD symbol are not invalid time domain resource types), the UE does not transmit (drop) an actual repetition that overlaps with both the SBFD symbol and the non-SBFD symbol. For example, after the UE determines the actual repetitions according to the valid symbols, if one actual repetition overlaps with both the SBFD symbol and the non-SBFD symbol, the UE does not transmit (drop / omit) the actual repetition.

[0223] In some embodiments, (when the SBFD symbol and the non-SBFD symbol are not invalid time domain resource types), if one nominal repetition overlaps with both the SBFD symbol and the non-SBFD symbol, the nominal repetition corresponds to an actual repetition that overlaps with the SBFD symbol and an actual repetition that overlaps with the non-SBFD symbol, for example, the UE divides the nominal repetition and / or the actual repetition according to the (boundaries / borders of) the SBFD symbol and the non-SBFD symbol, for example, after the UE determines the actual repetitions according to the valid symbols, if one actual repetition overlaps with both the SBFD symbol and the non-SBFD symbol, the UE further divides the actual repetition into 2 or more actual repetitions, each of which includes all SBFD symbols (i.e., overlaps only with the SBFD symbol) or all non-SBFD symbols (overlaps only with the non-SBFD symbol).

[0224] In some embodiments, (when SBFD symbol and non-SBFD symbol are not invalid time domain resource type, ) if one nominal repetition overlaps with both SBFD symbol and non-SBFD symbol, there is no corresponding actual repetition for the nominal repetition (or, drop / omit the nominal repetition). For example, for the nominal repetition, the number of (potentially) valid symbols is 0, and thus there is no corresponding actual repetition.

[0225] In some embodiments, for PUSCH with PUSCH repetition Type A, or, for PUSCH repetition Type A, the number of corresponding slots (N·K slots) can be determined as described in Table 8, etc.:

[0226] Table 8

[0227] In some embodiments, for PUSCH with TBoMS, or for TBoMS, the number of corresponding slots (N·K slots) can be determined as described in Table 9, etc.:

[0228] Table 9

[0229] In some embodiments, for the first repetition type and / or TBoMS, the symbol allocation can be determined as follows, i.e., the number of symbols allocated in one slot.

[0230] Table 10

[0231] For repetition Type A and TBoMS, the following is illustratively described how to determine the corresponding N·K slots for PUSCH.

[0232] In some embodiments, for PUSCH with the first type of repetition with enabled available slot counting, or, for PUSCH with multi-slot TB (whether or not with repetition at the same time):

[0233] The (N·K) slots corresponding to the PUSCH are related to the first time domain resource and / or the second time domain resource and / or invalid time domain resource type and / or valid time domain resource type and / or uplink / downlink configuration and / or SSB.

[0234] For example, the (N·K) slots corresponding to the PUSCH can be determined according to the first time domain resource and / or the second time domain resource and / or the invalid time domain resource type and / or the valid time domain resource type and / or the uplink-downlink configuration (e.g., the first uplink-downlink configuration and / or the second uplink-downlink configuration and / or the third uplink-downlink configuration) and / or the SSB.

[0235] In some embodiments, for PUSCH repetition type A, without being configured with available slot count, the UE determines N·K consecutive slots for a PUSCH transmission of a PUSCH repetition type A scheduled by DCI format 0_1, 0_2 or 0_3, based on the TDRA information field value in the DCI format 0_1, 0_2 or 0_3.

[0236] In some embodiments, the slots in the N·K slots satisfy a second condition, which is the same for case 1 / case 1-1 / case 1-2 / case 2. In some other embodiments, the slots in the N·K slots satisfy a second condition, which is different for case 1 / case 1-1 / case 1-2 / case 2.

[0237] For example, the second condition includes but is not limited to: (for / applicable to case 1-1 / case 1-2 / case 2,) not overlapping with non-SBFD symbols indicated as downlink by (the first uplink-downlink configuration and / or the second uplink-downlink configuration), and / or, (for case 1-1,) not overlapping with downlink symbols indicated by (the first uplink-downlink configuration and / or the second uplink-downlink configuration), and / or, (for case 1-2 / case 2,) not overlapping with SBFD symbols indicated as downlink by (the second uplink-downlink configuration and / or the third uplink-downlink configuration), and / or, (for case 1-1 / case 1-2 / case 2,) not overlapping with SSB, and / or, (for case 1-1 / case 1-2 / case 2,) not overlapping with both SBFD symbols and non-SBFD symbols, and / or, (for case 1-1,) not overlapping with SBFD symbols, (for case 1-2,) not overlapping with non-SBFD symbols, and / or, (for case 1,) not overlapping with invalid time domain resource type.

[0238] For example, for case 1-1, the second condition includes but is not limited to: not overlapping with non-SBFD symbols indicated as downlink by (the first and / or second uplink-downlink configuration), and / or, not overlapping with downlink symbols indicated by (the first and / or second uplink-downlink configuration), and / or, not overlapping with SSB, and / or, not overlapping with both SBFD symbols and non-SBFD symbols, and / or, not overlapping with SBFD symbols.

[0239] For example, for case 1-2, the second condition includes but is not limited to: not overlapping with non-SBFD symbols indicated as downlink by (the first and / or second uplink-downlink configuration), and / or, not overlapping with SBFD symbols indicated as downlink by (the second and / or third uplink-downlink configuration), and / or, not overlapping with SSB, and / or, not overlapping with both SBFD symbols and non-SBFD symbols, and / or, not overlapping with non-SBFD symbols.

[0240] For example, for case 2, the second condition includes but is not limited to: not overlapping with non-SBFD symbols indicated as downlink by (the first and / or second uplink-downlink configuration), and / or, not overlapping with SBFD symbols indicated as downlink by (the second and / or third uplink-downlink configuration), and / or, not overlapping with SSB, and / or, not overlapping with both SBFD symbols and non-SBFD symbols.

[0241] In some embodiments, if the symbols corresponding to one slot do not satisfy the above-mentioned second condition, it is not counted in the N·K slots.

[0242] In some embodiments, (for case 1 / 1-1 / 1-2 / 2,) the second condition required for the first slot and other slots in the N·K slots is the same.

[0243] For example, Table 11 exemplarily shows an example of how to determine the slots corresponding to PUSCH for PUSCH repetition type A.

[0244] Table 11

[0245] In some embodiments, (for case 1,) the second condition required for the first slot and other slots in the N·K slots is different, for example, when determining the valid / invalid time domain resource type based on the second reference repetition.

[0246] In some embodiments, the first slot of the N·K slots is the same as the slot determined by the slot offset K2. For example, (for case 1,) the UE expects the slot determined by the slot offset K2 to satisfy one or more of the fourth conditions. For example, the UE expects the slot determined by the slot offset K2 to not overlap with non-SBFD symbols indicated as downlink by (the first and / or second uplink-downlink configurations) and not overlap with SSBs. For another example, the UE expects the slot determined by the slot offset K2 to not overlap with non-SBFD symbols indicated as downlink by (the first and / or second uplink-downlink configurations), not overlap with SBFD symbols indicated as downlink by (the second and / or third uplink-downlink configurations), not overlap with SSBs (not overlap with both SBFD symbols and non-SBFD symbols).

[0247] For example, Table 12 exemplarily shows another example of how to determine the slots corresponding to PUSCH for PUSCH repetition type A. Table 13 exemplarily shows an example of how to determine the slots corresponding to PUSCH for TBoMS.

[0248] Table 12

[0249] Table 13

[0250] The following further illustrates the frequency resource allocation of PUSCH, and the present application is not limited thereto.

[0251] In some embodiments, the PUSCH overlapping with the first time-domain resource and the PUSCH overlapping with the second time-domain resource correspond to the same starting RB and / or frequency hopping offset (FH offset).

[0252] In some embodiments, the PUSCH overlapping with the first time-domain resource and the PUSCH overlapping with the second time-domain resource correspond to different starting RB and / or frequency hopping offset (FH offset).

[0253] In some embodiments, for the second time-domain resource (for PUSCH overlapping with the first time-domain resource or (for repetition Type B: nominal and / or actual) repetition), a first starting RB (the starting RB within the UL BWP, as calculated from the resource block assignment information of resource allocation type 1) indicated by the DCI is applied, for the first time-domain resource (for PUSCH overlapping with the second time-domain resource or repetition), a second starting RB is applied.

[0254] In some embodiments, the second starting RB is the same as the first starting RB.

[0255] In some embodiments, the second starting RB is determined from a first RB offset (predefined or indicated) and / or the first starting RB and / or the bandwidth of the (active) (UL) BWP and / or the bandwidth of the UL usable PRBs.

[0256] In some embodiments, the above-mentioned first starting RB is, for example, the first PRB in the frequency domain resource (PRBs) indicated by the aforementioned DCI / the PRB with the lowest frequency domain position / the PRB with the smallest index.

[0257] In some embodiments, the second starting RB is determined, for example, according to a modulo value and / or scaling factor related to the first RB offset and / or the first starting RB and / or the bandwidth of the (active) (UL) BWP and / or the bandwidth of the UL usable PRBs. In some embodiments, the second starting RB is determined according to the first RB offset (RB' offset ) without the first starting RB, for example, the first RB offset is an offset relative to the starting RB (the first PRB / the PRB with the lowest frequency domain position / the PRB with the smallest index) of the UL usable PRBs, when RB' offset = 0, the second starting RB is the first PRB / the PRB with the lowest frequency domain position / the PRB with the smallest index in the UL usable PRBs, when RB' offset = 1, the second starting RB is the second PRB / the PRB with the second lowest frequency domain position / the PRB with the second smallest index in the UL usable PRBs, and so on. For example, Or Corresponding to the PRB index in the UL usable PRBs, the PRBs in the UL usable PRBs are numbered in ascending order from 0 to high by frequency, for example. indicates the size of UL usable PRBs, i.e., the number of PRBs it includes.

[0258] In some embodiments, the first RB offset is determined by the first starting RB and / or the size of the BWP and / or the size of UL usable PRBs, and in turn, the UE determines the second starting RB according to the first RB offset (e.g., using the above method). For example, wherein, is the first starting RB. is a scaling factor, for example.

[0259] In some embodiments, the second starting RB is determined according to the first RB offset and the first starting RB, for example,

[0260] In some embodiments, the first RB offset is indicated by higher layer signaling and / or FDRA field or other field in DCI.

[0261] In some embodiments, when the first RB offset is not indicated by higher layer signaling / DCI (FDRA field or other field in DCI), the second starting RB is the same as the first starting RB, or in other words, the first starting RB is applied for SBFD symbols.

[0262] In some embodiments, when the first RB offset is not indicated by higher layer signaling and / or DCI (FDRA field or other field in DCI), by default, the first RB offset = 0.

[0263] In some embodiments, (when the first RB offset is applied), the number of PRBs is the same for PUSCH transmissions in SBFD symbols and PUSCH transmissions in non-SBFD symbols.

[0264] In some embodiments, the first RB offset is applied for case 1 and / or case 2. For example, when the first RB offset is only applied for case 2, not for case 1, then for case 1-1 and resource allocation type Type 0, the frequency domain resources indicated by DCI outside the first frequency domain resources are invalid, and / or, the UE determines TBS according to the frequency domain resources indicated by DCI within the first frequency domain resources.

[0265] The following is a schematic description of how to support PUSCH frequency hopping.

[0266] In some embodiments, frequency hopping is only for / applied to the second resource allocation type, but not limited thereto.

[0267] In some embodiments, for PUSCH scheduled by DCI format 0_1, frequency hopping (e.g., intra-slot frequency hopping or inter-slot frequency hopping) is configured by frequencyHopping provided in pusch-Config for the case of the first repetition type and / or TBoMS, and frequency hopping (e.g., inter-repetition frequency hopping or inter-slot frequency hopping) is configured by frequencyHoppingDCI-0-1 provided in pusch-Config for the case of the second repetition type. And, frequency offsets are configured by higher layer parameter frequencyHoppingOffsetLists in pusch-Config (e.g., corresponding to the first FH offset list described below).

[0268] In some embodiments, for PUSCH scheduled by DCI format 0_2, frequency hopping (e.g., intra-slot frequency hopping or inter-slot frequency hopping) is configured by the higher layer parameter frequencyHoppingDCI-0-2 in pusch-Config for the case of the first repetition type, and frequency hopping (e.g., inter-repetition frequency hopping or inter-slot frequency hopping) is configured by the higher layer parameter frequencyHoppingDCI-0-2 in pusch-Config for the case of the second repetition type. And, frequency offsets are configured by higher layer parameter frequencyHoppingOffsetListsDCI-0-2 in pusch-Config (e.g., corresponding to the first FH offset list described below).

[0269] In some embodiments, the first FH offset list can be referred to as being for non-SBFD symbols, but not limited thereto. In some embodiments, the first FH offset list can be for / applied to SBFD symbols and / or non-SBFD symbols.

[0270] In some embodiments, the UE can be configured by higher layer signaling a second FH offset list for SBFD symbols. For example, the UE can be provided a higher layer parameter for configuring the second FH offset list. Where different DCI formats, e.g., DCI format 0_1 and 0_2 or 0_3, can correspond to common or independent higher layer parameters for configuring the second FH offset list. For example, the higher layer parameter for configuring the second FH offset list is optionally present in pusch-Config / PUSCH-Config, but not limited thereto. The higher layer parameter is, for example, frequencyHoppingOffsetListsSBFD (e.g., for DCI format 0_1 and 0_3), frequencyHoppingOffsetListsDCI-0-2-SBFD, (e.g., for DCI format 0_2).

[0271] In some embodiments, the second FH offset list is configured only if the first FH offset list is configured, that is, when the first FH offset list is not configured, the second FH offset list is not configured.

[0272] In some embodiments, the number of FH offsets in the second FH offset list should not be greater than or must be equal to the number of FH offsets in the first FH offset list.

[0273] In some embodiments, the number of FH offsets in the first FH offset list and the second FH offset list are both limited to the bandwidth of the BWP. For example, when the bandwidth of the corresponding BWP is less than 50 PRBs, 2 are included, otherwise, 4 are included.

[0274] In some embodiments, the number of FH offsets in the first FH offset list is limited to the bandwidth of the BWP. The number of FH offsets in the second FH offset list is limited to the bandwidth of the UL usable PRBs. For example, when the bandwidth of the corresponding UL usable PRBs is less than 50 PRBs, 2 are included, otherwise, 4 are included.

[0275] In some embodiments, the UE can be enabled / disabled by higher layer signaling to hop for SBFD symbols. For example, the UE can be provided with a higher layer parameter to enable / disable hopping for SBFD symbols (in case of (being configured with the first FH offset list but) not being configured with the second FH offset list or the DCI does not indicate the second offset). Where different DCI formats, e.g., DCI format 0_1 and 0_2 or 0_3, can correspond to common or independent higher layer parameters to enable / disable hopping for SBFD symbols. For example, the higher layer parameter to enable / disable hopping for SBFD symbols is optionally present in pusch-Config / PUSCH-Config, but not limited thereto.

[0276] In some embodiments, (when being configured with frequency hopping,) one frequency hopping flag field (to indicate whether the scheduled PUSCH is with frequency hopping or not, e.g., as shown in Table 14 below) is included in the DCI.

[0277] Table 14

[0278] In some embodiments, the DCI includes 2 frequency hopping flag fields, e.g., for SBFD symbols and non-SBFD symbols respectively, to indicate whether to hop for SBFD symbols and non-SBFD symbols respectively.

[0279] In some embodiments, (when being configured with frequency hopping,) information to indicate the frequency offset is included in the DCI, which includes, for example, N UL,hop MSB bits in the FDRA field.

[0280] In some embodiments, N UL,hop is determined by the number of FH offsets in the first FH offset list. For example, when the first FH offset list includes 2 offsets, then N UL,hop = 1, when including 4 offsets, then N UL,hop = 2.

[0281] In some embodiments, when one value of the information to indicate the frequency offset corresponds to one first FH offset (i.e., offset in the first FH offset list) and / or one second FH offset (i.e., offset in the second FH offset list), e.g., as shown in Table 15 below (where the number of offsets are assumed to be 4 and 2 respectively).

[0282] Table 15

[0283] In some embodiments, for non-SBFD symbols, a first FH offset is applied; for the SBFD symbols, the first FH offset or a second FH offset is applied or no FH offset is applied (i.e., no frequency hopping is performed).

[0284] In some embodiments, for SBFD symbols, when no second FH offset list is configured or no second FH offset is indicated by the DCI (e.g., the value corresponding to the information for indicating frequency offset in the DCI does not correspond to the second FH offset), a first FH offset (indicated by the information for indicating frequency offset in the DCI) is applied or no FH offset is applied; for example, if the value (e.g., 10 / 11 in the above table) corresponding to the information for indicating frequency offset in the DCI (corresponds to the first FH offset but) does not correspond to the second FH offset, for SBFD symbols, the first FH offset corresponding to the value is applied or no FH offset is applied.

[0285] In some embodiments, for SBFD symbols, when no second FH offset list is configured or no second FH offset is indicated by the DCI, and FH is not enabled (e.g., by higher layer signaling or DCI, as described above), a first FH offset (indicated by the information for indicating frequency offset in the DCI) is applied.

[0286] In some embodiments, for SBFD symbols, when no second FH offset list is configured or no second FH offset is indicated by the DCI, and FH is enabled (e.g., by higher layer signaling or DCI, as described above), a first FH offset (indicated by the information for indicating frequency offset in the DCI) is applied.

[0287] In some embodiments, for SBFD symbols, when FH is enabled (by the FH flag in the DCI, and) a second FH offset is indicated (by the information for indicating frequency offset in the DCI), the second FH offset is applied.

[0288] In some embodiments, for SBFD symbols, when no second FH offset is indicated (by the information for indicating frequency offset in the DCI) or no second FH offset list is configured, (and FH is disabled (by higher layer signaling or DCI, as described above) or FH is not enabled (by higher layer signaling or DCI, as described above)),) no FH offset is applied.

[0289] In some embodiments, for SBFD symbols, when no second FH offset is indicated by (information in DCI for indicating frequency offset) or no second FH offset list is configured, and FH is not enabled (e.g. by (higher layer signaling or DCI, as described above)), no FH offset is applied; for example, if DCI includes 2 frequency hopping flag fields, for SBFD symbols, when the value of frequency hopping flag field for SBFD symbols is 0 (disabled), no FH offset is applied.

[0290] In some embodiments, for SBFD symbols, when no second FH offset is indicated by (information in DCI for indicating frequency offset) or no second FH offset list is configured, and FH is not enabled (e.g. by (higher layer signaling or DCI, as described above)), no FH offset is applied.

[0291] In some embodiments, for the second time-domain resource, the third starting RB corresponding to the FH offset (the first FH offset) is determined according to the first starting RB and the bandwidth / size of the BWP.

[0292] In some embodiments, for the first time-domain resource, (in case of applying FH offset) the fourth starting RB corresponding to the FH offset (the first FH offset or the second FH offset) is determined according to the second starting RB and the bandwidth / size of the first frequency-domain resource.

[0293] The following is schematically described in connection with various types of frequency hopping.

[0294] In some embodiments, for for PUSCH repetition Type A and for TB processing over multiple slots, in case of intra-slot FH, if symbol allocation in a slot (only) overlaps with non-SBFD symbols, the first hop in the slot corresponds to the first starting RB, and the second hop corresponds to the third starting RB. If symbol allocation in a slot (only) overlaps with SBFD symbols, the first hop in the slot corresponds to the second starting RB, and the second hop corresponds to the fourth starting RB.

[0295] Table 16 exemplarily shows an example for intra-slot FH, to which the application is not limited. Wherein, if symbol allocation in a slot (only) overlaps with non-SBFD symbols (or in other words, for PUSCH transmission (only) overlapping with non-SBFD symbols), RB start is the first starting RB, RB offset is the first FH offset as described above, is the bandwidth / size of (UL) BWP, RB start (i = 1) is the third starting RB as described above. If symbol allocation in a slot (only) overlaps with SBFD symbols (or in other words, for PUSCH transmission (only) overlapping with SBFD symbols), (when applying FH), RB start is the second starting RB, RB offset is the first FH offset or the second FH offset (determined according to the aforementioned method which one to apply), is the bandwidth / size of UL usable PRBs, RB start (i = 1) is the fourth starting RB as described above.

[0296] Table 16

[0297] In some embodiments, for PUSCH repetition Type A and for TB processing over multiple slots, slots or repetitions are counted independently, and it has been determined that the corresponding frequency domain resources of the slots / repetitions.

[0298] For example, in the case of inter-slot FH, for slots in a frame, slots containing SBFD symbols and slots containing non-SBFD symbols are numbered respectively. For example, if a slot contains both SBFD symbols and non-SBFD symbols, in numbering: the slot is counted in both slots containing SBFD symbols and slots containing non-SBFD symbols; or the slot is regarded as 2 slots, one containing only SBFD symbols and one containing only non-SBFD symbols, and then counted in slots containing SBFD symbols and slots containing non-SBFD symbols respectively.

[0299] For example, for slots containing non-SBFD symbols, the first hop corresponds to the first starting RB, and the second hop corresponds to the third starting RB. For slots containing SBFD symbols, the first hop corresponds to the second starting RB, and the second hop corresponds to the fourth starting RB.

[0300] Table 17 exemplarily shows one example for inter-slot FH, the present application is not limited thereto.

[0301] Table 17

[0302] For example, for for PUSCH repetition Type A and for TB processing over multiple slots, in case of inter-slot FH, only the repetitions or PUSCH transmissions (occasions) overlapping with SBFD symbols and only the repetitions or PUSCH transmissions (occasions) overlapping with non-SBFD symbols are numbered separately.

[0303] For example, for the repetitions or PUSCH transmissions (occasions) overlapping with non-SBFD symbols, the first hop corresponds to the first starting RB and the second hop corresponds to the third starting RB. For the repetitions or PUSCH transmissions (occasions) overlapping with SBFD symbols, the first hop corresponds to the second starting RB and the second hop corresponds to the fourth starting RB.

[0304] Table 18 exemplarily shows one example for inter-slot FH, the present application is not limited thereto.

[0305] Table 18

[0306] For example, in case of inter-repetition FH, only the nominal repetitions overlapping with SBFD symbols and only the nominal repetitions overlapping with non-SBFD symbols are numbered separately.

[0307] For example, for the nominal repetitions overlapping with non-SBFD symbols, the first hop corresponds to the first starting RB and the second hop corresponds to the third starting RB. For the nominal repetitions overlapping with SBFD symbols, the first hop corresponds to the second starting RB and the second hop corresponds to the fourth starting RB.

[0308] Table 19 exemplarily shows one example for inter-repetition FH, the present application is not limited thereto.

[0309] Table 19

[0310] The above only describes the steps or processes related to the present application, but the present application is not limited thereto. The method of the embodiments of the present application can also include other steps or processes, and the specific content of these steps or processes can be referred to the related art.

[0311] The above embodiments only exemplarily describe the embodiments of the present application, but the present application is not limited thereto, and appropriate modifications can be made on the basis of the above embodiments. For example, the above embodiments can be used alone, or one or more of the above embodiments can be combined.

[0312] As can be seen from the above embodiments, the terminal device receives downlink control information (DCI) for activating a semi-persistent CSI triggering state; and performs semi-persistent CSI reporting on a PUSCH. In this way, the network device can work in a full-duplex mode (simultaneous reception and transmission), and the terminal device can also use the corresponding resources to transceive signals when the network device works in the full-duplex mode, which can improve the capacity and coverage of uplink transmission, reduce the latency of uplink transmission, and improve the resource allocation flexibility and resource utilization.

[0313] Embodiments of the second aspect

[0314] The embodiments of the present application provide a CSI receiving method, which is described from the network device side. The same content as the embodiments of the first aspect will not be described again.

[0315] FIG. 6 is a schematic diagram of a CSI receiving method according to an embodiment of the present application. As shown in FIG. 6, the method includes the following steps.

[0316] 601. The network device sends DCI for activating a semi-persistent CSI triggering state to a terminal device; and

[0317] 602. The network device receives semi-persistent CSI reporting of the terminal device on a PUSCH.

[0318] In the PUSCH: the PUSCH overlapping with the first time domain resource is not used for the semi-persistent CSI reporting (or the PUSCH overlapping with the first time domain resource is not sent), or the PUSCH overlapping with the second time domain resource is not used for the semi-persistent CSI reporting (or the PUSCH overlapping with the second time domain resource is not sent), or both the PUSCH overlapping with the first time domain resource and the PUSCH overlapping with the second time domain resource are used for the semi-persistent CSI reporting; in the first time domain resource, the first frequency domain resource is used for uplink and the second frequency domain resource is used for downlink, and the second time domain resource is outside the first time domain resource.

[0319] It is noticeable that the above Fig. 6 only schematically illustrates the embodiments of the present application, but the present application is not limited to this. For example, the execution sequence between various operations can be properly adjusted, and furthermore, some operations can be added or some operations can be reduced. Those skilled in the art can properly modify them according to the above description, and the present application is not limited to the above Fig. 6.

[0320] In some embodiments, the PUSCH does not carry uplink data.

[0321] In some embodiments, the trigger state associated CSI reporting configuration associated CSI-RS is confined in the first time domain resource or the second time domain resource.

[0322] In some embodiments, the CSI reporting configuration includes information indicating that the associated CSI-RS is confined in the first time domain resource or the second time domain resource, and / or, the CSI resource configuration corresponding to the CSI-RS includes information indicating that the CSI-RS is confined in the first time domain resource or the second time domain resource.

[0323] In some embodiments, the PUSCH has repetition:

[0324] When the first time domain resource is invalid time domain resource type, the repetition overlapping with the first time domain resource is not transmitted, and / or,

[0325] When the second time domain resource is invalid time domain resource type, the repetition overlapping with the second time domain resource is not transmitted.

[0326] In some embodiments, the invalid time domain resource type and / or valid time domain resource type is determined based on the first information and / or the second information and / or time domain resource indicated by (TDRA field in) the first reference PUSCH and / or corresponding activation DCI.

[0327] In some embodiments, the first information is used to indicate that there is no invalid time domain resource type and / or is used to indicate that there is invalid time domain resource type (for example, at least one of the first time domain resource and the second time domain resource is invalid time domain resource type);

[0328] The first information (optionally) exists outside the SP-CSI configuration (for example, is included in PUSCH-Config or PUSCH-ConfigCommon), the first information is applied to all or part of the SP-CSI configuration in the SP-CSI configuration, or the first information (optionally) exists in the SP-CSI configuration, and the first information is applied to the SP-CSI configuration where it exists.

[0329] In some embodiments, the first information is also applied to other PUSCH scheduling (e.g., DCI scheduling multiple PUSCHs and / or DCI scheduling PUSCH repetition) and / or CSI-RS (e.g., periodic CSI-RS and / or semi-persistent CSI-RS).

[0330] In some embodiments, the second information is used to indicate an invalid time domain resource type and / or a valid time domain resource type (e.g., the second information is used to indicate that the first time domain resource is an invalid time domain resource type and / or used to indicate that the second time domain resource is an invalid time domain resource type, or, the second information is used to indicate that the first time domain resource is a valid time domain resource type and / or used to indicate that the second time domain resource is a valid time domain resource type); the second information (optionally) exists in a SP-CSI configuration, and the second information is applied to the SP-CSI configuration where the second information exists.

[0331] In some embodiments, the invalid time domain resource type and / or the valid time domain resource type is determined based on a first reference PUSCH, including:

[0332] The valid time domain resource type is a time domain resource type of the first reference PUSCH;

[0333] Wherein, if the first reference PUSCH overlaps with only the first time domain resource, the valid time domain resource type is the first time domain resource, if the first reference PUSCH overlaps with only the second time domain resource, the valid time domain resource type is the second time domain resource, or, the terminal device does not expect the first reference PUSCH to overlap with both the first time domain resource and the second time domain resource.

[0334] In some embodiments, in the case of repetition, the terminal device expects all repetitions of the first reference PUSCH to overlap with only the first time domain resource or to overlap with only the second time domain resource, or, the valid time domain resource type or the time domain resource type of the first reference PUSCH is a time domain resource type of a first reference repetition of the first reference PUSCH.

[0335] In some embodiments, the invalid time domain resource type and / or the valid time domain resource type is determined based on a time domain resource indicated by an activation DCI, including:

[0336] If the time domain resource indicated by the activation DCI overlaps with only the first time domain resource, the valid time domain resource type is the first time domain resource, and / or, the invalid time domain resource type is the second time domain resource;

[0337] If the time-domain resources indicated by the activation DCI overlap (only) with the second time-domain resources, the valid time-domain resource type is the second time-domain resource, and / or, the invalid time-domain resource type is the first time-domain resource.

[0338] In some embodiments, when the first information (only) indicates that there is no invalid time-domain resource type:

[0339] The first information and the second information do not exist at the same time (when the first information exists, the second information does not exist, and vice versa); or,

[0340] When the first information and the second information exist at the same time, the first information is not applied to the SP-CSI configuration including the second information, and / or, is applied to the SP-CSI configuration not including the second information.

[0341] In some embodiments, when the terminal device is not provided with the first information or when the first information indicates that there is an invalid time-domain resource type, the second information is (must) included in the SP-CSI configuration; or,

[0342] For the SP-CSI configuration not including the second information:

[0343] The terminal device determines the invalid time-domain resource type and / or the valid time-domain resource type based on the first reference PUSCH or the time-domain resources indicated by the activation DCI, or the terminal device considers that the first time-domain resource or the second time-domain resource is the invalid time-domain resource type.

[0344] In some embodiments, the PUSCH overlapping with the first time-domain resource and the PUSCH overlapping with the second time-domain resource correspond to the same starting RB and / or frequency hopping offset (FH offset), or correspond to different starting RB and / or frequency hopping offset (FH offset).

[0345] In some embodiments, for the PUSCH overlapping with the first time-domain resource, the first starting RB indicated by the DCI (FDRA field) is applied, and for the PUSCH overlapping with the second time-domain resource, the second starting RB is applied, the second starting RB is the same as the first starting RB or is offset (predefined or indicated) from the first starting RB and / or determined by the first starting RB and / or the bandwidth of the uplink BWP and / or the bandwidth of the uplink available resources.

[0346] In some embodiments, the first RB offset is relative to the first starting RB indicated by the DCI (FDRA field), or the first RB offset is relative to the starting RB of the UL BWP where the PUSCH is located.

[0347] In some embodiments, the first RB offset is an offset between a starting RB of the first frequency domain resource and a starting RB of the UL BWP where the PUSCH is located.

[0348] In some embodiments,

[0349] For a PUSCH overlapping with the first time domain resource, the DCI (of the FDRA field) indicates the first starting RB based on a starting RB of the UL BWP where the PUSCH is located; and / or

[0350] For a PUSCH overlapping with the second time domain resource, the DCI (of the FDRA field) indicates the first starting RB based on the starting RB of the first frequency domain resource or based on the RB determined by the first RB offset.

[0351] In some embodiments, the first RB offset is configured by higher layer signaling, or the first RB offset is indicated by the DCI.

[0352] In some embodiments, for a PUSCH overlapping with the first time domain resource, a first FH offset is applied, and for a PUSCH overlapping with the second time domain resource, the first FH offset or a second FH offset or no FH offset is applied.

[0353] In some embodiments, for a PUSCH overlapping with the first time domain resource, a third starting RB corresponding to a frequency hopping offset (the first FH offset or the second FH offset) is determined according to a first starting RB and a bandwidth / size of the BWP.

[0354] In some embodiments, for a PUSCH overlapping with the second time domain resource, a fourth starting RB corresponding to a frequency hopping offset (the first FH offset or the second FH offset) is determined according to a second starting RB and a bandwidth / size of the first frequency domain resource.

[0355] The above only describes each step or process related to the present application, but the present application is not limited thereto. The method of the embodiments of the present application can also include other steps or processes, and the specific content of these steps or processes can be referred to the related art.

[0356] The above various embodiments only exemplarily describe the embodiments of the present application, but the present application is not limited thereto, and can be appropriately modified on the basis of the above various embodiments. For example, each of the above various embodiments can be used alone, or one or more of the above various embodiments can be combined.

[0357] From the above embodiments, the network device sends, to the terminal device, downlink control information (DCI) for activating a semi-persistent CSI triggering state, and receives semi-persistent CSI reporting on a PUSCH. In this way, the network device can work in a full-duplex mode (simultaneous reception and transmission), and the terminal device can also receive and transmit signals using corresponding resources when the network device works in the full-duplex mode, which can improve the capacity and coverage of uplink transmission, reduce the latency of uplink transmission, and improve the resource allocation flexibility and resource utilization.

[0358] Embodiments of the third aspect

[0359] Embodiments of the present application provide a CSI reporting device. The device may, for example, be a terminal device, or one or more components or assemblies configured in the terminal device. The same content as the embodiments of the first aspect will not be described again.

[0360] FIG. 7 is a schematic diagram of a CSI reporting device according to an embodiment of the present application. Since the principle of solving the problem of the device is the same as that of the method of the embodiments of the first aspect, the specific implementation thereof can refer to the embodiments of the first aspect, and the same content will not be described repeatedly. As shown in FIG. 7, the CSI reporting device 700 includes a receiver 701 and a transmitter 702, and can further include a processor 703.

[0361] The receiver 701 receives downlink control information (DCI) for activating a semi-persistent CSI triggering state, and

[0362] The transmitter 702 performs semi-persistent CSI reporting on a PUSCH.

[0363] In the PUSCH, the PUSCH overlapping with the first time domain resource is not used for the semi-persistent CSI reporting (or the PUSCH overlapping with the first time domain resource is not transmitted), or the PUSCH overlapping with the second time domain resource is not used for the semi-persistent CSI reporting (or the PUSCH overlapping with the second time domain resource is not transmitted), or both the PUSCH overlapping with the first time domain resource and the PUSCH overlapping with the second time domain resource are used for the semi-persistent CSI reporting. In the first time domain resource, the first frequency domain resource is used for uplink and the second frequency domain resource is used for downlink, and the second time domain resource is outside the first time domain resource.

[0364] In some embodiments, the PUSCH does not carry uplink data.

[0365] In some embodiments, the CSI reporting configuration associated with the triggering state is limited to the first time domain resource or the second time domain resource.

[0366] In some embodiments, the CSI report configuration includes information indicating that the associated CSI-RS is confined in the first time domain resource or the second time domain resource, and / or the CSI resource configuration corresponding to the CSI-RS includes information indicating that the CSI-RS is confined in the first time domain resource or the second time domain resource.

[0367] In some embodiments, the PUSCH has repetition:

[0368] When the first time domain resource is invalid time domain resource type, the repetition overlapping with the first time domain resource is not transmitted, and / or,

[0369] When the second time domain resource is invalid time domain resource type, the repetition overlapping with the second time domain resource is not transmitted.

[0370] In some embodiments, the invalid time domain resource type and / or valid time domain resource type is determined based on the first information and / or the second information and / or time domain resource (e.g., symbol in slot n+k0) indicated by TDRA field in the first reference PUSCH and / or corresponding activation DCI.

[0371] In some embodiments, the first information is used to indicate no invalid time domain resource type and / or to indicate having invalid time domain resource type (e.g., at least one of the first time domain resource and the second time domain resource is invalid time domain resource type);

[0372] The first information is (optionally) present outside the SP-CSI configuration (e.g., included in PUSCH-Config or PUSCH-ConfigCommon), the first information applies to all or part of the SP-CSI configuration, or the first information is (optionally) present in the SP-CSI configuration, the first information applies to the SP-CSI configuration where it is present.

[0373] In some embodiments, the first information also applies to other PUSCH scheduling (e.g., DCI scheduling multiple PUSCH and / or DCI scheduling PUSCH repetition) and / or CSI-RS (e.g., periodic CSI-RS and / or semi-persistent CSI-RS).

[0374] In some embodiments, the second information is used to indicate an invalid time domain resource type and / or a valid time domain resource type (e.g., the second information is used to indicate that the first time domain resource is an invalid time domain resource type and / or used to indicate that the second time domain resource is an invalid time domain resource type, or, the second information is used to indicate that the first time domain resource is a valid time domain resource type and / or used to indicate that the second time domain resource is a valid time domain resource type); the second information (optionally) exists in the SP-CSI configuration to which the second information applies.

[0375] In some embodiments, the invalid time domain resource type and / or the valid time domain resource type are determined based on the first reference PUSCH, including:

[0376] The valid time domain resource type is a time domain resource type of the first reference PUSCH;

[0377] wherein, if the first reference PUSCH overlaps with only the first time domain resource, the valid time domain resource type is the first time domain resource, if the first reference PUSCH overlaps with only the second time domain resource, the valid time domain resource type is the second time domain resource, or, the terminal device does not expect the first reference PUSCH to overlap with both the first time domain resource and the second time domain resource.

[0378] In some embodiments, in the case of repetition, the terminal device expects all repetitions of the first reference PUSCH to overlap with only the first time domain resource or to overlap with only the second time domain resource, or, the valid time domain resource type or the time domain resource type of the first reference PUSCH is a time domain resource type of a first reference repetition of the first reference PUSCH.

[0379] In some embodiments, the invalid time domain resource type and / or the valid time domain resource type are determined based on a time domain resource indicated by the activation DCI, including:

[0380] If the time domain resource indicated by the activation DCI overlaps with only the first time domain resource, the valid time domain resource type is the first time domain resource, and / or, the invalid time domain resource type is the second time domain resource;

[0381] If the time domain resource indicated by the activation DCI overlaps with only the second time domain resource, the valid time domain resource type is the second time domain resource, and / or, the invalid time domain resource type is the first time domain resource.

[0382] In some embodiments, when the first information is used to indicate only no invalid time domain resource type:

[0383] The first information and the second information do not exist at the same time (when the first information exists, the second information does not exist, and vice versa); or

[0384] When the first information and the second information exist at the same time, the first information is not applied to the SP-CSI configuration including the second information, and / or, is applied to the SP-CSI configuration not including the second information.

[0385] In some embodiments, when the terminal device is not provided with the first information or when the first information indicates a time domain resource type with invalidity, the second information is (must be) included in the SP-CSI configuration; or,

[0386] For the SP-CSI configuration not including the second information:

[0387] The terminal device determines the invalid time domain resource type and / or the valid time domain resource type based on the first reference PUSCH or the time domain resource indicated by the activation DCI, or the terminal device considers that the first time domain resource or the second time domain resource is the invalid time domain resource type.

[0388] In some embodiments, the PUSCH overlapping with the first time domain resource and the PUSCH overlapping with the second time domain resource correspond to the same starting RB and / or frequency hopping offset (FH offset), or correspond to different starting RB and / or frequency hopping offset (FH offset).

[0389] In some embodiments, for the PUSCH overlapping with the first time domain resource, the first starting RB indicated by the FDRA field of the DCI is applied, and for the PUSCH overlapping with the second time domain resource, the second starting RB is applied, the second starting RB is the same as the first starting RB or is offset (predefined or indicated) from the first starting RB and / or determined by the first starting RB and / or the bandwidth of the uplink BWP and / or the bandwidth of the uplink available resources.

[0390] In some embodiments, the first RB offset is relative to the first starting RB indicated by the FDRA field of the DCI, or the first RB offset is relative to the starting RB of the UL BWP where the PUSCH is located.

[0391] In some embodiments, the first RB offset is the offset between the starting RB of the first frequency domain resource and the starting RB of the UL BWP where the PUSCH is located.

[0392] In some embodiments, for the PUSCH overlapping with the first time domain resource, the DCI (FDRA field of the DCI) indicates the first starting RB based on a starting RB of a UL BWP where the PUSCH is located; and / or

[0393] For the PUSCH overlapping with the second time domain resource, the DCI (FDRA field of the DCI) indicates the first starting RB based on a starting RB of the first frequency domain resource or based on the RB determined by the first RB offset.

[0394] In some embodiments, the first RB offset is configured by higher layer signaling, or the first RB offset is indicated by the DCI.

[0395] In some embodiments, for the PUSCH overlapping with the first time domain resource, a first FH offset is applied, and for the PUSCH overlapping with the second time domain resource, the first FH offset or a second FH offset is applied or no FH offset is applied.

[0396] In some embodiments, for the PUSCH overlapping with the first time domain resource, a third starting RB corresponding to the frequency hopping offset (the first FH offset or the second FH offset) is determined according to the first starting RB and a bandwidth / size of a BWP.

[0397] In some embodiments, for the PUSCH overlapping with the second time domain resource, a fourth starting RB corresponding to the frequency hopping offset (the first FH offset or the second FH offset) is determined according to the second starting RB and a bandwidth / size of the first frequency domain resource.

[0398] It is worth noting that the above only describes the components or modules related to the present application, but the present application is not limited thereto. The CSI reporting device 700 of the embodiments of the present application can also include other components or modules, and the specific content of these components or modules can be referred to the related art.

[0399] In addition, for the sake of simplicity, only the connection relationship or signal path between the components or modules is exemplarily shown in FIG. 7, but it should be clear to those skilled in the art that various related technologies such as bus connection can be used. The above components or modules can be realized by hardware facilities such as processors, memories, transmitters, receivers, etc.; the present application is not limited thereto.

[0400] The above embodiments only exemplarily illustrate the embodiments of the present application, but the present application is not limited thereto, and can be appropriately modified on the basis of the above embodiments. For example, the above embodiments can be used alone or one or more of the above embodiments can be combined.

[0401] As can be seen from the above embodiments, the terminal device receives downlink control information (DCI) for activating a semi-persistent CSI triggering state; and performs semi-persistent CSI reporting on a PUSCH. In this way, the network device can work in a full-duplex mode (simultaneous reception and transmission), and the terminal device can also receive and transmit signals using the corresponding resources when the network device works in the full-duplex mode, which can improve the capacity and coverage of uplink transmission, reduce the latency of uplink transmission, and improve the resource allocation flexibility and resource utilization.

[0402] Embodiments of the fourth aspect

[0403] The embodiments of the present application provide a CSI receiving device. The device may, for example, be a network device, or one or more components or assemblies configured in the network device. The same content as the embodiments of the third aspect will not be described again.

[0404] FIG. 8 is a schematic diagram of a CSI receiving device according to an embodiment of the present application. Since the principle of solving the problem of the device is the same as that of the method of the first and second aspects, the specific implementation can refer to the embodiments of the first and second aspects, and the same content will not be described again. As shown in FIG. 8, the CSI receiving device 800 includes a transmitter 801 and a receiver 802, and can further include a processor 803.

[0405] The transmitter 801 transmits downlink control information (DCI) for activating a semi-persistent CSI triggering state; and the receiver 802 receives semi-persistent CSI reporting on a PUSCH;

[0406] In the PUSCH, the PUSCH overlapping with the first time domain resource is not used for the semi-persistent CSI reporting (or the PUSCH overlapping with the first time domain resource is not transmitted), or the PUSCH overlapping with the second time domain resource is not used for the semi-persistent CSI reporting (or the PUSCH overlapping with the second time domain resource is not transmitted), or both the PUSCH overlapping with the first time domain resource and the PUSCH overlapping with the second time domain resource are used for the semi-persistent CSI reporting; in the first time domain resource, the first frequency domain resource is used for uplink and the second frequency domain resource is used for downlink, and the second time domain resource is outside the first time domain resource.

[0407] It is worth noting that the above only illustrates the components or modules related to the present application, but the present application is not limited thereto. The CSI receiving apparatus 800 of the embodiments of the present application can further include other components or modules, and the specific content of these components or modules can be referred to the related art.

[0408] In addition, for the sake of simplicity, only the connection relationship or signal path between the components or modules is exemplarily shown in FIG. 8, but it should be clear to those skilled in the art that various related technologies such as bus connection can be used. The above components or modules can be implemented by hardware facilities such as processors, memories, transmitters, receivers, etc.; the present application is not limited thereto.

[0409] The above embodiments only exemplarily illustrate the embodiments of the present application, but the present application is not limited thereto, and appropriate modifications can be made on the basis of the above embodiments. For example, the above embodiments can be used alone, or one or more of the above embodiments can be combined.

[0410] From the above embodiments, the network device sends downlink control information (DCI) for activating a semi-persistent CSI triggering state to the terminal device; and receives semi-persistent CSI reporting on the PUSCH. In this way, the network device can work in a full-duplex mode (simultaneous reception and transmission), and the terminal device can also use the corresponding resources to transceive signals when the network device works in the full-duplex mode, which can improve the capacity and coverage of uplink transmission, reduce the latency of uplink transmission, and improve the resource allocation flexibility and resource utilization.

[0411] Embodiments of the fifth aspect

[0412] The embodiments of the present application also provide a communication system, which can be referred to FIG. 1, and the same content as the embodiments of the first to fourth aspects will not be repeated.

[0413] In some embodiments, the communication system 100 can at least include:

[0414] The network device sends downlink control information (DCI) for activating a semi-persistent CSI triggering state; and receives semi-persistent CSI reporting on the PUSCH;

[0415] The terminal device receives downlink control information (DCI) for activating a semi-persistent CSI triggering state; and performs semi-persistent CSI reporting on the PUSCH;

[0416] In the PUSCH, the PUSCH overlapping with the first time domain resource is not used for the semi-persistent CSI reporting (or the PUSCH overlapping with the first time domain resource is not transmitted), or the PUSCH overlapping with the second time domain resource is not used for the semi-persistent CSI reporting (or the PUSCH overlapping with the second time domain resource is not transmitted), or both the PUSCH overlapping with the first time domain resource and the PUSCH overlapping with the second time domain resource are used for the semi-persistent CSI reporting; the first time domain resource is used for uplink and the second time domain resource is used for downlink.

[0417] Embodiments of the present application further provide a network device, which can be a base station, but the present application is not limited thereto, and can also be other network devices.

[0418] FIG. 9 is a schematic diagram of a network device according to an embodiment of the present application. As shown in FIG. 9, the network device 900 can include a processor 910 (such as a central processing unit CPU) and a memory 920; the memory 920 is coupled to the processor 910. The memory 920 can store various data; in addition, it also stores a program 930 for information processing, and executes the program 930 under the control of the processor 910.

[0419] For example, the processor 910 can be configured to execute a program to implement the method according to the embodiments of the second aspect.

[0420] In addition, as shown in FIG. 9, the network device 900 can also include a transceiver 940, an antenna 950, etc.; the functions of the above components are similar to those of the prior art, and will not be described here. It is worth noting that the network device 900 does not necessarily include all the components shown in FIG. 9; in addition, the network device 900 can also include components not shown in FIG. 9, which can be referred to the prior art.

[0421] Embodiments of the present application further provide a terminal device, but the present application is not limited thereto, and can also be other devices.

[0422] FIG. 10 is a schematic diagram of a terminal device according to an embodiment of the present application. As shown in FIG. 10, the terminal device 1000 can include a processor 1010 and a memory 1020; the memory 1020 stores data and programs, and is coupled to the processor 1010. It is worth noting that the diagram is exemplary; other types of structures can also be used to supplement or replace the structure to implement telecommunication functions or other functions.

[0423] For example, the processor 1010 can be configured to execute a program to implement the method according to the embodiments of the first aspect.

[0424] As shown in FIG. 10, the terminal device 1000 can further include a communication module 1030, an input device 1040, a display 1050, and a power supply 1060. The functions of the above components are similar to those of the prior art, and will not be described here. It is important to note that the terminal device 1000 does not necessarily include all the components shown in FIG. 10, and the above components are not essential; in addition, the terminal device 1000 can include components not shown in FIG. 10, and reference can be made to the prior art.

[0425] The embodiments of the present application also provide a computer readable program, which, when executed in a network device, causes the computer to perform the method of the embodiments of the second aspect in the network device.

[0426] The embodiments of the present application also provide a storage medium storing a computer readable program, which causes the computer to perform the method of the embodiments of the second aspect in the network device.

[0427] The embodiments of the present application also provide a computer readable program, which, when executed in a terminal device, causes the computer to perform the method of the embodiments of the first aspect in the terminal device.

[0428] The embodiments of the present application also provide a storage medium storing a computer readable program, which causes the computer to perform the method of the embodiments of the first aspect in the terminal device.

[0429] The above apparatus and method of the present application can be implemented by hardware, or by a combination of hardware and software. The present application relates to a computer readable program, which, when executed by a logic component, can cause the logic component to implement the above apparatus or components, or to implement the above various methods or steps. The logic component is, for example, a field programmable logic component, a microprocessor, a processor used in a computer, etc. The present application also relates to a storage medium for storing the above program, such as a hard disk, a magnetic disk, an optical disk, a DVD, a flash memory, etc.

[0430] The method / apparatus described in conjunction with the embodiments of the present application can be directly embodied as hardware, a software module executed by a processor, or a combination of the two. For example, one or more of the functional blocks shown in the figure and / or a combination of one or more functional blocks can correspond to a software module of a computer program flow, or to a hardware module. These software modules can correspond to the respective steps shown in the figure. These hardware modules can be implemented by, for example, fixing the software modules with a field programmable gate array (FPGA).

[0431] The software modules can reside in RAM, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. The storage medium can be 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 can be integral to the processor. The processor and the storage medium can reside in an ASIC. The software modules can be stored in a memory of the mobile terminal, or in a memory card that can be inserted into the mobile terminal. For example, if the device (e.g., mobile terminal) employs a MEGA-SIM card or a flash memory device with a large capacity, the software modules can be stored in the MEGA-SIM card or the flash memory device.

[0432] One or more of the functional blocks described in the accompanying drawings can be implemented as 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 appropriate combination thereof, for performing the functions described in this application. One or more of the functional blocks described in the accompanying drawings can also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.

[0433] The application has been described in connection with certain embodiments. However, those skilled in the art will appreciate that modifications and variations to the described embodiments are possible, and that such modifications and variations are within the scope of the application. Accordingly, the application is not to be limited to the described embodiments, but is intended to include all such modifications and variations as are within the scope of the appended claims.

[0434] In connection with the embodiments including the above embodiments, the following supplementary notes are also disclosed:

[0435] 1. A CSI reporting method, comprising:

[0436] receiving, by a terminal device, a downlink control information (DCI) for activating a semi-persistent CSI triggering state; and

[0437] reporting, by the terminal device, a semi-persistent CSI on a PUSCH;

[0438] In the PUSCH, PUSCHs overlapping with the first time domain resources are not used for the semi-persistent CSI reporting (or PUSCHs overlapping with the first time domain resources are not transmitted), or PUSCHs overlapping with the second time domain resources are not used for the semi-persistent CSI reporting (or PUSCHs overlapping with the second time domain resources are not transmitted), or both PUSCHs overlapping with the first time domain resources and PUSCHs overlapping with the second time domain resources are used for the semi-persistent CSI reporting.

[0439] 2. A CSI receiving method, comprising:

[0440] a network device transmitting downlink control information (DCI) for activating a semi-persistent CSI triggering state; and

[0441] the network device receiving semi-persistent CSI reporting on a PUSCH.

[0442] In the PUSCH, PUSCHs overlapping with the first time domain resources are not used for the semi-persistent CSI reporting (or PUSCHs overlapping with the first time domain resources are not transmitted), or PUSCHs overlapping with the second time domain resources are not used for the semi-persistent CSI reporting (or PUSCHs overlapping with the second time domain resources are not transmitted), or both PUSCHs overlapping with the first time domain resources and PUSCHs overlapping with the second time domain resources are used for the semi-persistent CSI reporting.

[0443] 3. A terminal device comprising a memory and a processor, the memory storing a computer program, and the processor being configured to execute the computer program to implement the CSI reporting method according to the preceding clause 1.

[0444] 4. A network device comprising a memory and a processor, the memory storing a computer program, and the processor being configured to execute the computer program to implement the CSI receiving method according to the preceding clause 2.

[0445] 5. A computer program product comprising at least a computer program, the computer program being executed by a processor to cause a terminal device to perform the CSI reporting method according to the preceding clause 1.

[0446] 6. A computer program product comprising at least a computer program, the computer program being executed by a processor to cause a network device to perform the CSI receiving method according to the preceding clause 2.

Claims

1. A CSI reporting apparatus, comprising: a receiver configured to receive a downlink control information for activating a semi-persistent CSI triggering state; and a transmitter configured to perform a semi-persistent CSI reporting on a PUSCH; wherein, in the PUSCH: PUSCHs overlapping with a first time domain resource are not used for the semi-persistent CSI reporting, or PUSCHs overlapping with a second time domain resource are not used for the semi-persistent CSI reporting, or both PUSCHs overlapping with the first time domain resource and PUSCHs overlapping with the second time domain resource are used for the semi-persistent CSI reporting; in the first time domain resource, a first frequency domain resource is used for uplink and a second frequency domain resource is used for downlink, and the second time domain resource is out of the first time domain resource. the PUSCH does not carry uplink data.

2. The apparatus of claim 1, wherein, a CSI report configuration associated with the triggering state is associated with a CSI-RS which is restricted in the first time domain resource or the second time domain resource; 3. The apparatus of claim 1, wherein, information in the CSI report configuration is used to indicate that the associated CSI-RS is restricted in the first time domain resource or the second time domain resource, and / or information in a CSI resource configuration corresponding to the CSI-RS is used to indicate that the CSI-RS is restricted in the first time domain resource or the second time domain resource. 4.The apparatus of claim 1, wherein, frequency domain resources within the allocated second frequency domain resource are valid, or the allocated frequency domain resources are valid, or frequency domain resources out of the allocated second frequency domain resource are invalid. 5.The apparatus of claim 4, wherein, when the second time domain resource is an invalid time domain resource type, frequency domain resources within the allocated second frequency domain resource are valid, and / or frequency domain resources out of the allocated second frequency domain resource are invalid. 6.The apparatus of claim 4, wherein, when there is no invalid time domain resource type, for PUSCHs overlapping with the first time domain resource, frequency domain resources within the allocated second frequency domain resource are valid, and / or for PUSCHs overlapping with the second time domain resource, the allocated frequency domain resources are valid. 7.The apparatus of claim 1, wherein, when the first time domain resource is an invalid time domain resource type, PUSCHs overlapping with the first time domain resource are not transmitted, and / or when the second time domain resource is an invalid time domain resource type, PUSCHs overlapping with the second time domain resource are not transmitted; wherein, the invalid time domain resource type and / or the valid time domain resource type is determined based on first information and / or second information and / or a first reference PUSCH and / or time domain resources indicated by a corresponding activating DCI. the first information is used to indicate that there is no invalid time domain resource type and / or is used to indicate that there is an invalid time domain resource type. ​ 8. The apparatus of claim 7, wherein, ​ The first information exists outside the SP-CSI configuration, the first information is applied to all or part of the SP-CSI configuration in the SP-CSI configuration, or the first information exists in the SP-CSI configuration, and the first information is applied to the SP-CSI configuration.

9. The apparatus of claim 7, wherein, The second information is used to indicate invalid time domain resource types and / or valid time domain resource types. The second information exists in the SP-CSI configuration, and the second information is applied to the SP-CSI configuration.

10. The apparatus of claim 7, wherein, Determining the invalid time domain resource type and / or the valid time domain resource type based on the first reference PUSCH comprises: The valid time domain resource type is the time domain resource type of the reference PUSCH. If the first reference PUSCH overlaps with the first time domain resource, the valid time domain resource type is the first time domain resource, if the first reference PUSCH overlaps with the second time domain resource, the valid time domain resource type is the second time domain resource, or the terminal device does not expect the first reference PUSCH to overlap with both the first time domain resource and the second time domain resource. In the case of repetition, the terminal device expects all repetitions of the first reference PUSCH to overlap with the first time domain resource or the second time domain resource, or the valid time domain resource type or the time domain resource type of the first reference PUSCH is the time domain resource type of the first reference repetition of the first reference PUSCH.

11. The apparatus of claim 7, wherein, Determining the invalid time domain resource type and / or the valid time domain resource type based on the time domain resource indicated by the activation DCI comprises: If the time domain resource indicated by the activation DCI overlaps with the first time domain resource, the valid time domain resource type is the first time domain resource, and / or the invalid time domain resource type is the second time domain resource. If the time domain resource indicated by the activation DCI overlaps with the second time domain resource, the valid time domain resource type is the second time domain resource, and / or the invalid time domain resource type is the first time domain resource.

12. The apparatus of claim 7, wherein, When the first information is used to indicate that there is no invalid time domain resource type: The first information and the second information do not exist at the same time; or When the first information and the second information exist at the same time, the first information is not applied to the SP-CSI configuration including the second information, and / or is applied to the SP-CSI configuration not including the second information.

13. The apparatus of claim 7, wherein, When the terminal device is not provided with the first information or when the first information indicates that there is an invalid time domain resource type, the SP-CSI configuration includes the second information; or For the SP-CSI configuration not including the second information: The terminal device determines the invalid time domain resource type and / or the valid time domain resource type based on the first reference PUSCH or the time domain resource indicated by the activation DCI, or the terminal device considers that the first time domain resource or the second time domain resource is the invalid time domain resource type.

14. The apparatus of claim 1, wherein, The PUSCH overlapping with the first time domain resource and the PUSCH overlapping with the second time domain resource correspond to the same starting RB and / or frequency hopping offset (FH offset), or correspond to different starting RB and / or frequency hopping offset.

15. The apparatus of claim 14, wherein, A first starting RB indicated by the DCI is applied for the PUSCH overlapping with the first time domain resource, and a second starting RB is applied for the PUSCH overlapping with the second time domain resource, the second starting RB being the same as the first starting RB or being offset from the first starting RB and / or being determined by the first starting RB and / or uplink BWP bandwidth and / or bandwidth of uplink available resources. The first RB offset is relative to the first starting RB indicated by the DCI, or the first RB offset is relative to the starting RB of the UL BWP where the PUSCH is located; the first RB offset is configured by higher layer signaling, or the first RB offset is indicated by the DCI.

16. The apparatus of claim 15, wherein, The DCI indicates the first starting RB based on the starting RB of the UL BWP where the PUSCH is located for the PUSCH overlapping with the first time domain resource; and / or The DCI (FDRA field of the DCI) indicates the first starting RB based on the starting RB of the first frequency domain resource or based on the RB determined by the first RB offset for the PUSCH overlapping with the second time domain resource.

17. The apparatus of claim 14, wherein, A first frequency hopping offset is applied for the PUSCH overlapping with the first time domain resource, and the first frequency hopping offset or a second frequency hopping offset or no frequency hopping offset is applied for the PUSCH overlapping with the second time domain resource.

18. The apparatus of claim 17, wherein, The third starting RB corresponding to the frequency hopping offset is determined according to the first starting RB and the bandwidth / size of the BWP for the PUSCH overlapping with the first time domain resource; The fourth starting RB corresponding to the frequency hopping offset is determined according to the second starting RB and the bandwidth / size of the first frequency domain resource for the PUSCH overlapping with the second time domain resource.

19. A CSI receiving apparatus, comprising: a transmitter that transmits a downlink control information (DCI) for activating a semi-persistent CSI triggering state; and a receiver that receives a semi-persistent CSI reporting on a PUSCH; wherein in the PUSCH: the PUSCH overlapping with a first time domain resource is not used for the semi-persistent CSI reporting, or the PUSCH overlapping with a second time domain resource is not used for the semi-persistent CSI reporting, or both the PUSCH overlapping with the first time domain resource and the PUSCH overlapping with the second time domain resource are used for the semi-persistent CSI reporting; the first time domain resource, a first frequency domain resource is used for uplink and a second frequency domain resource is used for downlink, and the second time domain resource is outside the first time domain resource.

20. A communication system, comprising: a network device that transmits a downlink control information (DCI) for activating a semi-persistent CSI triggering state; and receives a semi-persistent CSI reporting on a PUSCH; A terminal device receives a downlink control information (DCI) for activating a semi-persistent CSI triggering state; and performs semi-persistent CSI reporting on a PUSCH; wherein, in the PUSCH: PUSCHs overlapping with first time domain resources are not used for the semi-persistent CSI reporting, or PUSCHs overlapping with second time domain resources are not used for the semi-persistent CSI reporting, or both PUSCHs overlapping with the first time domain resources and PUSCHs overlapping with the second time domain resources are used for the semi-persistent CSI reporting; in the first time domain resources, a first frequency domain resource is used for uplink and a second frequency domain resource is used for downlink, and the second time domain resources are outside the first time domain resources.

Images