Parking lot payment management method, device and equipment and storage medium

Abstract

The invention discloses a parking lot payment management method and device, equipment and a storage medium, and relates to the technical field of parking lot management, and the method comprises the steps: obtaining an order query request of a user, and the order query request comprises a parking lot identifier and vehicle information; sending the order query request to a service system of each charging service associated with the parking lot identifier, so that each service system queries a service order associated with the vehicle information; and based on the business orders returned by the business systems, generating a target combined order, and pushing the target order to the user for payment. According to the invention, the order query request is sent to the business systems of different charging businesses to obtain the business orders returned by the business systems, and then the business orders are combined to obtain the target combined order, so that the target order is pushed to the user for payment, the orders of different businesses are combined into one order, and the user experience is improved. The user does not need to pay a plurality of business fees separately, so that the parking payment convenience of the user is improved.

Description

Technical Field

[0001] The present invention relates to the technical field of parking lot management, and in particular to a parking lot payment management method, device, equipment and storage medium. Background Art

[0002] As the scope of parking services expands, the types of services provided by parking lots are also becoming increasingly diverse. For example, parking lots have added charging services for electric vehicles and are equipped with special new energy parking spaces. In order to prevent fuel vehicles from occupying these new energy parking spaces, parking lots can charge parking fees. In addition, overtime parking or illegal parking will also result in additional illegal parking fees. Since the fees for these different services may be generated by different service providers, users may need to pay for multiple different service fees separately when leaving the parking lot, which makes the payment operation more cumbersome. Summary of the invention

[0003] Based on this, it is necessary to provide a parking lot payment management method, device, equipment and storage medium to address the above technical issues, so as to solve at least one of the above technical issues.

[0004] The present invention provides a parking lot payment management method, comprising:

[0005] Obtaining an order query request from a user, wherein the order query request includes a parking lot identification and vehicle information;

[0006] Sending the order query request to the business system of each billing service associated with the parking lot identification, so that each business system can query the business order associated with the vehicle information;

[0007] Based on the business orders returned by each of the business systems, a target merged order is generated, and the target order is pushed to the user for payment.

[0008] Optionally, according to a parking lot payment management method provided by the present invention, the step of sending the order query request to a business system of each billing business associated with the parking lot identifier includes:

[0009] Determine the fee query interface address of each billing service associated with the parking lot identification;

[0010] The order query request is sent to the business system corresponding to each fee query interface address.

[0011] Optionally, according to a parking lot payment management method provided by the present invention, the business order includes fees to be paid;

[0012] The generating a target merged order based on the business orders returned by each of the business systems includes:

[0013] Determine each target business order whose pending payment fee is greater than 0 among all business orders;

[0014] The target business orders are merged to obtain the target merged order.

[0015] Optionally, according to a parking lot payment management method provided by the present invention, the step of merging the target business orders to obtain the target merged order includes:

[0016] Add up the fees to be paid in each of the target business orders to obtain the total fee;

[0017] Based on the total cost, the target combined order is generated.

[0018] Optionally, according to a parking lot payment management method provided by the present invention, after generating a target merged order based on the business orders returned by each of the business systems and pushing the target order to the user for payment, the method further includes:

[0019] When receiving a payment success notification, determining the payment notification interface address associated with each business order in the target merged order;

[0020] The payment success notification is sent to the business system corresponding to each payment notification interface address, so that the business system can modify the payment status of the business order to a paid status.

[0021] Optionally, according to a parking lot payment management method provided by the present invention, after generating a target merged order based on the business orders returned by each of the business systems and pushing the target order to the user for payment, the method further includes:

[0022] When a payment success notification is received, the payment status of the target merged order is changed to a paid status.

[0023] Optionally, according to a parking lot payment management method provided by the present invention, after generating a target merged order based on the business orders returned by each of the business systems and pushing the target order to the user for payment, the method further includes:

[0024] When a payment success notification is received, the payment success notification is sent to the exit control device of the parking lot to allow the vehicle corresponding to the vehicle information to leave.

