EP4666467A1

EP4666467A1 - Enhancements for aggregated uplink transmissions in wireless communication systems

Info

Publication number: EP4666467A1
Application number: EP24723253.1A
Authority: EP
Inventors: Tarakkumar G. Dhanani; Haitong Sun; Sharad Garg; Vijay Gadde; Karan R. Sachdev; Rohit Thareja; Sanjeevi Balasubramanian; Vijay Venkataraman; Wei Zhang; Wei Zeng
Original assignee: Apple Inc
Current assignee: Apple Inc
Priority date: 2023-04-07
Filing date: 2024-03-29
Publication date: 2025-12-24
Also published as: CN121058183A; WO2024211197A1

Abstract

A user equipment (UE) may establish a cellular link with a network and receive a UE capability request from the network. The UE may transmit a UE capability response to the network. The UE capability response may include an indication that the UE supports slot aggregation and the UE may receive, from the network, a radio resource control (RRC) connection reconfiguration message indicating a maximum value for slot aggregation. The UE may determine, based on one or more calculations, a preferred slot aggregation level (SAL) and transmit, to the network, a message indicating the preferred SAL. The UE may receive, from the network, downlink control information (DCI) including configuration information associated with a different SAL and accordingly transmit, in accordance with the different SAL, uplink (UE) signaling to the network.

Description

ENHANCEMENTS FOR AGGREGATED UPLINK TRANSMISSIONS IN WIRELESS COMMUNICATION SYSTEMS

FIELD

[0001] The present application relates to wireless devices, and more particularly to apparatus, systems, and methods for enhanced aggregated uplink transmission in a wireless communication system.

DESCRIPTION OF THE RELATED ART

[0002] Wireless communication systems are rapidly growing in usage. In recent years, wireless devices such as smart phones and tablet computers have become increasingly sophisticated. In addition to supporting telephone calls, many mobile devices now provide access to the internet, email, text messaging, and navigation using the global positioning system (GPS), and are capable of operating sophisticated applications that utilize these functionalities. Additionally, there exist numerous different wireless communication technologies and standards. Some examples of wireless communication standards include UMTS (associated with, for example, WCDMA or TD-SCDMA air interfaces), LTE, LTE Advanced (LTE-A), HSPA, IEEE 802.11 (WLAN or Wi-Fi), BLUETOOTH™, etc.

[0003] The ever increasing number of features and functionality introduced in wireless communication devices also creates a continuous need for improvement in both wireless communications and in wireless communication devices. In particular, it is important to ensure the accuracy of transmitted and received signals through wireless devices used in wireless cellular communications. In addition, increasing the functionality of a UE device can place a significant strain on the battery life of the UE device. Thus it is very important to also reduce power requirements in UE device designs while allowing the UE device to maintain good transmit and receive abilities for improved communications. Accordingly, improvements in the field are desired. SUMMARY

[0004] Embodiments relate to apparatuses, systems, and methods for enhanced aggregated uplink transmission in a wireless communication.

[0005] According to some embodiments, a user equipment (UE) may establish a cellular link with a network and receive a UE capability request from the network. The UE may transmit a UE capability response to the network. The UE capability response may include an indication that the UE supports slot aggregation and the UE may receive, from the network, a radio resource control (RRC) connection reconfiguration message indicating a maximum value for slot aggregation. The UE may determine, based on one or more calculations, a preferred slot aggregation level (SAL) and transmit, to the network, a message indicating the preferred SAL. The UE may receive, from the network, downlink control information (DCI) including configuration information associated with a different SAL and accordingly transmit, in accordance with the different SAL, uplink (UL) signaling to the network.

[0006] In some embodiments, the one or more calculations may include calculating a parameter Z. Additionally, the determination of the preferred SAL may be further based on a comparison of the parameter Z to one or more values including values specified by a manufacturer of the UE. The parameter Z may be calculated using the formula Z = x dB - duty cycle gain dB - y dB, where x may be a specific absorption rate (SAR) limit subtracted from a regulatory transmission (Tx) limit, the duty cycle gain may be an SAR budget associated with a duration when transmission is disabled, and the parameter y may be an additional buffer or offset for an additional duty cycle prediction.

[0007] According to some scenarios, the UE may determine a preferred SAL by utilizing calculated parameter Z in one or more equations and/or inequalities and the values “a” and “b” specified by the UE manufacturer. As a first option, the preferred SAL may be determined according to the equation and inequality the preferred SAL = min [8, maximum allowed by network], if Z < 0. As a second option, the preferred SAL may be determined according to the equation and inequality the preferred SAL = min [4, maximum allowed by network], if 0 < Z < a. As a third option, the preferred SAL may be determined according to the equation and inequality the preferred SAL = min [2, maximum allowed by network], if a < Z < b. As a fourth option, the preferred SAL may be determined by the equation and inequality the preferred SAL = 1, if b < Z. [0008] In some instances, expiry of a timer or occurrence of one or more events may trigger the UE to determine a new SAL. Additionally, the one or more events may include at least one of an occurrence of a handover, an airplane mode being enabled or disabled, a change of a transmission (Tx) Port, a change of in the UE’s RRC state; the UE being turned on or powered up; a change in the UE’s specific absorption rate (SAR) scenario, a change in at least one of an UL or downlink (DL) slot configuration, a change in a subcarrier spacing (SCS), activation, deactivation, deconfiguration of an UL carrier aggregation (CA) configuration, or a change related to connection properties of an application running on the UE.

[0009] According to some embodiments, the UE may detect an increasing UL duty cycle and decrease, in response to detecting the increasing UL duty cycle, the optimal SAL. Additionally or alternatively, the UE may detect a decreasing UL duty cycle and increase, in response to detecting the decreasing UL duty cycle, the preferred SAL. In some embodiments, a default SAL may be a value of one.

[0010] According to some embodiments, a network node may establish a cellular link with a user equipment (UE) and transmit, to the UE, a UE capability request. The BS may receive, from the UE, a UE capability response including an indication that the UE supports slots aggregation via transmission timing interval (TTI) bundling. The network node may transmit, to the UE, a radio resource control (RRC) connection reconfiguration message indicating a maximum value for slot aggregation. The network node may receive, from the UE, a message indicating a slot aggregation level (SAL) and transmit, to the UE, downlink control information (DCI) indicating at least one of an updated or a different SAL.

[0011] In some embodiments, the DCI may include configuration information useable by the UE in transmitting, according to the at least one of the updated or the different SAL, uplink (UL) signaling to the network node. Additionally or alternatively, the network node may refrain from transmitting the RRC connection reconfiguration message as part of an indication for the UE to use a default SAL value. In some embodiments, the UE capability response may indicate for the network node to disable TTI bundling via a feature group indicator (FGI).

[0012] According to some embodiments, a method may include receiving, from a base station (BS), a user equipment (UE) capability request including an indication requesting support for transmission timing interval (TTI) bundling. The method may further include, transmitting a UE capability response to the BS. The UE capability response may include a feature group indicator (FGI) indicating support for TTI bundling, according to some embodiments. The method may additionally include determining, based on one or more calculations, to enable or disable TTI bundling and transmitting, to the BS and based at least in part on the determination to enable or disable TTI bundling, a request message indicating for the BS to enable or disable TTI bundling. Additionally, the method may include receiving, from the BS, downlink control information (DCI) including configuration information to enable or disable TTI bundling. In some embodiments, the method may include transmitting, prior to receiving the UE capability request, signaling comprising a tracking area update (TAU) to the BS.

[0013] The techniques described herein may be implemented in and/or used with a number of different types of devices, including but not limited to cellular phones, tablet computers, wearable computing devices, portable media players, and any of various other computing devices.

[0014] This Summary is intended to provide a brief overview of some of the subject matter described in this document. Accordingly, it will be appreciated that the above-described features are merely examples and should not be construed to narrow the scope or spirit of the subject matter described herein in any way. Other features, aspects, and advantages of the subject matter described herein will become apparent from the following Detailed Description, Figures, and Claims.

BRIEF DESCRIPTION OF THE DRAWINGS

[0015] A better understanding of the present subject matter can be obtained when the following detailed description of various embodiments is considered in conjunction with the following drawings, in which:

[0016] Figure 1 illustrates an example wireless communication system, according to some embodiments;

[0017] Figure 2 illustrates a base station (BS) in communication with a user equipment (UE) device, according to some embodiments;

[0018] Figure 3 illustrates an example block diagram of a UE, according to some embodiments;

[0019] Figure 4 illustrates an example block diagram of a BS, according to some embodiments;

[0020] Figure 5 illustrates an example block diagram of cellular communication circuitry, according to some embodiments; [0021] Figure 6A illustrates an example of connections between an EPC network, an LTE base station (eNB), and a 5G NR base station (gNB), according to some embodiments;

[0022] Figure 6B illustrates an example of a protocol stack for an eNB and a gNB, according to some embodiments;

[0023] Figures 7A-B illustrate example aspects of transmission timing interval (TTI) bundling with and without the utilization of time averaging, according to some embodiments;

[0024] Figure 8 illustrates example performance plots comparing the use versus non-use of TTI bundling, according to some embodiments;

[0025] Figure 9 is a flowchart diagram illustrating an example method of enhanced aggregated uplink transmission in a wireless communication system, according to some embodiments;

[0026] Figure 10 is a flowchart diagram illustrating an example method for determining an optimal slot aggregation level (SAL), according to some embodiments; and

[0027] Figures 11 and 12 are communication flow diagrams of wireless communication systems performing example aspects of enhanced TTI bundling enabling/disabling, according to some embodiments.

[0028] While the features described herein may be susceptible to various modifications and alternative forms, specific embodiments thereof are shown by way of example in the drawings and are herein described in detail. It should be understood, however, that the drawings and detailed description thereto are not intended to be limiting to the particular form disclosed, but on the contrary, the intention is to cover all modifications, equivalents and alternatives falling within the spirit and scope of the subject matter as defined by the appended claims.

DETAILED DESCRIPTION

Acronyms

[0029] Various acronyms are used throughout the present disclosure. Definitions of the most prominently used acronyms that may appear throughout the present disclosure are provided below:

• 3GPP: Third Generation Partnership Project

• TS: Technical Specification

• RAN : Radio Access Network

• RAT: Radio Access Technology • UE: User Equipment

• RE: Radio Frequency

• BS: Base Station

• DL: Downlink

• UL: Uplink

• Tx: Transmit/Transmission

• Rx: Receive/Reception

• LTE: Long Term Evolution

• NR: New Radio

• E-UTRA: Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access

• 5GS: 5G System

• 5GMM: 5GS Mobility Management

• 5GC: 5G Core Network

• IE: Information Element

• RRC: Radio Resource Control

• V oNR: Voi ce over New Radi o

• VoLTE: Voice over Long Term Evolution

• TTI: Transmission Time Interval

• SAR: Specific Absorption Rate

• BLER: Block Error Rate

• MOS: Mean Opinion Score

• MTPL: Maximum Transmit Power Level

• TDD: Time Division Duplex

