Patent Description:
Wireless cellular telecommunication networks include Radio Access Networks (RANs) that enable User Equipment (UE), such as smartphones, tablet computers, laptop computers, etc., to connect to a core network. In a cellular network, UEs typically communicate with base stations using radio channels corresponding to a licensed spectrum of radio frequencies.

Wireless mobile communication technology uses various standards and protocols to transmit data between a base station and a wireless mobile device. Wireless communication system standards and protocols can include the 3rd Generation Partnership Project (3GPP) long term evolution (LTE) (e.g., <NUM>) or new radio (NR) (e.g., <NUM>); the Institute of Electrical and Electronics Engineers (IEEE) <NUM> standard, which is commonly known to industry groups as worldwide interoperability for microwave access (WiMAX); and the IEEE <NUM> standard for wireless local area networks (WLAN), which is commonly known to industry groups as Wi-Fi. In 3GPP radio access networks (RANs) in LTE systems, the base station can include a RAN Node such as a Evolved Universal Terrestrial Radio Access Network (E-UTRAN) Node B (also commonly denoted as evolved Node B, enhanced Node B, eNodeB, or eNB) and/or Radio Network Controller (RNC) in an E-UTRAN, which communicate with a wireless communication device, known as user equipment (UE). In fifth generation (<NUM>) wireless RANs, RAN Nodes can include a <NUM> Node, NR node (also referred to as a next generation Node B or g Node B (gNB)).

RANs use a radio access technology (RAT) to communicate between the RAN Node and UE. RANs can include global system for mobile communications (GSM), enhanced data rates for GSM evolution (EDGE) RAN (GERAN), Universal Terrestrial Radio Access Network (UTRAN), and/or E-UTRAN, which provide access to communication services through a core network. Each of the RANs operates according to a specific 3GPP RAT. For example, the GERAN implements GSM and/or EDGE RAT, the UTRAN implements universal mobile telecommunication system (UMTS) RAT or other 3GPP RAT, the E-UTRAN implements LTE RAT, and NG-RAN implements <NUM> RAT. In certain deployments, the E-UTRAN may also implement <NUM> RAT.

UEs may measure the received power (signal quality) of the serving cell (i.e., the cell to which the UE is attached) and/or neighboring cells, and may report the measured values, in a measurement report, to the base station associated with the cell. In NR, the cell quality is measured by using Synchronization Signal Blocks (SSBs) in an SSB-based Radio Resource Management (RRM) Measurement Timing Configuration (SMTC) window. Additional details of NR measurements are shown and described in <NPL>). In particular, <FIG> of Sano et al. shows SSB and SMTC configuration examples. RRM measurement may include Reference Signal Received Power (RSRP), Reference Signal Received Quality (RSRQ), Received Signal Strength Indicator (RSSI), Reference Signal Time Difference (RSTD), or other measurements.

Sano, et al. also describes previous attempts at developing measurement gaps to streamline hardware by using the same RF transceiver (also referred to as an RF chain) for both (<NUM>) transmitting/receiving data in the serving cell and (<NUM>) measuring neighbor-cell quality or other component carriers (CCs). (In carrier aggregation (CA), each aggregated carrier is referred to as a CC. ) Thus, a gap is scheduled at the serving cell in which the UE does not receive or transmit anything. During the gap, the UE may switch the carrier frequency to that of the target cell, perform the signal quality measurements, and then switch back to the frequency of the serving cell. For example, <FIG> of Sano, et al. shows an example attempt at measurement gap configuration in NR, which implements configurable Measurement Gap Lengths (MGLs) and Measurement Gap Repetition Periods (MGRP) according to NR measurement gap patterns (<NUM> total) specified in 3GPP TS <NUM> (Rel-<NUM>). In LTE systems, the MGL is fixed.

As described in 3GPP TS <NUM> (Rel-<NUM>), short measurement gaps scheduled by the network are referred to as Network Controlled Small Gaps (NCSGs). NCSGs may be used by a cellular network to, for example, enhance the signal measurement processes by which a UE performs inter-frequency measurements. NCSG are intended to allow a UE to measure and do data transmission (or reception) in the time of a conventional MGL, which is based on the assumption that the UE may use some additional RF chain to conduct the measurement on the target frequency layer such that the UE can use a different RF chain for the data transmission/reception with the service cell.

A 3GPP Release <NUM> measurement gap enhancement work item was approved in RANP#89e (RP-<NUM>). An objective of the work item is to enhance aspects of the NCSG specification developed by RAN work group four (RAN4) and RAN work group two (RAN2). Specifically, the work item calls for the following RRM requirements for NCSG (i.e., RAN4 work items): requirements for Visible Interruption Length (VIL) for different numerologies in FR1 and FR2; specification of NCSG patterns, Measurement Length (ML), and Visible Interruption Repetition Period (VIRP); requirements for DL reception and UL transmission during ML, before start VIL and after end VIL; and measurement requirements with NCSG. Additionally, the work item calls for specification of applicability of NCSG patterns (i.e., RAN4 work items) and procedures and signaling for NCSG patterns (i.e., a RAN2 work item). Thus, certain additional details for NCSG design in Release <NUM> NR are described in this disclosure.

