CN116011971A - Service request control method and device - Google Patents
Service request control method and device Download PDFInfo
- Publication number
- CN116011971A CN116011971A CN202310031977.9A CN202310031977A CN116011971A CN 116011971 A CN116011971 A CN 116011971A CN 202310031977 A CN202310031977 A CN 202310031977A CN 116011971 A CN116011971 A CN 116011971A
- Authority
- CN
- China
- Prior art keywords
- interface
- target
- target user
- accumulated
- service platform
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Landscapes
- Information Transfer Between Computers (AREA)
Abstract
After obtaining a service request initiated by a target user, determining a first accumulated number of times that the target user accesses a query interface in an aviation service platform and a second accumulated number of times that the target user accesses a payment interface in the aviation service platform, and if the first accumulated number of times and the second accumulated number of times meet a set condition, limiting access of the query interface to the service request. According to the scheme, the computer is used for inquiring the interface access frequency and controlling the interface access, so that manpower is saved, and whether the inquiring interface exceeds the access frequency is discovered more timely.
Description
Technical Field
The present disclosure relates to the field of computer technologies, and in particular, to a service request control method and apparatus.
Background
With the continuous development of internet technology, various industries gradually introduce internet technology to improve the working efficiency. In the aviation industry, in order to facilitate the user's inquiry of flight conditions, a number of web travel agents (OnlineTravelAgency, OTA) are in charge, and OTA can provide clients with ticket booking, unsubscribing, purchasing products, etc. When a customer inquires about an airline flight through an OTA, the airline needs to inquire corresponding data from a black screen (Eterm) system after receiving the request, and the black screen system charges according to the data inquiry times. Based on this, in order to ensure the benefit of the airlines, the airlines need to set corresponding checking and comparing strategies, namely, when the number of times of querying the query interface of the airlines by using an OTA reaches the set number of times, a payment order must be generated to ensure the benefit of the airlines.
In the prior art, access control of an airline's query interface often requires human operations. After a worker needs to take a service log of a background service, judging whether the query interface exceeds the access amount or not through the statistics result of the use frequency of the query interface and the payment interface of the airline company, if the query interface exceeds the access amount, counting related contents into report mails, sending the report mails to the OTA, and carrying out corresponding punishment according to confirmed mails replied by the OTA. According to the method, the service access request is controlled through manual operation, so that the time from problem discovery to punishment is long, and the fact that the query interface exceeds the access limit cannot be timely discovered.
Disclosure of Invention
The application provides a service request control method and device, which can monitor and access control a query interface under the condition of no need of manual intervention, reduce the waste of manpower and material resources and improve the working efficiency.
In one aspect, the present application further provides a service request control method, including:
acquiring a service request initiated by a target user;
determining a first accumulated number of times that the target user accesses a query interface in an aviation service platform and a second accumulated number of times that the target user accesses a payment interface in the aviation service platform;
and if the first accumulated times and the second accumulated times meet the set conditions, carrying out access restriction of a query interface on the service request.
In yet another aspect, the present application further provides a service request control device, including:
a request acquisition unit, configured to acquire a service request initiated by a target user;
the number determining unit is used for determining a first accumulated number of times that the target user accesses the query interface in the aviation service platform and a second accumulated number of times that the target user accesses the payment interface in the aviation service platform;
and the access limiting unit is used for limiting the access of the query interface to the service request if the first accumulated times and the second accumulated times meet the set conditions.
As can be seen from the above, in the embodiment of the present application, after obtaining the service request initiated by the target user, the first accumulated number of times that the target user accesses the query interface in the aviation service platform and the second accumulated number of times that the target user accesses the payment interface in the aviation service platform are determined, and if the first accumulated number of times and the second accumulated number of times meet the set conditions, the access restriction of the query interface is performed on the service request. Compared with the prior art that the access times of the interface are inquired manually and the time and the labor are wasted in interface access control, the scheme utilizes the computer to inquire the access frequency of the interface and control the access of the interface, so that manpower is saved, and meanwhile, whether the access times of the inquired interface are exceeded or not can be found more timely.
Drawings
The above and other features, advantages, and aspects of embodiments of the present disclosure will become more apparent by reference to the following detailed description when taken in conjunction with the accompanying drawings. The same or similar reference numbers will be used throughout the drawings to refer to the same or like elements. It should be understood that the figures are schematic and that elements and components are not necessarily drawn to scale.
Fig. 1 is a schematic flow chart of a service request control method according to an embodiment of the present application;
fig. 2 is a schematic flow chart of another service request control method according to an embodiment of the present application;
fig. 3 is a schematic structural diagram of a service request control device according to an embodiment of the present application.
Detailed Description
Embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. While certain embodiments of the present disclosure have been shown in the accompanying drawings, it is to be understood that the present disclosure may be embodied in various forms and should not be construed as limited to the embodiments set forth herein, but are provided to provide a more thorough and complete understanding of the present disclosure. It should be understood that the drawings and embodiments of the present disclosure are for illustration purposes only and are not intended to limit the scope of the present disclosure.
The term "including" and variations thereof as used herein are intended to be open-ended, i.e., including, but not limited to. The term "based on" is based at least in part on. The term "one embodiment" means "at least one embodiment"; the term "another embodiment" means "at least one additional embodiment"; the term "some embodiments" means "at least some embodiments. Related definitions of other terms will be given in the description below.
It should be noted that the terms "first," "second," and the like in this disclosure are merely used to distinguish between different devices, modules, or units and are not used to define an order or interdependence of functions performed by the devices, modules, or units.
It should be noted that references to "one", "a plurality" and "a plurality" in this disclosure are intended to be illustrative rather than limiting, and those of ordinary skill in the art will appreciate that "one or more" is intended to be understood as "one or more" unless the context clearly indicates otherwise.
The following describes a service request control method provided in the embodiment of the present application.
Referring to fig. 1, a flow diagram of a service request control method provided in an embodiment of the present application is shown, and the present application may be applied to a computer device or a server, which is not limited thereto.
The method comprises the following steps:
step S100, obtaining a service request initiated by a target user.
The target user may be a network travel agency (OnlineTravelAgency, OTA), and the OTA is mainly used for conducting airline business on-line, for example: the air ticket is reserved, unsubscribed, products pushed by the airlines are purchased, and the like, so that the clients can conveniently inquire the service information of the airlines.
Of course, the target user may be other institutions or individuals who need to provide services by means of the data of the airlines, and the like, without limitation.
The service request of the target user can be divided into two parts, namely a query request, and the query request is mainly a query request for the service of an airline company. For convenience of description, taking a target user as an OTA as an example, an OTA client applies for an aviation service query to the OTA, and the OAT initiates a query request for a certain service to an airline company through a terminal, for example: reservation of air tickets, reservation of goods, purchase of goods, and the like. And secondly, a payment request is mainly a request of a target user for applying for paying for the number of times of inquiring the airline company. When the OTA needs to inquire the flight of the airline company, after the airline company receives the request initiated by the OTA, the airline company needs to inquire corresponding data from a black screen (Eterm) system, and the black screen system charges according to the data inquiry times. Based on the above, in order to ensure the benefit of the airlines, when the number of times that one OTA queries the query interface of the airlines reaches the set number of times, the airlines can generate corresponding payment orders to pay by the OTA.
There are many possible ways to obtain the service request initiated by the target user, and in this application, there is no limitation to this.
Step S110, determining a first accumulated number of times that the target user accesses the query interface in the aviation service platform and a second accumulated number of times that the target user accesses the payment interface in the aviation service platform.
The aviation service platform refers to a platform used by an airline company to provide application services, for example, the aviation service platform may be a server, a server cluster, a distributed server system, or the like of the airline company.
Wherein after obtaining the service request initiated by the target user, the target user accessing the airline interface may be determined. The specific manner of determining the target user initiating the access service request may be various, for example, the service request may carry identification information of the target user, or the target user associated with the sending terminal may be determined based on the sending terminal of the service request, which is not limited.
Based on the information, after the target user is determined, a historical access record of the target user accessing the aviation service platform can be determined, and the historical access record can record information such as accumulated times of the target user accessing all interfaces in the aviation service platform, so that a first accumulated times of the target user accessing the query interfaces in the aviation service platform and a second accumulated times of accessing the payment interfaces in the aviation service platform can be obtained, wherein the accumulated times are historical accesses.
The first accumulated times of the target user accessing the query interfaces in the aviation service platform can be accumulated times of the query interfaces related to the service request currently initiated by the target user, or accumulated times of all query interfaces of the target user accessing the airlines. Likewise, the second accumulated number of payment interfaces in the airline service platform may be the accumulated number of payment interfaces corresponding to the service request currently initiated by the target user, or the accumulated number of payment interfaces of the target user accessing the airline.
For ease of understanding, the following is given as an example of one possible scenario. Taking the accumulated times of all query interfaces and the accumulated times of all payment interfaces of the target user accessing the airline company as an example illustration, namely, the first accumulated times of the target user accessing at least one query interface configured in an airline service platform and the second accumulated times of the target user accessing at least one payment interface configured in the airline service platform are determined.
Such as: the airlines have A, B, C configured query interfaces and D, E, F configured payment interfaces. The service request initiated by the target user is a query request, and the accessed interface is an interface A. After obtaining the service request, the total number of accesses of the target user to the three interfaces, namely the query interface A, B and the query interface C in the airline service platform, may be queried, and the total number of accesses is taken as the first accumulated number. Similarly, the total number of accesses of the target user to the three interfaces of the payment interface D, E and F in the airline service platform is taken as the second cumulative number.
Wherein, for an interface, the accumulated number of times the interface recorded by the airline service platform may be the number of times the interface has been accessed before the service request. On the basis, for the interface which is required to be accessed by the service request (namely, the interface accessed by the target user), when the accumulated times of the interface are determined, the accumulated times of the history of the interface can be added with the accessed times.
Considering that the current access interface of the target user needs to be reflected in the accumulated times of the accessed interfaces, before determining the first accumulated times of the target user accessing at least one query interface configured in the airline service platform and the second accumulated times of the target user accessing at least one payment interface configured in the airline service platform, the target interface requested to be accessed by the service request may be determined first, and then the accumulated times of the target user accessing the target interface is increased by one, where the target interface is the query interface or the payment interface configured in the airline service platform.
Step S120, if the first accumulated times and the second accumulated times meet the set conditions, the service request is subjected to access restriction of the query interface.
The setting condition may be possible in many ways, and may be set based on the access requirement of the airlines to the query interface and the payment interface.
For example, in one implementation, the condition is that the ratio of the first accumulated number of times to the second accumulated number of times exceeds a threshold value, where the threshold value is a ratio of the number of times of accessing the query interface to the payment interface that is preset by human. Based on the foregoing, after obtaining the data query request of the OTA, the airline needs to perform the data query to the black screen system, but the data query is charged in the black screen system, for example: the inquiry is 1000 times, 10 yuan charge is needed, so in order to ensure that the benefit of the airlines is not impaired, the airlines need to generate a payment bill to the OTA inquiring the data, such as: 500 queries were run, charged 10 yuan. But not as much as the benefit, such as: the inquiry data is 100 times, and the price is 10 yuan, so that the utilization rate of the inquiry interface of the airline company is reduced, and the inquiry interface is also lost, and therefore, the specific ratio of the inquiry interface to the payment interface needs to be manually analyzed and determined.
And when the ratio of the query interface to the payment interface of the target user to the airline company is determined not to exceed the preset threshold, sending a service request to a background service, and carrying out corresponding query service or payment service. And when the ratio of the query interface to the payment interface of the target user to the airline company exceeds a preset threshold, limiting the access of the query interface to the service request.
Of course, there are many possible ways of access restriction, such as: the airline interface does not respond to the request of the query interface, discards the request, or returns a reminder that no access rights are available, etc.
In a manner that is easy to understand, access restrictions of the query interface are described. The access restriction in this approach is to return a reminder that does not have access rights.
Such as: the request amount of all query interfaces of the airline company cannot exceed 1 ten thousand per second, so that only the first 1 ten thousand query requests can pass through the gateway layer for corresponding request query in each second, the subsequent query requests can be limited, and finally, the request is directly returned to the user at the gateway layer too frequently, and the request is not sent to the background service for corresponding request query.
In one implementation, if the first accumulated times and the second accumulated times meet the set condition, a notification may be generated based on a preset notification template. If it is determined that the ratio of the number of times the target user accesses the query interface and the payment interface of the airline company exceeds the preset threshold, in order to remind the target user that the number of times the target user accesses the query interface has reached the limit, corresponding bill payment should be performed, and a corresponding reminding notification may be sent to the target user.
There are many possible ways to send alert notifications. And when the ratio of the target user to the query interface and the payment interface of the airline company exceeds the preset threshold value, the related information of the real-time query interface and the payment interface can be automatically filled in by utilizing the preset notification template and sent to the target user so that the target user can pay correspondingly.
Among other possible forms, alert notifications are various, such as: short messages, mails, etc., in this application, one or more alert notifications may be selected, which is not limited.
In this application, in this embodiment, after obtaining a service request initiated by a target user, a first accumulated number of times that the target user accesses a query interface in an aviation service platform and a second accumulated number of times that the target user accesses a payment interface in the aviation service platform are determined, and if the first accumulated number of times and the second accumulated number of times meet a set condition, access restriction of the query interface is performed on the service request. Compared with the prior art, the method takes time and labor for inquiring the access times of the interface and controlling the access of the interface manually, and the scheme utilizes the computer to inquire the access frequency of the interface and control the access of the interface, so that manpower is saved, and whether the access times of the inquired interface are exceeded or not is discovered more timely.
As can be seen from the foregoing description, after receiving an access request initiated by a target user, it may be possible to determine the cumulative access times of the query interface and the payment interface accessed by the target user, and accordingly, the specific manner of controlling access to the query interface may also be different, and an example of one of the service request control methods provided in the embodiments of the present application is described below. Fig. 2 is a schematic flow chart of another service request control method according to an embodiment of the present application, where the schematic flow chart includes the following steps:
step S200, obtaining a service request initiated by a target user.
Step S200 corresponds to step S100 in the foregoing embodiment, and the detailed description is referred to above, which is not repeated here.
Step S210, determining a target interface which is requested to be accessed by the service request.
After obtaining the service request of the target user, analyzing whether the type of the service request is a query request or a payment request, and determining a target interface matched with the service request based on the query request or the payment request. The target interface is a target query interface or a target payment interface, wherein the target query interface is one of at least one query interface configured in the aviation service platform, and the target payment interface is one of at least one payment interface configured in the aviation service platform.
Step S220, if the target interface accessed by the target user is the target query interface, determining a first accumulated number of times the target user accesses the target query interface and a second accumulated number of times the target user accesses a payment interface associated with the target query interface.
Wherein the target interface and the interface associated therewith are not of the same type of interface, such as: the target interface is a target query interface, and the associated interface associated with the target interface is one of at least one payment interface configured in the aviation service platform, or the target interface is a target payment interface, and the associated interface associated with the target interface is one of at least one query interface configured in the aviation service platform.
Based on this, if the target interface accessed by the target user is the target query interface, the interface associated therewith is the payment interface. If the target interface accessed by the target user is a target payment interface, the interface associated with the target user is a query interface.
After determining the target interface and the associated interface associated with the target interface, the first accumulated times and the second accumulated times need to be determined. The first accumulated times and the second accumulated times are historical access times.
For ease of understanding, the following examples are presented.
Such as: if the target interface accessed by the target user is a target query interface, determining a first accumulated number of times the target user accesses the target query interface and a second accumulated number of times a payment interface associated with the target query interface;
another example is: if the target interface accessed by the target user is the target payment interface, determining the first accumulated times of the target user accessing the query interface associated with the target payment interface and the second accumulated times of the target payment interface.
Wherein each accumulated number of times may be an accumulated number of times before the local service access request. Alternatively, each accumulated number of times may be an accumulated number of times of the present and historical access times. Since the current access is considered, in order to add the accumulated number of times to the number of times of the current access, the accumulated number of times of the target interface is added by one after the target interface of the current access is determined before the accumulated number of times is determined. Then, the first accumulated times and the second accumulated times are respectively determined.
Step S230, if the ratio of the first accumulated times to the second accumulated times exceeds the threshold value, the access limitation of the query interface is carried out on the service request.
In this embodiment, a setting condition is taken as an example, where the setting condition is that a ratio of the first accumulated times to the second accumulated times exceeds a threshold, and the threshold is a ratio manually set based on an optimal access amount of the query interface and the payment interface associated therewith, where the optimal access amount of the query interface and the payment interface associated therewith is also manually determined.
And when the ratio of the first accumulated times to the second accumulated times does not exceed a preset threshold, sending the service request to a background service to perform corresponding inquiry service or payment service. And when the ratio of the first accumulated times to the second accumulated times exceeds a preset threshold value, carrying out access restriction on the query interface on the service request.
In order to timely inform the target user of payment, a corresponding reminding notification can be sent, and the reminding notification is described in the foregoing and is not repeated here.
In the method, the first accumulated times and the second accumulated times of the target user accessing the aviation service platform interface are further determined by confirming the target interface requested by the service request, if the ratio of the first accumulated times to the second accumulated times exceeds the threshold value based on the first accumulated times and the second accumulated times, the service request is subjected to access restriction of the query interface, and in the embodiment, the actual access quantity of each interface can be clearly known by carrying out access control on the target interface and the associated interface thereof, and meanwhile, the set threshold value is dynamically adjusted. And the method can save manpower and find out whether the access times of the query interface are exceeded or not more timely.
The flowcharts and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
Although operations are depicted in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order. In certain circumstances, multitasking and parallel processing may be advantageous.
Computer program code for carrying out operations of the present disclosure may be written in one or more programming languages, including, but not limited to, an object oriented programming language such as Java, smalltalk, C ++ and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any kind of network, including but not limited to a Local Area Network (LAN) or a Wide Area Network (WAN), or may be connected to an external computer (for example, through the Internet using an Internet service provider).
The following describes a service request control device provided in the embodiment of the present application, and the service request control device described below and the service request control method described above may be referred to correspondingly.
Referring to fig. 3, an apparatus for service request control provided in the application embodiment is described, where, as shown in fig. 3, the apparatus for service request control may include:
a request acquiring unit 300, configured to acquire a service request initiated by a target user;
a number determining unit 310, configured to determine a first accumulated number of times the target user accesses the query interface in the aviation service platform and a second accumulated number of times the target user accesses the payment interface in the aviation service platform;
the access limiting unit 320 is configured to query the service request for access limitation of the interface if the first accumulated number of times and the second accumulated number of times meet the set condition.
Optionally, the number of times determining unit of the service request control device of the present application includes:
the number determining total unit is used for determining a first accumulated number of times that the target user accesses at least one query interface configured in the aviation service platform and a second accumulated number of times that the target user accesses at least one payment interface configured in the aviation service platform.
Optionally, the device for controlling service request of the present application may further include:
the system comprises a target interface determining unit, a service request processing unit and a service request processing unit, wherein the target interface determining unit is used for determining a target interface which is requested to be accessed by the service request before the first accumulated times of accessing a query interface in an aviation service platform and the second accumulated times of accessing a payment interface in the aviation service platform by a target user are determined by the times determining unit, the target interface is a target query interface or a target payment interface, the target query interface is one of at least one query interface configured in the aviation service platform, and the target payment interface is one of at least one payment interface configured in the aviation service platform;
the number of times determining unit includes:
the first time number determining unit is used for determining a first accumulated number of times that the target user accesses the target query interface and a second accumulated number of times that the target user accesses the payment interface associated with the target query interface if the target interface accessed by the target user is the target query interface;
and the second time determining unit is used for determining the first accumulated time of the target user accessing the query interface associated with the target payment interface and the second accumulated time of the target payment interface if the target interface accessed by the target user is the target payment interface.
Optionally, the device for controlling service request of the present application may further include:
and the first time number accumulating unit is used for adding one to the accumulated number of times that the target user accesses the target interface after the target interface determining unit determines the target interface which is requested to be accessed by the service request.
Optionally, the device for controlling service request of the present application may further include:
the target interface determining subunit is used for determining a target interface requested to be accessed by the service request before the number determining total unit determines a first accumulated number of times that the target user accesses at least one query interface configured in the aviation service platform and a second accumulated number of times that the target user accesses at least one payment interface configured in the aviation service platform, wherein the target interface is a query interface or a payment interface configured in the aviation service platform;
and the second time accumulating unit is used for adding one to the accumulated time of the target user accessing the target interface.
Optionally, the device for controlling service request of the present application may further include:
the notification generation unit is used for generating a reminding notification based on a preset notification template if the first accumulated times and the second accumulated times meet the set conditions, wherein the reminding notification is used for reminding a target user to pay fees;
and the notification output unit is used for outputting the reminding notification.
The units involved in the embodiments of the present disclosure may be implemented by means of software, or may be implemented by means of hardware. Wherein the names of the units do not constitute a limitation of the units themselves in some cases.
The functions described above herein may be performed, at least in part, by one or more hardware logic components. For example, without limitation, exemplary types of hardware logic components that may be used include: a Field Programmable Gate Array (FPGA), an Application Specific Integrated Circuit (ASIC), an Application Specific Standard Product (ASSP), a system on a chip (SOC), a Complex Programmable Logic Device (CPLD), and the like.
A computer readable medium is also provided in the present application.
The computer readable medium carries one or more programs which, when executed by the electronic device, cause the electronic device to:
acquiring a service request initiated by a target user;
determining a first accumulated number of times that the target user accesses a query interface in an aviation service platform and a second accumulated number of times that the target user accesses a payment interface in the aviation service platform;
and if the first accumulated times and the second accumulated times meet the set conditions, carrying out access restriction of a query interface on the service request.
In the context of this disclosure, a machine-readable medium may be a tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. The machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. The machine-readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of a machine-readable storage medium would include an electrical connection based on one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
It should be noted that the computer readable medium described in the present disclosure may be a computer readable signal medium or a computer readable storage medium, or any combination of the two. The computer readable storage medium can be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or a combination of any of the foregoing. More specific examples of the computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this disclosure, a computer-readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. In the present disclosure, however, the computer-readable signal medium may include a data signal propagated in baseband or as part of a carrier wave, with the computer-readable program code embodied therein. Such a propagated data signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination of the foregoing. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: electrical wires, fiber optic cables, RF (radio frequency), and the like, or any suitable combination of the foregoing.
The computer readable medium may be contained in the electronic device; or may exist alone without being incorporated into the electronic device.
According to one or more embodiments of the present disclosure, the embodiments of fig. 1 and 2 provide a service request control method, including:
acquiring a service request initiated by a target user;
determining a first accumulated number of times that the target user accesses a query interface in an aviation service platform and a second accumulated number of times that the target user accesses a payment interface in the aviation service platform;
and if the first accumulated times and the second accumulated times meet the set conditions, carrying out access restriction of a query interface on the service request.
Preferably, the determining the first accumulated number of times that the target user accesses the query interface in the aviation service platform and the second accumulated number of times that the target user accesses the payment interface in the aviation service platform includes:
a first cumulative number of times the target user accesses at least one query interface configured in an aviation service platform and a second cumulative number of times the target user accesses at least one payment interface configured in the aviation service platform are determined.
Preferably, before determining the first accumulated number of times the target user accesses the query interface in the aviation service platform and the second accumulated number of times the target user accesses the payment interface in the aviation service platform, the method further comprises:
determining a target interface requested to be accessed by the service request, wherein the target interface is a target query interface or a target payment interface, the target query interface is one of at least one query interface configured in the aviation service platform, and the target payment interface is one of at least one payment interface configured in the aviation service platform;
the determining the first accumulated times of the target user accessing the query interface in the aviation service platform and the second accumulated times of the target user accessing the payment interface in the aviation service platform comprises the following steps:
if the target interface accessed by the target user is a target query interface, determining a first accumulated number of times the target user accesses the target query interface and a second accumulated number of times a payment interface associated with the target query interface;
and if the target interface accessed by the target user is the target payment interface, determining the first accumulated times of the target user accessing the query interface associated with the target payment interface and the second accumulated times of the target payment interface.
Preferably, after the determining the target interface to which the service request requests access, the method further includes:
and adding one to the accumulated number of times that the target user accesses the target interface.
Preferably, before the determining the first accumulated number of times the target user accesses the at least one query interface configured in the aviation service platform and the second accumulated number of times the target user accesses the at least one payment interface configured in the aviation service platform, the method further comprises:
determining a target interface requested to be accessed by the service request, wherein the target interface is a query interface or a payment interface configured in an aviation service platform;
and adding one to the accumulated number of times that the target user accesses the target interface.
Preferably, the first and second accumulated times satisfy a set condition, including: the ratio of the first accumulated times to the second accumulated times exceeds a preset threshold value.
Preferably, the method further comprises:
if the first accumulated times and the second accumulated times meet the set conditions, generating a reminding notice based on a preset notice template, wherein the reminding notice is used for reminding the target user to pay fees;
and outputting the reminding notification.
Although the subject matter has been described in language specific to structural features and/or methodological acts, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are example forms of implementing the claims.
While several specific implementation details are included in the above discussion, these should not be construed as limiting the scope of the disclosure. Certain features that are described in the context of separate embodiments can also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment can also be implemented in multiple embodiments separately or in any suitable subcombination.
The foregoing description is only of the preferred embodiments of the present disclosure and description of the principles of the technology being employed. It will be appreciated by persons skilled in the art that the scope of the disclosure referred to in this disclosure is not limited to the specific combinations of features described above, but also covers other embodiments which may be formed by any combination of features described above or equivalents thereof without departing from the spirit of the disclosure. Such as those described above, are mutually substituted with the technical features having similar functions disclosed in the present disclosure (but not limited thereto).
Claims (10)
1. A service request control method, comprising:
acquiring a service request initiated by a target user;
determining a first accumulated number of times that the target user accesses a query interface in an aviation service platform and a second accumulated number of times that the target user accesses a payment interface in the aviation service platform;
and if the first accumulated times and the second accumulated times meet the set conditions, carrying out access restriction of a query interface on the service request.
2. The method of claim 1, wherein determining the first cumulative number of times the target user accesses the query interface in the aerial service platform and the second cumulative number of times the target user accesses the payment interface in the aerial service platform comprises:
a first cumulative number of times the target user accesses at least one query interface configured in an aviation service platform and a second cumulative number of times the target user accesses at least one payment interface configured in the aviation service platform are determined.
3. The method of claim 1, further comprising, prior to said determining the first cumulative number of times the target user accesses the query interface in the aerial service platform and the second cumulative number of times the target user accesses the payment interface in the aerial service platform:
determining a target interface requested to be accessed by the service request, wherein the target interface is a target query interface or a target payment interface, the target query interface is one of at least one query interface configured in the aviation service platform, and the target payment interface is one of at least one payment interface configured in the aviation service platform;
the determining the first accumulated times of the target user accessing the query interface in the aviation service platform and the second accumulated times of the target user accessing the payment interface in the aviation service platform comprises the following steps:
if the target interface accessed by the target user is a target query interface, determining a first accumulated number of times the target user accesses the target query interface and a second accumulated number of times a payment interface associated with the target query interface;
and if the target interface accessed by the target user is the target payment interface, determining the first accumulated times of the target user accessing the query interface associated with the target payment interface and the second accumulated times of the target payment interface.
4. A method according to claim 3, further comprising, after said determining the target interface to which said service request requests access:
and adding one to the accumulated number of times that the target user accesses the target interface.
5. The method of claim 2, further comprising, prior to said determining a first cumulative number of times the target user accesses at least one query interface configured in an aviation services platform and a second cumulative number of times the target user accesses at least one payment interface configured in the aviation services platform:
determining a target interface requested to be accessed by the service request, wherein the target interface is a query interface or a payment interface configured in an aviation service platform;
and adding one to the accumulated number of times that the target user accesses the target interface.
6. A method according to any one of claims 1 to 3, wherein the first and second cumulative numbers satisfy a set condition, comprising: the ratio of the first accumulated times to the second accumulated times exceeds a preset threshold value.
7. The method as recited in claim 1, further comprising:
if the first accumulated times and the second accumulated times meet the set conditions, generating a reminding notice based on a preset notice template, wherein the reminding notice is used for reminding the target user to pay fees;
and outputting the reminding notification.
8. A service request control apparatus, comprising:
a request acquisition unit, configured to acquire a service request initiated by a target user;
the number determining unit is used for determining a first accumulated number of times that the target user accesses the query interface in the aviation service platform and a second accumulated number of times that the target user accesses the payment interface in the aviation service platform;
and the access limiting unit is used for limiting the access of the query interface to the service request if the first accumulated times and the second accumulated times meet the set conditions.
9. The apparatus according to claim 8, wherein the number determining unit includes:
the number determining total unit is used for determining a first accumulated number of times that the target user accesses at least one query interface configured in the aviation service platform and a second accumulated number of times that the target user accesses at least one payment interface configured in the aviation service platform.
10. The apparatus as recited in claim 8, further comprising:
a target interface determining unit, configured to determine, before the number determining unit determines a first accumulated number of times the target user accesses a query interface in an aviation service platform and a second accumulated number of times accesses a payment interface in the aviation service platform, a target interface requested to be accessed by the service request, where the target interface is a target query interface or a target payment interface, the target query interface is one of at least one query interface configured in the aviation service platform, and the target payment interface is one of at least one payment interface configured in the aviation service platform;
the number of times determining unit includes:
a first time number determining unit, configured to determine a first accumulated number of times the target user accesses the target query interface and a second accumulated number of times the target user accesses a payment interface associated with the target query interface if the target interface accessed by the target user is the target query interface;
and the second time determining unit is used for determining the first accumulated time of the target user accessing the query interface associated with the target payment interface and the second accumulated time of the target payment interface if the target interface accessed by the target user is the target payment interface.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310031977.9A CN116011971A (en) | 2023-01-10 | 2023-01-10 | Service request control method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310031977.9A CN116011971A (en) | 2023-01-10 | 2023-01-10 | Service request control method and device |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN116011971A true CN116011971A (en) | 2023-04-25 |
Family
ID=86024640
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202310031977.9A Pending CN116011971A (en) | 2023-01-10 | 2023-01-10 | Service request control method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN116011971A (en) |
-
2023
- 2023-01-10 CN CN202310031977.9A patent/CN116011971A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108122139B (en) | Invoice data processing method, equipment and system | |
| CN110866709B (en) | Method and device for merging orders | |
| US20150032516A1 (en) | Managing electric vehicle (ev) charging station usage | |
| CN112150106A (en) | Method and device for processing order task and providing travel service | |
| CN109754292A (en) | Stop self-service billing method, device and electronic equipment | |
| CN114418551A (en) | Bill processing method and device, electronic equipment and storage medium | |
| CN112258220B (en) | Information acquisition and analysis method, system, electronic equipment and computer readable medium | |
| CN110826943B (en) | Method and related equipment for judging whether bus allocation is needed or not and determining bus allocation number | |
| CN116011971A (en) | Service request control method and device | |
| US20190347616A1 (en) | Systems and methods for transport of construction materials | |
| KR20200088025A (en) | Method for sharing total delivery taking | |
| US20120053967A1 (en) | System and Method for Account Reconciliation | |
| KR102474903B1 (en) | Methods for import cargo beforehand carrying out and system therefor | |
| CN111612402B (en) | Automatic arbitration method and device | |
| CN115034763A (en) | Processing method and device for government affair handling affairs, electronic equipment and storage medium | |
| CN113313392A (en) | Airline ticket waiting and supplementing ticket registering method, related device and computer storage medium | |
| CN113496321A (en) | Method and device for determining workload | |
| CN113269339A (en) | Method and system for automatically creating and distributing network appointment tasks | |
| US11775921B2 (en) | System and method for transportation management | |
| CN109784816A (en) | Express delivery distribution method and device | |
| CN113537574B (en) | Service processing aging pushing method and device, storage medium and computer equipment | |
| US20180075497A1 (en) | Database management system | |
| CN112766839B (en) | Convenient electronic payment system and method for railway freight station | |
| CN117808555A (en) | Additional service product processing method and related device | |
| CN111369204B (en) | Customs service management system |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |