TRANSMISSIONS IN A 5G NR NETWORK

PRIORITY CLAIM

[0001] This application ciaims priority to United States Provisional Patent Application Serial No. 63/067,637, filed August 19, 2020 [reference number AD1942-Z], and United States Provisional Patent Application Serial No. 63/138,100, filed January 15, 2021 [reference number AD4708-Z], each of which is incorporated herein by reference in its entirety.

TECHNICAL. FIELD

[0002] Embodiments pertain to wireless communications. Some embodiments relate to repeated transmission of uplink channels in a fifthgeneration new radio (5G NR) network. Some embodiments relate repetition of a physical uplink shared channel (PUSCH) and/or a physical uplink control channel (PUCCH).

BACKGROUND

[0003] Mobile communication has evolved significantly from early voice systems to today’s highly sophisticated integrated communication platform. The next generation wireless communication system, 5G, or new ⁷ radio (NR) will provide access to information and sharing of data anywhere, anytime by various users and applications. NR is expected to be a unified network/system that target to meet vastly different and sometime conflicting performance dimensions and services. Such diverse multi-dimensional requirements are driven by different sendees and applications. In general, NR will evolve based on 3GPP LTE- Advanced with additional potential new Radio Access Technologies (RATs) to enrich people lives with better, simple and seamless wdreless connectivity solutions. NR will enable everything connected by wireless and deliver tast, rich contents and services.

[0004] For a cellular system, coverage is an important factor for successful operation. Compared to LTE, NR can be deployed at relatively higher carrier frequency in frequency range 1 (FR1), e.g., at 3.5GHz. In this case, coverage loss is expected due to larger path-loss, which makes it more challenging to maintain an adequate quality of sendee. Typically, uplink coverage is the bottleneck for system operation considering the low transmit power at the user equipment (UE) side. Thus, there are general needs for systems and methods that provide improved coverage for a UE.

BRIEF DESCRIPTION OF THE DRAWINGS

[0005] FIG. 1 A illustrates an architecture of a network, in accordance with some embodiments.

[0006] FIG. IB and FIG. 1C illustrate a non-roaming 5G sy stem architecture in accordance with some embodiments.

[0007] FIG. ID illustrates Simulation results for PUSCH with and without cross-slot channel estimation, in accordance with some embodiments. [0008] FIG. 2 illustrates Repetition bundle size for PUSCH repetition, in accordance with some embodiments.

[0009] FIG. 3 illustrates PUSCH repetition bundle in case of cancellation: option 1, in accordance with some embodiments.

[0010] FIG. 4 illustrates PUSCH repetition bundle in case of cancellation: option 2, in accordance with some embodiments.

[0011] FIG. 5 illustrates PUSCH repetition bundle on nominal PUSCH repetition, in accordance with some embodiments.

[0012] FIG. 6 illustrates PUSCH repetition bundle on actual PUSCH repetition, in accordance with some embodiments.

[0013] FIG. 7 illustrates a functional block diagram of a wireless communication device in accordance with some embodiments. DETAILED DESCRIPTION

[0014] The following description and the drawings sufficiently illustrate specific embodiments to enable those skilled in the art to practice them. Other embodiments may incorporate structural, logical, electrical, process, and other changes. Portions and features of some embodiments may be included in, or substituted for, those of other embodiments. Embodiments set forth in the claims encompass all available equivalents of those claims.

[0015] Embodiments disclosed herein provide for improved coverage for a user equipment (UE). In these embodiments, for joint channel estimation, a time domain window is specified during which a UE is expected to maintain power consistency and phase continuity among PUSCH transmissions subject to power consistency and phase continuity requirements.

[0016] In some embodiments, a UE configured for operation in a fifthgeneration new radio (5G NR) network is indicated for repetition of an uplink channel. The uplink channel may be at least one of a physical uplink shared channel (PUSCH) or a physical uplink control channel (PUCCH). In these embodiments, the UE may be configured to determine a size of a repetition bundle and apply a same precoder and transmit power for each repetition of the uplink channel transmitted within the repetition bundle. In these embodiments, the UE may determine whether to switch to a new precoder for uplink channel transmissions after a repetition bundle boundary' or to continue to use the same precoder for the uplink channel transmissions after the repetition bundle boundary. In these embodiments, use of the same precoder by the UE for each repetition of an uplink channel (i.e., the PUSCH and/or the PUCCH) within a repetition bundle allows the gNB to perform joint channel estimation based on demodulation reference signal (DMRS) within the repetition bundle. In these embodiments, a generation Node B (gNB) may perform cross-slot channel estimation for receiving the uplink channel. These embodiments are described in more detail below.

[0017] In some embodiments, the repetition bundle corresponds to a time-domain window' during which the UE may be configured to maintain power consistency and phase continuity for transmission of each repetition ot the uplink channel within the repetition bundle. In these embodiments for PUSCH repetition, the UE may use the same transmit power level and the same precoder for each PUSCH transmission within a repetition bundle. In these embodiments for PUCCH repetition, the UE may use the same transmit power level and the same precoder for each PUCCH transmission within a repetition bundle. These embodiments are described in more detail below.

[0018] In some embodiments, the UE may transmit a demodulation reference signal (DMRS) within the repetition bundle. The DMRS may be used by the gNB for cross-slot channel estimation within the repetition bundle to decode the uplink channel. In these embodiments, the UE may apply the same precoder for the DMRS and the associated uplink channel transmission. These embodiments are described in more detail below'.

[0019] In some embodiments, the size of the repetition bundle comprises at least one of a number of repetitions of the uplink channel, a number of time slots, or a number of transmission occasions. In these embodiments, the UE may to refrain from changing a precoder used for transmission of each repetition of the uplink channel within the repetition bundle. These embodiments are described in more detail below.

[0020] In some embodiments, the size of the repetition bundle may be configured by higher layers. In these embodiments, the UE may decode higher layer signalling from the gNB comprising at least one of a system information block (SIB), and radio-resource control (RRC) signalling. In some embodiments, the size of the repetition bundle may be predefined (configured by remaining minimum system information (RMSI) (e.g., SIB1), or NR other system information (OSI)). These embodiments are described in more detail below'.

[0021] In some embodiments, the UE may decode a downlink control information (DCI) from the gNB to determine the size of the repetition bundle. In these embodiments, the gNB may dynamically signal the size of the repetition bundle to the UE. In some embodiments, the DCI indicates one size of a set of sizes of the repetition bundle. These embodiments are described in more detail below'. [0022] In some embodiments, the UE may implicitly denve or determine the size of the repetition bundle based on a number of repetitions or slots for the uplink channel. These embodiments are described in more detail below, [0023] In some embodiments, when the uplink channel is the PUSCH, and when the UE is configured to apply enhanced inter-slot frequency hopping for PUSCH repetition, the size of the repetition bundle may correspond with a number of contiguous PUSCH repetitions on a same frequency resource. These embodiments are described in more detail below.

[0024] In some embodiments, when the uplink channel is the PUSCH and the UE is configured to perform a 2-step RACH procedure, PUSCH repetition using the same precoder is applied within the repetition bundle for MsgA of the 2-step RACH procedure. In some embodiments, when the uplink channel is the PUSCH and the LIE is configured to perform a 4-step RACH procedure, the PUSCH repetition using the same precoder is applied within the repetition bundle for Msg3 of the 4-step RACH procedure. In some embodiments, when the UE is configured to perform a 4-step RACH procedure, a number of repetitions of the PUSCH for the Msg3 is based on a reference signal received power (RSRP) threshold. These embodiments are described in more detail below.