<CIT> of INTEL discloses configuration of NCSG having VIL, ML and VIRP.

<FIG> shows a network <NUM> having a user equipment UE <NUM> capable of measuring signal levels on one or more frequencies in designated measurement gaps in accordance with one or more embodiments. Network <NUM> may comprise a wireless wide area network (WWAN) operating in accordance with a Fifth Generation (<NUM>) New Radio (NR) standards, although the scope of the claimed subject matter is not limited in this respect.

UE <NUM> is illustrated as smartphones (e.g., handheld touchscreen mobile computing devices connectable to one or more cellular networks), but may also comprise any mobile or non-mobile computing device, such as consumer electronics devices, cellular phones, smartphones, feature phones, tablet computers, wearable computer devices, personal digital assistants (PDAs), pagers, wireless handsets, desktop computers, laptop computers, in-vehicle infotainment (IVI), in-car entertainment (ICE) devices, an Instrument Cluster (IC), head-up display (HUD) devices, onboard diagnostic (OBD) devices, dashtop mobile equipment (DME), mobile data terminals (MDTs), Electronic Engine Management System (EEMS), electronic/engine control units (ECUs), electronic/engine control modules (ECMs), embedded systems, microcontrollers, control modules, engine management systems (EMS), networked or "smart" appliances, MTC devices, M2M, IoT devices, and/or the like.

UE <NUM> may be configured to connect, for example, communicatively couple, with an access node or radio access node (RAN). RAN may be an NG RAN and include a gNB <NUM>. In network <NUM>, UE <NUM> may be communicatively coupled via a radio link <NUM> with a serving cell embodied as gNB <NUM>, which may also function as a primary cell (PCell) in some scenarios such as dual connectivity. UE <NUM> utilize connections (or channels) (e.g., radio link <NUM>), each of which comprises a physical communications interface or layer. In this example, radio link <NUM> implements a NR protocol.

A RAN can include one or more AN nodes, such as a gNB <NUM> that enables a radio link <NUM> and a gNB <NUM> that enables a radio link <NUM>. As used herein, the terms "access node," "access point," or the like may describe equipment that provides the radio baseband functions for data and/or voice connectivity between a network and one or more users. These access nodes can be referred to as BS, gNBs, RAN nodes, eNBs, NodeBs, RSUs, TRxPs or TRPs, and so forth, and can comprise ground stations (e.g., terrestrial access points) or satellite stations providing coverage within a geographic area (e.g., a cell). As used herein, the term "NG RAN node" or the like may refer to a RAN node that operates in an NR or SG system (for example, a gNB), and the term "E-UTRAN node" or the like may refer to a RAN node that operates in an LTE or <NUM> system (e.g., an eNB). According to various embodiments, the RAN nodes may be implemented as one or more of a dedicated physical device such as a macrocell base station, and/or a low power (LP) base station for providing femtocells, picocells or other like cells having smaller coverage areas, smaller user capacity, or higher bandwidth compared to macrocells.

During measurement gaps designated by gNB <NUM>, UE <NUM> will measure downlink (DL) frequency or frequencies of one or neighbor or target cells deployed on neighbor gNB <NUM> via radio link <NUM>, which may function as a primary secondary cell (PSCell) in some scenarios. In addition, there may be one or more secondary cells such as secondary cell (SCell) or gNB <NUM> on which UE <NUM> may obtain DL measurements via radio link <NUM> during a designated measurement gap period. During the measurement gap period, UE <NUM> may measure RSRP and then provide a measurement report to gNB <NUM>.

Measurement gap configurations may be specified and signaled via dedicated signaling for UE <NUM> such that no downlink or uplink scheduling between UE <NUM> and gNB <NUM> occurs to allow the UE to perform measurements on the one or more given frequencies. In some embodiments, the neighbor cell or gNB <NUM> may comprise a small cell or remote radio head (RRH) coupled to gNB <NUM> of the serving cell. In such embodiments, the neighbor cell or gNB <NUM> may comprise a micro cell, a pico cell, a femto cell, and so on. In other embodiments, neighbor cell or gNB <NUM> may comprise or otherwise be connected with a different eNB than the serving cell or gNB <NUM>. The measurement results obtained by UE <NUM> for the one or more neighbors cells of gNB <NUM> or gNB <NUM> allow gNB <NUM> to determine whether to handover UE <NUM> to a new cell or eNB, for example if the signal levels with a neighboring cell are better than the signal levels for the serving cell of gNBs <NUM>.

