How to access Cloud Notes users

Abstract

The present application discloses an access method for cloud note users, comprising: intercepting an access request for a cloud note, the access request carrying an identifier of a target user; if it is determined based on the identifier of the target user that the target user is a user registered before the cloud note was upgraded to the current version, then based on the historical access data of the cloud base of the target user, predicting that the access request will consume a first carrying capacity of the cloud base after entering the cloud base corresponding to the cloud note; and determining whether to allow the access request to enter the cloud base based on the first carrying capacity and a preset carrying capacity range of the cloud base.

Description

Technical Field

[0001] The present application relates to the technical field of cloud notes, and in particular to an access method for cloud notes users. Background Art

[0002] Cloud Notes is a document note-taking software. Cloud Notes is stored in plain text cloud, which is concise and clear. It is completely free storage, and its functions include cloud storage, etc. Since the interfaces of Cloud Notes after version upgrade or update reconstruction are only connected to the new cloud base, the registered users bound to the new / old cloud base are compatible through interface routing. The interface traffic or access requests of Cloud Notes after version upgrade will enter the new cloud base, which will cause the new cloud base, such as memory and other resources, to carry too much capacity and service performance to decline.

[0003] How to improve the service performance of the cloud base that Cloud Notes connects to after version upgrade is a technical problem that needs to be solved at present. Summary of the invention

[0004] The purpose of the embodiments of the present application is to provide an access method for cloud note users, so as to solve the problem of decreased service performance of the cloud base connected after the cloud note version is upgraded.

[0005] In order to solve the above technical problems, this specification is implemented as follows: In a first aspect, a method for accessing a cloud note user is provided, comprising: Intercepting access requests to cloud notes, where the access requests carry the identifier of the target user; If it is determined based on the identifier of the target user that the target user is a user registered before the cloud note is upgraded to the current version, then based on the historical access data of the cloud base of the target user, predicting that the first carrying capacity of the cloud base will be consumed after the access request enters the cloud base corresponding to the cloud note; Based on the first carrying capacity and a preset carrying capacity range of the cloud base, it is determined whether to allow the access request to enter the cloud base.

[0006] Optionally, the determining, based on the identifier of the target user, that the target user is a user registered before the cloud note is upgraded to the current version includes: Based on the identifier of the target user, obtaining authentication information of the target user currently logging into the cloud note, wherein the authentication information includes the cloud base identifier bound when the user registered the cloud note; If the cloud base identifier corresponds to the cloud base to which the cloud note was connected before it was upgraded to the current version, the target user is determined to be a user registered before the cloud note was upgraded to the current version.

[0007] Optionally, the predicting, based on the target user's cloud base historical access data, that the access request consumes a first carrying capacity of the cloud base corresponding to the cloud note after entering the cloud base, includes: Obtaining traffic data in the cloud base historical access data generated when each historical access request of the target user enters the corresponding cloud base, the traffic data including access duration, the number of cloud note pages accessed, and the consumed cloud base carrying capacity; The average value of each flow data is used as the predicted first carrying capacity of the cloud base.

[0008] Optionally, the predicting, based on the target user's cloud base historical access data, before the access request enters the cloud base corresponding to the cloud note and consumes the first carrying capacity of the cloud base, further includes: Determine whether the target user is a user in a preset whitelist; If the target user is not a user in the preset whitelist, based on the historical access data of the cloud base of the target user, predicting that the first carrying capacity of the cloud base will be consumed after the access request enters the cloud base corresponding to the cloud note; If the target user is a user in the preset whitelist, the access request is allowed to enter the cloud base.

[0009] Optionally, the determining whether to allow the access request to enter the cloud base based on the first carrying capacity and a preset carrying capacity range of the cloud base includes: If the first carrying capacity is less than a minimum value in a preset carrying capacity range of the cloud base, allowing the access request to enter the cloud base; If the first carrying capacity is greater than a maximum value in a preset carrying capacity range of the cloud base, switching the access request to access a backup cloud base of the cloud base; If the first carrying capacity falls within a preset carrying capacity range of the cloud base, it is determined whether to allow the access request to enter the cloud base based on the first carrying capacity and the current remaining carrying capacity of the cloud base.

