A passenger verification terminal, system and method for calling a ride-hailing vehicle

Abstract

The application discloses a kind of for calling net car of proxy passenger verification terminal, system and method. The terminal includes: communication module, for receiving proxy order information issued by cloud service platform;Display module, for displaying vehicle information to passenger;Identity verification module, for collecting passenger identity verification information and comparing with authorized passenger identity information verification;Feedback module, for triggering to send notice to driver terminal and car caller terminal after verification passes. The proxy order is initiated by car caller through car caller terminal. Further, the terminal can also include queuing management module, through the synergistic effect of at least two kinds of reminder methods such as screen brightness enhancement display, light flicker, voice broadcast, realize the reminder under the scene of multiple concurrent. The application solves the technical problem of passenger identity verification and three-party safety confirmation closed loop under proxy calling scene.

Description

Technical Field

[0001] This invention relates to the fields of intelligent transportation and Internet of Things security technology, specifically to a terminal device, system, and method for verifying the identity of passengers and achieving two-way security confirmation between drivers and passengers in a scenario where someone else hails a ride.

[0002] In this invention, the passenger refers to a passenger who has another person call a ride-hailing service on their behalf, including but not limited to persons without civil capacity, persons with limited civil capacity, elderly persons with full civil capacity, and other persons with full civil capacity who are unable to operate ride-hailing software independently. Background Technology

[0003] With the rapid development of the ride-hailing industry, calling a car on behalf of someone else (hereinafter referred to as "calling on behalf of someone") has become a common travel scenario. For example, children calling a car for their elderly parents, parents calling a car for their school-aged children, other persons legally obligated to provide guardianship or care for minors or persons with limited capacity for civil conduct calling a car for each other for convenience or other reasons.

[0004] It is important to note that the "ride-hailing on behalf" described in this patent is fundamentally different from the prior art where a user uses their own mobile phone to hail a ride for themselves (hereinafter referred to as "the caller"). In the caller scenario, the person who hails the ride and the passenger are the same person. The passenger is also the initiator and payer of the order, possesses a smartphone, and can actively view order information, verify the vehicle, communicate with the driver, and bear full responsibility for their actions of getting in and out of the vehicle. In the ride-hailing on behalf scenario, the person who hails the ride and the passenger are two separate entities—the person who hails the ride initiates the order and pays the fare, while the passenger is merely the recipient of the service. The passenger may not possess or have a smartphone, cannot actively view order information, and cannot independently confirm the vehicle they are riding in.

