CN111756506A - Method and communication device for transmitting uplink information - Google Patents

Method and communication device for transmitting uplink information Download PDF

Info

Publication number
CN111756506A
CN111756506A CN201910252637.2A CN201910252637A CN111756506A CN 111756506 A CN111756506 A CN 111756506A CN 201910252637 A CN201910252637 A CN 201910252637A CN 111756506 A CN111756506 A CN 111756506A
Authority
CN
China
Prior art keywords
pusch
channel
uplink data
uplink
time
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Withdrawn
Application number
CN201910252637.2A
Other languages
Chinese (zh)
Inventor
胡丹
官磊
李胜钰
马蕊香
邵家枫
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Priority to CN201910252637.2A priority Critical patent/CN111756506A/en
Priority to PCT/CN2020/081620 priority patent/WO2020200078A1/en
Publication of CN111756506A publication Critical patent/CN111756506A/en
Withdrawn legal-status Critical Current

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00Arrangements affording multiple use of the transmission path
    • H04L5/003Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053Allocation of signaling, i.e. of overhead other than pilot signals
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00Arrangements affording multiple use of the transmission path
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00Arrangements affording multiple use of the transmission path
    • H04L5/003Arrangements for allocating sub-channels of the transmission path
    • H04L5/0058Allocation criteria
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W72/00Local resource management
    • H04W72/04Wireless resource allocation
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W72/00Local resource management
    • H04W72/50Allocation or scheduling criteria for wireless resources
    • H04W72/53Allocation or scheduling criteria for wireless resources based on regulatory allocation policies
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W72/00Local resource management
    • H04W72/50Allocation or scheduling criteria for wireless resources
    • H04W72/56Allocation or scheduling criteria for wireless resources based on priority criteria

Abstract

The application provides a method and a communication device for transmitting uplink information, which can multiplex UCI on a PUSCH for transmission, thereby improving the reliability of transmission and improving the system efficiency. Specifically, when the time-frequency resource of the PUCCH carrying the UCI overlaps with the time-frequency resources of the multiple PUSCHs carrying the same transport block in the time domain, the terminal device carries the UCI on a first PUSCH and transmits the UCI, where the first PUSCH meets the timeline condition that the UCI is multiplexed on the PUSCH among the multiple PUSCHs for transmission.

Description

