Measurement enhancements for user equipment (UE) in a radio resource control (RRC) connection

Abstract

The techniques discussed herein can facilitate enhanced measurement of carrier aggregation (CA) and / or dual connectivity (DC) configurations for user equipment (UE) in radio resource control (RRC) connected mode. An exemplary embodiment includes a UE device comprising a processor configured to perform operations comprising: sending a UE assistance information message comprising a measurement request; receiving a first RRCReconfiguration message comprising a measConfig information element (IE); performing one or more measurements on each of one or more frequencies based at least on the RRC measConfig IE, wherein the one or more frequencies include at least one non-serving frequency associated with a neighboring cell; sending a MeasurementReport message indicating the one or more measurements for at least one of the one or more frequencies; and receiving a second RRCReconfiguration message configuring the UE with the at least one of the one or more frequencies.

Description

Background Art

[0001] Mobile communications in 5G, the next generation of wireless communication systems, or New Radio (NR) networks, will provide ubiquitous connectivity and access to information and the ability to share data globally. 5G networks and network slicing will be a unified, service-based framework that will target common and sometimes conflicting performance standards and provide services for a wide range of application domains, from enhanced mobile broadband (eMBB) to massive machine-type communications (mMTC), ultra-reliable low-latency communications (URLLC), and other communications. Generally speaking, NR will evolve based on the 3rd Generation Partnership Project (3GPP) Long Term Evolution (LTE) Advanced technology and additional enhanced radio access technologies (RATs) to achieve seamless and faster wireless connectivity solutions. BRIEF DESCRIPTION OF THE DRAWINGS

[0002] Figure 1 is a block diagram illustrating the architecture of a system including a core network (CN), eg, a fifth generation (5G) CN (5GC), according to various aspects.

[0003] Figure 2 is a diagram illustrating example components of an apparatus that may be employed in accordance with various aspects discussed herein.

[0004] Figure 3 is a diagram illustrating an example interface of baseband circuitry that may be employed in accordance with various aspects discussed herein.

[0005] Figure 4 is a block diagram illustrating a system that facilitates enhanced measurements for a radio resource control (RRC) connected mode UE, which can facilitate DC / CA configuration, in accordance with various aspects discussed herein.

[0006] Figure 5 is a state diagram illustrating three radio resource control (RRC) states in which a UE may operate in conjunction with various aspects discussed herein.

[0007] Figure 6 is a diagram showing a measurement model for a Radio Resource Control (RRC) connected mode UE based on K beams from a gNB (or other BS) in conjunction with various aspects discussed herein.

[0008] Figure 7 is a table illustrating measurement configurations and associated descriptions for measurement reporting in conjunction with various aspects discussed herein.

[0009] Figure 8 A flow chart illustrating an example method that can be employed by a UE and a NW to configure and send measurement reports in conjunction with various aspects discussed herein.

[0010] Figure 9 A MeasConfig information element (IE) is shown that specifies measurements to be performed by the UE in conjunction with various aspects discussed herein.

[0011] Figure 10 The MeasResults IE and MeasResultNR IE are shown in conjunction with various aspects discussed herein, covering measurement results for intra-frequency, inter-frequency, and inter-RAT mobility.

[0012] Figure 11 A flow chart illustrating a first exemplary method for facilitating enhancement of measurement reporting for connected mode UEs, which may facilitate DC / CA configuration, incorporating various aspects discussed herein.

[0013] Figure 12 A flow chart illustrating a second exemplary method for facilitating enhancement of measurement reporting for connected mode UEs, which may facilitate DC / CA configuration, incorporating various aspects discussed herein.

[0014] Figure 13 Shown are examples of ReportConfigNR and EventTriggerConfig IEs that have been updated to indicate CA / DC purposes, incorporating various aspects discussed herein.

[0015] Figure 14 An example of a MeasObjectNR IE incorporating various aspects discussed herein is shown, which has been updated to indicate CA / DC purpose.

[0016] Figure 15 Shown is an example of a MeasObjectEUTRA IE incorporating various aspects discussed herein, which has been updated to indicate CA / DC purpose.

[0017] Figure 16 A flow chart illustrating a third exemplary method for facilitating enhancement of measurement reporting for connected mode UEs, which may facilitate DC / CA configuration, incorporating various aspects discussed herein.

[0018] Figure 17 A flow chart illustrating a fourth exemplary method for enhancing measurement reporting for connected mode UEs, which may facilitate DC / CA configuration, incorporating various aspects discussed herein.

[0019] Figure 18 A flow chart illustrating an example method or process that can be employed at a UE according to various aspects discussed herein, which example method or process facilitates one or more enhancements for measurements in connected mode discussed herein.

[0020] Figure 19 A flow chart is shown that illustrates an example method or process that can be employed at a BS according to various aspects discussed herein, which example method or process facilitates one or more enhancements discussed herein for measurements performed by a UE in connected mode. DETAILED DESCRIPTION

[0021] The present disclosure will now be described with reference to the accompanying drawings, wherein similar reference numerals are used to refer to similar elements throughout the text, and the structures and devices shown therein need not be drawn to scale. As used herein, the terms "component", "system", "interface", etc. are intended to refer to entities, hardware, software (e.g., in execution) and / or firmware related to a computer. For example, a component can be a processor (e.g., a microprocessor, a controller or other processing device), a process running on a processor, a controller, an object, an executable file, a program, a storage device, a computer, a tablet computer and / or a user equipment with a processing device (e.g., a mobile phone or other devices configured to communicate via a 3GPP RAN, etc.). By way of example, an application and a server running on a server can also be a component. One or more components can reside in a process, and a component can be located on a computer and / or distributed between two or more computers. A group of elements or a group of other components can be described herein, wherein the term "group" can be interpreted as "one or more" unless the context indicates otherwise (e.g., "empty group", "a group of two or more Xs", etc.).

[0022] In addition, the components can execute from various computer-readable storage media having various data structures stored thereon, such as using modules, for example. The components can communicate via local and / or remote processes, such as according to signals having one or more data packets (e.g., data from one component interacts with another component in a local system, a distributed system, and / or across a network, such as the Internet, a local area network, a wide area network, or a similar network with other systems via signals).

[0023] As another example, a component may be a device that has a specific functionality provided by a mechanical component that operates through electrical or electronic circuitry, where the electrical or electronic circuitry may be operated by a software application or firmware application executed by one or more processors. The one or more processors may be internal or external to the device and may execute at least a portion of the software or firmware application. As another example, a component may be a device that provides a specific functionality through an electronic component without the need for a mechanical component; the electronic component may include one or more processors therein to execute at least a portion of the software and / or firmware that provides the functionality of the electronic component.

[0024] The use of the word "exemplary" is intended to present concepts in a concrete manner. As used in this application, the term "or" is intended to mean an inclusive "or" rather than an exclusive "or." That is, unless otherwise specified or clear from the context, "X employs A or B" is intended to mean any natural inclusive permutation. That is, if X employs A; X employs B; or X employs both A and B, then "X employs A or B" is satisfied in any of the foregoing cases. In addition, the articles "a" and "an" as used in this application and the appended claims should generally be construed to mean "one or more," unless otherwise specified or clear from the context to be directed to the singular. Furthermore, to the extent that the terms "comprising," "including," "having," "having," "with," or variations thereof are used in the detailed description and claims, such terms are intended to be inclusive in a manner similar to the term "comprising." Furthermore, where one or more numbered items are discussed (e.g., "a first X," "a second X," etc.), generally, the one or more numbered items can be different or they can be the same, but in some cases, the context may indicate that they are different or that they are the same.

[0025] As used herein, the term "circuitry" may refer to, may be part of, or may include an application-specific integrated circuit (ASIC), electronic circuit, processor (shared, dedicated, or group), and / or memory (shared, dedicated, or group) that executes one or more software or firmware programs, combinational logic circuits, and / or other suitable hardware components that provide the described functionality. In some aspects, a circuit may be implemented in one or more software or firmware modules, or functionality associated with the circuit may be implemented by one or more software or firmware modules. In some aspects, a circuit may include logic components that may operate at least partially in hardware.

[0026]

[0010] Various aspects discussed herein may be directed to facilitating wireless communications, and the nature of these communications may vary.

[0027] It is understood that the use of personally identifiable information should be subject to privacy policies and practices that are generally recognized to meet or exceed industry or government requirements for maintaining 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 stated to users.

[0028] Aspects described herein may be implemented into a system using any suitably configured hardware and / or software. Figure 1The architecture of a system 100 including a core network (CN) 120 (e.g., a fifth generation (5G) CN (5GC)) according to various aspects is shown. The system 100 is shown to include: a UE 101, which can be the same as or similar to one or more other UEs discussed herein; a third generation partnership project (3GPP) radio access network (wireless AN or RAN) or other (e.g., non-3GPP) AN, (R) AN 210, which can include one or more RAN nodes (e.g., evolved Node B (eNB)), next generation Node B (gNB and / or other nodes) or other nodes or access points; and a data network (DN) 203, which can be, for example, operator services, Internet access, or third-party services; and a fifth generation core network (5GC) 120. 5GC 120 may include one or more of the following functions and network components: an authentication server function (AUSF) 122, an access and mobility management function (AMF) 121, a session management function (SMF) 124, a network exposure function (NEF) 123, a policy control function (PCF) 126, a network repository function (NRF) 125, a unified data management (UDM) 127, an application function (AF) 128, a user plane (UP) function (UPF) 102, and a network slice selection function (NSSF) 129, for example. Figure 1 As shown, they can be connected via various interfaces and / or reference points.

