Parking method and device for nested parking lot, electronic equipment and readable storage medium

Abstract

The invention provides a nested parking lot parking method and device, electronic equipment and a readable storage medium, and the method comprises the steps: generating sub-parking lot settlement information of a user vehicle for a sub-parking lot according to a payment mode of the sub-parking lot when it is monitored that the user vehicle drives away from any sub-parking lot, on the basis of a processing result of the settlement information of the sub-parking lot, controlling whether the user vehicle is released from the sub-parking lot or not; when it is monitored that the user vehicle is driven away from the parent parking lot, parent parking lot settlement information of the user vehicle to the parent parking lot is generated according to the payment mode of the user vehicle driven into each child parking lot and the child parking lot settlement information, and whether the user vehicle is released in the parent parking lot is controlled based on the processing result of the parent parking lot settlement information. Through the method, the problem of repeated charging is avoided, and the vehicle passing efficiency is improved.

Description

Technical Field

[0001] This application relates to the field of vehicle technology, and in particular to a parking method, apparatus, electronic device, and readable storage medium for nested parking lots. Background Technology

[0002] As urban parking demands become increasingly complex, the parking lot operation model in large-scale integrated areas (such as large shopping malls, transportation hubs, and industrial parks) is evolving from a single entity managing parking lots to a multi-entity, zoned operation model. This evolution has given rise to the application scenario of "nested parking lots," where multiple "child parking lot" areas, managed independently by different operators, exist within a large physical area of ​​a "parent parking lot."

[0003] However, existing parking management systems are typically designed to perform one-time exit billing and release control only for single, isolated parking lots. When applied to nested parking lot scenarios, they cannot intelligently determine whether to immediately complete settlement and release at the exit of a sub-parking lot, or to temporarily store the fee record and release it directly. They also cannot effectively aggregate and process temporary fees from multiple sub-parking lots at the exit of the parent parking lot. This can easily lead to duplicate billing for the same vehicle when it exits both the parent and sub-parking lots sequentially, negatively impacting the user experience.

[0004] Meanwhile, in existing technologies, regardless of whether a vehicle has entered a sub-parking lot within a nested parking lot, the system initiates a parking fee calculation and payment process every time the vehicle leaves the outermost parent parking lot. When applied to nested parking lots, this means that all fee calculations, information aggregation, and user interactions (such as bill confirmation and payment) must be completed at the parent parking lot exit. When a vehicle's activity within the nested parking lot is complex (e.g., multiple entries and exits from different sub-parking lots), the fees for multiple time periods need to be recalculated at the parent parking lot exit, significantly increasing the processing time per vehicle. During peak hours, this sequential, centralized processing method easily leads to exit congestion, directly reducing the vehicle throughput per unit time and impacting traffic efficiency. Summary of the Invention

[0005] In view of this, the purpose of this application is to provide a parking method, device, electronic device and readable storage medium for nested parking lots, so as to avoid the problems of duplicate billing and low billing efficiency in nested parking lots, and improve vehicle traffic efficiency.

[0006] In a first aspect, embodiments of this application provide a parking method for nested parking lots. The method is applied to a server, which is pre-configured with a nested parking lot relationship between a parent parking lot and at least one child parking lot, and a payment mode for each child parking lot. The method includes: When a user vehicle is detected leaving any of the sub-parking lots, the sub-parking lot settlement information for the user vehicle is generated according to the payment mode of the sub-parking lot, and the sub-parking lot is controlled to release the user vehicle based on the processing result of the settlement information. When a user vehicle is detected leaving the parent parking lot, the system generates parent parking lot settlement information for the user vehicle based on the payment mode and settlement information of the user vehicle in each sub-parking lot. Based on the processing result of the parent parking lot settlement information, the system controls whether the parent parking lot allows the user vehicle to leave.

[0007] In conjunction with the first aspect, this application provides a first possible implementation of the first aspect, wherein the payment mode includes an independent payment mode and a combined payment mode; when a user vehicle is detected leaving any of the sub-parking lots, according to the payment mode of that sub-parking lot, sub-parking lot settlement information for the user vehicle at that sub-parking lot is generated, and based on the processing result of the sub-parking lot settlement information, the control is made to determine whether the sub-parking lot allows the user vehicle to leave, including: When a user vehicle is detected leaving any of the sub-parking lots, if the sub-parking lot is configured with the independent payment mode, the sub-parking lot settlement information for the user vehicle is generated and pushed to the user terminal. After receiving the payment confirmation information returned by the user terminal, a release command is sent to the control equipment at the entrance and exit of the sub-parking lot. If the sub-parking lot is configured with the combined payment mode, the sub-parking lot settlement information is temporarily stored and a release command is sent to the control equipment at the entrance and exit of the sub-parking lot. When a user vehicle is detected leaving the parent parking lot, based on the user vehicle's payment mode and settlement information at each sub-parking lot, parent parking lot settlement information for the user vehicle is generated. Based on the processing result of this parent parking lot settlement information, the parent parking lot is controlled to determine whether to allow the user vehicle to leave, including: When the user vehicle is detected leaving the parent parking lot, if all vehicles already in the sub-parking lots are configured with the independent payment mode, a release command is sent to the control equipment at the entrance and exit of the parent parking lot; if there are vehicles already in the sub-parking lots configured with the combined payment mode, the parent parking lot settlement information of the user vehicle for the parent parking lot is generated based on all temporarily stored sub-parking lot settlement information and pushed to the user terminal. After receiving the payment confirmation information returned by the user terminal, a release command is sent to the control equipment at the entrance and exit of the parent parking lot.

[0008] In conjunction with the first possible implementation of the first aspect, this application provides a second possible implementation of the first aspect, wherein, before generating the sub-parking lot settlement information for the user vehicle at any of the sub-parking lots when the user vehicle is detected leaving any of the sub-parking lots, if the sub-parking lot is configured with the independent payment mode, the method further includes: When a user vehicle is detected to enter any of the sub-parking lots, the vehicle identifier of the user vehicle, the sub-parking lot identifier, and the entry time are collected. When a user vehicle is detected leaving any of the sub-parking lots, if the sub-parking lot is configured with the independent payment mode, then the sub-parking lot settlement information for the user vehicle at that sub-parking lot is generated, including: When the user's vehicle is detected leaving the sub-parking lot, if the sub-parking lot is configured with the independent payment mode, the sub-parking lot settlement information for the user's vehicle is generated based on the departure time and the entry time.

