WO2021140351A1 - Appareil et son procédé de commande de multiplexage d'informations - Google Patents

Appareil et son procédé de commande de multiplexage d'informations Download PDF

Info

Publication number
WO2021140351A1
WO2021140351A1 PCT/IB2020/000048 IB2020000048W WO2021140351A1 WO 2021140351 A1 WO2021140351 A1 WO 2021140351A1 IB 2020000048 W IB2020000048 W IB 2020000048W WO 2021140351 A1 WO2021140351 A1 WO 2021140351A1
Authority
WO
WIPO (PCT)
Prior art keywords
pusch
uci
pucch
multiplexing
user equipment
Prior art date
Application number
PCT/IB2020/000048
Other languages
English (en)
Inventor
Hao Lin
Original Assignee
Orope France Sarl
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Orope France Sarl filed Critical Orope France Sarl
Priority to PCT/IB2020/000048 priority Critical patent/WO2021140351A1/fr
Publication of WO2021140351A1 publication Critical patent/WO2021140351A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/21—Control channels or signalling for resource management in the uplink direction of a wireless link, i.e. towards the network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/23—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal

Definitions

  • the present disclosure relates to the field of communication systems, and more particularly, to an apparatus (such as a user equipment (UE) and/or a base station) and a method for uplink control information (UCI) multiplexing in configured grant (CG)-physical uplink shared channel (PUSCH) and provide a good communication performance and high reliability.
  • an apparatus such as a user equipment (UE) and/or a base station
  • UCI uplink control information
  • CG configured grant
  • PUSCH physical uplink shared channel
  • a network can configure that uplink control information (UCI) is multiplexed in a configured grant (CG)-physical uplink shared channel (PUSCH) in the case where allocated physical uplink control channel (PUCCH) resources (expected to carry UCI) are overlapped with the CG-PUSCH.
  • CG-PUSCHs are consecutive in a time domain and one CG-slot can have multiple CG-PUSCHs. Since the PUCCH resources are separately configured, it is possible that in some cases, the PUCCH resources are partially overlapped with more than one CG-PUSCH. In this situation a UE behavior for UCI multiplexing is an open problem.
  • an apparatus such as a user equipment (UE) and/or a base station
  • a method for uplink control information (UCI) multiplexing in configured grant (CG)-physical uplink shared channel (PUSCH) which can provide a UE behavior for UCI multiplexing in CG-PUSCH, a good communication performance, and high reliability.
  • An object of the present disclosure is to propose an apparatus (such as a user equipment (UE) and/or a base station) and a method for uplink control information (UCI) multiplexing in configured grant (CG)-physical uplink shared channel (PUSCH), which can provide a UE behavior for UCI multiplexing in CG-PUSCH, a good communication performance, and high reliability.
  • UE user equipment
  • PUSCH configured grant-physical uplink shared channel
  • a user equipment for control information multiplexing in includes a memory, a transceiver, and a processor coupled to the memory and the transceiver.
  • the processor is configured to: control the transceiver to receive an uplink control information (UCI) multiplexing configuration and a configured grant (CG)-physical uplink shared channel (PUSCH) resource configuration, determine physical uplink control channel (PUCCH) resources, and process UCI multiplexing in a selected PUSCH based on the UCI multiplexing configuration, the CG-PUSCH resource configuration, and the PUCCH resources.
  • UCI uplink control information
  • CG configured grant
  • PUSCH physical uplink control channel
  • a method for control information multiplexing of a user equipment includes receiving an uplink control information (UCI) multiplexing configuration and a configured grant (CG)-physical uplink shared channel (PUSCH) resource configuration, determining physical uplink control channel (PUCCH) resources, and processing UCI multiplexing in a selected PUSCH based on the UCI multiplexing configuration, the CG-PUSCH resource configuration, and the PUCCH resources.
  • UCI uplink control information
  • PUSCH configured grant
  • PUCCH physical uplink control channel
  • a base station for control information multiplexing includes a memory, a transceiver, and a processor coupled to the memory and the transceiver.
  • the processor is configured to: configure an uplink control information (UCI) multiplexing configuration and a configured grant (CG)-physical uplink shared channel (PUSCH) resource configuration, allocate physical uplink control channel (PUCCH) resources, and control the transceiver to receive, from a user equipment (UE), UCI multiplexing in a selected PUSCH based on the UCI multiplexing configuration, the CG-PUSCH resource configuration, and the PUCCH resources.
  • UCI uplink control information
  • CG configured grant
  • PUSCH physical uplink control channel
  • a method for control information multiplexing of a base station includes configuring an uplink control information (UCI) multiplexing configuration and a configured grant (CG)-physical uplink shared channel (PUSCH) resource configuration, allocating physical uplink control channel (PUCCH) resources, and receiving, from a user equipment (UE), UCI multiplexing in a selected PUSCH based on the UCI multiplexing configuration, the CG-PUSCH resource configuration, and the PUCCH resources.
  • UCI uplink control information
  • CG configured grant
  • PUSCH physical uplink control channel
  • a non-transitory machine-readable storage medium has stored thereon instructions that, when executed by a computer, cause the computer to perform the above method.
  • a chip includes a processor, configured to call and run a computer program stored in a memory, to cause a device in which the chip is installed to execute the above method.
  • a computer readable storage medium in which a computer program is stored, causes a computer to execute the above method.
  • a computer program product includes a computer program, and the computer program causes a computer to execute the above method.
  • a computer program causes a computer to execute the above method.
  • FIG. 1 is a block diagram of a user equipment (UE) and a network (e.g., gNB) for uplink control information (UCI) multiplexing in configured grant (CG)-physical uplink shared channel (PUSCH) in a communication network system according to an embodiment of the present disclosure.
  • UE user equipment
  • gNB network for uplink control information (UCI) multiplexing in configured grant (CG)-physical uplink shared channel (PUSCH) in a communication network system according to an embodiment of the present disclosure.
  • CG configured grant
  • PUSCH physical uplink shared channel
  • FIG. 2 is a flowchart illustrating a method for control information multiplexing of a UE according to an embodiment of the present disclosure.
  • FIG. 3 is a flowchart illustrating a method for control information multiplexing of a base station according to an embodiment of the present disclosure.
  • FIG. 4 is a flowchart illustrating a method for uplink control information (UCI) multiplexing in configured grant (CG)-physical uplink shared channel (PUSCH) of a UE according to an embodiment of the present disclosure.
  • UCI uplink control information
  • CG configured grant
  • PUSCH physical uplink shared channel
  • FIG. 5 is a flowchart illustrating a method for uplink control information (UCI) multiplexing in configured grant (CG)-physical uplink shared channel (PUSCH) of a base station according to an embodiment of the present disclosure.
  • UCI uplink control information
  • CG configured grant
  • PUSCH physical uplink shared channel
  • FIG. 6 is a schematic diagram illustrating an example for providing a UE behavior for UCI multiplexing in CG-PUSCH according to an embodiment of the present disclosure.
  • FIG. 7 is a schematic diagram illustrating an example for providing a UE behavior for UCI multiplexing in CG-PUSCH according to an embodiment of the present disclosure.
  • FIG. 8 is a schematic diagram illustrating an example for providing a UE behavior for UCI multiplexing in CG-PUSCH according to an embodiment of the present disclosure.
  • FIG. 9 is a schematic diagram illustrating an example for providing a UE behavior for UCI multiplexing in CG-PUSCH according to an embodiment of the present disclosure.
  • FIG. 10 is a schematic diagram illustrating an example for providing a UE behavior for UCI multiplexing in CG-PUSCH according to an embodiment of the present disclosure.
  • FIG. 11 is a schematic diagram illustrating an example for providing a UE behavior for UCI multiplexing in CG-PUSCH according to an embodiment of the present disclosure.
  • FIG. 12 is a schematic diagram illustrating an example for providing a UE behavior for UCI multiplexing in CG-PUSCH according to an embodiment of the present disclosure.
  • FIG. 13 is a block diagram of a system for wireless communication according to an embodiment of the present disclosure.
  • the unlicensed spectrum is a shared spectrum. Communication equipment in different communication systems can use the spectrum if it meets regulatory requirements set by a country or region on the spectrum and does not need to apply for a proprietary spectrum authorization from the government.
  • the communication device follows the principle of “listen before talk (LBT)”, that is, a device needs to perform channel sensing before transmitting a signal on a channel. Only when an LBT outcome shows that the channel is idle, the device can perform signal transmission; otherwise, the device cannot perform signal transmission.
  • LBT listen before talk
  • MCOT maximum channel occupancy time
  • a base station On an unlicensed carrier, for channel occupation time obtained by a base station, it may share the channel occupation time to a user equipment (UE) for transmitting an uplink signal or an uplink channel.
  • UE user equipment
  • the base station shares its own channel occupancy time with the UE, the UE can use an LBT mode with higher priority than that used by the UE itself to obtain the channel, thereby obtaining the channel with greater probability.
  • Embodiments of the present disclosure provide an apparatus (such as a user equipment (UE) and/or a base station) and a method for uplink control information (UCI) multiplexing in configured grant (CG)-physical uplink shared channel (PUSCH), which can provide a UE behavior for UCI multiplexing in CG-PUSCH, a good communication performance, and high reliability.
  • FIG. 1 illustrates that, in some embodiments, a user equipment (UE) 10 and a network (e.g., gNB) 20 for uplink control information (UCI) multiplexing in configured grant (CG)-physical uplink shared channel (PUSCH) in a communication network system 30 according to an embodiment of the present disclosure are provided.
  • a network e.g., gNB
  • the communication network system 30 includes the UE 10 and the network 20.
  • the UE 10 may include a memory 12, a transceiver 13, and a processor 11 coupled to the memory 12, the transceiver 13.
  • the network 20 may include a memory 22, a transceiver 23, and a processor 21 coupled to the memory 22, the transceiver 23.
  • the processor 11 or 21 may be configured to implement proposed functions, procedures and/or methods described in this description. Layers of radio interface protocol may be implemented in the processor 11 or 21.
  • the memory 12 or 22 is operatively coupled with the processor 11 or 21 and stores a variety of information to operate the processor 11 or 21.
  • the transceiver 13 or 23 is operatively coupled with the processor 11 or 21, and the transceiver 13 or 23 transmits and/or receives a radio signal.
  • the processor 11 or 21 may include application-specific integrated circuit (ASIC), other chipset, logic circuit and or data processing device.
  • the memory 12 or 22 may include read-only memory (ROM), random access memory (RAM), flash memory, memory card, storage medium and or other storage device.
  • the transceiver 13 or 23 may include baseband circuitry to process radio frequency signals.
  • modules e.g., procedures, functions, and so on
  • the modules can be stored in the memory 12 or 22 and executed by the processor 11 or 21.
  • the memory 12 or 22 can be implemented within the processor 11 or 21 or external to the processor 11 or 21 in which case those can be communicatively coupled to the processor 11 or 21 via various means as is known in the art.
  • the processor 11 is configured to: control the transceiver 13 to receive an uplink control information (UCI) multiplexing configuration and a configured grant (CG)-physical uplink shared channel (PUSCH) resource configuration, determine physical uplink control channel (PUCCH) resources, and process UCI multiplexing in a selected PUSCH based on the UCI multiplexing configuration, the CG-PUSCH resource configuration, and the PUCCH resources.
  • UCI uplink control information
  • CG configured grant
  • PUSCH configured grant
  • PUCCH physical uplink control channel
  • processing of the UCI multiplexing in the selected PUSCH satisfies the following: the UCI multiplexing configuration enables the UCI multiplexing in the selected PUSCH.
  • processing of the UCI multiplexing in the selected PUSCH satisfies the following: the PUCCH resources are fully overlapped or partially overlapped with the selected PUSCH.
  • processing of the UCI multiplexing in the selected PUSCH satisfies the following: the selected PUSCH is a transmit PUSCH.
  • the UE has data to transmit in the selected PUSCH.
  • processing of the UCI multiplexing in the selected PUSCH satisfies the following: the selected PUSCH satisfies a processing time. In some embodiments, processing of the UCI multiplexing in the selected PUSCH satisfies any of the above conditions or a combination thereof.
  • the processing time comprise a first predefined time, and the first predefined time is less than a time duration between a last symbol of a physical downlink shared channel (PDSCH) and a first symbol of the selected PUSCH; and/or the processing time comprise a second predefined time, and the second predefined time is less than a time duration between a last symbol of a DCI and a first symbol of the selected PUSCH; and/or the processing time comprise a third predefined time, and the third predefined time is less than a time duration between a last symbol of a channel state information reference signal (CSI-RS) and a first symbol of the selected PUSCH.
  • CSI-RS channel state information reference signal
  • the processing time comprises at least one of a processing time for decoding the selected PUSCH, a processing time for decoding the DCI, a processing time for preparing a UCI and the selected PUSCH, and a processing time for a CSI measurement.
  • the UCI multiplexing configuration comprises a radio resource control (RRC) parameter, and the RRC parameter is used for enabling or disabling the UCI multiplexing in the selected PUSCH.
  • RRC radio resource control
  • the CG-PUSCH resource configuration comprises an RRC configuration about CG-PUSCH resource allocation.
  • the CG-PUSCH resource configuration comprises an RRC configuration and a downlink control indicator (DCI) indication about CG-PUSCH resource allocation.
  • DCI downlink control indicator
  • the PUSCH resource configuration has a part in RRC and a part in DCI.
  • the PUCCH resources are configured to report hybrid automatic repeat request (HARQ)-acknowledgement (ACK).
  • the PUCCH resources are configured to report uplink control information as channel state information (CSI).
  • the PUCCH resources are configured to report AN feedback for semi-persistent scheduled PDSCH (SPS-PDSCH).
  • the PUCCH resources are indicated by DCI or an RRC signaling.
  • a determined PUCCH is overlapped with more than one selected PUSCH.
  • a UCI is multiplexed in an earliest PUSCH or a last PUSCH of the more than one selected PUSCH.
  • PUCCH is used to transmit HARQ-ACK.
  • the PUCCH can be scheduled by DCI, or PUCCH can be periodic.
  • PUCCH is used to transmit AN feedback for SPS-PDSCH.
  • PUCCH can be scheduled by DCI or PUCCH can be periodic.
  • PUCCH is used to transmit HARQ-ACK.
  • PUCCH can be scheduled by DCI or PUCCH can be periodic.
  • PUCCH resources are indicated by DCI.
  • PUCCH resources are indicated by RRC. In this case, no DCI scheduling is required.
  • the PUCCH needs to maintain a period consistent with the PDSCH according to the RRC instruction. That is, PUCCH has periodicity. PUCCH and PUSCH maintain consistent periods.
  • PUCCH can transmit HARQ-ACK or CSI.
  • a listen before talk (LBT) is performed after processing of the UCI multiplexing in the selected PUSCH. In some embodiments, if the LBT fails, the UCI multiplexing is performed in a new selected PUSCH. In some embodiments, the new selected PUSCH is a next one of the selected PUSCH or a last PUSCH of more than one selected PUSCH.
  • the CG-PUSCH resource configuration provides a first PUSCH and a second PUSCH, and when a PUCCH repetition is enabled, a first PUCCH and a second PUCCH are repeated.
  • the first PUCCH corresponds to the first PUSCH
  • the second PUCCH corresponds to the second PUSCH
  • the first PUSCH and the second PUSCH are different
  • a UCI is multiplexed in the first PUSCH and the second PUSCH, respectively
  • the first PUSCH and the second PUSCH are used as selected PUSCHs.
  • the first PUCCH corresponds to the first PUSCH
  • the second PUCCH corresponds to the second PUSCH
  • the first PUSCH and the second PUSCH are same.
  • a UCI is multiplexed twice in the first PUSCH, and the first PUSCH is used as the selected PUSCH.
  • a UCI is multiplexed once in the first PUSCH, and the first PUSCH is used as the selected PUSCH.
  • a UCI is transmitted on the first PUCCH and the second PUCCH, respectively.
  • the first PUCCH corresponds to the first PUSCH
  • the second PUCCH has no corresponding PUSCH.
  • a UCI is multiplexed in the first PUSCH, and the first PUSCH is used as the selected PUSCH. In some embodiments, a UCI is multiplexed in the first PUSCH, and the UCI is transmitted separately on the second PUCCH, and the first PUSCH is used as the selected PUSCH. In some embodiments, the UCI is transmitted on the first PUCCH and the second PUCCH, respectively.
  • the first PUSCH and the second PUSCH are selected in the same manner as above, that is, any one of the following conditions or a combination thereof needs to be satisfied. If there are multiple optional first PUSCHs or multiple optional second PUSCHs, the earliest one is selected.
  • the following conditions comprise the followings: the UCI multiplexing configuration enables the UCI multiplexing in the selected PUSCH, the PUCCH resources are fully overlapped or partially overlapped with the selected PUSCH, the selected PUSCH is a transmit PUSCH, and the selected PUSCH satisfies the above processing time.
  • the processor 11 is configured to: control the transceiver 13 to receive a UCI multiplexing configuration (UCI config) and a CG-PUSCH resource configuration (CG config), determine physical uplink control channel (PUCCH) resources (PUC res), and process UCI multiplexing based on the UCI multiplexing configuration, the CG-PUSCH resource configuration, and the PUCCH resources, such that: if the UCI multiplexing configuration enables the UCI multiplexing in a CG-PUSCH, if the determined PUCCH resources are fully overlapped or partially overlapped with the CG-PUSCH, and if an overlapped CG-PUSCH is a transmit PUSCH, then the processor 11 multiplexes UCI from a determined PUCCH to the overlapped CG-PUSCH, otherwise, the processor 11 skips the overlapped CG-PUSCH and transmits the UCI in the determined PUCCH. This can provide a UE behavior for UCI multiplexing in CG-PUSCH.
  • UCI config UCI
  • the processor 21 is configured to: configure a UCI multiplexing configuration and a CG-PUSCH resource configuration; allocate physical uplink control channel (PUCCH) resources; and control the transceiver 23 to receive, from a user equipment (UE), UCI multiplexing based on the UCI multiplexing configuration, the CG-PUSCH resource configuration, and the PUCCH resources, such that: if the UCI multiplexing configuration enables the UCI multiplexing in a CG-PUSCH, if determined PUCCH resources are fully overlapped or partially overlapped with the CG-PUSCH, and if an overlapped CG-PUSCH is a transmit PUSCH, then the UE multiplexes UCI from a determined PUCCH to the overlapped CG-PUSCH; otherwise, the UE skips the overlapped CG-PUSCH and transmits the UCI in the determined PUCCH. This can provide a UE behavior for UCI multiplexing in CG-PUSCH.
  • PUCCH physical uplink control channel
  • the UCI multiplexing configuration is a radio resource control (RRC) parameter to enable or disable the UCI multiplexing with the CG-PUSCH.
  • the CG-PUSCH resource configuration is an RRC configuration and/or a downlink control indicator (DCI) indication about CG-PUSCH resource allocation.
  • the PUCCH resources are determined by a physical downlink shared channel (PDSCH) assignment downlink control indicator (DCI) to report hybrid automatic repeat request (HARQ)-acknowledgement (ACK) or determined by a periodic PUCCH resource to be configured to report uplink control information as channel state information.
  • PDSCH physical downlink shared channel
  • DCI hybrid automatic repeat request
  • ACK hybrid automatic repeat request
  • the given configured CG-PUSCH if the transceiver 13 uses the given configured CG-PUSCH to transmit data, the given configured CG-PUSCH is considered as a transmit PUSCH; while if the transceiver 13 does not use the given configured CG-PUSCH to transmit data, the given configured CG-PUSCH is not the transmit PUSCH.
  • the given transmit PUSCH is a multiplexable transmit PUSCH.
  • the processing timeline comprises at least one of a processing time for decoding the given transmit PUSCH, a processing time for decoding a DCI, a processing time for preparing a UCI and the given transmit PUSCH, and a processing time for a channel state information (CSI) measurement.
  • CSI channel state information
  • the processing timeline comprises a processing time for decoding the given transmit PUSCH, and/or a processing time for decoding a DCI, and/or a processing time for preparing a UCI and the given transmit PUSCH, and or a processing time for a channel state information (CSI) measurement.
  • CSI channel state information
  • the given transmit PUSCH satisfying the processing timeline comprises at least one of the following: a time duration between a latest PDSCH, whose AN feedback is reported in a multiplexed UCI, and the given transmit PUSCH is beyond a first predefined minimum processing time (Nl), a time duration between a latest DCI that assigns the latest PDSCH and the given transmit PUSCH is beyond a second predefined minimum processing time (N2), and a time duration between a latest reference signal, on which the processor measures a CSI and reports the CSI in the multiplexed UCI, and the given transmit PUSCH is beyond a third predefined minimum processing time (N3).
  • the given transmit PUSCH satisfying the processing timeline comprises a time duration between a latest PDSCH, whose AN feedback is reported in a multiplexed UCI, and the given transmit PUSCH is beyond a first predefined minimum processing time (Nl), and/or a time duration between a latest DCI that assigns the latest PDSCH and the given transmit PUSCH is beyond a second predefined minimum processing time (N2), and/or a time duration between a latest reference signal, on which the processor measures a CSI and reports the CSI in the multiplexed UCI, and the given transmit PUSCH is beyond a third predefined minimum processing time (N3).
  • Nl first predefined minimum processing time
  • N2 second predefined minimum processing time
  • N3 third predefined minimum processing time
  • a UCI when a determined PUCCH is overlapped with more than one mutilplexable transmit PUSCH, a UCI is multiplexed in an earliest multiplexable transmit PUSCH. In some embodiments, when a PUSCH that multiplexes the UCI cannot be transmitted due to a listen before talk (LBT) failure, the UCI is multiplexed in a next earliest mutiplexable transmit PUSCH.
  • LBT listen before talk
  • the CG-PUSCH resource configuration provides a first PUSCH and a second PUSCH, and when a PUCCH repetition is enabled, a UCI can be multiplexed in the CG-PUSCH if all repeated PUCCH resources can find multiplexable transmit PUSCHs; otherwise, the UCI is transmitted the UCI in in a PUCCH only and all transmit PUSCHs are skipped. In some embodiments, found multiplexable transmit PUSCHs are distinct.
  • FIG. 2 illustrates a method 200 for control information multiplexing of a UE according to an embodiment of the present disclosure.
  • the method 200 includes: a block 202, receiving an uplink control information (UCI) multiplexing configuration and a configured grant (CG)-physical uplink shared channel (PUSCH) resource configuration, a block 204, determining physical uplink control channel (PUCCH) resources, and a block 206, processing UCI multiplexing in a selected PUSCH based on the UCI multiplexing configuration, the CG-PUSCH resource configuration, and the PUCCH resources.
  • UCI uplink control information
  • PUSCH configured grant
  • PUCCH physical uplink control channel
  • FIG. 3 illustrates a method 300 for control information multiplexing of a base station according to an embodiment of the present disclosure.
  • the method 300 includes: a block 302, configuring an uplink control information (UCI) multiplexing configuration and a configured grant (CG)-physical uplink shared channel (PUSCH) resource configuration, a block 304, allocating physical uplink control channel (PUCCH) resources, and a block 306, and receiving, from a user equipment (UE), UCI multiplexing in a selected PUSCH based on the UCI multiplexing configuration, the CG-PUSCH resource configuration, and the PUCCH resources.
  • UCI uplink control information
  • PUSCH configured grant
  • PUCCH physical uplink control channel
  • the method 400 includes: a block 402, receiving a UCI multiplexing configuration and a CG-PUSCH resource configuration, a block 404, determining physical uplink control channel (PUCCH) resources, and a block 406, processing UCI multiplexing based on the UCI multiplexing configuration, the CG-PUSCH resource configuration, and the PUCCH resources, such that: if the UCI multiplexing configuration enables the UCI multiplexing in a CG-PUSCH, if determined PUCCH resources are fully overlapped or partially overlapped with the CG-PUSCH, and if an overlapped CG-PUSCH is a transmit PUSCH, then the user equipment multiplexes UCI from a determined PUCCH to the overlapped CG-PUSCH, otherwise, the user equipment skips the overlapped CG-PU
  • FIG. 5 illustrates a method 500 for uplink control information (UCI) multiplexing in configured grant (CG)-physical uplink shared channel (PUSCH) of a base station according to an embodiment of the present disclosure.
  • the method 500 includes: a block 502, configuring a UCI multiplexing configuration and a CG-PUSCH resource configuration, a block 504, allocating physical uplink control channel (PUCCH) resources, and a block 506, receiving, from a user equipment (UE), UCI multiplexing based on the UCI multiplexing configuration, the CG-PUSCH resource configuration, and the PUCCH resources, such that: if the UCI multiplexing configuration enables the UCI multiplexing in a CG-PUSCH, if determined PUCCH resources are fully overlapped or partially overlapped with the CG-PUSCH, and if an overlapped CG-PUSCH is a transmit PUSCH, then the UE multiplexes UCI from a determined PUCCH to the overlapped CG-PUSCH
  • processing of the UCI multiplexing in the selected PUSCH satisfies the following: the UCI multiplexing configuration enables the UCI multiplexing in the selected PUSCH.
  • processing of the UCI multiplexing in the selected PUSCH satisfies the following: the PUCCH resources are fully overlapped or partially overlapped with the selected PUSCH.
  • processing of the UCI multiplexing in the selected PUSCH satisfies the following: the selected PUSCH is a transmit PUSCH.
  • the UE has data to transmit in the selected PUSCH.
  • processing of the UCI multiplexing in the selected PUSCH satisfies the following: the selected PUSCH satisfies a processing time. In some embodiments, processing of the UCI multiplexing in the selected PUSCH satisfies any of the above conditions or a combination thereof.
  • the processing time comprise a first predefined time, and the first predefined time is less than a time duration between a last symbol of a physical downlink shared channel (PDSCH) and a first symbol of the selected PUSCH; and/or the processing time comprise a second predefined time, and the second predefined time is less than a time duration between a last symbol of a DCI and a first symbol of the selected PUSCH; and/or the processing time comprise a third predefined time, and the third predefined time is less than a time duration between a last symbol of a channel state information reference signal (CSI-RS) and a first symbol of the selected PUSCH.
  • CSI-RS channel state information reference signal
  • the processing time comprises at least one of a processing time for decoding the selected PUSCH, a processing time for decoding the DCI, a processing time for preparing a UCI and the selected PUSCH, and a processing time for a CSI measurement.
  • the UCI multiplexing configuration comprises a radio resource control (RRC) parameter, and the RRC parameter is used for enabling the UCI multiplexing in the selected PUSCH.
  • RRC radio resource control
  • the CG-PUSCH resource configuration comprises an RRC configuration about CG-PUSCH resource allocation.
  • the CG-PUSCH resource configuration comprises an RRC configuration and a downlink control indicator (DCI) indication about CG-PUSCH resource allocation.
  • DCI downlink control indicator
  • the PUSCH resource configuration has a part in RRC and a part in DCI.
  • the PUCCH resources are configured to report hybrid automatic repeat request (HARQ)-acknowledgement (ACK).
  • the PUCCH resources are configured to report uplink control information as channel state information (CSI).
  • the PUCCH resources are configured to report AN feedback for semi-persistent scheduled PDSCH (SPS-PDSCH).
  • the PUCCH resources are indicated by DCI or an RRC signaling.
  • a determined PUCCH is overlapped with more than one selected PUSCH.
  • a UCI is multiplexed in an earliest PUSCH or a last PUSCH of the more than one selected PUSCH.
  • PUCCH is used to transmit HARQ-ACK.
  • the PUCCH can be scheduled by DCI, or PUCCH can be periodic.
  • PUCCH is used to transmit AN feedback for SPS-PDSCH.
  • PUCCH can be scheduled by DCI or PUCCH can be periodic.
  • PUCCH is used to transmit HARQ-ACK.
  • PUCCH can be scheduled by DCI or PUCCH can be periodic.
  • PUCCH resources are indicated by DCI.
  • PUCCH resources are indicated by RRC. In this case, no DCI scheduling is required.
  • the PUCCH needs to maintain a period consistent with the PDSCH according to the RRC instruction. That is, PUCCH has periodicity. PUCCH and PUSCH maintain consistent periods.
  • PUCCH can transmit HARQ-ACK or CSI.
  • a listen before talk (LBT) is performed after processing of the UCI multiplexing in the selected PUSCH. In some embodiments, if the LBT fails, the UCI multiplexing is performed in a new selected PUSCH. In some embodiments, the new selected PUSCH is a next one of the selected PUSCH or a last PUSCH of more than one selected PUSCH.
  • the CG-PUSCH resource configuration provides a first PUSCH and a second PUSCH, and when a PUCCH repetition is enabled, a first PUCCH and a second PUCCH are repeated.
  • the first PUCCH corresponds to the first PUSCH
  • the second PUCCH corresponds to the second PUSCH
  • the first PUSCH and the second PUSCH are different
  • a UCI is multiplexed in the first PUSCH and the second PUSCH, respectively
  • the first PUSCH and the second PUSCH are used as selected PUSCHs.
  • the first PUCCH corresponds to the first PUSCH
  • the second PUCCH corresponds to the second PUSCH
  • the first PUSCH and the second PUSCH are same.
  • a UCI is multiplexed twice in the first PUSCH, and the first PUSCH is used as the selected PUSCH.
  • a UCI is multiplexed once in the first PUSCH, and the first PUSCH is used as the selected PUSCH.
  • a UCI is transmitted on the first PUCCH and the second PUCCH, respectively.
  • the first PUCCH corresponds to the first PUSCH
  • the second PUCCH has no corresponding PUSCH.
  • a UCI is multiplexed in the first PUSCH, and the first PUSCH is used as the selected PUSCH. In some embodiments, a UCI is multiplexed in the first PUSCH, and the UCI is transmitted separately on the second PUCCH, and the first PUSCH is used as the selected PUSCH. In some embodiments, the UCI is transmitted on the first PUCCH and the second PUCCH, respectively.
  • the first PUSCH and the second PUSCH are selected in the same manner as above, that is, any one of the following conditions or a combination thereof needs to be satisfied. If there are multiple optional first PUSCHs or multiple optional second PUSCHs, the earliest one is selected.
  • the UCI multiplexing configuration enables the UCI multiplexing in the selected PUSCH, the PUCCH resources are fully overlapped or partially overlapped with the selected PUSCH, the selected PUSCH is a transmit PUSCH, and the selected PUSCH satisfies the above processing time.
  • the UCI multiplexing configuration is a radio resource control (RRC) parameter to enable or disable the UCI multiplexing with the CG-PUSCH.
  • the CG-PUSCH resource configuration is an RRC configuration and/or a DCI indication about CG-PUSCH resource allocation.
  • the PUCCH resources are determined by a physical downlink shared channel (PDSCH) assignment downlink control indicator (DCI) to report hybrid automatic repeat request (HARQ)-acknowledgement (ACK) or determined by a periodic PUCCH resource to be configured to report uplink control information as channel state information (CSI) or AN feedback for semi-persistent scheduled PDSCH (SPS-PDSCH).
  • PDSCH physical downlink shared channel
  • DCI downlink control indicator
  • HARQ hybrid automatic repeat request
  • ACK hybrid automatic repeat request
  • ACK hybrid automatic repeat request-acknowledgement
  • CSI channel state information
  • SPS-PDSCH AN feedback for semi-persistent scheduled PDSCH
  • the given configured CG-PUSCH if the UE 10 uses the given configured CG-PUSCH to transmit data, the given configured CG-PUSCH is considered as a transmit PUSCH; while if the UE 10 does not use the given configured CG-PUSCH to transmit data, the given configured CG-PUSCH is not the transmit PUSCH.
  • the given transmit PUSCH if the given transmit PUSCH satisfies a processing timeline, the given transmit PUSCH is a multiplexable transmit PUSCH.
  • the processing timeline comprises at least one of a processing time for decoding the given transmit PUSCH, a processing time for decoding a DCI, a processing time for preparing a UCI and the given transmit PUSCH, and a processing time for a channel state information (CSI) measurement.
  • the processing timeline comprises a processing time for decoding the given transmit PUSCH, and or a processing time for decoding a DCI, and/or a processing time for preparing a UCI and the given transmit PUSCH, and or a processing time for a channel state information (CSI) measurement.
  • the given transmit PUSCH satisfying the processing timeline comprises at least one of the following: a time duration between a latest PDSCH, whose AN feedback is reported in a multiplexed UCI, and the given transmit PUSCH is beyond a first predefined minimum processing time (Nl), a time duration between a latest DCI that assigns the latest PDSCH and the given transmit PUSCH is beyond a second predefined minimum processing time (N2), and a time duration between a latest reference signal, on which the processor measures a CSI and reports the CSI in the multiplexed UCI, and the given transmit PUSCH is beyond a third predefined minimum processing time (N3).
  • the given transmit PUSCH satisfying the processing timeline comprises a time duration between a latest PDSCH, whose AN feedback is reported in a multiplexed UCI, and the given transmit PUSCH is beyond a first predefined minimum processing time (Nl), and or a time duration between a latest DCI that assigns the latest PDSCH and the given transmit PUSCH is beyond a second predefined minimum processing time (N2), and/or a time duration between a latest reference signal, on which the processor measures a CSI and reports the CSI in the multiplexed UCI, and the given transmit PUSCH is beyond a third predefined minimum processing time (N3).
  • Nl first predefined minimum processing time
  • N2 second predefined minimum processing time
  • N3 third predefined minimum processing time
  • a UCI when a determined PUCCH is overlapped with more than one mutilplexable transmit PUSCH, a UCI is multiplexed in an earliest multiplexable transmit PUSCH. In some embodiments, when a PUSCH that multiplexes the UCI cannot be transmitted due to a listen before talk (LBT) failure, the UCI is multiplexed in a next earliest mutiplexable transmit PUSCH.
  • LBT listen before talk
  • the CG-PUSCH resource configuration provides a first PUSCH and a second PUSCH, and when a PUCCH repetition is enabled, a UCI can be multiplexed in the CG-PUSCH if all repeated PUSCH resources can find multiplexable transmit PUSCHs; otherwise, the UCI is transmitted in a PUCCH only and all transmit PUSCHs are skipped. In some embodiments, found multiplexable transmit PUSCHs are distinct.
  • a multiplexable transmit PUSCH may refer to a PUSCH satisfying two conditions: 1) a UE has data to transmit on the PUSCH, and 2) the PUSCH satisfies the processing time in any one of embodiments.
  • a transmit PUSCH may refer to a PUSCH satisfying one condition: 1 ) a UE has data to transmit on the PUSCH.
  • FIG. 6 illustrates an example for providing a UE behavior for UCI multiplexing in CG-PUSCH according to an embodiment of the present disclosure.
  • FIG. 7 illustrates an example for providing a UE behavior for UCI multiplexing in CG-PUSCH according to an embodiment of the present disclosure.
  • COT channel occupancy time
  • the UE is configured with three CG-PUSCHs (PUSCH1-3) in one CG period. These CG-PUSCHs (PUSCH1-3) are consecutive and in slot 2. Moreover, the UE is scheduled by a DCI in slot 1 to receive a PDSCH, and its corresponding ACK/negative acknowledgement (NACK) feedback (in a more general term UCI) is scheduled in PUCCH resources in slot 2.
  • NACK ACK/negative acknowledgement
  • FIG. 6 illustrates that in some embodiments, if the PUCCH is partially overlapped with more than one CG-PUSCHs such as PUSCH1 and PUSCH2, the UE needs to select which one to multiplex the UCI.
  • PUCCH resources are overlapped with CG-PUSCH1 and CG-PUSCH2.
  • the UE needs to first check if the earliest CG-PUSCH (i.e. CG-PUSCH1) can satisfy a UE processing time condition.
  • a UE processing time condition is that if a time duration between the last symbol of PDSCH and the first symbol of the CG-PUSCH, in which UCI is about to be multiplexed, is greater than a pre-defined value Nl. If this condition can be satisfied, then the concerned CG-PUSCH can multiplex the UCI. It is assumed that CG-PUSCH1 can satisfy this condition, then CG-PUSCH1 will multiplex the UCI. If the condition cannot be satisfied, the UE will check if the next CG-PUSCH (i.e. CG-PUSCH2) can satisfy this condition, and so on.
  • FIG. 7 illustrates that in some embodiments, processing timeline N3 is a minimum processing time for the UE to measure a channel state information (CSI) and to prepare for a CSI reporting.
  • the PUCCH is not for hybrid automatic repeat request (HARQ)-acknowledgement (ACK) feedback but for CSI feedback.
  • PUCCH resources and channel state information reference signal (CSI-RS) resources can be periodically configured.
  • the processing timeline is a time duration between the CSI-RS, on which the UE measures the CSI and reports this CSI in the UCI, and the CG-PUSCH that intends to include the UCI. This means that the selected PUSCH is the one that the UE can have enough time for CSI measurement and CSI report preparation with regards to the configured CSI-RS.
  • FIG. 8 illustrates an example for providing a UE behavior for UCI multiplexing in CG-PUSCH according to an embodiment of the present disclosure.
  • FIG. 8 illustrates that in some embodiments, CG-PUSCH1 and CG-PUSCH2 are multiplexable transmit PUSCHs to PUCCH, UCI is multiplexed in the earliest multiplexable transmit PUSCH, i.e. PUSCH1. If PUSCH1 cannot be transmitted due to LBT failure, the UCI is then multiplexed in the next multiplexable transmit PUSCH, i.e. PUSCH2. In this example, similar to the previous example, where the PUCCH is overlapped with both CG-PUSCH1 and CG-PUSCH2. If the CG-PUSCH1 can satisfy the processing timeline and it is firstly considered for UCI multiplexing.
  • the UCI is multiplexed in CG-PUSCH2 and UE retries the LBT for CG-PUSCH2. This way, the UCI can be reported with multiple transmission occasions (i.e. multiple LBT opportunities). This can increase the probability for UCI to be reported to the gNB.
  • the UCI is multiplexed in the earliest multiplexable transmit PUSCH, if the PUSCH cannot be transmitted, the UCI is lost. It doesn't need to be multiplexed to the next upcoming multiplexable transmit PUSCH.
  • the UCI is multiplexed in the earliest multiplexable transmit PUSCH, if the PUSCH cannot be transmitted, the UCI can be multiplexed in the next upcoming multiplexable transmit PUSCH.
  • FIG. 9 illustrates an example for providing a UE behavior for UCI multiplexing in CG-PUSCH according to an embodiment of the present disclosure.
  • FIG. 10 illustrates an example for providing a UE behavior for UCI multiplexing in CG-PUSCH according to an embodiment of the present disclosure.
  • FIG. 11 illustrates an example for providing a UE behavior for UCI multiplexing in CG-PUSCH according to an embodiment of the present disclosure.
  • the CG-PUSCH resource configuration provides a first PUSCH and a second PUSCH, and when a PUCCH repetition is enabled, a first PUCCH and a second PUCCH are repeated.
  • the first PUCCH corresponds to the first PUSCH
  • the second PUCCH corresponds to the second PUSCH
  • the first PUSCH and the second PUSCH are different
  • a UCI is multiplexed in the first PUSCH and the second PUSCH, respectively
  • the first PUSCH and the second PUSCH are used as selected PUSCHs.
  • the first PUCCH corresponds to the first PUSCH
  • the second PUCCH corresponds to the second PUSCH
  • the first PUSCH and the second PUSCH are same.
  • a UCI is multiplexed twice in the first PUSCH, and the first PUSCH is used as the selected PUSCH.
  • a UCI is multiplexed once in the first PUSCH, and the first PUSCH is used as the selected PUSCH.
  • a UCI is transmitted on the first PUCCH and the second PUCCH, respectively.
  • the first PUCCH corresponds to the first PUSCH
  • the second PUCCH has no corresponding PUSCH.
  • a UCI is multiplexed in the first PUSCH, and the first PUSCH is used as the selected PUSCH. In some embodiments, a UCI is multiplexed in the first PUSCH, and the UCI is transmitted separately on the second PUCCH, and the first PUSCH is used as the selected PUSCH. In some embodiments, the UCI is transmitted on the first PUCCH and the second PUCCH, respectively.
  • FIG. 9 illustrates that in some embodiments, PUCCH repetition is configured, assuming PUCCHl and PUCCH2 are repeated PUCCHs in a slot.
  • UCIs are multiplexed in PUSCH1 and PUSCH3 as they are the earliest multiplexable transmit PUCHs for PUCCHl and PUCCH2, respectively.
  • the gNB might need to configure multiple PUCCH transmissions within a slot or cross multiple slots in order to increase time diversity leading to an enhanced coverage.
  • UE will multiplex UCI into these CG-PUSCHs (PUSCH1 , PUSCH2, and PUSCH3 in FIG. 9).
  • the multiplexing rule is similar to that presented in examples 1 and 2. If the processing timeline is satisfied, the UCI will be multiplexed in CG-PUSCH1 and CG-PUSCH3 (PUSCH1 and PUSCH3 in FIG. 9). If there is at least one PUCCH repetition that is not overlapped with the CG-PUSCH (for instance if UE does not intend to use CG-PUSCH3 or there does not exist CG-PUSCH3). The whole repeated PUCCH cannot be multiplexed with CG-PUSCH. In this situation, the UE will report the UCI only in PUCCH and will skip the CG-PUSCH transmission. This solution can keep a good UCI decoding performance.
  • FIG. 10 illustrates that in some embodiments, UCI cannot be multiplexed since PUCCH2 cannot find a multiplexable transmit PUSCH, thus UCI is transmitted in PUCCHl and PUCCH2, respectively. Moreover, PUSCH2 and PUSCH3 are skipped.
  • the second PUCCH2 is not overlapped with any CG-PUSCH, therefore, even all CG-PUSCH1-3 (PUSCH1, PUSCH2, and PUSCH3 in FIG. 10) are to be used by UE for data transmissions, the UCI cannot be multiplexed into CG-PUSCH. In this case, the UE skips the overlapped CG-PUSCH and will transmit PUCCH instead.
  • the UE can only use CG-PUSCH] for data transmission and skip CG-PUSCH2 and CG-PUSCH3.
  • FIG. 11 illustrates that in some embodiments, PUSCH3 is the only multiplexable transmit PUSCH for both PUCCHl and PUCCH2, thus UCI cannot be multiplexed since PUCCHl and PUCCH2 cannot find distinct multiplexable transmit PUSCH.
  • all the repeated PUCCHs are overlapped with CG-PUSCHs (PUSCH1, PUSCH2, and PUSCH3 in FIG. 11).
  • UCI in PUCCHl could have been multiplexed in CG-PUSCH2 and UCI in PUCCH2 could have been multiplexed in CG-PUSCH3.
  • the CG-PUSCH2 is not qualified to multiplex UCI due to the processing timeline violation. In this case the UCI in PUCCHl will have to be put in CG-PUSCH3, leaving no place for UCI in PUCCH2. In this case, this is not counted as repeated PUCCHs, which are overlapped with CG-PUSCHs.
  • FIG. 12 illustrates an example for providing a UE behavior for UCI multiplexing in CG-PUSCH according to an embodiment of the present disclosure.
  • FIG. 12 illustrates that in some embodiments, UCI multiplexing in inter-slot PUCCH repetition case.
  • PUCCH repetition is inter-slot, i.e. PUCCH are repeated cross slots.
  • the UCI can be multiplexed in those CG-PUSCHs.
  • FIG. 12 where PUCCHl and PUCCH2 are two repeated PUCCHs and they are overlapped with CG-PUSCH1, CG-PUSCH2 and CG-PUSCH4, CG-PUSCH5 (PUSCH1, PUSCH2, PUSCH4, and PUSCH5 in FIG. 12).
  • PUSCH1, PUSCH2, PUSCH4, and PUSCH5 in FIG. 12 It is assumed that the UE will use these PUSCHs (PUSCH1, PUSCH2, PUSCH4, and PUSCH5 in FIG. 12) to transmit data. Then UE will multiplex UCI into these CG-PUSCHs (PUSCH1, PUSCH2, PUSCH4, and PUSCH5 in FIG. 12).
  • Some embodiments of the present disclosure are used by 5G-NR chipset vendors, V2X communication system development vendors, automakers including cars, trains, trucks, buses, bicycles, moto-bikes, helmets, and etc., drones (unmanned aerial vehicles), smartphone makers, communication devices for public safety use, AR/VR device maker for example gaming, conference/seminar, education purposes.
  • Some embodiments of the present disclosure are a combination of “techniques/processes” that can be adopted in 3GPP specification to create an end product.
  • Some embodiments of the present disclosure could be adopted in the 5G NR unlicensed band communications.
  • Some embodiments of the present disclosure propose technical mechanisms.
  • FIG. 13 is a block diagram of an example system 700 for wireless communication according to an embodiment of the present disclosure. Embodiments described herein may be implemented into the system using any suitably configured hardware and/or software.
  • FIG. 13 illustrates the system 700 including a radio frequency (RF) circuitry 710, a baseband circuitry 720, an application circuitry 730, a memory/storage 740, a display 750, a camera 760, a sensor 770, and an input/output (EO) interface 780, coupled with each other at least as illustrated.
  • the application circuitry 730 may include a circuitry such as, but not limited to, one or more single-core or multi-core processors.
  • the processors may include any combination of general-purpose processors and dedicated processors, such as graphics processors, application processors.
  • the processors may be coupled with the me ory/storage and configured to execute instructions stored in the memory/storage to enable various applications and or operating systems running on the system.
  • the baseband circuitry 720 may include circuitry such as, but not limited to, one or more single-core or multi-core processors.
  • the processors may include a baseband processor.
  • the baseband circuitry may handle various radio control functions that enables communication with one or more radio networks via the RF circuitry.
  • the radio control functions may include, but are not limited to, signal modulation, encoding, decoding, radio frequency shifting, etc.
  • the baseband circuitry may provide for communication compatible with one or more radio technologies.
  • the baseband circuitry may support communication with an evolved universal terrestrial radio access network (EUTRAN) and/or other wireless metropolitan area networks (WMAN), a wireless local area network (WLAN), a wireless personal area network (WPAN).
  • EUTRAN evolved universal terrestrial radio access network
  • WMAN wireless metropolitan area networks
  • WLAN wireless local area network
  • WPAN wireless personal area network
  • Embodiments in which the baseband circuitry is configured to support radio communications of more than one wireless protocol may be referred to as multi-mode baseband circuit
  • the baseband circuitry 720 may include circuitiy to operate with signals that are not strictly considered as being in a baseband frequency.
  • baseband circuitry may include circuitry to operate with signals having an intermediate frequency, which is between a baseband frequency and a radio frequency.
  • the RF circuitry 710 may enable communication with wireless networks using modulated electromagnetic radiation through a non-solid medium.
  • the RF circuitry may include switches, filters, amplifiers, etc. to facilitate the communication with the wireless network.
  • the RF circuitry 710 may include circuitry to operate with signals that are not strictly considered as being in a radio frequency.
  • RF circuitry may include circuitry to operate with signals having an intermediate frequency, which is between a baseband frequency and a radio frequency.
  • the transmitter circuitry, control circuitry, or receiver circuitry discussed above with respect to the user equipment, eNB, or gNB may be embodied in whole or in part in one or more of the RF circuitry, the baseband circuitry, and/or the application circuitry.
  • “circuitry” may refer to, be part of, or include an Application Specific Integrated Circuit (ASIC), an electronic circuit, a processor (shared, dedicated, or group), and/or a memory (shared, dedicated, or group) that execute one or more software or firmware programs, a combinational logic circuit, and or other suitable hardware components that provide the described functionality.
  • ASIC Application Specific Integrated Circuit
  • the electronic device circuitry may be implemented in, or functions associated with the circuitry may be implemented by, one or more software or firmware modules.
  • some or all of the constituent components of the baseband circuitiy, the application circuitry, and/or the memory/storage may be implemented together on a system on a chip (SOC).
  • SOC system on a chip
  • the memory/storage 740 may be used to load and store data and or instructions, for example, for system.
  • the memory/storage for one embodiment may include any combination of suitable volatile memory, such as dynamic random access memory (DRAM)), and/or non-volatile memory, such as flash memory.
  • DRAM dynamic random access memory
  • flash memory non-volatile memory
  • the I/O interface 780 may include one or more user interfaces designed to enable user interaction with the system and/or peripheral component interfaces designed to enable peripheral component interaction with the system.
  • User interfaces may include, but are not limited to a physical keyboard or keypad, a touchpad, a speaker, a microphone, etc.
  • Peripheral component interfaces may include, but are not limited to, a non-volatile memory port, a universal serial bus (USB) port, an audio jack, and a power supply interface.
  • the sensor 770 may include one or more sensing devices to determine environmental conditions and or location information related to the system.
  • the sensors may include, but are not limited to, a gyro sensor, an accelerometer, a proximity sensor, an ambient light sensor, and a positioning unit.
  • the positioning unit may also be part of, or interact with, the baseband circuitry and/or RF circuitry to communicate with components of a positioning network, e.g., a global positioning system (GPS) satellite.
  • GPS global positioning system
  • the display 750 may include a display, such as a liquid crystal display and a touch screen display.
  • the system 700 may be a mobile computing device such as, but not limited to, a laptop computing device, a tablet computing device, a netbook, an ultrabook, a smartphone, a AR/VR glasses, etc.
  • system may have more or less components, and or different architectures.
  • methods described herein may be implemented as a computer program.
  • the computer program may be stored on a storage medium, such as a non-transitoiy storage medium.
  • the units as separating components for explanation are or are not physically separated.
  • the units for display are or are not physical units, that is, located in one place or distributed on a plurality of network units. Some or all of the units are used according to the purposes of the embodiments.
  • each of the functional units in each of the embodiments can be integrated in one processing unit, physically independent, or integrated in one processing unit with two or more than two units.
  • the software function unit is realized and used and sold as a product, it can be stored in a readable storage medium in a computer.
  • the technical plan proposed by the present disclosure can be essentially or partially realized as the form of a software product.
  • one part of the technical plan beneficial to the conventional technology can be realized as the form of a software product.
  • the software product in the computer is stored in a storage medium, including a plurality of commands for a computational device (such as a personal computer, a server, or a network device) to run all or some of the steps disclosed by the embodiments of the present disclosure.
  • the storage medium includes a USB disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a floppy disk, or other kinds of media capable of storing program codes.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

