WO2020142087A1 - Systems and methods for device fingerprint determination in a transportation service - Google Patents

Systems and methods for device fingerprint determination in a transportation service Download PDF

Info

Publication number
WO2020142087A1
WO2020142087A1 PCT/US2018/068218 US2018068218W WO2020142087A1 WO 2020142087 A1 WO2020142087 A1 WO 2020142087A1 US 2018068218 W US2018068218 W US 2018068218W WO 2020142087 A1 WO2020142087 A1 WO 2020142087A1
Authority
WO
WIPO (PCT)
Prior art keywords
terminal device
fingerprint
server
user data
information
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/US2018/068218
Other languages
French (fr)
Inventor
Xiaoyong Yi
Yu Wang
Fengmin Gong
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Didi Research America LLC
Original Assignee
Didi Research America LLC
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Didi Research America LLC filed Critical Didi Research America LLC
Priority to CN201880098088.1A priority Critical patent/CN112868018B/en
Priority claimed from US16/237,043 external-priority patent/US11038877B2/en
Priority claimed from US16/237,016 external-priority patent/US11080509B2/en
Priority claimed from US16/236,970 external-priority patent/US20200213855A1/en
Publication of WO2020142087A1 publication Critical patent/WO2020142087A1/en
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/80—Services using short range communication, e.g. near-field communication [NFC], radio-frequency identification [RFID] or low energy communication
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/30—Authentication, i.e. establishing the identity or authorisation of security principals
    • G06F21/44—Program or device authentication
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
    • H04L63/0876—Network architectures or network communication protocols for network security for authentication of entities based on the identity of the terminal or configuration, e.g. MAC address, hardware or software configuration or device fingerprint
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/06—Authentication
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/60—Context-dependent security
    • H04W12/69—Identity-dependent
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/30—Services specially adapted for particular environments, situations or purposes
    • H04W4/40—Services specially adapted for particular environments, situations or purposes for vehicles, e.g. vehicle-to-pedestrians [V2P]

