REFERENCE TO RELATED APPLICATIONS

[0001] This application claims the benefit of U.S. Provisional Application No.

62/294,862 filed February 12, 2016, entitled "SIGNALING FOR ENHANCED

MEASUREMENT GAP FOR SYNCHRONOUS NETWORK", the contents of which are herein incorporated by reference in their entirety.

FIELD

[0002] The present disclosure relates to enhanced measurement gaps, and more specifically, signaling an enhanced measurement gap for a synchronous network.

BACKGROUND

[0003] Wireless mobile communication technology uses various standards and protocols to transmit data between an access node (e.g., a transmission station) and a wireless device (e.g., a mobile device) or a user equipment (UE). Some wireless devices communicate using orthogonal frequency-division multiple access (OFDMA) in a downlink (DL) transmission and single carrier frequency division multiple access (SC- FDMA) in an uplink (UL) transmission. Standards and protocols that use orthogonal frequency-division multiplexing (OFDM) for signal transmission include the third generation partnership project (3GPP) long term evolution (LTE), the Institute of Electrical and Electronics Engineers (IEEE) 802.16 standard (e.g., 802.16e, 802.16m), which is commonly known to industry groups as WiMAX (Worldwide interoperability for Microwave Access), and the IEEE 802.1 1 standard, which is commonly known to industry groups as WiFi.

[0004] In 3GPP radio access network (RAN) LTE systems, the access node can be an Evolved Universal Terrestrial Radio Access Network (E-UTRAN) Node Bs (also commonly denoted as evolved Node Bs, enhanced Node Bs, eNodeBs, or eNBs) with or without one or more Radio Network Controllers (RNCs), which can communicate with the UE. The downlink (DL) transmission can be a communication from an access point / node or base station (e.g., a macro cell device, an eNodeB, an eNB, or other similar network device) to the UE, and the uplink (UL) transmission can be a communication from the wireless device to the node. In LTE, data can be transmitted from the eNB to the UE via a physical downlink shared channel (PDSCH). A physical uplink control channel (PUCCH) can be used to acknowledge that data was received. Downlink and uplink channels can also use time-division duplexing (TDD) or frequency-division duplexing (FDD) for network communication.

[0005] In LTE network communications, two DL synchronization signals are often used by the UE to obtain the cell identity and frame timing in order to then link to the network cell, namely the primary synchronization signal (PSS) and the secondary synchronization signal (SSS). The PSS is linked to the cell identity within a physical cell identity group. The SSS is linked to the cell identity group and the cell identity within the group. The PSS is mapped into the first 31 subcarriers either side of the direct current (DC) subcarrier, and thus, uses six resource blocks with normally five reserved subcarriers on each side of the DC subcarrier. The second SSS sequence used in each radio frame is scrambled with a binary scrambling code corresponding to the cyclic shift value of the first sequence transmitted in the radio frame. The SSS is transmitted in the same subframe as the PSS but one OFDM symbol earlier. The SSS is mapped to the same subcarriers (middle 72 subcarriers) as the PSS.

[0006] The PSS and SSS synchronization signals are utilized by the UE in synchronously connecting with the cell network of an eNB, or even for the UE to maintain its already gained synchronization. The eNB communicates reference signals (PSS and SSS) for the UE to measure the signal strength in LTE networks. These signals are sent periodically for each eNB, in which some of the networks will be synchronized and some networks will be asynchronized, with 6ms being a standard measurement gap by which the UE is enabled to measure. Within the 6ms

measurement gap, the UE is believed to be able to target at least one of the

synchronized signals from all neighboring cells or bands, which is part of the policy behind the current 6ms duration within the LTE network. In particular, the UE can cover measurements over an entire range of synchronized and asynchronized network signals associated with an eNB within 6 ms. However, for the UE to actually measure these signals, the entire 6 ms measurement gap is often not needed, especially in

synchronous networks. BRIEF DESCRIPTION OF THE DRAWINGS

[0008] FIG. 1 illustrates a block diagram illustrating an example wireless

communications network environment for a UE or eNB according to various aspects or embodiments.

[0009] FIG. 2 illustrates example system or device for operating network

measurement gap patterns according to various aspects or embodiments.

[0010] FIG. 3 illustrates an example network device for operating network

measurement gap patterns according to various aspects or embodiments.

[0011] FIG. 4 illustrates an example signaling flow for an enhanced measurement gap in an LTE network according to various aspects or embodiments.

[0012] FIG. 5 illustrates an example measurement configuration information element for signaling an enhanced or non-enhanced measurement gap according to various aspects or embodiments.

[0013] FIG. 6 illustrates an example measurement object information element according for signaling an enhanced or non-enhanced measurement gap to various aspects or embodiments.

[0014] FIG. 7 illustrates an example measurement gap configuration information element for signaling an enhanced or non-enhanced measurement gap according to various aspects or embodiments.

[0015] FIG. 8 illustrates a process flow for processing or generating enhanced and non-enhanced measurement gaps within a network according to various aspects or embodiments.

DETAILED DESCRIPTION

[0016] The present disclosure will now be described with reference to the attached drawing figures, 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 utilized herein, 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 can be a processor, a process running on a processor, a controller, a circuit or a circuit element, an object, an executable, a program, a storage device, a computer, a tablet PC and/or a mobile phone with a processing device. By way of illustration, an application running on a server and the server can also be a component. One or more components can reside within a process, and a component can be localized on one computer and/or distributed between two or more computers. A set of elements or a set of other components can be described herein, in which the term "set" can be interpreted as "one or more."

[0017] Further, these components can execute from various computer readable storage media having various data structures stored thereon such as with a module, for example. The components can communicate via 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, a wide area network, or similar network with other systems via the signal).

[0018] As another example, a component can be an apparatus with specific functionality provided by mechanical parts operated by electric or electronic circuitry, in which the electric or electronic circuitry can be operated by a software application or a firmware application executed by one or more processors. The one or more processors can be internal or external to the apparatus and can execute at least a part of the software or firmware application. As yet another example, a component can be an apparatus that provides specific functionality through electronic components or elements without mechanical parts; the electronic components can include one or more processors therein to execute software and/or firmware that confer(s), at least in part, the functionality of the electronic components.

[0019] 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 employs B; or X employs both A and B, then "X employs A or B" is satisfied under any of the foregoing instances. In addition, the articles "a" and "an" as used in this application and the appended claims should generally be construed to mean "one or more" unless specified otherwise or clear from context to be directed to a singular form. Furthermore, to the extent that the terms "including", "includes", "having", "has", "with", or variants thereof are used in either the detailed description and the claims, such terms are intended to be inclusive in a manner similar to the term

"comprising".

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

