Patent Application
20130040649
This disclosure relates generally to a technical field of location estimation and, in one example embodiment, to a system, method and an apparatus for mobile device location estimation using operational data of a wireless network.
Location based services (LBS) may be an emerging trend in today's digital world. A variety of businesses may use LBS to strategically reach existing and/or potential customers. For example, a restaurant may use location information of a user to offer attractive discounts to a user, when the user is in a vicinity of the restaurant. In another example, location of users commuting on a specific route may be used to determine the meaningful travel information (e.g., speed of traffic, congestion, etc.) on that route, which when provided to a user may save commute time of the user. Example of other contexts that LBS are used may include health, indoor object search, entertainment, work, and/or personal life. LBS may depend on location of a mobile communication device.
Conventional technologies often use global Positioning System (GPS) device to determine positions of mobile communication devises and transmit these data via a wireless network to businesses. While this approach may give accurate information for a small number of devices, any attempt to gather positioning information from a large number of devices may use up large amounts of scarce bandwidth from the wireless network. Further, the said approach may be cost intensive and gathering all the GPS data may be time intensive as well. Further, GPS data may not be available in locations where LBS may be used extensively such as urban cities where high elevation buildings block access to a clear sky.
On the other hand, wireless technologies may have a vast infrastructure of communication facilities that generate data routinely to enable the system to properly function, e.g., to enable cellular phone users to place and receive calls and stay connected to these calls as they move though the cell sectors of a system. Examples of these data include signaling data, call detail records (CDR), handover messages, and/or registration messages. In view of the foregoing, there is a need for a technology for location estimation of mobile communication devices based on data from wireless networks.
Disclosed are a method, system and apparatus for mobile device location estimation using operational data of a wireless network. In one aspect, a method includes creating, by a modeling module, sector geometry of an antenna in the wireless network based on a tower data of the wireless network and first operational data from the wireless network. The term sector geometry may generally refer to a geometry and/or data representative of a coverage area of an antenna. The method further includes creating, by the modeling module, a geospatial model of a geospatial feature for an area associated with the wireless network. The method also includes generating, by the modeling module, one or more range bands for the antenna based on the first operational data. Each of the range bands may be bound by a first distance and a second distance from the antenna. Further, the method includes estimating, by a location module, a location of a mobile device in the wireless network. The location may be estimated based on the sector geometry of the antenna, the geospatial model of the geospatial feature, and the one or more range bands of the antenna. The mobile device may be serviced by the antenna.
The term ‘first operational data’ as used herein may generally refer to signaling data collected at a first time. The first operational data may be used to determine the coverage area of an antenna. In some embodiments, the first operational data may be used to estimate the location of the mobile device as well.
In another aspect, a position determination engine may include a modeling module. The modeling module is configured to create, for at least one antenna of one or more antennas in a wireless network, a sector geometry representative of a coverage area of the at least one antenna. The sector geometry may be created based on a tower data of the wireless network and first operational data from the wireless network. The modeling module is also configured to create a geospatial model of a geospatial feature for an area associated with the wireless network. In addition, the modeling module is configured to generate, for the at least one antenna, one or more range bands based on the first operational data. Each of the range bands are bound by a first distance and a second distance. Further, the position determination engine includes a location module configured to estimate a location of a mobile device communicatively associated with an antenna of the one or more antennas in the wireless network. The location may be estimated based on the sector geometry of the antenna, the geospatial model of the geospatial feature, the one or more range bands of the antenna and second operational data.
The term ‘second operational data’ as used herein may generally refer to signaling data collected at a second time. The second operational data may be used to estimate a location of the mobile device. In some embodiments, the second operational data may be used to determine the coverage area of antennas in the network along with determining the location of the mobile device.
In yet another aspect, a system includes a position determination engine. The position determination engine includes a modeling module. The modeling module is configured to create, for each antenna of one or more antennas in the wireless network, a sector geometry representative of a coverage area of each antenna. The sector geometry may be created based on a tower data of the wireless network and historical signaling data from the wireless network. Further, the modeling module is configured to create a geospatial model of a geospatial feature for an area associated with the wireless network. In addition, the modeling module is configured to generate, for each antenna, one or more range bands. Each of the range bands may be bound by a first distance and a second distance that is determined based on the historical signaling data. The system further includes a location module configured to estimate a location of a mobile device in the wireless network. The location may be estimated based on the sector geometry of at least one antenna of the one or more antennas in the wireless network, the geospatial model of the geospatial feature, the one or more range bands of the at least one antenna, and real-time signaling data obtained from the wireless network.
In an additional aspect, a method includes creating, by a modeling module, for each antenna of one or more antennas in the wireless network, a sector geometry re-presentative of a coverage area of each antenna. The sector geometry may be based on a tower data of the wireless network and first operational data from the wireless network. In addition the method includes creating, by the modeling module, a geospatial model of a geospatial feature for an area associated with the wireless network. Further, the method includes generating, by the modeling module, for each antenna, one or more range bands. Each range band may be bound by a first distance and a second distance based on the first operational data. The method also includes estimating, by a location module, a location of a mobile device communicatively associated with an antenna from the one or more antennas in the wireless network. The location may be estimated based on the sector geometry of the antenna, the geospatial model of the geospatial feature, and the one or more range bands of the antenna.
In yet another aspect, a position determination engine includes a modeling module. The modeling module is configured to create, for each antenna of one or more antennas in the wireless network, a sector geometry representative of a coverage area of each antenna. The sector geometry may be created based on a tower data of the wireless network and first operational data from the wireless network. Further, the modeling module is configured to create a geospatial model of a geospatial feature for an area associated with the wireless network. In addition, the position determination engine includes a location module. The location module is configured to estimate a location of a mobile device communicatively associated with an antenna of the one or more antennas in the wireless network. The location is estimated based on the sector geometry of the antenna, the geospatial model of the geospatial feature, and a range band of the antenna.
Example embodiments are illustrated by way of example and not limitation in the figures of accompanying drawings, in which:
Many aspects of the invention can be better understood with reference to the above drawings. The elements and features shown in the drawings are not to scale, emphasis instead being placed upon clearly illustrating the principles of exemplary embodiments of the present invention. Moreover, certain dimensions may be exaggerated to help visually convey such principles. In the drawings, reference numerals designate like or corresponding, but not necessarily identical, elements throughout the several views. Other features of the present embodiments will be apparent from the Detailed Description that follows.
Disclosed are a system, a method and an apparatus for mobile device location estimation using operational data of a wireless network It will be appreciated that the various embodiments discussed herein need not necessarily belong to the same group of exemplary embodiments, and may be grouped into various other embodiments not explicitly disclosed herein. In the following description, for purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of the various embodiments.
The mobile device (MD) 105 transmits signals to and receives signals from the radiofrequency cellular tower 110 (e.g., transmission tower), while within a geographic cell covered by the cellular tower 110. These cells can vary in size based on anticipated signal volume. The cellular tower 110 may include one or more antennas that facilitate communication within the cell. In one embodiment, the cellular tower 110 may use an omni directional antenna or multiple directional antennas to handle communication within the cell. For example, a cellular tower 110 may have 3 directional antennas that cover 120 degrees each and thereby facilitating communication in 360 degree coverage area. The coverage area of an antenna may be referred to as a sector.
The base transceiver station (BTS) 115 facilitates providing service to mobile subscribers within a cell. Several BTS'S are combined and controlled by the base station controller (BSC) 120 through a connection called the Abis interface. The position determination engine 100 can interface with the Abis interface line as illustrated in
The position determination engine 100 may monitor operational (e.g., signaling) data in the wireless network either directly or using a signal monitoring system such as a protocol analyzer. Alternatively, these messages may be extracted from a Base Station Manager that continuously monitors message streams on the BTS 115.
The term ‘operational data’ as used herein, may generally refer to any appropriate signaling data between an antenna (of a cellular tower) and a mobile device. In one embodiment, during communication, multiple antennas from one or more cellular towers may be communicably visible to and/or may service the mobile device 105. However, at any given time, one antenna of the multiple antennas visible to the mobile device, handles communication (e.g., holds the call) associated with the mobile device, which is referred to as ‘reference antenna’ herein. The other antennas may be referred to as non-reference antennas. For any given reason, if the reference antenna is not able to handle the communication associated with the mobile device, then the communication may be handed over to one of the non-reference antennas. The reference and non-reference antennas associated with the mobile device may be updated based on a location of the mobile device 105.
In an exemplary embodiment, the position determination engine 100 may receive operational data from a variety of locations in the wireless network. These locations may include the BSC 120, Abis interface, the BTS 115, MSC 125, and/or the HLR 130. The position determination engine is further described below in association with
Turning to
The wireless network 202 can exchange information with the data extraction (DEX) module 204 of the position determination engine 100. Further, the DEX module 204 can exchange information with the parser module 208. The parser module 208 is configured to exchange information with the modeling module 206 and/or the location module 210. The modeling module 206 can exchange information with the location module 210, which in turn can exchange information with end users 212.
In one embodiment, the DEX module 204 can directly exchange information with the modeling module 206 and/or the end users 212. In one embodiment, the modeling module can exchange information with the end users 212. In some embodiments, a process other than DEX module 204 may provide operational data to the parser module 208, modeling module 206 and/or the location module 210. The end users 212 may include information service providers, location based service providers, a government organization, emergency service providers, transportation providers or media outlets. The type of information exchanged between the modules is described below in association with
Turning to
In one embodiment, the parser module 208 may receive the first operational data and/or second operational data from the DEX module 204. In addition, the parser module 208 may process the first operational data and/or the second operational data. Further, the parser module 208 can extract one or more signaling records from the operational data (first and/or second). Typical information contained in a signaling record may include at least the identity of one or multiple cell towers/antennas servicing a call, data indicating the elapsed time that signals take to travel the distance from the antenna to the mobile device (round-trip delay (RTD)), and/or other measures related to distance from the antenna such as a measure of signal phase and/or signal strength. The parser module 208 may parse the signaling record to extract desired data such as the identity of one or multiple cell towers/antennas participating listed in the signaling record call, RTD, signal phase and/or signal strength associated with each antenna. Further, when multiple antennas are communicably visible to the mobile device 105, the parser module 208 can sort the multiple antennas in a specific order. The sorting mechanism may be described in greater detail, in association with
Further, the signaling record information is time stamped, which allows estimation of the location of the mobile device 105 at a particular point in time. The types and timing of the signaling record from the wireless network 202 may differ by the specific wireless network 202 technology used by the carrier in an area. The types of signaling record that can be received and used in location estimation include call start, completion, or drop, as well as cell tower “handoff” or for some technologies, periodic transactions throughout the call. In one embodiment, signaling records may be generated at the beginning or a call, at the end of a call and/or periodically in between calls based on the wireless network technology. Operational data may be produced for voice calls, text messages, and/or data connections. The operational data can be thought of as a “picture” of one or more cell towers/antennas the mobile device could “see” at the time of the generating or logging the signaling record.
The DEX module 204 interacts with the wireless network 202 to retrieve operational data from the wireless network 202. In one embodiment, the DEX module 204 may be a software module coupled to any appropriate element of the wireless network 202 to retrieve operational data from the wireless network 202. In another embodiment, the DEX module may be a hardware device or a combination of software and hardware device coupled to any appropriate element of the wireless network 202. The DEX module 204 may stream data from the wireless network to the position determination engine 100. The streamed operational data may be stored in the position determination engine 100 or in a storage device external to the position determination engine 100.
In one embodiment, the first operational data 350 may refer to operational data used to generate various geospatial models that are described in greater detail below and in association with
The second operational data 360 may refer to operational data used to calculate location of the mobile device in the wireless network 202. Once geospatial models are generated using the first operational data, the second operational data may be collected in near real-time during the course of estimating the location of the mobile device 105. In some embodiments, the second operational data 360 may be collected prior to estimating the location of the mobile device 105. In an alternate embodiment, the first operational data 350 may be used to estimate location of the mobile device. Hereinafter, the first operational data may be referred to as historical operational data and the second operational data may be referred to as real-time operational data.
In operation 356, the modeling module 206 may generate a wireless network sector database (cell sector database hereinafter) (shown in
Using the tower/antenna data 352 and the parsed data associated with historical operational data, the modeling module 206 may generate a geospatial model representative of the wireless network coverage. The geospatial model representative of the wireless network coverage may include locations of one or more antennas in the wireless network 202. Further, the geospatial model representative of the wireless network coverage (hereinafter network map) may include geometries defining the coverage areas of each antenna (sectors) of the one or more antenna in the wireless network 202. In one embodiment, calculations of the network map can be performed as often as desired to keep the model updated for changes in the cellular network. For example, the network map may be created every time a carrier adds a tower in the cellular network or when a tower is removed from the cellular network. In an additional embodiment, the calculations of the network map may include changing atmospheric conditions.
Further, in operation 356, the road map created in operation 368 may be stored in the cell sector database and incorporated into (or overlaid on) the network map to create the cell sector database. The process of creating the network map and the cell sector database 580 (in operation 356) is described in greater detail in association with
In operation 370, using the real-time operational data associated with the mobile device 105 and the cell sector data base 580, the location module 210 may estimate the location of the mobile device 105 in the wireless network 202. In another embodiment, the location of the mobile device 105 may be estimated based on the road map, the network map and other features such as range bands associated with the network map. Range bands are described in detail below, in associated with
The overall process of the position determination engine 100 may be described in greater detail in the following paragraphs, in association with
Turning to
The DEX module 204 can exchange information with the antenna data extraction module 402. The antenna data extraction module 402 can exchange information with the modeling module 206 and/or the antenna sort module 404. Further, the antenna sort module 404 may exchange information with antenna list module 406, which in turn exchanges information with the location module 210. In some embodiments, the antenna list module 404 may exchange information with the modeling module 206. In an alternate embodiment, operations of the antenna data extraction module 402, the antenna sort module 404 and/or the antenna list module 406 may be performed using any one of the modules. The information exchanged between modules and the operation of the parser module is described in further detail in associated with
Turning to
In an exemplary embodiment, the one or more non-reference antennas may be sorted based on RTD values associated with the antennas. Once the non-reference antennas are sorted based on the RTD values and if two or more non-references antennas have substantially similar RTD values, then the first sorted list of non-reference antennas is further sorted based on signal strength values of each non-reference antennas. Based on RTD value, the antennas may be sorted as antennas in the signaling record having lowest RTD value to antennas having highest RTD value, with antenna having lowest RTD value as preferred antenna. Based on signal strength, the antennas may be sorted as antennas in the signaling record having the highest signal strength to antennas having lowest signal strength, with the antenna having highest signal strength as the preferred antenna. In another example embodiment, the non-reference antennas may be sorted based on the signal strength after which they maybe sorted based on the RTD value if required.
Further in operation 456, the sorted non-reference antennas along with the reference antenna are arranged as a list. Further, the list of sorted antennas communicably visible to the mobile device may be forwarded to the location module 210 to facilitate estimating a location of the mobile device. The reference antenna may be the first listed antenna followed by the non-reference antennas in the sorted order.
In one embodiment, the signaling record may include multiple fields. One field of the multiple fields may identify the antenna as a reference antenna. In an alternate embodiment, if the field that identifies the reference antenna is empty, the parser module 208 may sort all the antennas based on signal strength and/or RTD values. The first antenna (antenna with lowest RTD value or highest signal strength) in the sorted list may be identified as reference antenna. In another embodiment, if the field that identifies the reference antenna is empty, the parser module 208 may generate a corresponding error message, which may be transmitted to the end user, location module 210 and/or the modeling module 206. The modeling module 206 is described in greater detail in association with
In another exemplary embodiment, the parser module 208 may process the real-time operational data to extract the associated signaling record. The signaling record may include a number of antennas communicatively associated with (e.g., communicably visible or servicing) a mobile device of the signaling record. The number of antennas may be sorted based on RTD values. In one embodiment, the antenna with the smallest RTD may be set as the reference antenna (regardless of the reference identifier field) and the following antennas may be set as non-reference antenna.
Turning now to
The parser module 208 may exchange information with the percentile module, which in turn may exchange information with the lobe generation module 506. Further, the parser module 208 may exchange information with the range band module 508. In an alternate embodiment, the percentile module 502 and/or range band module 508 may directly communicate with the DEX module 206, if the data received from the DEX module is pre-processed to extract desired antenna data.
The lobe generation module 506 and the range band module may exchange information with the ring module 510. Further, the ring module may exchange information with the ring road module 514. The ring road module 514 may be coupled to the road network database 512, with which information may be exchanged. The range band module 508, the lobe generation module 506, the ring module 510 and the ring road module 514 may be logically coupled to the cell sector database 580. In one embodiment, information may be exchanged between the cell sector database 580 and range band module 508, the lobe generation module 506, the ring module 510 and the ring road module 514. The operation of the modeling module and the information exchanged is described in further detail, in association with
Turning to
In operation 550, the percentile module 502 may receive a number of RTD values associated with signaling records of historical operational data collected over a predetermined period of time. In some embodiments, the percentile module 502 may receive other values such as signal strength and/or signal phase.
In one embodiment, the RTD values may be received from the parser module 208. In another embodiment, the RTD values may be directly received from the DEX module 204 provided the DEX module 204 is configured to extract RTD values. In operation 552, the percentile module 502 may process a number of RTD values, associated with an antenna, to generate RTD deciles. In an alternate embodiment, the received RTD values may be distributed into an ‘x’ number of groups. Further, in operation 552, the percentile module 502 may determine a characteristic RTD value based on the RTD deciles. The characteristic RTD value may be determined such that a given percentage of the number of received RTD values of the antenna fall below the characteristic RTD value. For example, the 80th percentile RTD value may be chosen as characteristic RTD such that 80% of the received RTD values fall below the characteristic RTD value.
In operation 554, using the characteristic RTD value and static parameters such as the tower/antenna data 252 (and/or Voronoi generated sectors), the lobe generation module 506 may generate a geometry representative of coverage area of the antenna. The geometry of the antenna coverage area may represent at least a maximum effective range of the antenna that may be calculated based on the characteristic RTD obtained from the historical operational data. The maximum effective range may refer to the maximum distance from the antenna that pilot information from the antenna may be received. Further, the geometry of the antenna coverage area may represent the location of the antenna in the cellular network, the direction of orientation of the antenna and/or the spread of the signal beam associated with the antenna, which may be calculated based on the static tower/antenna data 252. The tower/antenna data 252 may be incorporated with the characteristic RTD (which is a dynamic parameter) to enhance the geometry of the antenna coverage to substantially accurately represent the coverage of the antenna is the real world.
Creating the geometry representative of the antenna coverage area may include creating a “bounding polygon” (typically looking like a kite with the antenna at the bottom of the kite pointed at the top and the “top” point of the kite which may be defined by the maximum calculated effective range of the antenna). In some embodiments, the maximum calculated effective range of the antenna may be determined based on other parameters associated with the historical operational data such as signal phase and/or signal strength. In an alternate embodiment, the maximum calculated effective range of the antenna may be determined based on static parameters. In another embodiment, the maximum effective coverage of the antenna may be provided by the wireless network carrier. The modeling module, may create the sector geometries based on the maximum effective coverage of the antenna sent by the wireless network carrier, the RTD values or a combination of both. Further, the “width” of the polygon (e.g., kite shape) may be determined by the published beam width of the antenna obtained from the tower/antenna data 252 (and/or Voronoi generated sectors). The overall shape may be governed by ratios that were derived to best mimic the off axis attenuation that directional antennas exhibit. Once the bounding polygon is calculated, an appropriate smoothening function may be applied to approximate and smoothen the boundaries of the sector within the bounding polygon. The output of the function may be a lobe-shaped sector approximation that incorporates the dynamic parameter from historical operational data, along with the published identification, location, azimuth, and beam width of the antenna from the tower/antenna data 252. The geometry representative of the antenna coverage area (hereinafter sector geometry) may be stored in the cell sector database 580. The creation of the sector geometry may be graphically presented in
Turning now to
Returning to
Each antenna may have a number of range bands associated with it, based on the number of RTD values of the antenna. For example, an antenna in the cellular network may have 1000 range bands associated with each antenna. Range band 100 may extend from 1000 meters (e.g., first distance) to 1020 meters (e.g., second distance) which may correspond to RTD values 100 to 120. Thus range band 100 may represent any RTD values that fall between 100 and 120. RTD values that fall outside 100 to 120 value range may fall in another range band associated with the antenna.
Further, in operation 556, the ring module 510 may mathematically or logically intersect (or overlay) each range band of the antenna with the sector geometry of the antenna which may result in a new geometry that represents an area common to the range band and the sector geometry, referred to as a ring. In one embodiment, for each antenna, there may be as many or lesser number of rings as the number of range bands associated with the antenna. The ring may be portion of the range band. In one embodiment, if a range band lies outside the sector geometry, then the range band may not have a ring since the range band does not intersect the sector geometry. The calculated range band values (and/or geometry) and the ring geometries may be stored in the cell sector database 580.
In operation 558, the ring road module 514 may retrieve the road map from the road network database 582. In one embodiment, the road network database 512 may be a part of the cell sector database 580. Further, in operation 558, the ring road module 514 may mathematically or logically intersect the road map with each ring of the antenna. The geometry resulting from the intersection of the road map and the ring, if any, may be stored in the cell sector database 580 as ring roads.
The foregoing operations described in association with
The cell sector database 580 may refer to a collection of data including data representing sector geometry for each antenna in the cellular network, range band geometry for each antenna in the cellular network, ring geometry of each range band for each antenna in the cellular network, ring road geometry of each ring for each antenna in the cellular network and/or the road map. Using an appropriate API, the data of the cell sector database may be visually represented (e.g., as a map) as illustrated in
Turning to
In one embodiment, the cell sector database 580 may be preprocessed prior to estimating the location of a mobile device in the wireless network 202. In another embodiment, the cell sector database 580 may be created as an initial phase of the location estimation process. Using the data in the cell sector database 580, the location module 210 may estimate the location of a mobile device 105 in the wireless network 202 based on real-time operational data. In one embodiment, the real-time operational data may be streamed by the DEX module 204 once the cell sector database 580 is created.
In one embodiment, the cell sector database may refer to a collection of data including data representative of the sector geometry for each antenna in the cellular network and road map. In the said embodiment, the ring geometry of each range band for each antenna in the cellular network and ring road geometry of each ring for each antenna in the cellular network may be created by the location module 210. The location estimation module 210 may be described in greater detail in association with
In one embodiment, a location of a mobile device 105 in the wireless network 202 may be estimated, by the location module 210, based on real-time operational data received (e.g., streamed by DEX module 204) from the cellular network. The real-time operational data may include a number of signal records. Each signal record may be associated with the communication of a mobile device in the cellular network and the one or more antennas assisting the communication.
In one embodiment, the location of the mobile device 105 may be estimated for each signaling record. In another embodiment, the location of the mobile device 105 may be estimated upon request. All the estimated locations for the mobile device 105 may be stored in a location database and the location may be retrieved by an end user 212 through accessing the database. Alternately, the location may be presented to the end user 212 by the position determination engine 100 upon request.
Turning to
The parser module 204 may exchange information with the DEX module 204. In addition, the parser module 208 may exchange information (e.g., list of antennas 706) with the intersection module 702. In an alternate embodiment, the intersection module 702 may receive real-time operational data directly from the DEX module 204. Further, the modeling module 206 may exchange information with the intersection module 702, which in turn exchanges information with the location estimation module 704. The location estimation module 704 may exchange information with end users 212. The operation of the location module 210 and the information exchanged between the modules is discussed in greater detail in association with
Turning to
Further, for each signaling data the parser module 208 may retrieve information associated with each antenna in the list 706. The information associated with the antenna extracted from the signaling record may include at least a market identifier, a cell/tower identifier, a sector/antenna identifier, a round trip delay and/or signal strength.
In operation 720, the intersection module 702 may receive the list of antennas 706 and/or the information associated with the each antenna in the list 706. Using the received list of antennas 706 and information associated with each antenna, in operation 722, the intersection module 702 may access the cell sector database to retrieve appropriate data from the cell sector database for each antenna in the list 706. The data from the cell sector database 580 may be used to estimate the location of the mobile device 105. The process of retrieving appropriate data from the cell sector database based on the real-time operational data is described in the following paragraph, using an example.
In the example, a cell sector database 580 may include data representative of the sector geometries of antenna A, B and C in the wireless network 202. The antennas may belong to one tower 110 or different towers in the wireless network 202. Further, the cell sector database 580 may include data representative of range bands associated with each antenna, ring geometry for each range band and ring road geometries. In the example embodiment, the DEX module 204 may stream real-time operational data from the wireless network 202 to the position determination engine 100. The real-time operational module may include a signaling record X associated with mobile device 105. The parser module 204 may process the signaling record X to generate a list of antennas communicably visible to (and/or serving) the mobile device 105 and information associated with each antenna in the list. In the example embodiment, the information from signaling record X may identify antenna A and antenna C as the serving antennas. Further, the list may identify antenna A as the reference antenna and antenna C as the non-reference antenna. The information associated with each of the antennas may include, RTD value associated with antenna A (e.g., 100) and RTD value associated with antenna C (e.g., 60). Once the RTD values are determined, the intersection module 702 may access the cell sector database 580 to retrieve sector geometry associated with antenna A and antenna C. Further, the intersection module 702 may retrieve the range band associated with antenna A which contains the RTD value 100 (corresponding distance value) (e.g., range band 10) and the range band associated with antenna C which contains the RTD value 60 (corresponding distance value) (e.g., range band 6). In addition, the rings and ring roads associated with range band 10 and range band 6 may be retrieved as well.
Once the appropriate data from the cell sector database is retrieved, in operation 724 the intersection module 702 may determine an overlapping region (e.g., common region, region of intersection, etc.) between the areas representative of the geometries retrieved from the cell sector database 580.
When the list includes one antenna, then the intersection module 702 may set the common region (or intersection region) as either the ring geometry and/or ring road geometry associated with the antenna. However, if the list includes more than one antenna, then the intersection module 702 may determine the common region by finding an intersection between one or more elements (e.g., rings, ring roads, sector geometry, etc.) of all the listed antennas.
The number of antennas in the list 706 may determine the number of constraints used to estimate the location of the mobile device 105. In some embodiments, the constraints may be relaxed to obtain a common region. The process of determining a common region when the list 706 includes a single antenna and/or multiple antennas may be described in greater detail in the following paragraphs.
Case 1: When the list of antennas 706 includes a reference antenna and no non-reference antennas.
The process of the intersection module 702 may include:
The intersection module 702 may retrieve the ring geometry and the ring road geometry using an appropriate function. In one embodiment, the function may return a value for the ring and/or ring road. In another embodiment, the function may return an empty value for the ring road. An empty ring road value may indicate that there are no roads intersecting the ring. In some embodiments, the function may return an empty value for the ring geometry. In one embodiment, an empty ring value may indicate that the range band corresponding to RTD value (RTD_ref) may be outside the sector geometry of the antenna and therefore does not intersect the sector geometry of the reference antenna. In another embodiment, an empty ring value may indicate that a range band comprising the RTD_ref value does not exist in the cell sector database 580. In an additional embodiment, the function may return multiple values for the ring road which may indicate that the ring geometry intersects and the road (or multiple roads) intersects at multiple locations within the ring (multiple disjoint ring roads for a given ring).
On the basis of the intersections, the intersection module 702 may determine the common region (region of intersection). In one embodiment, the common region may be identified as the ring road, if any. If there is no ring road, then the ring may be identified as the common region. If, both the ring and ring road does not exist then sector geometry of the reference antenna may be identified as the common region.
In another embodiment, the cell sector database may include the sector geometry of the antennas in the wireless network 202 and the road map. The range bands, ring geometry and the ring road geometry may be created by the location module 210 as a part of the location estimation process. The location module 210 may create the range band based on RTD value of the antenna (in the list 706) received from the parser module 208. Using the sector geometry of the antenna from the cell sector database 580, the road map from the cell sector database 580 and the created range band, the location module may determine a common region.
The process of estimating a common region and estimating a location therefrom for one antenna is illustrated in greater detail in
Returning to
Case 2: When the list of antennas 706 include a reference antenna and a non-reference antenna.
The process of the intersection module 702 may include:
In this case, the common region(s) may be defined as the geometry in which all the constraints are met. The constraints may include sector geometry of reference antenna (ref_id), sector geometry of non-reference antenna (non-ref_id), range_ref, range_non-ref, ring geometry of range_ref, ring geometry of range_non-ref, ring road geometry of range_ref and ring road geometry of range_non-ref. In an example embodiment, the common region(s) may be determined based on either one of the following equations that use AND operators:
Common region=(Ring Roadreference AND Ring Roadnon-reference) (1)
Or
Common region=(Ringreference AND Ringnon-reference) AND (Sectorref
Equation 1 and Equation 2 may identify the common region(s) as a geometry obtained when all the constraints intersect. In other words, according to Equations 1 and 2, the mobile device 105 may be present in a region where the ring roads of the reference sector and the non-reference sector intersect or the mobile device may be present in the non-reference sector, the reference sector, the reference ring, the non-reference ring and the road map.
If the common region determined by Equations 1 or 2 returns an empty set i.e., an intersection between all the constraints do not exist, then the conditions applied on the constraints may be relaxed. In an example embodiment, the condition on the constraints may be changed such that the mobile device may be located in either the sector geometry of the reference antenna OR the sector geometry of the non-reference antenna instead of using an AND operation. In an example embodiment, the common region(s) may be determined based on the following equation that uses an OR operator:
Common region=(Ringreference AND Ringnon-reference) AND (Sectorref
If Equation 3 returns an empty value as well, the conditions on the constraints are further relaxed till at least one common region is determined. In no common region is identified, the sector geometry of the reference antenna may be defined as the common region.
In another embodiment, the cell sector database may include the sector geometry of the antennas in the wireless network 202 and the road map. The range bands, ring geometry and the ring road geometry may be created by the location module 210 as a part of the location estimation process. The location module 210 may create the range band of the reference antenna and the non-reference antenna based on the RTD value of the reference antenna and the non-reference antenna respectively (in the list 706). Using the sector geometry of the reference and the non-reference antenna from the cell sector database 580, the road map from the cell sector database 580 and the created range bands, the location module may determine a common region based on Equations 2 or 3. The process of estimating a common region and estimating a location therefrom is illustrated in greater detail in
Turning now to
In operation 750, the intersection module 702 may retrieve the RTD value of the reference antenna, the RTD value of the first non-reference antenna and the RTD value of the second non-reference antenna in the list 706. In one embodiment, the parser module 208 may provide the RTD value for each antenna in the list 706. In an alternate embodiment, the intersection module 702 may process the signaling record to extract the corresponding RTD values associated with each antenna in the list 706.
In operation 752, the intersection module 702 may determine whether the RTD value of either one of the antennas in the list 706 is greater than a specified value. If the RTD value is greater than the specified value, the intersection module 702 may proceed to operation 754, where the intersection module 702 may define the sector geometry of the reference antenna as the common region. In operation 752, if it is determined that the RTD value is below the specified value, the intersection module 702 may proceed to operation 756. In operation 756, the intersection module 702 may access the cell sector database 580 to retrieve the range band geometry that includes the distance value corresponding to the RTD value of the reference antenna. In addition, the intersection module 702 may make appropriate function calls to retrieve the ring geometry associated with the range band geometry of the reference antenna.
In operation 758, if the function call for the ring geometry returns an empty value, the intersection module 702 may proceed to operation 754, in which the sector geometry of the reference antenna is defined as the common region. If the function call for the ring geometry returns a value, then the intersection module 702 proceeds to operation 760. In operation 760, the intersection module 702 may issue a function call to retrieve ring road geometry for the ring geometry of the reference antenna. In operation 762, if the function call for the ring road geometry returns an empty value, the intersection module 702 may define the sector geometry of the reference antenna as the common region (in operation 754). However, if the function call for the ring road returns a value, the intersection module 702 may proceed to operation 764.
In operation 764, the intersection module 702 may issue a function call to retrieve both the ring geometries associated with the first non-reference antenna and the second non-reference antenna. Based on the value of the function call, the intersection module 702 may proceed to either operation 774 or operation 768. If the function call for ring geometries of the first non-reference antenna (associated with RTD value of first non-reference antenna) and the second non-reference antenna ((associated with RTD value of first non-reference antenna) returns a value, then the intersection module proceeds to operation 768. In operation 768, the intersection module 702 checks if the ring geometries of the first non-reference antenna and the second non-reference antenna intersect. If they intersect, the intersection module 702 may proceed to operation 770, where an additional constraint is added. The additional constraint may be the ring road of the reference antenna. In operation 770, the intersection module 702 checks if the ring geometry of the first non-reference antenna, ring geometry of the second non-reference antenna and the ring road geometry of the reference antenna intersect with each other. If the ring geometries of the first non-reference antenna and the second non-reference antenna and the ring road geometry of the reference antenna intersect, intersection module 702 may proceed to operation 772. In operation 772, the intersection module 702 may define the geometry (or region) representative of the area of intersection of the he first non-reference antenna and the second non-reference antenna intersect and the ring road geometry of the reference antenna, as the common region.
If the ring geometries of the first non-reference antenna and the second non-reference antenna and the ring road geometry of the reference antenna do not intersect, the intersection module 702 may proceed to operation 774. Returning to operation 766, if the function call for ring geometries of the first non-reference antenna and the second non-reference antenna returns an empty value, the intersection module 702 may proceed to operation 774. In operation 774, the intersection module 702 may check if the cell sector database contains the ring geometry of the first non-reference antenna. If the cell sector database 580 contains the ring geometry of the first non-reference antenna, then the location module may retrieve the ring geometry of the first non-reference antenna and proceed to operation 780. In operation 780, the intersection module 702 checks if the ring geometry of the first non-reference antenna intersects the ring road geometry of the reference antenna. If the ring geometry of the first non-reference antenna intersects the ring road geometry of the reference antenna, in operation 786 the intersection module 702 may define the geometry representative of the area of intersection between the ring geometry of the first non-reference antenna and the ring road geometry of the reference antenna as the common region.
If either the cell sector database does not contain the ring geometry of the first non-reference antenna or the ring geometry of the first non-reference antenna does not intersects the ring road geometry of the reference antenna, the intersection module 702 may define the ring road geometry of the reference antenna as the common region.
Briefly, the intersection module 702 may check whether the reference antenna has a ring road associated with the RTD value of the reference antenna. If there is a ring road, the intersection module 702 may check if the non-reference antennas have ring geometries associated with their respective RTD values and then tries to find an intersection between the ring roads of the reference antenna and the rings of the non-reference antennas. If such an intersection does not exist, then the intersection module 702 may relax the constraint, by trying to find an intersection between the ring road of the reference antenna and the ring geometry of the first non-reference antenna. If such an intersection does not exist for the relaxed constraint, then the ring road of the reference antenna may be set as the common region. However, if any of the said intersections do exist, then the intersection module 702 defines the geometry representative of the area of intersection as the common region.
Further, if the ring road geometry for the reference antenna does not exist, the sector geometry of the reference antenna is set as the common region. The intersection module 702 may return the common region to the location estimation module 704.
Returning to
Although the present embodiments have been described with reference to specific example embodiments, it will be evident that various modifications and changes may be made to these embodiments without departing from the broader spirit and scope of the various embodiments. For example, the various devices and modules described herein may be enabled and operated using hardware circuitry (e.g., CMOS based logic circuitry), firmware, software or any combination of hardware, firmware, and software (e.g., embodied in a machine readable medium). For example, the various electrical structure and methods may be embodied using transistors, logic gates, and electrical circuits (e.g., application specific integrated (ASIC) circuitry and/or in Digital Signal Processor (DSP) circuitry).
The terms “invention,” “the invention,” “this invention,” and “the present invention,” as used herein, intend to refer broadly to all disclosed subject matter and teaching, and recitations containing these terms should not be misconstrued as limiting the subject matter taught herein or to limit the meaning or scope of the claims. From the description of the exemplary embodiments, equivalents of the elements shown therein will suggest themselves to those skilled in the art, and ways of constructing other embodiments of the present invention will appear to practitioners of the art. Therefore, the scope of the present invention is to be limited only by the claims that follow.
In addition, it will be appreciated that the various operations, processes, and methods disclosed herein may be embodied in a machine-readable medium and/or a machine accessible medium compatible with a data processing system (e.g., a computer system), and may be performed in any order (e.g., including using means for achieving the various operations). Accordingly, the specification and drawings are to be regarded in an illustrative rather than a restrictive sense.
This application claims priority to U.S. Provisional Patent Application No. 61/475,878 filed Apr. 15, 2011 in the name of Leonardo A. Soto Matamala and entitled “Mobile Device Location Estimation from Cell Network Signaling Data,” the entire contents of which are hereby incorporated herein by reference.
| Number | Date | Country | |
|---|---|---|---|
| 61475878 | Apr 2011 | US |
