PUCCH repetition number indication

Abstract

Methods and apparatuses for indicating a number of repetitions of a PUCCH are disclosed. A base unit includes a transmitter that transmits a configuration containing an indication of a number of repetitions of a PUCCH, wherein the configuration is determined according to a type of UCI carried in the PUCCH; and a receiver that receives the PUCCH repeatedly with the number of repetitions.

Description

TECHNICAL FIELD

[0001] The subject matter disclosed herein relates to wireless communications, and more particularly, to methods and apparatuses for indicating a number of repetitions of a PUCCH. BACKGROUND

[0002] The following abbreviations are defined herein, at least some of which are mentioned throughout the description: Third Generation Partnership Project (3GPP), Long Term Evolution (LTE), New Radio (NR), Very Large Scale Integration (VLSI), Random Access Memory (RAM), Read Only Memory (ROM), Erasable Programmable Read Only Memory (EPROM or Flash memory), Compact Disc Read Only Memory (CD-ROM), Local Area Network (LAN), Wide Area Network (WAN), user equipment (UE), uplink (UL), Evolved Node B (eNB), Next Generation Node B (gNB), downlink (DL), central processing unit (CPU), graphics processing unit (GPU), field programmable gate array (FPGA), dynamic RAM (DRAM), radio resource control (RRC), user entity / equipment (mobile terminal) (UE), physical downlink shared channel (PDSCH), physical uplink shared channel (PUSCH), physical uplink control channel (PUCCH), downlink control information (DCI), transmission reception point (TRP), multi-TRP (multi-TRP or M-TRP), frequency range 2 (FR2), channel state information (CSI), CSI-RS resource indicator (CRI), transmission configuration indication (TCI), sounding reference signal (SRS), control resource set (CORESET), synchronization signal (SS), reference signal (RS), uplink control information (UCI), medium access control (MAC), control element (CE), scheduling request (SR), hybrid automatic repeat request (HARQ), hybrid automatic repeat request acknowledgement (HARQ-ACK), semi-persistent scheduling (SPS), technical specification (TS), semi-persistent (SP), bandwidth part (BWP), ultra-reliable and low-latency communication (URLLC).

[0003] UCI repetition with multiple beams in multiple slots can leverage the spatial diversity of multiple beams of PUCCH transmission to increase the reliability and robustness of UCI transmission. However, in NR Rel-15, the number of repetitions of PUCCH is configured per PUCCH format. In addition, only long PUCCH resources of formats 1, 3, or 4 can be configured to be transmitted repeatedly (i.e., transmitted by a number of repetitions). For example, for PUCCH format 1, 3, or 4, a UE can be configured with a number of slots nrofSlots for PUCCH transmission repetition. The UE transmits the PUCCH in each of the nrofSlots slots. The PUCCH is transmitted repeatedly in the nrofSlots slots. The number of repetitions of PUCCH is indicated by nrofSlots for PUCCH transmission repetition. The above indication of the number of repetitions of PUCCH is inflexible.

[0004] The present disclosure aims to improve the indication of the number of repetitions of PUCCH. SUMMARY

[0005] Methods and apparatuses for are disclosed.

[0006] In one embodiment, the base unit comprises a transmitter that transmits a configuration containing an indication of the number of repetitions of PUCCH, wherein the configuration is determined according to the type of UCI carried in the PUCCH; and a receiver that receives the PUCCH repeatedly with the number of repetitions.

[0007] In one embodiment, the configuration is RRC signaling for all types of UCI carried in the PUCCH, and the indication is per PUCCH resource. In another embodiment, the configuration is MAC CE for all types of UCI carried in the PUCCH, and the indication is per PUCCH resource or per PUCCH resource group.

[0008] In yet another embodiment, when the type of UCI carried in the PUCCH is one of periodic CSI corresponding to DL SPS, SR, and HARQ-ACK, the configuration is RRC signaling. When the type of UCI carried in the PUCCH is semi-persistent CSI, the configuration is a MAC CE that activates the semi-persistent CSI.

[0009] In some embodiments, when the type of UCI carried in the PUCCH is HARQ-ACK corresponding to a DL transmission scheduled by a DCI, the configuration is the DCI that schedules the DL transmission. The indication can be contained in a new field of the DCI. Alternatively, the indication can be contained in the time domain resource assignment field of the DCI. For example, the value of the time domain assignment assignment field indicates a row in a table that includes a column for indicating the number of repetitions. The table can be configured by RRC as a pdsch time domain allocation list, or if no pdsch time domain allocation list is configured, it can be a pre-defined table. The column for indicating the number of repetitions can be a newly added column in the table, or an existing column in the table that is also used to indicate the number of repetitions of a PDSCH carrying the scheduled DL transmission. The indication can also be contained in the PDSCH-to-HARQ_feedback timing indicator field of the DCI. For example, the value of the PDSCH-to-HARQ-feedback timing indicator field indicates a row in a table that includes a column for indicating the number of repetitions. The table can be configured by RRC as a dl data to ul ACK list, or if no dl data to ul ACK list is configured, it can be a pre-defined table. The column for indicating the number of repetitions can be a newly added column in the table.

