Non-inductive payment awakening method and device based on ultra-wideband positioning and storage medium

Abstract

The invention discloses a non-inductive payment awakening method and device based on UWB positioning and a storage medium, and relates to the technical field of wireless communication networks, and the method comprises the steps: receiving response information of a mobile terminal for UWB anchor point broadcast, and building a session with the mobile terminal; in response to session data corresponding to the session, determining a current position of the mobile terminal; if the current position is in a payment triggering area, generating a transaction instruction based on license plate information, parking lot information and target payment program information; the transaction instruction is sent to a mobile terminal, the mobile terminal can pull up a corresponding payment program based on the transaction instruction, and the parking fee payment action is completed through the payment program. When the mobile terminal meets the specific distance, the instruction is automatically analyzed, the corresponding small payment program is called for fee payment, automatic non-inductive payment can be achieved, and the payment efficiency is improved.

Description

Technical Field

[0001] This application relates to the field of wireless communication network technology, and in particular to a method, device and storage medium for contactless payment wake-up based on ultra-wideband positioning. Background Technology

[0002] Currently, parking fee payments are made using ETC (Electronic Toll Collection) or Bluetooth tags. In this method, a dedicated ETC on-board unit or Bluetooth tag hardware is pre-installed in the vehicle. When a vehicle enters the parking lot entrance / exit, the parking lot's terminal equipment establishes a wireless communication connection with the on-board hardware via a dedicated radio frequency signal, reading the vehicle identification, account information, or linked payment voucher pre-written into the on-board hardware. The fee is deducted based on the read vehicle identification and account information, and after deduction, the gate opens to allow the vehicle to pass. Because a dedicated on-board hardware device needs to be pre-installed in the vehicle to achieve identification and interaction between the terminal equipment and the vehicle, this increases the user's learning curve and initial investment costs.

[0003] The above content is only used to help understand the technical solution of this application and does not represent an admission that the above content is prior art. Summary of the Invention

[0004] The main purpose of this application is to provide a seamless payment wake-up method based on ultra-wideband positioning, which aims to solve the technical problem of how to improve payment efficiency in parking fee payment scenarios.

[0005] To address the aforementioned issues, this application provides a method for waking up a contactless payment system based on ultra-wideband positioning, applied to the field-side equipment. This method includes: Receive response information broadcast by the mobile terminal for the UWB anchor point, and establish a session with the mobile terminal; In response to the session data corresponding to the session, the current location of the mobile terminal is determined; If the current location is within the payment trigger zone, a transaction instruction is generated based on the license plate information, parking lot information, and target payment program information; The transaction instruction is sent to the mobile terminal, which can launch the corresponding payment program based on the transaction instruction and complete the parking fee payment through the payment program.

[0006] In one embodiment, after the step of receiving the response information broadcast by the mobile terminal for the UWB anchor point and establishing a session with the mobile terminal, the seamless payment wake-up method based on ultra-wideband positioning further includes: When it is determined that the mobile terminal is in the entry trigger zone, an identifier acquisition request is generated and sent to the mobile terminal. In response to the identifier acquisition request, the mobile terminal acquires the license plate information associated with the mobile terminal identifier and sends the license plate information to the parking service module of the site-side equipment. When the mobile terminal identifier is associated with the license plate information, associated entry information is generated based on the license plate information, the interaction timestamp corresponding to the anchor point, and the parking area number.

[0007] In one embodiment, after the step of generating and sending an identifier acquisition request to the mobile terminal, the seamless payment wake-up method based on ultra-wideband positioning includes: If the mobile terminal identifier does not have an associated license plate information, then a match is made based on the area number, the interaction timestamp, and the vehicle information database, wherein the vehicle information database contains license plate images captured by the parking lot gate camera module of the site-side equipment. If the anchor point has the same area number as the license plate image, and the difference between the interaction timestamp of the anchor point and the license plate recognition timestamp is within a preset time difference range, then the license plate image is determined as the license plate information. Based on the license plate information, the interaction timestamp, and the parking area number, the associated entry information is generated.

[0008] In one embodiment, before the step of determining the current location of the mobile terminal in response to session data corresponding to the session, the seamless payment wake-up method based on ultra-wideband positioning further includes: Based on preset clustering distance thresholds and preset clustering angle thresholds, density clustering is performed on the distance and angle coordinate pairs of the mobile terminal to obtain effective target clusters; Based on preset weights, the distance matching degree, reflection intensity matching degree, and contour size matching degree of the effective target cluster are weighted and summed to obtain the radar detection confidence. If the radar detection confidence level is greater than or equal to a preset confidence threshold, the mobile terminal is determined to be a valid billing target, and the step of determining the current location of the mobile terminal is executed.

[0009] In one embodiment, after the step of performing density clustering on the distance-angle coordinate pairs of the mobile terminal based on a preset clustering distance threshold and a preset clustering angle threshold to obtain effective target clusters, the seamless payment wake-up method based on ultra-wideband positioning further includes: Obtain a first difference between the center distance of the effective target cluster and a preset effective distance range, and a second difference between the center angle of the effective target cluster and a preset effective angle range. The sum of the first difference and the second difference is determined as the distance offset. Based on the preset correspondence between offset and distance matching degree, the distance matching degree corresponding to the distance offset is determined; The average reflection intensity of the effective target cluster is obtained, and the average reflection intensity is compared with the preset minimum reflection intensity threshold and the preset optimal reflection intensity threshold to obtain the reflection intensity matching degree.

[0010] In one embodiment, before the step of generating a transaction instruction based on license plate information, parking lot information, and target payment program information if the current location is in a payment triggering zone, the seamless payment wake-up method based on ultra-wideband positioning further includes: The identity identifier of the mobile terminal is obtained. If the identity identifier is in a preset whitelist and the identity identifier has an associated entry registration identifier, then the authentication of the mobile terminal is confirmed to be successful.

[0011] This application also provides a method for waking up a user for contactless payment based on ultra-wideband positioning, applied to a mobile terminal. The aforementioned method for waking up a user for contactless payment based on ultra-wideband positioning includes: When a transaction instruction is received from the site-side device, a start identifier for the payment application is generated based on the parking lot information and target payment program information in the transaction instruction; The corresponding payment program is launched based on the activation identifier, and the parking fee payment is completed through the payment program.

[0012] In one embodiment, the step of completing the parking fee payment action based on the payment procedure includes: A parking fee query request is generated based on the parking lot information, license plate information, and current timestamp. The parking fee query request is then sent to the parking lot service module, which calculates the parking fee based on the parking fee query request and the billing rules. The parking payment is completed based on the parking fee sent by the parking service module.

[0013] Furthermore, to achieve the above objectives, this application also proposes a device for a contactless payment wake-up method based on ultra-wideband positioning. The device includes: a memory, a processor, and a computer program stored in the memory and executable on the processor. The computer program is configured to implement the steps of the contactless payment wake-up method based on ultra-wideband positioning as described above.

[0014] In addition, to achieve the above objectives, this application also proposes a storage medium, which is a computer-readable storage medium, on which a computer program is stored, and when the computer program is executed by a processor, it implements the steps of the contactless payment wake-up method based on ultra-wideband positioning as described above.

[0015] This application provides a seamless payment wake-up method based on ultra-wideband positioning. By first obtaining the location of the mobile terminal and determining whether it is in a preset payment trigger zone, when a specific distance is met, the mobile terminal automatically parses the instruction and invokes the corresponding payment mini-program to make payment. This enables automated seamless payment, simplifies the user operation process, and improves payment efficiency and user experience. Attached Figure Description

[0016] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application.

[0017] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, for those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0018] Figure 1 This is a schematic diagram of the first process for the contactless payment wake-up method based on ultra-wideband positioning in this application; Figure 2 A schematic diagram of anchor point deployment provided for the contactless payment wake-up method based on ultra-wideband positioning in this application; Figure 3 A second flowchart illustrating the contactless payment wake-up method based on ultra-wideband positioning provided in this application; Figure 4 A third flowchart illustrating the contactless payment wake-up method based on ultra-wideband positioning provided in this application; Figure 5 A fourth flowchart illustrating the contactless payment wake-up method based on ultra-wideband positioning provided in this application; Figure 6 This is a schematic diagram of the hardware operating environment involved in the contactless payment wake-up method based on ultra-wideband positioning in the embodiments of this application.

[0019] The purpose, features, and advantages of this application will be further explained in conjunction with the embodiments and with reference to the accompanying drawings. Detailed Implementation

[0020] It should be understood that the specific embodiments described herein are merely illustrative of the technical solutions of this application and are not intended to limit this application.

[0021] To better understand the technical solution of this application, a detailed description will be provided below in conjunction with the accompanying drawings and specific implementation methods.

