Method and device for transmitting uplink control information

Abstract

The present application discloses a method and apparatus for transmitting uplink control information, which relates to the field of communications and solves the problem of multiplexing UCI with a non-UE-specific PUSCH when there is a time domain overlap between PUSCH and PUCCH during a two-step random access process. The method comprises: determining the time domain resources of a physical uplink shared channel PUSCH to be transmitted, where the PUSCH is used to carry uplink data; if the time domain resources of the PUSCH overlap with the time domain resources of a physical uplink control channel PUCCH used to carry uplink control information UCI, transmitting a PUSCH carrying UCI and uplink data, wherein 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.

Description

Technical Field

[0001] The present application relates to the field of communications, and in particular to a method and apparatus for transmitting uplink control information. Background Art

[0002] In wireless communication systems such as long term evolution (LTE) and fifth generation (5G) new radio (NR), terminal devices need to enter the RRC connected state from the radio resource control (RRC) idle state or inactive state through random access. Alternatively, in the event of uplink desynchronization, no scheduling request (SR) resources, or multiple SR failures, random access is also used to resynchronize and request uplink resources to communicate with network devices.

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

[0004] Existing NR systems support multiplexing uplink control information (UCI) on the normal PUSCH. Specifically, during the two-step random access procedure, if the PUSCH and the physical uplink control channel (PUCCH) overlap in time domain resources, UCI is only supported on the user equipment (UE)-specific PUSCH. UE-specific PUSCH refers to the PUSCH dedicated to the UE. Summary of the Invention

[0005] 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 with a non-UE-specific PUSCH when there is time domain overlap between the PUSCH and the PUCCH during a two-step random access process.

[0006] To achieve the above objectives, the embodiments of the present application adopt the following technical solutions:

[0007] In a first aspect, a method for transmitting uplink control information is provided, including: determining a time domain resource for a physical uplink shared channel (PUSCH) to be sent, where the PUSCH is used to carry uplink data; if the time domain resource of the PUSCH overlaps with the time domain resource of a physical uplink control channel (PUCCH) used to carry uplink control information (UCI), sending the PUSCH carrying the UCI and uplink data, wherein 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.

[0008] The method for transmitting uplink control information provided in the embodiments of the present application enables network equipment to determine the location of UCI in the PUSCH, thereby correctly parsing the UCI, by having the terminal device carry multiplexed UCI and uplink data in the MAC PDU. This solves the problem of non-UE-specific PUSCH multiplexing UCI when there is time domain overlap between the PUSCH and PUCCH during two-step random access.

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

[0010] In one possible implementation, the UCI is carried in a MAC sub-PDU of a MAC PDU, wherein the MAC sub-PDU includes a MAC sub-header and a MAC control element CE, the MAC CE is used to carry the UCI, the MAC sub-header includes a logical channel identifier LCID field and a length field, the LCID field is used to indicate that the type of the MAC CE is UCI, and the length field is used to indicate the size of the MAC CE.

[0011] In a possible implementation, the UCI includes channel state information (CSI) feedback and / or hybrid automatic repeat request (HARQ) feedback information.

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

[0013] In one possible implementation, 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, so as to facilitate knowing the positions of the two parts of the CSI feedback in the MAC CE.

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

[0015] In a possible implementation, when the first symbol in the time domain resources where PUCCH and PUSCH overlap meets a preset condition, 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 can be one or more of the following conditions: the first symbol is not earlier than T2 time after the last symbol of any physical downlink shared channel PDSCH associated with UCI; the first symbol is not earlier than T3 time after the last symbol of any PDCCH that releases semi-persistent scheduling (SPS) PDSCH; the first symbol is not earlier than T4 time after the last symbol of the PDCCH that schedules PUSCH; the first symbol is not earlier than T5 time after the last symbol of any PDCCH that schedules PDSCH related to HARQ feedback information; the first symbol is not earlier than T6 time after the last symbol of any PDCCH that releases semi-persistent scheduling SPS PDSCH. T2, T3, T4, T5, and T6 are thresholds predefined by the protocol or configured by the base station.

[0016] In a second aspect, a method for transmitting uplink control information is provided, including: receiving a physical uplink shared channel PUSCH, wherein the time domain resources of the PUSCH overlap with the time domain resources of the PUCCH used to carry uplink control information; parsing the PUSCH to obtain uplink control information UCI and uplink data, wherein 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.

[0017] The method for transmitting uplink control information provided in the embodiments of the present application enables network equipment to determine the location of UCI in the PUSCH, thereby correctly parsing the UCI, by having the terminal device carry multiplexed UCI and uplink data in the MAC PDU. This solves the problem of non-UE-specific PUSCH multiplexing UCI when there is time domain overlap between the PUSCH and PUCCH during two-step random access.

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

[0019] In one possible implementation, the UCI is carried in a MAC sub-PDU of a MAC PDU, wherein the MAC sub-PDU includes a MAC sub-header and a MAC control element CE, the MAC CE is used to carry the UCI, the MAC sub-header includes a logical channel identifier LCID field and a length field, the LCID field is used to indicate that the type of the MAC CE is UCI, and the length field is used to indicate the size of the MAC CE.

[0020] In a possible implementation, the UCI includes channel state information (CSI) feedback and / or hybrid automatic repeat request (HARQ) feedback information.

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

[0022] In one possible implementation, 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, so as to facilitate knowing the positions of the two parts of the CSI feedback in the MAC CE.

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

[0024] In a possible implementation, when the first symbol in the time domain resources where PUCCH and PUSCH overlap meets a preset condition, 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 can be one or more of the following conditions: the first symbol is not earlier than T2 time after the last symbol of any physical downlink shared channel PDSCH associated with UCI; the first symbol is not earlier than T3 time after the last symbol of any PDCCH that releases semi-persistent scheduling (SPS) PDSCH; the first symbol is not earlier than T4 time after the last symbol of the PDCCH that schedules PUSCH; the first symbol is not earlier than T5 time after the last symbol of any PDCCH that schedules PDSCH related to HARQ feedback information; the first symbol is not earlier than T6 time after the last symbol of any PDCCH that releases semi-persistent scheduling SPS PDSCH. T2, T3, T4, T5, and T6 are thresholds predefined by the protocol or configured by the base station.

