Patent Description:
Third Generation Partnership Project (3GPP) long term evolutions (LTE) includes carrier aggregation (CA) that enables a user equipment (UE) to transmit/receive information via multiple cells (referred to as secondary cells or SCell(s)) from multiple carrier frequencies to benefit from the existing non-contiguous and contiguous carriers. In CA terminology, the PCell is the cell towards which the UE established the radio resource control (RRC) connection or did handover to. In CA, cells are aggregated on the medium access control (MAC)-level. The MAC gets grants for a certain cell and multiplexes data from different bearers to one transport block being sent on that cell. The MAC controls the process. An example is illustrated in <FIG>.

<FIG> is a block diagram illustrating an example of carrier aggregation. In the illustrated example, the MAC layer multiplexes multiple bearers from the packet data convergence protocol (PDCP) and radio link control (RLC) layers for Cell1, Cell2, and Cell3.

SCells can be added (or configured) for the UE using RRC signaling (e.g., RRCConnectionReconfiguration), which takes on the order of <NUM> of milliseconds. A cell that is configured for the UE becomes a serving cell for the UE. An SCell may also be associated to an SCell state. When configured/added via RRC, an SCell starts in deactivated state. The eNB can indicate to activate-upon-configuration, or change the state, at least in RRCReconfiguration, as described below.

An intermediate state between the deactivated and active state is used for enhanced uplink operation. A MAC Control Element (MAC CE) can be used to change the SCell state between the three states as illustrated below in <FIG>. There are also timers in MAC to move a cell between deactivated/activated/dormant. The timers are: (a) sCellHibernationTimer, which moves the SCell from activated state to dormant state; (b) sCellDeactivationTimer, which moves the SCell from activated state to deactivated state; and (c) dormantSCellDeactivationTimer, which moves the SCell from dormant state to deactivated state. The MAC level SCell activation takes in the order of <NUM>-<NUM>.

After the network understands the need to configure and/or activate CA, the question is which cells to initially configure and/or activate, if they are configured, and/or whether a cell/carrier is good enough in terms of radio quality/coverage (e.g., reference signal received power (RSRP) and reference signal received quality (RSRQ)). To understand the conditions on SCell(s) or potential SCell(s) in a given available carrier the network may configure the UE to perform radio resource management (RRM) measurements.

Typically, the network may be assisted by RRM measurements to be reported by a UE. The network may configure the UE with measurement IDs associated to reportConfig with event A1 (serving becomes better than threshold) in case this is a configured SCell, or A4 (neighbor becomes better than threshold) for carriers without a configured SCell. The measurement objects are associated to the carrier the network wants reports on. If the network is aware of the exact cells it wants the UE to measure, a white cell list can be configured in the measurement object so that the UE is only required to measure the listed cells in that carrier. An example is illustrated in <FIG>.

<FIG> is a flow diagram illustrating carrier aggregation and/or dual connectivity 9DC) setup. The UE connects to the master node and the master node determines to setup CA/DC. To determine appropriate SCell(s), the master node configures the UE to report measurements. Based on the reported measurements (which can take a significant amount of time), the master node determines which SCell(s) to add.

With dual connectivity, it is possible to add what is referred to as a SCG (Secondary Cell Group) configuration to the UE. The main benefit is that the UE can in principle add a cell from another eNodeB. Protocol-wise, that requires different MAC entities, one for each cell group. The UE has two cell groups, one associated to the PCell (master node) and another associated to a PScell (of the secondary eNodeB), where each group may possibly have their own associated SCells.

When it comes to adding SCells, when the UE is in single connectivity, for example, the RRCConnectionReconfiguration message may carry a cell index (so MAC identifiers are optimized, i.e., shorter), cell identifier and carrier frequency, common parameters, and state information, (activated or dormant). <IMG>
<IMG>.

The procedure to add SCells to the MCG in LTE (or to modify) is described as follows (as in TS <NUM>).

If the RRCConnectionReconfiguration message does not include the mobilityControlInfo and the UE is able to comply with the configuration included in this message, the UE shall:.

