FR2 UL gap configuration

Abstract

The present disclosure relates to FR2 UL gap configuration. The present invention provides apparatuses and associated configuration methods for FR2 UL gap configuration. In one aspect, dedicated radio resource control (RRC) signaling is used to configure a UL gap by transmission. The UL gap configuration can indicate a reference cell to determine a UL gap pattern for a multi-radio dual connectivity (MR-DC) configuration. The UL gap configuration can indicate a system frame number (SFN) and a subframe of the reference cell to use for calculating the UL gap pattern. The reference cell can be selected from a list of cells including FR1 cells, or can be limited to FR2 cells.

Description

Technical Field

[0001] This invention relates to wireless data transmission technology and to high-frequency band transmission configuration. Background Technology

[0002] Wireless communication networks can include user equipment (UEs) (e.g., smartphones, tablets, etc.) capable of communicating with base stations and other network nodes. Aspects of wireless communication networks include the methods, conditions, scenarios, and processes by which wireless devices connect to each other and otherwise communicate with one another. This may involve issues related to how wireless devices synchronize and how transmission time slots are reserved for various measurements. Attached Figure Description

[0003] Figure 1 A block diagram illustrating the architecture of a wireless system according to some aspects is shown, the wireless system including user equipment (UE) communicating with a base station (BS) via an uplink (UL) gap pattern.

[0004] Figure 2 An example of a time slot configuration including a UL gap pattern is shown, based on several aspects.

[0005] Figure 3 Another example of a time slot configuration including a UL gap pattern is shown, based on several aspects.

[0006] Figure 4 Several tabular diagrams illustrating a list of UL gap pattern parameters are shown.

[0007] Figure 5 A diagram illustrating an exemplary definition of a UL gap configuration based on some aspects of an RRC message is shown.

[0008] Figure 6 A flowchart illustrating a method for configuring UL gaps for a UE based on some aspects using RRC messages is shown.

[0009] Figure 7 A tabular diagram illustrating the coordination of the primary node (MN) and secondary node (SN) for gap configuration is shown.

[0010] Figure 8 A diagram illustrating exemplary components of a device that can be used according to some aspects is shown.

[0011] Figure 9 A diagram illustrating an exemplary interface of a baseband circuit that may be adopted according to some aspects is shown. Detailed Implementation

[0012] This disclosure is described with reference to the accompanying drawings. Similar reference numerals are used throughout to indicate similar elements. The drawings are not drawn to scale and are provided solely for illustrative purposes. Several aspects of this disclosure are described below with reference to exemplary applications for illustration. Numerous specific details, relationships, and methods are set forth to provide an understanding of this disclosure. This disclosure is not limited to the order of the illustrated actions or events, as some actions may occur in a different order and / or simultaneously with other actions or events. Furthermore, not all illustrated actions or events are necessary to implement the methods chosen according to this disclosure.

[0013] Enhancements to Frequency Range 2 (FR2) coverage are of interest, including improvements in signal quality, power efficiency, and overall system throughput in wireless communication systems. Various FR2 enhancements rely on or benefit from the use of uplink (UL) gaps. A UL gap can represent one or more UL time slots during which UL data transmission is paused to perform additional measurements using the hardware used for UL data transmission. For example, as explained in more detail below, FR2 transmit power management can be performed using UL gaps because it uses an FR2 transceiver for proximity sensing and therefore cannot be performed concurrently with UL data transmission.

[0014] In view of the foregoing, this disclosure relates to apparatus and associated configuration methods for FR2 UL gap configuration. In one aspect, dedicated radio resource control (RRC) signaling is used to configure the UL gap via transmission. This UL gap configuration may instruct a reference cell to determine a UL gap pattern for a multiple radio dual connectivity (MR-DC) configuration. The UL gap configuration may instruct the system frame number (SFN) and subframe of the reference cell used to calculate the UL gap pattern. The reference cell may be selected from a list of cells including FR1 cells, or may be limited to FR2 cells.

[0015] In one aspect, the UL gap configuration also indicates the UL gap length (UGL), UL gap repetition period (UGRP), and UL gap offset to determine the UL gap pattern. The UGL and UGRP can be represented by a UL gap pattern ID. Alternatively, the UGL and UGRP can be represented by bits representing the UGL and UGRP respectively. In some other alternative aspects, the UL gap length, UL gap repetition period, and UL gap offset are provided by different sources, for example, by dynamic scheduling using downlink control information (DCI) or by public or private time-division duplex (TDD) uplink / downlink configuration.

[0016] In one aspect, the UL gap configuration also indicates support for each FR gap, where FR1 data transmission continues during the UL gap. In another aspect, the UL gap is independent of the measurement gap, such that when the indicated measurement gap overlaps with the UL gap, user equipment (UE) measurements continue through the internal loop.

[0017] Figure 1 A block diagram illustrating the architecture of a wireless system 100 according to some aspects is shown, the wireless system including a UE 101 communicating with a base station (BS) 111 using an uplink (UL) gap pattern. The following description is provided in conjunction with 5G or NR system standards provided by 3GPP technical specifications. However, the exemplary aspects are not limited in this regard, and said aspects can be applied to other networks that benefit from the principles described herein, such as other 3GPP systems (e.g., fourth-generation (4G) or sixth-generation (6G)) systems, IEEE 802.16 protocols (e.g., WMAN, WiMAX, etc.), etc.

[0018] like Figure 1 As shown, the wireless system 100 includes UE 101a and UE 101b (collectively, "UE 101"). UE 101 can be configured to connect to a radio access network (RAN) 110 via connections (or channels) 102 and 104, which respectively include physical communication channels / interfaces, for example, through communication ground coupling. RAN 110 may include one or more RAN nodes that enable connections 102 and 104, including base stations (BS) 111a and 111b (collectively, "BS 111").

[0019] In some respects, UE 101 can use FR2 UL gaps to perform FR2 transmit power management, during which regular uplink data transmission is suspended. For example, UE 101 can selectively apply additional power management maximum power reduction (P-MPR) or a duty cycle compliant with 5G FR2 cellular radio regulations only when a human target is in a location that could cause significant RF exposure to the directional beam 144, thus improving overall system throughput. The presence or absence of a human target approaching the radiating FR2 antenna panel 142 can be detected using a body proximity sensor. Since the body proximity sensor may not be able to operate simultaneously with the 5G NR FR2 transceiver, the FR2 UL gap needs to be created and configured to allow body proximity detection. As will be described in more detail below, a sensing gap / slot is configured between the regular DL and UL slots to determine the UL gap pattern.

