CN116823248A

CN116823248A - Payment method and electronic device

Info

Publication number: CN116823248A
Application number: CN202210285629.XA
Authority: CN
Inventors: 卢骑; 张衡
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2022-03-22
Filing date: 2022-03-22
Publication date: 2023-09-29
Also published as: WO2023179481A1

Abstract

The embodiment of the application provides a payment method and electronic equipment. The payment method comprises the following steps: checking whether transaction information sent by the collection device is abnormal or not by the payment device according to a preset charging rule; if the transaction information is not abnormal, the payment equipment determines to continue the transaction with the collection equipment; if there is an abnormality in the transaction information, the payment device determines to suspend the transaction with the collection device, or the payment device prompts the user of the abnormality in the transaction, and the payment device may continue the transaction with the collection device under the instruction for use. The application provides a novel transaction mode which has relatively high transaction efficiency, is beneficial to reducing user operation in the transaction process, and can enable the transaction to be relatively accurate, efficient and flexible in various scenes.

Description

Payment method and electronic device

Technical Field

The embodiment of the application relates to the field of electronic equipment, and more particularly relates to a payment method and electronic equipment.

Background

Users may use electronic transactions in a variety of scenarios. For example, the electronic transaction may be completed through electronic toll collection (electronic toll collection, ETC) as the vehicle passes over the highway. For another example, the user may complete the electronic transaction by scanning the transaction two-dimensional code, touching a bump, and the like. However, electronic transactions may present a series of transaction problems, such as being limited to specific transaction actions, order information requiring user verification, etc.

Disclosure of Invention

The embodiment of the application provides a payment method and electronic equipment, and aims to provide a new transaction mode which has relatively high transaction efficiency, is beneficial to reducing user operation in the transaction process, and can enable the transaction to be relatively accurate, efficient and flexible in various scenes.

In a first aspect, there is provided a payment method applied to a payment device, the payment method comprising:

receiving transaction information from a collection device, the transaction information indicating an amount to be paid;

judging whether the transaction information is abnormal or not according to a preset charging rule;

paying the amount to be paid to the collection device under the condition that the transaction is not abnormal;

in the event of an abnormality in the transaction information, the transaction with the collecting device is aborted or completed at the direction of the user.

In the application, the payment equipment can check whether the payment request from the merchant is abnormal according to the agreement between the user and the merchant, which is beneficial to reducing the information quantity of manual check. Under the condition that the payment device is not confirmed by people, the payment device can automatically complete the transaction flow, thereby being beneficial to reducing operations required by users to complete electronic transaction and reducing time consumption of the electronic transaction. The payment device may also reject unreasonable transactions without human confirmation, which is beneficial to reducing the likelihood of the user's account being stolen.

With reference to the first aspect, in some implementation manners of the first aspect, the determining, according to a preset charging rule, whether the transaction information is abnormal includes:

judging whether the transaction information is abnormal according to the information related to the transaction information, wherein the information related to the transaction information comprises a preset charging rule, and the information related to the transaction information further comprises one or more of the following: payment account, device information, location information, and time information.

In the application, the payment equipment can synthesize various information to judge whether the transaction information is abnormal, wherein the various information can reflect the current transaction scene of the payment equipment, which is beneficial to the identification of abnormal transactions of the payment equipment in various scenes.

With reference to the first aspect, in certain implementations of the first aspect, the device information includes oil delta information.

In the application, the payment device can confirm whether the oil charge transaction request sent by the collection device is abnormal or not according to the change condition of the oil quantity of the payment device, such as over-high oil charge. Under the condition that the oil charge transaction request is not abnormal, the payment equipment and the collection equipment relatively automatically complete the transaction, so that the time that the payment equipment stays at a gas station is reduced, and further the refueling time is shortened.

With reference to the first aspect, in certain implementations of the first aspect, the location information indicates an entrance and an exit through which the payment device passes.

In the present application, the payment device can confirm whether there is abnormality in the toll transaction request issued by the money receiving device, for example, excessive toll, or the like, based on the exit and entrance through which the payment device passes. In the case that the toll transaction request is not abnormal, the payment device and the collection device relatively automatically complete the transaction, so that the time that the payment device stays at the exit for paying the toll is reduced, and the payment device can complete payment of the toll even in the moving process.

With reference to the first aspect, in certain implementations of the first aspect, the time information indicates a time of passage of the payment device through the entrance and a time of passage through the exit.

In the application, the payment device can confirm whether the transaction request of the parking fee (such as parking fee) sent by the payment device is abnormal or not according to the time of the exit and the entrance which the payment device passes through, such as overhigh toll fee and the like. In the case that the parking fee transaction request is not abnormal, the payment device and the collection device relatively automatically complete the transaction, so that the time that the payment device stays at the outlet for paying the parking fee is reduced, and the payment device can complete payment of the parking fee even in the moving process.

With reference to the first aspect, in certain implementation manners of the first aspect, the payment device is applied to a vehicle, and the payment method further includes:

determining a deduction account of the amount to be paid according to personnel conditions in the vehicle, wherein

Determining that the deducted account of the amount to be paid includes an account of a passenger in the vehicle; and/or the number of the groups of groups,

determining that the deducted account of the amount to be paid includes an account of the driver in the case where the driver is present in the vehicle and the driver is not the vehicle owner; and/or the number of the groups of groups,

in the case where there is a driver in the vehicle and the driver is an owner of the vehicle, or no person is in the vehicle, determining the deducted account for the amount to be paid includes an account of the owner of the vehicle.

In the present application, the payment apparatus can judge the account for payment of the fee according to the condition in the vehicle, that is, the payment apparatus can flexibly confirm which account the fee generated using the vehicle is borne by in particular. In one scenario provided by the application, a vehicle owner may borrow a vehicle from a friend of the vehicle owner. The fee paid by the owner's friend(s) when using the vehicle may be paid by the owner's friend(s). If the vehicle directly deducts funds from the vehicle owner's account, the vehicle owner may experience an economic loss.

With reference to the first aspect, in certain implementation manners of the first aspect, the payment method further includes:

establishing a first short-range wireless communication connection with the passenger's electronic device;

and charging a fee from the electronic account of the passenger over the first short-range wireless communication connection, the fee being associated with a transaction indicated by the transaction information, the fee being less than or equal to the amount to be paid.

In the application, after the passenger enters the vehicle, the electronic equipment of the passenger can establish short-distance wireless communication connection with the payment equipment, so that the payment equipment can flexibly deduct the cost of the passenger, and a flat cost technical scheme is provided for the user.

establishing a second short-range wireless communication connection with the checkout device;

and controlling the vehicle to reduce the running speed.

In the application, after the payment equipment triggers the payment process of the high-speed toll, the payment equipment can control the vehicle to reduce the running speed, thereby being beneficial to prolonging the passable time of the vehicle running to the collection equipment and reserving time for the payment process of the toll.

With reference to the first aspect, in certain implementation manners of the first aspect, after the payment of the amount to be paid to the payment device, the payment method further includes:

and controlling the vehicle to increase the running speed.

In the application, after the vehicle finishes the payment process of the high-speed toll, the payment equipment can control the vehicle to increase the running speed, so that the vehicle can rapidly pass through the collection equipment, and the blocking time of the vehicle to the rear vehicle is reduced.

With reference to the first aspect, in certain implementation manners of the first aspect, the payment device is applied to a vehicle, and in a case that there is no abnormality in the transaction, the payment method further includes:

controlling the vehicle to pass through an unmanned toll gate.

In the application, the payment equipment can confirm whether to adjust the path of the vehicle passing according to the payment condition of the passing fee, so that the vehicle can run on a relatively proper path, and the driving operation of the user on the vehicle is reduced.

With reference to the first aspect, in certain implementation manners of the first aspect, the payment device is applied to a vehicle, and in a case that there is an abnormality in the transaction, the payment method further includes:

And controlling the vehicle to pass through an ETC charging outlet or a manual charging outlet.

In the application, under the condition of abnormal toll payment, the payment equipment can timely adjust the vehicle passing path, thereby being beneficial to enabling the vehicle to smoothly pass through a toll gate and reducing the blocking time of the vehicle to the rear vehicle.

With reference to the first aspect, in certain implementation manners of the first aspect, the payment device has a trusted execution environment for determining whether there is an abnormality in the transaction, and a secure element for operating electronic money, and in a case where there is no abnormality in the transaction, the payment device is paid the amount to be paid, including:

the trusted execution environment sends payment instructions to the secure element;

the security element operates electronic money according to the payment instruction and generates a money certificate of the electronic money, and the amount indicated by the money certificate is the amount to be paid;

the secure element sends the currency credential to the collection device.

In the present application, the secure element and trusted execution environment facilitate improving the security of electronic transactions. Since electronic money is stored on hardware, the money receiving device and the payment device can complete a transaction through a short-range communication technology. The electronic money is operated by the safety element, so that the communication times between the vehicle and the cloud end equipment in the transaction process can be reduced, and the vehicle can relatively smoothly complete the transaction under the condition of poor mobile communication network service.

With reference to the first aspect, in certain implementation manners of the first aspect, the trusted execution environment is configured to store the preset charging rule.

In the application, the trusted execution environment independently maintains the preset charging rules, which is beneficial to safely maintaining the payment equipment to perform legal transaction.

With reference to the first aspect, in certain implementations of the first aspect, the transaction information further indicates one or more of: a collection account, a payment account, a charging rule, a payment entry, an order occurrence time, an order payment time limit, and an order number.

In the application, the transaction information can comprise various information so as to facilitate the payment equipment to acquire transaction details, and the payment equipment can check at least part of the transaction information, thereby reducing the possibility of missing abnormal transactions by the payment equipment.

With reference to the first aspect, in certain implementations of the first aspect, the preset charging rule is included in a contract signed by a user of the payment device and a user of the collection device, or

The preset charging rules are included in a contract made by a user of the payment device and a third party company, the third party company having a contract made by the user of the collection device.

In the application, the user and the merchant can directly contract, and the user and the merchant can also contract through a third party. By pre-writing the charging rules into the contract, it is advantageous to increase the binding force of the user and merchant to fulfill the contract with each other. The user and the merchant sign contracts through a third party company, and the third party company is beneficial to providing a transaction platform for the merchant, showing services, articles and the like of the merchant to the user, and reducing the time for the user to select and search the merchant.

In a second aspect, there is provided a payment device comprising:

a receiving unit configured to receive transaction information from a collection device, the transaction information indicating an amount to be paid;

the processing unit is used for judging whether the transaction information is abnormal according to a preset charging rule;

the processing unit is further used for paying the amount to be paid to the collection device under the condition that the transaction is not abnormal;

the processing unit is further used for suspending the transaction with the collection device or completing the transaction with the collection device under the instruction of a user when the transaction information is abnormal.

In a third aspect, an electronic device is provided, comprising: one or more processors; one or more memories; the one or more memories store one or more computer programs comprising instructions that, when executed by the one or more processors, cause the electronic device to perform the payment method of any of the possible implementations of the first aspect described above.

In a fourth aspect, there is provided a non-transitory computer readable storage medium comprising computer instructions which, when run on an electronic device, cause the electronic device to perform the payment method of any one of the possible implementations of the first aspect.

In a fifth aspect, there is provided a computer program product comprising instructions which, when run on an electronic device, cause the electronic device to perform the payment method of any one of the possible implementations of the first aspect described above.

Drawings

Fig. 1 is a schematic diagram of a hardware structure of an electronic device according to an embodiment of the present application.

Fig. 2 is a schematic software structure of an electronic device according to an embodiment of the present application.

Fig. 3 is a schematic structural diagram of an autonomous vehicle according to an embodiment of the present application.

Fig. 4 is an application schematic diagram of a cloud-side command autopilot vehicle according to an embodiment of the present application.

Fig. 5 is a schematic block diagram of an electronic device according to an embodiment of the present application.

Fig. 6 is a schematic structural diagram of a computer system according to an embodiment of the present application.

Fig. 7 is an application scenario schematic diagram of a payment method according to an embodiment of the present application.

Fig. 8 is a schematic flow chart of a payment method provided by an embodiment of the present application.

Fig. 9 is a schematic diagram of man-machine interaction of a payment method according to an embodiment of the present application.

Fig. 10 is a schematic flow chart of a payment method provided by an embodiment of the present application.

Fig. 11 is a schematic flow chart of another payment method provided by an embodiment of the present application.

Fig. 12 is a schematic view of a scenario for controlling driving of a vehicle according to an embodiment of the present application.

Fig. 13 is a schematic view of another scenario for controlling driving of a vehicle according to an embodiment of the present application.

Fig. 14 is a schematic flow chart of a payment method provided by an embodiment of the present application.

Fig. 15 is a schematic block diagram of a payment device according to an embodiment of the present application.

Fig. 16 is a schematic block diagram of a cash register according to an embodiment of the present application.

Fig. 17 is a schematic structural diagram of an electronic device according to an embodiment of the present application.

Detailed Description