The measurement gap configuration is provided by network <NUM> to UE <NUM> via the serving cell or gNB <NUM>. In accordance with one or more embodiments, UE <NUM> may indicate to network <NUM> the radio-frequency (RF) capability and the band capability of UE <NUM> so that network <NUM> can configure cell-group specific measurement for carrier aggregation or dual connectivity to reduce measurement delay and/or increase the downlink date rate if UE <NUM> has two or more RF chains and is capable of operating on multiple frequency bands for the two or more RF chains. For example, <FIG> shows a detail view of circuitry <NUM> of UE <NUM> including multiple RF chains <NUM> operating on multiple frequency bands. RF chains <NUM> may be coupled to multiple antennas, such as antenna <NUM>, and RF chains <NUM> may be controlled by a processor <NUM>. In another embodiment, one or more of the RF chains may be capable of operating on one or more frequency bands to transmit and/or receive data in the uplink (UL) and/or the downlink.

In this example, since UE <NUM> has more than one RF chain, UE <NUM> is capable of using both RF chains for gap measurements to reduce measurement delay and/or to increase spectrum efficiency. In other words, some UEs, such as UEs that have multiple radio circuits or radio chains, may thus be capable of concurrently communicating on multiple frequency bands, in which case a conventional measurement gap may not be needed. However, even though a UE with multiple radios may not require measurement gaps to perform measurements, communication gaps may still be used or needed in certain situations, such as to perform RF tuning in the physical layer. These short gaps may be scheduled by the network and may be referred to as NCSGs. In furtherance of using a NCSG, UE <NUM> may indicate is measurement gap capability to network <NUM>, and network <NUM> may configure UE <NUM> to utilize a selected NCSG pattern, as shown in and described with respect to <FIG>.

<FIG> shows two general designs for NCSG patterns <NUM>, which include a synchronous case <NUM> and an asynchronous case <NUM>. In synchronous case <NUM>, a propagation delay <NUM> is shown as a timing offset between a DL timing <NUM> and UL timing <NUM>. In asynchronous case <NUM>, a delay <NUM> is also shown because serving cell A timing <NUM> and serving cell B timing <NUM> are maintained separately from each other.

Each NCSG pattern consists of four components: VIL1, ML, VIL2, and VIRP. VIL1 is the visible interruption length before measurement. VIL1 is provided due to the fact that UE needs time to configure the additional RF chain for measurement. During VIL1, the UE is not expected to transmit or receive any data on corresponding serving cells. ML is the measurement length. During ML, the UE is expected to transmit and receive data on the corresponding serving carrier. VIL2 is the visible interruption length after measurement. VIL2 is provided due to the fact that the UE needs to switching off the spare RF chain after measurement. During VIL2, the UE is not expected to transmit or receive any date on corresponding serving cells. VIRP is the visible interruption repetition period.

In one embodiment, NCSG can be configured per UE. For example, each CC has the same NCSG configuration applied to the CC.

In other embodiments, NCSG can be configured per carrier, as shown in a bandwidth timing diagram <NUM> of <FIG>. In the example bandwidth timing diagram <NUM>, a UE (not shown) is configured with two CCs, including a CC1-RF1 <NUM> and a CC2-RF2 <NUM>. A CC may have a bandwidth of <NUM>, <NUM>, <NUM>, <NUM>, <NUM> or <NUM> and a maximum of five CCs can be aggregated, and therefore, a maximum aggregated bandwidth is <NUM>. In frequency division duplexing (FDD) systems, the number of aggregated carriers can be different for DL and UL, where the number of UL CCs is equal to or lower than the number of DL CCs. In some cases, individual CCs can have a different bandwidth than other CCs. In TDD systems, the number of CCs as well as the bandwidths of each CC is usually the same for DL and UL.

Since CC1-RF1 <NUM> and CC2-RF2s <NUM> are displaced from each other in terms of a <NUM> bandwidth <NUM>, they are allocated to separate RF chains, where "RF1" corresponds to a first RF chain and "RF2" corresponds to a second RF chain. The first RF chain is configured to handle the data for the first CC. The second RF chain is configured to handle the data for the second CC. Each may include a different NCSG configuration.

If a measurement object is configured for the UE to measure a block outside the CC bandwidth, e.g., outside CC1-RF1 <NUM>, there are two options as follows. One option is that the UE can enlarge the bandwidth of CC1-RF1 <NUM> to cover the target access block, as shown in broken lines. This option depends on how close the target access block is away from CC1-RF1 <NUM> in terms of bandwidth such that CC1-RF1 <NUM> can cover the target access block. Also, in this option, there may not be any impact on CC2-RF2 <NUM>.

The other option is that the UE can enable another RF chain, e.g., a third RF chain, to cover the target access block.

<FIG> shows another embodiment of a bandwidth timing diagram <NUM> in which NCSG is configured per frequency range. For example, <NUM> NR may include two different frequency ranges, labeled FR1 <NUM> and FR2 <NUM>. Frequency Range <NUM> may include frequency bands operating in sub-<NUM> frequencies, some of which are bands that may be used by previous standards and may potentially be extended to cover new spectrum offerings from <NUM> to <NUM>. Frequency Range <NUM> (FR2) may include frequency bands from <NUM> to <NUM>. Bands in the millimeter wave (mmWave) range of FR2 may have smaller coverage but potentially higher available bandwidth than bands in the FR1. Skilled persons will recognize these frequency ranges, which are provided by way of example, may change from time to time or from region to region. In some embodiments, a UE may include a separate baseband module for each frequency range. For that type of UE, operation on one baseband will not impact operation on the other one.

