Telecommunication system

ES 2 834 577 T3

DESCRIPTION

Coverage map in a telecommunications network

Description field

This description refers to providing radiocommunication coverage cells between communication devices and a core network. In particular, the invention relates to defining a set of criteria for selecting certain communication devices from among the candidates to become active to provide service to a set of communication devices.

Background of the invention

Cellular telecommunications networks characteristically provide radio communication coverage "cells" between communication devices (which are typically mobile) and a core network (with a "downlink" from the core network to the communication device and an "uplink" ”In the opposite direction).

Various radio access technologies (RAT) are implemented: digital cellular networks are currently the most common and these are freely classified as second generation (2G), third generation (3G), fourth generation (4G) technologies, etc. ., depending on whether the RAT achieves effective data communications that meet increasingly challenging requirements. By meeting these requirements, technologies make different uses of the available radio frequency (RF) bandwidth: neighboring cells in 2G technologies, for example, are deployed to use RF bandwidth at different frequencies to avoid interference .

To ensure effective coverage of a large geographic area, a plurality of cells are provided by respective network nodes, variously referred to as base transceiver stations and base stations. The base stations (transceivers) are associated with one or more antenna arrays which in turn establish the respective cells. They are controlled at least in part by other entities in the core network known as controllers (in 3G technologies such as UMTS, these are referred to as radio network controllers, RNCs). More recently, certain categories of base transceiver stations, referred to as eNodeBs or eNBs in the context of LTE, implement both base station functionality and at least some controller functionality. The antenna clusters (and thus often the base stations) are geographically distributed, so that the coverage of each cell typically overlaps that of neighboring cells only at the edge of the cell. RATs aim to ensure that communication devices are provided with continuous coverage, even if they are moving from the coverage of a first cell to that of a second through the cell border region: to do this, they use a reselection technique referred to as "handover" (or "handover"). Handover is described as "smooth" when the procedure allows a transition period during which control and / or user data traffic destined for a given communication device is routed to the device through more than one of the cells. In other words, the device is allowed to "camp" in more than one cell.

Providing communication devices with coverage at the edge of the cell typically requires more network resources; for example, the transmit power needs to be higher on the downlink in order for the RF signal to propagate to the edge of the cell.

The '99 version of the W-CDMA Standard enabled reuse of the same frequency at the edge of the cell with a soft handover (that is, a handover that has a transition phase where a terminal effectively camps both in the cell of origin as the destination).

However, in later versions of RAT 3G, HSDPA, for example, has mainly eliminated in the downlink the concept of soft handoff: data is transmitted from only one cell to the terminal.

In many parts of the world, 4G RATs are deployed (such as those conforming to 3GPP standards known as Long Term Evolution (LTE)). Like these latest versions of 3G, LTE uses universal frequency reuse (where cells far enough apart operate on the same frequency) without soft handoff. Consequently, high levels of interference and low SINR (signal-to-interference plus noise) can be expected near the edge of the cell. This assumes that users at the cell edge in LTE (and HSDPA, etc.) require more radio resources (i.e. user plane resource blocks, control channel resource blocks, etc.) than the users closest to serving base transceiver stations (i.e. eNB). Consequently, the potential for the cell to be affected increases when there is an increase in the number and activity of users on / near the border of the cell.

LTE is also specified to handle different types of base transceiver station entities. The requirement for cellular communication coverage is far from uniform across a typical geographic area. In addition, the natural features or the characteristics of the built environment introduce additional restrictions on the operation of the base station entities.

ES 2 834 577 T3

The most prevalent class of base transceiver station is the wide area eNodeB which provides coverage over a wide geographic area (spanning distances up to 20 km), this is sometimes referred to as the "eNB macro (layer)" type. Such eNBs often provide more than one "cell" or sector.

Base transceiver stations with more limited transmit power than macro eNBs, and typically providing a cell or sector, are known as micro eNBs.

Smaller cells can be provided by devices of even lower power: local area eNBs (or picocell base stations) and home eNBs (or femtocell base stations). The resulting femtocells and picocells are sometimes referred to generally as "small cells." These classes of base transceiver stations are typically used in areas where coverage would otherwise be inadequate or inconvenient to maintain using conventional eNB equipment. The main distinction between home and local area eNBs is that, in the case of home eNBs, the location and control of the device is with the end user rather than the network operator; these devices conventionally offer communication services to a "whitelist" of home users rather than any network subscriber who happens to be in range.

LTE has a hierarchical architecture so that a wide area coverage layer (the macro layer) can overlap or span geographic regions within the coverage of smaller cells (the “micro layer”). However, there may be a preference on behalf of the network operator to have uplink and / or downlink traffic for certain devices delivered to the micro layer; to free capacity in the macro layer for devices that are outside the coverage of the micro layer, for example.

Network operators want to improve the efficiency of using their networks at or near cell edges.

It is known to address the cell border problem:

• Increasing performance at the cell edge, for example by adding increasingly complex software to macro cells to improve cell edge performance (usually within the area of ​​coordinated scheduling between adjacent cells). In certain cases, such as for the CoMP (Coordinated Multiple Point) feature described in 3GPP Version 11, improved cell edge performance brings with it the need for dedicated transmit (Tx) and receive (Rx) antennas. associated with one or more macro eNBs.

• Installing fixed Small Cells (ie local area eNodeBs) to increase system capacity.

The installation of small fixed cells by a network operator brings with it the burden of finding suitable locations, paying the site rent, and deploying additional cables to connect the small fixed cells to other nodes on the network. In addition, the installation and commissioning (including configuration) of small fixed cells takes time: even if a wireless backhaul link is used instead of cables, the small fixed cells need to be installed in a suitable position and configured for their operation at that location. In some cases, this process may include setting up and testing directional antennas associated with such small cell devices that require the skills of a professional radio engineer. In addition, when the small cell device fails or otherwise requires servicing the device and the installation site needs to be accessible by the operator: since these devices are typically owned by the network operator but are located on private land and in locations sometimes inaccessible, there are likely to be logistical and practical obstacles to the intervention of one of the operator's engineers.

The LTE standards (3GPP Version 10 (and later)) also describe two additional Radio Access Network entities: relays and repeaters that can be used to address the cell edge problem. Both types of entities provide the coverage extension for a cell of an existing base transceiver station.

A repeater is communicatively linked to a corresponding (typically macro) eNB, which has a first antenna within a given cell (the "donor cell") of the eNB and a second antenna directed toward a coverage area where an extension is required. coverage. In certain cases, a repeater merely retransmits (that is, rebroadcasts) a signal, received on a first frequency, on a second frequency, typically amplifying the repeated signal. The uplink and downlink signals can thus be carried through repeaters without any need for decoding.

The repeaters specified in Version 10 (and later) of the 3GPP standards decode the (incoming) signal and then recode and retransmit that signal: this new class of repeater is referred to as a "relay".

A relay is also communicatively linked to a corresponding eNB. It also has a first antenna within a given cell (the "donor cell") of the eNB and a second antenna directed towards a target coverage area. However, relays form their own cells and operate in many ways such as

ES 2 834 577 T3 base transceiver stations in their own right. The relays decode the signals from the donor cell, applying any necessary error correction, and make decisions about how radio resources (such as channels within each radio subframe) are allocated.

There are certain network conditions where individual communication devices in cellular networks have a disproportionately detrimental effect on network performance.

In certain cases, for example, one or more terminals (also called "user equipment" or simply UE) may be near the edge of a serving cell. A small number of active users at the cell edge can consume a high number of cell resources (eg, LTE resource blocks) since the cell edge typically correlates with poor coverage; implying that a high number of resources must be dedicated to the cell edge users to provide a throughput at a given level when compared to the demand for resources by users who are in better radio conditions (that is, far from the cell borders). Serving radio resources for communication devices at the edge of the cell have a higher cost in terms of resource allocation and power usage than a similar device in a cell region closer to a station system service base transceiver (such as an eNodeB).

When cellular networks are deployed, they are often specified with greater capacity than is anticipated to be required by existing communication devices. However, the numbers of communication devices and the demand for increasing network resources mean that the network may be affected by capacity problems on the radio interface more often than is acceptable.

Known approaches to cell edge problems seek to increase the capacity or coverage of the cellular network by adding additional network equipment at locations in the network where cell edge problems regularly occur (or are expected). . Such teams are typically fixed in one location and require careful planning.

The network and other performance conditions very often change over time: for example, individual communication devices which, by virtue of their location at the edge of the cell and active use of the network, have a detrimental effect on the network performance at the same time, may, at other times, be idle and not cause such an effect. Furthermore, since UEs are typically mobile, they may have moved out of the affected cell entirely or closer to the base transceiver station equipment serving the cell, in any way, reducing the detrimental effect.

Therefore, it is desirable to ensure that the network can adapt to the presence of dynamic effects on capacity and coverage, and also to provide a system that allows the extension of coverage in a cellular network that can be dynamically deployed without requiring the site. of additional radio equipment near regions of poor radio coverage.

Known approaches typically require the provision of additional and dedicated radio network equipment to assist in the extension of cell coverage. Such equipment is typically fixed in one location and requires careful planning.

When there are several potential aggregators that can be used, there is a need to define a set of criteria to select which aggregators among the candidates can become active to provide the service to a set of terminals. Specifically, there is a need for a solution that allows communication devices to provide a coverage area to a set of terminals.