[0025] In some embodiments, for improved spatial diversity, the UE may change precoders at the repetition bundle boundary. In these embodiments, the UE may apply a first, precoder for each PUSCH transmitted during a first repetition bundle and the UE may apply a second precoder for each PUSCH transmitted during a second repetition bundle (i.e., after the repetition bundle boundary). In these embodiments, two or more antennas may be used for transmission of the PUSCH. These embodiments are described in more detail below.

[0026] Some embodiments are directed to a non-transitory computer- readable storage medium that stores instructions for execution by processing circuitry of a user equipment (UE) configured for operation in a fifth-generation new radio (5G NR) network. In these embodiments, when the UE is indicated for repetition of an uplink channel, the processing circuitry may be configured to determine a size ot a repetition bundle and apply a same precoder and transmit power for each repetition of the uplink channel transmitted within the repetition bundle. The UE is configurable to determine whether to swatch to a new' precoder for uplink channel transmissions after a repetition bundle boundary or to continue to use the same precoder for the uplink channel transmissions after the repetition bundle boundary. These embodiments are described in more detail below.

[0027] Some embodiments are directed to a generation Node B (gNB). In these embodiments, for a user equipment (UE) is indicated for repetition of an uplink channel, the gNB may be configured to determine a size of a repetition bundle and perform joint channel estimation based on demodulation reference signal (DMRS) received from the UE within the repetition bundle. In these embodiments, the gNB may attempt to decode each repetition of the uplink channel transmitted by the UE within the repetition bundle based on the channel estimation for the repetition bundle. In these embodiments, the gNB may perform a separate joint channel estimate for each repetition bundle for use in decoding uplink channel transmission from the UE within an associated repetition bundle. In some embodiments, the UE may initiate performance of the separate joint channel estimate at a repetition bundle boundary although this is not a requirement. These embodiments are described in more detail below ⁷ .

[0028] FIG. I A illustrates an architecture of a network in accordance wdth some embodiments. The network 140A is shown to include user equipment (UE) 101 and UE 102. The UEs 101 and 102 are illustrated as smartphones (e.g., handheld touchscreen mobile computing devices connectable to one or more cellular networks) but may also include any mobile or non-mobile computing device, such as Personal Data Assistants (PDAs), pagers, laptop computers, desktop computers, wireless handsets, drones, or any other computing device including a wired and/or wireless communications interface. The UEs 101 and 102 can be collectively referred to herein as UE 101, and UE 101 can be used to perform one or more of the techniques disclosed herein. [0029] Any of the radio links described herein (e.g., as used in the network 140A or any other illustrated network) may operate according to any exemplary radio communication technology and/or standard.

[0030] LTE and LTE- Advanced are standards for wireless communications of high-speed data for UE such as mobile telephones. In LTE- Advanced and various wireless systems, carrier aggregation is a technology according to which multiple carrier signals operating on different frequencies may be used to carry communications for a single UE, thus increasing the bandwidth available to a single device. In some embodiments, carrier aggregation may be used where one or more component carriers operate on unlicensed frequencies.

[0031] Embodiments described herein can be used in the context of any spectrum management scheme including, for example, dedicated licensed spectrum, unlicensed spectrum, (licensed) shared spectrum (such as Licensed Shared Access (LSA) in 2.3-2.4 GHz, 3.4-3.6 GHz, 3.6-3.8 GHz, and further frequencies and Spectrum Access System (SAS) in 3.55-3.7 GHz and further frequencies).

[0032] Embodiments described herein can also be applied to different Single Carrier or OFDM flavors (CP-OFDM, SC-FDMA, SC-OFDM, filter bank-based multicarrier (FBMC), OFDMA, etc.) and in particular 3GPP NR (New Radio) by allocating the OFDM carrier data bit vectors to the corresponding symbol resources.

[0033] In some embodiments, any of the UEs 101 and 102 can comprise an Intemet-of-Things (loT) UE or a Cellular loT (CIoT) UE, which can comprise a network access layer designed for low-power loT applications utilizing short-lived UE connections. In some embodiments, any of the UEs 101 and 102 can include a narrowband (NB) loT UE (e.g., such as an enhanced NB- loT (eNB-IoT) UE and Further Enhanced (FeNB-IoT) UE). An loT UE can utilize technologies such as machine-to-machine (M2M) or machine-type communications (MTC) for exchanging data with an MTC server or device via a public land mobile network (PLMN), Proximity -Based Service (ProSe) or device-to-device (D2D) communication, sensor networks, or loT networks. The M2M or MTC exchange of data may be a machine-initiated exchange of data. An loT network includes interconnecting loT UEs, which may include uniquely identifiable embedded computing devices (within the Internet infrastructure), with short-lived connections. The loT UEs may execute background applications (e.g., keep-alive messages, status updates, etc.) to facilitate the connections of the loT network.

[0034] In some embodiments, any of the UEs 101 and 102 can include enhanced MTC (eMTC) UEs or further enhanced MTC (FeMTC) UEs.

[0035] The UEs 101 and 102 may be configured to connect, e.g., communicatively couple, with a radio access network (RAN) 110. The RAN 110 may be, for example, an Evolved Universal Mobile Telecommunications System (UNITS) Terrestrial Radio Access Network (E-UTRAN), a NextGen RAN (NG RAN), or some other type of RAN. The UEs 101 and 102 utilize connections 103 and 104, respectively, each of winch comprises a physical communications interface or layer (discussed in further detail below), in this example, the connections 103 and 104 are illustrated as an air interface to enable communicative coupling and can be consistent with cellular communications protocols, such as a Global System for Mobile Communications (GSM) protocol, a code-division multiple access (CDMA) network protocol, a Push-to- Talk (PTT) protocol, a PTT over Cellular (POC) protocol, a Universal Mobile Telecommunications System (UMTS) protocol, a 3GPP Long Term Evolution (UTE) protocol, a fifth-generation (5G) protocol, a New ⁷ Radio (NR) protocol, and the like.

[0036] In an aspect, the UEs 101 and 102 may further directly exchange communication data via a ProSe interface 105. The ProSe interface 105 may alternatively be referred to as a sidelink interface comprising one or more logical channels, including but not limited to a Physical Sidelink Control Channel (PSCCH), a Physical Sidelink Shared Channel (PSSCH), a Physical Sidelink Discovery Channel (PSDCH), and a Physical Sidelink Broadcast Channel (PSBCH). [0037] The UE 102 is shown to be configured to access an access point (AP) 106 via connection 107. The connection 107 can comprise a local wireless connection, such as, for example, a connection consistent with any IEEE 802.11 protocol, according to which the AP 106 can comprise a wireless fidelity (WiFi®) router. In this example, the AP 106 is shown to be connected to the Internet without connecting to the core network of the wireless system (described in further detail below).

[0038] The RAN 110 can include one or more access nodes that enable the connections 103 and 104. These access nodes (ANs) can be referred to as base stations (BSs), NodeBs, evolved NodeBs (eNBs), Next Generation NodeBs (gNBs), RAN nodes, and the like, and can comprise ground stations (e.g., terrestrial access points) or satellite stations providing coverage within a geographic area (e.g., a cell). In some embodiments, the communication nodes 111 and 112 can be transmission/reception points (TRPs). In instances when the communication nodes 111 and 112 are NodeBs (e.g., eNBs or gNBs), one or more TRPs can function within the communication cell of the NodeBs. The RAN 110 may include one or more ILAN nodes for providing macrocells, e.g., macro-RAN node 111, and one or more RAN nodes for providing femtocells or picocells (e.g., cells having smaller coverage areas, smaller user capacity, or higher bandwidth compared to macrocells), e.g., low power (LP) RAN node 112.