[0010] Optionally, the determining whether to allow the access request to enter the cloud base based on the first carrying capacity and the current remaining carrying capacity of the cloud base includes: Based on the time when the target user sends the access request, the consumption of the carrying capacity of the cloud base by each user who simultaneously accesses the cloud base and the used carrying capacity of the cloud base, determine the current remaining carrying capacity of the cloud base; If the current remaining carrying capacity of the cloud base is less than or equal to the first carrying capacity, switching the access request to access a backup cloud base of the cloud base; If the current remaining capacity of the cloud base is greater than the first capacity, it is determined whether to allow the access request to enter the cloud base based on the access security value of the target user, where the access security value is related to the behavioral security data of the target user's historical access to the cloud base.

[0011] Optionally, the determining the current remaining carrying capacity of the cloud base based on the time when the target user sends the access request and the consumption of the carrying capacity of the cloud base and the used carrying capacity of the cloud base by each user who simultaneously accesses the cloud base comprises: Acquire the time when the target user sends the access request, and the access requests of other users who have sent and entered the cloud base; Obtaining access requests from other users and entering the cloud base to consume the concurrent carrying capacity of the cloud base; Sum the concurrent load of other users and the used load of the cloud base to obtain the total load consumption of the cloud base; The total load consumption of the cloud base is subtracted from the maximum value of the preset load capacity range of the cloud base to obtain the current remaining load capacity of the cloud base.

[0012] Optionally, the determining whether to allow the access request to enter the cloud base based on the access security value of the target user includes: Obtain the number of virus intrusions and potential risk behaviors existing in the cloud base when the target user accesses the cloud base from the target user's behavior security data; Determine the access security value of the target user based on the number of virus intrusions and the number of potential risk behaviors; If the access security value is less than a preset access security threshold, switching the access request to access a backup cloud base of the cloud base; If the access security value is greater than or equal to the preset access security threshold, the access request is allowed to enter the cloud base.

[0013] Optionally, determining the access security value of the target user based on the number of virus intrusions and the number of potential risk behaviors includes: Determine the access time period to which the target user sends the access request; Obtaining the number of virus intrusions and potential danger behaviors existing in the cloud base when the target user accesses the cloud base within the corresponding access period from the target user's behavior security data; Based on the number of virus intrusions and the number of potential danger behaviors, and the safety coefficient of the access period corresponding to the target user, the access safety value of the target user is determined, wherein the safety coefficients of different access periods are different.

[0014] Optionally, switching the access request to access a backup cloud base of the cloud base includes: Obtain a backup cloud base list corresponding to the cloud base; Determine the current remaining capacity of each backup cloud base in the backup cloud base list; If the current remaining carrying capacity of the multiple target backup cloud bases is greater than the first carrying capacity of the target user, obtaining access response durations of the multiple target backup cloud bases; The target user's access request to the cloud base is switched to a target backup cloud base having the shortest access response time.

[0015] In an embodiment of the present application, an access request for a cloud note is intercepted, and the access request carries an identifier of a target user; if the target user is determined to be a user registered before the cloud note is upgraded to the current version based on the identifier of the target user, then based on the historical access data of the cloud base of the target user, it is predicted that the access request will consume the first carrying capacity of the cloud base after entering the cloud base corresponding to the cloud note; based on the first carrying capacity and the preset carrying capacity range of the cloud base, it is determined whether the access request is allowed to enter the cloud base, thereby firstly performing a user analysis on the user accessing the cloud base used by the cloud note, so as to allow or prohibit the access request of the user registered before the cloud note is upgraded in combination with the carrying capacity of the accessed cloud base. Compared with the previous cloud note version update, after all users' access requests will enter the cloud base connected to the cloud note, resulting in excessive carrying capacity of the cloud base and reduced service performance, the embodiment of the present application can realize the traffic switching of the cloud base used by the cloud note by intelligently switching and transferring the access pressure of the user registered before the cloud note upgrade, effectively improving the service performance of the base used by the cloud note and reducing the carrying capacity of the base used by the cloud note, so as to better serve the user and bring a good user experience to the user. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] The drawings described herein are used to provide a further understanding of the present application and constitute a part of the present application. The illustrative embodiments of the present application and their descriptions are used to explain the present application and do not constitute an improper limitation on the present application. In the drawings: Figure 1 It is a flowchart of the access method for cloud note users in an embodiment of the present application.

[0017] Figure 2 It is a structural block diagram of an access device for a cloud note user according to an embodiment of the present application. DETAILED DESCRIPTION