[0009] In conjunction with the first aspect, the first possible implementation of the first aspect, or the second possible implementation of the first aspect, this application provides a third possible implementation of the first aspect, wherein the server is pre-configured with billing rules and parking rights certificates for each of the sub-parking lots; the parking rights certificate includes a preset rights period, fee reduction rules, and a corresponding sub-parking lot identifier; generating the sub-parking lot settlement information for the user vehicle includes: Query the association between the user's vehicle identifier and the parking rights certificate to determine whether the user's vehicle has been associated with the parking rights certificate corresponding to the sub-parking lot; If the user's vehicle is already associated with the parking rights certificate corresponding to the sub-parking lot, then determine whether the parking time of the user's vehicle in the sub-parking lot falls within the preset rights period of the parking rights certificate; If the parking time falls within the preset period of the parking rights certificate, the parking fee payable for the sub-parking lot is calculated according to the fee reduction rules, and the sub-parking lot settlement information for the user vehicle is generated. If the user's vehicle is not associated with the parking rights certificate corresponding to the sub-parking lot, or if the parking period does not fall within the preset rights period of the parking rights certificate, the parking fee payable for the sub-parking lot will be calculated according to the billing rules of the sub-parking lot, and the sub-parking lot settlement information for the user's vehicle will be generated.

[0010] In conjunction with the third possible implementation of the first aspect, this application provides a fourth possible implementation of the first aspect, wherein the parking rights certificate further includes a target parking space identifier, the target parking space identifier being a unique identifier for a specific parking space under the sub-parking lot corresponding to the parking rights certificate; the step of querying the association and binding relationship between the user's vehicle identifier and the parking rights certificate to determine whether the user's vehicle has been associated and bound to the parking rights certificate corresponding to the sub-parking lot includes: Query all parking rights certificates associated with the user's vehicle identifier, filter out parking rights certificates that contain the sub-parking lot identifier, and extract the corresponding target parking space identifier from the parking rights certificate. Determine the parking space identifier of the user vehicle actually occupying the parking space in the sub-parking lot, and confirm whether the parking space identifier of the actually occupied parking space is consistent with the target parking space identifier extracted from the parking rights certificate; if they are consistent, it means that the user vehicle has been associated with the parking rights certificate corresponding to the sub-parking lot; if they are inconsistent, it means that the user vehicle has not been associated with the parking rights certificate corresponding to the sub-parking lot.

[0011] In conjunction with the fourth possible implementation of the first aspect, this application provides a fifth possible implementation of the first aspect, wherein the association between the user's vehicle identifier and the parking rights certificate is generated in the following manner: The system receives a parking rights purchase request sent by the user terminal; wherein the parking rights purchase request is generated by the user terminal in response to the user's selection operation of multiple pre-configured parking rights certificates; the parking rights purchase request includes the certificate identifier of the parking rights certificate specified by the user's selection operation and the vehicle identifier of the user's vehicle. Based on the credential identifier, determine whether the parking rights credential specified by the user's selection operation is bound to the vehicle identifier of another user's vehicle; If the parking rights certificate specified by the user's selection operation is not bound to the vehicle identifier of another user's vehicle, then an association binding relationship between the vehicle identifier of the user's vehicle and the parking rights certificate specified by the user's selection operation is established and stored.

[0012] In conjunction with the second possible implementation of the first aspect, this application provides a sixth possible implementation of the first aspect, wherein the server is pre-configured with billing rules for each of the sub-parking lots; after collecting the vehicle identifier of the user vehicle, the sub-parking lot identifier, and the entry time when a user vehicle is detected entering any of the sub-parking lots, the method further includes: Receive a parking fee query request sent by the user terminal; the parking fee query request includes the vehicle identifier of the user's vehicle and the current query time; Based on the vehicle identifier, query the payment mode of all sub-parking lots that the user vehicle has entered during this parking process, and obtain the entry time of the user vehicle in each sub-parking lot. For the sub-parking lots that the user's vehicle has entered during this parking process, the parking fees payable for the sub-parking lot up to the current query time are calculated in real time based on the billing rules of the sub-parking lot, the entry time of the user's vehicle, and the current query time. For the first sub-parking lot configured with the independent payment mode that has been entered, the current independent query results for each first sub-parking lot are generated based on the parking fees payable for each first sub-parking lot up to the current query time, and the current independent query results for each first sub-parking lot are pushed to the user terminal. For the second sub-parking lot configured with the combined payment mode, which has already been entered, a current combined query result for the second sub-parking lot is generated based on the parking fees payable for each sub-parking lot up to the current query time, and the current combined query result is pushed to the user terminal.

[0013] Secondly, embodiments of this application also provide a parking device for nested parking lots. The device is applied to a server, which is pre-configured with a nested relationship between a parent parking lot and at least one child parking lot, and a payment mode for each child parking lot. The device includes: The first monitoring module is used to generate the user vehicle's sub-parking lot settlement information for the sub-parking lot according to the payment mode of the sub-parking lot when it is detected that the user vehicle leaves any of the sub-parking lots, and control whether the sub-parking lot allows the user vehicle to leave based on the processing result of the sub-parking lot settlement information. The second monitoring module is used to generate parent parking lot settlement information for the user vehicle to the parent parking lot when the user vehicle leaves the parent parking lot, based on the payment mode and settlement information of the user vehicle in each sub-parking lot that it has entered, and control whether the parent parking lot allows the user vehicle to leave based on the processing result of the parent parking lot settlement information.

[0014] Thirdly, embodiments of this application also provide an electronic device, including: a processor, a memory, and a bus, wherein the memory stores machine-readable instructions executable by the processor, and when the electronic device is running, the processor communicates with the memory via the bus, and when the machine-readable instructions are executed by the processor, the steps in any of the possible implementations of the first aspect described above are performed.

[0015] Fourthly, embodiments of this application also provide a computer-readable storage medium storing a computer program, which, when executed by a processor, performs the steps in any of the possible implementations of the first aspect described above.

[0016] This application provides a parking method, apparatus, electronic device, and readable storage medium for nested parking lots. The server is pre-configured with a nested relationship between a parent parking lot and at least one child parking lot. When a user vehicle leaves any child parking lot, settlement information for that child parking lot is generated based on its payment method. This means that for any fee incurred by a user vehicle within any child parking lot, a separate, clearly defined child parking lot settlement record is generated at the moment of departure. Subsequently, when a user vehicle leaves the parent parking lot, settlement information for the parent parking lot is generated based on the payment methods and settlement information of each child parking lot the user vehicle has entered. This indicates that when summarizing fees at the final exit (parent parking lot exit), the basis is the already generated and recorded settlement information of each child parking lot, rather than recalculating the vehicle's dwell time and fees within each child parking lot independently. By calling and integrating these existing, unique sub-parking lot settlement information to generate parent parking lot settlement information, the possibility of recalculating the same parking duration or the same parking service is eliminated from the technical process, thereby avoiding duplicate billing.

