CN107431957B - Cell-specific group measurement gap device, readable medium and system for carrier aggregation - Google Patents

Abstract

A network device (e.g., an evolved node b (enb) or User Equipment (UE)) may identify a measurement object identifier and a measurement gap pattern to enable network measurements of carriers or bands during measurement gaps. For version 13 or higher, a measurement object identifier may be added. Measurement gap patterns may be communicated to reduce measurement delay and improve data efficiency in the downlink. The measurement gap pattern and the transmission or reception of measurement objects (e.g., carriers or bands) communicatively coupled on the network may be communicated by one or more Radio Resource Control (RRC) signals.

Description

Cell-specific group measurement gap device, readable medium and system for carrier aggregation

Reference to related applications

This application claims the benefit of U.S. provisional patent application No.62/145,318 entitled "CELL SPEC MG" filed on 9.4.2015, the contents of which are incorporated herein by reference in their entirety.

Technical Field

The present disclosure relates to measurement gaps (measurement gaps), and more particularly, to cell-specific group measurement gaps for carrier aggregation.

Background

Wireless mobile communication technology uses various standards and protocols to transmit data between a node (e.g., a transmission station) and a wireless device (e.g., a mobile device) or User Equipment (UE). Some wireless devices communicate using Orthogonal Frequency Division Multiple Access (OFDMA) in Downlink (DL) transmissions and single carrier frequency division multiple access (SC-FDMA) in Uplink (UL) transmissions. Standards and protocols for signal transmission using Orthogonal Frequency Division Multiplexing (OFDM) include the third generation partnership project (3GPP) Long Term Evolution (LTE), the Institute of Electrical and Electronics Engineers (IEEE)802.16 standards (e.g., 802.16e, 802.16m, commonly referred to in the industry as WiMAX (worldwide interoperability for microwave access)), the IEEE 802.11 standard (commonly referred to in the industry as WiFi).

In a 3GPP Radio Access Network (RAN) LTE system, a node may be a combination of an evolved universal terrestrial radio access network (E-UTRAN) node B (also commonly denoted as evolved node B, enhanced node B, eNodeB, or eNB) and a Radio Network Controller (RNC) that communicates with UEs. Downlink (DL) transmissions may be communications from an access point/node or base station (e.g., a macro cell device, eNodeB, eNB, or other similar network device) to a UE, and Uplink (UL) transmissions may be communications from a wireless device to a node. In LTE, data may be transmitted from an eNodeB to a UE via a Physical Downlink Shared Channel (PDSCH). The received data may be acknowledged using a Physical Uplink Control Channel (PUCCH). The downlink and uplink channels may use Time Division Duplexing (TDD) or Frequency Division Duplexing (FDD).

Due to the development and higher demand of newer technologies in wireless communications, future network deployments will ensure that the number of frequencies continues to increase. The number of cells and frequency requirements will increase. Macro cell network devices, small cell network devices, or other such network devices having smaller coverage or lower power capabilities than macro cell devices (e.g., small enbs, pico enbs, femto enbs, home enbs (e.g., henbs)) may also be introduced into the dual connectivity feature specified in 3GPP release 12. Thus, a User Equipment (UE) (e.g., a network device, a mobile device, a wireless device, etc.) can simultaneously connect two or more cells.

To facilitate smooth network transitions (e.g., cell handover, redirection, reselection, etc.) with high quality of experience (QoE), a UE must have the capability to measure surrounding cells and provide relevant data to the network. In a network deployment scenario where there may be many frequencies, some frequency carriers may be microcells deployed back-to-back in a dense network deployment. However, the UE may not be able to handover to these cells, e.g. due to large load within the macro cell. As a result of the high density of network deployments, the UE may not have access to these small cells depending on the location of the UE. If the UE misses the opportunity to measure the small cell frequency carrier, there may be no backup network available. In addition, if measurements on the macro layer are missed, the UE may not be able to handover fast enough and the call may be lost. Thus, for example, the network may assign a macro cell layer or particular network device (e.g., one or more macro/small cell network devices) to the normal performance group and a small cell layer or other particular network device (e.g., one or more macro/small cell network devices) to the reduced performance group, such that the UE will perform more measurements in the normal performance group and less measurements in the reduced performance group. The reason for introducing these two groups is that 3GPP release 12 increases the number of carriers measured by the UE. This causes more delay for measuring one specific carrier, since the UE has to measure more carriers.

Drawings

Fig. 1 illustrates a block diagram of an example wireless communication network environment for a UE or eNB in accordance with various aspects.

Fig. 2 illustrates an example of a data gap indicating a number of measurement objects in accordance with various aspects or embodiments disclosed herein.

Fig. 3 illustrates an exemplary measurement gap pattern in accordance with various aspects or embodiments disclosed herein.

Fig. 4 illustrates an example UE device with different radio frequency processing chains and corresponding band coverage in accordance with various aspects or embodiments disclosed.

Fig. 5 illustrates another example measurement gap pattern in accordance with various aspects or embodiments disclosed herein.

Fig. 6 illustrates an exemplary modification of a measurement gap configuration information element of version 13 or higher in accordance with various aspects or embodiments disclosed.

Fig. 7 illustrates an example of a measurement gap configuration information element for version 13 or higher in accordance with various aspects or embodiments disclosed.

Fig. 8 illustrates another example measurement gap pattern in accordance with various aspects or embodiments disclosed herein.

Fig. 9 illustrates another exemplary measurement gap pattern as a small gap pattern in accordance with various aspects or embodiments disclosed.

Fig. 10 illustrates an exemplary modification of a measurement gap configuration information element of version 13 or higher in accordance with various aspects or embodiments disclosed.

Fig. 11 illustrates an example of a measurement gap configuration information element for version 13 or higher in accordance with various aspects or embodiments disclosed.

Fig. 12 illustrates a process flow for a measurement gap pattern for a network in accordance with various aspects or embodiments disclosed.

Fig. 13 illustrates another process flow for a measurement gap pattern for a network in accordance with various aspects or embodiments disclosed.

Fig. 14 illustrates another process flow for another measurement gap pattern for a network in accordance with various aspects or embodiments disclosed.

Fig. 15 illustrates another process flow for another measurement gap pattern with small gaps for a network in accordance with various aspects or embodiments disclosed.

FIG. 16 illustrates an example electronic (network) device in accordance with various aspects.

Fig. 17 illustrates an example system that operates a network measurement gap pattern in accordance with various aspects.

Detailed Description

The present disclosure will now be described with reference to the drawings, wherein like reference numerals are used to refer to like elements throughout, and wherein the illustrated structures and devices are not necessarily drawn to scale. As used herein, the terms "component," "system," "interface," and the like are intended to refer to a computer-related entity, hardware, software (e.g., in execution), and/or firmware. For example, a component may be a processor, a process running on a processor, a controller, a circuit or circuit element, an object, an executable, a program, a storage device, a computer, a tablet, and/or a cell phone with a processing device. By way of illustration, both an application running on a server and the server can be a component. One or more components may reside within a process and a component may be localized on one computer and/or distributed between two or more computers. A set of elements or a set of other components may be described herein, wherein the term "set" may be interpreted as "one or more.

In addition, these components can execute from various computer readable storage media having various data structures stored thereon (e.g., in modules). The components may communicate by way of local and/or remote processes such as in accordance with a signal having one or more data packets (e.g., data from one component interacting with another component in a local system, distributed system, and/or across a network such as the internet, a local area network, wide area network, or the like having other systems via the signal).

As another example, a component may be an apparatus having a particular functionality provided by mechanical parts operated by electrical or electronic circuitry, where the electrical or electronic circuitry may be operated by a firmware application or software application executed by one or more processors. The one or more processors may be internal or external to the device and may execute at least a portion of a software or firmware application. As yet another example, an assembly may be a device that provides a particular function through electronic components or elements without the use of mechanical components; the electronic components may include one or more processors therein to execute software and/or firmware that at least partially impart functionality to the electronic components.

The use of the word "exemplary" is intended to present concepts in a concrete fashion. As used in this application, the term "or" is intended to mean an inclusive "or" rather than an exclusive "or". That is, unless specified otherwise, or clear from context, "X employs A or B" is intended to mean any of the natural inclusive permutations. That is, if X employs A; x is B; or X employs both A and B, then "X employs A or B" is satisfied under any of the foregoing circumstances. In addition, the words "a" and "an" as used in this application and the appended claims should generally be construed to mean "one or more" unless specified otherwise or clear from context to be directed to a singular form. Furthermore, to the extent that the terms "includes," including, "" has, "" configured with, "or variants thereof are used in either the detailed description or the claims, such terms are intended to be inclusive in a manner similar to the term" comprising.

In view of the above-described deficiencies, network devices (e.g., macro cells, Access Points (APs), Access Controllers (ACs), enbs, small cells, UEs, etc.) described herein may implement one or more specific measurement gap patterns and related solutions to support LTE Carrier Aggregation (CA) for up to 32 Carrier Components (CCs) for DL and UL. For CA procedures, two measurement performance groups alone may not be sufficient for LTE CA to support up to 32 CCs or more. Various measurement gap patterns are proposed in the present disclosure to more efficiently measure carriers at measurement gaps. The measurement gap pattern may be referred to, for example, as a pattern of measurement gaps (at which the UE may facilitate frequency carrier measurements over a period or duration). For example, a UE may operate during a measurement gap to switch from a serving frequency band to which it is connected to a different frequency band to perform carrier measurements. The term serving band as used herein means that the UE can connect to this band as the serving band and can receive downlink data, in which case measurements in this band are not necessarily needed, since the UE is already operating in this band.