Method and communication device for transmitting uplink information
Technical Field
The present application relates to the field of communications, and in particular, to a method and a communications apparatus for transmitting uplink information.
Background
When performing uplink transmission in a communication system, it may happen that a Physical Uplink Control Channel (PUCCH) transmission and at least one Physical Uplink Shared Channel (PUSCH) transmission carrying the same Transport Block (TB) are configured in one slot (slot) at the same time. If the PUCCH overlaps with the at least one PUSCH in the time domain, how to transmit Uplink Control Information (UCI) carried on the PUCCH or PUCCH needs to be further discussed.
Disclosure of Invention
The application provides a method and a communication device for transmitting uplink information, which can multiplex uplink control information on an uplink data channel for transmission, thereby improving the reliability of transmission and improving the system efficiency.
In a first aspect, a method for transmitting uplink information is provided, where the method may be performed by a terminal device or a module (e.g., a chip) in the terminal device.
The method comprises the following steps: determining a first time-frequency resource and uplink control information carried on an uplink control channel to be sent on the first time-frequency resource; and determining a second time-frequency resource and N uplink data channels to be sent on the second time-frequency resource, wherein the N uplink data channels bear the same transmission block, and N is an integer greater than 1. And under the condition that the first time-frequency resource and the second time-frequency resource are overlapped on a time domain, if an uplink data channel meeting a first condition exists in the N uplink data channels, carrying the uplink control information on a first target channel for transmission. The first target channel is an uplink data channel satisfying a first condition among the N uplink data channels, and the first condition is a timeline condition that uplink control information is multiplexed on the uplink data channel for transmission.
Therefore, based on the method for transmitting uplink information provided by the present application, as long as there is an uplink data channel satisfying the timeline condition that uplink control information is multiplexed and transmitted on the uplink data channel among the N uplink data channels, and all uplink data channels are not required to satisfy the timeline condition, the uplink control information that is carried on the uplink control channel can be transmitted on the uplink data channel satisfying the timeline condition that uplink control information is multiplexed and transmitted on the uplink data channel. Therefore, the problem that the uplink control information is discarded in the prior art can be solved, so that the transmission reliability can be improved, and the system efficiency can be improved. In addition, since retransmission scheduling of the uplink control information is not required, the scheduling signaling overhead can be reduced.
It should be understood that "a" and "B" described in this application overlap in the time domain or "a" and "B" overlap may include both cases where "a" and "B" partially overlap in the time domain and where "a" and "B" completely overlap in the time domain. That is, whether "a" and "B" completely overlap in the time domain or "a" and "B" partially overlap in the time domain, the method provided by the present application may be employed.
In this application, the time line condition that the uplink control information is multiplexed and transmitted on the uplink data channel, that is, the first condition, refers to: (1) a time interval between a first Orthogonal Frequency Division Multiplexing (OFDM) symbol of a temporally earliest one of an uplink control channel and an uplink data channel, which are overlapped in a time domain, and an end time of the downlink data channel is not less than a first threshold. Any one of the uplink data channel and the uplink control channel corresponds to the downlink data channel, that is, the uplink control channel or the uplink data channel carries feedback information of the downlink data channel. (2) And the time interval between the first OFDM symbol of the earliest channel in time in the uplink control channel and the uplink data channel which are overlapped in the time domain and the end time of the downlink control channel is not less than a second threshold. Wherein, any one of the uplink data channel and the uplink control channel corresponds to the downlink control channel, and the corresponding meaning here is: the downlink control channel schedules a downlink data channel, and the uplink control channel or the uplink data channel carries feedback information of the downlink data channel; or, the downlink control channel schedules uplink data channel transmission. In the above, the first threshold may be N1+ X OFDM symbols, and the second threshold may be N2+ Y OFDM symbols. N1 represents the processing time of the downlink data channel by the terminal device, that is, the time for the terminal device to demodulate and decode the downlink data channel and generate feedback information to prepare for transmission after receiving the downlink data channel. N2 represents the preparation time of the uplink data channel by the terminal device, i.e. the time when the terminal device demodulates and decodes the signaling and prepares to send the uplink data channel packet according to the signaling after receiving the scheduling information of the uplink data channel. X and Y are pre-configured, pre-defined or network device indicated OFDM symbol numbers. It should be understood that if the uplink control channel or the uplink data channel needs to be scheduled or activated by the downlink control channel, the uplink control channel and the uplink data channel need to satisfy the above two conditions at the same time. If the uplink control channel or the uplink data channel is scheduling-free or activation-free, only the first condition needs to be satisfied.
With reference to the first aspect, in certain implementations of the first aspect, there is also an uplink data channel that does not satisfy the first condition among the N uplink data channels.
Based on the scheme, in a scenario that there are both uplink data channels that do not satisfy the first condition and uplink data channels that satisfy the first condition in the N uplink data channels, the uplink control information may be carried on the uplink data channels that satisfy the first condition for transmission. Therefore, the problem that the uplink control information or the uplink control channel is discarded as long as the N uplink data channels do not meet the first condition in the prior art can be solved, so that the transmission reliability can be improved, and the system efficiency can be improved. In addition, since retransmission scheduling of the uplink control information is not required, the scheduling signaling overhead can be reduced.
With reference to the first aspect, in some implementations of the first aspect, the first target channel is an earliest uplink data channel among all uplink data channels satisfying the first condition, among the N uplink data channels. In other words, the time-frequency resource carrying the first target channel in the second time-frequency resource is earlier in time domain than the time-frequency resource carrying any other uplink data channel satisfying the first condition.
Based on the scheme, the uplink control information is borne on the earliest uplink data channel which meets the first condition and is sent, so that the time delay requirement of the uplink control information can be ensured as far as possible.
With reference to the first aspect, in some implementations of the first aspect, the first target channel overlaps with the uplink control channel in a time domain. In other words, the time frequency resource carrying the first target channel in the second time frequency resource overlaps with the first time frequency resource in the time domain.
Based on this scheme, uplink control information can be transmitted on an uplink data channel that satisfies the first condition and overlaps with the uplink control channel in the time domain.
With reference to the first aspect, in some implementations of the first aspect, the first target channel is an earliest uplink data channel among all uplink data channels, which overlap with the uplink control channel in a time domain, of the N uplink data channels, and satisfy the first condition.
Based on the scheme, the uplink control information is carried on the uplink data channel which meets the first condition, is overlapped with the uplink control information in the time domain and is transmitted at the earliest time, so that the time delay requirement of the uplink control information can be ensured as far as possible.
With reference to the first aspect, in certain implementations of the first aspect, the method may further include: and carrying the uplink control information on at least one second target channel in the N uplink data channels for transmission. Wherein the second target channel is later than the first target channel.
It should be understood that the second target channel is later than the first target channel in the sense that the time-frequency resources carrying the second target channel are located behind the time-frequency resources carrying the first target channel in the time domain. It is to be understood that the uplink data channels subsequent to the first target channel of the N uplink data channels all satisfy the first condition.
Based on this scheme, by repeatedly transmitting the uplink control information using the inherent repetition of the uplink data channel, the transmission reliability of the uplink control information can be further improved.
With reference to the first aspect, in some implementations of the first aspect, the second target channel overlaps with the uplink control channel in a time domain.
Based on this scheme, the uplink control information may be repeatedly transmitted on an uplink data channel that satisfies the first condition and overlaps with the uplink control channel in the time domain, among the N uplink data channels.
With reference to the first aspect, in some implementations of the first aspect, the loading the uplink control information on a first target channel for transmission includes: and carrying the uplink control information on a first target channel to be sent under the condition that the priority of the uplink control channel is lower than or equal to the priority of the uplink data channel.
Based on the scheme, the transmission of the uplink control information and the uplink data channel can be realized on the premise of ensuring the priority of the uplink control information and the uplink data channel as much as possible.
With reference to the first aspect, in some implementations of the first aspect, the priority of the uplink data channel may be indicated by scheduling downlink control information of the uplink data channel, or the priority of the uplink data channel may be indicated by a Radio Network Temporary Identifier (RNTI) that scrambles and schedules the downlink control information of the uplink data channel; and/or the presence of a gas in the gas,
the priority of the uplink control information is the priority of a downlink data channel corresponding to the uplink control information, and the priority of the downlink data channel is indicated by scheduling the downlink control information of the downlink data channel, or the priority of the downlink data channel is indicated by scrambling the RNTI of the downlink control information of the downlink data channel.
Some description is made by taking the priority of the uplink data channel as an example. The priority of the uplink data channel may be indicated by scheduling downlink control information of the uplink data channel, and may mean any one of the following: (1) a format (format) for scheduling the downlink control information of the uplink data channel may indicate a priority of the uplink data channel; (2) a Downlink Control Information (DCI) field or field in the DCI scheduling the uplink data channel may indicate a priority of the uplink data channel; (3) the load size (payload size) of the downlink control information for scheduling the uplink data channel may indicate the priority of the uplink data channel. In addition, the time unit length of the uplink data channel scheduling or a Modulation and Coding Scheme (MCS) table adopted by the uplink data channel may also indicate the priority of the uplink data channel.
In a second aspect, a method for transmitting uplink information is provided, which may be performed by a network device or a module (e.g., a chip) in the network device.
The method comprises the following steps: determining a first time-frequency resource, wherein the first time-frequency resource is used for sending an uplink control channel, and the uplink control channel is used for carrying uplink control information; and determining a second time-frequency resource, wherein the second time-frequency resource is used for sending N uplink data channels, the N uplink data channels bear the same transmission block, and N is an integer greater than 1. And under the condition that the first time-frequency resource and the second time-frequency resource are overlapped on a time domain, if an uplink data channel meeting a first condition exists in the N uplink data channels, receiving the uplink control information on a first target channel. The first target channel is an uplink data channel satisfying a first condition among the N uplink data channels, and the first condition is a timeline condition that uplink control information is multiplexed on the uplink data channel for transmission.
Based on the method for transmitting uplink information provided by the application, as long as the uplink data channels meeting the timeline condition that the uplink control information is multiplexed and transmitted on the uplink data channel exist in the N uplink data channels, and all the uplink data channels do not need to meet the timeline condition, the uplink control information borne on the uplink control channel can be transmitted on the uplink data channels meeting the timeline condition that the uplink control information is multiplexed and transmitted on the uplink data channel. Therefore, the problem that the uplink control information is discarded in the prior art can be solved, so that the transmission reliability can be improved, and the system efficiency can be improved. In addition, since retransmission scheduling of the uplink control information is not required, the scheduling signaling overhead can be reduced.
With reference to the second aspect, in some implementations of the second aspect, there is also an uplink data channel that does not satisfy the first condition among the N uplink data channels.
With reference to the second aspect, in some implementations of the second aspect, the first target channel is an earliest uplink data channel among all uplink data channels satisfying the first condition, among the N uplink data channels.
With reference to the second aspect, in some implementations of the second aspect, the first target channel overlaps with the uplink control channel in a time domain.
With reference to the second aspect, in some implementations of the second aspect, the first target channel is an earliest uplink data channel among all uplink data channels, which overlap with the uplink control channel in a time domain, of the N uplink data channels, and satisfy the first condition.
With reference to the second aspect, in some implementations of the second aspect, the method may further include: receiving the uplink control information on at least one second target channel of the N uplink data channels. Wherein the second target channel is later than the first target channel.
With reference to the second aspect, in some implementations of the second aspect, the second target channel overlaps with the uplink control channel in a time domain.
With reference to the second aspect, in some implementations of the second aspect, the receiving the uplink control information on the first target channel includes: the uplink control information is received on a first target channel in the event that the priority of the uplink control channel is lower than or equal to the priority of the uplink data channel.
With reference to the second aspect, in some implementations of the second aspect, the priority of the uplink data channel is indicated by scheduling downlink control information of the uplink data channel, or the priority of the uplink data channel is indicated by a radio network temporary identifier RNTI scrambling the downlink control information of the uplink data channel; and/or the presence of a gas in the gas,
the priority of the uplink control information is the priority of a downlink data channel corresponding to the uplink control information, and the priority of the downlink data channel is indicated by scheduling the downlink control information of the downlink data channel, or the priority of the downlink data channel is indicated by a Radio Network Temporary Identifier (RNTI) of the downlink control information of the downlink data channel which is scheduled by scrambling.
For specific details and advantageous effects of various implementations provided by the second aspect, reference may be made to the above description of various implementations of the first aspect, and details are not repeated in the second aspect.
In a third aspect, a method for transmitting uplink information is provided, where the method may be performed by a terminal device or a module (e.g., a chip) in the terminal device.
The method comprises the following steps: determining a time-frequency resource for bearing a plurality of uplink control channels, wherein the uplink control channels are used for bearing uplink control information; and determining time-frequency resources for bearing the uplink data channel. And if the priority of the uplink control information is not higher than that of the uplink data channel and the uplink data channel meets a first condition, carrying the uplink control information on the uplink data channel and sending the uplink control information.
Wherein the plurality of uplink control channels are used for transmitting the same uplink control information. The plurality of uplink control channels correspond to a plurality of time units one to one, that is, each time unit can transmit one uplink control channel. The uplink data channel and a first uplink control channel of the multiple uplink control channels belong to the same time unit, or in other words, the time-frequency resource bearing the uplink data channel and the time-frequency resource bearing the first uplink control channel belong to the same time unit in the time domain. The first uplink control channel may be any one of the plurality of uplink control channels. And the time frequency resource bearing the uplink data channel is overlapped with the time frequency resource bearing the first uplink data channel in the time domain. The first condition is a timeline condition where uplink control information is multiplexed for transmission on an uplink data channel. The specific meanings of the overlap and the first condition can be referred to in the description of the first aspect.
Specifically, if the priority of the uplink control information is not higher than the priority of the uplink data channel, and the uplink data channel and the first uplink control channel overlap in the time domain, and the uplink data channel and the first uplink control channel satisfy the first condition, the first uplink control channel is discarded, and the uplink control information that is carried on the uplink control channel is transmitted on the uplink data channel.
Therefore, according to the method for transmitting uplink information provided by the present application, when an uplink data channel overlaps with one of a plurality of uplink control channels in a time domain, if the priority of the uplink control information that is supposed to be carried on the uplink control channel is not higher than the priority of the uplink data channel, and the uplink data channel and the uplink control channel that overlaps with the uplink data channel in the time domain satisfy a first condition, the uplink control information is carried on the uplink data channel for transmission. By the method, the transmission of the uplink data channel and the uplink control information can be realized under the scene that the repeated transmission of the uplink data channel and the uplink data channel is overlapped on the time domain.
Optionally, the time unit may be a time unit such as a slot (slot) and a subframe, and the time unit is not limited in this application.
In a fourth aspect, a method for transmitting uplink information is provided, which may be performed by a network device or a module (e.g., a chip) in the network device.
The method comprises the following steps: determining a time-frequency resource for bearing a plurality of uplink control channels, wherein the uplink control channels are used for bearing uplink control information; and determining time-frequency resources for bearing the uplink data channel. If the priority of the uplink control information is not higher than the priority of the uplink data channel and the uplink data channel meets a first condition, the uplink control information is received on the uplink data channel in a time unit to which the first uplink control channel belongs.
Wherein the plurality of uplink control channels are used for transmitting the same uplink control information. The plurality of uplink control channels correspond to a plurality of time units one to one, that is, each time unit can transmit one uplink control channel. The uplink data channel and a first uplink control channel of the multiple uplink control channels belong to the same time unit, or in other words, the time-frequency resource bearing the uplink data channel and the time-frequency resource bearing the first uplink control channel belong to the same time unit in the time domain. The first uplink control channel may be any one of the plurality of uplink control channels. And the time frequency resource bearing the uplink data channel is overlapped with the time frequency resource bearing the first uplink data channel in the time domain. The meaning of the overlap here can be seen in the description of the first aspect.
Specifically, if the priority of the uplink control information is not higher than the priority of the uplink data channel, and the uplink data channel and the first uplink control channel overlap in the time domain, and the uplink data channel and the first uplink control channel satisfy the first condition, the first uplink control channel is discarded, and the uplink control information that is carried on the uplink control channel is transmitted on the uplink data channel.
Therefore, according to the method for transmitting uplink information provided by the present application, when an uplink data channel overlaps with one of a plurality of uplink control channels in a time domain, if the priority of the uplink control information that is supposed to be carried on the uplink control channel is not higher than the priority of the uplink data channel, and the uplink data channel and the uplink control channel that overlaps with the uplink data channel in the time domain satisfy a first condition, the uplink control information is carried on the uplink data channel for transmission. By the method, the transmission of the uplink data channel and the uplink control information can be realized under the scene that the repeated transmission of the uplink data channel and the uplink data channel is overlapped on the time domain.
In a fifth aspect, a method for transmitting uplink information is provided, where the method may be performed by a terminal device or a module (e.g., a chip) in the terminal device.
The method comprises the following steps: determining service information of uplink control information to be sent on an uplink control channel; determining service information of each uplink data channel in M uplink data channels; determining a target uplink data channel from the M uplink data channels according to the service information of the uplink control information and the service information of each uplink data channel; and carrying the uplink control information on a target uplink data channel for transmission.
Wherein, the service information is service type or priority. The service information of at least two uplink data channels in the M uplink data channels is different. Moreover, each uplink data channel overlaps with the uplink control channel in the time domain, and the overlapping meaning is the same as the overlapping meaning described above, and is not described again. And, the M uplink data channels and the uplink control channel belong to the same time unit, and the meaning of the time unit is the same as the overlapping meaning described above, and is not described again.
Specifically, in a case where the uplink control channel and the plurality of uplink data channels are all overlapped, the terminal device may determine the uplink data channel multiplexed by the uplink control information according to the service type of the uplink control information and the service type of each uplink data channel that are originally carried on the uplink control channel, or according to the priority of the uplink control information and the priority of each uplink data channel. Thus, the terminal device may discard the uplink control channel and transmit the uplink control information on the uplink data channel multiplexed by the uplink control information.
According to the method for transmitting the uplink information, the uplink data channel multiplexed by the uplink control information is determined according to the service type or the priority, so that more reasonable transmission can be performed under the condition that the uplink control channel and a plurality of uplink data channels are overlapped. For example, it may be ensured that the transmission of information with higher priority is ensured as much as possible, or the transmission of a service with higher requirements on reliability and delay is ensured as much as possible, or the transmission of uplink control information is ensured as much as possible, so that the network device may obtain the transmitted feedback information in time.
Optionally, the representation manner or the indication manner of the priority of the uplink control information and the uplink data channel may refer to the description made above for the priority of the uplink control information and the uplink data channel, and is not described here again.
Alternatively, the traffic type of the uplink data channel may be indicated by any one of the following information:
(1) the length of the time unit of uplink data channel scheduling. That is, the length of the time unit scheduled by the uplink data channel may indicate the traffic type of the uplink data channel.
For example, if the time unit scheduled by the uplink data channel is a mini-slot, the service type of the uplink data channel is considered to be high reliable and low latency communications (URLLC), and if the time unit scheduled by the uplink data channel is a slot, the service type of the uplink data channel is considered to be enhanced mobile broadband (eMBB).
(2) And scrambling RNTI of downlink control information of the uplink data channel. That is, the type of RNTI scrambling the downlink control information of the scheduling uplink data channel may indicate the traffic type of the uplink data channel.
For example, if the RNTI of the downlink control information for scrambling and scheduling the uplink data channel is the first RNTI, the service type of the uplink data channel is considered to be URLLC. The first RNTI may be, for example, modulation and coding scheme-cell-radio network temporary identifier (MCS-C-RNTI) or configuration scheduling radio network temporary identifier (CS-RNTI). And if the RNTI of the downlink control information of the scrambling scheduling uplink data channel is the second RNTI, the service type of the uplink data channel is considered to be eMBB. Wherein the second RNTI is of a different type than the first RNTI. The second RNTI may be, for example, a cell radio network temporary identifier (C-RNTI).
(3) The load size (payload size) of the downlink control information of the uplink data channel is scheduled. That is, the load size of the downlink control information for scheduling the uplink data channel may indicate the traffic type of the uplink data channel.
For example, if the load size of the downlink control information for scheduling the uplink data channel #1 is smaller than the load size of the downlink control information for scheduling the uplink data channel #2, it is determined that the uplink data channel #1 is the URLLC service and the uplink data channel #2 is the eMBB service. For another example, if the load size of the downlink control information for scheduling the uplink data channel #1 is greater than or equal to a certain preset threshold, the service type of the uplink data channel is considered to be the eMBB, otherwise, the service type is the URLLC.
(4) MCS table for uplink data channel. That is, the MCS table employed by the uplink data channel may implicitly indicate the traffic type of the uplink data channel.
For example, if the MCS table with low spectral efficiency is used for the uplink data channel, the service type of the uplink data channel is considered to be URLLC. If the uplink data channel uses an MCS table with high spectral efficiency or an MCS table with a modulation scheme of 256 Quadrature Amplitude Modulation (QAM), the traffic type of the uplink data channel is considered to be eMBB.
(5) And scheduling a DCI domain in the downlink control information of the uplink data channel. That is, the traffic type of the uplink data channel may be indicated by a value in one DCI domain in the downlink control information of the scheduling uplink data channel. The DCI field may include 1 bit or a plurality of bits.
The indication mode of the service type of the uplink control information is similar to the indication mode of the service type of the uplink data channel, and the difference is that the service type of the uplink control information can be the service type of the downlink data channel corresponding to the uplink control information, and the meaning that the uplink control information corresponds to the downlink data channel is that the uplink control information includes the feedback of the downlink data channel. Here, the downlink control information for scheduling the uplink control channel means the downlink control information for scheduling the downlink data channel.
It should be understood that the determination of the traffic type of the uplink data channel may be replaced by the determination of any one of (1) to (5) above. Similarly, the determination of the traffic type of the uplink control information may be replaced by the determination similar to any one of (1) to (5) above.
With reference to the fifth aspect, in some implementations of the fifth aspect, the service information is a priority; and the target uplink data channel is one of the M uplink data channels, the priority of which is not higher than the uplink control information and meets a first condition. Wherein the meaning of the first condition is as described hereinbefore.
Based on the scheme, the transmission of the uplink control information and the uplink data channel can be realized on the premise of ensuring the priority of the uplink control information and the uplink data channel as much as possible.
With reference to the fifth aspect, in some implementations of the fifth aspect, the service information is a priority; and the target uplink data channel is the earliest uplink data channel of all uplink data channels, the priority of which is not higher than the uplink control information and meets the first condition, in the M uplink data channels.
Based on the scheme, the time delay requirement of the uplink control information can be ensured on the premise of ensuring the priority of the uplink control information and the uplink data channel as much as possible.
With reference to the fifth aspect, in some implementations of the fifth aspect, the service information is a priority; and the target uplink data channel may be the uplink data channel with the lowest priority among all the uplink data channels in the uplink control information, which satisfies the first condition and has a priority not higher than that of the M uplink data channels.
Based on the scheme, the transmission of the uplink control information can be realized on the premise of not influencing the transmission of the high-priority data.
With reference to the fifth aspect, in some implementations of the fifth aspect, the service information is a priority; and the target uplink data channel is the earliest uplink data channel which has the lowest priority and meets the first condition among the M uplink data channels and the priority of which is not higher than that of the uplink data channel of the uplink control information.
Based on the scheme, the transmission of high-priority data and the time delay requirement of uplink control information are favorably ensured.
With reference to the fifth aspect, in some implementation manners of the fifth aspect, the service information is a service type, and the service type of the uplink control information is URLLC; and the target uplink data channel is one of the M uplink data channels that meets the first condition.
Based on the scheme, the transmission of the uplink control information can be realized on the premise of not influencing the transmission of the uplink data.
With reference to the fifth aspect, in some implementation manners of the fifth aspect, the service information is a service type, and the service type of the uplink control information is URLLC; and the target uplink data channel is the earliest uplink data channel meeting the first condition in the M uplink data channels.
Based on the scheme, the time delay requirement of the uplink control information can be ensured on the premise of not influencing the transmission of the uplink data.
With reference to the fifth aspect, in some implementation manners of the fifth aspect, the service information is a service type, and the service type of the uplink control information is an eMBB; and the target uplink data channel is one of the M uplink data channels which meets the first condition and has the service type of the eMBB.
Based on the scheme, the transmission of the uplink control information is favorably realized on the premise of ensuring the transmission of the high-priority data.
With reference to the fifth aspect, in some implementation manners of the fifth aspect, the service information is a service type, and the service type of the uplink control information is an eMBB; and the target uplink data channel is the earliest uplink data channel which meets the first condition in the uplink data channels with the business type of eMBB in the M uplink data channels.
Based on the scheme, the method is favorable for ensuring the time delay requirement of the uplink control information on the premise of ensuring the transmission of the high-priority data.
In a sixth aspect, a method for transmitting uplink information is provided, which may be performed by a network device or a module (e.g., a chip) in the network device.
The method comprises the following steps: determining service information of uplink control information to be sent on an uplink control channel; determining service information of each uplink data channel in M uplink data channels; determining a target uplink data channel from the M uplink data channels according to the service information of the uplink control information and/or the service information of each uplink data channel; the uplink control information is received on a target uplink data channel.
Wherein, the service information is service type or priority. The service information of at least two uplink data channels in the M uplink data channels is different. Moreover, each uplink data channel overlaps with the uplink control channel in the time domain, and the overlapping meaning is the same as the overlapping meaning described above, and is not described again. And, the M uplink data channels and the uplink control channel belong to the same time unit, and the meaning of the time unit is the same as the overlapping meaning described above, and is not described again.
Specifically, in a case where the uplink control channel and the plurality of uplink data channels are all overlapped, the terminal device may determine the uplink data channel multiplexed by the uplink control information according to the service type of the uplink control information and the service type of each uplink data channel that are originally carried on the uplink control channel, or according to the priority of the uplink control information and the priority of each uplink data channel. Thus, the terminal device may discard the uplink control channel and transmit the uplink control information on the uplink data channel multiplexed by the uplink control information.
According to the method for transmitting the uplink information, the uplink data channel multiplexed by the uplink control information is determined according to the service type or the priority, so that more reasonable transmission can be performed under the condition that the uplink control channel and a plurality of uplink data channels are overlapped. For example, it may be ensured that the transmission of information with higher priority is ensured as much as possible, or the transmission of a service with higher requirements on reliability and delay is ensured as much as possible, or the transmission of uplink control information is ensured as much as possible, so that the network device may obtain the transmitted feedback information in time.
With reference to the sixth aspect, in some implementations of the sixth aspect, the service information is a priority; and the target uplink data channel is one of the M uplink data channels, the priority of which is not higher than the uplink control information and meets a first condition. Wherein the meaning of the first condition is as described hereinbefore.
With reference to the sixth aspect, in some implementations of the sixth aspect, the service information is a priority; and the target uplink data channel is the earliest uplink data channel of all uplink data channels, the priority of which is not higher than the uplink control information and meets the first condition, in the M uplink data channels.
With reference to the sixth aspect, in some implementations of the sixth aspect, the service information is a priority; and the target uplink data channel may be the uplink data channel with the lowest priority among all the uplink data channels in the uplink control information, which satisfies the first condition and has a priority not higher than that of the M uplink data channels.
With reference to the sixth aspect, in some implementations of the sixth aspect, the service information is a priority; and the target uplink data channel is the earliest uplink data channel which has the lowest priority and meets the first condition among the M uplink data channels and the priority of which is not higher than that of the uplink data channel of the uplink control information.
With reference to the sixth aspect, in some implementation manners of the sixth aspect, the service information is a service type, and the service type of the uplink control information is URLLC; and the target uplink data channel is one of the M uplink data channels that meets the first condition.
With reference to the sixth aspect, in some implementation manners of the sixth aspect, the service information is a service type, and the service type of the uplink control information is URLLC; and the target uplink data channel is the earliest uplink data channel meeting the first condition in the M uplink data channels.
With reference to the sixth aspect, in some implementation manners of the sixth aspect, the service information is a service type, and the service type of the uplink control information is an eMBB; and the target uplink data channel is one of the M uplink data channels which meets the first condition and has the service type of the eMBB.
With reference to the sixth aspect, in some implementation manners of the sixth aspect, the service information is a service type, and the service type of the uplink control information is an eMBB; and the target uplink data channel is the earliest uplink data channel which meets the first condition in the uplink data channels with the business type of eMBB in the M uplink data channels.
For specific details and advantageous effects of the various implementations provided by the sixth aspect, reference may be made to the above description of the various implementations of the fifth aspect, and details are not repeated in the sixth aspect.
In a seventh aspect, a communication apparatus is provided, including: the processing module is used for determining the first time-frequency resource and uplink control information carried on an uplink control channel to be sent on the first time-frequency resource; the processing module is further configured to determine a second time-frequency resource and N uplink data channels to be sent on the second time-frequency resource, where the N uplink data channels carry the same transport block, and N is an integer greater than 1; and a transceiver module, configured to, under a condition that the first time-frequency resource and the second time-frequency resource overlap in a time domain, if there is an uplink data channel that meets a first condition in the N uplink data channels, bear the uplink control information on a first target channel to send, where the first target channel is one of the N uplink data channels that meets the first condition, and the first condition is a timeline condition that uplink control information is multiplexed on an uplink data channel for transmission.
With reference to the seventh aspect, in some implementations of the seventh aspect, there is also an uplink data channel that does not satisfy the first condition among the N uplink data channels.
With reference to the seventh aspect, in some implementations of the seventh aspect, the first target channel is an earliest uplink data channel among all uplink data channels that satisfy the first condition, among the N uplink data channels.
With reference to the seventh aspect, in some implementations of the seventh aspect, the first target channel and the uplink control channel overlap in a time domain.
With reference to the seventh aspect, in some implementations of the seventh aspect, the first target channel is an earliest uplink data channel among all uplink data channels, which overlap with the uplink control channel in a time domain, of the N uplink data channels, and satisfy the first condition.
With reference to the seventh aspect, in some implementations of the seventh aspect, the transceiver module is further configured to:
and carrying the uplink control information on at least one second target channel in the N uplink data channels to be sent, wherein the second target channel is later than the first target channel.
With reference to the seventh aspect, in some implementations of the seventh aspect, the second target channel overlaps with the uplink control channel in a time domain.
With reference to the seventh aspect, in some implementations of the seventh aspect, the transceiver module is specifically configured to:
and carrying the uplink control information on the first target channel to be sent under the condition that the priority of the uplink control channel is lower than or equal to the priority of the uplink data channel.
With reference to the seventh aspect, in some implementations of the seventh aspect, the priority of the uplink data channel is indicated by scheduling downlink control information of the uplink data channel, or the priority of the uplink data channel is indicated by a radio network temporary identifier RNTI of the downlink control information of the uplink data channel that is scrambled and scheduled; and/or the presence of a gas in the gas,
the priority of the uplink control information is the priority of a downlink data channel corresponding to the uplink control information, and the priority of the downlink data channel is indicated by scheduling the downlink control information of the downlink data channel, or the priority of the downlink data channel is indicated by a Radio Network Temporary Identifier (RNTI) of the downlink control information of the downlink data channel which is scheduled by scrambling.
It is to be understood that the communication device of the seventh aspect performs the method of any one of the possible implementations of the first aspect.
In an eighth aspect, there is provided a communication apparatus comprising: a communications apparatus, comprising:
a processing module, configured to determine a first time-frequency resource, where the first time-frequency resource is used to send an uplink control channel, and the uplink control channel carries uplink control information; the processing module is further configured to determine a second time-frequency resource, where the second time-frequency resource is used to send N uplink data channels, where the N uplink data channels carry the same transport block, and N is an integer greater than 1; a transceiver module, configured to receive the uplink control information on a first target channel if there is an uplink data channel that meets a first condition in the N uplink data channels under a condition that the first time-frequency resource and the second time-frequency resource overlap in a time domain, where the first target channel is one of the N uplink data channels that meets the first condition, and the first condition is a timeline condition that uplink control information is multiplexed on an uplink data channel for transmission.
With reference to the eighth aspect, in some implementations of the eighth aspect, there is also an uplink data channel that does not satisfy the first condition among the N uplink data channels.
With reference to the eighth aspect, in some implementations of the eighth aspect, the first target channel is an earliest uplink data channel among all uplink data channels satisfying the first condition, among the N uplink data channels.
With reference to the eighth aspect, in some implementations of the eighth aspect, the first target channel and the uplink control channel overlap in a time domain.
With reference to the eighth aspect, in some implementations of the eighth aspect, the first target channel is an earliest uplink data channel among all uplink data channels, which overlap with the uplink control channel in a time domain, of the N uplink data channels, that meets the first condition.
With reference to the eighth aspect, in some implementations of the eighth aspect, the transceiver module is further configured to:
receiving the uplink control information on at least one second target channel of the N uplink data channels, wherein the second target channel is later than the first target channel.
With reference to the eighth aspect, in some implementations of the eighth aspect, the second target channel overlaps with the uplink control channel in a time domain.
With reference to the eighth aspect, in some implementations of the eighth aspect, the transceiver module is specifically configured to:
receiving the uplink control information on the first target channel if the priority of the uplink control channel is lower than or equal to the priority of the uplink data channel.
With reference to the eighth aspect, in some implementations of the eighth aspect, the priority of the uplink data channel is indicated by scheduling downlink control information of the uplink data channel, or the priority of the uplink data channel is indicated by a radio network temporary identifier RNTI that scrambles and schedules the downlink control information of the uplink data channel; and/or the presence of a gas in the gas,
the priority of the uplink control information is the priority of a downlink data channel corresponding to the uplink control information, and the priority of the downlink data channel is indicated by scheduling the downlink control information of the downlink data channel, or the priority of the downlink data channel is indicated by a Radio Network Temporary Identifier (RNTI) of the downlink control information of the downlink data channel which is scheduled by scrambling.
It will be appreciated that the communications apparatus of the eighth aspect performs the method of any one of the possible implementations of the second aspect.
In a ninth aspect, there is provided a communication device comprising means for performing the method of any one of the possible implementations of the third or fifth aspect.
In a tenth aspect, a communication device is provided that includes a processor. The processor is coupled to the memory and is operable to execute the instructions in the memory to implement the method of any of the possible implementations of the first, third or fifth aspect described above and of the first, third or fifth aspect. Optionally, the communication device further comprises a memory. Optionally, the communication device further comprises an interface circuit, the processor being coupled to the interface circuit.
In one implementation, the communication device is a terminal device. When the communication device is a terminal device, the interface circuit may be a transceiver, or an input/output interface.
In another implementation, the communication device is a chip configured in the terminal equipment. When the communication device is a chip configured in a terminal device, the interface circuit may be an input/output interface.
Alternatively, the transceiver may be a transmit-receive circuit. Alternatively, the input/output interface may be an input/output circuit.
In an eleventh aspect, there is provided a communication device comprising means for performing the methods of the fourth or sixth aspects in any possible implementation manner of the fourth or sixth aspects.
In a twelfth aspect, a communications apparatus is provided that includes a processor. The processor is coupled to the memory and is operable to execute the instructions in the memory to implement the method of the second, fourth or sixth aspect described above and any possible implementation of the second, fourth or sixth aspect. Optionally, the communication device further comprises a memory. Optionally, the communication device further comprises an interface circuit, the processor being coupled to the communication interface.
In one implementation, the communication device is a network device. When the communication device is a network device, the interface circuit may be a transceiver, or an input/output interface.
In another implementation, the communication device is a chip configured in the network device. When the communication device is a chip configured in a network device, the interface circuit may be an input/output interface.
Alternatively, the transceiver may be a transmit-receive circuit. Alternatively, the input/output interface may be an input/output circuit.
In a thirteenth aspect, a processor is provided, including: input circuit, output circuit and processing circuit. The processing circuit is configured to receive a signal via the input circuit and transmit a signal via the output circuit, so that the processor performs the method of any one of the possible implementations of the first to sixth aspects and the first to sixth aspects.
In a specific implementation process, the processor may be a chip, the input circuit may be an input pin, the output circuit may be an output pin, and the processing circuit may be a transistor, a gate circuit, a flip-flop, various logic circuits, and the like. The input signal received by the input circuit may be received and input by, for example and without limitation, a receiver, the signal output by the output circuit may be output to and transmitted by a transmitter, for example and without limitation, and the input circuit and the output circuit may be the same circuit that functions as the input circuit and the output circuit, respectively, at different times. The embodiment of the present application does not limit the specific implementation manner of the processor and various circuits.
In a fourteenth aspect, a processing apparatus is provided that includes a processor and a memory. The processor is configured to read instructions stored in the memory, and may receive a signal via the receiver and transmit a signal via the transmitter to perform the method of any one of the possible implementations of the first to sixth aspects and the first to sixth aspects.
Optionally, the number of the processors is one or more, and the number of the memories is one or more.
Alternatively, the memory may be integral to the processor or provided separately from the processor.
In a specific implementation process, the memory may be a non-transient memory, such as a Read Only Memory (ROM), which may be integrated on the same chip as the processor, or may be separately disposed on different chips.
It will be appreciated that the associated data interaction process, for example, sending the upper control information may be a process that outputs the upper control information from the processor, and receiving the information may be a process that receives the information from the processor. In particular, the data output by the processor may be output to a transmitter and the input data received by the processor may be from a receiver. The transmitter and receiver may be collectively referred to as a transceiver, among others.
The processing device in the above fourteenth aspect may be a chip, the processor may be implemented by hardware or may be implemented by software, and when implemented by hardware, the processor may be a logic circuit, an integrated circuit, or the like; when implemented in software, the processor may be a general-purpose processor implemented by reading software code stored in a memory, which may be integrated with the processor, located external to the processor, or stand-alone.
In a fifteenth aspect, a computer program product is provided, the computer program product comprising: a computer program (which may also be referred to as code, or instructions), which when executed, causes a computer to perform the method of any one of the possible implementations of the first to sixth aspects and of the first to sixth aspects described above.
In a sixteenth aspect, a computer-readable medium is provided, which stores a computer program (which may also be referred to as code or instructions) that, when executed on a computer, causes the computer to perform the method of any of the possible implementations of the first to sixth aspects and of the first to sixth aspects.
In a seventeenth aspect, a communication system is provided, which includes the foregoing network device and terminal device.
Drawings
Fig. 1 is an architecture diagram of a mobile communication system applied to the present application;
fig. 2 is a schematic diagram of timeline conditions for UCI multiplexing for transmission on PUSCH;
fig. 3 is a schematic diagram of relative positions of PUCCH and PUSCH in the time domain;
fig. 4 is a schematic flow chart of a method for transmitting uplink information provided by the present application;
fig. 5 to 8 are schematic diagrams of different situations where a first time-frequency resource and a second time-frequency resource overlap in a time domain;
fig. 9 to 13 are specific exemplary diagrams of a first target channel and/or a second target channel;
fig. 14 is a diagram of another specific example of a method for transmitting uplink information provided in the present application;
fig. 15 is a schematic flow chart of still another method for transmitting uplink information provided herein;
fig. 16 to fig. 22 are specific exemplary diagrams of another method for transmitting uplink information provided in the present application;
fig. 23 is a schematic diagram of a communication device according to the present application;
fig. 24 is a schematic structural diagram of a terminal device provided in the present application;
fig. 25 is a schematic structural diagram of a network device provided in the present application.
Detailed Description
The technical solution in the present application will be described below with reference to the accompanying drawings.
The technical scheme of the embodiment of the application can be applied to various communication systems, for example: a New Radio (NR) system in a fifth generation (5G) mobile communication system of a Long Term Evolution (LTE) system, a future mobile communication system, and the like.
The Terminal device in the embodiment of the present application may be referred to as a Terminal, a User Equipment (UE), a Mobile Station (MS), a Mobile Terminal (MT), and the like. The terminal device may be a mobile phone (mobile phone), a tablet computer (Pad), a computer with a wireless transceiving function, a Virtual Reality (VR) terminal device, an Augmented Reality (AR) terminal device, a wireless terminal in industrial control (industrial control), a wireless terminal in unmanned driving (self driving), a wireless terminal in remote surgery (remote management), a wireless terminal in smart grid (smart grid), a wireless terminal in transportation safety (transportation safety), a wireless terminal in smart city (smart city), a wireless terminal in home (smart home), and the like. The embodiment of the present application does not limit the specific technology and the specific device form adopted by the terminal device.
The network device in this embodiment is an access device in which a terminal device accesses to the mobile communication system in a wireless manner, and may be a base station NodeB, an evolved node b (eNB), a Transmission Reception Point (TRP), a next generation base station (gNB) in a 5G mobile communication system, a base station in a future mobile communication system, or an access node in a WiFi system. The embodiments of the present application do not limit the specific technologies and the specific device forms adopted by the radio access network device.
In the embodiment of the application, the terminal device or the network device includes a hardware layer, an operating system layer running on the hardware layer, and an application layer running on the operating system layer. The hardware layer includes hardware such as a Central Processing Unit (CPU), a Memory Management Unit (MMU), and a memory (also referred to as a main memory). The operating system may be any one or more computer operating systems that implement business processing through processes (processes), such as a Linux operating system, a Unix operating system, an Android operating system, an iOS operating system, or a windows operating system. The application layer comprises applications such as a browser, an address list, word processing software, instant messaging software and the like. Furthermore, the embodiment of the present application does not particularly limit the specific structure of the execution main body of the method provided by the embodiment of the present application, as long as the communication can be performed according to the method provided by the embodiment of the present application by running the program recorded with the code of the method provided by the embodiment of the present application, for example, the execution main body of the method provided by the embodiment of the present application may be a terminal device or a network device, or a functional module capable of calling the program and executing the program in the terminal device or the network device.
In addition, various aspects or features of the present application may be implemented as a method, apparatus, or article of manufacture using standard programming and/or engineering techniques. The term "article of manufacture" as used herein is intended to encompass a computer program accessible from any computer-readable device, carrier, or media. For example, computer-readable media can include but are not limited to magnetic storage devices (e.g., hard disk, floppy disk, magnetic strips, etc.), optical disks (e.g., Compact Disk (CD), Digital Versatile Disk (DVD), etc.), smart cards, and flash memory devices (e.g., erasable programmable read-only memory (EPROM), card, stick, or key drive, etc.). In addition, various storage media described herein can represent one or more devices and/or other machine-readable media for storing information. The term "machine-readable medium" can include, without being limited to, wireless channels and various other media capable of storing, containing, and/or carrying instruction(s) and/or data.
Fig. 1 is a schematic architecture diagram of a mobile communication system applied to the present application. As shown in fig. 1, the communication system 100 may include at least one network device, such as the network device 110 shown in fig. 1; the communication system 100 may also include at least one terminal device, such as the terminal device 120 shown in fig. 1. Network device 110 and terminal device 120 may communicate via a wireless link. The terminal device 120 may be fixed or mobile. It should be understood that fig. 1 is only a schematic diagram, and other network devices, such as a core network device, a wireless relay device, a wireless backhaul device, and the like, may also be included in the communication system. In addition, the embodiments of the present application do not limit the number of network devices and terminal devices included in the mobile communication system.
In the present application, a PUSCH is used as an uplink data channel, a Physical Downlink Shared Channel (PDSCH) is used as a downlink data channel, a PUCCH is used as an uplink control channel, a Physical Downlink Control Channel (PDCCH) is used as a downlink control channel, Uplink Control Information (UCI) is used as uplink control information, and Downlink Control Information (DCI) is used as downlink control information.
A technique is known in which, in a slot (slot), if a PUCCH and at least one PUSCH carrying the same Transport Block (TB) overlap in a time domain and both the at least one PUSCH satisfy a timeline condition that UCI is multiplexed on the PUSCH for transmission, UCI originally carried on PUCCH transmission is carried on the PUSCH for transmission, and the PUCCH is not transmitted.
The timeline condition of UCI multiplexing for transmission on PUSCH refers to: (1) the time interval between the first OFDM symbol of the earliest channel in time in the PUCCH and PUSCH overlapped in the time domain and the end time of the PDSCH is not less than a first threshold. Wherein, any one of the PUSCH and the PUCCH corresponds to the PDSCH, that is, feedback information of the PDSCH is carried on the PUCCH or the PUSCH. (2) And the time interval between the first OFDM symbol of the earliest channel in time in the PUCCH and PUSCH which are overlapped in the time domain and the end time of the PDCCH is not less than a second threshold. Here, any one of the PUSCH and PUCCH corresponds to the PDCCH, and the corresponding meaning here is: the PDCCH schedules a PDSCH, and the PUCCH or PUSCH carries feedback information of the PDSCH. Or the PDCCH schedules PUSCH transmission. In the above, the first threshold may be N1+ X OFDM symbols, and the second threshold may be N2+ Y OFDM symbols. N1 represents the processing time of the PDSCH by the terminal device, that is, the time when the terminal device receives the PDSCH, demodulates and decodes the PDSCH to generate feedback information, and prepares for transmission. N2 represents the preparation time of the PUSCH by the terminal apparatus, i.e., the time when the terminal apparatus demodulates and decodes the signaling and prepares the PUSCH packet for transmission according to the signaling after receiving the scheduling information of the PUSCH. X and Y are pre-configured, pre-defined or network device indicated OFDM symbol numbers.
Fig. 2 shows a schematic diagram of timeline conditions for UCI multiplexing for transmission on PUSCH. Referring to fig. 2, a channel earlier in time among PUCCH and PUSCH overlapped in the time domain is PUCCH, a time interval between a first OFDM symbol of PUCCH and an end time of PDSCH is not less than N1+ X OFDM symbols, and a time interval between the first OFDM symbol and the end time of PDCCH is not less than N2+ Y OFDM symbols.
For example, assuming that the positions of the PUCCH and the PUSCH in the time domain are as shown in fig. 3, it is required that both PUSCH #1 and PUSCH #2 satisfy the above timeline condition, and uplink control information carried on the PUCCH can be carried on PUSCH #1 for transmission.
It should be understood that if PUCCH or PUSCH requires PDCCH scheduling or activation, PUCCH and PUSCH need to satisfy both conditions. If the PUCCH or PUSCH is scheduling-free, only the first condition needs to be satisfied.
Based on the protocol specification, if there is a PUSCH which does not satisfy the timeline condition in the at least one PUSCH, for example, PUSCH #1 does not satisfy the timeline condition and PUSCH #2 satisfies the timeline condition in fig. 3, uplink control information carried on the PUCCH cannot be transmitted on the PUSCH, which may result in a decrease in reliability of transmission and a decrease in system efficiency.
In view of this, the present application provides a method for transmitting uplink information, based on which, as long as there is a PUSCH meeting a timeline condition, uplink control information carried on a PUCCH can be transmitted on the PUSCH without all PUSCHs meeting the timeline condition, which can avoid the problem that the uplink control information is discarded in the prior art, thereby improving transmission reliability and improving system efficiency.
The following describes a method for transmitting uplink information provided by the present application. It should be understood that, for the convenience of understanding, when the method is described below, some steps of operations are mainly described with the terminal device as the execution subject, and other operations are mainly described with the network device as the execution subject, but this does not limit the present application in any way, and actually, operations performed by the terminal device may also be performed by a module (e.g., a chip) in the terminal device, and similarly, operations performed by the network device may also be performed by a module (e.g., a chip) in the network device.
The method of the present application can be applied to any time unit, that is, in any time unit, both the terminal device and the network device can transmit the uplink control information based on the method. The time unit may be a subframe, a slot (slot), a half slot, or the like, and the specific length of the time unit is not limited in the present application. For example, the time unit may include 14 OFDM symbols or 7 OFDM symbols, and the number of OFDM symbols included in the time unit is not limited in the present application. Hereinafter, a time slot will be described as an example.
Fig. 4 shows an exemplary flowchart of a method 200 for transmitting uplink information provided by the present application. The method 200 mainly includes S210 to S250. The respective steps will be explained below.
S210, the terminal equipment determines a first time-frequency resource. The first time-frequency resource is used for transmitting PUCCH, and the PUCCH is used for carrying UCI.
It should be understood that the UCI in the present application may include feedback information, i.e., hybrid automatic repeat request (HARQ) feedback information, but the present application is not limited thereto. For example, the UCI may further include a Scheduling Request (SR), Channel State Information (CSI), where the CSI includes periodic CSI (periodic-CSI) and aperiodic-CSI.
Illustratively, the first time-frequency resource may be configured to the terminal device by the network device through either of the following two ways.
1. The first time frequency resource may be indicated by the trigger signaling. Accordingly, the PUCCH may be an aperiodic signal triggered by the trigger signaling.
The trigger signaling is DCI or a downlink data channel, the DCI may be carried by a downlink control channel, and the DCI may schedule the downlink data channel. Correspondingly, the UCI carried on the PUCCH is uplink feedback information corresponding to the downlink data channel, such as an Acknowledgement (ACK) or a Negative Acknowledgement (NACK).
2. The first time frequency resource may be configured by configuration signaling. Accordingly, the PUCCH may be a periodic signal configured by the signaling configuration.
The configuration signaling may be RRC signaling or MAC signaling or physical layer signaling. The configuration signaling may configure a transmission period and a time domain resource offset of a periodic signal, where the periodic signal may be an unlicensed uplink control channel grant-freePUCCH or a semi-persistent scheduling uplink control channel SPS PUCCH. That is, the PUCCH may be grant-freePUCCH or SPS PUCCH.
S220, the terminal equipment determines a second time-frequency resource.
And the second time-frequency resource is used for sending N PUSCHs, wherein N is an integer greater than 1. The N PUSCHs carry the same transport block, or are used for transmitting the same transport block. That is, the N PUSCHs are used for repeated transmission of the same transport block. And the second time frequency resource and the first time frequency resource belong to the same time unit, and the first time frequency resource and the second time frequency resource are overlapped.
The time domain length of each PUSCH may be granular in sub-time units (alternatively referred to as micro-time units). The time domain length of a sub-time unit is less than a time unit. The sub-time units may be micro-subframes or mini-slots (mini-slots) or other possible units of time. Further, when the time unit is a slot, the sub-time unit may be a mini-slot (mini-slot). When the time unit is a subframe, the sub-time unit may be a micro-subframe. Typical values for the mini-slot are 2,4,7 OFDM symbols, and may also be {1,3,5,6,8,9,10,11,12,13} OFDM symbols. Hereinafter, the description will be given taking a sub-time unit as an example of a mini-slot.
Illustratively, the network device may configure the terminal device with the number of times of mini-slot repetition and occupied resources through a trigger signaling indication or through a configuration signaling. The resource occupied by each mini-slot may be the same value or may be different values. The number of resources occupied by each mini-slot may be indicated by a value. Alternatively, the number of resources occupied by each mini-slot may be indicated by a set of values, which may be all the same, or different, or partially different.
The first time-frequency resource and the second time-frequency resource are overlapped in a time domain, which may mean that the first time-frequency resource and the second time-frequency resource are completely overlapped in the time domain, or that the first time-frequency resource and the second time-frequency resource are partially overlapped in the time domain.
The complete overlap means that the second time frequency resource comprises the first time frequency resource and the first time frequency resource also comprises the second time frequency resource. For example, fig. 5 shows a case where the first time-frequency resource and the second time-frequency resource completely overlap. In fig. 5 and fig. 6 to 8 described below, it is assumed that the second time-frequency resource is the sum of the time-frequency resources occupied by the PUSCHs #1 to #4, that is, the N PUSCHs are the PUSCHs #1 to #4, and the first time-frequency resource is the time-frequency resource occupied by the PUCCH.
Partial overlap may include three cases: (1) the first time-frequency resource does not include all of the second time-frequency resource, and the second time-frequency resource does not include all of the first time-frequency resource, as shown in fig. 6; (2) the first time-frequency resource includes all of the second time-frequency resources, but some of the first time-frequency resources do not belong to the second time-frequency resources, that is, the second time-frequency resources are a proper subset of the first time-frequency resources, as shown in fig. 7; (3) the first time frequency resource is a proper subset of the second time frequency resource, as shown in fig. 8. It should be understood that the relationship between time-frequency resources described herein only refers to the relationship in the time domain, and is not limited in the frequency domain.
For example, the network device may configure the second time-frequency resource to the terminal device by a method similar to the method for configuring the first time-frequency resource. It should be noted that, if the time-frequency resources occupied by each PUSCH are the same, the network device may configure the second time-frequency resource by configuring the time-frequency resource occupied by one PUSCH and the number of times of repeated transmission. The number of repetitions of the PUSCH, that is, the value of N, may be carried on the DCI, or may be preconfigured by the network device. If the time frequency resources occupied by each PUSCH are different or the time frequency resources occupied by at least two PUSCHs are different, the network device may notify the terminal device of the time frequency resources respectively occupied by each PUSCH. The configuration mode of the second time frequency resource is not limited, and the configuration mode is reasonable.
It should be understood that the chronological order of S210 and S220 is not specified, and S210 may be performed prior to S220, S220 may be performed prior to S210, or both may be performed simultaneously.
S230, the network device determines a first time-frequency resource.
S240, the network device determines a second time-frequency resource.
It should be understood that, at this time, the network device determines the first time-frequency resource and the second time-frequency resource that have been configured to the terminal device.
And S250, the terminal equipment loads the UCI on the first target channel to send. Accordingly, the network device receives the UCI on the first target channel.
Specifically, under the condition that the first time-frequency resource and the second time-frequency resource are completely or partially overlapped in the time domain, if there is a PUSCH meeting the first condition in the N PUSCHs, the terminal device may discard the PUCCH, and bear the UCI, which is originally borne on the PUCCH, on the first target channel for transmission. The first target channel is one of the N PUSCHs that meets a first condition, and the first condition is a timeline condition that the UCI is multiplexed on the PUSCH for transmission.
That is to say, under the condition that the first time-frequency resource and the second time-frequency resource are overlapped in the time domain, the UCI may be carried on one PUSCH of the N PUSCHs, which satisfies the timeline condition that the UCI is multiplexed and transmitted on the PUSCH. For the timeline condition of UCI multiplexing for transmission on PUSCH, refer to the foregoing description specifically, and are not described herein again.
Therefore, based on the method of the present application, as long as there is a PUSCH that satisfies the timeline condition for UCI multiplexing to transmit on the PUSCH among the N PUSCHs, and all PUSCHs are not required to satisfy the timeline condition, the UCI that is originally carried on the PUCCH can be transmitted on the PUSCH. Therefore, the problem that UCI is discarded in the prior art can be avoided, so that the transmission reliability can be improved, and the system efficiency can be improved. In addition, because retransmission scheduling of UCI is not required, the scheduling signaling overhead can be reduced.
In the present application, the UCI multiplexing may be performed on the PUSCH in two manners, namely puncturing (prediction) and rate-matching (rate-matching).
The following description will mainly be made with reference to two scenarios, regarding a possible scenario of the first target channel.
Scene one
The first target channel may not overlap with the PUCCH in a time domain.
In other words, the time-frequency resource carrying the first target channel in the second time-frequency resource may not overlap with the first time-frequency resource in the time domain.
In this scenario, the first target channel may be any PUSCH of the N PUSCHs that satisfies the first condition. Or, the first target channel may be the earliest PUSCH among all PUSCHs that satisfy the first condition among the N PUSCHs, that is, the time-frequency resource that carries the first target channel in the second time-frequency resource is earlier in time domain than the time-frequency resource that carries any other PUSCH that satisfies the first condition.
For example, referring to fig. 9, if the N PUSCHs are PUSCH #1 to PUSCH #4, and only PUSCH #3 and PUSCH #4 of PUSCH #1 to PUSCH #4 satisfy the first condition, the first target channel may be PUSCH #3 or PUSCH # 4. Alternatively, the first target channel may be the earliest PUSCH among PUSCH #3 and PUSCH #4, i.e., PUSCH # 3.
For another example, referring to fig. 10, the N PUSCHs are PUSCH #1 to PUSCH #4, and if PUSCH #1 to PUSCH #4 all satisfy the first condition, the first target channel may be PUSCH #1, i.e., the earliest PUSCH satisfying the first condition.
Scene two
The first target channel overlaps with the PUCCH in the time domain.
In other words, the time frequency resource carrying the first target channel in the second time frequency resource overlaps with the first time frequency resource in the time domain.
In this scenario, the first target channel may be any PUSCH among all PUSCHs that overlap with the PUCCH (or the first time-frequency resource) in the time domain and satisfy the first condition. Alternatively, the first target channel may be an earliest PUSCH among all PUSCHs that overlap with the PUCCH in the time domain and satisfy the first condition, of the N PUSCHs.
For example, referring to fig. 11, of PUSCH #1 to PUSCH #4, only PUSCH #2 and PUSCH #3 overlap with PUCCH. If both PUSCH #2 and PUSCH #3 satisfy the first condition, the first target channel may be PUSCH #2 or PUSCH # 3. Alternatively, the first target channel may be the earliest PUSCH among PUSCH #2 and PUSCH #3, i.e., PUSCH # 2.
In the present application, there may be PUSCH satisfying the first condition among the N PUSCHs, but the present application is not limited to this. That is, the present application is also applicable when all of the N PUSCHs satisfy the first condition.
In some implementations, the UCI is carried on the earliest PUSCH satisfying the first condition and transmitted, so that the delay requirement of the UCI can be guaranteed as much as possible.
Optionally, as an embodiment of the present application, S250 may be performed when the priority of UCI is lower than or equal to the priority of PUSCH.
That is, when the priority of UCI is lower than or equal to the priority of PUSCH, UCI may be transmitted using the method of the present application. For example, when UCI of a high-reliability low-latency communication (URLLC) service is transmitted on a PUCCH and an enhanced mobile broadband (eMBB) service is transmitted on a PUSCH, the UCI may be transmitted by using the method of the present application. It should be understood that the priority of UCI may also be considered as the priority of PUCCH.
In the present application, optionally, the priority of the PUSCH may be indicated by any one of the following information:
(1) length of time unit for PUSCH scheduling. That is, the time unit length of PUSCH scheduling may indicate the priority of PUSCH.
For example, if the time unit of PUSCH scheduling is a mini-slot, the priority of PUSCH is considered to be high, and if the time unit of PUSCH scheduling is a slot, the priority of PUSCH is considered to be low.
(2) And scrambling RNTI of DCI for scheduling PUSCH. That is, the type of RNTI scrambling DCI scheduling PUSCH may indicate the priority of PUSCH.
For example, if the RNTI of the DCI for scrambling and scheduling the PUSCH is the first RNTI, the priority of the PUSCH is considered to be higher. The first RNTI may be, for example, a modulation and coding scheme-cell radio network temporary identifier (MCS-C-RNTI) or a configured scheduling radio network temporary identifier (CS-RNTI), and if the RNTI of the DCI scrambled and scheduled PUSCH is the second RNTI, the priority of the PUSCH is considered to be low. Wherein the second RNTI is of a different type than the first RNTI. The second RNTI may be, for example, a cell radio network temporary identifier (C-RNTI).
(3) A load size (payload size) of DCI scheduling PUSCH. That is, the load size of DCI scheduling PUSCH may indicate the priority of PUSCH.
For example, if the DCI payload size for scheduling PUSCH #1 is smaller than the DCI payload size for scheduling PUSCH #2, it is considered that the priority of PUSCH #1 is higher and the priority of PUSCH #2 is lower. For another example, if the load size of the DCI scheduling PUSCH #1 is greater than or equal to a certain preset threshold, the priority of the PUSCH is considered to be lower, otherwise, the priority is higher.
(4) MCS table adopted for PUSCH. That is, the MCS table employed by the PUSCH may indicate the priority of the PUSCH.
For example, if the PUSCH uses the MCS table with low spectral efficiency, the priority of the PUSCH is considered to be high. When the PUSCH uses a MCS table with high spectral efficiency or includes an MCS table with a modulation scheme of 256QAM, the PUSCH is considered to have a low priority.
(5) A DCI field in the DCI of the PUSCH is scheduled. That is, the priority of the PUSCH may be indicated by a value in one DCI domain in the DCI scheduling the PUSCH. The DCI field may include 1 bit or a plurality of bits.
The indication manner of the priority of the UCI is similar to that of the PUSCH, except that the priority of the UCI may be the priority of the PDSCH corresponding to the UCI, and the meaning of the UCI (or PUCCH) corresponding to the PDSCH may be as described above. At this time, DCI scheduling PUCCH here means DCI scheduling PDSCH corresponding to PUCCH.
It is to be understood that determining the priority of the PUSCH may be replaced with determining any of (1) to (5) above. Similarly, determining the priority of UCI may instead be determined similarly to any of (1) to (5) above.
Optionally, as an embodiment of the present application, the method may further include:
and S260, the terminal equipment loads the UCI on at least one second target channel to be sent. Accordingly, the network device receives the UCI on the at least one second target channel.
The at least one second target channel is at least one PUSCH of the N PUSCHs, and the second target channel is later in time domain than the first target channel, or the first target channel is earlier in time domain than the second target channel. It should be understood that the second target channel is later than the first target channel in the sense that the time-frequency resources carrying the second target channel are located behind the time-frequency resources carrying the first target channel in the time domain. It is to be understood that the uplink data channels subsequent to the first target channel of the N uplink data channels all satisfy the first condition.
Specifically, the terminal device may transmit the UCI on the PUSCH subsequent to the first target channel, i.e., repeatedly transmit the UCI, in addition to transmitting the UCI on the first target channel.
Therefore, by repeatedly transmitting UCI using the inherent repetition of the PUSCH, the transmission reliability of UCI can be further improved.
For example, the terminal device may transmit UCI on each PUSCH after the first target channel in the N PUSCHs, and may also transmit UCI on a partial PUSCH after the first target channel.
For example, for a scenario where the first target channel is not limited to be overlapped with the PUCCH in the time domain, the terminal device may transmit UCI on each PUSCH after the first target channel. As another example, for a scenario in which the first target channel needs to overlap the PUCCH in the time domain, the terminal device may transmit the UCI on the PUSCH after the first target channel that overlaps the PUCCH in the time domain, i.e., the second target channel overlaps the PUCCH in the time domain. This is explained in conjunction with fig. 9 and 11 described above. In fig. 9, if the first target channel is PUSCH #3, the terminal apparatus may also transmit the UCI on PUSCH # 4. In fig. 11, if the first target channel is PUSCH #2, the terminal apparatus may also transmit the UCI on PUSCH # 3. It should be understood that, in fig. 11, further, the terminal device may also transmit the UCI on PUSCH #4, which is not limited in this application.
In this application, the resource occupied by the UCI on the first target channel and/or the second target channel may be determined by an offset value beta-offset. The beta-offset can be notified to the terminal equipment through DCI of the scheduling PUCCH, and can also be configured to the terminal equipment through high-level parameters.
In summary, based on the method of the present application, it is not necessary that the N PUSCHs all satisfy the timeline condition, and as long as there is a PUSCH that satisfies the timeline condition that UCI is multiplexed and transmitted on the PUSCH among the N PUSCHs, UCI carried on the PUCCH may be transmitted on one or more PUSCHs that satisfy the timeline condition.
In another prior art, when a slot-based PUCCH repetition and a mini-slot-based PUSCH repetition overlap in a time domain, the PUCCH is transmitted while the PUSCH is dropped and not transmitted. That is, when a plurality of mini-slot based PUSCHs repeatedly transmitting the same data block and a plurality of PUCCH based on slots repeatedly transmitting the same UCI overlap in a time domain, the related art may drop the PUSCH and transmit the PUCCH. This approach may reduce the reliability of the transmission. For example, if the URLLC traffic is transmitted on the PUSCH, or the traffic priority of the PUSCH transmission is higher than that of the PUCCH transmission, the transmission according to the prior art may result in the reliability of the URLLC traffic transmission being reduced.
The description will be given by taking fig. 12 as an example. The network device may configure PUSCH retransmission, i.e. multiple PUSCHs repeat transmitting the same transport block, by either triggering signaling indication or by configuration signaling. When the repeated transmission crosses a slot boundary, the PUSCH crossing the boundary automatically becomes a two PUSCH repeated transmission. For example, as shown in fig. 12, the network device configures 4 PUSCH repeated transmissions by a trigger signaling indication or by a configuration signaling, where PUSCH #2 and PUSCH #3 are two repeated transmissions divided by a slot boundary. Thus, PUSCH #1 to PUSCH #5 need to be transmitted. The network device may also configure repeated transmission of PUCCH, for example, PUCCH repeated transmission in slot #1 to slot #4 shown in fig. 12, i.e., PUCCH #1 to PUCCH #4, by a trigger signaling indication or by a configuration signaling. It can be seen that, in slot #1 and slot #2, the time-frequency resource carrying PUSCH and the time-frequency resource carrying PUCCH overlap in time domain, and according to the technique, the PUSCH overlapping with the PUCCH, i.e. PUSCH #1, PUSCH #2, PUSCH #4, and PUSCH #5, of PUSCH #1 to PUSCH #5 is discarded.
The method described above can solve the problem, thereby avoiding dropping of the PUSCH and improving reliability of transmission. Taking fig. 12 as an example, for slot #1 and slot #2, the UCI carried on PUCCH may be carried on PUSCH for transmission by the method described above.
Specifically, for slot #1, the time-frequency resource carrying PUCCH #1 is the first time-frequency resource in the foregoing, the sum of the time-frequency resource carrying PUSCH #1 and the time-frequency resource carrying PUSCH #2 is the second time-frequency resource in the foregoing, PUCCH #1 is the PUCCH in the foregoing, and PUSCH #1 and PUSCH #2 are the N PUSCHs in the foregoing. It can be seen that the first time frequency resource and the second time frequency resource overlap. In this case, if there is a PUSCH satisfying the first condition out of the PUSCHs #1 and #2, UCI originally carried on the PUCCH #1 may be carried on the first target channel and transmitted. As can be seen from the foregoing description, the first target channel may be any one of PUSCH #1 and PUSCH #2 that satisfies the first condition, or may be the earliest PUSCH that satisfies the first condition among PUSCH #1 and PUSCH # 2. Alternatively, the first target channel may be any one of PUSCH #1 and PUSCH #2 that overlaps with the PUCCH in the time domain and satisfies the first condition, or may be the earliest PUSCH among PUSCH #1 and PUSCH #2 that overlaps with the PUCCH in the time domain and satisfies the first condition. For example, if PUSCH #2 satisfies the first condition, UCI may be carried on PUSCH #2 for transmission. For example, when both PUSCH #1 and PUSCH #2 satisfy the first condition, UCI may be piggybacked on PUSCH #1 for transmission. It is to be appreciated that in addition to transmitting UCI on a first target channel, as described above, UCI may further be transmitted on at least one second target channel. The definition of the second target channel is as described above and will not be described herein.
Similarly, for slot #2, the sum of the time-frequency resources carrying PUSCH #3 to PUSCH #5 is the second time-frequency resource in the foregoing, the time-frequency resource carrying PUCCH #2 is the first time-frequency resource in the foregoing, PUSCH #3 to PUSCH #5 are the N PUSCHs in the foregoing, and PUCCH #2 is the PUCCH in the foregoing. The first time frequency resource and the second time frequency resource are overlapped, and if the PUSCHs meeting the first condition exist in the PUSCHs #3 to #5, the UCI can be borne on the first target channel to be transmitted. Here, the first target channel may be any one of PUSCH #3 to PUSCH #5 that satisfies the first condition, or may be the earliest PUSCH among PUSCH #3 to PUSCH #5 that satisfies the first condition. Alternatively, the first target channel may be any one of PUSCH #3 to PUSCH #5 that overlaps with the PUCCH in the time domain and satisfies the first condition, or may be the earliest PUSCH among PUSCH #3 to PUSCH #5 that overlaps with the PUCCH in the time domain and satisfies the first condition. For example, when the first condition is satisfied and the earliest PUSCH among the PUSCHs #3 to #5 is PUSCH #4, UCI may be piggybacked on PUSCH #4 and transmitted. It should be understood that, in addition to transmitting UCI on the first target channel, as described above, further, UCI may be transmitted on at least one second target channel, such as PUSCH # 5. The definition of the second target channel is as described above and will not be described herein.
Fig. 13 shows another example in which a slot-based PUCCH repetition and a mini-slot-based PUSCH repetition overlap in a time domain. Referring to fig. 13, the time-frequency resource bearing the PUCCH #1 is the first time-frequency resource, the sum of the time-frequency resources bearing the PUSCHs #1 to PUSCH #4 is the second time-frequency resource, the PUCCH #1 is the PUCCH, and the PUSCHs #1 to PUSCH #4 are the N PUSCHs. It can be seen that in slot #1, the first time-frequency resource and the second time-frequency resource overlap. For the slot #1, the UCI carried on the PUCCH #1 may be transmitted by using the method described above, which may specifically refer to the description above and is not described herein again.
In addition, the prior art does not relate to the problem of how to transmit UCI carried on a slot-based PUCCH in a scenario where the PUCCH repetition and a mini-slot-based or slot-based PUSCH overlap in the time domain.
Based on the method, the application also provides a method for transmitting the method information. In this method, if a certain PUCCH in the PUSCH and PUCCH repetition overlaps in the time domain and the priority of UCI that should be carried on the PUCCH is not higher than the priority of the PUSCH, the UCI may be carried on the PUSCH and transmitted when the PUSCH and the PUCCH overlapping in the time domain satisfy the first condition. By the scheme for transmitting the UCI, the UCI can be transmitted.
It should be understood that how to determine the priority of the PUSCH and the priority of the UCI specifically may refer to the description of the priority of the PUSCH and the priority of the UCI above, and details are not repeated here. The first condition can also be seen in the foregoing description.
Specifically, the method may comprise the steps of:
step one, terminal equipment determines time-frequency resources bearing a plurality of PUCCHs.
Wherein the plurality of PUCCHs are used for transmitting the same UCI. The plurality of PUCCHs are in one-to-one correspondence with a plurality of time units, i.e., one PUCCH may be transmitted per time unit.
The time-frequency resource carrying multiple PUCCHs can be configured to the terminal device by the network device through a trigger signaling indication or through a configuration signaling. It should be understood that the network device may indicate, to the terminal device, the time-frequency resource carrying the multiple PUCCHs by configuring the time-frequency resource for transmitting one PUCCH and the number of repeated transmissions. In addition, the network device may also indicate the time-frequency resource carrying each PUCCH to the terminal device. The method and the device for configuring the time-frequency resources bearing the PUCCHs to the terminal equipment are not limited, and the method and the device for configuring the time-frequency resources bearing the PUCCHs are reasonable.
And step two, the terminal equipment determines the time-frequency resource bearing the PUSCH.
The PUSCH and a first PUCCH in the plurality of PUCCHs belong to the same time unit, or the time-frequency resource bearing the PUSCH and the time-frequency resource bearing the first PUCCH belong to the same time unit in a time domain. The first PUCCH may be any one of the plurality of PUCCHs. And the time frequency resource bearing the PUSCH is overlapped with the time frequency resource bearing the first PUSCH in the time domain. It should be understood that the overlapping here has the same meaning as the overlapping described above and will not be described again.
The network device may configure the time-frequency resource carrying the PUSCH to the terminal device through a trigger signaling indication or through a configuration signaling. For details, reference may be made to the description of the method 200, which is not described herein again.
And step three, the network equipment determines the time-frequency resources bearing the PUCCHs.
And step four, the network equipment determines the time-frequency resource bearing the PUSCH.
And step five, if the priority of the UCI is not higher than that of the PUSCH and the PUSCH meets a first condition, carrying the UCI carried on the first PUCCH on the PUSCH for sending. Accordingly, the network device receives the UCI on the PUSCH.
Specifically, if the priority of the UCI is not higher than the priority of the PUSCH, and if the PUSCH and the first PUCCH overlap in the time domain and the PUSCH and the first PUCCH satisfy the first condition, the UCI that is originally carried on the PUCCH is transmitted on the PUSCH, and the first PUCCH is discarded.
In summary, according to the method for transmitting uplink information provided by the present application, when a PUSCH overlaps with a PUCCH in a plurality of PUCCHs in a time domain, if the priority of UCI originally carried on the PUCCH is not higher than the priority of the PUSCH and the PUCCH overlapping with the PUSCH in the time domain satisfy a first condition, the UCI is carried on the PUSCH and transmitted. By the method, the transmission of the PUSCH and the UCI can be realized under the scene that the repeated transmission of the PUSCH and the PUSCH is overlapped on the time domain.
This is illustrated in connection with fig. 14. Referring to fig. 14, that is, the network device may configure the terminal device to repeatedly transmit the same information on PUCCH #1 to PUCCH #4 and may configure the terminal device to transmit uplink data on PUSCH # 1. As can be seen, PUCCH #1 to PUCCH #4 and PUSCH #1 overlap in time domain, or in other words, the time-frequency resources for carrying PUCCH #1 to PUCCH #4 and the time-frequency resources for carrying PUSCH #1 overlap in time domain. In this case, if PUSCH #1 satisfies the first condition, the UCI that should be piggybacked on the PUCCH that overlaps PUSCH #1 in the time domain may be piggybacked on PUSCH #1 for transmission, that is, the UCI that should be piggybacked on PUCCH #2 may be piggybacked on PUSCH #1 for transmission, and PUCCH #2 may be discarded.
It should be understood that the determination of whether the first condition is satisfied in the method described herein is granular in time units, i.e., determination of whether PUSCH #1 satisfies the first condition is only performed in slot #2 in fig. 14, or we only care about the time length between the first symbol of PUSCH #1 and PUCCH #2 and the corresponding PDSCH and PDCCH, and do not care about the time length between the other PUCCH and PUSCH and the corresponding PDSCH and PDCCH.
In another scenario, the network device may configure, through trigger signaling or through configuration signaling, a PUCCH carrying UCI to be transmitted in one time unit, and also transmit multiple PUSCHs in the time unit, where at least two PUSCHs of the multiple PUSCHs are used to carry different traffic type data, or the priorities (or referred to as transmission priorities) of the at least two PUSCHs are different, and the PUCCH and each PUSCH of the multiple PUSCHs overlap in a time domain. For this scenario, how the terminal device transmits PUSCH and PUCCH is not involved in the prior art.
Based on this, the present application provides another method for transmitting uplink information. This method is explained below with reference to fig. 15 to 22.
Fig. 15 is an exemplary flowchart of another method 300 for transmitting uplink information provided herein. The method 300 may include S310 to S370. The steps will be described below.
S310, the terminal equipment determines the service information of the UCI to be sent on the PUCCH.
S320, the terminal equipment determines the service information of each PUSCH in the M PUSCHs.
Wherein, the service information is service type or priority. The service information of at least two PUSCHs in the M PUSCHs is different. For example, at least two PUSCHs of the M PUSCHs have different traffic types or different priorities. Moreover, each PUSCH overlaps with a PUCCH in the time domain, and the overlapping meaning is the same as that described above, and is not described again. And the M PUSCHs and the PUCCH belong to the same time unit.
The representation manner or the indication manner of the priority of the UCI and the PUSCH may refer to the description of the priority of the UCI and the PUSCH, and is not described herein again. Here, how to indicate the traffic types of the PUSCH and PUCCH is mainly described.
Alternatively, the traffic type of the PUSCH may be indicated by any of the following information:
(1) length of time unit for PUSCH scheduling. That is, the length of the time unit of the PUSCH schedule may indicate the traffic type of the PUSCH.
For example, if the time unit of PUSCH scheduling is a mini-slot, the traffic type of PUSCH is considered to be URLLC, and if the time unit of PUSCH scheduling is a slot, the traffic type of PUSCH is considered to be eMBB.
(2) And scrambling RNTI of DCI for scheduling PUSCH. That is, the type of RNTI scrambling DCI scheduling PUSCH may indicate the traffic type of PUSCH.
For example, if the RNTI of the DCI for scrambling and scheduling the PUSCH is the first RNTI, the service type of the PUSCH is considered to be URLLC. The first RNTI may be, for example, MCS-C-RNTI or CS-RNTI. And if the RNTI of the DCI for scrambling and scheduling the PUSCH is the second RNTI, the service type of the PUSCH is considered to be eMBB. Wherein the second RNTI is of a different type than the first RNTI. The second RNTI may be, for example, a C-RNTI.
(3) A load size (payload size) of DCI scheduling PUSCH. That is, the load size of the DCI scheduling the PUSCH may indicate the traffic type of the PUSCH.
For example, if the DCI load size for scheduling PUSCH #1 is smaller than the DCI load size for scheduling PUSCH #2, PUSCH #1 is considered to be the URLLC traffic and PUSCH #2 is considered to be the eMBB traffic. For another example, if the load size of the DCI scheduling PUSCH #1 is greater than or equal to a certain preset threshold, the service type of PUSCH is considered as eMBB, otherwise, it is URLLC.
(4) MCS table adopted for PUSCH. That is, the MCS table employed by the PUSCH may indicate the traffic type of the PUSCH.
For example, if the PUSCH uses the MCS table with low spectral efficiency, the traffic type of the PUSCH is considered to be URLLC. If the PUSCH uses a MCS table with high spectral efficiency or includes an MCS table with a modulation scheme of 256QAM, the traffic type of the PUSCH is considered to be eMBB.
(5) A DCI field in the DCI of the PUSCH is scheduled. That is, the traffic type of the PUSCH may be indicated by a value in one graduation field in DCI scheduling the PUSCH. The DCI field may include 1 bit or a plurality of bits.
The indication manner of the UCI service type is similar to that of the PUSCH service type, and the difference is that the UCI service type may be a PDSCH service type corresponding to the UCI, and the corresponding meaning of the UCI and the PDSCH may be as described above. At this time, the DCI scheduling the PUCCH here means DCI scheduling the PDSCH.
It is to be understood that determining the traffic type of PUSCH may instead determine any of (1) through (5) above. Similarly, determining the traffic type of the UCI may be replaced with determining any of the similar (1) to (5) above.
S330, the terminal equipment determines a target PUSCH from the M PUSCHs according to the service information of the UCI and the service information of each PUSCH.
Wherein, the target PUSCH is a PUSCH multiplexed by the UCI, and the UCI can be carried on the target PUSCH and transmitted.
S340, the network device determines the service information of each PUSCH.
Optionally, the network device may determine the service information of the PUSCH according to the service request from the terminal device.
S350, the network device determines the service information of the UCI.
Optionally, the network device may determine the service information of the UCI according to the service information of the downlink data corresponding to the UCI.
S340 corresponds to S310, and S350 corresponds to S320, and how to determine the service information of the UCI and the service information of each PUSCH by the network device may refer to the above description of S310 and S320, which is not described herein again.
And S360, the network equipment determines the target PUSCH from the M PUSCHs according to the service information of the UCI and the service information of each PUSCH.
If the target PUSCH exists, the method may further include:
and S370, the terminal equipment carries the UCI on the target PUSCH for transmission. Accordingly, the network device receives the UCI on the target PUSCH.
Specifically, in the case that the PUCCH overlaps with multiple PUSCHs, the terminal device may determine the PUSCH multiplexed by the UCI according to the traffic type of the UCI and the traffic type of each PUSCH originally carried on the PUCCH, or according to the priority of the UCI and the priority of each PUSCH. Accordingly, the terminal device may drop the PUCCH and transmit the UCI on the PUSCH multiplexed by the UCI.
According to the method for transmitting the uplink information, the PUSCH multiplexed by the UCI is determined according to the service type or the priority, and more reasonable transmission can be performed under the condition that the PUCCH and a plurality of PUSCHs are overlapped. For example, it may be ensured that the transmission of information with higher priority is ensured as much as possible, or the transmission of a service with higher requirements on reliability and delay is ensured as much as possible, or the transmission of UCI is ensured as much as possible, so that the network device may obtain the transmitted feedback information in time.
In this application, the resource occupied by the UCI on the target channel may be determined by an offset value beta-offset. The beta-offset can be notified to the terminal equipment through DCI of the scheduling PUCCH, and can also be configured to the terminal equipment through high-level parameters.
Hereinafter, two ways of determining the PUSCH according to the priority and determining the target PUSCH according to the traffic type will be described.
First, determining target PUSCH according to priority
In this manner, the target PUSCH may be one of the M PUSCHs that satisfies the following condition:
the first condition is as follows: the priority is not higher than the UCI.
And a second condition: a first condition is satisfied.
That is, the target PUSCH may be one of the M PUSCHs having a priority not higher than the UCI and satisfying a first condition. Wherein the meaning of the first condition is as described hereinbefore.
Illustratively, referring to fig. 16, the M PUSCHs are PUSCH #1 and PUSCH #2, and if the priorities of PUSCH #1 and PUSCH #2 are not higher than the UCI and both PUSCH #1 and PUSCH #2 satisfy the first condition, the target PUSCH may be PUSCH #1 or PUSCH # 2.
Referring to fig. 17, the M PUSCHs are PUSCH #1 to PUSCH #3, and if the priority of PUSCH #1 is higher than that of UCI, the priorities of PUSCH #2 and PUSCH #3 are not higher than that of UCI, and both PUSCH #2 and PUSCH #3 satisfy the first condition, the target PUSCH may be PUSCH #2 or PUSCH # 3.
Further, the target PUSCH also needs to satisfy at least one of the following conditions:
and (3) carrying out a third condition: the earliest was.
And a fourth condition: the lowest priority.
That is, the target PUSCH may be the earliest PUSCH among all PUSCHs of the M PUSCHs having a priority not higher than the UCI and satisfying the first condition.
Taking fig. 16 as an example, if the priorities of PUSCH #1 and PUSCH #2 are not higher than the UCI, and both PUSCH #1 and PUSCH #2 satisfy the first condition, the target PUSCH may be PUSCH # 1.
Taking fig. 17 as an example, if the priority of PUSCH #1 is higher than the priority of UCI, the priorities of PUSCH #2 and PUSCH #3 are not higher than the UCI, and both PUSCH #2 and PUSCH #3 satisfy the first condition, the target PUSCH may be PUSCH # 2.
Alternatively, the target PUSCH may be the PUSCH of the M PUSCHs that satisfies the first condition and has a priority not higher than the lowest priority among all PUSCHs in the UCI.
Taking fig. 16 as an example, if the priorities of PUSCH #1 and PUSCH #2 are not higher than the UCI, and both PUSCH #1 and PUSCH #2 satisfy the first condition, and the priority of PUSCH #1 is higher than that of PUSCH #2, the target PUSCH may be PUSCH # 2.
Taking fig. 17 as an example, if the priorities of PUSCH #1 to PUSCH #3 are not higher than the UCI, PUSCH #1 does not satisfy the first condition, PUSCH #2 and PUSCH #3 both satisfy the first condition, and PUSCH #3 has a higher priority than PUSCH #2, the target PUSCH may be PUSCH # 2.
Alternatively, the target PUSCH may be the earliest PUSCH which has the lowest priority among the M PUSCHs which is not higher than the UCI and satisfies the first condition.
Taking fig. 16 as an example, if the priorities of PUSCH #1 and PUSCH #2 are not higher than the UCI, and both PUSCH #1 and PUSCH #2 satisfy the first condition, and the priority of PUSCH #1 is higher than that of PUSCH #2, the target PUSCH may be PUSCH # 2.
Taking fig. 17 as an example, if all of the priorities of PUSCH #1 to PUSCH #3 are not higher than the UCI, all of PUSCH #1 to PUSCH #3 satisfy the first condition. If the priority of PUSCH #1 is higher than that of PUSCH #2, and the priority of PUSCH #2 is the same as that of PUSCH #3, the target PUSCH may be PUSCH # 2. The target PUSCH may be PUSCH #3 if PUSCH #1 is higher in priority than PUSCH #2 and PUSCH #2 is higher in priority than PUSCH # 3.
In one possible implementation, if all of the M PUSCHs satisfy the first condition and all of the M PUSCHs do not satisfy the second condition, the M PDSCHs are discarded, and the UCI is transmitted on the PUCCH.
Taking fig. 16 as an example, if the priority of both PUSCH #1 and PUSCH #2 is not higher than the UCI, but both PUSCH #1 and PUSCH #2 do not satisfy the first condition, the UCI is transmitted, and PUSCH #1 and PUSCH #2 are discarded.
In one possible implementation, if the UCI has the lowest priority, the UCI is discarded and the M PUSCHs are transmitted. That is, if the priority of the UCI is the lowest among the M PUSCHs and the UCI, the UCI is discarded.
Taking fig. 16 as an example, if both PUSCH #1 and PUSCH #2 have higher priority than the UCI, the UCI is discarded and PUSCH #1 and PUSCH #2 are transmitted.
Mode two, determining target PUSCH according to service type
In this manner, the case will be described according to the difference in the traffic type of the UCI.
The first condition is as follows: the service type of the UCI is URLLC.
At this time, the target PUSCH may be one of the M PUSCHs that satisfies the first condition.
Further, the target PUSCH may be the earliest PUSCH of the M PUSCHs that meets the first condition.
That is, if the traffic type of the UCI is URLLC, the UCI may be transmitted on the PUSCH regardless of the traffic type of the PUSCH being RULLC or eMBB as long as the PUSCH satisfies the first condition. Further, the PUSCH transmitting the UCI may be the earliest PUSCH among all PUSCHs satisfying the first condition.
Illustratively, referring to fig. 18, the M PUSCHs are PUSCH #1 and PUSCH #2, and the traffic type of UCI is URLLC. And the target PUSCH may be PUSCH #1 or PUSCH #2, or the earliest PUSCH among PUSCH #1 and PUSCH #2, that is, PUSCH #1, if both PUSCH #1 and PUSCH #2 satisfy the first condition. In fig. 18, the service type of PUSCH #1 may be URLLC or eMBB; the traffic type of PUSCH #2 may be URLLC or eMBB.
Referring to fig. 19, the M PUSCHs are PUSCH #1 to PUSCH #3, and the traffic type of UCI is URLLC. And both the PUSCH #1 and the PUSCH #2 do not satisfy the first condition, and the PUSCH #3 satisfies the first condition, the target PUSCH may be PUSCH # 3. In fig. 19, the service type of PUSCH #1 may be URLLC or eMBB; the service type of the PUSCH #2 can be URLLC or eMBB; the traffic type of PUSCH #3 may be URLLC or eMBB.
Case two: the UCI service type is eMBB.
At this time, the target PUSCH may be one of the M PUSCHs that satisfies the first condition and has a traffic type of eMBB.
Further, the target PUSCH may be the earliest PUSCH among the M PUSCHs with the traffic type of eMBB that satisfies the first condition.
Illustratively, referring to fig. 20, the M PUSCHs are PUSCH #1 and PUSCH #2, and the traffic type of UCI is eMBB. And both the PUSCH #1 and the PUSCH #2 meet the first condition, the service type of the PUSCH #1 is eMBB, the service type of the PUSCH #2 is URLLC, and then the target PUSCH can be the PUSCH # 1.
Referring to fig. 21, the M PUSCHs are PUSCH #1 to PUSCH #3, and the traffic type of UCI is eMBB. And the PUSCH #1 to the PUSCH #3 all satisfy the first condition, the traffic type of the PUSCH #1 is URLLC, the traffic types of the PUSCH #2 and the PUSCH #3 are eMBB, the target PUSCH may be PUSCH #2 or PUSCH #3, or the target PUSCH may be the earliest PUSCH among the PUSCH #2 and PUSCH #3, that is, PUSCH # 2.
In a possible implementation manner, if none of the M PUSCHs satisfies the first condition or none of the traffic types is eMBB, the UCI is discarded and the PUCCH is not sent.
For example, in fig. 20, if neither PUSCH #1 nor PUSCH #2 satisfies the first condition, the PUCCH carrying the UCI is discarded, and PUSCH #1 and PUSCH #2 are transmitted.
For another example, referring to fig. 22, the M PUSCHs are PUSCH #1 and PUSCH #2, and the traffic type of UCI is eMBB. And if the service types of the PUSCH #1 and the PUSCH #2 are URLLC, discarding the PUCCH carrying the UCI, and transmitting the PUSCH #1 and the PUSCH # 2.
The method provided by the present application is described above mainly in conjunction with fig. 2 to 22. The apparatus provided by the present application will be described below.
Fig. 23 is a schematic block diagram of a communication device provided in an embodiment of the present application. As shown in fig. 23, the communication device 400 may include a processing module 410 and a transceiver module 420.
In one possible design, the communication apparatus 400 may correspond to the terminal device in the above method embodiment, and may be, for example, the terminal device or a chip configured in the terminal device. When the communication device is a terminal equipment, the processing module may be a processor and the transceiver module may be a transceiver. The communication device may further comprise a storage module, which may be a memory. The storage module is used for storing instructions, and the processing module executes the instructions stored by the storage module so as to enable the communication device to execute the method. When the communication device is a chip in a terminal device, the processing module may be a processor, and the transceiver module may be an interface circuit, an input/output interface, a pin or a circuit, etc.; the processing module executes the instructions stored in the storage module (e.g., register, cache, etc.) to make the communication device execute the operations executed by the terminal device in the methods, and the storage module may be a storage module (e.g., read only memory, random access memory, etc.) in the chip or a storage module (e.g., read only memory, random access memory, etc.) outside the chip in the communication device
In one implementation, the modules and other operations and/or functions described above in the communication apparatus 400 are for implementing the corresponding flows of the method in fig. 4. Specifically, the processing module 410 may be configured to perform S210 to S220 in the method shown in fig. 4, and the transceiver module 420 may be configured to perform S250 and S260 in the method shown in fig. 4.
In another implementation, the modules and other operations and/or functions described above in the communication device are implemented to realize the corresponding flow of the method including the steps one to five above. Specifically, the processing module 410 may be configured to perform the first step and the second step, and the transceiver module 420 may be configured to perform the fifth step.
In yet another implementation, the modules and other operations and/or functions described above in the communication apparatus 400 are for implementing the corresponding flows of the method in fig. 15. Specifically, the processing module 410 may be configured to perform S310 to S330 in the method shown in fig. 15, and the transceiver module 420 may be configured to perform S370 in the method shown in fig. 15.
In another possible design, the communication apparatus 400 may correspond to the network device in the above method embodiment, and may be, for example, a network device or a chip configured in a network device. When the communication device is a network device, the processing module may be a processor and the transceiver module may be a transceiver. The communication device may further comprise a storage module, which may be a memory. The storage module is used for storing instructions, and the processing module executes the instructions stored by the storage module so as to enable the communication device to execute the method. When the communication device is a chip within a network device, the processing module may be a processor, and the transceiver module may be an interface circuit, an input/output interface, a pin or a circuit, etc.; the processing module executes instructions stored in a storage module (e.g., a register, a cache, etc.) inside the chip or a storage module (e.g., a read-only memory, a random access memory, etc.) outside the chip in order to make the communication device perform the operations performed by the network device in the method.
In one implementation, the modules and other operations and/or functions described above in the communication apparatus 400 are for implementing the corresponding flows of the method in fig. 4. Specifically, the processing module 410 may be configured to perform S230 to S240 in the method shown in fig. 4, and the transceiver module 420 may be configured to perform S250 and S260 in the method shown in fig. 4.
In another implementation, the modules and other operations and/or functions described above in the communication device are implemented to realize the corresponding flow of the method including the steps one to five above. Specifically, the processing module 410 may be configured to perform step three and step four, and the transceiver module 420 may be configured to perform step five.
In yet another implementation, the modules and other operations and/or functions described above in the communication apparatus 400 are for implementing the corresponding flows of the method in fig. 15. Specifically, the processing module 410 may be configured to execute S340 to S360 in the method shown in fig. 15, and the transceiver module 420 may be configured to execute S370 in the method shown in fig. 15.
The network device in the foregoing various apparatus embodiments completely corresponds to the network device or the terminal device in the terminal device and method embodiments, and the corresponding module or unit executes the corresponding steps, for example, the transceiver module (transceiver) method executes the steps of transmitting and/or receiving in the method embodiments, and other steps except for transmitting and receiving may be executed by the processing module (processor). The functions of the specific elements may be referred to in the respective method embodiments. The transceiver module may include a transmitting unit and/or a receiving unit, and the transceiver may include a transmitter and/or a receiver, which implement transceiving functions respectively; the processing module can be one or more.
It should be understood that the above-described division of the respective modules is only a functional division, and other division methods may be possible in actual implementation.
The terminal device or the network device may be a chip, the processing module may be implemented by hardware or software, and when implemented by hardware, the processing module may be a logic circuit, an integrated circuit, or the like; when implemented in software, the processing module may be a general-purpose processor implemented by reading software code stored in a memory module, which may be integrated with the processor or located external to the processor, and may exist separately.
Fig. 24 is a schematic structural diagram of a terminal device 10 provided in the present application. For convenience of explanation, fig. 24 shows only main components of the terminal device. As shown in fig. 24, the terminal device 10 includes a processor, a memory, a control circuit, an antenna, and an input-output means.
The processor is mainly configured to process the communication protocol and the communication data, control the entire terminal device, execute a software program, and process data of the software program, for example, to support the terminal device to perform the actions described in the above method embodiments. The memory is used primarily for storing software programs and data. The control circuit is mainly used for converting baseband signals and radio frequency signals and processing the radio frequency signals. The control circuit and the antenna together, which may also be called a transceiver, are mainly used for transceiving radio frequency signals in the form of electromagnetic waves. Input and output devices, such as touch screens, display screens, keyboards, etc., are used primarily for receiving data input by a user and for outputting data to the user.
When the terminal device is turned on, the processor can read the software program in the storage unit, interpret and execute the instruction of the software program, and process the data of the software program. When data needs to be sent wirelessly, the processor outputs a baseband signal to the radio frequency circuit after performing baseband processing on the data to be sent, and the radio frequency circuit performs radio frequency processing on the baseband signal and sends the radio frequency signal outwards in the form of electromagnetic waves through the antenna. When data is sent to the terminal equipment, the radio frequency circuit receives radio frequency signals through the antenna, converts the radio frequency signals into baseband signals and outputs the baseband signals to the processor, and the processor converts the baseband signals into the data and processes the data.
Those skilled in the art will appreciate that fig. 24 shows only one memory and processor for ease of illustration. In an actual terminal device, there may be multiple processors and memories. The memory may also be referred to as a storage medium or a storage device, and the like, which is not limited in this application.
As an alternative implementation manner, the processor may include a baseband processor and a central processing unit, where the baseband processor is mainly used to process a communication protocol and communication data, and the central processing unit is mainly used to control the whole terminal device, execute a software program, and process data of the software program. The processor in fig. 24 integrates the functions of the baseband processor and the central processing unit, and those skilled in the art will understand that the baseband processor and the central processing unit may be independent processors, and are interconnected through a bus or the like. Those skilled in the art will appreciate that the terminal device may include a plurality of baseband processors to accommodate different network formats, the terminal device may include a plurality of central processors to enhance its processing capability, and various components of the terminal device may be connected by various buses. The baseband processor can also be expressed as a baseband processing circuit or a baseband processing chip. The central processing unit can also be expressed as a central processing circuit or a central processing chip. The function of processing the communication protocol and the communication data may be built in the processor, or may be stored in the storage unit in the form of a software program, and the processor executes the software program to realize the baseband processing function.
For example, in the embodiment of the present application, the antenna and the control circuit having the transceiving function may be regarded as the transceiving unit 101 of the terminal device 10, and the processor having the processing function may be regarded as the processing unit 102 of the terminal device 10. As shown in fig. 24, the terminal device 10 includes a transceiving unit 101 and a processing unit 102. A transceiver unit may also be referred to as a transceiver, a transceiving device, etc. Optionally, a device for implementing a receiving function in the transceiver 101 may be regarded as a receiving unit, and a device for implementing a transmitting function in the transceiver 101 may be regarded as a transmitting unit, that is, the transceiver 101 includes a receiving unit and a transmitting unit. For example, the receiving unit may also be referred to as a receiver, a receiving circuit, etc., and the sending unit may be referred to as a transmitter, a transmitting circuit, etc.
The terminal device shown in fig. 24 can perform each action performed by the terminal device in the above method, and here, a detailed description thereof is omitted to avoid redundancy.
Fig. 25 is a schematic structural diagram of a network device provided in the present application, where the network device may be a base station, for example. Such as
As shown in fig. 25, the base station may be applied to the communication system shown in fig. 1, and performs the functions of the network device in the above method embodiments. The base station 20 may include one or more radio frequency units, such as a Remote Radio Unit (RRU) 201 and one or more baseband units (BBUs) (which may also be referred to as Digital Units (DUs)) 202. The RRU 201 may be referred to as a transceiver unit, transceiver circuit, or transceiver, etc., which may include at least one antenna 2011 and a radio unit 2012. The RRU 201 is mainly used for transceiving radio frequency signals and converting radio frequency signals and baseband signals, for example, for sending the BFR configuration of the above method embodiment. The BBU 202 is mainly used for performing baseband processing, controlling a base station, and the like. The RRU 201 and the BBU 202 may be physically disposed together or may be physically disposed separately, that is, distributed base stations.
The BBU 202 is a control center of a base station, and may also be referred to as a processing unit, and is mainly used for performing baseband processing functions, such as channel coding, multiplexing, modulation, spreading, and the like. For example, the BBU (processing unit) 202 can be used to control the base station to execute the operation flow related to the network device in the above method embodiment.
In an embodiment, the BBU 202 may be formed by one or more boards, and the boards may jointly support a radio access network (e.g., an LTE network) with a single access indication, or may respectively support radio access networks with different access schemes (e.g., an LTE network, a 5G network, or other networks). The BBU 202 also includes a memory 2021 and a processor 2022, the memory 2021 for storing the necessary instructions and data. The processor 2022 is configured to control the base station to perform necessary actions, for example, to control the base station to perform the operation procedures related to the network device in the above method embodiments. The memory 2021 and the processor 2022 may serve one or more boards. That is, the memory and processor may be provided separately on each board. Multiple boards may share the same memory and processor. In addition, each single board can be provided with necessary circuits.
The network device is not limited to the above-described embodiment, and may be in another embodiment: for example: the antenna comprises a BBU (baseband unit) and an Adaptive Radio Unit (ARU), or the BBU and an Active Antenna Unit (AAU); the CPE may be a Customer Premise Equipment (CPE) or another type, and the present application is not limited thereto.
It should be noted that the processor in the embodiments of the present application may be an integrated circuit chip having signal processing capability. In implementation, the steps of the above method embodiments may be performed by integrated logic circuits of hardware in a processor or instructions in the form of software. The processor may 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 device, discrete gate or transistor logic device, or discrete hardware components. The various methods, steps, and logic blocks disclosed in the embodiments of the present application may be implemented or performed. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of the method disclosed in connection with the embodiments of the present application may be directly implemented by a hardware decoding processor, or implemented by a combination of hardware and software modules in the decoding processor. The software module may be located in ram, flash memory, rom, prom, or eprom, registers, etc. storage media as is well known in the art. The storage medium is located in a memory, and a processor reads information in the memory and completes the steps of the method in combination with hardware of the processor.
It will also be appreciated that the memory in the embodiments of the subject application can be either volatile memory or nonvolatile memory, or can include both volatile and nonvolatile memory. The non-volatile memory may be a read-only memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an Electrically Erasable PROM (EEPROM), or a flash memory. Volatile memory can be Random Access Memory (RAM), which acts as external cache memory. By way of example, but not limitation, many forms of Random Access Memory (RAM) are available, such as Static RAM (SRAM), Dynamic Random Access Memory (DRAM), Synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), Enhanced SDRAM (ESDRAM), synchlink DRAM (SLDRAM), and direct bus RAM (DR RAM).
According to the method provided by the embodiment of the present application, the present application further provides a computer program product, which includes: computer program code which, when run on a computer, causes the computer to perform the methods described above.
There is also provided, in accordance with a method provided by an embodiment of the present application, a computer-readable medium having program code stored thereon, which, when run on a computer, causes the computer to perform the above-described parties.
According to the method provided by the embodiment of the present application, the present application further provides a system, which includes the foregoing one or more terminal devices and one or more network devices.
The above embodiments may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented in software, the above-described embodiments may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When loaded or executed on a computer, cause the flow or functions according to embodiments of the invention to occur, in whole or in part. The computer may be a general purpose computer, a special purpose computer, a network of computers, or other programmable device. The computer instructions may be stored on a computer readable storage medium or transmitted from one computer readable storage medium to another computer readable storage medium, for example, the computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center by wire (e.g., infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server, data center, etc. that contains one or more collections of available media. The usable medium may be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., Digital Versatile Disk (DVD)), or a semiconductor medium. The semiconductor medium may be a solid state disk.
It should be understood that, in the various embodiments of the present application, the sequence numbers of the above-mentioned processes do not mean the execution sequence, and the execution sequence of each process should be determined by its function and inherent logic, and should not constitute any limitation to the implementation process of the embodiments of the present application.
It should also be understood that, in the present application, "when …", "if" and "if" all refer to the terminal device or the network device making corresponding processing under certain objective conditions, and are not time-limited, and do not require certain judgment actions when the terminal device or the network device is implemented, and do not mean that there are other limitations.
The term "and/or" herein is merely an association describing an associated object, meaning that three relationships may exist, e.g., a and/or B, may mean: a exists alone, A and B exist simultaneously, and B exists alone.
Herein, the term "at least one of … …" or "at least one of … …" or "at least one of … …" means all or any combination of the listed items, e.g., "at least one of A, B and C", may mean: there are six cases of a alone, B alone, C alone, a and B together, B and C together, and A, B and C together.
It should be understood that in the embodiments of the present application, "B corresponding to a" means that B is associated with a, from which B can be determined. It should also be understood that determining B from a does not mean determining B from a alone, but may be determined from a and/or other information.
Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.
It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.
In the several embodiments provided in the present application, it should be understood that the disclosed system, apparatus and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.
The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit.
In the embodiments of the present application, unless otherwise specified or conflicting with respect to logic, the terms and/or descriptions in different embodiments have consistency and may be mutually cited, and technical features in different embodiments may be combined to form a new embodiment according to their inherent logic relationship.
The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application or portions thereof that substantially contribute to the prior art may be embodied in the form of a software product stored in a storage medium and including instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: various media capable of storing program codes, such as a usb disk, a removable hard disk, a read-only memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk.
The above description is only for the specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present application, and shall be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims (21)

