Measurement extension in radio resource control (RRC) connected for a base station (BS)

Abstract

[0003] Techniques described herein facilitate base station (BS) enhancements for measurements by RRC connected mode user equipment (UE) for carrier aggregation (CA) and / or dual connectivity (DC) configurations. One example embodiment comprises a BS device including a processor configured to perform operations including receiving a UE Assistance Information message including a measurement request, transmitting a first RRC Reconfiguration message including a measConfig IE, receiving from the user equipment (UE) a Measurement Report message indicating one or more measurements on one or more sets of frequencies, the one or more sets of frequencies including a serving frequency set for the serving cell or one of neighboring cells and a non-serving frequency set for the UE, the non-serving frequency set being associated with the neighboring cell, and transmitting a second RRC Reconfiguration message to configure the UE with at least one of the one or more sets of frequencies.

Description

Background Art

[0001] Mobile communications in next-generation wireless communication systems, 5G, or new radio (NR) networks provide connectivity and access to information everywhere, as well as data sharing capabilities worldwide. 5G networks and network slicing are unified service-based frameworks that aim to provide services for very heterogeneous application areas, from meeting multi-purpose and sometimes conflicting performance criteria, from enhanced mobile broadband (eMBB) to massive machine-type communications (mMTC), ultra-reliable low-latency communications (URLLC), and other communications. Generally, NR evolves based on the long-term evolution (LTE) advanced technology of the third generation partnership project (3GPP (registered trademark)) and uses additional enhanced radio access technologies (RATs) to enable seamless and faster wireless connectivity solutions.

Brief Description of the Drawings

[0002]

Figure 1

[0003]

Figure 2

[0004]

Figure 3

[0005]

Figure 4

[0006]

Figure 5

[0007]

Figure 6

[0008]

Figure 7

[0009]

Figure 8

[0010]

Figure 9

[0011]

Figure 10

[0012]

Figure 11

[0013]

Figure 12

[0014]

Figure 13

[0015]

Figure 14

[0016]

Figure 15

[0017]

Figure 16

[0018]

Figure 17

[0019]

Figure 18

[0020]

Figure 19

[0021] Here, the present disclosure will be described with reference to the accompanying drawings, where like reference numerals are used throughout to refer to like elements, and the structures and devices illustrated are not necessarily drawn to scale. As used herein, terms such as "component", "system", "interface", etc. are intended to refer to computer-related entities, hardware, (e.g., running) software, and / or firmware. For example, a component can be a processor (e.g., a microprocessor, a controller, or other processing device), a process running on the processor, a controller, an object, an executable file, a program, a storage device, a computer, a tablet PC, and / or a user device equipped with a processing device (e.g., a mobile phone or other device configured to communicate via a 3GPP (registered trademark) RAN, etc.). As an example, an application running on a server and the server itself can also be components. One or more components can reside within a process, one component can be localized on one computer, and / or can be distributed among two or more computers. Although this specification may describe a set of elements or other set of components, the term "set" can be interpreted as "one or more" unless the context indicates otherwise (e.g., "an empty set", "a set of two or more X's", etc.).

[0022] Furthermore, these components can be executed, for example, in modules, from various computer-readable storage media having various data structures stored therein. Components can communicate via local and / or remote processes according to signals, for example, having one or more data packets (e.g., data from a component that interacts with another component via a signal across a local system, a distributed system, and / or a network, such as the Internet, a local area network, a wide area network, or other similar network).

[0023] As another example, a component can be a device having specific functionality provided by a mechanical part operated by an electrical or electronic circuit, and the electrical or electronic circuit can be operated by a software application or a firmware application executed by one or more processors. The one or more processors can be inside or outside the device and can execute at least a part of the software or firmware application. As yet another example, a component can be a device that provides specific functionality through an electronic component without mechanical parts, and the electronic component can include one or more processors that execute software and / or firmware that at least partially imparts the functionality of the electronic component.

[0024] The use of the word "exemplary" is intended to concretely represent a concept. The term "or" as used in this application is intended to mean an inclusive "or" rather than an exclusive "or". That is, unless otherwise specified or clear from the context, "X uses A or B" is intended to mean any of all possible permutations. That is, in the case where "X uses A", in the case where "X uses B", or in the case where "X uses both A and B", each of the foregoing cases satisfies "X uses A or B". In addition, the articles "a" and "an" 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 that they refer to the singular form. Further, when "including", "includes", "having", "has", "with", or variations thereof are used in either the embodiments of the invention or the claims, these terms are intended to be as inclusive as the term "comprising". Further, in situations where one or more numbered items are detailed (e.g., "the first X", "the second X", etc.), in some situations, the context may indicate whether the one or more numbered items are distinct or the same, but generally, these one or more numbered items can be distinct or the same.

[0025] As used herein, the term "circuit" may refer to, be part of, or include an Application Specific Integrated Circuit (ASIC), an electronic circuit, a processor (shared, dedicated, or group), and / or a memory (shared, dedicated, or group), combinational logic circuit, and / or other suitable hardware components that execute one or more software programs or firmware programs, and that provide the described functionality. In some aspects, the circuit may be implemented in one or more software or firmware modules, or functions associated with the circuit may be executed by one or more software or firmware modules. In some aspects, the circuit can include logic that is at least partially operable in hardware.

[0026] The various aspects described herein may be related to facilitating wireless communications, and the nature of these communications may vary.

[0027] It is well understood that the use of personal information should comply with privacy policies and practices that are generally recognized as meeting or exceeding industry or government requirements for maintaining user privacy. In particular, personal information data should be managed and handled to minimize the risk of unintended or unauthorized access or use, and the nature of the permitted use should be clearly disclosed to the user.

[0028] Aspects described herein can be implemented in a system using any suitably configured hardware and / or software. FIG. 1 shows an architecture of a system 100 that includes a core network (CN) 120, e.g., a 5th Generation (5G) CN (5GC), according to various aspects. The system 100 includes, as shown in the figure, a UE 101 that can be the same as or similar to one or more other UEs described herein, a 3rd Generation Partnership Project (3GPP (R)) radio access network (radio AN or RAN) or other (e.g., non-3GPP) AN, one or more RAN nodes (e.g., evolved Node B(s) (eNB(s)), next generation Node B(s) (gNB(s)), and / or other nodes) or other nodes or access points that can be included in a (R)AN 210, a data network (DN) 203 that can be, e.g., an operator service, Internet access, or a third party service, and a 5th Generation Core Network (5GC) 120.5GC 120 may include one or more of the following functions and network components, i.e., 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, which can be connected by various interfaces and / or reference points as shown in, for example, FIG. 1.

[0029] Figure 2 shows exemplary components of device 200 according to some aspects. In some aspects, device 200 may include, at least as shown in the figure, an integrated application circuit 202, a baseband circuit 204, a radio frequency (RF) circuit 206, a front-end module (FEM) circuit 208, one or more antennas 210, and a power management circuitry (PMC) 212. The components of device 200 shown in the figure may be included in a UE or a RAN node. In some aspects, device 200 may include fewer elements (e.g., a RAN node may not utilize application circuit 202 and instead may include a processor / controller that processes IP data received from a CN such as 5GC 120 or an Evolved Packet Core (EPC)). In some embodiments, device 200 may include additional elements such as, for example, a memory / storage device, a display, a camera, one or more sensors (including one or more temperature sensors such as a single temperature sensor or multiple temperature sensors at different locations within device 200), or an input / output (I / O) interface. In other aspects, the components described below may be included in two or more devices (e.g., the circuits described above may be separately included in two or more devices for a cloud-RAN (C-RAN) implementation).

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

[0031] The baseband circuit 204 may include, but is not limited to, circuits such as one or more single-core processors or multi-core processors. The baseband circuit 204 may include one or more baseband processors or control logics to process the baseband signals received from the receive signal path of the RF circuit 206 and generate baseband signals for the transmit signal path of the RF circuit 206. The baseband processing circuit 204 can interface with the application circuit 202 to generate and process baseband signals and control the operation of the RF circuit 206. For example, in some embodiments, the baseband circuit 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 (singular or plural) 204D of other existing generations, under development or to be developed in the future (e.g., second-generation (2G), sixth-generation (6G), etc.). The baseband circuit 204 (e.g., one or more of the baseband processors 204A to 204D) can handle various radio control functions that enable communication with one or more wireless networks via the RF circuit 206. In another embodiment, some or all of the functions of the baseband processors 204A to D may be included in modules stored in the memory 204G and executed via the central processing unit (CPU) 204E. The radio control functions can include, but are not limited to, signal modulation / demodulation, encoding / decoding, radio frequency shifting, etc. In some embodiments, the modulation / demodulation circuit of the baseband circuit 204 can include fast-Fourier transform (FFT), precoding, or constellation mapping / demapping functions. In some embodiments, the encoding / decoding circuit of the baseband circuit 204 can include convolution, tail-biting convolution, turbo, Viterbi, or low-density parity check (LDPC) encoder / decoder functions.Aspects of modulation / demodulation and encoder / decoder functions are not limited to these examples and may include other suitable functions in other aspects.

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

