WO2019071997A1 - 账号资源共享方法、系统、设备和计算机可读存储介质 - Google Patents

账号资源共享方法、系统、设备和计算机可读存储介质 Download PDF

Info

Publication number
WO2019071997A1
WO2019071997A1 PCT/CN2018/097910 CN2018097910W WO2019071997A1 WO 2019071997 A1 WO2019071997 A1 WO 2019071997A1 CN 2018097910 W CN2018097910 W CN 2018097910W WO 2019071997 A1 WO2019071997 A1 WO 2019071997A1
Authority
WO
WIPO (PCT)
Prior art keywords
account
user
original
preset
meets
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/CN2018/097910
Other languages
English (en)
French (fr)
Inventor
胡文松
刘振
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
BOE Technology Group Co Ltd
Hefei Xinsheng Optoelectronics Technology Co Ltd
Original Assignee
BOE Technology Group Co Ltd
Hefei Xinsheng Optoelectronics Technology Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by BOE Technology Group Co Ltd, Hefei Xinsheng Optoelectronics Technology Co Ltd filed Critical BOE Technology Group Co Ltd
Priority to US16/329,350 priority Critical patent/US11210284B2/en
Publication of WO2019071997A1 publication Critical patent/WO2019071997A1/zh
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/10—Network architectures or network communication protocols for network security for controlling access to devices or network resources
    • H04L63/108—Network architectures or network communication protocols for network security for controlling access to devices or network resources when the policy decisions are valid for a limited amount of time
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/23—Updating
    • G06F16/2379—Updates performed during online database operations; commit processing
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/90—Details of database functions independent of the retrieved data types
    • G06F16/95—Retrieval from the web
    • G06F16/953—Querying, e.g. by the use of web search engines
    • G06F16/9535—Search customisation based on user profiles and personalisation
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/21—Design, administration or maintenance of databases
    • G06F16/219—Managing data history or versioning
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/24—Querying
    • G06F16/245—Query processing
    • G06F16/2457—Query processing with adaptation to user needs
    • G06F16/24578—Query processing with adaptation to user needs using ranking
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/30—Information retrieval; Database structures therefor; File system structures therefor of unstructured textual data
    • G06F16/33—Querying
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/60—Information retrieval; Database structures therefor; File system structures therefor of audio data
    • G06F16/68—Retrieval characterised by using metadata, e.g. metadata not derived from the content or metadata generated manually
    • G06F16/686—Retrieval characterised by using metadata, e.g. metadata not derived from the content or metadata generated manually using information manually generated, e.g. tags, keywords, comments, title or artist information, time, location or usage information, user ratings
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/10—Network architectures or network communication protocols for network security for controlling access to devices or network resources
    • H04L63/102—Entity profiles
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/535—Tracking the activity of the user
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/10—Office automation; Time management
    • G06Q10/105—Human resources
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q30/00—Commerce
    • G06Q30/018—Certifying business or products

