Gate management system, method, device, storage medium and computer program product
Patent Information
- Application Number
- CN202510533064.6
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-04-25
- Publication Date
- 2026-10-27
AI Technical Summary
[0003]本发明提供一种闸机管理系统、方法、设备、存储介质和计算机程序产品，用以解决现有技术中闸机管理方案无法满足不同场景的管理需求的缺陷，实现更好地适应不同的业务流程和管理需求，从而满足不同场景的管理需求
[0014]本发明提供的闸机管理系统、方法、设备、存储介质和计算机程序产品，该系统包括商户管理模块，用于向后端服务模块发送配置请求；后端服务模块，用于接收商户管理模块发送的配置请求，若配置请求为新增扫码消费方案请求，则向中台计费服务模块发送新扫码消费方案的计费规则参数；若配置请求为新增闸机设备请求，则向中台商户中心模块发送新闸机设备的设备信息；若配置请求为新增闸机终端请求，则向中台商户中心模块发送新闸机终端的绑定指令；其中，闸机终端为安装于闸机设备上的终端；中台计费服务模块，用于校验计费规则参数的合法性，生成新扫码消费方案的方案ID；中台商户中心模块，用于校验设备信息的唯一性生成新闸机设备的ID，以及校验绑定指令的合法性。该系统支持多样的计费模式和灵活的设备绑定方式，使得系统能够更好地适应不同的业务流程和管理需求，从而满足不同场景的管理需求。
Smart Images
Figure CN122990839A_ABST
Abstract
Description
Technical Field
[0001] This invention relates to the field of turnstile technology, and in particular to a turnstile management system, method, device, storage medium, and computer program product. Background Technology
[0002] Currently, the management needs of entertainment facilities and venues are becoming increasingly diverse, highlighting the limitations of traditional turnstile systems in entry / exit management and payment methods. Existing turnstiles in transportation scenarios such as subways generally employ billing schemes based on travel distance or time, with the core logic being the calculation of fees based on the user's physical location or time difference between entry and exit. However, such schemes are difficult to directly apply to scenarios such as entertainment venues and shared equipment rentals. Therefore, the inability of existing turnstile management solutions to meet the management needs of different scenarios has become a pressing issue that needs to be addressed. Summary of the Invention
[0003] This invention provides a gate management system, method, device, storage medium, and computer program product to address the shortcomings of existing gate management solutions that cannot meet the management needs of different scenarios, thereby better adapting to different business processes and management requirements and meeting the management needs of different scenarios.
[0004] This invention provides a gate management system, comprising the following modules: The merchant management module is used to send configuration requests to the backend service module; The backend service module is used to receive configuration requests sent by the merchant management module. If the configuration request is a request to add a QR code consumption scheme, it sends the billing rule parameters of the new QR code consumption scheme to the middle platform billing service module; if the configuration request is a request to add a gate device, it sends the device information of the new gate device to the middle platform merchant center module; if the configuration request is a request to add a gate terminal, it sends a binding instruction for the new gate terminal to the middle platform merchant center module; wherein, the gate terminal is a terminal installed on the gate device. The middleware billing service module is used to verify the legality of the billing rule parameters and generate the scheme ID of the new QR code consumption scheme. The middleware merchant center module is used to verify the uniqueness of the device information, generate the ID of the new gate device, and verify the legality of the binding command.
[0005] According to a gate management system provided by the present invention, the gate management system further includes a device communication service module and a terminal service module of the gate terminal; The merchant management module is also used to send basic functions and primary parameters to the backend service module; The backend service module is also used to forward the basic functions and primary parameters to the device communication service module; The device communication service module is used to forward the basic functions and primary parameters to the terminal service module; The terminal service module is used to perform parameter configuration operations based on the basic functions and primary parameters.
[0006] According to a gate management system provided by the present invention, the gate management system further includes: The terminal service module is also used to send a query request to the device communication service module to determine whether the gate device is registered. The device communication service module is also used to obtain gate device information from the middleware merchant center module based on the query request, and to feed back the registration result of the gate device to the terminal service module based on the gate device information.
[0007] According to a gate management system provided by the present invention, the gate management system further includes: The terminal service module is also used to send a request to the device communication service module to obtain the device consumption scheme of the gate device; The device communication service module is also used to forward the acquisition request to the backend service module; The backend service module is further configured to obtain the device consumption plan from the middle platform billing service module based on the acquisition request, and send the device consumption plan to the terminal service module through the device communication service module.
[0008] According to the present invention, a gate management system further includes a cashier service module; The terminal service module is also used to send gate opening parameters to the equipment communication service module; The device communication service module is also used to send project deduction information to the cashier service module based on the gate opening parameters; The cashier service module is used to forward the project deduction information to the middle platform billing service module; The middleware billing service module is also used to perform deduction operations based on the project deduction information and send the deduction results to the cashier service module.
[0009] According to a gate management system provided by the present invention, the gate management system further includes: The terminal service module is also used to send gate exit parameters to the equipment communication service module; The device communication service module is also used to send an exit request to the backend service based on the exit parameters; The backend service module is also used to determine whether the user has timed out based on the exit request. If there is no timeout, the exit result is sent to the terminal service module through the device communication service module.
[0010] The present invention also provides a gate management method, comprising the following steps: Receive configuration requests sent by the merchant management module; If the configuration request is a request to add a new QR code consumption scheme, then the billing rule parameters of the new QR code consumption scheme are sent to the middle platform billing service module so that the middle platform billing service module can verify the legality of the billing rule parameters and generate the scheme ID of the new QR code consumption scheme. If the configuration request is a request to add a new gate device, the device information of the new gate device is sent to the middle platform merchant center module so that the middle platform merchant center module can verify the uniqueness of the device information and generate the ID of the new gate device; If the configuration request is a request to add a new gate terminal, a binding instruction for the new gate terminal is sent to the middleware merchant center module so that the middleware merchant center module can verify the legality of the binding instruction; wherein, the gate terminal is a terminal installed on the gate device.
[0011] The present invention also provides an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the gate management method as described above.
[0012] The present invention also provides a non-transitory computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the gate management method as described above.
[0013] The present invention also provides a computer program product, including a computer program that, when executed by a processor, implements the gate management method as described above.
[0014] This invention provides a gate management system, method, device, storage medium, and computer program product. The system includes a merchant management module for sending configuration requests to a backend service module. The backend service module receives configuration requests from the merchant management module. If the configuration request is for adding a QR code payment scheme, it sends the billing rule parameters of the new QR code payment scheme to the middle-platform billing service module. If the configuration request is for adding a gate device, it sends the device information of the new gate device to the middle-platform merchant center module. If the configuration request is for adding a gate terminal, it sends a binding instruction for the new gate terminal to the middle-platform merchant center module. The gate terminal is a terminal installed on the gate device. The middle-platform billing service module verifies the legality of the billing rule parameters and generates a scheme ID for the new QR code payment scheme. The middle-platform merchant center module verifies the uniqueness of the device information, generates the ID of the new gate device, and verifies the legality of the binding instruction. This system supports diverse billing modes and flexible device binding methods, enabling it to better adapt to different business processes and management needs, thereby meeting the management requirements of different scenarios. Attached Figure Description
[0015] To more clearly illustrate the technical solutions in this invention or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of this invention. For those skilled in the art, other drawings can be obtained from these drawings without creative effort.
[0016] Figure 1 This is a schematic diagram of the business process of the gate management system provided by the present invention.
[0017] Figure 2 This is a flowchart illustrating the gate management method provided by the present invention.
[0018] Figure 3 This is a schematic diagram of the structure of the electronic device provided by the present invention. Detailed Implementation
[0019] To make the objectives, technical solutions, and advantages of this invention clearer, the technical solutions of this invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of this invention. All other embodiments obtained by those skilled in the art based on the embodiments of this invention without creative effort are within the scope of protection of this invention.
[0020] The turnstile management solutions provided in related technologies are difficult to directly apply to scenarios such as entertainment venues and shared equipment rentals because: 1) Limited billing model: The distance / time billing rules of subway turnstiles are fixed and cannot adapt to the diverse billing needs in entertainment scenarios, such as per-use billing, time-based billing, and differentiated pricing based on equipment type. 2) Insufficient device binding flexibility: In traditional solutions, user credentials (such as transportation cards) are only bound to a single account, which cannot support users to dynamically bind / unbind multiple devices, such as shared game consoles, sports equipment, or customize the billing rules for different devices; 3) Lack of dynamic policy management: Existing systems typically use preset global billing policies, which do not allow users or administrators to flexibly adjust the billing scheme according to actual needs (such as membership discounts, promotional activities).
[0021] Based on the above problems, this invention proposes a gate management system, which can achieve the following objectives: support users to flexibly bind or unbind multiple devices through a unified platform and set differentiated deduction rules for them; provide a configurable billing strategy engine to adapt to various billing modes such as per-use, per-duration, and tiered pricing; and realize dynamic association between credentials (such as QR codes and NFC) and devices to ensure the accuracy and real-time nature of deductions.
[0022] The following is combined with Figures 1-3 This invention describes a gate management system, method, apparatus, storage medium, and computer program product.
[0023] This invention proposes a gate management system, comprising: The merchant management module is used to send configuration requests to the backend service module; The backend service module receives configuration requests from the merchant management module. If the configuration request is for adding a QR code consumption scheme, it sends the billing rule parameters of the new QR code consumption scheme to the middle platform billing service module. If the configuration request is for adding a gate device, it sends the device information of the new gate device to the middle platform merchant center module. If the configuration request is for adding a gate terminal, it sends the binding instruction of the new gate terminal to the middle platform merchant center module. The middleware billing service module is used to verify the legality of billing rule parameters and generate a scheme ID for a new QR code consumption scheme. The merchant center module in the middle platform is used to verify the uniqueness of device information, generate the ID of new gate devices, and verify the legality of binding commands.
[0024] It should be understood that configuration requests may include requests to add a QR code payment solution, requests to add a turnstile device, and requests to add a turnstile terminal. Optionally, configuration requests may also include: 1) Gate Terminal Binding Request: For example, when an existing gate terminal needs to be associated with a new QR code payment scheme, a binding operation is required. The merchant management module sends a binding request to the backend service module. Upon receiving the request, the backend service module sends a binding instruction containing the gate terminal device ID, terminal type, and QR code payment scheme ID to the middleware merchant center module. The middleware merchant center module is responsible for verifying the validity of the binding instruction and executing the binding operation.
[0025] 2) Unbinding Request between Gate Terminal and QR Code Payment Solution: When the QR code payment solution changes, or when the gate terminal no longer needs to use a specific QR code payment solution, an unbinding operation is required. The merchant management module sends an unbinding request to the backend service module. Upon receiving the request, the backend service module sends the corresponding unbinding instruction to the middleware merchant center module. The middleware merchant center module is responsible for executing the unbinding operation and updating the relevant data.
[0026] 3) Unbinding Request between Gate Terminal and Gate Equipment: If the gate terminal malfunctions and needs to be replaced, or if the usage scenario of the gate equipment changes, it may be necessary to unbind the gate terminal from the gate equipment. In this case, the merchant management module sends an unbinding request, and the backend service module coordinates with the middleware merchant center module to complete the unbinding operation between the gate terminal and the gate equipment, including clearing relevant binding information.
[0027] 4) Gate Equipment Information Modification Request: This is used to modify relevant information about the gate equipment, such as changes in the equipment's installation location or the need to update the equipment serial number. The merchant management module sends a modification request containing the new equipment information to the backend service module. The backend service module forwards the request to the middleware merchant center module, which verifies the validity of the information and then updates the equipment information.
[0028] 5) Modification request for QR code payment scheme: When the billing rules, scope of application and other parameters of the QR code payment scheme need to be adjusted, the merchant management module sends a modification request to the backend service module. The backend service module sends the new billing rule parameters and other information in the request to the middle platform billing service module. After verifying the legality, the middle platform billing service module updates the relevant information of the QR code payment scheme.
[0029] 6) Gate Terminal Information Modification Request: For some attributes of the gate terminal, such as changes in terminal type (from entrance terminal to exit terminal) or other configuration information of the terminal that need to be modified, the merchant management module sends a modification request to the middle platform merchant center module through the backend service module. The middle platform merchant center module verifies and executes the modification operation.
[0030] 7) Query Request: The merchant management module may need to query various information, such as the list and status of turnstile devices, detailed information on QR code payment schemes, and the binding status of turnstile terminals. After receiving the query request, the backend service module retrieves the relevant information from the middle platform billing service module, the middle platform merchant center module, etc., according to the type of request, and returns it to the merchant management module.
[0031] It should be understood that a QR code payment scheme is a payment configuration method for turnstile equipment, used to define the specific rules and processes for user consumption. The QR code payment scheme includes clearly defined billing rule parameters, which may include parameters for each use (such as the single charge amount and free use threshold), time-based rules (such as tiered rates and minimum billing time units), preferential policies, and charging periods. The QR code payment scheme determines how fees are deducted from users' fares based on different scenarios and conditions when they pass through the turnstile. For example, different charging standards can be set according to different time periods; or different discounts can be offered to different types of users (such as members and non-members). In addition, the QR code payment scheme also specifies the applicable turnstile equipment types, turnstile terminal types, and user groups. For example, a particular QR code payment scheme may only be applicable to turnstile equipment in a specific area, or only for users using a specific payment method.
[0032] It should be understood that the device information of the turnstile can include the device serial number and installation location, etc. The binding instruction can carry the device ID, terminal type, and QR code payment scheme ID of the turnstile terminal, etc. The turnstile terminal type can include entrance terminals and exit terminals, etc., and the same turnstile device ID can be bound to multiple terminal types. In addition, in the process of adding (or registering) turnstile devices, the allocation of turnstile terminals is dynamically adjusted according to the physical installation location of the turnstile and business logic requirements, and the same turnstile device supports binding multiple QR code payment schemes simultaneously.
[0033] A turnstile terminal is a terminal installed on a turnstile device. Specifically, a turnstile terminal refers to an electronic terminal device installed on a turnstile device that is responsible for controlling the operation of the turnstile. For example, devices on the turnstile device used to identify user identity (such as card swiping, QR code scanning, or facial recognition), or panels used for displaying information and interactive operations, can be considered turnstile terminals. Furthermore, a turnstile device can contain multiple turnstile terminals, each responsible for a different function. For example, a turnstile device may have one terminal for entrance control and one terminal for exit control.
[0034] During the process of adding a new QR code payment scheme, the merchant selects to create a new QR code payment scheme (e.g., 30 yuan / hour or 5 yuan / time) on the management side, triggering the merchant management module to send a request to the backend service module. Upon receiving the request, the backend service module assembles the specific billing rule parameters. For example, based on the merchant's selected billing type (hourly / time-based) and the entered price rules, it converts the user input into structured data recognizable by the middle platform billing service module, such as converting "30 yuan / hour" into a recognizable JSON data structure. Then, the backend service module calls the middle platform billing service module's API (Application Programming Interface) through the Feign client to submit a scheme configuration request. After the middle platform billing service module completes the validation and storage of the billing rule parameters, it returns a unique scheme ID (e.g., scheme_id:1001). The backend service module then transmits the configuration result returned by the middle platform billing service module back to the merchant's front-end interface, displaying "Successfully added" or the reason for failure.
[0035] During the process of adding a new turnstile device, the merchant registers the physical turnstile device information (such as device serial number SN_123456) in the management terminal, triggering the merchant management module to send a request to the backend service module to add the turnstile device. The backend service module retrieves the device information of the new turnstile device based on the received request, and then calls the middleware merchant center module to verify the device's legality and uniqueness (to prevent duplicate registration). After the middleware merchant center module passes the verification, it assigns a unique device ID (such as device_id:2024) to the newly added turnstile device and persistently stores the device's basic information (location, model, etc.). Simultaneously, the middleware merchant center module sends the result of the turnstile device addition, such as whether the device addition was successful, to the merchant management module through the backend service module.
[0036] During the process of adding a new turnstile terminal, the merchant enters relevant information about the new terminal in the management terminal, such as the terminal's device ID, terminal type, and associated QR code payment scheme ID. This triggers the merchant management module to send a request to the backend service module to add the new turnstile terminal. Upon receiving the request, the backend service module retrieves the relevant information entered by the merchant and generates a binding instruction based on this information. Then, the backend service module calls the middleware merchant center module and sends the binding instruction to it. The middleware merchant center module verifies the validity of the binding instruction, for example, checking whether the terminal's device ID has already been used (to prevent duplicate registration), verifying whether the terminal type conforms to the specifications, and confirming the validity of the QR code payment scheme ID. Finally, the middleware merchant center module sends the result of adding the turnstile terminal to the merchant management module through the backend service module, informing the merchant whether the terminal addition was successful.
[0037] It should be understood that merchants can add gate terminals to newly added gate equipment, or add gate terminals to existing gate equipment.
[0038] The gate management system provided by this invention supports the dynamic binding and unbinding of the same credentials (such as membership cards, mobile applications, etc.) with multiple devices. Taking shared equipment rental as an example, when renting a shared game machine, a user can bind their account to the game machine via a mobile application. After use, they can unbind it at any time and bind it to other sports equipment. Therefore, users can flexibly use different devices according to their own needs without having to apply for separate credentials or accounts for each device. In addition, it allows users / merchants to customize the charging rules for different devices within a certain range. For example, users can set shared game machines to charge per use, such as 5 yuan per use; and sports equipment to charge per hour, such as 10 yuan per hour, etc. The system charges according to the user-defined rules to meet the user's personalized needs. Different discount ratios can also be set for members based on their membership level or consumption history. When billing at the gate, the system automatically identifies the member's identity and deducts the corresponding discount. For example, senior members enjoy a 20% discount, and ordinary members enjoy a 10% discount, etc. At the same time, promotional plans can be set up at any time according to actual conditions, such as 20% off the entire store during holidays, limited-time discounts on specific equipment, etc. The gate management system obtains promotional information in real time and automatically applies the corresponding discounts when users make purchases.
[0039] The gate management system provided by this invention supports diverse billing modes and flexible device binding methods, enabling the system to better adapt to different business processes and management needs, thereby meeting the management requirements of different scenarios.
[0040] In one embodiment, the gate management system further includes: a device communication service module and a terminal service module for the gate terminal; The merchant management module is also used to send basic functions and master-level parameters to the backend service module; The backend service module is also used to forward basic functions and master-level parameters to the device communication service module; The device communication service module is used to forward basic functions and master parameters to the terminal service module; The terminal service module is used to perform parameter configuration operations based on basic functions and primary parameters.
[0041] It should be understood that basic functions and primary parameters include basic function parameters and primary parameters. Basic function parameters are the underlying hardware functions supported by the gate device, such as: device control functions (e.g., gate opening / closing command execution, fault detection and alarm), user interaction functions (e.g., QR code / NFC recognition, display screen information display), communication functions (e.g., encrypted data transmission, heartbeat detection mechanism), etc. Primary parameters are business rule parameters dynamically configured by the management system, such as billing-related parameters (e.g., billing mode, discount rules), access control parameters (e.g., device usage time restrictions, terminal type restrictions), business strategy parameters (e.g., promotional activity rules, device grouping strategies), etc.
[0042] It should be understood that the terminal service module can be an Android service for the gate terminal.
[0043] Merchants click the "Basic Functions and Primary Parameters Deployment" button on the management interface, triggering the merchant management module to deploy basic functions and primary parameters to the backend service module. The backend service module sends parameter deployment instructions to the device communication service module, which then pushes the parameters to the terminal control module of the designated gate via protocols such as MQTT / WebSocket. The terminal control module returns a "Deployment Result," indicating only that the instruction has been delivered to the terminal, not that the parameters have taken effect. After the terminal control module actually completes the parameter settings, it reports the final execution status via asynchronous messages. The merchant frontend continuously queries the parameter setting results through a polling mechanism until timeout or a clear success / failure status is obtained. If the network is interrupted during this period, the terminal will use the last valid parameters cached locally.
[0044] This invention, through its embodiments, distributes basic functions and master-level parameters to the turnstiles. When merchants change their billing rules, access strategies, or other business requirements, the new parameters can be quickly applied to the turnstiles without complex system updates or hardware modifications, enabling rapid response to market changes and operational adjustments. Furthermore, by distributing different master-level parameters, it can adapt to various turnstile application scenarios, such as scenic spots, shopping malls, and transportation hubs, configuring billing and access rules as needed to meet the unique management requirements of each scenario and improve the system's versatility and applicability.
[0045] In one embodiment, the gate management system further includes: The terminal service module is also used to send a query request to the device communication service module to check whether the gate device is registered; The device communication service module is also used to obtain gate device information from the middleware merchant center module based on query requests, and to return the registration result of the gate device to the terminal service module based on the gate device information.
[0046] Specifically, when a user needs to determine whether a gate device is registered, they can use the terminal service module to confirm whether the current gate device has been registered in the system. Only by confirming the device's registration status can subsequent operation procedures be carried out correctly; if the device is not registered, it may be unable to perform functions such as identity verification and billing.
[0047] After receiving a query request from the terminal service module, the device communication service module retrieves the turnstile device information from the middleware merchant center module based on the query request. The middleware merchant center module stores various information about the turnstile devices, such as device number, model, and registration time. This information is used to determine the device's registration status.
[0048] After obtaining the gate device information, the device communication service module analyzes and processes the information to determine whether the device is registered. Based on the determination result, it feeds back the registration result of the gate device to the terminal service module. For example, if the device has a complete registration record in the merchant center module, the device communication service module will inform the terminal service module that the device has been registered. This allows the terminal service module to continue with subsequent business processes, such as allowing users to perform identity verification. If the device is not registered, the terminal service module can take appropriate measures, such as notifying users or administrators that there is a problem with the device that needs to be addressed.
[0049] The terminal service module and device communication service module provided in this embodiment of the invention cooperate with each other in the gate management system. Through query and feedback mechanisms, they ensure that the gate equipment can operate normally and orderly in the system, and ensure the accuracy and continuity of the entire gate management process.
[0050] In one embodiment, the gate management system further includes: The terminal service module is also used to send a request to the device communication service module to obtain the device consumption scheme of the gate device; The device communication service module is also used to forward acquisition requests to the backend service module; The backend service module is also used to obtain the device consumption plan from the middle platform billing service module based on the acquisition request, and send the device consumption plan to the terminal service module through the device communication service module.
[0051] Specifically, when a user wants to know the consumption rules corresponding to the current use of the gate device (such as a mobile APP or gate operation interface), such as the per-use charging standard or the time-based charging amount, the terminal service module sends a request to the device communication service module to obtain the device consumption plan.
[0052] The device communication service module forwards the request to the backend service module. Upon receiving the request, the backend service module retrieves the device consumption plan from the middleware billing service module. The middleware billing service module stores various rules and plans related to cost calculation, from which the backend service module extracts the corresponding consumption plan for the gate device.
[0053] The backend service module obtains the device consumption plan and then sends it back to the terminal service module through the device communication service module. In this way, the terminal service module can receive complete device consumption plan information and display it to the user or use it for subsequent business logic judgments, such as informing the user of the cost before passage or calculating the cost based on the plan during billing.
[0054] The embodiments of the present invention enable efficient acquisition of device consumption plans, provide users with clear consumption guidance, and also provide a basis for accurate billing and other business operations of the system.
[0055] In one embodiment, the gate management system also includes a cashier service module; The terminal service module is also used to send gate opening parameters to the equipment communication service module; The equipment communication service module is also used to send project deduction information to the cashier service module based on the gate opening parameters; The POS service module is used to forward project deduction information to the middle-office billing service module; The billing service module in the middle platform is also used to perform deduction operations based on project deduction information and send the deduction results to the cashier service module.
[0056] Specifically, the terminal service module is responsible for sending gate opening parameters to the device communication service module. These gate opening parameters can be understood as the instruction information that triggers the gate to open and is associated with subsequent billing operations. For example, when a user passes through the gate, the terminal service module generates corresponding gate opening parameters based on the user's identity verification and payment plan, such as the user's selected payment method (membership card payment, online payment, etc.) and the corresponding billing rules for this passage. These parameters are then sent to the device communication service module to initiate the subsequent process.
[0057] After receiving the gate opening parameters from the terminal service module, the device communication service module sends item deduction information to the cashier service module based on these parameters. For example, it extracts key information related to fee deduction from the gate opening parameters and converts it into item deduction information that the cashier service module can recognize and process. For example, it organizes the user's consumption amount, consumption items, and other information and sends it to the cashier service module, informing it that a fee deduction operation needs to be performed on the user's passage.
[0058] The main task of the POS service module is to receive the item deduction information sent by the device communication service module and forward it to the middle platform billing service module. The POS service module does not directly perform deduction calculations, but is responsible for accurately transmitting the information to the middle platform billing service module, which actually performs the billing operation, to ensure the smooth flow of the billing process.
[0059] After receiving the item deduction information forwarded by the cashier service module, the middle-platform billing service module executes the deduction operation based on this information. For example, according to pre-set billing rules (such as per-use charging, time-based charging, etc.), combined with specific data in the item deduction information (such as the number of transactions, the duration of the transaction, etc.), it accurately calculates the fee to be deducted for the user's current use and completes the actual deduction. Then, the middle-platform billing service module sends the deduction result (such as successful deduction, reason for failure, etc.) back to the cashier service module for feedback and processing in subsequent processes.
[0060] This invention enables close collaboration among the modules in the gate management system during the fee deduction process. From the generation and transmission of gate opening parameters to the flow of deduction information and the execution and feedback of the final deduction operation, the accuracy and efficiency of the gate system in billing scenarios involving consumption are ensured.
[0061] In one embodiment, the gate management system further includes: The terminal service module is also used to send gate exit parameters to the equipment communication service module; The equipment communication service module is also used to send a gate exit request to the backend service module based on the gate exit parameters; The backend service module is also used to determine whether the user has timed out based on the exit request. If there is no timeout, the exit result is sent to the terminal service module through the device communication service module.
[0062] Specifically, when a user completes their activities inside the turnstile and prepares to exit, the terminal service module generates exit parameters. These parameters may include the user's entry timestamp, identity information, and consumption information associated with this entry. The module sends these parameters to the device communication service module to inform the system that the user is about to exit and requires appropriate processing.
[0063] After receiving the exit parameters, the device communication service module sends an exit request to the backend service module based on these parameters. Upon receiving the exit request forwarded by the device communication service module, the backend service module determines whether the user has timed out based on the information in the request. For example, the backend service module needs to query relevant records or compare the user's current stay time inside the gate with the preset time limit according to specific rules. If the user has not timed out, the backend service module sends the exit result to the terminal service module through the device communication service module, informing the terminal service module that the user can exit normally. Upon receiving this information, the terminal service module controls the gate to open, allowing the user to pass.
[0064] It should be understood that for re-entry, when processing the entry fee deduction process for non-online payments, the system first needs to determine whether the member's latest entry record for the day (temporary exit time, not the cumulative time of multiple entries and exits) meets the rules for temporary exit. If it meets the rules, no fee is deducted for entry; otherwise, a fee is deducted again. Specifically, the system will search for the member's latest entry record for the day, including information such as the member's first entry time and temporary exit time. Pre-set rules for temporary exit can include time limits (e.g., returning within 30 minutes is considered a temporary exit) and limits on the number of exits (e.g., only one temporary exit is allowed per day). If the member's latest entry record meets the rules for temporary exit, it means that this re-entry is within the allowed range and is considered a normal temporary exit followed by a return; no further fee is required, and the member can directly re-enter. For example, if a member makes a purchase at a shopping mall, temporarily leaves to pick up takeout, and returns within 30 minutes, this meets the temporary exit rules, and the member can re-enter without further fee. If a member's entry record does not comply with the rules, such as exceeding the temporary exit time limit or exceeding the allowed number of exits, the system will determine that a fee needs to be deducted again before entry. This is to ensure the reasonableness and accuracy of the gate management system's billing and to prevent fee loss.
[0065] The embodiments of the present invention can effectively monitor the time a user stays inside the turnstile, ensure that the system performs the exit operation according to the preset rules, and guarantee the normal operation of the turnstile system and the effective management of user behavior.
[0066] refer to Figure 1 , Figure 1 This is a schematic diagram of the business process of the gate management system provided by the present invention. The specific business processing flow may include the following steps: Step 1: The merchant sends a request to the backend service to add a QR code payment solution; Step 2: After receiving the request, the backend service calls the middle platform billing service to assemble the count / time rule parameters; Step 3: The middle platform billing service returns the result of the newly added QR code scanning service plan to the backend service; Step 4: The backend service returns the new results to the merchant; Step 5: The merchant sends a request to add a new turnstile device to the backend service; Step 6: After receiving the request, the backend service calls the merchant center in the middle platform to add the gate device; Step 7: The middleware merchant center returns the results of adding devices to the backend service; Step 8: The backend service returns the new results to the merchant; Step 9: The merchant sends a request to add a new gate terminal to the backend service; Step 10: After receiving the request, the backend service calls the device communication service to add a gate terminal (exit / entrance). Step 11: The device communication service returns the result of adding a new gate terminal to the backend service; Step 12: The backend service returns the new results to the merchant; Step 13: The merchant sends basic functions and primary parameters to the backend service; Step 14: The backend service sends a parameter distribution request to the device communication service; Step 15: The device communication service sends a delivery request to the Android service; Step 16: The Android service returns the distribution result (which does not necessarily mean the setup was successful) to the device communication service; Step 17: The device communication service returns the result to the backend service; Step 18: The backend service will return the results to the merchant; Step 19: The Android service sends a request for the parameter setting results to the device communication service; Step 20: The device communication service returns the parameter setting results to the backend service; Step 21: The middle platform merchant center returns the results to the backend service, and the backend service queries the frontend to obtain the parameter setting results in a loop.
[0067] The above process demonstrates the complete process from the merchant initiating a request to the various servers processing the request and returning the result to the merchant. Each step involves different servers, which work together through message passing to complete the configuration and management tasks of the gate system.
[0068] In one embodiment, the user entry-related business process in the gate management system may include: Step 1: The user initiates a request based on the Android service to determine whether the device should be registered; Step 2: After receiving the request, the device communication service queries the device information through the merchant center of the middle platform; Step 3: The merchant center in the middle platform returns the device registration result to the device communication service; Step 4: The device communication service returns the device registration result to the Android service; Step 5: The Android service sends a request to the device communication service to obtain the device consumption plan; Step 6: The device communication service forwards the request to the backend service to obtain the device consumption plan; Step 7: The backend service forwards the request to the middleware billing service to obtain the device consumption plan; Step 8: The middleware billing service returns the device consumption plan to the backend service; Step 9: The backend service returns the device consumption plan to the device communication service; Step 10: The device communication service returns the device consumption plan to the Android service, and the user obtains the device consumption plan; Step 11: The user obtains the device's QR code; Step 12: Bind the device communication service to the device's QR code; Step 13: The user enters the turnstile; Step 14: The user sends the gate opening parameters, including online payment (WeChat / Alipay), membership code, and membership card; Step 15: The device communication service sends a billing request to the cashier service. Step 16: The cashier service forwards the item deduction request to the middle-office billing service; Step 17: The middle-office billing service executes the deduction operation based on the project deduction request and returns the deduction result to the cashier service; Step 18: The cashier service will return the deduction result to the device communication service; Step 19: Make an online payment in the Member Center; Step 20: The order payment service returns the payment result to the middleware billing service; Step 21: The billing service returns the project deduction and payment results to the member center; Step 22: The member center returns the entry result to the user; Step 23: The user re-enters the turnstile; Step 24: After scanning the code, the user scans the code to enter the gate; Step 25: The user sends an automatic gate opening request; Step 26: The equipment communication service issues an automatic gate opening command; Step 27: The device communication service returns the automatic gate opening result to the member center.
[0069] The above process demonstrates the complete process from a user entering the gate to completing payment and exiting the gate. Each step involves different servers, which work together through message passing to complete the gate system configuration, payment, and gate opening tasks.
[0070] In one embodiment, the user exit-related business process in the gate management system may include: Step 1: User applies to exit the gate; Step 2: After receiving the user's exit request, the Android service sends the gate parameters to the device communication service. Step 3: The device communication service sends a gate request to the backend service; Step 4: After receiving the exit request, the backend service determines whether the user has taken action; if there is no timeout, it returns the exit result to the device communication service. Step 5: The device communication service forwards the gate exit result to the Android service; Step 6: After the Android service responds with the gate exit result, the gate device opens the gate; Step 7: If the user times out, the backend service returns a timeout payment request to the device communication service; Step 8: The device communication service will forward the overdue payment to the Android service; Step 9: After the Android service responds to the payment timeout, the user scans the code to pay. Step 10: User scans payment code; Step 11: The Android service sends the payment string information to the device communication service; Step 12: The device communication service sends payment information to the cashier service; Step 13: The cashier service forwards payment information to the middle-office billing service; Step 14: The order payment service sends the payment result to the middleware billing service; Step 15: The middle-platform billing service forwards the payment result to the Duojinbao payment callback service; Step 16: Duojinbao payment callback service forwards the payment result to the device communication service; Step 17: The device communication service forwards the payment result to the Android service; Step 18: After the Android service receives the payment result, the gate device opens. Step 19: User scans QR code to open the gate; Step 20: Member C sends an exit request to the backend service; Step 21: After receiving the exit request, the backend service determines whether the user has timed out. If not, the gate opens. Step 22: Member C sends a gate opening request to the device communication service; Step 23: The device communication service sends a gate opening command to the Android service; Step 24: The Android service sends the startup result to the device communication service; Step 25: The device communication service forwards the startup result to the member's C-end; Step 26: Open the gate; Step 27: The backend service determines that the user has timed out and returns an overtime deduction to the member's client. Step 28: User pays the fee; Step 29: The user returns payment information to the member (C-end); Step 30: The member (C-end) forwards payment information to the order payment service; Step 31: The order payment service returns the payment result to the Duojinbao payment callback service; Step 32: The Duojinbao payment callback service returns a message to the device communication service to start the device; Step 33: The device communication service forwards the device startup information to the Android service; Step 34: Open the gate.
[0071] This invention distinguishes between whether a user has timed out and plans different processing paths accordingly. It involves the collaboration of multiple modules such as Android service, device communication service, backend service, cashier service, and middleware billing service to complete a series of operations such as gate exit determination, payment (if timed out), and gate opening, thereby optimizing operation management and improving user experience.
[0072] refer to Figure 2 , Figure 2 This is a flowchart illustrating the gate management method provided by the present invention. The gate management method provided by the present invention includes the following steps: Step 101: Receive the configuration request sent by the merchant management module; Step 102: If the configuration request is a request to add a QR code consumption scheme, then send the billing rule parameters of the new QR code consumption scheme to the middle platform billing service module so that the middle platform billing service module can verify the legality of the billing rule parameters and generate the scheme ID of the new QR code consumption scheme. Step 103: If the configuration request is a request to add a new gate device, then send the device information of the new gate device to the middle platform merchant center module so that the middle platform merchant center module can verify the uniqueness of the device information and generate the ID of the new gate device. Step 104: If the configuration request is a request to add a new gate terminal, then send a binding instruction for the new gate terminal to the middleware merchant center module so that the middleware merchant center module can verify the legality of the binding instruction.
[0073] During the process of adding a new QR code payment scheme, the merchant selects to create a new QR code payment scheme (e.g., 30 yuan / hour or 5 yuan / time) on the management side, triggering the merchant management module to send a request to the backend service module. Upon receiving the request, the backend service module assembles the specific billing rule parameters. For example, based on the merchant's selected billing type (hourly / time-based) and the entered price rules, it converts the user input into structured data recognizable by the middle platform billing service module, such as converting "30 yuan / hour" into a recognizable JSON data structure. Then, the backend service module calls the middle platform billing service module's API (Application Programming Interface) through the Feign client to submit a scheme configuration request. After the middle platform billing service module completes the validation and storage of the billing rule parameters, it returns a unique scheme ID (e.g., scheme_id:1001). The backend service module then transmits the configuration result returned by the middle platform billing service module back to the merchant's front-end interface, displaying "Successfully added" or the reason for failure.
[0074] During the process of adding a new turnstile device, the merchant registers the physical turnstile device information (such as device serial number SN_123456) in the management terminal, triggering the merchant management module to send a request to the backend service module to add the turnstile device. The backend service module retrieves the device information of the new turnstile device based on the received request, and then calls the middleware merchant center module to verify the device's legality and uniqueness (to prevent duplicate registration). After the middleware merchant center module passes the verification, it assigns a unique device ID (such as device_id:2024) to the newly added turnstile device and persistently stores the device's basic information (location, model, etc.). Simultaneously, the middleware merchant center module sends the result of the turnstile device addition, such as whether the device addition was successful, to the merchant management module through the backend service module.
[0075] During the process of adding a new turnstile terminal, the merchant enters relevant information about the new terminal in the management terminal, such as the terminal's device ID, terminal type, and associated QR code payment scheme ID. This triggers the merchant management module to send a request to the backend service module to add the new turnstile terminal. Upon receiving the request, the backend service module retrieves the relevant information entered by the merchant and generates a binding instruction based on this information. Then, the backend service module calls the middleware merchant center module and sends the binding instruction to it. The middleware merchant center module verifies the validity of the binding instruction, for example, checking whether the terminal's device ID has already been used (to prevent duplicate registration), verifying whether the terminal type conforms to the specifications, and confirming the validity of the QR code payment scheme ID. Finally, the middleware merchant center module sends the result of adding the turnstile terminal to the merchant management module through the backend service module, informing the merchant whether the terminal addition was successful.
[0076] The gate management method provided in this invention receives configuration requests from a merchant management module. If the configuration request is for adding a QR code payment scheme, the method sends billing rule parameters of the new QR code payment scheme to the middleware billing service module, allowing the middleware billing service module to verify the legality of the billing rule parameters and generate a scheme ID for the new QR code payment scheme. If the configuration request is for adding a gate device, the method sends device information of the new gate device to the middleware merchant center module, allowing the middleware merchant center module to verify the uniqueness of the device information and generate an ID for the new gate device. If the configuration request is for adding a gate terminal, the method sends a binding instruction for the new gate terminal to the middleware merchant center module, allowing the middleware merchant center module to verify the legality of the binding instruction. This invention supports diverse billing modes and flexible device binding methods, enabling the system to better adapt to different business processes and management needs, thereby meeting the management requirements of different scenarios.
[0077] Figure 3 An example is a schematic diagram of the physical structure of an electronic device, such as... Figure 3As shown, the electronic device may include: a processor 310, a communications interface 320, a memory 330, and a communications bus 340, wherein the processor 310, the communications interface 320, and the memory 330 communicate with each other through the communications bus 340. The processor 310 can call logic instructions in the memory 330 to execute a gate management method, which includes: receiving a configuration request sent by the merchant management module; if the configuration request is a request to add a QR code consumption scheme, sending billing rule parameters of the new QR code consumption scheme to the middle platform billing service module so that the middle platform billing service module verifies the legality of the billing rule parameters and generates a scheme ID of the new QR code consumption scheme; if the configuration request is a request to add a gate device, sending device information of the new gate device to the middle platform merchant center module so that the middle platform merchant center module verifies the uniqueness of the device information and generates an ID of the new gate device; if the configuration request is a request to add a gate terminal, sending a binding instruction for the new gate terminal to the middle platform merchant center module so that the middle platform merchant center module verifies the legality of the binding instruction; wherein, the gate terminal is a terminal installed on the gate device.
[0078] Furthermore, the logical instructions in the aforementioned memory 330 can be implemented as software functional units and, when sold or used as independent products, can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention, essentially, or the part that contributes to the prior art, or a part 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 the present invention. 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.
[0079] On the other hand, the present invention also provides a computer program product, which includes a computer program that can be stored on a non-transitory computer-readable storage medium. When the computer program is executed by a processor, the computer can execute the gate management method provided by the above methods. The method includes: receiving a configuration request sent by the merchant management module; if the configuration request is a request to add a QR code consumption scheme, sending billing rule parameters of the new QR code consumption scheme to the middle platform billing service module so that the middle platform billing service module verifies the legality of the billing rule parameters and generates a scheme ID of the new QR code consumption scheme; if the configuration request is a request to add a gate device, sending device information of the new gate device to the middle platform merchant center module so that the middle platform merchant center module verifies the uniqueness of the device information and generates an ID of the new gate device; if the configuration request is a request to add a gate terminal, sending a binding instruction for the new gate terminal to the middle platform merchant center module so that the middle platform merchant center module verifies the legality of the binding instruction; wherein, the gate terminal is a terminal installed on the gate device.
[0080] In another aspect, the present invention also provides a non-transitory computer-readable storage medium storing a computer program thereon. When executed by a processor, the computer program implements the gate management method provided by the above methods. The method includes: receiving a configuration request sent by the merchant management module; if the configuration request is a request to add a QR code consumption scheme, sending billing rule parameters of the new QR code consumption scheme to the middle platform billing service module, so that the middle platform billing service module verifies the legality of the billing rule parameters and generates a scheme ID of the new QR code consumption scheme; if the configuration request is a request to add a gate device, sending device information of the new gate device to the middle platform merchant center module, so that the middle platform merchant center module verifies the uniqueness of the device information and generates an ID of the new gate device; if the configuration request is a request to add a gate terminal, sending a binding instruction for the new gate terminal to the middle platform merchant center module, so that the middle platform merchant center module verifies the legality of the binding instruction; wherein, the gate terminal is a terminal installed on the gate device.
[0081] The device embodiments described above are merely illustrative. 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 modules can be selected to achieve the purpose of this embodiment according to actual needs. Those skilled in the art can understand and implement this without any creative effort.
[0082] Through the above description of the embodiments, those skilled in the art can clearly understand that each embodiment can be implemented by means of software plus necessary general-purpose hardware platforms, and of course, it can also be implemented by hardware. Based on this understanding, the above technical solutions, in essence or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product can be stored in a computer-readable storage medium, such as ROM / RAM, magnetic disk, optical disk, etc., and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute the methods described in the various embodiments or some parts of the embodiments.
[0083] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, and not to limit them; although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features; and these modifications 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 the present invention.
Claims
1. A gate management system, characterized in that, include: The merchant management module is used to send configuration requests to the backend service module; The backend service module is used to receive configuration requests sent by the merchant management module. If the configuration request is a request to add a QR code consumption scheme, it sends the billing rule parameters of the new QR code consumption scheme to the middle platform billing service module; if the configuration request is a request to add a gate device, it sends the device information of the new gate device to the middle platform merchant center module; if the configuration request is a request to add a gate terminal, it sends a binding instruction for the new gate terminal to the middle platform merchant center module; wherein, the gate terminal is a terminal installed on the gate device. The middleware billing service module is used to verify the legality of the billing rule parameters and generate the scheme ID of the new QR code consumption scheme. The middleware merchant center module is used to verify the uniqueness of the device information, generate the ID of the new gate device, and verify the legality of the binding command.
2. The gate management system according to claim 1, characterized in that, The gate management system also includes a device communication service module and a terminal service module for the gate terminal; The merchant management module is also used to send basic functions and primary parameters to the backend service module; The backend service module is also used to forward the basic functions and primary parameters to the device communication service module; The device communication service module is used to forward the basic functions and primary parameters to the terminal service module; The terminal service module is used to perform parameter configuration operations based on the basic functions and primary parameters.
3. The gate management system according to claim 2, characterized in that, The gate management system also includes: The terminal service module is also used to send a query request to the device communication service module to determine whether the gate device is registered. The device communication service module is also used to obtain gate device information from the middleware merchant center module based on the query request, and to feed back the registration result of the gate device to the terminal service module based on the gate device information.
4. The gate management system according to claim 1, characterized in that, The gate management system also includes: The terminal service module is also used to send a request to the device communication service module to obtain the device consumption scheme of the gate device; The device communication service module is also used to forward the acquisition request to the backend service module; The backend service module is further configured to obtain the device consumption plan from the middle platform billing service module based on the acquisition request, and send the device consumption plan to the terminal service module through the device communication service module.
5. The gate management system according to claim 1, characterized in that, The gate management system also includes a cashier service module; The terminal service module is also used to send gate opening parameters to the equipment communication service module; The device communication service module is also used to send project deduction information to the cashier service module based on the gate opening parameters; The cashier service module is used to forward the project deduction information to the middle platform billing service module; The middleware billing service module is also used to perform deduction operations based on the project deduction information and send the deduction results to the cashier service module.
6. The gate management system according to claim 1, characterized in that, The gate management system also includes: The terminal service module is also used to send gate exit parameters to the equipment communication service module; The device communication service module is also used to send an exit request to the backend service based on the exit parameters; The backend service module is also used to determine whether the user has timed out based on the exit request. If there is no timeout, the exit result is sent to the terminal service module through the device communication service module.
7. A gate management method, characterized in that, Applied to the gate management system according to any one of claims 1 to 6, the method comprises: Receive configuration requests sent by the merchant management module; If the configuration request is a request to add a new QR code consumption scheme, then the billing rule parameters of the new QR code consumption scheme are sent to the middle platform billing service module so that the middle platform billing service module can verify the legality of the billing rule parameters and generate the scheme ID of the new QR code consumption scheme. If the configuration request is a request to add a new gate device, the device information of the new gate device is sent to the middle platform merchant center module so that the middle platform merchant center module can verify the uniqueness of the device information and generate the ID of the new gate device; If the configuration request is a request to add a new gate terminal, a binding instruction for the new gate terminal is sent to the middleware merchant center module so that the middleware merchant center module can verify the legality of the binding instruction; wherein, the gate terminal is a terminal installed on the gate device.
8. An electronic device comprising a memory, a processor, and a computer program stored in the memory and running on the processor, characterized in that, When the processor executes the computer program, it implements the gate management method as described in claim 7.
9. A non-transitory computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by the processor, it implements the gate management method as described in claim 7.
10. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by the processor, it implements the gate management method as described in claim 7.