Document US 2010/167743 A1 describes a method for centralized control of relay operations in a network.

Compendium of the invention

The invention is defined by independent claims 1, 12 and 13.

The second communication devices are different from the first communication devices with respect to their ability to act as aggregators, where an aggregator is a device that comprises means to add one or more connections from the first communication devices to a RAN. In the context of the present specification, aggregation is to be understood as the ability to provide a coverage area to provide service to a number of first communication devices that are currently connected through an additional layer. An aggregation connection carries aggregated data from the first communication devices, the data from each first communication device that is packed for the backhaul link to a core network.

The second communication devices are instructed to send a signal, for example a pilot signal or a beacon signal, and the first communication devices report this signal back to the central controller, which then uses these reports to build coverage maps. or coverage maps for the second communication devices.

ES 2 834 577 T3

In the case when there is a need to provide a complementary coverage area, and where there are several potential aggregators, there is a need to define a set of criteria to select which aggregators among the candidates can become active providing the service to a set. of terminals. In the present specification, the user equipment UE and the terminals refer to the first communication devices that can receive the aforementioned beacon signals from the second communication devices.

In this type of solution, a series of communication devices may be available in a specific cell to provide a coverage area to offer service to a series of normal terminals that are currently connected through an additional layer, that is, the layer of Participative RAN.

A method according to the invention advantageously collects specific information on radio conditions in order to make decisions about which aggregators can be activated. Given the specific characteristics and conditions of a network of second communication devices that act as a small cell or access points that are dynamically activated, the defined invention provides a way for the first communication devices or terminals to be added to measure the quality of coverage they could get from an aggregator before the aggregator goes into service. The radio conditions mentioned can be availability, battery life, location, expected profit, etc.

The second communication devices are communication devices that are configurable to act as aggregators, and the central controller is a central aggregator controller. Advantageously, this allows the central controller to instruct the second communication devices to establish an aggregation connection with the first communication device and a second connection between the first communication device and a central network CN, wherein the second connection includes the aggregation connection and the statement is dependent on performance conditions.

The central controller instructs said one or more second communication devices to activate.

In the context of this specification, a coverage map can be a record of the relationships discovered between potential aggregators and the population of first communication devices or UEs. If the geographic locations of both the potential aggregator and the UEs are known, then the map can be a geographic map where the relationship between potential aggregators and UEs is distance. However, when the geographic location of the UE is unknown with some precision, then the map can be a radio map, where the relationship between the potential aggregator and the UEs is path loss, received signal strength, or an equivalent measure. . Multiple relationships can be recorded using a coverage map if known. For example, both distance and path loss can be discovered and recorded. This information can be displayed graphically (as if they were a conventional map) and / or the relationships can only be recorded in a machine-readable database. There may be information in the coverage map that includes the time that potential aggregators and potential aggregated devices are static or how long they have been in the cell, or even data such as the remaining battery life.

In certain embodiments of the invention, the activation of one or more second communication devices is performed periodically. Advantageously, beacon signals can be periodically sent by the second communication devices to one or more first communication devices that allow updating of the radio conditions of the telecommunications network in the central controller. This is quite advantageous in situations where the first communication devices, for example mobile phones, change position continuously.

Alternatively, instead of periodically, activation can be performed upon a command received from the central controller. Advantageously, the central controller can be in communication with a central network from which estimates can be received so that the decision is made to activate said beacon signals in the second communication devices.

In certain embodiments of the invention, the one or more radio frequency bands are non-cellular bands close to the cellular bands to be used in the RAN.

Measurements are made in the non-cellular band but in a band that is representative of the measurements that would have been made if a cellular band had been used. Representative comprises that said cell band provides propagation characteristics similar to the propagation characteristics of those cell bands, such as fading, reflection or diffraction, in such a way that the path loss behavior reported by communication devices reliably reproduces the path loss of the cellular bands to be used in the RAN. That is, instead of making a measurement directly on a cellular band, which can only be done using cellular communications, for example, for regulatory reasons, a non-cellular band is used to make a measurement on that cellular band, and the band non-cellular used is one that is close to the cellular band such that all radio measurements (such as received power, attenuation, interference, etc.) can be considered as equivalent to the measurements that would have been made in the cellular band.

ES 2 834 577 T3

Advantageously, RF bands that are non-cellular bands that are close to the cell bands to be used by the RAN provide propagation characteristics similar to the propagation characteristics of those cell bands, such as fading, reflection or diffraction, in such a way that the path loss behavior reported by the communication devices reliably reproduces the path loss of the cellular bands to be used in the RAN. In this way, the map created is a more reliable pattern for path loss and at the same time cellular bands are lightened from such transmissions, therefore it is suitable to be used for other purposes, such as communication.

In certain embodiments, one or more RF bands can be cellular bands to be used in the RAN. In certain embodiments, there may be unused FDD or TDD channels within the cellular RF band that can be used to broadcast beacon signals.

In certain embodiments where the one or more RF bands are cellular bands, the one or more second communication devices are activated to broadcast said beacon signals in a blocked state.

In the case when cellular RF bands are used for broadcasting beacon signals, a second communication device can be put into a forbidden state so that it does not appear as an available access point / cell to the first communication device that receives a broadcast signal. This advantageously allows a central controller to receive measurements from said first communication device, but there is an option for the second communication devices to broadcast beacon signals without the requirement to act as aggregators: that is, simply due to conditions such as life remaining battery or bandwidth requirements of the second communication device in a particular time frame, or others. Advantageously, in these embodiments, the beacon signal carrier is a carrier that does not carry traffic, so this is a way to ensure that it only acts as a beacon carrier to the extent that it is prevented from handling data or voice traffic. . In the event that a second communication device is selected, activated, to act as an aggregator, a used cellular carrier will be a first carrier, while a second carrier would be used only as a beacon. Alternatively, in the same area, a single carrier can be used as both:

- only beacon, when the aggregator is not being added but only its presence is signaled, or

- traffic and beacon when the aggregator is actually handling aggregate traffic.

In certain embodiments, the beacon signal is sent through a cellular technology such as LTE FDD, TDD or 3G) or a Wi-Fi technology such as a Wi-Fi carrier in the 2 GHz spectrum, for example.

In certain embodiments, a method according to the invention further comprises activating one or more of the second communication devices as an aggregator based on at least the coverage map.

In addition to creating a coverage map, the central controller can activate one or more second communication devices depending on the requirements for an allowable path loss, for example. In one example, a coverage map can meet the requirements of a group of devices so that potential aggregators offering a required service can be activated. In another example, beyond the coverage map, the central controller can activate some of the potential aggregators only if other conditions are met.

The telecommunications network also comprises a central network (CN) and a radio access network (RAN), where the first communication devices are communication devices connected to the CN through the RAN, and which are candidates to be connected to the CN through the second communication devices.

In certain embodiments, the one or more second enabled communication devices are the second communication devices that are not currently acting as aggregators. Advantageously, this allows the rotation of the second communication devices that act as aggregators.

In certain embodiments, the second communication devices comprise communication devices that are not currently acting as aggregators and / or the second communication devices that are already acting as aggregators.

Advantageously, this allows the entire set of second communication devices to be considered as aggregators, thus capturing both groups of second communication devices to be correlated:

- only the aggregators to be turned on, so that they are considered as candidate aggregators and potentially selected, and

- also those aggregators that are already active.

In this way, handover is avoided for the first communication devices that are added through a particular aggregator in the case when, for example, a second communication device is selected as

ES 2 834 577 T3 potential aggregator; In this example, even if the potential aggregator is to be activated, the aggregator maintains its function as a second communication device which is to be an aggregator and thus the first communication device does not need to be handed over to a RAN layer. Different participatory.

In certain embodiments, creating the coverage map comprises estimating, for each of the first communication devices, a path loss with each relevant second communication device.

The coverage map is created for aggregators not yet active (that is, those to be activated by a method according to the invention) and also for those that are already active.

A second relevant communication device may be a device whose connection path with the first communication device is to be included in the coverage map. For example, the path loss can only be calculated between those first communication devices and aggregators with which there is at least one possibility of connection. In another example, the path loss can be calculated between each and every pair of aggregators and first communication devices.

In certain embodiments, the estimated path loss, the estimated path loss, is based on measurements reported by the first one or more communication devices that have received the relevant beacon signal.

It is an objective of certain embodiments of the present disclosure to resolve, mitigate or obviate, at least in part, at least one of the problems and / or disadvantages associated with the prior art. Certain embodiments aim to provide at least one of the advantages described below.

Brief description of the drawings

Various embodiments of the present description will now be described with reference to the accompanying drawings, in which:

Figures 1A to 1C illustrate a radio access network where certain communication devices are dynamically assigned as aggregators within a single cell;

Figures 2A and 2B illustrate a further radio access network where certain communication devices are dynamically assigned as aggregators within a multi-cell network;

Figure 3 illustrates the functional elements of an aggregator controller suitable for enabling, controlling and disabling an aggregator layer in the network architecture of Figures 1A, 1B, 1C, 2A and 2B;

Figure 4 illustrates the behavior of nearby communication devices when the aggregator controller of Figure 3 enables an aggregator layer on a given aggregator;

Figure 5 illustrates the functional elements of a communication device suitable for use in the network architecture of Figures 1A, 1B, 1C, 2A and 2B;

Figures 6A and 6B illustrate certain operations of a controlling entity in determining whether activation of an aggregator facility is supported;