The technical solutions in the embodiments of the present application will be described below with reference to the accompanying drawings.

The embodiments of the application provide an electronic device and embodiments for using such an electronic device. In some embodiments, the electronic device may be a portable electronic device that also includes other functionality such as personal digital assistant and/or music player functionality, such as a cell phone, car set, on-board computer (or On-board PC), chip (e.g., car chip, speech processing chip, etc.), processor, personal computer, wearable electronic device with wireless communication functionality (e.g., smart watch), tablet, in-car device, media consumption device, smart home device, laptop (Laptop), desktop computer, etc. Exemplary embodiments of electronic devices include, but are not limited to, piggybacking Or other operating system electronic devices. The electronic device may be other electronic devices.

Fig. 1 shows a schematic configuration of an electronic device 100. The electronic device 100 may include a processor 110, an external memory interface 120, an internal memory 121, a universal serial bus (universal serial bus, USB) interface 130, a charge management module 140, a power management module 141, a battery 142, an antenna 1, an antenna 2, a mobile communication module 150, a wireless communication module 160, an audio module 170, a speaker 170A, a receiver 170B, a microphone 170C, an ear-piece interface 170D, a sensor module 180, keys 190, a camera 193, a display 194, and the like.

It should be understood that the illustrated structure of the embodiment of the present application does not constitute a specific limitation on the electronic device 100. In other embodiments of the application, electronic device 100 may include more or fewer components than shown, or certain components may be combined, or certain components may be split, or different arrangements of components. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

The processor 110 may include one or more processing units, such as: the processor 110 may include an application processor (application processor, AP), a modem processor, a graphics processor (graphics processing unit, GPU), an image signal processor (image signal processor, ISP), a controller, a video codec, a digital signal processor (digital signal processor, DSP), a baseband processor, and/or a neural network processor (neural-network processing unit, NPU), etc. Wherein the different processing units may be separate components or may be integrated in one or more processors. In some embodiments, the electronic device 101 may also include one or more processors 110. The controller can generate operation control signals according to the instruction operation codes and the time sequence signals to finish the control of instruction fetching and instruction execution. In other embodiments, memory may also be provided in the processor 110 for storing instructions and data. Illustratively, the memory in the processor 110 may be a cache memory. The memory may hold instructions or data that the processor 110 has just used or recycled. If the processor 110 needs to reuse the instruction or data, it can be called directly from the memory. This avoids repeated accesses and reduces the latency of the processor 110, thereby improving the efficiency of the electronic device 101 in processing data or executing instructions.

In some embodiments, the processor 110 may include one or more interfaces. The interfaces may include inter-integrated circuit (inter-integrated circuit, I2C) interfaces, inter-integrated circuit audio (inter-integrated circuit sound, I2S) interfaces, pulse code modulation (pulse code modulation, PCM) interfaces, universal asynchronous receiver transmitter (universal asynchronous receiver/transmitter, UART) interfaces, mobile industry processor interfaces (mobile industry processor interface, MIPI), general-purpose input/output (GPIO) interfaces, SIM card interfaces, and/or USB interfaces, among others. The USB interface 130 is an interface conforming to the USB standard, and may specifically be a Mini USB interface, a Micro USB interface, a USB Type C interface, or the like. The USB interface 130 may be used to connect a charger to charge the electronic device 101, or may be used to transfer data between the electronic device 101 and a peripheral device. The USB interface 130 may also be used to connect headphones through which audio is played.

It should be understood that the interfacing relationship between the modules illustrated in the embodiments of the present application is only illustrative, and is not meant to limit the structure of the electronic device 100. In other embodiments of the present application, the electronic device 100 may also employ different interfacing manners in the above embodiments, or a combination of multiple interfacing manners.

The charge management module 140 is configured to receive a charge input from a charger. The charger can be a wireless charger or a wired charger. In some wired charging embodiments, the charge management module 140 may receive a charging input of a wired charger through the USB interface 130. In some wireless charging embodiments, the charge management module 140 may receive wireless charging input through a wireless charging coil of the electronic device 100. The charging management module 140 may also supply power to the electronic device through the power management module 141 while charging the battery 142.

The power management module 141 is used for connecting the battery 142, and the charge management module 140 and the processor 110. The power management module 141 receives input from the battery 142 and/or the charge management module 140 and provides power to the processor 110, the internal memory 121, the external memory, the display 194, the camera 193, the wireless communication module 160, and the like. The power management module 141 may also be configured to monitor battery capacity, battery cycle number, battery health (leakage, impedance) and other parameters. In other embodiments, the power management module 141 may also be provided in the processor 110. In other embodiments, the power management module 141 and the charge management module 140 may be disposed in the same device.

The wireless communication function of the electronic device 100 may be implemented by the antenna 1, the antenna 2, the mobile communication module 150, the wireless communication module 160, a modem processor, a baseband processor, and the like.

The antennas 1 and 2 are used for transmitting and receiving electromagnetic wave signals. Each antenna in the electronic device 100 may be used to cover a single or multiple communication bands. Different antennas may also be multiplexed to improve the utilization of the antennas. For example: the antenna 1 may be multiplexed into a diversity antenna of a wireless local area network. In other embodiments, the antenna may be used in conjunction with a tuning switch.

The mobile communication module 150 may provide a solution for wireless communication including 2G/3G/4G/5G, etc., applied to the electronic device 100. The mobile communication module 150 may include at least one filter, switch, power amplifier, low noise amplifier (low noise amplifier, LNA), etc. The mobile communication module 150 may receive electromagnetic waves from the antenna 1, perform processes such as filtering, amplifying, and the like on the received electromagnetic waves, and transmit the processed electromagnetic waves to the modem processor for demodulation. The mobile communication module 150 can amplify the signal modulated by the modem processor, and convert the signal into electromagnetic waves through the antenna 1 to radiate. In some embodiments, at least some of the functional modules of the mobile communication module 150 may be disposed in the processor 110. In some embodiments, at least some of the functional modules of the mobile communication module 150 may be provided in the same device as at least some of the modules of the processor 110.

The wireless communication module 160 may provide solutions for wireless communication including wireless local area network (wireless local area networks, WLAN) (e.g., wireless fidelity (wireless fidelity, wi-Fi) network), bluetooth (BT), global navigation satellite system (global navigation satellite system, GNSS), frequency modulation (frequency modulation, FM), near field wireless communication technology (near field communication, NFC), infrared technology (IR), etc., as applied to the electronic device 100. The wireless communication module 160 may be one or more devices that integrate at least one communication processing module. The wireless communication module 160 receives electromagnetic waves via the antenna 2, modulates the electromagnetic wave signals, filters the electromagnetic wave signals, and transmits the processed signals to the processor 110. The wireless communication module 160 may also receive a signal to be transmitted from the processor 110, frequency modulate it, amplify it, and convert it to electromagnetic waves for radiation via the antenna 2.

The electronic device 100 implements display functions through a GPU, a display screen 194, an application processor, and the like. The GPU is a microprocessor for image processing, and is connected to the display 194 and the application processor. The GPU is used to perform mathematical and geometric calculations for graphics rendering. Processor 110 may include one or more GPUs that execute program instructions to generate or change display information.

The display screen 194 is used to display images, videos, and the like. The display 194 includes a display panel. The display panel may employ a liquid crystal display (liquid crystal display, LCD), an organic light-emitting diode (OLED), an active-matrix organic light-emitting diode (AMOLED) or an active-matrix organic light-emitting diode (matrix organic light emitting diode), a flexible light-emitting diode (flex), a mini, a Micro led, a Micro-OLED, a quantum dot light-emitting diode (quantum dot light emitting diodes, QLED), or the like. In some embodiments, the electronic device 100 may include 1 or more display screens 194.

The display 194 of the electronic device 100 may be a flexible screen that is currently of great interest due to its unique characteristics and great potential. Compared with the traditional screen, the flexible screen has the characteristics of strong flexibility and bending property, can provide a new interaction mode based on the bending property for a user, and can meet more requirements of the user on electronic equipment. For electronic devices equipped with foldable display screens, the foldable display screen on the electronic device can be switched between a small screen in a folded configuration and a large screen in an unfolded configuration at any time. Accordingly, users use split screen functions on electronic devices configured with foldable display screens, as well as more and more frequently.

The electronic device 100 may implement photographing functions through an ISP, a camera 193, a video codec, a GPU, a display screen 194, an application processor, and the like.

The ISP is used to process data fed back by the camera 193. For example, when photographing, the shutter is opened, light is transmitted to the camera photosensitive element through the lens, the optical signal is converted into an electric signal, and the camera photosensitive element transmits the electric signal to the ISP for processing and is converted into an image visible to naked eyes. ISP can also optimize the noise, brightness and skin color of the image. The ISP can also optimize parameters such as exposure, color temperature and the like of a shooting scene. In some embodiments, the ISP may be provided in the camera 193.

The camera 193 is used to capture still images or video. The object generates an optical image through the lens and projects the optical image onto the photosensitive element. The photosensitive element may be a charge coupled device (charge coupled device, CCD) or a Complementary Metal Oxide Semiconductor (CMOS) phototransistor. The photosensitive element converts the optical signal into an electrical signal, which is then transferred to the ISP to be converted into a digital image signal. The ISP outputs the digital image signal to the DSP for processing. The DSP converts the digital image signal into an image signal in a standard RGB, YUV, or the like format. In some embodiments, electronic device 100 may include 1 or more cameras 193.

The digital signal processor is used for processing digital signals, and can process other digital signals besides digital image signals. For example, when the electronic device 100 selects a frequency bin, the digital signal processor is used to fourier transform the frequency bin energy, or the like.

Video codecs are used to compress or decompress digital video. The electronic device 100 may support one or more video codecs. In this way, the electronic device 100 may play or record video in a variety of encoding formats, such as: dynamic picture experts group (moving picture experts group, MPEG) 1, MPEG2, MPEG3, MPEG4, etc.

The NPU is a neural-network (NN) computing processor, and can rapidly process input information by referencing a biological neural network structure, for example, referencing a transmission mode between human brain neurons, and can also continuously perform self-learning. Applications such as intelligent awareness of the electronic device 100 may be implemented through the NPU, for example: image recognition, face recognition, speech recognition, text understanding, etc.

The external memory interface 120 may be used to connect an external memory card, such as a Micro SD card, to enable expansion of the memory capabilities of the electronic device 100. The external memory card communicates with the processor 110 through an external memory interface 120 to implement data storage functions. For example, files such as music, video, etc. are stored in an external memory card.

The internal memory 121 may be used to store one or more computer programs, including instructions. The processor 110 may cause the electronic device 101 to perform the method of off-screen display provided in some embodiments of the present application, as well as various applications, data processing, and the like, by executing the above-described instructions stored in the internal memory 121. The internal memory 121 may include a storage program area and a storage data area. The storage program area can store an operating system; the storage program area may also store one or more applications (such as gallery, contacts, etc.), etc. The storage data area may store data created during use of the electronic device 101 (e.g., photos, contacts, etc.), and so on. In addition, the internal memory 121 may include high-speed random access memory, and may also include nonvolatile memory, such as one or more disk storage units, flash memory units, universal flash memory (universal flash storage, UFS), and the like. In some embodiments, processor 110 may cause electronic device 101 to perform the off-screen display methods provided in embodiments of the present application, as well as other applications and data processing, by executing instructions stored in internal memory 121, and/or instructions stored in a memory provided in processor 110. The electronic device 100 may implement audio functions through an audio module 170, a speaker 170A, a receiver 170B, a microphone 170C, an earphone interface 170D, an application processor, and the like. Such as music playing, recording, etc.

The sensor module 180 may include a pressure sensor 180A, a gyroscope sensor 180B, an acceleration sensor 180C, a distance sensor 180D, a proximity light sensor 180E, a fingerprint sensor 180F, a temperature sensor 180G, a touch sensor 180H, an ambient light sensor 180J, and the like.

The keys 190 include a power-on key, a volume key, etc. The keys 190 may be mechanical keys. Or may be a touch key. The electronic device 100 may receive key inputs, generating key signal inputs related to user settings and function controls of the electronic device 100.

Fig. 2 is a software configuration block diagram of the electronic device 100 according to the embodiment of the present application. The layered architecture divides the software into several layers, each with distinct roles and branches. The layers communicate with each other through a software interface. In some embodiments, the Android system is divided into four layers, from top to bottom, an application layer, an application framework layer, an Zhuoyun row (Android run) and system libraries, and a kernel layer, respectively. The application layer may include a series of application packages.

As shown in FIG. 2, the application package may include applications such as gallery, calendar, talk, map, navigation, autopilot, electronic transaction, and the like.

The application framework layer provides an application programming interface (application programming interface, API) and programming framework for application programs of the application layer. The application framework layer includes a number of predefined functions.

As shown in FIG. 2, the application framework layer may include a window manager, a content provider, a view system, a telephony manager, a resource manager, a notification manager, and the like.

