CN114579211A

CN114579211A - Flow control method, device, equipment and system of service providing system

Info

Publication number: CN114579211A
Application number: CN202210158346.9A
Authority: CN
Inventors: 秦隆
Original assignee: Alibaba China Co Ltd
Current assignee: Alibaba China Co Ltd
Priority date: 2022-02-21
Filing date: 2022-02-21
Publication date: 2022-06-03

Abstract

The embodiment of the application provides a flow control method, a flow control device, flow control equipment and a flow control system of a service providing system. The method comprises the following steps: receiving a calling request aiming at a target interface and sent by a terminal, wherein the calling request is sent to a server by the terminal in response to the input operation of a user under the condition that the user logs in by using a login account, the parameters of the calling request comprise a first label, the first label is used for representing the importance degree of the calling request, the frequency threshold value corresponding to the first label under a flow control account corresponding to the login account is obtained, the called frequency of the flow control account in the current unit time to the target interface based on the first label is obtained, if the called frequency does not reach the frequency threshold value, processing corresponding to the calling request is executed, and a corresponding processing result is returned to the terminal. The method and the device can avoid the problem that the important call request for calling the interface later is rejected because more unimportant call requests call a certain interface first, and are favorable for improving the use experience of a user.

Description

Flow control method, device, equipment and system of service providing system

Technical Field

The present application relates to the field of computer technologies, and in particular, to a method, an apparatus, a device, and a system for controlling traffic in a service providing system.

Background

Currently, a user may use a service provided by a service provider by invoking an interface provided by the service provider.

Generally, a service provider may control flow for a user to call the same interface, and specifically, may limit a user to call a certain interface at most N times per minute. After the number of times the user has called the interface reaches N times within a certain minute, the service provider will reject the user's call request to the interface within the minute.

However, in the above manner, a problem may occur that an important call request for calling an interface later is rejected because a lot of unimportant call requests call the interface first.

Disclosure of Invention

Embodiments of the present application provide a method, an apparatus, a device, and a system for controlling traffic of a service providing system, so as to solve the problem in the prior art that an important call request for calling an interface later is rejected because a plurality of unimportant call requests call the interface first.

In a first aspect, an embodiment of the present application provides a flow control method for a service providing system, where the system includes a terminal and a server, and the method is executed by the server and includes:

receiving a calling request aiming at a target interface sent by the terminal, wherein the calling request is sent to the server by the terminal in response to the input operation of a user under the condition that the user logs in by using a login account, and the parameter of the calling request comprises a first label which is used for representing the importance degree of the calling request;

acquiring a frequency threshold corresponding to the first label under a flow control account corresponding to the login account, and the number of times that the flow control account has been used for the target interface based on the first label in the current unit time;

and if the called times do not reach the threshold value of times, executing the processing corresponding to the calling request, and returning the corresponding processing result to the terminal.

In a second aspect, an embodiment of the present application provides a flow control method for a service providing system, where the system includes a terminal and a server, and the method is executed by the terminal and includes:

acquiring input operation of a user under the condition that the user logs in by using a login account;

and sending a call request aiming at a target interface to the server in response to the input operation, wherein the parameters of the call request comprise a first label, and the first label is used for representing the importance degree of the call request.

In a third aspect, an embodiment of the present application provides a method for controlling a flow in a service providing system, including:

the method comprises the steps that a terminal obtains input operation of a user under the condition that the user logs in by using a login account;

and the terminal responds to the input operation and sends a calling request aiming at a target interface to the server, wherein the parameter of the calling request comprises a first label, and the first label is used for representing the importance degree of the calling request.

The server acquires a frequency threshold corresponding to the first label under a flow control account corresponding to the login account, and the number of times that the flow control account has been used for the target interface based on the first label in the current unit time;

and if the called times do not reach the threshold value of times, the server executes processing corresponding to the calling request and returns a corresponding processing result to the terminal.

In a fourth aspect, an embodiment of the present application provides a flow control device for a service providing system, including:

the terminal comprises a receiving module, a sending module and a processing module, wherein the receiving module is used for receiving a calling request aiming at a target interface sent by the terminal, the calling request is sent to the server in response to the input operation of a user under the condition that the user logs in by using a login account, the parameter of the calling request comprises a first label, and the first label is used for representing the importance degree of the calling request;

the acquisition module is used for acquiring a frequency threshold corresponding to the first label under a flow control account corresponding to the login account, and the number of times that the flow control account has been used for the target interface based on the first label in the current unit time;

