WO2021062711A1

WO2021062711A1 - Method and apparatus for transmitting uplink control information

Info

Publication number: WO2021062711A1
Application number: PCT/CN2019/109611
Authority: WO
Inventors: 柴晓萌; 吴艺群
Original assignee: 华为技术有限公司
Priority date: 2019-09-30
Filing date: 2019-09-30
Publication date: 2021-04-08
Also published as: CN114503722A

Abstract

The present application relates to the field of communications, and provides a method and apparatus for transmitting uplink control information (UCI), for use in solving the problem of multiplexing UCI on a non-UE-specific PUSCH when a PUSCH and a PUCCH overlap in a time domain during a two-step random access process. The method comprises: determining a time domain resource of a physical uplink shared channel (PUSCH) to be sent, the PUSCH being used for carrying uplink data; if the time domain resource of the PUSCH overlaps a time domain resource of a physical uplink control channel (PUCCH) used for carrying UCI, sending a PUSCH carrying UCI and uplink data, wherein the uplink data and the UCI are multiplexed in a same medium access control protocol data unit (MAC PDU), and the MAC PDU is carried on the PUSCH.

Description

Method and device for transmitting uplink control information

Technical field

This application relates to the field of communications, and in particular to a method and device for transmitting uplink control information.

Background technique

In long term evolution (LTE), fifth generation (5G) new radio (NR) and other wireless communication systems, terminal devices need to use random access from radio resource control (radio resource control, RRC) Idle state or inactive state enters RRC connected state, or, in the case of uplink out-of-synchronization, no scheduling request (SR) resources, or multiple failures of SR, random access will be used to perform reconfiguration. Synchronize and request uplink resources, and then communicate with network devices.

In the two-step random access process, in the first step, the terminal device sends a random access preamble and data to the network device in a message, and in the second step, the network device sends a random access response to the terminal device. In the first step, the random access preamble part is transmitted on a physical random access channel (PRACH), and the data part is transmitted on a physical uplink shared channel (PUSCH).

The existing NR system supports the reuse of uplink control information (UCI) on the common PUSCH. In particular, in the two-step random access process, if the PUSCH and the physical uplink control channel (PUCCH) overlap in the time domain resources, only the user equipment (UE) specific PUSCH is supported. With UCI, the UE-specific PUSCH refers to the PUSCH dedicated to the UE.

Summary of the invention

The embodiments of the present application provide a method and apparatus for transmitting uplink control information, which are used to solve the problem of multiplexing UCI on the non-UE specific PUSCH when the PUSCH and the PUCCH overlap in the time domain in the two-step random access process.

In order to achieve the foregoing objectives, the embodiments of the present application adopt the following technical solutions:

In the first aspect, a method for transmitting uplink control information is provided, including: determining the time domain resource of the physical uplink shared channel PUSCH to be transmitted, where the PUSCH is used to carry uplink data; if the time domain resource of the PUSCH is used to carry uplink control information The time domain resources of the physical uplink control channel PUCCH of UCI overlap, and the PUSCH carrying UCI and uplink data is sent. The uplink data and UCI are multiplexed in the same media access control protocol data unit MAC PDU, and the MAC PDU is carried on the PUSCH .

The method for transmitting uplink control information provided in the embodiments of the present application uses the terminal device to carry multiplexed UCI and uplink data in the MAC PDU, so that the network device can determine the position of the UCI in the PUSCH, so that the UCI can be correctly parsed. It solves the problem of multiplexing UCI for non-UE specific PUSCH when PUSCH and PUCCH have time domain overlap in the two-step random access process.

In a possible implementation manner, the time relationship between the first symbol in the time domain resources where the PUCCH and the PUSCH overlap and the related PDSCH and PDCCH should meet the processing capability of the terminal device.

In a possible implementation manner, UCI is carried in the MAC sub-PDU of the MAC PDU, where the MAC sub-PDU includes a MAC sub-header and a MAC control cell CE, the MAC-CE is used to carry UCI, and the MAC sub-header includes a logical channel identifier The LCID field and the length field. The LCID field is used to indicate that the type of MAC CE is UCI, and the length field is used to indicate the size of MAC CE.

In a possible implementation manner, UCI includes channel state information CSI feedback and/or hybrid automatic repeat request HARQ feedback information.

In a possible implementation manner, the MAC CE includes a field indicating the size of the CSI feedback and/or a field indicating the size of the HARQ feedback information.

In a possible implementation manner, the CSI feedback includes a first part and a second part, and the MAC CE includes a field indicating the size of the first part of the CSI feedback and/or a field indicating the size of the second part of the CSI feedback. It is convenient to know the positions of the two parts of CSI feedback in MAC CE.

In a possible implementation manner, the CSI feedback and HARQ feedback information in UCI are located in different MAC sub-PDUs.

In a possible implementation manner, when the first symbol in the time domain resource overlapping the PUCCH and the PUSCH satisfies a preset condition, the uplink data and the UCI can be multiplexed in the same MAC PDU, and the MAC PDU can be carried on the PUSCH. The preset condition is related to the processing capability of the UE. Specifically, the preset condition can be one or more of the following conditions: the first symbol is not earlier than the last symbol of any physical downlink shared channel PDSCH associated with UCI After T2 time; the first symbol is no earlier than T3 time after the last symbol of the PDCCH of the semi-persistent scheduling (SPS) PDSCH is released; the first symbol is no earlier than the PDCCH of the scheduled PUSCH T4 time after the last symbol; the first symbol is no earlier than T5 time after the last symbol of any PDCCH scheduling PDSCH related to HARQ feedback information; the first symbol is no earlier than any semi-persistent scheduling SPS release Time T6 after the last symbol of the PDCCH of the PDSCH. T2, T3, T4, T5, and T6 are thresholds predefined by the protocol or configured by the base station.

In a second aspect, a method for transmitting uplink control information is provided, including: receiving a physical uplink shared channel PUSCH, where the time domain resources of the PUSCH overlap with the time domain resources of the PUCCH used to carry the uplink control information; and the PUSCH is analyzed to obtain Uplink control information UCI and uplink data. Among them, the uplink data and UCI are multiplexed in the same media access control protocol data unit MAC PDU, and the MAC PDU is carried on the PUSCH.

In a third aspect, a method for transmitting uplink control information is provided. The method includes sending indication information associated with the time-frequency resource of the physical uplink shared channel PUSCH, and the indication information is used to determine the uplink transmitted on the time-frequency resource of the PUSCH. The size of the control information UCI or the number of resource elements RE occupied by UCI in the time-frequency resource of the PUSCH; UCI and uplink data are sent on the time-frequency resource of the PUSCH, where the UCI and the uplink data are carried on the PUSCH.

In the method for transmitting uplink control information provided by the embodiments of the present application, the terminal device indicates which terminal device sends the PUSCH, or indicates the size of UCI or the number of REs occupied, so that the network device can determine the position of UCI in the PUSCH, thereby Can parse UCI correctly. It solves the problem of multiplexing UCI for non-UE specific PUSCH when PUSCH and PUCCH have time domain overlap in the two-step random access process.

In a possible implementation manner, the method further includes: determining that the time domain resources of the PUSCH overlap with the time domain resources of the physical uplink control channel PUCCH, where the PUCCH is used to carry UCI and the PUSCH is used to carry uplink data.