[0022] To achieve the above objectives, this application proposes a seamless payment wake-up method based on ultra-wideband positioning. The method includes: receiving response information broadcast by a mobile terminal to the UWB anchor point and establishing a session with the mobile terminal; determining the current location of the mobile terminal in response to session data corresponding to the session; if the current location is within a payment trigger zone, generating a transaction instruction based on license plate information, parking lot information, and target payment program information; and sending the transaction instruction to the mobile terminal, wherein the mobile terminal can launch the corresponding payment program based on the transaction instruction and complete the parking fee payment action through the payment program.

[0023] Currently, parking fee payments are made using ETC (Electronic Toll Collection) or Bluetooth tags. In this method, a dedicated ETC on-board unit or Bluetooth tag hardware is pre-installed in the vehicle. When a vehicle enters the parking lot entrance / exit, the parking lot's terminal equipment establishes a wireless communication connection with the on-board hardware via a dedicated radio frequency signal, reading the vehicle identification, account information, or linked payment voucher pre-written into the on-board hardware. The fee is deducted based on the read vehicle identification and account information, and the gate is then opened to allow the vehicle to pass. Because a dedicated on-board hardware device needs to be pre-installed in the vehicle to enable identification and interaction between the terminal equipment and the vehicle, this increases the user's learning curve and initial investment costs.

[0024] This application provides a seamless payment wake-up method based on ultra-wideband positioning. By first obtaining the location of the mobile terminal and determining whether it is in a preset payment trigger zone, when a specific distance is met, the mobile terminal automatically parses the instruction and invokes the corresponding payment mini-program to make payment. This enables automated seamless payment, simplifies the user operation process, and improves payment efficiency and user experience.

[0025] It should be noted that the executing entity in this embodiment can be a computing service device with network communication and program execution functions, such as a tablet computer, personal computer, or mobile phone, or an electronic device or apparatus capable of performing the above functions. The following description uses a device for a contactless payment wake-up method based on ultra-wideband positioning as an example to illustrate this embodiment and the subsequent embodiments.

[0026] Based on this, the embodiments of this application provide a method for contactless payment wake-up based on ultra-wideband positioning, referring to... Figure 1 , Figure 1This is a flowchart illustrating the first embodiment of the contactless payment wake-up method based on ultra-wideband positioning in this application.

[0027] In this embodiment, the contactless payment wake-up method based on ultra-wideband positioning includes steps S10 to S40: Step S10: Receive the response information broadcast by the mobile terminal for the UWB anchor point and establish a session with the mobile terminal.

[0028] In this embodiment, the site-side equipment refers to all hardware and service units deployed at the parking lot site and in the backend to jointly support parking payment and access control. This includes: UWB anchors, parking gate modules, and parking service modules. The UWB anchors are hardware base stations deployed near the gate, responsible for near-field wireless sensing, vehicle and pedestrian identification, and terminal wake-up triggering. The parking gate module is the entrance / exit hardware control node, including license plate recognition cameras, gate actuators, and payment status recognition units, responsible for vehicle identification and physical release control. The parking service module is the backend business service cluster, responsible for parking order management and billing calculation. Mobile terminals can be mobile phones, smartwatches, etc. Additionally, the site-side equipment can also be handheld positioning devices for gas station employees, built-in positioning modules in fuel dispensers, and positioning modules for charging piles, adaptable to multiple scenarios such as parking lots, gas stations, and charging piles.

[0029] Please refer to Figure 2 The field-end equipment is equipped with UWB anchor points. These anchor points establish a UWB communication session with the mobile terminal. Fixed anchor points continuously send location wake-up signals via a preset broadcast frequency, while mobile anchor points, such as handheld devices at gas stations, send wake-up signals directionally after being triggered by employees. Upon responding to the signal, the mobile terminal negotiates location parameters with the anchor point to confirm the establishment of the location session. The anchor point and mobile terminal interact bidirectionally via the UWB air interface, transmitting, responding, and receiving signals. The anchor point records the time difference between signal transmission and receiving the mobile terminal's response signal. Combined with the propagation speed of the UWB signal, the straight-line distance between the anchor point and the mobile terminal is obtained. Optionally, to eliminate errors caused by signal reflection and multipath interference, the anchor point continuously collects multiple sets of distance measurement data, removes outliers, and takes the average value to ensure the stability of the distance data.

[0030] Optionally, in different scenarios, the anchor points are used to verify and correct the calculated coordinates based on the characteristics of the scenario. For example, in a parking lot gate scenario, the coordinates are verified to be within the preset range of the gate channel; in a gas station scenario, the coordinates are verified to be within the coverage radius of the corresponding fuel dispenser; and in a charging pile scenario, the coordinates are verified to be close to the surrounding area of ​​the charging pile. If the coordinates exceed the reasonable range of the scenario, it is determined to be a positioning anomaly, and the ranging and calculation process is retried to ensure that the positioning results match the actual scenario.

[0031] In this embodiment, the field-side equipment is equipped with a BLE module and a UWB anchor point. The BLE module is pre-configured with broadcast intervals, broadcast packet formats, and broadcast content. The broadcast content includes core UWB capability identifiers and anchor point identity information. The BLE module sends broadcast packets based on the preset broadcast intervals, broadcast packet formats, and broadcast content. The broadcast packets include basic identity data such as the gate's unique identifier Anchor ID, BLE MAC address, and scene type (e.g., parking lot gate), as well as UWB-related data such as the supported UWB version, whether it can be used as a UWB anchor point, and OOB connection invitation identifier.

[0032] The mobile terminal enables BLE scanning in passive mode, receiving only broadcast packets and not actively sending any. The scanning filtering rules are configured to only receive broadcast packets containing UWB capability identifiers to avoid invalid scans. Upon receiving a BLE broadcast packet, the terminal parses the data, verifies if the Anchor ID is in the pre-stored trusted whitelist, and identifies the presence of an OOB connection invitation identifier to confirm support for UWB parameter exchange. If the verification passes, the terminal marks the field-side device as a target device for establishing a connection; otherwise, it ignores the broadcast packet. Based on the gate's BLE MAC address, the terminal sends a GATT connection request to the gate. The request parameters include the connection interval, the mobile terminal's UWB identifier, and an encryption request. Upon receiving the connection request, the gate verifies the mobile terminal's legitimacy using a pre-set key, a temporarily generated random number, and a two-way authentication mechanism. After successful verification and the establishment of a UWB air interface connection with the mobile device, both ends mount a UWB parameter exchange service based on the GATT protocol. This service includes readable and writable feature values ​​for transmitting UWB configuration parameters. The turnstile sends UWB configuration parameters to the terminal via GATT signature values. Upon receiving the parameters, the terminal verifies the parameter format and confirms that its UWB module supports the set of parameters. If the parameters are valid, the terminal returns a parameter confirmation response to the turnstile, along with its own UWB capability parameters. If the parameters are not supported, the terminal returns a parameter negotiation request, carrying its supported parameter range. The turnstile then readjusts the parameters and sends them again. After receiving the terminal's confirmation response, the turnstile sends a parameter synchronization completion command to the terminal. Both ends store the final negotiated UWB parameters in the configuration area of ​​their local UWB modules and mark the OOB parameter exchange as complete.

[0033] Step S20: In response to the session data corresponding to the session, determine the current location of the mobile terminal.

[0034] In this embodiment, the distance between the mobile terminal tag and the field-side equipment anchor point is determined based on the signal transmission timestamp of the mobile terminal tag, the signal reception timestamp of the field-side equipment anchor point, the response transmission timestamp of the field-side equipment anchor point, and the reception response timestamp of the mobile terminal tag. After UWB configuration parameter synchronization is completed, a UWB ranging session is initiated. The anchor point initiates a unified air interface session establishment request that includes ranging, angle measurement, and radar. The mobile terminal tag sends UWB ranging frames according to a preset time slot, recording the transmission timestamp T1; the anchor point receives the ranging frames, recording the reception timestamp T2, and simultaneously recording its own processing delay; the anchor point sends a response frame in a preset response time slot, recording the transmission timestamp T3; the tag receives the response frame, recording the reception timestamp T4, and recording its own processing delay. Calculate the effective time difference ΔT = (T4 - T1 - tag processing delay) - (T3 - T2 - anchor point processing delay); signal time of flight (ToF) = ΔT / 2; based on distance = speed × time, obtain the distance d between the tag and the anchor point = ToF × c, where c is the speed of light, thus obtaining the measured distance d between the user tag and a single anchor point. Continuously collect a preset number of measured distance values ​​d, remove outliers exceeding the extreme value threshold, calculate the mean of the remaining values, and obtain the final distance R.

[0035] In this embodiment, the phase value of the UWB signal sent by the mobile terminal tag is received and extracted, and the average phase value of the continuous sampling points is determined as the target phase value; the phase difference of the target phase values ​​of adjacent effective antennas is obtained, and the phase difference is used to collect angle measurement data to obtain the azimuth angle and elevation angle.