and the execution module is used for executing the processing corresponding to the calling request and returning the corresponding processing result to the terminal if the called times do not reach the time threshold value.

In a fifth aspect, an embodiment of the present application provides a flow control device for a service providing system, including:

the acquisition module is used for acquiring the input operation of a user under the condition that the user logs in by using a login account;

and the sending module is used for responding to the input operation and sending a calling request aiming at a target interface to the server, wherein the parameter of the calling request comprises a first label, and the first label is used for representing the importance degree of the calling request.

In a sixth aspect, an embodiment of the present application provides a server, including: a memory, a processor; wherein the memory is to store one or more computer instructions, wherein the one or more computer instructions, when executed by the processor, implement the method of any of the first aspects.

In a seventh aspect, an embodiment of the present application provides a terminal, including: a memory, a processor; wherein the memory is configured to store one or more computer instructions, wherein the one or more computer instructions, when executed by the processor, implement the method of any of the second aspects.

In an eighth aspect, an embodiment of the present application provides a service providing system, including a server and a terminal, where the server is configured to execute the method in any one of the first aspects, and the terminal is configured to execute the method in any one of the second aspects.

In a ninth aspect, embodiments of the present application provide a computer-readable storage medium, on which a computer program is stored, which, when executed, implements the method according to any one of the first aspect.

In a tenth aspect, embodiments of the present application provide a computer-readable storage medium, on which a computer program is stored, which, when executed, implements the method according to any one of the second aspects.

Embodiments of the present application also provide a computer program, which is used to implement the method according to any one of the first aspect when the computer program is executed by a computer.

Embodiments of the present application also provide a computer program, which is used to implement the method according to any one of the second aspect when the computer program is executed by a computer.

In the embodiment of the application, a terminal can respond to an input operation of a user when the user logs in by using a login account, and sends a call request aiming at a target interface and having parameters including a first label for representing importance degree to a server, the server can obtain a frequency threshold corresponding to the first label under a flow control account corresponding to the login account, and the number of times of calls of the flow control account to the interface based on the first label in the current unit time, if the number of times of calls does not reach the frequency threshold, corresponding processing to the call request is executed, and corresponding processing results are returned to the terminal, so that flow control of call requests with different importance degrees to the same flow control account can be independently performed, and more unimportant call requests to an interface first do not occupy call opportunities belonging to important call requests, therefore, the problem that the important calling request for calling the interface later is rejected because more unimportant calling requests call a certain interface first can be avoided, and the use experience of a user is improved.

Drawings

In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly described below, and it is obvious that the drawings in the following description are some embodiments of the present application, and other drawings can be obtained by those skilled in the art without creative efforts.

Fig. 1 is a schematic structural diagram of a service providing system according to an embodiment of the present application;

fig. 2 is a flowchart illustrating a flow control method of a service providing system according to an embodiment of the present application;

fig. 3 is a schematic diagram illustrating flow control performed on a same flow control object based on different labels for a call request of a same interface according to an embodiment of the present application;

fig. 4 is a flow control method of a service providing system according to another embodiment of the present application;

fig. 5 is a flow control method of a service providing system according to another embodiment of the present application;

fig. 6 is a schematic structural diagram of a flow control device of a service providing system according to an embodiment of the present application;

fig. 7 is a schematic structural diagram of a server according to an embodiment of the present application;

fig. 8 is a schematic structural diagram of a flow control device of a service providing system according to another embodiment of the present application;

fig. 9 is a schematic structural diagram of a terminal according to an embodiment of the present application.

Detailed Description

In order to make the objects, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are some embodiments of the present application, but not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.

The terminology used in the embodiments of the present application is for the purpose of describing particular embodiments only and is not intended to be limiting of the application. As used in the examples of this application and the appended claims, the singular forms "a", "an", and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise, and "a" and "an" typically include at least two, but do not exclude the presence of at least one.

It should be understood that the term "and/or" as used herein is merely one type of association that describes an associated object, meaning that three relationships may exist, e.g., a and/or B may mean: a exists alone, A and B exist simultaneously, and B exists alone. In addition, the character "/" herein generally indicates that the former and latter related objects are in an "or" relationship.

The words "if", as used herein, may be interpreted as "at … …" or "when … …" or "in response to a determination" or "in response to a detection", depending on the context. Similarly, the phrases "if determined" or "if detected (a stated condition or event)" may be interpreted as "when determined" or "in response to a determination" or "when detected (a stated condition or event)" or "in response to a detection (a stated condition or event)", depending on the context.

