WO2024031696A1 - 信道状态信息的上报方法和装置 - Google Patents

信道状态信息的上报方法和装置 Download PDF

Info

Publication number
WO2024031696A1
WO2024031696A1 PCT/CN2022/112293 CN2022112293W WO2024031696A1 WO 2024031696 A1 WO2024031696 A1 WO 2024031696A1 CN 2022112293 W CN2022112293 W CN 2022112293W WO 2024031696 A1 WO2024031696 A1 WO 2024031696A1
Authority
WO
WIPO (PCT)
Prior art keywords
dci format
cell
cells
csi
uplink carrier
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/CN2022/112293
Other languages
English (en)
French (fr)
Inventor
蒋琴艳
张磊
王昕�
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Fujitsu Ltd
Original Assignee
Fujitsu Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Fujitsu Ltd filed Critical Fujitsu Ltd
Priority to PCT/CN2022/112293 priority Critical patent/WO2024031696A1/zh
Priority to KR1020257003933A priority patent/KR20250036176A/ko
Priority to JP2025507085A priority patent/JP2025526627A/ja
Priority to EP22954648.6A priority patent/EP4572258A4/en
Priority to CN202280098013.XA priority patent/CN119547391A/zh
Publication of WO2024031696A1 publication Critical patent/WO2024031696A1/zh
Priority to US19/029,707 priority patent/US20250175840A1/en
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/0001—Systems modifying transmission characteristics according to link quality, e.g. power backoff
    • H04L1/0023—Systems modifying transmission characteristics according to link quality, e.g. power backoff characterised by the signalling
    • H04L1/0026—Transmission of channel quality indication
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04B—TRANSMISSION
    • H04B7/00—Radio transmission systems, i.e. using radiation field
    • H04B7/02—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas
    • H04B7/04—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas
    • H04B7/06—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas at the transmitting station
    • H04B7/0613—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas at the transmitting station using simultaneous transmission
    • H04B7/0615—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas at the transmitting station using simultaneous transmission of weighted versions of same signal
    • H04B7/0619—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas at the transmitting station using simultaneous transmission of weighted versions of same signal using feedback from receiving side
    • H04B7/0621—Feedback content
    • H04B7/0626—Channel coefficients, e.g. channel state information [CSI]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/0001—Systems modifying transmission characteristics according to link quality, e.g. power backoff
    • H04L1/0023—Systems modifying transmission characteristics according to link quality, e.g. power backoff characterised by the signalling
    • H04L1/0027—Scheduling of signalling, e.g. occurrence thereof
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1822—Automatic repetition systems, e.g. Van Duuren systems involving configuration of automatic repeat request [ARQ] with parallel processes
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/0001—Arrangements for dividing the transmission path
    • H04L5/0003—Two-dimensional division
    • H04L5/0005—Time-frequency
    • H04L5/0007—Time-frequency the frequencies being orthogonal, e.g. OFDM(A) or DMT
    • H04L5/001—Time-frequency the frequencies being orthogonal, e.g. OFDM(A) or DMT the frequencies being arranged in component carriers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0048—Allocation of pilot signals, i.e. of signals known to the receiver
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0048—Allocation of pilot signals, i.e. of signals known to the receiver
    • H04L5/005—Allocation of pilot signals, i.e. of signals known to the receiver of common pilots, i.e. pilots destined for multiple users or terminals
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053—Allocation of signalling, i.e. of overhead other than pilot signals
    • H04L5/0057—Physical resource allocation for CQI
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/10—Scheduling measurement reports ; Arrangements for measurement reports
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation
    • H04W72/044—Wireless resource allocation based on the type of the allocated resource
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/12—Wireless traffic scheduling
    • H04W72/1263—Mapping of traffic onto schedule, e.g. scheduled allocation or multiplexing of flows
    • H04W72/1268—Mapping of traffic onto schedule, e.g. scheduled allocation or multiplexing of flows of uplink data flows
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/21—Control channels or signalling for resource management in the uplink direction of a wireless link, i.e. towards the network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/004—Arrangements for detecting or preventing errors in the information received by using forward error control
    • H04L1/0056—Systems characterized by the type of code used
    • H04L1/0061—Error detection codes
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1812—Hybrid protocols; Hybrid automatic repeat request [HARQ]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053—Allocation of signalling, i.e. of overhead other than pilot signals
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation
    • H04W72/044—Wireless resource allocation based on the type of the allocated resource
    • H04W72/0453—Resources in frequency domain, e.g. a carrier in FDMA
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/23—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal
    • H04W72/232—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal the control data signalling from the physical layer, e.g. DCI signalling

