Operation permission control method and device, storage medium and electronic device

Abstract

The application discloses a kind of operation authority control method and device, storage medium and electronic equipment.It relates to computer technical field, the method includes: in response to the login request initiated by first object, and after identity verification passes, according to the object identifier of the first object contained in login request, the opening record of target opening state associated with object identifier is inquired;In the case where the opening record of target opening state is inquired, whether the first object is allowed to log in according to target opening state is determined;In the case where the first object is allowed to log in and target opening state is overdue non-payment state, after the first object logs in successfully, overdue measure is written into the running context of current login session, and the target operation of the first object is controlled according to the running context. Solve the problem that the operation authority of agent is controlled by manual in the business scene of airline company selling bill through agent in the related art, there is the problem of low efficiency.

Description

Technical Field

[0001] This application relates to the field of computer technology, and more specifically, to a method and apparatus for controlling operating permissions, a storage medium, and an electronic device. Background Technology

[0002] Currently, in the business scenario of airlines selling tickets through agents, the control of agents' operating permissions mainly relies on manual processes, including the collection of evidence of violations, the issuance of written notices, follow-up on collection, confirmation of financial reconciliation, and manual restoration of permissions in multiple systems. This process consumes a lot of manpower and time, resulting in low efficiency.

[0003] In the business scenario where airlines sell tickets through agents, the reliance on manual control of agents' operational permissions in related technologies results in low efficiency, and no effective solution has yet been proposed. Summary of the Invention

[0004] The main objective of this application is to provide a method, apparatus, storage medium, and electronic device for controlling operating permissions, in order to solve the problem of low efficiency in the business scenario of airlines selling tickets through agents, where manual control of the agent's operating permissions is required.

[0005] To achieve the above objectives, according to one aspect of this application, a method for controlling operational permissions is provided. The method includes: responding to a login request initiated by a first object and authenticating the first object; after successful authentication, querying an order record associated with the object identifier of the first object contained in the login request, specifying a target order status, wherein the order record includes at least the object identifier of an object with abnormal behavior and overdue measures, the overdue measures including one or more of prohibiting login, prohibiting sales, and prohibiting refunds / changes, and the target order status being one or more of pending payment and overdue payment; if an order record for the target order status is found, determining whether to allow the first object to log in based on the target order status; if the first object is allowed to log in and the target order status is overdue payment, after successful login, writing the overdue measures into the runtime context of the current login session, and controlling the target operation of the first object based on the runtime context.

[0006] Furthermore, determining whether to allow the first party to log in based on the target invoice status includes: for invoices in the pending payment status, allowing the first party to log in and sending a payment reminder message to the first party; for invoices in the overdue payment status, determining whether to allow the first party to log in based on the overdue measures.

[0007] Furthermore, determining whether to allow the first object to log in based on the overdue measures includes: if the overdue measures include prohibiting login, then the login request is rejected; if the overdue measures do not include prohibiting login, then the login request is allowed.

[0008] Furthermore, the target operation includes one or more of the following: ticket sales operation and ticket refund / change operation. Access control for the target operation of the first object based on the operating context includes: upon receiving a request from the first object to initiate a ticket sales operation, if the overdue measures in the operating context include prohibition of sales, then the request for the ticket sales operation is rejected, and a first preset prompt message is returned to the first object; upon receiving a request from the first object to initiate a ticket refund / change operation, if the overdue measures in the operating context include prohibition of refunds / changes, then the request for the ticket refund / change operation is rejected, and a second preset prompt message is returned to the first object.

[0009] Furthermore, after pushing the payment reminder information to the first object, the method further includes: responding to the invoice payment request initiated by the first object, verifying whether the payment amount contained in the invoice payment request is consistent with the invoice amount contained in the invoice record in the pending payment status; if the payment amount contained in the invoice payment request is consistent with the invoice amount contained in the invoice record in the pending payment status, updating the pending payment status to the paid status.

[0010] Furthermore, the method also includes: traversing all invoice records in the database with pending payment status based on a preset time interval; for each invoice record, comparing the payment deadline in the invoice record with the current system time; if the payment deadline is earlier than or equal to the current system time, updating the pending payment status to overdue; if the payment deadline is later than the current system time, sending a reminder message to the object associated with the invoice record.

[0011] Furthermore, prior to responding to the login request initiated by the first object, the method also includes: generating and publishing an invoice record in response to the target object's confirmation of the abnormal behavior of the object with abnormal behavior.

[0012] To achieve the above objectives, according to another aspect of this application, an operation permission control device is provided. The device includes: a first processing unit, configured to respond to a login request initiated by a first object and authenticate the first object; after successful authentication, querying an order record associated with the object identifier of the first object contained in the login request, specifying a target order status, wherein the order record includes at least the object identifier of an object with abnormal behavior and overdue measures, the overdue measures including one or more of prohibiting login, prohibiting sales, and prohibiting refunds / changes, and the target order status being one or more of pending payment and overdue payment; a first determining unit, configured to determine whether to allow the first object to log in based on the target order status if an order record with the target order status is found; and a second processing unit, configured to, if the first object is allowed to log in and the target order status is overdue payment, write the overdue measures into the runtime context of the current login session after successful login, and perform permission control on the first object's target operation based on the runtime context.

[0013] Furthermore, the first determining unit includes: a first determining subunit, used to allow the first object to log in for invoice records in the pending payment status and to push payment reminder information to the first object; and a second determining subunit, used to determine whether to allow the first object to log in for invoice records in the overdue payment status based on overdue measures.