[0025] The present invention also provides a parking lot payment management device, comprising:

[0026] An acquisition module, used to acquire an order query request from a user, wherein the order query request includes a parking lot identification and vehicle information;

[0027] A query module, used for sending the order query request to the business system of each billing business associated with the parking lot identification, so that each business system can query the business order associated with the vehicle information;

[0028] The payment module is used to generate a target merged order based on the business orders returned by each of the business systems, and push the target order to the user for payment.

[0029] The present invention also provides a computer device, comprising a memory, a processor, and computer-readable instructions stored in the memory and executable on the processor, wherein the processor implements the above-mentioned parking lot payment management method when executing the computer-readable instructions.

[0030] The present invention also provides one or more readable storage media storing computer-readable instructions, and the computer-readable instructions, when executed by a processor, implement the above-mentioned parking lot payment management method.

[0031] The parking lot payment management method, device, equipment and storage medium mentioned above include: obtaining a user's order query request, wherein the order query request includes a parking lot identification and vehicle information; sending the order query request to the business system of each billing service associated with the parking lot identification, so that each business system can query the business order associated with the vehicle information; based on the business order returned by each business system, generating a target merged order, and pushing the target order to the user for payment. The present invention sends an order query request to the business systems of different billing services to obtain the business orders returned by each business system, and then merges each business order to obtain a target merged order, thereby pushing the target order to the user for payment, thereby merging orders for different services into one order, and the user does not need to pay for multiple different business fees separately, thereby improving the convenience of the user's parking payment. BRIEF DESCRIPTION OF THE DRAWINGS

[0032] In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the accompanying drawings required for use in the description of the embodiments of the present invention will be briefly introduced below. Obviously, the accompanying drawings in the following description are only some embodiments of the present invention. For ordinary technicians in this field, other accompanying drawings can be obtained based on these accompanying drawings without paying creative labor.

[0033] Figure 1 It is one of the flow charts of the parking lot payment management method in one embodiment of the present invention;

[0034] Figure 2 is a system architecture diagram provided by an embodiment of the present invention;

[0035] Figure 3 This is the second flow chart of the parking lot payment management method in one embodiment of the present invention;

[0036] Figure 4 This is a third flow chart of a parking lot payment management method in one embodiment of the present invention;

[0037] Figure 5 It is a structural schematic diagram of a parking lot payment management device in one embodiment of the present invention;

[0038] Figure 6 is a schematic diagram of a computer device in one embodiment of the present invention. DETAILED DESCRIPTION

[0039] In order to make the purpose, technical solution and advantages of the present invention clearer, the technical solution of the present invention will be clearly and completely described below in conjunction with the drawings of the present invention. Obviously, the described embodiments are part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0040] The terms used in one or more embodiments of the present invention are only for the purpose of describing specific embodiments, and are not intended to limit one or more embodiments of the present invention. The singular forms of "a", "said" and "the" used in one or more embodiments of the present invention are also intended to include plural forms, unless the context clearly indicates other meanings. It should also be understood that the term "and / or" used in one or more embodiments of the present invention refers to and includes any or all possible combinations of one or more associated listed items.

[0041] It should be understood that, although the terms first, second, etc. may be used to describe various information in one or more embodiments of the present invention, these information should not be limited to these terms. These terms are only used to distinguish the same type of information from each other. For example, without departing from the scope of one or more embodiments of the present invention, the first may also be referred to as the second, and similarly, the second may also be referred to as the first. Depending on the context, the word "if" as used herein may be interpreted as "when..." or "when...".

[0042] As the scope of parking services expands, the types of services it provides are also becoming increasingly diverse, such as the addition of electric vehicle charging services and the provision of special new energy parking spaces. In order to prevent fuel vehicles from occupying these parking spaces, parking lots have begun to charge parking fees. In addition, overtime parking or illegal parking will also result in additional illegal parking fees. Since these fees may be generated by different service providers, users may need to pay for multiple different business fees separately when leaving the park, and the payment operation is relatively cumbersome.