[0017] Furthermore, in this embodiment, at the sub-parking lot exit level, when a user vehicle is detected leaving, the server controls whether to allow the user vehicle to leave based on the processing result of the sub-parking lot settlement information. This means that some decision-making and processing tasks (i.e., generating information based on the payment mode and determining whether to allow the vehicle to leave) are completed at intermediate nodes in the process. This avoids piling up all judgments and interactions at the final exit (parent parking lot exit), achieving the diversion of processing tasks in time and space. Secondly, at the parent parking lot exit level, when a user vehicle is detected leaving, the server generates parent parking lot settlement information based on the existing sub-parking lot settlement information and controls the vehicle to leave based on its processing result. Since the fees for each sub-parking lot have already been calculated and structured into sub-parking lot settlement information, at the parent parking lot exit, only a relatively simple sub-parking lot settlement information aggregation and merging logic needs to be executed. This greatly simplifies the processing logic at the final exit (parent parking lot exit) and shortens the processing time per vehicle.

[0018] To make the above-mentioned objectives, features and advantages of this application more apparent and understandable, preferred embodiments are described below in detail with reference to the accompanying drawings. Attached Figure Description

[0019] To more clearly illustrate the technical solutions of the embodiments of this application, the accompanying drawings used in the embodiments will be briefly introduced below. It should be understood that the following drawings only show some embodiments of this application and should not be regarded as a limitation of the scope. For those skilled in the art, other related drawings can be obtained based on these drawings without creative effort.

[0020] Figure 1 A flowchart illustrating a parking method for nested parking lots provided in an embodiment of this application is shown; Figure 2 This illustration shows a schematic diagram of a nested parking structure between a parent parking lot and a child parking lot provided in an embodiment of this application; Figure 3 This illustration shows a structural schematic diagram of a parking method apparatus for nested parking lots provided in an embodiment of this application; Figure 4 A schematic diagram of the structure of an electronic device provided in an embodiment of this application is shown. Detailed Implementation

[0021] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. The components of the embodiments of this application described and shown in the accompanying drawings can generally be arranged and designed in various different configurations. Therefore, the following detailed description of the embodiments of this application provided in the accompanying drawings is not intended to limit the scope of the claimed application, but merely represents selected embodiments of this application. All other embodiments obtained by those skilled in the art based on the embodiments of this application without inventive effort are within the scope of protection of this application.

[0022] As urban parking demands become increasingly complex, the parking lot operation model in large-scale integrated areas (such as large shopping malls, transportation hubs, and industrial parks) is evolving from a single entity managing parking lots to a multi-entity, zoned operation model. This evolution has given rise to the application scenario of "nested parking lots," where multiple "child parking lot" areas, managed independently by different operators, exist within a large physical area of ​​a "parent parking lot."

[0023] However, existing parking management systems are typically designed to perform one-time exit billing and release control only for single, isolated parking lots. When applied to nested parking lot scenarios, they cannot intelligently determine whether to immediately complete settlement and release at the exit of a sub-parking lot, or to temporarily store the fee record and release it directly. They also cannot effectively aggregate and process temporary fees from multiple sub-parking lots at the exit of the parent parking lot. This can easily lead to duplicate billing for the same vehicle when it exits both the parent and sub-parking lots sequentially, negatively impacting the user experience.

[0024] Meanwhile, in existing technologies, regardless of whether a vehicle has entered a sub-parking lot within a nested parking lot, the system initiates a parking fee calculation and payment process every time the vehicle leaves the outermost parent parking lot. When applied to nested parking lots, this means that all fee calculations, information aggregation, and user interactions (such as bill confirmation and payment) must be completed at the parent parking lot exit. When a vehicle's activity within the nested parking lot is complex (e.g., multiple entries and exits from different sub-parking lots), the fees for multiple time periods need to be recalculated at the parent parking lot exit, significantly increasing the processing time per vehicle. During peak hours, this sequential, centralized processing method easily leads to exit congestion, directly reducing the vehicle throughput per unit time and impacting traffic efficiency.

[0025] Based on this, the present application provides a parking method, apparatus, electronic device, and readable storage medium for nested parking lots to avoid the problem of duplicate billing and improve vehicle traffic efficiency. The following is a description through embodiments.

[0026] It should be noted that in this embodiment, a "parent parking lot" refers to a large parking lot with complete entrances and exits, which can be divided into one or more logically or physically independent parking areas. A "child parking lot" refers to a parking area located within the physical area of ​​the parent parking lot, with independent management attributes (such as independent billing rules and independent operators). It may have its own independent control gate or may only be logically divided. The "payment mode" is a rule pre-configured for each child parking lot, used to define how the fees incurred when a vehicle leaves the child parking lot should be handled, such as immediate settlement or temporary storage pending consolidation.

[0027] To facilitate understanding of this embodiment, a parking method for nested parking lots disclosed in this application will first be described in detail. This method is applied to a server, which is pre-configured with the nested relationship between a parent parking lot and at least one child parking lot, as well as the payment mode for each child parking lot; for example... Figure 1 As shown, the method includes the following steps S101-S102: S101: When a user vehicle is detected leaving any sub-parking lot, the user vehicle's sub-parking lot settlement information is generated according to the payment mode of that sub-parking lot, and the user vehicle is controlled to leave the sub-parking lot based on the processing result of the settlement information. S102: When a user vehicle is detected leaving the parent parking lot, the parent parking lot settlement information of the user vehicle is generated based on the payment mode and settlement information of the user vehicle in each sub-parking lot. Based on the processing result of the parent parking lot settlement information, the parent parking lot is controlled to release the user vehicle.

[0028] In step S101, as Figure 2 As shown, a sub-parking lot is a local physical area of ​​the parent parking lot. The server receives real-time data on user vehicle departure events from the exit gates or inductive loop detectors of each sub-parking lot via an IoT interface or parking lot management system. Once a user vehicle departure event is detected, the server first determines which sub-parking lot the vehicle left and reads the pre-configured payment mode for that sub-parking lot. Then, the server generates the sub-parking lot settlement information for that user vehicle based on the current billing rules (which can be calculated based on parking time or consider pre-purchased parking packages, etc.). This sub-parking lot settlement information includes at least the parking fee amount and the sub-parking lot identifier.

[0029] Next, the server controls vehicle access based on the processing result of the settlement information for that sub-parking lot. This processing result is determined by the payment method of that sub-parking lot. For example, if the payment method requires immediate settlement, the processing result might be "Payment Required, Pending Confirmation"; if the payment method allows deferred merging, the processing result might be "Recorded, Allowed to Pass." Based on the processing result generated by this internal logic, the server sends corresponding instructions to the control equipment (such as the gate controller) at the entrance and exit of that sub-parking lot, thereby controlling whether to raise the gate to allow the user's vehicle to pass.

[0030] In step S102, when the user vehicle reaches the exit of the parent parking lot, the server detects the user vehicle leaving. At this time, the server needs to perform the final settlement for this complete parking trip. It queries the records of all sub-parking lots that the user vehicle has entered during this parking process, and obtains the payment mode of these sub-parking lots as well as the previously stored sub-parking lot settlement information (such as the sub-parking lot settlement information temporarily stored in S101).