L'invention concerne un appareil et son procédé de multiplexage d'informations de commande capables de fournir un comportement d'UE pour un multiplexage d'informations de commande de liaison montante (UCI) dans un canal partagé de liaison montante physique (PUSCH) à octroi configuré. Le procédé de multiplexage d'informations de commande d'un équipement utilisateur (UE) consiste à recevoir une configuration de multiplexage d'informations de commande de liaison montante (UCI) et une configuration de ressources de canal partagé de liaison montante physique (PUSCH) à octroi partagé (CG), à déterminer des ressources de canal de commande de liaison montante physique (PUCCH), et à traiter un multiplexage d'UCI dans un PUSCH sélectionné d'après la configuration de multiplexage d'UCI, la configuration des ressources CG-PUSCH et les ressources PUCCH.
PCT/IB2020/000048 2020-01-08 2020-01-08 Appareil et son procédé de commande de multiplexage d'informations WO2021140351A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/IB2020/000048 WO2021140351A1 (fr) 2020-01-08 2020-01-08 Appareil et son procédé de commande de multiplexage d'informations

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/IB2020/000048 WO2021140351A1 (fr) 2020-01-08 2020-01-08 Appareil et son procédé de commande de multiplexage d'informations

Publications (1)

Publication Number Publication Date
WO2021140351A1 true WO2021140351A1 (fr) 2021-07-15