For example, in one measurement gap mode, a first receive circuit component (e.g., an RF chain or pipeline having one or more antenna ports, antennas, filters, signal processors, or other circuitry for processing signals received at one or more frequencies) may be configured to operate on a first frequency band during a first measurement gap to facilitate measurement of the first frequency band. Further, measurements may be made on the second frequency band at the second measurement gap. The first receive circuit assembly may also operate on the first serving frequency band to conduct downlink transmissions of data outside of the measurement gap pattern, or at other time periods or intervals outside of the first measurement gap or the second measurement gap, e.g., to distinguish from the serving frequency band on which the additional/second receive circuit will operate.

The second or additional receive circuit components may also be configured to operate on the third frequency band at the first measurement gap and operate on the fourth frequency band at the second measurement gap to facilitate measurement of the third and fourth frequency bands during the respective measurement gap. The second receive circuit component may further operate on the second serving frequency band for downlink transmission of data during other time periods. The first service band, the second service band, the first band, the second band, the third band, and the fourth band may be carrier frequencies different from each other.

In one embodiment, the first and second receive circuit components are further configured to receive downlink data in different measurement gaps existing between the first and second measurement gaps. Thus, the sequence used for the measurement during the measurement gap will alternate between measuring the respective frequency bands covered by the first and second receive circuit components and downlink data transmission on their respective serving frequency bands. In this way, downlink data can be suppressed when measurements are made during measurement gaps. One advantage here is that the problem of no or very little downlink data can be ameliorated by increasing the downlink data efficiency.

In another embodiment, the first receive circuitry component may facilitate measurement of the first frequency band at a first measurement gap and measure the second frequency band at a second measurement gap while downlink transmission of data on the first service frequency band. The first receive circuit component may not perform measurements or perform downlink transmission of data at the third measurement gap and perform downlink transmission of data on the serving frequency band at the fourth measurement gap. At the same time, or substantially the same time, the second receive circuit component may perform downlink transmission of data on a second serving frequency band different from the first serving frequency band at the first measurement gap, perform no measurement or downlink transmission of data at the second measurement gap, measure the third frequency band while performing downlink transmission of data on the second serving frequency band at the third measurement gap, and measure the fourth frequency band at the fourth measurement gap. Additional aspects and details of the present disclosure are further described below with reference to the figures.

Fig. 1 illustrates an example non-limiting wireless communication environment 100 that can facilitate or enable one or more measurement gap configurations for LTE CA to support an increased number of frequency carriers or carrier components through communication between a base station network device (e.g., an eNB) and a UE. The wireless communication environment 100 may include a plurality of wireless communication networks, each having a respective coverage area. The coverage areas of some wireless communication networks may overlap such that one or more mobile devices may be served by any of the network devices whose coverage areas overlap.

The wireless communication environment 100 includes one or more cellular broadcast servers or macrocells ND102, 104 (e.g., base stations, enbs, APs, etc.), and one or more small cells ND or APs (e.g., small enbs, micro enbs, pico enbs, home enbs (henbs), or Wi-Fi nodes) 106, 108 deployed within the wireless communication environment 100 and serving one or more UE devices 110, 112, 114, 116, 118. Each wireless communication network (e.g., cellular broadcast servers 102a and 104 and small cell network devices 106, 108) includes one or more network devices (e.g., a set of Network Devices (NDs)) that operate jointly to process network traffic for one or more UE devices 110, 112, 114, 116, or 118. For example, the macrocell NDs 102, 104 may include a set of network devices that are cellular enabled network devices. In another example, the small cell network devices 106, 108 may comprise a set of network devices operating with a smaller coverage area than the macro cell network devices 102 and 104, for example.

Although the Network Devices (NDs) 106 and 108 are described as small cell network devices, they may also be Wi-Fi enabled devices or Wireless Local Area Network (WLAN) devices, as well as macro cell network devices, small cell network devices, or some other type of ND operable, for example, as a base station or eNB. Alternatively, one or more of the macro cells NDs 102 and 110 may be small cell network devices or other NDs of different Radio Access Technologies (RATs), e.g., operating using different frequency carriers.

As shown, each of the one or more Wi- Fi access points 106, 108 may have a corresponding service area 120, 122. Additionally, each of the one or more cellular broadcast servers or macrocells ND102, 104 may have a respective service area 124, 126. It should be understood, however, that the wireless communication environment 100 is not limited to this implementation. For example, any number of APs or NDs with corresponding service areas may be deployed in the wireless communication environment 100. In addition, any number of cellular broadcast servers and corresponding service areas may also be deployed within the wireless communication environment 100.

Although only five UE devices 110, 112, 114, 116, 118 are shown, any number of UE devices may be deployed within the wireless communication environment 100. A UE device may, for example, contain some or all of the functionality of a system, subscriber unit, subscriber station, mobile, wireless terminal, device, mobile, remote station, remote terminal, access terminal, user terminal, wireless communication device, wireless communication apparatus, user agent, user device, or other ND. A mobile device may be a cellular telephone, a cordless telephone, a Session Initiation Protocol (SIP) phone, a smart phone, a feature phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA), a laptop, a handheld communication device, a handheld computing device, a netbook, a tablet, a satellite radio, a data card, a wireless modem card, and/or another processing device for communicating over a wireless system. Further, the UE devices 110, 112, 114, 116, 118 may include functionality as described more fully herein, and may also be configured as dual connectivity devices, where one or more UE devices 110, 112, 114, 116, 118 may be connected to more than one eNB or ND of different RATs (e.g., LTE and WLAN or other combinations).

In one aspect, the cellular broadcast servers or macro cells ND102, 104 and small cells ND 106, 108 may monitor radio conditions around them (e.g., by employing respective measurement components). For example, each of the macro cell ND102, 204 and the small cell ND 106, 108 may determine the network traffic load on its respective network by performing a network diagnostic procedure. As an example, during the network listening process, the macro cell ND102, 104, small cell ND 106, 108, or UE device 110, 112, 114, 116, 118 may scan its radio environment to determine network performance statistics or network parameters (e.g., frequency, SNR, signal quality, QoS, QoE, load, congestion, signal rate, etc.). Various parameters associated with the macro cells ND102, 104, small cells ND 106, 108, such as, but not limited to, frequency band, scrambling code, common channel pilot power, bandwidth of the respective networks, universal mobile telecommunications system terrestrial radio access received signal strength indicator, and frequency carrier priority for a particular group of cells (e.g., normal or reduced group), etc., may be detected during measurements by the UE device or during network diagnostic procedures.

In an example scenario, the UE devices 110, 112, 114, 116, 118 may be served by the network through one of the macro cell ND102, 104 or the small cell ND 106, 108. As user equipment devices move within the wireless communication environment 100, the respective user equipment devices may move into and out of the coverage area of the associated serving network. For example, when users send/receive communications through their respective UE devices, the users may be walking, riding in cars, riding in trains, moving around densely populated urban areas (e.g., metropolitan cities), where the movement may cause the mobile devices to move between various wireless communication networks. In such a case, it would be beneficial for the UE to route network traffic from the serving ND to the target ND (e.g., handover) to continue communication (e.g., to avoid call loss) or to facilitate offloading for load distribution or other efficiency objectives. However, as ND and the number of frequency carriers to measure increase, the UE devices 110, 112, 114, 116, 118 may have problems when each carrier is to be measured within the allocated time measurement gap. These measurement gaps may introduce more delay because the UE devices 110, 112, 114, 116, 118 must measure an increased number of carriers (e.g., 32 or more).

In one example, if there are two frequency carriers of different frequencies (e.g., carrier components of LTE CA) on the network environment 100, where 40 milliseconds (ms) is a measurement gap. Since there are two carriers, the UE device 110, 112, 114, 116, 118 will operate on one carrier as the serving frequency, so only one additional carrier needs to be measured. In this way, a UE (e.g., UE 110) will switch to another carrier to measure on every 40 ms. This means that UE 110 will make one measurement every 40ms (as Measurement Gap Reception Period (MGRP)). In each measurement sample, a measurement may include any network measurement of a network condition related to a frequency band, a network device operating (transmitting) the frequency band, or a channel condition, such as signal strength, channel quality, a load condition of the ND, or other measurements (e.g., Reference Signal Received Power (RSRP), Reference Signal Received Quality (RSRQ), Channel State Information (CSI), one or more Channel Quality Indicators (CQIs), etc.).

However, if two additional carriers exist on the network or within communication range (communicatively coupled to UE device 110) to be measured by UE device 110, then three carriers exist on the network, including the serving frequency carrier on which UE device 110 may conduct downlink transmissions of data and communications. In a first measurement gap of the gap sequence, the UE device 110 may, for example, measure a second frequency (the serving frequency being the first frequency), and in a second or subsequent measurement gap the UE device 110 may measure a third frequency of the different carrier. This means that the UE device can only make measurements every 80 ms. This is longer than the delay of only one frequency carrier that needs to be measured, where the total delay is proportional to the number of carriers that the UE device 110 has to measure. Thus, 32 or more carriers would mean a gap delay of about 32 x 40ms (measurement gap repetition/reception period) to obtain one sample of a particular frequency or frequencies (inter or intra frequency) of one or more different NDs. Such a long delay may cause problems for the UE, which may not be able to measure the frequency within a sufficient or valid time frame. This longer delay may also create additional problems in the following cases: for example, a network handover or a determination of which cell or cell ND is best in a sufficient time based on the conditions of the UE device 110.

On the one hand, the network objective is therefore to enhance the time measurement gaps for carriers belonging to the normal performance group, which can receive more measurements than the reduced performance group. The network may assign which operators or NDs are part of which group. For example, the normal performance group may have macro cells ND 202 and 204, while the reduced performance group may have small cells ND 106, 108; any mix of NDs and associated frequency carriers may be specified by the network or ND device (e.g., macrocell ND102), etc. The ND or UE of the network may be enhanced in various embodiments to enable carrier aggregation of up to 32 component carriers for both DL and UL, and further to enable, for example, that five or more frequency carriers may be supported at a time. Thus, in addition to or instead of CA, two measurement performance groups of CA, various cell-specific measurement gap patterns for CA are disclosed to support up to 32 CCs in CA.