The window manager is used for managing window programs. The window manager can acquire the size of the display screen, judge whether a status bar exists, lock the screen, intercept the screen and the like.

The content provider is used to store and retrieve data and make such data accessible to applications. The data may include video, images, audio, calls made and received, browsing history and bookmarks, phonebooks, etc.

The view system includes visual controls, such as controls to display text, controls to display pictures, and the like. The view system may be used to build applications. The display interface may be composed of one or more views. For example, a display interface including a text message notification icon may include a view displaying text and a view displaying a picture.

The telephony manager is used to provide the communication functions of the electronic device 100. Such as the management of call status (including on, hung-up, etc.).

The resource manager provides various resources for the application program, such as localization strings, icons, pictures, layout files, video files, and the like.

The notification manager allows the application to display notification information in a status bar, can be used to communicate notification type messages, can automatically disappear after a short dwell, and does not require user interaction. Such as notification manager is used to inform that the download is complete, message alerts, etc. The notification manager may also be a notification in the form of a chart or scroll bar text that appears on the system top status bar, such as a notification of a background running application, or a notification that appears on the screen in the form of a dialog window. For example, a text message is prompted in a status bar, a prompt tone is emitted, the electronic device vibrates, and an indicator light blinks, etc.

Android run time includes a core library and virtual machines. Android run time is responsible for scheduling and management of the Android system.

The core library consists of two parts: one part is a function which needs to be called by java language, and the other part is a core library of android.

The application layer and the application framework layer run in a virtual machine. The virtual machine executes java files of the application program layer and the application program framework layer as binary files. The virtual machine is used for executing the functions of object life cycle management, stack management, thread management, security and exception management, garbage collection and the like.

The system library may include a plurality of functional modules. For example: surface manager (surface manager), media library (media library), three-dimensional graphics processing library (e.g., openGL ES), 2D graphics engine (e.g., SGL), etc.

The surface manager is used to manage the display subsystem and provides a fusion of 2D and 3D layers for multiple applications.

Media libraries support a variety of commonly used audio, video format playback and recording, still image files, and the like. The media library may support a variety of audio and video encoding formats, such as MPEG4, h.264, MP3, AAC, AMR, JPG, PNG, etc.

The three-dimensional graphic processing library is used for realizing three-dimensional graphic drawing, image rendering, synthesis, layer processing and the like.

The 2D graphics engine is a drawing engine for 2D drawing.

The kernel layer is a layer between hardware and software. The inner core layer at least comprises a display driver, a camera driver, an audio driver and a sensor driver.

Fig. 3 is a functional block diagram of a vehicle provided by an embodiment of the present application. The vehicle may be an electronic device provided by an embodiment of the present application. In one embodiment, the vehicle is configured in a fully or partially autonomous mode. For example, the vehicle may control the vehicle itself while in the automatic driving mode, and the current state of the vehicle and its surrounding environment may be determined by human operation, the possible behavior of at least one other vehicle in the surrounding environment may be determined, and a confidence level corresponding to the likelihood that the other vehicle performs the possible behavior may be determined, and the vehicle may be controlled based on the determined information. When the vehicle is in the autonomous mode, the vehicle may be placed into operation without interaction with a person.

The vehicle may include various subsystems, such as a travel system 202, a sensor system 204, a control system 206, one or more peripherals 208, as well as a power supply 210, a computer system 262, and a user interface 216. Alternatively, the vehicle may include more or fewer subsystems, and each subsystem may include multiple elements. In addition, each subsystem and element of the vehicle may be interconnected by wire or wirelessly.

The travel system 202 may include components that provide powered movement of the vehicle. In one embodiment, propulsion system 202 may include an engine 218, an energy source 219, a transmission 220, and wheels/tires 221. The engine 218 may be an internal combustion engine, an electric motor, an air compression engine, or other type of engine combination, such as a hybrid engine of a gasoline engine and an electric motor, or a hybrid engine of an internal combustion engine and an air compression engine. The engine 218 converts the energy source 219 into mechanical energy.

Examples of energy sources 219 include gasoline, diesel, other petroleum-based fuels, propane, other compressed gas-based fuels, ethanol, solar panels, batteries, and other sources of electricity. The energy source 219 may also provide energy to other systems of the vehicle.

The transmission 220 may transmit mechanical power from the engine 218 to the wheels 221. The transmission 220 may include a gearbox, a differential, and a drive shaft. In one embodiment, the transmission 220 may also include other devices, such as a clutch. Wherein the drive shaft may comprise one or more axles that may be coupled to one or more wheels 221.

The sensor system 204 may include several sensors that sense information about the environment surrounding the vehicle. For example, the sensor system 204 may include a positioning system 222 (which may be a global positioning system (global positioning system, GPS) system, as well as a beidou system or other positioning system), an inertial measurement unit (inertial measurement unit, IMU) 224, a radar 226, a laser rangefinder 228, and a camera 230. The sensor system 204 may also include sensors of the internal systems of the monitored vehicle (e.g., in-vehicle air quality monitors, fuel gauges, oil temperature gauges, etc.). Sensor data from one or more of these sensors may be used to detect objects and their corresponding characteristics (location, shape, direction, speed, etc.). Such detection and identification are key functions for safe operation of the autonomous vehicle.

The positioning system 222 may be used to estimate the geographic location of the vehicle. The IMU 224 is used to sense the position and orientation changes of the vehicle based on inertial acceleration. In one embodiment, the IMU 224 may be a combination of an accelerometer and a gyroscope.

Radar 226 may utilize radio signals to sense objects within the surrounding environment of the vehicle. In some embodiments, in addition to sensing an object, the radar 226 may be used to sense the speed and/or heading of the object.

The laser rangefinder 228 may utilize a laser to sense objects in the environment in which the vehicle is located. In some embodiments, laser rangefinder 228 may include one or more laser sources, a laser scanner, and one or more detectors, among other system components.

The camera 230 may be used to capture multiple images of the surrounding environment of the vehicle. The camera 230 may also be used to capture the facial expression of the driver. The camera 230 may be a still camera or a video camera.

The control system 206 is configured to control the operation of the vehicle and its components. The control system 206 may include various elements including a steering system 232, a throttle 234, a brake unit 236, a sensor fusion algorithm, a computer vision system 240, a route control system 242, and an obstacle avoidance system 244.

The steering system 232 is operable to adjust the heading of the vehicle. For example, in one embodiment may be a steering wheel system.

The throttle 234 is used to control the operating speed of the engine 218 and thus the speed of the vehicle.

The brake unit 236 is used to control the vehicle deceleration. The brake unit 236 may use friction to slow the wheel 221. In other embodiments, the brake unit 236 may convert the kinetic energy of the wheels 221 into electrical current. The brake unit 236 may take other forms to slow the rotational speed of the wheels 221 to control the speed of the vehicle.

The computer vision system 240 may be operative to process and analyze images captured by the camera 230 to identify objects and/or features in the vehicle surroundings. The objects and/or features may include traffic signals, road boundaries, and obstacles. The computer vision system 240 may use object recognition algorithms, in-motion restoration structure (structure from motion, SFM) algorithms, video tracking, and other computer vision techniques. In some embodiments, the computer vision system 240 may be used to map an environment, track objects, estimate the speed of objects, and so forth. When the camera 230 captures an image of the driver's face, the computer vision system 240 may analyze the characteristics of the driver's facial expression. For example, whether the driver's eye is deviated, whether the driver is talking on words, etc. The computer vision system 240 may use facial recognition algorithms.

The route control system 242 is used to determine a travel route of the vehicle. In some embodiments, route control system 242 may incorporate data from sensors, GPS 222, and one or more predetermined maps to determine a travel route for the vehicle.

The obstacle avoidance system 244 is operable to identify, evaluate, and avoid or otherwise clear potential obstacles in the environment of the vehicle.

Of course, in one example, control system 206 may additionally or alternatively include components other than those shown and described. Or some of the components shown above may be eliminated.

The vehicle interacts with external sensors, other vehicles, other computer systems, or users through peripheral devices 208. Peripheral devices 208 may include a wireless communication system 246, a vehicle computer 248, a microphone 250, and/or a speaker 252.

In some embodiments, the peripheral device 208 provides a means for a user of the vehicle to interact with the user interface 216. For example, the vehicle computer 248 may provide information to a user of the vehicle. The user interface 216 may also operate the vehicle computer 248 to receive user input. The vehicle computer 248 may be operated by a touch screen. In other cases, the peripheral device 208 may provide a means for the vehicle to communicate with other devices located within the vehicle. For example, microphone 250 may receive audio (e.g., voice commands or other audio input) from a user of the vehicle. Similarly, speaker 252 may output audio to a user of the vehicle.

The wireless communication system 246 may communicate wirelessly with one or more devices directly or via a communication network. For example, the wireless communication system 246 may use 3G cellular communication, such as code division multiple access (code division multiple access, CDMA), global system for mobile communications (global system for mobile communications, GSM), general packet radio service technology (general packet radio service, GPRS), or 4G cellular communication, such as long term evolution (long term evolution, LTE). Or 5G cellular communication. The wireless communication system 246 may communicate with a wireless local area network (wireless local area network, WLAN) using WiFi. In some embodiments, wireless communication system 246 may communicate directly with devices using an infrared link, bluetooth, or the like. Other wireless protocols, such as various vehicle communication systems, for example, wireless communication system 246 may include one or more dedicated short-range communication (dedicated short range communications, DSRC) devices, which may include public and/or private data communications between vehicles and/or roadside stations.

The power supply 210 may provide power to various components of the vehicle. In one embodiment, the power source 210 may be a rechargeable lithium ion or lead acid battery. One or more battery packs of such batteries may be configured with a power source to provide power to various components of the vehicle. In some embodiments, the power source 210 and the energy source 219 may be implemented together, such as in some all-electric vehicles.

Some or all of the functions of the vehicle are controlled by a computer system 262. The computer system 262 may include at least one processor 263, with the processor 263 executing instructions 265 stored in a non-transitory computer-readable medium such as data storage 264. The computer system 262 may also be a plurality of computing devices that control individual components or subsystems of the vehicle in a distributed manner.

The processor 263 may be any conventional processor such as a commercially available central processing unit (central processing unit, CPU). Alternatively, the processor may be a special purpose device such as an ASIC or other hardware-based processor. Although FIG. 3 functionally illustrates a processor, memory, and other elements of computer 210 in the same block, it will be understood by those of ordinary skill in the art that the processor, computer, or memory may in fact comprise multiple processors, computers, or memories that may or may not be stored within the same physical housing. For example, the memory may be the hard disk drive 233 or other storage medium located in a different enclosure than the computer 210. Thus, references to a processor or computer will be understood to include references to a collection of processors or computers or memories that may or may not operate in parallel. Rather than using a single processor to perform the steps described herein, some components, such as the steering component and the retarding component, may each have their own processor that performs only calculations related to the component-specific functions.

In various aspects described herein, the processor may be located remotely from the vehicle and in wireless communication with the vehicle. In other aspects, some of the processes described herein are performed on a processor disposed within the vehicle and others are performed by a remote processor, including taking the necessary steps to perform a single maneuver.

In some embodiments, data storage 264 may contain instructions 265 (e.g., program logic) that instructions 265 may be executed by processor 263 to perform various functions of the vehicle, including those described above. The data storage 264 may also contain additional instructions, including instructions to send data to, receive data from, interact with, and/or control one or more of the propulsion system 202, the sensor system 204, the control system 206, and the peripherals 208.

In addition to instructions 265, data storage 264 may store data such as road maps, route information, vehicle location, direction, speed, and other such vehicle data, as well as other information. Such information may be used by the vehicle and the computer system 262 during operation of the vehicle in autonomous, semi-autonomous, and/or manual modes.

A user interface 216 for providing information to or receiving information from a user of the vehicle. Optionally, the user interface 216 may include one or more input/output devices within the set of peripheral devices 208, such as a wireless communication system 246, a car-in-computer 248, a microphone 250, and a speaker 252.

The computer system 262 may control the functions of the vehicle based on inputs received from various subsystems (e.g., the travel system 202, the sensor system 204, and the control system 206) and from the user interface 216. For example, computer system 262 may utilize input from control system 206 to control steering unit 232 to avoid obstacles detected by sensor system 204 and obstacle avoidance system 244. In some embodiments, computer system 262 is operable to provide control over a number of aspects of the vehicle and its subsystems.

Alternatively, one or more of these components may be mounted separately from the vehicle or associated therewith. For example, the data storage 264 may exist partially or completely separate from the vehicle. The above components may be communicatively coupled together in a wired and/or wireless manner.

Alternatively, the above components are only an example, and in practical applications, components in the above modules may be added or deleted according to actual needs, and fig. 3 should not be construed as limiting the embodiments of the present application.

An autonomous car traveling on a road, such as the vehicle above, may identify objects within its surrounding environment to determine adjustments to the current speed. The object may be another vehicle, a traffic control device, or another type of object. In some examples, each identified object may be considered independently and based on its respective characteristics, such as its current speed, acceleration, spacing from the vehicle, etc., may be used to determine the speed at which the autonomous car is to adjust.