[0021] In consideration of the above described deficiencies, network devices (e.g., macro cells, Access Points (APs), Access Controllers (ACs), eNBs, small cells, UEs, etc.) described herein can enable one or more specific measurement gap patterns and related solutions to support LTE carrier aggregation (CA) of a number of carrier components (CCs) for DL and UL. If a network device such as an eNB has knowledge that a connected network device (e.g., a UE communicatively connected to the eNB's network) is synchronized in its connection, then the measurement duration of 6 ms can be wasteful in it's duration for the UE because most of the reference signals will be pretty much already be aligned. This waste could then accumulate within the measurement gaps, where the UE cannot receive downlink signals, and introduces corruptions or interruptions for the UE to receive data.

[0022] As such, during a synchronized network operation, each UE can be configured to implement a specific measurement (an enhanced measurement gap) that differs from a standard measurement gap or a non-enhanced measurement gap. This re-configuration can operate, for example, to reduce the measurement gap length to about 2 ms, 3 ms or other shorter duration as an enhanced measurement gap for use in DL signaling.

[0023] Enhanced measurement gaps with shorter durations than non-enhanced measurement gaps can be dynamically configured for various UEs within or

communicatively coupled to a cell network. Within the synchronized network of the macro network, an eNB can configured enhanced measurement gaps on a per UE basis, such that some UEs are optimized in their communications with a reduced duration for measurement gaps or measurement gap patterns, while others can operate measurement gap patterns for neighboring cell measurement or cell measurements according to a regular measurement gap and measurement gap patterns utilizing such measurement gap. [0024] A measurement gap pattern can be referred to as the pattern of measurement gaps that the UE can facilitate frequency CC measurements on within a time period or duration (e.g., about 6 ms as a measurement gap, and less than 6 ms for an enhanced measurement gap). The UE, for example, can operate during a measurement gap to switch from a serving band it is connected on to a different band or CC in order to perform a measurement of the band or CC. The term serving band as used herein means the UE can be connected to that band as a serving band to receive downlink data on, in this case no measurement is necessarily required in that band because the UE is already operating in or on that band.

[0025] Additionally, a gap offset is referred to in order to indicate when a

measurement gap starts of begins. Measurement gap length can be another term used to refer to a duration of the measurement gap, such as about 6 ms or about 7 ms, for example. A network controlled small gap (NCSP) can refer to a reduced gap duration, such as about 2 ms, 3 ms, or another shorter duration than the measurement gap (e.g., a non-enhanced measurement gap) that is standard of about 6 ms. The use of the phrase enhanced measurement gap can also be used interchangeably with NCSP or a reduced measurement gap duration, for example.

[0026] In some aspects, an eNB can operate, via one or more components, to generate a first downlink communication to a first UE configured to indicate an enhanced measurement gap that is different than a non-enhanced measurement gap that is communicated to a second UE. In this network scenario, the first UE and the second UE are communicatively coupled to the eNB via a synchronous connection of a synchronous network, as opposed to an asynchronous network, which can be within the same macro cell or network enabled by the eNB. In one example, the eNB can communicate the enhanced measurement gap, for example, via one or more radio resource control (RRC) signals to the first UE.

[0027] In other aspects, a UE can operate, via one or more components, such as a communication component, comprising one or more communication chains

corresponding to one or more component carriers (CCs), configured to process one or more radio RRC signals. A processor component, communicatively coupled to the communication component, can process the one or more RRC signals and determine whether to apply an enhanced measurement gap based on the RRC signals. Additional aspects and details of the disclosure are further described below with reference to figures. [0028] FIG. 1 illustrates an example non-limiting wireless communications

environment 100 that can facilitate or enable one or more measurement gap

configurations via communications between an eNB and UEs for LTE CA to support an enhanced measurement gaps (e.g., shorter measurement gaps about 2 ms, 3 ms, or otherwise) or a non-enhanced measurement gap (e.g., about 6 ms or 7 ms) for any number of frequency carriers or carrier components, either differently from one another or the same with enhanced measurement gaps at one time and non-enhanced at another time under different network conditions. The wireless communications environment 100 can include a multitude of wireless communication networks, each having a respective coverage area that can operate to serve different measurement gap configurations that utilize different measurement gap lengths depending upon the network.

[0029] Wireless communications environment 100 can includes one or more cellular broadcast servers or macro cell network devices 1 02, 104 (e.g., base stations, eNBs, access points (APs) or the like) and one or more small cell network devices or APs (e.g., small eNBs, micro-eNBs, pico-eNBs, femto-eNBs, home eNBs (HeNBs), or Wi-Fi nodes) 106, 108 deployed within the wireless communications environment 100 and servicing one or more UE devices 1 10, 1 12, 1 14, 1 16, 1 18. Each wireless

communications network (e.g., cellular broadcast servers 102, 104 and small cell network devices 1 06, 108) can comprise one or more network devices (e.g., a set of network devices (NDs)) that operate in conjunction in order to process network traffic for the one or more UE devices 1 10, 1 12, 1 14, 1 16, or 1 18. For example, macro cell NDs 102, 104 can comprise a set of network devices that are cellular enabled network devices. In another example, the small cell network devices 106, 1 08 can include a set of network devices that operate with a smaller coverage zone than the macro cell network devices 1 02 and 102, for example.

[0030] Although NDs 106 and 108 are described as small cell network devices, they can 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 as a base station, eNB, or secondary cell network device for example. Alternatively one or more of the macro cell NDs 102 and 104 could be small cell network devices or other NDs of a different radio access technology (RAT) that operate with different frequency carriers, for example. [0031] As illustrated, each of the one or more Wi-Fi access points 106, 1 08 can have a corresponding service area 120, 122. Additionally, each of the one or more cellular broadcast servers or macro cell NDs 102, 104 can have a corresponding service area 124, 126. However, it should be understood that the wireless communications environment 100 is not limited to this implementation. For example, any number of APs or NDs with respective service areas can be deployed within the wireless

communications environment 100. Further, any number of cellular broadcast servers and respective service areas can be deployed within the wireless communications environment 100 as well.

[0032] Although only five UE devices 1 10, 1 12, 1 14, 1 1 6, 1 18 are illustrated, any number of UE devices can be deployed within the wireless communications

environment 100 as well. A UE device can contain some or all of the functionality of a system, subscriber unit, subscriber station, mobile station, mobile, wireless terminal, device, mobile device, remote station, remote terminal, access terminal, user terminal, terminal, wireless communication device, wireless communication apparatus, user agent, user device, or other ND, for example.

[0033] In one aspect, cellular broadcast servers or macro cell NDs 102, 104 and small cell NDs 106, 108 can monitor their surrounding radio conditions (e.g., by employing respective measurement components). For example, each of the macro cell NDs 102, 1 04 and small cell NDs 106, 108 can determine network traffic load on its respective network by performing a network diagnostic process. As an example, during a network listen procedure, macro cell NDs 102, 104, small cell NDs 106, 108 or UE devices 1 10, 1 12, 1 14, 1 1 6, 1 18 can scan their 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 macro cell NDs 102, 104 and small cell NDs 106, 108 can be detected during the network diagnostic procedure or measurements by the UE devices, such as, but not limited to, frequency bands, scrambling codes, common channel pilot power, bandwidth across respective networks, universal mobile telecommunications system terrestrial radio access receive signal strength indicator, as well as frequency carrier priorities for particular cell groups (e.g., a normal group or a reduced group) and so on.

[0034] In an example scenario, UE devices 1 10, 1 12, 1 14, 1 16, 1 18 can be serviced by networks through one of the macro cell NDs 102, 104, or small cell NDs 106, 108. As a user equipment device is moved within the wireless communications environment 100, the respective user equipment device might be moved in and out of the coverage area of the associated serving network. For example, as a user is sending/receiving communications through their respective UE device, the user might be walking, riding in a car, riding on a train, moving around a densely populated urban area (e.g., a large city), wherein the movement could cause the mobile device to be moved between various wireless communication networks. In such cases, it is beneficial for the UE to route the network traffic (e.g., handoff) from a serving ND to a target ND in order to continue the communication (e.g., avoid dropped calls) or facilitating offloading for load distribution or other efficiency purposes. However, with an increased number of NDs and frequency carriers to measure, UE devices 1 10, 1 12, 1 14, 1 16, 1 18 can have a problem being able to measure each carrier within allotted time measurement gaps, and when already synchronous with a particular eNB further waste time conducting measurement within measurement gap durations that are excessive. Because the UE devices 1 10, 1 12, 1 14, 1 1 6, 1 18 have to measure an increasingly greater number of carriers (e.g., 32 or greater), the measurement gaps can introduce more delay.

[0035] In one embodiment, the network 1 24 corresponding to the service area of eNB 102 can include different networks depending on the synchronous connection of the UE with the eNB 102. For example, the network or service area 124 can include portions of a network or service area 140 operating as a synchronous network, in which the UE 1 16 is synchronously connected thereat with a band or CC, and network 142 operating as an asynchronous network, in which the UE 1 10 is asynchronously connected thereat with a band or CC. In a synchronous connection, such as with the UE 1 1 6 to the eNB 102, the clocking of the data can be transmitted with data together, in the asynchronous connection, such as with the UE 1 1 0 and the eNB 102, the clocking mechanisms or times are independent of one another between receiver and transmitter of the UE 1 10 and eNB 102, for example.

[0036] As such, for UEs 1 16 and 1 10 within the network service area 124, the UE 1 1 6 can be configured by the eNB 1 02 to operate with an enhanced measurement gap of less duration or length than a non-enhanced measurement gap. While at the same time, or concurrently, the UE 1 10 can be configured by the eNB 102 to operate with a non-enhanced measurement gap that is longer in duration than the enhanced measurement gap. The enhanced measurement gap, for example, can comprise about 2 ms, 3 ms or other shorter duration than about 6 ms or 7 ms, which is a non-enhanced measurement gap duration, for example. [0037] In one example, two frequency carriers (e.g., CCs for LTE CA) of different frequencies can exist on the network environment 100, where 40 milliseconds (ms) can be the measurement gap reception period (MGRP), or some other period, such as 40 ms, 80 ms, or other gap period, for example. Because there are two CCs or more, for example, when supporting carrier aggregation, the UE devices 1 10, 1 12, 1 14, 1 16, 1 18 could operate on one carrier, which is the serving frequency, and thus with a single radio receiver / transmitter could measure one additional carrier. As such, every 40ms the UE (e.g., UE 1 10), for example, the UEs 1 10, 1 12, 1 14, 1 16, 1 18 can switch to another carrier to perform measurements thereon as a neighboring carrier or a neighboring network band. This means that every 40ms that the UE 1 10, for example, could measure once for a given MGRP, which can include a measurement gap to the DL communications on the serving band, in which as a measurement gap no DL data is being received by the UE on this serving band for it to measure the other neighboring band, for example. As such, if the measurement gap associated with the measuring operation during the given MGRP (e.g., 40 ms or other duration) is reduced as an enhanced measurement gap for a particular UE. As a result of the shorter or enhanced measurement gaps being signaled by the eNB 102 to the UE 1 16, for example, a cumulative time savings over a defined time could be exponential, or at least very significant in terms of resource savings and DL data throughput. The waste can thus accumulate within the measurement gaps, where the UE cannot receive downlink signals, and introduces corruptions or interruptions for the UE to receive data.

[0038] An enhanced measurement gap can be particularly useful for UEs (e.g., UE 1 1 6) within a synchronous network 140 where the UE 1 16 already has a synchronized connection and is aligned with the SSS and PSS synchronized signals sent by the eNB 102. The UE 1 1 6 can thus utilize shorter measurement gaps without having to utilize the full duration of a non-enhanced measurement gap. Because DL data is reduced or no data is received on downlink during measurement gap, particular with UEs (e.g., 1 1 6) with a single chain receiver corresponding with a single CC or band of operation, then delays do not accumulate as significantly as a result of the shorter / enhanced measurement gap configurations.

[0039] The eNB 1 02, for example, communicates the reference signals for the UE to measure. At each measurement sample, measurements could comprise any network measurement of network conditions related to the frequency band, network device operating (communicating) the frequency band, or channel conditions, such as a signal strength, a channel quality, a signal-to-noise-plus interference ratio (SINR), a received signal strength indictor (RSSI) or other measurement such as a reference signal received power (RSRP), a reference signal received quality (RSRQ), or the like. The UE can then generate channel state information (CSI), one or more channel quality indicators (CQIs) or the like to a transmission path for transmission based on one or more of the measurements. The synchronous signals are sent periodically by each eNB or ND 102, 104, for example, and some of the network will be synchronized (e.g., at 140) and some asynchronized (e.g., 142), but within the 6ms of non-enhanced measurement gap the UEs 1 16 or 1 10 are expected to be able to hit at least one of the synchronized signals from all the neighboring cells, which is one policy behind the current, approximately 6ms duration as standard currently within the LTE networks.

[0040] In another embodiment, the eNB 1 02 can determine or operate to ascertain whether the UEs 1 16 and 1 10 are synchronized or not. If a UE's network is a synchronized network 140, then the eNB 102 can signal to the individual UE 1 16 to use the enhanced measurement gap configuration to reduce the measurement gap duration to 2 ms or 3 ms. Different ways for the network to configure or signal this enhanced measurement gap to reduce the size of the measurement gap for a particular UE 1 16 and a different non-enhanced measurement gap for another UE 1 1 0, can be utilized by the eNB 102. Alternatively or additionally, the eNB 102 can signal an enhanced measurement gap to trigger or configure the UE 1 16 to utilize at one time and then a non-enhanced measurement gap to be utilized at another time based on changing network conditions (e.g., movement from a synchronized network connection 140 to an asynchronous network connection 142, or other changing network parameters).

Alternatively or additionally, the eNB 102 can signal the UEs 1 16 and 1 10 differently at the same time to utilize different measurement gaps (enhanced or non-enhance) and modify these measurement gaps as each of them experiences different network conditions.

[0041] The eNB 1 02 can also utilize different signaling mechanisms for configuring the UEs 1 16 and 1 10 with different measurement gaps. In one embodiment, UEs 1 1 6 and 1 10, for example, can be preconfigured to receive signaling from an eNB 102 with prior knowledge of an enhanced measurement gap duration in a standards

specification. If the UE 1 1 6 is preconfigured to use an enhanced measurement gap, for example, then it could be either 2 or 3 ms in duration, which can be activated in response to a signaling by the eNB 102, such as via a one bit signal to indicate or configured an enhanced measurement gap at that particular UE 1 1 6.

[0042] For example, the one bit indication can be added in the measurement information element (IE), which is illustrated in FIG. 5 as a short measurement indication 502 (e.g., shortMeaslndicator-r14), such as for 3GPP release 14 (r14). In response to the UE 1 16 receiving the indication (e.g., a one bit in a MeasConfig / MeasGapConfig IE, or a MeasObjectEUTRA IE) to trigger utilizing an enhanced measurement gap for band measurements, neighbor cell measurements, or for different CCs, and the UE 1 16 being within a synchronized network 140, then the UE 1 16 can alter / modify measurement gaps to be within the enhanced measurement gap duration (e.g., 2 ms, 3 ms, or other shorter duration) from a non-enhanced measurement gap configuration (e.g., about 6 ms or 7 ms). The IE MeasConfig or measconfig can generally specify measurement(s) to be performed by the UE, covering intra-frequency, inter-frequency and inter-RAT mobility as well as the configuration of the measurement gaps (enhanced or non-enhanced), which can be further defined in 3GPP TS 36.331 , for example.

[0043] In another embodiment, a one bit indication to implement the enhanced measurement gap can be configured and provided by the communication of a measurement object (e.g., MeasObject) by the eNB 1 02 to the UE 1 16, which is illustrated for example at FIG. 6. For each measurement gap (enhanced or non- enhanced), the eNB 102 can configure measurement objects for individual different carriers, frequency bands, or different cells. The different cells, for example can be evolved universal terrestrial radio access (EUTRA) cells or networks of a EUTRA protocol. So if a network for a particular frequency is synchronized and such

synchronicity is known / determined by the eNB 102, then the eNB 102 can configure this measurement object (MeasObjectEUTRA ID) such as shortMeaslndicator-r14 602 to be used within or for a shorter measurement gap. For example, the eNB 102 can utilize the measurement object EUTRAN IE and inside this IE configure the short measurement indicator of one bit for a particular UE 1 16 to use on the network or a CC for measuring. A single measurement object can be configured per radio frequency (RF) carrier or cell, for example, or be applied to any and all bands, CCs or EUTRA cells, for example, especially for inter-frequency EUTRA bands, CCs or cells.

[0044] In another embodiment, instead of using one bit, the eNB 102 can generate be one or more (e.g., two) different measurement gap durations for any measurement gap configurations in the MeasurementGapConfig or MeasGapConfig IE, which is illustrated in more detail at FIG. 7. As such, different measurement gap patterns can be signaled to the UE 1 16. In response to receiving the MeasGapConfig IE 700, for example, the UE 1 16 can measure bands or CCs utilizing at least two different patterns with different enhanced measurement gaps or shorter durations than otherwise would with a non-enhanced measurement gap. As such, a better optimization of time and resources can be configured dynamically and when already synchronized via the synchronous network 140 or a synchronous connection with the eNB 102.

[0045] In one example of the measurement gap configuration information element (MeasGapConfig IE), an indication of 0 and 1 for measurement gaps, can be provided by the eNB 102 to indicate enhanced measurement gaps for 40 ms and 80 ms periodic measurement periods / MGRPs depending on the configuration of the information element (e.g., a MeasGapConfig IE as in TS 36.331 , or a measurement gap object (MeasObjectEUTRA IE), such as referred to in TS 36.133). As such, the eNB 102 can configure a communication to the UE 1 16 of either a shorter gap for 40 ms, for 80 ms, and other periods at the same time or concurrently when in a synchronous network. For example, an indication for each period of 40 ms and 80 ms can be signaled by a zero or one for each to the UE 1 16 and signal the UE to measure shorter or enhanced measurement gaps therein depending on which period is being configured for measurement reporting. As such, a shorter / enhanced measurement gap can be configured for gap offsets or MGRPs at 40 ms and not for 80 ms (with non-enhanced measurement gaps) or vice versa, enhanced measurement gaps for both 40 ms and 80 ms, or neither MGRP with an enhanced measurement gap, but instead a non-enhanced measurement gap, depending on the state of the bit(s) for each MGRP.

[0046] The MeasGapConfig IE can be communicated by the eNB 102 to the UE 1 16, for example, with various field descriptions, such as a gap offset (gapOffset)

corresponding to different measurement gap patterns with either an enhanced measurement gap or a non-enhanced measurement gap as illustrated in FIG. 7. A gapOffset can have a value of gpO that corresponds, for example, to a gap offset of a measurement gap pattern (Gap Pattern ID "0") with a MGRP = to 40 ms, while gapOffset of gp1 corresponds to a gap offset of a gap pattern (Gap Pattern ID "1 ") with MGRP = 80 ms. These designations or formulations are also used to specify the measurement gap pattern to be applied, as defined in TS 36.1 33, for example. A gap offset of gpO-short can correspond to a gap offset of a Gap Pattern ID "0" with MGRP - 40 ms with 2 ms duration for the measurement / measurement gap. A gap offset (gapOffset) of gp1 -short corresponds to a gap offset of a Gap Pattern ID "1 " with MGRP = 80 ms with a 2 ms gap duration for measurement. Other durations than 2 ms can also be indicated as well that are shorter than a non-enhanced measurement gap of about 6 ms, for example. The gap pattern is not particularly discussed herein, but can refer to the sequence of measurement on one band or another band, while not receiving or only partially receiving DL data, such as with a single receive chain corresponding to a frequency range or multiple different receiver chains. The gap pattern Id can provide indication of the particular measurement gap pattern, for example.

[0047] Embodiments described herein can be implemented into a system using any suitably configured hardware / software. FIG. 2 illustrates, for one embodiment, example components of a cell network device 200, such as a base station, a macro cell network device, a secondary cell network device, a small cell network device, an evolved/enhanced NodeB (eNB), or any other network device (e.g. a user equipment, pico cell, Femto cell or the like). In some embodiments, the cell network device 200 can include application circuitry 202, baseband circuitry 204, Radio Frequency (RF) circuitry 206, front-end module (FEM) circuitry 208 and one or more antennas 210, coupled together at least as shown.

[0048] The application circuitry 202 can include one or more application processors. For example, the application circuitry 202 can include circuitry such as, but not limited to, one or more single-core or multi-core processors. The processor(s) can include any combination of general-purpose processors and dedicated processors (e.g., graphics processors, application processors, etc.). The processors can be coupled with and/or can include memory / storage and can be configured to execute instructions stored in the memory/storage to enable various applications and/or operating systems to run on the system.

[0049] The baseband circuitry 204 can include circuitry such as, but not limited to, one or more single-core or multi-core processors. The baseband circuitry 204 can include one or more baseband processors and/or control logic to process baseband signals received from a receive signal path of the RF circuitry 206 and to generate baseband signals for a transmit signal path of the RF circuitry 206. Baseband processing circuity 204 can interface with the application circuitry 202 for generation and processing of the baseband signals and for controlling operations of the RF circuitry 206. For example, in some embodiments, the baseband circuitry 204 can include a second generation (2G) baseband processor 204a, third generation (3G) baseband processor 204b, fourth generation (4G) baseband processor 204c, and/or other baseband processor(s) 204d for other existing generations, generations in development or to be developed in the future (e.g., fifth generation (5G), 6G, etc.). The baseband circuitry 204 (e.g., one or more of baseband processors 204a-d) can handle various radio control functions that enable communication with one or more radio networks via the RF circuitry 206. The radio control functions can include, but are not limited to, signal modulation/demodulation, encoding/decoding, radio frequency shifting, etc. In some embodiments, modulation/demodulation circuitry of the baseband circuitry 204 can include Fast-Fourier Transform (FFT), precoding, and/or constellation mapping / demapping functionality. In some embodiments, encoding/decoding circuitry of the baseband circuitry 204 can include convolution, tail-biting convolution, turbo, Viterbi, and/or Low Density Parity Check (LDPC) encoder/decoder functionality. Embodiments of modulation/demodulation and encoder/decoder functionality are not limited to these examples and can include other suitable functionality in other embodiments.

[0050] In some embodiments, the baseband circuitry 204 can include elements of a protocol stack such as, for example, elements of an evolved universal terrestrial radio access network (EUTRAN) protocol including, for example, physical (PHY), media access control (MAC), radio link control (RLC), packet data convergence protocol (PDCP), and/or radio resource control (RRC) elements. A central processing unit (CPU) 204e of the baseband circuitry 204 can be configured to run elements of the protocol stack for signaling of the PHY, MAC, RLC, PDCP and/or RRC layers. In some embodiments, the baseband circuitry can include one or more audio digital signal processor(s) (DSP) 204f. The audio DSP(s) 204f can be include elements for compression/decompression and echo cancellation and can include other suitable processing elements in other embodiments. Components of the baseband circuitry can be suitably combined in a single chip, a single chipset, or disposed on a same circuit board in some embodiments. In some embodiments, some or all of the constituent components of the baseband circuitry 204 and the application circuitry 202 can be implemented together such as, for example, on a system on a chip (SOC).

[0051] In some embodiments, the baseband circuitry 204 can provide for

communication compatible with one or more radio technologies. For example, in some embodiments, the baseband circuitry 204 can support communication with a EUTRAN and/or other wireless metropolitan area networks (WMAN), a wireless local area network (WLAN), a wireless personal area network (WPAN). Embodiments in which the baseband circuitry 204 is configured to support radio communications of more than one wireless protocol can be referred to as multi-mode baseband circuitry.

[0052] RF circuitry 206 can enable communication with wireless networks

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

[0053] In some embodiments, the RF circuitry 206 can include a receive signal path and a transmit signal path. The receive signal path of the RF circuitry 206 can include mixer circuitry 206a, amplifier circuitry 206b and filter circuitry 206c. The transmit signal path of the RF circuitry 206 can include filter circuitry 206c and mixer circuitry 206a. RF circuitry 206 can also include synthesizer circuitry 206d for synthesizing a frequency for use by the mixer circuitry 206a of the receive signal path and the transmit signal path. In some embodiments, the mixer circuitry 206a of the receive signal path can be configured to down-convert RF signals received from the FEM circuitry 208 based on the synthesized frequency provided by synthesizer circuitry 206d. The amplifier circuitry 206b can be configured to amplify the down-converted signals and the filter circuitry 206c can be a low-pass filter (LPF) or band-pass filter (BPF) configured to remove unwanted signals from the down-converted signals to generate output baseband signals. Output baseband signals can be provided to the baseband circuitry 204 for further processing. In some embodiments, the output baseband signals can be zero- frequency baseband signals, although this is not a requirement. In some embodiments, mixer circuitry 206a of the receive signal path can comprise passive mixers, although the scope of the embodiments is not limited in this respect.

[0054] In some embodiments, the mixer circuitry 206a of the transmit signal path can be configured to up-convert input baseband signals based on the synthesized frequency provided by the synthesizer circuitry 206d to generate RF output signals for the FEM circuitry 208. The baseband signals can be provided by the baseband circuitry 204 and can be filtered by filter circuitry 206c. The filter circuitry 206c can include a low-pass filter (LPF), although the scope of the embodiments is not limited in this respect.

[0055] In some embodiments, the mixer circuitry 206a of the receive signal path and the mixer circuitry 206a of the transmit signal path can include two or more mixers and can be arranged for quadrature down-conversion or up-conversion respectively. In some embodiments, the mixer circuitry 206a of the receive signal path and the mixer circuitry 206a of the transmit signal path can include two or more mixers and can be arranged for image rejection (e.g., Hartley image rejection). In some embodiments, the mixer circuitry 206a of the receive signal path and the mixer circuitry 206a can be arranged for direct down-conversion or direct up-conversion, respectively. In some embodiments, the mixer circuitry 206a of the receive signal path and the mixer circuitry 206a of the transmit signal path can be configured for super-heterodyne operation.

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

[0057] In some dual-mode embodiments, a separate radio IC circuitry can be provided for processing signals for each spectrum, although the scope of the

embodiments is not limited in this respect.

[0058] In some embodiments, the synthesizer circuitry 206d can be a fractional-N synthesizer or a fractional N/N+2 synthesizer, although the scope of the embodiments is not limited in this respect as other types of frequency synthesizers can be suitable. For example, synthesizer circuitry 206d can be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer comprising a phase-locked loop with a frequency divider.

[0059] The synthesizer circuitry 206d can be configured to synthesize an output frequency for use by the mixer circuitry 206a of the RF circuitry 206 based on a frequency input and a divider control input. In some embodiments, the synthesizer circuitry 206d can be a fractional N/N+2 synthesizer.

[0060] In some embodiments, frequency input can be provided by a voltage controlled oscillator (VCO), although that is not a requirement. Divider control input can be provided by either the baseband circuitry 204 or the applications processor 202 depending on the desired output frequency. In some embodiments, a divider control input (e.g., N) can be determined from a look-up table based on a channel indicated by the applications processor 202.

[0061] Synthesizer circuitry 206d of the RF circuitry 206 can include a divider, a delay-locked loop (DLL), a multiplexer and a phase accumulator. In some embodiments, the divider can be a dual modulus divider (DMD) and the phase accumulator can be a digital phase accumulator (DPA). In some embodiments, the DMD can be configured to divide the input signal by either N or N+2 (e.g., based on a carry out) to provide a fractional division ratio. In some example embodiments, the DLL can include a set of cascaded, tunable, delay elements, a phase detector, a charge pump and a D-type flip- flop. In these embodiments, the delay elements can be configured to break a VCO period up into Nd equal packets of phase, where Nd is the number of delay elements in the delay line. In this way, the DLL provides negative feedback to help ensure that the total delay through the delay line is one VCO cycle.

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

[0063] FEM circuitry 208 can include a receive signal path which can include circuitry configured to operate on RF signals received from one or more antennas 210, amplify the received signals and provide the amplified versions of the received signals to the RF circuitry 206 for further processing. FEM circuitry 208 can also include a transmit signal path which can include circuitry configured to amplify signals for transmission provided by the RF circuitry 206 for transmission by one or more of the one or more antennas 21 0.

[0064] In some embodiments, the FEM circuitry 208 can include a TX/RX switch to switch between transmit mode and receive mode operation. The FEM circuitry can include a receive signal path and a transmit signal path. The receive signal path of the FEM circuitry can include a low-noise amplifier (LNA) to amplify received RF signals and provide the amplified received RF signals as an output (e.g., to the RF circuitry 206). The transmit signal path of the FEM circuitry 208 can include a power amplifier (PA) to amplify input RF signals (e.g., provided by RF circuitry 206), and one or more filters to generate RF signals for subsequent transmission (e.g., by one or more of the one or more antennas 21 0.

[0065] In some embodiments, the cell network device 200 can include additional elements such as, for example, memory/storage, display, camera, sensor, and/or input/output (I/O) interface. In some embodiments, the electronic device of Figure 2 may be configured to perform one or more processes, techniques, and/or methods as described herein, or portions thereof.

[0066] In other embodiments, the network device 200 can operate to generate / process measurement gap enhancement as an enhanced measurement gap with a single Rx chain. This includes, but not limited to, an increased UE scheduling opportunity or reduced UE power consumption. In particular, for synchronous only operation, the measurement gap configurations with reduced measurement gap lengths can be generated and processed with the lengths being configured via one or more information elements (e.g., MeasConfig lEs, MeasObjectEUTRA lEs, MeasGapConfig lEs, or otherwise). The eNB 102 as the network device 200 can provide a per component carrier configuration of measurement gaps with different CCs or cells utilizing different measurement gap lengths (enhanced or non-enhanced measurement gaps) via the same UE 1 1 6, for example, or via different UEs 1 16 and 1 10, within a synchronous network. In the per CC based measurement gap configuration, MGRP can be configured independently per CC. This can also include the case where the measurement gaps are configured for some of CC, but not configured for the other CC. Network controlled small gap (NCSG) or enhanced measurement gaps as discussed herein can be introduced when per CC measurement gap configurations are configured to reduce the Ack / Nack missing rate due to primary cell (PCell) / secondary cell (SCell) / primary secondary cell (PSCell) interruption. Whether the UE 1 16, for example, should report its capabilities on per CC based measurement gaps can further be under the network control via the eNB 102, for example.

[0067] FIG. 3 further illustrates an embodiment of a network device or system 300 to be employed in an eNB, a UE or other network device that facilitates or enables signaling mechanisms to process or provide enhanced measurement gaps of shorter duration than non-enhanced measurement gaps. System or device 300 can include the baseband circuitry component 204, the radio frequency (RF) circuitry component 206, or a front end module circuitry component 308 of FIG. 2, as well as communication component or platform 308 with transmitter circuitry component(s) / receiver circuitry component 310 (e.g., a communication component), a processor 316 and memory 324.

[0068] In various aspects, system 300 can be included within an Evolved Universal Terrestrial Radio Access Network (E-UTRAN) Node B (Evolved Node B, eNodeB, or eNB 102), other base station, network access point, a secondary cell network device (e.g., a small cell, or WiFi network device) or other cell network component/device (e.g., UE 1 16 and 1 10) in a wireless communications network (e.g., network 1 24). Memory 324 also can include instructions that can be implemented by processor 316, transmitter circuitry 31 0, or receiver circuitry 310 to implement various aspects or embodiments described herein.

[0069] Memory 324 can comprise one or more machine-readable medium / media including instructions that, when performed by a machine or component herein cause the machine to perform acts of the method or of an apparatus or system for concurrent communication using multiple communication technologies according to embodiments and examples described herein. It is to be understood that aspects described herein can be implemented by hardware, software, firmware, or any combination thereof.

When implemented in software, functions can be stored on or transmitted over as one or more instructions or code on a computer-readable medium (e.g., the memory described herein or other storage device). 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 a 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 medium, 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 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 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. As described in greater detail below, system 300.

[0070] Access equipment (e.g., eNB, network entity, or the like), UE or software related to access of the network device 300 can receive and transmit signal(s) from and to wireless devices, wireless ports, wireless routers, etc. through segments 302 302 _B (B is a positive integer). Segments 302 302 _B can be internal and/or external to access equipment and/or software related to access of a network, and can be controlled by a monitor component 304 and an antenna component 306. Monitor component 304 and antenna component 306 can couple to communication component 308, which can include electronic components and associated circuitry that provide for processing and manipulation of received signal(s) and other signal(s) to be transmitted.

[0071] In an aspect, communication component 308 includes the receiver/transmitter 31 0 that can convert analog signals to digital signals upon reception of the analog signals, and can convert digital signals to analog signals upon transmission. In addition, receiver / transmitter 310 can divide a single data stream into multiple, parallel data streams, or perform the reciprocal operation. Coupled to receiver/transmitter 310 can be a multiplexer / demultiplexer 312 that can facilitate manipulation of signals in time and frequency space. Multiplexer / demultiplexer 312 can multiplex information (data/traffic and control/signaling) according to various multiplexing schemes such as time division multiplexing, frequency division multiplexing, orthogonal frequency division multiplexing, code division multiplexing, space division multiplexing. In addition, multiplexer / demultiplexer component 312 can scramble and spread information (e.g., codes, according to substantially any code known in the art, such as Hadamard-Walsh codes, Baker codes, Kasami codes, polyphase codes, and so forth).

[0072] A modulator / demodulator 314 can also be a part of communication component / platform 308, and can modulate information according to multiple modulation techniques, such as frequency modulation, amplitude modulation (e.g., M- ary quadrature amplitude modulation, with M a positive integer); phase-shift keying; and so forth).

[0073] Access equipment and/or software related to access of a network also includes a processor 316 (or processor component) configured to confer, at least in part, functionality to substantially any electronic component in access equipment and/or software. In particular, processor 316 can facilitate configuration of access equipment and/or software through, for example, monitor component 304, antenna component 306, and one or more components therein. Additionally, access equipment and/or software can include display interface 318, which can display functions that control functionality of access equipment and/or software or reveal operation conditions thereof. In addition, display interface 318 can include a screen to convey information to an end user. In an aspect, display interface 318 can be a liquid crystal display, a plasma panel, a monolithic thin-film based electrochromic display, and so on. Moreover, display interface 318 can include a component (e.g., speaker) that facilitates communication of aural indicia, which can also be employed in connection with messages that convey operational instructions to an end user. Display interface 318 can also facilitate data entry (e.g., through a linked keypad or through touch gestures), which can cause access equipment and/or software to receive external commands (e.g., restart operation).

[0074] Broadband network interface 320 facilitates connection of access equipment or software to a service provider network (not shown) that can include one or more cellular technologies (e.g., third generation partnership project universal mobile telecommunication system, global system for mobile communication, and so on) through backhaul link(s) (not shown), which enable incoming and outgoing data flow. Broadband network interface 320 can be internal or external to access equipment and/or software and can utilize display interface 318 for end-user interaction and status information delivery.

[0075] Processor 316 can be functionally connected to communication platform 308 and can facilitate operations on data (e.g., symbols, bits, or chips) for

multiplexing/demultiplexing, such as effecting direct and inverse fast Fourier transforms, selection of modulation rates, selection of data packet formats, inter-packet times, and so on. Moreover, processor 316 can be functionally connected, through data, system, or an address bus 322, to display interface 31 8 and broadband network interface 320, to confer, at least in part, functionality to each of such components.

[0076] In access equipment and/or software memory 324 can retain location and/or coverage area (e.g., macro sector, identifier(s)) access list(s) that authorize access to wireless coverage through access equipment and/or software sector intelligence that can include ranking of coverage areas in the wireless environment of access equipment and/or software, radio link quality and strength associated therewith, or the like. Memory 324 also can store data structures, code instructions and program modules, system or device information, code sequences for scrambling, spreading and pilot transmission, access point configuration, and so on. Processor 31 6 can be coupled (e.g., through a memory bus), to memory 324 in order to store and retrieve information used to operate and/or confer functionality to the components, platform, and interface that reside within access equipment and/or software.

[0077] The network device 300, system, component or device herein can be incorporated into or otherwise part of, an eNB, a UE, or some other type of electronic device in accordance with various embodiments. Specifically, the electronic device or components or interfaces described herein can be logic and/or circuitry that can be at least partially implemented in one or more of hardware, software, and/or firmware. In embodiments, the electronic device logic can include radio transmit logic and receive logic (e.g., 310) coupled to control logic (e.g., processor 316). In embodiments, the transmit and/or receive logic can be elements or modules of transceiver logic 310. The electronic device and/or the components, circuitry or interfaces of such electronic device can be configured to perform operations similar to those described elsewhere in this disclosure.

[0078] In one embodiment, the processor 316 can generate or process reduced measurement durations / enhanced measurement gaps for the UE 1 1 6 of FIG. 1 while the UE 1 10 processes non-reduced or non-enhanced measurements gaps, according to configurations provided via the eNB 102. As part of the UE 1 16, the processor 316 can operate to receive an enhanced measurement gap via one or more RRC signals, which can be communicated with a bit indication (e.g., a bit indication or set of bits) that indicates / triggers utilizing the enhanced measurement gap for synchronous operation. The UE 1 16 can process an IE such as a MeasConfig (see, TS 36.331 ) and obtain or extract the shortMeaslndicator-r14 to determine whether the enhanced measurement gap should be configured or not as part of the measurement gaps for measuring one or more bands, CCs or cells across different frequencies or frequency ranges as part of a measurement gap pattern or sequence.

[0079] In another embodiment, the UE 1 1 6 can process or eNB 1 02 generate, via the processor (e.g., 316) therein a DL communication with a MeasObject or

measurement object within an IE, which can correspond to one or more CCs, bands, or inter-frequency EUTRA cells. The MeasObjectEUTRA information element can then indicate whether to utilize enhanced measurement gaps (e.g., 2 m or 3 ms), or non- enhanced measurement gaps (e.g., 6 ms). The utilization of the enhanced

measurement gaps can further occur in response to being connected to the

synchronous network 140, for example, as well as from processing of the

MeasObjectEUTRA IE with an indication to utilize the enhanced measurement gap, which is shorter in duration than the non-enhanced measurement gap.

[0080] In another embodiment, a new gap configuration can be added to indicate the enhanced measurement gap configurations for synchronous only operation. The measurement gap configuration (MeasGapConfig, see, TS 36.331 ) can further include a measurement gap configuration corresponding to controlling the setup and release of the enhanced measurement gaps. A gap offset field of the IE can be added with values that correspond to a gap offset (gapOffset) of a measurement gap pattern identifier or ID with a particular MGRP corresponding to a particular shortened duration compared to a non-enhanced measurement gap. For example, a gapOffset value of gpO-short can correspond to a gap offset of a Gap Pattern ID "0" with MGRP = 40 ms with a 2 ms gap duration for measurement. In the same IE a gapOffset of gp1 -short can be signaled as corresponding to a Gap Pattern ID "1 " with MGRP = 80 ms with 2 ms gap duration for measurement. The gapOffset can also be used to specify the measurement gap pattern to be applied, as defined in TS 36.133.

[0081] Referring to FIG. 4, illustrated is an example signaling flow between the UEs 1 1 0, 1 16 and the eNB 102 for enhanced measurement gaps. At 402, the UE102 can signal measurement gaps, either as an enhanced measurement gap with shorter lengths (e.g., 2 ms, 3 ms, or otherwise) or non-enhanced measurement gaps with longer durations than the enhanced measurement gaps (e.g., about 6 ms). As discussed above, the UE 1 1 0 or 1 16 can be preconfigured so that when either a measurement gap IE (MeasConfig IE) has a bit indicator (e.g., a Boolean indicator) or set of bits providing an indication based on their status, or a measurement object (MeasObject IE) is received the UEs 1 10 or 1 16 can determined from the lEs in an RRC signal whether to apply a non-enhanced measurement gap or not and what duration. The enhanced measurement gap can further be implemented in further response to already having a synchronous connection rather than an asynchronous connection on the network with the eNB 102. Further, the UE 1 10 can receive a different signaling than the UE 1 16 so that the UE 1 10 implements one or more non-enhanced measurement gaps based on the indication status of the IE received via RRC signaling 402, while the UE 1 16 receives a different IE via RRC signaling 402 to utilize one or more enhanced measurement gaps.

[0082] Each UE 1 10 and 1 16 can then report 404 measurement data to the eNB 1 02 based on the measurement gap patterns, the MGRP, a set shortened duration and a configuration of the enhanced measurement gap within the measurement gap configuration information element. In response to the eNB 1 02 determining that the UE 1 1 0 or 1 16 either no longer benefits from the current measurement gap corresponding to each (enhanced or non-enhanced), the eNB 102 can re-configure or indicate by different status with another information element. For example, if UE 1 10 enters a synchronous network or obtains a synchronous connection, the eNB 102 can decide to reconfigure an information element, as discussed herein, with a configuration or status indication for an enhanced measurement gap to initiate there. Likewise, a modification of the current measurement gap in the UE 1 16 can also be made in response to one or more changing network conditions, for example.

[0083] While the methods described within this disclosure are illustrated in 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 of the description herein. Further, one or more of the acts depicted herein may be carried out in one or more separate acts and/or phases.

[0084] Referring to FIG. 8, illustrated is a process flow for operations to generate or process an enhanced measurement gap in response to instructions of one or more processors of an eNB (e.g., 102) or a user equipment (e.g., 1 16).

[0085] The method 800 initiates at 802 with determining, via the one or more processors, an indication of an enhanced measurement gap.

[0086] At 804, the method 800 comprises processing, via the one or more processors on a receive path or on a transmit path, the indication of the enhanced measurement gap to enable cell measurements, wherein the enhanced measurement gap comprises a shorter measurement gap than a non-enhanced measurement gap configuration that enable the cell measurements. As such, the processing can include processing the indication of the enhanced measurement gap with a shorter gap duration than a non-enhanced measurement gap, which enables cell measurements based on the enhanced measurement gap or the non-enhanced measurement gap.

[0087] Further, the processing the indication of the enhanced measurement gap is in response to identifying a synchronous network connection to a network device on a synchronous long term evolution (LTE) network.

[0088] In another embodiment, the method 800 can further comprise applying the enhanced measurement gap to a first component carrier for the cell measurements and applying a non-enhanced measurement gap to a second component carrier for the cell measurements based on a radio resource control (RRC) signal. The enhanced measurement gap comprises a measurement gap length of about two milliseconds or about three milliseconds, and the non-enhanced measurement gap comprises about six milliseconds.

[0089] The method 800 can also comprise identifying whether a bit of an information element indicates whether to utilize the enhanced measurement gap or a non-enhanced measurement gap. While one UE can receive an enhanced measurement gap corresponding thereto, another UE can receive a non-enhanced measurement gap indication as an IE or as a part of a measurement gap configuration, for example.

Identifying the indication of the enhanced measurement gap can be performed within an information element that comprises a measurement configuration (MeasConfig), or a MeasObjectEUTRA), or as part of a measurement gap configuration IE.