Definitions

  • the disclosed account resource sharing method, system, device and computer readable storage medium are disclosed.
  • a method for sharing an account resource including: acquiring an account of an original user that meets a preset collection condition; and saving user information of an original user that meets a preset collection condition to a resource library, The account of the original user that meets the preset collection condition is added to the assignable account database; and the request for the user to allocate the account is received, and the account is assigned to the application user from the assignable account database.
  • the acquiring an account of the original user that meets the preset collection condition includes: obtaining a frequency of use of the original user's account and/or a duration of use, determining whether the frequency of use and/or the duration of use meets a preset collection condition, If yes, the original user's account number is marked as the original user's account that reaches the preset recycling condition.
  • the obtaining the usage frequency and/or the usage duration of the original user's account includes: periodically querying the usage frequency and/or the usage duration of the original user's account to obtain the account of the original user that meets the preset collection condition. Or the original user's account frequency and/or usage duration meets the preset recycling conditions, and is automatically marked as the original user's account that meets the preset recycling conditions.
  • the acquiring an account of the original user that meets the preset collection condition includes: obtaining a list of the original user's account that meets the preset candidate recovery condition; and ranking the account number in the account list according to the frequency of use, and the frequency of use The low account is used as the account of the original user who meets the preset recycling conditions.
  • the method includes: reading the current usage duration and the historical usage duration of the original user, and calculating the next usage duration to save to the original user information. .
  • the method before adding the account of the original user that meets the preset collection condition to the assignable account database, the method includes: sending a notification message to the original user.
  • the method before adding the account of the original user that meets the preset collection condition to the assignable account database, the method includes: determining whether the account of the original user is in use; and if not, the original user that meets the preset collection condition. The account is added to the assignable account library.
  • the method includes: determining whether the user information corresponding to the application user exists in the resource library; if yes, assigning the account to the application user The user information associated with the application user saved in the repository is associated.
  • the user information includes an identification ID of the user
  • the request for the user to allocate an account includes the identification ID of the application user
  • the content of the user corresponding to the application user is determined in the resource library.
  • the method includes: comparing the identification ID of the application user with the identification ID in the user information saved in the resource library to obtain user information corresponding to the identification ID of the application user.
  • the determining whether the user information corresponding to the application user exists in the resource library includes: determining whether the user information corresponding to the application user exists in the resource library; if not, matching the default for the application user. User information, and associate the account assigned to the requesting user with the default user information.
  • the user information includes one or more of a user's identification ID, historical usage duration, current usage duration, next usage duration, usage frequency, user rights, and favorite information.
  • the method further includes: counting and outputting one or more of account information of the associated user information, account information in the assignable account library, and user information saved in the resource library.
  • an account resource sharing system including: an obtaining module configured to acquire an account of an original user that meets a preset recycling condition; and a recycling module configured to satisfy a preset recycling
  • the user information of the original user of the condition is saved to the resource library, and the account of the original user that meets the preset recycling condition is added to the account that can be allocated to the account;
  • the allocation module is configured to receive the request for the user to allocate the account, and the account is available in the account database.
  • the application user assigns an account.
  • a computer readable storage medium having stored thereon a computer program, the computer program executing the steps of implementing the account resource sharing method of any of the foregoing.
  • an apparatus for sharing account resources comprising a computer readable storage medium, a processor, and a computer program stored on the computer readable storage medium and executable on the processor; The step of implementing the account resource sharing method according to any one of the preceding claims when the processor executes the computer program.
  • FIG. 1 is a schematic flowchart diagram of an embodiment of an account resource sharing method according to at least one embodiment of the present disclosure
  • FIG. 2 is a schematic flowchart diagram of an embodiment of an account resource sharing method according to at least one embodiment of the present disclosure
  • FIG. 3 is a schematic flowchart diagram of still another embodiment of an account resource sharing method according to at least one embodiment of the present disclosure
  • FIG. 4 is a schematic diagram of an account resource sharing system according to at least one embodiment of the present disclosure.
  • the embodiments of the present disclosure aim to solve the problem that the actual utilization rate of some low-frequency account accounts is too low, and in particular, the problem of improving the utilization rate of the account by recycling the account and saving the user information in each of the collected accounts is solved.
  • an account resource sharing method is proposed. Referring to the flow diagram shown in FIG. 1, the method includes the following steps.
  • step S10 an account of the original user that satisfies the preset collection condition is acquired.
  • step S20 the user information of the original user that meets the preset collection condition is saved to the resource library, and the account of the original user that meets the preset collection condition is added to the assignable account database.
  • step S30 a request for the user to allocate an account is received, and an account is allocated to the application user from the assignable account database.
  • the account of the original user that satisfies the preset collection condition is obtained in step S10, for example, the account of the original user is an account that has been assigned to a specific user, and the account is associated with the user information of the specific user, and is used according to the actual use of the specific user.
  • the situation continues to update user information.
  • the preset recovery condition may be a unified preset account recovery condition of the system, or may be a separate collection condition for a specific account or a user; or, according to the user's own use of the account and the use of the account in the entire system, self-intelligent Adjusted recycling conditions.
  • the account of the original user who obtains the preset recovery condition can be obtained through a timed task, and the frequency of using the system account is periodically collected, updated, and counted, so that the low frequency account meeting the preset condition can be recycled to the assignable account database;
  • the timed scan can allocate the usage of the account in the account database, and the allocated time and the collection time of each allocated account can be stored in the account database to recover the account that reaches the preset usage time; or, the user reaches the preset recovery condition.
  • step S20 the user information of the original user that meets the preset collection condition is saved to the resource library, and adding the account of the original user that meets the preset collection condition to the assignable account database may include, for example, when the actual usage of the account satisfies the preset.
  • the condition is reclaimed, the user information associated with the original user's account will be saved to the specified resource library for subsequent calls; then the account is added to the assignable account database; the account in the assignable account library is not associated with the user information. Only when the account is assigned to a specific user, it is associated with the user information of the user.
  • the account of the original user is the account of the financial reimbursement user of the department shared by multiple people, and the specific recycling condition can be preset for it to avoid confusion after the recycling; if the user is in the state of resignation or other state that it is impossible to apply for the account again, It can be determined that the user information is directly deleted to save the space of the resource library and optimize the subsequent information search speed; the resource library can also set the function of regularly cleaning redundant user information to optimize system efficiency.
  • the two sub-steps in the step S20 can be changed to the order, that is, the step S20 can also include: adding the account of the original user that meets the preset collection condition to the assignable account database, and saving the user information of the original user that meets the preset collection condition to Resource library; does not affect the implementation of the technical solution of the present disclosure.
  • step S30 a request for the user to allocate an account is received, and the account is allocated to the application user from the assignable account database, for example, the application user may be a new user who has never applied for an account, or may be an original user who has reclaimed the account.
  • the request for assigning an account may include information such as user rights and duration of the application account to match an appropriate account from the assignable account database.
  • the recovered account can be reassigned to the new applicant.
  • the request for assigning the account may also include a request for associating the user information of the original user, so as to obtain the user information of the original user as soon as possible, and reduce the search waiting time.
  • the disclosure also proposes another embodiment for the user who has reclaimed the account to re-apply for the account, so that the user who applies for the account again can read the previously saved user information, which is convenient for the user to use and improve work efficiency.
  • the solution may include: after the account is allocated to the application user in the self-allocable account database, the method further includes: in step S40, determining whether the user information corresponding to the application user exists in the resource library; And, the account number assigned to the application user is associated with the user information corresponding to the application user saved in the resource library.
  • the application user can select whether to be a new user or the original user when requesting to allocate an account. If the application user confirms to be a new user, no matching search is needed, and if the application user confirms the original user, Further guide the application user to input the time range of the last application account, or the time range in which the account is recycled, to improve the search matching speed in the resource library, and save the time for applying for the account.
  • the application user has a record of using the account, and the user information corresponding to the application user stored in the resource library is associated with the account assigned to the application user. So that users can read the previous usage information and improve user productivity.
  • the user's account when the account is collected, the user's account is separated from the user's user information, and the user's personal information can be saved, so that the next time the application is read, the account can be re-allocated to improve the account usage rate. .
  • the present disclosure further provides another embodiment.
  • a criterion for determining a preset recovery condition is set: the acquiring the original user that meets the preset collection condition.
  • the method of the account number may include the following steps.
  • step S11 the usage frequency and/or the usage duration of the original user's account is obtained, and it is determined whether the usage frequency and/or the usage duration meet the preset collection condition. If yes, the original user's account number is marked as the original recovery condition. User's account.
  • Step S11 may include, for example, the following three steps.
  • step S111 the usage frequency and/or the length of use of the original user's account is obtained, and it is determined whether the frequency of use and/or the length of use meets the preset recovery condition; if yes, step S112 is performed; if not, step S113 is performed;
  • step S112 the original user's account number is marked as the original user's account number that reaches the preset collection condition.
  • step S113 no processing is performed.
  • the pre-recovered account is generally a low-frequency account, or an account that reaches the specified usage time.
  • a certain time task module can be set in the system for collecting and updating user information and account information. The module can perform two functions: one is timing statistics.
  • the preset usage duration of each account stored in the account resource pool is periodically scanned to recover the account that reaches the preset usage time. In order to avoid misjudgment, the frequency of use and the length of use can be combined to judge.
  • the user's preset usage time may be automatically extended, or the user may be reminded to issue an extended use time. Request, or remind the manager whether it is necessary to extend the user's default usage time.
  • step S112 is performed to mark the original user's account as the original recovery condition.
  • User's account After the marking is completed, referring to step S21 in FIG. 3, the user information of the original user that has reached the preset recycling condition is saved to the resource library, and the account of the original user that has reached the preset recycling condition is added to the assignable account database to complete the recycling step. If the original user whose subsequent account is reclaimed applies for the account again, the saved user information of the original user can be read from the resource library.
  • the embodiment of the present disclosure can enable the application user to quickly obtain the previous history information by reading the previous user information, thereby improving the work efficiency of the user.
  • step S113 in the case where the determination in the present disclosure is NO, no processing is performed. If the account is not processed, for example, the account may not be recovered, and the account or the user's usage may be continuously monitored; if the account is close to the recycling condition but has not reached the recycling condition, the account is not recovered and is sent to the user of the account. Reminder information so that users can predict the status of the account in time.
  • the method for obtaining the frequency of use and/or the duration of use of the account of the original user may be implemented by a system timed query, or when the user's account reaches a preset collection condition, the user actively broadcasts or uploads.
  • the technical solution includes the following two methods: periodically querying the usage frequency and/or duration of use of the original user's account to obtain the account of the original user that meets the preset collection condition; or, the frequency and/or use of the original user's account. If the duration meets the preset recycling conditions, it is automatically marked as the original user's account that meets the preset recycling conditions.
  • Both methods require preset recovery conditions. For example, if the account frequency is less than 30 days/time, the account number is used as the account that meets the recycling conditions; or, when the account is assigned, the longest use of the account is obtained.
  • the time is 100 days, up to 100 days, the account is used as the account that meets the recycling conditions.
  • the first type of timed query method can obtain more comprehensive account information, and can also set or modify the filtering query conditions according to specific conditions, and then confirm whether these accounts need to be recycled according to specific conditions.
  • the second method for automatically marking users is to actively broadcast or upload an account, and the system does not need to query one by one to improve the query efficiency; the system can confirm the account that needs to be recycled from the account that the user actively broadcasts or uploads, to avoid mis-recovery.
  • the two methods can automatically obtain the account of the original user that meets the preset recovery condition by using the preset recovery condition, without manual participation in screening.
  • the account in the account library can be allocated enough, the account recovery function can be cancelled; the frequency of use of the account can be sorted when the number of accounts is scarce, so that the account with lower frequency is directly used as an alternative.
  • Pre-reclaim accounts and then select the top ranked accounts from the alternate pre-recycling accounts for recycling.
  • the technical solution includes, for example, obtaining an account of an original user that meets a preset collection condition, including: obtaining a list of accounts of the original user that meets the preset candidate recovery condition; ranking the account number in the account list according to the frequency of use, and using the frequency
  • the low account is used as the account of the original user who meets the preset recycling conditions.
  • the account with low frequency of use can be the account with the lowest frequency of use in the account ranking. For example, through the comparison algorithm of the program, the account with the lowest frequency of use is found, and then the comparison algorithm is executed cyclically to obtain the lowest frequency of use. Account number; also according to the ranking, determine the average frequency of use of the account, and then use the account below the average frequency of use as the account with low frequency of use.
  • the embodiment shown in FIG. 3 is applicable to recovering an account lower than a preset frequency (other recovery conditions can also be preset), and ranking of user usage frequency.
  • This embodiment is suitable for recycling a specific number of accounts or specific accounts by using the frequency of use of the account as a reference.
  • the present embodiment provides another method for judging whether the account is reclaimed to compensate for the deficiencies of the embodiment shown in FIG.
  • the candidate's account list may be filtered out through specific conditions, and then According to the account usage frequency in the account list, the number of users with the lowest frequency is taken as the account of the original user who meets the preset recycling condition.
  • the method further includes: in step S12, reading the current usage duration and the historical usage duration of the original user, and calculating the next usage duration to save to the user of the original user. Information.
  • the calculation method may adopt an averaging method or a difference method, or may be combined with a user's use frequency as a reference for calculating the duration of use. For example, the current usage duration of the user who takes the pre-reclaimed account and the historical usage duration of the last two times are calculated, and the average usage duration is calculated as the usage duration when the user applies for the account next time; or, according to the usage frequency of the user, if the user frequency is reached A certain set value corresponds to a weighting parameter, and the average use duration is calculated and multiplied by the weight, for example, multiplied, and the operation result is saved as the usage duration of the user's next application account.
  • the usage time of the next application account calculated and saved is used as the preset usage time of the user's current application account; if the actual usage time of the user reaches the The default usage time is used to reclaim the account.
  • the average usage time or other time parameters it is also possible to refer to the historical usage duration of all the recovered accounts, not limited to the user's own usage time.
  • the frequency of use in the user preset collection condition when the frequency of use in the user preset collection condition is set, the frequency of use by the user may be calculated, and the frequency of use of all users in the resource library may be referred to, and whether the user's authority and the account number are public accounts are combined. And other factors as a reference.
  • the present disclosure also provides an embodiment. Before the account of the original user that meets the preset collection condition is added to the assignable account database, the embodiment includes sending a notification message to the original user in step S13.
  • the notification can be sent to the email associated with the user information by email, or sent to the mobile phone via SMS, or directly to the user by means of a reminder message to the user.
  • the content of the notification message may include a reminder to reclaim the account, a method of re-applying the account, how to re-apply the user information when re-applying the account, and a verification code of the associated user information.
  • the disclosure further provides that before the account of the original user that meets the preset collection condition is added to the account that can be allocated, the method includes: in step S14, determining the original user. Whether the account is in the use state; if not, the account of the original user who meets the preset recycling condition is added to the assignable account database.
  • the use status includes whether the user is currently logged in, whether the user currently has an account operation, Whether the user currently has an unfinished IT process status; for example, in an enterprise management system, an account recently initiated a reimbursement process, but the process is still in an intermediate audit state, and if the process is not completed, the account is still in use. Do not recycle this account. If the account is not currently used, the account is recycled to the assignable account library for subsequent distribution to other users.
  • the recovery condition such as the preset use duration or the preset use frequency
  • the disclosure further provides that the user information includes the user's identification ID, and the request for the user to allocate the account includes the identification ID of the application user; and whether the user corresponding to the application user exists in the judgment resource library.
  • the information includes: comparing the identification ID of the application user with the identification ID in the user information stored in the resource library to obtain user information corresponding to the identification ID of the application user.
  • the user's identification ID can be unique identification information such as the user's real name, ID number, job number, email address, mobile phone number, or the identification code or identity mark calculated by the unique identification information.
  • the corresponding verification code may be calculated for the identification ID, and the verification code is sent to the original user in the manner of the foregoing notification message; when the application user wants to obtain the user information or the user information and the account number
  • the application user may be required to input a corresponding verification code to ensure that the current application user and the original user to which the user information stored in the resource library belongs are the same user, or confirm that the current application user reads the user information or The operation of associating the user information with the account has been authorized by the original user.
  • the determining whether the user information corresponding to the application user exists in the resource library may further include: determining, in step S41, whether the user information corresponding to the application user exists in the resource library; if yes, Then, step S42 is performed, and if no, step S43 is performed.
  • step S42 if yes, the account number assigned to the application user is associated with the user information corresponding to the application user stored in the resource library.
  • step S43 if not, the application user is matched with the default user information, and the account assigned to the application user is associated with the default user information.
  • the application user is the original user, that is, the user who has applied for the old account before, when the old account is recycled, the user information of the original user will be stored in the resource library, and when the original user applies for a new account again, It can be searched from the resource library; if it is not found, it is judged that the application user is a new user, according to a preset rule, the new user is matched with the default user information, and the account assigned to the application user is associated with the default User information association; the default user information may include account information such as user rights, user usage time, and account application time, and may also include software setting information such as a system operation wizard and a default function interface; therefore, if the application user is the original user, It can not only read the original account information, but also read the information related to the original software settings, making the user's operation more convenient.
  • the present disclosure may include the following, in step S50, returning the associated account number and user information to the applicant user.
  • the review step or the verification step may be included to confirm that the returned account meets the system preset condition or other special conditions, and details are not described herein again.
  • the user information may include one of the user's identification ID, historical usage duration, current usage duration, next use duration, usage frequency, user rights, and favorite information. A variety. Certainly, the user information may further include the foregoing verification code, usage count, usage time, and the like.
  • the disclosure may also count and output one or more of the account information of the associated user information, the account information in the assignable account database, and the user information stored in the resource library, that is, the output may be used.
  • the condition for deleting the user information may also be preset. For example, if the user information stored in the resource library belongs to the user who has not applied for the account for more than five years, and the stored user information is outdated or cannot match the latest system, the deletion is deleted. This user information to save space in the repository.
  • the disclosure also provides an account resource sharing system.
  • the account resource sharing system 400 includes: an obtaining module 410 configured to acquire an account of an original user that meets a preset recycling condition; and a recycling module 420 configured to be configured To save the user information of the original user that meets the preset collection condition to the resource library, add the account of the original user that meets the preset collection condition to the assignable account database; the distribution module 430 is configured to receive the request for the user to allocate the account.
  • An account is assigned to the application user from the assignable account library.
  • the account resource sharing system may further include: an association module configured to determine whether the user information corresponding to the application user exists in the resource library; if yes, the application user is allocated to the application user.
  • the account number is associated with the user information corresponding to the application user stored in the resource library.
  • the present disclosure may further include the following functional units: an interface unit, an intelligent analysis unit, an intelligent processing unit, a dynamic management unit, a timing task unit, a query unit, and a message unit.
  • the interface unit is a unit that interacts between the system and the front-end system.
  • the user sends a request for assigning an account in the front-end system, and the request reaches the foregoing system of the present disclosure through the middleware; after receiving the request for the user to allocate the account, the system returns the account password and other information to the front-end system after being processed by the subsequent intelligent analysis unit.
  • the interface module is directly connected to the middleware, and the middleware is connected to the front end system.
  • the intelligent analysis unit consists of two parts. Part of the use of the results of the timed task analysis of the use of the assigned account and the assignable account in the account resource pool in the current system, especially the users with low frequency of use in the system, into the account resource pool for centralized management. The other part analyzes the result that needs to be allocated according to the request of the application user, the user information stored in the resource library (user authority, the user's favorite content, the user's usage time, etc.) and the account allocation status in the account resource pool.
  • the resource library user authority, the user's favorite content, the user's usage time, etc.
  • the intelligent processing unit consists of three parts.
  • the first part is based on the results analyzed by the intelligent analysis unit, and allocates account passwords and other feedbacks to the application users in the system, and timely updates the account status of the account resource pool.
  • the second part according to the following timed task unit function, the account that meets the preset recovery condition is searched from the system in time, and the account that reaches the preset recovery condition is collected into the assignable account database.
  • the third part collects statistics and analyzes the length of time that the application user actually uses the account. The maximum time of the application user's recent usage time may be used as the default usage time of the user to re-allocate the account.
  • the dynamic management unit is configured to dynamically manage the account resources in the account resource pool, the user information resources of the user, the rights resources, and the favorite resources, and automatically add the user's account according to the user whose usage frequency is low according to the intelligent analysis unit.
  • the user information such as the user's permission information and favorites are automatically saved to the resource library, and the user is automatically sent an email or a short message to notify the user of the manner of re-applying the account.
  • the timed task unit is configured to collect and update information, and mainly includes two types of job functions: first, periodically counting the account usage frequency in the account resource pool, so that the intelligent analysis unit recycles the account of the user with low frequency of use to the account resource pool; The second is to periodically scan the usage of the allocated account in the current system, and use it to recover the account that has reached the recovery condition.
  • the query unit is configured to query the dynamic usage of the current account resource pool, and query the user information of the application user in the account resource pool, such as the rights information and the favorite information.
  • the message unit is configured to send a message notification to the user to prompt the user account to be reclaimed, reclaimed, and re-applied for notification of the account.
  • the present disclosure further provides a computer readable storage medium having stored thereon a computer program, the computer program executing the steps of implementing the account resource sharing method according to any one of the items.
  • the present disclosure also provides an apparatus for sharing account resources, including the computer readable storage medium, a processor, and the computer readable storage medium and operable on the processor a computer program; the step of implementing the account resource sharing method according to any one of the preceding items when the processor executes the computer program.
  • the modules in the various embodiments of the present disclosure may be integrated into one processing module, or each unit may exist physically separately, or two or more units may be integrated into one module.
  • the above integrated modules can be implemented in the form of hardware or in the form of software functional modules.
  • the integrated modules, if implemented in the form of software functional modules and sold or used as stand-alone products, may also be stored in a computer readable storage medium.
  • the original user information associated with the account is not cleared, but the original user information is saved to the resource library, and when the original user re-applies for an account, the original user can read from the resource library.
  • the original user information is saved, so that the original user can get the original information and related settings more quickly, so as to improve work efficiency.
  • the reclaimed account is added to the assignable account database, and the association with the original user is cancelled to be reassigned to the new user.
  • the present disclosure can reclaim low-frequency account with low usage rate and re-allocate to the new application user, thereby improving the flow speed and usage rate of the account; on the other hand, the present disclosure saves the user information of the original user, which is convenient for the original Users quickly get relevant information before, which improves user productivity and improves user experience.
  • the present disclosure is applicable to a system in which the number of users is larger than the number of accounts, or an IT system with a limited number of accounts, so that an account can correspond to a plurality of low-frequency users or employees, thereby improving account utilization, reducing the number of accounts, and saving account fees.
  • whether the account is reclaimed is determined by the frequency of use or the duration of use of the account of the original user; the duration of the account may be preset when the account is assigned to the original user, according to whether the actual usage duration of the user reaches the pre-determination.
  • various information such as the user's historical usage time, frequency of use, user rights, and collection information can be obtained, which is convenient for statistical output; and can also be used according to the history of the user.
  • the duration and the current usage time at the time of collection calculate the usage time of the user's next application for the account, optimize the usage period of the account, and further improve the usage rate of the account.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Databases & Information Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Data Mining & Analysis (AREA)
  • General Physics & Mathematics (AREA)
  • Physics & Mathematics (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Computer Hardware Design (AREA)
  • Computer Security & Cryptography (AREA)
  • Computing Systems (AREA)
  • Computational Linguistics (AREA)
  • Multimedia (AREA)
  • Library & Information Science (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

本公开提供了一种账号资源共享方法、系统、设备和计算机可读存储介质。所述账号资源共享方法，包括：获取满足预设回收条件的原用户的账号；将原用户的用户信息保存至资源库，将原用户的账号加入可分配账号库；接收申请用户分配账号的请求，自可分配账号库中为该申请用户分配账号。

Description

账号资源共享方法、系统、设备和计算机可读存储介质
相关申请的交叉引用
本申请要求于2017年10月12日递交的中国专利申请201710948122.7的优先权，该申请的内容通过引用的方式全部并入本文用于所有目的。
技术领域
本公开账号资源共享方法、系统、设备和计算机可读存储介质。
背景技术
目前信息化建设在企业发展中起到了举足轻重的作用，在信息化过程中一般会采用企业信息化管理的IT系统。部分重要的IT系统都是按照IT账号的数量来收费的，而且此类系统的账号费用都较高。但是在实际使用过程中，部分用户只是偶尔使用IT系统，致使部分账号的使用频率很低，就给企业增加了成本。因此，如何提高账号的利用率，降低企业在IT系统建设中的成本，是目前亟待解决的问题。
发明内容
根据本公开的至少一个实施例，提供了一种账号资源共享方法，包括：获取满足预设回收条件的原用户的账号；将满足预设回收条件的原用户的用户信息保存至资源库，将满足预设回收条件的原用户的账号加入可分配账号库；以及接收申请用户分配账号的请求，自可分配账号库中为该申请用户分配账号。
在一个示例中，所述获取满足预设回收条件的原用户的账号，包括：获取原用户的账号的使用频率和/或使用时长，判断使用频率和/或使用时长是否满足预设回收条件，若是，则将原用户的账号标记为达到预设回收条件的原用户的账号。
在一个示例中，所述获取原用户的账号的使用频率和/或使用时长，包括：定时查询原用户的账号的使用频率和/或使用时长，以获取满足预设回收条件的原用户的账号；或原用户的账号的使用频率和/或使用时长满足预设回收条件，则自动标记为满足预设回收条件的原用户的账号。
在一个示例中，所述获取满足预设回收条件的原用户的账号，包括：获取满足预设备选回收条件的原用户的账号清单；根据使用频率将账号清单中的账号排名，将 使用频率低的账号作为满足预设回收条件的原用户的账号。
在一个示例中，所述获取满足预设回收条件的原用户的账号之后，包括：读取原用户的当前使用时长和历史使用时长，计算下次使用时长，以保存至原用户的用户信息中。
在一个示例中，所述将满足预设回收条件的原用户的账号加入可分配账号库之前，包括：向原用户发送通知消息。
在一个示例中，所述将满足预设回收条件的原用户的账号加入可分配账号库之前，包括：判断原用户的账号是否在使用状态；若否，则将满足预设回收条件的原用户的账号加入可分配账号库。
在一个示例中，所述自可分配账号库中为该申请用户分配账号之后，包括：判断资源库中是否存有该申请用户对应的用户信息；若是，则将分配给该申请用户的账号与保存在资源库中的该申请用户对应的用户信息关联。
在一个示例中，所述用户信息包括用户的身份识别ID，所述接收申请用户分配账号的请求中包括申请用户的身份识别ID；所述判断资源库中是否存有该申请用户对应的用户信息，包括：将该申请用户的身份识别ID与资源库中保存的用户信息中的身份识别ID进行比对，以获取与该申请用户的身份识别ID对应的用户信息。
在一个示例中，所述判断资源库中是否存有该申请用户对应的用户信息，包括：判断资源库中是否存有该申请用户对应的用户信息；若否，则为该申请用户匹配默认的用户信息，并将分配给该申请用户的账号与默认的用户信息关联。
在一个示例中，所述用户信息包括用户的身份识别ID、历史使用时长、当前使用时长、下次使用时长、使用频率、用户权限、收藏信息中的一种或多种。
在一个示例中，所述方法还包括：统计并输出已关联用户信息的账号信息、可分配账号库中的账号信息、资源库中保存的用户信息中的一种或多种。
根据本公开的至少另一个实施例，提供了一种账号资源共享系统，包括：获取模块，被配置为获取满足预设回收条件的原用户的账号；回收模块，被配置为将满足预设回收条件的原用户的用户信息保存至资源库，将满足预设回收条件的原用户的账号加入可分配账号库；分配模块，被配置为接收申请用户分配账号的请求，自可分配账号库中为该申请用户分配账号。
根据本公开的至少另一个实施例，提供了一种计算机可读存储介质，其上存储有计算机程序，该计算机程序执行时实现前述任一项所述的账号资源共享方法的步骤。
根据本公开的至少另一个实施例，提供了一种账号资源共享的设备，包括计算机可读存储介质、处理器及存储在计算机可读存储介质上并可在处理器上运行的计算机程序；所述处理器执行所述计算机程序时，实现前述任意一项所述的账号资源共享方法的步骤。
附图说明
本公开上述的和/或附加的方面和优点从下面结合附图对实施例的描述中将变得明显和容易理解，其中：
图1为本公开至少一个实施例的一种账号资源共享方法的实施例的流程示意图；
图2为本公开至少一个实施例的一种账号资源共享方法的实施例的流程示意图；
图3为本公开至少一个实施例的一种账号资源共享方法的又一实施例的流程示意图；
图4为本公开至少一个实施例的账号资源共享系统的示意图。
具体实施方式
下面详细描述本公开的实施例，所述实施例的示例在附图中示出，其中自始至终相同或类似的标号表示相同或类似的元件或具有相同或类似功能的元件。下面通过参考附图描述的实施例是示例性的，仅用于解释本公开，而不能解释为对本公开的限制。
本技术领域技术人员可以理解，除非特意声明，这里使用的单数形式“一”、“一个”、“所述”和“该”也可包括复数形式。应该进一步理解的是，本公开的说明书中使用的措辞“包括”是指存在所述特征、整数、步骤、操作、元件和/或组件，但是并不排除存在或添加一个或多个其他特征、整数、步骤、操作、元件、组件和/或它们的组。
本技术领域技术人员可以理解，除非另外定义，这里使用的所有术语(包括技术术语和科学术语)，具有与本公开所属领域中的普通技术人员的一般理解相同的意义。还应该理解的是，诸如通用字典中定义的那些术语，应该被理解为具有与现有技术的上下文中的意义一致的意义，并且除非像这里一样被特定定义，否则不会用理想化或过于正式的含义来解释。
本公开的实施例旨在解决部分低频账号实际利用率过低的问题，尤其是解决通 过回收账号提高账号利用率的同时，又保存各回收账号中的用户信息的问题。
根据本公开的至少一个实施例，提出了一种账号资源共享方法。参见图1所示的流程示意图，该方法包括如下步骤。
在步骤S10，获取满足预设回收条件的原用户的账号。
在步骤S20，将满足预设回收条件的原用户的用户信息保存至资源库，将满足预设回收条件的原用户的账号加入可分配账号库。
在步骤S30，接收申请用户分配账号的请求，自可分配账号库中为该申请用户分配账号。
其中，在步骤S10获取满足预设回收条件的原用户的账号例如包括：原用户的账号为已分配至特定用户的账号，该账号关联了特定用户的用户信息，并根据该特定用户的实际使用情况持续更新用户信息。预设回收条件可为系统统一预设的账号回收条件，亦可为针对特定账号或用户单独设置的回收条件；或，根据用户自身使用账号的情况和整个系统中账号的使用情况，自行智能化调整的回收条件。
所示获取满足预设回收条件的原用户的账号可通过定时任务实现，以定时收集、更新和统计系统账号的使用频率，以将符合预设条件的低频账号回收至可分配账号库；亦可定时扫描可分配账号库中账号的使用情况，可分配账号库中可存有各分配账号的分配时间和回收时间，以将达到预设使用时长的账号回收；或，用户在达到预设回收条件时，主动播报或上传自己的账号信息或用户信息，以使系统及时获知预回收的账号；或，根据可分配账号库中的账号剩余情况，主动提醒管理用户扫描低频账号，或重新设置筛选低频用户的使用频率条件，或重新设置筛选低频用户的使用时长条件，以重新获取满足新条件的低频用户账号，方便后续匹配账号资源与用户申请。
在步骤S20将满足预设回收条件的原用户的用户信息保存至资源库，将满足预设回收条件的原用户的账号加入可分配账号库例如可以包括：当该账号的实际使用情况满足预设回收条件时，将与该原用户的账号关联的用户信息将保存至指定的资源库，以备后续调用；然后将账号加入可分配账号库；可分配账号库中的账号与用户信息均不关联，仅当其中的账号分配至某一具体用户时，再与该用户的用户信息关联。
当然，在实际使用中，还可根据情况设定更多的回收账号规则、用户信息保存规则，甚至删除用户信息的规则。例如，原用户的账号为多人共用的部门财务报销用户的账号，可为其预设特定的回收条件，避免回收后引起混乱；若用户为离职状态或其它不可能再次申请账号的状态，亦可判定为直接删除用户信息，以节省资源库的空 间，以及优化后续的信息搜索速度；所述资源库亦可设置定期清理冗余用户信息的功能，以优化系统效率。
该步骤S20中的两个子步骤可调换顺序，即步骤S20亦可包括：将满足预设回收条件的原用户的账号加入可分配账号库，将满足预设回收条件的原用户的用户信息保存至资源库；亦不影响本公开技术方案的实施。
在步骤S30接收申请用户分配账号的请求，自可分配账号库中为该申请用户分配账号例如可以包括：申请用户可为从未申请过账号的新用户，亦可为被回收了账号的原用户；分配账号的请求中可包括申请账号的用户权限、使用时长等信息，以从可分配账号库中匹配合适的账号。通过本步骤，回收的账号可再次分配至新的申请用户。若新的申请用户为被回收了账号的原用户，在其分配账号的请求中，还可包括关联原用户的用户信息的请求，以尽快获取原用户的用户信息，减少搜索等待时间。
针对被回收了账号的用户再次申请账号的使用场景，本公开还提出另一种实施例，以便再次申请账号的用户读取之前保存的用户信息，方便用户使用，提高工作效率。如图2所示，该方案例如可以包括：所述自可分配账号库中为该申请用户分配账号之后，还包括在步骤S40，判断资源库中是否存有该申请用户对应的用户信息；若是，则将分配给该申请用户的账号与保存在资源库中的该申请用户对应的用户信息关联。
判断资源库中是否存有该申请用户对应的用户信息，可根据申请用户主动发出的关联原用户的用户信息的请求进行查找，亦可直接在资源库中进行搜索匹配。为提高搜索匹配速度，申请用户可在发出分配账号的请求时，选择是否为新用户或原用户，若申请用户确认为新用户，则无需进行匹配查找，若申请用户确认为原用户，则可进一步引导申请用户输入上次申请账号的时间范围，或账号被回收的时间范围，以提高在资源库中的搜索匹配速度，节省申请账户的时间。若资源库中存有该申请用户对应的用户信息，则说明该申请用户曾经有使用账号的记录，将保存在资源库中的该申请用户对应的用户信息与分配给该申请用户的账号关联，以便用户读取到曾经的使用信息，提高用户工作效率。
本实施例的方法在回收账号时，将用户的账号与用户的用户信息分离，既可保存用户的个人信息，以便下次申请时读取，又可将账号重新分配，以提高账号的使用率。
本公开还提供了另一实施例，如图3所示，该实施例与上一实施例的区别之一在 于设置了预设回收条件的判断标准：所述获取满足预设回收条件的原用户的账号的方法，例如可以包括如下步骤。
在步骤S11，获取原用户的账号的使用频率和/或使用时长，判断使用频率和/或使用时长是否满足预设回收条件，若是，则将原用户的账号标记为达到预设回收条件的原用户的账号。
步骤S11例如可以包括如下三个步骤。
在步骤S111，获取原用户的账号的使用频率和/或使用时长，判断使用频率和/或使用时长是否满足预设回收条件；若是，则执行步骤S112，若否，则执行步骤S113；
在步骤S112，将原用户的账号标记为达到预设回收条件的原用户的账号。
在步骤S113，不处理。
预回收的账号一般为低频账号，或到达指定使用时长的账号，可于系统中设置一定时任务模块，用于收集和更新用户信息与账号信息，该模块可执行两种功能：一是定时统计账号资源池中的各账号，以及当前用户的账号使用频率和使用时长，以将低频使用账号回收至可分配账号库，所述账号资源池中包括可分配账号库和已分配账号库；二是定时扫描账号资源池中存储的各账号的预设使用时长，以回收达到预设使用时长的账号。为避免误判，可将使用频率与使用时长结合判断。例如，若用户的使用时长为一个月，但该用户的使用频率很高，超出当前系统内用户的平均使用频率，则可自动延长该用户的预设使用时长，或提醒用户发出延长使用时长的请求，或提醒管理者是否需要延长该用户的预设使用时长。
判断原用户的账号的使用频率、或使用时长，或使用频率与使用时长二者的结合，是否满足预设回收条件后，执行步骤S112：将原用户的账号标记为达到预设回收条件的原用户的账号。标记完成后，参见图3中的步骤S21，将达到预设回收条件的原用户的用户信息保存至资源库，将达到预设回收条件的原用户的账号加入可分配账号库，完成回收步骤。若后续账号被回收的原用户再次申请账号时，则可自资源库中读取保存的原用户的用户信息。与标准化设置的全新账号相比，本公开的实施例通过读取之前的用户信息，可使申请用户快速获得之前的历史信息，提高了用户的工作效率。
在本公开中的判断为否的步骤S113，不处理。不处理例如可以包括不回收该账号，可继续监控该账号或该用户的使用情况；若该账号已临近回收条件，但还未达到回收条件，则不回收该账号，同时向该账号的用户发出提醒信息，以便用户及时预知账号状态。
如前所述，所述获取原用户的账号的使用频率和/或使用时长的方法可通过系统定时查询实现，或在用户的账号达到预设回收条件时，由用户主动播报或上传。其技术方案例如包括以下两种：定时查询原用户的账号的使用频率和/或使用时长，以获取满足预设回收条件的原用户的账号；或，原用户的账号的使用频率和/或使用时长满足预设回收条件，则自动标记为满足预设回收条件的原用户的账号。
这两种方法均需预设回收条件，例如：账号的使用频率低于30天/次，则将该账号作为满足回收条件的账号；或，在分配账号时的同时，获得账号的最长使用时间为100天，达到100天，则将该账号作为满足回收条件的账号。第一种定时查询方法可获取较为全面的账号信息，还可根据具体情况设置或修改筛选查询条件，再根据具体情况确认这些账号是否需要回收。第二种用户自动标记的方法，通过用户主动播报或上传账号，无需系统逐一查询，提高了查询效率；系统可从用户主动播报或上传的账号中确认需要回收的账号，避免误回收。这两种方法通过预设回收条件，可直接自动获得所述满足预设回收条件的原用户的账号，无需人工参与筛选。
在实际使用中，若可分配账号库内的账号充足，可取消账号的回收功能；亦可在账号数量紧缺时将账号的使用频率进行排序，以将使用频率较低的账号直接作为备选的预回收账号，再自备选的预回收账号中挑选排名靠前的账号进行回收。技术方案例如包括：所述获取满足预设回收条件的原用户的账号，包括：获取满足预设备选回收条件的原用户的账号清单；根据使用频率将账号清单中的账号排名，将使用频率低的账号作为满足预设回收条件的原用户的账号。
使用频率低的账号可为账号排名中使用频率最低的若干个账号，例如，通过程序的比较算法，找出使用频率最低的账号，再通过循环执行该比较算法，依次得到多个使用频率最低的账号；亦可根据排名，确定账号的平均使用频率，再将低于平均使用频率的账号作为使用频率低的账号。
本技术方案的实施例与图3所示的实施例差别在于，图3所示的实施例适用于回收低于预设频率的账户(亦可预设其它回收条件)，与用户使用频率的排名无关。本实施例适用于以账号的使用频率排名为参考，回收特定数量的账户或特定的账户。当所有用户的使用频率和/或使用时长都不满足预设回收条件时，本实施例提供了另一种判断账户是否回收的方法，以弥补图3所示实施例的不足。例如，若系统通过定时查询未找到满足预设回收条件的账户，但又必须回收若干个账号，以便分配至新的申请用户，则可通过特定条件筛选出备选的原用户的账号清单，再根据账号清单中的账 号使用频率进行排名，最后取使用频率最低的几位用户作为满足预设回收条件的原用户的账号。当然，亦可再结合其它具体情况确认需要回收的账号，例如使用时长、账号权限等。
为确定用户的下次使用账号的时长，即预设回收条件中的使用时长，可根据用户的历史使用记录进行推算，以平衡账号利用率与用户体验。故，所述获取满足预设回收条件的原用户的账号之后，还包括：在步骤S12，读取原用户的当前使用时长和历史使用时长，计算下次使用时长，以保存至原用户的用户信息中。
所述计算方法可采用平均法或差值法等，亦可结合用户的使用频率，作为计算使用时长的参考。例如，取预回收账号的用户的当前使用时长和最近两次的历史使用时长，计算平均使用时长，作为用户下次申请账号时的使用时长；或，参考用户的使用频率，若用户使用频率达到某一设定值，则对应一加权参数，将前述平均使用时长与该加权进行运算，例如相乘，将运算结果保存为用户下次申请账号的使用时长。当原用户的账号被回收后，原用户再次申请账号时，则以之前计算并保存的下次申请账号的使用时长作为用户本次申请账号的预设使用时长；若用户的实际使用时长达到该预设使用时长，则再次回收该账号。当然，计算平均使用时长或其它时间参数时，亦可参考所有回收的账号的历史使用时长，而不仅限于本用户自身的使用时长。
在一个示例中，设定用户预设回收条件中的使用频率时，可根据用户自身的使用频率计算，亦可参考资源库中所有用户的使用频率，以及结合用户的权限、账号是否为公共账号等因素作为参考。
回收账号之前，可向用户发送通知，以便用户及时处理相关信息，或获知重新申请账号的方法、以及如何读取已保存的用户信息等相关事宜。故本公开还提出一种实施例，该实施例在所述将满足预设回收条件的原用户的账号加入可分配账号库之前，包括在步骤S13，向原用户发送通知消息。
该通知可通过邮件发到与用户信息关联的邮箱，或通过短信发送至手机，或直接在系统内向用户推送提醒消息等途径通知用户。该通知消息的内容可包括即将回收账号的提醒、重新申请账号的方法、重新申请账号时如何再次关联用户信息、关联用户信息的验证码等内容。
回收账号时，考虑到该账号对应的原用户的使用状态，本公开进一步提出，在所述将满足预设回收条件的原用户的账号加入可分配账号库之前，包括在步骤S14，判断原用户的账号是否在使用状态；若否，则将满足预设回收条件的原用户的账号加 入可分配账号库。
在该步骤中，若账号已经达到预设使用时长或预设使用频率等回收条件，则继续判断该账号的用户是否在使用状态；使用状态包括用户当前是否登录、用户当前是否有进行账号操作、用户当前是否具有未完成的IT流程等状态；例如：在企业管理系统中，某账号最近发起了一次报销流程，但该流程仍处于中间审核状态，未结束，则判断该账号仍处于使用状态，不回收该账号。若该账号当前没有使用，则将该账号回收至可分配账号库中，以供后续分配给其他用户使用。
执行实施例中的所述判断资源库中是否存有该申请用户对应的用户信息用户时，需预设用户信息的识别标记，以便用户重新申请账号时通过该识别标记快速匹配到对应的用户信息。故本公开还提出：所述用户信息包括用户的身份识别ID，所述接收申请用户分配账号的请求中包括申请用户的身份识别ID；所述判断资源库中是否存有该申请用户对应的用户信息，包括：将该申请用户的身份识别ID与资源库中保存的用户信息中的身份识别ID进行比对，以获取与该申请用户的身份识别ID对应的用户信息。
该用户的身份识别ID可以为用户的真实姓名、身份证号码、工号、邮箱地址、手机号码等唯一识别信息，或是通过唯一识别信息计算出的识别码或身份标记等。存储用户信息时，还可为该身份识别ID计算对应的验证码，并将该验证码以前述通知消息的方式发送至原用户；当申请用户欲获取该用户信息或将该用户信息与账号进行关联时，可要求申请用户输入对应的验证码，以确保当前的申请用户与资源库中存储的用户信息所属的原用户为同一用户，或是确认当前申请用户读取该用户信息的操作或是关联该用户信息与账号的操作经过了原用户的授权。
实施例中的步骤S40，所述判断资源库中是否存有该申请用户对应的用户信息，还可可以包括：在步骤S41，判断资源库中是否存有该申请用户对应的用户信息；若是，则执行步骤S42，若否，则执行步骤S43。
在步骤S42，若是，将分配给该申请用户的账号与保存在资源库中的该申请用户对应的用户信息关联。
在步骤S43，若否，则为该申请用户匹配默认的用户信息，并将分配给该申请用户的账号与默认的用户信息关联。
如图3所示，若申请用户为原用户，即之前申请过旧的账号的用户，则旧的账号回收时，原用户的用户信息将存储于资源库中，原用户再次申请新账号时，可自资源 库中查找出；若查找不到，则判断该申请用户为新用户，根据预设的规则，为该新用户匹配默认的用户信息，并将分配给该申请用户的账号与默认的用户信息关联；该默认的用户信息可包括用户权限、用户使用时长、账户申请时间等账号信息，亦可包括系统操作向导、默认功能界面等软件设置信息；故，若申请用户若为原用户，其不仅可读取到原来的账号信息，亦可读取到原软件设置相关的信息，使用户操作更便捷。
在一个示例中，在将分配给该申请用户的账号与保存在资源库中的该申请用户对应的用户信息关联后，或，在将分配给该申请用户的账号与默认的用户信息关联之后，本公开可包括以下，在步骤S50，将关联的账号与用户信息返回至申请用户。
当然，向申请用户返回关联的账号与用户信息之前，亦可包括审核步骤或校验步骤等，以确认返回的账户符合系统预设条件或其它特殊条件，在此不再赘述。
为方便识别用户与账号，以及统计相关信息，所述用户信息可包括用户的身份识别ID、历史使用时长、当前使用时长、下次使用时长、使用频率、用户权限、收藏信息中的一种或多种。当然，该用户信息中还可包括前述的验证码、使用次数、使用时间等信息。
根据上述用户信息，本公开还可统计并输出已关联用户信息的账号信息、可分配账号库中的账号信息、资源库中保存的用户信息中的一种或多种，即：可输出已使用的账号信息和对应的用户信息，以及可分配账号库中未分配的账号信息，和资源库中保存的所有用户信息等。当然，亦可预设删除用户信息的条件，例如：资源库中存储的用户信息所属的用户已超过五年未申请账号，所存储的用户信息已过时或无法与最新系统相匹配等，则删除该用户信息，以节省资源库的空间。
本公开还提出一种账号资源共享系统，如图4所示，该账号资源共享系统400包括：获取模块410，被配置为获取满足预设回收条件的原用户的账号；回收模块420，被配置为将满足预设回收条件的原用户的用户信息保存至资源库，将满足预设回收条件的原用户的账号加入可分配账号库；分配模块430，被配置为接收申请用户分配账号的请求，自可分配账号库中为该申请用户分配账号。
为方便回收了账号的用户再次申请账号，该账号资源共享系统还可包括：关联模块，被配置为判断资源库中是否存有该申请用户对应的用户信息；若是，则将分配给该申请用户的账号与保存在资源库中的该申请用户对应的用户信息关联。
基于以上账号资源共享系统的各模块，本公开还可进一步包括如下各功能单元：接口单元、智能分析单元、智能处理单元、动态管理单元、定时任务单元、查询单元 和消息单元。
接口单元为本系统和前端系统交互的单元。用户在前端系统发出分配账号的请求，该请求通过中间件到达本公开前述的系统；系统接收申请用户分配账号的请求后，经过后续的智能分析单元处理后，返回账号密码等信息至前端系统，一般该接口模块直接和中间件连接，中间件再和前端系统连接。
智能分析单元包括两部分。一部分利用定时任务的结果分析当前系统中账号资源池内的已分配账号和可分配账号的使用情况，尤其是系统中使用频率低的用户，将其纳入到账号资源池中进行集中管理。另一部分根据申请用户的请求、资源库保存的用户信息(用户权限、用户的收藏夹内容、用户的使用时长等)和账号资源池中的账号分配现状，分析出需要分配的结果。
智能处理单元包括三部分。第一部分根据智能分析单元分析出的结果，在系统中分配账号密码等反馈给申请用户，并及时更新账号资源池的账号情况。第二部分根据下述的定时任务单元功能，及时从系统中查找符合预设回收条件的账号，并将达到预设回收条件的账号回收至可分配账号库中。第三部分回收时统计并分析申请用户实际使用账号的时长，可将该申请用户近几次使用时长中的最长时间作为该用户后续再次分配账号的账号预设使用时长。
动态管理单元，被配置为动态管理账号资源池中的账号资源、用户的用户信息资源、权限资源和收藏夹资源等，根据智能分析单元得出的使用频率低的用户，将用户的账号自动加入到可分配账号库中，将用户的权限信息、收藏夹等用户信息自动保存至资源库中，并自动发邮件或短信通知该用户后续重新申请账号的方式。
定时任务单元，被配置为收集和更新信息，主要包括两类作业功能：一是定时统计账号资源池中的账号使用频率，使智能分析单元将使用频率低的用户的账号回收至账号资源池；二是定时扫描当前系统中已分配账号的使用情况，用于回收达到回收条件的账号。
查询单元，被配置为查询当前账号资源池的动态使用情况，查询账号资源池中申请用户的用户信息，例如权限信息、收藏夹信息等。
消息单元，被配置为向用户发送消息通知，以便提示用户账号即将回收、已回收和重新申请账号的通知。
根据以上账号资源共享方法，本公开还提出一种计算机可读存储介质，其上存储有计算机程序，该计算机程序执行时实现任一项所述的账号资源共享方法的步骤。
根据以上计算机可读存储介质，本公开还提出一种账号资源共享的设备，包括所述计算机可读存储介质、处理器及存储在所述计算机可读存储介质上并可在处理器上运行的计算机程序；所述处理器执行所述计算机程序时，实现前述任意一项所述的账号资源共享方法的步骤。
在本公开各个实施例中的各模块可以集成在一个处理模块中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个模块中。上述集成的模块既可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。所述集成的模块如果以软件功能模块的形式实现并作为独立的产品销售或使用时，也可以存储在一个计算机可读取存储介质中。
根据本公开的实施例，在回收账号的时候，不清空与该账号关联的原用户信息，而是将原用户信息保存至资源库，当原用户重新申请账号时，可自资源库中读取保存的原用户信息，从而使原用户更快获得原来的信息和相关设置，以提高工作效率。回收的账号加入可分配账号库，取消了与原用户的关联，以重新分配至新用户使用。一方面，本公开可回收使用率低下的低频账号，并重新分配至新申请用户，提高了账号的流转速度和使用率；另一方面，本公开又保存了各位原用户的用户信息，方便原用户快速获取之前的相关信息，提高了用户工作效率，改善了用户体验。本公开适用于用户数量大于账号数量的系统，或账号数量有限的IT系统，以使一个账号可对应于多个低频使用用户或员工，提高了账号利用率，可减少账号数量，节省账号费用。
根据本公开的实施例，通过原用户的账号的使用频率或使用时长来判定是否回收该账号；可在给原用户分配账号时预设账号使用时长，以根据用户的实际使用时长是否达到该预设使用时长来判断是否回收该账号；或，通过用户历史数据计算用户的使用频率，以用户的实际使用频率是否低于预设使用频率来判断是否回收该账号；或，将使用频率和使用时长二者结合判断，减少误回收的概率；获取原用户的账号的使用频率或使用时长的方式可以为用户自行标记并上报，以减少系统运算量，亦可由系统定期查询统计，以便及时获知用户数据与账号数据，方便调配。
根据本公开的实施例，通过资源库内存储的用户信息，可获知用户的历史使用时长、使用频率、用户权限、收藏信息等多种信息，方便统计输出；同时，还可根据用户的历史使用时长和回收时的当前使用时长，计算用户下次申请账号时的使用时长，优化了账号的使用周期，进一步提高了账号的使用率。
以上所述仅是本公开的部分实施方式，应当指出，对于本技术领域的普通技术人 员来说，在不脱离本公开原理的前提下，还可以做出若干改进和润饰，这些改进和润饰也应视为本公开的保护范围。

Claims (16)

  1. 一种账号资源共享方法，包括：
    获取满足预设回收条件的原用户的账号；
    将满足预设回收条件的原用户的用户信息保存至资源库，将满足预设回收条件的原用户的账号加入可分配账号库；以及
    接收申请用户分配账号的请求，自可分配账号库中为该申请用户分配账号。
  2. 根据权利要求1所述的方法，其中，所述获取满足预设回收条件的原用户的账号，包括：
    获取原用户的账号的使用频率和/或使用时长，以及
    判断使用频率和/或使用时长是否满足预设回收条件，若是，则将原用户的账号标记为达到预设回收条件的原用户的账号。
  3. 根据权利要求2所述的方法，其中，所述获取原用户的账号的使用频率和/或使用时长，包括：
    定时查询原用户的账号的使用频率和/或使用时长，以获取满足预设回收条件的原用户的账号；或
    原用户的账号的使用频率和/或使用时长满足预设回收条件，则自动标记为满足预设回收条件的原用户的账号。
  4. 根据权利要求1所述的方法，其中，所述获取满足预设回收条件的原用户的账号，包括：
    获取满足预设备选回收条件的原用户的账号清单；以及
    根据使用频率将账号清单中的账号排名，将使用频率低的账号作为满足预设回收条件的原用户的账号。
  5. 根据权利要求1所述的方法，其中，所述获取满足预设回收条件的原用户的账号之后，包括：
    读取原用户的当前使用时长和历史使用时长，计算下次使用时长，以保存至原 用户的用户信息中。
  6. 根据权利要求1所述的方法，其中，所述将满足预设回收条件的原用户的账号加入可分配账号库之前，包括：
    向原用户发送通知消息。
  7. 根据权利要求1所述的方法，其中，所述将满足预设回收条件的原用户的账号加入可分配账号库之前，包括：
    判断原用户的账号是否在使用状态；以及
    若否，则将满足预设回收条件的原用户的账号加入可分配账号库。
  8. 根据权利要求1所述的方法，其中，所述自可分配账号库中为该申请用户分配账号之后，包括：
    判断资源库中是否存有该申请用户对应的用户信息；以及
    若是，则将分配给该申请用户的账号与保存在资源库中的该申请用户对应的用户信息关联。
  9. 根据权利要求8所述的方法，其中，所述用户信息包括用户的身份识别ID，所述接收申请用户分配账号的请求中包括申请用户的身份识别ID；
    其中所述判断资源库中是否存有该申请用户对应的用户信息，包括：
    将该申请用户的身份识别ID与资源库中保存的用户信息中的身份识别ID进行比对，以获取与该申请用户的身份识别ID对应的用户信息。
  10. 根据权利要求8所述的方法，其中，所述判断资源库中是否存有该申请用户对应的用户信息，包括：
    判断资源库中是否存有该申请用户对应的用户信息；以及
    若否，则为该申请用户匹配默认的用户信息，并将分配给该申请用户的账号与默认的用户信息关联。
  11. 根据权利要求1所述的方法，其中，所述用户信息包括用户的身份识别ID、 历史使用时长、当前使用时长、下次使用时长、使用频率、用户权限、收藏信息中的一种或多种。
  12. 根据权利要求1所述的方法，其中，还包括：
    统计并输出已关联用户信息的账号信息、可分配账号库中的账号信息、资源库中保存的用户信息中的一种或多种。
  13. 一种账号资源共享系统，其中，包括：
    获取模块，被配置为获取满足预设回收条件的原用户的账号；
    回收模块，被配置为将满足预设回收条件的原用户的用户信息保存至资源库，将满足预设回收条件的原用户的账号加入可分配账号库；
    分配模块，被配置为接收申请用户分配账号的请求，自可分配账号库中为该申请用户分配账号。
  14. 根据权利要求13所述的账号资源共享系统，还包括：
    关联模块，被配置为判断资源库中是否存有该申请用户对应的用户信息；若是，则将分配给该申请用户的账号与保存在资源库中的该申请用户对应的用户信息关联。
  15. 一种计算机可读存储介质，其上存储有计算机程序，该计算机程序执行时实现权利要求1～12任一项所述的账号资源共享方法的步骤。
  16. 一种账号资源共享的设备，包括：
    计算机可读存储介质、处理器及存储在计算机可读存储介质上并可在处理器上运行的计算机程序；
    所述处理器执行所述计算机程序时，实现权利要求1～12任意一项所述的账号资源共享方法的步骤。
PCT/CN2018/097910 2017-10-12 2018-08-01 账号资源共享方法、系统、设备和计算机可读存储介质 Ceased WO2019071997A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US16/329,350 US11210284B2 (en) 2017-10-12 2018-08-01 Method, system, apparatus, and computer-readable storage medium for sharing account resources

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710948122.7A CN107689966B (zh) 2017-10-12 2017-10-12 账号资源共享方法、系统、设备和计算机可读存储介质
CN201710948122.7 2017-10-12

Publications (1)

Publication Number Publication Date
WO2019071997A1 true WO2019071997A1 (zh) 2019-04-18

Family

ID=61154443

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/097910 Ceased WO2019071997A1 (zh) 2017-10-12 2018-08-01 账号资源共享方法、系统、设备和计算机可读存储介质

Country Status (3)

Country Link
US (1) US11210284B2 (zh)
CN (1) CN107689966B (zh)
WO (1) WO2019071997A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN119598505A (zh) * 2024-11-14 2025-03-11 浪潮云信息技术股份公司 应用于数据共享的审核流程和权限控制管理系统及方法

Families Citing this family (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107689966B (zh) 2017-10-12 2020-06-02 京东方科技集团股份有限公司 账号资源共享方法、系统、设备和计算机可读存储介质
CN108683587B (zh) * 2018-05-11 2021-09-21 腾讯科技（深圳）有限公司 一种账号管理方法及装置
CN108694648B (zh) * 2018-05-15 2021-07-20 腾讯科技（深圳）有限公司 物品交互方法、物品标识注册方法、系统、装置和存储介质
CN109224455A (zh) * 2018-09-29 2019-01-18 广州华多网络科技有限公司 虚拟宠物的互动方法、装置和服务器
CN111538721A (zh) * 2020-04-23 2020-08-14 北京字节跳动网络技术有限公司 账号处理方法、装置、电子设备及计算机可读存储介质
CN112052096B (zh) * 2020-09-14 2024-03-01 北京达佳互联信息技术有限公司 资源处理方法、装置、服务器及终端
CN113312176B (zh) * 2021-04-30 2024-07-30 浙江大搜车软件技术有限公司 资源信息的管理方法、装置、电子装置及存储介质
CN114697084B (zh) * 2022-03-14 2024-03-26 浙江大豪科技有限公司 缝纫设备数据访问方法

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8631478B2 (en) * 2009-07-23 2014-01-14 International Business Machines Corporation Lifecycle management of privilege sharing using an identity management system
CN104852903A (zh) * 2015-04-13 2015-08-19 苏州天趣信息科技有限公司 一种游戏账号的临时共享的方法和系统
CN105847277A (zh) * 2016-04-29 2016-08-10 乐视控股（北京）有限公司 用于第三方应用的服务账号共享管理方法及系统
CN107689966A (zh) * 2017-10-12 2018-02-13 京东方科技集团股份有限公司 账号资源共享方法、系统、设备和计算机可读存储介质

Family Cites Families (37)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7308434B2 (en) * 2000-03-30 2007-12-11 Verizon Business Global Llc Account management tool for e-billing system
US8639824B1 (en) * 2003-09-19 2014-01-28 Hewlett-Packard Development Company, L.P. System and method for dynamic account management in a grid computing system
US7650137B2 (en) * 2005-12-23 2010-01-19 Apple Inc. Account information display for portable communication device
US8622837B2 (en) * 2006-03-20 2014-01-07 Sony Computer Entertainment America Llc Managing game metrics and authorizations
US20090044237A1 (en) * 2007-07-13 2009-02-12 Zachary Ryan Keiter Sport video hosting system and method
US20090089757A1 (en) * 2007-10-01 2009-04-02 Fujitsu Limited Configurable Web Services System and a Method to Detect Defects in Software Applications
US8182346B2 (en) * 2007-12-26 2012-05-22 Scientific Games Holdings Limited System and method for collecting and using player information
US8301502B2 (en) * 2008-12-17 2012-10-30 Noam Livnat Methods and systems for account management of group accounts
US8285658B1 (en) * 2009-08-25 2012-10-09 Scout Analytics, Inc. Account sharing detection
CN102137067B (zh) * 2010-01-26 2014-03-12 上海美你德软件有限公司 在网上社区分享网上订阅账号方法及系统
US8856955B2 (en) * 2010-05-18 2014-10-07 ServiceSource International, Inc. Remediating unauthorized sharing of account access to online resources
US8321681B2 (en) * 2010-07-19 2012-11-27 Google Inc. Managing user accounts
US20160350848A1 (en) * 2010-08-04 2016-12-01 Jpmorgan Chase Bank, N.A. Systems And Methods For Providing Group Accounts
US9740435B2 (en) * 2012-02-27 2017-08-22 Fujifilm North America Corporation Methods for managing content stored in cloud-based storages
US9022869B1 (en) * 2012-12-14 2015-05-05 Kabam, Inc. System and method for merging user accounts
US8968104B2 (en) * 2013-03-13 2015-03-03 Game Play Network, Inc. System and method of providing wagering opportunities based on multiplayer interactions
US20140279526A1 (en) * 2013-03-18 2014-09-18 Fulcrum Ip Corporation Systems and methods for a private sector monetary authority
CN103237307B (zh) * 2013-04-19 2016-07-06 杭州全维通信服务有限公司 一种基于资源池的portal账号资源分配方法及系统
CN104219204A (zh) * 2013-06-01 2014-12-17 姚爱军 一种网络账号的生成方法及装置
CN104144419B (zh) * 2014-01-24 2017-05-24 腾讯科技（深圳）有限公司 一种身份验证的方法、装置及系统
US9483529B1 (en) * 2014-02-14 2016-11-01 Twitter, Inc. Selection and presentation of unviewed messages
CN104869143B (zh) * 2014-02-26 2018-05-08 腾讯科技（深圳）有限公司 资料分享方法、装置、客户端和服务器
WO2015161284A1 (en) * 2014-04-18 2015-10-22 Personally, Inc. Dynamic directory and content communication
CN105100028A (zh) * 2014-05-22 2015-11-25 中兴通讯股份有限公司 账号管理方法及装置
US9363260B2 (en) * 2014-07-07 2016-06-07 Oracle International Corporation Detecting sharing of passwords for password protected user accounts
US9491155B1 (en) * 2014-08-13 2016-11-08 Amazon Technologies, Inc. Account generation based on external credentials
US10091174B2 (en) * 2014-09-29 2018-10-02 Dropbox, Inc. Identifying related user accounts based on authentication data
US9503451B1 (en) * 2014-12-15 2016-11-22 Amazon Technologies, Inc. Compromised authentication information clearing house
US9782677B1 (en) * 2015-04-02 2017-10-10 Aftershock Services, Inc. Systems and methods for incentivizing user log-in to a user account associated with an online game
CN104852965B (zh) * 2015-04-16 2018-10-02 北京京东尚科信息技术有限公司 一种用户账号项目管理方法及系统
US20160350783A1 (en) * 2015-06-01 2016-12-01 Visa International Service Association Systems and methods to organize data supporting efficient processing of large scale propagation of resources among users of accounts
US9407652B1 (en) * 2015-06-26 2016-08-02 Palantir Technologies Inc. Network anomaly detection
US10425811B2 (en) * 2015-08-24 2019-09-24 Ayla Networks, Inc. Linked user accounts for an internet-of-things platform
CN105391654A (zh) * 2015-11-26 2016-03-09 中国建设银行股份有限公司 基于账户活跃度的系统资源分配方法及装置
US10303653B2 (en) * 2016-04-22 2019-05-28 Microsoft Technology Licensing, Llc Automatic computer user account management on multi account computer system
US10509779B2 (en) * 2016-09-14 2019-12-17 Visa International Service Association Self-cleaning token vault
CN106656957A (zh) * 2016-09-27 2017-05-10 乐视控股（北京）有限公司 账户共享方法及装置

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8631478B2 (en) * 2009-07-23 2014-01-14 International Business Machines Corporation Lifecycle management of privilege sharing using an identity management system
CN104852903A (zh) * 2015-04-13 2015-08-19 苏州天趣信息科技有限公司 一种游戏账号的临时共享的方法和系统
CN105847277A (zh) * 2016-04-29 2016-08-10 乐视控股（北京）有限公司 用于第三方应用的服务账号共享管理方法及系统
CN107689966A (zh) * 2017-10-12 2018-02-13 京东方科技集团股份有限公司 账号资源共享方法、系统、设备和计算机可读存储介质

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN119598505A (zh) * 2024-11-14 2025-03-11 浪潮云信息技术股份公司 应用于数据共享的审核流程和权限控制管理系统及方法

Also Published As

Publication number Publication date
CN107689966B (zh) 2020-06-02
US11210284B2 (en) 2021-12-28
US20210011903A1 (en) 2021-01-14
CN107689966A (zh) 2018-02-13

Similar Documents

Publication Publication Date Title
WO2019071997A1 (zh) 账号资源共享方法、系统、设备和计算机可读存储介质
US10664312B2 (en) Computing resource inventory system
CN111414070B (zh) 一种机箱功耗管理方法、系统及电子设备和存储介质
JP5623271B2 (ja) 情報処理装置、権限管理方法、プログラムおよび記録媒体
WO2019075842A1 (zh) 任务分配方法、装置、存储介质和计算机设备
CN107103009B (zh) 一种数据处理方法及装置
US20130226639A1 (en) Task management method and task management apparatus
CN101997894A (zh) 一种信息推送方法及其系统和网络系统
CN109542894B (zh) 用户数据集中存储方法、装置、介质和计算机设备
CN107679718A (zh) 名单分配方法、设备以及计算机可读存储介质
CN112967091A (zh) 营销服务事件的智能分发方法、系统及存储介质
WO2019200767A1 (zh) 坐席任务分配方法、装置、计算机设备及存储介质
CN105468619A (zh) 用于数据库连接池的资源分配方法和装置
CN119130366B (zh) 基于引擎的流程审批方法、装置、计算机设备及存储介质
CN118296580A (zh) 一种多角色权限管理方法及系统
CN120822234B (zh) 一种基于集成系统的权限动态管理系统
CN109583615B (zh) 会议室的预订方法、系统及服务器、计算机可读存储介质
CN115310787A (zh) 任务分配方法、电子设备及计算机可读存储装置
CN105956749A (zh) 巡防管理信息的处理方法和装置
JP5812911B2 (ja) ワークフロー管理システム、ワークフロー管理方法及びワークフロー管理プログラム
CN112288329A (zh) 一种操作行为记录的风险预估方法及装置
JP2016501392A (ja) リソース管理システム、リソース管理方法、およびプログラム
JP2012190354A (ja) 文書管理システム、及び文書管理方法
JP2021096514A (ja) 情報処理装置および情報処理方法
CN118426928A (zh) 异常指令的处理方法及其装置、电子设备、存储介质

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 18865670

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 07/09/2020)

122 Ep: pct application non-entry in european phase

Ref document number: 18865670

Country of ref document: EP

Kind code of ref document: A1