<FIG> shows another embodiment of a bandwidth timing diagram <NUM> in which NCSG is configured per bandwidth part (BWP). In the example bandwidth timing diagram <NUM>, a UE (not shown) is configured with two BWPs, including a BWP1-RF1 <NUM> and a BWP2-RF1 <NUM>, which are allocated to the same RF chain. A UE can be configured with up to four different BWPs per CC. Accordingly, <FIG> shows an example in which BWP1-RF1 <NUM> and BWP2-RF1 <NUM> are both allocated to a CC1 <NUM>. When a UE is working on BWP1-RF1 <NUM>, the UE may use an NCSG to measure the target SSB by enlarging BWP1-RF1 <NUM> in the frequency domain. Another option is to activate another RF chain.

In other embodiments, NCSG may be configured per band or per band combination. Per band means a UE can report different a VIL2 length (or VIL1 length, ML length, etc.) on different band, e.g. <NUM> on band <NUM> and <NUM> on band <NUM>. Per band-combination means a UE can report different VIL2 length (or VIL1 length, ML length, etc.) on different band combination, e.g. <NUM> when UE is working on Band <NUM>+<NUM> CA or DC, and <NUM> when UE is working on Band <NUM>+<NUM> CA or DC.

In yet another embodiment, NCSG is also configurable per feature set. As described in 3GPP TS <NUM>, a fallback band combination is a band combination that would result from another band combination by releasing at least one SCell or uplink configuration of SCell, or SCG. An intra-band non-contiguous band combination is not considered to be a fallback band combination of an intra-band contiguous band combination. A fallback per band feature set is feature set per band that has same or lower values than the reported values from the reported feature set per band for a given band. A fallback per CC feature set is a feature set per CC that has lower value of UE supported MIMO layers and BW while keeping the numerology and other parameters the same from the reported feature set per CC for a given carrier per band. For example, <FIG> shows a bandwidth timing diagram <NUM> including a CC1-RF1 <NUM>, a CC2-RF2 <NUM>, and a CC3-RF3 <NUM>. There is no spare RF chain to perform a measurement. Accordingly, the UE can fallback to a per-UE measurement gap operation so that the measurement gap applies to all the CCs.

Finally, NCSG may be configured as any combination of the above-described embodiments: per carrier; per UE; per frequency range; per BWP; per band or per band combination; or per feature set (TS38. <NUM>) (per band or per band combination).

This disclosure also describes embodiments relating to NCSG configuration applicability. A first option is that NCSG can be configured on the carrier (or BWP) on which there is not any other configured measurement gap. For instance, if a UE does not support per-FR gap or per-CC gap, then NCSG can only be configured when there is not any other configured measurement gap, unless UE can support parallel measurement gap patterns.

Per-FR gap means that a UE has a separate baseband module per each FR, so when the UE is doing a measurement on a target carrier in FR1, then FR2 need not have a gap. Data between the UE and base station is possible in FR2, for example. If a UE supports per-FR gap, then NCSG can only be configured in the frequency range in which there is not any other configured measurement gap, unless UE can support parallel measurement gap patterns.

Pre-CC gap means an NCSG is allowed on certain carriers (instead of all carriers in a frequency range). If a UE supports per-CC gap, then NCSG can only be configured on CCs on which there is not any other configured measurement gap, unless UE can support parallel measurement gap patterns.

A second option is that NCSG can be configured together with other (i.e., legacy) measurement gaps. <FIG> shows an example diagram <NUM> in which a UE <NUM> is working on a first carrier <NUM>. Since a second carrier <NUM> is close to first carrier <NUM> (i.e., close in terms of frequency domain), UE <NUM> can measure second carrier <NUM> by enlarging bandwidth of first carrier <NUM>. Thus, an NCSG <NUM> in first carrier <NUM> is used for measuring an SSB <NUM> in second carrier <NUM>. However, UE <NUM> is configured with a Positioning Reference Signals (PRS) PRS <NUM> measurement object on a third carrier <NUM>. Since there is no spare RF chain, UE <NUM> includes a regular gap (non-NCSG) to measure target PRS <NUM>.

In some embodiments, there are interruptions due to NCSG. During NCSG, a UE is allowed to cause an interruption during VIL1 and VIL2. Thus, the UE is not expected to transmit or receive data on the corresponding serving cells. Outside of these windows, however, a UE can transmit or receive data with a serving cell. The general design of the number of slots interrupted is summarized in the following paragraph, which is then followed by an example shown and described with reference to <FIG>.