[0036] All receiving channels of the anchor point multi-antenna array are turned on to receive the UWB signal transmitted by the tag in parallel. The radio frequency signal is down-converted to a baseband signal by a mixer, and the baseband signal is sampled in I / Q quadrature. Taking an 8-antenna array as an example, the I and Q component sequences of each antenna are obtained: I1(t), Q1(t) (antenna 1), I2(t), Q2(t) (antenna 2)...I8(t), Q8(t) (antenna 8). The signal-to-noise ratio (SNR) of each antenna signal is calculated as SNR = 10 × lg(signal power / noise power). Invalid signals with SNR < preset SNR threshold are filtered out to obtain valid signals. For the I / Q components of each valid antenna, the instantaneous phase value is calculated according to the formula: φi(t) = arctan(Qi(t) / Ii(t)) (i = 1~8). The average of the phase values ​​of a preset number of consecutive sampling points is taken to obtain the stable phase value φi of a single antenna. Read the pre-stored calibration offset i in the calibration offset table, such as antenna 1 offset 0.02rad and antenna 2 offset 0.015rad. Correct the phase value of a single antenna based on the calibration offset, φi_correction = φi - calibration offset i, thereby eliminating the phase error caused by the inconsistency of antenna hardware.

[0037] Horizontally adjacent effective antennas are selected, and the phase difference between each pair is calculated, such as antennas 1-2, 2-3, 3-4, 4-5, and 5-6. The phase differences of multiple groups of adjacent antennas are averaged to obtain the horizontal reference phase difference. The same operation is performed on the vertical antennas to obtain the vertical reference phase difference. Low-pass filters are used to filter the horizontal and vertical phase differences separately to suppress phase jumps caused by environmental multipath and jitter, keeping the phase difference smooth. Based on current environmental parameters, temperature and scene compensation are applied to the filtered phase difference: Δφ_horizontal_final = Δφ_horizontal_filtered - environmental compensation value; Δφ_vertical_final = Δφ_vertical_filtered - environmental compensation value, resulting in a final stable and distortion-free corrected phase difference. Phase stability is determined by the amplitude of phase difference changes over multiple consecutive frames; changes within the allowable range are marked as stable, while changes exceeding the threshold are marked as jumps. Finally, the stable phase differences in the horizontal and vertical directions after correction, filtering, and compensation, along with a phase difference stability indicator, are obtained.

[0038] When the corrected phase difference has a stability indicator and the number of effective antennas is greater than or equal to a preset threshold, AoA (Angle of Arrival) calculation is performed. The wavelength λ of the current signal is calculated based on the UWB carrier frequency and the speed of light, λ=c / f. The validity of the phase difference is judged. The theoretical maximum value of the phase difference is: Δφ_max=2πd / λ. If the measured Δφ>Δφ_max, it is determined that the phase difference overflows, and modulus correction is performed to avoid abnormal angle calculation. Δφ correction=Δφ-2π×floor(Δφ / (2π)).

[0039] Finally, the horizontal azimuth angle θ and the vertical elevation angle φ are calculated. For the azimuth angle θ, the original azimuth angle is calculated based on the arcsine model: θ_original = arcsin(Δφ_horizontal_final × λ / (2πd)); the radians are converted to degrees: θ_original = θ_original × 180 / π, and then converted to the global azimuth angle. If θ_original < 0°, then θ_original = 360° + θ_original. The phase difference and angle mapping calibration table is read, and the corresponding angle offset is queried according to the current Δφ_horizontal_final. The difference between θ_original and the angle offset is determined as the corrected value. The calculation logic for the elevation angle φ is the same as that for the azimuth angle, and will not be repeated here.

[0040] Using phase difference, wavelength, and antenna baseline length, the original azimuth angle of the tag signal relative to the anchor point is calculated using an arcsine function model. Employing the same geometric model, the original elevation angle of the tag signal relative to the anchor point is calculated using the vertical phase difference. The calculated radian values ​​are converted to commonly used angle values, and the azimuth angle is normalized to a range of 0° to 360°, while the elevation angle is limited to a range of -90° to 90°. Based on the phase difference-angle mapping calibration table, the corresponding angle offset is looked up, and the original azimuth and elevation angles are compensated and corrected to eliminate angle errors caused by environmental reflections and installation deviations.

[0041] Based on indicators such as phase difference stability, effective antenna quantity, and signal-to-noise ratio (SNR), the angle measurement confidence level is calculated comprehensively: a stable phase results in a high confidence level, while a jump in phase, insufficient effective antenna quantity, or a low SNR leads to a progressively lower confidence level according to rules. This yields calibrated high-precision azimuth and elevation angles, along with their corresponding angle measurement confidence levels.

[0042] The azimuth and pitch angles in angular form are converted into radians for trigonometric function calculations. Using the anchor point as the local coordinate origin, and combining distance, azimuth, and pitch angles, the relative x, y, and z coordinates of the tag in the local coordinate system of the anchor point are calculated. The local relative coordinates are superimposed with the global coordinates of the anchor point to obtain the tag's global 3D coordinates in the entire scene. The global coordinates are validated for reasonableness, determining whether they fall within the preset effective scene area and whether the height conforms to the normal height range of mobile phones or vehicle terminals; if not, the coordinates are marked as abnormal. The distance measurement confidence and angle measurement confidence are weighted and averaged to obtain the overall confidence score after location fusion. Anomalies are distinguished: high confidence scores but coordinates outside the range are considered as the terminal actually leaving the area; low confidence scores are considered as measurement deviations, allowing for remeasurement of distance and angle. The centimeter-level global 3D coordinates, coordinate validity indicators, distance measurement confidence, angle measurement confidence, and fusion confidence score of the tag in the scene are obtained as the final position of the mobile terminal tag.

[0043] Step S30: If the current location is in the payment triggering zone, a transaction instruction is generated based on the license plate information, parking lot information, and target payment program information.

[0044] In this embodiment, after successful authentication, parking lot parameter information such as license plate number, parking lot number, exit gate number, timestamp, payment processing target program, and other exit business message instructions and data are transmitted to the mobile terminal via UWB air interface. The mobile terminal then launches the payment processing target program based on the parking lot parameter information, encapsulates it into a query instruction, and sends it to the parking lot backend server platform to complete the query of the current parking business and subsequent payment actions.

[0045] Please refer to Figure 3The anchor point periodically generates BLE broadcast frames, with the frame payload encapsulating UWB communication configuration parameters, including channel number, pre-synchronization code, data rate, anchor point ID, and ranging / radar operating mode identifier. The anchor point transmits broadcast packets on a designated BLE channel at fixed time intervals. The mobile terminal initiates BLE scanning, listens for broadcast frames in the barrier gate area, and filters out data packets carrying UWB configuration identifiers. The terminal parses the UWB configuration parameters in the broadcast frame, verifies the anchor point ID and channel validity. If a match is found in the current parking area rules, the terminal triggers its own UWB module to power on and initialize. Based on the parsed configuration parameters, the terminal configures its own UWB registers and sends a UWB connection request frame to the anchor point. This connection request frame includes the terminal ID, device type identifier, etc. Upon receiving the request, the anchor point verifies the terminal's validity, replies with a UWB connection confirmation frame, completes the RF layer handshake, and both parties enter a ready state for ranging / radar detection.

[0046] The anchor point and terminal initiate bidirectional time-of-flight measurement, cyclically collecting multiple sets of timestamps to calculate the three-dimensional straight-line distance and distance change rate. The anchor point array antenna receives the terminal signal, extracts the phase difference of each antenna, calculates the horizontal azimuth angle (AoA) and elevation angle, and generates the target spatial direction vector. The anchor point transmits UWB pulse signals, receives the target echo, and extracts the channel impulse response (CIR), micro-Doppler features, radar cross-section (RCS), and point cloud distribution. The gate license plate recognition module outputs the license plate number, vehicle entry direction, and timestamp, which are synchronized to the anchor point via UART serial port to form a vehicle identification tag. The anchor point converts the ranging and angle measurement results into the target's real-time spatial coordinates (X, Y, Z), fits the motion trajectory, and calculates the fluctuation amplitude of movement speed, direction, and altitude. A Fourier transform is performed on the radar echo data to extract the micro-Doppler spectrum. Pedestrians exhibit a 1–3Hz step frequency fluctuation characteristic, while vehicles exhibit a stable low-frequency characteristic; simultaneously, the mean RCS is calculated to distinguish between large RCS (vehicles) and small RCS (pedestrians / mobile phones). The system correlates and matches spatial coordinates, trajectory features, radar features, and license plate information synchronized at the front end of the barrier gate: if the coordinates fall within the lane area, the speed matches the vehicle's travel range, and the radar features match the vehicle database, it is marked as a departing vehicle; otherwise, it is marked as a pedestrian / interference target. If the vehicle feature matching degree is greater than or equal to the threshold and the coordinates are in the departure lane, the subsequent payment wake-up process begins; if it is determined to be a pedestrian / interference target, a silence command is sent to the terminal to release the UWB connection, terminate the process, and avoid false wake-up.

