Matching multiple devices to identify joint movement of the mobile devices

• US 9,661,464 B2
• Filed: 02/28/2013
• Issued: 05/23/2017
• Est. Priority Date: 02/28/2013
• Status: Active Grant

• Current Assignee: SAP SE
• Original Assignee: SAP SE
• Inventors: Lerenc, Vedran
• Primary Examiner(s): Mitchell, Nathan
• Assistant Examiner(s): TACSIK, ERNEST G
• Application Number:
  US13/780,294
• Publication Number:
  US 20140243020A1
• Time in Patent Office: 1,545 Days
• Field of Search: 455405, 455456, 4554561, 4554563
• CPC Class Codes: H04W 4/02 Services making use of location information
• CPC Class Codes: H04W 4/023 using mutual or relative location information between multiple location based services [LBS] targets or of distance thresholds
• CPC Class Codes: H04W 4/027 using movement velocity, acceleration information
• CPC Class Codes: H04W 4/029 Location-based management or tracking services
• CPC Class Codes: H04W 4/40 for vehicles, e.g. vehicle-to-pedestrians [V2P]

Abstract

Location data and/or acceleration data of a mobile device may be received. The data may include timestamps. The timestamped data of the mobile device may be compared to timestamped data of another mobile device. Upon determining the timestamped data of the mobile device matches the timestamped data of the other mobile device, joint movement of the mobile devices may be signaled.

Claims

1. A computer-implemented method for determining joint movement of multiple mobile devices, the method comprising:

receiving first timestamped data that indicate both of location data and acceleration data from a first mobile device, and determining a first movement profile and a first acceleration profile of the first mobile device based on the first timestamped data, the first movement profile specifying a plurality of locations at which the first mobile device was located over a first period of time and the first acceleration profile specifying acceleration measurements of the first mobile device over a second period of time, wherein the first movement profile comprises a series of paired start timestamps and end timestamps corresponding to each of a plurality of rides, the start timestamps being automatically transmitted to a backend server by a mobile device associated with a driver upon commencement of the corresponding ride and the end timestamps being automatically transmitted to the backend server by such mobile device associated with the driver upon termination of the corresponding ride;

receiving second timestamped data that indicate both of location data and acceleration data from a second mobile device, and determining a second movement profile and a second acceleration profile of the second mobile device based on the second timestamped data, the second movement profile specifying a plurality of locations at which the second mobile device was located over a third period of time and the second acceleration profile specifying acceleration measurements of the second mobile device over a fourth period of time, wherein the second movement profile comprises a series of paired start timestamps and end timestamps corresponding to each of a plurality of rides, the start timestamps being automatically transmitted to a backend server by a mobile device associated with a driver upon commencement of the corresponding ride as indicated by activation of a navigation device and the end timestamps being automatically transmitted to the backend server by the mobile device associated with such driver upon termination of the corresponding ride as indicated by deactivation of the navigation device;

comparing the first and second movement profiles using a combination of geographic and temporal dimensions;

comparing the first and second acceleration profiles using a combination of acceleration and temporal dimensions;

processing the acceleration and movement profiles to determine if there is a match between both of

     1) the first and second movement profiles and

     2) the first and second acceleration profiles,

signaling joint movement of the first and second mobile devices if the match is determined, wherein first and second timestamped data are one of

     1) synchronized and

     2) not synchronized;

determining whether a ridesharing service is available based upon the determined match; and

transmitting a ridesharing option to the first and second mobile devices if the ridesharing service is available.

20. The method of claim 1, wherein the first mobile device and the second mobile device each respectively comprise a GPS sensor for generating the location data and an accelerometer for generating the acceleration data.

2. A computer-implemented method for determining joint movement of multiple mobile devices, the method comprising:

receiving first timestamped data that indicate both of location data and acceleration data from a first mobile device, and determining a first movement profile and a first acceleration profile of the first mobile device based on the first timestamped data, the first movement profile specifying a plurality of locations at which the first mobile device was located over a first period of time and the first acceleration profile specifying acceleration measurements of the first mobile device over a second period of time, wherein the first movement profile comprises a series of paired start timestamps and end timestamps corresponding to each of a plurality of rides, the start timestamps being automatically transmitted to a backend server by a mobile device associated with a driver upon commencement of the corresponding ride as indicated by activation of a navigation device and the end timestamps being automatically transmitted to the backend server by such mobile device associated with the driver upon termination of the corresponding ride as indicated by deactivation of the navigation device;

receiving second timestamped data that indicate both of location data and acceleration data from a second mobile device, and determining a second movement profile and a second acceleration profile of the second mobile device based on the second timestamped data, the second movement profile specifying a plurality of locations at which the second mobile device was located over a third period of time and the second acceleration profile specifying acceleration measurements of the second mobile device over a fourth period of time, wherein the second movement profile comprises a series of paired start timestamps and end timestamps corresponding to each of a plurality of rides, the start timestamps being automatically transmitted to a backend server by a mobile device associated with a driver upon commencement of the corresponding ride and the end timestamps being automatically transmitted to the backend server by the mobile device associated with such driver upon termination of the corresponding ride;

comparing the first and second movement profiles using a combination of geographic and temporal dimensions;

comparing the first and second acceleration profiles using a combination of acceleration and temporal dimensions;

processing the acceleration and movement profiles to determine if there is a match between both of

     1) the first and second movement profiles and

     2) the first and second acceleration profiles,

signaling joint movement of the first and second mobile devices if the match is determined;

determining whether a ridesharing service is available based upon the determined match; and

transmitting a ridesharing option to the first and second mobile devices if the ridesharing service is available.

3. The method according to claim 2, wherein the timestamped data of the first mobile device is received at predefined intervals.