• FDD: Frequency Division Duplex

• UCI: Uplink Control Information

• DCI: Downlink Control Information

• UL-CA: Uplink Carrier Aggregation

• URLLC: Ultra-reliable Low Latency Connection

• SAL: Slot Aggregation Level

• CB: Call Barring • FGI: Feature Group Indicator

• TRP: Transmission and Reception Point

• MAC-CE: Media Access Control - Control Element

• CSI-RS: Channel State Information - Reference Signal

• RLC: Radio Link Control

• SSB: Synchronization Signal Block

• CSI: Channel State Information

• CQI: Channel Quality Indicator

• PMI: Precoding Matrix Indicator

• RI: Rank Indicator

• CMR: Channel Measurement Resource

• IMR: Interference Measurement Resource

• MIMO: Multiple Input Multiple Output

• SP: Semi-persistent

• AP: Aperiodic

Terms

[0030] The following is a glossary of terms used in this disclosure:

[0031] Memory Medium - Any of various types of non-transitory memory devices or storage devices. The term “memory medium” is intended to include an installation medium, e.g., a CD-ROM, floppy disks, or tape device; a computer system memory or random access memory such as DRAM, DDR RAM, SRAM, EDO RAM, Rambus RAM, etc.; a non-volatile memory such as a Flash, magnetic media, e.g., a hard drive, or optical storage; registers, or other similar types of memory elements, etc. The memory medium may include other types of non-transitory memory as well or combinations thereof. In addition, the memory medium may be located in a first computer system in which the programs are executed, or may be located in a second different computer system which connects to the first computer system over a network, such as the Internet. In the latter instance, the second computer system may provide program instructions to the first computer for execution. The term “memory medium” may include two or more memory mediums which may reside in different locations, e.g., in different computer systems that are connected over a network. The memory medium may store program instructions (e.g., embodied as computer programs) that may be executed by one or more processors.

[0032] Carrier Medium - a memory medium as described above, as well as a physical transmission medium, such as a bus, network, and/or other physical transmission medium that conveys signals such as electrical, electromagnetic, or digital signals.

[0033] Programmable Hardware Element - includes various hardware devices comprising multiple programmable function blocks connected via a programmable interconnect. Examples include FPGAs (Field Programmable Gate Arrays), PLDs (Programmable Logic Devices), FPOAs (Field Programmable Object Arrays), and CPLDs (Complex PLDs). The programmable function blocks may range from fine grained (combinatorial logic or look up tables) to coarse grained (arithmetic logic units or processor cores). A programmable hardware element may also be referred to as "reconfigurable logic”.

[0034] Computer System - any of various types of computing or processing systems, including a personal computer system (PC), mainframe computer system, workstation, network appliance, Internet appliance, personal digital assistant (PDA), television system, grid computing system, or other device or combinations of devices. In general, the term "computer system" can be broadly defined to encompass any device (or combination of devices) having at least one processor that executes instructions from a memory medium.

[0035] User Equipment (UE) (or “UE Device”) - any of various types of computer systems devices which are mobile or portable and which performs wireless communications. Examples of UE devices include mobile telephones or smart phones (e.g., iPhone™, Android™-based phones), portable gaming devices (e.g., Nintendo DS™, PlayStation Portable™, Gameboy Advance™, iPhone™), laptops, wearable devices (e.g. smart watch, smart glasses), PDAs, portable Internet devices, music players, data storage devices, or other handheld devices, etc. In general, the term “UE” or “UE device” can be broadly defined to encompass any electronic, computing, and/or telecommunications device (or combination of devices) which is easily transported by a user and capable of wireless communication.

[0036] Base Station - The term "Base Station" has the full breadth of its ordinary meaning, and at least includes a wireless communication station installed at a fixed location and used to communicate as part of a wireless telephone system or radio system.

[0037] Processing Element - refers to various elements or combinations of elements that are capable of performing a function in a device, such as a user equipment or a cellular network device. Processing elements may include, for example: processors and associated memory, portions or circuits of individual processor cores, entire processor cores, processor arrays, circuits such as an ASIC (Application Specific Integrated Circuit), programmable hardware elements such as a field programmable gate array (FPGA), as well any of various combinations of the above.

[0038] Channel - a medium used to convey information from a sender (transmitter) to a receiver. It should be noted that since characteristics of the term “channel” may differ according to different wireless protocols, the term “channel” as used herein may be considered as being used in a manner that is consistent with the standard of the type of device with reference to which the term is used. In some standards, channel widths may be variable (e.g., depending on device capability, band conditions, etc.). For example, LTE may support scalable channel bandwidths from 1.4 MHz to 20MHz. In contrast, WLAN channels may be 22MHz wide while Bluetooth channels may be IMhz wide. Other protocols and standards may include different definitions of channels. Furthermore, some standards may define and use multiple types of channels, e.g., different channels for uplink or downlink and/or different channels for different uses such as data, control information, etc.

[0039] Band - The term "band" has the full breadth of its ordinary meaning, and at least includes a section of spectrum (e.g., radio frequency spectrum) in which channels are used or set aside for the same purpose.

[0040] Automatically - refers to an action or operation performed by a computer system (e.g., software executed by the computer system) or device (e.g., circuitry, programmable hardware elements, ASICs, etc.), without user input directly specifying or performing the action or operation. Thus the term "automatically" is in contrast to an operation being manually performed or specified by the user, where the user provides input to directly perform the operation. An automatic procedure may be initiated by input provided by the user, but the subsequent actions that are performed “automatically” are not specified by the user, i.e., are not performed “manually”, where the user specifies each action to perform. For example, a user filling out an electronic form by selecting each field and providing input specifying information (e.g., by typing information, selecting check boxes, radio selections, etc.) is filling out the form manually, even though the computer system must update the form in response to the user actions. The form may be automatically filled out by the computer system where the computer system (e.g., software executing on the computer system) analyzes the fields of the form and fills in the form without any user input specifying the answers to the fields. As indicated above, the user may invoke the automatic filling of the form, but is not involved in the actual filling of the form (e.g., the user is not manually specifying answers to fields but rather they are being automatically completed). The present specification provides various examples of operations being automatically performed in response to actions the user has taken. [0041] Approximately - refers to a value that is almost correct or exact. For example, approximately may refer to a value that is within 1 to 10 percent of the exact (or desired) value. It should be noted, however, that the actual threshold value (or tolerance) may be application dependent. For example, in some embodiments, “approximately” may mean within 0.1% of some specified or desired value, while in various other embodiments, the threshold may be, for example, 2%, 3%, 5%, and so forth, as desired or as required by the particular application.

[0042] Concurrent - refers to parallel execution or performance, where tasks, processes, or programs are performed in an at least partially overlapping manner. For example, concurrency may be implemented using “strong” or strict parallelism, where tasks are performed (at least partially) in parallel on respective computational elements, or using “weak parallelism”, where the tasks are performed in an interleaved manner, e.g., by time multiplexing of execution threads.

[0043] Various components may be described as “configured to” perform a task or tasks. In such contexts, “configured to” is a broad recitation generally meaning “having structure that” performs the task or tasks during operation. As such, the component can be configured to perform the task even when the component is not currently performing that task (e.g., a set of electrical conductors may be configured to electrically connect a module to another module, even when the two modules are not connected). In some contexts, “configured to” may be a broad recitation of structure generally meaning “having circuitry that” performs the task or tasks during operation. As such, the component can be configured to perform the task even when the component is not currently on. In general, the circuitry that forms the structure corresponding to “configured to” may include hardware circuits.

[0044] Various components may be described as performing a task or tasks, for convenience in the description. Such descriptions should be interpreted as including the phrase “configured to.” Reciting a component that is configured to perform one or more tasks is expressly intended not to invoke 35 U.S.C. § 112(f) interpretation for that component.

Figures 1 and 2 - Communication System [0045] Figure 1 illustrates a simplified example wireless communication system, according to some embodiments. It is noted that the system of Figure 1 is merely one example of a possible system, and that features of this disclosure may be implemented in any of various systems, as desired.

[0046] As shown, the example wireless communication system includes a base station 102 A which communicates over a transmission medium with one or more user devices 106A, 106B, etc., through 106N. Each of the user devices may be referred to herein as a “user equipment” (UE). Thus, the user devices 106 are referred to as UEs or UE devices.

[0047] The base station (BS) 102 A may be a base transceiver station (BTS) or cell site (a “cellular base station”), and may include hardware that enables wireless communication with the UEs 106 A through 106N.

[0048] The communication area (or coverage area) of the base station may be referred to as a “cell.” The base station 102A and the UEs 106 may be configured to communicate over the transmission medium using any of various radio access technologies (RATs), also referred to as wireless communication technologies, or telecommunication standards, such as UMTS (associated with, for example, WCDMA or TD-SCDMA air interfaces), LTE, LTE-Advanced (LTE-A), 5G new radio (5GNR), HSPA, etc. Note that if the base station 102A is implemented in the context of LTE, it may alternately be referred to as an 'eNodeB' or ‘eNB’. Note that if the base station 102A is implemented in the context of 5G NR, it may alternately be referred to as ‘gNodeB’ or ‘gNB’.

[0049] As shown, the base station 102 A may also be equipped to communicate with a network 100 (e.g., a core network of a cellular service provider, a telecommunication network such as a public switched telephone network (PSTN), and/or the Internet, among various possibilities). Thus, the base station 102A may facilitate communication between the user devices and/or between the user devices and the network 100. In particular, the cellular base station 102 A may provide UEs 106 with various telecommunication capabilities, such as voice, SMS and/or data services.

[0050] Base station 102 A and other similar base stations (such as base stations 102B ... 102N) operating according to the same or a different cellular communication standard may thus be provided as a network of cells, which may provide continuous or nearly continuous overlapping service to UEs 106A-N and similar devices over a geographic area via one or more cellular communication standards. [0051] Thus, while base station 102A may act as a “serving cell” for UEs 106A-N as illustrated in Figure 1, each UE 106 may also be capable of receiving signals from (and possibly within communication range of) one or more other cells (which might be provided by base stations 102B-N and/or any other base stations), which may be referred to as “neighboring cells”. Such cells may also be capable of facilitating communication between user devices and/or between user devices and the network 100. Such cells may include “macro” cells, “micro” cells, “pico” cells, and/or cells which provide any of various other granularities of service area size. For example, base stations 102A-B illustrated in Figure 1 might be macro cells, while base station 102N might be a micro cell. Other configurations are also possible.

[0052] In some embodiments, base station 102A may be a next generation base station, e.g., a 5G New Radio (5G NR) base station, or “gNB”. In some embodiments, a gNB may be connected to a legacy evolved packet core (EPC) network and/or to a NR core (NRC) network. In addition, a gNB cell may include one or more transition and reception points (TRPs). In addition, a UE capable of operating according to 5G NR may be connected to one or more TRPs within one or more gNBs.