[0018] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, rather than all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application. The numbering of the drawings in this application is only used to distinguish the various steps in the scheme, and is not used to limit the execution order of the various steps. The specific execution order is subject to the description in the specification.

[0019] In order to solve the problems existing in the prior art, the present application embodiment provides a method for accessing a cloud note user, such as Figure 1 As shown, the following steps 102 to 106 are included.

[0020] Step 102: intercepting an access request to a cloud note, wherein the access request carries an identifier of a target user.

[0021] The target user sends an access request to the cloud note to request to perform the corresponding operation on the cloud note. The relevant text data on the cloud note is stored on the cloud base. The user's access request to the cloud note requires access to the cloud base to which the cloud note is connected. The user ID carried in the access request can be the unique user ID when the user registers the cloud note. Through this user ID, the relevant information of the user registration can be obtained.

[0022] Intercepting the access request here means that the access request sent by the target user will not be directly connected to the cloud base corresponding to the cloud note. After the corresponding judgment is made in the subsequent steps, the operation corresponding to the access request will be executed.

[0023] Step 104: If it is determined based on the identifier of the target user that the target user is a user registered before the cloud note is upgraded to the current version, then based on the historical access data of the cloud base of the target user, it is predicted that the access request will consume the first carrying capacity of the cloud base after entering the cloud base corresponding to the cloud note.

[0024] After a user registers on Cloud Notes, the cloud base that Cloud Notes is connected to will be bound to the registered user. If Cloud Notes is subsequently upgraded, Cloud Notes will be connected to a new cloud base, which is different from the cloud base bound after the user registered. Users who registered before Cloud Notes was upgraded to the current version are also called old users; users who registered after Cloud Notes was upgraded to the current version are also called new users. The current version here refers to the latest version.

[0025] In an embodiment of the present application, if the user of the currently intercepted access request is an old user, it is first predicted whether the access request of the old user can directly enter the new cloud base connected to the cloud note after the version upgrade.

[0026] Optionally, determining the target user as a user registered before the cloud note is upgraded to the current version based on the identifier of the target user includes: obtaining authentication information of the target user when currently logging into the cloud note based on the identifier of the target user, the authentication information including a cloud base identifier bound when the user registered the cloud note; if the cloud base identifier corresponds to the cloud base connected before the cloud note was upgraded to the current version, determining that the target user is a user registered before the cloud note is upgraded to the current version.

[0027] The target user's ID can be used to obtain the target user's authentication information when logging into the cloud note, including the target user's account, password, and the cloud base ID bound when the user registered the cloud note. The cloud base ID bound when the user registered is compared with the cloud base ID currently connected to the cloud note. If they do not match, it means that the target user is a user who registered before the cloud note was upgraded to the current version, that is, an old user.

[0028] The embodiment of the present application can implement the interception of access requests and traffic switching by adding an interceptor in the cloud base. First, the new and old users of the users currently accessed by the new cloud base used by the cloud note are analyzed. If they are new users, the new users can continue to access the services of the new cloud base; if they are old users, it is necessary to predict the corresponding load consumption of the old users' access requests.

[0029] If the target user of the intercepted access request is an old user, firstly, based on the historical access data of the cloud base of the target user, predict the capacity of the cloud base that will be consumed after the intercepted access request enters the new cloud base corresponding to the cloud note. The capacity of the cloud base can be represented by the memory percentage of the cloud base operation. For example, when there is no access, all the memory of the cloud base is idle, the used capacity of the cloud base is 0%, and the remaining capacity is 100%. After the access request enters the cloud base for the corresponding access operation, it will occupy or consume the proportion of the cloud base's memory. For example, if 10% of the cloud base's memory is consumed, the corresponding cloud base's capacity is 10%.

[0030] Before an access request enters the cloud base, the capacity of the cloud base consumed by the access request is predicted based on the target user's historical access data of the cloud base. This is to determine in advance whether the access request of an old user entering the cloud base will cause the current capacity of the cloud base to be too large.

[0031] Optionally, the method predicts the first carrying capacity of the cloud base consumed by the access request after entering the cloud base corresponding to the cloud note based on the historical access data of the cloud base of the target user, including: obtaining traffic data in the historical access data of the cloud base generated when each historical access request of the target user enters the corresponding cloud base, the traffic data including the access duration, the number of cloud note pages visited and the amount of cloud base resources consumed; and taking the average value of each traffic data as the predicted first carrying capacity of the cloud base.

