CN113260068B

CN113260068B - Transmission control method, terminal and network equipment

Info

Publication number: CN113260068B
Application number: CN202010083024.3A
Authority: CN
Inventors: 施源; 宋扬; 孙鹏
Original assignee: Vivo Mobile Communication Co Ltd
Current assignee: Vivo Mobile Communication Co Ltd
Priority date: 2020-02-07
Filing date: 2020-02-07
Publication date: 2023-09-19
Anticipated expiration: 2040-02-07
Also published as: CN113260068A; WO2021155807A1

Abstract

The invention provides a transmission control method, a terminal and network equipment, wherein the method comprises the following steps: receiving downlink control information DCI; and determining control information of Physical Uplink Shared Channel (PUSCH) transmission scheduled by the DCI according to the target identifier associated with the DCI. The embodiment of the invention can realize the dispatching of the PUSCH transmission in a multi-TRP transmission scene of multi-DCI.

Description

Transmission control method, terminal and network equipment

Technical Field

The present invention relates to the field of communications technologies, and in particular, to a transmission control method, a terminal, and a network device.

Background

In current communication systems, scheduling of physical uplink shared channel (Physical Uplink Shared Channel, PUSCH) transmissions is typically scheduled by downlink control information (Downlink Control Information, DCI). In order to improve reliability of PUSCH transmission and reduce transmission delay, a multi-transmission receiving point (Transmission Reception Point, TRP) transmission scenario of multiple DCIs is proposed, that is, at least two DCI scheduled terminals transmit to at least two transmission receiving points TRP in a time-sharing or simultaneous manner. However, in a multi-TRP transmission scenario with multiple DCIs, how to schedule PUSCH transmission becomes a problem to be solved.

Disclosure of Invention

The embodiment of the invention provides a transmission control method, a terminal and network equipment, which are used for solving the problem of how to schedule PUSCH transmission in a multi-TRP transmission scene of multi-DCI.

In a first aspect, an embodiment of the present invention provides a transmission control method, which is applied to a terminal, including:

receiving downlink control information DCI;

and determining control information of Physical Uplink Shared Channel (PUSCH) transmission scheduled by the DCI according to the target identifier associated with the DCI.

In a second aspect, an embodiment of the present invention provides a transmission control method, applied to a network device, including:

and sending Downlink Control Information (DCI) to a terminal, wherein the DCI is used for the terminal to determine the control information of the Physical Uplink Shared Channel (PUSCH) transmission scheduled by the DCI according to the target identifier associated with the DCI.

In a third aspect, an embodiment of the present invention provides a terminal, including:

a receiving module, configured to receive downlink control information DCI;

and the determining module is used for determining control information of Physical Uplink Shared Channel (PUSCH) transmission scheduled by the DCI according to the target identifier associated with the DCI.

In a fourth aspect, an embodiment of the present invention provides a network device, including:

a sending module, configured to send downlink control information DCI to a terminal, where the DCI is used for the terminal to determine control information of PUSCH transmission scheduled by the DCI according to a target identifier associated with the DCI.

In a fifth aspect, an embodiment of the present invention provides a terminal, including: the transmission control method comprises a memory, a processor and a program stored in the memory and capable of running on the processor, wherein the program is executed by the processor to realize the steps in the transmission control method.

In a sixth aspect, an embodiment of the present invention provides a network device, including: the transmission control method comprises a memory, a processor and a program stored in the memory and capable of running on the processor, wherein the program is executed by the processor to realize the steps in the transmission control method.

In a seventh aspect, an embodiment of the present invention provides a computer-readable storage medium having stored thereon a computer program which, when executed by a processor, implements the steps of the transmission control method described above.

In the embodiment of the invention, downlink control information DCI is received; and determining control information of Physical Uplink Shared Channel (PUSCH) transmission scheduled by the DCI according to the target identifier associated with the DCI. In this way, the target identity is set to be associated with the DCI, and control information is determined based on the target identity, so that different TRPs can be associated using different target identities. Therefore, the embodiment of the invention can realize the dispatching of the PUSCH transmission in the multi-TRP transmission scene of the multi-DCI.

Drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings that are needed in the description of the embodiments of the present invention will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and other drawings may be obtained according to these drawings without inventive effort to a person of ordinary skill in the art.

FIG. 1 is a block diagram of a network system to which embodiments of the present invention are applicable;

fig. 2 is a flowchart of a transmission control method according to an embodiment of the present invention;

fig. 3 is a flowchart of another transmission control method according to an embodiment of the present invention;

fig. 4 is a block diagram of a terminal according to an embodiment of the present invention;

fig. 5 is a block diagram of a network device according to an embodiment of the present invention;

fig. 6 is a block diagram of another terminal according to an embodiment of the present invention;

fig. 7 is a block diagram of another network device according to an embodiment of the present invention.

Detailed Description

The following description of the embodiments of the present invention will be made clearly and fully with reference to the accompanying drawings, in which it is evident that the embodiments described are some, but not all embodiments of the invention. All other embodiments, which can be made by those skilled in the art based on the embodiments of the invention without making any inventive effort, are intended to be within the scope of the invention.

The terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus. Furthermore, the use of "and/or" in the specification and claims means at least one of the connected objects, e.g., a and/or B, meaning that it includes a single a, a single B, and that there are three cases of a and B.

In embodiments of the application, words such as "exemplary" or "such as" are used to mean serving as an example, instance, or illustration. Any embodiment or design described herein as "exemplary" or "e.g." in an embodiment should not be taken as preferred or advantageous over other embodiments or designs. Rather, the use of words such as "exemplary" or "such as" is intended to present related concepts in a concrete fashion.

Embodiments of the present application are described below with reference to the accompanying drawings. The transmission control method, the terminal and the network equipment provided by the embodiment of the application can be applied to a wireless communication system. The wireless communication system may be a 5G system, or an evolved long term evolution (Evolved Long Term Evolution, elet) system, or a subsequent evolved communication system.