[0047] The anchor point encapsulates the successfully matched license plate number, payment scheme ID, anchor point ID, and timestamp into a DataPhase data frame and transmits it to the corresponding terminal via UWB radio frequency (based on terminal ID addressing). A CRC check and anti-replay counter are added to the data packet to ensure data integrity and security and prevent duplicate pushes. The mobile terminal receives the Data Phase data packet, verifies the CRC and Nonce validity, parses the license plate and scheme information, and launches a pre-set APP or mini-program through the system wake-up mechanism. The APP / mini-program initiates an HTTP / HTTPS request to the parking lot server, carrying the license plate, terminal ID, and timestamp, to query the amount due, billing details, and payment link for the corresponding parking order. The server receives the query request, retrieves the outstanding order based on the license plate, generates a payment session, and returns a payment page link to the terminal. After the user completes the payment, the third-party payment channel calls back to the server, which updates the order status to paid, generates a payment voucher, and pushes a payment success instruction containing the order number, license plate, and timestamp to the gate front end. The gate front end receives a payment success command from the server, verifies whether the license plate matches the currently recognized license plate, and checks the validity of the timestamp to prevent forged commands. If the verification passes, the gate control module triggers the gate opening action and records the opening log; if the verification fails, the gate remains closed and an abnormal alarm is reported to the server. The anchor point continuously monitors the target coordinates. When a vehicle completely leaves the UWB coverage area (e.g., distance measurement exceeds the threshold or angle measurement signal disappears), it sends a departure confirmation frame to the server. Upon receiving the departure confirmation, the server closes the corresponding parking order, updates the parking space status to vacant, and sends a resource release command to both the anchor point and the terminal. Upon receiving the command, the anchor point and terminal close the UWB radio frequency connection and enter a low-power standby state, awaiting the next device discovery process. Optionally, the license plate number can also be pre-bound to a mobile terminal identifier. After receiving the DataPhase data frame, the mobile terminal determines the corresponding license plate information based on its unique identifier.

[0048] In one feasible implementation, before step S30, the seamless payment wake-up method based on ultra-wideband positioning includes the steps of: obtaining the identity identifier of the mobile terminal; if the identity identifier is in a preset whitelist library and the identity identifier has an associated entry registration identifier, then confirming that the mobile terminal is authenticated.

[0049] In this embodiment, after establishing a UWB air interface session with the mobile terminal tag, the site-side equipment anchor point sends an identity retrieval request frame to the mobile terminal tag. This request frame carries the site-side equipment anchor point's unique site-end identifier and timestamp. The unique site-end identifier can be the parking lot number plus the anchor point number. After receiving the request, the mobile terminal tag obtains the whitelist database of the parking service module. The whitelist database contains user identity identifiers that have completed payment qualification verification and is updated synchronously with the platform according to a preset period to ensure the real-time nature of the whitelist database. The decrypted mobile terminal identity identifier is then fully compared with the identifiers in the local whitelist database. If the identifier does not appear in the whitelist database, the anchor point determines that the whitelist verification has failed and returns an authentication failure message to the mobile terminal.

[0050] If a match is successful, the system further verifies whether the identity is bound to valid entry information to ensure the user has completed the entry process. Based on this identity, the system queries the backend database to retrieve associated entry registration identifiers, such as entry timestamp, entry lane number, license plate binding code, and entry verification code. If no associated entry registration identifier is found, the platform returns "no registration information" to the anchor point. If any associated entry registration identifier is found, and the anchor point receives the identifier from the platform, it verifies its time validity and status validity. Only if both time validity and status validity verifications pass are the identity confirmed to have an associated valid entry registration identifier. If either verification fails, the anchor point generates a verification failure message and synchronizes the failure result to the parking service module, simultaneously terminating the transaction instruction issuance process.

[0051] Regarding time validity, optionally, the anchor point extracts the entry timestamp from the entry registration identifier returned by the platform, verifies the format validity of the timestamp, such as whether it conforms to the UTC time format and whether it is a valid time value, and excludes invalid registration data with incorrect format; obtains the preset maximum parking validity period threshold, calculates the time difference between the current timestamp and the entry timestamp, and if the time difference exceeds the threshold, it is determined to be a timeout, thereby filtering out invalid users who occupy parking spaces for a long time but have not left the registration or whose entry data is abnormal, and avoiding issuing transaction instructions to such users.

[0052] Optionally, the status field in the entry registration identifier can also be extracted. For example, the status field can be a preset enumeration value: 0 = entered but not paid, 1 = paid but not left, 2 = left, 3 = abnormal. The status flag is considered valid only when the status is 0 (entered but not paid). If the status is other, corresponding to paid and no further instruction is needed, the exit loop has been completed, or the entry data is abnormal, it is considered that the entry registration is not within the valid time window for billing and deduction, i.e., the time validity check fails.

[0053] Optionally, for status validity verification, the platform verifies whether the entry verification code has been tampered with. When the entry registration identifier is generated, the platform generates a unique entry verification code based on the identity identifier, entry timestamp, entry lane number, and random value using a preset hash algorithm. After receiving the registration identifier, the anchor point extracts the original fields mentioned above, recalculates the verification code using the same algorithm, and compares it with the verification code in the registration identifier. If they match, the verification code is determined not to have been tampered with; if they do not match, the data is determined to have been tampered with, and the status validity verification fails.

[0054] Optionally, to verify whether it matches the entry rules, the site-side equipment retrieves the preset coverage gate area attributes, such as anchor point number 001 corresponding to entry lanes L1 and L2, and gate area R1. Then, it extracts the entry lane number and entry gate area fields from the entry registration identifier. The entry lane number must belong to the lane list covered by the current anchor point to exclude cross-area erroneous triggers where a user enters in lane A but leaves in lane B. The entry gate area must be consistent with the coverage area of ​​the current anchor point to further narrow the effective range and avoid misjudgments of anchor points in different areas within the same parking lot. The entry rule is considered valid only if both layers of matching pass; any mismatch results in a failed status validity check.

[0055] Step S40: The transaction instruction is sent to the mobile terminal, wherein the mobile terminal can launch the corresponding payment program based on the transaction instruction and complete the parking fee payment through the payment program.

[0056] In this embodiment, pre-defined payment trigger zone rules are set for each scenario. For example, parking lot aisles are defined as a specific coordinate range around the gate, gas stations as the radius of the fuel dispenser, and charging piles as the area around the pile. The three-dimensional spatial coordinates of the mobile terminal are acquired in real time to determine whether it falls within the payment trigger zone of the corresponding scenario. If the location meets the requirements, the site-side equipment authenticates the mobile terminal. After successful authentication, it retrieves the fee data for that scenario, such as parking fees, fuel fees, and charging fees, and generates a standardized transaction instruction, which is then sent to the mobile terminal via UWB. After receiving the instruction, the mobile terminal parses the scenario type and payment information and automatically launches the corresponding payment program. If the launch fails, it is downgraded to web payment. Through the pre-defined positioning rules and exclusive fee calculation logic for multiple scenarios, combined with the precise positioning capabilities of UWB, the mobile terminal can automatically parse the instruction and launch the corresponding payment mini-program (such as Alipay Quick Parking) when a specific distance is met or a specific transaction instruction is received in different scenarios such as parking lot aisles, gas stations, and charging piles, achieving a smooth experience of paying as soon as you stop or move.

[0057] In this embodiment, by first obtaining the location of the mobile terminal and determining whether it is within a preset payment trigger zone, the mobile terminal automatically parses the instruction and launches the corresponding payment mini-program to make payment when a specific distance is met. This enables automated, seamless payment, simplifies the user's operation process, and improves payment efficiency and user experience.

[0058] Based on the first embodiment of this application, in the second embodiment of this application, the content that is the same as or similar to that in the first embodiment described above can be referred to the above description and will not be repeated hereafter. Furthermore, after step S10, the contactless payment wake-up method based on ultra-wideband positioning further includes steps A10~A20: Step A10: When it is determined that the mobile terminal is in the entry triggering area, an identifier acquisition request is generated and sent to the mobile terminal. In response to the identifier acquisition request, the mobile terminal acquires the license plate information associated with the mobile terminal identifier and sends the license plate information to the parking service module of the site-side equipment. Step A20: When the mobile terminal identifier has associated license plate information, associated entry information is generated based on the license plate information, the interaction timestamp corresponding to the anchor point, and the parking area number.