[0039] Any of the RAN nodes 11 1 and 112 can terminate the air interface protocol and can be the first point of contact for the UEs 101 and 102. In some embodiments, any of the RAN nodes 111 and 1 12 can fulfill various logical functions for the RAN 110 including, but not limited to, radio network controller (RNC) functions such as radio bearer management, uplink and downlink dynamic radio resource management and data packet scheduling, and mobility management. In an example, any of the nodes 111 and/or 1 12 can be a new generation Node-B (gNB), an evolved node-B (eNB), or another type of RAN node.

[0040] The RAN 110 is shown to be communicatively coupled to a core network (CN) 120 via an SI interface 113. In embodiments, the CN 120 may be an evolved packet core (EPC) network, a NextGen Packet Core (NPC) network, or some other type of CN (e.g., as illustrated in reference to FIGS. 1B-1C). In this aspect, the SI interface 113 is split into two parts: the Sl-U interface 114, which carries traffic data between the RAN nodes 111 and 112 and the serving gateway (S-GW) 122, and the SI -mobility management entity (MME) interface 115, which is a signaling interface between the RAN nodes 111 and 112 and MMEs 121.

[0041] In this aspect, the CN 120 comprises the MMEs 121, the S-GW 122, the Packet Data Network (PDN) Gateway (P-GW) 123, and a home subscriber server (HSS) 124. The MMEs 121 may be similar in function to the control plane of legacy Serving General Packet Radio Sendee (GPRS) Support Nodes (SGSN). The MMEs 121 may manage mobility embodiments in access such as gateway selection and tracking area list management. The HSS 124 may comprise a database for network users, including subscription-related information to support the network entities' handling of communication sessions. The CN 120 may comprise one or several HSSs 124, depending on the number of mobile subscribers, on the capacity of the equipment, on the organization of the network, etc. For example, the HSS 124 can provide support, for routing/roaming, authentication, authorization, naming/addressing resolution, location dependencies, etc.

[0042] The S-GW 122 may terminate the SI interface 113 towards the RAN 110, and routes data packets between the RAN 110 and the CN 120. In addition, the S-GW 122 may be a local mobility anchor point for inter-RAN node handovers and also may provide an anchor for inter-3GPP mobility. Other responsibilities of the S-GW 122 may include a lawful intercept, charging, and some policy enforcement.