Some implementations include early measurements upon idle/inactive to connected transition in LTE. It is possible to configure the UE to report early measurements upon the transition from idle/inactive to connected state. These measurements are measurements that the UE can perform in idle/inactive state, and according to a configuration provided by the source cell with the intention to receive these measurements immediately after the UE is connected and quickly setup CA and/or other forms of DC (e.g., EN-DC, MR-DC, etc.) without the need to first provide a measurement configuration (measConfig) in RRC_CONNECTED, and wait for hundreds of milliseconds until first samples are collected, monitored and then the first reports are triggered and transmitted to the network.

A first aspect of the existing solution, as standardized in EUTRA <NUM> (v15. <NUM>), is described in <NUM>. <NUM> Idle Mode Measurements. The UE can receive the idle/inactive mode measurement configurations in the system information (SIB5) in the field MeasIdleConfigSIB-r15, indicating up to <NUM> cells or ranges of cell IDs to perform measurements on. In addition, the UE can be either configured upon the transition from RRC_CONNECTED to RRC_IDLE with a dedicated measurement configuration in the RRCConnectionRelease message with the measldleDedicated-r15 which overrides the broadcasted configurations in SIB5. The broadcasted and dedicated signaling is shown below:.

Some implementations include carrier information and a cell list. The UE is provided with a list of carriers and optionally with a list of cells that the UE shall perform measurements. The fields s-NonIntraSearch in SystemInformationBlockType3 do not affect the UE measurement procedures in IDLE mode.

Upon the reception of the measurement configuration, the UE starts a timer T331 with the value provided in measIdleDuration, which can go from <NUM> to <NUM> seconds. The timer stops upon receiving RRCConnectionSetup, RRCConnectionResume which indicates a transition to RRC_CONNECTED. The purpose is to limit the amount of time the UE performs early measurements.

A validity area comprises a list of physical cell identities (PCIs) that is signalled per carrier that the UE shall perform idle mode measurements on. The intention is to limit the area where CA or DC may be setup later when the UE resumes/setups the connection, so the early measurements are somewhat useful for that purpose. If a validityArea is configured, and UE reselects to a serving cell whose PCI does not match any entry in validityArea for the corresponding carrier frequency, the timer T331 is stopped. Then, the UE stops performing IDLE measurements and releases the idle mode measurement configuration (i.e., VarMeasIdleConfig). This does not necessarily mean that the UE releases the idle measurement results that were configured and that were performed i.e. these may still be stored and possibly requested by the network. In addition, the UE may continue with IDLE mode measurements according to the broadcasted SIB5 configuration after the timer T331 has expired or stopped.

Only measurements above a certain threshold shall be stored because the cell candidates for CA setup needs to be within a minimum acceptable threshold. How the UE performs measurements in IDLE mode is up to UE implementation as long as RAN4 requirements for measurement reporting defined in <NUM> are met.

The UE behaviour in more details is shown below as captured in <NUM>:.

This procedure specifies the measurements done by a UE in RRC_IDLE when it has an IDLE mode measurement configuration and the storage of the available measurements by a UE in both RRC_IDLE and RRC_CONNECTED.

NOTE: It is up to UE implementation whether to continue IDLE mode measurements according to SIB5 configuration after T331 has expired or stopped.

Some implementations include an indication of available early measurements upon resume/setup in LTE. For example, when the UE tries to resume or setup a call from RRC_IDLE without context, if the previous step is performed, i.e., if the UE is configured to store idle measurements, the network may request the UE after resume/setup (after security is activated) whether the UE has idle measurements available.

If the UE is setting up a connection coming from RRC_IDLE without the AS Context, the network is not aware that the UE has available measurements stored. Then, to enable the network to know that, and possibly request the UE to report early measurements, the UE may indicate the availability of stored idle measurements in RRCConnectionSetupComplete. Because not all cells support the feature, the UE only includes that availability information if the cell broadcasts in SIB2 the idleModeMeasurements indication. The flag in RRCReconnectionSetupComplete and procedure text are shown below:
<IMG>.

NOTE <NUM>: Prior to this, lower layer signalling is used to allocate a C-RNTI. For further details see TS <NUM>;.