Figure 7 shows a flow chart showing certain operations of a communication device associated with the mobility state;

Figure 8 shows a flow chart showing certain additional operations of a communication device associated with the mobility state; and Figure 9 illustrates an example of a system where a method according to the invention is implemented.

Figure 10 illustrates a scenario where a method according to the invention can be implemented, where currently the second communication devices are acting as aggregators.

Figure 11 illustrates two different configurations according to the present description.

Detailed description of the preferred embodiments

The present description refers to a method for providing a coverage map within a telecommunications network architecture that includes a radio access network (RAN), a core network (CN) and a packet data network (PDN). . Communication devices, such as mobile terminals, user equipment (UE), and wireless access stations, establish wireless connections to the network via the RAN.

Figures 1A to 1C show a single cell 100 of the telecommunications network provided by a base transceiver station (ie macro eNB) 120 within the RAN. The telecommunications network architecture further comprises a network node, referred to as an aggregator controller (AC) 102, which is

ES 2 834 577 T3 communicates with the RAN and the CN (illustrated here as a link between the AC 102 and the eNB 120) but can be implemented independently of the component entities of either the RAN or the CN.

AC 102 identifies at least one communication device 104 as a candidate for aggregator assignment. The AC 102 also instructs any given aggregator candidate 104 to activate (or deactivate) an aggregator mode, whereby it provides base station functionality for nearby (mobile) communication devices 110: in Figure 1C, each aggregator device Aggregator-enabled, enabled communication 104 provides a respective aggregator cell 150. The AC 102 also determines whether any aggregator candidate 104 is activated at all at any given time in a given region of the telecommunications network. In Figures 1A to 1C, the candidate aggregators 104 are illustrated as the UEs: this is merely an example of a suitable communication device 104, the candidate aggregators can equally be dedicated communication devices or even small cell base transceiver stations such as HeNBs or eNB femtocell.

The AC 102 is configured to interrogate one or more communication devices 104, where these devices are connected to the RAN (i.e., the eNB 120), to determine certain parameters associated with the device 104 and / or its connection to the RAN. (for example, SINR, received power to reference signal (RSRP), power to signal received code (RSCP), location information, battery life, etc.). The data associated with the parameters is processed in the AC 102 and, if it is determined that the parameters indicate that the or each communication device 104 is a candidate for assignment as an aggregator, the communication device 104 may be configured to implement a mode. aggregator, thereby providing base station functionality for nearby (mobile) communication devices 110.

Figures 1A through 1C also illustrate a scenario where the facility is contemplated to extend base station functionality to nearby (mobile) communication devices 110. As communication devices approach the furthest macro cell coverage interval in the cell (ie, the edge of the cell, illustrated as shaded area 130), they consume more network resources. By selecting certain communication devices to act as aggregators, these devices that are within good macro cell coverage but have the facility to extend base station functionality within an "aggregator cell" beyond the coverage of the macro cell layer, the network can deploy aggregators to address cell edge issues.

Certain communication devices 104 connected to the network are thus used as a type of small cell entity. The network-connected communication devices assigned to perform this small cell-like functionality are called "aggregators" because, when there is more than one communication device 110 near a given network-connected communication device 104 in aggregator mode, data traffic from nearby communication devices 110, for each of the nearby communication devices 110, is temporarily stored for transport (i.e., "Aggregates") using a backlink connection between aggregator 104 and the core network. By aggregating the data from one or more nearby communication devices 110, the aggregator can both (a) help extend network coverage to locations where (i) macro-layer coverage is otherwise either temporarily inadequate or permanently or (ii) macro layer coverage is adequate but devices within a certain coverage area (e.g. cell edge) consume too many resources as (b) transport data over the RAN more efficiently. One of the advantages of temporarily storing data from nearby communication devices 110 is that the backlink connection from aggregator 104 (which can be thought of as a single logical "tube") can be made less "bursty" by reducing the consumption of signal resources and reducing signaling overhead.

Aggregators are typically turned on and off dynamically depending on conditions that affect network performance. These performance conditions include both network conditions (such as interference, load, etc.) and other conditions that could affect system performance (such as the expected level of activity in the cell at a given time or date, the presence and / or number of candidate aggregators at suitable locations, distribution of UEs at cell edge locations, and / or the level of resource consumption by the communication devices in the potential coverage area of ​​the respective candidate aggregators).

In certain cases, the existing macro layer coverage is used for the backlink and a different technology / band than the one used for the backlink is used as a radio interface to extend the coverage to communication devices (mobile) 110 close. The coverage extension, therefore, is supplied to nearby communication devices 110 by aggregators operating "out of band" with respect to macro layer operating frequencies.

In one example, the macro layer operates using LTE carriers in frequency bands around 800 MHz or 1800 MHz, while cell 150 provided by the aggregator to nearby communication devices operates at 2600 MHz. In another example, the macro layer operates using LTE carriers in frequency bands around 2600MHz using FDD technology while the cell extension provided by the aggregator to nearby communication devices operates at 2600MHz in TDD technology. Furthermore, the reader

ES 2 834 577 T3 will appreciate that additional out-of-band frequency bands may be available at frequencies for which no license is required, such as the 2.4GHz and 5GHz bands used by conventional WiFi technologies (i.e., family-compliant). IEEE 802.11 standards) or in the near infrared and visible light spectrum used by light communications technologies, such as visible light communications, VLC (sometimes referred to as "Li-Fi").

Aggregators (and candidate aggregators) can be set to a single location just as conventional small cell base station transceivers are: determining or obtaining a location of such devices is essentially a matter of checking that this fixed state is not applied. has altered. Likewise, and without loss of generalization, it will be appreciated that in many cases the aggregators (and candidate aggregators) are themselves mobile. While in certain embodiments, it is a requirement that the aggregator be static when active, it is also contemplated that the aggregator can be moved to another site and activated at the new site, such communication devices are referred to as "nomads", unlike “fixed” devices. A specific example of a nomadic device arises when the candidate aggregator is installed in a motor vehicle, such as a commute car: the vehicle is driven from a home location (where it can be static) to an office location (where, after the journey is complete, the device can again remain motionless throughout the working day).

The AC 102 is a central logical entity (for example, a server), which may or may not be integrated within the elements of the 3GPP Radio Access Network. The AC 102 monitors conditions that affect network performance to help decide which UE 104 (or other communication devices connected to the network) will act as an aggregator.

Certain implementations of the AC 102 obtain information from all communication devices connected to the network in a given sector before determining which of these devices can act as aggregators by virtue of device status and current location. This determination is repeated for the respective sectors at time intervals: in certain cases, the intervals are equal in duration, while in others, the intervals are of variable duration and can be adapted to the known or predicted behavior of the communication devices using network.

The AC can repeatedly determine whether, under a set of basic criteria (i.e., performance conditions such as network conditions, current location and status of communication devices, etc.), any device in a given sector should go into service as an aggregator at all. The criteria may include a measure of the comparative benefit of introducing an aggregator facility versus not having an aggregator facility in a given industry.

The AC is capable of establishing, maintaining and deactivating communications with the candidate aggregators, that is, those UEs or other communication devices connected to the determined network have the capacity to act as aggregators. This capability (provided through an application layer carried over the macro layer user plane, for example) allows the AC to:

• obtain information from all UEs that can act as aggregators 104, this information may include performance factors such as location and its accuracy, supported RATs and related technologies (such as conventional WiFi technologies, VLC technologies, etc.), supported operating frequency bands, battery characteristics, current battery status and consumption; and / or • provide commands to aggregators 104, such as: commands to configure an aggregator control layer using some specific algorithm depending on the performance conditions such as those obtained from the aggregators 104, to select the RAT / band to be used in such layer, to start transmission, to send commands of handover to aggregated UEs (i.e., nearby communication devices 110 served by aggregators 104), to stop transmission, and / or to send information to the aggregator control layer.

In certain implementations, the AC 102 may communicate with the LTE eNodeB or the 3G RNC in order to "move", through a handover to a specific RAT / frequency, a terminal (or other communication device) that is sets it to act as an aggregator 104. This movement may be a change in the serving cells: in such cases, the communication with the LTE or RNC eNodeB is a request for a handover of the aggregator 104 from a current cell to a neighboring cell: the communication with the eNodeB or RNC It is necessary then, since the handovers are under the control of the LTE eNode (for 3G, the control is done by the RNC). The move could also be a forced reselection: in which case, communication with the LTE eNodeB would be unnecessary.

In certain implementations, the AC 102 may establish additional direct communication with "normal" UEs 110 (ie, those communication devices that are not currently assigned to act as aggregators). This direct communication can be through a pre-installed application, for example configured to collect additional performance information, such as signal strength / quality.

ES 2 834 577 T3 received in cell 100 where normal UE 110s are seated / connected, and / or data on the intensity / quality of signals received in other RAT / bands, and / or location information.

In certain implementations, aggregation-enabled communication devices 104 (ie, aggregators or candidate devices) are also relay nodes. Such devices can transfer data for one group of communication devices connected to the network as a conventional relay node, while serving another group of communication devices connected to the network as an aggregator.