[0043] The P-GW 123 may terminate an SGi interface toward a PDN. The P-GW 123 may route data packets between the EPC network 120 and external networks such as a network including the application server 184 (alternatively referred to as application function ( AF)) via an Internet Protocol (IP) interface 125. The P-GW 123 can also communicate data to other external networks 131 A, which can include the Internet, IP multimedia subsystem (IPS; network, and other networks. Generally, the application server 184 may be an element offering applications that use IP bearer resources with the core network (e.g., L MTS Packet Services (PS) domain, LTE PS data sendees, etc.). In this aspect, the P-GW 123 is shown to be communicatively coupled to an application server 184 via an IP interface 125. The application server 184 can also be configured to support one or more communication sendees (e.g., Voice-over- Internet Protocol (VoIP) sessions, PTT sessions, group communication sessions, social networking sendees, etc.) for the UEs 101 and 102 via the CN 120.

[0044] The P-GW 123 may further be a node for policy enforcement and charging data collection. Policy and Charging Rules Function (PCRF) 126 is the policy and charging control element of the CN 120. In a non-roaming scenario, in some embodiments, there may be a single PCRF in the Home Public Land Mobile Network (HPLMN) associated with a UE's Internet Protocol Connectivity Access Network (IP-CAN) session. In a roaming scenario with a local breakout of traffic, there may be two PCRFs associated with a UE's IP- CAN session: a Home PCRF (H-PCRF) within an HPLMN and a Visited PCRF (V-PCRF) within a Visited Public Land Mobile Network (VPLMN). The PCRF 126 may be communicatively coupled to the application server 184 via the P- GW 123.

[0045] In some embodiments, the communication network 140 A can be an loT network or a 5G network, including 5G new radio network using communications in the licensed (5G NR) and the unlicensed (5G NR-U) spectrum. One of the current enablers of loT is the narrowband-IoT (NB-IoT). [0046] An NG system architecture can include the RAN 1 10 and a 5G network core (5GC) 120. The NG-RAN 110 can include a plurality of nodes, such as gNBs and NG-eNBs. The core network 120 (e.g., a 5G core network or 5GC) can include an access and mobility function (AMF) and/or a user plane function (UPF). The AMF and the UPF can be communicatively coupled to the gNBs and the NG-eNBs via NG interfaces. More specifically, in some embodiments, the gNBs and the NG-eNBs can be connected to the AMF by NG- C interfaces, and to the UPF by NG-U interfaces. The gNBs and the NG-eNBs can be coupled to each other via Xn interfaces.

[0047] In some embodiments, the NG system architecture can use reference points between various nodes as provided by 3GPP Technical Specification (TS) 23.501 (e.g., V15.4.0, 2018-12). In some embodiments, each of the gNBs and the NG-eNBs can be implemented as a base station, a mobile edge server, a small cell, a home eNB, and so forth. In some embodiments, a gNB can be a master node (MN) and NG-eNB can be a secondary node (SN) in a 5G architecture.

[0048] FIG. IB illustrates a non-roaming 5G system architecture in accordance with some embodiments. Referring to FIG. IB, there is illustrated a 5G system architecture 140B in a reference point representation. More specifically, UE 102 can be in communication with RAN 110 as well as one or more other 5G core (5GC) network entities. The 5G system architecture 140B includes a plurality of network functions (NFs), such as access and mobility management function (AMF) 132, session management function (SMF) 136, policy control function (PCF) 148, application function (AF) 150, user plane function (UPF) 134, network slice selection function (NSSF) 142, authentication server function (AUSF) 144, and unified data management (UDM)/home subscriber server (FISS) 146. The UPF 134 can provide a connection to a data network (DN) 152, which can include, for example, operator services, Internet access, or third-party services. The AMF 132 can be used to manage access control and mobility and can also include network slice selection functionality. The SMF 136 can be configured to set up and manage various sessions according to network policy. The UPF 134 can be deployed in one or more configurations according to the desired service type. The PCF 148 can be configured to provide a policy framework using network slicing, mobility management, and roaming (similar to PCRF in a 4G communication system). The UDM can be configured to store subscriber profiles and data (similar to an HSS in a 4G communication system). [0049] In some embodiments, the 5G system architecture 140B includes an EP multimedia subsystem (IMS) 168B as well as a plurality of IP multimedia core network subsystem entities, such as call session control functions (CSCFs). More specifically, the IMS 168B includes a CSCF, which can act as a proxy CSCF (P-CSCF) 162BE, a serving CSCF (S-CSCF) 164B, an emergency CSCF (E-CSCF) (not illustrated in FIG. IB), or interrogating CSCF (I-CSCF) 166B. The P-CSCF 162B can be configured to be the first contact point for the UE 102 within the IM subsystem (IMS) 168B. The S-CSCF 164B can be configured to handle the session states in the network, and the E-CSCF can be configured to handle certain embodiments of emergency sessions such as routing an emergency request to the correct emergency center or PS AP. The I-CSCF 166B can be configured to function as the contact point within an operator's network for all IMS connections destined to a subscriber of that network operator, or a roaming subscriber currently located within that network operator's service area. In some embodiments, the I-CSCF 166B can be connected to another IP multimedia network 170E (e.g., an IMS operated by a different network operator).

[0050] In some embodiments, the UDM/HSS 146 can be coupled to an application server 160E, which can include a telephony application server (TAS) or another application server (AS). The AS 160B can be coupled to the IMS 168B via the S-CSCF 164B or the I-CSCF 166B.

[0051] A reference point representation shows that interaction can exist between corresponding NF services. For example, FIG. I B illustrates the following reference points: N1 (between the UE 102 and the AMF 132), N2 (between the RAN 110 and the AMF 132), N3 (between the RAN 110 and the UPF 134), N4 (between the SMF 136 and the UPF 134), N5 (between the PCF 148 and the AF 150, not shown), N6 (between the UPF 134 and the DN 152), N7 (between the SMF 136 and the PCF 148, not shown), N8 (between the UDM 146 and the AMF 132, not shown), N9 (between two UPFs 134, not shown), N10 (between the UDM 146 and the SMF 136, not shown), N11 (between the AMF 132 and the SMF 136, not shown), N12 (between the AUSF 144 and the AMF 132, not shown), N13 (between the AUSF 144 and the UDM 146, not shown), N14 (between two AMFs 132, not shown;, N15 (between the PCF 148 and the AMF 132 in case of a non-roaming scenario, or between the PCF 148 and a visited network and AMF 132 in case of a roaming scenario, not shown), N16 (between two SMFs, not shown), and N22 (between AMF 132 and NSSF 142, not shown). Other reference point representations not shown in FIG. IB can also be used.

[0052] FIG. 1C illustrates a 5G system architecture 140C and a servicebased representation. In addition to the network entities illustrated in FIG. IB, system architecture 140C can also include a network exposure function (NEF) 154 and a network repository function (NRF) 156. In some embodiments, 5G system architectures can be sendee-based and interaction between network functions can be represented by corresponding point-to-point reference points Ni or as senice-based interfaces.

[0053] In some embodiments, as illustrated in FIG. 1C, service-based representations can be used to represent network functions within the control plane that, enable other authorized network functions to access their services. In this regard, 5G system architecture 140C can include the following sendee-based interfaces: Namf 158H (a sendee-based interface exhibited by the AMF 132), Nsmf 1581 (a sendee-based interface exhibited by the SMF 136), Nnef 158B (a service-based interface exhibited by the NEF 154), Npcf 158D (a sendee-based interface exhibited by the PCF 148), a Nudrn 158E (a service-based interface exhibited by the UDM 146), Naf 158F (a service-based interface exhibited by the AF 150), Nnrf 158C (a service-based interface exhibited by the NRF 156), Nnssf 158 A (a service-based interface exhibited by the NSSF 142), Nausf 158G (a service-based interface exhibited by the AUSF 144). Other service-based interfaces (e.g., Nudr, N5g-eir, and Nudsf) not shown in FIG. 1C can also be used.

[0054] In some embodiments, any of the UEs or base stations described in connection with FIGS. 1 A-1C can be configured to perform the functionalities described herein. [0055] Mobile communication has evolved significantly from early voice systems to today’s highly sophisticated integrated communication platform. The next generation wireless communication system, 5G, or new ⁷ radio (NR) will provide access to information and sharing of data anywhere, anytime by various users and applications. NR is expected to be a unified network/system that targets to meet vastly different and sometimes conflicting performance dimensions and sendees. Such diverse multi-dimensional requirements are driven by different services and applications. In general, NR will evolve based on 3GPP LTE-Advanced with additional potential new' Radio Access Technologies (RATs) to enrich people's lives with better, simple, and seamless wireless connectivity solutions. NR will enable everything connected by wireless and deliver fast, rich content and sendees.

[0056] Rel-15 NR systems are designed to operate on the licensed spectrum. The NR-unlicensed (NR-U), a short-hand notation of the NR-based access to unlicensed spectrum, is a technology that enables the operation of NR systems on the unlicensed spectrum.

[0057] For NR, dynamic grant and configured grant based physical uplink shared channel (PUSCH) transmission are supported. For dynamic grant PUSCH transmission, PUSCH is scheduled by downlink control information (DC!) format 0 __0 , 0_1 or 0_2. Further, two types of configured grant PUSCH transmission are specified. In particular, for Type 1 configured grant PUSCH transmission, UL data transmission is only based on radio resource control (RRC) (re)configuration without any layer I (L1) signalling. In particular, semistatic resource may be configured for one UE, which includes time and frequency resource, modulation and coding scheme, reference signal, etc. For Type 2 configured grant. PUSCH transmission, UL. data transmission is based on both RRC configuration and L1 signaling to activate/ deactivate UL data transmission.

[0058] Further, in NR Rel-15, a number of repetitions can be configured for the transmission of PUSCH to help improve the coverage performance. When repetition is employed for the transmission ot PUCCH and PUSCH, same time domain resource allocation (TDRA) is used in each slot. In addition, interslot frequency hopping can be configured to improve the performance by exploiting frequency diversity. In Rel-16, the number of repetitions for PUSCH can be dynamically indicated in the DC I.

[0059] When UE is equipped with multiple antennas or multiple panels, UE may apply different precoders during repetition of uplink transmission. For open loop transmit diversity, precoder cycling pattern may need to be defined for uplink transmission. In case when same precoder is employ in consecutive repetition or slots for uplink transmission, gNB receiver may perform cross-slot channel estimation to further improve the decoding performance. In order to allow gNB to perform cross-slot channel estimation, precoding cycling pattern or repetition bundle size needs to be known at both UE and gNB side.

[0060] FIG. ID illustrates link level simulation results for PUSCH transmission with and without cross-slot channel estimation. In the simulations, it is assumed a fixed window size of 4 slots is used for cross-slot, channel estimation. From the figure, it can be observed that for PUSCH with 8 repetitions and inter-slot frequency hopping, when employing cross-slot channel estimation algorithm, >1.7dB performance gain can be achieved compared to without cross-slot channel estimation.

[0061] This disclosure describes systems and methods for indication of repetition bundle size for uplink transmission. Various embodiments may improve coverage of NR PUSCH.

[0062] Indication of repetition bundle size for uplink transmission

[0063] As mentioned above, when UE is equipped with multiple antennas or multiple panels, UE may apply different precoders during repetition of uplink transmission. For open loop transmit diversity, precoder cycling pattern may need to be defined for uplink transmission. In case when same precoder is employ in consecutive repetition or slots for uplink transmission, gNB receiver may perform cross-slot, channel estimation to further improve the decoding performance. In order to allow gNB to perform cross-slot channel estimation, precoding cycling pattern or repetition bundle size needs to be known at both UE and gNB side,

[0064] Embodiments of indication of repetition bundle size for uplink transmission are provided as follows:

[0065] In one embodiment of the disclosure, for open loop transmit diversity, PUSCH repetition bundle in time domain may be defined for PUSCH repetition, where within a PUSCH repetition bundle, UE shall use the same precoder for PUSCH transmission. In this case, gNB may perform joint channel estimation based on demodulation reference signal (DMRS) within the PUSCH repetition bundle. Note that this may apply for both PUSCH repetition type A and type B.

[0066] The size of PUSCH repetition bundle may be predefined in the specification, configured by higher layers via NR remaining minimum system information (RMSI), NR other system information (OSI) or dedicated radio resource control (RRC) signalling, dynamically indicated in the DCI, or a combination thereof. The PUSCH repetition bundle size may be defined in terms of number of slots, number of repetitions, number of transmission occasions, number of nominal repetitions or number of actual repetitions. Further, PUSCH repetition bundle starts from the first PUSCH repetition, which may be the first nominal repetition or first actual repetition.

[0067] In one option, the size of PUSCH repetition bundle can be configured by dedicated RRC signalling. When PUSCH repetition is enabled by RRC configuration or dynamic indication via DCI, UE shall apply same precoder within PUSCH repetition bundle.

[0068] Note that within the PUSCH repetition bundle, same transmit power is employed for the transmission of PUSCH repetition. Further, same transmit power, transmit beam and precoder within a PUSCH repetition bundle can apply for both PUSCH repetition type A and type B. This can also apply for dynamic grant based PUSCH (DG-PUSCH) and configured grant based PUSCH (CG-PUSCH). [0069] FIG. 2 illustrates one example repetition bundle size for PUSCH repetition. In the example, the size of PUSCH repetition bundle may be configured as 2 slots. In this case, UE shall apply a same precoder within the repetition bundle for PUSCH transmission.

[0070] In another embodiment of the disclosure, a set of repetition bundle sizes may be configured by higher layers via RMSI (SIB1), OSI or RRC signalling. Further, one field in the DCI can be used to indicate one repetition bundle size from the set of repetition bundle sizes for PUSCH transmission. In one example, repetition bundle sizes of 2 or 4 slots can be configured by higher layers, and one-bit field in the DCI can be used to indicate whether 2 or 4 slots are used as repetition bundle size.

[0071] In another embodiment of the disclosure, the size of PUSCH repetition bundle may be determined in accordance with the number of repetitions or slots for PUSCH transmission. In particular, assuming ‘Wep as the number of repetitions or slots for PUSCH transmission, the PUSCH repetition bundle size can be given by

[0072]

[0073] Where is an integer, which can be predefined in the specification. For instance, M = 2, or 4. is the number of repetitions or slots for PUSCH transmission. For instance, can be 2, 4, 6, 8, 16.

[0074] In another option, the size of PUSCH repetition bundle may be implicitly derived in accordance with the number of repetitions or slots for PUSCH transmission. In one example, when number of repetitions or slots for PUSCH transmission is greater than a certain threshold, one repetition bundle size can be used; while when number of repetitions or slots for PUSCH transmission is less than or equal to the certain threshold, another repetition bundle size can be used.

[0075] The rule to determine the size of PUSCH repetition bundle can be given by [0076]

[0077] Where are predefined PUSCH repetition bundle size; is the threshold, which can be predefined in the specification or configured by higher layers via RMSI (SIB I), OSI or RRC signalling.

[0078] In another embodiment of the disclosure, when enhanced interslot frequency hopping is applied for PUSCH repetition, where N contiguous PUSCH repetitions use a first same frequency resource before they switch to a second frequency resource, the size of PUSCH repetition bundle may be aligned with N contiguous PUSCH repetitions.

[0079] Note that N may be predefined in the specification or configured by higher layers via RMSI (SIB1), OSI or RRC signalling or determined in accordance with the number of repetitions or slots for PUSCH transmission.

[0080] In another embodiment of the disclosure, a combination of above options can be used to indicate/determine the repetition bundle size of PUSCH transmission. In one example, two sets of repetition bundle sizes can be configured by higher layers via RRC signalling. Further, one-bit field in the DCI can be used to indicate one set of repetition bundle size from the two sets of repetition bundle sizes is used.

[0081] When more than one values are configured in a set of repetition bundle sizes, and when one special value is indicated in the set of repetition bundle sizes, then implicit determination of repetition bundle size for PUSCH can be applied. For instance, when the number of number of repetitions or slots for PUSCH transmission is greater than a certain threshold, one predefined repetition bundle size can be used.

[0082] In another embodiment of the disclosure, for PUSCH transmission without corresponding PDCCH, e.g., configured grant PUSCH, the size of PUSCH repetition bundle may be configured by higher layers via RRC signalling or determined in accordance with the number of number of repetitions or slots for PUSCH transmission. [0083] Note that the dynamic indication of repetition bundle size may be included in the DCI format 0 1 and 0 2. For DCI format 0 0, when PUSCH repetition is applied, a default repetition bundle size may be used, e.g., 2 or 4 slots or repetitions.

[0084] In another embodiment of the disclosure, when repetition is employed for Msg3 transmission which is scheduled by an RAR UL grant and/or fallback RAR UL. grant, and Msg3 retransmission, which is scheduled by a DCI format 0__0 with Cyclic Redundancy Error (CRC) scrambled by a temporary cell - Radio Network Temporary Identifier (TC-RNTI), a default PUSCH repetition bundle size may be predefined in the specification or configured by RMSI (SLB1) which can be used for Msg3 repetition. In one example, default PUSCH repetition bundle size of 2 slots can be defined.

[0085] In another option, one field in the RAR UL grant and/or fallback RAR UL grant and/or DCI format 0 _0 with CRC scrambled by a TC-RNTI can be repurposed to indicate the PUSCH repetition bundle size for Msg3 transmission when repetition is applied.

[0086] Yet in another option, repetition bundle size may be determined in accordance with the number of repetitions or slots for Msg3 PUSCH transmission. Note that aforementioned options can be employed for this option.

[0087] Note that aforementioned mechanism may also apply for the MsgA PUSCH for 2-step RACK when repetition is applied for MsgA PUSCH.

[0088] In yet another option, whether to apply repetition bundling for Msg3 PUSCH transmission may be configured by higher layers via remaining minimum system information (RMSI) or other system information (OSI). In case when it is not configured, UE may employ different precoders for Msg3 PUSCH repetitions. Alternatively, whether to apply repetition bundling for Msg3 PUSCH transmission may be indicated explicitly in in the RAR UL grant and/or fallback R,AR UL grant and/or DCI format 0_0 with CRC scrambled by a TC- RNTI. In another option, some fields in the RAR UL grant and/or fallback RAR UL. grant and/or DCI format 0 0 with CRC scrambled by a TC-RNTI can be repurposed to indicate whether to apply repetition bundling for Msg3 PUSCH transmission.

[0089] In another embodiment of the disclosure, same Tx beam is applied for the transmission of Msg3 PUSCH repetition. In another option, same Tx beam is applied for the transmission of Msg3 PUSCH within a repetition bundle.

[0090] In another embodiment of the disclosure, for Msg3 PUSCH repetition, if a Msg3 PUSCH repetition collides with DL symbols from semistatic UL/DL configuration and SSB transmission at least in one symbol, UE shall drop the Msg3 PUSCH repetition without postponement. Note that semistatic DL/UL configuration is configured by tdd-UL-DL-ConfigurationCommon or tdd-ULDL-ConfigurationDedicated. Further, a SS/PBCH block symbol is a symbol indicated to a UE by ssb-PositionsInBurst in SIB 1 or ssb- PositionslnBurst in ServingCellConftgCommon.

[0091] In another embodiment of the disclosure, for a Msg3 PUSCH, a transport block (TB) can span multiple slots. Further, repetition may be employed in conjunction with the transmission carrying a TB spanning multiple slots. The above embodiments can be applied to indicate whether TB spanning multiple slots can be applied for Msg3 PUSCH transmission and to indicate the number of slots and/or the number of repetitions for Msg3 PUSCH transmission.

[0092] In another embodiment of the disclosure, multiple reference signal received power (RSRP) thresholds may be configured by higher layers via RM SI (SIB 1), OSI or RRC signalling. Further, each RSRP thresholds are associated with a certain configured or predefined number of repetitions for Msg3 PUSCH transmission. In one example, the following rule can be used to determine the number of repetitions for Msg3 PUSCH transmission

[0093]

[0094] if SSB-RSRP > RSRP threshold 1, UE uses 1 transmission for PUSCH Msg3

[0095] if SSB-RSRP <= RSRP threshold 1 and SSB-RSRP > RSRP threshold 2, UE uses 4 transmission for PUSCH Msg3 [0096] if SSB-RSRP <= RSRP threshold 2 and SSB-RSRP > RSRP threshold 3, UE uses 8 transmission for PUSCH Msg3

[0097] if SSB-RSRP <- RSRP threshold 3, UE uses 16 transmission for PUSCH Msg3

[0098]

[0099] In another embodiment of the disclosure, for PUSCH repetition type A, in case when a repetition or transmission occasion of the PUSCH transmission is cancelled during the repetition, e.g., due to overlapping of other physical channels or semi-static TDD DL/UL configuration, PUSCH bundle in time is continued regardless of whether one PUSCH repetition or transmission occasion is dropped.

[00100] FIG. 3 illustrates one example of PUSCH repetition bundle in case of cancellation of PUSCH transmission with repetition. In the example, PUSCH transmission in the slot# n+ 1 is dropped. Further, PUSCH bundle size of 2 slots is employed. Based on this option, UE will continue PUSCH repetition bundle without considering the cancellation of PUSCH transmission. In this case, UE applies a same precoder for PUSCH transmission in slot #n and #n+2.

[00101] In another embodiment of the disclosure, for PUSCH repetition type A, in case when a repetition or transmissi on occasion of the PUSCH transmission is cancelled during the repetition, e.g., due to overlapping of other physical channels or semi-static TDD DL/UL configuration, PUSCH bundle in time is resumed after the cancellation.

[00102] FIG. 4 illustrates one example of PUSCH repetition bundle in case of cancellation of PUSCH transmission with repetition. In the example, PUSCH transmission in the slot# n+1 is dropped. Further, PUSCH bundle size of 2 slots is employed. Based on this option, UE will resume PUSCH repetition bundle after cancellation. In this case, UE applies a same precoder for PUSCH transmission in slot #n+2 and #n+3.

[00103] In another embodiment of the disclosure, for PUSCH repetition type B, PUTSCH repetition bundle is applied on the nominal PUSCH repetition. In other words, regardless of whether multiple segments are generated due to conflict with DL symbols, invalid symbols and/or slot boundary, PUSCH repetition bundle or same precoder within PUSCH repetition bundle size is applied on the nominal PUSCH repetition before handling the collision.

[00104] FIG. 5 illustrates one example of PUSCH repetition bundle on nominal PUSCH repetition. In the example, it is assumed that starting symbol of first nominal PUSCH repetition is 6 and length of PUSCH repetition is 14 symbols. Further, 4 repetitions are applied for PUSCH transmission. Based on the PUSCH repetition type B, PUSCH repetition is divided into two segments for each repetition due to across slot boundary. For this option, regardless of multiple segments on actual transmission in each repetition, PUSCH repetition bundle is applied on nominal repetition. Assuming PUSCH repetition bundle size of 2 repetitions, same precoder for PUSCH transmission is used in nominal repetition #1 and #2; and nominal repetition #3 and #4, respectively.

[00105] In another embodiment of the disclosure, for PUSCH with repetition type B, PUSCH repetition bundle is applied on the actual PUSCH repetition. In other words, PUSCH repetition bundle or same precoder within PUSCH repetition bundle size is applied on the actual PUSCH repetition after handling the collision with DL symbols, invalid symbols and/or slot boundary.

[00106] FIG. 6 illustrates one example of PUSCH repetition bundle on actual PUSCH repetition. In the example, it is assumed that starting symbol of first nominal PUSCH repetition is 6 and length of PUSCH repetition is 14 symbols. Further, 4 repetitions are applied for PUSCH transmission. Based on the PUSCH repetition type B, PUSCH repetition is divided into two segments for each repetition due to across slot boundary. In particular, repetition #1-1 and repetition #1-2 are the first, and second actual repetition within nominal repetition #1, while repetition #2-1 and repetition #2-2 are the first and second actual repetition within nominal repetition #2, and so on,

[00107] Assuming PUSCH repetition bundle size of 2 repetitions, same precoder for PUSCH transmission is used in repetition#!- 1 and #1-2, and repetition #2-1 and #2-2, respectively, and so on. [00108] In another embodiment ot the disclosure, for PUSCH repetition type B, repetition bundling may be configured based on the slot boundary. In this case, the repetition bundling is defined as a number of slots for PUSCH repetitions. Further, actual PUSCH repetition in the repetition bundling would employ same Tx beam, precoder and transmit power.

[00109] In another embodiment of the disclosure, the aforementioned embodiments can also apply for physical uplink control channel (PUCCH). In one option, for PUCCH carrying dynamic hybrid automatic repeat request - acknowledgement (HARQ-ACK), the size of PUCCH repetition bundle may be configured by higher layers via RRC signalling, dynamically indicated in the DCI or a combination thereof Alternatively, it can be determined in accordance with the number of number of repetitions or slots for PUCCH transmission [00110] For PUCCH carrying scheduling request (SR) and channel state information (('SB report, the size of PUCCH repetition bundle may be configured by higher layers via RRC signalling or determined in accordance with the number of number of repetitions or slots for PUCCH transmission.

[00111] Note that when the size of PUCCH repetition bundle is configured by RRC signalling, it can be configured per PUCCH resource, per PUCCH format or per PUCCH resource set.

[00112] In another embodiment of the disclosure, the aforementioned embodiments can also apply for physical downlink control channel (PDCCH) and/or physical downlink shared channel (PDSCH) when repetition is applied for the PDCCH and/or PDSCH, respectively.

[00113]

[00114] FIG. 7 illustrates a functional block diagram of a wireless communication device, in accordance with some embodiments. Wireless communication device 700 may be suitable for use as a UE or gNB configured for operation in a 5G NR network. The communication device 700 may also be suitable for use as a handheld device, a mobile device, a cellular telephone, a smartphone, a tablet, a netbook, a wireless terminal, a laptop computer, a wearable computer device, a femtocell, a high data rate (HDR) subscriber device, an access point, an access terminal, or other personal communication system (PCS) device.

[00115] The communication device 700 may include communications circuitry 702 and a transceiver 710 for transmitting and receiving signals to and from other communication devices using one or more antennas 701. The communications circuitry 702 may include circuitry' that can operate the physical layer (PHY) communications and/or medium access control (MAC) communications for controlling access to the wireless medium, and/or any other communications layers for transmitting and receiving signals. The communication device 700 may also include processing circuitry 706 and memory' 708 arranged to perform the operations described herein. In some embodiments, the communications circuitry 702 and the processing circuitry 706 may be configured to perform operations detailed in the above figures, diagrams, and flows.

[00116] In accordance with some embodiments, the communications circuitry 702 may be arranged to contend for a wireless medium and configure frames or packets for communicating over the wireless medium. The communications circuitry 702 may be arranged to transmit and receive signals. The communications circuitry 702 may also include circuitry for modul ati on/demodul ati on, upconversi on/downconversi on, filteri ng, amplification, etc. In some embodiments, the processing circuitry 706 of the communication device 700 may include one or more processors. In other embodiments, two or more antennas 701 may be coupled to the communications circuitry 702 arranged for sending and receiving signals. The memory 708 may store information for configuring the processing circuitry 706 to perform operations for configuring and transmitting message frames and performing the various operations described herein. The memory 708 may include any type of memory, including n on-transitory memory, for storing information in a form readable by a machine (e.g., a computer). For example, the memory 708 may include a computer-readable storage device, read-only memory (ROM), random- access memory' (RAM), magnetic disk storage media, optical storage media, flash-memory devices and other storage devices and media.

[00117] In some embodiments, the communication device 700 may be part of a portable wireless communication device, such as a personal digital assistant (PDA), a laptop or portable computer with wireless communication capability, a web tablet, a wireless telephone, a smartphone, a wireless headset, a pager, an instant messaging device, a digital camera, an access point, a television, a medical device (e.g., a heart rate monitor, a blood pressure monitor, etc.), a wearable computer device, or another device that may receive and/or transmit information wirelessly.

[00118] In some embodiments, the communication device 700 may include one or more antennas 701. The antennas 701 may include one or more directional or omnidirectional antennas, including, for example, dipole antennas, monopole antennas, patch antennas, loop antennas, microstrip antennas, or other types of antennas suitable for transmission of RF signals. In some embodiments, instead of two or more antennas, a single antenna with multiple apertures may be used. In these embodiments, each aperture may be considered a separate antenna. In some multiple-input multiple-output (MIMO) embodiments, the antennas may be effectively separated for spatial diversity and the different channel characteristics that may result between each of the antennas and the antennas of a transmitting device.

[00119] In some embodiments, the communication device 700 may include one or more of a keyboard, a display, a non-volatile memory'' port, multiple antennas, a graphics processor, an application processor, speakers, and other mobile device elements. The display may be an LCD screen including a touch screen.

[00120] Although the communication device 700 is illustrated as having several separate functional elements, two or more of the functional elements may be combined and may be implemented by combinations of software-configured elements, such as processing elements including digital signal processors (DSPs), and/or other hardware elements. For example, some elements may include one or more microprocessors, DSPs, field-programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), radio-frequency integrated circuits (RFICs) and combinations of various hardware and logic circuitry for performing at least the functions described herein. In some embodiments, the functional elements of the communication device 700 may refer to one or more processes operating on one or more processing elements.

[00121] Examples:

[00122] Example 1 may include a method of wireless communication for a fifth generation (5G) or new radio (NR) system:

[00123] receiving, by a UE from a gNodeB, configuration information to indicate a physical uplink shared channel (PUSCH) repetition bundle size when a repetition is employed for the PUSCH transmission;

[00124] applying, by the UE, a same precoder for the PUSCH transmission during the configured PUSCH repetition bundle size.

[00125] Example 2 may include the method of example 1 or some other example herein, wherein the size of PUSCH repetition bundle may be predefined in the specification, configured by higher layers via NR remaining minimum system information (RMSI), NR other system information (OSI) or dedicated radio resource control (RRC) signalling, dynamically indicated in the DCI, or a combination thereof.

[00126] Example 3 may include the method of example 1 or some other example herein, wherein PUSCH repetition bundle size may be defined in terms of number of slots, number of repetitions, number of transmission occasions, number of nominal repetitions or number of actual repetitions, wherein, PUSCH repetition bundle starts from the first PUSCH repetition, which may be the first nominal repetition or first actual repetition.

[00127] Example 4 may include the method of example I or some other example herein, wherein a set of repetition bundle sizes may be configured by higher layers via RMSI (SIB1), OSI or RRC signalling; wherein one field in the DCI can be used to indicate one repetition bundle size from the set of repetition bundle sizes for PUSCH transmission. [00128] Example 5 may include the method of example 1 or some other example herein, wherein the size of PUSCH repetition bundle may be determined in accordance with the number of repetitions or slots for PUSCH transmission.

[00129] Example 6 may include the method of example I or some other example herein, wherein the size of PUSCH repetition bundle may be implicitly derived in accordance with the number of repetitions or slots for PUSCH transmission

[00130] Example 7 may include the method of example 1 or some other example herein, wherein when enhanced inter-slot frequency hopping is applied for PUSCH repetition, where N contiguous PUSCH repetitions use a first same frequency resource before they switch to a second frequency resource, the size of PUSCH repetition bundle may be aligned with N contiguous PUSCH repetitions. [00131] Example 8 may include the method of example 1 or some other example herein, wherein a combination of above options can be used to indicate/determine the repetition bundle size of PUSCH transmission.

[00132] Example 9 may include the method of example 1 or some other example herein, wherein for PUSCH transmission without corresponding PDCCH, e.g., configured grant PUSCH, the size of PUSCH repetition bundle may be configured by higher layers via RRC signalling or determined in accordance with the number of number of repetitions or slots for PUSCH transmission.

[00133] Example 10 may include the method of example I or some other example herein, wherein when repetition is employed for Msg3 transmission which is scheduled by RAR UL grant and/or fallbackRAR UL grant, and Msg3 retransmission, which is scheduled by a DCI format 0 0 with Cyclic Redundancy Error (CRC) scrambled by a temporary cell - Radio Network Temporary Identifier (TC-RNTI), a default PUSCH repetition bundle size may be predefined in the specification or configured by RMSI (SIB 1 )

[00134] Example 11 may include the method of example 1 or some other example herein, wherein one field in the RAR UL grant and/or fallbackRAR UL grant and/or DCI format 0_0 with CRC scrambled by a TC-RNTI can be repurposed to indicate the PUSCH repetition bundle size tor Msg3 transmission when repetition is applied.

[00135] Example 12 may include the method of example 1 or some other example herein, wherein for PUSCH repetition type A, in case when a repetition or transmission occasion of the PUSCH transmission is cancelled during the repetition, e.g., due to overlapping of other physical channels or semi-static TDD DL/UL configuration, PUSCH bundle in time is continued regardless of whether one PUSCH repetition or transmission occasion is dropped

[00136] Example 13 may include the method of example I or some other example herein, wherein for PUSCH repetition type A, in case when a repetition or transmission occasion of the PUSCH transmission is cancelled during the repetition, e.g., due to overlapping of other physical channels or semi-static TDD DL/UL configuration, PUSCH bundle in time is resumed after the cancellation.

[00137] Example 15 may include the method of example 1 or some other example herein, wherein for PUSCH repetition type B, PUSCH repetition bundle is applied on the nominal PUSCH repetition.

[00138] Example 16 may include the method of example 1 or some other example herein, wherein for PUSCH with repetition type B, PUSCH repetition bundle is applied on the actual PUSCH repetition.

[00139] Example 17 may include the method of example 1 or some other example herein, wherein the aforementioned embodiments can also apply for physical uplink control channel (PUCCH).

[00140] Example 18 may include the method of example 1 or some other example herein, wherein the size of PUCCH repetition bundle can be configured per PUCCH resource, per PUCCH format or per PUCCH resource set.

[00141] Example 19 may include the method of example 1 or some other example herein, wherein within the PUSCH repetition bundle, same transmit power is employed for the transmission of PUSCH repetition.

[00142] Example 20 may include the method of example 1 or some other example herein, wherein whether to apply repetition bundling for Msg3 PLTSCH transmission may be configured by higher layers via remaining minimum system information (RMSI) or other system information (OSI). [00143] Example 21 may include the method of example I or some other example herein, wherein same Tx beam is applied for the transmission of Msg3 PUSCH repetition.

[00144] Example 22 may include the method of example 1 or some other example herein, wherein same Tx beam is applied for the transmission of Msg3 PUSCH within a repetition bundle.

[00145] Example 23 may include the method of example 1 or some other example herein, wherein for Msg3 PUSCH repetition, if a Msg3 PUSCH repetition collides with Div symbols from semi-static UL/DL configuration and SSB transmission at least in one symbol, UE shall drop the Msg3 PUSCH repetition without postponement.

[00146] Example 24 may include the method of example 1 or some other example herein, wherein for a Msg3 PUSCH, a transport, block (TB) can span multiple slots.

[00147] Example 25 may include the method of example 1 or some other example herein, wherein multiple reference signal received power (RSRP) thresholds may be configured by higher layers via RMSI (SIB 1), OSI or RRC signalling; wherein each RSRP thresholds are associated with a certain configured or predefined number of repetitions for Msg3 PUSCH transmission.

[00148] Example 26 may include the method of example 1 or some other example herein, wherein for PUSCH repetition type B, repetition bundling may be configured based on the slot boundary.

[00149] Example 27 may include the method of example 1 or some other example herein, wherein the aforementioned embodiments can also apply for physical downlink control channel (PDCCH) and/or physical downlink shared channel (PDSCH) when repetition is applied for the PDCCH and/or PDSCH, respectively.

[00150] Example 28 may include a method of a UE, the method comprising:

[00151] determining a repetition bundle size for transmission of an uplink signal with repetitions; and [00152] applying a same precoder for transmission of a number of the repetitions that corresponds to the repetition bundle size.

[00153] Example 29 may include the method of example 28 or some other example herein, further comprising receiving an indication of the repetition bundle size via NR remaining minimum system information (RMSI), NR other system information (OSI), dedicated radio resource control (RRC) signalling, and/or downlink control information (DCI).

[00154] Example 30 may include the method of example 28 or some other example herein, wherein the repetition bundle size is predetermined.

[00155] Example 31 may include the method of example 28-30 or some other example herein, wherein the repetition bundle size corresponds to a number of slots, a number of repetitions, a number of transmission occasions, a number of nominal repetiti ons, and/or a number of actual repetitions.

[00156] Example 32 may include the method of example 31 or some other example herein, wherein a repetition bundle associated with the repetition bundle size starts from an earliest repetition of the number of repetitions.

[00157] Example 33 may include the method of example 32 or some other example herein, wherein the earliest repetition is an earliest nominal repetition or an earliest actual repetition.

[00158] Example 34 may include the method of example 28-33 or some other example herein, wherein the repetition bundle size is a first repetition bundle size, and wherein the method further includes receiving configuration information for a set of repetition bundle sizes that includes the first repetition bundle size; and receiving a DCI that includes an indication of the first repetition bundle size to be used from the set of repetition bundle sizes.

[00159] Example 35 may include the method of example 34 or some other example herein, wherein the configuration information is received via RMSI (e.g., SIB1), OSI, and/or RRC signaling.

[00160] Example 36 may include the method of example 28-35 or some other example herein, wherein the repetition bundle size is determined based on a number of repetitions of the uplink signal and/or a number of slots for transmission of the uplink signal. [00161] Example 37 may include the method of example 28-36 or some other example herein, further comprising applying inter-slot frequency hopping for transmission of the repetitions of the uplink signal, wherein applying the inter-slot frequency hopping includes using a first frequency resource for a first set of contiguous repetitions, and using a second frequency resource for a second set of contiguous repetitions after the first set; wherein the Prepetition bundle size corresponds to a size of the first and/or second set of contiguous repetitions. [00162] Example 38 may include the method of example 28-37 or some other example herein, wherein the uplink signal is not scheduled by a PDCCH.

[00163] Example 39 may include the method of example 38 or some other example herein, wherein the uplink signal is scheduled by a configured grant, [00164] Example 40 may include the method of example 28-39 or some other example herein, wherein the uplink signal is a PUSCH.

[00165] Example 41 may include the method of example 40 or some other example herein, wherein the PUSCH is included in a Msg3 of a random-access procedure.

[00166] Example 42 may include the method of example 41 or some other example herein, wherein the repetition bundle size is indicated by a field in a RAR LIE grant, a fallbackRAR UL grant, and/or a DCI format 0_0 with CRC scrambled by a TC-RNTI.

[00167] Example 43 may include the method of example 28-39 or some other example herein, wherein the uplink signal is a PUCCH.

[00168] Example 44 may include the method of example 43 or some other example herein, wherein the repetition bundle size is configured per PUCCH resource, per PUCCH format, or per PUCCH resource set,

[00169] Example 45 may include the method of example 28-44 or some other example herein, further comprising applying a same transmit power for the repetitions of the uplink signal within the repetition bundle.

[00170] Example 46 may include the method of example 28-45 or some other example herein, further comprising receiving an indication of whether to apply repetition bundling for Msg3 PUSCH transmission. [00171] Example 47 may include the method of example 46 or some other example herein, wherein the indication is received via remaining minimum system information (RMSI) and/or other system information (OSI).

[00172] Example 48 may include the method of example 28-47 or some other example herein, wherein the uplink signal is a Msg3 PUSCH.

[00173] Example 49 may include the method of example 48 or some other example herein, wherein a same Tx beam is applied for the transmission of the Msg3 PUSCH repetitions.

[00174] Example 50 may include the method of example 48 or some other example herein, wherein a same Tx beam is applied for the transmission of Msg3 PUSCH within the repetition bundle and different Tx beams are applied for different repetition bundles.

[00175] Example 51 may include the method of example 48-50 or some other example herein, further comprising: determining that a Msg3 PUSCH repetition collides with DL symbols from a semi-static UL/DL configuration and/or SSB transmission in at least in one symbol; and dropping the Msg3 PUSCH repetition based on the determination.

[00176] Example 51 may include the method of example 48-50 or some other example herein, wherein a transport block (TB) of the Msg3 PUSCH repetition spans multiple slots.

[00177] Example 52 may include a method of a gNB, the method comprising:

[00178] determining a repetition bundle size for transmission of a downlink signal with repetitions, and

[00179] applying a same precoder for transmi ssion of a number of the repetitions that corresponds to the repetition bundle size.

[00180] Example 53 may include the method of example 52 or some other example herein, further comprising encoding, for transmission to a UE, an indication of the repetition bundle size via NR remaining minimum system information (RMSI), NR other system information (OSI), dedicated radio resource control (RRC) signalling, and/or downlink control information (DO). [00181] Example 54 may include the method of example 52-53 or some other example herein, wherein the repetition bundle size is a first repetition bundle size, and wherein the method further includes encoding, for transmission to a UE, configuration information for a set of repetition bundle sizes that includes the first repetition bundle size; and encoding, for transmission to the UE, a DCI that includes an indication of the first repetition bundle size to be used from the set of repetition bundle sizes.

[00182] Example 55 may include the method of example 52-54 or some other example herein, wherein the downlink signal is a PDCCH. [00183] Example 56 may include the method of example 52-54 or some other example herein, wherein the downlink signal is a PDSCH.

[00184] The Abstract is provided to comply with 37 C.F.R. Section

1.72(b) requiring an abstract that will allow ⁷ the reader to ascertain the nature and gist of the technical disclosure. It is submitted with the understanding that it wall not be used to limit or interpret the scope or meaning of the claims. The following claims are hereby incorporated into the detailed description, with each claim standing on its own as a separate embodiment.