[0090] The method 800 further enables increasing scheduling opportunities configured for enabling the cell measurements at one or more synchronous connections on a synchronous network by applying the enhanced measurement gap for the cell measurements on a synchronous network band based on the indication in an information element of the RRC signal.

[0091] As used herein, the term "logic" can refer to, be part of, or include

an Application Specific Integrated Circuit (ASIC), an electronic circuit, a processor (shared, dedicated, or group), or memory (shared, dedicated, or group) that execute one or more software or firmware programs, a combinational logic circuit, and/or other suitable hardware components that provide the described functionality. Specifically, the logic can 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. [0092] In various embodiments herein, a system can 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, etc. In various embodiments, system can have more or less components, and/or different architectures. For example, in some embodiments the RF logic and/or the baseband logic can be embodied in

communication logic (not shown). The communication logic can include one or more single-core or multi-core processors and logic circuits to provide signal processing techniques, for example, encoding, modulation, filtering, converting, amplifying, etc., suitable to the appropriate communication interface over which communications will take place. The communication logic can communicate over wireline, optical, or wireless communication mediums. In embodiments in which the system is configured for wireless communication, the communication logic can include the RF logic and/or baseband logic to provide for communication compatible with one or more radio technologies. For example, in some embodiments, the communication logic can support communication with an evolved universal terrestrial radio access network (EUTRAN) and/or other wireless metropolitan area networks (WMAN), a wireless local area network (WLAN), a wireless personal area network (WPAN).