[0010] In some embodiments, when the UCI type carried in the PUCCH is not HARQ-ACK corresponding to a DL transmission scheduled by the DCI, the configuration is RRC signaling and indicates for each PUCCH format.

[0011] In one embodiment, a method includes transmitting a configuration containing an indication of a number of repetitions of a PUCCH, wherein the configuration is determined according to a UCI type carried in the PUCCH; and receiving the PUCCH repeatedly with the number of repetitions.

[0012] In another embodiment, a remote unit includes a receiver that receives a configuration containing an indication of a number of repetitions of a PUCCH, wherein the configuration is determined according to a UCI type carried in the PUCCH; and a transmitter that transmits the PUCCH repeatedly with the number of repetitions.

[0013] In yet another embodiment, a method includes receiving a configuration containing an indication of a number of repetitions of a PUCCH, wherein the configuration is determined according to a UCI type carried in the PUCCH; and transmitting the PUCCH repeatedly with the number of repetitions. BRIEF DESCRIPTION OF DRAWINGS

[0014] A more particular description of the embodiments briefly described above will be rendered by reference to specific embodiments illustrated in the drawings that are shown by way of example, in which:

[0015] Figure 1 illustrates a MAC CE for activating semi-persistent CSI in TS 38.321;

[0016] Figure 2 illustrates a MAC CE according to a fourth embodiment;

[0017] Figure 3 is a schematic flowchart illustrating an embodiment of a method;

[0018] Figure 4 is a schematic flowchart illustrating yet another embodiment of a method; and

[0019] Figure 5 is a schematic block diagram illustrating an apparatus according to an embodiment. DETAILED DESCRIPTION

[0020] As will be appreciated by those skilled in the art, certain aspects of the embodiments can be embodied as a system, a device, a method or a program product. Accordingly, the embodiments can take the form of an entirely hardware embodiment, an entirely software embodiment (including firmware, resident software, micro-code, etc.) or an embodiment combining software and hardware aspects that can all generally be referred to herein as a "circuit," "module" or "system." Furthermore, the embodiments can take the form of a program product embodied in one or more computer readable storage devices storing machine-readable code, computer readable code, and / or program code, hereinafter "code". The storage devices can be tangible and / or non-transitory. The storage devices can not embody signals. In a certain embodiment, the storage devices only employ signals for the accessing code.

[0021] Certain of the functional units described in this specification can be labeled as "modules," in order to more particularly emphasize their implementation independence. For example, a module can be implemented as a hardware circuit comprising custom very-large-scale integration (VLSI) circuits or gate arrays, off-the-shelf semiconductors such as logic chips, transistors, or other discrete components. A module can also be implemented in programmable hardware devices such as field programmable gate arrays, programmable array logic, programmable logic devices or the like.

[0022] Modules can also be implemented in code and / or software for execution by various types of processors. An identified module of code may, for instance, include one or more physical or logical blocks of executable code which may, for instance, be organized as an object, procedure or function. Nevertheless, the executables of an identified module need not be physically located together, but can include disparate instructions stored in different locations which, when joined logically together, include the module and achieve the stated purpose for the module.

[0023] Indeed, a module of code can be a single instruction, or many instructions, and can even be distributed over several different code segments, in several different programs and across several memory devices. Similarly, operational data can be identified and illustrated herein within modules, and can be embodied in any suitable form and organized within any suitable type of data structure. The operational data can be collected as a single data set, or can be distributed over different locations including over different computer readable storage devices. Where a module or portions of a module are implemented in software, the software portions are stored in one or more computer readable storage devices.

[0024] Any combination of one or more computer readable medium can be utilized. The computer readable medium can be a computer readable storage medium. The computer readable storage medium can be a storage device storing the code. The storage device can be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, holographic, micromechanical, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing.

[0025] A non-exhaustive list of more specific examples of storage devices would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer readable storage medium can be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.

[0026] Code for carrying out operations for embodiments can include any number of lines and any combination of lines including any combination of procedural lines, program lines, and / or machine lines in any appropriate programming language such as object-oriented programming, Python, Ruby, Java, Smalltalk, C++, and conventional procedural programming languages, and / or machine languages such as assembly languages. The code can execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer can be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection can be made to an external computer (for example, through the Internet using an Internet Service Provider).

[0027] References to “one embodiment,” “an embodiment,” or the like, mean that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment. The appearances of the phrase “in one embodiment” in various places in the specification are not necessarily all referring to the same embodiment, although it can. Any combination of one or more

[0028] Moreover, the described features, structures, or characteristics of the various embodiments can be combined in any suitable manner. In the following description, numerous specific details are provided, such as examples of programming, software modules, user selections, network transactions, database queries, database structures, hardware modules, hardware circuits, hardware chips, etc., to provide a thorough understanding of the embodiments. One skilled in the relevant art will recognize, however, that the embodiments can be practiced without one or more of the specific details, or with other methods, components, materials, and so forth. In other instances, well-known structures, materials, or operations are not shown or described in detail in order to avoid obscuring aspects of the embodiments.

