PUCCH resources for Msg4 HARQ feedback repetition

Abstract

An apparatus comprising at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus to at least: receive a message using a physical downlink shared channel; determining a physical uplink control channel resource for transmission of a hybrid automatic repeat request acknowledgement based on a message received using a physical downlink shared channel; wherein the physical uplink control channel resource is used for the repetition of the transmission; and transmitting a hybrid automatic repeat request acknowledgement using the determined physical uplink control channel resource for the repetition.

Description

Technical Field

[0001] The exemplary and non-limiting exemplary embodiments relate generally to communications, and more particularly to PUCCH resources for msg4 HARQ feedback repetition. Background Art

[0002] It is known to implement a random access response procedure in a communication network. Summary of the invention

[0003] According to one aspect, a device includes at least one processor; and at least one memory storing instructions, which when executed by the at least one processor causes the device to at least: receive a message using a physical downlink shared channel; determine a physical uplink control channel resource for transmission of a hybrid automatic repeat request acknowledgment based on the message received using the physical downlink shared channel; wherein the physical uplink control channel resource is used for repetition of the transmission; and send a hybrid automatic repeat request acknowledgment using the determined physical uplink control channel resource for repetition.

[0004] According to one aspect, a device includes at least one processor; and at least one memory storing instructions, which when executed by the at least one processor causes the device to at least: send a message using a physical downlink shared channel; and receive a hybrid automatic repeat request confirmation using a physical uplink control channel resource, the hybrid automatic repeat request confirmation being received based on the message sent using the physical downlink shared channel; wherein the physical uplink control channel resource is used for repetition of transmission; wherein the hybrid automatic repeat request confirmation is received using the physical uplink control channel resource used for repetition when a dedicated physical uplink control channel configuration has not yet been sent.

[0005] According to one aspect, a method includes: receiving a message using a physical downlink shared channel; determining a physical uplink control channel resource for transmission of a hybrid automatic repeat request acknowledgment based on the message received using the physical downlink shared channel; wherein the physical uplink control channel resource is used for repetition of the transmission; and sending a hybrid automatic repeat request acknowledgment using the determined physical uplink control channel resource for repetition.

[0006] According to one aspect, a method includes: sending a message using a physical downlink shared channel; and receiving a hybrid automatic repeat request confirmation using a physical uplink control channel resource, wherein the hybrid automatic repeat request confirmation is received based on the message sent using the physical downlink shared channel; wherein the physical uplink control channel resource is used for repetition of transmission; wherein the hybrid automatic repeat request confirmation is received using the physical uplink control channel resource used for repetition when a dedicated physical uplink control channel configuration has not been sent.

[0007] According to one aspect, an apparatus includes: a component for receiving a message using a physical downlink shared channel; a component for determining a physical uplink control channel resource for transmission of a hybrid automatic repeat request acknowledgment based on the message received using the physical downlink shared channel; wherein the physical uplink control channel resource is used for repetition of the transmission; and a component for sending a hybrid automatic repeat request acknowledgment using the determined physical uplink control channel resource for repetition.

[0008] According to one aspect, an apparatus includes: a component for sending a message using a physical downlink shared channel; and a component for receiving a hybrid automatic repeat request confirmation using a physical uplink control channel resource, the hybrid automatic repeat request confirmation being received based on the message sent using the physical downlink shared channel; wherein the physical uplink control channel resource is used for repetition of transmission; wherein the hybrid automatic repeat request confirmation is received using the physical uplink control channel resource used for repetition when a dedicated physical uplink control channel configuration has not yet been sent.

[0009] According to one aspect, a machine-readable, non-volatile program storage device is provided and described, the device tangibly implementing a machine-executable instruction program for performing operations, the operations including: receiving a message using a physical downlink shared channel; determining a physical uplink control channel resource for transmission of a hybrid automatic repeat request acknowledgment based on the message received using the physical downlink shared channel; wherein the physical uplink control channel resource is used for repetition of the transmission; and sending a hybrid automatic repeat request acknowledgment using the determined physical uplink control channel resource for repetition.

[0010] According to one aspect, a machine-readable, non-volatile program storage device is provided and described, the device tangibly implementing a machine-executable instruction program for performing operations, the operations including: sending a message using a physical downlink shared channel; and receiving a hybrid automatic repeat request confirmation using a physical uplink control channel resource, the hybrid automatic repeat request confirmation being received based on the message sent using the physical downlink shared channel; wherein the physical uplink control channel resource is used for repetition of transmission; wherein the hybrid automatic repeat request confirmation is received using the physical uplink control channel resource used for repetition when a dedicated physical uplink control channel configuration has not yet been sent. BRIEF DESCRIPTION OF THE DRAWINGS

[0011] The above-described aspects and other features are explained in the following description taken in conjunction with the accompanying drawings.

[0012] Figure 1 is a block diagram of one possible and non-limiting system in which example embodiments may be practiced.

[0013] Figure 2 An example PUCCH-Config information element is shown.

[0014] Figure 3 An example PUCCH-Resource information element is shown.

[0015] Figure 4 An example PUCCH-ResourceExt-v1610 information element is shown.

[0016] Figure 5 is a table showing resource sets before dedicated PUCCH resource configuration.

[0017] Figure 6 is an example apparatus configured to implement the examples described herein.

[0018] Figure 7 A representation of an example of a non-volatile storage medium is shown.

[0019] Figure 8 is an example method of implementing the examples described herein.

[0020] Fig. 9 is an example method of implementing the examples described herein. DETAILED DESCRIPTION

[0021] Steering Figure 1 , which shows a block diagram of one possible and non-limiting example in which the examples may be practiced. A user equipment (UE) 110, a radio access network (RAN) node 170 and (multiple) network elements 190 are shown. Figure 1 In the example of FIG. 1 , a user equipment (UE) 110 wirelessly communicates with a wireless network 100. A UE is a wireless device that can access the wireless network 100. The UE 110 includes one or more processors 120, one or more memories 125, and one or more transceivers 130 interconnected by one or more buses 127. Each transceiver in the one or more transceivers 130 includes a receiver Rx 132 and a transmitter Tx 133. The one or more buses 127 may be address, data, or control buses, and may include any interconnection mechanism, such as a series of lines on a motherboard or integrated circuit, optical fiber or other optical communication devices, etc. The one or more transceivers 130 are connected to one or more antennas 128. The one or more memories 125 include computer program code 123. The UE 110 includes a module 140, which includes one or both parts of 140-1 and / or 140-2, which may be implemented in a variety of ways. The module 140 may be implemented in hardware as the module 140-1, such as being implemented as part of the one or more processors 120. Module 140-1 may also be implemented as an integrated circuit or by other hardware such as a programmable gate array. In another example, module 140 may be implemented as module 140-2, which is implemented as computer program code 123 and executed by one or more processors 120. For example, one or more memories 125 and computer program code 123 may be configured to, together with one or more processors 120, enable user equipment 110 to perform one or more operations in the operations described herein. UE 110 communicates with RAN node 170 via wireless link 111.