[0025] In a third aspect, a method for transmitting uplink control information is provided, the method comprising: sending indication information associated with the time-frequency resources of a physical uplink shared channel (PUSCH), the indication information being used to determine the size of uplink control information (UCI) sent on the time-frequency resources of the PUSCH or the number of resource elements (RE) occupied by the UCI in the time-frequency resources of the PUSCH; and sending UCI and uplink data on the time-frequency resources of the PUSCH, wherein the UCI and uplink data are carried on the PUSCH.

[0026] The method for transmitting uplink control information provided in the embodiments of the present application allows the terminal device to indicate which terminal device sent the PUSCH, or to indicate the size of the UCI or the number of occupied REs, so that the network device can determine the location of the UCI in the PUSCH and thus correctly parse the UCI. This solves the problem of non-UE-specific PUSCH multiplexing UCI when there is time domain overlap between the PUSCH and PUCCH during the two-step random access process.

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

[0028] In a possible implementation, when the first symbol in the time domain resources where PUCCH and PUSCH overlap meets a preset condition, 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 can be one or more of the following conditions: the first symbol is not earlier than T2 time after the last symbol of any physical downlink shared channel PDSCH associated with UCI; the first symbol is not earlier than T3 time after the last symbol of any PDCCH that releases semi-persistent scheduling (SPS) PDSCH; the first symbol is not earlier than T4 time after the last symbol of the PDCCH that schedules PUSCH; the first symbol is not earlier than T5 time after the last symbol of any PDCCH that schedules PDSCH related to HARQ feedback information; the first symbol is not earlier than T6 time after the last symbol of any PDCCH that releases semi-persistent scheduling SPS PDSCH. T2, T3, T4, T5, and T6 are thresholds predefined by the protocol or configured by the base station.

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

[0030] In a possible implementation, the indication information includes at least one of the following information: indication information of the UCI size, or indication information of the number of REs occupied by the UCI, or an identifier of the device sending the UCI. Such information facilitates determining the specific location of the UCI.

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

[0032] In a fourth aspect, a method for transmitting uplink control information is provided, the method also including: receiving indication information associated with the time-frequency resources of a physical uplink shared channel PUSCH, the indication information being used to determine the size of uplink control information UCI sent on the time-frequency resources of the PUSCH or the number of resource elements RE occupied by the UCI in the time-frequency resources of the PUSCH; receiving UCI and uplink data on the time-frequency resources of the PUSCH, wherein the UCI and uplink data are carried on the PUSCH.

[0033] The method for transmitting uplink control information provided in the embodiments of the present application allows the terminal device to indicate which terminal device sent the PUSCH, or to indicate the size of the UCI or the number of occupied REs, so that the network device can determine the location of the UCI in the PUSCH and thus correctly parse the UCI. This solves the problem of non-UE-specific PUSCH multiplexing UCI when there is time domain overlap between the PUSCH and PUCCH during the two-step random access process.

[0034] In a possible implementation, the indication information includes at least one of the following information: indication information of the UCI size, or indication information of the number of REs occupied by the UCI, or an identifier of the device sending the UCI. Such information facilitates determining the specific location of the UCI.

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

[0036] In the fifth aspect, a communication device is provided, comprising a processing module and a transceiver module, wherein the processing module is used to control the transceiver module to execute the method as described in the first aspect and any one of the items, or to execute the method as described in the second aspect and any one of the items, or to execute the method as described in the third aspect and any one of the items, or to execute the method as described in the fourth aspect and any one of the items.

[0037] In a sixth aspect, a communication device is provided, comprising a processor, a memory, and a transceiver, wherein the processor is coupled to the memory, and when the processor executes a computer program or instruction in the memory, the method as described in the first aspect and any one of the items thereof is executed, or the method as described in the second aspect and any one of the items thereof is executed, or the method as described in the third aspect and any one of the items thereof is executed, or the method as described in the fourth aspect and any one of the items thereof is executed.

[0038] In the seventh aspect, a chip is provided, comprising: a processor and an interface, for calling and running a computer program stored in the memory from a memory, executing the method as described in the first aspect and any one of the items, or executing the method as described in the second aspect and any one of the items, or executing the method as described in the third aspect and any one of the items, or executing the method as described in the fourth aspect and any one of the items.

[0039] In an eighth aspect, a computer-readable storage medium is provided, wherein instructions are stored in the computer-readable storage medium. When the instructions are executed on a computer or a processor, the computer or the processor executes the method according to the first aspect and any one of the items, or the method according to the second aspect and any one of the items, or the method according to the third aspect and any one of the items, or the method according to the fourth aspect and any one of the items.

[0040] In the ninth aspect, a computer program product comprising instructions is provided, which, when the instructions are executed on a computer or a processor, causes the computer or the processor to execute the method as described in the first aspect and any one of the items, or to execute the method as described in the second aspect and any one of the items, or to execute the method as described in the third aspect and any one of the items, or to execute the method as described in the fourth aspect and any one of the items.

[0041] The technical effects of the fifth to ninth aspects can refer to the contents of the various possible implementation methods of the first to fourth aspects. BRIEF DESCRIPTION OF THE DRAWINGS

[0042] Figure 1 A schematic diagram of the architecture of a communication system provided in an embodiment of the present application;

[0043] Figure 2 A schematic diagram of the structure of a terminal device provided in an embodiment of the present application;

[0044] Figure 3 A schematic diagram of the structure of a network device provided in an embodiment of the present application;

[0045] Figure 4 A schematic diagram of a four-step random access process provided in an embodiment of the present application;

[0046] Figure 5 A schematic diagram of a two-step random access process provided in an embodiment of the present application;

[0047] Figure 6 A flow chart of a method for transmitting uplink control information provided in an embodiment of the present application Figure 1 ;

[0048] Figure 7 A schematic diagram of a MAC PDU provided in an embodiment of the present application;

[0049] Figure 8 A schematic diagram of a MAC subheader provided in an embodiment of the present application;

[0050] Figure 9 An example of a method for carrying CSI feedback via MAC CE provided in an embodiment of the present application Figure 1 ;

[0051] Figure 10 An example of a method for carrying CSI feedback via MAC CE provided in an embodiment of the present application Figure 2 ;