[0029] Aspects of the different embodiments can be described below with reference to schematic flowcharts and / or schematic block diagrams of methods, apparatuses, systems, and program products according to the different embodiments. It will be understood that each block of the schematic flowcharts and / or schematic block diagrams, and combinations of blocks in the schematic flowcharts and / or schematic block diagrams, can be implemented by code. The code can be provided to a processor of a general purpose computer, a special purpose computer, or other programmable data processing apparatus to produce a machine, such that the code, which executes via the processor of the computer or other programmable data processing apparatus, creates means for implementing the functions specified in the flowchart block or blocks.

[0030] The code can also be stored in a storage device that can direct a computer, other programmable data processing apparatus, or other devices to function in a particular manner, such that the instructions stored in the storage device produce an article of manufacture including instructions which implement the function specified in the flowchart block or blocks.

[0031] The code can also be loaded onto a computer, other programmable data processing apparatus, or other devices to cause a series of operational steps to be performed on the computer, other programmable apparatus or other devices to produce a computer implemented process such that the code which execute on the computer or other programmable apparatus provide processes for implementing the function specified in the flowchart block or blocks.

[0032] The flowcharts and / or block diagrams in the various figures illustrate the architecture, functionality, and operation of possible implementations of apparatuses, systems, methods and program products according to various embodiments. In this regard, each block in the flowcharts and / or block diagrams can represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the flowcharts and / or block diagrams can represent a

[0033] It should also be noted that in some alternative implementations, the functions noted in the blocks can occur out of the order noted in the figures. For example, two blocks noted in succession can in fact be executed substantially concurrently or can sometimes be executed in the reverse order, depending upon the functionality involved. Other steps and methods can be conceived that are equivalent in function, logic, or effect to those illustrated, with the scope of the present disclosure intended to include all such steps and methods.

[0034] Although various arrow types and line types can be employed in the flowchart and / or block diagrams, these are understood to be merely illustrative of the logical flows of the embodiments. In reality, the arrows or connector lines can be used to depict only a single logical flow of a depicted embodiment. For example, an arrow can depict the same logical flow in a case of enumerating the particular steps involved. Also, various objects on the logical flows can represent one or more acts. Each block of the block diagrams and / or flowchart illustrations, and combinations of blocks in the block diagrams and / or flowchart illustrations, can be implemented by special purpose hardware-based systems that perform the specified functions or acts, or combinations of special purpose hardware and code.

[0035] The descriptions of elements in the figures can refer to elements of the preceding figures. Like reference numbers in all figures refer to like elements, including alternative embodiments of the same element.

[0036] The UCI carried in a PUCCH can be classified into periodic UCI (e.g., any one of periodic CSI, SR, or HARQ-ACK corresponding to DL SPS), semi-persistent UCI (e.g., semi-persistent CSI), and aperiodic UCI (e.g., HARQ-ACK corresponding to DL scheduling). The number of repetitions of a PUCCH can be indicated according to the type of UCI carried in the PUCCH. For example, the indication of the number of repetitions of a PUCCH can be the same for all types of UCI carried in the PUCCH. Alternatively, the number of repetitions of a PUCCH can be indicated differently for different types of UCI carried in the PUCCH. The explanations of the present disclosure are described in detail.

[0037] According to a first embodiment, the number of repetitions of a PUCCH (hereinafter, can be abbreviated as “number of repetitions”) is configured by RRC for each PUCCH resource for all types of UCI carried in the PUCCH. Unlike the prior art in which the number of repetitions is configured for each PUCCH format, according to the first embodiment, the number of repetitions is configured for each PUCCH resource. Thus, a gNB can configure different numbers of repetitions for different PUCCH resources of the same PUCCH format to provide maximum flexibility. On the other hand, configuring the number of repetitions by RRC for each PUCCH resource can incur much overhead and can also incur greater latency due to updating the number of repetitions.

[0038] As an example of the first embodiment, the RRC configuration of PUCCH resources in TS 38.331 can be augmented with an additional column to indicate the number of repetitions of a PUCCH. In the following example, the added column is named nrofSlots, whose possible values are any one of {n1, n2, n4, n8}.

[0039]

[0040] According to a second embodiment, the number of repetitions can be indicated or updated by a MAC CE for all UCI types carried in a PUCCH. The number of repetitions of a PUCCH can be indicated in a MAC CE per PUCCH resource or per PUCCH resource group comprising multiple PUCCH resources.

[0041] An example of a MAC CE for indicating the number of repetitions per PUCCH resource can be constructed by indicating the number of repetitions per PUCCH resource indicated in the MAC CE.

[0042] Another example of a MAC CE for indicating the number of repetitions per PUCCH resource group can be constructed by indicating the number of repetitions per PUCCH resource group indicated in the MAC CE. All PUCCH resources contained in one PUCCH resource group will be configured with the same number of repetitions.