[0020] UE 101 is shown as a smartphone (e.g., a handheld touchscreen mobile computing device that can connect to one or more cellular networks), but may include any mobile or non-mobile computing device, such as consumer electronics devices including headsets, handheld devices, cellular phones, smartphones, feature phones, tablets, wearable computing devices, personal digital assistants (PDAs), pagers, wireless handheld devices, desktop computers, laptops, in-vehicle infotainment (IVI), in-vehicle entertainment (ICE) devices, instrument cluster (IC), head-up display (HUD) devices, on-board diagnostic (OBD) devices, dashboard mobile equipment (DME), mobile data terminal (MDT), electronic engine management system (EEMS), electronic / engine control unit (ECU), electronic / engine control module (ECM), embedded systems, microcontrollers, control modules, engine management system (EMS), connected or “smart” appliances, machine-type communication (MTC) devices, machine-to-machine (M2M) devices, Internet of Things (IoT) devices, etc.

[0021] In some aspects, RAN 110 can be a next-generation (NG) RAN or a 5G RAN, an evolved-UMTS terrestrial RAN (E-UTRAN), or a legacy RAN such as UTRAN or GERAN. As used herein, the term "NG RAN," etc., can refer to RAN 110 operating in an NR or 5G radio system, and the term "E-UTRAN," etc., can refer to RAN 110 operating in a Long Term Evolution (LTE) or 4G system. In this example, connection 102 and connection 104 are shown as air interfaces for communication coupling and can be consistent with cellular communication protocols such as the Global System for Mobile Communications (GSM) protocol, Code Division Multiple Access (CDMA) network protocol, Push-to-Talk (PTT) protocol, Cellular PTT (POC) protocol, Universal Mobile Telecommunications System (UMTS) protocol, 3GPP LTE protocol, 5G protocol, NR protocol, and / or any of the other communication protocols discussed herein. In this aspect, UE 101 can directly exchange communication data via ProSe interface 105. ProSe interface 105 may alternatively be referred to as SL interface 105 and may include one or more logical channels, including but not limited to Physical Side Link Control Channel (PSCCH), Physical Side Link Shared Channel (PSSCH), Physical Side Link Discovery Channel (PSDCH), and Physical Side Link Broadcast Channel (PSBCH).

[0022] BSs 111a and 111b can be configured to communicate with each other via interface 112. In specific implementations where the system is a 5G or NR system, interface 112 can be an Xn interface 112. The Xn interface is defined between two or more BSs 111. In some implementations, the Xn interface may include an Xn user plane (Xn-U) interface and an Xn control plane (Xn-C) interface. Xn-U provides non-guaranteed delivery of user plane PDUs and supports / provides data forwarding and flow control functions. Xn-C provides management and error handling functions for managing the functionality of the Xn-C interface; mobility support for UE 101 in connected modes (e.g., CM-CONNECTED) includes functions for managing UE mobility in connected modes between one or more BSs 111. As used herein, the terms "access node," "access point," etc., can describe equipment that provides radio baseband functionality for data and / or voice connections between the network and one or more users. These BSs may be referred to as access nodes, gNBs, RAN nodes, eNBs, Node Bs, RSUs, Transmit / Receive Points (TRxPs), or TRPs, and may include ground stations (e.g., terrestrial access points) or satellite stations that provide coverage within a geographic area (e.g., a cell). Depending on the aspects, BS 111 may be implemented as one or more dedicated physical devices such as macrocell base stations and / or low-power (LP) base stations, which are used to provide femtocells, picocells, or other similar cells with smaller coverage areas, smaller user capacity, or higher bandwidth compared to macrocells.

[0023] RAN 110 is communicatively coupled to core network (CN) 120. CN 120 may include multiple network elements 122 configured to provide various data and telecommunications services to customers / subscribers (e.g., users of UE 101) connected to CN 120 via RAN 110. In various embodiments, when CN 120 is an EPC, RAN 110 may be connected to CN 120 via S1 interface 113. In an implementation, S1 interface 113 may be divided into two parts: an S1 user plane (S1-U) interface 114, which carries traffic data between BS 111 and S-GW; and an S1-MME interface 115, which is the signaling interface between BS 111 and MME.

[0024] Application server 130 may be an element providing IP-bearing resources for applications using CN 120 via Internet Protocol (IP) interface 127 (e.g., Universal Mobile Telecommunications System Packet Service (UMTS PS) domain, LTE PS data service, etc.). Application server 130 may also be configured to support one or more communication services for UE 101 via CN 120 (e.g., VoIP sessions, PTT sessions, group communication sessions, social networking services, etc.). Application server 130 may signal to CN 120 to indicate new service flows and select appropriate QoS and charging parameters using appropriate Traffic Flow Templates (TFTs) and QoS Class Identifiers (QCIs), which initiates the QoS and charging specified by application server 130.

[0025] As the number of mobile devices within wireless networks and the demand for mobile data traffic continue to increase, system requirements and architectures are being modified to increase communication capacity and speed. One aspect of such modifications may include dual connectivity (DC), where a secondary node (SN) provides additional resources to UE 101, while a primary node (MN) provides control plane connectivity to the core network. UE 101 can be configured with DC as multiple RAT or multiple radio dual connectivity (MR-DC), where a UE with multiple Rx / Tx capabilities can be configured to utilize resources provided by two different nodes capable of providing backhaul connections via non-ideal connections; for example, one node provides NR access, and the other provides E-UTRA for LTE or NR access for 5G. MN and SN may be connected via network interfaces, and at least MN is connected to CN 120. At least one of MN and / or SN may operate using shared spectrum channel access. All functions specified for UE 101 are available for Integrated Access and Backhaul Mobile Terminal (IAB-MT). Similar to UE101, IAB-MT can access the network using one network node or two different nodes with EN-DC, NR-DC, or similar architectures. NR-DC is the DC configuration used in 5G NR networks, where both MN and SN are 5G gNBs. In EN-DC (EutranNR Dual Connectivity), LTE becomes the MCG (Primary Cell Group), and NR becomes the SCG (Secondary Cell Group).

[0026] In MR-DC, a group of serving cells associated with the primary node can be configured as a primary cell group (MCG), including a special cell (SpCell) as the primary cell (PCell) and optionally one or more secondary cells (SCells). The MCG can be a radio access node providing control plane connectivity to the core network (CN) 120; for example, the MCG can be a primary eNB (in EN-DC), a primary ng-eNB (in NGEN-DC), or a primary gNB (in NR-DC and NE-DC). The SCG in MR-DC can be a group of serving cells associated with the SN, including a SpCell as the PSCell and optionally one or more SCells. Therefore, depending on whether the MAC entity is associated with an MCG or a second cell group (SCG), the SpCell can refer to either the PCell of the MCG or the primary / secondary cell (PSCell) of the SCG.

