Method and system for physical uplink control channel repetition indication

Abstract

Systems and methods for physical uplink control channel (PUCCH) repetition indication are presented. A wireless communication device. A wireless communication node. A wireless communication device (e.g., a user equipment (UE)) can transmit a message to a wireless communication node indicating a capability of the wireless communication device to perform PUCCH repetition. The PUCCH repetition can include at least one repetition of a PUCCH transmission on a common PUCCH resource. The wireless communication node can receive the message indicating the capability of the wireless communication device to perform PUCCH repetition.

Description

Technical Field

[0001] This disclosure relates generally to wireless communications, including but not limited to systems and methods for indications related to repetition of physical uplink control channels. Background Technology

[0002] The standards organization Third Generation Partnership Project (3GPP) is currently developing a new air interface called 5G New Radio (5G NR) and a Next Generation Packet Core Network (NG-CN or NGC). 5G NR will consist of three main components: the 5G Access Network (5G-AN), the 5G Core Network (5GC), and User Equipment (UE). To facilitate the implementation of different data services and needs, the network elements (also known as network functions) of the 5GC have been simplified, with some based on software and others on hardware, so that they can be adapted as needed. Summary of the Invention

[0003] The exemplary embodiments disclosed herein are intended to address problems related to one or more issues raised in the prior art, and to provide additional features that will become apparent from the following detailed description taken in conjunction with the accompanying drawings. Example systems, methods, apparatuses, and computer program products are disclosed herein according to various embodiments. However, it should be understood that these embodiments are presented by way of example and not limitation, and various modifications to the disclosed embodiments will be apparent to those skilled in the art who read this disclosure while remaining within the scope of this disclosure.

[0004] At least one aspect relates to a system, method, apparatus, or computer-readable medium that may relate to a wireless communication node (e.g., a base station) interacting with a wireless communication device (e.g., a user equipment). The wireless communication device may send a message to the wireless communication node instructing / reporting the wireless communication device's ability to perform physical uplink control channel (PUCCH) repetition. PUCCH repetition may include at least one repetition of PUCCH transmissions on public PUCCH resources (e.g., in contrast to dedicated or UE-specific PUCCH resources).

[0005] In some embodiments, public PUCCH resources may include at least one of the following: public PUCCH resources in an idle state (e.g., when the wireless communication device is in an idle state), public PUCCH resources in a connected state (e.g., when the wireless communication device is in a connected or RRC connected state), public PUCCH resources when no dedicated PUCCH resources are configured, public PUCCH resources after a successful completion of a contention-based random access procedure and before the configuration of dedicated PUCCH resources, or public PUCCH resources after a successful completion of a contention-free random access procedure and before the configuration of dedicated PUCCH resources. The wireless communication device may receive an indication of a repeating factor for PUCCH repeating from the wireless communication node. The wireless communication device may use this repeating factor to perform PUCCH repeating.

[0006] In some embodiments, the indication can be configured via / using higher-layer signaling. For a single repetition factor to be used on PUCCH repetition, the indication can be configured via first system information block (SIB) signaling. The indication can identify the repetition factor from multiple repetition factors configured via second SIB signaling. The indication can be configured via a field of downlink control information (DCI) signaling. The indication can be configured via at least one bit (e.g., two or more bits) of multiple cyclic redundancy check (CRC) bits used to scramble and schedule Msg4 physical downlink shared channel (PDSCH) transmissions. The indication can be configured via a field of DCI signaling used to schedule Msg3 physical uplink shared channel (PUSCH) transmissions. The indication can be determined based on the repetition factor for Msg3 transmissions.

[0007] In some implementations, the indication used to identify the repetition factor from a plurality of repetition factors configured via the second SIB signaling may include: one of four values ​​indicated in two bits of the two most significant bits (MSB), least significant bits (LSB), or other bits of the modulation and coding scheme (MCS) field of the DCI signaling. The indication may include: one of four values ​​indicated in two bits of the reserved field of the DCI signaling; one of four states indicated in the PUCCH resource indicator field of the DCI signaling; one of four states indicated in the Hybrid Automatic Request (HARQ) process number field of the DCI signaling. The indication may also include: one of four states indicated in the physical downlink shared channel (PDSCH) to HARQ feedback timing indicator field of the DCI signaling, wherein each value of the two bits can be mapped to a corresponding repetition factor, and wherein each of the four states can be mapped to a corresponding repetition factor.

[0008] In some implementations, the repetition factor can be determined based on at least one bit of a plurality of CRC bits. At least one bit of the plurality of CRC bits may include: two CRC bits other than the CRC bit scrambled by the cell radionetwork temporary identifier (C-RNTI) or a temporary C-RNTI; or the two most significant bits (MSBs) of a CRC bit scrambled with information corresponding to the repetition factor. The repetition factor can be determined based on the definition of the repetition factor for Msg3 transmission (configuration), determined as a defined fraction / multiple / function of the repetition factor for Msg3 transmission, or determined to be the same as the repetition factor for Msg3 transmission.

[0009] In some embodiments, DCI signaling may include: first DCI signaling, which may be scrambled by a Cell Radio Network Temporary Identifier (C-RNTI) after a successful completion of a random access procedure; DCI signaling that may be scrambled by a C-RNTI after a successful completion of a random access procedure, and which may be scrambled before the configuration of dedicated PUCCH resources; DCI signaling that may be scrambled by a C-RNTI, and which may be used by a wireless communication device to determine whether a random access procedure can be successfully completed when addressing PDCCH transmissions using a C-RNTI; or DCI signaling that may be scrambled by a random access (RA) RNTI, and which may be scrambled before the configuration of dedicated PUCCH resources.

[0010] In some embodiments, the repetition factor can be configured via DCI signaling or higher-layer signaling and can be valid before configuring dedicated PUCCH resources. In response to a condition being met, the wireless communication device can determine to send a message instructing the wireless communication device to perform PUCCH repetition using at least one public PUCCH resource. This condition may include at least one of the following: when the wireless communication device initiates an initial random access for contention-based or contention-free random access; when one or more repetition factors and a reference signal received power (RSRP) threshold are configured and an RSRP is measured to be lower than the configured RSRP threshold; when one or more repetition factors are configured and an RSRP threshold is not configured; when the wireless communication device initiates / performs a handover, wherein the handover includes at least a handover according to a contention-based random access procedure; or when the wireless communication device initiates / performs a handover, wherein the handover includes at least a handover according to a contention-free random access procedure.

[0011] In some embodiments, a wireless communication node may receive from a wireless communication device a message instructing the wireless communication device to perform Physical Uplink Control Channel (PUCCH) repetition. PUCCH repetition may include at least one repetition of PUCCH transmissions on public PUCCH resources.

[0012] In some embodiments, a non-transient computer-readable medium may store instructions that, when executed by at least one processor, cause the at least one processor to perform any one or more methods disclosed herein. An apparatus may include at least one processor configured to perform any one or more methods disclosed herein. Attached Figure Description

[0013] Various exemplary embodiments of this solution are described in detail below with reference to the figures or drawings. The drawings are for illustrative purposes only and depict only exemplary embodiments of the technical solution to facilitate the reader's understanding. Therefore, the drawings should not be considered as limitations on the breadth, scope, or applicability of this solution. It should be noted that these drawings are not necessarily drawn to scale for clarity and ease of explanation.

[0014] Figure 1 An example cellular communication network is shown, which can implement the techniques disclosed herein, according to embodiments of the present disclosure; Figure 2 Block diagrams of example base stations and user equipment according to some embodiments of the present disclosure are shown; Figure 3 Example implementations of non-terrestrial networks according to some embodiments of this disclosure are shown; Figure 4 An example process is shown for scrambling cyclic redundancy check bits with information about the number of repetitions of the physical uplink control channel, according to some embodiments of the present disclosure; Figure 5 A flowchart illustrating an example method for communication between a wireless communication device and a wireless communication node according to an embodiment of this disclosure is shown. Detailed Implementation