Referring to fig. 1, fig. 1 is a block diagram of a network system to which an embodiment of the present invention is applicable, and as shown in fig. 1, the network system includes a terminal 11 and a network device 12, where the terminal 11 may be a user terminal or other terminal side device, for example: terminal-side devices such as a mobile phone, a tablet (Tablet Personal Computer), a Laptop (Laptop Computer), a personal digital assistant (personal digital assistant, PDA for short), a mobile internet Device (Mobile Internet Device, MID) or a Wearable Device (weardable Device), it should be noted that the specific type of the terminal 11 is not limited in the embodiment of the present invention. The network device 12 may be a 5G base station, or a later version of a base station, or a base station in other communication systems, or referred to as a node B, an evolved node B, or TRP, or an Access Point (AP), or other words in the field, and the network device is not limited to a specific technical word as long as the same technical effect is achieved. In addition, the network device 12 may be a Master Node (MN) or a Secondary Node (SN). It should be noted that, in the embodiment of the present invention, only a 5G base station is taken as an example, but the specific type of the network device is not limited.

Referring to fig. 2, fig. 2 is a flowchart of a transmission control method according to an embodiment of the present invention, where the method is applied to a terminal, as shown in fig. 2, and includes the following steps:

step 201, receiving downlink control information DCI;

step 202, determining control information of PUSCH transmission of the physical uplink shared channel scheduled by the DCI according to the target identifier associated with the DCI.

It should be understood that a terminal may receive DCI transmitted with only one TRP or may receive DCI transmitted with multiple TRPs within one period.

Optionally, the DCI scheduled PUSCH transmission may include transmission of scheduled uplink data, and may also include transmission of a resource set (SRS) for activating an aperiodic sounding reference signal (Sounding Reference Signal) on a PUSCH.

In an embodiment, the control information may include indication information for activating the SRS resource set. Optionally, in a case that the control information includes indication information for activating an SRS resource set, after determining, according to the target identifier associated with the DCI, control information of PUSCH transmission of a physical uplink shared channel scheduled by the DCI, the method further includes:

and activating an aperiodic SRS resource set associated with the target identifier.

In the embodiment of the present invention, the target identifier may be understood as a TRP identifier or association information corresponding to TRP one to one, which is not further limited herein. Wherein each target identity is associated with at least one aperiodic SRS resource set. Alternatively, the power control parameters of different aperiodic SRS resource sets associated with the target identifier may be the same or different. For example, when the distances from the terminal to two TRPs are the same, the power control parameters of the aperiodic SRS resource set corresponding to the two TRPs may be the same; when the distances from the terminal to the two TRPs are different, the power control parameters of the aperiodic SRS resource set corresponding to the two TRPs may be different.

In another embodiment, the control information may include indication information of a third indication field in the DCI, where the third indication field includes at least one of a sounding reference signal resource indication (Sounding Reference Signal resource indicator, SRI) field, a transmission precoding matrix indication (Transmit Precoding Matrix Indicator, TPMI) field, a redundancy version (Redundancy version) field, a power control field, an Antenna port (Antenna ports) field, an SRS request (request) field, and a channel state information request (Channel State Information request, CSI request) field. In other words, in this embodiment, the third indication field needs to be interpreted according to the corresponding configuration of the target identifier triggering the corresponding uplink transmission.

The SRI field, TPMI field, redundancy version field, power control field, antenna port field, SRS request field, and CSI request field of the M DCIs may be configured to have different values. And each domain needs to be interpreted according to the corresponding configuration of the TRP identity triggering the corresponding uplink transmission. In other words, the SRI field, TPMI field, redundancy version field, power control field, antenna port field, SRS request field, and at least one field configuration parameter in the CSI request field of any two DCIs are different.

Optionally, before the receiving DCI, the method further includes:

and receiving configuration information, wherein the configuration information is used for configuring at least one aperiodic SRS resource set, and each target identifier is associated with the at least one aperiodic SRS resource set.

In the embodiment of the present invention, for the scenes of codebook, non-codebook, beam management and antenna switching, a plurality of aperiodic SRS resource sets may be supported, where the configuration information may configure at least one aperiodic SRS resource set for the TRP associated with each target identifier. Optionally, in an embodiment, the set identities of the aperiodic SRS resource set associated with different target identities are different. That is, there is no intersection between the set identifications of the aperiodic SRS resource set associated with any two target identifications. For example, object identification a is associated with aperiodic SRS resource set 1, object identification B is associated with aperiodic SRS resource set 2 and associated aperiodic SRS resource set 3.

Optionally, the target indicator field of the DCI is used to activate a target aperiodic SRS resource set in the at least one aperiodic SRS resource set, a target identifier associated with the target aperiodic SRS resource set is the same as a target identifier associated with the DCI, and the target indicator field is a field used to activate the aperiodic SRS resource set.

In other words, in the embodiment of the present invention, only when the target identifier associated with the aperiodic SRS resource set coincides with the target identifier associated with the DCI for activating the aperiodic SRS resource set, the target indication field (for example SRS request field) in the DCI may be used to activate the aperiodic SRS resource set.

It should be noted that, the manner of obtaining the target identifier associated with the aperiodic SRS resource set may be set according to actual needs. For example, in one embodiment, the aperiodic SRS resource set includes a target identifier; in another embodiment, the target identity associated with the aperiodic SRS resource set is obtained through spatial relationship information (spatial relation info) of the associated RSs in the aperiodic SRS resource set.

Further, the manner of determining the target identifier associated with the DCI may be set according to actual needs, for example, in an embodiment, before determining the control information of the physical uplink shared channel PUSCH transmission scheduled by the DCI according to the target identifier associated with the DCI, at least one of the following is further included:

mode 1, determining a target identifier associated with the DCI according to a control resource set identifier (CORESET pool index) associated with the DCI;

mode 2, determining a target identifier associated with the DCI according to first indication information carried by the DCI, wherein the first indication information is used for indicating the target identifier associated with the DCI;

mode 3, determining a target identifier associated with the DCI according to second indication information carried by the DCI, where the second indication information is used to indicate an activated trigger state (trigger state);

And 4, determining a target identifier associated with the DCI according to the SRI carried by the DCI.