The aggregator 104 is different from a typical relay node in a number of respects. First, the relay nodes are linked to a particular donor cell. They are assumed to be static and fully under the control of the network operator through the eNB provided by the donor cell. Furthermore, the relay nodes are typically operated using radio resources allocated to them by the donor cell and thus integrated into the macro cell scheduling. In logical terms, a connection from a communication device to the core network through a relay node is the same logical connection as that between the communication device and the core network through the donor eNB: a resource that would be allocated within The macro layer for the direct connection from the communication device to the eNodeB is instead assigned to the indirect connection through the relay unit.

The macro layer (ie, provided by eNB 120) and aggregator 104 provide separate logical connections between the Core Network and communication device 110, with aggregator 104 being "configurable" to provide this connection. While the relay node provides an alternate physical route provided that the communication device sits in the relay cell rather than the donor cell, AC 102 ensures that the network can control whether a candidate (or group of candidates) given for the aggregator is enabled (that is, it enters service as an aggregator) and thus determines the conditions under which the communication device switches between a connection established by the RAN and a connection established by the aggregator (when exemplified).

Figures 2A and 2B illustrate a further radio access network where certain communication devices are dynamically assigned as aggregators within a multi-cell network. This scenario demonstrates that the aggregator is not, however, merely a "temporary" base transceiver station. As the aggregator is activated and deactivated for this (that is, opportunistically) based on the need for the RAN as a whole, it is contemplated that certain communication devices 204 seated in neighboring cells 280 could be assigned an aggregator state: in Figure 2B, each aggregator-enabled communication device 204 provides a respective aggregator cell 250.

Such aggregators 204 may be arranged to provide more efficient base station functionality to communication devices in cell 200 that currently serve a conventional communication device 210. While that aggregator 204 would normally be out of range of serving cell 200, it can nevertheless be activated through AC 202.

Since the AC 202 need not be specifically associated with a given cell 200, but rather with a network that may include a plurality of cells (200, 280), the AC 202 is adapted to view the network holistically. By activating aggregator facilities 204 that sit outside the coverage (macro layer) of a cell 200 but still serve communication devices 210 within that cell 200, the AC 202 can still provide a general benefit to the network.

Figure 3 illustrates the functional elements of an aggregator controller 300 suitable for enabling, controlling, and disabling an aggregator layer in the network architecture of Figures 1A, 1B, 1C, 2A, or 2B. These functional elements can be implemented as software routines and / or as dedicated hardware units, these elements being substantially interchangeable.

The functional elements include a communication module 320 for obtaining information from potential aggregators by establishing communication through an application layer with these devices. The information obtained contributes to the factors that affect the performance of the network on which the establishment of a connection between aggregators and nearby communication devices depends, and may include: a current location (for example, location information derived from systems of global or regional satellite positioning, such as the Global Positioning System, GPS, GLONASS, BeiDou / COMPASS, IRNSS or Galileo)); historical information (covering, for example, the last two weeks) of the location of the candidate aggregator; current level of physical mobility (that is, whether or not you move); a measure of LTE radio coverage in the macro layer; an indicator of battery level, current consumption, expected remaining battery, etc .; information concerning the neighboring cells of the aggregator, regarding the connection between the aggregator and the RAN macro layer; and a measure of the expected (or otherwise) improvements, after turning on an aggregator layer in a specific region of the radio network, the improvements that are measured in terms of latency (i.e. data timeout) , for example. This information can be made available at the application layer through an aggregator client application running on the respective candidate aggregator devices.

ES 2 834 577 T3

One reason for obtaining such information relates to the nature of the devices that are candidates. It is likely that many of the candidate aggregators are in fact "nomadic", shifting (ie commuting) between two or more static locations over a period of hours or days. Thus, for many candidate devices, the characteristics of the network will change as they move within the network: a communication device that is a suitable candidate aggregator at a given location, X, and at a given time, T, may not be suitable elsewhere, X + x, at a later time, T + t: specifically if the location is close enough to extend an aggregator cell to the cell border (macro layer) at T, but outside the range of the cell border at T + t. Thus, controller 300 needs to obtain this information to inform decisions as to whether the communication device is (currently) a candidate aggregator and whether, if it is a candidate aggregator, it should be activated / deactivated as an aggregator.

Optionally, communication module 320 can be configured to obtain additional information from communication devices other than aggregators; this additional information that is analogous to the information obtained from the candidate aggregators and that contributes in a similar way to the factors that affect the performance of the network on which the establishment of a connection between aggregators and nearby communication devices depends. A specific non-aggregator client application can be installed on some or all of the communication devices within a network to provide this additional information.

The communication module 320 can also be configured to obtain macro layer information (that is, data concerning network conditions) from the macro layer concerning the current level of resource consumption of programmers, coverage maps and (if available) real-time traffic maps.

The functional elements include a selection module 330 to select (and communicate with) the aggregators to initiate transmission of an aggregator cell and to determine which of the supported frequency bands / technology the selected aggregators are to use in operation.

A monitoring module 340 is also provided to evaluate performance conditions (such as network conditions and other conditions affecting performance) to determine which of the currently selected aggregators will continue its transmission.

In cases where a change in the aggregator is indicated by the monitoring module 340, the selection module 330 can be further configured to select (and communicate with) those aggregators that should stop their transmission (and therefore allow being in service as an aggregator).

When an aggregator layer is enabled in a given sector or cell of a radio network, the aggregator controller first instructs one or more communication devices (preselected to act as aggregators) to begin radiating coverage (i.e. , to implement an aggregator "cell").

In Figure 4, communication device activity near an active aggregator is illustrated. Once a given aggregator begins to radiate coverage to its own cell 405, the behavior of nearby communication devices is adapted accordingly.