[0053] Note that a UE 106 may be capable of communicating using multiple wireless communication standards. For example, the UE 106 may be configured to communicate using a wireless networking (e.g., Wi-Fi) and/or peer-to-peer wireless communication protocol (e.g., Bluetooth, Wi-Fi peer-to-peer, etc.) in addition to at least one cellular communication protocol (e.g., UMTS (associated with, for example, WCDMA or TD-SCDMA air interfaces), LTE, LTE-A, 5G NR, HSPA, etc.). The UE 106 may also or alternatively be configured to communicate using one or more global navigational satellite systems (GNSS, e.g., GPS or GLONASS), one or more mobile television broadcasting standards (e.g., ATSC-M/H or DVB- 11), and/or any other wireless communication protocol, if desired. Other combinations of wireless communication standards (including more than two wireless communication standards) are also possible.

[0054] Figure 2 illustrates user equipment 106 (e.g., one of the devices 106A through 106N) in communication with a base station 102, according to some embodiments. The UE 106 may be a device with cellular communication capability such as a mobile phone, a hand-held device, a computer or a tablet, or virtually any type of wireless device.

[0055] The UE 106 may include a processor that is configured to execute program instructions stored in memory. The UE 106 may perform any of the method embodiments described herein by executing such stored instructions. Alternatively, or in addition, the UE 106 may include a programmable hardware element such as an FPGA (field-programmable gate array) that is configured to perform any of the method embodiments described herein, or any portion of any of the method embodiments described herein.

[0056] The UE 106 may include one or more antennas for communicating using one or more wireless communication protocols or technologies. In some embodiments, the UE 106 may be configured to communicate using, for example, LTE using a single shared radio. The shared radio may couple to a single antenna, or may couple to multiple antennas (e.g., for MIMO) for performing wireless communications. In general, a radio may include any combination of a baseband processor, analog RF signal processing circuitry (e.g., including filters, mixers, oscillators, amplifiers, etc.), or digital processing circuitry (e.g., for digital modulation as well as other digital processing). Similarly, the radio may implement one or more receive and transmit chains using the aforementioned hardware. For example, the UE 106 may share one or more parts of a receive and/or transmit chain between multiple wireless communication technologies, such as those discussed above.

[0057] In some embodiments, the UE 106 may include separate transmit and/or receive chains (e.g., including separate antennas and other radio components) for each wireless communication protocol with which it is configured to communicate. As a further possibility, the UE 106 may include one or more radios which are shared between multiple wireless communication protocols, and one or more radios which are used exclusively by a single wireless communication protocol. For example, the UE 106 might include a shared radio for communicating using either of LTE or 5G NR (or LTE or IxRTT), and separate radios for communicating using each of Wi-Fi and Bluetooth. Other configurations are also possible.

Figure 3 - Block Diagram of a UE

[0058] Figure 3 illustrates an example simplified block diagram of a communication device 106, according to some embodiments. It is noted that the block diagram of the communication device of Figure 3 is only one example of a possible communication device. According to embodiments, communication device 106 may be a user equipment (UE) device, a mobile device or mobile station, a wireless device or wireless station, a desktop computer or computing device, a mobile computing device (e.g., a laptop, notebook, or portable computing device), a tablet and/or a combination of devices, among other devices. As shown, the communication device 106 may include a set of components 300 configured to perform core functions. For example, this set of components may be implemented as a system on chip (SOC), which may include portions for various purposes. Alternatively, this set of components 300 may be implemented as separate components or groups of components for the various purposes. The set of components 300 may be coupled (e.g., communicatively; directly or indirectly) to various other circuits of the communication device 106.

[0059] For example, the communication device 106 may include various types of memory (e.g., including NAND flash 310), an input/output interface such as connector I/F 320 (e.g., for connecting to a computer system; dock; charging station; input devices, such as a microphone, camera, keyboard; output devices, such as speakers; etc.), the display 360, which may be integrated with or external to the communication device 106, and cellular communication circuitry 330 such as for 5GNR, LTE, etc., and short to medium range wireless communication circuitry 329 (e.g., Bluetooth™ and WLAN circuitry). In some embodiments, communication device 106 may include wired communication circuitry (not shown), such as a network interface card, e.g., for Ethernet.

[0060] The cellular communication circuitry 330 may couple (e.g., communicatively; directly or indirectly) to one or more antennas, such as antennas 335 and 336 as shown. The short to medium range wireless communication circuitry 329 may also couple (e.g., communicatively; directly or indirectly) to one or more antennas, such as antennas 337 and 338 as shown. Alternatively, the short to medium range wireless communication circuitry 329 may couple (e.g., communicatively; directly or indirectly) to the antennas 335 and 336 in addition to, or instead of, coupling (e.g., communicatively; directly or indirectly) to the antennas 337 and 338. The short to medium range wireless communication circuitry 329 and/or cellular communication circuitry 330 may include multiple receive chains and/or multiple transmit chains for receiving and/or transmitting multiple spatial streams, such as in a multiple-input multiple output (MIMO) configuration.

[0061] In some embodiments, as further described below, cellular communication circuitry 330 may include dedicated receive chains (including and/or coupled to, e.g., communicatively; directly or indirectly, dedicated processors and/or radios) for multiple RATs (e.g., a first receive chain for LTE and a second receive chain for 5G NR). In addition, in some embodiments, cellular communication circuitry 330 may include a single transmit chain that may be switched between radios dedicated to specific RATs. For example, a first radio may be dedicated to a first RAT, e.g., LTE, and may be in communication with a dedicated receive chain and a transmit chain shared with an additional radio, e.g., a second radio that may be dedicated to a second RAT, e.g., 5G NR, and may be in communication with a dedicated receive chain and the shared transmit chain.

[0062] The communication device 106 may also include and/or be configured for use with one or more user interface elements. The user interface elements may include any of various elements, such as display 360 (which may be a touchscreen display), a keyboard (which may be a discrete keyboard or may be implemented as part of a touchscreen display), a mouse, a microphone and/or speakers, one or more cameras, one or more buttons, and/or any of various other elements capable of providing information to a user and/or receiving or interpreting user input.

[0063] The communication device 106 may further include one or more smart cards 345 that include SIM (Subscriber Identity Module) functionality, such as one or more UICC(s) (Universal Integrated Circuit Card(s)) cards 345.

[0064] As shown, the SOC 300 may include processor(s) 302, which may execute program instructions for the communication device 106 and display circuitry 304, which may perform graphics processing and provide display signals to the display 360. The processor(s) 302 may also be coupled to memory management unit (MMU) 340, which may be configured to receive addresses from the processor(s) 302 and translate those addresses to locations in memory (e.g., memory 306, read only memory (ROM) 350, NAND flash memory 310) and/or to other circuits or devices, such as the display circuitry 304, short range wireless communication circuitry 229, cellular communication circuitry 330, connector I/F 320, and/or display 360. The MMU 340 may be configured to perform memory protection and page table translation or set up. In some embodiments, the MMU 340 may be included as a portion of the processor(s) 302.

[0065] As noted above, the communication device 106 may be configured to communicate using wireless and/or wired communication circuitry. The communication device 106 may be configured to transmit a request to attach to a first network node operating according to the first RAT and transmit an indication that the wireless device is capable of maintaining substantially concurrent connections with the first network node and a second network node that operates according to the second RAT. The wireless device may also be configured transmit a request to attach to the second network node. The request may include an indication that the wireless device is capable of maintaining substantially concurrent connections with the first and second network nodes. Further, the wireless device may be configured to receive an indication that dual connectivity with the first and second network nodes has been established. [0066] As described herein, the communication device 106 may include hardware and software components for implementing the above features for time division multiplexing UL data for NSA NR operations. The processor 302 of the communication device 106 may be configured to implement part or all of the features described herein, e.g., by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium). Alternatively (or in addition), processor 302 may be configured as a programmable hardware element, such as an FPGA (Field Programmable Gate Array), or as an ASIC (Application Specific Integrated Circuit). Alternatively (or in addition) the processor 302 of the communication device 106, in conjunction with one or more of the other components 300, 304, 306, 310, 320, 329, 330, 340, 345, 350, 360 may be configured to implement part or all of the features described herein.

[0067] In addition, as described herein, processor 302 may include one or more processing elements. Thus, processor 302 may include one or more integrated circuits (ICs) that are configured to perform the functions of processor 302. In addition, each integrated circuit may include circuitry (e.g., first circuitry, second circuitry, etc.) configured to perform the functions of processor(s) 302.

[0068] Further, as described herein, cellular communication circuitry 330 and short range wireless communication circuitry 329 may each include one or more processing elements. In other words, one or more processing elements may be included in cellular communication circuitry 330 and, similarly, one or more processing elements may be included in short range wireless communication circuitry 329. Thus, cellular communication circuitry 330 may include one or more integrated circuits (ICs) that are configured to perform the functions of cellular communication circuitry 330. In addition, each integrated circuit may include circuitry (e.g., first circuitry, second circuitry, etc.) configured to perform the functions of cellular communication circuitry 230. Similarly, the short range wireless communication circuitry 329 may include one or more ICs that are configured to perform the functions of short range wireless communication circuitry 32. In addition, each integrated circuit may include circuitry (e.g., first circuitry, second circuitry, etc.) configured to perform the functions of short range wireless communication circuitry 329.

Figure 4 - Block Diagram of a Base Station

[0069] Figure 4 illustrates an example block diagram of a base station 102, according to some embodiments. It is noted that the base station of Figure 4 is merely one example of a possible base station. As shown, the base station 102 may include processor(s) 404 which may execute program instructions for the base station 102. The processor(s) 404 may also be coupled to memory management unit (MMU) 440, which may be configured to receive addresses from the processor(s) 404 and translate those addresses to locations in memory (e.g., memory 460 and read only memory (ROM) 450) or to other circuits or devices.

[0070] The base station 102 may include at least one network port 470. The network port 470 may be configured to couple to a telephone network and provide a plurality of devices, such as UE devices 106, access to the telephone network as described above in Figures 1 and 2.

[0071] The network port 470 (or an additional network port) may also or alternatively be configured to couple to a cellular network, e.g., a core network of a cellular service provider. The core network may provide mobility related services and/or other services to a plurality of devices, such as UE devices 106. In some cases, the network port 470 may couple to a telephone network via the core network, and/or the core network may provide a telephone network (e.g., among other UE devices serviced by the cellular service provider).

[0072] In some embodiments, base station 102 may be a next generation base station, e.g., a 5G New Radio (5G NR) base station, or “gNB”. In such embodiments, base station 102 may be connected to a legacy evolved packet core (EPC) network and/or to a NR core (NRC) network. In addition, base station 102 may be considered a 5G NR cell and may include one or more transmission and reception points (TRPs). In addition, a UE capable of operating according to 5GNR may be connected to one or more TRPs within one or more gNBs.

[0073] The base station 102 may include at least one antenna 434, and possibly multiple antennas. The at least one antenna 434 may be configured to operate as a wireless transceiver and may be further configured to communicate with UE devices 106 via radio 430. The antenna 434 communicates with the radio 430 via communication chain 432. Communication chain 432 may be a receive chain, a transmit chain or both. The radio 430 may be configured to communicate via various wireless communication standards, including, but not limited to, 5G NR, LTE, LTE-A, UMTS, Wi-Fi, etc.