[0029] Figure 2 1. Example components of a device 200 according to some aspects are shown. In some aspects, the device 200 may include application circuitry 202, baseband circuitry 204, radio frequency (RF) circuitry 206, front-end module (FEM) circuitry 208, one or more antennas 210, and power management circuitry (PMC) 212 (coupled together at least as shown). The components of the illustrated device 200 may be included in a UE or a RAN node. In some aspects, the device 200 may include fewer components (e.g., a RAN node may not utilize application circuitry 202 but instead include a processor / controller to process IP data received from a CN such as a 5GC 120 or an evolved packet core (EPC)). In some aspects, the device 200 may include additional components such as, for example, memory / storage, a display, a camera, sensors (including one or more temperature sensors, such as a single temperature sensor, multiple temperature sensors at different locations in the device 200, etc.), or input / output (I / O) interfaces. In other aspects, the components described below may be included in more than one device (e.g., the circuitry may be separately included in more than one device for a Cloud-RAN (C-RAN) implementation).

[0030] The application circuitry 202 may include one or more application processors. For example, the application circuitry 202 may include circuitry such as, but not limited to, one or more single-core or multi-core processors. The processors may include any combination of general-purpose processors and specialized processors (e.g., graphics processors, application processors, etc.). The processors may be coupled to or include memory / storage and may be configured to execute instructions stored in the memory / storage to enable various applications or operating systems to run on the device 200. In some aspects, the processors of the application circuitry 202 may process IP data packets received from the EPC.

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

[0032] In some aspects, the baseband circuitry 204 may include one or more audio digital signal processors (DSPs) 204F. The audio DSPs 204F may include components for compression / decompression and echo cancellation, and in other aspects may include other suitable processing elements. In some aspects, the components of the baseband circuitry may be suitably combined in a single chip, a single chipset, or disposed on the same circuit board. In some aspects, some or all of the components of the baseband circuitry 204 and the application circuitry 202 may be implemented together, such as on a system on a chip (SOC).

[0033] In some aspects, the baseband circuitry 204 can provide communications compatible with one or more radio technologies. For example, in some aspects, the baseband circuitry 204 can support communications with NG-RAN, Evolved Universal Terrestrial Radio Access Network (EUTRAN), or other wireless metropolitan area networks (WMANs), wireless local area networks (WLANs), wireless personal area networks (WPANs), etc. Aspects in which the baseband circuitry 204 is configured to support radio communications of more than one wireless protocol can be referred to as multi-mode baseband circuitry.

[0034] RF circuitry 206 can communicate with a wireless network using modulated electromagnetic radiation through a non-solid medium. In various aspects, RF circuitry 206 can include switches, filters, amplifiers, etc. to facilitate communication with the wireless network. RF circuitry 206 can include a receive signal path, which can include circuitry for down-converting RF signals received from FEM circuitry 208 and providing a baseband signal to baseband circuitry 204. RF circuitry 206 can also include a transmit signal path, which can include circuitry for up-converting baseband signals provided by baseband circuitry 204 and providing an RF output signal to FEM circuitry 208 for transmission.

[0035] In some aspects, the receive signal path of RF circuitry 206 may include mixer circuitry 206a, amplifier circuitry 206b, and filter circuitry 206c. In some aspects, the transmit signal path of RF circuitry 206 may include filter circuitry 206c and mixer circuitry 206a. RF circuitry 206 may also include synthesizer circuitry 206d for synthesizing frequencies used by mixer circuitry 206a in the receive and transmit signal paths. In some aspects, mixer circuitry 206a in the receive signal path may be configured to downconvert the RF signal received from FEM circuitry 208 based on the synthesized frequency provided by synthesizer circuitry 206d. Amplifier circuitry 206b may be configured to amplify the downconverted signal, and filter circuitry 206c may be a low-pass filter (LPF) or a band-pass filter (BPF) configured to remove unwanted signals from the downconverted signal to generate an output baseband signal. The output baseband signal may be provided to baseband circuitry 204 for further processing. In some aspects, the output baseband signal can be a zero-frequency baseband signal, although this is not required.In some aspects, the mixer circuit 206a of the receive signal path can include a passive mixer, although the scope of the various aspects is not limited in this respect.

[0036] In some aspects, mixer circuit 206a of the transmit signal path may be configured to upconvert an input baseband signal based on a synthesized frequency provided by synthesizer circuit 206d to generate an RF output signal for FEM circuit 208. The baseband signal may be provided by baseband circuit 204 and may be filtered by filter circuit 206c.

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

[0038] In some aspects, the output baseband signal and the input baseband signal can be analog baseband signals, although the scope of the various aspects is not limited in this respect. In some alternative aspects, the output baseband signal and the input baseband signal can be digital baseband signals. In these alternative aspects, the RF circuitry 206 can include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuitry, and the baseband circuitry 204 can include a digital baseband interface to communicate with the RF circuitry 206.

[0039] In some dual-mode aspects, separate radio IC circuits may be provided to process signals for each spectrum, although the scope of the various aspects is not limited in this respect.

[0040] In some aspects, the synthesizer circuit 206 d can be a fractional-N synthesizer or a fractional-N / N+1 synthesizer, although the scope of the various aspects is not limited in this respect, as other types of frequency synthesizers may be suitable. For example, the synthesizer circuit 206 d can be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer including a phase-locked loop with a frequency divider.

[0041] Synthesizer circuit 206d may be configured to synthesize an output frequency based on the frequency input and the divider control input for use by mixer circuit 206a of RF circuit 206. In some aspects, synthesizer circuit 206d may be a fractional-N / N+1 synthesizer.

[0042] In some aspects, the frequency input can be provided by a voltage controlled oscillator (VCO), but this is not required. The divider control input can be provided by the baseband circuitry 204 or the application processor 202 depending on the desired output frequency. In some aspects, the divider control input (e.g., N) can be determined from a lookup table based on the channel indicated by the application processor 202.

[0043] The synthesizer circuit 206d of the RF circuit 206 may include a frequency divider, a delay-locked loop (DLL), a multiplexer, and a phase accumulator. In some aspects, the frequency divider may be a dual-mode frequency divider (DMD), and the phase accumulator may be a digital phase accumulator (DPA). In some aspects, the DMD may be configured to divide the input signal by N or N+1 (e.g., based on a carry output) to provide a fractional division ratio. In some exemplary aspects, 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 aspects, the delay element may be configured to divide the VCO cycle into Nd equal phase groups, where Nd is the number of delay elements in the delay line. In this way, the DLL provides negative feedback to help ensure that the total delay through the delay line is one VCO cycle.

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

[0045] The FEM circuitry 208 may include a receive signal path that may include circuitry configured to operate on RF signals received from one or more antennas 210, amplify the received signals, and provide an amplified version of the received signals to the RF circuitry 206 for further processing. The FEM circuitry 208 may also include a transmit signal path that may include circuitry configured to amplify transmit signals provided by the RF circuitry 206 for transmission via one or more of the one or more antennas 210. In various aspects, amplification by either the transmit or receive signal path may be performed solely in the RF circuitry 206, solely in the FEM 208, or in both the RF circuitry 206 and the FEM 208.

[0046] In some aspects, the FEM circuitry 208 may include a TX / RX switch to switch between transmit and receive modes of operation. The FEM circuitry may include a receive signal path and a transmit signal path. The receive signal path of the FEM circuitry may include an LNA to amplify a received RF signal and provide the amplified received RF signal as an output (e.g., to the RF circuitry 206). The transmit signal path of the FEM circuitry 208 may include a power amplifier (PA) to amplify an input RF signal (e.g., provided by the RF circuitry 206), and one or more filters to generate an RF signal for subsequent transmission (e.g., via one or more of the one or more antennas 210).

[0047] In some aspects, the PMC 212 can manage the power provided to the baseband circuitry 204. Specifically, the PMC 212 can control power source selection, voltage scaling, battery charging, or DC-DC conversion. When the device 200 is capable of being powered by a battery, such as when the device is included in a UE, the PMC 212 is typically included. The PMC 212 can improve power conversion efficiency while providing a desired implementation size and heat dissipation characteristics.

[0048] Although Figure 2The PMC 212 is shown coupled only to the baseband circuitry 204. However, in other aspects, the PMC 212 may additionally or alternatively be coupled to other components (such as, but not limited to, the application circuitry 202, the RF circuitry 206, or the FEM 208) and perform similar power management operations.

[0049] In some aspects, the PMC 212 can control or otherwise participate in various power saving mechanisms of the device 200. For example, if the device 200 is in the RRC_Connected state, in which it is still connected to the RAN node and expects to receive traffic soon, then after a period of inactivity, it can enter a state known as discontinuous reception mode (DRX). During this state, the device 200 can be powered down for short intervals to save power.

[0050] If there is no data traffic activity for an extended period of time, the device 200 may transition to the RRC_Idle state, in which it is disconnected from the network and does not perform operations such as channel quality feedback, handover, etc. The device 200 enters a very low power state and performs paging, in which it periodically wakes up again to listen to the network and then powers down again. The device 200 may not receive data in this state; to receive data, the device may transition back to the RRC_Connected state.

[0051] An additional power saving mode can disable the device from using the network for periods exceeding the paging interval (ranging from a few seconds to several hours). During this period, the device is completely unable to connect to the network and can be completely powered down. Any data sent during this period will incur significant latency, assuming that latency is acceptable.

[0052] The processor of the application circuitry 202 and the processor of the baseband circuitry 204 can be used to execute elements of one or more instances of the protocol stack. For example, the processor of the baseband circuitry 204 can be used alone or in combination to perform Layer 3, Layer 2, or Layer 1 functions, while the processor of the application circuitry 204 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 a Radio Resource Control (RRC) layer, which is described in further detail below. As mentioned herein, Layer 2 may include a Medium Access Control (MAC) layer, a Radio Link Control (RLC) layer, and a Packet Data Convergence Protocol (PDCP) layer, which are described in further detail below. As mentioned herein, Layer 1 may include a Physical (PHY) layer of the UE / RAN node, which is described in further detail below.