[0093] Embodiments herein can be described as related to the 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), etc. may be used that may be viewed as LTE- related terms or entities. However, in other embodiments the technology may be used in or related to other wireless technologies such as the Institute of Electrical and Electronic Engineers (IEEE) 802.16 wireless technology (WiMax), IEEE 802.1 1 wireless technology (WiFi), various other wireless technologies such as 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.

technologies either already developed or to be developed. In those embodiments, where LTE-related terms such as eNB, MME, UE, etc. are used, one or more entities or components may be used that may be considered to be equivalent or approximately equivalent to one or more of the LTE-based terms or entities.

[0094] As it employed in the subject specification, the term "processor" can refer to substantially any computing processing unit or device including, but not limited to including, single-core processors; single-processors with software multithread execution capability; multi-core processors; multi-core processors with software multithread execution capability; multi-core processors with hardware multithread technology;

parallel platforms; and parallel platforms with distributed shared memory. Additionally, a processor can 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, a discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions and/or processes described herein. Processors can exploit nano-scale architectures such as, but not limited to, molecular and quantum-dot based transistors, switches and gates, in order to optimize space usage or enhance performance of mobile devices. A processor may also be implemented as a combination of computing processing units.

[0095] In the subject specification, terms such as "store," "data store," data storage," "database," and substantially any other information storage component relevant to operation and functionality of a component and/or process, refer to "memory