Nearby communication devices (i.e. terminals, such as UEs) that are in idle mode, will automatically settle into the newly established aggregator cell 420 (by virtue of the cell's conventional idle mode reselection with the intensity of stronger signal coupled with prioritization of the LTE layers broadcast by the LTE eNodeB). If the nearby idle device thereafter enters an active mode 430, transmission is initiated (or not initiated) over aggregator cell 440. When there is an existing connection in progress through the macro-layer of the RAN (that is, the nearby communication device is determined to be active in the macro-layer) 410, the RAN can optionally, upon request of the aggregator controller, move (ie, transferring) the ongoing communication from the respective nearby device to aggregator cell 415. If such a request is made, transmission is initiated (or continued) on aggregator cell 440.

Figure 5 illustrates the functional elements of a communication device 500 suitable for use as an aggregator in the network architecture of Figure 1A, 1B, 1C, 2A, or 2B.

The communication device 500 includes a memory 510, location unit 520, a processor 540, input / output devices 550, and a network interface unit 560 having a transceiver module 565. Data is transferred between the various components through of a bus 545. To operate as an aggregator, the network interface unit 560, through its transceiver module 545, must be capable of establishing two separate network interfaces: a backlink interface and a coverage extension interface. In certain implementations, the transceiver module operates in at least two sets of frequency bands: a set of bands that correspond to the macro layer RAT and an additional set of "out-of-band" frequencies not used by the RAT. In some cases, communications on the “out-of-band” frequency set use a different RAT than the macro layer.

In certain implementations, the backhaul link and the coverage extension interface could use the same working frequency / RAT as a conventional relay node in order to facilitate the deployment of multi-hop scenarios, in which chains are deployed. of Radio Access Network entities. For

For example, a first aggregator may appear to other communication devices as a Donor eNodeB and a second aggregator may appear to the first aggregator as a conventional UE while providing its own cell to nearby communication devices appearing to them as a conventional Relay Node.

Clearly, the backlink connection from the backlink interface of communication device 500 need not be a cellular wireless connection and may include a non-cellular wireless connection and / or a landline connection using connection technology such as : fiber optic cable technology; Ethernet technologies; a fixed line xDSL technology; a microwave backlink technology; communications with visible light, VLC and / or a Wi-Fi technology.

As noted above, many of the candidate aggregators are anticipated to move between two or more static locations over a period of hours or days. Therefore, it is important that the communication device 500 can, using the data obtained from the location unit 520, provide adequate reports of changes in location, which in turn can inform the controller's decisions regarding if the communication device is considered a candidate aggregator and if, if it is a candidate aggregator, it should be activated / deactivated as an aggregator.

The location unit 520 may include a global navigation satellite system (GNSS) unit, such as a global positioning system (GPS) unit or the like to provide location information for the communication device 500, as well as synchronization of cell if no other methods are available. Alternatively or additionally, the location unit 520 may obtain an inference location "correction" of the RSRP in conjunction with knowledge of the location of the cell sites in the macro layer.

By obtaining a plurality of location corrections from communication device 500 at different (known) times, communication device 500 can determine its current mobility level. The level of mobility can be determined as a binary determination, that is, the device can be "static" or "non-static": clearly, however, a level of non-static mobility can be more finely distinguished by characterizing the degree and nature of mobility situations, for example semi-static / nomadic scenarios, high mobility, static in relation to others (but changing location), etc. Alternatively, the communication device 500 can notify each location correction (along with a time stamp) to the controller and the controller can determine the current mobility level of the communication device 500. In the latter case, the persistent report of the corrections Locator may incur a higher cost in terms of battery usage necessary to facilitate the transmission of such reports.

In certain embodiments, the communication device is not considered a candidate aggregator device if the mobility level is not "static." In other cases, there may be non-static mobility states that nevertheless qualify the communication device to be considered a candidate aggregator device (for example, the detected movement can be determined to be at a speed lower than a predetermined threshold speed, or the change in location may be within a limited geographic area). In the latter case, the controller may determine that an alternative operating pattern (such as selecting aggregator selection routines that are best suited for such non-static rating situations) may be necessary to ensure effective use of communication devices. that have qualifying mobility statuses.

Although not shown, the communication device 500 may be powered from a battery, such as a rechargeable lithium ion battery, conventional in the field of portable cellular communication devices, such as smart phones. The level of that battery can be conveniently monitored. Alternatively or in addition to the mobility criteria discussed above, the communication device may be rejected as a candidate aggregator device if the monitored battery level falls below a battery level threshold.

In the present discussion, it will be readily apparent to the reader that many alternative and complementary factors can be used to determine whether a given communication device can be considered ready to act as an aggregator: the state of mobility as discussed above is one of a set of useful criteria upon which disposition can be determined. In fact, the state of mobility as illustrated, where a simple dichotomy is made between "static" and "non-static" state, is clearly a simplification of a more complex determination of a plurality of categories of "state of mobility" (which it could encompass multiple degrees and / or types of 'mobility', for example).

For a device to be determined to be "aggregator ready," it must meet certain physical criteria (for example, be on, be able to receive and send signals according to an appropriate protocol, etc.) and meet one or more eligibility criteria: for example presenting a state of mobility that allows an efficient aggregator operation. Battery life is a significant example of a physical criterion that would also be considered in determining readiness to act as an aggregator.

ES 2 834 577 T3

Even if there are conditions that suggest that it would be possible to deploy one or more aggregation layers in a cellular communication network, there must be good reason for deciding to configure an aggregator layer: in essence, there needs to be some tangible expected benefit of doing so. instead of persisting with the normal macro layer operation.

Figures 6A and 6B show a flow chart of certain operations performed by a controlling entity in determining whether activation of an aggregator facility is supported.

In step S610, the controller obtains values ​​for one or more cell or user related metrics, referred to hereinafter as "cell metrics", thereby testing the performance of the macro layer. Cell metrics can include, for example, measurements of: cell load (for example, resource block usage (RB)), cell throughput, number of active communication devices located in predefined parts of the cell coverage area, a “happiness” value for users (measured latency in data transfer, uplink time-out or a value obtained by inference from user feedback on social networking services, for example); and / or the use of control resources (eg, the use of PDCCH).

Cell metrics provide a macro layer performance measure that is used in determining whether conditions in a given area of ​​radio coverage offered by a cellular communication network support the activation of an aggregator facility. In this case, the given radio coverage area can be selected from: a macro cell coverage area for at least one macro cell within the cellular telecommunications network; a coverage area for at least one sector within the macro layer of the cellular telecommunications network; and the coverage area of ​​the entire cellular telecommunications network.

In certain cases, the controller can be configured to define the given area of ​​radio coverage that is to support the activation of an aggregator facility by identifying a subset of available cells for which one or more cell parameter conditions are maintained, e.g. For example, more than a given number of cells in the subset have a cell metric and / or user metric less than the corresponding threshold value. This could result in the radio coverage area to be supported by the activation of an aggregator facility being a subset of the cells in the cellular network covering an entire city.

In Figure 6A, for example, this determination involves two distinct steps: step S612, which deals with certain maintained conditions that would make activation of an aggregator facility desirable (even necessary), and step S614, which deals with additional conditions. which would determine whether such an installation would be feasible. In alternative approaches, the conditions supporting the activation of an aggregator facility can be performed in other ways, in particular steps S612 and S614 can be performed in parallel with each other or in "reverse" order; furthermore, all conditions can be evaluated in a single procedure based on cell metrics.

In step S612, the controller determines whether the cell metrics meet the target threshold values. This operation may include: determining if the cell load (ie use of RB) exceeds a load threshold while the flow rate is below a minimum flow threshold; determine if the number of users in a cell region (such as the edge of the cell) exceeds a threshold number of users, while the throughput per application (App) falls below a minimum throughput threshold App (an App is a software application executable on a user's communication device: App that depends on network connectivity can be affected if the allocated throughput is below some threshold, for example, an App streaming video with throughput less than 300 kbps would provide inadequate display output ); determine if a happiness metric (whether aggregated for a number of users or a group of users or not) is below a happiness threshold; and / or determining whether the use of control resources (such as a PDCCH) exceeds a control resource threshold.

If the cell metrics meet the target threshold conditions, the controller concludes that the conditions necessary for the aggregator layer deployment are maintained and moves to step S614.

In step S614, the controller determines whether certain conditions sufficient for the deployment of the aggregator layer are maintained. The controller thus determined whether effective aggregator layer deployment will be possible. Step S614 may include determining:

whether there are aggregator-enabled communication devices (i.e. candidate aggregator devices) in the cell and whether these communication devices have certain characteristics in terms of mobility (e.g. they are, have been for an amount of time and / or are expected that are "static");

if there are communication devices (aggregator enabled or not) in one or more macro cells with certain characteristics in terms of mobility (eg, they are, have been for an amount of time and / or are expected to be "static");

ES 2 834 577 T3 if the controller has access to the data concerning the path loss towards the macro cell and / or between communication devices (for example, UE / terminals) and / or location information of the aggregators and / or the other communication devices;

if there are communication devices in coverage of potential aggregators;

if there is a match between the capabilities (technology / band supported) between aggregators and nearby communication devices;

if at least some of the aggregators have sufficient battery life to maintain aggregator functionality for a predetermined period of time;

if low interference conditions are maintained; and / or if necessary spectrum and technology resources are available for use in aggregator layer deployment.

If the controller concludes that sufficient conditions are maintained for the aggregator layer deployment, the controller then performs operation S616. In certain alternative approaches, the controller performs operation S616 before or in parallel with the operations at S612 and / or S614.

At step S616, the controller makes a preliminary determination of whether a benefit to the network would be expected if the network were to deploy the aggregator layer. This preliminary determination considers a limited number of properties of the cell metrics obtained in operation S610 and, thus, is based on a subset of the information necessary for the display of the aggregator layer: for example, a benefit would be expected at this stage because there were multiple static users on the edge of the cell under the potential coverage of some static aggregators or because there are small cells with unused capacity in an area close to some static users but with aggregators placed in its coverage area.

If it is determined that either necessary conditions (in step S612) or sufficient conditions (in step S614) are not present, the controller waits for a predetermined period of time (by setting a timer, for example) and then obtains a additional set of cell metrics (in step S610). Likewise, if it is determined that no benefits are expected from the aggregator layer deployment (in step S616), the controller will return to step S610 and obtain an additional set of cell metrics.

If, however, in step S616, the controller makes a preliminary determination that there would be an expected benefit, in principle, to the network if the aggregator layer were to be deployed, the controller initiates a more detailed phase of operation (illustrated in Figure 6B) collecting additional performance information, operation S620 (in addition to the cell metrics obtained in operation S610).

During the collection of additional performance information, operation S620, the controller obtains a list of aggregator-enabled communication devices (i.e. candidate aggregators) currently seated within a given macro cell, using received information updates, at time-spaced intervals. , of the aggregators. In addition to the list of candidate aggregators, the additional performance information may include some or all of the following information obtained from the respective aggregators:

• location (of the update aggregator). This location information can be obtained by the aggregator by inference from the RSRP and / or using a GPS unit.

• path loss / SINR (measured in update aggregator). This can be with respect to the current macro cell or to a set of macro cells.

• level of mobility (static or not) measured by the aggregator itself • information about the location and / or path loss of all UEs or other communication devices connected to the network that are static (optionally, this can be filter to relate only to UEs that are static and are also expected to remain static analyzing and using geolocated historical information of the UE) and that are settled / or are / have been connected there

The controller processes some or all of this performance information to evaluate the relative distance and path loss / SINR (or similar quality) between the candidate aggregators and the user devices in the cell.

In certain embodiments, the controller selects aggregators from aggregator-enabled communication devices according to a single aggregator selection algorithm. In other embodiments, there may be a plurality of aggregator selection routines (ie algorithms) available and it is first necessary to determine which routine to adopt. When required, the operation of determining which routine to use can be any conventional selection operation.

ES 2 834 577 T3

Figure 6B illustrates an embodiment in which a plurality of aggregator selection routines are available. In this case, the respective available aggregator selection routines can each be tailored to the respective different performance conditions. In step S622, an algorithm corresponding to one of these routines is determined depending on the availability of specific additional performance information, such as aggregator location information or path loss measurement data. In cases where only a single aggregator selection algorithm is available, determining which algorithm to use is trivial and step S622 can be omitted.

Once it is determined which routine (that is, algorithm) is appropriate to the additional performance information available, this algorithm determines, if any, which aggregator-enabled devices should be activated for aggregator functionality and defines the threads using the which profit (i.e. achievable profit) will be calculated from the aggregator layer deployment. The algorithm thus serves to select aggregators from among candidate aggregators for aggregator layer deployment. The operation of this algorithm is illustrated as operation S624 in Figure 6B.

At step S624 (whether this is the only aggregator selection routine available or a routine that is determined to be suitable for the additional performance information available at step S622), the controller makes a selection from among the monitoring devices. communication enabled with aggregator, this selection being a selection of one or more aggregators based on either the individual characteristics of the respective selected aggregators or the collective characteristics when the selected aggregators are considered as a selected group from among aggregator-enabled communication devices.

While the present embodiment contemplates the use of a single aggregator selection routine within a single area, this does not preclude the use of more than one selection routine, for example, the use of a first aggregator selection routine during peak hours of the day or week and a second aggregator selection routine at other times. Furthermore, it is also contemplated that when two radio coverage areas are considered separately, each area may adopt a respective different aggregator selection routine consistent with information regarding the candidate aggregator devices that can be obtained.

Thus, it is possible that the choice of the aggregator selection routine can be set based on empirical knowledge (using routines for which sufficient information has historically been available, because the penetration of terminals that support a client application of network operator has become sufficiently high, say) or dynamic (based on how much information is currently available for each routine).

It is further contemplated that the choice of which selection routine to adopt may be governed by a quality metric of the effectiveness of any given routine based on the amount of relevant information that can be collected. Obtaining information that could be used by one or more of the possible routines and discarding the routines for which the information available is such that its quality metric is too low, the routine whose quality metric implies that it can provide the higher gain for the network.

In certain embodiments, the aggregator selection includes the selection as a group of some or all different possible groups or subsets of aggregator-enabled communication devices, each group being referred to as an "evaluation group." An expected gain is then calculated for each evaluation group.

In other embodiments, the aggregator selection is the selection of individual devices (ie, subsets of aggregator-enabled communication devices that each have a single member). In this case, the expected profit is calculated for each individual candidate aggregator.

The expected (achievable) gain results from an evaluation of the expected improvement in a given cell metric: this cell metric can be the, or one of, the cell metrics obtained in step S610. For example, the expected gain may be the result of a comparison between a) the value of that given cell metric when the or each aggregator is selected and b) the currently experienced (that is, measured) value of that cell metric.