[0053] Figure 31 shows an exemplary interface of a baseband circuit according to some aspects. As discussed above, Figure 2 The baseband circuit 204 may include processors 204A-204E and a memory 204G utilized by the processors. Each of the processors 204A-204E may include a memory interface 304A-304E, respectively, to send / receive data to / from the memory 204G.

[0054] The baseband circuit 204 may also include one or more interfaces for communicatively coupling to other circuits / devices, such as a memory interface 312 (e.g., an interface for sending / receiving data to / from a memory external to the baseband circuit 204); an application circuit interface 314 (e.g., an interface for sending / receiving data to / from a memory external to the baseband circuit 204); Figure 2 RF circuit interface 316 (for example, for sending / receiving data to / from the application circuit 202); Figure 2 an interface for sending / receiving data to / from the RF circuit 206); a wireless hardware connection interface 318 (e.g., for sending / receiving data to / from a near field communication (NFC) component, Components (e.g. Low Energy), Wi- components and other communication components to send / receive data); and a power management interface 320 (eg, an interface for sending / receiving power or control signals to / from the PMC 212).

[0055] As discussed in greater detail herein, various aspects that can be employed, for example, at a UE, can facilitate power management associated with a wireless modem. Various aspects can employ the power management techniques discussed herein, wherein, based on monitored power consumption levels and temperature levels, one or more power management stages discussed herein can be employed to mitigate overheating. The power management stages discussed herein can reduce power consumption and associated overheating caused by 5G (fifth generation) NR (New Radio) operation, LTE (Long Term Evolution) operation, or both.

[0056] See also Figure 4, which shows a block diagram of a system 400 that can be employed at a UE (user equipment), a base station (BS, such as a next-generation NodeB (gNodeB or gNB), an evolved NodeB (eNB), or other BS (base station) / TRP (transmit / receive point)), or another component of a 3GPP (3rd Generation Partnership Project) network (e.g., a 5GC (fifth generation core network) component or function, such as a UPF (user plane function)) in accordance with various aspects discussed herein, to facilitate enhanced measurements for radio resource control (RRC) connected mode UEs, which can facilitate DC / CA configuration. System 400 may include a processor 410, communication circuitry 420, and memory 430. Processor 410 (e.g., which may include one or more of 202 and / or 204A-204F, etc.) may include processing circuitry and associated interfaces (e.g., a communication interface (e.g., RF circuit interface 316) for communicating with communication circuitry 420, a memory interface (e.g., memory interface 312) for communicating with memory 430, etc.). The communication circuit 420 may include, for example, circuits for wired and / or wireless connections (e.g., 206 and / or 208), which may include transmitter circuits (e.g., associated with one or more transmission chains) and / or receiver circuits (e.g., associated with one or more reception chains), wherein the transmitter circuits and the receiver circuits may employ common and / or different circuit elements, or a combination thereof. The memory 430 may include one or more memory devices (e.g., memory 204G, local memory (e.g., including CPU registers of the processor discussed herein), etc.), which may have any of various storage media (e.g., volatile and / or non-volatile according to any of various technologies / configurations, etc.), and may store instructions and / or data associated with one or more of the processor 410 or the transceiver circuit 420.

[0057] Specific types of aspects of the system 400 (eg, UE aspects, etc.) may be indicated via subscripts (eg, system 400 UE Including processor 410 UE , communication circuit 420 UE and memory 430 UE In some aspects, such as BS aspects (eg, system 400 BS ) and network components (eg, UPF (User Plane Function), etc.) aspects (eg, system 400 UPF ), processor 410 BS (etc.), communication circuits (eg, 420 BS etc.) and memory (eg, 430 BS, etc.) may be included in a single device or may be included in different devices, such as part of a distributed architecture. In some aspects, signaling or messaging between different aspects of system 400 (e.g., 4001 and 4002) may be generated by processor 4101, transmitted by communication circuitry 4201 over an appropriate interface or reference point (e.g., 3GPP air interfaces N3, N4, etc.), received by communication circuitry 4202, and processed by processor 4102. Depending on the type of interface, additional components (e.g., antennas, network ports, etc. associated with systems 4001 and 4002) may participate in the communication.

[0058] In various aspects, one or more of information (e.g., system information, resources associated with signaling, etc.), features, parameters, etc., may be received from a gNB or other access point (e.g., via a processor 410) via signaling (e.g., associated with one or more layers, such as L1 signaling or higher layer signaling (e.g., MAC, RRC, etc.)). BS Generate, by the communication circuit 420 BS Transmission, by the communication circuit 420 UE Received and processed by processor 410 UE The UE is configured with information / features / parameters / etc., generated or processed by the UE. The type of signaling employed and / or the exact details of the operations performed at the UE and / or BS during the processing (e.g., signaling structure, processing of PDUs / SDUs, etc.) may vary depending on the type, features, parameters, etc. of the information. However, for convenience, such operations may be referred to herein as configuring information / features / parameters / etc. for the UE, generating or processing configuration signaling, or by similar terminology.

[0059] See also Figure 5 , which shows a state diagram of three radio resource control (RRC) states in which a UE may operate in conjunction with various aspects discussed herein. In the idle state, the UE is disconnected from the core network (CN). In the idle state, the UE performs cell reselection and may receive paging messages from the CN via the cell in which the UE is residing. To enter the connected state, the UE performs an RRC connection procedure 510, in which the UE uses a random access channel (RACH) procedure to connect to the CN and the radio access network (RAN). In the connected state, the UE connects to the CN and registers with the CN. Control and user plane connections are established between the RAN and the CN for the UE. The RAN knows which cell the UE belongs to, and all parameters necessary for unicast communication between the UE and the RAN are known to both the UE and the RAN. The UE context, including the UE's access stratum (AS) context (e.g., the UE's cell radio network temporary identifier (C-RNTI) and the cell identity of the primary cell), and the RRC configuration for the UE (e.g., radio bearers and security information) are stored in the RAN and the UE.

[0060] The UE may move from the connected state back to the idle state by performing an RRC release procedure 520. When the UE returns to the idle state, the UE context is deleted from the UE and the RAN. As indicated at 530 and 560, the UE may also default to the idle state from the connected state or the inactive state when no cell to camp on is found.

[0061] The inactive state was introduced in 5G to provide an intermediate state between the idle and connected states. This intermediate state will accelerate the reconnection process by eliminating some of the signaling required to transition from the idle state to the connected state. The inactive state is beneficial for UEs that do not frequently communicate with the RAN and can potentially save energy compared to these UEs remaining in the connected state. To enter the inactive state, the UE performs an RRC release procedure using a suspended configuration 540, in which the UE context is stored by both the UE and the serving gNB. While in the inactive state, the UE maintains a non-access stratum (NAS) connection to the CN (i.e., it remains in a connection management (CM)-connected state, rather than an idle state where the UE has no CM-connection).

[0062] While in the Inactive state, the UE can move within the RAN Notification Area (RNA) without notifying the RAN, perform cell reselection, and receive paging messages from the RAN. However, the UE does not have dedicated AS resources for unicast communication and therefore cannot perform any dedicated data transmission or reception. Because the UE cannot perform dedicated data reception while in the Inactive state, when downlink data is to be sent to the UE, the RAN pages the UE to trigger the UE to enter the Connected state. When the UE has uplink data to send, the UE first enters the Connected state before sending the uplink data.

[0063] To enter the connected state from the inactive state, the UE performs an RRC resume procedure 550, in which the AS context and RRC configuration are restored to the UE and the (new) serving cell. Compared to the transition from the idle state to the connected state, this speeds up the transition to the connected state by allowing the previous connection to be restored without having to perform extensive signaling.

[0064] See also Figure 6 , which shows a diagram of a measurement model for a Radio Resource Control (RRC) connected mode UE based on K beams from a gNB (or other BS) in combination with various aspects discussed herein.

[0065] See also Figure 7 , which shows a table of measurement configurations and associated descriptions for measurement reporting in conjunction with various aspects discussed herein.

[0066] See also Figure 8 , which illustrates a method that can be used by UE 400 in conjunction with various aspects discussed herein.UE and NW 400 BS Flowchart of an example method 800 for configuring and sending measurement reports. At 810, the method 800 may include the NW (e.g., via a BS such as a gNB) sending one or more of an RRCReconfiguration or RRCResume message to the UE that may include a measurement configuration (e.g., via a measConfig information element (IE)). At 820, the RRCReconfiguration / RRCResume procedure may be completed, and the UE may perform measurements based on the measurement configuration. At 830, the UE may send a measurement report to the NW indicating the results of the performed measurements.

[0067] However, existing measurement techniques target mobility and are not optimized for dual connectivity (DC) and / or carrier aggregation (CA) configurations.

[0068] The NW may configure the RRC_CONNECTED UE to perform measurements and report the measurements according to the measurement configuration indicated via the MeasConfig information element (IE). The measurement configuration may be provided by means of dedicated signaling (e.g., RRCReconfiguration or RRCResume).

[0069] A connected UE may generate and send a measurement report (MR) having one or more of the following characteristics: (1) the MR may include a measurement identifier of the associated measurement configuration that triggered the report; (2) the cell and beam measurement quantities to be included in the measurement report are configured by the network; (3) the number of non-serving cells to be reported may be limited by configuration made by the network; (4) cells belonging to a blacklist (when it is configured by the network) are not used for event evaluation and reporting, and when a whitelist is configured by the network, only cells belonging to the whitelist are used for event evaluation and reporting; and (5) and the beam measurements to be included in the measurement report are configured by the network (e.g., only a beam identifier, measurement results and beam identifier, or no beam report).