[0043] In view of the above problems, the present invention provides the following embodiments. In one embodiment, Figure 1 As shown, Figure 1 The present invention provides a parking lot payment management method in accordance with an embodiment of the present invention, which includes the following steps:

[0044] Step S11, obtaining the user's order query request;

[0045] It should be noted that the order query request includes a parking lot identification and vehicle information. The vehicle information includes license plate information, vehicle type and other information. The parking lot identification refers to the identity tag of the parking lot.

[0046] In one embodiment, referring to Figure 2 , Figure 2 This is a system architecture diagram provided by one embodiment of the present invention. A user can use a user terminal to register and log in to a parking lot-related order inquiry platform (for example, an APP software, a public account, a mini-program, or a web system). In other embodiments, the user can also scan the parking lot QR code to log in to the platform, and then initiate an order inquiry request based on the vehicle information associated with the user.

[0047] In another embodiment, the user drives the vehicle to the exit identification area of ​​the parking lot, and uses a camera to identify the vehicle information of the vehicle, and then generates an order query request based on the vehicle information and the parking lot sign.

[0048] Step S12, sending the order query request to the business system of each billing service associated with the parking lot identification, so that each business system can query the business order associated with the vehicle information;

[0049] It should be noted that, refer to Figure 2 Each billing service is associated with at least one fee type, including charging fees, parking fees, parking space fees, temporary parking fees, illegal parking fees, etc. Different billing services correspond to different business managers. Optionally, the business manager can customize the fee rules, such as setting coupons or discounts. In this embodiment, the parking lot is regarded as a project plan, and a variety of different billing services are pre-configured for the parking lot. It can be understood that the platform can access the business systems of different billing services, such as: parking space-level operation, charging services, B2C parking spaces, C2C parking spaces, parking space contracting, illegal parking services, and parking lot temporary parking.

[0050] In one embodiment, the fee query interface address of each billing service associated with the parking lot identification is determined; then, an order query request is sent to the business system corresponding to each fee query interface address, so that the business system can query the service order to be paid associated with the vehicle information. Optionally, the service order includes information such as the fee to be paid, the fee type and the billing service identification. The billing service identification refers to the identity identification of the billing service, so that the fees of different billing services can be queried.

[0051] Step S13, based on the business orders returned by each business system, a target merged order is generated, and the target order is pushed to the user for payment.

[0052] It should be noted that for vehicles parked in the parking lot, it may not involve all billing services. Therefore, when querying the billing services related to the vehicle, not every service will generate a fee order that needs to be paid. It is understandable that the service order returned by the service system may be a 0 yuan order or an empty order. In one embodiment, the service orders with fees to be paid greater than 0 are merged to obtain a target merged order, and the target order is pushed to the user for payment. The user does not need to pay for multiple different service fees separately, which improves the convenience of the user's parking payment.

[0053] The embodiment of the present invention, through the above scheme, includes: obtaining the user's order query request, wherein the order query request includes the parking lot identification and vehicle information; sending the order query request to the business system of each billing service associated with the parking lot identification, so that each business system can query the business order associated with the vehicle information; based on the business order returned by each business system, generating a target merged order, and pushing the target order to the user for payment. The embodiment of the present invention sends the order query request to the business systems of different billing services to obtain the business orders returned by each business system, and then merges each business order to obtain the target merged order, so as to push the target order to the user for payment, thereby merging the orders of different services into one order, and the user does not need to pay for multiple different business fees separately, thereby improving the convenience of the user's parking payment.

[0054] like Figure 3 As shown, Figure 3 This is a second flow chart of a parking lot payment management method in an embodiment of the present invention; in an embodiment of the present invention, based on the business orders returned by each business system, a target merged order is generated, including:

[0055] Step S21, determining each target business order whose pending payment fee is greater than 0 among all business orders;

[0056] Step S22: merge the target business orders to obtain a target merged order.