[0059] In this embodiment, the field-side device continuously receives mobile terminal interaction data collected by its own UWB anchor point. This data includes mobile terminal identification information, real-time ranging data, interaction timestamp, and signal stability parameters. The field-side device compares the real-time ranging data with a preset entry trigger zone spatial threshold and verifies whether the signal stability parameters meet the continuous and valid interaction conditions. When it is determined that the ranging data is within the trigger zone threshold range and the signal stability parameters meet the preset standard, an entry trigger determination result is generated, which is associated with the mobile terminal identification information and the trigger timestamp.

[0060] Optionally, the field-side equipment extracts signal reception strength, ranging result, interaction response time, and interaction success flags from multiple sets of continuously collected interaction data from UWB anchor points as raw data for signal stability. These raw data sets are then subjected to continuous statistical analysis and fluctuation amplitude calculation. First, the interaction success flags within a preset time window are statistically analyzed to determine the proportion of valid interactions to the total number of interactions. This proportion is compared with a preset effective interaction ratio threshold to determine if the effective interaction coverage meets the standard. Second, variance calculation and difference statistics are performed on multiple consecutive frames of ranging result values ​​within the same time window to obtain the fluctuation amplitude value of the ranging data. This fluctuation amplitude value is compared with a preset ranging fluctuation threshold to determine if the location data is stable. Simultaneously, the mean value and interval determination are performed on the signal reception strength values ​​within the same time window to determine if the signal reception strength remains within a preset effective signal interval. Only when the conditions of effective interaction coverage meeting the standard, ranging fluctuation amplitude value being less than the preset threshold, and signal reception strength remaining within the effective interval are simultaneously met is the signal stability parameter deemed to meet the preset standard.

[0061] Based on the entry trigger determination result, a unique identifier acquisition request is encapsulated and generated according to the preset UWB air interface protocol, and sent to the corresponding mobile terminal via UWB anchor point through the air interface. After receiving the identifier acquisition request from the site-side device, the mobile terminal extracts its own unique terminal identifier and retrieves the license plate information data already bound to its local APP. If a pre-bound license plate exists, the terminal identifier and bound license plate information are packaged to generate response data; if no license plate is bound, only the terminal identifier and the status indicator of no associated license plate are returned. The parking service module parses the mobile terminal response data, extracts the terminal identifier and license plate association status field, verifies the field content one by one, determines whether the mobile terminal identifier has corresponding associated license plate information, and forms a status determination result. If a bound license plate exists, the parking service module extracts the associated license plate information, area number, and interaction timestamp data, integrates them according to the unified data format of the parking lot backend, and generates standardized associated entry information to complete the association binding of the license plate with the mobile terminal and entry event.

[0062] In one feasible implementation, steps A30 to A50 may be included after step A10: Step A30: If the mobile terminal identifier does not have an associated license plate information, then a match is made based on the area number, the interaction timestamp, and the vehicle information database, wherein the vehicle information database contains license plate images captured by the parking lot gate camera module of the site-side equipment. Step A40: If the anchor point has the same area number as the license plate image, and the difference between the interaction timestamp of the anchor point and the license plate recognition timestamp is within a preset time difference range, then the license plate image is determined as the license plate information. Step A50: Generate the associated entry information based on the license plate information, the interaction timestamp, and the parking area number.

[0063] In this embodiment, if no license plate is bound, the UWB anchor point area number, UWB interaction timestamp, and mobile terminal identification information corresponding to the mobile terminal are extracted and used as matching input data. The field-side equipment retrieves vehicle image information, vehicle recognition result information, vehicle recognition timestamp, and image acquisition area number uploaded by the field-side image acquisition equipment from the vehicle information database to form a matching dataset in the vehicle information database.

[0064] The system compares the region ID corresponding to the UWB anchor point with the corresponding region ID in the vehicle information database to determine if they are the same, thus obtaining a region matching result. It calculates the absolute difference between the UWB interaction timestamp and the vehicle information recognition timestamp, compares this time difference with a preset time difference range, and determines if the time difference falls within the preset range, thus obtaining a time matching result. The field-side device performs a joint logical judgment on the region matching result, session matching result, and time matching result. If the region IDs are the same and the difference between the interaction timestamp and the vehicle information recognition timestamp is within the preset time difference range, it determines that the UWB interaction data and the vehicle information in the vehicle information database are associated data corresponding to the same entry event, generating a successful matching result. Based on this successful matching result, the field-side device generates associated entry information.

[0065] In this embodiment, based on the first embodiment of this application, the content that is the same as or similar to that in the first embodiment described above can be referred to the above description and will not be repeated hereafter. Based on this, please refer to... Figure 4 Following step S10, the contactless payment wake-up method based on ultra-wideband positioning further includes steps B10 to S80: Step B10: Based on preset clustering distance threshold and preset clustering angle threshold, perform density clustering on the distance and angle coordinate pairs of the mobile terminal to obtain effective target clusters.

[0066] In this embodiment, the anchor point is loaded with preset UWB radar transmission parameters, including pulse width, repetition frequency, and transmission power. It transmits UWB pulse trains at fixed intervals, while simultaneously activating the synchronous triggering mechanism of the receiving channel to ensure precise clock alignment between transmission and reception. The anchor point receiving antenna captures reflected echoes from targets within the scene and performs preprocessing. A low-noise amplifier amplifies the weak echo signal, suppressing interference introduced by the amplifier's own noise. A mixer down-converts the RF echo signal to a baseband signal, eliminating the high-frequency processing complexity caused by the carrier frequency. A high-speed analog-to-digital converter performs I / Q quadrature sampling (sampling rate ≥ 100 MSps) on the baseband signal, obtaining a digitized I / Q two-channel baseband signal sequence. The digitized I / Q signals are filtered, and the amplitude of the filtered I / Q signals is normalized to map the signal amplitude to the 0~1 range, eliminating amplitude differences caused by transmission power fluctuations and path loss. Based on the normalized I / Q signal, the channel impulse response (CIR) sequence is calculated and extracted. This sequence, with time as the horizontal axis and amplitude as the vertical axis, reflects the reflection characteristics of the target at different distances, and finally, the digital baseband echo I / Q signal and the normalized channel impulse response (CIR) sequence are obtained.

[0067] Anchor points are used to perform sliding window peak detection on the CIR sequence. A peak detection threshold is set, and local maxima points with amplitudes exceeding the threshold are selected to obtain suspected target reflection peaks. Simultaneously, static background peaks that repeatedly appear within multiple consecutive windows are removed to obtain valid reflection peaks. For each valid reflection peak, its timestamp position in the CIR sequence is extracted, and the time difference between this timestamp and the radar pulse emission timestamp is calculated. The absolute distance between each suspected target and the anchor point is determined using the formula: target distance = speed of light × time of flight / 2. The amplitude of each valid reflection peak is extracted as the target reflection intensity feature. A preset reflection intensity threshold for vehicle metal materials is used to remove invalid reflection targets with amplitudes below the threshold. For the retained suspected targets, the feature pairs of distance and reflection intensity are recorded.

[0068] The anchor point calls the multi-antenna array angle resolution module to extract the phase value of the received signal from different antennas at the peak moment of the channel impulse response corresponding to the reflected echo of each suspected target, and calculates the phase difference between adjacent antennas. Based on the pre-stored antenna baseline length, UWB carrier frequency and light speed constant, the signal wavelength is calculated and substituted into the arcsine model formula: target azimuth θ=arcsin(Δφ×λ / (2πd)), where Δφ is the corrected phase difference, λ is the wavelength, and d is the antenna baseline length. The azimuth angle corresponding to each reflection peak is calculated, and the distance-angle polar coordinate data of each suspected target is generated and stored as a structured array. The anchor point starts the DBSCAN density clustering algorithm, first converting all distance-angle polar coordinates to Cartesian coordinates, setting clustering distance threshold and angle threshold as neighborhood determination conditions, and setting the minimum number of neighborhood points of the core point. It traverses all target points and calculates the distance-angle polar coordinate data for each point p. i Count the number of target points in its ε-neighborhood; if the number is greater than or equal to the preset minimum number, then mark p. i A core point is selected; if the number of core points is less than the preset minimum number but falls within the ε-neighborhood of a core point, it is marked as a boundary point; if it is neither a core point nor a boundary point, it is marked as a noise point. Unclassified core points p are selected. i Starting from a core point, all points within its ε-neighborhood are assigned to the same target cluster C1. All core points within C1 are traversed, and all unclassified points within their ε-neighborhoods are merged into C1 until no new points can be added. This process is repeated, selecting the next unclassified core point to generate new target clusters C2, C3…CK, until all core points are classified. All boundary points are assigned to the target cluster of their respective core points, and noise points are directly discarded. Small clusters containing fewer than a preset minimum number of target points are discarded, retaining the effective target cluster set {C1, C2…CK}. m}, thus obtaining a set of effective target clusters, including all distance-angle coordinates of each target cluster and the coordinates of the core point of each target cluster.