[0027] Figure 2 An example of a time slot configuration 200 including an uplink (UL) gap pattern 202 (202-1, 202-2) is shown, based on several aspects. The UL gap pattern 202 includes parameters such as the UL gap length (UGL), the UL repetition period (ULRP), and the UL gap offset (ULGapOffset). ULGapOffset is the offset of the UL gap pattern 202 from the start of the reference ULRP. ULRP is the gap repetition period of the UL gap pattern 202. UGL is the gap length of the UL gap pattern 202. Figure 2 The slot configuration 200 uses an example parameter set with 80 slots in a radio frame and a subcarrier space (SCS) of 120 kHz, but other parameter sets can also be modified by applying the same method.

[0028] like Figure 2 In the example shown, radio frames SFN X, SFN X+1, and SFN X+2 are 10 ms and 80 batches, respectively. In one aspect, the UL gap pattern 202 includes multiple aggregated UL gap time slots. The ULRP can be less than, equal to, or greater than the length of the radio frame. Here, for example, the ULRP could be 20 ms and 160 batches across two radio frames. The ULRP can be an integer multiple of the radio frame period. The first time slot of the UL gap immediately follows the ULGapOffset. The UL gap has a UGL length comprising one or more consecutive time slots, in the example 1 ms and 8 time slots.

[0029] Figure 3 Another example of a time slot configuration 300 including uplink (UL) gap patterns 302 (302-1, 302-2, 302-3) is shown, based on several aspects. The parameters of the UL gap pattern 302 are similar to those described above. Figure 2 The UL gap pattern 202 describes this. In one aspect, the ULRP can be relatively small, for example, smaller than the length of the radio frame, and the UL gap slots can even be distributed across different locations within a single radio frame. Therefore, the impact of the UL gap on uplink data transmission can be reduced. The ULRP can be an integer multiple of the radio frame period. Figure 3 In the example shown, radio frame SFN X is 10ms and has 80 batches. ULRP can be 2.5ms and has 20 batches, and can include 4 UL gaps within radio frame SFN X. The first slot of the UL gap immediately follows ULGapOffset. The UL gap has a UGL length, comprising one or more consecutive slots, which in the example is 0.125ms and 1 slot.

[0030] Figure 4 Several tables, 400A to 400D, illustrate a list of UL gap pattern parameters. As shown in tables 400A to 400C, multiple UL gap pattern IDs are used to represent multiple combinations of UGL and ULRP. As shown in table 400D, UGL and ULRP can be indicated by data bits respectively. A first number of bits represents a set of UGLs, and a second number of bits represents a set of ULRPs. The first and second amounts can be different or the same. By having different numbers of bits for UGL and ULRP, resources are conserved, and flexibility in bit allocation is increased.

[0031] As shown in Table 400A, in one aspect, ID 0 represents a 1ms UGL and a 20ms ULRP; ID 1 represents a 1ms UGL and a 40ms ULRP; ID 2 represents a 1ms UGL and an 80ms ULRP; ID 3 represents a 1ms UGL and a 160ms ULRP; ID 4 represents a 0.125ms UGL and a 2.5ms ULRP; ID 5 represents a 0.125ms UGL and a 5ms ULRP; ID 6 represents a 0.125ms UGL and a 10ms ULRP; and ID 7 represents a 0.125ms UGL and a 20ms ULRP. IDs 0 to 3 are used for clustered UL gap patterns, where the UL gaps have relatively long UGLs and relatively long ULRPs (e.g., multiple slots of a consecutive UL gap). IDs 4 to 7 are used for distributed UL gap patterns, where the UL gaps have relatively short UGLs and relatively short ULRPs (e.g., multiple UL gaps within a radio frame).

[0032] As shown in Table 400B, on the other hand, ID 0 represents 1 ms of UGL and 40 ms of ULRP; ID 1 represents 0.125 ms of UGL and 5 ms of ULRP; ID 2 represents 0.5 ms of UGL and 40 ms of ULRP, or 0.125 ms of UGL and 10 ms of ULRP; and ID 3 represents 0.125 ms of UGL and 20 ms of ULRP. The UL gap patterns of ID 0 and ID 1 have an overhead of 2.5%, where the overhead is defined as the UGL / ULRP ratio. The UL gap pattern of ID 1 has an overhead of 1.25%. The UL gap pattern of ID 2 has an overhead of 0.625%.

[0033] As shown in Table 400C, on the other hand, ID 0 represents a 1ms UGL and a 40ms ULRP with an overhead of 2.5%, and ID 1 represents a 0.125ms UGL and a 10ms ULRP with an overhead of 1.25%.

[0034] As shown in Table 400D, alternatively, 1 bit can be used to indicate a UGL of 1 ms or 0.125 ms. 3 bits can be used to indicate a ULRP of 5 ms, 10 ms, 20 ms, 40 ms, 80 ms, or 160 ms. Although not shown in the attached figures, different UGL, ULRP options and different bits can be used, such as 1 bit for UGL and 2 bits for ULRP, or 1 bit for UGL and 1 bit for ULRP. In one aspect, the number of bits representing UGL can be the same as the number of bits representing ULRP. Alternatively, the number of bits representing UGL can be different, such as less than the number of bits representing ULRP.

[0035] Figure 5 Figure 500 illustrates an exemplary definition of the UL gap configuration based on some aspects of the RRC message. In one aspect, this is achieved by means of BS 111 to UE 101 (reference...). Figure 1 The dedicated radio resource control (RRC) signaling is used to configure the UL gap. Figure 6 The diagram illustrates the configuration of RRC messages from BS 111 to UE 101 based on several aspects (reference). Figure 1 Flowchart 600 of the method for UL gap.

[0036] like Figure 5 and Figure 6As shown in action 602, the UE can receive the field or information element (IE) ULGapConfig from the BS and use it for UL gap configuration. In multi-radio dual-connectivity (MR-DC) configurations, such as EN-DC, NE-DC, or NR-DC, the IE ULGapConfig can indicate the reference cell used to determine the UL gap pattern based on the timing and parameter set of the reference cell. In some aspects, the reference cell can be a PCell or PSCell in various frequency ranges, such as FR1 and FR2. FR1 refers to the frequency band from 4.1 GHz to 7.125 GHz. FR2 refers to the frequency band from 24.25 GHz to 52.6 GHz.

[0037] like Figure 5 and Figure 6 As shown in actions 604 and 606, the reference cell indication parameter refServCellIndication_ULGap is checked and used to configure the reference cell (if it exists). The reference cell indication parameter refServCellIndication_ULGap can indicate the selection of a reference cell from the PCell or PSCell, or alternatively, indicate that the reference cell should be restricted to an FR2 cell. For NE-DC and NR-DC, the reference cell is limited to an FR2 cell of the MCG. The system frame number (SFN) and subframe of the reference cell can be used to determine the UL gap pattern. This may allow an FR1 cell to be used for timing reference.