[0052] Figure 11 A schematic diagram of PUSCH multiplexing HARQ feedback information and CSI feedback provided in an embodiment of the present application;

[0053] Figure 12 An example of a method for carrying HARQ feedback information and CSI feedback via MAC CE provided in an embodiment of the present application Figure 1 ;

[0054] Figure 13 An example of a method for carrying HARQ feedback information and CSI feedback via MAC CE provided in an embodiment of the present application Figure 2 ;

[0055] Figure 14 A flow chart of a method for transmitting uplink control information provided in an embodiment of the present application Figure 1 ;

[0056] Figure 15 A schematic diagram of the structure of a communication device provided in an embodiment of the present application Figure 1 ;

[0057] Figure 16 A schematic diagram of the structure of a communication device provided in an embodiment of the present application Figure 2 . DETAILED DESCRIPTION

[0058] The embodiments of the present application can be applied to both time division duplexing (TDD) and frequency division duplexing (FDD) scenarios.

[0059] The embodiments of the present application are described based 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 the present application can also be applied to other wireless communication networks, such as the sixth generation mobile communication system, and the corresponding names can also be replaced by 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.

[0060] The embodiments of the present application may be applicable to a long term evolution (LTE) system, such as a narrowband internet of things (NB-IoT) system, or to an advanced long term evolution (LTE-Advanced, LTE-A) system. The embodiments of the present application may also be applicable to other wireless communication systems, such as the global system for mobile communication (GSM), the universal mobile telecommunications system (UMTS), the code division multiple access (CDMA) system, and new network equipment systems.

[0061] like Figure 1 As shown, the communication system 100 provided in the embodiment of the present application includes a network device 101 and terminal devices 102-107.

[0062] The terminal devices involved in the embodiments of the present application may be devices that provide voice and / or data connectivity to users, handheld devices with wireless connection capabilities, 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 may be a mobile terminal, such as a mobile phone (or "cellular" phone) and a computer with a mobile terminal. For example, the wireless terminal may be a portable, pocket-sized, handheld, computer-built-in, or vehicle-mounted mobile device that exchanges voice and / or data with a radio 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 (PDAs), and other devices. A wireless terminal may also be referred to as a system, subscriber unit, subscriber station, mobile station, mobile station, remote station, access point, remote terminal, access terminal, user terminal, user agent, user device, or user equipment. For example, the terminal device may be high-speed rail communication equipment 102, smart air conditioner 103, smart fuel dispenser 104, mobile phone 105, smart teacup 106, printer 107, etc., but this application does not limit this.

[0063] The network device involved in the embodiment of the present application may be a base station, which can be used to convert received air frames into and from Internet Protocol (IP) packets, and serve as a router between the wireless terminal and the rest of the access network, wherein the rest of the access network may include IP network devices. 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, or a base station (NodeB) in wideband code division multiple access (WCDMA), or an evolutionary Node B (eNB or e-NodeB) in LTE, or a gNB in ​​5G, and the embodiment of the present application is not limited. The above base stations are only examples, and the network device can also be a relay station, an access point, a vehicle-mounted device, a wearable device, and other types of devices.

[0064] like Figure 2 As shown, the structure of the terminal device is described by taking the terminal device as a mobile phone as an example.

[0065] 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, a processor 180, a Bluetooth module 181, and a power supply 190.

[0066] RF circuit 110 can be used to receive and transmit signals during information transmission or calls. It can receive downlink data from the base station and pass it to processor 180 for processing; it can also send uplink data to the base station. Typically, RF circuits include but are not limited to antennas, at least one amplifier, a transceiver, a coupler, a low-noise amplifier, a duplexer, and other components.

[0067] 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 the software programs 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 disk storage device, a flash memory device, or other volatile solid-state storage device. The memory 120 stores an operating system that enables the terminal device 105 to run, such as the operating system 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 can store an operating system and various application programs, and can also store codes for executing the methods of the embodiments of the present application.

[0068] The input unit 130 (e.g., 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, which may collect user touch operations on or near the touch screen.

[0069] The display unit 140 (i.e., display screen) can 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. The display screen 141 may be configured in the form of a liquid crystal display, a light-emitting diode, etc. The display unit 140 can be used to display the various graphical user interfaces described in this application. The touch screen 131 can be covered on the display screen 141, or the touch screen 131 and the display screen 141 can be integrated to realize the input and output functions of the terminal device 105. After integration, it can be simply referred to as a touch screen display.

[0070] The terminal device 105 may further include at least one sensor 150, such as a light sensor, a motion sensor, or other sensors such as a gyroscope, a barometer, a hygrometer, a thermometer, and an infrared sensor.

[0071] The audio circuit 160, speaker 161, and microphone 162 provide an audio interface between the user and the terminal device 105. The audio circuit 160 can convert the received audio data into an electrical signal and transmit it to the speaker 161, which converts it into a sound signal for output. On the other hand, the microphone 162 converts the collected sound signal into an electrical signal, which is received by the audio circuit 160 and converted into audio data. The audio data is then output to the RF circuit 110 for transmission to, for example, another terminal, or the audio data is output to the memory 120 for further processing.

[0072] Wi-Fi is a short-range wireless transmission technology. The terminal device 105 can help users send and receive emails, browse web pages, and access streaming media through the Wi-Fi module 170, which provides users with wireless broadband Internet access.

[0073] The processor 180 is the control center of the terminal device 105. It uses various interfaces and lines to connect various parts of the entire terminal. By running or executing software programs stored in the memory 120 and calling data stored in the memory 120, it performs various functions of the terminal device 105 and processes data. In this application, the processor 180 can refer to one or more processors, and the processor 180 can include one or more processing units. The processor 180 can also integrate an application processor and a baseband processor, wherein the application processor mainly processes the operating system, user interface, and application programs, and the baseband processor mainly processes wireless communications. It is understandable that the above-mentioned baseband processor may not be integrated into the processor 180. In this application, the processor 180 can run the operating system, application programs, user interface display and touch response, as well as the communication method described in the embodiments of this application.

[0074] 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 to exchange data.

[0075] The terminal device 105 also includes a power supply 190 (eg, a battery) for supplying power to various components. The power supply can be logically connected to the processor 180 via a power management system, thereby managing charging, discharging, and power consumption.

[0076] like Figure 3 As shown, an embodiment of the present application provides a 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 referred to as digital units (DU)) 320. The RRU 310 may be referred to as a transceiver unit. Optionally, the transceiver unit 310 may also be referred to as a transceiver, a transceiver circuit, a transceiver, a transmitter, a receiver, etc., and may include at least one antenna 311 and an RF circuit 312. Optionally, the transceiver unit 310 may include a receiving unit and a transmitting unit, the receiving unit may correspond to a receiver (or a receiver, a receiving circuit), and the transmitting unit may correspond to a transmitter (or a transmitter, a transmitting circuit). The RRU 310 part is mainly used for receiving and transmitting radio frequency signals and converting radio frequency signals into baseband signals, for example, for sending indication information to a terminal device. The BBU 320 part is mainly used for baseband processing, controlling the network device, etc. The RRU 310 and the BBU 320 may be physically arranged together or physically separated, that is, a distributed base station.