[0014] Furthermore, the second determining subunit includes: a first determining module, configured to reject the login request if the overdue measures include a ban on login; and a second determining module, configured to allow the login request if the overdue measures do not include a ban on login.

[0015] Furthermore, the second processing unit includes: a first processing subunit, configured to, upon receiving a request from the first object to initiate a ticket sales operation, reject the request for the ticket sales operation if the overdue measures in the operating context include a prohibition on sales, and return a first preset prompt message to the first object; and a second processing subunit, configured to, upon receiving a request from the first object to initiate a ticket refund or change operation, reject the request for the ticket refund or change operation if the overdue measures in the operating context include a prohibition on refunds or changes, and return a second preset prompt message to the first object.

[0016] Furthermore, the device also includes: a third processing unit, configured to, after pushing payment prompt information to the first object, respond to the invoice payment request initiated by the first object and verify whether the payment amount contained in the invoice payment request is consistent with the invoice amount contained in the invoice record in the pending payment status; and a fourth processing unit, configured to update the pending payment status to the paid status if the payment amount contained in the invoice payment request is consistent with the invoice amount contained in the invoice record in the pending payment status.

[0017] Furthermore, the device also includes: a fifth processing unit, used to traverse all invoice records with pending payment status in the database based on a preset time interval; a sixth processing unit, used to compare the payment deadline in each invoice record with the current system time; a seventh processing unit, used to update the pending payment status to overdue payment status if the payment deadline is earlier than or equal to the current system time; and an eighth processing unit, used to send a reminder message to the object associated with the invoice record if the payment deadline is later than the current system time.

[0018] Furthermore, the device also includes a generation unit, configured to generate and publish an invoice record in response to the target object's confirmation of the abnormal behavior of the object with abnormal behavior, prior to responding to the login request initiated by the first object.

[0019] According to another aspect of the present invention, an electronic device is also provided, comprising: a memory storing an executable program; and a processor for running the program, wherein the program executes an operation permission control method for any of the above-mentioned items during runtime.

[0020] According to another aspect of the present invention, a computer-readable storage medium is also provided, wherein a method for controlling the operation permissions of the device where the storage medium is located to perform any of the above-mentioned operations is provided when the program is running.

[0021] In this embodiment, the following steps are employed: Responding to a login request initiated by a first object, and authenticating the first object; after successful authentication, querying the order record associated with the object identifier and the target order status based on the object identifier of the first object contained in the login request, wherein the order record includes at least the object identifier of the object with abnormal behavior and overdue measures, the overdue measures including one or more of prohibiting login, prohibiting sales, and prohibiting refunds and changes, and the target order status being one or more of pending payment and overdue payment status; if an order record with the target order status is found, determining whether to allow the first object to log in based on the target order status; if the first object is allowed to log in and the target order status is overdue payment, after the first object successfully logs in, writing the overdue measures into the runtime context of the current login session, and controlling the target operation of the first object based on the runtime context. This solves the technical problem in related technologies where, in the business scenario of airlines selling tickets through agents, the reliance on manual control of the agent's operation permissions results in low efficiency.

[0022] In this solution, after identity verification, the system dynamically queries the invoice status based on the object identifier and loads overdue measures in real time using the runtime context mechanism. This achieves precise, dynamic, and automated control over the operational permissions of ticket agents. When an agent has invoices with outstanding or overdue payments, the system can intelligently determine whether to allow login. If login is allowed, the system will immediately intercept related operations at the session level for overdue measures such as prohibiting sales and prohibiting refunds and changes. This allows the system to push the agent to complete the payment without interrupting normal business processes, improving the efficiency of controlling operational permissions and responding to agent violations. Attached Figure Description

[0023] The accompanying drawings, which form part of this application, are used to provide a further understanding of this application. The illustrative embodiments and descriptions of this application are used to explain this application and do not constitute an undue limitation of this application. In the drawings:

[0024] Figure 1 A hardware structure block diagram of a computer terminal for implementing a method for controlling operational permissions is shown.

[0025] Figure 2 This is a flowchart of the operation permission control method provided in the embodiments of this application;

[0026] Figure 3 This is a schematic diagram of a control system for operation permissions provided according to an embodiment of this application;

[0027] Figure 4 This is a schematic diagram of the control flow of operation permissions provided in the embodiments of this application;

[0028] Figure 5 This is a schematic diagram of an operation permission control device provided according to an embodiment of this application;

[0029] Figure 6 This is a structural block diagram of an electronic device according to an embodiment of this application. Detailed Implementation

[0030] To enable those skilled in the art to better understand the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present application, and not all embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative effort should fall within the scope of protection of the present application.

[0031] It should be noted that the terms "first," "second," etc., in the specification, claims, and accompanying drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of this application described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0032] It should be noted that the information collected in this application (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for display, data used for analysis, etc.) are information and data authorized by the user or fully authorized by all parties. Furthermore, the collection, storage, use, processing, transmission, provision, disclosure, and application of this data all comply with relevant laws, regulations, and standards, and necessary measures have been taken to ensure compliance with public order and good morals. Corresponding access points are provided for users to choose whether to authorize or refuse. For example, interfaces are established between this system and relevant users or organizations, providing users with corresponding access points to choose whether to agree to or refuse automated decision-making results; if the user chooses to refuse, the process proceeds to the expert decision-making stage.

[0033] Example 1