[0069] Step B20: Based on preset weights, the distance matching degree, reflection intensity matching degree, and contour size matching degree of the effective target cluster are weighted and summed to obtain the radar detection confidence degree.

[0070] Step B30: When the radar detection confidence level is greater than or equal to a preset confidence threshold, the mobile terminal is determined to be a valid billing target, and the step of determining the current location of the mobile terminal is executed.

[0071] In this embodiment, the distance matching degree, reflection intensity matching degree and contour size matching degree are weighted and summed based on preset weights to obtain the radar detection confidence degree; a preset confidence threshold is set, and when the confidence degree is greater than or equal to the preset confidence threshold, the mobile terminal is determined to be a valid billing target. When using only a single feature for target identification, it is easily affected by complex environmental factors such as metal railings, wall reflections, and pedestrians carrying metal objects in parking lots, leading to misjudgments or missed detections. However, by weighting and summing distance matching degree, reflection intensity matching degree, and contour size matching degree, multi-dimensional discrete features can be fused into a continuous quantified confidence level, enabling a comprehensive evaluation of target attributes, accurately distinguishing edge targets from interfering targets, and significantly improving detection reliability. At the same time, the preset weight method can flexibly adapt to the feature priority of different scenarios such as open-air, underground, and turnstile channels, improving scenario adaptability without modifying the core algorithm. Combined with the confidence threshold, it can effectively filter low-confidence interfering targets and avoid the erroneous rejection of valid targets due to small deviations of a single feature. While ensuring the accuracy of judgment, it improves the robustness of detection, achieves stable distinction between vehicle targets and non-vehicle targets, and reduces the problem of users leaving on foot being mistakenly triggered with payment reminders.

[0072] In one feasible implementation, UWB radar can be used to perform echo imaging on the user's mobile phone location to determine if it contains vehicle shape features. If it does, UWB parking payment information is pushed to the user. If it does not contain vehicle shape features, or if a person's standing shape features are detected, or if continuous location information matches the walking characteristics of a person, it is determined that the user is walking out of the parking lot, and parking payment information is not pushed to the user, thus reducing disturbance to the user.

[0073] Specifically, the field-side UWB anchor point transmits a narrow-pulse UWB signal into the coverage area. The anchor point array antenna receives the target's reflected echo and records the channel impulse response, including data such as echo arrival time, amplitude, phase, and multipath components. The three-dimensional distance between the target and the anchor point is obtained through ranging, and the target's azimuth / elevation angle is obtained through AoA angle measurement. The collected data is preprocessed using sliding window averaging and bandpass filtering to remove environmental thermal noise, wall and ground reflection multipath interference, and retain the target's direct wave echo. The radar echo timestamp is aligned with the UWB positioning timestamp to ensure a one-to-one correspondence between the position data and the echo data.

[0074] Based on arrival time and angle of arrival, SAR (Synthetic Aperture Radar) or MIMO imaging reconstruction is performed on the preprocessed echo data to generate a target point cloud image. Key features are extracted from the imaging results, including contour size, radar cross-section (RCS), and shape regularity. Based on vehicle characteristics, it is determined whether the target is a vehicle. The vehicle determination rules can be: the overall contour size and spatial volume of the target conform to the typical shape characteristics of vehicle-type targets; the echo reflection intensity conforms to the reflection characteristics of vehicle-type targets; the target contour structure is regular, continuous, and has strong overall consistency; the radar point cloud is densely and continuously distributed, exhibiting the characteristics of an overall reflector. If one or more of the above rules are met, it is considered a vehicle. For example, if it is determined to be a vehicle, the UWB anchor point sends a Data Phase data packet to the corresponding mobile terminal, activating the parking APP / mini-program; if it is determined to be a pedestrian, the payment push process is terminated.

[0075] In one possible implementation, steps B40 to B60 may be included after step B10: Step B40: Obtain a first difference between the center distance of the effective target cluster and a preset effective distance range, and a second difference between the center angle of the effective target cluster and a preset effective angle range. The sum of the first difference and the second difference is determined as the distance offset.

[0076] Step B50: Based on the preset correspondence between offset and distance matching degree, determine the distance matching degree corresponding to the distance offset.

[0077] In this embodiment, the center distance d_center is calculated for each valid target cluster. i and center angle θ_center i , where d_center i =(d1+d2+...+d k θ_center / k, where k is the number of target points within the cluster. i =(θ1+θ2+...+θ k ) / k. The distance between the cluster centers, d_center. i Whether it is within the preset effective distance range, for example, whether it meets the condition 0≤d_center. i If the distance is ≤10m, and exceeds the effective distance range, the effective target cluster is deemed not to meet the distance validity condition. If the effective target cluster meets the distance validity condition, the cluster center angle θ_center is further verified. iWhether it is within the effective angle range. When the center distance of the effective target cluster is within the effective distance range and the center angle of the effective target cluster is within the effective angle range, the distance matching degree is recorded as 1; if one of the conditions is not met or both conditions are not met, the offset is linearly reduced in weight, and the distance matching degree corresponding to the distance offset is determined according to the preset correspondence between the offset and the distance matching degree.

[0078] Step B60: Obtain the average reflection intensity of the effective target cluster, and compare the average reflection intensity with the preset minimum reflection intensity threshold and the preset optimal reflection intensity threshold to obtain the reflection intensity matching degree.

[0079] In this embodiment, for each effective target cluster, the mean value A_avg of the reflection intensity of all points within the cluster is calculated. i A_avg i =(A1+A2+...+A k ) / k, remove extreme points of reflection intensity within the cluster. If points exceed the mean by a pre-multiplied standard deviation, recalculate to ensure the mean is not affected by outliers. Preset thresholds for vehicle metal material reflection characteristics are used, including a preset minimum reflection intensity threshold A_min and a preset optimal reflection intensity threshold A_opt. If the mean reflection intensity is ≥ the preset optimal threshold, the reflection intensity is considered a perfect match for the vehicle characteristics, and the matching degree is recorded as 1. If the preset minimum threshold is ≤ the mean reflection intensity < the preset optimal threshold, the matching degree is calculated using linear interpolation, with the formula: Reflection Intensity Matching Degree = (A_avg) / k. i -A_min) / (A_opt-A_min); if A_avg i If the reflection intensity is less than A_min, then the reflection intensity does not match the vehicle features, and the matching degree is recorded as 0. Optionally, the coefficient of variation (CV) of the reflection intensity within the cluster can also be calculated, where CV = standard deviation / mean. If the coefficient of variation is greater than a preset threshold, the reflection intensity is considered to fluctuate too much. In this case, the matching degree is multiplied by a preset penalty coefficient to reduce the confidence level, thus obtaining the reflection intensity matching degree of each target cluster.

[0080] In this embodiment, for the Cartesian coordinates (x, y) of all points within the target cluster, the maximum value x_max and the minimum value x_min of the x-coordinate, and the maximum value y_max and the minimum value y_min of the y-coordinate are calculated; the horizontal contour width W is calculated. i W i =√[(x_max-x_min)²+(y_max-y_min)²]. Based on the vertical angle resolution capability of the UWB multi-antenna array, the vertical angle (i.e., elevation angle) of all points within the cluster is extracted, and the maximum and minimum vertical angles φ_max and φ_min are calculated, combined with the cluster center distance d_center. i Estimate the vertical height H using the formula. i, H i = d_center i × |sinφ_max - sinφ_min|, to obtain the vertical profile height of the target cluster. The minimum vehicle size threshold includes the minimum horizontal width W_min and the minimum vertical height H_min; perform hierarchical calculation on the profile size matching degree. If W i ≥ W_min and H i ≥ H_min, it is considered that the size completely matches the vehicle characteristics, and the matching degree is recorded as 1; if W i ≥ W_min but H i < H_min, or H i ≥ H_min but W i < W_min, the matching degree is calculated by linear interpolation of the short board term, and the profile size matching degree = min[(W i / W_min), (H i / H_min)]; if W i < W_min and H i < H_min, it is considered that the size does not match the vehicle characteristics, and the matching degree is recorded as 0; obtain the horizontal profile width, vertical profile height, and profile size matching degree of each target cluster.

[0081] In the fourth embodiment of the present application, a method for waking up contactless payment based on ultra-wideband positioning is provided. Refer to Figure 5 , Figure 5 which is the schematic flowchart of the fourth embodiment of the method for waking up contactless payment based on ultra-wideband positioning in the present application.

