CN110784351A - Data access control method and device, electronic equipment and storage medium - Google Patents
Data access control method and device, electronic equipment and storage medium Download PDFInfo
- Publication number
- CN110784351A CN110784351A CN201911027886.8A CN201911027886A CN110784351A CN 110784351 A CN110784351 A CN 110784351A CN 201911027886 A CN201911027886 A CN 201911027886A CN 110784351 A CN110784351 A CN 110784351A
- Authority
- CN
- China
- Prior art keywords
- access
- upper limit
- data access
- data
- configuration policy
- 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
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0893—Assignment of logical groups to network elements
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/10—Flow control; Congestion control
- H04L47/20—Traffic policing
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/10—Network architectures or network communication protocols for network security for controlling access to devices or network resources
- H04L63/108—Network architectures or network communication protocols for network security for controlling access to devices or network resources when the policy decisions are valid for a limited amount of time
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/20—Network architectures or network communication protocols for network security for managing network security; network security policies in general
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/56—Provisioning of proxy services
- H04L67/561—Adding application-functional data or data for application control, e.g. adding metadata
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Security & Cryptography (AREA)
- Computer Hardware Design (AREA)
- Computing Systems (AREA)
- General Engineering & Computer Science (AREA)
- Information Transfer Between Computers (AREA)
Abstract
The application provides a data access control method and device, electronic equipment and a storage medium. The scheme comprises the following steps: sending service metadata to a server; receiving a configuration strategy issued by a server according to the service metadata; and according to the access upper limit indicated by the configuration policy, stopping triggering the data access function when the number of data access times reaches the upper limit. Therefore, the problem that the application system is hung when the data access amount is suddenly increased is solved.
Description
Technical Field
The present application relates to the field of internet technologies, and in particular, to a method and an apparatus for controlling data access, an electronic device, and a storage medium.
Background
With the advent of the internet era, enterprise applications often need to handle traffic peak problems, such as encountering a hot spot event, planning an activity, or pushing a page, the sudden increase in access brings about a sudden increase in read-write traffic, and each corresponding module faces an experience.
In the prior art, a system node is down easily due to service traffic caused by a hot event, and due to the cooperation of multiple applications, one application is slow in response or down, so that other applications are affected. For example, the second application may call an interface of the first application, so that the first application is hung up, and the operation of the second application is affected, so that a system node goes down, and many application nodes are triggered to go down, so that an avalanche is caused to make the whole system unavailable.
Disclosure of Invention
The embodiment of the application provides a data access control method, which is used for solving the problem that a machine is down when the data access amount is suddenly increased.
The application provides a control method of data access, which is applied to a client and comprises the following steps: sending service metadata to a server; receiving a configuration strategy issued by a server according to the service metadata; and according to the access upper limit indicated by the configuration policy, stopping triggering the data access function when the number of data access times reaches the upper limit.
In one embodiment, the configuration policy includes an upper access limit for a preset time period for each application; according to the access upper limit indicated by the configuration policy, when the number of data access reaches the upper limit, stopping triggering the data access function, comprising: receiving a data access request of a specified application; judging whether the access times of the specified application in the preset time period reach the access upper limit or not according to the access upper limit of the specified application in the preset time period; and if the access times of the specified application in the preset time period reach the access upper limit, stopping triggering the data access function.
In one embodiment, the configuration policy includes an access upper limit for each access type within a preset time period; according to the access upper limit indicated by the configuration policy, when the number of data access reaches the upper limit, stopping triggering the data access function, comprising: receiving a data access request; obtaining an access upper limit corresponding to the access type from the configuration strategy according to the access type indicated by the data access request; and judging whether the access times of the access types in a preset time period reach the access upper limit corresponding to the access types, and if so, stopping triggering the access functions corresponding to the access types.
In one embodiment, when the upper access limit is reached, the method further comprises: and returning prompt information to the initiator of the data access request.
In an embodiment, the method further comprises: and uploading the stop trigger record of the data access request to the server.
The application also provides a data access control method, which is applied to a server and comprises the following steps: receiving service metadata uploaded by a client; returning a configuration strategy to the client according to the service metadata; the configuration policy is used for enabling the client to stop triggering the data access function when the number of data access times reaches the upper limit according to the access upper limit indicated by the configuration policy.
In one embodiment, the service metadata includes a plurality of applications and a plurality of access types; returning a configuration policy to the client according to the service metadata, comprising: displaying the service metadata on a user interface; and generating a configuration policy according to the configured access upper limit for each application and the configured access upper limit for each access type.
The present application also provides a control device for data access, including: the data sending module is used for sending the service metadata to the server; the processing receiving module is used for receiving a configuration strategy issued by the server according to the service metadata; and the access current limiting module is used for stopping triggering the data access function when the number of data access times reaches the upper limit according to the access upper limit indicated by the configuration policy.
The present application further provides an electronic device, which includes: a processor; a memory for storing processor-executable instructions; the processor is configured to execute the control method for data access provided by the application.
The present application also provides a computer-readable storage medium storing a computer program executable by a processor to perform the control method for data access provided by the present application.
According to the technical scheme provided by the embodiment of the application, the data access function is stopped to be triggered when the data access times reach the upper limit by acquiring the configuration policy from the server and according to the access upper limit indicated by the configuration policy. Therefore, the problem that the system is hung up when the data access volume is suddenly increased is solved, the faults caused by overload of part of system services are effectively avoided, and the service development is stably supported.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings required to be used in the embodiments of the present application will be briefly described below.
Fig. 1 is a schematic application scenario diagram of a control method for data access according to an embodiment of the present application;
fig. 2 is a schematic flowchart of a method for controlling data access according to an embodiment of the present application;
FIG. 3 is a flowchart providing details of step 250 of the corresponding embodiment of FIG. 2, according to an embodiment of the present application;
FIG. 4 is a flowchart illustrating details of step 250 of the corresponding embodiment of FIG. 2 according to another embodiment of the present application;
fig. 5 is a block diagram of a control device for data access according to an embodiment of the present application.
Detailed Description
The technical solutions in the embodiments of the present application will be described below with reference to the drawings in the embodiments of the present application.
Like reference numbers and letters refer to like items in the following figures, and thus, once an item is defined in one figure, it need not be further defined and explained in subsequent figures. Meanwhile, in the description of the present application, the terms "first", "second", and the like are used only for distinguishing the description, and are not to be construed as indicating or implying relative importance.
Fig. 1 is a schematic application scenario diagram of a control method for data access according to an embodiment of the present application. As shown in fig. 1, the application scenario includes a server 110, a first terminal 120, and a second terminal 130. The first terminal 120 and the second terminal 130 may be a server, a Personal Computer (PC), a tablet, a smart phone, a Personal Digital Assistant (PDA), and the like. The first terminal 120 and the second terminal 130 may also be two virtual machines in the same server. The server 110 may be a server, a cluster of servers, or a cloud computing center. The first terminal 120, the second terminal 130 and the service end 110 communicate with each other through a wired or wireless network.
Other applications, such as a payment system, an order system, an inventory system, a user system, etc., are installed in the first terminal 120 and the second terminal 130. For example, the first terminal 120 has a payment system installed therein, and the second terminal 130 has an order system installed therein. When the payment system requests to call the data of the order system, before the data of the order system is called, the client of the second terminal 130 performs current limiting judgment, and if the data access reaches the upper limit, the triggering of the data access function is stopped.
The second terminal 130 may send service metadata to the server 110, and the service metadata may include access types (modified, deleted, added) and may also include various applications (e.g., payment systems) accessing the second terminal 130.
The server 110 may perform display of the service metadata so that the user may perform configuration of the access upper limit. The server 110 may generate a configuration policy according to the access type selected by the user and the access upper limit configured for the access type. The configuration policy is used to indicate an upper access limit for each access type within a preset time period. The server 110 may generate a configuration policy according to the application selected by the user and the access upper limit configured for the application. The configuration policy may also indicate an upper access limit for each application within a preset time period. The server 110 may issue the configuration policy to the client, so that the client may stop triggering the data access function when the access frequency of a certain access type reaches the access upper limit according to the indication of the configuration policy, and stop triggering the data access function when the access frequency of a certain application reaches the access upper limit.
The application provides an electronic device, which can be used as a first terminal 120 or a second terminal 130, and can also be used as a server 110. The electronic device may include: a processor; a memory for storing processor-executable instructions; the processor is configured to execute the control method for data access provided by the application.
The Memory may be implemented by any type of volatile or non-volatile Memory device or combination thereof, such as Static Random Access Memory (SRAM), Electrically Erasable Programmable Read-Only Memory (EEPROM), Erasable Programmable Read-Only Memory (EPROM), Programmable Read-Only Memory (PROM), Read-Only Memory (ROM), magnetic Memory, flash Memory, magnetic disk or optical disk.
The present application provides a computer-readable storage medium storing a computer program executable by a processor to perform the above-described data access control method.
Fig. 2 is a flowchart illustrating a method for controlling data access according to the present application. As shown in fig. 2, the method includes the following steps.
In step 210, the client sends service metadata to the server. The client may be the first terminal 120 or the second terminal 130 in the implementation environment shown in fig. 1.
In step 220, the server receives the service metadata sent by the client.
The service metadata may include an access type, and may further include a plurality of applications accessing the client, wherein different applications may be represented by the application identifier. For example, a represents a payment system, B represents an order system, and C represents an inventory system. Assuming that the client has a payment system installed, and the applications accessing the payment system in the client may have an order system and an inventory system, the service metadata may include an order system identification B and an inventory system identification C. The client side and the server side establish bidirectional connection, and the service metadata are sent to a controller of the server side in a json (JavaScript Object Notation) format. After receiving the service metadata, the controller may store the service metadata in a data storage of the server by using an IP (Internet Protocol Address) or an instance name of the client as a primary key.
In step 230, the server returns the configuration policy to the client according to the service metadata.
In one embodiment, the configuration policy may specify an upper access limit for each application to access the client within a preset time period. The access upper limit refers to the maximum number of accesses. For example, application B is specified to have an upper limit of 15 accesses in 10 minutes. The upper access limit for application C in 10 minutes is 13. The preset time period may be 1 minute, 5 minutes, or longer.
In another embodiment, the configuration policy may specify an upper access limit for each access type for a preset period of time. The access type may be modified, added or deleted data. For example, an upper limit of 5 times is defined for a 1 minute response to a modification request, and if it is 5 times, the triggering of the data modification operation may be stopped. Similarly, the number of times of adding and deleting data in the preset time period can be specified.
In one embodiment, the step 230 includes: and the server displays the service metadata on the user interface. And generating a configuration policy according to the configured access upper limit for each application and the configured access upper limit for each access type.
The controller of the server can control the user interface management unit to display the service metadata, and can acquire the performance parameters of the client according to the IP address and the instance name of the client, so that the user can know the performance of each client and configure the access upper limit based on the performance. At the user interface the user may select a configured application and then enter an access ceiling for the selected application. The user can also select the configured access type in the user interface, and then input the access upper limit of the selected access type, so that the server can generate the configuration policy according to the access upper limit of each application and the access upper limit of each access type configured by the user. The server side can return the generated configuration strategy according to the IP address of the client side.
In step 240, the client receives the configuration policy returned by the server according to the service metadata.
In step 250, the client stops triggering the data access function when the number of data accesses reaches the upper limit according to the access upper limit indicated by the configuration policy.
In one embodiment, the configuration policy includes an upper access limit for a preset period of time for each application. As shown in fig. 3, the above step 250 may include the following steps.
In step 251, a data access request is received specifying an application.
A designated application refers to an application program that accesses a client, such as an order system. The client receives a data access request sent by a specified application. The data access request may include an access type, an application identification of a specified application.
In step 252, it is determined whether the number of access times of the specified application in the preset time period reaches the access upper limit according to the access upper limit of the specified application in the preset time period.
Because the configuration policy defines the access upper limit of each application in the preset time period, the client can obtain the access upper limit of the specified application in the preset time period from the configuration policy according to the application identifier of the specified application. The client may count the number of times of access of a given application in a preset time period, where the number of times of access may be the number of times of initiating an access request or the number of times of successfully accessing data. The client may determine whether the number of accesses of the specified application within the preset time period is greater than or equal to an access upper limit specified by the configuration policy. If so, the upper access limit is deemed to have been reached, and if not, the upper access limit may be deemed to have not been reached.
In step 253, if the number of access times of the specified application in the preset time period reaches the access upper limit, the triggering of the data access function is stopped.
The stopping of triggering the data access function means that data modification, data addition or data deletion operation is not triggered for the data access request any more. If the access times of the specified application in the preset time period do not reach the access upper limit, the action indicated by the data access request executed by the application program of the client can be triggered.
In an embodiment, the configuration policy may further include an access upper limit for each access type within a preset time period. As shown in fig. 4, the above step 250 may include the following steps.
In step 251', a data access request is received. The data access request may be the data access request sent by the specified application in step 251 described above. The data access request may include an access type, an application identification of a specified application.
In step 252', according to the access type indicated by the data access request, an access upper limit corresponding to the access type is obtained from the configuration policy.
Since the configuration policy specifies the upper limit of access for each access type within a preset time period, for example, the number of data modifications in 1 minute may be 5, the number of data deletions in 1 minute may be 3, and the number of data additions in 1 minute may be 4. Therefore, the client can obtain the access upper limit corresponding to the access type from the configuration policy according to the access type indicated by the data access request. Assuming that the access type of the data access request is modified data, the upper limit of the number of times the client obtains the modified data from the configuration policy is 1 minute up to 5 times.
In step 253', it is determined whether the access frequency of the access type in the preset time period reaches the access upper limit corresponding to the access type, and if the access frequency reaches the access upper limit, the triggering of the access function corresponding to the access type is stopped.
In an embodiment, the server may count the number of times of receiving the modification request in the preset time period, as the number of times of accessing the access type of the modification data in the preset time period. Similarly, the access times of other access types in the preset time period can be counted. In another embodiment, the number of times of successfully modifying, deleting or adding the data may be counted as the number of times of access of the corresponding access type within the preset time period.
The client can judge whether the access times of the access type in the preset time period is greater than or equal to the access upper limit corresponding to the access type, if so, the access upper limit is considered to be reached, and the access function corresponding to the access type is not triggered for the access request. For example, if the number of times the data has been modified within 1 minute has been 5 times, the data modification action may no longer be triggered when the data modification request is received. Conversely, if the upper limit is not reached, the same access function may be triggered according to the access type indicated by the data access request.
In an embodiment, the method provided by the present application further includes: and when the access upper limit is reached, returning prompt information to the initiator of the data access request.
The access upper limit is reached when the number of accesses of a certain access type in a preset time period reaches the access upper limit specified by the configuration policy. It may also be that the number of accesses of a certain application in a preset time period reaches the upper limit of accesses specified by the configuration policy. The initiator of the data access request may be a designated application that initiates the data access request, such as a payment system, an order system. The prompt message may prompt the number of accesses to reach an upper limit for later access.
In an embodiment, the method provided by the present application further includes: and the client uploads the stop trigger record of the data access request to the server.
When the access upper limit is reached and the data access function is not triggered for the data access request any more, the client side can send a stop trigger record to the server side. The stop trigger record may include the originator of the data access request, the access type, the access time, etc.
In one embodiment, the client may upload a record of each data access to the server at a certain frequency. The server can store the records and perform statistical analysis according to set rules. The server may include a controller, a user interface management unit, and a memory. The controller can receive the recorded data and store the recorded data in the memory. The user interface management unit responds to the trigger of a user, acquires the recorded data from the memory through the controller, and displays the recorded data on the user interface in a chart form, so that an analyst can adjust the configuration strategy as required after analyzing according to the service condition.
The following is an embodiment of the apparatus of the present application, which may be used to execute an embodiment of a control method for data access executed by the client described above in the present application. For details not disclosed in the embodiments of the apparatus of the present application, please refer to the embodiments of the control method for data access of the present application.
Fig. 5 is a block diagram of a control device for data access according to an embodiment of the present application. As shown in fig. 5, the data access control device may include: a data transmission module 510, a policy receiving module 520, and an access throttling module 530.
A data sending module 510, configured to send service metadata to a server;
a policy receiving module 520, configured to receive a configuration policy issued by the server according to the service metadata;
and the access limiting module 530 is configured to stop triggering the data access function when the number of data accesses reaches an upper limit according to an access upper limit indicated by the configuration policy.
In one embodiment, the configuration policy includes an upper access limit for a preset time period for each application; the access throttling module 530 includes: the device comprises a request receiving unit, an upper limit judging unit and a stop triggering unit.
A request receiving unit for receiving a data access request of a specified application;
the current-limiting judging unit is used for judging whether the access times of the specified application in the preset time period reach the access upper limit or not according to the access upper limit of the specified application in the preset time period;
and if the access times of the specified application in the preset time period reach the access upper limit, stopping triggering the data access function.
In one embodiment, the configuration policy includes an access upper limit for each access type within a preset time period; the access throttling module 530 includes:
a request receiving unit for receiving a data access request;
the upper limit acquisition unit is used for acquiring an access upper limit corresponding to the access type from the configuration strategy according to the access type indicated by the data access request;
and the current limiting judging unit is used for judging whether the access frequency of the access type in a preset time period reaches an access upper limit corresponding to the access type, and if so, stopping triggering the access function corresponding to the access type.
In an embodiment, the apparatus further comprises: and the prompting module is used for returning prompting information to the initiator of the data access request when the access upper limit is reached.
In an embodiment, the apparatus further comprises: and uploading the stop trigger record of the data access request to the server.
The implementation process of the functions and actions of each module in the device is specifically detailed in the implementation process of the corresponding step in the control method for data access, and is not described herein again.
In the embodiments provided in the present application, the disclosed apparatus and method can be implemented in other ways. The apparatus embodiments described above are merely illustrative, and for example, the flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of apparatus, methods and computer program products according to various embodiments of the present application. 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). 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.
In addition, functional modules in the embodiments of the present application may be integrated together to form an independent part, or each module may exist separately, or two or more modules may be integrated to form an independent part.
The functions, if implemented in the form of software functional modules and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application or portions thereof that substantially contribute to the prior art may be embodied in the form of a software product stored in a storage medium and including instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and other various media capable of storing program codes.
Claims (10)
1. A method for controlling data access, which is applied to a client and comprises the following steps:
sending service metadata to a server;
receiving a configuration strategy issued by the server according to the service metadata;
and stopping triggering the data access function when the number of data access times reaches the upper limit according to the access upper limit indicated by the configuration policy.
2. The method of claim 1, wherein the configuration policy comprises an upper access limit for a preset time period for each application; the step of stopping triggering the data access function when the number of data access times reaches the upper limit according to the access upper limit indicated by the configuration policy comprises the following steps:
receiving a data access request of a specified application;
judging whether the access times of the specified application in a preset time period reach the access upper limit or not according to the access upper limit of the specified application in the preset time period;
and if the access times of the specified application in the preset time period reach the access upper limit, stopping triggering the data access function.
3. The method of claim 1, wherein the configuration policy comprises an upper access limit for each access type within a preset time period; the step of stopping triggering the data access function when the number of data access times reaches the upper limit according to the access upper limit indicated by the configuration policy comprises the following steps:
receiving a data access request;
obtaining an access upper limit corresponding to the access type from the configuration policy according to the access type indicated by the data access request;
and judging whether the access times of the access type in a preset time period reach an access upper limit corresponding to the access type, and if so, stopping triggering the access function corresponding to the access type.
4. The method of claim 2 or 3, wherein upon reaching the upper access limit, the method further comprises:
and returning prompt information to the initiator of the data access request.
5. A method according to claim 2 or 3, characterized in that the method further comprises:
and uploading the stop trigger record of the data access request to the server.
6. A control method for data access is applied to a server side, and is characterized in that the method comprises the following steps:
receiving service metadata uploaded by a client;
returning a configuration strategy to the client according to the service metadata; and the configuration policy is used for enabling the client to stop triggering the data access function when the number of data access times reaches the upper limit according to the access upper limit indicated by the configuration policy.
7. The method of claim 6, wherein the service metadata includes a plurality of applications and a plurality of access types; the returning of the configuration policy to the client according to the service metadata includes:
displaying the service metadata on a user interface;
and generating the configuration policy according to the configured access upper limit for each application and the configured access upper limit for each access type.
8. A control apparatus for data access, comprising:
the data sending module is used for sending the service metadata to the server;
the processing receiving module is used for receiving the configuration strategy issued by the server according to the service metadata;
and the access current limiting module is used for stopping triggering the data access function when the number of data access times reaches the upper limit according to the access upper limit indicated by the configuration strategy.
9. An electronic device, characterized in that the electronic device comprises:
a processor;
a memory for storing processor-executable instructions;
wherein the processor is configured to perform the method of controlling data access of any one of claims 1-7.
10. A computer-readable storage medium, characterized in that the storage medium stores a computer program executable by a processor to perform the method of controlling data access according to any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911027886.8A CN110784351A (en) | 2019-10-25 | 2019-10-25 | Data access control method and device, electronic equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911027886.8A CN110784351A (en) | 2019-10-25 | 2019-10-25 | Data access control method and device, electronic equipment and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN110784351A true CN110784351A (en) | 2020-02-11 |
Family
ID=69386844
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911027886.8A Pending CN110784351A (en) | 2019-10-25 | 2019-10-25 | Data access control method and device, electronic equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110784351A (en) |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102724189A (en) * | 2012-06-06 | 2012-10-10 | 杭州华三通信技术有限公司 | Method and device for controlling user URL (uniform resource locator) access |
| CN106375472A (en) * | 2016-09-29 | 2017-02-01 | 北京三快在线科技有限公司 | Access request processing method and apparatus, and server |
| CN109815716A (en) * | 2019-01-08 | 2019-05-28 | 平安科技（深圳）有限公司 | Access request processing method, device, storage medium and server |
| CN109962855A (en) * | 2017-12-14 | 2019-07-02 | 深圳市融汇通金科技有限公司 | A kind of current-limiting method of WEB server, current-limiting apparatus and terminal device |
-
2019
- 2019-10-25 CN CN201911027886.8A patent/CN110784351A/en active Pending
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102724189A (en) * | 2012-06-06 | 2012-10-10 | 杭州华三通信技术有限公司 | Method and device for controlling user URL (uniform resource locator) access |
| CN106375472A (en) * | 2016-09-29 | 2017-02-01 | 北京三快在线科技有限公司 | Access request processing method and apparatus, and server |
| CN109962855A (en) * | 2017-12-14 | 2019-07-02 | 深圳市融汇通金科技有限公司 | A kind of current-limiting method of WEB server, current-limiting apparatus and terminal device |
| CN109815716A (en) * | 2019-01-08 | 2019-05-28 | 平安科技（深圳）有限公司 | Access request processing method, device, storage medium and server |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US9935847B2 (en) | Dynamic grouping of managed devices | |
| CN108153670B (en) | Interface testing method and device and electronic equipment | |
| CN109064345B (en) | Message processing method, system and computer readable storage medium | |
| CN109542361B (en) | Distributed storage system file reading method, system and related device | |
| US9836346B2 (en) | Error troubleshooting using a correlated knowledge base | |
| US9930632B2 (en) | M2M application remote registration method, device, system and storage medium | |
| EP2989543B1 (en) | Method and device for updating client | |
| CN104253741A (en) | Information sending method and device and system thereof | |
| CN110704872B (en) | Data query method and device, electronic equipment and computer readable storage medium | |
| EP4277239A1 (en) | Cloud platform and bucket management method for object storage service provided thereby | |
| CN107154959A (en) | A kind of method and apparatus of the access network address | |
| CN112367345A (en) | Data processing method, server device and computer readable storage medium | |
| CN106713242B (en) | Data request processing method and processing device | |
| CN108650123B (en) | Fault information recording method, device, equipment and storage medium | |
| CN110784358A (en) | Method and device for constructing network call relation topological graph | |
| CN110933152A (en) | Preheating method, device and system and electronic equipment | |
| CN107509097B (en) | Video sharing method and device and sharing server | |
| CN109391658B (en) | Account data synchronization method and equipment, storage medium and terminal thereof | |
| CN105184559A (en) | System and method for payment | |
| CN107547221B (en) | Method and equipment for providing log information | |
| CN112019546A (en) | Protection strategy adjusting method, system, equipment and computer storage medium | |
| US20170223136A1 (en) | Any Web Page Reporting and Capture | |
| CN110784351A (en) | Data access control method and device, electronic equipment and storage medium | |
| TW201719455A (en) | Metadata server, network device and automatic resource management method | |
| CN110134547B (en) | Middleware-based repeated data deleting method and related device |
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 | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20200211 |
|
| RJ01 | Rejection of invention patent application after publication |