[0022] In this example, RAN node 170 is a base station that provides access to wireless network 100 for wireless devices such as UE 110. RAN node 170 may be, for example, a base station for 5G, also referred to as New Radio (NR). In 5G, RAN node 170 may be a NG-RAN node, which is defined as a gNB or ng-eNB. A gNB is a node that provides NR user plane and control plane protocol termination towards UE and is connected to a 5GC (such as, for example, (multiple) network elements 190) via an NG interface (such as connection 131). An ng-eNB is a node that provides E-UTRA user plane and control plane protocol termination towards UE and is connected to a 5GC via an NG interface (such as connection 131). An NG-RAN node may include multiple gNBs, which may also include a central unit (CU) (gNB-CU) 196 and (multiple) distributed units (DU) (gNB-DU), of which DU 195 is shown. Note that DU 195 may include or be coupled to and control a radio unit (RU). The gNB-CU 196 is a logical node that hosts the radio resource control (RRC), SDAP and PDCP protocols of a gNB, or the RRC and PDCP protocols of an en-gNB that controls the operation of one or more gNB-DUs. The gNB-CU 196 terminates the F1 interface connected to the gNB-DU 195. The F1 interface is shown as reference numeral 198, although reference numeral 198 also shows a link between a remote element of the RAN node 170 and a centralized element of the RAN node 170, such as a link between the gNB-CU 196 and the gNB-DU 195. The gNB-DU 195 is a logical node that hosts the RLC, MAC, and PHY layers of a gNB or en-gNB, and its operation is controlled in part by the gNB-CU 196. One gNB-CU 196 supports one or more cells. One cell can be supported by one gNB-DU 195, or one cell can be supported / shared with multiple DUs under RAN sharing. The gNB-DU 195 terminates the F1 interface 198 which connects to the gNB-CU 196. Note that the DU 195 is considered to include the transceiver 160, e.g., as part of the RU, but some examples in this regard may have the transceiver 160 as part of a separate RU, e.g., under the control of the DU 195 and connected to the DU 195. The RAN node 170 may also be an eNB (evolved NodeB) base station for LTE (Long Term Evolution), or any other suitable base station or node.

[0023] The RAN node 170 includes one or more processors 152, one or more memories 155, one or more network interfaces ((multiple) N / WI / F) 161, and one or more transceivers 160 interconnected by one or more buses 157. Each of the one or more transceivers 160 includes a receiver Rx 162 and a transmitter Tx 163. The one or more transceivers 160 are connected to one or more antennas 158. The one or more memories 155 include computer program code 153. The CU 196 may include (multiple) processors 152, (multiple) memories 155, and a network interface 161. Note that the DU 195 may also contain its own memory / memory and (multiple) processors, and / or other hardware, but these are not shown.

[0024] The RAN node 170 includes a module 150, which includes one or both parts of 150-1 and / or 150-2, which can be implemented in a variety of ways. The module 150 can be implemented in hardware as the module 150-1, such as being implemented as part of one or more processors 152. The module 150-1 can also be implemented as an integrated circuit or by other hardware such as a programmable gate array. In another example, the module 150 can be implemented as a module 150-2, which is implemented as a computer program code 153 and is executed by one or more processors 152. For example, one or more memories 155 and the computer program code 153 are configured to, together with the one or more processors 152, enable the RAN node 170 to perform one or more operations in the operations described herein. Note that the functionality of the module 150 can be distributed, such as being distributed between the DU 195 and the CU 196, or implemented solely in the DU 195.

[0025] One or more network interfaces 161 communicate over a network, such as via links 176 and 131. Two or more gNBs 170 may communicate using, for example, link 176. Link 176 may be wired or wireless or both, and may implement, for example, an Xn interface for 5G, an X2 interface for LTE, or other suitable interfaces for other standards.

[0026] The one or more buses 157 may be address, data, or control buses, and may include any interconnection mechanism, such as a series of wires on a motherboard or integrated circuit, optical fiber or other optical communication device, wireless channel, etc. For example, the one or more transceivers 160 may be implemented as a remote radio head (RRH) 195 for LTE or a distributed unit (DU) 195 for a gNB implementation for 5G, where other elements of the RAN node 170 may be physically located at a different location than the RRH / DU 195, and the one or more buses 157 may be implemented in part, for example, as fiber optic cables, or other suitable network connections for connecting other elements of the RAN node 170 (e.g., central unit (CU), gNB-CU 196) to the RRH / DU 195. Reference numeral 198 also indicates these suitable network link(s).

[0027] The RAN node / gNB may include one or more TRPs, to which the methods described herein may be applied. Figure 1 The RAN node 170 is shown to include two TRPs (TRP 51 and TRP 52). The RAN node 170 may host or include Figure 1 Other TRPs not shown.

[0028] The relay nodes in NR are called integrated access and backhaul nodes. The mobile terminal part of the IAB node facilitates the backhaul (parent link) connection. In other words, the mobile terminal part is the function that carries the UE functionality. The distributed unit part of the IAB node facilitates the so-called access link (sub-link) connection (i.e., for the access link UE, and in the case of multi-hop IAB, for the backhaul of other IAB nodes). In other words, the distributed unit part is responsible for certain base station functions. The IAB scenario can follow a so-called split architecture, where the central unit hosts the high-level protocols to the UE and terminates at the control plane and user plane interfaces of the 5G core network.

[0029] Note that the description herein indicates that a "cell" performs a function, but it should be clear that the device that forms the cell can perform the function. A cell constitutes part of a base station. That is, there can be multiple cells for each base station. For example, there can be three cells for a single carrier frequency and associated bandwidth, each cell covering one-third of a 360-degree area, so the coverage area of ​​a single base station covers an approximate ellipse or circle. In addition, each cell can correspond to a single carrier, and a base station can use multiple carriers. So if there are 3 120-degree cells for each carrier, and there are 2 carriers, the base station has a total of 6 cells.

[0030] The wireless network 100 may include one or more network elements 190, which may include core network functions and provide connectivity to other networks such as telephone networks and / or data communication networks (e.g., the Internet) via one or more links 181. Such core network functions for 5G may include location management functions ((multiple) LMFs) and / or (multiple) access and mobility management functions ((multiple) AMFs) and / or user plane functions ((multiple) UPFs) and / or (multiple) session management functions ((multiple) SMFs). Such core network functions for LTE may include MME (mobility management entity) / SGW (serving gateway) functions. Such core network functions may include SON (self-organizing / optimizing network) functions. These are merely example functions that may be supported by (multiple) network elements 190, and it is noted that both 5G and LTE functions may be supported. The RAN node 170 is coupled to the network element 190 via a link 131. The link 131 may be implemented as, for example, an NG interface for 5G, or an S1 interface for LTE, or other suitable interfaces for other standards. The network element 190 includes one or more processors 175, one or more memories 171, and one or more network interfaces (N / WI / F) 180 interconnected by one or more buses 185. The one or more memories 171 include computer program code 173. The computer program code 173 may include SON and / or MRO functionality 172.

[0031] The wireless network 100 may implement network virtualization, which is the process of combining hardware and software network resources and network functions into a single software-based management entity (virtual network). Network virtualization involves platform virtualization, which is often combined with resource virtualization. Network virtualization is classified as external network virtualization or internal network virtualization, where external network virtualization combines many networks or network parts into virtual units and internal network virtualization provides network-like functions to software containers on a single system. Note that the virtualized entities resulting from network virtualization are still implemented to some extent using hardware such as processors 152 or 175 and memories 155 and 171, and such virtualized entities also produce technical effects.

[0032] Computer readable memories 125, 155, and 171 may be of any type suitable for the local technical environment and may be implemented using any suitable data storage technology, such as semiconductor-based memory devices, flash memory, magnetic memory devices and systems, optical memory devices and systems, non-volatile memory and transient memory, fixed memory, and removable memory. Computer readable memories 125, 155, and 171 may be components for performing storage functions. Processors 120, 152, and 175 may be of any type suitable for the local technical environment, and may include, as non-limiting examples, one or more of the following: a general-purpose computer, a special-purpose computer, a microprocessor, a digital signal processor (DSP), and a processor based on a multi-core processor architecture. Processors 120, 152, and 175 may be components for performing functions such as controlling UE 110, RAN node 170, (multiple) network elements 190, and other functions described herein.

[0033] In general, various example embodiments of the user equipment 110 may include, but are not limited to, a cellular phone with wireless communication capabilities (such as a smart phone, a tablet computer, a personal digital assistant (PDA)), a portable computer with wireless communication capabilities, an image capture device with wireless communication capabilities (such as a digital camera), a gaming device with wireless communication capabilities, a music storage and playback device with wireless communication capabilities, an Internet device that allows wireless Internet access and browsing, a tablet computer with wireless communication capabilities, a head-mounted display (such as a display that implements virtual / augmented / mixed reality), and a portable unit or terminal that combines such functions. The UE 110 may also be a vehicle such as a car, or a UE installed in a vehicle, a UAV such as a drone, or a UE installed in a UAV. The user equipment 110 may be a terminal device, such as a mobile phone, a mobile device, a sensor device, etc., which is a device used by a user or not used by a user.