Referring to fig. 2, an example of an Identifier (ID) from an eNB indicating the number of measurements of a carrier by a UE is shown. In Radio Resource (RRM) measurement in LTE, a frequency carrier or a frequency band in which a UE performs measurement may be configured by a measurement object (e.g., measObject). For example, the maximum number of measurement object IDs maxobjeld 202 may be defined in the 3GPP specifications. In principle, a single measurement object is configured per Radio Frequency (RF) carrier. Considering up to thirty-two CCs designed for Rel-13CA, the number of measurement object IDs theoretically to reach the target may be increased to an even larger value (e.g., 64). On the other hand, the maximum value represented by data field 202 is still sufficient. There may be some cases where the eNB may acquire necessary information for CC management purposes from a measurement report on one CC in the same frequency band when the UE configures up to 32 CCs. For example, such a scheme may be applied at least to aggregation of carriers B and C when carriers B and C are in the same frequency band. Accordingly, the required measurement object ID can be reduced, and the current value will be sufficient.

The ID 202 includes 32 CCs as a measure of the specified object ID. When the network adds measurement objects to accommodate more than 32 CCs (e.g., in the data ID 204 maxObject ID specifying the maximum integer 64), the network may also configure more measurement objects to link to the measurement configuration (MeasGapConfig), 32 of which may not be enough. Thus, to accommodate the increase in the number of carrier frequencies, the eNB may provide a proposed increase to about 64 or other numbers of CCs, which is merely one example. For example, the E-UTRAN may apply a processor with, for example, data ID 202 or 204 or some other addition, to, for example, ensure that whenever the UE receives a measConfig, it includes a measObject for each service frequency with maxoobjectid.

Referring to fig. 3, an example of a measurement gap pattern 300 according to various embodiments and with reference to fig. 1 is shown. The measurement gap pattern 300 may operate with a measurement gap repetition/reception period of 40ms or 80ms, for example. For example, the measurement gap pattern 300 may be implemented with a single server (serving) band for operation with a single Radio Frequency (RF) chain (not shown) with a constant gap duration of approximately 6ms for each gap, which is provided by the eNB (e.g., ND102) to the UE device (e.g., 114). For example, an RF chain (e.g., transmit circuit components/receive circuit components) may include one or more processing components (e.g., filters, digital signal processors, amplifiers, or other components for processing data signals) that may cover various ranges of the RF spectrum. The UE 114 does not have to make inter-frequency measurements for a particular frequency carrier (e.g., in the measurement gap pattern 300) with all RF chains.

As described above, the duration of each gap may be approximately 6ms, for example, as applied or configured by the eNB (e.g., the ND102) to the UE device 114 of fig. 1. There is no data transmission in this 6ms gap. However, the UE device 114 may also have CA capability, meaning that the UE device 114 may operate with more than one RF chain at a time. Thus, with more than one RF chain, it is possible for the UE device 114 to increase throughput gain by using some RFs for measurements and having data transmissions at the same time. Thus, Radio Resource Management (RRM) measurements without gaps may result in throughput gains of up to 15% (e.g., 40ms MGRP), and it is therefore desirable to improve UE device performance, especially in cases where the CA has a large number of CCs. To achieve this advantage, the measurement gaps are preferably applied only to the relevant serving cell (i.e., the serving cell operating on the RF circuitry measuring the relevant frequency).

The measurement gap pattern 300 (i.e., 40ms MGRP or 80ms MGRP) may be configured by the network to the UE. The network takes into account that the UE performs measurements of one band at a time to meet the measurement requirements, and that all bands during the measurement gap will have no downlink transmission. For example, the network may have five available frequencies such that the serving frequency band is band a 302 (which may be the serving frequency over which the UE facilitates operation of the connection). For example, other frequency bands may include band X304, band Y306, band Z308, and band L310. A black gap indicates where no measurements can be made, a darker shaded gap (e.g., gap 312) indicates where measurements of the frequency band can be performed, and a lighter shaded gap (e.g., 314) indicates where no data transmission occurs.

Based on the measurement gap pattern 300, the UE device 114 may perform measurements on band X304 in the first 40 millisecond gap 316 without data transmission on the serving band a 302. For example, each frequency band may represent a frequency band or frequency range for DL or UL. Then in the next 40ms measurement gap 318, the UE device 114 may measure band Y306. Subsequently, in a third measurement gap 320, the UE device 114 may measure band Z308 and subsequently measure band L310 in a fourth measurement gap 322. Subsequently, the UE device 114 may again cycle through to measure frequency band X304 again, where the sequence of measurement gaps may be continuously repeated.

Referring to fig. 4, an example of a CA scenario 400 is shown along with an example UE 114, where for an RF chain 1402, the UE device 114 may cover, for example, band X304 and band Y306. Each RF chain 1402 and 2404 may include one or more components for a signal processing chain, e.g., which may include filters and hardware for incrementing the filters and further processing the RF signals for the data. Not all RF chains can cover all frequency bands at once, since the frequencies can be very high. For example, RF chain 1402 can only cover band X304 (e.g., any frequency range specified by 3GPP for DL or UL) and band Y306. Further, the RF chain 2404 can only cover band Z308 and band L310, where each RF chain 1402 and RF chain 2404 can cover certain bands or bandwidths of spectrum.

Referring now to fig. 5, an example of another measurement gap pattern 500 for a release 13 or higher version of a measurement gap configuration information element is shown to reduce measurement delay by one or more network devices on a network. As with the measurement gap pattern 300 of fig. 3, the pattern of measuring the delay in the measurement gap pattern 500 to make four measurements to obtain measurement samples for each frequency band (e.g., frequency bands X, Y, Z and L) occurs. Thus, every 160ms, the UE device 114 may obtain one sample of each frequency band, which is considered to be a measurement delay. In measurement gap pattern 300, if UE device 114 can measure frequency bands X304 and Y306, for example, using one serving frequency, and simultaneously measure frequency bands Z and L using a second serving frequency.

In the first measurement gap 502, the UE device 114 may use the RF chain 1402 to measure band X304 and the RF chain 2404 to measure sum band Z308 and to make simultaneous measurements. Similarly, in the second measurement gap 504, the UE device 114 may measure band Y with the RF chain 1402 and band L310 with the RF chain 2404. This pattern then repeats itself for the measurement gaps 508 and 510. Now in each measurement gap, the UE device 114 can measure two bands instead of one, so the measurement delay is cut in half, since the UE device 114 can utilize two RF chains simultaneously. For example, in this case only two measurement gaps are used to obtain measurement samples for all frequency bands, and no four measurement gaps are required.

However, the network may assume that UE device 114 has only one RF chain instead of two, and that the measurement requirements are also based on only one RF chain, unless sufficient communication between the network devices (e.g., UE and eNB) is ensured that it will not utilize the network capabilities. Therefore, gap configurations may also be added to the 3GPP standard (TS 36.331) to further facilitate communication based on CA-specific measurement mode measurements. Instead of using only the existing zeros and ones (i.e. 40ms and 80ms), an additional specification CA-gap 0602 may be added as shown in fig. 6, which is part of the measurement gap configuration (MeasGapConfig) on the Information Element (IE) 600.

Fig. 6 illustrates an example of a measurement gap configuration or MeasGapConfig that enables transmission and implementation of a measurement gap pattern between NDs (e.g., eNB(s) and UE (s)), e.g., as shown in fig. 5 and 8. A data slot or entry CA-gap 0602 indicates an interval repetition period 604 (which may be 40ms and 80ms), and one or more backups (spares) for optional or future extensions. In addition, the CA-gap 0602 data entry of the measgapcfig IE may also include a measurement gap offset 606, which indicates when the gap starts for further measurements. CA-gap 0602 further indicates a band measurement list (bandMeasurementList)608, which includes which measurement band the UE should measure using the measurement gap. For example, reduced performance groups or normal performance groups may be divided and designated, and certain bands requiring more frequent or full measurements are also indicated by utilizing band measurement list 608.

The gap offset (gapOffset)602 describes a gap offset for which the gp0 value may correspond to a gap pattern Id "0" of 40ms, for example, measurement gap repetition/reception period (MGRP). The gap offset of gp1 may correspond to the gap offset of gap pattern "1" with MGRP being 80 ms. These gap offset pattern IDs may be used to specify the measurement gap pattern to be applied (as defined in release 3 or higher specifications), e.g., which provides information (e.g., via the UE or eNB) for determining, e.g., the choice between IDs. For example, ca-gap 0602 includes gapOffset-r 13606 as a gapOffset value based on a selected gap pattern repetition period (or MGRP) (gapRepetitionperiod) or based on a measurement gap pattern repetition period as defined in 3GPP specification TS 36.133. Finally, the bandMeasurementList specifies or indicates the frequency band that should be measured using the same gap period or MGRP.

Alternatively, fig. 7 shows a compatible measurement configuration (measgapcfig) IE alternative to 3GPP release 13 for carrier aggregation (e.g., CA-measgapcfonfig-r 13ID) 700. A first option may be to add another measurement gap in the existing IE (as provided above in fig. 6), although the new measurement gap configuration CA-measgapcfig-r 13IE of CA 700 may be shown with at least some similarities to IE 600 of fig. 6. For example, the gap repetition period 702 may be 40ms and 80ms, with one or more backups for optional or future expansion. Additionally, the measgapcfonfig-r 13IE may also include a measurement gap offset 704, which may indicate when the gap begins for further measurements and is based on the selected gap pattern repetition period. The band measurement list (bandMeasurementList)706 also includes which measurement band the UE should measure using the measurement gap or measurement gap pattern.