[0032] First, obtain the historical access traffic data of old users, including the number of times old users have accessed the cloud base (or the number of access requests sent) in the past preset time, as well as the access duration of each visit to the corresponding cloud base, the number of cloud note pages visited, and the cloud base capacity consumed when visiting different cloud note pages. The cloud bases visited by old users here include the cloud bases connected before the cloud notes were upgraded to the current version, and the cloud bases connected after the cloud notes were upgraded to the current version.

[0033] Calculate the average value of each historical traffic data obtained, and use the average value of the traffic data as the predicted carrying capacity generated after the target user's access request enters the cloud base currently connected to the cloud note, that is, the carrying capacity that may be generated when the user's access request accesses the cloud base is predicted in advance.

[0034] The average value of historical traffic data = [access duration / first standard value + (number of cloud note pages visited * amount of data carried) / second standard value] / number of access requests.

[0035] To improve the security of cloud base access, in one embodiment, optionally, the prediction based on the target user's cloud base historical access data before the access request consumes the first carrying capacity of the cloud base after entering the cloud base corresponding to the cloud note also includes: determining whether the target user is a user in a preset whitelist; if the target user is not a user in the preset whitelist, predicting based on the target user's cloud base historical access data before the access request consumes the first carrying capacity of the cloud base after entering the cloud base corresponding to the cloud note; if the target user is a user in the preset whitelist, allowing the access request to enter the cloud base.

[0036] In the above embodiment, after determining that the target user is an old user, the number information of the user in the whitelist is first obtained, and the number information is compared with the user number of the target user who is an old user. If the user number matches the number information in the whitelist, the target user is allowed to access the services of the cloud base currently connected to the cloud note; if the user number does not match the number information in the whitelist, the traffic analysis is performed on the target user whose number information does not match, in order to predict the load capacity of the cloud base consumed after the target user's access request enters the cloud base.

[0037] Step 106: Determine whether to allow the access request to enter the cloud base based on the first carrying capacity and a preset carrying capacity range of the cloud base.

[0038] The first carrying capacity is the carrying capacity of the cloud base that may be consumed by the target user's access request after entering the cloud base as predicted in step 104. The preset carrying capacity range of the cloud base can be determined based on the actual carrying capacity consumed by each historical access request on the cloud base. For example, the maximum and minimum values ​​of the actual carrying capacity historically consumed by the cloud base are used as the interval corresponding to the preset carrying capacity range of the cloud base.

[0039] The determining whether to allow the access request to enter the cloud base based on the first carrying capacity and the preset carrying capacity range of the cloud base includes: if the first carrying capacity is less than the minimum value in the preset carrying capacity range of the cloud base, allowing the access request to enter the cloud base; if the first carrying capacity is greater than the maximum value in the preset carrying capacity range of the cloud base, switching the access request to enter the backup cloud base of the cloud base; if the first carrying capacity falls within the preset carrying capacity range of the cloud base, determining whether to allow the access request to enter the cloud base based on the first carrying capacity and the current remaining carrying capacity of the cloud base.

[0040] By comparing the first load capacity predicted by the target user with the maximum value and the minimum value of the preset load capacity range of the cloud base, it is determined whether the first load capacity predicted by the target user is within the preset load capacity range of the cloud base.

[0041] If the first carrying capacity is not within the preset carrying capacity range of the cloud base, there are two situations: 1. The predicted first carrying capacity is smaller than the left endpoint of the preset carrying capacity range, and the access request of the intercepted target user is allowed to enter the cloud base for continuous access; 2. The predicted first carrying capacity is larger than the right endpoint of the preset carrying capacity range, and the access request of the intercepted target user is switched to enter the backup cloud base of the cloud base.

[0042] If the first carrying capacity is within the preset carrying capacity range of the cloud base, it is necessary to determine whether to allow the intercepted access request to enter the cloud base in combination with the current remaining carrying capacity of the cloud base.