[0015] 1. Mobile communication technology and environment Figure 1 An example wireless communication network and / or system 100 according to an embodiment of the present disclosure is illustrated, in which the technologies disclosed herein can be implemented. In the following discussion, the wireless communication network 100 can be any wireless network, such as a cellular network or a narrowband Internet of Things (NB-IoT) network, and is referred to herein as "network 100". Such an example network 100 includes base stations 102 (hereinafter referred to as "BS 102", also called wireless communication nodes) and user equipment 104 (hereinafter referred to as "UE 104", also called wireless communication devices) that can communicate with each other via communication links 110 (e.g., wireless communication channels), and a cluster of cells 126, 130, 132, 134, 136, 138, and 140 covering a geographic area 101. Figure 1 In this context, BS 102 and UE 104 are contained within their respective geographical boundaries in cell 126. Each of the other cells 130, 132, 134, 136, 138, and 140 may include at least one base station operating on its allocated bandwidth to provide sufficient radio coverage to its intended users.

[0016] For example, BS 102 can operate on the allocated channel transmission bandwidth to provide sufficient coverage to UE 104. BS 102 and UE 104 can communicate via downlink (DL) radio frame 118 and uplink (UL) radio frame 124, respectively. Each radio frame 118 / 124 can also be divided into subframes 120 / 127, which may include data symbols 122 / 128. In this disclosure, BS 202 and UE 104 are generally described herein as non-limiting examples of "communication nodes" that can practice the methods disclosed herein. According to various embodiments of this scheme, such communication nodes are capable of wireless and / or wired communication.

[0017] Figure 2 A block diagram of an example wireless communication system 200 for transmitting and receiving wireless communication signals (e.g., OFDM (Orthogonal Frequency Division Multiplexing) / OFDMA (Orthogonal Frequency Division Multiple Access) signals) according to some embodiments of this solution is shown. System 200 may include components and elements configured to support known or conventional operating characteristics that do not require detailed description herein. In one illustrative embodiment, system 200 may be used in applications such as... Figure 1 The wireless communication environment 100 is a wireless communication environment in which communication (e.g., sending and receiving) data symbols are as described above.

[0018] System 200 typically includes a base station 202 (hereinafter referred to as "BS 202") and a user equipment 204 (hereinafter referred to as "UE 204"). BS 202 includes a BS (Base Station) transceiver module 210 (hereinafter also referred to as "BS transceiver 210"), a BS antenna 212 (hereinafter also referred to as "antenna 212"), a BS processor module 214 (hereinafter also referred to as "processor module 214"), a BS memory module 216 (hereinafter also referred to as "memory module 216"), and a network communication module 218, each module being coupled and interconnected with each other as needed via a data communication bus 220. UE 204 includes a UE (User Equipment) transceiver module 230 (hereinafter also referred to as "UE transceiver 230"), a UE antenna 232 (hereinafter also referred to as "antenna 232"), a UE memory module 234 (hereinafter also referred to as "memory module 234"), and a UE processor module 236, each module being coupled and interconnected with each other as needed via a data communication bus 240. BS 202 communicates with UE 204 via communication channel 250, which (hereinafter also referred to as: wireless transmission link 250, wireless data communication link 250) can be any wireless channel or other medium suitable for the data transmission described herein.

[0019] As those skilled in the art will understand, system 200 may also include, in addition to Figure 2 Any number of modules other than those shown. Those skilled in the art will understand that the various illustrative blocks, modules, circuits, and processing logic described in conjunction with the embodiments disclosed herein can be implemented in hardware, computer-readable software, firmware, or any practical combination thereof. To clearly illustrate this interchangeability and compatibility of hardware, firmware, and software, various illustrative components, blocks, modules, circuits, and steps are described in general terms of their functionality. Whether this functionality is implemented as hardware, firmware, or software may depend on the specific application and design constraints imposed on the system as a whole. Those skilled in the art described herein can implement this functionality appropriately for each specific application; however, such implementation decisions should not be construed as limiting the scope of this disclosure.

[0020] According to some embodiments, UE transceiver 230 may be referred to herein as an "uplink" transceiver 230 including a radio frequency (RF) transmitter and an RF receiver, each RF transmitter and RF receiver including circuitry coupled to antenna 232. A duplex switch (not shown) may alternately couple the uplink transmitter or receiver to the uplink antenna in a time-duplex manner. Similarly, according to some embodiments, BS transceiver 210 may be referred herein as a "downlink" transceiver 210 including an RF transmitter and an RF receiver, each RF transmitter and RF receiver including circuitry coupled to antenna 212. A downlink duplex switch may alternatively couple the downlink transmitter or receiver to the downlink antenna 212 in a time-division duplex manner. The operation of the two transceiver modules 210 and 230 may be time-coordinated such that the uplink receiver circuitry is coupled to the uplink antenna 232 so that transmissions are received over the wireless transmission link 250 while the downlink transmitter is coupled to the downlink antenna 212. Conversely, the operation of the two transceivers 210 and 230 can be time-coordinated so that the downlink receiver is coupled to the downlink antenna 212, so that transmissions can be received via the wireless transmission link 250 while the uplink transmitter is coupled to the uplink antenna 232. In some embodiments, there is tight time synchronization with a minimum guard time between changes in the duplex direction.

[0021] UE transceiver 230 and base transceiver 210 are configured to communicate via wireless data communication link 250 (hereinafter also referred to as: wireless transmission link 250, wireless data communication link 250) and cooperate with RF antenna arrangements 212 / 232 appropriately configured to support specific wireless communication protocols and modulation schemes. In some illustrative embodiments, UE transceiver 210 and base transceiver 210 are configured to support industry standards (such as Long Term Evolution (LTE) and emerging 5G standards). However, it should be understood that this disclosure is not necessarily limited to application to specific standards and related protocols. Rather, UE transceiver 230 and base transceiver 210 may be configured to support alternative or additional wireless data communication protocols (including future standards or variations thereof).

[0022] According to various embodiments, BS 202 may be, for example, an evolved Node B (eNB), a serving eNB, a target eNB, a femtocell, or a picocell. In some embodiments, UE 204 may be implemented in various types of user equipment, such as mobile phones, smartphones, personal digital assistants (PDAs), tablets, laptops, wearable computing devices, etc. Processor modules 214 and 236 may be implemented or realized using a general-purpose processor, content-addressable memory, digital signal processor, application-specific integrated circuit, field-programmable gate array, any suitable programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof, designed to perform the functions described herein. In this way, the processor may be implemented as a microprocessor, a controller, a microcontroller, a state machine, etc. The processor may also be implemented as a combination of computing devices, such as a digital signal processor and a microprocessor, multiple microprocessors, one or more microprocessors combined with a digital signal processor core, or any other combination of such configurations.

[0023] Furthermore, the steps of the methods or algorithms described in conjunction with the embodiments disclosed herein can be directly implemented in hardware, firmware, software modules executed by processor modules 214 and 236 respectively, or any practical combination thereof. Memory modules 216 and 234 can be implemented as RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, removable disk, CD-ROM, or any other form of storage medium known in the art. In this regard, memory modules 216 and 234 can be coupled to processor modules 210 and 230 respectively, such that processor modules 210 and 230 can read information from and write information to memory modules 216 and 234 respectively. Memory modules 216 and 234 can also be integrated into their respective processor modules 210 and 230. In some embodiments, memory modules 216 and 234 may each include cache memory for storing temporary variables or other intermediate information during the execution of instructions executed by processor modules 210 and 230 respectively. Memory modules 216 and 234 may each include non-volatile memory for storing instructions executed by processor modules 210 and 230, respectively.