Alternatively, an autonomous automotive vehicle or a computing device associated with an autonomous vehicle (e.g., computer system 262, computer vision system 240, data storage 264 of fig. 3) may predict the behavior of an identified object based on characteristics of the identified object and the state of the surrounding environment (e.g., traffic, rain, ice on a road, etc.). Alternatively, each identified object depends on each other's behavior, so all of the identified objects can also be considered together to predict the behavior of a single identified object. The vehicle is able to adjust its speed based on the predicted behavior of the identified object. In other words, an autonomous car is able to determine what steady state the vehicle will need to adjust to (e.g., accelerate, decelerate, or stop) based on the predicted behavior of the object. In this process, the speed of the vehicle may also be determined taking into account other factors, such as the lateral position of the vehicle in the road on which it is traveling, the curvature of the road, the proximity of static and dynamic objects, and so on.

In addition to providing instructions to adjust the speed of the autonomous vehicle, the computing device may also provide instructions to modify the steering angle of the vehicle so that the autonomous vehicle follows a given trajectory and/or maintains safe lateral and longitudinal distances from objects in the vicinity of the autonomous vehicle (e.g., cars in adjacent lanes on the road).

Optionally, an autonomous automotive vehicle or a computing device associated with an autonomous vehicle (e.g., computer system 262, computer vision system 240, data storage 264 of fig. 3) may predict the driver's attention during driving based on the driver's facial expression (e.g., whether the driver is distracted, whether the driver is talking with others, etc.). The vehicle can start or shut down its own auxiliary driving function based on the attention of the driver. In other words, the autonomous car is able to determine that the automatic driving level of the vehicle is one of L0 to L5 based on the attention of the driver.

L0: the driver is in full control of the vehicle.

L1: automated systems are sometimes capable of assisting a driver in accomplishing certain driving tasks.

L2: the automatic system can complete certain driving tasks, but a driver needs to monitor the driving environment to complete the rest part, and meanwhile, the problem is guaranteed to occur, and take over at any time. At this level, the false sense and judgment of the automated system is corrected by the driver at any time. L2 can be divided into different use scenarios by speed and environment, such as loop low-speed traffic jam, fast driving on highways and automatic parking of drivers in the vehicles.

L3: the automated system can perform certain driving tasks and in some cases monitor the driving environment, but the driver must be ready to regain control of the driving (when the automated system makes a request). At this level the driver still cannot go to sleep or have a deep rest.

L4: the automated system is capable of completing driving tasks and monitoring the driving environment under certain circumstances and specific conditions. At this stage, all tasks related to driving and drivers are irrelevant in the range that automatic driving can operate, and the outside responsibility is perceived to be in the automatic driving system.

L5: the automatic system can complete all driving tasks under all conditions.

The vehicle may be a car, a truck, a motorcycle, a bus, a ship, an airplane, a helicopter, a mower, an amusement ride, a recreation ground vehicle, construction equipment, an electric car, a golf car, a train, a trolley, or the like, and the embodiment of the present application is not particularly limited.

The autopilot system may include several auxiliary autopilot functions. Such as pre-crash safety braking (PCS), adaptive cruise control (adaptive cruise control, ACC), lane Keeping Aid (LKA), cross traffic warning (cross traffic alert, CTA), tail cross traffic warning (rear cross traffic alert, RCTA), blind spot warning (blind spot warning, BSW), turn off vehicle warning, and traffic jam aid (traffic jam assist, TJA), etc.

Computer system 262 in FIG. 3 may also receive information from, or transfer information to, other computer systems. Alternatively, sensor data collected from the vehicle's sensor system 204 may be transferred to another computer for processing of the data.

For example, as shown in fig. 4, data from computer system 312 may be transmitted via a network to cloud-side server 320 for further processing. The networks and intermediate nodes may include various configurations and protocols including the internet, world wide web, intranets, virtual private networks, wide area networks, local area networks, private networks using proprietary communication protocols of one or more companies, ethernet, wiFi and hypertext transfer protocols (hyper text transfer protocol, HTTP), and various combinations of the foregoing. Such communication may be by any device capable of transmitting data to and from other computers, such as modems and wireless interfaces. For example, the attention data of the driver is transmitted to the cloud-side server 320 for further processing, the cloud-side server may identify and process the attention data using various neural network models, and feed back the attention identification result of the driver to the computer system 312, so that the computer system 312 may confirm whether to turn on or off the auxiliary automatic driving function.

In one example, server 320 may comprise a server having multiple computers, such as a load balancing server farm, that exchanges information with different nodes of a network for the purpose of receiving, processing, and transmitting data from computer system 312. The server may be configured similar to computer system 312 with processor 330, memory 340, instructions 350, and data 360.

Users may use electronic transactions in a variety of scenarios. The electronic transaction may be a transaction manner by an electronic money transaction. The electronic money may be money stored on an electronic account, the electronic money having a transactable attribute. The transaction may include, for example, consumption, transfer, collection, presentation, etc. There are a number of specific ways of electronic transactions.

In one possible scenario, electronic money may be stored on the user's electronic account. The electronic account may be provided by a vendor. That is, the carrier of electronic money may be an electronic account. The user may act as a payer, and the money stored on the user's electronic account may be deducted through the electronic transaction. For example, a user may log into an electronic account on an electronic device and transfer money on the electronic account to a payee through a series of operations (e.g., scanning a two-dimensional code, entering a transfer account number, touching in close proximity, etc.). The user may also act as a payee, receiving money from the payer via an electronic transaction, and storing the received electronic money on the user's electronic account.

In another possible scenario, an electronic device held by a user may have a transaction module. The transaction module may have a function of storing electronic money. The transaction module may be a hardware module of the electronic device, or the functions of the transaction module may be implemented by hardware of the electronic device. That is, the carrier of electronic money may be hardware. The user may carry an electronic device with a transaction module. When the user is acting as a payer, the user may perform a series of operations on the electronic device, which may control the transaction module to deduct the electronic money stored on the transaction module. When the user acts as the payee, the electronic device may write the received electronic money to the transaction module so that the money received by the user may be stored on the transaction module.

Fig. 5 is a schematic structural diagram of an electronic device according to an embodiment of the present application.

The electronic device may run an application. The application may be provided by a vendor, for example. In one embodiment, the functions or roles of the application program shown in FIG. 5 may be implemented, for example, by the processor 110 shown in FIG. 1. In another embodiment, the application program shown in FIG. 5 may correspond to an application in the application layer shown in FIG. 2, for example. In yet another embodiment, the application program shown in FIG. 5 may correspond to, for example, instructions 265 shown in FIG. 3. As shown in fig. 5, the application program may include an electronic transaction program. The electronic transaction program may refer to, for example, an application program having an electronic cash register function and/or an electronic payment function. In another embodiment, the application may also run on a device other than the electronic device. In connection with fig. 4, an application program is, for example, instructions 350 stored in memory 340, and the instructions 350 may be executed by processor 330 to implement the functions associated with the application program.

In some embodiments, the user may initiate the electronic transaction by an operation with respect to the application. For example, the user may open an application (e.g., an electronic transaction program, or an application associated with an electronic transaction program), and the application may prompt the user for transaction information. The transaction information may include, for example, transaction content, amount, transaction time, etc. The user can confirm the transaction information provided by the application program and operate the application program to perform subsequent electronic transaction flow.

In other embodiments, the user may collect electronic money through an operation for the application program. For example, a user confirms transaction information in an application and sends the transaction information to a payer through the application to advance an electronic transaction process. After the electronic transaction is completed, the user may also operate the application to confirm the payment information of the electronic account.

In some embodiments provided by the present application, the electronic transaction program may complete the transaction through a transaction module of the electronic device. In the embodiment shown in fig. 5, the transaction module of the electronic device may include a trusted execution environment (trusted execution environment, TEE) (or trusted execution module, trusted execution application, or trusted execution element, etc.) and a Secure Element (SE). In some embodiments, the electronic device may include a TEE chip to implement the functionality of the trusted execution environment. In other possible embodiments, the trusted execution environment and/or the secure element may be an external element of the electronic device. Wherein the trusted execution environment and the secure element may interact with the electronic device through an external interface.

The secure element may refer to separate physical hardware on the electronic device. The secure element itself may also be referred to as an operating system. In some embodiments, the electronic device may include an SE chip to implement the functionality of the secure element. The secure element may be used for storing electronic money, and may also have a secure authentication function (e.g., authentication key, etc.) to secure access to electronic money. In one embodiment, the secure element may enable electronic money storage, retrieval, etc. by receiving or outputting a money credential containing electronic money.

A trusted execution environment may refer to independent physical hardware on an electronic device. The trusted execution environment itself may also refer to an operating system. In some embodiments, the electronic device may include a TEE chip to implement the functionality of the trusted execution environment. The trusted execution environment is used to transfer information between the application and the secure element shown in fig. 5. The trusted execution environment may process a transaction request from the application and instruct the secure element to deposit/withdraw electronic money in accordance with the transaction request. Trusted execution environments may have relatively efficient computing efficiency to enable relatively complex computations. In one embodiment provided by the present application, the trusted execution environment may identify whether the transaction request is abnormal, and if so, may abort the transaction. In another embodiment provided by the application, the trusted execution environment may also oversee the transfer of currency credentials so that the secure element can accurately access electronic currency.

In some embodiments, the electronic device may further include a communication module. The electronic device may interact transaction information with the receipts/payment devices via the communication module. The communication module shown in fig. 5 may correspond to, for example, the wireless communication module and/or the mobile communication module shown in fig. 1. The communication module shown in fig. 5 may, in turn, correspond to the wireless communication system 246 shown in fig. 3, for example.

In some embodiments, the electronic device may send a payment request to the payment device, which may include transaction information. The payment device may pay electronic money through the electronic account, and accordingly, the electronic device may obtain currency notes containing the electronic money from the cloud device. The cloud device may be, for example, the server 320 shown in fig. 4. The payment device may also pay electronic money stored on the hardware. The trusted execution environment of the electronic device may monitor whether the transaction is abnormal, if not, the trusted execution environment may indicate to the secure element to collect electronic money. The secure element may verify the monetary credentials and store the electronic money under the direction of the trusted execution environment.

In other embodiments, the electronic device may receive a payment request sent by the checkout device, which may include transaction information. The trusted execution environment of the electronic device may verify whether the transaction information is anomalous, if not, the trusted execution environment may instruct the secure element to pay electronic money. The secure element may output a currency credential containing electronic currency under the direction of the trusted execution environment and deduct the electronic currency stored on the secure element. The electronic device may send the money voucher to the payee device. The money receiving apparatus may receive the money voucher to receive electronic money according to the money voucher.

In the embodiment shown in fig. 5, since electronic money is stored in hardware, in one possible scenario, the electronic device may not be networked at the time of collection and payment, and interaction for electronic transactions is accomplished through short-range communications. In the embodiment shown in fig. 5, the communication module may have a near field communication (near field communication, NFC) module, a bluetooth low energy (bluetooh low energy, BLE) module, an ultra-wideband (UWB) module, or the like, short-range communication module. In other possible embodiments, the communication modules may have more or fewer short-range communication modules.

In one possible scenario, the electronic device may search for nearby checkout devices through the short-range communication module. The checkout device may send a payment request to the electronic device via a short-range communication protocol. The electronic device may output a money voucher containing electronic money according to the payment request and deduct the electronic money stored on the secure element. The electronic device may send the money voucher to the payee device. The money receiving apparatus may receive the money certificate and collect the electronic money.

In another possible scenario, the electronic device may search for nearby payment devices through the short-range communication module. The electronic device may send a payment request to the payment device via a short-range communication protocol. The payment device may send a message containing the monetary credentials in response to the payment request. The electronic device may collect electronic money according to the money voucher and store the electronic money in the secure element.

Referring to fig. 3 to 5, fig. 6 is a schematic diagram of an autopilot system according to an embodiment of the present application. In the embodiments provided herein, the autopilot system may be used to complete electronic transactions in addition to autopilot.

The autopilot system as shown in fig. 6 includes a computer system 201, wherein the computer system 201 includes a processor 203, the processor 203 being coupled to a system bus 205. The processor 203 may be one or more processors, each of which may include one or more processor cores. A display adapter 207, which may drive a display 209, the display 209 being coupled to the system bus 205. The system bus 205 is coupled to an input/output (I/O) bus via a bus bridge 211. I/O interface 215 is coupled to an I/O bus. The I/O interface 215 communicates with a variety of I/O devices such as an input device 217 (e.g., keyboard, mouse, touch screen, etc.), a multimedia disk 221 (e.g., CD-ROM (compact disc read-only memory), a multimedia interface, etc.). A transceiver 223 (which may transmit and/or receive radio communication signals), a camera 255 (which may capture Jing Tian and dynamic digital video images), and an external universal serial bus (universal serial bus, USB) interface 225. Wherein the interface to which I/O interface 215 is optionally connected may be a USB interface.