[0077] The BBU 320 is the control center of the network device, which can also be called a processing unit, and is mainly used to perform baseband processing functions such as channel coding, multiplexing, modulation, spread spectrum, etc. For example, the BBU 320 can be used to control the network device to execute the method involved in this application.

[0078] In one example, the BBU 320 may be composed of one or more single boards, and the multiple single boards may jointly support a wireless access network with a single access standard (such as an LTE network), or may separately support wireless access networks with different access standards (such as an LTE network, a 5G network, or other networks). The BBU 320 also 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, such as controlling 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. That is, a memory and a processor may be separately set on each single board. Alternatively, multiple single boards may share the same memory and processor. In addition, necessary circuits may be set on each single board.

[0079] In addition, the network equipment is not limited to the above-mentioned forms, and may also be other forms: for example, including a BBU and an adaptive radio unit (ARU), or a BBU and an active antenna unit (AAU); it may also be customer premises equipment (CPE), or it may be other forms, which are not limited in this application.

[0080] First, the four-step random access process currently performed by terminal devices in wireless communication systems such as LTE and 5G NR is described. Figure 4 Shown, including:

[0081] S401. The terminal device sends a random access preamble to the network device.

[0082] It can also be called that the terminal device sends the first message (Msg1) to the network device.

[0083] The purpose of the random access preamble is to notify the terminal device of 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. The calibration information is then notified to the terminal device via the timing advance command.

[0084] S402: After detecting the random access preamble, the network device sends a random access response to the terminal device.

[0085] It is also called that the network device sends a second message (Msg2) to the terminal device.

[0086] The random access response includes the sequence number of the received random access preamble, the timing advance instruction, the uplink resource allocation information and the cell radio network temporary identifier, etc.

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

[0088] It is also called that the terminal device sends the third message (Msg3) to the network device.

[0089] The uplink data can carry the unique identifier of the terminal device.

[0090] 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 a random access response for the terminal device. The terminal device may send uplink data in the allocated uplink resources according to the indication of the random access response, for example, sending a PUSCH in the third message.

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

[0092] It is also called that the network device sends the fourth message (Msg4) to the terminal device.

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

[0094] For the above four-step random access process, the four information exchanges will result in a high access delay, so a two-step random access process is introduced in the 5G NR wireless communication system. Figure 5 As shown, the two-step random access process includes:

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

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

[0097] The description of the random access preamble and uplink data is as mentioned above and will not be repeated here.

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

[0099] The description of random access response is as mentioned above and will not be repeated here.

[0100] As mentioned above, although the above-mentioned 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 not dedicated to the terminal device. In the existing NR system, when UCI is multiplexed on PUSCH, UCI and data are independently encoded and use different resource elements (RE). Since the UCI size of each UE is not fixed, the number of REs occupied by the UCI of each UE is not fixed. Therefore, UCI can only be multiplexed on the UE-specific PUSCH, so that the network device can determine whether UCI is multiplexed in the PUSCH and the number of REs occupied by the multiplexed UCI based on the resource configuration and scheduling information of the terminal device, so that the UCI can be correctly parsed. For non-UE-specific PUSCH, the network device cannot determine which terminal device sent the PUSCH, and it is also impossible to determine whether UCI is multiplexed on the PUSCH and the number of REs occupied by UCI.

[0101] An embodiment of the present application provides a method for transmitting uplink control information, in which a terminal device carries multiplexed UCI and uplink data in a media access control protocol data unit (MAC PDU), or indicates a user identifier for sending a PUSCH, or indicates the size of the UCI multiplexed on the PUSCH or the number of REs occupied, so that a network device can determine the position of the UCI in the PUSCH, thereby correctly parsing the UCI.

[0102] For ease of description, unless otherwise specified, the PUSCH involved in the embodiments of the present application refers to contention-based PUSCH, including PUSCH of contention resources in the random access process (especially, the two-step random access process), and may also include other contention-based PUSCH.

[0103] like Figure 6 As shown, an embodiment of the present application provides a method for transmitting uplink control information, including:

[0104] S601. The terminal device determines the time domain resources of the PUSCH to be sent.

[0105] The PUSCH is used to carry uplink data. That is, if a terminal device has uplink data to send, the terminal device needs to determine the time domain resources of the PUSCH that carries the uplink data.

[0106] S602: If the time domain resources of the PUSCH overlap with the time domain resources of the PUCCH, the terminal device sends a PUSCH carrying UCI and uplink data.

[0107] Accordingly, the network device receives the PUSCH.

[0108] The PUCCH is used to carry UCI, which may include channel state information (CSI) feedback and / or hybrid automatic repeat request (HARQ) feedback information (such as acknowledgement (ACK) information or non-acknowledgement (NACK) information).

[0109] 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.

[0110] The time domain resources of the PUSCH and PUCCH overlap. This means that UCI and uplink data need to be sent simultaneously and multiplexed on the PUSCH. The uplink data and UCI can be multiplexed on the same MAC PDU, which can be carried on the PUSCH. The timing relationship between the first symbol in the time domain resources where PUCCH and PUSCH overlap and the associated PDSCH and PDCCH must meet the processing capabilities of the terminal device.