It is also noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a good or system that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such good or system. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of additional like elements in the article of commerce or system in which the element is comprised.

In addition, the sequence of steps in each method embodiment described below is only an example and is not strictly limited.

Fig. 1 is a schematic structural diagram of a service providing system provided in an embodiment of the present application, and as shown in fig. 1, the service providing system may include a server 11 of a service provider for providing a service and a terminal 12 of a user for using the service provided by the service provider.

The server 11 may provide services to the outside in an interface form, one interface may be used to provide one service to the outside, the same interface may be used to provide services to different users, and a user may also be referred to as a user, and one user may correspond to one login account. The server 11 may include any form of data processing server, such as a cloud server, a distributed server, and the like. The functions provided by the server 11 may include, for example, a query function, a storage function, a computation function, and the like.

The terminal 12 may send a call request for the target interface to the server 12 in response to an operation by the user, and the terminal 12 may be, for example, a mobile phone, a tablet, a personal computer, a wearable device, or the like. The server 11 may also perform processing corresponding to the call request, and return a corresponding processing result to the terminal 12, so as to provide the service corresponding to the interface to the terminal 12.

In general, the server 11 may limit a user to call a certain interface at most N times per minute, and after the number of times the user has called the interface reaches N times in a certain minute, the server 11 may reject the user's call request for the interface in the minute. However, in actual applications, the importance of call requests for the same interface may be different at different times, so that a problem may occur in that, since many unimportant call requests call a certain interface first, an important call request calling the interface later is rejected.

In order to solve the technical problem that an important call request for calling an interface later is rejected as a plurality of unimportant call requests call a certain interface first in the prior art, in the embodiment of the application, a terminal can respond to the input operation of a user under the condition that the user logs in by using a login account, send a call request which aims at a target interface and has parameters including a first label for representing the importance degree to a server, the server can obtain a frequency threshold value corresponding to the first label under a flow control account corresponding to the login account and the number of times of calls to the interface based on the first label in the current unit time with the flow control account, if the number of times of calls does not reach the frequency threshold value, execute processing corresponding to the call request, and return corresponding processing results to the terminal, so that the flow control of the call requests with different importance degrees of the same flow control account can be performed independently, because more unimportant call requests are called to a certain interface first and the call opportunity which belongs to an important call request cannot be occupied, the problem that the important call request which calls the interface later is rejected because more unimportant call requests call a certain interface first can be avoided, and the use experience of a user is improved.

Some embodiments of the present application will be described in detail below with reference to the accompanying drawings. The embodiments described below and the features of the embodiments can be combined with each other without conflict.

Fig. 2 is a flowchart illustrating a flow control method of a service providing system according to an embodiment of the present application. As shown in fig. 2, the method of this embodiment may include:

step 21, the terminal acquires the input operation of the user under the condition that the user logs in by using a login account;

and step 22, the terminal responds to the input operation and sends a calling request aiming at a target interface to the server, wherein parameters of the calling request comprise a first label, and the first label is used for representing the importance degree of the calling request.

Step 23, the server obtains a frequency threshold corresponding to the first label under a flow control account corresponding to the login account, and the number of times that the flow control account has been called to the target interface based on the first label in the current unit time;

and 24, if the called times do not reach the threshold value of times, executing the processing corresponding to the calling request, and returning the corresponding processing result to the terminal.

For example, the login account used by the user to login may be a separate login account or may be a sub-account subordinate to the primary account. The independent login account may refer to a login account that does not have an affiliation with another login account. In practical applications, the number of sub-accounts subordinate to the same primary account may be multiple, and the multiple sub-accounts may be created from the same primary account, for example, a company unit may correspond to the same primary account, multiple departments under the company unit may have their own sub-accounts respectively, and the sub-accounts of the multiple departments respectively belong to the sub-account of the same primary account.

In the embodiment of the application, the login account used for the user login has the corresponding flow control account, and one login account used for the user login can correspond to one flow control account. The flow control account is a login account which needs to call flow control in login accounts which need to call interfaces. For example, when the login account used for the user login can be an independent login account, the corresponding flow control account can be the login account used for the user login; when the login account used for user login is a sub-account subordinate to the primary account, the corresponding flow control account may be a primary account subordinate to the login account used for user login.

The terminal can acquire the input operation of the user under the condition that the user logs in by using the login account. The input operation of the user may be any operation that can trigger the terminal to send a call request to the server, such as a viewing operation and a settlement operation.

