Classifications

• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W16/00—Network planning, e.g. coverage or traffic planning tools; Network deployment, e.g. resource partitioning or cells structures
  • H04W16/14—Spectrum sharing arrangements between different networks

Definitions

• the present invention enables to preventively reconfigure, by a spectrum manager connected to a network of spectrum managers, the channels used for transmission and / or reception by a radio base station of a secondary user, so as to avoid interferences with primary users.
• Figure 1 shows an architecture for detecting a primary user according to the state of the art.
• a multiplicity of RF sensors RFS is deployed over a geographical area.
• a spectrum manager e.g., a SAS server in the case of the 3. US 5GHz band
• the spectrum manager then reconfigures the network of secondary users (e.g., switches off radio base stations or requests radio base stations to reduce their transmission power), in order to prevent interferences with primary users.
• This reactive approach introduces a delay between detection of the primary user and completion of the reconfiguration of radio base stations, during which mutual interferences may impact both primary and secondary users.
• This reactive approach may result in a bad user experience for users connected to radio base stations of secondary users, since there is no time to gracefully transition those users to other frequencies for transmission or reception.
• This invention provides means to overcome those limitations, by exploiting the information on channels reconfiguration, broadcasted by other radio base stations, in order to preventively initiate a reconfiguration, while protecting privacy of primary users.
• Figure 1 shows an example of architecture according to the state of the art.
• FIG. 2 shows an example of architecture on which this invention is applicable.
• Figure 3 describes the steps to determine when to preventively reconfigure a radio base station according to the present invention.
• Figure 4 shows an example of Reconfiguration Report.
• Figure 5 shows an example of Reconfiguration Policies.
• Figure 6 shows an example of preventive reconfiguration according to this invention.
• Figure 2 illustrates an example of architecture on which the present invention is applicable.
• This figure shows a deployment of radio base stations, labeled ST, belonging to the same or different operators.
• Each radio base station is capable of communicating over a radio interface, for example with end user devices, labeled Dl to D4.
• RF sensors RFS capable of sensing radio frequencies and detecting radio frequency signals, may be deployed within the proximity of radio base stations ST, collocated with radio base stations ST, or embedded within radio base stations ST. Each RF sensor is connected to a spectrum manager SM.
• sensing data retrieved by a third party sensor network could be provided to spectrum managers.
• a third party sensor network e.g., the ESC - Environmental Sensing Capability - in the case of the US 3.5GHz band
• the spectrum manager provides radio base stations ST with the allowed frequencies for transmission and reception.
• Spectrum managers are connected with each other and capable of exchanging information, for example through an IP network. The information exchanged among spectrum managers is used to determine which frequencies to allocate to each radio base station ST.
• FIG 2 shows an example of architecture where spectrum managers are distributed.
• each spectrum manager is responsible for allocating frequencies to one single radio base station ST.
• the spectrum manager could be physically collocated with or embedded within the base station ST.
• Communication between spectrum managers and RF sensors can be performed using a direct physical link, or wirelessly (e.g., using Wi-Fi or LTE).
• Some spectrum managers may be connected with multiple RF sensors.
• some spectrum managers may be connected with no RF sensor.
• Spectrum managers may communicate with radio base stations through an entity managing the network of radio base stations ST. In the case of a 3GPP network, this entity can be the Network Manager. This is illustrated in Figure 1 by SMI communicating with ST1 through interfaces [C2] and [C3].
• spectrum managers may communicate directly with radio base stations, for example through an IP network. This is illustrated in Figure 2 by SM2 and SM3 communicating with ST2 and ST3 via interface [CI].
• Radio base stations not managed by a spectrum manager or whose spectrum managers are not connected to the spectrum managers of stations ST1 to ST3, labeled FST in the figure, may be deployed within the same geographical area.
• Devices communicating with those radio base stations, labeled FD1 to FD4 are also shown in this figure.
• Figure 3 illustrates the steps performed in order to preventively reconfigure a radio base station according to the present invention.
• This reconfiguration may be the result of the detection of a primary user in the vicinity of the radio base station associated with the spectrum manager.
• this reconfiguration may be the result of a request from the radio base station for more bandwidth for transmission or reception, or the result of a decrease in bandwidth resource needs at the radio base station.
• a reconfiguration report may contain, for example:
• Figure 4 shows an example of Reconfiguration Report.
• channels 1, 3, and 4 were deallocated, and channels 6 and 7 were allocated to the radio base station.
• some information provided in Reconfiguration Reports may be encrypted (e.g. using the public key of an operator's certificate) so that it is only accessible (e.g. using the private key of an operator's certificate) to spectrum managers associated with radio base stations of the same operator.
• the Reconfiguration Report is broadcast over the network of spectrum managers and stored locally.
• Each spectrum manager receives all the Reconfiguration Reports that are broadcasted over the network that connects them.
• This step is initiated every time a Reconfiguration Report is received.
• the spectrum manager uses the information included in Reconfiguration Reports, as well as the current operational parameters of the base station stored in the spectrum manager (e.g., currently allocated channels), in order to determine whether the radio base station needs to be preventively reconfigured, according to the Reconfiguration Policies stored at the spectrum manager.
• the Reconfiguration Policies provide a set of criteria that must be fulfilled in order to initiate a preventive reconfiguration.
• This primary user may be mobile and therefore, potentially move within proximity of the radio base station connected to the spectrum manager that received those Reconfiguration Reports.
• the parameter "Minimum Received Reconfiguration Reports” indicates the minimum of Reconfiguration Reports that must be received, indicating that a given channel has been deallocated, in order to initiate a preventive reconfiguration.
• the preventive reconfiguration may consist in requesting the radio base station not to use the given channel and to allocate a new channel to the radio base station, if such channel is available.
• the spectrum manager may simply send a notification to the radio base station indicating that the given channel may be deallocated in the near future.
• the radio base station may use this information, for example, to give less priority to this channel when allocating bandwidth for downlink or uplink. This enables to minimize the degradation of quality of experience in case a primary user using this channel moves within the vicinity of the radio base station.
• a validity period may also be provided by the spectrum manager in the notification, or pre-configured at the radio base station, indicating the duration during which the radio base station should take into account the received notification. The farther a primary user is located from a given radio base station, the smaller is the probability that this primary user will move within the proximity of this radio base station.
• the "Minimum Received Reconfiguration Reports” parameter may vary according to the distance.
• the "Minimum Received Reconfiguration Reports” may vary according to path loss.
• a maximum distance between two radio base stations may be configured, beyond which two Reconfiguration Reports received from spectrum managers associated with those base stations are considered not related to the same potential primary user.
• a maximum path loss may be defined, enabling to take into account the impact of the environment in the estimation of the propagation range of primary user RF signals.
• the "Minimum Received Reconfiguration Reports" parameter may vary according to the density of the deployment of radio base stations. When a small number radio base stations are deployed over a given area, the number of Reconfigurations Reports indicating that a given channel has been deallocated that must be received in order to initiate a preventive reconfiguration is smaller than when a high number of radio base stations is deployed over a given area.
• Figure 5 shows an example of Reconfiguration Policies.
• the "Minimum Received Reconfiguration Reports” indicates the minimum number of Reconfiguration Reports that must be received on a given channel to initiate a reconfiguration. This parameter depends on the distance and the density of base stations.
• the first column indicates that if the density of the network deployment is 10 radio base stations per kilometer square, at least 15 Reconfiguration Reports must be received from Spectrum Managers associated with radio base stations located within less than 10 kilometers, in order to initiate a reconfiguration.
• the 5th column indicates that if the density of the network deployment is 20 radio base stations per kilometer square, at least 35 Reconfiguration Reports must be received from spectrum managers associated with radio base stations located within less than 50 kilometers, in order to initiate a reconfiguration.
• the "Maximum distance between Reconfiguration Reports” parameter indicates that the distance between each radio base stations whose reconfiguration was reported must be less than 30 kilometers.
• the "Validity period” parameter indicates that the Reconfiguration Reports must be received within a 10 seconds time window.
• the spectrum manager When determining in step C that some channels should be preventively deallocated, the spectrum manager identifies whether alternative channels are available. The spectrum manager then sends a request to the radio base station indicating the channels that are deallocated and the newly allocated channels.
• the spectrum manager may alternatively simply send a notification to the radio base station including the list of channels allocated to the radio base station that are more likely to be deallocated than the others channels allocated to the radio base station.
• Figure 6 shows an example of reconfiguration of radio base stations according to the current invention.
• SMI, SM2, and SM3 send a Reconfiguration Report indicating that channel 1 is deallocated
• SMI, SM3 and SM8 send a Reconfiguration Report indicating that channel 2 is deallocated.
• SM4 receives and analyzes those reports using its Reconfiguration Policies. According to those policies, at least 3 Reconfiguration Reports need to be received, from spectrum managers associated with radio base stations located within a maximum of 3 kilometers from each other, in order to initiate a preventive reconfiguration.
• SMI, SM2 and SM3 are located within 3 kilometers from each other. As a result, the criteria of the Reconfiguration Policies are fulfilled for channel 1 and SM4 initiates a preventive reconfiguration on this channel.
• the radio base station associated with SM8 is located at more than 3 kilometers from other radio base stations associated with spectrum managers reporting a reconfiguration on channel 2. Therefore, even though 3 Reconfiguration Reports were received for channel 2, SM4 does not initiate a preventive reconfiguration for this channel.
• Spectrum managers may store the history of preventive reconfigurations performed according to the present invention. Using this information, spectrum managers may verify whether a given preventive reconfiguration was relevant or not, by checking whether they received a notification from a RF sensor or an entity managing a network of RF sensors about the presence of a primary user on the channel on which they requested a preventive reconfiguration, within a given period of time. This period of time may correspond to an estimation of the maximum time required for a primary user, whose presence is assumed to be nearby the location provided in received Reconfiguration Reports, to reach the radio base station.
• the spectrum manager may modify the parameters in the Reconfiguration Policies to limit the amount of preventive reconfigurations. For example, the "Minimum Received Reconfiguration Reports" parameter may be increased. Conversely, if based on this analysis, the spectrum manager is often notified about the presence of a primary user within the proximity of the radio base station to which it is associated, without having anticipated a preventive reconfiguration, the spectrum manager may modify the parameters in the Reconfiguration Policies to increase the amount of preventive reconfigurations. For example, the "Minimum Received Reconfiguration Reports" parameter may be decreased.

Landscapes

• Engineering & Computer Science (AREA)
• Computer Networks & Wireless Communication (AREA)
• Signal Processing (AREA)
• Mobile Radio Communication Systems (AREA)

Priority Applications (1)

Applications Claiming Priority (2)

Publications (1)

Family

ID=57113373

Family Applications (1)

Country Status (3)

Citations (2)

• 2015
  • 2015-11-03 FR FR1502313A patent/FR3043298B1/fr active Active
• 2016
  • 2016-10-19 EP EP16791536.2A patent/EP3371996A1/en not_active Withdrawn
  • 2016-10-19 WO PCT/EP2016/075061 patent/WO2017076643A1/en not_active Ceased

Patent Citations (2)

Non-Patent Citations (1)

Also Published As

Similar Documents

Legal Events