WO2022011555A1 - 用于确定上行传输参数的方法和终端设备 - Google Patents

用于确定上行传输参数的方法和终端设备 Download PDF

Info

Publication number
WO2022011555A1
WO2022011555A1 PCT/CN2020/101907 CN2020101907W WO2022011555A1 WO 2022011555 A1 WO2022011555 A1 WO 2022011555A1 CN 2020101907 W CN2020101907 W CN 2020101907W WO 2022011555 A1 WO2022011555 A1 WO 2022011555A1
Authority
WO
WIPO (PCT)
Prior art keywords
pusch
transmission
transmission parameters
terminal device
transmission parameter
Prior art date
Application number
PCT/CN2020/101907
Other languages
English (en)
French (fr)
Inventor
陈文洪
Original Assignee
Oppo广东移动通信有限公司
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 Oppo广东移动通信有限公司 filed Critical Oppo广东移动通信有限公司
Priority to CN202080100687.XA priority Critical patent/CN115553006A/zh
Priority to EP20945665.6A priority patent/EP4185037B1/en
Priority to KR1020237004064A priority patent/KR20230037590A/ko
Priority to JP2023501676A priority patent/JP2023538487A/ja
Priority to PCT/CN2020/101907 priority patent/WO2022011555A1/zh
Priority to CN202310127377.2A priority patent/CN116208308B/zh
Publication of WO2022011555A1 publication Critical patent/WO2022011555A1/zh
Priority to US18/090,378 priority patent/US20230262696A1/en

Links

Images