components," or entities embodied in a "memory," or components including the memory. It is noted that the memory components described herein can be either volatile memory or nonvolatile memory, or can include both volatile and nonvolatile memory.

[0096] By way of illustration, and not limitation, nonvolatile memory, for example, can be included in a memory, non-volatile memory, disk storage, and memory storage. Further, nonvolatile memory can be included in read only memory, programmable read only memory, electrically programmable read only memory, electrically erasable programmable read only memory, or flash memory. Volatile memory can include random access memory, which acts as external cache memory. By way of illustration and not limitation, random access memory is available in many forms such as synchronous random access memory, dynamic random access memory, synchronous dynamic random access memory, double data rate synchronous dynamic random access memory, enhanced synchronous dynamic random access memory, Synchlink dynamic random access memory, and direct Rambus random access memory.

Additionally, the disclosed memory components of systems or methods herein are intended to include, without being limited to including, these and any other suitable types of memory. [0097] Examples can include subject matter such as a method, means for performing acts or blocks of the method, at least one machine-readable medium including instructions that, when performed by a machine cause the machine to perform acts of the method or of an apparatus or system for concurrent communication using multiple communication technologies according to embodiments and examples described herein.

[0098] Example 1 is an apparatus configured to be employed in an evolved NodeB (eNB) comprising one or more processors configured to: generate a first downlink communication to a first user equipment (UE) configured to indicate an enhanced measurement gap that is different than a non-enhanced measurement gap that is communicated to a second UE, wherein the first UE and the second UE are