Family

ID=69903708

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/IB2020/000048 WO2021140351A1 (fr) 2020-01-08 2020-01-08 Appareil et son procédé de commande de multiplexage d'informations

Country Status (1)

Country Link
WO (1) WO2021140351A1 (fr)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20220038211A1 (en) * 2020-10-16 2022-02-03 Salvatore Talarico Repetition schemes for urllc operating in unlicensed spectrum
US20230239081A1 (en) * 2020-04-09 2023-07-27 Ofinno, Llc HARQ Feedback Collision in Unlicensed Bands
EP4192136A4 (fr) * 2020-08-05 2024-03-06 Samsung Electronics Co Ltd Procédé et dispositif pour prendre en charge un service urllc

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
ERICSSON: "On UCI Multiplexing on PUCCH", vol. RAN WG1, no. Busan, South Korea; 20180521 - 20180525, 20 May 2018 (2018-05-20), XP051442447, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/Meetings%5F3GPP%5FSYNC/RAN1/Docs/> [retrieved on 20180520] *
VIVO: "Feature lead summary on Configured grant enhancement", vol. RAN WG1, no. Chongqing, China; 20191014 - 20191020, 22 October 2019 (2019-10-22), XP051798593, Retrieved from the Internet <URL:https://ftp.3gpp.org/tsg_ran/WG1_RL1/TSGR1_98b/Docs/R1-1910559.zip R1-1910559 FL summary on NRU-CG.docx> [retrieved on 20191022] *

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20230239081A1 (en) * 2020-04-09 2023-07-27 Ofinno, Llc HARQ Feedback Collision in Unlicensed Bands
EP4192136A4 (fr) * 2020-08-05 2024-03-06 Samsung Electronics Co Ltd Procédé et dispositif pour prendre en charge un service urllc
US20220038211A1 (en) * 2020-10-16 2022-02-03 Salvatore Talarico Repetition schemes for urllc operating in unlicensed spectrum
US11996942B2 (en) * 2020-10-16 2024-05-28 Intel Corporation Repetition schemes for URLLC operating in unlicensed spectrum