The processor 203 may be any conventional processor, including a reduced instruction set computing (reduced instruction set computer, RISC) processor, a complex instruction set computing (complex instruction set computer, CISC) processor, or a combination thereof. In the alternative, the processor may be a dedicated device such as an application specific integrated circuit (application specific integrated circuit, ASIC). Alternatively, the processor 203 may be a neural network processor or a combination of a neural network processor and the conventional processors described above.

Alternatively, in various embodiments described herein, the computer system 201 may be located remotely from the autonomous vehicle and may be in wireless communication with the autonomous vehicle. In other aspects, some of the processes described herein are performed on a processor disposed within the autonomous vehicle, others are performed by a remote processor, including taking the actions required to perform a single maneuver.

The computer 201 may communicate with a software deploying server 249 via a network interface 229. The software deploying server 249 may correspond to the server 320 shown in fig. 4, for example. The network interface 229 is a hardware network interface, such as a network card. The network 227 may be an external network, such as the Internet, or an internal network, such as an Ethernet or virtual private network (virtual private network, VPN). Optionally, the network 227 may also be a wireless network, such as a WiFi network, cellular network, or the like.

The hard drive interface is coupled to the system bus 205. The hardware driver interface 231 is connected to the hard drive 233. System memory 235 is coupled to system bus 205. The data running in system memory 235 may include an operating system 237 and application programs 243 for computer 201.

The operating system includes a parser 239 (shell) and a kernel 241 (kernel). Shell 239 is an interface between the user and the kernel (kernel) of the operating system. A shell is the outermost layer of the operating system. Shell manages interactions between users and the operating system: waiting for user input, interpreting the user input to the operating system, and processing output results of a variety of operating systems.

Kernel 241 is comprised of those portions of the operating system that are used to manage memory, files, peripherals, and system resources. The operating system kernel typically runs processes and provides inter-process communication, CPU time slice management, interrupts, memory management, input-output management, and the like.

The application programs 243 include programs 247 related to controlling the automatic driving of the automobile, such as programs for managing interaction between the automatically driven automobile and obstacles on the road, programs for controlling the route or speed of the automatically driven automobile, programs for controlling interaction between the automatically driven automobile and other automatically driven automobiles on the road, programs for controlling the automatically driven automobile to avoid collision with other vehicles, programs for safely passing through an intersection, and programs for controlling the automatically driven automobile to start or close auxiliary automatic driving functions. The application 243 may also include an electronic transaction program 245 to implement a cash-out function and/or a payment function. The application 243 may correspond to the application shown in fig. 5, for example.

Application 243 may also exist on the system of the copying server 249. In one embodiment, computer system 201 may download application 243 from a depleting server when execution of application 243 is desired.

A sensor 253 is associated with the computer system 201. The sensor 253 is used to detect the environment around the computer 201. For example, the sensor 253 may detect animals, automobiles, obstacles, crosswalks, etc., and the sensor may further detect the environment surrounding such animals, automobiles, obstacles, crosswalks, etc., such as: the environment surrounding the animal, e.g., other animals present around the animal, weather conditions, the brightness of the surrounding environment, etc. Alternatively, if computer 201 is located on an autonomous car, the sensor may be a camera, infrared sensor, chemical detector, microphone, or the like.

The following describes a new payment method and various application scenarios of the payment method provided by the present application in conjunction with the electronic devices (such as vehicles) shown in fig. 1 to 6. In addition, the application combines various application scenes of the payment method, and describes the execution steps and beneficial effects of the payment method.

Fig. 7 is a schematic diagram of an application scenario of a payment method according to an embodiment of the present application.

Fig. 8 is a schematic flow chart of a payment method provided by an embodiment of the present application. It should be understood that the specific execution sequence of the steps of the payment method in the present application may not be limited to the embodiments shown in the drawings. The embodiments shown in fig. 7 and 8 may be applied to, for example, an unmanned vehicle or a general vehicle. Fig. 8 illustrates the implementation of the payment method provided by the present application, taking a vehicle as an example. In other embodiments, the steps shown in FIG. 8 may be performed by other electronic devices.

Suppose a vehicle is going from city a to city C. The vehicle may use the navigation function to obtain a navigation path from city a to city C. As shown in fig. 7, the travel path may be routed to service area B, which may provide fueling services for the vehicle. The vehicle can travel from city A to service area B according to the navigation path, and travel to service area C after the service area B is refueled.

When the vehicle travels to the gas station of the service area B, the collection device at the gas station can acquire the identification information of the vehicle. After the vehicle is completely refueled, the collection device at the gas station can also acquire the refueled quantity of the vehicle. The collection device at the gas station may generate a fuel bill based on the identification information of the vehicle and the fuel charge amount, and the fuel bill may be associated with the identification information of the vehicle.

In one embodiment, the identification information of the vehicle may include, for example, license plate information of the vehicle or electronic account information of the vehicle owner, etc. In another embodiment, the vehicle and the collection device at the gas station may communicate wirelessly when the vehicle is in proximity to the collection device at the gas station. The identification information of the vehicle may also include a wireless communication identification of the vehicle, such as an IP address, identity (ID) information, topology information, or the like, used by the vehicle when interacting with nearby devices.

The vehicle may obtain oil delta information for the vehicle after refueling. In one embodiment, the vehicle may record the amount of fuel in the fuel tank as fuel 1 before the vehicle begins to refuel. After the vehicle is refueled, the vehicle can record the oil quantity in the oil tank as oil quantity 2. The difference between the oil amount 2 and the oil amount 1 may be the oil increment information of the vehicle. Referring to fig. 3, the vehicle may obtain oil volume from the energy source 219 via the control system 206, and thus oil delta information. When the amount of oil in the oil tank increases, the vehicle can trigger an oil fee payment process.

In some embodiments, the vehicle may trigger recording of the oil delta information when an increase in the amount of oil in the vehicle's oil tank occurs. In other embodiments, the vehicle may periodically record the amount of fuel in the fuel tank, and the most recent fuel peaks and fuel valleys may indicate the fuel delta information.

The oil delta information may also be used to indicate to the vehicle, in one possible scenario, a transaction related to fuel. For example, the oil delta information may be used to instruct the vehicle to pay an oil fee to a fuel company (e.g., a collection device located at a gas station); as another example, the oil delta information may be used to indicate that the vehicle is completing a transaction in which the payment entry is an oil fee.

After the fueling is complete, the vehicle may perform a fuel charge payment procedure. The vehicle may search for nearby collection devices. Assume that the collection devices searched by the vehicle include a collection device a1 and a collection device a2, wherein the collection device a1 is a collection device located at a gas station, and the collection device a2 is a collection device of a food provider.

In one embodiment, the vehicle may interact with transaction information with a plurality of checkout devices that the vehicle is seeking. In another embodiment, the vehicle may preferentially interact with transaction information with the closest checkout device. In yet another embodiment, the vehicle may select an appropriate checkout device from a plurality of checkout devices based on an identification of the checkout device (e.g., a name of a checkout account in which the checkout device is registered). For example, the identification of the collection device a1 is related to fuel, the identification of the collection device a2 is related to food, and the fee to be paid by the vehicle is related to fuel, so that the vehicle can determine transaction information to be interacted with the collection device a1 according to the identification of the plurality of collection devices searched for. In one possible scenario, the vehicle may establish a wireless communication connection with the checkout device a1 to interact transaction information. In another possible scenario, the vehicle and the collection device a1 may interact transaction information through a cloud device. The cloud device may be, for example, the server 320 shown in fig. 4. The cloud device may in turn be, for example, a software deployment server 249 shown in fig. 6.

As shown at 801 in fig. 8, the collection device a1 may transmit the transaction information 1 to the vehicle, and accordingly, the vehicle may acquire the transaction information 1 from the collection device a 1. The transaction information 1 may be a payment request or a bill. The transaction information 1 may include an amount to be paid 1, i.e. the amount of the oil charge the vehicle needs to pay. In some embodiments provided by the present application, transaction information 1 may also include, but is not limited to, one or more of the following: a collection account, a payment account, a charging rule, a payment entry, an order occurrence time, an order payment time limit, an order number, and the like.

As shown at 802 in fig. 8, the vehicle may determine whether the transaction information 1 is abnormal according to the oil increment information of the vehicle and a preset charging rule. As shown in fig. 7, the vehicle may acquire the oil charge rule: the cost per liter of oil is 1. The oil charge rule may be a preset charging rule.

In one possible scenario, the vehicle may make a trade contract with the fuel company to which the gas station corresponds, which may contain a fuel rate rule.

In another possible scenario, the vehicle may contract with a third party company (e.g., a third party trading platform), where the third party company may contract with a fuel company to which the fuel station corresponds. The oil fee rules may be included in a transaction contract made by a third party company and the vehicle. The vehicle may receive the service provided by the fuel company through a third party company.

In one embodiment, during a fuel rate transaction, the vehicle may send an indication to a collection device located at a fuel station, which may indicate that the vehicle has contracted a transaction with a third party company. Accordingly, the collection device at the gas station may receive the indication information from the vehicle and provide the service related to the third party company to the vehicle according to the indication information.

As at 803 in fig. 8, if transaction information 1 is reasonable or there is no anomaly, the vehicle may pay to the collection device a1 for transaction information 1; if the transaction information 1 is unreasonable or abnormal, the vehicle may refuse to pay the payment receiving device a1 for the transaction information 1 or complete the transaction at the direction of the user.

In the following, by way of a number of examples, it is explained how the vehicle judges whether the transaction information 1 is abnormal or not.

In one example, transaction information 1 may satisfy the following conditions: the collection account in the transaction information 1 is a fuel company corresponding to a gas station; the payment account in the transaction information 1 is a license plate of a vehicle, a communication identifier of the vehicle, an electronic account of the vehicle, and the like; the amount to be paid 1=/house1 (oil amount 2-oil amount 1) ("amount to be paid 1 house (oil amount 2-oil amount 1)" in the transaction information 1 may mean that the difference between the amount to be paid 1 house and the amount 1 house (oil amount 2-oil amount 1) is less than or equal to a preset threshold value, and the amount 1 house (oil amount 2-oil amount 1) may be the estimated amount to be paid by the vehicle); the payment entry in the transaction information 1 is an oil fee entry; the oil charge rule in the transaction information 1 is matched with a preset charge rule; the time difference between the order occurrence time and the vehicle refueling completion time in the transaction information 1 is smaller than or equal to the preset time; the order payment time limit in the transaction information 1 is matched with the payment time limit agreed in the preset charging rule; the order number in the transaction information 1 is matched with an order number rule agreed in a preset charging rule, and the like. Thus, the vehicle can judge that the transaction information 1 is reasonable, i.e. no abnormality exists, and the vehicle can continue the subsequent payment flow with the collection device a 1. The vehicle may pay the amount to be paid 1 to the collection device a 1.

In the application, the matching of the information A and the information B can refer to that the information A and the information B are the same or similar, or the information A and the information B belong to the same or similar type, can refer to that the association degree of the information A and the information B is relatively large, and can refer to that the difference between the information A and the information B is relatively small.

In another example, transaction information 1 satisfies any of the following conditions: the collection account in the transaction information 1 is not matched with the gas station where the vehicle is currently located; the payment account in the transaction information 1 is not matched with the license plate of the vehicle or the communication identifier of the vehicle or the electronic account of the vehicle; the difference between the amount to be paid 1 and the fee 1 (oil quantity 2-oil quantity 1) in the transaction information 1 is larger than a preset threshold value; the payment entry in transaction information 1 does not match the oil fee entry; the oil charge rule in the transaction information 1 is not matched with the preset charge rule; the time difference between the order occurrence time and the vehicle refueling completion time in the transaction information 1 is larger than the preset time; the order payment time limit in the transaction information 1 is not matched with the payment time limit agreed in the preset charging rule; the order number in the transaction information 1 is not matched with the order number rule agreed in the preset charging rule, and the like. Thus, the vehicle can judge that the transaction information 1 is unreasonable, that is, that there is an abnormality.

In one possible scenario, the vehicle may refuse to pay the amount to be paid 1 to the collection device a 1. In one embodiment, the user may complete the payment of the oil charge by other means (e.g., scanning a two-dimensional code, cash payment, etc.).

In another possible scenario, the vehicle may complete the oil fee payment at the direction of the user. In one embodiment, the vehicle may prompt the user for a transaction anomaly, requesting the user to confirm the transaction details. The vehicle may pay the amount to be paid 1 to the collection device a1 for the transaction information 1 in response to the confirmation of the user.

In the application, the information A and the information B are not matched, which means that the information A and the information B are different, or the information A and the information B are not of the same or similar type, or the association degree of the information A and the information B is small, or the difference between the information A and the information B is large.

In other possible examples, the amount of information contained in the transaction information 1 may be more or less, and the judgment condition of the vehicle may be more or less.

