Patent Description:
When measuring RF transmission systems, uplink transmissions (i.e. from user equipment device, such as a user endpoint device or handset, to a base station) and downlink transmissions (i.e. from the base station to the user equipment device) are both important. However, systems and methods to simultaneously collect measurements of both the uplink transmissions and the downlink transmissions require scanning equipment at two locations: the user equipment device and the base station. Furthermore, such systems require that the measurements of the uplink transmissions and the downlink transmissions be aligned to reflect information with a shared time stamp. Unfortunately, in most cases, there is no shared network or data connection available between the user equipment device and the base station, thereby limiting time stamp coordination.

Known systems and methods to address the above-identified challenges are manual and work in connection with a single base station in one location and a plurality of user equipment devices in second, different locations. For example, known systems and methods collect first data at the base station using internal data generated by the base station and, during post processing, occasionally or periodically compare that first data to second data collected at any of the plurality of user equipment devices. Accordingly, such systems and methods rely on self-reporting from hardware at the base station and do not use any independent RF scanning equipment. As such, there is no easy way to coordinate the first data with the second data. Indeed, to coordinate the first data with the second data, some known systems and methods require recording the first data at the base station for an abnormally long period of time (e.g. all day) and matching time stamps of the first data with time stamps of the second data that was recorded at any of the plurality of user equipment devices during a smaller period of time (e.g. a few hours). Furthermore, despite such a complicated coordination of manual data, known systems and methods still give engineers a limited picture of the uplink transmissions and the downlink transmissions.

In <CIT> RF sensors acquire and store RF data in memory. One RF sensor generates a trigger signal when the RF sensor detects a feature of interest in its acquired RF data. The detecting RF sensor wirelessly transmits the trigger signal to the non-detecting RF sensor. The non-detecting RF sensor reads the appropriate RF data from its memory in response to receipt of the trigger signal. The non-detecting RF sensor accesses the appropriate RF data using a time of day when the trigger signal is received and a predetermined time offset. In <CIT> synchronizing a wireless sensor includes receiving a first command at the wireless sensor, noting a first timestamp value indicating when the first reply is sent, responding to the first command with a first reply, receiving a second command at the wireless sensor that contains a second timestamp value indicating when the first reply was received and a third timestamp value indicating when the second command was sent to the wireless sensor, noting a fourth timestamp value indicating when the second command was received by the wireless sensor, and determining an offset at the wireless sensor using the first, second, third, and fourth timestamp values. The presence of the first timestamp value may be interpreted as a request to provide timestamp information for synchronization. An access point may communicate with the wireless sensor.

In view of the above, there is a continuing, ongoing need for improved systems and methods. Embodiments of the invention will now be described, by way of non-limiting example only, with reference to the accompanying drawings.

The present invention is defined in the independent claims, to which reference should now be made. Optional embodiments are defined in the dependent claims.

While this invention is susceptible of an embodiment in many different forms, there are shown in the drawings and will be described herein in detail specific embodiments thereof with the understanding that the present disclosure is to be considered as an exemplification of the principles of the invention. It is not intended to limit the invention to the specific illustrated embodiments.

Embodiments disclosed herein can include systems and methods for time coordinating a plurality of RF data collection devices at disparate locations. In particular, the plurality of RF data collection devices can record collected data using an effectively shared time stamp and coordinate events, such as control logic, without a need for a shared network or data connection.

It is to be understood that each of the plurality of RF data collection devices disclosed and described herein can include a respective piece of scanning equipment. It is also to be understood that any of the plurality of the RF data collection devices disclosed and described herein can include one or more base stations or one or more of a plurality of user equipment devices.

In accordance with disclosed embodiments, all of the plurality of RF data collection devices can be configured with the same settings. For example, those settings can identify which RF network to monitor for timing information and can define a series of repeating data recording events. In some embodiments, the RF network to monitor can include a <NUM> LTE network at a specific frequency or any other network that is not otherwise being monitored for timing for other purposes. Furthermore, in some embodiments, the series of repeating data recording events can identify one or more triggers and one or more time periods.

In operation, the respective piece of scanning equipment of each of the plurality of RF data collection devices can lock on the RF network to monitor, record the collected data responsive to a respective one of the plurality of RF data collection devices identifying one of the triggers for a length of time equal to a first of the time periods, and reset every length of time equal to a second of the time periods. As a specific, but non-limiting example, the respective piece of scanning equipment of each of the plurality of RF data collection devices can lock on the <NUM> LTE network at a first frequency, switch to a next frequency to test every <NUM> (i.e. one of the triggers), record the collected data on the next frequency to test for <NUM> (i.e. the first of the time periods), and reset every <NUM> (i.e. the second of the time periods).