[0033] In some aspects, baseband circuit 204 can provide communication compatible with one or more wireless technologies. For example, in some aspects, baseband circuit 204 can support communication with next generation (NG)-radio access network (RAN), evolved universal terrestrial radio access network (EUTRAN) or other wireless metropolitan area network (WMAN), wireless local area network (WLAN), wireless personal area network (WPAN), etc. An aspect in which baseband circuit 204 is configured to support wireless communication of two or more wireless protocols can be referred to as a multi-mode baseband circuit.

[0034] The RF circuit 206 can enable communication with a wireless network using modulated electromagnetic radiation through a non-solid medium. In various embodiments, the RF circuit 206 may include switches, filters, amplifiers, etc. to facilitate communication with the wireless network. The RF circuit 206 may include a receive signal path that includes a circuit that down-converts the RF signal received from the FEM circuit 208 and provides the baseband signal to the baseband circuit 204. The RF circuit 206 may also include a transmit signal path that includes a circuit that up-converts the baseband signal provided by the baseband circuit 204 and provides an RF output signal for transmission to the FEM circuit 208.

[0035] In some embodiments, the receive signal path of the RF circuit 206 may include a mixer circuit 206a, an amplifier circuit 206b, and a filter circuit 206c. In some embodiments, the transmit signal path of the RF circuit 206 may include a filter circuit 206c and a mixer circuit 206a. The RF circuit 206 may also include a synthesizer circuit 206d that synthesizes the frequencies used by the mixer circuit 206a of the receive signal path and the transmit signal path. In some embodiments, the mixer circuit 206a of the receive signal path may be configured to down-convert the RF signal received from the FEM circuit 208 based on the synthesized frequency provided by the synthesizer circuit 206d. The amplifier circuit 206b may be configured to amplify the down-converted signal, and the filter circuit 206c may be a low-pass filter (LPF) or a band-pass filter (BPF) configured to remove unwanted signals from the down-converted signal and generate an output baseband signal. The output baseband signal may be provided to the baseband circuit 204 for further processing. In some embodiments, the output baseband signal may be a zero-frequency baseband signal, but this is not a requirement. In some embodiments, the mixer circuit 206a of the receive signal path may include a passive mixer, but the scope of the embodiments is not limited in this regard.

[0036] In some embodiments, the mixer circuit 206a of the transmission signal path may be configured to up-convert an input baseband signal based on the combined frequency provided by the combining circuit 206d to generate an RF output signal for the FEM circuit 208. The baseband signal may be provided by the baseband circuit 204 and may be filtered by the filter circuit 206c.

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

[0038] In some embodiments, the output baseband signal and the input baseband signal may be analog baseband signals, but the scope of the embodiments is not limited in this regard. In some alternative embodiments, the output baseband signal and the input baseband signal may be digital baseband signals. In these alternative embodiments, the RF circuit 206 may include an analog-to-digital converter (ADC) and a digital-to-analog converter (DAC) circuit, and the baseband circuit 204 may include a digital baseband interface that communicates with the RF circuit 206.

[0039] In some dual-mode embodiments, separate radio IC circuits may be provided to process the signals of each spectrum, but the scope of the embodiments is not limited in this regard.

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

[0041] The synthesizer circuit 206d can be configured to synthesize the output frequency used by the mixer circuit 206a of the RF circuit 206 based on a frequency input and a divider control input. In some embodiments, the synthesizer circuit 206d can be a fractional-N / N+1 synthesizer.

[0042] In some embodiments, the frequency input may be provided by a voltage controlled oscillator (VCO), but this is not a requirement. The divider control input can be provided by either the baseband circuit 204 or the application processor 202 depending on the desired output frequency. In some embodiments, the divider control input (e.g., N) can be determined from a look-up table based on the channel indicated by the application processor 202.

[0043] The synthesizer circuit 206d of the RF circuit 206 may include a divider, a Delay-Locked Loop (DLL), a multiplexer, and a phase accumulator. In some embodiments, the divider may be a dual modulus divider (DMD), and the phase accumulator may be a digital phase accumulator (DPA). In some embodiments, the DMD may be configured to divide an input signal (e.g., based on execution) into either N or N+1 to provide a fractional division ratio. In some exemplary embodiments, the DLL may include a set of cascaded tunable delay elements, a phase detector, a charge pump, and D-type flip-flops. In these embodiments, the delay elements can be configured to divide the VCO period into packets of equal phase of Nd, 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 embodiments, the synthesizer circuit 206d may be configured to generate a carrier frequency as the output frequency. In other embodiments, the output frequency may be a multiple of the carrier frequency (e.g., twice the carrier frequency, four times the carrier frequency), and can be used in conjunction with a quadrature generator and a divider circuit to generate multiple signals at carrier frequencies having multiple different phases relative to each other. In some embodiments, the output frequency may be the LO frequency (fLO). In some embodiments, the RF circuit 206 may include an IQ / polarity converter.

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

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

[0047] In some aspects, the PMC 212 can manage the power supplied to the baseband circuit 204. Specifically, the PMC 212 can control power selection, voltage scaling, battery charging, or DC-DC conversion. When the device 200 is powered by a battery, for example, when this device is included in a UE, the PMC 212 can often be included. The PMC 212 can increase the power conversion efficiency while imparting desirable implementation size and heat dissipation characteristics.

[0048] FIG. 2 shows PMC212 coupled only to baseband circuit 204. However, in other embodiments, PMC212 may be additionally or alternatively coupled to other components including, but not limited to, application circuit 202, RF circuit 206, or FEM 208 to perform similar power management operations.

[0049] In some embodiments, PMC212 can control or otherwise be part of various power saving mechanisms of device 200. For example, if the device 200 is in the RRC_Connected state where it is still connected to the RAN node as it is expected to receive traffic soon, after a certain inactive period, the device can enter a state known as discontinuous reception mode (DRX). During this state, device 200 can save power by powering down at short intervals.

[0050] If there is no data traffic activity for a long period, device 200 can transition to the RRC_Idle state where it disconnects from the network and does not perform operations such as channel quality feedback, handover, etc. Device 200 enters a very low power state and periodically wakes up to perform paging to listen for the network and then powers down again. Device 200 cannot receive data in this state. To receive data, it can transition back to the RRC_Connected state.

[0051] In an additional power saving mode, the device may be allowed to be unavailable from the network for a period longer than the paging interval (ranging from seconds to hours). During this time, the device may not be able to reach the network at all and may completely power down. If there is data sent during this time, there will be a significant delay, but the delay is considered acceptable.

[0052] Using the processors of the application circuit 202 and the processors of the baseband circuit 204, elements of one or more instances of the protocol stack can be executed. For example, the processors of the baseband circuit 204 can be used alone or in combination to execute layer 3, layer 2, or layer 1 functionality, while the processors of the application circuit 204 can utilize the data received from these layers (e.g., packet data) to further execute layer 4 functionality (e.g., the transmission communication protocol (TCP) layer and the user datagram protocol (UDP) layer). As described above in this specification, layer 3 can include a radio resource control (RRC) layer, which will be described in more detail below. As described above in this specification, layer 2 can include a medium access control (MAC) layer, a radio link control (RLC) layer, and a packet data convergence protocol (PDCP) layer, which will be described in more detail below. As described above in this specification, layer 1 can include the physical (PHY) layer of the UE / RAN node, which will be described in more detail below.

[0053] Figure 3 shows an exemplary interface of a baseband circuit according to some aspects. As described above, the baseband circuit 204 of FIG. 2 can include processors 204A - 204E and a memory 204G utilized by these processors. Each of the processors 204A - 204E can include a memory interface 304A - 304E for transmitting and receiving data with the memory 204G, respectively.

[0054] The baseband circuit 204 may further include one or more interfaces communicatively coupled to other circuits / devices, such as a memory interface 312 (e.g., an interface for transmitting and receiving data to and from a memory external to the baseband circuit 204), an application circuit interface 314 (e.g., an interface for transmitting and receiving data to and from the application circuit 202 of FIG. 2), an RF circuit interface 316 (e.g., an interface for transmitting and receiving data to and from the RF circuit 206 of FIG. 2), a wireless hardware connectivity interface 318 (e.g., an interface for transmitting and receiving data to and from a Near Field Communication (NFC) component, a Bluetooth® component (e.g., Bluetooth® Low Energy), a Wi-Fi® component, and other communication components), and a power management interface 320 (e.g., an interface for transmitting and receiving power or control signals to and from the PMC 212).

