Patent Application
20230318748
The present disclosure relates generally to communication systems. More specifically, the present disclosure relates to code rate determination for multiplexing of HARQ-ACK with different priorities on physical uplink control channel (PUCCH) with separate coding.
Wireless communication devices have become smaller and more powerful in order to meet consumer needs and to improve portability and convenience. Consumers have become dependent upon wireless communication devices and have come to expect reliable service, expanded areas of coverage and increased functionality. A wireless communication system may provide communication for a number of wireless communication devices, each of which may be serviced by a base station. A base station may be a device that communicates with wireless communication devices.
As wireless communication devices have advanced, improvements in communication capacity, speed, flexibility and/or efficiency have been sought. However, improving communication capacity, speed, flexibility, and/or efficiency may present certain problems.
For example, wireless communication devices may communicate with one or more devices using a communication structure. However, the communication structure used may only offer limited flexibility and/or efficiency. As illustrated by this discussion, systems and methods that improve communication flexibility and/or efficiency may be beneficial.
In one example, a user equipment (UE), comprising: a processor configured to: determine a maximum code rate for a low priority hybrid automatic repeat request-acknowledgement (HARQ-ACK) that is multiplexed with a high priority HARQ-ACK on a high priority physical uplink control channel (PUCCH), the low priority HARQ-ACK having a separate code rate than the high priority HARQ-ACK, and separately code and multiplex the high priority HARQ-ACK and the low priority HARQ-ACK based on a maximum code rate for the high priority HARQ-ACK and the determined maximum code rate for the low priority HARQ-ACK respectively; and transmitting circuitry configured to transmit the multiplexed HARQ-ACK on the PUCCH.
In one example, a base station (gNB), comprising: a processor configured to: determine a maximum code rate for a low priority hybrid automatic repeat request-acknowledgement (HARQ-ACK) that is multiplexed with a high priority HARQ-ACK on a high priority physical uplink control channel (PUCCH), the low priority HARQ-ACK having a separate code rate than the high priority HARQ-ACK; and receiving circuitry configured to receive multiplexed HARQ-ACK on the PUCCH, the high priority HARQ-ACK and the low priority HARQ-ACK being separately coded and multiplexed based on a maximum code rate for the high priority HARQ-ACK and the determined maximum code rate for the low priority HARQ-ACK respectively.
In one example, a method by a user equipment (UE), comprising: determining a maximum code rate for a low priority hybrid automatic repeat request-acknowledgement (HARQ-ACK) that is multiplexed with a high priority HARQ-ACK on a high priority physical uplink control channel (PUCCH), the low priority HARQ-ACK having a separate code rate than the high priority HARQ-ACK; separate coding and multiplexing the high priority HARQ-ACK and the low priority HARQ-ACK based on a maximum code rate for the high priority HARQ-ACK and the determined maximum code rate for the low priority HARQ-ACK respectively; and transmitting the multiplexed HARQ-ACK on the PUCCH.
In one example, a method by a base station (gNB), comprising: determining a maximum code rate for a low priority hybrid automatic repeat request-acknowledgement (HARQ-ACK) that is multiplexed with a high priority HARQ-ACK on a high priority physical uplink control channel (PUCCH), the low priority HARQ-ACK having a separate code rate than the high priority HARQ-ACK; and receiving multiplexed HARQ-ACK on the PUCCH, the high priority HARQ-ACK and the low priority HARQ-ACK being separately coded and multiplexed based on a maximum code rate for the high priority HARQ-ACK and the determined maximum code rate for the low priority HARQ-ACK respectively.
A user equipment (UE) is described. The UE may include a processor configured to determine a maximum code rate for a low priority hybrid automatic repeat request-acknowledgement (HARQ-ACK) that is multiplexed with a high priority HARQ-ACK on a physical uplink control channel (PUCCH). The low priority HARQ-ACK may have a separate code rate than the high priority HARQ-ACK. The processor may multiplex the low priority HARQ-ACK and the high priority HARQ-ACK based on the determined maximum code rate for the low priority HARQ-ACK. The UE may also include transmit circuitry configured to transmit the multiplexed HARQ-ACK on the PUCCH.
In some examples, the determined maximum code rate for the low priority HARQ-ACK is based on a configuration in PUCCH-Configs. The determined maximum code rate for the low priority HARQ-ACK may be based on a power control parameter in a PUCCH-Configs.
In some examples, the determined maximum code rate for the low priority HARQ-ACK is based on a PUCCH-Config for ultra-reliable low-latency communication (URLLC) configured with two maximum code rates.
In some examples, the determined maximum code rate for the low priority HARQ-ACK may be based on a beta offset value or coding rate ratio between uplink control information (UCI) of different priorities.
In some examples, the determined maximum code rate for the low priority HARQ-ACK is based on an offset value for a maxCodeRate index configured between URLLC and enhanced mobile broadband (eMBB).
In some examples, the determined maximum code rate for the low priority HARQ-ACK is based on a configured maxCodeRate for low priority UCI multiplexing on high priority PUCCH.
In some examples, the determined maximum code rate for the low priority HARQ-ACK is based on a number of Physical Resource Blocks (PRBs) for UCIs of each priority, a maximum payload size for UCIs of each priority, or a payload size and an available number of PRBs.
A base station (gNB) is also described. The gNB may include a processor configured to determine a maximum code rate for a low priority HARQ-ACK that is multiplexed with a high priority HARQ-ACK on a PUCCH. The low priority HARQ-ACK may have a separate code rate than the high priority HARQ-ACK. The gNB may also include receiving circuitry configured to receive multiplexed HARQ-ACK on the PUCCH. The low priority HARQ-ACK and the high priority HARQ-ACK may be multiplexed based on the determined maximum code rate for the low priority HARQ-ACK.
A method by a UE is also described. The method includes determining a maximum code rate for a low priority HARQ-ACK that is multiplexed with a high priority HARQ-ACK on a PUCCH. The low priority HARQ-ACK may have a separate code rate than the high priority HARQ-ACK. The method may also include multiplexing the low priority HARQ-ACK and the high priority HARQ-ACK based on the determined maximum code rate for the low priority HARQ-ACK. The method may further include transmitting the multiplexed HARQ-ACK on the PUCCH.
A method by a gNB is also described. The method includes determining a maximum code rate for a low priority HARQ-ACK that is multiplexed with a high priority HARQ-ACK on a PUCCH. The low priority HARQ-ACK may have a separate code rate than the high priority HARQ-ACK. The method also includes receiving multiplexed HARQ-ACK on the PUCCH. The low priority HARQ-ACK and the high priority HARQ-ACK may be multiplexed based on the determined maximum code rate for the low priority HARQ-ACK.
The 3rd Generation Partnership Project, also referred to as “3GPP,” is a collaboration agreement that aims to define globally applicable technical specifications and technical reports for third, fourth, and fifth generation wireless communication systems. The 3GPP may define specifications for next generation mobile networks, systems, and devices.
3GPP Long Term Evolution (LTE) is the name given to a project to improve the Universal Mobile Telecommunications System (UMTS) mobile phone or device standard to cope with future requirements. In one aspect, UMTS has been modified to provide support and specification for the Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN).
At least some aspects of the systems and methods disclosed herein may be described in relation to the 3GPP LTE, LTE-Advanced (LTE-A) and other standards (e.g., 3GPP Releases 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, etc.). However, the scope of the present disclosure should not be limited in this regard. At least some aspects of the systems and methods disclosed herein may be utilized in other types of wireless communication systems.
A wireless communication device may be an electronic device used to communicate voice and/or data to a base station, which in turn may communicate with a network of devices (e.g., public switched telephone network (PSTN), the Internet, etc.). In describing systems and methods herein, a wireless communication device may alternatively be referred to as a mobile station, a UE, an access terminal, a subscriber station, a mobile terminal, a remote station, a user terminal, a terminal, a subscriber unit, a mobile device, etc. Examples of wireless communication devices include cellular phones, smart phones, personal digital assistants (PDAs), laptop computers, netbooks, e-readers, wireless modems, etc. In 3GPP specifications, a wireless communication device is typically referred to as a UE. However, as the scope of the present disclosure should not be limited to the 3GPP standards, the terms “UE” and “wireless communication device” may be used interchangeably herein to mean the more general term “wireless communication device.” A UE may also be more generally referred to as a terminal device.
In 3GPP specifications, a base station is typically referred to as a Node B, an evolved Node B (eNB), a home enhanced or evolved Node B (HeNB) or some other similar terminology. As the scope of the disclosure should not be limited to 3GPP standards, the terms “base station,” “Node B,” “eNB,” “gNB” and/or “HeNB” may be used interchangeably herein to mean the more general term “base station.” Furthermore, the term “base station” may be used to denote an access point. An access point may be an electronic device that provides access to a network (e.g., Local Area Network (LAN), the Internet, etc.) for wireless communication devices. The term “communication device” may be used to denote both a wireless communication device and/or a base station. An eNB may also be more generally referred to as a base station device.
It should be noted that as used herein, a “cell” may be any communication channel that is specified by standardization or regulatory bodies to be used for International Mobile Telecommunications-Advanced (IMT-Advanced) and all of it or a subset of it may be adopted by 3GPP as licensed bands (e.g., frequency bands) to be used for communication between an eNB and a UE. It should also be noted that in E-UTRA and E-UTRAN overall description, as used herein, a “cell” may be defined as “combination of downlink and optionally uplink resources.” The linking between the carrier frequency of the downlink resources and the carrier frequency of the uplink resources may be indicated in the system information transmitted on the downlink resources.
“Configured cells” are those cells of which the UE is aware and is allowed by an eNB to transmit or receive information. “Configured cell(s)” may be serving cell(s). The UE may receive system information and perform the required measurements on all configured cells. “Configured cell(s)” for a radio connection may include a primary cell and/or no, one, or more secondary cell(s). “Activated cells” are those configured cells on which the UE is transmitting and receiving. That is, activated cells are those cells for which the UE monitors the physical downlink control channel (PDCCH) and in the case of a downlink transmission, those cells for which the UE decodes a physical downlink shared channel (PDSCH). “Deactivated cells” are those configured cells that the UE is not monitoring the transmission PDCCH. It should be noted that a “cell” may be described in terms of differing dimensions. For example, a “cell” may have temporal, spatial (e.g., geographical) and frequency characteristics.
Fifth generation (5G) cellular communications (also referred to as “New Radio,” “New Radio Access Technology” or “NR” by 3GPP) envisions the use of time/frequency/space resources to allow for enhanced mobile broadband (eMBB) communication and ultra-reliable low-latency communication (URLLC) services, as well as massive machine type communication (MMTC) like services. A new radio (NR) base station may be referred to as a gNB. A gNB may also be more generally referred to as a base station or base station device.
Methods are described herein to determine the maximum code rate for HARQ-ACK with low priority when separate coding for multiplexing of HARQ-ACK with different priorities is applied. For high priority HARQ-ACK, the maxCodeRate parameter can be used to determine the maximum code rate for UCI rate matching. A different maximum code rate may be applied for the low priority HARQ-ACK to provide different error protection and BER requirements. Thus, a UE can be configured with two maximum code rates for UCI multiplexing of HARQ-ACK with different priorities on a single PUCCH (selected from high priority PUCCH resources configured for URLLC).
PUCCH resource selection and multiplexing of HARQ-ACK with different priorities on PUCCH are also described herein. With different maximum code rate applied for UCIs with different priorities, this disclosure presents details of PUCCH resource selection and multiplexing of HARQ-ACK with different priorities on the selected PUCCH resource.
Various examples of the systems and methods disclosed herein are now described with reference to the Figures, where like reference numbers may indicate functionally similar elements. The systems and methods as generally described and illustrated in the Figures herein could be arranged and designed in a wide variety of different implementations. Thus, the following more detailed description of several implementations, as represented in the Figures, is not intended to limit scope, as claimed, but is merely representative of the systems and methods.
The UE 102 and the gNB 160 may use one or more channels 119, 121 to communicate with each other. For example, a UE 102 may transmit information or data to the gNB 160 using one or more uplink channels 121. Examples of uplink channels 121 include a PUCCH (Physical Uplink Control Channel) and a PUSCH (Physical Uplink Shared Channel), PRACH (Physical Random Access Channel), etc. For example, uplink channels 121 (e.g., PUSCH) may be used for transmitting UL data (i.e., Transport Block(s), MAC PDU, and/or UL-SCH (Uplink-Shared Channel)).
In some examples, UL data may include URLLC data. The URLLC data may be UL-SCH data. Here, URLLC-PUSCH (i.e., a different Physical Uplink Shared Channel from PUSCH) may be defined for transmitting the URLLC data. For the sake of simple description, the term “PUSCH” may mean any of (1) only PUSCH (e.g., regular PUSCH, non-URLLC-PUSCH, etc.), (2) PUSCH or URLLC-PUSCH, (3) PUSCH and URLLC-PUSCH, or (4) only URLLC-PUSCH (e.g., not regular PUSCH).
Also, for example, uplink channels 121 may be used for transmitting Hybrid Automatic Repeat Request-ACK (HARQ-ACK), Channel State Information (CSI), and/or Scheduling Request (SR) signals. The HARQ-ACK may include information indicating a positive acknowledgment (ACK) or a negative acknowledgment (NACK) for DL data (i.e., Transport Block(s), Medium Access Control Protocol Data Unit (MAC PDU), and/or DL-SCH (Downlink-Shared Channel)).
The CSI may include information indicating a channel quality of downlink. The SR may be used for requesting UL-SCH (Uplink-Shared Channel) resources for new transmission and/or retransmission. For example, the SR may be used for requesting UL resources for transmitting UL data.
The one or more gNBs 160 may also transmit information or data to the one or more UEs 102 using one or more downlink channels 119, for instance. Examples of downlink channels 119 include a PDCCH, a PDSCH, etc. Other kinds of channels may be used. The PDCCH may be used for transmitting Downlink Control Information (DCI).
Each of the one or more UEs 102 may include one or more transceivers 118, one or more demodulators 114, one or more decoders 108, one or more encoders 150, one or more modulators 154, a data buffer 104, and a UE operations module 124. For example, one or more reception and/or transmission paths may be implemented in the UE 102. For convenience, only a single transceiver 118, decoder 108, demodulator 114, encoder 150, and modulator 154 are illustrated in the UE 102, though multiple parallel elements (e.g., transceivers 118, decoders 108, demodulators 114, encoders 150, and modulators 154) may be implemented.
The transceiver 118 may include one or more receivers 120 and one or more transmitters 158. The one or more receivers 120 may receive signals from the gNB 160 using one or more antennas 122a-n. For example, the receiver 120 may receive and downconvert signals to produce one or more received signals 116. The one or more received signals 116 may be provided to a demodulator 114. The one or more transmitters 158 may transmit signals to the gNB 160 using one or more antennas 122a-n. For example, the one or more transmitters 158 may upconvert and transmit one or more modulated signals 156.
The demodulator 114 may demodulate the one or more received signals 116 to produce one or more demodulated signals 112. The one or more demodulated signals 112 may be provided to the decoder 108. The UE 102 may use the decoder 108 to decode signals. The decoder 108 may produce decoded signals 110, which may include a UE-decoded signal 106 (also referred to as a first UE-decoded signal 106). For example, the first UE-decoded signal 106 may comprise received payload data, which may be stored in a data buffer 104. Another signal included in the decoded signals 110 (also referred to as a second UE-decoded signal 110) may comprise overhead data and/or control data. For example, the second UE-decoded signal 110 may provide data that may be used by the UE operations module 124 to perform one or more operations.
In general, the UE operations module 124 may enable the UE 102 to communicate with the one or more gNBs 160. The UE operations module 124 may include a UE scheduling module 126. In some examples, the UE scheduling module 126 may be utilized to perform multiplexing of HARQ-ACK with different priorities on PUCCH as described herein.
Code rate determination for multiplexing of HARQ-ACK with different priorities on PUCCH with separate coding is described herein. For example, details of separate coding methods for UCI multiplexing of HARQ-ACK with different priorities are described.
As enhancements of HARQ-ACK reporting with different priorities, multiplexing of UCI between different priorities can be supported by high layer signaling under some timing restrictions. For example, multiplexing of the same UCI type on a single PUCCH (e.g., URLLC HARQ-ACK and eMBB HARQ-ACK) may be supported.
A high priority UCI may be a high priority HARQ-ACK or a high priority SR. The priority of a SR can be indicated in a SR configuration by higher layer signaling. A high priority HARQ-ACK may correspond to a high priority PDSCH transmission. The priority of a scheduled PDSCH transmission may be determined by the priority indication in the scheduling DCI. The priority of an SPS PDSCH transmission may be configured by higher layer signaling. A high priority PUCCH resource should be used to report high priority HARQ-ACK with or without SR. A high priority PDSCH, HARQ-ACK or PUCCH resource may be configured to support URLLC services. In some examples, the high priority is configured with a priority index 1. A PUSCH or a PUCCH, including repetitions if any, can be of priority index 0 or of priority index 1. If a priority index is not provided for a PUSCH or a PUCCH, the priority index is 0.
A low priority UCI may be a low-priority HARQ-ACK, a low priority SR, or a low priority CSI report, etc. A low priority HARQ-ACK may correspond to a low priority PDSCH transmission. The priority of a scheduled PDSCH transmission may be determined by the priority indication in the scheduling DCI. The priority of a SPS PDSCH transmission may be configured by higher layer signaling. A low priority PUCCH resource should be used to report low priority UCI. A low priority PDSCH, HARQ-ACK or PUCCH resource may be configured to support eMBB services. The low priority may be configured with a priority index 0.
If multiplexing of HARQ-ACK with different priorities on a PUCCH is supported, separate coding may be supported. In this case, the HARQ-ACK codebook of URLLC and eMBB may be coded and rate matched independently based on the maximum coding rate of the URLLC and eMBB PUCCH configuration. The coded bits may be rate matched separately and then concatenated together and transmitted on the selected PUCCH resource for URLLC.
Separate coding can be applied at least for the case that the number of HARQ-ACK bits for codebooks with different priorities is greater than 2 bits. With a separate coding method, HARQ-ACK codebooks with or without SR may be encoded separately based on different maximum code rate for each UCI priority. Thus, the UE may have two maximum code rates for HARQ-ACK with different priorities for multiplexing on a single PUCCH selected from high priority PUCCH resources configured for URLLC. For the high priority HARQ-ACK, the maximum code rate configured for the high priority PUCCH may be used. However, how to determine the maximum code rate of the low priority UCI on a high priority PUCCH resource may be further specified. Several methods are described herein.
In a first method (Method 1), an existing configuration in PUCCH-Configs may be used. In NR, two PUCCH-Configs can be configured on a UE. The PUCCH resources for eMBB HARQ-ACK can be configured with a PUCCH-Config with low priority or priority index 0, and the PUCCH resources for URLLC HARQ-ACK can be configured with a separate PUCCH-Config with high priority or priority index 1. The maximum code rate can be configured independently in each PUCCH-Config for PUCCH format 2, PUCCH format 3 and PUCCH format 4. Listing-1 illustrates an example for configuring the maximum code rate (maxCodeRate). Table-1 illustrates examples of the code rate (r) corresponding to the value of maxCodeRate.
Therefore, in one method, in the case that two PUCCH-Configs are configured, the maximum code rate in PUCCH-Config with high priority may be used for URLLC HARQ-ACK, and the maximum code rate in the PUCCH-Config with low priority can be used for eMBB HARQ-ACK.
To provide higher reliability for high priority UCI, the high priority PUCCH carrying high priority URLLC HARQ-ACK may be lower than the maximum code rate for low priority PUCCH carrying low priority eMBB HARQ-ACK. This would be true if the high priority and low priority PUCCH are configured with the same transmit powers. Thus, if the same transmit power is configured for PUCCH resources configured for different priorities, the maximum code rate in each PUCCH-Config may be applied to the HARQ-ACK bits with the corresponding priority for multiplexing of HARQ-ACK with different priorities on a single PUCCH.
However, the transit power boosting is another method for URLLC PUCCH enhancement. The PUCCH reliability may be differentiated by configuring different power control parameters (e.g., a high priority PUCCH may be configured with higher transmit power than a low priority PUCCH). In this case, the maximum code rate configured for a low priority PUCCH may not be higher than the maximum code rate configured for a high priority PUCCH; or the maximum code rate difference between the high priority PUCCH and low priority PUCCH itself is not sufficient to satisfy the reliability requirements. If the maximum code rate of a low priority PUCCH is used directly for HARQ-ACK multiplexing of different priorities on a high priority PUCCH, the low priority HARQ-ACK would be given unnecessary protection with higher overhead on a high priority PUCCH resource.
With different PUCCH-Configs, separate PUCCH-PowerControl can be configured, and different p0-nominal parameters can be configured in the PUCCH-ConfigCommon for PUCCH with different priorities. The information element (IE) PUCCH-ConfigCommon may be used to configure the cell specific PUCCH parameters. Listing-2 illustrates an example of a PUCCH-ConfigCommon IE.
The IE PUCCH-PowerControl is used to configure UE-specific parameters for the power control of PUCCH. Listing-3 illustrates an example of a PUCCH-PowerControl IE.
PPUCCH,b,f,c(i, qu, qd, l)=min{A,B} [dBm],
where
If P0-nominal is the same for PUCCHs with different priorities, the maximum code rate in each PUCCH-Config can be applied HARQ-ACKs with the corresponding priority. That is, the maximum code rate in PUCCH-Config with high priority may be used for URLLC HARQ-ACK, and the maximum code rate in the PUCCH-Config with low priority may be used for eMBB HARQ-ACK.
If P0-nominal is different for the PUCCHs with different priorities, the P0-nominal for the high priority PUCCH may be configured with a higher power than that of a low priority PUCCH. The method to adjust the maximum code rate based on the transmit power difference can be further defined as discussed below.
For a PUCCH transmission, a 3 dB transmit power boost is equivalent to a repetition of the PUCCH transmission with the same transmit power, which can be approximately equivalent to apply an extra coding rate of r_extra=½. In general, for a power boost of x dB between URLLC and eMBB PUCCH, an equivalent extra coding rate can be given as
Thus, for the UCI with low priority transmitted on a PUCCH with high priority, if the transmit power of a PUCCH with high priority has a power boost of x dB over the transmit power of a PUCCH with low priority, to keep the same maximum code rate for UCI with low priority, the actual maximum code rate for the low priority UCI should be adjusted by dividing the r_extra coding rate as follows:
Thus, if P0-nominal is different for PUCCHs with different priorities, for multiplexing of UCI with different priorities on a high priority PUCCH, the maximum code rate for low priority UCI should be adjusted based on the differences between P0-nominal values based on the above calculations.
r_determined=min(r_adjusted, 0.8).
In one approach, the resulting r_determined can be any value below the maximum coding rate of 0.8. The encoded UCI rate matching can be performed accordingly based on the r_determined.
In another approach, to make sure a standard maximum code rate is used, the r_determined can be selected from the standard code rate values in the maxCodeRate table by choosing the closest code rate that is less than or equal to the calculated adjusted code rate r_adjusted.
To reduce complexity, a constant ratio can be used. Thus, in another method, a separate beta offset value or a code rate ratio can be configured. The beta offset or code rate ratio may be configured in a PUCCH-Config or PUCCH-ConfigCommon for PUCCHs with high priority PUCCH resources, as given in the examples of Listing-4.
The beta offset or code rate ratio may be separately configured by higher layer signaling (e.g., RRC signaling). The new parameter (e.g., a beta-offset) may specify the relative code rate ratio between UCI (e.g., HARQ-ACK) with different priorities. The beta offset or code ratio indicates relative protection between URLLC UCI over eMBB UCI.
In one approach, the beta offset is a value greater than or equal to 1 as the ratio between the maximum code rate of eMBB and URLLC. For example, beta_offset_1=r_0/r_1, where r_0 is the expected maximum code rate for low priority UCI with priority index 0, and r_1 is the maximum code rate for high priority UCI with priority index 1. The r_1 is determined by the maxCodeRate parameter in the PUCCH-Config for high priority PUCCH. With the configured beta_offset_1, the expected maximum code rate for low priority UCI is determined by r_0=r_1*beta_offet_1. The beta offset value may be selected from a pre-defined or configured set of values (e.g., a set of {1.5, 2, 3, 4}).
In another approach, the beta offset is a value less than or equal to 1 as the ratio between the maximum code rate of URLLC and eMBB. For example, beta_offset_2=r_1/r_0, where r_0 is the maximum code rate for low priority UCI with priority index 0, and r_1 is the maximum code rate for high priority UCI with priority index 1. The r_1 may be determined by the maxCodeRate parameter in the PUCCH-Config for high priority PUCCH. With the configured beta_offset_2, the expected maximum code rate for low priority UCI is determined by r_0=r_1/beta_offet_2. The beta offset value may be selected from a pre-defined or configured set of values (e.g., a set of {0.67, 0.5, 0.33, 0.25}).
The beta offset or code rate ratio may be configured for a UCI type to provide the relative redundancy (e.g., applying an extra code rate ratio for the UCI over PUSCH data). Also, different beta-offset values may be applied to different UCI types (e.g., a HARQ-ACK is configured with a higher beta-offset value than a CSI). Furthermore, for the multiplexing of UCI with different priorities, the beta-offset or code rate ratio may determine the relative protection of high priority UCI over the low priority UCI.
r_determined=min(r_0, 0.8).
In one approach, the resulting r_determined can be any value below the maximum coding rate of 0.8. The encoded UCI rate matching can be performed accordingly based on the r_determined.
In another approach, to make sure a standard maximum code rate is used, the r_determined can be selected from the standard code rate values in the maxCodeRate table by choosing the closest code rate that is less than or equal to the calculated code rate r_0.
In a third method (Method 3), the PUCCH-Config for URLLC can be configured with two maximum code rates. With both Method 1 and Method 2, the determined maximum code rate for low priority UCI may provide the desired protection for low priority UCI on a high priority PUCCH. However, with one approach, the adjusted or determined maximum code rate may not be a standard rate specified in the max-CodeRate table. With another approach, an extra step may be performed to select a standard code rate in the maxCodeRate table by choosing the closest code rate that is less than or equal to the calculated adjusted code rate.
To avoid the potential complexity and calculations, in another method, the PUCCH-Config for high priority PUCCH can be configured with two maximum code rates, one for high priority URLLC UCI, and one for low priority eMBB UCI when UCI multiplexing on a single PUCCH is applied.
For example, an extra configuration maxCodeRate_0 can be added to the PUCCH-FormatConfig for PUCCH-Config of high priority PUCCH resources. The max-CodeRate is used to determine the maximum code rate for high priority UCI on a high priority PUCCH. The maxCodeRate_0 is used to determine the maximum code rate for low priority UCI only when multiplexing of UCI with different priorities are applied on a high priority PUCCH. The maxCodeRate_0 should always be configured with a higher code rate than the maxCodeRate. The maximum code rate of each priority is then determined based on the maxCodeRate parameter based on the table above. An example of a PUCCH-FormatConfig IE with a maxCodeRate_0 is illustrated in Listing-5.
In a fourth method (Method 4), an offset value for maxCodeRate index may be configured between the URLLC and eMBB. In this method, to reduce the complexity of code rate calculation and select a maximum code rate from the standard rates specified in the maxCodeRate table, an offset value for the maxCodeRate index may be configured between the UCI with different priorities. The maxCodeRate offset may be configured in a PUCCH-Config or PUCCH-ConfigCommon for PUCCHs with high priority PUCCH resources. In example of this approach is illustrated in Listing-6.
The maxCodeRate offset (e.g., maxCodeRate_Offset) may be separately configured by higher layer signaling (e.g., RRC signaling). The maxCodeRate offset parameter may specify the relative distance between the maxCodeRate index of high priority UCI and low priority UCI. The maxCodeRate offset may be a positive integer (e.g., an integer within the set {1, 2, 3, 4}).
In the case of multiplexing of HARQ-ACK with different priorities on a high priority PUCCH resource, the maximum code rate of high priority UCI (e.g., HARQ-ACK with priority index 1), may be given by the maxCodeRate parameter. The maximum code rate of the low priority UCI (e.g., HARQ-ACK with priority index 0) may be the code rate value determined by an index value given by (maxCodeRate+max-CodeRate_Offset) in the code rate table. It should be noted that the maximum coding rate for the low priority UCI should not exceed the values defined in the code rate table. Thus, the valid maxCodeRate index should not be higher than 6 because index value 7 is reserved. Therefore, the resulting index value used for low priority HARQ-ACK is given by maxCodeRate index for low priority UCI=min((maxCodeRate+maxCodeRate_Offset), 6).
For example, if maxCodeRate is configured with 1 in the PUCCH configure for high priority HARQ-ACK, and an offset value is configured with a value of 2, when separate coding is used for multiplexing of HARQ-ACK with different priorities on a single PUCCH with high priority, the maximum code rate for HARQ-ACK with high priority is 0.15 given by the maxCodeRate index value of 1.
The maximum code rate for HARQ-ACK with low priority may be determined by the maxCodeRate index value of 1 added with the maxCodeRate_Offset value of 2, resulting a value of 3. Thus, the maximum code rate for HARQ-ACK with low priority is 0.35 based on the result maxCodeRate value of 3.
As a special case in this method, the maxCodeRate_Offset may be a fixed value (e.g., 1 or 2). The value can be fixed in the standard or configured by higher layer signaling.
In a fifth method (Method 5), a maxCodeRate for low priority UCI multiplexing on high priority PUCCH may be configured. In this method, a UE can be configured with a separate maxCodeRate (e.g., maxCodeRate_Mux) for low priority UCI when UCI multiplexing with different priorities on a single high priority PUCCH is applied. This parameter can be configured separately by higher layer signaling. The parameter is used only when multiplexing of UCI with different priorities is applied.
Therefore, for low priority HARQ-ACK, if it is reported on a low priority PUCCH resource, the maxCodeRate on the low priority PUCCH-Config is applied. When it is multiplexed with high priority UCI on a high priority PUCCH, the separately configured maxCodeRate_Mux is applied for the low priority UCI.
In a sixth method (Method 6), additional parameters may be configured. For example, the number of PRBs or the maximum payload size for UCIs of each priority and/or the maximum code rate of the low priority UCI may be determined based on the payload size and the available number of PRBs. The details of this method are described below. In this method, the code rate of the low priority UCI is not predetermined. The UE may first calculate the number of PRBs for the high priority UCI to determine the available number of PRBs for the low priority UCI. The code rate of the low priority UCI is then determined based on the payload size and the available number of PRBs.
PUCCH resource selection and multiplexing of HARQ-ACK with different priorities on PUCCH is also described herein. In current NR releases, UCI multiplexing on PUCCH is supported only for UCIs with the same priority. The PUCCH resource is selected based on the total UCI payload size, and a single maxCodeRate is applied for the UCI coding and rate matching on PUCCH. Thus, for HARQ-ACK codebook with high priority or a HARQ-ACK codebook with low priority, a UE can be configured up to four sets of PUCCH resources. A set of PUCCH resources is provided by PUCCH-ResourceSet and is associated with a Set of PUCCH resources index provided by pucch-ResourceSetld, with a set of PUCCH resource indexes provided by resourceList that provides a set of PUCCH-Resourceld used in the Set of PUCCH resources, and with a maximum number of UCI information bits the UE can transmit using a PUCCH resource in the set of PUCCH resources provided by maxPayloadSize. For the first Set of PUCCH resources, the maximum number of UCI information bits is 2. A maximum number of PUCCH resource indexes for a set of PUCCH resources is provided by maxNrofPUCCH-ResourcesPerSet. The maximum number of PUCCH resources in the first set of PUCCH resources is 32 and the maximum number of PUCCH resources in the other set of PUCCH resources is 8.
When multiplexing of HARQ-ACK with different priorities is supported, two different maximum code rates will be applied for the HARQ-ACK with or without SR with different priorities. To determine the PUCCH resource for the HARQ-ACK multiplexing, the payload calculation should be specified based on the payload size of the high priority HARQ-ACK and the payload size of the low priority HARQ-ACK. Since the low priority UCI is configured with a higher maximum code rate than that of high priority UCI, on the same high priority PUCCH resource, the total UCI payload can be higher than the configured maximum payload for high priority UCI only.
O
UCI_estimate
=O
UCI_1
+α·O
UCI_0,
where OUCI_estimate is the equivalent estimated UCI payload with UCI multiplexing of different priorities. OUCI_1 is the payload of high priority UCI (e.g.,. with priority index 1). For HARQ-ACK with or without SR multiplexing with different priorities, the UCI payload OUCI_1 may be determined as given above for the high priority HARQ-ACK codebook and high priority SR configurations. OUCI_0 is the payload of low priority UCI (e.g., with priority index 0). For HARQ-ACK with or without SR multiplexing with different priorities, the UCI payload OUCI_0 may be determined as given above for the low priority HARQ-ACK codebook and low priority SR configurations. In some examples, α is a scaling factor or a ratio between the maximum code rate of high priority UCI and the maximum code rate of the low priority UCI. That is:
α=r1/r0,
where r1 is the maximum code rate determined by the maxCodeRate parameter for high priority UCI (e.g., UCI with priority index 1), and r0 is the maximum code rate determined by the above-mentioned methods for low priority UCI (e.g., UCI with priority index 0).
The estimated UCI payload represents the different code rate applied on UCIs with different priorities. Since the high priority UCI has a lower maximum code rate than the low priority UCI, the ratio α is smaller than 1, and the estimated UCI payload is smaller than the sum of the payload of high priority UCI and the payload of low priority UCI.
In a second method (Method 2), re-selection of PUCCH resource may be allowed in the case of insufficient PRBs in a selected PUCCH. With method 1, an estimated UCI payload is used to determine a PUCCH resource for multiplexing of UCI with different priorities. The determined PUCCH is used to perform UCI multiplexing. The estimated payload is a good approximation, but may not always be accurate, especially since the UCI of each priority has to be mapped to fit at PRB level. For example, in the following two cases, the low priority UCI may be get the desired code rate.
Since a UE can be configured up to 4 set of PUCCH resources, with the first set of PUCCH resources supports up to 2 bits only. The maximum tests for the PUCCH resource determination and selection is 3 when all 4 sets of PUCCH resources are configured. With the estimated payload in method 1, the actual number of PUCCH resource selection may be even smaller.
In a third method (Method 3), re-selection of PUCCH resource without an estimated payload may be allowed. Since the maximum tests for the PUCCH resource deter-mination and selection is 3 even if all 4 sets of PUCCH resources are configured, the UE may not need to perform the equivalent payload estimation as in Method 1 and Method 2.
Alternative approaches with additional parameters are also described herein. In the case of multiplexing of HRQ-ACK with different priorities, additional parameters can be configured. The additional parameters can be used to select a PUCCH resource for UCI reporting, and determine whether the HARQ-ACK with different priorities can be multiplexed on the selected PUCCH resource. If multiplexing on a single PUCCH is supported, the additional parameters can then be used to determine the number of PRBs to be used for the HARQ-ACK with each priority. The code rate of the low priority UCI may then be determined based on the low priority UCI payload size and the available PRB resources for the multiplexing.
In the case that the number of PRBs are configured for UCIs of each priority, the maximum code rate of the low priority UCI may be determined based on the payload size and the available number of PRBs. The UE may determine a PUCCH resource based on the payload of the high priority UCI. The UE may determine a PUCCH resource based on the payload of the high priority UCI and the payload of the low priority UCI.
Additionally, or alternatively, the UE may perform PUCCH reselection by choosing a PUCCH in the next set of PUCCH resources with higher maximum payload size if it is available, then repeat the same procedure as described above.
In a second method (Method 2), the payload sizes for UCIs of each priority may be configured. In this approach, additional parameters are not configured for each PUCCH resource. Instead, additional parameters are configured for the maximum payload sizes of each resource set. Thus, in case of multiplexing of UCI with different priorities, besides the maximum payload for each set of PUCCH resources, the payload sizes of UCIs with each priority index can be further configured for each set of PUCCH resources.
The maximum payload for the high priority UCI, i.e. with priority index 1, can be less than or equal to the configured maximum payload of the PUCCH resource. The maximum payload for the low priority UCI, i.e. with priority index 0, can be less than or equal to the configured maximum payload of the PUCCH resource. The maximum payload for the low priority UCI may be greater than the configured maximum payload of the PUCCH resource because a higher code rate may be applied for the low priority UCI than the high priority UCI.
In the case that the maximum payload sizes are configured for UCIs of each priority, the maximum code rate of the low priority UCI is also determined based on the payload size and the available number of PRBs. In this case, the PUCCH resource may be selected based the maximum payload size for a high priority UCI instead of the original maximum payload size. For the selected PUCCH resource, multiplexing of HARQ-ACK with different priorities may not be supported if the payload of the low priority HARQ-ACK is higher than the configured maximum payload of low priority UCI.
Additionally, if the actual code rate is greater than the maximum code rate threshold, e.g. a maximum code rate of 0.8, the UE may drop the low priority UCI. The high priority HARQ-ACK with or without SR may be reported on the PUCCH resource selected based on only the high priority UCI payload.
Additionally, or alternatively, the UE may perform PUCCH reselection by choosing a PUCCH in the next set of PUCCH resources with higher maximum payload size if it is available, then repeat the same procedure as described above.
In one approach, only one parameter is configured, the maximum number of PRBs for UCI with each priority index in each PUCCH resource or the maximum number of payloads for UCI with each priority index for each set of PUCCH resources.
In another approach, the maximum number of PRBs for UCI with each priority index in each PUCCH resource and the maximum number of payloads for UCI with each priority index for each set of PUCCH resources may be configured independently and/or jointly.
In the above descriptions, with additional parameters, a maximum code rate of low priority UCI is not separately configured on a PUCCH resource with high priority. The actual code rate for the low priority HARQ-ACK with or without SR is determined based on the available remaining PRBs for the low priority UCI and the payload size of the low priority HARQ-ACK with or without SR.
The additional parameters may be configured indirectly from a separate configuration for maximum code rate of low priority UCI. That is, a maximum code rate for the low priority UCI multiplexed on a high priority PUCCH can still be configured. In this case, if the actual code rate is greater than the configured maximum code rate for low priority UCI, the UE may drop the low priority UCI. The high priority HARQ-ACK with or without SR may be reported on the PUCCH resource selected based on only the high priority UCI payload.
The UE operations module 124 may provide information 148 to the one or more receivers 120. For example, the UE operations module 124 may inform the receiver(s) 120 when to receive retransmissions.
The UE operations module 124 may provide information 138 to the demodulator 114. For example, the UE operations module 124 may inform the demodulator 114 of a modulation pattern anticipated for transmissions from the gNB 160.
The UE operations module 124 may provide information 136 to the decoder 108. For example, the UE operations module 124 may inform the decoder 108 of an anticipated encoding for transmissions from the gNB 160.
The UE operations module 124 may provide information 142 to the encoder 150. The information 142 may include data to be encoded and/or instructions for encoding. For example, the UE operations module 124 may instruct the encoder 150 to encode transmission data 146 and/or other information 142. The other information 142 may include PDSCH HARQ-ACK information.
The encoder 150 may encode transmission data 146 and/or other information 142 provided by the UE operations module 124. For example, encoding the data 146 and/or other information 142 may involve error detection and/or correction coding, mapping data to space, time and/or frequency resources for transmission, multiplexing, etc. The encoder 150 may provide encoded data 152 to the modulator 154.
The UE operations module 124 may provide information 144 to the modulator 154. For example, the UE operations module 124 may inform the modulator 154 of a modulation type (e.g., constellation mapping) to be used for transmissions to the gNB 160. The modulator 154 may modulate the encoded data 152 to provide one or more modulated signals 156 to the one or more transmitters 158.
The UE operations module 124 may provide information 140 to the one or more transmitters 158. This information 140 may include instructions for the one or more transmitters 158. For example, the UE operations module 124 may instruct the one or more transmitters 158 when to transmit a signal to the gNB 160. For instance, the one or more transmitters 158 may transmit during a UL subframe. The one or more transmitters 158 may upconvert and transmit the modulated signal(s) 156 to one or more gNBs 160.
Each of the one or more gNBs 160 may include one or more transceivers 176, one or more demodulators 172, one or more decoders 166, one or more encoders 109, one or more modulators 113, a data buffer 162, and a gNB operations module 182. For example, one or more reception and/or transmission paths may be implemented in a gNB 160. For convenience, only a single transceiver 176, decoder 166, demodulator 172, encoder 109, and modulator 113 are illustrated in the gNB 160, though multiple parallel elements (e.g., transceivers 176, decoders 166, demodulators 172, encoders 109, and modulators 113) may be implemented.
The transceiver 176 may include one or more receivers 178 and one or more transmitters 117. The one or more receivers 178 may receive signals from the UE 102 using one or more antennas 180a-n. For example, the receiver 178 may receive and downconvert signals to produce one or more received signals 174. The one or more received signals 174 may be provided to a demodulator 172. The one or more transmitters 117 may transmit signals to the UE 102 using one or more antennas 180a-n. For example, the one or more transmitters 117 may upconvert and transmit one or more modulated signals 115.
The demodulator 172 may demodulate the one or more received signals 174 to produce one or more demodulated signals 170. The one or more demodulated signals 170 may be provided to the decoder 166. The gNB 160 may use the decoder 166 to decode signals. The decoder 166 may produce one or more decoded signals 164, 168. For example, a first eNB-decoded signal 164 may comprise received payload data, which may be stored in a data buffer 162. A second eNB-decoded signal 168 may comprise overhead data and/or control data. For example, the second eNB decoded signal 168 may provide data (e.g., PDSCH HARQ-ACK information) that may be used by the gNB operations module 182 to perform one or more operations.
In general, the gNB operations module 182 may enable the gNB 160 to communicate with the one or more UEs 102. The gNB operations module 182 may include a gNB scheduling module 194. The gNB scheduling module 194 may perform operations for PUCCH repetition as described herein.
The gNB operations module 182 may provide information 188 to the demodulator 172. For example, the gNB operations module 182 may inform the demodulator 172 of a modulation pattern anticipated for transmissions from the UE(s) 102.
The gNB operations module 182 may provide information 186 to the decoder 166. For example, the gNB operations module 182 may inform the decoder 166 of an anticipated encoding for transmissions from the UE(s) 102.
The gNB operations module 182 may provide information 101 to the encoder 109. The information 101 may include data to be encoded and/or instructions for encoding. For example, the gNB operations module 182 may instruct the encoder 109 to encode information 101, including transmission data 105.
The encoder 109 may encode transmission data 105 and/or other information included in the information 101 provided by the gNB operations module 182. For example, encoding the data 105 and/or other information included in the information 101 may involve error detection and/or correction coding, mapping data to space, time and/or frequency resources for transmission, multiplexing, etc. The encoder 109 may provide encoded data 111 to the modulator 113. The transmission data 105 may include network data to be relayed to the UE 102.
The gNB operations module 182 may provide information 103 to the modulator 113. This information 103 may include instructions for the modulator 113. For example, the gNB operations module 182 may inform the modulator 113 of a modulation type (e.g., constellation mapping) to be used for transmissions to the UE(s) 102. The modulator 113 may modulate the encoded data 111 to provide one or more modulated signals 115 to the one or more transmitters 117.
The gNB operations module 182 may provide information 192 to the one or more transmitters 117. This information 192 may include instructions for the one or more transmitters 117. For example, the gNB operations module 182 may instruct the one or more transmitters 117 when to (or when not to) transmit a signal to the UE(s) 102. The one or more transmitters 117 may upconvert and transmit the modulated signal(s) 115 to one or more UEs 102.
It should be noted that a DL subframe may be transmitted from the gNB 160 to one or more UEs 102 and that a UL subframe may be transmitted from one or more UEs 102 to the gNB 160. Furthermore, both the gNB 160 and the one or more UEs 102 may transmit data in a standard special subframe.
It should also be noted that one or more of the elements or parts thereof included in the eNB(s) 160 and UE(s) 102 may be implemented in hardware. For example, one or more of these elements or parts thereof may be implemented as a chip, circuitry or hardware components, etc. It should also be noted that one or more of the functions or methods described herein may be implemented in and/or performed using hardware. For example, one or more of the methods described herein may be implemented in and/or realized using a chipset, an application-specific integrated circuit (ASIC), a large-scale integrated circuit (LSI) or integrated circuit, etc.
The higher layer processor 223 may manage physical layer's behaviors (the DL transmitter's and the UL receiver's behaviors) and provide higher layer parameters to the physical layer. The higher layer processor 223 may obtain transport blocks from the physical layer. The higher layer processor 223 may send/acquire higher layer messages such as an RRC message and MAC message to/from a UE's higher layer. The higher layer processor 223 may provide the PDSCH transmitter transport blocks and provide the PDCCH transmitter transmission parameters related to the transport blocks.
The DL transmitter 225 may multiplex downlink physical channels and downlink physical signals (including reservation signal) and transmit them via transmission antennas 231. The UL receiver 233 may receive multiplexed uplink physical channels and uplink physical signals via receiving antennas 231 and de-multiplex them. The PUCCH receiver 235 may provide the higher layer processor 223 UCI. The PUSCH receiver 237 may provide the higher layer processor 223 received transport blocks.
The higher layer processor 323 may manage physical layer's behaviors (the UL transmitter's and the DL receiver's behaviors) and provide higher layer parameters to the physical layer. The higher layer processor 323 may obtain transport blocks from the physical layer. The higher layer processor 323 may send/acquire higher layer messages such as an RRC message and MAC message to/from a UE's higher layer. The higher layer processor 323 may provide the PUSCH transmitter transport blocks and provide the PUCCH transmitter 353 UCI.
The DL receiver 343 may receive multiplexed downlink physical channels and downlink physical signals via receiving antennas 331 and de-multiplex them. The PDCCH receiver 345 may provide the higher layer processor 323 DCI. The PDSCH receiver 347 may provide the higher layer processor 323 received transport blocks.
It should be noted that names of physical channels described herein are examples. The other names such as “NRPDCCH, NRPDSCH, NRPUCCH and NRPUSCH”, “new Generation-(G)PDCCH, GPDSCH, GPUCCH and GPUSCH” or the like can be used.
The UE 402 may also include a housing that contains one or more transmitters 458 and one or more receivers 420 to allow transmission and reception of data. The transmitter(s) 458 and receiver(s) 420 may be combined into one or more transceivers 418. One or more antennas 422a-n are attached to the housing and electrically coupled to the transceiver 418.
The various components of the UE 402 are coupled together by a bus system 411, which may include a power bus, a control signal bus, and a status signal bus, in addition to a data bus. However, for the sake of clarity, the various buses are illustrated in
The gNB 560 may also include a housing that contains one or more transmitters 517 and one or more receivers 578 to allow transmission and reception of data. The transmitter(s) 517 and receiver(s) 578 may be combined into one or more transceivers 576. One or more antennas 580a-n are attached to the housing and electrically coupled to the transceiver 576.
The various components of the gNB 560 are coupled together by a bus system 511, which may include a power bus, a control signal bus, and a status signal bus, in addition to a data bus. However, for the sake of clarity, the various buses are illustrated in
It should be noted that one or more of the methods described herein may be implemented in and/or performed using hardware. For example, one or more of the methods described herein may be implemented in and/or realized using a chipset, an application-specific integrated circuit (ASIC), a large-scale integrated circuit (LSI) or integrated circuit, etc.
Each of the methods disclosed herein comprises one or more steps or actions for achieving the described method. The method steps and/or actions may be interchanged with one another and/or combined into a single step without departing from the scope of the claims. In other words, unless a specific order of steps or actions is required for proper operation of the method that is being described, the order and/or use of specific steps and/or actions may be modified without departing from the scope of the claims.
It is to be understood that the claims are not limited to the precise configuration and components illustrated above. Various modifications, changes, and variations may be made in the arrangement, operation, and details of the systems, methods, and apparatus described herein without departing from the scope of the claims.
A program running on the gNB 160 or the UE 102 according to the described systems and methods is a program (a program for causing a computer to operate) that controls a CPU and the like in such a manner as to realize the function according to the described systems and methods. Then, the information that is handled in these apparatuses is temporarily stored in a RAM while being processed. Thereafter, the information is stored in various ROMs or HDDs, and whenever necessary, is read by the CPU to be modified or written. As a recording medium on which the program is stored, among a semiconductor (for example, a ROM, a nonvolatile memory card, and the like), an optical storage medium (for example, a DVD, a MO, a MD, a CD, a BD, and the like), a magnetic storage medium (for example, a magnetic tape, a flexible disk, and the like), and the like, any one may be possible. Furthermore, in some cases, the function according to the described systems and methods described above is realized by running the loaded program, and in addition, the function according to the described systems and methods is realized in conjunction with an operating system or other application programs, based on an instruction from the program.
Furthermore, in a case where the programs are available on the market, the program stored on a portable recording medium can be distributed or the program can be transmitted to a server computer that connects through a network such as the Internet. In this case, a storage device in the server computer also is included. Furthermore, some or all of the gNB 160 and the UE 102 according to the systems and methods described above may be realized as an LSI that is a typical integrated circuit. Each functional block of the gNB 160 and the UE 102 may be individually built into a chip, and some or all functional blocks may be integrated into a chip. Furthermore, a technique of the integrated circuit is not limited to the LSI, and an integrated circuit for the functional block may be realized with a dedicated circuit or a general-purpose processor. Furthermore, if with advances in a semiconductor technology, a technology of an integrated circuit that substitutes for the LSI appears, it is also possible to use an integrated circuit to which the technology applies.
Moreover, each functional block or various features of the base station device and the terminal device used in each of the aforementioned implementations may be implemented or executed by a circuitry, which is typically an integrated circuit or a plurality of integrated circuits. The circuitry designed to execute the functions described in the present specification may comprise a general-purpose processor, a digital signal processor (DSP), an application specific or general application integrated circuit (ASIC), a field programmable gate array (FPGA), or other programmable logic devices, discrete gates or transistor logic, or a discrete hardware component, or a combination thereof. The general-purpose processor may be a microprocessor, or alternatively, the processor may be a conventional processor, a controller, a microcontroller, or a state machine. The general-purpose processor or each circuit described above may be configured by a digital circuit or may be configured by an analogue circuit. Further, when a technology of making into an integrated circuit superseding integrated circuits at the present time appears due to advancement of a semiconductor technology, the integrated circuit by this technology is also able to be used.
As used herein, the term “and/or” should be interpreted to mean one or more items. For example, the phrase “A, B, and/or C” should be interpreted to mean any of: only A, only B, only C, A and B (but not C), B and C (but not A), A and C (but not B), or all of A, B, and C. As used herein, the phrase “at least one of” should be interpreted to mean one or more items. For example, the phrase “at least one of A, B and C” or the phrase “at least one of A, B or C” should be interpreted to mean any of: only A, only B, only C, A and B (but not C), B and C (but not A), A and C (but not B), or all of A, B, and C. As used herein, the phrase “one or more of” should be interpreted to mean one or more items. For example, the phrase “one or more of A, B and C” or the phrase “one or more of A, B or C” should be interpreted to mean any of: only A, only B, only C, A and B (but not C), B and C (but not A), A and C (but not B), or all of A, B, and C.
In one example, a user equipment (UE), comprising: a processor configured to: determine a maximum code rate for a low priority hybrid automatic repeat request-acknowledgement (HARQ-ACK) that is multiplexed with a high priority HARQ-ACK on a physical uplink control channel (PUCCH), the low priority HARQ-ACK having a separate code rate than the high priority HARQ-ACK, and multiplex the low priority HARQ-ACK and the high priority HARQ-ACK based on the determined maximum code rate for the low priority HARQ-ACK; and transmitting circuitry configured to transmit the multiplexed HARQ-ACK on the PUCCH.
In one example, the UE, wherein the determined maximum code rate for the low priority HARQ-ACK is based on a configuration in PUCCH-Configs.
In one example, the UE, wherein the determined maximum code rate for the low priority HARQ-ACK is based on a power control parameter in a PUCCH-Configs.
In one example, the UE, wherein the determined maximum code rate for the low priority HARQ-ACK is based on a PUCCH-Config for ultra-reliable low-latency communication (URLLC) configured with two maximum code rates.
In one example, the UE, wherein the determined maximum code rate for the low priority HARQ-ACK is based on a beta offset value or coding rate ratio between uplink control information (UCI) of different priorities.
In one example, the UE, wherein the determined maximum code rate for the low priority HARQ-ACK is based on an offset value for a maxCodeRate index configured between URLLC and enhanced mobile broadband (eMBB).
In one example, the UE, wherein the determined maximum code rate for the low priority HARQ-ACK is based on a configured maxCodeRate for low priority UCI multiplexing on high priority PUCCH.
In one example, the UE, wherein the determined maximum code rate for the low priority HARQ-ACK is based on a number of Physical Resource Blocks (PRBs) for UCIs of each priority, a maximum payload size for UCIs of each priority, or a payload size and an available number of PRBs.
In one example, a base station (gNB), comprising: a processor configured to: determine a maximum code rate for a low priority hybrid automatic repeat request-acknowledgement (HARQ-ACK) that is multiplexed with a high priority HARQ-ACK on a physical uplink control channel (PUCCH), the low priority HARQ-ACK having a separate code rate than the high priority HARQ-ACK; and receiving circuitry configured to receive multiplexed HARQ-ACK on the PUCCH, the low priority HARQ-ACK and the high priority HARQ-ACK being multiplexed based on the determined maximum code rate for the low priority HARQ-ACK.
In one example, the gNB, wherein the determined maximum code rate for the low priority HARQ-ACK is based on a configuration in PUCCH-Configs.
In one example, the gNB, wherein the determined maximum code rate for the low priority HARQ-ACK is based on a power control parameter in a PUCCH-Configs.
In one example, the gNB, wherein the determined maximum code rate for the low priority HARQ-ACK is based on a PUCCH-Config for ultra-reliable low-latency communication (URLLC) configured with two maximum code rates.
In one example, the gNB, wherein the determined maximum code rate for the low priority HARQ-ACK is based on a beta offset value or coding rate ratio between uplink control information (UCI) of different priorities.
In one example, the gNB, wherein the determined maximum code rate for the low priority HARQ-ACK is based on an offset value for a maxCodeRate index configured between URLLC and enhanced mobile broadband (eMBB).
In one example, the gNB, wherein the determined maximum code rate for the low priority HARQ-ACK is based on a configured maxCodeRate for low priority UCI multiplexing on high priority PUCCH.
In one example, the gNB, wherein the determined maximum code rate for the low priority HARQ-ACK is based on a number of Physical Resource Blocks (PRBs) for UCIs of each priority, a maximum payload size for UCIs of each priority, or a payload size and an available number of PRBs.
In one example, a method by a user equipment (UE), comprising: determining a maximum code rate for a low priority hybrid automatic repeat request-acknowledgement (HARQ-ACK) that is multiplexed with a high priority HARQ-ACK on a physical uplink control channel (PUCCH), the low priority HARQ-ACK having a separate code rate than the high priority HARQ-ACK; multiplexing the low priority HARQ-ACK and the high priority HARQ-ACK based on the determined maximum code rate for the low priority HARQ-ACK; and transmitting the multiplexed HARQ-ACK on the PUCCH.
In one example, a method by a base station (gNB), comprising: determining a maximum code rate for a low priority hybrid automatic repeat request-acknowledgement (HARQ-ACK) that is multiplexed with a high priority HARQ-ACK on a physical uplink control channel (PUCCH), the low priority HARQ-ACK having a separate code rate than the high priority HARQ-ACK; and receiving multiplexed HARQ-ACK on the PUCCH, the low priority HARQ-ACK and the high priority HARQ-ACK being multiplexed based on the determined maximum code rate for the low priority HARQ-ACK.
In one example, a user equipment (UE), comprising: a processor configured to: determine a maximum code rate for a low priority hybrid automatic repeat request-acknowledgement (HARQ-ACK) that is multiplexed with a high priority HARQ-ACK on a high priority physical uplink control channel (PUCCH), the low priority HARQ-ACK having a separate code rate than the high priority HARQ-ACK, and separately code and multiplex the high priority HARQ-ACK and the low priority HARQ-ACK based on a maximum code rate for the high priority HARQ-ACK and the determined maximum code rate for the low priority HARQ-ACK respectively; and transmitting circuitry configured to transmit the multiplexed HARQ-ACK on the PUCCH.
In one example, the UE, wherein the maximum code rate for the high priority HARQ-ACK is based on a maxCodeRate parameter in a configuration in the PUCCH-Config for priority index 1.
In one example, the UE, wherein the determined maximum code rate for the low priority HARQ-ACK is based on a maxCodeRate parameter in a configuration in the PUCCH-Config for priority index 0.
In one example, the UE, wherein the determined maximum code rate for the low priority HARQ-ACK is based on a power control parameter in a PUCCH-Config.
In one example, the UE, wherein the determined maximum code rate for the low priority HARQ-ACK is based on a PUCCH-Config for priority index 1 configured with two maximum code rates.
In one example, the UE, wherein the determined maximum code rate for the low priority HARQ-ACK is based on a beta offset value or coding rate ratio between uplink control information (UCI) of different priorities.
In one example, the UE, wherein the determined maximum code rate for the low priority HARQ-ACK is based on an offset value for a maxCodeRate index configured between high priority UCI and low priority UCI.
In one example, the UE, wherein the determined maximum code rate for the low priority HARQ-ACK is based on a configured maxCodeRate for low priority UCI multiplexing on high priority PUCCH.
In one example, the UE, wherein the determined maximum code rate for the low priority HARQ-ACK is based on a number of Physical Resource Blocks (PRBs) for UCIs of each priority, a maximum payload size for UCIs of each priority, or a payload size and an available number of PRBs.
In one example, a base station (gNB), comprising: a processor configured to: determine a maximum code rate for a low priority hybrid automatic repeat request-acknowledgement (HARQ-ACK) that is multiplexed with a high priority HARQ-ACK on a high priority physical uplink control channel (PUCCH), the low priority HARQ-ACK having a separate code rate than the high priority HARQ-ACK; and receiving circuitry configured to receive multiplexed HARQ-ACK on the PUCCH, the high priority HARQ-ACK and the low priority HARQ-ACK being separately coded and multiplexed based on a maximum code rate for the high priority HARQ-ACK and the determined maximum code rate for the low priority HARQ-ACK respectively.
In one example, the gNB, wherein the maximum code rate for the high priority HARQ-ACK is based on a maxCodeRate parameter in a configuration in the PUCCH-Config for priority index 1.
In one example, the gNB, wherein the determined maximum code rate for the low priority HARQ-ACK is based on a maxCodeRate parameter in a configuration in the PUCCH-Configs for priority index 0.
In one example, the gNB, wherein the determined maximum code rate for the low priority HARQ-ACK is based on a power control parameter in a PUCCH-Configs.
In one example, the gNB, wherein the determined maximum code rate for the low priority HARQ-ACK is based on a PUCCH-Config for priority index 1 configured with two maximum code rates.
In one example, the gNB, wherein the determined maximum code rate for the low priority HARQ-ACK is based on a beta offset value or coding rate ratio between uplink control information (UCI) of different priorities.
In one example, the gNB, wherein the determined maximum code rate for the low priority HARQ-ACK is based on an offset value for a maxCodeRate index configured between high priority UCI and low priority UCI.
In one example, the gNB, wherein the determined maximum code rate for the low priority HARQ-ACK is based on a configured maxCodeRate for low priority UCI multiplexing on high priority PUCCH.
In one example, the gNB, wherein the determined maximum code rate for the low priority HARQ-ACK is based on a number of Physical Resource Blocks (PRBs) for UCIs of each priority, a maximum payload size for UCIs of each priority, or a payload size and an available number of PRBs.
In one example, a method by a user equipment (UE), comprising: determining a maximum code rate for a low priority hybrid automatic repeat request-acknowledgement (HARQ-ACK) that is multiplexed with a high priority HARQ-ACK on a high priority physical uplink control channel (PUCCH), the low priority HARQ-ACK having a separate code rate than the high priority HARQ-ACK; separate coding and multiplexing the high priority HARQ-ACK and the low priority HARQ-ACK based on a maximum code rate for the high priority HARQ-ACK and the determined maximum code rate for the low priority HARQ-ACK respectively; and transmitting the multiplexed HARQ-ACK on the PUCCH.
In one example, a method by a base station (gNB), comprising: determining a maximum code rate for a low priority hybrid automatic repeat request-acknowledgement (HARQ-ACK) that is multiplexed with a high priority HARQ-ACK on a high priority physical uplink control channel (PUCCH), the low priority HARQ-ACK having a separate code rate than the high priority HARQ-ACK; and receiving multiplexed HARQ-ACK on the PUCCH, the high priority HARQ-ACK and the low priority HARQ-ACK being separately coded and multiplexed based on a maximum code rate for the high priority HARQ-ACK and the determined maximum code rate for the low priority HARQ-ACK respectively.
This Nonprovisional application claims priority under 35 U.S.C. § 119 on provisional Application No. 63/061,765 on Aug. 5, 2020, the entire contents of which are hereby incorporated by reference.
| Filing Document | Filing Date | Country | Kind |
|---|---|---|---|
| PCT/JP2021/028887 | 8/4/2021 | WO |
| Number | Date | Country | |
|---|---|---|---|
| 63061765 | Aug 2020 | US |