[0074] The base station 102 may be configured to communicate wirelessly using multiple wireless communication standards. In some instances, the base station 102 may include multiple radios, which may enable the base station 102 to communicate according to multiple wireless communication technologies. For example, as one possibility, the base station 102 may include an LTE radio for performing communication according to LTE as well as a 5G NR radio for performing communication according to 5GNR. In such a case, the base station 102 may be capable of operating as both an LTE base station and a 5G NR base station. As another possibility, the base station 102 may include a multi-mode radio which is capable of performing communications according to any of multiple wireless communication technologies (e.g., 5G NR and Wi-Fi, LTE and Wi-Fi, LTE and UMTS, etc.).

[0075] As described further subsequently herein, the BS 102 may include hardware and software components for implementing or supporting implementation of features described herein. The processor 404 of the base station 102 may be configured to implement or support implementation of part or all of the methods described herein, e.g., by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium). Alternatively, the processor 404 may be configured as a programmable hardware element, such as an FPGA (Field Programmable Gate Array), or as an ASIC (Application Specific Integrated Circuit), or a combination thereof. Alternatively (or in addition) the processor 404 of the BS 102, in conjunction with one or more of the other components 430, 432, 434, 440, 450, 460, 470 may be configured to implement or support implementation of part or all of the features described herein.

[0076] In addition, as described herein, processor(s) 404 may be comprised of one or more processing elements. In other words, one or more processing elements may be included in processor(s) 404. Thus, processor(s) 404 may include one or more integrated circuits (ICs) that are configured to perform the functions of processor(s) 404. In addition, each integrated circuit may include circuitry (e.g., first circuitry, second circuitry, etc.) configured to perform the functions of processor(s) 404.

[0077] Further, as described herein, radio 430 may be comprised of one or more processing elements. In other words, one or more processing elements may be included in radio 430. Thus, radio 430 may include one or more integrated circuits (ICs) that are configured to perform the functions of radio 430. In addition, each integrated circuit may include circuitry (e.g., first circuitry, second circuitry, etc.) configured to perform the functions of radio 430.

Figure 5: Block Diagram of Cellular Communication Circuitry

[0078] Figure 5 illustrates an example simplified block diagram of cellular communication circuitry, according to some embodiments. It is noted that the block diagram of the cellular communication circuitry of Figure 5 is only one example of a possible cellular communication circuit. According to embodiments, cellular communication circuitry 330 may be include in a communication device, such as communication device 106 described above. As noted above, communication device 106 may be a user equipment (UE) device, a mobile device or mobile station, a wireless device or wireless station, a desktop computer or computing device, a mobile computing device (e.g., a laptop, notebook, or portable computing device), a tablet and/or a combination of devices, among other devices.

[0079] The cellular communication circuitry 330 may couple (e.g., communicatively; directly or indirectly) to one or more antennas, such as antennas 335a-b and 336 as shown (in Figure 3). In some embodiments, cellular communication circuitry 330 may include dedicated receive chains (including and/or coupled to, e.g., communicatively; directly or indirectly, dedicated processors and/or radios) for multiple RATs (e.g., a first receive chain for LTE and a second receive chain for 5GNR). For example, as shown in Figure 5, cellular communication circuitry 330 may include a modem 510 and a modem 520. Modem 510 may be configured for communications according to a first RAT, e.g., such as LTE or LTE- A, and modem 520 may be configured for communications according to a second RAT, e.g., such as 5G NR.

[0080] As shown, modem 510 may include one or more processors 512 and a memory 516 in communication with processors 512. Modem 510 may be in communication with a radio frequency (RF) front end 530. RF front end 530 may include circuitry for transmitting and receiving radio signals. For example, RF front end 530 may include receive circuitry (RX) 532 and transmit circuitry (TX) 534. In some embodiments, receive circuitry 532 may be in communication with downlink (DL) front end 550, which may include circuitry for receiving radio signals via antenna 335a.

[0081] Similarly, modem 520 may include one or more processors 522 and a memory 526 in communication with processors 522. Modem 520 may be in communication with an RF front end 540. RF front end 540 may include circuitry for transmitting and receiving radio signals. For example, RF front end 540 may include receive circuitry 542 and transmit circuitry 544. In some embodiments, receive circuitry 542 may be in communication with DL front end 560, which may include circuitry for receiving radio signals via antenna 335b.

[0082] In some embodiments, a switch 570 may couple transmit circuitry 534 to uplink (UL) front end 572. In addition, switch 570 may couple transmit circuitry 544 to UL front end 572. UL front end 572 may include circuitry for transmitting radio signals via antenna 336. Thus, when cellular communication circuitry 330 receives instructions to transmit according to the first RAT (e.g., as supported via modem 510), switch 570 may be switched to a first state that allows modem 510 to transmit signals according to the first RAT (e.g., via a transmit chain that includes transmit circuitry 534 and UL front end 572). Similarly, when cellular communication circuitry 330 receives instructions to transmit according to the second RAT (e.g., as supported via modem 520), switch 570 may be switched to a second state that allows modem 520 to transmit signals according to the second RAT (e.g., via a transmit chain that includes transmit circuitry 544 and UL front end 572).

[0083] In some embodiments, the cellular communication circuitry 330 may be configured to establish a first wireless link with a first cell according to a first radio access technology (RAT), wherein the first cell operates in a first system bandwidth and establish a second wireless link with a second cell according to a second radio access technology (RAT), wherein the second cell operates in a second system bandwidth. Further, the cellular communication circuitry 330 may be configured to determine whether the cellular communication circuitry 330 has uplink activity scheduled according to both the first RAT and the second RAT and perform uplink activity for both the first RAT and the second RAT by time division multiplexing (TDM) uplink data for the first RAT and uplink data for the second RAT if uplink activity is scheduled according to both the first RAT and the second RAT. In some embodiments, to perform uplink activity for both the first RAT and the second RAT by time division multiplexing (TDM) uplink data for the first RAT and uplink data for the second RAT if uplink activity is scheduled according to both the first RAT and the second RAT, the cellular communication circuitry 330 may be configured to receive an allocation of a first UL subframe for transmissions according to the first RAT and an allocation of a second UL subframe for transmissions according to the second RAT. In some embodiments, the TDM of the uplink data may be performed at a physical layer of the cellular communication circuitry 330. In some embodiments, the cellular communication circuitry 330 may be further configured to receive an allocation of a portion of each UL subframe for control signaling according to one of the first or second RATs.

[0084] As described herein, the modem 510 may include hardware and software components for implementing the above features or for time division multiplexing UL data for NS A NR operations, as well as the various other techniques described herein. The processors 512 may be configured to implement part or all of the features described herein, e.g., by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium). Alternatively (or in addition), processor 512 may be configured as a programmable hardware element, such as an FPGA (Field Programmable Gate Array), or as an ASIC (Application Specific Integrated Circuit). Alternatively (or in addition) the processor 512, in conjunction with one or more of the other components 530, 532, 534, 550, 570, 572, 335 and 336 may be configured to implement part or all of the features described herein.

[0085] In addition, as described herein, processors 512 may include one or more processing elements. Thus, processors 512 may include one or more integrated circuits (ICs) that are configured to perform the functions of processors 512. In addition, each integrated circuit may include circuitry (e.g., first circuitry, second circuitry, etc.) configured to perform the functions of processors 512.

[0086] As described herein, the modem 520 may include hardware and software components for implementing the above features for time division multiplexing UL data for NSA NR operations, as well as the various other techniques described herein. The processors 522 may be configured to implement part or all of the features described herein, e.g., by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium). Alternatively (or in addition), processor 522 may be configured as a programmable hardware element, such as an FPGA (Field Programmable Gate Array), or as an ASIC (Application Specific Integrated Circuit). Alternatively (or in addition) the processor 522, in conjunction with one or more of the other components 540, 542, 544, 550, 570, 572, 335 and 336 may be configured to implement part or all of the features described herein.

[0087] In addition, as described herein, processors 522 may include one or more processing elements. Thus, processors 522 may include one or more integrated circuits (ICs) that are configured to perform the functions of processors 522. In addition, each integrated circuit may include circuitry (e.g., first circuitry, second circuitry, etc.) configured to perform the functions of processors 522.

5G NR Non- standalone (NSA) Operation with LTE

[0088] In some implementations, fifth generation (5G) wireless communication will initially be deployed concurrently with current wireless communication standards (e.g., LTE). For example, dual connectivity between LTE and 5G new radio (5G NR or NR) has been specified as part of the initial deployment of NR. Thus, as illustrated in Figures 6A-B, evolved packet core (EPC) network 600 may continue to communicate with current LTE base stations (e.g., eNB 602). In addition, eNB 602 may be in communication with a 5G NR base station (e.g., gNB 604) and may pass data between the EPC network 600 and gNB 604. Thus, EPC network 600 may be used (or reused) and gNB 604 may serve as extra capacity for UEs, e.g., for providing increased downlink throughput to UEs. In other words, LTE may be used for control plane signaling and NR may be used for user plane signaling. Thus, LTE may be used to establish connections to the network and NR may be used for data services.

[0089] Figure 6B illustrates a proposed protocol stack for eNB 602 and gNB 604. As shown, eNB 602 may include a medium access control (MAC) layer 632 that interfaces with radio link control (RLC) layers 622a-b. RLC layer 622a may also interface with packet data convergence protocol (PDCP) layer 612a and RLC layer 622b may interface with PDCP layer 612b. Similar to dual connectivity as specified in LTE- Advanced Release 12, PDCP layer 612a may interface via a master cell group (MCG) bearer to EPC network 600 whereas PDCP layer 612b may interface via a split bearer with EPC network 600.

[0090] Additionally, as shown, gNB 604 may include a MAC layer 634 that interfaces with RLC layers 624a-b. RLC layer 624a may interface with PDCP layer 622b of eNB 602 via an X2 interface for information exchange and/or coordination (e.g., scheduling of a UE) between eNB 602 and gNB 604. In addition, RLC layer 624b may interface with PDCP layer 614. Similar to dual connectivity as specified in LTE- Advanced Release 12, PDCP layer 614 may interface with EPC network 600 via a secondary cell group (SCG) bearer. Thus, eNB 602 may be considered a master node (MeNB) while gNB 604 may be considered a secondary node (SgNB). In some scenarios, a UE may be required to maintain a connection to both an MeNB and a SgNB. In such scenarios, the MeNB may be used to maintain a radio resource control (RRC) connection to an EPC while the SgNB may be used for capacity (e.g., additional downlink and/or uplink throughput).