[0057] In one embodiment, when querying the billing services related to the vehicle, not every service will generate a fee order that needs to be paid, and the service order returned by the service system can be a 0-yuan order or an empty order. In this embodiment, each target service order whose to-be-paid fee is greater than 0 is determined among all service orders; then the to-be-paid fees in each target service order are added up to obtain the total fee, and further, based on the total fee, a target merged order is generated. In other embodiments, in order to allow users to intuitively understand the order details, a target merged order can be generated based on the total fee, the to-be-paid fees in each target service order, the billing service identifier, and the fee type.

[0058] The embodiment of the present invention adopts the above scheme, including: determining each target business order whose to-be-paid fee is greater than 0 in all business orders; merging each target business order to obtain a target merged order. This realizes merging orders of different businesses into one order, and users do not need to pay for multiple different business fees separately, thereby improving the convenience of users' parking payment.

[0059] like Figure 4 As shown, Figure 4 This is a flow chart of the parking lot payment management method in one embodiment of the present invention; in one embodiment of the present invention, based on the business orders returned by each business system, a target merged order is generated, and the target order is pushed to the user for payment, and further includes:

[0060] Step S31, when receiving a payment success notification, determining the payment notification interface address associated with each business order in the target merged order;

[0061] Step S32, sending a payment success notification to the business system corresponding to each payment notification interface address, so that the business system can modify the payment status of the business order to a paid status.

[0062] It should be noted that the target merged order may include multiple business orders, each of which is processed by a different business system. In this embodiment, when a payment success notification is received, it is necessary to determine the payment notification interface address corresponding to each business order, where the payment notification interface address is a URL interface used by the business system to receive payment notifications. The payment success notification is then sent to the business system corresponding to each payment notification interface address, so that the business system can change the payment status of the business order from the pending payment status to the paid status.

[0063] In addition, when receiving the payment success notification, the payment status of the target merged order needs to be changed from the pending payment status to the paid status.

[0064] The embodiment of the present invention, through the above scheme, includes: when receiving a payment success notification, determining the payment notification interface address associated with each business order in the target merged order; sending the payment success notification to the business system corresponding to each payment notification interface address, so that the business system can modify the payment status of the business order to a paid status. The integrity and accuracy of the entire order processing flow is ensured, and data synchronization between various business systems is also ensured.

[0065] In one embodiment of the present invention, after generating a target merged order based on the business orders returned by each business system and pushing the target order to the user for payment, the following steps are also included:

[0066] When a payment success notification is received, the payment success notification is sent to the exit control device of the parking lot to allow the vehicle corresponding to the vehicle information to leave.

[0067] In one embodiment, when a payment success notification is received, the payment success notification is sent to the exit control device of the parking lot, so that the exit control device controls the exit gate to open, thereby allowing the vehicle corresponding to the vehicle information to leave.

[0068] Through the above scheme, the embodiment of the present invention realizes the merging of orders for different services into one order. Users do not need to pay for multiple different service fees separately, which improves the convenience of users' parking payment. After the user completes the payment, the vehicle corresponding to the vehicle information can be released to leave.

[0069] It should be understood that the order of execution of the steps in the above embodiment does not necessarily mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiment of the present invention.

[0070] In one embodiment, a parking lot payment management device is provided, which corresponds one-to-one to the parking lot payment management method in the above embodiment. Figure 5 As shown, Figure 5 1 is a schematic diagram of a parking lot payment management device in one embodiment of the present invention, the parking lot payment management device comprises:

[0071] The acquisition module 41 is used to acquire the user's order query request, wherein the order query request includes the parking lot identification and vehicle information;

[0072] The query module 42 is used to send the order query request to the business system of each billing business associated with the parking lot identification, so that each business system can query the business order associated with the vehicle information;

[0073] The payment module 43 is used to generate a target merged order based on the business orders returned by each business system, and push the target order to the user for payment.

[0074] The query module 42 is also used for:

[0075] Determine the fee query interface address of each billing service associated with the parking lot identification;

[0076] The order query request is sent to the business system corresponding to each fee query interface address.