In response to an input operation by the user, the terminal may transmit a call request for the target interface to the server. It should be noted that the number of the call requests sent by the same input operation trigger terminal to the server may be one or more, when the number of the call requests triggered by the input operation is multiple, each call request in the multiple call requests may be used to request to call one interface, and the importance degrees of the multiple call requests may be the same or different.

In this embodiment of the application, the parameter of the invocation request sent by the terminal to the server includes a Tag (denoted as a first Tag) used for characterizing the importance degree of the invocation request, where the first Tag included in one invocation request may be one of multiple tags corresponding to the flow control account corresponding to the login account used by the user for login, and different tags in the multiple tags may be used for representing different importance degrees, and the multiple tags may be, for example, Tag1, Tag2, Tag3, … …, and Tagn. Of course, the parameter of the invocation request may include other parameter values besides the first tag, which is not limited in this application.

In one embodiment, the sum of the number thresholds corresponding to the plurality of tags and the target interface may be less than or equal to a total number threshold for allowing the flow control account to call the target interface in a unit time. Therefore, the flow control of the total times of calling the interface by the flow control account can be realized. For example, assuming that under a certain flow control account, the time threshold corresponding to Tag1 is Frqua1, the time threshold corresponding to Tag2 is Frqua2 and … …, and the time threshold corresponding to Tagn is Frquan, the sum may not exceed the total time threshold Frqu allowing the flow control account to call the interface per unit time, that is, Frqua1+ Frqua2+ … … + Frquan ≦ Frqu.

Assuming that the significance of Tag1 to Tagn is Tag1 < Tag2 < … … < Tagn, and that the call request labeled Tag1 comes first and the call requests labeled Tag2 and Tagn come later in the current unit time, as shown in fig. 3, the server will reject the call request labeled Tag1 to the target interface in the unit time after the number of times the call request labeled Tag1 has been made to the target interface reaches the threshold number of times corresponding to Tag1 (i.e., Frqua1) in the current unit time, although more call requests labeled Tag1 are received first in the current time window. For the call request labeled Tag2 received after the current unit time, since the number of times that the call request labeled Tag2 has been invoked on the target interface has not yet reached the threshold number of times corresponding to Tag2 (i.e., Frqua2) in the current unit time, the server may further perform processing corresponding to the call request labeled Tag2 and return a corresponding processing result to the terminal. Similarly, for the call request labeled with Tagn received after the current unit time, since the number of times that the call request labeled with Tagn has been called by the target interface in the current unit time has not yet reached the threshold number of times corresponding to Tagn (i.e., Frquan), the server may also perform corresponding processing for the call request labeled with Tagn and return a corresponding processing result to the terminal. It can be seen that, with the adoption of the mode provided by the embodiment of the application, since a plurality of unimportant call requests are firstly called to a certain interface, the call opportunity which belongs to an important call request cannot be occupied, and therefore the problem that the important call request which is called later to the interface is rejected because a plurality of unimportant call requests are firstly called to the certain interface can be avoided.

It should be noted that, for different flow control accounts, the corresponding labels may be partially the same, may be completely the same, or may be completely different.

The terminal may determine the importance of the invocation request based on information associated with the invocation request. Optionally, the importance of the invocation request may be related to the login account used by the user to login. Based on this, in one embodiment, the login account used for the user to login is a certain sub-account subordinate to the primary account, the number of the sub-accounts subordinate to the primary account is multiple, and each sub-account in the multiple sub-accounts corresponds to one tag; the method provided by the embodiment may further include: and taking a label corresponding to a login account used for login of a user as a first label. The flow control object is a flow control object corresponding to a login account used for login of a user.

Or, optionally, the importance of the invocation request may be related to the data processing flow that triggered the sending of the invocation request. Based on this, in one embodiment, the call request is sent in a certain data processing flow of a plurality of data processing flows, and each data processing flow of the plurality of data processing flows corresponds to one tag; the method provided by the embodiment may further include: and taking a label corresponding to the data processing flow triggering the sending of the call request as a first label. The flow control object is a flow control object corresponding to a login account used for login of a user.

After receiving a call request sent by a terminal, a server can obtain a frequency threshold corresponding to a first label under a flow control account corresponding to a login account, and the number of times that the flow control account has been called to a target interface based on the first label in the current unit time. It should be noted that the time unit for the server to perform flow control may be flexibly implemented according to needs, and for example, the time unit may be a minute, in which case, the current unit time may be a current minute.