In the embodiment of the present invention, with respect to the above mode 1, it may be understood that the target identifier associated with the DCI is indicated by the control resource set identifier associated with the DCI, in other words, the DCI only acts on the same target identifier. For example, in an embodiment, the DCI is not configured with a control resource set group identifier or the DCI is configured with a control resource set group identifier of 0, indicating that the DCI is associated with target identifier 1; the DCI configures a control resource set group identifier to be 1, indicating that the DCI is associated with a target identifier 2. In this embodiment, the object identifier only includes the object identifier 1 and the object identifier 2 as an example, and in other embodiments, a greater number of object identifiers may be configured.

With respect to the above embodiment 2, it can be understood that the target identifier is directly indicated in the DCI. Specifically, the location of the indication target identifier in the DCI may be set according to actual needs, for example, in an embodiment, an independent indication field may be added to indicate, or a bit may be added to an existing indication field to indicate.

In other words, in this embodiment, the first indication information is located in a first indication field or a second indication field of the DCI, where the first indication field is an independent indication field for indicating the target identifier, and the second indication field includes any one of the following:

A field (i.e., SRS request field) for activating aperiodic SRS resource set;

an SRI domain;

a TPMI field, which may include precoding information and a layer number (Precoding information and number of layers).

For example, in this embodiment, the target identifier may be indicated by adding 1 bit in SRS request field, SRI field or TPMI field. An example of adding 1 bit indication target identifier in SRS request field is described.

In this embodiment, SRS request field is typically 2 bits, indicating 4 states: 00. 01, 10 and 11, wherein 00 indicates no activation, 01 indicates activation trigger state1, 10 indicates activation trigger state2, and 11 indicates activation trigger state3. In the case of adding 1 bit to indicate the target identifier, the first indication information may include two states of 0 and 1, where when the first indication information is 0, the first indication information is used to indicate the target identifier 1; and when the first indication information is 1, the first indication information is used for indicating the target mark 2.

At this point, the indication of SRS request field can be understood as: 000 denotes that target identifier 1 is not activated, 001 denotes that target identifier 1 activates trigger state1, 010 denotes that target identifier 1 activates trigger state2, 011 denotes that target identifier 1 activates trigger state3, 100 denotes that target identifier 2 is not activated, 101 denotes that target identifier 2 activates trigger state1, 110 denotes that target identifier 2 activates trigger state2, and 111 denotes that target identifier 2 activates trigger state3.

Further, the DCI may carry the first indication information in a state that the target identifier is enabled. The target identification enable may be understood as a multi-target identification enable, that is, a multi-TRP enable. In other words, the first indication information is carried in the DCI only when the multi-TRP is enabled.

In the above manner 3, it should be noted that, when the target identifier associated with the DCI is determined according to the second indication information carried by the DCI, the association relationship between each trigger state and each target identifier is configured by a protocol convention, terminal reporting, or network device.

In this embodiment, SRS request field is typically 2 bits, indicating 4 states: 00. 01, 10 and 11, wherein 00 indicates no activation, 01 indicates activation trigger state1, 10 indicates activation trigger state2, and 11 indicates activation trigger state3. The association relationship that can be agreed by the protocol, reported by the terminal, or configured by the network device without adding bits may include: the trigger state1 is associated with the target identifier 1, and the trigger state2 and the trigger state3 are associated with the target identifier 2.

Further, in order to obtain more trigger states, the trigger states may be set to 3 bits. The SRS request field indication can be understood as: 000 denotes no activation, 001 denotes activation trigger state1, 010 denotes activation trigger state2, 011 denotes activation trigger state3, 100 denotes activation trigger state4, 101 denotes activation trigger state5, 110 denotes activation trigger state6, and 111 denotes activation trigger state7. Wherein, the association relationship may include: the trigger state1, the trigger state2 and the trigger state3 are associated with the target identifier 1, and the trigger state4, the trigger state5, the trigger state6 and the trigger state7 are associated with the target identifier 2. Of course, in other embodiments, other association groupings may be employed. For example, three target identifiers are associated with the trigger states 1-7, or two trigger states are associated with the target identifier 1, and 5 trigger states are associated with the target identifier 2. And are not listed here.

In the above-described mode 4, when the target identifier associated with the DCI is determined according to the sounding reference signal resource indicator SRI carried by the DCI, if the PUSCH transmission is a codebook-based transmission, one SRS resource is associated with each aperiodic SRS resource set.

In this embodiment, for codebook transmission, in the case of multiple TRP, only 1 SRS resource is supported in the SRS resource set. Each object identifier allows configuration of at most one SRS resource set-the associated SRS resource IDs in the SRS resource sets associated with different object identifiers are different. Wherein, SRI is used for indicating SRS resource set.

It should be understood that when joint indication is performed in at least two ways of ways 1 to 4, each way indicates that the target identity associated with the same DCI should be the same.

Further, the method further comprises:

and receiving target information, wherein the target information is used for configuring or indicating enabling information, and the enabling information comprises target identification enabling or target identification disabling.

In this embodiment, target identification enabling or disabling may be understood as multi-TRP enabling or disabling. When the target identity is enabled, the terminal may transmit PUSCH to at least two TRPs simultaneously or time-division. When the target identity is enabled, the terminal can transmit PUSCH to only one TRP. Specifically, the target information may be received before receiving the DCI, and the enable information may be configured or indicated. Alternatively, the network device may indicate whether the UE multi-TRP is enabled or disabled through a medium access control element (Medium Access Control Control Element, MAC CE) and/or radio resource control (Radio Resource Control, RRC) signaling.

In an embodiment, the enabling or disabling may be activated separately. In another embodiment, the TRP may be configured by RRC, including configuring a plurality of TRP numbers, etc., and enabled by MAC CE activation or deactivation. Wherein deactivation enabling may be understood as disabling.

In order that the invention may be better understood, a detailed description of the practice of the invention will be given below by way of specific examples.

For each of the codebook, non-codebook, beam management, and antenna switching scenarios, a plurality of aperiodic SRS resource sets may be supported, and each target identity (e.g., TRP identity or association information, hereinafter illustrated with TRP identity as an example) corresponds to at least one aperiodic SRS resource set. The power control parameters of the two aperiodic SRS resource sets may not be identical.