[0034] According to an embodiment of this application, a method embodiment for controlling operation permissions is also provided. It should be noted that the steps shown in the flowchart in the accompanying drawings can be executed in a computer system such as a set of computer-executable instructions. Although a logical order is shown in the flowchart, in some cases, the steps shown or described may be executed in a different order than that shown here.

[0035] The method embodiment provided in Embodiment 1 of this application can be executed on a mobile terminal, computer terminal, or similar computing device. Figure 1 A hardware block diagram of a computer terminal (or mobile device) for implementing a method of controlling operational permissions is shown. Figure 1As shown, the computer terminal 10 (or mobile device) may include one or more processors 102 (shown as 102a, 102b, ..., 102n in the figure) 102 (processor 102 may include, but is not limited to, a microprocessor MCU or a programmable logic device FPGA, etc.), a memory 104 for storing data, and a transmission device 106 for communication functions. In addition, it may also include: a display, an input / output interface (I / O interface), a universal serial bus (USB) port (which may be included as one of the ports of a BUS bus), a network interface, a power supply, and / or a camera. Those skilled in the art will understand that... Figure 1 The structure shown is for illustrative purposes only and does not limit the structure of the aforementioned electronic device. For example, computer terminal 10 may also include... Figure 1 The more or fewer components shown, or having the same Figure 1 The different configurations shown.

[0036] It should be noted that the aforementioned one or more processors 102 and / or other data processing circuits are generally referred to herein as "data processing circuits". These data processing circuits may be embodied, in whole or in part, in software, hardware, firmware, or any other combination thereof. Furthermore, the data processing circuits may be a single, independent processing module, or may be integrated, in whole or in part, into any other element within the computer terminal 10 (or mobile device). As involved in the embodiments of this application, the data processing circuits serve as a processor control mechanism (e.g., selection of a variable resistor termination path connected to an interface).

[0037] The memory 104 can be used to store software programs and modules of application software, such as the program instructions / data storage device corresponding to the operation permission control method in this embodiment. The processor 102 executes various functional applications and data processing by running the software programs and modules stored in the memory 104, thereby implementing the above-mentioned operation permission control method. The memory 104 may include high-speed random access memory, and may also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some instances, the memory 104 may further include memory remotely located relative to the processor 102, and these remote memories can be connected to the computer terminal 10 via a network. Examples of such networks include, but are not limited to, the Internet, corporate intranets, local area networks, mobile communication networks, and combinations thereof.

[0038] The transmission device 106 is used to receive or send data via a network. Specific examples of the network described above may include a wireless network provided by the communication provider of the computer terminal 10. In one example, the transmission device 106 includes a Network Interface Controller (NIC), which can connect to other network devices via a base station to communicate with the Internet. In another example, the transmission device 106 may be a Radio Frequency (RF) module, used for wireless communication with the Internet.

[0039] The display may be a touchscreen liquid crystal display (LCD) that allows the user to interact with the user interface of the computer terminal 10 (or mobile device).

[0040] Under the aforementioned operating environment, this application provides the following: Figure 2 The method for controlling operation permissions is shown. Figure 2 This is a flowchart of an operation permission control method according to Embodiment 1 of this application. The operation permission control method includes:

[0041] Step S201: In response to the login request initiated by the first object, the first object is authenticated. After the authentication is successful, the object identifier of the first object contained in the login request is used to query the order record associated with the object identifier and the target order status. The order record includes at least the object identifier of the object with abnormal behavior and overdue measures. The overdue measures include one or more of the following: prohibiting login, prohibiting sales, and prohibiting refunds and changes. The target order status is one or more of the following: pending payment status and overdue payment status.

[0042] Step S202: If an order record with the target order status is found, determine whether to allow the first object to log in based on the target order status;

[0043] Step S203: If the first object is allowed to log in and the target invoice status is overdue and unpaid, after the first object successfully logs in, the overdue measures are written into the running context of the current login session, and the target operation of the first object is subject to permission control based on the running context.

[0044] Optionally, operational permissions refer to the various business functions that the agent can perform in the airline's sales system, including but not limited to logging into the system, selling tickets, refunding tickets, rescheduling, checking fares, and printing tickets. The control system responds to login requests initiated by the agent (i.e., the first object). For example, after the agent enters their username and password at the system front end and initiates a login request, the system first completes identity authentication. After successful authentication, the backend service uses the username (i.e., the object identifier) ​​as the query key to retrieve all invoice records in the invoice database with a status of "pending payment" or "overdue payment". The retrieved invoice records include fields such as: object identifier, invoice amount, payment period, reason for invoice, and overdue measures. If no matching record is found, an empty set is returned.

[0045] Optionally, the system allows the agent to log in if no invoice record with the target invoice status is found. If an invoice record with the target invoice status is found, the system determines whether to allow the agent to log in based on the target invoice status. For example, if the system finds the invoice record and its status is "overdue payment", it determines login permission based on the "login prohibited" field in the overdue measures: since the overdue measures for this record are only "prohibited sales" and "prohibited refunds and changes", and do not include "login prohibited", the system determines that the agent can complete the login; if the overdue measures for this record include "login prohibited", the system immediately interrupts the login process, returns an error message, such as "The account has been locked due to overdue payment, please contact the airline", and refuses to establish a session.

