Method and device for concurrent login of same account, computer equipment and storage medium
By evaluating the trust and feasibility of the new login requests of the account, determining the processing strategy, solving the security and user experience problems of concurrent login management of the account in the existing technology, and realizing the orderly concurrent login of the account and the system resources. Efficient management.
Patent Information
- Application Number
- CN202411034293.5
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-07-30
- Publication Date
- 2024-11-29
- Estimated Expiration
- 2044-07-30
AI Technical Summary
The existing technology is difficult to effectively manage concurrent logins of the same account, resulting in conflicts in security risks, resource occupation and account status, and it is impossible to select an appropriate processing strategy for the new login requests of the account, reducing the user experience.
By receiving new login requests for your account, you can evaluate the trust and feasibility and determine the login request processing strategy, including allowing login, denying login or joining the waiting queue, and evaluate based on the online utilization rate of the account, system resource utilization rate and load coefficient, and combine it with Historical behavior, device behavior, and login request characteristics are evaluated in multi-dimensionally.
It realizes orderly management of concurrent login for the same account, optimizes the use of system resources, improves the security and user experience of account management, ensures that the system avoids overload and crashes under high load conditions, and improves system stability and security.
Smart Images

Figure CN119051898A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the technical field of account management, and in particular to a method, apparatus, computer device and storage medium for concurrent login of the same account. Background Art
[0002] In modern network applications and services, it has become a common phenomenon for users to log in to their accounts through terminal devices to use services. With the changes in technology and needs, service providers have begun to allow the same account to be logged in multiple times, for example: the same user using the same account on multiple devices, and multiple users sharing the same account. However, these situations have put forward higher requirements for the login management of the same account in order to meet the challenges related to security risks, resource occupation, account status conflicts, etc.
[0003] Existing technologies usually implement concurrent login management for the same account by simply limiting the number of logins, manual review or single device binding. However, the singleness of these methods makes it difficult to deal with the complex situation of concurrent logins of the same account, and it is also impossible to select appropriate processing strategies for new login requests of the account, which leads to disordered logins of the same account and reduces the user experience. Summary of the invention
[0004] Based on this, it is necessary to provide a method, device, computer equipment and storage medium for concurrent login of the same account that can realize orderly concurrent login of the same account, which is conducive to optimizing system resource management, thereby improving the security of account management, and improving user experience.
[0005] In one aspect, a method for concurrently logging in with the same account is provided, the method comprising:
[0006] Receive a new login request from an account and obtain the new login request parameters;
[0007] Perform a trust evaluation based on the newly added login request parameters to obtain the newly added login trust;
[0008] Get the current number of online accounts;
[0009] Perform a feasibility assessment based on the account login setting parameters, the current number of online accounts and system status information to obtain a login new feasibility;
[0010] Based on the new login trust and the new login feasibility, a login request processing strategy is determined; wherein the login request processing strategy includes one of the following: allowing login, refusing login, and adding to a login waiting queue.
[0011] In one embodiment, it also includes:
[0012] The login setting parameters include the account online limit and login retention margin;
[0013] The system status information includes the total number of online system accounts, the upper limit of online system accounts, system load, and maximum system load;
[0014] Obtaining the login setting parameters of the account, the current number of online users of the account, and system status information, and performing feasibility assessment includes:
[0015] Obtaining an account online utilization rate according to the current number of online accounts, the login retention balance and the online upper limit of the account;
[0016] Obtaining system resource utilization according to the total number of online system accounts and the upper limit of online system accounts;
[0017] Obtaining a system load factor according to the system load and the system maximum load;
[0018] The feasibility of the new login is obtained based on the online utilization rate of the account, the utilization rate of the system resources, and the system load factor.
[0019] In one embodiment, it also includes:
[0020] The calculation formula of the account online utilization rate is: account online utilization rate = (current number of accounts online + login retention balance) / (account online upper limit);
[0021] The calculation formula of the system resource utilization is: system resource utilization = (total number of online system accounts) / (upper limit of online system accounts);
[0022] The calculation formula of the system load factor is: system load factor = 1 - (system load) / (system maximum load);
[0023] The calculation formula of the new login feasibility is: new login feasibility = (1-account online utilization rate) × system resource utilization rate × system load factor.
[0024] In one embodiment, it also includes:
[0025] The newly added login request parameters include: account history login information, device behavior information and login request information;
[0026] According to the newly added login request parameters, the trust evaluation includes:
[0027] Obtain the historical login information of the account, conduct a historical trustworthiness assessment of the account, and obtain a historical behavior score;
[0028] Obtaining the device behavior information, performing device trust evaluation, and obtaining a device score;
[0029] Obtaining the login request information, performing a request trustworthiness assessment, and obtaining a login request score;
[0030] A comprehensive trust evaluation is performed based on the historical behavior score, the device score, and the login request score to obtain a newly added login trust.
[0031] In one embodiment, it also includes:
[0032] The account login history information includes: normal login times, total login times, abnormal behavior times, active days, and total usage days;
[0033] The calculation formula of the historical behavior score is:
[0034]
[0035] ; Among them, S Behavior is the historical behavior score; L normal is the number of normal logins; L wrong is the number of abnormal behaviors; L all is the total number of logins; D active is the number of active days; D all is the total number of days of use; ω1, ω2, and ω3 represent the weights of login frequency, abnormal behavior, and activity, respectively, and the sum is 1;
[0036] The device behavior information includes: the number of trusted device logins, device security level, the number of new device attempts, and the total number of device attempts;
[0037] The calculation formula of the device behavior score is:
[0038]
[0039] ; Among them, S Device It is the equipment rating; DL trust is the number of trusted device logins; DL all is the total number of device attempts; DL new is the number of attempts for new devices; Level device is the device security level, which takes a value of 0 or 1 depending on whether the device has passed secondary verification; μ1, μ2, and μ3 represent the weights of device consistency, security, and new device use, respectively, and the sum is 1;
[0040] The login request information includes: the number of geographic location matches, the number of time matches, the number of network matches, and the total number of requests;
[0041] The calculation formula of the login request score is:
[0042]
[0043] ; Among them, S request is the login request score; R all is the total number of requests; Match address is the number of geographic location matches; Match time is the number of time matches; Match net is the number of network matches; φ1, φ2, and φ3 represent the weights of geographic location, time, and network characteristics, respectively, and the sum is 1;
[0044] The calculation formula of the newly added login trust is:
[0045] TrustScore=(α·S Behavior +βvS Device +γ·S request )*σ; where TrustScore
[0046] is the newly added login trust; α, β, and γ represent the weights of the historical behavior score, device behavior score, and login request score, respectively, and the sum is 1; σ represents the penalty coefficient, which is used to reduce the trust in specific situations;
[0047] Among them, the calculation formula of the penalty coefficient σ is: Among them, WA represents the current number of abnormal behaviors; WA all Represents the total number of abnormal behaviors recorded by the system; ρ is the penalty factor, ranging from 0 to 0.5.
[0048] In one embodiment, determining a login request processing strategy based on the new login trust and the new login feasibility includes:
[0049] Setting a trust threshold, and classifying the newly added login request as trusted, untrusted, or conditionally trusted based on the trust threshold and the newly added login trust level;
[0050] Setting a feasible threshold, and classifying the system login request into feasible, infeasible, and conditionally feasible based on the feasible threshold and the login feasibility;
[0051] When the new login request is trustworthy and the system login request is feasible, the selected login request processing policy is to allow login;
[0052] When the new login request is trustworthy but the system login new request is not feasible, the selected login request processing strategy is to deny login;
[0053] When the new login request is trusted but the system login new request conditions are feasible, the selected login request processing strategy is to join the waiting queue;
[0054] When the newly added login request is untrustworthy, the selected login request processing strategy is to deny login;
[0055] When the new login request condition is trusted and the system login new request is feasible or the condition is feasible, the selected login request processing strategy is to join the waiting queue;
[0056] When the newly added login request conditions are trusted and the system login newly added request conditions are not feasible, the selected login request processing strategy is to deny login.
[0057] In one embodiment, it also includes:
[0058] According to the determined login request processing strategy, the system recognition degree of the account is evaluated to obtain the system recognition degree of the account; based on the system recognition degree of the account, the login setting parameters are modified;
[0059] Wherein, according to the determined login request processing strategy, performing system recognition evaluation on the account further includes:
[0060] Acquire the plurality of login request processing policies determined by the account, and when the determined login request processing policy is to allow login and the newly added login request is in a trusted state, record it as a trust event;
[0061] According to the number of trust events, the account system recognition is calculated based on the formula:
[0062] Among them, Score satisfaction is the system recognition, Event represents the trust event, and N is the total number of trust events.
[0063] On the other hand, a device for concurrent login of the same account is provided, the device comprising:
[0064] The login module is used to accept new login requests for accounts and obtain new login request parameters;
[0065] A trust evaluation module, used to perform a trust evaluation based on the newly added login request parameters and generate a newly added login trust;
[0066] An account online query module is used to query the status of the associated accounts of the account and obtain the current online number of the account;
[0067] A feasibility evaluation module is used to obtain the account's login setting parameters and system status information, perform feasibility evaluation based on the current number of online users of the account, and generate a login new feasibility;
[0068] A request processing module, configured to select a corresponding login request processing strategy for the new login request according to the new login trust and the new login feasibility;
[0069] An approval evaluation module, used to evaluate the system approval of the account according to the determined login request processing strategy;
[0070] The optimization and correction module is used to modify the login setting parameters according to the system recognition of the account.
[0071] In another aspect, a computer device is provided, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor performs the following steps:
[0072] Receive a new login request for an account, obtain parameters of the new login request; perform a trust evaluation based on the parameters of the new login request to obtain the trust of the new login; obtain the number of accounts currently online; perform a feasibility evaluation based on login setting parameters of the account, the number of accounts currently online and system status information to obtain the feasibility of the new login;
[0073] Based on the new login trust and the new login feasibility, a login request processing strategy is determined; wherein the login request processing strategy includes one of the following: allowing login, refusing login, and adding to a login waiting queue.
[0074] In another aspect, a computer-readable storage medium is provided, on which a computer program is stored, and when the computer program is executed by a processor, the following steps are implemented:
[0075] Receive a new login request for an account, obtain parameters of the new login request; perform a trust evaluation based on the parameters of the new login request to obtain the trust of the new login; obtain the number of accounts currently online; perform a feasibility evaluation based on login setting parameters of the account, the number of accounts currently online and system status information to obtain the feasibility of the new login;
[0076] Based on the new login trust and the new login feasibility, a login request processing strategy is determined; wherein the login request processing strategy includes one of the following: allowing login, refusing login, and adding to a login waiting queue.
[0077] The above-mentioned method, device, computer equipment and storage medium for concurrent login of the same account, through trust evaluation of the new login request of the account, determine whether the new login request is credible, and at the same time, perform feasibility evaluation on the new system login request to determine whether the system can realize the login of the new request; combining the results of the new login trust and the new login feasibility, it is possible to achieve a certain degree of integration and generalization of the complex situation of concurrent login of the same account, so that it is possible to select appropriate request processing strategies for the new login request of the account, realize orderly concurrent login of the same account, and ensure security while improving user experience. BRIEF DESCRIPTION OF THE DRAWINGS
[0078] Figure 1 An application environment diagram of a method for concurrent login with the same account in one embodiment;
[0079] Figure 2 A flowchart of a method for concurrent login of the same account in one embodiment;
[0080] Figure 3 A schematic diagram of a process for processing a login waiting queue in one embodiment;
[0081] Figure 4 is a structural block diagram of a device for concurrent login of the same account in one embodiment;
[0082] Figure 5 FIG. 4 is a diagram showing the internal structure of a computer device in one embodiment. DETAILED DESCRIPTION
[0083] In order to make the purpose, technical solution and advantages of the present application more clearly understood, the present application is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.
[0084] The method for concurrent login with the same account provided in this application can be applied to Figure 1 In the application environment shown, the terminal 102 communicates with the server 104 through a network. The terminal 102 may be, but is not limited to, various personal computers, laptops, smart phones, tablet computers, and portable wearable devices, and the server 104 may be implemented as an independent server or a server cluster consisting of multiple servers.
[0085] In one embodiment, Figure 2 As shown, a method for concurrent login of the same account is provided, and the method is applied to Figure 1 Taking the server 104 in the example as an example, the following steps are included:
[0086] Step 201, receiving a new login request for an account, and obtaining parameters of the new login request.
[0087] Among them, the newly added login request parameters include account history login information, device behavior information and login request information.
[0088] Step 202: perform a trust evaluation based on the newly added login request parameters to obtain the newly added login trust.
[0089] The newly added login trust is a parameter used to determine whether the current login request of the account is trustworthy.
[0090] Specifically, the historical behavior score, device behavior score, and login request score are obtained, the historical behavior score, device behavior score, and login request score are integrated and weighted accordingly, and the newly added login trust is calculated.
[0091] Step 203, obtaining the current number of online accounts;
[0092] The number of currently online accounts refers to the number of devices that have logged in to the account that issued the new login request, or the number of sessions that the account has currently opened.
[0093] Step 204, perform a feasibility assessment based on the account login setting parameters, the number of accounts currently online and system status information to obtain the login addition feasibility.
[0094] Among them, the account login setting parameters are the conditional parameters that need to be met when the account logs in, and are set by the account owner or permission holder; the system status information is the current resource usage status of the system when the account issues a new login request; the login feasibility is the parameter for determining whether the current system status and account settings allow the new login request.
[0095] Specifically, the online utilization rate of the account, the utilization rate of system resources and the system load factor are obtained, and the feasibility of the new login is calculated.
[0096] Step 205, based on the new login trust and the new login feasibility, determine the login request processing strategy; wherein the login request processing strategy includes one of the following: allowing login, denying login, and adding to the login waiting queue.
[0097] Specifically, when both the new login trust and the new login feasibility are high, login is allowed; when at least one of the new login trust and the new login feasibility is medium or high, and the other is not low, the user is added to the login waiting queue; when either the new login trust or the new login feasibility is low, login is rejected.
[0098] In the above method for concurrent login of the same account, the trust of the new login request of the account is evaluated to determine whether the new login request is credible. At the same time, the feasibility of the new system login request is evaluated to determine whether the system can realize the login of the new request. Combining the results of the new login trust and the new login feasibility, it is possible to achieve a certain degree of integration and generalization of the complex situation of concurrent login of the same account, so that appropriate request processing strategies can be selected for the new login request of the account, and orderly concurrent login of the same account can be realized, which is conducive to improving user experience while ensuring security.
[0099] In one embodiment, the login setting parameters include an online upper limit of the account and a login retention margin;
[0100] System status information includes the total number of online system accounts, the upper limit of online system accounts, system load, and maximum system load;
[0101] Obtaining the account's login setting parameters, the number of accounts currently online, and system status information, and conducting a feasibility assessment includes:
[0102] According to the current number of online accounts, the remaining login time and the upper limit of the online account, the online utilization rate of the account is obtained;
[0103] Get the system resource utilization rate based on the total number of online system accounts and the upper limit of online system accounts;
[0104] According to the system load and the system maximum load, the system load factor is obtained;
[0105] Based on the online utilization rate of the account, the utilization rate of system resources and the system load factor, the feasibility of the new login is obtained.
[0106] Specifically, this embodiment establishes an evaluation mechanism for the feasibility of new logins. By evaluating the online utilization rate of accounts, the utilization rate of system resources, and the system load factor, it can reflect to a certain extent the situation currently faced by the system when accounts log in concurrently, thereby ensuring that system resources are not over-occupied, effectively balancing the system load, and improving resource utilization. In addition, when the system is relatively idle, it can arrange for accounts to log in quickly to reduce unnecessary waiting time.
[0107] In one embodiment, the calculation formula of the account online utilization rate is: account online utilization rate = (number of accounts currently online + login retention margin) / (account online upper limit);
[0108] The calculation formula of system resource utilization is: system resource utilization = (total number of online system accounts) / (upper limit of online system accounts);
[0109] The calculation formula of system load factor is: system load factor = 1-(system load) / (system maximum load);
[0110] The calculation formula for the new login feasibility is: New login feasibility = (1-account online utilization rate) × system resource utilization rate × system load factor.
[0111] Specifically, the account utilization rate, system resource utilization rate and system load coefficient are combined to obtain the feasibility of new logins. Among them, a login retention margin is introduced into the account utilization rate. The login retention margin is the difference between the online upper limit of the account and the actual maximum upper limit of the account. It is used to avoid account saturation login and prevent problems such as fluctuations in the current online account status, which is beneficial to improving system stability. At the same time, the introduction of the system load coefficient is used to judge the current load status of the system, so that the system can reject or delay some login requests under high load conditions, avoid system crashes due to overload, and further improve the stability and security of the system.
[0112] In one embodiment, the newly added login request parameters include: account history login information, device behavior information, and login request information;
[0113] Based on the newly added login request parameters, the trust evaluation includes:
[0114] Obtain the account's historical login information, conduct an account's historical trustworthiness assessment, and obtain a historical behavior score;
[0115] Obtain device behavior information, conduct device trust evaluation, and obtain device scores;
[0116] Obtain login request information, conduct request trust evaluation, and obtain login request score;
[0117] A comprehensive trust evaluation is performed based on the historical behavior score, device score, and login request score to obtain the new login trust.
[0118] Specifically, through multi-dimensional evaluation of new login requests for accounts, such as historical behavior, device behavior, and login requests, potential security risks can be more accurately identified, such as abnormal login behavior, account theft risks, etc., thereby improving the security of the system; at the same time, the mutual complementation of evaluation indicators in different dimensions, such as login frequency, device consistency, geographic location matching, etc., makes the trust assessment results more accurate and comprehensive; further, based on the evaluation results, the system can more comprehensively reflect the situation when a new login request is made to an account, thereby flexibly adjusting the processing strategy for login requests.
[0119] In one embodiment, the account history login information includes: normal login times, total login times, abnormal behavior times, active days, and total usage days;
[0120] The calculation formula for the historical behavior score is:
[0121]
[0122] ; Among them, S Behavior is the historical behavior score; L normal is the number of normal logins; L wrong is the number of abnormal behaviors; L all is the total number of logins; D active is the number of active days; D all is the total number of days of use; ω1, ω2, and ω3 represent the weights of login frequency, abnormal behavior, and activity, respectively, and the sum is 1;
[0123] Device behavior information includes: trusted device login times, device security level, new device attempts, and total device attempts;
[0124] The device behavior score is calculated as:
[0125]
[0126] ; Among them, S Device It is the equipment rating; DL trust is the number of trusted device logins; DL all is the total number of device attempts; DL new is the number of attempts for new devices; Level device is the device security level, which takes a value of 0 or 1 depending on whether the device has passed secondary verification; μ1, μ2, and μ3 represent the weights of device consistency, security, and new device use, respectively, and the sum is 1;
[0127] Login request information includes: geographic location matching times, time matching times, network matching times, and total request times;
[0128] The calculation formula for the login request score is:
[0129]
[0130] ; Among them, S request is the login request score; R all is the total number of requests; Match address is the number of geographic location matches; Match time is the number of time matches; Match net is the number of network matches; φ1, φ2, and φ3 represent the weights of geographic location, time, and network characteristics, respectively, and the sum is 1;
[0131] The calculation formula for the new login trust is:
[0132] TrustScore=(α·S Behavior +β·S Device +γ·S request )*σ; where TrustScore
[0133] is the newly added login trust; α, β, and γ represent the weights of the historical behavior score, device behavior score, and login request score, respectively, and the sum is 1; σ represents the penalty coefficient, which is used to reduce the trust in specific situations;
[0134] Among them, the calculation formula of the penalty coefficient σ is: Among them, WA represents the current number of abnormal behaviors; WA all Represents the total number of abnormal behaviors recorded by the system; ρ is the penalty factor, ranging from 0 to 0.5.
[0135] Specifically, the multi-dimensional and multi-faceted considerations of the historical behavior score, device behavior score, and login request score are revised according to the actual situation in combination with the corresponding weights, which can more comprehensively reflect the current situation of the new login request, and thus more accurately judge whether it is credible; further, the introduction of penalty coefficients and penalty factors can reduce trust in the account when it has or has had abnormal behaviors such as abnormal address migration, blacklist entry, and high-risk operation behavior, reduce the occurrence of mistaken login, and improve login security while avoiding waste of resources.
[0136] In one embodiment, based on the new login trust and the new login feasibility, determining a login request processing strategy includes:
[0137] Set a trust threshold, and classify new login requests into trusted, untrusted, and conditionally trusted based on the trust threshold and the trust level of new logins.
[0138] Set a feasible threshold, and classify system login requests into feasible, infeasible, and conditionally feasible based on the feasible threshold and the feasibility of login addition;
[0139] When the new login request is trustworthy and the system login request is feasible, the selected login request processing policy is to allow login;
[0140] When the new login request is trustworthy but the system login new request is not feasible, the selected login request processing strategy is to deny login;
[0141] When the new login request is trusted but the system login new request conditions are feasible, the selected login request processing strategy is to join the waiting queue;
[0142] When the newly added login request is untrustworthy, the selected login request processing strategy is to deny login;
[0143] When the newly added login request condition is trusted and the system login new request is feasible or the condition is feasible, the selected login request processing strategy is to add it to the waiting queue;
[0144] When the newly added login request condition is trusted and the system login new request condition is not feasible, the selected login request processing strategy is to reject the login.
[0145] In one of the embodiments, the division of the newly added login request specifically includes:
[0146] Set the theoretical parameter of the newly added login trust degree to obtain the theoretical maximum trust degree, denoted as T MAX ;
[0147] Set the trust threshold parameters a1 and a2, where a1 < a2; a1 is preferably 0.5 and a2 is preferably 0.7;
[0148] When the newly added login trust degree satisfies TrustScore < a1·T MAX then the newly added login request is divided into untrusted;
[0149] When the newly added login trust degree satisfies a1·T MAX ≤TrustScore < a2·T MAX then the newly added login request is divided into conditionally trusted;
[0150] When the newly added login trust degree satisfies a2·T MAX ≤TrustScore, then the newly added login request is divided into trusted.
[0151] In one of the embodiments, the division of the system login new request specifically includes:
[0152] Set the theoretical parameter of the login new feasibility to obtain the theoretical maximum feasibility, denoted as F MAX ;
[0153] Set the feasibility threshold parameters b1 and b2, where b1 < b2; b1 is preferably 0.6 and b2 is preferably 0.8;
[0154] The login new feasibility is denoted as FeasibleScore. When the login new feasibility FeasibleScore < b1·F MAX then the newly added login request is divided into feasible;
[0155] When the login new feasibility satisfies b1·F MAX ≤FeasibleScore < b2·F MAX then the system login new request is divided into conditionally feasible;
[0156] When the feasibility of adding new logins meets b2·F MAX ≤FeasibleScore, the system login request is classified as feasible.
[0157] It is worth noting that, according to the actual situation, by modifying the trust threshold parameters a1, a2 and the feasible threshold parameters b1, b2, the size of the trust threshold and the feasible threshold can be adjusted, thereby controlling the capacity of the login waiting queue.
[0158] Specifically, comprehensive consideration of the trust of new logins and the feasibility of new logins makes the processing decision of login requests more comprehensive and reasonable, which not only ensures the security of the system but also takes into account the login needs of users; at the same time, by setting different trust thresholds and feasibility thresholds, the system can flexibly respond to login requests in different situations. For example, requests with high trust but tight system resources can be added to the waiting queue; in addition, by optimizing the processing strategy, the system can process login requests more efficiently and reduce unnecessary waiting time and system resource consumption, which can not only improve the user experience, but also protect the system from potential security threats.
[0159] In one embodiment, after adding the new login request of the account to the login waiting queue, it is managed through the following steps, including:
[0160] Step 301, log in to wait for queue priority evaluation.
[0161] Specifically, the trust level when the newly added login request enters the login waiting queue is recorded as the initial trust level T0;
[0162] Specifically, as the waiting time and user security behavior increase, additional trust is added to the new login request, denoted as T add , where the additional trust satisfies the formula: T add =kt1×log(ω wait ×t)+k2×V+k3×A, where t is the waiting time, V is the secondary verification status, V=1 when the verification is successful, otherwise it is 0, A is the other verification or activity score, ranging from 0 to 1, k1, k2, k3 are the corresponding weight coefficients, which are adjusted according to system requirements, ω wait is the waiting time influencing factor;
[0163] Specifically, the comprehensive trust of the newly added login request is calculated, where the comprehensive trust is denoted as T total , satisfying the formula: T total =T0+T add .
[0164] Step 302: queue sorting.
[0165] Specifically, each request entering the queue is sorted according to its comprehensive trust, and the initial arrangement order is determined by the T0 value. At the same time, the priority is adjusted dynamically, the comprehensive trust is updated regularly, and the queue is re-sorted according to the new trust.
[0166] Step 303, request processing.
[0167] Specifically, based on the current system resource status, the highest priority request in the queue is processed; further, when system resources permit, requests are processed in batches according to the level of comprehensive trust to ensure system stability and efficiency.
[0168] Specifically, when a new request for system login is in an infeasible state, all requests wait and continue to increase additional trust; when a new request for system login is in a feasible state, it is processed in sequence according to the comprehensive trust ranking to ensure the rational use of resources.
[0169] It is worth noting that when the system login request is in a conditionally feasible state, the screening comprehensive trust exceeds the high trust threshold T high Requests from the system are given priority processing; at this time, the system priority processing steps include but are not limited to querying the status of the current online account and forcibly logging off accounts that have not generated any operations within a certain period of time, modifying the account online limit, and releasing system redundant resources.
[0170] Among them, for the high confidence threshold T high The setting is based on the formula: Among them, T max is the theoretical maximum trust; L c is the system load factor; R u is the system resource utilization; T mean is the average trust of all login requests in the current system; Φ is the standard deviation of the trust distribution; ε is the weight parameter of the trust, which determines the theoretical maximum trust T max The ratio of the influence of the current trust distribution in the threshold setting is preferably 0.5-0.9; θ is the load adaptation factor, which is used to adjust the influence of the system load factor, preferably 0.1-0.5; τ is the influence factor of resource utilization, which is used to adjust the influence of system resource utilization, preferably 0.1-0.5; It is a dynamic adjustment factor used to dynamically balance system load and user experience, preferably 0.9-1.1.
[0171] Specifically, for a high confidence threshold T highThe setting can take into account the current resource utilization and system load factor of the system, ensuring that the high trust threshold is increased under high load conditions to reduce resource consumption and avoid congestion caused by processing too many login requests; further, combined with the maximum trust and the current trust distribution, it ensures that an appropriate high trust threshold is set when the trust of most requests is high; in addition, under high load conditions, the system burden is reduced by raising the threshold, and at the same time, users are provided with a way to improve their trust, thereby optimizing the user experience.
[0172] Specifically, by introducing additional trust and dynamic priority management mechanisms, the login queue management method can effectively schedule requests when system resources are tight, ensuring security and user experience: this method can ensure the security of the system and improve the user experience in scenarios where multiple users log in concurrently, and achieve efficient management and reasonable scheduling of login requests.
[0173] In one embodiment, according to the determined login request processing strategy, the system recognition degree of the account is evaluated to obtain the system recognition degree of the account; based on the system recognition degree of the account, the login setting parameters are modified;
[0174] Wherein, according to the determined login request processing strategy, the system recognition evaluation of the account further includes:
[0175] Obtain several login request processing policies determined by the account. When the determined login request processing policy is to allow login and the newly added login request is in a trusted state, it is recorded as a trust event.
[0176] According to the number of trust events, the account system recognition is calculated based on the formula:
[0177] Among them, Score satisfaction is the system recognition, Event represents the trust event, and N is the total number of trust events.
[0178] Specifically, based on the historical performance of the account, personalized login settings can be provided for different accounts. For example, for accounts with low recognition, by lowering their online upper limit or adding other security restrictions, security risks can be reduced and the security of the system and other users can be protected. At the same time, through dynamic adjustment of the system recognition, the system can adjust the login setting parameters as the account behavior changes, so that it can respond to various situations more flexibly. In addition, the feedback mechanism for adjusting the login setting parameters established in this way can guide users to improve their login behavior and improve the recognition of their accounts, so that they can enjoy more system permissions and services, which not only optimizes the user experience, but also facilitates orderly login when the same account logs in concurrently.
[0179] It should be understood that although Figure 2The steps in the flowchart are shown in sequence as indicated by the arrows, but these steps are not necessarily executed in the order indicated by the arrows. Unless otherwise specified in this document, there is no strict order restriction for the execution of these steps, and these steps can be executed in other orders. Moreover, Figure 2 At least part of the steps may include multiple sub-steps or multiple stages. These sub-steps or stages are not necessarily executed at the same time, but can be executed at different times. The execution order of these sub-steps or stages is not necessarily sequential, but can be executed in turn or alternately with other steps or at least part of the sub-steps or stages of other steps.
[0180] In one embodiment, Figure 4 As shown, a device for concurrent login of the same account is provided, including a login module, a trust evaluation module, an account online query module, a feasibility evaluation module, a request processing module, a recognition evaluation module, and an optimization and correction module, wherein:
[0181] The login module is used to accept new login requests for accounts and obtain new login request parameters;
[0182] A trust evaluation module, used to perform a trust evaluation based on the newly added login request parameters and generate a newly added login trust;
[0183] An account online query module is used to query the status of the associated accounts of the account and obtain the current online number of the account;
[0184] A feasibility evaluation module is used to obtain the account's login setting parameters and system status information, perform feasibility evaluation based on the current number of online users of the account, and generate a login new feasibility;
[0185] A request processing module, configured to select a corresponding login request processing strategy for the new login request according to the new login trust and the new login feasibility;
[0186] An approval evaluation module, used to evaluate the system approval of the account according to the determined login request processing strategy;
[0187] The optimization and correction module is used to modify the login setting parameters according to the system recognition of the account.
[0188] In one embodiment, the device login module is used to accept a new login request for an account and obtain new login request parameters; wherein the new login request parameters include account history login information, device behavior information, and login request information.
[0189] In one embodiment, the device trust evaluation module is used to obtain new login request parameters, which include: account history login information, device behavior information and login request information; used to obtain account history login information, perform account history trust evaluation, and obtain a historical behavior score; used to obtain device behavior information, perform device trust evaluation, and obtain a device score; used to obtain login request information, perform request trust evaluation, and obtain a login request score; used to perform a comprehensive trust evaluation based on the historical behavior score, device score, and login request score to obtain a new login trust.
[0190] In one embodiment, the feasibility assessment module of the device is used to obtain login setting parameters, which include an online upper limit for an account and a login retention margin; to obtain system status information, which includes a total number of online system accounts, an online upper limit for system accounts, a system load, and a maximum system load; to obtain an online account utilization rate based on the current number of online accounts, the login retention margin, and the online upper limit for an account, to obtain a system resource utilization rate based on the total number of online system accounts and the online upper limit for system accounts, and to obtain a system load coefficient based on the system load and the maximum system load; and to obtain a login-added feasibility rate based on the online account utilization rate, the system resource utilization, and the system load coefficient.
[0191] In one embodiment, the device request processing module is used to determine the login request processing strategy based on the new login trust and the new login feasibility; wherein, a trust threshold is set, and the new login request is divided into trusted, untrusted, and conditionally trusted based on the trust threshold and the new login trust; wherein a feasible threshold is set, and the system login new request is divided into feasible, unfeasible, and conditionally feasible based on the feasible threshold and the login new feasibility; wherein the selectable login request processing strategies include: A. When the new login request is trustworthy and the system login new request is feasible, the selected login request processing strategy is to allow login; B. When When the new login request is trusted but the new system login request is not feasible, the selected login request processing policy is to reject login; C. When the new login request is trusted but the system login request is feasible, the selected login request processing policy is to join the waiting queue; D. When the new login request is not trusted, the selected login request processing policy is to reject login; E. When the new login request condition is trusted and the system login request is feasible or the condition is feasible, the selected login request processing policy is to join the waiting queue; F. When the new login request condition is trusted and the system login request is not feasible, the selected login request processing policy is to reject login.
[0192] In one embodiment, the device recognition evaluation module is used to perform system recognition evaluation on the account according to the determined login request processing strategy to obtain the system recognition of the account.
[0193] In one embodiment, the device optimizes and modifies a module for obtaining the system recognition of an account and modifying login setting parameters according to the system recognition of the account.
[0194] For the specific definition of the device for concurrent login of the same account, please refer to the definition of the method for concurrent login of the same account above, which will not be repeated here. Each module in the above-mentioned device for concurrent login of the same account can be implemented in whole or in part by software, hardware and a combination thereof. The above-mentioned modules can be embedded in or independent of the processor in the computer device in the form of hardware, or can be stored in the memory of the computer device in the form of software, so that the processor can call and execute the operations corresponding to the above modules.
[0195] In one embodiment, a computer device is provided. The computer device may be a server, and its internal structure diagram may be as follows: Figure 5 As shown. The computer device includes a processor, a memory, a network interface and a database connected through a system bus. Among them, the processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program and a database. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The database of the computer device is used to store system status information and account login setting parameter information data. The network interface of the computer device is used to communicate with an external terminal through a network connection. When the computer program is executed by the processor, a method for concurrent login of the same account is implemented.
[0196] Those skilled in the art will understand that Figure 5 The structure shown in the figure is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied. The specific computer device may include more or fewer components than those shown in the figure, or combine certain components, or have a different arrangement of components.
[0197] In one embodiment, a computer device is provided, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the following steps when executing the computer program:
[0198] Receive a new login request from an account and obtain parameters of the new login request; perform a trust evaluation based on the parameters of the new login request to obtain the trust of the new login; obtain the current number of online users of the account; perform a feasibility evaluation based on the login setting parameters of the account, the current number of online users of the account and system status information to obtain the new login feasibility;
[0199] Based on the new login trust and the new login feasibility, a login request processing strategy is determined; wherein the login request processing strategy includes one of the following: allowing login, denying login, and adding to a login waiting queue.
[0200] In one embodiment, when the processor executes the computer program, the processor further implements the following steps:
[0201] Obtain login setting parameters, including the online upper limit of the account and the login retention margin; obtain system status information, including the total number of system accounts online, the online upper limit of the system accounts, the system load, and the maximum system load; obtain the account's login setting parameters, the current number of accounts online, and the system status information, and perform a feasibility assessment; wherein, according to the current number of accounts online, the login retention margin, and the online upper limit of the account, obtain the account online utilization rate; according to the total number of system accounts online and the online upper limit of the system accounts, obtain the system resource utilization rate; according to the system load and the maximum system load, obtain the system load coefficient; based on the account online utilization rate, the system resource utilization rate, and the system load coefficient, obtain the login added feasibility.
[0202] In one embodiment, when the processor executes the computer program, the processor further implements the following steps:
[0203] The calculation formula for account online utilization rate is: account online utilization rate = (number of accounts currently online + login retention balance) / (account online upper limit);
[0204] The calculation formula of system resource utilization is: system resource utilization = (total number of online system accounts) / (upper limit of online system accounts);
[0205] The calculation formula of system load factor is: system load factor = 1-(system load) / (system maximum load);
[0206] The calculation formula for the new login feasibility is: New login feasibility = (1-account online utilization rate) × system resource utilization rate × system load factor.
[0207] In one embodiment, when the processor executes the computer program, the following steps are also implemented: obtaining new login request parameters, the new login request parameters including: account history login information, device behavior information and login request information; obtaining account history login information, performing account history trust evaluation, and obtaining a history behavior score; obtaining device behavior information, performing device trust evaluation, and obtaining a device score; obtaining login request information, performing request trust evaluation, and obtaining a login request score; performing a comprehensive trust evaluation based on the history behavior score, device score, and login request score to obtain a new login trust.
[0208] In one embodiment, when the processor executes the computer program, the following steps are further implemented: obtaining historical account login information, the historical account login information includes: normal login times, total login times, abnormal behavior times, active days, and total usage days; the calculation formula for the historical behavior score is: Among them, S Behavior is the historical behavior score; L normal is the number of normal logins; L wrong is the number of abnormal behaviors; L all is the total number of logins; D active is the number of active days; D all is the total number of days of use; ω1, ω2, and ω3 represent the weights of login frequency, abnormal behavior, and activity, respectively, and the sum is 1;
[0209] Obtain device behavior information, including: trusted device login times, device security level, new device attempts, and total device attempts. The device behavior score is calculated as follows: Among them, S Device It is the equipment rating; DL trust is the number of trusted device logins; DL all is the total number of device attempts; DL new is the number of attempts for new devices; Level device is the device security level, which takes a value of 0 or 1 depending on whether the device has passed secondary verification; μ1, μ2, and μ3 represent the weights of device consistency, security, and new device use, respectively, and the sum is 1;
[0210] Get login request information, which includes: number of geographic location matches, number of time matches, number of network matches, and total number of requests; the calculation formula for login request score is: Among them, S request is the login request score; R all is the total number of requests; Match address is the number of geographic location matches; Match time is the number of time matches; Match net is the number of network matches; φ1, φ2, and φ3 represent the weights of geographic location, time, and network characteristics, respectively, and the sum is 1;
[0211] Calculate the new login trust, where the calculation formula for the new login trust is: TrustScore = (α·S Behavior +βvS Device +γ·S request)*σ; where TrustScore is the newly added login trust; α, β, and γ represent the weights of the historical behavior score, device behavior score, and login request score, respectively, and the sum is 1; σ represents the penalty coefficient, which is used to reduce the trust in a specific situation; where the penalty coefficient σ is calculated as follows: Among them, WA represents the current number of abnormal behaviors; WA all Represents the total number of abnormal behaviors recorded by the system; ρ is the penalty factor, ranging from 0 to 0.5.
[0212] In one embodiment, when the processor executes the computer program, the following steps are also implemented: determining a login request processing strategy based on the newly added login trust and the newly added login feasibility; wherein, a trust threshold is set, and based on the trust threshold and the newly added login trust, the newly added login request is divided into trusted, untrusted, and conditionally trusted; wherein, a feasible threshold is set, and based on the feasible threshold and the newly added login feasibility, the newly added system login request is divided into feasible, unfeasible, and conditionally feasible; wherein, the selectable login request processing strategies include: A. when the newly added login request is trustworthy and the newly added system login request is feasible, the selected login request processing strategy is to allow login; B. When the new login request is trustworthy but the new system login request is not feasible, the selected login request processing strategy is to reject login; C. When the new login request is trustworthy but the system login request is feasible, the selected login request processing strategy is to join the waiting queue; D. When the new login request is not trustworthy, the selected login request processing strategy is to reject login; E. When the new login request condition is trustworthy and the system login request is feasible or the condition is feasible, the selected login request processing strategy is to join the waiting queue; F. When the new login request condition is trustworthy and the system login request is not feasible, the selected login request processing strategy is to reject login.
[0213] In one embodiment, when the processor executes the computer program, the following steps are further implemented: according to the determined login request processing strategy, the system recognition degree of the account is evaluated to obtain the system recognition degree of the account; based on the system recognition degree of the account, the login setting parameters are modified; wherein, according to the determined login request processing strategy, the system recognition degree of the account is evaluated further including: obtaining several login request processing strategies determined by the account, when the determined login request processing strategy is to allow login, and the newly added login request is in a trusted state, it is recorded as a trust event; according to the number of trust events, the system recognition degree of the account is calculated based on the formula: Among them, Score satisfaction is the system recognition, Event represents the trust event, and N is the total number of trust events.
[0214] In one embodiment, a computer readable storage medium is provided, on which a computer program is stored, and when the computer program is executed by a processor, the following steps are implemented:
[0215] Receive a new login request from an account and obtain parameters of the new login request; perform a trust evaluation based on the parameters of the new login request to obtain the trust of the new login; obtain the current number of online users of the account; perform a feasibility evaluation based on the login setting parameters of the account, the current number of online users of the account and system status information to obtain the new login feasibility;
[0216] Based on the new login trust and the new login feasibility, a login request processing strategy is determined; wherein the login request processing strategy includes one of the following: allowing login, denying login, and adding to a login waiting queue.
[0217] Those skilled in the art can understand that all or part of the processes in the above-mentioned embodiment methods can be completed by instructing the relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to memory, storage, database or other media used in the embodiments provided in this application can include non-volatile and / or volatile memory. Non-volatile memory can include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM) or flash memory. Volatile memory can include random access memory (RAM) or external cache memory. As an illustration and not limitation, RAM is available in many forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous link (Synchlink) DRAM (SLDRAM), memory bus (Rambus) direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM).
[0218] The technical features of the above embodiments may be combined arbitrarily. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.
[0219] The above-mentioned embodiments only express several implementation methods of the present application, and the descriptions thereof are relatively specific and detailed, but they cannot be understood as limiting the scope of the invention patent. It should be pointed out that, for a person of ordinary skill in the art, several variations and improvements can be made without departing from the concept of the present application, and these all belong to the protection scope of the present application. Therefore, the protection scope of the patent of the present application shall be subject to the attached claims.
Claims
1. A method for concurrent login of the same account, characterized in that: include: Receive a new login request from an account and obtain the new login request parameters; Perform a trust evaluation based on the newly added login request parameters to obtain the newly added login trust; Get the current number of online accounts; Perform a feasibility assessment based on the account login setting parameters, the current number of online accounts and system status information to obtain a login new feasibility; Based on the new login trust and the new login feasibility, a login request processing strategy is determined; wherein the login request processing strategy includes one of the following: allowing login, refusing login, and adding to a login waiting queue.
2. A method for concurrent login of the same account according to claim 1, characterized in that: The login setting parameters include the account online limit and login retention margin; The system status information includes the total number of online system accounts, the upper limit of online system accounts, system load, and maximum system load; Obtaining the login setting parameters of the account, the current number of online users of the account, and system status information, and performing feasibility assessment includes: Obtaining an account online utilization rate according to the current number of online accounts, the login retention balance and the account online upper limit; Obtaining system resource utilization according to the total number of online system accounts and the upper limit of online system accounts; Obtaining a system load factor according to the system load and the system maximum load; The feasibility of the new login is obtained based on the online utilization rate of the account, the utilization rate of the system resources, and the system load factor.
3. A method for concurrent login of the same account according to claim 2, characterized in that: The calculation formula of the account online utilization rate is: account online utilization rate = (current number of accounts online + login retention balance) / (account online upper limit); The calculation formula of the system resource utilization is: system resource utilization = (total number of online system accounts) / (upper limit of online system accounts); The calculation formula of the system load factor is: system load factor = 1 - (system load) / (system maximum load); The calculation formula of the new login feasibility is: new login feasibility = (1-account online utilization rate) × system resource utilization rate × system load factor.
4. A method for concurrent login of the same account according to claim 1, characterized in that: The newly added login request parameters include: account history login information, device behavior information and login request information; According to the newly added login request parameters, the trust evaluation includes: Obtain the historical login information of the account, conduct a historical trustworthiness assessment of the account, and obtain a historical behavior score; Obtaining the device behavior information, performing device trust evaluation, and obtaining a device score; Obtaining the login request information, performing a request trustworthiness assessment, and obtaining a login request score; A comprehensive trust evaluation is performed based on the historical behavior score, the device score, and the login request score to obtain a newly added login trust.
5. A method for concurrent login of the same account according to claim 4, characterized in that: The account login history information includes: normal login times, total login times, abnormal behavior times, active days, and total usage days; The calculation formula of the historical behavior score is: ; Among them, S Behavior is the historical behavior score; L normal is the number of normal logins; L wrong is the number of abnormal behaviors; L all is the total number of logins; D active is the number of active days; D all is the total number of days of use; ω1, ω2, and ω3 represent the weights of login frequency, abnormal behavior, and activity, respectively, and the sum is 1; The device behavior information includes: the number of trusted device logins, device security level, the number of new device attempts, and the total number of device attempts; The calculation formula of the device behavior score is: ; Among them, S Device It is the equipment rating; DL trust is the number of trusted device logins; DL all is the total number of device attempts; DL new is the number of attempts for new devices; Level device is the device security level, which takes a value of 0 or 1 depending on whether the device has passed secondary verification; μ1, μ2, and μ3 represent the weights of device consistency, security, and new device use, respectively, and the sum is 1; The login request information includes: the number of geographic location matches, the number of time matches, the number of network matches, and the total number of requests; The calculation formula of the login request score is: ; Among them, S request is the login request score; R all is the total number of requests; Match address is the number of geographic location matches; Match time is the number of time matches; Match net is the number of network matches; φ1, φ2, and φ3 represent the weights of geographic location, time, and network characteristics, respectively, and the sum is 1; The calculation formula of the newly added login trust is: TrustScore = (α·S Behavior + β·S Device + γ·S request ) * σ; where, TrustScore is the newly added login trust; α, β, and γ represent the weights of the historical behavior score, device behavior score, and login request score, respectively, and the sum is 1; σ represents the penalty coefficient, which is used to reduce the trust in specific situations; Among them, the calculation formula of the penalty coefficient σ is: Among them, WA represents the current number of abnormal behaviors; WA all Represents the total number of abnormal behaviors recorded by the system; ρ is the penalty factor, ranging from 0 to 0.
5.
6. A method for concurrent login of the same account according to claim 1, characterized in that: Determining a login request processing strategy based on the new login trust and the new login feasibility includes: Setting a trust threshold, and classifying the newly added login request as trusted, untrusted, or conditionally trusted based on the trust threshold and the newly added login trust level; Setting a feasible threshold, and classifying the system login request into feasible, infeasible, and conditionally feasible based on the feasible threshold and the login feasibility; When the new login request is trustworthy and the system login request is feasible, the selected login request processing policy is to allow login; When the new login request is trustworthy but the system login new request is not feasible, the selected login request processing strategy is to deny login; When the new login request is trusted but the system login new request conditions are feasible, the selected login request processing strategy is to join the waiting queue; When the newly added login request is untrustworthy, the selected login request processing strategy is to deny login; When the new login request condition is trusted and the system login new request is feasible or the condition is feasible, the selected login request processing strategy is to join the waiting queue; When the newly added login request conditions are trusted and the system login newly added request conditions are not feasible, the selected login request processing strategy is to deny login.
7. A method for concurrent login of the same account according to claim 6, characterized in that: Also includes: According to the determined login request processing strategy, the system recognition degree of the account is evaluated to obtain the system recognition degree of the account; Based on the account system recognition, modify the login setting parameters; Wherein, according to the determined login request processing strategy, performing system recognition evaluation on the account further includes: Acquire the plurality of login request processing policies determined by the account, and when the determined login request processing policy is to allow login and the newly added login request is in a trusted state, record it as a trust event; According to the number of trust events, the account system recognition is calculated based on the formula: Among them, Score satisfaction is the system recognition, Event represents the trust event, and N is the total number of trust events.
8. A device for concurrent login of the same account, characterized in that: The device comprises: The login module is used to accept new login requests for accounts and obtain new login request parameters; A trust evaluation module, used to perform a trust evaluation based on the newly added login request parameters and generate a newly added login trust; An account online query module is used to query the status of the associated accounts of the account and obtain the current online number of the account; A feasibility evaluation module is used to obtain the account's login setting parameters and system status information, perform feasibility evaluation based on the current number of online users of the account, and generate a login new feasibility; A request processing module, configured to select a corresponding login request processing strategy for the new login request according to the new login trust and the new login feasibility; An approval evaluation module, used to evaluate the system approval of the account according to the determined login request processing strategy; The optimization and correction module is used to modify the login setting parameters according to the system recognition of the account.
9. A computer device comprising a memory, a processor and a computer program stored in the memory and executable on the processor, characterized in that: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 7 are implemented.
10. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 7 are implemented.
Citation Information
Patent Citations
Login verification method and device, equipment and storage medium
CN113194079A
Online login equipment management method and device and electronic equipment
CN113591068A
Multi-device simultaneous login management method and system, electronic device and storage medium
CN115186249A
Method and device for logging in multiple devices with same account, medium and device
CN116208388A
Online system and access control method
JP2010044633A
Cited By
Resource-isolated ubiquitous operating system reinforcing method and system
CN120579178A