Alternatively, the method for obtaining the TRP identifier associated with the aperiodic SRS resource set may be by the TRP identifier contained in the aperiodic SRS resource set or spatial relation info of the RS associated with the aperiodic SRS resource set.

The following methods 1 to 6 may be employed for the determination of the TRP identification associated with DCI.

Method 1: the TRP identification is obtained by controlling the resource set identification.

Optionally, the associated TRP identification of the DCI is indicated by a control resource set group identification associated with the DCI. I.e. the DCI acts only on the same TRP identity. I.e. not configured with a control resource set group identity or a control resource set group identity equal to 0 represents the DCI associated TRP identity 1 and a control resource set group identity equal to 1 represents the DCI associated TRP identity 2.

Method 2: the DCI directly carries the TRP ID field.

Method 3: the 1bit is added in the domain for activating the aperiodic SRS resource set, the SRI domain or the TPMI domain in the DCI for indicating the associated TRP identification.

Method 4: the domain for activating aperiodic SRS resource set, SRI domain or TPMI domain in DCI increases 1bit for indicating the associated TRP identity only when multi-TRP is enabled.

Method 5: and indirectly obtaining the TRP identifier associated with the DCI through the trigger state.

When DCI cannot directly obtain the associated TRP identifier, grouping the trigger states, wherein the trigger states in the group are associated with the same TRP identifier, and grouping method protocol convention, terminal reporting or network configuration is carried out through MAC CE or RRC. Wherein the trigger states between groups may not be identical.

Alternatively, in one embodiment, SRS request field is typically 2 bits without adding a trigger state, indicating 4 states: 00. 01, 10 and 11, wherein 00 indicates no activation, 01 indicates activation trigger state1, 10 indicates activation trigger state2, and 11 indicates activation trigger state3. The trigger state1 and trigger state2 and trigger state3 can be configured to be associated with the target identifier 1 and the target identifier 2. That is to say: the 00 mark is not activated; 01, associating a target identifier 1, and activating trigger state1;10 represents an associated target identifier 2, and trigger state2 is activated; 11 denotes the associated target identity 2 and trigger state3 is activated.

Alternatively, in another embodiment, the number of trigger states is increased, and the overhead of SRS request field is correspondingly increased. At this time, SRS request field is 3 bits, indicating 8 states, where 000 indicates no activation, 001 indicates activation trigger state1, 010 indicates activation trigger state2, 011 indicates activation trigger state3, 100 indicates activation trigger state4, 101 indicates activation trigger state5, 110 indicates activation trigger state6, and 111 indicates activation trigger state7. Optionally, trigger state1, trigger state2, and trigger state3 may be associated with target identifier 1, and trigger state4, trigger state5, trigger state6, and trigger state7 may be associated with target identifier 2.

Method 6: the TRP identification associated with the DCI is obtained through the SRI.

Alternatively, for codebook transmission, in the case of multiple TRPs, only 1 SRS resource is supported in association in the aperiodic SRS resource set. Each TPR identification allows configuration of at most one aperiodic SRS resource set. Different TRPs identify different associated SRS reference IDs in the associated SRS reference set.

Wherein the SRI is used to indicate an aperiodic SRS resource set.

It should be noted that, the network device may instruct, through MAC CE and/or RRC signaling, whether the UE network side multi-TRP is enabled or disabled. For example, may include a separate activation enable or deactivation enable, or may be configured by RRC and activated or deactivated by MAC CE. Wherein the RRC configuration includes configuring a plurality of TRP numbers, etc.

Alternatively, for the above methods 1 to 6, at least one of the SRI field, TPMI field, redundancy version field, power control field, antenna port field, SRS request field, CSI request field of the plurality of DCIs may be configured to different values. And each domain needs to be interpreted according to the corresponding configuration of the TRP identity triggering the corresponding uplink transmission.

In this embodiment, only when the target identifier associated with the aperiodic SRS resource set coincides with the target identifier associated with the DCI for activating the aperiodic SRS resource set, the target indication field (for example SRS request field) in the DCI may be used to activate the aperiodic SRS resource set.

When the network device does not enable the multi-TRP, the UE demodulates the data according to the normal DCI size (size). If the network equipment is enabled, the UE demodulates according to the DCI size of the multi-TRP.

The following describes increasing the number of aperiodic SRS resource sets.

For the codebook or non-codebook, at most two aperiodic SRS resource sets are supported, and if two aperiodic SRS resource sets are configured, the two aperiodic SRS resource sets are associated with different TRP identifiers.

The following cases are included for antenna switching.

1. With respect to 1 transmit 2 receive (1T 2R). Optionally, up to 4 SRS resource sets are configured. Wherein each TRP identity is associated with a maximum of 2 SRS resource sets. Within the single TRP identity are the following features:

Each SRS resource set has a different resource Type (resource Type), i.e. the period is different;

collocation is periodic/semi-persistent + non-periodic;

2 SRS resources are configured for each SRS resource set;

within one SRS resource set, each SRS resource contains 1 port;

within one SRS resource set, each SRS resource needs to be transmitted on a different symbol (symbol);

in one SRS resource set, the UE transmits different SRS resources using different UE antenna ports (physical antennas);

i.e., 1 different physical antenna for each port in SRS resource.

2. With respect to 2T4R. Optionally, up to 4 SRS resource sets are configured. Wherein each TRP identity is associated with a maximum of 2 SRS resource sets. Within the single TRP identity are the following features:

collocation is periodic/semi-persistent + non-periodic;

2 SRS resources are configured for each SRS resource set;

within one SRS resource set, each SRS resource contains 2 ports;

within one SRS resource set, each SRS resource needs to be transmitted on a different symbol;

one resource is transmitted from two UE antenna ports (physical antennas) and the other resource is transmitted from the other two UE antenna ports (physical antennas) within one SRS resource set. Wherein each SRS resource corresponds to 2 different physical antennas and the port in each SRS resource corresponds to 1 different physical antenna.