[0005] Existing ride-hailing systems suffer from the following technical deficiencies in the context of ride-hailing on behalf of others: 1. Information transmission gap: In current technology, ride-hailing order information is only sent to the caller's mobile terminal, while the actual passenger cannot directly access this information. This is not a problem in the caller's scenario, as the caller is the same person as the passenger. However, in the ride-hailing on behalf of others scenario, the passenger cannot actively confirm whether the vehicle they are boarding is the one they were supposed to be in, resulting in severe information asymmetry. 2. Lack of identity verification: Existing ride-hailing systems primarily verify identity on the driver's end. Some patents also involve passenger identity verification, but these only verify whether the passenger and the person who placed the order are the same person—essentially still a verification process under the caller's scenario. There is currently no complete technical solution for identity verification completed by the actual passenger at their location before boarding in the ride-hailing on behalf of others scenario. 3. Lack of a closed-loop safety confirmation system: In the ride-hailing on behalf of others scenario, the caller cannot systematically and remotely confirm whether the passenger has safely boarded the correct vehicle. In the scenario of calling the car, the passenger knows whether it is safe to get on the car. However, in the scenario of calling the car on behalf of someone else, the caller can only rely on non-systematic methods such as phone calls and text messages to confirm, resulting in a lack of a closed loop for safety confirmation. 4. Technical defects of the existing "software-based car-calling" function. Currently, mainstream ride-hailing platforms (such as Didi Chuxing, Gaode Map, T3 Mobility, etc.) all provide the "car-calling on behalf of someone else" function. This function allows the caller to enter the passenger's mobile phone number and name to call a car for someone else. Some platforms also support the caller to set "priority to contact the passenger" and send text notes to the driver. However, this function has the following technical defects: (1) Information is still sent to the caller's terminal. The order information is still mainly displayed on the caller's mobile phone. The passenger can only passively view it through text messages or shared links forwarded by the caller. They cannot actively obtain complete vehicle information on an independent terminal. "Priority to contact the passenger" is only a communication priority setting, and the text notes are only unstructured text information. Neither constitutes a technical verification of the passenger's identity. (2) There is no passenger identity verification mechanism. The existing ride-hailing function relies solely on verbal confirmation between the driver and passenger, lacking technical identity verification methods. Several publicly reported safety incidents have shown that the lack of passenger identity verification in ride-hailing orders has led to disputes such as picking up the wrong person or discrepancies between the authorization of the actual passenger and the ride-hailing user. (3) No safety confirmation loop. Ridesharers cannot confirm whether passengers have boarded safely through a systematic approach and can only rely on non-systematic methods such as telephone and SMS. 5. Compliance risk issues of the calling scheme. Some existing technologies attempt to allow persons without civil capacity or with limited civil capacity to independently initiate ride-hailing requests through simplified operations. However, in this model, the contracting party of the transportation contract is the same person as the passenger. When the passenger is a person without civil capacity or with limited civil capacity, the validity of the contract is uncertain, bringing compliance risks to ride-hailing platforms that are difficult to manage uniformly through technical means. 6. Factual obstacles.For elderly people with full civil capacity, they are legally capable of independently entering into transportation contracts. However, due to practical obstacles such as declining vision, decreased finger dexterity, and unfamiliarity with smartphone operation, this group cannot actually use existing ride-hailing apps smoothly. Existing caller schemes attempt to address this issue by simplifying the user interface, but they do not fundamentally change the premise that "passengers must operate the device themselves."

[0006] Analysis of Existing Technologies: 1. Chinese Patent CN108665079A (Beijing Didi Infinite Technology Development Co., Ltd.) discloses a ride-hailing device that enables one-click ride-hailing via physical buttons, allowing elderly people and children who do not carry smart terminals or know how to use ride-hailing apps to easily book a ride. This solution addresses the problem of "how to simplify the ride-hailing operation" in the active call scenario, where the user actively calls a ride for themselves. This solution does not address the scenario of someone else calling the ride—there is no separation between the person calling the ride and the passenger, the passenger passively receiving orders called by others, or the verification of the passenger's identity. 2. US Patent US10825121B2 (Ford Global Technologies, LLC) discloses an identity verification scheme for passengers in ride-hailing scenarios, using facial and voiceprint recognition via the driver's device. The verification action is initiated by the driver, and the verification subject is the driver's device. It addresses the problem of "whether the person getting into the car is the person who placed the order." This solution also targets the calling scenario and does not address the situation where the caller and passenger are separated in the ride-hailing proxy scenario. 3. Japanese Patent JP7025684B2 (Konica Minolta, Inc.) discloses a network service proxy authentication system that intercepts terminal access requests through a reverse proxy server, triggers the authentication application on the terminal to complete biometric authentication, and logs the proxy terminal into external network services after successful authentication. This solution is applied to the general network service authentication field and does not address physical security verification in the ride-hailing proxy scenario. 4. In addition, Chinese Patent CN105635304A (China United Network Communications Group Co., Ltd.) discloses a device for initiating a ride-hailing request in public places via NFC near-field communication. This solution addresses the problem of how to complete a ride-hailing service in a network-free environment and falls under the category of the calling mode. Commercial products that allow one-click ride-hailing on fixed terminals using facial recognition or ID cards have also appeared in Shanghai and other places. However, the above patents and products all belong to the calling mode and do not address the ride-hailing proxy scenario. While mainstream ride-hailing platforms such as Didi Chuxing, Gaode Maps, and T3 Mobility offer "ride-hailing on behalf of others" services, these are merely software-level information transmission optimizations and do not involve passenger identity verification or independent terminals.