Enhancements for Aggregated Uplink Transmission in Wireless Communication Systems [0091] Based on recent studies, 3GPP standards for LTE and 5G NR have been working on TTI bundling and/or slot aggregation techniques to improve uplink (UL) performance for voice calls (e.g., voice over LTE (VoLTE) or voice over NR (VoNR)) and latency critical applications (e.g., ultra reliable low latency connections (URLLC).

[0092] More specifically, in cell edge conditions (e.g., far cell, low RSRP, etc.), UEs may utilize certain techniques such as transmitting same information multiple times as part of TTI bundling or slot aggregation procedures. For example, in LTE, UEs may transmit a total of four repetitions as part of TTI bundled transmissions, according to some embodiments. Alternatively, in NR, UEs may be configured to perform slot aggregation using two, four, or eight repetitions, according to some embodiments. [0093] These repetitions involved in TTI bundling or slot aggregation may be beneficial during transmission (Tx) limited scenarios where Tx power is capped (e.g., a maximum Tx power is enforced) due to specific absorption rate (SAR) regulatory backoff in which the UE may be unable to close the uplink loop. For example, if two UEs are capped to the same Tx power, then the UE with TTI bundling ON or slot aggregation level (SAL) ON may experience time diversity gain. In other words, TTI bundling or SAL may be beneficial for increasing average transmit power for UEs capable of performing said techniques. However, with the introduction of time averaging regulatory features for UL, the UE may not need to cap (e.g., limit) the instantaneous Tx power to the specified SAR limits. For example, instead of limiting the instantaneous Tx power, the UE only need to maintain the average Tx power over a running averaging time window defined by various regulatory bodies for various frequency groups, according to some embodiments. However, due to TTI bundling or slot aggregation, uplink (UL) scheduling rate may increase significantly. This may have an adverse impact on Tx power as, in some instances, the UE may need to back off Tx power (e.g., as part of maintaining an average Tx power) which may further lead to an increase in block error rate (BLER). For example, the UE may reduce the Tx power over the course of a few seconds (as one example) in order to keep the average Tx within the respective time averaging window at or below a regulatory SAR limit. Accordingly, the reduced Tx power may further result in significant degradation of audio quality, call drops, increased latency, and increased UE power consumption. Accordingly, improvements are desired.

Figures 7A-B - TTI Bundling With and Without Time Averaging

[0094] Figures 7A-B illustrate example aspects of transmission timing interval (TTI) bundling with and without the utilization of time averaging, according to some embodiments. More specifically, Figure 7A illustrates a UE operating in a far cell (e.g., cell edge scenario) and transmitting uplink signaling to a network (e.g., a base station (BS) or network node) through use of TTI bundling without using time averaging of the bundled transmissions. For example, in Figure 7A, a UE may be limited to a regulatory Tx power of 23dBm and may be further regulated to an SAR regulatory backoff limit of 17dBm. While Figures 7A and 7B illustrate examples using specific SAR regulatory backoff limits (e.g., 17dBm), regulatory Tx powers (e.g., 23dBm), and TA reserve limits (e.g., 15dBm), other values may be utilized for these parameters with respect to different frequency bands, antennas, projects, etc. [0095] Accordingly, in 702 A, the UE may transmit uplink signaling according to these limits and without performing any time averaging or TTI bundling. Additionally, Figure 7A illustrates an “X” corresponding to an indication that the transmission of 702A has failed (e.g., the transmission was not successfully received at the network). In 704A, the UE may still operate under these parameters but additionally perform TTI bundling using an increased scheduling rate. According to some embodiments, the UE may determine to perform TTI bundling based at least in part on the previously failed transmission of 702A. More specifically, the UE may repeat the uplink transmissions as shown in the scheduling instances of TTI n, TTI n+1, TTI n+2, TTI n+3. According to some embodiments, the uplink transmissions of 704A may or may not include data which was transmitted in 702A (e.g., 704A may be characterized as retransmissions). Accordingly, each of these TTI repetitions may be transmitted at the SAR limit of 17dBm, according to some embodiments. In some embodiments, the TTI bundled transmissions of 704A may also fail (e.g., as indicated by the “X”). Accordingly, the UE may, in some instances, continue to perform the TTI bundling without time averaging for another repetition of four UL transmissions at the SAR limit (e.g., as shown in 706A). Similar to 704A, the uplink transmissions of 706A may or may not include data which was transmitted in 702A and/or 704A (e.g., 706A may be characterized as retransmissions). While four repetitions are shown in Figure 7A (e.g., as in LTE scenarios), other repetition patterns such as two (e.g., TTI n, TTI n+1) and eight (e.g., TTI n, TTI n+1, TTI n+2, TTI n+3 . . . TTI n+7) may be possible in NR scenarios, according to some embodiments. Accordingly, these repetitions may not have an adverse effect on the Tx power of the UE as the Tx power may already be capped at the SAR limit. Furthermore, the TTI bundled transmissions of 706A may result in a successful transmission (and reception) as indicated by the “check” or “checkmark”, according to some embodiments.

[0096] Alternatively, when TTI bundling is enabled with time averaging (e.g., running in background), the UE may start transmitting same information multiple times as configured by the network (e.g., four repetitions as in LTE). For example, as shown in Figure 7B, a UE may be operating in a cell edge scenario and transmitting uplink signaling or user data to the network (e.g., a BS or other network node) through use of TTI bundling and using time averaging of the bundled transmissions. According to some embodiments, when time averaging is enabled, the UE may not need to cap the Tx power at the regulated SAR. Instead, the UE may be allowed to transmit at the regulatory limit but still need to maintain the SAR budget. Accordingly, consecutive transmissions or re-transmissions with TTI bundling or slot aggregation may increase the scheduling rate by the factor of re-transmission. In other words, for LTE TTI bundling, the scheduling rate may increase by four times as the same data is transmitted four times. In some embodiments related to NR, the change (e.g., increasing or decreasing) of the scheduling rate may depend on the SAL. For example, a greater number of transmissions at the regulatory Tx power (which may be higher than the SAR as is the case in most scenarios), the UE may rapidly exhaust the SAR budget and therefore would need to reduce the Tx power to a reserve value which is much lower than the SAR value (e.g., TA__reserve corresponding to 15dBm for the given example). For example, some regulatory entities may specify to UEs a SAR limit that the Tx power may be reduced to, according to some embodiments. Furthermore, UE manufacturers or original equipment manufacturers (OEMs) may specify to UEs a reserve limit (e.g., TA reserve) that the Tx power may be reduced to pass or exceed the SAR regulatory backoff limit, according to some embodiments.

[0097] Accordingly, in 702B the UE may repeat the uplink transmissions as shown in the scheduling instances of TTI n, TTI n+1, TTI n+2, TTI n+3. Additionally, Figure 7B illustrates an “X” corresponding to an indication that the transmission of 702B may have failed (e.g., the transmission was not successfully received at the network). Accordingly, in 704 B, the UE’s scheduling rate may further increase (although such redundant transmissions may not always be necessary) which may not be beneficial when retransmissions occur due to the BLER of some or all of the packets, according to some embodiments. In some embodiments, the Tx power may converge to the SAR limit due to high scheduling rates. Furthermore, the TTI bundled transmissions of 704B may result in a successful transmission (and/or reception) as indicated by the “check” or “checkmark”, according to some embodiments.

[0098] Alternatively, as in 706B, the Tx power may be reduced such that it is lower than the SAR limit due to time averaging. For example, as shown in 706B, the repeated transmissions in the TTI bundle may be transmitted at the transmission reserve limit TAreserve of 15dBm which will further increase the BLER, degrade retransmissions, and will keep on using the SAR power budget inefficiently and unnecessarily, according to some embodiments. Accordingly, the TTI bundled transmissions of 706B may result in a failed transmission (and/or reception) as indicated by the “X”, according to some embodiments. Accordingly, improvements are desired.

Figure 8 - Performance Enhancements of TTI Bundling [0099] Figure 8 illustrates example performance plots comparing the use versus non-use of TTI bundling, according to some embodiments. More specifically, the top plot of Figure 8 illustrates plots of an audio quality score (in terms of mean opinion score (MOS)) ranging in values of 1 to 5 of an approximately four minute long (e.g., ~ 12:22:00 to 12:26:00) voice call that was recorded, analyzed, and plotted over time (e.g., MOS vs. time). Additionally, the bottom plot of Figure 8 illustrates a plot of maximum transmit power level (MTPL) ranging from values of 14dBm to 25dBm versus time for the same voice call. Furthermore, by evaluating the voice call between two UEs, the same conversation was able to be analyzed with TTI bundling ON (solid line, corresponding to a first UE) and TTI bundling OFF (dashed line, corresponding to a second UE).

[00100] As shown in the top plot of Figure 8 (MOS vs. time), as the conversation progressed the MOS of the TTI bundling ON and OFF scenarios stayed relatively close to a MOS value of four until from 12:24:00 to 12:24:45 and 12:25:30 to 12:25:45 in which the MOS of the TTI bundling ON scenario experienced multiple dips (e.g., decreases) in MOS. These decreases in MOS may be as a result of TTI bundling using time averaging. For example, as related to Figure 7B, in the scenario in which the UE is operating with TTI bundling ON and with time averaging running on the UE, the Tx power may be reduced, as part of the time averaging technique, such that it is lower than the SAR limit.

[00101] This reduction in Tx power is illustrated in the bottom plot of Figure 8 by the decreased MTPL in the time periods from 12:24:00 to 12:24:45 and 12:25:30 to 12:25:45. More specifically, for the TTI bundling ON scenario, the MTPL dropped to approximately 19dBm at 12:24: 15 and remained at or around that level until about 12:24:45. According to some embodiments, this may be indicative of the Tx power reaching and maintaining the Tx power at the SAR limit of the UE. However, at 12:25:45, the MTPL dropped even further to approximately 16dBm. This larger decrease in MTPL may be indicative of the Tx power reaching TA reserve limit of the UE in order to lower the average Tx power over time, according to some embodiments.

[00102] Accordingly, as shown in the top plot of Figure 8, the reduced Tx power (e.g., MTPL) resulted in a decrease in voice call quality (e.g., a lower MOS) as shown by the dips in audio quality score from 12:24:00 to 12:24:45 and 12:25:30 to 12:25:45. In contrast, the MOS of the TTI bundling OFF scenario stayed relatively close to a value of 4.5. In other embodiments, UEs without TTI bundling such as the one described in Figure 8 may also experience degraded MOS when the SAR limit is greater than a regulated transmission limit (as part of a TTI bundling benefit). Additionally or alternatively, the MOS for a UE without TTI bundling may be degraded when both devices are capped to the same Tx power for the duration of the call (e.g., a maximum Tx threshold), according to some embodiments. Therefore, there may exist a need for enhancements or methods related to mitigating or minimizing degradation of audio quality, call drops, increased latency, and increased UE power consumption which may be effects of time averaging techniques coupled with TTI bundling.

Figure 9 - Method for Enhanced Aggregated Uplink Transmission

[00103] Figure 9 is a flowchart diagram illustrating an example method of enhanced aggregated uplink transmission in a wireless communication system, according to some embodiments Aspects of the method of Figure 9 may be implemented by a user equipment (e.g., UE 106) in communication with one or more base stations (such as the BS 102) as illustrated in and described with respect to the Figures, or more generally in conjunction with any of the computer systems or devices shown in the Figures, among other circuitry, systems, devices, elements, or components shown in the Figures, among other devices, as desired. For example, one or more processors (or processing elements) of the UE (e.g., processor(s) 302, baseband processor(s), processor(s) associated with communication circuitry, etc., among various possibilities) may cause the UE to perform some or all of the illustrated method elements. Additionally, one or more processors (or processing elements) of the BS (e.g., processor(s) 402, baseband processor(s), processor(s) associated with communication circuitry, etc., among various possibilities) may cause the BS to perform some or all of the illustrated method elements. Note that while at least some elements of the method are described in a manner relating to the use of communication techniques and/or features associated with 3GPP specification documents, such description is not intended to be limiting to the disclosure, and aspects of the method may be used in any suitable wireless communication system, as desired. In various embodiments, some of the elements of the methods shown may be performed concurrently, in a different order than shown, may be substituted for by other method elements, or may be omitted. Additional method elements may also be performed as desired. As shown, the method may operate as follows.

[00104] In 902, a wireless device (e.g., a UE) may establish a cellular link with a network (e.g., a network node such as a BS), according to some embodiments. The cellular link may operate according to 5GNR. For example, the wireless device may establish a session with an AMF entity of the cellular network by way of one or more gNBs that provide radio access to the cellular network. As another possibility, the cellular link may operate according to LTE. For example, the wireless device may establish a session with a mobility management entity of the cellular network by way of an eNB that provides radio access to the cellular network. Other types of cellular links are also possible, and the cellular network may also or alternatively operate according to another cellular communication technology (e.g., UMTS, etc.), according to various embodiments.

[00105] Establishing the wireless link may include establishing a RRC connection with a serving cellular base station, at least according to some embodiments. Establishing the first RRC connection may include configuring various parameters for communication between the wireless device and the cellular base station, establishing context information for the wireless device, and/or any of various other possible features, e.g., relating to establishing an air interface for the wireless device to perform cellular communication with a cellular network associated with the cellular base station. After establishing the RRC connection, the wireless device may operate in a RRC connected state. In some instances, the RRC connection may also be released (e.g., after a period of inactivity with respect to data communication), in which case the wireless device may operate in a RRC idle state or a RRC inactive state. In some instances, the wireless device may perform handover (e.g., while in RRC connected mode) or cell re-selection (e.g., while in RRC idle or RRC inactive mode) to a new serving cell, e.g., due to wireless device mobility, changing wireless medium conditions, and/or for any of various other possible reasons.

[00106] In 904, the UE may receive a UE capability request from the network node, according to some embodiments. More specifically, the network node may transmit, to the UE, a UE capability request in order to inquire or determine whether or not the UE has a capability to support dynamic slot aggregation or TTI bundling, according to some embodiments.

[00107] In 906, the UE may transmit, to the network node, a UE capability response, according to some embodiments. More specifically, the UE may, in response to the UE capability request received from the network node, transmit a UE capability response to the network node and further indicate whether or not it has or supports a capability related to dynamic slot aggregation or TTI bundling. According to some embodiments related to 5G NR, the UE may refrain transmitting a UE capability response. For example, the UE may not explicitly indicate its capability of slot aggregation to the network node via a UE capability response. In some embodiments, the UE may indicate a maximum value of a slot aggregation level that it supports (e.g., 2, 4, or 8). [00108] In 908, the UE may receive an RRC Connection Reconfiguration message from the network, according to some embodiments. More specifically, the network node may transmit the RRC Connection Reconfiguration message to configure the UE for an appropriate slot aggregation level (SAL). For example, the network may configure the UE via RRC message with a configuration of two, four, or eight SALs. In some embodiments, the UE may assume or implement a SAL with a value of one if the network doesn’t configure the SAL (e.g., if the UE doesn’t receive an RRC Connection Reconfiguration message). Accordingly, for NR, the slot aggregation procedure may be able to be performed using a reduced number of steps. For example, as the UE detects the increasing UL duty cycle, the SAL may be increased as UL duty cycle improves or if other settings change (such as SAR scenario or frequency, TX port, application being used, as some examples). In other words, the increasing or decreasing duty cycle may be associated with how frequently network gives grant to the UE. Therefore, the occurrence of how often transmission is being engaged at the UE is driven by the network depending on the UE’s needs (e.g., scenarios) and also the BLER.

[00109] Therefore, while initially the UE may assume a SAL of “ 1”, if it doesn’t receive a RRC Connection Reconfiguration message, the UE may then be able to determine a new optimal SAL and increase to a new SAL equal to 2, 4, or 8 (e.g., as in NR). Accordingly, a RRC Reconfiguration message may not be needed at each instance that the SAL updated. For example, the SAL may be increased or decreased (if a higher SAL is configured) based on a formula. Therefore, a RRC reconfiguration message may not be needed every time is there has been prior communication between the network and UE (in some embodiments including a bit map for increasing or reducing a SAL.

[00110] In 910, the UE may determine an optimal (e.g., preferred) slot aggregation level, according to some embodiments. For example, the UE may determine a preferred SAL based on the current Tx port and RF frequency of operation that UE is utilizing. In some embodiments, the optimal or preferred SAL may be determined based on a UE specific implementation.

[00111] According to some embodiments, a preferred (e.g., optimal) SAL may be determined based at least one of the following equations and inequalities. As a first option, an optimal SAL may be determined according to the equation and inequality the preferred SAL = min [8, maximum allowed by network], if Z < 0. As a second option, the preferred SAL may be determined according to the equation and inequality the preferred SAL = min [4, maximum allowed by network], if 0 < Z < a. As a third option, the preferred SAL may be determined according to the equation and inequality the preferred SAL = min [2, maximum allowed by network], if a < Z < b. As a fourth option, the preferred SAL may be determined by the equation and inequality the preferred SAL = 1 (disabled), if b < Z. Additionally, the values ‘a’ & ‘b’ may correspond to values per band or per port and may be further specified by UE manufacturer. Furthermore, the UE may calculate value or parameter Z according to the formula Z = “x dB - duty cycle gain dB - y dB.

[00112] In 912, the UE may transmit a message to the network node, according to some embodiments. More specifically, the UE may transmit uplink messaging or signaling (e.g., a message) including an indication or notification of the preferred SAL that the UE has determined to use for uplink transmissions. For example, having determined a preferred SAL according to the procedure discussed in 910, the UE may indicate to the network node which SAL it should optimally use for uplink transmissions. Accordingly, the message may include an indication or notification of whether the optimal SAL is a value of 1, 2, 4, or 8, according to some embodiments. In some embodiments, the message may be comprised in or part of physical (PHY) layer signaling, media access control (MAC) signaling, uplink control information (UCI), or higher layer signaling or messages.

[00113] In 914, the UE may receive downlink control information (DCI) transmitted from the network node, according to some embodiments. More specifically, the network node may transmit DCI to the UE including an indication or configuration information associated with an updated or different SAL from the SAL indicated in the message received in 912. For example, according to some embodiments, the DCI may include an indication or configuration information for a different or updated SAL (e.g., different than the preferred SAL) with value of 1, 2, 4, or 8 (depending on the value of the previously indicated preferred SAL). For example, having indicated in 912 to the network node which SAL it should optimally use for uplink transmissions, the BS may transmit DCI indicating an updated SAL or different SAL to the UE so as to inform the UE of whether or not it can proceed with uplink transmissions according to the preferred SAL it determined in 910. Accordingly, the UE may proceed to perform uplink transmissions according to the updated or different SAL indicated in the DCI of 914.

Figure 10 - Method for Optimal SAL Determination [00114] Figure 10 is a flowchart diagram illustrating an example method of determining an optimal SAL, according to some embodiments. More specifically, Figure 10 illustrates an example UE implementation of determining an optimal SAL based on calculating one or more values (e.g., Z) and comparing them to various inequalities of UE manufacturer specified parameters, according to some embodiments.

[00115] In 1002, the UE may determine whether or not the network has configured dynamic slot aggregation, according to some embodiments. For example, the UE may be able to determine whether or not the network has configured dynamic slot aggregation for TTI bundling based on the UE receiving (or not receiving) an RRC Connection Reconfiguration message from the network. More specifically, if the RRC Connection Reconfiguration message included a configuration for dynamic slot aggregation, the UE may therefore assume that dynamic slot aggregation has been configured by the network. Additionally or alternatively, if the UE receives DCI including an update of an SAL, the UE may determine that the network has configured dynamic slot aggregation. Accordingly, if the UE determines that the network has configured dynamic slot aggregation, it may proceed to 1004 to calculate a parameter Z in order to later determine an optimal SAL. Alternatively, the UE determines that the network has not configured dynamic slot aggregation, it may proceed to 1008 to determine whether a timer has expired or a triggering event has occurred such that it should redetermine whether or not the network has configured dynamic slot aggregation (e.g., perform 1002 again).

[00116] In 1004, the UE may calculate value or parameter Z according to the formula Z = “x dB - duty cycle gain dB - y dB, according to some embodiments. Additionally, X may be an SAR limit subtracted from a regulatory transmission limit, the duty cycle gain may be an SAR budget leveraged from duration when Tx is off, and Y may be an additional buffer or offset for additional duty cycle prediction based on past “f ’ seconds. Furthermore, for a time division duplex (TDD) band, if the network configures an UL / DL split with 20% UL and 80% DL, then this may result in the UE Tx being off for 80 percent of the time which may be approximately 6dB greater than the SAR limit, according to some embodiments.

[00117] In some embodiments, the UE may calculate Z for the current Tx port and RF frequency of operation currently being used by the UE. Accordingly, once Z has been calculated, the UE may proceed to 1006 to determine an optimal SAL using the calculated Z parameter, according to some embodiments. [00118] In 1006, the UE may utilize the parameter Z calculated in 1004 to help determine an optimal SAL. For example, the UE may determine an optimal SAL by utilizing calculated parameter Z in one or more equations and/or inequalities. As a first option, an optimal SAL may be determined according to the equation and inequality SAL = min [8, maximum allowed by network], if Z < 0. In other words, if a value Z is less than or equal to zero, an optimal SAL may be determined to be the minimum of either 8 or the maximum SAL allowed by the network, according to some embodiments. As a second option, the optimal SAL may be determined according to the equation and inequality SAL = min [4, maximum allowed by network], if 0 < Z < a. In other words, if a value Z is greater zero and less than or equal to a value “a”, an optimal SAL may be determined to be the lesser value of either 4 or the maximum SAL allowed by the network, according to some embodiments. As a third option, the optimal SAL may be determined according to the equation and inequality SAL = min [2, maximum allowed by network], if a < Z < b. In other words, if parameter Z is greater than value “a” and less than or equal to value “b”, the optimal SAL may be the minimum value of either 2 or the maximum SAL allowed by the network, according to some embodiments. As a fourth option, the optimal SAL may be determined by the equation and inequality SAL = 1 (disabled), if b < Z. In other words, if parameter Z is greater than value “b”, the optimal slot aggregation level may be set to a value of one corresponding to slot aggregation or TTI bundling being disabled, according to some embodiments.

[00119] Additionally and as described in regard to Figure 9, the values ‘a’ & ‘b’ may correspond to values per band or per port and may be further specified by UE manufacturer. Furthermore, the optimal SAL may be determined for the current Tx port and RF frequency of operation currently being used by the UE. Accordingly, upon determining an optimal SAL in 1006, the UE may proceed to 1008.

[00120] In 1008, the optimal SAL may be determined periodically and/or determined upon occurrence or of an event or expiry of a timer. For example, the UE may be triggered to determine an optimal SAL upon occurrence of one or more events or expiry of a timer initiated and/or maintained by the UE. Additionally or alternatively, the UE may be triggered to determine a SAL upon occurrence of one or more events or expiry of a timer initiated and/or maintained by the network. For example, the network may initiate and maintain a timer and therefore request the UE for a status of the SAL. However, the UE may need to be aware of the timer (e.g., a value or state of the timer) to re-evaluate or re-calculate a SAL so as to maintain an optimal or preferred SAL value. As shown in 1008a, events that may trigger the UE to calculate parameter Z and compare it to the aforementioned values zero, “a”, and “b” in order to determinate an optimal SAL may include at least one of a handover, toggling ON/OFF of airplane mode (e.g., which may disable or enable certain features of the UE such as Wi-Fi or Bluetooth, as some examples), a change of Tx port being used by the UE, an RRC state change of the UE, a change in the powered state of the UE (e.g., powering up/on or down/off), a change in SAR scenario (e.g., head, body, etc.). According to some embodiments, SAR scenarios such as head or body may correspond to power back-off scenarios. For example, appropriate back-off values may be chosen based on how the UE is held and/or the type of application. Additionally or alternatively, events that may trigger the UE to calculate parameter Z and compare it to the aforementioned values zero, “a”, and “b” in order to determinate an optimal SAL may include at least one of a change in UL/DL slot configuration, a change in subcarrier spacing (SCS), activation, deactivation, configuration or deconfiguration of an UL carrier aggregation configuration, or a change in connectivity related to an application running on the UE (e.g., changing from URLLC to data centric or vice versa).

Figures 11 and 12 - Enhanced TTI Bundling Enabling/Disabling

[00121] Figures 11 and 12 are communication flow diagrams of wireless communication systems performing example aspects of enhanced TTI bundling enabling/disabling, according to some embodiments. More specifically, Figure 11 illustrates an example method of enhanced LTE uplink coverage improvement via a UE capability to disable TTI bundling, according to some embodiments. For example, as briefly discussed above, TTI bundling or slot aggregation may not be efficient for certain scenarios (e.g., such as LTE) and may produce adverse effects such as call drops, poor audio quality, high latency when time averaging is enabled and the “Z” parameter is less than zero. Accordingly, it may be beneficial to disable TTI bundling/slot aggregation for such scenarios.

[00122] As shown in Figure 11, at 1102, the UE may transmit a message to the network in order to invoke a response from the base station, according to some embodiments. More specifically, the UE may transmit signaling to the BS to invoke (e.g., request) or cause the BS to transmit a UE capability request in response to receiving the message from the UE. In some embodiments, the signaling may include a tracking area update (TAU) which may be used to explicitly or implicit indicate that the BS should transmit a UE capability request to the UE. Accordingly, in 1104, the UE may receive a UE capability request from the BS, according to some embodiments. More specifically, the BS may transmit, to the UE and at least partially based on receiving the signaling in 1102, a UE capability request in order to inquire or determine whether or not the UE has a capability to support slot aggregation (e.g., dynamic slot aggregation, as one example) or TTI bundling, according to some embodiments.

[00123] Accordingly, if a UE has calculated parameter Z and determined that Z is less than zero, the UE may determine whether or not to disable TTI bundling via a UE capability response. In some embodiments, the UE may be able to indicate to the network (e.g., BS) to disable TTI bundling via a feature group indicator (FGI) bit in a UE capability response. Additionally, an example code block related to disabling TTI bundling via a FGI bit may be characterized as follows:

1 = Indicator 25: Inter-frequency measurements and reporting in E-UTRA connected mode - Supported .0 indicator 25: HRPD measurements, reporting and measurement reporting event B2 in E-UTRA connected mode - not supported

. 1. .. = Indicator 27: EUTRA RRC CONNECTED to UTRA CELL DCH CS handover- supported

. . . 1 . . . = Indicator 28: TTI bundling - Supported

FeatureGroupIndicators ‘01111111’ 11001111 1111110 lOl I l HO’B

. . . .0.. = Indicator 29: Semi-Persistent Scheduling - Not supported

. . .0.. = Indicator 30: Handover between FDD and TDD - Not supported

...1... = Indicator 31 : Mechanisms defined for cells broadcasting multi band information - Supported

> 0 = Indicator 32: Undefined - Not supported

[00124] Furthermore, as the TTI bundling may be disabled through a FGI bit in the UE capability response, it may be applicable to all bands (e.g., frequency bands) and ports (e.g., Tx ports), according to some embodiments. Accordingly, potential benefits of TTI bundling or slot aggregation may not exist for bands or ports where SAR limits may be higher than a specified regulatory maximum. However, as this method may be essentially implemented as a call barring (CB), minimal software changes may be necessary to provide this enhancement.

[00125] As shown in Figure 12, at 1202, the UE may receive a UE capability request from the BS, according to some embodiments. More specifically, the BS may transmit, to the UE, a UE capability request in order to inquire or determine (e.g., via a request) whether or not the UE has a capability to support dynamic TTI bundling, according to some embodiments.

[00126] Furthermore, the UE may determine to indicate, via a UE capability response in 1204, to the network whether it supports the dynamic TTI bundling. In some embodiments, the UE may be able to indicate this support to the network (e.g., BS) via a FGI bit in a UE capability response. Moreover, if a UE has calculated parameter Z and determined that Z is less than zero, the UE may also transmit a request in 1206 to the BS to disable TTI bundling, according to some embodiments. Alternatively, if a UE has calculated parameter Z and determined that Z is greater than zero, the UE may also transmit a request to the BS in 1206 to enable TTI bundling, according to some embodiments. Accordingly, the network may transmit in 1208 downlink signaling (e.g., DCI) to enable or disable the TTI bundling based on whether the UE indicated to enable or disable TTI bundling via the transmitting request. This method may provide an optimized enhancement as the TTI bundling / slot aggregation benefits may be retained.

Example Embodiments

[00127] According to some embodiments, a user equipment (UE) may establish a cellular link with a network and receive a UE capability request from the network. The UE may transmit a UE capability response to the network. The UE capability response may include an indication that the UE supports slot aggregation and the UE may receive, from the network, a radio resource control (RRC) connection reconfiguration message indicating a maximum value for slot aggregation. The UE may determine, based on one or more calculations, a preferred slot aggregation level (SAL) and transmit, to the network, a message indicating the preferred SAL. The UE may receive, from the network, downlink control information (DCI) including configuration information associated with a different SAL and accordingly transmit, in accordance with the different SAL, uplink (UL) signaling to the network.

[00128] In some embodiments, the one or more calculations may include calculating a parameter Z. Additionally, the determination of the preferred SAL may be further based on a comparison of the parameter Z to one or more values including values specified by a manufacturer of the UE. The parameter Z may be calculated using the formula Z = x dB - duty cycle gain dB - y dB, where x may be a specific absorption rate (SAR) limit subtracted from a regulatory transmission (Tx) limit, the duty cycle gain may be an SAR budget associated with a duration when transmission is disabled, and the parameter y may be an additional buffer or offset for an additional duty cycle prediction.

[00129] According to some scenarios, the UE may determine a preferred SAL by utilizing calculated parameter Z in one or more equations and/or inequalities and the values “a” and “b” specified by the UE manufacturer. As a first option, the preferred SAL may be determined according to the equation and inequality the preferred SAL = min [8, maximum allowed by network], if Z < 0. As a second option, the preferred SAL may be determined according to the equation and inequality the preferred SAL = min [4, maximum allowed by network], if 0 < Z < a. As a third option, the preferred SAL may be determined according to the equation and inequality the preferred SAL = min [2, maximum allowed by network], if a < Z < b. As a fourth option, the preferred SAL may be determined by the equation and inequality the preferred SAL = 1, if b < Z.

[00130] In some instances, expiry of a timer or occurrence of one or more events may trigger the UE to determine a new SAL. Additionally, the one or more events may include at least one of an occurrence of a handover, an airplane mode being enabled or disabled, a change of a transmission (Tx) Port, a change of in the UE’s RRC state; the UE being turned on or powered up; a change in the UE’s specific absorption rate (SAR) scenario, a change in at least one of an UL or downlink (DL) slot configuration, a change in a subcarrier spacing (SCS), activation, deactivation, deconfiguration of an UL carrier aggregation (CA) configuration, or a change related to connection properties of an application running on the UE.

[00131] According to some embodiments, the UE may detect an increasing UL duty cycle and decrease, in response to detecting the increasing UL duty cycle, the optimal SAL. Additionally or alternatively, the UE may detect a decreasing UL duty cycle and increase, in response to detecting the decreasing UL duty cycle, the preferred SAL. In some embodiments, a default SAL may be a value of one.

[00132] According to some embodiments, a network node may establish a cellular link with a user equipment (UE) and transmit, to the UE, a UE capability request. The BS may receive, from the UE, a UE capability response including an indication that the UE supports slots aggregation via transmission timing interval (TTI) bundling. The network node may transmit, to the UE, a radio resource control (RRC) connection reconfiguration message indicating a maximum value for slot aggregation. The network node may receive, from the UE, a message indicating a slot aggregation level (SAL) and transmit, to the UE, downlink control information (DCI) indicating at least one of an updated or a different SAL.

[00133] In some embodiments, the DCI may include configuration information useable by the UE in transmitting, according to the at least one of the updated or the different SAL, uplink (UL) signaling to the network node. Additionally or alternatively, the network node may refrain from transmitting the RRC connection reconfiguration message as part of an indication for the UE to use a default SAL value. In some embodiments, the UE capability response may indicate for the network node to disable TTI bundling via a feature group indicator (FGI).

[00134] According to some embodiments, a method may include receiving, from a base station (BS), a user equipment (UE) capability request including an indication requesting support for transmission timing interval (TTI) bundling. The method may further include, transmitting a UE capability response to the BS. The UE capability response may include a feature group indicator (FGI) indicating support for TTI bundling, according to some embodiments. The method may additionally include determining, based on one or more calculations, to enable or disable TTI bundling and transmitting, to the BS and based at least in part on the determination to enable or disable TTI bundling, a request message indicating for the BS to enable or disable TTI bundling. Additionally, the method may include receiving, from the BS, downlink control information (DCI) including configuration information to enable or disable TTI bundling. In some embodiments, the method may include transmitting, prior to receiving the UE capability request, signaling comprising a tracking area update (TAU) to the BS.

[00135] Note that while various embodiments described herein may relate to 5G/NR, they may be extended to any set of wireless communication, including LTE, etc.

[00136] Still another example embodiment may include a device, comprising: an antenna; a radio coupled to the antenna; and a processing element operably coupled to the radio, wherein the device is configured to implement any or all parts of the preceding examples.

[00137] Yet another example embodiment may include a method, comprising: by a device: performing any or all parts of the preceding examples.

[00138] A still further example embodiment may include a computer program comprising instructions for performing any or all parts of any of the preceding examples.

[00139] A yet further example embodiment may include an apparatus comprising means for performing any or all of the elements of any of the preceding examples. [00140] Still another example embodiment may include an apparatus comprising a processing element configured to cause a wireless device to perform any or all of the elements of any of the preceding examples.

[00141] Embodiments of the present disclosure may be realized in any of various forms. For example, some embodiments may be realized as a computer-implemented method, a computer- readable memory medium, or a computer system. Other embodiments may be realized using one or more custom-designed hardware devices such as ASICs. Still other embodiments may be realized using one or more programmable hardware elements such as FPGAs.

[00142] In some embodiments, a non-transitory computer-readable memory medium may be configured so that it stores program instructions and/or data, where the program instructions, if executed by a computer system, cause the computer system to perform a method, e.g., any of the method embodiments described herein, or, any combination of the method embodiments described herein, or, any subset of any of the method embodiments described herein, or, any combination of such subsets.

[00143] In some embodiments, a device (e.g., a UE 106 or BS 102) may be configured to include a processor (or a set of processors) and a memory medium, where the memory medium stores program instructions, where the processor is configured to read and execute the program instructions from the memory medium, where the program instructions are executable to implement any of the various method embodiments described herein (or, any combination of the method embodiments described herein, or, any subset of any of the method embodiments described herein, or, any combination of such subsets). The device may be realized in any of various forms.

[00144] It is well understood that the use of personally identifiable information should follow privacy policies and practices that are generally recognized as meeting or exceeding industry or governmental requirements for maintaining the privacy of users. In particular, personally identifiable information data should be managed and handled so as to minimize risks of unintentional or unauthorized access or use, and the nature of authorized use should be clearly indicated to users.

[00145] Although the embodiments above have been described in considerable detail, numerous variations and modifications will become apparent to those skilled in the art once the above disclosure is fully appreciated. It is intended that the following claims be interpreted to embrace all such variations and modifications.

Claims

CLAIMS What is claimed is:

1. An apparatus, comprising: at least one processor configured to cause a user equipment (UE) to: establish a cellular link with a network; receive, from the network, a UE capability request; transmit, to the network, a UE capability response, wherein the UE capability response comprises an indication that the UE supports slot aggregation; receive, from the network, a radio resource control (RRC) connection reconfiguration message, wherein the RRC connection reconfiguration message indicates a maximum value for slot aggregation; determine, based on one or more calculations, a preferred slot aggregation level (SAL); transmit, to the network, a message indicating the preferred SAL; receive, from the network, downlink control information (DCI), wherein the DCI comprises configuration information associated with a different SAL; and transmit, in accordance with the different SAL, uplink (UL) signaling to the network.

2. The apparatus of claim 1, wherein the one or more calculations comprise a calculation of a parameter Z using the formula Z = x dB - duty cycle gain dB - y dB, wherein x is a specific absorption rate (SAR) limit subtracted from a regulatory transmission (Tx) limit, wherein the duty cycle gain is an SAR budget associated with a duration when transmission is disabled, and wherein the parameter y is an additional buffer or offset for an additional duty cycle prediction.

3. The apparatus of claim 2, wherein “a” and “b” are values specified by a manufacturer of the UE and the SAL is determined according to at least one of the following formulas and inequalities: the preferred SAL = minimum [8, maximum allowed by network], if Z A 0; the preferred SAL = minimum [4, maximum allowed by network], if 0 < Z A a; the preferred SAL = minimum [2, maximum allowed by network], if a < Z A b; or the preferred SAL = 1, if b < Z.

4. The apparatus of claim 1, wherein expiry of a timer or occurrence of one or more events triggers the UE to determine a new SAL.

5. The apparatus of claim 4, wherein the one or more events include at least one of: occurrence of a handover; an airplane mode being enabled or disabled; a change of a transmission (Tx) Port; a change of in the UE’s RRC state; the UE being turned on or powered up; a change in the UE’s specific absorption rate (SAR) scenario; a change in at least one of an UL or downlink (DL) slot configuration; a change in a subcarrier spacing (SCS); activation, deactivation, deconfiguration of an UL carrier aggregation (CA) configuration; or a change related to connection properties of an application running on the UE.

6. The apparatus of claim 1, wherein the at least one processor is further configured to cause the UE to: detect an increasing UL duty cycle; and determine to decrease, in response to detecting the increasing UL duty cycle, a SAL.

7. The apparatus of claim 1, wherein the at least one processor is further configured to cause the UE to: detect a decreasing UL duty cycle; and increase, in response to detecting the decreasing UL duty cycle, a SAL.

8. The apparatus of claim 1, wherein a default SAL is a value of one.

9. The apparatus of claim 1, further comprising: a radio operably coupled to the at least one processor.

10. An apparatus, comprising: at least one processor configured to cause a network node to: establish a cellular link with a user equipment (UE); transmit, to the UE, a UE capability request; receive, from the UE, a UE capability response, wherein the UE capability response comprises an indication that the UE supports slots aggregation via transmission timing interval (TTI) bundling; transmit, to the UE, a radio resource control (RRC) connection reconfiguration message, wherein the RRC connection reconfiguration message indicates a maximum value for slot aggregation; receive, from the UE, a message indicating a preferred slot aggregation level (SAL); and transmit, to the UE, downlink control information (DCI) indicating at least one of an updated or a different SAL.

11. The apparatus of claim 10, wherein “a” and “b” are values specified by a manufacturer of the UE, Z is a parameter determined by the UE, and the SAL satisfies one of the following formulas and inequalities: the SAL = minimum [8, maximum allowed by network], if Z A 0; the SAL = minimum [4, maximum allowed by network], if 0 < Z A a; the SAL = minimum [2, maximum allowed by network], if a < Z A b; or the SAL = 1, ifb < Z.

12. The apparatus of claim 11, wherein Z is a parameter characterized by a formula Z = x dB - duty cycle gain dB - y dB, wherein x is a specific absorption rate (SAR) limit subtracted from a regulatory transmission (Tx) limit, wherein the duty cycle gain is an SAR budget associated with a duration when transmission is disabled, and wherein the parameter y is an additional buffer or offset for an additional duty cycle prediction.

13. The apparatus of claim 11, wherein the DCI comprises configuration information useable by the UE in transmitting, according to at least one of the updated or the different SAL, uplink (UL) signaling to the network node.

14. The apparatus of claim 11, wherein the at least one processor is further configured to cause the network node to refrain from transmitting the RRC connection reconfiguration message as part of an indication for the UE to use a default SAL value.

15. The apparatus of claim 11, wherein the UE capability response indicates for the network node to disable TTI bundling via a feature group indicator (FGI).

16. The apparatus of claim 11, further comprising: at least one antenna; and transceiver circuitry operably coupled to the at least one processor.

17. A method, comprising: receiving, from a base station (BS), a user equipment (UE) capability request, wherein the UE capability request includes an indication requesting support for transmission timing interval (TTI) bundling; transmitting, to the BS, a UE capability response, wherein the UE capability response comprises a feature group indicator (FGI) indicating support for TTI bundling; determining, based on one or more calculations, to enable or disable TTI bundling; transmitting, to the BS and based at least in part on the determination to enable or disable TTI bundling, a request message indicating for the BS to enable or disable TTI bundling; and receiving, from the BS, downlink control information (DCI) comprising configuration information to enable or disable TTI bundling.

18. The method of claim 17, wherein the one or more calculations include: calculating a parameter Z, wherein the calculation of the parameter Z is performed according to the formula Z = x dB - duty cycle gain dB - y dB, wherein x is a specific absorption rate (SAR) limit subtracted from a regulatory transmission (Tx) limit, wherein the duty cycle gain is an SAR budget associated with a duration when transmission is disabled, and wherein the parameter y is an additional buffer or offset for an additional duty cycle prediction.

19. The method of claim 18, wherein in determining to enable or disable TTI bundling, the method further comprises: comparing the parameter Z to one or more values including a plurality of values specified by a manufacturer of the UE.

20. The method of claim 17, further comprising: transmitting, prior to receiving the UE capability request, signaling comprising a tracking area update (TAU) to the BS.

21. A device, comprising: an antenna; a radio coupled to the antenna; and a processing element coupled to the radio; wherein the device is configured to implement a method according to any of the preceding claims.

22. A memory medium comprising program instructions that, when executed, cause a device to implement a method according to any of the preceding claims.

23. A computer program comprising instructions for performing any of the methods of the preceding claims.

24. An apparatus comprising means for performing any of the method elements of any of the preceding claims.

25. A method that includes any action or combination of actions as substantially described herein in the Detailed Description and claims.

26. A method as substantially described herein with reference to each or any combination of the Figures contained herein, with reference to each or any combination of paragraphs in the Detailed Description, with reference to each or any combination of Figures and/or Detailed Description, or with reference to each or any combination of the claims.

27. A wireless device configured to perform any action or combination of actions as substantially described herein in the Detailed Description, Figures, and/or claims.

28. A wireless device that includes any component or combination of components as described herein in the Detailed Description and/or Figures as included in a wireless device.

29. A non-volatile computer-readable medium that stores instructions that, when executed, cause the performance of any action or combination of actions as substantially described herein in the Detailed Description and/or Figures.

30. An integrated circuit configured to perform any action or combination of actions as substantially described herein in the Detailed Description and/or Figures.

31. A mobile station configured to perform any action or combination of actions as substantially described herein in the Detailed Description and/or Figures.

32. A mobile station that includes any component or combination of components as described herein in the Detailed Description and/or Figures as included in a mobile station.

33. A mobile device configured to perform any action or combination of actions as substantially described herein in the Detailed Description and/or Figures.

34. A mobile device that includes any component or combination of components as described herein in the Detailed Description and/or Figures as included in a mobile device.

35. A network node configured to perform any action or combination of actions as substantially described herein in the Detailed Description and/or Figures.

36. A network node that includes any component or combination of components as described herein in the Detailed Description and/or Figures as included in a mobile device.

37. A base station configured to perform any action or combination of actions as substantially described herein in the Detailed Description and/or Figures.

38. A base station that includes any component or combination of components as described herein in the Detailed Description and/or Figures as included in a mobile device.

39. A 5G NR network node or base station configured to perform any action or combination of actions as substantially described herein in the Detailed Description and/or Figures.

40. A 5G NR network node or base station that includes any component or combination of components as described herein in the Detailed Description and/or Figures as included in a mobile device.