Definitions

  • the present disclosure relates to systems and methods for device fingerprint determination in a transportation service, and more particularly to, systems and methods for determining fingerprint information of a terminal device in a transportation service using an authenticated terminal device.
  • Terminal device frauds have negative impact on the fairness and efficiency of transportation services such as ride-hailing (also referred to as ride-sharing) services.
  • transportation service providers e.g., drivers
  • Fraudsters may also run faked ride-sharing trips to gain awards for accomplishing certain amount of transactions.
  • each faked mobile device can be assigned to a phone number, using Short Message Service (SMS) to verify is not enough to prevent such fraud activities.
  • SMS Short Message Service
  • User registration may alleviate the fraud activities to some extent.
  • Existing user registration methods collect basic user information such as user name, phone number, and so on. That information is easy to fake and thus is not enough to prevent fraud activities.
  • terminal device related information such as BluetoothTM fingerprint of the user’s terminal device is relatively hard to fake, the information is also difficult to acquire (e.g., a user may need to go to a certain location to have his/her terminal device scanned to register the terminal device’s BluetoothTM fingerprint). The inconveniency may deter the user from choosing to use the transportation service.
  • Embodiments of the disclosure address the above problems by methods and systems for fingerprint determination in a transportation service using authenticated terminal devices to enhance registering accuracy and efficiency.
  • inventions of the disclosure provide a system for determining fingerprint information of a terminal device in a transportation service.
  • An exemplary system may include a communication interface configured to establish a communication link between first and second terminal devices and receive user data from the first terminal device associated with a user of the transportation service.
  • the communication interface may also be configured to receive authentication information authenticating the second terminal device.
  • the system may also include a memory configured to store the user data and at least one processor coupled to the memory.
  • the at least one processor may be configured to determine a first fingerprint of the first terminal device based on the user data after receiving the authentication information
  • embodiments of the disclosure also provide a method for determining fingerprint information of a terminal device in a transportation service.
  • An exemplary method may include a establishing a communication link between first and second terminal devices and receiving user data from the first terminal device associated with a user of the transportation service.
  • the method may also include receiving authentication information authenticating the second terminal device and determining a first fingerprint of the first terminal device based on the user data after receiving the authentication information authenticating the second terminal device.
  • embodiments of the disclosure further provide a non-transitory computer-readable medium storing instruction that, when executed by one or more processors, cause the one or more processors to perform a method for determining fingerprint information of a terminal device in a transportation service.
  • the method may include establishing a
  • the method may also include receiving authentication information authenticating the second terminal device and determining a first fingerprint of the first terminal device based on the user data after receiving the authentication information authenticating the second terminal device.
  • FIG. 1 illustrates a schematic diagram of an exemplary device fingerprint determination system in a transportation service, according to embodiments of the disclosure.
  • FIG. 2 illustrates a block diagram of an exemplary fingerprint determining system, according to embodiments of the disclosure.
  • FIG. 3 illustrates a flowchart of an exemplary method for fingerprint determination in a transportation service, according to embodiments of the disclosure.
  • FIG. 4 illustrates a flowchart of another exemplary method for fingerprint determination in a transportation service, according to embodiments of the disclosure
  • FIG. 1 illustrates a schematic diagram of an exemplary device fingerprint determination system 100 in a transportation service, according to embodiments of the disclosure.
  • a service vehicle 120 associated with a service provider 122 may be registered to a transportation service platform (e.g., a ride-hailing or ride-sharing service platform) to provide transportation service to passengers/riders.
  • a terminal device 110 associated with service provider 120 may also be registered.
  • a device fingerprint e.g., unique information identifying a terminal device, hereinafter simply referred to as “fingerprint” of terminal device 110 may be acquired and stored by the transportation service platform as part of the registration process.
  • the fingerprint may be used as a reference fingerprint in authentication, authorization, verification, or other terminal device identity related processes.
  • the fingerprint of terminal device 110 may be stored in a server 130, which may be part of the transportation service platform. Server 130 may authenticate terminal device 110 based on the stored reference fingerprint.
  • terminal device 110 may be built in, integrated into, installed on, or otherwise associated with service vehicle 120.
  • terminal device 110 may be part of service vehicle 120’s built-in system that can be configured to perform fingerprint determination functions disclosed herein (e.g., a built-in computer system).
  • terminal device 110 may be installed as an add-on system after service vehicle 120 is registered to the transportation service platform.
  • terminal device 110 may be a stand-alone device separate from service vehicle 120.
  • terminal device 110 may be a mobile device used by service provider 122 that facilitates provision of transportation services.
  • terminal device 110 may receive authentication information from server 130 (e.g., a cloud server providing computational power, storage space, and/or communication capacity to the transportation service platform).
  • server 130 e.g., a cloud server providing computational power, storage space, and/or communication capacity to the transportation service platform.
  • terminal device 110 may be equipped with a communication interface to communicate with server 130, including transmitting data to server 130 and receiving authentication information from server 130.
  • service vehicle 120 may be equipped with one or more communication interfaces to receive information from and/or transmit information to server 130.
  • information transmitted from terminal device 110/120 to server 130 may include fingerprint information or may be used to determine the fingerprint of terminal device 110 by server 130. Based on the fingerprint, server 130 may determine whether to authenticate terminal device 110. For example, when server 130 determines to authenticate terminal device 110, server 130 may transmit an authentication back to terminal device 110.
  • Terminal device 110 may communicate with a terminal device 140 associated with a user 142, either directly or through server 130, to facilitate various functions such as receiving user data including, for example, identification information; transmitting and/or receiving transportation service requests; making and/or receiving payment, or the like.
  • a transportation service request may include a current location of the passenger, a destination of the requested transportation service, a request time, or the like.
  • terminal device 140 may be associated with the same transportation service platform to which service vehicle 120 and/or terminal device 110 register.
  • user 142 may use terminal device 140 (e.g., via communication with server 130) to use transportation service provided by the transportation service platform (e.g., a rider uses a smart phone to request transportation service, a driver uses a smart phone to provide
  • Terminal device 140 may be connected to terminal device 110 via a direct link or through a network, such as a Wireless Local Area Network (WLAN), a Wide Area Network (WAN), wireless networks such as radio waves, a cellular network, a satellite communication network, and/or a local or short-range wireless network (e.g., BluetoothTM or near-field communication) for exchanging transportation service-related information.
  • a network such as a Wireless Local Area Network (WLAN), a Wide Area Network (WAN), wireless networks such as radio waves, a cellular network, a satellite communication network, and/or a local or short-range wireless network (e.g., BluetoothTM or near-field communication) for exchanging transportation service-related information.
  • WLAN Wireless Local Area Network
  • WAN Wide Area Network
  • wireless networks such as radio waves, a cellular network, a satellite communication network, and/or a local or short-range wireless network (e.g., BluetoothTM or near-field communication) for exchanging transportation service-related information.
  • BluetoothTM BluetoothTM or near-field
  • terminal devices 110 and/or 140 may include any suitable devices that can interact with users (e.g., service provider 120 and/or user 142), communicate with server 130 (e.g., transmitting user data including, for example, identification information, to server 130 and/or receive authentication information from server 130), and/or communicate with each other (e.g., by establishing a direct link or through a network, as described above).
  • terminal devices 110 and/or 140 may be standalone devices or integrated with another device, e.g., a vehicle, a mobile phone, a wearable device, a camera, a smart phone, a tablet, a computer, or the like. It is contemplated that terminal devices 110 and/or 140 may be any kind of electronic devices or equivalent structures equipped with a suitable interface module that enables terminal devices 110 and/or 140 to communicate with each other and/or with server 130.
  • service vehicle 120 may be a vehicle configured to provide transportation services. It is contemplated that service vehicle 120 may be an electric vehicle, a fuel cell vehicle, a hybrid vehicle, or a conventional internal combustion engine vehicle. Service vehicle 120 may have a body and at least one wheel. The body may be of any body style, such as a sports vehicle, a coupe, a sedan, a pick-up truck, a station wagon, a sports utility vehicle (SUV), a minivan, or a conversion van. In some embodiments, service vehicle 120 may include a pair of front wheels and a pair of rear wheels. However, it is contemplated that service vehicle 120 may have more or less wheels or equivalent structures that enable service vehicle 120 to move around. Service vehicle 120 may be configured to be all wheel drive (AWD), front wheel drive (FWR), or rear wheel drive (RWD). In some examples of service vehicle 120 may be configured to be all wheel drive (AWD), front wheel drive (FWR), or rear wheel drive (RWD). In some examples of service vehicle 120 may be configured to be all wheel drive (AWD
  • service vehicle 120 may be configured to be operated by an operator occupying the vehicle, remotely controlled, and/or autonomous.
  • server 130 may be a cloud server (as illustrated in FIG. 1), a virtual server, a distributed server, or any other suitable computing device. Server 130 may also include a general-purpose server, or a proprietary device specially designed for device fingerprint determination ⁇ It is contemplated that, server 130 can be a stand-alone system (e.g., a server) or an integrated component of a stand-alone server. In some embodiments, server 130 may determine whether to authenticate terminal device 110 based on fingerprint information received from terminal device 110. For example, server 130 may determine if the fingerprint received from terminal device 110 or a fingerprint determined based on data received from terminal device 110 matches a reference fingerprint.
  • server 130 may generate an authentication to authenticate terminal device 110 (e.g., if the fingerprint does match the reference fingerprint) or deny authentication (e.g., if the fingerprint does not match the reference fingerprint). Server 130 may transmit the authentication or denial to terminal device 110.
  • FIG. 2 illustrates a block diagram of system 100, according to embodiments of the disclosure.
  • terminal device 110 may transmit user data (not shown) including, for example, identification information of terminal device 110 or fingerprint information to server 130 to request authentication.
  • Server 130 may be configured to determine a terminal device fingerprint of terminal device 110 based on the received user data and compare the fingerprint with a pre-stored reference fingerprint to determine whether to authenticate terminal device 110. If, for example, the fingerprint matches the reference fingerprint, server 130 may authenticate terminal device 110.
  • terminal device 110 may receive authorization information 201 from server 130 after server 130 authenticates terminal device 110.
  • terminal device 110 may act as an extension of server 130 to determine fingerprint information of other terminal devices, such as terminal device 140.
  • Terminal device 110 may transmit a message (e.g., message 205) including a determined terminal device fingerprint to server 130.
  • terminal device 110 may receive user data 203 from terminal device 140and determine the fingerprint of terminal device 140 based on the received user data 203.
  • terminal device 110 may include a communication interface 202, a processor 204, a memory 206, and a storage 208.
  • terminal device 110 may have different modules in a single device, such as an integrated circuit (IC) chip (implemented as an application-specific integrated circuit (ASIC) or a field-programmable gate array (FPGA)), or separate devices with dedicated functions.
  • IC integrated circuit
  • ASIC application-specific integrated circuit
  • FPGA field-programmable gate array
  • one or more function blocks of terminal device 110 may be implemented in association with a cloud computing environment. For example, certain computational and/or storage tasks may be performed jointly by terminal device 110 and a remote server, such as server 130.
  • Components of terminal device 110 may be in an integrated device or arranged in a distributed manner but communicate with each other through direct links or one or more networks (not shown).
  • Communication interface 202 may send data to and receive data from components such as terminal device 140 and server 130 via communication cables, a Wireless Local Area Network (WLAN), a Wide Area Network (WAN), wireless networks such as radio waves, a cellular network, satellite communication links, and/or a local or short-range wireless network (e.g., BluetoothTM), or other communication methods.
  • communication interface 202 can be an Integrated Services Digital Network (ISDN) card, a cable modem, a satellite modem, or a modem to provide a data communication connection.
  • ISDN Integrated Services Digital Network
  • communication interface 202 can be a local area network (LAN) card to provide a data communication connection to a compatible LAN.
  • Wireless links can also be implemented by communication interface 202.
  • communication interface 202 can send and receive electrical, electromagnetic or optical signals that carry digital data streams representing various types of information via a wireless network.
  • communication interface 202 may receive data such as authentication information 201 from server 130 as well as user data 203 from terminal device 140. In some embodiments, communication interface 202 may also transmit messages (e.g., message 205) to server 130. In some embodiments, message 205 may include terminal device fingerprint of terminal device 140 determined by terminal device 110 based on user data 203 received from terminal device 140.
  • communication interface 202 may further provide any received data to memory 206 / storage 208 for storage or to processor 204 for processing.
  • Communication interface 202 may also send terminal device fingerprint (e.g., included in message 205) determined by processor 204 based on user data 203 to server 130, or any remote device via a network.
  • terminal device fingerprint e.g., included in message 205
  • Processor 204 may include any appropriate type of general-purpose or special- purpose microprocessor, digital signal processor, or microcontroller. Processor 204 may be configured as a separate processor module dedicated to determining terminal device fingerprint of a terminal device in transportation services. Alternatively, processor 204 may be configured as a shared processor module for performing other functions unrelated to terminal device fingerprint determination.
  • processor 204 may include multiple modules, such as an authentication unit 210, user data analysis unit 212, and the like. These modules (and any corresponding sub-modules or sub-units) can be hardware units (e.g., portions of an integrated circuit) of processor 204 designed for use with other components or software units implemented by processor 204 through executing at least part of a program.
  • the program may be stored on a computer-readable medium, and when executed by processor 204, it may perform one or more functions disclosed herein.
  • FIG. 2 shows authentication unit 210 and user data analysis unit 212 both within one processor 204, it is contemplated that these units may be distributed among multiple processors located close to or remotely with each other.
  • authentication unit 210 may generate identification information indicating the identity of terminal device 110 and transmit the identification information to server 130 for authentication purpose through communication interface 202.
  • server 130 may determine a terminal device fingerprint of terminal device 110 such as BluetoothTM fingerprint, International Mobile Equipment Identity (IMEI) of terminal device 110, or the like. Based on the determined terminal device fingerprint, server 130 may be configured to compare the determined terminal device fingerprint of terminal device 110 with a reference terminal device fingerprint that is
  • the terminal device fingerprint may be associated with a phone number, a BluetoothTM fingerprint, an International Mobile Equipment Identity (IMEI), or any other information indicating an identity of the terminal device.
  • the reference terminal device fingerprint of terminal device 110 may be acquired any time before terminal device 110 initiates an authentication process.
  • a BluetoothTM fingerprint reader or scanner may be used to determine the BluetoothTM fingerprint of terminal device 110 when terminal device 120 is registered for participating transportation services (e.g., as a rider or service provider). The BluetoothTM fingerprint reader or scanner may transmit the determined BluetoothTM fingerprint to server 130 and store the fingerprint in the storage of server 130 as a reference terminal device fingerprint for authentication purposes.
  • the reference fingerprint of terminal device 110 may also be acquired by another authenticated terminal device such as a terminal device similar to terminal device 110.
  • the reference fingerprint of terminal device 110 may be determined and transmit to server 130 by another authenticated terminal device through a similar process as the fingerprint determination process disclosed herein.
  • the fingerprint of terminal device 110 may be determined by service vehicle 120 (e.g., by a computing system integrated or otherwise associated with service vehicle 120) based on, for example, establishing communication links such as
  • the determined fingerprint may be encrypted and sent back to terminal device 110, which may in turn transmit the encrypted fingerprint to server 130.
  • Server 130 may first decrypt the encrypted fingerprint, and then compare the fingerprint with the reference fingerprint to determine whether the authenticate terminal device 110.
  • Terminal device 110 may determine device fingerprints of other terminal devices, such as terminal device 140, after receiving authentication 201 from server 130.
  • user data analysis unit 212 may receive and analyze user data 203 to extract relevant information for determining terminal device fingerprint based on user data 203. It is noted that user data analysis unit 212 may receive and analyze user data 203 prior to, simultaneously, or after terminal device 110 is authenticated.
  • user data 203 may include identification information of terminal device 140. Based on the identification information, user data analysis unit 212 may determine a terminal device fingerprint of terminal device 140 such as BluetoothTM fingerprint, International Mobile Equipment Identity (IMEI) of terminal device 110, or the like.
  • IMEI International Mobile Equipment Identity
  • user data analysis unit 212 may generate a message (e.g., message 205) including the determined terminal device fingerprint and transmit the message to server 130.
  • the terminal device fingerprint may be associated with a phone number, a BluetoothTM fingerprint, an International Mobile Equipment Identity (IMEI), or any other information indicating an identity of terminal device 140.
  • IMEI International Mobile Equipment Identity
  • the determined fingerprint may be used as a reference terminal device fingerprint for later authentication purpose (e.g., server 130 may use the received terminal device fingerprint to later authenticate terminal device 140 when terminal device 140 requests authentication).
  • user data analysis unit 212 may determine terminal device fingerprint of terminal device 140 based on user data 203 transmitted via communication established between terminal device 110 and terminal device 140.
  • communication interface 202 may establish a connection with terminal device 140.
  • User data analysis unit 212 may determine the terminal device fingerprint of terminal device 140 based on information exchanged with terminal device 140 (e.g., user data 203) through the connection.
  • user data analysis unit 212 may extract the information indicating the identity of terminal device 140.
  • communication interface 202 may establish a BluetoothTM communication with terminal device 140.
  • User data analysis unit 212 may determine a
  • BluetoothTM fingerprint of terminal device 140 based on the BluetoothTM signals received from terminal device 140.
  • user data 203 may include information indicating the International Mobile Equipment Identity (IMEI) of terminal device 140.
  • IMEI International Mobile Equipment Identity
  • User data analysis unit 212 may determine the terminal device fingerprint (e.g., IMEI in this scenario) of terminal device 140 based on user data 203.
  • Memory 206 and storage 208 may include any appropriate type of mass storage provided to store any type of information that processor 204 may need to operate.
  • Memory 206 and storage 208 may be volatile or non-volatile, magnetic, semiconductor-based, tape-based, optical, removable, non-removable, or other type of storage device or tangible (i.e., non- transitory) computer-readable medium including, but not limited to, a ROM, a flash memory, a dynamic RAM, and a static RAM.
  • Memory 206 and/or storage 208 may be configured to store one or more computer programs that may be executed by processor 204 to perform fingerprint determination disclosed herein.
  • memory 206 and/or storage 208 may be configured to store program(s) that may be executed by processor 204 to determine terminal device fingerprints based on user data received from a terminal device.
  • Memory 206 and/or storage 208 may be further configured to store information and data used by processor 204.
  • memory 206 and/or storage 208 may be configured to store various types of data (e.g., user data, terminal device fingerprint data, authentication data, etc.) transmitted by terminal device 140 and/or server 130.
  • the various types of data may be stored permanently, removed periodically, or disregarded immediately after each frame of data is processed.
  • FIG. 3 illustrates a flowchart of an exemplary method for device fingerprint determination in a transportation service, according to embodiments of the disclosure.
  • method 300 may be performed by terminal device 110. It is noted that method 300 is not limited to that exemplary embodiment and may be implemented jointly by terminal device 110, terminal device 140, and/or server 130.
  • Method 300 may include steps S302-S314 as described below. It is to be appreciated that some of the steps may be optional to perform the disclosure provided herein. Further, some of the steps may be performed simultaneously, or in a different order than shown in FIG. 3.
  • terminal device 110 may transmit an authentication request to server 130 for authentication purpose.
  • the authentication request may include identification information and/or fingerprint information of terminal device 110.
  • terminal device 110 may be registered with a transportation service platform and the fingerprint of terminal device 110 may have been obtained and stored in server 130.
  • terminal device 110 may be connected to server 130 via a direct link or through a network to transmit the authentication request.
  • terminal device 110 may receive authentication information from server 130 authenticating terminal device 110.
  • server 130 may determine a terminal device fingerprint of terminal device 110 based on the data transmitted to server 130.
  • server 130 may have an individual module or a module built-in another device that can extract the information indicating the identity of terminal device 110.
  • Server 130 may also authenticate terminal device 110 by comparing the determined terminal device fingerprint with a reference terminal device fingerprint.
  • the reference fingerprint may be acquired any time before terminal device 110 initiates an authentication process.
  • a BluetoothTM fingerprint reader or scanner may be used to determine the BluetoothTM fingerprint of terminal device 110 when terminal device 110 is registered to facilitate transportation services. The BluetoothTM fingerprint reader or scanner may transmit the determined
  • BluetoothTM fingerprint to server 130, which may store the fingerprint as the reference fingerprint of terminal device 110 for authentication purposes.
  • server 130 may use the rise time signature of terminal device 110 to match the reference fingerprint.
  • physical layer fingerprints physical layer authentication solutions may be used to match the fingerprint of terminal device 110 and the reference fingerprint.
  • terminal device 110 may receive from server 130 an authentication authenticating terminal device 110, which may then determine fingerprint information of other terminal devices (e.g., terminal device 140). Otherwise, terminal device 110 may receive a notice indicating that the terminal device fingerprint dose not match the reference fingerprint and server 130 may thus deny terminal device 110’s authentication request.
  • the transportation service platform e.g., via server 130
  • may take further actions e.g., initiating a fraud alert, disfranchising the license of the fraudsters, contacting third party authorities such as local police stations, etc.
  • terminal device 110 may perform fingerprint determination operations to determine fingerprint information of another terminal device, such as terminal device 140.
  • terminal device 110 may establish a communication link between terminal device 110 and another terminal device whose terminal device fingerprint is to be determined (e.g., terminal device 140).
  • terminal device 140 may be associated with user 142, who may use the transportation service to which terminal device 110 is registered.
  • terminal device 110 may receive user data 203 from terminal device 140.
  • user data 203 may include identification information of terminal device 140.
  • terminal device 110 may determine a terminal device fingerprint of terminal device 140 based on the received user data.
  • the terminal device fingerprint may be associated with a phone number, a BluetoothTM fingerprint, an International Mobile Equipment Identity (IMEI), or any other information indicating an identity of the terminal device.
  • terminal device 110 may establish a BluetoothTM communication link with terminal device 140 and determine the BluetoothTM fingerprint of terminal device 140 based on the BluetoothTM signals received from terminal device 140.
  • IMEI International Mobile Equipment Identity
  • terminal device 110 may generate a message including the determined fingerprint of terminal device 140.
  • the message may include an encrypted version of the determined fingerprint for transmission to server 130.
  • terminal device 110 may transmit the message to a server associated with the transportation service platform (e.g., server 130).
  • server 130 may store the determined fingerprint as the reference fingerprint of terminal device 140.
  • terminal device 140 may later request authentication from server 130, for example, for determining another terminal device’s fingerprint.
  • the determined fingerprint of terminal device 140 may be used as the reference fingerprint for authenticating terminal device 140.
  • FIG. 4 is a flow chart of another exemplary method 400 for determining device fingerprints, according to embodiments of the disclosure.
  • method 400 may be performed by terminal device 110. It is noted that method 400 is not limited to that exemplary embodiment and may be implemented jointly by terminal device 110, terminal device 140, and/or server 130.
  • Method 400 may include steps S402-S414 as described below. It is to be appreciated that some of the steps may be optional to perform the disclosure provided herein. Further, some of the steps may be performed simultaneously, or in a different order than shown in FIG. 4.
  • terminal device 110 may establish a communication link between terminal device 110 and another terminal device whose terminal device fingerprint is to be determined (e.g., terminal device 140).
  • Step S402 is similar to step S306.
  • terminal device 110 may receive user data 203 from terminal device 140, similar to step S308.
  • terminal device 110 may request authentication from server 130 by transmitting an authentication request to server 130, similar to step S302.
  • terminal device 110 may determine if the authentication is received.
  • server 130 may determine a terminal device fingerprint of terminal device 110 based on the data transmitted to server 130, similar to operations performed by server 130 in connection with the description of step S304. If terminal device 110 does not receive the authentication, method 400 loops back to step S406, where terminal device 110 may transmit another authentication request to server 130. If terminal device 110 receives the authentication, method 400 proceeds to step S410, where terminal device 110 may determine a fingerprint of terminal device 140. Step S410 is similar to step S310. In step S412, terminal device 110 may generate a message including the determined fingerprint. Step S412 is similar to step S312. In step S414, terminal device 110 may transmit the message to server 130. Step S414 is similar to step S314.
  • Embodiments of the present disclosure provide a secure method of acquiring device fingerprint information that is not available in current systems.
  • Systems and methods disclosed herein enable a first user (e.g., a transportation service provider or a rider) to use his/her terminal device to securely determine device fingerprint information of another terminal device (e.g., associated with a second user) after the first user’s terminal device has been properly authenticate.
  • the second user e.g., a rider or a service provider
  • the disclosed systems and methods improve the convenience and efficiency of acquiring device fingerprint information, which is relatively difficult to tamper, and thus increasing the overall security of using the transportation services.
  • Another aspect of the disclosure is directed to a non-transitory computer-readable medium storing instructions which, when executed, cause one or more processors to perform the methods, as discussed above.
  • the computer-readable medium may include volatile or non volatile, magnetic, semiconductor, tape, optical, removable, non-removable, or other types of computer-readable medium or computer-readable storage devices.
  • the computer- readable medium may be the storage device or the memory module having the computer instructions stored thereon, as disclosed.
  • the computer-readable medium may be a disc or a flash drive having the computer instructions stored thereon.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Theoretical Computer Science (AREA)
  • Computing Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Computer Hardware Design (AREA)
  • Power Engineering (AREA)
  • Medical Informatics (AREA)
  • General Health & Medical Sciences (AREA)
  • Software Systems (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Health & Medical Sciences (AREA)
  • Telephonic Communication Services (AREA)
  • Alarm Systems (AREA)
  • Collating Specific Patterns (AREA)
  • Position Fixing By Use Of Radio Waves (AREA)

Abstract

Embodiments of the disclosure provide systems and methods for determining fingerprint information of a terminal device in a transportation service. An exemplary system may include a communication interface configured to establish a communication link between first and second terminal devices and receive user data from the first terminal device associated with a user of the transportation service. The communication interface may also be configured to receive authentication information authenticating the second terminal device. The system may also include a memory configured to store the user data and at least one processor coupled to the memory. The at least one processor is configured to determine a first fingerprint of the first terminal device based on the user data after receiving the authentication information authenticating the second terminal device.

Description

SYSTEMS AND METHODS FOR DEVICE FINGERPRINT DETERMINATION IN A
TRANSPORTATION SERVICE
RELATED APPLICATIONS
[001] This application relates to and claims the benefits of priority to U.S. Patent Application Nos. 16/237,043, 16/237,016, and 16/236,970, all filed December 31, 2018. The entire contents of each of the above-identified applications are incorporated herein by reference.
TECHNICAL FIELD
[002] The present disclosure relates to systems and methods for device fingerprint determination in a transportation service, and more particularly to, systems and methods for determining fingerprint information of a terminal device in a transportation service using an authenticated terminal device.
BACKGROUND
[003] Terminal device frauds have negative impact on the fairness and efficiency of transportation services such as ride-hailing (also referred to as ride-sharing) services. For example, transportation service providers (e.g., drivers) may tamper user terminal devices to create fake trips, thus tricking the transportation service platform and make unjustified profits. Fraudsters may also run faked ride-sharing trips to gain awards for accomplishing certain amount of transactions. As each faked mobile device can be assigned to a phone number, using Short Message Service (SMS) to verify is not enough to prevent such fraud activities.
[004] User registration may alleviate the fraud activities to some extent. Existing user registration methods collect basic user information such as user name, phone number, and so on. That information is easy to fake and thus is not enough to prevent fraud activities. On the other hand, although terminal device related information such as Bluetooth™ fingerprint of the user’s terminal device is relatively hard to fake, the information is also difficult to acquire (e.g., a user may need to go to a certain location to have his/her terminal device scanned to register the terminal device’s Bluetooth™ fingerprint). The inconveniency may deter the user from choosing to use the transportation service.
[005] Embodiments of the disclosure address the above problems by methods and systems for fingerprint determination in a transportation service using authenticated terminal devices to enhance registering accuracy and efficiency.
SUMMARY
[006] In one aspect, embodiments of the disclosure provide a system for determining fingerprint information of a terminal device in a transportation service. An exemplary system may include a communication interface configured to establish a communication link between first and second terminal devices and receive user data from the first terminal device associated with a user of the transportation service. The communication interface may also be configured to receive authentication information authenticating the second terminal device. The system may also include a memory configured to store the user data and at least one processor coupled to the memory. The at least one processor may be configured to determine a first fingerprint of the first terminal device based on the user data after receiving the authentication information
authenticating the second terminal device.
[007] In another aspect, embodiments of the disclosure also provide a method for determining fingerprint information of a terminal device in a transportation service. An exemplary method may include a establishing a communication link between first and second terminal devices and receiving user data from the first terminal device associated with a user of the transportation service. The method may also include receiving authentication information authenticating the second terminal device and determining a first fingerprint of the first terminal device based on the user data after receiving the authentication information authenticating the second terminal device.
[008] In a further aspect, embodiments of the disclosure further provide a non-transitory computer-readable medium storing instruction that, when executed by one or more processors, cause the one or more processors to perform a method for determining fingerprint information of a terminal device in a transportation service. The method may include establishing a
communication link between first and second terminal devices and receiving user data from the first terminal device associated with a user of the transportation service. The method may also include receiving authentication information authenticating the second terminal device and determining a first fingerprint of the first terminal device based on the user data after receiving the authentication information authenticating the second terminal device.
[009] It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the invention, as claimed.
BRIEF DESCRIPTION OF THE DRAWINGS
[010] FIG. 1 illustrates a schematic diagram of an exemplary device fingerprint determination system in a transportation service, according to embodiments of the disclosure.
[Oil] FIG. 2 illustrates a block diagram of an exemplary fingerprint determining system, according to embodiments of the disclosure.
[012] FIG. 3 illustrates a flowchart of an exemplary method for fingerprint determination in a transportation service, according to embodiments of the disclosure.
[013] FIG. 4 illustrates a flowchart of another exemplary method for fingerprint determination in a transportation service, according to embodiments of the disclosure
DETAILED DESCRIPTION
[014] Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. Wherever possible, the same reference numbers will be used throughout the drawings to refer to the same or like parts.
[015] FIG. 1 illustrates a schematic diagram of an exemplary device fingerprint determination system 100 in a transportation service, according to embodiments of the disclosure. As shown in FIG. 1, a service vehicle 120 associated with a service provider 122 may be registered to a transportation service platform (e.g., a ride-hailing or ride-sharing service platform) to provide transportation service to passengers/riders. A terminal device 110 associated with service provider 120 may also be registered. For example, a device fingerprint (e.g., unique information identifying a terminal device, hereinafter simply referred to as “fingerprint”) of terminal device 110 may be acquired and stored by the transportation service platform as part of the registration process. The fingerprint may be used as a reference fingerprint in authentication, authorization, verification, or other terminal device identity related processes. In some embodiments, the fingerprint of terminal device 110 may be stored in a server 130, which may be part of the transportation service platform. Server 130 may authenticate terminal device 110 based on the stored reference fingerprint.
[016] In some embodiments, terminal device 110 may be built in, integrated into, installed on, or otherwise associated with service vehicle 120. For example, terminal device 110 may be part of service vehicle 120’s built-in system that can be configured to perform fingerprint determination functions disclosed herein (e.g., a built-in computer system). In another example, terminal device 110 may be installed as an add-on system after service vehicle 120 is registered to the transportation service platform. In some embodiments, terminal device 110 may be a stand-alone device separate from service vehicle 120. For example, terminal device 110 may be a mobile device used by service provider 122 that facilitates provision of transportation services.
[017] After registered with a transportation service platform, terminal device 110 may receive authentication information from server 130 (e.g., a cloud server providing computational power, storage space, and/or communication capacity to the transportation service platform).
For example, terminal device 110 may be equipped with a communication interface to communicate with server 130, including transmitting data to server 130 and receiving authentication information from server 130. In some embodiments, service vehicle 120 may be equipped with one or more communication interfaces to receive information from and/or transmit information to server 130. In some embodiments, information transmitted from terminal device 110/120 to server 130 may include fingerprint information or may be used to determine the fingerprint of terminal device 110 by server 130. Based on the fingerprint, server 130 may determine whether to authenticate terminal device 110. For example, when server 130 determines to authenticate terminal device 110, server 130 may transmit an authentication back to terminal device 110.
[018] Terminal device 110 may communicate with a terminal device 140 associated with a user 142, either directly or through server 130, to facilitate various functions such as receiving user data including, for example, identification information; transmitting and/or receiving transportation service requests; making and/or receiving payment, or the like. A transportation service request may include a current location of the passenger, a destination of the requested transportation service, a request time, or the like.
[019] In some embodiments, terminal device 140 may be associated with the same transportation service platform to which service vehicle 120 and/or terminal device 110 register. For example, user 142 may use terminal device 140 (e.g., via communication with server 130) to use transportation service provided by the transportation service platform (e.g., a rider uses a smart phone to request transportation service, a driver uses a smart phone to provide
transportation service, etc.).
[020] Terminal device 140 may be connected to terminal device 110 via a direct link or through a network, such as a Wireless Local Area Network (WLAN), a Wide Area Network (WAN), wireless networks such as radio waves, a cellular network, a satellite communication network, and/or a local or short-range wireless network (e.g., Bluetooth™ or near-field communication) for exchanging transportation service-related information.
[021] Consistent with some embodiments, terminal devices 110 and/or 140 may include any suitable devices that can interact with users (e.g., service provider 120 and/or user 142), communicate with server 130 (e.g., transmitting user data including, for example, identification information, to server 130 and/or receive authentication information from server 130), and/or communicate with each other (e.g., by establishing a direct link or through a network, as described above). In some embodiments, terminal devices 110 and/or 140 may be standalone devices or integrated with another device, e.g., a vehicle, a mobile phone, a wearable device, a camera, a smart phone, a tablet, a computer, or the like. It is contemplated that terminal devices 110 and/or 140 may be any kind of electronic devices or equivalent structures equipped with a suitable interface module that enables terminal devices 110 and/or 140 to communicate with each other and/or with server 130.
[022] Consistent with some embodiments, service vehicle 120 may be a vehicle configured to provide transportation services. It is contemplated that service vehicle 120 may be an electric vehicle, a fuel cell vehicle, a hybrid vehicle, or a conventional internal combustion engine vehicle. Service vehicle 120 may have a body and at least one wheel. The body may be of any body style, such as a sports vehicle, a coupe, a sedan, a pick-up truck, a station wagon, a sports utility vehicle (SUV), a minivan, or a conversion van. In some embodiments, service vehicle 120 may include a pair of front wheels and a pair of rear wheels. However, it is contemplated that service vehicle 120 may have more or less wheels or equivalent structures that enable service vehicle 120 to move around. Service vehicle 120 may be configured to be all wheel drive (AWD), front wheel drive (FWR), or rear wheel drive (RWD). In some
embodiments, service vehicle 120 may be configured to be operated by an operator occupying the vehicle, remotely controlled, and/or autonomous.
[023] In some embodiments, server 130 may be a cloud server (as illustrated in FIG. 1), a virtual server, a distributed server, or any other suitable computing device. Server 130 may also include a general-purpose server, or a proprietary device specially designed for device fingerprint determination· It is contemplated that, server 130 can be a stand-alone system (e.g., a server) or an integrated component of a stand-alone server. In some embodiments, server 130 may determine whether to authenticate terminal device 110 based on fingerprint information received from terminal device 110. For example, server 130 may determine if the fingerprint received from terminal device 110 or a fingerprint determined based on data received from terminal device 110 matches a reference fingerprint. Based on the matching result, server 130 may generate an authentication to authenticate terminal device 110 (e.g., if the fingerprint does match the reference fingerprint) or deny authentication (e.g., if the fingerprint does not match the reference fingerprint). Server 130 may transmit the authentication or denial to terminal device 110.
[024] FIG. 2 illustrates a block diagram of system 100, according to embodiments of the disclosure. Consistent with some embodiments, terminal device 110 may transmit user data (not shown) including, for example, identification information of terminal device 110 or fingerprint information to server 130 to request authentication. Server 130 may be configured to determine a terminal device fingerprint of terminal device 110 based on the received user data and compare the fingerprint with a pre-stored reference fingerprint to determine whether to authenticate terminal device 110. If, for example, the fingerprint matches the reference fingerprint, server 130 may authenticate terminal device 110. As a result, terminal device 110 may receive authorization information 201 from server 130 after server 130 authenticates terminal device 110. After authenticated, terminal device 110 may act as an extension of server 130 to determine fingerprint information of other terminal devices, such as terminal device 140. Terminal device 110 may transmit a message (e.g., message 205) including a determined terminal device fingerprint to server 130. For example, terminal device 110 may receive user data 203 from terminal device 140and determine the fingerprint of terminal device 140 based on the received user data 203.
[025] In some embodiments, as shown in FIG. 2, terminal device 110 may include a communication interface 202, a processor 204, a memory 206, and a storage 208. In some embodiments, terminal device 110 may have different modules in a single device, such as an integrated circuit (IC) chip (implemented as an application-specific integrated circuit (ASIC) or a field-programmable gate array (FPGA)), or separate devices with dedicated functions. In some embodiments, one or more function blocks of terminal device 110 may be implemented in association with a cloud computing environment. For example, certain computational and/or storage tasks may be performed jointly by terminal device 110 and a remote server, such as server 130. Components of terminal device 110 may be in an integrated device or arranged in a distributed manner but communicate with each other through direct links or one or more networks (not shown).
[026] Communication interface 202 may send data to and receive data from components such as terminal device 140 and server 130 via communication cables, a Wireless Local Area Network (WLAN), a Wide Area Network (WAN), wireless networks such as radio waves, a cellular network, satellite communication links, and/or a local or short-range wireless network (e.g., Bluetooth™), or other communication methods. In some embodiments, communication interface 202 can be an Integrated Services Digital Network (ISDN) card, a cable modem, a satellite modem, or a modem to provide a data communication connection. As another example, communication interface 202 can be a local area network (LAN) card to provide a data communication connection to a compatible LAN. Wireless links can also be implemented by communication interface 202. In such an implementation, communication interface 202 can send and receive electrical, electromagnetic or optical signals that carry digital data streams representing various types of information via a wireless network.
[027] Consistent with some embodiments, communication interface 202 may receive data such as authentication information 201 from server 130 as well as user data 203 from terminal device 140. In some embodiments, communication interface 202 may also transmit messages (e.g., message 205) to server 130. In some embodiments, message 205 may include terminal device fingerprint of terminal device 140 determined by terminal device 110 based on user data 203 received from terminal device 140.
[028] In some embodiments, communication interface 202 may further provide any received data to memory 206 / storage 208 for storage or to processor 204 for processing.
Communication interface 202 may also send terminal device fingerprint (e.g., included in message 205) determined by processor 204 based on user data 203 to server 130, or any remote device via a network.
[029] Processor 204 may include any appropriate type of general-purpose or special- purpose microprocessor, digital signal processor, or microcontroller. Processor 204 may be configured as a separate processor module dedicated to determining terminal device fingerprint of a terminal device in transportation services. Alternatively, processor 204 may be configured as a shared processor module for performing other functions unrelated to terminal device fingerprint determination.
[030] As shown in FIG. 2, processor 204 may include multiple modules, such as an authentication unit 210, user data analysis unit 212, and the like. These modules (and any corresponding sub-modules or sub-units) can be hardware units (e.g., portions of an integrated circuit) of processor 204 designed for use with other components or software units implemented by processor 204 through executing at least part of a program. The program may be stored on a computer-readable medium, and when executed by processor 204, it may perform one or more functions disclosed herein. Although FIG. 2 shows authentication unit 210 and user data analysis unit 212 both within one processor 204, it is contemplated that these units may be distributed among multiple processors located close to or remotely with each other.
[031] In some embodiments, authentication unit 210 may generate identification information indicating the identity of terminal device 110 and transmit the identification information to server 130 for authentication purpose through communication interface 202. In some embodiments, based on the identification information, server 130 may determine a terminal device fingerprint of terminal device 110 such as Bluetooth™ fingerprint, International Mobile Equipment Identity (IMEI) of terminal device 110, or the like. Based on the determined terminal device fingerprint, server 130 may be configured to compare the determined terminal device fingerprint of terminal device 110 with a reference terminal device fingerprint that is
predetermined and stored in a storage unit of server 130. In some embodiments, the terminal device fingerprint may be associated with a phone number, a Bluetooth™ fingerprint, an International Mobile Equipment Identity (IMEI), or any other information indicating an identity of the terminal device. In some embodiments, the reference terminal device fingerprint of terminal device 110 may be acquired any time before terminal device 110 initiates an authentication process. For example, a Bluetooth™ fingerprint reader or scanner may be used to determine the Bluetooth™ fingerprint of terminal device 110 when terminal device 120 is registered for participating transportation services (e.g., as a rider or service provider). The Bluetooth™ fingerprint reader or scanner may transmit the determined Bluetooth™ fingerprint to server 130 and store the fingerprint in the storage of server 130 as a reference terminal device fingerprint for authentication purposes. In some other embodiments, the reference fingerprint of terminal device 110 may also be acquired by another authenticated terminal device such as a terminal device similar to terminal device 110. For example, the reference fingerprint of terminal device 110 may be determined and transmit to server 130 by another authenticated terminal device through a similar process as the fingerprint determination process disclosed herein.
[032] In some embodiments, the fingerprint of terminal device 110 may be determined by service vehicle 120 (e.g., by a computing system integrated or otherwise associated with service vehicle 120) based on, for example, establishing communication links such as
Bluetooth™ connections between terminal device 110 and service vehicle 120. The determined fingerprint may be encrypted and sent back to terminal device 110, which may in turn transmit the encrypted fingerprint to server 130. Server 130 may first decrypt the encrypted fingerprint, and then compare the fingerprint with the reference fingerprint to determine whether the authenticate terminal device 110.
[033] Terminal device 110 may determine device fingerprints of other terminal devices, such as terminal device 140, after receiving authentication 201 from server 130. For example, user data analysis unit 212 may receive and analyze user data 203 to extract relevant information for determining terminal device fingerprint based on user data 203. It is noted that user data analysis unit 212 may receive and analyze user data 203 prior to, simultaneously, or after terminal device 110 is authenticated. In some embodiments, user data 203 may include identification information of terminal device 140. Based on the identification information, user data analysis unit 212 may determine a terminal device fingerprint of terminal device 140 such as Bluetooth™ fingerprint, International Mobile Equipment Identity (IMEI) of terminal device 110, or the like. Based on the determined terminal device fingerprint, user data analysis unit 212 may generate a message (e.g., message 205) including the determined terminal device fingerprint and transmit the message to server 130. In some embodiments, the terminal device fingerprint may be associated with a phone number, a Bluetooth™ fingerprint, an International Mobile Equipment Identity (IMEI), or any other information indicating an identity of terminal device 140. In some embodiments, the determined fingerprint may be used as a reference terminal device fingerprint for later authentication purpose (e.g., server 130 may use the received terminal device fingerprint to later authenticate terminal device 140 when terminal device 140 requests authentication).
[034] In some embodiments, user data analysis unit 212 may determine terminal device fingerprint of terminal device 140 based on user data 203 transmitted via communication established between terminal device 110 and terminal device 140. For example, communication interface 202 may establish a connection with terminal device 140. User data analysis unit 212 may determine the terminal device fingerprint of terminal device 140 based on information exchanged with terminal device 140 (e.g., user data 203) through the connection. In some embodiments, user data analysis unit 212 may extract the information indicating the identity of terminal device 140. For example, communication interface 202 may establish a Bluetooth™ communication with terminal device 140. User data analysis unit 212 may determine a
Bluetooth™ fingerprint of terminal device 140 based on the Bluetooth™ signals received from terminal device 140. In another example, user data 203 may include information indicating the International Mobile Equipment Identity (IMEI) of terminal device 140. User data analysis unit 212 may determine the terminal device fingerprint (e.g., IMEI in this scenario) of terminal device 140 based on user data 203.
[035] Memory 206 and storage 208 may include any appropriate type of mass storage provided to store any type of information that processor 204 may need to operate. Memory 206 and storage 208 may be volatile or non-volatile, magnetic, semiconductor-based, tape-based, optical, removable, non-removable, or other type of storage device or tangible (i.e., non- transitory) computer-readable medium including, but not limited to, a ROM, a flash memory, a dynamic RAM, and a static RAM. Memory 206 and/or storage 208 may be configured to store one or more computer programs that may be executed by processor 204 to perform fingerprint determination disclosed herein. For example, memory 206 and/or storage 208 may be configured to store program(s) that may be executed by processor 204 to determine terminal device fingerprints based on user data received from a terminal device.
[036] Memory 206 and/or storage 208 may be further configured to store information and data used by processor 204. For instance, memory 206 and/or storage 208 may be configured to store various types of data (e.g., user data, terminal device fingerprint data, authentication data, etc.) transmitted by terminal device 140 and/or server 130. The various types of data may be stored permanently, removed periodically, or disregarded immediately after each frame of data is processed. [037] FIG. 3 illustrates a flowchart of an exemplary method for device fingerprint determination in a transportation service, according to embodiments of the disclosure. In some embodiments, method 300 may be performed by terminal device 110. It is noted that method 300 is not limited to that exemplary embodiment and may be implemented jointly by terminal device 110, terminal device 140, and/or server 130. Method 300 may include steps S302-S314 as described below. It is to be appreciated that some of the steps may be optional to perform the disclosure provided herein. Further, some of the steps may be performed simultaneously, or in a different order than shown in FIG. 3.
[038] In step S302, terminal device 110 may transmit an authentication request to server 130 for authentication purpose. For example, the authentication request may include identification information and/or fingerprint information of terminal device 110. As described above, terminal device 110 may be registered with a transportation service platform and the fingerprint of terminal device 110 may have been obtained and stored in server 130. In some embodiments, terminal device 110 may be connected to server 130 via a direct link or through a network to transmit the authentication request.
[039] In step S304, terminal device 110 may receive authentication information from server 130 authenticating terminal device 110. In some embodiment, server 130 may determine a terminal device fingerprint of terminal device 110 based on the data transmitted to server 130. For example, server 130 may have an individual module or a module built-in another device that can extract the information indicating the identity of terminal device 110. Server 130 may also authenticate terminal device 110 by comparing the determined terminal device fingerprint with a reference terminal device fingerprint. In some embodiments, the reference fingerprint may be acquired any time before terminal device 110 initiates an authentication process. For example, a Bluetooth™ fingerprint reader or scanner may be used to determine the Bluetooth™ fingerprint of terminal device 110 when terminal device 110 is registered to facilitate transportation services. The Bluetooth™ fingerprint reader or scanner may transmit the determined
Bluetooth™ fingerprint to server 130, which may store the fingerprint as the reference fingerprint of terminal device 110 for authentication purposes.
[040] In some embodiments, server 130 may use the rise time signature of terminal device 110 to match the reference fingerprint. In some embodiments, physical layer fingerprints (physical layer authentication solutions) may be used to match the fingerprint of terminal device 110 and the reference fingerprint.
[041] In some embodiments, if the determined terminal device fingerprint matches the reference terminal device fingerprint, terminal device 110 may receive from server 130 an authentication authenticating terminal device 110, which may then determine fingerprint information of other terminal devices (e.g., terminal device 140). Otherwise, terminal device 110 may receive a notice indicating that the terminal device fingerprint dose not match the reference fingerprint and server 130 may thus deny terminal device 110’s authentication request. In some embodiments, the transportation service platform (e.g., via server 130) may take further actions (e.g., initiating a fraud alert, disfranchising the license of the fraudsters, contacting third party authorities such as local police stations, etc.) after it is determined that the terminal device fingerprint does not match the reference fingerprint.
[042] After receiving the authentication, in steps S306-310, terminal device 110 may perform fingerprint determination operations to determine fingerprint information of another terminal device, such as terminal device 140. In step S306, terminal device 110 may establish a communication link between terminal device 110 and another terminal device whose terminal device fingerprint is to be determined (e.g., terminal device 140). As described above, terminal device 140 may be associated with user 142, who may use the transportation service to which terminal device 110 is registered. In step S308, terminal device 110 may receive user data 203 from terminal device 140. For example, user data 203 may include identification information of terminal device 140. In step S310, terminal device 110 may determine a terminal device fingerprint of terminal device 140 based on the received user data. In some embodiments, the terminal device fingerprint may be associated with a phone number, a Bluetooth™ fingerprint, an International Mobile Equipment Identity (IMEI), or any other information indicating an identity of the terminal device. For example, terminal device 110 may establish a Bluetooth™ communication link with terminal device 140 and determine the Bluetooth™ fingerprint of terminal device 140 based on the Bluetooth™ signals received from terminal device 140.
[043] In step S312, terminal device 110 may generate a message including the determined fingerprint of terminal device 140. For example, the message may include an encrypted version of the determined fingerprint for transmission to server 130. In step S314, terminal device 110 may transmit the message to a server associated with the transportation service platform (e.g., server 130). In some embodiments, server 130 may store the determined fingerprint as the reference fingerprint of terminal device 140. For example, after receiving the determined fingerprint of terminal device 140, terminal device 140 may later request authentication from server 130, for example, for determining another terminal device’s fingerprint. The determined fingerprint of terminal device 140 may be used as the reference fingerprint for authenticating terminal device 140.
[044] FIG. 4 is a flow chart of another exemplary method 400 for determining device fingerprints, according to embodiments of the disclosure. In some embodiments, method 400 may be performed by terminal device 110. It is noted that method 400 is not limited to that exemplary embodiment and may be implemented jointly by terminal device 110, terminal device 140, and/or server 130. Method 400 may include steps S402-S414 as described below. It is to be appreciated that some of the steps may be optional to perform the disclosure provided herein. Further, some of the steps may be performed simultaneously, or in a different order than shown in FIG. 4.
[045] In step S402, terminal device 110 may establish a communication link between terminal device 110 and another terminal device whose terminal device fingerprint is to be determined (e.g., terminal device 140). Step S402 is similar to step S306. In step S404, terminal device 110 may receive user data 203 from terminal device 140, similar to step S308. In step S406, terminal device 110 may request authentication from server 130 by transmitting an authentication request to server 130, similar to step S302.
[046] In step S408, terminal device 110 may determine if the authentication is received. In some embodiment, server 130 may determine a terminal device fingerprint of terminal device 110 based on the data transmitted to server 130, similar to operations performed by server 130 in connection with the description of step S304. If terminal device 110 does not receive the authentication, method 400 loops back to step S406, where terminal device 110 may transmit another authentication request to server 130. If terminal device 110 receives the authentication, method 400 proceeds to step S410, where terminal device 110 may determine a fingerprint of terminal device 140. Step S410 is similar to step S310. In step S412, terminal device 110 may generate a message including the determined fingerprint. Step S412 is similar to step S312. In step S414, terminal device 110 may transmit the message to server 130. Step S414 is similar to step S314.
[047] Embodiments of the present disclosure provide a secure method of acquiring device fingerprint information that is not available in current systems. Systems and methods disclosed herein enable a first user (e.g., a transportation service provider or a rider) to use his/her terminal device to securely determine device fingerprint information of another terminal device (e.g., associated with a second user) after the first user’s terminal device has been properly authenticate. As a result, the second user (e.g., a rider or a service provider) need not to go to a certain location to have his/her terminal device scanned for fingerprint determination purposes (e.g., as part of the registration process). The disclosed systems and methods improve the convenience and efficiency of acquiring device fingerprint information, which is relatively difficult to tamper, and thus increasing the overall security of using the transportation services. [048] Another aspect of the disclosure is directed to a non-transitory computer-readable medium storing instructions which, when executed, cause one or more processors to perform the methods, as discussed above. The computer-readable medium may include volatile or non volatile, magnetic, semiconductor, tape, optical, removable, non-removable, or other types of computer-readable medium or computer-readable storage devices. For example, the computer- readable medium may be the storage device or the memory module having the computer instructions stored thereon, as disclosed. In some embodiments, the computer-readable medium may be a disc or a flash drive having the computer instructions stored thereon.
[049] It will be apparent to those skilled in the art that various modifications and variations can be made to the disclosed system and related methods. Other embodiments will be apparent to those skilled in the art from consideration of the specification and practice of the disclosed system and related methods.
[050] It is intended that the specification and examples be considered as exemplary only, with a true scope being indicated by the following claims and their equivalents.

Claims

WHAT IS CLAIMED IS:
1. A system for determining fingerprint information of a terminal device in a transportation service, comprising:
a communication interface configured to:
establish a communication link between first and second terminal devices;
receive user data from the first terminal device associated with a user of the transportation service; and
receive authentication information authenticating the second terminal device; a memory configured to store the user data; and
at least one processor coupled to the memory and configured to:
determine a first fingerprint of the first terminal device based on the user data after receiving the authentication information authenticating the second terminal device.
2. The system of claim 1 , wherein the at least one processor is further configured to transmit the first fingerprint to a server.
3. The system of claim 1, wherein the second terminal device is associated with a service vehicle.
4. The system of claim 1, wherein the at least one processor is further configured to: determine a second fingerprint of the second terminal device; and
transmit, via the communication interface, the second fingerprint to a server.
5. The system of claim 4, wherein the authentication information is provided by the server based on matching the second fingerprint with a reference fingerprint.
6. The system of claim 1, wherein:
the user data include identification information of the first terminal device; and the at least one processor is further configured to determine the first fingerprint of the first terminal device based on the identification information.
7. The system of claim 6, wherein the identification information includes information of a transmitter of the first terminal device, the transmitter being used for establishing the communication link.
8. The system of claim 7, wherein the information of the transmitter includes rise time signature of the transmitter of the first terminal device associated with signals transmitted in the communication link.
9. The system of claim 1 , wherein the communication link is a short-range communication link.
10. A computer-implemented method for determining fingerprint information of a terminal device in a transportation service, comprising:
establishing, by a communication interface, a communication link between first and second terminal devices;
receiving, by the communication interface, user data from the first terminal device associated with a user of the transportation service;
receiving, by the communication interface, authentication information authenticating the second terminal device; and
determining a first fingerprint of the first terminal device based on the user data after receiving the authentication information authenticating the second terminal device.
11. The method of claim 10, further comprising transmitting the first fingerprint to a server.
12. The method of claim 10, wherein the second terminal device is associated with a service vehicle.
13. The method of claim 10, further comprising:
determining a second fingerprint of the second terminal device; and
transmitting, via the communication interface, the second fingerprint to a server.
14. The method of claim 13, wherein the authentication information is provided by the server based on matching the second fingerprint with a reference fingerprint.
15. The method of claim 10, wherein:
the user data include identification information of the first terminal device; and the method further comprises determining the first fingerprint of the first terminal device based on the identification information.
16. The method of claim 15, wherein the identification information includes information of a transmitter of the first terminal device, the transmitter being used for establishing the communication link.
17. The method of claim 16, wherein the information of the transmitter includes rise time signature of the transmitter of the first terminal device associated with signals transmitted in the communication link.
18. The method of claim 10, wherein the communication link is a short-range communication link.
19. A non-transitory computer-readable medium storing instruction that, when executed by one or more processors, cause the one or more processors to perform a method for determining fingerprint information of a terminal device in a transportation service, the method comprising:
establishing a communication link between first and second terminal devices;
receiving user data from the first terminal device associated with a user of the transportation service;
receiving authentication information authenticating the second terminal device; and determining a first fingerprint of the first terminal device based on the user data after receiving the authentication information authenticating the second terminal device.
20. The non-transitory computer-readable medium of claim 19, wherein the method further comprises:
determining a second fingerprint of the second terminal device; and
transmitting, via a communication interface, the second fingerprint to a server.
PCT/US2018/068218 2018-12-31 2018-12-31 Systems and methods for device fingerprint determination in a transportation service Ceased WO2020142087A1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201880098088.1A CN112868018B (en) 2018-12-31 2018-12-31 System and method for device fingerprint determination in transportation services

Applications Claiming Priority (6)

Application Number Priority Date Filing Date Title
US16/237,043 US11038877B2 (en) 2018-12-31 2018-12-31 Systems and methods for device fingerprint determination in a transportation service
US16/237,016 2018-12-31
US16/237,016 US11080509B2 (en) 2018-12-31 2018-12-31 Systems and methods for onboard fraud detection in a transportation service
US16/236,970 2018-12-31
US16/237,043 2018-12-31
US16/236,970 US20200213855A1 (en) 2018-12-31 2018-12-31 Systems and methods for fraud detecting in a transportation service

Publications (1)

Publication Number Publication Date
WO2020142087A1 true WO2020142087A1 (en) 2020-07-09

Family

ID=71406522

Family Applications (3)

Application Number Title Priority Date Filing Date
PCT/US2018/068214 Ceased WO2020142085A1 (en) 2018-12-31 2018-12-31 Systems and methods for fraud detecting in a transportation service
PCT/US2018/068218 Ceased WO2020142087A1 (en) 2018-12-31 2018-12-31 Systems and methods for device fingerprint determination in a transportation service
PCT/US2018/068215 Ceased WO2020142086A1 (en) 2018-12-31 2018-12-31 Systems and methods for onboard fraud detection in a transportation service

Family Applications Before (1)

Application Number Title Priority Date Filing Date
PCT/US2018/068214 Ceased WO2020142085A1 (en) 2018-12-31 2018-12-31 Systems and methods for fraud detecting in a transportation service

Family Applications After (1)

Application Number Title Priority Date Filing Date
PCT/US2018/068215 Ceased WO2020142086A1 (en) 2018-12-31 2018-12-31 Systems and methods for onboard fraud detection in a transportation service

Country Status (2)

Country Link
CN (3) CN112930531B (en)
WO (3) WO2020142085A1 (en)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115484545B (en) * 2022-08-16 2025-02-11 五八有限公司 Virtual positioning identification method, device, electronic device and storage medium

Citations (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106453234A (en) * 2016-08-12 2017-02-22 北京东方车云信息技术有限公司 Identity authentication method, relevant server and client
US20170187707A1 (en) * 2015-12-29 2017-06-29 Morphotrust Usa, Llc Onboard vehicle digital identification transmission
US20170316533A1 (en) * 2016-04-29 2017-11-02 GM Global Technology Operations LLC Personal safety and privacy features for passengers of an autonomous vehicle based transportation system
US20180047220A1 (en) * 2015-03-06 2018-02-15 Stephane SAVOURE Device, system and method for sharing vehicles
US20180075565A1 (en) * 2016-09-13 2018-03-15 Ford Global Technologies, Llc Passenger validation systems and methods
US20180074494A1 (en) * 2016-09-13 2018-03-15 Ford Global Technologies, Llc Passenger tracking systems and methods
US20180074495A1 (en) * 2016-09-13 2018-03-15 Ford Global Technologies, Llc Passenger tracking systems and methods
CN107872767A (en) * 2017-11-07 2018-04-03 中国联合网络通信集团有限公司 A recognition method and recognition system for online car-hailing swiping behavior
US20180338229A1 (en) * 2017-05-19 2018-11-22 Waymo Llc Early boarding of passengers in autonomous vehicles

Family Cites Families (28)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20040254890A1 (en) * 2002-05-24 2004-12-16 Sancho Enrique David System method and apparatus for preventing fraudulent transactions
US7272728B2 (en) * 2004-06-14 2007-09-18 Iovation, Inc. Network security and fraud detection system and method
JP4859631B2 (en) * 2006-11-14 2012-01-25 三菱電機株式会社 ENCRYPTED COMMUNICATION SYSTEM, COMMUNICATION TERMINAL DEVICE, ENCRYPTED COMMUNICATION PROGRAM, AND ENCRYPTED COMMUNICATION METHOD
GB0712376D0 (en) * 2007-06-26 2007-08-01 Nxp Bv Processing of satellite navigation system signals
CN102710770A (en) * 2012-06-01 2012-10-03 汪德嘉 Identification method for network access equipment and implementation system for identification method
CN102769531A (en) * 2012-08-13 2012-11-07 鹤山世达光电科技有限公司 Identity authentication device and method thereof
CN103020505B (en) * 2012-12-03 2016-02-03 鹤山世达光电科技有限公司 Based on information management system and the approaches to IM of finger print identifying
US9367968B2 (en) * 2013-01-25 2016-06-14 Moj.Io Inc. System and methods for mobile applications using vehicle telematics data
US20150058191A1 (en) * 2013-08-26 2015-02-26 Apple Inc. Secure provisioning of credentials on an electronic device
US9578025B2 (en) * 2013-10-14 2017-02-21 Zumigo, Inc. Mobile network-based multi-factor authentication
CN104648317B (en) * 2013-11-21 2018-12-25 华为终端（东莞）有限公司 Vehicle condition notice method and apparatus
US20160012465A1 (en) * 2014-02-08 2016-01-14 Jeffrey A. Sharp System and method for distributing, receiving, and using funds or credits and apparatus thereof
CN104869638B (en) * 2015-05-28 2018-04-13 北京嘀嘀无限科技发展有限公司 The detection method and device of gps coordinate cheating
US20160300242A1 (en) * 2015-04-10 2016-10-13 Uber Technologies, Inc. Driver verification system for transport services
WO2016164834A1 (en) * 2015-04-10 2016-10-13 Uber Technologies, Inc. Augmenting transport services using driver profiling
CN106934627B (en) * 2015-12-28 2021-03-30 中国移动通信集团公司 Method and device for detecting cheating behavior in e-commerce industry
CN106686055A (en) * 2015-12-31 2017-05-17 乐视控股（北京）有限公司 Vehicle position monitoring method and system, server, terminal equipment and vehicle
CN105657659A (en) * 2016-01-29 2016-06-08 北京邮电大学 Method and system for identifying scalping user in taxi service
US20180316670A1 (en) * 2016-02-03 2018-11-01 Averon Us, Inc. Method and apparatus for facilitating frictionless two-factor authentication
US9805370B1 (en) * 2016-03-31 2017-10-31 Square, Inc. Device fingerprinting at a merchant location
EP3463994A1 (en) * 2016-06-03 2019-04-10 Volkswagen Aktiengesellschaft Apparatus, system and method for vehicle access and function control utilizing a portable device
CN107079034B (en) * 2016-11-15 2020-07-28 深圳达闼科技控股有限公司 Identity authentication method, terminal equipment, authentication server and electronic equipment
CN108133593A (en) * 2016-12-01 2018-06-08 北京嘀嘀无限科技发展有限公司 The safety certifying method of driver and vehicle, device, system
US10117096B2 (en) * 2016-12-22 2018-10-30 Athentek Innovations, Inc. Systems and methods to determine safe zones and safe routes of a device
CN106997052B (en) * 2017-03-08 2019-06-28 Oppo广东移动通信有限公司 Position information processing method and device and computer equipment
US10552594B2 (en) * 2017-05-04 2020-02-04 Visitlock Llc Verification system
US20180352376A1 (en) * 2017-05-31 2018-12-06 Here Global B.V. Location fingerprinting
US10117098B1 (en) * 2017-06-19 2018-10-30 Amazon Technologies, Inc. User authentication verification service

Patent Citations (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20180047220A1 (en) * 2015-03-06 2018-02-15 Stephane SAVOURE Device, system and method for sharing vehicles
US20170187707A1 (en) * 2015-12-29 2017-06-29 Morphotrust Usa, Llc Onboard vehicle digital identification transmission
US20170316533A1 (en) * 2016-04-29 2017-11-02 GM Global Technology Operations LLC Personal safety and privacy features for passengers of an autonomous vehicle based transportation system
CN106453234A (en) * 2016-08-12 2017-02-22 北京东方车云信息技术有限公司 Identity authentication method, relevant server and client
US20180075565A1 (en) * 2016-09-13 2018-03-15 Ford Global Technologies, Llc Passenger validation systems and methods
US20180074494A1 (en) * 2016-09-13 2018-03-15 Ford Global Technologies, Llc Passenger tracking systems and methods
US20180074495A1 (en) * 2016-09-13 2018-03-15 Ford Global Technologies, Llc Passenger tracking systems and methods
US20180338229A1 (en) * 2017-05-19 2018-11-22 Waymo Llc Early boarding of passengers in autonomous vehicles
CN107872767A (en) * 2017-11-07 2018-04-03 中国联合网络通信集团有限公司 A recognition method and recognition system for online car-hailing swiping behavior

Also Published As

Publication number Publication date
CN112930531A (en) 2021-06-08
CN112868018A (en) 2021-05-28
WO2020142086A1 (en) 2020-07-09
CN112823348A (en) 2021-05-18
CN112868018B (en) 2024-08-02
CN112823348B (en) 2022-11-04
WO2020142085A1 (en) 2020-07-09
CN112930531B (en) 2024-08-23

Similar Documents

Publication Publication Date Title
CA2861470C (en) Method for checking toll transactions and components therefor
US20090024458A1 (en) Position-based Charging
US8615424B2 (en) Electronic toll settlement system for vehicle
CN106209876A (en) Net about car security service authentication method and vehicle personal identification system
US11695766B2 (en) Apparatus and server for sharing position information of vehicle
US20170076279A1 (en) Authenticating purchases made with a handheld wireless device using a vehicle
US20160171477A1 (en) Payment System with Reduced User Interaction
EP3140825B1 (en) Authentication method for vehicular number plate recognition
CN110798320B (en) Vehicle information sharing method and device and vehicle-mounted equipment
US11038877B2 (en) Systems and methods for device fingerprint determination in a transportation service
CN114821877B (en) Traffic method, terminal and computer readable storage medium
CN114841691A (en) Automatic vehicle start service system
CN114881622A (en) Automatic payment method and device based on digital currency and storage medium
US11080509B2 (en) Systems and methods for onboard fraud detection in a transportation service
US12587393B2 (en) System for diagnosis of a vehicle and method thereof
CN111340969B (en) Non-card ETC offline processing method and device, computer equipment and storage medium
CN113095818B (en) License plate payment, license plate payment authentication method and license plate payment enhanced authentication system
CN112868018B (en) System and method for device fingerprint determination in transportation services
US20190318352A1 (en) Wireless Digital Payment For Vehicles
CN113815461A (en) Charging control method and device based on fingerprint verification
US20200213855A1 (en) Systems and methods for fraud detecting in a transportation service
CN112333703B (en) ETC-based platform operation vehicle security authentication system and method
JP2000293717A (en) Authentication system and authentication method
CN121795011A (en) Vehicle interaction authentication
JP2025179709A (en) Identity authentication method

Legal Events

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

Ref document number: 18945403

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 18945403

Country of ref document: EP

Kind code of ref document: A1