[0111] If the UCI only includes HARQ feedback information, the terminal device only sends PUCCH and does not send PUSCH, and there is no need to multiplex the UCI in the PUSCH.

[0112] If the UCI only contains CSI feedback and at least one of the PUCCH and PUSCH is used to respond to downlink control information (DCI), then when the first symbol in the time domain resources where the PUCCH and PUSCH overlap meets the preset conditions, 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 conditions are related to the processing capability of the UE. Specifically, the preset conditions can be one or more of the following conditions:

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

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

[0115] 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. The uplink data and UCI can be multiplexed in the same MAC PDU, and the MAC PDU can be carried on the PUSCH.

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

[0117] like Figure 7 Figure 2 is a schematic diagram of a MAC PDU. A MAC PDU includes one or more MAC sub-PDUs (MACsubPDUs). MAC sub-PDUs can be divided into MAC sub-PDUs including MAC service data units (SDUs), MAC sub-PDUs including MAC control elements (CEs), and MAC sub-PDUs including padding (optional).

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

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

[0120] The first MAC sub-PDU includes a second MAC sub-header and a fixed-sized MAC CE. The second MAC sub-header includes an LCID field and a length L field, wherein 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.

[0121] The second MAC sub-PDU includes a third MAC subheader and a variable-sized MAC CE. The third MAC subheader includes an R field, an F field, an LCID field, and an L field, wherein 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 size of the MAC CE.

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

[0123] Specifically, the MAC sub-PDU carrying UCI includes a MAC subheader and a 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 (L) field. The R field is a reserved field and is usually 0; the F field is used to indicate the size of the L field, as described above; the LCID field is used to indicate that the type of the MAC CE is UCI; and the length field L is used to indicate the size of the MAC CE. For example, the LCID of the MAC CE carrying CSI feedback can be predefined as 35. When the LCID is 35, it indicates that the type of the MAC CE is CSI feedback.

[0124] The CSI feedback may include only one part or two parts (i.e., a first part and a second part). Regardless of whether the CSI feedback includes one part or two parts, it may be carried by a single MAC CE. If the CSI feedback includes two parts, and the CSI feedback is carried by two MAC CEs, the first and second parts of the CSI feedback may each be carried by a separate MAC CE, and the two MAC CEs may be distinguished by different LCIDs.

[0125] like Figure 9 As shown, when CSI feedback is carried by a MAC CE, the CSI feedback information can be combined in sequence. Even if the CSI includes two parts, after the network device decodes the relevant information of the terminal device (such as the identifier), the two parts of the CSI feedback information can be distinguished.

[0126] like Figure 10 As shown, the MAC CE may include a field indicating the size of the first part of the CSI feedback (e.g., in bytes) and / or a field indicating the size of the second part of the CSI feedback (e.g., in bytes). The above fields may 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 a value of 0. The size and position 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 sizes of all fields in the MAC CE in the drawings of this application are only examples.

[0127] If the UCI contains HARQ feedback information with less than or equal to 2 bits of information, the HAR feedback information is multiplexed on the PUSCH by overlaying the REs used to transmit uplink data on the PUSCH. If the UCI contains CSI feedback and / or HARQ feedback information with more than 2 bits of information, the CSI feedback and / or HARQ feedback information with more than 2 bits of information are multiplexed with the uplink data on the PUSCH using the MAC CE carrying method described above. The following first describes this overlay method.

[0128] like Figure 11 As shown, the existing 5G NR wireless communication system supports multiplexing UCI on PUSCH, including multiplexing HARQ feedback information and CSI feedback on PUSCH. As mentioned above, CSI feedback can include two parts.

[0129] 1) Determine the number of REs required to map the HARQ feedback information and CSI feedback according to the number of bits and modulation order after encoding the HARQ feedback information and CSI feedback.

[0130] 2) Mapping HARQ feedback information starts from the first PUSCH symbol after the PUSCH demodulation reference signal (DMRS), and mapping CSI feedback starts from the first non-DMRS PUSCH symbol.

[0131] 3) If the remaining number of REs required for mapping is greater than or equal to the number of REs available for the current symbol, the current symbol is used to map the UCI; if the remaining number of REs required for mapping is less than the number of REs available for the current symbol, the first REs are used to map UCI, where n=1, 2, ..., N2, N1 is the number of REs available for the current symbol, and N2 is the number of remaining REs required for mapping.

[0132] 4) HARQ feedback information with less than or equal to 2 information bits is multiplexed on the PUSCH using puncturing. That is, HARQ feedback information with less than or equal to 2 information bits will overwrite the original modulation symbols on the RE. CSI feedback and / or HARQ feedback information with more than 2 information bits is multiplexed on the PUSCH using rate matching. That is, the data portion is only mapped to the REs other than those mapped to the CSI feedback and / or HARQ feedback information with more than 2 information bits, and the code rate of the data portion is adjusted based on the number of remaining REs.

[0133] like Figure 12As shown, CSI feedback and HARQ feedback information with information bits greater than 2 bits can be carried by one MAC CE, that is, the CSI feedback and HARQ feedback information with information bits greater than 2 bits are combined together in sequence. When the network device decodes the relevant information of the terminal device (such as the identifier), the CSI feedback and HARQ feedback information with information bits greater than 2 bits can be distinguished.

[0134] like Figure 13 As shown, the MAC CE may also include a field indicating the CSI feedback size (e.g., in bytes) and / or a field indicating the HARQ feedback information size (e.g., in bytes). Furthermore, 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 fields may 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 sizes of the field indicating the HARQ feedback information size and the field indicating the CSI feedback size are predefined.

[0135] Optionally, the CSI feedback and HARQ feedback information in the UCI are located in different MAC sub-PDUs. The CSI feedback and HARQ feedback information with information bits greater than 2 bits can be carried by two MAC CEs, where the HARQ feedback information and CSI feedback are each carried by a separate MAC CE, and the two MAC CEs can be distinguished by different LCIDs.

[0136] CSI feedback and HARQ feedback information with information bits greater than 2 bits can be carried by three MAC CEs, wherein the HARQ feedback information, the first part of the CSI feedback and the second part of the CSI feedback are respectively carried by a separate MAC CE, and the three MAC CEs can be distinguished by different LCIDs.

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

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