[0034] UE 110, RAN node 170 and / or network element(s) 190 (and associated memory, computer program code and modules) may be configured to implement (e.g., in part) the methods described herein, including PUCCH resources for msg4 HARQ feedback repetition. Thus, Figure 1 The computer program code 123, module 140-1, module 140-2 and other elements / features of the UE 110 shown may implement the user equipment related aspects of the examples described herein. Similarly, Figure 1 The computer program code 153, module 150-1, module 150-2, and other elements / features of the illustrated RAN node 170 may implement the example gNB / TRP-related aspects described herein. Figure 1The computer program code 173 and other elements / features of the illustrated network element(s) 190 may be configured to implement the example network element related aspects described herein.

[0035] Having thus introduced a suitable but non-limiting technical context for the practice of example embodiments, the example embodiments are now described in more detail.

[0036] In the RAN1#110 meeting, coverage enhancement for NTN was discussed with the conclusion of enhancing PUCCH for MSG4 HARQ-ACK. "RAN1 concluded that PUCCH for Msg4 HARQ-ACK should be enhanced to meet the coverage requirements of parameter set 1 for LEO-1200 operating in LOS" (quotation marks added for emphasis), assuming a UE antenna gain of -5dBi.

[0037] This is also reflected in the updated Rel-18 WID for NTN in RP-222654. The detailed goal is for NTN to "specify PUCCH enhancements for Msg4 HARQ-ACK (e.g., repetition) [RAN1, RAN4]" (quotation marks added for emphasis), and to study DMRS bundling for PUSCH, taking into account NTN's specifics (e.g., time-frequency pre-compensation), and to specify enhancements to Rel-17 procedures if necessary [RAN1].

[0038] PUCCH repetition for dedicated PUCCH resources has been introduced in Rel-17 coverage enhancement WI, where the possible number of repetitions is configured for each PUCCH resource, and the PUCCH resource indicator field in the DCI can indicate which resource to use, thereby indicating the number of repetitions to be applied.

[0039] TS 38.331 describes the PUCCH-Config information element (IE).IE The PUCCH-Config IE is used to configure UE-specific PUCCH parameters (for each BWP). Figure 2 An example PUCCH-Config information element 200 is shown, which is also shown below:

[0040]

[0041]

[0042] Figure 2A resourceSetToAddModList information element 202 and a resourceToAddMostListExt-v1610 information element 204 are further shown.

[0043] Figure 3 Also shown below is a PUCCH-Resource information element 300 , which includes a pucch-ResourceId syntax element 302 .

[0044]

[0045] Figure 4 Also shown below is a PUCCH-ResourceExt-v1610 information element 400 including a pucch-RepetitionNrofSlots-r17 syntax element 402 .

[0046]

[0047]

[0048] As indicated in TS 38.331:

[0049] "resourceToAddModList, resourceToAddModListExt, resourceToReleaseList

[0050] Lists are defined for adding and releasing PUCCH resources applicable to the UL BWP and the serving cell in which the PUCCH-Config is defined. The resources defined herein are referenced from other parts of the configuration to determine which resource the UE should use for which report. "If the network includes resourceToAddModListExt, it includes the same number of entries as in resourceToAddModList, listed in the same order as in resourceToAddModList (quotation marks ("") are used for emphasis)."

[0051] TS 38.213 describes the UE procedure for reporting HARQ-ACK as follows, with quotation marks ("") added:

[0052] "9.2.3 UE procedures for reporting HARQ-ACK

[0053] In this clause, for the purpose of using the “PUCCH resource indicator field in the DCI format for scheduling PDSCH reception” to determine the PUCCH resources used for PUCCH transmission in a timeslot, and for the purpose of determining a timeslot to be used for PUCCH transmission:

[0054] - The UE is assumed to generate HARQ-ACK information regardless of whether PDSCH reception provides transport blocks with disabled HARQ-ACK information for the HARQ process, as indicated by HARQ-feedbackEnabling-disablingperHARQprocess (if provided)

[0055] - It is assumed that the UE does not generate HARQ-ACK information associated with a G-RNTI or a G-CS-RNTI with HARQ-ACK information disabled, as described in clause 18. ”

[0056] TS 38.212 describes format 1_0 as follows, with quotation marks ("") added:

[0057] "7.3.1.2.1 Format 1_0

[0058] DCI format 1_0 is used for scheduling PDSCH in one DL cell.

[0059] …

[0060] "-PUCCH resource indicator - 3 bits, as defined in clause 9.2.3 of [5, TS 38.213]"

[0061] -PDSCH-to-HARQ_feedback timing indicator – 3 bits, as defined in clause 9.2.3 of [5, TS 38.213].

[0062] MSG3 repetition is also supported in Rel-17 coverage enhancement WI, including the description of PUSCH scheduled by RAR UL grant, as shown below (with quotation marks ("") added):

[0063] "8.3 PUSCH scheduled by RAR UL grant

[0064] …

[0065] The UE may be provided in RACH-ConfigCommon with a set of repetition numbers for PUSCH transmissions with PUSCH repetition type A scheduled by RAR UL grant or by DCI format 0_0 with CRC scrambled by TC-RNTI. If the UE requests repetitions for a PUSCH transmission [11, TS 38.321], then “UE PUSCH is sent on time slots, where Represented by the 2 MSBs of the MCS field in the RAR UL grant or DCI format 0_0, from the set of four values ​​provided by numberOfMsg3Repetitions, or if numberOfMsg3Repetitions is not provided, from {1, 2, 3, 4}". The UE determines the MCS for PUSCH transmission from the 2 LSBs of the MCS field in the RAR UL grant or from the 3 LSBs of the MCS field in DCI format 0_0, and determines the redundancy version and RBs to be used for each repetition as described in [6, TS 38.214]. For unpaired spectrum operation, the UE shall The time slot is determined as the previous time slot starting from time slot n+k2+Δ time slots, where the repetition of the PUSCH transmission does not include symbols indicated as downlink by tdd-UL-DL-ConfigurationCommon, nor does it include symbols of SS / PBCH blocks with indices provided by ssb-PositionsInBurst.

[0066] Type A refers to PUSCH transmission with PUSCH repetition type A: UE can send several repetitions of PUSCH in consecutive available time slots without feedback scheduled by UL grant or RRC. This method is called PUSCH repetition type A.