For DL, one additional slot interruption is allowed for both VIL1 and VIL2 in asynchronous cases. For UL, if VIL1 = VIL2 in synchronous cases, then an additional slot interruption is allowed for both VIL1 and VIL2 in asynchronous cases; if VIL2 = VIL1 + <NUM> slot in synchronous cases, then an additional slot interruption is allowed only for VIL1 in asynchronous cases. In other words, even in synchronous cases, VIL2 on uplink would have one more slot than VIL1, e.g., in <NUM>. Thus, in asynchronous cases, there is additional slot in VIL1, but VIL2 would be the same.

<FIG> shows that on asynchronous CCs, one more slot interruption in VIL1 are allowed. This is attributable to different timings alignment of the different CCs. Thus, in an example bandwidth timing diagram <NUM> of <FIG>, if a measurement gap <NUM> is configured as shown from a first slot <NUM> labeled i+n to another slot <NUM> labeled i+n for service cell A, then a UE will perform the measurement in this measurement gap <NUM>. Due to RF chain operation and timing differences, VIL1 <NUM> occupies two slots of serving cell B such that a second slot <NUM> labeled j+<NUM> and a third slot <NUM> labeled j+<NUM> are interrupted. For synchronous case (not shown), there is no additional slot that is interrupted during VIL1.

<FIG> also shows that VIL2 interrupts two slots, although in some cases (noted above), an additional slot in not necessary for VIL2. For instance, in some UE implementations, the RF switching time could be <NUM>. And for <NUM> cases, the <NUM> time corresponds to one slot. Considering timing advance, interruption on an additional slot on uplink should be allowed even in synchronous cases. Total interruption on uplink in synchronous cases would be two slots. Thus, even in asynchronous cases, the switching time (<NUM>) at most covers two slots. The difference from synchronous cases is that in asynchronous cases there is more overlapping on the next second slot. And interruption on the whole slot is allowed. The total interruption would still be two slots in uplink in asynchronous case.

If a UE supports and has being configured with NCSG, during RRM measurement (RSRP/RSRQ/RSSI/RSTD, and etc.) on SCC, UE shall not make any autonomous interruptions outside of the configured gap patterns.

In terms of interruption applicability, there are two options. A first option depends on UE capability. If UE supports per-FR gap, then interruption due to NCSG is only allowed within the frequency range in which NCSG is configured. A second option depends on NCSG configuration. If NCSG is per-CC or per-band configured, then interruption due to NCSG is only allowed on the corresponding CCs and band.

The design of VIL1 includes options for the length of VIL1 and the minimum value for VIL1.

In terms of the length of VIL1, there are three options. A first option is that the length of VIL1 is defined as fixed value (such as <NUM>, <NUM>, or other fixed length), rounding up to number of slot according different numerologies. A second option is to introduce a new UE capability indicating a length of VIL1 (same or different capabilities for intra-band and inter-band). The new UE capability may be indicated per band or per band combination. A third option depends on UE capability of an information element (IE) called SRS-SwitchingTimeNR, which is indicated from UE to the network to signal how much time is used to perform RF tuning to another carrier. The SRS-SwitchingTimeNR signaling corresponds to a number of slots for VIL1.

In terms of the minimum value for VIL1, there are two options. A first option is to define in slot level, i.e., the minimum number of slots is one in both uplink and downlink. When there is partial overlap, the overlapped symbol is interrupted. A second option is to define in symbol level, i.e., the minimum number of symbols is one in both uplink and downlink. Accordingly, symbols in a slot that are not interrupted (e.g., a half slot interruption) could still be used to support transmission and reception.

The design of VIL2 also includes options for the length of VIL2 and the minimum value for VIL2. The design is similar to that of VIL1, but it includes one more symbol in the uplink as explained below.

In terms of the length of VIL2, there are three options. A first option is when VIL2 is defined as fixed value (such as <NUM>, <NUM>, and etc.), rounding up to a number of slots according different numerologies. A second option is to introduce a new UE capability indicating length of VIL2 (same or different capabilities for intra-band and inter-band). The new UE capability may be indicated per band or per band combination. A third option depends on UE capability of SRS-SwitchingTimeNR.

In terms of the minimum number of slots in VIL2, there are two options. A first option is to define VIL2 at a slot level. For instance, there may be one slot for DL and one slot for UL (for small timing advance). Alternatively, there may be one slot for DL and two slots for UL (if the timing advance exceeds CP length). A second option is to define VIL2 at a symbol level. For instance, the is one symbol for DL and <NUM>+x symbols for UL, where x is determined by how much timing advance is greater than CP.

The design of ML includes two options. A first option for the total measurement gap length is to employ the same length of the existing measurement gap patterns. Therefore, ML = MGL - VIL1 - VIL2, where MGL is defined in 3GPP TS <NUM>, table <NUM>. <NUM>-<NUM> for different gap patterns. For example, for UE indicating VIL1 = VIL2 = <NUM>, then the ML = <NUM>. A second option is to introduce a new ML separately from MGL in existing MG patterns. For example, ML is specified at a slot level, e.g., ML = <NUM>, <NUM>,. Alternatively, ML is specified at a symbol level, e.g., ML = x symbols.