In certain cases, the expected gain can be expressed as the difference between the value of a given cell metric predicted for a given evaluation group (evaluated before actually activating that group for aggregator functionality) and the current value of the metric of given cell. When aggregator-enabled communication devices are not activated, the current value of the cell metric is the measured value of the cell metric for the cellular communication network where no aggregator functionality is activated. Otherwise, the current value of the cell metric is the measured value of the cell metric for the network in which a current group of aggregator-enabled communication devices are activated for aggregator functionality, such current group does not need be the evaluation group. The prediction of the cell metric may be a function of the additional performance information collected in operation S620.

When the expected gain is determined for evaluation groups or individual candidate aggregators, the aggregator selection algorithm then evaluates the respective expected gains for some or all of

ES 2 834 577 T3 the different aggregators or groups of aggregators possible, the aggregator or the group of aggregators selected can be the individual or the group that provides the highest expected gain. Alternatively, the selected aggregator or group of aggregators can be selected from a subset of groups that have gains that exceed a threshold gain, taking into account other practical constraints such as keeping aggregators that are already active, unless there is a good reason for stopping them (for example, battery level falling below a level that can support continuous operation or detected movement of the active aggregator).

In step S626, the controller makes a full determination of whether a benefit to the network would be expected if the network were to deploy the aggregator layer by modeling network performance for a network with the selected aggregator or aggregator group enabled and comparing that performance with the currently measured network performance information (as collected in step S620).

In the case of aggregator selection using evaluation groups, the complete determination of the benefit to the network involves comparing the expected profit from using the selected evaluation group of aggregators with data representative of current network performance.

In a specific example where one of the selected subsets of aggregators is not currently active, sufficient benefit from the first activation of that selected subset would be confirmed where the measured value of a given cell metric (assuming the cell metric given is the one used in the algorithm in step S624) is significantly higher than the cell metric measured before activation.

In another example when the aggregator layer is on (that is, at least a subset of aggregator-enabled communication devices are turned on for aggregator functionality), sufficient profit is confirmed when the gain is higher than one of a metric reference average (for example, historical data) or a cell metric measured in the last N previous iterations, where N is an integer greater than 1.

In certain cases, a measured value of a first metric (metric A) is used before activation, whereas after activation, a different second metric (metric B) is used instead. Known pre-activation network performance indicators (often referred to as KPl, or Key Performance Indicators) are used for the purpose of evaluating the A metric. The estimated values ​​of the A metric are compared to the known measured values ​​of the A metric to indicate whether the network needs assistance and to deduce that the activation of the aggregator layer will provide that assistance. After activation, the B metric can be calculated using both the previous activation of the stored KPIs, as well as the current KPIs measured after activation. If the B metric after activation is sufficiently better than the B metric before activation, the aggregator layer remains active.

If the determination in step S626 is that a net benefit is indeed provided by deploying the selected device or group of devices (i.e., subset) as the aggregators, the controller activates an aggregator server (step S628) to support the aggregator and instructs each of the selected communication devices to activate (or keep active) their respective aggregator functionalities (for example, running a routine in an aggregator client application). These aggregator functionalities include functionalities consistent with operation as a MiFi architecture access point (offering the WiFi protocol and / or VLC connectivity to nearby communication devices) and / or as a small cell (offering connectivity using a standard of cellular telecommunications).

While not illustrated in Figure 6B, the controller may conveniently launch a RAT selection routine to determine which carrier / RAT / band bandwidth will be used by each aggregator (selected), the carrier / RAT bandwidth / band will be chosen from one or more permutations of RAT, band and available carrier bandwidth, available for the implementation of an aggregator layer in a specific cell. For example, the RAT select routine may determine that since LTE's FDD2.6 is not used in the current and / or neighboring macro cell, it can be used by all selected aggregators within the range of those cells.

As discussed in connection with Figure 4, nearby communication devices may transfer some or all of their data traffic to the selected aggregator (s) differently depending on whether they are in the "idle" or "connected" state.

In the first case, the transfer of inactive devices can be facilitated by the controller modifying the neighbor cell list (NCL), which is provided to the devices in inactive mode, with the parameters of the selected active aggregators.

In the latter case, the controller can determine whether to request a handover for a device in the connected state when information, just as the radio measurements of the communication devices in the macro cell compare unfavorably with the radio measurements of the communication devices used by the selected aggregators (always provided that such information is available and could be accessed by the relevant RRM function of the eNodeB / RNC in the macro cell). Examples of communication devices for

ES 2 834 577 T3 which a handover could be requested include those devices: a) that are in the coverage area of ​​a specific aggregator or aggregators and b) that have a channel quality indicator (CQI) and / or RSRP in relation to the macro cell which is worse than that of the aggregators.

Although not illustrated in Figure 4, the aggregator may alternatively (or additionally) offer the WiFi protocol and / or VLC connectivity to nearby communication devices (thereby operating as a MiFi architecture access point). In such cases, the handover over aggregation functionality can be effected by informing the respective nearby communication devices whose aggregators offer an access point in the cell and ordering those communication devices near the identified access points to enable Wi transmission. -Fi.

Optionally, the controller can then seek to optimize the aggregator layer, step S630.

Driver optimization can include at least one of the following:

• check, once a given nearby communication device is connected to an aggregator, whether that device has a worse CQl / SINR / RSRP with respect to the macro cell than with respect to the aggregator, and in such case it will be (or may be ) passed on to the Macrolayer (for example, by issuing a handover command or releasing the aggregation connection with redirection). Conveniently, the selection parameters for this device would be changed for an amount of time to avoid unwanted ping-pong effects (ie, hysteresis);