In a possible implementation manner, the indication information includes at least one of the following information: indication information of the size of the UCI, or indication information of the number of REs occupied by the UCI, or identification of the device that sends the UCI. This information facilitates the determination of the specific location of UCI.

In a possible implementation manner, UCI is mapped to REs in predetermined positions in the time-frequency resources of PUSCH, and uplink data is mapped to REs in other positions in the time-frequency resources of PUSCH.

In a fourth aspect, a method for transmitting uplink control information is provided. The method further includes: receiving indication information associated with the time-frequency resource of the physical uplink shared channel PUSCH, where the indication information is used to determine the uplink transmitted on the time-frequency resource of the PUSCH The size of the control information UCI or the number of resource elements RE occupied by the UCI in the time-frequency resource of the PUSCH; UCI and uplink data are received on the time-frequency resource of the PUSCH, where the UCI and the uplink data are carried on the PUSCH.

In a fifth aspect, a communication device is provided, including a processing module and a transceiver module. The processing module is used to control the transceiver module, and execute the method according to the first aspect or any one of the methods, or execute the method according to the second aspect and the transceiver module. The method according to any one of the methods described in the third aspect and any one of the methods, or the method described in the fourth aspect and any one of them is performed.

In a sixth aspect, a communication device is provided. The communication device includes a processor, a memory, and a transceiver. The processor is coupled to the memory. When the processor executes a computer program or instruction in the memory, The method according to one aspect and any one of the methods, or the method according to the second aspect and any one thereof, or the method according to the third aspect and any one thereof, or the method as described in The fourth aspect and the method of any one of them.

In a seventh aspect, a chip is provided, including: a processor and an interface, configured to call and run a computer program stored in the memory from a memory, and execute the method according to the first aspect or any one of them, or Execute the method according to the second aspect and any one thereof, or execute the method according to the third aspect and any one thereof, or execute the method according to the fourth aspect and any one thereof.

In an eighth aspect, a computer-readable storage medium is provided. The computer-readable storage medium stores instructions. When the instructions run on a computer or a processor, the computer or the processor executes the first aspect and any of the instructions. The method described in one item, or the method described in the second aspect and any one thereof is performed, or the method described in the third aspect and any one thereof is performed, or the method described in the fourth aspect and any one thereof is performed Any of the methods.

In a ninth aspect, a computer program product containing instructions is provided. When the instructions run on a computer or a processor, the computer or the processor executes the method described in the first aspect or any one of the methods, or executes The method according to the second aspect and any one thereof, or the method according to the third aspect and any one thereof, or the method according to the fourth aspect and any one thereof.

For the technical effects of the fifth aspect to the ninth aspect, reference may be made to the content of the various possible implementation manners of the first aspect to the fourth aspect.

Description of the drawings

FIG. 1 is a schematic diagram of the architecture of a communication system provided by an embodiment of this application;

FIG. 2 is a schematic structural diagram of a terminal device provided by an embodiment of this application;

FIG. 3 is a schematic structural diagram of a network device provided by an embodiment of this application;

FIG. 4 is a schematic diagram of a four-step random access process provided by an embodiment of this application;

FIG. 5 is a schematic diagram of a two-step random access process provided by an embodiment of this application;

FIG. 6 is a schematic flowchart 1 of a method for transmitting uplink control information according to an embodiment of this application;

FIG. 7 is a schematic diagram of a MAC PDU provided by an embodiment of the application;

FIG. 8 is a schematic diagram of a MAC subheader provided by an embodiment of the application;

FIG. 9 is a schematic diagram 1 of CSI feedback carried by MAC CE and provided by an embodiment of this application;

FIG. 10 is a second schematic diagram of CSI feedback carried by MAC CE and provided by an embodiment of this application;

FIG. 11 is a schematic diagram of PUSCH multiplexing HARQ feedback information and CSI feedback according to an embodiment of this application;

FIG. 12 is a schematic diagram 1 of carrying HARQ feedback information and CSI feedback through MAC CE according to an embodiment of this application;

FIG. 13 is a second schematic diagram of carrying HARQ feedback information and CSI feedback through MAC CE according to an embodiment of this application;

FIG. 14 is a first schematic flowchart of a method for transmitting uplink control information according to an embodiment of this application;

15 is a schematic structural diagram 1 of a communication device provided by an embodiment of this application;

FIG. 16 is a second structural diagram of a communication device provided by an embodiment of this application.

Detailed ways

The embodiments of this application can be applied to both time division duplexing (TDD) scenarios and frequency division duplexing (FDD) scenarios.

The embodiments of this application rely on the scenario of the fifth generation (5G) communication network in the wireless communication network. It should be noted that the solutions in the embodiments of this application can also be applied to other wireless communication networks, such as the sixth generation (5G) communication network. For generations of mobile communication systems, the corresponding names can also be replaced with the names of corresponding functions in other wireless communication networks. The 5G mobile communication system involved in this application includes a non-standalone (NSA) 5G mobile communication system and/or a standalone (SA) 5G mobile communication system.

The embodiments of this application may be applicable to long term evolution (LTE) systems, such as narrowband internet of things (NB-IoT) systems, or may also be applicable to advanced long term evolution (LTE Advanced, LTE-A) system. It can also be applied to other wireless communication systems, such as global system for mobile communication (GSM), universal mobile telecommunications system (UMTS), code division multiple access (CDMA) Systems, and new network equipment systems, etc.

As shown in Fig. 1, the communication system 100 provided by the embodiment of the present application includes a network device 101 and terminal devices 102-107.

The terminal device involved in the embodiments of the present application may be a device that provides voice and/or data connectivity to a user, a handheld device with a wireless connection function, or other processing devices connected to a wireless modem. A wireless terminal can communicate with one or more core networks via a radio access network (RAN). The wireless terminal can be a mobile terminal, such as a mobile phone (or “cellular” phone) and a computer with a mobile terminal. For example, they can be portable, pocket-sized, handheld, computer-built or vehicle-mounted mobile devices that exchange voice and/or data with the wireless access network. For example, user equipment (UE), personal communication service (PCS) phones, cordless phones, session initiation protocol (SIP) phones, wireless local loop (WLL) stations, personal digital assistants (personal digital assistant, PDA) and other equipment. Wireless terminal can also be called system, subscriber unit, subscriber station, mobile station, mobile station, remote station, access point, Remote terminal (remote terminal), access terminal (access terminal), user terminal (user terminal), user agent (user agent), user equipment (user device), or user equipment (user equipment). Exemplarily, the terminal device may be a high-speed rail communication device 102, a smart air conditioner 103, a smart gas dispenser 104, a mobile phone 105, a smart teacup 106, a printer 107, etc., which are not limited in this application.

The network device involved in the embodiment of this application may be a base station, which can be used to convert received air frames and Internet protocol (IP) packets to each other, and act as a router between the wireless terminal and the rest of the access network , Where the rest of the access network can include IP network equipment. The base station can also coordinate the attribute management of the air interface. For example, the base station can be a base transceiver station (BTS) in GSM or CDMA, a base station (NodeB) in wideband code division multiple access (WCDMA), or an evolution in LTE A type base station (evolutional Node B, eNB or e-NodeB) may also be a gNB in 5G, which is not limited in the embodiment of the present application. The above-mentioned base station is only an example, and the network device may also be a relay station, an access point, a vehicle-mounted device, a wearable device, and other types of devices.