[0007] In summary, existing technologies all focus on the caller scenario and have not yet solved the technical problems unique to the ride-hailing scenario of hailing on behalf of others, including passenger information acquisition, passenger identity verification, remote security confirmation of the caller, and three-party security closed loop. Summary of the Invention

[0008] (a) The technical problems to be solved.

[0009] The present invention aims to solve the following technical problems existing in the prior art: in the scenario of hailing a ride-hailing service on behalf of another party (i.e., the person who hails the ride and the passenger are different entities), how to enable the passenger to actively complete identity verification through an independent terminal before getting on the vehicle, and to realize a closed loop of security confirmation among the person who hails the ride, the driver and the passenger.

[0010] (ii) Technical solution.

[0011] To achieve the above objectives, the present invention provides a passenger verification terminal for hailing a ride-hailing service on behalf of another, comprising: The communication module is used to receive ride-hailing order information sent by the cloud service platform. The ride-hailing order is initiated by the person who hails the ride through the person's terminal. The ride-hailing order designates the user bound to the passenger verification terminal as the passenger. The ride-hailing order information includes at least vehicle information. The display module is used to display vehicle information to passengers. The identity verification module is used to collect the identity verification information of passengers and compare the collected identity verification information with the authorized passenger identity information bound in the proxy order when or before the proxy order is initiated, and generate a verification result; the identity verification information includes at least one of password verification information, fingerprint information, facial information, iris information, and voiceprint information. The feedback module is used to send a verification pass message to the cloud service platform when the verification result is pass, so as to trigger the cloud service platform to send a service permission notification to the driver terminal and a safety confirmation notification to the ride-hailing terminal.

[0012] The core innovation of this invention lies in the fact that, for the first time, it addresses the specific needs of ride-hailing scenarios (where the caller and the passenger are separate) by transferring the right to verify identity from the driver to the passenger's independent physical terminal. Through the interactive mode of "passengers passively receiving service information and actively completing identity verification," a secure information loop is achieved among the three parties in the ride-hailing service: the caller, the ride-hailing platform, and the passenger.

[0013] The binding of the passenger verification terminal to the passenger can be achieved through at least one of the following methods: The administrator registers and associates the passenger's identity information with the terminal device identifier through the cloud service platform; the passenger initiates a ride-hailing order by scanning the QR code on the terminal device to complete a temporary binding; or the passenger completes self-binding through identity verification when using the terminal for the first time. The binding relationship is stored on the cloud service platform and supports unbinding and rebinding.

[0014] Furthermore, the specific implementation of the identity verification module includes, but is not limited to: a fingerprint recognition unit for collecting the passenger's fingerprint information; a face recognition unit for collecting the passenger's face image; an iris recognition unit for collecting the passenger's iris information; and a voiceprint recognition unit for collecting the passenger's voiceprint information. Specifically, the voiceprint recognition unit can play a random number or text through the terminal's speaker, and after the passenger repeats it, the microphone collects the voice and extracts the voiceprint features for comparison. In addition, the terminal can also support password verification, allowing the passenger to complete identity verification by entering a preset verification password via a touchscreen or physical keyboard.

[0015] The identity verification module also includes a failure count unit. When the number of consecutive verification failures reaches a preset threshold (for example, this threshold can be set to 3 times), the identity verification module automatically locks, stops subsequent verification operations, and sends a terminal lock message to the cloud service platform through the feedback module. The locked state can be unlocked in the following ways: the ride-hailing terminal sends a remote unlock command through the cloud service platform; or the on-site management personnel of the passenger verification terminal manually unlock it by entering the administrator password.

[0016] Furthermore, the order information also includes driver information and real-time vehicle location information; the display module is also used to display the driver information and real-time vehicle location information.

[0017] Furthermore, the passenger verification terminal also includes a mode control module, used to detect whether there is a valid ride-hailing order with the user bound to the passenger verification terminal as the passenger. When a valid ride-hailing order exists, the mode control module switches the terminal to passive verification mode, which is the working mode for receiving and processing the ride-hailing order; when no valid ride-hailing order exists, the mode control module activates active ride-hailing mode, which is the working mode where the passenger initiates the ride-hailing request themselves. In active ride-hailing mode, since the person calling the ride and the passenger are the same person, and the passenger is the user bound to the terminal, the identity verification steps can be simplified or omitted—the terminal defaults to the current operator being the authorized user.