[0055] As described in more detail herein, for example, various aspects that may be used in a UE can facilitate power management in relation to a radio modem(s). The various aspects can use the power management techniques described herein and can reduce overheating using one or more of the power management stages described herein based on power consumption and temperature monitoring levels. The power management stages described 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] Referring to FIG. 4, shown is a block diagram of a system 400 that can be used in a UE (user equipment), a base station (BS such as a next-generation node B (gNodeB or gNB)), an evolved node B (eNodeB), or another BS (base station) / TRP (transmission / reception point), or other components of a 3GPP (3rd Generation Partnership Project) (registered trademark) network (e.g., 5GC (5th Generation Core Network)) component, or a UPF (user plane function), which facilitates enhancements to measurements for a radio resource control (RRC) connected mode UE that can facilitate a DC / CA configuration according to various aspects described herein. The system 400 may include a processor(s) 410, a communication circuit 420, and a memory 430. The processor(s) 410 (e.g., may include one or more of 202 and / or 204A - 204F, etc.) may include a processing circuit and associated interface(s) (e.g., a communication interface (e.g., RF circuit interface 316) for communicating with the communication circuit 420, a memory interface (e.g., memory interface 312, etc.) for communicating with the memory 430). The communication circuit 420 may include, for example, circuits for wired and / or wireless connection(s) (e.g., 206 and / or 208) (e.g., a transmitter circuit (associated with one or more transmission chains) and / or a receiver circuit (associated with one or more reception chains)), and the transmitter circuit and the receiver circuit may use common and / or separate circuit elements, or combinations thereof. The memory 430 may be any of various storage media (e.g., volatile and / or non-volatile by any of various technologies / configurations) (e.g., memory 204G, local memory of the processor(s) described herein (including CPU register(s))) and may include one or more memory devices and can store instructions and / or data associated with one or more processors 410 or the transceiver circuit 420.

[0057] A particular type of aspect of the system 400 (e.g., an aspect of the UE, etc.) is denoted by a subscript (e.g., the processor(s) 410UE , communication circuit 420 UE , and memory 430 UE A system 400 comprising UE ) can be shown via. Aspects of the BS (e.g., system 400 BS ) and aspects of network components (e.g., UPF (User Plane Function), etc.) (e.g., system 400 UPF ) and in some aspects such as, the processor(s) 410 BS (etc.), communication circuits (e.g., 420 BS etc.), and memory (e.g., 430 BS etc.) may be included in a single device or in different devices such as part of a distributed architecture. In an aspect, signaling or messaging between different aspects of system 400 (e.g., 4001 and 4002) is generated by processor(s) 4101, transmitted by communication circuit 4201 via an appropriate interface or reference point (e.g., 3GPP (registered trademark) radio interface, N3, N4, etc.), received by communication circuit 4202, and processed by processor(s) 4102. Depending on the type of interface, additional components (e.g., antenna(s), network port(s), etc. associated with system(s) 4001 and 4002) may be involved in this communication.

[0058] In various aspects, one or more of information (e.g., system information, resources associated with signaling, etc.), features, parameters, etc. are via signaling from a gNB or other access point (e.g., associated with one or more layers of L1 signaling or upper layer signaling (e.g., MAC, RRC, etc.)), (e.g., generated by processor(s) 410 BS transmitted by communication circuit 420 BS received by communication circuit 420 UE and processed by processor(s) 410 UEIt can be configured in the UE via signaling processed by []. Depending on the type of information, features, parameters, etc., the type of signaling used, and / or the exact details of the operations performed in the UE and / or BS during processing (e.g., signaling structure, handling of PDU(s) / SDU(s), etc.) can vary. However, for the sake of convenience, such operations may be referred to herein by terms such as configuration of information / feature(s) / parameter(s) / etc. in the UE, generation or processing of configuration signaling, or the like.

[0059] Referring to FIG. 5, a state diagram showing three radio resource control (RRC) states in which a UE can operate in relation to various aspects described herein is shown. In the IDLE state, the UE is disconnected from the core network (CN). While in IDLE, the UE performs cell reselection and can receive paging messages from the CN via the cell on which the UE is camping. To enter the CONNECTED state, the UE executes an RRC connection process 510 in which the UE uses a random access channel (RACH) process to connect to the CN and the radio access network (RAN). In the CONNECTED state, the UE is connected and registered 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 cell identification information of the primary cell), and the RRC configuration for the UE (e.g., radio bearers and security information), is also stored in both the RAN and the UE.

[0060] The UE can return from the CONNECTED state to the IDLE state by executing the RRC release process 520. When the UE returns to the IDLE state, the UE context is deleted from the UE and the RAN. The UE can also enter the default IDLE state from either the CONNECTED state or the INACTIVE state if it cannot find a cell for camping as indicated by 530, 560.

[0061] The INACTIVE state is introduced in 5G to provide an intermediate state between the IDLE state and the CONNECTED state that will facilitate the reconnection process by eliminating some of the signaling used to transition from the IDLE state to the CONNECTED state. The INACTIVE state is beneficial for UEs that do not communicate frequently with the RAN and allows for power savings compared to these UEs remaining in the CONNECTED state. To enter the INACTIVE state, the UE executes the RRC release process using the suspension configuration 540 where the UE context is stored by both the UE and the serving gNB. In the INACTIVE state, the UE still has a non-access stratum (NAS) connection to the CN (i.e., it is still in the connection management (CM)-CONNECTED state as opposed to the IDLE state where the UE is not CM-CONNECTED).

