Wireless communication method, terminal device and network device
By associating multiple unscheduled PUSCHs with different spatial parameters in terminal and network devices, the transmission problem of unscheduled PUSCHs under multi-antenna panel configuration is solved, improving the uplink transmission spectral efficiency and performance.
Patent Information
- Application Number
- CN202511161954.5
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2023-01-12
- Publication Date
- 2025-11-11
AI Technical Summary
How to effectively transmit the scheduling-free Physical Uplink Shared Channel (PUSCH), especially in the case of multiple antenna panels, to improve uplink transmission performance.
Terminal and network devices enable independent transmission of multiple PUSCHs by associating multiple unscheduled PUSCHs with different spatial parameters, including reference signal sets, TCI status, antenna panels, control resource sets, and beam information.
It improves the spectral efficiency and performance of uplink transmission and solves the problem of scheduling-free PUSCH transmission.
Smart Images

Figure CN120934725A_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of communications, specifically to a wireless communication method, terminal device, and network device. Background Technology
[0002] In some scenarios, if a terminal device is configured with multiple antenna panels, it can transmit multiple Physical Uplink Shared Channels (PUSCHs) through these panels to improve uplink spectral efficiency. These multiple PUSCHs can be scheduled using a single Downlink Control Information (DCI) or multiple DCIs. However, how to transmit scheduling-free PUSCHs is a problem that urgently needs to be solved. Summary of the Invention
[0003] This application provides a wireless communication method, terminal device, and network device, which are beneficial for improving uplink transmission performance.
[0004] In a first aspect, a wireless communication method is provided, comprising: a terminal device transmitting one or more unscheduled Physical Uplink Shared Channels (PUSCHs), wherein the plurality of unscheduled PUSCHs are associated with different spatial parameters.
[0005] In a second aspect, a wireless communication method is provided, comprising: a network device receiving one or more unscheduled Physical Uplink Shared Channels (PUSCHs), wherein the plurality of unscheduled PUSCHs are associated with different spatial parameters.
[0006] Thirdly, a terminal device is provided for executing the methods described in the first aspect or its various implementations.
[0007] Specifically, the terminal device includes a functional module for performing the methods described in the first aspect or its various implementations.
[0008] Fourthly, a network device is provided for performing the methods described in the second aspect or its various implementations.
[0009] Specifically, the network device includes a functional module for performing the methods described in the second aspect or its various implementations.
[0010] Fifthly, a terminal device is provided, including a processor and a memory. The memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory to perform the methods described in the first aspect or its various implementations.
[0011] In a sixth aspect, a network device is provided, including a processor and a memory. The memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory to perform the methods in the second aspect or its implementations described above.
[0012] In a seventh aspect, a chip is provided for implementing the methods of any one of the first to second aspects or their respective implementations.
[0013] Specifically, the chip includes a processor for calling and running a computer program from memory, causing a device equipped with the device to perform the method as described in any of the first to second aspects above or in their respective implementations.
[0014] Eighthly, a computer-readable storage medium is provided for storing a computer program that causes a computer to perform the methods of any one of the first to second aspects or their respective implementations.
[0015] Ninthly, a computer program product is provided, including computer program instructions that cause a computer to perform the methods of any one of the first to second aspects or their respective implementations.
[0016] In a tenth aspect, a computer program is provided that, when run on a computer, causes the computer to perform the methods of any one of the first to second aspects or their respective implementations.
[0017] Through the above technical solution, the terminal device can send one or more unscheduled PUSCHs to the network device. The terminal device can use different spatial parameters to send these multiple unscheduled PUSCHs, which is beneficial to improving uplink transmission performance. Attached Figure Description
[0018] Figure 1 This is a schematic diagram of a communication system architecture provided in an embodiment of this application.
[0019] Figure 2 This is a schematic diagram illustrating simultaneous transmission across multiple panels.
[0020] Figure 3 This is a schematic interactive diagram of a wireless communication method provided according to an embodiment of this application.
[0021] Figure 4 This is a schematic diagram of the first and second PUSCHs that overlap in the time domain.
[0022] Figure 5 This is a schematic diagram of the interference between the first PUSCH and the second PUSCH.
[0023] Figure 6 This is a schematic block diagram of a terminal device provided according to an embodiment of this application.
[0024] Figure 7 This is a schematic block diagram of a network device provided according to an embodiment of this application.
[0025] Figure 8 This is a schematic block diagram of a communication device provided according to an embodiment of this application.
[0026] Figure 9 This is a schematic block diagram of a chip provided according to an embodiment of this application.
[0027] Figure 10 This is a schematic block diagram of a communication system provided according to an embodiment of this application. Detailed Implementation
[0028] The technical solutions of the embodiments of this application will now be described with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of this application, and not all of them. All other embodiments obtained by those skilled in the art without creative effort regarding the embodiments of this application are within the scope of protection of this application.
[0029] The technical solutions of this application embodiment can be applied to various communication systems, such as: Global System for Mobile Communication (GSM) system, Code Division Multiple Access (CDMA) system, Wideband Code Division Multiple Access (WCDMA) system, General Packet Radio Service (GPRS), Long Term Evolution (LTE) system, Advanced Long Term Evolution (LTE-A) system, New Radio (NR) system, evolution of NR system, LTE-based access to unlicensed spectrum (LTE-U) system, NR-based access to unlicensed spectrum (NR-U) system, Non-Terrestrial Networks (NTN) system, Universal Mobile Telecommunication System (UMTS), Wireless Local Area Networks (WLAN), and Wireless Fidelity (WF). Fidelity (WiFi), 5th-Generation (5G) communication systems, or other communication systems.
[0030] Traditional communication systems typically support a limited number of connections and are easy to implement. However, with the development of communication technology, mobile communication systems will not only support traditional communication but also, for example, device-to-device (D2D) communication, machine-to-machine (M2M) communication, machine-type communication (MTC), vehicle-to-vehicle (V2V) communication, or vehicle-to-everything (V2X) communication. The embodiments of this application can also be applied to these communication systems.
[0031] Optionally, the communication system in this application embodiment can be applied to a carrier aggregation (CA) scenario, a dual connectivity (DC) scenario, or a standalone (SA) network deployment scenario.
[0032] Optionally, the communication system in this application embodiment can be applied to unlicensed spectrum, wherein unlicensed spectrum can also be considered as shared spectrum; or, the communication system in this application embodiment can also be applied to licensed spectrum, wherein licensed spectrum can also be considered as non-shared spectrum.
[0033] This application describes various embodiments in conjunction with network devices and terminal devices. The terminal device may also be referred to as user equipment (UE), access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent, or user device, etc.
[0034] Terminal devices can be stations (STs) in WLANs, cellular phones, cordless phones, Session Initiation Protocol (SIP) phones, Wireless Local Loop (WLL) stations, Personal Digital Assistant (PDA) devices, handheld devices with wireless communication capabilities, computing devices or other processing devices connected to a wireless modem, in-vehicle devices, wearable devices, terminal devices in next-generation communication systems such as NR networks, or terminal devices in future evolved Public Land Mobile Network (PLMN) networks, etc.
[0035] In the embodiments of this application, 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); and it can also be deployed in the air (such as airplanes, balloons and satellites).
[0036] In the embodiments of this application, the terminal device may be a mobile phone, a tablet computer, a computer with wireless transceiver capabilities, 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 care, a wireless terminal device in a smart grid, a wireless terminal device in transportation safety, a wireless terminal device in a smart city, or a wireless terminal device in a smart home, etc.
[0037] By way of example and not limitation, in this embodiment, the terminal device can also be a wearable device. Wearable devices, also known as wearable smart devices, are a general term for devices that utilize wearable technology to intelligently design and develop everyday wearables, such as glasses, gloves, watches, clothing, and shoes. Wearable devices are portable devices that are worn directly on the body or integrated into the user's clothing or accessories. Wearable devices are not merely hardware devices, but also achieve powerful functions through software support, data interaction, and cloud interaction. Broadly speaking, wearable smart devices include those that are feature-rich, large in size, and can achieve complete or partial functions without relying on a smartphone, such as smartwatches or smart glasses, as well as those that focus on a specific type of application function and require the use of other devices such as smartphones, such as various smart bracelets and smart jewelry for vital sign monitoring.
[0038] In the embodiments of this application, the network device can be a device for communicating with mobile devices. The network device can be an access point (AP) in WLAN, a base station (BTS) in GSM or CDMA, a base station (NodeB, NB) in WCDMA, an evolved Node B (eNB or eNodeB) in LTE, a relay station or access point, or a vehicle-mounted device, wearable device, or a network device (gNB) in an NR network, or a network device in a future evolved PLMN network or an NTN network, etc.
[0039] By way of example and not limitation, in this embodiment, the network device may have mobility characteristics; for example, the network device may be a mobile device. Optionally, the network device may be a satellite or a balloon station. For example, 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. Optionally, the network device may also be a base station located on land, water, or other similar locations.
[0040] In this embodiment, the network device can provide services to a cell. The terminal device communicates with the network device through the transmission resources (e.g., frequency domain resources, or spectrum resources) used by the cell. The cell can be the cell corresponding to the network device (e.g., a base station). The cell can belong to a macro base station or to a base station corresponding to a small cell. The small cell can include: metro cell, micro cell, pico cell, femto cell, etc. These small cells have the characteristics of small coverage area and low transmission power, and are suitable for providing high-speed data transmission services.
[0041] For example, the communication system 100 used in the embodiments of this application is as follows: Figure 1 As shown. The communication system 100 may include a network device 110, which may be a device that communicates with a terminal device 120 (or a communication terminal, terminal). The network device 110 can provide communication coverage for a specific geographical area and can communicate with terminal devices located within that coverage area.
[0042] Figure 1 An exemplary embodiment shows a 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 its coverage area. This application embodiment does not limit this.
[0043] Optionally, the communication system 100 may also include other network entities such as a network controller and a mobility management entity, which is not limited in this embodiment.
[0044] It should be understood that devices with communication functions in the network / system of this application embodiment can be referred to as communication devices. Figure 1Taking the communication system 100 shown as an example, the communication equipment may include a network device 110 and a terminal device 120 with communication functions. The network device 110 and the terminal device 120 may be the specific devices described above, which will not be repeated here. The communication equipment may also include other devices in the communication system 100, such as network controllers, mobility management entities and other network entities. This application embodiment does not limit this.
[0045] It should be understood that the terms "system" and "network" are often used interchangeably in this document. The term "and / or" in this document merely describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, or B alone. Furthermore, the character " / " in this document generally indicates that the preceding and following related objects have an "or" relationship.
[0046] It should be understood that the term "instruction" mentioned in the embodiments of this application can be a direct instruction, an indirect instruction, or an indication of a relationship. For example, A instructing B can mean that A directly instructs B, such as B being able to obtain information through A; it can also mean that A indirectly instructs B, such as A instructing C, so B can obtain information through C; or it can mean that there is a relationship between A and B.
[0047] In the description of the embodiments of this application, the term "correspondence" may indicate that there is a direct or indirect correspondence between two things, or that there is an association between two things, or that there is a relationship of instruction and being instructed, configuration and being configured, etc.
[0048] In this application embodiment, "predefined" can be implemented by pre-storing corresponding codes, tables, or other means that can be used to indicate relevant information in the device (e.g., including terminal devices and network devices). This application does not limit the specific implementation method. For example, predefined can refer to what is defined in the protocol.
[0049] In this application embodiment, the "protocol" may refer to a standard protocol in the field of communication, such as the LTE protocol, the NR protocol, and related protocols applied to future communication systems. This application does not limit this.
[0050] To facilitate a better understanding of the embodiments of this application, the transmission scheme of the downlink multiple transmission reception point (TRP) related to this application will be described.
[0051] In NR systems, incoherent downlink and uplink transmission based on multiple TRPs is introduced. The ideal backhaul connection between TRPs can be ideal or non-ideal. Under ideal backhaul, TRPs can exchange information quickly and dynamically; under non-ideal backhaul, due to higher latency, TRPs can only exchange information quasi-statically. In downlink incoherent transmission, multiple TRPs can use different control channels to independently schedule multiple Physical Downlink Shared Channels (PDSCHs) of a single terminal, or they can use the same control channel to schedule the transmission of different TRPs. Data from different TRPs uses different transport layers; the latter is only suitable for ideal backhaul scenarios.
[0052] Network devices can schedule terminal devices to transmit Physical Uplink Shared Channels (PUSCHs) to two TRPs via a single Downlink Control Information (DCI). The PUSCHs transmitted to the two TRPs can be configured with independent transmission parameters, such as beamforming and precoding matrices, and the number of transmission layers for the PUSCHs transmitted to both TRPs is the same. In some scenarios, the PUSCHs transmitted to the two TRPs are transmitted using Time Division Multiplexing (TDM). The terminal devices align the PUSCHs transmitted to different TRPs with the corresponding TRPs using simulated beamforming, thereby spatially distinguishing different PUSCHs and improving uplink spectral efficiency. For codebook-based PUSCH transmission, this single DCI needs to include two Sounding Reference Signal Resource Indicator (SRS) fields and two Precoding Information and Number of Layers fields. The network device configures two Sounding Reference Signal (SRS) resource sets (SRSs). The first and second SRI fields correspond to these two SRS resource sets and are used to indicate the beam direction of the PUSCH transmitted to the two Transmission Points (TRPs). The second Precoding Information and Number of Layers field only needs to indicate the precoding information; the number of layers is the same as indicated by the first field by default. For non-codebook-based PUSCH transmission, this single DCI needs to include two SRI fields. The first SRI field indicates the PUSCH beam direction and the number of transmission layers, and the second SRI field indicates the PUSCH beam direction. The number of transmission layers field is the same as the number of transmission layers indicated by the first SRI. In the above description, the beam direction of PUSCH is the same as the beam direction of the SRS resource indicated by SRI.
[0053] Network devices can also schedule terminal devices to transmit PUSCH to two TRPs through multiple DCIs. These multiple DCIs can be carried by different Control Resource Sets (CORESETs). Specifically, the network device configures multiple CORESET groups, and each TRP uses the CORESETs in its own CORESET group for scheduling. That is, different TRPs can be distinguished by CORESET groups. For example, the network device can configure a CORESET group index for each CORESET, with different indices corresponding to different TRPs.
[0054] In some scenarios, PDSCHs from two TRPs scheduled by a single DCI (s-DCI) can be distinguished by the Transmission Configuration Indicator (TCI) state. One state of the TCI information field in the DCI can be mapped to a maximum of two TCI states. Each TCI state corresponds to one of the PDSCHs transmitted by Frequency-Division Multiplexing (FDM) or Spatial Division Multiplexing (SDM).
[0055] Due to the different spatial locations of various Transmission Platforms (TRPs), the large-scale characteristics of the channels corresponding to each TRP differ significantly. Therefore, in multi-TRP joint transmission, it is necessary to indicate the quasi-co-located (QCL) information corresponding to each TRP separately. In some cases, one state in the TCI information field of the DCI corresponds to only one TCI state. To support multi-TRP-based transmission, the Media Access Control Element (MACCE) signaling has been enhanced, meaning that one state in the TCI information field of the DCI can map to a maximum of two TCI states. If the TCI information field indicated in the DCI indicates two TCI states, the PDSCH associated with the first TCI state will be transmitted using the DMRS port indicated in the first Code Division Multiplexing (CDM) group, and the PDSCH associated with the second TCI state will be transmitted using the DMRS port indicated in the second CDM group. The beam direction of the PDSCH is the same as that of the Synchronization Signal Block (SSB) or Channel State Information Reference Signal (CSI-RS) corresponding to the TCI state.
[0056] The configuration and indication of TCI status includes three steps: Radio Resource Control (RRC) configuration, MAC CE activation, and DCI indication. The specific process is as follows:
[0057] RRC configures up to M TCI states for the terminal through PDSCH configuration (PDSCH-Config), where the value of M is determined by the UE capability, and the maximum value of M can be 128.
[0058] MAC CE activates up to eight TCI state groups to map to the 3-bit TCI information field in the DCI. Each TCI state group activated by MAC CE can contain one or two TCI states. If the higher-layer parameters configure the DCI to include a TCI indicator field, DCI format 1_1 can indicate a TCI state group from the MAC-activated TCI state groups. If the higher-layer parameters configure the DCI not to include a TCI indicator field or if data is scheduled via DCI format 1_0, the DCI will not contain a TCI state indicator field.
[0059] One TCI state can contain the following configuration:
[0060] TCI Status ID is used to identify a TCI status;
[0061] QCL Information 1;
[0062] QCL information 2.
[0063] One QCL message contains the following information:
[0064] The QCL type configuration can be one of QCL type A, QCL type B, QCL type C, or QCL type D;
[0065] QCL reference signal configuration includes the cell ID where the reference signal is located, the Band Width Part (BWP) ID, and the reference signal information (which can be the Channel State Information Reference Signal (CSI-RS) resource ID or the Synchronization Signal Block (SSB) index).
[0066] The definitions of different QCL type configurations are as follows:
[0067] 'QCL-TypeA': {Doppler shift, Doppler spread, average delay, delay spread};
[0068] 'QCL-TypeB': {Doppler shift, Doppler spread};
[0069] 'QCL-TypeC': {Doppler shift, average delay};
[0070] 'QCL-TypeD':{Spatial Rx parameter}.
[0071] To facilitate a better understanding of the embodiments of this application, the transmission scheme of uplink multi-TRP or antenna panel related to this application will be described.
[0072] If the terminal device is configured with multiple panels and supports simultaneous transmission of uplink information on multiple panels, then multiple uplink information messages can be sent simultaneously on multiple panels, such as... Figure 2 As shown, this is to improve uplink spectral efficiency. Uplink transmissions of multiple panels or TRPs can be scheduled via a single DCI or via multiple DCIs. Multiple PUSCHs sent by the terminal device can be in a unified TCI (unified TCI state) scenario, with multiple PUSCHs associated with different TCI states, and they can be non-overlapping, partially overlapping, or completely overlapping in the time domain.
[0073] In some scenarios, terminal devices also need to transmit scheduling-free PUSCH, such as Type 1 or Type 2 scheduling-free PUSCH. Type 1 scheduling-free PUSCH is configured via RRC and does not require DCI detection, while Type 2 scheduling-free PUSCH is configured via RRC and activated / deactivated via DCI. In this case, how to transmit scheduling-free PUSCH is a problem that urgently needs to be solved.
[0074] To facilitate understanding of the technical solutions of the embodiments of this application, the technical solutions of this application are described in detail below through specific embodiments. The above-mentioned related technologies are optional solutions and can be arbitrarily combined with the technical solutions of the embodiments of this application, all of which fall within the protection scope of the embodiments of this application. The embodiments of this application include at least some of the following contents.
[0075] Figure 3 This is a schematic interactive diagram of a wireless communication method 200 according to an embodiment of this application, such as... Figure 3 As shown, the method 200 includes at least the following:
[0076] S210, the terminal device sends one or more unscheduled Physical Uplink Shared Channels (PUSCHs), wherein the multiple unscheduled PUSCHs are associated with different spatial parameters.
[0077] In some embodiments, the type of the scheduling-free PUSCH can be type 1 or type 2, wherein the type 1 scheduling-free PUSCH is activated and deactivated by RRC signaling, and the type 2 scheduling-free PUSCH is configured by RRC signaling and activated or deactivated by DCI.
[0078] For example, when a terminal device sends a scheduling-free PUSCH, the scheduling-free PUSCH can be a type 1 or a type 2 scheduling-free PUSCH.
[0079] For example, when a terminal device sends multiple scheduling-free PUSCHs, these multiple scheduling-free PUSCHs may include type 1 scheduling-free PUSCHs and / or type 2 scheduling-free PUSCHs. That is, the multiple scheduling-free PUSCHs may all be type 1 scheduling-free PUSCHs, or they may all be type 2 scheduling-free PUSCHs, or they may include both type 1 and type 2 scheduling-free PUSCHs.
[0080] In some embodiments, spatial parameters may refer to spatial settings or spatial relations used for PUSCH transmission.
[0081] In some embodiments, the spatial parameters include, but are not limited to, at least one of the following:
[0082] Reference signal set information, Transmission Configuration Indicator (TCI) status information, antenna panel information, coresetPoolIndex information, and beam information.
[0083] In some embodiments, the reference signal set information may be SRS resource set information, SSB resource set information, or CSI-RS resource set information, etc. For example, the reference signal set information may include a reference signal set index, such as an SSB set index, a CSI-RS resource set index, or an SRS resource set index (SRS-ResourceSetId).
[0084] In some embodiments, antenna panel information may include an antenna panel ID or an index.
[0085] In some embodiments, CORESET group information may include the coresetPoolIndex.
[0086] In some embodiments, beam information may include a beam ID or an index.
[0087] In the embodiments of this application, the beam can also be referred to as a spatial domain filter or a spatial Rx parameter.
[0088] In some embodiments, the association of PUSCH with reference signal set information can refer to:
[0089] The set of reference signals associated with the antenna panel used to transmit PUSCH.
[0090] In some embodiments, the association between PUSCH and TCI status information can refer to:
[0091] The PUSCH transmit beam is determined based on the TCI status information.
[0092] In some embodiments, the association between PUSCH and antenna panel information can refer to:
[0093] PUSCH is transmitted via the antenna panel indicated by the antenna panel information.
[0094] In some embodiments, the association of PUSCH with control resource set information may refer to:
[0095] The CORESET group indicated by the control resource set group information is the CORESET group configured by higher-layer signaling for sending PUSCH.
[0096] In some embodiments, associating uplink information with beam information may include:
[0097] PUSCH is transmitted via the beam indicated by the beam information.
[0098] In some embodiments, multiple scheduling-free PUSCHs associated with different spatial parameters can refer to:
[0099] Multiple unscheduled PUSCHs are associated with multiple spatial parameters, where each unscheduled PUSCH is associated with one spatial parameter, and different unscheduled PUSCHs are associated with different spatial parameters. For example, multiple unscheduled PUSCHs include a first PUSCH and a second PUSCH, where the first PUSCH is associated with a first spatial parameter, and the second PUSCH is associated with a second spatial parameter, and the first and second spatial parameters are different.
[0100] In some embodiments, the first spatial parameter includes at least one of the following:
[0101] First reference signal set, first TCI state, first antenna panel (e.g., panel1), first CORESET group, first beam.
[0102] In some embodiments, the second spatial parameter includes at least one of the following:
[0103] Second reference signal set, second TCI state, second antenna panel (e.g., panel2), second CORESET group, second beam.
[0104] Example 1: Multiple scheduling-free PUSCHs are configured through the same high-level parameter.
[0105] For example, the transmission parameters of multiple unscheduled PUSCHs can be configured using the same high-level parameter. Specifically, the transmission parameters of these multiple unscheduled PUSCHs can be carried in an Information Element (IE).
[0106] For example, the spatial parameters of multiple unscheduled PUSCHs can be configured through the same high-level parameter. Specifically, the spatial parameters of multiple unscheduled PUSCHs can be carried in one IE.
[0107] For example, the transmission and spatial parameters of multiple unscheduled PUSCHs can be configured using the same high-level parameter. Specifically, the transmission and spatial parameters of multiple unscheduled PUSCHs can be carried in a single IE.
[0108] Optionally, the transmission parameters of the scheduling-free PUSCH include, but are not limited to, at least one of the following:
[0109] PUSCH time-domain offset, PUSCH time-domain allocation information, PUSCH frequency-domain allocation information, PUSCH antenna port, PUSCH precoding information and number of layers.
[0110] In some embodiments, multiple unscheduled PUSCHs are associated with different SRS resource set indices (SRS-ResourceSetId).
[0111] For example, multiple unscheduled PUSCHs include n unscheduled PUSCHs, where the SRS resource set indices associated with these n unscheduled PUSCHs are index 0, index 1, ..., index n-1, which can also be denoted as the first SRS resource set, ..., the nth SRS resource set.
[0112] In some embodiments, multiple unscheduled PUSCHs overlap in the time domain.
[0113] For example, if multiple unscheduled PUSCHs include two unscheduled PUSCHs, denoted as the first PUSCH and the second PUSCH, then the overlap of multiple unscheduled PUSCHs in the time domain may include the overlap of the time domain resources of the first PUSCH and the second PUSCH. Specifically, for example, the time domain symbols occupied by the first PUSCH and the second PUSCH may overlap.
[0114] In some embodiments, the time domain resources of the first PUSCH are configured through the first time domain resource configuration information (timeDomainAllocation), and the time domain resources of the second PUSCH are configured through the second time domain resource configuration information (timeDomainAllocation2).
[0115] Among them, the time-domain resources configured in the first time-domain resource configuration information and the second time-domain resource configuration information overlap, for example, the time-domain symbols overlap.
[0116] In some embodiments, the frequency domain resources of the first PUSCH are configured through the first frequency domain resource configuration information (frequencyDomainAllocation), and the frequency domain resources of the second PUSCH are configured through the second frequency domain resource configuration information (frequencyDomainAllocation2).
[0117] In some embodiments, the precoding information and number of layers for multiple scheduling-free PUSCHs are configured separately.
[0118] For example, multiple unscheduled PUSCHs include a first PUSCH and a second PUSCH. The precoding information and number of layers of the first PUSCH are configured through the first precoding and number of layers configuration information (precodingAndNumberOfLayers), and the precoding information and number of layers of the second PUSCH are configured through the second precoding and number of layers configuration information (precodingAndNumberOfLayers2).
[0119] In some embodiments, the precoding and layer number information of the first PUSCH is associated with the first SRS resource set, and the precoding and layer number information of the second PUSCH is associated with the second SRS resource set.
[0120] Optionally, the sum of the number of transport layers configured in the first precoding and layer number configuration information and the second precoding and layer number configuration information does not exceed 4, or the number of transport layers configured in both the first precoding and layer number configuration information and the second precoding and layer number configuration information does not exceed 2.
[0121] In some embodiments, the SRS resource indicators (srs-ResourceIndicator) for multiple unscheduled PUSCHs are configured separately.
[0122] For example, multiple unscheduled PUSCHs include a first PUSCH and a second PUSCH. The SRS resource corresponding to the first PUSCH is configured through the first SRS resource indication, and the SRS resource corresponding to the second PUSCH is configured through the second SRS resource indication.
[0123] The first SRS resource indicator is used to indicate a first SRS resource, and the second SRS resource indicator is used to indicate a second SRS resource. The first SRS resource indicated by the first SRS resource indicator belongs to the first SRS resource set, and the second SRS resource indicated by the second SRS resource indicator belongs to the second SRS resource set.
[0124] In some embodiments, the phase-tracking reference signals (PTRS) port index (e.g., ptrs-PortIndex) associated with the first SRS resource is different from the PTRS port index (e.g., ptrs-PortIndex2) associated with the second SRS resource. In some embodiments, the plurality of scheduling-free PUSCHs includes at least one codebook-based PUSCH and / or at least one non-codebook-based PUSCH. That is, the plurality of scheduling-free PUSCHs can all be codebook-based PUSCHs, all be non-codebook-based PUSCHs, or be partially codebook-based and partially non-codebook-based PUSCHs.
[0125] Optionally, when multiple unscheduled PUSCHs include non-codebook-based PUSCHs, such as the first PUSCH, the PTRS ports associated with one or more SRS resources corresponding to the first PUSCH are the same, that is, they correspond to the same ptrs-PortIndex.
[0126] In some embodiments, multiple unscheduled PUSCHs are associated with corresponding PTRSs, such as a first PTRS and a second PTRS. The port of the first PTRS associated with the port of the first PTRS is determined according to predefined rules. The port of the second PTRS associated with the port of the second PTRS is determined according to predefined rules.
[0127] In some implementations, a predefined rule is used to define the association relationship between PTRS and DMRS corresponding to a preset state in the PTRS-DMRS association information field of the DCI. This preset state can be any state. For example, the port of the first DMRS associated with the port of the first PTRS is determined based on state '0' or state '00' in the PTRS-DMRS association information field. Similarly, the port of the second DMRS associated with the port of the second PTRS is determined based on state '1', state '01', or state '11' in the PTRS-DMRS association information field. Optionally, the correspondence between the state values of the PTRS-DMRS association information field and the DMRS ports associated with the PTRS ports can be as shown in Table 1 or Table 2.
[0128] In other implementations, a predefined rule applies a default DMRS port. For example, the first DMRS port associated with the first PTRS port is the first DMRS port associated with PTRS port 0, or the first DMRS port associated with the first PTRS port is the first DMRS port associated with both PTRS port 0 and PTRS port 1. Similarly, the second DMRS port associated with the second PTRS port is the second DMRS port associated with PTRS port 0, or the second DMRS port associated with the second PTRS port is the second DMRS port associated with both PTRS port 0 and PTRS port 1.
[0129] Optionally, the port of the first DMRS is different from the port of the second DMRS.
[0130] Table 1
[0131]
[0132] Table 2
[0133]
[0134] In some embodiments, the maximum number of transport layers corresponding to multiple unscheduled PUSCHs is configured separately. In this case, the maximum number of transport layers corresponding to the multiple unscheduled PUSCHs can be the same or different.
[0135] In other embodiments, the maximum number of transport layers corresponding to multiple unscheduled PUSCHs is configured through the same higher-layer parameter.
[0136] In this case, the maximum number of transport layers corresponding to the multiple unscheduled PUSCHs can be the same.
[0137] Therefore, when multiple unscheduled PUSCHs are all type 1 unscheduled PUSCHs, this application provides a method for configuring the transmission parameters of these multiple PUSCHs, such as using independent precoding information and layer number, using independent maximum transmission layer configuration or the same maximum transmission layer configuration, etc.
[0138] In some embodiments, the multiple unscheduled PUSCHs include a first PUSCH and a second PUSCH. The first PUSCH is associated with a first SRS resource set, and the second PUSCH is associated with a second SRS resource set. The first SRS resource set is associated with a first control resource set, and the second SRS resource set is associated with a second control resource set. The indexes of the first control resource set and the second control resource set are different.
[0139] In some embodiments, the indexes of the first control resource set and the second control resource set are predefined or configured by the network device.
[0140] For example, if the indexes of the first control resource set and the second control resource set can be predefined, then the first SRS resource set is associated with the control resource set with index 0, and the second SRS resource set is associated with the control resource set with index 1.
[0141] For example, if the indexes of the first control resource set and the second control resource set are configured by the network device, the index of the control resource set associated with the SRS resource set can be configured in the configuration information of the SRS resource set, or both the control resource set index and the associated SRS resource set index can be configured in the ConfiguredUplinkGrant.
[0142] The following example illustrates the design of the RRC structure for carrying the transmission and spatial parameters of multiple unscheduled PUSCHs.
[0143] Example 1:
[0144]
[0145] Among them, srs-ResourceSetId is used to configure the SRS resource set of the first PUSCH, and srs-ResourceSetId2 is used to configure the SRS resource set of the second PUSCH; timeDomainOffset is used for the time domain offset of the first PUSCH, and timeDomainOffset2 is used to configure the time domain offset of the second PUSCH; timeDomainAllocation is used to configure the time domain allocation of the first PUSCH, and timeDomainAllocation2 is used to configure the time domain allocation of the second PUSCH; frequencyDomainAllocation is used to configure the frequency domain allocation of the first PUSCH, and frequencyD... `omainAllocation2` is used to configure the frequency domain allocation of the second PUSCH; `antennaPort` is used to configure the antenna port of the first PUSCH, and `antennaPort2` is used to configure the antenna port of the second PUSCH; `precodingAndNumberOfLayers` is used to configure the precoding information and number of layers of the first PUSCH, and `precodingAndNumberOfLayers2` is used to configure the precoding information and number of layers of the second PUSCH; `srs-ResourceIndicator` is used to configure the SRS resources corresponding to the first PUSCH, and `srs-ResourceIndicator2` is used to configure the SRS resources corresponding to the second PUSCH.
[0146] Example 2:
[0147]
[0148] Among them, srs-ResourceSetId is used to configure the SRS resource set of the first PUSCH, and srs-ResourceSetId2 is used to configure the SRS resource set of the second PUSCH; coresetPoolIndex1 is used to configure the control resource set group of the first PUSCH, and coresetPoolIndex2 is used to configure the control resource set group of the second PUSCH; timeDomainOffset is used for the time domain offset of the first PUSCH, and timeDomainOffset2 is used to configure the time domain offset of the second PUSCH; timeDomainAllocation is used to configure the time domain allocation of the first PUSCH, and timeDomainAllocation2 is used to configure the time domain allocation of the second PUSCH; frequencyDomainA `llocation` is used to configure the frequency domain allocation of the first PUSCH, and `frequencyDomainAllocation2` is used to configure the frequency domain allocation of the second PUSCH; `antennaPort` is used to configure the antenna port of the first PUSCH, and `antennaPort2` is used to configure the antenna port of the second PUSCH; `precodingAndNumberOfLayers` is used to configure the precoding information and number of layers of the first PUSCH, and `precodingAndNumberOfLayers2` is used to configure the precoding information and number of layers of the second PUSCH; `srs-ResourceIndicator` is used to configure the SRS resource corresponding to the first PUSCH, and `srs-ResourceIndicator2` is used to configure the SRS resource corresponding to the second PUSCH.
[0149] Example 3:
[0150]
[0151] Among them, srs-ResourceSetId is used to configure the SRS resource set of the first PUSCH, and srs-ResourceSetId2 is used to configure the SRS resource set of the second PUSCH; coresetPoolIndex1 is used to configure the control resource set group associated with the SRS resource set of the first PUSCH, and coresetPoolIndex2 is used to configure the control resource set group associated with the SRS resource set of the second PUSCH.
[0152] It should be noted that in the above examples, Examples 1 and 3 can be used together, meaning the terminal device can obtain the transmission parameters and spatial parameters corresponding to the first and second PUSCH based on the parameters in Examples 1 and 3. Example 2 can be used alone, meaning the terminal device can obtain the transmission parameters and spatial parameters corresponding to the first and second PUSCH based on the parameters in Example 2.
[0153] Therefore, when multiple unscheduled PUSCHs are all type 1 unscheduled PUSCHs, this application provides a method for configuring the spatial parameters of these multiple PUSCHs. The spatial parameters of the multiple PUSCHs and the transmission parameters of these multiple PUSCHs can be associated or configured independently, which improves the flexibility of configuration.
[0154] Example 2: Multiple scheduling-free PUSCHs are configured with different high-level parameters.
[0155] For example, multiple scheduling-free PUSCHs include a first PUSCH and a second PUSCH. The transmission parameters and spatial parameters of the first PUSCH are configured through a first higher-layer parameter, and the transmission parameters and higher-layer parameters of the second PUSCH are configured through a second higher-layer parameter.
[0156] Optionally, when the multiple scheduling-free PUSCHs are configured separately through multiple higher-level parameters, the multiple scheduling-free PUSCHs configured by the multiple higher-level parameters can have the characteristics described in Example 1.
[0157] For example, multiple unscheduled PUSCHs can be associated with different SRS resource set indexes.
[0158] For example, multiple unscheduled PUSCHs may overlap in the time domain.
[0159] For example, the precoding information and number of layers for multiple scheduling-free PUSCHs are configured independently.
[0160] For example, the SRS resource indications for multiple unscheduled PUSCHs are configured separately.
[0161] For example, multiple scheduling-free PUSCHs may include at least one codebook-based PUSCH and / or at least one non-codebook-based PUSCH.
[0162] For example, the maximum number of transport layers corresponding to multiple unscheduled PUSCHs can be configured separately, or they can be configured through the same higher-layer parameter.
[0163] The following example illustrates the design of the RRC structure for carrying the transmission and spatial parameters of multiple unscheduled PUSCHs.
[0164] Example 4:
[0165]
[0166]
[0167] The multiple unscheduled PUSCHs include a first PUSCH and a second PUSCH. `rrc-ConfiguredUplinkGrant1` is used to configure the transmission and spatial parameters of the first PUSCH, and `rrc-ConfiguredUplinkGrant2` is used to configure the transmission and spatial parameters of the second PUSCH. The functions of the parameters included in `rrc-ConfiguredUplinkGrant1` are described in Example 1 and will not be repeated here for simplicity. The functions of the parameters included in `rrc-ConfiguredUplinkGrant2` are also described in Example 1 and will not be repeated here for simplicity.
[0168] Example 5:
[0169]
[0170] The multiple unscheduled PUSCHs include a first PUSCH and a second PUSCH. `rrc-ConfiguredUplinkGrant1` is used to configure the transmission and spatial parameters of the first PUSCH, and `rrc-ConfiguredUplinkGrant2` is used to configure the transmission and spatial parameters of the second PUSCH. The functions of the parameters included in `rrc-ConfiguredUplinkGrant1` are described in Example 2, and for simplicity, they will not be repeated here. The functions of the parameters included in `rrc-ConfiguredUplinkGrant2` are also described in Example 2, and for simplicity, they will not be repeated here.
[0171] Example 6:
[0172]
[0173] Among them, srs-ResourceSetId is used to configure the SRS resource set of the first PUSCH, and srs-ResourceSetId2 is used to configure the SRS resource set of the second PUSCH; coresetPoolIndex1 is used to configure the control resource set group associated with the SRS resource set of the first PUSCH, and coresetPoolIndex2 is used to configure the control resource set group associated with the SRS resource set of the second PUSCH.
[0174] It should be noted that in the above examples, Examples 4 and 6 can be used together, meaning the terminal device can obtain the transmission parameters and spatial parameters corresponding to the first and second PUSCH based on the parameters in Examples 4 and 6. Example 5 can be used alone, meaning the terminal device can obtain the transmission parameters and spatial parameters corresponding to the first and second PUSCH based on the parameters in Example 5.
[0175] Therefore, when multiple unscheduled PUSCHs are all type 1 unscheduled PUSCHs, this application provides a method for configuring the spatial parameters of these multiple PUSCHs. The spatial parameters of the multiple PUSCHs and the transmission parameters of these multiple PUSCHs can be associated or configured independently, which improves the flexibility of configuration.
[0176] In some embodiments of this application, when the terminal device has multiple scheduling-free PUSCH configuration information (i.e., the terminal device has multiple scheduling-free configuration information), the method 200 further includes:
[0177] Based on the first instruction information from the network device, determine whether to send a scheduling-free PUSCH, or switch to sending a scheduling-free PUSCH; or,
[0178] If the preset conditions are met, determine whether to send a PUSCH without scheduling, or switch to sending a PUSCH without scheduling.
[0179] Specifically, the scheduling-free PUSCH is associated with either a first spatial parameter or a second spatial parameter. That is, the scheduling-free PUSCH can be either a first PUSCH or a second PUSCH.
[0180] In some embodiments, the terminal device has configuration information for multiple scheduling-free PUSCHs, which may include:
[0181] The terminal device receives configuration information for multiple scheduling-free PUSCHs configured by the network device. That is, the configuration information for these multiple scheduling-free PUSCHs can be configured by the network device. For example, it can be configured by the network device through RRC parameters, such as ConfiguredGrantConfig or RRC-ConfiguredUplinkGrant.
[0182] In some embodiments, the multiple unscheduled configuration information is used to configure the transmission of multiple unscheduled PUSCHs. These multiple unscheduled configuration information are associated with different spatial parameters; that is, the multiple unscheduled PUSCHs are associated with different spatial parameters. In other words, the terminal device needs to transmit multiple unscheduled PUSCHs using different spatial parameters. The unscheduled configuration information is a semi-static configuration. The terminal device can transmit multiple unscheduled PUSCHs based on these multiple unscheduled configuration information for a period of time. When the terminal device receives the first indication information from the network device, or when the terminal device determines that preset conditions are met, the terminal device can switch to sending a single unscheduled PUSCH, for example, transmitting the corresponding unscheduled PUSCH based on one of the multiple unscheduled configuration information.
[0183] It should be noted that the terminal device switching to send only one unscheduled PUSCH is relative to the terminal device's previous transmission. If the terminal device's previous transmission was based on multiple unscheduled configuration information for the transmission of multiple unscheduled PUSCHs, then upon receiving the first indication information or determining that the preset conditions are met, the terminal device can switch to sending only one unscheduled PUSCH. If the terminal device's previous transmission was also an unscheduled PUSCH transmission, then the terminal device may not perform the switch.
[0184] Therefore, in the embodiments of this application, when the terminal device needs to send multiple unscheduled PUSCHs, the terminal device can send only one unscheduled PUSCH according to the instructions of the network device or its own judgment, or in other words, suspend (drop) the transmission of some unscheduled PUSCHs.
[0185] In some embodiments, when the terminal device has configuration information for multiple Type 1 unscheduled PUSCHs, the terminal device switches to sending an unscheduled PUSCH according to the first indication information of the network device, or switches to sending an unscheduled PUSCH if preset conditions are met.
[0186] For example, a terminal device is configured with multiple unscheduling configuration information entries. These entries are used to configure the transmission of multiple Type 1 unscheduling PUSCHs. Each of these configuration entries is associated with a different spatial parameter; that is, each Type 1 unscheduling PUSCH is associated with a different spatial parameter. For a period of time, the terminal device transmits multiple Type 1 unscheduling PUSCHs based on these configuration entries. When the terminal device receives a first indication from the network device, or when the terminal device determines that a preset condition is met, it can switch to sending a single unscheduling PUSCH, for example, transmitting a corresponding Type 1 unscheduling PUSCH based on one of the multiple configuration entries.
[0187] The network device determines whether multiple unscheduled PUSCHs can be transmitted using multiple spatial parameters. In this way, the network device can determine whether the terminal device should transmit multiple unscheduled PUSCHs using multiple spatial parameters or transmit a single unscheduled PUSCH using a single spatial parameter based on system performance. The terminal device only needs to transmit according to the instructions of the network device, which helps to reduce the implementation complexity of the terminal device.
[0188] In some embodiments, the first indication information carries downlink signaling, which may be DCI or MAC CE, etc.
[0189] It should be understood that this application does not limit the specific indication method of the first indication information. For example, the first indication information can be used to indicate the PUSCH that needs to be suspended from transmission, or the PUSCH that does not need to be suspended from transmission, or the transmission status of each PUSCH among multiple unscheduled PUSCHs, such as whether the transmission needs to be suspended or whether the transmission should continue.
[0190] In some specific embodiments, the n states of the first indication information correspond to n unscheduled PUSCH transmissions, and each state is used to indicate that the corresponding PUSCH transmission is a PUSCH transmission that needs to be terminated, where n is a positive integer greater than 1.
[0191] For example, multiple unscheduled PUSCHs can be designated as a first PUSCH and a second PUSCH. The first indication information can be 1 bit, indicating two states: 0 and 1. These two states indicate that the first PUSCH and the second PUSCH need to be aborted, respectively. For example, state 0 indicates that the first PUSCH needs to be aborted, and state 1 indicates that the second PUSCH needs to be aborted.
[0192] For example, multiple unscheduled PUSCHs are designated as First PUSCH, Second PUSCH, Third PUSCH, and Fourth PUSCH. The first indication information can be 2 bits, used to indicate four states: 00, 01, 10, and 11. These four states respectively indicate that the transmission of the First PUSCH, Second PUSCH, Third PUSCH, and Fourth PUSCH needs to be aborted. For instance, state 00 indicates that the First PUSCH needs to be aborted, state 01 indicates that the Second PUSCH needs to be aborted, state 10 indicates that the Third PUSCH needs to be aborted, and state 11 indicates that the Fourth PUSCH needs to be aborted.
[0193] In some embodiments, the first indication information indicates, through a bit mapping method, which PUSCHs among a plurality of unscheduled PUSCHs need to be aborted, or which PUSCHs do not need to be aborted, or which PUSCHs need to continue transmission.
[0194] For example, multiple unscheduled PUSCHs include a first PUSCH and a second PUSCH. The first indication information can be 2 bits (B1B0). The first bit (B0) indicates whether the first PUSCH needs to be aborted, and the second bit (B1) indicates whether the second PUSCH needs to be aborted. As an example, B0 set to 1 indicates that the first PUSCH needs to be aborted, and B0 set to 0 indicates that the first PUSCH does not need to be aborted, or that transmission needs to continue. B1 set to 1 indicates that the second PUSCH needs to be aborted, and B1 set to 0 indicates that the second PUSCH does not need to be aborted, or that transmission needs to continue.
[0195] For example, multiple unscheduled PUSCHs include a first PUSCH, a second PUSCH, a third PUSCH, and a fourth PUSCH. The first indication information can be 4 bits (B3~B0). B0 indicates whether the first PUSCH needs to be aborted, B1 indicates whether the second PUSCH needs to be aborted, B2 indicates whether the third PUSCH needs to be aborted, and B3 indicates whether the fourth PUSCH needs to be aborted. As an example, B0 set to 1 indicates that the first PUSCH needs to be aborted, and B0 set to 0 indicates that the first PUSCH does not need to be aborted, or that transmission needs to continue. B1 set to 1 indicates that the second PUSCH needs to be aborted, and B1 set to 0 indicates that the second PUSCH does not need to be aborted, or that transmission needs to continue. B2 set to 1 indicates that the third PUSCH needs to be aborted, and B2 set to 0 indicates that the third PUSCH does not need to be aborted, or that transmission needs to continue. Setting B3 to 1 indicates that the fourth PUSCH needs to be aborted, while setting B3 to 0 indicates that the fourth PUSCH does not need to be aborted, or that transmission needs to continue.
[0196] In some embodiments of this application, the method 200 further includes:
[0197] Based on the first information, determine whether a preset condition is met, wherein the first information includes, but is not limited to, at least one of the following:
[0198] Power of multiple unscheduled PUSCHs;
[0199] Timing advance for multiple scheduling-free PUSCHs;
[0200] The time length during which multiple unscheduled PUSCHs overlap in the time domain;
[0201] Interference between multiple unscheduled PUSCHs;
[0202] Signal quality of multiple unscheduled PUSCHs.
[0203] The terminal device determines whether to use multiple spatial parameters to transmit multiple unscheduled PUSCHs. On the one hand, this helps reduce the signaling overhead of network devices. On the other hand, the terminal device determines whether to use multiple spatial parameters to transmit multiple unscheduled PUSCHs based on the first information, which helps ensure the transmission performance of PUSCHs.
[0204] In some embodiments, the preset conditions include, but are not limited to, at least one of the following:
[0205] The power difference of the plurality of unscheduled PUSCHs is greater than or equal to a first threshold.
[0206] The difference in timing advance of the multiple unscheduled PUSCHs is greater than or equal to the second threshold.
[0207] The number of symbols overlapping in the time domain among the multiple unscheduled PUSCHs is greater than or equal to the third threshold.
[0208] The difference or ratio of the strength of the first PUSCH and the interference strength of the second PUSCH on the first PUSCH in the plurality of scheduling-free PUSCHs is less than or equal to the fourth threshold.
[0209] The difference or ratio between the strength of the second PUSCH and the interference strength of the first PUSCH on the second PUSCH in the plurality of scheduling-free PUSCHs is less than or equal to the fifth threshold.
[0210] The interference between the multiple unscheduled PUSCHs is greater than or equal to the sixth threshold.
[0211] The difference or ratio of the signal quality of the multiple unscheduled PUSCHs is greater than or equal to the seventh threshold.
[0212] The power of a PUSCH reflects the level of interference it causes to other PUSCHs. When the difference or ratio of the power of two PUSCHs is large, it indicates that the transmission of the higher-powered PUSCH causes greater interference to the lower-powered PUSCH. In this case, switching to sending only one unscheduled PUSCH, such as sending only the higher-powered PUSCH, or sending only the lower-powered PUSCH, can help improve transmission performance.
[0213] For example, if the power of the first PUSCH is P11 and the power of the second PUSCH is P22, the terminal device can switch to sending only one unscheduled PUSCH, such as sending only the first PUSCH or the second PUSCH, when the absolute value of the difference between P11 and P22 is greater than or equal to a first threshold, or when the ratio of P11 to P22 is greater than or equal to the first threshold, or when the ratio of P22 to P11 is greater than or equal to the first threshold.
[0214] In some embodiments, the first threshold is predefined, or configured by the network device.
[0215] The difference in timing advance (TA) among multiple PUSCHs reflects the timing synchronization between these PUSCH transmissions. A large difference, such as exceeding the length of the cyclic prefix (CP), can lead to performance degradation. In this case, the terminal device can switch to sending only one unscheduled PUSCH, for example, only sending the PUSCH with a larger timing advance, or only sending the PUSCH with a smaller timing advance, which can improve transmission performance.
[0216] For example, if the TA of the first PUSCH is TA1 and the TA of the second PUSCH is TA2, then when the difference between TA1 and TA2 exceeds the second threshold or the difference between TA2 and TA1 exceeds the second threshold, the terminal device switches to sending only one unscheduled PUSCH, such as sending only the first PUSCH or the second PUSCH.
[0217] In some embodiments, the second threshold is predefined, or configured by the network device.
[0218] The time length during which multiple PUSCHs overlap in the time domain can refer to, for example, the number of overlapping symbols. The longer the time during which multiple PUSCHs overlap in the time domain, the greater the interference between them. When the time length during which multiple PUSCHs overlap is long, the terminal device can switch to sending only one unscheduled PUSCH, such as sending only the first PUSCH or the second PUSCH, which is beneficial to improving transmission performance.
[0219] For example, such as Figure 4 As shown, when the number of symbols overlapping between the first PUSCH and the second PUSCH is greater than the third threshold, the system switches to sending only one PUSCH, such as sending only the first PUSCH or only the second PUSCH.
[0220] In some embodiments, the third threshold is predefined or configured by the network device.
[0221] When there is significant interference between multiple unscheduled PUSCHs, the terminal device can switch to sending only one PUSCH, such as sending only the first PUSCH or only the second PUSCH, which helps improve transmission performance.
[0222] The term "significant interference between PUSCHs" can refer to a large interference intensity caused by the transmission of one PUSCH to the transmission of another, or it can refer to a large interference intensity relative to the intensity of the PUSCH transmission. For example, the difference between the interference intensity and the PUSCH intensity is large, or the ratio between the interference intensity and the PUSCH intensity is large.
[0223] In some embodiments, the interference of the first PUSCH to the second PUSCH is determined based on the SRS corresponding to the first PUSCH, or based on the signal quality and beam gain of the first PUSCH.
[0224] In some embodiments, the interference of the second PUSCH to the first PUSCH is determined based on the SRS corresponding to the second PUSCH, or based on the signal quality and beam gain of the second PUSCH.
[0225] In some embodiments, the signal quality of the PUSCH may include, but is not limited to, at least one of the following:
[0226] Reference Signal Receiving Power (RSRP), Reference Signal Receiving Quality (RSRQ), Signal to Interference plus Noise Ratio (SINR), and Received Signal Strength Indication (RSSI).
[0227] For example, such as Figure 5As shown, the power of the first PUSCH is P11, the power of the second PUSCH is P22, the interference of the first PUSCH on the second PUSCH is P12, and the interference of the second PUSCH on the first PUSCH is P21. Then, the terminal device can switch to sending only one PUSCH, such as sending only the first PUSCH or only the second PUSCH, when P12 is greater than the sixth threshold or P21 is greater than the sixth threshold, or P22 / P12 (or P22-P12) is less than or equal to the fifth threshold, or P11 / P21 (or P11-P21) is less than or equal to the fourth threshold.
[0228] In some embodiments, the fourth threshold is predefined, or configured by the network device.
[0229] In some embodiments, the fifth threshold is predefined, or configured by the network device.
[0230] In some embodiments, the sixth threshold is predefined or configured by the network device.
[0231] The signal quality of a PUSCH can also reflect the degree of interference that the transmission of that PUSCH causes to the transmission of other PUSCHs. A large difference in the signal quality of two PUSCHs indicates that the transmission of one PUSCH causes greater interference to the transmission of the other PUSCH. Therefore, when the difference or ratio of the signal quality of two PUSCHs is large, switching to transmitting only one PUSCH, such as transmitting only the first PUSCH or only the second PUSCH, is beneficial to improving transmission performance.
[0232] For example, when the difference or ratio between the signal quality of the first PUSCH and the signal quality of the second PUSCH is greater than or equal to the seventh threshold, or when the difference or ratio between the signal quality of the second PUSCH and the signal quality of the first PUSCH is greater than or equal to the seventh threshold, switching to sending only the first PUSCH or only the second PUSCH can improve transmission performance.
[0233] In some embodiments, the seventh threshold is predefined or configured by the network device.
[0234] In summary, in the embodiments of this application, the terminal device can send one or more unscheduled PUSCHs to the network device, wherein the terminal device can use different spatial parameters to send the multiple unscheduled PUSCHs.
[0235] Furthermore, when a terminal device sends multiple unscheduled PUSCHs, these multiple PUSCHs can be configured using the same higher-layer parameter, or they can be configured using different higher-layer parameters.
[0236] For example, the transmission and spatial parameters of these multiple PUSCHs can be configured through the same higher-level parameters.
[0237] For example, the transmission and spatial parameters of these multiple PUSCHs can be configured through different higher-level parameters.
[0238] Furthermore, when a terminal device sends multiple unscheduled PUSCHs, the terminal device can also switch to sending only one unscheduled PUSCH according to the instructions of the network device or under preset conditions, which helps to ensure the transmission performance of PUSCHs.
[0239] The above text combined Figures 3 to 5 The method embodiments of this application are described in detail below, in conjunction with... Figures 6 to 10 The present application describes the device embodiments in detail. It should be understood that the device embodiments correspond to the method embodiments, and similar descriptions can be referred to the method embodiments.
[0240] Figure 6 A schematic block diagram of a terminal device 400 according to an embodiment of this application is shown. Figure 6 As shown, the terminal device 400 includes:
[0241] Communication unit 410 is used to transmit one or more unscheduled Physical Uplink Shared Channels (PUSCHs), wherein the multiple unscheduled PUSCHs are associated with different spatial parameters.
[0242] In some embodiments, the spatial parameters include at least one of the following:
[0243] Reference signal set information, transmission configuration indication (TCI) status information, antenna panel information, control resource set information, and beam information.
[0244] In some embodiments, the plurality of unscheduled PUSCHs are configured with the same higher-level parameter, or the plurality of unscheduled PUSCHs are configured with different higher-level parameters.
[0245] In some embodiments, the plurality of unscheduled PUSCHs are associated with different Probe Reference Signal (SRS) resource set indices.
[0246] In some embodiments, the plurality of scheduling-free PUSCHs include a first PUSCH and a second PUSCH, the first PUSCH is associated with a first SRS resource set, the second PUSCH is associated with a second SRS resource set, the first SRS resource set is associated with a first control resource set, the second SRS resource set is associated with a second control resource set, and the index of the first control resource set is different from the index of the second control resource set.
[0247] In some embodiments, the indexes of the first control resource set and the second control resource set are predefined or configured by the network device.
[0248] In some embodiments, the plurality of unscheduled PUSCHs overlap in the time domain.
[0249] In some embodiments, the precoding information and the number of layers of the plurality of scheduling-free PUSCHs are configured separately.
[0250] In some embodiments, the SRS resource indications of the plurality of unscheduled PUSCHs are configured separately.
[0251] In some embodiments, the plurality of scheduling-free PUSCHs include at least one codebook-based PUSCH and / or at least one non-codebook-based PUSCH.
[0252] In some embodiments, the maximum number of transport layers corresponding to the plurality of unscheduled PUSCHs is configured separately or configured through the same higher-layer parameter.
[0253] In some embodiments, where the terminal device has configuration information for multiple scheduling-free PUSCHs, the terminal device further includes:
[0254] The processing unit is configured to determine, based on the first indication information from the network device, to send a scheduling-free PUSCH; or,
[0255] Under the condition that the preset conditions are met, determine to send a PUSCH without scheduling;
[0256] The scheduling-free PUSCH is associated with a first spatial parameter or a second spatial parameter, and the spatial parameters associated with the plurality of scheduling-free PUSCHs include the first spatial parameter and the second spatial parameter.
[0257] In some embodiments, the first indication information is carried in downlink control information (DCI) or media access control element (MAC CE).
[0258] In some embodiments, the n states of the first indication information correspond to n unscheduled PUSCH transmissions, and each state is used to indicate that the corresponding PUSCH transmission is a PUSCH transmission that needs to be terminated, where n is a positive integer greater than 1.
[0259] In some embodiments, the first indication information indicates, through a bit mapping method, which PUSCH among the plurality of unscheduled PUSCHs needs to be aborted.
[0260] In some embodiments, the terminal device further includes:
[0261] The processing unit is configured to determine whether a preset condition is met based on first information, wherein the first information includes at least one of the following:
[0262] The power of the multiple scheduling-free PUSCHs;
[0263] Timing advance of the multiple scheduling-free PUSCHs;
[0264] The time length during which the multiple scheduling-free PUSCHs overlap in the time domain;
[0265] Interference between the multiple scheduling-free PUSCHs;
[0266] The signal quality of the multiple scheduling-free PUSCHs.
[0267] In some embodiments, the preset conditions include at least one of the following:
[0268] The power difference of the plurality of unscheduled PUSCHs is greater than or equal to a first threshold.
[0269] The difference in timing advance of the multiple unscheduled PUSCHs is greater than or equal to the second threshold.
[0270] The number of symbols overlapping in the time domain among the multiple unscheduled PUSCHs is greater than or equal to the third threshold.
[0271] The difference or ratio of the strength of the first PUSCH and the interference strength of the second PUSCH on the first PUSCH in the plurality of scheduling-free PUSCHs is less than or equal to the fourth threshold.
[0272] The difference or ratio between the strength of the second PUSCH and the interference strength of the first PUSCH on the second PUSCH in the plurality of scheduling-free PUSCHs is less than or equal to the fifth threshold.
[0273] The interference between the multiple unscheduled PUSCHs is greater than or equal to the sixth threshold.
[0274] The difference in signal quality among the multiple unscheduled PUSCHs is greater than or equal to the seventh threshold.
[0275] In some embodiments, the first threshold is predefined, or configured by the network device.
[0276] In some embodiments, the second threshold is predefined, or configured by the network device.
[0277] In some embodiments, the third threshold is predefined or configured by the network device.
[0278] In some embodiments, the fourth threshold is predefined, or configured by the network device.
[0279] In some embodiments, the fifth threshold is predefined, or configured by the network device.
[0280] In some embodiments, the sixth threshold is predefined or configured by the network device.
[0281] In some embodiments, the seventh threshold is predefined or configured by the network device.
[0282] In some embodiments, the plurality of scheduling-free PUSCHs include a first PUSCH and a second PUSCH, wherein the interference of the first PUSCH to the second PUSCH is determined based on the SRS corresponding to the first PUSCH, or based on the signal quality and beam gain of the first PUSCH; the interference of the second PUSCH to the first PUSCH is determined based on the SRS corresponding to the second PUSCH, or based on the signal quality and beam gain of the second PUSCH.
[0283] Optionally, in some embodiments, the communication unit may be a communication interface or transceiver, or an input / output interface of a communication chip or system-on-a-chip. The processing unit may be one or more processors.
[0284] It should be understood that the terminal device 400 according to the embodiments of this application may correspond to the terminal device in the method embodiments of this application, and the above and other operations and / or functions of each unit in the terminal device 400 are respectively for implementing Figures 3 to 5 The corresponding process of the terminal device in method 200 shown will not be described in detail here for the sake of brevity.
[0285] Figure 7 This is a schematic block diagram of a network device according to an embodiment of this application. Figure 7 The network equipment 500 includes:
[0286] The communication unit 510 is configured to receive one or more unscheduled Physical Uplink Shared Channels (PUSCHs), wherein the multiple unscheduled PUSCHs are associated with different spatial parameters.
[0287] In some embodiments, the spatial parameters include at least one of the following:
[0288] Reference signal set information, transmission configuration indication (TCI) status information, antenna panel information, control resource set information, and beam information.
[0289] In some embodiments, the plurality of unscheduled PUSCHs are configured with the same higher-level parameter, or the plurality of unscheduled PUSCHs are configured with different higher-level parameters.
[0290] In some embodiments, the plurality of unscheduled PUSCHs are associated with different Probe Reference Signal (SRS) resource set indices.
[0291] In some embodiments, the plurality of scheduling-free PUSCHs include a first PUSCH and a second PUSCH, the first PUSCH is associated with a first SRS resource set, the second PUSCH is associated with a second SRS resource set, the first SRS resource set is associated with a first control resource set, the second SRS resource set is associated with a second control resource set, and the index of the first control resource set is different from the index of the second control resource set.
[0292] In some embodiments, the indexes of the first control resource set and the second control resource set are predefined or configured by the network device.
[0293] In some embodiments, the plurality of unscheduled PUSCHs overlap in the time domain.
[0294] In some embodiments, the precoding information and the number of layers of the plurality of scheduling-free PUSCHs are configured separately.
[0295] In some embodiments, the SRS resource indications of the plurality of unscheduled PUSCHs are configured separately.
[0296] In some embodiments, the plurality of scheduling-free PUSCHs include at least one codebook-based PUSCH and / or at least one non-codebook-based PUSCH.
[0297] In some embodiments, the maximum number of transport layers corresponding to the plurality of unscheduled PUSCHs is configured separately or configured through the same higher-layer parameter.
[0298] In some embodiments, the communication unit 510 is further configured to:
[0299] Send a first indication message, which is used to instruct the terminal device to send a scheduling-free PUSCH or switch to sending a scheduling-free PUSCH, wherein the scheduling-free PUSCH is associated with a first spatial parameter.
[0300] In some embodiments, the first indication information is carried in downlink control information (DCI).
[0301] In some embodiments, the n states of the first indication information correspond to n unscheduled PUSCH transmissions, and each state is used to indicate that the corresponding PUSCH transmission is a PUSCH transmission that needs to be terminated, where n is a positive integer greater than 1.
[0302] In some embodiments, the first indication information indicates, through a bit mapping method, which PUSCH among the plurality of unscheduled PUSCHs needs to be aborted.
[0303] In some embodiments, the communication unit 510 is further configured to:
[0304] Send first configuration information to the terminal device. The first configuration information is used to configure the judgment conditions for the terminal device to switch from sending multiple unscheduled PUSCHs to sending one unscheduled PUSCH.
[0305] In some embodiments, the first configuration information is used to configure at least one of the following thresholds:
[0306] First threshold, second threshold, third threshold, fourth threshold, fifth threshold, sixth threshold, seventh threshold;
[0307] The terminal device switches from sending multiple unscheduled PUSCHs to sending a single unscheduled PUSCH when at least one of the following conditions is met:
[0308] The power difference of the plurality of unscheduled PUSCHs is greater than or equal to the first threshold.
[0309] The difference in timing advance of the multiple unscheduled PUSCHs is greater than or equal to the second threshold.
[0310] The number of symbols overlapping in the time domain among the multiple unscheduled PUSCHs is greater than or equal to the third threshold.
[0311] The difference or ratio of the strength of the first PUSCH and the interference strength of the second PUSCH on the first PUSCH in the plurality of scheduling-free PUSCHs is less than or equal to the fourth threshold.
[0312] The difference or ratio between the strength of the second PUSCH and the interference strength of the first PUSCH on the second PUSCH in the plurality of scheduling-free PUSCHs is less than or equal to the fifth threshold.
[0313] The interference between the multiple unscheduled PUSCHs is greater than or equal to the sixth threshold.
[0314] The difference in signal quality among the multiple unscheduled PUSCHs is greater than or equal to the seventh threshold.
[0315] Optionally, in some embodiments, the communication unit may be a communication interface or transceiver, or an input / output interface of a communication chip or system-on-a-chip. The processing unit may be one or more processors.
[0316] It should be understood that the network device 500 according to the embodiments of this application may correspond to the network device in the method embodiments of this application, and the above and other operations and / or functions of each unit in the network device 500 are respectively for implementing Figures 3 to 5 The corresponding procedures for network devices in method 200 are not described in detail here for the sake of brevity.
[0317] Figure 8 This is a schematic structural diagram of a communication device 600 provided in an embodiment of this application. Figure 8 The communication device 600 shown includes a processor 610, which can call and run computer programs from memory to implement the methods in the embodiments of this application.
[0318] Optionally, such as Figure 8 As shown, the communication device 600 may further include a memory 620. The processor 610 can retrieve and run computer programs from the memory 620 to implement the methods described in this embodiment.
[0319] The memory 620 can be a separate device independent of the processor 610, or it can be integrated into the processor 610.
[0320] Optionally, such as Figure 8 As shown, the communication device 600 may also include a transceiver 630, and the processor 610 may control the transceiver 630 to communicate with other devices. Specifically, it may send information or data to other devices or receive information or data sent by other devices.
[0321] The transceiver 630 may include a transmitter and a receiver. The transceiver 630 may further include antennas, and the number of antennas may be one or more.
[0322] Optionally, the communication device 600 may specifically be a network device in the embodiments of this application, and the communication device 600 may implement the corresponding processes implemented by the network device in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.
[0323] Optionally, the communication device 600 may specifically be a mobile terminal / terminal device in the embodiments of this application, and the communication device 600 may implement the corresponding processes implemented by the mobile terminal / terminal device in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.
[0324] Figure 9This is a schematic structural diagram of the chip according to an embodiment of this application. Figure 9 The chip 700 shown includes a processor 710, which can call and run computer programs from memory to implement the methods in the embodiments of this application.
[0325] Optionally, such as Figure 9 As shown, chip 700 may further include memory 720. Processor 710 can retrieve and run computer programs from memory 720 to implement the methods described in this embodiment.
[0326] The memory 720 can be a separate device independent of the processor 710, or it can be integrated into the processor 710.
[0327] Optionally, the chip 700 may also include an input interface 730. The processor 710 can control the input interface 730 to communicate with other devices or chips; specifically, it can acquire information or data sent by other devices or chips.
[0328] Optionally, the chip 700 may also include an output interface 740. The processor 710 can control the output interface 740 to communicate with other devices or chips, specifically, to output information or data to other devices or chips.
[0329] Optionally, the chip can be applied to the network device in the embodiments of this application, and the chip can implement the corresponding processes implemented by the network device in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.
[0330] Optionally, the chip can be applied to the mobile terminal / terminal device in the embodiments of this application, and the chip can implement the corresponding processes implemented by the mobile terminal / terminal device in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.
[0331] It should be understood that the chip mentioned in the embodiments of this application may also be referred to as a system-on-a-chip, system chip, chip system, or system-on-a-chip, etc.
[0332] Figure 10 This is a schematic block diagram of a communication system 900 provided in an embodiment of this application. Figure 10 As shown, the communication system 900 includes a terminal device 910 and a network device 920.
[0333] The terminal device 910 can be used to implement the corresponding functions implemented by the terminal device in the above method, and the network device 920 can be used to implement the corresponding functions implemented by the network device in the above method. For the sake of brevity, these will not be elaborated here.
[0334] It should be understood that the processor in the embodiments of this application may be an integrated circuit chip with signal processing capabilities. In implementation, the steps of the above method embodiments can be completed by integrated logic circuits in the processor's hardware or by instructions in software form. The processor described above can be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. It can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of this application. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the methods disclosed in the embodiments of this application can be directly embodied in the execution of a hardware decoding processor, or executed by a combination of hardware and software modules in the decoding processor. The software modules can be located in random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, or other mature storage media in the art. The storage medium is located in memory, and the processor reads information from the memory and, in conjunction with its hardware, completes the steps of the above method.
[0335] It is understood that the memory in the embodiments of this application can be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. The non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. The volatile memory can be random access memory (RAM), which is used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), Synchronous DRAM (SDRAM), Double Data Rate SDRAM (DDR SDRAM), Enhanced Synchronous DRAM (ESDRAM), Synchlink DRAM (SLDRAM), and Direct Rambus RAM (DR RAM). It should be noted that the memory used in the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.
[0336] It should be understood that the above-described memory is exemplary and not a limiting description. For example, the memory in the embodiments of this application may also be static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct memory bus RAM (DR RAM), etc. That is to say, the memory in the embodiments of this application is intended to include, but is not limited to, these and any other suitable types of memory.
[0337] This application also provides a computer-readable storage medium for storing computer programs.
[0338] Optionally, the computer-readable storage medium can be applied to the network device in the embodiments of this application, and the computer program causes the computer to execute the corresponding processes implemented by the network device in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.
[0339] Optionally, the computer-readable storage medium can be applied to the mobile terminal / terminal device in the embodiments of this application, and the computer program causes the computer to execute the corresponding processes implemented by the mobile terminal / terminal device in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.
[0340] This application also provides a computer program product, including computer program instructions.
[0341] Optionally, the computer program product can be applied to the network device in the embodiments of this application, and the computer program instructions cause the computer to execute the corresponding processes implemented by the network device in the various methods of the embodiments of this application. For the sake of brevity, they will not be described in detail here.
[0342] Optionally, the computer program product can be applied to the mobile terminal / terminal device in the embodiments of this application, and the computer program instructions cause the computer to execute the corresponding processes implemented by the mobile terminal / terminal device in the various methods of the embodiments of this application. For the sake of brevity, they will not be described in detail here.
[0343] This application also provides a computer program.
[0344] Optionally, the computer program can be applied to the network device in the embodiments of this application. When the computer program is run on the computer, it causes the computer to execute the corresponding processes implemented by the network device in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.
[0345] Optionally, the computer program can be applied to the mobile terminal / terminal device in the embodiments of this application. When the computer program is run on a computer, it causes the computer to execute the corresponding processes implemented by the mobile terminal / terminal device in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.
[0346] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.
[0347] Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.
[0348] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.
[0349] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.
[0350] In addition, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.
[0351] If the aforementioned functions are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.
[0352] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.
Claims
1. A method for wireless communication, characterized in that, include: The terminal device sends multiple unscheduled Physical Uplink Shared Channels (PUSCHs), wherein the multiple unscheduled PUSCHs are associated with different spatial parameters, the spatial parameters including control resource set information, and the unscheduled PUSCHs are either type 1 unscheduled PUSCHs or type 2 unscheduled PUSCHs.
2. The method according to claim 1, characterized in that, The multiple unscheduled PUSCHs are associated with different Probe Reference Signal (SRS) resource set indices.
3. The method according to claim 2, characterized in that, The plurality of scheduling-free PUSCHs include a first PUSCH and a second PUSCH. The first PUSCH is associated with a first SRS resource set, and the second PUSCH is associated with a second SRS resource set. The first SRS resource set is associated with a first control resource set, and the second SRS resource set is associated with a second control resource set. The index of the first control resource set is different from the index of the second control resource set.
4. The method according to claim 3, characterized in that, The indexes of the first control resource set and the second control resource set are either predefined or configured by the network device.
5. The method according to claim 3 or 4, characterized in that, If the indexes of the first control resource set and the second control resource set are predefined, then the first SRS resource set is associated with the control resource set with index 0, and the second SRS resource set is associated with the control resource set with index 1.
6. The method according to any one of claims 1-5, characterized in that, The multiple unscheduled PUSCHs overlap in the time domain.
7. The method according to any one of claims 1-6, characterized in that, The plurality of scheduling-free PUSCHs include at least one codebook-based PUSCH and / or at least one non-codebook-based PUSCH.
8. A method for wireless communication, characterized in that, include: The network device receives multiple unscheduled Physical Uplink Shared Channels (PUSCHs), wherein the multiple unscheduled PUSCHs are associated with different spatial parameters, the spatial parameters including control resource set information, and the unscheduled PUSCHs are either type 1 unscheduled PUSCHs or type 2 unscheduled PUSCHs.
9. The method according to claim 8, characterized in that, The multiple unscheduled PUSCHs are associated with different Probe Reference Signal (SRS) resource set indices.
10. The method according to claim 9, characterized in that, The plurality of scheduling-free PUSCHs include a first PUSCH and a second PUSCH. The first PUSCH is associated with a first SRS resource set, and the second PUSCH is associated with a second SRS resource set. The first SRS resource set is associated with a first control resource set, and the second SRS resource set is associated with a second control resource set. The index of the first control resource set is different from the index of the second control resource set.
11. The method according to claim 10, characterized in that, The indexes of the first control resource set and the second control resource set are either predefined or configured by the network device.
12. The method according to any one of claims 8-11, characterized in that, The multiple unscheduled PUSCHs overlap in the time domain.
13. The method according to any one of claims 8-12, characterized in that, The plurality of scheduling-free PUSCHs include at least one codebook-based PUSCH and / or at least one non-codebook-based PUSCH.
14. A terminal device, characterized in that, include: A processor and a memory for storing a computer program, the processor for calling and running the computer program stored in the memory to perform the method as described in any one of claims 1 to 7.