[0018] Furthermore, the passenger verification terminal also includes a queue management module, which generates a queue number for each pending order when there are multiple pending orders, and sends a reminder to the corresponding passenger when the vehicle arrives through at least one of the following methods: enhanced screen brightness display, flashing lights, voice broadcast, or display of passenger name or order information; wherein at least two reminder methods can be triggered simultaneously.

[0019] Furthermore, the passenger verification terminal is configured in either a fixed installation or a mobile form. The fixed installation form is suitable for fixed locations such as school gatehouses, nursing home reception areas, office building lobbies, and community service centers. The mobile form is a wearable or handheld portable device that can be moved to different locations as needed. This mobile terminal can be directly operated and managed by on-site management personnel.

[0020] Furthermore, the feedback module is also used to notify the passenger of the identity information of the booked vehicle through voice broadcast or vibration after the verification is passed, so as to complete the reverse confirmation of the passenger.

[0021] Furthermore, the feedback module is also used to send a verification failure message to the cloud service platform after verification failure, so as to trigger the sending of an anomaly reminder to the driver terminal and the ride-hailing terminal.

[0022] The present invention also provides a passenger verification system for hailing ride-hailing services, including the passenger verification terminal described in any of the above-mentioned claims, and a cloud service platform.

[0023] The cloud service platform is used to: receive ride-hailing orders initiated by the user's terminal, the ride-hailing orders containing the identity information of the authorized passenger; send the ride-hailing order information to the passenger verification terminal; and after receiving the verification pass message from the passenger verification terminal, send a service permission notification to the driver's terminal and a security confirmation notification to the user's terminal.

[0024] Furthermore, the cloud service platform is also used to generate dynamic ride passes and distribute them to the passenger verification terminal; the display module of the passenger verification terminal is also used to display the dynamic ride passes for the driver's terminal to scan and verify. The dynamic ride passes are visually identifiable information that changes over time or when triggered by an event.

[0025] Furthermore, the cloud service platform is also used to calculate the spatiotemporal proximity based on the real-time location information of each passenger verification terminal and each driver terminal in multiple concurrent order scenarios, and to perform driver-passenger matching and notification based on the spatiotemporal proximity.

[0026] The present invention also provides a method for verifying passengers who book ride-hailing services on behalf of others, including the above-mentioned verification steps.

[0027] (iii) Beneficial effects.

[0028] Compared with the prior art, the present invention has the following beneficial effects.

[0029] 1. Direct technical effects.

[0030] (1) Solving the information asymmetry problem unique to ride-hailing scenarios. This invention directly displays vehicle information to passengers through a display module, so that passengers can know the information of the booked vehicle without relying on the caller's mobile phone to forward the information.

[0031] (2) To realize proactive identity verification of passengers before boarding in the scenario of calling on behalf of others. The present invention collects the identity verification information of passengers on an independent terminal at the location of the passenger through the identity verification module and compares it with the identity information of the authorized passenger. For the first time, it verifies "whether the person boarding the car is the passenger authorized by the caller" in the scenario of calling on behalf of others.

[0032] (3) A three-party security confirmation closed loop is formed in the ride-hailing scenario. After the verification is passed, the present invention automatically triggers the sending of notifications to the driver terminal and the ride-hailing terminal respectively through the feedback module, thus establishing a complete security signaling channel.

[0033] (4) To achieve scientific and reasonable reminders in scenarios with multiple concurrent users. This invention ensures that passengers of different types and in different states can effectively receive reminder information by combining the queuing management module with the synergistic effect of at least two reminder methods.

[0034] (5) Provide a security lock-in mechanism for verification failures. The present invention automatically locks the device when the number of consecutive verification failures reaches a preset threshold through a failure count unit, preventing unauthorized personnel from repeatedly attempting to board the vehicle.

[0035] 2. Derivative effects.