As shown in Figure 2, the terminal device is a mobile phone as an example to illustrate the structure of the terminal device.

The terminal device 105 may include: a radio frequency (RF) circuit 110, a memory 120, an input unit 130, a display unit 140, a sensor 150, an audio circuit 160, a wireless fidelity (Wi-Fi) module 170, and a processor 180, Bluetooth module 181, and power supply 190 and other components.

The RF circuit 110 can be used for receiving and sending signals in the process of sending and receiving information or talking. It can receive the downlink data of the base station and then send it to the processor 180 for processing; it can send the uplink data to the base station. Generally, the RF circuit includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, and other devices.

The memory 120 can be used to store software programs and data. The processor 180 executes various functions and data processing of the terminal device 105 by running a software program or data stored in the memory 120. The memory 120 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one magnetic disk storage device, a flash memory device, or other volatile solid-state storage devices. The memory 120 stores an operating system that enables the terminal device 105 to run, such as the one developed by Apple

Operating system, developed by Google

Open source operating system, developed by Microsoft

Operating system, etc. In the present application, the memory 120 may store an operating system and various application programs, and may also store codes for executing the methods in the embodiments of the present application.

The input unit 130 (for example, a touch screen) may be used to receive input digital or character information, and generate signal input related to user settings and function control of the terminal device 105. Specifically, the input unit 130 may include a touch screen 131 provided on the front of the terminal device 105, and may collect user touch operations on or near it.

The display unit 140 (ie, the display screen) may be used to display information input by the user or information provided to the user, as well as a graphical user interface (GUI) of various menus of the terminal device 105. The display unit 140 may include a display screen 141 provided on the front of the terminal device 105. Among them, the display screen 141 may be configured in the form of a liquid crystal display, a light emitting diode, or the like. The display unit 140 may be used to display various graphical user interfaces described in this application. The touch screen 131 may be overlaid on the display screen 141, or the touch screen 131 and the display screen 141 may be integrated to realize the input and output functions of the terminal device 105. After integration, it may be referred to as a touch display screen.

The terminal device 105 may also include at least one sensor 150, such as a light sensor and a motion sensor. The terminal device 105 may also be configured with other sensors such as a gyroscope, a barometer, a hygrometer, a thermometer, and an infrared sensor.

The audio circuit 160, the speaker 161, and the microphone 162 can provide an audio interface between the user and the terminal device 105. The audio circuit 160 can transmit the electrical signal converted from the received audio data to the speaker 161, which is converted into a sound signal for output by the speaker 161; on the other hand, the microphone 162 converts the collected sound signal into an electrical signal, and the audio circuit 160 After being received, it is converted into audio data, and then the audio data is output to the RF circuit 110 to be sent to, for example, another terminal, or the audio data is output to the memory 120 for further processing.

Wi-Fi is a short-distance wireless transmission technology. The terminal device 105 can help users receive and send emails, browse webpages, and access streaming media through the Wi-Fi module 170. It provides users with wireless broadband Internet access.

The processor 180 is the control center of the terminal device 105. It uses various interfaces and lines to connect the various parts of the entire terminal, and executes the terminal device by running or executing the software program stored in the memory 120 and calling the data stored in the memory 120. 105's various functions and processing data. In this application, the processor 180 may refer to one or more processors, and the processor 180 may include one or more processing units; the processor 180 may also integrate an application processor and a baseband processor, where the application processor mainly processes operations For systems, user interfaces, and applications, the baseband processor mainly handles wireless communications. It can be understood that the aforementioned baseband processor may not be integrated into the processor 180. The processor 180 in this application can run an operating system, application programs, user interface display and touch response, as well as the communication method described in the embodiments of this application.

The Bluetooth module 181 is used to exchange information with other Bluetooth devices having a Bluetooth module through the Bluetooth protocol. For example, the terminal device 105 can establish a Bluetooth connection with a wearable electronic device (such as a smart watch) that also has a Bluetooth module through the Bluetooth module 181, so as to perform data interaction.

The terminal device 105 also includes a power source 190 (such as a battery) for supplying power to various components. The power supply can be logically connected to the processor 180 through a power management system, so that functions such as charging, discharging, and power consumption can be managed through the power management system.

As shown in FIG. 3, an embodiment of the present application provides a schematic structural diagram of a network device. The network device 300 may include one or more radio frequency units, such as a remote radio unit (RRU) 310 and one or more baseband units (BBU) (also known as digital units (digital units, RRU) 310). DU)) 320. The RRU 310 may be referred to as a transceiver unit. Optionally, the transceiver unit 310 may also be called a transceiver, a transceiver circuit, a transceiver, a transmitter, and a receiver, etc., and it may include at least one antenna 311 and an RF circuit 312. Optionally, the transceiving unit 310 may include a receiving unit and a transmitting unit, the receiving unit may correspond to a receiver (also called a receiver, a receiving circuit), and the transmitting unit may correspond to a transmitter (also called a transmitter, a transmitting circuit). The part of the RRU 310 is mainly used for the transmission and reception of radio frequency signals and the conversion between radio frequency signals and baseband signals, for example, for sending instruction information to terminal equipment. The 320 part of the BBU is mainly used for baseband processing, control of network equipment, and so on. The RRU 310 and the BBU 320 may be physically set together, or may be physically separated, that is, a distributed base station.

The BBU 320 is the control center of the network equipment, and may also be called a processing unit, which is mainly used to complete baseband processing functions, such as channel coding, multiplexing, modulation, spread spectrum, and so on. For example, the BBU 320 may be used to control a network device to execute the method involved in this application.

In an example, the BBU 320 may be composed of one or more single boards, and multiple single boards may jointly support a radio access network (such as an LTE network) of a single access standard, or can support different access standards. Wireless access network (such as LTE network, 5G network or other network). The BBU 320 further includes a memory 321 and a processor 322. The memory 321 is used to store necessary instructions and data. The processor 322 is used to control the network device to perform necessary actions, for example, to control the network device to execute the method involved in this application. The processor 322 in this application may refer to one or more processors. The memory 321 and the processor 322 may serve one or more single boards. In other words, the memory and the processor can be set separately on each board. It can also be that multiple boards share the same memory and processor. In addition, necessary circuits can be provided on each board.

In addition, the network equipment is not limited to the above forms, and may also be in other forms: for example, including BBU and adaptive radio unit (ARU), or BBU and active antenna unit (AAU); or Customer premises equipment (CPE) may also be in other forms, which is not limited in this application.

First, the four-step random access process performed by terminal equipment in wireless communication systems such as LTE and 5G NR is described. As shown in Figure 4, it includes:

S401: The terminal device sends a random access preamble (random access preamble) to the network device.

It can also be referred to as the terminal device sending the first message (Msg1) to the network device.

The function of the random access preamble is to notify the terminal device that there is a random access request, and enable the network device to estimate the transmission delay between itself and the terminal device, so that the terminal device can calibrate the uplink timing and pass the calibration information The timing advance command (timing advance command) is notified to the terminal device.