[0070] Whether a measurement is non-gap assisted or gap assisted depends on the UE's capabilities, the UE's active bandwidth part (BWP), and the current operating frequency. In a non-gap assisted scenario, the UE is capable of performing such measurements without measurement gaps. In a gap assisted scenario, the UE cannot be assumed to be able to perform such measurements without measurement gaps.

[0071] For event-triggered or periodic measurement reports, the UE may include reportAddNeighMeas in the measurement report. For reportAddNeighMeas, the UE includes the measurement result of the best neighbor cell on the serving frequency.

[0072] Because existing measurements target mobility rather than the configuration of dual connectivity (DC) and / or carrier aggregation (CA), they do not provide measurements of neighboring cells on non-serving frequencies.

[0073] See also Figure 9 , which shows the MeasConfig IE that specifies the measurements to be performed by the UE in conjunction with various aspects discussed herein. Figure 10 , which shows the MeasResults IE and MeasResultNR IE in conjunction with various aspects discussed herein, covering measurement results for intra-frequency, inter-frequency, and inter-RAT mobility.

[0074] Existing measurement techniques are not suitable for DC / CA configuration. In some NW strategies, NW DC / CA configuration relies on measurement configuration.

[0075] Typically, for connected UEs, the NW will perform primary cell (PCell) change, secondary cell (SCell) addition, and secondary cell group (SCG) addition based on UE measurement reports on non-serving cells. In other words, if the NW does not configure neighbor cell measurements, the NW will not perform such RRC Reconfiguration.

[0076] Currently, in some NW vendors' LTE networks, when a UE initially accesses the NW, the NW only configures inter-RAT (Radio Access Technology) NR measurement configurations. If the UE does not report NR measurement reports for a period of time, the NW will delete the measurement configurations. The main motivation for the NW to delete the measurement configurations is that NR measurements may involve measurement gaps, which will cause ongoing transmissions to be interrupted.

[0077] Therefore, the first problem with the prior art is that the lack of measurement configuration will prevent the NW from enabling the DC / CA configuration, regardless of whether the DC / CA configuration is more suitable for the latest UE situations, such as in the following situations: (1) the UE triggers a new service; (2) the UE enters the LTE+NR overlapping coverage area; and / or (3) the amount of data transmitted becomes larger.

[0078] In addition, although the existing MR report can carry the MR of the serving frequency, it cannot carry the potential frequency used for CA / DC.

[0079] In existing systems, only the best neighboring cell on the serving frequency is allowed to be reported to the NW along with the measurement report by the connected UE. The motivation for introducing these measurement results is for mobility handover. For example, during the handover preparation phase, the source node can provide all measurement results to the target node, and the target node can select a cell as the target PCell.

[0080] Therefore, the second problem of the existing system is that for the measurement report triggered by the A3 event (the offset of the neighboring cell exceeds the PCell / PSCell) and / or the A5 event (the PCell / PSCell becomes worse than the absolute threshold 1 and the neighboring cell / SCell becomes better than another absolute threshold 2), the NW can decide the target PCell based on the measurement report, but cannot decide the SCG / SCell for CA / DC configuration based on the measurement report, because the measurement result can only reflect the best neighboring cell on the current serving frequency, and will not reflect the best cell on the potential CA / DC secondary component carrier.

[0081] See also Figure 11 , which illustrates a flow chart of a first exemplary method 1100 for enhancing measurement reporting for connected mode UEs, incorporating various aspects discussed herein, which may facilitate DC / CA configuration. Method 1100 provides a first exemplary technique for addressing the first problem, wherein a lack of measurement configuration prevents a NW in an existing system from enabling DC / CA configuration even when DC / CA configuration is more appropriate for the UE.

[0082] Compared to existing systems, various embodiments discussed herein may utilize exemplary method 1100 and / or related techniques to facilitate measurement of potential frequencies for DC / CA configurations. In conjunction with method 1100 , an RRC connection may be established (or may have been established) for the UE, as shown at 1110 .

[0083] The method 1100 may be used in a scenario where a connected UE prefers a CA / DC configuration but does not have a measurement configuration associated with a neighboring cell.

