Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are some embodiments of the present application, but not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
For the purpose of facilitating understanding of the embodiments of the present application, the following description will be made in terms of specific embodiments with reference to the accompanying drawings, which are not intended to limit the embodiments of the present application.
The payment method, the payment client, the charging device and the control method and system thereof are suitable for a scene that a user pays through the charging device, particularly suitable for a scene that the user pays through the charging device bound with the payment client in advance, and can be applied to a scene that payment is needed, such as parking charging and the like.
It should be noted that the payment client may be a client of a payment wallet, which runs on a terminal device, where the terminal device may be a mobile phone or a tablet computer. The charging device is movable, for example, an IC card or other hardware device that can be conveniently carried, and is provided with a sensor and a timer, wherein the sensor is used for sensing the change of the position, and the timer is used for timing, and the timing unit can be an hour or times. In different application scenarios, the payment client may also be other clients with payment functions, and the charging device may also be a device of other forms, as long as it can count time to count charging time.
Fig. 1 is a flowchart of a payment method according to an embodiment of the present application. An execution subject of the method may be a payment client, as shown in fig. 1, and the method may specifically include:
in step 110, the payment client obtains an identifier of the charging device.
And step 120, the payment client establishes a data connection with the charging device according to the identifier of the charging device.
For example, in a parking lot, the charging device is placed in the control system in advance, when a vehicle enters the parking lot and a user takes the charging device from the control system by pressing a button on the control system or in other ways, the control system detects that the charging device is taken out, and the handrail is controlled to lift up to release the vehicle; and the charging equipment can sense that the position is changed through the sensor, so that the timer is activated to start timing.
Optionally, a two-dimensional code is arranged on the charging device;
the payment client acquiring the identifier of the charging device comprises:
and the payment client side obtains the identifier of the charging equipment by scanning the two-dimensional code.
Optionally, the identifier of the charging device is a bluetooth address of the charging device;
the payment client establishes data connection with the charging device according to the identifier of the charging device, and the data connection comprises the following steps:
and the payment client establishes data connection with the charging equipment according to the Bluetooth address of the charging equipment.
That is, for the above charging device that has started timing, the payment client may establish data connection with the charging device in two ways: the first mode is a mode of scanning a two-dimensional code; the second mode is a bluetooth mode.
In a first manner, for example, a two-dimensional code is arranged on the charging device, and after the payment client is operated, the two-dimensional code on the charging device can be scanned through a scanning function of the payment client, so as to obtain an identifier of the charging device; after acquiring the identifier of the charging equipment, the payment client stores the identifier of the charging equipment and initiates a request for establishing data connection; after the charging device returns the confirmation message, the data connection is established between the payment client and the charging device.
A second way, for example, a "bluetooth" function may be added in the "service window" of the payment client; after the payment client is operated, when the newly added Bluetooth function is opened, the payment client can search, when the Bluetooth function of the charging equipment is started and the distance between the charging equipment and the payment client is smaller than a threshold value (for example, 10m), the payment client can obtain the Bluetooth address of the charging equipment, store the Bluetooth address of the charging equipment, initiate a pairing request to the charging equipment according to the Bluetooth address of the charging equipment, and after the pairing is successful, establish data connection between the payment client and the charging equipment.
Of course, in practical applications, the connection between the payment client and the charging device may be established in different manners as needed, for example, through a wifi network or the like.
Step 130, when the payment client receives a payment instruction input by a user, sending a reading instruction to the charging device.
After the data connection between the payment client and the charging device is established, the payment operation can be performed by the payment client. For example, in a parking lot, when a vehicle is ready to leave the parking lot, a user may send a payment instruction to a payment client, where a "pay parking fee" function may be added in a "service window" of the payment client in advance, that is, the user needs to send the payment instruction after the "pay parking fee" function is started; the payment instruction may be used to instruct the payment client to send a read instruction to the charging device with which the data connection is established.
And step 140, the payment client receives the charging information read by the charging device according to the reading instruction, and executes payment operation according to the charging information.
After receiving the reading instruction, the charging device reads the charging duration of the charging device and the payment amount per unit time, wherein the charging duration refers to the current timing time of a timer of the charging device, and the payment amount per unit time is stored in the charging device in advance. After reading the charging time length and the payment amount of unit time, the charging equipment sends the read charging time length and the payment amount of unit time to a payment client; or, the total payment amount can be obtained according to the read charging duration and the payment amount in unit time, and then the obtained total payment amount is sent to the payment client; that is, the charging information includes the charging duration and the payment amount per unit time; alternatively, the billing information includes a total payment amount.
Further, the performing the payment operation according to the billing information in step 140 may further include: and executing payment operation through a wireless network wifi or a beacon network according to the charging information.
That is, after receiving the charging information sent by the charging device, the payment client may perform the payment operation in two ways: the first way is to execute payment operation through wireless network wifi; the second way is to perform payment operations through the beacon network.
The first mode is suitable for a scene with a smooth network, and under the scene, the terminal device of the payment client and the payment server can be connected to the same router so as to ensure that the network of the terminal device and the network of the payment server are in the same network segment. Since it is the prior art to perform payment operations in such a scenario, it is not described herein in detail.
The second method is applicable to a scene with an obstructed network, see a beacon network schematic diagram provided in the present application shown in fig. 2, where the beacon network includes at least one charging device, a control system, and a gateway, where the gateway is used to manage communication between the charging device and other devices (e.g., the control system) in the beacon network, and is responsible for sending a request to a server (e.g., a payment server) in an external network or receiving a response message; the control system is used for reading the completion state (such as completed payment and uncompleted payment) and completion time of the payment operation of the charging equipment and judging whether the charging equipment is overtime according to the completion time.
In fig. 2, after receiving the charging information sent by the charging device, the payment client sends a payment request to the charging device, and the charging device forwards the payment request to the payment server through a gateway in the beacon network, where the payment request includes the received charging information and may also include a payment account and a payment password of the payment client; after receiving the payment request, the payment server judges whether the charging information is the total payment amount, if not, the payment server firstly obtains the total payment amount according to the charging duration and the payment amount in unit time, and then executes payment operation according to the payment account number, the payment password and the total payment amount; and if so, directly executing payment operation according to the payment account number, the payment password and the total payment amount. And after the payment server pays the payment operation, the payment server returns payment result information to the charging equipment through the gateway in the beacon network, and the charging equipment forwards the payment result information to the payment client. After receiving the payment result information, the charging device may record the completion status and the completion time of the payment operation.
As in the foregoing example, when the vehicle reaches the exit of the parking lot, the user puts the charging device back to the control system, at this time, the control system reads and judges the completion status and completion time of the payment operation of the charging device, and if the completion status is that payment is completed and the interval duration between the completion time and the current time is not greater than the threshold time (i.e., is not overtime), the barrier is controlled to open the released vehicle; and if the completion state is that the payment is not completed or the time is out, returning to the charging equipment, and informing the user of completing the payment or filling up the balance through voice or other modes.
Here, when the control system determines that the completion state of the charging device is that payment is completed and the interval duration between the completion time and the current time is not greater than the threshold time (i.e., not overtime), an emptying instruction is sent to the charging device, where the emptying instruction is used to trigger the charging device to disconnect the data connection with the payment client and stop charging.
To sum up, in the second payment method, the payment client sends a payment request to the charging device, the charging device forwards the payment request to the payment server through the gateway of the beacon network, and after the payment server performs a payment operation (e.g., a collection operation), payment result information is returned to the payment client through the gateway and the charging device. Therefore, in the payment process, the payment client does not directly interact with the payment server, namely, the terminal equipment to which the payment client belongs is not required to be directly connected with the external network, but the charging equipment and the gateway realize transfer, namely, the payment process firstly passes through the beacon network and then is connected with the external network, so that the problem that the payment operation cannot be executed when the payment client and the payment server cannot directly communicate is solved. In addition, through the billing device, the user can complete payment at any place of the parking lot without queuing up for payment to a fixed-location charging terminal area, thereby being capable of bringing great convenience to the user.
Optionally, the method further comprises:
when the payment client receives a positioning instruction input by a user, acquiring the position information of the charging equipment and the position information of the terminal equipment to which the payment client belongs through a beacon network according to the identifier of the charging equipment;
and the payment client generates navigation line information according to the position information of the charging equipment and the position information of the terminal equipment to which the payment client belongs.
Here, a "vehicle positioning" function may be added in the "service window" of the payment client;
as in the foregoing example, when the vehicle enters the parking lot and is parked at any position in the parking lot, assuming that the data connection between the billing device and the payment client has been established at this time, the billing device may be placed in the vehicle, and then the user leaves; when a user needs to get a vehicle, a vehicle positioning function of the payment client is started, and a positioning instruction is input; when the payment client receives the positioning instruction, the identifier of the charging device stored in step 210 is read, a positioning request is sent to a gateway of the beacon network, the positioning request comprises the identifier of the charging device and the identifier of the terminal device to which the payment client belongs, the gateway positions the charging device and the terminal device to obtain the position information of the charging device and the position information of the terminal device, the obtained position information of the charging device and the obtained position information of the terminal device are sent to the payment client, and the payment client generates navigation line information according to the position information of the charging device and the position information of the terminal device to which the payment client belongs, so that a user can conveniently search vehicles in a parking lot.
Fig. 3 is a flowchart of a payment method provided in the second embodiment of the present application, where an execution subject of the method may be a charging device, and as shown in fig. 3, the method may specifically include:
in step 310, the charging device receives a request for establishing a data connection sent by a payment client.
For example, in a parking lot, the charging device is placed in the control system in advance, when a vehicle enters the parking lot and a user takes the charging device from the control system by pressing a button on the control system or in other ways, the control system detects that the charging device is taken out, and the handrail is controlled to lift up to release the vehicle; and the charging equipment can sense that the position is changed through the sensor, so that the timer is activated to start timing.
In step 320, the charging device returns a response message to the payment client to establish a data connection with the payment client.
For the charging device which starts timing, the payment client can establish data connection with the charging device in two ways: the first mode is a mode of scanning a two-dimensional code; the second mode is a bluetooth mode.
In a first manner, for example, a two-dimensional code is arranged on the charging device, and after the payment client is operated, the two-dimensional code on the charging device can be scanned through a scanning function of the payment client, so as to obtain an identifier of the charging device; after acquiring the identifier of the charging equipment, the payment client stores the identifier of the charging equipment and initiates a request for establishing data connection; after the charging device returns the confirmation message, the data connection is established between the payment client and the charging device.
The second way, for example, needs to add a new bluetooth function in the service window of the payment client; after the payment client is operated, when the newly added Bluetooth function is opened, the payment client can search, when the Bluetooth function of the charging equipment is started and the distance between the charging equipment and the payment client is smaller than a threshold value (for example, 10m), the payment client can obtain the Bluetooth address of the charging equipment, store the Bluetooth address of the charging equipment, initiate a pairing request to the charging equipment according to the Bluetooth address of the charging equipment, and after the pairing is successful, establish data connection between the payment client and the charging equipment.
In step 330, the charging device receives a reading instruction sent by the payment client when receiving a payment instruction input by a user.
After the data connection between the payment client and the charging device is established, the payment operation can be performed by the payment client. For example, in a parking lot, when a vehicle is ready to leave the parking lot, a user may send a payment instruction to a payment client, where a "pay parking fee" function may be added in a "service window" of the payment client in advance, that is, the user needs to send the payment instruction after the "pay parking fee" function is started; the payment instruction may be used to instruct the payment client to send a read instruction to the charging device with which the data connection is established.
And 340, the charging equipment reads the charging information according to the reading instruction and sends the charging information to the payment client so that the payment client executes payment operation according to the charging information.
After receiving the reading instruction, the charging device reads the charging duration of the charging device and the payment amount per unit time, wherein the charging duration refers to the current timing time of a timer of the charging device, and the payment amount per unit time is stored in the charging device in advance.
After reading the charging time length and the payment amount of unit time, the charging equipment sends the read charging time length and the payment amount of unit time to a payment client; or, the total payment amount can be obtained according to the read charging duration and the payment amount in unit time, and then the obtained total payment amount is sent to the payment client; that is, the charging information includes the charging duration and the payment amount per unit time; alternatively, the billing information includes a total payment amount.
After receiving the charging information sent by the charging equipment, the payment client sends a payment request to the payment server, wherein the payment request comprises the received charging information and can also comprise a payment account number and a payment password of the payment client; after receiving the payment request, the payment server judges whether the charging information is the total payment amount, if not, the payment server firstly obtains the total payment amount according to the charging duration and the payment amount in unit time, and then executes payment operation according to the payment account number, the payment password and the total payment amount; and if so, directly executing payment operation according to the payment account number, the payment password and the total payment amount. And after the payment operation is paid, the payment server returns payment result information to the payment client, and the payment client forwards the payment result information to the charging equipment. After receiving the payment result information, the charging device may record the completion status and the completion time of the payment operation.
Optionally, the method further comprises:
and the charging equipment receives an emptying instruction, wherein the emptying instruction is used for triggering the charging equipment to disconnect the data connection with the payment client and stop charging.
As in the foregoing example, when the vehicle reaches the exit of the parking lot, the user puts the charging device back to the control system, at this time, the control system reads and judges the completion status and completion time of the payment operation of the charging device, and if the completion status is that payment is completed and the interval duration between the completion time and the current time is not greater than the threshold time (i.e., is not overtime), the barrier is controlled to open the released vehicle; and if the completion state is that the payment is not completed or the time is out, returning to the charging equipment, and informing the user of completing the payment or filling up the balance through voice or other modes.
Through the payment method, the user can complete payment at any place of the parking lot without queuing to the fixed-position charging terminal area, so that great convenience can be brought to the user.
Fig. 4 is a flowchart of a control method of a charging device according to a third embodiment of the present application. The execution subject of the method may be a control system, as shown in fig. 1, and the method may specifically include:
in step 410, the control system obtains an identifier of a billing device, which has previously established a data connection with the payment client.
And step 420, the control system reads the completion state and completion time of the payment operation recorded in the billing device according to the identifier of the billing device.
And 430, when the completion state is that the payment is completed and the completion time is not timed out, sending an emptying instruction to the charging equipment so that the charging equipment is disconnected from the data connection with the payment client and stops charging.
For example, when a vehicle reaches the entrance of the parking lot, and a user takes the charging equipment from the control system by pressing a button on the control system or other modes, the control system detects that the charging equipment is taken out, and the control handrail is lifted to release the vehicle; and when the vehicle drives away from the exit of the parking lot, the user puts the charging device back to the control system, wherein the charging device establishes a data connection with the payment client in advance. At the moment, the control system reads the identifier of the charging equipment, judges the completion state and completion time of the payment operation of the charging equipment according to the identifier of the charging equipment, and sends an emptying instruction to the charging equipment if the completion state is that payment is completed and the interval duration between the completion time and the current time is not greater than the threshold time (namely, the time is not overtime), and controls the railing to lift up and release the vehicle; after receiving the emptying instruction, the charging equipment disconnects the data connection with the payment client and controls the charging equipment to stop charging; and if the completion state is that the payment is not completed or the time is out, returning to the charging equipment, and informing the user of completing the payment or filling up the balance through voice or other modes.
In the above embodiments of the payment method, the charging information read by the payment client from the charging device includes the charging duration and the payment amount per unit time, and in practical application, the charging information may also include only the charging duration, and the payment amount per unit time may be preset on the payment client or the charging server and may be read by the payment client. In addition, when the payment client performs payment, the payment client refers to a preset charging account number, for example, an account number pre-stored on a charging server, or the payment client may pre-store the charging account number, when the user determines that payment is required through the payment client, the user may pay funds in the user's own account to the charging account number, and the specific payment process of the funds is not described in detail.
In practical application, the charging device may record a payment completion status and completion time, so that the control system may determine whether the user completes payment, in other implementation manners, the charging device may also not record the payment completion status and completion time, but after the user completes payment through the payment client, the charging server may feed back the payment status of the user to the control system, and the payment status may include an identifier of the charging device, so that when the control system detects that the charging device is placed back, the control system may determine whether the user completes payment through the payment status returned by the charging server.
Corresponding to the above payment method, an embodiment of the present application further provides a payment client, as shown in fig. 5, where the payment client includes: an acquisition unit 501, a building unit 502, a sending unit 503 and a payment unit 504;
an obtaining unit 501, configured to obtain an identifier of a charging device.
Optionally, a two-dimensional code is arranged on the charging device; the obtaining unit 501 is specifically configured to:
and scanning the two-dimension code to obtain the identifier of the charging equipment.
The establishing unit 502 is configured to establish a data connection with the charging device according to the identifier of the charging device acquired by the acquiring unit 501.
Optionally, the identifier of the charging device is a bluetooth address of the charging device; the establishing unit 502 is specifically configured to:
and establishing data connection with the charging equipment according to the Bluetooth address of the charging equipment.
A sending unit 503, configured to send a reading instruction to the charging device when receiving a payment instruction input by a user.
A payment unit 504, configured to receive charging information read by the charging device according to the reading instruction sent by the sending unit 503, and execute a payment operation according to the charging information.
Optionally, the charging information includes a charging duration and a payment amount per unit time; or,
the billing information includes a total payment amount.
The payment unit 504 is specifically configured to:
and executing payment operation through a wireless network wifi or a beacon network according to the charging information.
Optionally, the apparatus further comprises: a generation unit 505;
the obtaining unit 501 is further configured to, when receiving a positioning instruction input by a user, obtain, through the beacon network, location information of the charging device and location information of a terminal device to which the payment client belongs, according to the identifier of the charging device;
a generating unit 505, configured to generate navigation line information according to the location information of the charging device and the location information of the terminal device to which the payment client belongs, which are acquired by the acquiring unit 501.
In the payment client provided in the embodiment of the present application, the obtaining unit 501 obtains an identifier of a charging device; the establishing unit 502 establishes a data connection with the charging device according to the identifier of the charging device acquired by the acquiring unit 501; when receiving a payment instruction input by a user, the sending unit 503 sends a reading instruction to the charging device; the payment unit 504 receives the charging information read by the charging device according to the reading instruction, and executes payment operation according to the charging information. Therefore, the flexibility of payment operation can be improved, and the user experience can be improved.
Corresponding to the above payment method, an embodiment of the present application further provides a charging device, as shown in fig. 6, where the charging device includes: a receiving unit 601, a returning unit 602 and a reading unit 603.
The receiving unit 601 is configured to receive a request for establishing a data connection sent by a payment client.
A returning unit 602, configured to return a response message to the payment client to establish a data connection with the payment client.
The receiving unit 601 is further configured to receive a reading instruction sent by the payment client when receiving a payment instruction input by a user.
A reading unit 603, configured to read charging information according to the reading instruction received by the receiving unit 601, and send the charging information to the payment client, so that the payment client performs a payment operation according to the charging information.
Optionally, the charging information includes a charging duration and a payment amount per unit time; or,
the billing information includes a total payment amount.
Optionally, the receiving unit 601 is further configured to receive a first message returned by the payment client after performing a payment operation, where the first message is used to trigger the charging device to record a completion state and a completion time of the payment operation.
Optionally, the receiving unit 601 is further configured to receive an emptying instruction, where the emptying instruction is used to trigger the charging device to disconnect the data connection with the payment client and stop charging.
In the charging device provided by the embodiment of the application, the receiving unit 601 receives a request for establishing data connection sent by a payment client; a returning unit 602 returns a response message to the payment client to establish a data connection with the payment client; the receiving unit 601 receives a reading instruction sent by the payment client when receiving a payment instruction input by a user; the reading unit 603 reads the charging information according to the reading instruction, and sends the charging information to the payment client, so that the payment client executes the payment operation according to the charging information. Thus, the user can complete payment at any place of the parking lot without queuing up for payment to a fixed-position charging terminal area, thereby bringing great convenience to the user.
Corresponding to the control method of the charging device, an embodiment of the present application further provides a control system of a charging device, as shown in fig. 7, where the control system includes: an acquisition unit 701, a reading unit 702, and a transmission unit 703.
An obtaining unit 701, configured to obtain an identifier of a charging device, where the charging device establishes a data connection with a payment client in advance;
a reading unit 702, configured to read, according to the identifier of the charging apparatus acquired by the acquiring unit 701, a completion state and completion time of the payment operation recorded in the charging apparatus;
a sending unit 703, configured to send an emptying instruction to the charging device when the completion status is that payment is completed and the completion time is not expired, so that the charging device disconnects data connection with the payment client and stops charging.
The control system of the charging device provided by the embodiment of the application can control the charging device to disconnect the bound payment client and stop charging when the charging device completes one-time charging, so that the charging device can be used again, and the purpose of effectively utilizing resources is achieved.
Those of skill would further appreciate that the various illustrative objects and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, computer software, or combinations of both, and that the various illustrative components and steps have been described above generally in terms of their functionality in order to clearly illustrate the interchangeability of hardware and software. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. 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.
The steps of a method or algorithm described in connection with the embodiments disclosed herein may be embodied in hardware, a software module executed by a processor, or a combination of the two. A software module may reside in Random Access Memory (RAM), memory, Read Only Memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art.
The above-mentioned embodiments, objects, technical solutions and advantages of the present application are described in further detail, it should be understood that the above-mentioned embodiments are merely exemplary embodiments of the present application, and are not intended to limit the scope of the present application, and any modifications, equivalent substitutions, improvements and the like made within the spirit and principle of the present application should be included in the scope of the present application.