[0036] (6) Reduce platform compliance risks. This invention defines the contracting party of the transportation contract as the person who initiates the ride-hailing order through the ride-hailing terminal, so that every order of the ride-hailing platform in the ride-hailing scenario has clear legal effect.

[0037] (7) Clearly differentiated from existing technologies. Unlike Didi's one-click ride-hailing solution (CN108665079A), this invention addresses the problem of ride-hailing on behalf of others; unlike Ford's driver verification solution (US10825121B2), the verification subject of this invention is the independent terminal held by the passenger; unlike Konica Minolta's universal agent authentication solution (JP7025684B2), this invention solves the specific problem of matching people and vehicles for safety in the physical world. Attached Figure Description

[0038] Figure 1 This is a schematic diagram of the overall architecture of the passenger verification system of the present invention.

[0039] Figure 2 This is a structural block diagram of the passenger verification terminal of the present invention.

[0040] Figure 3 This is a flowchart illustrating the passenger verification method of the present invention.

[0041] Figure 4 This is a schematic diagram of a queue management interface in a multi-person, multi-vehicle scenario according to one embodiment of the present invention. Detailed Implementation

[0042] Example 1: Fixed terminal applied to school gatehouse.

[0043] In this embodiment, the passenger verification terminal is fixedly installed on the wall outside the school gatehouse. The terminal is equipped with a facial recognition camera, a display screen, a speaker, and a network communication module.

[0044] Parents use their mobile app to book rides for their children, specifying the pick-up location as the school gatehouse. When initiating the order, they upload a photo of the student's face as proof of identity. The transportation contract is between the parents and the ride-hailing platform; the student is merely the designated service recipient.

[0045] After receiving a ride-hailing order, the cloud service platform matches drivers and sends the order information to the passenger verification terminal. Upon receiving the order information, the terminal first determines if the order is valid. Only if the order is valid will the terminal perform subsequent display and verification operations. The terminal screen automatically lights up, displaying the vehicle's license plate number, model, color, and estimated arrival time.

[0046] The determination of vehicle arrival at the pick-up point is based on geofencing: the cloud service platform calculates the distance based on the vehicle's real-time GPS location and the coordinates of the pick-up point. When the vehicle enters the preset geofence, the terminal reminds the student through enhanced screen brightness and voice announcement.

[0047] The student walks to the terminal and looks directly at the camera. The terminal's facial recognition unit collects the student's facial features and compares them with the facial information of the authorized passenger linked by the parent when initiating the ride-hailing order.

[0048] After successful verification, the terminal screen displays "Verification successful, please board safely." Simultaneously, the cloud service platform sends a service permission notification to the driver's terminal and a safety confirmation notification to the parent's terminal. If verification fails, the terminal sends a verification failure message to the cloud service platform, which then sends an anomaly alert to both the driver's and parent's terminals.

[0049] If three consecutive verification attempts fail, the identity verification module will automatically lock, halting further verification operations and sending a terminal lock message to the cloud service platform via the feedback module. Parents can remotely send unlock commands via their mobile app, or the school security guard can manually unlock the device by entering the administrator password.

[0050] Example 2: Handheld terminal applied in nursing homes.

[0051] In this embodiment, the passenger verification terminal is a handheld portable device placed at the front desk of the nursing home. The terminal is equipped with a fingerprint recognition module, a facial recognition camera, a display screen, and a voice broadcast module.

[0052] The nursing home administrators pre-registered accounts for each resident on the cloud service platform and recorded their fingerprint information.

[0053] Children book rides on behalf of their parents. The transportation contract is between the children and the ride-hailing platform. Although the elderly person is a person with full civil capacity, they are not familiar with smartphone operation and are unable to book a ride independently.

[0054] When the vehicle arrives, the terminal provides a voice prompt to the elderly person. After the elderly person completes the verification by pressing their fingerprint, the system sends notifications to both the driver's and children's terminals. Simultaneously, the terminal announces the last four digits of the license plate number to help the elderly person further confirm the vehicle. If the elderly person's fingerprint is severely worn, causing verification to fail, the terminal automatically switches to facial recognition for a second verification.