Fig. 8 illustrates another gap pattern 800 that can enable increased downlink data efficiency between network devices (e.g., eNB(s) and UE (s)). As described above, the UEs serving the bands are bands a + B302 and 502. In addition to X304 and Y306, RF chain 1402 (RF _1) also supports service band a 302. In addition to Z308 and L310, RF chain 2404 (RF _2) also supports service band B502. Thus, for example, the UE device 114 may use both the RF chain 1402 and the RF chain 2404 in the first measurement gap slot 504 to simultaneously measure on bands X304 and Z308. Similarly, the UE device 114 may also simultaneously measure bands Y306 and L310 in the third measurement gap slot 508. With the same measurement performance, the UE device 114 may now facilitate or enable downlink data transmission on the frequency bands a + B302 and 502 in the second measurement gap time slot 506 and the fourth measurement gap time slot 4510.

As such, the network device may use the measurement gap pattern 800 as a CA-specific gap pattern to improve downlink data efficiency over other measurement gap patterns (e.g., as shown above). Thus, as shown in the above figure, the network or ND may configure a similar data pattern as the UE device 114. However, rather than allowing the UE device 114 to make more measurements with the RF chain, the network may send data down to the UE device 114 during some gap patterns as a compromise of configuration. For example, the decision from the eNB or other network device or entity may be based on, for example, network conditions, a request or status report for the most needed resources, reduced latency, increased data efficiency/transmission, or a combination of both.

Fig. 9 illustrates another example of a measurement gap pattern 900 that may take advantage of the two advantages described above (an increase in data efficiency/transmission and a decrease in delay via one or more network devices (e.g., eNB 102, ND 14, or other NDs)). The previously discussed measurement gap pattern 800 of fig. 8 increases data transmission, allowing data to pass through the downlink between certain data measurement gaps (e.g., every other measurement gap or measurement gap). The measurement gap pattern 900 enables data transmission in a small gap (minigap) or small gap pattern fashion while keeping measurements of downlink data and frequency bands continuous.

In the measurement gap pattern 900, the UE device 114 may, for example, indicate the frequency bands it can support and, at the same time, allow different RF chains to have downlink data, with the tradeoff being interruptions 902 and 904. For example, the network, network device 102, or other network device may transmit alternate RF chains 1 or 2 (e.g., RF chains 402 and 404) within measurement gaps 504, 506, 508, and 510 in a small-gap pattern and at off times. The UE device 114 may be configured to operate on the serving frequency bands a and B302 and 502. When the UE device 114 measures band X304, for example using RF chain 1402, the serving band a 302 has no data transmission. However, UE device 114 may still receive downlink data in band B during RF tuning using RF chain 2404 with interruptions 902 and 904.

In each measurement gap 504, 506, 508, and 510, the UE device 114 may measure one frequency band (e.g., X, Y, Z or L) at a time, which means that the UE device 114 still has one idle RF chain for receiving data. Thus, if the UE device 114 is performing CA, the network may do so in a frequency band that may be covered by or correspond to an available or idle RF chain that the UE device 114 has. Since the measurement and data transmission are simultaneous, there is an interruption of about 1ms, represented by the cross pattern squares in fig. 9, where the network will not be able to download data. Thus, the measurement gap mode 900 is referred to as a small gap mode because when the UE device 114 is tuning into the RF chain, if the network is transmitting data, an interruption of other frequency bands that interrupt the data may be generated. During the 6ms delay period, the network can actually only send 4ms of data. In each message gap, the same is true for the rest of the figure. The network transmits data using the idle RF of the UE device 114.

Referring now to fig. 10 and 11, additional standard modifications or data sets for les 1000 and 1100 are shown, enabling, for example, the minigap configuration or measurement gap configuration of IE 900 of fig. 9. For example. Modifications, for example, may be submitted in TS 36.331 to implement measurement gap configuration. The data slot or indication of CA-gap 01002 includes gapRepetitionperiod 1004, gapOffset-r 131006, service band 1008, and Boolean mini-slot 1010. If the small gap is set to true or valid, the network will send data over those idle RFs, if not, it will not transmit data during those data link transmissions, and the UE will perform more measurements to reduce measurement delay.

Fig. 11 provides an alternative example of a completely different IE for the small gap measurement mode, rather than modifying the existing IE in the 3GPP standard TS 36.331.

While the methods described within this disclosure are illustrated and described herein as a series of acts or events, it will be appreciated that the illustrated ordering of such acts or events are not to be interpreted in a limiting sense. For example, some acts may occur in different orders and/or concurrently with other acts or events apart from those illustrated and/or described herein. In addition, not all illustrated acts may be required to implement one or more aspects or embodiments described herein. Further, one or more of the acts described herein may be performed in one or more separate acts and/or phases.

Referring to fig. 12, an exemplary process flow is illustrated for a method 1200 or a computer readable medium comprising executable instructions that in response to execution cause a network device or system comprising one or more processors to perform the operations of the method.

At 1202, the process flow includes identifying, via one or more processors of a network device, a measurement object Identifier (ID) (measObject) and a measurement gap pattern. The measurement gap pattern may be determined, via one or more processors of the network device, for example, as a function of an identifier or identification of an indication of UE capabilities related to Radio Frequency (RF) band capabilities (e.g., a single RF chain or multiple RF chains and respective band coverage for each RF chain). The identification process may be further performed by the control circuit component of the network device to identify the MeasGapConfig IE, the gap offset (which includes information for selecting/selecting a gap repetition period that supports the carrier aggregation measurement gap pattern between different gap repetition periods), the gap repetition period, and a supported band list (which indicates a first set of bands to be measured that is more than a second set of bands).

At 1204, process flow continues with sending or receiving, via one or more processors of the network device, measObject and measurement gap pattern via one or more Radio Resource Control (RRC) signals. Transmitting or receiving, via a transmit circuit component of the network device, a measurement gap configuration (MeasGapConfig) on an Information Element (IE) via one or more Radio Resource Control (RRC) signals based on the indication.

In other embodiments, the process flow may also include identifying, via a control circuit component of the network device, the MeasGapConfig IE, the gap offset, the gap repetition period, the serving band (servingBand), and whether a small gap or a full gap (which is a measurement gap larger than the small gap) based on one or more downlink data.

Based on the indication or report of the UE capabilities, the desired implementation, or the request for resources, the process flow may operate according to path a or B. Path a may continue to reduce interruptions while path B may continue to provide less interruption time and increased data flow. As shown below, alternate path a may further facilitate a balance between reducing latency and demand for data along path C based on the demand of one or more network devices. All alternative paths may also be selected according to the capabilities of the UE (e.g., whether there are one or more RF chains, and corresponding band frequencies that each can cover in operation).

Referring to fig. 13, an exemplary measurement gap pattern process flow 1300 is shown continuing from process flow 1200 of fig. 12 according to process flow a for selecting a measurement gap pattern (e.g., via MeasGapConfig IE 600 or 700 for pattern 500).

At 1302, process flow 1300 continues at selected process flow a with facilitating, via a first radio circuit (e.g., RF chain 1420) component, a first band measurement at a first measurement gap and a second band measurement at a second measurement gap.

At 1304, process flow 1300 continues with facilitating, via the second radio circuit component, a third frequency band measurement at the first measurement gap and a fourth frequency band measurement at the second measurement gap.

The process flow 1300 may end or further enable additional process step C in fig. 14. At 1402, process flow 1400 may also include providing an indication (e.g., MeasGapConfig IE 600 or 700 for mode 800) of: enabling downlink transmission of data on the first radio circuit assembly and the second radio circuit assembly during an additional measurement gap between the first measurement gap and the second measurement gap.

Fig. 15 illustrates a method 1500 for measurement gap patterns including small gaps according to the selection of path a of fig. 12, in accordance with various aspects or embodiments herein. The method 1500 may represent, for example, a measurement gap pattern with small gaps that may be indicated by the MeasGapConfig IE 1000 or 1100 of the pattern 900.

At 1502, method 1500 includes facilitating, via a first radio circuit component (e.g., RF chain 1402), a first band measurement at a first measurement gap, a second band measurement at a second measurement gap, and a downlink transmission of data in a first service band at the second measurement gap and a fourth measurement gap.

At 1504, method 1500 continues with the following operations: downlink transmission of data on the second serving frequency band at the first measurement gap, and third and fourth frequency band measurements at the third and fourth measurement gaps are facilitated via second radio circuit components (e.g., RF chain 2404).

In one embodiment, the downlink transmission of data may include a small gap pattern of break times. One or more gaps may be tolerated during the downlink transmission of data to keep the data flow continuous and band measurements made in a small-gap pattern. For example, each small gap may include a pause in downlink data transmission for a transition to an RF service band or link. In this case, the RF chain 1402 (first radio circuit component) may operate with a pause (no data link and measurement) at the third measurement gap, and the RF chain 2404 (second radio circuit component) may operate with the same pause for DL data transmission and measurement at the second measurement gap. The sequence between the two RF chains can then be cycled.

Fig. 16 illustrates an electronic device 1600 in accordance with various aspects disclosed herein. According to various embodiments, electronic (network) device 1600 may be incorporated into, or otherwise be part of, an eNB (e.g., 102), a UE (e.g., 114), or some other type of electronic or network device. In particular, electronic device 1600 may be logic or circuitry that may be at least partially implemented in one or more of hardware, software, or firmware. In an embodiment, electronic device 1600 logic may include a radio transmit logic component 1602 and a receive logic component 1606 coupled to a control logic component 1604. In an embodiment, the transmit or receive logic component may be an element or module of a transceiver, transmitter, or receiver chain, as shown. The electronic device 1602 may include or be coupled with one or more antenna elements 1608 of one or more antennas. The electronic device and/or components of the electronic device may be configured to perform operations similar to those described elsewhere in this disclosure.