In accordance with disclosed embodiments, each of the plurality of RF data collection devices can communicate with a shared NTP server to set a respective time stamp to a common clock, thereby achieving the benefit of a shared time stamp without the shared network or data connection and even though each of the plurality of RF data collection devices uses its own respective time stamp to record the collected data.

In accordance with the above, a single one of the plurality of user equipment devices can be tested against two or more of the base stations. Similarly, more than one of the plurality of user equipment devices can be tested against two or more of the base stations.

<FIG> is a block diagram of a system 20A in accordance with disclosed embodiments. As seen in <FIG>, in some embodiments, the system 20A can include a first RF data collection device <NUM>, a second RF collection device <NUM>, a network time server <NUM>, a base station BS that can generate an RF network N, and user equipment UE that can connect to the RF network N. In some embodiments, the first RF collection device <NUM> can include a first programmable processor <NUM>, a first RF transceiver device <NUM>, a first memory device <NUM>, and a first internal clock <NUM> that can manage a first local time for the first RF transceiver device <NUM>. Similarly, in some embodiments, the second RF device <NUM> can include a second programmable processor <NUM>, a second RF transceiver device <NUM>, a second memory device <NUM>, and a second internal clock <NUM> that can manage a second local time for the second RF transceiver device <NUM>. Additionally, the network time server <NUM> can include a third programmable processor <NUM>, a third RF transceiver device <NUM>, and a third internal clock <NUM> that can act as a common time source for the first RF data collection device <NUM> and the second RF data collection device <NUM>.

In some embodiments, the first RF data collection device <NUM> can collect and record a first plurality of RF data from the RF network N. For example, in some embodiments, the first RF transceiver device <NUM> can receive the first plurality of RF data from the RF network N when located proximate to the base station BS or the user equipment UE, and in some embodiments, the first programmable processor <NUM> can record the first plurality of RF data in the first memory device <NUM>. As such, in some embodiments, the first plurality of RF data can include first values of the first local time at which corresponding first RF signal components are recorded in the first memory device <NUM>.

In some embodiments, the first plurality of RF data can be compared to and/or coordinated with a second plurality RF data collected and recorded by the second RF data collection device <NUM>. However, to enable proper comparison and coordination of the first plurality of RF data and the second plurality of RF data when the first RF data collection device <NUM> and/or the second RF data collection device <NUM> have independent network connectivity and/or no network connectivity when the first plurality of RF data and/or the second plurality of RF data are collected, the first local time can be coordinated with the second local time.

For example, in some embodiments, the first programmable processor <NUM> can synchronize the first local time to an initial value of the common time source. Following such synchronization, the first programmable processor <NUM> can generate a first timestamp log file documenting a propensity of the first local time to deviate from the common time source and save the first timestamp log file in the first memory device <NUM>. Then, after the first plurality of RF data is collected, the first timestamp log file can be used to normalize the first values of the first local time to corresponding values of the common time source for comparison and coordination with the second plurality of RF data.

For example, in some embodiments, the first RF data collection device <NUM> can connect to the network time server <NUM> via the first RF transceiver <NUM> and the third RF transceiver device <NUM> using a network time protocol to synchronize the first local time to the common time source. In some embodiments, following such synchronization, the first RF data collection device <NUM> can periodically connect to the network time server <NUM> to compare a current value of the first local time to a current value of the common time source, and when the current value of the first local time fails to match the current value of the common time source, the first programmable processor <NUM> can add an entry to the first timestamp log file that records offset amounts between the current value of the first local time and the current value of the common time source and subsequently increase a rate at which the first RF data collection device <NUM> periodically connects to the network time server <NUM>. In some embodiments, the rate can be doubled (e.g. from every hour to every <NUM> minutes).

Similarly, in some embodiments, the second RF transceiver device <NUM> can receive the second plurality of RF data from the RF network when located proximate to the base station BS or the user equipment UE, and in some embodiments, the second programmable processor <NUM> can record the second plurality of RF data in the second memory device <NUM>. As such, in some embodiments, the second plurality of RF data can include second values of the second local time at which the corresponding second RF signal components are recorded in the second memory device <NUM>.