3. With respect to 1T4R. Optionally, 2 SRS resource sets are configured at most. Wherein each TRP identity is associated with at most 1 SRS resource set. Within the single TRP identity are the following features:

configuration 0 or 1 SRS resource set (configuration 0 means that the network device does not instruct the UE to enable the configuration);

the resourceType only supports periodic or semi-persistent;

for 1T2R and 2T4R, a maximum of 2 SRS resource sets are arranged, and the case where 0 SRS resource sets are included is not limited to the combination of periodic/semi-continuous/aperiodic SRS resource sets;

for 1T4R, periodic/semi-persistent forcing can only configure one SRS resource set;

configuring 4 SRS resources;

each SRS resource contains 1 port;

each SRS resource needs to be transmitted on a different symbol;

the UE transmits different SRS resources using different UE antenna ports (physical antennas), i.e. a port in each SRS resource corresponds to a different physical antenna.

4. Regarding 1T4R, optionally, a maximum of 4 SRS resource sets are configured, with 2 SRS resource sets associated with each TRP identity. Within the single TRP identity are the following features:

configuring 0 or 2 SRS resource sets;

the resourceType only supports aperiodicity;

The two SRS resource sets are configured with 4 SRS resources in total;

each SRS resource contains 1 port;

the SRS resources respectively configured in the two SRS resource sets are 2+2 or 1+3 or 3+1;

the values of alpha, p0, pathloss reference RS and SRS-PowerControlAdjust states in the two SRS resource sets remain consistent;

the values of the apeeriodics SRS-resourceTrigger or the apeeriodics SRS-resourceTriggerList of the two SRS resource sets are kept consistent;

i.e., triggered simultaneously by one DCI;

each SRS resource set needs to be transmitted on two different slots (slots).

5. With respect to 1T1R, 2T2R, and 4T4R. Optionally, up to 4 SRS resource sets are configured, and each TRP identification is associated with up to 2 SRS resource sets. Within the single TRP identity are the following features:

configuring 2 SRS resource sets at most;

each SRS resource set configures 1 SRS resource;

the number of SRS ports in each resource is equal to 1/2/4 and the number of the SRS ports is equal to the number of the transmitting antennas.

Referring to fig. 3, fig. 3 is a flowchart of another transmission control method according to an embodiment of the present invention, where the method is applied to a network device, as shown in fig. 3, and includes the following steps:

step 301, downlink control information DCI is sent to a terminal, where the DCI is used for the terminal to determine control information of PUSCH transmission of a physical uplink shared channel scheduled by the DCI according to a target identifier associated with the DCI.

Optionally, the DCI satisfies at least one of:

the DCI is associated with a control resource set identifier, and the control resource set identifier is used for determining the target identifier;

the DCI carries first indication information, and the first indication information is used for indicating a target identifier associated with the DCI;

the DCI carries second indication information, wherein the second indication information is used for determining the target identifier and is used for indicating the activated triggering state;

the DCI carries a SRI (sounding reference signal resource indicator), and the SRI is used for determining the target identifier.

Optionally, the first indication information is located in a first indication domain or a second indication domain of the DCI, where the first indication domain is an independent indication domain for indicating the target identifier, and the second indication domain includes any one of the following:

a field for activating an aperiodic sounding reference signal, SRS, resource set;

an SRI domain;

the transmit precoding matrix indicates the TPMI domain.

Optionally, in the case that the target identifier is enabled, the DCI carries the first indication information.

Optionally, under the condition that the DCI carries the second indication information, a protocol convention, terminal reporting or network equipment configures association relations between each trigger state and each target identifier.

Optionally, if the DCI carries the SRI, if the PUSCH transmission is a codebook-based transmission, each aperiodic SRS resource set is associated with one SRS resource.

Optionally, the method further comprises:

and sending target information to the terminal, wherein the target information is used for configuring or indicating enabling information, and the enabling information comprises target identification enabling or target identification disabling.

It should be noted that, in this embodiment, as a implementation manner of the network device corresponding to the embodiment shown in fig. 2, a specific implementation manner of the network device may refer to the description related to the embodiment shown in fig. 2, and achieve the same beneficial effects, and in order to avoid repeated descriptions, no further description is given here.

Referring to fig. 4, fig. 4 is a block diagram of a terminal according to an embodiment of the present invention, and as shown in fig. 4, a terminal 400 includes:

a receiving module 401, configured to receive downlink control information DCI;

a determining module 402, configured to determine control information of PUSCH transmission of the physical uplink shared channel scheduled by the DCI according to the target identifier associated with the DCI.

Optionally, the terminal 400 further includes a determining module, configured to perform at least one of:

determining a target identifier associated with the DCI according to the control resource set identifier associated with the DCI;

Determining a target identifier associated with the DCI according to first indication information carried by the DCI, wherein the first indication information is used for indicating the target identifier associated with the DCI;

determining a target identifier associated with the DCI according to second indication information carried by the DCI, wherein the second indication information is used for indicating an activated triggering state;

and determining a target identifier associated with the DCI according to the SRI carried by the DCI.

an SRI domain;

the transmit precoding matrix indicates the TPMI domain.

Optionally, under the condition that the target identifier associated with the DCI is determined according to the second indication information carried by the DCI, the association relation between each trigger state and each target identifier is configured by protocol convention, terminal reporting or network equipment.

Optionally, in the case that the target identifier associated with the DCI is determined according to the SRI indicated by the sounding reference signal resource carried by the DCI, if the PUSCH transmission is a codebook-based transmission, each aperiodic SRS resource set is associated with one SRS resource.

Optionally, the receiving module 401 is further configured to receive target information, where the target information is used to configure or indicate enabling information, and the enabling information includes target identifier enabling or target identifier disabling.

Optionally, in a case that the control information includes indication information for activating an SRS resource set, after determining, according to the target identifier associated with the DCI, control information of PUSCH transmission of a physical uplink shared channel scheduled by the DCI, the method further includes:

Optionally, the receiving module 401 is further configured to receive configuration information, where the configuration information is used to configure at least one aperiodic SRS resource set, and each target identifier is associated with at least one aperiodic SRS resource set.