In embodiments where the electronic device circuitry is (or is incorporated into or otherwise part of) a network entity, the control circuitry component 1604 may be configured to identify a measurement object Identifier (ID) (measObject) and a measurement gap pattern. The transmit circuitry component 1602 may be configured to transmit an indication of measObject and measurement gap pattern to a User Equipment (UE) via one or more Radio Resource Control (RRC) signals. Further, receive circuitry component 1606 (e.g., RF chain 1402 and RF chain 2404) may be configured to receive, via one or more Radio Resource Control (RRC) signals, a measurement gap configuration (measgapcfig) on a measgapcfig (ie) information element that controls measurements during multiple measurement gaps using carrier aggregation.

As used herein, the term "logic" may refer to or include an Application Specific Integrated Circuit (ASIC), an electronic circuit, a processor (shared, dedicated, or group) and/or memory (shared, dedicated, or group) that executes one or more software or firmware programs, a combinational logic circuit, and/or other suitable hardware components that provide the described functionality. In particular, logic may be at least partially implemented in or an element of hardware, software, and/or firmware. In some embodiments, the electronic device logic or functionality associated with the logic may be implemented by one or more software or firmware modules.

The embodiments described herein may be implemented using any suitably configured hardware and/or software. Fig. 17 illustrates, for one embodiment, an example system that includes, at least as shown, Radio Frequency (RF) logic 1702, baseband logic 1704, application logic 1706, memory/storage 1708, display 1710, camera 1712, sensor 1714, and input/output (I/O) interface 1716 coupled to one another.

The application logic 1706 may include one or more single-core or multi-core processors. The processor(s) may include any combination of general-purpose processors and special-purpose processors (e.g., graphics processors, application processors, etc.). The processor may be coupled with the memory/storage device and configured to execute instructions stored in the memory/storage device to enable various applications and/or operating systems to run on the system.

Baseband logic 1704 may include one or more single-core or multi-core processors. The processor(s) may include a baseband processor 1718 and/or an additional or alternative processor 1720 that may be designed to implement the functions or actions of control logic, transmit logic, and/or receive logic as described elsewhere herein. Baseband logic 1704 may handle various radio control functions that enable communication with one or more radio networks through RF logic. The radio control functions may include, but are not limited to, signal modulation, encoding, decoding, radio frequency drift, and the like. In some embodiments, the baseband logic may provide communications compatible with one or more radio technologies. For example, in some embodiments, baseband logic 1704 may support communication with an Evolved Universal Terrestrial Radio Access Network (EUTRAN) and/or other Wireless Metropolitan Area Networks (WMANs), Wireless Local Area Networks (WLANs), Wireless Personal Area Networks (WPANs). Embodiments in which baseband logic 1704 is configured to support radio communications of more than one wireless protocol may be referred to as multi-mode baseband logic.

In various embodiments, baseband logic 1704 may include logic to operate with signals that are not strictly considered to be baseband frequencies. For example, in some embodiments, baseband logic 1704 may include logic to operate with signals having an intermediate frequency between the baseband frequency and the radio frequency.

RF logic 1702 may enable communication with wireless networks through non-solid media using modulated electromagnetic radiation. In various embodiments, the RF logic 1702 may include switches, filters, amplifiers, and the like to facilitate communication with a wireless network.

In various embodiments, RF logic 1702 may include logic to operate using signals that are not strictly considered to be at radio frequencies. For example, in some embodiments, the RF logic may include logic to operate with signals at intermediate frequencies between baseband and radio frequencies.

In various embodiments, the transmit logic, control logic, and/or receive logic discussed or described herein may be embodied in whole or in part in one or more of the RF logic 1702, baseband logic 1704, and/or application logic 1706. As used herein, the term "logic" may refer to, be part of, or include the following: an Application Specific Integrated Circuit (ASIC), an electronic circuit (shared, dedicated, or group) that executes one or more software or firmware programs, a processor and/or memory (shared, dedicated, or group), a combinational logic circuit, and/or other suitable hardware components that provide the described functionality. In particular, logic may be at least partially implemented in or an element of hardware, software, and/or firmware. In some embodiments, the electronic device logic may be implemented in or functions associated with the logic may be implemented by one or more software or firmware modules.

In some embodiments, some or all of the components of the baseband logic, application logic, and/or memory/storage devices may be implemented together on a system on a chip (SOC).

Memory/storage 1708 may be used to load and store data and/or instructions, for example, for a system. Memory/storage 1708 for one embodiment may comprise any combination of suitable volatile memory (e.g., Dynamic Random Access Memory (DRAM)) and/or nonvolatile memory (e.g., flash memory).

In various embodiments, the I/O interfaces 1716 may include one or more user interfaces designed to enable a user to interact with the system and/or peripheral component interfaces designed to enable peripheral components to interact with the system. The user interface may include, but is not limited to, a physical keyboard or keypad, a touchpad, a speaker, a microphone, and the like. The peripheral component interfaces may include, but are not limited to, a non-volatile memory port, a Universal Serial Bus (USB) port, an audio jack, and a power interface.

In various embodiments, the sensors 1714 may include one or more sensing devices that determine environmental conditions and/or location information related to the system. In some embodiments, the sensors may include, but are not limited to, a gyroscopic sensor, an accelerometer, a proximity sensor, an ambient light sensor, and a positioning unit. The positioning unit may also be part of or interact with baseband logic and/or RF logic to communicate with components of a positioning network, such as Global Positioning System (GPS) satellites.

In various embodiments, the display 1710 may include a display screen (e.g., a liquid crystal display, a touch screen display, etc.).

In various embodiments, the system may be a mobile computing device, such as, but not limited to, a laptop computing device, a tablet computing device, a netbook, an ultrabook, a smartphone, and the like. In various embodiments, the system may have more or fewer components and/or different architectures.

In various embodiments, the system may be a mobile computing device, such as, but not limited to, a laptop computing device, a tablet computing device, a netbook, an ultrabook, a smartphone, and the like. In various embodiments, the system may have more or fewer components and/or different architectures. For example, in some embodiments, the RF logic and/or baseband logic may be embodied in communication logic (not shown). The communication logic may include one or more single-core or multi-core processors and logic circuits that provide signal processing techniques (e.g., encoding, modulation, filtering, conversion, amplification, etc.) suitable for the appropriate communication interface through which communication is to occur. The communication logic may communicate over a wired, optical, or wireless communication medium. In embodiments where the system is configured for wireless communication, the communication logic may include RF logic and/or baseband logic to provide communication compatible with one or more radio technologies. For example, in some embodiments, the communication logic may support communication with an Evolved Universal Terrestrial Radio Access Network (EUTRAN) and/or other Wireless Metropolitan Area Networks (WMANs), Wireless Local Area Networks (WLANs), Wireless Personal Area Networks (WPANs).

Embodiments of the present technology may be described as relating to third generation partnership project (3GPP) Long Term Evolution (LTE) or LTE-advanced (LTE-a) standards. For example, terms or entities such as enodeb (enb), Mobility Management Entity (MME), User Equipment (UE), which may be considered LTE related terms or entities, may be used. In other embodiments, however, the techniques may be used in or in connection with other wireless technologies, such as Institute of Electrical and Electronics Engineers (IEEE)802.16 wireless technology (WiMax), IEEE 802.11 wireless technology (WiFi), various other wireless technologies (e.g., global system for mobile communications (GSM), enhanced data rates for GSM evolution (EDGE), GSM EDGE Radio Access Network (GERAN), Universal Mobile Telecommunications System (UMTS), UMTS Terrestrial Radio Access Network (UTRAN), or other 2G, 3G, 4G, 5G, etc. developed or yet to be developed technologies). In those embodiments that use LTE-related terms such as eNB, MME, UE, etc., one or more entities or components that may be considered equivalent or substantially equivalent to one or more terms or entities based on LTE may be used.

As used in this specification, the term "processor" may refer to virtually any computing processing unit or device, including, but not limited to, a single-core processor; a single processor with software multi-threaded execution capability; a multi-core processor; a multi-core processor having software multi-thread execution capability; a multi-core processor having hardware multithreading; a parallel platform; and parallel platforms with distributed shared memory. Further, a processor may refer to an integrated circuit, an application specific integrated circuit, a digital signal processor, a field programmable gate array, a programmable logic controller, a complex programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions and/or processes described herein. Processors can utilize nanoscale architectures (such as, but not limited to, molecular and quantum dot based transistors, switches, and gates) to optimize space usage or enhance performance of mobile devices. A processor may also be implemented as a combination of computing processing units.

In the subject specification, terms such as "storage," "data store," "database," and substantially any other information storage component related to the operation and functionality of components and/or processes refer to "memory components," or entities embodied in "memory," or components including memory. Note that the memory components described herein can be either volatile memory or nonvolatile memory, or can include both volatile and nonvolatile memory.

By way of illustration, and not limitation, nonvolatile memory can be included in the memory, nonvolatile memory, disk storage, and storage devices, for example. Further, the non-volatile memory may be included in a read only memory, a programmable read only memory, an electrically erasable programmable read only memory, or a flash memory. Volatile memory may include random access memory that acts as external cache memory. By way of illustration and not limitation, RAM can take many forms, such as SDRAM, DRAM, SDRAM, DDR SDRAM, eSDRAM, SDRAM, and direct Rambus RAM. Moreover, the disclosed memory components of systems or methods herein are intended to comprise, without being limited to, comprising these and any other suitable types of memory.

Examples may include the subject matter of a concurrent communication system using multiple communication technologies, e.g., a method, an apparatus for performing the acts or blocks of a method, at least one machine readable medium including instructions which, when executed by a machine, cause the machine to perform the acts of the method or apparatus, in accordance with the embodiments and examples described herein.