[0043] Specifically, the determining whether to allow the access request to enter the cloud base based on the first carrying capacity and the current remaining carrying capacity of the cloud base includes: determining the current remaining carrying capacity of the cloud base based on the moment when the target user sends the access request, and the consumption of the carrying capacity of the cloud base and the used carrying capacity of the cloud base by each user who simultaneously accesses the cloud base; if the current remaining carrying capacity of the cloud base is less than or equal to the first carrying capacity, switching the access request to enter a backup cloud base of the cloud base; if the current remaining carrying capacity of the cloud base is greater than the first carrying capacity, determining whether to allow the access request to enter the cloud base based on the access security value of the target user, and the access security value is related to the behavioral security data of the target user's historical access to the cloud base.

[0044] The current remaining capacity of the cloud base refers to the proportion of the cloud base's unoccupied memory, which is related to the current used capacity of the cloud base and the concurrent capacity of the cloud base consumed by concurrent access requests when the target user sends the access request.

[0045] Specifically, the method determines the current remaining carrying capacity of the cloud base based on the moment when the target user sends the access request, the carrying capacity of the cloud base and the used carrying capacity of the cloud base consumed by each user who simultaneously accesses the cloud base, and includes: obtaining the moment when the target user sends the access request, and the access requests of other users who have sent and entered the cloud base; obtaining the concurrent carrying capacity of the cloud base consumed after the access requests of other users enter the cloud base; summing the concurrent carrying capacity of other users and the used carrying capacity of the cloud base to obtain the total carrying capacity consumption of the cloud base; subtracting the total carrying capacity consumption of the cloud base from the maximum value of the preset carrying capacity range of the cloud base to obtain the current remaining carrying capacity of the cloud base.

[0046] When the target user sends an access request to access the cloud base (when the access request is intercepted and has not yet entered the cloud base), the current used carrying capacity of the cloud base is obtained, and at the same time, the concurrent carrying capacity of other users of the cloud base at the current moment is obtained (the carrying capacity consumed by the access requests sent at the same moment and that have entered the cloud base). The concurrent carrying capacity is the cloud base carrying capacity consumed by other users who access the cloud base at the same time as the target user. The current used carrying capacity of the cloud base plus the concurrent carrying capacity are obtained to obtain the total carrying capacity consumption of the cloud base when the target user accesses the cloud base.

[0047] If the predicted first carrying capacity is within the preset carrying capacity range of the cloud base, the total carrying consumption of the cloud base is subtracted from the right end point of the preset carrying capacity range to obtain the current remaining carrying capacity of the cloud base accessed by the target user.

[0048] If the current remaining capacity of the cloud base is less than or equal to the predicted first capacity, it means that the current remaining capacity of the cloud base is too small and no new access requests can be accepted. If new access requests are accepted, the service performance of the cloud base will be reduced. Therefore, the intercepted access request will be switched to the backup cloud base that enters the cloud base.

[0049] If the current remaining capacity of the cloud base is greater than the predicted first capacity, then in order to ensure the safe operation of the cloud base, it can be further combined with the access security value of the target user to determine whether to allow the intercepted access request to enter the cloud base. The access security value is related to the target user's historical behavioral security data of accessing the cloud base.

[0050] Optionally, determining whether to allow the access request to enter the cloud base based on the access security value of the target user includes: obtaining the number of virus intrusions and the number of hidden danger behaviors that exist in the cloud base when the target user accesses the cloud base from the behavioral security data of the target user; determining the access security value of the target user based on the number of virus intrusions and the number of hidden danger behaviors; if the access security value is less than a preset access security threshold, switching the access request to enter a backup cloud base of the cloud base; if the access security value is greater than or equal to the preset access security threshold, allowing the access request to enter the cloud base.

[0051] By obtaining the target user's historical behavioral security data generated when accessing the cloud base, and according to the number of virus intrusions and hidden danger behaviors suffered by the target user in the historical behavioral security data, the target user's access security value when accessing the cloud base is determined. Hidden danger behaviors include the target user uploading files that have not been security authenticated and are of unknown origin when accessing the cloud base.

[0052] The calculation method of the access safety value is: Access safety value = 1 / (number of virus intrusions * corresponding weight coefficient + number of potential risk behaviors * corresponding weight coefficient).

[0053] If the access security value of the target user is less than the preset access security threshold, the intercepted access request of the target user is switched to enter the backup cloud base of the cloud base, and the access request to the cloud base is switched; if the access security value of the target user is greater than or equal to the preset access security threshold, the intercepted access request of the target user is allowed to enter the cloud base for continuous access to the cloud base.