Optionally, the set identities of the aperiodic SRS resource sets associated with different target identities are different.

Optionally, the control information includes indication information of a third indication field in the DCI, where the third indication field includes at least one of an SRI field, a TPMI field, a redundancy version field, a power control field, an antenna port field, an SRS request field, and a CSI request field.

The terminal provided by the embodiment of the present invention can implement each process implemented by the terminal in the method embodiment of fig. 2, and in order to avoid repetition, a description is omitted here.

Referring to fig. 5, fig. 5 is a block diagram of a network device according to an embodiment of the present invention, and as shown in fig. 5, a network device 500 includes:

a sending module 501, configured to send configuration information to the terminal, where the configuration information is used to configure at least one aperiodic SRS resource set, and each target identifier is associated with at least one aperiodic SRS resource set.

Optionally, the DCI satisfies at least one of:

an SRI domain;

the transmit precoding matrix indicates the TPMI domain.

Optionally, the sending module 501 is further configured to: and sending target information to the terminal, wherein the target information is used for configuring or indicating enabling information, and the enabling information comprises target identification enabling or target identification disabling.

The network device provided in the embodiment of the present invention can implement each process implemented by the network device in the method embodiment of fig. 3, and in order to avoid repetition, a description is omitted here.

Figure 6 is a schematic diagram of a hardware architecture of a terminal implementing various embodiments of the present invention,

the terminal 600 includes, but is not limited to: radio frequency unit 601, network module 602, audio output unit 603, input unit 604, sensor 605, display unit 606, user input unit 607, interface unit 608, memory 609, processor 610, and power supply 611. It will be appreciated by those skilled in the art that the terminal structure shown in fig. 6 is not limiting of the terminal and that the terminal may include more or fewer components than shown, or may combine certain components, or a different arrangement of components. In the embodiment of the invention, the terminal comprises, but is not limited to, a mobile phone, a tablet computer, a notebook computer, a palm computer, a vehicle-mounted terminal, a wearable device, a pedometer and the like.

A radio frequency unit 601, configured to receive downlink control information DCI;

and a processor 610, configured to determine control information of PUSCH transmission of the physical uplink shared channel scheduled by the DCI according to the target identifier associated with the DCI.

It should be understood that, in this embodiment, the processor 610 and the radio frequency unit 601 can implement each process implemented by the terminal in the method embodiment of fig. 2, and in order to avoid repetition, a description is omitted here.

It should be understood that, in the embodiment of the present invention, the radio frequency unit 601 may be used to receive and send information or signals during a call, specifically, receive downlink data from a base station, and then process the downlink data with the processor 610; and, the uplink data is transmitted to the base station. Typically, the radio frequency unit 601 includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, and the like. In addition, the radio frequency unit 601 may also communicate with networks and other devices through a wireless communication system.

The terminal provides wireless broadband internet access to the user via the network module 602, such as helping the user to send and receive e-mail, browse web pages, access streaming media, etc.

The audio output unit 603 may convert audio data received by the radio frequency unit 601 or the network module 602 or stored in the memory 609 into an audio signal and output as sound. Also, the audio output unit 603 may also provide audio output (e.g., a call signal reception sound, a message reception sound, etc.) related to a specific function performed by the terminal 600. The audio output unit 603 includes a speaker, a buzzer, a receiver, and the like.

The input unit 604 is used for receiving audio or video signals. The input unit 604 may include a graphics processor (Graphics Processing Unit, GPU) 6041 and a microphone 6042, the graphics processor 6041 processing image data of still pictures or video obtained by an image capturing apparatus (such as a camera) in a video capturing mode or an image capturing mode. The processed image frames may be displayed on the display unit 606. The image frames processed by the graphics processor 6041 may be stored in the memory 609 (or other storage medium) or transmitted via the radio frequency unit 601 or the network module 602. Microphone 6042 may receive sound and can process such sound into audio data. The processed audio data may be converted into a format output that can be transmitted to the mobile communication base station via the radio frequency unit 601 in the case of a telephone call mode.

The terminal 600 also includes at least one sensor 605, such as a light sensor, a motion sensor, and other sensors. Specifically, the light sensor includes an ambient light sensor and a proximity sensor, wherein the ambient light sensor can adjust the brightness of the display panel 6061 according to the brightness of ambient light, and the proximity sensor can turn off the display panel 6061 and/or the backlight when the terminal 600 moves to the ear. As one of the motion sensors, the accelerometer sensor can detect the acceleration in all directions (generally three axes), and can detect the gravity and direction when the accelerometer sensor is stationary, and can be used for recognizing the terminal gesture (such as horizontal and vertical screen switching, related games, magnetometer gesture calibration), vibration recognition related functions (such as pedometer and knocking), and the like; the sensor 605 may also include a fingerprint sensor, a pressure sensor, an iris sensor, a molecular sensor, a gyroscope, a barometer, a hygrometer, a thermometer, an infrared sensor, etc., which are not described herein.

The display unit 606 is used to display information input by a user or information provided to the user. The display unit 606 may include a display panel 6061, and the display panel 6061 may be configured in the form of a liquid crystal display (Liquid Crystal Display, LCD), an Organic Light-Emitting Diode (OLED), or the like.

The user input unit 607 may be used to receive input numeric or character information and to generate key signal inputs related to user settings and function control of the terminal. Specifically, the user input unit 607 includes a touch panel 6071 and other input devices 6072. Touch panel 6071, also referred to as a touch screen, may collect touch operations thereon or thereabout by a user (e.g., operations of the user on touch panel 6071 or thereabout using any suitable object or accessory such as a finger, stylus, or the like). The touch panel 6071 may include two parts of a touch detection device and a touch controller. The touch detection device detects the touch azimuth of a user, detects a signal brought by touch operation and transmits the signal to the touch controller; the touch controller receives touch information from the touch detection device and converts it into touch point coordinates, which are then sent to the processor 610, and receives and executes commands sent from the processor 610. In addition, the touch panel 6071 may be implemented in various types such as resistive, capacitive, infrared, and surface acoustic wave. The user input unit 607 may include other input devices 6072 in addition to the touch panel 6071. Specifically, other input devices 6072 may include, but are not limited to, a physical keyboard, function keys (e.g., volume control keys, switch keys, etc.), a track ball, a mouse, and a joystick, which are not described herein.