[0084] At 1120, the UE (eg, including 400 UE ) can generate a UE assistance information message including a measurement request and send it to the BS of the NW (eg, including 400 BS Depending on the implementation, the request may include or indicate one or more of the following types of information: (1) a 1-bit indication of a measurement request; (2) an indication of the radio access technology (RAT) to be measured (e.g., EUTRA, NR, etc.); (3) one or more frequencies / bands to be measured; and / or (4) one or more frequencies / bands to be measured in the absence of a measurement gap.

[0085] At 1130 , in response to the measurement request, the BS may generate and transmit an RRCReconfiguration message including a MeasConfig configuring the requested measurement.

[0086] The UE may perform the configured measurements, and at 1140, the UE may generate and send a measurement report to the BS, the measurement report indicating the configured measurements on the potential CA / DC frequencies / bands.

[0087] At 1150 , the BS may generate and send an RRCReconfiguration message including a DC / CA configuration including at least one of the potential CA / DC frequencies / bands configured at 1130 and indicated in the measurement report at 1140 to the UE.

[0088] See also Figure 12 , which illustrates a flow chart of a second exemplary method 1200 for enhancing measurement reporting for connected mode UEs, incorporating various aspects discussed herein, which may facilitate DC / CA configuration. Method 1200 provides a second exemplary technique for addressing the first problem, wherein a lack of measurement configuration prevents a NW in an existing system from enabling DC / CA configuration even when DC / CA configuration is more appropriate for the UE.

[0089] In conjunction with method 1200, an RRC connection may be established (or already established) for the UE (eg, using 400 UE etc.), as shown at 1210.

[0090] At 1220, the BS (eg, using 400 BS etc.) can generate and send an RRCReconfiguration message including MeasConfig, where the MeasConfig configuration includes the potential CA / DC frequency (e.g., Figure 12 One or more measurements of measurements of F1 and F2 in , etc., where the measurement configuration can be used for CA / DC purposes and the CA / DC purpose can be indicated. The purpose can be indicated in one of the configurations of the measurement report or the measurement object. In an embodiment where the DC / CA purpose configuration is indicated in the report configuration, the purpose can be indicated in the ReportConfigNR IE, or a new event Ax can be introduced for CA / DC purposes. Figure 13 , which shows an example of a ReportConfigNR and EventTriggerConfig IE (portions of the latter have been omitted) that incorporate various aspects discussed herein, updated to indicate CA / DC purposes. Figure 14 , which shows an example of a MeasObjectNR IE that has been updated to indicate CA / DC purpose, incorporating various aspects discussed herein. Figure 15 , which shows an example of a MeasObjectEUTRA IE incorporating various aspects discussed herein, which has been updated to indicate CA / DC purpose.

[0091] See again Figure 12 , the UE may perform the configured measurements at 1230 , including performing the configured measurements on potential frequencies for CA / DC.

[0092] At 1240, the UE may generate and send a measurement report to the BS, the measurement report indicating the configured measurements on the potential CA / DC frequencies / bands.

[0093] At 1250, the BS may generate and send an RRCReconfiguration message to the UE, which includes an NR secondary cell group (SCG) configuration, which includes at least one frequency / band among the potential CA / DC frequencies / bands configured at 1220 and indicated in the measurement report of 1240.

[0094] See also Figure 16 , which illustrates a flow chart of a third exemplary method 1600 for enhancing measurement reporting for connected mode UEs, incorporating various aspects discussed herein, to facilitate DC / CA configuration. Method 1600 provides a first exemplary technique for addressing the second issue, wherein, for measurement reports triggered by A3 / A5 events, while the NW in existing systems can determine the target PCell based on the measurement report, it cannot determine the SCG / SCell for CA / DC configuration based on the measurement report because the measurement results can only reflect the best neighboring cell on the current serving frequency and will not reflect the best cell on a potential CA / DC secondary component carrier, as existing systems only allow reporting of the best non-serving cell on the serving frequency of a neighboring cell.

[0095] In conjunction with method 1600, an RRC connection may be established (or already established) for the UE (eg, using 400 UE etc.), as shown at 1610.

[0096] At 1620, the BS (eg, using 400 BS etc.) may generate and send an RRCReconfiguration message including a MeasConfig, the MeasConfig configuring one or more measurements including a first set of frequencies associated with the triggered measurement report (eg, Figure 16 F2 in ) and one or more candidate CA / DC frequencies (e.g., Figure 16In various implementations, the first set of frequencies and the one or more candidate CA / DC frequencies may belong to a frequency band combination supported by the UE. In some scenarios, the first set of frequencies may correspond to adjacent frequencies, while in other scenarios, they may include a serving frequency.

[0097] The measurement configuration may indicate one or more frequencies (e.g., candidate CA / DC frequencies, etc.) to be carried as additional measurement reports. In some embodiments, the NW (e.g., via the BS) may configure the frequencies (e.g., candidate CA / DC frequencies) to be carried as additional measurement reports, for example, in a measurement object of a first set of frequencies (e.g., F2). In some embodiments, the NW may configure a measurement object similar to an existing measurement object for measurements on candidate CA / DC frequencies (e.g., F3, F4, or F5).

[0098] At 1630 , the UE may perform configured measurements, including configured measurements on configured candidate frequencies for CA / DC.

[0099] At 1640, the UE may generate and send a measurement report to the BS, the measurement report indicating the configured measurements for the first set of frequencies and for one or more frequencies / bands in the potential CA / DC frequencies / bands. In various embodiments, the NW may configure (e.g., at 1620) criteria for the UE to determine which frequencies from the potential / candidate CA / DC group to provide as additional reports. For example, the NW may configure a radio link quality threshold (e.g., reference signal (RS) received power (RSRP) / RS received quality (RSRQ) / signal to interference and noise ratio (SINR)), etc.), and if the quality of one frequency group (e.g., F3) is greater than the threshold and the quality of another frequency group (e.g., F4) is less than the threshold, the UE may include the frequency group (e.g., F3) with a quality greater than the threshold and the associated results in the additional report, while ignoring the frequency group (e.g., F4) with a quality less than the threshold.

[0100] At 1650, the BS may generate and send an RRCReconfiguration message including an NR SCG configuration and / or SCell configuration to the UE, wherein the NR SCG configuration and / or SCell configuration includes at least one frequency / band among the potential CA / DC frequencies / bands configured at 1620 and indicated in the measurement report of 1640.

[0101] See also Figure 17, which shows a flowchart of a fourth exemplary method 1600 that facilitates enhancement of measurement reporting for connected mode UEs in combination with various aspects discussed herein, which enhancement can facilitate DC / CA configuration. Method 1700 provides a second exemplary technique that can address the second problem, wherein for a measurement report triggered by an A3 / A5 event, although the NW in an existing system can determine the target PCell based on the measurement report, it cannot determine the SCG / SCell for CA / DC configuration based on the measurement report because the measurement result can only reflect the best neighboring cell on the current serving frequency and will not reflect the best cell on the potential CA / DC secondary component carrier because the existing system only allows reporting of the best non-serving cell on the serving frequency of the neighboring cell. Method 1700 may be similar to method 1600, but may omit the detailed dedicated configuration provided at 1620. Instead, the NW may provide

[0102] In conjunction with method 1700, an RRC connection may be established (or already established) for the UE (eg, using 400 UE etc.), as shown at 1710.

[0103] At 1720, the BS (eg, using 400 BS etc.) may generate and send an RRCReconfiguration message including a MeasConfig, the MeasConfig configuring a first frequency group associated with the triggered measurement report (eg, Figure 17 F2 in , and allows one or more candidate CA / DC frequencies (e.g., Figure 17 In various embodiments, the NW (e.g., via the BS) may provide the UE with a threshold (e.g., for radio link quality) to determine which potential / candidate CA / DC frequencies may be included as additional reports.

[0104] At 1730, the UE may perform configured measurements, including configured measurements of one or more candidate frequencies for CA / DC. In some embodiments, the candidate frequencies for CA / DC may be determined by the UE based on system information blocks (e.g., SIB4 and SIB5, etc.) generated by the BS. In some embodiments, the candidate frequencies for CA / DC may be determined based on any UE knowledge and may vary based on UE specific implementation.

[0105] At 1740, the UE may generate and send a measurement report to the BS, the measurement report indicating the configured measurements for the first set of frequencies (e.g., F2) and for one or more frequencies / bands in the potential CA / DC frequencies / bands. In various embodiments, the NW may configure (e.g., at 1620) criteria for the UE to determine which frequencies from the potential / candidate CA / DC group to provide as additional reports. For example, the NW may configure a radio link quality threshold (e.g., reference signal (RS) received power (RSRP) / RS received quality (RSRQ) / signal to interference and noise ratio (SINR)), etc.), and the UE may include any frequency groups (e.g., F3 and F4, etc.) with a quality greater than the threshold and associated results in the additional report, while ignoring frequency groups below the threshold.

[0106] At 1750, the BS may generate and send an RRCReconfiguration message including an NR SCG configuration and / or SCell configuration to the UE, wherein the NR SCG configuration and / or SCell configuration includes at least one frequency / band among the potential CA / DC frequencies / bands indicated in the measurement report of 1740.

[0107] See also Figure 18 , which illustrates a flow chart of an exemplary method or process 1800 that can be employed at a UE in accordance with various aspects discussed herein, which facilitates one or more enhancements for measurements in connected mode discussed herein. In other aspects, a machine-readable medium may store instructions associated with the method 1800 that, when executed, may cause a UE (e.g., employing the system 400) to UE ) performs the actions of method 1800. Although method 1800 is provided as one specific exemplary aspect of the techniques discussed herein, it should be understood that other specific exemplary aspects may employ additional and / or alternative techniques.

[0108] At 1810, the UE may optionally send a UE assistance information message including a measurement request. In some embodiments, the measurement request may include one or more of: a single bit indicating the measurement request, the RAT for measurement, one or more potential CA / DC frequency groups for measurement, and / or one or more potential CA / DC frequency groups for measurement in the absence of gaps.

[0109] At 1820, the UE may receive a first RRCReconfiguration message including a measurement configuration for configuring one or more frequency groups for measurement. The one or more frequency groups may include at least one serving frequency or a neighboring cell on a serving frequency. The one or more frequency groups may include at least one CA / DC candidate. In various embodiments, the first RRCReconfiguration message may indicate that the measurement configuration is for CA / DC purposes.

[0110] At 1830, the UE may perform measurements on one or more frequency groups configured via the first RRCReconfiguration message, which in some embodiments may include at least one CA / DC candidate. In some embodiments, although the one or more configured frequency groups do not include a CA / DC candidate, the UE may also perform measurements on at least one CA / DC candidate determined via the SIB or other information at the UE. The measurements may be performed so as not to interrupt ongoing transmissions (e.g., without measurement gaps, during discontinuous reception (DRX) inactivity time, etc.).

[0111] At 1840, the UE may send a measurement report message indicating at least some of the frequency groups measured at 1830 and associated measurements for the reported frequency groups. In some embodiments, the measurement report may include a serving frequency or a neighboring cell on the serving frequency and at least one CA / DC candidate. In some embodiments, the UE may report measurements for CA / DC candidates having at least a threshold radio link quality (e.g., where the threshold may be configured in the first RRCReconfiguration message at 1820, etc.). In some embodiments, the UE may report all measured CA / DC candidates.

[0112] At 1850 , the UE may receive a second RRCReconfiguration message that configures the UE with at least one of the CA / DC candidates (eg, for SCell configuration, SCG configuration, or some other CA / DC configuration).

[0113] Additionally or alternatively, the method 1800 may include the following: UE One or more other actions described in various aspects.

[0114] See also Figure 19, which illustrates a flow chart of an exemplary method or process 1900 that can be employed at a BS in accordance with various aspects discussed herein to facilitate one or more enhancements discussed herein for measurements performed by a UE in connected mode. In other aspects, a machine-readable medium may store instructions associated with the method 1900 that, when executed, may cause a BS (e.g., employing the system 400) to BS ) performs the actions of method 1900. Although method 1900 is provided as one specific exemplary aspect of the techniques discussed herein, it should be understood that other specific exemplary aspects may employ additional and / or alternative techniques.

[0115] At 1910, the BS may optionally receive a UE assistance information message including a measurement request. In some embodiments, the measurement request may include one or more of: a single bit indicating the measurement request, the RAT for measurement, one or more potential CA / DC frequency groups for measurement, and / or one or more potential CA / DC frequency groups for measurement in the absence of gaps.

[0116] At 1920, the base station may send a first RRCReconfiguration message including a measurement configuration for configuring one or more frequency groups for measurement. The one or more frequency groups may include at least one serving frequency or a neighboring cell on a serving frequency. The one or more frequency groups may include at least one CA / DC candidate. In various embodiments, the first RRCReconfiguration message may indicate that the measurement configuration is for CA / DC purposes.

[0117] At 1930, the BS may receive a measurement report message indicating at least some frequency groups measured by the UE based on the first RRCReconfiguration message and associated measurements for the reported frequency groups. In some embodiments, the measurement report may include a serving frequency or a neighboring cell on the serving frequency and at least one CA / DC candidate. In some embodiments, the UE may report measurements of CA / DC candidates having at least a threshold radio link quality (e.g., where the threshold may be configured in the first RRCReconfiguration message at 1920, etc.). In some embodiments, the UE may report all measured CA / DC candidates.

[0118] At 1940 , the BS may send a second RRCReconfiguration message that configures the UE with at least one of the CA / DC candidates (eg, for SCell configuration, SCG configuration, or some other CA / DC configuration).

[0119] Additionally or alternatively, the method 1900 may include the following: BS One or more other actions described in various aspects.

[0120] Additional Examples

[0121] Embodiments herein may include subject matter such as a method, components for performing the actions or blocks of the method, and at least one machine-readable medium comprising 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 the actions of the method or apparatus or system for concurrent communication using multiple communication technologies according to the described aspects and examples.

[0122] Embodiment 1 is a baseband processor configured to perform operations including the following: optionally, generating a UE assistance information message for transmission, wherein the UE assistance information message includes a measurement request; receiving a first RRCReconfiguration message including a measConfig information element (IE); performing one or more measurements on each of one or more frequency groups based at least on the measConfig IE, wherein the one or more frequency groups include a non-service frequency group associated with a neighboring cell; generating a MeasurementReport message for transmission, wherein the MeasurementReport message indicates the one or more measurements on at least one of the one or more frequency groups, wherein the one or more frequency groups include a service frequency group for a serving cell or one of the neighboring cells and the non-service frequency group associated with the neighboring cell; and receiving a second RRCReconfiguration message, wherein the second RRCReconfiguration message configures the UE using the at least one frequency group of the one or more frequency groups.

[0123] Embodiment 2 includes the subject matter of any variation of any one of Embodiment 1, wherein the first RRCReconfiguration message is received in response to the UE assistance information message.

[0124] Embodiment 3 includes the subject matter of any variation of any one of Embodiments 1 to 2, wherein the measurement request comprises one or more of: a single bit indicating the measurement request, an indication of the radio access technology (RAT) to be measured, the one or more frequency groups, or a first frequency group of the one or more frequency groups to be measured in the absence of a measurement gap.

[0125] Embodiment 4 includes the subject matter of any variant of any one of Embodiments 1 to 3, wherein the measConfig IE configures the UE to measure the non-serving frequency group associated with the neighboring cell, wherein the first RRCReconfiguration message indicates a purpose of one or more of carrier aggregation (CA) or dual connectivity (DC), wherein the purpose is indicated via one or more of a measurement report configuration or a measurement object configuration.

[0126] Embodiment 5 includes the subject matter of any variant of any one of embodiments 1 to 4, wherein the operation further comprises: starting, based at least on the measConfig IE, performing the one or more measurements on each of the one or more frequency groups immediately after receiving the first RRCReconfiguration message or in response to a determination by the UE of a configuration for one or more of carrier aggregation (CA) or dual connectivity (DC).

[0127] Embodiment 6 includes the subject matter of any variation of any one of embodiments 1 to 5, wherein the operation comprises performing the one or more measurements on each of the one or more frequency groups without a measurement gap or during discontinuous reception (DRX) inactive time.

[0128] Embodiment 7 includes the subject matter of any variation of any one of Embodiments 1 to 6, wherein the measConfig IE indicates the non-serving frequency group associated with the neighboring cell via a measurement object associated with the serving frequency group.

[0129] Embodiment 8 includes the subject matter of any variation of any one of Embodiments 1 to 7, wherein at least one of the one or more frequency groups includes the non-service frequency group when the one or more measurements for the non-service frequency group exceeds a threshold configured for the one or more measurements.

[0130] Embodiment 9 includes the subject matter of any variation of any one of Embodiments 1 to 8, wherein the operations further comprise determining the non-serving frequency group from a system information block (SIB) associated with neighbor cell measurements.

[0131] Embodiment 10 is a machine-readable medium comprising instructions that, when executed, cause a user equipment (UE) to: optionally, send a UE assistance information message comprising a measurement request; receive a first RRCReconfiguration message comprising a measConfig information element (IE); perform one or more measurements on each of one or more frequency groups based at least on the measConfig IE, wherein the one or more frequency groups include a non-serving frequency group associated with a neighboring cell; send a MeasurementReport message, wherein the MeasurementReport message indicates the one or more measurements on at least one of the one or more frequency groups, wherein the one or more frequency groups include a serving frequency group for a serving cell or one of the neighboring cells and the non-serving frequency group associated with the neighboring cell; and receive a second RRCReconfiguration message, wherein the second RRCReconfiguration message configures the UE using the at least one frequency group of the one or more frequency groups.

[0132] Embodiment 11 includes the subject matter of any variation of any one of Embodiment 10, wherein the first RRCReconfiguration message is received in response to the UE assistance information message.

[0133] Embodiment 12 includes the subject matter of any variation of any one of Embodiments 10 to 11, wherein the measurement request comprises one or more of: a single bit indicating the measurement request, an indication of a radio access technology (RAT) to be measured, the one or more frequency groups, or a first frequency group of the one or more frequency groups to be measured in the absence of a measurement gap.

[0134] Embodiment 13 includes the subject matter of any variant of any one of Embodiments 10 to 12, wherein the measConfig IE configures the UE to measure the non-serving frequency group associated with the neighboring cell, wherein the first RRCReconfiguration message indicates a purpose of one or more of carrier aggregation (CA) or dual connectivity (DC), wherein the purpose is indicated via one or more of a measurement report configuration or a measurement object configuration.

[0135] Embodiment 14 includes the subject matter of any variant of any one of embodiments 10 to 13, wherein the instructions, when executed, further cause the UE to: based at least on the measConfig IE, immediately after receiving the first RRCReconfiguration message or in response to a determination by the UE of a configuration for one or more of carrier aggregation (CA) or dual connectivity (DC), start performing the one or more measurements on each of the one or more frequency groups.

[0136] Embodiment 15 includes the subject matter of any variation of any one of embodiments 10 to 14, wherein the instructions, when executed, cause the UE to perform the one or more measurements on each of the one or more frequency groups without a measurement gap or during discontinuous reception (DRX) inactive time.

[0137] Embodiment 16 includes the subject matter of any variation of any one of Embodiments 10 to 15, wherein the measConfig IE indicates the non-serving frequency group associated with the neighboring cell via a measurement object associated with the serving frequency group.

[0138] Embodiment 17 includes the subject matter of any variation of any one of Embodiments 10 to 16, wherein at least one of the one or more frequency groups includes the non-service frequency group when the one or more measurements for the non-service frequency group exceeds a threshold configured for the one or more measurements.

[0139] Embodiment 18 includes the subject matter of any variation of any one of Embodiments 10 to 17, wherein the instructions, when executed, further cause the UE to determine the non-serving frequency group from a system information block (SIB) associated with neighbor cell measurements.

[0140] Embodiment 19 is a user equipment (UE) device, which includes a processor configured to perform operations including the following items: optionally, sending a UE assistance information message including a measurement request; receiving a first RRCReconfiguration message including a measConfig information element (IE); performing one or more measurements on each of one or more frequencies based at least on the RRC measConfig IE, wherein the one or more frequencies include at least one non-serving frequency associated with a neighboring cell; sending a MeasurementReport message, the MeasurementReport message indicating the one or more measurements for at least one of the one or more frequencies; and receiving a second RRCReconfiguration message, which configures the UE using the at least one of the one or more frequencies.

[0141] Embodiment 20 includes the subject matter of any variation of any one of Embodiment 19, wherein the first RRCReconfiguration message is received in response to the UE assistance information message.

[0142] Embodiment 21 includes the subject matter of any variant of any one of Embodiments 19 to 20, wherein the measurement request includes one or more of: a single bit indicating the measurement request, an indication of a radio access technology (RAT) to be measured, the one or more frequency groups, or a first frequency group in the one or more frequency groups to be measured in the absence of a measurement gap.

[0143] Embodiment 22 includes the subject matter of any variant of any one of embodiments 19 to 21, wherein the measConfig IE configures the UE to measure the non-serving frequency group associated with the neighboring cell, wherein the first RRCReconfiguration message indicates a purpose of one or more of carrier aggregation (CA) or dual connectivity (DC), wherein the purpose is indicated via one or more of a measurement report configuration or a measurement object configuration.

[0144] Embodiment 23 includes the subject matter of any variant of any one of embodiments 19 to 22, wherein the operation further comprises: based at least on the measConfig IE, immediately after receiving the first RRCReconfiguration message or in response to a determination by the UE of a configuration for one or more of carrier aggregation (CA) or dual connectivity (DC), starting to perform the one or more measurements on each of the one or more frequency groups.

[0145] Embodiment 24 includes the subject matter of any variation of any one of embodiments 19 to 23, wherein the operation comprises performing the one or more measurements on each of the one or more frequency groups in the absence of a measurement gap or during discontinuous reception (DRX) inactive time.

[0146] Embodiment 25 includes the subject matter of any variation of any one of Embodiments 19 to 24, wherein the measConfig IE indicates the non-serving frequency group associated with the neighboring cell via a measurement object associated with the serving frequency group.

[0147] Embodiment 26 includes the subject matter of any variation of any one of Embodiments 19 to 25, wherein at least one of the one or more frequency groups includes the non-service frequency group when the one or more measurements for the non-service frequency group exceeds a threshold configured for the one or more measurements.

[0148] Embodiment 27 includes the subject matter of any variation of any one of Embodiments 19 to 26, wherein the operations further comprise determining the non-serving frequency group from a system information block (SIB) associated with neighbor cell measurements.

[0149] Embodiment 28 is a baseband processor configured to perform operations including the following: receiving a first RRCReconfiguration message including a measConfig information element (IE); performing one or more measurements on each of one or more frequency groups based at least on the measConfigIE, wherein the one or more frequency groups include a non-service frequency group associated with a neighboring cell; generating a MeasurementReport message for transmission, wherein the MeasurementReport message indicates the one or more measurements on at least one of the one or more frequency groups, wherein the one or more frequency groups include a service frequency group for a serving cell or one of the neighboring cells and the non-service frequency group associated with the neighboring cell; and receiving a second RRCReconfiguration message, wherein the second RRCReconfiguration message configures the UE using the at least one frequency group of the one or more frequency groups.

[0150] Embodiment 29 includes the subject matter of any variation of any one of Embodiment 28, wherein the operation further comprises generating a UE assistance information message for transmission, wherein the UE assistance information message includes a measurement request, and wherein the first RRCReconfiguration message is received in response to the UE assistance information message.

[0151] Embodiment 30 includes the subject matter of any variant of any one of embodiments 28 to 29, wherein the measurement request includes one or more of: a single bit indicating the measurement request, an indication of the radio access technology (RAT) to be measured, the one or more frequency groups, or a first frequency group of the one or more frequency groups to be measured in the absence of a measurement gap.

[0152] Embodiment 31 includes the subject matter of any variant of any one of embodiments 28 to 30, wherein the measConfig IE configures the UE to measure the non-serving frequency group associated with the neighboring cell, wherein the first RRCReconfiguration message indicates a purpose of one or more of carrier aggregation (CA) or dual connectivity (DC), wherein the purpose is indicated via one or more of a measurement report configuration or a measurement object configuration.

[0153] Embodiment 32 includes the subject matter of any variant of any one of embodiments 28 to 31, wherein the operation further comprises: based at least on the measConfig IE, immediately after receiving the first RRCReconfiguration message or in response to a determination by the UE of a configuration for one or more of carrier aggregation (CA) or dual connectivity (DC), starting to perform the one or more measurements on each of the one or more frequency groups.

[0154] Embodiment 33 includes the subject matter of any variation of any one of Embodiments 28 to 32, wherein the operation comprises performing the one or more measurements on each of the one or more frequency groups in the absence of a measurement gap or during discontinuous reception (DRX) inactive time.

[0155] Embodiment 34 includes the subject matter of any variation of any one of Embodiments 28 to 33, wherein the measConfig IE indicates the non-serving frequency group associated with the neighboring cell via a measurement object associated with the serving frequency group.

[0156] Embodiment 35 includes the subject matter of any variation of any one of Embodiments 28 to 34, wherein at least one of the one or more frequency groups includes the non-service frequency group when the one or more measurements for the non-service frequency group exceeds a threshold configured for the one or more measurements.

[0157] Embodiment 36 includes the subject matter of any variation of any one of Embodiments 28 to 35, wherein the operations further comprise determining the non-serving frequency group from a system information block (SIB) associated with neighbor cell measurements.

[0158] Embodiment 37 comprises an apparatus comprising means for performing any of the operations of embodiments 1-36.

[0159] Embodiment 38 includes a machine-readable medium storing instructions for execution by a processor to perform any of the operations of embodiments 1-36.

[0160] Embodiment 39 includes an apparatus comprising: a memory interface; and a processing circuit configured to: perform any of the operations of embodiments 1 to 36.

[0161] Embodiment 40 includes a user equipment (UE), which is configured to perform any one of the operations of embodiments 1 to 36.

[0162] Embodiment 41 is a baseband processor configured to perform operations including the following: receiving a UE assistance information message including a measurement request; generating a first RRCReconfiguration message for transmission, wherein the first RRCReconfiguration message includes a measConfig information element (IE); receiving a MeasurementReport message from a user equipment (UE) indicating one or more measurements of one or more frequency groups, wherein the one or more frequency groups include a serving frequency group for a serving cell or one of the neighboring cells and a non-serving frequency group for the UE, wherein the non-serving frequency group is associated with the neighboring cell; and generating a second RRCReconfiguration message for transmission, wherein the second RRCReconfiguration message configures the UE using at least one of the one or more frequency groups.

[0163] Embodiment 42 includes the subject matter of any variation of any one of Embodiment 41, wherein the first RRCReconfiguration message is generated in response to the UE assistance information message.

[0164] Embodiment 43 includes the subject matter of any variant of any one of embodiments 41 to 42, wherein the measurement request comprises one or more of: a single bit indicating the measurement request, an indication of the radio access technology (RAT) to be measured, the one or more frequency groups, or a first frequency group of the one or more frequency groups to be measured in the absence of a measurement gap.

[0165] Embodiment 44 includes the subject matter of any variant of any one of embodiments 41 to 43, wherein the measConfig IE configures the UE to measure the non-serving frequency group associated with the neighboring cell, wherein the first RRCReconfiguration message indicates a purpose of one or more of carrier aggregation (CA) or dual connectivity (DC), wherein the purpose is indicated via one or more of a measurement report configuration or a measurement object configuration.

[0166] Embodiment 45 includes the subject matter of any variation of any one of Embodiments 41 to 44, wherein the measConfig IE indicates the non-serving frequency group associated with the neighboring cell via a measurement object associated with the serving frequency group.

[0167] Embodiment 46 includes the subject matter of any variation of any one of Embodiments 41 to 45, wherein the one or more frequency groups include the non-serving frequency group when the one or more measurements for the non-serving frequency group exceed a threshold configured for the one or more measurements.

[0168] Embodiment 47 includes the subject matter of any variation of any one of Embodiments 41 to 46, wherein the operations further comprise generating a system information block (SIB) associated with neighbor cell measurements indicating the non-serving frequency group.

[0169] Embodiment 48 is a machine-readable medium comprising instructions that, when executed, cause a base station (BS) to: receive a UE assistance information message comprising a measurement request; send a first RRCReconfiguration message comprising a measConfig information element (IE); receive a MeasurementReport message from a user equipment (UE) indicating one or more measurements of one or more frequency groups, wherein the one or more frequency groups include a serving frequency group for a serving cell or one of the neighboring cells and a non-serving frequency group for the UE, wherein the non-serving frequency group is associated with the neighboring cell; and send a second RRCReconfiguration message that configures the UE using at least one of the one or more frequency groups.

[0170] Embodiment 49 includes the subject matter of any variation of any one of Embodiment 48, wherein the first RRCReconfiguration message is generated in response to the UE assistance information message.

[0171] Embodiment 50 includes the subject matter of any variant of any one of Embodiments 48 to 49, wherein the measurement request comprises one or more of: a single bit indicating the measurement request, an indication of a radio access technology (RAT) to be measured, the one or more frequency groups, or a first frequency group of the one or more frequency groups to be measured in the absence of a measurement gap.

[0172] Embodiment 51 includes the subject matter of any variant of any one of embodiments 48 to 50, wherein the measConfig IE configures the UE to measure the non-serving frequency group associated with the neighboring cell, wherein the first RRCReconfiguration message indicates a purpose of one or more of carrier aggregation (CA) or dual connectivity (DC), wherein the purpose is indicated via one or more of a measurement report configuration or a measurement object configuration.

[0173] Embodiment 52 includes the subject matter of any variation of any one of Embodiments 48 to 51, wherein the measConfig IE indicates the non-serving frequency group associated with the neighboring cell via a measurement object associated with the serving frequency group.

[0174] Embodiment 53 includes the subject matter of any variation of any one of Embodiments 48 to 52, wherein the one or more frequency groups include the non-serving frequency group when the one or more measurements for the non-serving frequency group exceed a threshold configured for the one or more measurements.

[0175] Embodiment 54 includes the subject matter of any variation of any one of Embodiments 48 to 53, wherein the instructions, when executed, further cause the UE to generate a system information block (SIB) associated with neighbor cell measurements indicating the non-serving frequency group.

[0176] Embodiment 55 is a base station (BS) device, which includes a processor configured to perform operations including the following items: receiving a UE assistance information message including a measurement request; sending a first RRCReconfiguration message including a measConfig information element (IE); receiving a MeasurementReport message from a user equipment (UE) indicating one or more measurements of one or more frequency groups, wherein the one or more frequency groups include a serving frequency group for a serving cell or one of the neighboring cells and a non-serving frequency group for the UE, wherein the non-serving frequency group is associated with the neighboring cell; and sending a second RRCReconfiguration message, which configures the UE using at least one frequency group of the one or more frequency groups.

[0177] Embodiment 56 includes the subject matter of any variation of any one of Embodiment 55, wherein the first RRCReconfiguration message is generated in response to the UE assistance information message.

[0178] Embodiment 57 includes the subject matter of any variation of any one of Embodiments 55 to 56, wherein the measurement request comprises one or more of: a single bit indicating the measurement request, an indication of the radio access technology (RAT) to be measured, the one or more frequency groups, or a first frequency group in the one or more frequency groups to be measured in the absence of a measurement gap.

[0179] Embodiment 58 includes the subject matter of any variant of any one of embodiments 55 to 57, wherein the measConfig IE configures the UE to measure the non-serving frequency group associated with the neighboring cell, wherein the first RRCReconfiguration message indicates a purpose of one or more of carrier aggregation (CA) or dual connectivity (DC), wherein the purpose is indicated via one or more of a measurement report configuration or a measurement object configuration.

[0180] Embodiment 59 includes the subject matter of any variation of any one of Embodiments 55 to 58, wherein the measConfig IE indicates the non-serving frequency group associated with the neighboring cell via a measurement object associated with the serving frequency group.

[0181] Embodiment 60 includes the subject matter of any variation of any one of Embodiments 55 to 59, wherein the one or more frequency groups include the non-serving frequency group when the one or more measurements for the non-serving frequency group exceed a threshold configured for the one or more measurements.

[0182] Embodiment 61 includes the subject matter of any variation of any one of Embodiments 55 to 60, wherein the operations further comprise generating a system information block (SIB) associated with neighbor cell measurements indicating the non-serving frequency group.

[0183] Embodiment 62 is a base station (BS) device, which includes a processor configured to perform operations including the following items: sending a first RRCReconfiguration message including a measConfig information element (IE); receiving a MeasurementReport message from a user equipment (UE) indicating one or more measurements of one or more frequency groups, wherein the one or more frequency groups include a serving frequency group for a serving cell or one of the neighboring cells and a non-serving frequency group for the UE, wherein the non-serving frequency group is associated with the neighboring cell; and sending a second RRCReconfiguration message, which configures the UE using at least one frequency group of the one or more frequency groups.

[0184] Embodiment 63 includes the subject matter of any variation of any one of Embodiment 62, wherein the operation further comprises receiving a UE assistance information message for transmission, wherein the UE assistance information message comprises a measurement request, and wherein the first RRCReconfiguration message is generated in response to the UE assistance information message.

[0185] Embodiment 64 includes the subject matter of any variant of any one of Embodiments 62 to 63, wherein the measurement request comprises one or more of: a single bit indicating the measurement request, an indication of a radio access technology (RAT) to be measured, the one or more frequency groups, or a first frequency group of the one or more frequency groups to be measured in the absence of a measurement gap.

[0186] Embodiment 65 includes the subject matter of any variant of any one of embodiments 62 to 64, wherein the measConfig IE configures the UE to measure the non-serving frequency group associated with the neighboring cell, wherein the first RRCReconfiguration message indicates a purpose of one or more of carrier aggregation (CA) or dual connectivity (DC), wherein the purpose is indicated via one or more of a measurement report configuration or a measurement object configuration.

[0187] Embodiment 66 includes the subject matter of any variation of any one of Embodiments 62 to 65, wherein the measConfig IE indicates the non-serving frequency group associated with the neighboring cell via a measurement object associated with the serving frequency group.

[0188] Embodiment 67 includes the subject matter of any variation of any one of Embodiments 62 to 66, wherein the one or more frequency groups include the non-serving frequency group when the one or more measurements for the non-serving frequency group exceed a threshold configured for the one or more measurements.

[0189] Embodiment 68 includes the subject matter of any variation of any one of Embodiments 62 to 67, wherein the operations further comprise generating a system information block (SIB) associated with neighbor cell measurements indicating the non-serving frequency group.

[0190] Embodiment 69 comprises an apparatus comprising means for performing any of the operations of embodiments 41-68.

[0191] Embodiment 70 includes a machine-readable medium storing instructions for execution by a processor to perform any of the operations of embodiments 41 to 68.

[0192] Embodiment 71 includes an apparatus comprising: a memory interface; and a processing circuit configured to: perform any of the operations of embodiments 41 to 68.

[0193] Embodiment 72 includes a base station (BS) configured to perform any one of the operations of embodiments 41 to 68.

[0194] The above description of exemplary aspects of the disclosed subject matter, including what is described in the Abstract, is not intended to be exhaustive or to limit the disclosed aspects to the precise forms disclosed. Although specific aspects and embodiments are described herein for illustrative purposes, various modifications are contemplated within the scope of such aspects and embodiments, as those skilled in the relevant art will recognize.

[0195] In this regard, although the subject matter disclosed herein has been described in conjunction with various aspects and corresponding drawings, it should be understood that other similar aspects may be used or modifications and additions may be made to the described aspects to perform the same, similar, alternative, or alternative functions of the disclosed subject matter without departing from the described aspects. Accordingly, the disclosed subject matter should not be limited to any single aspect described herein, but rather should be construed in accordance with the breadth and scope of the claims appended hereto.

[0196] In particular, with respect to the various functions performed by the aforementioned components or structures (assemblies, devices, circuits, systems, etc.), unless otherwise indicated, the terms used to describe such components (including references to "members") are intended to correspond to any component or structure that performs the specified function of the component (e.g., functionally equivalent), even if not structurally equivalent to the disclosed structures that perform the functions in the exemplary implementations shown herein. In addition, while particular features have been disclosed with respect to only one of a number of implementations, for any given or particular application, such features may be combined with one or more other features of other implementations, as may be desirable and advantageous.

Claims

1. A user equipment (UE) device, the UE device comprising a processor, the processor configured to perform operations including the following items: receiving a first RRCReconfiguration message including a measConfig information element (IE), wherein the first RRCReconfiguration message explicitly indicates a purpose of one or more of carrier aggregation (CA) or dual connectivity (DC), and wherein the measConfig IE configures one or more measurements of a non-serving frequency group associated with a neighboring cell; generating a MeasurementReport message indicating the one or more measurements; and A second RRCReconfiguration message is received, where the second RRCReconfiguration message configures the one or more of CA or DC. 2 . The UE device according to claim 1 , wherein the first RRCReconfiguration message is received in response to a measurement request.

3. The UE device of claim 2 , wherein the measurement request comprises one or more of: a single bit indicating the measurement request, an indication of a radio access technology (RAT) for measurement, the non-serving frequency group, or a first frequency group in the non-serving frequency group for measurement in the absence of a measurement gap. 4 . The UE device of claim 1 , wherein the purpose is indicated via one or more of a measurement report configuration or a measurement object configuration.

5. The UE device according to claim 1, wherein the operation further comprises: Based at least on the measConfig IE, the one or more measurements are performed after receiving the first RRCReconfiguration message.

6. The UE device according to claim 1, wherein the operation comprises: The one or more measurements are performed without a measurement gap or during a discontinuous reception (DRX) inactive time. 7 . The UE device according to claim 1 , wherein the measConfig IE indicates the non-serving frequency group associated with the neighboring cell via a measurement object associated with a serving frequency group.

8. The UE device according to any one of claims 1 to 6, wherein when the one or more measurements for the non-serving frequency group exceed a threshold configured for the one or more measurements, the non-serving frequency group is configured in the MeasurementReport message.

9. The UE device of any one of claims 1 to 6, wherein the operations further comprise determining the non-serving frequency group from a system information block (SIB) associated with neighbor cell measurements.

10. A machine-readable medium comprising instructions that, when executed, cause a user equipment (UE): receiving a first RRCReconfiguration message including a measConfig information element (IE), wherein the first RRCReconfiguration message explicitly indicates a purpose of one or more of carrier aggregation (CA) or dual connectivity (DC), and wherein the measConfig IE configures one or more measurements of a non-serving frequency group associated with a neighboring cell; sending a MeasurementReport message, wherein the MeasurementReport message indicates the one or more measurements; and A second RRCReconfiguration message is received, where the second RRCReconfiguration message configures the one or more of CA or DC.

11. The machine-readable medium of claim 10, wherein the first RRCReconfiguration message is received in response to a measurement request.

12. The machine-readable medium of claim 11 , wherein the measurement request comprises one or more of: a single bit indicating the measurement request, an indication of a radio access technology (RAT) to use for measurement, the non-serving frequency group, or a first frequency group in the non-serving frequency group to use for measurement in the absence of a measurement gap.

13. The machine-readable medium of claim 10, wherein the purpose is indicated via one or more of a measurement report configuration or a measurement object configuration.

14. The machine-readable medium of claim 10, wherein the instructions, when executed, further cause the UE to: perform the one or more measurements after receiving the first RRCReconfiguration message based on at least the measConfig IE.

15. The machine-readable medium of claim 10, wherein the instructions, when executed, cause the UE to perform the one or more measurements without a measurement gap or during a discontinuous reception (DRX) inactive time.

16. The machine-readable medium of any one of claims 10 to 15, wherein the measConfig IE indicates the non-serving frequency group associated with the neighboring cell via a measurement object associated with a serving frequency group.

17. The machine-readable medium of any one of claims 10 to 15, wherein the non-serving frequency group is configured in the MeasurementReport message when the one or more measurements for the non-serving frequency group exceed a threshold configured for the one or more measurements.

18. The machine-readable medium of any one of claims 10 to 15, wherein the instructions, when executed, further cause the UE to determine the non-serving frequency group from a system information block (SIB) associated with neighbor cell measurements.

19. A user equipment (UE) device, the UE device comprising a processor, the processor configured to perform operations comprising: generating a UE assistance information message including a measurement request for transmission to a base station; receiving, from the base station in response to the UE assistance information message, a first RRCReconfiguration message, the first RRCReconfiguration message including a measConfig information element (IE), wherein the measConfig IE configures one or more measurements of a non-serving frequency group associated with a neighboring cell; sending a MeasurementReport message, the MeasurementReport message indicating the one or more measurements; and A second RRCReconfiguration message is received, where the second RRCReconfiguration message configures the UE device using the neighboring cell.

20. The UE device of claim 19, wherein the measurement request comprises one or more of: a single bit indicating the measurement request, an indication of a radio access technology (RAT) for measurement, the non-serving frequency group, or a first frequency group in the non-serving frequency group for measurement in the absence of a measurement gap.

21. The UE device of claim 19, wherein the first RRCReconfiguration message indicates a purpose of one or more of carrier aggregation (CA) or dual connectivity (DC), wherein the purpose is indicated via one or more of measurement report configuration or measurement object configuration.

22. The UE device of claim 19, wherein the operations further comprise: Based at least on the measConfig IE, the one or more measurements are performed after receiving the first RRCReconfiguration message.

23. The UE device of claim 19, wherein the operations comprise: The one or more measurements are performed without a measurement gap or during a discontinuous reception (DRX) inactive time.

24. The UE device according to any one of claims 19 to 23, wherein the measConfig IE indicates the non-serving frequency group associated with the neighboring cell via a measurement object associated with at least one serving frequency.

25. The UE device according to any one of claims 19 to 23, wherein when the one or more measurements for the non-serving frequency group exceed a threshold configured for the one or more measurements, the non-serving frequency group is configured in the MeasurementReport message.

26. The UE device of any one of claims 19 to 23, wherein the operations further comprise determining the non-serving frequency group from a system information block (SIB) associated with neighbor cell measurements.

27. A machine-readable medium comprising instructions that, when executed, cause a user equipment (UE) to perform operations comprising: receiving a first RRCReconfiguration message including a measConfig information element (IE), wherein the first RRCReconfiguration message explicitly indicates a purpose of one or more of carrier aggregation (CA) or dual connectivity (DC), and wherein the measConfig IE configures one or more measurements of a non-serving frequency group associated with a neighboring cell; generating a MeasurementReport message for transmission, wherein the MeasurementReport message indicates the one or more measurements; and A second RRCReconfiguration message is received, wherein the second RRCReconfiguration message configures the UE with the one or more of CA or DC.

28. The machine-readable medium of claim 27, wherein the operations further comprise generating a UE assistance information message for transmission to a base station, wherein the UE assistance information message comprises a measurement request, and wherein the first RRCReconfiguration message is received in response to the UE assistance information message.

29. The machine-readable medium of claim 28, wherein the measurement request comprises one or more of: a single bit indicating the measurement request, an indication of a radio access technology (RAT) to use for measurement, or the non-serving frequency group to use for measurement without a measurement gap.

30. The machine-readable medium of claim 27, wherein the purpose is indicated via one or more of a measurement report configuration or a measurement object configuration.

31. The machine-readable medium of claim 27, wherein the operations further comprise: Based at least on the measConfig IE, the one or more measurements are performed after receiving the first RRCReconfiguration message.

32. The machine-readable medium of claim 27, wherein the operations comprise: The one or more measurements are performed without a measurement gap or during a discontinuous reception (DRX) inactive time.

33. The machine-readable medium of any one of claims 27 to 32, wherein the measConfig IE indicates the non-serving frequency group associated with the neighboring cell via a measurement object associated with a serving frequency group.

34. The machine-readable medium of any one of claims 27 to 32, wherein the non-serving frequency group is configured in the MeasurementReport message when the one or more measurements for the non-serving frequency group exceed a threshold configured for the one or more measurements.

35. The machine-readable medium of any one of claims 27 to 32, wherein the operations further comprise determining the non-serving frequency group from a system information block (SIB) associated with neighbor cell measurements.

Images