System and method for distributed sensor system for object location measurement - Patents.com
The distributed sensor system synchronizes and correlates timestamped events from multiple receivers to accurately determine the location and identity of mobile devices in wireless communication systems, addressing the challenges of asynchronous data reception.
Patent Information
- Application Number
- JP2024527324
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2021-11-10
- Filing Date
- 2022-11-10
- Publication Date
- 2024-12-05
AI Technical Summary
Existing wireless communication systems face challenges in accurately determining the location and identity of mobile devices due to asynchronous and unsynchronized data reception by multiple receivers, which leads to incomplete and unreliable position estimation.
A distributed sensor system that combines data from multiple receivers to reconstruct a cohesive position estimate by synchronizing and correlating timestamped events, using beacon packets with unique timestamps and MAC addresses to triangulate the location and identify mobile devices.
The system provides accurate and reliable location estimation of mobile devices by merging asynchronous data from dispersed sensors, enhancing the precision and completeness of position determination.
Smart Images

Figure 2024544891000001_ABST
Abstract
Description
[Technical field]
[0001] (CROSS REFERENCE TO RELATED APPLICATIONS) This application claims priority to U.S. Application Serial No. 17 / 523,554, filed November 10, 2021, the disclosure of which is incorporated herein by reference in its entirety.
[0002] The embodiments disclosed herein generally relate to a system, apparatus, and / or method for providing a distributed sensor system for object position measurement. [Background technology]
[0003] No. 10,182,315 to Shpak (hereinafter the '315 patent) discloses a signal processing method that includes receiving at a predetermined location at least first and second signals transmitted from at least first and second antennas, respectively, of a wireless transmitter. The at least first and second signals encode identical data using a multi-carrier encoding scheme having a predefined cyclic delay between the transmitted signals. The received first and second signals are processed using a cyclic delay to derive a measurement of the phase delay between the first and second signals. Based on the measurement of the phase delay, an angle of departure of the first and second signals from a wireless access point to the predetermined location is estimated.
[0004] U.S. Patent No. 9,814,051 to Shpak (hereinafter the '051 patent) discloses a method for signal processing, which, among other things, includes receiving at least first and second signals at a predetermined location transmitted from at least first and second antennas of a wireless transmitter, respectively, the at least first and second signals encoding identical data using a multi-carrier encoding scheme having a predefined cyclic delay between the transmitted signals, and processing the received first and second signals using the cyclic delay to derive a measurement of the phase delay between the first and second signals. Based on the measurement of the phase delay, the method estimates an angle of departure of the first and second signals from the wireless transmitter to the predetermined location. Summary of the Invention
[0005] In at least one embodiment, an apparatus is provided for generating a mosaic of a wireless communication system. The apparatus includes a memory and a server. The server includes a memory and is programmed to receive from an associated access point first information indicative of (i) a first receiver timestamp at which the associated access point received a first packet from a mobile device and (ii) a second receiver timestamp at which the associated access point received a second packet from the first access point. The server is further programmed to determine a first difference between the first receiver timestamp and the second receiver timestamp to generate a first difference value, and to receive from the first location receiver second information indicative of (i) a third receiver timestamp indicative of the first location receiver receiving a third packet from the mobile device and (ii) a fourth receiver timestamp indicative of the first location receiver receiving the second packet from the first access point. The server is further programmed to determine a second difference between the third receiver timestamp and the fourth receiver timestamp to generate a second difference value, and to compare each of the first and second difference values to a predetermined reception time error range. The server is further programmed to determine that the first and third packets transmitted by the mobile device are identical in response to each of the first and second difference values being within the predetermined reception time error range.
[0006] In at least another embodiment, an apparatus for generating a mosaic for a wireless communication system is provided. The apparatus includes a memory and a server. The server includes the memory and is programmed to receive, from an associated access point, first information corresponding to an acknowledgement packet received from a mobile device. The acknowledgement packet is transmitted by the mobile device in response to a data packet transmitted by the associated access point, and the first information further corresponds to a receiver address field in the data packet providing an identification of the mobile device for the associated access point to transmit the data packet. The server is further programmed to access the receiver address field to determine the identity of the mobile device after the acknowledgement packet is received from the mobile device at the associated access point.
[0007] In at least another embodiment, a method of generating a mosaic for a wireless communication system is provided. The method includes receiving, at a server, first information from an associated access point indicative of (i) a first receiver timestamp at which the associated access point received a first packet from a mobile device and (ii) a second receiver timestamp at which the associated access point received a second packet from the first access point. The method includes determining a first difference between the first receiver timestamp and the second receiver timestamp to generate a first difference value. The method further includes receiving, from the first location receiver, second information indicative of (i) a third receiver timestamp indicative of the first location receiver receiving a third packet from the mobile device and (ii) a fourth receiver timestamp indicative of the first location receiver receiving the second packet from the first access point. The method further includes determining a second difference between the third receiver timestamp and the fourth receiver timestamp to generate a second difference value. The method further includes comparing each of the first and second difference values with a predetermined reception time error range, and determining that the first packet and the third packet transmitted by the portable device are identical in response to each of the first and second difference values being within the predetermined reception time error range.
[0008] In at least another embodiment, a method of generating a mosaic for a wireless communication system is provided. The method includes receiving, at a first server, first information from an associated access point corresponding to an acknowledgement packet received from a mobile device. The acknowledgement packet is transmitted by the mobile device in response to a data packet transmitted by the associated access point, and the first information further corresponds to a receiver address field in the data packet providing identification information of the mobile device for the associated access point to transmit the data packet. The method further includes accessing the receiver address field to determine an identity of the mobile device after the acknowledgement packet is received at the associated access point from the mobile device.
[0009] Embodiments of the present disclosure are particularly pointed out in the appended claims, however other features of the various embodiments will become more apparent and will be best understood by reference to the following detailed description taken in conjunction with the accompanying drawings. [Brief description of the drawings]
[0010] [Figure 1] FIG. 1 is a schematic diagram illustrating a system for wireless location detection, according to one embodiment. [Diagram 2] FIG. 2 illustrates a packet of information transmitted from a transmitter to various receivers. [Diagram 3] 3 is a diagram showing angles of arrival of received signals in the receiver of FIG. 2. [Figure 4] FIG. 2 illustrates a method for determining a transmitter location according to one embodiment. [Diagram 5] 2 corresponds to a more detailed method 250 for locating a transmitter, performed by the system of FIG. 1 in one embodiment. [Figure 6] FIG. 2 illustrates a scheme depicting identifying a transmitter based on coalesced instantaneous events performed by the system of FIG. 1 according to one embodiment. [Figure 7] 6 illustrates a method for determining a receiver's position based on the scheme of FIG. 5 according to one embodiment. [Figure 8] 6 illustrates another method for determining a receiver's position based on the scheme of FIG. 5 according to one embodiment. [Figure 9] 7 illustrates a more detailed method for determining the location of a mobile device relative to the scheme of FIG. 6 and the system of FIG. 1 according to one embodiment. [Figure 10]FIG. 13 illustrates an example of a table that a server can use in one embodiment to coalesce the identity of a mobile device based on at least one of a transmitter timestamp from the access point, a transmitter timestamp of the mobile device, and a receiver timestamp from the receiver to determine which receiver received a signal transmission from an identified transmitter. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0011] Where necessary, detailed embodiments of the present invention are disclosed herein, but it should be understood that the disclosed embodiments are merely exemplary of the present invention, which may be embodied in various alternative forms. The figures are not necessarily to scale, and some features may be exaggerated or minimized to show details of specific components. Therefore, specific structural and functional details disclosed herein are not to be construed as limiting, but merely as a representative basis for teaching those skilled in the art to employ the present invention in various ways.
[0012] It is recognized that the at least one controller (or at least one processor) disclosed herein may include various microprocessors, integrated circuits, memory devices (e.g., FLASH, random access memory (RAM), read-only memory (ROM), electrically programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or other suitable variations thereof), and software that cooperate with one another to perform the operations disclosed herein. Additionally, the at least one controller disclosed herein utilizes one or more microprocessors to execute computer programs embodied in non-transitory computer-readable media that are programmed to perform any number of functions as disclosed. Additionally, the controllers provided herein include a housing and various numbers of microprocessors, integrated circuits, and memory devices (e.g., FLASH, random access memory (RAM), read-only memory (ROM), electrically programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM)) disposed within the housing. The disclosed controllers also include hardware-based inputs and outputs for receiving and transmitting data, respectively, from and to other hardware-based devices, as described herein.
[0013] Packet wireless communication collection systems are necessary to passively ascertain the location of a portable radio ("device"). The device communicates with an associated access point ("AP") and bridges traffic to and from the Internet. Advances in wireless communication methods make collection from any location difficult, as transmissions adapt and adjust to the instantaneous link conditions, resulting in a lack of content due to unfavorable receiver locations. For example, the modulation method of 1024-quadrature amplitude modulation (QAM) is selected only when the device determines that the current link conditions to the receiving AP are good. Thus, receptions from less favorable locations are likely to go unreadable. For this reason, passive wireless sniffers are becoming less popular as modem technology advances. Passive sniffers are less reliable because the sniffer is removed from the active adaptation process. Diversity of receiver locations is a key factor for the collection of location-sensitive data, such as for triangulation purposes. Thus, passive wireless locating is an inherent challenge.
[0014] Solutions described below include, but are not limited to, reconstructing a mosaic of bits of information obtained from multiple receivers and associated access points into a cohesive location estimate. An object may be observed by multiple sensors in space-time on a single inertial coordinate system. A mosaic of individual sensor readings over time may reveal the object's location in a desired space-time coordinate system. Individual sensors are like keyholes, each of which can only see a portion of space. Effective observations may be achieved if different keyhole observations are fused into a complete picture of reality. Because observers are distributed in space-time, the observations do not synchronize well. Furthermore, different sensors have different capabilities. For example, a location receiver may be able to read the angle of arrival and register a timestamp event with a local clock, but not decode packet contents other than the PHY header. An associated access point may be able to decode packet contents including the PHY and MAC layers and register a timestamp event, but not necessarily read the angle of arrival. Reconstructing reality may be possible by stitching together the observations in some way. Both a temporal and a spatial perspective are necessary.
[0015] The disclosed embodiments can provide the ability to uniquely and globally label individual events recorded at different locations in space and time in time, for example, to build a global understanding of an event that is not possible with a single "keyhole" observer. Each event log is chronological, i.e., from a local perspective, the first is recorded in the same order as the second, etc. For example, a local supernova event using gamma ray sensors scattered around the world. The sensors may use autonomous clocks. When individual explosion events are identified at various sensor locations, such as NGC 2770 on February 2, 2015, the big picture reveals secrets that cannot be deciphered using individual measurements. For example, the location of a supernova in the sky can be extracted by triangulation (e.g., using the parallax effect) only if measurements of the same event are taken from different angles, spreading out the sensor locations and identifying the event (e.g., NGC 2770) in multiple distributed event logs.
[0016] Another analogy is to solve a crime using multiple event logs from different witnesses that are loosely synchronized in time: one witness hears two gunshots 3 seconds apart from his apartment, while another witness sees a flash walking down the street. Since the observers are in the same inertial coordinate system, the time difference between the two different events witnessed by the two observers will be approximately the same (same in the Newtonian world, time lag in the Einsteinian world). Thus, the following embodiments provide a system that reconstructs the mosaic based on information collected from the receivers to provide consistent location estimates.
[0017] In another example, a set of radio receivers analyzes individual packet transmissions at different locations. The transmitter location and identity can only be analyzed if this individual packet transmission is uniquely and globally tagged (e.g., as with NGC2770 in the previous example). In practice, more than a single antenna is required, as some sensors can extract the received angle of arrival but not the identity, other sensors can extract the transmitter identity, and still others (e.g., a single-antenna location receiver) can extract the time of arrival of an anonymous transmission but not the identity, nor the angle of arrival.
[0018] Mobile WiFi devices communicate with access points, and such WiFi devices associate with an access point that is a gateway to the Internet. A mobile device may only be associated with one access point at a time. When transmitting data packets, the mobile device rate-adapts its packet transmissions utilizing different modulation schemes such as quadrature phase shift keying (QPSK), 16 quadrature amplitude modulation (QAM) (or "16QAM"), and beam formats to ensure that the associated access point can receive these packets, especially those that contain the mobile device's media access control (MAC) address (including its identity). If the access point fails to receive a packet, it avoids acknowledging the packet and causes the mobile device to retransmit the packet. This mechanism is called automatic repeat request (ARQ), and such retransmissions ensure the reliability and complete transmission of the message. However, this mechanism is point-to-point by design between the mobile device and the associated access point. Receivers other than the associated access point may not be protected by the ARQ mechanism or may be off-beam. Additionally, other receivers may have too few antennas to decode the MIMO (Multiple Input Multiple Output) message and therefore may not receive the mobile MAC address due to errors (e.g., no transmission) or a rate that is too high for the receiver to receive given the particular link conditions. With the introduction of MIMO, the link conditions become more point-to-point in nature due to ARQ and rate adaptation. Similarly, data may be received under very specific multipath conditions that are very sensitive to the location of the transmitter, the receiver, and the reflectors illuminated by the transmitter or receiver. Thus, many location receivers may only receive the PHY header, which is robust by design, and not the transmitter address.
[0019] FIG. 1 is a schematic diagram of a system 100 for wireless communication and location detection, according to an embodiment of the present invention. As an example, FIG. 1 illustrates a typical environment, such as a shopping mall or a street, where multiple access points 122, 124, 126 (or transmitters 122, 124, 126) are deployed by different WLAN owners, often independently of each other. It is recognized that the number of access points 122, 124, 126 may vary or be fixed. The access points 122 may be defined as associated access points. An associated access point is an entity selected by a mobile device 128 that bridges all traffic with a distribution (or distribution) system ("DS") (i.e., the system 100). The associated access points 122 are configured to observe all information transmitted to the mobile device 128. The associated access points 122 are generally configured to provide information to at least one server 140 ("server 140"), passing beacon packets among other packets, as described below. Each of the access points 124 and 126 is generally defined as an unassociated access point and transmits or broadcasts a beacon. The access points 124 and 126 are not connected to the server 160 (i.e., the unassociated access points 124 and 126 cannot report to the server 140).
[0020] The signals transmitted by the access points 122, 124, 126 are received by receivers in the form of mobile devices 128, 130 operated by a user 132, who may be freely mobile within the area covered by the system 100. In the illustrated embodiment, the mobile devices 128, 130 are shown as mobile phones, but other types of mobile transceivers, such as laptops, tablet computers, wearable electronic devices (e.g., smart watches), Internet of Things (IoT) devices, etc., may be used in a similar manner. It will be appreciated that the number of mobile devices 128, 130 may also vary. It will also be appreciated that the mobile device 128 may correspond to a location tag 137, which includes a wireless transceiver and other electronic circuitry that is arranged for attachment to the object 129. For example, the object 129 may correspond to a woman's handbag (or purse), and the location tag 131 may provide information indicative of the location of the handbag 129. Each mobile device 128, 130 typically includes a MODEM or other device for enabling wireless communication with the various access points 122, 124, 126 in the environment.
[0021] It is recognized that the access points 122, 124, 126 and the mobile devices 128, 130 may also wirelessly communicate with any number of sensors (also "receivers" or "passive receivers" or "location receivers") 131a, 131b, etc. It is recognized that any number of sensors (or receivers) 131a, 131b may be provided. In one example, the sensors 131a, 131b may be fixed location sensors, such as proximity sensors, geofencing sensors, etc., that are placed throughout one or more floors of a building to detect the presence of a user 132. Generally speaking, the sensors 131a, 131b may be fixed and programmed to receive beacons and other information from the access points 122, 124, 126, as well as data packets from the mobile devices 128, 130. This aspect is described in more detail below. The sensors 131a, 131b may also transmit information to at least one server 140. In one example, the sensors 131a, 131b may transmit angle of arrival measurements to the server 140 for purposes of determining the position of at least the mobile devices 128, 130. This aspect is described in further detail below.
[0022] The location receivers 131a, 131b, etc. can determine the angle of arrival of signals transmitted from the mobile devices 128, 130. Each of the location receivers 131a, 131b, etc. in the system 100 is assumed to have two or three antennas 135, for example, as shown in FIG. 1. The number of antennas 135 may vary in the system 100. The mobile devices 128, 130 are each assumed to have a single omni-directional antenna 136, although the techniques described herein for finding angles may be implemented by multi-antenna stations as well.
[0023] The server 140 includes a programmable processor 142 and a memory 144. The functionality of the server 140 described herein is typically implemented in software running on the processor 142, which may be stored on a tangible, non-transitory computer readable medium, such as an optical, magnetic, or electronic memory medium. As noted herein, there are inherent problems in piecing together the identities of mobile devices 128, 130 transmitting information to associated access points 122 and various receivers 131 in a network. Figure 2 provides a graphical representation of such a challenge.
[0024] For example, FIG. 2 generally illustrates transmitters 128a, 128b, 128c (or mobile devices 128a, 128b, 128c) transmitting packets (e.g., WiFi-based packets) to associated access points 122 and sensors 131a, 131b (hereinafter, “receivers 131a, 131b”). For example, transmitter 128a may transmit packets 1 and 5, transmitter 128b may transmit packets 3 and 7, and transmitter 128c may transmit packet 4. It will be appreciated that access point 126 (e.g., access point 126, although the beacons used for time differences may or may not be associated with associated access point 122) periodically transmits beacons 150a, 150b (as packets 2, 6) at a predetermined rate (e.g., approximately every 102.4 ms) that conforms to 802.11n (e.g., a WIFI-based standard). Similarly, receivers 131a, 131b are intended to receive beacons 150a, 150b (or packets 2, 6). However, as shown, receiver 131b does not detect beacon 150a (e.g., as also shown in FIG. 2 as packet 2 (but not a data packet)), but does detect beacon 150b (or packet 6 (but not a data packet)).
[0025] 2, access point 126 is behind receiver 131a in time and ahead of receiver 131b in time. Also, as shown in the example, receiver 131a does not detect packets 3 and 7, and receiver 131b does not detect packet 2. As noted above, transmitter 128a transmits packets 1 and 5. Thus, the angle of arrival (AoA) measurements detected by receiver 131a for packets 1 and 5 are approximately the same (e.g., 100 degrees). The angle of arrival generally indicates the location of transmitter 128a, which is constrained to a known line on a plane.
[0026] Receiver 131b also receives packets 1 and 5 from transmitter 128a, and the AoA measurement detected by receiver 131b is approximately, for example, 220 degrees. Because receivers 131a and 131b are positioned at different angles relative to transmitter 128a, the AoA measurements of receiver 131b associated with packets 1 and 5 differ from the AoA measurements of receiver 131a (see FIG. 3). Assuming that receivers 131a, 131b and transmitter 128a were orthogonal and that transmitter 128a was not in the center, the AoA measurements of each of receivers 131a, 131b would have been approximately the same.
[0027] It is recognized that data packets or (WiFi packets) (e.g., packets 1, 3, 4, 5, and 7) generally do not provide the identity to the location receiver 131a, 131b of the transmitter 128a, 128b, 128c transmitting such packets for the reasons explained above. WiFi packets generally consist of a physical header (e.g., PHY), followed by a medium access control (MAC) header, followed by a payload. Although the identity of the transmitter 128a, 128b, 128c may be encoded into every data packet, not every receiver 131a, 131b is able to decode that part of the message in the data packet. Generally, data packets or messages include a physical "PHY" header portion that is encoded with a simple / robust modulation scheme. This portion is designed to be recognizable even under extreme link conditions. The PHY header does not include the identity of the transmitter 128a, 128b, 128c. The identity of the transmitter 128a, 128b, 128c may be part of the MAC header transmitted after the PHY header. The unique access point 122 with which a mobile device 128a, 128b is associated can ensure that such mobile device 128a, 128b decodes all packets that it bridges between a wireless network, such as a Basic Service Set (BSS), and a distribution system ("DS") of a wired network. The ARQ retry mechanism defined in the 802.11 MAC protocol, in which the access point 122 plays an active role, can ensure reliable transmission of the entire message to the access point 122 protected by the Frame Check Sequence ("FCS").
[0028] Also note that data packets 1, 3, 4, 5, 7 do not have a unique explicit sequence. The PHY headers of the data packets (e.g., packets 1, 3, 4, 5, 7) are not unique because many packets have the same PHY header. In contrast, complete data packets are very likely to be unique, especially if encrypted. The complete contents of a packet may be available to the associated access point 122 but not to the receivers 131a, 131b.
[0029] 2 conveys that, in general, the identities of transmitters 128a, 128b, 128c cannot be discerned by the individual location receivers 131a, 131b. Such lack of necessary discrimination can adversely affect the location estimates of transmitters 128a, 128b, 128c. For example, receiver 131a may read AoA measurements from transmitter 128a and receiver 131b may read AoA measurements from transmitter 128b, and the resulting mosaic will be a stark outlier if it is erroneously assumed that the transmitters originate from the same location.
[0030] In a typical wireless protocol such as IEEE 802.11 (e.g., the WIFI standard), the modulation scheme is adaptively set to optimize the data rate taking into account the link conditions. However, other receivers 131a, 131b may experience different and worse link conditions, which prevents reliable reception of the data. As mentioned above, WiFi packets transmitted by the access points 122, 124, 126 and the mobile devices 128a, 128b, 128c, etc., generally include a PHY header followed by a (MAC) header, which is then followed by the payload. The packet PHY header may be designed to be robust to avoid collisions of media packets, for example as part of the protocol's elaborate "collision avoidance" mechanism. And the packet PHY header is designed to withstand the most extreme link conditions, avoiding the well-known "hidden node syndrome" where a transmitter 128a, 128b, 128c is useless to the receiver 131a, 131b, but prevents the receiver 131a, 131b from receiving packets from a closer transmitter 128a, 128b, 128c. In general, only the PHY header, for example, is needed for each receiver 131a, 131b to extract the direction of arrival ("DoA"), and thus such a sensor (or receiver 131a, 131b) provides an AoA measurement but not the identity of the transmitter 128a, 128b, 128c. The physical header PHY provides an accurate estimate of the reception epoch (e.g., the time the packet arrived) sampled by the receiver 131a, 131b's local clock. However, local clocks at different sensor (or receiver 131a, 131b) locations are offset and also experience slight drift due to crystal oscillator tolerances, typically up to 100 parts per million (ppm), up to 1 second every 2.78 hours. Furthermore, in IEEE 802.11 "wireless LANs," for example, and as discussed above, beacons 150a, 150b are transmitted approximately every 102.4 milliseconds by access points 124, which are typically stationary.The access points 122, 124, 126 transmit the beacons 150a, 150b to any potential receiver (e.g., mobile devices 128a, 128b, 128c or receivers 131a, 131b), and thus the beacons 150 are not rate adaptive, beamformed, or MIMO encoded. Rather, the beacons 150 are CDD encoded, which facilitates AoA techniques. Nearly all receivers 131a, 131b and mobile devices 128, 130 can reliably receive the beacons 150, including the MAC layer contents. In general, the MAC layer of a beacon packet consists of an identifiable transmitter timestamp. The MAC layer of the beacons 150a, 150b includes the source MAC address of the access point 122, plus a transmitter timestamp that is globally unique in space and time, such as the NGC2270 example mentioned above. In general, beacon transmissions are like supernova events that are visible around the world and can be distinguished from one another.
[0031] The mobile devices 128, 130 (or transmitters 128a, 128b, 128c) transmit DATA packets of a type that is not necessarily unique and uses high-speed modulation schemes that allow beamforming and MIMO encoding, so that they may not be read by receivers 131a, 131b located in most locations in space. However, the receivers 131a, 131b are able to receive beacons 150 from access points 122, 124, 126 that are unique in time and space using the stationary receiver's location and a monotonic local clock over its lifetime to timestamp received packets. By measuring the time difference between (i) beacon 150 events, along with MAC address and transmitter timestamp, and (ii) data packet events, consisting of AoA and local receiver timestamp, receivers 131a, 131b can report those measurements in an invariant form so that the location of each individual transmitter 128a, 128b, 128c can be estimated at a central location (e.g., server 140) by collecting data from multiple receivers 131a, 131b on the reporting network. In general, receivers 131a, 131b utilize the beacons 150 transmitted by access points 122, 124, 126 as a time synchronization mechanism for the data packets transmitted by transmitters 128a, 128b, 128c immediately prior to the transmission of the beacons 150a, 150b. This differential reporting is less susceptible to network delays and jitter experienced between the location receivers and the server.
[0032] Each receiver 131a, 131b may provide an individual report consisting of the packet identification information of the beacon 150, the reception epoch of the packet transmitted by the access points 122, 124, 126, and also location information derived from the physical headers of the data packets from the transmitters 128a, 128b, 128c (e.g., angle of arrival, time of arrival, etc.). The server 140 may then coalesce all measurements of data packets that have nearly identical time differences relative to a globally unique beacon event to provide a list of mobile packet transmission events that are specific in time with respect to the location of the transmitters 128a, 128b, 128c and the receivers 131a, 131b, such that an observation can be made at any single point in time. To obtain greater accuracy, clock drift between the receivers 131a, 131b may be mitigated by reporting the time differences between beacon packets from the access points 122 or 124 or 126 from receivers at different known locations.
[0033] FIG 4 illustrates a method 200 for locating a transmitter 122, 124, 126 (or a mobile device 128, 130) performed by the system 100 according to one embodiment. In general, the disclosure with reference to FIGs 2-4 generally corresponds to the case where an access point 122, 124, 126 transmits a beacon to a mobile device (or a transmitter 128a, 128b, 128c) whereby no acknowledgement may be sent back to the access point 122, 124, 126 in response to such a beacon. Similarly, FIGs 2-4 also correspond to the case where an access point 122, 124, 126 receives an acknowledgement from the mobile device 128a, 128b, 128c in response to a data packet previously transmitted from the access point 124, 126, 128 to the mobile device 128a, 128b, 128c. In this case, however, a scheme such as that disclosed in connection with FIG. 6 may have to be implemented to take into account the acknowledgements sent from the mobile devices 128a, 128b, 128c back to the access points 122, 124, 126.
[0034] In operation 202, a corresponding transmitter (or access point) 122, 124, or 126 broadcasts a beacon 150 including a physical ("PHY") header followed by a source MAC header and data to corresponding receivers 131a, 131b in the network. It is recognized that the PHY header, MAC header, and data are all provided in a WiFi-based packet. The transmitter 122, 124, or 126 transmits a transmitter timestamp to the receiver 131a, 131b.
[0035] In operation 204, the receivers 131a, 131b receive the beacons 150 together with the transmitter timestamps from the corresponding transmitters 122, 124, 126. The receiver 131 generally determines the time at which the packets of the beacon 150 arrive as sampled by its local clock, providing a receiver timestamp. In general, the beacon(s) 150 may be used as a time encoder. Data events (or data packets) from the transmitters (or mobile devices) 128a, 128b, 128c are reported with reference to a unique beacon 150. For example, a data packet may be transmitted by the mobile device 128a, 128b, 128c either immediately before or immediately after the beacon 150 is transmitted by the access point 122, 124, 126. Thus, at this point, the time difference between the data packets and the individual beacons 150 may be known.
[0036] In operation 208, the receiver 131 extracts a transmitter timestamp of the beacon 150 of the corresponding access point 122, 124, 126. In addition, the receiver 131 also determines a source MAC address indicating the identity of the corresponding access point 122, 124, 126. Typically, the source MAC address is included in the MAC layer of the beacon 150 transmitted by the corresponding access point 122, 124, 126. The transmitter timestamp and the MAC address of the corresponding access point 122, 124, 126 are globally unique in space and time. The beacon transmissions may be seen by receivers within the service area, and each beacon transmission is distinguishable from one another.
[0037] In operation 209, the receiver 131 receives data packets from the transmitters 128a, 128b, 128c.
[0038] In operation 210, the receivers 131a, 131b and associated access points 122 generate individual reports that include reference beacon packet information (e.g., transmitter timestamp and MAC address), the time difference between the reception epoch of the beacon 150 and the reception epoch of the cellular data packet (e.g., a packet transmitted by a transmitter 128a, 128b, 128c (or a cellular device)) (e.g., a relative time measurement between when the beacon 150 is received at the receiver 131 and when the data packet is received at the receiver 131), and location information obtained from the AoA via information in the PHY layer (or physical header) of the data packet received by the location receivers 131a, 131b. The report generated by the associated access point consists of the data packet MAC layer transmission address (unique identity), but not necessarily the AoA information. The server 140 can determine the identities of the transmitters 128a, 128b, 128c by locating the same time difference (within a predefined error range) between the same received beacon 150 and the received data packed for the receivers 131a, 131b in the location receiver report and the associated access point report.
[0039] The time difference between the reception epoch of the beacon 150 and the reception epoch of the packet from the transmitter 128a, 128b, 128c (or mobile device) can be described as follows: For example, the beacon 150 (or beacon packet) transmitted by the access points 122, 124, 126 and the data packet transmitted by the transmitter (or mobile device) 128a, 128b, 128c are transmitted one after the other by the transmitters 128a, 128b, 128c without overlap, the former finishing before the latter starts. The exact time when either packet "starts" at the receiver 131 is well defined by the WiFi standard to an accuracy of better than 1 microsecond. For example, the beacon start (epoch) arrives at 1.111111 seconds local time at the receiver 131a, 131b, and the data packet arrives at 1.111999 seconds at the receiver 131a, 131b, so the calculated difference is 0.000888 seconds or 888 microseconds.
[0040] In operation 212, each receiver 131 delivers (or transmits) a report to the server 140. The associated access points also deliver their reports to the server 140. The server 140 then combines all measurements of data packets with approximately the same time difference for a globally unique beacon event, where observations of a single event in time from different known locations can be observed. This can be done in the following way. For example, the server 140 has been reported by the corresponding receivers 131a, 131b, 131c that a beacon 150 with a transmitter timestamp of 111,222,333 microseconds (conventionally measured since the access point recently booted, a little over 111 seconds in this example) was received by the receivers 131a, 131b, 131c. Also, all three receivers 131a, 131b, or 131c received a data packet from the corresponding transmitter 128 after 344, 346, and 347 microseconds, respectively. Each receiver 131a, 131b, or 131c measures the time difference using its local clock. The server 140 determines that all three packet events originate from the same data packet transmission event originating from a single specific portable transmitter 128a, 128b, or 128c because the timing error is less than or equal to a predetermined error. In other words, the server 140 determines that each receiver 131a, 131b, or 131c received a beacon 150 with a transmitter timestamp of 111222333, and because all three receivers 131a, 131b, or 131c received data packets from the transmitter 128 at approximately the same time relative to the transmitter timestamp, the identity of the transmitter 128, e.g., receiver 131c, is the associated access point, and the report consists of the identity of the portable transmitter decoded by the associated access point from the MAC layer of the transmitted data packet.
[0041] In operation 214, the server 140 determines the location of the transmitter 128 (once identified in operation 212) by utilizing triangulation. The server 140 performs triangulation on the identified transmitter 128 based on the AoA reading of the receiver 131a, e.g., 100 degrees, and based on the AoA reading of the receiver 131b, e.g., 220 degrees (see FIG. 3). Triangulation requires three or more AoA measurements, one for each location receiver, to evaluate the estimation error. An example of an embodiment in which triangulation based on AoA measurements may be employed to determine the location of the transmitter 128 may be disclosed in “Providing Localization using Triangulation Method in Wireless Sensor Network”, International Journal of Innovative Technology and Exploring Engineering (IJITEE) ISSN: 2278-3075, Volume-4 Issue 6, November 2014, Leelavathy SR and Sophia S.
[0042] Another example of performing triangulation is shown below with reference to FIG. 2. Receiver 131b reports receipt of beacon 150b (e.g., 6), data packets 1, 3, 4, 5, and 7, and receiver 131a reports receipt of beacons 150a and 150b (e.g., 2 and 6) and data packets 1, 4, and 5, along with the transmitter timestamps in the beacons, etc. Data packets 1, 4, and 5 cannot be decoded by location receiver 131, only the associated access point 122, but location receiver 131a can estimate their AoA measurements as 100 degrees, 140 degrees, and 100 degrees, respectively. Server 140 provides an inference that the packet representing (4) reported by receiver 131a (4) and the packet representing (4) reported by receiver 131b (4) are also reported by associated access point 122 as packet 4 in FIG. 2. The time difference between packet 4 and beacon 6 (or beacon 150b) is nearly identical between the events reported by receiver 131a, receiver 131b and associated access point 122 for beacon 150b, within a given reception time error range (e.g., 10 μs, see events #12-24 in table 500 of FIG. 10). At this point, packet 5 is known to have an AoA measurement of 100 degrees as seen by receiver 131a, and the identity of transmitter 128a as decoded by associated access point 122 (see also below). Once at least three AoA measurements from the receivers for one particular packet (e.g., packet 5) in the above example have been identified, the location of transmitter 128a may be estimated by drawing three lines, one for each receiver 131a, that intersect the known location of receiver 131a in receiver 131a's estimated AoA direction of 100 degrees (e.g., 99.9, see FIG. 3). The three lines constitute a triangle (FIG. 3 only depicts two lines for simplicity) in which transmitter 128a is trapped by this estimation procedure. Returning to FIG. 2, only two receivers 131a, 131b are shown, but a third receiver may be required for actual triangulation. Although not shown in FIG. 3, at least three receivers are required for triangulation.
[0043] FIG. 5 generally corresponds to a more detailed method 250 performed by the system 100 for determining the location of a transmitter 122, 124, 126 (or a mobile device 128, 130) according to one embodiment.
[0044] In operation 252, the server 140 receives first information from the associated access point 122 indicating (i) a first receiver timestamp indicating that the associated access point 122 has received a first data packet from the mobile device 128, and (ii) a second receiver timestamp indicating that the associated access point 122 has received a second (beacon) packet from the access point 124 (i.e., the non-associated access point 124).
[0045] In operation 254, the server 140 determines a first difference between the first receiver timestamp and the second receiver timestamp to generate a first difference value.
[0046] In operation 256, the server 140 receives second information from the first location receiver 131a indicating (i) a third receiver timestamp 131b at which the first location receiver 131b received a third data packet from the mobile device 128, and (ii) a fourth receiver timestamp at which the first location receiver 131a received a second (beacon) packet from the access point 124.
[0047] In operation 258, the server 140 determines a second difference between the third receiver timestamp and the fourth receiver timestamp to generate a second difference value.
[0048] In operation 260, the server 140 compares each of the first and second difference values to a predetermined reception time error range.
[0049] In operation 262, the server 140 determines that the first packet and the third packet transmitted by the portable device 128 are identical in response to each of the first difference value and the second difference value being within a predetermined reception time error range.
[0050] In operation 264, the server 140 performs operations 252, 254, 256, 258, 260, and 262 again, but utilizing the second location receiver 131b instead of the first location receiver 131. For example, the server 140 performs the following in relation to the second location receiver 131b: The server 140 receives third information from the second location receiver 131b indicating (i) a fifth receiver timestamp at which the second location receiver 131b received a fourth packet from the mobile device 128, and (ii) a sixth receiver timestamp at which the second location receiver 128 received a second packet from the access point 124. The server 140 determines a third difference between the fifth receiver timestamp and the sixth receiver timestamp to generate a third difference value.
[0051] Then, the server 140 compares each of the first and third difference values with a predetermined reception time error range, and determines that the first packet and the fourth packet transmitted by the mobile device 128 are identical in accordance with the first and third difference values being within the predetermined reception time error range. The server 140 then obtains AoA information from the first location receiver 131a and the second location receiver 131b, the AoA information indicating the direction of the mobile device 128 relative to the orientations of the first location receiver 131a and the second location receiver 131b. In operation 266, the server 140 determines the location of the mobile device 128 based on at least the AoA information received from the first location receiver 131a and the second location receiver 131b.
[0052] 6 is a scheme 300 illustrating identifying an access point 122 based on a coalesced immediate acknowledgement packet event performed by the system 100 according to one embodiment. The scheme 300 may be employed when the mobile device (or transmitter 128) sends an acknowledgement packet (or acknowledgement) back to the access point 122 in response to receiving a data packet 128c from the access point 122. In some cases, the transmitters 128a, 128b, 128c may send an acknowledgement back to the associated access point 126, for example. In other cases, the transmitters 128a, 128b, 128c may not send an acknowledgement back to the associated access point 126, for example. If the case is the latter, the actions are taken as defined below. It is recognized that the method 200 provides an aspect in which identity readings at the associated access points 122, 124, 126 may be used to identify the location of the transmitters 128a, 128b, 128c at the receivers 131a, 131b (e.g., by combining two receiver readings of the same event). However, the scheme 300 also employed by the system 100 may identify the transmitters 128a, 128b, 128c by combining two events into one at the access points 122, 124, 126 via the server 140. For example, WiFi protocols (e.g., IEEE 802.11) rely on a mechanism called immediate acknowledgement, in which the access point 122a sends a packet to the mobile device 128b. In this case, the mobile device 128b immediately sends an acknowledgement packet (or ACK packet) 302 back to the access point 122 to acknowledge receipt of the data packet from the access point 122. However, in accordance with IEEE 802.11, the ACK packet sent back to access point 128b does not have the identity of transmitter 128b embedded in it, only the identity of access point 128. It is possible to implicitly reveal the identity of transmitter 128b by observing the MAC header 304 in the data packet transmitted immediately before the ACK packet is received.For example, the MAC header 304 includes a recipient address (RA) field 306. Thus, in response to receiving the ACK packet 302 from the transmitter 128b, the server 140 can check the contents of the RA field 306 in the MAC header 304 to determine which transmitter 128 transmitted the ACK packet 302. In the scheme 300 shown in FIG. 6, the RA field 306 is set to transmitter 128b (or T2), in which case the server 140 determines that transmitter 128b transmitted the ACK packet 302.
[0053] FIG. 6 also shows that the receivers 131a, 131b receive data packets (e.g., DATA) from the access point 122 and ACK packets from the transmitter 128b. The receivers 131a, 131b receive the ACK from the transmitter (or mobile device 128b). The receivers 131a, 131b also measure AoA measurements from the transmitter 128b (e.g., receiver 131a's AoA measurement is 100 degrees and receiver 131b's AoA measurement is 220 degrees). FIG. 6 illustrates that while the receivers 131a, 131b receive data packets and acknowledgment packets, the contents of the data packets at the MAC layer are not known or provided as discussed above. It is also recognized that the receivers 131a, 131b also receive beacons 150 from the access point 122 that include the transmitter timestamps of the access points 122, 124. As mentioned above, the transmitter timestamp indicates the time when the access point 122 transmitted the beacon 150 to the receiver 131a, 131b. Similarly, the receiver 131a, 131b receives the time-stamped transmitter acknowledgement transmitted by the transmitter 128a (i.e., the mobile device 128a). Thus, in this regard, the receiver 131a generates timestamps for both the access points 122a, 122b and the mobile devices 128a, 128b. There can be two types of timestamps. For example, a first type of timestamp (or transmitter timestamp) may be embedded in the beacon packet by the access points 122, 124, and a second type of timestamp (or receiver timestamp) is a timestamp taken by the receiver 131 when the beacon 150 or data or acknowledgement is received. Thus, the beacon packet includes both a transmitter timestamp (e.g., a timestamp from the access point 122) and a receiver timestamp (e.g., a timestamp at the receiver 131). Thus, the receiver 131 determines the time difference between the timestamp of the beacon 150 received at the receiver 131 and the timestamp of the data packet (or acknowledgment) to report to the server 140 .The transmitter timestamp (e.g., a timestamp embedded in a beacon 150 transmitted by the access point 122) is used to enable individual beacons 150 to be identified among multiple receivers 131a, 131b (e.g., time difference reporting by receivers 131a, 131b for beacons with embedded transmitter timestamps associated with the same beacon transmission event).
[0054] As described above, the server 140 can determine the identity of the transmitter 128 based on verifying the contents of the RA field 306 after receiving an acknowledgement from the transmitter 128. The server 140 also receives transmitter timestamps from the receivers 131a, 131b from the access point 122 (e.g., via the beacon 150) and from the mobile device 128 (e.g., via the acknowledgement) to determine when the identified transmitter 128 transmitted information based on multiple receptions of the beacon 150. Based on the identity of the transmitter 128 and the transmitter timestamps, the server 140 can determine or identify different receptions for individual transmissions. The receivers 131a, 131b can then report the AoA measurements they measured to the server 140. The server 140 can determine the location of a single transmitter 128 (e.g., a mobile device) based on the identity of the transmitter 128 and two or more AoA measurements.
[0055] FIG. 7 is a method 400 for determining a receiver's position based on the scheme 300 of FIG. 6, according to one embodiment.
[0056] In operation 402, the server 140 determines the identity of the transmitter (i.e., mobile device) 128 based on receipt of the acknowledgement, as described in connection with the scheme 200 of FIG. 5. As described above, the access points 122, 124, 126 receive an acknowledgement packet (or acknowledgement) 302 from the transmitter 128a or 128b or 128c to acknowledge receipt of the data packet from the access points 122, 124, 126. The access points 122, 124, 126 transmit information corresponding to a MAC header 304, including an RA field 306, to the server 140. The server 140 can observe the contents of the MAC header 304 (e.g., the contents of the RA field 306) to determine which transmitter 128 transmitted the acknowledgement packet 302. It will be appreciated that the access points 122 , 124 , 126 may transmit information corresponding to the MAC header 304 , including the RA field 306 and the acknowledgement packet 302 , to the server 140 to enable the server 140 to determine the identity of the transmitter 128 .
[0057] In operation 404, the receiver 131 receives the beacons 150 from the access points 122, 124, 126 along with the transmitter timestamps.
[0058] In operation 406, the receiver 131 also receives the AoA measurement and acknowledgement packet 302 from the transmitter 128. The receiver 131 determines the time that the packet arrives on the beacon 150, as sampled by its local clock, to provide a receiver timestamp.
[0059] In operation 408, the server 140 aggregates the location receiver reports of transmitter timestamps and MAC addresses transmitted by the access point 122 (e.g., via the beacon 150) and packet receiver timestamps + AoA measurements from the receivers 131a, 131b to report a set of relatively received timestamps and AoA measurements. The timestamps are relative to the beacon 150. The following example illustrates how an identified mobile device (or transmitter) transmits an acknowledgement and the receivers 131a, 131b receive the acknowledgement at approximately a single point in time (approximately due to, for example, slightly different propagation delays within an acceptable margin of error). Referring to FIG. 2 (see also event number 21 (see 502) in TABLE 500), data packet 4 details the transmitter 128c and the receiver address of transmitter 128a. The next packet in time received by the associated access point 122 consists only of the receiver address starting with transmitter 128c as the receiver, according to IEEE 802.11. The server 140 may optionally annotate this data packet as packet #5. The server 140 may need to uncover the mobile identity packet #5 originating from the mobile device. Packet #5 indicates that it is destined for transmitter 128c. The server 140 may look back one packet in time to the packet annotated as #4, which confirms that it was sent by transmitter 128c. Packet #4 declares that it is destined for transmitter 128a, and therefore, by inference, packet #5 originated from the mobile transmitter 128a. The server 140 likely needs to look back one packet in time, here to the packet annotated as packet #4. In such an inference scenario, the acknowledgement packet #5 is sent immediately after packet #4 in response to packet #4. It is recognized that the acknowledgement packet does not report the identity of the sender (or transmitter 128a, 128b, 128c), but rather the identity of the intended recipient of the acknowledgement.The identity of the sender is revealed by inference from a previous packet (eg, annotated data packet #4 sent to transmitter 128a).
[0060] In operation 410, the server 140 incorporates measurements of the same relative timestamp with a particular beacon report, specifically the transmitter timestamp and the transmitter MAC address. The location receiver provides the AoA measurements, and the associated access point provides the identity of the transmitter 128 (e.g., a mobile device). Figure 7, described below, provides more details with respect to operation 410 (and operation 212 described with respect to Figure 4).
[0061] In operation 412, server 140 performs triangulation to determine the location of transmitter 128. As described above, triangulation may be performed as follows: Receiver 131b reports receipt of packet 5. Receiver 131a reports receipt of packet 5. Given the AoA measurements from three known location receivers of the same packet transmission event, and the identity of the transmitter characterized by a unique MAC address, server 140 triangulates a line that intersects the known locations of the receivers depicted in FIG. 3 with the measured AoA that the receivers were individually reading, into the triangle where transmitter 128 is estimated to be located.
[0062] Figure 8 is another method 420 for determining a receiver's position based on the scheme of Figure 5, according to one embodiment. Operations 422, 424, 426, 428, 430, and 438 are similar to operations 202, 204, 208, 209, 210, 212, and 214, respectively, defined in Figure 4. As such, these operations will not be described below. Operations 434 and 436 are unique to method 420.
[0063] In operation 434, the associated access point 122 reports the destination ("DST") address of the data packet immediately preceding the ACK packet.
[0064] In operation 436 , the server 140 infers the address identity of the mobile device 128 from the previous DST address in the ACK packet reported by the associated access point 122 .
[0065] FIG. 9 illustrates a more detailed method 450 for determining the location of the mobile device 128 of the method 300 of FIG. 6 and the system 100 of FIG. 1, according to one embodiment.
[0066] In operation 452, the server 140 receives first information from the associated access point 122 corresponding to an acknowledgement packet 302 received from the mobile device 128. The acknowledgement packet 302 is transmitted by the mobile device 128 in response to a data packet transmitted by the associated access point 122, the first information further corresponding to a receiver address field 306 in the data packet providing an identification of the mobile device 128 for the associated access point 122 to transmit the data packet thereto.
[0067] In operation 454 , the server 140 accesses the receiver address field 306 to determine the identity of the mobile device 128 when the acknowledgement packet 302 is received from the mobile device 128 at the associated access point 122 .
[0068] In operation 456, the server 140 receives first information from the associated access point 122 indicating (i) a first receiver timestamp at which the associated access point 122 received a first packet from the mobile device 128, and (ii) a second receiver timestamp at which the associated access point 122 received a second beacon packet from the access point 124 (i.e., the non-associated access point 124).
[0069] In operation 458, the server 140 determines a first difference between the first receiver timestamp and the second receiver timestamp to generate a first difference value.
[0070] In operation 460, the server 140 receives second information from the first location receiver 131a indicating (i) a third receiver timestamp 131b indicating that the first location receiver 131b has received a third packet from the mobile device 128, and (ii) a fourth receiver timestamp indicating that the first location receiver 131a has received a second packet from the access point 124.
[0071] In operation 462, the server 140 determines a second difference between the third receiver timestamp and the fourth receiver timestamp to generate a second difference value.
[0072] In operation 464, the server 140 compares the first difference value with the second difference value to ensure that a predetermined reception time error range is satisfied.
[0073] In operation 466, server 140 determines that the first and third packets transmitted by mobile device 128 are identical in response to each of the first and second difference values being within a predetermined reception time error range. The packets received by the associated access point reveal the MAC address identity of 128. The packets received by the location server provide the information necessary for triangulation of 128.
[0074] In operation 468, the server 140 performs operations 456, 458, 460, 462, 464, and 468 again, but utilizing the second location receiver 131b instead of the first location receiver 131. For example, the server 140 performs the following in relation to the second location receiver 131b: The server 140 receives third information from the second location receiver 131b indicating (i) a fifth receiver timestamp at which the second location receiver 131b received a fourth packet from the mobile device 128, and (ii) a sixth receiver timestamp at which the second location receiver 128 received a second packet from the access point 124. The server 140 determines a third difference between the fifth receiver timestamp and the sixth receiver timestamp to generate a third difference value.
[0075] Then, the server 140 compares each of the first and third difference values with a predetermined reception time error range, and determines that the first and fourth packets transmitted by the mobile device 128 are identical to each other if the first and third difference values are within the predetermined reception time error range. The server 140 then obtains AoA information from the first location receiver 131a and the second location receiver 131b, the AoA information indicating the direction of the mobile device 128 relative to the orientation of the first location receiver 131a and the second location receiver 131b. In operation 470, the server 140 determines the location of the mobile device 128 based on at least the AoA information received from the first location receiver 131a and the second location receiver 131b.
[0076] FIG. 10 illustrates an example of a table 500 that may be used by the server 140. The table 500 combines the identity of the mobile device 128 and the AoA measurements transmitted by the mobile device 128 based on at least a transmitter timestamp from the access point 122, 124 beacon, a receiver timestamp of the mobile device 128a, 128b data packet, and a receiver timestamp from the receiver 131a, 131b receiving the beacon from the access point 122, 124 to determine the identity of the mobile data packet AoA measurement, according to one embodiment. In column 502, various event numbers are depicted that correspond to various transmission events. In column 504, an enumeration of receivers, or generally devices that are receiving the beacon 150, data packet, or acknowledgement, is depicted. In column 504, an associated access point 122 may receive the data packet or acknowledgement, and this condition applies to any of the embodiments defined herein. As noted throughout this disclosure, any one of the receivers 131a, 131b, 131c and associated access points 122 may receive the beacon 150, data packets, and / or acknowledgments. For example, as shown in table 500, the events are numbered 12 through 24, and it should be recognized that events prior to events 12 through 24 also occur and events after event number 24 also occur.
[0077] Column 506 generally represents timestamps embedded in the beacon 150 by a transmitting device (e.g., a transmitter identified in column 514). Column 508 generally represents timestamps generated by a receiving device (e.g., receivers 131a, 131b, 131c, and associated access points 122) in response to receiving either a beacon 150, a data packet, or an acknowledgment. As discussed above, the receiver timestamps are generated based on internal clocks present in the receivers 131a, 131b, 131c, and associated access points 122 in response to receiving the beacon 150, a data packet, or an acknowledgment.
[0078] Column 510 generally corresponds to the AoA measurements of packets of a transmitter (e.g., mobile device 128) received and estimated by location receiver 131. Column 512 generally corresponds to the center annotation of a received packet event reported by receivers 131a, 131b and associated access points. Each packet is uniquely annotated as described in 410. All reports of an individual event are annotated the same. For example, with reference to FIG. 2, the fifth packet of associated access point 122, the fourth packet of the report from receiver 131a, and the fourth packet of the report from receiver 131b are all associated with the same event, which server 140 annotates as packet #5. This annotated event originates from transmitter 128a, reads an AoA measurement of 100 degrees from receiver 131a, and reads an AoA measurement of 220 degrees from receiver 131b. The numerals 1, 3, 4, 5 and 7 correspond to data or acknowledgement packets, while the numerals 2 and 6 correspond to beacons 150a, 150b. Column 514 generally corresponds to the unique identity of the transmitting device transmitting the beacon 150, data packet or acknowledgement. In this case, the transmitting device could be associated access point 122 and non-associated access point 124 or mobile device 128.
[0079] 2 and 10, access point 122 (event #23) reports receiving a data packet (e.g., data packet #5) from transmitter 128a at a local time (or receiver timestamp) of 3,980.03 μsec, and then receives a beacon 150b (e.g., beacon #6) from another access point 124 with an embedded transmitter timestamp of 1,000,000 microseconds at a local time (or receiver timestamp) of 4000.04 μsec (see event #17).
[0080] Similarly, receiver 131a reports receiving a data packet (e.g., data packet #5) from transmitter 128a at a local time of 14,000.01 μsec with an AoA measurement of 99.9 degrees (see event #24), and then reports receiving beacon packet 150b with an embedded transmitter timestamp of 1,000,000 μsec at a local time (or receiver timestamp) of 14,020.10 μsec (see event #18). In this example, the time difference between receiver 131a's receiver timestamp when beacon 150 arrives (e.g., 14,020.01 μsec) and receiver 131a's receiver timestamp when the data packet arrives (e.g., 14,000.10 μsec) is equal to 19.91 μsec.
[0081] Further, receiver 131b reports receiving a data packet (e.g., data packet #5) from transmitter 128a at a local time (or receiver timestamp) of 11,000.05 μsec with an AoA measurement of 219.9 degrees (see event #22), and subsequently beacon packet 150b (e.g., beacon #6) is embedded with a transmitter timestamp of 1,000,000 μsec at a local time (or receiver timestamp) of 11,019.85 μsec (see event #19). In this example, the time difference between receiver 131b's receiver timestamp when beacon 150 arrives (e.g., 11,019.85 μsec) and receiver 131a's receiver timestamp when the data packet arrives (e.g., 11,000.05 μsec) is equal to 19.8 μsec.
[0082] For packet identification by time difference, the receiver 131, also called MODEM, provides a resolution of 16 samples (or more) at 20 MHz (i.e., 16*50nsec = 0.8 μs, with a difference error of less than 2x (i.e., 1.6 μs)). The difference in the propagation path between the transmitter 128 and the receivers 131 amounts to 333 m / μs. In a typical environment, the error is limited to 0.5 μs, since the length is limited to 100 m on a side. At the medium access layer, packets are separated from the end of one packet to the beginning of the next packet by at least 10 μs. Typically, the end of a packet is separated from the beginning of the next packet by the length of the shortest packet plus the gap between packets, which is at least 26 μs, very commonly 100 to 400 μs. Thus, an error of 2.1 to 26 μs safely takes into account the inherent uncertainty while still guaranteeing accurate identification between adjacent packets. From the above, a margin of, for example, 100 μs may serve as a predetermined reception time interval for time differences to be considered equal to each other.
[0083] As can be seen, the time difference of receiver 131a (e.g., 19.91 μsec) is generally similar to the time difference of receiver 131b (e.g., 19.8 μsec). Therefore, at this point, it can be concluded that receivers 131a and 131b received the same data packet from transmitter 128. Also, based on the disclosed method 200, it can be concluded that the transmission event of a data packet from a transmitter to two or more receivers in a network.
[0084] In the above example, the server 140 determines the identity of the transmitter 128a by collecting at least the transmitter timestamp on the beacon 150b transmitted from the access point 122 and the receiver timestamps of the receivers 131a, 131b. For example, the server 140 may identify all of the receivers in the system 100 that have similar transmitter timestamps as reported on the beacon, and then obtain the difference between the receiver timestamps for all of the identified receivers 131a, 131b. If the time differences between the various receiver timestamps are similar to each other, the server 140 may then determine (or infer) which transmitter 128 originated a single transmission event (e.g., transmitted a data packet) to the corresponding receiver 131a, 131b at a certain point in time. For the sake of clarity, the server 140 may determine the identity of the events reported by the location receivers 131a, 131b by extracting the identities from the reports transmitted by the associated access points 122 and finding events with the same relative time difference as known beacon events.
[0085] It is recognized that the system 100 may employ the above-mentioned method including collecting all reported transmitter timestamps from the beacons 150 received by the receivers 131a, 131b, 131c, then taking the difference between the receiver timestamp of the data packets received at the receiver and the receiver timestamp of the beacons received at the receiver and determining which of the set of reported received data packets have the same difference for a known beacon event based on the fact that all packets received by the location receivers 131a, 131b and the associated access point 122 are received at the same time, except for a small propagation delay difference that is less than the allowed time difference error as described above. With further reference to table 500 and FIG. 2, the beacon 150a has not been received by the receiver 131b. However, since the beacon 150a has been received by the receiver 131a, it can be inferred using the beacon 150b for event #12, as reported for event #16.
[0086] Although exemplary embodiments have been described above, it is not intended that these embodiments describe all possible forms of the invention. Rather, the words used herein are words of description rather than limitation, and it will be understood that various changes may be made without departing from the spirit and scope of the invention. Moreover, features of various embodiments may be combined to form further embodiments of the invention.
Claims
1. 1. An apparatus for generating a mosaic for a wireless communication system, comprising: Memory, a server having the memory; The server, receiving first information from an associated access point indicating (i) a first receiver timestamp indicating that the associated access point has received a first packet from a mobile device, and (ii) a second receiver timestamp indicating that the associated access point has received a second packet from the first access point; determining a first difference between the first receiver timestamp and the second receiver timestamp to generate a first difference value; receiving second information from the first location receiver indicative of (i) a third receiver timestamp indicating that the first location receiver has received a third packet from the mobile device, and (ii) a fourth receiver timestamp indicating that the first location receiver has received the second packet from the first access point; determining a second difference between the third receiver timestamp and the fourth receiver timestamp to generate a second difference value; comparing the first difference value and the second difference value with a predetermined reception time error range, and in response to each of the first difference value and the second difference value being within the predetermined reception time error range, determining that the first packet and the third packet transmitted by the portable device are identical.
2. 2. The apparatus of claim 1, wherein the server is further programmed to receive third information from the second location receiver indicative of (i) a fifth receiver timestamp at which the second location receiver received a fourth packet from the mobile device, and (ii) a sixth receiver timestamp at which the second location receiver received the second packet from the first access point.
3. 3. The apparatus of claim 2, wherein the server is further programmed to determine a third difference between the fifth receiver timestamp and the sixth receiver timestamp to generate a third difference value.
4. The server, comparing the first difference value and the third difference value with the predetermined reception time error range, 4. The apparatus of claim 3, further programmed to determine that the first packet and the fourth packet transmitted by the portable device are identical in response to the first difference value and the third difference value being within the predetermined reception time error range.
5. 5. The apparatus of claim 4, wherein the server is further programmed to obtain Angle of Arrival (AoA) information from the first location receiver and the second location receiver, the AoA information indicating a direction of the mobile device relative to an orientation of the first location receiver and the second location receiver.
6. 6. The apparatus of claim 5, wherein the server is further programmed to determine a location of the mobile device based on the AoA information received from at least the first location receiver and the second location receiver.
7. The apparatus of claim 1 , wherein the first packet and the third packet are data packets transmitted according to a WIFI standard.
8. The apparatus of claim 7 , wherein the second packet is a beacon transmitted according to a WiFi standard.
9. 1. An apparatus for generating a mosaic for a wireless communication system, comprising: Memory and a server having the memory; The server, receiving first information from an associated access point corresponding to an acknowledgement packet received from the mobile device, the acknowledgement packet being transmitted by the mobile device in response to a data packet transmitted by the associated access point, the first information further corresponding to a receiver address field in the data packet providing an identification of the mobile device to which the associated access point transmits the data packet; A device programmed to access the receiver address field to determine an identity of the mobile device after the acknowledgement packet is received from the mobile device at the associated access point.
10. The apparatus of claim 9, wherein the receiver address field is located within the data packet.
11. 10. The apparatus of claim 9, wherein the associated access point is an entity selected by the mobile device to bridge all traffic to and from a distribution system.
12. The apparatus of claim 11, wherein the distribution system is a network externally bridged to a wireless local radio network with which the mobile device is associated.
13. 10. The apparatus of claim 9, wherein the server is further programmed to receive first information from an associated access point indicating (i) a first receiver timestamp indicating that the associated access point has received a first packet from the mobile device, and (ii) a second receiver timestamp indicating that the associated access point has received a second packet from the first access point.
14. 14. The apparatus of claim 13, wherein the server is further programmed to determine a first difference between the first receiver timestamp and the second receiver timestamp to generate a first difference value.
15. The server, receiving second information from the first location receiver indicating (i) a third receiver timestamp at which the first location receiver received a third packet from the mobile device, and (ii) a fourth receiver timestamp at which the first location receiver received the second packet from the first access point; 15. The apparatus of claim 14, further programmed to determine a second difference between the third receiver timestamp and the fourth receiver timestamp to generate a second difference value.
16. The server, comparing each of the first difference value and the second difference value with a predetermined reception time error range; 16. The apparatus of claim 15, further programmed to determine that the first packet and the third packet transmitted by the portable device are identical in response to each of the first difference value and the second difference value being within the predetermined reception time error range.
17. 10. The apparatus of claim 9, wherein the server is further programmed to obtain Angle of Arrival (AoA) information from the first location receiver, the AoA information indicating a direction of the mobile device relative to a bearing of the first location receiver.
18. 20. The apparatus of claim 17, wherein the server is further programmed to determine a location of the mobile device based on at least the AoA information received from the first location receiver.
19. 1. A method for generating a mosaic for a wireless communication system, comprising: receiving, at a server, first information from an associated access point indicating (i) a first receiver timestamp indicating that the associated access point received a first packet from a mobile device, and (ii) a second receiver timestamp indicating that the associated access point received a second packet from the first access point; determining a first difference between the first receiver timestamp and the second receiver timestamp to generate a first difference value; receiving second information from the first location receiver indicative of (i) a third receiver timestamp indicating that the first location receiver has received a third packet from the mobile device, and (ii) a fourth receiver timestamp indicating that the first location receiver has received the second packet from the first access point; determining a second difference between the third receiver timestamp and the fourth receiver timestamp to generate a second difference value; comparing the first difference value and the second difference value with a predetermined reception time error range, and determining that the first packet and the third packet transmitted by the portable device are identical in response to the first difference value and the second difference value each being within the predetermined reception time error range.
20. 1. A method for generating a mosaic for a wireless communication system, comprising: receiving, at the first server, first information from an associated access point corresponding to an acknowledgement packet received from the mobile device, the acknowledgement packet being transmitted by the mobile device in response to a data packet transmitted by the associated access point, the first information further corresponding to a receiver address field in the data packet providing an identification of the mobile device to which the associated access point transmits the data packet; After the acknowledgement packet is received from the mobile device at the associated access point, the receiver address field is accessed to determine the identity of the mobile device.
Citation Information
Patent Citations
Access point, positional information acquisition method, computer program, and positional information acquisition system
JP2016052062A
Method for controlling medium access in full-duplex wi-fi network
US20160277160A1
Apparatus and method for calibrating a wireless access point comprising an array of multiple antennas
US20160345286A1
Communication processor, integrated circuit, wireless communication terminal, memory card, wireless communication device, and wireless communication method
WO2015087870A1