In some embodiments, the vehicle may also obtain transaction information 1' from the checkout device a 2. The vehicle may determine that the transaction information 1 'is abnormal according to one or more of the amount to be paid, the collection account, the payment account, the charging rule, the payment entry, the order occurrence time, the order payment time limit, and the order number in the transaction information 1'. For example, the collection account in the transaction information 1 'is independent of the fuel, so there is an abnormality in the transaction information 1'. The vehicle may refuse to pay the checkout device a 2.

In the embodiment provided by the application, the vehicle can check whether the payment request from the merchant is abnormal according to the agreement between the user and the merchant, which is beneficial to reducing the information quantity of manual check. Under the condition that the manual confirmation is not carried out, the vehicle can automatically complete the transaction flow, thereby being beneficial to reducing operations required by users to complete the electronic transaction and reducing time consumption of the electronic transaction. The vehicle can also reject unreasonable transactions without human confirmation, which is beneficial to reducing the possibility of the user account being stolen.

In the embodiment provided by the application, the vehicle can judge the account for paying the oil fee according to the condition in the vehicle. That is, the vehicle may select at least one account from among a vehicle owner account, a driver account, and a passenger account as an account for paying the oil fee. As shown in fig. 9, the vehicle may pay the fee for the transaction information 1 to the collection device a1 through one or more of a vehicle owner account, a driver account, and a passenger account.

In some embodiments, the vehicle may incorporate information about the vehicle, such as by a camera, microphone, etc. The vehicle can judge whether personnel are in the vehicle, whether a driver is in the vehicle, whether the driver is a vehicle owner and the like according to the related information in the vehicle. If no personnel are present in the vehicle, the vehicle may determine to pay the oil fee through the owner's account. If there is a passenger in the vehicle but no driver, the vehicle may determine to pay the fuel fee through the passenger account. If there is a driver in the vehicle and the driver is not the owner of the vehicle, the vehicle may determine to pay the oil fee through the driver's account. If there is a driver in the vehicle and the driver is the owner of the vehicle, the vehicle may determine that the oil charge is paid through the owner account.

In one scenario provided by the application, a vehicle owner may borrow a vehicle from a friend of the vehicle owner. The fee paid by the owner's friend(s) when using the vehicle may be paid by the owner's friend(s). If the vehicle directly deducts funds from the vehicle owner's account, the vehicle owner may experience an economic loss.

To facilitate the vehicle debiting the driver or passenger account, in one embodiment, the vehicle may establish an association with the driver or passenger account. In other embodiments, the owner account, driver account, or passenger account may store the oil charge or a portion of the oil charge in a transaction module of the vehicle itself, and the vehicle may pay the oil charge through the transaction module of the vehicle itself to a collection device located at the gas station. The step of storing at least a portion of the oil charge on the transaction module may be performed before or after or simultaneously with the transaction module completing the payment of the oil charge. The transaction module may be the transaction module shown in fig. 5.

In one possible scenario, a vehicle may determine that an oil charge may be amortized by a plurality of passengers in the vehicle based on information associated with the vehicle. The vehicle may issue an indication (e.g., a voice indication, as well as display an indication message on a display screen) to a plurality of passengers instructing the plurality of passengers to store the flat fee in a transaction module of the vehicle. The vehicle may interact with the electronic devices of the plurality of passengers, for example, by way of short-range communications (e.g., bump-to-bump), etc., so that the plurality of passengers may store the flat oil charge on the transaction module of the vehicle.

In one embodiment, the passenger may store a fee generated by spreading the oil fee on the transaction module after the transaction module of the vehicle completes the payment of the oil fee, which may be the same as the amount 1 to be paid in the transaction information 1.

In another embodiment, the passenger may store a fee generated by spreading the fuel fee on the transaction module before the transaction module of the vehicle completes payment of the fuel fee, which may be the same as the fuel fee estimated by the vehicle.

In another possible scenario, the vehicle may also determine that the oil charge may be paid by the driver or the vehicle owner. Embodiments in which the driver or owner pays the oil fee through the transaction module of the vehicle may refer to the description of the previous scenario.

Alternatively, the vehicle may indicate to the occupants that the fee collection is complete after collecting the fee from the owner's account, the driver's account, or the passenger's account.

In yet another possible scenario, the vehicle may determine whether to indicate a payment of the fee in the vehicle based on whether there are personnel in the vehicle. The fee payment situation may include, for example, completion of payment of the oil fee, abnormality of payment of the oil fee, or confirmation of the oil fee transaction information, etc. If personnel are in the vehicle, the vehicle can indicate the payment condition of the fee in the vehicle, for example, by means of voice indication, indication information displayed on a display screen and the like. If no personnel are present in the vehicle, in some embodiments, the vehicle may send an indication to an electronic device that is bound to the vehicle to indicate a payment of the vehicle. For example, an electronic device bound to a vehicle may use the same electronic account as the vehicle; as another example, an electronic device bound to a vehicle may establish an association with the vehicle. If no personnel are in the vehicle, in other embodiments, the vehicle may report the payment status of the vehicle to the cloud device, so that the user may query the payment status of the vehicle through the cloud device. Thus, the vehicle can communicate the payment to the user relatively accurately.

Fig. 10 shows a schematic flow chart of a method of payment by a transaction module according to an embodiment of the present application.

1001, the checkout device may establish a wireless communication connection with the payment device. Either of the collection device and the payment device may be an electronic device (such as a vehicle) provided by the present application.

The payment device may establish a wireless communication connection with the collection device, meaning that the payment device may establish a data transmission channel for data communication with the collection device. In one embodiment, the payment device may establish a short-range wireless communication connection with the collection device. That is, the distance between the payment device and the collection device is relatively close. In another embodiment, the payment device may establish a wireless communication connection with the collection device through the cloud device.

In some embodiments, the checkout device and the payment device may establish a wireless communication connection through a wireless communication protocol.

For example, the checkout device may be in data communication with the payment device, such as via a Bluetooth communication protocol. For example, the checkout device may send a message to the payment device via a bluetooth communication protocol; accordingly, the payment device may send a message to the checkout device via a bluetooth communication protocol.

As another example, the checkout device and the payment device may access the same wireless local area network, which may be provided by a communication service device (e.g., router 301 in fig. 5). The checkout device and the payment device may communicate through a communication service device. For example, the checkout device may send message 1 to the communication service device, which message 1 may be forwarded by the communication service device to the checkout device; accordingly, the payment device may send message 2 to the communication service device, which message 2 may be forwarded by the communication service device to the collection device.

In other embodiments, the payment device may be in data communication with a cloud server (e.g., may be server 320 shown in fig. 4) via a mobile communications network; the checkout device may be in data communication with the cloud server over a mobile communication network. That is, the cloud server may relay messages between the payment device and the collection device. In one embodiment, the cloud server may obtain the location of the payment device, the collection device. When the distance between the payment device and the collection device is smaller than the preset distance, the cloud server can indicate that the collection device exists around the payment device to the payment device, and the cloud server can also indicate that the payment device exists around the collection device to the collection device.

1002, the checkout device sends transaction information to the payment device. Accordingly, the payment device obtains transaction information from the collection device.

The payment device may receive transaction information from the payment device, for example, through a communication module of the payment device. The communication module may forward the transaction information to a processing module of the payment device. The processing module of the payment device may be, for example, a module with processing capabilities. The processing module may be a hardware module or a software module. In some embodiments, the processing module may be an application of the electronic device shown in FIG. 5.

After the provider of the collecting device, or a partner cooperating with the provider of the collecting device, provides services or goods, etc. to the user using the collecting device, the collecting device may provide transaction information, which may be a payment request or a bill, to the collecting device, which may be information about the amount to be paid by the collecting device. The payment device may obtain information about the amount to be paid based on the transaction information provided by the payment device. The transaction information may include an amount to be paid. In some embodiments, the transaction information may also include, but is not limited to, one or more of the following: a collection account, a payment account, a charging rule, a payment entry, an order occurrence time, an order payment time limit, an order number, and the like. For an embodiment of transaction information reference may be made to transaction information 1 in the embodiment shown in fig. 8.

The processing module of the payment device obtains 1003 information related to the transaction information.

The transaction information may trigger the processing module to obtain information related to the transaction information. The processing module may obtain information related to the transaction information, for example, by reading, receiving, or sensing. The information related to the transaction information may include, but is not limited to, one or more of the following: payment account, device information, location information, preset charging rules, and time information.

The payment account may be an electronic account in which the payment device is registered, or may be an identification of the payment device, such as a license plate of the vehicle, or a wireless communication identification of the vehicle.

The device information may refer to a hardware state of the device, such as a remaining oil amount of the oil tank, a remaining amount of the battery, and the like.

The location information may refer to a current location, a historical location, etc. of the payment device.

The preset charging rule may refer to the preset charging rule in the embodiment shown in fig. 8.

The time information may refer to the time at which the payment device performs various operations, such as the start time of the payment device refueling, the time at which the location of the payment device is located in the service area B, and the like.

1004, the processing module of the payment device sends transaction information, as well as information related to the transaction information, to a trusted execution environment of the payment device. Accordingly, the trusted execution environment may receive transaction information and information related to the transaction information from the processing module.

1005, the trusted execution environment judges whether the transaction information is abnormal according to the transaction information and the information related to the transaction information.

The trusted execution environment may be, for example, the trusted execution environment shown in fig. 5. Information related to the transaction information may be used to confirm whether the transaction information is anomalous. And judging whether the transaction information is abnormal or not through the trusted execution environment, so that the payment equipment can check the transaction information before paying the currency.

For example, the device information may include oil delta information. The trusted execution environment can determine whether the transaction information is abnormal or not according to the oil increment information and the preset charging rule.

In some embodiments, the preset charging rules may also be maintained by the trusted execution environment. The trusted execution environment may directly read the preset charging rules instead of retrieving the preset charging rules from the processing module. The trusted execution environment independently maintains preset charging rules, which is beneficial to safely maintaining the electronic equipment to perform legal transaction.

As another example, the device information may include oil delta information, which may indicate that a collection account, payment entry, etc. is associated with the fuel. The trusted execution environment can judge whether a collection account, a payment entry and the like in the transaction information are related to fuel oil according to the oil increment information, so as to determine whether the transaction information is abnormal.

For another example, the trusted execution environment may obtain a payment account and compare it to information in the transaction information for the payment account. If so, the trusted execution environment may confirm that there is no exception to the transaction information. If not, the trusted execution environment may confirm that the transaction information is abnormal.

For another example, the trusted execution environment may obtain a preset charging rule and compare with the charging rule in the transaction information. If the two match, the trusted execution environment may confirm that there is no exception to the transaction information. If the two do not match, the trusted execution environment can confirm that the transaction information is abnormal.

As another example, the trusted execution environment may obtain location information of the vehicle and location information of the payee indicated by the transaction information. If the location of the vehicle is closer to the location of the payee, the trusted execution environment may confirm that the transaction information is not anomalous. If the location of the vehicle is far from the location of the payee, the trusted execution environment may confirm that the transaction information is anomalous.

As another example, the payment device may compare the time of receipt of the transaction information with the time of occurrence of the order in the transaction information based on the determination. If the time difference is smaller than the preset time, the payment device can confirm that no abnormality exists in the order occurrence time of the transaction information. If the time difference is larger than the preset time, the payment equipment can confirm that the order occurrence time of the transaction information is abnormal.

1006, in the event that there is no abnormality in the transaction information, the trusted execution environment of the payment device sends payment instructions to the secure element. Accordingly, the secure element may receive payment instructions from the trusted execution environment.

The trusted execution environment may verify that the transaction information is not abnormal, thereby instructing the secure element to operate the electronic money. The security element may be the security element shown in fig. 5. In some embodiments, the payment instructions may be signed, for example, by a factory preset key of the payment device. In other embodiments, payment instructions may be transmitted to the secure element through a hardware-level secure channel.

In one possible scenario, the trusted execution environment may send instructions to the processing module to decline payment in the event of an abnormality in the transaction information. Accordingly, the processing module may receive instructions to decline payment from the trusted execution environment and perform other operations. For example, the processing module completes the subsequent payment at the direction of the user. As another example, the processing module prompts the user for an abnormality in the transaction or prompts the user for a transaction abort.

1007, the secure element of the payment device operates the electronic money according to the payment instruction to generate a money voucher of the electronic money.

The operation of the security element on the electronic money may include storing money, extracting money, converting money types, and the like. The secure element may extract the electronic money stored by the secure element and generate a money voucher for the corresponding amount according to the payment instruction. The currency credential may be converted by hardware storing electronic currency, and the currency credential may be an interactive signaling containing electronic currency. In one embodiment, the monetary credential may include a credential signature and an amount. The credential signature may be used for verification of the monetary credential. The amount may indicate the amount of electronic money the amount contains.

In some embodiments, the payment instructions may include a security key. The secure element may verify the secure key in the payment instruction. In case of a successful verification, the secure element may operate the electronic money stored in itself.