[0038] like Figure 5 and Figure 6 As shown in actions 604 and 610, if the reference cell indication parameter refServCellIndication_ULGap does not indicate a specific reference cell, but rather indicates that the reference cell is limited to FR2 cells, and in the case of asynchronous carrier aggregation (CA) in FR2, in some respects, the FR2 asynchronous reference cell indication parameter refFR2ServCellAsyncCA_ULGap can indicate the reference cell index as the reference cell ID indicating the reference cell used to determine the UL gap pattern.

[0039] like Figure 6 As shown in actions 604 and 608, if the reference cell indication parameter refServCellIndication_ULGap does not indicate a specific reference cell, but rather indicates that the reference cell is limited to FR2 cells, and in the case of synchronized CA in FR2, the UL gap pattern can be determined using the SFN and subframe of any cell in FR2.

[0040] In some alternative aspects, for simplicity, the reference cell can be hardcoded to be limited to FR2 cells, rather than cells in lower frequency ranges such as FR1. There is no refServCellIndication_ULGap in the UL gap RRC configuration itself. Only refFR2ServCellAsyncCA_ULGap is signaled, indicating the reference cell index of the FR2 reference cell used to determine the UL gap pattern. In the case of asynchronous CA in FR2, the reference cell can be configured by the FR2 asynchronous reference cell indication parameter refFR2ServCellAsyncCA_ULGap. Alternatively, a PSCell can be used as the reference cell. The system frame number (SFN) and subframe of the reference cell are used to determine the UL gap pattern. In the case of synchronous CA in FR2, the reference cell is not configured by IE ULGapConfig, and the SFN and subframe of any cell in FR2 can be used to determine the UL gap pattern.

[0041] like Figure 5 As shown, in some aspects, ULGapConfig may include configurations of ULGapOffset, UGL, and ULRP. ULGapOffset may be in the range of 0 to ULRP-1. UGL and ULRP may be indicated by individual bits or by the UL gap pattern ID as described above. In some alternative aspects, the UL gap pattern may be derived from a static uplink timeslot of a Time Division Duplex (TDD) uplink / downlink configuration, such as the TDD UL / DL configuration common message TDD-UL-DL-ConfigurationCommon and the TDD UL / DL configuration dedicated message TDD-UL-DL-ConfigurationDedicated, which have the same reference cell or reference cell index indication as ULGapConfig.

[0042] like Figure 6 As shown in action 612, in some aspects, the UE suspends UL data transmission on the FR2 cell and performs FR2 transmission power management during the UL gap. For example, the UE can use a body proximity sensor to perform body proximity sensing to detect the presence or absence of a human target approaching the radiating FR2 antenna panel. Then, only when the human target is in a location that could cause significant RF exposure to the directional beam, the UE can selectively apply additional power management maximum power reduction (P-MPR) or a duty cycle compliant with 5G FR2 cellular radio regulations, and thus improve overall system throughput.

[0043] In one aspect, the UE is configured to support UL gap capability independent of measurement gap capability. Thus, when the measurement gap overlaps with the UL gap, UE measurements continue through the internal loop. UE measurements may include Synchronization Signal-Reference Signal Received Power (SS-RSRP), Synchronization Signal-Reference Signal Received Quality (SS-RSRQ), Synchronization Signal-Signal Pair Interference and Noise Ratio (SS-SINR), Channel State Information-Reference Signal Received Power (CSI-RSRP), CSI-RSRQ, CSI-SINR, or other application-specific UE measurements.

[0044] On the other hand, the UE capability report indicates support for each FR gap, where data transmission and reception in FR1 or another frequency range continue during the UL gap in FR2. The UE stops uplink data transmission on all FR2 cells during the UL gap. Alternatively, the UL gap is configured by the network entity that supports or configures FR2 communication, simplifying coordination with other network entities and UE evaluation. For example, for EN-DC, the secondary NR node configures the UL gap.

[0045] Figure 7 Figure 700 illustrates a table illustrating primary node (MN)-secondary node (SN) coordination for UL gap configuration based on several aspects. In one aspect, the UE capability report indicates each UE gap where data transmission and reception in FR1 or another frequency range are also affected during the UL gap in FR2. In this case, the UE can share some components between FR2 and FR1 or another frequency range, and the UE-specific implementation architecture is integrated. However, the MN and SN need to coordinate on the network side to align the future autonomous node's UL gap configuration with the SN, especially when the SN is responsible for measuring the FR2 gap configuration.

[0046] like Figure 7 As shown, for each UE gap in EN-DC, the MN is responsible for UL gap configuration. The SN should send the FR1 / FR2 measurement frequency list configured by the SN and the UL gap pattern request to the MN. The MN should send gap pattern information, including the UL gap pattern, to the SN through the per-UE gap configuration.

[0047] For NE-DC and NR-DC, the MN is responsible for configuring the UL gap for each UE gap and each FR gap. Where applicable, the SN should send the SN-configured list of FR1 / FR2 measurement frequencies and a UL gap pattern request to the MN, especially if the SN has configured the UE with the FR2 band. If the UE only supports per-UE gaps, the MN should ensure that the UL gap pattern is included and sent to the SN.

[0048] Figure 8The diagram illustrates exemplary components of a device 800 that may be adopted according to some aspects. In some embodiments, device 800 may include application circuitry 802, baseband circuitry 804, radio frequency (RF) circuitry 806, front-end module (FEM) circuitry 808, one or more antennas 810, and power management circuitry (PMC) 812 (at least coupled together as shown). Components of the illustrated device 800 may be included in a UE or RAN node. In some embodiments, device 800 may include fewer components (e.g., the RAN node may not utilize application circuitry 802, but instead include a processor / controller to process IP data received from the CN). In some embodiments, device 800 may include additional components such as, for example, memory / storage devices, displays, cameras, sensors (including one or more temperature sensors, such as a single temperature sensor, multiple temperature sensors at different locations in device 800, etc.), or input / output (I / O) interfaces. In other implementations, the following components may be included in more than one device (e.g., the circuit may be included separately in more than one device for a cloud-RAN (C-RAN) implementation).

[0049] Application circuitry 802 may include one or more application processors. For example, application circuitry 802 may include circuitry such as, but not limited to, one or more single-core or multi-core processors. The processor may include any combination of general-purpose processors and special-purpose processors (e.g., graphics processors, application processors, etc.). The processor may be coupled to or may include a memory / storage device and may be configured to execute instructions stored in the memory / storage device to enable various applications or operating systems to run on device 800. In some specific implementations, the processor of application circuitry 802 may process IP data packets received from the Evolved Packet Core (EPC).