If the UE is setting up a connection coming from RRC_IDLE but with a stored AS Context (i.e., resume from suspended), the network may be aware that the UE may have available idle measurements stored after checking the fetched context from the source node where the UE got suspended. However, it is still not certain that the UE has measurements available because the UE is only required to perform the measurements if the cells are above the configured RSRP/RSRQ thresholds and while it performs cell selection/cell reselection within the configured validity area. Then, to enable the network to know that, and possibly request the UE to report early measurements, the UE may also indicate the availability of stored idle measurements in RRCConnectionResumeComplete. Because not all cells support the feature, the UE only includes that availability information if the cell broadcasts in SIB2 the idleModeMeasurements indication. The flag in RRCReconnectionResumeComplete and procedure text are shown below:
<IMG>.

Some implementations include reporting of early measurements upon resume/setup in LTE. After the UE indicates to the target cell upon resume or setup that idle measurements are available, the network may request the UE to report these available measurements by including the field idleModeMeasurementReq in the UEInformationRequest message transmitted to the UE. Then, the UE responds with a UEInformationResponse containing these measurements. An example is illustrated in <FIG>.

Upon receiving the UEInformationRequest message, the UE shall, only after successful security activation:.

There currently exist certain challenges. For example, in LTE euCA, the UE can be configured with idle mode measurement configurations comprising a validity area. The validity area is configured as a list of cells per frequency in the idle mode measurement configuration (MeasIdleConfig), and may be configured for one, several or all the frequencies that are part of the idle mode measurement configuration.

In case a validity area is configured, i.e. the validity area is configured for any of the frequencies in MeasIdleConfig, then the UE shall consider itself to be outside the validity area if it reselects to either a carrier that does not have any validity area configured or a cell on a carrier for which a validity area is configured but the PCI for the cell is not included in that validity area. In such case, the UE stops timer T331, and thus releases the idle measurement configuration.

A problem with the existing configuration of validity area in LTE is that each carrier where the UE should be allowed to be camping while still being within the validity area needs to be part of the idle mode measurement configuration (MeasIdleConfig). Because the idle mode measurement configuration is for measurements of carriers that should be added as SCell in a CA configuration or (in Rel-<NUM>) as SCG in an MR-DC configuration, the carriers are in many cases not suitable or likely to be camped on. If the validity area, which relates to areas of camping, is included in the idle mode measurement configuration this will need to include carriers (frequencies) that are not useful for the idle/inactive mode measurements (or early measurements). This can additionally cause problems because there is a restriction on the number of carriers that can be included in the idle mode measurement configuration.

In LTE, if the UE reselects to a carrier that does not include a validity area, i.e. list of cells that are part of the validity area, then it considers itself to be outside the validity area. However, in many cases, the desired configuration would be that the UE continues the idle/inactive mode measurements (or early measurements) when it is camping on a specific carrier, independent on what cell it is camping on. This is e.g. the case if a CA or DC configuration is supported for all the cells on a certain carrier, which could be a typical case. The network is however not able to configure a validity area that includes a whole carrier (frequency).

The IE MeasIdleConfig is used to convey information to UE about measurements requested to be done while in RRC_IDLE or RRC_INACTIVE.

As a summary, a shortcoming of this approach is that the network can configure a validity area only comprising cells that are operating on frequencies that the UE is configured to perform early measurements on. For example, the network is not able to configure a validity area of cells operating on frequency x if the UE was not configured to perform early measurements on frequency x.

Additionally, the LTE euCA signaling for validity area only allows limiting the cells/frequencies where the UE is mandated to perform measurements. But it does not allow the possibility to make a certain serving frequency valid for early measurements regardless of the particular cell. For example, the network may have a very good complete coverage at a low frequency x and it can perform CA with many other frequencies and the frequency x, and as such it may want to configure the UE to perform early measurements whenever the UE is camping on a cell operating at that frequency. Current signaling doesn't allow that, as the list of valid cells have to be included per validity area carrier.

<CIT> discloses a method and apparatus for efficiently controlling carrier aggregation of a terminal in a network using LTE or a next generation radio access technology. The method of the disclosed terminal may include receiving IDLE mode measurement configuration information for measuring a channel state in an RRC_IDLE mode from a base station, performing at least one of storing and applying the IDLE mode measurement configuration information, and transmitting IDLE mode measurement result information measured in the RRC_IDLE mode based on the IDLE mode measurement configuration information to the base station.