As explained above, the second plurality of RF data can be compared to and/or coordinated with the first plurality RF data collected. However, to enable proper comparison and coordination of the first plurality of RF data and the second plurality of RF data when the first RF data collection device <NUM> and/or the second RF data collection device <NUM> have independent network connectivity and/or no network connectivity when the first plurality of RF data and/or the second plurality of RF data are collected, the second local time can be coordinated with the first local time.

For example, in some embodiments, the second programmable processor <NUM> can synchronize the second local time to the initial value of the common time source. Following such synchronization, the second programmable processor <NUM> can generate a second timestamp log file documenting a propensity of the second local time to deviate from the common time source and save the second timestamp log file in the second memory device <NUM>. Then, after the second plurality of RF data is collected, the second timestamp log file can be used to normalize the second values of the second local time to the corresponding values of the common time source for comparison and coordination with the first plurality of RF data.

For example, the second RF data collection device <NUM> can connect to the network time server <NUM> via the second RF transceiver device <NUM> and the third RF transceiver device <NUM> using the network time protocol to synchronize the second local time to the common time source. In some embodiments, following such synchronization, the second RF data collection device <NUM> can periodically connect to the network time server <NUM> to compare a current value of the second local time to the current value of the common time source, and when the current value of the second local time fails to match the current value of the common time source, the second programmable processor <NUM> can add an entry to the second timestamp log file that records offset amounts between the current value of the second local time and the current value of the common time source and subsequently increase a rate at which the second RF data collection device <NUM> periodically connects to the network time server <NUM>.

The first programmable processor <NUM> and/or the second programmable processor <NUM> can normalize the first plurality of RF data and/or the second plurality of RF data before export that data from the first RF data collection device <NUM> and the second RF data collection device <NUM>, respectively. However, the first RF data collection device <NUM> and/or the second RF data collection device <NUM> can export the first timestamp log file and/or the second time stamp log file with the first plurality of RF data and the second plurality of RF data, respectively, so that another device, such as the third programmable processor <NUM> can normalize the first plurality of RF data and/or the second plurality of RF data for comparison and coordination thereof.

In some embodiments, the first timestamp log file is used to normalize the first values of the first local time to the corresponding values of the common time source for comparison with the second plurality RF data by calculating time offsets for each interval period at which the corresponding first RF signal components are recorded using a linear average of the offset amounts recorded in the first timestamp log file for an adjustable elapsed time period. Similarly, in some embodiments, the second timestamp log file can be used to normalize the second values of the second local time to the corresponding values of the common time source for comparison with the first plurality RF data by calculating time offsets for each interval period at which the corresponding second RF signal components are recorded using a linear average of the offset amounts recorded in the second timestamp log file for the adjustable elapsed time period. As a specific, but non-limiting example, if the first timestamp log file and/or the second timestamp log file has a linear average of the offset amounts recorded of <NUM> milliseconds for a <NUM> second time period, and the first plurality of RF data and/or the second plurality of RF data includes <NUM> pieces of data recorded every <NUM> seconds, then the first plurality of RF data and/or the second plurality of RF data can be normalized by adjusting the first value of the first local time and/or the second value of the second local time by <NUM>/<NUM> milliseconds.

In some embodiments, the first RF data collection device <NUM> and/or the second RF data collection device <NUM> can receive a meta data collection file that includes configuration information for the RF network N and an identification of the network time server <NUM>. In these embodiments, the first RF data collection device <NUM> and/or the second RF data collection device <NUM> can identify the network time server <NUM> from the meta data collection file and use the configuration information to collect and record the first plurality of RF data and/or the second plurality of RF data, respectively. In some embodiments, the configuration information for the RF network N can include frequencies, bands, or channels of the RF network N, a recording bandwidth, and/or a recording data rate.

<FIG> is a block diagram of a system 20B in accordance with disclosed embodiments. As seen in <FIG>, in some embodiments, the system 20B can include the first RF data collection device <NUM>, the second RF data collection device <NUM>, the user equipment UE, and the base station BS while omitting the network time server <NUM>. In these embodiments, the first local time and the second local time can be synchronized by using one of the first local time and the second local time as the common time source, for example, when there is no physical network access and any RF data from the RF network N is retrieved manually through direct access by a device at the base station BS or the user equipment UE, such as via a USB stick or similar removal storage device.