[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 thus cannot perform any dedicated data transmission or reception. Since the UE cannot perform dedicated data reception while in the INACTIVE state, when downlink data is sent to the UE, the RAN pages the UE to trigger it to enter the CONNECTED state. If the UE has uplink data to send, the UE first enters the CONNECTED state before sending the uplink data.

[0063] To transition from the INACTIVE state to the CONNECTED 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. This facilitates the transition to the CONNECTED state compared to the transition from the IDLE state to the CONNECTED state by enabling the resumption of the previous connection without the need to perform extensive signaling.

[0064] Referring to FIG. 6, a diagram is shown that depicts a measurement model for a radio resource control (RRC) connection mode UE based on K beams from a gNB (or other BS) in relation to the various aspects described herein.

[0065] Referring to FIG. 7, a table is shown that depicts a measurement configuration for measurement reports, along with related explanations, in relation to the various aspects described herein.

[0066] Referring to FIG. 8, a UE400 that configures and transmits measurement reports UE and an NW400 BSA flowchart showing an exemplary method 800 that can be used by is shown. At 810, method 800 may include the NW sending one or more of an RRCReconfiguration message or an RRCResume message that may include a measurement configuration (e.g., via a measConfig information element (IE)) to the UE via a BS such as a gNB. At 820, the RRCReconfiguration / RRCResume procedure can be completed and the UE can perform measurements based on the measurement configuration. At 830, the UE can send a measurement report indicating the results of the performed measurements to the NW.

[0067] However, existing measurement techniques are targeted at mobility and are not optimized for the configuration of dual connectivity (DC) and / or carrier aggregation (CA).

[0068] The NW can configure RRC_CONNECTED UEs to perform measurements according to a measurement configuration indicated via a MeasConfig information element (IE) and report them. The measurement configuration can be provided by dedicated signaling (e.g., RRCReconfiguration or RRCResume).

[0069] A CONNECTED UE can generate and send a measurement report (MR) with one or more of the following characteristics: (1) the MR may include measurement identification information of the relevant measurement configuration that triggered the report; (2) the cell and beam measurement quantities included in the measurement report are configured by the network; (3) the number of non-serving cells reported can be restricted through network configuration; (4) cells belonging to a blacklist (if 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; (5) the beam measurement values included in the measurement report are configured by the network (e.g., only beam identifiers, measurement results and beam identifiers, or without beam reports).

[0070] Whether the 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 can perform such measurements without a measurement gap. In a gap-assisted scenario, the UE cannot assume that it can perform such measurements without a measurement gap.

[0071] In the case of a triggered event or periodic measurement report, the UE can include reportAddNeighMeas in the measurement report. In the case of reportAddNeighMeas, the UE includes the measurement results of the best neighboring cell on the serving frequency.

[0072] Existing measurements do not provide measurements of neighboring cells on non-serving frequencies, as they are targeted at mobility instead of dual connectivity (DC) and / or carrier aggregation (CA) configurations.

[0073] Referring to FIG. 9, a MeasConfig IE is shown that specifies the measurements performed by the UE in relation to the various aspects described herein. Referring to FIG. 10, MeasResults IE and MeasResultNR IE are shown that cover the results measured for intra-frequency, inter-frequency, and inter-RAT mobility in relation to the various aspects described herein.

[0074] Existing measurement techniques are not adapted to DC / CA configurations. In some NW policies, the NW DC / CA configuration depends on the measurement configuration.

[0075] Typically, for a CONNECTED UE, the NW will perform primary cell (PCell) changes, secondary cell (SCell) additions, and secondary cell group (SCG) additions based on UE measurement reports on non-serving cells. In other words, if the NW does not configure adjacent cell measurements, the NW will not perform such RRCReconfiguration.

[0076] Currently, in some NW vendor's LTE networks, the NW only configures inter-RAT (radio access technology) NR measurement configurations when the UE first accesses the NW. If the UE does not report NR measurement reports for some time, the NW will delete the measurement configuration. The main motivation for the NW to delete the measurement configuration is that NR measurements may involve measurement gaps that could lead to interruptions in ongoing transmissions.

[0077] Therefore, the first problem with existing techniques is that the lack of measurement configuration blocks the NW from enabling DC / CA configuration whether the DC / CA configuration is more suitable for the latest UE situation, such as when (1) the UE triggers a new service, (2) the UE enters LTE+NR overlapping coverage, and / or (3) the data volume for transmission becomes larger.

[0078] In addition, existing MR reports can piggyback MR on the serving frequency but cannot carry potential frequencies for CA / DC.

[0079] In existing systems, a CONNECTED UE is only allowed to report the best adjacent cells on the serving frequency along with measurement reports to the NW, and the motivation for introducing these measurement results is for mobility handover purposes. 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 one cell as the target PCell.

[0080] Therefore, the second problem in the existing system is that for measurement reports triggered by an A3 event (where the neighbor has a better offset than the PCell / PSCell) and / or an A5 event (where the PCell / PSCell becomes worse than an absolute threshold 1 and the neighbor / SCell becomes better than another absolute threshold 2), the measurement results can only reflect the best neighboring cell on the current serving frequency and cannot reflect the best cells on potential CA / DC secondary component carriers. As a result, the NW can determine the target PCell based on this, but cannot determine the SCG / SCell for the CA / DC configuration based on this measurement report.

[0081] Referring to FIG. 11, a flowchart of a first exemplary method 1100 is shown that facilitates an extension to a measurement report for a connected mode UE that can facilitate a DC / CA configuration in relation to the various aspects described herein. Method 1100 provides a first exemplary technique that can solve the first problem and blocks the NW within the existing system from enabling a DC / CA configuration even when it is more suitable for the UE due to the lack of a measurement configuration.

[0082] In contrast to the existing system, the various embodiments described herein can facilitate measurements for potential frequencies for a DC / CA configuration (s) using the exemplary method 1100 and / or related techniques. In relation to method 1100, an RRC connection can be established (or already in place) for the UE as shown at 1110.

[0083] Method 1100 can be used in scenarios where a CONNECTED UE preferably has a CA / DC configuration but does not have a measurement configuration associated with neighboring cells.

[0084] At 1120, (for example, 400 UEThe UE (including...) can generate a UE assistance information message including a measurement requirement and send it to the NW's BS (e.g., 400 BS including...). Depending on the embodiment, the requirement can include or indicate one or more of the following types of information, namely, (1) a 1-bit indication of the measurement requirement, (2) an indication of the radio access technology (RAT) for the measurement (e.g., EUTRA, NR, etc.), (3) one or more frequencies / bands for the measurement, and / or (4) one or more frequencies / bands for measurements without measurement gaps.

[0085] At 1130, in response to the measurement requirement, the BS can generate and send an RRCReconfiguration message including MeasConfig that constitutes the requested measurement value(s).

[0086] The UE can perform the configured measurement, and at 1140, the UE can generate a measurement report indicating the configured measurement on the potential CA / DC frequency / band and send it to the BS.

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

[0088] Referring to FIG. 12, a flowchart of a second exemplary method 1200 is shown that facilitates an extension to the measurement report for a connected-mode UE that can facilitate a DC / CA configuration in relation to the various aspects described herein. The method 1200 provides a second exemplary technique that can solve the first problem and blocks the NW in an existing system from enabling a DC / CA configuration even when it is more suitable for the UE due to the lack of measurement configuration.

[0089] In connection with method 1200, an RRC connection can be established (or already in place) for the UE (e.g., using 400 UE as shown at 1210).

[0090] At 1220, the BS (e.g., using 400 BS as shown) can generate and transmit an RRCReconfiguration message containing a MeasConfig that constitutes one or more measurements including measurements (singular or plural) on potential CA / DC frequencies (e.g., F1 and F2 in FIG. 12 etc.), the measurement configuration(s) can be for CA / DC purposes and can indicate CA / DC purposes. The purpose can be indicated by one of measurement reporting or measurement object configuration. In embodiments where a DC / CA purpose configuration is indicated in the reporting configuration, it may be indicated by a ReportConfigNR IE and a new event Ax for CA / DC purposes can be introduced. Referring to FIG. 13, examples of updated ReportConfigNR and EventTriggerConfig IEs (part of the latter is omitted) for indicating CA / DC purposes are shown in connection with various aspects described herein. Referring to FIG. 14, an example of an updated MeasObjectNR IE for indicating CA / DC purposes is shown in connection with various aspects described herein. Referring to FIG. 15, an example of an updated MeasObjectEUTRA IE for indicating CA / DC purposes is shown in connection with various aspects described herein.

[0091] Referring back to FIG. 12, at 1230 the UE can perform the configured measurements including on potential frequencies for CA / DC.

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

[0093] At 1250, the BS can generate an RRC Reconfiguration message including an NR Secondary Cell Group (SCG) configuration that is configured at 1220 and includes at least one of the potential CA / DC frequencies / bands indicated in the measurement report at 1240, and transmit it to the UE.

[0094] Referring to FIG. 16, a flowchart of a third exemplary method 1600 is shown that facilitates an extension to the measurement report for a connected mode UE that can facilitate a DC / CA configuration in relation to the various aspects described herein. Method 1600 provides a first exemplary technique that can solve a second problem, where for a measurement report triggered by an A3 / A5 event(s), the measurement result can reflect only the best neighbor cell on the current serving frequency and not the best cell on a potential CA / DC secondary component carrier. Thus, in an existing system, the NW can determine a target PCell based thereon, but cannot determine an SCG / SCell for a CA / DC configuration based on this measurement report, and the existing system only provides reporting of the best non-serving cell on the serving frequency for a neighbor cell.

[0095] In relation to method 1600, an RRC connection can be established (or already in place) for the UE as shown at 1610 (e.g., using 400 UE ).

[0096] At 1620, (e.g., 400 BSThe BS (such as by using) can generate and transmit an RRCReconfiguration message that includes a MeasConfig that constitutes one or more measurements (singular or plural) on a first set of frequencies (e.g., F2 in FIG. 16) associated with the triggered measurement report and on one or more candidate CA / DC frequencies (such as F3, F4, and F5 in FIG. 16). In various embodiments, the first set of frequencies and the one or more candidate CA / DC frequencies can belong to a combination of bands supported by the UE. In some scenarios, the first set of frequencies can correspond to adjacent frequencies, and in other scenarios, it can include the serving frequency.

[0097] The measurement configuration can indicate one or more frequencies (such as candidate CA / DC frequencies) that are carried as additional measurement reports. In some embodiments, the NW can configure (e.g., via the BS) a frequency (such as a candidate CA / DC frequency) to be carried as an additional measurement report in a measurement object for, e.g., a first set of frequencies (such as F2). In some embodiments, the NW can configure a measurement object (singular or plural) for measurements on candidate CA / DC frequencies (such as F3, F4, or F5) in the same way as existing measurement objects.

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

[0099] At 1640, the UE can generate a measurement report indicating measurements on a first set of frequencies and on one or more of the potential CA / DC frequencies / bands, and transmit it to the BS. In various embodiments, the NW can configure (e.g., at 1620) the criteria by which the UE determines which frequency(ies) from the potential / candidate CA / DC set can be provided as additional report(s). For example, the NW can configure a radio link quality threshold (e.g., reference signal (RS) received power (RSRP) / RS received quality (RSRQ) / signal-to-interference-plus-noise ratio (SINR), etc.), and if the quality of one set of frequencies (e.g., F3) exceeds the threshold while the quality of another set of frequencies (e.g., F4) is below the threshold, the UE can include in the additional report the set of frequencies (e.g., F3) having a quality higher than the threshold and the associated results, while omitting those below the threshold (e.g., F4).

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

[0101] Referring to FIG. 17, a flow diagram of a fourth exemplary method 1600 is shown that facilitates an extension to measurement reports for connection mode UEs that can facilitate a DC / CA configuration, in relation to the various aspects described herein. Method 1700 provides a second exemplary technique that can solve a second problem, where for measurement reports triggered by A3 / A5 event(s), the measurement results can reflect only the best neighboring cells on the current serving frequency and not the best cells on potential CA / DC secondary component carriers. Thus, in an existing system, the NW can determine a target PCell based thereon, but cannot determine an SCG / SCell for a CA / DC configuration based on this measurement report. The existing system only provides reporting of the best non-serving cells on the serving frequency for neighboring cells. Method 1700 may be similar to method 1600, but the detailed dedicated configuration provided at 1620 can be omitted. Instead, the NW can provide...

[0102] In relation to method 1700, an RRC connection can be established (or already in place) for the UE (e.g., using 400 UE etc.) as shown at 1710.

[0103] At 1720, the BS (e.g., using 400 BS etc.) can generate and transmit an RRCReconfiguration message including MeasConfig that configures measurements on a first set of frequencies (e.g., F2 in FIG. 17) associated with the triggered measurement report and enables additional reporting of one or more candidate CA / DC frequencies (e.g., F3 and F4 in FIG. 17, etc.). In various embodiments, the NW can provide (e.g., via the BS) thresholds (e.g., for radio link quality) to the UE to determine which potential / candidate CA / DC frequencies can be included as additional report(s).

[0104] In 1730, the UE can perform configured measurements including on one or more candidate frequencies for CA / DC. In some embodiments, the candidate frequencies for CA / DC can be determined by the UE based on system information block(s) (e.g., SIB4 and SIB5, etc.) generated by the BS. In some embodiments, the candidate frequencies for CA / DC can be determined according to any UE knowledge that can vary based on the UE implementation form.

[0105] In 1740, the UE can generate a measurement report indicating configured measurements on a first set of frequencies (e.g., F2) and on one or more of the potential CA / DC frequencies / bands, and transmit it to the BS. In various embodiments, the NW can configure (e.g., in 1620) the criteria by which the UE determines which frequency(ies) from the potential / candidate CA / DC set can be provided as additional report(s). For example, the NW can configure a radio link quality threshold (e.g., reference signal (RS) received power (RSRP) / RS received quality (RSRQ) / signal-to-interference-plus-noise ratio (SINR), etc.), and the UE can include any set(s) of frequencies (e.g., F3 and F4, etc.) having a quality higher than the threshold, along with the related results, in the additional report, while omitting those below the threshold.

[0106] In 1750, the BS can generate an RRCReconfiguration message including an NR SCG configuration and / or an SCell configuration including at least one of the potential CA / DC frequencies / bands indicated in the measurement report of 1740, and transmit it to the UE.

[0107] Referring to FIG. 18, a flowchart of an exemplary method or process 1800 available in a UE that facilitates one or more extensions to the measurements in the connected mode according to various aspects described herein is shown. In other aspects, when executed, (e.g., system 400 UEInstructions associated with method 1800 that may cause a UE to perform the operations of method 1800 can be stored on a machine-readable medium. Method 1800 is provided as one specific exemplary aspect of the techniques described herein, but it should be understood that other specific exemplary aspects may use additional and / or alternative techniques.

[0108] At 1810, optionally, the UE can transmit 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, a RAT for the measurement, one or more potential sets of CA / DC frequencies for the measurement, and / or one or more potential sets of CA / DC frequencies for measurement without gaps.

[0109] At 1820, the UE can receive a first RRCReconfiguration message including a measurement configuration that configures one or more sets of frequencies for the measurement. The one or more sets of frequencies can include at least one serving frequency or an adjacent cell on the serving frequency. The one or more sets of frequencies can include at least one CA / DC candidate. In various embodiments, the first RRCReconfiguration message can indicate that the measurement configuration is for CA / DC purposes.

[0110] At 1830, the UE can perform measurements on one or more sets of frequencies configured via the first RRCReconfiguration message, which may include at least one CA / DC candidate in some embodiments. In some embodiments, the one or more sets of configured frequencies do not include CA / DC candidates, but the UE can also perform measurements on at least one CA / DC candidate determined via SIB(s) or other information in the UE. The measurements can be performed so as not to interrupt an ongoing transmission (e.g., without a measurement gap, during discontinuous reception (DRX) inactive time, etc.).

[0111] In 1840, the UE can send a measurement report message indicating at least some of the set of frequencies measured at 1830 and the associated measurements on the reported set(s) of frequencies. In some embodiments, the measurement report may include the serving frequency, or an adjacent cell on the serving frequency, and at least one CA / DC candidate. In some embodiments, the UE can report measurements on CA / DC candidates having at least a threshold radio link quality (e.g., the threshold can be configured in the first RRC Reconfiguration message at 1820, etc.). In some embodiments, the UE can report all measured CA / DC candidates.

[0112] In 1850, the UE can receive a second RRC Reconfiguration message that configures the UE using at least one of the CA / DC candidates, for example, for SCell configuration, SCG configuration, or some other CA / DC configuration.

[0113] Additionally or alternatively, method 1800 can include one or more other operations described herein in connection with various aspects of the UE and / or system 400 UE as described herein.

[0114] Referring to FIG. 19, a flow diagram of an exemplary method or process 1900 available at the BS that facilitates one or more extensions to the measurements by the UE in the connected mode, according to various aspects described herein, is shown. In other aspects, instructions associated with method 1900 can be stored on a machine-readable medium that, when executed, can cause the BS (e.g., using system 400 BS to perform the operations of method 1900). Method 1900 is provided as one particular exemplary aspect of the techniques described herein, but it should be understood that other particular exemplary aspects can use additional and / or alternative techniques.

[0115] In 1910, optionally, the BS can receive a UE assistance information message including a measurement request. In some embodiments, the measurement request can include one or more of a single bit indicating the measurement request, a RAT for the measurement, one or more potential sets of CA / DC frequencies for the measurement, and / or one or more potential sets of CA / DC frequencies for measurement without gaps.

[0116] In 1920, the BS can send a first RRCReconfiguration message including a measurement configuration that constitutes one or more sets of frequencies for the measurement. The one or more sets of frequencies can include at least one serving frequency or an adjacent cell on the serving frequency. The one or more sets of frequencies can include at least one CA / DC candidate. In various embodiments, the first RRCReconfiguration message can indicate that the measurement configuration is for CA / DC purposes.

[0117] In 1930, the BS can receive a measurement report message indicating at least some sets of frequencies measured by the UE based on the first RRCReconfiguration message, along with the relevant measurements for the reported set(s) of frequencies. In some embodiments, the measurement report can include the serving frequency, or an adjacent cell on the serving frequency, and at least one CA / DC candidate. In some embodiments, the UE can report measurements for CA / DC candidates having at least a threshold radio link quality (e.g., the threshold can be configured within the first RRCReconfiguration message in 1920, etc.). In some embodiments, the UE can report all measured CA / DC candidates.

[0118] In 1940, the BS can transmit a second RRCReconfiguration message that configures the UE using at least one of the CA / DC candidates, for example, for SCell configuration, SCG configuration, or some other CA / DC configuration.

[0119] Additionally or alternatively, method 1900 may include one or more other operations described herein in connection with various aspects of the BS and / or system 400 BS and may include one or more other operations described herein in connection with various aspects of the BS and / or system 400. Additional Examples

[0120] Examples herein may include a method, means for performing operations or blocks of the method, (e.g., a processor with memory such as a processor, an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), etc.), and when executed by a machine, executable instructions that cause the machine to perform the operations of the method or apparatus or system for simultaneous communication using multiplex communication techniques according to the aspects and examples described herein, including at least one machine-readable medium.

[0121] Example 1 is a UE assistance information message for transmission, optionally generating a UE assistance information message, where 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 for each of one or more sets of frequencies, where the one or more sets of frequencies include a set of non-serving frequencies associated with an adjacent cell, based at least on the measConfig IE, generating a MeasurementReport message for transmission, where the MeasurementReport message indicates one or more measurements on at least one of the one or more sets of frequencies, and the one or more sets of frequencies include a set of serving frequencies for one of a serving cell or an adjacent cell and a set of non-serving frequencies associated with the adjacent cell, and receiving a second RRCReconfiguration message configuring the UE using at least one of the one or more sets of frequencies, and is a baseband processor configured to perform operations including these.

[0122] Example 2 includes the subject matter of any optional variations of Example 1, and the first RRCReconfiguration message is received in response to the UE assistance information message.

[0123] Example 3 includes the subject matter of any optional variations of Examples 1-2, and the measurement request includes one or more of a single bit indicating the measurement request, an indication of a radio access technology (RAT) for the measurement, one or more sets of frequencies, or a first set of frequencies of the one or more sets of frequencies for the measurement without a measurement gap.

[0124] Example 4 includes the subject matter of any of the optional variations of Examples 1 to 3, the measConfig IE configures the UE to measure a set of non-serving frequencies associated with adjacent cells, and the first RRCReconfiguration message indicates one or more objectives of carrier aggregation (CA) or dual connectivity (DC), where the objectives are indicated via one or more of a measurement reporting configuration or a measurement target configuration.

[0125] Example 5 includes the subject matter of any of the optional variations of Examples 1 to 4, and the operation further includes starting to perform one or more measurements for each of one or more sets of frequencies, by one of 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), at least based on the measConfig IE.

[0126] Example 6 includes the subject matter of any of the optional variations of Examples 1 to 5, and the operation includes performing one or more measurements for each of one or more sets of frequencies, by one of without a measurement gap or during discontinuous reception (DRX) inactive time.

[0127] Example 7 includes the subject matter of any of the optional variations of Examples 1 to 6, and the measConfig IE indicates a set of non-serving frequencies associated with adjacent cells via a measurement target associated with a set of serving frequencies.

[0128] Example 8 includes the subject matter of any of the optional variations of Examples 1 to 7, and at least one of the one or more sets of frequencies includes a set of non-serving frequencies when one or more measurements of the set of non-serving frequencies exceed one or more configured thresholds of the measurements.

[0129] Example 9 includes the subject matter of any of the optional variations of Examples 1-8, and the operation further includes determining a set of non-serving frequencies from a system information block (SIB) associated with adjacent cell measurements.

[0130] Example 10, when executed, causes a user equipment (UE) to optionally transmit a UE assistance information message including a measurement request, receive a first RRCReconfiguration message including a measConfig information element (IE), execute one or more measurements for each of one or more sets of frequencies based at least on the measConfig IE, where one or more sets of frequencies include a set of non-serving frequencies associated with adjacent cells, transmit a MeasurementReport message indicating one or more measurements on at least one of the one or more sets of frequencies, where one or more sets of frequencies include a set of serving frequencies for one of a serving cell or an adjacent cell and a set of non-serving frequencies associated with adjacent cells, and receive a second RRCReconfiguration message that configures the UE using at least one of the one or more sets of frequencies.

[0131] Example 11 includes the subject matter of any of the optional variations of Example 10, and the first RRCReconfiguration message is received in response to a UE assistance information message.

[0132] Example 12 includes the subject matter of any of the optional variations of Examples 10-11, and the measurement request includes one or more of a single bit indicating the measurement request, an indication of a radio access technology (RAT) for the measurement, one or more sets of frequencies, or a first set of frequencies of one or more sets of frequencies for the measurement without a measurement gap.

[0133] Example 13 includes the subject matter of any of the optional variations of Examples 10 to 12, the measConfig IE configures the UE to measure a set of non-serving frequencies associated with an adjacent cell, and the first RRCReconfiguration message indicates one or more objectives of carrier aggregation (CA) or dual connectivity (DC), and the objective is indicated via one or more of a measurement reporting configuration or a measurement target configuration.

[0134] Example 14 includes the subject matter of any of the optional variations of Examples 10 to 13, and when the instruction is executed, the UE further, at least based 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), starts to perform one or more measurements for each of one or more sets of frequencies by one of them.

[0135] Example 15 includes the subject matter of any of the optional variations of Examples 10 to 14, and when the instruction is executed, the UE performs one or more measurements for each of one or more sets of frequencies by one of without a measurement gap or during discontinuous reception (DRX) inactive time.

[0136] Example 16 includes the subject matter of any of the optional variations of Examples 10 to 15, and the measConfig IE indicates a set of non-serving frequencies associated with an adjacent cell via a measurement target associated with a set of serving frequencies.

[0137] Example 17 includes the subject matter of any of the optional variations of Examples 10 to 16, and at least one set of one or more sets of frequencies includes a set of non-serving frequencies when one or more measurements of the set of non-serving frequencies exceed one or more configured thresholds of the measurements.

[0138] Example 18 includes the subject matter of any of the optional variations of Examples 10 to 17, and when the instruction is executed, the UE is further caused to determine a set of non-serving frequencies from a system information block (SIB) associated with adjacent cell measurements.

[0139] Example 19 is a UE device comprising a processor configured to perform operations including optionally transmitting a user equipment (UE) assistance information message including a measurement request, receiving a first RRCReconfiguration message including a measConfig information element (IE), performing one or more measurements for each of one or more frequencies based at least on the RRC measConfig IE, the one or more frequencies including at least one non-serving frequency associated with an adjacent cell, transmitting 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 using at least one of the one or more frequencies.

[0140] Example 20 includes the subject matter of any of the optional variations of Example 19, and the first RRCReconfiguration message is received in response to the UE assistance information message.

[0141] Example 21 includes the subject matter of any of the optional variations of Examples 19 to 20, and the measurement request includes one or more of a single bit indicating the measurement request, an indication of a radio access technology (RAT) for the measurement, one or more sets of frequencies, or a first set of frequencies of one or more sets of frequencies for the measurement without a measurement gap.

[0142] Example 22 includes the subject matter of any of the optional variations of Examples 19 to 21, and configures the UE such that the measConfig IE measures a set of non-serving frequencies associated with adjacent cells, and the first RRCReconfiguration message indicates one or more objectives of carrier aggregation (CA) or dual connectivity (DC), and the objective is indicated via one or more of a measurement reporting configuration or a measurement target configuration.

[0143] Example 23 includes the subject matter of any of the optional variations of Examples 19 to 22, and the operation further includes starting execution of one or more measurements for each of one or more sets of frequencies by one of: 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), at least based on the measConfig IE.

[0144] Example 24 includes the subject matter of any of the optional variations of Examples 19 to 23, and the operation includes performing one or more measurements for each of one or more sets of frequencies by one of: without a measurement gap, or during discontinuous reception (DRX) inactive time.

[0145] Example 25 includes the subject matter of any of the optional variations of Examples 19 to 24, and the measConfig IE indicates a set of non-serving frequencies associated with adjacent cells via a measurement target associated with a set of serving frequencies.

[0146] Example 26 includes the subject matter of any of the optional variations of Examples 19 to 25, and at least one set of one or more sets of frequencies includes a set of non-serving frequencies when one or more measurements of the set of non-serving frequencies exceed one or more configured thresholds of the measurements.

[0147] Example 27 includes the subject matter of any of the optional variations of Examples 19 to 26, and the operation further includes determining a set of non-serving frequencies from system information blocks (SIBs) associated with adjacent cell measurements.

[0148] Example 28 includes receiving a first RRCReconfiguration message including a measConfig information element (IE), performing one or more measurements for each of one or more sets of frequencies, where the one or more sets of frequencies include a set of non-serving frequencies associated with adjacent cells, based at least on the measConfig IE, generating a MeasurementReport message for transmission, where the MeasurementReport message indicates one or more measurements on at least one of the one or more sets of frequencies, and the one or more sets of frequencies include a set of serving frequencies for one of a serving cell or an adjacent cell and a set of non-serving frequencies associated with the adjacent cell, and receiving a second RRCReconfiguration message for configuring the UE using at least one of the one or more sets of frequencies.

[0149] Example 29 includes the subject matter of any of the optional variations of Example 28, and the operation further includes generating a UE assistance information message for transmission, where the UE assistance information message includes a measurement request and the first RRCReconfiguration message is received in response to the UE assistance information message.

[0150] Example 30 includes the subject matter of any of the optional variations of Examples 28 to 29, and the measurement requirements include one or more of a single bit indicating the measurement requirement, an indication of a radio access technology (RAT) for the measurement, one or more sets of frequencies, or a first set of frequencies for the measurement without a measurement gap.

[0151] Example 31 includes the subject matter of any of the optional variations of Examples 28 to 30, and the measConfig IE configures the UE to measure a set of non-serving frequencies associated with an adjacent cell, and the first RRCReconfiguration message indicates one or more objectives of carrier aggregation (CA) or dual connectivity (DC), and the objectives are indicated via one or more of a measurement report configuration or a measurement target configuration.

[0152] Example 32 includes the subject matter of any of the optional variations of Examples 28 to 31, and the operation further includes starting the execution of one or more measurements for each of one or more sets of frequencies by one of immediately after receiving the first RRCReconfiguration message, at least based on the measConfig IE, or in response to a determination by the UE of a configuration for one or more of carrier aggregation (CA) or dual connectivity (DC).

[0153] Example 33 includes the subject matter of any of the optional variations of Examples 28 to 32, and the operation includes performing one or more measurements for each of one or more sets of frequencies by one of without a measurement gap or during discontinuous reception (DRX) inactive time.

[0154] Example 34 includes the subject matter of any of the optional variations of Examples 28 to 33, and the measConfig IE indicates a set of non-serving frequencies associated with an adjacent cell via a measurement target associated with a set of serving frequencies.

[0155] Example 35 includes the subject matter of any of the variations of Examples 28 to 34, and includes a set of non-serving frequencies when at least one of one or more sets of frequencies exceeds a configured threshold of one or more measurements of a set of non-serving frequencies.

[0156] Example 36 includes the subject matter of any of the variations of Examples 28 to 35, and further includes determining a set of non-serving frequencies from a system information block (SIB) associated with adjacent cell measurements.

[0157] Example 37 includes an apparatus comprising means for performing any of the operations described in Examples 1 to 36.

[0158] Example 38 includes a machine-readable medium storing instructions executed by a processor to perform any of the operations described in Examples 1 to 36.

[0159] Example 39 includes an apparatus comprising a memory interface and a processing circuit configured to perform any of the operations described in Examples 1 to 36.

[0160] Example 40 includes a user equipment (UE) configured to perform any of the operations described in Examples 1 to 36.

[0161] Example 41 is configured to execute operations including receiving a UE assistance information message including measurement requirements, generating a first RRCReconfiguration message for transmission, where the first RRCReconfiguration message includes a measConfig information element (IE), receiving from the UE a MeasurementReport message indicating one or more measurements on one or more sets of frequencies, where the one or more sets of frequencies include a set of serving frequencies for one of a serving cell or an adjacent cell and a set of non-serving frequencies for a user equipment (UE), and the set of non-serving frequencies is associated with an adjacent cell, and generating a second RRCReconfiguration message for transmission, where the second RRCReconfiguration message configures the UE using at least one of the one or more sets of frequencies.

[0162] Example 42 includes the subject matter of any variation of Example 41, and the first RRCReconfiguration message is generated in response to the UE assistance information message.

[0163] Example 43 includes the subject matter of any variation of any of Examples 41 to 42, and the measurement requirements include one or more of a single bit indicating the measurement requirements, an indication of a radio access technology (RAT) for the measurement, one or more sets of frequencies, or a first set of frequencies of the one or more sets of frequencies for the measurement without a measurement gap.

[0164] Example 44 includes the subject matter of any of the variations of Examples 41 to 43, the measConfig IE configures the UE to measure a set of non-serving frequencies associated with adjacent cells, and the first RRCReconfiguration message indicates one or more objectives of carrier aggregation (CA) or dual connectivity (DC), and the objectives are indicated via one or more of a measurement reporting configuration or a measurement object configuration.

[0165] Example 45 includes the subject matter of any of the variations of Examples 41 to 44, and the measConfig IE indicates a set of non-serving frequencies associated with adjacent cells via a measurement object associated with a set of serving frequencies.

[0166] Example 46 includes the subject matter of any of the variations of Examples 41 to 45, and one or more sets of frequencies include a set of non-serving frequencies when one or more measurements of the set of non-serving frequencies exceed one or more configured thresholds of the measurements.

[0167] Example 47 includes the subject matter of any of the variations of Examples 41 to 46, and the operation further includes generating a system information block (SIB) associated with adjacent cell measurements indicating a set of non-serving frequencies.

[0168] When executed, Example 48 causes a base station (BS) to receive a UE assistance information message including a measurement request, transmit a first RRCReconfiguration message including a measConfig information element (IE), receive a MeasurementReport message from a user equipment (UE) indicating one or more measurements on one or more sets of frequencies, where one or more sets of frequencies include a set of serving frequencies for one of a serving cell or an adjacent cell and a set of non-serving frequencies for the UE, the set of non-serving frequencies being associated with an adjacent cell, and transmit a second RRCReconfiguration message configuring the UE using at least one of the one or more sets of frequencies.

[0169] Example 49 includes the subject matter of any variation of Example 48, and the first RRCReconfiguration message is generated in response to the UE assistance information message.

[0170] Example 50 includes the subject matter of any variation of any of Examples 48 - 49, and the measurement request includes one or more of a single bit indicating the measurement request, an indication of a radio access technology (RAT) for the measurement, one or more sets of frequencies, or a first set of frequencies of one or more sets of frequencies for the measurement without a measurement gap.

[0171] Example 51 includes the subject matter of any variation of any of Examples 48 - 50, the measConfig IE configures the UE to measure a set of non-serving frequencies associated with an adjacent cell, and the first RRCReconfiguration message indicates one or more purposes of carrier aggregation (CA) or dual connectivity (DC), the purpose being indicated via one or more of a measurement report configuration or a measurement target configuration.

[0172] Example 52 includes the subject matter of any variation of Examples 48 to 51, and the measConfig IE indicates a set of non-serving frequencies associated with an adjacent cell via a measurement object associated with a set of serving frequencies.

[0173] Example 53 includes the subject matter of any variation of Examples 48 to 52, and one or more sets of frequencies include a set of non-serving frequencies when one or more measurements of the set of non-serving frequencies exceed a configured threshold of one or more measurements.

[0174] Example 54 includes the subject matter of any variation of Examples 48 to 53, and when the instruction is executed, it further causes the UE to generate a system information block (SIB) associated with adjacent cell measurements indicating a set of non-serving frequencies.

[0175] Example 55 includes receiving a UE assistance information message including a measurement request, transmitting a first RRCReconfiguration message including a measConfig information element (IE), receiving from the UE a MeasurementReport message indicating one or more measurements on one or more sets of frequencies, where the one or more sets of frequencies include a set of serving frequencies for one of a serving cell or an adjacent cell and a set of non-serving frequencies for a user equipment (UE), and the set of non-serving frequencies is associated with an adjacent cell, and transmitting a second RRCReconfiguration message configuring the UE using at least one of the one or more sets of frequencies, and includes a base station (BS) device comprising a processor configured to perform operations including these.

[0176] Example 56 includes the subject matter of any variation of Example 55, and the first RRCReconfiguration message is generated in response to the UE assistance information message.

[0177] Example 57 includes the subject matter of any variation of any of Examples 55 to 56, and the measurement requirement includes one or more of a single bit indicating the measurement requirement, an indication of a radio access technology (RAT) for the measurement, one or more sets of frequencies, or a first set of frequencies of one or more sets of frequencies for measurements without a measurement gap.

[0178] Example 58 includes the subject matter of any variation of any of Examples 55 to 57, the measConfig IE configures the UE to measure a set of non-serving frequencies associated with an adjacent cell, and the first RRCReconfiguration message indicates one or more objectives of carrier aggregation (CA) or dual connectivity (DC), and the objective is indicated via one or more of a measurement report configuration or a measurement target configuration.

[0179] Example 59 includes the subject matter of any variation of any of Examples 55 to 58, and the measConfig IE indicates a set of non-serving frequencies associated with an adjacent cell via a measurement target associated with a set of serving frequencies.

[0180] Example 60 includes the subject matter of any variation of any of Examples 55 to 59, and one or more sets of frequencies include a set of non-serving frequencies when one or more measurements of the set of non-serving frequencies exceed a configured threshold of one or more measurements.

[0181] Example 61 includes the subject matter of any variation of any of Examples 55 to 60, and the operation further includes generating a system information block (SIB) associated with an adjacent cell measurement indicating a set of non-serving frequencies.

[0182] Example 62 is a base station (BS) device comprising a processor configured to perform operations including transmitting a first RRCReconfiguration message comprising a measConfig information element (IE), receiving from a user equipment (UE) a MeasurementReport message indicating one or more measurements on one or more sets of frequencies, wherein the one or more sets of frequencies include a set of serving frequencies for one of a serving cell or an adjacent cell and a set of non-serving frequencies for the UE, and the set of non-serving frequencies is associated with an adjacent cell, and transmitting a second RRCReconfiguration message configuring the UE using at least one of the one or more sets of frequencies.

[0183] Example 63 includes the subject matter of any variation of Example 62, and the operations further include receiving a UE assistance information message including a measurement request, wherein the first RRCReconfiguration message is generated in response to the UE assistance information message.

[0184] Example 64 includes the subject matter of any variation of any of Examples 62 to 63, and the measurement request includes one or more of a single bit indicating the measurement request, an indication of a radio access technology (RAT) for the measurement, one or more sets of frequencies, or a first set of frequencies of one or more sets of frequencies for the measurement without a measurement gap.

[0185] Example 65 includes the subject matter of any variation of any of Examples 62 to 64, wherein the measConfig IE configures the UE to measure a set of non-serving frequencies associated with an adjacent cell, and the first RRCReconfiguration message indicates one or more objectives of carrier aggregation (CA) or dual connectivity (DC), and the objectives are indicated via one or more of a measurement report configuration or a measurement object configuration.

[0186] Example 66 includes the subject matter of any variation of any of Examples 62 - 65, and the measConfig IE indicates a set of non - serving frequencies associated with neighboring cells via a measurement target associated with a set of serving frequencies.

[0187] Example 67 includes the subject matter of any variation of any of Examples 62 - 66, and includes a set of non - serving frequencies when one or more measurements of one or more sets of frequencies exceed a configured threshold of one or more measurements of the set of non - serving frequencies.

[0188] Example 68 includes the subject matter of any variation of any of Examples 62 - 67, and further includes generating a System Information Block (SIB) associated with adjacent cell measurements indicating a set of non - serving frequencies.

[0189] Example 69 comprises an apparatus including means for performing any of the operations described in Examples 41 - 68.

[0190] Example 70 comprises a machine - readable medium storing instructions executable by a processor to perform any of the operations described in Examples 41 - 68.

[0191] Example 71 comprises an apparatus including a memory interface and a processing circuit configured to perform any of the operations described in Examples 41 - 68.

[0192] Example 72 comprises a base station (BS) configured to perform any of the operations described in Examples 41 - 68.

[0193] The foregoing description of illustrative aspects of the disclosed subject matter, including what is set forth in the Abstract, is not intended to be exhaustive or to limit the disclosed aspects to the precise forms disclosed. Specific aspects and examples are described herein for illustrative purposes, but as will be recognized by those of ordinary skill in the art, various modifications are possible within the scope of such aspects and examples.

[0194] In this regard, although the disclosed subject matter has been described in connection with various aspects and corresponding drawings, it should be understood that other similar aspects can be used, or modifications and additions can be made without departing from the described aspects, in order to perform the same function, similar function, alternative function, or substitute function as the disclosed subject matter, where applicable. 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 following appended claims.

[0195] In particular, with respect to the various functions performed by the above-described components or structures (assemblies, devices, circuits, systems, etc.), the terms used to describe such components (including descriptions related to "means") are intended to correspond to any component or structure that performs the specific function of the described component, even if not structurally equivalent to the disclosed structure that performs the functions of the exemplary implementations of the invention illustrated herein (e.g., functionally equivalent), unless otherwise specified. Further, although a particular feature may be disclosed with respect to only one of several implementations, such a feature may be combined with one or more other features of one or more other implementations so as to be desirable and advantageous for any given or particular application.

Claims

1. A base station (BS) device comprising a processor and a memory, wherein the processor, by executing instructions stored in the memory, transmits a first RRC Reconfiguration message including a measConfig information element (IE) to a user equipment (UE), wherein the first RRC Reconfiguration message explicitly indicates, via a binary flag included in a measurement report configuration or a measurement object configuration, the purpose of one or more measurements of carrier aggregation (CA) and dual connectivity (DC), and the measConfig IE configures and transmits one or more measurements on a set of non-serving frequencies associated with an adjacent cell, receives a MeasurementReport message from the UE indicating the one or more measurements, and based on the MeasurementReport message, transmits a second RRC Reconfiguration message configuring the UE in one or more of the CA and DC. The BS device is configured to perform operations including the above.

2. The BS device according to claim 1, wherein the first RRC Reconfiguration message is generated in response to a measurement request received from the UE.

3. The BS device according to claim 2, wherein the measurement request includes one or more of a single bit indicating the measurement request, an indication of a radio access technology (RAT) for the measurement, the set of non-serving frequencies, or a first set of frequencies of the set of non-serving frequencies for measurements without a measurement gap.

4. The BS device according to claim 1, wherein the purpose of the measurement is indicated via one or more of a measurement report configuration or a measurement object configuration.

5. The BS device according to claim 1, wherein the measConfig IE indicates the set of non-serving frequencies associated with the adjacent cell via a measurement object associated with a set of serving frequencies.

6. The BS device according to claim 1, wherein the set of non-serving frequencies is configured in the MeasurementReport message when the one or more measurements of the set of non-serving frequencies exceed a configured threshold of the one or more measurements.

7. The BS device according to claim 1, wherein the operation further includes generating a system information block (SIB) associated with adjacent cell measurements indicating a set of the non-serving frequencies.

8. A machine-readable medium comprising instructions that, when executed, cause a base station (BS) to receive, from a user equipment (UE), a UE assistance information message including a measurement request, send, in response to the measurement request, a first RRC Reconfiguration message including a measConfig information element (IE) to the UE, wherein the first RRC Reconfiguration message explicitly indicates, via a binary flag included in a measurement reporting configuration or a measurement object configuration, an objective of one or more measurements of carrier aggregation (CA) and dual connectivity (DC), and the measConfig IE configures one or more measurements on a set of non-serving frequencies associated with adjacent cells, receive, from the UE, a MeasurementReport message indicating the one or more measurements, send, based on the MeasurementReport message, a second RRC Reconfiguration message that configures the UE using the adjacent cells.

9. The machine-readable medium according to claim 8, wherein the measurement request includes one or more of a single bit indicating the measurement request, an indication of a radio access technology (RAT) for the measurement, the set of non-serving frequencies, or a first set of frequencies of the set of non-serving frequencies for measurements without a measurement gap.

10. The machine-readable medium according to claim 8, wherein the objective of the measurement is indicated via one or more of a measurement reporting configuration or a measurement object configuration.

11. The machine-readable medium according to claim 8, wherein the measConfig IE indicates the set of non-serving frequencies associated with the adjacent cells via a measurement object associated with a set of serving frequencies.

12. The machine-readable medium according to claim 8, wherein the set of non-serving frequencies is configured in the MeasurementReport message when the one or more measurements of the set of non-serving frequencies exceed a configured threshold of the one or more measurements.

13. The machine-readable medium according to claim 8, wherein when the command is executed, the BS is further caused to generate a system information block (SIB) associated with adjacent cell measurements indicating a set of the non-serving frequencies.

14. A baseband processor, decoding a UE assistance information message received from a user equipment (UE) and including a measurement request; generating a first RRC Reconfiguration message for transmission, the first RRC Reconfiguration message including a measConfig information element (IE), the first RRC Reconfiguration message explicitly indicating, via a binary flag included in a measurement report configuration or a measurement object configuration, an object of one or more measurements of carrier aggregation (CA) and dual connectivity (DC), the measConfig IE configuring one or more measurements on a set of non-serving frequencies associated with adjacent cells; decoding a Measurement Report message received from the UE and based on the first RRC Reconfiguration message, the Measurement Report message indicating the one or more measurements; generating a second RRC Reconfiguration message for transmission based on the Measurement Report message, the second RRC Reconfiguration message configuring the UE with one or more of the CA and DC; A baseband processor configured to perform operations including the above.

15. The baseband processor according to claim 14, wherein the first RRC Reconfiguration message is generated in response to the UE assistance information message.

16. The baseband processor according to claim 14, wherein the measurement request includes one or more of a single bit indicating the measurement request, an indication of a radio access technology (RAT) for the measurement, a set of the non-serving frequencies, or a first set of frequencies of the set of the non-serving frequencies for the measurement without a measurement gap.

17. The baseband processor according to claim 14, wherein the purpose of the measurement is indicated via one or more of a measurement report configuration or a measurement target configuration.

18. The baseband processor according to claim 14, wherein the measConfig IE indicates the set of non-serving frequencies associated with the neighboring cell via a measurement target associated with a set of serving frequencies.

19. The baseband processor according to claim 14, wherein the set of non-serving frequencies is configured in the MeasurementReport message when one or more measurements of the set of non-serving frequencies exceed a configured threshold of the one or more measurements.

20. The baseband processor according to claim 14, wherein the operation further includes generating a system information block (SIB) associated with a neighboring cell measurement indicating the set of non-serving frequencies.

Images