<CIT> discloses a method of performing a logged measurement by using a terminal in a wireless communication system. The disclosed method includes: receiving a measurement configuration from a network; logging a Minimization of Driving Tests (MDT) measurement; detecting whether a state shift condition occurs; shifting a state if the state shift condition occurs; and logging state shift information related to the state shift.

<CIT> discloses a method of performing measurement. The disclosed method may be performed by a user equipment (UE) and comprise: receiving, by the UE, a cell list from a serving cell; if at least one cell in the cell list is detected, performing, by the UE, measurements on a frequency corresponding to the cell list and applying layer <NUM> filtering for the measurements; and if any cell in the cell list is not detected, not performing the measurements on the frequency corresponding to the cell list.

Based on the description above, certain challenges currently exist with validity areas for early measurements. Certain aspects of the present disclosure and their embodiments may provide solutions to these or other challenges.

Certain embodiments may provide one or more of the following technical advantages. For example, in some embodiments the network can configure the cells/frequencies where the UE should perform early measurements separately from the frequencies that the UE is configured to measure while in RRC_IDLE/RRC_INACTIVE. In addition to that, it is also possible to white-list certain frequencies, where the network can configure the UE to perform early measurements while camping on any cell operating at the frequency.

As described above, certain challenges currently exist with validity areas for early measurements. Certain aspects of the present disclosure and their embodiments may provide solutions to these or other challenges. For example, particular embodiments configure validity area comprising of cells operating on frequencies that the user equipment (UE) is not configured to measure during idle/inactive modes. Particular embodiments configure validity area in such a way that the UE performs measurements while camping on any cell operating at a given frequency.

Particular embodiments are described more fully with reference to the accompanying drawings.

The embodiments and examples herein are described with respect to methods, signaling and procedures for fifth generation (<NUM>) new radio (NR). However, the embodiments and examples are equally applicable to evolved universal terrestrial radio access (E-UTRA) and other wireless networks. The terms idle/inactive measurements and early measurements are used inter-changeably herein.

In long term evolution (LTE) euCA, a UE can be configured to perform idle/inactive mode measurements to be reported after the UE returns to RRC_CONNECTED. The early measurement configurations may optionally contain a validity area, which are signaled as a physical cell identifier (PCI) per carrier the UE is configured to measure on.

If the UE re-selects to a cell with a frequency and PCI matching the validity area, the UE continues to perform measurements. However, if the UE re-selects to a cell on a carrier where the validity area does not include the PCI, the UE stops the early measurements and deletes the early measurement configurations.

NR may also include a validity area. The LTE design of the validity area meant that the validity area could only contain cells on frequencies that the UE was configured to perform early measurements on (as the same carrier list was used to indicate which carriers to measure, and which carriers the cells in the validity area belonged to).

If the network wants to configure a validity area with cells that are on a frequency that the UE could re-select to, but which would not be relevant for early measurements, e.g. a low bandwidth carrier on a low frequency applicable for robustness but not useful for carrier aggregation (CA)/dual connectivity (DC), the network would still have to configure early measurements on that carrier to enable the cells to belong to the validity area.

To avoid this restriction in NR, particular embodiments define a validity area separate from the idle/inactive measurement carrier list. In addition, when the validity area is defined separately from the carrier list to measure, the validity area may comprise a set of carriers instead of a set of cells.

In particular embodiments, the validity area is defined as a carrier list (which could be different from the carriers to be measured during RRC_IDLE/INACTIVE) with optional PCI list per carrier. In addition, because it is possible to configure the idle/inactive measurements for only a particular frequency (i.e. without indicating a cell list), particular embodiments may configure a validity area comprising frequencies without indicating a cell list.

In some embodiments, the cell list in the validity area is optional to facilitate idle/inactive measurements while camping on any cell on that frequency.

An example ASN. <NUM> and procedural handling of the validity area is shown below.

In some embodiments, the UE is not mandated to continue performing early measurements when T331 is stopped, but it can continue to perform the measurements based on UE implementation (i.e., as in LTE euCA).

<FIG> illustrates an example wireless network, according to certain embodiments.