S402: The network device sends a random access response to the terminal device after detecting the random access preamble.

It is also referred to as the network device sending the second message (Msg2) to the terminal device.

The random access response includes the received sequence number of the random access preamble, timing advance instruction, uplink resource allocation information, and cell wireless network temporary identification.

S403: After receiving the random access response, the terminal device sends uplink data to the network device.

It is also called the terminal device sending the third message (Msg3) to the network device.

The unique identifier of the terminal device can be carried in the uplink data.

If the random access preamble indicated by the sequence number of the random access preamble in the random access response is the same as the random access preamble sent by the terminal device to the network device in S401, the terminal device considers that the random access response is for the Random access response from the terminal device. The terminal device may send uplink data in the allocated uplink resource according to the instruction of the random access response, for example, send the PUSCH in the third message.

S404: After receiving the uplink data, the network device sends a conflict resolution message to the terminal device that has successfully accessed.

Also known as the network device sending the fourth message (Msg4) to the terminal device.

The conflict resolution message carries the unique identifier of the terminal device in step S403 to specify the terminal device that has successfully accessed, and other terminal devices that have not successfully accessed will re-initiate random access.

For the above-mentioned four-step random access process, four information exchanges will produce a higher access delay. Therefore, a two-step random access process is introduced in the 5G NR wireless communication system. As shown in Figure 5, the two-step random access process includes:

S501: The terminal device sends a random access preamble and uplink data to the network device.

The random access preamble and uplink data are sent in the same message, where the random access preamble is transmitted on the PRACH, and the uplink data is transmitted on the PUSCH.

For the description of the random access preamble and uplink data, see the preceding text, and will not be repeated here.

S502: The network device sends a random access response to the terminal device.

The description of the random access response is described in the previous section, and will not be repeated here.

As mentioned above, although the aforementioned two-step random access process reduces the access delay, the PUSCH in the two-step random access process is a contention-based PUSCH, which is neither dedicated to terminal equipment. In the existing NR system, when UCI is multiplexed on PUSCH, UCI and data are coded independently, and different resource elements (RE) are used. Since the UCI size of each UE is not fixed, the size of each UE is not fixed. The number of REs occupied by UCI is not fixed, so UCI can only be multiplexed on the UE dedicated PUSCH, so that the network device can determine whether the PUSCH is multiplexed with UCI according to the resource configuration and scheduling information of the terminal device, and the multiplexed UCI The number of occupied REs so that UCI can be correctly parsed. For a non-UE-specific PUSCH, the network device cannot determine which terminal device sends the PUSCH, and cannot determine whether the UCI is multiplexed on the PUSCH and the number of REs occupied by the UCI.

The embodiment of the application provides a method for transmitting uplink control information. A terminal device carries multiplexed UCI and uplink data in a media access control protocol data unit (MAC PDU), or instructs to send PUSCH. The user ID of, or indicates the size of the UCI multiplexed on the PUSCH or the number of REs occupied, so that the network device can determine the position of the UCI in the PUSCH, so that the UCI can be correctly parsed.

[Corrected according to Rule 91 30.10.2019]
For ease of description, unless otherwise specified, the PUSCHs involved in the embodiments of this application refer to contention-based PUSCHs, including the PUSCHs that compete for resources in the random access process (especially, the two-step random access process), and may also include Other PUSCH based on competition.

As shown in FIG. 6, an embodiment of the present application provides a method for transmitting uplink control information, including:

S601: The terminal device determines the time domain resource of the PUSCH to be sent.

Among them, PUSCH is used to carry uplink data. That is, if the terminal device needs to send uplink data, the terminal device needs to determine the time domain resource of the PUSCH that carries the uplink data.

S602: If the time domain resources of the PUSCH and the time domain resources of the PUCCH overlap, the terminal device sends a PUSCH that carries UCI and uplink data.

Correspondingly, the network device receives the PUSCH.

PUCCH is used to carry UCI. UCI may include channel state information (CSI) feedback and/or hybrid auto repeat request (HARQ) feedback information (such as acknowledgement (ACK) information or non-acknowledgement) (non-acknowledge, NACK) information).

The embodiment of the present application does not limit whether the frequency domain resources of the PUSCH and the frequency domain resources of the PUCCH overlap.

PUSCH time domain resources overlap with PUCCH time domain resources, that is to say, UCI and uplink data need to be sent at the same time, UCI and uplink data are multiplexed in PUSCH, where uplink data and UCI can be multiplexed in the same MAC In PDU, MAC PDU can be carried on PUSCH. The time relationship between the first symbol in the time domain resources where the PUCCH and PUSCH overlap and the related PDSCH and PDCCH should meet the processing capabilities of the terminal device.

If UCI only contains HARQ feedback information, the terminal device only sends PUCCH, not PUSCH, and there is no need to multiplex UCI in PUSCH.

If UCI only includes CSI feedback, and at least one of PUCCH and PUSCH is used to respond to downlink control information (DCI), when the first symbol in the time domain resource overlapping PUCCH and PUSCH meets the preset condition, the uplink Data and UCI can be multiplexed in the same MAC PDU, and the MAC PDU can be carried on the PUSCH. The preset condition is related to the processing capability of the UE. Specifically, the preset condition may be one or more of the following conditions:

The first symbol is no earlier than T2 time after the last symbol of any physical downlink shared channel PDSCH associated with UCI; the first symbol is no earlier than any release of semi-persistent scheduling (SPS) PDSCH T3 time after the last symbol of the PDCCH; the first symbol is no earlier than T4 time after the last symbol of the PDCCH scheduling PUSCH; the first symbol is no earlier than any PDCCH scheduling PDSCH related to HARQ feedback information The T5 time after the last symbol; the first symbol is no earlier than the T6 time after the last symbol of the PDCCH that releases the semi-persistent scheduling SPS PDSCH. T2, T3, T4, T5, and T6 are thresholds predefined by the protocol or configured by the base station.

In a possible implementation manner, if the time domain resources of the PRACH and the time domain resources of the PUCCH overlap, the terminal device transmits a PUSCH carrying UCI and uplink data, and the PUSCH is the PUSCH associated with the PRACH.

The time domain resources of PRACH overlap with the time domain resources of PUCCH, that is, the random access preamble and uplink data need to be sent at the same time, and the UCI and uplink data are multiplexed in the PUSCH associated with the random access preamble. Data and UCI can be multiplexed in the same MAC PDU, and the MAC PDU can be carried on the PUSCH.

If neither the PUCCH nor the PUSCH responds to DCI, the above conditions do not need to be met. The uplink data and UCI can be multiplexed in the same MAC PDU, and the MAC PDU can be carried on the PUSCH.

As shown in Figure 7, it is a schematic diagram of a MAC PDU. The MAC PDU includes one or more MAC subPDUs (MAC subPDU). The MAC subPDU can be divided into MAC subPDUs including MAC service data units (SDU), and MAC subPDUs including MAC control elements (CE). MAC sub-PDU and MAC sub-PDU including padding (optional).