[0046] Optionally, after the agent successfully logs in, the system writes all overdue measures (such as "prohibited from logging in" and "prohibited from refunds and changes") in the order record into the current session's runtime context in the form of structured data. Then, when the agent initiates a ticket sales or refund / change operation, the system reads this session context first. If it detects that the corresponding operation is prohibited, it intercepts it in real time and pops up a preset prompt message until the agent completes the payment, updates the status, and clears the context, at which point the permissions can be restored to normal.

[0047] In an optional embodiment, Figure 3 This is a schematic diagram of a control system for operation permissions provided in an embodiment of this application, such as... Figure 3 As shown, the system includes an airline back-office order management module and an airline front-office agent sales module. The airline back-office order management module mainly includes the following:

[0048] Invoice Issuance Component: Used by airline managers to issue invoice records to agents who violate regulations. The invoice record information includes: agent information, reason for invoice, invoice amount, payment deadline, and measures to be taken for overdue payment, such as banning login, banning sales, and banning refunds and changes.

[0049] Invoice Inquiry Component: This component allows airline managers to query invoice records based on search criteria, such as invoice time range, payment deadline range, agent information, and invoice payment status.

[0050] Invoice Statistics Report Component: This component is used by airline managers to download statistical reports based on the query criteria for invoice inquiries, for purposes such as reconciliation and settlement.

[0051] Automatic Billing Record Processing Component: This component is used to periodically (e.g., every morning at midnight) query the billing records awaiting payment. It compares the overdue time of the billing record with the current time. If the overdue time is earlier than the current time, the status is updated from "Awaiting Payment" to "Overdue". If the overdue time is later than the current time by one day, an email notification is automatically sent to the agent in the billing record to remind them to make the payment.

[0052] The airline's front-desk agent sales module mainly includes the following:

[0053] Front-end login component: Used to obtain agent login information, including username and password, and verify agent login information. After identity verification is completed, the invoice query component in the front-end agent sales module can be called to query invoice records with pending payment and overdue payment status. If there are invoice records with pending payment, the agent is prompted to place an invoice for payment; if there are overdue invoice records, the overdue measures in the invoice records are recorded in the agent login session. If the overdue measures prohibit login, a pop-up window is displayed to the agent, such as "You have overdue invoice records and are prohibited from logging in. Please contact the airline."

[0054] Invoice Inquiry Component: Used to query the database for invoice records with pending payment status and overdue payment status for the currently logged-in agent.

[0055] Invoice Payment Component: Used to process payments for pending invoice records and pay the invoice amount.

[0056] The ticket sales component is used to check whether there are any overdue invoices that have been issued and paid on time and are prohibited from being sold. If so, a pop-up message will be displayed, such as "You have an overdue invoice record that is prohibited from being sold. Please pay first." If not, you can fill in the departure and arrival locations to search for flights, fill in the passenger information, check the fare, and then make a payment and issue a ticket.

[0057] The ticket refund and change component is used to check the agent's login session for any overdue invoices that are prohibited from being refunded or changed. If there are any, a pop-up message will appear, such as "You have an overdue invoice record that is prohibited from being refunded or changed. Please pay first." If there are no overdue invoices, then you can refund, change, or upgrade your ticket for an already issued ticket.

[0058] Optionally, in the operation permission control method provided in the embodiments of this application, before responding to the login request initiated by the first object, the method further includes: generating and publishing an invoice record in response to the target object's confirmation of the abnormal behavior of the object with abnormal behavior.

[0059] In an optional embodiment, Figure 4 This is a schematic diagram of the control flow of operation permissions provided in the embodiments of this application, such as... Figure 4 As shown, firstly, airline administrators (i.e., the target entity) issue invoices in the backend. For example, they can issue invoice records to violating agents through the invoice issuance component of the airline's backend invoice management module. The invoice record information includes: agent information, reason for issuance, invoice amount, payment deadline, and measures to be taken for overdue payment, such as banning login, banning sales, and banning refunds and changes. Optionally, the system can also automatically generate and issue invoice records if it detects abnormal behavior.

[0060] Optionally, in the operation permission control method provided in the embodiments of this application, determining whether to allow the first object to log in based on the target invoice status includes: for invoice records in the pending payment status, allowing the first object to log in and pushing payment reminder information to the first object; for invoice records in the overdue payment status, determining whether to allow the first object to log in based on overdue measures.

[0061] Optionally, in the operation permission control method provided in the embodiments of this application, determining whether to allow the first object to log in based on the overdue measures includes: if the overdue measures include prohibiting login, then the login request is rejected; if the overdue measures do not include prohibiting login, then the login request is allowed.

[0062] In an alternative embodiment, such as Figure 4 As shown, agents log in through the front-end login component of the airline's front-end agent sales module. This module uses the invoice query component to check invoices in the pending payment and overdue payment status. If there are no overdue payment invoices and no pending payment invoices, the agent proceeds with the sales process normally. If there are no overdue payment invoices but pending payment invoices, the agent is allowed to log in, and a payment reminder is sent to prompt them to make the payment. If there are overdue payment invoices, the overdue action is recorded in the agent's login session. If the overdue action prohibits login, a pop-up message is displayed to the agent, such as "You have overdue payment invoices and are prohibited from logging in. Please contact the airline." If there are overdue payment invoices, but the overdue action does not prohibit login, the agent can log in and proceed with subsequent operations.

[0063] Through the above process, intelligent and differentiated permission management of agent behavior is achieved, effectively avoiding business interruption caused by "one-size-fits-all" suspension, improving collection conversion rate and management efficiency.