[0031] Then, the server synthesizes these temporarily stored sub-parking lot settlement information to generate parent parking lot settlement information. For example, it can aggregate the settlement information of sub-parking lots configured for combined payment mode and then overlay it with the parent parking lot settlement information generated in the public area (non-sub-parking lot area) of the parent parking lot. Finally, similarly, the server controls the gate at the parent parking lot exit based on the processing result of this parent parking lot settlement information. The core judgment of this processing result is likely whether all payable fees (including parent and sub-parking lot settlement information) have been confirmed for payment. Only after receiving a positive processing result will the server send a release instruction.

[0032] In other words, in one possible implementation, the payment mode includes an independent payment mode and a combined payment mode; the server pre-stores which payment mode each sub-parking lot belongs to.

[0033] When performing step S101, the specific steps can be as follows: S1011: When a user vehicle is detected leaving any sub-parking lot, if the sub-parking lot is configured for independent payment mode, the user vehicle's sub-parking lot settlement information for that sub-parking lot is generated and pushed to the user terminal. After receiving the payment confirmation information returned by the user terminal, a release instruction is sent to the control equipment at the entrance and exit of the sub-parking lot. If the sub-parking lot is configured for combined payment mode, the sub-parking lot settlement information is temporarily stored and a release instruction is sent to the control equipment at the entrance and exit of the sub-parking lot. When performing step S102, the specific steps can be as follows: S1021: When a user vehicle is detected leaving the parent parking lot, if all vehicles already in the sub-parking lots are configured for independent payment mode, a release instruction is sent to the control equipment at the entrance and exit of the parent parking lot; if there are vehicles already in the sub-parking lots configured for combined payment mode, the parent parking lot settlement information of the user vehicle to the parent parking lot is generated based on all temporarily stored sub-parking lot settlement information and pushed to the user terminal. After receiving the payment confirmation information returned by the user terminal, a release instruction is sent to the control equipment at the entrance and exit of the parent parking lot.

[0034] In step S1011, when a user's vehicle is detected leaving any sub-parking lot, if that sub-parking lot is configured for independent payment mode, sub-parking lot settlement information is generated and immediately pushed to the user's terminal via application, SMS, or other means, requiring the user to make payment immediately. Here, the user's terminal refers to the terminal owned by the user of the user vehicle (such as the vehicle owner or driver).

[0035] Only after receiving the payment confirmation information from the user terminal does the server generate a processing result indicating that the payment is complete, and then send a release command to the gate of the sub-parking lot to allow the user's vehicle to leave the sub-parking lot.

[0036] If the sub-parking lot is configured for combined payment mode, the sub-parking lot settlement information will also be generated, but the settlement information will be temporarily stored in the database or cache. At the same time, a pass-through result will be generated directly, and a release instruction will be sent to the sub-parking lot gate immediately. The user vehicle can leave the sub-area without stopping.

[0037] In step S1021, when the server detects that a user's vehicle has left the parent parking lot, it queries all the sub-parking lot records that the user's vehicle has entered during this trip and their payment patterns: If all vehicles entering the sub-parking lots are configured with independent payment mode, it means that the fees have already been settled at the exit of each sub-parking lot. At this time, for the exit of the parent parking lot, it is only necessary to check whether there are any fees for the public area of ​​the parent parking lot. If there are none or they have been settled, the server directly generates a release result and sends a release instruction to the parent parking lot gate.