Specifically, the MAC sub-PDU including the MAC SDU includes a first MAC sub-header and a MAC SDU, and the first MAC sub-header includes a reserved (R) field, a format (format, F) field, and a logical channel identification (logical channel identification, LCID) field and length (length, L) field. Among them, the R field is a reserved field, usually 0; the F field is used to indicate the size of the L field, as shown in A in Figure 8, and a 0 in the F field means that the L field is 8 bits, as shown in B in Figure 8. The F field is 1 meaning that the L field is 16 bits; the LCID field is used to uniquely identify the logical channel to which the MAC SDU belongs; the L field is used to indicate the size of the MAC SDU.

The MAC sub-PDU including the MAC CE is divided into a first MAC sub-PDU and a second MAC sub-PDU.

The first MAC subPDU includes a second MAC subheader and a fixed-sized MAC CE. The second MAC subheader includes an LCID field and a length L field, where the LCID field is used to uniquely identify the logical channel to which the MAC CE belongs, and the L field is used to indicate the size of the MAC CE.

The second MAC subPDU includes a third MAC subheader and a variable-sized MAC CE. The third MAC subheader includes the R field, the F field, the LCID field and the L field. The F field is used to indicate the size of the L field, the LCID field is used to uniquely identify the logical channel to which the MAC CE belongs, and the L field is used to indicate the MAC CE the size of.

In the embodiment of this application, the uplink data and UCI can be carried in the MAC sub-PDU of the MAC PDU. Specifically, the uplink data can be carried in the MAC SDU, and the UCI can be carried in the variable-size MAC CE.

Specifically, the MAC subPDU carrying UCI includes a MAC subheader and MAC CE. The MAC CE is used to carry UCI. The MAC subheader includes an R field, an F field, a logical channel identifier (LCID) field, and a length (length, L) field, the R field is a reserved field, usually 0; the F field is used to indicate the size of the L field, see the previous description for details; the LCID field is used to indicate that the type of MAC CE is UCI; the length field L is used to indicate MAC CE the size of. For example, the LCID of the MAC CE carrying the CSI feedback may be predefined as 35, and when the LCID is 35, it is indicated that the type of the MAC CE is CSI feedback.

The CSI feedback can include only one part or two parts (that is, the first part and the second part). Regardless of whether the CSI feedback includes one part or two parts, one MAC CE can be passed. If the CSI feedback includes two parts, and the CSI feedback is carried by two MAC CEs, the first part and the second part of the CSI feedback can be carried by a single MAC CE respectively, and the two MAC CEs can be distinguished by different LCIDs.

As shown in Figure 9, when the CSI feedback is carried by a MAC CE, the information of the CSI feedback can be combined in order. Even if the CSI includes two parts, when the network device extracts the relevant information (such as the identification) of the terminal device, it can The two parts of CSI feedback information are distinguished.

As shown in FIG. 10, the MAC CE may include a field indicating the size of the first part of the CSI feedback (for example, in bytes) and/or a field indicating the size of the second part of the CSI feedback (for example, in bytes). The above-mentioned fields can be used to indicate which information in the MAC CE belongs to the first part of the CSI feedback and which information belongs to the second part of the CSI feedback. When the CSI feedback includes only the first part, the field indicating the size of the second part of the CSI feedback may take the value 0. The size and location of the field indicating the size of the first part of the CSI feedback and the field indicating the size of the second part of the CSI feedback are predefined. It should be noted that the size of all fields in the MAC CE in the drawings of this application is only an example.

If the UCI contains HARQ feedback information with information bits less than or equal to 2 bits, the HARQ feedback information is multiplexed on the PUSCH by covering the REs that transmit uplink data on the PUSCH. If the UCI contains CSI feedback and/or HARQ feedback information with information bits greater than 2 bits, the CSI feedback and/or HARQ feedback information with information bits greater than 2 bits are combined with the uplink data through the aforementioned MAC CE carrying method. Used on PUSCH. The following first describes the above-mentioned covering method.

As shown in FIG. 11, the existing 5G NR wireless communication system supports multiplexing of UCI on PUSCH, including multiplexing HARQ feedback information and CSI feedback on PUSCH. CSI feedback may include two parts as described above.

1) Determine the number of REs required for mapping HARQ feedback information and CSI feedback according to the number of bits and modulation order after HARQ feedback information and CSI feedback are encoded.

2) The HARQ feedback information is mapped from the first PUSCH symbol after the demodulation reference signal (DMRS) of the PUSCH, and the CSI feedback is mapped from the first non-DMRS PUSCH symbol.

3) If the number of REs that need to be mapped is greater than or equal to the number of REs available for the current symbol, then all the current symbols are used for mapping UCI; if the number of REs that need to be mapped is less than the number of REs available for the current symbol, the number of REs of the current symbol

One RE is used to map UCI, where n=1, 2,..., N ₂ , N ₁ is the number of REs available for the current symbol, and N ₂ is the number of REs that need to be mapped remaining.

4) The HARQ feedback information with information bits less than or equal to 2 is multiplexed on the PUSCH in a puncturing manner, that is, the HARQ feedback information with information bits less than or equal to 2 will cover the original modulation symbols on the RE. For CSI feedback and/or HARQ feedback information with information bits greater than 2 bits, multiplexed on PUSCH in a rate matching manner, that is, the data part is only mapped to REs mapped by HARQ feedback information except for CSI feedback and/or information bits greater than 2 bits. In addition, the code rate of the data part is adjusted according to the remaining RE quantity.

As shown in Figure 12, CSI feedback and HARQ feedback information with information bits greater than 2 bits can be carried by a MAC CE. The CSI feedback and HARQ feedback information with information bits greater than 2 bits are combined in order. When the network device decodes After the relevant information (such as the identification) of the terminal device, the CSI feedback and the HARQ feedback information with information bits greater than 2 bits can be distinguished.

As shown in FIG. 13, the MAC CE may further include a field indicating the size of the CSI feedback (for example, in bytes) and/or a field indicating the size of the HARQ feedback information (for example, in bytes). Further, the MAC CE may also include at least one of the following indication information: a field indicating the size of the first part of the CSI feedback, a field indicating the size of the second part of the CSI feedback, and a field indicating the size of the HARQ feedback information. The above-mentioned fields can be used to indicate which information in the MAC CE belongs to the HARQ feedback information, which information belongs to the first part of the CSI feedback, and which information belongs to the second part of the CSI feedback. The size of the field indicating the size of HARQ feedback information and the size of the field indicating the size of CSI feedback are predefined.

Optionally, the CSI feedback and HARQ feedback information in UCI are located in different MAC subPDUs. CSI feedback and HARQ feedback information with information bits greater than 2 bits can be carried by two MAC CEs. Among them, HARQ feedback information and CSI feedback are carried by a single MAC CE, and two MAC CEs can be distinguished by different LCIDs.

CSI feedback and HARQ feedback information with information bits greater than 2 bits can be carried by three MAC CEs. Among them, HARQ feedback information, the first part of CSI feedback, and the second part of CSI feedback are carried by a single MAC CE, three MACs CE can be distinguished by different LCIDs.

S603: The network device parses the PUSCH to obtain UCI and uplink data.

The network device demodulates the received PUSCH, obtains the MAC PDU carried on the PUSCH, and determines the SDU and MAC CE in each MAC sub-PDU according to the format of the MAC PDU and the sub-header of each MAC sub-PDU, where , The uplink data can be obtained according to the SDU, and the UCI can be obtained according to the format of the MAC CE carrying UCI.