[0064] In summary, by dynamically querying the invoice status based on the object identifier after successful identity verification and loading overdue measures in real time using the runtime context mechanism, precise, dynamic, and automated control of ticket agent operation permissions is achieved. When an agent has invoices with outstanding or overdue payments, the system can intelligently determine whether to allow login. If login is allowed, the system can immediately intercept related operations at the session level for overdue measures such as prohibiting sales and prohibiting refunds and changes. This allows the system to push the violating agent to complete the payment without interrupting normal business processes, thereby improving the efficiency of control over operation permissions and the efficiency of response to agent violations.

[0065] Optionally, in the operation permission control method provided in the embodiments of this application, the target operation includes one or more of the following: ticket sales operation and ticket refund / change operation. The permission control for the target operation of the first object based on the operating context includes: upon receiving a request from the first object to initiate a ticket sales operation, if the overdue measures in the operating context include prohibition of sales, then the request for the ticket sales operation is rejected, and a first preset prompt message is returned to the first object; upon receiving a request from the first object to initiate a ticket refund / change operation, if the overdue measures in the operating context include prohibition of refunds / changes, then the request for the ticket refund / change operation is rejected, and a second preset prompt message is returned to the first object.

[0066] In an optional embodiment, when an agent enters the sales process, the system receives a ticket sales request initiated by the agent. The ticket sales component verifies whether there are any overdue invoices in the user session and whether the overdue measures prohibit sales. If so, the system rejects the ticket sales request and returns a first preset prompt message, such as "You have overdue invoice records, sales are prohibited, please pay first." If not, the user can fill in the departure and arrival locations, search for flights, fill in the passenger information, search for fares, and then make payment and issue tickets.

[0067] In an optional embodiment, when an agent enters the refund / change process, the system receives the ticket refund / change request initiated by the agent. The ticket refund / change component verifies whether there are any overdue invoices in the user session and whether the overdue measures prohibit refunds / changes. If so, the system rejects the ticket refund / change request and returns a second preset prompt message, such as "You have overdue invoice records, which prohibit refunds / changes. Please pay first." If not, the system can process refunds or rescheduling / upgrades for already issued ticket orders.

[0068] The above process can improve the efficiency of debt collection and compliance management, encourage agents who violate regulations to pay fees, and improve the efficiency of controlling operational authority.

[0069] Optionally, in the operation permission control method provided in the embodiments of this application, after pushing payment prompt information to the first object, the method further includes: responding to the invoice payment request initiated by the first object, verifying whether the payment amount contained in the invoice payment request is consistent with the invoice amount contained in the invoice record in the pending payment state; if the payment amount contained in the invoice payment request is consistent with the invoice amount contained in the invoice record in the pending payment state, updating the pending payment state to the paid state.

[0070] In an optional embodiment, after receiving a payment prompt, the agent proceeds to the invoice payment stage to pay for any pending or overdue invoices. Upon completion of payment, the invoice status is updated to "paid." For example, if the agent initiates an invoice payment request and clicks the "Pay Now" button, the system displays a payment page. After entering the payment amount, the agent sends the payment request to the backend. The backend service retrieves the record corresponding to the invoice number from the database and compares the payment amount in the request with the original invoice amount. If they match, the system automatically updates the invoice record's status from "pending payment" to "paid," clears all overdue measures from the agent's session context, and returns a success message to the agent: "Invoice payment successful, your sales and refund / modification permissions have been restored." If they do not match, the payment request is rejected, and a message "Payment amount does not match invoice amount, please check and re-pay" is returned.

[0071] Through the above process, the accuracy of airline financial reconciliation and the rigor of invoice execution are ensured, accurate control of operational permissions is achieved, and the efficiency of operational permission control is improved.

[0072] Optionally, in the operation permission control method provided in the embodiments of this application, the method further includes: traversing all billing records in the database with pending payment status based on a preset time interval; for each billing record, comparing the payment period in the billing record with the current system time; if the payment period is earlier than or equal to the current system time, updating the pending payment status to overdue and unpaid status; if the payment period is later than the current system time, sending a prompt message to the object associated with the billing record.

[0073] In an optional embodiment, the automatic billing record processing component iterates through all billing records in the database with a pending payment status based on a preset time interval (e.g., midnight every day). It compares the overdue time of each billing record with the current time. If the overdue time is earlier than the current time, the status is updated from pending payment to overdue. If it is later than the current time by one day, an email notification is automatically sent to the agent in the billing record to remind them to make the payment.

[0074] In an optional embodiment, when an agent is found to have violated regulations, airline management can issue an invoice to the violating agent in the background, explaining the reason for the fee collection, setting a payment deadline, and outlining the operational restrictions to be imposed for overdue payments. If the agent still fails to pay by the deadline, the system will restrict the agent's sales activities according to the restrictions set in the invoice. This achieves automatic restriction of the agent's sales behavior, providing timely and efficient control over violating agents, saving time and manpower costs, and effectively achieving the goal of recovering and regulating agent sales behavior.

[0075] The operation permission control method provided in this application embodiment adopts the following steps: Responding to a login request initiated by a first object, and authenticating the first object; after successful authentication, querying the order record associated with the object identifier and the target order status based on the object identifier of the first object contained in the login request, wherein the order record includes at least the object identifier of the object with abnormal behavior and overdue measures, the overdue measures including one or more of prohibiting login, prohibiting sales, and prohibiting refunds and changes, and the target order status is one or more of pending payment status and overdue payment status; if an order record with the target order status is found, determining whether to allow the first object to log in based on the target order status; if the first object is allowed to log in and the target order status is overdue payment status, after the first object successfully logs in, writing the overdue measures into the running context of the current login session, and controlling the target operation of the first object based on the running context. This solves the technical problem in related technologies where, in the business scenario of airlines selling tickets through agents, the reliance on manual control of the agent's operation permissions is inefficient.