communicatively coupled to the eNB via a synchronous connection of a synchronous network; and communicate the enhanced measurement gap via one or more radio resource control (RRC) signals.

[0099] Example 2 includes the apparatus of claim 1 , wherein the one or more processors are further configured to generate a measurement configuration

(MeasConfig) with an indicator configured to indicate whether the enhanced

measurement gap is active or inactive for the first UE.

[00100] Example 3 includes the subject matter of any one of Examples 1 -2, including or omitting optional elements, wherein the indicator comprises a single bit within an information element comprising the MeasConfig, and the MeasConfig is configured to further indicate measurements to be performed based on at least one of: an inter- frequency or an inter-radio access technology (inter-RAT) mobility, and configuration of one or more measurement gaps or measurement gap patterns.

[00101 ] Example 4 includes the subject matter of any one of Examples 1 -3, including or omitting optional elements, wherein the enhanced measurement gap comprises a shorter measurement gap length than the non-enhanced measurement gap.

[00102] Example 5 includes the subject matter of any one of Examples 1 -4, including or omitting optional elements, wherein the enhanced measurement gap comprises a measurement gap length that comprises two milliseconds or three milliseconds.

[00103] Example 6 includes the subject matter of any one of Examples 1 -5, including or omitting optional elements, wherein the one or more processors are further configured to generate a measurement object of an evolved universal terrestrial radio access (MeasObjectEUTRA) interface within an information element that indicates that the enhanced measurement gap is active to the first UE and inactive to the second UE based on a bit, and the MeasObjectEUTRA is configured to further indicate measurements to be performed based on an inter-frequency of evolved universal terrestrial radio access (EUTRA) cells.