Similar Documents

Publication Publication Date Title
US11490265B2 (en) Apparatus and method of processing collision between SSB transmission and periodic transmission
EP3844925A1 (fr) Équipement utilisateur, station de base, et procédé de communication de véhicule à tout correspondant
WO2021140351A1 (fr) Appareil et son procédé de commande de multiplexage d&#39;informations
US20230019570A1 (en) Apparatus and method of wireless communication
WO2021228203A1 (fr) Appareil et procédé de communication sans fil
US20230025005A1 (en) Apparatus and method of wireless communication
US20230107364A1 (en) Communication device and method of transmission of same
US20230125590A1 (en) User equipment and method for sharing periodic channel occupancy
US20230112171A1 (en) Apparatus and method of wireless communication
EP3977795B1 (fr) Appareil et procédé de communication sans fil
US20230140467A1 (en) Apparatus and method of wireless communication
US20230337224A1 (en) Method for handling high-priority uplink transmissions and user equipment
US20230023518A1 (en) Apparatus and method of communication of same
US20230087543A1 (en) Methods for wireless communication, ue, and base station
WO2021228201A1 (fr) Appareil et procédé de communication sans fil
WO2023052806A1 (fr) Appareil et procédé de communication sans fil de multiples canaux physiques partagés de liaison descendante, pdsch
WO2021110109A1 (fr) Appareil et procédé de communication sans fil
WO2023012490A1 (fr) Appareil et procédé de communication sans fil
US20220408463A1 (en) User equipment and method of communication of same
US20220385417A1 (en) Apparatus and method of communication of same
WO2022148982A1 (fr) Appareil et procédé de communication sans fil
EP4085554A1 (fr) Équipement utilisateur et son procédé de rétroaction de demande de répétition automatique hybride unique

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 20713082

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 11/10/2022)

122 Ep: pct application non-entry in european phase

Ref document number: 20713082

Country of ref document: EP

Kind code of ref document: A1