Further, the touch panel 6071 may be overlaid on the display panel 6061, and when the touch panel 6071 detects a touch operation thereon or thereabout, the touch operation is transmitted to the processor 610 to determine a type of a touch event, and then the processor 610 provides a corresponding visual output on the display panel 6061 according to the type of the touch event. Although in fig. 6, the touch panel 6071 and the display panel 6061 are two independent components to implement the input and output functions of the terminal, in some embodiments, the touch panel 6071 and the display panel 6061 may be integrated to implement the input and output functions of the terminal, which is not limited herein.

The interface unit 608 is an interface to which an external device is connected to the terminal 600. For example, the external devices may include a wired or wireless headset port, an external power (or battery charger) port, a wired or wireless data port, a memory card port, a port for connecting a device having an identification module, an audio input/output (I/O) port, a video I/O port, an earphone port, and the like. The interface unit 608 may be used to receive input (e.g., data information, power, etc.) from an external device and transmit the received input to one or more elements within the terminal 600 or may be used to transmit data between the terminal 600 and an external device.

The memory 609 may be used to store software programs as well as various data. The memory 609 may mainly include a storage program area that may store an operating system, an application program required for at least one function (such as a sound playing function, an image playing function, etc.), and a storage data area; the storage data area may store data (such as audio data, phonebook, etc.) created according to the use of the handset, etc. In addition, the memory 609 may include high speed random access memory, and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other volatile solid state storage device.

The processor 610 is a control center of the terminal, connects various parts of the entire terminal using various interfaces and lines, and performs various functions of the terminal and processes data by running or executing software programs and/or modules stored in the memory 609 and calling data stored in the memory 609, thereby performing overall monitoring of the terminal. The processor 610 may include one or more processing units; preferably, the processor 610 may integrate an application processor that primarily handles operating systems, user interfaces, applications, etc., with a modem processor that primarily handles wireless communications. It will be appreciated that the modem processor described above may not be integrated into the processor 610.

The terminal 600 may further include a power supply 611 (e.g., a battery) for supplying power to the respective components, and preferably, the power supply 611 may be logically connected to the processor 610 through a power management system, so that functions of managing charging, discharging, and power consumption management are performed through the power management system.

In addition, the terminal 600 includes some functional modules, which are not shown, and will not be described herein.

Preferably, the embodiment of the present invention further provides a terminal, which includes a processor 610, a memory 609, and a computer program stored in the memory 609 and capable of running on the processor 610, where the computer program when executed by the processor 610 implements each process of the foregoing embodiment of the transmission control method, and the same technical effects can be achieved, and for avoiding repetition, a detailed description is omitted herein.

Referring to fig. 7, fig. 7 is a block diagram of another network device according to an embodiment of the present invention, and as shown in fig. 7, the network device 700 includes: a processor 701, a transceiver 702, a memory 703 and a bus interface, wherein:

and a transceiver 702, configured to send downlink control information DCI to a terminal, where the DCI is used for the terminal to determine control information of PUSCH transmission of a physical uplink shared channel scheduled by the DCI according to a target identifier associated with the DCI.

It should be understood that, in this embodiment, the processor 701 and the transceiver 702 can implement the respective processes implemented by the network device in the method embodiment of fig. XX, and are not described herein again for avoiding repetition.

In fig. 7, a bus architecture may be comprised of any number of interconnected buses and bridges, and in particular, one or more processors represented by the processor 701 and various circuits of memory represented by the memory 703. The bus architecture may also link together various other circuits such as peripheral devices, voltage regulators, power management circuits, etc., which are well known in the art and, therefore, will not be described further herein. The bus interface provides an interface. The transceiver 702 may be a number of elements, i.e., including a transmitter and a receiver, providing a means for communicating with various other apparatus over a transmission medium. The user interface 704 may also be an interface capable of interfacing with an inscribed desired device for a different user device, including but not limited to a keypad, display, speaker, microphone, joystick, etc.

The processor 701 is responsible for managing the bus architecture and general processing, and the memory 703 may store data used by the processor 701 in performing operations.

Preferably, the embodiment of the present invention further provides a network device, which includes a processor 701, a memory 703, and a computer program stored in the memory 703 and capable of running on the processor 701, where the computer program when executed by the processor 701 implements each process of the foregoing transmission control method embodiment, and the same technical effects can be achieved, and for avoiding repetition, a description is omitted herein.

The embodiment of the invention also provides a computer readable storage medium, on which a computer program is stored, where the computer program when executed by a processor implements each process of the transmission control method embodiment of the network device side provided by the embodiment of the invention, or when executed by a processor implements each process of the transmission control method embodiment of the terminal side provided by the embodiment of the invention, and the same technical effects can be achieved, so that repetition is avoided and no further description is provided herein. Wherein the computer readable storage medium is selected from Read-Only Memory (ROM), random access Memory (Random Access Memory, RAM), magnetic disk or optical disk.

It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.

From the above description of the embodiments, it will be clear to those skilled in the art that the above-described embodiment method may be implemented by means of software plus a necessary general hardware platform, but of course may also be implemented by means of hardware, but in many cases the former is a preferred embodiment. Based on such understanding, the technical solution of the present invention may be embodied essentially or in a part contributing to the prior art in the form of a software product stored in a storage medium (e.g. ROM/RAM, magnetic disk, optical disk) comprising instructions for causing a terminal (which may be a mobile phone, a computer, a server, an air conditioner, or a base station, etc.) to perform the method according to the embodiments of the present invention.

The embodiments of the present invention have been described above with reference to the accompanying drawings, but the present invention is not limited to the above-described embodiments, which are merely illustrative and not restrictive, and many forms may be made by those having ordinary skill in the art without departing from the spirit of the present invention and the scope of the claims, which are to be protected by the present invention.

Claims

1. A transmission control method applied to a terminal, comprising:

receiving downlink control information DCI;