The time threshold corresponding to the first label under the flow control account is a time threshold allowing the flow control account to call the target interface based on the first label in unit time, where the time length of the unit time is equal to the time length of the current unit time, and is 1 minute, for example.

In the embodiment of the application, the number of times of the calls is counted by distinguishing the flow control account and the label, and the number of times of the calls counted by the same flow control account can be multiple. The flow control account may count the number of times that the flow control account has been invoked for different interfaces based on different labels, for example, as shown in table 1 below.

TABLE 1

Label (R)	Interface	Number of times of use
			Tag1	Interface x	N11 times
Tag2	Interface x	N21 times
			……	Interface x	……
Tagn	Interface x	Nn1 times
			Tag1	Interface y	N12 times
Tag2	Interface y	N22 times
			……	Interface y	……
Tagn	Interface y	Nn2 times
			……	……	……

For example, the number of times that the flow control account has been called for interface y based on Tag1 can be obtained by looking up table 1, which is N12 times. It should be noted that, in table 1, different flow control accounts correspond to different tables for storing the number of times of calls as an example, it can be understood that, in other embodiments, different flow control accounts may also correspond to the same table, and in this case, fields related to the flow control accounts may be added in table 1.

In the sum of the fetch number threshold and the number of times invoked, the server may determine whether the number of times invoked reaches the number threshold, for example. Alternatively, for example, the server may determine whether the number of times of the call is less than a number threshold, and if the number of times of the call is less than the number threshold, it may indicate that the number of times of the call has not reached the number threshold.

For example, the threshold of the number of times corresponding to the first label under the flow control account may be determined by the server by querying the correspondence. Based on this, in an embodiment, the obtaining a threshold of the number of times corresponding to the first label under the flow control account corresponding to the login account may include: and determining a frequency threshold corresponding to the first label under the flow control account based on the corresponding relation between the plurality of labels and the frequency threshold under the flow control account. The correspondence between multiple labels and the time threshold under the flow control account may be, for example, as shown in table 2 below.

TABLE 2

Label (R)	Number of times threshold
		Tag1	C11 times
Tag2	C21 times
		……	……
Tagn	Cn1 times

Assuming that the first label is Tag1, the threshold of the number of times corresponding to the first label under the flow control account can be determined to be C11 times according to table 1. It should be noted that, the correspondence between the labels and the time threshold values for different interfaces under the same flow control account may be the same or different, and when the correspondence is different, the time threshold value corresponding to the first label may specifically be the time threshold value corresponding to the first label + the target interface.

Optionally, the correspondence between the multiple labels and the time threshold under the flow control account may be configured by the user, so as to facilitate improvement of flexibility. Based on this, in an embodiment, the method provided in this embodiment may further include: the terminal acquires flow control configuration information input by a user and sends the flow control configuration information to the server, and the server can obtain the corresponding relation between a plurality of labels and a frequency threshold value under a flow control account according to the flow control configuration information sent by the receiving terminal and the flow control configuration information. For example, the flow control configuration information may indicate a number threshold corresponding to each of the plurality of tags, or, for example, the flow control configuration information may indicate a percentage corresponding to each of the plurality of tags, and a product of a percentage total number threshold corresponding to a certain tag is the number threshold corresponding to the certain tag.

If the number of times of use does not reach the threshold value of times of use, it can be shown that the number of times of use of the flow control account for the target interface based on the first label in the current unit time does not reach the upper limit value yet, and therefore the flow control account can be allowed to call the target interface based on the first label continuously in the current time window. Thus, the server can execute processing corresponding to the call request and return a corresponding processing result to the terminal. It should be noted that, as for the implementation manner of the server executing the processing corresponding to the call request, reference may be made to the detailed description in the related art, and details are not described here again.

If the called times reach the time threshold, the number of times that the control account number has been called to the target interface based on the first label in the current unit time may be represented as having not reached the upper limit. Optionally, when the number of times that the flow control account has been used for the target interface based on the first tag in the current unit time has not reached the upper limit value, the server may further reject the flow control account to call the target interface based on the first tag in the current time window, and for example, the server may not perform processing corresponding to the call request and return an error code to the terminal.