These components work together to provide network node and/or wireless device functionality, such as providing wireless connections in a wireless network.

Interface <NUM> is used in the wired or wireless communication of signaling and/or data between network node <NUM>, network <NUM>, and/or WDs <NUM>.

As used herein, wireless device (WD) refers to a device capable, configured, arranged and/or operable to communicate wirelessly with network nodes and/or other wireless devices. Unless otherwise noted, the term WD may be used interchangeably herein with user equipment (UE). Communicating wirelessly may involve transmitting and/or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and/or other types of signals suitable for conveying information through air.

In some embodiments, a WD may be configured to transmit and/or receive information without direct human interaction. For instance, a WD may be designed to transmit information to a network on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the network.

Examples of a WD include, but are not limited to, a smart phone, a mobile phone, a cell phone, a voice over IP (VoIP) phone, a wireless local loop phone, a desktop computer, a personal digital assistant (PDA), a wireless cameras, a gaming console or device, a music storage device, a playback appliance, a wearable terminal device, a wireless endpoint, a mobile station, a tablet, a laptop, a laptop-embedded equipment (LEE), a laptop-mounted equipment (LME), a smart device, a wireless customer-premise equipment (CPE). a vehicle-mounted wireless terminal device, etc. A WD may support device-to-device (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), vehicle-to-everything (V2X) and may in this case be referred to as a D2D communication device.

As yet another specific example, in an Internet of Things (IoT) scenario, a WD may represent a machine or other device that performs monitoring and/or measurements and transmits the results of such monitoring and/or measurements to another WD and/or a network node. The WD may in this case be a machine-to-machine (M2M) device, which may in a 3GPP context be referred to as an MTC device. As one example, the WD may be a UE implementing the 3GPP narrow band internet of things (NB-IoT) standard. Examples of such machines or devices are sensors, metering devices such as power meters, industrial machinery, or home or personal appliances (e.g. refrigerators, televisions, etc.) personal wearables (e.g., watches, fitness trackers, etc.).

In other scenarios, a WD may represent a vehicle or other equipment that is capable of monitoring and/or reporting on its operational status or other functions associated with its operation. A WD as described above may represent the endpoint of a wireless connection, in which case the device may be referred to as a wireless terminal. Furthermore, a WD as described above may be mobile, in which case it may also be referred to as a mobile device or a mobile terminal.

Radio front end circuitry <NUM> is connected to antenna <NUM> and processing circuitry <NUM> and is configured to condition signals communicated between antenna <NUM> and processing circuitry <NUM>.

The benefits provided by such functionality are not limited to processing circuitry <NUM> alone or to other components of WD <NUM>, but are enjoyed by WD <NUM>, and/or by end users and the wireless network generally.

In some embodiments, processing circuitry <NUM> and device readable medium <NUM> may be integrated.

User interface equipment <NUM> is configured to allow input of information into WD <NUM> and is connected to processing circuitry <NUM> to allow processing circuitry <NUM> to process the input information. Using one or more input and output interfaces, devices, and circuits, of user interface equipment <NUM>, WD <NUM> may communicate with end users and/or the wireless network and allow them to benefit from the functionality described herein.

Although the subject matter described herein may be implemented in any appropriate type of system using any suitable components, the embodiments disclosed herein are described in relation to a wireless network, such as the example wireless network illustrated in <FIG>. For simplicity, the wireless network of <FIG> only depicts network <NUM>, network nodes <NUM> and 160b, and WDs <NUM>, 110b, and 110c. In practice, a wireless network may further include any additional elements suitable to support communication between wireless devices or between a wireless device and another communication device, such as a landline telephone, a service provider, or any other network node or end device. Of the illustrated components, network node <NUM> and wireless device (WD) <NUM> are depicted with additional detail. The wireless network may provide communication and other types of services to one or more wireless devices to facilitate the wireless devices' access to and/or use of the services provided by, or via, the wireless network.

<FIG> illustrates an example user equipment, according to certain embodiments.

Certain UEs may use all the components shown in <FIG>, or only a subset of the components.

<FIG> is a flowchart illustrating an example method in a wireless device, according to certain embodiments. In particular embodiments, one or more steps of <FIG> may be performed by wireless device <NUM> described with respect to <FIG>.