[00104] Example 7 includes the subject matter of any one of Examples 1 -6, including or omitting optional elements, wherein the one or more processors are further configured to generate a MeasGapConfig within an information element configured specify that the enhanced measurement gap, comprising a shorter measurement gap than the non-enhanced measurement gap, corresponds to different measurement gap patterns utilizing a gap offset for a UE measurement.

[00105] Example 8 includes the subject matter of any one of Examples 1 -7, including or omitting optional elements, wherein the first downlink communication is further configured to indicate a first set of component carriers that correspond to the enhanced measurement gap and a second set of component carriers that correspond to the non- enhanced measurement gap.

[00106] Example 9 is an apparatus configured to be employed in a user equipment (UE) comprising one or more processors configured to: process one or more radio resource control (RRC) signals of one or more communication chains corresponding to one or more component carriers (CCs); and process the one or more RRC signals and determine whether to apply an enhanced measurement gap based on the one or more RRC signals.

[00107] Example 10 includes the subject matter of Example 9, including or omitting optional elements, wherein the enhanced measurement gap comprises about two milliseconds or about three milliseconds.

[00108] Example 1 1 includes the subject matter of any one of Examples 9-10, including or omitting optional elements, wherein the processor component is further configured to apply the enhanced measurement gap comprising a shorter measurement gap duration than a non-enhanced measurement gap by generating cell measurements within the shorter measurement gap duration in response to residing in a synchronized network and an information element of the one or more RRC signals including an indication associated with the enhanced measurement gap.

[00109] Example 12 includes the subject matter of any one of Examples 9-1 1 , including or omitting optional elements, wherein the processor component is further configured to apply the enhanced measurement gap to a first component carrier for the cell measurements and apply the non-enhanced measurement gap to a second component carrier for the cell measurements based on the one or more RRC signals.

[00110] Example 13 includes the subject matter of any one of Examples 9-12, including or omitting optional elements, wherein the information element comprises a measurement configuration (MeasConfig) comprising at least one bit configured to indicate whether to apply the enhanced measurement gap to the cell measurements, and to perform measurements based on at least one of an inter-frequency or an inter- radio access technology (inter-RAT) mobility, and further comprising one or more other indications of the non-enhanced measurement gap or a measurement gap pattern.

[00111 ] Example 14 includes the subject matter of any one of Examples 9-13, including or omitting optional elements, wherein the information element comprises a measurement object of an evolved universal terrestrial radio access

(MeasObjectEUTRA) interface that indicates that the enhanced measurement gap is active, and whether the cell measurements are based on an inter-frequency of evolved universal terrestrial radio access (EUTRA) cells.

[00112] Example 15 includes the subject matter of any one of Examples 9-14, including or omitting optional elements, wherein the information element comprises a measurement gap configuration (MeasGapConfig) configured to specify a plurality of measurement gap patterns that comprise different gap offsets to be applied with the enhanced measurement gap for performing the cell measurements.

[00113] Example 16 includes the subject matter of any one of Examples 9-15, including or omitting optional elements, wherein the different gap offsets comprise a network controlled small gap with at least one of the plurality of measurement gap patterns that comprises a different measurement gap duration from other gap durations within the plurality of measurement gap patterns, and wherein the enhanced

measurement gap is applied at each measurement gap repetition/reception period (MGRP).

[00114] Example 17 includes the subject matter of any one of Examples 9-16, including or omitting optional elements, wherein the one or more processors are further configured to increase scheduling opportunities configured for generating

measurements of one or more synchronous connections on a synchronous network by applying the enhanced measurement gap to cell measurements based on an information element of the one or more RRC signals. [00115] Example 18 is a computer-readable medium comprising executable instructions that, in response to execution, cause one or more processors of an evolved NodeB (eNB) or a user equipment (UE) to perform operations, the operations comprising: determining, via the one or more processors, an indication of an enhanced measurement gap; and processing, via the one or more processors on a receive path or on a transmit path, the indication of the enhanced measurement gap to enable cell measurements, wherein the enhanced measurement gap comprises a shorter measurement gap than a non-enhanced measurement gap to enable the cell measurements.

[00116] Example 19 includes the subject matter of Example 18, including or omitting optional elements, wherein the processing the indication of the enhanced measurement gap is in response to identifying a synchronous network connection to a network device on a synchronous long term evolution (LTE) network.

[00117] Example 20 includes the subject matter of any one of Examples 18-19, including or omitting optional elements, wherein the operations further comprise:

applying the enhanced measurement gap to a first component carrier for the cell measurements and applying a non-enhanced measurement gap to a second

component carrier for the cell measurements based on a radio resource control (RRC) signal.

[00118] Example 21 includes the subject matter of any one of Examples 18-20, including or omitting optional elements, wherein the operations further comprise:

identifying whether a bit of an information element indicates whether to utilize the enhanced measurement gap or a non-enhanced measurement gap.

[00119] Example 22 includes the subject matter of any one of Examples 1 8-21 , including or omitting optional elements, wherein the enhanced measurement gap comprises a measurement gap length of about two milliseconds or about three milliseconds, and the non-enhanced measurement gap comprises about six

milliseconds.

[00120] Example 23 includes the subject matter of any one of Examples 1 8-22, including or omitting optional elements, wherein the operations further comprise:

identifying the indication of the enhanced measurement gap in an information element that comprises a measurement configuration (MeasConfig), or a measurement object of an evolved universal terrestrial radio access (MeasObjectEUTRA), comprising the indication. [00121 ] Example 24 includes the subject matter of any one of Examples 1 8-23, including or omitting optional elements, wherein the operations further comprise:

processing a measurement gap configuration (MeasGapConfig) configured to specify a plurality of measurement gaps patterns corresponding to different gap offsets that specify durations for each measurement gap repetition/reception period (MGRP) based on the indication of the enhanced measurement gap.

[00122] Example 25 includes the subject matter of any one of Examples 1 8-24, including or omitting optional elements, wherein the operations further comprise:

increasing scheduling opportunities configured for enabling the cell measurements at one or more synchronous connections on a synchronous network by applying the enhanced measurement gap for the cell measurements on a synchronous network band based on the indication in an information element of the RRC signal.

[00123] Example 26 is an apparatus to be employed by an evolved NodeB (eNB) or a user equipment (UE) to perform operations, the operations comprising: means for determining, via the one or more processors, an indication of an enhanced

measurement gap; and means for processing, via the one or more processors on a receive path or on a transmit path, the indication of the enhanced measurement gap to enable cell measurements, wherein the enhanced measurement gap comprises a shorter measurement gap than a non-enhanced measurement gap to enable the cell measurements.

[00124] Example 27 includes the subject matter of Example 26, including or omitting optional elements, wherein the processing the indication of the enhanced measurement gap is in response to identifying a synchronous network connection to a network device on a synchronous long term evolution (LTE) network.

[00125] Example 28 includes the subject matter of any one of Examples 26-27, including or omitting optional elements, wherein the operations further comprise: means for applying the enhanced measurement gap to a first component carrier for the cell measurements and applying a non-enhanced measurement gap to a second

component carrier for the cell measurements based on a radio resource control (RRC) signal.

[00126] Example 29 includes the subject matter of any one of Examples 26-28, including or omitting optional elements, wherein the operations further comprise: means for identifying whether a bit of an information element indicates whether to utilize the enhanced measurement gap or a non-enhanced measurement gap. [00127] Example 30 includes the subject matter of any one of Examples 26-29, including or omitting optional elements, wherein the enhanced measurement gap comprises a measurement gap length of about two milliseconds or about three milliseconds, and the non-enhanced measurement gap comprises about six

milliseconds.

[00128] Example 31 includes the subject matter of any one of Examples 26-30, including or omitting optional elements, wherein the operations further comprise: means for identifying the indication of the enhanced measurement gap in an information element that comprises a measurement configuration (MeasConfig), or a measurement object of an evolved universal terrestrial radio access (MeasObjectEUTRA), comprising the indication.

[00129] Example 32 includes the subject matter of any one of Examples 26-31 , including or omitting optional elements, wherein the operations further comprise: means for processing a measurement gap configuration (MeasGapConfig) configured to specify a plurality of measurement gaps patterns corresponding to different gap offsets that specify durations for each measurement gap repetition/reception period (MGRP) based on the indication of the enhanced measurement gap.

[00130] Example 33 includes the subject matter of any one of Examples 26-32, including or omitting optional elements, wherein the operations further comprise: means for increasing scheduling opportunities configured for enabling the cell measurements at one or more synchronous connections on a synchronous network by applying the enhanced measurement gap for the cell measurements on a synchronous network band based on the indication in an information element of the RRC signal.

[00131 ] Example 34 is a system configured to be employed in an evolved NodeB (eNB) comprising one or more processors configured to: generate a first downlink communication associated with a first user equipment (UE) to provide an enhanced measurement gap that is different from a non-enhanced measurement gap associated with a second UE, wherein the first UE and the second UE are communicatively coupled to the one or more processors, or the eNB, via a synchronous connection of a synchronous network; and communicate the enhanced measurement gap via one or more radio resource control (RRC) signals.

[00132] Example 35 includes the subject matter of Example 34, wherein the one or more processors are further configured to generate a measurement configuration (MeasConfig) with an indicator configured to indicate whether the enhanced

measurement gap is active or inactive for the first UE.

[00133] Example 36 includes the subject matter of any one of Examples 34-35, including or omitting optional elements, wherein the one or more processors are further configured to generate a measurement object of an evolved universal terrestrial radio access (MeasObjectEUTRA) interface within an information element that indicates that the enhanced measurement gap is active to the first UE and inactive to the second UE based on a bit, and the MeasObjectEUTRA is configured to further indicate measurements to be performed based on an inter-frequency of evolved universal terrestrial radio access (EUTRA) cells.

[00134] Example 37 includes the subject matter of any one of Examples 34-36, including or omitting optional elements, wherein the one or more processors are further configured to generate a MeasGapConfig within an information element configured specify that the enhanced measurement gap, comprising a shorter measurement gap than the non-enhanced measurement gap, corresponds to different measurement gap patterns utilizing a gap offset for a UE measurement or to different component carriers than the non-enhanced measurement gap.

[00135] It is to be understood that aspects described herein can be implemented by hardware, software, firmware, or any combination thereof. When implemented in software, functions can 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 a 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 medium, 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 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 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.

[00136] Various illustrative logics, logical blocks, modules, and circuits described in connection with aspects disclosed herein can be implemented or performed with a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other

programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform functions described herein. A general-purpose processor can be a microprocessor, but, in the alternative, processor can be any conventional processor, controller, microcontroller, or state machine. A processor can also be implemented as a combination of computing devices, for example, 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. Additionally, at least one processor can comprise one or more modules operable to perform one or more of the s and/or actions described herein.

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

[00138] Techniques described herein can be used for various wireless communication systems such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA and other systems. The terms "system" and "network" are often used interchangeably. A CDMA system can implement a radio technology such as Universal Terrestrial Radio Access (UTRA), CDMA1800, etc. UTRA includes Wideband-CDMA (W-CDMA) and other variants of CDMA. Further, CDMA1800 covers IS-1800, IS-95 and IS-856 standards. A TDMA system can implement a radio technology such as Global System for Mobile

Communications (GSM). An OFDMA system can implement a radio technology such as Evolved UTRA (E-UTRA), Ultra Mobile Broadband (UMB), IEEE 802.1 1 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.18, Flash-OFDM L , etc. UTRA and E-UTRA are part of Universal Mobile Telecommunication System (UMTS). 3GPP Long Term Evolution (LTE) is a release of UMTS that uses E-UTRA, which employs OFDMA on downlink and SC-FDMA on uplink. UTRA, E-UTRA, UMTS, LTE and GSM are described in documents from an organization named "3rd Generation Partnership Project" (3GPP). Additionally, CDMA1 800 and UMB are described in documents from an organization named "3rd Generation Partnership Project 2" (3GPP2). Further, such wireless communication systems can additionally include peer-to-peer (e.g., mobile-to-mobile) ad hoc network systems often using unpaired unlicensed spectrums, 802. xx wireless LAN, BLUETOOTH and any other short- or long- range, wireless communication techniques.

[00139] Single carrier frequency division multiple access (SC-FDMA), which utilizes single carrier modulation and frequency domain equalization is a technique that can be utilized with the disclosed aspects. SC-FDMA has similar performance and essentially a similar overall complexity as those of OFDMA system. SC-FDMA signal has lower peak-to-average power ratio (PAPR) because of its inherent single carrier structure. SC-FDMA can be utilized in uplink communications where lower PAPR can benefit a mobile terminal in terms of transmit power efficiency.

[00140] Moreover, various aspects or features described herein can 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.). Additionally, 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. Additionally, a computer program product can include a computer readable medium having one or more instructions or codes operable to cause a computer to perform functions described herein. [00141 ] Communications media embody 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., a carrier wave or other transport mechanism, and includes any information delivery or transport media. The term "modulated data signal" or signals refers to a signal that has one or more of its characteristics set or changed in such a manner as to encode information in one or more signals. By way of example, and not limitation, communication media include wired media, such as a wired network or direct-wired connection, and wireless media such as acoustic, RF, infrared and other wireless media.

[00142] Further, the actions of a method or algorithm described in connection with aspects disclosed herein can be embodied directly in hardware, in a software module executed by a processor, or a combination thereof. A software module can 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 processor, such that processor can read information from, and write information to, storage medium. In the alternative, storage medium can be integral to processor. Further, in some aspects, processor and storage medium can reside in an ASIC. Additionally, ASIC can reside in a user terminal. In the alternative, processor and storage medium can reside as discrete components in a user terminal. Additionally, in some aspects, the acts or actions of a method or algorithm can reside as one or any combination or set of codes and/or instructions on a machine-readable medium and/or computer readable medium, which can be incorporated into a computer program product.

[00143] The above description of illustrated embodiments of the subject disclosure, including what is described in the Abstract, is not intended to be exhaustive or to limit the disclosed embodiments to the precise forms disclosed. While specific embodiments and examples are described herein for illustrative purposes, various modifications are possible that are considered within the scope of such embodiments and examples, as those skilled in the relevant art can recognize.

[00144] In this regard, while the disclosed subject matter has been described in connection with various embodiments and corresponding Figures, where applicable, it is to be understood that other similar embodiments can be used or modifications and additions can be made to the described embodiments for performing the same, similar, alternative, or substitute function of the disclosed subject matter without deviating therefrom. Therefore, the disclosed subject matter should not be limited to any single embodiment described herein, but rather should be construed in breadth and scope in accordance with the appended claims below.

[00145] 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 disclosure. 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.