[0043] If the number of repetitions of a PUCCH is indicated by RRC per PUCCH format or per PUCCH resource, the indication of the number of repetitions of a PUCCH by a MAC CE will update the existing indication.

[0044] Compared to indicating the number of repetitions by RRC according to the first embodiment, the indication of the number of repetitions by a MAC CE can be faster and cause less overhead.

[0045] In the first and second embodiments described above, the indication of the number of repetitions of a PUCCH by RRC or a MAC CE is for all UCI types carried in a PUCCH. In the following third, fourth and fifth embodiments, the number of repetitions of a PUCCH can be indicated in different ways for different UCI types carried in a PUCCH.

[0046] The third embodiment relates to indicating the number of repetitions of a PUCCH carrying periodic UCI, e.g. any of periodic CSI, SR or HARQ-ACK corresponding to DL SPS. The fourth embodiment relates to indicating the number of repetitions of a PUCCH carrying semi-persistent UCI, e.g. semi-persistent CSI. The fifth embodiment relates to indicating the number of repetitions of a PUCCH carrying aperiodic UCI, e.g. HARQ-ACK corresponding to DL scheduling.

[0047] Periodic UCI, e.g. any of periodic CSI, SR or HARQ-ACK corresponding to DL SPS, is configured to be transmitted in a PUCCH resource by RRC. According to the third embodiment, the number of repetitions of a PUCCH carrying periodic UCI is indicated in the RRC configuring the PUCCH resource.

[0048] For example, for a PUCCH resource carrying periodic CSI, the RRC configuration in TS 38.331 can be updated to add a row to indicate the number of repetitions of a PUCCH carrying periodic CSI. In the following example, the added row is named nrofSlots, whose possible values are any of {n1, n2, n4, n8}.

[0049]

[0050]

[0051]

[0052]

[0053]

[0054] For a PUCCH carrying SR, the RRC configuration in TS 38.331 can be updated to add a row to indicate the number of repetitions of a PUCCH carrying SR. In the following example, the added row is named nrofSlots, whose possible values are any of {n1, n2, n4, n8}.

[0055]

[0056]

[0057] For PUCCH carrying HARQ-ACK corresponding to DL SPS, the RRC configuration in TS 38.331 can be updated to add a row to indicate the number of repetitions of PUCCH carrying HARQ-ACK corresponding to DL SPS. In the following example, the added row is named nrofSlots, whose possible values are any one of {n1, n2, n4, n8}.

[0058]

[0059]

[0060] Semi-persistent UCI, e.g., semi-persistent CSI, configured to be transmitted in PUCCH resources is activated by MAC CE in NR Rel-15. According to the fourth embodiment, the number of repetitions of PUCCH carrying semi-persistent UCI, e.g., semi-persistent CSI, is indicated in the redesigned MAC CE activating semi-persistent CSI.

[0061] The MAC CE for activating semi-persistent CSI in TS 38.321 is shown in Figure 1 . As shown in Figure 1 , the SP CSI reporting with PUCCH activation / deactivation MAC CE has a fixed size of 16 bits with the following fields:

[0062] Serving Cell ID: This field indicates the identity of the serving cell to which the MAC CE applies. The length of this field is 5 bits.

[0063] BWP ID: This field indicates the UL BWP to which the MAC CE applies as a codepoint of the DCI bandwidth part indicator field as specified in TS 38.212 [9]. The length of the BWP ID field is 2 bits.

[0064] S i(i = 0, 1, 2 and 3): This field indicates the activation / deactivation status of the semi-persistent CSI reporting configuration within csi-ReportConfigToAddModList as specified in TS 38.331 [5]. S0 refers to the reporting configuration that includes PUCCH resource for SP CSI reporting in the indicated BWP and has the lowest CSI-ReportConfigld within the list whose type is set to semiPersistentOnPUCCH, S1 refers to the reporting configuration that includes PUCCH resource for SP CSI reporting in the indicated BWP and has the next lowest CSI-ReportConfigld, and so on. If the number of reporting configurations within the list whose type is set to semiPersistentOnPUCCH in the indicated BWP is less than i+1, the MAC entity shall ignore S i field. S i The field is set to 1 to indicate the corresponding semi-persistent CSI reporting configuration that shall be activated. S i The field is set to 0 to indicate the corresponding semi-persistent CSI reporting configuration i that shall be deactivated.

[0065] R: Reserved bit, set to 0.

[0066] According to the fourth embodiment, the number of repetitions of PUCCH carrying semi-persistent CSI can be indicated by using the reserved bits (e.g., 4 reserved bits in Oct 2) on SP CSI reporting of PUCCH activation / deactivation MAC CE.