In embodiments in which the second local time is the common time source, the first RF data collection device <NUM> can connect to the second RF data collection device <NUM> via the first RF transceiver device <NUM> connecting to the second RF transceiver device <NUM>, and the first programmable processor <NUM> can receive the initial value of the common time source (i.e. the second local time) from the second local clock <NUM>. Then, the first RF data collection device <NUM> can maintain such a connection with the second RF collection device <NUM> for a predetermined time period and periodically compare the current value of the first local time to the current value of the common time source during the predetermined time period. Then, when the current value of the first local time fails to match the current value of the common time source, the first programmable processor <NUM> can record offset amounts therebetween in the first timestamp log file. As a specific, but non-limiting example, the first RF data collection device <NUM> can stay connected to the second RF data collection device <NUM> for <NUM> seconds while validating the current value of the first local time every <NUM> seconds to create the first timestamp log file as described herein.

In some embodiments, the first RF data collection device <NUM> can pair with the second RF data collection device <NUM> via a Bluetooth connection to receive the initial value of the common time source from the second RF data collection device <NUM>. For example, in these embodiments, the second programmable processor <NUM> can select the first RF data collection device <NUM> from a list of paired devices, and responsive to such a selection, the second RF collection device can transmit the initial value of the common time source to the first RF data collection device <NUM> via the second RF transceiver device <NUM> and the first RF transceiver device <NUM>. Furthermore, while paired, the first RF data collection device <NUM> can periodically receive the current value of the common time source from the second RF data collection device <NUM>.

<FIG> is a block diagram of a system 20C according to disclosed embodiments. As seen in <FIG>, in some embodiments, the system 20C can include the first RF data collection device <NUM>, the second RF data collection device <NUM>, the user equipment UE, the base station BS, and a second station <NUM> that can broadcast a local broadcast signal in proximity to the base station BS and the user equipment UE. In these embodiments, the first RF data collection device <NUM> and/or the second RF data collection device <NUM> can use properties of the local broadcast signal to generate the first timestamp log file and the second timestamp log file, respectively. In some embodiments, the local broadcast signal can include a <NUM> AM radio signal.

For example, in some embodiments, the first RF data collection device <NUM> and/or the second RF data collection device <NUM> can select a timing frequency for collecting the first plurality of RF data and/or the second plurality of RF data, respectively, using a simple amplitude modulation of the local broadcast signal. In these embodiments, the first RF data collection device <NUM> and/or the second RF data collection device <NUM> can monitor the timing frequency, count peaks of the local broadcast signal, and generate the first timestamp log file and/or the second timestamp log file, respectively, by recording the current value of the first local time and/or the second local time after N*<NUM>/X peaks of the local broadcast signal, where X is the timing frequency and N is a preconfigured multiplier selected to limit an impact of recording the current value of the first local time and/or the current value of the second local time. As such, in these embodiments, the first timestamp log file and/or the second timestamp log file can include an effective peak count log of the timing frequency monitored.

In some embodiments, additional RF data collection devices similar to the first RF data collection device <NUM> and the second RF data collection device <NUM> can be included in any of the systems 20A, 20B, and 20C as described herein. For example, in the system 20A, any of the additional RF data collection devices can synchronize its respective local time with the network time server <NUM> as described herein. In the system 20B, any of the additional RF data collection devices can synchronize its respective local time with the second local time of the second RF data collection device <NUM>. Finally, in the system 20C, any of the additional RF data collection devices can use the properties of the local broadcast signal to synchronize its respective local time.

Although a few embodiments have been described in detail above, other modifications are possible. For example, other components may be added to or removed from the described systems, and other embodiments may be within the scope of the invention.

Claim 1:
A method comprising:
synchronizing a first local time of a first RF data collection device (<NUM>) to an initial value of a common time source (<NUM>);
generating a first timestamp log file at the first RF data collection device (<NUM>), the first timestamp log file documenting offset amounts between a current value of the first local time and a current value of the common time source (<NUM>);
saving the first timestamp log file in a first memory device (<NUM>) of the first RF data collection device (<NUM>);
collecting a first plurality of RF data from an RF network (N);
recording, in the first memory device (<NUM>), the first plurality of RF data including first values of the first local time at which corresponding first RF signal components are recorded; and
using the first timestamp log file to normalize the first values of the first local time to corresponding values of the common time source (<NUM>) for comparison with a second plurality of RF data recorded by a second RF data collection device (<NUM>).