Method for determining uplink transmission parameters and terminal device - Patents.com
The terminal device determines the transmission parameters for PUSCH in NR systems by utilizing the configured parameters for the PUCCH resource in the uplink BWP, addressing the challenge of multiple configured parameters and enhancing transmission reliability and efficiency.
Patent Information
- Application Number
- JP2023501676
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Filing Date
- 2020-07-14
- Publication Date
- 2025-05-19
- Estimated Expiration
- 2040-07-14
AI Technical Summary
In NR systems, determining the transmission parameters for PUSCH scheduled by DCI format 0_0 is challenging, especially when multiple sets of transmission parameters are configured for the PUCCH resource with the lowest resource identifier in the uplink BWP.
The terminal device determines the transmission parameters of the PUSCH based on the transmission parameters configured for the PUCCH resource in the uplink BWP, which includes selecting from PUCCH resources with single sets of transmission parameters, using parameters from the same TRP, or obtaining parameters from the QCL assumption of the downlink signal.
This method allows the terminal device to accurately determine the transmission parameters for PUSCH scheduled by DCI format 0_0, even in scenarios with multiple configured transmission parameters, thereby enhancing transmission reliability and efficiency.
Smart Images

Figure 0007679448000003 
Figure 0007679448000004 
Figure 0007679448000005
Abstract
Description
Technical Field
[0001] The embodiments of the present application relate to the field of communications, and specifically, to a method for determining uplink transmission parameters and a terminal device.
Background Art
[0002] In an NR (New Radio) system, for a Physical Uplink Shared Channel (PUSCH) scheduled by a Downlink Control Information (DCI) format 0_0, a terminal device can use the transmission beam on the PUCCH resource with the lowest resource identifier in the uplink bandwidth part (Band Width Part, BWP) activated on the carrier where the PUSCH is located as the transmission beam of the PUSCH.
[0003] To improve the transmission reliability of PUCCH, PUCCH diversity transmission based on multiple transmission / reception points (TRPs) is introduced, and the terminal device can repeatedly transmit the same PUCCH using the same PUCCH resource and different transmission parameters (such as transmission beam and power control parameters) in different slots. In the scenario of multi-TRP PUCCH diversity transmission, the PUCCH resource with the lowest resource identifier in the uplink BWP activated on the carrier where the PUSCH is located may constitute multiple spatial correlation information (i.e., multiple transmission beams). In this case, the PUSCH can only perform transmission of a single TRP (i.e., can only transmit with a single beam). In this case, how to determine the transmission parameters (such as the transmission beam) of the PUSCH scheduled by the DCI format 0_0 is an issue that needs to be solved urgently.
Summary of the Invention
[0004] The embodiments of the present application provide a method for determining uplink transmission parameters and a terminal device. When a plurality of sets of transmission parameters are configured for the PUCCH resource with the lowest resource identifier in the uplink BWP activated on the carrier where the PUSCH is located, the terminal device can determine the transmission parameters of the PUSCH scheduled by DCI format 0_0.
[0005] The first aspect provides a method for determining uplink transmission parameters, and the method includes: determining the transmission parameters of the PUSCH based on the transmission parameters on the PUCCH resource in the uplink BWP activated on the carrier where the PUSCH is located, where the PUSCH is the PUSCH scheduled by the first DCI format, and the transmission parameters are the transmission beam, and / or the transmission parameters are the reference signal used for path loss measurement.
[0006] Optionally, the first DCI format is DCI format 0_0.
[0007] The second aspect provides a terminal device for executing the method in the first aspect.
[0008] Specifically, the terminal device includes a functional module for executing the method in the first aspect.
[0009] The third aspect provides a terminal device including a processor and a memory. The memory stores a computer program, and the processor calls and executes the computer program stored in the memory to execute the method in the first aspect.
[0010] The fourth aspect provides an apparatus for realizing the method in the first aspect.
[0011] Specifically, it includes a processor that calls and executes a computer program from a memory so that a device equipped with the apparatus executes the method of the first aspect.
[0012] In a fifth aspect, there is provided a computer-readable storage medium for storing a computer program for causing a computer to execute the method in the first aspect.
[0013] In a sixth aspect, there is provided a computer program product including computer program instructions for causing a computer to execute the method in the first aspect.
[0014] In a seventh aspect, there is provided a computer program for causing a computer to execute the method in the first aspect when operating on a computer.
[0015] According to the above technical solution, when a plurality of sets of transmission parameters are configured for the PUCCH resource with the lowest resource identifier in the uplink BWP activated in the carrier where the PUSCH is located, the terminal device can determine the transmission parameters of the PUSCH scheduled by DCI format 0_0.
Brief Description of the Drawings
[0016]
Figure 1
Figure 2
Figure 3
Figure 4
Figure 5
Figure 6
Figure 7
Figure 8
Figure 9
Figure 10
Embodiments for Carrying Out the Invention
[0017] Hereinafter, the technical solutions in the embodiments of the present application will be described with reference to the drawings in the embodiments of the present application. Obviously, the described embodiments are some of the embodiments of the present application, not all of them. Based on the embodiments in the present application, all other embodiments obtained by those skilled in the art without creative labor belong to the protection scope of the present application.
[0018] Embodiments of the present application are applicable to various communication systems, for example, GSM (Global System of Mobile Communication) systems, CDMA (Code Division Multiple Access) systems, Wideband Code (wideband coding) systems, WCDMA (Division Multiple Access) systems, GPRS (General Packet Radio Service) systems, LTE (Long Term Evolution) systems, LTE-A (Advanced long term evolution) systems, NR (New Radio) systems, evolved systems of the NR system, LTE-U (LTE-based access to unlicensed spectrum) systems, NR-U (NR-based access to unlicensed spectrum) systems, Umts (Universal Mobile Telecommunication System), WLAN (Wireless Local Area Network), WiFi (Wireless Fidelity), next-generation communication (5G) systems or other communication systems.
[0019] Generally, conventional communication systems can handle a limited number of connections and are easy to implement. However, with the evolution of communication technologies, mobile communication systems support not only conventional communication but also, for example, D2D (Device to Device) communication, M2M (Machine to Machine) communication, MTC (Machine Type Communication), V2V (Vehicle to Vehicle) communication, etc., which are also available in embodiments of the present application.
[0020] Optionally, the communication system in embodiments of the present application can be applied to a carrier aggregation (CA) scenario, a dual connectivity (DC) scenario, or a standalone (SA) deployment scenario.
[0021] Optionally, the communication system in the embodiments of the present application can be applied to ungranted spectra that can be regarded as shared spectra, or the communication system in the embodiments of the present application can also be applied to granted spectra that can be regarded as non-shared spectra.
[0022] The embodiments of the present application describe various embodiments related to terminal devices and network devices. Here, the terminal device may also be referred to as a user equipment (UE), access terminal, user unit, user station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent, or user device.
[0023] The terminal device may be a station within a WLAN (STAION, ST), mobile phone, cordless phone, SIP (Session Initiation Protocol) phone, WLL (Wireless Local Loop) station, PDA (Personal Digital Assistant), digital assistant device, mobile device with wireless communication function, computing device connected to a wireless modem and other processing devices, in-vehicle device, wearable device, or a terminal device in an NR network or a future evolving Public Land Mobile Network (PLMN) network.
[0024] In the embodiments of the present application, the terminal device can be configured on land, including indoors or outdoors, handheld, worn or in-vehicle, can also be configured on the water surface (such as a steamship), and can also be configured in the air, such as an aircraft, balloon, satellite, etc.
[0025] In the embodiments of the present application, the terminal device may be a mobile phone, a tablet (Pad), a computer with wireless transmission and reception functions, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal device in industrial control, a wireless terminal device in self-driving, a wireless terminal device in remote medical, a wireless terminal device in smart grid, a wireless terminal device in transportation safety, a wireless terminal device in smart city, or a wireless terminal device in smart home, etc.
[0026] By way of example and not limitation, in the embodiments of the present application, the terminal device may be a wearable device. A wearable device, also known as a wearable smart device, is a general term for devices that apply wearable technology to daily wear such as glasses, gloves, watches, clothes, shoes, etc. and are intelligently designed and developed on the premise of being worn on the body. A wearable device is a portable terminal that can be directly worn on the body or incorporated into the user's clothes or accessories for use. A wearable device is not just a hardware device, but realizes its functions not only through software support, but also through data interaction and cloud-based interaction. Generally speaking, a wearable smart device refers to a full-function large device that does not depend on all or part of the functions of a smartphone, such as a smartwatch or smart glasses, and a smart bracelet or smart jewelry that is specialized for specific applications such as various body monitoring and needs to be used in combination with other devices such as a smartphone.
[0027] In the embodiments of the present application, the network device may be an access point (AP) in a WLAN, a base transceiver station (BTS) in GSM or CDMA, or a base station (NodeB, NB) in WCDMA, or an evolved base station (Evolutional Node B, eNB or eNodeB) in LTE, or a relay station or an access point, or an in-vehicle device, a wearable device, and a network device (gNB) in an NR network, or a network device in a future evolved PLMN network, or a network device in an NTN network, etc.
[0028] As an example, without limitation, in the embodiments of the present application, the network device may have mobile characteristics such that, for example, the network device can be a mobile device. Optionally, the network device may be a satellite, a balloon station. For example, the satellite can 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. Alternatively, the network device may be a base station installed in a terrestrial area, a water area, etc.
[0029] In an embodiment of the present application, a network device can provide services to a cell, a terminal device can communicate with the network device via transmission resources (e.g., frequency domain resources or spectrum resources) used by the cell, the cell may be a cell corresponding to a network device (e.g., a base station), the cell may belong to a macro base station, or may belong to a base station corresponding to a small cell, where the small cell may include a metro cell, a micro cell, a pico cell, a femto cell, etc. These small areas are characterized by a small coverage range and low transmission power, and are suitable for providing high-rate data transmission services.
[0030] Exemplarily, a communication system 100 to which an embodiment of the present application is applied is shown in FIG. 1. The communication system 100 may include a network device 110 that can be a device for communicating with a terminal device 120 (or a communication terminal, a terminal). The network device 110 can provide a communication overlay in a specific geographical area and communicate with terminal devices located within the overlay area.
[0031] FIG. 1 shows an exemplary communication system 100 consisting of one network device and two terminal devices. Optionally, the communication system 100 may include multiple network devices, and each network device may include other numbers of terminal devices within the coverage area, although not limited in this application example.
[0032] Optionally, the communication system 100 may also include other network entities such as a network controller, a mobility management entity, etc., and the embodiments of the present application are not limited thereto.
[0033] Note that in the network / system of the embodiments of the present application, it should be understood that a device having a communication function may sometimes be referred to as a communication device. Taking the communication system 100 shown in FIG. 1 as an example, the communication device may include a network device 110 and a terminal device 120 having a communication function. The network device 110 and the terminal device 120 may be specific devices as described above, and the description thereof is omitted here. The communication device may also include other devices in the communication system 100, such as a network controller, a mobile management entity, and other network entities, which are not limited in this application example.
[0034] It should be understood that in this document, the terms "system" and "network" are often used interchangeably. The "and / or" as used in this document merely indicates the relevance of related items. For example, for A and / or B, it indicates the existence of three relationships: A alone, both A and B, and B alone. Also, the character " / " in this document generally indicates an "or" relationship between the related objects before and after.
[0035] It should be understood that the "instruction" mentioned in the embodiments of the present application may be a direct instruction, an indirect instruction, or an indication of a related relationship. For example, A indicates B, A can directly indicate B. For example, B can be obtained by A. A indicates C, and B can be obtained through C, which can also represent the correlation between A and B.
[0036] In the description of the embodiments of the present application, the term "corresponding" may mean that there is a direct or indirect corresponding relationship between the two, or that there is a related relationship between the two, or it may be a relationship such as instruction and being instructed, configuration and being configured.
[0037] In the NR system, the terminal device can transmit uplink data and uplink control information using an analog beam. The terminal device can perform uplink beam management based on the probe reference signal (SRS: Sounding Reference Signal) and determine the analog beam used for uplink transmission. Specifically, the network device configures an SRS resource set for the terminal device, selects the SRS resource with the best received quality based on the SRS transmitted by the terminal device in the SRS resource set, and can notify the terminal device of the corresponding SRS resource indicator (SRI). When the terminal device receives the SRI, it 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). For the PUSCH scheduled by DCI, the SRI is indicated by the SRI indicator domain in the DCI, and for the PUSCH scheduled by Radio Resource Control (RRC), the SRI is notified by the corresponding scheduling signaling. If the DCI used to schedule the PUSCH is DCI format 0_0, the DCI does not include the SRI, and the terminal device uses the transmission beam on the Physical Uplink Control Channel (PUCCH) with the lowest resource identifier (Identity, ID) among the resources in which the spatial correlation information is configured on the activated bandwidth part (BWP) of the carrier where the PUSCH is located as the transmission beam of the PUSCH. At the same time, the terminal device uses the path loss measurement reference signal of the PUCCH as the path loss measurement reference signal of the PUSCH.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 there is no spatial correlation information configured in the PUCCH resource configured on the activated BWP on the carrier where the PUSCH is located, the terminal device can obtain the transmission beam of the PUSCH and the reference signal for path loss measurement based on the quasi-co-located (QCL) assumption (QCL type D) used for the CORESET with the lowest ID among the downlink BWPs activated on the carrier. For example, the reception beam of the downlink reference signal included in the QCL assumption can be used as the transmission beam of the PUSCH, and the downlink reference signal can be used as the reference signal for path loss measurement of the PUSCH.
[0038] For PUCCH, the beams used are also indicated using a similar method. Specifically, for each PUCCH resource, a plurality of PUCCH spatial relation information (PUCCH-spatialrelationinfo) is configured in the RRC signaling, and the currently used PUCCH-spatialrelationinfo is indicated via signaling of the Media Access Control (MAC) layer. Here, each PUCCH-Spatialrelationinfo includes a reference signal for determining the transmission beam of the PUCCH, which is any one of the SRS, the Channel State Information Reference Signal (CSI-RS), or the Synchronization Signal Block (SSB). The PUCCH-spatialrelationinfo can also include power control parameters corresponding to the PUCCH. For each SRS resource, corresponding SRS spatial relation information (SRS-spatialrelationinfo) including a reference signal for determining the transmission beam of the SRS can also be configured by the RRC signaling. When the PUCCH-spatialrelationinfo is not configured on the network side, the terminal device can obtain the transmission beam of the PUCCH based on the QCL assumption (QCL type D) used in the control resource set (CORESET) with the lowest ID among the downlink BWPs activated on the carrier where the PUCCH is located, in a similar manner to the PUSCH. For example, the reception beam of the downlink reference signal included in the QCL assumption can be used as the transmission beam of the PUCCH.
[0039] In the NR system, a network device configures a corresponding Transmission Configuration Indicator (TCI) state indicating a QCL reference signal corresponding to a target downlink signal or a target downlink channel for each downlink signal or downlink channel, whereby a terminal can receive the target downlink signal or the target downlink channel based on the reference signal.
[0040] Here, one TCI state includes the following configuration: A TCI state ID, which is used to indicate the TCI state. QCL information 1. QCL information 2.
[0041] Here, one QCL information further includes the following information: A QCL type configuration, which may be any of QCL type A, QCL type B, QCL type C, and QCL type D. A QCL reference signal configuration, including the cell ID where the reference signal is located, the BWP ID, and the identifier of the reference signal (which may be the CSI-RS resource ID or the SSB index). Here, the QCL type of at least one of QCL information 1 and QCL information 2 must be one of type A, type B, and type C, and the QCL type of another QCL information (if configured) must be QCL type D.
[0042] Here, the definitions of different QCL type configurations are as follows: '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}.
[0043] When the QCL reference signal for which the network device configures the target downlink channel via the TCI state is a reference SSB or a reference CSI-RS resource, and the QCL type is typeA, typeB, or typeC, the terminal device can receive using the same corresponding reception parameter, assuming that the target downlink channel is the same as the target large-scale parameter of the reference SSB or the reference CSI-RS resource, and the target large-scale parameter is determined by the QCL type configuration. Similarly, when the QCL reference signal for which the network device configures the target downlink channel via the TCI state is a reference SSB or a reference CSI-RS resource, and the QCL type is typeD, the terminal device can receive the target downlink channel using the same reception beam (i.e., Spatial Rx parameter) as that for receiving the reference SSB or the reference CSI-RS resource. Usually, the target downlink channel is transmitted by the same TRP or the same antenna panel or the same beam on the network side as its reference SSB or reference CSI-RS resource. When the transmission TRP or the transmission panel or the transmission beam of two downlink signals or downlink channels is different, usually different TCI states are configured.
[0044] Regarding the downlink control channel, the TCI state can be indicated by RRC signaling or RRC signaling + MAC signaling. In the case of the downlink data channel, the set of available TCI states is indicated by RRC signaling, a part of the TCI state is activated by MAC layer signaling, and finally one or two TCI states are indicated from the TCI state activated by the TCI state indication area in the DCI and used for the PDSCH scheduled by the DCI. For example, as shown in Figure 2, the network device indicates N candidate TCI states by RRC signaling, activates K TCI states by MAC signaling, and finally indicates one or two used TCI states from the TCI state activated by the TCI state indication area in the DCI.
[0045] To meet the requirements for the transmission delay and reliability of the physical Downlink Shared Channel (PDSCH), Release 16 (Rel-16) introduced PDSCH diversity transmission based on Transmission / Reception Points (TRPs), and receives data of different TRP transmissions in Frequency-division multiplexing (FDM), Time-division multiplexing mode (Testing Data Management / Technical Data Manage, TDM), or Space Division Multiplexing (SDM). A similar mechanism can also be used for PUCCH transmission to enhance the transmission reliability of PUCCH. Specifically, the terminal device can repeatedly transmit the same PUCCH (uplink control information for transmitting the same uplink control information (Uplink Control Information, UCI)) in different slots using the same PUCCH resource. Since PUCCHs in different slots are transmitted to different TRPs, the transmission beams and power control parameters used (such as the path loss reference signal, etc.) are also configured independently as shown in Figure 3. For example, one PUCCH resource can indicate N spatial-related information PUCCH-spatialrelationinfo or N TCI states for repeated PUCCH transmissions in different slots, and the transmission beam and power control parameters of the PUCCH can be obtained from the N spatial-related information PUCCH-spatialrelationinfo or N TCI states. Here, N is the number of cooperative TRPs. In the case of two TRPs, N = 2, as shown in Figure 4.
[0046] In the embodiments of the present application, the transmission power of the PUSCH is calculated by the following formula 1, TIFF0007679448000001.tif20170
[0047] TIFF0007679448000002.tif123170
[0048] After multi-TRP based PUCCH diversity transmission is introduced, the terminal device can retransmit the same PUCCH in different slots using the same PUCCH resource and different transmission parameters such as transmission beams and power control parameters. When multiple sets of spatial correlation information such as multiple beams are configured in the PUCCH resource with the lowest PUCCH resource ID on the activated BWP of the carrier where the PUSCH is located, how to determine the beam and path loss measurement reference signal of the PUSCH scheduled by DCI format 0_0 is an issue that needs to be resolved urgently.
[0049] Based on the above problems, the present application proposes a method for determining uplink transmission parameters. When multiple sets of transmission parameters (transmission beams and / or path loss measurement reference signals) are configured in the PUCCH resource with the lowest PUCCH resource ID in the uplink BWP activated on the carrier where the PUSCH is located, the terminal device can determine the transmission parameters (transmission beams and / or path loss measurement reference signals) of the PUSCH based on the technical solution of the present application. Specifically, the terminal device can select other PUCCH resources without multiple sets of spatial correlation information to obtain the transmission parameters of the PUSCH, or use the transmission parameters of the PUCCH transmitted to the same TRP as the transmission parameters of the PUSCH, or obtain the transmission parameters of the PUSCH from the QCL assumption of the downlink signal, so as to solve the problem that the PUSCH transmission parameters cannot be determined without signaling.
[0050] Hereinafter, the technical aspects of the present application will be described in detail with specific embodiments.
[0051] 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 can include at least a part of the following content.
[0052] In S210, the terminal device determines the transmission parameters of the PUSCH based on the transmission parameters on the PUCCH resource in the uplink BWP activated on the carrier where the PUSCH is located. Here, the PUSCH is a PUSCH scheduled by the first DCI format, and the transmission parameters are the transmission beam, and / or the transmission parameters are the reference signal used for path loss measurement.
[0053] Optionally, the first DCI format is DCI format 0_0.
[0054] Note that DCI format 0_0 is used for scheduling the PUSCH, and the DCI format 0_0 does not include the SRS resource indication (SRI). For the PUSCH scheduled by some other DCI formats other than DCI format 0_0, the network device can configure an SRS resource set for the terminal device, select the SRS resource with the best reception quality based on the SRS transmitted by the terminal device in the SRS resource set, and notify the corresponding SRS resource indication (SRI) to the terminal device. When the terminal device receives the SRI, it determines the analog beam used for transmitting the PUSCH as the analog beam used for the SRS resource indicated by the SRI.
[0055] That is, when the PUSCH is scheduled by the DCI format 0_0, since the DCI format 0_0 does not include the SRS resource indication (SRI), the terminal device cannot determine the analog beam used for transmitting the PUSCH based on the analog beam used for the SRS resource indicated by the SRI.
[0056] In addition, in the embodiments of the present application, the transmission beam of the PUCCH resource and the reference signal used for path loss measurement may be obtained by spatial correlation information (for example, PUCCH-Spatialrelationinfo), or may be obtained by the TCI state. Therefore, the transmission parameters of the PUCCH resource in the embodiments of the present application can refer to the spatial correlation information of the PUCCH resource or the TCI state.
[0057] In the embodiments of the present application, the transmission beam can also be called a spatial domain transmission filter (Spatial domain tranSmiSSion filter or Spatial domain filter for tranSmiSSion), or a spatial relation, or a spatial setting. The reception beam may also be called a spatial domain reception filter (Spatial domain reception filter or Spatial domain filter for reception), or a spatial Rx parameter.
[0058] In the embodiments of the present application, the reference signal used for path loss measurement may be a downlink reference signal for path loss measurement such as CSI-RS or SSB, and the terminal device can calculate the transmission power of the PUSCH based on the above formula 1 and calculate the transmission power of the PUSCH based on the measured path loss measurement value.
[0059] Optionally, in the embodiments of the present application, the uplink BWP can include a plurality of PUCCH resources, and each PUCCH resource can independently configure a resource identifier and PUCCH transmission parameters (for example, PUCCH spatial related information configuration). For example, for a certain PUCCH resource, no transmission beam is configured (for example, no PUCCH spatial related information is configured), for a certain PUCCH resource, only a single transmission beam is configured (for example, only one piece of PUCCH spatial related information is configured), and for a certain PUCCH resource, a plurality of transmission beams are configured (for example, a plurality of pieces of PUCCH spatial related information used for different repetitions of transmission are configured). That is, in the embodiments of the present application, PUCCH diversity transmission based on multi-TRP can be used in the uplink BWP.
[0060] Optionally, in the embodiments of the present application, S210 can specifically determine the transmission parameters of the PUSCH according to one or more of the following Examples 1 to 3.
[0061] As Example 1, the terminal device determines, as the transmission parameters of the PUSCH, the transmission parameters on the PUCCH resource with the lowest resource identifier among the PUCCH resources in which only one set of transmission parameters is configured in the uplink BWP activated on the carrier where the PUSCH is located.
[0062] In Example 1, for example, as shown in FIG. 6, five PUCCH resources are configured in the uplink BWP activated in the carrier where the PUSCH is located, namely, PUCCH Resource 0, PUCCH Resource 1, PUCCH Resource 2, PUCCH Resource 3, and PUCCH Resource 4, and the PUSCH is scheduled by DCI format 0_0. Here, two sets of transmission parameters (for example, PUCCH spatial related information 0 and PUCCH spatial related information 1) are configured for PUCCH Resource 0, one set of transmission parameters (for example, PUCCH spatial related information 2) is configured for PUCCH Resource 1, one set of transmission parameters (for example, PUCCH spatial related information 3) is configured for PUCCH Resource 2, no transmission parameters are configured for PUCCH Resource 3, that is, there is no PUCCH spatial related information in PUCCH Resource 3, and two sets of transmission parameters (for example, PUCCH spatial related information 4 and PUCCH spatial related information 5) are configured for PUCCH Resource 4. Specifically, the terminal device selects from PUCCH Resource 1 and PUCCH Resource 2, which are PUCCH resources with only one set of transmission parameters configured. Among PUCCH Resource 1 and PUCCH Resource 2, the PUCCH resource with the lowest resource identifier is PUCCH Resource 1, and the terminal device uses the transmission parameters of PUCCH Resource 1 as the transmission parameters of the PUSCH. For example, the terminal device uses the transmission beam of PUCCH Resource 1 as the transmission beam of the PUSCH. Also, the terminal device uses the reference signal used for the path loss measurement of PUCCH Resource 1 as the reference signal used for the path loss measurement of the PUSCH.
[0063] Therefore, in Example 1, when using multi-TRP-based PUCCH diversity transmission on the uplink BWP activated on the carrier where the PUSCH is located, the terminal device determines the transmission parameters 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 activated on the carrier where the PUSCH is located as the transmission parameters of the PUSCH, thereby avoiding the problem that there are multiple sets of transmission parameters to obtain the PUCCH resource of the PUSCH transmission parameters.
[0064] As Example 2, when multiple sets of transmission parameters are configured for the PUCCH resource with the lowest resource identifier in the uplink BWP activated on the carrier where the PUSCH is located, the terminal device determines the target transmission parameters among the multiple sets of transmission parameters as the transmission parameters of the PUSCH.
[0065] Optionally, in Example 2, the target transmission parameters are one set of pre-agreed transmission parameters among the multiple sets of transmission parameters, or the target transmission parameters are one set of transmission parameters pre-configured for the multiple sets of transmission parameters, or the target transmission parameters are one set of transmission parameters indicated by the network device among the multiple sets of transmission parameters.
[0066] For example, two sets of transmission parameters used for odd-numbered PUCCH retransmission and even-numbered PUCCH retransmission are configured for the PUCCH resource with the lowest resource identifier in the uplink BWP. In this case, the terminal device can determine the first set of transmission parameters among the two sets of transmission parameters as the transmission parameters of the PUSCH.
[0067] Also, for example, in this case, two pieces of PUCCH spatial correlation information used for odd-numbered PUCCH repeated transmissions and even-numbered PUCCH repeated transmissions respectively are configured for the PUCCH resource with the lowest resource identifier among the uplink BWP. The terminal device uses the transmission beam indicated by the first piece of PUCCH spatial correlation information as the transmission beam of the PUSCH, and uses the path loss measurement reference signal indicated by the first piece of PUCCH spatial correlation information as the path loss measurement reference signal of the PUSCH. Alternatively, the terminal device uses the transmission beam indicated by the second piece of PUCCH spatial correlation information as the transmission beam of the PUSCH, or uses the path loss measurement reference signal indicated by the second piece of PUCCH spatial correlation information as the path loss measurement reference signal of the PUSCH.
[0068] Optionally, in Example 2, the target transmission parameter is determined from the plurality of sets of transmission parameters by the CORESET set index (CORESETPoolIndex) of the CORESET where the DCI for scheduling the PUSCH is located.
[0069] Furthermore, in Example 2, the target transmission parameter is determined from the plurality of sets of transmission parameters based on the CORESET set index and the first correspondence relationship, where the first correspondence relationship is the correspondence relationship between the value of the CORESET set index and the transmission parameter set identifier.
[0070] Optionally, the CORESET set index can occupy N bits, where N is an integer greater than or equal to 1. For example, when N = 1, the values of the CORESET set index may be 0 and 1. Also, for example, when N = 2, the values of the CORESET set index may be 00, 01, 10, 11. Furthermore, for example, when N = 3, the CORESET set index may be 000, 001, 010, 011, 100, 101, 110, 111.
[0071] Optionally, when N = 1, if the CORESET set index value is 0, the target transmission parameter is the transmission parameter of the first set among the transmission parameters of the plurality of sets; if the CORESET set index value is 1, the target transmission parameter is the transmission parameter of the second set among the transmission parameters of the plurality of sets.
[0072] Optionally, when N = 2, if the CORESET set index value is 00, the target transmission parameter is the transmission parameter of the first set among the transmission parameters of the plurality of sets; if the CORESET set index value is 01, the target transmission parameter is the transmission parameter of the second set among the transmission parameters of the plurality of sets.
[0073] For example, the network device pre-configures one CORESET set index (CORESETPoolIndex) for each CORESET. Different CORESETs may adopt the same CORESET set index or different CORESET set indexes. Sometimes, when the CORESET set index occupies 1 bit, if no CORESET set index is configured for one CORESET, the terminal device assumes that the CORESET set index value of the CORESET is 0. When the terminal device detects a PDCCH carrying DCI in which the PUSCH is scheduled in the first CORESET, the terminal device determines a target transmission parameter from the plurality of sets of transmission parameters based on the CORESET set index of the first CORESET. For example, assuming that the CORESET set index occupies 1 bit and two sets of transmission parameters are configured for the PUCCH resource, when the CORESET set index value of the first CORESET is 0 or no CORESET set index is configured for the first CORESET, the transmission parameter of the first set among the two sets of transmission parameters is used as the transmission parameter of the PUSCH. When the CORESET set index value of the first CORESET is 1, the transmission parameter of the second set among the two sets of transmission parameters is used as the transmission parameter of the PUSCH.
[0074] Optionally, the method may also be applied to the case where two or more sets of transmission parameters are configured for the PUCCH resource.
[0075] Therefore, in Example 2, when using multi-TRP-based PUCCH diversity transmission in the uplink BWP activated on the carrier where the PUSCH is located, the terminal device ensures that different channels transmitted on the same TRP use the same transmission parameter by using the transmission parameter of the PUCCH that is the same as the receiving TRP of the PUSCH as the transmission parameter of the PUSCH.
[0076] As Example 3, the terminal device determines the transmission parameters of the PUSCH based on the number of transmission parameters configured for the PUCCH resource with the lowest resource identifier in the uplink BWP activated on the carrier where the PUSCH is located.
[0077] For example, if three PUCCH resources are configured in the uplink BWP activated on the carrier where the PUSCH is located, namely PUCCH Resource 0, PUCCH Resource 1, and PUCCH Resource 2, in this case, the terminal device can determine the transmission parameters of the PUSCH based on the number of transmission parameters configured for PUCCH Resource 0.
[0078] Optionally, in Example 3, when the number of the transmission parameters is 1, the terminal device determines the transmission parameters configured for the PUCCH resource with the lowest resource identifier in the uplink BWP as the transmission parameters of the PUSCH. When the number of the transmission parameters is greater than 1, the terminal device obtains the transmission parameters of the PUSCH from the QCL assumption used for the target CORESET, where the target CORESET is the CORESET with the lowest CORESET identifier among the CORESETs configured in the downlink BWP activated on the carrier where the PUSCH is located.
[0079] For example, if three CORESETs are configured in the downlink BWP activated on the carrier where the PUSCH is located, namely CORESET0, CORESET1, and CORESET2 respectively, the CORESET with the lowest CORESET identifier is CORESET0, that is, the target CORESET is CORESET 0.
[0080] Note that the network device pre-configures one CORESET identifier for each CORESET, and the CORESET identifiers of different CORESETs are different and are used to identify the CORESETs. For example, when the transmission parameter is a reference signal used for path loss measurement, the terminal device uses the downlink reference signal corresponding to the QCL assumption (the QCL type is QCL type-D) used for the target CORESET as the reference signal used for the path loss measurement of the PUSCH. Also, for example, when the transmission parameter is a transmission beam, the terminal device uses the reception beam of the downlink reference signal corresponding to the QCL assumption (the QCL type is QCL type-D) used for the target CORESET as the transmission beam of the PUSCH.
[0081] Optionally, in Example 3, when the number of the transmission parameters is 1, the terminal device determines the transmission parameter configured in the PUCCH resource with the lowest resource identifier in the uplink BWP as the transmission parameter of the PUSCH. When the number of the transmission parameters is greater than 1, the terminal device obtains the transmission parameter of the PUSCH from the QCL assumption used for the target CORESET, where the target CORESET is the CORESET where the DCI for scheduling the PUSCH is located.
[0082] For example, when the terminal device detects a PDCCH carrying DCI in which the PUSCH is scheduled in CORESET1, the terminal device obtains the transmission parameters of the PUSCH from the QCL assumption used for CORESET 1. For example, when the transmission parameter is a reference signal used for path loss measurement, the terminal device uses the downlink reference signal corresponding to the QCL assumption (the QCL type is QCL type-D) used for CORESET 1 as the reference signal used for the path loss measurement of the PUSCH. Also, for example, when the transmission parameter is a transmission beam, the terminal device uses the reception beam of the downlink reference signal corresponding to the QCL assumption (the QCL type is QCL type-D) used for CORESET 1 as the transmission beam of the PUSCH.
[0083] Optionally, in Example 3, when the number of the transmission parameters is 1, the terminal device determines the transmission parameter configured in the PUCCH resource with the lowest resource identifier in the uplink BWP as the transmission parameter of the PUSCH. When the number of the transmission parameters is greater than 1, the terminal device obtains the transmission parameters of the PUSCH from the target TCI state, where the target TCI state is the TCI state with the lowest TCI state identifier among the TCI states for the PDSCH transmission activated in the downlink BWP activated in the carrier where the PUSCH is located.
[0084] For example, five TCI states are configured in the downlink BWP activated in the carrier where the PUSCH is located, namely, TCI state 0, TCI state 1, TCI state 2, TCI state 3, and TCI state 4. Here, the TCI states for the PDSCH transmission in the active state include TCI state 2, TCI state 3, and TCI state 4. In this case, the TCI state identifier with the lowest TCI state identifier among the TCI states for the PDSCH transmission activated in the downlink BWP activated in the carrier where the PUSCH is located is TCI state 2, that is, the target TCI state is TCI state 2.
[0085] Note that the network device activates the TCI state for PDSCH transmission using a Media Access Control Control Element (MAC CE).
[0086] For example, when the transmission parameter is a reference signal used for path loss measurement, the terminal device uses, as the reference signal for PUSCH path loss measurement, the downlink reference signal (QCL type is QCL type-D) included in the TCI state with the lowest TCI state identifier among the TCI states for PDSCH transmission activated in the downlink BWP activated in the carrier where PUSCH is located. Also, for example, when the transmission parameter is a transmission beam, the terminal device uses, as the transmission beam of PUSCH, the reception beam of the downlink reference signal (QCL type is QCL type-D) included in the TCI state with the lowest TCI state identifier among the TCI states for PDSCH transmission activated in the downlink BWP activated in the carrier where PUSCH is located, or the terminal device uses, as the transmission beam of PUSCH, the transmission beam of the uplink reference signal included in the TCI state with the lowest TCI state identifier among the TCI states for PDSCH transmission activated in the downlink BWP activated in the carrier where PUSCH is located.
[0087] Therefore, in Example 3, the terminal device determines the transmission parameters of PUSCH in different ways based on the number of transmission parameters configured in the PUCCH resource with the lowest resource identifier in the uplink BWP activated in the carrier where PUSCH is located, that is, based on whether the PUCCH resource performs PUCCH diversity transmission based on multi-TRP, thereby supporting both single-TRP PUCCH transmission and multi-TRP PUCCH diversity transmission.
[0088] Optionally, in the embodiments of the present application, the CORESETs constituting different CORESET set indexes may be from different TRPs. For example, the CORESET transmission with the CORESET set index configured to 0 is from TRP 0, and the CORESET transmission with the CORESET set index configured to 1 is from TRP 1.
[0089] Optionally, in some embodiments, the terminal device transmits the PUSCH based on the determined transmission parameters of the PUSCH.
[0090] For example, after determining the transmission beam of the PUSCH, the terminal device can transmit the PUSCH using the transmission beam.
[0091] For example, after determining the reference signal used for path loss measurement of the PUSCH, the terminal device can perform path loss measurement using the reference signal and calculate the transmission power of the PUSCH using the measured path loss value.
[0092] Therefore, in the embodiments of the present application, when multiple spatial correlation information is configured in the PUCCH resource with the lowest resource identifier in the uplink BWP activated in the carrier where the PUSCH is located, the terminal device can determine the transmission parameters of the PUSCH scheduled by DCI format 0_0. Or, when using PUCCH diversity transmission based on multiple TRPs in the uplink BWP activated in the carrier where the PUSCH is located, the terminal device can determine the transmission parameters of the PUSCH scheduled by DCI format 0_0. Further, the terminal device can obtain the transmission parameters of the PUSCH by using other PUCCH resources in which multiple spatial correlation information is not configured, or use the transmission parameters transmitted to the PUCCH of the same TRP as the transmission parameters of the USCH, or obtain the transmission parameters of the PUSCH from the QCL assumption of the downlink signal, thereby solving the problem that the PUSCH transmission parameters cannot be determined without signaling.
[0093] In the above, in connection with FIGS. 5 to 6, embodiments of the method of the present application are described in detail. Hereinafter, in connection with FIGS. 7 to 10, embodiments of the device of the present application are described in detail. It should be understood that the device embodiments and the method embodiments correspond to each other, and the same description can refer to the method embodiments.
[0094] FIG. 7 is a block diagram of a terminal device 300 in an embodiment of the present application. As shown in FIG. 7, the terminal device 300 includes a processing unit 310. Based on the transmission parameters on the PUCCH resource in the uplink BWP activated in the carrier where the PUSCH is located, the processing unit 310 is configured to determine the transmission parameters of the PUSCH. Here, the PUSCH is a PUSCH scheduled by a first DCI format, and the transmission parameters are transmission beams, and / or the transmission parameters are reference signals used for path loss measurement.
[0095] Optionally, the processing unit 310 is specifically configured to: Determine, as the transmission parameter of the PUSCH, the transmission parameter on the PUCCH resource with the lowest resource identifier among the PUCCH resources in which only one set of transmission parameters is configured for the uplink BWP.
[0096] Optionally, the processing unit 310 is specifically configured to: When a plurality of sets of transmission parameters are configured for the PUCCH resource with the lowest resource identifier in the uplink BWP, determine, as the transmission parameter of the PUSCH, the target transmission parameter among the plurality of sets of transmission parameters.
[0097] Optionally, the target transmission parameter is one set of transmission parameters pre-agreed upon for the plurality of sets of transmission parameters, or the target transmission parameter is one set of transmission parameters pre-configured among the plurality of sets of transmission parameters, or the target transmission parameter is one set of transmission parameters indicated by the network device among the plurality of sets of transmission parameters.
[0098] Optionally, the target transmission parameter is determined from the plurality of sets of transmission parameters based on the CORESET set index where the DCI for scheduling the PUSCH is located.
[0099] Optionally, the target transmission parameter is determined from the plurality of sets of transmission parameters based on the CORESET set index and a first correspondence relationship, where the first correspondence relationship is the correspondence relationship between the value of the CORESET set index and the transmission parameter set identifier.
[0100] Optionally, if the CORESET set index value is 0, the target transmission parameter is the transmission parameter of the first set among the transmission parameters of the plurality of sets, and if the CORESET set index value is 1, the target transmission parameter is the transmission parameter of the second set among the transmission parameters of the plurality of sets.
[0101] Optionally, the processing unit 310 is specifically configured to determine the transmission parameter of the PUSCH based on the number of transmission parameters configured for the PUCCH resource with the lowest resource identifier in the uplink BWP.
[0102] Optionally, the processing unit 310 is specifically configured to determine, as the transmission parameter of the PUSCH, the transmission parameter configured for the PUCCH resource with the lowest resource identifier in the uplink BWP when the number of the transmission parameters is 1, and when the number of the transmission parameters is greater than 1, to obtain the transmission parameter of the PUSCH from the quasi - co - address QCL assumption used for the target CORESET, where the target CORESET is the CORESET with the lowest CORESET identifier among the CORESETs configured in the downlink BWP activated on the carrier where the PUSCH is located, or the target CORESET is the CORESET where the DCI for which the PUSCH is scheduled is located.
[0103] Optionally, the processing unit 310 is specifically configured to determine, as the transmission parameter of the PUSCH, the transmission parameter configured for the PUCCH resource with the lowest resource identifier in the uplink BWP when the number of the transmission parameters is 1, When the number of the transmission parameters is greater than 1, obtain the transmission parameters of the PUSCH from the target transmission configuration indication (TCI) state, where the target TCI state is the TCI state with the lowest TCI state identifier among the TCI states for the physical downlink shared channel (PDSCH) transmission activated in the downlink bandwidth part (BWP) activated in the carrier where the PUSCH is located.
[0104] Optionally, the terminal device 300 further includes a communication unit 320. The communication unit 320 is configured to transmit the PUSCH based on the determined transmission parameters of the PUSCH.
[0105] Optionally, the first DCI format is DCI format 0_0.
[0106] Optionally, in some embodiments, the above-mentioned communication unit may be a communication interface or transceiver, or an input / output interface of a communication chip or on-chip system. The above-mentioned processing unit may be one or more processors.
[0107] It should be noted that the terminal device 300 according to the embodiment of the present application can correspond to the terminal device in the method embodiment of the present application. For the sake of brevity, the above-mentioned operations and / or functions of each part in the terminal device 300 are not described here as they can realize the corresponding flow of the terminal device in the method 200 shown in FIG. 5.
[0108] FIG. 8 is a schematic configuration diagram of a communication device 400 according to an embodiment of the present application. The communication device 400 includes a processor 410 that can call and execute a computer program from a memory to implement the method in the embodiment of the present application.
[0109] Optionally, as shown in FIG. 8, the communication device 400 may also include a memory 420. Here, the processor 410 can call and execute a computer program from the memory 420 to implement the method in the embodiments of the present application.
[0110] Here, the memory 420 may be a device separate from the processor 410 or may be integrated into the processor 410.
[0111] Optionally, as shown in FIG. 8, the communication device 400 further includes a transceiver 430, and the processor 410 can control the transceiver 430 to communicate with other devices. Specifically, it can transmit information or data to other devices or receive information or data transmitted by other devices.
[0112] Here, the transceiver 430 can include a transmitter and a receiver. The transceiver 430 may further include an antenna, and the number of antennas may be one or more.
[0113] Optionally, the communication device 400 may be a network device in the embodiments of the present application, and the communication device 400 may implement the corresponding flows realized by the network device in various methods of the embodiments of the present application, but for the sake of brevity, it is omitted here.
[0114] Optionally, the communication device 400 may be a mobile terminal / terminal device in the embodiments of the present application, and the communication device 400 may implement the corresponding flows realized by the mobile terminal / terminal device in various methods of the embodiments of the present application, but for the sake of brevity, it is omitted here.
[0115] FIG. 9 is a schematic configuration diagram of an apparatus according to an embodiment of the present application. The apparatus 500 includes a processor 510 that can call and execute a computer program from a memory to implement the method in the embodiments of the present application.
[0116] Optionally, as shown in FIG. 9, the apparatus 500 may also include a memory 520. Here, the processor 510 can call and execute a computer program from the memory 520 to implement the method in the embodiments of the present application.
[0117] Here, the memory 520 may be a device separate from the processor 510 or may be integrated with the processor 510.
[0118] Optionally, the apparatus 500 may further include an input interface 530. The processor 510 can control the input interface 530 to communicate with other devices or chips. Specifically, it can obtain information or data transmitted by other devices or chips.
[0119] Optionally, the apparatus 500 may further include an output interface 540. The processor 510 can control the output interface 540 to communicate with other devices or chips. Specifically, it can output information or data to other devices or chips.
[0120] Optionally, the apparatus may be a network device in the embodiments of the present application, and the apparatus may implement the corresponding flows realized by the network device in various methods of the embodiments of the present application, but for the sake of brevity, they are omitted here.
[0121] Optionally, the apparatus may be a mobile terminal / terminal device in the embodiments of the present application, and the apparatus may implement the corresponding flows realized by the mobile terminal / terminal device in various methods of the embodiments of the present application, but for the sake of brevity, they are omitted here.
[0122] It should be noted that the apparatus mentioned in the embodiments of the present application may also be a chip. For example, a system-on-chip, a chip system, a system-level chip, or a system-on-chip, etc.
[0123] 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.
[0124] Here, this terminal device 610 can be used to implement the corresponding functions realized by the terminal device in the above method, and this network device 620 can be used to implement the corresponding functions realized by the network device in the above method. For the sake of brevity, the description is omitted here.
[0125] The processor of the embodiment of the present application may be an integrated circuit chip having signal processing capabilities. In implementation, the above steps in the method embodiment may be achieved by the integrated logic circuit of the hardware in the processor or instructions in the form of software. The above-mentioned processor may be a general-purpose processor, a DSP (Digital Signal Processor), an ASIC (Application Specific Integrated Circuit), an FPGA (Field Programmable Gate Array), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components. The general-purpose processor may be a microprocessor or any conventional processor, etc. The steps of the method disclosed in connection with the embodiments of the present application may be embodied as being directly executed and completed by the hardware decoder processor, or may be embodied as being executed and completed by combining the hardware and software modules in the decoder processor. The software module may exist in a mature storage medium in the art such as random access memory, flash memory, read-only memory, programmable read-only memory, or electrically erasable programmable memory, register, etc. This storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method according to its hardware.
[0126] It should be understood that the memory in the embodiments of this specification may be a volatile memory or a non-volatile memory, or may include both volatile memory and non-volatile memory. Here, the non-volatile memory may be a Read-Only Memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an Electrically EPROM (EEPROM), or a flash memory. The volatile memory may be a Random Access Memory (RAM) used as an external cache. By way of example and not limitation, many forms of RAM are available, such as 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). The memory of the systems and methods described in this specification is intended to include these and any other suitable types of memory, but is not limited thereto.
[0127] The above memory is illustrative and not limiting. For example, the memory in the embodiments of the present application may be a static random access memory (SRAM), a dynamic random access memory (DRAM), a synchronous dynamic random access memory (SDRAM), a double data rate synchronous dynamic random access memory (DDR SDRAM), an enhanced SDRAM (ESDRAM), a synch link DRAM (SLDRAM), or a Direct Rambus RAM (DR RAM), etc. That is, the memory in the embodiments of this specification is intended to include these and any other suitable types of memory, but is not limited thereto.
[0128] The embodiments of the present application further provide a computer-readable storage medium storing a computer program.
[0129] Optionally, the computer-readable storage medium is applied to the terminal device in the embodiments of the present application, and the computer program causes the computer to execute the corresponding flow realized by the mobile terminal / terminal device in each method of the embodiments of the present application. For the sake of brevity, the description thereof is omitted here.
[0130] The embodiments of the present application further provide a computer program product including computer program instructions.
[0131] Optionally, the computer program product is 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 flow realized by the mobile terminal / terminal device in each method of the embodiments of the present application. For the sake of brevity, the description thereof is omitted here.
[0132] The embodiments of the present application further provide a computer program.
[0133] Optionally, the computer program may be applied to the mobile terminal / terminal device in the embodiments of the present application. When the computer program is executed on a computer, the computer is caused to execute the corresponding flow realized by the mobile terminal / terminal device in each method of the embodiments of the present application. For the sake of brevity, the description thereof is omitted here.
[0134] Those skilled in the art will recognize that the units and algorithm steps of each example described in connection with the embodiments disclosed herein may be implemented in electronic hardware, or in a combination of computer software and electronic hardware. Whether these functions are executed in hardware or software depends on the specific application examples and design constraints of the technical solution. Those skilled in the art may use different methods for each specific application example to implement the described functions, but such implementations should not be considered as departing from the scope of the present application.
[0135] For the convenience and brevity of the description, those skilled in the art may refer to the corresponding processes in the method embodiments for the specific operation processes of the systems, devices, and units described above, and it will be understood that the description thereof is omitted here.
[0136] In some embodiments provided herein, it should be understood that the disclosed systems, devices, and methods may be implemented in other ways. For example, the device embodiments described above are merely illustrative. For example, the division of the units described is only a division of one logical function. When actually implemented, there may be additional divisions. For example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted or not executed. In another aspect, the shown or considered mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interface, device, or unit in electrical, mechanical, or other forms.
[0137] The means described as the separation means may or may not be physically separated, and the means shown as the means may or may not be physical means, that is, it may be located at one place or may be distributed among a plurality of network elements. In addition, in order to achieve the object of this embodiment, part or all of them can be selected as necessary.
[0138] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, each unit may physically exist separately, or two or more units may be integrated into one unit.
[0139] In addition, when these functions are realized as software functions and sold or used as independent products, they may be stored in a computer-readable recording medium. Based on such an understanding, the technical solution of the present application can essentially, or the part that contributes to the prior art, or the part of the technical solution, be embodied in the form of a software product stored in a storage medium. The software product includes instructions for causing 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 method described in each embodiment of the present application. Note that the storage medium includes various ones that can store program codes such as a U-disk, a portable hard disk, a Read-Only Memory, a ROM, a Random Access Memory, a RAM, a magnetic disk, and an optical disk.
[0140] As described above, the embodiments of the present application are described based on the technical idea of the present application. However, the present application is not limited to the above-described embodiments, and those skilled in the art based on the technical idea of the present application are included in the technical scope of the present application. Therefore, the protection scope of the present application should be determined only by the protection scope of the claims.
Claims
1. The terminal device determines a transmission parameter of a physical uplink control channel (PUCCH) based on a transmission parameter on a physical uplink shared channel (PUSCH) resource in an uplink bandwidth portion (BWP) activated on a carrier on which the physical uplink shared channel (PUSCH) is located; The PUSCH is a PUSCH scheduled in a first downlink control information (DCI) format, the transmission parameter is a transmission beam, and / or the transmission parameter is a reference signal used for path loss measurement; The terminal device determines a transmission parameter of the PUSCH based on a transmission parameter on a PUCCH resource in an uplink BWP activated on a carrier on which the PUSCH is located, When two sets of transmission parameters are configured for a PUCCH resource having the lowest resource identifier in the uplink BWP, the two sets of transmission parameters are used for an odd number of PUCCH repetitions and an even number of PUCCH repetitions, respectively, and a first set of transmission parameters of the two sets of transmission parameters is determined as the transmission parameters of the PUCCH, and the first set of transmission parameters is the transmission parameters used for the odd number of PUCCH repetitions.
13. A method for determining uplink transmission parameters, comprising:
2. The first DCI format is DCI format 0_0. The method of claim 1, further comprising: determining an uplink transmission parameter based on the determined uplink transmission parameter.
3. Determining a first set of transmission parameters of the two sets of transmission parameters as transmission parameters of the PUSCH, The PUCCH spatial related information determined for the first time by the terminal device is set as a transmission beam of a PUSCH. Method for determining uplink transmission parameters according to claim 1 or 2.
4. A plurality of PUCCH spatial related information is configured for the PUCCH resource, The method further includes: setting a path loss measurement reference signal indicated by the PUCCH spatial related information determined for the first time by the terminal device as a path loss measurement reference signal for a PUSCH. Method for determining uplink transmission parameters according to claim 1 or 2.
5. Indicating spatial related information or a TCI status for the PUCCH resource; The method further includes obtaining a transmit beam for a PUCCH resource and a reference signal for path loss measurement based on spatial correlation information or the TCI state. Method for determining uplink transmission parameters according to claim 1 or 2.
6. A terminal device comprising a processing unit, The processing unit is configured to determine a transmission parameter of a physical uplink control channel (PUCCH) based on a transmission parameter on a physical uplink shared channel (PUCCH) resource in an uplink bandwidth portion (BWP) activated on a carrier on which the physical uplink shared channel (PUCCH) is located, the PUSCH being a PUSCH scheduled in a first downlink control information (DCI) format, the transmission parameter being a transmission beam, and / or the transmission parameter being a reference signal used for path loss measurement; The processing unit includes: When two sets of transmission parameters are configured for a PUCCH resource having the lowest resource identifier in the uplink BWP, the two sets of transmission parameters are used for an odd number of PUCCH repeated transmissions and an even number of PUCCH repeated transmissions, respectively; The processing unit determines a first set of transmission parameters of the two sets of transmission parameters as transmission parameters of the PUSCH, and the first set of transmission parameters are transmission parameters used for the odd number of repeated PUCCH transmissions. A terminal device comprising:
7. The processing unit is configured to determine the PUCCH spatial related information determined for the first time as a transmission beam of a PUSCH. A terminal device according to claim 6 .
8. A plurality of PUCCH spatial related information is configured for the PUCCH resource, The processing unit is configured to determine a path loss measurement reference signal indicated by the first determined PUCCH spatial related information as a path loss measurement reference signal for a PUSCH. A terminal device according to claim 6 .
9. Indicating spatial related information or a TCI status for the PUCCH resource; The processing unit is configured to derive a transmit beam for a PUCCH resource and a reference signal for path loss measurement based on spatial correlation information or the TCI state. A terminal device according to claim 6 .