Example 1 is an apparatus for a User Equipment (UE), comprising: a receive circuitry component configured to receive, via one or more Radio Resource Control (RRC) signals, a measgapcfig on a measurement gap configuration (measgappconfig) Information Element (IE) that controls measurements during a plurality of measurement gaps using carrier aggregation; and a control circuit component communicatively coupled to the receive circuit component configured to identify an increased number of measurement object Identifiers (IDs) (measObject) that identify a first plurality of frequency carriers to be measured more than a second plurality of frequency carriers of the plurality of frequency carriers, and a measurement gap pattern associated with the MeasGapConfig.

Example 2 includes the subject matter of example 1, wherein the measObject is configured to support more than 32 carrier components to support 3GPP release 13 or higher.

Example 3 includes the subject matter of any of examples 1-2, including or omitting optional elements, wherein the control circuitry component is further configured to select a gap repetition period from a plurality of gap repetition periods from the MeasGapConfig IE, a gap offset based on the selected gap repetition period, and a list of supported frequency bands indicating one or more frequency bands to be measured with the gap repetition period.

Example 4 includes the subject matter of any of examples 1-3, including or omitting optional elements, wherein the control circuitry component is further configured to: determining a different gap offset from the MeasGapConfig IE by selecting a different gap repetition period, the different gap offset being implemented based on the gap repetition period, identifying whether a small gap indicator and a serving band are being used in response to the MeasGapConfig being configured for downlink data transmission during the measurement gap pattern. .

Example 5 includes the subject matter of any of examples 1-4, including or omitting the optional element, wherein the small gap indicator is true or valid to enable downlink data transmission during the measurement gap pattern with the interruption.

Example 6 includes the subject matter of any of examples 1-5, including or omitting optional elements, wherein the control circuitry component is further configured to: performing measurements of the first plurality of frequency carriers based on a determination of whether the measurements use full gaps or small gaps comprising segments of full gaps, and wherein, in response to the determination comprising measuring the first plurality of frequency carriers with full gaps, the control circuitry component is configured to perform measurements without data transmission, and in response to the determination comprising measuring the first plurality of frequency carriers with small gaps, the receive circuitry component is configured to receive downlink transmissions within measurement gaps of the plurality of measurement gaps.

Example 7 includes the subject matter of any of examples 1-6, including or omitting optional elements, wherein the control circuitry component is further configured to: the MeasGapConfig is selected based on a decrease in measurement gap delay, an increase in downlink data efficiency, or a simultaneous decrease in measurement gap delay and increase in downlink data efficiency.

Example 8 includes the subject matter of any of examples 1-7, including or omitting optional elements, wherein the receive circuitry component is further configured to: generating a measurement on a first frequency band at a first measurement gap and a measurement on a second frequency band at a second measurement gap of the plurality of measurement gaps, and operating on a first serving frequency band for downlink data transmission at other periods outside the plurality of measurement gaps; further comprising: another receive circuit component configured to operate on a third frequency band at the first measurement gap and a fourth frequency band at the second measurement gap to facilitate measurement of the third and fourth frequency bands, and to operate on a second serving frequency band for downlink data transmission during other periods outside of the plurality of measurement gaps; wherein the first service frequency band, the second service frequency band, the first frequency band, the second frequency band, the third frequency band, and the fourth frequency band are different from each other.

Example 9 includes the subject matter of any of examples 1-8, including or omitting optional elements, wherein the receive circuitry component and the further receive circuitry component are further configured to receive downlink data in a different measurement gap existing between the first measurement gap and the second measurement gap.

Example 10 includes the subject matter of any of examples 1-9, including or omitting optional elements, wherein the receive circuitry component is further configured to: the first frequency band is measured at a first measurement gap and the second frequency band is measured at a second measurement gap while downlink data transmission is conducted on the first service band based on a small gap pattern as a measurement gap pattern at the second measurement gap.

Example 11 includes the subject matter of any one of examples 1-10, including or omitting optional elements, further comprising: another receive circuit component configured to perform downlink data transmission at a first measurement gap on a second serving frequency band different from the first serving frequency band based on the small gap pattern, measure a third frequency band at a third measurement gap while performing downlink data transmission on the second serving frequency band, and measure a fourth frequency band at a fourth measurement gap.

Example 12 includes the subject matter of any of examples 1-11, including or omitting optional elements, wherein the receive circuitry component is further configured to conduct a downlink transmission of data at the fourth measurement gap.

Example 13 includes an apparatus of an evolved node b (enb), comprising: a control circuit component configured to identify a measurement object Identifier (ID) (measObject) and a measurement gap pattern to facilitate carrier aggregation based measurement gap measurements; and transmit circuitry communicatively coupled to the control circuitry and configured to transmit the measObject and the measurement gap pattern via one or more Radio Resource Control (RRC) signals.

Example 14 includes the subject matter of example 13, wherein the control circuitry component is further configured to identify an indication of UE capabilities related to Radio Frequency (RF) band capabilities, and wherein the transmit circuitry component is further to transmit, based on the indication, a MeasGapConfig on a measurement gap configuration (MeasGapConfig) Information Element (IE) via one or more Radio Resource Control (RRC) signals.

Example 15 includes the subject matter of any of examples 13-14, including or omitting optional elements, wherein the control circuitry component is further configured to identify a gap offset with the MeasGapConfig IE by selecting a gap repetition period, identify an active small gap indicator in response to the MeasGapConfig being configured for downlink data transmission based on a transmission gap pattern, and identify at least one serving band that specifies a UE serving band.

Example 16 includes the subject matter of any of examples 13-15, including or omitting optional elements, wherein the control circuitry component is further configured to identify a gap offset comprising information for selecting a different gap repetition period, a gap repetition period, and a list of supported frequency bands indicating a first set of frequency bands to be measured more with the gap repetition period than a second set of frequency bands.

Example 17 includes the subject matter of any of examples 13-16, including or omitting optional elements, wherein the control circuitry component is further configured to indicate whether measurements of the first set of frequency bands utilize a full gap or a small gap based on a decrease in measurement gap delay, an increase in downlink data efficiency, or a simultaneous decrease in measurement gap delay and increase in downlink data efficiency, wherein there is no data transmission by the transmit circuitry component associated with a measurement gap pattern in response to the control circuitry component indicating that a full gap is true, wherein a small gap comprises a fraction of a full gap.

Example 18 includes the subject matter of any one of examples 13-17, including or omitting optional elements, wherein the carrier aggregation measurement gap configuration specifies a measurement gap pattern comprising: a first indication corresponding to a first radio circuit component indicating that a first frequency band is measured at a first measurement gap and a second frequency band is measured at a second measurement gap and operating on a first serving frequency band for downlink data transmission; and a second indication, corresponding to a second radio circuit component, indicating that the third frequency band is measured at the first measurement gap or the third measurement gap and the fourth frequency band is measured at the second measurement gap or the fourth measurement gap, and operating on the second serving frequency band for downlink data transmission.

Example 19 includes the subject matter of any of examples 13-18, including or omitting the optional element, wherein the first indication and the second indication provide that downlink data is present during an additional measurement gap between the first measurement gap and the second measurement gap, or alternatively that downlink data is present between the first receive circuitry component and the second receive circuitry component in between the first measurement gap and the second measurement gap.

Example 20 is a computer-readable medium comprising executable instructions that, in response to execution, cause a system comprising one or more processors to perform operations comprising: identifying, via one or more processors of a network device, a measurement object Identifier (ID) (measObject) and a measurement gap pattern; and transmitting or receiving the measObject and the measurement gap pattern via one or more Radio Resource Control (RRC) signals via the one or more processors of the network device.

Example 21 includes the subject matter of example 20, wherein the operations further comprise: identifying, via the one or more processors of the network device, an indication of UE capabilities related to Radio Frequency (RF) band capabilities; and measuring, by a transmit circuit component of the network device, a MeasGapConfig on a gap configuration (MeasGapConfig) Information Element (IE) via one or more Radio Resource Control (RRC) signals based on the indication.

Example 22 includes the subject matter of any one of examples 20-21, including or omitting the optional element, wherein the operations further comprise: identifying, by a control circuit component of the network device, at least one of the following with a measgapcfonfig IE: a gap offset comprising information for selection of different gap repetition periods supporting a carrier aggregation measurement gap pattern, a gap repetition period, and a list of supported frequency bands indicating a first set of frequency bands to be measured more than a second set of frequency bands, a serving frequency band, or an indication whether a small gap or a full gap, which is a measurement gap larger than the small gap, is to be utilized for downlink data.

Example 23 includes the subject matter of any one of examples 20-22, including or omitting the optional element, wherein the operations further comprise: facilitating, on the first radio circuit assembly, a first band measurement at the first measurement gap and a second band measurement at the second measurement gap; and facilitating, on a second radio circuit component, a third frequency band measurement at the first measurement gap and a fourth frequency band measurement at the second measurement gap.

Example 24 includes the subject matter of any one of examples 20-23, including or omitting the optional element, wherein the operations further comprise: providing one or more indications specifying downlink transmission of data on the first and second radio circuit components during an additional measurement gap between the first and second measurement gaps.

Example 25 includes the subject matter of any one of examples 20-24, including or omitting the optional element, wherein the operations further comprise: facilitating, by the first radio circuitry component, a first band measurement of the first measurement gap and a second band measurement at the second measurement gap, and downlink transmission of data by the first serving frequency band at the second measurement gap and a fourth measurement gap; facilitating, by the second radio circuit component, downlink transmission of data on the second serving frequency band at the first measurement gap, a third frequency band measurement at the third measurement gap and a fourth frequency band measurement at the fourth measurement gap; wherein the downlink transmission of the data comprises a small-gap pattern of break times.

Example 26 is a system, comprising: means for identifying a measurement object Identifier (ID) (measObject) and a measurement gap pattern; and means for transmitting or receiving the measObject and the measurement gap pattern via one or more Radio Resource Control (RRC) signals. .