[0038] If a vehicle has already entered a sub-parking lot and is configured for combined payment, the server needs to retrieve the settlement information for all such sub-parking lots from the temporary storage area, aggregate them to generate a combined parent parking lot settlement information (which may also include the parent parking lot's own fees). This combined settlement information (parent parking lot settlement information) is then pushed to the user terminal. After receiving payment confirmation from the user terminal for this combined fee (parent parking lot settlement information), the server generates a processing result indicating payment completion before finally sending a release command to the parent parking lot's gate.

[0039] In one possible implementation, to accurately calculate the parking fees payable by a user's vehicle within the parking lot, the method further includes monitoring and data collection of user vehicle entry events. Before executing step S1011, the following step S100 can be performed: S100: When a user's vehicle is detected to enter any sub-parking lot, the vehicle identification number of the user's vehicle, the sub-parking lot identification number of that sub-parking lot, and the entry time are collected. In step S100, the vehicle identifier can be the license plate number, the sub-parking lot identifier is the unique code of the sub-parking lot, and the entry time is recorded by the barrier gate system or sensor set at the entrance of the sub-parking lot and reported to the server.

[0040] When executing step S1011, if it is detected that a user's vehicle has left any sub-parking lot, and if that sub-parking lot is configured with an independent payment mode, the following steps are followed when generating the sub-parking lot settlement information for the user's vehicle: When a user's vehicle is detected leaving the parking lot, if the parking lot is configured for independent payment mode, the user's parking lot settlement information for that parking lot will be generated based on the departure time and entry time.

[0041] In this embodiment, when a user's vehicle is detected leaving the sub-parking lot, if the sub-parking lot is configured for independent payment mode, the server obtains the current departure time and calculates the actual parking duration of the user's vehicle in the sub-parking lot based on the departure time and the previously recorded entry time. Then, combined with the sub-parking lot's billing rules (such as hourly rates), the server generates sub-parking lot settlement information for the user's vehicle, including the specific parking fees payable.

[0042] In one possible implementation, to support parking benefits such as monthly parking passes and parking packages, the server is pre-configured with billing rules and parking benefit certificates for each sub-parking lot; the parking benefit certificate includes a preset benefit period, fee reduction rules, and the corresponding sub-parking lot identifier; when generating the sub-parking lot settlement information for the user's vehicle in step S101 (and in step S1011), the specific steps S201-S204 can be executed as follows: S201: Query the association between the user's vehicle identifier and the parking rights certificate to determine whether the user's vehicle has been associated with the parking rights certificate corresponding to the sub-parking lot. S202: If the user's vehicle has been associated with and bound to the parking rights certificate corresponding to the sub-parking lot, then determine whether the user's vehicle's parking time in the sub-parking lot falls within the preset rights time period of the parking rights certificate; S203: If the parking time falls within the preset period of the parking rights certificate, the parking fee payable for the sub-parking lot will be calculated according to the fee reduction rules, and the sub-parking lot settlement information for the user's vehicle will be generated. S204: If the user's vehicle is not associated with the parking rights certificate corresponding to the sub-parking lot, or the parking period does not fall within the preset rights period of the parking rights certificate, the parking fee payable for the sub-parking lot shall be calculated according to the billing rules of the sub-parking lot, and the sub-parking lot settlement information of the user's vehicle for the sub-parking lot shall be generated.

[0043] In step S201, determining whether the user's vehicle has been associated with the parking rights certificate corresponding to the sub-parking lot can be done by determining whether the vehicle has purchased a parking package or monthly parking pass for the sub-parking lot.

[0044] In step S202, the parking period is determined based on the entry and exit times of the user's vehicle in the sub-parking lot.

[0045] In step S203, the fee reduction rule may be "free parking" or "charged at a discounted price". After the calculation is completed, the sub-parking lot settlement information for the user's vehicle is generated.

[0046] In step S204, the billing rule refers to the standard charging rule of the parking lot.

[0047] In one possible implementation, to support parking rights such as fixed parking space monthly passes that are bound to specific parking spaces, the parking rights certificate also includes a target parking space identifier, which is a unique identifier for the specific parking space under the sub-parking lot corresponding to the parking rights certificate; when executing step S201, the following steps S2011-S2012 can be performed: S2011: Query all parking rights certificates associated with the user's vehicle identification, filter out parking rights certificates that contain the sub-parking lot identification, and extract the corresponding target parking space identification from the parking rights certificate. S2012: Determine the parking space identifier of the user's vehicle actually occupying the parking space in the sub-parking lot, and confirm whether the parking space identifier of the actually occupied parking space is consistent with the target parking space identifier extracted from the parking rights certificate; if they are consistent, it means that the user's vehicle has been associated with the parking rights certificate corresponding to the sub-parking lot; if they are inconsistent, it means that the user's vehicle has not been associated with the parking rights certificate corresponding to the sub-parking lot.

[0048] In step S2011, for example, if the user's vehicle is currently driving to parking lot B, then the parking rights certificate with the parking lot identifier B is selected from all parking rights certificates associated with the user's vehicle identifier. Then, the server extracts the corresponding target parking space identifier from the selected parking rights certificate.

[0049] In step S2012, the server needs to determine the parking space identifier actually occupied by the user's vehicle within the sub-parking lot. This parking space identifier can be reported to the server through methods such as parking space locks, video recognition, or manual selection by the user. The server will then verify whether the parking space identifier actually occupied matches the target parking space identifier extracted from the parking rights certificate.

[0050] If the parking space identifier of the actual occupied parking space matches the target parking space identifier, it means that the user's vehicle has been correctly parked in the specific parking space corresponding to their rights. At this time, the server determines that the user's vehicle has been associated with and bound to the parking rights certificate corresponding to the sub-parking lot.

[0051] If the parking space identifier of the actual occupied parking space is inconsistent with the target parking space identifier, it means that the user's vehicle is not parked in the specific parking space corresponding to its rights. At this time, the server determines that the user's vehicle is not associated with the parking rights certificate corresponding to the sub-parking lot, or that its rights are not applicable in the current parking behavior.

[0052] In one possible implementation, the association between the user's vehicle identifier and the parking rights certificate is generated in the following manner (S301-S303): S301: Receive a parking rights purchase request sent by the user terminal; wherein, the parking rights purchase request is generated by the user terminal in response to the user's selection operation of multiple pre-configured parking rights certificates; the parking rights purchase request includes the certificate identifier of the parking rights certificate specified by the user's selection operation and the vehicle identifier of the user's vehicle. S302: Based on the credential identifier, determine whether the parking rights credential specified by the user's selection operation is bound to the vehicle identifier of another user's vehicle; S303: If the parking rights certificate specified by the user's selection operation is not bound to the vehicle identifier of another user's vehicle, then establish and store the association between the vehicle identifier of the user's vehicle and the parking rights certificate specified by the user's selection operation.

[0053] In step S301, the server receives a parking rights purchase request sent by the user terminal. The parking rights purchase request is generated by the user terminal in response to the user's selection of multiple pre-configured parking rights credentials (such as monthly passes or packages for different parking lots) on their application interface. The parking rights purchase request includes the credential identifier of the parking rights credential specified by the user's selection and the vehicle identifier of the user's vehicle (such as the license plate number entered by the user).

[0054] In step S302, after receiving the parking rights purchase request, the server queries the database for the current binding status of the parking rights certificate specified by the user's selection operation based on the certificate identifier contained in the request, in order to determine whether the parking rights certificate has been bound to the vehicle identifier of another user's vehicle.

[0055] In step S303, if the server finds after querying that the parking rights certificate specified by the user's selection operation is not bound to the vehicle identifier of another user's vehicle, that is, the parking rights certificate is in a sellable or unbound state, then the server establishes and stores the association between the user's vehicle identifier and the parking rights certificate specified by the user's selection operation. This association will be stored in the server's database for subsequent billing queries.

[0056] If the parking rights certificate has already been bound, the server can return a purchase failure message to the user's terminal.

[0057] In one possible implementation, the server is pre-configured with the billing rules for each parking lot; after executing step S100, in order to meet the user's need to query fees in real time during parking, the following query steps S401-S405 can also be executed: S401: Receive a parking fee query request sent by the user terminal; the parking fee query request includes the vehicle identifier of the user's vehicle and the current query time; S402: Based on the vehicle identifier, query the payment mode of all sub-parking lots that the user's vehicle has entered during this parking process, and obtain the entry time of the user's vehicle in each sub-parking lot. S403: For the sub-parking lots that the user's vehicle has entered during this parking process, calculate the parking fee payable for the sub-parking lot up to the current query time based on the billing rules of the sub-parking lot, the entry time of the user's vehicle and the current query time. S404: For the first sub-parking lot configured with independent payment mode among the sub-parking lots that have been entered, generate the current independent query results for each first sub-parking lot based on the parking fees payable for each first sub-parking lot up to the current query time, and push the current independent query results for each first sub-parking lot to the user terminal. S405: For the second sub-parking lot configured with the combined payment mode among the sub-parking lots that have been entered, generate the current combined query result for the second sub-parking lot based on the parking fees payable for each sub-parking lot up to the current query time, and push the current combined query result to the user terminal.

[0058] In step S401, the server receives a parking fee query request sent by the user terminal. The parking fee query request includes the vehicle identifier of the user's vehicle and the current query time.

[0059] In step S402, the server queries all the sub-parking lot records that the user vehicle has entered during this parking process based on the vehicle identifier, obtains the payment mode (independent payment mode or combined payment mode) of these sub-parking lots, and obtains the entry time of the user vehicle in each sub-parking lot.

[0060] In step S403, for each sub-parking lot that the user's vehicle has entered during this parking process, the server calculates in real time the parking fees payable by the user's vehicle in that sub-parking lot up to the current query time, based on the billing rules of that sub-parking lot, the entry time of the user's vehicle, and the current query time.

[0061] Next, the server categorizes the vehicles that have entered the parking lot according to their payment method: In step S404, for the first parking lot configured with independent payment mode among the parking lots already entered, the server generates a current independent query result for each first parking lot based on the parking fees payable up to the current query time. This current independent query result clearly displays the fees for that first parking lot. Then, the server pushes these current independent query results for the first parking lots to the user terminal.

[0062] In step S405, for the second parking lot configured with combined payment mode among the parking lots already entered, the server generates a current combined query result for all second parking lots based on the parking fees payable for each second parking lot calculated up to the current query time. This current combined query result displays the total fee for all combined billing parking lots. Then, the server pushes the current combined query result to the user terminal.

[0063] In one possible implementation, to support automatic revenue sharing among operators in nested parking lots, the server is pre-configured with the revenue distribution ratio for each sub-parking lot; the method can also be executed according to the following steps: After receiving the payment confirmation information returned by the user terminal, determine one or more corresponding sub-parking lots based on the sub-parking lot settlement information or the parent parking lot settlement information that triggered the payment confirmation information; Based on the determined revenue distribution ratio for each sub-parking lot, calculate the revenue distribution amount for each sub-parking lot and generate revenue distribution information.

[0064] In this embodiment, after receiving the payment confirmation information returned by the user terminal, the server first determines one or more sub-parking lots corresponding to this settlement based on the settlement information that triggered the payment confirmation information.

[0065] Specifically, if the payment confirmation information is a confirmation of the settlement information of a sub-parking lot with an independent payment mode, the server will parse the corresponding sub-parking lot identifier from the sub-parking lot settlement information, and the sub-parking lot determined therefrom will be the single sub-parking lot corresponding to the identifier.

[0066] If the payment confirmation information is a confirmation of a parent parking lot settlement information, the server will parse out the identifiers of each sub-parking lot based on all the temporarily stored sub-parking lot settlement information on which the parent parking lot settlement information was generated. The sub-parking lots identified in this way are all the one or more sub-parking lots involved that are configured with the combined payment mode.

[0067] Next, the server queries the pre-configured revenue sharing ratio for each identified sub-parking lot. This revenue sharing ratio is pre-set by the management and represents the share of revenue that the sub-parking lot operator should receive from the parking fees this time.

[0068] Then, the server calculates the revenue distribution amount for each sub-parking lot based on the parking fees payable in this settlement (obtained from the corresponding sub-parking lot settlement information) and their respective revenue distribution ratios. The calculation method is usually as follows: Revenue distribution amount = Parking fees payable for the sub-parking lot × Revenue distribution ratio for the sub-parking lot.

[0069] Finally, the server encapsulates the determined sub-parking lot identifiers, the revenue distribution ratios corresponding to each sub-parking lot, the calculated revenue distribution amounts, and other relevant information (such as settlement order numbers) to generate structured revenue distribution information. This revenue distribution information can be used to drive the subsequent financial system to automatically complete the transfer and settlement of revenue across operators.

[0070] Based on the same technical concept, this application also provides a parking device for nested parking lots. The device is applied to a server, which is pre-configured with a nested relationship between a parent parking lot and at least one child parking lot, and a payment mode for each child parking lot; such as... Figure 3 As shown, the device includes: The first monitoring module 301 is used to generate sub-parking lot settlement information for the user vehicle based on the payment mode of the sub-parking lot when it is detected that the user vehicle leaves any of the sub-parking lots, and control whether the sub-parking lot allows the user vehicle to leave based on the processing result of the sub-parking lot settlement information. The second monitoring module 302 is used to generate parent parking lot settlement information for the user vehicle to the parent parking lot when the user vehicle leaves the parent parking lot, based on the payment mode and settlement information of the user vehicle in each sub-parking lot that it has entered, and control whether the parent parking lot allows the user vehicle to leave based on the processing result of the parent parking lot settlement information.

[0071] Optionally, the payment mode includes an independent payment mode and a combined payment mode; the first monitoring module 301, when detecting that a user vehicle has left any of the sub-parking lots, generates sub-parking lot settlement information for the user vehicle based on the payment mode of that sub-parking lot, and controls whether the sub-parking lot allows the user vehicle to leave based on the processing result of the sub-parking lot settlement information, is specifically used for: When a user vehicle is detected leaving any of the sub-parking lots, if the sub-parking lot is configured with the independent payment mode, the sub-parking lot settlement information for the user vehicle is generated and pushed to the user terminal. After receiving the payment confirmation information returned by the user terminal, a release command is sent to the control equipment at the entrance and exit of the sub-parking lot. If the sub-parking lot is configured with the combined payment mode, the sub-parking lot settlement information is temporarily stored and a release command is sent to the control equipment at the entrance and exit of the sub-parking lot. The second monitoring module 302, when detecting that a user vehicle has left the parent parking lot, generates parent parking lot settlement information for the user vehicle based on the payment mode and settlement information of the user vehicle in each sub-parking lot it has entered, and controls whether the parent parking lot allows the user vehicle to leave based on the processing result of the parent parking lot settlement information, specifically uses the following functions: When the user vehicle is detected leaving the parent parking lot, if all vehicles already in the sub-parking lots are configured with the independent payment mode, a release command is sent to the control equipment at the entrance and exit of the parent parking lot; if there are vehicles already in the sub-parking lots configured with the combined payment mode, the parent parking lot settlement information of the user vehicle for the parent parking lot is generated based on all temporarily stored sub-parking lot settlement information and pushed to the user terminal. After receiving the payment confirmation information returned by the user terminal, a release command is sent to the control equipment at the entrance and exit of the parent parking lot.

[0072] The device further includes: The data collection module is used to collect the vehicle identifier of the user vehicle, the sub-parking lot identifier, and the entry time when the user vehicle enters any of the sub-parking lots, before the first monitoring module 301 generates the sub-parking lot settlement information for the user vehicle if the sub-parking lot is configured as the independent payment mode. The first monitoring module 301, when detecting that a user vehicle has left any of the sub-parking lots, and if the sub-parking lot is configured with the independent payment mode, generates sub-parking lot settlement information for the user vehicle at that sub-parking lot, specifically for: When the user's vehicle is detected leaving the sub-parking lot, if the sub-parking lot is configured with the independent payment mode, the sub-parking lot settlement information for the user's vehicle is generated based on the departure time and the entry time.

[0073] Optionally, the server is pre-configured with billing rules and parking rights certificates for each of the sub-parking lots; the parking rights certificate includes a preset rights period, fee reduction rules, and a corresponding sub-parking lot identifier; when the first monitoring module 301 generates the sub-parking lot settlement information for the user vehicle, it is specifically used for: Query the association between the user's vehicle identifier and the parking rights certificate to determine whether the user's vehicle has been associated with the parking rights certificate corresponding to the sub-parking lot; If the user's vehicle is already associated with the parking rights certificate corresponding to the sub-parking lot, then determine whether the parking time of the user's vehicle in the sub-parking lot falls within the preset rights period of the parking rights certificate; If the parking time falls within the preset period of the parking rights certificate, the parking fee payable for the sub-parking lot is calculated according to the fee reduction rules, and the sub-parking lot settlement information for the user vehicle is generated. If the user's vehicle is not associated with the parking rights certificate corresponding to the sub-parking lot, or if the parking period does not fall within the preset rights period of the parking rights certificate, the parking fee payable for the sub-parking lot will be calculated according to the billing rules of the sub-parking lot, and the sub-parking lot settlement information for the user's vehicle will be generated.

[0074] Optionally, the parking rights certificate further includes a target parking space identifier, which is a unique identifier for a specific parking space under the sub-parking lot corresponding to the parking rights certificate; when the first monitoring module 301 queries the association between the user's vehicle identifier and the parking rights certificate to determine whether the user's vehicle has been associated with the parking rights certificate corresponding to the sub-parking lot, it is specifically used for: Query all parking rights certificates associated with the user's vehicle identifier, filter out parking rights certificates that contain the sub-parking lot identifier, and extract the corresponding target parking space identifier from the parking rights certificate. Determine the parking space identifier of the user vehicle actually occupying the parking space in the sub-parking lot, and confirm whether the parking space identifier of the actually occupied parking space is consistent with the target parking space identifier extracted from the parking rights certificate; if they are consistent, it means that the user vehicle has been associated with the parking rights certificate corresponding to the sub-parking lot; if they are inconsistent, it means that the user vehicle has not been associated with the parking rights certificate corresponding to the sub-parking lot.

[0075] Optionally, the device further includes a generation module, the first generation module being used to generate the association between the user's vehicle identifier and the parking rights certificate in the following manner: The system receives a parking rights purchase request sent by the user terminal; wherein the parking rights purchase request is generated by the user terminal in response to the user's selection operation of multiple pre-configured parking rights certificates; the parking rights purchase request includes the certificate identifier of the parking rights certificate specified by the user's selection operation and the vehicle identifier of the user's vehicle. Based on the credential identifier, determine whether the parking rights credential specified by the user's selection operation is bound to the vehicle identifier of another user's vehicle; If the parking rights certificate specified by the user's selection operation is not bound to the vehicle identifier of another user's vehicle, then an association binding relationship between the vehicle identifier of the user's vehicle and the parking rights certificate specified by the user's selection operation is established and stored.

[0076] Optionally, the server is pre-configured with billing rules for each of the sub-parking lots; the device further includes: The receiving module is used to receive a parking fee query request sent by the user terminal after the acquisition module detects that a user vehicle has entered any of the sub-parking lots, acquires the vehicle identifier of the user vehicle, the sub-parking lot identifier, and the entry time; the parking fee query request includes the vehicle identifier of the user vehicle and the current query time. The query module is used to query the payment mode of all sub-parking lots that the user vehicle has entered during this parking process, based on the vehicle identifier, and to obtain the entry time of the user vehicle in each sub-parking lot. The accounting module is used to calculate the parking fees payable for the sub-parking lots that the user's vehicle has entered during the current parking process, based on the billing rules of the sub-parking lot, the entry time of the user's vehicle, and the current query time. The second generation module is used to generate the current independent query results for each first parking lot configured with the independent payment mode, based on the parking fees payable for each first parking lot up to the current query time, and push the current independent query results of each first parking lot to the user terminal. The third generation module is used to generate a current merged query result for the second sub-parking lot configured with the merged payment mode, based on the parking fees payable for each sub-parking lot up to the current query time, and push the current merged query result to the user terminal.

[0077] Optionally, the server is also pre-configured with the revenue distribution ratio for each of the sub-parking lots; the device further includes: The determination module is used to determine one or more corresponding sub-parking lots based on the sub-parking lot settlement information or parent parking lot settlement information that triggered the payment confirmation information after receiving the payment confirmation information returned by the user terminal. The calculation module is used to calculate the revenue distribution amount for each sub-parking lot based on the determined revenue distribution ratio, and generate revenue distribution information.

[0078] Figure 4 A schematic diagram of an electronic device provided in this application embodiment includes: a processor 401, a memory 402, and a bus 404. The memory 402 stores machine-readable instructions executable by the processor 401. When the electronic device runs the above-described information processing method, the processor 401 and the memory 402 communicate through the bus 404. The processor 401 executes the machine-readable instructions to perform the steps of the method described in Embodiment 1.

[0079] This application also provides a computer-readable storage medium storing a computer program, which, when executed by a processor, performs the steps described in Embodiment 1.

[0080] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working processes of the devices, electronic devices, and computer-readable storage media described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0081] In the several embodiments provided in this application, it should be understood that the disclosed methods, apparatuses, electronic devices, and computer-readable storage media can be implemented in other ways. The apparatus embodiments described above are merely illustrative. For example, the division of modules is only a logical functional division, and in actual implementation, there may be other division methods. Furthermore, multiple modules or components may be combined or integrated into another system, or some features may be ignored or not executed. Additionally, the displayed or discussed mutual couplings, direct couplings, or communication connections may be through some communication interfaces; indirect couplings or communication connections between devices or modules may be electrical, mechanical, or other forms.