The method may begin at step <NUM>, where the wireless device (e.g., wireless device <NUM>) receives an early measurement configuration for performing idle/inactive mode measurements. The early measurement configuration comprises a measurement carrier list and a validity area list.

Each entry of the measurement carrier list comprises a carrier frequency and one or more cell identifiers associated with the carrier frequency for which the wireless device is to perform idle/inactive mode measurements. The validity area list is separate from the measurement carrier list.

Each entry of the validity area list comprises a carrier frequency and zero or more cell identifiers associated with the carrier frequency for which the wireless device is supposed to perform idle/inactive mode measurements.

Accordingly, as described in more detail above, the validity area list is decoupled from the measurement carrier list, which facilitates improved configuration flexibility. In particular embodiments, the carrier frequencies in the validity area list differ by at least one carrier frequency from the carrier frequencies in the measurement carrier list.

At step <NUM>, the wireless device reselects to a new cell. The wireless device then needs to determine what kind of early measurements, if any, the wireless device should perform.

At step <NUM>, the wireless device determines whether to perform idle/inactive mode measurements while camping on the new cell based on the validity area list. For example, in particular embodiments, the wireless device may determine that a carrier frequency of the new cell matches a carrier frequency in the validity area list. As one example, when an entry in the validity area list includes a carrier frequency and zero associated cell identifiers, then the entry is valid for any cell that uses the carrier frequency.

In particular embodiments, the wireless device may further determine that a carrier frequency and a cell identifier of the new cell matches a carrier frequency and an associated cell identifier in the validity area list.

Based on the validity area list, the wireless device either continues to step <NUM>, where it performs the idle/inactive mode measurements, or to step <NUM> where the wireless device stops the measurement timer and does not perform idle/inactive mode measurements.

Modifications, additions, or omissions may be made to method <NUM> of <FIG>. Additionally, one or more steps in the method of <FIG> may be performed in parallel or in any suitable order.

<FIG> is a flowchart illustrating an example method in a network node, according to certain embodiments. In particular embodiments, one or more steps of <FIG> may be performed by network node <NUM> described with respect to <FIG>.

The method may begin at step <NUM>, where the network node (e.g., network node <NUM>) generates an early measurement configuration for performing idle/inactive mode measurements. The early measurement configuration comprises a measurement carrier list and a validity area list as described above with respect to <FIG>.

At step <NUM>, the network node transmits the early measurement configuration to a wireless device. The wireless device may use the early measurement configuration as described above with respect to <FIG>.

<FIG> illustrates a schematic block diagram of two apparatuses in a wireless network (for example, the wireless network illustrated in <FIG>). The apparatuses include a wireless device and a network node (e.g., wireless device <NUM> and network node <NUM> illustrated in <FIG>). Apparatuses <NUM> and <NUM> are operable to carry out the example methods described with reference to <FIG> and <FIG>, respectively, and possibly any other processes or methods disclosed herein. It is also to be understood that the methods of <FIG> and <FIG> are not necessarily carried out solely by apparatuses <NUM> and/or <NUM>. At least some operations of the methods can be performed by one or more other entities.

Virtual apparatuses <NUM> and <NUM> may comprise processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), special-purpose digital logic, and the like. The processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as read-only memory (ROM), random-access memory, cache memory, flash memory devices, optical storage devices, etc. Program code stored in memory includes program instructions for executing one or more telecommunications and/or data communications protocols as well as instructions for carrying out one or more of the techniques described herein, in several embodiments.

In some implementations, the processing circuitry may be used to cause receiving module <NUM>, determining module <NUM>, transmitting module <NUM>, and any other suitable units of apparatus <NUM> to perform corresponding functions according one or more embodiments of the present disclosure. Similarly, the processing circuitry described above may be used to cause generating module <NUM>, transmitting module <NUM>, and any other suitable units of apparatus <NUM> to perform corresponding functions according one or more embodiments of the present disclosure.

As illustrated in <FIG>, apparatus <NUM> includes receiving module <NUM> configured to receive early measurement configuration according to any of the embodiments and examples described herein. Determining module <NUM> is configured to determine whether to perform idle/inactive mode measurements according to any of the embodiments and examples described herein. Transmitting module <NUM> is configured to transmit measurement results, according to any of the embodiments and examples described herein.