Example 27 includes the subject matter of example 26, further comprising: means for determining an indication of UE capabilities related to Radio Frequency (RF) band capabilities; and means for transmitting, based on the indication, a MeasGapConfig on a measurement gap configuration (MeasGapConfig) Information Element (IE) via one or more Radio Resource Control (RRC) signals.

Example 28 includes the subject matter of any one of examples 26-27, including or omitting optional elements, further comprising: means for defining with the MeasGapConfig IE at least one of: a gap offset comprising information for selection of different gap repetition periods supporting a carrier aggregation measurement gap pattern, a gap repetition period, and a list of supported frequency bands indicating a first set of frequency bands to be measured more than a second set of frequency bands, a serving frequency band, or an indication whether a small gap or a full gap, which is a measurement gap larger than the small gap, is to be utilized for downlink data. .

Example 29 includes the subject matter of any one of examples 26-28, including or omitting the optional element, further comprising: means for generating, on the first radio circuit assembly, a first band measurement at the first measurement gap and a second band measurement at the second measurement gap; and means for generating a third frequency band measurement at the first measurement gap and a fourth frequency band measurement at the second measurement gap on a second radio circuit component.

Example 30 includes the subject matter of any one of examples 26-29, including or omitting optional elements, further comprising: means for providing one or more indications specifying downlink transmission of data on the first and second radio circuit components during an additional measurement gap between the first and second measurement gaps.

Example 31 includes the subject matter of any one of examples 26-30, including or omitting the optional element, further comprising: means for generating, by a first radio circuitry component, a first band measurement of a first measurement gap and a second band measurement at a second measurement gap, and a first serving band for downlink data transmission at the second measurement gap and a fourth measurement gap; and means for generating, by a second radio circuit component, a downlink transmission of data on a second service frequency band at the first measurement gap, a third frequency band measurement at a third measurement gap and a fourth frequency band measurement at a fourth measurement gap; wherein the downlink transmission of the data comprises a small-gap pattern with a break time.

It should be understood that the aspects described herein may be implemented in hardware, software, firmware, or any combination thereof. When implemented in software, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium. Computer-readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A storage media or computer-readable storage device can be any available media that can be accessed by a general purpose or special purpose computer. By way of example, and not limitation, such computer-readable media can comprise RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or other tangible and/or non-transitory media that can be used to carry or store desired information or executable instructions. Also, any connection is properly termed a computer-readable medium. For example, if the software is transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, Digital Subscriber Line (DSL), or wireless technologies such as infrared, radio, and microwave, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of medium. Disk and disc, as used herein, includes Compact Disc (CD), laser disc, optical disc, Digital Versatile Disc (DVD), floppy disk and blu-ray disc where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above should also be included within the scope of computer-readable media.