[0050] Baseband circuit 804 may include circuitry such as, but not limited to, one or more single-core or multi-core processors. Baseband circuit 804 may include one or more baseband processors or control logic components to process baseband signals received from the receive signal path of RF circuit 806 and to generate baseband signals for the transmit signal path of RF circuit 806. Baseband circuit 804 may interact with application circuitry 802 to generate and process baseband signals and control the operation of RF circuit 806. For example, in some implementations, baseband circuit 804 may include a third-generation (3G) baseband processor 804A, a fourth-generation (4G) baseband processor 804B, a fifth-generation (5G) baseband processor 804C, or other existing, under development, or future generations (e.g., second-generation (2G), sixth-generation (6G), etc.) baseband processors 804D. Baseband circuitry 804 (e.g., one or more baseband processors 804A-804D) can handle various radio control functions that can communicate with one or more radio networks via RF circuitry 806. In other embodiments, some or all of the functions of baseband processors 804A-D may be included in modules stored in memory 804G and executed via central processing unit (CPU) 804E. Radio control functions may include, but are not limited to, signal modulation / demodulation, encoding / decoding, RF shifting, etc. In some embodiments, the modulation / demodulation circuitry of baseband circuitry 804 may include Fast Fourier Transform (FFT), precoding, or constellation mapping / demapping functions. In some embodiments, the encoding / decoding circuitry of baseband circuitry 804 may include convolution, tail-biting convolution, turbo, Viterbi, or low-density parity-check (LDPC) encoder / decoder functions. Specific implementations of modulation / demodulation and encoder / decoder functions are not limited to these examples and may include other suitable functions in other respects.

[0051] In some embodiments, the baseband circuit 804 may include one or more audio digital signal processors (DSPs) 804F. The audio DSP 804F may include elements for compression / decompression and echo cancellation, and in other embodiments may include other suitable processing elements. In some embodiments, components of the baseband circuit may be suitably combined in a single chip, a single chipset, or disposed on the same circuit board. In some embodiments, some or all components of the baseband circuit 804 and the application circuit 802 may be implemented together, for example, on a system-on-a-chip (SoC).

[0052] In some implementations, baseband circuit 804 can provide communication compatible with one or more radio technologies. For example, in some implementations, baseband circuit 804 can support communication with NG-RAN, Evolved Universal Terrestrial Radio Access Network (EUTRAN), or other Wireless Metropolitan Area Networks (WMAN), Wireless Local Area Networks (WLAN), Wireless Personal Area Networks (WPAN), etc. Implementations of baseband circuit 804 configured to support radio communication with more than one radio protocol may be referred to as multimode baseband circuits.

[0053] RF circuit 806 enables communication with a wireless network via a non-solid medium using modulated electromagnetic radiation. In various implementations, RF circuit 806 may include switches, filters, amplifiers, etc., to facilitate communication with the wireless network. RF circuit 806 may include a receive signal path, which may include circuitry for down-converting the RF signal received from FEM circuit 808 and providing a baseband signal to baseband circuit 804. RF circuit 806 may also include a transmit signal path, which may include circuitry for up-converting the baseband signal provided by baseband circuit 804 and providing an RF output signal to FEM circuit 808 for transmission.

[0054] In some embodiments, the receive signal path of RF circuit 806 may include mixer circuit 806a, amplifier circuit 806b, and filter circuit 806c. In some embodiments, the transmit signal path of RF circuit 806 may include filter circuit 806c and mixer circuit 806a. RF circuit 806 may also include synthesizer circuit 806d for synthesizing the frequency used by mixer circuit 806a in both the receive and transmit signal paths. In some embodiments, mixer circuit 806a in the receive signal path may be configured to down-convert the RF signal received from FEM circuit 808 based on the synthesized frequency provided by synthesizer circuit 806d. Amplifier circuit 806b may be configured to amplify the down-converted signal, and filter circuit 806c may be a low-pass filter (LPF) or band-pass filter (BPF) configured to remove unwanted signals from the down-converted signal to generate an output baseband signal. The output baseband signal may be provided to baseband circuit 804 for further processing. In some implementations, the output baseband signal may be a zero-frequency baseband signal, but this is not required. In some implementations, the mixer circuit 806a in the receiving signal path may include a passive mixer, but the scope of implementation is not limited in this respect.

[0055] In some implementations, the mixer circuit 806a of the transmission signal path can be configured to up-convert the input baseband signal based on the synthesis frequency provided by the synthesizer circuit 806d to generate an RF output signal for the FEM circuit 808. The baseband signal can be provided by the baseband circuit 804 and can be filtered by the filter circuit 806c.

[0056] In some embodiments, the mixer circuit 806a for the receive signal path and the mixer circuit 806a for the transmit signal path may include two or more mixers, and may be arranged for quadrature down-conversion and up-conversion, respectively. In some embodiments, the mixer circuit 806a for the receive signal path and the mixer circuit 806a for the transmit signal path may include two or more mixers, and may be arranged for image suppression (e.g., Hartley image suppression). In some embodiments, the mixer circuit 806a for the receive signal path and the mixer circuit 806a for the transmit signal path may be arranged for direct down-conversion and direct up-conversion, respectively. In some embodiments, the mixer circuit 806a for the receive signal path and the mixer circuit 806a for the transmit signal path may be configured for superheterodyne operation.

[0057] In some embodiments, the output baseband signal and the input baseband signal may be analog baseband signals, although the scope of embodiments is not limited in this respect. In some alternative embodiments, the output baseband signal and the input baseband signal may be digital baseband signals. In these alternative embodiments, RF circuit 806 may include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuitry, and baseband circuit 804 may include a digital baseband interface for communication with RF circuit 806.

[0058] In some dual-mode implementations, separate radio IC circuits can be provided to process signals for each spectrum, but the scope of implementations is not limited in this respect.

[0059] In some specific implementations, synthesizer circuit 806d can be a fractional-N synthesizer or a fractional-N / N+1 synthesizer, but the scope of implementation is not limited in this respect, as other types of frequency synthesizers may also be suitable. For example, synthesizer circuit 806d can be a Δ-∑ synthesizer, a frequency multiplier, or a synthesizer including a phase-locked loop with a frequency divider.

[0060] Synthesizer circuit 806d can be configured to synthesize an output frequency based on the frequency input and the divider control input for use by mixer circuit 806a of RF circuit 806. In some specific implementations, synthesizer circuit 806d can be a fractional N / N+1 synthesizer.

[0061] In some implementations, the frequency input may be provided by a voltage-controlled oscillator (VCO), although this is not mandatory. The divider control input may be provided by the baseband circuit 804 or the application circuit 802 according to the desired output frequency. In some implementations, the divider control input (e.g., N) may be determined from a lookup table based on the channel indicated by the application circuit 802.