Or optionally, when the number of times of the control account in the current unit time that the target interface has been called based on the first label has not reached the upper limit value, the call opportunity corresponding to the label with the lower importance degree may be occupied. Based on this, in one embodiment, the method provided in the embodiment of the present application may further include: if the called times reach a time threshold, determining whether a second label exists in a plurality of labels corresponding to the flow control account, wherein the importance degree of the second label representation is lower than that of the first label representation, and the called times of the flow control account calling a target interface based on the second label in the current unit time do not reach the time threshold corresponding to the second label and the target interface under the flow control account; if the current time interval exists, the corresponding processing of the calling request can be executed, the corresponding processing result is returned to the terminal, and the number of times of calling the target interface by the current flow control account number in the unit time based on the second label is updated. Further, if the current flow control account does not exist, the flow control account can be rejected from calling the target interface based on the first label.

Fig. 4 is a flow control method of a service providing system according to another embodiment of the present application, where the method provided in this embodiment may be executed by the server 11 in fig. 1, and as shown in fig. 4, the method provided in this embodiment may include:

step 41, receiving a call request for a target interface sent by the terminal, where the call request is sent to the server in response to an input operation of a user when the user logs in using a login account, and a parameter of the call request includes a first tag, and the first tag is used for representing an importance degree of the call request;

step 42, acquiring a frequency threshold corresponding to the first label under a flow control account corresponding to the login account, and the number of times that the flow control account has been used for the target interface based on the first label in the current unit time;

and 43, if the called times do not reach the threshold value of times, executing the processing corresponding to the calling request, and returning the corresponding processing result to the terminal.

In one embodiment, the flow control account has a plurality of labels, and the sum of the number of times threshold corresponding to the plurality of labels and the target interface is less than or equal to the total number of times threshold allowing the flow control account to call the target interface in unit time.

In one embodiment, the method provided in this embodiment further includes:

if the called times reach the time threshold, determining whether a second label exists in a plurality of labels corresponding to the flow control account, wherein the importance degree of the second label representation is lower than that of the first label representation, and the called times of the flow control account calling the target interface based on the second label in the current unit time do not reach the time threshold corresponding to the second label and the target interface under the flow control account;

and if the current flow control account number exists in the unit time, executing processing corresponding to the calling request, returning a corresponding processing result to the terminal, and updating the called times of the flow control account number on the target interface based on the second label in the current unit time.

In an embodiment, the obtaining a threshold of times corresponding to the first label under the flow control account corresponding to the login account includes: and determining a frequency threshold corresponding to the first label under the flow control account based on the corresponding relation between the plurality of labels and the frequency threshold under the flow control account.

In one embodiment, the method provided in this embodiment further includes: and receiving flow control configuration information sent by the terminal, and acquiring the corresponding relation according to the flow control configuration information.

It should be noted that, for a specific implementation of the server, reference may be made to the specific description in the embodiment shown in fig. 2, and details are not described here again.

In the flow control method provided by this embodiment, a call request for a target interface sent by a terminal is received, where the call request is sent to a server by the terminal in response to an input operation of a user when the user logs in using a login account, a parameter of the call request includes a first tag, a frequency threshold corresponding to the first tag under a flow control account corresponding to the login account is obtained, and a number of times that the flow control account has been called to the target interface based on the first tag in a current unit time is obtained, if the number of times that has been called does not reach the frequency threshold, processing corresponding to the call request is executed, and a corresponding processing result is returned to the terminal, so that flow control of call requests of different importance degrees for the same flow control account can be performed independently, and since more unimportant call requests are called to a certain interface first, a call opportunity that should belong to an important call request is not occupied, therefore, the problem that the important calling request for calling the interface later is rejected because more unimportant calling requests call a certain interface first can be avoided, and the use experience of a user is improved.

Fig. 5 is a flow control method of a service providing system according to another embodiment of the present application, where the method provided in this embodiment may be executed by the terminal 12 in fig. 1, as shown in fig. 5, the method provided in this embodiment may include:

step 51, acquiring an input operation of a user under the condition that the user logs in by using a login account;

and step 52, responding to the input operation, sending a call request aiming at a target interface to the server, wherein parameters of the call request comprise a first label, and the first label is used for representing the importance degree of the call request.

In one embodiment, the login account is a sub-account subordinate to a primary account, the number of the sub-accounts subordinate to the primary account is multiple, and each sub-account in the multiple sub-accounts corresponds to one tag;

the method provided by the embodiment further comprises the following steps: and taking a label corresponding to a login account used for the user login as the first label.

In one embodiment, the call request is sent in a certain data processing flow of a plurality of data processing flows, and each data processing flow of the plurality of data processing flows corresponds to a tag;

the method provided by the embodiment further comprises the following steps: and taking a label corresponding to the data processing flow triggering the sending of the calling request as the first label.