As shown in FIG. 14, an embodiment of the present application provides another method for transmitting uplink control information, including:

S1401. The terminal device sends indication information associated with the time-frequency resource of the PUSCH.

Correspondingly, the network device receives the indication information associated with the time-frequency resource of the PUSCH.

The indication information is used to determine the size of the UCI sent on the time-frequency resource of the PUSCH or the number of resource element REs occupied by the UCI in the time-frequency resource of the PUSCH.

The indication information includes at least one of the following information: indication information of the size of UCI, or indication information of the number of REs occupied by UCI, or the identifier of the device sending UCI (for example, cell radio network temporary identifier, C-RNTI)).

The indication information can be carried by a fixed format UCI. The fixed format UCI refers to one of the following types of UCI: the number of fields, sequence, meaning, and number of bits included are predefined or configured by the network device. ; The number of occupied REs, or the relationship between the number of occupied REs and the size of PUSCH resources, or the modulation mode is predefined or UCI configured by the network device.

For the indication information of the size of the UCI or the indication information of the number of REs occupied by the UCI, the network device can decode the UCI in the fixed format without knowing the identity of the device transmitting the UCI. For example, a fixed format UCI associated with the PUSCH occupies all REs of the first symbol of the PUSCH, the first field in the UCI is 4 bits, which is used to indicate the size of HARQ feedback information, and the second field is 6 bits. Used to indicate the size of the first part of the CSI feedback.

For the identification of the device that sends UCI, for example, UCI in a fixed format associated with the PUSCH occupies the first 8 REs of the PUSCH, and the first field in the UCI is 16 bits, which is used to indicate the identification of the device that sends UCI.

S1402. The terminal device sends UCI and uplink data on the time-frequency resource of the PUSCH.

Correspondingly, the network device receives UCI and uplink data on the time-frequency resources of PUSCH.

Among them, UCI and uplink data are carried on PUSCH.

UCI can be mapped to REs in predetermined positions in the time-frequency resources of PUSCH, and uplink data can be mapped to REs in other positions in the time-frequency resources of PUSCH. The multiplexing manner of UCI and uplink data may adopt the multiplexing manner in the prior art, or adopt the multiplexing manner described in FIG. 11 in step S602, which will not be repeated here.

For other content, please refer to the previous description, which will not be repeated here.

It can be understood that, in the above embodiments, the methods and/or steps implemented by the terminal device can also be implemented by components (such as chips or circuits) that can be used in the terminal device, and the methods and/or steps implemented by the network device can also be implemented by the terminal device. It can also be implemented by components that can be used in network devices.

The foregoing mainly introduces the solution provided by the embodiment of the present application from the perspective of interaction between various network elements. Correspondingly, an embodiment of the present application also provides a communication device, which is used to implement the foregoing various methods. The communication device may be the terminal device in the foregoing method embodiment, or a device including the foregoing terminal device, or a chip or functional module in the terminal device; or, the communication device may be the network device in the foregoing method embodiment, or A device containing the above-mentioned network equipment, or a chip or functional module in the network equipment. It can be understood that, in order to realize the above-mentioned functions, the communication device includes hardware structures and/or software modules corresponding to various functions. Those skilled in the art should easily realize that in combination with the units and algorithm steps of the examples described in the embodiments disclosed herein, the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a certain function is executed by hardware or computer software-driven hardware depends on the specific application and design constraints of the technical solution. Professionals and technicians can use different methods for each specific application to implement the described functions, but such implementation should not be considered beyond the scope of this application.

The embodiments of the present application may divide the communication device into functional modules according to the foregoing method embodiments. For example, each functional module may be divided corresponding to each function, or two or more functions may be integrated into one processing module. The above-mentioned integrated modules can be implemented in the form of hardware or software function modules. It should be noted that the division of modules in the embodiments of the present application is illustrative, and is only a logical function division, and there may be other division methods in actual implementation.

For example, take the communication device as the terminal device in the foregoing method embodiment as an example. FIG. 15 shows a schematic structural diagram of a communication device 150. The communication device 150 includes a processing module 1501 and a transceiver module 1502. The transceiver module 1502, which may also be referred to as a transceiver unit, includes a transmitting unit and/or a receiving unit, for example, a transceiver circuit, transceiver, transceiver, or communication interface, which is used to implement the transmission and/or transmission of the terminal device in the foregoing method embodiment. Receiving function. For example, step S602 in FIG. 6 and steps S1401 and S1402 in FIG. 14 are executed. The processing module 1501 is used to perform data processing to implement the processing function of the terminal device in the foregoing method embodiment, for example, to perform step S601 in FIG. 6.

Exemplarily, the processing module 1501 is configured to determine the time domain resources of the physical uplink shared channel PUSCH to be transmitted, and the PUSCH is used to carry uplink data.

The transceiver module 1502 is configured to send the PUSCH carrying UCI and uplink data if the time domain resources of the PUSCH and the physical uplink control channel PUCCH used to carry the uplink control information UCI overlap, where the uplink data and the UCI complex Used in the same media access control protocol data unit MAC PDU, the MAC PDU is carried on the PUSCH.

In a possible implementation manner, the CSI feedback includes a first part and a second part, and the MAC CE includes a field indicating the size of the first part of the CSI feedback and/or a field indicating the size of the second part of the CSI feedback.

In addition, the transceiver module 1502 is used to send indication information associated with the time-frequency resource of the physical uplink shared channel PUSCH, and the indication information is used to determine the size of the uplink control information UCI sent on the time-frequency resource of the PUSCH or the time-frequency resource of the PUSCH. The number of resource element REs occupied by UCI in the resource;

The transceiver module 1502 is also used to send UCI and uplink data on the time-frequency resources of the PUSCH, where the UCI and uplink data are carried on the PUSCH.

In a possible implementation manner, the processing module 1501 is configured to determine that the time domain resources of the PUSCH and the time domain resources of the physical uplink control channel PUCCH overlap, where the PUCCH is used to carry UCI and the PUSCH is used to carry uplink data.

In a possible implementation manner, the indication information includes at least one of the following information: indication information of the size of the UCI, or indication information of the number of REs occupied by the UCI, or identification of the device that sends the UCI.

In this embodiment, the communication device 150 is presented in the form of dividing various functional modules in an integrated manner. The "module" here may refer to a specific ASIC, a circuit, a processor and memory that executes one or more software or firmware programs, an integrated logic circuit, and/or other devices that can provide the above-mentioned functions. In a simple embodiment, those skilled in the art can imagine that the communication device 150 may take the form of the terminal device 105 shown in FIG. 2.

For example, the processor 180 in the terminal device 105 shown in FIG. 2 may invoke the computer execution instruction stored in the memory 120 to make the terminal device 105 execute the method in the foregoing method embodiment.

Specifically, the function/implementation process of the transceiver module 1502 in FIG. 15 may be implemented by the processor 180 in the terminal device 105 shown in FIG. 2 calling a computer execution instruction stored in the memory 120. Alternatively, the function/implementation process of the transceiver module 1502 in FIG. 15 may be implemented by the RF circuit 110 in the terminal device 105 shown in FIG. 2.

Since the communication device 150 provided in this embodiment can perform the above-mentioned method, the technical effects that can be obtained can refer to the above-mentioned method embodiment, which will not be repeated here.

For example, take the communication device as the network device in the foregoing method embodiment as an example. FIG. 16 shows a schematic structural diagram of a communication device 160. The communication device 160 includes a processing module 1601 and a transceiver module 1602. The transceiver module 1602, which may also be referred to as a transceiver unit, includes a transmitting unit and/or a receiving unit, for example, a transceiver circuit, transceiver, transceiver, or communication interface, which is used to implement the transmission and/or transmission of the terminal device in the foregoing method embodiment. Receiving function. For example, step S602 in FIG. 6 and steps S1401 and S1402 in FIG. 14 are executed. The processing module 1501 is used to perform data processing, and is used to implement the processing function of the terminal device in the foregoing method embodiment. For example, step S603 in FIG. 6 is executed.

Exemplarily, the transceiver module 1602 is configured to receive the physical uplink shared channel PUSCH, where the time domain resources of the PUSCH overlap with the time domain resources of the PUCCH used to carry uplink control information.

The processing module 1601 is configured to parse the PUSCH to obtain uplink control information UCI and uplink data, where the uplink data and UCI are multiplexed in the same media access control protocol data unit MAC PDU, and the MAC PDU is carried on the PUSCH.

In a possible implementation manner, the CSI feedback includes a first part and a second part, and the MAC CE includes a field indicating the size of the first part of the CSI and/or a field indicating the size of the second part of the CSI feedback.

In addition, the transceiver module 1602 is configured to receive indication information associated with the time-frequency resource of the physical uplink shared channel PUSCH, and the indication information is used to determine the size of the uplink control information UCI sent on the time-frequency resource of the PUSCH or the time-frequency resource of the PUSCH. The number of resource element REs occupied by UCI in the resource.

The transceiver module 1602 is configured to receive UCI and uplink data on the time-frequency resources of the PUSCH, where the UCI and uplink data are carried on the PUSCH.

In this embodiment, the communication device 160 is presented in the form of dividing various functional modules in an integrated manner. The "module" here may refer to a specific ASIC, a circuit, a processor and memory that executes one or more software or firmware programs, an integrated logic circuit, and/or other devices that can provide the above-mentioned functions. In a simple embodiment, those skilled in the art can imagine that the communication device 160 may take the form of the network device 300 shown in FIG. 3.

For example, the processor 321 in the network device 300 shown in FIG. 3 may invoke the computer execution instructions stored in the memory 322 to make the network device 300 execute the method in the foregoing method embodiment.

Specifically, the function/implementation process of the transceiver module 1602 in FIG. 16 may be implemented by the processor 321 in the network device 300 shown in FIG. 3 calling a computer execution instruction stored in the memory 322. Alternatively, the function/implementation process of the transceiver module 1602 in FIG. 16 may be implemented by the RF circuit 312 in the network device 300 shown in FIG. 3.

Since the communication device 160 provided in this embodiment can perform the above-mentioned method, the technical effects that can be obtained can refer to the above-mentioned method embodiment, which will not be repeated here.

An embodiment of the present application also provides a communication device. The communication device includes a processor, a memory, and a transceiver. The processor is coupled to the memory. When the processor executes the computer program or instruction in the memory, the The method corresponding to the terminal device or network device.

The embodiment of the present application also provides a chip, including: a processor and an interface, used to call and run a computer program stored in the memory from the memory, and execute the method corresponding to the terminal device or the network device in FIG. 6 and FIG. 14.

The embodiment of the present application also provides a computer-readable storage medium that stores instructions in the computer-readable storage medium. When the instructions run on a computer or a processor, the computer or the processor executes the steps shown in FIG. 6 and FIG. 14 The method corresponding to the terminal device or network device.

The embodiment of the present application also provides a computer program product containing instructions. When the instructions run on a computer or a processor, the computer or the processor executes the method corresponding to the terminal device or the network device in FIG. 6 and FIG. 14.

The embodiment of the present application provides a chip system, which includes a processor, and is used for a communication device to execute the method corresponding to the terminal device or the network device in FIG. 6 and FIG. 14.

In a possible design, the chip system further includes a memory for storing necessary program instructions and data for the terminal device. The chip system may include a chip, an integrated circuit, or may include a chip and other discrete devices, which is not specifically limited in the embodiment of the present application.

Among them, the communication device, chip, computer storage medium, computer program product, or chip system provided in the present application are all used to execute the method described above. Therefore, the beneficial effects that can be achieved can refer to the implementation manners provided above. The beneficial effects in the process will not be repeated here.

The processor involved in the embodiment of the present application may be a chip. For example, it can be a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), a system on chip (SoC), or a central processing unit. The central processor unit (CPU) can also be a network processor (NP), a digital signal processing circuit (digital signal processor, DSP), or a microcontroller (microcontroller unit, MCU) It can also be a programmable logic device (PLD) or other integrated chips.

The memory involved in the embodiments of the present application may be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. Among them, the non-volatile memory can be read-only memory (ROM), programmable read-only memory (programmable ROM, PROM), erasable programmable read-only memory (erasable PROM, EPROM), and electrically available Erase programmable read-only memory (electrically EPROM, EEPROM) or flash memory. The volatile memory may be random access memory (RAM), which is used as an external cache. By way of exemplary but not restrictive description, many forms of RAM are available, such as static random access memory (static RAM, SRAM), dynamic random access memory (dynamic RAM, DRAM), and synchronous dynamic random access memory (synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (double data rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchronous connection dynamic random access memory (synchlink DRAM, SLDRAM) ) And direct memory bus random access memory (direct rambus RAM, DR RAM). It should be noted that the memories of the systems and methods described herein are intended to include, but are not limited to, these and any other suitable types of memories.

It should be understood that in the various embodiments of the present application, the size of the sequence number of the above-mentioned processes does not mean the order of execution, and the execution order of each process should be determined by its function and internal logic, and should not correspond to the embodiments of the present application. The implementation process constitutes any limitation.

A person of ordinary skill in the art may realize that the units and algorithm steps of the examples described in combination with the embodiments disclosed herein can be implemented by electronic hardware or a combination of computer software and electronic hardware. Whether these functions are performed by hardware or software depends on the specific application and design constraint conditions of the technical solution. Professionals and technicians can use different methods for each specific application to implement the described functions, but such implementation should not be considered beyond the scope of this application.

Those skilled in the art can clearly understand that, for the convenience and conciseness of description, the specific working process of the system, device and unit described above can refer to the corresponding process in the foregoing method embodiment, which will not be repeated here.

In the several embodiments provided in this application, it should be understood that the disclosed system, device, and method may be implemented in other ways. For example, the device embodiments described above are only illustrative. For example, the division of the units is only a logical function division, and there may be other divisions in actual implementation, for example, multiple units or components may be combined or It can be integrated into another system, or some features can be ignored or not implemented. In addition, the displayed or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection between devices or units through some interfaces, and may be in electrical, mechanical or other forms.

The units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the objectives of the solutions of the embodiments.

In addition, the functional units in the various embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units may be integrated into one unit.

In the above-mentioned embodiments, it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented using a software program, it can be implemented in the form of a computer program product in whole or in part. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on the computer, the processes or functions described in the embodiments of the present application are generated in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instructions may be stored in 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 a website, computer, server, or data center. Transmission to another website, computer, server or data center via wired (such as coaxial cable, optical fiber, Digital Subscriber Line (DSL)) or wireless (such as infrared, wireless, microwave, etc.). The computer-readable storage medium may be any available medium that can be accessed by a computer, or may include one or more data storage devices such as servers and data centers that can be integrated with the medium. The usable medium may be a magnetic medium (for example, a floppy disk, a hard disk, and a magnetic tape), an optical medium (for example, a DVD), or a semiconductor medium (for example, a solid state disk (SSD)).

The above are only specific implementations of this application, but the protection scope of this application is not limited to this. Any person skilled in the art can easily think of changes or substitutions within the technical scope disclosed in this application. Should be covered within the scope of protection of this application. Therefore, the protection scope of this application should be subject to the protection scope of the claims.

Claims

A method for transmitting uplink control information, characterized in that it comprises:

Determining the time domain resource of the physical uplink shared channel PUSCH to be sent, where the PUSCH is used to carry uplink data;

If the time domain resources of the PUSCH overlap with the time domain resources of the physical uplink control channel PUCCH used to carry uplink control information UCI, the PUSCH carrying UCI and uplink data is transmitted, wherein the uplink data and the uplink data UCI is multiplexed in the same media access control protocol data unit MAC PDU, and the MAC PDU is carried on the PUSCH.
The method according to claim 1, wherein the UCI is carried in a MAC sub-PDU of the MAC PDU, wherein the MAC sub-PDU includes a MAC sub-header and a MAC control cell CE, and the MAC CE Used to carry the UCI, the MAC subheader includes a logical channel identifier LCID field and a length field, the LCID field is used to indicate that the MAC CE type is UCI, and the length field is used to indicate the MAC CE size.
The method according to claim 2, wherein the UCI includes channel state information CSI feedback and/or hybrid automatic repeat request HARQ feedback information.
The method according to claim 3, wherein the MAC CE includes a field indicating the size of the CSI feedback and/or a field indicating the size of the HARQ feedback information.
The method according to claim 3 or 4, wherein the CSI feedback includes a first part and a second part, and the MAC CE includes a field indicating the size of the first part of the CSI feedback and/or indicates the CSI The size of the second part of the feedback field.
The method according to claim 3, wherein the CSI feedback and HARQ feedback information in the UCI are located in different MAC sub-PDUs.
A method for transmitting uplink control information, characterized in that it comprises:

Receiving a physical uplink shared channel PUSCH, where the time domain resources of the PUSCH overlap with the time domain resources of the PUCCH used to carry uplink control information;

The PUSCH is parsed to obtain uplink control information UCI and uplink data, where the uplink data and the UCI are multiplexed in the same media access control protocol data unit MAC PDU, and the MAC PDU is carried on the PUSCH.
The method according to claim 7, wherein the UCI is carried in a MAC sub-PDU of the MAC PDU, wherein the MAC sub-PDU includes a MAC sub-header and a MAC control cell CE, and the MAC CE Used to carry the UCI, the MAC subheader includes a logical channel identifier LCID field and a length field, the LCID field is used to indicate that the MAC CE type is UCI, and the length field is used to indicate the MAC CE size.
The method according to claim 8, wherein the UCI includes channel state information CSI feedback and/or hybrid automatic repeat request HARQ feedback information.
The method according to claim 9, wherein the MAC CE includes a field indicating the size of the CSI feedback and/or a field indicating the size of the HARQ feedback information.
The method according to claim 9 or 10, wherein the CSI feedback includes a first part and a second part, and the MAC CE includes a field indicating the size of the first part of the CSI feedback and/or indicates the CSI The size of the second part of the feedback field.
The method according to claim 9, wherein the CSI feedback and HARQ feedback information in the UCI are located in different MAC sub-PDUs.
A method for transmitting uplink control information, characterized in that the method includes:

Send indication information associated with the time-frequency resource of the physical uplink shared channel PUSCH, where the indication information is used to determine the size of the uplink control information UCI sent on the time-frequency resource of the PUSCH or in the time-frequency resource of the PUSCH The number of resource elements RE occupied by the UCI;

The UCI and uplink data are sent on the time-frequency resource of the PUSCH, where the UCI and the uplink data are carried on the PUSCH.
[Corrected according to Rule 91 30.10.2019]

The method according to claim 13, wherein the method further comprises:

It is determined that the time domain resources of the PUSCH and the time domain resources of the physical uplink control channel PUCCH overlap, where the PUCCH is used to carry the UCI, and the PUSCH is used to carry the uplink data.
The method according to any one of claims 13-14, wherein the indication information comprises at least one of the following information: indication information of the size of the UCI, or indication of the number of REs occupied by the UCI Information, or the identifier of the device that sent the UCI.
The method according to any one of claims 13-15, wherein the UCI is mapped to an RE at a predetermined position in the time-frequency resource of the PUSCH, and the uplink data is mapped to the time-frequency resource of the PUSCH RE in other locations.
A method for transmitting uplink control information, characterized in that the method includes:

Receive indication information associated with the time-frequency resource of the physical uplink shared channel PUSCH, where the indication information is used to determine the size of the uplink control information UCI sent on the time-frequency resource of the PUSCH or in the time-frequency resource of the PUSCH The number of resource elements RE occupied by the UCI;

The UCI and uplink data are received on the time-frequency resource of the PUSCH, where the UCI and the uplink data are carried on the PUSCH.
The method according to claim 17, wherein the indication information comprises at least one of the following information: indication information of the size of the UCI, or indication information of the number of REs occupied by the UCI, or sending The identifier of the UCI device.
The method according to claim 17 or 18, wherein the UCI is mapped to an RE at a predetermined position in the time-frequency resource of the PUSCH, and the uplink data is mapped to an RE at a predetermined position in the time-frequency resource of the PUSCH. RE on.
A communication device, characterized by comprising a processing module and a transceiving module, the processing module is used to control the transceiving module to execute the method according to any one of claims 1-6, or execute the method as claimed in claim 7. -12 The method according to any one of claims 13-16, or the method according to any one of claims 17-19.
A communication device, comprising a processor, a memory, and a transceiver, the processor is coupled to the memory, and when the processor executes a computer program or instruction in the memory, it executes as claimed in claims 1-6 The method of any one, or the method of any one of claims 7-12, or the method of any one of claims 13-16, or the method of any one of claims 17- 19. The method of any one of.
A computer-readable storage medium having instructions stored in the computer-readable storage medium. When the instructions are executed on a computer or a processor, the computer or the processor can execute any of claims 1-6. The method of one item, or the method of any one of claims 7-12, or the method of any one of claims 13-16, or the method of any one of claims 17-19 Any of the methods described.
A computer program product containing instructions that, when the instructions run on a computer or a processor, cause the computer or the processor to execute the method according to any one of claims 1-6, or execute the method as described in any one of claims 1 to 6 The method according to any one of claims 7-12, or the method according to any one of claims 13-16, or the method according to any one of claims 17-19.