determining control information of Physical Uplink Shared Channel (PUSCH) transmission scheduled by the DCI according to the target identifier associated with the DCI; the target identifier is a TRP identifier or associated information corresponding to the TRP one by one;

in the case that the control information includes indication information for activating an SRS resource set, after determining, according to the target identifier associated with the DCI, control information of PUSCH transmission of a physical uplink shared channel scheduled by the DCI, the method further includes:

activating an aperiodic SRS resource set associated with the target identity;

before the downlink control information DCI is received, the method further includes:

receiving configuration information, wherein the configuration information is used for configuring at least one aperiodic SRS resource set, and each target identifier is associated with the at least one aperiodic SRS resource set;

the set identities of the aperiodic SRS resource sets associated with different ones of the target identities are different.

2. The method of claim 1, wherein the determining control information for the DCI scheduled physical uplink shared channel PUSCH transmission based on the target identification associated with the DCI further comprises at least one of:

3. The method of claim 2, wherein the first indication information is located in a first indication field or a second indication field of the DCI, the first indication field being an independent indication field for indicating the target identity, the second indication field comprising any one of:

an SRI domain;

the transmit precoding matrix indicates the TPMI domain.

4. The method of claim 2, wherein the DCI carries the first indication information if a target identity is enabled.

5. The method of claim 2, wherein, in the case of determining the target identifier associated with the DCI according to the second indication information carried by the DCI, an association relationship between each trigger state and each target identifier is configured by a protocol convention, a terminal report, or a network device.

6. The method of claim 2, wherein if the target identity associated with the DCI is determined according to a sounding reference signal resource indicator SRI carried by the DCI, each aperiodic SRS resource set is associated with one SRS resource if the PUSCH transmission is a codebook-based transmission.

7. The method according to claim 1, wherein the method further comprises:

8. The method of claim 1, wherein a target identifier associated with a target set of aperiodic SRS resources in a target indication field of the DCI for activating the target set of aperiodic SRS resources in the at least one aperiodic SRS resource set is the same as a target identifier associated with the DCI, the target indication field being a field for activating the set of aperiodic SRS resources.

9. The method of claim 1, wherein the control information comprises indication information of a third indication field in the DCI, the third indication field comprising at least one of an SRI field, a TPMI field, a redundancy version field, a power control field, an antenna port field, an SRS request field, and a CSI request field.

10. A transmission control method applied to a network device, comprising:

transmitting Downlink Control Information (DCI) to a terminal, wherein the DCI is used for the terminal to determine control information of Physical Uplink Shared Channel (PUSCH) transmission scheduled by the DCI according to a target identifier associated with the DCI; the target identifier is a TRP identifier or associated information corresponding to the TRP one by one;

the control information includes indication information for activating an SRS resource set;

before the downlink control information DCI is sent to the terminal, the method further includes:

transmitting configuration information to the terminal, wherein the configuration information is used for configuring at least one aperiodic SRS resource set, and each target identifier is associated with at least one aperiodic SRS resource set;

11. The method of claim 10, wherein the DCI satisfies at least one of:

12. The method of claim 11, wherein the first indication information is located in a first indication field or a second indication field of the DCI, the first indication field being an independent indication field for indicating the target identity, the second indication field comprising any one of:

an SRI domain;

the transmit precoding matrix indicates the TPMI domain.

13. The method of claim 11, wherein the DCI carries the first indication information if a target identity is enabled.

14. The method of claim 11, wherein, in the case that the DCI carries the second indication information, an association between each trigger state and each target identifier is configured by a protocol convention, a terminal reporting, or a network device.

15. The method of claim 11, wherein if the PUSCH transmission is a codebook-based transmission, if the DCI carries the SRI, then each set of aperiodic SRS resources is associated with one SRS resource.

16. The method according to claim 10, wherein the method further comprises:

17. The method of claim 10, wherein a target identity associated with a target set of aperiodic SRS resources is the same as a target identity associated with the DCI in a target indication field of the DCI for activating the target set of aperiodic SRS resources in the at least one set of aperiodic SRS resources, the target indication field being a field for activating the set of aperiodic SRS resources.

18. The method of claim 10, wherein the control information comprises indication information of a third indication field in the DCI, the third indication field comprising at least one of an SRI field, a TPMI field, a redundancy version field, a power control field, an antenna port field, an SRS request field, and a CSI request field.

19. A terminal, comprising:

a receiving module, configured to receive downlink control information DCI;

a determining module, configured to determine control information of PUSCH transmission of a physical uplink shared channel scheduled by the DCI according to a target identifier associated with the DCI; the target identifier is a TRP identifier or associated information corresponding to the TRP one by one;

In the case that the control information includes indication information for activating an SRS resource set, after determining, according to the target identifier associated with the DCI, control information for PUSCH transmission of the physical uplink shared channel scheduled by the DCI, the method further includes:

activating an aperiodic SRS resource set associated with the target identity;

the receiving module is further configured to receive configuration information, where the configuration information is used to configure at least one aperiodic SRS resource set, and each target identifier is associated with at least one aperiodic SRS resource set;

20. A network device, comprising:

a sending module, configured to send downlink control information DCI to a terminal, where the DCI is used for the terminal to determine control information of PUSCH transmission scheduled by the DCI according to a target identifier associated with the DCI;

the target identifier is a TRP identifier or associated information corresponding to the TRP one by one; the control information includes indication information for activating an SRS resource set;

the sending module is further configured to: transmitting configuration information to the terminal, wherein the configuration information is used for configuring at least one aperiodic SRS resource set, and each target identifier is associated with at least one aperiodic SRS resource set;

21. A terminal, comprising: a memory, a processor, and a program stored on the memory and executable on the processor, which when executed by the processor, implements the steps in the transmission control method according to any one of claims 1 to 9.

22. A network device, comprising: memory, a processor and a program stored on the memory and executable on the processor, which when executed by the processor, implements the steps in the transmission control method according to any one of claims 10 to 18.

23. A computer-readable storage medium, on which a computer program is stored, which when executed by a processor implements the steps of the transmission control method according to any one of claims 1 to 18.