[0024] Network communication module 218 typically represents the hardware, software, firmware, processing logic, and / or other components of base station 202 that enable bidirectional communication between base station transceiver 210 and other network components and communication nodes configured to communicate with base station 202. For example, network communication module 218 may be configured to support Internet or WiMAX services. In a typical deployment, but without limitation, network communication module 218 provides an 802.3 Ethernet interface, enabling base station transceiver 210 to communicate with conventional Ethernet-based computer networks. In this way, network communication module 218 may include a physical interface for connecting to a computer network (e.g., a Mobile Switching Center (MSC)). The terms “configured as,” “configured to,” and their variations, used herein with respect to a specified operation or function, refer to a device, component, circuit, structure, machine, signal, etc., which is physically constructed, programmed, formatted, and / or arranged to perform a specified operation or function.

[0025] The Open Systems Interconnection (OSI) model (referred to herein as the "OSI model") is a conceptual and logical layout that defines network communications used by systems (e.g., wireless communication devices, wireless communication nodes) for interconnecting and communicating with other systems. The model is divided into seven sub-components or layers, each representing a conceptual set of services provided to its upper and lower layers. The OSI model also defines logical networks and efficiently describes computer packet transmission using different layer protocols. The OSI model may also be referred to as the seven-layer OSI model or the seven-layer model. In some embodiments, the first layer may be the physical layer. In some embodiments, the second layer may be the Medium Access Control (MAC) layer. In some embodiments, the third layer may be the Radio Link Control (RLC) layer. In some embodiments, the fourth layer may be the Packet Data Convergence Protocol (PDCP) layer. In some embodiments, the fifth layer may be the Radio Resource Control (RRC) layer. In some embodiments, the sixth layer may be the Non-Access Stratum (NAS) layer or the Internet Protocol (IP) layer, and the seventh layer is other layers.

[0026] Various exemplary embodiments of this solution are described below with reference to the accompanying drawings to enable those skilled in the art to create and use this solution. As will be apparent to those skilled in the art, various changes or modifications can be made to the examples described herein without departing from the scope of this solution after reading this disclosure. Therefore, this solution is not limited to the exemplary embodiments and applications described and illustrated herein. Furthermore, the specific order or hierarchy of steps in the methods disclosed herein is merely exemplary. Based on design preferences, the specific order or hierarchy of steps in the disclosed methods or processes can be rearranged while remaining within the scope of this solution. Therefore, those skilled in the art will understand that the methods and techniques disclosed herein present various steps or actions in an exemplary order, and unless otherwise expressly stated, this solution is not limited to the specific order or hierarchy presented.

[0027] 2. Systems and methods for physical uplink control channel repetition indication The PUCCH (Physical Uplink Control Channel) can be used to carry uplink control information. This uplink control information may include HARQ (Hybrid Automatic Repeat reQuest) -ACK (ACKknowledgement) for downlink data reception. Msg4 HARQ-ACK can be the HARQ-ACK_feedback for the fourth message in the four-message / four-step handshake of the initial access procedure. Regarding PUCCH repetition for Msg4 HARQ-ACK, when the repetition count is configured by the System Information Block (SIB), a Reference Signal Received Power (RSRP) threshold can be configured via the SIB to determine whether a wireless communication device (e.g., a UE) has reported the ability to repetite PUCCH on one or more public PUCCH resources. When the RSRP threshold is configured, a UE capable of PUCCH repetition for Msg4 HARQ-ACK can report the ability to repetite PUCCH for Msg4 HARQ-ACK when the measured RSRP is below the configured RSRP threshold. If / if no RSRP threshold is configured, a UE capable of PUCCH repetition for Msg4 HARQ-ACK can / should report its ability to perform PUCCH repetition for Msg4 HARQ-ACK. When multiple repetition factors are configured / may exist / are available, the specific repetition factor to be used can be indicated by the Downlink Assignment Index (DAI) field in the Downlink Control Information (DCI) signaling. If only one repetition factor is configured / available, a UE capable of PUCCH repetition for Msg4 HARQ-ACK can report its ability to perform PUCCH repetition for Msg4 HARQ-ACK. The UE can perform PUCCH repetition with the repetition factor configured by the SIB.

[0028] The DAI field can be considered when a dynamic indication of the repetition factor is used / required. A temporary C-RNTI (Cell Radio Network Temporary Identifier) ​​can be used to scramble the DCI used to schedule the Msg4 Physical Downlink Shared Channel (PDSCH) during initial access, and the state of the DAI can be preserved. Connection modes may include random-access channel (RACH) procedures (e.g., handover based on a contention-based RACH). The UE can use the target cell's public PUCCH resources to provide feedback for HARQ-ACK before receiving the target cell's dedicated configuration. The UE can report the C-RNTI in Msg3 during handover. DCI scheduling of Msg4 and / or other data transmissions can be directly scrambled by the C-RNTI instead of the TC-RNTI.

[0029] Figure 3 An example procedure for a non-terrestrial network (NTN) is shown. The link between the UE and the satellite can be a serving link. The link between the base station (BS) and the satellite can be a feeder link.

[0030] Step 1: When the conditions for PRACH transmission are met, the UE can send a Physical Random Access Channel (PRACH) preamble with RA-RNTI (Random Access - Temporary Identifier for Radio Networks).

[0031] Step 2: The Next Generation Node B (gNB) can transmit a DCI scrambled with RA-RNTI. The UE can detect the PDCCH (DCI) with the corresponding RA-RNTI within the Msg2 or Random Access Response (RAR) window period. When the UE decodes the PDCCH, it can decode the PDSCH transmission carrying RAR data. After decoding the RAR, the UE can check whether the RAPID (Random Access Preamble Identifier) ​​in the RAR matches the RAPID assigned to the UE.

[0032] Step 3: The UE can transmit Msg3 (PUSCH transmission) on the same serving cell that sent the PRACH to it. If the UE has a unique identifier (e.g., C-RNTI), the C-RNTI can be carried in Msg3; otherwise, the core network identifier can be carried in Msg3.

[0033] Step 4: When Msg3 contains C-RNTI, the gNB can use C-RNTI to scramble the PDCCH transmission. If C-RNTI does not exist, the gNB can use TC-RNTI to scramble the PDCCH transmission.

[0034] Sub-step A: The UE, identified by a unique C-RNTI, can listen to decode the PDCCH scrambled with the C-RNTI. If the UE successfully decodes the PDCCH, it can confirm the successful completion of the random access procedure.

[0035] Sub-step B: One or more UEs without a unique C-RNTI can listen to decode PDCCH transmissions scrambled with TC-RNTI. If the UE successfully decodes the PDCCH transmission, it can decode the PDSCH transmission to retrieve the MAC (Medium Access Control) control element (CE), and when the core network identifier carried in Msg3 is equal to the identifier carried in Msg4, the UE can set the value of TC-RNTI to C-RNTI.

[0036] Step 5: When the UE successfully decodes Msg4 (the contention resolution message mentioned in step 4B), the UE may send a HARQ ACK in response to data (e.g., for a PDSCH transmission carrying Msg4).

[0037] Example Implementation 1: PUCCH duplication in public PUCCH resources in the CONNECTED state In connected states, a UE may have dedicated configurations (e.g., a unique identifier or identifier configured by the network (e.g., C-RNTI), or dedicated PUCCH resources, etc.). However, in some cases (e.g., according to connection-based RACH or connectionless RACH (e.g., handover according to connection-based RACH)), dedicated PUCCH resources may not be available or have not yet been configured. In some cases (e.g., during handovers relying on connection-based or connectionless RACH procedures), dedicated PUCCH resources may not yet be configured; therefore, it is worth considering how to define PUCCH duplication on / using public PUCCH resources before configuring dedicated PUCCH resources.

[0038] PUCCH duplication can refer to duplication (e.g., duplicate transmission) on or using public PUCCH resources (e.g., after a successful completion of a contention-based RACH (e.g., a CBRA in handover) process, before the configuration of a dedicated PUCCH resource, or after a successful completion of a contention-free RACH (e.g., a CFRA in handover) process, and / or before the configuration of a dedicated PDCCH resource).