4. The method according to claim 2, wherein the timestamped data of the first mobile device and the timestamped data of the second mobile device are synchronized based on internal clocks of the first mobile device and the second mobile device being synchronized.

5. The method according to claim 2, wherein the timestamped data of the first mobile device and the timestamped data of the second mobile device are not synchronized.

6. The method according to claim 5, wherein the timestamped data of the first mobile device and the timestamped data of the second mobile device are matched based on a time shift.

7. The method according to claim 2, wherein the timestamped data of the first mobile device and the timestamped data of the second mobile device are matched within a tolerance level.

8. An apparatus comprising:

a processor to;

receive first timestamped data that indicate both of location data and acceleration data from a first mobile device, and determine a first movement profile and a first acceleration profile of the first mobile device based on the first timestamped data, the first movement profile specifying a plurality of locations at which the first mobile device was located over a first period of time and the first acceleration profile specifying acceleration measurements of the first mobile device over a second period of time, wherein the first movement profile comprises a series of paired start timestamps and end timestamps corresponding to each of a plurality of rides, the start timestamps being automatically transmitted to a backend server by a mobile device associated with a driver upon commencement of the corresponding ride as indicated by activation of a navigation device and the end timestamps being automatically transmitted to the backend server by such mobile device associated with the driver upon termination of the corresponding ride as indicated by deactivation of the navigation device;

receive second timestamped data that indicate both of location data and acceleration data from a second mobile device, and determining a second movement profile and a second acceleration profile of the second mobile device based on the second timestamped data, the second movement profile specifying a plurality of locations at which the second mobile device was located over a third period of time and the second acceleration profile specifying acceleration measurements of the second mobile device over a fourth period of time, wherein the second movement profile comprises a series of paired start timestamps and end timestamps corresponding to each of a plurality of rides, the start timestamps being automatically transmitted to a backend server by a mobile device associated with a driver upon commencement of the corresponding ride and the end timestamps being automatically transmitted to the backend server by the mobile device associated with such driver upon termination of the corresponding ride;

compare the first and second movement profiles using a combination of geographic and temporal dimensions;

compare the first and second acceleration profiles using a combination of acceleration and temporal dimensions;

process the acceleration and movement profiles to determine if there is a match between both of

     1) the first and second movement profiles and

     2) the first and second acceleration profiles,

signal joint movement of the first and second mobile devices if the match is determined;

determine whether a ridesharing service is available based upon the determined match; and

transmit a ridesharing option to the first and second mobile devices if the ridesharing service is available.

9. The apparatus of claim 8, wherein the timestamped data of the mobile device is received at predefined intervals.

10. The apparatus of claim 8, wherein the timestamped data of the mobile device and the timestamped data of the other mobile device are synchronized.

11. The apparatus of claim 8, wherein the timestamped data of the mobile device and the timestamped data of the other mobile device are not synchronized.

12. The apparatus of claim 11, wherein the timestamped data of the mobile device and the timestamped data of the other mobile device are matched based on a time shift.

13. The apparatus of claim 8, wherein the timestamped data of the mobile device and the timestamped data of the other mobile device are matched within a tolerance level.

14. A non-transitory computer-readable medium embodied with computer-executable instructions for causing a computer to execute instructions, the computer instructions comprising:

receiving first timestamped data that indicate both of location data and acceleration data from a first mobile device, and determining a first movement profile and a first acceleration profile of the first mobile device based on the first timestamped data, the first movement profile specifying a plurality of locations at which the first mobile device was located over a first period of time and the first acceleration profile specifying acceleration measurements of the first mobile device over a second period of time, wherein the first movement profile comprises a series of paired start timestamps and end timestamps corresponding to each of a plurality of rides, the start timestamps being automatically transmitted to a backend server by a mobile device associated with a driver upon commencement of the corresponding ride as indicated by activation of a fare meter and the end timestamps being automatically transmitted to the backend server by such mobile device associated with the driver upon termination of the corresponding ride as indicated by deactivation of the fare meter;

receiving second timestamped data that indicate both of location data and acceleration data from a second mobile device, and determining a second movement profile and a second acceleration profile of the second mobile device based on the second timestamped data, the second movement profile specifying a plurality of locations at which the second mobile device was located over a third period of time and the second acceleration profile specifying acceleration measurements of the second mobile device over a fourth period of time, wherein the second movement profile comprises a series of paired start timestamps and end timestamps corresponding to each of a plurality of rides, the start timestamps being automatically transmitted to a backend server by a mobile device associated with a driver upon commencement of the corresponding ride and the end timestamps being automatically transmitted to the backend server by the mobile device associated with such driver upon termination of the corresponding ride;

comparing the first and second movement profiles using a combination of geographic and temporal dimensions;

comparing the first and second acceleration profiles using a combination of acceleration and temporal dimensions;

processing the acceleration and movement profiles to determine if there is a match between both of

     1) the first and second movement profiles and

     2) the first and second acceleration profiles,

signaling joint movement of the first and second mobile devices if the match is determined;

determining whether a ridesharing service is available based upon the determined matched; and

transmitting a ridesharing option to the first and second mobile devices if the ridesharing service is available.

15. The computer-readable medium of claim 14, wherein the timestamped data of the mobile device is received at predefined intervals.

16. The computer-readable medium of claim 14, wherein the timestamped data of the mobile device and the timestamped data of the other mobile device are synchronized.

17. The computer-readable medium of claim 14, wherein the timestamped data of the mobile device and the timestamped data of the other mobile device are not synchronized.

18. The computer-readable medium of claim 17, wherein the timestamped data of the mobile device and the timestamped data of the other mobile device are matched based on a time shift.

19. The computer-readable medium of claim 14, wherein the timestamped data of the mobile device and the timestamped data of the other mobile device are matched within a tolerance level.