[0082] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0083] In addition, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0084] If the aforementioned functions are implemented as software functional units and sold or used as independent products, they can be stored in a processor-executable, non-volatile, computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0085] Finally, it should be noted that the above-described embodiments are merely specific implementations of this application, used to illustrate the technical solutions of this application, and not to limit them. The scope of protection of this application is not limited thereto. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that any person skilled in the art can still modify or easily conceive of changes to the technical solutions described in the foregoing embodiments, or make equivalent substitutions for some of the technical features, within the scope of the technology disclosed in this application. Such modifications, changes, or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of this application, and should all be covered within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of protection of the claims.

Claims

1. A parking method for nested parking lots, characterized in that, The method is applied to a server, which is pre-configured with a nested relationship between a parent parking lot and at least one child parking lot, and a payment mode for each child parking lot; the method includes: When a user vehicle is detected leaving any of the sub-parking lots, the sub-parking lot settlement information for the user vehicle is generated according to the payment mode of the sub-parking lot, and the sub-parking lot is controlled to release the user vehicle based on the processing result of the settlement information. When a user vehicle is detected leaving the parent parking lot, the system generates parent parking lot settlement information for the user vehicle based on the payment mode and settlement information of the user vehicle in each sub-parking lot. Based on the processing result of the parent parking lot settlement information, the system controls whether the parent parking lot allows the user vehicle to leave.