[0077] The payment module 43 is also used for:

[0078] Determine each target business order whose pending payment fee is greater than 0 among all business orders;

[0079] The target business orders are merged to obtain a target merged order.

[0080] The payment module 43 is also used for:

[0081] Add up the fees to be paid in each target business order to get the total fee;

[0082] Based on the total cost, a target consolidated order is generated.

[0083] The parking lot payment management device also includes:

[0084] A first modification module is used to determine the payment notification interface address associated with each business order in the target merged order when receiving a payment success notification;

[0085] The sending module is used to send the payment success notification to the business system corresponding to each payment notification interface address, so that the business system can modify the payment status of the business order to the paid status.

[0086] The parking lot payment management device also includes:

[0087] The second modification module is used to modify the payment status of the target merged order to a paid status when receiving a payment success notification.

[0088] The parking lot payment management device also includes:

[0089] The release module is used to send the payment success notification to the exit control device of the parking lot when receiving the payment success notification, so as to release the vehicle corresponding to the vehicle information to leave.

[0090] The specific definition of the parking lot payment management device can be found in the definition of the parking lot payment management method above, which will not be repeated here. Each module in the above parking lot payment management device can be implemented in whole or in part by software, hardware and a combination thereof. The above modules can be embedded in or independent of the processor in the computer device in the form of hardware, or can be stored in the memory of the computer device in the form of software, so that the processor can call and execute the operations corresponding to the above modules.

[0091] In one embodiment, a computer device is provided. The computer device may be a server, and its internal structure diagram may be as follows: Figure 6 As shown, Figure 6 : is a schematic diagram of a computer device in an embodiment of the present invention. The computer device includes a processor, a memory, a network interface and a database connected by a device bus. Among them, the processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a readable storage medium and an internal memory. The readable storage medium stores an operating device, a computer-readable instruction and a database. The internal memory provides an environment for the operation of the operating device and the computer-readable instructions in the readable storage medium. The database of the computer device is used to store data involved in the parking lot payment management method. The network interface of the computer device is used to communicate with an external terminal through a network connection. When the computer-readable instruction is executed by the processor, a parking lot payment management method is implemented. The readable storage medium provided in this embodiment includes a non-volatile readable storage medium and a volatile readable storage medium.

[0092] In one embodiment, a computer device is provided. The computer device may be a terminal device, and its internal structure diagram may be as follows: Figure 6 As shown. The computer device includes a processor, a memory, and a network interface connected through a device bus. The processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a readable storage medium. The readable storage medium stores computer-readable instructions. The network interface of the computer device is used to communicate with an external terminal through a network connection. When the computer-readable instructions are executed by the processor, a parking lot payment management method is implemented. The method includes: obtaining an order query request from a user, wherein the order query request includes a parking lot identification and vehicle information; sending the order query request to the business system of each billing business associated with the parking lot identification, so that each business system can query the business order associated with the vehicle information; based on the business orders returned by each business system, a target merged order is generated, and the target order is pushed to the user for payment. The readable storage medium provided in this embodiment includes a non-volatile readable storage medium and a volatile readable storage medium.

[0093] In one embodiment, a computer device is provided, including a memory, a processor, and computer-readable instructions stored in the memory and executable on the processor, and when the processor executes the computer-readable instructions, the steps of the parking lot payment management method described above are implemented. The method includes: obtaining an order query request from a user, wherein the order query request includes a parking lot identification and vehicle information; sending the order query request to a business system of each billing business associated with the parking lot identification, so that each business system can query the business order associated with the vehicle information; generating a target merged order based on the business orders returned by each business system, and pushing the target order to the user for payment.