NR supports multiple NCSG patterns with different VIRP. A first option is to follow existing MGRP: <NUM>, <NUM>, <NUM>, and <NUM> for baseline support; and <NUM>, <NUM>, or larger for a UE supporting new positioning gap patterns. A second option is to introduce new VIRP separately from existing MGRP. Accordingly, VIRP can be flexibly configured, such as VIRP = <NUM>, <NUM>,. <NUM>, and so forth.

<FIG> shows a process, performed by a user equipment (UE) for a <NUM> network, of configuring the UE to perform a measurement during an NCSG. In block <NUM>, process <NUM> entails transmitting to the <NUM> network a UE capability indicating a length of one or both the VIL1 and the VIL2. For example, the length can be indicated in a Radio Resource Control (RRC) message as a UE capability such as SRS-SwitchingTimeNR.

In block <NUM>, process <NUM> entails receiving NCSG pattern information indicating the NCSG. The VIL1 and the VIL2 indicate when the UE is not expected to transmit and receive data on a serving carrier, the ML indicates when the UE is expected to transmit and receive data on the serving carrier, and the VIRP indicates a period in which to repeat the NCSG.

<FIG> is a block diagram illustrating components <NUM>, according to some example embodiments, able to read instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and perform any one or more of the methodologies discussed herein. Specifically, <FIG> shows a diagrammatic representation of hardware resources <NUM> including one or more processors <NUM> (or processor cores), one or more memory/storage devices <NUM>, and one or more communication resources <NUM>, each of which may be communicatively coupled via a bus <NUM>. For embodiments where node virtualization (e.g., NFV) is utilized, a hypervisor <NUM> may be executed to provide an execution environment for one or more network slices/sub-slices to utilize the hardware resources <NUM>.

