WO2018069180A1 - Localisation d'unités de communication sans fil mobiles - Google Patents

Localisation d'unités de communication sans fil mobiles Download PDF

Info

Publication number
WO2018069180A1
WO2018069180A1 PCT/EP2017/075493 EP2017075493W WO2018069180A1 WO 2018069180 A1 WO2018069180 A1 WO 2018069180A1 EP 2017075493 W EP2017075493 W EP 2017075493W WO 2018069180 A1 WO2018069180 A1 WO 2018069180A1
Authority
WO
WIPO (PCT)
Prior art keywords
wireless communication
communication unit
cells
cell
information
Prior art date
Application number
PCT/EP2017/075493
Other languages
English (en)
Inventor
James Harrow
Original Assignee
Ip.Access Limited
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Ip.Access Limited filed Critical Ip.Access Limited
Publication of WO2018069180A1 publication Critical patent/WO2018069180A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W64/00—Locating users or terminals or network equipment for network management purposes, e.g. mobility management
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/02—Services making use of location information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/18—Management of setup rejection or failure
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/16—Performing reselection for specific purposes
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
    • H04W60/04—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration using triggered events
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W84/00—Network topologies
    • H04W84/02—Hierarchically pre-organised networks, e.g. paging networks, cellular networks, WLAN [Wireless Local Area Network] or WLL [Wireless Local Loop]
    • H04W84/04—Large scale networks; Deep hierarchical networks
    • H04W84/042—Public Land Mobile systems, e.g. cellular systems
    • H04W84/045—Public Land Mobile systems, e.g. cellular systems using private Base Stations, e.g. femto Base Stations, home Node B