• check the performance at the aggregator layer versus the performance that would be expected if a given communication device were to remain in the macro layer, depending on what information can be made available to the controller and / or aggregator. Examples of performance information that can be verified include user happiness metrics measures such as: latency (i.e. round trip time (RTT) for packets transmitted and received or uplink timeout . Examples of performance information that can be verified may also include: historical data (such as throughput for specific applications) obtained in the macrolayer at a similar or the same location and under the same or similar RSRP / CQI conditions;

• check the level of interference and / or availability of resources for the spectrum / technology used in the aggregator layer and take actions to improve these parameters (for example, create groups of use of spectrum / technology, reduce the use of those resources in the macro layer); and • optimize the selection of aggregators taking into account mobility. Aggregators themselves may be required to take certain actions when added users (that is, communication devices using the aggregation facility of a selected aggregator) initiate mobility. Likewise, when the aggregators themselves become mobile, the controller can act to alter the performance of the aggregator later, for example by instructing the new mobile aggregator to turn off aggregation functionality.

Checking the performance at the aggregator layer using RTT may involve comparing RTT for the same packet using the macro cell and the current aggregation layer service, respectively. Using the uplink timeout to check performance may involve comparing this time before and after optimization.

Testing performance at the aggregator layer using historical data may involve comparing historical data with actual data obtained through the aggregator. It is also possible to run periodic speed tests just to check the current quality.

Whether or not optimized as described, the controller iterates again through operations S622, S624, and S626, selecting one or more aggregators that may be identical to the aggregator (s) selected in previous iterations or may represent a group that has a different constitution of aggregator-enabled communication devices.

Periodically, cell metrics are checked, step S632, and this information is used in further iterations of steps S622, S624, and S626. The cell metrics checked here can be the same as those obtained in operation S610: they can also be different from those cell metrics.

If the determination in step S626 is that a net benefit is not actually provided by deploying the selected devices (or group of devices) as aggregators, the controller stops using the aggregator layer operation S640. This may involve instructing all aggregator-enabled communication devices in the cell to deactivate their aggregator functionality and deactivate the aggregator layer server in the controller.

ES 2 834 577 T3

After a second predetermined time (typically longer than the typical period of the iteration of operations S622, S624 and S626), the controller restarts the first phase of determining the preliminary benefit of the deployment of the aggregator layer in operation S610 .

To provide the information needed by the controller to perform the operations described in Figures 6A and 6B, the communication devices are arranged to present information on which the controller can make its respective determinations of the suitability of the device as a candidate aggregator and whether it has been to activate (or deactivate) a suitable candidate.

Figure 7 shows an exemplary flow chart showing certain operations of a communication device according to one aspect of the present disclosure.

In Figure 7, the communication device evaluates its current location at time-spaced intervals (eg, every T1 seconds). Once there are at least two location measurements (ie location corrections) it is possible to determine if there has been any change in the mobility state of the communication device. Any given location correction is conveniently obtained with a minimum level of precision. The time difference between the acquisition of the location corrections is used to determine the degree of mobility (if any) between two corrections. To ensure that the corrections are far enough apart in time for significant movement to be detected, each correction is conveniently associated with a corresponding timestamp (which can be acquired from a connected macro cell and / or within the signaling structure of GPS). When more than one communication device is used, it is contemplated that they can operate in a synchronized manner.

An initial location correction is obtained at time T0, step S710. At a point in time T1 seconds later than T0 an additional location correction, S712, is obtained.

The separate T1 second location corrections are compared to determine whether there has been a change in the detected location, step S720.

In other embodiments, the algorithm used to determine if a change in a location has occurred may alternatively or additionally use parameters other than the reported position and time, eg, direction of movement or altitude.

In general terms, a potential aggregator can be considered to have moved (that is, changed from a “static” state to a “non-static” state) if its position moves a distance of D meters over a time interval T ¡-T (¡- 1), where D and Ti can be determined, calculated, flagged, or otherwise obtained dependent on parameters (eg, current mobility state).

When the location has changed between corrections, the mobility state is set to "not static", step S722. For the sake of clarity, the scenario illustrated in Figure 7 shows the determination in the S720 operation as binary between "static" and "not static", based on any detected change in location. The skilled reader will readily appreciate that alternative determinations, having more than two cases or indeed two decided cases of different criteria, can be substituted for the current S720 operation without requiring any other alteration to the flow chart. For example, the location change between corrections can be recorded as indicating a "non-static" state when the location has changed by more than a minimum position change threshold of D1 meters since the last location correction.

When in the non-static mobility state, new location corrections are sent to the controller, step S724, and an additional location correction is taken after an interval of T2 seconds / minutes, step S726. Typically, the T2 timescale is greater than Ti, but it could be equal to or less than Ti: sending updates will use power, compute, and signaling resources, etc., so this task would be performed less frequently when the information more recent is that the device is on the move (and presumably not currently under consideration as a candidate aggregator). The operation flow then returns to operation S720, where it is again determined whether there has been a change in the detected location. In this way, the location is still checked in case the mobility status has changed to "static". If the communication device has become static, but the latest report still indicates that its state is "not static", the use of a T2 greater than Ti will merely result in a slight delay in considering it as a potential candidate for activation.

When the location has not changed between corrections, it is determined that the mobility state may be "static", but additional corrections are required to be more accurate. In the illustrated case, it is considered that a communication device needs to have been static for a period longer than the interval of T1 between successive corrections in the S710 and S712 instructions (during initialization) or the interval of T2 in the S726 operation ( in subsequent iterations).

To avoid a situation of “false” attribution of “static” status to a device (which can be incorporated after all in a vehicle) just because the device has been temporarily stopped (for example, a car that has stopped at a traffic light , for refueling or in heavy traffic, or a car that has been parked

ES 2 834 577 T3 temporarily), the communication device obtains an additional location correction in time N * T3 seconds later, where N and / or T3 could be dependent on the type of communication device (for example, in a car , residential) or type of installation scenario (for example, in a bus terminal, in a scenario that is likely to be static), S728 operation. For example, if the scenario is likely to be static, it may be appropriate to set N or T3 equal to or close to zero, as an earlier indication of "static" status in the S720 instruction can be assumed to be likely correct. .

The location corrections N * T3 seconds apart are compared to determine whether there has been a change in the detected location, step S730. If at the end of period N * T3 the position has not yet changed, the mobility status is set to "static", step S732. The current (static) location correction is sent in a report message to the controller, step S734. Optionally, the communication device can also indicate that it is in the "static" state (either in the same report message as the S734 instruction or in a separate status report message), S736 operation. This option can be considered convenient to the extent that it makes it easier to understand why the location correction was reported. Alternatively, the controller can infer that because it has received a report message that has a location correction from the communication device, it can conclude that the report communication device is static.

When location corrections are derived from GPS-based position marking, the location correction can be sent as GPS location information (i.e. based on the WGS84 standard) instead of just latitude and longitude. Conveniently, the report message may include an indication that the location information is in a GPS position format. Alternatively or additionally, the report message may include an indication that GPS information is available, regardless of the source of the reported location correction.

A report message (either the same report message as the S734 operation or in a separate additional information report message) can optionally include additional information, for example: candidate aggregator details: for example, device model, information version of software, hardware identifiers, etc. device status, such as battery status; and / or radio information, such as the Seated Cell ID, Radio Coverage Quality, CQI of the radio channel used to carry out such communication, neighboring cells for the modem of the communication device, etc.

The flow then iterates, while the communication device is in a "static" state of mobility. The communication device obtains an additional location correction after an interval of T4 seconds, step S740. T4 is typically a shorter period of time than T2, since it is desirable to avoid a communication device being considered "static" when in fact it is "non-static": any static communication device is a potential candidate aggregator, so any False attribution of "static" state can have a detrimental effect on the delivery of an effective aggregator layer. The operation flow in the "static" mobility state then returns to operation S730, where it is checked once more if the detected location has changed. Any change in location results in the mobility state being set to non-static and that location corrections are taken at T2 (rather than T4) intervals.

In a further arrangement of the present disclosure, more than one aggregation layer is activated within the network. In certain cases, the respective aggregation layers are turned on and off in the corresponding sectors or groups of sectors of the cellular network. In certain cases, the aggregation layers are established within a sector or cell that extends the coverage of that sector or cell to encompass communication devices served by neighboring sectors or cells: in this way, the benefit to the network of the deployment of any A given aggregation layer can be calculated for a region of the radio coverage of the cellular network that includes more than one sector and / or cell.

Certain provisions of the present description refer to the dynamic activation of one or more communication devices to provide an aggregation layer. Each of the one or more communication devices appears in the macro layer as a UE; while for other communication devices, each appears as a kind of small cell base transceiver station. The dynamic activation is due in part to the determination of whether a benefit could be expected from such dual UE / small cell activation: that could arise if the macro layer does not provide a quality of service prerequisite to the other communication devices. Dynamic activation also requires finer-tuned determination dependent on selecting a set of devices capable of dual UE / small cell or UE / MiFi functionality for activation and determining whether the network would benefit from the activation of that particular group. Only when it is determined that the network benefits based on this detailed determination will the selected communication devices be activated as hybrid UE / small cells (or UE / MiFi devices).

Similarly, certain embodiments of the present disclosure refer to the dynamic deactivation of an aggregation layer provided by certain communication devices.

Considering once again the simplified example of a binary determination of whether a communication device is in a "static" or "non-static" state, it is clear that once an aggregator device has activated an aggregator mode (and irradiates a small cell , VLC or WiFi coverage, for example) is desirable

ES 2 834 577 T3 monitor the location of the device in case there is a change in that mobility state and a method to deal with the change in mobility state: the "non-static" state that is supposed to be incompatible with effective aggregator functionality .

This scenario is illustrated in Figure 8.

Once the communication device has been activated, the communication device monitors its location every T5 seconds (obtaining an initial location correction in step S810, if necessary, and additional location corrections in step S812). T5 needs to be a very short time, as it is crucial to determine as soon as possible if the communication device is still "static", since network performances can be affected. Note that this may be the same iterative monitoring of the mobility state as in the S740 operation of Figure 7 or a different iteration at a specific different time interval to monitor the operation of the active aggregator devices.

The location corrections obtained in steps S810 and S812, step S820 are compared, and if the location changes (to a predetermined degree of precision, etc.), the communication device will immediately ban the cell (so that the UEs in idle will not connect), operation S830 and will send handover commands to all communication devices connected to the aggregator cell and to the macro cell. The handover procedure from the aggregator cell to the macro cell can then be handled according to any conventional standardized handover procedure.

The communication device sends the handover command because it effectively operates as a base station for the aggregator cell when activated.

The cell ban is important in order to prevent nearby communication devices in idle mode from trying to connect to the cell irradiated by the communication device, while that cell is still being irradiated, to support the handover operation, for example.

Conveniently, the deactivation aggregator device sends a message to the controller including an indication that the aggregator state has been released giving the cause as "mobility". In addition, the deactivation aggregator device can then update its mobility status to "not static".

The communication device can additionally monitor its battery life every T6 seconds. As noted above, a low battery level can prevent the communication device from being considered a candidate for activation. If the expected remaining battery life is less than T7 seconds / minute, the active communication device can conveniently gradually deactivate the aggregator mode by performing operations similar to operations S832 and S834. In this case, however, the handover commands will run, and confirm completion, one at a time, before sending additional handover commands.

As will be apparent from the discussion above, it is assumed that the interactions between the controller and the communication device are governed by a shared communication protocol.

Using this protocol, the controller can send requests for information to one or more communication devices (aggregators), specifying any additional information it wishes to receive.

The communication device uses the shared protocol in the same way to respond to such requests for information, providing the requested information, which may consist, for example, of the following:

• Mobility Status • Specific details of the communication device: for example, device model, software version, hardware identifiers, and so on.

• Device Status: battery status • Radio Information: Service Cell ID, Radio Coverage Quality (for example, Service Cell RSRP, Service Cell RSRQ, etc.); CQI of the radio channel used to carry out such communication, Neighbor cells for the UE modem • Radio measurements executed on neighboring cells, cells detected on other LTE frequencies that are not part of the neighbor list, Wi access point identifiers -Fi (i.e. SSID) and intensity detected on the Wi-Fi receiver

Conveniently, the communication device can keep a protocol connection open by sending dummy bits for the next Z seconds, otherwise it stops sending dummy bits.

Using this protocol, the controller can also send commands that instruct the communication device to enter the aggregator state (i.e. either as a small cell and / or as a dot

ES 2 834 577 T3 of Wi-Fi access). The communication protocol for such a command includes a configuration command (sent to the communication device) that provides the following information: the LTE carrier to be used for transmission and the main parameters; transmission, TX, power to be used: (default is “MAX TX Power); optionally, a parameter to configure a second carrier; optionally, a parameter to configure a Wi-Fi access point; time of day the cell will begin to irradiate; parameters needed to manage the state of the local algorithms within the communication device while it is in the aggregator state.

Once the command to enter aggregator mode is received, the communication device uses the shared communication protocol to obtain, from a controller database or a database within the OSS server, the necessary parameters to configure the aggregator cell: for example, IP addresses (if not derived with a fixed rule from the R-UE IP address). Alternatively the communication device can use the parameters used the last time it acted as an aggregator, provided that some criteria are still met: for example that the location is still the same as the last time; that, although the location has changed, the RAU is still the same; that although the location has changed, the UK settled in the same cell as last time.

Once the communication device has the necessary information to configure the aggregator cell, it prepares its transceiver module (565, Figure 5) to be ready to irradiate. The communication device then begins to radiate at the requested Time of Day. The communication device then confirms to the controller that it is radiating (ie aggregator mode is active).

While the communication device is in the aggregator state, the communication protocol can also be used by the controller to request the provision of additional information, such as: Battery status; Number of communication devices connected; occupation of Average Resource Blocks; Average CQl of connected UEs; and average CQI of the connected modem.

Figure 9 illustrates a scenario where a method according to the invention can be implemented, where currently the second communication devices 902 are not acting as aggregators. In particular, the second communication devices 902 and the first communication devices 901 are shown in a telecommunications network comprising a central controller 903; In Figure 9, the central controller is in communication with an eNodeB 904.

Central controller 903 is configured to activate second communication devices 902 to broadcast beacon signals. The RF bands that can be used can be close to, for example, 2.6 GHz either as FDD LTE2600 or as TDD LTE2600. The transmit power can be set by the central controller 903 or, if this is not possible, the second communication devices 902 can communicate to the central controller that the transmit power is being used via Wi-Fi or Bluetooth.

The first communication devices are commanded to scan and listen to the Bluetooth Wi / Fi band, and to report 906 to the central controller 903 of the signal strength received by any second communication device 902 or potential aggregator.

The central controller 903 is capable of constructing a complete path loss map between the first communication devices 901 (active or inactive) and the second communication devices 902 or potential aggregator, and use this information to select the aggregators according to the implemented method. to be added.

In one example, potential aggregators periodically activate or deactivate an application comprising means for implementing a method according to the invention, for example, a Crowdnet layer (TDD or FDD2, 6) in forbidden state; the candidate terminals to be added are requested by the telecommunications network to measure these bands while they are in connected mode and report the discovered Cells and, if possible, the signal level to the eNodeB).