[0062] The synthesizer circuit 806d of the RF circuit 806 may include a frequency divider, a delay-locked loop (DLL), a multiplexer, and a phase accumulator. In some embodiments, the frequency divider may be a dual-mode divider (DMD), and the phase accumulator may be a digital phase accumulator (DPA). In some embodiments, the DMD may be configured to divide the input signal by N or N+1 (e.g., based on carry output) to provide a fractional division ratio. In some exemplary embodiments, the DLL may include a cascaded, tunable delay element, a phase detector, a charge pump, and a set of D-type flip-flops. In these embodiments, the delay elements may be configured to divide the VCO period into Nd equal phase groups, where Nd is the number of delay elements in the delay line. Thus, the DLL provides negative feedback to help ensure that the total delay through the delay line is one VCO period.

[0063] In some embodiments, synthesizer circuit 806d may be configured to generate a carrier frequency as the output frequency, while in other embodiments, the output frequency may be a multiple of the carrier frequency (e.g., twice the carrier frequency, four times the carrier frequency) and may be used in conjunction with quadrature generator and frequency divider circuitry to generate multiple signals having multiple different phases relative to each other at that carrier frequency. In some embodiments, the output frequency may be the LO frequency (fLO). In some embodiments, RF circuit 806 may include an IQ / polarity converter.

[0064] FEM circuit 808 may include a receive signal path, which may include circuitry configured to operate on RF signals received from one or more antennas 56, amplify the received signals, and provide an amplified version of the received signals to RF circuit 806 for further processing. FEM circuit 808 may also include a transmit signal path, which may include circuitry configured to amplify signals provided by RF circuit 806 for transmission through one or more of the one or more antennas 56. In various specific embodiments, amplification via the transmit or receive signal path may be performed only in RF circuit 806, only in FEM circuit 808, or in both RF circuit 806 and FEM circuit 808.

[0065] In some implementations, FEM circuit 808 may include a TX / RX switch to switch between transmit mode operation and receive mode operation. The FEM circuit may include a receive signal path and a transmit signal path. The receive signal path of the FEM circuit may include an LNA to amplify the received RF signal and provide the amplified received RF signal as an output (e.g., provided to RF circuit 806). The transmit signal path of FEM circuit 808 may include a power amplifier (PA) for amplifying the input RF signal (e.g., provided by RF circuit 806); and one or more filters for generating an RF signal for subsequent transmission (e.g., through one or more antennas of one or more antennas 56).

[0066] In some implementations, the PMC 812 can manage the power supplied to the baseband circuitry 804. Specifically, the PMC 812 can control power selection, voltage scaling, battery charging, or DC-DC conversion. The PMC 812 is typically included when the device 800 can be powered by a battery, for example, when the device is included in a UE. The PMC 812 can improve power conversion efficiency while providing the desired implementation size and thermal characteristics.

[0067] and Figure 8 The PMC 812 is shown coupled only to the baseband circuit 804. However, in other specific implementations, the PMC 812 may be additionally or alternatively coupled to other components (such as, but not limited to, application circuit 802, RF circuit 806, or FEM 808) and perform similar power management operations for those other components.

[0068] In some implementations, the PMC 812 can control various power-saving mechanisms of device 800, or otherwise become part of those mechanisms. For example, if device 800 is in the RRC_Connected state, where it remains connected to the RAN node because it expects to receive traffic immediately, it can enter a state called Discontinuous Receive Mode (DRX) after a period of inactivity. During this state, device 800 can be powered down for short intervals, thus saving power.

[0069] If there is no data traffic activity during the extended period, device 800 may transition to the RRC_Idle state, in which the device disconnects from the network and does not perform operations such as channel quality feedback or handover. Device 800 enters a very low power state and performs paging, in which the device periodically wakes up again to listen to the network, and then powers off again. Device 800 may not receive data in this state; to receive data, the device may transition back to the RRC_Connected state.

[0070] An additional power-saving mode allows the device to be unavailable from the network for periods exceeding the paging interval (ranging from seconds to hours). During this time, the device is completely unconnected to the network and can be completely powered off. Any data sent during this period will incur significant latency, which is assumed to be acceptable.

[0071] The processors of application circuit 802 and baseband circuit 804 are elements that can be used to execute one or more instances of a protocol stack. For example, the processor of baseband circuit 804 can be used alone or in combination to perform Layer 3, Layer 2, or Layer 1 functions, and the processor of baseband circuit 804 can utilize data received from these layers (e.g., packet data) and further perform Layer 4 functions (e.g., Transport Communication Protocol (TCP) and User Datagram Protocol (UDP) layers). As mentioned herein, Layer 3 may include the Radio Resource Control (RRC) layer, which will be described in further detail below. As mentioned herein, Layer 2 may include the Media Access Control (MAC) layer, the Radio Link Control (RLC) layer, and the Packet Data Convergence Protocol (PDCP) layer, which will be described in further detail below. As mentioned herein, Layer 1 may include the Physical (PHY) layer of the UE / RAN node, which will be described in further detail below.

[0072] Figure 9 A diagram illustrating an exemplary interface of a baseband circuit that may be adopted according to some aspects is shown. As discussed above, Figure 8 The baseband circuit 804 may include processors 804A-804E and a memory 804G utilized by the processors. Each of the processors 804A-804E may include a memory interface 904A-904E for sending / receiving data to / from the memory 804G.

[0073] The baseband circuit 804 may also include one or more interfaces for communicatively coupling to other circuits / devices, such as a memory interface 912 (e.g., an interface for sending / receiving data to / from a memory external to the baseband circuit 804) and an application circuit interface 914 (e.g., an interface for sending / receiving data to / from a memory external to the baseband circuit 804). Figure 8 Application circuit 802 (interface for sending / receiving data), RF circuit interface 916 (e.g., for sending / receiving data to / from...). Figure 8 The interface includes an RF circuit 806 for transmitting / receiving data, a wireless hardware connection interface 918, and a power management interface 720 (e.g., an interface for sending / receiving power or control signals to / from the PMC 812).

[0074] While the methods described herein are shown and described as a series of actions or events, it should be understood that the order of such actions or events shown should not be construed as limiting. For example, some actions may occur in a different order and / or simultaneously with other actions or events besides those shown and / or described herein. Furthermore, not all shown actions may be required to implement one or more aspects of this specification. Additionally, one or more of the actions depicted herein may be performed in one or more separate actions and / or phases. Reference may be made to the accompanying drawings for ease of description. However, the methods are not limited to any particular aspect, aspect, or example provided in this disclosure and can be applied to any of the systems / devices / components disclosed herein.

[0075] As is widely recognized, the use of personally identifiable information should comply with privacy policies and practices that are generally accepted to meet or exceed industry or governmental requirements for protecting user privacy. Specifically, personally identifiable information data should be managed and processed to minimize the risk of unintentional or unauthorized access or use, and the nature of authorized use should be clearly explained to users.