As illustrated in <FIG>, apparatus <NUM> includes generating module <NUM> configured to generate an early measurement configuration according to any of the embodiments and examples described herein. Transmitting module <NUM> is configured to transmit the early measurement configuration to a wireless device according to any of the embodiments and examples described herein.

NFV may be used to consolidate many network equipment types onto industry standard high-volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment.

Still in the context of NFV, Virtual Network Function (VNF) is responsible for handling specific network functions that run in one or more virtual machines <NUM> on top of hardware networking infrastructure <NUM> and corresponds to application <NUM> in Figure <NUM>.

Host computer <NUM> may be under the ownership or control of a service provider or may be operated by the service provider or on behalf of the service provider.

<FIG> illustrates an example host computer communicating via a base station with a user equipment over a partially wireless connection, according to certain embodiments. Example implementations, in accordance with an embodiment of the UE, base station and host computer discussed in the preceding paragraphs will now be described with reference to <FIG>.

Connection <NUM> may be direct, or it may pass through a core network (not shown in <FIG>) of the telecommunication system and/or through one or more intermediate networks outside the telecommunication system.

While OTT connection <NUM> is active, the network infrastructure may further take decisions by which it dynamically changes the routing (e.g., based on load balancing consideration or reconfiguration of the network).

Wireless connection <NUM> between UE <NUM> and base station <NUM> is in accordance with the teachings of the embodiments described throughout this disclosure. One or more of the various embodiments improve the performance of OTT services provided to UE <NUM> using OTT connection <NUM>, in which wireless connection <NUM> forms the last segment. More precisely, the teachings of these embodiments may improve the signaling overhead and reduce latency, which may provide faster internet access for users.

A measurement procedure may be provided for monitoring data rate, latency and other factors on which the one or more embodiments improve. In embodiments, sensors (not shown) may be deployed in or in association with communication devices through which OTT connection <NUM> passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above or supplying values of other physical quantities from which software <NUM>, <NUM> may compute or estimate the monitored quantities.

Additionally, or alternatively, in step <NUM>, the UE provides user data.

Modifications, additions, or omissions may be made to the systems and apparatuses disclosed herein without departing from the scope of the invention. The components of the systems and apparatuses may be integrated or separated. Moreover, the operations of the systems and apparatuses may be performed by more, fewer, or other components. Additionally, operations of the systems and apparatuses may be performed using any suitable logic comprising software, hardware, and/or other logic. As used in this document, "each" refers to each member of a set or each member of a subset of a set.

The foregoing description sets forth numerous specific details. It is understood, however, that embodiments may be practiced without these specific details. In other instances, well-known circuits, structures and techniques have not been shown in detail in order not to obscure the understanding of this description. Those of ordinary skill in the art, with the included descriptions, will be able to implement appropriate functionality without undue experimentation.

Although this disclosure has been described in terms of certain embodiments, alterations and permutations of the embodiments will be apparent to those skilled in the art. Accordingly, the above description of the embodiments does not constrain this disclosure. Other changes, substitutions, and alterations are possible without departing from the scope of this disclosure, as defined by the claims below.

Claim 1:
A method performed by a user equipment (<NUM>) for performing idle/inactive mode measurements, the method comprising:
receiving (<NUM>) an early measurement configuration for performing idle/inactive mode measurements, the early measurement configuration comprising:
a measurement carrier list, each entry of the measurement carrier list comprising a carrier frequency and one or more cell identifiers associated with the carrier frequency for which the user equipment (<NUM>) is to perform idle/inactive mode measurements;
a validity area list, separate from the measurement carrier list, each entry of the validity area list comprising a carrier frequency and zero or more cell identifiers associated with the carrier frequency for which the user equipment (<NUM>) is to perform idle/inactive mode measurements;
reselecting (<NUM>) to a new cell;
determining (<NUM>) whether the user equipment (<NUM>) may perform idle/inactive mode measurements while camping on the new cell based on the validity area list; and
upon determining the user equipment (<NUM>) may perform idle/inactive mode measurements while camping on the new cell, performing (<NUM>) the idle/inactive mode measurements.