[0139] The method for transmitting uplink control information provided in the embodiments of the present application enables network equipment to determine the location of UCI in the PUSCH, thereby correctly parsing the UCI, by having the terminal device carry multiplexed UCI and uplink data in the MAC PDU. This solves the problem of non-UE-specific PUSCH multiplexing UCI when there is time domain overlap between the PUSCH and PUCCH during two-step random access.

[0140] like Figure 14 As shown, the embodiment of the present application provides another method for transmitting uplink control information, including:

[0141] S1401. The terminal device sends indication information associated with the time-frequency resources of PUSCH.

[0142] Accordingly, the network device receives indication information associated with the time-frequency resources of the PUSCH.

[0143] The indication information is used to determine the size of the UCI sent on the time-frequency resources of the PUSCH or the number of resource elements (REs) occupied by the UCI in the time-frequency resources of the PUSCH.

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

[0145] The indication information may be carried by a fixed-format UCI, where the fixed-format UCI refers to one of the following types of UCI: the number of fields, order, meaning, and number of bits included are predefined or configured by the network device; the number of REs occupied, or the relationship between the number of REs occupied and the PUSCH resource size, or the modulation method is predefined or configured by the network device.

[0146] For the information indicating the size of the UCI or the number of REs occupied by the UCI, the network device can decode the fixed-format UCI without knowing the identity of the device transmitting the UCI. For example, the 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 the HARQ feedback information, and the second field is 6 bits, which is used to indicate the size of the first part of the CSI feedback.

[0147] For the identifier of the device sending the UCI, for example, the fixed-format UCI associated with the PUSCH occupies the first 8 REs of the PUSCH. The first field in the UCI is 16 bits, which is used to indicate the identifier of the device sending the UCI.

[0148] S1402. The terminal device sends UCI and uplink data on the time-frequency resources of PUSCH.

[0149] Accordingly, the network device receives UCI and uplink data on the time-frequency resources of the PUSCH.

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

[0151] UCI can be mapped to a predetermined position RE in the PUSCH time-frequency resource, and uplink data can be mapped to other positions RE in the PUSCH time-frequency resource. The UCI and uplink data can be multiplexed in the manner of the prior art, or in the manner of step S602. Figure 11 The multiplexing method described above will not be repeated here.

[0152] For other contents, please refer to the previous description and will not be repeated here.

[0153] The method for transmitting uplink control information provided in the embodiments of the present application allows the terminal device to indicate which terminal device sent the PUSCH, or to indicate the size of the UCI or the number of occupied REs, so that the network device can determine the location of the UCI in the PUSCH and thus correctly parse the UCI. This solves the problem of non-UE-specific PUSCH multiplexing UCI when there is time domain overlap between the PUSCH and PUCCH during the two-step random access process.

[0154] 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 for the terminal device, and the methods and / or steps implemented by the network device can also be implemented by components that can be used for the network device.

[0155] The above description primarily describes the solutions provided by the embodiments of the present application from the perspective of interaction between various network elements. Accordingly, the embodiments of the present application also provide a communication device for implementing the various methods described above. The communication device can be the terminal device described in the method embodiments described above, or a device including the terminal device described above, or a chip or functional module within the terminal device; or the communication device can be the network device described in the method embodiments described above, or a device including the network device described above, or a chip or functional module within the network device. It will be understood that, to implement the aforementioned functions, the communication device includes hardware structures and / or software modules corresponding to the respective functions. Those skilled in the art will readily appreciate that, in conjunction with the various exemplary units and algorithm steps described in the embodiments disclosed herein, the present application can be implemented in hardware or a combination of hardware and computer software. Whether a function is implemented in hardware or by computer software driving hardware depends on the specific application and design constraints of the technical solution. Professionals may use different methods to implement the described functions for each specific application, but such implementations should not be considered beyond the scope of this application.

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

[0157] For example, take the communication device as the terminal device in the above method embodiment. Figure 15 The structure diagram of a communication device 150 is shown. The communication device 150 includes a processing module 1501 and a transceiver module 1502. The transceiver module 1502, which can also be called a transceiver unit, includes a sending unit and / or a receiving unit, which can be, for example, a transceiver circuit, a transceiver, a transceiver or a communication interface, to implement the sending and / or receiving functions of the terminal device in the above method embodiment. For example, Figure 6 Step S602 in Figure 14 The processing module 1501 is used to process data to implement the processing function of the terminal device in the above method embodiment, such as executing steps S1401 and S1402. Figure 6 Step S601 in .

[0158] Exemplarily, the processing module 1501 is configured to determine a time domain resource for transmitting a physical uplink shared channel PUSCH, where the PUSCH is used to carry uplink data.

[0159] The transceiver module 1502 is configured to send a PUSCH carrying UCI and 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, wherein 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.

[0160] In one possible implementation, the UCI is carried in a MAC sub-PDU of a MAC PDU, wherein the MAC sub-PDU includes a MAC sub-header and a MAC control element CE, the MAC CE is used to carry the UCI, the MAC sub-header includes a logical channel identifier LCID field and a length field, the LCID field is used to indicate that the type of the MAC CE is UCI, and the length field is used to indicate the size of the MAC CE.

[0161] In a possible implementation, the UCI includes channel state information (CSI) feedback and / or hybrid automatic repeat request (HARQ) feedback information.

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

[0163] In a possible implementation, 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.

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

[0165] In addition, the transceiver module 1502 is configured to send indication information associated with the time-frequency resources of the physical uplink shared channel PUSCH, where the indication information is used to determine the size of uplink control information (UCI) sent on the time-frequency resources of the PUSCH or the number of resource elements (REs) occupied by the UCI in the time-frequency resources of the PUSCH;

[0166] The transceiver module 1502 is further configured to send UCI and uplink data on the time-frequency resources of the PUSCH, wherein the UCI and uplink data are carried on the PUSCH.

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

[0168] In a possible implementation manner, the indication information includes at least one of the following information: indication information of the UCI size, or indication information of the number of REs occupied by the UCI, or an identifier of a device sending the UCI.

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

[0170] In this embodiment, the communication device 150 is presented in the form of various functional modules divided in an integrated manner. Here, "module" can refer to a specific ASIC, circuit, processor and memory that executes one or more software or firmware programs, integrated logic circuit, and / or other devices that can provide the above functions. In a simple embodiment, those skilled in the art can imagine that the communication device 150 can be used. Figure 2 The form of the terminal device 105 is shown.