[0076] As used herein, the term "processor" can refer to virtually any computing processing unit or device, including but not limited to single-core processors; single-processors with software multithreading capabilities; multi-core processors; multi-core processors with software multithreading capabilities; multi-core processors with hardware multithreading technology; parallel platforms; and parallel platforms with distributed shared memory. Additionally, a processor can refer to an integrated circuit, application-specific integrated circuit, digital signal processor, field-programmable gate array, programmable logic controller, complex programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions and / or processes described herein. Processors can utilize nanoscale architectures, such as, but not limited to, molecular and quantum dot-based transistors, switches, and gates, to optimize space utilization or enhance the performance of mobile devices. Processors can also be implemented as a combination of computing processing units.

[0077] While this disclosure has been shown and described with respect to one or more specific embodiments, changes and / or modifications may be made to the illustrated examples without departing from the spirit and scope of the appended claims. In particular, regarding the various functions performed by the aforementioned components or structures (components, devices, circuits, systems, etc.), unless otherwise stated, the terminology used to describe such components (including references to “component”) is intended to correspond to any component or structure that performs the specified function of the said component (e.g., functionally equivalent), even if it is not structurally equivalent to the disclosed structure that performs the functions in the exemplary specific embodiments of this disclosure shown herein.

[0078] The above description of exemplary aspects of the subject matter of this disclosure, including those described in the specification summary, is not intended to be exhaustive or to limit the disclosed aspects to their precise forms. While specific aspects and embodiments have been described herein for illustrative purposes, various modifications may be contemplated within the scope of such aspects and embodiments, as will be appreciated by those skilled in the art.

[0079] Additional Examples

[0080] Embodiments herein may include subjects such as methods, components for performing actions or blocks of the method, and at least one machine-readable medium including executable instructions that, when executed by a machine (e.g., a processor with memory, an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), etc.), cause the machine to perform actions of a method, apparatus, or system for concurrent communication using various communication technologies according to the described aspects and examples.

[0081] Example 1 is an apparatus for a user equipment (UE) including a baseband processor configured to perform operations including: receiving a UL gap configuration for uplink (UL) gaps from a base station (BS) via dedicated radio resource control (RRC) signaling, the UL gap configuration indicating a reference cell for a multiple radio dual connectivity (MR-DC) configuration; determining a UL gap pattern based on the received UL gap configuration; and stopping UL data transmission on frequency range 2 (FR2) cells and performing FR2 transmission power management during the UL gap.

[0082] Example 2 includes the subject matter of any variation of any of Examples 1, wherein performing the FR2 transmission power management during the UL gap includes: performing body proximity sensing using a body proximity sensor to detect the presence or absence of a human target approaching around the radiating FR2 antenna panel; and selectively applying additional power management maximum power reduction (P-MPR) or duty cycle based on the results of the performed body proximity sensing.

[0083] Example 3 includes the subject matter of any variation of Examples 1 to 2, wherein the UL gap configuration indicates the system frame number (SFN) and subframe of the reference cell used to calculate the UL gap pattern.

[0084] Example 4 includes the subject matter of any variation of any of Examples 1 to 3, wherein the reference cell is an FR2 cell.

[0085] Example 5 includes the subject matter of any variation of Examples 1 to 3, wherein the reference cell is configured by reference cell indication parameters selected from a list of cells including FR1 cells.

[0086] Example 6 includes the subject matter of any variation of any of Examples 5, wherein if the reference cell is not configured by the reference cell indication parameters, and in the case of asynchronous carrier aggregation (CA) in FR2, the reference cell is configured by the FR2 asynchronous reference cell indication parameters indicating the FR2 cell.

[0087] Example 7 includes the subject matter of any variation of any of Examples 1 to 3, wherein, in the case of asynchronous carrier aggregation (CA) in FR2, the reference cell is configured by FR2 asynchronous reference cell indication parameters indicating FR2 cells.

[0088] Example 8 includes the subject matter of any variation of any of Examples 1 to 3, wherein the UE is configured to continue frequency range 1 (FR1) communication during the UL gap.

[0089] Example 9 includes the subject matter of any variation of any of Examples 1 to 3, wherein the UE is configured to continue UE measurements indicated by the measurement gap during the UL gap.

[0090] Example 10 includes the subject matter of any variation of any of Examples 1 to 3, wherein the UE is configured to stop frequency range 1 (FR1) communication during the UL gap.

[0091] Example 11 includes the subject matter of any variation of Examples 1 to 3, wherein the baseband processor is configured to derive the UL gap pattern based on a time division duplex (TDD) uplink / downlink configuration with the same reference cell indication.

[0092] Example 12 includes the subject matter of any variation of any of Examples 1 to 3, wherein the UL gap configuration includes a plurality of UL gap pattern IDs corresponding to a plurality of combinations of UL gap lengths and UL gap repetition periods.

[0093] Example 13 includes the subject matter of any variation of any of Examples 1 to 3, wherein the UL gap configuration includes bits representing a first amount of UL gap lengths and bits representing a second amount of UL gap repetition periods, wherein the first amount is different from the second amount.

[0094] Example 14 includes the subject matter of any variation of any of Examples 1 to 3, wherein the UL gap configuration includes 1 bit representing a UL gap length of 1 ms or 0.125 ms and 3 bits representing a UL gap repetition period of 5 ms, 10 ms, 20 ms, 40 ms, 80 ms or 160 ms.

[0095] Example 15 is an apparatus for a base station (BS), the BS including a baseband processor configured to perform operations including: transmitting a UL gap configuration for uplink (UL) gaps to a user equipment (UE) via dedicated radio resource control (RRC) signaling, the UL gap configuration indicating a reference cell for a multiple radio dual connectivity (MR-DC) configuration for determining the UL gap pattern; and suspending communication with the UE during the UL gap so that the UE performs frequency range 2 (FR2) transmission power management.

[0096] Example 16 includes the subject matter of any variation of any of Examples 15, wherein the BS is configured to receive a UL gap pattern request from the auxiliary BS and send the UL gap pattern to the auxiliary BS if the UE supports per-UE gaps and the auxiliary BS configures the UE for EN-DC.

[0097] Example 17 includes the subject matter of any variation of any of Examples 15, wherein the BS is configured to send the UL gap pattern to the auxiliary BS if the UE supports per-UE gap of NE-DC.

[0098] Example 18 includes the subject matter of any variation of any of Examples 15, wherein the BS is configured to receive a UL gap pattern request from an auxiliary BS, and to send the UL gap pattern to the auxiliary BS if the UE supports per-UE gaps and the auxiliary BS configures the UE with an FR2 band for NR-DC.

[0099] Example 19 is a method for configuring an uplink (UL) gap, the method comprising: receiving, by a user equipment (UE), a UL gap configuration for the uplink (UL) gap from a base station (BS) via dedicated radio resource control (RRC) signaling, the UL gap configuration indicating a reference cell for a multiple radio dual connectivity (MR-DC) configuration; determining a UL gap pattern based on the received UL gap configuration; and stopping UL data transmission on a frequency range 2 (FR2) cell and performing FR2 transmission power management during the UL gap.