[0054] In one embodiment, the preset capacity range of the cloud base can also be divided into preset capacity ranges corresponding to different access time periods according to different access time periods corresponding to each historical access request, for example, the access time period includes a low-peak time period, a normal time period, and a peak time period. For example, the normal time period is 12:00-14:00 and 17:30-00:00, the low-peak time period is 00:00-08:30, and the peak time period is 08:30-12:00 and 14:00-17:30.

[0055] Obtain the real-time load capacity of the cloud base during multiple historical peak periods, traverse and compare the real-time load capacity during multiple historical peak periods, obtain the maximum and minimum real-time load capacity, and use the maximum and minimum real-time load capacity as the preset load capacity range for the peak period. Similarly, the preset load capacity ranges for normal periods and off-peak periods can be obtained according to the above method. At the same time, the left endpoint of the preset load capacity range corresponding to the peak period (i.e., the minimum real-time load capacity) is greater than or equal to the right endpoint of the preset load capacity range corresponding to the normal period (i.e., the maximum real-time load capacity), and the left endpoint of the preset load capacity range corresponding to the normal period is greater than or equal to the right endpoint of the preset load capacity range corresponding to the off-peak period.

[0056] Correspondingly, when comparing the first carrying capacity with the preset carrying capacity range of the cloud base in step 106, the access time period to which the target user sends the access request belongs can be first determined, and then the first carrying capacity can be compared with the preset carrying capacity range of the corresponding access time period to determine whether the intercepted access request is allowed to enter the cloud base.

[0057] Correspondingly, different preset access security factors may be set in combination with the access time period to obtain the access security value of the target user at the access moment.

[0058] Specifically, the access security value of the target user is determined based on the number of virus intrusions and the number of hidden danger behaviors, including: determining the access time period to which the moment when the target user sends the access request belongs; obtaining the number of virus intrusions and the number of hidden danger behaviors existing on the cloud base when the target user accesses the cloud base within the corresponding access time period from the target user's behavioral security data; based on the number of virus intrusions and the number of hidden danger behaviors, and the safety factor of the access time period corresponding to the target user, determining the access security value of the target user, wherein the safety factors of different access time periods are different.

[0059] At this time, the calculation method of the access safety value is specifically: access safety value = 1 / (number of virus intrusions*corresponding weight coefficient+number of hidden danger behaviors*corresponding weight coefficient)*access period safety coefficient.

[0060] Among them, the access safety factor during peak hours is smaller than that during normal hours, and the access safety factor during normal hours is smaller than that during off-peak hours.

[0061] As described above, in combination with the remaining carrying capacity of the cloud base, if the intercepted access request is not allowed to enter the cloud base, the access request can be switched to enter the backup cloud base of the cloud base.

[0062] Optionally, switching the access request to enter a backup cloud base of the cloud base includes: obtaining a backup cloud base list corresponding to the cloud base; determining the current remaining carrying capacity of each backup cloud base in the backup cloud base list; if the current remaining carrying capacity of multiple target backup cloud bases is greater than the first carrying capacity of the target user, obtaining the access response time of the multiple target backup cloud bases; and switching the target user's access request to the cloud base to enter the target backup cloud base with the shortest access response time.

[0063] Multiple backup cloud bases with similar functions are stored in the backup list of the cloud base connected to the cloud note currently accessed by the target user. Then, the preset capacity range and used capacity of each backup cloud base in the current access period are obtained, and the current remaining capacity of each backup cloud base is obtained by subtracting the used capacity from the right end point of the preset capacity range of each backup cloud base. If the current remaining capacity of multiple backup cloud bases exceeds the first capacity predicted by the target user, the access response time of the multiple backup cloud bases is obtained, and based on the access response time, the one with the shortest access response time is selected from the multiple backup cloud bases and used as the backup cloud base to which the target user's access request is finally switched. If the current remaining capacity of only one backup cloud base exceeds the first capacity predicted by the target user, the backup cloud base is directly used as the backup cloud base to which the target user's access request is finally switched.