[0076] In this solution, after identity verification, the system dynamically queries the invoice status based on the object identifier and loads overdue measures in real time using the runtime context mechanism. This achieves precise, dynamic, and automated control over the operational permissions of ticket agents. When an agent has invoices with outstanding or overdue payments, the system can intelligently determine whether to allow login. If login is allowed, the system will immediately intercept related operations at the session level for overdue measures such as prohibiting sales and prohibiting refunds and changes. This allows the system to push the agent to complete the payment without interrupting normal business processes, improving the efficiency of controlling operational permissions and responding to agent violations.

[0077] It should be noted that the steps shown in the flowchart in the accompanying drawings can be executed in a computer system such as a set of computer-executable instructions, and although a logical order is shown in the flowchart, in some cases the steps shown or described may be executed in a different order than that shown here.

[0078] Example 2

[0079] This application also provides an operation permission control device. It should be noted that the operation permission control device of this application can be used to execute the operation permission control method provided in this application. The operation permission control device provided in this application is described below.

[0080] According to an embodiment of this application, a control device for operation permissions to implement the above-described operation permission control method is also provided, such as... Figure 5 As shown, the device includes: a first processing unit 501, a first determining unit 502, and a second processing unit 503.

[0081] The first processing unit 501 is used to respond to the login request initiated by the first object and to authenticate the first object. After the authentication is successful, it queries the order record associated with the object identifier of the first object contained in the login request and the target order status. The order record includes at least the object identifier of the object with abnormal behavior and overdue measures. The overdue measures include one or more of the following: prohibiting login, prohibiting sales, and prohibiting refunds and changes. The target order status is one or more of the following: pending payment status and overdue non-payment status.

[0082] The first determining unit 502 is used to determine whether to allow the first object to log in based on the target order status when an order record with the target order status is found.

[0083] The second processing unit 503 is used to write the overdue measures into the running context of the current login session after the first object successfully logs in, and to perform permission control on the target operation of the first object according to the running context, provided that the first object is allowed to log in and the target invoice status is overdue and unpaid.

[0084] The operation permission control device provided in this application embodiment responds to the login request initiated by the first object through the first processing unit 501 and verifies the identity of the first object. After the identity verification is successful, the device queries the order record associated with the object identifier of the first object in the login request, which is related to the target order status. The order record includes at least the object identifier of the object with abnormal behavior and overdue measures. The overdue measures include one or more of the following: prohibiting login, prohibiting sales, and prohibiting refunds and changes. The target order status is one or more of the following: pending payment status and overdue payment status. If the order record of the target order status is found, the first determining unit 502 determines whether to allow the first object to log in based on the target order status. If the first object is allowed to log in and the target order status is overdue payment status, the second processing unit 503 writes the overdue measures into the running context of the current login session after the first object logs in successfully, and performs permission control on the target operation of the first object based on the running context.

[0085] Optionally, in the operation permission control device provided in the embodiments of this application, the first determining unit includes: a first determining subunit, used to allow the first object to log in for invoice records in the pending payment state and push payment reminder information to the first object; and a second determining subunit, used to determine whether to allow the first object to log in for invoice records in the overdue payment state based on overdue measures.

[0086] Optionally, in the operation permission control device provided in the embodiments of this application, the second determining subunit includes: a first determining module, used to reject the login request if the overdue measures include prohibiting login; and a second determining module, used to allow the login request if the overdue measures do not include prohibiting login.

[0087] Optionally, in the operation permission control device provided in the embodiments of this application, the second processing unit includes: a first processing subunit, configured to, upon receiving a request from a first object to initiate a ticket sales operation, reject the request for a ticket sales operation if the overdue measures in the operating context include prohibition of sales, and return a first preset prompt message to the first object; and a second processing subunit, configured to, upon receiving a request from a first object to initiate a ticket refund or change operation, reject the request for a ticket refund or change operation if the overdue measures in the operating context include prohibition of refund or change, and return a second preset prompt message to the first object.

[0088] Optionally, in the operation permission control device provided in the embodiments of this application, the device further includes: a third processing unit, configured to, after pushing payment prompt information to the first object, respond to the invoice payment request initiated by the first object and verify whether the payment amount contained in the invoice payment request is consistent with the invoice amount contained in the invoice record in the pending payment state; and a fourth processing unit, configured to, if the payment amount contained in the invoice payment request is consistent with the invoice amount contained in the invoice record in the pending payment state, update the pending payment state to the paid state.

[0089] Optionally, in the operation permission control device provided in the embodiments of this application, the device further includes: a fifth processing unit, used to traverse all invoice records with pending payment status in the database based on a preset time interval; a sixth processing unit, used to compare the payment period in each invoice record with the current system time; a seventh processing unit, used to update the pending payment status to overdue payment status if the payment period is earlier than or equal to the current system time; and an eighth processing unit, used to send a reminder message to the object associated with the invoice record if the payment period is later than the current system time.