Instructions <NUM> may comprise software, a program, an application, an applet, an app, or other executable code for causing at least any of the processors <NUM> to perform any one or more of the methodologies discussed herein. The instructions <NUM> may reside, completely or partially, within at least one of the processors <NUM> (e.g., within the processor's cache memory), the memory/storage devices <NUM>, or any suitable combination thereof. Furthermore, any portion of the instructions <NUM> may be transferred to the hardware resources <NUM> from any combination of the peripheral devices <NUM> or the databases <NUM>. Accordingly, the memory of the processors <NUM>, the memory/storage devices <NUM>, the peripheral devices <NUM>, and the databases <NUM> are examples of computer-readable and machine-readable media.

<FIG> illustrates example components of a device <NUM> in accordance with some embodiments. In some embodiments, the device <NUM> may include application circuitry <NUM>, baseband circuitry <NUM>, Radio Frequency (RF) circuitry (shown as RF circuitry <NUM>), front-end module (FEM) circuitry (shown as FEM circuitry <NUM>), one or more antennas <NUM>, and power management circuitry (PMC) (shown as PMC <NUM>) coupled together at least as shown. The components of the illustrated device <NUM> may be included in a UE or a RAN node. In some embodiments, the device <NUM> may include fewer elements (e.g., a RAN node may not utilize application circuitry <NUM>, and instead include a processor/controller to process IP data received from an EPC). In some embodiments, the device <NUM> may include additional elements such as, for example, memory/storage, display, camera, sensor, or input/output (I/O) interface. In other embodiments, the components described below may be included in more than one device (e.g., said circuitries may be separately included in more than one device for Cloud-RAN (C-RAN) implementations).

The baseband circuitry <NUM> may include one or more baseband processors or control logic to process baseband signals received from a receive signal path of the RF circuitry <NUM> and to generate baseband signals for a transmit signal path of the RF circuitry <NUM>. The baseband circuitry <NUM> may interface with the application circuitry <NUM> for generation and processing of the baseband signals and for controlling operations of the RF circuitry <NUM>. For example, in some embodiments, the baseband circuitry <NUM> may include a third generation (<NUM>) baseband processor (<NUM> baseband processor <NUM>), a fourth generation (<NUM>) baseband processor (<NUM> baseband processor <NUM>), a fifth generation (<NUM>) baseband processor (<NUM> baseband processor <NUM>), or other baseband processor(s) <NUM> for other existing generations, generations in development or to be developed in the future (e.g., second generation (<NUM>), sixth generation (<NUM>), etc.). The baseband circuitry <NUM> (e.g., one or more of baseband processors) may handle various radio control functions that enable communication with one or more radio networks via the RF circuitry <NUM>. In other embodiments, some or all of the functionality of the illustrated baseband processors may be included in modules stored in the memory <NUM> and executed via a Central Processing Unit (CPU <NUM>). The radio control functions may 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 <NUM> may include Fast-Fourier Transform (FFT), precoding, or constellation mapping/demapping functionality. In some embodiments, encoding/decoding circuitry of the baseband circuitry <NUM> may include convolution, tail-biting convolution, turbo, Viterbi, or Low Density Parity Check (LDPC) encoder/decoder functionality. Embodiments of modulation/demodulation and encoder/decoder functionality are not limited to these examples and may include other suitable functionality in other embodiments.

In some embodiments, the baseband circuitry <NUM> may include a digital signal processor (DSP), such as one or more audio DSP(s) <NUM>. The one or more audio DSP(s) <NUM> may include elements for compression/decompression and echo cancellation and may include other suitable processing elements in other embodiments. Components of the baseband circuitry may 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 <NUM> and the application circuitry <NUM> may be implemented together such as, for example, on a system on a chip (SOC).

For example, in some embodiments, the baseband circuitry <NUM> may support communication with an evolved universal terrestrial radio access network (EUTRAN) or other wireless metropolitan area networks (WMAN), a wireless local area network (WLAN), or a wireless personal area network (WPAN).

The RF circuitry <NUM> may enable communication with wireless networks using modulated electromagnetic radiation through a non-solid medium. The RF circuitry <NUM> may include a receive signal path which may include circuitry to down-convert RF signals received from the FEM circuitry <NUM> and provide baseband signals to the baseband circuitry <NUM>. The RF circuitry <NUM> may also include a transmit signal path which may include circuitry to up-convert baseband signals provided by the baseband circuitry <NUM> and provide RF output signals to the FEM circuitry <NUM> for transmission.

In some embodiments, the receive signal path of the RF circuitry <NUM> may include mixer circuitry <NUM>, amplifier circuitry <NUM> and filter circuitry <NUM>. In some embodiments, the transmit signal path of the RF circuitry <NUM> may include filter circuitry <NUM> and mixer circuitry <NUM>. The RF circuitry <NUM> may also include synthesizer circuitry <NUM> for synthesizing a frequency for use by the mixer circuitry <NUM> of the receive signal path and the transmit signal path. In some embodiments, the mixer circuitry <NUM> of the receive signal path may be configured to down-convert RF signals received from the FEM circuitry <NUM> based on the synthesized frequency provided by synthesizer circuitry <NUM>. The amplifier circuitry <NUM> may be configured to amplify the down-converted signals and the filter circuitry <NUM> may 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 may be provided to the baseband circuitry <NUM> for further processing. In some embodiments, the output baseband signals may be zero-frequency baseband signals, although this is not a requirement. In some embodiments, the mixer circuitry <NUM> of the receive signal path may comprise passive mixers, although the scope of the embodiments is not limited in this respect.

In some embodiments, the mixer circuitry <NUM> of the transmit signal path may be configured to up-convert input baseband signals based on the synthesized frequency provided by the synthesizer circuitry <NUM> to generate RF output signals for the FEM circuitry <NUM>. The baseband signals may be provided by the baseband circuitry <NUM> and may be filtered by the filter circuitry <NUM>.

In some embodiments, the mixer circuitry <NUM><NUM> of the receive signal path and the mixer circuitry <NUM> of the transmit signal path may include two or more mixers and may be arranged for quadrature downconversion and upconversion, respectively. In some embodiments, the mixer circuitry <NUM> of the receive signal path and the mixer circuitry <NUM> of the transmit signal path may include two or more mixers and may be arranged for image rejection (e.g., Hartley image rejection). In some embodiments, the mixer circuitry <NUM> of the receive signal path and the mixer circuitry <NUM> may be arranged for direct downconversion and direct upconversion, respectively. In some embodiments, the mixer circuitry <NUM> of the receive signal path and the mixer circuitry <NUM> of the transmit signal path may be configured for super-heterodyne operation.

In some embodiments, the synthesizer circuitry <NUM> may be a fractional-N synthesizer or a fractional N/N+<NUM> synthesizer, although the scope of the embodiments is not limited in this respect as other types of frequency synthesizers may be suitable. For example, synthesizer circuitry <NUM> may be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer comprising a phase-locked loop with a frequency divider.

The synthesizer circuitry <NUM> may be configured to synthesize an output frequency for use by the mixer circuitry <NUM> of the RF circuitry <NUM> based on a frequency input and a divider control input. In some embodiments, the synthesizer circuitry <NUM> may be a fractional N/N+<NUM> synthesizer.

Divider control input may be provided by either the baseband circuitry <NUM> or the application circuitry <NUM> (such as an applications processor) depending on the desired output frequency. In some embodiments, a divider control input (e.g., N) may be determined from a look-up table based on a channel indicated by the application circuitry <NUM>.

Synthesizer circuitry <NUM> of the RF circuitry <NUM> may include a divider, a delay-locked loop (DLL), a multiplexer and a phase accumulator. In some embodiments, the divider may be a dual modulus divider (DMD) and the phase accumulator may be a digital phase accumulator (DPA). In some embodiments, the DMD may be configured to divide the input signal by either N or N+<NUM> (e.g., based on a carry out) to provide a fractional division ratio. In some example embodiments, the DLL may 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 may 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.

In some embodiments, the synthesizer circuitry <NUM> may be configured to generate a carrier frequency as the output frequency, while in other embodiments, the output frequency may be a multiple of the carrier frequency (e.g., twice the carrier frequency, four times the carrier frequency) and 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 may be a LO frequency (fLO). In some embodiments, the RF circuitry <NUM> may include an IQ/polar converter.

The FEM circuitry <NUM> may include a receive signal path which may include circuitry configured to operate on RF signals received from one or more antennas <NUM>, amplify the received signals and provide the amplified versions of the received signals to the RF circuitry <NUM> for further processing. The FEM circuitry <NUM> may also include a transmit signal path which may include circuitry configured to amplify signals for transmission provided by the RF circuitry <NUM> for transmission by one or more of the one or more antennas <NUM>. In various embodiments, the amplification through the transmit or receive signal paths may be done solely in the RF circuitry <NUM>, solely in the FEM circuitry <NUM>, or in both the RF circuitry <NUM> and the FEM circuitry <NUM>.

The FEM circuitry <NUM> may include a receive signal path and a transmit signal path. The receive signal path of the FEM circuitry <NUM> may include an LNA to amplify received RF signals and provide the amplified received RF signals as an output (e.g., to the RF circuitry <NUM>). The transmit signal path of the FEM circuitry <NUM> may include a power amplifier (PA) to amplify input RF signals (e.g., provided by the RF circuitry <NUM>), and one or more filters to generate RF signals for subsequent transmission (e.g., by one or more of the one or more antennas <NUM>).

The PMC <NUM> may often be included when the device <NUM> is capable of being powered by a battery, for example, when the device <NUM> is included in a UE.

<FIG> shows the PMC <NUM> coupled only with the baseband circuitry <NUM>. However, in other embodiments, the PMC <NUM> may be additionally or alternatively coupled with, and perform similar power management operations for, other components such as, but not limited to, the application circuitry <NUM>, the RF circuitry <NUM>, or the FEM circuitry <NUM>.

If there is no data traffic activity for an extended period of time, then the device <NUM> may transition off to an RRC_Idle state, where it disconnects from the network and does not perform operations such as channel quality feedback, handover, etc. The device <NUM> goes into a very low power state and it performs paging where again it periodically wakes up to listen to the network and then powers down again. The device <NUM> may not receive data in this state, and in order to receive data, it transitions back to an RRC_Connected state.

For example, processors of the baseband circuitry <NUM>, alone or in combination, may be used to execute Layer <NUM>, Layer <NUM>, or Layer <NUM> functionality, while processors of the application circuitry <NUM> may utilize data (e.g., packet data) received from these layers and further execute Layer <NUM> functionality (e.g., transmission communication protocol (TCP) and user datagram protocol (UDP) layers).

<FIG> illustrates example interfaces <NUM> of baseband circuitry in accordance with some embodiments. As discussed above, the baseband circuitry <NUM> of <FIG> may comprise <NUM> baseband processor <NUM>, <NUM> baseband processor <NUM>, <NUM> baseband processor <NUM>, other baseband processor(s) <NUM>, CPU <NUM>, and a memory <NUM> utilized by said processors. As illustrated, each of the processors may include a respective memory interface <NUM> to send/receive data to/from the memory <NUM>.

For one or more embodiments, at least one of the components set forth in one or more of the preceding figures may be configured to perform one or more operations, techniques, processes, and/or methods as set forth in the Example Section below. For example, the baseband circuitry as described above in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth below. For another example, circuitry associated with a UE, base station, network element, etc. as described above in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth below in the example section.

Embodiments and implementations of the systems and methods described herein may include various operations, which may be embodied in machine-executable instructions to be executed by a computer system. A computer system may include one or more general-purpose or special-purpose computers (or other electronic devices). The computer system may include hardware components that include specific logic for performing the operations or may include a combination of hardware, software, and/or firmware.

It should be recognized that the systems described herein include descriptions of specific embodiments. These embodiments can be combined into single systems, partially combined into other systems, split into multiple systems or divided or combined in other ways. In addition, it is contemplated that parameters, attributes, aspects, etc. of one embodiment can be used in another embodiment. The parameters, attributes, aspects, etc. are merely described in one or more embodiments for clarity, and it is recognized that the parameters, attributes, aspects, etc. can be combined with or substituted for parameters, attributes, aspects, etc. of another embodiment unless specifically disclaimed herein.

Claim 1:
A method, performed by a user equipment, UE, for a <NUM> network, of configuring the UE to perform a measurement during a network controlled small gap, NCSG, the NCSG including a first visible interruption length, VIL1, a measurement length, ML, a second visible interruption length, VIL2, and a visible interruption repetition period, VIRP, the method comprising:
transmitting to the <NUM> network a UE capability indicating a length of one or both the VIL1 and the VIL2, in which the UE capability is indicated in an SRS-SwitchingTimeNR information element; and
receiving NCSG pattern information indicating the NCSG, in which the VIL1 and the VIL2 indicate when the UE is not expected to transmit and receive data on a serving carrier, the ML indicates when the UE is expected to transmit and receive data on the serving carrier, and the VIRP indicates a period in which to repeat the NCSG, in which the VIRP includes a set of periods matching those of Measurement Gap Repetition Periods, MGRP, including <NUM>, <NUM>, <NUM>, and <NUM>.