Knowing the transmitted power as well as the power level received by the communication devices makes it possible to define a path loss between each potential aggregator 902 and each first communication device 901; for example, if the received signal is low, it may mean that there is too much distance between a specific potential aggregator 902 and a first communication device 901 and, as a consequence, the path loss is high.

A small part of the FDD or TDD spectrum of the networks can be dedicated to the activity of sending the temporary signal. Advantageously, this reduces the potential interference towards a serving aggregator from potential aggregators during the implementation of a method according to the invention.

There may be alternatives for the first communication devices 901 to report 906 measurements to the central controller 903: All the first communication devices can be instructed to report to the CN and the second communication devices or aggregators using 3GPP mechanisms to report the observed TDD or FDD cells used by the Participatory RAN (a network of terminals that act as Points of Access / Small Cell that turn on dynamically depending on availability, battery life,

ES 2 834 577 T3 location, expected benefits, etc.) and the carriers detected in an area, and then that sends all this information to the central controller 903.

In another alternative, some of the communication devices may have an application installed that either

- it connects with a set of chips that orders to report the TDD / FDD cells used by the Participatory RAN and detected, or

- opens the Wi-Fi receiver and observes the applications detected in the area and reports the measurements to the central controller 903.

Communication devices around an aggregator may be the ones instructed to report to the central controller. In an alternative embodiment, only communication devices within a specific area can be instructed to report to central controller 903.

Communication devices 901 to be added potentially need to measure the quality of coverage that they could get from an aggregator 902 before the aggregator has gone into service.

The received signal or power may be that which is reported 906 back to the central controller 903. The quality of the received signal may also be reported. In addition, this information can be reported using a 3GPP mechanism, for example, the LTE specification inherently supports a self-organized network, SON, in which features such as Automatic Neighbors Relation (ANR) use the normal measurement report including the cells that are not part of a neighbor list. Alternatively, Wi-Fi can be used as a beacon. It can be started through a dedicated application for which a design for a reporting method can be implemented, for example reporting periodically in an area where it is expected to have a participatory RAN.

The coverage map can be created in the following way: the central controller 903 can know the transmission power TX of the second communication devices 902 on the carrier that they use as beacon; this carrier can be the TDD or FDD carrier used in the Participatory RAN, or the second carrier used for beacon purpose, or the Wi-Fi carriers used as a beacon. Central controller 903 then calculates path loss = TX power - RX power.

Figure 10 illustrates a scenario where a method according to the invention can be implemented, where currently the second communication devices 1002 are acting as aggregators. The central controller may be an aggregator controller 1003; a telecommunications network may comprise one or more participatory RANs 1006; the aggregator controller 1003 and can send an instruction to the second communication devices 1002 to broadcast beacon signals in one or more specific RF radio frequency bands, so that the first communication devices 1001 make measurements in such a way that it can be changed current configuration, due to certain conditions reported from eNodeB 1004 to central controller 1003.

As illustrated in Figure 10, a series of aggregators 1002 may be available in a specific cell to provide a coverage area to serve a series of first communication devices 1001 that are currently connected through the network through the eNodeB 1004 or the Macro Cell.

In one example, a central controller 1103 within a telecommunications network implements the following method steps:

- activating (810) one or more second communication devices (1108) to broadcast beacon signals (1105) in one or more specific RF radio frequency bands, wherein the beacon signals (1105) allow one or more first communication devices communication (1101) make measurements;

- receiving in the central controller (1103) measurements of the one or more first communication devices, said measurements based on the beacon signals (1105) received in said one or more first communication devices (1101); Y

- creating, using the measurements, by means of the central controller, a coverage map, wherein the coverage map is indicative of the coverage (that the second communication devices (1108) can provide for the first communication devices (1101).

It will be appreciated that, although various aspects and embodiments of the present invention have been described thus far, the scope of the present invention is not limited to the particular arrangements set forth herein and is instead extended to encompass all arrangements, and modifications and alterations thereto, which fall within the scope of the appended claims.

For example, while the embodiments described in the preceding description refer to LTE, it should be noted that the described aggregator architecture can be equally deployed in telecommunications networks based on other cellular telecommunications architectures, for example 2G, 3G, Advanced LTE. (3GPP version 10 forward), future architectures (eg 5G), as well as WD-CDMA and WiMAX. The aggregator architecture is agnostic for the specific type of RAN used. In other words, the aggregator / entity controller

ES 2 834 577 T3 controller is adapted to work with any RAN and / or combinations of RANs. This is, for example, one of the reasons why, in certain embodiments, the aggregator / controlling entity controller is independent of the RAN. Similar remarks apply to the communication device to provide an aggregator facility.

Furthermore, it will be apparent to the reader that the term radio access technology (RAT) can be extended to include related technologies, such as conventional WiFi technologies (i.e., conforming to the IEEE 802.11 family of standards) and / or VLC technologies, where the context requires or allows this.

Furthermore, while the above description describes the aggregation layer as providing a bridge to the cellular network for communication devices that are at the edges of cells, the skilled reader will appreciate that "black spots" of dynamic coverage can arise in other parts within radio coverage regions (for example, due to equipment malfunctions, unusual usage patterns, and / or characteristics of the natural or built environment).

The reader will further appreciate that the aspects of the preceding description apply equally and without loss of generality to aggregators (and candidate aggregators) that are fixed in a single location as to aggregators (and candidate aggregators) that are in a state of mobility. alternative: such as nomadic or mobile.

It will also be well understood by those skilled in the art that while the described embodiments implement certain functionality by means of software, that functionality could likewise be implemented solely in hardware (for example, by means of one or more ASICs (Application Integrated Circuits). specific)) or actually by a mixture of hardware and software. Therefore, the scope of the present invention should not be construed as being limited only to being implemented in software.