[0067] Figure 2 Fig. illustrates an example of SP CSI reporting of PUCCH activation / deactivation MAC CE according to the fourth embodiment. As Figure 2 shown, Figure 1 the 4 reserved bits in Oct 2 are used to indicate the number of repetitions of PUCCH carrying semi-persistent CSI activated by the MAC CE. In particular, a field ‘nrofSlots’ of up to 4 bits is included in SP CSI reporting of PUCCH activation / deactivation MAC CE according to the fourth embodiment to indicate the number of repetitions of each PUCCH carrying semi-persistent CSI activated by S i (i = 0, 1, 2 and 3) that are set to 1. That is, all PUCCHs in SP CSI reporting of PUCCH activation / deactivation MAC CE according to the fourth embodiment are indicated by the nrofSlots field with the same number of repetitions, where each PUCCH carries semi-persistent CSI activated by S i (i = 0, 1, 2 and 3) that are set to 1.

[0068] The repetition number indication does not necessarily occupy all four reserved bits in Oct 2. For example, if the repetition number has four possible values, the two reserved bits in Oct 2 are sufficient to indicate four different repetition numbers.

[0069] Incidentally, the number of repetitions of the PUCCH carrying the semi-persistent CSI can be alternatively indicated in the CSI-ReportConfig via RRC in the same manner as in the third embodiment.

[0070] The HARQ-ACK corresponding to the scheduled DL transmission is sent in the PUCCH resource. The DCI that schedules the DL transmission also schedules the PUCCH resource for sending the HARQ-ACK corresponding to the scheduled DL transmission. Therefore, according to the fifth embodiment, the number of repetitions of the PUCCH carrying the HARQ-ACK corresponding to the scheduled DL transmission is indicated in the DCI that schedules the DL transmission.

[0071] There are three options for indicating the number of repetitions of the PUCCH carrying the HARQ-ACK corresponding to the scheduled DL transmission in the DCI for scheduling DL transmission (hereinafter referred to as "scheduling DCI").

[0072] According to the first sub-implementation of the fifth embodiment, a new DCI field is added to the scheduling DCI to indicate the number of repetitions of the PUCCH carrying the HARQ-ACK corresponding to the scheduled DL transmission. The first sub-implementation achieves maximum flexibility. However, the payload of the scheduling DCI is increased compared to the conventional scheduling DCI, which increases the complexity of DCI decoding.

[0073] According to the second sub-implementation of the fifth embodiment, the time-domain resource assignment field of the DCI indicates the number of repetitions of the PUCCH for the HARQ-ACK corresponding to the scheduled DL transmission. The value m of the time-domain resource assignment field indicates row m+1 of the allocation table in NR version 15. The allocation table is configured by pdsch-TimeDomainAllocationList in pdsch-Config via RRC. If pdsch-TimeDomainAllocationList is not configured, the allocation table is a predefined table. According to the second sub-implementation, a new column is added to the allocation table to indicate the number of repetitions of the PUCCH for the HARQ-ACK corresponding to the scheduled DL transmission. In other words, the value m of the time-domain resource assignment field of the DCI according to the second sub-implementation indicates row m+1 of the allocation table, which indicates the time allocation of the PDSCH for the scheduled DL transmission and the number of repetitions of the PUCCH for the HARQ-ACK corresponding to the scheduled DL transmission.

[0074] For example, the configuration of pdsch-TimeDomainAllocationList in TS 38.331 can be updated to add a column to indicate the number of repetitions of the PUCCH carrying HARQ-ACK corresponding to the scheduled DL transmission. In the following example, the added column is named nrofSlots, whose possible values are any one of {n1, n2, n4, n8}.

[0075]

[0076] According to the second sub-embodiment described above, a column named nrofSlots in TS 38.331 of NR Rel-15 is added to the configuration of the allocation table configured by pdsch-TimeDomainAllocationList (or the pre-defined table if pdsch-TimeDomainAllocationList is not configured). In URLLC (Ultra-Reliable and Low-Latency Communication) scheme 4 in NR Rel-16, the number of repetitions of PDSCH carrying the scheduled DL transmission is supported by adding a new column in the allocation table in the time domain resource assignment field. In the following example, the added column is named repNumR16, whose possible values are any one of {n1, n2, n4, n8}.

[0077]

[0078]

[0079] According to a variant of the second sub-embodiment, the number of repetitions of PDSCH indicated in the column named repNumR16 is reused as the number of repetitions of the PUCCH carrying HARQ-ACK corresponding to the scheduled DL transmission. That is, the PDSCH carrying the DL transmission scheduled by DCI and the PUCCH carrying HARQ-ACK corresponding to the scheduled DL transmission are transmitted repeatedly using the same number of repetitions indicated by the column ‘repNumR16’ added in the allocation table configured by pdsch-TimeDomainAllocationList in the time domain resource assignment field by DCI (or in the pre-defined table if pdsch-TimeDomainAllocationList is not configured).

[0080] According to another variant of the second sub-embodiment, in addition to repNumR16 which is added for indicating the number of repetitions of the PDSCH carrying the DCI-scheduled DL transmission, a new column named nrofSlots (whose possible values are any one of {n1, n2, n4, n8}) is additionally added to the allocation table configured by pdsch-TimeDomainAllocationList in pdsch-Config (or to the pre-defined table if pdsch-TimeDomainAllocationList is not configured). In the following example, the added columns are named repNumR16 and nrofSlots in pdsch-TimeDomainAllocationList in pdsch-Config, each of which has possible values of any one of {n1, n2, n4, n8}.