[0039] If PUCCH repetition for PUCCH transmission is supported without providing dedicated PUCCH resource configuration, the following method for PUCCH repetition on public PUCCH resources in the connected state can be considered before configuring dedicated PUCCH resources.

[0040] The ability to retransmit PUCCH can reuse the ability to retransmit previously reported PUCCH (e.g., the ability to retransmit PUCCH can be determined to be the same as the ability to retransmit previously reported PUCCH (e.g., reported in the initial random access, reported in Msg3 during contention-based random access control (RACH) handover, etc.).

[0041] Step 1: When a UE capable of PUCCH repetition does not have the ability to report PUCCH repetition, PUCCH repetition on public PUCCH resources may not be allowed.

[0042] Step 2: When a UE capable of PUCCH repetition has reported its PUCCH repetition capability, in some cases, a repetition factor can be configured by higher-layer signaling from the network / base station (e.g., SIB, RRC, MAC CE, etc.) (e.g., by handover commands, RRC reconfiguration, reconfiguration with synchronization, or other signaling). In some cases, if only one repetition factor is configured in the SIB signaling (e.g., SIB signaling for the target cell, SIB signaling for initial access, SIB signaling for the target cell when the UE is in a connected state, SIB signaling for the UE in a connected state, etc.), then the same repetition factor can be applied to PUCCH repetition on public PUCCH resources for UEs in a connected state.

[0043] In some cases, if multiple repetition factors are configured in the SIB signaling (e.g., SIB signaling for the target cell, SIB signaling for initial access, SIB signaling for the target cell when the UE is in a connected state, SIB signaling for the UE in a connected state, etc.), then for a UE in a connected state, the repetition factor can be defined / indicated / specified by one or more of the following A to E: A. Reuse existing bit fields in a DCI (e.g., that can be scrambled by C-RNTI / TC-RNTI, etc.) or other DCIs used for scheduling UL / DL transmissions (e.g., by a value indicated by 2 bits in the MCS field (the 2 bits in the MCS field can be the highest 2 bits or the lowest 2 bits)) to indicate the repetition factor for PUCCH repetition on public PUCCH resources, wherein, when higher-layer parameters (e.g., SIB signaling) are configured with at least two values ​​and the UE has indicated the capability for PUCCH repetition on public PUCCH resources, these 2 bits in the MCS field indicate the number of repetitions for the PUCCH according to Table 1; in ( For example, one of the four states indicated in the PUCCH resource indicator field (configured by the repetition factor per PUCCH resource), one of the four states indicated in the HARQ process number field, one of the four states indicated in the PDSCH-to-HARQ_feedback timing indicator field, wherein these four states indicate the number of repetitions for the PUCCH according to Table 2 when the higher-layer parameters (e.g., SIB signaling) are configured with at least two values ​​and the UE has indicated the ability to repeat PUCCH on public PUCCH resources; and / or the value indicated by the 2 bits in the reserved field.

[0044] A new 2-bit field in B.DCI indicates the repetition factor for PUCCH repetitions on one or more public PUCCH resources.

[0045] C. CRC bits used for scrambling the DCI of the scheduled Msg4 PDSCH. Two CRC bits (e.g., bits other than those scrambled by TC-RNTI / C-RNTI) can be used as a dynamic indicator to indicate the repetition factor of PUCCH repetitions on public PUCCH resources. The first two MSB bits of the CRC can be scrambled with information about the number of PUCCH repetitions (or the repetition factor), and the UE can retrieve this information by descrambling in the same manner as with TC-RNTI.

[0046] D. Fields in the DCI for scheduling Msg3 (PUSCH transmissions). The PUCCH repeat factor and Msg3 repeat factor can be jointly indicated using a predefined / configured relationship between the PUCCH repeat factor and the Msg3 repeat factor. If the Msg3 repeat factor is configured, the repeat factor for PUCCH repetition on public PUCCH resources can be a specific fraction (or multiple or function) of the Msg3 repeat factor; otherwise, PUCCH transmissions on public PUCCH resources cannot support repetition.

[0047] E. An implicit mapping between the repeat factor of PUCCH repeats on public PUCCH resources and the indication of Msg3 PUSCH repeats without reinterpreting fields / new fields (i.e., without changing the existing DCI format / design). If the Msg3 repeat factor is configured, the repeat factor of PUCCH repeats on public PUCCH resources can be the same as the Msg3 repeat factor; otherwise, PUCCH transmissions on public PUCCH resources cannot support repeats.

[0048] Table 1: 2-bit MCS field / Reserved bit field / New field / 2 CRCs

[0049] Table 2: Four possible states that can be indicated in the PUCCH resource indicator field / HARQ process number field / PDSCH-to-HARQ_feedback timer indicator field

[0050] According to Section 2 (A or B), the mapping rule for the 2-bit dynamic indication can be defined / configured as follows: the configured first / second / third / fourth repetition factor can be mapped to the "00", "01", "10", and "11" values / code points of the 2-bit field, respectively. When the third and / or fourth repetition factor is not configured, the corresponding code points (i.e., "10" and / or "11") can be omitted, as shown in Table 1. The mapping rule for the four states of the dynamic indication can be defined / configured as follows: the configured first / second / third / fourth repetition factor can be mapped to the "State 1", "State 2", "State 3", and "State 4" of the four possible / available states indicated in the PUCCH resource indicator field, HARQ process number field, and PDSCH-to-HARQ_feedback timing indicator field, respectively. When the third and / or fourth repetition factor is not configured, the corresponding state / code points (e.g., "10" and / or "11") can be omitted, as shown in Table 2.

[0051] Figure 4 An example procedure for scrambling Cyclic Redundancy Check (CRC) with information about the number of repetitions of the Physical Uplink Control Channel, according to Section 2(C), is shown. Figure 4 In this context, the mapping rules for 2 bits can be defined / configured as follows: the configured first / second / third / fourth repetition factors can respectively use the 2-bit CRC scrambling values / code points "00", "01", "10", and "11". When the third and / or fourth repetition factors are not configured, the corresponding code points (i.e., "10" and / or "11") can be omitted, as shown in Table 1.

[0052] If the capability for PUCCH repetition has been previously reported (e.g., reported in initial random access, reported in Msg3 during handover based on a contention-based RACH, and / or reported in Msg3 during handover based on a contention-free RACH, etc.), the capability for PUCCH repetition can reuse the previously reported capability for PUCCH repetition (e.g., the capability for PUCCH repetition can be determined by using the previously reported capability for PUCCH repetition / the capability for PUCCH repetition is determined by the previously reported capability for PUCCH repetition); otherwise, the capability for PUCCH repetition can be reported by higher-layer signaling using Msg3 in a new RACH (e.g., a contention-based RACH during handover, a contention-free RACH during handover, or another initial random access). The higher-layer signaling can be at least one of the following: logical channel identifier (LCID) code point, R bits in the MAC sub-header, or other fields.

[0053] If a UE capable of PUCCH repetition has previously reported its PUCCH repetition capability, then PUCCH repetition on public PUCCH resources (e.g., public resources in the target cell where the UE is connected, or public resources where the UE is connected) can support PUCCH repetition. The repetition factor for connected UEs can be configured in the same manner as in step 2.

[0054] If this capability has not been reported previously (e.g., the UE has not communicated its PUCCH repeat capability), the capability to repeat PUCCH on public PUCCH resources can be reported using higher-layer signaling such as Msg3 (e.g., Msg3 in the target cell when the UE is in connected state, or Msg3 sent by the UE in connected state). For a connected UE, the repeat factor for PUCCH repeats can be defined / indicated / determined as follows: A. UEs capable of PUCCH repetition can report their PUCCH repetition capability in the Msg3 signaling. The repetition factor can be configured in the same way as in step 2 (e.g., for a target cell where the UE is in a connected state, or for the UE in a connected state).

[0055] B. UEs capable of PUCCH repetition may not report their PUCCH repetition capability in the Msg3 signaling. In this case, PUCCH repetition on public PUCCH resources may not be permitted.

[0056] The ability to repeat a PUCCH can be reported using higher-layer signaling in Msg3 with a new RACH (e.g., a contention-based RACH during handover, a contention-free RACH during handover, another initial random access, etc.). This process can be similar to the process described in any one or more of the first three paragraphs.

[0057] The conditions for determining whether the PUCCH repeat capability on public PUCCH resources can be reported via higher-layer signaling can be based on at least one of the following (e.g., the capability is reported if / when any of the following conditions are met): (1) when the UE initiates initial random access, the initial random access can be a contention-based CBRA or CFRA; (2) when a repeat factor and RSRP threshold are configured, and the measured RSRP is lower than the configured RSRP threshold; (3) when a repeat factor is configured, but an RSRP threshold is not configured; (4) when the UE initiates a handover that includes at least a contention-based RACH procedure; and / or (5) when the UE initiates a handover that includes at least a contention-free RACH procedure.

[0058] A DCI can indicate / include an indicator of the repetition factor. Such a DCI can be a first DCI scrambled by C-RNTI after successful random access, and the repetition factor(s) can be valid before dedicated PUCCH resource configuration is provided. The first DCI (e.g., format 0_0 / 1 / 2, format 1_0 / 1 / 2, etc.) can be a DCI used to schedule DL transmissions or a DCI used to schedule UL transmissions. A DCI can be a DCI encrypted by C-RNTI after a successful random access procedure and before configuring one / any dedicated PUCCH resource. A DCI (e.g., format 0_0 / 1 / 2, format 1_0 / 1 / 2) can be a DCI used for DL ​​transmission scheduling. The UE can use a C-RNTI-scrambled DCI to determine if the random access procedure was successful, while using C-RNTI to address PDCCH transmissions, and the repetition factor can be valid before dedicated PUCCH resource configuration is provided / executed / completed. A DCI scrambled by RA-RNTI can be used as an indicator of the repetition factor, and the repetition factor can be valid before dedicated PUCCH resource configuration is provided.

[0059] The following are example scenarios illustrating the features disclosed in this disclosure.

[0060] When a UE has reported its PUCCH repetition capability (e.g., during initial random access, during Msg3 in a handover based on contention-based RACH, etc.), the gNB or base station (e.g., a wireless communication node) can configure a repetition factor for PUCCH repetition on public PUCCH resources for a connected UE via higher-layer signaling (e.g., SIB, RRC, MAC CE, etc.) (e.g., via handover command, RRC reconfiguration, reconfiguration with synchronization, or other signaling). Immediately after the successful completion of the RACH procedure (e.g., during CFRA or CBRA handover) and before configuring dedicated PUCCH resources, PUCCH transmissions can support repetition on public PUCCH resources, and / or the UE can perform PUCCH repetition on public PUCCH resources based on the repetition factor configured by higher-layer signaling. If the UE has not previously reported its PUCCH repetition capability, the UE cannot support PUCCH repetition on public PUCCH resources.

[0061] When a UE has previously reported its PUCCH repetition capability (e.g., during initial random access or in Msg3 during a handover based on contention-based RACH), if only one repetition factor is configured in the SIB signaling (e.g., SIB signaling for the target cell, SIB signaling for initial access, SIB signaling for the target cell, SIB signaling for initial access, SIB signaling for the target cell when the UE is connected, SIB signaling for the UE when the UE is connected), then for a UE in the connected state, the same repetition factor can be applied to PUCCH repetition on the public PUCCH resource. Immediately after the successful completion of the RACH procedure (e.g., during CFRA or CBRA handover) and before configuring dedicated PUCCH resources, PUCCH repetition on the public PUCCH resource can be supported. The UE can perform PUCCH repetition on public PUCCH resources based on a repetition factor configured by SIB signaling (e.g., SIB signaling for the target cell, SIB signaling for initial access, SIB signaling for the target cell when the UE is in a connected state, and SIB signaling for the UE when the UE is in a connected state). If the UE does not previously have the ability to report PUCCH repetition, the UE cannot support PUCCH repetition on public PUCCH resources.

[0062] When a UE has previously reported its ability to repeat PUCCH (e.g., during initial random access, or as reported in Msg3 during a handover based on contention-based RACH), if multiple repetition factors are configured in the SIB signaling (e.g., SIB signaling for the target cell, SIB signaling for initial access, SIB signaling for the target cell when the UE is in a connected state, SIB signaling for the UE in a connected state), the gNB / BS can configure a specific / precise repetition factor for PUCCH repetition on public PUCCH resources for a connected UE by a specific 2-bit value / state or one of four states indicated in the DCI (which can be any DCI). Following the successful completion of the RACH procedure (e.g., during CFRA or CBRA handover) and before configuring dedicated PUCCH resources, the PUCCH can support repetition on public PUCCH resources, and the UE can perform PUCCH repetition on PUCCH resources based on a repetition factor configured by dynamic indications (e.g., repetition indications for connected UEs in the target cell (e.g., repetition indications for connected UEs in the target cell (e.g., MCS indicator as a dynamic indication), repetition indications for connected UEs)). If the UE does not previously have the ability to report its PUCCH repetitions, the UE cannot support PUCCH repetition on public PUCCH resources.

[0063] When a UE has previously reported its ability to repeat PUCCH (e.g., during initial random access, or as reported in Msg3 during a handover based on contention-based RACH), the following can be applied: the gNB / BS can configure a repeat factor for PUCCH repeats on public PUCCH resources for a connected UE via higher-layer signaling (e.g., SIB, RRC, MAC CE, etc.) (e.g., via handover command, RRC reconfiguration, reconfiguration with synchronization, or other signaling). Following the successful completion of the RACH procedure (e.g., during CFRA or CBRA handover) and before configuring dedicated PUCCH resources, the UE's PUCCH transmissions can support repetition on public PUCCH resources, and / or the UE can perform PUCCH repetition on public PUCCH resources based on a repetition factor configured by higher-layer signaling. Alternatively, if only one repetition factor is configured in the SIB signaling (e.g., SIB signaling for the target cell, SIB signaling for initial access, SIB signaling for the target cell when the UE is in a connected state, SIB signaling for the UE in a connected state), the same repetition factor can be applied to PUCCH repetition on public PUCCH resources for the UE in a connected state. Following the successful completion of the RACH procedure (e.g., during CFRA or CBRA handover) and before configuring dedicated PUCCH resources, PUCCH can support repetition on public PUCCH resources, and / or the UE can perform PUCCH repetition on public PUCCH resources based on a repetition factor configured by SIB signaling (e.g., SIB signaling for the target cell, SIB signaling for initial access, SIB signaling in the target cell where the UE is connected, SIB signaling for the UE in connected state, etc.). Alternatively, if multiple repetition factors are configured in the SIB signaling (e.g., SIB signaling for the target cell, SIB signaling for initial access, SIB signaling in the target cell where the UE is connected, SIB signaling for the UE in connected state, etc.), the gNB can configure / specify / indicate a specific / precise repetition factor for use / application for PUCCH repetition on public PUCCH resources by using a 2-bit value / state or a specific state from four states indicated in the DCI (which can be any DCI). Following the successful completion of the RACH procedure (e.g., during CFRA or CBRA handover) and before configuring dedicated PUCCH resources, PUCCH can support repetition on public PUCCH resources, and the UE can perform PUCCH repetition on PUCCH resources based on dynamic indications (e.g., repetition indication for UEs in connected state in the target cell (e.g., repetition indication for UEs in connected state in the target cell (e.g., MCS indicator as dynamic indication), repetition indication for UEs in connected state)).Otherwise, the following applies: If the UE initiates a handover that includes either a contention-based RACH or a contention-free RACH, or if the UE-initiated handover (which may be based on a contention-based RACH or a contention-free RACH) is accompanied by a configured repetition factor and an RSRP threshold, and / or if the measured RSRP is below this threshold, or if the UE initiates a handover (which may be based on a contention-based RACH or a contention-free RACH) and has configured a repetition factor but not an RSRP threshold, then a UE capable of PUCCH repetition can report its PUCCH repetition capability in higher-layer signaling of Msg3. Afterward, the following applies: the gNB / BS can configure a repetition factor for PUCCH repetition on public PUCCH resources via higher-layer signaling (e.g., SIB, RRC, MAC CE, etc.) (e.g., via handover command, RRC reconfiguration, reconfiguration with synchronization, or other signaling, etc.). Following the successful completion of the RACH procedure (e.g., during CFRA or CBRA handover) and before configuring dedicated PUCCH resources, the UE's PUCCH transmissions can support repetition on public PUCCH resources, and / or the UE can perform PUCCH repetition on public PUCCH resources based on a repetition factor configured by higher-layer signaling. Alternatively, if only one repetition factor is configured in the SIB signaling (e.g., SIB signaling for the target cell, SIB signaling for initial access, SIB signaling for the target cell when the UE is in a connected state, SIB signaling for the UE in a connected state), the same repetition factor can be applied to PUCCH repetition on public PUCCH resources. Following the successful completion of the RACH procedure (e.g., during CFRA or CBRA handover) and before configuring dedicated PUCCH resources, PUCCH can support repetition on public PUCCH resources, and / or the UE can perform PUCCH repetition on public PUCCH resources based on a repetition factor configured by SIB signaling (e.g., SIB signaling for the target cell, SIB signaling for initial access, SIB signaling in the target cell where the UE is connected, SIB signaling for the UE in connected state). Alternatively, if multiple repetition factors are configured in the SIB signaling (e.g., SIB signaling for the target cell, SIB signaling for initial access, SIB signaling in the target cell where the UE is connected, SIB signaling for the UE in connected state), the gNB can configure / specify / indicate a specific / precise repetition factor for use / application for PUCCH repetition on public PUCCH resources by using a 2-bit value / state or a specific state from four states indicated in the DCI (which can be any DCI).Following the successful completion of the RACH procedure (e.g., during CFRA or CBRA handover) and before configuring dedicated PUCCH (or UE-specific) resources, PUCCH transmissions may support repetition on public PUCCH resources, and the UE may perform PUCCH repetition on PUCCH resources based on a repetition factor configured by dynamic indications (e.g., repetition indications for connected UEs in the target cell (e.g., repetition indications for connected UEs in the target cell (such as MCS indicators as dynamic indications), repetition indications for connected UEs)). Otherwise, the UE does not support PUCCH repetition on public PUCCH resources.

[0064] When a UE initiates a handover that includes either a contention-based RACH or a contention-free RACH, or when a UE-initiated handover (which may be based on a contention-based RACH or a contention-free RACH) is accompanied by a configured repetition factor and an RSRP threshold, and / or if the measured RSRP is observed to be below this threshold, or when a UE-initiated handover (which may be based on a contention-based RACH or a contention-free RACH) has a configured repetition factor but no configured RSRP threshold, a UE capable of PUCCH repetition can report its PUCCH repetition capability in higher-layer signaling of Msg3. Afterwards, the gNB / BS can configure a repetition factor for PUCCH repetition on public PUCCH resources via higher-layer signaling (e.g., SIB, RRC, MAC CE, etc.) (e.g., via handover command, RRC reconfiguration, reconfiguration with synchronization, or other signaling, etc.). Following the successful completion of the RACH procedure (e.g., during CFRA or CBRA handover) and before configuring dedicated PUCCH resources, the UE's PUCCH transmissions can support repetition on public PUCCH resources, and / or the UE can perform PUCCH repetition on public PUCCH resources based on a repetition factor configured by higher-layer signaling. Alternatively, if only one repetition factor is configured in the SIB signaling (e.g., SIB signaling for the target cell, SIB signaling for initial access, SIB signaling for the target cell when the UE is connected, SIB signaling for the UE when the UE is connected), the same repetition factor can be applied to PUCCH repetition on public PUCCH resources. Following the successful completion of the RACH procedure (e.g., during CFRA or CBRA handover) and before configuring dedicated PUCCH resources, PUCCH can support repetition on public PUCCH resources, and / or the UE can perform PUCCH repetition on public PUCCH resources based on a repetition factor configured by SIB signaling (e.g., SIB signaling for the target cell, SIB signaling for initial access, or SIB signaling for the target cell where the UE is connected, or SIB signaling for the UE in a connected state). Alternatively, if multiple repetition factors are configured in the SIB signaling (e.g., SIB signaling for the target cell, SIB signaling for initial access, SIB signaling in the target cell where the UE is connected, or SIB signaling for the UE in a connected state), the gNB can configure / specify / indicate a specific / precise repetition factor for use / application for PUCCH repetition on public PUCCH resources by the value / state of a 2-bit field indicated in the DCI (which can be any DCI) or a specific state among four states.Following the successful completion of the RACH procedure (e.g., during CFRA or CBRA handover) and before configuring dedicated PUCCH (or UE-specific) resources, PUCCH transmissions may support repetition on public PUCCH resources, and the UE may perform PUCCH repetition on PUCCH resources based on a repetition factor configured by dynamic indications (e.g., repetition indications for connected UEs in the target cell (e.g., repetition indications for connected UEs in the target cell (e.g., MCS indicator as a dynamic indication), repetition indications for connected UEs)). Otherwise, the UE does not support PUCCH repetition on public PUCCH resources.

[0065] When a UE has previously reported its PUCCH repetition capability (e.g., during initial random access, or as reported in Msg3 during a handover based on contention-based RACH), the following can be applied: the gNB / BS can configure a repetition factor for PUCCH repetition on public PUCCH resources via higher-layer signaling (e.g., SIB, RRC, MAC CE, etc.) (e.g., via handover command, RRC reconfiguration, reconfiguration with synchronization, or other signaling). Immediately after the successful completion of the RACH procedure (e.g., during CFRA or CBRA handover) and before configuring dedicated PUCCH resources, the UE's PUCCH transmissions can support repetition on public PUCCH resources, and / or the UE can perform PUCCH repetition on public PUCCH resources based on the repetition factor configured by higher-layer signaling. Alternatively, if only one repetition factor is configured in the SIB signaling (e.g., SIB signaling for the target cell, SIB signaling for initial access, SIB signaling for the target cell when the UE is in a connected state, SIB signaling for the UE in a connected state), the same repetition factor can be applied to PUCCH repetition on public PUCCH resources. Following the successful completion of the RACH procedure (e.g., during CFRA or CBRA handover) and before configuring dedicated PUCCH resources, PUCCH can support repetition on public PUCCH resources, and / or the UE can perform PUCCH repetition on public PUCCH resources based on a repetition factor configured by SIB signaling (e.g., SIB signaling for the target cell, SIB signaling for initial access, SIB signaling in the target cell where the UE is connected, SIB signaling for the UE in connected state). Alternatively, if multiple repetition factors are configured in the SIB signaling (e.g., SIB signaling for the target cell, SIB signaling for initial access, SIB signaling in the target cell where the UE is connected, SIB signaling for the UE in connected state), the gNB can configure / specify / indicate a specific / precise repetition factor for use / application for PUCCH repetition on public PUCCH resources by using a 2-bit value / state or a specific state from four states indicated in the DCI (which can be any DCI). Following the successful completion of the RACH procedure (e.g., during CFRA or CBRA handover) and before configuring dedicated PUCCH (or UE-specific) resources, PUCCH transmissions can support repetition on public PUCCH resources, and the UE can perform PUCCH repetition on PUCCH resources based on a repetition factor configured by dynamic indications (e.g., repetition indications for connected UEs in the target cell (e.g., repetition indications for connected UEs in the target cell (e.g., MCS indicator as a dynamic indication), repetition indications for connected UEs)).If the UE does not previously have the ability to report its PUCCH duplication, the UE cannot support PUCCH duplication on public PUCCH resources.

[0066] If a UE initiates a handover that includes either a contention-based RACH or a contention-free RACH, or if the handover initiated by the UE (which may be based on a contention-based RACH or a contention-free RACH) is accompanied by a configured repetition factor and RSRP threshold, and / or if the measured RSRP is observed to be below this threshold, a UE capable of PUCCH repetition may report its PUCCH repetition capability in the higher-layer signaling of Msg3. Alternatively, if a UE initiates a handover (which may be based on a contention-based RACH or a contention-free RACH) and neither the repetition factor nor the RSRP threshold is configured, a UE capable of PUCCH repetition may report its PUCCH repetition capability in the higher-layer signaling of Msg3.

[0067] It should be understood that one or more features from the above / below examples of implementations are not specific to these specific examples of implementations, but can be combined in any way (e.g., with any priority and / or order, concurrently or otherwise).

[0068] Figure 5 A flowchart of a method 500 for communication between a wireless communication device and a wireless communication node is shown. Method 500 may use any one or more components and devices described in detail herein, in conjunction with the appendix. Figures 1 to 4 Implementation is carried out. Generally, in some embodiments, method 500 may be performed by a wireless communication device (e.g., UE) and / or a wireless communication node (e.g., BS, gNB). According to embodiments, additional, fewer, or different operations may be performed in method 500. At least one aspect of these operations relates to a system, method, apparatus, or computer-readable medium.

[0069] A wireless communication device (e.g., a user equipment (UE)) may send a message (505) to a wireless communication node (e.g., a base station (BS)) instructing the wireless communication device to perform PUCCH repetition. The wireless communication node may receive a message (510) instructing the wireless communication device to perform PUCCH repetition. The wireless communication node may also receive a message from the wireless communication device instructing the wireless communication device to perform Physical Uplink Control Channel (PUCCH) repetition.

[0070] In some embodiments, public PUCCH resources may include at least one of the following: public PUCCH resources in an idle state (e.g., when the wireless communication device is in an idle state), public PUCCH resources in a connected state (e.g., when the wireless communication device is in a connected or RRC connected state), public PUCCH resources when no dedicated PUCCH resources are configured, public PUCCH resources after a successful completion of a contention-based random access procedure and before the configuration of dedicated PUCCH resources, or public PUCCH resources after a successful completion of a contention-free random access procedure and before the configuration of dedicated PUCCH resources.

[0071] A wireless communication device can receive an indication of the repetition factor for PUCCH repetition from a wireless communication node. The wireless communication device can use this repetition factor to perform PUCCH repetition. This indication can be configured via / using higher-layer signaling sent by the wireless communication node. For a single repetition factor to be used in PUCCH repetition, the indication can be configured via a first System Information Block (SIB) signaling. The indication can be identified from multiple repetition factors configured via a second SIB signaling. The indication can be configured via a field of Downlink Control Information (DCI) signaling. The indication can be configured via at least one bit (e.g., two or more bits) of multiple Cyclic Redundancy Check (CRC) bits used for scrambling and scheduling Msg4 Physical Downlink Shared Channel (PDSCH) transmissions. The indication can be configured via a field of DCI signaling used for scheduling Msg3 Physical Uplink Shared Channel (PUSCH) transmissions. The indication can be determined based on the repetition factor for Msg3 transmissions.

[0072] In some implementations, the indication used to identify the repetition factor from a plurality of repetition factors configured via the second SIB signaling may include: one of four values ​​indicated in two bits of the two most significant bits (MSB), least significant bits (LSB), or other bits of the modulation and coding scheme (MCS) field of the DCI signaling. The indication may include: one of four values ​​indicated in two bits of the reserved field of the DCI signaling; one of four states indicated in the PUCCH resource indicator field of the DCI signaling; one of four states indicated in the Hybrid Automatic Request (HARQ) process number field of the DCI signaling. The indication may include one of four states indicated in the Physical Downlink Shared Channel (PDSCH) to HARQ Feedback Timing Indicator field of the DCI signaling. Each value of these two bits can be mapped to a corresponding repetition factor. Each of the four states can be mapped to a corresponding repetition factor. The wireless communication device can receive the DCI signaling from the wireless communication node.

[0073] In some implementations, the wireless communication device can determine the repetition factor based on at least one of a plurality of CRC bits. At least one of the plurality of CRC bits may include: two CRC bits other than the CRC bit scrambled by the Cell Radio Network Temporary Identifier (C-RNTI) or a temporary C-RNTI; or the two most significant bits (MSBs) of the CRC bit scrambled with information corresponding to the repetition factor. The wireless communication device can determine the repetition factor based on a defined relationship of the repetition factor for the Msg3 transmission (configuration), for example, a defined fraction / multiple / function of the repetition factor determined for the Msg3 transmission, or the same as the repetition factor for the Msg3 transmission.

[0074] In some embodiments, the DCI signaling discussed above may include: a first DCI signaling, which may be scrambled by a Cell Radio Network Temporary Identifier (C-RNTI) after the successful completion of the random access procedure; a DCI signaling that may be scrambled by a C-RNTI after the successful completion of the random access procedure, and which may be scrambled before the configuration of dedicated PUCCH resources; a DCI signaling that may be scrambled by a C-RNTI, and which may be used by the wireless communication device to determine whether the random access procedure can be successfully completed when addressing PDCCH transmission using a C-RNTI; or a DCI signaling that may be scrambled by a random access (RA) RNTI, and which may be scrambled before the configuration of dedicated PUCCH resources.

[0075] In some embodiments, the repetition factor can be configured via DCI signaling or higher-layer signaling and can be valid before configuring dedicated PUCCH resources. In response to the fulfillment of certain conditions(or the occurrence of certain scenarios), the wireless communication device can determine to send a message instructing the wireless communication device to perform PUCCH repetition using at least one public PUCCH resource. The conditions / scenarios may include at least one of the following: when the wireless communication device initiates an initial random access for contention-based or contention-free random access; when one or more repetition factors and a reference signal received power (RSRP) threshold are configured and an RSRP is measured to be lower than the configured RSRP threshold; when one or more repetition factors are configured and an RSRP threshold is not configured; when the wireless communication device initiates / performs a handover, wherein the handover includes at least a handover according to a contention-based random access procedure; or when the wireless communication device initiates / performs a handover, wherein the handover includes at least a handover according to a contention-free random access procedure.

[0076] While various embodiments of the present solution have been described above, it should be understood that these embodiments are presented by way of example only and not as limitations. Similarly, various diagrams may depict exemplary architectures or configurations provided to enable those skilled in the art to understand exemplary features and functionality of the present solution. However, those skilled in the art will understand that the solution is not limited to the illustrated exemplary architectures or configurations but can be implemented using various alternative architectures and configurations. Furthermore, as those skilled in the art will understand, one or more features of one embodiment may be combined with one or more features of another embodiment described herein. Therefore, the breadth and scope of this disclosure should not be limited to any of the illustrative embodiments described above.

[0077] It should also be understood that any reference to elements using names such as "first," "second," etc., in this document generally does not restrict the number or order of these elements. Rather, these names may be used herein as a convenient means of distinguishing between two or more elements or instances of elements. Therefore, references to the first and second elements do not imply that only two elements can be used or that the first element must precede the second element in some way.

[0078] Furthermore, those skilled in the art will understand that information and signals can be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, and symbols referenced in the above description can be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or light particles, or any combination thereof.

[0079] Those skilled in the art will further understand that any of the various illustrative logic blocks, modules, processors, means, circuits, methods, and functions described in connection with the aspects disclosed herein can be implemented by electronic hardware (e.g., digital implementation, analog implementation, or a combination of both), firmware, various forms of program or design code in conjunction with instructions (which may be referred to herein as "software" or "software module"), or any combination of these technologies. To clearly illustrate this interchangeability of hardware, firmware, and software, various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware, firmware, or software, or a combination of these technologies, depends on the specific application and the design constraints imposed on the system as a whole. Those skilled in the art can implement the described functionality in various ways for each specific application, but such implementation will not depart from the scope of this disclosure.

[0080] Furthermore, those skilled in the art will understand that the various illustrative logic blocks, modules, devices, components, and circuits described herein can be implemented within or executed by an integrated circuit (IC), which may include a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, or any combination thereof. Logic blocks, modules, and circuits may also include antennas and / or transceivers for communicating with various components within a network or device. A general-purpose processor may be a microprocessor, but alternatively, the processor may be any conventional processor, controller, or state machine. The processor may also be implemented as a combination of computing devices, such as a DSP and a microprocessor, multiple microprocessors, one or more microprocessors combined with a DSP core, or any other suitable configuration that performs the functions described herein.

[0081] If implemented as software, these functionalities can be stored as one or more instructions or code on a computer-readable medium. Therefore, the steps of the methods or algorithms disclosed herein can be implemented as software stored on a computer-readable medium. Computer-readable media include computer storage media and communication media, with communication media including any medium that enables the transfer of computer programs or code from one location to another. Storage media can be any available medium that is accessible to a computer. By way of example and not limitation, such computer-readable media can include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to store the required program code in the form of instructions or data structures and that is accessible to a computer.

[0082] In this document, the term "module" as used herein refers to software, firmware, hardware, and any combination of such elements for performing the associated functions described herein. Furthermore, for purposes of discussion, various modules are described as separate modules; however, as will be apparent to those skilled in the art, two or more modules may be combined to form a single module that performs the associated functions according to embodiments of this solution.

[0083] Furthermore, memory or other storage devices and communication components may be used in embodiments of this solution. It should be understood that, for clarity, the above description refers to embodiments of this solution with reference to different functional units and processors. However, it will be apparent that any suitable distribution of functionality among different functional units, processing logic elements, or domains can be used without diminishing the effectiveness of this solution. For example, functions shown to be performed by a separate processing logic element or controller may be performed by the same processing logic element or controller. Therefore, references to specific functional units are merely references to suitable means for providing the described functionality and do not indicate a strict logical or physical structure or organization.

[0084] Various modifications to the embodiments described in this disclosure will be apparent to those skilled in the art, and the general principles defined herein can be applied to other embodiments without departing from the scope of this disclosure. Therefore, this disclosure is not intended to be limited to the embodiments shown herein, but is given the broadest scope consistent with the novel features and principles disclosed herein as set forth in the following claims.

Claims

1. A method comprising: A message is sent from a wireless communication device to a wireless communication node instructing the wireless communication device to perform the Physical Uplink Control Channel (PUCCH) repetition. The PUCCH repetition includes at least one repetition of PUCCH transmission on public PUCCH resources.

2. The method according to claim 1, wherein, The public PUCCH resources include at least one of the following: Public PUCCH resources that are currently idle. Public PUCCH resources that are in a connected state Public PUCCH when no dedicated PUCCH resource is configured After a successful contention-based random access procedure and before configuring dedicated PUCCH resources, or The public PUCCH resource after a successful completion of the contention-free random access procedure and before the configuration of the dedicated PUCCH resource.

3. The method according to claim 1, comprising: The wireless communication device receives an indication of the repetition factor of the PUCCH repetition from the wireless communication node, and The PUCCH repetition is performed by the wireless communication device using the repetition factor.

4. The method according to claim 3, wherein, At least one of the following situations exists: The instruction is configured via higher-level signaling. The indication for a single repetition factor to be used on PUCCH repetition is configured via the first System Information Block (SIB) signaling. The indication is used to identify the repeating factor from a plurality of repeating factors configured via the second SIB signaling. The indication is configured via fields in the downlink control information (DCI) signaling. The indication is configured by at least one bit of a plurality of Cyclic Redundancy Check (CRC) bits in the DCI signaling used for scrambling scheduling Msg4 Physical Downlink Shared Channel (PDSCH) transmissions. The indication is configured through a field used to schedule DCI signaling transmissions on the Msg3 Physical Uplink Shared Channel (PUSCH), or The indication is based on the repetition factor for Msg3 transmission.

5. The method according to claim 4, wherein, The indication used to identify the repeating factor from a plurality of repeating factors configured via the second SIB signaling includes: One of four values ​​indicated in two bits of the two most significant bits (MSB), least significant bits (LSB), or other bits of the modulation and coding scheme (MCS) field, which includes DCI signaling; One of four values ​​indicated in the two bits of the reserved field of the DCI signaling; One of the four states indicated in the PUCCH resource indicator field of the DCI signaling; One of the four states indicated in the Hybrid Automatic Request (HARQ) process number field of the DCI signaling; or One of the four states indicated in the Physical Downlink Shared Channel (PDSCH) to HARQ Feedback Timing Indicator field of the DCI signaling. Each value of the two bits is mapped to a corresponding repetition factor. Each of the four states is mapped to a corresponding repetition factor.

6. The method according to claim 4, wherein, At least one bit among the plurality of CRC bits includes: The two CRC bits are scrambled by the Cell Radio Network Temporary Identifier (C-RNTI) or the temporary C-RNTI; or The two most significant bits (MSB) of the CRC bits are scrambled with information corresponding to the repeat factor.

7. The method according to claim 4, wherein, The repetition factor was determined to be: The determination is based on the defined relationship of the repetition factor for the Msg3 transmission; The defined fraction of the repetition factor transmitted for Msg3; or The same as the repetition factor for the transmission of Msg3.

8. The method according to claim 4, wherein, The DCI signaling includes: The first DCI signaling, after the successful completion of the random access procedure, is scrambled by the Cell Radio Network Temporary Identifier (C-RNTI); DCI signaling scrambled by C-RNTI after the successful completion of the random access procedure, and the DCI signaling prior to the configuration of dedicated PUCCH resources; DCI signaling scrambled by C-RNTI, and said DCI signaling is used by the wireless communication device to determine whether the random access procedure has been successfully completed when addressing PDCCH transmission using C-RNTI; or The DCI signaling is scrambled by Random Access (RA) RNTI, and the DCI signaling is configured prior to the configuration of dedicated PUCCH resources.

9. The method according to claim 8, wherein, The repetition factor configured via the DCI signaling is valid before the dedicated PUCCH resource is configured.

10. The method according to claim 1, comprising: In response to the fulfillment of a condition, the wireless communication device determines to send a message instructing the wireless communication device to perform PUCCH repetition using at least one public PUCCH resource, the condition including at least one of the following: When the wireless communication device initiates an initial random access, either a contention-based random access or a contention-free random access, When one or more repetition factors and a reference signal received power (RSRP) threshold are configured, and the measured RSRP is lower than the configured RSRP threshold, When one or more repetition factors are configured, and the RSRP threshold is not configured, When the wireless communication device initiates a handover, the handover includes at least a handover based on a contention-based random access procedure, or When the wireless communication device initiates a handover, the handover includes at least a handover based on a contention-free random access procedure.

11. A method comprising: The wireless communication node receives a message from the wireless communication device instructing the wireless communication device to perform Physical Uplink Control Channel (PUCCH) repetition. The PUCCH repetition includes at least one repetition of PUCCH transmission on public PUCCH resources.

12. A non-transient computer-readable medium storing instructions that, when executed by at least one processor, cause the at least one processor to perform the method according to any one of claims 1 to 11.

13. An apparatus comprising: At least one processor is configured to perform the method according to any one of claims 1 to 11.

Images