[0082] In this embodiment, the above method is applied to a mobile terminal. The method for waking up contactless payment based on ultra-wideband positioning includes steps C10~C20: Step C10, when receiving a transaction instruction sent by the field-side device, generate a start identifier for the payment application based on the parking lot information and the target payment program information in the transaction instruction.

[0083] Step C20, pull up the corresponding payment program based on the start identifier, and complete the parking fee payment action through the payment program.

[0084] In this embodiment, the mobile terminal continuously listens to the UWB data frames sent by the field-side anchor points through the built-in UWB module. After receiving the data, it first performs basic verification to verify the integrity of the data frame, confirm that the check bits of the frame header and frame tail match the preset rules, and exclude invalid data lost or tampered during the transmission process. Secondly, call the locally preset encryption key to decrypt the ciphertext of the data frame and restore it to plaintext data; verify the format compliance of the plaintext data to ensure that the data structure contains necessary fields such as instruction type and core service parameters, and discard the data directly if the format is incorrect.

[0085] The mobile terminal parses the decrypted plaintext data to determine if a transaction instruction identifier exists in the data. The payment wake-up process is triggered only when a transaction instruction identifier is identified; otherwise, the process is terminated.

[0086] Extract core business parameters related to payment from the data, including but not limited to payment type, application identifier, order information, fee amount, and order validity period; validate the extracted parameters to confirm that the parameter values ​​comply with business rules, such as the amount being a valid value and the order validity period not having expired; terminate the process and record the exception if the parameter is invalid.

[0087] The mobile terminal generates a launch identifier URI for the third-party payment application based on the parsed valid parameters.

[0088] The system retrieves a locally pre-built configuration library, which stores launch identifier templates for different payment applications categorized by payment type. The parsed business parameters are then populated into the corresponding payment type template to generate a complete payment application launch identifier, ensuring precise matching between parameters and template fields. The generated launch identifier format is validated to confirm compliance with system specifications; if the format is incorrect, the process is rebuilt or terminated. The mobile terminal submits an application launch request to the operating system, including the generated payment application launch identifier and system-level launch parameters such as foreground launch and new task creation. The system listens for the operating system's launch response; if the response indicates that the payment application has been successfully launched, the wake-up process is completed, and the user is awaited to complete the payment operation.

[0089] If the response indicates a startup failure, such as the payment application not being installed, the system intercepting the startup request, or the application not supporting the startup method, an exception degradation handling process is triggered. The corresponding web payment link template for the payment type is retrieved from the local configuration library, and the parsed order information, application identifier, and other parameters are filled into the template to generate a complete web payment link. The system's browser access capability is invoked to submit a web access request to the operating system, including the generated web payment link. The browser's response is verified. If the browser successfully opens and loads the web payment page, the degradation process is complete. If the browser call fails, a notification message is pushed to the user, informing them of the payment activation failure and guiding them to perform manual operations.

[0090] In one feasible implementation, the steps of completing the parking fee payment through the payment program include: generating a parking fee query request based on the parking lot information, license plate information, and current timestamp; sending the parking fee query request to the parking service module; wherein the parking service module calculates the parking fee based on the parking fee query request and the billing rules; and completing the parking payment based on the parking fee sent by the parking service module.

[0091] In this embodiment, the mobile terminal continuously monitors the UWB radio frequency signal broadcast by the parking lot's UWB anchor point through its built-in UWB communication module. When it receives a payment instruction from the anchor point, it performs protocol parsing and security verification, verifying the data packet's frame header, CRC checksum, and source anchor point ID to confirm that the data packet was legitimately sent by the parking lot's device and has not been tampered with or replayed, ensuring the security and integrity of the interactive data. After successful parsing and verification, the mobile terminal parses the service payload in the data packet, extracts the payment scenario identifier and license plate information, and establishes an association mapping with the current parking lot payment service, providing data support for subsequent processes. Optionally, the license plate information can also be confirmed through the binding relationship between the mobile terminal identifier and the license plate information. The mobile terminal's system layer matches a preset application wake-up strategy based on the parsed payment scenario identifier. If there are parking-related apps or mini-programs in the terminal's background, they are woken up from their dormant / background state to run in the foreground through system-level broadcast or background service callback mechanisms.

[0092] The activated parking app / mini-program, based on the parsed license plate information, unique terminal identifier, and current timestamp, encapsulates a standardized parking fee query request message. Using an encrypted network communication protocol, it initiates a fee query request to the parking service module. This request includes core parameters for identity verification and business matching, ensuring the compliance and accuracy of the query command. Upon receiving the query request, the parking service retrieves the corresponding parking order data based on the license plate information, calculates the payable fee according to pre-designed fee rules, and generates a response message containing parking duration, payable amount, order number, and payment link. The mobile terminal receives the response message, parses and renders the data, and displays the parking fee details and payment entry point to the user in the application interface. After the user completes the payment through the app / mini-program's payment interface, the third-party payment channel completes the fund settlement and sends a payment result back to the parking service. The mobile terminal simultaneously receives the payment success instruction pushed by the server, updates the order status locally to "paid," and generates a payment voucher.

[0093] The parking service module synchronizes the payment success status to the parking gate front end. Upon receiving the release command, the gate front end verifies the license plate information, order number, and timestamp in the command to confirm its legality and validity. After successful verification, the gate actuator is triggered to open the gate. Simultaneously, the mobile terminal receives the release synchronization command from the server, updates its local parking order status to "departed," and sends a resource release request to the parking lot anchor point via the UWB module. Upon receiving the request, the anchor point terminates its UWB connection with the terminal, and the mobile terminal disables UWB radio frequency communication, returning to low-power standby mode, awaiting the next service trigger.

[0094] This application provides a device for a contactless payment wake-up method based on ultra-wideband positioning, comprising: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, the instructions being executed by the at least one processor to enable the at least one processor to execute the contactless payment wake-up method based on ultra-wideband positioning in the first embodiment described above.

[0095] The following is for reference. Figure 6 The diagram illustrates a structural schematic of a device suitable for implementing the contactless payment wake-up method based on ultra-wideband positioning in the embodiments of this application. The device for the contactless payment wake-up method based on ultra-wideband positioning in the embodiments of this application may include, but is not limited to, mobile terminals such as mobile phones, laptops, personal digital assistants (PDAs), tablet computers (PADs), in-vehicle terminals (e.g., in-vehicle navigation terminals), and main positioning terminals such as digital TVs and desktop computers. Figure 6 The device for the contactless payment wake-up method based on ultra-wideband positioning shown is merely an example and should not impose any limitations on the functionality and scope of use of the embodiments of this application.

[0096] like Figure 6As shown, the device for a contactless payment wake-up method based on ultra-wideband positioning may include a processing unit 1001 (e.g., a central processing unit, a graphics processing unit, etc.) that performs various appropriate actions and processes according to a program stored in a read-only memory (ROM) 1002 or a program loaded from a storage device 1003 into a random access memory (RAM) 1004. The RAM 1004 also stores various programs and data required for the operation of the device. The processing unit 1001, the ROM 1002, and the RAM 1004 are interconnected via a bus 1005. An input / output (I / O) interface 1006 is also connected to the bus. Typically, the following systems can be connected to I / O interface 1006: input devices 1007 including, for example, touchscreens, touchpads, keyboards, mice, image sensors, microphones, accelerometers, gyroscopes, etc.; output devices 1008 including, for example, liquid crystal displays (LCDs), speakers, vibrators, etc.; storage devices 1003 including, for example, magnetic tapes, hard disks, etc.; and communication devices 1009. Communication device 1009 allows the UWBS-based contactless payment wake-up method device to exchange data with other devices wirelessly or via wired communication. Although the figure shows a UWBS-based contactless payment wake-up method device with various systems, it should be understood that it is not required to implement or possess all of the systems shown. More or fewer systems can be implemented alternatively.

[0097] Specifically, according to the embodiments disclosed in this application, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, embodiments disclosed in this application include a computer program product comprising a computer program carried on a computer-readable medium, the computer program containing program code for performing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via a communication device, or installed from storage device 1003, or installed from read-only memory 1002. When the computer program is executed by processing device 1001, it performs the functions defined in the methods of the embodiments disclosed in this application.

[0098] The contactless payment wake-up method and device based on ultra-wideband positioning provided in this application, employing the contactless payment wake-up method based on ultra-wideband positioning in the above embodiments, can solve the technical problem of how to improve payment efficiency in parking fee payment scenarios. Compared with the prior art, the beneficial effects of the contactless payment wake-up method and device based on ultra-wideband positioning provided in this application are the same as those of the contactless payment wake-up method based on ultra-wideband positioning provided in the above embodiments, and other technical features in this contactless payment wake-up method and device based on ultra-wideband positioning are the same as those disclosed in the previous embodiment method, and will not be repeated here.