[0064] In an embodiment of the present application, an access request for a cloud note is intercepted, and the access request carries an identifier of a target user; if the target user is determined to be a user registered before the cloud note is upgraded to the current version based on the identifier of the target user, then based on the historical access data of the cloud base of the target user, it is predicted that the access request will consume the first carrying capacity of the cloud base after entering the cloud base corresponding to the cloud note; based on the first carrying capacity and the preset carrying capacity range of the cloud base, it is determined whether the access request is allowed to enter the cloud base, thereby firstly performing a user analysis on the user accessing the cloud base used by the cloud note, so as to allow or prohibit the access request of the user registered before the cloud note is upgraded in combination with the carrying capacity of the accessed cloud base. Compared with the previous cloud note version update, after all users' access requests will enter the cloud base connected to the cloud note, resulting in excessive carrying capacity of the cloud base and reduced service performance, the embodiment of the present application can realize the traffic switching of the cloud base used by the cloud note by intelligently switching and transferring the access pressure of the user registered before the cloud note upgrade, effectively improving the service performance of the base used by the cloud note and reducing the carrying capacity of the base used by the cloud note, so as to better serve the user and bring a good user experience to the user.

[0065] Alternatively, if Figure 2 As shown, the embodiment of the present application also provides an access device 2000 for a cloud note user, including a processor 2400 and a memory 2200, and the memory 2200 stores programs or instructions that can be executed on the processor 2400. When the program or instructions are executed by the processor 2400, the various steps of the above-mentioned cloud note user access method embodiment are implemented, and the same technical effect can be achieved. To avoid repetition, they are not repeated here.

[0066] The embodiment of the present application also provides a readable storage medium, on which a program or instruction is stored. When the program or instruction is executed by the processor, each process of any of the above-mentioned cloud note user access method embodiments is implemented, and the same technical effect can be achieved. To avoid repetition, it is not repeated here. Among them, the readable storage medium includes a computer-readable storage medium, such as a read-only memory (ROM), a random access memory (RAM), a disk or an optical disk, etc.

[0067] An embodiment of the present application also provides a computer program product, which includes a non-transitory computer-readable storage medium storing a computer program. The computer program is operable to enable a computer to implement the various processes of any of the above-mentioned cloud note user access method embodiments when executed, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0068] It should be noted that, in this article, the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, an element defined by the sentence "comprises a ..." does not exclude the existence of other identical elements in the process, method, article or device including the element.

[0069] Through the description of the above implementation methods, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of software plus a necessary general hardware platform, and of course by hardware, but in many cases the former is a better implementation method. Based on such an understanding, the technical solution of the present application, or the part that contributes to the prior art, can be embodied in the form of a software product, which is stored in a storage medium (such as ROM / RAM, a magnetic disk, or an optical disk), and includes a number of instructions for a terminal (which can be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) to execute the methods described in each embodiment of the present application.

[0070] The embodiments of the present application are described above in conjunction with the accompanying drawings, but the present application is not limited to the above-mentioned specific implementation methods. The above-mentioned specific implementation methods are merely illustrative and not restrictive. Under the guidance of the present application, ordinary technicians in this field can also make many forms without departing from the purpose of the present application and the scope of protection of the claims, all of which are within the protection of the present application.

Claims

1. A method for accessing a cloud note user, characterized in that: include: Intercepting access requests to cloud notes, where the access requests carry the identifier of the target user; If it is determined based on the identifier of the target user that the target user is a user registered before the cloud note is upgraded to the current version, then based on the historical access data of the cloud base of the target user, predicting that the first carrying capacity of the cloud base will be consumed after the access request enters the cloud base corresponding to the cloud note; Based on the first carrying capacity and a preset carrying capacity range of the cloud base, it is determined whether to allow the access request to enter the cloud base.

2. The method according to claim 1, characterized in that The determining, based on the identifier of the target user, that the target user is a user registered before the cloud note is upgraded to the current version includes: Based on the identifier of the target user, obtaining authentication information of the target user currently logging into the cloud note, wherein the authentication information includes the cloud base identifier bound when the user registered the cloud note; If the cloud base identifier corresponds to the cloud base to which the cloud note was connected before it was upgraded to the current version, the target user is determined to be a user registered before the cloud note was upgraded to the current version.

3. The method according to claim 1, characterized in that The predicting, based on the target user's cloud base historical access data, that the access request enters the cloud base corresponding to the cloud note and consumes a first carrying capacity of the cloud base includes: Obtaining traffic data in the cloud base historical access data generated when each historical access request of the target user enters the corresponding cloud base, the traffic data including access duration, the number of cloud note pages accessed, and the consumed cloud base carrying capacity; The average value of each flow data is used as the predicted first carrying capacity of the cloud base.