[0055] Example 3: Application of multi-person, multi-vehicle scenarios in office buildings.

[0056] In this embodiment, the passenger verification terminal is fixedly installed in the lobby of an office building. A company calls ride-hailing services on behalf of multiple employees to different destinations at the same time.

[0057] The terminal's built-in queue management module generates a queue number for each ride-hailing order and displays the order list on the screen. The cloud service platform's spatial engine calculates spatiotemporal proximity based on the real-time location information of each driver and passenger terminal, prioritizing the matching of orders that are closest in distance and have the best matching arrival time.

[0058] In terms of specific reminder methods, the terminal adopts the following combination strategy: First, the LED light strip at the top of the terminal flashes at high brightness; second, a large-font reminder message pops up on the screen, displaying order information and passenger names; third, the terminal speaker broadcasts the same content at a moderate volume.

[0059] On the terminal screen's queue list, the row containing the passenger who should be verified is highlighted, with a triangular arrow marking the beginning of the row.

[0060] Employees boarded the bus one by one after completing identity verification through facial recognition on the terminal.

[0061] Example 4: Dual-mode switching – a supplement to the calling function.

[0062] The passenger verification terminal in this embodiment also integrates an active ride-hailing function. When the mode control module detects that there is no valid ride-hailing order with the user bound to this terminal as the passenger, it automatically activates the active calling mode, and the passenger can press the physical button on the terminal or touch the NFC tag to initiate a trip request. When a valid ride-hailing order exists, the active calling function is automatically disabled.

[0063] Example 5: Dynamic boarding passes enhance security.

[0064] When the cloud service platform sends the ride-hailing order information to the passenger's verification terminal, it simultaneously generates a high-contrast serial number that changes over time as a dynamic ride voucher. The terminal display shows this dynamic voucher while displaying vehicle information. Upon arrival, the driver scans the voucher for background comparison. If the comparison matches, the driver's terminal screen displays a blurred photo of the passenger for manual confirmation.

[0065] Example 6: Application of password verification method.

[0066] In this embodiment, the passenger verification terminal is equipped with a touchscreen or a physical keyboard. When a passenger is unable to use biometric identification, they can choose password verification. When placing an order on behalf of another passenger, the ride-hailing service provider sets a temporary verification password for the passenger, which is sent to the passenger via a cloud service platform. Before arriving at the terminal, the passenger enters this password to complete identity verification.

[0067] Example 7: Wearable terminal.

[0068] In this embodiment, the passenger verification terminal is in the form of a smart bracelet, worn on the passenger's wrist. Upon receiving a ride-hailing order, the bracelet screen displays the last four digits of the vehicle's license plate number and the vehicle's color, and alerts the passenger via vibration and voice announcement. The passenger can complete fingerprint or password verification by touching the bracelet screen. For verification methods requiring a larger interface, the passenger can be guided to a nearby fixed or handheld terminal to complete the verification.

[0069] The above description is only a preferred embodiment of the present invention and is not intended to limit the present invention.

[0070] Industrial applicability.

[0071] This invention can be widely applied in places such as schools, nursing homes, community service centers, office buildings, hospitals, and transportation hubs where there is a need for ride-hailing services. The terminal equipment has low manufacturing costs and flexible deployment, and the cloud service platform can interface with existing ride-hailing platforms through standardized interfaces, demonstrating good industrial applicability.

Claims

1. A passenger verification terminal for hailing a ride-hailing service on behalf of another, characterized in that, include: The communication module is used to receive ride-hailing order information sent by the cloud service platform. The ride-hailing order is initiated by the person who hails the ride through the person's terminal. The ride-hailing order designates the user bound to the passenger verification terminal as the passenger. The ride-hailing order information includes at least vehicle information. The display module is used to display vehicle information to passengers. The identity verification module is used to collect the identity verification information of passengers and compare the collected identity verification information with the authorized passenger identity information bound in the proxy order when or before the proxy order is initiated, and generate a verification result; the identity verification information includes at least one of password verification information, fingerprint information, facial information, iris information, and voiceprint information; The feedback module is used to send a verification pass message to the cloud service platform when the verification result is pass, so as to trigger the cloud service platform to send a service permission notification to the driver terminal and a safety confirmation notification to the ride-hailing terminal.