[0067] PUCCH repetition for MSG4 feedback before the UE has dedicated PUCCH configuration is not currently supported because the number of repetitions is configured in the dedicated PUCCH-Config. Before the UE has dedicated PUCCH resources, the UE shall perform the PUCCH repetition based on the table defined in 38.213 (as described herein and Figure 5 The PUCCH resource is determined by the index configured in the SIB:

[0068] TS 38.213 also describes PUCCH resource sets as follows, where quotation marks ("") are added for emphasis:

[0069] "9.2.1 PUCCH Resource Set

[0070] "If the UE does not have a dedicated PUCCH resource configuration provided by PUCCH-ResourceSet in PUCCH-Config, the PUCCH resource set is provided by pucch-ResourceCommon through an index to a row in Table 9.2.1-1 for use in For operation in FR2-2, pucch-ResourceCommon may also provide information for PUCCH resource set N. RB RBs; otherwise N RB =1.

[0071] …

[0072] If the UE is provided with PUCCH resources via pucch-ResourceCommon and useInterlacePUCCH-PUSCH in BWP-UplinkCommon:

[0073] -UE determines the interleaving index m for the PUCCH resource, such as where M is the number of interleavings [4, TS 38.211], and is the interleaving index offset, As given in Table 9.2.1-1;

[0074] -The UE determines the initial cyclic shift index in the set of initial cyclic shift indices as r PUCCH modN CS , where N CS is the total number of initial cyclic shift indices in the set of initial cyclic shift indices in Table 9.2.1-1;

[0075] - If pucch-ResourceCommon indicates:

[0076] - Index 0: If r PUCCH ≥10, then for PUCCH resources with PUCCH format 0, the first symbol is 9;

[0077] - Index 1 or 2: If r PUCCH =15, then for a PUCCH resource with PUCCH format 0, the first symbol is 9;

[0078] - Index 3, 7, or 11: If r PUCCH ≥10, then for PUCCH resources with PUCCH format 1, an orthogonal cover code with index 1 is used; otherwise, for PUCCH resources with PUCCH format 1, an orthogonal cover code with index 0 is used;

[0079] -The UE does not expect pucch-ResourceCommon to indicate index 15. "

[0080] Figure 5Table 9.2.1-1 in TS 38.213 is shown and is also given below (quotation marks ("") added for emphasis):

[0081] "Table 9.2.1-1: PUCCH resource set before dedicated PUCCH resource configuration"

[0082]

[0083]

[0084] The problem of how to define PUCCH resources for repetition to avoid collision with legacy UEs transmitting PUCCH and to mitigate or randomize inter-cell interference will be addressed to support PUCCH repetition for MSG4 HARQ-ACK before the UE has dedicated PUCCH resources configured.

[0085] Therefore, a method for determining PUCCH resources for repetition before the UE has a dedicated PUCCH configuration is described herein. In more detail, the following options may be separate options or may be combined together.

[0086] In one option, the PUCCH resources remain fixed, i.e., the same as provided in the DCI, for all PUCCH repetition transmissions. In this option, a PRB offset hopping pattern may be defined (e.g., in the specification, or provided in the configuration of common PUCCH resources) and applied for each repetition.

[0087] The PRB offset hopping pattern may be derived based at least in part on the cell ID:

[0088] mod(cell ID, 4) == 0, then the mode is {0, 1, 2, 3}

[0089] mod(cell ID, 4) == 1, then the mode is {1, 2, 3, 0}

[0090] mod(cell ID, 4) == 2, then the mode is {2, 3, 0, 1}

[0091] mod(cell ID, 4) == 3, then the mode is {3, 0, 1, 2}

[0092] In another option, the PUCCH resources are changed for each repeated transmission in a predetermined manner. In this option, a resource hopping pattern may be introduced.

[0093] The frequency hopping pattern can be fixed:

[0094] First transmission: according to the Δ in DCI PRIdetermined r_pucch(mod(r_pucch+n(0),16))

[0095] · Second transmission: confirmed r_pucchmod(r_pucch+n(1),16)

[0096] · Third transmission: confirmed r_pucchmod(r_pucch+n(2),16)

[0097] Fourth transmission: confirmed r_pucchmod(r_pucch+n(3), 16)

[0098] Where n = {0, 1, 2, 3} (then n(1) = 1, n(2) = 2, n(3) = 3)

[0099] Frequency hopping may be based in part on the cell ID, e.g.

[0100] n(0) in the above formula is mod(cell ID, 4)

[0101] · n(1) in the above formula is mod(cell ID+1,4)

[0102] n(2) in the above formula is mod(cell ID+2,4)

[0103] n(3) in the above formula is mod(cell ID+3,4)

[0104] For those indexed repetition resources and / or symbol offsets that do not use the entire slot, PRB offset hopping for each repetition may be introduced.

[0105] In yet another option, a new indication in the DCI that triggers HARQ ACK is used to indicate to the UE whether the starting symbol is 0 / 2 (which may be specified in the specification) or the value actually defined in the table (legacy starting symbol). In this option, if the DCI indicates starting symbol 0 / 2 for indexes 0 to 6 (or implicitly, e.g. based on whether Msg3 PUSCH is sent in a repeated manner), the UE determines that the starting symbol is 0 / 2, and the UE sends PUCCH resources in a repeated manner in the same slot.

[0106] For example, if the provided row index is 0, and the explicit indication (or implicit determination) indicates that the starting symbol is 2 (new behavior), the UE determines that there are multiple transmissions (repetitions) in this slot:

[0107] For example, if the row index is 0, 1, or 2, then 6 PUCCH transmissions

[0108] For example, if the row index is 3, 4, 5, or 6, then 3 PUCCH transmissions

[0109] To determine the number of repetitions to use for MSG4 HARQ-ACK before the UE has a dedicated PUCCH configuration, the following options may be considered:

[0110] In one option, the number of repetitions for MSG4 HARQ-ACK before the UE has a dedicated PUCCH configuration can be derived from the MSG3 repetitions indicated in the RAR UL grant. The same number of repetitions as for MSG3 can be used, or a specific number of ticks can be defined / configured. For example, the network can configure the number of repetitions to be less than or greater than the number of MSG3 repetitions indicated in the RAR UL grant or SIB. In one option, if no repetitions for MSG3 are indicated, the UE does not perform MSG4 HARQ-ACK repetitions.

[0111] Alternatively, the number of repetitions used for MSG4 HARQ-ACK before the UE has a dedicated PUCCH configuration can be explicitly indicated in the DCI scheduling MSG4 / MSGB or in the MSGB payload. It should be noted that if the DCI option is used for 2-step RACH (i.e., DCI schedules MSGB, the same number of repetitions is applied by the UE receiving the MSGB). In one option, before the UE has a dedicated PUCCH configuration, the current PUCCH resource indicator field can be reused with a different interpretation, for example, mapping the number of repetitions to each value that is predefined or preconfigured in the SIB. In one option, the number of repetitions is indicated in the DCI scheduling MSGB, and the applicability of the MSGB HARQ-ACK repetition is indicated for each UE in the MSGB payload.

[0112] PUCCH repetitions can be in consecutive slots or in the same pattern as MSG3 repetitions. Only valid slots are considered (e.g., in the case of TDD). When repetitions collide with DL slots, they are dropped or postponed to the next valid slot. The number of repetitions can be associated with an index (e.g., through SIB signaling), and the index is indicated to the UE in the above manner, based on which the UE derives the number of repetitions.

[0113] Advantages and technical effects of the examples described herein include supporting PUCCH repetition for MSG4 HARQ-Ack preceding dedicated PUCCH configuration without conflicting with legacy common PUCCH resources. The examples described herein may be adopted and specified in TS 38.331 and / or TS 38.213.

[0114] Figure 6600 is an example apparatus, which may be implemented in hardware, configured to implement the examples described herein. The apparatus 600 includes at least one processor 602 (e.g., an FPGA and / or a CPU), at least one memory 604 including computer program code 605, wherein the at least one memory 604 and the computer program code 605 are configured to, together with the at least one processor 602, cause the apparatus 600 to implement circuit systems, processes, components, modules, or functions (collectively referred to as controls 606) to implement the examples described herein, including PUCCH resources for msg4 HARQ feedback repetition. The memory 604 may be a non-volatile memory, a transient memory, a volatile memory (e.g., a RAM), or a non-volatile memory (e.g., a ROM).

[0115] The device 600 optionally includes a display and / or I / O interface 608, which can be used to display aspects or states of the methods described herein (e.g., while one of the methods is being performed or at a subsequent time), or to receive input from a user, such as input using a keypad, camera, touch screen, touch area, microphone, biometrics, one or more sensors, etc. The device 600 includes one or more communication (e.g., network (N / W)) interfaces ((multiple) I / Fs) 610. The (multiple) communication I / Fs 610 can be wired and / or wireless and communicate over the Internet / (multiple) other networks via any communication technology. The (multiple) communication I / Fs 610 can include one or more transmitters and one or more receivers. The (multiple) communication I / Fs 610 can include standard well-known components such as amplifiers, filters, frequency converters, modulators (demodulators) and encoder / decoder circuit systems and one or more antennas.

[0116] The apparatus 600 implementing the functionality of the control 606 may be a UE 110, a RAN node 170 (e.g., a gNB), or a network element (s) 190. Thus, the processor 602 may correspond to the processor (s) 120, the processor (s) 152, and / or the processor (s) 175, the memory 604 may correspond to the memory (s) 125, the memory (s) 155, and / or the memory (s) 171, the computer program code 605 may correspond to the computer program code 123, the module 140-1, the module 140-2, and / or the computer program code 153, the module 150-1, the module 150-2, and / or the computer program code 173, and the communication I / F (s) 610 may correspond to the transceiver 130, the antenna (s) 128, the transceiver 160, the antenna (s) 158, the N / WI / F (s) 161, and / or the N / WI / F (s) 180. Alternatively, apparatus 600 may not correspond to any of UE 110, RAN node 170, or network element(s) 190, as apparatus 600 may be part of a Self-Organizing / Optimizing Network (SON) node, such as in the cloud.

[0117] The apparatus 600 may also be distributed throughout the network (eg, 100 ), including within and between the apparatus 600 and any network elements, such as a network control element (NCE) 190 and / or a RAN node 170 and / or a UE 110 .

[0118] like Figure 6 As shown, interface 612 enables data communication between various items of device 600. For example, interface 612 can be one or more buses, such as address, data or control buses, and can include any interconnection mechanism, such as a series of lines on a motherboard or integrated circuit, optical fiber or other optical communication devices, etc. Computer program code (e.g., instructions) 605 including control 606 can include object-oriented software that is configured to pass data or messages between objects within computer program code 605. Device 600 need not include each of the above features, or may also include other features.

[0119] Figure 7 Schematic diagrams of non-volatile storage media 700a (e.g., a computer optical disc / compact disk (CD) or digital versatile disc (DVD)) and 700b (e.g., a universal serial bus (USB) memory stick) storing instructions and / or parameters 702 that, when executed by a processor, enable the processor to perform one or more of the steps of the methods described herein.

[0120] Figure 8The present invention is an example method 800 for implementing the example embodiments described herein. At 810, the method includes receiving a message using a physical downlink shared channel. At 820, the method includes determining a physical uplink control channel resource for transmission of a hybrid automatic repeat request acknowledgment based on the message received using the physical downlink shared channel. At 830, the method includes wherein the physical uplink control channel resource is used for repetition of the transmission. At 840, the method includes sending a hybrid automatic repeat request acknowledgment using the determined physical uplink control channel resource for repetition. The method 800 may be performed using the UE 110 or the apparatus 600.

[0121] Fig. 9 The present invention is an example method 900 for implementing the example embodiments described herein. At 910, the method includes sending a message using a physical downlink shared channel. At 920, the method includes receiving a hybrid automatic repeat request acknowledgment using a physical uplink control channel resource, the hybrid automatic repeat request acknowledgment being received based on the message sent using the physical downlink shared channel. At 930, the method includes wherein the physical uplink control channel resource is used for repetition of the transmission. At 940, the method includes wherein the hybrid automatic repeat request acknowledgment is received using the physical uplink control channel resource for repetition in the case where a dedicated physical uplink control channel configuration has not been sent. The method 900 may be performed using the RAN node 170, the network element(s) 190, or the apparatus 600.

[0122] The following examples are provided and described herein.

[0123] Example 1. A device comprising: at least one processor; and at least one memory storing instructions which, when executed by the at least one processor, cause the device to at least: receive a message using a physical downlink shared channel; determine a physical uplink control channel resource for transmission of a hybrid automatic repeat request acknowledgment based on the message received using the physical downlink shared channel; wherein the physical uplink control channel resource is used for repetition of the transmission; and send a hybrid automatic repeat request acknowledgment using the determined physical uplink control channel resource for repetition.

[0124] Example 2. An apparatus according to Example 1, wherein the apparatus is further caused to: determine physical uplink control channel resources for repetition when a dedicated physical uplink control channel configuration has not been received.

[0125] Example 3. An apparatus according to any one of Examples 1 to 2, wherein a physical uplink control channel resource is fixed for physical uplink control channel repeated transmissions.

[0126] Example 4. An apparatus according to Example 3, wherein the apparatus is caused to: receive downlink control information including physical uplink control channel resources.

[0127] Example 5. An apparatus according to any one of Examples 3 to 4, wherein the apparatus is caused to: determine a repeated physical resource block offset hopping pattern for repeated transmission of a physical uplink control channel; and apply the repeated physical resource block offset hopping pattern.

[0128] Example 6. The apparatus of Example 5, wherein the physical resource block hopping pattern is predefined or provided within the configuration of the common physical uplink control channel resources.

[0129] Example 7. An apparatus according to any one of Examples 5 to 6, wherein the apparatus is caused to: determine a physical resource block hopping pattern based at least in part on a cell identifier.

[0130] Example 8. An apparatus according to Example 7, wherein the apparatus is caused to: determine a remainder of dividing a cell identifier by an integer using a modulo function; and determine a physical resource block hopping pattern as a set of values, the set of values ​​being based on determining the remainder using the modulo function.

[0131] Example 9. An apparatus according to any one of Examples 1 to 8, wherein a physical uplink control channel resource is changed for a corresponding physical uplink control channel repetition transmission in a plurality of physical uplink control channel repetition transmissions.

[0132] Example 10. An apparatus according to Example 9, wherein the apparatus is caused to: determine repeated physical uplink control channel resources for repeated transmission of the physical uplink control channel based on a resource offset indicator in the downlink control information.

[0133] Example 11. An apparatus according to any one of Examples 9 to 10, wherein the apparatus is configured to: determine a frequency hopping pattern for physical uplink control channel resources; and determine physical uplink control channel resources for repeated transmission based on the frequency hopping pattern.

[0134] Example 12. The apparatus of Example 11, wherein the apparatus is caused to: determine the frequency hopping pattern based at least in part on the cell identifier.

[0135] Example 13. An apparatus according to any one of Examples 9 to 12, wherein the apparatus is configured to: determine an initial value by adding a resource value associated with a physical uplink control channel resource to an output of a function given by a first integer; determine a remainder of the initial value divided by a second integer by a modulo function; and determine the physical uplink control channel resource based on the remainder determined by the modulo function.

[0136] Example 14. An apparatus according to Example 13, wherein the apparatus is caused to: determine the other value by dividing the cell identifier by a third integer; wherein the output of the function given by the first integer includes the other value.

[0137] Example 15. An apparatus according to any one of Examples 9 to 14, wherein the apparatus is caused to: determine a repeated physical resource block offset hopping pattern for repeated transmission of a physical uplink control channel; and apply the repeated physical resource block offset hopping pattern.

[0138] Example 16. An apparatus according to any one of Examples 9 to 15, wherein the apparatus is configured to: determine a symbol offset for an index associated with the physical uplink control channel resource without using an entire time slot.

[0139] Example 17. An apparatus according to any one of Examples 1 to 16, wherein the apparatus is configured to: receive downlink control information, the downlink control information being configured to trigger the transmission of a hybrid automatic repeat request acknowledgment; wherein the downlink control information indicates a start symbol; and based on the start symbol, repeatedly sending repeated transmissions using physical uplink control channel resources within a time slot.

[0140] Example 18. An apparatus according to Example 17, wherein: the downlink control information explicitly indicates a starting symbol; or the downlink control information implicitly indicates a starting symbol based on whether a message for a physical uplink shared channel is repeatedly sent.

[0141] Example 19. An apparatus according to any one of Examples 17 to 18, wherein the starting symbol is 0 or 2.

[0142] Example 20. An apparatus according to any one of Examples 17 to 19, wherein the apparatus is configured to: receive a row index using downlink control information; and determine the number of times a physical uplink control channel is repeatedly transmitted based at least in part on the row index.

[0143] Example 21. A device comprising: at least one processor; and at least one memory storing instructions which, when executed by the at least one processor, cause the device to at least: send a message using a physical downlink shared channel; and receive a hybrid automatic repeat request acknowledgment using physical uplink control channel resources, the hybrid automatic repeat request acknowledgment being received based on the message sent using the physical downlink shared channel; wherein the physical uplink control channel resources are used for repetition of transmission; wherein the hybrid automatic repeat request acknowledgment is received using the physical uplink control channel resources used for repetition when a dedicated physical uplink control channel configuration has not yet been sent.

[0144] Example 22. The apparatus of Example 21, wherein the physical uplink control channel resources are fixed for physical uplink control channel repetition transmissions.

[0145] Example 23. An apparatus according to Example 22, wherein the apparatus is caused to: send downlink control information including physical uplink control channel resources.

[0146] Example 24. An apparatus according to any one of Examples 22 to 23, wherein the apparatus is caused to: receive repetitions of physical uplink control channel repetition transmissions based on a physical resource block offset hopping pattern.

[0147] Example 25. An apparatus according to Example 24, wherein the apparatus is caused to: send a configuration of common physical uplink control channel resources, the configuration comprising a physical resource block hopping pattern.

[0148] Example 26. An apparatus according to any one of Examples 24 to 25, wherein the physical resource block hopping pattern is predefined.

[0149] Example 27. An apparatus according to any one of Examples 24 to 26, wherein the physical resource block hopping pattern is based at least in part on a cell identifier.

[0150] Example 28. The apparatus of Example 27, wherein the physical resource block hopping pattern comprises a set of values, the set of values ​​being based on a modulo function, the output of the modulo function being a remainder of a cell identifier divided by an integer.

[0151] Example 29. An apparatus according to any one of Examples 21 to 28, wherein a physical uplink control channel resource is changed for a corresponding physical uplink control channel repetition transmission in a plurality of physical uplink control channel repetition transmissions.

[0152] Example 30. An apparatus according to Example 29, wherein the apparatus is configured to: send downlink control information including a resource offset indicator; and receive repetitions of physical uplink control channel repetition transmissions using physical uplink control channel resources based on the resource offset indicator in the downlink control information.

[0153] Example 31. An apparatus according to any one of Examples 29 to 30, wherein the apparatus is caused to: receive repetitions of physical uplink control channel repeated transmissions based on a frequency hopping pattern associated with a physical uplink control channel resource.

[0154] Example 32. The apparatus of Example 31, wherein the frequency hopping pattern is based at least in part on a cell identifier.

[0155] Example 33. An apparatus according to any one of Examples 29 to 32, wherein a physical uplink control channel resource is based on a modulo function that determines a remainder of an initial value divided by a first integer, wherein the initial value is based on adding a resource value associated with the physical uplink control channel resource to the output of a function given by a second integer.

[0156] Example 34. The apparatus of Example 33, wherein the output of the function given by the second integer comprises another value based on the cell identifier divided by the third integer.

[0157] Example 35. An apparatus according to any one of Examples 29 to 34, wherein the apparatus is configured to: receive repetitions of physical uplink control channel repetition transmissions based on a physical resource block offset hopping pattern.

[0158] Example 36. An apparatus according to any one of Examples 29 to 35, wherein a symbol offset for an index is associated with the physical uplink control channel resource without using an entire time slot.

[0159] Example 37. An apparatus according to any one of Examples 21 to 36, wherein the apparatus is configured to: send downlink control information, the downlink control information being configured to trigger the transmission of a hybrid automatic repeat request acknowledgment; wherein the downlink control information indicates a start symbol; and based on the start symbol, repeatedly utilizing physical uplink control channel resources within a time slot to receive repeated transmissions.

[0160] Example 38. An apparatus according to Example 37, wherein: the downlink control information explicitly indicates a starting symbol; or the downlink control information implicitly indicates a starting symbol based on whether a message for a physical uplink shared channel is repeatedly sent.

[0161] Example 39. An apparatus according to any one of Examples 37 to 38, wherein the starting symbol is 0 or 2.

[0162] Example 40. An apparatus according to any one of Examples 37 to 39, wherein the apparatus is configured to: send a row index using downlink control information; wherein the number of times a physical uplink control channel is repeated is at least partially based on the row index.

[0163] Example 41. A method comprising: receiving a message using a physical downlink shared channel; determining a physical uplink control channel resource for transmission of a hybrid automatic repeat request acknowledgment based on the message received using the physical downlink shared channel; wherein the physical uplink control channel resource is used for repetition of the transmission; and sending a hybrid automatic repeat request acknowledgment using the determined physical uplink control channel resource for repetition.

[0164] Example 42. A method comprising: sending a message using a physical downlink shared channel; and receiving a hybrid automatic repeat request acknowledgment using a physical uplink control channel resource, wherein the hybrid automatic repeat request acknowledgment is received based on the message sent using the physical downlink shared channel; wherein the physical uplink control channel resources are used for repetition of transmission; wherein the hybrid automatic repeat request acknowledgment is received using the physical uplink control channel resources used for repetition when a dedicated physical uplink control channel configuration has not yet been sent.

[0165] Example 43. An apparatus comprising: a component for receiving a message using a physical downlink shared channel; a component for determining a physical uplink control channel resource for transmission of a hybrid automatic repeat request acknowledgment based on the message received using the physical downlink shared channel; wherein the physical uplink control channel resource is used for repetition of the transmission; and a component for sending a hybrid automatic repeat request acknowledgment using the determined physical uplink control channel resource for repetition.

[0166] Example 44. An apparatus comprising: a component for sending a message using a physical downlink shared channel; and a component for receiving a hybrid automatic repeat request confirmation using a physical uplink control channel resource, the hybrid automatic repeat request confirmation being received based on the message sent using the physical downlink shared channel; wherein the physical uplink control channel resources are used for repetition of transmission; wherein the hybrid automatic repeat request confirmation is received using the physical uplink control channel resources used for repetition when a dedicated physical uplink control channel configuration has not yet been sent.

[0167] Example 45. A machine-readable, non-volatile program storage device tangibly embodies a machine-executable instruction program for performing operations, the operations comprising: receiving a message using a physical downlink shared channel; determining a physical uplink control channel resource for transmission of a hybrid automatic repeat request acknowledgment based on the message received using the physical downlink shared channel; wherein the physical uplink control channel resource is used for repetition of the transmission; and sending a hybrid automatic repeat request acknowledgment using the determined physical uplink control channel resource for repetition.

[0168] Example 46. A machine-readable, non-volatile program storage device, tangibly implementing a machine-executable instruction program for performing operations, the operations comprising: sending a message using a physical downlink shared channel; and receiving a hybrid automatic repeat request acknowledgment using a physical uplink control channel resource, the hybrid automatic repeat request acknowledgment being received based on the message sent using the physical downlink shared channel; wherein the physical uplink control channel resources are used for repetition of transmission; wherein the hybrid automatic repeat request acknowledgment is received using the physical uplink control channel resources used for repetition when a dedicated physical uplink control channel configuration has not yet been sent.

[0169] References to "computers," "processors," and the like should be understood to cover not only computers having different architectures (such as single / multi-processor architectures and sequential or parallel architectures), but also special purpose circuits such as field programmable gate arrays (FPGAs), application specific circuits (ASICs), signal processing devices, and other processing circuit systems. References to computer programs, instructions, code, and the like should be understood to cover software or firmware for programmable processors, such as, for example, the programmable content of hardware devices, whether instructions for a processor, or configuration settings for a fixed function device, gate array, or programmable logic device, and the like.

[0170] The memory(s) described herein may be implemented using any suitable data storage technology, such as semiconductor-based memory devices, flash memory, magnetic memory devices and systems, optical memory devices and systems, non-volatile memory, transient memory, fixed memory, and removable memory. The memory(s) may include a database for storing data.

[0171] As used herein, the term "circuitry" may refer to the following: (a) hardware circuit implementations, such as implementations in analog and / or digital circuitry, and (b) combinations of circuitry and software (and / or firmware), such as, as applicable: (i) a combination of (multiple) processors, or (ii) portions of (multiple) processors / software (including (multiple) digital signal processors, software, and (multiple) memories), which work together to enable the device to perform various functions, and (c) circuits that require software or firmware to operate (even if the software or firmware is not physically present), such as (multiple) microprocessors or portions of (multiple) microprocessors. As a further example, as used herein, the term "circuitry" would also cover implementations of only a processor (or multiple processors) or a portion of a processor and its accompanying software and / or firmware. For example, if applicable to the particular element, the term "circuitry" would also cover a baseband integrated circuit or application processor integrated circuit for a mobile phone, or a similar integrated circuit in a server, cellular network device, or another network device.

[0172] In the figure, arrows between individual boxes indicate the coupling of operations between them, and the direction of data flow over these couplings.

[0173] It should be understood that the above description is illustrative only. Those skilled in the art may design various alternatives and modifications. For example, the features described in the various dependent claims may be combined with each other in any suitable (multiple) combinations. In addition, the features from different example embodiments described above may be selectively combined into new example embodiments. Therefore, this specification is intended to cover all such alternatives, modifications and variations that fall within the scope of the appended claims.

[0174] The following abbreviations and abbreviations that may appear in the specification and / or drawings are given below (abbreviations and abbreviations may be appended to each other or to other characters using, for example, dashes, hyphens or numbers, etc.):

[0175] 4G Fourth Generation

[0176] 5G Fifth Generation

[0177] 5GC 5G Core Network

[0178] ACK

[0179] AMF Access and Mobility Management Function

[0180] ASIC Application-Specific Integrated Circuit

[0181] BWP Bandwidth Part

[0182] CD / Computer CD

[0183] Config

[0184] CPU Central Processing Unit

[0185] CRC Cyclic Redundancy Check

[0186] CS cyclic shift

[0187] CU Central Unit or Centralized Unit

[0188] DCI Downlink Control Information

[0189] DL or dl downlink

[0190] DMRS Demodulation Reference Symbol

[0191] DSP Digital Signal Processor

[0192] DVD Digital Versatile Disc

[0193] EDGE Enhanced Data Rates for GSM Evolution

[0194] eNB Evolved Node B (e.g., LTE base station)

[0195] EN-DC E-UTRAN New Radio - Dual Connectivity

[0196] en-gNB A node that provides NR user plane and control plane protocol termination towards the UE and acts as a secondary node in EN-DC

[0197] E-UTRA Evolved Universal Terrestrial Radio Access, i.e. LTE radio access technology

[0198] E-UTRAN E-UTRA Network

[0199] F1 Interface between CU and DU

[0200] FPGA Field Programmable Gate Array

[0201] FR Frequency Range

[0202] G GERAN

[0203] GERAN GSM EDGE Radio Access Network

[0204] GSM Global System for Mobile Communications

[0205] gNB is a base station for 5G / NR, i.e., a node that provides NR user plane and control plane protocol termination towards the UE and is connected to the 5GC via the NG interface

[0206] HARQ Hybrid Automatic Repeat Request

[0207] IAB Integrated Access and Backhaul

[0208] ID Identifier

[0209] I / F Interface

[0210] I / O Input / Output

[0211] LEO Low Earth Orbit

[0212] LMF Location Management Function

[0213] LOS Line of Sight

[0214] LSB Least Significant Bit

[0215] LTE Long Term Evolution (4G)

[0216] MAC Media Access Control

[0217] MCS Modulation Coding Scheme

[0218] MME Mobility Management Entity

[0219] MRO Mobility Robustness Optimization

[0220] MSB Most Significant Bit

[0221] MSG3 or Msg3 The third message in the random access response process

[0222] MSG4 or Msg4 The fourth message in the random access response process

[0223] MSGB Message b in random access response process

[0224] NCE Network Control Element

[0225] ng or NG new generation

[0226] ng-eNB Next Generation eNB

[0227] NG-RAN Next Generation Radio Access Network

[0228] NR New Radio (5G)

[0229] NTN Non-Terrestrial Network

[0230] N / W Network

[0231] PBCH Physical Broadcast Channel

[0232] PDA Personal Digital Assistant

[0233] PDCP Packet Data Convergence Protocol

[0234] PDSCH Physical Downlink Shared Channel

[0235] PHY Physical Layer

[0236] PRB Physical Resource Block

[0237] PRI Resource offset indicator, or the value of the bit indicator

[0238] PUCCH Physical Uplink Control Channel

[0239] PUSCH Physical Uplink Shared Channel

[0240] RACH Random Access Channel

[0241] RAM Random Access Memory

[0242] RAN Radio Access Network

[0243] RAN1 Radio Layer 1

[0244] RAN4 Radio Layer 4

[0245] RAR Random Access Response

[0246] RB or rb resource block

[0247] Rel- version

[0248] RLC Radio Link Control

[0249] RNTI Radio Network Temporary Identifier

[0250] ROM Read Only Memory

[0251] RP RAN Conference

[0252] r_pucch or r PUCCH PUCCH resource index

[0253] RRC Radio Resource Control (protocol)

[0254] RU Radio Unit

[0255] Rx Receiver or Receiver

[0256] SA system aspects

[0257] SGW Service Gateway

[0258] SIB System Information Block

[0259] SMF session management functions

[0260] SON self-organizing / optimizing network

[0261] SS Sync Signal

[0262] Ssb Synchronous Signal Block

[0263] TC Temporary Community

[0264] TDD or TDD time division duplex

[0265] TRP Transmission Reception Point

[0266] TS Technical Specifications

[0267] Tx Transmitter or Transmit

[0268] UAV

[0269] UE User Equipment (e.g., wireless device, typically a mobile device)

[0270] UL Uplink

[0271] UPF User Plane Function

[0272] USB Universal Serial Bus

[0273] WI Work Item

[0274] WID Work Item Description

[0275] X2 Network interface between RAN nodes and between RAN and core network

[0276] Xn Network interface between NG-RAN nodes

Claims

1. A device comprising: at least one processor; as well as at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus to at least: receiving a message using a physical downlink shared channel; determining, based on the message received using the physical downlink shared channel, physical uplink control channel resources to be used for transmission of a hybrid automatic repeat request acknowledgement; wherein the physical uplink control channel resources are used for repetition of transmission; as well as The hybrid automatic repeat request acknowledgement is sent using the determined physical uplink control channel resources for repetition.

2. The apparatus according to claim 1, wherein the apparatus is further configured to: In case a dedicated physical uplink control channel configuration has not been received, the physical uplink control channel resources for repetition are determined.

3. The apparatus according to any one of claims 1 to 2, wherein the physical uplink control channel resource is fixed for physical uplink control channel repetitive transmission.

4. The apparatus according to claim 3, wherein the apparatus is configured to: Downlink control information including the physical uplink control channel resources is received.

5. The device according to any one of claims 3 to 4, wherein the device is configured to: determining a repeated physical resource block offset hopping pattern for repeated transmission of the physical uplink control channel; and The physical resource block offset hopping pattern for the repetition is applied.

6. The apparatus of claim 5, wherein the physical resource block frequency hopping pattern is predefined or provided within the configuration of a common physical uplink control channel resource.

7. The device according to any one of claims 5 to 6, wherein the device is configured to: The physical resource block frequency hopping pattern is determined based at least in part on a cell identifier.

8. The apparatus according to claim 7, wherein the apparatus is caused to: determining a remainder when the cell identifier is divided by an integer using a modulo function; and The physical resource block hopping pattern is determined as a set of values ​​based on the determination of the remainder using the modulo function.

9. The apparatus according to any one of claims 1 to 8, wherein the physical uplink control channel resource is changed for a corresponding physical uplink control channel repetition transmission in a plurality of physical uplink control channel repetition transmissions.

10. The apparatus according to claim 9, wherein the apparatus is caused to: The physical uplink control channel resource for repetition of the physical uplink control channel repetition transmission is determined based on a resource offset indicator in downlink control information.

11. The device according to any one of claims 9 to 10, wherein the device is configured to: determining a frequency hopping pattern for the physical uplink control channel resources; and The physical uplink control channel resources for repeated transmission are determined based on the frequency hopping pattern.

12. The apparatus according to claim 11, wherein the apparatus is caused to: The frequency hopping pattern is determined based at least in part on a cell identifier.

13. The device according to any one of claims 9 to 12, wherein the device is configured to: determining an initial value by adding a resource value associated with the physical uplink control channel resource to an output of a function given by a first integer; Determining a remainder when the initial value is divided by a second integer using a modulo function; The physical uplink control channel resource is determined based on the remainder determined using the modulo function.

14. The apparatus according to claim 13, wherein the apparatus is caused to: determining another value by dividing the cell identifier by a third integer; wherein the output of the function given by means of the first integer comprises the further value.

15. The apparatus according to any one of claims 9 to 14, wherein the apparatus is configured to: determining a repeated physical resource block offset hopping pattern for repeated transmission of the physical uplink control channel; and The physical resource block offset hopping pattern for the repetition is applied.

16. The apparatus according to any one of claims 9 to 15, wherein the apparatus is configured to: A symbol offset for an index associated with the physical uplink control channel resource is determined without using an entire time slot.

17. The device according to any one of claims 1 to 16, wherein the device is configured to: receiving downlink control information configured to trigger transmission of the hybrid automatic repeat request acknowledgement; wherein the downlink control information indicates a start symbol; and Based on the starting symbol, repeated transmissions are sent repeatedly using the physical uplink control channel resources within a time slot.

18. The device according to claim 17, wherein: The downlink control information explicitly indicates the starting symbol; or The downlink control information implicitly indicates the starting symbol based on whether a message for a physical uplink shared channel is repeatedly transmitted.

19. The apparatus according to any one of claims 17 to 18, wherein the starting symbol is 0 or 2.

20. The apparatus according to any one of claims 17 to 19, wherein the apparatus is configured to: receiving a row index using the downlink control information; and A number of physical uplink control channel repetition transmissions is determined based at least in part on the row index.

21. An apparatus comprising: at least one processor; as well as at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus to at least: Sending a message using a physical downlink shared channel; as well as receiving a hybrid automatic repeat request acknowledgment using a physical uplink control channel resource, the hybrid automatic repeat request acknowledgment being received based on the message sent using the physical downlink shared channel; wherein the physical uplink control channel resources are used for repetition of transmission; Wherein the hybrid automatic repeat request confirmation is received using the physical uplink control channel resources for repetition in case a dedicated physical uplink control channel configuration has not been sent.

22. The apparatus of claim 21, wherein the physical uplink control channel resources are fixed for physical uplink control channel repetitive transmissions.

23. The apparatus of claim 22, wherein the apparatus is caused to: Downlink control information including the physical uplink control channel resources is sent.

24. The apparatus according to any one of claims 22 to 23, wherein the apparatus is configured to: Repetitions of the physical uplink control channel repetition transmission are received based on a physical resource block offset hopping pattern.

25. The apparatus of claim 24, wherein the apparatus is caused to: A configuration of common physical uplink control channel resources is transmitted, the configuration comprising the physical resource block frequency hopping pattern.

26. The apparatus according to any one of claims 24 to 25, wherein the physical resource block frequency hopping pattern is predefined.

27. The apparatus of any one of claims 24 to 26, wherein the physical resource block hopping pattern is based at least in part on a cell identifier.

28. The apparatus of claim 27, wherein the physical resource block hopping pattern comprises a set of values, the set of values ​​being based on a modulo function, the output of the modulo function being a remainder of dividing the cell identifier by an integer.

29. The apparatus according to any one of claims 21 to 28, wherein the physical uplink control channel resources are changed for respective physical uplink control channel repetition transmissions of a plurality of physical uplink control channel repetition transmissions.

30. The apparatus of claim 29, wherein the apparatus is caused to: sending downlink control information including a resource offset indicator; Repetitions of the physical uplink control channel repetition transmissions are received using the physical uplink control channel resources based on the resource offset indicator in the downlink control information.

31. The apparatus according to any one of claims 29 to 30, wherein the apparatus is configured to: Repetitions of the physical uplink control channel repetitive transmissions are received based on a frequency hopping pattern associated with the physical uplink control channel resources.

32. The apparatus of claim 31, wherein the frequency hopping pattern is based at least in part on a cell identifier.

33. An apparatus according to any one of claims 29 to 32, wherein the physical uplink control channel resource is based on a modulo function that determines the remainder of an initial value divided by a first integer, wherein the initial value is based on adding a resource value associated with the physical uplink control channel resource to the output of a function given by a second integer.

34. The apparatus of claim 33, wherein the output of the function given by the second integer comprises another value based on a cell identifier divided by a third integer.

35. The apparatus according to any one of claims 29 to 34, wherein the apparatus is configured to: Repetitions of the physical uplink control channel repetition transmission are received based on a physical resource block offset hopping pattern.

36. The apparatus of any one of claims 29 to 35, wherein a symbol offset for an index is associated with the physical uplink control channel resource without using an entire time slot.

37. The apparatus according to any one of claims 21 to 36, wherein the apparatus is configured to: sending downlink control information, the downlink control information being configured to trigger transmission of the hybrid automatic repeat request acknowledgement; wherein the downlink control information indicates a start symbol; and Based on the starting symbol, repeated transmissions are received repeatedly utilizing the physical uplink control channel resources within a time slot.

38. The apparatus of claim 37, wherein: The downlink control information explicitly indicates the starting symbol; or The downlink control information implicitly indicates the starting symbol based on whether a message for a physical uplink shared channel is repeatedly transmitted.

39. The apparatus according to any one of claims 37 to 38, wherein the starting symbol is 0 or 2.

40. The apparatus according to any one of claims 37 to 39, wherein the apparatus is configured to: sending a row index using the downlink control information; The number of times the physical uplink control channel is repeated is based at least in part on the row index.

41. A method comprising: receiving a message using a physical downlink shared channel; determining, based on the message received using the physical downlink shared channel, physical uplink control channel resources to be used for transmission of a hybrid automatic repeat request acknowledgement; wherein the physical uplink control channel resources are used for repetition of transmission; as well as The hybrid automatic repeat request acknowledgement is sent using the determined physical uplink control channel resources for repetition.

42. A method comprising: Sending a message using a physical downlink shared channel; as well as receiving a hybrid automatic repeat request acknowledgment using a physical uplink control channel resource, the hybrid automatic repeat request acknowledgment being received based on the message sent using the physical downlink shared channel; wherein the physical uplink control channel resources are used for repetition of transmission; Wherein the hybrid automatic repeat request confirmation is received using the physical uplink control channel resources for repetition in case a dedicated physical uplink control channel configuration has not been sent.

43. An apparatus comprising: means for receiving a message using a physical downlink shared channel; means for determining physical uplink control channel resources to be used for transmission of a hybrid automatic repeat request acknowledgement based on said message received using said physical downlink shared channel; wherein the physical uplink control channel resources are used for repetition of transmission; as well as Means for sending the hybrid automatic repeat request acknowledgement using the physical uplink control channel resources determined for repeating.

44. An apparatus comprising: means for sending a message using a physical downlink shared channel; as well as means for receiving a hybrid automatic repeat request acknowledgment using a physical uplink control channel resource, the hybrid automatic repeat request acknowledgment being received based on the message sent using the physical downlink shared channel; wherein the physical uplink control channel resources are used for repetition of transmission; Wherein the hybrid automatic repeat request confirmation is received using the physical uplink control channel resources for repetition in case a dedicated physical uplink control channel configuration has not been sent.

45. A non-transitory program storage device readable by a machine, tangibly embodying a program of instructions executable by the machine for performing operations comprising: receiving a message using a physical downlink shared channel; determining, based on the message received using the physical downlink shared channel, physical uplink control channel resources to be used for transmission of a hybrid automatic repeat request acknowledgement; wherein the physical uplink control channel resources are used for repetition of transmission; as well as The hybrid automatic repeat request acknowledgement is sent using the determined physical uplink control channel resources for repetition.

46. ​​A non-transitory program storage device readable by a machine, tangibly embodying a program of instructions executable by the machine for performing operations comprising: Sending a message using a physical downlink shared channel; as well as receiving a hybrid automatic repeat request acknowledgment using a physical uplink control channel resource, the hybrid automatic repeat request acknowledgment being received based on the message sent using the physical downlink shared channel; wherein the physical uplink control channel resources are used for repetition of transmission; Wherein the hybrid automatic repeat request confirmation is received using the physical uplink control channel resources for repetition in case a dedicated physical uplink control channel configuration has not been sent.

Images