4. The method according to claim 3, characterized in that The step of predicting that the access request enters the cloud base corresponding to the cloud note and consumes the first carrying capacity of the cloud base based on the historical access data of the cloud base of the target user before the first carrying capacity of the cloud base is consumed also includes: Determine whether the target user is a user in a preset whitelist; If the target user is not a user in the preset whitelist, based on the historical access data of the cloud base of the target user, predicting that the first carrying capacity of the cloud base will be consumed after the access request enters the cloud base corresponding to the cloud note; If the target user is a user in the preset whitelist, the access request is allowed to enter the cloud base.

5. The method according to claim 1, characterized in that The determining whether to allow the access request to enter the cloud base based on the first carrying capacity and a preset carrying capacity range of the cloud base includes: If the first carrying capacity is less than a minimum value in a preset carrying capacity range of the cloud base, allowing the access request to enter the cloud base; If the first carrying capacity is greater than a maximum value in a preset carrying capacity range of the cloud base, switching the access request to access a backup cloud base of the cloud base; If the first carrying capacity falls within a preset carrying capacity range of the cloud base, it is determined whether to allow the access request to enter the cloud base based on the first carrying capacity and the current remaining carrying capacity of the cloud base.

6. The method according to claim 5, characterized in that The determining, based on the first carrying capacity and the current remaining carrying capacity of the cloud base, whether to allow the access request to enter the cloud base comprises: Based on the time when the target user sends the access request, the consumption of the carrying capacity of the cloud base by each user who simultaneously accesses the cloud base and the used carrying capacity of the cloud base, determine the current remaining carrying capacity of the cloud base; If the current remaining carrying capacity of the cloud base is less than or equal to the first carrying capacity, switching the access request to access a backup cloud base of the cloud base; If the current remaining capacity of the cloud base is greater than the first capacity, it is determined whether to allow the access request to enter the cloud base based on the access security value of the target user, where the access security value is related to the behavioral security data of the target user's historical access to the cloud base.

7. The method according to claim 6, characterized in that The determining, based on the time when the target user sends the access request, the carrying capacity of the cloud base consumed by each user who simultaneously accesses the cloud base and the used carrying capacity of the cloud base, of the current remaining carrying capacity of the cloud base comprises: Acquire the time when the target user sends the access request, and the access requests of other users who have sent and entered the cloud base; Obtaining access requests from other users and entering the cloud base to consume the concurrent carrying capacity of the cloud base; Sum the concurrent load of other users and the used load of the cloud base to obtain the total load consumption of the cloud base; The total load consumption of the cloud base is subtracted from the maximum value of the preset load capacity range of the cloud base to obtain the current remaining load capacity of the cloud base.

8. The method according to claim 6, characterized in that The determining whether to allow the access request to enter the cloud base based on the access security value of the target user includes: Obtain the number of virus intrusions and potential risk behaviors existing in the cloud base when the target user accesses the cloud base from the target user's behavior security data; Determine the access security value of the target user based on the number of virus intrusions and the number of potential risk behaviors; If the access security value is less than a preset access security threshold, switching the access request to access a backup cloud base of the cloud base; If the access security value is greater than or equal to the preset access security threshold, the access request is allowed to enter the cloud base.

9. The method according to claim 8, characterized in that The determining the access security value of the target user based on the number of virus intrusions and the number of potential danger behaviors includes: Determine the access time period to which the target user sends the access request; Obtaining the number of virus intrusions and potential danger behaviors existing in the cloud base when the target user accesses the cloud base within the corresponding access period from the target user's behavior security data; Based on the number of virus intrusions and the number of potential danger behaviors, and the safety coefficient of the access period corresponding to the target user, the access safety value of the target user is determined, wherein the safety coefficients of different access periods are different.

10. The method according to any one of claims 5 to 6 and 8, characterized in that: The step of switching the access request to a backup cloud base of the cloud base includes: Obtain a backup cloud base list corresponding to the cloud base; Determine the current remaining capacity of each backup cloud base in the backup cloud base list; If the current remaining carrying capacity of the multiple target backup cloud bases is greater than the first carrying capacity of the target user, obtaining access response durations of the multiple target backup cloud bases; The target user's access request to the cloud base is switched to a target backup cloud base having the shortest access response time.

Images