[0090] Optionally, in the operation permission control device provided in the embodiments of this application, the device further includes: a generation unit, used to generate and publish an invoice record in response to the target object's confirmation of the abnormal behavior of the object with abnormal behavior before responding to the login request initiated by the first object.

[0091] It should be noted that the first processing unit 501, the first determining unit 502, and the second processing unit 503 mentioned above correspond to steps S201 to S203 in Embodiment 1. The three units and the corresponding steps implement the same instances and application scenarios, but are not limited to the content disclosed in Embodiment 1. It should be noted that the above modules or units can be hardware or software components stored in memory (e.g., memory 104) and processed by one or more processors (e.g., processors 102a, 102b, ..., 102n). The above units can also be part of a device and run in the computer terminal 10 provided in Embodiment 1.

[0092] Example 3

[0093] Embodiments of this application may provide an electronic device. Figure 6 This is a structural block diagram of an electronic device according to an embodiment of this application. Figure 6 As shown, the electronic device may include: one or more ( Figure 6 (Only one is shown) Processor 602, memory 604, memory controller, and peripheral interface, wherein the peripheral interface is connected to the radio frequency module, audio module and display.

[0094] The memory can be used to store software programs and modules, such as the program instructions / modules corresponding to the methods and apparatus in the embodiments of this application. The processor executes various functional applications and data processing by running the software programs and modules stored in the memory, thereby implementing the above-described methods. The memory may include high-speed random access memory, and may also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some instances, the memory may further include memory remotely located relative to the processor, and these remote memories can be connected to the terminal via a network. Examples of such networks include, but are not limited to, the Internet, corporate intranets, local area networks, mobile communication networks, and combinations thereof.

[0095] The processor can invoke information and applications stored in the memory via the transmission device to perform the following steps: responding to a login request initiated by a first object and authenticating the first object; after successful authentication, querying the invoice record associated with the object identifier of the first object contained in the login request, whereby the invoice record includes at least the object identifier of the object with abnormal behavior and overdue measures, the overdue measures including one or more of prohibiting login, prohibiting sales, and prohibiting refunds and changes, and the target invoice status is one or more of pending payment status and overdue payment status; if an invoice record with the target invoice status is found, determining whether to allow the first object to log in based on the target invoice status; if the first object is allowed to log in and the target invoice status is overdue payment status, after the first object successfully logs in, writing the overdue measures into the runtime context of the current login session, and performing access control on the target operation of the first object based on the runtime context.

[0096] The processor can access the information and application stored in the memory via the transmission device to perform the following steps: for invoice records in the pending payment status, allow the first object to log in and push payment reminder information to the first object; for invoice records in the overdue payment status, determine whether to allow the first object to log in based on the overdue measures.

[0097] The processor can access information and applications stored in memory via a transmission device to perform the following steps: if the overdue measures include prohibiting login, then the login request is rejected; if the overdue measures do not include prohibiting login, then the login request is allowed.

[0098] The processor can invoke information and application programs stored in the memory through the transmission device to perform the following steps: upon receiving a request from a first object to initiate a ticket sales operation, if the overdue measures in the operating context include prohibition of sales, the processor rejects the request for the ticket sales operation and returns a first preset prompt message to the first object; upon receiving a request from the first object to initiate a ticket refund or change operation, if the overdue measures in the operating context include prohibition of refunds or changes, the processor rejects the request for the ticket refund or change operation and returns a second preset prompt message to the first object.

[0099] The processor can invoke the information and application stored in the memory through the transmission device to perform the following steps: after pushing payment prompt information to the first object, in response to the invoice payment request initiated by the first object, verify whether the payment amount contained in the invoice payment request is consistent with the invoice amount contained in the invoice record in the pending payment status; if the payment amount contained in the invoice payment request is consistent with the invoice amount contained in the invoice record in the pending payment status, update the pending payment status to the paid status.

[0100] The processor can access the information and application programs stored in the memory via the transmission device to perform the following steps: based on a preset time interval, traverse all billing records in the database with pending payment status; for each billing record, compare the payment deadline in the billing record with the current system time; if the payment deadline is earlier than or equal to the current system time, update the pending payment status to overdue; if the payment deadline is later than the current system time, send a reminder message to the object associated with the billing record.

[0101] The processor can invoke information and applications stored in memory via the transmission device to perform the following steps: before responding to a login request initiated by the first object, in response to the target object's confirmation of the abnormal behavior of the object with abnormal behavior, generate and publish an invoice record.

[0102] Those skilled in the art will understand that Figure 6 The structure shown is for illustrative purposes only. Electronic devices can also be smartphones, tablets, handheld computers, mobile internet devices (MIDs), PADs, and other terminal devices. Figure 6 This does not limit the structure of the aforementioned electronic device. For example, electronic devices may also include components that are more... Figure 6 The more or fewer components shown (such as network interfaces, display devices, etc.), or having the same Figure 6 The different configurations shown.

[0103] Those skilled in the art will understand that all or part of the steps in the various methods of the above embodiments can be implemented by a program instructing the hardware related to the terminal device. The program can be stored in a computer-readable storage medium, which may include: flash drive, read-only memory (ROM), random access memory (RAM), disk or optical disk, etc.

[0104] Example 4

[0105] Embodiments of this application also provide a computer-readable storage medium. Optionally, in this embodiment, the storage medium can be used to store the program code executed by the operation permission control method provided in Embodiment 1.

[0106] Optionally, in this embodiment, the storage medium may be located in any computer terminal in a group of computer terminals in a computer network, or in any mobile terminal in a group of mobile terminals.

[0107] This application also provides a computer program product that, when executed on a data processing device, is suitable for performing operation permission control method steps.

[0108] The sequence numbers of the embodiments in this application are for descriptive purposes only and do not represent the superiority or inferiority of the embodiments.

[0109] In the above embodiments of this application, the descriptions of each embodiment have different focuses. For parts not described in detail in a certain embodiment, please refer to the relevant descriptions of other embodiments.

[0110] In the several embodiments provided in this application, it should be understood that the disclosed technical content can be implemented in other ways. The device embodiments described above are merely illustrative; for example, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the displayed or discussed mutual coupling, direct coupling, or communication connection may be through some interfaces; the indirect coupling or communication connection between units or modules may be electrical or other forms.

[0111] 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.

[0112] Furthermore, 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. The integrated unit can be implemented in hardware or as a software functional unit.

[0113] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a 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 all or 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 this application. The aforementioned storage medium includes various media capable of storing program code, such as a USB flash drive, read-only memory (ROM), random access memory (RAM), portable hard drive, magnetic disk, or optical disk.

[0114] The above description is only a preferred embodiment of this application. It should be noted that for those skilled in the art, several improvements and modifications can be made without departing from the principle of this application, and these improvements and modifications should also be considered within the scope of protection of this application.

Claims

1. A method for controlling operation permissions, characterized in that, include: In response to a login request initiated by a first object, and after the first object is authenticated, the system queries the order record associated with the first object's object identifier contained in the login request, which is associated with the target order status. The order record includes at least the object identifier of the object with abnormal behavior and overdue measures. The overdue measures include one or more of the following: prohibiting login, prohibiting sales, and prohibiting refunds and changes. The target order status is one or more of the following: pending payment status and overdue payment status. If an order record with the target order status is found, determine whether to allow the first object to log in based on the target order status; If the first object is allowed to log in and the target invoice status is overdue and unpaid, after the first object successfully logs in, the overdue measures are written into the running context of the current login session, and the target operation of the first object is subject to permission control based on the running context.

2. The method according to claim 1, characterized in that, Determining whether to allow the first object to log in based on the target order status includes: For the invoice records in the pending payment status, the first object is allowed to log in, and a payment prompt message is pushed to the first object; For the invoice records with overdue payment status, determine whether to allow the first object to log in based on the overdue measures.

3. The method according to claim 2, characterized in that, Determining whether to allow the first object to log in based on the overdue measures includes: If the overdue measures include prohibiting login, then the login request is rejected; If the overdue measures do not include prohibiting login, then the login request is allowed.

4. The method according to claim 1, characterized in that, The target operation includes one or more of the following: ticket sales operation and ticket refund / change operation. Access control for the target operation of the first object based on the runtime context includes: Upon receiving a request from the first object to initiate the ticket sales operation, if the overdue measures in the operating context include a prohibition on sales, the request to initiate the ticket sales operation is rejected, and a first preset prompt message is returned to the first object. Upon receiving a request from the first object to initiate the ticket refund / change operation, if the overdue measures in the operating context include prohibition of refunds / changes, the request to initiate the ticket refund / change operation is rejected, and a second preset prompt message is returned to the first object.

5. The method according to claim 2, characterized in that, After sending a payment notification message to the first object, the method further includes: In response to the invoice payment request initiated by the first object, verify whether the payment amount contained in the invoice payment request is consistent with the invoice amount contained in the invoice record in the pending payment status; If the payment amount included in the invoice payment request is consistent with the invoice amount included in the invoice record in the pending payment status, the pending payment status will be updated to the paid status.

6. The method according to claim 1, characterized in that, The method further includes: Based on a preset time interval, iterate through all invoice records in the database that are pending payment. For each of the aforementioned invoice records, the payment period in the invoice record is compared with the current system time; If the payment deadline is earlier than or equal to the current system time, the pending payment status will be updated to overdue payment status. If the payment deadline is later than the current system time, a reminder message is sent to the object associated with the invoice record.

7. The method according to claim 1, characterized in that, Prior to responding to a login request initiated by the first object, the method further includes: In response to the target object's confirmation of the abnormal behavior of the object with abnormal behavior, an invoice record is generated and published.

8. A device for controlling operating permissions, characterized in that, include: The first processing unit is configured to respond to a login request initiated by a first object and authenticate the first object. After successful authentication, based on the object identifier of the first object contained in the login request, it queries the order record associated with the object identifier and the target order status. The order record includes at least the object identifier of the object with abnormal behavior and overdue measures. The overdue measures include one or more of the following: prohibiting login, prohibiting sales, and prohibiting refunds and changes. The target order status is one or more of the following: pending payment status and overdue payment status. The first determining unit is used to determine whether to allow the first object to log in based on the target order status when an order record of the target order status is found. The second processing unit is configured to, when the first object is allowed to log in and the target invoice status is the overdue payment status, write the overdue measures into the running context of the current login session after the first object successfully logs in, and perform permission control on the target operation of the first object according to the running context.

9. A computer-readable storage medium, characterized in that, The computer-readable storage medium includes a stored executable program, wherein, when the executable program is executed, it controls the device containing the computer-readable storage medium to perform the operation permission control method according to any one of claims 1 to 7.

10. An electronic device, characterized in that, include: Memory, which stores executable programs; A processor for running the program, wherein the program executes the operation permission control method according to any one of claims 1 to 7 when it runs.

Images