[0099] It should be understood that the various parts disclosed in this application can be implemented using hardware, software, firmware, or a combination thereof. In the description of the above embodiments, specific features, structures, materials, or characteristics can be combined in any suitable manner in one or more embodiments or examples.

[0100] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

[0101] This application provides a computer-readable storage medium having computer-readable program instructions (i.e., a computer program) stored thereon, which are used to execute the contactless payment wake-up method based on ultra-wideband positioning in the above embodiments.

[0102] The computer-readable storage medium provided in this application may be, for example, a USB flash drive, but is not limited to, electrical, magnetic, optical, electromagnetic, infrared, or semiconductor systems or devices, or any combination thereof. More specific examples of computer-readable storage media may include, but are not limited to: electrical connections having one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fibers, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof. In this embodiment, the computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system or device. The program code contained on the computer-readable storage medium may be transmitted using any suitable medium, including but not limited to: wires, optical cables, radio frequency (RF), etc., or any suitable combination thereof.

[0103] The aforementioned computer-readable storage medium may be included in the device for the contactless payment wake-up method based on ultra-wideband positioning; or it may exist independently and not assembled into the device. The aforementioned computer-readable storage medium carries one or more programs. When the aforementioned one or more programs are executed by the device for the contactless payment wake-up method based on ultra-wideband positioning, the device for the contactless payment wake-up method based on ultra-wideband positioning: receives response information broadcast by the mobile terminal to the UWB anchor point and establishes a session with the mobile terminal; in response to the session data corresponding to the session, determines the current location of the mobile terminal; if the current location is within the payment trigger zone, generates a transaction instruction based on license plate information, parking lot information, and target payment program information; and sends the transaction instruction to the mobile terminal, wherein the mobile terminal can launch the corresponding payment program based on the transaction instruction and complete the parking fee payment action through the payment program.

[0104] Computer program code for performing the operations of this application can be written in one or more programming languages ​​or a combination thereof, including object-oriented programming languages ​​such as Java, Smalltalk, and C++, and conventional procedural programming languages ​​such as the "C" language or similar programming languages. The program code can be executed entirely on the client computer, partially on the client computer, as a standalone software package, partially on the client computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving remote computers, the remote computer can be connected to the client computer via any type of network—including a local area network (LAN) or a wide area network (WAN)—or can be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0105] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation that may be implemented in systems, methods, and computer program products according to various embodiments of this application. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing the specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, may be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0106] The modules described in the embodiments of this application can be implemented in software or hardware. The names of the modules do not necessarily limit the functionality of the unit itself.

[0107] The readable storage medium provided in this application is a computer-readable storage medium that stores computer-readable program instructions (i.e., a computer program) for executing the above-described contactless payment wake-up method based on ultra-wideband positioning, thereby solving the technical problem of how to improve payment efficiency in parking fee payment scenarios. Compared with the prior art, the beneficial effects of the computer-readable storage medium provided in this application are the same as those of the contactless payment wake-up method based on ultra-wideband positioning provided in the above embodiments, and will not be repeated here.

[0108] The above description is only a part of the embodiments of this application and does not limit the patent scope of this application. All equivalent structural transformations made under the technical concept of this application and using the contents of the specification and drawings of this application, or direct / indirect applications in other related technical fields, are included in the patent protection scope of this application.

Claims

1. A method for waking up a contactless payment system based on ultra-wideband positioning, characterized in that, Applied to the field-side equipment, which is equipped with UWB anchor points, the seamless payment wake-up method based on ultra-wideband positioning includes: Receive response information broadcast by the mobile terminal for the UWB anchor point, and establish a session with the mobile terminal; In response to the session data corresponding to the session, the current location of the mobile terminal is determined; If the current location is within the payment trigger zone, a transaction instruction is generated based on the license plate information, parking lot information, and target payment program information; The transaction instruction is sent to the mobile terminal, wherein the mobile terminal can launch the corresponding payment program based on the transaction instruction and complete the parking fee payment through the payment program.

2. The contactless payment wake-up method based on ultra-wideband positioning as described in claim 1, characterized in that, After the steps of receiving the response information broadcast by the mobile terminal for the UWB anchor point and establishing a session with the mobile terminal, the seamless payment wake-up method based on ultra-wideband positioning further includes: When it is determined that the mobile terminal is in the entry trigger zone, an identifier acquisition request is generated and sent to the mobile terminal. In response to the identifier acquisition request, the mobile terminal acquires the license plate information associated with the mobile terminal identifier and sends the license plate information to the parking service module of the site-side equipment. When the mobile terminal identifier is associated with the license plate information, associated entry information is generated based on the license plate information, the interaction timestamp corresponding to the anchor point, and the parking area number.

3. The contactless payment wake-up method based on ultra-wideband positioning as described in claim 2, characterized in that, Following the step of generating and sending an identifier acquisition request to the mobile terminal, the seamless payment wake-up method based on ultra-wideband positioning includes: If the mobile terminal identifier does not have an associated license plate information, then a match is made based on the area number, the interaction timestamp, and the vehicle information database, wherein the vehicle information database contains license plate images captured by the parking lot gate camera module of the site-side equipment. If the anchor point has the same area number as the license plate image, and the difference between the interaction timestamp of the anchor point and the license plate recognition timestamp is within a preset time difference range, then the license plate image is determined as the license plate information. Based on the license plate information, the interaction timestamp, and the parking area number, the associated entry information is generated.

4. The contactless payment wake-up method based on ultra-wideband positioning as described in claim 1, characterized in that, Before the step of determining the current location of the mobile terminal in response to the session data corresponding to the session, the seamless payment wake-up method based on ultra-wideband positioning further includes: Based on preset clustering distance thresholds and preset clustering angle thresholds, density clustering is performed on the distance and angle coordinate pairs of the mobile terminal to obtain effective target clusters; Based on preset weights, the distance matching degree, reflection intensity matching degree, and contour size matching degree of the effective target cluster are weighted and summed to obtain the radar detection confidence. If the radar detection confidence level is greater than or equal to a preset confidence threshold, the mobile terminal is determined to be a valid billing target, and the step of determining the current location of the mobile terminal is executed.

5. The contactless payment wake-up method based on ultra-wideband positioning as described in claim 4, characterized in that, After the step of performing density clustering on the distance-angle coordinate pairs of the mobile terminal based on a preset clustering distance threshold and a preset clustering angle threshold to obtain effective target clusters, the seamless payment wake-up method based on ultra-wideband positioning further includes: Obtain a first difference between the center distance of the effective target cluster and a preset effective distance range, and a second difference between the center angle of the effective target cluster and a preset effective angle range. The sum of the first difference and the second difference is determined as the distance offset. Based on the preset correspondence between offset and distance matching degree, the distance matching degree corresponding to the distance offset is determined; The average reflection intensity of the effective target cluster is obtained, and the average reflection intensity is compared with the preset minimum reflection intensity threshold and the preset optimal reflection intensity threshold to obtain the reflection intensity matching degree.

6. The contactless payment wake-up method based on ultra-wideband positioning as described in claim 1, characterized in that, Before the step of generating a transaction instruction based on license plate information, parking lot information, and target payment program information if the current location is in the payment trigger zone, the seamless payment wake-up method based on ultra-wideband positioning further includes: The identity identifier of the mobile terminal is obtained. If the identity identifier is in a preset whitelist and the identity identifier has an associated entry registration identifier, then the authentication of the mobile terminal is confirmed to be successful.

7. A method for waking up a contactless payment system based on ultra-wideband positioning, characterized in that, Applied to mobile terminals, the seamless payment wake-up method based on ultra-wideband positioning includes: When a transaction instruction is received from the site-side device, a start identifier for the payment application is generated based on the parking lot information and target payment program information in the transaction instruction; The corresponding payment program is launched based on the activation identifier, and the parking fee payment is completed through the payment program.

8. The contactless payment wake-up method based on ultra-wideband positioning as described in claim 7, characterized in that, The steps for completing the parking fee payment through the payment procedure include: A parking fee query request is generated based on the parking lot information, license plate information, and current timestamp. The parking fee query request is then sent to the parking lot service module, which calculates the parking fee based on the parking fee query request and the billing rules. The parking payment is completed based on the parking fee sent by the parking service module.

9. A contactless payment wake-up device based on ultra-wideband positioning, characterized in that, The device includes: a memory, a processor, and a computer program stored in the memory and executable on the processor, the computer program being configured to implement the steps of the contactless payment wake-up method based on ultra-wideband positioning as described in any one of claims 1 to 8.

10. A storage medium, characterized in that, The storage medium is a computer-readable storage medium, and a computer program is stored on the computer-readable storage medium. When the computer program is executed by a processor, it implements the steps of the contactless payment wake-up method based on ultra-wideband positioning as described in any one of claims 1 to 8.

Images