Classifications

    • 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 signaling, i.e. of overhead other than pilot signals
    • 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
    • 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/0686—Hybrid systems, i.e. switching and simultaneous transmission
    • H04B7/0695—Hybrid systems, i.e. switching and simultaneous transmission using beam selection
    • H04B7/06952—Selecting one or more beams from a plurality of beams, e.g. beam training, management or sweeping
    • 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), DMT
    • H04L5/001—Time-frequency the frequencies being orthogonal, e.g. OFDM(A), 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/0001—Arrangements for dividing the transmission path
    • H04L5/0014—Three-dimensional division
    • H04L5/0023—Time-frequency-space
    • 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
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W16/00—Network planning, e.g. coverage or traffic planning tools; Network deployment, e.g. resource partitioning or cells structures
    • H04W16/24—Cell structures
    • H04W16/28—Cell structures using beam steering
    • 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/046—Wireless resource allocation based on the type of the allocated resource the resource being in the space domain, e.g. beams
    • 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
    • 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 the present application relate to the field of communications, and more particularly, to a method and a terminal device for determining uplink transmission parameters.
  • the terminal device can activate the PUSCH on the carrier where the PUSCH is located.
  • the transmission beam on the PUCCH resource with the lowest resource identifier in the uplink bandwidth part (Band Width Part, BWP) of the PUSCH is used as the transmission beam of the PUSCH.
  • PUCCH diversity transmission based on multiple transmission and reception points (Transmission/Reception Point, TRP) is introduced. and power control parameters) repeatedly transmit the same PUCCH.
  • TRP Transmission/Reception Point
  • the PUCCH resource with the lowest resource identifier in the uplink BWP activated on the carrier where the PUSCH is located may be configured with multiple spatially related information (ie, multiple transmit beams).
  • the transmission of a single TRP is performed (ie, only a single beam can be used for transmission).
  • how to determine the transmission parameters of the PUSCH scheduled by the DCI format 0_0 (such as the transmission beam) is an urgent problem to be solved.
  • the embodiments of the present application provide a method and a terminal device for determining uplink transmission parameters.
  • the terminal device Transmission parameters of the PUSCH scheduled by DCI format 0_0 may be determined.
  • a first aspect provides a method for determining uplink transmission parameters, the method comprising:
  • the terminal device determines the transmission parameter of the PUSCH according to the transmission parameter on the PUCCH resource in the uplink BWP activated on the carrier where the PUSCH is located, wherein the PUSCH is the PUSCH scheduled in the first DCI format, and the transmission parameter is the transmission beam and/or Or the transmission parameter is a reference signal used for path loss measurement.
  • the first DCI format is DCI format 0_0.
  • a terminal device for executing the method in the above-mentioned first aspect.
  • the terminal device includes functional modules for executing the method in the first aspect.
  • a terminal device including a processor and a memory.
  • the memory is used to store a computer program
  • the processor is used to call and run the computer program stored in the memory to execute the method in the first aspect.
  • an apparatus for implementing the method in the above-mentioned first aspect.
  • the apparatus includes: a processor for invoking and running a computer program from a memory, so that a device in which the apparatus is installed executes the method in the above-mentioned first aspect.
  • a computer-readable storage medium for storing a computer program, and the computer program causes a computer to execute the method in the above-mentioned first aspect.
  • a computer program product comprising computer program instructions, the computer program instructions causing a computer to perform the method of the first aspect above.
  • a computer program which, when run on a computer, causes the computer to perform the method of the above-mentioned first aspect.
  • the terminal device can determine the transmission parameters of the PUSCH scheduled by DCI format 0_0.
  • FIG. 1 is a schematic diagram of a communication system architecture to which an embodiment of the present application is applied.
  • FIG. 2 is a schematic diagram of a TCI state configuration of a PDSCH provided by the present application.
  • FIG. 3 is a schematic diagram of a PUCCH repeated transmission provided by the present application.
  • FIG. 4 is a schematic diagram of a multi-TRP-based PUCCH diversity transmission provided by the present application.
  • FIG. 5 is a schematic flowchart of a method for determining uplink transmission parameters according to an embodiment of the present application.
  • FIG. 6 is a schematic diagram of determining a PUSCH transmission parameter according to an embodiment of the present application.
  • FIG. 7 is a schematic block diagram of a terminal device provided according to an embodiment of the present application.
  • FIG. 8 is a schematic block diagram of a communication device provided according to an embodiment of the present application.
  • FIG. 9 is a schematic block diagram of an apparatus provided according to an embodiment of the present application.
  • FIG. 10 is a schematic block diagram of a communication system provided according to an embodiment of the present application.
  • GSM Global System of Mobile communication
  • CDMA Code Division Multiple Access
  • CDMA Wideband Code Division Multiple Access
  • WCDMA Wideband Code Division Multiple Access
  • GPRS General Packet Radio Service
  • LTE Long Term Evolution
  • LTE-A Advanced Long Term Evolution
  • NR New Radio
  • NTN Non-Terrestrial Networks
  • UMTS Universal Mobile Telecommunication System
  • WLAN Wireless Local Area Networks
  • Wireless Fidelity Wireless Fidelity
  • WiFi fifth-generation communication
  • D2D Device to Device
  • M2M Machine to Machine
  • MTC Machine Type Communication
  • V2V Vehicle to Vehicle
  • V2X Vehicle to everything
  • the communication system in this embodiment of the present application may be applied to a carrier aggregation (Carrier Aggregation, CA) scenario, a dual connectivity (Dual Connectivity, DC) scenario, or a standalone (Standalone, SA) distribution. web scene.
  • Carrier Aggregation, CA Carrier Aggregation, CA
  • DC Dual Connectivity
  • SA standalone
  • the communication system in the embodiment of the present application may be applied to an unlicensed spectrum, where the unlicensed spectrum may also be considered as a shared spectrum; or, the communication system in the embodiment of the present application may also be applied to a licensed spectrum, where, Licensed spectrum can also be considered unshared spectrum.
  • the embodiments of the present application describe various embodiments in conjunction with network equipment and terminal equipment, where the terminal equipment may also be referred to as user equipment (User Equipment, UE), access terminal, subscriber unit, subscriber station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent or user device, etc.
  • user equipment User Equipment, UE
  • access terminal subscriber unit, subscriber station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent or user device, etc.
  • the terminal device can be a station (STAION, ST) in the WLAN, can be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a personal digital processing (Personal Digital Assistant, PDA) devices, handheld devices with wireless communication capabilities, computing devices or other processing devices connected to wireless modems, in-vehicle devices, wearable devices, next-generation communication systems such as end devices in NR networks, or future Terminal equipment in the evolved public land mobile network (Public Land Mobile Network, PLMN) network, etc.
  • STAION, ST in the WLAN
  • SIP Session Initiation Protocol
  • WLL Wireless Local Loop
  • PDA Personal Digital Assistant
  • the terminal device can be deployed on land, including indoor or outdoor, handheld, wearable, or vehicle-mounted; it can also be deployed on water (such as ships, etc.); it can also be deployed in the air (such as airplanes, balloons, and satellites) superior).
  • the terminal device may be a mobile phone (Mobile Phone), a tablet computer (Pad), a computer with a wireless transceiver function, a virtual reality (Virtual Reality, VR) terminal device, and an augmented reality (Augmented Reality, AR) terminal Equipment, wireless terminal equipment in industrial control, wireless terminal equipment in self driving, wireless terminal equipment in remote medical, wireless terminal equipment in smart grid , wireless terminal equipment in transportation safety, wireless terminal equipment in smart city or wireless terminal equipment in smart home, etc.
  • a mobile phone Mobile Phone
  • a tablet computer Pad
  • a computer with a wireless transceiver function a virtual reality (Virtual Reality, VR) terminal device
  • augmented reality (Augmented Reality, AR) terminal Equipment wireless terminal equipment in industrial control, wireless terminal equipment in self driving, wireless terminal equipment in remote medical, wireless terminal equipment in smart grid , wireless terminal equipment in transportation safety, wireless terminal equipment in smart city or wireless terminal equipment in smart home, etc.
  • the terminal device may also be a wearable device.
  • Wearable devices can also be called wearable smart devices, which are the general term for the intelligent design of daily wear and the development of wearable devices using wearable technology, such as glasses, gloves, watches, clothing and shoes.
  • a wearable device is a portable device that is worn directly on the body or integrated into the user's clothing or accessories. Wearable device is not only a hardware device, but also realizes powerful functions through software support, data interaction, and cloud interaction.
  • wearable smart devices include full-featured, large-scale, complete or partial functions without relying on smart phones, such as smart watches or smart glasses, and only focus on a certain type of application function, which needs to cooperate with other devices such as smart phones.
  • the network device may be a device for communicating with a mobile device, and the network device may be an access point (Access Point, AP) in WLAN, or a base station (Base Transceiver Station, BTS) in GSM or CDMA , it can also be a base station (NodeB, NB) in WCDMA, it can also be an evolved base station (Evolutional Node B, eNB or eNodeB) in LTE, or a relay station or access point, or in-vehicle equipment, wearable devices and NR networks
  • the network device may have a mobile feature, for example, the network device may be a mobile device.
  • the network device may be a satellite or a balloon station.
  • the satellite may be a low earth orbit (LEO) satellite, a medium earth orbit (MEO) satellite, a geostationary earth orbit (GEO) satellite, a High Elliptical Orbit (HEO) ) satellite etc.
  • the network device may also be a base station set in a location such as land or water.
  • a network device may provide services for a cell, and a terminal device communicates with the network device through transmission resources (for example, frequency domain resources, or spectrum resources) used by the cell, and the cell may be a network device (
  • the cell can belong to the macro base station, or it can belong to the base station corresponding to the small cell (Small cell).
  • Pico cell Femto cell (Femto cell), etc.
  • These small cells have the characteristics of small coverage and low transmission power, and are suitable for providing high-speed data transmission services.
  • the communication system 100 may include a network device 110, and the network device 110 may be a device that communicates with a terminal device 120 (or referred to as a communication terminal, a terminal).
  • the network device 110 may provide communication coverage for a particular geographic area, and may communicate with terminal devices located within the coverage area.
  • FIG. 1 exemplarily shows one network device and two terminal devices.
  • the communication system 100 may include multiple network devices and the coverage of each network device may include other numbers of terminal devices. This application The embodiment does not limit this.
  • the communication system 100 may further include other network entities such as a network controller and a mobility management entity, which are not limited in this embodiment of the present application.
  • network entities such as a network controller and a mobility management entity, which are not limited in this embodiment of the present application.
  • a device having a communication function in the network/system may be referred to as a communication device.
  • the communication device may include a network device 110 and a terminal device 120 with a communication function, and the network device 110 and the terminal device 120 may be the specific devices described above, which will not be repeated here.
  • the communication device may also include other devices in the communication system 100, such as other network entities such as a network controller, a mobility management entity, etc., which are not limited in this embodiment of the present application.
  • the "instruction" mentioned in the embodiments of the present application may be a direct instruction, an indirect instruction, or an associated relationship.
  • a indicates B it can indicate that A directly indicates B, for example, B can be obtained through A; it can also indicate that A indicates B indirectly, such as A indicates C, and B can be obtained through C; it can also indicate that there is an association between A and B relation.
  • corresponding may indicate that there is a direct or indirect corresponding relationship between the two, or may indicate that there is an associated relationship between the two, or indicate and be instructed, configure and be instructed configuration, etc.
  • terminal equipment can use analog beams to transmit uplink data and uplink control information.
  • the terminal device may perform uplink beam management based on a Sounding Reference Signal (Sounding Reference Signal, SRS) signal, so as to determine the analog beam used for uplink transmission.
  • SRS Sounding Reference Signal
  • the network device may configure an SRS resource set for the terminal device, select an SRS resource with the best reception quality based on the SRS transmitted by the terminal device in the SRS resource set, and assign the corresponding SRS resource indicator (SRS resource indicator, SRI ) to notify the terminal device.
  • SRS resource indicator SRS resource indicator
  • the terminal device determines the analog beam used for the SRS resource indicated by the SRI as the analog beam used for transmitting the Physical Uplink Shared Channel (PUSCH).
  • PUSCH Physical Uplink Shared Channel
  • the SRI is indicated by the SRI indication field in the DCI; for the PUSCH scheduled by radio resource control (Radio Resource Control, RRC), the SRI is notified by corresponding scheduling signaling.
  • RRC Radio Resource Control
  • the terminal device configures the physical uplink control channel (Physical Uplink) with spatially related information on the active bandwidth part (Band Width Part, BWP) of the carrier where the PUSCH is located.
  • the transmission beam on the PUCCH resource with the lowest resource identifier (Identity, ID) in the Control Channel (PUCCH) is used as the transmission beam of the PUSCH.
  • the terminal device uses the path loss measurement reference signal of the PUCCH as the PUSCH Path loss measurement reference signal. If there is no PUCCH resource configured on the activated BWP on the carrier where the PUSCH scheduled by the DCI format 0_0 is located, or if the PUCCH resource configured on the activated BWP on the carrier where the PUSCH is located has no spatial related information, the terminal device can The quasi-co-located (QCL) assumption (QCL type D) used by the CORESET with the lowest ID in the activated downlink BWP is used to obtain the transmit beam and path loss measurement reference signal of the PUSCH. For example, the receive beam of the downlink reference signal included in the QCL hypothesis may be used as the transmit beam of the PUSCH, and the downlink reference signal may be used as the path loss measurement reference signal of the PUSCH.
  • QCL quasi-co-located
  • the receive beam of the downlink reference signal included in the QCL hypothesis may be used as the transmit beam of the PUSCH
  • the downlink reference signal
  • each PUCCH-spatialrelationinfo includes a reference signal used to determine the transmission beam of the PUCCH, which can be an SRS or a channel state information reference signal (Channel State Information Reference Signal, CSI-RS) or a synchronization signal block (Synchronization Signal Block, SSB).
  • the PUCCH-spatialrelationinfo may also include power control parameters corresponding to the PUCCH.
  • SRS-spatial relationinfo For each SRS resource, corresponding SRS spatial correlation information (SRS-spatial relationinfo) may also be configured through RRC signaling, which includes a reference signal used to determine the transmission beam of the SRS.
  • PUCCH-spatialrelationinfo is not configured on the network side, the terminal device can use a method similar to PUSCH, according to the QCL assumption (QCL assumption) used by the control resource set (Control Resource Set, CORESET) with the lowest ID in the downlink BWP activated on the carrier where the PUCCH is located. Type D), to obtain the transmission beam of the PUCCH.
  • the receive beam of the downlink reference signal included in the QCL hypothesis may be used as the transmit beam of the PUCCH.
  • the network device can configure a corresponding Transmission Configuration Indicator (TCI) state for each downlink signal or downlink channel, indicating the QCL reference signal corresponding to the target downlink signal or the target downlink channel, so that the terminal is based on the reference signal.
  • TCI Transmission Configuration Indicator
  • a TCI state can contain the following configurations:
  • TCI state ID used to identify a TCI state
  • a QCL information also includes the following information:
  • QCL type (type) configuration which can be one of QCL type A, QCL type B, QCL type C, and QCL type D;
  • the QCL reference signal configuration includes the ID of the cell where the reference signal is located, the BWP ID, and the identifier of the reference signal (which can be a CSI-RS resource ID or an SSB index).
  • the QCL type of at least one of QCL information 1 and QCL information 2 must be one of typeA, typeB, and typeC, and the QCL type of the other QCL information (if configured) must be QCL type D.
  • 'QCL-TypeA' ⁇ Doppler shift, Doppler spread, average delay, delay spread ⁇ ;
  • the terminal device can assume that the target downlink channel is the same as the reference SSB. Or the target large-scale parameters of the reference CSI-RS resources are the same, so that the same corresponding reception parameters are used for reception, and the target large-scale parameters are determined by the QCL type configuration.
  • the terminal device can use and receive the reference SSB or reference CSI-RS resource.
  • the receive beam with the same RS resource (that is, the Spatial Rx parameter) is used to receive the target downlink channel.
  • the target downlink channel and its reference SSB or reference CSI-RS resources are transmitted by the same TRP or the same antenna panel or the same beam on the network side. If the transmission TRPs, transmission panels or transmission beams of the two downlink signals or downlink channels are different, different TCI states are usually configured.
  • the TCI state can be indicated by means of RRC signaling or RRC signaling+MAC signaling.
  • the available TCI state set is indicated by RRC signaling, and some of the TCI states are activated by MAC layer signaling, and finally one or two TCI states are indicated from the activated TCI state by the TCI state indication field in the DCI.
  • TCI status for PDSCH scheduled by the DCI For example, as shown in Figure 2, the network device indicates N candidate TCI states through RRC signaling, activates K TCI states through MAC signaling, and finally indicates 1 from the activated TCI state through the TCI state indication field in DCI 1 or 2 TCI states used.
  • Release 16 In order to meet the transmission delay and reliability requirements of the Physical Downlink Shared Channel (PDSCH), Release 16 (Release 16, Rel-16) introduces a multi-transmission/reception point (TRP) based PDSCH diversity transmission, received by frequency division multiplexing (Frequency-division multiplexing, FDM), time division multiplexing mode (Testing Data Management/Technical Data Management, TDM) or space division multiplexing (Space Division Multiplexing, SDM) Data transmitted by different TRPs.
  • FDM Frequency-division multiplexing
  • TDM Time division multiplexing mode
  • SDM Space Division Multiplexing
  • a similar mechanism can also be used for PUCCH transmission to improve the transmission reliability of PUCCH.
  • the terminal device can use the same PUCCH resource in different time slots to repeatedly transmit the same PUCCH (carrying the same uplink control information (Uplink Control Information, UCI)). Since the PUCCHs in different time slots are sent to different TRPs, the used transmit beams and power control parameters (such as path loss measurement reference signals) are also configured independently, as shown in FIG. 3 .
  • N pieces of spatial correlation information PUCCH-spatialrelationinfo or N pieces of TCI status can be indicated for one PUCCH resource, which are respectively used for repeated transmission of PUCCH in different time slots, and the transmission beam and power control parameters of PUCCH can be obtained from the N pieces of spatial correlation information.
  • the transmit power of the PUSCH can be calculated by the following formula 1:
  • P CMAX,f,c (i) is the maximum transmit power on the current carrier of the terminal
  • i is the index of a PUSCH transmission
  • j is the open-loop power control parameter index (including the target power P O_PUSCH,b ,f,c (j) and path loss factor ⁇ b,f,c (j))
  • q d is the index of the reference signal used for path loss measurement, used to obtain the path loss value
  • PL b,f,c ( q d ) is also an open-loop power control parameter
  • f b,f,c (i,l) is the closed-loop power control adjustment state, where l is the index of the closed-loop power control adjustment state.
  • the terminal determines the closed-loop power adjustment factor according to a transmission power control (Transmission Power Control, TPC) command field sent by the network side, and the TPC command field can be carried by the DCI used for scheduling the PUSCH in the terminal search space, or It can be carried by DCI format 2_2 for carrying the group TPC command field in the common search space.
  • TPC Transmission Power Control
  • the closed-loop power control adjustment states corresponding to different closed-loop power control adjustment state indexes are independently calculated, so that different PUSCH transmission powers can be obtained.
  • the terminal device can repeatedly transmit the same PUCCH using the same PUCCH resource and different transmission parameters (such as transmit beam and power control parameters) in different time slots. If the PUCCH resource with the lowest PUCCH resource ID on the active BWP of the carrier where the PUSCH is located is configured with multiple spatially related information (such as multiple beams), how to determine the beam and path loss measurement reference signal of the PUSCH scheduled by DCI format 0_0 is an urgent problem to be solved. The problem.
  • the present application proposes a scheme for determining uplink transmission parameters. If the PUCCH resource with the lowest PUCCH resource ID in the uplink BWP activated on the carrier where the PUSCH is located is configured with multiple sets of transmission parameters (transmission beam and/or or path loss measurement reference signal), the terminal device may determine the transmission parameters of the PUSCH (transmission beam and/or path loss measurement reference signal) based on the solution of the present application. Specifically, the terminal device can select other PUCCH resources that are not configured with multiple spatial-related information to obtain the PUSCH transmission parameters, or use the PUCCH transmission parameters sent to the same TRP as the PUSCH transmission parameters, or obtain from the QCL assumption of the downlink signal. PUSCH transmission parameters, so that the problem of inability to determine PUSCH transmission parameters can be solved without signaling.
  • FIG. 5 is a schematic flowchart of a method 200 for determining uplink transmission parameters according to an embodiment of the present application. As shown in FIG. 5 , the method 200 may include at least part of the following contents:
  • the terminal device determines the transmission parameter of the PUSCH according to the transmission parameter on the PUCCH resource in the uplink BWP activated on the carrier where the PUSCH is located, where the PUSCH is the PUSCH scheduled in the first DCI format, and the transmission parameter is the transmission beam And/or the transmission parameter is a reference signal used for path loss measurement.
  • the first DCI format is DCI format 0_0.
  • the DCI format 0_0 is used for PUSCH scheduling, and the SRS resource indication (SRI) is not included in the DCI format 0_0.
  • the network device can configure an SRS resource set for the terminal device, and select an SRS with the best reception quality based on the SRS transmitted by the terminal device in the SRS resource set. resources, and notify the terminal equipment of the corresponding SRS resource indication (SRI). After receiving the SRI, the terminal device determines the analog beam used for the SRS resource indicated by the SRI as the analog beam used for transmitting the PUSCH.
  • DCI format 0_0 scheduling PUSCH since DCI format 0_0 does not include SRS resource indication (SRI), the terminal device cannot determine the analog beam used for transmitting PUSCH based on the analog beam used for SRS resource indicated by the SRI.
  • SRI SRS resource indication
  • the reference signal used for the transmission beam of the PUCCH resource and the path loss measurement can be obtained through spatial correlation information (for example, PUCCH-spatial relationinfo), or can be obtained through the TCI state to get. Therefore, the transmission parameter of the PUCCH resource in the embodiment of the present application may refer to the space-related information of the PUCCH resource or the TCI state.
  • the transmit beam may also be referred to as a spatial domain transmission filter (Spatial domain transmission filter or Spatial domain filter for transmission), or a spatial relation (Spatial relation) or a spatial setting (spatial setting).
  • the receive beam may also be called a spatial domain reception filter (Spatial domain reception filter or Spatial domain filter for reception) or a spatial reception parameter (Spatial Rx parameter).
  • the reference signal used for path loss measurement may be a downlink reference signal used for path loss measurement, such as CSI-RS or SSB, and the terminal device may calculate the transmit power of the PUSCH according to the measured path loss value, For example, the transmission power of the PUSCH is calculated based on the above formula 1.
  • multiple PUCCH resources may be configured in the uplink BWP, and each PUCCH resource may be independently configured with resource identifiers and PUCCH transmission parameters (for example, configured through PUCCH space-related information).
  • some PUCCH resources are not configured with a transmit beam (for example, no PUCCH spatial related information is configured), some PUCCH resources are only configured with a single transmit beam (for example, only one PUCCH spatial related information is configured), and some PUCCH resources are configured with multiple transmit beams (For example, configure multiple PUCCH space-related information, which are respectively used for transmission of different repetitions). That is to say, in this embodiment of the present application, multi-TRP-based PUCCH diversity transmission may be used in the uplink BWP.
  • S210 may specifically determine the transmission parameter of the PUSCH through one or more of the following solutions in Example 1 to Example 3.
  • Example 1 the terminal device determines the transmission parameter on the PUCCH resource with the lowest resource identifier among the PUCCH resources activated on the carrier on which the PUSCH is located, which is configured with only one set of transmission parameters, as the transmission parameter of the PUSCH.
  • Example 1 for example, as shown in FIG. 6 , 5 PUCCH resources are configured in the activated uplink BWP on the carrier where the PUSCH is located, which are denoted as PUCCH resource 0, PUCCH resource 1, PUCCH resource 2, PUCCH resource 3 and PUCCH respectively Resource 4, the PUSCH is scheduled by DCI format 0_0.
  • PUCCH resource 0 is configured with 2 sets of transmission parameters (such as PUCCH spatial related information 0 and PUCCH spatial related information 1)
  • PUCCH resource 1 is configured with 1 set of transmission parameters (such as PUCCH spatial related information 2)
  • PUCCH resource 2 One group of transmission parameters (such as PUCCH space related information 3) is configured, and no transmission parameters are configured on PUCCH resource 3, that is, PUCCH resource 3 has no PUCCH space related information
  • PUCCH resource 4 is configured with two groups of transmission parameters (such as PUCCH space related information) 4 and PUCCH space related information 5).
  • the PUCCH resource configured with only one group of transmission parameters includes PUCCH resource 1 and PUCCH resource 2, and the PUCCH resource with the lowest resource identifier among PUCCH resource 1 and PUCCH resource 2 is PUCCH resource 1.
  • the transmission parameter of the PUCCH resource 1 is used as the transmission parameter of the PUSCH.
  • the terminal device uses the transmission beam of PUCCH resource 1 as the transmission beam of the PUSCH.
  • the terminal device uses the reference signal used for the path loss measurement of the PUCCH resource 1 as the reference signal used for the path loss measurement of the PUSCH.
  • Example 1 when multi-TRP-based PUCCH diversity transmission is used in the uplink BWP activated on the carrier where the PUSCH is located, the terminal device can configure only one set of transmission parameters in the uplink BWP activated on the carrier where the PUSCH is located.
  • the transmission parameter on the PUCCH resource with the lowest resource identifier among the PUCCH resources is determined as the transmission parameter of the PUSCH, thereby avoiding the problem of multiple sets of transmission parameters for the PUCCH resource used to obtain the PUSCH transmission parameter.
  • Example 2 if the PUCCH resource with the lowest resource identifier in the uplink BWP activated on the carrier where the PUSCH is located is configured with multiple sets of transmission parameters, the terminal device determines the target transmission parameter in the multiple sets of transmission parameters as the transmission parameter of the PUSCH.
  • the target transmission parameter is a pre-agreed group of transmission parameters in the multiple groups of transmission parameters, or the target transmission parameter is a pre-configured group of transmission parameters in the multiple groups of transmission parameters, Or, the target transmission parameter is a group of transmission parameters indicated by the network device in the multiple groups of transmission parameters.
  • the PUCCH resource with the lowest resource identifier in the uplink BWP is configured with two sets of transmission parameters, which are respectively used for odd-numbered PUCCH repeated transmission and even-numbered PUCCH repeated transmission.
  • the terminal device may determine the first group of transmission parameters in the two groups of transmission parameters as the transmission parameters of the PUSCH.
  • the PUCCH resource with the lowest resource identifier in the uplink BWP is configured with two PUCCH spatial related information, which are respectively used for odd-numbered PUCCH repeated transmissions and even-numbered PUCCH repeated transmissions.
  • the terminal device can use the transmission beam indicated by the first PUCCH spatial correlation information as the transmission beam of the PUSCH; and use the path loss measurement reference signal indicated by the first PUCCH spatial correlation information as the path loss measurement reference of the PUSCH Signal.
  • the terminal device may use the transmission beam indicated by the second PUCCH spatial correlation information as the transmission beam of the PUSCH; and the path loss measurement reference signal indicated by the second PUCCH spatial correlation information as the path loss of the PUSCH Measurement reference signal.
  • the target transmission parameter is a CORESET group index (CORESETPoolIndex) of the CORESET where the DCI that schedules the PUSCH is determined from the multiple groups of transmission parameters.
  • the target transmission parameter is determined from the multiple groups of transmission parameters based on the CORESET group index and a first correspondence, wherein the first correspondence is the value of the CORESET group index and the transmission parameter Correspondence of group IDs.
  • the CORESET group index may occupy N bits, where N is an integer greater than or equal to 1.
  • N is an integer greater than or equal to 1.
  • the CORESET group index may take values of 0 and 1.
  • the CORESET group index values may be 00, 01, 10, and 11.
  • the CORESET group index values may be 000, 001, 010, 011, 100, 101, 110, and 111.
  • the target transmission parameter is the first group of transmission parameters in the multiple groups of transmission parameters; if the CORESET group index is 1, The target transmission parameter is the second group of transmission parameters in the multiple groups of transmission parameters.
  • the target transmission parameter is the first group of transmission parameters in the multiple groups of transmission parameters; if the CORESET group index is 01, The target transmission parameter is the second group of transmission parameters in the multiple groups of transmission parameters.
  • the network device may configure a CORESET group index (CORESETPoolIndex) for each CORESET in advance, and different CORESETs may use the same CORESET group index, or may use different CORESET group indexes.
  • CORESETPoolIndex CORESET group index
  • the terminal device may assume that the CORESET group index of the CORESET is 0.
  • the terminal device detects the PDCCH carrying the DCI scheduling the PUSCH in the first CORESET, the terminal device determines the target transmission parameter from the multiple sets of transmission parameters according to the CORESET group index of the first CORESET.
  • the PUCCH resource is configured with two sets of transmission parameters. If the CORESET group index of the first CORESET is 0 or the first CORESET is not configured with a CORESET group index, then The first group of transmission parameters in the two groups of transmission parameters is used as the transmission parameter of the PUSCH; if the CORESET group index of the first CORESET is 1, the second group of transmission parameters in the two groups of transmission parameters is used as the transmission parameter of the PUSCH; Transmission parameters of PUSCH.
  • this method can also be used in the case where the PUCCH resource is configured with more than two sets of transmission parameters.
  • Example 2 when PUCCH diversity transmission based on multi-TRP is used in the uplink BWP activated on the carrier where the PUSCH is located, the terminal device can use the PUCCH transmission parameters of the PUCCH in the diversity transmission that are the same as the PUSCH receiving TRP as the transmission parameter PUSCH transmission parameters, so as to ensure that different channels sent to the same TRP use the same transmission parameters.
  • Example 3 the terminal device determines the transmission parameters of the PUSCH according to the number of transmission parameters configured in the PUCCH resource with the lowest resource identifier in the uplink BWP activated on the carrier where the PUSCH is located.
  • three PUCCH resources are configured in the activated uplink BWP on the carrier where the PUSCH is located, which are denoted as PUCCH resource 0, PUCCH resource 1 and PUCCH resource 2 respectively.
  • the terminal device can configure the transmission parameters according to PUCCH resource 0 The number of , determines the transmission parameters of the PUSCH.
  • Example 3 if the number of the transmission parameters is equal to 1, the terminal device determines the transmission parameter of the PUCCH resource configuration with the lowest resource identifier in the uplink BWP as the transmission parameter of the PUSCH;
  • the terminal device obtains the transmission parameters of the PUSCH from the QCL assumption used by the target CORESET, where the target CORESET is the CORESET configured on the downlink BWP activated on the carrier where the PUSCH is located, CORESET Identifies the lowest CORESET.
  • CORESETs are configured on the downlink BWP activated on the carrier where the PUSCH is located, namely CORESET 0, CORESET 1 and CORESET 2, then the CORESET with the lowest CORESET ID is CORESET 0, that is, the target CORESET is CORESET 0.
  • the network device may configure a CORESET identifier for each CORESET in advance, and the CORESET identifiers of different CORESETs are different, which are used to identify the CORESET.
  • the terminal device uses the downlink reference signal corresponding to the QCL assumption (QCL type is QCL type-D) used by the target CORESET as the reference signal used for the path loss measurement of the PUSCH .
  • the terminal device uses the receive beam of the downlink reference signal corresponding to the QCL assumption used by the target CORESET (QCL type is QCL type-D) as the transmit beam of the PUSCH.
  • Example 3 if the number of the transmission parameters is equal to 1, the terminal device determines the transmission parameter of the PUCCH resource configuration with the lowest resource identifier in the uplink BWP as the transmission parameter of the PUSCH;
  • the terminal device obtains the transmission parameters of the PUSCH from the QCL assumption used by the target CORESET, where the target CORESET is the CORESET where the DCI that schedules the PUSCH is located.
  • the terminal device detects in CORESET 1 the PDCCH carrying the DCI that schedules the PUSCH, it obtains the transmission parameters of the PUSCH from the QCL assumption used in CORESET 1.
  • the terminal device uses the downlink reference signal corresponding to the QCL assumption (QCL type is QCL type-D) used by CORESET 1 as the reference used for the path loss measurement of the PUSCH Signal.
  • the terminal device uses the receive beam of the downlink reference signal corresponding to the QCL assumption used by CORESET 1 (QCL type is QCL type-D) as the transmit beam of the PUSCH.
  • Example 3 if the number of the transmission parameters is equal to 1, the terminal device determines the transmission parameter of the PUCCH resource configuration with the lowest resource identifier in the uplink BWP as the transmission parameter of the PUSCH;
  • the terminal device obtains the transmission parameters of the PUSCH from the target TCI state, where the target TCI state is the downlink BWP activated on the carrier where the PUSCH is located for PDSCH transmission.
  • the TCI state identifies the lowest TCI state.
  • the downlink BWP activated on the carrier where the PUSCH is located is configured with five TCI states, namely TCI state 0, TCI state 1, TCI state 2, TCI state 3, and TCI state 4.
  • the TCI states of PDSCH transmission include: TCI state 2, TCI state 3 and TCI state 4. Then, among the TCI states activated for PDSCH transmission in the downlink BWP activated on the carrier where the PUSCH is located, the TCI state with the lowest TCI state identifier is TCI state 2, that is, the target TCI state is TCI state 2.
  • the network device activates the TCI state for PDSCH transmission through a Media Access Control Control Element (Media Access Control Element, MAC CE) in advance.
  • Media Access Control Element Media Access Control Element, MAC CE
  • the terminal device uses the TCI state activated for PDSCH transmission in the downlink BWP activated on the carrier where the PUSCH is located, and the TCI state with the lowest TCI state identifier.
  • the downlink reference signal (QCL type is QCL type-D) is used as a reference signal for path loss measurement of PUSCH.
  • the terminal device uses the downlink reference signal ( The receiving beam whose QCL type is QCL type-D) is used as the sending beam of PUSCH; or, the terminal device uses the TCI state activated for PDSCH transmission in the downlink BWP activated on the carrier where the PUSCH is located, and the one with the lowest TCI state identifier
  • the transmission beam of the uplink reference signal included in the TCI state is used as the transmission beam of the PUSCH.
  • the terminal device can configure the number of transmission parameters according to the PUCCH resource with the lowest resource identifier in the uplink BWP activated on the carrier where the PUSCH is located, that is, according to whether the PUCCH resource performs multi-TRP-based PUCCH diversity transmission, Correspondingly different methods are used to determine the transmission parameters of the PUSCH, thereby simultaneously supporting two scenarios of single-TRP PUCCH transmission and multi-TRP cooperative PUCCH diversity transmission.
  • CORESETs configured with different CORESET group indexes may come from different TRPs.
  • the CORESET configured with CORESET group index 0 is transmitted from TRP 0
  • the CORESET configured with CORESET group index of 1 is transmitted from TRP. 1.
  • the terminal device transmits the PUSCH according to the determined transmission parameter of the PUSCH.
  • the terminal device may use the transmission beam to transmit the PUSCH.
  • the terminal device may use the reference signal to perform path loss measurement, and calculate the transmit power of the PUSCH according to the measured path loss value.
  • the terminal device in the case where the PUCCH resource with the lowest resource identifier in the uplink BWP activated on the carrier where the PUSCH is located is configured with multiple spatially related information, the terminal device can determine the transmission parameters of the PUSCH scheduled by DCI format 0_0 .
  • the terminal device may determine the transmission parameters of the PUSCH scheduled by the DCI format 0_0.
  • the terminal device can select other PUCCH resources that are not configured with multiple spatial related information to obtain the transmission parameters of the PUSCH, or use the transmission parameters of the PUCCH sent to the same TRP as the transmission parameters of the PUSCH, or obtain from the QCL assumption of the downlink signal.
  • PUSCH transmission parameters so that the problem that the PUSCH transmission parameters cannot be determined can be solved without signaling.
  • FIG. 7 shows a schematic block diagram of a terminal device 300 according to an embodiment of the present application.
  • the terminal device 300 includes:
  • the processing unit 310 is configured to determine the transmission parameter of the PUSCH according to the transmission parameter on the PUCCH resource in the uplink BWP activated on the carrier where the PUSCH is located, wherein the PUSCH is the PUSCH scheduled in the first DCI format, and the transmission parameter is
  • the transmit beam and/or the transmission parameters are reference signals used for path loss measurements.
  • processing unit 310 is specifically configured to:
  • the transmission parameter on the PUCCH resource with the lowest resource identifier among the PUCCH resources configured with only one set of transmission parameters in the uplink BWP is determined as the transmission parameter of the PUSCH.
  • processing unit 310 is specifically configured to:
  • the target transmission parameter in the multiple sets of transmission parameters is determined as the transmission parameter of the PUSCH.
  • the target transmission parameter is a pre-agreed group of transmission parameters in the multiple groups of transmission parameters, or the target transmission parameter is a pre-configured group of transmission parameters in the multiple groups of transmission parameters, or the target transmission parameter The parameter is a group of transmission parameters indicated by the network device in the multiple groups of transmission parameters.
  • the target transmission parameter is determined from the multiple groups of transmission parameters according to the CORESET group index of the CORESET where the DCI that schedules the PUSCH is located.
  • the target transmission parameter is determined from the multiple groups of transmission parameters according to the CORESET group index and a first correspondence, wherein the first correspondence is the value of the CORESET group index and the correspondence of the transmission parameter group identifier. relation.
  • the target transmission parameter is the first group of transmission parameters in the multiple groups of transmission parameters; if the CORESET group index is 1, the target transmission parameter is the multiple groups of transmission parameters.
  • processing unit 310 is specifically configured to:
  • the transmission parameters of the PUSCH are determined according to the number of transmission parameters configured in the PUCCH resource with the lowest resource identifier in the uplink BWP.
  • processing unit 310 is specifically configured to:
  • the transmission parameters of the PUSCH are obtained from the quasi-co-located QCL assumption used by the target CORESET, where the target CORESET is the CORESET configured on the downlink BWP activated on the carrier where the PUSCH is located, CORESET The lowest CORESET is identified, or the target CORESET is the CORESET where the DCI that schedules the PUSCH is located.
  • processing unit 310 is specifically configured to:
  • the TCI state identifies the lowest TCI state.
  • the terminal device 300 further includes:
  • the communication unit 320 is configured to transmit the PUSCH according to the determined transmission parameter of the PUSCH.
  • the first DCI format is DCI format 0_0.
  • the above-mentioned communication unit may be a communication interface or a transceiver, or an input/output interface of a communication chip or a system-on-chip.
  • the aforementioned processing unit may be one or more processors.
  • terminal device 300 may correspond to the terminal device in the method embodiment of the present application, and the above-mentioned and other operations and/or functions of the various units in the terminal device 300 are respectively for realizing the method shown in FIG. 5 .
  • the corresponding process of the terminal device in 200 is not repeated here for brevity.
  • FIG. 8 is a schematic structural diagram of a communication device 400 provided by an embodiment of the present application.
  • the communication device 400 shown in FIG. 8 includes a processor 410, and the processor 410 can call and run a computer program from a memory, so as to implement the method in the embodiment of the present application.
  • the communication device 400 may further include a memory 420 .
  • the processor 410 may call and run a computer program from the memory 420 to implement the methods in the embodiments of the present application.
  • the memory 420 may be a separate device independent of the processor 410 , or may be integrated in the processor 410 .
  • the communication device 400 may further include a transceiver 430, and the processor 410 may control the transceiver 430 to communicate with other devices, specifically, may send information or data to other devices, or receive other Information or data sent by the device.
  • the transceiver 430 may include a transmitter and a receiver.
  • the transceiver 430 may further include antennas, and the number of the antennas may be one or more.
  • the communication device 400 may specifically be the network device in this embodiment of the present application, and the communication device 400 may implement the corresponding processes implemented by the network device in each method in the embodiment of the present application. For the sake of brevity, details are not repeated here. .
  • the communication device 400 may specifically be the mobile terminal/terminal device in the embodiments of the present application, and the communication device 400 may implement the corresponding processes implemented by the mobile terminal/terminal device in each method in the embodiments of the present application. , and will not be repeated here.
  • FIG. 9 is a schematic structural diagram of an apparatus according to an embodiment of the present application.
  • the apparatus 500 shown in FIG. 9 includes a processor 510, and the processor 510 can call and run a computer program from a memory, so as to implement the method in this embodiment of the present application.
  • the apparatus 500 may further include a memory 520 .
  • the processor 510 may call and run a computer program from the memory 520 to implement the methods in the embodiments of the present application.
  • the memory 520 may be a separate device independent of the processor 510 , or may be integrated in the processor 510 .
  • the apparatus 500 may further include an input interface 530 .
  • the processor 510 may control the input interface 530 to communicate with other devices or chips, and specifically, may acquire information or data sent by other devices or chips.
  • the apparatus 500 may further include an output interface 540 .
  • the processor 510 may control the output interface 540 to communicate with other devices or chips, and specifically, may output information or data to other devices or chips.
  • the apparatus can be applied to the network equipment in the embodiments of the present application, and the apparatus can implement the corresponding processes implemented by the network equipment in the various methods of the embodiments of the present application, which are not repeated here for brevity.
  • the apparatus can be applied to the mobile terminal/terminal equipment in the embodiments of the present application, and the apparatus can implement the corresponding processes implemented by the mobile terminal/terminal equipment in each method of the embodiments of the present application.
  • the apparatus can implement the corresponding processes implemented by the mobile terminal/terminal equipment in each method of the embodiments of the present application.
  • the apparatus can implement the corresponding processes implemented by the mobile terminal/terminal equipment in each method of the embodiments of the present application.
  • the device mentioned in the embodiment of the present application may also be a chip.
  • it can be a system-on-chip, a system-on-a-chip, a system-on-a-chip, or a system-on-a-chip.
  • FIG. 10 is a schematic block diagram of a communication system 600 provided by an embodiment of the present application. As shown in FIG. 10 , the communication system 600 includes a terminal device 610 and a network device 620 .
  • the terminal device 610 can be used to implement the corresponding functions implemented by the terminal device in the above method
  • the network device 620 can be used to implement the corresponding functions implemented by the network device in the above method. For brevity, details are not repeated here. .
  • the processor in this embodiment of the present application may be an integrated circuit chip, which has a signal processing capability.
  • each step of the above method embodiments may be completed by a hardware integrated logic circuit in a processor or an instruction in the form of software.
  • the above-mentioned processor can be a general-purpose processor, a digital signal processor (Digital Signal Processor, DSP), an application specific integrated circuit (Application Specific Integrated Circuit, ASIC), an off-the-shelf programmable gate array (Field Programmable Gate Array, FPGA) or other available Programming logic devices, discrete gate or transistor logic devices, discrete hardware components.
  • DSP Digital Signal Processor
  • ASIC Application Specific Integrated Circuit
  • FPGA Field Programmable Gate Array
  • a general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
  • the steps of the method disclosed in conjunction with the embodiments of the present application may be directly embodied as executed by a hardware decoding processor, or executed by a combination of hardware and software modules in the decoding processor.
  • the software modules may be located in random access memory, flash memory, read-only memory, programmable read-only memory or electrically erasable programmable memory, registers and other storage media mature in the art.
  • the storage medium is located in the memory, and the processor reads the information in the memory, and completes the steps of the above method in combination with its hardware.
  • the memory in this embodiment of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memory.
  • the non-volatile memory may be a read-only memory (Read-Only Memory, ROM), a programmable read-only memory (Programmable ROM, PROM), an erasable programmable read-only memory (Erasable PROM, EPROM), an electrically programmable read-only memory (Erasable PROM, EPROM). Erase programmable read-only memory (Electrically EPROM, EEPROM) or flash memory.
  • Volatile memory may be Random Access Memory (RAM), which acts as an external cache.
  • RAM Static RAM
  • DRAM Dynamic RAM
  • SDRAM Synchronous DRAM
  • SDRAM double data rate synchronous dynamic random access memory
  • Double Data Rate SDRAM DDR SDRAM
  • enhanced SDRAM ESDRAM
  • synchronous link dynamic random access memory Synchlink DRAM, SLDRAM
  • Direct Rambus RAM Direct Rambus RAM
  • the memory in the embodiment of the present application may also be a static random access memory (static RAM, SRAM), a dynamic random access memory (dynamic RAM, DRAM), Synchronous dynamic random access memory (synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (double data rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchronous connection Dynamic random access memory (synch link DRAM, SLDRAM) and direct memory bus random access memory (Direct Rambus RAM, DR RAM) and so on. That is, the memory in the embodiments of the present application is intended to include but not limited to these and any other suitable types of memory.
  • Embodiments of the present application further provide a computer-readable storage medium for storing a computer program.
  • the computer-readable storage medium can be applied to the mobile terminal/terminal device in the embodiments of the present application, and the computer program enables the computer to execute the corresponding processes implemented by the mobile terminal/terminal device in each method of the embodiments of the present application. , and are not repeated here for brevity.
  • the computer program product can be applied to the mobile terminal/terminal device in the embodiments of the present application, and the computer program instructions cause the computer to execute the corresponding processes implemented by the mobile terminal/terminal device in each method of the embodiments of the present application, For brevity, details are not repeated here.
  • the embodiments of the present application also provide a computer program.
  • the computer program may be applied to the mobile terminal/terminal device in the embodiments of the present application, and when the computer program is run on the computer, the mobile terminal/terminal device implements the various methods of the computer program in the embodiments of the present application.
  • the corresponding process for the sake of brevity, will not be repeated here.
  • the disclosed system, apparatus and method may be implemented in other manners.
  • the apparatus embodiments described above are only illustrative.
  • the division of the units is only a logical function division. In actual implementation, there may be other division methods.
  • multiple units or components may be combined or Can be integrated into another system, or some features can be ignored, or not implemented.
  • the shown or discussed mutual coupling or direct coupling or communication connection may be through some interfaces, indirect coupling or communication connection of devices or units, and may be in electrical, mechanical or other forms.
  • the units described as separate components may or may not be physically separated, and components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution in this embodiment.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically alone, or two or more units may be integrated into one unit.
  • the functions, if implemented in the form of software functional units and sold or used as independent products, may be stored in a computer-readable storage medium.
  • the technical solution of the present application can be embodied in the form of a software product in essence, or the part that contributes to the prior art or the part of the technical solution.
  • the computer software product is stored in a storage medium, including Several instructions are used to cause a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present application.
  • the aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), magnetic disk or optical disk and other media that can store program codes .

Landscapes

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

Abstract

本申请实施例提供了一种用于确定上行传输参数的方法和终端设备，在PUSCH所在的载波上激活的上行BWP中资源标识最低的PUCCH资源被配置了多组传输参数的情况下，终端设备可以确定DCI格式0_0调度的PUSCH的传输参数。该用于确定上行传输参数的方法包括：终端设备根据PUSCH所在的载波上激活的上行BWP中的PUCCH资源上的传输参数，确定该PUSCH的传输参数，其中，该PUSCH为采用第一DCI格式调度的PUSCH，该传输参数为发送波束和/或该传输参数为路损测量所用的参考信号。

Description

用于确定上行传输参数的方法和终端设备 技术领域
本申请实施例涉及通信领域，并且更具体地，涉及一种用于确定上行传输参数的方法和终端设备。
背景技术
在新空口(New Radio，NR)系统中，对于下行控制信息(Downlink Control Information，DCI)格式0_0调度的物理上行共享信道(Physical Uplink Shared Channel，PUSCH)，终端设备可以将PUSCH所在的载波上激活的上行带宽部分(Band Width Part，BWP)中资源标识最低的PUCCH资源上的发送波束，作为该PUSCH的发送波束。
为了提高PUCCH的传输可靠性，引入了基于多发送接收点(Transmission/Reception Point，TRP)的PUCCH分集传输，终端设备可以在不同的时隙中使用同一PUCCH资源和不同的传输参数(如发送波束和功率控制参数)重复传输同一个PUCCH。在多TRP的PUCCH分集传输的场景下，PUSCH所在的载波上激活的上行BWP中资源标识最低的PUCCH资源可能被配置了多个空间相关信息(即多个发送波束)，而此时PUSCH可以只进行单个TRP的传输(即只能使用单个波束传输)。此种情况下，如何确定DCI格式0_0调度的PUSCH的传输参数(如发送波束)是一个亟待解决的问题。
发明内容
本申请实施例提供了一种用于确定上行传输参数的方法和终端设备，在PUSCH所在的载波上激活的上行BWP中资源标识最低的PUCCH资源被配置了多组传输参数的情况下，终端设备可以确定DCI格式0_0调度的PUSCH的传输参数。
第一方面，提供了一种用于确定上行传输参数的方法，该方法包括：
终端设备根据PUSCH所在的载波上激活的上行BWP中的PUCCH资源上的传输参数，确定该PUSCH的传输参数，其中，该PUSCH为采用第一DCI格式调度的PUSCH，该传输参数为发送波束和/或该传输参数为路损测量所用的参考信号。
可选地，该第一DCI格式为DCI格式0_0。
第二方面，提供了一种终端设备，用于执行上述第一方面中的方法。
具体地，该终端设备包括用于执行上述第一方面中的方法的功能模块。
第三方面，提供了一种终端设备，包括处理器和存储器。该存储器用于存储计算机程序，该处理器用于调用并运行该存储器中存储的计算机程序，执行上述第一方面中的方法。
第四方面，提供了一种装置，用于实现上述第一方面中的方法。
具体地，该装置包括：处理器，用于从存储器中调用并运行计算机程序，使得安装有该装置的设备执行如上述第一方面中的方法。
第五方面，提供了一种计算机可读存储介质，用于存储计算机程序，该计算机程序使得计算机执行上述第一方面中的方法。
第六方面，提供了一种计算机程序产品，包括计算机程序指令，所述计算机程序指令使得计算机执行上述第一方面中的方法。
第七方面，提供了一种计算机程序，当其在计算机上运行时，使得计算机执行上述第一方面中的方法。
通过上述技术方案，在PUSCH所在的载波上激活的上行BWP中资源标识最低的PUCCH资源被配置了多组传输参数的情况下，终端设备可以确定DCI格式0_0调度的PUSCH的传输参数。
附图说明
图1是本申请实施例应用的一种通信系统架构的示意性图。
图2是本申请提供的一种PDSCH的TCI状态配置的示意性图。
图3是本申请提供的一种PUCCH重复传输的示意性图。
图4是本申请提供的一种基于多TRP的PUCCH分集传输的示意性图。
图5是根据本申请实施例提供的一种用于确定上行传输参数的方法的示意性流程图。
图6是根据本申请实施例提供的一种确定PUSCH传输参数的示意性图。
图7是根据本申请实施例提供的一种终端设备的示意性框图。
图8是根据本申请实施例提供的一种通信设备的示意性框图。
图9是根据本申请实施例提供的一种装置的示意性框图。
图10是根据本申请实施例提供的一种通信系统的示意性框图。
具体实施方式
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行描述，显然，所描述的实施例是本申请一部分实施例，而不是全部的实施例。针对本申请中的实施例，本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例，都属于本申请保护的范围。
本申请实施例的技术方案可以应用于各种通信系统，例如：全球移动通讯(Global System of Mobile communication，GSM)系统、码分多址(Code Division Multiple Access，CDMA)系统、宽带码分多址(Wideband Code Division Multiple Access，WCDMA)系统、通用分组无线业务(General Packet Radio Service，GPRS)、长期演进(Long Term Evolution，LTE)系统、先进的长期演进(Advanced long term evolution，LTE-A)系统、新空口(New Radio，NR)系统、NR系统的演进系统、非授权频谱上的LTE(LTE-based access to unlicensed spectrum，LTE-U)系统、非授权频谱上的NR(NR-based access to unlicensed spectrum，NR-U)系统、非地面通信网络(Non-Terrestrial Networks，NTN)系统、通用移动通信系统(Universal Mobile Telecommunication System，UMTS)、无线局域网(Wireless Local Area Networks，WLAN)、无线保真(Wireless Fidelity，WiFi)、第五代通信(5th-Generation，5G)系统或其他通信系统等。
通常来说，传统的通信系统支持的连接数有限，也易于实现，然而，随着通信技术的发展，移动通信系统将不仅支持传统的通信，还将支持例如，设备到设备(Device to Device，D2D)通信，机器到机器(Machine to Machine，M2M)通信，机器类型通信(Machine Type Communication，MTC)，车辆间(Vehicle to Vehicle，V2V)通信，或车联网(Vehicle to everything，V2X)通信等，本申请实施例也可以应用于这些通信系统。
可选地，本申请实施例中的通信系统可以应用于载波聚合(Carrier Aggregation，CA)场景，也可以应用于双连接(Dual Connectivity，DC)场景，还可以应用于独立(Standalone，SA)布网场景。
可选地，本申请实施例中的通信系统可以应用于非授权频谱，其中，非授权频谱也可以认为是共享频谱；或者，本申请实施例中的通信系统也可以应用于授权频谱，其中，授权频谱也可以认为是非共享频谱。
本申请实施例结合网络设备和终端设备描述了各个实施例，其中，终端设备也可以称为用户设备(User Equipment，UE)、接入终端、用户单元、用户站、移动站、移动台、远方站、远程终端、移动设备、用户终端、终端、无线通信设备、用户代理或用户装置等。
终端设备可以是WLAN中的站点(STAION，ST)，可以是蜂窝电话、无绳电话、会话启动协议(Session Initiation Protocol，SIP)电话、无线本地环路(Wireless Local Loop，WLL)站、个人数字处理(Personal Digital Assistant，PDA)设备、具有无线通信功能的 手持设备、计算设备或连接到无线调制解调器的其它处理设备、车载设备、可穿戴设备、下一代通信系统例如NR网络中的终端设备，或者未来演进的公共陆地移动网络(Public Land Mobile Network，PLMN)网络中的终端设备等。
在本申请实施例中，终端设备可以部署在陆地上，包括室内或室外、手持、穿戴或车载；也可以部署在水面上(如轮船等)；还可以部署在空中(例如飞机、气球和卫星上等)。
在本申请实施例中，终端设备可以是手机(Mobile Phone)、平板电脑(Pad)、带无线收发功能的电脑、虚拟现实(Virtual Reality，VR)终端设备、增强现实(Augmented Reality，AR)终端设备、工业控制(industrial control)中的无线终端设备、无人驾驶(self driving)中的无线终端设备、远程医疗(remote medical)中的无线终端设备、智能电网(smart grid)中的无线终端设备、运输安全(transportation safety)中的无线终端设备、智慧城市(smart city)中的无线终端设备或智慧家庭(smart home)中的无线终端设备等。
作为示例而非限定，在本申请实施例中，该终端设备还可以是可穿戴设备。可穿戴设备也可以称为穿戴式智能设备，是应用穿戴式技术对日常穿戴进行智能化设计、开发出可以穿戴的设备的总称，如眼镜、手套、手表、服饰及鞋等。可穿戴设备即直接穿在身上，或是整合到用户的衣服或配件的一种便携式设备。可穿戴设备不仅仅是一种硬件设备，更是通过软件支持以及数据交互、云端交互来实现强大的功能。广义穿戴式智能设备包括功能全、尺寸大、可不依赖智能手机实现完整或者部分的功能，例如：智能手表或智能眼镜等，以及只专注于某一类应用功能，需要和其它设备如智能手机配合使用，如各类进行体征监测的智能手环、智能首饰等。
在本申请实施例中，网络设备可以是用于与移动设备通信的设备，网络设备可以是WLAN中的接入点(Access Point，AP)，GSM或CDMA中的基站(Base Transceiver Station，BTS)，也可以是WCDMA中的基站(NodeB，NB)，还可以是LTE中的演进型基站(Evolutional Node B，eNB或eNodeB)，或者中继站或接入点，或者车载设备、可穿戴设备以及NR网络中的网络设备或者基站(gNB)或者未来演进的PLMN网络中的网络设备或者NTN网络中的网络设备等。
作为示例而非限定，在本申请实施例中，网络设备可以具有移动特性，例如网络设备可以为移动的设备。可选地，网络设备可以为卫星、气球站。例如，卫星可以为低地球轨道(low earth orbit，LEO)卫星、中地球轨道(medium earth orbit，MEO)卫星、地球同步轨道(geostationary earth orbit，GEO)卫星、高椭圆轨道(High Elliptical Orbit，HEO)卫星等。可选地，网络设备还可以为设置在陆地、水域等位置的基站。
在本申请实施例中，网络设备可以为小区提供服务，终端设备通过该小区使用的传输资源(例如，频域资源，或者说，频谱资源)与网络设备进行通信，该小区可以是网络设备(例如基站)对应的小区，小区可以属于宏基站，也可以属于小小区(Small cell)对应的基站，这里的小小区可以包括：城市小区(Metro cell)、微小区(Micro cell)、微微小区(Pico cell)、毫微微小区(Femto cell)等，这些小小区具有覆盖范围小、发射功率低的特点，适用于提供高速率的数据传输服务。
示例性的，本申请实施例应用的通信系统100如图1所示。该通信系统100可以包括网络设备110，网络设备110可以是与终端设备120(或称为通信终端、终端)通信的设备。网络设备110可以为特定的地理区域提供通信覆盖，并且可以与位于该覆盖区域内的终端设备进行通信。
图1示例性地示出了一个网络设备和两个终端设备，可选地，该通信系统100可以包括多个网络设备并且每个网络设备的覆盖范围内可以包括其它数量的终端设备，本申请实施例对此不做限定。
可选地，该通信系统100还可以包括网络控制器、移动管理实体等其他网络实体，本申请实施例对此不作限定。
应理解，本申请实施例中网络/系统中具有通信功能的设备可称为通信设备。以图1示出的通信系统100为例，通信设备可包括具有通信功能的网络设备110和终端设备120，网络设备110和终端设备120可以为上文所述的具体设备，此处不再赘述；通信设备还可包括通信系统100中的其他设备，例如网络控制器、移动管理实体等其他网络实体，本申请实施例中对此不做限定。
应理解，本文中术语“系统”和“网络”在本文中常被可互换使用。本文中术语“和/或”，仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。另外，本文中字符“/”，一般表示前后关联对象是一种“或”的关系。
应理解，在本申请的实施例中提到的“指示”可以是直接指示，也可以是间接指示，还可以是表示具有关联关系。举例说明，A指示B，可以表示A直接指示B，例如B可以通过A获取；也可以表示A间接指示B，例如A指示C，B可以通过C获取；还可以表示A和B之间具有关联关系。
在本申请实施例的描述中，术语“对应”可表示两者之间具有直接对应或间接对应的关系，也可以表示两者之间具有关联关系，也可以是指示与被指示、配置与被配置等关系。
在NR系统中，终端设备可以采用模拟波束来传输上行数据和上行控制信息。终端设备可以基于探测参考信号(Sounding Reference Signal，SRS)信号来进行上行波束管理，从而确定上行传输所用的模拟波束。具体的，网络设备可以给终端设备配置SRS资源集合，基于终端设备在SRS资源集合中传输的SRS，选择出接收质量最好的一个SRS资源，并将对应的SRS资源指示(SRS resource indicator，SRI)通知给终端设备。终端设备接收到SRI后，将SRI指示的SRS资源所用的模拟波束确定为传输物理上行共享信道(Physical Uplink Shared Channel，PUSCH)所用的模拟波束。对于DCI调度的PUSCH，所述SRI通过DCI中的SRI指示域来指示；对于无线资源控制(Radio Resource Control，RRC)调度的PUSCH，所述SRI通过相应的调度信令通知。如果用于调度PUSCH的DCI为DCI格式0_0，则DCI中不包含SRI，终端设备将PUSCH所在载波的激活带宽部分(Band Width Part，BWP)上配置了空间相关信息的物理上行控制信道(Physical Uplink Control Channel，PUCCH)中资源标识(Identity，ID)最低的PUCCH资源上的发送波束，作为所述PUSCH的发送波束，同时，终端设备将所述PUCCH的路损测量参考信号，作为所述PUSCH的路损测量参考信号。如果所述DCI格式0_0调度的PUSCH所在载波上的激活BWP上没有配置PUCCH资源，或者所述PUSCH所在载波上的激活BWP上配置的PUCCH资源没有配置空间相关信息，则终端设备可以根据该载波上激活的下行BWP中ID最低的CORESET所用的准共址(Quasi-co-located，QCL)假设(QCL类型D)，来得到所述PUSCH的发送波束和路损测量参考信号。例如，可以将所述QCL假设中包含的下行参考信号的接收波束，作为所述PUSCH的发送波束，并将所述下行参考信号作为所述PUSCH的路损测量参考信号。
对于PUCCH，也采用类似的方法来指示所用的波束。具体的，对于每个PUCCH资源，在RRC信令中配置多个PUCCH空间相关信息(PUCCH-spatialrelationinfo)，再通过媒体接入控制(Media Access Control，MAC)层信令从中指示当前所用的PUCCH-spatialrelationinfo。其中，每个PUCCH-spatialrelationinfo中包含一个用于确定PUCCH的发送波束的参考信号，可以是SRS或信道状态信息参考信号(Channel State Information Reference Signal，CSI-RS)或同步信号块(Synchronization Signal Block，SSB)。PUCCH-spatialrelationinfo中还可以包含对应PUCCH的功率控制参数。对于每个SRS资源，也可以通过RRC信令配置对应的SRS空间相关信息(SRS-spatialrelationinfo)，其中包含一个用于确定SRS的发送波束的参考信号。如果网络侧没有配置PUCCH-spatialrelationinfo，则终端设备可以采用与PUSCH类似的方法，根据PUCCH所 在的载波上激活的下行BWP中ID最低的控制资源集(Control Resource Set，CORESET)所用的QCL假设(QCL类型D)，来得到所述PUCCH的发送波束。例如，可以将所述QCL假设中包含的下行参考信号的接收波束，作为所述PUCCH的发送波束。
在NR系统中，网络设备可以为每个下行信号或下行信道配置相应的传输配置指示(Transmission Configuration Indicator，TCI)状态，指示目标下行信号或目标下行信道对应的QCL参考信号，从而终端基于该参考信号进行目标下行信号或目标下行信道的接收。
其中，一个TCI状态可以包含如下配置：
TCI状态ID，用于标识一个TCI状态；
QCL信息1；
QCL信息2。
其中，一个QCL信息又包含如下信息：
QCL类型(type)配置，可以是QCL type A，QCL type B，QCL type C，QCL type D中的一个；
QCL参考信号配置，包括参考信号所在的小区ID，BWP ID以及参考信号的标识(可以是CSI-RS资源ID或SSB索引)。
其中，QCL信息1和QCL信息2中的至少一个QCL信息的QCL类型必须为typeA，typeB，typeC中的一个，另一个QCL信息(如果配置)的QCL类型必须为QCL type D。
其中，不同QCL类型配置的定义如下：
'QCL-TypeA':{多普勒频移(Doppler shift),多普勒扩展(Doppler spread),平均时延(average delay)，延时扩展(delay spread)}；
'QCL-TypeB':{多普勒频移(Doppler shift),多普勒扩展(Doppler spread)}；
'QCL-TypeC':{多普勒频移(Doppler shift),平均时延(average delay)}；
'QCL-TypeD':{空间接收参数(Spatial Rx parameter)}。
如果网络设备通过TCI状态配置目标下行信道的QCL参考信号为参考SSB或参考CSI-RS资源，且QCL类型配置为typeA，typeB或typeC，则终端设备可以假设所述目标下行信道与所述参考SSB或参考CSI-RS资源的目标大尺度参数是相同的，从而采用相同的相应接收参数进行接收，所述目标大尺度参数通过QCL类型配置来确定。类似的，如果网络设备通过TCI状态配置目标下行信道的QCL参考信号为参考SSB或参考CSI-RS资源，且QCL类型配置为type D，则终端设备可以采用与接收所述参考SSB或参考CSI-RS资源相同的接收波束(即Spatial Rx parameter)，来接收所述目标下行信道。通常的，目标下行信道与其参考SSB或参考CSI-RS资源在网络侧由同一个TRP或者同一个天线面板(panel)或者相同的波束来发送。如果两个下行信号或下行信道的传输TRP或传输panel或发送波束不同，通常会配置不同的TCI状态。
对于下行控制信道，TCI状态可以通过RRC信令或者RRC信令+MAC信令的方式来指示。对于下行数据信道，可用的TCI状态集合通过RRC信令来指示，并通过MAC层信令来激活其中部分TCI状态，最后通过DCI中的TCI状态指示域从激活的TCI状态中指示一个或两个TCI状态，用于所述DCI调度的PDSCH。例如，如图2所示，网络设备通过RRC信令指示N个候选的TCI状态，并通过MAC信令激活K个TCI状态，最后通过DCI中的TCI状态指示域从激活的TCI状态中指示1个或2个使用的TCI状态。
为了满足物理下行共享信道(Physical Downlink Shared Channel，PDSCH)的传输时延和可靠性需求，版本16(Release 16，Rel-16)中引入了基于多发送接收点(Transmission/Reception Point，TRP)的PDSCH分集传输，通过频分多路复用(Frequency-division multiplexing，FDM)、时分复用模式(Testing Data Management/Technical Data Manage，TDM)或空分复用(Space Division Multiplexing，SDM)的方式接收不同TRP传输的数据。类似的机制也可以用于PUCCH传输，以提高PUCCH的传输可靠性。具体的，终端设备可以在不同的时隙中使用相同的PUCCH资源 重复传输同一个PUCCH(携带相同的上行控制信息(Uplink Control Information，UCI))。由于不同时隙中的PUCCH是发给不同的TRP的，所使用的发送波束和功率控制参数(如路损测量参考信号)也是独立配置的，如图3所示。例如，可以给一个PUCCH资源指示N个空间相关信息PUCCH-spatialrelationinfo或者N个TCI状态，分别用于不同时隙中的PUCCH重复传输，PUCCH的发送波束和功率控制参数可以从所述N个空间相关信息PUCCH-spatialrelationinfo或者N个TCI状态中得到。其中，N为协作TRP的数量，对于两个TRP的情况，N＝2，如图4所示。
在本申请实施例中，PUSCH的发送功率可以通过如下公式1计算：
Figure PCTCN2020101907-appb-000001
其中，在公式1中，P CMAX,f,c(i)是终端当前载波上的最大发送功率，i是一次PUSCH传输的索引，j是开环功率控制参数索引(包括目标功率P O_PUSCH,b,f,c(j)和路损因子α b,f,c(j))；q d是用于进行路损测量的参考信号的索引，用于得到路损值PL b,f,c(q d)，也是一个开环功率控制参数；f b,f,c(i,l)是闭环功控调整状态，其中l是闭环功控调整状态的索引。其中，终端根据网络侧发送的传输功率控制(Transmission Power Control，TPC)命令域来确定闭环功率调整因子，所述TPC命令域可以通过终端搜索空间中用于调度所述PUSCH的DCI来承载，也可以通过公共搜索空间中用于携带组TPC命令域的DCI格式2_2来承载。不同闭环功控调整状态索引对应的闭环功控调整状态是独立计算的，从而可以得到不同的PUSCH发送功率。
由于在引入了基于多TRP的PUCCH分集传输之后，终端设备可以在不同的时隙中使用同一PUCCH资源和不同的传输参数(如发送波束和功率控制参数)重复传输同一个PUCCH。如果PUSCH所在载波的激活BWP上的PUCCH资源ID最低的PUCCH资源被配置了多个空间相关信息(如多个波束)，如何确定DCI格式0_0调度的PUSCH的波束和路损测量参考信号是个亟待解决的问题。
基于上述问题，本申请提出了一种用于确定上行传输参数的方案，如果PUSCH所在的载波上激活的上行BWP中的PUCCH资源ID最低的PUCCH资源被配置了多组传输参数(发送波束和/或路损测量参考信号)，终端设备可以基于本申请方案确定PUSCH的传输参数(发送波束和/或路损测量参考信号)。具体地，终端设备可以选择未配置多个空间相关信息的其他PUCCH资源来得到PUSCH的传输参数，或者将发给同一TRP的PUCCH的传输参数作为PUSCH的传输参数，或者从下行信号的QCL假设得到PUSCH的传输参数，从而不需要信令就可以解决无法确定PUSCH传输参数的问题。
以下通过具体实施例详述本申请的技术方案。
图5是根据本申请实施例的用于确定上行传输参数的方法200的示意性流程图，如图5所示，该方法200可以包括如下内容中的至少部分内容：
S210，终端设备根据PUSCH所在的载波上激活的上行BWP中的PUCCH资源上的传输参数，确定该PUSCH的传输参数，其中，该PUSCH为采用第一DCI格式调度的PUSCH，该传输参数为发送波束和/或该传输参数为路损测量所用的参考信号。
可选地，该第一DCI格式为DCI格式0_0。
需要说明的是，DCI格式0_0用于PUSCH调度，并且DCI格式0_0中不包括SRS资源指示(SRI)。而对于除DCI格式0_0之外的一些其他的DCI格式调度的PUSCH，网络设备可以给终端设备配置SRS资源集合，基于终端设备在SRS资源集合中传输的SRS，选择出接收质量最好的一个SRS资源，并将对应的SRS资源指示(SRI)通知给终端设备。终端设备接收到SRI后，将SRI指示的SRS资源所用的模拟波束确定为传输PUSCH所用的模拟波束。
也就是说，对于DCI格式0_0调度PUSCH，由于DCI格式0_0中不包括SRS资源指示(SRI)，终端设备无法基于SRI指示的SRS资源所用的模拟波束确定传输PUSCH所用的模拟波束。
需要说明的是，在本申请实施例中，PUCCH资源的发送波束和路损测量所用的参考信号可以通过空间相关信息(Spatial relation information)来得到(例如，PUCCH-spatialrelationinfo)，也可以通过TCI状态来得到。因此，本申请实施例中PUCCH资源的传输参数可以是指PUCCH资源的空间相关信息或TCI状态。
在本申请实施例中，发送波束也可以称为空间域传输滤波器(Spatial domain transmission filter或者Spatial domain filter for transmission)或者空间关系(Spatial relation)或者空间配置(spatial setting)。接收波束也可以称为空间域接收滤波器(Spatial domain reception filter或者Spatial domain filter for reception)或者空间接收参数(Spatial Rx parameter)。
在本申请实施例中，路损测量所用的参考信号可以为用于测量路损的下行参考信号，例如CSI-RS或SSB，终端设备可以根据测量得到的路损值来计算PUSCH的发送功率，例如基于上述公式1计算PUSCH的发送功率。
可选地，在本申请实施例中，该上行BWP中可以配置多个PUCCH资源，每个PUCCH资源可以独立配置资源标识和PUCCH的传输参数(如通过PUCCH空间相关信息配置)。例如，有的PUCCH资源上没有配置发送波束(例如没有配置PUCCH空间相关信息)，有的PUCCH资源只配置单个发送波束(例如只配置一个PUCCH空间相关信息)，有的PUCCH资源配置多个发送波束(例如配置多个PUCCH空间相关信息，分别用于不同重复(Repetition)的传输)。也就是说，在本申请实施例中，该上行BWP中可以使用基于多TRP的PUCCH分集传输。
可选地，在本申请实施例中，S210具体可以通过如下示例1至示例3中的一种或者多种方案，确定该PUSCH的传输参数。
示例1，该终端设备将PUSCH所在的载波上激活的上行BWP中仅配置有一组传输参数的PUCCH资源中资源标识最低的PUCCH资源上的传输参数，确定为该PUSCH的传输参数。
在示例1中，例如，如图6所示，PUSCH所在的载波上激活的上行BWP中配置了5个PUCCH资源，分别记为PUCCH资源0、PUCCH资源1、PUCCH资源2、PUCCH资源3和PUCCH资源4，该PUSCH由DCI格式0_0调度。其中，PUCCH资源0上配置有2组传输参数(如PUCCH空间相关信息0和PUCCH空间相关信息1)，PUCCH资源1上配置有1组传输参数(如PUCCH空间相关信息2)，PUCCH资源2上配置有1组传输参数(如PUCCH空间相关信息3)，PUCCH资源3上没有配置传输参数，即PUCCH资源3无PUCCH空间相关信息，PUCCH资源4上配置有2组传输参数(如PUCCH空间相关信息4和PUCCH空间相关信息5)。具体地，终端设备将仅配置有1组传输参数的PUCCH资源包括PUCCH资源1和PUCCH资源2，其中，PUCCH资源1和PUCCH资源2中资源标识最低的PUCCH资源为PUCCH资源1，终端设备可以将PUCCH资源1的传输参数，作为该PUSCH的传输参数。例如，终端设备将PUCCH资源1的发送波束，作为该PUSCH的发送波束。同时，终端设备将PUCCH资源1的路损测量所用的参考信号，作为该PUSCH的路损测量所用的参考信号。
因此，在示例1中，在PUSCH所在的载波上激活的上行BWP中使用基于多TRP的PUCCH分集传输的情况下，终端设备可以将PUSCH所在的载波上激活的上行BWP中仅配置有一组传输参数的PUCCH资源中资源标识最低的PUCCH资源上的传输参数，确定为该PUSCH的传输参数，从而避免了用于得到PUSCH传输参数的PUCCH资源有多组传输参数的问题。
示例2，若PUSCH所在的载波上激活的上行BWP中资源标识最低的PUCCH资源 配置有多组传输参数，该终端设备将该多组传输参数中的目标传输参数，确定为该PUSCH的传输参数。
可选地，在示例2中，该目标传输参数为该多组传输参数中预先约定好的一组传输参数，或者，该目标传输参数为该多组传输参数中预配置的一组传输参数，或者，该目标传输参数为该多组传输参数中网络设备指示的一组传输参数。
例如，该上行BWP中资源标识最低的PUCCH资源配置有两组传输参数，分别用于奇数次的PUCCH重复传输和偶数次的PUCCH重复传输。此种情况下，终端设备可以将两组传输参数中的第一组传输参数，确定为该PUSCH的传输参数。
又例如，此种情况下，该上行BWP中资源标识最低的PUCCH资源配置有两个PUCCH空间相关信息，分别用于奇数次的PUCCH重复传输和偶数次的PUCCH重复传输。终端设备可以将第一个PUCCH空间相关信息所指示的发送波束，作为该PUSCH的发送波束；以及将第一个PUCCH空间相关信息所指示的路损测量参考信号，作为该PUSCH的路损测量参考信号。或者，终端设备可以将第二个PUCCH空间相关信息所指示的发送波束，作为该PUSCH的发送波束；以及将第二个PUCCH空间相关信息所指示的路损测量参考信号，作为该PUSCH的路损测量参考信号。
可选地，在示例2中，该目标传输参数为调度该PUSCH的DCI所在的CORESET的CORESET组索引(CORESETPoolIndex)从该多组传输参数中确定的。
进一步的，在示例2中，该目标传输参数为基于该CORESET组索引和第一对应关系从该多组传输参数中确定的，其中，该第一对应关系为CORESET组索引的取值与传输参数组标识的对应关系。
可选地，该CORESET组索引可以占用N比特，N为大于或者等于1的整数。例如，在N＝1的情况下，该CORESET组索引取值可以是0和1。又例如，在N＝2的情况下，该CORESET组索引取值可以是00、01、10和11。再例如，在N＝3的情况下，该CORESET组索引取值可以是000、001、010、011、100、101、110和111。
可选地，在N＝1的情况下，若该CORESET组索引取值为0，该目标传输参数为该多组传输参数中的第一组传输参数；若该CORESET组索引取值为1，该目标传输参数为该多组传输参数中的第二组传输参数。
可选地，在N＝2的情况下，若该CORESET组索引取值为00，该目标传输参数为该多组传输参数中的第一组传输参数；若该CORESET组索引取值为01，该目标传输参数为该多组传输参数中的第二组传输参数。
例如，网络设备可以预先为每个CORESET配置一个CORESET组索引(CORESETPoolIndex)，不同CORESET可以采用相同的CORESET组索引，也可以采用不同的CORESET组索引。特别的，在该CORESET组索引占用1比特的情况下，如果一个CORESET没有配置CORESET组索引，终端设备可以假设该CORESET的CORESET组索引取值为0。终端设备在第一CORESET中检测到了携带调度该PUSCH的DCI的PDCCH，则终端设备根据该第一CORESET的CORESET组索引，从该多组传输参数中确定目标传输参数。例如，在该CORESET组索引占用1比特的情况下，假设该PUCCH资源被配置了两组传输参数，如果该第一CORESET的CORESET组索引取值为0或者第一CORESET没有配置CORESET组索引，则采用该两组传输参数中的第一组传输参数作为该PUSCH的传输参数；如果该第一CORESET的CORESET组索引取值为1，则采用该两组传输参数中的第二组传输参数作为该PUSCH的传输参数。
可选地，该方法也可以用于PUCCH资源被配置了多于两组传输参数的情况。
因此，在示例2中，在PUSCH所在的载波上激活的上行BWP中使用基于多TRP的PUCCH分集传输的情况下，终端设备可以将分集传输的PUCCH中与PUSCH接收TRP相同的PUCCH的传输参数作为PUSCH的传输参数，从而保证发给同一个TRP的不同信道采用相同的传输参数。
示例3，该终端设备根据PUSCH所在的载波上激活的上行BWP中资源标识最低的PUCCH资源配置的传输参数的数量，确定该PUSCH的传输参数。
例如，PUSCH所在的载波上激活的上行BWP中配置了3个PUCCH资源，分别记为PUCCH资源0、PUCCH资源1和PUCCH资源2，此种情况下，终端设备可以根据PUCCH资源0配置的传输参数的数量，确定该PUSCH的传输参数。
可选地，在示例3中，若该传输参数的数量等于1，该终端设备将该上行BWP中资源标识最低的PUCCH资源配置的传输参数，确定为该PUSCH的传输参数；
若该传输参数的数量大于1，该终端设备从目标CORESET所用的QCL假设中得到该PUSCH的传输参数，其中，该目标CORESET为该PUSCH所在的载波上激活的下行BWP上配置的CORESET中，CORESET标识最低的CORESET。
例如，PUSCH所在的载波上激活的下行BWP上配置了3个CORESET，分别为CORESET 0、CORESET 1和CORESET 2，则CORESET标识最低的CORESET为CORESET 0，即目标CORESET为CORESET 0。
需要说明的是，网络设备可以预先为每个CORESET配置一个CORESET标识，不同CORESET的CORESET标识是不同的，用于标识此CORESET。例如，传输参数为路损测量所用的参考信号时，终端设备将目标CORESET所用的QCL假设(QCL类型为QCL type-D)对应的下行参考信号，作为所述PUSCH的路损测量所用的参考信号。又例如，传输参数为发送波束时，终端设备将目标CORESET所用的QCL假设(QCL类型为QCL type-D)对应的下行参考信号的接收波束，作为所述PUSCH的发送波束。
可选地，在示例3中，若该传输参数的数量等于1，该终端设备将该上行BWP中资源标识最低的PUCCH资源配置的传输参数，确定为该PUSCH的传输参数；
若该传输参数的数量大于1，该终端设备从目标CORESET所用的QCL假设中得到该PUSCH的传输参数，其中，该目标CORESET为调度该PUSCH的DCI所在的CORESET。
例如，终端设备在CORESET 1中检测到了携带调度该PUSCH的DCI的PDCCH，则从CORESET 1所用的QCL假设中，得到所述PUSCH的传输参数。例如，当传输参数为路损测量所用的参考信号时，终端设备将CORESET 1所用的QCL假设(QCL类型为QCL type-D)对应的下行参考信号，作为所述PUSCH的路损测量所用的参考信号。又例如，当传输参数为发送波束时，终端设备将CORESET 1所用的QCL假设(QCL类型为QCL type-D)对应的下行参考信号的接收波束，作为所述PUSCH的发送波束。
可选地，在示例3中，若该传输参数的数量等于1，则该终端设备将该上行BWP中资源标识最低的PUCCH资源配置的传输参数，确定为该PUSCH的传输参数；
若该传输参数的数量大于1，该终端设备从目标TCI状态中得到该PUSCH的传输参数，其中，该目标TCI状态为该PUSCH所在的载波上激活的下行BWP中所激活的用于PDSCH传输的TCI状态中TCI状态标识最低的TCI状态。
例如，PUSCH所在的载波上激活的下行BWP上配置了5个TCI状态，分别为TCI状态0、TCI状态1、TCI状态2、TCI状态3和TCI状态4，其中，处于激活状态的的用于PDSCH传输的TCI状态包括：TCI状态2、TCI状态3和TCI状态4。则PUSCH所在的载波上激活的下行BWP中所激活的用于PDSCH传输的TCI状态中TCI状态标识最低的TCI状态标识为TCI状态2，即目标TCI状态为TCI状态2。
需要说明的是，网络设备预先通过媒体接入控制控制元素(Media Access Control Control Element，MAC CE)激活用于PDSCH传输的TCI状态。
例如，当传输参数为路损测量所用的参考信号时，终端设备将PUSCH所在的载波上激活的下行BWP中所激活的用于PDSCH传输的TCI状态中，TCI状态标识最低的TCI状态中包含的下行参考信号(QCL类型为QCL type-D)，作为PUSCH的路损测量所用的参考信号。又例如，在传输参数为发送波束时，终端设备将PUSCH所在的载波上激活 的下行BWP中所激活的用于PDSCH传输的TCI状态中，TCI状态标识最低的TCI状态中包含的下行参考信号(QCL类型为QCL type-D)的接收波束，作为PUSCH的发送波束；或者，终端设备将PUSCH所在的载波上激活的下行BWP中所激活的用于PDSCH传输的TCI状态中，TCI状态标识最低的TCI状态中包含的上行参考信号的发送波束，作为PUSCH的发送波束。
因此，在示例3中，终端设备可以根据PUSCH所在的载波上激活的上行BWP中资源标识最低的PUCCH资源配置的传输参数的数量，即根据该PUCCH资源是否进行的基于多TRP的PUCCH分集传输，采用相应不同的方法来确定PUSCH的传输参数，从而同时支持单TRP的PUCCH传输和多TRP协作的PUCCH分集传输两种场景。
可选的，在本申请实施例中，配置不同CORESET组索引的CORESET可以来自不同的TRP，例如，配置CORESET组索引为0的CORESET传输自TRP 0，配置CORESET组索引为1的CORESET传输自TRP 1。
可选地，在一些实施例中，该终端设备根据所确定的该PUSCH的传输参数，传输该PUSCH。
例如，在确定该PUSCH的发送波束之后，终端设备可以采用该发送波束来发送该PUSCH。
例如，在确定该PUSCH的路损测量所用的参考信号之后，终端设备可以采用该参考信号进行路损测量，并根据测量得到的路损值来计算该PUSCH的发送功率。
因此，本申请实施例中，在PUSCH所在的载波上激活的上行BWP中资源标识最低的PUCCH资源被配置了多个空间相关信息的情况下，终端设备可以确定DCI格式0_0调度的PUSCH的传输参数。或者，在PUSCH所在的载波上激活的上行BWP中使用基于多TRP的PUCCH分集传输的情况下，终端设备可以确定DCI格式0_0调度的PUSCH的传输参数。进一步的，终端设备可以选择未配置多个空间相关信息的其他PUCCH资源来得到PUSCH的传输参数，或者将发给同一TRP的PUCCH的传输参数作为PUSCH的传输参数，或者从下行信号的QCL假设得到PUSCH的传输参数，从而不需要信令就可以解决无法确定PUSCH传输参数的问题。
上文结合图5至图6，详细描述了本申请的方法实施例，下文结合图7至图10，详细描述本申请的装置实施例，应理解，装置实施例与方法实施例相互对应，类似的描述可以参照方法实施例。
图7示出了根据本申请实施例的终端设备300的示意性框图。如图7所示，该终端设备300包括：
处理单元310，用于根据PUSCH所在的载波上激活的上行BWP中的PUCCH资源上的传输参数，确定该PUSCH的传输参数，其中，该PUSCH为采用第一DCI格式调度的PUSCH，该传输参数为发送波束和/或该传输参数为路损测量所用的参考信号。
可选地，该处理单元310具体用于：
将该上行BWP中仅配置有一组传输参数的PUCCH资源中资源标识最低的PUCCH资源上的传输参数，确定为该PUSCH的传输参数。
可选地，该处理单元310具体用于：
若该上行BWP中资源标识最低的PUCCH资源配置有多组传输参数，将该多组传输参数中的目标传输参数，确定为该PUSCH的传输参数。
可选地，该目标传输参数为该多组传输参数中预先约定好的一组传输参数，或者，该目标传输参数为该多组传输参数中预配置的一组传输参数，或者，该目标传输参数为该多组传输参数中网络设备指示的一组传输参数。
可选地，该目标传输参数为根据调度该PUSCH的DCI所在的CORESET的CORESET组索引从该多组传输参数中确定的。
可选地，该目标传输参数为根据该CORESET组索引和第一对应关系从该多组传输 参数中确定的，其中，该第一对应关系为CORESET组索引的取值与传输参数组标识的对应关系。
可选地，若该CORESET组索引取值为0，该目标传输参数为该多组传输参数中的第一组传输参数；若该CORESET组索引取值为1，该目标传输参数为该多组传输参数中的第二组传输参数。
可选地，该处理单元310具体用于：
根据该上行BWP中资源标识最低的PUCCH资源配置的传输参数的数量，确定该PUSCH的传输参数。
可选地，该处理单元310具体用于：
若该传输参数的数量等于1，将该上行BWP中资源标识最低的PUCCH资源配置的传输参数，确定为该PUSCH的传输参数；
若该传输参数的数量大于1，从目标CORESET所用的准共址QCL假设中得到该PUSCH的传输参数，其中，该目标CORESET为该PUSCH所在的载波上激活的下行BWP上配置的CORESET中，CORESET标识最低的CORESET，或者，该目标CORESET为调度该PUSCH的DCI所在的CORESET。
可选地，该处理单元310具体用于：
若该传输参数的数量等于1，将该上行BWP中资源标识最低的PUCCH资源配置的传输参数，确定为该PUSCH的传输参数；
若该传输参数的数量大于1，从目标传输配置指示TCI状态中得到该PUSCH的传输参数，其中，该目标TCI状态为该PUSCH所在的载波上激活的下行BWP中所激活的用于物理下行共享信道PDSCH传输的TCI状态中，TCI状态标识最低的TCI状态。
可选地，该终端设备300还包括：
通信单元320，用于根据所确定的该PUSCH的传输参数，传输该PUSCH。
可选地，该第一DCI格式为DCI格式0_0。
可选地，在一些实施例中，上述通信单元可以是通信接口或收发器，或者是通信芯片或者片上系统的输入输出接口。上述处理单元可以是一个或多个处理器。
应理解，根据本申请实施例的终端设备300可对应于本申请方法实施例中的终端设备，并且终端设备300中的各个单元的上述和其它操作和/或功能分别为了实现图5所示方法200中终端设备的相应流程，为了简洁，在此不再赘述。
图8是本申请实施例提供的一种通信设备400示意性结构图。图8所示的通信设备400包括处理器410，处理器410可以从存储器中调用并运行计算机程序，以实现本申请实施例中的方法。
可选地，如图8所示，通信设备400还可以包括存储器420。其中，处理器410可以从存储器420中调用并运行计算机程序，以实现本申请实施例中的方法。
其中，存储器420可以是独立于处理器410的一个单独的器件，也可以集成在处理器410中。
可选地，如图8所示，通信设备400还可以包括收发器430，处理器410可以控制该收发器430与其他设备进行通信，具体地，可以向其他设备发送信息或数据，或接收其他设备发送的信息或数据。
其中，收发器430可以包括发射机和接收机。收发器430还可以进一步包括天线，天线的数量可以为一个或多个。
可选地，该通信设备400具体可为本申请实施例的网络设备，并且该通信设备400可以实现本申请实施例的各个方法中由网络设备实现的相应流程，为了简洁，在此不再赘述。
可选地，该通信设备400具体可为本申请实施例的移动终端/终端设备，并且该通信设备400可以实现本申请实施例的各个方法中由移动终端/终端设备实现的相应流程，为 了简洁，在此不再赘述。
图9是本申请实施例的装置的示意性结构图。图9所示的装置500包括处理器510，处理器510可以从存储器中调用并运行计算机程序，以实现本申请实施例中的方法。
可选地，如图9所示，装置500还可以包括存储器520。其中，处理器510可以从存储器520中调用并运行计算机程序，以实现本申请实施例中的方法。
其中，存储器520可以是独立于处理器510的一个单独的器件，也可以集成在处理器510中。
可选地，该装置500还可以包括输入接口530。其中，处理器510可以控制该输入接口530与其他设备或芯片进行通信，具体地，可以获取其他设备或芯片发送的信息或数据。
可选地，该装置500还可以包括输出接口540。其中，处理器510可以控制该输出接口540与其他设备或芯片进行通信，具体地，可以向其他设备或芯片输出信息或数据。
可选地，该装置可应用于本申请实施例中的网络设备，并且该装置可以实现本申请实施例的各个方法中由网络设备实现的相应流程，为了简洁，在此不再赘述。
可选地，该装置可应用于本申请实施例中的移动终端/终端设备，并且该装置可以实现本申请实施例的各个方法中由移动终端/终端设备实现的相应流程，为了简洁，在此不再赘述。
可选地，本申请实施例提到的装置也可以是芯片。例如可以是系统级芯片，系统芯片，芯片系统或片上系统芯片等。
图10是本申请实施例提供的一种通信系统600的示意性框图。如图10所示，该通信系统600包括终端设备610和网络设备620。
其中，该终端设备610可以用于实现上述方法中由终端设备实现的相应的功能，以及该网络设备620可以用于实现上述方法中由网络设备实现的相应的功能为了简洁，在此不再赘述。
应理解，本申请实施例的处理器可能是一种集成电路芯片，具有信号的处理能力。在实现过程中，上述方法实施例的各步骤可以通过处理器中的硬件的集成逻辑电路或者软件形式的指令完成。上述的处理器可以是通用处理器、数字信号处理器(Digital Signal Processor，DSP)、专用集成电路(Application Specific Integrated Circuit，ASIC)、现成可编程门阵列(Field Programmable Gate Array，FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件。可以实现或者执行本申请实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。结合本申请实施例所公开的方法的步骤可以直接体现为硬件译码处理器执行完成，或者用译码处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器，闪存、只读存储器，可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器，处理器读取存储器中的信息，结合其硬件完成上述方法的步骤。
可以理解，本申请实施例中的存储器可以是易失性存储器或非易失性存储器，或可包括易失性和非易失性存储器两者。其中，非易失性存储器可以是只读存储器(Read-Only Memory，ROM)、可编程只读存储器(Programmable ROM，PROM)、可擦除可编程只读存储器(Erasable PROM，EPROM)、电可擦除可编程只读存储器(Electrically EPROM，EEPROM)或闪存。易失性存储器可以是随机存取存储器(Random Access Memory，RAM)，其用作外部高速缓存。通过示例性但不是限制性说明，许多形式的RAM可用，例如静态随机存取存储器(Static RAM，SRAM)、动态随机存取存储器(Dynamic RAM，DRAM)、同步动态随机存取存储器(Synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(Double Data Rate SDRAM，DDR SDRAM)、增强型同步动态随机存取存储器(Enhanced SDRAM，ESDRAM)、同步连接动态随机 存取存储器(Synchlink DRAM，SLDRAM)和直接内存总线随机存取存储器(Direct Rambus RAM，DR RAM)。应注意，本文描述的系统和方法的存储器旨在包括但不限于这些和任意其它适合类型的存储器。
应理解，上述存储器为示例性但不是限制性说明，例如，本申请实施例中的存储器还可以是静态随机存取存储器(static RAM，SRAM)、动态随机存取存储器(dynamic RAM，DRAM)、同步动态随机存取存储器(synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(double data rate SDRAM，DDR SDRAM)、增强型同步动态随机存取存储器(enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(synch link DRAM，SLDRAM)以及直接内存总线随机存取存储器(Direct Rambus RAM，DR RAM)等等。也就是说，本申请实施例中的存储器旨在包括但不限于这些和任意其它适合类型的存储器。
本申请实施例还提供了一种计算机可读存储介质，用于存储计算机程序。
可选地，该计算机可读存储介质可应用于本申请实施例中的移动终端/终端设备，并且该计算机程序使得计算机执行本申请实施例的各个方法中由移动终端/终端设备实现的相应流程，为了简洁，在此不再赘述。
可选地，该计算机程序产品可应用于本申请实施例中的移动终端/终端设备，并且该计算机程序指令使得计算机执行本申请实施例的各个方法中由移动终端/终端设备实现的相应流程，为了简洁，在此不再赘述。
本申请实施例还提供了一种计算机程序。
可选地，该计算机程序可应用于本申请实施例中的移动终端/终端设备，当该计算机程序在计算机上运行时，使得计算机执行本申请实施例的各个方法中由移动终端/终端设备实现的相应流程，为了简洁，在此不再赘述。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。针对这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例所述方法的全部或部 分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(Read-Only Memory，ROM)、随机存取存储器(Random Access Memory，RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应所述以权利要求的保护范围为准。

Claims (29)

  1. 一种用于确定上行传输参数的方法，其特征在于，包括：
    终端设备根据物理上行共享信道PUSCH所在的载波上激活的上行带宽部分BWP中的物理上行控制信道PUCCH资源上的传输参数，确定所述PUSCH的传输参数，其中，所述PUSCH为采用第一下行控制信息DCI格式调度的PUSCH，所述传输参数为发送波束和/或所述传输参数为路损测量所用的参考信号。
  2. 如权利要求1所述的方法，其特征在于，所述终端设备根据PUSCH所在的载波上激活的上行BWP中的PUCCH资源上的传输参数，确定所述PUSCH的传输参数，包括：
    所述终端设备将所述上行BWP中仅配置有一组传输参数的PUCCH资源中资源标识最低的PUCCH资源上的传输参数，确定为所述PUSCH的传输参数。
  3. 如权利要求1所述的方法，其特征在于，所述终端设备根据PUSCH所在的载波上激活的上行BWP中的PUCCH资源上的传输参数，确定所述PUSCH的传输参数，包括：
    若所述上行BWP中资源标识最低的PUCCH资源配置有多组传输参数，所述终端设备将所述多组传输参数中的目标传输参数，确定为所述PUSCH的传输参数。
  4. 如权利要求3所述的方法，其特征在于，所述目标传输参数为所述多组传输参数中预先约定好的一组传输参数，或者，所述目标传输参数为所述多组传输参数中预配置的一组传输参数，或者，所述目标传输参数为所述多组传输参数中网络设备指示的一组传输参数。
  5. 如权利要求3所述的方法，其特征在于，所述目标传输参数为根据调度所述PUSCH的DCI所在的控制资源集CORESET的CORESET组索引从所述多组传输参数中确定的。
  6. 如权利要求5所述的方法，其特征在于，所述目标传输参数为根据所述CORESET组索引和第一对应关系从所述多组传输参数中确定的，其中，所述第一对应关系为CORESET组索引的取值与传输参数组标识的对应关系。
  7. 如权利要求5或6所述的方法，其特征在于，
    若所述CORESET组索引取值为0，所述目标传输参数为所述多组传输参数中的第一组传输参数；
    若所述CORESET组索引取值为1，所述目标传输参数为所述多组传输参数中的第二组传输参数。
  8. 如权利要求1所述的方法，其特征在于，所述终端设备根据PUSCH所在的载波上激活的上行BWP中的PUCCH资源上的传输参数，确定所述PUSCH的传输参数，包括：
    所述终端设备根据所述上行BWP中资源标识最低的PUCCH资源配置的传输参数的数量，确定所述PUSCH的传输参数。
  9. 如权利要求8所述的方法，其特征在于，所述终端设备根据所述上行BWP中资源标识最低的PUCCH资源配置的传输参数的数量，确定所述PUSCH的传输参数，包括：
    若所述传输参数的数量等于1，所述终端设备将所述上行BWP中资源标识最低的PUCCH资源配置的传输参数，确定为所述PUSCH的传输参数；
    若所述传输参数的数量大于1，所述终端设备从目标CORESET所用的准共址QCL假设中得到所述PUSCH的传输参数，其中，所述目标CORESET为所述PUSCH所在的载波上激活的下行BWP上配置的CORESET中，CORESET标识最低的CORESET，或者，所述目标CORESET为调度所述PUSCH的DCI所在的CORESET。
  10. 如权利要求8所述的方法，其特征在于，所述终端设备根据所述上行BWP中PUCCH资源标识最低的PUCCH资源配置的传输参数的数量，确定所述PUSCH的传输参数，包括：
    若所述传输参数的数量等于1，则所述终端设备将所述上行BWP中资源标识最低的PUCCH资源配置的传输参数，确定为所述PUSCH的传输参数；
    若所述传输参数的数量大于1，所述终端设备从目标传输配置指示TCI状态中得到所述PUSCH的传输参数，其中，所述目标TCI状态为所述PUSCH所在的载波上激活的下行BWP中所激活的用于物理下行共享信道PDSCH传输的TCI状态中，TCI状态标识最低的TCI状态。
  11. 如权利要求1至10中任一项所述的方法，其特征在于，所述方法还包括：
    所述终端设备根据所确定的所述PUSCH的传输参数，传输所述PUSCH。
  12. 如权利要求1至11中任一项所述的方法，其特征在于，所述第一DCI格式为DCI格式0_0。
  13. 一种终端设备，其特征在于，包括：
    处理单元，用于根据物理上行共享信道PUSCH所在的载波上激活的上行带宽部分BWP中的物理上行控制信道PUCCH资源上的传输参数，确定所述PUSCH的传输参数，其中，所述PUSCH为采用第一下行控制信息DCI格式调度的PUSCH，所述传输参数为发送波束和/或所述传输参数为路损测量所用的参考信号。
  14. 如权利要求13所述的终端设备，其特征在于，所述处理单元具体用于：
    将所述上行BWP中仅配置有一组传输参数的PUCCH资源中资源标识最低的PUCCH资源上的传输参数，确定为所述PUSCH的传输参数。
  15. 如权利要求13所述的终端设备，其特征在于，所述处理单元具体用于：
    若所述上行BWP中资源标识最低的PUCCH资源配置有多组传输参数，将所述多组传输参数中的目标传输参数，确定为所述PUSCH的传输参数。
  16. 如权利要求15所述的终端设备，其特征在于，所述目标传输参数为所述多组传输参数中预先约定好的一组传输参数，或者，所述目标传输参数为所述多组传输参数中预配置的一组传输参数，或者，所述目标传输参数为所述多组传输参数中网络设备指示的一组传输参数。
  17. 如权利要求15所述的终端设备，其特征在于，所述目标传输参数为根据调度所述PUSCH的DCI所在的控制资源集CORESET的CORESET组索引从所述多组传输参数中确定的。
  18. 如权利要求17所述的终端设备，其特征在于，所述目标传输参数为根据所述CORESET组索引和第一对应关系从所述多组传输参数中确定的，其中，所述第一对应关系为CORESET组索引的取值与传输参数组标识的对应关系。
  19. 如权利要求17或18所述的终端设备，其特征在于，
    若所述CORESET组索引取值为0，所述目标传输参数为所述多组传输参数中的第一组传输参数；
    若所述CORESET组索引取值为1，所述目标传输参数为所述多组传输参数中的第二组传输参数。
  20. 如权利要求13所述的终端设备，其特征在于，所述处理单元具体用于：
    根据所述上行BWP中资源标识最低的PUCCH资源配置的传输参数的数量，确定所述PUSCH的传输参数。
  21. 如权利要求20所述的终端设备，其特征在于，所述处理单元具体用于：
    若所述传输参数的数量等于1，将所述上行BWP中资源标识最低的PUCCH资源配置的传输参数，确定为所述PUSCH的传输参数；
    若所述传输参数的数量大于1，从目标CORESET所用的准共址QCL假设中得到所述PUSCH的传输参数，其中，所述目标CORESET为所述PUSCH所在的载波上激活的下行BWP上配置的CORESET中，CORESET标识最低的CORESET，或者，所述目标CORESET为调度所述PUSCH的DCI所在的CORESET。
  22. 如权利要求20所述的终端设备，其特征在于，所述处理单元具体用于：
    若所述传输参数的数量等于1，将所述上行BWP中资源标识最低的PUCCH资源配置的传输参数，确定为所述PUSCH的传输参数；
    若所述传输参数的数量大于1，从目标传输配置指示TCI状态中得到所述PUSCH的传输参数，其中，所述目标TCI状态为所述PUSCH所在的载波上激活的下行BWP中所激活的用于物理下行共享信道PDSCH传输的TCI状态中，TCI状态标识最低的TCI状态。
  23. 如权利要求13至22中任一项所述的终端设备，其特征在于，所述终端设备还包括：
    通信单元，用于根据所确定的所述PUSCH的传输参数，传输所述PUSCH。
  24. 如权利要求13至23中任一项所述的终端设备，其特征在于，所述第一DCI格式为DCI格式0_0。
  25. 一种终端设备，其特征在于，包括：处理器和存储器，该存储器用于存储计算机程序，所述处理器用于调用并运行所述存储器中存储的计算机程序，执行如权利要求1至12中任一项所述的方法。
  26. 一种芯片，其特征在于，包括：处理器，用于从存储器中调用并运行计算机程序，使得安装有所述芯片的设备执行如权利要求1至12中任一项所述的方法。
  27. 一种计算机可读存储介质，其特征在于，用于存储计算机程序，所述计算机程序使得计算机执行如权利要求1至12中任一项所述的方法。
  28. 一种计算机程序产品，其特征在于，包括计算机程序指令，该计算机程序指令使得计算机执行如权利要求1至12中任一项所述的方法。
  29. 一种计算机程序，其特征在于，所述计算机程序使得计算机执行如权利要求1至12中任一项所述的方法。
PCT/CN2020/101907 2020-07-14 2020-07-14 用于确定上行传输参数的方法和终端设备 WO2022011555A1 (zh)

Priority Applications (7)

Application Number Priority Date Filing Date Title
CN202080100687.XA CN115553006A (zh) 2020-07-14 2020-07-14 用于确定上行传输参数的方法和终端设备
EP20945665.6A EP4185037B1 (en) 2020-07-14 2020-07-14 Method for determining uplink transmission parameter, and terminal device
KR1020237004064A KR20230037590A (ko) 2020-07-14 2020-07-14 상향 전송 파라미터의 결정 방법 및 단말 디바이스
JP2023501676A JP2023538487A (ja) 2020-07-14 2020-07-14 アップリンク伝送パラメータの決定方法及び端末デバイス
PCT/CN2020/101907 WO2022011555A1 (zh) 2020-07-14 2020-07-14 用于确定上行传输参数的方法和终端设备
CN202310127377.2A CN116208308B (zh) 2020-07-14 2020-07-14 用于确定上行传输参数的方法和终端设备
US18/090,378 US20230262696A1 (en) 2020-07-14 2022-12-28 Method for determining uplink transmission parameter, and terminal device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2020/101907 WO2022011555A1 (zh) 2020-07-14 2020-07-14 用于确定上行传输参数的方法和终端设备

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US18/090,378 Continuation US20230262696A1 (en) 2020-07-14 2022-12-28 Method for determining uplink transmission parameter, and terminal device

Publications (1)

Publication Number Publication Date
WO2022011555A1 true WO2022011555A1 (zh) 2022-01-20

Family

ID=79555923

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/101907 WO2022011555A1 (zh) 2020-07-14 2020-07-14 用于确定上行传输参数的方法和终端设备

Country Status (6)

Country Link
US (1) US20230262696A1 (zh)
EP (1) EP4185037B1 (zh)
JP (1) JP2023538487A (zh)
KR (1) KR20230037590A (zh)
CN (2) CN115553006A (zh)
WO (1) WO2022011555A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023185870A1 (zh) * 2022-03-28 2023-10-05 北京紫光展锐通信技术有限公司 通信方法及相关装置
WO2023206354A1 (en) * 2022-04-29 2023-11-02 Apple Inc. Control signaling for multiple antenna panel physical uplink control channel transmission

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP4052524A4 (en) * 2019-11-01 2023-11-22 Hannibal IP LLC METHODS AND APPARATUS FOR DETERMINING DEFAULT SPATIAL RELATIONSHIP INFORMATION

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110120862A (zh) * 2018-02-06 2019-08-13 英特尔Ip公司 用于波束管理的装置和方法
CN110475360A (zh) * 2018-05-10 2019-11-19 华硕电脑股份有限公司 无线通信系统中上行链路传送的波束指示的方法和设备
WO2020035718A1 (en) * 2018-08-16 2020-02-20 Telefonaktiebolaget Lm Ericsson (Publ) Shared resource configuration for bandwidth parts
CN110913490A (zh) * 2018-01-12 2020-03-24 Oppo广东移动通信有限公司 上行数据传输方法及相关设备
CN111726213A (zh) * 2019-03-21 2020-09-29 华硕电脑股份有限公司 物理上行链路共享信道的波束指示的方法和设备

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10506587B2 (en) * 2017-05-26 2019-12-10 Samsung Electronics Co., Ltd. Method and apparatus for beam indication in next generation wireless systems
US11160061B2 (en) * 2018-07-05 2021-10-26 Apple Inc. Uplink transmission for multi-panel operation
CN111277395B (zh) * 2020-01-20 2022-10-25 北京紫光展锐通信技术有限公司 一种路损参考信号的确定方法及装置

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110913490A (zh) * 2018-01-12 2020-03-24 Oppo广东移动通信有限公司 上行数据传输方法及相关设备
CN110120862A (zh) * 2018-02-06 2019-08-13 英特尔Ip公司 用于波束管理的装置和方法
CN110475360A (zh) * 2018-05-10 2019-11-19 华硕电脑股份有限公司 无线通信系统中上行链路传送的波束指示的方法和设备
WO2020035718A1 (en) * 2018-08-16 2020-02-20 Telefonaktiebolaget Lm Ericsson (Publ) Shared resource configuration for bandwidth parts
CN111726213A (zh) * 2019-03-21 2020-09-29 华硕电脑股份有限公司 物理上行链路共享信道的波束指示的方法和设备

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
MEDIATEK INC.: "Remaining issues on multi-beam operation", 3GPP DRAFT; R1-2001823, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG1, no. e-Meeting; 20200420 - 20200430, 11 April 2020 (2020-04-11), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051875290 *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023185870A1 (zh) * 2022-03-28 2023-10-05 北京紫光展锐通信技术有限公司 通信方法及相关装置
WO2023206354A1 (en) * 2022-04-29 2023-11-02 Apple Inc. Control signaling for multiple antenna panel physical uplink control channel transmission

Also Published As

Publication number Publication date
US20230262696A1 (en) 2023-08-17
KR20230037590A (ko) 2023-03-16
EP4185037B1 (en) 2024-05-15
CN115553006A (zh) 2022-12-30
CN116208308A (zh) 2023-06-02
CN116208308B (zh) 2024-09-17
EP4185037A4 (en) 2023-07-19
JP2023538487A (ja) 2023-09-08
EP4185037A1 (en) 2023-05-24

Similar Documents

Publication Publication Date Title
US20230262696A1 (en) Method for determining uplink transmission parameter, and terminal device
CN115413045B (zh) 信息传输方法、终端设备和网络设备
WO2021258369A1 (zh) 无线通信方法、终端设备和网络设备
EP4216610A1 (en) Wireless communication method, terminal device, and network device
WO2021253455A1 (zh) 无线通信方法、终端设备和网络设备
US20220394503A1 (en) Wireless communication method and device
WO2023035144A1 (zh) 无线通信的方法、终端设备和网络设备
WO2022016342A1 (zh) 信道加扰方法和终端设备
WO2022188253A1 (zh) 无线通信的方法、终端设备和网络设备
WO2022155975A1 (zh) 无线通信的方法、终端设备和网络设备
WO2022227041A1 (zh) 上行传输方法、终端设备和网络设备
WO2022188081A1 (zh) 无线通信的方法、终端设备和网络设备
WO2022217443A1 (zh) 信道估计方法、终端设备、网络设备、芯片和存储介质
WO2022056870A1 (zh) 无线通信方法、终端设备和网络设备
WO2022027684A1 (zh) 信息上报方法、信息处理方法、终端设备和网络设备
WO2022006827A1 (zh) 无线通信方法、终端设备和网络设备
WO2023102848A1 (zh) 无线通信的方法和终端设备
WO2023102813A1 (zh) 无线通信的方法、终端设备和网络设备
WO2023141823A1 (zh) 无线通信的方法、终端设备和网络设备
WO2023197260A1 (zh) 无线通信的方法、终端设备和网络设备
WO2023123399A1 (zh) 无线通信的方法、终端设备和网络设备
WO2024026839A1 (zh) 无线通信的方法和终端设备
WO2022077346A1 (zh) 信道传输的方法、终端设备和网络设备
WO2023141760A1 (zh) 无线通信的方法、终端设备和网络设备
WO2023000328A1 (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: 20945665

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2023501676

Country of ref document: JP

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 20237004064

Country of ref document: KR

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2020945665

Country of ref document: EP

Effective date: 20230214