1. A method for transmitting uplink information, comprising:
determining a first time-frequency resource and uplink control information carried on an uplink control channel to be sent on the first time-frequency resource;
determining a second time-frequency resource and N uplink data channels to be sent on the second time-frequency resource, wherein the N uplink data channels bear the same transmission block, and N is an integer greater than 1;
under the condition that the first time-frequency resource and the second time-frequency resource are overlapped on a time domain, if an uplink data channel meeting a first condition exists in the N uplink data channels, the uplink control information is carried on a first target channel to be sent, the first target channel is one of the N uplink data channels meeting the first condition, and the first condition is a time line condition that the uplink control information is multiplexed on the uplink data channel to be transmitted.
2. The method of claim 1, wherein there are also uplink data channels of the N uplink data channels that do not satisfy the first condition.
3. The method according to claim 1 or 2, wherein the first target channel is an earliest uplink data channel among all uplink data channels satisfying the first condition among the N uplink data channels.
4. The method of claim 1 or 2, wherein the first target channel and the uplink control channel overlap in a time domain.
5. The method of claim 4, wherein the first target channel is an earliest uplink data channel among all uplink data channels of the N uplink data channels that overlap in time domain with the uplink control channel, which satisfies the first condition.
6. The method of any of claims 1 to 5, further comprising:
and carrying the uplink control information on at least one second target channel in the N uplink data channels to be sent, wherein the second target channel is later than the first target channel.
7. The method of claim 6, the second target channel overlaps with the uplink control channel in a time domain.
8. The method of any of claims 1 to 7, wherein the loading the uplink control information on a first target channel for transmission comprises:
and carrying the uplink control information on the first target channel to be sent under the condition that the priority of the uplink control channel is lower than or equal to the priority of the uplink data channel.
9. The method of claim 8, wherein the priority of the uplink data channel is indicated by scheduling downlink control information of the uplink data channel, or wherein the priority of the uplink data channel is indicated by a Radio Network Temporary Identity (RNTI) scrambling the downlink control information of the uplink data channel; and/or the presence of a gas in the gas,
the priority of the uplink control information is the priority of a downlink data channel corresponding to the uplink control information, and the priority of the downlink data channel is indicated by scheduling the downlink control information of the downlink data channel, or the priority of the downlink data channel is indicated by a Radio Network Temporary Identifier (RNTI) of the downlink control information of the downlink data channel which is scheduled by scrambling.
10. A method for transmitting uplink information, comprising:
determining a first time-frequency resource, wherein the first time-frequency resource is used for sending an uplink control channel, and the uplink control channel is used for carrying uplink control information;
determining a second time-frequency resource, wherein the second time-frequency resource is used for sending N uplink data channels, the N uplink data channels bear the same transmission blocks, and N is an integer greater than 1;
and under the condition that the first time-frequency resource and the second time-frequency resource are overlapped on a time domain, if an uplink data channel meeting a first condition exists in the N uplink data channels, receiving the uplink control information on a first target channel, wherein the first target channel is one of the N uplink data channels meeting the first condition, and the first condition is a time line condition that the uplink control information is multiplexed on the uplink data channel for transmission.
11. The method of claim 10, wherein there are also uplink data channels of the N uplink data channels that do not satisfy the first condition.
12. The method according to claim 10 or 11, wherein the first target channel is an earliest uplink data channel among all uplink data channels satisfying the first condition among the N uplink data channels.
13. The method of claim 10 or 11, wherein the first target channel and the uplink control channel overlap in a time domain.
14. The method of claim 13, wherein the first target channel is an earliest uplink data channel among all uplink data channels of the N uplink data channels that overlap in time domain with the uplink control channel, which satisfies the first condition.
15. The method of any of claims 10 to 14, further comprising:
receiving the uplink control information on at least one second target channel of the N uplink data channels, wherein the second target channel is later than the first target channel.
16. The method of claim 15, the second target channel overlaps with the uplink control channel in a time domain.
17. The method of any of claims 10 to 16, wherein the receiving the uplink control information on the first target channel comprises:
receiving the uplink control information on the first target channel if the priority of the uplink control channel is lower than or equal to the priority of the uplink data channel.
18. The method of claim 17, wherein the priority of the uplink data channel is indicated by scheduling downlink control information of the uplink data channel, or wherein the priority of the uplink data channel is indicated by a Radio Network Temporary Identity (RNTI) scrambling the downlink control information of the uplink data channel; and/or the presence of a gas in the gas,
the priority of the uplink control information is the priority of a downlink data channel corresponding to the uplink control information, and the priority of the downlink data channel is indicated by scheduling the downlink control information of the downlink data channel, or the priority of the downlink data channel is indicated by a Radio Network Temporary Identifier (RNTI) of the downlink control information of the downlink data channel which is scheduled by scrambling.
19. A communications apparatus, comprising means for performing the method of any of claims 1-9 or 10-18.
20. A communications device comprising a processor and interface circuitry for receiving and transmitting signals from or sending signals to other communications devices than the communications device, the processor being arranged to implement the method of any one of claims 1 to 9 or 10 to 18 by means of logic circuitry or executing code instructions.
21. A computer-readable storage medium, in which a program or instructions are stored which, when executed, implement the method of any one of claims 1 to 9 or 10 to 18.
CN201910252637.2A 2019-03-29 2019-03-29 Method and communication device for transmitting uplink information Withdrawn CN111756506A (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN201910252637.2A CN111756506A (en) 2019-03-29 2019-03-29 Method and communication device for transmitting uplink information
PCT/CN2020/081620 WO2020200078A1 (en) 2019-03-29 2020-03-27 Method for transmitting uplink information and communication device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201910252637.2A CN111756506A (en) 2019-03-29 2019-03-29 Method and communication device for transmitting uplink information

Publications (1)

Publication Number Publication Date
CN111756506A true CN111756506A (en) 2020-10-09

Family

ID=72664687

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201910252637.2A Withdrawn CN111756506A (en) 2019-03-29 2019-03-29 Method and communication device for transmitting uplink information

Country Status (2)

Country Link
CN (1) CN111756506A (en)
WO (1) WO2020200078A1 (en)

Cited By (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022110028A1 (en) * 2020-11-27 2022-06-02 北京小米移动软件有限公司 Uplink control information transmission method and apparatus, and storage medium
CN114745083A (en) * 2021-01-08 2022-07-12 维沃移动通信有限公司 Information transmission method, device, terminal and network equipment
WO2022147754A1 (en) * 2021-01-08 2022-07-14 Zte Corporation Systmes and methods for selecting overlapped channels
WO2022151227A1 (en) * 2021-01-14 2022-07-21 北京小米移动软件有限公司 Method and apparatus for indicating number of pucch transmissions, and repeat transmission method and apparatus
WO2022156567A1 (en) * 2021-01-19 2022-07-28 大唐移动通信设备有限公司 Information transmission method, apparatus, terminal device, network device, and storage medium
CN114826508A (en) * 2021-01-18 2022-07-29 大唐移动通信设备有限公司 Channel transmission method, device and readable storage medium
WO2022206635A1 (en) * 2021-04-01 2022-10-06 华为技术有限公司 Information sending method and apparatus, and information receiving method and apparatus
WO2022213362A1 (en) * 2021-04-09 2022-10-13 Oppo广东移动通信有限公司 Channel determination methods, channel transmission methods, electronic devices, and storage mediums
WO2022218157A1 (en) * 2021-04-13 2022-10-20 大唐移动通信设备有限公司 Channel processing method and apparatus, and storage medium

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN117676861A (en) * 2022-08-10 2024-03-08 大唐移动通信设备有限公司 Communication method and device

Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103220070A (en) * 2012-01-20 2013-07-24 中兴通讯股份有限公司 Sending method for uplink signal and user equipment
US20130195084A1 (en) * 2012-01-27 2013-08-01 Qualcomm Incorporated Physical layer issues related to multi-ta group support
CN104641577A (en) * 2012-09-19 2015-05-20 Lg电子株式会社 Method and device for transmitting uplink control information
WO2018043494A1 (en) * 2016-09-02 2018-03-08 シャープ株式会社 Terminal device, base station device, communication method, and integrated circuit
CN107889223A (en) * 2016-09-29 2018-04-06 电信科学技术研究院 A kind of data transmission method and device
US20180359057A1 (en) * 2015-12-11 2018-12-13 Lg Electronics Inc. Method for transmitting uplink signal and apparatus therefor
CN109155726A (en) * 2018-03-09 2019-01-04 北京小米移动软件有限公司 Information transferring method, device, system and storage medium

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10334598B2 (en) * 2017-04-25 2019-06-25 Motorola Mobility Llc Determining a priority order based on uplink transmission parameters
CN110035550B (en) * 2018-01-12 2021-08-13 华为技术有限公司 Uplink control information transmission method and communication device
CN110139363B (en) * 2018-02-09 2021-11-09 维沃移动通信有限公司 Method for sending UCI and user terminal

Patent Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103220070A (en) * 2012-01-20 2013-07-24 中兴通讯股份有限公司 Sending method for uplink signal and user equipment
US20130195084A1 (en) * 2012-01-27 2013-08-01 Qualcomm Incorporated Physical layer issues related to multi-ta group support
CN104641577A (en) * 2012-09-19 2015-05-20 Lg电子株式会社 Method and device for transmitting uplink control information
US20180359057A1 (en) * 2015-12-11 2018-12-13 Lg Electronics Inc. Method for transmitting uplink signal and apparatus therefor
WO2018043494A1 (en) * 2016-09-02 2018-03-08 シャープ株式会社 Terminal device, base station device, communication method, and integrated circuit
CN107889223A (en) * 2016-09-29 2018-04-06 电信科学技术研究院 A kind of data transmission method and device
CN109155726A (en) * 2018-03-09 2019-01-04 北京小米移动软件有限公司 Information transferring method, device, system and storage medium

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
QUALCOMM INCORPORATED: ""Remaining issues for overlapping UL transmissions"", 《3GPP TSG RAN WG1 MEETING #93 R1- 1807359》 *
VIVO: ""Remaining issues on PUCCH"", 《3GPP TSG RAN WG1 MEETING #95 R1-1812289》 *

Cited By (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022110028A1 (en) * 2020-11-27 2022-06-02 北京小米移动软件有限公司 Uplink control information transmission method and apparatus, and storage medium
CN114745083A (en) * 2021-01-08 2022-07-12 维沃移动通信有限公司 Information transmission method, device, terminal and network equipment
WO2022147754A1 (en) * 2021-01-08 2022-07-14 Zte Corporation Systmes and methods for selecting overlapped channels
WO2022148368A1 (en) * 2021-01-08 2022-07-14 维沃移动通信有限公司 Information transmission method and apparatus, and terminal and network device
CN114745083B (en) * 2021-01-08 2024-01-30 维沃移动通信有限公司 Information transmission method, device, terminal and network equipment
WO2022151227A1 (en) * 2021-01-14 2022-07-21 北京小米移动软件有限公司 Method and apparatus for indicating number of pucch transmissions, and repeat transmission method and apparatus
CN114826508A (en) * 2021-01-18 2022-07-29 大唐移动通信设备有限公司 Channel transmission method, device and readable storage medium
CN114826508B (en) * 2021-01-18 2023-07-21 大唐移动通信设备有限公司 Channel transmission method, device and readable storage medium
WO2022156567A1 (en) * 2021-01-19 2022-07-28 大唐移动通信设备有限公司 Information transmission method, apparatus, terminal device, network device, and storage medium
WO2022206635A1 (en) * 2021-04-01 2022-10-06 华为技术有限公司 Information sending method and apparatus, and information receiving method and apparatus
CN115189826A (en) * 2021-04-01 2022-10-14 华为技术有限公司 Information sending method, receiving method and device
WO2022213362A1 (en) * 2021-04-09 2022-10-13 Oppo广东移动通信有限公司 Channel determination methods, channel transmission methods, electronic devices, and storage mediums
WO2022218157A1 (en) * 2021-04-13 2022-10-20 大唐移动通信设备有限公司 Channel processing method and apparatus, and storage medium

Also Published As

Publication number Publication date
WO2020200078A1 (en) 2020-10-08

Similar Documents

Publication Publication Date Title
CN111756506A (en) Method and communication device for transmitting uplink information
US20210345373A1 (en) Uplink information transmission method and communications apparatus
US11678351B2 (en) Scheduling radio resources using first and second configuration
CN111770572B (en) Method for determining feedback information and communication device
CN111836366B (en) Uplink transmission method and communication device
CN111865511B (en) Method and communication device for transmitting hybrid automatic repeat request (HARQ) feedback information
CN112399604B (en) Apparatus and method for processing reception
CN112398592B (en) Feedback information transmission method and communication device
WO2020220253A1 (en) Information transmission method and communication devices
WO2021159979A1 (en) Feedback method and apparatus for hybrid automatic repeat request acknowledgement codebook
CN112311501B (en) Communication method and communication device
CN111769916B (en) Communication method, communication device and system
CN114451017A (en) Method and device for activating and releasing non-dynamic scheduling transmission
CN109802765B (en) Response message sending method and device
CN111867118A (en) Resource scheduling method and communication device
CN114390698A (en) Data transmission method, device, medium and program product
CN112312559A (en) Communication method and communication device
WO2022151383A1 (en) Uplink transmission method and apparatus
WO2022206579A1 (en) Uplink control information transmission method and apparatus
WO2020031278A1 (en) Transmission device, receiving device, wireless communication system and communication method
CN112584358A (en) Device-to-device communication method and communication device
TW202329730A (en) Communication device and communication method
CN115462149A (en) Wireless communication method and wireless communication device
JP2022511202A (en) HARQ-ACK processing using multiple PUCCHs in multi-TRP transmission in NR
CN116097589A (en) Uplink information transmission method and device

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
WW01 Invention patent application withdrawn after publication

Application publication date: 20201009

WW01 Invention patent application withdrawn after publication