In one embodiment, the method provided in this embodiment further includes: and acquiring the flow control configuration information input by the user, and sending the flow control configuration information to the server.

It should be noted that, for a specific implementation of the terminal, reference may be made to the specific description in the embodiment shown in fig. 2, and details are not described here again.

According to the flow control method provided by the embodiment, the input operation of the user is acquired under the condition that the user logs in by using the login account, the call request aiming at the target interface is sent to the server in response to the input operation, and the parameter of the call request comprises the first label, so that the flow control of the call requests of different importance degrees of the same flow control account by the server can be independently carried out.

Fig. 6 is a schematic structural diagram of a flow control device of a service providing system according to an embodiment of the present application; referring to fig. 6, the present embodiment provides an apparatus, which may perform the method provided in the embodiment shown in fig. 4, and specifically, the apparatus may include:

a receiving module 61, configured to receive a call request for a target interface sent by the terminal, where the call request is sent to the server by the terminal in response to an input operation of a user when the user logs in using a login account, and a parameter of the call request includes a first tag, and the first tag is used to represent an importance degree of the call request;

an obtaining module 62, configured to obtain a time threshold corresponding to the first label under a flow control account corresponding to the login account, and a number of times that the flow control account has been called to the target interface based on the first label in a current unit time;

and the execution module 63 is configured to execute processing corresponding to the call request and return a corresponding processing result to the terminal if the called number of times does not reach the number threshold.

In one embodiment, the execution module 63 is further configured to:

In an embodiment, the obtaining module 62 is configured to obtain a threshold of times corresponding to the first label under the flow control account corresponding to the login account, where the threshold of times is obtained by: and determining a frequency threshold corresponding to the first label under the flow control account based on the corresponding relation between the plurality of labels and the frequency threshold under the flow control account.

In an embodiment, the receiving module 61 is further configured to receive flow control configuration information sent by the terminal; the device also comprises a configuration module used for obtaining the corresponding relation according to the flow control configuration information.

The apparatus shown in fig. 6 can execute the method provided by the embodiment shown in fig. 4, and reference may be made to the related description of the embodiment shown in fig. 4 for a part not described in detail in this embodiment. The implementation process and technical effect of the technical solution refer to the description in the embodiment shown in fig. 4, and are not described herein again.

In one possible implementation, the structure of the apparatus shown in fig. 6 may be implemented as a server. As shown in fig. 7, the server may include: a processor 71 and a memory 72. Wherein the memory 72 is used for storing the program that supports the server to execute the method provided by the embodiment shown in fig. 4, and the processor 71 is configured to execute the program stored in the memory 72.

The program comprises one or more computer instructions which, when executed by the processor 71, are capable of performing the steps of:

Optionally, the processor 71 is further configured to perform all or part of the steps in the embodiment shown in fig. 4.

The server may further include a communication interface 73 for the server to communicate with other devices or a communication network.

Fig. 8 is a schematic structural diagram of a flow control device of a service providing system according to another embodiment of the present application; referring to fig. 8, the present embodiment provides an apparatus, which may perform the method provided in the embodiment shown in fig. 5, and specifically, the apparatus may include:

an obtaining module 81, configured to obtain an input operation of a user when the user logs in using a login account;

a sending module 82, configured to send, to the server, a call request for a target interface in response to the input operation, where a parameter of the call request includes a first tag, and the first tag is used to characterize an importance degree of the call request.

the sending module 82 is further configured to use a tag corresponding to the login account used for the user login as the first tag.

the sending module 82 is further configured to use a label corresponding to the data processing flow that triggers sending of the invocation request as the first label.

In an embodiment, the obtaining module 81 is further configured to obtain the flow control configuration information input by the user, and the sending module 82 is further configured to send the flow control configuration information to the server.

The apparatus shown in fig. 8 can execute the method provided by the embodiment shown in fig. 5, and reference may be made to the related description of the embodiment shown in fig. 5 for a part not described in detail in this embodiment. The implementation process and technical effect of the technical solution are described in the embodiment shown in fig. 5, and are not described herein again.

In one possible implementation, the structure of the apparatus shown in fig. 8 may be implemented as a terminal. As shown in fig. 9, the middle terminal may include: a processor 91 and a memory 92. Wherein the memory 92 is used for storing the program that supports the terminal to execute the method provided by the embodiment shown in fig. 5, and the processor 91 is configured to execute the program stored in the memory 92.

The program comprises one or more computer instructions which, when executed by the processor 91, are capable of performing the steps of:

Optionally, the processor 91 is further configured to perform all or part of the steps in the foregoing embodiment shown in fig. 5.