Definitions

  • the field of this invention relates to network entities, a wireless communication system and methods therefor and particularly to a method for locating mobile wireless communications units.
  • the field of this invention relates to a mechanism to allow indoor triangulation by RRC redirecting a UE to several neighbouring (and located close to one another) small cells, which may be presence cells (pCells) for presence applications.
  • pCells presence cells
  • Wireless communication systems such as the 3 rd Generation (3G) of mobile telephone standards and technology
  • 3G 3rd Generation
  • 3GPPTM 3 rd Generation Partnership Project
  • the 3 rd generation of wireless communications has generally been developed to support macro-cell mobile phone communications.
  • Such macro cells utilise high power base stations (NodeBs in 3GPPTM parlance) to communicate with wireless communication units within a relatively large geographical coverage area.
  • a wireless communication system typically comprises a plurality of radio network subsystems, each radio network subsystem comprising one or more cells to which UEs may attach, and thereby connect to other communication units within, or through, the wireless communication system.
  • 3GPPTM also has developed a 4G Long Term Evolution (LTE) solution, namely, an Evolved Universal Mobile Telecommunication System Territorial Radio Access Network, (E-UTRAN), for a mobile access network, and a System Architecture Evolution (SAE) solution, namely, an Evolved Packet Core (EPC), for a mobile core network.
  • LTE Long Term Evolution
  • E-UTRAN Evolved Universal Mobile Telecommunication System Territorial Radio Access Network
  • SAE System Architecture Evolution
  • EPC Evolved Packet Core
  • UE User Equipment
  • a core network through a 2G,3G or 4G RAN such as the (Enhanced Data Rate for GSM Evolution, EDGE) Radio Access Network (Radio Access Network, GERAN) or a Universal Mobile Telecommunication System Terrestrial Radio Access Network (Universal Mobile Telecommunication System Terrestrial Radio Access Network, UTRAN), and access the EPC through the E-UTRAN.
  • EDGE Enhanced Data Rate for GSM Evolution
  • GERAN Radio Access Network
  • UTRAN Universal Mobile Telecommunication System Terrestrial Radio Access Network
  • the Core Network is responsible for switching and routing voice calls and data to and from wired telephone networks or the Internet.
  • a RAN is located between the Core Network and the UE.
  • Operators are seeking to exploit their radio spectrum by providing micro-location based tracking of anonymised UEs in their networks.
  • the operators already provide large-scale macro location insights using probes to monitor which UEs are using which macro cells and then combine this with other data sources (such as their Customer Relationship Management (CRM) information, billing data and the web sites that the users visit).
  • CRM Customer Relationship Management
  • CRM Customer Relationship Management
  • Lower power (and therefore smaller coverage area) cells are a recent development within the field of wireless cellular communication systems. Such small cells are effectively communication coverage areas supported by low power base stations.
  • the terms 'picocell' and 'femtocell' are often used to mean a cell with a small coverage area, with the term femtocell being more commonly used with reference to residential small cells.
  • the term 'small cell' means any cell having a relatively small coverage area (a coverage area less than a typical macro cell) and includes picocells and femtocells.
  • the low power base stations that support small cells are referred to as Access Points (APs), with the term Home Node B (HNBs) or Home evolved Node B (HeNB) identifying femtocell access points.
  • APs Access Points
  • HNBs Home Node B
  • HeNB Home evolved Node B
  • These small cells are intended to augment the wide area macrocell network and support communications to User Equipment in a restricted, for example, indoor environment.
  • An additional benefit of small cells is that they can offload traffic from the macrocell network, thereby freeing up valuable macrocell network resources.
  • HNB type devices With the increasing use of small cell HNB type devices instead of macro cells the Operators can now provide location data at a much finer granularity. Recently, it is noted that retailers also want to know where a mobile wireless communication unit, such as a UE/smartphone, is located within an indoor environment, say within their specific shop. This has numerous retail applications, such as allowing a retailer to have insight into the type of people who frequent their stores (based on anonymous aggregated sightings).
  • the use of HNB-type devices being configured to provide location information is often referred to the HNB functioning as a 'Presence Cell', which works much like a HNB operating in a closed access mode.
  • the HNB appears like any other cell in the Operator's network in terms of UE reselection behaviour.
  • the standard operation of a UE is to attempt to use the strongest (i.e. nearest) small cell to initiate its RRC Connection Request to, irrespective of whether or not this small cell has functionality to be re-configured as a Presence Cell.
  • the Presence Cell would first ask UEs trying to access it for their unique identity and would then reject the UE back to the normal macro network.
  • the UE's unique identity, together with a timestamp and location may be obtained and provided to a presence collector to be passed to the retailer.
  • aspects of the invention provide a method for location determination of a wireless communication unit, a controller, and a communication system as described in the appended claims.
  • a method for location determination of a wireless communication unit comprises, at a controller: identifying a wireless communication unit; causing multiple access attempts of the wireless communication unit to selected multiple cells; obtaining information from each of said selected multiple cells related to the respective access attempt; and forwarding the information to a device to calculate a position of the wireless communication unit based on the obtained information from the selected multiple cells.
  • location information of a wireless communication unit such as a UE, may be obtained through a targeted re-direction of multiple access attempts for the wireless communication unit.
  • causing multiple access attempts may comprise forcing a targeted redirection process of the wireless communication unit to obtain information to perform location validation.
  • causing multiple access attempts may comprise instructing the wireless communication unit to effect multiple access attempts to multiple cells using respective multiple re-direction messages.
  • the multiple re-direction messages may comprise multiple radio resource control, RRC, reject with re-direction messages.
  • the method may further comprise performing a location update (LU) reject operation, as part of a RRC Connection Release operation as a respective re-direction message.
  • LU location update
  • the information obtained from the multiple cells may comprise: a wireless communication unit identity captured by each of the multiple cells; and a measured parameter that represents a relative distance of the wireless communication unit to the cell.
  • the information obtained from the multiple cells may comprise a temporary mobile subscriber identity, TMSI, identity and a received signal code power, RSCP, measurement performed by the wireless communication unit on a common pilot channel transmission by the respective cell.
  • the information obtained from the multiple cells may comprise a wireless communication unit International Mobile Equipment Identity, IMEI, where the method further comprises: deriving a manufacture or handset type or classmark of the wireless communication unit; and determining whether the wireless communication unit can be redirected based on the derived manufacture or handset type or classmark.
  • IMEI International Mobile Equipment Identity
  • causing multiple access attempts of the wireless communication unit to selected multiple cells may comprise instructing the multiple cells to transmit an access rejection message to the wireless communication unit with an indication of a further cell to attempt access to.
  • the indication of a further cell to attempt access to may comprise a re-direction indication of an offset frequency to other cells carrier frequencies to attempt access to as part of an orthogonal carrier arrangement.
  • the method may further comprise applying at least one threshold to at least one of: a time limit to the causing and obtaining operations; a number of Cells to obtain information from; a low received signal value threshold.
  • the method may further comprise, in response to the at least one threshold being reached: abandoning the obtaining of information from further of said selected multiple cells; and basing the calculation on the information already obtained.
  • the multiple cells may be multiple small cells and the method further comprises adapting a Presence cell redirection list and instructing Presence cells in order to obtain information from at least three different cells.
  • the method may further comprise one of: calculating a position of the wireless communication unit based on the obtained information using triangulation, or forwarding the obtained information to a presence collector, when the obtained information is presence sighting information.
  • a controller for supporting location determination of a wireless communication unit in a wireless communication system that comprises multiple cells.
  • the controller comprises: a transceiver, a signal processor operably coupled to the transceiver and configured to: identify a wireless communication unit; cause multiple access attempts of the wireless communication unit to selected multiple cells; obtain information from each of said selected multiple cells related to the respective access attempt; and forward the information to a device to calculate a position of the wireless communication unit based on the obtained information from the selected multiple cells.
  • the signal processor may be configured to instruct the wireless communication unit to effect multiple access attempts to multiple cells using respective multiple redirection messages.
  • the multiple re-direction messages may comprise one or more from a group of: (i) multiple radio resource control, RRC, Reject with re-direction messages, (ii) multiple RRC Connection Reject messages, (iii) multiple RRC Connection Release with re-direction messages.
  • the signal processor may be further configured to instruct the multiple cells to transmit an access rejection message to the wireless communication unit with a re-direction indication of a further cell to attempt access to.
  • the indication of a further cell to attempt access to may comprise an indication of an offset frequency to other cells carrier frequency to attempt access to as part of an orthogonal carrier arrangement.
  • the signal processor may be coupled to a timer and a threshold circuit and configured to apply at least one threshold to at least one of: a time limit to the causing and obtaining operations; a number of Cells to obtain information from; a low received signal value threshold.
  • the signal processor may be configured to, in response to the at least one threshold being reached: abandon the obtaining of information from further of said selected multiple cells; and base the calculation on the information already obtained.
  • a wireless communication system comprises at least one wireless communication unit attachable to one of multiple cells and a controller operably coupled to each of the multiple cells for supporting location determination of the wireless communication unit.
  • the controller comprises: a transceiver, a signal processor operably coupled to the transceiver and configured to: identify a wireless communication unit; cause multiple access attempts of the wireless communication unit to selected multiple cells; obtain information from each of said selected multiple cells related to the respective access attempt; and forward the information to a device to calculate a position of the wireless communication unit based on the obtained information from the selected multiple cells.
  • FIG. 1 illustrates a part of an example wireless communication system comprising a macro core network and small cells, with at least a plurality of small cells being configured to operate as presence cells and, as such, coupled to a presence collector and presence controller, in accordance with an example embodiment of the invention.
  • FIG. 2 illustrates an example block diagram of a base station (for example a HNB functioning as a presence cell) configured to operate in accordance with an example embodiment of the invention.
  • a base station for example a HNB functioning as a presence cell
  • FIG. 3 illustrates an example flowchart of a method of forced re-direction of mobile handset access requests to assist a location determination in accordance with an example embodiment of the invention.
  • FIG. 4 illustrates a frequency-based diagram of a carrier usage in an example wireless communication system in accordance with an example embodiment of the invention.
  • FIG. 5 illustrates an example cell-based diagram of a position estimation scheme with a single Cell, in accordance with an example embodiment of the invention
  • FIG. 6 illustrates an example cell-based diagram of a position estimation scheme with two Cells, in accordance with an example embodiment of the invention.
  • FIG. 7 illustrates an example cell-based diagram of a position estimation scheme with three
  • FIG 8 illustrates an example cell-based diagram of a cluster controller of multiple Cells, in accordance with an example embodiment of the invention.
  • FIG 9 illustrates an example flowchart of how a Cluster Controller can automatically learn which cells are closely located and have the maximum chance of getting sightings after a redirection attempt, in accordance with an example embodiment of the invention.
  • Examples of the invention describe a method for location determination of a wireless communication unit, a controller and a wireless communication system.
  • the method comprises, at a controller: identifying a wireless communication unit; causing multiple access attempts of the wireless communication unit to selected multiple cells; obtaining information from each of said selected multiple cells related to the respective access attempt; and forwarding the information to a device to calculate a position of the wireless communication unit based on the obtained information from the selected multiple cells.
  • location information of a wireless communication unit such as a UE, may be obtained through a targeted re-direction of multiple access attempts for the wireless communication unit.
  • Examples of the invention are described with reference to a use by small cells reconfigured as Presence cells, it is envisaged that some examples may be employed by small cells or other cells, for other applications.
  • One such envisaged example application is in the context of an enterprise environment, where for example an employer may want to identify where employees are and then uses the example embodiments described herein for coverage/capacity (e.g. voice /data calls) support.
  • Presence Cell is typically deployed by itself, due to the random interactions that would be caused if multiple Presence Cell were deployed in a similar location.
  • the inventor of the present invention has recognised that if presence cells were arranged in a cluster (e.g. in a grid-type structure, as described with reference to FIG. 8) then, as part of the process of performing a location update request, the UE would report the CPICH RSCP at RACH, which is included in the RRC Connection Request message to the Node B.
  • a first cell such as a small cell that may be re-configured as a Presence Cell
  • a first cell is arranged to accept a UE Connection Request message and send a RRC Connection Setup message to the UE. Thereafter, in some examples, the UE will send an RRC Connection Setup Complete message back to the first cell, e.g. the Presence Cell.
  • the UE will typically wish to perform a Location Update Request due to the Presence Cell having a different Location Area Code (LAC) from the macro cell that it was previously camped onto.
  • the first cell e.g. Presence Cell, will send an Identity Request to ask the UE for its IMSI and may optionally also ask the UE for its IMEI. Once the UE responds with its IMSI, and optionally IMEI, the Presence Cell will send the UE a Location Update Reject message.
  • LAC Location Area Code
  • the first Presence Cell may send an RRC Connection Release that includes Redirection Information, in order to direct the UE to one of the other Presence Cells in the vicinity.
  • Nells neighbouring cells
  • the second Presence Cell if the UE detected the second Presence Cell, it will send an RRC Connection Setup message and will include its TMSI and CPICH RSCP measurement of the second Presence Cell. Instead of accepting the UE (by means of sending it an RRC Connection Setup message), in accordance with examples of the invention, the second Presence Cell is configured to send the UE an RRC Reject with Re-direction message towards a third Presence Cell. Similarly if the UE detects the third Presence Cell then it may also attempt to access the third Presence cell and would send its TMSI and CPICH RSCP measurement.
  • the third Presence Cell may decide to send RRC Connection Reject with Redirection Info message to either another nearby fourth Presence Cell or it may redirect the UE back towards the macro network, in order to ensure that the UE is not disconnected from the macro network for too long in case there are incoming calls for that UE which may be missed.
  • the re-direction messages may comprise (multiple) RRC Connection Reject messages.
  • the term 'co-located' is used to encompass the pCells being in close physical proximity to one another, typically within a distance between pCells measured in meters or a few tens of meters.
  • examples of the invention propose a mechanism to support a targeted redirection of an user/user equipment to a selection of presence cells in order to validate a location, and in most instances determine a more accurate location, of the user/user equipment.
  • the validation of a UE's location may be obtained from received signal code power (RSCP) measurements and a relative (apriori known) positioning of Presence Cells by applying, say, a known triangulation algorithm.
  • RSCP received signal code power
  • Further examples of the invention propose a mechanism to avoid the relative apriori known positioning of Presence Cells by describing a mechanism for the system to self-learn from system installation and autonomously adapt to locations of Presence Cells as they are installed, deactivated or re-located.
  • Some examples of the inventive concept find applicability in a wireless communication system comprising a presence collector.
  • FIG. 1 an example of part of a 3G wireless communication system comprising a macro core network and a number of small cells, with at least a plurality of small cells being configured to operate as, is illustrated in accordance with an example embodiment of the invention.
  • the wireless communication system is illustrated and indicated generally at 100, referred to as a 'core network connected mode' and comprises a Node B 102 that supports wireless communications in a macro cell.
  • the Node B 102 is connected with a radio network controller (RNC) 104, which in turn is linked with a Core Network 106 that includes a Mobile Switching Centre and other conventional network elements or subsystems (not shown).
  • RNC radio network controller
  • the MSC of the Core Network 106 routes services for both the small cell and macro cell networks of FIG.1 .
  • a plurality of small cells is supported in the wireless communication system, with communication within the small cell being provided by HNBs.
  • An example of a typical HNB for use within a 3GPP 3G system may comprise Node-B functionality and some aspects of RNC functionality, as specified in 3GPP TS 25.467.
  • the HNBs provide a radio access network (RAN) connectivity to the UE 108 using the so-called luh interface to a network Access Controller, also known as a Home NodeB Gateway (HNB-GW) (not shown), which in turn is connected to the MSC of the Core Network 106.
  • the HNBs, as represented in FIG. 1 are configurable to function as Presence Cells 1 10, 120, 130, with only three being shown for the sake of clarity and simplicity.
  • the Presence Cells 1 10, 120, 130 are coupled to a presence collector 160 via a local presence controller 150.
  • a User Equipment (UE) 108 may roam in and out of the coverage areas of the Node B 102 or the pCells 1 10, 120, or 130 and may attempt to perform a Location Update Request to any one of these pCells.
  • the pCells upon receipt of a RRC Connection Request and Location Updated Request will request the UE identity (IMSI) and will then send a Location Update Reject and in doing so redirect the UE back to the Node B.
  • the local presence Controller 150 is configured to generate a location presence notification message and send this to a presence collector 160 each time it receives a registration request from a UE 108 via any one of the Presence cells 1 10, 120, 130 to which it is linked.
  • a location presence notification message contains information relating to the identity of the UE 108 (e.g. it's IMSI) and the identity of the Presence Cell that received the initial request for registration.
  • a first RRC set-up request message 170 is sent from UE 108 to first presence cell (pCell) 1 10.
  • the first presence cell accepts the connection and expects to receive a Location Update Request message.
  • the first presence cell in receiving a Location Update Request, asks the UE for its IMSI and optionally IMEI by sending an Identity Request.
  • the first presence cell then may send a Location Update Reject message to the UE and release the RRC connection using, a RRC Connection Release with redirection message 172 is returned from first pCell 1 10 to UE 108, re-directing the UE 108 to request access to a further pCell from an identified pCell redirection list.
  • the UE 108 In response to the first RRC Connection Release with redirection message 172, the UE 108 detects pCell 120 and sends a second RRC Request message 174 to second pCell 120. This time, in response, a RRC Connection Reject with redirection message 176 is returned from second pCell 120 to UE 108, re-directing the UE 108 to request access to a further pCell 130 from the identified pCell redirection list. In response to the second RRC Connection Reject with redirection message 176, the UE 108 sends a third RRC Connection Request message 178 to third pCell 130.
  • a third RRC reject with redirection message 180 is returned from third pCell 130 to UE 108, re-directing the UE 108 to request access, say, via NodeB 102.
  • the third pCell has realised, or is informed, that a sufficient number of pCell access attempts has been performed by the UE 108, such an accurate location determination, say through triangulation, can be performed from the previous pCell attempts.
  • the final redirection message may be to return to an appropriate macro cell NodeB, such as NodeB 102.
  • the local presence cluster controller 150 may be a local server device or a Presence Cell dedicated as a master Presence Cell to co-ordinate other Presence Cells located around it.
  • the local presence (cluster) controller 150 may be configured to control a cluster of Presence Cells, such as Presence Cells 110, 120, 130.
  • the local presence cluster controller 150 is configured to inform the associated Presence Cell of which of its neighbours to redirect to, for example with a RRC Connection Release with Re-direction message or multiple RRC Connection Reject with Re-direction messages. In this manner, a more controlled and intelligent redirection technique is provided.
  • local presence cluster controller 150 may comprise a processor or controller 152 arranged to control and update one or more Presence Cell RRC re-direction lists stored in memory 158 for sending to the Presence cells 1 10, 120, 130.
  • the processor or controller 152 may comprise, or be coupled to a timer or counter 154, and be configured to apply time limits to the RRC redirection process.
  • the processor or controller 152 may be used to limit how many Presence cells are used as part of the mini cluster, thereby avoiding relatively long periods where the UE 108 is off the macro network.
  • the processor or controller 152 of the local presence cluster controller 150 may use the timer or counter 154 to coordinate a cluster wide view of the system.
  • the timer or counter 154 may be used to prevent UEs being handed around the cluster indefinitely.
  • the timer or counter 154 may be used to avoid processing a UE a second time (within a certain time period) should it appear on a different pCell.
  • the processor or controller 152 may be coupled to a timer or counter 154 and a threshold detection circuit 156.
  • the timer or counter 154 is configured to track a number of RRC Connection Reject with redirection messages that are sent to UE 108, so that a number of access attempts and rejections can be controlled if the threshold detection circuit 156 detects that the number has exceeded a value, e.g. three cells.
  • the processor or controller 152 of the local presence cluster controller 150 may be configured to adapt a number of RRC Connection Reject with redirection messages that it proposes for a specific UE 108 based on, say, the UE's estimated position.
  • the processor or controller 152 of the local presence cluster controller 150 may decide that it is too risky (or of too little potential value) to RRC Redirect the UE 108 to another Presence Cell in the cluster. In this instance, for example, the processor or controller 152 of the local presence cluster controller 150 may deem that it is safer and more efficient with regard to use of the available communication resource to redirect the UE 108 back to the macro cell network and for it to access NodeB 102.
  • the local presence cluster controller may also decide that after two sightings of the UE 108, say based on CPICH RSCP signal measurements from two respective Presence Cells, the position of the UE 108 is now further disambiguated.
  • processor or controller 152 of the local presence cluster controller 150 may decide that there is no other Presence Cell in the cluster that the local presence cluster controller 150 should try to obtain more presence-related data from and abandon the location validation or accuracy improvement process.
  • the processor or controller 152 of the local presence cluster controller 150 may also decide to redirect the UE 108 back to the macro cell network instead of attempt a third presence cell (pCell) access.
  • pCell third presence cell
  • FIG. 2 a block diagram of a wireless communication unit, adapted in accordance with some example embodiments of the invention, is shown.
  • the wireless communication unit is described in terms of a wireless base station 200, such as a HNB configured to operate as a Presence Cell, such as pCell 130 in FIG. 1 .
  • the base station 200 contains an antenna 202, antenna array, or plurality of antennas for receiving and transmitting signals 221 coupled to an antenna switch or duplexer 204 that provides isolation between receive and transmit chains within the base station 200.
  • One or more receiver chains include receiver front-end circuitry 206 (effectively providing reception, filtering and intermediate or base-band frequency conversion).
  • the receiver front-end circuitry 206 is coupled to a signal processor 228 (generally realized by a digital signal processor (DSP)).
  • DSP digital signal processor
  • the controller 214 maintains overall operational control of the base station 200.
  • the controller 214 is also coupled to the receiver front-end circuitry 206 and the signal processor 228.
  • the controller 214 is also coupled to a buffer module 217 and a memory circuit 216 that selectively stores operating regimes, such as decoding/encoding functions, synchronization patterns, code sequences, and the like, as well as information related to UEs that it is communicating with.
  • a timer 218 is operably coupled to the controller 214 to control the timing of operations (e.g. transmission or reception of time-dependent signals) within the base station 200.
  • this essentially includes an input module 240, coupled in series through transmitter/modulation circuitry 222 and a power amplifier 224 to the antenna 202, antenna array, or plurality of antennas.
  • the transmitter/ modulation circuitry 222 and the power amplifier 224 are operationally responsive to the controller 214.
  • base station 200 is configured such that the transmitter and receiver circuits (often referred to as a transceiver) are configured to communicate with a plurality of mobile handsets, e.g. users of UEs 108 from FIG. 1 .
  • the signal processor 228 or controller 214 is able to re-configure the base station 200 as a presence cell.
  • the signal processor 228 receives a connection request message, say in a form of a RRC Connection Req. message, from a wireless communication unit, such as UE 108 from FIG. 1 .
  • the RRC connection request message transmitted on the random access channel (RACH) may include a common pilot channel (CPICH) received signal code power (RSCP) level that the UE measured from a transmission by the base station 200, as well as the UE's temporary mobile subscriber identity (TMSI).
  • CPICH common pilot channel
  • RSCP received signal code power
  • TMSI temporary mobile subscriber identity
  • the base station 200 is in a RRC Connected mode in order to receive the Location Update Request and attempt to get the IMSI/IMEI.
  • the signal processor 228 (in operation with the receiver front-end circuitry 206 and associated radio frequency circuits) then, in some examples, is configured to determine whether (or not) a UE that sends a RRC Connection Request message should be accepted in a normal manner, or whether the UE should be redirected in accordance with the examples herein described.
  • this determination by the signal processor 228 involves the signal processor 228 using the known TMSI from the local presence controller and a count of how many recent sightings of this same TMSI that the local presence controller has seen, say in the last 5 seconds. In this manner, the base station 200 may avoid an occurrence of continuous redirection amongst other base stations/pCells.
  • the signal processor 228 includes, or is operably coupled to, a counter circuit 240 that is configured to count a number of recent sightings of this same TMSI that the local presence controller has seen. In this manner, base station 200 configured as a pCell is able to limit the number of access attempts it responds to, and the interactions it triggers with the Presence Controller, say Presence Controller 150 of FIG. 1 .
  • the signal processor 228 In response to a RRC Connection Request message, the signal processor 228 (in operation with the transmitter/ modulation circuitry 222 and the power amplifier 224) sends an RRC Connection Setup message to the UE. In response to the RRC Connection Setup the UE sends a RRC Connection Setup Complete message, and may then send a Location Update Request to the pCell. In response thereto, the signal processor 228 (in operation with the transmitter/ modulation circuitry 222 and the power amplifier 224) sends an Identity Request (IMSI) message to the wireless communication unit. In response, the signal processor 228 (in operation with the receiver front-end circuitry 206 and associated radio frequency circuits) receives an Identity Response (IMSI) message.
  • IMSI Identity Request
  • the signal processor 228 (in operation with the transmitter/ modulation circuitry 222 and the power amplifier 224) then sends an Identity Request (IMEI) to the wireless communication unit and receives, in response, the wireless communication unit's Identity Response (IMEI).
  • IMEI Identity Request
  • the signal processor 228 sends a Location Update Reject message and includes an RRC Connection Release with Redirect Info to a new UARFCN of a second Presence Cell (such as pCell 120 of FIG. 1 ) for the wireless communication unit to attempt access to.
  • the signal processor 228 may implement this re-direction after performing a location update (LU) reject operation, as part of a RRC Connection Release (e.g. redirect) operation.
  • LU location update
  • memory circuit 216 operably coupled to the signal processor 228, may be configured to store details of the redirection to the next base station/presence cell, in accordance with a re-direction list (such as a RRC redirection list) controlled by the presence controller.
  • a re-direction list such as a RRC redirection list
  • the signal processor 228 in the transmit chain may be implemented as distinct from the signal processor in the receive chain. Alternatively, a single processor may be used to implement a processing of both transmit and receive signals, as shown in FIG. 2. Clearly, the various components within the base station 200 can be realized in discrete or integrated component form, with an ultimate structure therefore being an application-specific or design selection.
  • FIG. 3 illustrates a simplified flowchart 300 of a method of forced re-direction of mobile handset access requests to assist a location determination of a UE in accordance with an example embodiment of the invention.
  • the pCell may implement this re-direction after performing a location update (LU) reject operation, as part of a RRC Connection Release (e.g. redirect) operation.
  • LU location update
  • a UE such as UE 108 of FIG. 1
  • a first small cell such as an HNB
  • the UE 108 attempts to send a connection request message on a random access channel (RACH), say in a form of a RRC Connection Req. message, to first pCell 1 10 and includes a common pilot channel (CPICH) received signal code power (RSCP) level that the UE measured of the transmission of the first pCell 1 10 and the UE's temporary mobile subscriber identity (TMSI).
  • RACH random access channel
  • RSCP received signal code power
  • the first pCell 1 admits the UE by sending an RRC Connection Setup message to the UE 108.
  • the UE 108 then completes the RRC Connection and sends a Location Update Request.
  • the first pCell 1 10 sends an Identity Request (IMSI) message to UE 108.
  • the UE 108 sends an Identity Response (IMSI) message to first pCell 1 10.
  • first pCell 1 10 sends an Identity Request (IMEI) to UE 108 and at 312 the UE 108 sends its Identity Response (IMEI) to first pCell 1 10.
  • the local presence cluster controller may use the UE's IMEI, say in order to derive manufacture and handset type or classmark, in order to advantageously determine which UEs can safely be introduced into the location determination process and be redirected, since there are sometimes known issues with specific handsets that do not behave well.
  • the first pCell 1 10 sends a Location Update Reject message and includes an RRC Connection Release with Redirect Info to a new UARFCN of a second Presence Cell (pCell 120).
  • the selection of the second Presence Cell (pCell 120) to re-direct the UE 108 to has, in some examples, been decided by the local presence cluster controller and duly informed to the first pCell 1 10.
  • the second pCell 1 10 has also been duly informed to redirect UEs to a third pCell, such as third pCell 130 in FIG. 1 .
  • the UE 108 attempts to connect to the second Presence Cell (pCell 120) and then sends RRC Connection Request to the second pCell 120, which again includes TMSI and 'CPICH RSCP on RACH' information.
  • the second pCell 120 is configured to send a RRC Connection Reject message and includes an RRC Redirect Info to a new UARFCN of third Presence Cell (pCell 130).
  • the UE 108 attempts to connect to the third pCell 130 and sends a RRC Connection Request to third Presence Cell (pCell 130), which includes TMSI and "CPICH RSCP on RACH".
  • third Presence Cell (pCell 130) may continue this process to pCell #4, etc.
  • the third pCell 130 redirects the UE 108 back to the macro cell network.
  • the pCell 130 also sends a RRC Connection Reject and, in this example, includes an RRC Redirect Info to redirect the UE to the macro cell UARFCN of NodeB 102.
  • first, second and third pCells 1 10, 120 & 130 forward their respective presence sighting data (based on CPICH RSCP signal measurements), including the UE's TMSI, to a Local presence controller, such as Local presence controller 150 of FIG. 1 .
  • the Local presence controller 150 calculates an estimated location of the UE, from the information obtained from the three pCells, or forwards the respective sightings data and/or a location estimate to Presence collector 160.
  • the Presence collector 160 determines a UE location based on the received sightings data.
  • the Presence collector 160 may determine a UE location based on the received sightings data by using, say, known triangulation techniques to improve the location accuracy of the UE 108.
  • the known triangulation technique may be based on a pathloss estimate.
  • the location of the pCells themselves would need to be apriori known, e.g. by performing an approximate survey to know their relative positions.
  • the UE 108 attempts to connect to macro NodeB 102 and performs Location update back to Macro network.
  • two sightings from two Presence cells based on CPICH RSCP signal measurements will be able to provide sufficient information to provide an indication of a UE's location.
  • three sightings from three Presence cells provides better accuracy than two sightings from two Presence cells, thereby helping remove any ambiguity of location.
  • the processor or controller of the local presence cluster controller may decide that it is too risky (or of too little potential value) to RRC Redirect the UE to another Presence Cell in the cluster.
  • the UE 108 if the UE 108 cannot detect the redirected pCell, on the specified UARFCN, then the UE 108 will give up and search back for the macro network anyway. Thus, a few seconds later, the UE 108 may either result in being connected to the macro network (where it is Location Update Accepted) or the UE 108 will attempt a connection to another pCell, which may be the same one it was redirected from or a new pCell.
  • the UE In the current 3GPPTM standard, it is not possible to inform the UE of the scrambling code to redirect the UE. As such, the UE typically selects the newest strongest cell by itself (from the system information broadcast (SIB) SIB1 1 message), and is told what frequency to use on that cell. Thereafter, the UE chooses any available scrambling code (e.g. from ScrCodes 1 -512) on the channel.
  • SIB system information broadcast
  • an orthogonal carrier technique i.e. offset by +200kHz, 0 and -200kHz from the normal pCell layer.
  • This technique may be used to force the UE temporarily to re-measure a new specific frequency, related to a different pCell, as illustrated in FIG. 4.
  • the use of such an offset frequency arrangement allows the cell to perform a RRC Connection reject operation and re-direct the wireless communication unit to another cell in accordance with a predetermined redirection list, for example stored in memory 158 of local presence controller 150 of FIG. 1 .
  • FIG. 4 illustrates an example frequency-based diagram 400 of a carrier usage in an example wireless communication system in accordance with an example embodiment of the invention.
  • multiple orthogonal UARFCN carriers are used.
  • a UARFCN defines the centre frequency of a UMTS carrier that is typically 5MHz wide.
  • the UARFCN maps onto an absolute frequency in MHz with a channel raster typically at 200kHz offsets, for example UARFCN 10700 maps to 2140MHz and UARFCN 10701 maps to 2140.2MHz. Therefore, it is possible for two different UARFCNs to overlap significantly, though normally an operator will deploy their spectrum so that their carriers do not overlap.
  • UMTS UMTS
  • UMTSTM when a UE is redirected, only the UARFCN is specified in the Redirect-lnfo (there is no ability to redirect to a specific cell Scrambling Code for example) and so then the UE is free to choose whichever detected cell it discovers on that UARFCN, meaning that there would be no real control over which specific cell the UE is redirected to.
  • examples of the invention propose using a couple of additional such offset UARFCNs that result in there being an ability to redirect towards a specific cell in order to take advantage of known RRC Reject with Redirect messages.
  • such an approach may be employed in a normal cellular re-use pattern within the cluster.
  • a cluster of cells may be configured to operate on a (mostly) separate UARFCN to the macro cell (NodeB).
  • this separate UARFCN may be used to turn a single block of spectrum (of say 5.4MHz wide) into three usable 5MHz channels.
  • a largish cluster of cells may be deployed by using a standard re-use pattern, which advantageously results in a minimal impact on the macro cell due to limited frequency overlap.
  • offsets may be used to provide control to each presence cell to forcefully redirect a user/UE to a known carrier frequency (UARFCN) on which other pCells in a cluster are configured.
  • URFCN carrier frequency
  • the use of multiple orthogonal UARFCN carriers allows RRC Reject with Re-direction messages to alternative channels, which may be co-channel with other macro NodeBs use but allows UEs to treat them as separate in RRC Redirection Info messages.
  • orthogonal UARFCNs for use in a presence cell arrangement as described herein may be employed.
  • the example frequency-based diagram 400 is divided into three contiguous 5MHz channel bandwidths 402, 404, 406.
  • the first frequency channel band (F1 ) 412 is identified by its UTRA absolute radio frequency channel number (UARFCNJ 10637 and the second frequency channel band (F2) 414 is identified by UARFCN 10661 .
  • carrier frequencies may be offset by 200 kHz 420.
  • a first offset channel band (F2') 432 is allocated a UARFCN number 10660 and relates to second frequency channel band (F2) with a 200KHz offset.
  • a second offset channel band (F2") 434 is allocated a UARFCN number 10659 and relates to second frequency channel band (F2) with a 400 kHz offset.
  • such offsets may be used by different pCells in order to facilitate orthogonality, e.g. first presence cell (pCell 1 ) is used on F2, ScrCode 1 , second presence cell (pCell 2) is used on (F2-200kHz, ScrCode 2), third presence cell (pCell 3) is used on (F2 - 400kHz, ScrCode 3, etc.
  • the macro cell may only broadcast one UARFCN/ScrCode in its neighbour cell (NCell) list to first presence cell (pCell 1 ).
  • pCelM is configured to redirect the UE to pCell2 (e.g. based on its UARFCN).
  • pCell2 is configured to redirect to pCell 3.
  • pCell3 is configured to redirect the UE back to the macro cell network.
  • this example may also provide the presence Layer a 'sub-layer' (for the carriers F2' and F2" that are not normally used by the operator's normal macro nodeBs, and as such the presence deployment is free to choose its own allocated ScrCodes, rather than needing these to be specifically allocated by the operator's cell planning team.
  • an intelligent and focused instruction to specifically obtain information from a selected cell from an identified list may assist a presence service.
  • multiple structure access attempts may be configured, rather than randomly obtaining pCell measurement and data.
  • a mechanism to have an adaptive, self-learning system for location determination of a wireless communication unit in a wireless communication system that includes multiple small cells that can be re-configured as presence cells is described.
  • a local presence controller is configured to develop relationships between multiple presence cells. For example, in the first aspect of the invention with a targeted redirection (for example through an access rejection) of a wireless communication unit to attempt to access cells, the relationships between multiple presence cells may be used to facilitate the location validation or location accuracy improvement of the wireless communication unit's location.
  • the RRC Redirect list per pCell
  • the system can be made to self-learn these relationships so as to reduce the probability of RRC Redirection failures.
  • the relationships that are developed between multiple cells may be used to improve a neighbour cell list.
  • the relationships that are developed between multiple cells may be used to improve handover options.
  • One such example is when multiple small cells that are used for coverage and capacity purposes, for example in a training mode, are deployed into a building then the system can be made to use the UE RRC redirects successes and failures to automatically detect relative proximity between the small cells and outdoor macro cells, so as to build handover relationships and idle mode cell reselection neighbour relationships as part of a self- organising system. Once the system is trained then it can operate in a 'stable' mode.
  • each pCell in the cluster is provided with a unique UTRA absolute radio frequency channel number (UARFCNJ and a scrambling code to use as its transmission operating parameters.
  • URFCNJ UTRA absolute radio frequency channel number
  • Each pCell is also provided with a randomly generated pCell list of UARFCNs of other nearby pCells (which should not include the UARFCN of itself) which it will use to redirect a wireless communication unit to another pCell in the cluster.
  • the randomly generated pCell list is created and updated, for example, by local presence cluster controller 150.
  • the results from multiple cells obtaining information from a wireless communication unit's multiple attempts to access a wireless communication system are received and collated by the local presence cluster controller 150.
  • the local presence cluster controller 150 then revises the pCell list according to each new result, to fine-tune relationship information between multiple cells to identify those presence cells that are in the vicinity of others, and may then be more suited than others for a location validation algorithm, or to improve a neighbour cell list for handover purposes.
  • This approach to initially use a randomly generated pCell list of UARFCN and Scrambling codes significantly eases the deployment of multiple small cells into a macro cell coverage area, for example within a retailer's shop. For example, no site surveys or system planning are required, and small cells that are re-configurable as presence cells may be, to some degree, dropped into operation.
  • the local presence cluster controller 150 may be a local server device or a Presence Cell dedicated as a master Presence Cell to co-ordinate other Presence Cells located around it.
  • the local presence (cluster) controller 150 may be configured to adaptively control relationships between a cluster of Presence Cells, such as Presence Cells 1 10, 120, 130.
  • the local presence cluster controller 150 is configured to adaptively build a relationship between multiple cells, for example adaptively inform the associated Presence Cells of which of its neighbours to instruct a UE attempting to access the cell as to which other cell the UE should redirect to. In this manner, a more controlled and intelligent re-direction technique is provided.
  • local presence cluster controller 150 may comprise a processor or controller 152 that is arranged to control and update one or more Presence Cell RRC re-direction lists stored in memory 158 for sending to the Presence cells 1 10, 120, 130.
  • the RRC Redirection list on each Presence Cell was not correct (for example a redirection from one cell to another cell in the cluster that was too far away for the UE to detect) as stipulated by the local presence controller, such as local presence controller 150 of FIG. 1 , or if one of the neighbouring Presence Cells was switched off, then the RRC Redirect mechanism may fail. When this occurs the UE must perform a scan to try to get back onto the network which may take several tens of seconds which would cause unacceptable service disruption to UEs if it was to happen all of the time. In response to any such failures, the local presence controller 150 is configured to adapt the RRC Redirect list stored in memory 158.
  • the UE 108 if the UE 108 cannot detect the redirected pCell, on the specified UARFCN, then the UE 108 will give up and search back for the macro network anyway. Thus, a few seconds later, the UE 108 may either result in being connected to the macro network (where it is Location Update Accepted) or the UE 108 will attempt a connection to another pCell, which may be the same one it was redirected from or a new pCell.
  • the processor or controller 152 may be coupled to timer or counter 154 and a threshold detection circuit 156.
  • timer or counter 154 is configured to track the success or failure rate of the RRC redirection messages that are sent to UEs. In this manner, a rating between the successful re-direction from a first pCell to other pCells can be calculated and adapted according to the number of successes or failures. If the number of failures increases beyond a threshold, for example as determined by the threshold detection circuit 156, then the relationship between the first pCell and the failing pCell can be disregarded (or allocated a low priority option).
  • the processor or controller 152 of the local presence cluster controller 150 may be configured to adapt a number of RRC reject with redirection messages that it proposes for a specific UE 108 based on, say, the UE's estimated position. For example, if the initial power reading on a first Presence Cell (pCell 1 ) was weak and below a power threshold determined by threshold detection circuit 156, and it was known or suspected that pCell 1 was on the edge of a cluster, the processor or controller 152 of the local presence cluster controller 150 may decide that it is too risky (or of too little potential value) to redirect the UE 108 to another Presence Cell in the cluster.
  • the processor or controller 152 of the local presence cluster controller 150 may deem that it is safer and more efficient, with regard to use of the available communication resource, to redirect the UE 108 back to the macro cell network and for it to access NodeB 102. Accordingly, in this example, the processor or controller 152 of the local presence cluster controller 150 may also adapt the Presence Cell RRC re-direction lists stored in memory 158.
  • the local presence cluster controller may also decide that after two sightings of the UE 108, say based on CPICH RSCP signal measurements from two respective Presence Cells, the position of the UE 108 is now sufficiently further disambiguated.
  • processor or controller 152 of the local presence cluster controller 150 may decide that there is no other Presence Cell in the cluster that the local presence cluster controller 150 should try to obtain more presence-related data from and abandon the location validation or accuracy improvement process.
  • the processor or controller 152 of the local presence cluster controller 150 may also decide to redirect the UE 108 back to the macro cell network instead of attempt a third presence cell (pCell) access.
  • pCell third presence cell
  • the processor or controller 152 of the local presence cluster controller 150 may also adapt the Presence Cell RRC re-direction lists stored in memory 158.
  • the algorithm applied by the local presence cluster controller 150 may be configured to swap out (or lower a priority status of) pCells, such as pCells 1 10, 120, 130 that are less useful and effectively re-organise the list so that the closest pCells to other pCells are discovered over a period of time.
  • pCells such as pCells 1 10, 120, 130 that are less useful and effectively re-organise the list so that the closest pCells to other pCells are discovered over a period of time.
  • the local presence cluster controller i.e. local with the pCells
  • Some examples of the invention propose to use the TMSI, as this is always sent with the CPICH Power level on the RRC Connection Request.
  • the local presence cluster controller 150 aims to make deployment simpler through a self-learning/optimisation technique for generating and maintaining an RRC Redirect list without needing to perform multiple site surveys.
  • an example cell-based diagram 500 is illustrated showing a first example of a position estimation scheme with a single Cell, in accordance with an example embodiment of the invention.
  • a first (single) small cell 510 configurable to support presence services, is located in, say a building.
  • RSCP received signal code power
  • An additional circular area 530 indicated by an extended uncertainty radius 535 provides a margin of error for location estimates of the UE 540.
  • the position of the UE 540 may be, in essence, anywhere within the estimated location zone 530, and therefore there is a large margin for location error.
  • FIG. 6 an example cell-based diagram 600 is illustrated showing a position estimation scheme with two Cells, in accordance with an example embodiment of the invention.
  • this diagram and based on UE measurement of the Cell#1 510 RSCP power level and with the knowledge of the position of the Cell #1 510 it is possible to estimate a circular location zone based 530 on an assumed 'radius' and a margin of error, as shown in FIG. 5.
  • a second measurement from the UE 540 of Cell #2 612 RSCP power level and with the knowledge of the position of Cell #2 612 it is possible to produce a similar circular location zone of UE around Cell #2 612 with a radius of 621 , with an additional uncertainty area 632 with an additional uncertainty radius 637.
  • FIG. 7 an example cell-based diagram 700 is illustrated showing a position estimation scheme with three Cells, in accordance with an example embodiment of the invention.
  • a position estimation scheme with three Cells, in accordance with an example embodiment of the invention.
  • FIG. 5 and FIG. 6 based on UE measurement of the Cell#1 510 RSCP power level and with the knowledge of the position of the Cell #1 510, it is possible to estimate a circular location zone based 530 on an assumed 'radius' and a margin of error.
  • FIG 8 illustrates a cluster controller 810 that coordinates the cells#1 -#9 510, 612, 714, 816-826, which are located in a grid arrangement.
  • the UE#1 540 is located closest to Cell#1 510 and cell#2 612, as well as cell#4 816 and cell#5 818. Whilst it may be advantageous to attempt to redirect the UE to Cell#9 826 due to its physical distance, it may be less likely to be detectable by the UE 540. As such, there is no value in redirecting UE 540 towards this cell if it was first detected on Cell #1 510.
  • FIG 9 an example flowchart 900 is illustrated detailing how a cluster controller, for example cluster controller 810 of FIG. 8, can automatically learn which cells are closely located and have the maximum chance of getting sightings after a redirection attempt, in accordance with an example embodiment of the invention.
  • a process may be based on having a 'learning' phase, where a set of re-direction rules between cells is created as a list, and each is tried at random in order to measure a likelihood of success.
  • a quality metric for each re-direction may be based on the UE signal strength measurements, which can be used to further bias which redirection is likely to yield a signal for good location estimation purposes.
  • the learning phase may be deemed complete and the cluster controller is able to change into an 'active' mode. In this example, instead of making decisions at random, they are based on the learnt data.
  • the system performance may change over time - e.g. a retail store refit may mean that a position of the sales till may move, or the position of the cells or internal walls / obstructions may change and, as such, people may congregate in different hotspot areas of a store.
  • This may mean that the redirection rules need to evolve automatically.
  • the self- learning nature of the algorithm described below allows it to adapt to changes and/or outages in cells, for example by updating the redirection rules based on real measurements.
  • the example flowchart 900 starts at 905, where the cluster controller, for example cluster controller 810 of FIG. 8, is configured with X, Y co-ordinates of all cells allocated in a cluster, in order to allow sighting location estimation to be performed.
  • the cluster controller may initialise a self- learning algorithm of state information for all relationships.
  • the cluster controller may begin to create relationship mapping rules (e.g. Cell#1 to Cell#2, Cell#1 to Cell#9, etc.).
  • the cluster controller may attempt (at random) different redirection rules and determines a success or failure of the re-direction attempt, for example 'was the UE sighted on the requested cell'?
  • the cluster controller updates, say, a probability of success of each possible redirection rule.
  • the cluster controller may optionally add a quality score of each redirection rule, say based on the reported UE measurement of RSCP / RSSI / RSRP of the redirected Cell. For example, if the RSCP / RSSI / RSRP is too weak (i.e. barely detectable), then the quality score is degraded.
  • the cluster controller may determine when the 'Learning' phase has sufficient data, in order to change to an 'Active' mode. This is based on a having statistically significant amounts of learnt data.
  • the cluster controller ranks the redirection rules based on the probability of successful redirection and quality.
  • the cluster controller may determine which rule is the most likely successful redirect rule to use, given the historical data and quality metric. Thereafter, for example, the cluster controller may determine which cell to redirect to and instructs the first Cell to redirect to next cell.
  • the cluster controller may update, say, its success metric for this redirection rule. If the second cell sighting is not seen, then the success metric for this redirection rule is degraded.
  • a controller such as controller 810, may be configured to change or update the UARFCN in response to a non-sighting. In this way the system may adapt to natural changes in the radio environment or cell outages.
  • the cluster controller detects a link failure to one of the cells in the redirection chain, it can update the associated redirection rules in order to prevent failed redirection attempts.
  • the cluster may also raise an alert to the operator that a cell is failed, or if the performance of a redirection rule has degraded for environmental reasons (e.g. the cell has been moved). For example, if a new cell is added to the cluster then the system may automatically transition into a learning mode. At 960, the redirection process may continue for several other attempts, which may be configured by the limit of redirection attempts.
  • the signal processing functionality of the embodiments of the invention may be achieved using computing systems or architectures known to those who are skilled in the relevant art.
  • Computing systems such as, a desktop, laptop or notebook computer, hand-held computing device (PDA, cell phone, palmtop, etc.), mainframe, server, client, or any other type of special or general purpose computing device as may be desirable or appropriate for a given application or environment can be used.
  • the computing system can include one or more processors which can be implemented using a general or special-purpose processing engine such as, for example, a microprocessor, microcontroller or other control module.
  • the computing system can also include a main memory, such as random access memory (RAM) or other dynamic memory, for storing information and instructions to be executed by a processor. Such a main memory also may be used for storing temporary variables or other intermediate information during execution of instructions to be executed by the processor.
  • the computing system may likewise include a read only memory (ROM) or other static storage device for storing static information and instructions for a processor.
  • ROM read only memory
  • the computing system may also include an information storage system which may include, for example, a media drive and a removable storage interface.
  • the media drive may include a drive or other mechanism to support fixed or removable storage media, such as a hard disk drive, a floppy disk drive, a magnetic tape drive, an optical disk drive, a compact disc (CD) or digital video drive (DVD) read or write drive (R or RW), or other removable or fixed media drive.
  • Storage media may include, for example, a hard disk, floppy disk, magnetic tape, optical disk, CD or DVD, or other fixed or removable medium that is read by and written to by media drive.
  • the storage media may include a computer-readable storage medium having particular computer software or data stored therein.
  • an information storage system may include other similar components for allowing computer programs or other instructions or data to be loaded into the computing system.
  • Such components may include, for example, a removable storage unit and an interface, such as a program cartridge and cartridge interface, a removable memory (for example, a flash memory or other removable memory module) and memory slot, and other removable storage units and interfaces that allow software and data to be transferred from the removable storage unit to computing system.
  • the computing system can also include a communications interface.
  • a communications interface can be used to allow software and data to be transferred between a computing system and external devices.
  • Examples of communications interfaces can include a modem, a network interface (such as an Ethernet or other NIC card), a communications port (such as for example, a universal serial bus (USB) port), a PCMCIA slot and card, etc.
  • Software and data transferred via a communications interface are in the form of signals which can be electronic, electromagnetic, and optical or other signals capable of being received by a communications interface medium.
  • 'computer program product' may be used generally to refer to tangible media such as, for example, a memory, storage device, or storage unit.
  • These and other forms of computer-readable media may store one or more instructions for use by the processor comprising the computer system to cause the processor to perform specified operations.
  • Such instructions generally referred to as 'computer program code' (which may be grouped in the form of computer programs or other groupings), when executed, enable the computing system to perform functions of embodiments of the present invention.
  • the code may directly cause a processor to perform specified operations, be compiled to do so, and/or be combined with other software, hardware, and/or firmware elements (e.g., libraries for performing standard functions) to do so.
  • the software may be stored in a computer-readable medium and loaded into computing system using, for example, removable storage drive.
  • a control module in this example, software instructions or executable computer program code, when executed by the processor in the computer system, causes a processor to perform the functions of the invention as described herein.
  • inventive concept can be applied to any circuit for performing signal processing functionality within a network element. It is further envisaged that, for example, a semiconductor manufacturer may employ the inventive concept in a design of a stand-alone device, such as a microcontroller of a digital signal processor (DSP), or application-specific integrated circuit (ASIC) and/or any other sub-system element.
  • DSP digital signal processor
  • ASIC application-specific integrated circuit
  • aspects of the invention may be implemented in any suitable form including hardware, software, firmware or any combination of these.
  • the invention may optionally be implemented, at least partly, as computer software running on one or more data processors and/or digital signal processors or configurable module components such as field programmable gate array (FPGA) devices.
  • FPGA field programmable gate array
  • the elements and components of an embodiment of the invention may be physically, functionally and logically implemented in any suitable way. Indeed, the functionality may be implemented in a single unit, in a plurality of units or as part of other functional units.

Landscapes

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

Abstract

L'invention concerne un procédé d'établissement de localisation d'une unité de communication sans fil (108). Le procédé consiste, au niveau d'un contrôleur (150), à : identifier une unité de communication sans fil ; provoquer de multiples tentatives d'accès, à partir de l'unité de communication sans fil, à des cellules multiples sélectionnées ; obtenir des informations (324) associées aux tentatives d'accès respectives à partir de chacune desdites multiples cellules sélectionnées ; et transmettre (326) les informations à un dispositif (160) pour calculer une position de l'unité de communication sans fil sur la base des informations obtenues à partir des multiples cellules sélectionnées.
PCT/EP2017/075493 2016-10-14 2017-10-06 Localisation d'unités de communication sans fil mobiles WO2018069180A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
GB1617437.7A GB2555101A (en) 2016-10-14 2016-10-14 Network entities, a wireless communication system and a method for locating mobile wireless communication units
GB1617437.7 2016-10-14

Publications (1)

Publication Number Publication Date
WO2018069180A1 true WO2018069180A1 (fr) 2018-04-19

Family

ID=57680689

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/EP2017/075493 WO2018069180A1 (fr) 2016-10-14 2017-10-06 Localisation d'unités de communication sans fil mobiles

Country Status (2)

Country Link
GB (1) GB2555101A (fr)
WO (1) WO2018069180A1 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112822752A (zh) * 2021-01-07 2021-05-18 西安电子科技大学 一种无人机自组织网络的路由建立方法及系统
CN113475157A (zh) * 2018-12-22 2021-10-01 诺基亚通信公司 用于无线网络的连接行为标识

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP0932999A1 (fr) * 1996-09-30 1999-08-04 TELEFONAKTIEBOLAGET L M ERICSSON (publ) Dispositif et procede a utiliser dans un systeme telephonique mobile cellulaire
GB2507119A (en) * 2012-10-22 2014-04-23 Ip Access Ltd Periodically changing small cell location area codes to assist location presence services
GB2526375A (en) * 2014-05-23 2015-11-25 Ip Access Ltd Network elements, wireless communication system and methods therefor

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP0932999A1 (fr) * 1996-09-30 1999-08-04 TELEFONAKTIEBOLAGET L M ERICSSON (publ) Dispositif et procede a utiliser dans un systeme telephonique mobile cellulaire
GB2507119A (en) * 2012-10-22 2014-04-23 Ip Access Ltd Periodically changing small cell location area codes to assist location presence services
GB2526375A (en) * 2014-05-23 2015-11-25 Ip Access Ltd Network elements, wireless communication system and methods therefor

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
CAROLINE GABRIEL: "CLIENT CONFIDENTIAL Copyright Maravedis-Rethink 2014", 16 June 2014 (2014-06-16), pages 1 - 17, XP055416204, Retrieved from the Internet <URL:http://www.ipaccess.com/uploads/wysiwyg_editor/files/Maravedis and ip access webinar slides.pdf> [retrieved on 20171017] *

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113475157A (zh) * 2018-12-22 2021-10-01 诺基亚通信公司 用于无线网络的连接行为标识
US11979754B2 (en) 2018-12-22 2024-05-07 Nokia Solutions And Networks Oy Connection behavior identification for wireless networks
CN113475157B (zh) * 2018-12-22 2024-05-14 诺基亚通信公司 用于无线网络的连接行为标识
CN112822752A (zh) * 2021-01-07 2021-05-18 西安电子科技大学 一种无人机自组织网络的路由建立方法及系统

Also Published As

Publication number Publication date
GB2555101A (en) 2018-04-25
GB201617437D0 (en) 2016-11-30

Similar Documents

Publication Publication Date Title
KR101279907B1 (ko) 사용자 기기 데이터베이스에서 펨토 셀 위치를 찾기 위한 위치 정보의 저장
US9497708B2 (en) Power setting
TWI641277B (zh) 在共享通訊媒體中的通道選擇
US9277468B2 (en) Maintaining neighbor cell list
JP5450588B2 (ja) 電力効果的小型基地局走査及び取得
RU2528422C2 (ru) Использование идентификаторов для установления связи
US8942745B2 (en) Methods and apparatus for dynamic carrier selection for cell base stations
US20110130144A1 (en) Handoff in a self-configuring communication system
US20130258875A1 (en) Method and Apparatus for Accounting of Cell Related Data
KR101473683B1 (ko) 핸드오버 제어
JP2013502878A (ja) 共同設置されたマクロおよびフェムト基地局の展開を管理するための方法、および移動局のハンドオフを開始するための方法
EP2453700A1 (fr) Identification de stations de base voisines
Vondra et al. Distance-based neighborhood scanning for handover purposes in network with small cells
KR20140090030A (ko) 기준 신호 크기 변경 시스템 및 방법
EP2262316B1 (fr) Contrôle de transfert
WO2018069180A1 (fr) Localisation d&#39;unités de communication sans fil mobiles
EP2268079B1 (fr) Identification d&#39;une station de base parmi des stations de base candidates au transfert qui utilisent le même code de brouillage principal
Nasrin et al. A self-adaptive handoff decision algorithm for densely deployed closed-group femtocell networks
JP6040588B2 (ja) 無線基地局装置、通信制御方法および通信制御プログラム
US20160037407A1 (en) Radio Network Node, a Base Station and Methods Therein
EP2395790B1 (fr) Réseau sans fil et procédé de transfert d&#39;une connexion d&#39;appel
WO2018069181A1 (fr) Entités de réseau, système de communication sans fil et procédé d&#39;amériolation d&#39;une relation entre de multiples cellules de présence
Razavi et al. Neighbour cell list management in wireless heterogeneous networks
JP2013187835A (ja) ランダムアクセス制御装置、無線基地局装置、管理装置およびランダムアクセス制御プログラム
RU2481735C2 (ru) Использование идентификаторов для установления связи

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 17780410

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 17780410

Country of ref document: EP

Kind code of ref document: A1