[0171] for example, Figure 2 The processor 180 in the terminal device 105 shown can call the computer-executable instructions stored in the memory 120 to enable the terminal device 105 to execute the method in the above method embodiment.

[0172] Specifically, Figure 15 The function / implementation process of the transceiver module 1502 can be achieved by Figure 2 The processor 180 in the terminal device 105 shown calls the computer execution instructions stored in the memory 120 to implement. Or, Figure 15 The function / implementation process of the transceiver module 1502 can be achieved by Figure 2 This is implemented by the RF circuit 110 in the terminal device 105 shown in FIG.

[0173] Since the communication device 150 provided in this embodiment can execute the above method, the technical effects that can be obtained can refer to the above method embodiments and will not be repeated here.

[0174] For example, the communication device is taken as the network device in the above method embodiment. Figure 16 The structure diagram of a communication device 160 is shown. The communication device 160 includes a processing module 1601 and a transceiver module 1602. The transceiver module 1602, which can also be called a transceiver unit, includes a sending unit and / or a receiving unit, which can be, for example, a transceiver circuit, a transceiver, a transceiver or a communication interface, to implement the sending and / or receiving functions of the terminal device in the above method embodiment. For example, Figure 6 Step S602 in Figure 14The processing module 1501 is used to process data to implement the processing function of the terminal device in the above method embodiment. Figure 6 Step S603 in .

[0175] Exemplarily, the transceiver module 1602 is configured to receive a physical uplink shared channel PUSCH, wherein time domain resources of the PUSCH overlap with time domain resources of a PUCCH used for carrying uplink control information.

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

[0177] In one possible implementation, the UCI is carried in a MAC sub-PDU of a MAC PDU, wherein the MAC sub-PDU includes a MAC sub-header and a MAC control element CE, the MAC CE is used to carry the UCI, the MAC sub-header includes a logical channel identifier LCID field and a length field, the LCID field is used to indicate that the type of the MAC CE is UCI, and the length field is used to indicate the size of the MAC CE.

[0178] In a possible implementation, the UCI includes channel state information (CSI) feedback and / or hybrid automatic repeat request (HARQ) feedback information.

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

[0180] In a possible implementation, 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.

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

[0182] In addition, the transceiver module 1602 is used to receive indication information associated with the time-frequency resources 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 resources of the PUSCH or the number of resource elements RE occupied by the UCI in the time-frequency resources of the PUSCH.

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

[0184] In a possible implementation manner, the indication information includes at least one of the following information: indication information of the UCI size, or indication information of the number of REs occupied by the UCI, or an identifier of a device sending the UCI.

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

[0186] In this embodiment, the communication device 160 is presented in the form of various functional modules divided in an integrated manner. Here, "module" can refer to a specific ASIC, circuit, processor and memory that executes one or more software or firmware programs, integrated logic circuit, and / or other devices that can provide the above functions. In a simple embodiment, those skilled in the art can imagine that the communication device 160 can be used. Figure 3 The form of network device 300 is shown.

[0187] for example, Figure 3 The processor 321 in the network device 300 shown can call the computer-executable instructions stored in the memory 322 to enable the network device 300 to execute the method in the above method embodiment.

[0188] Specifically, Figure 16 The function / implementation process of the transceiver module 1602 can be achieved by Figure 3 The processor 321 in the network device 300 shown calls the computer execution instructions stored in the memory 322 to implement. Or, Figure 16 The function / implementation process of the transceiver module 1602 can be achieved by Figure 3 This is implemented by the RF circuit 312 in the network device 300 shown in FIG.

[0189] Since the communication device 160 provided in this embodiment can execute the above method, the technical effects that can be obtained can refer to the above method embodiments and will not be repeated here.

[0190] The embodiment of the present application also provides a communication device, which 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 execution Figure 6 、 Figure 14 The method corresponding to the terminal device or network device.

[0191] The embodiment of the present application also provides a chip, including: a processor and an interface, for calling and running a computer program stored in the memory from the memory, and executing Figure 6 、 Figure 14 The method corresponding to the terminal device or network device.

[0192] The present invention also provides a computer-readable storage medium having instructions stored therein. When the instructions are executed on a computer or a processor, the computer or processor executes Figure 6 、 Figure 14 The method corresponding to the terminal device or network device.

[0193] The present application also provides a computer program product comprising instructions, which, when executed on a computer or processor, causes the computer or processor to execute Figure 6 、 Figure 14 The method corresponding to the terminal device or network device.

[0194] The embodiment of the present application provides a chip system, which includes a processor for executing a communication device. Figure 6 、 Figure 14 The method corresponding to the terminal device or network device.

[0195] In one possible design, the chip system also includes a memory for storing program instructions and data necessary for the terminal device. The chip system may include a chip, an integrated circuit, or a chip and other discrete devices, which are not specifically limited in this embodiment of the application.

[0196] Among them, the communication device, chip, computer storage medium, computer program product or chip system provided in this application are all used to execute the method described above. Therefore, the beneficial effects that can be achieved can refer to the beneficial effects in the implementation methods provided above and will not be repeated here.

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

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

[0199] It should be understood that in the various embodiments of the present application, the size of the serial numbers of the above-mentioned processes does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

[0200] Those skilled in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0201] Those skilled in the art will clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0202] In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are merely schematic. For example, the division of the units is merely a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0203] The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of these units may be selected to achieve the purpose of this embodiment according to actual needs.

[0204] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0205] In the above embodiments, it can 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 whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When loading and executing computer program instructions on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instructions can 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 can be transmitted from a website, computer, server or data center by wired (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (such as infrared, wireless, microwave, etc.) mode to another website, computer, server or data center. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that contains one or more media that can be integrated. The available medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a DVD), or a semiconductor medium (eg, a solid state disk (SSD)).

[0206] The above description is merely a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in this application should be included in the scope of protection of this application. Therefore, the scope of protection of this application should be based on the scope of protection of the claims.

Claims