[0081]

[0082]

[0083] It can be seen that the number of repetitions of the PDSCH carrying the DCI-scheduled DL transmission and the number of repetitions of the PUCCH carrying the HARQ-ACK corresponding to the scheduled DL transmission for URLLC scheme 4 are independently indicated by repNumR16 and nrofSlots, respectively.

[0084] According to a third sub-embodiment of the fifth embodiment, the number of repetitions of the PUCCH resource is indicated in the PDSCH-to-HARQ_feedback timing indicator field of the DCI. The value m of the PDSCH-to-HARQ_feedback timing indicator field indicates row m+1 of the allocation table in NR Rel. 15. The allocation table is configured by dl-DataToUL-ACK in pdsch-Config through RRC. If dl-DataToUL-ACK is not configured, the allocation table is a pre-defined table. It should be noted that there is only one column in the allocation table in NR Rel. 15. According to the present application, dl-DataToUL-ACK is renamed as dl-DataToUL-ACKList. According to the third sub-embodiment, a new column is added in dl-DataToUL-ACKList to indicate the number of repetitions of the PUCCH resource carrying HARQ-ACK corresponding to the scheduled DL transmission. Thus, the value m of the PDSCH-to-HARQ_feedback timing indicator field indicates row m+1 in dl-DataToUL-ACKList, which indicates the time offset between the PDSCH carrying the scheduled DL transmission and the PUCCH carrying HARQ-ACK corresponding to the scheduled DL transmission as well as the repetition time of the PUCCH.

[0085] For example, the configuration in TS 38.331 can be updated to add a column to indicate the number of repetitions of the PUCCH carrying HARQ-ACK corresponding to the scheduled DL transmission. In the following example, the added column is named as nrofSlots (its possible values are any one of {n1, n2, n4, n8}) in dl-DataToUL-ACKList. By the way, the column named as ‘k’ indicates the time offset between the PDSCH carrying the scheduled DL transmission and the PUCCH carrying HARQ-ACK corresponding to the scheduled DL transmission.

[0086]

[0087]

[0088]

[0089] According to the sixth embodiment, similar to the third to fifth embodiments, the number of repetitions of the PUCCH can be indicated in different ways depending on different UCI types carried in the PUCCH.

[0090] Considering the reliability of the PUCCH carrying HARQ-ACK corresponding to scheduled DL transmission is more important for the throughput of the network than other UCI types, it is preferred to provide more flexibility to indicate the number of repetitions of the PUCCH carrying HARQ-ACK corresponding to scheduled DL transmission only. According to the sixth embodiment, if the PUCCH carries UCI other than HARQ-ACK corresponding to scheduled DL transmission, the number of repetitions of the PUCCH is indicated per PUCCH format as in TS 38.331. On the other hand, if the PUCCH carries HARQ-ACK corresponding to scheduled DL transmission, the number of repetitions of the PUCCH can be indicated updated by the scheduling DCI as described in the fifth embodiment.

[0091] The advantage of the sixth embodiment is that the number of repetitions of the PUCCH carrying HARQ-ACK corresponding to scheduled DL transmission, which needs high level of reliability, can be more flexibly indicated by using the scheduling DCI as described in the fifth embodiment, however, the number of repetitions of the PUCCH carrying other UCI types than HARQ-ACK corresponding to scheduled DL transmission can be indicated in the existing way (i.e. indicated per PUCCH format as in TS 38.331) to reduce the impact on the existing specification.

[0092] Generally, according to the present application, the configuration containing the indication of the number of repetitions of the PUCCH can be determined according to the type of UCI carried in the PUCCH. The configuration can be RRC signaling or MAC CE or scheduling DCI.

[0093] Figure 3 FIG. 3 is a schematic flow chart illustrating a method 300 according to an embodiment of the present application. In some embodiments, the method 300 is performed by an apparatus, such as a base unit. In certain embodiments, the method 300 can be performed by a processor executing program code, e.g., a microcontroller, microprocessor, CPU, GPU, auxiliary processing unit, FPGA, etc.

[0094] The method 300 can comprise 302 transmitting a configuration containing an indication of a number of repetitions of a PUCCH, wherein the configuration is determined according to a type of UCI carried in the PUCCH; and 304 receiving the PUCCH repeatedly with the number of repetitions.

[0095] Figure 4 FIG. 4 is a schematic flow chart illustrating yet another embodiment of a method 400 according to the present application. In some embodiments, the method 400 is performed by an apparatus, such as a remote unit. In certain embodiments, the method 400 can be performed by a processor executing program code, e.g., a microcontroller, microprocessor, CPU, GPU, auxiliary processing unit, FPGA, etc.

[0096] The method 400 can include 402 receiving a configuration including an indication of a number of repetitions of a PUCCH, wherein the configuration is determined according to a type of UCI carried in the PUCCH; and 404 transmitting the PUCCH repeatedly with the number of repetitions.

[0097] Figure 5 is a schematic block diagram illustrating an apparatus according to one embodiment.

