Apparatus and method for transmitting and receiving control information
By separately encoding and transmitting first-priority and second-priority UCI on the same physical channel using DCI, the method addresses inefficiencies in UCI transmission, enhancing service provision in 5G and IoT networks.
Patent Information
- Application Number
- JP2023507759
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Priority Date
- 2021-05-31
- Filing Date
- 2021-08-02
- Publication Date
- 2025-11-07
- Estimated Expiration
- 2041-08-02
AI Technical Summary
Existing wireless communication systems face challenges in efficiently providing a variety of services, particularly in 5G and IoT networks, due to issues with uplink control information (UCI) transmission and reception, especially when different priority UCI is transmitted on the same physical channel.
A method for separately encoding first-priority and second-priority UCI based on their respective bit numbers and transmitting them on the same physical uplink channel using downlink control information (DCI) or higher layer signaling.
This approach enhances the efficient transmission and reception of UCI, improving the provision of various services in 5G and IoT networks by optimizing the handling of different priority UCI.
Smart Images

Figure 0007766078000168 
Figure 0007766078000169 
Figure 0007766078000170
Abstract
Description
[Technical Field]
[0001] A transmitting method and a receiving method for control information, a user equipment, a base station, and a computer-readable recording medium are provided. The transmission method includes the steps of receiving downlink control information (DCI) from a base station; separately encoding the first priority uplink control information (UCI) and the second priority UCI based on a first bit number of the first priority UCI and a second bit number of the second priority UCI when the first priority UCI and the second priority UCI are transmitted on the same physical uplink channel; and transmitting the encoded first priority UCI and the second priority UCI to the base station on the same physical uplink channel based on the DCI. [Background technology]
[0002] To meet the increased demand for wireless data traffic after the deployment of fourth-generation (4G) communication systems, efforts have been made to develop improved fifth-generation (5G) or pre-5G communication systems. 5G or "Pre-5G" communication systems are also referred to as "beyond 4G networks" or "post-LTE (post long term evolution) systems." 5G communication systems are implemented in higher frequency (mmWave) bands, for example, the 60 GHz band, to achieve even higher data rates. To reduce radio wave propagation loss and extend transmission distance, beamforming, massive MIMO (multiple-input multiple-output), FD-MIMO (full dimensional MIMO), array antennas, analog beamforming, and large-scale antenna techniques are being discussed for 5G communication systems.
[0003] In addition, in the 5G communication system, development is underway to improve the system network based on next-generation small cells, cloud RAN (radio access networks), ultra-dense networks, D2D (device-to-device) communication, wireless backhaul, moving networks, cooperative communication, CoMP (coordinated multi-points), and receiver-end interference cancellation. In 5G systems, hybrid FSK (frequency shift keying), FQAM (Feher's quadrature amplitude modulation), and SWSC (sliding window superposition coding) are developed as advanced coding modulation (ACM), and FBMC (filter bank multi carrier), NOMA (non-orthogonal multiple access), and SCMA (sparse code multiple access) are developed as advanced access technologies.
[0004] The Internet, a human-centric connectivity network where humans generate and consume information, is evolving into the Internet of things (IoT), where distributed entities such as things exchange and process information without human intervention. The Internet of Everything (IoE) has emerged, a combination of IoT technology and big data processing technology via connection to cloud servers. To realize IoT, technological elements such as sensing technology, wired / wireless communication and network infrastructure, service interface technology, and security technology are required, and sensor networks, M2M (machine-to-machine) communication, MTC (machine-type communication), etc. have recently been researched. Such an IoT environment can provide intelligent internet technology services that create new value in human life by collecting and analyzing data generated between connected things. Through the convergence and combination of existing information technology (IT) and various industrial applications, IoT can be applied to a variety of fields, including smart homes, smart buildings, smart cities, smart or connected cars, smart grids, healthcare, smart home appliances, and next-generation medical services.
[0005] Accordingly, various attempts are being made to apply 5G communication systems to IoT networks. For example, technologies such as sensor networks, MTC, and M2M communications are also realized by beamforming, MIMO, and array antennas. The aforementioned application of Cloud RAN as a big data processing technology can also be seen as an example of the convergence of 5G and IoT technologies. As mentioned above, various services are provided by the development of wireless communication systems, and therefore, there is a demand for a method for easily providing such services. Summary of the Invention [Problem to be solved by the invention]
[0006] The present invention has been made in view of the above-mentioned problems in conventional wireless communication systems, and an object of the present invention is to provide a method for easily providing a variety of services in a wireless communication system. [Means for solving the problem]
[0007] According to one aspect of the present invention, a method for transmitting uplink control information (UCI) is provided. The method includes receiving downlink control information (DCI) or higher layer signaling from a base station; separately encoding first-priority uplink control information (UCI) and second-priority UCI based on a first number of bits of the first-priority UCI and a second number of bits of the second-priority UCI when the first-priority UCI and the second-priority UCI are transmitted on the same physical uplink channel; and transmitting the encoded first-priority UCI and the encoded second-priority UCI to the base station on the same physical uplink channel based on the DCI or higher layer signaling. [Brief explanation of the drawings]
[0008] In order to more clearly illustrate the technical scheme of the embodiments of the present invention, the drawings of the embodiments of the present invention will be further briefly introduced below. Obviously, the drawings described below only refer to some embodiments of the present invention and do not limit the present invention. [Figure 1] 1 is an exemplary schematic diagram of a wireless network according to one embodiment of the present invention; [Figure 2A] FIG. 2 illustrates exemplary wireless transmit and receive paths according to one embodiment of the present invention. [Figure 2B] FIG. 2 illustrates exemplary wireless transmit and receive paths according to one embodiment of the present invention. [Figure 3A] 1 is a block diagram illustrating an exemplary schematic configuration of a user equipment (UE) according to an embodiment of the present invention. [Figure 3B] FIG. 1 is a block diagram showing an exemplary schematic configuration of a gNB according to one embodiment of the present invention. [Figure 4] FIG. 2 is a block diagram showing a schematic configuration of a second type of transmitting / receiving node according to an embodiment of the present invention. [Figure 5] 4 is a flowchart illustrating a method performed by a UE according to an embodiment of the present invention. [Figure 6]4 is a flowchart illustrating a method performed by a UE according to an embodiment of the present invention. [Figure 7] FIG. 2 is a block diagram showing a schematic configuration of a first type transmitting / receiving node according to an embodiment of the present invention. [Figure 8] 4 is a flowchart illustrating a method performed by a base station according to an embodiment of the present invention. [Figure 9] 4 is a flowchart illustrating a method performed by a base station according to an embodiment of the present invention. DETAILED DESCRIPTION OF THE INVENTION
[0009] Accordingly, the present invention is provided to address at least the problems and / or disadvantages discussed above, and to provide at least the advantages described below. According to one aspect of the present invention, a method for transmitting uplink control information (UCI) is provided. The method includes receiving downlink control information (DCI) or higher layer signaling from a base station; separately encoding first-priority uplink control information (UCI) and second-priority UCI based on a first number of bits of the first-priority UCI and a second number of bits of the second-priority UCI when the first-priority UCI and the second-priority UCI are transmitted on the same physical uplink channel; and transmitting the encoded first-priority UCI and the encoded second-priority UCI to the base station on the same physical uplink channel based on the DCI or higher layer signaling.
[0010] According to another aspect of the present invention, a method for receiving UCI is provided. The method includes transmitting downlink control information (DCI) or higher layer signaling to a user equipment (UE), and receiving encoded first-priority uplink control information (UCI) and encoded second-priority UCI from the UE on the same physical uplink channel, where the first-priority UCI and the second-priority UCI are encoded based on a first number of bits of the first-priority UCI and a second number of bits of the second-priority UCI when the first-priority UCI and the second-priority UCI are transmitted on the same physical uplink channel.
[0011] According to another aspect of the present invention, a UE is provided. The UE has a transceiver unit and at least one processor, and the processor is configured to receive downlink control information (DCI) or higher layer signaling from a base station, and when a first-priority uplink control information (UCI) and a second-priority UCI are transmitted on the same physical uplink channel, separately encode the first-priority UCI and the second-priority UCI based on a first number of bits of the first-priority UCI and a second number of bits of the second-priority UCI, and transmit the encoded first-priority UCI and the encoded second-priority UCI to the base station on the same physical uplink channel based on the DCI or higher layer signaling.
[0012] According to another aspect of the present invention, a base station is provided. The base station has a transceiver unit and a processor, and the processor is configured to transmit downlink control information (DCI) or higher layer signaling to a user equipment (UE) and to receive encoded first-priority uplink control information (UCI) and encoded second-priority UCI from the UE on the same physical uplink channel. When the first priority UCI and the second priority UCI are transmitted on the same physical uplink channel, the first priority UCI and the second priority UCI are encoded based on the first number of bits of the first priority UCI and the second number of bits of the second priority UCI.
[0013] Various embodiments of the present invention will now be described in detail with reference to the accompanying drawings. In the following description, specific details such as detailed configurations and components are provided only to aid in the overall understanding of these embodiments of the present invention. Therefore, it will be apparent to one of ordinary skill in the art that various changes and modifications to the embodiments described herein may be made without departing from the scope and spirit of the present invention. Furthermore, descriptions of well-known functions and configurations are omitted for the sake of clarity and conciseness.
[0014] As used herein, the term "couple" and its derivatives refer to any direct or indirect communication between two or more elements, regardless of whether those elements are in physical contact with one another. Similar words such as "connect" or "connected" are not limited to physical or mechanical connections, but also include electrical connections, whether direct or indirect. The terms "send," "receive," and "communicate," as well as derivatives thereof, include both direct and indirect communication. The terms "comprise" and "include," as well as derivatives thereof, imply an open-ended inclusion, i.e., a word such as "comprise" or "include" indicates that the element or object appearing before the word includes the sequence of elements or objects appearing after the word, and equivalents thereof, but does not exclude other elements or objects. The term "or" is inclusive, meaning "and / or." The term "related to," as well as derivatives thereof, means including, contained within, connecting to, interconnecting with, containing, contained within, connecting to or with, coupling to or with, communicable with, cooperating with, interleaving with, collocating with, adjacent to, associated with, having, having a characteristic of, relating to or with, and the like. The term "controller" means any device, system, or portion thereof that controls at least one operation. Such a controller may be embodied in hardware or a combination of hardware and software and / or firmware. The functionality associated with any particular control unit may be local or remote, centralized or distributed. The phrase "at least one of," when used in conjunction with a list of items, means that different combinations of one or more of the listed items may be used, and that only one item in the list is required. For example, "at least one of A, B, and C" includes any of the following combinations: A, B, C, A and B, A and C, B and C, A, B, and C.
[0015] Various functions described below may also be embodied or supported by one or more computer programs, each of which is formed from computer-readable program code and embodied in a computer-readable medium. The terms "application" and "program" refer to one or more computer programs, software components, sets of instructions, procedures, functions, objects, classes, instances, associated data, or portions thereof suitable for implementation in suitable computer-readable program code. The term "computer readable program code" includes any type of computer code, including source code, object code, and executable code. The term "computer-readable medium" includes any type of medium that can be accessed by a computer, such as read only memory (ROM), random access memory (RAM), a hard disk drive, a compact disc (CD), a digital video disc (DVD), or any other type of memory. "Non-transitory" computer-readable media excludes wired, wireless, optical, or other communication links that transmit transient electrical or other signals. Non-transitory computer-readable media includes media on which data can be permanently stored and media on which data can be stored and later overwritten, such as rewritable optical disks or erasable memory devices.
[0016] The terms used herein to describe the embodiments of the present invention are not intended to limit and / or define the scope of the present invention. For example, unless otherwise defined, technical or scientific terms used herein should have the ordinary meaning understood by a person of ordinary skill in the art to which this invention belongs. As used herein, terms such as "first," "second," and similar words do not denote any order, quantity, or importance, but are used to distinguish between different components. Unless the context clearly dictates otherwise, the use of the singular forms "a," "an," or "the" and similar words does not denote a limitation of quantity, but rather denotes the presence of at least one. As used herein, any reference to "one example" or "example," "one embodiment," or "embodiment" indicates that a particular element, feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment. The appearances of the phrases "in one embodiment" or "in one example" in different places in the specification do not necessarily refer to the same embodiment. "Top," "bottom," "left," and "right" are used only to indicate relative positional relationships; when the absolute positions of the described objects are changed, the relative positional relationships will also change accordingly.
[0017] The various embodiments discussed below to illustrate the present invention are merely exemplary and should not be construed as limiting the scope of the invention in any way. Those of ordinary skill in the art will appreciate that the present invention may be implemented by any suitably arranged wireless communication system. For example, although the detailed description of the embodiments of the present invention is for LTE and 5G, a person of ordinary skill in the art can understand that the present invention can be applied to other communication systems having similar technical backgrounds and channel formats with minor modifications without departing from the scope of the present invention.
[0018] For example, the communication system may include a global system for a mobile communications (GSM) system, a code division multiple access (CDMA) system, a wideband CDMA (WCDMA) system, a general packet radio service (GPRS), an LTE system, an LTE frequency division duplex (FDD) system, an LTE time division duplex (TDD), a universal mobile telecommunications system (UMTS), a worldwide interoperability for microwave access (WiMAX) communication system, a 5G system, or new radio (NR), etc.
[0019] Furthermore, the technical scheme of the embodiments of the present invention is also applicable to future-oriented communication technologies. Depending on the type of network, terms such as "access point (AP)" and "gNodeB (gNB)" are used instead of "base station." In the present invention, the terms "gNodeB" and "gNB" are used to refer to network infrastructure components that primarily provide wireless access to remote terminals. Similarly, depending on the type of network terminology, such as "mobile station," "user station," "remote terminal," "wireless terminal," or "user equipment" may be used in place of "UE." For example, the terms "terminal" and "UE" are used in the present invention to refer to a remote wireless device that wirelessly accesses a gNB, regardless of whether the UE is a mobile device (e.g., a mobile phone or smartphone) or a fixed device (e.g., a desktop computer or vending machine).
[0020] FIG. 1 is an exemplary schematic diagram of a wireless network according to one embodiment of the present invention. Referring to Figure 1, the wireless network includes gNB101, gNB102, and gNB103.
[0021] gNB101 communicates with gNB102 and gNB103. The gNB 101 also communicates with at least one Internet Protocol (IP) network 130, such as the Internet, a private IP network, or other data network. The gNB 102 provides wireless broadband access to the network 130 to a plurality of first UEs within the coverage area 120 of the gNB 102. The first plurality of UEs include UE 111, which may be located in a small business (SB), UE 112, which may be located in an enterprise (E), UE 113, which may be located in a WiFi hotspot (HS), UE 114, which may be located in a first residence (R), UE 115, which may be located in a second residence (R), and UE 116, which is a mobile device (M) such as a cell phone, a wireless laptop computer, or a wireless personal digital assistant (PDA). The gNB 103 provides wireless broadband access to the network 130 to a plurality of second UEs within the coverage area 125 of the gNB 103. The plurality of second UEs includes UE 115 and UE 116. One or more of the gNBs (101-103) can communicate with each other and with the UEs (111-116) using 5G, LTE, LTE-A, WiMAX, or other advanced wireless communication technologies.
[0022] In FIG. 1, dashed lines indicate the approximate extents of coverage areas 120 and 125, which are shown as approximately circular for purposes of illustration and explanation only. However, coverage areas associated with gNBs, such as coverage areas 120 and 125, may have other shapes, including irregular shapes, depending on the configuration of the gNB and changes in the radio environment associated with natural and man-made obstacles. One or more of the gNBs (101, 102, and 103) also includes a two-dimensional (2D) antenna array. Additionally, one or more of the gNBs (101, 102, and 103) support codebook design and construction for systems with 2D antenna arrays.
[0023] Various modifications may be made to the wireless network shown in FIG. For example, a wireless network may include any number of gNBs and any number of UEs in any suitable arrangement. The gNB 101 can also communicate directly with any number of UEs and provide wireless broadband access to the network 130 for those UEs. Similarly, each of the gNBs (102-103) can communicate directly with the network 130 and provide direct wireless broadband access to the network 130 for the UEs. Additionally, the gNBs (101, 102 and / or 103) provide access to other or further external networks, such as external telephone networks or other types of data networks.
[0024] FIG. 2A illustrates a wireless transmit path according to one embodiment of the present invention, and FIG. 2B illustrates a wireless receive path according to one embodiment of the present invention. 2A and 2B, the transmit path 200 is described as being implemented in a gNB such as gNB 102 of FIG. 1, and the receive path 250 is described as being implemented in a UE such as UE 116 of FIG. 1. However, the receiving path 250 may also be implemented in the gNB, and the transmitting path 200 may also be implemented in the UE. The receive path 250 is configured to support codebook design and construction for systems with 2D antenna arrays.
[0025] The transmit path 200 includes a channel coding and modulation block 205, a serial to parallel (S-to-P) block 210, a size N Inverse Fast Fourier Transform (IFFT) block 215, a parallel to serial (P-to-S) block 220, a cyclic prefix (CP) addition block 225, and an up-converter (UC) 230. The receive path 250 includes a down-converter (DC) 255, a CP removal block 260, an (S-to-P) block 265, a size-N fast Fourier transform (FFT) block 270, a (P-to-S) block 275, and a channel decoding and demodulation block 280.
[0026] In the transmit path 200, a channel coding and modulation block 205 receives a set of information bits, applies coding (e.g., low-density parity check (LDPC) coding), and modulates the input bits (e.g., using Quadrature Phase Shift Keying (QPSK) or QAM) to generate a sequence of frequency-domain modulation symbols. The (S-to-P) block 210 converts (e.g., demodulates) the serially modulated symbols into parallel data to generate N parallel symbol streams, where N is the size of the IFFT / FFT used in the gNB and the UE. The size N IFFT block 215 performs an IFFT operation on the N parallel symbol streams and generates a time-domain output signal. A (P-to-S) block 220 transforms (eg, multiplexes) the parallel time-domain output symbols from the size-N IFFT block 215 to generate a serial time-domain signal. The CP addition block 225 inserts a CP into the time domain signal. The upconverter 230 modulates (ie, upconverts) the output of the CP addition block 225 to a radio frequency (RF) frequency for transmission over a wireless channel.
[0027] The signal may also be baseband filtered before conversion to RF frequency. The RF signal transmitted from the gNB passes through a radio channel before arriving at the UE, and operations that are the reverse of those at the gNB are then performed at the UE. More specifically, downconverter 255 downconverts the received signal to baseband frequency, and CP removal block 260 removes the CP and generates a serial time-domain baseband signal. The (S-to-P) block 265 converts the time-domain baseband signal into a parallel time-domain signal. The size N FFT block 270 performs an FFT algorithm to generate N parallel frequency domain signals. The (P-to-S) block 275 converts the parallel frequency domain signals into a sequence of modulated data symbols. The channel decoding and demodulation block 280 demodulates and then decodes the modulated symbols to recover the original input data stream.
[0028] Each of the gNBs (101 to 103) shown in Figure 1 implements a transmission path 200 for transmission to UEs (111 to 116) in the downlink and implements a reception path 250 for reception from the UEs (111 to 116) in the uplink. Similarly, each of the UEs (111 to 116) implements a transmit path 200 for transmission to the gNBs (101 to 103) on the uplink and a receive path 250 for reception from the gNBs (101 to 103) on the downlink.
[0029] Each of the components in Figures 2A and 2B may be implemented using hardware alone or using a combination of hardware and software / firmware. That is, at least some of the components of FIGS. 2A and 2B are implemented in software, while other components are implemented in configurable hardware or a combination of software and configurable hardware. For example, FFT block 270 and IFFT block 215 may also be implemented as configurable software algorithms where the value of size N is modified depending on the implementation.
[0030] Although FIGS. 2A and 2B are illustrated using FFT and IFFT, this is merely an example and should not be construed as limiting the scope of the present invention. Other types of transforms can be used, such as the discrete Fourier transform (DFT) and inverse discrete Fourier transform (IDFT) functions. For DFT and IDFT functions, the value of the variable N can be any integer (e.g., 1, 2, 3, 4, etc.), while for FFT and IFFT functions, the value of the variable N can be any integer that is a power of 2 (e.g., 1, 2, 4, 8, 16, etc.). Furthermore, various components in Figures 2A and 2B may be combined, further subdivided, or omitted, and additional components may be added depending on particular requirements. Additionally, other suitable architectures may be used to support wireless communications in a wireless network.
[0031] FIG. 3A is a block diagram illustrating an exemplary schematic configuration of a user equipment (UE) according to an embodiment of the present invention. For example, the UE 116 of FIG. 1 is configured as shown in FIG. 3A. Referring to FIG. 3A, the UE includes an antenna 305, an RF transceiver 310, transmit (TX) processing circuitry 315, a microphone 320, and receive (RX) processing circuitry 325. The UE also includes a speaker 330 , a processor / controller 340 , an input / output (I / O) interface 345 , an input device 350 , a display 355 , and a memory 360 .
[0032] Memory 360 includes an operating system (OS) 361 and one or more applications 362 . The RF transceiver unit 310 receives from the antenna 305 incoming RF signals transmitted by gNBs of the wireless network. The RF transceiver 310 downconverts the incoming RF signal to generate an intermediate frequency (IF) signal or a baseband signal. The IF signal or baseband signal is sent to RX processing circuitry 325, where RX processing circuitry 325 generates a processed baseband signal by filtering, decoding and / or digitizing the baseband signal or IF signal.
[0033] RX processing circuitry 325 sends the processed baseband signal to a speaker 330 (eg, for voice data) or to a processor / controller 340 for further processing (eg, for web browsing data). TX processing circuitry 315 receives analog or digital voice data from microphone 320 or other outgoing baseband data (eg, network data, email, or interactive video game data) from processor / controller 340 . TX processing circuitry 315 encodes, multiplexes and / or digitizes outgoing baseband data to generate a processed baseband or IF signal. The RF transceiver 310 receives the processed baseband or IF signals from the TX processing circuitry 315 and upconverts the baseband or IF signals to RF signals that are transmitted via the antenna 305 .
[0034] The processor / controller 340 includes one or more processors or other processing devices and executes an OS 361 stored in memory 360 to control the overall operation of the UE. For example, processor / controller 340 controls the RX of forward channel signals and the TX of reverse channel signals via RF transceiver 310, RX processing circuitry 325, and TX processing circuitry 315 according to well-known principles. Processor / controller 340 may include at least one microprocessor or microcontroller. The processor / controller 340 also executes other processes and programs resident in the memory 360, such as operations for channel quality measurement and reporting for systems with 2D antenna arrays. Processor / controller 340 moves data into and out of memory 360 as required by executing processes.
[0035] The processor / controller 340 executes the application 362 based on the OS 361 or in response to a signal received from the gNB or operator. The processor / controller 340 is coupled to an I / O interface 345, which provides the UE with the ability to connect to other devices, such as laptop computers and handheld computers. The I / O interface 345 is a communication path between these accessories and the processor / controller 340 . The processor / controller 340 is coupled to an input device 350 and a display 355 . An operator of the UE can use input device 350 to input data into the UE. Display 355 is a liquid crystal display (LCD) or other display capable of presenting text and / or at least limited graphics (eg, from a website). The memory 360 is coupled to the processor / controller 340 . A portion of memory 360 includes RAM, while another portion of memory 360 includes flash memory or other ROM.
[0036] Also, various modifications may be made to the UE shown in FIG. 3A. For example, various components of FIG. 3A may be combined, further subdivided, or omitted, and additional components may be added depending on particular requirements. For example, processor / controller 340 may be divided into multiple processors, such as one or more central processing units (CPUs) and one or more graphics processing units (GPUs). Additionally, although FIG. 3A illustrates the UE being configured as a mobile phone or smartphone, the UE may also be configured to operate as other types of mobile or fixed devices.
[0037] FIG. 3B is a block diagram illustrating an exemplary schematic configuration of a gNB according to one embodiment of the present invention. For example, the gNB 102 in FIG. 1 is configured as shown in FIG. 3B. Referring to FIG. 3B, the gNB includes antennas (370a to 370n), RF transceiver units (372a to 372n), a TX processing circuit 374, and an RX processing circuit 376. One or more of the antennas (370a-370n) includes a 2D antenna array. The gNB also includes a controller / processor 378, memory 380, and a backhaul or network interface 382.
[0038] The RF transceivers (372a to 372n) receive incoming RF signals, such as signals transmitted by UEs or other gNBs, from the respective antennas (370a to 370n). The RF transceivers (372a to 372n) down-convert incoming RF signals to generate IF signals or baseband signals. The IF signal or baseband signal is sent to the RX processing circuitry 376, which generates a processed baseband signal by filtering, decoding, and / or digitizing the baseband signal or IF signal.
[0039] The RX processing circuitry 376 sends the processed baseband signal to a controller / processor 378 for further processing. The TX processing circuitry 374 receives analog or digital data (eg, voice data, network data, email, or interactive video game data) from the controller / processor 378 . TX processing circuitry 374 encodes, multiplexes, and / or digitizes the outgoing baseband data to generate a processed baseband or IF signal. The RF transceiver units (372a to 372n) receive the processed baseband signals or IF signals output from the TX processing circuit 374 and upconvert the baseband signals or IF signals to RF signals that are transmitted via the antennas (370a to 370n).
[0040] The controller / processor 378 may include one or more processors or other processing devices that control the overall operation of the gNB. For example, controller / processor 378 controls the RX of forward channel signals and the TX of reverse channel signals via RF transceivers (372a-372n), RX processing circuitry 376, and TX processing circuitry 374 according to well-known principles. The controller / processor 378 also supports additional functionality such as higher level wireless communication functions. For example, the controller / processor 378 may perform a blind interference sensing (BIS) process, such as a process performed via a BIS algorithm, to decode the received signal from which the interfering signal has been subtracted. The controller / processor 378 may support any of a variety of other functions in the gNB. The controller / processor 378 may include at least one microprocessor or microcontroller.
[0041] The controller / processor 378 also executes programs and other processes resident in the memory 380, such as an operating system. The controller / processor 378 also supports channel quality measurement and reporting for systems with 2D antenna arrays. The controller / processor 378 facilitates communication between entities such as the Web Radio TC Controller (RTC). The controller / processor 378 moves data into and out of memory 380 as required by the executing processes.
[0042] The controller / processor 378 is coupled to a backhaul or network interface 382 . The backhaul or network interface 382 allows the gNB to communicate with other devices or systems over a backhaul connection or over a network. Backhaul or network interface 382 facilitates communication over any suitable wired or wireless connection. For example, when the gNB is embodied as part of a cellular communication system, such as a cellular communication system supporting 5G, NR, LTE, or LTE-A, the backhaul or network interface 382 allows the gNB to communicate with other gNBs via a wired or wireless backhaul connection. When the gNB is embodied as an AP, the backhaul or network interface 382 allows the gNB to communicate via a wired or wireless local area network, or with a larger network such as the Internet via a wired or wireless connection. The backhaul or network interface 382 includes any suitable structure that supports communication over wired or wireless connections, such as an Ethernet or RF transceiver.
[0043] The memory 380 is coupled to the controller / processor 378 . A portion of memory 380 includes RAM, while another portion of memory 380 includes flash memory or other ROM. Multiple instructions, such as the BIS algorithm, are stored in memory. The instructions configure the controller / processor 378 to perform a BIS process and decode the received signal after subtracting at least one interfering signal determined by the BIS algorithm.
[0044] As described in more detail below, the TX and RX paths of the gNB (implemented using RF transceivers (372a-372n), TX processing circuitry 374, and / or RX processing circuitry 376) support aggregated communication of FDD and TDD cells. Also, various modifications can be made to the gNB shown in FIG. 3B. For example, a gNB may include any number of each of the components shown in FIG. 3A. More specifically, an AP may include multiple backhaul or network interfaces 382, and the controller / processor 378 may support routing functions to route data between different network addresses. Additionally, although shown as including a single TX processing circuit 374 and a single RX processing circuit 376, the gNB may also include multiple RX and TX processing circuits (e.g., one for each RF transceiver unit).
[0045] Those of ordinary skill in the art will understand that the terms "terminal" and "terminal device" as used herein include devices with radio signal receivers without transmit capabilities, as well as devices with receiving and transmitting hardware capable of bidirectional communication over a bidirectional communication link. Such devices may include cellular or other communication devices with single-line or multi-line displays or without multi-line displays, personal communications services (PCS) that may combine voice, data processing, fax, and / or data communication capabilities, PDAs that include RF receivers, pagers, Internet / intranet access, web browsers, notepads, calendars, and / or global positioning system (GPS) receivers, laptop and / or palmtop computers or other devices that have and / or include RF receivers.
[0046] A "terminal" and "terminal device" as used herein may be portable, transportable, mounted on a vehicle (airborne, seaborne and / or land-based), or suitable and / or configured to operate in a localized and / or distributed manner, or at any other location on the ground and / or in space. Furthermore, the terms "terminal" and "terminal device" as used in the present invention also refer to a communication terminal, an Internet terminal, a music / video playing terminal, such as a PDA, a mobile Internet device (MID) with music / video playing function and / or a mobile phone, a smart TV, a set-top box, etc.
[0047] To support more flexible scheduling, the 3rd Generation Partnership Project (3GPP) has decided to support variable hybrid automatic repeat request (HARQ)-acknowledgement (ACK) feedback delay in 5G. In existing LTE systems, the time from downlink data RX to uplink TX of HARQ-ACK is fixed. For example, in an FDD system, the delay is four subframes. In a TDD system, the HARQ-ACK feedback delay is determined for that downlink subframe by the uplink and downlink configuration.
[0048] In a 5G system, whether it is an FDD system or a TDD system, the uplink time unit in which HARQ-ACK can be fed back is variable relative to a determined downlink time unit (e.g., a downlink slot or a downlink minislot). For example, the HARQ-ACK feedback delay may be dynamically dictated by physical layer signaling, or different HARQ-ACK delays may also be determined by factors such as different services or user capabilities.
[0049] 3GPP has defined three directions of 5G application scenarios: enhanced mobile broadband (eMBB), massive MTC (mMTC), and ultra-reliable and low-latency communication (URLLC). The eMBB scenario is intended to further improve data transmission rates, enhance user experience, and pursue improved communication experience between people based on the existing mobile broadband service scenario. Although mMTC and URLLC are application scenarios for IoT, their respective emphases are different. mMTC is primarily intended for information interaction between people and things, while URLLC is primarily intended to reflect communication requirements between things.
[0050] In 5G, eMBB and URLLC adopt a joint networking scheme in which both URLLC and eMBB services are supported in the same cell. Compared with URLLC-only networking, eMBB and URLLC joint networking can improve the spectral efficiency of the system because URLLC service is a sparse service. When there is a URLLC service in the system, it is preferable to schedule the URLLC service, and when there is no URLLC service in the system or the resources occupied by the URLLC service are low, the eMBB service is scheduled. Currently, when there is a collision between a URLLC service and an eMBB service, the data and / or control information of the URLLC service is transmitted preferentially, thus degrading the performance of the eMBB service. Therefore, how to optimize the transmission of data and control information for eMBB services is an urgent problem that needs to be solved.
[0051] To solve the above-mentioned problems, the following provides a method for transmitting a signal in a wireless communication system, a method for receiving a signal in a wireless communication system, and a terminal, a base station, and a non-transitory computer-readable recording medium for performing these methods. In the present invention, the first type of transmitting and receiving node is a base station (or a gNB), and the second type of transmitting and receiving node is a UE. However, the first type transmitting / receiving node and the second type transmitting / receiving node are not limited to these specific examples.
[0052] FIG. 4 is a block diagram showing a schematic configuration of a second type of transmitting / receiving node according to an embodiment of the present invention. Referring to FIG. 4, the second type transmitting / receiving node 400 includes a transmitting / receiving unit 401 and a control unit 402 . The transceiver unit 401 is configured to receive a first type of data and / or a first type of control signal from a first type of transceiver node, and to transmit a second type of data and / or a second type of control signal to the first type of transceiver node in a determined time unit.
[0053] The controller 402 includes an application specific integrated circuit (ASIC) or at least one processor. The control unit 402 is configured to control the overall operation of the second type transmitting / receiving node and to control the second type transmitting / receiving node to implement at least one of the methods of the present invention. For example, the control unit 402 is configured to determine, based on the first type of data and / or the first type of control signal, the second type of data and / or the second type of control signal and a time unit for transmitting the second type of data and / or the second type of control signal, and to control the transceiver unit 401 to transmit the second type of data and / or the second type of control signal to the first type of transceiver node in the determined time unit.
[0054] The first type of data is data transmitted by a first type of transmitting / receiving node to a second type of transmitting / receiving node. In the following example, downlink data carried by a physical downlink shared channel (hereinafter referred to as PDSCH) is taken as an example (but not limited thereto) to illustrate the first type of data. Similarly, the second type of data is data transmitted by a second type of transmitting / receiving node to a first type of transmitting / receiving node. In the following example, uplink data carried by a physical uplink shared channel (hereinafter PUSCH) is taken as an example (but not limited thereto) to illustrate the second type of data.
[0055] The first type of control signal is a control signal transmitted by a first type of transmitting / receiving node to a second type of transmitting / receiving node. In the following example, a downlink control signal is taken as an example (but not limited thereto) to illustrate the first type of control signal. The downlink control signals include downlink control information (hereinafter referred to as DCI) carried by a physical downlink control channel (hereinafter referred to as PDCCH) and / or control signals carried by a PDSCH. The second type control signal is a control signal transmitted by a second type transmitting / receiving node to a first type transmitting / receiving node. In the following example, an uplink control signal is taken as an example (but not limited thereto) to illustrate the second type of control signal.
[0056] The uplink control signal may also include uplink control information (hereinafter referred to as UCI) carried by a physical uplink control channel (hereinafter referred to as PUCCH) and / or control signal carried by a PUSCH. One type of UCI may include HARQ-ACK information, a scheduling request (SR), a link recovery request (LRR), and channel state information (CSI).
[0057] The first type of time unit is a time unit in which the first type of transmitting / receiving node transmits the first type of data and / or the first type of control signal. In the following example, the downlink time unit is taken as an example (but not limited to) to illustrate the first type of time unit. Similarly, the second type of time unit is a time unit in which a second type of transmitting / receiving node transmits second type of data and / or second type of control signaling. In the following example, an uplink time unit is taken as an example (but not limited to) to illustrate the second type of time unit. The first type of time unit and the second type of time unit may be one or more slots, one or more sub-slots, one or more orthogonal frequency division multiplexing (OFDM) symbols, or one or more sub-frames.
[0058] Depending on the network type, the term "base station" may refer to any component (or collection of components) configured to provide wireless access to a network, such as a Transmission Point (TP), Transmit / Receive Point (TRP), enhanced base station (eNodeB or eNB), 5G base station (gNB), macrocell, femtocell, WiFi AP, or other wireless-enabled device. The base station can provide wireless access via one or more wireless communication protocols, such as 5G 3GPP NR interface / access, LTE, LTE-A (LTE advanced), HSPA (high speed packet access), Wi-Fi 802.11a / b / g / n / ac, etc. Also, depending on the network type, the term "user equipment" may refer to any component such as a "mobile station," "subscriber station," "remote terminal," "wireless terminal," "receiving point," "user device," or simply "terminal." For convenience, the terms "user equipment" and "UE" are primarily used in this invention to refer to a remote wireless device that wirelessly accesses a base station, regardless of whether the UE is a mobile device (e.g., a mobile phone or smartphone) or a fixed device (e.g., a desktop computer or vending machine).
[0059] FIG. 5 is a flowchart illustrating a method performed by a UE according to an embodiment of the present invention. Referring to FIG. 5, in step S510, the UE receives downlink data and / or downlink control signaling from the base station. In step S520, the UE determines, based on the downlink data and / or downlink control signaling, uplink data and / or uplink control signals and uplink time units and / or uplink physical channels on which the uplink data and / or uplink control signals are transmitted. In step S530, the UE transmits uplink data and / or uplink control signals to the base station in the determined uplink time unit.
[0060] The UE sets two levels of priority for uplink TX. For example, the first priority is higher than the second priority. However, embodiments of the present invention are not so limited, and a UE may be configured with more than two levels of priority. In the following description of the embodiment, it is assumed that the first priority is higher than the second priority.
[0061] The two levels of priority are also indicated by a priority number or priority index (eg, priority index 1 and priority index 0). A larger priority index corresponds to a higher priority, ie, the priority corresponding to priority index 1 is higher than the priority corresponding to priority index 0. In this case, a larger priority index (e.g., priority index 1) is a higher priority (e.g., first priority), and a smaller priority index (e.g., priority index 0) is a lower priority (e.g., second priority).
[0062] However, embodiments of the present invention are not so limited, and different priority indexes or indicators can be used to indicate the two levels of priority. In the following description, a priority corresponding to a higher priority index (eg, priority index 1) is higher than a priority corresponding to a lower priority index (eg, priority index 0). Additionally, priority index 1 is used interchangeably with first priority, a larger priority index, or a higher priority, and priority index 0 is used interchangeably with second priority, a smaller priority index, or a lower priority.
[0063] The two levels of priority set for the UE are also two physical layer priorities. For example, one of two levels of priority (priority index 1 or priority index 0) is provided for PUSCH or PUCCH. Specifically, the PUSCH or "PUCCH TX" (including repeated TX, if any) is of priority index 0 or a higher priority index (e.g., priority index 1) (e.g., corresponds to priority index 1). For the configured grant "PUSCH TX", the UE determines the priority index according to the priority parameter (if configured). If the HARQ-ACK information is a "PUCCH TX" corresponding to a semi-persistent scheduling (SPS) "PDSCH RX" or "SPS PDSCH" release, the UE determines the priority index of the "PUCCH TX" from the HARQ-CodebookID parameter (if configured). If a priority index is not configured for a particular PUSCH or "PUCCH TX" of a UE, the priority index of the PUSCH or "PUCCH TX" is "0".
[0064] If the UE monitors the PDCCH to detect DCI format (0_2) and DCI format (1_2) in the active downlink (DL) bandwidth part (BWP), or to detect DCI format (0_1) and DCI format (1_1), the priority index is also provided by the priority indicator field. If the UE indicates that it is capable of monitoring the active "PDCCH in DL BWP" to detect DCI format (0_1) and DCI format (1_1), as well as DCI format (0_2) and DCI format (1_2), DCI format (0_1) or DCI format (0_2) can schedule "PUSCH TX" with any priority, and DCI format (1_1) or DCI format (1_2) schedules "PDSCH RX" and triggers "PUCCH TX" of the corresponding HARQ-ACK information with any priority.
[0065] The UE is configured with a PUCCH configuration list, and the PUCCH configuration list includes two PUCCH configurations, including a first PUCCH configuration and a second PUCCH configuration. For example, the first PUCCH configuration corresponds to the second priority (eg, priority index 0). Similarly, the second PUCCH configuration corresponds to the first priority (eg, priority index 1). The sub-slot configuration length of each of the first PUCCH configuration and the second PUCCH configuration is 7 OFDM symbols or 2 OFDM symbols. The sub-slot configuration lengths of different PUCCH configurations are set differently.
[0066] The UE sets "pdsch-HARQ-ACK-CodebookList". For example, "pdsch-HARQ-ACK-CodebookList" includes two "pdsch-HARQ-ACK-Codebook" settings, including "first HARQ-ACK codebook" and "second HARQ-ACK codebook". For example, a "first HARQ-ACK codebook" is associated with a PUCCH having a smaller priority index (e.g., priority index 0), and a "second HARQ-ACK codebook" is associated with a PUCCH having a larger priority index (e.g., priority index 1). In this case, the priority of the "first HARQ-ACK codebook" is the second priority (e.g., a smaller priority index), and the priority of the "second HARQ-ACK codebook" is the first priority (e.g., a larger priority index). The first priority or a higher priority (e.g., priority index 1) corresponds to the first service (e.g., URLLC service), and the second priority or a lower priority (e.g., priority index 0) corresponds to the second service (e.g., eMBB service).
[0067] When multiple UCIs with different priorities are multiplexed in the same PUCCH or "PUSCH TX," how to determine the physical resources occupied by UCIs with each priority and how to map UCI information to physical resources for TX are problems to be solved. For example, a clear question is whether multiple UCIs with different priorities are encoded (e.g., channel coded) separately, and in such a scenario, multiple UCIs with different priorities would be encoded separately.
[0068] According to one embodiment of the present invention, when multiple UCIs are encoded separately, each UCI of the multiple UCIs is encoded separately. However, when multiple UCIs are jointly encoded, the multiple UCIs are encoded as a whole. At least one of the following approaches (approach (a-1) to approach (a-4)) is adopted to determine whether multiple UCIs with different priorities are encoded separately. Different UCI types with the same priority may be jointly encoded, or different UCI types with the same priority may be separately encoded.
[0069] For example, different UCI types with the same priority are jointly encoded when transmitted on the PUCCH. More specifically, the HARQ-ACK with a higher priority and the SR with a higher priority are jointly encoded. As another example, different UCI types with the same priority may be encoded separately when transmitted on the PUSCH. More specifically, the HARQ-ACK with higher priority, the part 1 CSI with higher priority, and the part 2 CSI with higher priority are encoded separately.
[0070] Approach (a-1): Semi-statically configure whether multiple UCIs with different priorities are encoded separately by higher layer signaling. The higher layer signaling includes radio resource control (RRC) signaling and / or media access control (MAC) signaling. For example, the UE may be notified or instructed by the base station via higher layer signaling that multiple UCIs with different priorities are to be encoded separately.
[0071] Approach (a-2): Dynamically indicate whether multiple UCIs with different priorities are encoded separately by physical layer signaling. For example, the UE may be notified or instructed by the base station via physical layer signaling that multiple UCIs with different priorities are encoded separately.
[0072] Approach (a-3): Determine whether multiple UCIs with different priorities are encoded separately via capabilities reported by the UE. For example, the UE may report to the base station the maximum number (or maximum number of times) A0 to be separately encoded on the PUCCH, where A0 is a positive integer. For example, A0 is equal to 1, 2, 3, or 4. Based on the maximum number A0 reported by the UE, the base station determines whether to support the UE in separately encoding multiple UCIs with different priority indexes in the PUCCH, and based on the determination, instructs the UE whether multiple UCIs with different priorities are to be separately encoded.
[0073] The UE reports to the base station via the PUCCH whether it supports separate encoding of multiple UCIs with different priority indexes. Based on the report by the UE, the base station determines whether the UE supports separate encoding of multiple UCIs having different priority indexes in the PUCCH, and based on the determination, instructs the UE whether multiple UCIs having different priorities are to be separately encoded.
[0074] Approaches (a-1) to (a-3) individually configure / instruct / report UE capabilities for PUSCH / PUCCHs with different priorities, or approaches (a-1) to (a-3) collectively configure / instruct / report UE capabilities for PUSCH / PUCCHs with different priorities. Approaches (a-1) to (a-3) configure / instruct / report UE capabilities separately for semi-statically configured PUSCHs and dynamically scheduled PUSCHs, or approaches (a-1) to (a-3) configure / instruct / report UE capabilities uniformly for semi-statically configured PUSCHs and dynamically scheduled PUSCHs. Approaches (a-1) to (a-3) configure / instruct / report UE capabilities individually for semi-statically configured PUCCHs and dynamically scheduled PUCCHs, or approaches (a-1) to (a-3) configure / instruct / report UE capabilities collectively for semi-statically configured PUCCHs and dynamically scheduled PUCCHs.
[0075] Approach (a-4): Determine whether multiple UCIs with different priorities are encoded separately according to a predefined rule. For example, the UE determines that multiple UCIs with different priorities are to be encoded separately according to a predefined rule. By making UE behavior more explicit based on predefined rules, incorrect scheduling is eliminated and the complexity of UE implementation is reduced. The predefined rules also include at least one of the following rules (b-1) to (b-7).
[0076] Rule (b-1): Whether the multiple UCIs are encoded separately is determined based on the priority of the PUCCH or PUSCH carrying the multiple UCIs with different priorities. The priority of the PUCCH or PUSCH is a priority index. For example, multiple UCIs with different priorities are determined to be encoded separately in one of the following cases: The priority index of a PUCCH or PUSCH carrying multiple UCIs is "1", or the priority index of a PUCCH or PUSCH carrying multiple UCIs is "0". The priority of the PUCCH is also the priority of the PUCCH resource. For example, if a UE configures a PUCCH configuration list including two PUCCH configurations (a first PUCCH configuration and a second PUCCH configuration), the priority index of the PUCCH resource in the first PUCCH configuration is "0", and the priority index of the PUCCH resource in the second PUCCH configuration is "1". As another example, if a UE configures a "First SPS-PUCCH-AN-List" and a "Second SPS-PUCCH-AN-List", the priority index of the PUCCH resource in the "First SPS-PUCCH-AN-List" is "0", and the priority index of the PUCCH resource in the "Second SPS-PUCCH-AN-List" is "1". The priority (eg, priority index) of the PUSCH is also the priority (eg, priority index) of the uplink data.
[0077] Rule (b-2): Whether multiple UCIs are encoded separately is determined according to the code rate and the number of physical resources of multiple UCIs with different priorities. For example, the physical resource includes resource elements (RE) and / or resource blocks (RB). The number of REs and / or RBs is also counted by the code rate of the UCI with higher priority and the total number of bits of the UCI. For example, when the counted number of REs and / or RBs exceeds the number of REs and / or RBs available for PUCCH and / or PUSCH, multiple UCIs with different priorities are determined to be encoded separately. The sum of the number of REs and / or the sum of the number of RBs is also counted by the code rate of UCIs with each priority and the number of bits of UCIs with each priority. For example, when the counted sum of the number of REs and / or the number of RBs does not exceed the number of REs and / or RBs available for the PUCCH and / or PUSCH, multiple UCIs with different priorities are determined to be encoded separately. When the counted sum of the number of REs and / or the number of RBs exceeds the number of REs and / or RBs available for PUCCH and / or PUSCH, only UCI with a higher priority is transmitted without transmitting UCI with a lower priority.
[0078] Rule (b-3): Whether or not the multiple UCIs are encoded separately is determined depending on the number of bits of at least one UCI among the multiple UCIs having different priorities. Depending on the ratio between the number of bits of UCIs with different priorities, multiple UCIs with different priorities are determined to be encoded separately. For convenience of explanation, two UCIs (first UCI and second UCI) are taken as examples for the following illustration, where the first UCI is of a higher priority (e.g., priority index 1) corresponding to a first service (e.g., URLLC service) and the second UCI is of a lower priority (e.g., priority index 0) corresponding to a second service (e.g., eMBB service).
[0079] In one of the following cases, multiple UCIs with different priorities are determined to be encoded separately: The number of bits of the first UCI (e.g., having a higher priority index (e.g., priority index 1)) divided by the number of bits of the second UCI (e.g., having a lower priority index (e.g., priority index 0)) is equal to or greater than N1; The number of bits in the first UCI divided by the number of bits in the second UCI is equal to or less than N2, The number of bits in the UCI with the smaller priority index divided by the number of bits in the UCI with the larger priority index is equal to or greater than N3, or The number of bits of a UCI with a smaller priority index divided by the number of bits of a UCI with a larger priority index is equal to or less than N4. N1, N2, N3, and N4 are real numbers greater than 0. N1, N2, N3, and N4 may be specified by a technical specification or configured by higher layer signaling, for example.
[0080] Whether multiple UCIs are encoded separately also depends on the number of bits of one UCI among multiple UCIs with different priorities. For example, multiple UCIs with different priorities are determined to be encoded separately in one of the following cases: The number of bits of the UCI with a higher priority (for example, priority index 1) is M1 or more, The number of bits in the UCI with higher priority is M2 or less, The number of bits in the UCI with an even lower priority (e.g., priority index 0) is equal to or greater than M3, or The number of bits in the UCI with even lower priority is M4 or less. M1, M2, M3, and M4 are integers greater than 0. M1, M2, M3, and M4 may be specified by a technical specification or configured by higher layer signaling, for example.
[0081] Whether multiple UCIs are encoded separately also depends on the number of bits of one UCI among multiple UCIs with different priorities. For example, multiple UCIs with different priorities are determined to be encoded separately in one of the following cases: The number of bits of a UCI having a lower priority (e.g., priority index 0) is M4 or less, and the number of bits of a UCI having a higher priority (e.g., priority index 1) is M1 or more; The number of bits of a UCI with a lower priority is M4 or less, and the number of bits of a UCI with a higher priority is M2 or less, The number of bits of the UCI with the lower priority is M3 or more, and the number of bits of the UCI with the higher priority is M1 or more, or The number of bits of the UCI with the lower priority is M3 or more, and the number of bits of the UCI with the higher priority is M2 or less. As previously mentioned, M1, M2, M3, and M4 are integers greater than zero. M1, M2, M3, and M4 may be specified by a technical specification or configured by higher layer signaling, for example.
[0082] Rule (b-4): Determine whether multiple UCIs are encoded separately based on the coding type adopted according to the number of bits of at least one UCI among multiple UCIs having different priorities. For example, when the number of bits of each UCI among multiple UCIs having different priorities is greater than 2 and less than or equal to 11, i.e., when Reed-Muller (RM) coding is adopted, the multiple UCIs are determined to be encoded separately. When the number of bits of a UCI having a lower priority (for example, priority index 0) among the multiple UCIs is greater than 2 and less than or equal to 11, the multiple UCIs are determined to be encoded separately. When the number of bits of a UCI having a higher priority (for example, priority index 1) among the multiple UCIs is greater than 2 and less than or equal to 11, the multiple UCIs are determined to be encoded separately. When the number of bits of each UCI among multiple UCIs having different priorities is greater than 11, the multiple UCIs are determined to be encoded separately. According to the above embodiment, the performance of "UCI TX" is further optimized by determining whether to adopt different encodings for different coding types.
[0083] Rule (b-5): Whether or not multiple UCIs are encoded separately is determined depending on the number of cyclic redundancy check (CRC) bits corresponding to multiple UCIs with different priorities. Assume that when a UCI with a lower priority (e.g., priority index 0) is encoded separately, the number of CRC bits is Q1, when a UCI with a higher priority (e.g., priority index 1) is encoded separately, the CRC is Q2, and when a UCI with a lower priority and a UCI with a higher priority are encoded together, the CRC is Q3. Q1, Q2, and Q3 are non-negative integers. For example, when Q3 is greater than Q1 and / or Q3 is greater than Q2, multiple UCIs with different priorities are identified to be encoded separately. As another example, when "Q1+Q2-Q3" is greater than or equal to R1, multiple UCIs with different priorities are identified to be encoded separately. As another example, when "Q1+Q2-Q3" is less than or equal to R2, multiple UCIs with different priorities are identified to be encoded separately. R1 and R2 are non-negative integers. The values of R1 and R2 are either specified by a technical specification or set by higher layer signaling. According to the above embodiment, by determining whether to adopt different encoding depending on the number of CRC bits, the total number of CRC bits is reduced and the spectral efficiency is improved.
[0084] Rule (b-6): Whether multiple UCIs with different priorities are encoded separately is determined according to the HARQ-ACK codebook type. For example, the HARQ-ACK codebook type configured for the UE may include a quasi-static codebook (e.g., a "Type-1" codebook in technical specification "3GPP TS 38.213") or a dynamic codebook (e.g., a "Type-2" codebook in technical specification "3GPP TS 38.213"). It is determined whether multiple UCIs with different priorities are encoded separately depending on the HARQ-ACK codebook type configured for the UE. For example, it is determined whether multiple UCIs with different priorities are encoded separately in one of the following cases: The HARQ-ACK codebook type of the first HARQ-ACK codebook (e.g., having a smaller priority index (e.g., priority index 0)) is a quasi-static codebook, or The HARQ-ACK codebook type of the first HARQ-ACK codebook is a dynamic codebook.
[0085] Rule (b-7): For multiple UCIs with different priorities, whether the multiple UCIs are encoded separately is determined depending on whether the maximum code rate of one UCI among the multiple UCIs is set in the PUCCH resource corresponding to the priority of another UCI among the multiple UCIs. For example, when the maximum code rate of a UCI with a lower priority (e.g., priority index 0) is set on a PUCCH resource with a higher priority (e.g., priority index 1), the multiple UCIs are determined to be encoded separately. As another example, when the maximum code rate of a UCI with a higher priority is set with a PUCCH resource with a lower priority, the UCIs are determined to be encoded separately.
[0086] According to the above-described embodiments of the present invention, various approaches are provided for determining whether UCIs with different priorities are encoded separately, including determining according to at least one of a plurality of predefined rules (rules (b-1) to (b-7)). By adopting specific methods for determining whether UCI is encoded differently in different scenarios, the flexibility of network scheduling is improved while ensuring the reliability of high priority service TX, and the spectrum utilization rate is improved.
[0087] In one embodiment, UCIs having different priorities are described as being encoded separately, but a person skilled in the art may also determine that UCIs having different priorities are not encoded separately according to the various embodiments described above. For example, when the conditions described in at least one of the rules (b-1) to (b-7) are not met, UCIs with different priorities are determined not to be encoded separately. According to an embodiment of the present invention, if it is determined that UCIs with different priorities are not to be encoded separately, the UCIs with different priorities are jointly encoded, or only the UCI with a higher priority is transmitted, and the UCI with a lower priority is dropped (or ignored or not transmitted), or the UCI with a lower priority (e.g., a HARQ-ACK with a lower priority) is compressed / bundled, and the compressed / bundled UCI is jointly encoded with the UCI with a higher priority.
[0088] Alternatively, depending on the conditions described in at least one of rules (b-1) to (b-7), it is determined that a UCI with a lower priority (e.g., a HARQ-ACK with a lower priority) is compressed / bundled, and the compressed / bundled UCI is jointly encoded with a UCI with a higher priority. For example, "determining that multiple UCIs having different priorities are to be encoded separately" includes or is replaced by "determining that UCIs having lower priorities (e.g., HARQ-ACKs having lower priorities) are to be compressed / bundled, and that the compressed / bundled UCIs are to be jointly encoded with UCIs having higher priorities."
[0089] Alternatively, it may be determined that only UCI with a higher priority is transmitted, and UCI with a lower priority is dropped (or ignored or not transmitted) depending on the conditions set in at least one of rules (b-1) to (b-7). For example, "determining that multiple UCIs having different priorities are to be encoded separately" includes or is replaced by "determining that only UCIs having higher priorities are to be transmitted, and UCIs having lower priorities are to be dropped (or ignored or not transmitted)."
[0090] The above-described embodiments of the present invention may further clarify UE behavior based on predefined rules, eliminate erroneous scheduling, and reduce the complexity of UE implementation. The performance of UCI TX is further optimized by determining whether to adopt different encodings for different coding types according to the above-described embodiment of the present invention. According to the above embodiment of the present invention, whether to adopt different encoding is also determined by the number of CRC bits, which can reduce the total number of CRC bits and improve spectral efficiency.
[0091] Furthermore, when multiple UCIs with different priorities are encoded separately, how to determine the maximum code rate of each UCI among the multiple UCIs is a problem to be solved. Therefore, a method according to one embodiment of the present invention is provided below to determine the maximum code rate for UCIs with respective priorities. In the following description, when using "PUCCH TX", various embodiments of the method for determining the maximum code rate of UCI with each priority are illustrated by taking two levels of priority (e.g., priority index) as an example. However, the embodiments described below are applicable to scenarios with more than two levels of priority index, and the embodiments are applicable to scenarios where "PUSCH TX" is used. In the embodiments described below, the method for determining the maximum code rate of UCIs with respective priorities can be applied to determine the modulation order of UCIs with respective priorities.
[0092] As mentioned above, the UE is configured with a PUCCH configuration list, and the PUCCH configuration list includes two PUCCH configurations, including a first PUCCH configuration and a second PUCCH configuration. The first PUCCH configuration has a lower priority (eg, priority index 0), and the second PUCCH configuration has a higher priority (eg, priority index 1). For each of the first PUCCH configuration and the second PUCCH configuration, the base station sets a maximum PUCCH code rate for each of a plurality of PUCCH formats (for example, PUCCH format 1, PUCCH format 2, PUCCH format 3, and PUCCH format 4). Thus, the multiple PUCCH formats in the first PUCCH configuration are of lower priority, and the multiple PUCCH formats in the second PUCCH configuration are of higher priority.
[0093] At least one of the following approaches (approaches (c-1) to (c-4)) is adopted to determine the maximum code rate of each UCI among the multiple UCIs. Approach (c-1): When multiple UCIs are transmitted in a PUCCH format corresponding to the priority (e.g., priority index) of one UCI among the multiple UCIs, the maximum code rate of the other UCIs is determined for the other UCIs by the maximum code rate set in the PUCCH format corresponding to the priority (e.g., priority index) of the other UCI among the multiple UCIs. For convenience of explanation, two UCIs (first UCI and second UCI) are taken as an example, where the first UCI has a higher priority (e.g., priority index 1) and the second UCI has a lower priority (e.g., priority index 0).
[0094] When the first UCI and the second UCI are transmitted in PUCCH format x in a second PUCCH setting having a higher priority, the maximum code rate of the UCI having a lower priority (e.g., the second UCI) is determined to be the maximum code rate set in PUCCH format x in the first PUCCH setting, and the maximum code rate of the UCI having a higher priority (e.g., the first UCI) is determined to be the maximum code rate set in PUCCH format x in the second PUCCH setting. When a first UCI and a second UCI are transmitted in PUCCH format x in a first PUCCH setting having a lower priority, the maximum code rate of the UCI having a higher priority (e.g., the first UCI) is determined to be the maximum code rate set in PUCCH format x in the second PUCCH setting, and the maximum code rate of the UCI having a lower priority (e.g., the second UCI) is determined to be the maximum code rate set in PUCCH format x in the first PUCCH setting. In PUCCH format x, x is 1, 2, 3, or 4.
[0095] Approach (c-2): When multiple UCIs are transmitted in a PUCCH format corresponding to the priority (e.g., priority index) of one UCI among the multiple UCIs, for other UCIs among the multiple UCIs having different priorities, the maximum code rate of the other UCIs is determined by the maximum code rate set in the PUCCH format corresponding to the priority (e.g., priority index) of one UCI among the multiple UCIs and an offset. For convenience of explanation, two UCIs (i.e., a first UCI and a second UCI) are taken as an example, where the first UCI has a higher priority (e.g., priority index 1) and the second UCI has a lower priority (e.g., priority index 0).
[0096] The base station sets an offset for each different PUCCH format, or sets the same offset for each different PUCCH format. When the first UCI and the second UCI are transmitted in a PUCCH format x having a higher priority (e.g., priority index 1), the maximum code rate of a UCI (e.g., the second UCI) having a lower priority (e.g., priority index 0) is determined by adding an offset to the maximum code rate set in the PUCCH format x having the higher priority, or by subtracting an offset from the maximum code rate. When the first UCI and the second UCI are transmitted in a PUCCH format x having a lower priority, the maximum code rate of the UCI having a higher priority (e.g., the first UCI) is determined by adding an offset to the maximum code rate set in the PUCCH format x having a lower priority, or by subtracting an offset from the maximum code rate.
[0097] For a specific PUCCH format, the base station may set an offset, or the base station may set offsets for different priorities. For example, the offset is a relative value. When the offset is a relative value, when the first UCI and the second UCI are transmitted in a PUCCH format x having a higher priority, the maximum code rate of the UCI (e.g., the second UCI) having a lower priority (e.g., priority index 0) is determined by multiplying or dividing the maximum code rate set in the PUCCH format x having a higher priority (e.g., priority index 1) by the offset. When the first UCI and the second UCI are transmitted in a PUCCH format x having a lower priority, the maximum code rate of the UCI having a higher priority (e.g., the first UCI) is a value obtained by multiplying or dividing the maximum code rate set in the PUCCH format x having a lower priority by an offset.
[0098] Approach (c-3): For UCIs of multiple UCIs with different priorities, the maximum code rate of the UCI is determined according to other maximum code rate parameters set by the base station for the PUCCH format. For convenience of explanation, the "other maximum code rate" is also referred to as an additional maximum code rate to distinguish it from the maximum code rate (eg, parameter "maxCodeRate") set in the existing PUCCH format. The "maximum additional code rate" set in the PUCCH format is used for UCIs whose priority differs from that of the PUCCH format. The base station may set a different additional maximum code rate parameter for each different PUCCH format, or the base station may set the same additional maximum code rate parameter for each different PUCCH format. For example, the additional maximum code rate parameter is configured for different PUCCH formats in the 3GPP parameter "PUCCH-FormatConfig". As another example, the same additional maximum code rate parameter is configured for different PUCCH formats in the 3GPP parameter "PUCCH-Config".
[0099] For convenience of explanation, the first UCI and the second UCI are taken as an example, where the first UCI has a higher priority (for example, priority index 1) and the second UCI has a lower priority (for example, priority index 0). When the first UCI and the second UCI are transmitted in a PUCCH format x having a higher priority, the maximum code rate of the UCI having a lower priority (e.g., the second UCI) is determined to be the additional maximum code rate set in the PUCCH format x having the higher priority. When the first UCI and the second UCI are transmitted in a PUCCH format x having a lower priority, the maximum code rate of the UCI having a higher priority (e.g., the first UCI) is determined to be the additional maximum code rate set in the PUCCH format x having the lower priority.
[0100] Approach (c-4): When multiple UCIs are transmitted in a PUCCH format corresponding to the priority (e.g., priority index) of one UCI among the multiple UCIs, the maximum code rate of the other UCIs is determined for the other UCIs by the maximum code rate set on the PUCCH resource (e.g., the PUCCH resource carrying the other UCI) corresponding to the priority (e.g., priority index) of the other UCI among the multiple UCIs. For convenience of explanation, the first UCI and the second UCI are taken as an example, where the first UCI has a higher priority (for example, priority index 1) and the second UCI has a lower priority (for example, priority index 0).
[0101] When the first UCI and the second UCI are transmitted in a PUCCH format y with a second PUCCH configuration having a higher priority, the maximum code rate of the UCI having a lower priority (e.g., the second UCI) is determined to be the maximum code rate of the PUCCH resource carrying the UCI having a lower priority (e.g., the second UCI). It is specified that if the PUCCH format z of the PUCCH resource carrying a UCI with a lower priority (e.g., a second UCI) is identical to the PUCCH format y of the PUCCH resource carrying a multiplexed UCI (e.g., a first UCI and a second UCI), the maximum code rate of the UCI with a lower priority (e.g., the second UCI) is determined to be the maximum code rate of the PUCCH resource carrying the UCI with a lower priority (e.g., the second UCI). Otherwise, the maximum code rate of the UCI with a lower priority is determined by the method specified in another embodiment of the present invention. In PUCCH format y, y is 1, 2, 3, or 4. In PUCCH format z, z is 1, 2, 3, or 4.
[0102] According to the above embodiments, various approaches are provided for determining the maximum code rate of UCIs with respective priorities. As described above, the maximum code rate actually used for UCIs with each priority is determined based on the set maximum code rate. Approach (c-1) reuses existing parameter settings and therefore reduces the overhead of higher layer signaling. Approach (c-2) and approach (c-3) clarify the maximum code rate when UCIs with respective priorities are multiplexed by further parameter settings, which increases the flexibility of scheduling and improves the reliability of "UCI TX". Approach (c-4) provides a method for determining the maximum code rate of one UCI among multiple UCIs when the multiple UCIs are transmitted in a PUCCH format corresponding to the priority of other UCIs among the multiple UCIs. This approach allows the UE to conveniently determine the maximum code rate for carrying other UCI, thereby reducing the overhead of higher layer signaling and ensuring the reliability of "UCI TX" with lower priority.
[0103] If a PUCCH resource or a PUCCH format is configured with two maximum code rate parameters (including an additional maximum code rate parameter and a maximum code rate (e.g., parameter "maxCodeRate") set in an existing PUCCH format) (or if an additional maximum code rate parameter is configured), the maximum code rates corresponding to UCIs with different priorities are determined by approach (c-3). Otherwise, if the PUCCH resource or PUCCH format is not configured with two maximum code rate parameters (or if no additional maximum code rate parameters are configured, for example, only the maximum code rate (e.g., parameter "maxCodeRate") is configured in the existing PUCCH format), the maximum code rates corresponding to UCIs with different priorities are determined by approach (c-1) and / or approach (c-2). For example, the UCI is a HARQ-ACK.
[0104] If the modulation order of the PUCCH resource or PUCCH format with the first priority is different from the modulation order of the PUCCH resource or PUCCH format with the second priority, the maximum code rate of the second UCI transmitted in the PUCCH resource or PUCCH format with the first priority is the maximum code rate obtained by multiplying or dividing the maximum code rate of the PUCCH resource or PUCCH format with the second priority by a parameter. The parameter is a fixed value, for example 2, 1, or 0.5. This parameter is obtained by dividing the modulation order of the PUCCH resource or PUCCH format with the second priority by the modulation order of the PUCCH resource or PUCCH format with the first priority. This parameter is obtained by dividing the modulation order of the PUCCH resource or PUCCH format with the first priority by the modulation order of the PUCCH resource or PUCCH format with the second priority. Furthermore, the parameters are set by higher layer signaling or specified by a protocol.
[0105] If the modulation orders of the PUCCH with the first priority and the PUCCH with the second priority that overlap in the time domain are different, the UE is specified by the protocol as transmitting the PUCCH with the first priority and not transmitting the PUCCH with the second priority. Alternatively, the protocol may specify that the UE does not expect the modulation orders of two PUCCHs with different priorities to overlap in the time domain as being different. The protocol specifies that the UE does not expect the modulation orders of two PUCCHs carrying HARQ-ACKs with different priorities to overlap in the time domain as being different. If the protocol specifies that HARQ-ACKs with different priorities are multiplexed in one PUCCH, the UE does not expect the modulation orders of the same PUCCH formats with different priorities to be different.
[0106] Among the PUCCHs with a first priority and a second priority that overlap in the time domain, if the PUCCH format with the first priority is PUCCH format x, and if the modulation orders of the PUCCH formats x with different priorities are different, the UE is specified by the protocol as transmitting the PUCCH with the first priority and not transmitting the PUCCH with the second priority. The modulation orders of UCIs that are separately encoded on one PUCCH are specified by the protocol as being different. The UE determines the RE to which each UCI is mapped based on the modulation order and maximum code rate of each UCI.
[0107] A method according to one embodiment of the present invention specifies an approach for determining whether to multiplex UCIs with different priorities and the maximum code rates of UCIs with different priorities when the modulation orders of PUCCHs with different priorities are different. The frequency spectrum efficiency of PUCCH resources is improved, system performance is improved, UE behavior is clearer, and network reliability is improved.
[0108] When multiple UCIs with different priorities are jointly encoded, the number of physical resource blocks (PRBs) for "PUCCH TX" is determined by the method of technical specification "3GPP TS 38.213", and then RE mapping is performed by the method of technical specification "3GPP TS 38.212". When multiple UCIs with different priorities are encoded separately, after determining the maximum code rates of the UCIs with different priorities, the number of PRBs for 'PUCCH TX' and the mode for RE mapping still need to be determined.
[0109] According to one embodiment of the present invention, when multiple UCIs are encoded separately, each of the multiple UCIs is encoded separately. However, when multiple UCIs are jointly encoded, the multiple UCIs are encoded as a whole. Alternatively, only UCIs with higher priority are transmitted, and UCIs with lower priority are dropped (or ignored or not transmitted). UCI with a lower priority (e.g., HARQ-ACK with a lower priority) is compressed / bundled, and the compressed / bundled UCI is jointly encoded with UCI with a higher priority.
[0110] An example of the number of PRBs and the mode for RE mapping for "PUCCH TX" when multiple UCIs with different priorities are encoded separately is described in the following approaches (d-1) and (d-2).
[0111] Approach (d-1): Determine the number of PRBs for each UCI based on multiple UCIs, each having a different priority (e.g., priority index) and corresponding maximum code rate, and perform RE mapping based on at least one determined number of PRBs for each UCI. The number of PRBs is determined first (for example, by the method of technical specification "3GPP TS 38.213"), and then RE mapping is performed (for example, by the method of technical specification "3GPP TS 38.212"). The total number of PRBs is the sum of the number of PRBs of UCIs with each priority. Two UCIs (ie, a first UCI and a second UCI) and both UCI types, which are HARQ-ACK, are taken as examples. In this case, the UCI includes first HARQ-ACK information (e.g., having a high priority (e.g., priority index 1)) and second HARQ-ACK information (e.g., having an even lower priority (e.g., priority index 0)).
[0112] When PUCCH format 2 or PUCCH format 3 is used, the UE determines the number of PRBs for TX using Equation (1). Determine TIFF0007766078000001.tif13140.
number
[0113] In formula (1), TIFF0007766078000003.tif13140 is the number of bits of the second HARQ-ACK information, TIFF0007766078000004.tif13140 is the number of CRC bits for the second HARQ-ACK information, TIFF0007766078000005.tif13140 is the number of bits of the first HARQ-ACK, TIFF0007766078000006.tif13140 is the number of CRC bits for the first HARQ-ACK, TIFF0007766078000007.tif10130 is the number of PRBs set for PUCCH format 2 or PUCCH format 3, TIFF0007766078000008.tif10130 is the number of PRB subcarriers available for TX in UCI, TIFF0007766078000009.tif10130 is the number of OFDM symbols available for TX in UCI, and Q m is the modulation order, and r 0 is the maximum code rate for the second UCI (second HARQ-ACK information), and r 1 is the maximum code rate for the first UCI (first HARQ-ACK information). symbol TIFF0007766078000010.tif10130 represents the ceiling operator, and min represents taking the minimum value.
[0114] TIFF0007766078000011.tif17130 corresponds to the number of PRBs for TX of the second HARQ-ACK determined based on the number of bits of the second HARQ-ACK information and the corresponding maximum code rate (i.e., the maximum code rate of the second HARQ-ACK information), TIFF0007766078000012.tif21130 corresponds to the number of PRBs for TX of the first HARQ-ACK information, which is determined based on the number of bits of the first HARQ-ACK information and the corresponding maximum code rate (i.e., the maximum code rate of the first HARQ-ACK information).
[0115] For PUCCH format 3, TIFF0007766078000013.tif13146 If it is not the same as TIFF0007766078000014.tif13146, TIFF0007766078000015.tif13146 is It should increase to the nearest value of TIFF0007766078000016.tif13146, where Valid values for TIFF0007766078000017.tif13146 are specified by the protocol and / or set by higher layer signaling (e.g., 3GPP parameter nrofPRBs), and α2, α3, α5 are non-negative integers.
[0116] In the case of PUCCH format 3, the second HARQ-ACK information is TIFF0007766078000018.tif is mapped to 17130 PRBs. The first HARQ-ACK information is TIFF0007766078000019.tif is mapped to 17146 PRBs. Alternatively, the first HARQ-ACK information is TIFF0007766078000020.tif21130 PRBs, and then the second HARQ-ACK information is TIFF0007766078000021.tif2014 is mapped to 6 PRBs.
[0117] For example, the PRB index of the PRB to which the second HARQ-ACK information is mapped is smaller than the PRB index of the PRB to which the first HARQ-ACK information is mapped. As another example, the PRB index of the PRB to which the second HARQ-ACK information is mapped is greater than the PRB index of the PRB to which the first HARQ-ACK information is mapped.
[0118] for example, TIFF0007766078000022.tif20146, the first HARQ-ACK information is TIFF0007766078000023.tif21130 PRBs, and then the second HARQ-ACK information is TIFF0007766078000024.tif is mapped to 17130 PRBs.
[0119] Another example is TIFF0007766078000025.tif20146, the first HARQ-ACK information is TIFF0007766078000026.tif21130 PRBs, and then the second HARQ-ACK information is TIFF0007766078000027.tif2 is mapped to 1146 PRBs.
[0120] When RE mapping is performed, UCIs with higher priority (eg, priority index 1) are preferentially mapped, followed by UCIs with lower priority (eg, priority index 0). The modulation orders of the first UCI and the second UCI are the same in this example. However, if the modulation orders of the first UCI and the second UCI are different, when PUCCH format 2 or PUCCH format 3 is used, the UE may select the number of PRBs for TX. TIFF0007766078000028.tif13140 can be determined as substitutable by formula (1).
[0121]
number
[0122] TIFF0007766078000032.tif16129 corresponds to the number of PRBs for TX of the second HARQ-ACK determined based on the number of bits of the second HARQ-ACK information, the corresponding maximum code rate (i.e., the maximum code rate of the second HARQ-ACK information), and the corresponding modulation order (i.e., the modulation order of the second HARQ-ACK information), TIFF0007766078000033.tif16146 corresponds to the number of PRBs for TX of the first HARQ-ACK, which is determined based on the number of bits of the first HARQ-ACK information, the corresponding maximum code rate (i.e., the maximum code rate of the first HARQ-ACK information), and the corresponding modulation order (i.e., the modulation order of the first HARQ-ACK information).
[0123] For PUCCH format 3, TIFF0007766078000034.tif13146 If it is not the same as TIFF0007766078000035.tif13146, TIFF0007766078000036.tif13146 is It should increase to the nearest value of TIFF0007766078000037.tif13146. for example, Valid values for TIFF0007766078000038.tif13146 are specified by the protocol and / or set by higher layer signaling (e.g., 3GPP parameter nrofPRBs), where α2, α3, α5 are non-negative integers. for example, If TIFF0007766078000039.tif13146 is the same as 7, TIFF0007766078000040.tif13146 is currently 8 It should increase to the nearest value of TIFF0007766078000041.tif13146.
[0124] In the case of PUCCH format 3, the second HARQ-ACK information is TIFF0007766078000042.tif is mapped to 16129 PRBs. The first HARQ-ACK information is TIFF0007766078000043.tif is mapped to 19146 PRBs. Alternatively, the first HARQ-ACK information is TIFF0007766078000044.tif16146 PRBs, and then the second HARQ-ACK information is TIFF0007766078000045.tif is mapped to 19146 PRBs.
[0125] for example, TIFF0007766078000046.tif20140, the first HARQ-ACK information is TIFF0007766078000047.tif16146 PRBs, and then the second HARQ-ACK information is TIFF0007766078000048.tif is mapped to 16129 PRBs.
[0126] Another example is TIFF0007766078000049.tif20140, the first HARQ-ACK information is TIFF0007766078000050.tif is mapped to 16146 PRBs, and then the second HARQ-ACK information is TIFF0007766078000051.tif2 is mapped to 1146 PRBs.
[0127] The number of REs for a UCI with a higher priority is also determined by the PRB start position set in the PUCCH format, the number of OFDM symbols, and the determined number of PRBs for TX of the UCI.
[0128] Approach (d-2): Determine the total number of PRBs for TX of multiple UCIs with different priorities (eg, priority indexes) according to multiple UCIs and corresponding maximum code rates, and perform RE mapping. Two UCIs (ie, a first UCI and a second UCI) and the type of both UCIs being HARQ-ACK are taken as an example. In this case, the UCI includes first HARQ-ACK information (e.g., having a high priority (e.g., priority index 1)) and second HARQ-ACK information (e.g., having an even lower priority (e.g., priority index 0)).
[0129] When PUCCH format 2 or PUCCH format 3 is used, the UE determines the number of PRBs for TX as follows: Determine TIFF0007766078000052.tif13146.
number
[0130] For PUCCH format 3, TIFF0007766078000060.tif13146 If it is not the same as TIFF0007766078000061.tif13146, TIFF0007766078000062.tif13146 is It should increase to the nearest value of TIFF0007766078000063.tif13146. for example, Valid values for TIFF0007766078000064.tif13146 are specified by the protocol and / or set by higher layer signaling (e.g., 3GPP parameter nrofPRBs), where α2, α3, α5 are non-negative integers.
[0131] Rate matching output sequence length E for the second HARQ-ACK 0 Q m , r 0 , TIFF0007766078000065.tif13140 and Determined by TIFF0007766078000066.tif13140, for example, TIFF0007766078000067.tif17146, and the rate matching output sequence length of the first HARQ-ACK is E 1 is E tot -E 0 where E tot is the total rate matching output sequence length.
[0132] Alternatively, the rate matching output sequence length E 1 Q m , r 1 , TIFF0007766078000068.tif13140 and TIFF0007766078000069.tif13140, for example, TIFF0007766078000070.tif17146, and the rate matching output sequence length of the second HARQ-ACK is E 0 is E tot -E 1 is. TIFF0007766078000071.tif13140 is the maximum available number of PRBs for the PUCCH format (for example, the number of PRBs configured for PUCCH format 2 or PUCCH format 3). TIFF0007766078000072.tif10130), the maximum available number of PRB PUCCH formats is used for TX.
[0133] When RE mapping is performed, UCIs with higher priority (eg, priority index 1) are preferentially mapped, followed by UCIs with lower priority (eg, priority index 0). UCIs with higher priority are mapped to REs with higher reliability. For example, UCI with higher priority may be mapped to symbols closer to the demodulation reference signal (DMRS), followed by UCI with lower priority.
[0134] For example, the number of REs to which a lower UCI is mapped is Also determined by TIFF0007766078000073.tif17146. If TIFF0007766078000074.tif17146 is not an integer, a rounding operation is performed. The rounding operation is also a ceiling operation or a flooring operation. Other available REs may then be used to map to UCIs with even higher priorities.
[0135] The modulation orders of the first UCI and the second UCI are the same in this example. If the modulation orders of the first UCI and the second UCI are different, when PUCCH format 2 or PUCCH format 3 is used, the UE determines the number of PRBs for TX. TIFF0007766078000075.tif13140 can be determined as a substitute by the following formula (4).
number
[0136] For PUCCH format 3, TIFF0007766078000077.tif13146 If it is not the same as TIFF0007766078000078.tif13146, TIFF0007766078000079.tif13146 is It should increase to the nearest value of TIFF0007766078000080.tif13146. For example, Valid values for TIFF0007766078000081.tif13146 are specified by the protocol and / or set by higher layer signaling (e.g., 3GPP parameter nrofPRBs), where α2, α3, α5 are non-negative integers.
[0137] Rate matching output sequence length E for the second HARQ-ACK 0 teeth, TIFF0007766078000082.tif11129, r 0 , TIFF0007766078000083.tif13140 and TIFF0007766078000084.tif13140, for example, TIFF0007766078000085.tif16146, and the rate matching output sequence length of the first HARQ-ACK is E 1 is E tot -E 0 where E tot is the total rate matching output sequence length.
[0138] Alternatively, the rate matching output sequence length E 1 teeth, TIFF0007766078000086.tif11129, r 1 , TIFF0007766078000087.tif13140 and TIFF0007766078000088.tif13140, for example, TIFF0007766078000089.tif16146, and the rate matching output sequence length of the second HARQ-ACK is E 0 is E tot -E 1 is. TIFF0007766078000090.tif13146 is the maximum available number of PRBs for the PUCCH format (for example, the number of PRBs configured for PUCCH format 2 or PUCCH format 3). TIFF0007766078000091.tif13146), the maximum available number of PRB PUCCH formats is used for TX.
[0139] In the case of approaches (d-1) and (d-2), when the number of PRBs available for TX of a UCI with a lower priority is less than a threshold, the UCI is not transmitted, or when the code rate for TX of a UCI with a lower priority exceeds a threshold, the UCI is not transmitted. For example, the threshold may be set by higher layer signaling or specified by a technical specification. As another example, the threshold may also be determined by a maximum payload size parameter (eg, the 3GPP parameter maxPayloadSize).
[0140] The threshold may be the maximum payload size parameter in the PUCCH resource set parameter (e.g., the 3GPP parameter "PUCCH-ResourceSet") with the highest index (e.g., the last one in the 3GPP parameter "resourceSetToAddModList") in a PUCCH configuration parameter (e.g., the 3GPP parameter "PUCCH-Config") with a higher priority. The threshold value may be the maximum payload size parameter in the PUCCH resource set parameter (eg, the 3GPP parameter "PUCCH-ResourceSet") with the highest index in the PUCCH configuration parameter (eg, the 3GPP parameter "PUCCH-Config") with an even higher priority. The threshold may be the maximum payload size parameter in the last "SPS PUCCH ACK / NACK" parameter (e.g., 3GPP parameter "SPS-PUCCH-AN") of an "SPS PUCCH ACK / NACK" list parameter (e.g., 3GPP parameter "SPS-PUCCH-AN-List") with an even higher priority. The threshold is set separately for HARQ-ACK for dynamically scheduled PDSCH and for HARQ-ACK for only "SPS PDSCH", or the threshold is set uniformly for HARQ-ACK for dynamically scheduled PDSCH and for HARQ-ACK for only "SPS PDSCH".
[0141] Alternatively, the threshold is valid only for HARQ-ACK for "SPS PDSCH" (which may also be "SPS PDSCH" with a higher priority and / or "SPS PDSCH" with a lower priority), and for HARQ-ACK for dynamically scheduled PDSCH, the base station dynamically instructs via DCI to multiplex / drop the HARQ-ACK. If the "SPS PUCCH ACK / NACK" list parameter (e.g., the 3GPP parameter "SPS-PUCCH-AN-List") is not configured in a PUCCH configuration parameter with a higher priority, it is specified by the protocol and / or configured by higher layer signaling.
[0142] If a PUCCH carrying a HARQ-ACK with a lower priority overlaps only in the time domain with a PUCCH carrying a HARQ-ACK with a higher priority corresponding to "SPS PDSCH", the UE transmits the PUCCH carrying the HARQ-ACK with the higher priority corresponding to "SPS PDSCH" only, and the UE does not transmit the PUCCH carrying the HARQ-ACK with the lower priority. If the total number of bits of the HARQ-ACK is greater than a predetermined number of bits (e.g., 2 bits), the UE transmits a PUCCH carrying a HARQ-ACK with a higher priority corresponding to only the "SPS PDSCH", and the UE does not transmit a PUCCH carrying a HARQ-ACK with a lower priority. If the total number of bits of the HARQ-ACK is equal to a predetermined number of bits (e.g., 2 bits), the UE multiplexes the HARQ-ACK with a higher priority corresponding only to the "SPS PDSCH" and the HARQ-ACK with a lower priority in the PUCCH. For example, the PUCCH is a PUCCH carrying a HARQ-ACK with a higher priority that corresponds only to the "SPS PDSCH". The method can clarify the UE's behavior and improve the reliability of "UCI TX".
[0143] According to the above embodiments of the present invention, various methods are provided for determining the number of PRBs and the mode for RE mapping. In approach (d-1), the number of PRBs is determined and RE mapping is performed for UCIs with different priorities, and an error in the number of bits of a UCI with a lower priority will not affect the determination of the number of PRBs and RE mapping of a UCI with a higher priority. As a result, the reliability of the UCI TX can be improved.
[0144] In approach (d-2), for UCIs with different priorities, the number of PRBs is jointly determined and RE mapping is performed, which reduces the PUCCH resources for TX of UCIs while ensuring TX reliability. Furthermore, the TX reliability of UCIs with high priority may be improved by mapping UCIs with high priority to REs with even higher reliability when performing mapping. When multiple UCIs with different priorities (e.g., physical layer priorities) are multiplexed in one PUCCH format (e.g., PUCCH format 2, PUCCH format 3, or PUCCH format 4) and encoded separately, if the number of bits of one or more UCIs among the multiple UCIs is less than a threshold number (e.g., the threshold number is a value less than or equal to 3 or 2), the number of bits of the one or more UCIs is separately extended to N bits according to a predefined rule. N is an integer equal to or greater than a threshold number (eg, 3).
[0145] The UCI information bits can be expanded to three bits by adding a known bit. For example, the UCI information bits are expanded to three bits by adding a zero ("0") bit at the end. More specifically, "1" is expanded to "100", "0" is expanded to "000", "10" is expanded to "100", "00" is expanded to "000", "01" is expanded to "010", and "11" is expanded to "110". The number of UCI bits is also extended by repetition coding (eg, UCI bits). For example, a 1-bit UCI is expanded to 3 bits by repetition coding. Additionally or alternatively, the 2-bit UCI may be extended to 4 bits by repetition coding. More specifically, "1" is expanded to "111", "0" is expanded to "000", and "01" is expanded to "0101".
[0146] If a priority includes (eg, corresponds to) multiple types of UCI, such as HARQ-ACK and SR, the multiple types of UCI included in the priority are jointly encoded. When multiple types of UCI included in the priority order are jointly encoded, if the total number of bits of the multiple types of UCI included in the priority order is less than or equal to a predetermined or preset threshold number, the total number of bits of the multiple types of UCI included in the priority order is extended to N bits, where N is an integer greater than or equal to the threshold number. For example, when the HARQ-ACK and SR corresponding to a priority (e.g., one of a higher priority or a lower priority) are determined to be jointly encoded and the total number of bits of the HARQ-ACK and SR is less than or equal to a predetermined threshold number, the total number of bits of the HARQ-ACK and SR is extended to N bits by adopting the various exemplary methods described above.
[0147] According to one embodiment of the present invention, when multiple UCIs with different priorities are multiplexed in one PUCCH format and encoded separately, a method for extending UCI bits depending on the number of UCI bits is provided. The method can improve the reliability of "UCI TX", reduce the retransmission probability of downlink data, and improve the spectral efficiency of the system. For example, if one bit "0 / 1" is expanded to three bits "000 / 111" and RM coding (e.g., coding as defined in "3GPP TS 38.212") is adopted, the two encoded codewords will be 32 bits of all "0" and 32 bits of all "1", respectively. In this way, the code distance between the two encoded codewords is maximum, so the performance is best and the TX reliability is improved.
[0148] When multiple UCIs with different priorities (e.g., physical layer priorities) are multiplexed and jointly encoded in one PUCCH, a specific (additional) maximum code rate parameter is set for the jointly encoded UCIs (e.g., HARQ-ACK information with a higher priority and HARQ-ACK information with a lower priority, or HARQ-ACK information with a higher priority, HARQ-ACK information with a lower priority, and SR information with a higher priority). For example, this is configured in the second PUCCH configuration (a PUCCH configuration with a higher priority, for example the "2nd PUCCH-Config" parameter of the 3GPP parameter "PUCCH-ConfigurationList").
[0149] For convenience of explanation, the aforementioned "specific (additional) maximum code rate" is also referred to as a second additional maximum code rate to distinguish it from the maximum code rate set in the existing PUCCH format (e.g., the parameter "maxCodeRate") and the aforementioned additional maximum code rate. In an embodiment of the present invention, a "second additional maximum code rate" or a "second additional maximum code rate parameter" is used for joint coding of UCIs with different priorities.
[0150] The second additional maximum code rate parameter is configured separately for each PUCCH format, for example, it is configured in the 3GPP parameter "PUCCH-FormatConfig". The UE determines the number of PRBs carrying jointly encoded UCI according to a second additional maximum code rate parameter. The number of PRBs for "PUCCH TX" is determined by the method of technical specification "3GPP TS 38.213", and then RE mapping is performed by the method of technical specification "3GPP TS 38.212".
[0151] Also, the second additional maximum code rate parameter is set separately for different numbers of bits (or different coding types). If the number of bits of the jointly encoded UCI is less than or equal to the parameter M1, the second additional maximum code rate parameter of the PUCCH format is set as P1. If the number of bits of the jointly encoded UCI is greater than the parameter M1, the second additional maximum code rate parameter of the PUCCH format is set as P2. M1 is a positive integer, for example, M1 is equal to 11.
[0152] If the jointly encoded UCI is encoded by adopting the RM code, the second additional maximum code rate parameter of the PUCCH format is set as P3. If the jointly encoded UCI is encoded by adopting a polar code, the second additional maximum code rate parameter of the PUCCH format is set as P4, or the second additional maximum code rate parameter is set collectively for different bit numbers (or different coding).
[0153] As another example, if the number of bits of the jointly encoded UCI is less than or equal to parameter M2, the second additional maximum code rate parameter of the PUCCH format is set as P5. If the number of bits of jointly encoded UCI is greater than parameter M2 and less than or equal to parameter M3, the second additional maximum code rate parameter of the PUCCH format is set as P6 if the number of bits of jointly encoded UCI is greater than parameter M3. M2 and M3 are positive integers. For example, M2 is the same as 2, and M3 is the same as 11.
[0154] When multiple UCIs with different priorities (e.g., physical layer priorities) are multiplexed in one PUCCH, joint coding of two or more UCIs is specified by a protocol or configured by higher layer parameters. For example, each of the multiple UCIs may include HARQ-ACK information, SR, or CSI. For example, the CSI may be a CSI with a higher priority and / or a CSI with a lower priority, or the CSI may be a Part 1 CSI or a Part 2 CSI. HARQ-ACK information with lower priority and / or SR with lower priority are jointly encoded with Part 2 CSI. The HARQ-ACK information with higher priority and / or the SR with higher priority are jointly encoded with Part 1 CSI. This method can improve the probability and reliability of "UCI TX" by avoiding dropping UCIs with lower priorities when the number of encoders is limited.
[0155] When multiple UCIs with different priorities are multiplexed on a PUSCH, joint coding of two or more UCIs is specified by a protocol or configured by a higher layer parameter. For example, HARQ-ACK information with a lower priority and HARQ-ACK information with a higher priority are set to be jointly encoded. As another example, HARQ-ACK information with lower priority is jointly encoded with CSI. The CSI may include CSI with a higher priority and / or CSI with a lower priority, or the CSI may include Part 1 CSI (first part CSI) or Part 2 CSI (second part CSI).
[0156] A specific (additional) parameter "betaOffsets" and / or a parameter "α" (or a parameter "scaling") is configured for jointly encoded UCI (e.g., HARQ-ACK information with a higher priority and HARQ-ACK information with a lower priority, or HARQ-ACK information with a lower priority and CSI) by higher layer signaling to determine the number of REs for the jointly encoded UCI. The specific (additional) parameter "betaOffsets" and / or the parameter "alpha" (or the parameter "scaling") are configured in the 3GPP parameter "PUSCH-Config". For example, a specific (additional) parameter "betaOffsets" and / or a parameter "alpha" (or a parameter "scaling") may be set for the jointly encoded UCI.
[0157] A specific (additional) parameter "betaOffsets" and / or a parameter "alpha" (or a parameter "scaling") may be set individually or collectively for PUSCHs with different priorities. A specific (additional) parameter "betaOffsets" and / or parameter "alpha" (parameter "scaling") may be configured for dynamically scheduled and semi-statically configured PUSCHs individually or collectively. For a particular priority, a specific (additional) parameter "betaOffsets" and / or a parameter "alpha" (parameter "scaling") is configured for dynamically scheduled and semi-statically configured PUSCHs individually or collectively. The UE determines the number of REs carrying jointly encoded UCI by a specific (additional) parameter "betaOffsets" and / or a parameter "alpha" (parameter "scaling"). For example, the number of REs carrying jointly encoded UCI is determined by the method of technical specification "3GPP TS 38.213", and then RE mapping is performed by the method of technical specification "3GPP TS 38.212".
[0158] The method of multiplexing UCI into PUSCH is specifically illustrated by taking joint coding of HARQ-ACK information with higher priority and HARQ-ACK information with lower priority as an example. However, this is merely an example, and the method also applies (e.g., after some modifications) to the joint coding of other types of UCIs with different priorities.
[0159] When HARQ-ACK information with higher priority and HARQ-ACK information with lower priority are jointly encoded, the number of HARQ-ACK symbols per layer is O ACK is obtained from the following formulas (5) to (7).
number
number
number
[0160] In formulas (5) to (7), O ACKis the sum of the number of HARQ-ACK information bits with higher priority and the number of HARQ-ACK information bits with lower priority. L ACK is the number of CRC bits, and L ACK O ACK is determined by. For example, L ACK is also determined by the method defined in "3GPP TS 38.212".
[0161] TIFF0007766078000095.tif13146 is a specific (additional) parameter 'betaOffsets' when HARQ-ACK information with higher priority and HARQ-ACK information with lower priority are jointly encoded as described above. C UL-SCH is the number of code blocks in the PUSCH. K r is the size of the rth code block, which is "0" if the block is not transmitted (e.g., the CBG is indicated as being "0" by the Code Block Group TX Information (CBGTI)).
[0162] TIFF0007766078000096.tif13146 is the bandwidth of "PUSCH TX" where the unit is multiple subcarriers. TIFF0007766078000097.tif13146 is the number of subcarriers in OFDM symbol l that carry the phase tracking reference signal (PTRS) on the PUSCH. TIFF0007766078000098.tif13146 is PUSCH is the number of REs available for TX of UCI for OFDM symbol l for TIFF0007766078000099.tif13146, TIFF0007766078000100.tif11146 is the total number of PUSCH OFDM symbols including DMRS OFDM symbols. For any OFDM symbol carrying a DMRS, The file is TIFF0007766078000101.tif11146.
[0163] For any OFDM symbol that does not carry a DMRS, The file is TIFF0007766078000102.tif11146. α is a scaling parameter set by higher layer signaling, for example, α is a specific (additional) parameter “alpha” (parameter “scaling”) when HARQ-ACK information with higher priority and HARQ-ACK information with lower priority are jointly encoded, as described above. I0 is the first OFDM symbol after the first DMRS symbol on the PUSCH that does not carry DMRS on the PUSCH. It should be noted that TIFF0007766078000103.tif11146 is either the number of symbols in the nominal repetition of TX or the number of symbols in the actual repetition of TX.
[0164] Whether or not HARQ-ACK information with lower priority is jointly encoded with HARQ-ACK information or CSI with higher priority is also determined by the reported capabilities of the UE and / or higher layer signaling configuration. For example, the UE may report the maximum number of distinct encodings supported on the PUSCH. As another example, the UE may report whether it supports joint coding of HARQ-ACK information with a lower priority and HARQ-ACK information or CSI with a higher priority.
[0165] When RE mapping of UCI is performed on PUSCH, the mapping priority and mapping order of UCI must be defined. For example, when HARQ-ACK information with a lower priority and Part 1 CSI are jointly encoded, the mapping priority and mapping order may ultimately be HARQ-ACK with a higher priority, HARQ-ACK information with a lower priority, both Part 1 CSI, and Part 2 CSI. When HARQ-ACK information with a lower priority and Part 2 CSI are jointly encoded, the mapping priority and mapping order may ultimately be HARQ-ACK information with a higher priority, Part 1 CSI, HARQ-ACK information with a lower priority, and both Part 2 CSI. If the number of REs is limited, UCIs with higher priorities are preferentially mapped (or transmitted) according to the mapping priority, and UCIs with lower priorities are not mapped (or transmitted).
[0166] If the specific (additional) parameter "betaOffsets" and / or parameter "alpha" (parameter "scaling") are not set, when RE of HARQ-ACK information and Part 1 CSI (or Part 2 CSI) with lower priority is determined, they are also determined by the parameter "betaOffsets" and / or parameter "alpha" (parameter "scaling") of Part 1 CSI (or Part 2 CSI). Some instances of joint coding when UCIs with different priorities are multiplexed have been described above. In these instances, when multiple different UCIs must be encoded using the methods, the number of encoders is reduced, the complexity and cost of the terminal implementation is reduced, the complexity and time of network decoding is reduced, network performance is improved, dropping of UCIs due to a limited number of encoders is avoided, and the reliability and TX probability of UCIs can be improved.
[0167] Furthermore, since PRB / RE is further determined by the set maximum code rate parameter, parameter "betaOffsets" and / or parameter "alpha" (parameter "scaling"), the spectral efficiency of the system may also be improved. Furthermore, when joint coding is adopted, the coding performance is improved and the block error rate (BLER) is reduced due to the longer code length compared to some coding schemes, such as polar coding. By further setting the maximum code rate (e.g., a lower maximum code rate), the physical resources occupied by UCI can be reduced, provided that the reliability of UCI is guaranteed, thereby improving the spectral efficiency of the system.
[0168] When multiple UCIs with different priorities are multiplexed and transmitted on the same PUCCH, how to determine the PUCCH resource for TX is a problem to be solved. According to one embodiment of the present invention, at least one of the following approaches is adopted to solve the problem.
[0169] Approach (e-1): The priority of the PUCCH resource is dynamically indicated in the DCI format, and the PUCCH resource for TX is determined based on the indicated priority. According to the priority of the PUCCH resources indicated by the last DCI format, the PUCCH configuration belonging to the PUCCH resources is determined, and then the PUCCH resources to be used are determined (for example, according to the method of "3GPP TS 38.213"). The set of PUCCHs is determined by the size of the UCI, and then the PUCCH resources in the determined set of PUCCHs are selected by the PUCCH resource indication in the DCI.
[0170] Approach (e-2): The priority of the PUCCH resource is determined by a predefined rule, and the PUCCH resource for TX is determined based on the determined priority. An example of a predefined rule is described below.
[0171] As mentioned above, the number of PRBs (NPRBs) is determined by the number of bits of UCIs with different priorities, the maximum code rate, the number of PRB subcarriers available for TX of UCIs, the number of OFDM symbols available for TX of UCIs, and the modulation order. When the determined number of PRBs (NPRBs) is not greater than the number of PRBs configured in a PUCCH format with a higher priority, the PUCCH resource with a higher priority (for example, priority index 1) is used. When the NPRB is greater than the number of PRBs configured in a PUCCH format with a higher priority, but not greater than the number of PRBs configured in a PUCCH format with a lower priority, the PUCCH resource with the lower priority (e.g., priority index 0) is used. When the NPRB is greater than the number of PRBs configured in a PUCCH format with a higher priority and greater than the number of PRBs configured in a PUCCH format with a lower priority, only the UCI with the higher priority index is transmitted and the PUCCH resource with the higher priority is used.
[0172] Various methods for determining PUCCH resources for TX according to an embodiment of the present invention have been described above. Approach (e-1) has low implementation complexity because the used PUCCH resources can be dynamically indicated through base station scheduling. Approach (e-2) clarifies the conditions for using PUCCH resources with different priorities, and therefore improves the reliability of "UCI TX".
[0173] In an embodiment of the present invention, a method for multiple UCIs with different priorities is applicable to a scenario in which the priority indexes of multiple UCIs are the same, but is also applicable to a scenario in which the types of multiple UCIs are different, the priority indexes of multiple UCIs are different, and the UCI types of multiple UCIs are different. In the above-described embodiment of the present invention, the method for multiplexing multiple UCIs with different priorities is also applicable to multiplexing unicast UCIs and groupcast (or multicast) / broadcast UCIs. In this case, various methods for multiplexing unicast UCI and groupcast / broadcast UCI can be obtained by replacing "multiple UCIs with different priorities" in the above embodiment with "unicast UCI and groupcast / broadcast UCI", or by replacing "multiple UCIs with different priorities" in the above embodiment with "unicast UCI and groupcast / broadcast UCI with the same priority". For the sake of brevity, a detailed description of the alternatives will be omitted.
[0174] According to an embodiment of the present invention, unicast refers to a manner in which a network communicates with one UE, and groupcast / broadcast refers to a manner in which a network communicates with multiple UEs. For example, a unicast PDSCH may also be a PDSCH received by one UE, and the scrambling of the PDSCH may be based on a UE-specific radio network temporary indicator (RNTI), for example, C-RNTI. A groupcast / broadcast PDSCH is also a PDSCH that is received by more than one UE simultaneously, and the scrambling of the PDSCH is based on a UE group-common RNTI, for example, a groupcast / broadcast service (MBS)-RNTI.
[0175] The unicast UCI may include HARQ-ACK information, SR, or CSI of the unicast PDSCH. The groupcast (or multicast) / broadcast UCI may include HARQ-ACK information for the groupcast / broadcast PDSCH. When unicast UCI and groupcast (or multicast) / broadcast UCI are multiplexed and jointly encoded in one PUCCH, a specific (additional) maximum code rate parameter is set for the jointly encoded UCI (e.g., at least one of HARQ-ACK information and Part 2 CSI of the groupcast / broadcast PDSCH, or HARQ-ACK of the groupcast / broadcast PDSCH and HARQ-ACK, SR, and CSI of the unicast PDSCH), and is configured, for example, in the PUCCH configuration (e.g., the 3GPP parameter "PUCCH-Config").
[0176] For convenience of explanation, the "specific (additional) maximum code rate" is also referred to as the third additional maximum code rate in the embodiments of the present invention to distinguish it from the maximum code rate set in the existing PUCCH format (e.g., the parameter "maxCodeRate"), the aforementioned additional maximum code rate, and the second additional maximum code rate. The "third additional maximum code rate" or "third additional maximum code rate parameter" is used for joint coding of unicast UCI and groupcast / broadcast UCI. However, embodiments of the present invention are not limited thereto, and the same parameter may be used to indicate one or more of the additional maximum code rate, the second additional maximum code rate, and the third additional maximum code rate, or different parameters may be used to indicate the additional maximum code rate, the second additional maximum code rate, and the third additional maximum code rate.
[0177] The third additional maximum code rate parameter is configured individually for each PUCCH format, for example in the 3GPP parameter "PUCCH-FormatConfig". The UE determines the number of PRBs carrying jointly encoded UCI according to a third additional maximum code rate parameter. The number of PRBs for "PUCCH TX" is determined by the method of technical specification "3GPP TS 38.213", and then RE mapping is performed by the method of technical specification "3GPP TS 38.212". For the method of multiplexing UCI onto PUSCH, refer to the previous description, and the details will be omitted. Also, the third additional maximum code rate parameter is set individually for different numbers of bits (or different coding). For example, this is set by the setting method in various embodiments of the present invention.
[0178] When unicast UCI and groupcast (or multicast) / broadcast UCI are multiplexed in one PUSCH, joint coding of two or more UCIs (e.g., HARQ-ACK for groupcast / broadcast PDSCH and HARQ-ACK for unicast PDSCH, or HARQ-ACK for groupcast / broadcast PDSCH and CSI) is specified by a protocol or configured by higher layer parameters. The CSI may include CSI with a higher priority and / or CSI with a lower priority, or the CSI may include Part 1 CSI (first part CSI) or Part 2 CSI (second part CSI).
[0179] A specific (additional) parameter "betaOffsets" and / or parameter "alpha" (parameter "scaling") are set for a jointly encoded UCI by higher layer signaling to determine the number of REs for the jointly encoded UCI. The specific (additional) parameter "betaOffsets" and / or the parameter "alpha" (or the parameter "scaling") are configured in the 3GPP parameter "PUSCH-Config". For example, a specific (additional) parameter "betaOffsets" and / or a parameter "alpha" (parameter "scaling") may be set individually or collectively for PUSCHs with different priorities.
[0180] As another example, specific (additional) parameters "betaOffsets" and / or "alpha" (parameter "scaling") may be configured individually or collectively for dynamically scheduled and semi-statically configured PUSCHs. As another example, for a particular priority, a specific (additional) parameter "betaOffsets" and / or a parameter "alpha" (parameter "scaling") may be configured for dynamically scheduled and semi-statically configured PUSCHs individually or collectively. The UE determines the number of REs carrying jointly encoded UCI by a specific (additional) parameter "betaOffsets" and / or a parameter "alpha" (parameter "scaling"). The number of REs carrying the jointly encoded UCI is determined by the method of technical specification "3GPP TS 38.213", and then RE mapping is performed by the method of technical specification "3GPP TS 38.212".
[0181] Whether one or more unicast UCIs are jointly encoded with groupcast / broadcast UCIs is also determined by the capabilities reported by the UE and / or higher layer signaling configuration. For example, the UE may report the maximum number of distinct encodings supported on the PUSCH. As another example, the UE reports whether it supports joint coding of one or more unicast UCIs and groupcast (or multicast) / broadcast UCIs.
[0182] When RE mapping of UCI is performed to PUSCH, the mapping priority and mapping order of UCI must be defined. For example, the mapping priority and mapping order may end up being HARQ-ACK for unicast PDSCH, HARQ-ACK for groupcast / broadcast PDSCH, both part 1 CSI, and part 2 CSI. The mapping priority and mapping order are ultimately HARQ-ACK, Part 1 CSI for unicast PDSCH, and both HARQ-ACK and Part 2 CSI for groupcast / broadcast PDSCH. If the number of REs is limited, UCIs with higher priorities are preferentially mapped (or transmitted) according to the mapping priority, and UCIs with lower priorities are not mapped (or transmitted).
[0183] If the specific (additional) parameter "betaOffsets" and / or parameter "alpha" (parameter "scaling") are not set, when the RE of HARQ-ACK and Part 1 CSI (or Part 2 CSI) of the groupcast / broadcast PDSCH is determined, they are also determined by the parameter "betaOffsets" and / or parameter "alpha" (parameter "scaling") of Part 1 CSI (or Part 2 CSI).
[0184] When unicast UCI and groupcast (or multicast) / broadcast UCI are multiplexed in PUSCH, if the unicast UCI and groupcast (or multicast) / broadcast UCI are encoded separately, the mapping priority and mapping order of UCI must be defined when RE mapping of UCI is performed in PUSCH. For example, the mapping priority and mapping order may ultimately be HARQ-ACK for unicast PDSCH, HARQ-ACK for groupcast / broadcast PDSCH, Part 1 CSI, and Part 2 CSI, or the mapping priority and mapping order may ultimately be HARQ-ACK for unicast PDSCH, Part 1 CSI, HARQ-ACK for groupcast / broadcast PDSCH, and Part 2 CSI.
[0185] Alternatively, the mapping priority and mapping order may end up being HARQ-ACK for unicast PDSCH, Part 1 CSI, Part 2 CSI, and HARQ-ACK for groupcast / broadcast PDSCH. If the number of REs is limited, UCIs with higher priorities are preferentially mapped (or transmitted) according to the mapping priority, and UCIs with lower priorities are not mapped (or transmitted). A specific (additional) parameter "betaOffsets" and / or a parameter "alpha" (parameter "scaling") are set for HARQ-ACK for groupcast / broadcast PDSCH according to the method of another embodiment of the present invention.
[0186] An instance of joint coding was described above when multiple UCIs associated with different PDSCH cast types are multiplexed. In these instances, when multiple UCIs corresponding to different PDSCH cast types (e.g., unicast type, groupcast (or multicast) type) must be coded, the number of encoders is reduced, the complexity and cost of the terminal implementation is reduced, the complexity and time of network decoding is reduced, network performance is improved, UCI dropping due to a limited number of encoders is avoided, and the reliability and TX probability of UCI are improved. Furthermore, since PRB / RE is further determined by the set maximum code rate parameter, parameter "betaOffsets" and / or parameter "alpha" (parameter "scaling"), the spectral efficiency of the system is also improved.
[0187] UCIs with different priorities are multiplexed in a PUCCH (eg, a PUCCH with a higher priority), where the UCIs with different priorities are encoded separately. The PUCCH resource set and / or the PUCCH resource may also be determined by the total number of UCI bits with different priorities and / or a predefined parameter. For example, HARQ-ACKs with different priorities (e.g., a HARQ-ACK with a higher priority is a dynamically scheduled HARQ-ACK) and / or SRs (e.g., an SR with a higher priority) are multiplexed in one PUCCH.
[0188] According to one embodiment, the PUCCH resource set configured for use is the sum of the number of HARQ-ACK bits with different priorities (including at least HARQ-ACKs with higher priorities and HARQ-ACKs with lower priorities), Whether HARQ-ACKs with different priorities are jointly encoded; the number of HARQ-ACK and / or SR bits with higher priority; the number of HARQ-ACK bits with lower priority, The number of HARQ-ACK bits with lower priority is adjusted and determined based on at least one of a code rate (e.g., maximum code rate) of a HARQ-ACK with higher priority and / or a predefined parameter related to a code rate (e.g., maximum code rate) of a HARQ-ACK with lower priority.
[0189] In particular, the PUCCH resource set is determined by adopting the following Approach 1 and / or Approach 2. Approach 1: If the number of HARQ-ACK bits with different priorities is equal to a default value (e.g., 2) and / or if HARQ-ACKs with different priorities are jointly encoded (or if HARQ-ACKs with different priorities are not separately encoded), the determined PUCCH resource set is the first PUCCH resource set (e.g., 3GPP parameter "pucch-ResourceSetId" = 0).
[0190] If the number of HARQ-ACK bits with different priorities is greater than a predetermined value (e.g., 2), and / or if HARQ-ACKs with different priorities are encoded separately (or if HARQ-ACKs with different priorities are not jointly encoded), the PUCCH resource set is determined to be greater than the number of HARQ-ACK and / or SR bits with higher priorities (e.g., parameter O HP ), the number of HARQ-ACK bits with lower priority (e.g., parameter O LP ) and predefined parameters.
[0191] The PUCCH resource set may be further divided into the number of HARQ-ACK and / or SR bits with higher priority (e.g., parameter O HP ) and the number of HARQ-ACK bits with lower priority (e.g., parameter O LP ) by a predefined parameter (e.g., parameter α) The image is determined based on the image size (represented by TIFF0007766078000104.tif11146). for example, TIFF0007766078000105.tif11146 is It is also expressed as TIFF0007766078000106.tif11146.
[0192] If TIFF0007766078000107.tif11146 is less than or equal to N2, the determined PUCCH resource set is the second PUCCH resource set (e.g., 3GPP parameter “pucch-ResourceSetId”=1); If TIFF0007766078000108.tif11146 is greater than N2 and less than or equal to N3, the determined PUCCH resource set is the third PUCCH resource set (e.g., 3GPP parameter “pucch-ResourceSetId”=2); If TIFF0007766078000109.tif11146 is greater than N3 and less than or equal to 1076, the determined PUCCH resource set is the fourth PUCCH resource set (eg, 3GPP parameter "pucch-ResourceSetId"=3).
[0193] Approach 2: The PUCCH resource set is further divided into the number of HARQ-ACK bits with higher priority and / or SR (e.g., parameter O HP ), the number of HARQ-ACK bits with lower priority (e.g., parameter O LP ) and a predefined parameter (for example, represented by the parameter α). The PUCCH resource set is the sum of values obtained by multiplying the number of HARQ-ACK bits with higher priority and / or SR and the number of HARQ-ACK bits with lower priority by a predefined parameter (e.g., parameter The image is determined based on the image size (represented by TIFF0007766078000110.tif11146). for example, TIFF0007766078000111.tif11146 is It is also expressed as TIFF0007766078000112.tif11146.
[0194] If TIFF0007766078000113.tif11146 is less than or equal to a predetermined value (e.g., 2), the determined PUCCH resource set is the first PUCCH resource set (e.g., 3GPP parameter “pucch-ResourceSetId”=0); If TIFF0007766078000114.tif11146 is greater than a predetermined value (e.g., 2) and less than or equal to N2, the determined PUCCH resource set is the second PUCCH resource set (e.g., 3GPP parameter pucch-ResourceSetId=1); If TIFF0007766078000115.tif11146 is greater than N2 and less than or equal to N3, the determined PUCCH resource set is the third PUCCH resource set (e.g., 3GPP parameter “pucch-ResourceSetId”=2); If TIFF0007766078000116.tif11146 is greater than N3 and less than or equal to 1076, the determined PUCCH resource set is the fourth PUCCH resource set (eg, 3GPP parameter "pucch-ResourceSetId"=3).
[0195] The re-determined PUCCH resource set is the second PUCCH resource set (e.g., 3GPP parameter 'pucch-ResourceSetId' = 1) if the determined PUCCH resource set is the first PUCCH resource set, and the sum of the number of HARQ-ACK bits with higher priority and the number of HARQ-ACK bits with lower priority is greater than a default value (e.g., 2), or HARQ-ACKs with different priorities are encoded separately.
[0196] Furthermore, in the approaches 1 and 2, for example, in the above-described embodiment, "PUCCH resource set" is replaced with "PUCCH resource", the parameter "pucch-ResourceSetId" is replaced with the 3GPP parameter "sps-PUCCH-AN-ResourceID", and the parameter N2 is replaced with N 1,SPS and parameter N3 is replaced by N 2,SPS and replace "1076" with N 3,SPS It can be applied to determine the PUCCH resource carrying "SPS PDSCH HARQ-ACK" by replacing it with
[0197] The predefined parameter α may be set by higher layer signaling or may be an offset defined in other embodiments of the present invention. The predefined parameter α is also the ratio between the code rate (e.g., maximum code rate) of a HARQ-ACK with a lower priority and the code rate (e.g., maximum code rate) of a HARQ-ACK and / or SR with a higher priority. Also, "Parameter TIFF0007766078000117.tif11146" is "Parameter The rounding operation can be rounding up, rounding down, or rounding to the nearest integer.
[0198] If a PUCCH resource carrying UCI with different priorities is determined to be PUCCH format 2, it is specified by the protocol and / or configured by higher layer signaling that UCI with lower priorities (e.g., HARQ-ACK) will not be transmitted. Alternatively, the selected PUCCH is used to transmit UCI with higher priority, or the PUCCH resource is re-determined according to the number of UCI bits with higher priority. Parameters N2, N3, N1,SPS , N 2,SPS , or N 3,SPS is set by higher layer signaling. Parameters N2, N3, N 1,SPS , N 2,SPS , or N 3,SPS N2, N3, N 1,SPS , N 2,SPS , or N 3,SPS One or more of the values are the same as predefined values. For example, a predefined value is 1076.
[0199] The method according to the above embodiment of the present invention can determine the PUCCH resource set / PUCCH resource according to the number of UCI bits and predefined parameters related to the code rate. If the PUCCH resource is determined only by the number of UCI bits, this will waste the PUCCH resource, since the code rate of the HARQ-ACK with a lower priority is higher than the code rate of the HARQ-ACK with a higher priority. For example, in the case of PUCCH format 4, the number of PRBs and OFDM symbols is fixed, so the number of PRBs cannot be determined by the number of REs actually required. According to the above method, the PUCCH resource set / PUCCH resource is determined by the number of UCI bits and predefined parameters related to the code rate, so that a more reasonable PUCCH resource can be selected, thereby improving the spectral efficiency of the system.
[0200] UCIs with different priorities are multiplexed in a PUCCH (eg, a PUCCH with a higher priority), where the UCIs with different priorities are encoded separately. The TX power of the PUCCH is determined by the number of HARQ-ACK bits with different priorities for PUCCH power control (e.g., 3GPP parameter n HARQ-ACK(i) and / or O ACK (i)) and / or determined by predefined parameters. The number of HARQ-ACK bits for PUCCH power control (e.g., 3GPP parameter n HARQ-ACK (i) and / or O ACK (i)) is determined based on at least one of the number of HARQ-ACK information bits with higher priority for power control, the number of HARQ-ACK information bits with lower priority for power control, and a predefined parameter. For example, the predefined parameters may be used to adjust the number of HARQ-ACK information bits with a lower priority for power control, and may be related to the code rate (e.g., maximum code rate) of HARQ-ACK information with a higher priority for power control and / or the code rate (e.g., maximum code rate) of HARQ-ACK information with a lower priority for power control.
[0201] If the UE transmits an active “PUCCH on UL BWP b” of carrier f from primary cell c using the PUCCH power control adjustment state with index l, the UE adjusts the “PUCCH TX” power P PUCCH,b,f,c (i,q u ,q d ,l) is determined.
number
[0202] In equation (8), P CMAX,f,c (i) is the configured maximum output power for carrier f of primary cell c at "PUCCH TX" opportunity i. P O_PUCCH,b,f,c (q u ) is the open loop power parameter. For example, this is also determined by the scheme specified in "3GPP TS 38.213". TIFF0007766078000120.tif12146 is the PUCCH TX bandwidth for active “PUCCH TX on UL BWP b” opportunity i on carrier f of primary cell c, in RB. It should be noted that the subcarrier spacing in "BWP b" is μ. PL b,f,c (q d ) is a parameter related to path loss. For example, this is also determined by the scheme specified in "3GPP TS 38.213". Δ F_PUCCH (F) is a parameter related to the PUCCH format. For example, this is also determined by the scheme specified in "3GPP TS 38.213". g b,f,c (i,l) are the closed-loop power parameters. For example, this is also determined by the scheme specified in "3GPP TS 38.213". Δ TF,b,f,c (i) is the PUCCH TX power adjustment parameter for PUCCH TX opportunity i on active UL BWP b of carrier b in primary cell c. In the case of PUCCH format 0 or PUCCH format 1, Δ TF,b,f,c (i) is also determined by the method specified in "3GPP TS 38.213".
[0203] For PUCCH format 2 and / or PUCCH format 3 and / or PUCCH format 4, and for a number of UCI bits (e.g., UCI with higher priority) that is less than or equal to 11, TIFF0007766078000121.tif12146, where: K1=6 n HARQ-ACK (i) is the number of HARQ-ACK information bits for power control.
[0204] n HARQ-ACK (i) is determined based on at least one of the number of HARQ-ACK information bits with higher priority for power control, the number of HARQ-ACK information bits with lower priority for power control, and a predefined parameter. For example, the predefined parameters may be used to adjust the number of HARQ-ACK information bits with a lower priority for power control, and may be related to the code rate (e.g., maximum code rate) of HARQ-ACK information with a higher priority for power control and / or the code rate (e.g., maximum code rate) of HARQ-ACK information with a lower priority for power control. n HARQ-ACK (i) is the sum of values obtained by multiplying the number of HARQ-ACK information bits with higher priority for power control and the number of HARQ-ACK information bits with lower priority for power control by a predefined parameter (e.g., represented by parameter α). The number of HARQ-ACK information bits with a particular priority for power control (e.g., 3GPP parameter n HARQ-ACK (i) and / or O ACK (i)) is also determined by the method specified in "3GPP TS 38.213".
[0205] O SR (i) is the number of SR and / or LRR information bits, e.g., O SR (i) is the number of SR and / or LRR information bits with higher priority index. For example, this may be determined by the scheme specified in section 9.2.5.1 of 3GPP TS 38.213. O CSI (i) is the number of CSI information bits, which may also be determined by the scheme specified in section 9.2.5.2 of 3GPP TS 38.213, for example. For example, the number of CSI information bits with higher priority is "0". OCRC (i) is the number of CRC bits, e.g., O CSI (i) is also the number of CRC bits with lower priority.
[0206] N RE (i) is the number of resource elements (RE) for transmitting UCI. TIFF0007766078000122.tif12146, where: TIFF0007766078000123.tif12146 is the number of subcarriers per resource block excluding subcarriers used for DMRS, TIFF0007766078000124.tif12146 is the number of OFDM symbols excluding the OFDM symbols used for DMRS.
[0207] For PUCCH format 2 and / or PUCCH format 3 and / or PUCCH format 4 and for a number of UCI bits greater than 11 (e.g., UCI with higher priority): TIFF0007766078000125.tif12146, where K2=2.4 BPRE(i)=(O ACK (i)+O SR (i)+O CSI (i)+O CRC (i)) / N RE (i)
[0208] O ACK (i) is a HARQ-ACK information bit for power control. O ACK (i) is determined based on at least one of the number of HARQ-ACK information bits with higher priority for power control, the number of HARQ-ACK information bits with lower priority for power control, and a predefined parameter. For example, the predefined parameters may be used to adjust the number of HARQ-ACK information bits with a lower priority for power control, and may be related to the code rate (e.g., maximum code rate) of HARQ-ACK information with a higher priority for power control and / or the code rate (e.g., maximum code rate) of HARQ-ACK information with a lower priority for power control. O ACK (i) is the sum of values obtained by multiplying the number of HARQ-ACK information bits with higher priority for power control and the number of HARQ-ACK information bits with lower priority for power control by a predefined parameter (e.g., represented by parameter α). The number of HARQ-ACK information bits with a particular priority for power control (e.g., 3GPP parameter n HARQ-ACK (i) and / or O ACK It should be noted that (i)) is also determined by the method specified in "3GPP TS 38.213".
[0209] O SR (i) is the number of SR and / or LRR information bits, e.g., O ACK (i) is the number of SR and / or LRR information bits with higher priority index. For example, this is determined by the method specified in "3GPP TS 38.213 9.2.5.1". O CSI (i) is the number of CSI information bits, which may also be determined by the scheme specified in section 9.2.5.2 of 3GPP TS 38.213, for example. For example, the number of CSI information bits with higher priority is "0". O CRC (i) is the number of CRC bits, e.g., O CSI (i) is also the sum of the number of CRC bits with different priorities.
[0210] N RE(i) is the number of REs for transmitting UCI. TIFF0007766078000126.tif12128, where: TIFF0007766078000127.tif12128 is the number of subcarriers per resource block excluding subcarriers used for DMRS, TIFF0007766078000128.tif12128 is the number of OFDM symbols excluding the OFDM symbols used for DMRS.
[0211] According to an embodiment of the present invention, the predefined parameter α is set by higher layer signaling or is an offset defined in another embodiment of the present invention. Alternatively, the predefined parameter α may also be the ratio between the code rate (e.g., maximum code rate) of a HARQ-ACK with a lower priority and the code rate (e.g., maximum code rate) of a HARQ-ACK and / or SR with a higher priority. The above-described embodiments of the present invention provide a power calculation method for use when multiplexing UCIs with different priority indices into a PUCCH TX. The reliability of the "PUCCH TX" is improved by determining the power via the total UCI. When power is limited, a method is defined to ensure the reliability of UCI with high priority, which can improve the reliability of "UCI TX" with high priority. By setting the parameters, scheduling flexibility is improved and UCI with lower priority can be transmitted as much as possible while still guaranteeing the reliability of "UCI TX" with higher priority.
[0212] FIG. 6 is a flowchart illustrating a method performed by a UE according to an embodiment of the present invention. Referring to FIG. 6, in step S610, the UE determines a first UCI having a first priority and a second UCI having a second priority to be transmitted on the same uplink channel, where the first priority is different from the second priority. For example, the first priority is higher than the second priority. The type of each of the first UCI and the second UCI includes at least one of HARQ-ACK information, SR, LRR, or CSI. The uplink channel includes a PUCCH or a PUSCH.
[0213] In step S620, the UE determines whether the first UCI and the second UCI are encoded separately. Determining whether the first UCI and the second UCI are encoded separately includes at least one of receiving higher layer signaling from the base station indicating whether the first UCI and the second UCI are encoded separately, or receiving physical layer signaling from the base station indicating whether the first UCI and the second UCI are encoded separately. Furthermore, determining whether the first UCI and the second UCI are encoded separately also includes determining whether the first UCI and the second UCI are encoded separately according to a predefined rule.
[0214] The predefined rules may include at least one of the following: determining whether the first UCI and the second UCI are encoded separately according to the priorities of the uplink channels carrying the first UCI and the second UCI; determining whether the first UCI and the second UCI are encoded separately according to a code rate and the number of physical resources of the first UCI and the second UCI; Determining whether the first UCI and the second UCI are encoded separately according to the number of bits of at least one of the first UCI and the second UCI; determining whether the first UCI and the second UCI are encoded separately according to a coding type adopted by at least one of the first UCI and the second UCI; Determining whether the first UCI and the second UCI are encoded separately according to the number of bits of a cyclic redundancy check (CRC) corresponding to each of the first UCI and the second UCI; Determining whether the primary UCI and the secondary UCI are encoded separately according to the HARQ-ACK codebook type; or Determining whether the first UCI and the second UCI are encoded separately depending on whether the maximum code rate corresponding to one of the first priority and the second priority is configured on the PUCCH resource corresponding to the other of the first priority and the second priority. The method for determining whether the first UCI and the second UCI are separately encoded may be described in the various embodiments above, and detailed description thereof will be omitted.
[0215] In step S630, in response to determining that the first UCI and the second UCI are to be encoded separately, the UE encodes the first UCI and the second UCI separately. The method may further include, in response to the UE determining that the first UCI and the second UCI are not separately encoded, jointly coding the first UCI and the second UCI.
[0216] In step S640, the UE transmits the encoded first UCI and second UCI on an uplink channel. The method may further include determining a maximum code rate for the first UCI and the second UCI. For example, the determined maximum code rate is used for at least one of the following: Separate encoding of the first UCI and the second UCI, or Determining the number of PRBs and / or the mode for RE mapping for the first UCI and the second UCI.
[0217] Determining the maximum code rate of the first UCI and the second UCI may include at least one of the following: determining a maximum code rate of the UCI corresponding to the other one of the first priority and the second priority according to a maximum code rate set in a PUCCH format corresponding to the other one of the first priority and the second priority when the first UCI and the second UCI are transmitted in a PUCCH format corresponding to one of the first priority and the second priority; determining a maximum code rate of a UCI corresponding to the other one of the first and second priorities according to a maximum code rate set in the PUCCH format corresponding to one of the first and second priorities and an offset when the first UCI and the second UCI are transmitted in a PUCCH format corresponding to one of the first and second priorities; determining a maximum code rate of the UCI corresponding to one of the first and second priorities according to an additional maximum code rate set in the PUCCH format corresponding to one of the first and second priorities when the first UCI and the second UCI are transmitted in a PUCCH format corresponding to the other of the first and second priorities; or When the first UCI and the second UCI are transmitted in a PUCCH format corresponding to one of the first priority and the second priority, determining a maximum code rate of the UCI corresponding to the other one of the first priority and the second priority according to a maximum code rate set in a PUCCH resource corresponding to the other one of the first priority and the second priority.
[0218] Transmitting the encoded first UCI and second UCI includes determining the number of PRBs and a mode for resource element RE mapping for the first UCI and the second UCI, and transmitting the encoded first UCI and second UCI based on the determined number of PRBs and the mode for RE mapping.
[0219] Determining the number of PRBs for the first UCI and the second UCI may include at least one of the following: respectively determining the number of PRBs of the first UCI and the second UCI according to the first UCI, the second UCI, and the corresponding maximum code rate; and performing RE mapping based on at least one of the determined number of PRBs of the first UCI and the number of PRBs of the second UCI; or Determine the total number of PRBs for the first UCI and the second UCI according to the number of bits of the first UCI and the second UCI and the corresponding maximum code rate, and perform RE mapping.
[0220] When RE mapping is performed, the UCI having a higher priority among the first UCI and the second UCI is mapped first, and then the remaining UCI among the first UCI and the second UCI is mapped. When RE mapping is performed, the UCI having a higher priority among the first UCI and the second UCI is mapped to a symbol closer to the DMRS symbol. The first priority is higher than the second priority. When the determined number of PRBs of the second UCI is less than a predefined or set first threshold, the second UCI is not transmitted, or when the code rate for TX of the second UCI exceeds a predefined or set second threshold, the second UCI is not transmitted.
[0221] The first priority is higher than the second priority, and transmitting the encoded first UCI and second UCI may include determining resources for the uplink channel TX including at least one of the following: receiving, from a base station, downlink control information (DCI) indicating resources for an uplink channel TX; or Determining resources for the uplink channel TX according to predefined rules.
[0222] Determining resources for the uplink channel TX according to a predefined rule may include at least one of the following: determining a number of PRBs for an uplink channel TX, and when the determined number of PRBs is equal to or less than the number of PRBs configured for a PUCCH format corresponding to a first priority, determining to use a PUCCH resource corresponding to a first priority; determining to use the PUCCH resource corresponding to the second priority when the determined number of PRBs is greater than the number of PRBs configured in the PUCCH format corresponding to the first priority and is less than or equal to the number of PRBs configured in the PUCCH format corresponding to the second priority; or When the determined number of PRBs is greater than the number of PRBs set in the PUCCH format corresponding to the first priority and greater than the number of PRBs set in the PUCCH format corresponding to the second priority, determining to use the PUCCH resource corresponding to the first priority to transmit only the first UCI and not the second UCI.
[0223] According to one embodiment of the present invention, a method for transmitting UCI is provided. The method includes the steps of: determining whether a third UCI corresponding to a first cast type of a PDSCH and a fourth UCI corresponding to a second cast type of a PDSCH are to be transmitted on the same uplink channel, wherein the first cast type is different from the second cast type and the third UCI and the fourth UCI are to be encoded separately; separately encoding the third UCI and the fourth UCI in response to determining that the third UCI and the fourth UCI are to be encoded separately; and transmitting the encoded third UCI and the fourth UCI on the uplink channel to a base station.
[0224] The first cast type is unicast, and the second cast type is groupcast. If it is determined that the third UCI and the fourth UCI are not to be encoded separately, the third UCI and the fourth UCI are jointly encoded. A method similar to that described in FIG. 6 may be adopted to determine whether the third UCI and the fourth UCI are encoded separately. For the sake of brevity, a detailed description will be omitted. Also, a method similar to that described in FIG. 6 can be adopted to determine the maximum code rates of the third UCI and the fourth UCI. For the sake of brevity, a detailed description will be omitted. The methods in the various embodiments described above may be adopted to transmit the encoded third UCI and fourth UCI to the base station on an uplink channel.
[0225] FIG. 7 is a block diagram showing a schematic configuration of a first type transmitting / receiving node according to an embodiment of the present invention. Referring to FIG. 7, a first type transmitting / receiving node 700 includes a transmitting / receiving unit 701 and a control unit 702 .
[0226] The transceiver unit 701 is configured to transmit a first type of data and / or a first type of control signal to a second type of transmitting / receiving node in a time unit, and to receive a second type of data and / or a second type of control signal from the second type of transmitting / receiving node. The control unit 702 is an ASIC or at least one processor. The control unit 702 is configured to control the overall operation of the first type transmitting / receiving node, including controlling the transceiver unit 701 to transmit the first type of data and / or the first type of control signal to the second type transmitting / receiving node in the determined time unit and to receive the second type of data and / or the second type of control signal from the second type transmitting / receiving node, wherein the second type of data and / or the second type of control signal and the time unit are determined by the second type transmitting / receiving node based on the received first type of data and / or the first type of control signal.
[0227] As mentioned above, a base station is taken as an example (but is not limited to) to illustrate a first type of transmitting / receiving node, a UE is taken as an example (but is not limited to) to illustrate a second type of transmitting / receiving node, a downlink time unit (but is not limited to) is used to illustrate the first type of time unit, and an uplink time unit (but is not limited to) is used to illustrate the time unit. DL data and / or DL control signaling (but not limited thereto) are used to exemplify a first type of data and / or a first type of control signal. The HARQ-ACK codebook is included in the second type of control signaling, and uplink control signals (including but not limited to) are used to illustrate the second type of control signaling.
[0228] FIG. 8 is a flowchart illustrating a method performed by a base station according to an embodiment of the present invention. Referring to FIG. 8, in step S810, the base station transmits DL data and / or DL control signals to the UE. In step S820, the base station receives a second type of data and / or a second type of control signal from the UE in an uplink time unit, where the second type of data and / or the second type of control signal and the uplink time unit are determined by the UE based on the received DL data and / or DL control signal.
[0229] A person of ordinary skill in the art will understand that the base station can decode the second type of data and / or the second type of control signal based on a method corresponding to the method performed by the UE in the above embodiment.
[0230] FIG. 9 is a flowchart illustrating a method performed by a base station according to an embodiment of the present invention. Referring to FIG. 9, in step S910, a base station receives a first UCI having a first priority and a second UCI having a second priority from a UE on the same uplink channel, where the first priority is different from the second priority, and the first UCI and the second UCI are encoded separately.
[0231] The method may further include transmitting higher layer signaling to the UE indicating that the first UCI and the second UCI are encoded separately. The method may further include transmitting physical layer signaling to the UE indicating that the first UCI and the second UCI are encoded separately. The types of the first UCI and the second UCI each include at least one of HARQ-ACK information, SR, LRR, or CSI. The uplink channel includes a PUCCH or a PUSCH.
[0232] Those of ordinary skill in the art will understand that the above-described exemplary embodiments are intended to illustrate and not limit the present invention. It should be understood that any two or more of the embodiments disclosed herein may be combined in any combination. Additionally, other embodiments may be utilized, and other changes may be made, without departing from the spirit or scope of the inventive subject matter presented herein. It will be readily understood that the aspects of the present invention as generally described herein and illustrated in the drawings can all be arranged, substituted, combined, separated and designed into a wide variety of different configurations contemplated by the present invention.
[0233] Those of ordinary skill in the art will appreciate that the various illustrative logic blocks, modules, circuits, and stages described herein may be embodied as hardware, software, or a combination of both. To clearly illustrate this interchangeability of hardware and software, various illustrative components, blocks, modules, circuits, and steps have been described generally in terms of their functional sets. Whether such a set of functions is implemented as hardware or software depends on the particular application and design constraints imposed on the overall system. Engineers may implement the described feature set in different ways for each particular application, but such design decisions should not be interpreted as causing a departure from the scope of this description.
[0234] According to one embodiment of the present invention, there is further provided a computer-readable recording medium storing one or more computer programs capable of implementing any of the aforementioned methods when the one or more computer programs are executed by one or more processors. The various exemplary logic blocks, modules, and circuits described herein may be embodied or performed by a general purpose processor, a digital signal processor (DSP), an ASIC, a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof, designed to perform the functions described in the present invention. A general purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. A processor may also be embodied as a combination of computing devices such as a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.
[0235] The steps of a method or algorithm described herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. A software module may reside in RAM memory, flash memory, ROM memory, erasable programmable ROM (EPROM) memory, electrically EPROM (EEPROM) memory, registers, hard disk, a removable disk, or any other form of storage medium known in the art. An exemplary storage medium is coupled to the processor such that the processor can read information from, and write information to, the storage medium.
[0236] In the alternative, the storage medium may be integral to the processor. The processor and the storage medium may reside in an ASIC. The ASIC may reside in a user terminal. In the alternative, the processor and the storage medium may reside as discrete components in a user terminal. In one or more exemplary designs, the functions may be embodied in hardware, software, firmware, or any combination thereof. If embodied in software, the respective functions may be stored on or transmitted over as one or more pieces of instructions or code on a computer-readable medium. Computer-readable media includes both computer storage media and communication media, the latter including any medium that facilitates transfer of a computer program from one place to another. A storage medium may be any available medium that can be accessed by a general purpose or special purpose computer.
[0237] Although the present invention has been particularly shown and described with reference to specific embodiments, it will be understood by those of ordinary skill in the art that various changes in form and details may be made therein without departing from the spirit and scope of the invention as defined by the appended claims and their equivalents. [Explanation of symbols]
[0238] 101~103 gNB 111~116UE 120, 125 coverage area 130 Network 305, 370a~370n antennas 310, 372a to 372n RF transceiver units 315, 374 Transmit (TX) processing circuit 320 microphone 325, 376 Receive (RX) processing circuit 330 Speaker 340, 378 Processor / Control Unit 345 Input / Output (I / O) Interface 350 input devices 355 Display 360, 380 memory 361 Operating System (OS) 362 Applications 382 Backhaul or Network Interface 400, 700 (Type 2, Type 1) sending and receiving nodes 401, 701 Transmitter / Receiver 402, 702 control section
Claims
1. 1. A method for a user equipment (UE) in a wireless communication system, comprising: receiving information from a base station (BS) including parameters related to a maximum code rate; Here, the parameters related to the maximum code rate are set for PUCCH (physical uplink control channel) format 2 and PUCCH format 3, respectively; receiving information from the base station, the information including parameters related to an additional maximum code rate; Here, the parameters related to the additional maximum code rate are set for each of the PUCCH format 2 and the PUCCH format 3, determining a first maximum code rate of a first uplink control information (UCI) having a first priority and a second maximum code rate of a second UCI having a second priority based on (i) a PUCCH format corresponding to the PUCCH format 2 or the PUCCH format 3, (ii) a maximum code rate set for the PUCCH format, and (iii) an additional maximum code rate set for the PUCCH format; For the PUCCH format, the minimum number of PRBs (PRBs) 【number】 ) determining where: 【number】 = [Equation 3] is determined based on Here, in equation (3), r 0 is the maximum code rate of the second UCI, r 1 is the maximum code rate of the first UCI, 【number】 is the number of bits of the second UCI, 【number】 is the number of CRC (Cyclic Redundancy Check) bits for the second UCI, 【number】 is the number of bits of the first UCI, 【number】 is the number of CRC bits for the first UCI, 【number】 is the number of subcarriers, 【number】 is the number of Orthogonal Frequency Division Multiplexing (OFDM) symbols, Q m is the modulation order; and transmitting the first UCI having a first priority and the second UCI having a second priority to the base station via one PUCCH using the PUCCH format based on the minimum number of PRBs for the PUCCH format.
2. A step of receiving, from the base station, a PUCCH configuration list including a first PUCCH configuration having a second priority and a second PUCCH configuration having a first priority; determining the first maximum code rate of the first UCI having the first priority from among the maximum code rates associated with the second PUCCH configuration having the first priority if the PUCCH format is included in the second PUCCH configuration; and determining the second maximum code rate of the second UCI having the second priority from among the additional maximum code rates associated with the second PUCCH configuration having the first priority.
3. The method of the user device described in claim 1, further comprising a step of separately encoding the first UCI having the first priority and the second UCI having the second priority.
4. A method for a user device as described in Claim 3, characterized in that the number of bits of the first UCI, which is the first priority, is greater than a default value, or the number of bits of the second UCI, which is the second priority, is greater than a default value.
5. A step of jointly encoding the third UCI and the fourth UCI; wherein the third UCI and the fourth UCI are of different types and have equal priorities; 4. The method of claim 3, further comprising: transmitting the third UCI and the fourth UCI via one PUCCH.
6. The PUCCH format is PUCCH format 3, and the minimum number of PRBs of the PUCCH format is If it is not the same as where: is a non-negative positive number, The minimum number of PRBs in the PUCCH format 2. The method of claim 1, further comprising increasing the value of the user device to a value closest to .
7. The method of claim 1, further comprising a step of transmitting the PUCCH using the maximum available number of PRBs of the PUCCH format if the minimum number of PRBs of the PUCCH format is greater than the maximum available number of PRBs of the PUCCH format. determining a first rate matching output sequence length of the first UCI based on the first maximum code rate of the first UCI; 2. The method of claim 1, further comprising determining a second rate matching sequence length of the second UCI based on the first rate matching output sequence length of the first UCI.
9. A user equipment (UE) in a wireless communication system, comprising: a transmitter / receiver; at least one processor coupled to the transceiver; one or more memories communicatively coupled to the at least one processor; the one or more memories store instructions to be executed by the at least one processor, either alone or in combination; The command word is: The user device: receiving information from a base station (BS) including parameters related to a maximum code rate; Here, the parameters related to the maximum code rate are set for PUCCH (physical uplink control channel) format 2 and PUCCH format 3, respectively; receiving information from the base station, the information including parameters related to an additional maximum code rate; Here, the parameters related to the additional maximum code rate are set for each of the PUCCH format 2 and the PUCCH format 3, (i) determining a first maximum code rate of a first uplink control information (UCI) having a first priority and a second maximum code rate of a second UCI having a second priority based on (i) a PUCCH format corresponding to the PUCCH format 2 or the PUCCH format 3, (ii) a maximum code rate set for the PUCCH format, and (iii) an additional maximum code rate set for the PUCCH format; For the PUCCH format, the minimum number of PRBs (PRBs) 【number】 ) is determined, where: 【number】 = [Equation 3] is determined based on Here, in equation (3), r 0 is the maximum code rate of the second UCI, r 1 is the maximum code rate of the first UCI, 【number】 is the number of bits of the second UCI, 【number】 is the number of CRC (Cyclic Redundancy Check) bits for the second UCI, 【number】 is the number of bits of the first UCI, 【number】 is the number of CRC bits for the first UCI, 【number】 is the number of subcarriers, 【number】 is the number of Orthogonal Frequency Division Multiplexing (OFDM) symbols, Q m is the modulation order; The user equipment is configured to transmit the first UCI having a first priority and the second UCI having a second priority to the base station via one PUCCH using the PUCCH format based on the minimum number of PRBs for the PUCCH format.
10. The instruction words stored in the one or more memories are: The user device: receiving, from the base station, a PUCCH configuration list including a first PUCCH configuration having a second priority and a second PUCCH configuration having a first priority; If the PUCCH format is included in the second PUCCH configuration, determining the first maximum code rate of the first UCI having the first priority from parameters related to the maximum code rate associated with the second PUCCH configuration having the first priority; 10. The user equipment of claim 9, further configured to determine the second maximum code rate of the second UCI of the second priority from among parameters related to the additional maximum code rate associated with the second PUCCH configuration of the first priority.
11. The instruction words stored in the one or more memories are: The user device: The user equipment of claim 9, further configured to separately encode the first UCI of the first priority and the second UCI of the second priority.
12. A user device as described in Claim 11, characterized in that the number of bits of the first UCI, which is the first priority, is greater than a default value, or the number of bits of the second UCI, which is the second priority, is greater than a default value.
13. A method for a base station (BS) in a wireless communication system, comprising: transmitting information to a user equipment (UE) including parameters related to a maximum code rate; Here, the parameters related to the maximum code rate are set for each of the PUCCH format 2 and the PUCCH format 3, transmitting information including parameters related to an additional maximum code rate to the user equipment; Here, the parameters related to the additional maximum code rate are set for each of the PUCCH format 2 and the PUCCH format 3, determining a first maximum code rate of a first uplink control information (UCI) having a first priority and a second maximum code rate of a second UCI having a second priority based on (i) a PUCCH format corresponding to the PUCCH format 2 or the PUCCH format 3, (ii) a maximum code rate set for the PUCCH format, and (iii) an additional maximum code rate set for the PUCCH format; For the PUCCH format, the minimum number of PRBs (PRBs) 【number】 ) determining where: 【number】 = [Equation 3] is determined based on Here, in equation (3), r 0 is the maximum code rate of the second UCI, r 1 is the maximum code rate of the first UCI, 【number】 is the number of bits of the second UCI, 【number】 is the number of CRC (Cyclic Redundancy Check) bits for the second UCI, 【number】 is the number of bits of the first UCI, 【number】 is the number of CRC bits for the first UCI, 【number】 is the number of subcarriers, 【number】 is the number of Orthogonal Frequency Division Multiplexing (OFDM) symbols, Q m is the modulation order; receiving the first UCI having the first priority and the second UCI having the second priority from the user equipment via one PUCCH using the PUCCH format based on the minimum number of PRBs for the PUCCH format.
14. A base station (BS) in a wireless communication system, comprising: The base station a transmitter / receiver; at least one processor coupled to the transceiver; one or more memories communicatively coupled to the at least one processor; the one or more memories store instructions that can be executed by the at least one processor, either alone or in combination; The command word is: The base station transmitting information to a user equipment (UE) including parameters related to a maximum code rate; Here, the parameters related to the maximum code rate are set for each of the PUCCH format 2 and the PUCCH format 3, transmitting information including parameters related to an additional maximum code rate to the user equipment; Here, the parameters related to the additional maximum code rate are set for each of the PUCCH format 2 and the PUCCH format 3, (i) determining a first maximum code rate of a first uplink control information (UCI) having a first priority and a second maximum code rate of a second UCI having a second priority based on (i) a PUCCH format corresponding to the PUCCH format 2 or the PUCCH format 3, (ii) a maximum code rate set for the PUCCH format, and (iii) an additional maximum code rate set for the PUCCH format; For the PUCCH format, the minimum number of PRBs (PRBs) 【number】 Determine where: 【number】 = [Equation 3] is determined based on Here, in equation (3), r 0 is the maximum code rate of the second UCI, r 1 is the maximum code rate of the first UCI, 【number】 is the number of bits of the second UCI, 【number】 is the number of CRC (Cyclic Redundancy Check) bits for the second UCI, 【number】 is the number of bits of the first UCI, 【number】 is the number of CRC bits for the first UCI, 【number】 is the number of subcarriers, 【number】 is the number of Orthogonal Frequency Division Multiplexing (OFDM) symbols, Q m is the modulation order; a base station configured to receive, from the user equipment, the first UCI having the first priority and the second UCI having the second priority via one PUCCH using the PUCCH format based on the minimum number of PRBs for the PUCCH format.
Citation Information
Patent Citations
User terminal and radio communication method
WO2019130521A1
Method and apparatus for transmitting uplink control information (UCI)
WO2020135214A1