2. The method according to claim 1, characterized in that, The payment modes include independent payment mode and combined payment mode; when a user vehicle is detected leaving any of the sub-parking lots, the system generates sub-parking lot settlement information for the user vehicle based on the payment mode of that sub-parking lot, and controls whether the sub-parking lot allows the user vehicle to leave based on the processing result of the sub-parking lot settlement information, including: When a user vehicle is detected leaving any of the sub-parking lots, if the sub-parking lot is configured with the independent payment mode, the sub-parking lot settlement information for the user vehicle is generated and pushed to the user terminal. After receiving the payment confirmation information returned by the user terminal, a release command is sent to the control equipment at the entrance and exit of the sub-parking lot. If the sub-parking lot is configured with the combined payment mode, the sub-parking lot settlement information is temporarily stored and a release command is sent to the control equipment at the entrance and exit of the sub-parking lot. When a user vehicle is detected leaving the parent parking lot, based on the user vehicle's payment mode and settlement information at each sub-parking lot, parent parking lot settlement information for the user vehicle is generated. Based on the processing result of this parent parking lot settlement information, the parent parking lot is controlled to determine whether to allow the user vehicle to leave, including: When the user vehicle is detected leaving the parent parking lot, if all vehicles already in the sub-parking lots are configured with the independent payment mode, a release command is sent to the control equipment at the entrance and exit of the parent parking lot; if there are vehicles already in the sub-parking lots configured with the combined payment mode, the parent parking lot settlement information of the user vehicle for the parent parking lot is generated based on all temporarily stored sub-parking lot settlement information and pushed to the user terminal. After receiving the payment confirmation information returned by the user terminal, a release command is sent to the control equipment at the entrance and exit of the parent parking lot.