[0098] Referring to Figure 5 , the UE (i.e., remote unit) includes a processor, a memory, and a transceiver. The processor implements the functions, procedures, and / or methods proposed in Figure 4 . The gNB (i.e., base station unit) includes a processor, a memory, and a transceiver. The processor implements the functions, procedures, and / or methods proposed in Figure 3 . Layers of the radio interface protocol can be implemented by the processor. The memory is connected with the processor to store various pieces of information for driving the processor. The transceiver is connected with the processor to transmit and / or receive radio signals. Needless to say, the transceiver can be implemented as a transmitter for transmitting radio signals and a receiver for receiving radio signals.

[0099] The memory can be positioned inside or outside the processor and connected with the processor through various well-known means.

[0100] In the above-described embodiments, components and features of the embodiments are combined in a predetermined form. Each component or function should be considered as an option unless explicitly stated otherwise. Each component or feature can be implemented as not associated with other components or features. Also, a certain embodiment can be configured by associating some components and / or features. The order of operations described in the embodiments can be changed. Some components or features of any embodiment can be included in another embodiment or replaced with components and features corresponding to another embodiment. It is obvious that claims not explicitly cited in the claims are combined to form embodiments or included in new claims.

[0101] Embodiments can be implemented by hardware, firmware, software, or a combination thereof. In case of implementation by hardware, according to the hardware implementation, the exemplary embodiments described herein can be implemented by one or more application specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), processors, controllers, micro-controllers, microprocessors, etc.

[0102] Embodiments can be practiced in other specific forms. The described embodiments are to be considered in all respects only as illustrative and not restrictive. The scope of the application is, therefore, indicated by the appended claims, rather than by the foregoing description. All changes that come within the meaning and range of equivalency of the claims are to be embraced within their scope.

Claims

1. A base station unit, comprising: A transmitter that transmits a configuration including an indication of the number of repetitions of a PUCCH, wherein the configuration is determined based on the UCI type carried in the PUCCH; and A receiver that repeatedly receives the PUCCH the specified number of repetitions. Wherein, when the UCI type carried in the PUCCH is HARQ-ACK corresponding to a DL transmission scheduled by the DCI, the configuration is the DCI that schedules the DL transmission. Wherein, when the UCI type carried in the PUCCH is not a HARQ-ACK corresponding to the DL transmission scheduled by the DCI, the configuration is RRC signaling and the indication is for each PUCCH format.

2. The base station unit according to claim 1, wherein, The indication is included in a new field of the DCI.

3. The base station unit according to claim 1, wherein, The instruction is contained in the time-domain resource assignment field of the DCI.

4. The base station unit according to claim 3, wherein, The value of the time-domain resource assignment field indicates a row in a table that includes a column indicating the number of repetitions.

5. The base station unit according to claim 4, wherein, The table is configured by RRC as a pdsch time-domain allocation list.

6. The base station unit according to claim 4, wherein, If no pdsch time-domain allocation list is configured, the table is a predefined table.

7. The base station unit according to claim 4, wherein, The column used to indicate the number of repetitions is a newly added column in the table.

8. The base station unit according to claim 4, wherein, The column used to indicate the number of repetitions is an existing column in the table that is also used to indicate the number of repetitions of the PDSCH carrying the scheduled DL transmission.

9. The base station unit according to claim 1, wherein, The indication is contained in the PDSCH-to-HARQ-feedback timing indicator field of the DCI.

10. The base station unit according to claim 9, wherein, The value of the PDSCH-to-HARQ-feedback timing indicator field indicates a row in a table that includes a column indicating the number of repetitions.

11. The base station unit according to claim 10, wherein, The table is configured by RRC as a dl data to ul ACK list.

12. The base station unit according to claim 10, wherein, If no dl data to ul ACK list is configured, the table is a predefined table.

13. The base station unit according to claim 10, wherein, The column used to indicate the number of repetitions is a newly added column in the table.

14. A method performed by a base station unit, comprising: A configuration for sending an indication of the number of repetitions of the PUCCH, wherein the configuration is determined based on the UCI type carried in the PUCCH; and The PUCCH is received repeatedly at the stated number of repetitions. Wherein, when the UCI type carried in the PUCCH is HARQ-ACK corresponding to a DL transmission scheduled by the DCI, the configuration is the DCI that schedules the DL transmission. Wherein, when the UCI type carried in the PUCCH is not a HARQ-ACK corresponding to the DL transmission scheduled by the DCI, the configuration is RRC signaling and the indication is for each PUCCH format.

15. The method according to claim 14, wherein, The indication is included in a new field of the DCI.

16. The method of claim 14, wherein, The instruction is contained in the time-domain resource assignment field of the DCI.

17. The method according to claim 16, wherein, The value of the time-domain resource assignment field indicates a row in a table that includes a column indicating the number of repetitions.

18. The method according to claim 17, wherein, The table is configured by RRC as a pdsch time-domain allocation list.

19. The method of claim 17, wherein, If no pdsch time-domain allocation list is configured, the table is a predefined table.