The secure element of the payment device may send 1008 the monetary credentials of the electronic currency to the processing module. Accordingly, the processing module may receive currency notes of electronic currency from the secure element.

Optionally, the processing module may perform operations such as packaging, encrypting, etc. on the currency document of electronic currency, to form a payment message containing the currency document of electronic currency.

1009, the payment apparatus transmits a money voucher of the electronic money to the collection apparatus. Accordingly, the money receiving apparatus may receive the money voucher of the electronic money from the payment apparatus.

The processing module of the payment device may transmit a message containing the money voucher of the electronic money to the communication module of the payment device, and transmit a message containing the money voucher of the electronic money to the collection device by the communication module. In other embodiments, the secure element of the payment device may send a message containing the currency credential of the electronic currency to the payment device, i.e. bypassing the processing module, via the communication module of the payment device.

1010, the payment receiving device completes the payment process according to the money certificate of the electronic money.

In some embodiments, the money receiving apparatus may perform unpacking, verification, etc. of a message including a money voucher of electronic money, and collect electronic money of a corresponding amount according to the money voucher of electronic money.

In one embodiment shown in FIG. 10, the checkout device and the payment device may complete the transaction via a short-range communication technology. The electronic money is operated by the safety element, so that the communication times between the vehicle and the cloud end equipment in the transaction process can be reduced, and the vehicle can relatively smoothly complete the transaction under the condition of poor mobile communication network service.

Fig. 11 is a schematic flow chart of another payment method provided by an embodiment of the present application. It should be understood that the specific execution sequence of the steps of the payment method in the present application may not be limited to the embodiments shown in the drawings. The embodiment shown in fig. 11 may be applied to an unmanned vehicle or a general vehicle, for example. Fig. 11 illustrates an implementation procedure of the payment method provided by the present application by taking a vehicle as an example. In other embodiments, the steps shown in FIG. 11 may be performed by other electronic devices. A payment method provided by the embodiment of the present application is described below with reference to fig. 7 and 11.

The vehicle may travel from city a to city C, for example, by unmanned, manual, etc. The vehicle may use the navigation function to obtain a navigation path from city a to city C, as shown in fig. 7. When the vehicle exits city a, the vehicle may enter the highway from the highway entrance of city a. In one embodiment, the camera of the vehicle may capture a high speed entrance image of city a so that the vehicle may record the vehicle's passage through the high speed entrance of city a. In another embodiment, the vehicle may determine that the vehicle passes through the high speed entrance of city a based on its own travel path. Thereafter, the vehicle may travel to city C according to the navigation path. When the vehicle is driven into city C, the vehicle can be driven out of the expressway from the expressway of city C. In one embodiment, the vehicle's camera may capture a high speed exit image of city C so that the vehicle may record the vehicle's passage through the city C's high speed exit. In another embodiment, the vehicle may determine that the vehicle passes through the high-speed exit of city C according to its own travel path.

The user can pay a high-speed toll while passing through the high-speed toll gate. In the embodiment shown in fig. 7 and 11, the high-speed exit may have a function of collecting a high-speed toll, i.e., the high-speed exit of city C may be a high-speed toll gate. The high speed entrances and exits through which the vehicle passes may indicate a specific amount of high speed toll the vehicle is to pay.

In some embodiments, the vehicle may determine, based on the navigation path and the location of the vehicle, a payment procedure that triggers the vehicle to perform a high speed toll when the vehicle approaches the high speed exit of city C. In other embodiments, the vehicle may search for surrounding electronic devices, and when a checkout device is found to be present in the surrounding high-speed toll collection, the vehicle may determine to trigger a payment process for the high-speed toll.

In one embodiment, as shown in fig. 12, after the vehicle triggers the payment process of the high-speed toll, the vehicle can reduce the running speed of the vehicle, which is beneficial to prolonging the passable duration of the vehicle running to the collection device of the high-speed toll collection department, and reserving time for the payment process of the high-speed toll. Alternatively, after the vehicle completes the payment process of the high-speed toll, the vehicle may increase the traveling speed to pass through the high-speed toll gate quickly.

When the vehicle approaches the high-speed exit, the device near the high-speed exit can sense the vehicle and acquire the identification information of the vehicle. For example, a camera near a high speed exit may capture the license plate of a vehicle. As another example, when the vehicle passes through the high speed portal, the vehicle may report the wireless communication identity of the vehicle to a device located at the high speed portal; when the vehicle is located near the high speed exit, the vehicle may report the wireless communication identification of the vehicle to a device located at the high speed exit. The collection device positioned at the high-speed exit can determine that the vehicle enters the high-speed entrance at high speed according to the identification information of the vehicle, so as to determine the high-speed toll to be paid by the vehicle.

When the vehicle approaches the high-speed exit, the vehicle may search for a checkout device located at the high-speed exit and may establish a wireless communication connection with the checkout device. It is assumed that the vehicle searches around a plurality of electronic devices including the high speed collection device b1, the high speed collection device b2, and may further include other vehicles in the vicinity of the vehicle, such as the vehicle b3. Among them, the highway reception device b1 is a reception device on the highway 1, that is, the highway reception device b1 is used to collect a high-speed toll of the vehicle traveling on the highway 1. The highway charging device b2 is a charging device on the highway 2, and the highway charging device b2 is used to charge a highway toll fee of a vehicle traveling on the highway 2. It is assumed that the vehicle is currently traveling on the highway 1.

In one embodiment, the vehicle may interact with transaction information with a plurality of checkout devices that the vehicle is seeking. In another embodiment, the vehicle may preferentially interact with transaction information with the closest checkout device. In yet another embodiment, the vehicle may select an appropriate checkout device from a plurality of checkout devices based on an identification of the checkout device (e.g., a name of a checkout account in which the checkout device is registered). For example, the identification of the collection device b1 is associated with the expressway 1, the identification of the collection device b2 is associated with the expressway 2, and the identification of the vehicle b3 is associated with the vehicle. The fee to be paid by the vehicle is related to the high-speed toll, and the vehicle can determine that the vehicle is currently running on the highway 1 by means of positioning, photographing road identification, etc., so that the vehicle can determine transaction information to be interacted with the collection device b1 according to the identification of the plurality of collection devices searched for. In one possible scenario, the vehicle may establish a wireless communication connection with the checkout device b1 to interact transaction information. In another possible scenario, the vehicle and the checkout device b1 may interact through a cloud device. The cloud device may be, for example, the server 320 shown in fig. 4. The cloud device may in turn be, for example, a software deployment server 249 shown in fig. 6.

As shown at 1101 in fig. 11, the collection device b1 may transmit the transaction information 2 to the vehicle, and accordingly, the vehicle may acquire the transaction information 2 from the collection device b 1. The transaction information 2 may include an amount to be paid 2, i.e. a high speed toll amount the vehicle needs to pay. In some embodiments provided by the present application, transaction information 2 may also include, but is not limited to, one or more of the following: a collection account, a payment account, a charging rule, a payment entry, an order occurrence time, an order payment time limit, an order number, and the like.

As shown at 1102 in fig. 11, the vehicle may determine whether the transaction information 2 is abnormal according to the high-speed entrance and the high-speed exit through which the vehicle passes and a preset charging rule. In the example shown in fig. 7, the vehicle can acquire a high-speed toll rule: the high-speed transit charge for city a to city C is charge 2. The high-speed toll rule may be a preset toll rule.

In one possible scenario, the vehicle may contract with a high-speed toll company, which may contain a toll rule for high-speed toll fees.

In another possible scenario, the vehicle may contract with a third party company, which may contract with a high-speed toll company. The charging rules for the high-speed toll may be contained in a transaction contract made by a third party company and the vehicle. The vehicle may receive a high-speed passing service provided by a high-speed toll company through a third party company.

Specific embodiments of the vehicle acquiring preset charging rules may refer to 802 in fig. 8.

In yet another possible scenario, the vehicle may contract with a third party company. A third party company may contract with multiple merchants. In connection with the embodiments shown in fig. 7 to 13, the third party company may contract with the high-speed toll company and the fuel company, and the user may obtain services provided by the high-speed toll company and the fuel company from the third party company by contracting with the third party company for a transaction. A third party company may provide a package to the user, the package including a high speed transit fee from city a to city C, and an oil fee from service area B for providing a high speed transit service from city a to city C associated with a high speed toll company, and a fueling service at server B, wherein the high speed transit fee from city a to city C is associated with a fueling company. The user may purchase the package and the vehicle may then obtain package credentials for the package. During the travel of the vehicle from city a to city C, the vehicle may pass through the package voucher, through the high speed entrance of city a, refuel at server B, and through the high speed exit of city C. In other possible embodiments, packages may also include providing more or fewer services.

As 1103 in fig. 11, if transaction information 2 is reasonable or there is no anomaly, the vehicle may pay to the collection device b1 for transaction information 2; if there is an abnormality in the transaction information 2, the vehicle may refuse to pay the collecting device b1 for the transaction information 2, or complete the transaction under the direction of the user.

In the following, by way of a number of examples, it is explained how the vehicle determines whether the transaction information 2 is abnormal.

In one example, transaction information 2 may satisfy the following conditions: the collection account in the transaction information 2 is the account of the high-speed collection device b 1; the payment account in the transaction information 2 is a license plate of the vehicle, a communication identifier of the vehicle, an electronic account of the vehicle and the like; the amount to be paid 2=/≡fee 2 ("amount to be paid 2≡fee 2)" in the transaction information 2 may mean that the difference between the amount to be paid 2 and the fee 2 is less than or equal to a preset threshold value); the payment item in the transaction information 2 is a high-speed toll item; the charging rules in the transaction information 2 are matched with preset charging rules; the time difference between the order occurrence time in the transaction information 2 and the time when the vehicle is located near the high-speed exit is less than or equal to a preset time; the order payment time limit in the transaction information 2 is matched with the payment time limit agreed in the preset charging rule; the order number in the transaction information 2 is matched with an order number rule agreed in a preset charging rule, and the like. Thus, the vehicle can judge that the transaction information 2 is reasonable, that is, no abnormality exists, and the vehicle can continue the subsequent payment flow with the collection device b 1. The vehicle may pay the amount 2 to be paid to the collection device b 1.

In another example, transaction information 2 satisfies any of the following conditions: the collection account in the transaction information 2 is not matched with the collection device b 1; the payment account in the transaction information 2 is not matched with the license plate of the vehicle or the communication identifier of the vehicle or the electronic account of the vehicle; the difference between the amount to be paid 2 and the fee 2 in the transaction information 2 is larger than a preset threshold value; the payment items in the transaction information 2 are not matched with the high-speed toll; the charging rules in the transaction information 2 are not matched with the preset charging rules; the time difference between the order occurrence time in the transaction information 2 and the time when the vehicle is located near the high-speed exit is greater than the preset time; the order payment time limit in the transaction information 2 is not matched with the payment time limit agreed in the preset charging rule; the order number in the transaction information 2 is not matched with the order number rule agreed in the preset charging rule, and the like. Thus, the vehicle can judge that the transaction information 2 is unreasonable, that is, that there is an abnormality. In one possible scenario, the vehicle may refuse to pay the amount 2 to be paid to the collection device b 1; in another possible scenario, the vehicle may complete the oil fee payment at the direction of the user, and reference may be made to the foregoing examples for specific implementations.

In other possible examples, the amount of information contained in the transaction information 2 may be more or less, and the judgment condition of the vehicle may be more or less.

In the case where there is no abnormality in the transaction information 2, the vehicle may pay the high-speed toll fee to the collecting device b1 for the transaction information 2 through one or more of the owner account, the driver account, and the passenger account, and the foregoing embodiments may be referred to for specific implementations.

In some embodiments, the vehicle may also obtain erroneous transaction information 2' from the checkout device b2, the vehicle b3, etc. The vehicle may determine that the transaction information 2 'is abnormal according to one or more of the amount to be paid, the collection account, the payment account, the charging rule, the payment entry, the order occurrence time, the order payment time limit, and the order number in the transaction information 2'. The vehicle may refuse to pay the amount to the collection device b2, the vehicle b3, or the like. Therefore, the vehicle is beneficial to reducing the information quantity of manual verification under the condition that the vehicle is not manually confirmed, reducing the operation required by a user for completing the electronic transaction, reducing the time consumption of the electronic transaction and reducing the possibility of the account of the user being stolen and brushed.

In the embodiment provided by the application, the vehicle can confirm whether to adjust the passing path according to the payment condition of the high-speed passing fee, the driving mode of the vehicle, the condition in the vehicle and the like. As shown in fig. 13, the high-speed exits in front of the vehicle may include a manual toll gate, an ETC toll gate, an unmanned toll gate. The vehicle is driven on the high-speed path and is continuously close to the manual toll gate, the ETC toll gate and the unmanned toll gate.