[0094] In one embodiment, a readable storage medium is provided, the readable storage medium stores computer-readable instructions, and when the computer-readable instructions are executed by the processor, the steps of the parking lot payment management method as described above are implemented. A person of ordinary skill in the art can understand that all or part of the processes in the above-mentioned embodiment method can be completed by instructing the relevant hardware through computer-readable instructions, and the computer-readable instructions can be stored in a non-volatile readable storage medium or a volatile readable storage medium. When the computer-readable instructions are executed, they can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to memory, storage, database or other media used in the embodiments provided in this application may include non-volatile and / or volatile memory. Non-volatile memory may include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM) or flash memory. Volatile memory may include random access memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in many forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous link (Synchlink) DRAM (SLDRAM), memory bus (Rambus) direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM), etc.

[0095] Those skilled in the art can clearly understand that for the convenience and simplicity of description, only the division of the above-mentioned functional units and modules is used as an example. In actual applications, the above-mentioned functions can be distributed and completed by different functional units and modules as needed, that is, the internal structure of the device can be divided into different functional units or modules to complete all or part of the functions described above.

[0096] The above embodiments are only used to illustrate the technical solutions of the present invention, rather than to limit the same. Although the present invention has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that the technical solutions described in the aforementioned embodiments may still be modified, or some of the technical features may be replaced by equivalents. Such modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the embodiments of the present invention, and should be included in the protection scope of the present invention.

Claims

1. A parking lot payment management method, characterized in that: include: Obtaining an order query request from a user, wherein the order query request includes a parking lot identification and vehicle information; Sending the order query request to the business system of each billing service associated with the parking lot identification, so that each business system can query the business order associated with the vehicle information; Based on the business orders returned by each of the business systems, a target merged order is generated, and the target order is pushed to the user for payment.

2. The parking lot payment management method according to claim 1, characterized in that: The step of sending the order query request to the business system of each billing business associated with the parking lot identification includes: Determine the fee query interface address of each billing service associated with the parking lot identification; The order query request is sent to the business system corresponding to each fee query interface address.

3. The parking lot payment management method according to claim 1, characterized in that: The business order includes fees to be paid; The generating a target merged order based on the business orders returned by each of the business systems includes: Determine each target business order whose pending payment fee is greater than 0 among all business orders; The target business orders are merged to obtain the target merged order.

4. The parking lot payment management method according to claim 3 is characterized in that: The step of merging the target business orders to obtain the target merged order includes: Add up the fees to be paid in each of the target business orders to obtain the total fee; Based on the total cost, the target combined order is generated.

5. The parking lot payment management method according to claim 1, characterized in that: After generating a target merged order based on the business orders returned by each of the business systems and pushing the target order to the user for payment, the method further includes: When receiving a payment success notification, determining the payment notification interface address associated with each business order in the target merged order; The payment success notification is sent to the business system corresponding to each payment notification interface address, so that the business system can modify the payment status of the business order to a paid status.

6. The parking lot payment management method according to claim 1, characterized in that: After generating a target merged order based on the business orders returned by each of the business systems and pushing the target order to the user for payment, the method further includes: When a payment success notification is received, the payment status of the target merged order is changed to a paid status.

7. The parking lot payment management method according to claim 1, characterized in that: After generating a target merged order based on the business orders returned by each of the business systems and pushing the target order to the user for payment, the method further includes: When a payment success notification is received, the payment success notification is sent to the exit control device of the parking lot to allow the vehicle corresponding to the vehicle information to leave.

8. A parking lot payment management device, characterized in that: include: An acquisition module, used to acquire an order query request from a user, wherein the order query request includes a parking lot identification and vehicle information; A query module, used for sending the order query request to the business system of each billing business associated with the parking lot identification, so that each business system can query the business order associated with the vehicle information; The payment module is used to generate a target merged order based on the business orders returned by each of the business systems, and push the target order to the user for payment.

9. A computer device comprising a memory, a processor, and computer-readable instructions stored in the memory and executed on the processor, characterized in that: When the processor executes the computer-readable instructions, the parking lot payment management method according to any one of claims 1 to 7 is implemented.

10. A readable storage medium having computer readable instructions stored thereon, characterized in that: When the computer-readable instructions are executed by a processor, the parking lot payment management method according to any one of claims 1 to 7 is implemented.

Images