3. The method according to claim 2, characterized in that, Before generating the sub-parking lot settlement information for the user vehicle at any of the sub-parking lots when the user vehicle is detected leaving any of the sub-parking lots, if the sub-parking lot is configured with the independent payment mode, the method further includes: When a user vehicle is detected to enter any of the sub-parking lots, the vehicle identifier of the user vehicle, the sub-parking lot identifier, and the entry time are collected. When a user vehicle is detected leaving any of the sub-parking lots, if the sub-parking lot is configured with the independent payment mode, then the sub-parking lot settlement information for the user vehicle at that sub-parking lot is generated, including: When the user's vehicle is detected leaving the sub-parking lot, if the sub-parking lot is configured with the independent payment mode, the sub-parking lot settlement information for the user's vehicle is generated based on the departure time and the entry time.

4. The method according to any one of claims 1-3, characterized in that, The server is pre-configured with billing rules and parking privilege certificates for each of the sub-parking lots; the parking privilege certificate includes a preset privilege period, fee reduction rules, and a corresponding sub-parking lot identifier; generating the sub-parking lot settlement information for the user's vehicle includes: Query the association between the user's vehicle identifier and the parking rights certificate to determine whether the user's vehicle has been associated with the parking rights certificate corresponding to the sub-parking lot; If the user's vehicle is already associated with the parking rights certificate corresponding to the sub-parking lot, then determine whether the parking time of the user's vehicle in the sub-parking lot falls within the preset rights period of the parking rights certificate; If the parking time falls within the preset period of the parking rights certificate, the parking fee payable for the sub-parking lot is calculated according to the fee reduction rules, and the sub-parking lot settlement information for the user vehicle is generated. If the user's vehicle is not associated with the parking rights certificate corresponding to the sub-parking lot, or if the parking period does not fall within the preset rights period of the parking rights certificate, the parking fee payable for the sub-parking lot will be calculated according to the billing rules of the sub-parking lot, and the sub-parking lot settlement information for the user's vehicle will be generated.

5. The method according to claim 4, characterized in that, The parking rights certificate also includes a target parking space identifier, which is a unique identifier for a specific parking space under the sub-parking lot corresponding to the parking rights certificate; the step of querying the association between the user's vehicle identifier and the parking rights certificate to determine whether the user's vehicle has been associated with the parking rights certificate corresponding to the sub-parking lot includes: Query all parking rights certificates associated with the user's vehicle identifier, filter out parking rights certificates that contain the sub-parking lot identifier, and extract the corresponding target parking space identifier from the parking rights certificate. Determine the parking space identifier of the user vehicle actually occupying the parking space in the sub-parking lot, and confirm whether the parking space identifier of the actually occupied parking space is consistent with the target parking space identifier extracted from the parking rights certificate; if they are consistent, it means that the user vehicle has been associated with the parking rights certificate corresponding to the sub-parking lot; if they are inconsistent, it means that the user vehicle has not been associated with the parking rights certificate corresponding to the sub-parking lot.

6. The method according to claim 5, characterized in that, The association between the user's vehicle identifier and the parking rights certificate is generated in the following way: The system receives a parking rights purchase request sent by the user terminal; wherein the parking rights purchase request is generated by the user terminal in response to the user's selection operation of multiple pre-configured parking rights certificates; the parking rights purchase request includes the certificate identifier of the parking rights certificate specified by the user's selection operation and the vehicle identifier of the user's vehicle. Based on the credential identifier, determine whether the parking rights credential specified by the user's selection operation is bound to the vehicle identifier of another user's vehicle; If the parking rights certificate specified by the user's selection operation is not bound to the vehicle identifier of another user's vehicle, then an association binding relationship between the vehicle identifier of the user's vehicle and the parking rights certificate specified by the user's selection operation is established and stored.

7. The method according to claim 3, characterized in that, The server is pre-configured with billing rules for each of the sub-parking lots; when a user vehicle is detected entering any of the sub-parking lots, after collecting the vehicle identifier of the user vehicle, the sub-parking lot identifier, and the entry time, the method further includes: Receive a parking fee query request sent by the user terminal; the parking fee query request includes the vehicle identifier of the user's vehicle and the current query time; Based on the vehicle identifier, query the payment mode of all sub-parking lots that the user vehicle has entered during this parking process, and obtain the entry time of the user vehicle in each sub-parking lot. For the sub-parking lots that the user's vehicle has entered during this parking process, the parking fees payable for the sub-parking lot up to the current query time are calculated in real time based on the billing rules of the sub-parking lot, the entry time of the user's vehicle, and the current query time. For the first sub-parking lot configured with the independent payment mode that has been entered, the current independent query results for each first sub-parking lot are generated based on the parking fees payable for each first sub-parking lot up to the current query time, and the current independent query results for each first sub-parking lot are pushed to the user terminal. For the second sub-parking lot configured with the combined payment mode, which has already been entered, a current combined query result for the second sub-parking lot is generated based on the parking fees payable for each sub-parking lot up to the current query time, and the current combined query result is pushed to the user terminal.

8. A parking device for nested parking lots, characterized in that, The device is applied to a server, which is pre-configured with a nested relationship between a parent parking lot and at least one child parking lot, and the payment mode for each child parking lot; the device includes: The first monitoring module is used to generate the user vehicle's sub-parking lot settlement information for the sub-parking lot according to the payment mode of the sub-parking lot when it is detected that the user vehicle leaves any of the sub-parking lots, and control whether the sub-parking lot allows the user vehicle to leave based on the processing result of the sub-parking lot settlement information. The second monitoring module is used to generate parent parking lot settlement information for the user vehicle to the parent parking lot when the user vehicle leaves the parent parking lot, based on the payment mode and settlement information of the user vehicle in each sub-parking lot that it has entered, and control whether the parent parking lot allows the user vehicle to leave based on the processing result of the parent parking lot settlement information.

9. An electronic device, characterized in that, include: The device includes a processor, a memory, and a bus, wherein the memory stores machine-readable instructions executable by the processor, and when the electronic device is in operation, the processor communicates with the memory via the bus, and the machine-readable instructions, when executed by the processor, perform the steps of the method as described in any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when executed by a processor, performs the steps of the method as described in any one of claims 1 to 7.

Images