Definitions

  • the embodiments of this application relate to the field of communication technology.
  • Physical Downlink Shared Channel is a type of physical downlink channel in wireless communication systems and is used to carry downlink data.
  • Physical Uplink Shared Channel (PUSCH) is a type of physical uplink channel in wireless communication systems and is used to carry uplink data.
  • PDSCH and PUSCH can be scheduled through downlink control information (DCI).
  • DCI downlink control information
  • NR new radio
  • DCI formats formats for scheduling PDSCH or PUSCH are defined. Different DCI formats include different specific information and/or sizes to meet different requirements. scheduling needs.
  • DCI format 0_1 and DCI format 0_2 can be used to trigger/activate/deactivate aperiodic CSI report and PUSCH-based SP CSI report, and both DCI format 0_1 and DCI format 0_2 can only schedule one cell. (or uplink carrier) PUSCH.
  • DCI format 0_1 and DCI format 0_2 can only schedule one cell. (or uplink carrier) PUSCH.
  • This DCI that supports scheduling multiple cells may be a new DCI format (such as DCI format 0_3, but not limited to this) or an enhancement to an existing DCI format (such as DCI format 0_1 and DCI format 0_2).
  • a new DCI format such as DCI format 0_3, but not limited to this
  • an enhancement to an existing DCI format such as DCI format 0_1 and DCI format 0_2.
  • embodiments of the present application provide a channel state information reporting method and device to support aperiodic CSI reporting when the DCI format can schedule PUSCH of multiple cells (or uplink carriers) and based on Semi-persistent CSI reporting by PUSCH.
  • an aperiodic CSI reporting device includes:
  • a receiving unit that receives a DCI format used to schedule PUSCH on one or more cells and/or uplink carriers, and the DCI format requests or triggers aperiodic CSI reporting;
  • a sending unit sends a CSI report.
  • a device for receiving a CSI report includes:
  • a sending unit that sends a DCI format used to schedule PUSCH on one or more cells and/or uplink carriers, and the DCI format requests or triggers aperiodic CSI reporting;
  • a receiving unit receives the CSI report.
  • a semi-persistent CSI reporting device where the device includes:
  • a receiving unit that receives a DCI format used to schedule PUSCH on one or more cells and/or uplink carriers, and the DCI format triggers or activates semi-persistent CSI reporting;
  • a sending unit sends a CSI report.
  • a device for receiving a CSI report includes:
  • a sending unit that sends a DCI format for scheduling PUSCH on one or more cells and/or uplink carriers, and the DCI format triggers or activates semi-persistent CSI reporting;
  • a receiving unit receives the CSI report.
  • a device for releasing or deactivating semi-persistent CSI reporting includes:
  • a receiving unit that receives a DCI format used to schedule PUSCH on one or more cells and/or uplink carriers, and the DCI format releases or deactivates semi-persistent CSI reporting;
  • a processing unit that deactivates semi-persistent CSI reporting deactivates
  • a device for releasing or deactivating semi-persistent CSI reporting includes:
  • a sending unit that sends a DCI format for scheduling PUSCH on one or more cells and/or uplink carriers, and the DCI format releases or deactivates semi-persistent CSI reporting.
  • One of the beneficial effects of the embodiments of the present application is that according to the embodiments of the present application, aperiodic CSI reporting and PUSCH-based semi-persistent CSI reporting are realized when the DCI format can schedule PUSCH of multiple cells.
  • Figure 1 is a schematic diagram of a communication system according to an embodiment of the present application.
  • Figure 2 is a schematic diagram of the timing relationship of aperiodic CSI reporting
  • Figure 3 is a schematic diagram of the timing relationship of SP CSI reporting based on PUSCH
  • Figure 4 is a schematic diagram of the aperiodic CSI reporting method according to an embodiment of the present application.
  • Figures 5 to 12 are schematic diagrams of examples of aperiodic CSI reporting
  • Figure 13 is a schematic diagram of a CSI report receiving method according to an embodiment of the present application.
  • Figure 14 is a schematic diagram of the semi-persistent CSI reporting method according to an embodiment of the present application.
  • Figures 15 to 22 are schematic diagrams of examples of semi-persistent CSI reporting
  • Figure 23 is a schematic diagram of a CSI report receiving method according to an embodiment of the present application.
  • Figure 24 is a schematic diagram of a method for releasing or deactivating semi-persistent CSI reporting according to an embodiment of the present application
  • Figure 25 is a schematic diagram of a method for releasing or deactivating semi-persistent CSI reporting according to an embodiment of the present application
  • Figure 26 is a schematic diagram of an aperiodic CSI reporting device according to an embodiment of the present application.
  • Figure 27 is a schematic diagram of a CSI report receiving device according to an embodiment of the present application.
  • Figure 28 is a schematic diagram of a semi-persistent CSI reporting device according to an embodiment of the present application.
  • Figure 29 is a schematic diagram of a CSI report receiving device according to an embodiment of the present application.
  • Figure 30 is a schematic diagram of a device for releasing or deactivating semi-persistent CSI reporting according to an embodiment of the present application
  • Figure 31 is a schematic diagram of a device for releasing or deactivating semi-persistent CSI reporting according to an embodiment of the present application
  • Figure 32 is a schematic structural diagram of a terminal device according to an embodiment of the present application.
  • Figure 33 is a schematic structural diagram of a network device according to an embodiment of the present application.
  • the terms “first”, “second”, etc. are used to distinguish different elements from the title, but do not indicate the spatial arrangement or temporal order of these elements, and these elements should not be used by these terms. restricted.
  • the term “and/or” includes any and all combinations of one or more of the associated listed terms.
  • the terms “comprises,” “includes,” “having” and the like refer to the presence of stated features, elements, elements or components but do not exclude the presence or addition of one or more other features, elements, elements or components.
  • the term “communication network” or “wireless communication network” may refer to a network that complies with any of the following communication standards, such as Long Term Evolution (LTE, Long Term Evolution), Long Term Evolution Enhanced (LTE-A, LTE- Advanced), Wideband Code Division Multiple Access (WCDMA, Wideband Code Division Multiple Access), High-speed Packet Access (HSPA, High-Speed Packet Access), 5G (5Generation) New Wireless (NR, New Radio), etc.
  • LTE Long Term Evolution
  • LTE-A Long Term Evolution Enhanced
  • WCDMA Wideband Code Division Multiple Access
  • High-speed Packet Access High-speed Packet Access
  • the communication between devices in the communication system can be carried out according to the communication protocol at any stage.
  • it can include but is not limited to the following communication protocols: 1G, 2G, 2.5G, 2.75G, 3G, 4G, 4.5G and 5G new wireless ( NR, New Radio), etc., and/or other communication protocols currently known or to be developed in the future.
  • Network device refers to a device in a communication system that connects a terminal device to a communication network and provides services to the terminal device.
  • Network equipment may include but is not limited to the following equipment: base station (BS, Base Station), access point (AP, Access Point), transmission and reception point (TRP, Transmission Reception Point), broadcast transmitter, mobile management entity (MME, Mobile Management Entity), gateway, server, wireless network controller (RNC, Radio Network Controller), base station controller (BSC, Base Station Controller), etc.
  • the base station may include but is not limited to: Node B (NodeB or NB), evolved Node B (eNodeB or eNB) and 5G base station (gNB), etc.
  • it may also include remote radio head (RRH, Remote Radio Head) , Remote Radio Unit (RRU, Remote Radio Unit), relay or low-power node (such as femeto, pico, etc.).
  • RRH Remote Radio Head
  • RRU Remote Radio Unit
  • relay or low-power node such as femeto, pico, etc.
  • base station may include some or all of their functions, each of which may provide communications coverage to a specific geographic area.
  • the term "cell” may refer to a base station and/or its coverage area, depending on the context in which the term is used.
  • the term "user equipment” (UE, User Equipment) or “terminal equipment” (TE, Terminal Equipment or Terminal Device) refers to a device that accesses a communication network through a network device and receives network services.
  • Terminal equipment can be fixed or mobile, and can also be called mobile station (MS, Mobile Station), terminal, subscriber station (SS, Subscriber Station), access terminal (AT, Access Terminal), station, etc.
  • the terminal equipment may include but is not limited to the following equipment: cellular phone (Cellular Phone), personal digital assistant (PDA, Personal Digital Assistant), wireless modem, wireless communication equipment, handheld device, machine-type communication equipment, laptop computer, Cordless phones, smartphones, smart watches, digital cameras, and more.
  • cellular phone Cellular Phone
  • PDA Personal Digital Assistant
  • wireless modem wireless communication equipment
  • handheld device machine-type communication equipment
  • laptop computer Cordless phones
  • Cordless phones smartphones, smart watches, digital cameras, and more.
  • the terminal device can also be a machine or device for monitoring or measuring.
  • the terminal device can include but is not limited to: Machine Type Communication (MTC) terminals, Vehicle communication terminals, device-to-device (D2D, Device to Device) terminals, machine-to-machine (M2M, Machine to Machine) terminals, etc.
  • MTC Machine Type Communication
  • D2D Device to Device
  • M2M Machine to Machine
  • network side refers to one side of the network, which may be a certain base station or may include one or more network devices as above.
  • user side or “terminal side” or “terminal device side” refers to the side of the user or terminal, which may be a certain UE or may include one or more terminal devices as above.
  • device can refer to network equipment or terminal equipment.
  • Figure 1 is a schematic diagram of a communication system according to an embodiment of the present application, schematically illustrating a terminal device and a network device as an example.
  • the communication system 100 may include a network device 101 and a terminal device 102.
  • FIG. 1 only takes one network device and one terminal device as an example for illustration, but the embodiment of the present application is not limited thereto.
  • eMBB enhanced mobile broadband
  • mMTC massive machine type communication
  • URLLC Ultra-Reliable and Low -Latency Communication
  • the overall process of UE reporting CSI includes the following steps:
  • gNB sends CSI-RS and/or SSB
  • the UE measures the DMRS of CSI-RS and/or PBCH (in SSB), including channel state measurement, interference measurement, L1-RSRP measurement, etc., and then the UE reports the measurement results to the gNB;
  • the gNB performs beam management, scheduling, etc. based on the CSI measurement results reported by the UE.
  • the overall CSI framework includes CSI resource settings and CSI reporting settings.
  • CSI resource settings define the structure of CSI-RS, occupied bandwidth, time domain characteristics (periodic, semi-persistent, aperiodic), etc.
  • the CSI reporting settings define the CSI resource settings associated with the measurement report, the time domain characteristics of the report (periodic, semi-persistent, aperiodic), the number of reports, the frequency domain configuration of the report, etc.
  • CSI reporting types include periodic CSI reporting, aperiodic CSI reporting, semi-persistent (SP) CSI reporting on PUCCH, and semi-persistent CSI reporting on PUSCH.
  • SP semi-persistent
  • aperiodic CSI reporting and SP CSI reporting on PUSCH are triggered or activated by DCI format and CSI reports are sent on PUSCH.
  • embodiments of the present application provide a method and device for reporting channel state information.
  • DCI format 0_X refers to the DCI format used to support PUSCH scheduling of multiple cells (or uplink carriers) through one DCI. There is no restriction on the name of the DCI format. It can be DCI format 0_1 , and/or DCI format 0_2, and/or DCI format 0_3, etc.
  • the network device configures the cells that DCI format 0_X can schedule through high-level signaling or parameters.
  • DCI format 0_X includes fields indicating cells and/or uplink carriers. According to the configuration of high-layer signaling or parameters, the value of this field corresponds to one or more cells and/or uplink carriers. Therefore, when this field indicates multiple cells and/or uplink carriers, scheduling of multiple cells and/or uplink carriers through one DCI can be implemented.
  • DCI format 0_X includes one or more fields for indicating cells and/or uplink carriers.
  • a cell can be configured with 1 uplink carrier, namely (N)UL ((normal)UL), or 2 uplink carriers, namely (N)UL and SUL (supplementary UL).
  • 1 uplink carrier namely (N)UL ((normal)UL)
  • 2 uplink carriers namely (N)UL and SUL (supplementary UL).
  • DCI format 0_X includes both a field for indicating a cell and a field for indicating an uplink carrier. That is to say, the above-mentioned fields used to indicate the cell and/or the uplink carrier may include a field used to indicate the cell and a field used to indicate the uplink carrier within the cell. For example, if one or more cells in the cells that DCI format 0_X can schedule include two uplink carriers (such as (N)UL and SUL), DCI format 0_X may include one or more fields used to indicate the cells ( For example, carrier indicator) and one or more fields used to indicate the uplink carrier in the cell (for example, UL-SUL indicator) to indicate which uplink carrier the scheduled PUSCH is on. Wherein, when multiple fields for indicating uplink carriers within a cell are included, different fields for indicating uplink carriers within a cell correspond to different cells or different cell sets/cell groups.
  • DCI format 0_X only includes a field indicating the cell and/or uplink carrier. For example, if the cells in the cells that can be scheduled by DCI format 0_X only include one uplink carrier, DCI format 0_X can only include the field used to indicate the cell, or in other words, only include the field used to indicate the uplink carrier. Because in this case, indicating a cell is equivalent to indicating the uplink carrier of the cell.
  • scheduling the cell and/or the uplink carrier is equivalent to “scheduling the uplink transmission (eg, PUSCH) on the cell and/or the uplink carrier.”
  • multiple means more than one, or two or more.
  • DCI format 0_X is scrambled by a certain RNTI
  • the CRC (cyclic redundancy check) check bit of the DCI format is scrambled by the RNTI.
  • the DCI format "used to schedule PUSCH on one or more cells and/or uplink carriers” means: the DCI format can at least/can/have the ability to schedule more than one time/simultaneously. PUSCH on cells and/or uplink carriers, the more than one cell and/or uplink carrier respectively have one or more than one scheduled PUSCH; and, the DCI format can/can/has the ability to schedule one cell and/or at a time PUSCH on the uplink carrier, there is one or more scheduled PUSCH on the cell and/or uplink carrier; or it means: the DCI format can at least/can/have the ability to schedule more than one cell and/or at the same time/at the same time PUSCH on the uplink carrier, there are one or more scheduled PUSCH on the more than one cell and/or uplink carrier; and, the DCI format cannot/cannot/has no ability to schedule only one cell and/or uplink at a time PUSCH on the carrier.
  • the embodiment of this application provides an aperiodic CSI reporting method, which is applied on the terminal device side.
  • Figure 4 is a schematic diagram of an aperiodic CSI reporting method according to an embodiment of the present application. As shown in Figure 4, the method includes:
  • the terminal device receives a DCI format used to schedule PUSCH on one or more cells and/or uplink carriers, and the DCI format requests or triggers aperiodic CSI reporting;
  • the terminal device sends a CSI report.
  • aperiodic CSI reporting is achieved when the DCI format can schedule PUSCH of multiple cells.
  • aperiodic CSI reporting based on DCI format 0_X includes the following steps:
  • the base station configures one or more trigger states (trigger state list) through high-layer signaling or parameters (such as CSI-AperiodicTriggerStateList), and each trigger state corresponds to or is associated with one or more CSI report configurations;
  • the UE listens to DCI format 0_X and determines which trigger state (CSI aperiodic trigger state) is triggered based on the value of the CSI request field.
  • possible CSI-RS configurations for aperiodic CSI reporting include aperiodic CSI-RS, periodic CSI-RS, and semi-persistent CSI-RS.
  • the timing relationship of aperiodic CSI reporting is shown in Figure 2, for example. In Figure 2, the reference signal used for measurement is omitted.
  • the triggering state refers to the CSI aperiodic triggering state
  • the CSI reporting refers to the aperiodic CSI reporting.
  • the high-level parameters used to configure the trigger status list are specific to DCI format 0_X, or are shared by DCI format 0_X and another DCI format. Specific means, only for DCI format 0_X. Sharing means that when another DCI format is configured to trigger aperiodic CSI reporting, for the other DCI format, DCI format 0_X and the other DCI format may be targeted at the same time or not at the same time.
  • this high-level parameter is both for DCI format 0_X, Also for this other DCI format.
  • the two DCI formats cannot be configured to both need to be monitored, or both cannot be configured to need to be monitored and both are used to trigger aperiodic CSI reporting.
  • this high-level parameter is only for DCI under specific DCI format configuration conditions. format 0_X or the other DCI format, but not both DCI format 0_X and the other DCI format.
  • the above-mentioned DCI format schedules PUSCH on a cell and/or uplink carrier, and the terminal device sends the above-mentioned CSI report on the cell and/or uplink carrier.
  • the DCI format when the above DCI format requests or triggers aperiodic CSI reporting, the DCI format only schedules PUSCH on one cell and/or uplink carrier. Then the terminal equipment can send the CSI report on this cell and/or uplink carrier.
  • existing methods can be reused to the maximum extent, complexity can be reduced, and equipment upgrade costs can be reduced.
  • the DCI format includes a field (or information field) used to request or trigger CSI reporting, such as a CSI request field, and the value of this field corresponds to the CSI aperiodic triggering state.
  • the DCI format only schedules PUSCH on one cell and/or uplink carrier, and the terminal device sends the corresponding CSI report on the PUSCH on the one cell and/or uplink carrier.
  • the length of the CSI request field is N TS (that is, including N TS bits), which is configured by the network device through high-level parameters (such as reportTriggerSize). It can indicate at most aperiodic trigger state.
  • N TS that is, including N TS bits
  • the CSI request field directly indicates which state is requested.
  • the network device also selects no more than MAC CE through MAC CE (such as CSI aperiodic trigger state subset selection MAC CE).
  • the CSI request field indicates which state is requested. There is a certain delay between the terminal device receiving the above MAC CE command and the command taking effect. If the HARQ-ACK corresponding to the PDSCH carrying the MAC CE is sent on time slot n, the CSI aperiodic trigger state selection takes effect.
  • the gap is
  • the length of the above CSI request field is configured by a high-level parameter, which may be specific to DCI format 0_X, or shared by DCI format 0_X and another DCI format. Specific means, only for DCI format 0_X. Sharing means that when the monitoring of another DCI format is configured to trigger CSI reporting, for the other DCI format, DCI format 0_X and the other DCI format may be targeted at the same time or not at the same time.
  • the high-level parameters are not only for DCI format 0_X, but also for the other DCI format.
  • a DCI format Not at the same time means that the two DCI formats cannot be configured to both need to be monitored, or both cannot be configured to need to be monitored and both are used to trigger CSI reporting.
  • this high-level parameter is only for DCI format 0_X in the specific DCI format configuration situation. or the other DCI format, but not both DCI format 0_X and the other DCI format.
  • the length of the above CSI request field is not determined by high-layer parameters, but is determined by the terminal device according to the number of trigger states in the configured corresponding trigger state list.
  • the above-mentioned DCI format includes a field for indicating a cell and/or an uplink carrier, and the field indicates a cell and/or an uplink carrier; the terminal device transmits on the cell and/or uplink carrier indicated by the field.
  • CSI report includes a field for indicating a cell and/or an uplink carrier, and the field indicates a cell and/or an uplink carrier; the terminal device transmits on the cell and/or uplink carrier indicated by the field.
  • DCI format 0_X includes fields used to indicate cells and/or uplink carriers, such as a carrier indication field, which may indicate one or more cells and/or uplink carriers.
  • a carrier indication field which may indicate one or more cells and/or uplink carriers.
  • Figure 5 is a schematic diagram of an example of aperiodic CSI reporting.
  • the CRC of DCI format 0_X is scrambled by C-RNTI or MCS-C-RNTI
  • the CSI request field indicates the triggered status
  • the carrier indication field indicates the cell and/or uplink carrier
  • the left side of Figure 5 illustrates the case where the indicated cell is Pcell
  • the right side of Figure 5 illustrates the case where the indicated cell is Scell.
  • the terminal device can send a CSI report on the cell and/or uplink carrier indicated by the carrier indication field.
  • the PUSCH may or may not carry UL-SCH data.
  • Figure 6 is a schematic diagram of another example of aperiodic CSI reporting.
  • the CRC of DCI format 0_X is scrambled by C-RNTI or MCS-C-RNTI
  • the CSI request field indicates the triggered status
  • the carrier indication field indicates the cell and/or uplink carrier.
  • the left side of Figure 6 illustrates the case where the indicated cell is Pcell
  • the right side of Figure 6 illustrates the case where the indicated cell is Scell.
  • the terminal device can send a CSI report on the cell and/or uplink carrier indicated by the carrier indication field.
  • the PUSCH may or may not carry UL-SCH data.
  • the DCI format 0_X schedules two PUSCHs.
  • the terminal device sends the CSI report on a cell and/or an uplink carrier that is default or configured by signaling for sending the CSI report.
  • the DCI format includes a field used to indicate a cell and/or an uplink carrier, and this field does not indicate a cell and/or an uplink carrier.
  • DCI format 0_X includes fields used to indicate scheduled cells and/or uplink carriers, such as a carrier indication field, which may indicate one or more cells and/or uplink carriers.
  • a carrier indication field which may indicate one or more cells and/or uplink carriers.
  • this field does not indicate the cell and/or uplink carrier.
  • the bits of this field are set to a specific value, and the specific value does not correspond to any cell and/or uplink carrier.
  • the terminal equipment sends the CSI report in the cell and/or uplink carrier configured by default or by signaling (for example, RRC and/or MAC CE and/or DCI, etc.) for sending the CSI report.
  • Figure 7 is a schematic diagram of an example of aperiodic CSI reporting.
  • the CRC of DCI format 0_X is scrambled by C-RNTI or MCS-C-RNTI
  • the CSI request field indicates the triggered status
  • the carrier indication field does not indicate the cell and/or uplink carrier.
  • the left side of Figure 7 illustrates the case where the indicated cell is Pcell
  • the right side of Figure 7 illustrates the case where the indicated cell is Scell.
  • the terminal device can send CSI on the default or signaling-configured cell and/or uplink carrier. Report.
  • the PUSCH may or may not carry UL-SCH data.
  • Figure 8 is a schematic diagram of another example of aperiodic CSI reporting.
  • the CRC of DCI format 0_X is scrambled by C-RNTI or MCS-C-RNTI
  • the CSI request field indicates the triggered status
  • the carrier indication field does not indicate the cell and/or uplink carrier.
  • the left side of Figure 8 illustrates the case where the indicated cell is Pcell
  • the right side of Figure 8 illustrates the case where the indicated cell is Scell.
  • the terminal device can transmit on the default or signaling-configured cell and/or uplink carrier.
  • the PUSCH may or may not carry UL-SCH data.
  • the DCI format 0_X schedules two PUSCHs.
  • the DCI format includes a field for indicating a cell and/or an uplink carrier, and the terminal device ignores this field.
  • DCI format 0_X includes fields used to indicate cells and/or uplink carriers, such as a carrier indication field, which may indicate one or more cells and/or uplink carriers.
  • a carrier indication field which may indicate one or more cells and/or uplink carriers.
  • the terminal equipment sends the CSI report in the cell and/or uplink carrier configured by default or by signaling (such as RRC and/or MAC CE and/or DCI, etc.) for sending the CSI report.
  • the DCI format includes a field for requesting or triggering CSI reporting, and the field for requesting or triggering CSI reporting is located before the field for indicating the cell and/or uplink carrier.
  • the DCI format does not include the above fields used to indicate cells and/or uplink carriers when requesting or triggering aperiodic CSI reporting.
  • the DCI format 0_X when DCI format 0_X does not request or trigger aperiodic CSI reporting, the DCI format 0_X includes a field used to indicate a cell and/or an uplink carrier, such as a carrier indication field, which may indicate one or more cells and/or uplink carrier.
  • the DCI format 0_X requests or triggers aperiodic CSI reporting, the DCI format 0_X does not include the carrier indication field.
  • the field used to request or trigger CSI reporting (CSI request field) precedes the field used to indicate the cell and/or uplink carrier (carrier indication field).
  • the terminal equipment sends the CSI report in the cell and/or uplink carrier configured by default or by signaling (such as RRC and/or MAC CE and/or DCI, etc.) for sending the CSI report.
  • the default cell for sending CSI reports may be Pcell (primary cell) or Pscell (primary and secondary cell) or PUCCH Scell (physical uplink control channel secondary cell). This application is not limited thereto.
  • the default uplink carrier is the uplink carrier of the cell; if the default cell includes more than one uplink carrier, such as NUL and SUL, which uplink carrier of the cell is used?
  • the carrier sending the CSI report is, for example, indicated by the DCI format 0_X field used to indicate the uplink carrier in the cell (such as UL-SUL indicator), or the CSI report is sent on the default uplink carrier of the cell, the default uplink carrier For example, it is NUL, SUL or a carrier configured with PUCCH in more than one uplink carrier.
  • the DCI format schedules PUSCH on one or more cells and/or uplink carriers; the terminal equipment in the above one or more cells and/or uplink carriers
  • the CSI report is sent on a cell and/or uplink carrier.
  • DCI format 0_X schedules PUSCH on one or more cells and/or uplink carriers when triggering aperiodic CSI reporting.
  • the terminal equipment is in one of the cells and/or Or the PUSCH on the uplink carrier sends a CSI report;
  • the terminal device uses the same method as the previous embodiment to send the CSI report.
  • the current method can be reused to a certain extent, and because the network device can schedule UL-SCH data transmission of multiple cells through the same DCI while triggering CSI reporting, the scheduling flexibility and data transmission throughput can be increased.
  • the DCI format may include a field (or information field) used to request or trigger CSI reporting, such as a CSI request field, and the value of this field corresponds to the CSI aperiodic triggering state.
  • the DCI schedules PUSCH on one or more cells and/or uplink carriers, and the terminal device sends a corresponding CSI report on the PUSCH of one cell and/or uplink carrier.
  • the length of this field may be configured by high-level parameters, or may be determined by the terminal device based on the number of trigger states in the configured trigger state list.
  • the high-level parameters can be specific to the DCI format, or they can be shared between the DCI format and other DCI formats. Since the CSI request field has been described in the previous embodiment, its content is merged with this and will not be described again here.
  • the above-mentioned one cell and/or uplink carrier is a default cell and/or uplink carrier configured by signaling for sending CSI reports. That is, the terminal device sends the CSI report in the cell and/or uplink carrier that is used to send the CSI report by default or configured by signaling.
  • the DCI format may also include a field for indicating a cell and/or an uplink carrier.
  • the above-mentioned default or signaling-configured cell and/or uplink carrier for sending CSI reports may be in this field. It may be within the range of one or more cells and/or uplink carriers indicated by this field, or it may not be within the range of one or more cells and/or uplink carriers indicated by this field.
  • DCI format 0_X includes fields used to indicate cells and/or uplink carriers, such as a carrier indication field, which may indicate one or more cells and/or uplink carriers.
  • a carrier indication field which may indicate one or more cells and/or uplink carriers.
  • the terminal device sends a CSI report on the PUSCH on one of the cells and/or uplink carriers.
  • One of the cells and/or uplink carriers is a default cell or an uplink carrier configured by signaling (such as RRC and/or MAC CE and/or DCI, etc.) for sending the CSI report.
  • Figure 9 is a schematic diagram of an example of aperiodic CSI reporting.
  • the CRC of DCI format 0_X is scrambled by C-RNTI or MCS-C-RNTI
  • the CSI request field indicates the triggered status
  • the carrier indication field indicates the cell and/or uplink carrier
  • Figure The left side of Figure 9 illustrates the situation where the indicated cells are Pcell and Scell.
  • the right side of Figure 9 illustrates the case where the indicated cells are two Scells.
  • the terminal equipment can be in the default or signaling-configured cell and/or uplink carrier.
  • the PUSCH may or may not carry UL-SCH data.
  • the DCI format 0_X is associated with two PUSCHs, one of which carries CSI reports and the other which does not carry CSI reports.
  • Figure 10 is a schematic diagram of another example of aperiodic CSI reporting.
  • the CRC of DCI format 0_X is scrambled by C-RNTI or MCS-C-RNTI
  • the CSI request field indicates the triggered status
  • the carrier indication field indicates the cell and/or uplink carrier
  • Figure The left side of Figure 10 illustrates the situation where the indicated cells are Pcell and Scell.
  • the right side of Figure 10 illustrates the case where the indicated cells are two Scells.
  • the terminal equipment can be in the default or signaling-configured cell and/or uplink carrier.
  • the PUSCH may or may not carry UL-SCH data.
  • the DCI format 0_X is associated with two PUSCHs, one of which carries CSI reports and the other which does not carry CSI reports.
  • the two PUSCHs are staggered in the time domain.
  • FIG. 9 and FIG. 10 the situation where one cell and/or uplink carrier has multiple PUSCHs is not shown, but the embodiment of the present application does not exclude this situation. That is, Figure 9 and Figure 10 only show that there is only one PUSCH on one cell and/or uplink carrier. In the embodiment of the present application, there may be other PUSCH on one cell and/or uplink carrier.
  • the default cell for sending CSI reports may be: the cell with the smallest serving cell identification number among the scheduled cells; and/or the first one in the scheduled PUSCH that satisfies the aperiodic CSI in the time domain.
  • the cell where the PUSCH that reports timing requirements is located; and/or the cell with the smallest serving cell identification number among the cells where the first PUSCH in the scheduled PUSCH that meets the aperiodic CSI reporting timing requirements in the time domain is located.
  • This application is not limited to this, and the default cell used to send CSI reports can also be other cells defined according to other rules.
  • the default cell used to send CSI reports may be Pcell or PScell or PUCCH Scell, and the present application is not limited thereto.
  • the terminal device sends the CSI report on the default PUCCH.
  • the DCI format may also include fields used to indicate cells and/or uplink carriers.
  • DCI format 0_X includes fields used to indicate cells and/or uplink carriers, such as a carrier indication field, which may indicate one or more cells and/or uplink carriers.
  • a carrier indication field which may indicate one or more cells and/or uplink carriers.
  • Figure 11 is a schematic diagram of an example of aperiodic CSI reporting.
  • the CRC of DCI format 0_X is scrambled by C-RNTI or MCS-C-RNTI
  • the CSI request field indicates the triggered status
  • the carrier indication field indicates the cell and/or uplink carrier
  • Figure The left side of Figure 11 shows the situation where the indicated cells are Pcell and Scell.
  • the right side of Figure 11 shows the situation where the indicated cells are two Scells.
  • the terminal equipment can send the CSI report on the default PUSCH.
  • the PUSCH may or may not carry UL-SCH data.
  • the DCI format 0_X is associated with two PUSCHs, one of which carries CSI reports and the other which does not carry CSI reports. Different from the example of Figure 9, in the example of Figure 11, the two PUSCHs are staggered in the time domain.
  • Figure 11 only shows that there is only one PUSCH on one cell and/or uplink carrier. In the embodiment of the present application, there may be other PUSCH on one cell and/or uplink carrier.
  • the default PUSCH may be: the PUSCH of the cell with the smallest serving cell identification number among the scheduled cells; and/or the first one in the time domain among the scheduled PUSCHs that satisfies the aperiodic CSI reporting timing requirements. PUSCH; and/or, the PUSCH of the cell with the smallest serving cell identification number among the cells where the first PUSCH in the scheduled PUSCH that meets the aperiodic CSI reporting timing requirements in the time domain is located.
  • the application is not limited to this, and the default PUSCH may also be other PUSCH defined according to other rules.
  • the cell where the default PUSCH is located may be Pcell or PScell or PUCCH Scell, and the present application is not limited thereto.
  • the DCI format schedules PUSCH on more than one cell and/or uplink carrier; the terminal equipment is configured on one or more of the above-mentioned more than one cell and/or uplink carrier.
  • the CSI report is sent on a cell and/or uplink carrier.
  • PUSCH is scheduled on one or more cells and/or uplink carriers.
  • the terminal equipment is in one or part of them or The PUSCH of all cells and/or uplink carriers sends CSI reports; when scheduling the PUSCH on one cell and/or uplink carrier, the terminal equipment uses the same method as the previous embodiment to send CSI reports.
  • the network device triggers the terminal device to send CSI reports in one, multiple or all cells and/or uplink carriers through the same DCI, and can schedule UL-SCH of multiple cells through the same DCI while triggering CSI reporting Data transmission, when the bandwidth of each carrier is small, can improve CSI feedback efficiency, while also increasing scheduling flexibility and data transmission throughput.
  • the DCI format may include a field used to indicate a cell and/or an uplink carrier, and the field indicates the above-mentioned more than one cell and/or uplink carrier.
  • DCI format 0_X includes fields used to indicate cells and/or uplink carriers, such as a carrier indication field, which may indicate one or more cells and/or uplink carriers.
  • a carrier indication field which may indicate one or more cells and/or uplink carriers.
  • the terminal device sends the CSI report on the PUSCH of more than one cell and/or uplink carrier.
  • the contents of CSI reports on different PUSCHs may be the same or different.
  • the above DCI format includes a field used to request or trigger CSI reporting.
  • the CSI reports on different PUSCHs are the same, and/or different PUSCHs are used to carry different triggering states corresponding to the fields associated with them.
  • CSI report, and/or different PUSCHs are respectively used to carry different parts of the CSI report.
  • DCI format 0_X includes a field used to request or trigger CSI, such as the CSI request field.
  • the CSI reports on different PUSCHs are the same (repeated), and/or, different PUSCHs are used to carry the trigger status corresponding to the field indicated. Different CSI reports (wherein one triggering state may correspond to one or more CSI reports), and/or different PUSCHs are used to carry different parts of the CSI reports (for example, carrying Part 1 and Part 2 respectively).
  • the above-mentioned DCI format includes multiple fields used to request or trigger CSI reporting, and different PUSCHs are used to carry CSI reports corresponding to triggering states associated with different fields used to request or trigger CSI reporting.
  • DCI format 0_X includes multiple fields used to request or trigger CSI, such as the CSI request field. Different fields correspond to different cells and/or uplink carriers. That is to say, different PUSCHs are used to carry different fields for requesting. Or the CSI report corresponding to the trigger status indicated by the CSI trigger field.
  • Figure 12 is a schematic diagram of an example of aperiodic CSI reporting.
  • the CRC of DCI format 0_X is scrambled by C-RNTI or MCS-C-RNTI, one or more CSI request fields indicate the triggered status, and the carrier indication field indicates the cell and/or Uplink carrier.
  • the left side of Figure 12 illustrates the situation where the indicated cells are Pcell and Scell.
  • the right side of Figure 12 illustrates the case where the indicated cells are two Scells.
  • the terminal device can send CSI on the two cells and/or the uplink carrier. report, and the contents of the CSI reports on the two cells and/or uplink carriers may be the same or different.
  • the PUSCH may or may not carry UL-SCH data.
  • the DCI format 0_X schedules two PUSCHs.
  • the CRC of the DCI format can be scrambled by C-RNTI or MCS-C-RNTI, and this application is not limited to this.
  • the terminal device may also receive configuration information for configuring the terminal device to monitor the DCI format in the UE-specific search space.
  • This application does not limit the specific configuration method. For the relevant content of the configuration information, you can refer to related technologies.
  • the terminal device may also receive configuration information for configuring whether the above-mentioned DCI format supports triggering CSI reporting or whether the above-mentioned DCI format is used to trigger CSI reporting.
  • This application does not limit the specific configuration method. For the relevant content of the configuration information, you can refer to related technologies.
  • the terminal device may also receive configuration information for configuring cells and/or uplink carriers that can be scheduled by the above DCI format.
  • This application does not limit the specific configuration method. For the relevant content of the configuration information, you can refer to related technologies.
  • the above-mentioned more than one uplink carriers may be in different cells respectively, or at least two of the above-mentioned more than one uplink carriers may be in different cells, and the present application is not limited thereto.
  • aperiodic CSI reporting is achieved when the DCI format can schedule PUSCH of multiple cells.
  • the embodiment of the present application provides a method for receiving a CSI report, which is applied to the network device side and is a process on the network device side corresponding to the method of the embodiment of the first aspect, in which the same content as that of the embodiment of the first aspect is no longer Repeat.
  • Figure 13 is a schematic diagram of a CSI report receiving method according to an embodiment of the present application. As shown in Figure 13, the method includes:
  • the network device sends a DCI format for scheduling PUSCH on one or more cells and/or uplink carriers.
  • the DCI format requests or triggers aperiodic CSI reporting;
  • the network device receives the CSI report.
  • aperiodic CSI reporting is achieved when the DCI format can schedule PUSCH of multiple cells.
  • the above DCI format schedules PUSCH on a cell and/or uplink carrier, and the network device receives the CSI report on the cell and/or uplink carrier.
  • the DCI format when the DCI format requests or triggers aperiodic CSI reporting, the DCI format only schedules PUSCH on one cell and/or uplink carrier.
  • the above-mentioned DCI format includes a field for indicating a cell and/or an uplink carrier, and the field indicates a cell and/or an uplink carrier; the network device receives CSI on the cell and/or uplink carrier indicated by the field. Report.
  • the network device receives the CSI report on a cell and/or an uplink carrier configured by default or configured by signaling for receiving the CSI report.
  • the above DCI format includes a field used to indicate a cell and/or an uplink carrier, and this field does not indicate a cell and/or an uplink carrier.
  • the above DCI format includes a field used to indicate a cell and/or an uplink carrier, and the terminal device ignores this field.
  • the above-mentioned DCI format includes a field for requesting or triggering CSI reporting, and the field for requesting or triggering CSI reporting is located before the field for indicating the cell and/or uplink carrier.
  • the above DCI format does not include fields used to indicate cells and/or uplink carriers when requesting or triggering aperiodic CSI reporting.
  • the above-mentioned default cell for receiving CSI reports is: Pcell or PScell or PUCCH Scell.
  • the above-mentioned DCI format schedules PUSCH on one or more cells and/or uplink carriers; the network device operates on one cell and/or uplink carrier in the one or more cells and/or uplink carriers. Receive the CSI report.
  • the DCI format may include a field used to request or trigger CSI reporting, and the value of this field corresponds to the CSI aperiodic triggering state.
  • the length of the above field may be configured by high-level parameters, or may be determined by the terminal device according to the number of trigger states in the configured trigger state list.
  • the aforementioned high-level parameters can be specific to the DCI format, or can be shared between the DCI format and other DCI formats.
  • the above-mentioned one cell and/or uplink carrier is a default cell and/or uplink carrier configured by signaling for sending CSI reports.
  • the default cell used for sending CSI reports may be at least one of the following:
  • the cell with the smallest serving cell identification number among the scheduled cells is the cell with the smallest serving cell identification number among the scheduled cells
  • the cell where the first PUSCH in the scheduled PUSCH that meets the aperiodic CSI reporting timing requirements in the time domain is located;
  • the cell with the smallest serving cell identification number among the cells where the first PUSCH in the scheduled PUSCH that meets the aperiodic CSI reporting timing requirements in the time domain is located.
  • the default cell used to send CSI reports may be: Pcell or PScell or PUCCH Scell.
  • the network device receives the CSI report on the default PUSCH.
  • the default PUSCH may be at least one of the following:
  • the PUSCH of the cell with the smallest serving cell identification number among the scheduled cells
  • the cell where the default PUSCH is located may be: Pcell or PScell or PUCCH Scell.
  • the above-mentioned DCI format includes fields used to indicate cells and/or uplink carriers.
  • the aforementioned default or signaling-configured cells and/or uplink carriers for sending CSI reports are within the range of one or more cells and/or uplink carriers indicated by the above field, or are not within the range of the above mentioned fields.
  • field indicates one or more cells and/or uplink carriers.
  • the above DCI format schedules PUSCH on more than one cell and/or uplink carrier; the network device operates on one or more than one cell and/or uplink carrier in the more than one cell and/or uplink carrier. Receive CSI reports on.
  • the above DCI format may include a field used to indicate a cell and/or an uplink carrier, and the field indicates the aforementioned more than one cell and/or uplink carrier.
  • the contents of CSI reports on different PUSCHs may be the same or different.
  • the above DCI format may include a field used to request or trigger CSI reporting.
  • the CSI reports on different PUSCHs are the same, and/or different PUSCHs are used to carry different triggering states associated with the field.
  • CSI report, and/or different PUSCHs are used to carry different parts of the CSI report.
  • the above DCI format may include multiple fields used to request or trigger CSI reporting, and different PUSCHs are used to carry CSI reports corresponding to triggering states associated with different fields used to request or trigger CSI reporting.
  • the CRC of the above DCI format may be scrambled by C-RNTI or scrambled by MCS-C-RNTI.
  • the network device may also send configuration information for configuring the terminal device to monitor the above-mentioned DCI format in the UE-specific search space.
  • the network device may also send configuration information for configuring whether the above-mentioned DCI format supports triggering CSI reporting or whether the above-mentioned DCI format is used to trigger CSI reporting.
  • the network device may also send configuration information for configuring cells and/or uplink carriers that can be scheduled by the DCI format.
  • the more than one uplink carriers may be of different cells respectively, or at least two of the more than one uplink carriers may be of different cells.
  • aperiodic CSI reporting is achieved when the DCI format can schedule PUSCH of multiple cells.
  • the embodiment of this application provides a semi-persistent CSI reporting method, which is applied on the terminal device side.
  • Figure 14 is a schematic diagram of a semi-persistent CSI reporting method according to an embodiment of the present application. As shown in Figure 14, the method includes:
  • the terminal device receives a DCI format used to schedule PUSCH on one or more cells and/or uplink carriers, and the DCI format triggers or activates semi-persistent CSI reporting;
  • the terminal device sends a CSI report.
  • semi-persistent CSI reporting is achieved when the DCI format can schedule PUSCH of multiple cells.
  • the base station configures the reporting period, time slot offset, etc. through high-level signaling or parameters, and triggers it through the DCI format scrambled by SP-CSI-RNTI.
  • SP CSI reporting based on DCI format 0_X includes the following steps:
  • the base station configures one or more trigger states (trigger state list) through high-layer signaling or parameters (such as CSI-SemiPersistentOnPUSCH-TriggerStateList).
  • Each trigger state corresponds to/is associated with one or more CSI report configurations;
  • the UE monitors the DCI format 0_X scrambled by SP-CSI-RNTI and determines which trigger state (SP-CSI trigger state) is triggered or activated based on the value of the CSI request field.
  • SP-CSI trigger state The value of the CSI request field equal to 0 corresponds to the first trigger state in the above list, the value of the CSI request field equal to 1 corresponds to the second trigger state in the above list, and so on.
  • the possible CSI-RS configurations reported by SP CSI include periodic CSI-RS, semi-persistent CSI-RS, etc.
  • the timing relationship of SP CSI reporting based on PUSCH is shown in Figure 3. In Figure 3, the reference signal used for measurement is omitted.
  • the high-level parameters used to configure the trigger status list are specific to DCI format 0_X, or are shared by DCI format 0_X and another DCI format. Specific means, only for DCI format 0_X. Sharing means that when the monitoring of another DCI format is configured to trigger SP-CSI to report DCI format, for the other DCI format, DCI format 0_X and the other DCI format may be targeted at the same time or not at the same time. At the same time, it means that when the monitoring DCI format 0_X (and DCI format 0_X is used to trigger SP-CSI reporting) and another DCI format used to trigger SP-CSI reporting, this high-level parameter is both for DCI format 0_X, Also for this other DCI format.
  • this high-level parameter is only for DCI in the specific DCI format configuration situation. format 0_X or the other DCI format, but not both DCI format 0_X and the other DCI format.
  • the triggering state refers to the semi-persistent CSI triggering state
  • the CSI reporting refers to the semi-persistent CSI reporting
  • the above-mentioned DCI format schedules PUSCH on a cell and/or uplink carrier, and the terminal device sends the above-mentioned CSI report on the cell and/or uplink carrier.
  • the DCI format when the above DCI format triggers or activates semi-persistent CSI reporting, the DCI format only schedules PUSCH on one cell and/or uplink carrier. Then the terminal equipment can send the CSI report on this cell and/or uplink carrier.
  • existing methods can be reused to the maximum extent, complexity can be reduced, and equipment upgrade costs can be reduced.
  • the DCI format includes a field (or information field) used to trigger or activate CSI reporting, such as a CSI request field, and the value of this field corresponds to the CSI trigger state.
  • the DCI format only schedules PUSCH on one cell and/or uplink carrier, and the terminal device sends the corresponding CSI report on the PUSCH on the one cell and/or uplink carrier.
  • the length of the CSI request field is N TS (that is, including N TS bits), which is configured by the network device through high-level parameters (such as reportTriggerSize). It can indicate at most a trigger state.
  • the CSI transmission status configured by the network device through the above-mentioned high-level signaling or parameters does not exceed In this case, the CSI request field directly indicates which state is requested.
  • the network device also selects no more than MAC CE through MAC CE (such as CSI trigger state subset selection MAC CE). CSI trigger state, and then the CSI request field indicates which state is requested. There is a certain delay between the terminal device receiving the above MAC CE command and the command taking effect. If the HARQ-ACK corresponding to the PDSCH carrying the MAC CE is sent on time slot n, the effective time slot selected by the CSI trigger state is
  • the length of the above CSI request field is configured by a high-level parameter, which may be specific to DCI format 0_X, or common to DCI format 0_X and another DCI format. Specific means, only for DCI format 0_X. Sharing means that when the monitoring of another DCI format is configured to trigger CSI reporting, for the other DCI format, DCI format 0_X and the other DCI format may be targeted at the same time or not at the same time.
  • the high-level parameters are not only for DCI format 0_X, but also for the other DCI format.
  • a DCI format Not at the same time means that the two DCI formats cannot be configured to both need to be monitored, or both cannot be configured to need to be monitored and both are used to trigger CSI reporting.
  • this high-level parameter is only for DCI format 0_X in the specific DCI format configuration situation. or the other DCI format, but not both DCI format 0_X and the other DCI format.
  • the length of the above CSI request field is not determined by high-layer parameters, but is determined by the terminal device according to the number of trigger states in the configured corresponding trigger state list.
  • the above-mentioned DCI format includes a field for indicating a cell and/or an uplink carrier, and the field indicates a cell and/or an uplink carrier; the terminal device transmits on the cell and/or uplink carrier indicated by the field.
  • CSI report includes a field for indicating a cell and/or an uplink carrier, and the field indicates a cell and/or an uplink carrier; the terminal device transmits on the cell and/or uplink carrier indicated by the field.
  • DCI format 0_X includes fields used to indicate cells and/or uplink carriers, such as a carrier indication field, which may indicate one or more cells and/or uplink carriers.
  • a carrier indication field which may indicate one or more cells and/or uplink carriers.
  • Figure 15 is a schematic diagram of an example of semi-persistent CSI reporting.
  • the CRC of DCI format 0_X is scrambled by SP-CSI-RNTI
  • the CSI request field indicates the trigger status
  • the carrier indication field indicates the cell and/or uplink carrier, left in Figure 15 This illustrates the case where the indicated cell is Pcell.
  • the right side of Figure 15 illustrates the case where the indicated cell is Scell.
  • the terminal device can send a CSI report on the cell and/or uplink carrier indicated by the carrier indication field.
  • the CSI reporting is semi-persistent.
  • the PUSCH may or may not carry UL-SCH data.
  • Figure 16 is a schematic diagram of another example of semi-persistent CSI reporting.
  • the CRC of DCI format 0_X is scrambled by SP-CSI-RNTI
  • the CSI request field indicates the trigger status
  • the carrier indication field indicates the cell and/or uplink carrier, left in Figure 16 It illustrates the case where the indicated cell is Pcell.
  • the right side of Figure 16 illustrates the case where the indicated cell is Scell.
  • the terminal device can send the CSI report on the cell and/or uplink carrier indicated by the carrier indication field.
  • the CSI reporting is semi-persistent.
  • the PUSCH may or may not carry UL-SCH data.
  • the DCI format 0_X schedules two PUSCHs.
  • the terminal device sends the CSI report on a cell and/or an uplink carrier that is default or configured by signaling for sending the CSI report.
  • the DCI format includes a field used to indicate a cell and/or an uplink carrier, and this field does not indicate a cell and/or an uplink carrier.
  • DCI format 0_X includes fields used to indicate scheduled cells and/or uplink carriers, such as a carrier indication field, which may indicate one or more cells and/or uplink carriers.
  • a carrier indication field which may indicate one or more cells and/or uplink carriers.
  • this field does not indicate the cell and/or uplink carrier.
  • the bits of this field are set to a specific value, and the specific value does not correspond to any cell and/or uplink carrier.
  • the terminal equipment sends the CSI report in the cell and/or uplink carrier configured by default or by signaling (for example, RRC and/or MAC CE and/or DCI, etc.) for sending the CSI report.
  • Figure 17 is a schematic diagram of an example of semi-persistent CSI reporting.
  • the CRC of DCI format 0_X is scrambled by SP-CSI-RNTI.
  • the CSI request field indicates the triggered status.
  • the carrier indication field does not indicate the cell and/or uplink carrier.
  • the left side of Figure 17 It illustrates the case where the indicated cell is Pcell.
  • the right side of Figure 17 illustrates the case where the indicated cell is Scell.
  • the terminal device can send the CSI report on the default or signaling-configured cell and/or uplink carrier.
  • the CSI reporting is semi-persistent.
  • the PUSCH may or may not carry UL-SCH data.
  • Figure 18 is a schematic diagram of another example of semi-persistent CSI reporting.
  • the CRC of DCI format 0_X is scrambled by SP-CSI-RNTI.
  • the CSI request field indicates the triggered status.
  • the carrier indication field does not indicate the cell and/or uplink carrier.
  • the left side of Figure 18 It illustrates the case where the indicated cell is Pcell.
  • the right side of Figure 18 illustrates the case where the indicated cell is Scell.
  • the terminal device can send the CSI report on the default or signaling-configured cell and/or uplink carrier.
  • the CSI reporting is semi-persistent.
  • the PUSCH may or may not carry UL-SCH data.
  • the DCI format 0_X schedules two PUSCHs.
  • the DCI format includes a field for indicating a cell and/or an uplink carrier, and the terminal device ignores this field.
  • DCI format 0_X includes fields used to indicate cells and/or uplink carriers, such as a carrier indication field, which may indicate one or more cells and/or uplink carriers.
  • a carrier indication field which may indicate one or more cells and/or uplink carriers.
  • the terminal device ignores this field.
  • the terminal equipment sends the CSI report in the cell and/or uplink carrier configured by default or by signaling (such as RRC and/or MAC CE and/or DCI, etc.) for sending the CSI report.
  • the DCI format includes a field for triggering or activating CSI reporting, and the field for triggering or activating CSI reporting is located before the field for indicating the cell and/or uplink carrier.
  • the DCI format does not include the above-mentioned fields used to indicate cells and/or uplink carriers when triggering or activating semi-persistent CSI reporting.
  • the DCI format 0_X when DCI format 0_X does not trigger or activate semi-persistent CSI reporting, the DCI format 0_X includes a field used to indicate a cell and/or an uplink carrier, such as a carrier indication field, which may indicate one or more cells and/or uplink carrier.
  • the DCI format 0_X triggers or activates semi-persistent CSI reporting, the DCI format 0_X does not include the carrier indication field.
  • the field used to trigger or activate CSI reporting (CSI request field) precedes the field used to indicate the cell and/or uplink carrier (carrier indication field).
  • the terminal equipment sends the CSI report in the cell and/or uplink carrier configured by default or by signaling (such as RRC and/or MAC CE and/or DCI, etc.) for sending the CSI report.
  • the default cell used to send CSI reports may be Pcell or Pscell or PUCCH Scell, and the present application is not limited thereto.
  • the default uplink carrier is the uplink carrier of the cell; if the default cell includes more than one uplink carrier, such as NUL and SUL, the default uplink carrier For example, it is NUL, SUL or a carrier configured with PUCCH in more than one uplink carrier.
  • the DCI format schedules PUSCH on one or more cells and/or uplink carriers; the terminal equipment in the above one or more cells and/or uplink carriers
  • the CSI report is sent on a cell and/or uplink carrier.
  • DCI format 0_X schedules PUSCH on one or more cells and/or uplink carriers when triggering or activating semi-persistent CSI reporting.
  • the terminal equipment is in one of the cells. and/or the PUSCH on the uplink carrier to send the CSI report; when scheduling a cell and/or the PUSCH on the uplink carrier, the terminal device uses the same method as the previous embodiment to send the CSI report.
  • the current method can be reused to a certain extent, and since the network device can trigger or activate semi-persistent CSI reporting, it can schedule UL-SCH data transmission of multiple cells through the same DCI, which can increase the flexibility of scheduling and data transmission. Transmission throughput.
  • the DCI format may include a field (or information field) used to trigger or activate CSI reporting, such as a CSI request field, and the value of this field corresponds to the CSI trigger state.
  • a field or information field
  • the DCI schedules PUSCH on one or more cells and/or uplink carriers, and the terminal device sends a corresponding CSI report on the PUSCH of one cell and/or uplink carrier.
  • the length of this field may be configured by high-level parameters, or may be determined by the terminal device based on the number of trigger states in the configured trigger state list.
  • the high-level parameters can be specific to the DCI format, or they can be shared between the DCI format and other DCI formats. Since the CSI request field has been described in the previous embodiment, its content is merged with this and will not be described again here.
  • the above-mentioned one cell and/or uplink carrier is a default cell and/or uplink carrier configured by signaling for sending CSI reports. That is, the terminal device sends the CSI report in the cell and/or uplink carrier that is used to send the CSI report by default or configured by signaling.
  • the DCI format may also include a field for indicating a cell and/or an uplink carrier.
  • the above-mentioned default or signaling-configured cell and/or uplink carrier for sending CSI reports may be in this field. It may be within the range of one or more cells and/or uplink carriers indicated by this field, or it may not be within the range of one or more cells and/or uplink carriers indicated by this field.
  • DCI format 0_X includes fields used to indicate cells and/or uplink carriers, such as a carrier indication field, which may indicate one or more cells and/or uplink carriers.
  • a carrier indication field which may indicate one or more cells and/or uplink carriers.
  • the terminal device sends a CSI report on the PUSCH on one of the cells and/or uplink carriers.
  • One of the cells and/or uplink carriers is a default cell or an uplink carrier configured by signaling (such as RRC and/or MAC CE and/or DCI, etc.) for sending the CSI report.
  • Figure 19 is a schematic diagram of an example of semi-persistent CSI reporting.
  • the CRC of DCI format 0_X is scrambled by SP-CSI-RNTI
  • the CSI request field indicates the trigger status
  • the carrier indication field indicates the cell and/or uplink carrier, as shown on the left in Figure 19
  • the indicated cells are Pcell and Scell.
  • the right side of Figure 19 illustrates the case where the indicated cells are two Scells.
  • the terminal device can send CSI reports on the default or signaling-configured cells and/or uplink carriers. .
  • the CSI reporting is semi-persistent.
  • the PUSCH may or may not carry UL-SCH data.
  • the DCI format 0_X is associated with two PUSCHs, one of which carries CSI reports and the other which does not carry CSI reports.
  • Figure 20 is a schematic diagram of another example of semi-persistent CSI reporting.
  • the CRC of DCI format 0_X is scrambled by SP-CSI-RNTI
  • the CSI request field indicates the trigger status
  • the carrier indication field indicates the cell and/or uplink carrier, as shown on the left in Figure 20
  • the indicated cells are Pcell and Scell.
  • the right side of Figure 20 illustrates the case where the indicated cells are two Scells.
  • the terminal device can send CSI reports on the default or signaling-configured cells and/or uplink carriers. .
  • the CSI reporting is semi-persistent.
  • the PUSCH may or may not carry UL-SCH data.
  • the DCI format 0_X is associated with two PUSCHs, one of which carries CSI reports and the other which does not carry CSI reports.
  • the two PUSCHs are staggered in the time domain.
  • FIG. 19 and FIG. 20 the situation where one cell and/or uplink carrier has multiple PUSCHs is not shown, but the embodiment of the present application does not exclude this situation. That is, Figure 19 and Figure 20 only show that there is only one PUSCH on one cell and/or uplink carrier. In the embodiment of the present application, there may be other PUSCH on one cell and/or uplink carrier.
  • the default cell for sending CSI reports may be: the cell with the smallest serving cell identification number among the scheduled cells; and/or the first one in the scheduled PUSCH that satisfies the semi-persistent CSI in the time domain.
  • the cell where the PUSCH that reports timing requirements is located; and/or the cell with the smallest serving cell identification number among the cells where the first PUSCH in the scheduled PUSCH that meets the semi-persistent CSI reporting timing requirements in the time domain is located.
  • This application is not limited to this, and the default cell used to send CSI reports can also be other cells defined according to other rules.
  • the default cell used to send CSI reports may be Pcell or PScell or PUCCH Scell, and the present application is not limited thereto.
  • the terminal device sends the CSI report on the default PUCCH.
  • the DCI format may also include fields used to indicate cells and/or uplink carriers.
  • DCI format 0_X includes fields used to indicate cells and/or uplink carriers, such as a carrier indication field, which may indicate one or more cells and/or uplink carriers.
  • a carrier indication field which may indicate one or more cells and/or uplink carriers.
  • Figure 21 is a schematic diagram of an example of semi-persistent CSI reporting.
  • the CRC of DCI format 0_X is scrambled by SP-CSI-RNTI
  • the CSI request field indicates the trigger status
  • the carrier indication field indicates the cell and/or uplink carrier
  • Figure 21 illustrates the situation where the indicated cells are Pcell and Scell.
  • the right side of Figure 21 illustrates the situation where the indicated cells are two Scells.
  • the terminal equipment can send the CSI report on the default PUSCH.
  • the CSI reporting is semi-persistent.
  • the PUSCH may or may not carry UL-SCH data.
  • the DCI format 0_X is associated with two PUSCHs, one of which carries CSI reports and the other which does not carry CSI reports.
  • the two PUSCHs are staggered in the time domain.
  • Figure 21 only shows that there is only one PUSCH on one cell and/or uplink carrier. In the embodiment of the present application, there may be other PUSCH on one cell and/or uplink carrier.
  • the default PUSCH may be: the PUSCH of the cell with the smallest serving cell identification number among the scheduled cells; and/or the first one in the time domain among the scheduled PUSCHs that meets the semi-persistent CSI reporting timing requirements. PUSCH; and/or, the PUSCH of the cell with the smallest serving cell identification number among the cells where the first PUSCH in the scheduled PUSCH that satisfies the semi-persistent CSI reporting timing requirements in the time domain is located.
  • the application is not limited to this, and the default PUSCH may also be other PUSCH defined according to other rules.
  • the cell where the default PUSCH is located may be Pcell or PScell or PUCCH Scell, and the present application is not limited thereto.
  • the DCI format schedules PUSCH on more than one cell and/or uplink carrier; the terminal equipment is configured on one or more of the above-mentioned more than one cell and/or uplink carrier.
  • the CSI report is sent on a cell and/or uplink carrier.
  • DCI format 0_X schedules PUSCH on one or more cells and/or uplink carriers when triggering or activating semi-persistent CSI reporting.
  • the terminal equipment is in one or The PUSCH on some or all cells and/or uplink carriers sends CSI reports; when scheduling the PUSCH on a cell and/or uplink carrier, the terminal equipment uses the same method as the previous embodiment to send CSI reports.
  • the network device triggers the terminal device to send CSI reports in one, multiple or all cells and/or uplink carriers through the same DCI, and can schedule UL-SCH of multiple cells through the same DCI while triggering CSI reporting Data transmission, when the bandwidth of each carrier is small, can improve CSI feedback efficiency, while also increasing scheduling flexibility and data transmission throughput.
  • the DCI format may include a field used to indicate a cell and/or an uplink carrier, and the field indicates the above-mentioned more than one cell and/or uplink carrier.
  • DCI format 0_X includes fields used to indicate cells and/or uplink carriers, such as a carrier indication field, which may indicate one or more cells and/or uplink carriers.
  • a carrier indication field which may indicate one or more cells and/or uplink carriers.
  • the terminal device sends the CSI report on the PUSCH of more than one cell and/or uplink carrier.
  • the contents of CSI reports on different PUSCHs may be the same or different.
  • the above DCI format includes a field used to trigger or activate CSI reporting.
  • the CSI reports on different PUSCHs are the same, and/or different PUSCHs are used to carry different triggering statuses associated with the field.
  • CSI report, and/or different PUSCHs are respectively used to carry different parts of the CSI report.
  • DCI format 0_X includes a field used to trigger or activate CSI, such as the CSI request field.
  • the CSI reports on different PUSCHs are the same (repeated), and/or different PUSCHs are used to carry the trigger status corresponding to the field indicated. Different CSI reports (wherein one triggering state may correspond to one or more CSI reports), and/or different PUSCHs are used to carry different parts of the CSI reports (for example, carrying Part 1 and Part 2 respectively).
  • the above-mentioned DCI format includes multiple fields used to trigger or activate CSI reporting, and different PUSCHs are used to carry CSI reports corresponding to triggering states associated with different fields used to trigger or activate CSI reporting.
  • DCI format 0_X includes multiple fields used to trigger or activate CSI, such as the CSI request field. Different fields correspond to different cells and/or uplink carriers. That is to say, different PUSCHs are used to carry different triggering fields. Or the CSI report corresponding to the trigger status indicated by the activated CSI field.
  • Figure 22 is a schematic diagram of an example of semi-persistent CSI reporting.
  • the CRC of DCI format 0_X is scrambled by SP-CSI-RNTI, one or more CSI request fields indicate the status of the trigger, and the carrier indication field indicates the cell and/or uplink carrier
  • Figure The left side of Figure 22 illustrates the situation where the indicated cells are Pcell and Scell
  • the right side of Figure 22 illustrates the case where the indicated cells are two Scells.
  • the terminal equipment can send CSI reports on the two cells and/or uplink carriers, and The contents of the CSI reports on the two cells and/or uplink carriers may be the same or different.
  • the PUSCH may or may not carry UL-SCH data.
  • the DCI format 0_X schedules two PUSCHs.
  • the SP-CSI reporting periods on different cells and/or uplink carriers are the same as an example. However, the application is not limited to this.
  • the SP-CSI reporting periods on different cells and/or uplink carriers can be the same. , can also be different.
  • the CRC of the DCI format can be scrambled by SP-CSI-RNTI, but this application is not limited to this.
  • the terminal device can also determine/validate the validity of the above-mentioned DCI format for semi-persistent CSI activation.
  • the terminal device is configured according to the field used to indicate the cell and/or the uplink carrier and/or the field used to indicate the HARQ (Hybrid Automatic Repeat Request) process ID and/or the field used to indicate the RV (The fields of the redundant version determine/validate the above validity.
  • HARQ Hybrid Automatic Repeat Request
  • the above-mentioned DCI format includes multiple fields used to indicate the HARQ process ID, and the terminal device determines/validates the above-mentioned validity based on part or all of the fields in the DCI format used to indicate the cell and/or uplink carrier.
  • the above-mentioned DCI format includes multiple fields used to indicate RV, and the terminal device determines/validates the above-mentioned validity based on some or all of the fields used to indicate RV in the DCI format.
  • the above-mentioned DCI format includes one or more fields used to indicate cells and/or uplink carriers, and the terminal equipment determines/validates (validates) based on part or all of the fields in the DCI format used for cells and/or uplink carriers. ) the validity of the above.
  • the above-mentioned embodiments for determining/validating the above-mentioned validity can be used alone or in combination, and are not limited in this application.
  • the terminal device ignores or discards the DCI format. In other words, if the DCI format is confirmed to be invalid, the terminal device assumes that the CRC of the DCI format does not match, or assumes that the CRC check failed.
  • the above fields in the valid DCI format should meet certain conditions.
  • the field used to indicate a cell and/or an uplink carrier should indicate a cell and/or an uplink carrier, and/or, the cell and/or the uplink carrier indicated by the field is a Pcell or a PScell or a PUCCH Scell.
  • this field should be a specific value, and the specific value does not correspond to any cell and/or uplink carrier.
  • the DCI format 0_X includes multiple fields used to indicate the HARQ process ID (such as the HARQ process number field) and/or multiple fields used to indicate the RV (such as the Redundancy version field), the multiple fields should meet the following condition.
  • the field used to indicate the HARQ process ID and/or the field used to indicate the RV corresponding to the cell and/or uplink carrier indicated by the field used to indicate the cell and/or the uplink carrier should meet the following conditions.
  • the terminal device ignores other fields used to indicate the HARQ process ID and/or fields used to indicate the RV.
  • the embodiment of the present application provides a method for receiving a CSI report, which is applied to the network device side and is a process on the network device side corresponding to the method of the embodiment of the third aspect, wherein the same content as that of the embodiment of the third aspect is no longer Repeat.
  • Figure 23 is a schematic diagram of a CSI report receiving method according to an embodiment of the present application. As shown in Figure 23, the method includes:
  • the network device sends a DCI format for scheduling PUSCH on one or more cells and/or uplink carriers.
  • the DCI format triggers or activates semi-persistent CSI reporting;
  • the network device receives the CSI report.
  • semi-persistent CSI reporting is achieved when the DCI format can schedule PUSCH of multiple cells.
  • the above DCI format schedules PUSCH on one cell and/or uplink carrier, and the network device receives the CSI report on the above one cell and/or uplink carrier.
  • the above DCI format when the above DCI format triggers or activates semi-persistent CSI reporting, the above DCI format only schedules PUSCH on one cell and/or uplink carrier.
  • the above-mentioned DCI format includes a field for indicating a cell and/or an uplink carrier, and the field indicates a cell and/or an uplink carrier; the network device receives CSI on the cell and/or uplink carrier indicated by the field. Report.
  • the network device receives the CSI report on a cell and/or an uplink carrier configured by default or configured by signaling for sending the CSI report.
  • the above DCI format includes a field used to indicate a cell and/or an uplink carrier, and this field does not indicate a cell and/or an uplink carrier.
  • the above DCI format includes a field used to indicate a cell and/or an uplink carrier, and the terminal device ignores this field.
  • the above DCI format includes a field for requesting or triggering CSI reporting, and the field for requesting or triggering CSI reporting is located before the field for indicating the cell and/or uplink carrier.
  • the above DCI format does not include fields used to indicate cells and/or uplink carriers when triggering or activating semi-persistent CSI reporting.
  • the above-mentioned default cell used for sending CSI reports may be: Pcell or PScell or PUCCH Scell.
  • the above-mentioned DCI format schedules PUSCH on one or more cells and/or uplink carriers; the network device is configured on one of the above-mentioned one or more cells and/or uplink carriers. Receive CSI reports on.
  • the DCI format may include a field used to request or trigger CSI reporting, and the value of this field corresponds to the CSI triggering state.
  • the length of the field may be configured by a high-level parameter, and the high-level parameter is specific to the above-mentioned DCI format, or the above-mentioned DCI format is shared with other DCI formats.
  • the length of this field may also be determined by the terminal device according to the number of trigger states in the configured trigger state list.
  • the above-mentioned one cell and/or uplink carrier is a default cell and/or an uplink carrier configured by signaling for sending CSI reports.
  • the default cell used to send CSI reports may be at least one of the following:
  • the cell with the smallest serving cell identification number among the scheduled cells is the cell with the smallest serving cell identification number among the scheduled cells
  • the cell where the first PUSCH in the scheduled PUSCH that meets the semi-persistent CSI reporting timing requirements in the time domain is located;
  • the cell with the smallest serving cell identification number among the cells where the first PUSCH in the scheduled PUSCH that satisfies the semi-persistent CSI reporting timing requirements in the time domain is located.
  • the default cell used to send CSI reports may be: Pcell or PScell or PUCCH Scell.
  • the network device receives the CSI report on the default PUSCH.
  • the default PUSCH can be at least one of the following:
  • the PUSCH of the cell with the smallest serving cell identification number among the scheduled cells
  • the cell where the default PUSCH is located may be: Pcell or PScell or PUCCH Scell.
  • the above-mentioned DCI format includes fields used to indicate cells and/or uplink carriers.
  • the above-mentioned default or signaling-configured cell and/or uplink carrier for sending CSI reports is within the range of one or more cells and/or uplink carriers indicated by the above-mentioned field, or is not within the range of the above-mentioned one or more cells and/or uplink carriers.
  • field indicates one or more cells and/or uplink carriers.
  • the above DCI format schedules PUSCH on more than one cell and/or uplink carrier; the network device operates on one or more than one cell and/or uplink carrier in the more than one cell and/or uplink carrier. Receive CSI reports on.
  • the above-mentioned DCI format may also include a field used to indicate a cell and/or an uplink carrier, and the field indicates the above-mentioned more than one cell and/or uplink carrier.
  • the contents of CSI reports on different PUSCHs may be the same or different.
  • the above DCI format may also include a field used to trigger or activate CSI reporting.
  • the CSI reports on different PUSCHs are the same, and/or different PUSCHs are used to carry the corresponding trigger status associated with the field. Different CSI reports and/or different PUSCHs are respectively used to carry different parts of the CSI reports.
  • the above DCI format may also include multiple fields used to trigger or activate CSI reporting, and different PUSCHs are used to carry CSI reports corresponding to the triggering status associated with different fields used to request or trigger CSI reporting.
  • the CRC of the above DCI format may be scrambled by SP-CSI-RNTI.
  • the embodiment of the present application provides a method for releasing or deactivating semi-persistent CSI reporting, which is applied on the terminal device side.
  • Figure 24 is a schematic diagram of a method for releasing or deactivating semi-persistent CSI reporting according to an embodiment of the present application. As shown in Figure 24, the method includes:
  • the terminal equipment receives a DCI format used to schedule PUSCH on one or more cells and/or uplink carriers, and the DCI format releases or deactivates semi-persistent CSI reporting;
  • the terminal device deactivates semi-persistent CSI reporting.
  • the release or deactivation of semi-persistent CSI reporting is achieved when the DCI format can schedule PUSCH of multiple cells.
  • the above-mentioned DCI format includes a field for indicating a cell and/or an uplink carrier, and the field indicates a cell or an uplink carrier, and/or the cell and/or the uplink carrier indicated by the field is a Pcell or a PScell. or PUCCH Scell, and/or, this field is a specific value, and this specific value does not correspond to any cell and/or uplink carrier.
  • the terminal device also considers fields used to indicate scheduled cells and/or uplink carriers when validating.
  • the terminal device determines/validates the validity of the above-mentioned DCI format for semi-persistent CSI release/deactivation.
  • the terminal device may use the field indicating the cell and/or the uplink carrier and/or the field indicating the HARQ process ID and/or the field indicating the RV and/or multiple fields indicating the MCS in the above DCI format. and/or multiple indicators used to indicate frequency domain resource (RB) allocation to determine/validate the above validity.
  • RB frequency domain resource
  • the above DCI format may include multiple fields used to indicate the HARQ process ID, and the terminal device may determine/confirm ( validates) the validity of the above.
  • the DCI format may include multiple fields used to indicate RV, and the terminal device may determine/validate the above validity based on some or all of the fields used to indicate RV in the DCI format.
  • the above DCI format may also include one or more fields used to indicate cells and/or uplink carriers, and the terminal device may use some or all of the fields in the DCI format for cells and/or uplink carriers. Determine/validate the validity of the above.
  • the above DCI format may also include multiple fields used to indicate MCS, and the terminal device may determine/validate (validates) based on some or all of the fields in the DCI format used to indicate cells and/or uplink carriers. validity of the above.
  • the above-mentioned DCI format may also include a field used to indicate frequency domain resource (RB) allocation, and the terminal equipment is determined based on part or all of the fields in the DCI format used to indicate cells and/or uplink carriers. /Confirms (validates) the validity of the above.
  • RB frequency domain resource
  • the terminal device can also ignore or discard the DCI format. In other words, if the DCI format is confirmed to be invalid, the terminal device assumes that the CRC of the DCI format does not match, or assumes that the CRC check failed.
  • the DCI format 0_X includes multiple fields used to indicate the HARQ process ID (such as the HARQ process number field) and/or multiple fields used to indicate the RV (such as the Redundancy version field) and/or If there are multiple fields used to support MCS and/or multiple fields used to indicate frequency domain resource (RB) allocation, the multiple fields should meet the following conditions.
  • the above-mentioned fields corresponding to the cells and/or uplink carriers indicated by the fields used to indicate the scheduled cells and/or uplink carriers should meet the following conditions.
  • the end device ignores other fields indicating the HARQ process ID.
  • the release or deactivation of semi-persistent CSI reporting is achieved when the DCI format can schedule PUSCH of multiple cells.
  • Embodiments of the present application provide a method for releasing or deactivating semi-persistent CSI reporting, which is applied to the network device side and is a process on the network device side corresponding to the method of the embodiment of the fifth aspect, wherein it is consistent with the embodiment of the fifth aspect. The same content will not be repeated again.
  • Figure 25 is a schematic diagram of a method for releasing or deactivating semi-persistent CSI reporting according to an embodiment of the present application. As shown in Figure 25, the method includes:
  • the network device sends a DCI format for scheduling PUSCH on one or more cells and/or uplink carriers, and the DCI format releases or deactivates semi-persistent CSI reporting.
  • the release or deactivation of semi-persistent CSI reporting is achieved when the DCI format can schedule PUSCH of multiple cells.
  • the above-mentioned DCI format includes a field for indicating a cell and/or an uplink carrier, and the field indicates a cell or an uplink carrier, and/or the cell and/or the uplink carrier indicated by the field is a Pcell or a PScell. or PUCCH Scell, and/or, this field is a specific value, and this specific value does not correspond to any cell and/or uplink carrier.
  • the release or deactivation of semi-persistent CSI reporting is achieved when the DCI format can schedule PUSCH of multiple cells.
  • the DCI format (denoted as DCI format 0_X) that supports PUSCH scheduling of one or more cells and/or uplink carriers through one DCI is described.
  • the following table is a specific example of the fields of this DCI format 0_X.
  • type-1field is: a single field indicating common information to all co-scheduled cells, or a single field indicating separate information to each co-scheduled cell via a joint indication; or only a single field indicating common information to all co-scheduled cells.
  • a single field indicating information In DCI format 0_X, only one of this field is included.
  • the "type-2field” is: a separate field for each co-scheduled cell, or a separate field for each subgroup including one or more co-scheduled cells, where a single field is generally applied to those belonging to the same subgroup.
  • a group of jointly scheduled cells In DCI format 0_X, multiple fields are included.
  • the "type-3field" is shared or separated with each co-scheduled cell or each subgroup.
  • DCI format 0_X include one or more of this field, depending on explicit configuration or determined by implicit means, such as intra-band or inter-band CA, FR1 or FR2.
  • the UL-SCH indicator is used to indicate whether the PUSCH used to carry CSI reports also carries UL-SCH data.
  • the domain refers to the field, which can also be called the information domain.
  • An embodiment of the present application provides an aperiodic CSI reporting device.
  • the device may be, for example, a terminal device, or may be some or some components or components configured in the terminal device, and the same content as the embodiments of the first to second aspects will not be described again.
  • Figure 26 is a schematic diagram of an aperiodic CSI reporting device according to an embodiment of the present application. As shown in Figure 26, the aperiodic CSI reporting device 2600 in this embodiment of the present application includes:
  • the receiving unit 2601 receives the DCI format used to schedule PUSCH on one or more cells and/or uplink carriers, and the DCI format requests or triggers aperiodic CSI reporting;
  • Sending unit 2602 which sends the CSI report.
  • the DCI format schedules PUSCH on one cell and/or uplink carrier, and the sending unit 2602 sends the CSI report on the one cell and/or uplink carrier.
  • the DCI format when the DCI format requests or triggers aperiodic CSI reporting, the DCI format only schedules PUSCH on one cell and/or uplink carrier.
  • the DCI format includes a field for indicating a cell and/or an uplink carrier, and the field indicates a cell and/or an uplink carrier; the sending unit 2602 determines the cell and/or the uplink carrier indicated by the field. Or send the CSI report on the uplink carrier.
  • the sending unit 2602 sends the CSI report on the cell and/or uplink carrier that is used to send the CSI report by default or configured by signaling.
  • the DCI format includes fields used to indicate cells and/or uplink carriers, and the fields do not indicate cells and/or uplink carriers.
  • the DCI format includes fields used to indicate cells and/or uplink carriers, and the sending unit 2602 ignores the fields.
  • the DCI format includes a field for requesting or triggering CSI reporting, and the field for requesting or triggering CSI reporting is located before the field for indicating the cell and/or uplink carrier.
  • the DCI format does not include fields used to indicate cells and/or uplink carriers when requesting or triggering aperiodic CSI reporting.
  • the default cell used to send CSI reports is: Pcell or PScell or PUCCH Scell.
  • the DCI format schedules PUSCH on one or more cells and/or uplink carriers; the sending unit 2602 schedules PUSCH on one or more cells and/or uplink carriers. Or send the CSI report on the uplink carrier.
  • the DCI format includes a field used to request or trigger CSI reporting, and the value of the field corresponds to the CSI aperiodic triggering state.
  • the length of the field is configured by a high-level parameter, and the high-level parameter is specific to the DCI format, or the DCI format is common to other DCI formats.
  • the length of the field is determined by the terminal device according to the number of trigger states in the configured trigger state list.
  • the one cell and/or uplink carrier is a default cell and/or an uplink carrier configured by signaling for sending CSI reports.
  • the default cell used for sending CSI reports is at least one of the following:
  • the cell with the smallest serving cell identification number among the scheduled cells is the cell with the smallest serving cell identification number among the scheduled cells
  • the cell where the first PUSCH in the scheduled PUSCH that meets the aperiodic CSI reporting timing requirements in the time domain is located;
  • the cell with the smallest serving cell identification number among the cells where the first PUSCH in the scheduled PUSCH that meets the aperiodic CSI reporting timing requirements in the time domain is located.
  • the default cell used to send CSI reports is: Pcell or PScell or PUCCH Scell.
  • the sending unit 2602 sends the CSI report on the default PUSCH.
  • the default PUSCH is at least one of the following:
  • the PUSCH of the cell with the smallest serving cell identification number among the scheduled cells
  • the cell where the default PUSCH is located is: Pcell or PScell or PUCCH Scell.
  • the DCI format includes fields indicating cells and/or uplink carriers.
  • the default or signaling configured cell and/or uplink carrier for sending CSI reports is within the range of one or more cells and/or uplink carriers indicated by the field, or Not within the range of one or more cells and/or uplink carriers indicated by the field.
  • the DCI format schedules PUSCH on more than one cell and/or uplink carrier; the sending unit 2602 schedules PUSCH on one or more of the more than one cell and/or uplink carrier. Or send the CSI report on the uplink carrier.
  • the DCI format includes a field indicating a cell and/or an uplink carrier, and the field indicates the more than one cell and/or uplink carrier.
  • the contents of CSI reports on different PUSCHs are the same or different.
  • the DCI format includes a field used to request or trigger CSI reporting.
  • the CSI reports on different PUSCHs are the same, and/or different PUSCHs are used to carry different triggering states associated with the field.
  • CSI report, and/or different PUSCHs are used to carry different parts of the CSI report.
  • the DCI format includes multiple fields used to request or trigger CSI reporting, and different PUSCHs are used to carry CSI reports corresponding to triggering states associated with different fields used to request or trigger CSI reporting.
  • the CRC of the DCI format is scrambled by C-RNTI or scrambled by MCS-C-RNTI.
  • the receiving unit 2601 also receives configuration information for configuring the terminal device to listen to the DCI format in a UE-specific search space.
  • the receiving unit 2601 also receives configuration information for configuring whether the DCI format supports triggering CSI reporting or whether the DCI format is used to trigger CSI reporting.
  • the receiving unit 2601 also receives configuration information for configuring cells and/or uplink carriers that can be scheduled by the DCI format.
  • the more than one uplink carriers are of different cells respectively, or at least two of the more than one uplink carriers are of different cells.
  • An embodiment of the present application also provides a device for receiving a CSI report.
  • the device may be, for example, a network device, or may be some or some components or components configured on the network device.
  • the same content as the embodiments of the first to second aspects will not be described again.
  • Figure 27 is a schematic diagram of a CSI report receiving device according to an embodiment of the present application. As shown in Figure 27, the CSI report receiving device 2700 in this embodiment of the present application includes:
  • the sending unit 2701 sends a DCI format used to schedule PUSCH on one or more cells and/or uplink carriers, and the DCI format requests or triggers aperiodic CSI reporting;
  • Receiving unit 2702 which receives the CSI report.
  • the DCI format schedules PUSCH on one cell and/or uplink carrier, and the receiving unit 2702 receives the CSI report on the one cell and/or uplink carrier.
  • the DCI format when the DCI format requests or triggers aperiodic CSI reporting, the DCI format only schedules PUSCH on one cell and/or uplink carrier.
  • the DCI format includes a field for indicating a cell and/or an uplink carrier, and the field indicates a cell and/or an uplink carrier; the receiving unit 2702 determines the cell and/or the uplink carrier indicated by the field. Or receive the CSI report on the uplink carrier.
  • the receiving unit 2702 receives the CSI report on a cell and/or an uplink carrier configured by default or configured by signaling.
  • the DCI format includes fields used to indicate cells and/or uplink carriers, and the fields do not indicate cells and/or uplink carriers.
  • the DCI format includes fields for indicating cells and/or uplink carriers, and the terminal device ignores the fields.
  • the DCI format includes a field for requesting or triggering CSI reporting, and the field for requesting or triggering CSI reporting is located before the field for indicating the cell and/or uplink carrier.
  • the DCI format does not include fields used to indicate cells and/or uplink carriers when requesting or triggering aperiodic CSI reporting.
  • the default cell used to receive CSI reports is: Pcell or PScell or PUCCH Scell.
  • the DCI format schedules PUSCH on one or more cells and/or uplink carriers; the receiving unit 2702 schedules PUSCH on one or more cells and/or uplink carriers. Or receive the CSI report on the uplink carrier.
  • the DCI format includes a field used to request or trigger CSI reporting, and the value of the field corresponds to the CSI aperiodic triggering state.
  • the length of the field is configured by a high-level parameter, and the high-level parameter is specific to the DCI format, or the DCI format is common to other DCI formats.
  • the length of the field is determined by the terminal device according to the number of trigger states in the configured trigger state list.
  • the one cell and/or uplink carrier is a default cell and/or an uplink carrier configured by signaling for receiving CSI reports.
  • the default cell used to receive CSI reports is at least one of the following:
  • the cell with the smallest serving cell identification number among the scheduled cells is the cell with the smallest serving cell identification number among the scheduled cells
  • the cell where the first PUSCH in the scheduled PUSCH that meets the aperiodic CSI reporting timing requirements in the time domain is located;
  • the cell with the smallest serving cell identification number among the cells where the first PUSCH in the scheduled PUSCH that meets the aperiodic CSI reporting timing requirements in the time domain is located.
  • the default cell used to receive CSI reports is: Pcell or PScell or PUCCH Scell.
  • the receiving unit 2702 receives the CSI report on the default PUSCH.
  • the default PUSCH is at least one of the following:
  • the PUSCH of the cell with the smallest serving cell identification number among the scheduled cells
  • the cell where the default PUSCH is located is: Pcell or PScell or PUCCH Scell.
  • the DCI format includes fields indicating cells and/or uplink carriers.
  • the default or signaling configured cells and/or uplink carriers for receiving CSI reports are within the range of one or more cells and/or uplink carriers indicated by the field, or Not within the range of one or more cells and/or uplink carriers indicated by the field.
  • the DCI format schedules PUSCH on more than one cell and/or uplink carrier; the network device is configured on one or more of the more than one cell and/or uplink carrier. /or receive the CSI report on the uplink carrier.
  • the DCI format includes a field indicating a cell and/or an uplink carrier, and the field indicates the more than one cell and/or uplink carrier.
  • the contents of CSI reports on different PUSCHs are the same or different.
  • the DCI format includes a field used to request or trigger CSI reporting.
  • the CSI reports on different PUSCHs are the same, and/or different PUSCHs are used to carry different triggering states associated with the field.
  • CSI report, and/or different PUSCHs are used to carry different parts of the CSI report.
  • the DCI format includes multiple fields used to request or trigger CSI reporting, and different PUSCHs are used to carry CSI reports corresponding to triggering states associated with different fields used to request or trigger CSI reporting.
  • the CRC of the DCI format is scrambled by C-RNTI or scrambled by MCS-C-RNTI.
  • the sending unit 2701 also sends configuration information for configuring the terminal device to listen to the DCI format in a UE-specific search space.
  • the sending unit 2701 also sends configuration information for configuring whether the DCI format supports triggering CSI reporting or whether the DCI format is used to trigger CSI reporting.
  • the sending unit 2701 also sends configuration information for configuring cells and/or uplink carriers that can be scheduled by the DCI format.
  • the more than one uplink carriers are of different cells respectively, or at least two of the more than one uplink carriers are of different cells.
  • An embodiment of the present application also provides a semi-persistent CSI reporting device.
  • the device may be, for example, a terminal device, or may be some or some parts or components configured in the terminal device.
  • the same content as the embodiments of the third to fourth aspects will not be described again.
  • Figure 28 is a schematic diagram of a semi-persistent CSI reporting device according to an embodiment of the present application.
  • the semi-persistent CSI reporting device 2800 in this embodiment of the present application includes:
  • the receiving unit 2801 receives the DCI format used to schedule PUSCH on one or more cells and/or uplink carriers, and the DCI format triggers or activates semi-persistent CSI reporting;
  • Sending unit 2802 which sends the CSI report.
  • the DCI format schedules PUSCH on one cell and/or uplink carrier, and the sending unit 2802 sends the CSI report on the one cell and/or uplink carrier.
  • the DCI format when the DCI format triggers or activates semi-persistent CSI reporting, the DCI format only schedules PUSCH on one cell and/or uplink carrier.
  • the DCI format includes a field for indicating a cell and/or an uplink carrier, and the field indicates a cell and/or an uplink carrier; the sending unit 2802 indicates the cell and/or an uplink carrier in the field. Or send the CSI report on the uplink carrier.
  • the sending unit 2802 sends the CSI report on a cell and/or an uplink carrier that is used to send the CSI report by default or configured by signaling.
  • the DCI format includes fields used to indicate cells and/or uplink carriers, and the fields do not indicate cells and/or uplink carriers.
  • the DCI format includes fields used to indicate cells and/or uplink carriers, and the sending unit 2802 ignores the fields.
  • the DCI format includes a field for requesting or triggering CSI reporting, and the field for requesting or triggering CSI reporting is located before the field for indicating the cell and/or uplink carrier.
  • the DCI format does not include fields used to indicate cells and/or uplink carriers when triggering or activating semi-persistent CSI reporting.
  • the default cell used to send CSI reports is: Pcell or PScell or PUCCH Scell.
  • the DCI format schedules PUSCH on one or more cells and/or uplink carriers; the sending unit 2802 schedules PUSCH on one or more cells and/or uplink carriers. Or send the CSI report on the uplink carrier.
  • the DCI format includes a field used to request or trigger CSI reporting, and the value of the field corresponds to the CSI trigger state.
  • the length of the field is configured by a high-level parameter, and the high-level parameter is specific to the DCI format, or the DCI format is common to other DCI formats.
  • the length of the field is determined by the terminal device according to the number of trigger states in the configured trigger state list.
  • the one cell and/or uplink carrier is a default cell and/or an uplink carrier configured by signaling for sending CSI reports.
  • the default cell used for sending CSI reports is at least one of the following:
  • the cell with the smallest serving cell identification number among the scheduled cells is the cell with the smallest serving cell identification number among the scheduled cells
  • the cell where the first PUSCH in the scheduled PUSCH that meets the semi-persistent CSI reporting timing requirements in the time domain is located;
  • the cell with the smallest serving cell identification number among the cells where the first PUSCH in the scheduled PUSCH that satisfies the semi-persistent CSI reporting timing requirements in the time domain is located.
  • the default cell used to send CSI reports is: Pcell or PScell or PUCCH Scell.
  • the sending unit 2802 sends the CSI report on the default PUSCH.
  • the default PUSCH is at least one of the following:
  • the PUSCH of the cell with the smallest serving cell identification number among the scheduled cells
  • the cell where the default PUSCH is located is: Pcell or PScell or PUCCH Scell.
  • the DCI format includes fields indicating cells and/or uplink carriers.
  • the default or signaling configured cell and/or uplink carrier for sending CSI reports is within the range of one or more cells and/or uplink carriers indicated by the field, or Not within the range of one or more cells and/or uplink carriers indicated by the field.
  • the DCI format schedules PUSCH on more than one cell and/or uplink carrier; the sending unit 2802 schedules PUSCH on one or more of the more than one cell and/or uplink carrier. Or send the CSI report on the uplink carrier.
  • the DCI format includes a field indicating a cell and/or an uplink carrier, and the field indicates the more than one cell and/or uplink carrier.
  • the contents of CSI reports on different PUSCHs are the same or different.
  • the DCI format includes a field used to trigger or activate CSI reporting.
  • the CSI reports on different PUSCHs are the same, and/or different PUSCHs are used to carry different triggering states associated with the field.
  • CSI report, and/or different PUSCHs are used to carry different parts of the CSI report.
  • the DCI format includes multiple fields used to trigger or activate CSI reporting, and different PUSCHs are used to carry CSI reports corresponding to triggering states associated with different fields used to request or trigger CSI reporting.
  • the CRC of the DCI format is scrambled by SP-CSI-RNTI.
  • device 2800 further includes:
  • the determination/confirmation unit 2803 determines/validates the validity of the DCI format for semi-persistent CSI activation.
  • the determination/confirmation unit 2803 determines/confirms based on the field used to indicate the cell and/or the uplink carrier and/or the field used to indicate the HARQ process ID and/or the field used to indicate the RV in the DCI format. Validates the validity.
  • the DCI format includes multiple fields used to indicate the HARQ process ID, and the determination/confirmation unit 2803 determines based on some or all of the fields used to indicate cells and/or uplink carriers in the DCI format. /Validates the stated validity.
  • the DCI format includes multiple fields used to indicate RV, and the determining/confirming unit 2803 determines/validates the method according to some or all of the fields used to indicate RV in the DCI format. effectiveness.
  • the DCI format includes one or more fields used to indicate cells and/or uplink carriers, and the determination/confirmation unit 2803 uses part or all of the DCI format for cells and/or uplink carriers.
  • the fields of the carrier determine/validate the validity.
  • the receiving unit 2801 ignores/discards the DCI format.
  • An embodiment of the present application also provides a device for receiving a CSI report.
  • the device may be, for example, a network device, or may be one or some components or components configured on the network device.
  • the same content as the embodiments of the third to fourth aspects will not be described again.
  • Figure 29 is a schematic diagram of a CSI report receiving device according to an embodiment of the present application. As shown in Figure 29, the CSI report receiving device 2900 in this embodiment of the present application includes:
  • Sending unit 2901 which sends a DCI format for scheduling PUSCH on one or more cells and/or uplink carriers, the DCI format triggers or activates semi-persistent CSI reporting;
  • Receiving unit 2902 which receives the CSI report.
  • the DCI format schedules PUSCH on one cell and/or uplink carrier, and the receiving unit 2902 receives the CSI report on the one cell and/or uplink carrier.
  • the DCI format when the DCI format triggers or activates semi-persistent CSI reporting, the DCI format only schedules PUSCH on one cell and/or uplink carrier.
  • the DCI format includes a field for indicating a cell and/or an uplink carrier, and the field indicates a cell and/or an uplink carrier; the receiving unit 2902 determines the cell and/or the uplink carrier indicated by the field. Or receive the CSI report on the uplink carrier.
  • the receiving unit 2902 receives the CSI report on a cell and/or an uplink carrier configured by default or configured by signaling for receiving the CSI report.
  • the DCI format includes fields used to indicate cells and/or uplink carriers, and the fields do not indicate cells and/or uplink carriers.
  • the DCI format includes fields for indicating cells and/or uplink carriers, and the terminal device ignores the fields.
  • the DCI format includes a field for requesting or triggering CSI reporting, and the field for requesting or triggering CSI reporting is located before the field for indicating the cell and/or uplink carrier.
  • the DCI format does not include fields used to indicate cells and/or uplink carriers when triggering or activating semi-persistent CSI reporting.
  • the default cell used to receive CSI reports is: Pcell or PScell or PUCCH Scell.
  • the DCI format schedules PUSCH on one or more cells and/or uplink carriers; the receiving unit 2902 schedules PUSCH on one or more cells and/or uplink carriers. Or receive the CSI report on the uplink carrier.
  • the DCI format includes a field used to request or trigger CSI reporting, and the value of the field corresponds to the CSI trigger state.
  • the length of the field is configured by a high-level parameter, and the high-level parameter is specific to the DCI format, or the DCI format is common to other DCI formats.
  • the length of the field is determined by the terminal device according to the number of trigger states in the configured trigger state list.
  • the one cell and/or uplink carrier is a default cell and/or an uplink carrier configured by signaling for receiving CSI reports.
  • the default cell used to receive CSI reports is at least one of the following:
  • the cell with the smallest serving cell identification number among the scheduled cells is the cell with the smallest serving cell identification number among the scheduled cells
  • the cell where the first PUSCH in the scheduled PUSCH that meets the semi-persistent CSI reporting timing requirements in the time domain is located;
  • the cell with the smallest serving cell identification number among the cells where the first PUSCH in the scheduled PUSCH that satisfies the semi-persistent CSI reporting timing requirements in the time domain is located.
  • the default cell used to receive CSI reports is: Pcell or PScell or PUCCH Scell.
  • the receiving unit 2902 receives the CSI report on the default PUSCH.
  • the default PUSCH is at least one of the following:
  • the PUSCH of the cell with the smallest serving cell identification number among the scheduled cells
  • the cell where the default PUSCH is located is: Pcell or PScell or PUCCH Scell.
  • the DCI format includes fields indicating cells and/or uplink carriers.
  • the default or signaling configured cells and/or uplink carriers for receiving CSI reports are within the range of one or more cells and/or uplink carriers indicated by the field, or Not within the range of one or more cells and/or uplink carriers indicated by the field.
  • the DCI format schedules PUSCH on more than one cell and/or uplink carrier
  • the network device receives the CSI report on one or more cells and/or uplink carriers among the more than one cells and/or uplink carriers.
  • the DCI format includes a field indicating a cell and/or an uplink carrier, and the field indicates the more than one cell and/or uplink carrier.
  • the contents of CSI reports on different PUSCHs are the same or different.
  • the DCI format includes a field used to trigger or activate CSI reporting.
  • the CSI reports on different PUSCHs are the same, and/or different PUSCHs are used to carry different triggering states associated with the field.
  • CSI report, and/or different PUSCHs are used to carry different parts of the CSI report.
  • the DCI format includes multiple fields used to trigger or activate CSI reporting, and different PUSCHs are used to carry CSI reports corresponding to triggering states associated with different fields used to request or trigger CSI reporting.
  • the CRC of the DCI format is scrambled by SP-CSI-RNTI.
  • Embodiments of the present application also provide a device for releasing or deactivating semi-persistent CSI reporting.
  • the device may be, for example, a terminal device, or may be some or some components or components configured in the terminal device.
  • the same content as the embodiments of the fifth to sixth aspects will not be described again.
  • Figure 30 is a schematic diagram of a device for releasing or deactivating semi-persistent CSI reporting according to an embodiment of the present application.
  • the device 3000 for releasing or deactivating semi-persistent CSI reporting in this embodiment of the present application includes:
  • the receiving unit 3001 receives the DCI format used to schedule PUSCH on one or more cells and/or uplink carriers, and the DCI format releases or deactivates semi-persistent CSI reporting;
  • the processing unit 3002 deactivates semi-persistent CSI reporting.
  • the DCI format includes a field for indicating a cell and/or an uplink carrier, the field indicates a cell or an uplink carrier, and/or the cell and/or the uplink carrier indicated by the field is Pcell or PScell or PUCCH Scell, and/or the field is a specific value, and the specific value does not correspond to any cell and/or uplink carrier.
  • device 3000 further includes:
  • the determination/confirmation unit 3003 determines/validates the validity of the DCI format for semi-persistent CSI release/deactivation.
  • the determination/confirmation unit 3003 determines according to the field used to indicate the cell and/or the uplink carrier and/or the field used to indicate the HARQ process ID and/or the field used to indicate the RV and/or in the DCI format. Or multiple fields used to indicate MCS and/or multiple fields used to indicate frequency domain resource (RB) allocation determine/validate the validity.
  • the DCI format includes multiple fields used to indicate the HARQ process ID, and the determination/confirmation unit 3003 determines based on some or all of the fields in the DCI format used to indicate cells and/or uplink carriers. /Validates the stated validity.
  • the DCI format includes multiple fields for indicating RV, and the determining/confirming unit 3003 determines/validates the method according to some or all of the fields in the DCI format for indicating RV. effectiveness.
  • the DCI format includes one or more fields for indicating cells and/or uplink carriers, and the determination/confirmation unit 3003 uses part or all of the DCI format for cells and/or uplink carriers.
  • the fields of the carrier determine/validate the validity.
  • the DCI format includes multiple fields used to indicate modulation and coding scheme (MCS, Modulation and coding scheme), and the determination/confirmation unit 3003 is used to indicate the cell according to part or all of the DCI format. And/or the field of the uplink carrier determines/validates the validity.
  • MCS modulation and coding scheme
  • Modulation and coding scheme Modulation and coding scheme
  • the DCI format includes a field used to indicate frequency domain resource (such as resource block RB) allocation (Frequency domain resource assignment), and the determination/confirmation unit 3003 determines/confirms based on part or all of the usage in the DCI format.
  • the validity is determined/validated in fields indicating cells and/or uplink carriers.
  • the determination/confirmation unit 3003 ignores/discards the DCI format.
  • Embodiments of the present application also provide a device for releasing or deactivating semi-persistent CSI reporting.
  • the device may be, for example, a network device, or may be some or some parts or components configured on the network device.
  • the same content as the embodiments of the fifth to sixth aspects will not be described again.
  • Figure 31 is a schematic diagram of a device for releasing or deactivating semi-persistent CSI reporting according to an embodiment of the present application.
  • the device 3100 for releasing or deactivating semi-persistent CSI reporting in this embodiment of the present application includes:
  • the sending unit 3101 sends a DCI format used to schedule PUSCH on one or more cells and/or uplink carriers, and the DCI format releases or deactivates semi-persistent CSI reporting.
  • the DCI format includes a field for indicating a cell and/or an uplink carrier, the field indicates a cell or an uplink carrier, and/or the cell and/or the uplink carrier indicated by the field is Pcell or PScell or PUCCH Scell, and/or the field is a specific value, and the specific value does not correspond to any cell and/or uplink carrier.
  • the devices 2600, 2700, 2800, 2900, 3000, and 3100 may also include other components or modules.
  • the specific contents of these components or modules please refer to related technologies.
  • FIG. 26 to 31 only illustrate the connection relationships or signal directions between various components or modules, but it should be clear to those skilled in the art that various related technologies such as bus connections can be used.
  • Each of the above components or modules can be implemented by hardware facilities such as a processor, a memory, a transmitter, a receiver, etc.; the implementation of this application is not limited to this.
  • aperiodic CSI reporting and PUSCH-based semi-persistent CSI reporting are achieved when the DCI format can schedule PUSCH of multiple cells.
  • An embodiment of the present application also provides a communication system. Refer to FIG. 1 . The same content as the embodiments of the first to sixth aspects will not be described again.
  • the communication system 100 may at least include a network device and a terminal device, wherein the network device is configured to perform the method described in the embodiments of the second, fourth or sixth aspect; the terminal device is configured to The method described in the embodiment of the first aspect, the third aspect or the fifth aspect is executed.
  • the embodiment of the present application also provides a terminal device, but the present application is not limited to this and may also be other devices.
  • Figure 32 is a schematic diagram of a terminal device according to an embodiment of the present application.
  • the terminal device 3200 may include a processor 3210 and a memory 3220; the memory 3220 stores data and programs and is coupled to the processor 3210. It is worth noting that this figure is exemplary; other types of structures may also be used to supplement or replace this structure to implement telecommunications functions or other functions.
  • the processor 3210 may be configured to execute a program to implement the method described in the embodiments of the first aspect, the third aspect, or the fifth aspect.
  • the terminal device 3200 may also include: a communication module 3230, an input unit 3240, a display 3250, and a power supply 3260.
  • the functions of the above components are similar to those in the prior art and will not be described again here. It is worth noting that the terminal device 3200 does not have to include all the components shown in Figure 32, and the above components are not required; in addition, the terminal device 3200 can also include components not shown in Figure 32, please refer to the current There is technology.
  • the embodiment of the present application also provides a network device, which may be a base station, for example, but the present application is not limited thereto and may also be other network devices.
  • a network device which may be a base station, for example, but the present application is not limited thereto and may also be other network devices.
  • FIG 33 is a schematic structural diagram of a network device according to an embodiment of the present application.
  • network device 3300 may include: a processor 3310 (eg, a central processing unit CPU) and a memory 3320; the memory 3320 is coupled to the processor 3310.
  • the memory 3320 can store various data; in addition, it also stores an information processing program 3330, and the program 3330 is executed under the control of the processor 3310.
  • the processor 3310 may be configured to execute a program to implement the method described in the embodiments of the second aspect, the fourth aspect, or the sixth aspect.
  • the network device 3300 may also include: a transceiver 3340, an antenna 3350, etc.; the functions of the above components are similar to those of the existing technology, and will not be described again here. It is worth noting that the network device 3300 does not necessarily include all components shown in Figure 33; in addition, the network device 3300 may also include components not shown in Figure 33, and reference can be made to the existing technology.
  • An embodiment of the present application also provides a computer program, wherein when the program is executed in a terminal device, the program causes the terminal device to execute the method described in the embodiment of the first aspect, the third aspect, or the fifth aspect. .
  • Embodiments of the present application also provide a storage medium storing a computer program, wherein the computer program causes the terminal device to execute the method described in the embodiments of the first aspect, the third aspect, or the fifth aspect.
  • An embodiment of the present application also provides a computer program, wherein when the program is executed in a network device, the program causes the network device to execute the method described in the embodiment of the second aspect, the fourth aspect, or the sixth aspect. .
  • An embodiment of the present application also provides a storage medium storing a computer program, wherein the computer program causes the network device to perform the method described in the embodiment of the second aspect, the fourth aspect, or the sixth aspect.
  • the above devices and methods of this application can be implemented by hardware, or can be implemented by hardware combined with software.
  • the present application relates to a computer-readable program that, when executed by a logic component, enables the logic component to implement the apparatus or component described above, or enables the logic component to implement the various methods described above or steps.
  • This application also involves storage media used to store the above programs, such as hard disks, magnetic disks, optical disks, DVDs, flash memories, etc.
  • the methods/devices described in connection with the embodiments of the present application may be directly embodied as hardware, a software module executed by a processor, or a combination of both.
  • one or more of the functional block diagrams and/or one or more combinations of the functional block diagrams shown in the figure may correspond to each software module of the computer program flow, or may correspond to each hardware module.
  • These software modules can respectively correspond to the various steps shown in the figure.
  • These hardware modules can be implemented by solidifying these software modules using a field programmable gate array (FPGA), for example.
  • FPGA field programmable gate array
  • the software module may be located in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, removable disk, CD-ROM, or any other form of storage medium known in the art.
  • a storage medium may be coupled to the processor such that the processor can read information from the storage medium and write information to the storage medium; or the storage medium may be an integral part of the processor.
  • the processor and storage media may be located in an ASIC.
  • the software module can be stored in the memory of the mobile terminal or in a memory card that can be inserted into the mobile terminal.
  • the software module can be stored in the MEGA-SIM card or the large-capacity flash memory device.
  • One or more of the functional blocks and/or one or more combinations of the functional blocks described in the accompanying drawings may be implemented as a general-purpose processor or a digital signal processor (DSP) for performing the functions described in this application. ), application specific integrated circuit (ASIC), field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware component, or any appropriate combination thereof.
  • DSP digital signal processor
  • ASIC application specific integrated circuit
  • FPGA field programmable gate array
  • One or more of the functional blocks and/or one or more combinations of the functional blocks described in the accompanying drawings can also be implemented as a combination of computing devices, for example, a combination of a DSP and a microprocessor, or multiple microprocessors. processor, one or more microprocessors combined with DSP communications, or any other such configuration.
  • An aperiodic CSI reporting method wherein the method includes:
  • the terminal equipment receives a DCI format used to schedule PUSCH on one or more cells and/or uplink carriers, and the DCI format requests or triggers aperiodic CSI reporting;
  • the terminal device sends a CSI report.
  • the DCI format schedules PUSCH on one cell and/or uplink carrier, and the terminal equipment sends the CSI report on the one cell and/or uplink carrier.
  • the DCI format In the case where the DCI format requests or triggers aperiodic CSI reporting, the DCI format only schedules PUSCH on one cell and/or uplink carrier.
  • the DCI format includes a field used to indicate a cell and/or an uplink carrier, and the field indicates a cell and/or an uplink carrier;
  • the terminal equipment sends the CSI report on the cell and/or uplink carrier indicated by the field.
  • the terminal equipment sends the CSI report on a default cell and/or an uplink carrier configured by signaling for sending the CSI report.
  • the DCI format includes fields used to indicate cells and/or uplink carriers, and the fields do not indicate cells and/or uplink carriers.
  • the DCI format includes fields used to indicate cells and/or uplink carriers, and the terminal equipment ignores the fields.
  • the DCI format includes a field used to request or trigger CSI reporting, and the field used to request or trigger CSI reporting is located before a field used to indicate a cell and/or an uplink carrier.
  • the DCI format does not include fields used to indicate cells and/or uplink carriers when requesting or triggering aperiodic CSI reporting.
  • the default cell used to send CSI reports is: Pcell or PScell or PUCCH Scell.
  • the DCI format schedules PUSCH on one or more cells and/or uplink carriers
  • the terminal equipment sends the CSI report on one of the one or more cells and/or uplink carriers.
  • the DCI format includes a field used to request or trigger CSI reporting, and the value of the field corresponds to the CSI aperiodic triggering state.
  • the length of the field is configured by high-level parameters, and the high-level parameters are specific to the DCI format, or the DCI format is shared with other DCI formats.
  • the length of the field is determined by the terminal device according to the number of trigger states in the configured trigger state list.
  • the one cell and/or uplink carrier is a default cell and/or an uplink carrier configured by signaling for sending CSI reports.
  • the default cell used to send CSI reports is at least one of the following:
  • the cell with the smallest serving cell identification number among the scheduled cells is the cell with the smallest serving cell identification number among the scheduled cells
  • the cell where the first PUSCH in the scheduled PUSCH that meets the aperiodic CSI reporting timing requirements in the time domain is located;
  • the cell with the smallest serving cell identification number among the cells where the first PUSCH in the scheduled PUSCH that meets the aperiodic CSI reporting timing requirements in the time domain is located.
  • the default cell used to send CSI reports is: Pcell or PScell or PUCCH Scell.
  • the terminal equipment sends the CSI report on the default PUSCH.
  • the default PUSCH is at least one of the following:
  • the PUSCH of the cell with the smallest serving cell identification number among the scheduled cells
  • the default cell where PUSCH is located is: Pcell or PScell or PUCCH Scell.
  • the DCI format includes fields used to indicate cells and/or uplink carriers.
  • the default or signaling-configured cell and/or uplink carrier for sending CSI reports is within the range of one or more cells and/or uplink carriers indicated by the field, or is not within the range indicated by the field. Within the range of one or more cells and/or uplink carriers.
  • the DCI format schedules PUSCH on more than one cell and/or uplink carrier
  • the terminal equipment sends the CSI report on one or more cells and/or uplink carriers among the more than one cells and/or uplink carriers.
  • the DCI format includes fields used to indicate cells and/or uplink carriers, and the fields indicate the more than one cells and/or uplink carriers.
  • the contents of CSI reports on different PUSCHs are the same or different.
  • the DCI format includes a field used to request or trigger CSI reporting, and the CSI reports on different PUSCHs are the same, and/or different PUSCHs are used to carry different CSI reports corresponding to the triggering status associated with the field, and/or Or, different PUSCHs are used to carry different parts of the CSI report.
  • the DCI format includes a plurality of fields used to request or trigger CSI reporting, and different PUSCHs are used to carry CSI reports corresponding to trigger states associated with different fields used to request or trigger CSI reporting.
  • the CRC of the DCI format is scrambled by C-RNTI or scrambled by MCS-C-RNTI.
  • the terminal device receives configuration information for configuring the terminal device to monitor the DCI format in a UE-specific search space.
  • the terminal device receives configuration information for configuring whether the DCI format supports triggering CSI reporting or whether the DCI format is used to trigger CSI reporting.
  • the terminal device receives configuration information for configuring cells and/or uplink carriers that can be scheduled by the DCI format.
  • the more than one uplink carriers are respectively of different cells, or at least two of the more than one uplink carriers are of different cells.
  • a method for receiving CSI reports includes:
  • the network device sends a DCI format used to schedule PUSCH on one or more cells and/or uplink carriers, and the DCI format requests or triggers aperiodic CSI reporting;
  • the network device receives the CSI report.
  • the DCI format schedules PUSCH on one cell and/or uplink carrier, and the network device receives the CSI report on the one cell and/or uplink carrier.
  • the DCI format In the case where the DCI format requests or triggers aperiodic CSI reporting, the DCI format only schedules PUSCH on one cell and/or uplink carrier.
  • the DCI format includes a field used to indicate a cell and/or an uplink carrier, and the field indicates a cell and/or an uplink carrier;
  • the network device receives the CSI report on the cell and/or uplink carrier indicated by the field.
  • the network device receives the CSI report on a cell and/or an uplink carrier configured by default or configured by signaling for receiving the CSI report.
  • the DCI format includes fields used to indicate cells and/or uplink carriers, and the fields do not indicate cells and/or uplink carriers.
  • the DCI format includes fields used to indicate cells and/or uplink carriers, and the terminal equipment ignores the fields.
  • the DCI format includes a field used to request or trigger CSI reporting, and the field used to request or trigger CSI reporting is located before a field used to indicate a cell and/or an uplink carrier.
  • the DCI format does not include fields used to indicate cells and/or uplink carriers when requesting or triggering aperiodic CSI reporting.
  • the default cell used to receive CSI reports is: Pcell or PScell or PUCCH Scell.
  • the DCI format schedules PUSCH on one or more cells and/or uplink carriers
  • the network device receives the CSI report on one of the one or more cells and/or uplink carriers.
  • the DCI format includes a field used to request or trigger CSI reporting, and the value of the field corresponds to the CSI aperiodic triggering state.
  • the length of the field is configured by high-level parameters, and the high-level parameters are specific to the DCI format, or the DCI format is shared with other DCI formats.
  • the length of the field is determined by the terminal device according to the number of trigger states in the configured trigger state list.
  • the one cell and/or uplink carrier is a default cell and/or an uplink carrier configured by signaling for receiving CSI reports.
  • the default cell used to receive CSI reports is at least one of the following:
  • the cell with the smallest serving cell identification number among the scheduled cells is the cell with the smallest serving cell identification number among the scheduled cells
  • the cell where the first PUSCH in the scheduled PUSCH that meets the aperiodic CSI reporting timing requirements in the time domain is located;
  • the cell with the smallest serving cell identification number among the cells where the first PUSCH in the scheduled PUSCH that meets the aperiodic CSI reporting timing requirements in the time domain is located.
  • the default cell used to receive CSI reports is: Pcell or PScell or PUCCH Scell.
  • the network device receives the CSI report on the default PUSCH.
  • the default PUSCH is at least one of the following:
  • the PUSCH of the cell with the smallest serving cell identification number among the scheduled cells
  • the default cell where PUSCH is located is: Pcell or PScell or PUCCH Scell.
  • the DCI format includes fields used to indicate cells and/or uplink carriers.
  • the default or signaling-configured cell and/or uplink carrier for receiving CSI reports is within the range of one or more cells and/or uplink carriers indicated by the field, or is not within the range indicated by the field. Within the range of one or more cells and/or uplink carriers.
  • the DCI format schedules PUSCH on more than one cell and/or uplink carrier
  • the network device receives the CSI report on one or more cells and/or uplink carriers among the more than one cells and/or uplink carriers.
  • the DCI format includes fields used to indicate cells and/or uplink carriers, and the fields indicate the more than one cells and/or uplink carriers.
  • the contents of CSI reports on different PUSCHs are the same or different.
  • the DCI format includes a field used to request or trigger CSI reporting, and the CSI reports on different PUSCHs are the same, and/or different PUSCHs are used to carry different CSI reports corresponding to the triggering status associated with the field, and/or Or, different PUSCHs are used to carry different parts of the CSI report.
  • the DCI format includes a plurality of fields used to request or trigger CSI reporting, and different PUSCHs are used to carry CSI reports corresponding to trigger states associated with different fields used to request or trigger CSI reporting.
  • the CRC of the DCI format is scrambled by C-RNTI or scrambled by MCS-C-RNTI.
  • the network device sends configuration information for configuring the terminal device to monitor the DCI format in a UE-specific search space.
  • the network device sends configuration information for configuring whether the DCI format supports triggering CSI reporting or whether the DCI format is used to trigger CSI reporting.
  • the network device sends configuration information for configuring cells and/or uplink carriers that can be scheduled by the DCI format.
  • the more than one uplink carriers are respectively of different cells, or at least two of the more than one uplink carriers are of different cells.
  • a semi-persistent CSI reporting method wherein the method includes:
  • the terminal equipment receives a DCI format used to schedule PUSCH on one or more cells and/or uplink carriers, and the DCI format triggers or activates semi-persistent CSI reporting;
  • the terminal device sends a CSI report.
  • the DCI format schedules PUSCH on one cell and/or uplink carrier, and the terminal equipment sends the CSI report on the one cell and/or uplink carrier.
  • the DCI format In the case where the DCI format triggers or activates semi-persistent CSI reporting, the DCI format only schedules PUSCH on one cell and/or uplink carrier.
  • the DCI format includes a field used to indicate a cell and/or an uplink carrier, and the field indicates a cell and/or an uplink carrier;
  • the terminal equipment sends the CSI report on the cell and/or uplink carrier indicated by the field.
  • the terminal equipment sends the CSI report on a default cell and/or an uplink carrier configured by signaling for sending the CSI report.
  • the DCI format includes fields used to indicate cells and/or uplink carriers, and the fields do not indicate cells and/or uplink carriers.
  • the DCI format includes fields used to indicate cells and/or uplink carriers, and the terminal equipment ignores the fields.
  • the DCI format includes a field used to request or trigger CSI reporting, and the field used to request or trigger CSI reporting is located before a field used to indicate a cell and/or an uplink carrier.
  • the DCI format does not include fields used to indicate cells and/or uplink carriers when triggering or activating semi-persistent CSI reporting.
  • the default cell used to send CSI reports is: Pcell or PScell or PUCCH Scell.
  • the DCI format schedules PUSCH on one or more cells and/or uplink carriers
  • the terminal equipment sends the CSI report on one of the one or more cells and/or uplink carriers.
  • the DCI format includes a field used to request or trigger CSI reporting, and the value of the field corresponds to the CSI trigger status.
  • the length of the field is configured by high-level parameters, and the high-level parameters are specific to the DCI format, or the DCI format is shared with other DCI formats.
  • the length of the field is determined by the terminal device according to the number of trigger states in the configured trigger state list.
  • the one cell and/or uplink carrier is a default cell and/or an uplink carrier configured by signaling for sending CSI reports.
  • the default cell used to send CSI reports is at least one of the following:
  • the cell with the smallest serving cell identification number among the scheduled cells is the cell with the smallest serving cell identification number among the scheduled cells
  • the cell where the first PUSCH in the scheduled PUSCH that meets the semi-persistent CSI reporting timing requirements in the time domain is located;
  • the cell with the smallest serving cell identification number among the cells where the first PUSCH in the scheduled PUSCH that satisfies the semi-persistent CSI reporting timing requirements in the time domain is located.
  • the default cell used to send CSI reports is: Pcell or PScell or PUCCH Scell.
  • the terminal equipment sends the CSI report on the default PUSCH.
  • the default PUSCH is at least one of the following:
  • the PUSCH of the cell with the smallest serving cell identification number among the scheduled cells
  • the default cell where PUSCH is located is: Pcell or PScell or PUCCH Scell.
  • the DCI format includes fields used to indicate cells and/or uplink carriers.
  • the default or signaling-configured cell and/or uplink carrier for sending CSI reports is within the range of one or more cells and/or uplink carriers indicated by the field, or is not within the range indicated by the field. Within the range of one or more cells and/or uplink carriers.
  • the DCI format schedules PUSCH on more than one cell and/or uplink carrier
  • the terminal equipment sends the CSI report on one or more cells and/or uplink carriers among the more than one cells and/or uplink carriers.
  • the DCI format includes fields used to indicate cells and/or uplink carriers, and the fields indicate the more than one cells and/or uplink carriers.
  • the contents of CSI reports on different PUSCHs are the same or different.
  • the DCI format includes a field used to trigger or activate CSI reporting, and the CSI reports on different PUSCHs are the same, and/or different PUSCHs are used to carry different CSI reports corresponding to the triggering status associated with the field, and/or Or, different PUSCHs are used to carry different parts of the CSI report.
  • the DCI format includes a plurality of fields used to trigger or activate CSI reporting, and different PUSCHs are used to carry CSI reports corresponding to triggering states associated with different fields used to request or trigger CSI reporting.
  • the CRC of the DCI format is scrambled by SP-CSI-RNTI.
  • the terminal device determines/validates the validity of the DCI format for semi-persistent CSI activation.
  • the terminal device determines/validates the validity according to the field used to indicate the cell and/or the uplink carrier and/or the field used to indicate the HARQ process ID and/or the field used to indicate the RV in the DCI format. sex.
  • the DCI format includes a plurality of fields used to indicate the HARQ process ID, and the terminal device determines/validates based on part or all of the fields in the DCI format used to indicate cells and/or uplink carriers. effectiveness.
  • the DCI format includes a plurality of fields used to indicate RV, and the terminal device determines/validates the validity according to some or all of the fields used to indicate RV in the DCI format.
  • the DCI format includes one or more fields used to indicate cells and/or uplink carriers, and the terminal device determines/confirms ( validates) the validity.
  • the terminal device ignores/discards the DCI format.
  • a method for receiving CSI reports includes:
  • the network device sends a DCI format used to schedule PUSCH on one or more cells and/or uplink carriers, and the DCI format triggers or activates semi-persistent CSI reporting;
  • the network device receives the CSI report.
  • the DCI format schedules PUSCH on one cell and/or uplink carrier, and the network device receives the CSI report on the one cell and/or uplink carrier.
  • the DCI format In the case where the DCI format triggers or activates semi-persistent CSI reporting, the DCI format only schedules PUSCH on one cell and/or uplink carrier.
  • the DCI format includes a field used to indicate a cell and/or an uplink carrier, and the field indicates a cell and/or an uplink carrier;
  • the network device receives the CSI report on the cell and/or uplink carrier indicated by the field.
  • the network device receives the CSI report on a cell and/or an uplink carrier configured by default or configured by signaling for receiving the CSI report.
  • the DCI format includes fields used to indicate cells and/or uplink carriers, and the fields do not indicate cells and/or uplink carriers.
  • the DCI format includes fields used to indicate cells and/or uplink carriers, and the terminal equipment ignores the fields.
  • the DCI format includes a field used to request or trigger CSI reporting, and the field used to request or trigger CSI reporting is located before a field used to indicate a cell and/or an uplink carrier.
  • the DCI format does not include fields used to indicate cells and/or uplink carriers when triggering or activating semi-persistent CSI reporting.
  • the default cell used to receive CSI reports is: Pcell or PScell or PUCCH Scell.
  • the DCI format schedules PUSCH on one or more cells and/or uplink carriers
  • the network device receives the CSI report on one of the one or more cells and/or uplink carriers.
  • the DCI format includes a field used to request or trigger CSI reporting, and the value of the field corresponds to the CSI trigger status.
  • the length of the field is configured by high-level parameters, and the high-level parameters are specific to the DCI format, or the DCI format is shared with other DCI formats.
  • the length of the field is determined by the terminal device according to the number of trigger states in the configured trigger state list.
  • the one cell and/or uplink carrier is a default cell and/or an uplink carrier configured by signaling for receiving CSI reports.
  • the default cell used to receive CSI reports is at least one of the following:
  • the cell with the smallest serving cell identification number among the scheduled cells is the cell with the smallest serving cell identification number among the scheduled cells
  • the cell where the first PUSCH in the scheduled PUSCH that meets the semi-persistent CSI reporting timing requirements in the time domain is located;
  • the cell with the smallest serving cell identification number among the cells where the first PUSCH in the scheduled PUSCH that satisfies the semi-persistent CSI reporting timing requirements in the time domain is located.
  • the default cell used to receive CSI reports is: Pcell or PScell or PUCCH Scell.
  • the network device receives the CSI report on the default PUSCH.
  • the default PUSCH is at least one of the following:
  • the PUSCH of the cell with the smallest serving cell identification number among the scheduled cells
  • the default cell where PUSCH is located is: Pcell or PScell or PUCCH Scell.
  • the DCI format includes fields used to indicate cells and/or uplink carriers.
  • the default or signaling-configured cell and/or uplink carrier for receiving CSI reports is within the range of one or more cells and/or uplink carriers indicated by the field, or is not within the range indicated by the field. Within the range of one or more cells and/or uplink carriers.
  • the DCI format schedules PUSCH on more than one cell and/or uplink carrier
  • the network device receives the CSI report on one or more cells and/or uplink carriers among the more than one cells and/or uplink carriers.
  • the DCI format includes fields used to indicate cells and/or uplink carriers, and the fields indicate the more than one cells and/or uplink carriers.
  • the contents of CSI reports on different PUSCHs are the same or different.
  • the DCI format includes a field used to trigger or activate CSI reporting, and the CSI reports on different PUSCHs are the same, and/or different PUSCHs are used to carry different CSI reports corresponding to the triggering status associated with the field, and/or Or, different PUSCHs are used to carry different parts of the CSI report.
  • the DCI format includes a plurality of fields used to trigger or activate CSI reporting, and different PUSCHs are used to carry CSI reports corresponding to triggering states associated with different fields used to request or trigger CSI reporting.
  • the CRC of the DCI format is scrambled by SP-CSI-RNTI.
  • a method for releasing or deactivating semi-persistent CSI reporting includes:
  • the terminal equipment receives a DCI format used to schedule PUSCH on one or more cells and/or uplink carriers, and the DCI format releases or deactivates semi-persistent CSI reporting;
  • the terminal device deactivates semi-persistent CSI reporting.
  • the DCI format includes a field for indicating a cell and/or an uplink carrier, the field indicates a cell or an uplink carrier, and/or, the cell and/or the uplink carrier indicated by the field is a Pcell or a PScell or a PUCCH Scell. , and/or the field is a specific value, and the specific value does not correspond to any cell and/or uplink carrier.
  • the terminal device determines/validates the validity of the DCI format for semi-persistent CSI release/deactivation.
  • the terminal equipment is configured according to the field used to indicate the cell and/or the uplink carrier and/or the field used to indicate the HARQ process ID and/or the field used to indicate the RV and/or multiple fields used to indicate the MCS in the DCI format. and/or multiple indicators for determining/validating the validity of frequency domain resource (RB) allocation.
  • RB frequency domain resource
  • the DCI format includes a plurality of fields used to indicate the HARQ process ID, and the terminal device determines/validates based on part or all of the fields in the DCI format used to indicate cells and/or uplink carriers. effectiveness.
  • the DCI format includes a plurality of fields used to indicate RV, and the terminal device determines/validates the validity according to some or all of the fields used to indicate RV in the DCI format.
  • the DCI format includes one or more fields used to indicate cells and/or uplink carriers, and the terminal device determines/confirms ( validates) the validity.
  • the DCI format includes multiple fields for indicating MCS, and the terminal device determines/validates the validity based on some or all of the fields in the DCI format for indicating cells and/or uplink carriers. .
  • the DCI format includes fields used to indicate frequency domain resource (RB) allocation, and the terminal device determines/validates based on part or all of the fields in the DCI format used to indicate cells and/or uplink carriers. said effectiveness.
  • RB frequency domain resource
  • the terminal device ignores/discards the DCI format.
  • a method for releasing or deactivating semi-persistent CSI reporting includes:
  • the network device sends a DCI format for scheduling PUSCH on one or more cells and/or uplink carriers, and the DCI format releases or deactivates semi-persistent CSI reporting.
  • the DCI format includes a field for indicating a cell and/or an uplink carrier, the field indicates a cell or an uplink carrier, and/or, the cell and/or the uplink carrier indicated by the field is a Pcell or a PScell or a PUCCH Scell. , and/or the field is a specific value, and the specific value does not correspond to any cell and/or uplink carrier.
  • a terminal device comprising a memory and a processor, the memory stores a computer program, and the processor is configured to execute the computer program to implement appendices 1 to 32, 1' to 34', and 1" to 10" any of the methods described.
  • a network device including a memory and a processor
  • the memory stores a computer program
  • the processor is configured to execute the computer program to implement appendices 33 to 64, 35' to 62' and 11" to 12" any of the methods described.
  • a communication system including network equipment and terminal equipment, wherein:
  • the network equipment is configured to:
  • the terminal device is configured as:
  • a communication system including network equipment and terminal equipment, wherein:
  • the network equipment is configured to:
  • the terminal device is configured as:
  • a communication system including network equipment and terminal equipment, wherein:
  • the network equipment is configured to:
  • the terminal device is configured as:

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Quality & Reliability (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本申请实施例提供一种信道状态信息上报方法和装置，所述方法包括：终端设备接收用于调度一个或多于一个小区和/或上行载波上的PUSCH的DCI format，所述DCI format请求或触发非周期CSI上报；所述终端设备发送CSI报告。根据本申请实施例，实现了在DCI format能够调度多个小区的PUSCH的情况下的非周期CSI上报以及基于PUSCH的半持续CSI上报。

Description

信道状态信息的上报方法和装置 技术领域
本申请实施例涉及通信技术领域。
背景技术
物理下行共享信道(Physical Downlink Shared Channel，PDSCH)是无线通信系统中物理下行信道的一种，用于承载下行数据。物理上行共享信道(Physical Uplink Shared Channel，PUSCH)是无线通信系统中物理上行信道的一种，用于承载上行数据。PDSCH和PUSCH可以通过下行控制信息(downlink control information，DCI)调度。在目前的新无线(new radio，NR)系统中，定义了多种用于调度PDSCH或PUSCH的DCI格式(format)，不同DCI format包括的具体信息和/或大小是不一样的，以满足不同的调度需求。
应该注意，上面对技术背景的介绍只是为了方便对本申请的技术方案进行清楚、完整的说明，并方便本领域技术人员的理解而阐述的，不能仅仅因为这些方案在本申请的背景技术部分进行了阐述而认为上述技术方案为本领域技术人员所公知。
发明内容
发明人发现，目前，DCI format 0_1和DCI format 0_2可以用于触发/激活/去激活非周期性CSI report以及基于PUSCH的SP CSI report，并且，DCI format 0_1和DCI format 0_2均只能调度一个小区(或上行载波)的PUSCH。而在刚刚开始的Rel-18NR的标准化工作中，作为多载波增强的目标之一，将考虑如何进一步支持通过一个DCI调度多个小区(或上行载波)的PUSCH，以减小DCI的资源开销，提高系统吞吐量。这个支持调度多个小区(或上行载波)的DCI可能是一个新的DCI format(例如DCI format 0_3，不限于此)或者是对现有DCI format(例如DCI format 0_1和DCI format 0_2)进行增强。
然而，由于现有的用于触发/激活/去激活非周期性CSI report以及基于PUSCH的SP CSI report的方法是基于DCI format仅能调度一个小区(或上行载波)的PUSCH的假设进行设计的，其不能直接应用于DCI format可以调度多个小区(或上行载波)的PUSCH 的情况。
针对上述问题的至少之一，本申请实施例提供一种信道状态信息的上报方法和装置，以支持DCI format能够调度多个小区(或上行载波)的PUSCH的情况下的非周期CSI上报以及基于PUSCH的半持续CSI上报。
根据本申请实施例的一个方面，提供一种非周期CSI上报装置，所述装置包括：
接收单元，其接收用于调度一个或多于一个小区和/或上行载波上的PUSCH的DCI format，所述DCI format请求或触发非周期CSI上报；
发送单元，其发送CSI报告。
根据本申请实施例的另一个方面，提供一种CSI报告的接收装置，所述装置包括：
发送单元，其发送用于调度一个或多于一个小区和/或上行载波上的PUSCH的DCI format，所述DCI format请求或触发非周期CSI上报；
接收单元，其接收CSI报告。
根据本申请实施例的另一个方面，提供一种半持续CSI上报装置，所述装置包括：
接收单元，其接收用于调度一个或多于一个小区和/或上行载波上的PUSCH的DCI format，所述DCI format触发或激活半持续CSI上报；
发送单元，其发送CSI报告。
根据本申请实施例的另一个方面，提供一种CSI报告的接收装置，所述装置包括：
发送单元，其发送用于调度一个或多于一个小区和/或上行载波上的PUSCH的DCI format，所述DCI format触发或激活半持续CSI上报；
接收单元，其接收CSI报告。
根据本申请实施例的另一个方面，提供一种半持续CSI上报的释放或去激活装置，所述装置包括：
接收单元，其接收用于调度一个或多于一个小区和/或上行载波上的PUSCH的DCI format，所述DCI format释放或去激活半持续CSI上报；
处理单元，其去激活半持续CSI上报。
根据本申请实施例的另一个方面，提供一种半持续CSI上报的释放或去激活装置，所述装置包括：
发送单元，其发送用于调度一个或多于一个小区和/或上行载波上的PUSCH的DCI format，所述DCI format释放或去激活半持续CSI上报。
本申请实施例的有益效果之一在于：根据本申请实施例，实现了在DCI format能够 调度多个小区的PUSCH的情况下的非周期CSI上报以及基于PUSCH的半持续CSI上报。
参照后文的说明和附图，详细公开了本申请的特定实施方式，指明了本申请的原理可以被采用的方式。应该理解，本申请的实施方式在范围上并不因而受到限制。在所附权利要求的精神和条款的范围内，本申请的实施方式包括许多改变、修改和等同。
针对一种实施方式描述和/或示出的特征可以以相同或类似的方式在一个或更多个其它实施方式中使用，与其它实施方式中的特征相组合，或替代其它实施方式中的特征。
应该强调，术语“包括/包含”在本文使用时指特征、整件、步骤或组件的存在，但并不排除一个或更多个其它特征、整件、步骤或组件的存在或附加。
附图说明
在本申请实施例的一个附图或一种实施方式中描述的元素和特征可以与一个或更多个其它附图或实施方式中示出的元素和特征相结合。此外，在附图中，类似的标号表示几个附图中对应的部件，并可用于指示多于一种实施方式中使用的对应部件。
图1是本申请实施例的通信系统的一示意图；
图2是非周期CSI上报的时序关系的一示意图；
图3是基于PUSCH的SP CSI上报的时序关系的一示意图；
图4是本申请实施例的非周期CSI上报方法的一示意图；
图5至图12是非周期CSI上报的示例的示意图；
图13是本申请实施例的CSI报告的接收方法的一示意图；
图14是本申请实施例的半持续CSI上报方法的一示意图；
图15至图22是半持续CSI上报的示例的示意图；
图23是本申请实施例的CSI报告的接收方法的一示意图；
图24是本申请实施例的半持续CSI上报的释放或去激活方法的一示意图；
图25是本申请实施例的半持续CSI上报的释放或去激活方法的一示意图；
图26是本申请实施例的非周期CSI上报装置的一示意图；
图27是本申请实施例的CSI报告的接收装置的一示意图；
图28是本申请实施例的半持续CSI上报装置的一示意图；
图29是本申请实施例的CSI报告的接收装置的一示意图；
图30是本申请实施例的半持续CSI上报的释放或去激活装置的一示意图；
图31是本申请实施例的半持续CSI上报的释放或去激活装置的一示意图；
图32是本申请实施例的终端设备的构成示意图；
图33是本申请实施例的网络设备的构成示意图。
具体实施方式
参照附图，通过下面的说明书，本申请的前述以及其它特征将变得明显。在说明书和附图中，具体公开了本申请的特定实施方式，其表明了其中可以采用本申请的原则的部分实施方式，应了解的是，本申请不限于所描述的实施方式，相反，本申请包括落入所附权利要求的范围内的全部修改、变型以及等同物。
在本申请实施例中，术语“第一”、“第二”等用于对不同元素从称谓上进行区分，但并不表示这些元素的空间排列或时间顺序等，这些元素不应被这些术语所限制。术语“和/或”包括相关联列出的术语的一种或多个中的任何一个和所有组合。术语“包含”、“包括”、“具有”等是指所陈述的特征、元素、元件或组件的存在，但并不排除存在或添加一个或多个其他特征、元素、元件或组件。
在本申请实施例中，单数形式“一”、“该”等包括复数形式，应广义地理解为“一种”或“一类”而并不是限定为“一个”的含义；此外术语“所述”应理解为既包括单数形式也包括复数形式，除非上下文另外明确指出。此外术语“根据”应理解为“至少部分根据……”，术语“基于”应理解为“至少部分基于……”，除非上下文另外明确指出。
在本申请实施例中，术语“通信网络”或“无线通信网络”可以指符合如下任意通信标准的网络，例如长期演进(LTE，Long Term Evolution)、增强的长期演进(LTE-A，LTE-Advanced)、宽带码分多址接入(WCDMA，Wideband Code Division Multiple Access)、高速报文接入(HSPA，High-Speed Packet Access)、5G(5Generation)新无线(NR，New Radio)等等。
并且，通信系统中设备之间的通信可以根据任意阶段的通信协议进行，例如可以包括但不限于如下通信协议：1G、2G、2.5G、2.75G、3G、4G、4.5G以及5G新无线(NR，New Radio)等等，和/或其他目前已知或未来将被开发的通信协议。
在本申请实施例中，术语“网络设备”例如是指通信系统中将终端设备接入通信网络并为该终端设备提供服务的设备。网络设备可以包括但不限于如下设备：基站(BS，Base Station)、接入点(AP、Access Point)、发送接收点(TRP，Transmission Reception Point)、广播发射机、移动管理实体(MME、Mobile Management Entity)、网关、服务器、无线 网络控制器(RNC，Radio Network Controller)、基站控制器(BSC，Base Station Controller)等等。
其中，基站可以包括但不限于：节点B(NodeB或NB)、演进节点B(eNodeB或eNB)以及5G基站(gNB)，等等，此外还可包括远端无线头(RRH，Remote Radio Head)、远端无线单元(RRU，Remote Radio Unit)、中继(relay)或者低功率节点(例如femeto、pico等等)。并且术语“基站”可以包括它们的一些或所有功能，每个基站可以对特定的地理区域提供通信覆盖。术语“小区”可以指的是基站和/或其覆盖区域，这取决于使用该术语的上下文。
在本申请实施例中，术语“用户设备”(UE，User Equipment)或者“终端设备”(TE，Terminal Equipment或Terminal Device)例如是指通过网络设备接入通信网络并接收网络服务的设备。终端设备可以是固定的或移动的，并且也可以称为移动台(MS，Mobile Station)、终端、用户台(SS，Subscriber Station)、接入终端(AT，Access Terminal)、站，等等。
其中，终端设备可以包括但不限于如下设备：蜂窝电话(Cellular Phone)、个人数字助理(PDA，Personal Digital Assistant)、无线调制解调器、无线通信设备、手持设备、机器型通信设备、膝上型计算机、无绳电话、智能手机、智能手表、数字相机，等等。
再例如，在物联网(IoT，Internet of Things)等场景下，终端设备还可以是进行监控或测量的机器或装置，例如可以包括但不限于：机器类通信(MTC，Machine Type Communication)终端、车载通信终端、设备到设备(D2D，Device to Device)终端、机器到机器(M2M，Machine to Machine)终端，等等。
此外，术语“网络侧”或“网络设备侧”是指网络的一侧，可以是某一基站，也可以包括如上的一个或多个网络设备。术语“用户侧”或“终端侧”或“终端设备侧”是指用户或终端的一侧，可以是某一UE，也可以包括如上的一个或多个终端设备。本文在没有特别指出的情况下，“设备”可以指网络设备，也可以指终端设备。
以下通过示例对本申请实施例的场景进行说明，但本申请不限于此。
图1是本申请实施例的通信系统的示意图，示意性说明了以终端设备和网络设备为例的情况，如图1所示，通信系统100可以包括网络设备101和终端设备102。为简单起见，图1仅以一个网络设备和一个终端设备为例进行说明，但本申请实施例不限于此。
在本申请实施例中，网络设备101和终端设备102之间可以进行现有的业务或者未来可实施的业务发送。例如，这些业务可以包括但不限于：增强的移动宽带(eMBB， enhanced Mobile Broadband)、大规模机器类型通信(mMTC，massive Machine Type Communication)和高可靠低时延通信(URLLC，Ultra-Reliable and Low-Latency Communication)，等等。
在NR中，UE上报CSI的总体过程包括以下步骤：
gNB发送CSI-RS和/或SSB；
UE对CSI-RS和/或PBCH(在SSB中)的DMRS进行测量，包括信道状态测量、干扰测量、L1-RSRP测量等，然后UE上报测量结果给gNB；
gNB根据UE上报的CSI测量结果，进行波束管理、调度等。
在NR中，CSI总体框架包括CSI资源设置和CSI上报设置。CSI资源设置定义了CSI-RS的结构、占用的带宽、时域特性(周期、半持续、非周期)等。CSI上报设置定义了测量报告相关联CSI资源设置、报告的时域特性(周期、半持续、非周期)、报告的数量、报告的频域配置等。
目前，CSI报告类型包括周期CSI上报、非周期CSI上报、在PUCCH上的半持续(semi-persistent，SP)CSI上报以及在PUSCH上的半持续CSI上报。其中，非周期CSI上报和在PUSCH上的SP CSI上报都是由DCI format触发或激活且在PUSCH上发送CSI报告。
发明人发现，由于现有的用于触发/激活/去激活非周期性CSI report以及基于PUSCH的SP CSI report的方法是基于DCI format仅能调度一个小区(或上行载波)的PUSCH的假设进行设计的，其不能直接应用于DCI format可以调度多个小区(或上行载波)的PUSCH的情况。
针对上述问题的至少之一，本申请实施例提供一种信道状态信息的上报方法和装置。
在本申请实施例中，以DCI format 0_X代指用于支持通过一个DCI调度多个小区(或上行载波)的PUSCH的DCI format，对该DCI format的叫法不做限制，可以是DCI format 0_1，和/或DCI format 0_2，和/或DCI format 0_3，等等。
例如，网络设备通过高层信令或参数配置DCI format 0_X所能调度的小区。例如，DCI format 0_X包括用于指示小区和/或上行载波的字段。根据高层信令或参数的配置，该字段的值分别对应一个或多个小区和/或上行载波。由此，当该字段指示多个小区和/或上行载波时，能够实现通过一个DCI调度多个小区和/或上行载波。
在一些实施例中，DCI format 0_X中包括一个或多个用于指示小区和/或上行载波的字段。
在一些实施例中，一个小区可以配置1个上行载波，即(N)UL((normal)UL)，或2个上行载波，即(N)UL和SUL(supplementary UL)。
在一些实施例中，DCI format 0_X既包括用于指示小区的字段，又包括用于指示上行载波的字段。也就是说，上述用于指示小区和/或上行载波的字段可以包括用于指示小区的字段和用于指示小区内的上行载波的字段。例如，若DCI format 0_X所能调度的小区中的一个或多个小区包括2个上行载波(例如(N)UL和SUL)，DCI format 0_X中可以包括一个或多个用于指示小区的字段(例如carrier indicator)和一个或多个用于指示小区内的上行载波的字段(例如UL-SUL indicator)，以指示调度的PUSCH在哪个上行载波。其中，在包括多个用于指示小区内的上行载波的字段的情况下，不同的用于指示小区内的上行载波的字段对应不同的小区或不同的小区集合/小区组。
在一些实施例中，DCI format 0_X仅包括一个用于指示小区和/或上行载波的字段。例如，若DCI format 0_X所能调度的小区中的小区均只包括1个上行载波，DCI format 0_X可以仅包括用于指示小区的字段，或者说，仅包括用于指示上行载波的字段。因为这种情况下，指示小区等价于指示该小区的上行载波。
在本申请实施例中，“调度小区和/或上行载波”等价于“调度在该小区和/或该上行载波上的上行传输(例如PUSCH)”。
在本申请实施例中，多个是指多于一个，或者，两个或两个以上。
在本申请实施例中，“DCI format 0_X由某一RNTI加扰”包括“该DCI format的CRC(循环冗余校验)校验位通过该RNTI进行扰码”。
在本申请实施例中，“用于调度一个或多于一个小区和/或上行载波上的PUSCH”的DCI format，是指：该DCI format至少可以/能够/有能力一次/同时调度多于一个小区和/或上行载波上的PUSCH，该多于一个小区和/或上行载波上分别有一个或多于一个调度的PUSCH；以及，该DCI format可以/能够/有能力一次调度一个小区和/或上行载波上的PUSCH，该一个小区和/或上行载波上有一个或多于一个调度的PUSCH；或者是指：该DCI format至少可以/能够/有能力一次/同时调度多于一个小区和/或上行载波上的PUSCH，该多于一个小区和/或上行载波上分别有一个或多于一个调度的PUSCH；以及，该DCI format不可以/不能够/没有能力一次仅调度一个小区和/或上行载波上的PUSCH。
下面结合附图和具体实施方式对本申请实施例进行说明。
第一方面的实施例
本申请实施例提供一种非周期CSI上报方法，应用在终端设备侧。
图4是本申请实施例的非周期CSI上报方法的一示意图，如图4所示，该方法包括：
401，终端设备接收用于调度一个或多于一个小区和/或上行载波上的PUSCH的DCI format，所述DCI format请求或触发非周期CSI上报；
402，所述终端设备发送CSI报告。
值得注意的是，以上附图4仅对本申请实施例进行了示意性说明，以终端设备为例，但本申请不限于此。例如可以适当地调整各个操作之间的执行顺序，此外还可以增加其他的一些操作或者减少其中的某些操作，此外，还可以调整上述操作的对象。本领域的技术人员可以根据上述内容进行适当地变型，而不仅限于上述附图4的记载。
根据本申请实施例，实现了在DCI format能够调度多个小区的PUSCH的情况下的非周期CSI上报。
在上述实施例中，基于DCI format 0_X的非周期CSI上报包括以下步骤：
基站通过高层信令或参数(例如CSI-AperiodicTriggerStateList)配置一个或多个触发状态(触发状态列表)，每个触发状态对应或关联一个或多个CSI报告配置；
UE监听DCI format 0_X，根据其中的CSI请求字段的值确定哪一个触发状态(CSI非周期触发状态)被触发。
此外，非周期CSI上报可能的CSI-RS配置包括非周期CSI-RS，周期CSI-RS、半持续CSI-RS。非周期CSI上报的时序关系例如图2所示，在图2中，省略了用于测量的参考信号。
在本实施例中，触发状态是指CSI非周期触发状态，CSI上报是指非周期CSI上报。
在本申请实施例中，用于配置触发状态列表的高层参数是DCI format 0_X特定的，或者DCI format 0_X和另一DCI format共用的。特定是指，仅针对DCI format 0_X。共用是指，在配置了监听另一用于触发非周期CSI上报DCI format的情况下，针对该另一DCI format，同时或不同时针对DCI format 0_X和该另一DCI format。同时是指，在配置了监听DCI format 0_X(且DCI format 0_X用于触发非周期CSI上报)和另一用于触发非周期CSI上报的DCI format的情况下，该高层参数既针对DCI format 0_X，也针对该另一DCI format。不同时是指，两个DCI format不能被配置为都需要监听，或者不能被配置为都需要监听且都用于触发非周期CSI上报，进而，该高层参数在具体DCI format 配置情况下仅针对DCI format 0_X或该另一DCI format，而不会同时针对DCI format 0_X和该另一DCI format。
在本申请实施例中，在一些实施例中，上述DCI format调度了一个小区和/或上行载波上的PUSCH，终端设备在该一个小区和/或上行载波上发送上述CSI报告。
在另一些实施例中，在上述DCI format请求或触发非周期CSI上报的情况下，该DCI format仅调度一个小区和/或上行载波上的PUSCH。进而终端设备可以在这一个小区和/或上行载波上发送CSI报告。由此，可以最大限度复用现有的方法，减小复杂度，降低设备升级成本。
例如，该DCI format包括用于请求或触发CSI上报的字段(或信息域)，例如CSI请求字段，该字段的值对应CSI非周期触发状态。当该字段的值对应一个CSI非周期触发状态时，该DCI format仅调度一个小区和/或上行载波上的PUSCH，终端设备在该一个小区和/或上行载波的PUSCH上发送相应的CSI报告。
在上述实施例中，CSI请求字段的长度为N TS(即包括N TS个比特)，由网络设备通过高层参数(例如reportTriggerSize)配置，最多可以指示
Figure PCTCN2022112293-appb-000001
个非周期触发状态。当网络设备通过上述高层信令或参数配置的CSI非周期触发状态没有超过
Figure PCTCN2022112293-appb-000002
个时，CSI请求字段直接指示哪一个状态被请求。当网络设备通过上述高层信令或参数配置的CSI非周期触发状态超过
Figure PCTCN2022112293-appb-000003
个时，网络设备还通过MAC CE(例如CSI非周期触发状态子集选择MAC CE)选择不超过
Figure PCTCN2022112293-appb-000004
个CSI非周期触发状态，然后由CSI请求字段指示哪一个状态被请求。终端设备在接收到上述MAC CE命令到该命令生效之间有一定时延，若承载该MAC CE的PDSCH所对应的HARQ-ACK在时隙n上发送，该CSI非周期触发状态选择的生效时隙是
Figure PCTCN2022112293-appb-000005
在上述实施例中，在一些实施方式中，上述CSI请求字段的长度是由高层参数配置的，该高层参数可以是DCI format 0_X特定的，或者DCI format 0_X和另一DCI format共用的。特定是指，仅针对DCI format 0_X。共用是指，在配置了监听另一用于触发CSI上报DCI format的情况下，针对该另一DCI format，同时或不同时针对DCI format 0_X和该另一DCI format。同时是指，在配置了监听DCI format 0_X(且DCI format 0_X用于触发CSI上报)和另一用于触发CSI上报的DCI format的情况下，该高层参数既针对DCI format 0_X，也针对该另一DCI format。不同时是指，两个DCI format不能被配置为都需要监听，或者不能被配置为都需要监听且都用于触发CSI上报，进而，该高层参 数在具体DCI format配置情况下仅针对DCI format 0_X或该另一DCI format，而不会同时针对DCI format 0_X和该另一DCI format。
在上述实施例中，在另一些实施方式中，上述CSI请求字段的长度不由高层参数确定，而是由终端设备根据配置的相应触发状态列表中的触发状态数量确定。
在又一些实施例中，上述DCI format包括用于指示小区和/或上行载波的字段，该字段指示了一个小区和/或上行载波；终端设备在该字段指示的小区和/或上行载波上发送CSI报告。
例如，DCI format 0_X中包括用于指示小区和/或上行载波的字段，例如载波指示字段，该字段可以指示一个或多个小区和/或上行载波。而在该DCI format 0_X请求或触发非周期CSI上报时，该字段仅指示一个小区和/或上行载波。
图5是非周期CSI上报的一个示例的示意图。
如图5所示，在这个示例中，DCI format 0_X的CRC由C-RNTI或MCS-C-RNTI加扰，CSI请求字段指示了触发的状态，载波指示字段指示了小区和/或上行载波，图5中左边示意了指示的小区为Pcell的情况，图5中右边示意了指示的小区为Scell的情况，终端设备可以在载波指示字段指示的小区和/或上行载波上发送CSI报告。在这个示例中，该PUSCH承载或者不承载UL-SCH数据。
图6是非周期CSI上报的另一个示例的示意图。
如图6所示，在这个示例中，DCI format 0_X的CRC由C-RNTI或MCS-C-RNTI加扰，CSI请求字段指示了触发的状态，载波指示字段指示了小区和/或上行载波，图6中左边示意了指示的小区为Pcell的情况，图6中右边示意了指示的小区为Scell的情况，终端设备可以在载波指示字段指示的小区和/或上行载波上发送CSI报告。在这个示例中，该PUSCH承载或者不承载UL-SCH数据。在这个示例中，与图5的示例不同的是，该DCI format 0_X调度了两个PUSCH。
在又一些实施例中，终端设备在缺省的或由信令配置的用于发送CSI报告的小区和/或上行载波上发送CSI报告。
在上述实施例中，在一些实施方式中，该DCI format包括用于指示小区和/或上行载波的字段，该字段不指示小区和/或上行载波。
例如，DCI format 0_X中包括用于指示调度的小区和/或上行载波的字段，例如载波指示字段，该字段可以指示一个或多个小区和/或上行载波。而在DCI format 0_X请求或触发非周期CSI上报时，该字段不指示小区和/或上行载波。例如，该字段的比特设为 特定值，而该特定值不对应任何小区和/或上行载波。终端设备在缺省的或由信令(例如，RRC和/或MAC CE和/或DCI等)配置的用于发送该CSI报告的小区和/或上行载波发送CSI报告。
图7是非周期CSI上报的一个示例的示意图。
如图7所示，在这个示例中，DCI format 0_X的CRC由C-RNTI或MCS-C-RNTI加扰，CSI请求字段指示了触发的状态，载波指示字段不指示小区和/或上行载波，图7中左边示意了指示的小区为Pcell的情况，图7中右边示意了指示的小区为Scell的情况，终端设备可以在缺省的或由信令配置的小区和/或上行载波上发送CSI报告。在这个示例中，该PUSCH承载或者不承载UL-SCH数据。
图8是非周期CSI上报的另一个示例的示意图。
如图8所示，在这个示例中，DCI format 0_X的CRC由C-RNTI或MCS-C-RNTI加扰，CSI请求字段指示了触发的状态，载波指示字段不指示小区和/或上行载波，图8中左边示意了指示的小区为Pcell的情况，图8中右边示意了指示的小区为Scell的情况，终端设备可以在缺省的或由信令配置的的小区和/或上行载波上发送CSI报告。在这个示例中，该PUSCH承载或者不承载UL-SCH数据。在这个示例中，与图7的示例不同的是，该DCI format 0_X调度了两个PUSCH。
在另一些实施方式中，该DCI format包括用于指示小区和/或上行载波的字段，终端设备忽略该字段。
例如，DCI format 0_X中包括用于指示小区和/或上行载波的字段，例如载波指示字段，该字段可以指示一个或多个小区和/或上行载波。而在DCI format 0_X请求或触发非周期CSI上报时，终端设备忽略该字段。终端设备在缺省的或由信令(例如RRC和/或MAC CE和/或DCI等)配置的用于发送该CSI报告的小区和/或上行载波发送CSI报告。
在又一些实施方式中，DCI format包括用于请求或触发CSI上报的字段，该用于请求或触发CSI上报的字段位于用于指示小区和/或上行载波的字段之前。
在上述实施方式中，在一些示例中，该DCI format请求或触发非周期CSI上报时不包括上述用于指示小区和/或上行载波的字段。
例如，在DCI format 0_X不请求或触发非周期CSI上报时，该DCI format 0_X包括用于指示小区和/或上行载波的字段，例如载波指示字段，该字段可以指示一个或多个小区和/或上行载波。而在DCI format 0_X请求或触发非周期CSI上报时，该DCI format  0_X不包括该载波指示字段。用于请求或触发CSI上报的字段(CSI请求字段)在用于指示小区和/或上行载波的字段(载波指示字段)之前。终端设备在缺省的或由信令(例如RRC和/或MAC CE和/或DCI等)配置的用于发送该CSI报告的小区和/或上行载波发送CSI报告。
在前述各实施例中，缺省的用于发送CSI报告的小区可以是Pcell(主小区)或者Pscell(主辅小区)或者PUCCH Scell(物理上行控制信道辅小区)，本申请不限于此。
其中，如果缺省的小区只包括一个上行载波，则缺省的上行载波即该小区的上行载波；如果缺省的小区包括多于一个上行载波，例如包括NUL和SUL，在该小区的哪个上行载波发送CSI报告例如是由DCI format 0_X用于指示小区内的上行载波的字段(例如UL-SUL indicator)指示的，或者，在该小区的缺省的上行载波发送CSI报告，缺省的上行载波例如是NUL，SUL或该多于一个上行载波中配置了PUCCH的载波。
在本申请实施例中，在另一些实施例中，DCI format调度了一个或多于一个小区和/或上行载波上的PUSCH；终端设备在上述一个或多于一个小区和/或上行载波中的一个小区和/或上行载波上发送CSI报告。
例如，DCI format 0_X在触发非周期CSI上报时，调度一个或多个小区和/或上行载波上的PUSCH，调度多个小区和/或上行载波上的PUSCH时，终端设备在其中一个小区和/或上行载波的PUSCH发送CSI报告；调度一个小区和/或上行载波上的PUSCH时，终端设备采用与前述实施例相同的方法发送CSI报告。由此，可以一定程度复用现在的方法，并且由于网络设备可以在触发CSI上报的同时，通过同一DCI调度多个小区的UL-SCH数据传输，能够增加调度的灵活性及数据传输吞吐量。
在上述实施例中，该DCI format可以包括用于请求或触发CSI上报的字段(或信息域)，例如CSI请求字段，该字段的值对应CSI非周期触发状态。当该字段的值对应一个CSI非周期触发状态时，该DCI调度一个或多个小区和/或上行载波上的PUSCH，终端设备在一个小区和/或上行载波的PUSCH上发送相应的CSI报告。
其中，该字段的长度可以是由高层参数配置的，也可以是由终端设备根据配置的触发状态列表中的触发状态数量确定的。这里，高层参数可以是该DCI format特定的，也可以是该DCI format与其他DCI format共用的。由于在前面的实施例中，已经对该CSI请求字段做了说明，其内容被合并与此，此处不再赘述。
在一些实施例中，上述一个小区和/或上行载波是缺省的或由信令配置的用于发送CSI报告的小区和/或上行载波。也即，终端设备在缺省的或由信令配置的用于发送CSI 报告的小区和/或上行载波发送CSI报告。
在上述实施例中，该DCI format还可以包括用于指示小区和/或上行载波的字段，上述缺省的或由信令配置的用于发送CSI报告的小区和/或上行载波可以在该字段指示的一个或多个小区和/或上行载波的范围内，也可以不在该字段指示的一个或多个小区和/或上行载波的范围内。
例如，DCI format 0_X中包括用于指示小区和/或上行载波的字段，例如载波指示字段，该字段可以指示一个或多个小区和/或上行载波。而在DCI format 0_X请求或触发非周期CSI上报时，如该字段指示了多个小区和/或上行载波，终端设备在其中一个小区和/或上行载波上的PUSCH发送CSI报告。该其中一个小区和/或上行载波是缺省的或由信令(例如RRC和/或MAC CE和/或DCI等)配置的用于发送该CSI报告的小区和/或上行载波。
图9是非周期CSI上报的一个示例的示意图。
如图9所示，在这个示例中，DCI format 0_X的CRC由C-RNTI或MCS-C-RNTI加扰，CSI请求字段指示了触发的状态，载波指示字段指示小区和/或上行载波，图9中左边示意了指示的小区为Pcell和Scell的情况，图9中右边示意了指示的小区为两个Scell的情况，终端设备可以在缺省的或由信令配置的小区和/或上行载波上发送CSI报告。在这个示例中，该PUSCH承载或者不承载UL-SCH数据。此外，在这个示例中，该DCI format 0_X关联两个PUSCH，其中一个承载CSI报告，另一个不承载CSI报告。
图10是非周期CSI上报的另一个示例的示意图。
如图10所示，在这个示例中，DCI format 0_X的CRC由C-RNTI或MCS-C-RNTI加扰，CSI请求字段指示了触发的状态，载波指示字段指示小区和/或上行载波，图10中左边示意了指示的小区为Pcell和Scell的情况，图10中右边示意了指示的小区为两个Scell的情况，终端设备可以在缺省的或由信令配置的小区和/或上行载波上发送CSI报告。在这个示例中，该PUSCH承载或者不承载UL-SCH数据。此外，在这个示例中，该DCI format 0_X关联两个PUSCH，其中一个承载CSI报告，另一个不承载CSI报告。与图9的示例不同的是，在图10的示例中，两个PUSCH在时域上是错开的。
在上述图9和图10的示例中，没有示出一个小区和/或上行载波有多个PUSCH的情况，但本申请实施例不排除这种情况。也即，图9和图10仅示出了一个小区和/或上行载波上仅有一个PUSCH，在本申请实施例中，一个小区和/或上行载波上还可以有其他PUSCH。
在上述实施例中，该缺省的用于发送CSI报告的小区可以是：调度的小区中服务小区标识号最小的小区；和/或，调度的PUSCH中时域上第一个满足非周期CSI上报时序要求的PUSCH所在的小区；和/或，调度的PUSCH中时域上第一个满足非周期CSI上报时序要求的PUSCH所在的小区中服务小区标识号最小的小区。本申请不限于此，该缺省的用于发送CSI报告的小区也可以根据其他规则定义的其他小区。
在上述实施例中，该缺省的用于发送CSI报告的小区可以是Pcell或者PScell或者PUCCH Scell，本申请不限于此。
在另一些实施例中，终端设备在缺省的PUCCH上发送CSI报告。
在上述实施例中，该DCI format还可以包括用于指示小区和/或上行载波的字段。
例如，DCI format 0_X中包括用于指示小区和/或上行载波的字段，例如载波指示字段，该字段可以指示一个或多个小区和/或上行载波。而在DCI format 0_X请求或触发非周期CSI上报时，如该字段指示了多个小区和/或上行载波，终端设备在其中一个缺省的PUSCH发送CSI报告。
图11是非周期CSI上报的一个示例的示意图。
如图11所示，在这个示例中，DCI format 0_X的CRC由C-RNTI或MCS-C-RNTI加扰，CSI请求字段指示了触发的状态，载波指示字段指示小区和/或上行载波，图11中左边示意了指示的小区为Pcell和Scell的情况，图11中右边示意了指示的小区为两个Scell的情况，终端设备可以在缺省的PUSCH上发送CSI报告。在这个示例中，该PUSCH承载或者不承载UL-SCH数据。此外，在这个示例中，该DCI format 0_X关联两个PUSCH，其中一个承载CSI报告，另一个不承载CSI报告。与图9的示例不同的是，在图11的示例中，两个PUSCH在时域上是错开的。
在上述图11的示例中，没有示出一个小区和/或上行载波有多个PUSCH的情况，但本申请实施例不排除这种情况。也即，图11仅示出了一个小区和/或上行载波上仅有一个PUSCH，在本申请实施例中，一个小区和/或上行载波上还可以有其他PUSCH。
在上述实施例中，该缺省的PUSCH可以是：调度的小区中服务小区标识号最小的小区的PUSCH；和/或，调度的PUSCH中时域上第一个满足非周期CSI上报时序要求的PUSCH；和/或，调度的PUSCH中时域上第一个满足非周期CSI上报时序要求的PUSCH中所在小区中服务小区标识号最小的小区的PUSCH。本申请不限于此，该缺省的PUSCH也可以是根据其他规则定义的其他PUSCH。
在上述实施例中，该缺省的PUSCH所在的小区可以是Pcell或者PScell或者PUCCH  Scell，本申请不限于此。
在本申请实施例中，在又一些实施例中，DCI format调度了多于一个小区和/或上行载波上的PUSCH；终端设备在上述多于一个小区和/或上行载波中的一个或多于一个小区和/或上行载波上发送CSI报告。
例如，DCI format 0_X在触发非周期CSI上报时，调度一个或多个小区和/或上行载波上的PUSCH，调度多个小区和/或上行载波上的PUSCH时，终端设备在其中一个或部分或全部小区和/或上行载波的PUSCH发送CSI报告；调度一个小区和/或上行载波上的PUSCH时，终端设备采用与前述实施例相同的方法发送CSI报告。由此，由于网络设备通过同一DCI触发终端设备在其中一个或多个或全部小区和/或上行载波发送CSI报告，并且可以在触发CSI上报的同时，通过同一DCI调度多个小区的UL-SCH数据传输，在各载波带宽较小的情况下，能够提高CSI反馈效率，同时能够增加调度的灵活性及数据传输吞吐量。
在上述实施例中，该DCI format可以包括用于指示小区和/或上行载波的字段，该字段指示了上述多于一个小区和/或上行载波。
例如，DCI format 0_X中包括用于指示小区和/或上行载波的字段，例如载波指示字段，该字段可以指示一个或多个小区和/或上行载波。在指示调度了多个小区和/或上行载波的情况下，终端设备在多于一个小区和/或上行载波的PUSCH上发送CSI报告。
在上述实施例中，不同PUSCH上的CSI报告的内容可以相同，也可以不同。
在一些实施方式中，上述DCI format包括一个用于请求或触发CSI上报的字段，不同PUSCH上的CSI报告相同，和/或，不同PUSCH分别用于承载所述字段关联的触发状态对应的不同的CSI报告，和/或，不同PUSCH分别用于承载所述CSI报告的不同部分。
例如，DCI format 0_X包括一个用于请求或触发CSI的字段，例如CSI请求字段，不同PUSCH上的CSI报告相同(重复)，和/或，不同PUSCH分别用于承载该字段指示的触发状态对应的不同CSI报告(其中，一个触发状态可以对应一个或多个CSI报告)，和/或，不同PUSCH分别用于承载CSI报告的不同部分(例如，分别承载Part 1和Part 2)。
在一些实施方式中，上述DCI format包括多个用于请求或触发CSI上报的字段，不同PUSCH分别用于承载不同的用于请求或触发CSI上报的字段关联的触发状态对应的CSI报告。
例如，DCI format 0_X包括多个用于请求或触发CSI的字段，例如CSI请求字段，不同字段分别对应不同的小区和/或上行载波，也就是说，不同PUSCH分别用于承载不同的用于请求或触发CSI的字段指示的触发状态对应的CSI报告。
图12是非周期CSI上报的一个示例的示意图。
如图12所示，在这个示例中，DCI format 0_X的CRC由C-RNTI或MCS-C-RNTI加扰，一个或多个CSI请求字段指示了触发的状态，载波指示字段指示小区和/或上行载波，图12中左边示意了指示的小区为Pcell和Scell的情况，图12中右边示意了指示的小区为两个Scell的情况，终端设备可以在两个小区和/或上行载波上发送CSI报告，并且中两个小区和/或上行载波上的CSI报告的内容可以相同，也可以不同。在这个示例中，该PUSCH承载或者不承载UL-SCH数据。在这个示例中，该DCI format 0_X调度了两个PUSCH。
在本申请实施例中，该DCI format的CRC可以由C-RNTI加扰，也可以由MCS-C-RNTI加扰，本申请不限于此。
在本申请实施例中，终端设备还可以接收用于配置该终端设备在UE特定的搜索空间监听该DCI format的配置信息。本申请对具体的配置方式不做限制，关于该配置信息的相关内容，可以参考相关技术。
在本申请实施例中，终端设备还可以接收用于配置上述DCI format是否支持触发CSI上报或者上述DCI format是否用于触发CSI上报的配置信息。本申请对具体的配置方式不做限制，关于该配置信息的相关内容，可以参考相关技术。
在本申请实施例中，终端设备还可以接收用于配置上述DCI format所能调度的小区和/或上行载波的配置信息。本申请对具体的配置方式不做限制，关于该配置信息的相关内容，可以参考相关技术。
在本申请实施例中，上述多于一个上行载波可以分别是不同小区的，或者，上述多于一个上行载波中的至少两个是不同小区的，本申请不限于此。
以上各个实施例仅对本申请实施例进行了示例性说明，但本申请不限于此，还可以在以上各个实施例的基础上进行适当的变型。例如，可以单独使用上述各个实施例，也可以将以上各个实施例中的一种或多种结合起来。
由上述实施例可知，实现了在DCI format能够调度多个小区的PUSCH的情况下的非周期CSI上报。
第二方面的实施例
本申请实施例提供一种CSI报告的接收方法，应用于网络设备侧，是与第一方面的实施例的方法对应的网络设备侧的处理，其中与第一方面的实施例相同的内容不再赘述。
图13是本申请实施例的CSI报告的接收方法的一示意图，如图13所示，该方法包括：
1301，网络设备发送用于调度一个或多于一个小区和/或上行载波上的PUSCH的DCI format，所述DCI format请求或触发非周期CSI上报；
1302，所述网络设备接收CSI报告。
值得注意的是，以上附图13仅对本申请实施例进行了示意性说明，但本申请不限于此。例如可以适当地调整各个操作之间的执行顺序，此外还可以增加其他的一些操作或者减少其中的某些操作。本领域的技术人员可以根据上述内容进行适当地变型，而不仅限于上述附图13的记载。
根据本申请实施例，实现了在DCI format能够调度多个小区的PUSCH的情况下的非周期CSI上报。
在一些实施例中，上述DCI format调度了一个小区和/或上行载波上的PUSCH，网络设备在该一个小区和/或上行载波上接收所述CSI报告。
在一些实施例中，在所述DCI format请求或触发非周期CSI上报的情况下，该DCI format仅调度一个小区和/或上行载波上的PUSCH。
在一些实施例中，上述DCI format包括用于指示小区和/或上行载波的字段，该字段指示了一个小区和/或上行载波；网络设备在该字段指示的小区和/或上行载波上接收CSI报告。
在一些实施例中，网络设备在缺省的或由信令配置的用于接收CSI报告的小区和/或上行载波上接收CSI报告。
在上述实施例中，在一些实施方式中，上述DCI format包括用于指示小区和/或上行载波的字段，该字段不指示小区和/或上行载波。
在上述实施例中，在另一些实施方式中，上述DCI format包括用于指示小区和/或上行载波的字段，终端设备忽略该字段。
在一些实施例中，上述DCI format包括用于请求或触发CSI上报的字段，该用于请求或触发CSI上报的字段位于用于指示小区和/或上行载波的字段之前。
在一些实施例中，上述DCI format请求或触发非周期CSI上报时不包括用于指示小 区和/或上行载波的字段。
在一些实施例中，上述缺省的用于接收CSI报告的小区为：Pcell或PScell或PUCCH Scell。
在一些实施例中，上述DCI format调度了一个或多于一个小区和/或上行载波上的PUSCH；网络设备在该一个或多于一个小区和/或上行载波中的一个小区和/或上行载波上接收所述CSI报告。
在前述各实施例中，上述DCI format可以包括用于请求或触发CSI上报的字段，该字段的值对应CSI非周期触发状态。
在上述实施例中，上述字段的长度可以是由高层参数配置的，也可以是终端设备根据配置的触发状态列表中的触发状态数量确定的。前述高层参数可以是该DCI format特定的，也可以是该DCI format与其他DCI format共用的。
在一些实施例中，上述一个小区和/或上行载波是缺省的或由信令配置的用于发送CSI报告的小区和/或上行载波。
在上述实施例中，该缺省的用于发送CSI报告的小区可以为以下至少之一：
调度的小区中服务小区标识号最小的小区；
调度的PUSCH中时域上第一个满足非周期CSI上报时序要求的PUSCH所在的小区；
调度的PUSCH中时域上第一个满足非周期CSI上报时序要求的PUSCH所在的小区中服务小区标识号最小的小区。
在上述实施例中，该缺省的用于发送CSI报告的小区可以为：Pcell或PScell或PUCCH Scell。
在一些实施例中，网络设备在缺省的PUSCH上接收所述CSI报告。
在上述实施例中，该缺省的PUSCH可以为以下至少之一：
调度的小区中服务小区标识号最小的小区的PUSCH；
调度的PUSCH中时域上第一个满足非周期CSI上报时序要求的PUSCH；
调度的PUSCH中时域上第一个满足非周期CSI上报时序要求的PUSCH中所在小区中服务小区标识号最小的小区的PUSCH。
在上述实施例中，该缺省的PUSCH所在的小区可以为：Pcell或PScell或PUCCH Scell。
在一些实施例中，上述DCI format包括用于指示小区和/或上行载波的字段。
在上述实施例中，前述缺省的或由信令配置的用于发送CSI报告的小区和/或上行载波在上述字段指示的一个或多个小区和/或上行载波的范围内，或者不在上述字段指示的一个或多个小区和/或上行载波的范围内。
在一些实施例中，上述DCI format调度了多于一个小区和/或上行载波上的PUSCH；网络设备在该多于一个小区和/或上行载波中的一个或多于一个小区和/或上行载波上接收CSI报告。
在上述实施例中，上述DCI format可以包括用于指示小区和/或上行载波的字段，该字段指示了前述多于一个小区和/或上行载波。
在上述实施例中，不同PUSCH上的CSI报告的内容可以相同或不同。
在上述实施例中，上述DCI format可以包括一个用于请求或触发CSI上报的字段，不同PUSCH上的CSI报告相同，和/或，不同PUSCH分别用于承载所述字段关联的触发状态对应的不同的CSI报告，和/或，不同PUSCH分别用于承载所述CSI报告的不同部分。
在上述实施例中，上述DCI format可以包括多个用于请求或触发CSI上报的字段，不同PUSCH分别用于承载不同的用于请求或触发CSI上报的字段关联的触发状态对应的CSI报告。
在前述各实施例中，上述DCI format的CRC可以由C-RNTI加扰或者由MCS-C-RNTI加扰。
在前述各实施例中，网络设备还可以发送用于配置终端设备在UE特定的搜索空间监听上述DCI format的配置信息。
在前述各实施例中，网络设备还可以发送用于配置上述DCI format是否支持触发CSI上报或者上述DCI format是否用于触发CSI上报的配置信息。
在前述各实施例中，网络设备还可以发送用于配置上述DCI format所能调度的小区和/或上行载波的配置信息。
在前述各实施例中，上述多于一个上行载波可以分别是不同小区的，或者，上述多于一个上行载波的中的至少两个可以是不同小区的。
以上各个实施例仅对本申请实施例进行了示例性说明，但本申请不限于此，还可以在以上各个实施例的基础上进行适当的变型。例如，可以单独使用上述各个实施例，也可以将以上各个实施例中的一种或多种结合起来。
由上述实施例可知，实现了在DCI format能够调度多个小区的PUSCH的情况下的 非周期CSI上报。
第三方面的实施例
本申请实施例提供一种半持续CSI上报方法，应用在终端设备侧。
图14是本申请实施例的半持续CSI上报方法的一示意图，如图14所示，该方法包括：
1401，终端设备接收用于调度一个或多于一个小区和/或上行载波上的PUSCH的DCI format，所述DCI format触发或激活半持续CSI上报；
1402，所述终端设备发送CSI报告。
值得注意的是，以上附图14仅对本申请实施例进行了示意性说明，以终端设备为例，但本申请不限于此。例如可以适当地调整各个操作之间的执行顺序，此外还可以增加其他的一些操作或者减少其中的某些操作，此外，还可以调整上述操作的对象。本领域的技术人员可以根据上述内容进行适当地变型，而不仅限于上述附图14的记载。
根据本申请实施例，实现了在DCI format能够调度多个小区的PUSCH的情况下的半持续CSI上报。
针对在PUSCH上的SP CSI上报，基站通过高层信令或参数配置上报的周期、时隙偏移等，并通过由SP-CSI-RNTI加扰的DCI format触发。
基于DCI format 0_X的SP CSI上报包括以下步骤：
基站通过高层信令或参数(例如CSI-SemiPersistentOnPUSCH-TriggerStateList)配置一个或多个触发状态(触发状态列表)。每个触发状态对应/关联一个或多个CSI报告配置；
UE监听由SP-CSI-RNTI加扰的DCI format 0_X，根据其中的CSI请求字段的值确定哪一个触发状态(SP-CSI触发状态)被触发或激活。CSI请求字段的值等于0对应上述列表中的第1个触发状态，CSI请求字段的值等于1对应上述列表中的第2个触发状态，依此类推。
其中，SP CSI上报可能的CSI-RS配置包括周期CSI-RS、半持续CSI-RS等。基于PUSCH的SP CSI上报的时序关系如图3所示，在图3中，省略了用于测量的参考信号。
在本申请实施例中，用于配置触发状态列表的高层参数是DCI format 0_X特定的，或者DCI format 0_X和另一DCI format共用的。特定是指，仅针对DCI format 0_X。共用是指，在配置了监听另一用于触发SP-CSI上报DCI format的情况下，针对该另一DCI  format，同时或不同时针对DCI format 0_X和该另一DCI format。同时是指，在配置了监听DCI format 0_X(且DCI format 0_X用于触发SP-CSI上报)和另一用于触发SP-CSI上报的DCI format的情况下，该高层参数既针对DCI format 0_X，也针对该另一DCI format。不同时是指，两个DCI format不能被配置为都需要监听，或者不能被配置为都需要监听且都用于触发SP-CSI上报，进而，该高层参数在具体DCI format配置情况下仅针对DCI format 0_X或该另一DCI format，而不会同时针对DCI format 0_X和该另一DCI format。
在本实施例中，触发状态是指半持续CSI触发状态，CSI上报是指半持续CSI上报。
在本申请实施例中，在一些实施例中，上述DCI format调度了一个小区和/或上行载波上的PUSCH，终端设备在该一个小区和/或上行载波上发送上述CSI报告。
在另一些实施例中，在上述DCI format触发或激活半持续CSI上报的情况下，该DCI format仅调度一个小区和/或上行载波上的PUSCH。进而终端设备可以在这一个小区和/或上行载波上发送CSI报告。由此，可以最大限度复用现有的方法，减小复杂度，降低设备升级成本。
例如，该DCI format包括用于触发或激活CSI上报的字段(或信息域)，例如CSI请求字段，该字段的值对应CSI触发状态。当该字段的值对应一个CSI触发状态时，该DCI format仅调度一个小区和/或上行载波上的PUSCH，终端设备在该一个小区和/或上行载波的PUSCH上发送相应的CSI报告。
在上述实施例中，CSI请求字段的长度为N TS(即包括N TS个比特)，由网络设备通过高层参数(例如reportTriggerSize)配置，最多可以指示
Figure PCTCN2022112293-appb-000006
个触发状态。当网络设备通过上述高层信令或参数配置的CSI发状态没有超过
Figure PCTCN2022112293-appb-000007
个时，CSI请求字段直接指示哪一个状态被请求。当网络设备通过上述高层信令或参数配置的CSI触发状态超过
Figure PCTCN2022112293-appb-000008
个时，网络设备还通过MAC CE(例如CSI触发状态子集选择MAC CE)选择不超过
Figure PCTCN2022112293-appb-000009
个CSI触发状态，然后由CSI请求字段指示哪一个状态被请求。终端设备在接收到上述MAC CE命令到该命令生效之间有一定时延，若承载该MAC CE的PDSCH所对应的HARQ-ACK在时隙n上发送，该CSI触发状态选择的生效时隙是
Figure PCTCN2022112293-appb-000010
Figure PCTCN2022112293-appb-000011
在上述实施例中，在一些实施方式中，上述CSI请求字段的长度是由高层参数配置的，该高层参数可以是DCI format 0_X特定的，或者DCI format 0_X和另一DCI format 共用的。特定是指，仅针对DCI format 0_X。共用是指，在配置了监听另一用于触发CSI上报DCI format的情况下，针对该另一DCI format，同时或不同时针对DCI format 0_X和该另一DCI format。同时是指，在配置了监听DCI format 0_X(且DCI format 0_X用于触发CSI上报)和另一用于触发CSI上报的DCI format的情况下，该高层参数既针对DCI format 0_X，也针对该另一DCI format。不同时是指，两个DCI format不能被配置为都需要监听，或者不能被配置为都需要监听且都用于触发CSI上报，进而，该高层参数在具体DCI format配置情况下仅针对DCI format 0_X或该另一DCI format，而不会同时针对DCI format 0_X和该另一DCI format。
在上述实施例中，在另一些实施方式中，上述CSI请求字段的长度不由高层参数确定，而是由终端设备根据配置的相应触发状态列表中的触发状态数量确定。
在又一些实施例中，上述DCI format包括用于指示小区和/或上行载波的字段，该字段指示了一个小区和/或上行载波；终端设备在该字段指示的小区和/或上行载波上发送CSI报告。
例如，DCI format 0_X中包括用于指示小区和/或上行载波的字段，例如载波指示字段，该字段可以指示一个或多个小区和/或上行载波。而在该DCI format 0_X触发或激活半持续CSI上报时，该字段仅指示一个小区和/或上行载波。
图15是半持续CSI上报的一个示例的示意图。
如图15所示，在这个示例中，DCI format 0_X的CRC由SP-CSI-RNTI加扰，CSI请求字段指示了触发的状态，载波指示字段指示了小区和/或上行载波，图15中左边示意了指示的小区为Pcell的情况，图15中右边示意了指示的小区为Scell的情况，终端设备可以在载波指示字段指示的小区和/或上行载波上发送CSI报告。如图15所示，该CSI报告是半持续的。在这个示例中，该PUSCH承载或者不承载UL-SCH数据。
图16是半持续CSI上报的另一个示例的示意图。
如图16所示，在这个示例中，DCI format 0_X的CRC由SP-CSI-RNTI加扰，CSI请求字段指示了触发的状态，载波指示字段指示了小区和/或上行载波，图16中左边示意了指示的小区为Pcell的情况，图16中右边示意了指示的小区为Scell的情况，终端设备可以在载波指示字段指示的小区和/或上行载波上发送CSI报告。如图16所示，该CSI报告是半持续的。在这个示例中，该PUSCH承载或者不承载UL-SCH数据。在这个示例中，与图15的示例不同的是，该DCI format 0_X调度了两个PUSCH。
在又一些实施例中，终端设备在缺省的或由信令配置的用于发送CSI报告的小区和 /或上行载波上发送CSI报告。
在上述实施例中，在一些实施方式中，该DCI format包括用于指示小区和/或上行载波的字段，该字段不指示小区和/或上行载波。
例如，DCI format 0_X中包括用于指示调度的小区和/或上行载波的字段，例如载波指示字段，该字段可以指示一个或多个小区和/或上行载波。而在DCI format 0_X触发或激活半持续CSI上报时，该字段不指示小区和/或上行载波。例如，该字段的比特设为特定值，而该特定值不对应任何小区和/或上行载波。终端设备在缺省的或由信令(例如，RRC和/或MAC CE和/或DCI等)配置的用于发送该CSI报告的小区和/或上行载波发送CSI报告。
图17是半持续CSI上报的一个示例的示意图。
如图17所示，在这个示例中，DCI format 0_X的CRC由SP-CSI-RNTI加扰，CSI请求字段指示了触发的状态，载波指示字段不指示小区和/或上行载波，图17中左边示意了指示的小区为Pcell的情况，图17中右边示意了指示的小区为Scell的情况，终端设备可以在缺省的或由信令配置的小区和/或上行载波上发送CSI报告。如图17所示，该CSI报告是半持续的。在这个示例中，该PUSCH承载或者不承载UL-SCH数据。
图18是半持续CSI上报的另一个示例的示意图。
如图18所示，在这个示例中，DCI format 0_X的CRC由SP-CSI-RNTI加扰，CSI请求字段指示了触发的状态，载波指示字段不指示小区和/或上行载波，图18中左边示意了指示的小区为Pcell的情况，图18中右边示意了指示的小区为Scell的情况，终端设备可以在缺省的或由信令配置的的小区和/或上行载波上发送CSI报告。如图18所示，该CSI报告是半持续的。在这个示例中，该PUSCH承载或者不承载UL-SCH数据。在这个示例中，与图17的示例不同的是，该DCI format 0_X调度了两个PUSCH。
在另一些实施方式中，该DCI format包括用于指示小区和/或上行载波的字段，终端设备忽略该字段。
例如，DCI format 0_X中包括用于指示小区和/或上行载波的字段，例如载波指示字段，该字段可以指示一个或多个小区和/或上行载波。而在DCI format 0_X触发或激活半持续CSI上报时，终端设备忽略该字段。终端设备在缺省的或由信令(例如RRC和/或MAC CE和/或DCI等)配置的用于发送该CSI报告的小区和/或上行载波发送CSI报告。
在又一些实施方式中，DCI format包括用于触发或激活CSI上报的字段，该用于触 发或激活CSI上报的字段位于用于指示小区和/或上行载波的字段之前。
在上述实施方式中，在一些示例中，该DCI format触发或激活半持续CSI上报时不包括上述用于指示小区和/或上行载波的字段。
例如，在DCI format 0_X不触发或激活半持续CSI上报时，该DCI format 0_X包括用于指示小区和/或上行载波的字段，例如载波指示字段，该字段可以指示一个或多个小区和/或上行载波。而在DCI format 0_X触发或激活半持续CSI上报时，该DCI format 0_X不包括该载波指示字段。用于触发或激活CSI上报的字段(CSI请求字段)在用于指示小区和/或上行载波的字段(载波指示字段)之前。终端设备在缺省的或由信令(例如RRC和/或MAC CE和/或DCI等)配置的用于发送该CSI报告的小区和/或上行载波发送CSI报告。
在前述各实施例中，缺省的用于发送CSI报告的小区可以是Pcell或者Pscell或者PUCCH Scell，本申请不限于此。
其中，如果缺省的小区只包括一个上行载波，则缺省的上行载波即该小区的上行载波；如果缺省的小区包括多于一个上行载波，例如包括NUL和SUL，则缺省的上行载波例如是NUL，SUL或该多于一个上行载波中配置了PUCCH的载波。
在本申请实施例中，在另一些实施例中，DCI format调度了一个或多于一个小区和/或上行载波上的PUSCH；终端设备在上述一个或多于一个小区和/或上行载波中的一个小区和/或上行载波上发送CSI报告。
例如，DCI format 0_X在触发或激活半持续CSI上报时，调度一个或多个小区和/或上行载波上的PUSCH，调度多个小区和/或上行载波上的PUSCH时，终端设备在其中一个小区和/或上行载波的PUSCH发送CSI报告；调度一个小区和/或上行载波上的PUSCH时，终端设备采用与前述实施例相同的方法发送CSI报告。由此，可以一定程度复用现在的方法，并且由于网络设备可以在触发或激活半持续CSI上报的同时，通过同一DCI调度多个小区的UL-SCH数据传输，能够增加调度的灵活性及数据传输吞吐量。
在上述实施例中，该DCI format可以包括用于触发或激活CSI上报的字段(或信息域)，例如CSI请求字段，该字段的值对应CSI触发状态。当该字段的值对应一个CSI触发状态时，该DCI调度一个或多个小区和/或上行载波上的PUSCH，终端设备在一个小区和/或上行载波的PUSCH上发送相应的CSI报告。
其中，该字段的长度可以是由高层参数配置的，也可以是由终端设备根据配置的触 发状态列表中的触发状态数量确定的。这里，高层参数可以是该DCI format特定的，也可以是该DCI format与其他DCI format共用的。由于在前面的实施例中，已经对该CSI请求字段做了说明，其内容被合并与此，此处不再赘述。
在一些实施例中，上述一个小区和/或上行载波是缺省的或由信令配置的用于发送CSI报告的小区和/或上行载波。也即，终端设备在缺省的或由信令配置的用于发送CSI报告的小区和/或上行载波发送CSI报告。
在上述实施例中，该DCI format还可以包括用于指示小区和/或上行载波的字段，上述缺省的或由信令配置的用于发送CSI报告的小区和/或上行载波可以在该字段指示的一个或多个小区和/或上行载波的范围内，也可以不在该字段指示的一个或多个小区和/或上行载波的范围内。
例如，DCI format 0_X中包括用于指示小区和/或上行载波的字段，例如载波指示字段，该字段可以指示一个或多个小区和/或上行载波。而在DCI format 0_X触发或激活半持续CSI上报时，如该字段指示了多个小区和/或上行载波，终端设备在其中一个小区和/或上行载波上的PUSCH发送CSI报告。该其中一个小区和/或上行载波是缺省的或由信令(例如RRC和/或MAC CE和/或DCI等)配置的用于发送该CSI报告的小区和/或上行载波。
图19是半持续CSI上报的一个示例的示意图。
如图19所示，在这个示例中，DCI format 0_X的CRC由SP-CSI-RNTI加扰，CSI请求字段指示了触发的状态，载波指示字段指示小区和/或上行载波，图19中左边示意了指示的小区为Pcell和Scell的情况，图19中右边示意了指示的小区为两个Scell的情况，终端设备可以在缺省的或由信令配置的小区和/或上行载波上发送CSI报告。如图19所示，该CSI报告是半持续的。在这个示例中，该PUSCH承载或者不承载UL-SCH数据。此外，在这个示例中，该DCI format 0_X关联两个PUSCH，其中一个承载CSI报告，另一个不承载CSI报告。
图20是半持续CSI上报的另一个示例的示意图。
如图20所示，在这个示例中，DCI format 0_X的CRC由SP-CSI-RNTI加扰，CSI请求字段指示了触发的状态，载波指示字段指示小区和/或上行载波，图20中左边示意了指示的小区为Pcell和Scell的情况，图20中右边示意了指示的小区为两个Scell的情况，终端设备可以在缺省的或由信令配置的小区和/或上行载波上发送CSI报告。如图20所示，该CSI报告是半持续的。在这个示例中，该PUSCH承载或者不承载UL-SCH 数据。此外，在这个示例中，该DCI format 0_X关联两个PUSCH，其中一个承载CSI报告，另一个不承载CSI报告。与图19的示例不同的是，在图20的示例中，两个PUSCH在时域上是错开的。
在上述图19和图20的示例中，没有示出一个小区和/或上行载波有多个PUSCH的情况，但本申请实施例不排除这种情况。也即，图19和图20仅示出了一个小区和/或上行载波上仅有一个PUSCH，在本申请实施例中，一个小区和/或上行载波上还可以有其他PUSCH。
在上述实施例中，该缺省的用于发送CSI报告的小区可以是：调度的小区中服务小区标识号最小的小区；和/或，调度的PUSCH中时域上第一个满足半持续CSI上报时序要求的PUSCH所在的小区；和/或，调度的PUSCH中时域上第一个满足半持续CSI上报时序要求的PUSCH所在的小区中服务小区标识号最小的小区。本申请不限于此，该缺省的用于发送CSI报告的小区也可以根据其他规则定义的其他小区。
在上述实施例中，该缺省的用于发送CSI报告的小区可以是Pcell或者PScell或者PUCCH Scell，本申请不限于此。
在另一些实施例中，终端设备在缺省的PUCCH上发送CSI报告。
在上述实施例中，该DCI format还可以包括用于指示小区和/或上行载波的字段。
例如，DCI format 0_X中包括用于指示小区和/或上行载波的字段，例如载波指示字段，该字段可以指示一个或多个小区和/或上行载波。而在DCI format 0_X触发或激活半持续CSI上报时，如该字段指示了多个小区和/或上行载波，终端设备在其中一个缺省的PUSCH发送CSI报告。
图21是半持续CSI上报的一个示例的示意图。
如图21所示，在这个示例中，DCI format 0_X的CRC由SP-CSI-RNTI加扰，CSI请求字段指示了触发的状态，载波指示字段指示小区和/或上行载波，图21中左边示意了指示的小区为Pcell和Scell的情况，图21中右边示意了指示的小区为两个Scell的情况，终端设备可以在缺省的PUSCH上发送CSI报告。如图21所示，该CSI报告是半持续的。在这个示例中，该PUSCH承载或者不承载UL-SCH数据。此外，在这个示例中，该DCI format 0_X关联两个PUSCH，其中一个承载CSI报告，另一个不承载CSI报告。与图19的示例不同的是，在图21的示例中，两个PUSCH在时域上是错开的。
在上述图21的示例中，没有示出一个小区和/或上行载波有多个PUSCH的情况，但本申请实施例不排除这种情况。也即，图21仅示出了一个小区和/或上行载波上仅有一 个PUSCH，在本申请实施例中，一个小区和/或上行载波上还可以有其他PUSCH。
在上述实施例中，该缺省的PUSCH可以是：调度的小区中服务小区标识号最小的小区的PUSCH；和/或，调度的PUSCH中时域上第一个满足半持续CSI上报时序要求的PUSCH；和/或，调度的PUSCH中时域上第一个满足半持续CSI上报时序要求的PUSCH中所在小区中服务小区标识号最小的小区的PUSCH。本申请不限于此，该缺省的PUSCH也可以是根据其他规则定义的其他PUSCH。
在上述实施例中，该缺省的PUSCH所在的小区可以是Pcell或者PScell或者PUCCH Scell，本申请不限于此。
在本申请实施例中，在又一些实施例中，DCI format调度了多于一个小区和/或上行载波上的PUSCH；终端设备在上述多于一个小区和/或上行载波中的一个或多于一个小区和/或上行载波上发送CSI报告。
例如，DCI format 0_X在触发或激活半持续CSI上报时，调度一个或多个小区和/或上行载波上的PUSCH，调度多个小区和/或上行载波上的PUSCH时，终端设备在其中一个或部分或全部小区和/或上行载波的PUSCH发送CSI报告；调度一个小区和/或上行载波上的PUSCH时，终端设备采用与前述实施例相同的方法发送CSI报告。由此，由于网络设备通过同一DCI触发终端设备在其中一个或多个或全部小区和/或上行载波发送CSI报告，并且可以在触发CSI上报的同时，通过同一DCI调度多个小区的UL-SCH数据传输，在各载波带宽较小的情况下，能够提高CSI反馈效率，同时能够增加调度的灵活性及数据传输吞吐量。
在上述实施例中，该DCI format可以包括用于指示小区和/或上行载波的字段，该字段指示了上述多于一个小区和/或上行载波。
例如，DCI format 0_X中包括用于指示小区和/或上行载波的字段，例如载波指示字段，该字段可以指示一个或多个小区和/或上行载波。在指示调度了多个小区和/或上行载波的情况下，终端设备在多于一个小区和/或上行载波的PUSCH上发送CSI报告。
在上述实施例中，不同PUSCH上的CSI报告的内容可以相同，也可以不同。
在一些实施方式中，上述DCI format包括一个用于触发或激活CSI上报的字段，不同PUSCH上的CSI报告相同，和/或，不同PUSCH分别用于承载所述字段关联的触发状态对应的不同的CSI报告，和/或，不同PUSCH分别用于承载所述CSI报告的不同部分。
例如，DCI format 0_X包括一个用于触发或激活CSI的字段，例如CSI请求字段， 不同PUSCH上的CSI报告相同(重复)，和/或，不同PUSCH分别用于承载该字段指示的触发状态对应的不同CSI报告(其中，一个触发状态可以对应一个或多个CSI报告)，和/或，不同PUSCH分别用于承载CSI报告的不同部分(例如，分别承载Part 1和Part2)。
在一些实施方式中，上述DCI format包括多个用于触发或激活CSI上报的字段，不同PUSCH分别用于承载不同的用于触发或激活CSI上报的字段关联的触发状态对应的CSI报告。
例如，DCI format 0_X包括多个用于触发或激活CSI的字段，例如CSI请求字段，不同字段分别对应不同的小区和/或上行载波，也就是说，不同PUSCH分别用于承载不同的用于触发或激活CSI的字段指示的触发状态对应的CSI报告。
图22是半持续CSI上报的一个示例的示意图。
如图22所示，在这个示例中，DCI format 0_X的CRC由SP-CSI-RNTI加扰，一个或多个CSI请求字段指示了触发的状态，载波指示字段指示小区和/或上行载波，图22中左边示意了指示的小区为Pcell和Scell的情况，图22中右边示意了指示的小区为两个Scell的情况，终端设备可以在两个小区和/或上行载波上发送CSI报告，并且中两个小区和/或上行载波上的CSI报告的内容可以相同，也可以不同。在这个示例中，该PUSCH承载或者不承载UL-SCH数据。在这个示例中，该DCI format 0_X调度了两个PUSCH。
在图15至图22中，以不同小区和/或上行载波上的SP-CSI上报周期相同为例，但本申请不限于此，不同小区和/或上行载波上的SP-CSI上报周期可以相同，也可以不同。
在本申请实施例中，该DCI format的CRC可以由SP-CSI-RNTI加扰，本申请不限于此。
在本申请实施例中，终端设备还可以确定/确认(validates)上述DCI format对于半持续CSI激活的有效性。
在一些实施例中，终端设备根据上述DCI format中用于指示小区和/或上行载波的字段和/或用于指示HARQ(混合自动重传请求)进程ID的字段和/或用于指示RV(冗余版本)的字段确定/确认(validates)上述有效性。
例如，上述DCI format中包括多个用于指示HARQ进程ID的字段，终端设备根据该DCI format中的部分或全部用于指示小区和/或上行载波的字段确定/确认(validates)上述有效性。
再例如，上述DCI format中包括多个用于指示RV的字段，终端设备根据该DCI format中的部分或全部用于指示RV的字段确定/确认(validates)上述有效性。
再例如，上述DCI format中包括一个或多个用于指示小区和/或上行载波的字段，终端设备根据该DCI format中的部分或全部用于小区和/或上行载波的字段确定/确认(validates)上述有效性。
在前述各实施例中，确定/确认(validates)上述有效性的上述各实施例可以单独使用，也可以结合使用，本申请不做限制。在前述各实施例中，如果确认DCI format是无效的，则终端设备忽略或丢弃该DCI format。或者说，如果确认DCI format是无效的，终端设备假设该DCI format的CRC不匹配，或者假设CRC校验失败。
在前述各实施例中，有效的DCI format中的上述字段应满足一定条件。
例如，该用于指示小区和/或上行载波的字段应指示一个小区和/或上行载波，和/或，该字段指示的小区和/或上行载波是Pcell或PScell或PUCCH Scell。再例如，该字段应为特定值，该特定值不对应任何小区和/或上行载波。
此外，如果DCI format 0_X中包括多个用于指示HARQ process ID的字段(例如HARQ process number字段)和/或多个用于指示RV的字段(例如Redundancy version字段)，多个字段都应满足以下条件。或者，用于指示小区和/或上行载波的字段指示的小区和/或上行载波对应的用于指示HARQ process ID的字段和/或用于指示RV的字段应满足以下条件。可选地，终端设备忽略其他用于指示HARQ process ID的字段和/或用于指示RV的字段。
这些条件是指下面表格所示的配置。
  DCI format 0_1
HARQ process number set to all'0's
Redundancy version set to'00'
以上各个实施例仅对本申请实施例进行了示例性说明，但本申请不限于此，还可以在以上各个实施例的基础上进行适当的变型。例如，可以单独使用上述各个实施例，也可以将以上各个实施例中的一种或多种结合起来。
由上述实施例可知，实现了在DCI format能够调度多个小区的PUSCH的情况下的半持续CSI上报。
第四方面的实施例
本申请实施例提供一种CSI报告的接收方法，应用于网络设备侧，是与第三方面的 实施例的方法对应的网络设备侧的处理，其中与第三方面的实施例相同的内容不再赘述。
图23是本申请实施例的CSI报告的接收方法的一示意图，如图23所示，该方法包括：
2301，网络设备发送用于调度一个或多于一个小区和/或上行载波上的PUSCH的DCI format，所述DCI format触发或激活半持续CSI上报；
2302，所述网络设备接收CSI报告。
值得注意的是，以上附图23仅对本申请实施例进行了示意性说明，但本申请不限于此。例如可以适当地调整各个操作之间的执行顺序，此外还可以增加其他的一些操作或者减少其中的某些操作。本领域的技术人员可以根据上述内容进行适当地变型，而不仅限于上述附图23的记载。
根据本申请实施例，实现了在DCI format能够调度多个小区的PUSCH的情况下的半持续CSI上报。
在一些实施例中，上述DCI format调度了一个小区和/或上行载波上的PUSCH，网络设备在上述一个小区和/或上行载波上接收CSI报告。
在一些实施例中，在上述DCI format触发或激活半持续CSI上报的情况下，上述DCI format仅调度一个小区和/或上行载波上的PUSCH。
在一些实施例中，上述DCI format包括用于指示小区和/或上行载波的字段，该字段指示了一个小区和/或上行载波；网络设备在该字段指示的小区和/或上行载波上接收CSI报告。
在一些实施例中，网络设备在缺省的或由信令配置的用于发送CSI报告的小区和/或上行载波上接收所述CSI报告。
在上述实施例中，在一些实施方式中，上述DCI format包括用于指示小区和/或上行载波的字段，该字段不指示小区和/或上行载波。
在上述实施例中，在一些实施方式中，上述DCI format包括用于指示小区和/或上行载波的字段，终端设备忽略该字段。
在上述实施例中，在一些实施方式中，上述DCI format包括用于请求或触发CSI上报的字段，该用于请求或触发CSI上报的字段位于用于指示小区和/或上行载波的字段之前。
在上述实施方式中，上述DCI format触发或激活半持续CSI上报时不包括用于指示小区和/或上行载波的字段。
在上述实施例中，上述缺省的用于发送CSI报告的小区可以为：Pcell或PScell或PUCCH Scell。
在一些实施例中，上述DCI format调度了一个或多于一个小区和/或上行载波上的PUSCH；网络设备在上述一个或多于一个小区和/或上行载波中的一个小区和/或上行载波上接收CSI报告。
在前述各实施例中，上述DCI format可以包括用于请求或触发CSI上报的字段，该字段的值对应CSI触发状态。
在上述实施例中，该字段的长度可以是由高层参数配置的，并且，该高层参数是上述DCI format特定的，或者是上述DCI format与其他DCI format共用的。
在上述实施例中，该字段的长度也可以是终端设备根据配置的触发状态列表中的触发状态数量确定的。
在前述各实施例中，上述一个小区和/或上行载波是缺省的或由信令配置的用于发送CSI报告的小区和/或上行载波。
例如，该缺省的用于发送CSI报告的小区可以为以下至少之一：
调度的小区中服务小区标识号最小的小区；
调度的PUSCH中时域上第一个满足半持续CSI上报时序要求的PUSCH所在的小区；
调度的PUSCH中时域上第一个满足半持续CSI上报时序要求的PUSCH所在的小区中服务小区标识号最小的小区。
再例如，该缺省的用于发送CSI报告的小区可以为：Pcell或PScell或PUCCH Scell。
在一些实施例中，网络设备在缺省的PUSCH上接收所述CSI报告。
例如，该缺省的PUSCH可以为以下至少之一：
调度的小区中服务小区标识号最小的小区的PUSCH；
调度的PUSCH中时域上第一个满足半持续CSI上报时序要求的PUSCH；
调度的PUSCH中时域上第一个满足半持续CSI上报时序要求的PUSCH中所在小区中服务小区标识号最小的小区的PUSCH。
再例如，该缺省的PUSCH所在的小区可以为：Pcell或PScell或PUCCH Scell。
在一些实施例中，上述DCI format包括用于指示小区和/或上行载波的字段。
在上述实施例中，上述缺省的或由信令配置的用于发送CSI报告的小区和/或上行载波在上述字段指示的一个或多个小区和/或上行载波的范围内，或者不在上述字段指示 的一个或多个小区和/或上行载波的范围内。
在一些实施例中，上述DCI format调度了多于一个小区和/或上行载波上的PUSCH；网络设备在该多于一个小区和/或上行载波中的一个或多于一个小区和/或上行载波上接收CSI报告。
在上述实施例中，上述DCI format还可以包括用于指示小区和/或上行载波的字段，该字段指示了上述多于一个小区和/或上行载波。
在上述实施例中，不同PUSCH上的CSI报告的内容可以相同或不同。
在上述实施例中，上述DCI format还可以包括一个用于触发或激活CSI上报的字段，不同PUSCH上的CSI报告相同，和/或，不同PUSCH分别用于承载所述字段关联的触发状态对应的不同的CSI报告，和/或，不同PUSCH分别用于承载所述CSI报告的不同部分。
在上述实施例中，上述DCI format还可以包括多个用于触发或激活CSI上报的字段，不同PUSCH分别用于承载不同的用于请求或触发CSI上报的字段关联的触发状态对应的CSI报告。
在前述各实施例中，上述DCI format的CRC可以由SP-CSI-RNTI加扰。
以上各个实施例仅对本申请实施例进行了示例性说明，但本申请不限于此，还可以在以上各个实施例的基础上进行适当的变型。例如，可以单独使用上述各个实施例，也可以将以上各个实施例中的一种或多种结合起来。
由上述实施例可知，实现了在DCI format能够调度多个小区的PUSCH的情况下的半持续CSI上报。
第五方面的实施例
本申请实施例提供一种半持续CSI上报的释放或去激活方法，应用在终端设备侧。
图24是本申请实施例的半持续CSI上报的释放或去激活方法的示意图，如图24所示，该方法包括：
2401，终端设备接收用于调度一个或多于一个小区和/或上行载波上的PUSCH的DCI format，所述DCI format释放或去激活半持续CSI上报；
2402，所述终端设备去激活半持续CSI上报。
值得注意的是，以上附图24仅对本申请实施例进行了示意性说明，以终端设备为例，但本申请不限于此。例如可以适当地调整各个操作之间的执行顺序，此外还可以增 加其他的一些操作或者减少其中的某些操作，此外，还可以调整上述操作的对象。本领域的技术人员可以根据上述内容进行适当地变型，而不仅限于上述附图24的记载。
根据本申请实施例，实现了在DCI format能够调度多个小区的PUSCH的情况下的半持续CSI上报的释放或去激活。
在一些实施例中，上述DCI format包括用于指示小区和/或上行载波的字段，该字段指示了一个小区或上行载波，和/或，该字段指示的小区和/或上行载波是Pcell或PScell或PUCCH Scell，和/或，该字段为特定值，该特定值不对应任何小区和/或上行载波。
在上述实施例中，终端设备在validate时还考虑了用于指示调度的小区和/或上行载波的字段。
在一些实施例中，终端设备确定/确认(validates)上述DCI format对于半持续CSI释放/去激活的有效性。
例如，终端设备可以根据上述DCI format中用于指示小区和/或上行载波的字段和/于指示HARQ进程ID的字段和/或用于指示RV的字段和/或多个用于指示MCS的字段和/或多个用于指示频域资源(RB)分配确定/确认(validates)上述有效性。
在上述示例中，上述DCI format中可以包括多个用于指示HARQ进程ID的字段，终端设备可以根据所述DCI format中的部分或全部用于指示小区和/或上行载波的字段确定/确认(validates)上述有效性。
在上述示例中，上述DCI format中可以包括多个用于指示RV的字段，终端设备可以根据该DCI format中的部分或全部用于指示RV的字段确定/确认(validates)上述有效性。
在上述示例中，上述DCI format中还可以包括一个或多个用于指示小区和/或上行载波的字段，终端设备可以根据该DCI format中的部分或全部用于小区和/或上行载波的字段确定/确认(validates)上述有效性。
在上述示例中，上述DCI format中还可以包括多个用于指示MCS的字段，终端设备可以根据该DCI format中的部分或全部用于指示小区和/或上行载波的字段确定/确认(validates)上述有效性。
在上述示例中，上述DCI format中还可以包括用于指示频域资源(RB)分配的字段，终端设备卡伊根据该DCI format中的部分或全部用于指示小区和/或上行载波的字段确定/确认(validates)上述有效性。
在前述各示例中，如果上述DCI format是无效的，终端设备还可以忽略或丢弃该 DCI format。或者说，如果确认DCI format是无效的，终端设备假设该DCI format的CRC不匹配，或者假设CRC校验失败。
在本申请实施例中，如果DCI format 0_X中包括多个用于指示HARQ process ID的字段(例如HARQ process number字段)和/或多个用于指示RV的字段(例如Redundancy version字段)和/或多个用于支持MCS的字段和/或多个用于指示频域资源(RB)分配的字段，则该多个字段都应满足以下条件。或者，用于指示调度的小区和/或上行载波的字段指示的小区和/或上行载波对应的上述字段应满足以下条件。可选地，终端设备忽略其他用于指示HARQ process ID的字段。
这些条件是指下列表格中列出的配置。
Figure PCTCN2022112293-appb-000012
以上各个实施例仅对本申请实施例进行了示例性说明，但本申请不限于此，还可以在以上各个实施例的基础上进行适当的变型。例如，可以单独使用上述各个实施例，也可以将以上各个实施例中的一种或多种结合起来。
由上述实施例可知，实现了在DCI format能够调度多个小区的PUSCH的情况下的半持续CSI上报的释放或去激活。
第六方面的实施例
本申请实施例提供一种半持续CSI上报的释放或去激活方法，应用于网络设备侧，是与第五方面的实施例的方法对应的网络设备侧的处理，其中与第五方面的实施例相同的内容不再赘述。
图25是本申请实施例的半持续CSI上报的释放或去激活方法的一示意图，如图25所示，该方法包括：
2501，网络设备发送用于调度一个或多于一个小区和/或上行载波上的PUSCH的 DCI format，所述DCI format释放或去激活半持续CSI上报。
值得注意的是，以上附图25仅对本申请实施例进行了示意性说明，但本申请不限于此。例如可以增加其他的一些操作。本领域的技术人员可以根据上述内容进行适当地变型，而不仅限于上述附图25的记载。
根据本申请实施例，实现了在DCI format能够调度多个小区的PUSCH的情况下的半持续CSI上报的释放或去激活。
在一些实施例中，上述DCI format包括用于指示小区和/或上行载波的字段，该字段指示了一个小区或上行载波，和/或，该字段指示的小区和/或上行载波是Pcell或PScell或PUCCH Scell，和/或，该字段为特定值，该特定值不对应任何小区和/或上行载波。
以上各个实施例仅对本申请实施例进行了示例性说明，但本申请不限于此，还可以在以上各个实施例的基础上进行适当的变型。例如，可以单独使用上述各个实施例，也可以将以上各个实施例中的一种或多种结合起来。
由上述实施例可知，实现了在DCI format能够调度多个小区的PUSCH的情况下的半持续CSI上报的释放或去激活。
在前述第一方面至第六方面的实施例中，对支持通过一个DCI调度一个或多个小区和/或上行载波的PUSCH的DCI format(记为DCI format 0_X)做了说明。下面的表格是该DCI format 0_X的字段的一个具体示例。
表：DCI format 0_X的域的摘要
Figure PCTCN2022112293-appb-000013
Figure PCTCN2022112293-appb-000014
在上述示例中，“type-1field”是：向所有共同调度小区指示公共信息的单个字段，或者经由联合指示向每个共同调度小区指示单独的信息的单个字段；或者仅向共同调度小区中的一个指示信息的单个字段。在DCI format 0_X中，只包括一个该字段。
在上述示例中，“type-2field”是：用于每个共同调度小区的单独字段，或者包括一个或多个共同调度小区的每个子组的单独字段，其中，单个字段通常应用于属于同一子组的共同调度小区。在DCI format 0_X中，包括多个该字段。
在上述示例中，“type-3field”与每个共同调度小区或每个子组共用或分开。在DCI format 0_X中，包括一个或多个该字段，取决于显式配置或通过隐式方式确定，例如带 内或带间CA，FR1或FR2。
在上述示例中，UL-SCH indicator用于指示用于承载CSI报告的PUSCH是否同时承载UL-SCH数据。
在上述示例中，域是指字段，也可以称为信息域。
第七方面的实施例
本申请实施例提供一种非周期CSI上报装置。该装置例如可以是终端设备，也可以是配置于终端设备的某个或某些部件或者组件，与第一至第二方面的实施例相同的内容不再赘述。
图26是本申请实施例的非周期CSI上报装置的一示意图。如图26所示，本申请实施例的非周期CSI上报装置2600包括：
接收单元2601，其接收用于调度一个或多于一个小区和/或上行载波上的PUSCH的DCI format，所述DCI format请求或触发非周期CSI上报；以及
发送单元2602，其发送CSI报告。
在一些实施例中，所述DCI format调度了一个小区和/或上行载波上的PUSCH，发送单元2602在所述一个小区和/或上行载波上发送所述CSI报告。
在一些实施例中，在所述DCI format请求或触发非周期CSI上报的情况下，所述DCI format仅调度一个小区和/或上行载波上的PUSCH。
在一些实施例中，所述DCI format包括用于指示小区和/或上行载波的字段，所述字段指示了一个小区和/或上行载波；发送单元2602在所述字段指示的所述小区和/或上行载波上发送所述CSI报告。
在一些实施例中，发送单元2602在缺省的或由信令配置的用于发送CSI报告的小区和/或上行载波上发送所述CSI报告。
在一些实施例中，所述DCI format包括用于指示小区和/或上行载波的字段，所述字段不指示小区和/或上行载波。
在一些实施例中，所述DCI format包括用于指示小区和/或上行载波的字段，发送单元2602忽略所述字段。
在一些实施例中，所述DCI format包括用于请求或触发CSI上报的字段，所述用于请求或触发CSI上报的字段位于用于指示小区和/或上行载波的字段之前。
在一些实施例中，所述DCI format请求或触发非周期CSI上报时不包括用于指示小 区和/或上行载波的字段。
在一些实施例中，所述缺省的用于发送CSI报告的小区为：Pcell或PScell或PUCCH Scell。
在一些实施例中，所述DCI format调度了一个或多于一个小区和/或上行载波上的PUSCH；发送单元2602在所述一个或多于一个小区和/或上行载波中的一个小区和/或上行载波上发送所述CSI报告。
在一些实施例中，所述DCI format包括用于请求或触发CSI上报的字段，所述字段的值对应CSI非周期触发状态。
在一些实施例中，所述字段的长度是由高层参数配置的，并且，所述高层参数是所述DCI format特定的，或者是所述DCI format与其他DCI format共用的。
在一些实施例中，所述字段的长度是所述终端设备根据配置的触发状态列表中的触发状态数量确定的。
在一些实施例中，所述一个小区和/或上行载波是缺省的或由信令配置的用于发送CSI报告的小区和/或上行载波。
在一些实施例中，所述缺省的用于发送CSI报告的小区为以下至少之一：
调度的小区中服务小区标识号最小的小区；
调度的PUSCH中时域上第一个满足非周期CSI上报时序要求的PUSCH所在的小区；
调度的PUSCH中时域上第一个满足非周期CSI上报时序要求的PUSCH所在的小区中服务小区标识号最小的小区。
在一些实施例中，所述缺省的用于发送CSI报告的小区为：Pcell或PScell或PUCCH Scell。
在一些实施例中，发送单元2602在缺省的PUSCH上发送所述CSI报告。
在一些实施例中，所述缺省的PUSCH为以下至少之一：
调度的小区中服务小区标识号最小的小区的PUSCH；
调度的PUSCH中时域上第一个满足非周期CSI上报时序要求的PUSCH；
调度的PUSCH中时域上第一个满足非周期CSI上报时序要求的PUSCH中所在小区中服务小区标识号最小的小区的PUSCH。
在一些实施例中，所述缺省的PUSCH所在的小区为：Pcell或PScell或PUCCH Scell。
在一些实施例中，所述DCI format包括用于指示小区和/或上行载波的字段。
在一些实施例中，所述缺省的或由信令配置的用于发送CSI报告的小区和/或上行载波在所述字段指示的一个或多个小区和/或上行载波的范围内，或者不在所述字段指示的一个或多个小区和/或上行载波的范围内。
在一些实施例中，所述DCI format调度了多于一个小区和/或上行载波上的PUSCH；发送单元2602在所述多于一个小区和/或上行载波中的一个或多于一个小区和/或上行载波上发送所述CSI报告。
在一些实施例中，所述DCI format包括用于指示小区和/或上行载波的字段，所述字段指示了所述多于一个小区和/或上行载波。
在一些实施例中，不同PUSCH上的CSI报告的内容相同或不同。
在一些实施例中，所述DCI format包括一个用于请求或触发CSI上报的字段，不同PUSCH上的CSI报告相同，和/或，不同PUSCH分别用于承载所述字段关联的触发状态对应的不同的CSI报告，和/或，不同PUSCH分别用于承载所述CSI报告的不同部分。
在一些实施例中，所述DCI format包括多个用于请求或触发CSI上报的字段，不同PUSCH分别用于承载不同的用于请求或触发CSI上报的字段关联的触发状态对应的CSI报告。
在一些实施例中，所述DCI format的CRC由C-RNTI加扰或者由MCS-C-RNTI加扰。
在一些实施例中，接收单元2601还接收用于配置所述终端设备在UE特定的搜索空间监听所述DCI format的配置信息。
在一些实施例中，接收单元2601还接收用于配置所述DCI format是否支持触发CSI上报或者所述DCI format是否用于触发CSI上报的配置信息。
在一些实施例中，接收单元2601还接收用于配置所述DCI format所能调度的小区和/或上行载波的配置信息。
在一些实施例中，所述多于一个上行载波分别是不同小区的，或者，所述多于一个上行载波的中的至少两个是不同小区的。
本申请实施例还提供一种CSI报告的接收装置。该装置例如可以是网络设备，也可以是配置于网络设备的某个或某些部件或者组件，与第一至第二方面的实施例相同的内容不再赘述。
图27是本申请实施例的CSI报告的接收装置的一示意图。如图27所示，本申请实 施例的CSI报告的接收装置2700包括：
发送单元2701，其发送用于调度一个或多于一个小区和/或上行载波上的PUSCH的DCI format，所述DCI format请求或触发非周期CSI上报；
接收单元2702，其接收CSI报告。
在一些实施例中，所述DCI format调度了一个小区和/或上行载波上的PUSCH，接收单元2702在所述一个小区和/或上行载波上接收所述CSI报告。
在一些实施例中，在所述DCI format请求或触发非周期CSI上报的情况下，所述DCI format仅调度一个小区和/或上行载波上的PUSCH。
在一些实施例中，所述DCI format包括用于指示小区和/或上行载波的字段，所述字段指示了一个小区和/或上行载波；接收单元2702在所述字段指示的所述小区和/或上行载波上接收所述CSI报告。
在一些实施例中，接收单元2702在缺省的或由信令配置的用于接收CSI报告的小区和/或上行载波上接收所述CSI报告。
在一些实施例中，所述DCI format包括用于指示小区和/或上行载波的字段，所述字段不指示小区和/或上行载波。
在一些实施例中，所述DCI format包括用于指示小区和/或上行载波的字段，所述终端设备忽略所述字段。
在一些实施例中，所述DCI format包括用于请求或触发CSI上报的字段，所述用于请求或触发CSI上报的字段位于用于指示小区和/或上行载波的字段之前。
在一些实施例中，所述DCI format请求或触发非周期CSI上报时不包括用于指示小区和/或上行载波的字段。
在一些实施例中，所述缺省的用于接收CSI报告的小区为：Pcell或PScell或PUCCH Scell。
在一些实施例中，所述DCI format调度了一个或多于一个小区和/或上行载波上的PUSCH；接收单元2702在所述一个或多于一个小区和/或上行载波中的一个小区和/或上行载波上接收所述CSI报告。
在一些实施例中，所述DCI format包括用于请求或触发CSI上报的字段，所述字段的值对应CSI非周期触发状态。
在一些实施例中，所述字段的长度是由高层参数配置的，并且，所述高层参数是所述DCI format特定的，或者是所述DCI format与其他DCI format共用的。
在一些实施例中，所述字段的长度是所述终端设备根据配置的触发状态列表中的触发状态数量确定的。
在一些实施例中，所述一个小区和/或上行载波是缺省的或由信令配置的用于接收CSI报告的小区和/或上行载波。
在一些实施例中，所述缺省的用于接收CSI报告的小区为以下至少之一：
调度的小区中服务小区标识号最小的小区；
调度的PUSCH中时域上第一个满足非周期CSI上报时序要求的PUSCH所在的小区；
调度的PUSCH中时域上第一个满足非周期CSI上报时序要求的PUSCH所在的小区中服务小区标识号最小的小区。
在一些实施例中，所述缺省的用于接收CSI报告的小区为：Pcell或PScell或PUCCH Scell。
在一些实施例中，接收单元2702在缺省的PUSCH上接收所述CSI报告。
在一些实施例中，所述缺省的PUSCH为以下至少之一：
调度的小区中服务小区标识号最小的小区的PUSCH；
调度的PUSCH中时域上第一个满足非周期CSI上报时序要求的PUSCH；
调度的PUSCH中时域上第一个满足非周期CSI上报时序要求的PUSCH中所在小区中服务小区标识号最小的小区的PUSCH。
在一些实施例中，所述缺省的PUSCH所在的小区为：Pcell或PScell或PUCCH Scell。
在一些实施例中，所述DCI format包括用于指示小区和/或上行载波的字段。
在一些实施例中，所述缺省的或由信令配置的用于接收CSI报告的小区和/或上行载波在所述字段指示的一个或多个小区和/或上行载波的范围内，或者不在所述字段指示的一个或多个小区和/或上行载波的范围内。
在一些实施例中，所述DCI format调度了多于一个小区和/或上行载波上的PUSCH；所述网络设备在所述多于一个小区和/或上行载波中的一个或多于一个小区和/或上行载波上接收所述CSI报告。
在一些实施例中，所述DCI format包括用于指示小区和/或上行载波的字段，所述字段指示了所述多于一个小区和/或上行载波。
在一些实施例中，不同PUSCH上的CSI报告的内容相同或不同。
在一些实施例中，所述DCI format包括一个用于请求或触发CSI上报的字段，不同 PUSCH上的CSI报告相同，和/或，不同PUSCH分别用于承载所述字段关联的触发状态对应的不同的CSI报告，和/或，不同PUSCH分别用于承载所述CSI报告的不同部分。
在一些实施例中，所述DCI format包括多个用于请求或触发CSI上报的字段，不同PUSCH分别用于承载不同的用于请求或触发CSI上报的字段关联的触发状态对应的CSI报告。
在一些实施例中，所述DCI format的CRC由C-RNTI加扰或者由MCS-C-RNTI加扰。
在一些实施例中，发送单元2701还发送用于配置所述终端设备在UE特定的搜索空间监听所述DCI format的配置信息。
在一些实施例中，发送单元2701还发送用于配置所述DCI format是否支持触发CSI上报或者所述DCI format是否用于触发CSI上报的配置信息。
在一些实施例中，发送单元2701还发送用于配置所述DCI format所能调度的小区和/或上行载波的配置信息。
在一些实施例中，所述多于一个上行载波分别是不同小区的，或者，所述多于一个上行载波的中的至少两个是不同小区的。
本申请实施例还提供一种半持续CSI上报装置。该装置例如可以是终端设备，也可以是配置于终端设备的某个或某些部件或者组件，与第三至第四方面的实施例相同的内容不再赘述。
图28是本申请实施例的半持续CSI上报装置的一示意图。如图28所示，本申请实施例的半持续CSI上报装置2800包括：
接收单元2801，其接收用于调度一个或多于一个小区和/或上行载波上的PUSCH的DCI format，所述DCI format触发或激活半持续CSI上报；
发送单元2802，其发送CSI报告。
在一些实施例中，所述DCI format调度了一个小区和/或上行载波上的PUSCH，发送单元2802在所述一个小区和/或上行载波上发送所述CSI报告。
在一些实施例中，在所述DCI format触发或激活半持续CSI上报的情况下，所述DCI format仅调度一个小区和/或上行载波上的PUSCH。
在一些实施例中，所述DCI format包括用于指示小区和/或上行载波的字段，所述字段指示了一个小区和/或上行载波；发送单元2802在所述字段指示的所述小区和/或上行 载波上发送所述CSI报告。
在一些实施例中，发送单元2802在缺省的或由信令配置的用于发送CSI报告的小区和/或上行载波上发送所述CSI报告。
在一些实施例中，所述DCI format包括用于指示小区和/或上行载波的字段，所述字段不指示小区和/或上行载波。
在一些实施例中，所述DCI format包括用于指示小区和/或上行载波的字段，发送单元2802忽略所述字段。
在一些实施例中，所述DCI format包括用于请求或触发CSI上报的字段，所述用于请求或触发CSI上报的字段位于用于指示小区和/或上行载波的字段之前。
在一些实施例中，所述DCI format触发或激活半持续CSI上报时不包括用于指示小区和/或上行载波的字段。
在一些实施例中，所述缺省的用于发送CSI报告的小区为：Pcell或PScell或PUCCH Scell。
在一些实施例中，所述DCI format调度了一个或多于一个小区和/或上行载波上的PUSCH；发送单元2802在所述一个或多于一个小区和/或上行载波中的一个小区和/或上行载波上发送所述CSI报告。
在一些实施例中，所述DCI format包括用于请求或触发CSI上报的字段，所述字段的值对应CSI触发状态。
在一些实施例中，所述字段的长度是由高层参数配置的，并且，所述高层参数是所述DCI format特定的，或者是所述DCI format与其他DCI format共用的。
在一些实施例中，所述字段的长度是所述终端设备根据配置的触发状态列表中的触发状态数量确定的。
在一些实施例中，所述一个小区和/或上行载波是缺省的或由信令配置的用于发送CSI报告的小区和/或上行载波。
在一些实施例中，所述缺省的用于发送CSI报告的小区为以下至少之一：
调度的小区中服务小区标识号最小的小区；
调度的PUSCH中时域上第一个满足半持续CSI上报时序要求的PUSCH所在的小区；
调度的PUSCH中时域上第一个满足半持续CSI上报时序要求的PUSCH所在的小区中服务小区标识号最小的小区。
在一些实施例中，所述缺省的用于发送CSI报告的小区为：Pcell或PScell或PUCCH Scell。
在一些实施例中，发送单元2802在缺省的PUSCH上发送所述CSI报告。
在一些实施例中，所述缺省的PUSCH为以下至少之一：
调度的小区中服务小区标识号最小的小区的PUSCH；
调度的PUSCH中时域上第一个满足非周期CSI上报时序要求的PUSCH；
调度的PUSCH中时域上第一个满足非周期CSI上报时序要求的PUSCH中所在小区中服务小区标识号最小的小区的PUSCH。
在一些实施例中，所述缺省的PUSCH所在的小区为：Pcell或PScell或PUCCH Scell。
在一些实施例中，所述DCI format包括用于指示小区和/或上行载波的字段。
在一些实施例中，所述缺省的或由信令配置的用于发送CSI报告的小区和/或上行载波在所述字段指示的一个或多个小区和/或上行载波的范围内，或者不在所述字段指示的一个或多个小区和/或上行载波的范围内。
在一些实施例中，所述DCI format调度了多于一个小区和/或上行载波上的PUSCH；发送单元2802在所述多于一个小区和/或上行载波中的一个或多于一个小区和/或上行载波上发送所述CSI报告。
在一些实施例中，所述DCI format包括用于指示小区和/或上行载波的字段，所述字段指示了所述多于一个小区和/或上行载波。
在一些实施例中，不同PUSCH上的CSI报告的内容相同或不同。
在一些实施例中，所述DCI format包括一个用于触发或激活CSI上报的字段，不同PUSCH上的CSI报告相同，和/或，不同PUSCH分别用于承载所述字段关联的触发状态对应的不同的CSI报告，和/或，不同PUSCH分别用于承载所述CSI报告的不同部分。
在一些实施例中，所述DCI format包括多个用于触发或激活CSI上报的字段，不同PUSCH分别用于承载不同的用于请求或触发CSI上报的字段关联的触发状态对应的CSI报告。
在一些实施例中，所述DCI format的CRC由SP-CSI-RNTI加扰。
在一些实施例中，如图28所示，装置2800还包括：
确定/确认单元2803，其确定/确认(validates)所述DCI format对于半持续CSI激活的有效性。
在一些实施例中，确定/确认单元2803根据所述DCI format中用于指示小区和/或上行载波的字段和/或用于指示HARQ进程ID的字段和/或用于指示RV的字段确定/确认(validates)所述有效性。
在一些实施例中，所述DCI format中包括多个用于指示HARQ进程ID的字段，确定/确认单元2803根据所述DCI format中的部分或全部用于指示小区和/或上行载波的字段确定/确认(validates)所述有效性。
在一些实施例中，所述DCI format中包括多个用于指示RV的字段，确定/确认单元2803根据所述DCI format中的部分或全部用于指示RV的字段确定/确认(validates)所述有效性。
在一些实施例中，所述DCI format中包括一个或多个用于指示小区和/或上行载波的字段，确定/确认单元2803根据所述DCI format中的部分或全部用于小区和/或上行载波的字段确定/确认(validates)所述有效性。
在一些实施例中，如果所述DCI format是无效的，接收单元2801忽略/丢弃所述DCI format。
本申请实施例还提供一种CSI报告的接收装置。该装置例如可以是网络设备，也可以是配置于网络设备的某个或某些部件或者组件，与第三至第四方面的实施例相同的内容不再赘述。
图29是本申请实施例的CSI报告的接收装置的一示意图。如图29所示，本申请实施例的CSI报告的接收装置2900包括：
发送单元2901，其发送用于调度一个或多于一个小区和/或上行载波上的PUSCH的DCI format，所述DCI format触发或激活半持续CSI上报；
接收单元2902，其接收CSI报告。
在一些实施例中，所述DCI format调度了一个小区和/或上行载波上的PUSCH，接收单元2902在所述一个小区和/或上行载波上接收所述CSI报告。
在一些实施例中，在所述DCI format触发或激活半持续CSI上报的情况下，所述DCI format仅调度一个小区和/或上行载波上的PUSCH。
在一些实施例中，所述DCI format包括用于指示小区和/或上行载波的字段，所述字段指示了一个小区和/或上行载波；接收单元2902在所述字段指示的所述小区和/或上行载波上接收所述CSI报告。
在一些实施例中，接收单元2902在缺省的或由信令配置的用于接收CSI报告的小 区和/或上行载波上接收所述CSI报告。
在一些实施例中，所述DCI format包括用于指示小区和/或上行载波的字段，所述字段不指示小区和/或上行载波。
在一些实施例中，所述DCI format包括用于指示小区和/或上行载波的字段，所述终端设备忽略所述字段。
在一些实施例中，所述DCI format包括用于请求或触发CSI上报的字段，所述用于请求或触发CSI上报的字段位于用于指示小区和/或上行载波的字段之前。
在一些实施例中，所述DCI format触发或激活半持续CSI上报时不包括用于指示小区和/或上行载波的字段。
在一些实施例中，所述缺省的用于接收CSI报告的小区为：Pcell或PScell或PUCCH Scell。
在一些实施例中，所述DCI format调度了一个或多于一个小区和/或上行载波上的PUSCH；接收单元2902在所述一个或多于一个小区和/或上行载波中的一个小区和/或上行载波上接收所述CSI报告。
在一些实施例中，所述DCI format包括用于请求或触发CSI上报的字段，所述字段的值对应CSI触发状态。
在一些实施例中，所述字段的长度是由高层参数配置的，并且，所述高层参数是所述DCI format特定的，或者是所述DCI format与其他DCI format共用的。
在一些实施例中，所述字段的长度是所述终端设备根据配置的触发状态列表中的触发状态数量确定的。
在一些实施例中，所述一个小区和/或上行载波是缺省的或由信令配置的用于接收CSI报告的小区和/或上行载波。
在一些实施例中，所述缺省的用于接收CSI报告的小区为以下至少之一：
调度的小区中服务小区标识号最小的小区；
调度的PUSCH中时域上第一个满足半持续CSI上报时序要求的PUSCH所在的小区；
调度的PUSCH中时域上第一个满足半持续CSI上报时序要求的PUSCH所在的小区中服务小区标识号最小的小区。
在一些实施例中，所述缺省的用于接收CSI报告的小区为：Pcell或PScell或PUCCH Scell。
在一些实施例中，接收单元2902在缺省的PUSCH上接收所述CSI报告。
在一些实施例中，所述缺省的PUSCH为以下至少之一：
调度的小区中服务小区标识号最小的小区的PUSCH；
调度的PUSCH中时域上第一个满足非周期CSI上报时序要求的PUSCH；
调度的PUSCH中时域上第一个满足非周期CSI上报时序要求的PUSCH中所在小区中服务小区标识号最小的小区的PUSCH。
在一些实施例中，所述缺省的PUSCH所在的小区为：Pcell或PScell或PUCCH Scell。
在一些实施例中，所述DCI format包括用于指示小区和/或上行载波的字段。
在一些实施例中，所述缺省的或由信令配置的用于接收CSI报告的小区和/或上行载波在所述字段指示的一个或多个小区和/或上行载波的范围内，或者不在所述字段指示的一个或多个小区和/或上行载波的范围内。
在一些实施例中，所述DCI format调度了多于一个小区和/或上行载波上的PUSCH；
所述网络设备在所述多于一个小区和/或上行载波中的一个或多于一个小区和/或上行载波上接收所述CSI报告。
在一些实施例中，所述DCI format包括用于指示小区和/或上行载波的字段，所述字段指示了所述多于一个小区和/或上行载波。
在一些实施例中，不同PUSCH上的CSI报告的内容相同或不同。
在一些实施例中，所述DCI format包括一个用于触发或激活CSI上报的字段，不同PUSCH上的CSI报告相同，和/或，不同PUSCH分别用于承载所述字段关联的触发状态对应的不同的CSI报告，和/或，不同PUSCH分别用于承载所述CSI报告的不同部分。
在一些实施例中，所述DCI format包括多个用于触发或激活CSI上报的字段，不同PUSCH分别用于承载不同的用于请求或触发CSI上报的字段关联的触发状态对应的CSI报告。
在一些实施例中，所述DCI format的CRC由SP-CSI-RNTI加扰。
本申请实施例还提供一种半持续CSI上报的释放或去激活装置。该装置例如可以是终端设备，也可以是配置于终端设备的某个或某些部件或者组件，与第五至第六方面的实施例相同的内容不再赘述。
图30是本申请实施例的半持续CSI上报的释放或去激活装置的一示意图。如图30所示，本申请实施例的半持续CSI上报的释放或去激活装置3000包括：
接收单元3001，其接收用于调度一个或多于一个小区和/或上行载波上的PUSCH的DCI format，所述DCI format释放或去激活半持续CSI上报；
处理单元3002，其去激活半持续CSI上报。
在一些实施例中，所述DCI format包括用于指示小区和/或上行载波的字段，所述字段指示了一个小区或上行载波，和/或，所述字段指示的小区和/或上行载波是Pcell或PScell或PUCCH Scell，和/或所述字段为特定值，所述特定值不对应任何小区和/或上行载波。
在一些实施例中，如图30所示，装置3000还包括：
确定/确认单元3003，其确定/确认(validates)所述DCI format对于半持续CSI释放/去激活的有效性。
在一些实施例中，确定/确认单元3003根据所述DCI format中用于指示小区和/或上行载波的字段和/或用于指示HARQ进程ID的字段和/或用于指示RV的字段和/或多个用于指示MCS的字段和/或多个用于指示频域资源(RB)分配确定/确认(validates)所述有效性。
在一些实施例中，所述DCI format中包括多个用于指示HARQ进程ID的字段，确定/确认单元3003根据所述DCI format中的部分或全部用于指示小区和/或上行载波的字段确定/确认(validates)所述有效性。
在一些实施例中，所述DCI format中包括多个用于指示RV的字段，确定/确认单元3003根据所述DCI format中的部分或全部用于指示RV的字段确定/确认(validates)所述有效性。
在一些实施例中，所述DCI format中包括一个或多个用于指示小区和/或上行载波的字段，确定/确认单元3003根据所述DCI format中的部分或全部用于小区和/或上行载波的字段确定/确认(validates)所述有效性。
在一些实施例中，所述DCI format中包括多个用于指示调制编码方案(MCS，Modulation and coding scheme)的字段，确定/确认单元3003根据所述DCI format中的部分或全部用于指示小区和/或上行载波的字段确定/确认(validates)所述有效性。
在一些实施例中，所述DCI format中包括用于指示频域资源(例如资源块RB)分配(Frequency domain resource assignment)的字段，确定/确认单元3003根据所述DCI format中的部分或全部用于指示小区和/或上行载波的字段确定/确认(validates)所述有效性。
在一些实施例中，如果所述DCI format是无效的，确定/确认单元3003忽略/丢弃所述DCI format。
本申请实施例还提供一种半持续CSI上报的释放或去激活装置。该装置例如可以是网络设备，也可以是配置于网络设备的某个或某些部件或者组件，与第五至第六方面的实施例相同的内容不再赘述。
图31是本申请实施例的半持续CSI上报的释放或去激活装置的一示意图。如图31所示，本申请实施例的半持续CSI上报的释放或去激活装置3100包括：
发送单元3101，其发送用于调度一个或多于一个小区和/或上行载波上的PUSCH的DCI format，所述DCI format释放或去激活半持续CSI上报。
在一些实施例中，所述DCI format包括用于指示小区和/或上行载波的字段，所述字段指示了一个小区或上行载波，和/或，所述字段指示的小区和/或上行载波是Pcell或PScell或PUCCH Scell，和/或所述字段为特定值，所述特定值不对应任何小区和/或上行载波。
以上各个实施例仅对本申请实施例进行了示例性说明，但本申请不限于此，还可以在以上各个实施例的基础上进行适当的变型。例如，可以单独使用上述各个实施例，也可以将以上各个实施例中的一种或多种结合起来。
值得注意的是，以上仅对与本申请相关的各部件或模块进行了说明，但本申请不限于此。装置2600、2700、2800、2900、3000、3100还可以包括其他部件或者模块，关于这些部件或者模块的具体内容，可以参考相关技术。
此外，为了简单起见，图26至图31中仅示例性示出了各个部件或模块之间的连接关系或信号走向，但是本领域技术人员应该清楚的是，可以采用总线连接等各种相关技术。上述各个部件或模块可以通过例如处理器、存储器、发射机、接收机等硬件设施来实现；本申请实施并不对此进行限制。
由上述实施例可知，实现了在DCI format能够调度多个小区的PUSCH的情况下的非周期CSI上报以及基于PUSCH的半持续CSI上报。
第八方面的实施例
本申请实施例还提供一种通信系统，可以参考图1，与第一方面至第六方面的实施例相同的内容不再赘述。
在一些实施例中，通信系统100至少可以包括网络设备和终端设备，其中，网络设 备被配置为执行第二方面、第四方面或者第六方面的实施例所述的方法；终端设备被配置为执行第一方面、第三方面或者第五方面的实施例所述的方法。
关于网络设备和终端设备的内容已经在第一至第六方面的实施例中做了详细说明，其内容被合并于此，此处不再赘述。
本申请实施例还提供一种终端设备，但本申请不限于此，还可以是其他的设备。
图32是本申请实施例的终端设备的示意图。如图32所示，该终端设备3200可以包括处理器3210和存储器3220；存储器3220存储有数据和程序，并耦合到处理器3210。值得注意的是，该图是示例性的；还可以使用其他类型的结构，来补充或代替该结构，以实现电信功能或其他功能。
例如，处理器3210可以被配置为执行程序而实现如第一方面或第三方面或第五方面的实施例所述的方法。
如图32所示，该终端设备3200还可以包括：通信模块3230、输入单元3240、显示器3250、电源3260。其中，上述部件的功能与现有技术类似，此处不再赘述。值得注意的是，终端设备3200也并不是必须要包括图32中所示的所有部件，上述部件并不是必需的；此外，终端设备3200还可以包括图32中没有示出的部件，可以参考现有技术。
本申请实施例还提供一种网络设备，例如可以是基站，但本申请不限于此，还可以是其他的网络设备。
图33是本申请实施例的网络设备的构成示意图。如图33所示，网络设备3300可以包括：处理器3310(例如中央处理器CPU)和存储器3320；存储器3320耦合到处理器3310。其中该存储器3320可存储各种数据；此外还存储信息处理的程序3330，并且在处理器3310的控制下执行该程序3330。
例如，处理器3310可以被配置为执行程序而实现如第二方面或第四方面或第六方面的实施例所述的方法。
此外，如图33所示，网络设备3300还可以包括：收发机3340和天线3350等；其中，上述部件的功能与现有技术类似，此处不再赘述。值得注意的是，网络设备3300也并不是必须要包括图33中所示的所有部件；此外，网络设备3300还可以包括图33中没有示出的部件，可以参考现有技术。
本申请实施例还提供一种计算机程序，其中当在终端设备中执行所述程序时，所述程序使得所述终端设备执行第一方面或第三方面或第五方面的实施例所述的方法。
本申请实施例还提供一种存储有计算机程序的存储介质，其中所述计算机程序使得 终端设备执行第一方面或第三方面或第五方面的实施例所述的方法。
本申请实施例还提供一种计算机程序，其中当在网络设备中执行所述程序时，所述程序使得所述网络设备执行第二方面或第四方面或第六方面的实施例所述的方法。
本申请实施例还提供一种存储有计算机程序的存储介质，其中所述计算机程序使得网络设备执行第二方面或第四方面或第六方面的实施例所述的方法。
本申请以上的装置和方法可以由硬件实现，也可以由硬件结合软件实现。本申请涉及这样的计算机可读程序，当该程序被逻辑部件所执行时，能够使该逻辑部件实现上文所述的装置或构成部件，或使该逻辑部件实现上文所述的各种方法或步骤。本申请还涉及用于存储以上程序的存储介质，如硬盘、磁盘、光盘、DVD、flash存储器等。
结合本申请实施例描述的方法/装置可直接体现为硬件、由处理器执行的软件模块或二者组合。例如，图中所示的功能框图中的一个或多个和/或功能框图的一个或多个组合，既可以对应于计算机程序流程的各个软件模块，亦可以对应于各个硬件模块。这些软件模块，可以分别对应于图中所示的各个步骤。这些硬件模块例如可利用现场可编程门阵列(FPGA)将这些软件模块固化而实现。
软件模块可以位于RAM存储器、闪存、ROM存储器、EPROM存储器、EEPROM存储器、寄存器、硬盘、移动磁盘、CD-ROM或者本领域已知的任何其它形式的存储介质。可以将一种存储介质耦接至处理器，从而使处理器能够从该存储介质读取信息，且可向该存储介质写入信息；或者该存储介质可以是处理器的组成部分。处理器和存储介质可以位于ASIC中。该软件模块可以存储在移动终端的存储器中，也可以存储在可插入移动终端的存储卡中。例如，若设备(如移动终端)采用的是较大容量的MEGA-SIM卡或者大容量的闪存装置，则该软件模块可存储在该MEGA-SIM卡或者大容量的闪存装置中。
针对附图中描述的功能方框中的一个或多个和/或功能方框的一个或多个组合，可以实现为用于执行本申请所描述功能的通用处理器、数字信号处理器(DSP)、专用集成电路(ASIC)、现场可编程门阵列(FPGA)或者其它可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件或者其任意适当组合。针对附图描述的功能方框中的一个或多个和/或功能方框的一个或多个组合，还可以实现为计算设备的组合，例如，DSP和微处理器的组合、多个微处理器、与DSP通信结合的一个或多个微处理器或者任何其它这种配置。
以上结合具体的实施方式对本申请进行了描述，但本领域技术人员应该清楚，这些 描述都是示例性的，并不是对本申请保护范围的限制。本领域技术人员可以根据本申请的精神和原理对本申请做出各种变型和修改，这些变型和修改也在本申请的范围内。
关于包括以上实施例的实施方式，还公开下述的附记：
1.一种非周期CSI上报方法，其中，所述方法包括：
终端设备接收用于调度一个或多于一个小区和/或上行载波上的PUSCH的DCI format，所述DCI format请求或触发非周期CSI上报；
所述终端设备发送CSI报告。
2.根据附记1所述的方法，其中，
所述DCI format调度了一个小区和/或上行载波上的PUSCH，所述终端设备在所述一个小区和/或上行载波上发送所述CSI报告。
3.根据附记1或2所述的方法，其中，
在所述DCI format请求或触发非周期CSI上报的情况下，所述DCI format仅调度一个小区和/或上行载波上的PUSCH。
4.根据附记2所述的方法，其中，
所述DCI format包括用于指示小区和/或上行载波的字段，所述字段指示了一个小区和/或上行载波；
所述终端设备在所述字段指示的所述小区和/或上行载波上发送所述CSI报告。
5.根据附记2所述的方法，其中，
所述终端设备在缺省的或由信令配置的用于发送CSI报告的小区和/或上行载波上发送所述CSI报告。
6.根据附记5所述的方法，其中，
所述DCI format包括用于指示小区和/或上行载波的字段，所述字段不指示小区和/或上行载波。
7.根据附记5所述的方法，其中，
所述DCI format包括用于指示小区和/或上行载波的字段，所述终端设备忽略所述字段。
8.根据附记1所述的方法，其中，
所述DCI format包括用于请求或触发CSI上报的字段，所述用于请求或触发CSI上报的字段位于用于指示小区和/或上行载波的字段之前。
9.根据附记5或8所述的方法，其中，
所述DCI format请求或触发非周期CSI上报时不包括用于指示小区和/或上行载波的字段。
10.根据附记5-9任一项所述的方法，其中，
所述缺省的用于发送CSI报告的小区为：Pcell或PScell或PUCCH Scell。
11.根据附记1所述的方法，其中，
所述DCI format调度了一个或多于一个小区和/或上行载波上的PUSCH；
所述终端设备在所述一个或多于一个小区和/或上行载波中的一个小区和/或上行载波上发送所述CSI报告。
12.根据附记1或2或11所述的方法，其中，
所述DCI format包括用于请求或触发CSI上报的字段，所述字段的值对应CSI非周期触发状态。
13.根据附记12所述的方法，其中，
所述字段的长度是由高层参数配置的，并且，所述高层参数是所述DCI format特定的，或者是所述DCI format与其他DCI format共用的。
14.根据附记12所述的方法，其中，
所述字段的长度是所述终端设备根据配置的触发状态列表中的触发状态数量确定的。
15.根据附记11所述的方法，其中，
所述一个小区和/或上行载波是缺省的或由信令配置的用于发送CSI报告的小区和/或上行载波。
16.根据附记15所述的方法，其中，
所述缺省的用于发送CSI报告的小区为以下至少之一：
调度的小区中服务小区标识号最小的小区；
调度的PUSCH中时域上第一个满足非周期CSI上报时序要求的PUSCH所在的小区；
调度的PUSCH中时域上第一个满足非周期CSI上报时序要求的PUSCH所在的小区中服务小区标识号最小的小区。
17.根据附记15或16所述的方法，其中，
所述缺省的用于发送CSI报告的小区为：Pcell或PScell或PUCCH Scell。
18.根据附记1所述的方法，其中，
所述终端设备在缺省的PUSCH上发送所述CSI报告。
19.根据附记18所述的方法，其中，
所述缺省的PUSCH为以下至少之一：
调度的小区中服务小区标识号最小的小区的PUSCH；
调度的PUSCH中时域上第一个满足非周期CSI上报时序要求的PUSCH；
调度的PUSCH中时域上第一个满足非周期CSI上报时序要求的PUSCH中所在小区中服务小区标识号最小的小区的PUSCH。
20.根据附记18或19所述的方法，其中，
所述缺省的PUSCH所在的小区为：Pcell或PScell或PUCCH Scell。
21.根据附记15所述的方法，其中，
所述DCI format包括用于指示小区和/或上行载波的字段。
22.根据附记21所述的方法，其中，
所述缺省的或由信令配置的用于发送CSI报告的小区和/或上行载波在所述字段指示的一个或多个小区和/或上行载波的范围内，或者不在所述字段指示的一个或多个小区和/或上行载波的范围内。
23.根据附记1所述的方法，其中，
所述DCI format调度了多于一个小区和/或上行载波上的PUSCH；
所述终端设备在所述多于一个小区和/或上行载波中的一个或多于一个小区和/或上行载波上发送所述CSI报告。
24.根据附记23所述的方法，其中，
所述DCI format包括用于指示小区和/或上行载波的字段，所述字段指示了所述多于一个小区和/或上行载波。
25.根据附记23所述的方法，其中，
不同PUSCH上的CSI报告的内容相同或不同。
26.根据附记23或25所述的方法，其中，
所述DCI format包括一个用于请求或触发CSI上报的字段，不同PUSCH上的CSI报告相同，和/或，不同PUSCH分别用于承载所述字段关联的触发状态对应的不同的CSI报告，和/或，不同PUSCH分别用于承载所述CSI报告的不同部分。
27.根据附记23或25所述的方法，其中，
所述DCI format包括多个用于请求或触发CSI上报的字段，不同PUSCH分别用于承载不同的用于请求或触发CSI上报的字段关联的触发状态对应的CSI报告。
28.根据附记1至27任一项所述的方法，其中，
所述DCI format的CRC由C-RNTI加扰或者由MCS-C-RNTI加扰。
29.根据附记1至28任一项所述的方法，其中，
所述终端设备接收用于配置所述终端设备在UE特定的搜索空间监听所述DCI format的配置信息。
30.根据附记1至29任一项所述的方法，其中，
所述终端设备接收用于配置所述DCI format是否支持触发CSI上报或者所述DCI format是否用于触发CSI上报的配置信息。
31.根据附记1至30任一项所述的方法，其中，
所述终端设备接收用于配置所述DCI format所能调度的小区和/或上行载波的配置信息。
32.根据附记1所述的方法，其中，
所述多于一个上行载波分别是不同小区的，或者，所述多于一个上行载波的中的至少两个是不同小区的。
33.一种CSI报告的接收方法，其中，所述方法包括：
网络设备发送用于调度一个或多于一个小区和/或上行载波上的PUSCH的DCI format，所述DCI format请求或触发非周期CSI上报；
所述网络设备接收CSI报告。
34.根据附记33所述的方法，其中，
所述DCI format调度了一个小区和/或上行载波上的PUSCH，所述网络设备在所述一个小区和/或上行载波上接收所述CSI报告。
35.根据附记33或34所述的方法，其中，
在所述DCI format请求或触发非周期CSI上报的情况下，所述DCI format仅调度一个小区和/或上行载波上的PUSCH。
36.根据附记34所述的方法，其中，
所述DCI format包括用于指示小区和/或上行载波的字段，所述字段指示了一个小区和/或上行载波；
所述网络设备在所述字段指示的所述小区和/或上行载波上接收所述CSI报告。
37.根据附记34所述的方法，其中，
所述网络设备在缺省的或由信令配置的用于接收CSI报告的小区和/或上行载波上 接收所述CSI报告。
38.根据附记37所述的方法，其中，
所述DCI format包括用于指示小区和/或上行载波的字段，所述字段不指示小区和/或上行载波。
39.根据附记37所述的方法，其中，
所述DCI format包括用于指示小区和/或上行载波的字段，所述终端设备忽略所述字段。
40.根据附记1所述的方法，其中，
所述DCI format包括用于请求或触发CSI上报的字段，所述用于请求或触发CSI上报的字段位于用于指示小区和/或上行载波的字段之前。
41.根据附记37或40所述的方法，其中，
所述DCI format请求或触发非周期CSI上报时不包括用于指示小区和/或上行载波的字段。
42.根据附记37-41任一项所述的方法，其中，
所述缺省的用于接收CSI报告的小区为：Pcell或PScell或PUCCH Scell。
43.根据附记33所述的方法，其中，
所述DCI format调度了一个或多于一个小区和/或上行载波上的PUSCH；
所述网络设备在所述一个或多于一个小区和/或上行载波中的一个小区和/或上行载波上接收所述CSI报告。
44.根据附记33或34或43所述的方法，其中，
所述DCI format包括用于请求或触发CSI上报的字段，所述字段的值对应CSI非周期触发状态。
45.根据附记44所述的方法，其中，
所述字段的长度是由高层参数配置的，并且，所述高层参数是所述DCI format特定的，或者是所述DCI format与其他DCI format共用的。
46.根据附记44所述的方法，其中，
所述字段的长度是所述终端设备根据配置的触发状态列表中的触发状态数量确定的。
47.根据附记43所述的方法，其中，
所述一个小区和/或上行载波是缺省的或由信令配置的用于接收CSI报告的小区和/或上行载波。
48.根据附记47所述的方法，其中，
所述缺省的用于接收CSI报告的小区为以下至少之一：
调度的小区中服务小区标识号最小的小区；
调度的PUSCH中时域上第一个满足非周期CSI上报时序要求的PUSCH所在的小区；
调度的PUSCH中时域上第一个满足非周期CSI上报时序要求的PUSCH所在的小区中服务小区标识号最小的小区。
49.根据附记47或48所述的方法，其中，
所述缺省的用于接收CSI报告的小区为：Pcell或PScell或PUCCH Scell。
50.根据附记1所述的方法，其中，
所述网络设备在缺省的PUSCH上接收所述CSI报告。
51.根据附记50所述的方法，其中，
所述缺省的PUSCH为以下至少之一：
调度的小区中服务小区标识号最小的小区的PUSCH；
调度的PUSCH中时域上第一个满足非周期CSI上报时序要求的PUSCH；
调度的PUSCH中时域上第一个满足非周期CSI上报时序要求的PUSCH中所在小区中服务小区标识号最小的小区的PUSCH。
52.根据附记50或51所述的方法，其中，
所述缺省的PUSCH所在的小区为：Pcell或PScell或PUCCH Scell。
53.根据附记47所述的方法，其中，
所述DCI format包括用于指示小区和/或上行载波的字段。
54.根据附记53所述的方法，其中，
所述缺省的或由信令配置的用于接收CSI报告的小区和/或上行载波在所述字段指示的一个或多个小区和/或上行载波的范围内，或者不在所述字段指示的一个或多个小区和/或上行载波的范围内。
55.根据附记1所述的方法，其中，
所述DCI format调度了多于一个小区和/或上行载波上的PUSCH；
所述网络设备在所述多于一个小区和/或上行载波中的一个或多于一个小区和/或上行载波上接收所述CSI报告。
56.根据附记55所述的方法，其中，
所述DCI format包括用于指示小区和/或上行载波的字段，所述字段指示了所述多于一个小区和/或上行载波。
57.根据附记55所述的方法，其中，
不同PUSCH上的CSI报告的内容相同或不同。
58.根据附记55或57所述的方法，其中，
所述DCI format包括一个用于请求或触发CSI上报的字段，不同PUSCH上的CSI报告相同，和/或，不同PUSCH分别用于承载所述字段关联的触发状态对应的不同的CSI报告，和/或，不同PUSCH分别用于承载所述CSI报告的不同部分。
59.根据附记56或57所述的方法，其中，
所述DCI format包括多个用于请求或触发CSI上报的字段，不同PUSCH分别用于承载不同的用于请求或触发CSI上报的字段关联的触发状态对应的CSI报告。
60.根据附记33至59任一项所述的方法，其中，
所述DCI format的CRC由C-RNTI加扰或者由MCS-C-RNTI加扰。
61.根据附记33至60任一项所述的方法，其中，
所述网络设备发送用于配置所述终端设备在UE特定的搜索空间监听所述DCI format的配置信息。
62.根据附记33至61任一项所述的方法，其中，
所述网络设备发送用于配置所述DCI format是否支持触发CSI上报或者所述DCI format是否用于触发CSI上报的配置信息。
63.根据附记33至62任一项所述的方法，其中，
所述网络设备发送用于配置所述DCI format所能调度的小区和/或上行载波的配置信息。
64.根据附记1所述的方法，其中，
所述多于一个上行载波分别是不同小区的，或者，所述多于一个上行载波的中的至少两个是不同小区的。
1’.一种半持续CSI上报方法，其中，所述方法包括：
终端设备接收用于调度一个或多于一个小区和/或上行载波上的PUSCH的DCI format，所述DCI format触发或激活半持续CSI上报；
所述终端设备发送CSI报告。
2’.根据附记1’所述的方法，其中，
所述DCI format调度了一个小区和/或上行载波上的PUSCH，所述终端设备在所述一个小区和/或上行载波上发送所述CSI报告。
3’.根据附记1’或2’所述的方法，其中，
在所述DCI format触发或激活半持续CSI上报的情况下，所述DCI format仅调度一个小区和/或上行载波上的PUSCH。
4’.根据附记2’所述的方法，其中，
所述DCI format包括用于指示小区和/或上行载波的字段，所述字段指示了一个小区和/或上行载波；
所述终端设备在所述字段指示的所述小区和/或上行载波上发送所述CSI报告。
5’.根据附记2’所述的方法，其中，
所述终端设备在缺省的或由信令配置的用于发送CSI报告的小区和/或上行载波上发送所述CSI报告。
6’.根据附记5’所述的方法，其中，
所述DCI format包括用于指示小区和/或上行载波的字段，所述字段不指示小区和/或上行载波。
7’.根据附记5’所述的方法，其中，
所述DCI format包括用于指示小区和/或上行载波的字段，所述终端设备忽略所述字段。
8’.根据附记1’所述的方法，其中，
所述DCI format包括用于请求或触发CSI上报的字段，所述用于请求或触发CSI上报的字段位于用于指示小区和/或上行载波的字段之前。
9’.根据附记5’或8’所述的方法，其中，
所述DCI format触发或激活半持续CSI上报时不包括用于指示小区和/或上行载波的字段。
10’.根据附记5’-8’任一项所述的方法，其中，
所述缺省的用于发送CSI报告的小区为：Pcell或PScell或PUCCH Scell。
11’.根据附记1’所述的方法，其中，
所述DCI format调度了一个或多于一个小区和/或上行载波上的PUSCH；
所述终端设备在所述一个或多于一个小区和/或上行载波中的一个小区和/或上行载波上发送所述CSI报告。
12’.根据附记1’或2’或11’所述的方法，其中，
所述DCI format包括用于请求或触发CSI上报的字段，所述字段的值对应CSI触发状态。
13’.根据附记12’所述的方法，其中，
所述字段的长度是由高层参数配置的，并且，所述高层参数是所述DCI format特定的，或者是所述DCI format与其他DCI format共用的。
14’.根据附记12’所述的方法，其中，
所述字段的长度是所述终端设备根据配置的触发状态列表中的触发状态数量确定的。
15’.根据附记11’所述的方法，其中，
所述一个小区和/或上行载波是缺省的或由信令配置的用于发送CSI报告的小区和/或上行载波。
16’.根据附记15’所述的方法，其中，
所述缺省的用于发送CSI报告的小区为以下至少之一：
调度的小区中服务小区标识号最小的小区；
调度的PUSCH中时域上第一个满足半持续CSI上报时序要求的PUSCH所在的小区；
调度的PUSCH中时域上第一个满足半持续CSI上报时序要求的PUSCH所在的小区中服务小区标识号最小的小区。
17’.根据附记15’或16’所述的方法，其中，
所述缺省的用于发送CSI报告的小区为：Pcell或PScell或PUCCH Scell。
18’.根据附记1’所述的方法，其中，
所述终端设备在缺省的PUSCH上发送所述CSI报告。
19’.根据附记18’所述的方法，其中，
所述缺省的PUSCH为以下至少之一：
调度的小区中服务小区标识号最小的小区的PUSCH；
调度的PUSCH中时域上第一个满足非周期CSI上报时序要求的PUSCH；
调度的PUSCH中时域上第一个满足非周期CSI上报时序要求的PUSCH中所在小区中服务小区标识号最小的小区的PUSCH。
20’.根据附记18’或19’所述的方法，其中，
所述缺省的PUSCH所在的小区为：Pcell或PScell或PUCCH Scell。
21’.根据附记15’所述的方法，其中，
所述DCI format包括用于指示小区和/或上行载波的字段。
22’.根据附记21’所述的方法，其中，
所述缺省的或由信令配置的用于发送CSI报告的小区和/或上行载波在所述字段指示的一个或多个小区和/或上行载波的范围内，或者不在所述字段指示的一个或多个小区和/或上行载波的范围内。
23’.根据附记1’所述的方法，其中，
所述DCI format调度了多于一个小区和/或上行载波上的PUSCH；
所述终端设备在所述多于一个小区和/或上行载波中的一个或多于一个小区和/或上行载波上发送所述CSI报告。
24’.根据附记23’所述的方法，其中，
所述DCI format包括用于指示小区和/或上行载波的字段，所述字段指示了所述多于一个小区和/或上行载波。
25’.根据权利要求23’所述的方法，其中，
不同PUSCH上的CSI报告的内容相同或不同。
26’.根据附记23’或25’所述的方法，其中，
所述DCI format包括一个用于触发或激活CSI上报的字段，不同PUSCH上的CSI报告相同，和/或，不同PUSCH分别用于承载所述字段关联的触发状态对应的不同的CSI报告，和/或，不同PUSCH分别用于承载所述CSI报告的不同部分。
27’.根据附记23’或25’所述的方法，其中，
所述DCI format包括多个用于触发或激活CSI上报的字段，不同PUSCH分别用于承载不同的用于请求或触发CSI上报的字段关联的触发状态对应的CSI报告。
28’.根据附记1’-27’任一项所述的方法，其中，
所述DCI format的CRC由SP-CSI-RNTI加扰。
29’.根据附记1’至28’任一项所述的方法，其中，
所述终端设备确定/确认(validates)所述DCI format对于半持续CSI激活的有效性。
30’.根据附记29’所述的方法，其中，
所述终端设备根据所述DCI format中用于指示小区和/或上行载波的字段和/或用于指示HARQ进程ID的字段和/或用于指示RV的字段确定/确认(validates)所述有效性。
31’.根据附记30’所述的方法，其中，
所述DCI format中包括多个用于指示HARQ进程ID的字段，所述终端设备根据所述DCI format中的部分或全部用于指示小区和/或上行载波的字段确定/确认(validates)所述有效性。
32’.根据附记30’或31’所述的方法，其中，
所述DCI format中包括多个用于指示RV的字段，所述终端设备根据所述DCI format中的部分或全部用于指示RV的字段确定/确认(validates)所述有效性。
33’.根据附记30’-32’任一项所述的方法，其中，
所述DCI format中包括一个或多个用于指示小区和/或上行载波的字段，所述终端设备根据所述DCI format中的部分或全部用于小区和/或上行载波的字段确定/确认(validates)所述有效性。
34’.根据附记30’-33’任一项所述的方法，其中，
如果所述DCI format是无效的，所述终端设备忽略/丢弃所述DCI format。
35’.一种CSI报告的接收方法，其中，所述方法包括：
网络设备发送用于调度一个或多于一个小区和/或上行载波上的PUSCH的DCI format，所述DCI format触发或激活半持续CSI上报；
所述网络设备接收CSI报告。
36’.根据附记35’所述的方法，其中，
所述DCI format调度了一个小区和/或上行载波上的PUSCH，所述网络设备在所述一个小区和/或上行载波上接收所述CSI报告。
37’.根据附记35’或36’所述的方法，其中，
在所述DCI format触发或激活半持续CSI上报的情况下，所述DCI format仅调度一个小区和/或上行载波上的PUSCH。
38’.根据附记36’所述的方法，其中，
所述DCI format包括用于指示小区和/或上行载波的字段，所述字段指示了一个小区和/或上行载波；
所述网络设备在所述字段指示的所述小区和/或上行载波上接收所述CSI报告。
39’.根据附记36’所述的方法，其中，
所述网络设备在缺省的或由信令配置的用于接收CSI报告的小区和/或上行载波上接收所述CSI报告。
40’.根据附记39’所述的方法，其中，
所述DCI format包括用于指示小区和/或上行载波的字段，所述字段不指示小区和/或上行载波。
41’.根据附记39’所述的方法，其中，
所述DCI format包括用于指示小区和/或上行载波的字段，所述终端设备忽略所述字段。
42’.根据附记35’所述的方法，其中，
所述DCI format包括用于请求或触发CSI上报的字段，所述用于请求或触发CSI上报的字段位于用于指示小区和/或上行载波的字段之前。
43’.根据附记39’或42’所述的方法，其中，
所述DCI format触发或激活半持续CSI上报时不包括用于指示小区和/或上行载波的字段。
44’.根据附记39’-42’任一项所述的方法，其中，
所述缺省的用于接收CSI报告的小区为：Pcell或PScell或PUCCH Scell。
45’.根据附记35’所述的方法，其中，
所述DCI format调度了一个或多于一个小区和/或上行载波上的PUSCH；
所述网络设备在所述一个或多于一个小区和/或上行载波中的一个小区和/或上行载波上接收所述CSI报告。
46’.根据附记35’或36’或45’所述的方法，其中，
所述DCI format包括用于请求或触发CSI上报的字段，所述字段的值对应CSI触发状态。
47’.根据附记46’所述的方法，其中，
所述字段的长度是由高层参数配置的，并且，所述高层参数是所述DCI format特定的，或者是所述DCI format与其他DCI format共用的。
48’.根据附记46’所述的方法，其中，
所述字段的长度是所述终端设备根据配置的触发状态列表中的触发状态数量确定的。
49’.根据附记45’所述的方法，其中，
所述一个小区和/或上行载波是缺省的或由信令配置的用于接收CSI报告的小区和/或上行载波。
50’.根据附记49’所述的方法，其中，
所述缺省的用于接收CSI报告的小区为以下至少之一：
调度的小区中服务小区标识号最小的小区；
调度的PUSCH中时域上第一个满足半持续CSI上报时序要求的PUSCH所在的小区；
调度的PUSCH中时域上第一个满足半持续CSI上报时序要求的PUSCH所在的小区中服务小区标识号最小的小区。
51’.根据附记49’或50’所述的方法，其中，
所述缺省的用于接收CSI报告的小区为：Pcell或PScell或PUCCH Scell。
52’.根据附记35’所述的方法，其中，
所述网络设备在缺省的PUSCH上接收所述CSI报告。
53’.根据附记52’所述的方法，其中，
所述缺省的PUSCH为以下至少之一：
调度的小区中服务小区标识号最小的小区的PUSCH；
调度的PUSCH中时域上第一个满足非周期CSI上报时序要求的PUSCH；
调度的PUSCH中时域上第一个满足非周期CSI上报时序要求的PUSCH中所在小区中服务小区标识号最小的小区的PUSCH。
54’.根据附记52’或53’所述的方法，其中，
所述缺省的PUSCH所在的小区为：Pcell或PScell或PUCCH Scell。
55’.根据附记49’所述的方法，其中，
所述DCI format包括用于指示小区和/或上行载波的字段。
56’.根据附记55’所述的方法，其中，
所述缺省的或由信令配置的用于接收CSI报告的小区和/或上行载波在所述字段指示的一个或多个小区和/或上行载波的范围内，或者不在所述字段指示的一个或多个小区和/或上行载波的范围内。
57’.根据附记35’所述的方法，其中，
所述DCI format调度了多于一个小区和/或上行载波上的PUSCH；
所述网络设备在所述多于一个小区和/或上行载波中的一个或多于一个小区和/或上行载波上接收所述CSI报告。
58’.根据附记57’所述的方法，其中，
所述DCI format包括用于指示小区和/或上行载波的字段，所述字段指示了所述多于一个小区和/或上行载波。
59’.根据权利要求57’所述的方法，其中，
不同PUSCH上的CSI报告的内容相同或不同。
60’.根据附记57’或59’所述的方法，其中，
所述DCI format包括一个用于触发或激活CSI上报的字段，不同PUSCH上的CSI报告相同，和/或，不同PUSCH分别用于承载所述字段关联的触发状态对应的不同的CSI报告，和/或，不同PUSCH分别用于承载所述CSI报告的不同部分。
61’.根据附记57’或59’所述的方法，其中，
所述DCI format包括多个用于触发或激活CSI上报的字段，不同PUSCH分别用于承载不同的用于请求或触发CSI上报的字段关联的触发状态对应的CSI报告。
62’.根据附记35’-61’任一项所述的方法，其中，
所述DCI format的CRC由SP-CSI-RNTI加扰。
1”.一种半持续CSI上报的释放或去激活方法，其中，所述方法包括：
终端设备接收用于调度一个或多于一个小区和/或上行载波上的PUSCH的DCI format，所述DCI format释放或去激活半持续CSI上报；
所述终端设备去激活半持续CSI上报。
2”.根据附记1”所述的方法，其中，
所述DCI format包括用于指示小区和/或上行载波的字段，所述字段指示了一个小区或上行载波，和/或，所述字段指示的小区和/或上行载波是Pcell或PScell或PUCCH Scell，和/或所述字段为特定值，所述特定值不对应任何小区和/或上行载波。
3”.根据附记1”或2”所述的方法，其中，
所述终端设备确定/确认(validates)所述DCI format对于半持续CSI释放/去激活的有效性。
4”.根据附记3”所述的方法，其中，
所述终端设备根据所述DCI format中用于指示小区和/或上行载波的字段和/于指示HARQ进程ID的字段和/或用于指示RV的字段和/或多个用于指示MCS的字段和/或多个用于指示频域资源(RB)分配确定/确认(validates)所述有效性。
5”.根据附记4”所述的方法，其中，
所述DCI format中包括多个用于指示HARQ进程ID的字段，所述终端设备根据所述DCI format中的部分或全部用于指示小区和/或上行载波的字段确定/确认(validates)所述有效性。
6”.根据附记4”或5”所述的方法，其中，
所述DCI format中包括多个用于指示RV的字段，所述终端设备根据所述DCI format中的部分或全部用于指示RV的字段确定/确认(validates)所述有效性。
7”.根据附记4”-6”任一项所述的方法，其中，
所述DCI format中包括一个或多个用于指示小区和/或上行载波的字段，所述终端设备根据所述DCI format中的部分或全部用于小区和/或上行载波的字段确定/确认(validates)所述有效性。
8”.根据附记4”-7”任一项所述的方法，其中，
所述DCI format中包括多个用于指示MCS的字段，所述终端设备根据所述DCI format中的部分或全部用于指示小区和/或上行载波的字段确定/确认(validates)所述有效性。
9”.根据附记4”-8”任一项所述的方法，其中，
所述DCI format中包括用于指示频域资源(RB)分配的字段，所述终端设备根据所述DCI format中的部分或全部用于指示小区和/或上行载波的字段确定/确认(validates)所述有效性。
10”.根据附记4”-9”任一项所述的方法，其中，
如果所述DCI format是无效的，所述终端设备忽略/丢弃所述DCI format。
11”.一种半持续CSI上报的释放或去激活方法，其中，所述方法包括：
网络设备发送用于调度一个或多于一个小区和/或上行载波上的PUSCH的DCI format，所述DCI format释放或去激活半持续CSI上报。
12”.根据附记11”所述的方法，其中，
所述DCI format包括用于指示小区和/或上行载波的字段，所述字段指示了一个小区或上行载波，和/或，所述字段指示的小区和/或上行载波是Pcell或PScell或PUCCH Scell，和/或所述字段为特定值，所述特定值不对应任何小区和/或上行载波。
1a.一种终端设备，包括存储器和处理器，所述存储器存储有计算机程序，所述处理器被配置为执行所述计算机程序而实现如附记1至32、1’至34’以及1”至10”任一项所述的方法。
2a.一种网络设备，包括存储器和处理器，所述存储器存储有计算机程序，所述处理器被配置为执行所述计算机程序而实现如附记33至64、35’至62’以及11”至12”任一项所述的方法。
3a.一种通信系统，包括网络设备和终端设备，其中：
所述网络设备被配置为：
发送用于调度一个或多于一个小区和/或上行载波上的PUSCH的DCI format，所述DCI format请求或触发非周期CSI上报；
接收CSI报告；
所述终端设备被配置为：
接收所述DCI format；
发送所述CSI报告。
4a.一种通信系统，包括网络设备和终端设备，其中：
所述网络设备被配置为：
发送用于调度一个或多于一个小区和/或上行载波上的PUSCH的DCI format，所述DCI format触发或激活半持续CSI上报；
接收CSI报告；
所述终端设备被配置为：
接收所述DCI format；
发送所述CSI报告。
5a.一种通信系统，包括网络设备和终端设备，其中：
所述网络设备被配置为：
发送用于调度一个或多于一个小区和/或上行载波上的PUSCH的DCI format，所述DCI format释放或去激活半持续CSI上报；
所述终端设备被配置为：
接收所述DCI format；
去激活半持续CSI上报。

Claims (20)

  1. 一种非周期信道状态信息上报装置，其中，所述装置包括：
    接收单元，其接收用于调度一个或多于一个小区和/或上行载波上的物理上行共享信道的DCI format，所述DCI format请求或触发非周期信道状态信息上报；
    发送单元，其发送信道状态信息报告。
  2. 根据权利要求1所述的装置，其中，
    所述DCI format调度了一个小区和/或上行载波上的物理上行共享信道，所述发送单元在所述一个小区和/或上行载波上发送所述信道状态信息报告。
  3. 根据权利要求1或2所述的装置，其中，
    在所述DCI format请求或触发非周期信道状态信息上报的情况下，所述DCI format仅调度一个小区和/或上行载波上的物理上行共享信道。
  4. 根据权利要求2所述的装置，其中，
    所述DCI format包括用于指示小区和/或上行载波的字段，所述字段指示了一个小区和/或上行载波；
    所述发送单元在所述字段指示的所述小区和/或上行载波上发送所述信道状态信息报告。
  5. 根据权利要求2所述的装置，其中，
    所述发送单元在缺省的或由信令配置的用于发送信道状态信息报告的小区和/或上行载波上发送所述信道状态信息报告。
  6. 根据权利要求5所述的装置，其中，
    所述缺省的用于发送信道状态信息报告的小区为：Pcell或PScell或PUCCH Scell。
  7. 根据权利要求1所述的装置，其中，
    所述DCI format调度了一个或多于一个小区和/或上行载波上的物理上行共享信道；
    所述发送单元在所述一个或多于一个小区和/或上行载波中的一个小区和/或上行载波上发送所述信道状态信息报告。
  8. 根据权利要求7所述的装置，其中，
    所述一个小区和/或上行载波是缺省的或由信令配置的用于发送信道状态信息报告的小区和/或上行载波。
  9. 根据权利要求8所述的装置，其中，
    所述缺省的用于发送信道状态信息报告的小区为以下至少之一：
    调度的小区中服务小区标识号最小的小区；
    调度的物理上行共享信道中时域上第一个满足非周期信道状态信息上报时序要求的物理上行共享信道所在的小区；
    调度的物理上行共享信道中时域上第一个满足非周期信道状态信息上报时序要求的物理上行共享信道所在的小区中服务小区标识号最小的小区。
  10. 根据权利要求8所述的装置，其中，
    所述缺省的用于发送信道状态信息报告的小区为：Pcell或PScell或PUCCH Scell。
  11. 根据权利要求1所述的装置，其中，
    所述DCI format调度了多于一个小区和/或上行载波上的物理上行共享信道；
    所述发送单元在所述多于一个小区和/或上行载波中的一个或多于一个小区和/或上行载波上发送所述信道状态信息报告。
  12. 一种半持续信道状态信息上报装置，其中，所述装置包括：
    接收单元，其接收用于调度一个或多于一个小区和/或上行载波上的物理上行共享信道的DCI format，所述DCI format触发或激活半持续信道状态信息上报；
    发送单元，其发送信道状态信息报告。
  13. 根据权利要求12所述的装置，其中，
    所述DCI format调度了一个小区和/或上行载波上的物理上行共享信道，所述发送单元在所述一个小区和/或上行载波上发送所述信道状态信息报告。
  14. 根据权利要求12所述的装置，其中，
    在所述DCI format触发或激活半持续信道状态信息上报的情况下，所述DCI format仅调度一个小区和/或上行载波上的物理上行共享信道。
  15. 根据权利要求13所述的装置，其中，
    所述DCI format包括用于指示小区和/或上行载波的字段，所述字段指示了一个小区和/或上行载波；
    所述发送单元在所述字段指示的所述小区和/或上行载波上发送所述信道状态信息报告。
  16. 根据权利要求13所述的装置，其中，
    所述发送单元在缺省的或由信令配置的用于发送信道状态信息报告的小区和/或上 行载波上发送所述信道状态信息报告。
  17. 根据权利要求12所述的装置，其中，
    所述DCI format的循环冗余校验由SP-CSI-RNTI加扰。
  18. 根据权利要求12所述的装置，其中，所述装置还包括：
    确定/确认单元，其确定/确认所述DCI format对于半持续信道状态信息激活的有效性。
  19. 根据权利要求18所述的装置，其中，
    所述确定/确认单元根据所述DCI format中用于指示小区和/或上行载波的字段和/或用于指示混合自动重传请求进程ID的字段和/或用于指示冗余版本的字段确定/确认所述有效性。
  20. 根据权利要求19所述的装置，其中，
    所述DCI format中包括多个用于指示冗余版本的字段，所述确定/确认单元根据所述DCI format中的部分或全部用于指示冗余版本的字段确定/确认所述有效性。
PCT/CN2022/112293 2022-08-12 2022-08-12 信道状态信息的上报方法和装置 Ceased WO2024031696A1 (zh)

Priority Applications (6)

Application Number Priority Date Filing Date Title
PCT/CN2022/112293 WO2024031696A1 (zh) 2022-08-12 2022-08-12 信道状态信息的上报方法和装置
KR1020257003933A KR20250036176A (ko) 2022-08-12 2022-08-12 채널 상태 정보를 보고하기 위한 방법 및 장치
JP2025507085A JP2025526627A (ja) 2022-08-12 2022-08-12 チャネル状態情報の報告方法と装置
EP22954648.6A EP4572258A4 (en) 2022-08-12 2022-08-12 METHOD FOR REPORTING CHANNEL STATE INFORMATION AND APPARATUS
CN202280098013.XA CN119547391A (zh) 2022-08-12 2022-08-12 信道状态信息的上报方法和装置
US19/029,707 US20250175840A1 (en) 2022-08-12 2025-01-17 Method and apparatus for reporting channel state information

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2022/112293 WO2024031696A1 (zh) 2022-08-12 2022-08-12 信道状态信息的上报方法和装置

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US19/029,707 Continuation US20250175840A1 (en) 2022-08-12 2025-01-17 Method and apparatus for reporting channel state information

Publications (1)

Publication Number Publication Date
WO2024031696A1 true WO2024031696A1 (zh) 2024-02-15

Family

ID=89850516

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/112293 Ceased WO2024031696A1 (zh) 2022-08-12 2022-08-12 信道状态信息的上报方法和装置

Country Status (6)

Country Link
US (1) US20250175840A1 (zh)
EP (1) EP4572258A4 (zh)
JP (1) JP2025526627A (zh)
KR (1) KR20250036176A (zh)
CN (1) CN119547391A (zh)
WO (1) WO2024031696A1 (zh)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20240114523A1 (en) * 2022-09-29 2024-04-04 Acer Incorporated Method for handling a multi-cell scheduling and user equipment

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111713069A (zh) * 2018-02-15 2020-09-25 夏普株式会社 用户设备、基站和方法
CN112470517A (zh) * 2018-07-20 2021-03-09 夏普株式会社 用于csi报告的用户设备、基站和方法
WO2021147088A1 (en) * 2020-01-23 2021-07-29 Qualcomm Incorporated Scheduling reference signals for multiple carriers
CN113796140A (zh) * 2019-05-03 2021-12-14 Lg电子株式会社 在无线通信系统中发送和接收信号的方法和装置
WO2022151620A1 (zh) * 2021-01-15 2022-07-21 华为技术有限公司 资源调度的方法和通信设备

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20170325216A1 (en) * 2016-05-09 2017-11-09 Sharp Laboratories Of America, Inc. User equipments, base stations and methods
WO2023137091A1 (en) * 2022-01-12 2023-07-20 Intel Corporation Cell grouping for multi-cell scheduling
WO2023137726A1 (en) * 2022-01-21 2023-07-27 Nec Corporation Method, device and computer readable medium for communication
US20230309093A1 (en) * 2022-03-25 2023-09-28 FG Innovation Company Limited Method, user equipment and base station for performing multiple receptions or transmission on multiple serving cells

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111713069A (zh) * 2018-02-15 2020-09-25 夏普株式会社 用户设备、基站和方法
CN112470517A (zh) * 2018-07-20 2021-03-09 夏普株式会社 用于csi报告的用户设备、基站和方法
CN113796140A (zh) * 2019-05-03 2021-12-14 Lg电子株式会社 在无线通信系统中发送和接收信号的方法和装置
WO2021147088A1 (en) * 2020-01-23 2021-07-29 Qualcomm Incorporated Scheduling reference signals for multiple carriers
WO2022151620A1 (zh) * 2021-01-15 2022-07-21 华为技术有限公司 资源调度的方法和通信设备

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
FUJITSU: "Consideration on multi-cell PUSCH/PDSCH scheduling with a single DCI", 3GPP DRAFT; R1-2205088, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG1, no. e-Meeting; 20220509 - 20220520, 29 April 2022 (2022-04-29), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP052191747 *
NOKIA, NOKIA SHANGHAI BELL: "On multi-cell PUSCH/PDSCH scheduling with a single DCI", 3GPP DRAFT; R1-2203276, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG1, no. e-Meeting; 20220509 - 20220520, 29 April 2022 (2022-04-29), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP052152907 *
See also references of EP4572258A4 *

Also Published As

Publication number Publication date
JP2025526627A (ja) 2025-08-15
EP4572258A4 (en) 2025-10-08
KR20250036176A (ko) 2025-03-13
US20250175840A1 (en) 2025-05-29
CN119547391A (zh) 2025-02-28
EP4572258A1 (en) 2025-06-18

Similar Documents

Publication Publication Date Title
US12089223B2 (en) Signal reception or transmission method and apparatus and system
US12004099B2 (en) Data transmission method and apparatus
CN114342535B (zh) 上行信号的发送和接收方法以及装置
US12289764B2 (en) Method and apparatus for transmitting and receiving uplink control information
WO2021026917A1 (zh) 信号发送方法、装置和系统
WO2021031042A1 (zh) 信号发送和接收方法以及装置
US11013018B2 (en) Data multiplexing apparatus and method and communication system
KR102690795B1 (ko) 업링크 신호를 송신하기 위한 방법 및 장치와, 업링크 신호를 수신하기 위한 방법 및 장치
US20240015665A1 (en) Method and apparatus for transmitting uplink data and a system
WO2022077410A1 (zh) 信息反馈方法以及装置
US20250175840A1 (en) Method and apparatus for reporting channel state information
WO2021087926A1 (zh) 上行信号的发送和接收方法以及装置
WO2020143064A1 (zh) 数据传输方法及装置
JP2023544762A (ja) データ受信方法及び装置
WO2025065434A1 (zh) 信息发送方法、信息接收方法以及装置
WO2021056570A1 (zh) 无线通信方法、装置和系统
CN118160387A (zh) 信号发送方法、信号接收方法和装置
WO2026065470A1 (zh) 报告发送和接收方法以及装置
WO2025166694A1 (zh) 信号收发方法、装置以及通信系统
WO2025035406A1 (zh) 信息发送方法、信息接收方法以及装置
WO2025208544A1 (zh) 资源配置方法、装置以及通信系统
WO2025208293A9 (zh) 波束管理方法和装置
WO2025156297A1 (zh) 信号发送方法、信号接收方法、装置以及通信系统
WO2026031212A1 (zh) Pusch发送和接收方法、装置以及通信系统
WO2025166697A1 (zh) 信号收发方法、装置以及通信系统

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 22954648

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 202280098013.X

Country of ref document: CN

ENP Entry into the national phase

Ref document number: 20257003933

Country of ref document: KR

Kind code of ref document: A

WWE Wipo information: entry into national phase

Ref document number: 1020257003933

Country of ref document: KR

Ref document number: 2025507085

Country of ref document: JP

WWP Wipo information: published in national office

Ref document number: 202280098013.X

Country of ref document: CN

WWE Wipo information: entry into national phase

Ref document number: 2022954648

Country of ref document: EP

NENP Non-entry into the national phase

Ref country code: DE

WWP Wipo information: published in national office

Ref document number: 1020257003933

Country of ref document: KR

ENP Entry into the national phase

Ref document number: 2022954648

Country of ref document: EP

Effective date: 20250312

WWP Wipo information: published in national office

Ref document number: 2022954648

Country of ref document: EP