2. The passenger verification terminal according to claim 1, characterized in that, The order information also includes driver information and real-time vehicle location information; the display module is also used to display the driver information and real-time vehicle location information.

3. The passenger verification terminal according to claim 1, characterized in that, It also includes a mode control module, used to detect whether there is a valid proxy order with the user bound to the passenger verification terminal as the passenger; When a valid proxy order exists, the mode control module switches the passenger verification terminal to passive verification mode. The passive verification mode is the working mode for receiving and processing the proxy order. In the passive verification mode, the display module displays the vehicle information, and the identity verification module performs the verification. When there is no valid ride-hailing order, the mode control module activates the active ride-hailing mode, which is a working mode in which the passenger initiates the ride-hailing request himself.

4. The passenger verification terminal according to claim 1, characterized in that, It also includes a queue management module, which generates a queue number for each order when there are multiple pending order requests, and sends a reminder to the corresponding passenger when the vehicle arrives through at least one of the following methods: enhanced screen brightness display, flashing lights, voice announcement, or display of passenger name or order information; wherein at least two reminder methods can be triggered simultaneously.

5. The passenger verification terminal according to claim 1, characterized in that, The passenger verification terminal is configured to be either fixed or movable; the movable form is a wearable device or a handheld portable device. The movable passenger verification terminal can be moved at any time according to the needs of the usage scenario and can be directly operated and managed by on-site management personnel.

6. The passenger verification terminal according to claim 1, characterized in that, The feedback module is also used to notify the passenger of the identity information of the booked vehicle through voice broadcast or vibration after the verification is passed.

7. The passenger verification terminal according to claim 1, characterized in that, The feedback module is also used to send a verification failure message to the cloud service platform after verification fails, so as to trigger the sending of an anomaly reminder to the driver terminal and the ride-hailing terminal.

8. A passenger verification system for hailing ride-hailing services on behalf of others, characterized in that, include: Passenger verification terminal as described in any one of claims 1 to 7; The cloud service platform is used to receive ride-hailing orders initiated by the user's terminal, the ride-hailing order containing the authorized passenger's identity information, send the ride-hailing order information to the passenger verification terminal, and after receiving the verification pass message from the passenger verification terminal, send a service permission notification to the driver's terminal and a safety confirmation notification to the user's terminal.

9. The passenger verification system according to claim 8, characterized in that, The cloud service platform is also used to generate dynamic ride vouchers and distribute the dynamic ride vouchers to the passenger verification terminal; the display module of the passenger verification terminal is also used to display the dynamic ride vouchers for the driver terminal to scan and verify; the dynamic ride vouchers are visually identifiable information that changes with time or event triggers.

10. The passenger verification system according to claim 8, characterized in that, The cloud service platform is also used to calculate the spatiotemporal proximity based on the real-time location information of each passenger verification terminal and each driver terminal in multiple concurrent order scenarios, and to perform driver-passenger matching and notification based on the spatiotemporal proximity.

11. A method for verifying passengers hailing ride-hailing services on behalf of others, characterized in that, Includes the following steps: Step S1: The passenger verification terminal receives the ride-hailing order information issued by the cloud service platform and displays the vehicle information. The ride-hailing order is initiated by the person who hails the ride through the ride-hailing terminal. The ride-hailing order designates the user bound to the passenger verification terminal as the passenger. The ride-hailing order information includes at least vehicle information. Step S2: The passenger verification terminal collects the passenger's identity verification information, which includes at least one of password verification information, fingerprint information, facial information, iris information, and voiceprint information; Step S3: The passenger verification terminal compares and verifies the collected identity verification information with the authorized passenger identity information bound in the proxy order when or before initiating the proxy order, and generates a verification result; Step S4: When the verification result is passed, the passenger verification terminal sends a verification pass message to the cloud service platform to trigger the cloud service platform to send a service permission notification to the driver terminal and a safety confirmation notification to the ride-hailing terminal.

Images