In one possible case, the vehicle can also judge whether to run on the path of the unmanned toll gate according to the payment condition of the high-speed toll. In one embodiment, the vehicle may complete payment of the high speed toll with a collection device located at the unmanned toll gate. The vehicle may determine to travel on the path of the unmanned toll gate based on the payment result. In another embodiment, the vehicle may refuse to pay a high-speed toll fee from a collection device located at the unmanned toll gate. The vehicle may determine to travel on a path on which the ETC toll gate or the manual toll gate is located based on the payment result. Further, the vehicle may determine whether to travel on a path where the ETC charge outlet is located based on whether the vehicle binds the ETC account. If the vehicle is bound to the ETC account, the vehicle may pass through the ETC exit and the vehicle may then determine to travel on the path that the ETC exit is located. If the vehicle is not bound to the ETC account, the vehicle may not pass through the ETC exit and the vehicle may then determine to travel on the path of the manual exit.

In another possible case, the vehicle may also determine whether to travel on a path where the unmanned toll gate is located according to a driving mode in which the vehicle is located. If the vehicle is in the unmanned mode, the vehicle may determine to travel on the ETC toll gate or the path that the unmanned toll gate is located on. If the vehicle is in manual driving mode, the vehicle may determine to travel on the ETC gate or the path along which the manual gate is located. In one embodiment, when the vehicle is located near the unmanned toll gate, the vehicle may confirm to the user whether to switch the driving mode from the manual driving mode to the unmanned mode in order for the vehicle to pass through the unmanned toll gate. The vehicle may switch the manual driving mode to the unmanned mode in response to a confirmation operation by the user, and determine to travel on a path where the unmanned toll gate is located.

In yet another possible scenario, the vehicle may also determine whether to travel on the path of the toll gate by determining whether there are people in the vehicle. If there is a person in the vehicle, the vehicle has a certain probability of using the manual driving mode, and the vehicle can determine to travel on the ETC toll gate or the path on which the toll gate is located. If no person is present in the vehicle, the vehicle may not be able to perform the manual driving mode and the vehicle may determine to travel on the path of the ETC toll gate or the unmanned toll gate.

In other embodiments, the number of toll exits in front of the vehicle may be greater or lesser. The vehicle may select the appropriate toll exit to pass through among more or fewer toll exits.

In some embodiments provided by the application, if the vehicle determines that the vehicle runs along the path of the unmanned toll gate and the vehicle judges that the transaction information provided by the collecting device at the unmanned toll gate is abnormal, the vehicle can pay the high-speed toll fee according to the transaction information and prompt the user that the transaction information is abnormal. The user can check the transaction information again according to the instruction of the vehicle and confirm whether the complaint is subsequently submitted to the high-speed toll booth.

In other embodiments provided by the application, if the vehicle determines that the vehicle is driving on the path of the unmanned toll gate and the vehicle determines that the transaction information provided by the collecting device at the unmanned toll gate is abnormal, the vehicle can refuse to pay the high-speed toll fee for the transaction information and timely transfer the toll gate to the path of the ETC toll gate or the manual toll gate.

The payment method provided by the application can be applied to unmanned scenes and other scenes.

In one possible scenario, the vehicle is intended to stay in a parking garage. When a vehicle enters the parking garage, the vehicle may pass through the entrance of the parking garage. A device at the entrance of the parking garage may sense the vehicle, obtain identification information of the vehicle, and determine a time 1 at which the vehicle enters the parking garage, which time 1 may be associated with the identification information of the vehicle. Accordingly, the vehicle may record the moment 1' when the vehicle enters the parking garage when passing through the entrance of the parking garage. When a vehicle exits the parking garage, the device at the exit of the parking garage may sense the vehicle, acquire identification information of the vehicle, and determine a time 2 at which the vehicle is at the exit of the parking garage, the time 2 may be associated with the identification information of the vehicle. Accordingly, the vehicle may record time 2' when the vehicle is at the exit of the parking garage. The collection device at the exit of the parking garage can determine the time length (time 2-time 1) that the vehicle stays in the parking garage according to the identification information of the vehicle, and then determine the parking fee to be paid by the vehicle according to the parking fee rule.

When the vehicle approaches the exit of the parking garage, the vehicle may search for a checkout device c located at the exit of the parking garage and may establish a wireless communication connection with the checkout device c. The collection device c may send transaction information 3 to the vehicle, and the transaction information 3 may include an amount 3 to be paid, i.e., a parking fee amount that the vehicle needs to pay. In some embodiments provided by the present application, transaction information 3 may also include, but is not limited to, one or more of the following: a collection account, a payment account, a charging rule, a payment entry, an order occurrence time, an order payment time limit, an order number, and the like. Accordingly, the vehicle can acquire the transaction information 3 from the collection device c. The vehicle can judge whether the transaction information 3 is abnormal or not according to the duration of stay in the parking garage (time 2 '-time 1') and the preset charging rules (including the preset parking fee rules). If there is no abnormality in the transaction information 3, the vehicle may pay the collection device c for the transaction information 3; if there is an abnormality in the transaction information 3, the vehicle may refuse to pay the collection device c for the transaction information 3 or complete the payment at the direction of the user.

In another possible scenario, the vehicle is intended to be charged at a charging stake. The vehicle may be connected with a charging stake, which may be used to provide the vehicle with power. The vehicle can determine the time to be charged or the amount to be charged according to the self remaining power. The vehicle may also interact with the charging peg for a time to be charged or for a charge to be charged. The charging pile can determine charging fees required to be paid by the vehicle according to the time to be charged or the charging amount to be charged provided by the vehicle and the electric fee rule. The charging stake may interact with the vehicle with transaction information 4, the transaction information 4 may indicate a charge fee the vehicle is required to pay. Accordingly, the vehicle can acquire the transaction information 4 from the charging stake. The vehicle may determine whether the transaction information 4 is abnormal according to a preset charging rule (including a preset electric charge rule), and a time to be charged or an actual charging time period of the vehicle or an actual charging amount of the vehicle. If there is no abnormality in the transaction information 4, the vehicle may pay the charging stake for the transaction information 4; if there is an anomaly in the transaction information 4, the vehicle may refuse to pay the charging stake for the transaction information 4 or complete the payment at the direction of the user.

1401, the collecting device transmits transaction information to the payment device, the transaction information indicating an amount to be paid. Accordingly, the payment device receives transaction information from the collection device.

1402, the payment device determines whether the transaction information is abnormal according to a preset charging rule.

1403, in the case where there is no abnormality in the transaction, the payment device pays the amount to be paid to the collection device. Accordingly, the checkout device receives the amount to be paid from the payment device; in the event of an abnormality in the transaction information, the payment device aborts the transaction with the collection device or completes the transaction with the collection device at the direction of the user.

Fig. 15 shows a schematic block diagram of an apparatus 1500 provided by an embodiment of the application. The apparatus 1500 may be disposed in the payment device or the electronic device or a payment module of the payment device or a payment module of the electronic device, where the apparatus 1500 includes: a receiving unit 1510 for receiving transaction information from a cash register, the transaction information indicating an amount to be paid; a processing unit 1520, configured to determine whether the transaction information is abnormal according to a preset charging rule; the processing unit 1520 is further configured to, in a case where there is no abnormality in the transaction, pay the amount to be paid to the collection device by the payment device; the processing unit 1520 is further configured to suspend the transaction with the collecting device or complete the transaction with the collecting device under the instruction of the user in case that there is an abnormality in the transaction information.

Fig. 16 shows a schematic block diagram of an apparatus 1600 provided by an embodiment of the present application. The apparatus 1600 may be disposed in the collection device, or the electronic device, or a payment module of the collection device, or a payment module of the electronic device, where the apparatus 1600 includes: a transmitting unit 1610, configured to transmit transaction information to the payment device, where the transaction information indicates an amount to be paid; a receiving unit 1620 for receiving the amount to be paid from the payment device.

Fig. 17 shows a schematic structural diagram of an electronic device 1700 provided by an embodiment of the present application. As shown in fig. 17, the electronic device includes: one or more processors 1710, one or more memories 1720, the one or more memories 1720 storing one or more computer programs, the one or more computer programs comprising instructions. The instructions, when executed by the one or more processors 1710, cause the electronic device 1700 to perform the technical solutions of any one of the payment device and the collection device sides in the above embodiments.

An embodiment of the present application provides a computer program product, which, when run on a payment device, causes the payment device to perform the technical solutions of the above embodiments. The implementation principle and technical effects are similar to those of the related embodiments of the method, and are not repeated here.

An embodiment of the present application provides a computer program product, which when executed on a collection device, causes the collection device to execute the technical solution in the foregoing embodiment. The implementation principle and technical effects are similar to those of the related embodiments of the method, and are not repeated here.

An embodiment of the present application provides a readable storage medium containing instructions that, when executed on a payment device, cause the payment device to perform the technical solution of the above embodiment. The implementation principle and technical effect are similar, and are not repeated here.

An embodiment of the present application provides a readable storage medium, where the readable storage medium contains instructions that, when executed by a collection device, cause the collection device to execute the technical solution of the foregoing embodiment. The implementation principle and technical effect are similar, and are not repeated here.

The embodiment of the application provides a chip for executing instructions, and when the chip runs, the technical scheme of any one of the payment equipment and the collection equipment in the embodiment is executed. The implementation principle and technical effect are similar, and are not repeated here.

Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

It will be clear to those skilled in the art that, for convenience and brevity of description, specific working procedures of the above-described systems, apparatuses and units may refer to corresponding procedures in the foregoing method embodiments, and are not repeated herein.

In the several embodiments provided by the present application, it should be understood that the disclosed systems, devices, and methods may be implemented in other manners. For example, the apparatus embodiments described above are merely illustrative, e.g., the division of the units is merely a logical function division, and there may be additional divisions when actually implemented, e.g., multiple units or components may be combined or integrated into another system, or some features may be omitted or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices or units, which may be in electrical, mechanical or other form.

The units described as separate units may or may not be physically separate, and units shown as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

In addition, each functional unit in the embodiments of the present application may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit.

The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application may be embodied essentially or in a part contributing to the prior art or in a part of the technical solution, in the form of a software product stored in a storage medium, comprising several instructions for causing a computer device (which may be a personal computer, a server, a network device, etc.) to perform all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a random access Memory (Random Access Memory, RAM), a magnetic disk, or an optical disk, or other various media capable of storing program codes.

The foregoing is merely illustrative of the present application, and the present application is not limited thereto, and any person skilled in the art will readily recognize that variations or substitutions are within the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

1. A payment method, wherein the payment method is applied to a payment device, the payment method comprising:

2. The payment method according to claim 1, wherein the determining whether the transaction information is abnormal according to the preset charging rule comprises:

3. The payment method of claim 2, wherein the device information includes oil delta information.

4. A payment method as claimed in claim 2, wherein the location information indicates an entrance and an exit through which the payment device passes.

5. A payment method as claimed in claim 2, wherein the time information indicates the time of passage of the payment device through the entrance and the time of passage through the exit.

6. A payment method as claimed in any one of claims 1 to 5, wherein the payment device is applied to a vehicle, the payment method further comprising:

7. The payment method of claim 6, wherein the payment method further comprises:

8. The payment method as set forth in any one of claims 1 to 7, wherein the payment apparatus is applied to a vehicle, the payment method further comprising:

and controlling the vehicle to reduce the running speed.

9. The payment method as recited in claim 8, wherein after the payment of the amount to be paid to the collection device, the payment method further comprises:

and controlling the vehicle to increase the running speed.

10. The payment method as recited in any one of claims 1 to 9, wherein the payment device is applied to a vehicle, and wherein in the event that there is no abnormality in the transaction, the payment method further comprises:

controlling the vehicle to pass through an unmanned toll gate.

11. A payment method as claimed in any one of claims 1 to 10, wherein the payment device is applied to a vehicle, the payment method further comprising, in the event of an anomaly in the transaction:

12. The payment method according to any one of claims 1 to 11, wherein the payment device has a trusted execution environment for determining whether there is an abnormality in the transaction, and a secure element for operating electronic money, and wherein in the case where there is no abnormality in the transaction, the payment to the payment device includes:

the secure element sends the currency credential to the collection device.

13. The payment method of claim 12, wherein the trusted execution environment is configured to store the preset charging rules.

14. A payment method as claimed in any one of claims 1 to 13, wherein the transaction information is further indicative of one or more of: a collection account, a payment account, a charging rule, a payment entry, an order occurrence time, an order payment time limit, and an order number.

15. A payment method as claimed in any one of claims 1 to 14, wherein the pre-set charging rules are included in a contract made by a user of the payment device and a user of the collection device, or

16. A payment device, comprising:

17. An electronic device, comprising:

one or more processors;

one or more memories;

The one or more memories store one or more computer programs comprising instructions that, when executed by the one or more processors, cause the electronic device to perform the payment method of any of claims 1-15.

18. A non-transitory computer readable storage medium comprising computer instructions that, when executed on an electronic device, cause the electronic device to perform the payment method of any of claims 1 to 15.

19. A computer program product containing instructions which, when run on an electronic device, cause the electronic device to perform the payment method of any of claims 1 to 15.