The various illustrative logics, logical blocks, modules, and circuits described in connection with the aspects disclosed herein may be a general purpose processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a field programmable gate array (PFGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general-purpose processor may be a microprocessor, or alternatively, the processor may be any conventional processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration. Further, at least one processor may comprise one or more modules operable to perform one or more of the steps and/or actions described herein.

For a software implementation, the techniques described herein may be implemented with modules (e.g., procedures, functions, and so on) that perform the functions described herein. The software codes may be stored in memory units and executed by processors. The memory unit may be implemented within the processor or external to the processor, in which case it can be communicatively coupled to the processor via various means as is known in the art. Further, at least one processor may comprise one or more modules operable to perform the functions described herein.

The techniques described herein may be used for various wireless communication systems such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, etc. systems. The terms "system" and "network" are generally used interchangeably. A CDMA system may implement radio technologies such as Universal Terrestrial Radio Access (UTRA), CDMA1800, etc. UTRA includes wideband CDMA (W-CDMA) and other variants of CDMA. In addition, CDMA1800 covers IS-1800, IS-95 and IS-856 standards. TDMA systems may implement radio technology communications (GSM) such as Global System for Mobile (GSM). The OFDMA system can implement evolved UTRA (E-UTRA), Ultra Mobile Broadband (UMB), IEEE 802.11(Wi-Fi), IEEE802.16(WiMAX), IEEE802.18, Flash-OFDML, and other radio technologies. UTRA and E-UTRA are part of the Universal Mobile Telecommunications System (UMTS). 3GPP Long Term Evolution (LTE) is a release of UMTS that uses E-UTRA, which employs OFDMA on the downlink and SC-FDMA on the uplink. UTRA, E-UTRA, UMTS, LTE, and GSM are described in documents from an organization named "third Generation partnership project" (3 GPP). Further, CDMA1800 and UMB are described in documents from an organization named "third generation partnership project 2" (3GPP 2). Further, such wireless communication systems may also include peer-to-peer (e.g., mobile-to-mobile) ad hoc network systems that often use unpaired unlicensed spectrum, 802.11 wireless LANs, bluetooth, and any other short-range or long-range wireless communication technologies.

Single carrier frequency division multiple access (SC-FDMA) with single carrier modulation and frequency domain equalization is a technique that can be used with the disclosed aspects. SC-FDMA has similar performance and substantially similar overall complexity as OFDMA systems. SC-FDMA signal has a low peak-to-average power ratio (PAPR) due to its inherent single carrier structure. SC-FDMA may be used for uplink communications where lower PAPR in transmission power efficiency may benefit mobile terminals.

Furthermore, various aspects or features described herein may be implemented as a method, apparatus, or article of manufacture using standard programming and/or engineering techniques. The term "article of manufacture" as used herein is intended to encompass a computer program accessible from any computer-readable device, carrier, or media. For example, computer-readable media can include but are not limited to magnetic storage devices (e.g., hard disk, floppy disk, magnetic strips, etc.), optical disks (e.g., Compact Disk (CD), Digital Versatile Disk (DVD), etc.), smart cards, and flash memory devices (e.g., EPROM, card, stick, key drive, etc.). In addition, various storage media described herein can represent one or more devices and/or other machine-readable media for storing information. The term "machine-readable medium" can include, without being limited to, wireless channels and various other media capable of storing, containing, and/or carrying instruction(s) and/or data. Further, a computer program product may include a computer-readable medium having one or more instructions or codes operable to cause a computer to perform the functions described herein.

Communication media embodies computer readable instructions, data structures, program modules or other structured or unstructured data in a data signal such as a modulated data signal (e.g., carrier wave or other transport mechanism) and includes any information delivery or transmission media. The term "modulated data signal" or signal refers to a signal that has one or more of its characteristics set or changed in such a manner as to encode information in the signal. By way of example, and not limitation, communication media includes wired media such as a wired network or direct-wired connection, and wireless media such as acoustic, RF, infrared and other wireless media.

Further, the actions of a method or algorithm described in connection with the aspects disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. A software module may reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. An exemplary storage medium can be coupled to the processor such the processor can read information from, and write information to, the storage medium. In the alternative, the storage medium may be part of the processor. Further, in some aspects, the processor and the storage medium may reside in an ASIC. Further, the ASIC may reside in a user terminal. In the alternative, the processor and the storage medium may reside as discrete components in a user terminal. Additionally, in certain aspects, the methods or algorithms and/or actions may reside as one or any combination or set of codes and/or instructions on a machine readable medium and/or computer readable medium, which may be incorporated into a computer program product.

The above description of illustrated embodiments of the invention, including what is described in the abstract, is not intended to be exhaustive or to limit the disclosed embodiments to the precise forms disclosed. Although specific embodiments of, and examples for, the invention are described herein for illustrative purposes, various modifications are possible within the scope of the embodiments and examples, as those skilled in the relevant art will recognize. In this regard, while the disclosed subject matter has been described in connection with various embodiments and corresponding figures, it is to be understood that other similar embodiments may be used or modifications and additions may be made to the described embodiment for performing the same, similar, alternative or alternative functions of the disclosed subject matter without deviating therefrom, where applicable. Accordingly, the disclosed subject matter should not be limited to any single embodiment described herein, but rather should be construed broadly in accordance with the appended claims.

In particular regard to the various functions performed by the above described components (assemblies, devices, circuits, systems, etc.), the terms (including a reference to a "means") used to describe such components are intended to correspond, unless otherwise indicated, to any component or structure which performs the specified function of the described component (e.g., that is functionally equivalent), even though not structurally equivalent to the disclosed structure which performs the function in the herein illustrated exemplary implementations of the invention. In addition, while a particular feature may have been disclosed with respect to only one of several implementations, such feature may be combined with one or more other features of the other implementations as may be desired and advantageous for any given or particular application.

Claims (31)

1. An apparatus for a User Equipment (UE), comprising:

a receive circuitry component configured to receive, via one or more radio resource control, RRC, signals, measgapcfig on a measurement gap configuration measgapcfig information element IE that controls measurements during a plurality of measurement gaps using carrier aggregation; and

a control circuit component communicatively coupled to the receive circuit component and configured to identify an increased number of measurement object measObject identifiers ID and measurement gap patterns associated with the measGapConfig, the increased number of measurement object identifiers identifying a first plurality of frequency carriers to be measured more than a second plurality of frequency carriers of a plurality of frequency carriers.

2. The apparatus of claim 1, wherein the measObject is configured to support more than 32 carrier components to support 3GPP release 13 or higher.

3. The apparatus of claim 1, wherein the control circuitry component is further configured to: selecting, from the MeasGapConfig IE, a gap repetition period from a plurality of gap repetition periods, a gap offset based on the selected gap repetition period, and a supported band list indicating one or more bands to be measured with the gap repetition period.

4. The apparatus of claim 3, wherein the control circuitry component is further configured to: determining a different gap offset from the MeasGapConfig IE by selecting a different gap repetition period, the different gap offset being implemented based on the gap repetition period, identifying whether a small gap indicator and a serving band are being used in response to the MeasGapConfig being configured for downlink data transmission during the measurement gap pattern.

5. The apparatus of claim 4, wherein the small-gap indicator is true or valid to enable downlink data transmission during a measurement gap pattern with interruption.

6. The apparatus of claim 1, wherein the control circuitry component is further configured to: performing measurements of the first plurality of frequency carriers based on a determination of whether the measurements use full gaps or small gaps comprising segments of full gaps, and wherein, in response to the determination comprising measuring the first plurality of frequency carriers with full gaps, the control circuitry component is configured to perform measurements without data transmission, and in response to the determination comprising measuring the first plurality of frequency carriers with small gaps, the receive circuitry component is configured to receive downlink transmissions within measurement gaps of the plurality of measurement gaps.

7. The apparatus of claim 1, wherein the control circuitry component is further configured to: the MeasGapConfig is selected based on a decrease in measurement gap delay, an increase in downlink data efficiency, or a simultaneous decrease in measurement gap delay and increase in downlink data efficiency.

8. The apparatus of claim 1, wherein the receive circuit component is further configured to: generating a measurement on a first frequency band at a first measurement gap and a measurement on a second frequency band at a second measurement gap of the plurality of measurement gaps, and operating on a first serving frequency band for downlink data transmission at other periods outside the plurality of measurement gaps;

further comprising:

another receive circuit component configured to operate on a third frequency band at the first measurement gap and a fourth frequency band at the second measurement gap to facilitate measurement of the third and fourth frequency bands, and to operate on a second serving frequency band for downlink data transmission during other periods outside of the plurality of measurement gaps;

wherein the first service frequency band, the second service frequency band, the first frequency band, the second frequency band, the third frequency band, and the fourth frequency band are different from each other.

9. The apparatus of claim 8, wherein the receive circuit component and the other receive circuit component are further configured to receive downlink data in a different measurement gap existing between the first measurement gap and the second measurement gap.

10. The apparatus of any one of claims 1-9, wherein the receive circuit component is further configured to: the first frequency band is measured at a first measurement gap and the second frequency band is measured at a second measurement gap while downlink data transmission is conducted on the first service band based on a small gap pattern as a measurement gap pattern at the second measurement gap.

11. The apparatus of claim 10, further comprising:

another receive circuit component configured to perform downlink data transmission at a first measurement gap on a second serving frequency band different from the first serving frequency band based on the small gap pattern, measure a third frequency band at a third measurement gap while performing downlink data transmission on the second serving frequency band, and measure a fourth frequency band at a fourth measurement gap.

12. The apparatus of claim 11, wherein the receive circuit component is further configured to: performing downlink data transmission at the fourth measurement gap.

13. An apparatus of a base station, BS, comprising:

a control circuit component configured to identify an increased number of measurement object measObject identifier IDs and measurement gap patterns to facilitate carrier aggregation based measurement gap measurements, the increased number of measurement object identifiers identifying a first plurality of frequency carriers to be measured more than a second plurality of frequency carriers of the plurality of frequency carriers; and

a transmit circuit component communicatively coupled to the control circuit component and configured to transmit the measObject and the measurement gap pattern via one or more Radio Resource Control (RRC) signals.

14. The apparatus of claim 13, wherein the control circuitry component is further configured to: an indication of UE capabilities related to radio frequency, RF, band capabilities is identified, and wherein the transmit circuitry component further transmits, based on the indication, the MeasGapConfig on the MeasGapConfig information element IE via one or more radio resource control, RRC, signals.

15. The apparatus of claim 14, wherein the control circuitry component is further configured to: identifying a gap offset with the MeasGapConfig IE by selecting a gap repetition period, identifying an active small gap indicator in response to the MeasGapConfig being configured for downlink data transmission based on a transmission gap pattern, and identifying at least one serving band that specifies a UE serving band.

16. The apparatus of any of claims 13-15, wherein the control circuitry component is further configured to identify a gap offset comprising information for selecting a different gap repetition period, a gap repetition period, and a supported band list indicating a first set of frequency bands to be measured more with the gap repetition period than a second set of frequency bands.

17. The apparatus of claim 16, wherein the control circuitry component is further configured to: indicating whether measurements of the first set of frequency bands utilize a full gap or a small gap based on a decrease in measurement gap delay, an increase in downlink data efficiency, or a simultaneous decrease in measurement gap delay and increase in downlink data efficiency, wherein there is no data transmission associated with a measurement gap pattern by the transmit circuit component in response to the control circuit component indicating that a full gap is true, wherein the small gap comprises a fraction of the full gap.

18. The apparatus of claim 17, wherein a carrier aggregation measurement gap configuration specifies a measurement gap pattern comprising:

a first indication corresponding to a first radio circuit component indicating that a first frequency band is measured at a first measurement gap and a second frequency band is measured at a second measurement gap and operating on a first serving frequency band for downlink data transmission; and

a second indication, corresponding to a second radio circuit component, indicating that the third frequency band is measured at the first measurement gap or the third measurement gap and the fourth frequency band is measured at the second measurement gap or the fourth measurement gap, and operating on the second serving frequency band for downlink data transmission.

19. The apparatus of claim 18, wherein the first and second indications provide that downlink data is present during an additional measurement gap between the first and second measurement gaps, or alternatively that downlink data is present between the first and second radio circuit components in the first and second measurement gaps.

20. A computer-readable medium comprising executable instructions that, in response to execution, cause an apparatus comprising one or more processors to perform operations comprising:

identifying, via one or more processors of a network device, an increased number of measurement object measObject identifier IDs and measurement gap patterns, the increased number of measurement object identifiers identifying a first plurality of frequency carriers to be measured more than a second plurality of frequency carriers of a plurality of frequency carriers; and

transmitting or receiving the measObject and the measurement gap pattern via one or more Radio Resource Control (RRC) signals via the one or more processors of the network device.

21. The computer-readable medium of claim 20, wherein the operations further comprise:

identifying, via the one or more processors of the network device, an indication of UE capabilities related to Radio Frequency (RF) band capabilities; and is

Transmitting, by a transmit circuit component of the network device, a MeasGapConfig on a measgappconfig information element IE via one or more radio resource control, RRC, signals based on the indication.

22. The computer-readable medium of claim 20, wherein the operations further comprise:

identifying, by a control circuit component of the network device, at least one of the following with a measgapcfonfig IE: a gap offset comprising information for selection of different gap repetition periods supporting a carrier aggregation measurement gap pattern, a gap repetition period, and a list of supported frequency bands indicating a first set of frequency bands to be measured more than a second set of frequency bands, a serving frequency band, or an indication whether a small gap or a full gap, which is a measurement gap larger than the small gap, is to be utilized for downlink data.

23. The computer-readable medium of claim 20, wherein the operations further comprise:

facilitating, on the first radio circuit assembly, a first band measurement at the first measurement gap and a second band measurement at the second measurement gap; and

facilitating, on a second radio circuit component, a third frequency band measurement at the first measurement gap and a fourth frequency band measurement at the second measurement gap.

24. The computer-readable medium of claim 23, wherein the operations further comprise:

providing one or more indications specifying downlink transmission of data on the first and second radio circuit components during an additional measurement gap between the first and second measurement gaps.

25. The computer-readable medium of any one of claims 20-24, wherein the operations further comprise:

facilitating, by a first radio circuitry component, a first band measurement of a first measurement gap and a second band measurement at a second measurement gap, and a downlink data transmission of a first service band at the second measurement gap and a fourth measurement gap; and is

Facilitating, by a second radio circuit component, downlink transmission of data on a second service frequency band at the first measurement gap, a third frequency band measurement at a third measurement gap and a fourth frequency band measurement at a fourth measurement gap;

wherein the downlink transmission of the data comprises a small-gap pattern of break times.

26. A system for communication, comprising:

means for identifying an increased number of measurement object measObject identifiers ID and measurement gap patterns, the increased number of measurement object identifiers identifying a first plurality of frequency carriers to be measured more than a second plurality of frequency carriers of the plurality of frequency carriers; and

means for transmitting or receiving the measObject and the measurement gap pattern via one or more Radio Resource Control (RRC) signals.

27. The system of claim 26, further comprising:

means for determining an indication of UE capabilities related to radio frequency, RF, band capabilities; and

means for sending the MeasGapConfig on the measgappconfig information element IE via one or more radio resource control, RRC, signals based on the indication.

28. The system of claim 27, further comprising:

means for defining with the MeasGapConfig IE at least one of: a gap offset comprising information for selection of different gap repetition periods supporting a carrier aggregation measurement gap pattern, a gap repetition period, and a list of supported frequency bands indicating a first set of frequency bands to be measured more than a second set of frequency bands, a serving frequency band, or an indication whether a small gap or a full gap, which is a measurement gap larger than the small gap, is to be utilized for downlink data.

29. The system of claim 26, further comprising:

means for generating, on the first radio circuit assembly, a first band measurement at the first measurement gap and a second band measurement at the second measurement gap; and

means for generating a third frequency band measurement at the first measurement gap and a fourth frequency band measurement at the second measurement gap on a second radio circuit component.

30. The system of claim 29, further comprising:

means for providing one or more indications specifying downlink transmission of data on the first and second radio circuit components during an additional measurement gap between the first and second measurement gaps.

31. The system of any one of claims 26-30, further comprising:

means for generating, by a first radio circuitry component, a first band measurement of a first measurement gap and a second band measurement at a second measurement gap, and a first serving band for downlink data transmission at the second measurement gap and a fourth measurement gap; and

means for generating, by a second radio circuit component, a downlink transmission of data on a second service frequency band at the first measurement gap, a third frequency band measurement at a third measurement gap and a fourth frequency band measurement at a fourth measurement gap;

wherein the downlink transmission of the data comprises a small-gap pattern with a break time.

Images