1. A method for transmitting uplink control information, characterized in that: include: Determining a time domain resource for a 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 a physical uplink control channel (PUCCH) used to carry uplink control information (UCI), transmitting the PUSCH carrying the UCI and uplink data, wherein 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 UCI is carried in a MAC sub-PDU of the MAC PDU, wherein the MAC sub-PDU includes a MAC sub-header and a variable-size MAC control information element (CE). The MAC CE is used to carry the UCI. The MAC sub-header includes a logical channel identifier (LCID) field and a length field. The LCID field is used to indicate that the type of the MAC CE is UCI, and the length field is used to indicate the size of the MAC CE. The UCI includes channel state information CSI feedback and / or hybrid automatic repeat request HARQ feedback information, and the CSI feedback and HARQ feedback information in the UCI are located in different MAC sub-PDUs.

2. The method according to claim 1, characterized in that The MAC CE includes a field indicating the CSI feedback size and / or a field indicating the HARQ feedback information size.

3. The method according to claim 1 or 2, characterized in that The CSI feedback includes a first part and a second part, and the MAC CE includes a field indicating a size of the first part of the CSI feedback and / or a field indicating a size of the second part of the CSI feedback.

4. A method for transmitting uplink control information, characterized in that: include: receiving a physical uplink shared channel (PUSCH), wherein time domain resources of the PUSCH overlap with time domain resources of a PUCCH used to carry uplink control information; Parsing the PUSCH to obtain uplink control information UCI and uplink data, wherein the uplink data and the UCI are multiplexed in the same media access control protocol data unit MAC PDU, the MAC PDU is carried on the PUSCH, and the UCI is carried in a MAC sub-PDU of the MAC PDU, wherein the MAC sub-PDU includes a MAC subheader and a variable-size MAC control information element CE, the MAC CE is 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 type of the MAC CE is UCI, and the length field is used to indicate the size of the MAC CE; The UCI includes channel state information CSI feedback and / or hybrid automatic repeat request HARQ feedback information, and the CSI feedback and HARQ feedback information in the UCI are located in different MAC sub-PDUs.

5. The method according to claim 4, characterized in that The MAC CE includes a field indicating the CSI feedback size and / or a field indicating the HARQ feedback information size.

6. The method according to claim 4 or 5, characterized in that The CSI feedback includes a first part and a second part, and the MAC CE includes a field indicating a size of the first part of the CSI feedback and / or a field indicating a size of the second part of the CSI feedback.

7. A method for transmitting uplink control information, characterized in that: The method comprises: Sending indication information associated with the time-frequency resources of a physical uplink shared channel (PUSCH), where the indication information is used to determine the size of uplink control information (UCI) sent on the time-frequency resources of the PUSCH or the number of resource elements (REs) occupied by the UCI in the time-frequency resources of the PUSCH, where the UCI includes channel state information (CSI) feedback and / or hybrid automatic repeat request (HARQ) feedback information; The UCI and uplink data are sent on the time-frequency resources of the PUSCH, wherein the UCI and the uplink data are carried on the PUSCH, the UCI is mapped to the RE at a predetermined position in the time-frequency resources of the PUSCH, and the uplink data is mapped to the RE at other positions in the time-frequency resources of the PUSCH, wherein the HARQ feedback information is mapped starting from the first PUSCH symbol after the demodulation reference signal DMRS of the PUSCH, and the CSI feedback is mapped starting from the first non-DMRS PUSCH symbol of the PUSCH.

8. The method according to claim 7, characterized in that The method further comprises: It is determined that time domain resources of the PUSCH overlap with time domain resources of a physical uplink control channel PUCCH, wherein the PUCCH is used to carry the UCI and the PUSCH is used to carry the uplink data.

9. The method according to any one of claims 7-8, characterized in that The indication information includes at least one of the following information: indication information of the UCI size, or indication information of the number of REs occupied by the UCI, or an identifier of a device sending the UCI.

10. A method for transmitting uplink control information, characterized in that: The method comprises: receiving indication information associated with a time-frequency resource of a physical uplink shared channel (PUSCH), the indication information being used to determine a size of uplink control information (UCI) sent on the time-frequency resource of the PUSCH or a number of resource elements (REs) occupied by the UCI in the time-frequency resource of the PUSCH, the UCI including channel state information (CSI) feedback and / or hybrid automatic repeat request (HARQ) feedback information; The UCI and uplink data are received on the time-frequency resources of the PUSCH, wherein the UCI and the uplink data are carried on the PUSCH, the UCI is mapped to REs at predetermined positions in the time-frequency resources of the PUSCH, and the uplink data is mapped to REs at other positions in the time-frequency resources of the PUSCH, wherein the HARQ feedback information is mapped starting from the first PUSCH symbol after the demodulation reference signal DMRS of the PUSCH, and the CSI feedback is mapped starting from the first non-DMRS PUSCH symbol of the PUSCH.

11. The method according to claim 10, characterized in that The indication information includes at least one of the following information: indication information of the UCI size, or indication information of the number of REs occupied by the UCI, or an identifier of a device sending the UCI.

12. A communication device, characterized in that: It includes a processing module and a transceiver module, the processing module is used to control the transceiver module to execute the method according to any one of claims 1 to 3, or execute the method according to any one of claims 4 to 6, or execute the method according to any one of claims 7 to 9, or execute the method according to any one of claims 10 to 11.

13. A communication device, characterized in that: The method comprises a processor, a memory, and a transceiver, wherein the processor is coupled to the memory, and when the processor executes the computer program or instructions in the memory, the method according to any one of claims 1 to 3 is performed, or the method according to any one of claims 4 to 6 is performed, or the method according to any one of claims 7 to 9 is performed, or the method according to any one of claims 10 to 11 is performed.

14. A computer-readable storage medium, characterized in that The computer-readable storage medium stores instructions, which, when executed on a computer or a processor, cause the computer or the processor to execute the method according to any one of claims 1 to 3, or the method according to any one of claims 4 to 6, or the method according to any one of claims 7 to 9, or the method according to any one of claims 10 to 11.

15. A computer program product comprising instructions, characterized in that When the instructions are executed on a computer or a processor, the computer or the processor executes the method according to any one of claims 1 to 3, or the method according to any one of claims 4 to 6, or the method according to any one of claims 7 to 9, or the method according to any one of claims 10 to 11.

Images