20. The method of claim 17, wherein, The column used to indicate the number of repetitions is a newly added column in the table.

21. The method according to claim 17, wherein, The column used to indicate the number of repetitions is an existing column in the table that is also used to indicate the number of repetitions of the PDSCH carrying the scheduled DL transmission.

22. The method according to claim 14, wherein, The indication is contained in the PDSCH-to-HARQ-feedback timing indicator field of the DCI.

23. The method according to claim 22, wherein, The value of the PDSCH-to-HARQ-feedback timing indicator field indicates a row in a table that includes a column indicating the number of repetitions.

24. The method according to claim 23, wherein, The table is configured by RRC as a dl data to ul ACK list.

25. The method according to claim 23, wherein, If no dl data to ulACK list is configured, the table is a predefined table.

26. The method according to claim 23, wherein, The column used to indicate the number of repetitions is a newly added column in the table.

27. A remote unit, comprising: A receiver that receives a configuration including an indication of the number of repetitions of a PUCCH, wherein the configuration is determined based on the UCI type carried in the PUCCH; and The transmitter repeatedly transmits the PUCCH at the stated number of repetitions. Wherein, when the UCI type carried in the PUCCH is HARQ-ACK corresponding to a DL transmission scheduled by the DCI, the configuration is the DCI that schedules the DL transmission. Wherein, when the UCI type carried in the PUCCH is not a HARQ-ACK corresponding to the DL transmission scheduled by the DCI, the configuration is RRC signaling and the indication is for each PUCCH format.

28. The remote unit according to claim 27, wherein, The indication is included in a new field of the DCI.

29. The remote unit according to claim 27, wherein, The instruction is contained in the time-domain resource assignment field of the DCI.

30. The remote unit according to claim 29, wherein, The value of the time-domain resource assignment field indicates a row in a table that includes a column indicating the number of repetitions.

31. The remote unit according to claim 29, wherein, The table is configured by RRC as a pdsch time-domain allocation list.

32. The remote unit according to claim 30, wherein, If no pdsch time-domain allocation list is configured, the table is a predefined table.

33. The remote unit according to claim 30, wherein, The column used to indicate the number of repetitions is a newly added column in the table.

34. The remote unit according to claim 30, wherein, The column used to indicate the number of repetitions is an existing column in the table that is also used to indicate the number of repetitions of the PDSCH carrying the scheduled DL transmission.

35. The remote unit according to claim 27, wherein, The indication is contained in the PDSCH-to-HARQ-feedback timing indicator field of the DCI.

36. The remote unit according to claim 35, wherein, The value of the PDSCH-to-HARQ-feedback timing indicator field indicates a row in a table that includes a column indicating the number of repetitions.

37. The remote unit according to claim 36, wherein, The table is configured by RRC as a dl data to ul ACK list.

38. The remote unit according to claim 36, wherein, If no dl data to ulACK list is configured, the table is a predefined table.

39. The remote unit according to claim 36, wherein, The column used to indicate the number of repetitions is a newly added column in the table.

40. A method executed by a remote unit, comprising: A configuration for receiving an indication of the number of repetitions of a PUCCH, wherein the configuration is determined based on the UCI type carried in the PUCCH; and The PUCCH is sent repeatedly at the stated number of repetitions. Wherein, when the UCI type carried in the PUCCH is HARQ-ACK corresponding to a DL transmission scheduled by the DCI, the configuration is the DCI that schedules the DL transmission. Wherein, when the UCI type carried in the PUCCH is not a HARQ-ACK corresponding to the DL transmission scheduled by the DCI, the configuration is RRC signaling and the indication is for each PUCCH format.

41. The method according to claim 40, wherein, The indication is included in a new field of the DCI.

42. The method according to claim 40, wherein, The instruction is contained in the time-domain resource assignment field of the DCI.

43. The method according to claim 42, wherein, The value of the time-domain resource assignment field indicates a row in a table that includes a column indicating the number of repetitions.

44. The method according to claim 43, wherein, The table is configured by RRC as a pdsch time-domain allocation list.

45. The method according to claim 43, wherein, If no pdsch time-domain allocation list is configured, the table is a predefined table.

46. ​​The method according to claim 43, wherein, The column used to indicate the number of repetitions is a newly added column in the table.

47. The method according to claim 43, wherein, The column used to indicate the number of repetitions is an existing column in the table that is also used to indicate the number of repetitions of the PDSCH carrying the scheduled DL transmission.

48. The method of claim 40, wherein, The indication is contained in the PDSCH-to-HARQ-feedback timing indicator field of the DCI.

49. The method according to claim 48, wherein, The value of the PDSCH-to-HARQ-feedback timing indicator field indicates a row in a table that includes a column indicating the number of repetitions.

50. The method according to claim 49, wherein, The table is configured by RRC as a dl data to ul ACK list.

51. The method according to claim 49, wherein, If no dl data to ulACK list is configured, the table is a predefined table.

52. The method according to claim 49, wherein, The column used to indicate the number of repetitions is a newly added column in the table.

Images