[0100] Example 20 includes the subject matter of any variation of any of the embodiments described in Example 19, wherein performing the FR2 transmission power management includes: performing body proximity sensing using a body proximity sensor to detect the presence or absence of a human target approaching around the radiating FR2 antenna panel; and selectively applying additional power management maximum power reduction (P-MPR) or duty cycle based on the results of the performed body proximity sensing.

[0101] Example 21 is a method that includes any action or combination of actions as substantially described herein in the detailed description.

[0102] Example 22 is a method, which is substantially described herein with reference to each or any combination of the accompanying drawings included herein or with reference to each or any combination of the paragraphs in the detailed description.

[0103] Example 23 is a user equipment configured to perform any action or combination of actions as substantially described herein in specific embodiments included in the user equipment.

[0104] Example 24 is a network node configured to perform any action or combination of actions as substantially described herein in the specific embodiments included in the network node.

[0105] Example 25 is a non-volatile computer-readable medium that stores instructions that, when executed, cause to perform any action or combination of actions as substantially described herein in the detailed description.

[0106] Example 26 is a baseband processor for a user equipment, the baseband processor being configured to perform any action or combination of actions as substantially described herein in specific embodiments included in the user equipment.

[0107] Example 27 is a baseband processor for a network node, the baseband processor being configured to perform any action or combination of actions as substantially described herein in specific embodiments included in the user equipment.

[0108] Example 28 includes a product comprising one or more tangible computer-readable nontransitory storage media, the one or more tangible computer-readable nontransitory storage media including computer-executable instructions operable to cause the at least one computer processor, when executed by at least one computer processor, to perform the method according to any of the above embodiments.

Claims

1. An apparatus for a user equipment (UE), the apparatus comprising a baseband processor configured to perform operations when instructions stored in a memory are executed, the operations including: The uplink UL gap configuration is received from the base station BS via dedicated radio resource control (RRC) signaling. The UL gap configuration indicates the UL gap pattern for the UL gap and the reference cell for the multi-radio dual-connectivity (MR-DC) configuration. The UL gap is independent of the measurement gap. UL data transmission on the 2FR2 cell in frequency range is stopped during the UL gap; and FR2 transmission power management is performed during the UL gap.

2. The apparatus of claim 1, wherein performing the FR2 transmission power management during the UL gap comprises: Body proximity sensors are used to perform body proximity sensing to detect the presence or absence of one or more human targets near the radiating FR2 antenna panel. as well as Based on the results of the performed body proximity sensing, additional power management maximum power reduction P-MPR or duty cycle can be selectively applied.

3. The apparatus of claim 1, wherein the UL gap configuration indicates the system frame number (SFN) and subframe of the reference cell used to calculate the UL gap pattern.

4. The apparatus according to claim 1, wherein the reference cell is an FR2 cell.

5. The apparatus of claim 1, wherein the reference cell is configured by a reference cell indication parameter selected from a list of cells including FR1 cells.

6. The apparatus of claim 5, wherein if the reference cell is not configured by the reference cell indication parameters, and in the case of asynchronous carrier aggregation (CA) in FR2, the reference cell is configured by the FR2 asynchronous reference cell indication parameters indicating the FR2 cell.

7. The apparatus of claim 1, wherein in the case of asynchronous carrier aggregation (CA) in FR2, the reference cell is configured by FR2 asynchronous reference cell indication parameters indicating the FR2 cell.

8. The apparatus of claim 1, wherein the UE is configured to continue frequency range 1FR1 communication during the UL gap.

9. The apparatus of claim 1, wherein the UE is configured to continue UE measurements indicated by the measurement gap during the UL gap.

10. The apparatus of claim 1, wherein the UE is configured to cease frequency range 1FR1 communication during the UL gap.

11. The apparatus of claim 1, wherein the operation further comprises: The UL gap pattern is derived based on a Time Division Duplex (TDD) uplink / downlink configuration with the same reference cell indication.

12. The apparatus of claim 1, wherein the UL gap configuration includes a plurality of UL gap pattern IDs, the plurality of UL gap pattern IDs corresponding to a plurality of combinations of UL gap lengths and UL gap repetition periods.

13. The apparatus of claim 1, wherein the UL gap configuration includes bits representing a first amount of UL gap lengths and bits representing a second amount of UL gap repetition periods, wherein the first amount is different from the second amount.

14. The apparatus of claim 1, wherein the UL gap configuration includes 1 bit representing a UL gap length of 1 ms or 0.125 ms and 3 bits representing a UL gap repetition period of 5 ms, 10 ms, 20 ms, 40 ms, 80 ms or 160 ms.

15. An apparatus for a base station (BS), the apparatus comprising a baseband processor configured to perform operations when instructions stored in a memory are executed, the operations including: Uplink UL gap configuration is provided to the User Equipment (UE) via Dedicated Radio Resource Control (RRC) signaling. This UL gap configuration indicates a UL gap pattern for the UL gap and a reference cell for a Multi-Radio Dual-Connection (MR-DC) configuration, the UL gap being independent of the measurement gap. Communication with the UE is stopped during the UL gap so that the UE can perform frequency range 2FR2 transmission power management.

16. The apparatus of claim 15, wherein the operation further comprises: The UE receives a UL gap pattern request from the auxiliary BS, and if the UE supports per-UE gaps and the auxiliary BS configures the UE for EN-DC, the UL gap pattern is sent to the auxiliary BS.

17. The apparatus of claim 15, wherein the operation further comprises: If the UE supports per-UE gaps for NE-DC, the UL gap pattern is sent to the auxiliary BS.

18. The apparatus of claim 15, wherein the operation further comprises: The UE receives a UL gap pattern request from the auxiliary BS, and if the UE supports per-UE gaps and the auxiliary BS configures the UE with the FR2 band for NR-DC, the UL gap pattern is sent to the auxiliary BS.

19. A method for communication, comprising: The uplink UL gap configuration is received from the base station BS via dedicated radio resource control (RRC) signaling. The UL gap configuration indicates the UL gap pattern for the UL gap and the reference cell for the multi-radio dual-connectivity (MR-DC) configuration. The UL gap is independent of the measurement gap. UL data transmission on the 2FR2 cell in frequency range is stopped during the UL gap; and FR2 transmission power management is performed during the UL gap.

20. The method of claim 19, wherein the FR2 transmission power management comprises: Body proximity sensors are used to perform body proximity sensing to detect the presence or absence of one or more human targets near the radiating FR2 antenna panel. as well as Based on the results of the performed body proximity sensing, additional power management maximum power reduction P-MPR or duty cycle can be selectively applied.

Images