The terminal may further include a communication interface 93 for the terminal to communicate with other devices or a communication network.

In addition, the embodiment of the present application provides a computer readable storage medium, on which a computer program is stored, and when the computer program is executed, the method provided by the embodiment shown in fig. 4 is implemented.

The embodiment of the application provides a computer readable storage medium, on which a computer program is stored, and when the computer program is executed, the method provided by the embodiment shown in fig. 5 is implemented.

The above-described embodiments of the apparatus are merely illustrative, and the units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of this embodiment. One of ordinary skill in the art can understand and implement such a technique without inventive effort.

Through the above description of the embodiments, those skilled in the art will clearly understand that each embodiment can be implemented by adding a necessary general hardware platform, and of course, can also be implemented by a combination of hardware and software. With this understanding in mind, the above-described technical solutions and/or portions thereof that contribute to the prior art may be embodied in the form of a computer program product, which may be embodied on one or more computer-usable storage media having computer-usable program code embodied therein (including but not limited to disk storage, CD-ROM, optical storage, etc.).

The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the application. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be loaded onto a computer or other programmable apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

In a typical configuration, a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.

The memory may include forms of volatile memory in a computer readable medium, Random Access Memory (RAM) and/or non-volatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of a computer-readable medium.

Computer-readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, linked lists, modules of a program, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), Read Only Memory (ROM), Electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), Digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information that can be accessed by a computing device. As defined herein, a computer readable medium does not include a transitory computer readable medium such as a modulated data signal and a carrier wave.

Finally, it should be noted that: the above embodiments are only used for illustrating the technical solutions of the present application, and not for limiting the same; although the present application has been described in detail with reference to the foregoing embodiments, it should be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some or all of the technical features may be equivalently replaced; and the modifications or the substitutions do not make the essence of the corresponding technical solutions depart from the scope of the technical solutions of the embodiments of the present application.

Claims

1. A flow control method of a service providing system, the system including a terminal and a server, the method being performed by the server, the method comprising:

2. The method according to claim 1, wherein the flow control account has a plurality of labels, and a sum of a number threshold corresponding to the plurality of labels and the target interface is less than or equal to a total number threshold allowing the flow control account to call the target interface in a unit time.

3. The method according to claim 1 or 2, characterized in that the method further comprises:

4. The method according to any one of claims 1 to 3, wherein the obtaining a threshold number of times corresponding to the first label under the flow control account corresponding to the login account comprises: and determining a frequency threshold corresponding to the first label under the flow control account based on the corresponding relation between the plurality of labels and the frequency threshold under the flow control account.

5. The method of claim 4, further comprising:

and receiving flow control configuration information sent by the terminal, and acquiring the corresponding relation according to the flow control configuration information.

6. A flow control method of a service providing system, the system including a terminal and a server, the method being performed by the terminal, the method comprising:

7. The method according to claim 6, wherein the login account is a sub-account subordinate to a primary account, the number of sub-accounts subordinate to the primary account is multiple, and each sub-account in the multiple sub-accounts corresponds to a tag;

the method further comprises the following steps: and taking a label corresponding to a login account used for the user login as the first label.

8. The method of claim 6, wherein the invocation request is sent in a data processing flow of a plurality of data processing flows, each data processing flow of the plurality of data processing flows corresponding to a tag;

the method further comprises the following steps: and taking a label corresponding to the data processing flow triggering the sending of the calling request as the first label.

9. The method according to any one of claims 6-8, further comprising: and acquiring the flow control configuration information input by the user, and sending the flow control configuration information to the server.

10. A flow control method of a service providing system, comprising:

the terminal responds to the input operation and sends a calling request aiming at a target interface to a server, wherein parameters of the calling request comprise a first label, and the first label is used for representing the importance degree of the calling request;

11. A server, comprising: a memory, a processor; wherein the memory is to store one or more computer instructions, wherein the one or more computer instructions, when executed by the processor, implement the method of any of claims 1 to 5.

12. A terminal, comprising: a memory, a processor; wherein the memory is to store one or more computer instructions, wherein the one or more computer instructions, when executed by the processor, implement the method of any of claims 6 to 9.

13. A service providing system comprising a server and a terminal, wherein the server is configured to perform the method of any one of claims 1 to 5, and the terminal is configured to perform the method of any one of claims 6 to 9.

14. A computer-readable storage medium, having stored thereon a computer program which, when executed, implements the method of any one of claims 1 to 9.