CN108830470B

CN108830470B - Account processing method and device

Info

Publication number: CN108830470B
Application number: CN201810557478.2A
Authority: CN
Inventors: 徐诚成; 李宏辉
Original assignee: Beijing Kingsoft Software Co Ltd; Beijing Kingsoft Digital Entertainment Co Ltd
Current assignee: Beijing Kingsoft Software Co Ltd; Beijing Kingsoft Digital Entertainment Co Ltd
Priority date: 2018-06-01
Filing date: 2018-06-01
Publication date: 2023-05-02
Anticipated expiration: 2038-06-01
Also published as: CN108830470A

Abstract

The embodiment of the invention provides a method and a device for processing accounts, which are used for solving the problems that in the prior art, the accounts of systems required by each employee are numerous and different, and management staff manually call the systems of enterprises, so that more information needs to be processed manually and the processing efficiency is low. The account processing method is applied to a main system, wherein the main system is provided with one and/or a plurality of subsystems, and the method comprises the following steps: acquiring an execution instruction of the established account processing task; and executing the account processing task based on the execution instruction, wherein the account processing task is used for processing an account of a user to be processed in a registered subsystem, and the registered subsystem registers the account for the user to be processed.

Description

Account processing method and device

Technical Field

The present invention relates to the field of information processing, and in particular, to a method and an apparatus for processing an account.

Background

At present, with the development of enterprises, the scale of the enterprises is continuously enlarged, the personnel flow is large, and an enterprise management system is established for enhancing enterprise management. Enterprise management regimes vary from enterprise to enterprise. However, different enterprises can have personnel flowing, such as employee departure or employee arrival, so that unified management of information related to the flowing personnel is needed, and information security is further protected. Thus, a general enterprise management regime includes: employee's job entry system and employee's job departure system. The employee's job-in system and employee's job-out system are described in detail below.

Staff's job entry system: after the employee is entered, the employee may be assigned an account of the system for use by his job. The account numbers of the systems required for each employee to use are different, and the account numbers of the systems used by the employees are uniformly managed by the manager. When someone needs to leave, the employee needing to leave needs to go on leave approval first. Employee departure system: after the leave approval passes, the manager manually invokes the system used by the enterprise for the staff who have passed the leave approval. In the invoked systems used by these enterprises, the account numbers of the systems used by the staff having passed the job leave approval are manually searched and logged off.

However, in the process of implementing the present invention, the inventor finds that the enterprise management system in the prior art completes the job entering of the staff and the job leaving of the staff, and at least has the following problems:

because of the large number of systems used by enterprises, the systems used are, for example, business systems, attendance systems, financial systems, instant messaging systems, and the like. Each staff has different functions, the systems used by different functions are different, so that the accounts of the systems required by each staff are numerous and different, the manager manually calls the systems used by the enterprises, more information is needed to be processed manually, and the processing efficiency is low.

Disclosure of Invention

The embodiment of the invention aims to provide an account processing method and device, which are used for solving the problems that in the prior art, accounts of systems required by each employee are numerous and different, management staff manually call the systems of enterprises, information required to be manually processed is more, and processing efficiency is lower. The specific technical scheme is as follows:

in a first aspect, the present invention provides an account processing method, applied to a main system, where the main system has one and/or more subsystems, the method includes:

acquiring an execution instruction of the established account processing task;

and executing the account processing task based on the execution instruction, wherein the account processing task is used for processing an account of a user to be processed in a registered subsystem, and the registered subsystem registers the account for the user to be processed.

Further, the acquiring the execution instruction of the created account processing task includes:

and acquiring an execution instruction of the account processing task sent by the task scheduling server.

acquiring an execution instruction of an established account processing task in a main system;

Based on the execution instruction, executing the account processing task, including:

judging whether the starting time point of the account processing task arrives or not based on the execution instruction;

and when the starting time point is judged to be reached, executing the account processing task, wherein the account processing task is used for processing an account of a user to be processed in a registered subsystem, and the registered subsystem registers an account for the user to be processed.

Further, the executing the account processing task includes:

obtaining a user account list, wherein the user account list comprises the following steps: account numbers of all users in all subsystems;

searching an account number of the user to be processed in the registered subsystem in the user account number list;

and sending an account processing request to the registered subsystem, wherein the account processing request carries an account of the user to be processed in the registered subsystem, and the account processing request is used for requesting the registered subsystem to process the account of the user to be processed in the registered subsystem.

Further, the account processing task includes: the first account processing task and the second account processing task; the starting time point includes: a starting time point of the first account processing task and a starting time point of the second account processing task after the starting time point of the first account processing task;

The method comprises the following steps of creating an account processing task:

acquiring a user subsystem grade list of a user to be processed; the user subsystem grade list of the user to be processed is a list formed according to the importance grade of the registered subsystem of the user to be processed;

processing an account in a subsystem of which the user to be processed is registered with a first preset importance level, and creating a first account processing task;

processing the account numbers in the subsystem of which the user to be processed is registered with a second preset importance level, and creating a second account number processing task, wherein the first preset importance level is higher than the second preset importance level;

when the starting time point is judged to be reached, executing the account processing task, wherein the account processing task comprises the following steps:

executing the first account processing task when judging that the starting time point of the first account processing task arrives;

and executing the second account processing task when the starting time point of the second account processing task is judged to be reached.

Further, when it is determined that the starting time point of the first account processing task arrives, executing the first account processing task includes:

When the starting time point of the first account processing task is judged to be reached, a user subsystem grade list is obtained;

traversing the user subsystem level list, and searching a subsystem of which the user to be processed is registered with a first preset importance level;

an account processing request is sent to a subsystem of the first preset importance level, the account processing request carries an account of the subsystem of the first preset importance level, and the account processing request is used for requesting the subsystem of the first preset importance level to process an account of the user to be processed in the subsystem of the first preset importance level;

and when the starting time point of the second account processing task is judged to arrive, executing the second account processing task, wherein the method comprises the following steps:

when the starting time point of the second account processing task is judged to be reached, a user subsystem grade list is obtained;

traversing the user subsystem level list, and searching a subsystem of which the user to be processed is registered with a second preset importance level;

and sending an account processing request to the subsystem of the second preset importance level, wherein the account processing request carries an account in the subsystem of the second preset importance level, and the account processing request is used for requesting the subsystem of the second preset importance level to process the account of the user to be processed in the subsystem of the second preset importance level.

Further, the executing the account processing task includes:

and respectively sending an account processing request to each subsystem, wherein the account processing request carries an account of the user to be processed, and the account processing request is used for determining whether the subsystem is a registered subsystem of the user to be processed or not based on the account by the subsystem, and processing the account of the user to be processed in the subsystem when the subsystem is the registered subsystem of the user to be processed.

Further, the number of registered subsystems of the user to be processed is a plurality, and after the account processing task is executed, the method further includes:

receiving an execution result returned by the registered subsystem of the user to be processed, wherein the execution result is obtained by processing an account of the user to be processed in the registered subsystem by the registered subsystem of the user to be processed aiming at the account processing request;

if the execution result contains a processing identifier for indicating incomplete processing, displaying prompt information, wherein the prompt information is used for prompting the registered subsystem of the user to be processed, and the account number of the user to be processed in the registered subsystem is not complete in processing;

And if the execution result contains processing identifiers for indicating all the processing is completed, processing the account numbers of the users to be processed in a registered host system, wherein the registered host system is a host system in which the account numbers of the users to be processed are registered.

In a second aspect, the present invention provides an account processing apparatus, applied to a main system, where the main system has one and/or more subsystems, the apparatus includes:

the acquisition module is used for acquiring an execution instruction of the established account processing task;

and the execution module is used for executing the account processing task based on the execution instruction, wherein the account processing task is used for processing the account of the user to be processed in a registered subsystem, and the registered subsystem registers the account for the user to be processed.

Further, the obtaining module is specifically configured to:

the execution module is specifically configured to:

Further, the execution module is specifically configured to:

The device also comprises a creation module, wherein the creation module is used for creating account processing tasks by adopting the following steps:

the execution module is specifically configured to:

Further, the execution module is specifically configured to:

the execution module is specifically configured to:

Further, the execution module is specifically configured to:

Further, the number of registered subsystems of the user to be processed is a plurality, and the device further comprises:

the receiving module is used for receiving an execution result returned by the registered subsystem of the user to be processed after the account processing task is executed when the starting time point is judged to be reached, wherein the execution result is obtained by processing an account of the user to be processed in the registered subsystem by the registered subsystem of the user to be processed aiming at the account processing request;

In a third aspect, the present invention provides an electronic device, including a processor, a communication interface, a memory, and a communication bus, where the processor, the communication interface, and the memory complete communication with each other through the communication bus;

a memory for storing a computer program;

and a processor, configured to implement the method steps described in the first aspect when executing the program stored in the memory.

In a fourth aspect, the present implementations provide a computer-readable storage medium having instructions stored therein that, when executed on a computer, cause the computer to perform the method of any of the first aspects described above.

In a fifth aspect, the present implementations also provide a computer program product containing instructions which, when run on a computer, cause the computer to perform the method of any of the first aspects described above.

In a sixth aspect, embodiments of the present invention provide a computer program which, when run on a computer, causes the computer to perform the method steps described in the first aspect above.

The embodiment of the invention provides an account processing method and device, which are used for acquiring an execution instruction of an established account processing task; based on the execution instruction, executing an account processing task, wherein the account processing task is used for processing an account of a user to be processed in a registered subsystem, and the registered subsystem registers the subsystem with the account for the user to be processed.

Therefore, the account processing task is executed, management personnel are not required to manually call the system of the enterprise, the information required to be processed manually is less, and the processing efficiency is higher.

Of course, it is not necessary for any one product or method of practicing the invention to achieve all of the advantages set forth above at the same time.

Drawings

In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings required in the description of the embodiments or the prior art will be briefly described below.

Fig. 1 is a schematic flow chart of a method for processing an account according to an embodiment of the present invention;

fig. 2 is a schematic diagram of a specific flow for executing an account processing task according to an embodiment of the present invention;

FIG. 3 is a flowchart illustrating the process after step 120 in FIG. 1 according to an embodiment of the present invention;

fig. 4 is a flowchart of a specific application example of an account processing method according to an embodiment of the present invention;

Fig. 5 is a schematic structural diagram of an apparatus for account processing according to an embodiment of the present invention;

fig. 6 is a schematic structural diagram of an electronic device according to an embodiment of the present invention.

Detailed Description

The technical solutions in the embodiments of the present invention will be described below with reference to the accompanying drawings in the embodiments of the present invention.

First, in order to facilitate understanding of the embodiments of the present invention, the terms "main system", "subsystem", "registered subsystem", "account number of subsystem", "account number processing task" and "start time point" will be described herein.

A host system may refer to one host system and/or a plurality of host systems. The plurality of main systems belong to the same class system and have no inclusion relation. For example, one host system is an OA (Office Automation System, office automation) system, and one host system is a pasm (Public Administration service module, unified user management public service module).

Each host system has one and/or more subsystems. The association between the main system and the subsystem is pre-established, and the same account number is registered in the main system and the subsystem by way of example. Further, the host system is an OA system, and the host system has a plurality of subsystems, the plurality of subsystems including: instant messaging software system, mailbox system and user preset system. The instant messaging software system comprises: an instant messaging software system of an external network and an instant messaging software system of an internal local area network. A user presets a system such as an attendance system, a financial system. Further, the host system is pasm, and the host system has a plurality of subsystems, and the plurality of subsystems includes: doms (Daily Operation Management System, daily operation and maintenance management system), a reporting system and a user preset system. These user preset systems may be set according to user needs, which is not illustrated herein.

The host system is provided with a plurality of users, each user registers an account in the host system, and the host system with the registered account is called a registered host system. When each user needs to use the subsystem, the user also needs to register in the subsystem, and the subsystem of the registered account is called a registered subsystem. The subsystems used by different users can be the same or different, and the subsystem depends on actual conditions. Some users may use all of the subsystems, some users may use some of the subsystems, and the number of subsystems used by a particular user is determined by the needs of the user. For example, the user requirement is a job requirement of the user, for example, for the job of the user to be cashier, the subsystem of cashier requirement includes: a financial system. Since multiple subsystems may be used by different users, a user may have multiple subsystems' accounts. In this way, the account numbers of a plurality of subsystems of a user are required to be associated with the account numbers registered by the main system of the user, and then the account number processing task can be executed in the main system, and the registered subsystem processes the account numbers of the user to be processed in the registered subsystem so as to process the account numbers of the user to be processed in the registered subsystem.

The above-mentioned multiple account numbers of subsystem of a user and the account number registered by the main system of the user are related in various ways, in order to facilitate executing account processing tasks in the main system, and implement unified management of the main system and subsystem, where one way of establishing the relationship includes: for each user in the host system, the host system may use a unique account identifier to indicate that the user has an account registered in the host system, and the subsystem may use the same unique account identifier as the host system to indicate that the user has an account in the subsystem. Unique account identifiers such as account numbers, assuming that two user names are Zhang three, in order to distinguish the two user names, zhangsan1 and zhangsan2 may be used to identify the two user names respectively. The account number is zhangsan1, zhangsan2, lisi, wangwu and the like; the unique account number identifies, for example, an identity code, which is a digital number, such as 001, 002, etc. The account numbers of a plurality of subsystems of the user and the account numbers registered by the main system of the user use the same account number, and the account numbers of the users to be processed in the registered subsystems are processed.

In order to process accounts of the same user to be processed in a registered subsystem, an account processing task is created in advance, wherein the registered subsystem is a subsystem in which the user to be processed registers an account. The user to be processed may refer to one or more users, among the multiple users of the host system, that need to process the account numbers in the registered subsystem. The account processing task of the embodiment of the invention is used for processing the account of the same user to be processed in the registered subsystem. In this way, the account numbers in the registered subsystem may be processed for each user to be processed.

Further, the account processing task may include: modifying the account number of the user to be processed in the registered subsystem, checking the account number of the user to be processed in the registered subsystem, and logging off the account number of the user to be processed in the registered subsystem. Any mode of processing the account number of the user to be processed in the registered subsystem can be realized according to industrial requirements or user requirements, and execution belongs to the protection scope of the embodiment of the invention, and the implementation is not exemplified one by one.

The account processing task is used for processing the account of the user to be processed in a registered subsystem, and the registered subsystem registers the subsystem with the account for the user to be processed. Further, the account processing task may include: the first account processes the task and the second account processes the task. Dividing the account processing task into a first account processing task and a second account processing task, wherein the first account processing task can be part of account processing tasks of the same user to be processed, and the corresponding second account processing task can be the same user to be processed, and the account processing tasks except the rest account processing tasks in the first account processing task. In this way, account processing tasks can be divided into two batches, and then accounts of the users to be processed in the registered subsystem are processed.

Of course, besides dividing account processing tasks into two batches, account processing tasks can be divided into P batches, wherein P is greater than or equal to 3, and account processing tasks can be divided into a first account processing task, a second account processing task and a P account processing task, so that the first account processing task can be part of account processing tasks of the same user to be processed, the corresponding second account processing task can also be the same user to be processed, and part of account processing tasks in the account processing tasks except for the rest account processing tasks in the first account processing task can be divided into the first account processing task. Therefore, the account processing tasks can be divided into three batches, the account processing tasks can also be divided into P batches, the task amount for processing the account processing tasks of the user to be processed each time is relatively small, and the account of the user to be processed in the registered subsystem can be processed subsequently. Relational terms such as first and second, and the like herein are used solely to distinguish "first account processing task," second account processing task, "and" P-th account processing task, "and do not necessarily require or imply that any such actual relationship or order exists between" first account processing task, "" second account processing task, "and" P-th account processing task. The order of the specific "first account processing task", "second account processing task" and "P-th account processing task" may be defined according to actual situations.

Setting a starting time point of the account processing task for the account processing task, wherein the starting time point can be set according to the requirement of a user. When the user to be processed is a person to be departed, starting a time point such as a time point of the last job departure working day of the person to be departed; starting time point again, for example, 24 of last job-leaving workday of the person waiting for job-leaving: 00. in this way, the set starting time point can be judged to be reached, and the main system executes account processing tasks.

The starting time point may include: a starting time point of the first account processing task and a starting time point of the second account processing task after the starting time point of the first account processing task. The number of the starting time points is the same as the number of the account processing tasks divided by the account processing tasks. The first account processing task, the second account processing task, and the P-th account processing task may be referred to as divided account processing. A starting time point is allocated to a divided account processing task, so that a divided account processing can be executed according to the respective starting time point.

The following describes an account processing method provided by the embodiment of the invention.

In combination with the above application description of the account processing method according to the embodiment of the present invention, details of the account processing method according to the embodiment of the present invention are described below.

Referring to fig. 1, fig. 1 is a schematic flow chart of a method for processing an account according to an embodiment of the present invention. The account processing method provided by the embodiment of the invention can comprise the following steps:

step 110, acquiring an execution instruction of the created account processing task. The execution instruction is used to trigger the host system, and step 120 is executed subsequently.

Step 120, based on the execution instruction, executing an account processing task, where the account processing task is used to process an account of a user to be processed in a registered subsystem, and the registered subsystem registers an account of the user to be processed.

In order to obtain the execution instruction in time and execute the account processing task in real time, in the step 110, the execution instruction of the created account processing task may be obtained by the following first implementation manner:

in a first implementation, a host system obtains an execution instruction of an account processing task input by a user.

Accordingly, in step 120, it is determined that the execution instruction is to immediately execute the account processing task using the execution instruction, where the execution instruction does not carry a starting time point of the account processing task. And executing the account processing task by using the execution instruction. Therefore, the main system can directly acquire the execution instruction, continue to execute the account processing task, and execute the account processing task in real time.

Not all the account processing tasks need to be executed in real time, and for some account processing tasks, the account processing tasks need to be executed at the starting time point of the account processing tasks, so in order to execute the account processing tasks at the starting time point of the account processing tasks, in this step 110, the execution instruction of the created account processing tasks may be obtained through the following second implementation manner:

in a second implementation manner, step 11, the main system acquires an execution instruction of an account processing task created in the main system;

correspondingly, the step 120 specifically includes: step 21, the main system executes step 22 if the execution instruction carries the starting time point of the account processing task and judges whether the starting time point of the account processing task arrives or not based on the execution instruction, and continues to execute step 21 if the starting time point of the account processing task does not arrive.

And 22, when the starting time point is judged to be reached, executing an account processing task by the main system, wherein the account processing task is used for processing accounts of the users to be processed in a registered subsystem, and the registered subsystem is a subsystem in which the accounts of the users to be processed are registered. The main system judges whether the starting time point of the account processing task is reached, and executes the account processing task when the starting time point of the account processing task is reached.

In order to enable the host system of the embodiment of the present invention to implement the trigger execution instruction by itself to implement the execution of the account processing task, the host system includes: the task scheduling server may acquire the execution instruction of the created account processing task in this step 110 through the following third implementation manner:

in a third implementation manner, in step 31, the main system acquires an account processing task created in the main system and a starting time point of the account processing task;

and step 32, the main system sends the created account processing task and the starting time point of the account processing task to a task scheduling server, the task scheduling server judges whether the starting time point of the account processing task is reached, and when the starting time point is judged to be reached, the main system sends an execution instruction of the created account processing task. The main system of the embodiment of the invention comprises a task scheduling server in a third implementation mode of the embodiment of the invention. The main system is equivalent to a task scheduling server through an integrated module in the main system, so that the main system can execute account processing tasks.

And 33, the main system acquires an execution instruction of the account processing task sent by the task scheduling server.

Correspondingly, the step 120 specifically includes: and step 23, judging that the execution instruction is immediately used for executing the account processing task, wherein the execution instruction does not carry a starting time point of the account processing task, and based on the execution instruction, the main system executes the account processing task.

In order to enable interaction between other devices and the host system of the embodiment of the present invention to implement an account processing task, where the other devices may be task scheduling servers, in step 110, the execution instruction of the created account processing task may be obtained through the following fourth implementation manner:

in a fourth implementation, an execution instruction of an account processing task sent by a task scheduling server is acquired. The task scheduling server is used for triggering the main system to execute the account processing tasks. The execution instruction does not carry a starting time point of the account processing task.

The task scheduling server in the fourth implementation manner of the embodiment of the present invention and the main system of the embodiment of the present invention belong to the same class of devices, and have no inclusion relationship. Equivalently, other devices at the same level trigger the main system of the embodiment of the invention, so that the main system executes the account processing task. The task scheduling server can judge whether the starting time point of the account processing task reaches or not by itself, and can also issue an execution instruction of the account processing task by itself. The task scheduling server only needs to establish a communication relation with the main system of the embodiment of the invention in advance so as to realize interaction between the task scheduling server and the main system of the embodiment of the invention. In a fourth implementation manner of the present invention, the task scheduling server may trigger the host system to execute the account processing task.

In order to accurately acquire the execution instruction, the following various acquisition modes can be adopted to acquire the execution instruction of the account processing task sent by the task scheduling server:

in the first step, a main system obtains an established account processing task in advance and sends the account processing task and a starting time point of the account processing task to a task scheduling server;

And a second step of receiving an execution instruction of the account processing task sent by the task scheduling server, wherein the execution instruction is sent when the task scheduling server judges that the starting time point arrives. In this way, the main system is equivalent to the transfer position of an account processing task, the task scheduling server judges the starting time point of the account processing task, and when the task scheduling server judges that the starting time point is reached, the task scheduling server sends an execution instruction to the main system, so that the main system can accurately receive the execution instruction of the task scheduling server.

According to the embodiment of the invention, management personnel are not required to manually call the enterprise system, the information required to be manually processed is less, and the processing efficiency is higher.

Aiming at the problems that in the prior art, the main system processes accounts of all registered subsystems in the main system in batches, the pressure of the main system is higher and the processing efficiency is lower, in order to solve the problems, the embodiment of the invention can adopt at least one implementation mode to create account processing tasks, wherein the account processing tasks are created for each user to be processed:

in one implementation, first, a user subsystem list of a user to be processed is obtained from a plurality of user subsystem lists; the user subsystem list of the user to be processed is a list formed by registered subsystems of the user to be processed. The plurality of user subsystem lists herein may be pre-stored. For example, referring to table 1, table 1 is a list of user subsystems, the main system having subsystems comprising: subsystem a, subsystem B, subsystem C, and subsystem D. The list of user subsystems includes: account identification and the condition of registered subsystems corresponding to each account identification. The case that each account identifies the corresponding registered subsystem includes: registered subsystem A, registered subsystem B, registered subsystem C, registered subsystem D; the users to be processed comprise: a user S to be processed and a user P to be processed.

TABLE 1

In table 1 above, the registered subsystem of zhangsan1 includes: registered subsystem A, registered subsystem B and registered subsystem C; the registered subsystem of the pending subscriber S comprises: registered subsystem a and registered subsystem B; the registered subsystem of zhangsan2 includes: registered subsystem A, registered subsystem B, registered subsystem C, and registered subsystem D; the registered subsystem of the pending user P comprises: registered subsystem D. Table 1 illustrates that only zhangsan2 uses all of the subsystems of the main system, and the remaining users use some of the subsystems of the main system. Table 1 also illustrates that the case of the registered subsystems corresponding to the user S to be processed and the user P to be processed is included, so that the user subsystem of the user to be processed can be found out from this table 1, and the user subsystem of the user to be processed is formed into a list as the user subsystem list of the user to be processed. For example, referring to table 2, table 2 is a list of user subsystems for users to be processed.

TABLE 2

And secondly, processing the account number of the subsystem registered by the user to be processed, and creating an account number processing task. Therefore, the account numbers of the registered subsystems of the users to be processed can be processed, the account numbers of the registered subsystems of the users to be processed are created into an account number processing task, the account numbers of the registered subsystems of the users to be processed are processed in a targeted and unified mode by utilizing the user subsystem list of the users to be processed, the efficiency of processing the account number processing task is improved, and the pressure of unified processing of the account numbers of all the registered subsystems in the main system is reduced.

In the above-mentioned implementation manner, the account numbers of the same user to be processed in the registered subsystem are processed, if there may be work which is not completed in the registered subsystem of the user to be processed, then the account numbers of the same user to be processed in the registered subsystem are directly processed in batches, for example, log-off, which may cause the problems that the work handover is not completed or the work cannot be completed, etc., so in order to solve the problem, the embodiment of the present invention may use the following second implementation manner to create the account number processing task:

in a second implementation, the account processing tasks include: the first account processing task and the second account processing task; the starting time point comprises: a starting time point of the first account processing task and a starting time point of the second account processing task after the starting time point of the first account processing task.

The method comprises the steps of firstly, obtaining a user subsystem grade list of a user to be processed; the user subsystem level list of the user to be processed is a list formed according to the importance level of the registered subsystem of the user to be processed.

Wherein, the user subsystem level list of the user to be processed comprises: the subsystem of the first preset importance level is registered by the user to be processed, and the subsystem of the second preset importance level is registered by the user to be processed. The user subsystem level of the user to be processed may be a user set level. The first preset importance level is higher than the second preset importance level. The importance may be determined according to the user's role. Illustratively, the user to be processed is a person to be moved away, and the user subsystem of the person to be moved away includes, for the job of the person to be moved away to a cashier: financial system, attendance system. And taking the financial system as a subsystem of a first preset importance level. The financial system comprises: payment system and collection system. And taking the attendance checking system as a subsystem of a second preset importance level.

The importance may also be determined according to the importance preset by the user, where the importance set for the registered subsystem dedicated to all the users to be processed is a first preset importance level, and the importance set for the registered subsystem common to all the users to be processed is a second preset importance level. The registered subsystem which is common to all users to be processed can be a registered subsystem which can be used by all users of the enterprise; such as an attendance system, a public system. All registered subsystems specific to the user to be processed may be systems other than registered subsystems common to the user to be processed.

The importance may also be determined by the completion of the work of the registered subsystem. When the work completion conditions of the registered subsystems are completed, the importance set for the registered subsystems is a first preset importance level, and when the work completion conditions of the registered subsystems are incomplete, the importance set for the registered subsystems is a second preset importance level.

The importance may also be determined by using an identifier of a preset importance according to a user requirement, where the importance required by the user may be set to a first preset importance level for a part of the plurality of subsystems of the main system, and the identifier of the first preset importance is set. The importance set by another subsystem of the subsystems of the main system is a second preset importance level, and the identifier of the second preset importance is set for the user. In this way, subsystems with different preset importance levels can be found through the marks with preset importance.

And secondly, processing the account numbers in the subsystem of which the user to be processed is registered with the first preset importance level, and creating a first account number processing task.

Thirdly, processing the account numbers in the subsystem of which the user to be processed is registered with a second preset importance level, and creating a second account number processing task, wherein the first preset importance level is higher than the second preset importance level. Therefore, all accounts of the same user to be processed are logged off in batches, and are processed according to the user subsystem level of the user to be processed, so that incomplete processing, such as forced logging off of a registered subsystem of incomplete work, is avoided, the requirement for sequential processing of the user subsystem level is met, the account processing tasks are processed in batches, the processing efficiency is improved, and the centralized processing pressure of a main system is reduced.

In order to satisfy the processing of the account number in the registered subsystem in multiple manners, in step 120, the account number in the registered subsystem of the user to be processed in the plurality of users in the host system is processed in one or more of the following manners:

in the first way, the account number of the user to be processed in the registered subsystem is checked. The user to be processed logs in the main system by using the account registered by the main system, then the main system executes an account processing task, and the account of the user to be processed in the registered subsystem is read by the account of the registered subsystem so as to check the account in the registered subsystem.

And in a second mode, the account number of the user to be processed in the registered subsystem is logged off. The user to be processed logs in the main system by using the account registered by the main system, then the main system executes an account processing task, and the account of the registered subsystem logs out of the account of the user to be processed in the registered subsystem so as to log out the account in the registered subsystem.

And in a third mode, modifying the account number of the user to be processed in the registered subsystem. The method for modifying the account number of the user to be processed in the registered subsystem comprises the following steps: and modifying the account number of the user to be processed in the registered subsystem. The user to be processed uses the account registered by the main system to log in the main system, then the main system executes the account processing task, and the account of the registered subsystem is used for modifying the account of the user to be processed in the registered subsystem so as to modify the account in the registered subsystem.

In order to directly send an account processing request to a registered subsystem of a user to be processed, the account of the user to be processed in the registered subsystem is prevented from being omitted, and the accuracy of processing the account in the registered subsystem can be improved. Referring to fig. 2, fig. 2 is a schematic flowchart of an embodiment of the present invention for executing an account processing task. In this step 120, at least one possible implementation manner is adopted to execute an account processing task, including:

In a first possible implementation manner, step 121, a user account list is obtained, where the user account list includes: account numbers of users in the subsystems. The list of user accounts here may be pre-stored. For example, referring to table 3, table 3 is a user account list, which includes: an account number identifier and an account number of a subsystem which each account number identifier has in the main system. The subsystem that the main system had includes: subsystem a, subsystem B, subsystem C, and subsystem D. The registered subsystem includes: registered subsystem A, registered subsystem B, registered subsystem C, and registered subsystem D. The users to be processed comprise: a user S to be processed and a user P to be processed.

TABLE 3 Table 3

In Table 3 above, the registered subsystem of zhangsan1 includes: registered subsystem A, registered subsystem C and registered subsystem D; the registered subsystem of the pending subscriber S comprises: registered subsystem a and registered subsystem C; the registered subsystem of zhangsan2 includes: registered subsystem A, registered subsystem B and registered subsystem C; the registered subsystem of the pending user P comprises: registered subsystem C. Table 3 illustrates that, for each user registered with the host system, the registered subsystem has an account number of the respective subsystem, for example, the account number of the registered subsystem A of the user S to be processed is 13456; the account number of the registered subsystem C of the user S to be processed is 24567, but the registered subsystems of the user S to be processed all use the account number of the user P to be processed as an account number identifier. And, the user account of the user to be processed can be found out from the table 3, and the user account of the user to be processed is formed into a list as the user account list. For example, referring to table 4, table 4 is a list of user accounts for users to be processed.

TABLE 4 Table 4

Step 122, searching the account number of the user to be processed in the registered subsystem in the user account number list.

The step 122 specifically includes: according to the account numbers of the users to be processed, searching the account numbers of the users to be processed in the registered subsystem in the user account number list. Thus, the account number of the user to be processed in the registered subsystem can be conveniently and rapidly found according to the account number of the user to be processed.

Step 123, an account processing request is sent to the registered subsystem, wherein the account processing request carries an account of the user to be processed in the registered subsystem, and the account processing request is used for requesting the registered subsystem to process the account of the user to be processed in the registered subsystem.

In the first possible implementation manner, according to the account number of the user to be processed, the account number of the user to be processed in the registered subsystem is conveniently and rapidly found, and an account number processing request is sent to the registered subsystem, so that the efficiency of processing the account number of the user to be processed in the registered subsystem is improved.

In the second possible implementation manner, the main system and the subsystems of the main system may be collectively referred to as a system, so as to solve the problem that, if there is a possibility that the account number of the same user to be processed in the registered subsystem has not completed yet, the account number of the same user to be processed in the registered subsystem is directly processed in batch, for example, log-off, which may cause incomplete work handover or failure to do incomplete work. The first step, a user subsystem level list of users to be processed comprises: the method comprises the steps of registering a subsystem with a first preset importance level of a user to be processed and registering a subsystem with a second preset importance level of the user to be processed, wherein the first preset importance level is higher than the second preset importance level. And when the starting time point of the first account processing task is judged to be reached, executing the first account processing task. The account numbers of the registered subsystems of the users to be processed are processed in batches, so that the processing efficiency of the account numbers of the registered subsystems of the users to be processed is improved, the pressure of the system is reduced, and the defect that the work handover is incomplete or the incomplete work cannot be performed due to the fact that the unified time logout occurs is avoided.

The first step specifically includes: when the starting time point of the first account processing task is judged to be reached, a user subsystem grade list is obtained; traversing a user subsystem level list, and searching a subsystem of which the user to be processed is registered with a first preset importance level; and sending an account processing request to the subsystem with the first preset importance level, wherein the account processing request carries an account of the subsystem with the first preset importance level, and the account processing request is used for requesting the subsystem with the first preset importance level to process the account of the user to be processed in the subsystem with the first preset importance level.

And a second step of executing the second account processing task when the starting time point of the second account processing task is judged to be reached.

The second step specifically includes: when the starting time point of the second account processing task is judged to be reached, a user subsystem grade list is obtained; traversing a user subsystem level list, and searching a subsystem of which the user to be processed is registered with a second preset importance level; and sending an account processing request to a subsystem of the second preset importance level, wherein the account processing request carries an account in the subsystem of the second preset importance level, and the account processing request is used for requesting the subsystem of the second preset importance level to process the account of the user to be processed in the subsystem of the second preset importance level.

Illustratively, the user to be processed is a person to be moved away, and the registered subsystem of the person to be moved away includes, for the job of the person to be moved away to a cashier: financial system, attendance system. And taking the financial system as a subsystem of a first preset importance level. The financial system comprises: payment system and collection system. And taking the attendance checking system as a subsystem of a second preset importance level.

The registered subsystem logs off accounts of staff to be logged off in the registered subsystem, and the account logged off the financial system is established as a first account processing task; and creating an account of the log-out attendance system as a second account processing task. The starting time point of the first account processing task of the person to be departed is set to be the off-duty time point of the last off-duty working day of the person to be departed, namely, the 18 points of 5 months and 5 days in 2018; the starting time point of the first account processing task of the person to be departed is set to be 24 points of 2018, 5 months and 5 days of the last departure working day of the person to be departed.

And executing the first account processing task when the 2018, 5 and 18 points of the starting time point of the first account processing task are judged to be reached. And executing the second account processing task when the 2018, 5 and 24 points of the starting time point of the second account processing task are judged to be reached. Therefore, the problems that the time for logging out the account number of the subsystem registered by the personnel waiting for departure in the concentrated time is long and the system pressure is high can be avoided. The account numbers of the subsystem registered by the personnel to be separated are successively logged off in batches, so that the processing efficiency of the account numbers of the subsystem registered by the personnel to be separated is improved, the pressure of the system is reduced, and the defect that the work handover is incomplete or incomplete work cannot be performed due to unified time logging off is avoided.

In the second possible implementation manner, the accounts of the registered subsystems of the users to be processed are processed in batches according to the importance level, so that the processing efficiency of the accounts of the registered subsystems of the users to be processed is improved, the pressure of the system can be reduced, and the defect that the work handover is incomplete or the incomplete work cannot be performed due to uniform time cancellation is avoided.

In order to solve the problem that in the above implementation manner, the account processing task may be omitted when the registered subsystem processes the account processing task, step 120 of the embodiment of the present invention may further adopt a third possible implementation manner, where the executing the account processing task includes:

in a third possible implementation manner, an account processing request is sent to each subsystem, where the account processing request carries an account of the user to be processed, and the account processing request is used for determining, by the subsystem, whether the subsystem is a registered subsystem of the user to be processed based on the account, and when the subsystem is a registered subsystem of the user to be processed, processing the account of the user to be processed in the subsystem. The method is equivalent to traversing all subsystems, and then the registered subsystem which is the user to be processed is used for processing the account number of the user to be processed in the registered subsystem. The user is not a registered subsystem of the user to be processed, and the account number of the user to be processed in the user can be processed.

The sending the account processing request to each subsystem includes: the host system broadcasts or mass-transmits account processing requests to the subsystems. Therefore, the main system does not need to judge which registered subsystem the account number of the registered subsystem of the user to be processed is, the processing steps of the main system are reduced, and the efficiency of the main system for respectively sending the account number processing requests to each subsystem is improved.

In order to facilitate the main system to send account processing requests to all subsystems, the embodiment of the present invention may send account processing requests to each subsystem respectively by the following steps, including:

and the main system respectively sends account processing requests to the subsystems by calling interfaces of the subsystems.

For the above steps, interfaces of the subsystems can be used, and account processing requests can be sent to the subsystems respectively, so that in order to specifically realize that account processing requests can be sent to all the subsystems, the embodiment of the invention includes the following steps that the main system sends account processing requests to the subsystems respectively by calling the interfaces of the subsystems, including:

and the main system sequentially and respectively sends account processing requests to the subsystems according to the interfaces of the subsystems by calling the interfaces of the subsystems.

Based on the main system, according to the interfaces of the subsystems, the account processing requests are sent to the subsystems in turn respectively, and the problem of lower sending efficiency exists, so in order to solve the problem, the embodiment of the invention adopts the following steps that the main system respectively sends the account processing requests to the subsystems by calling the interfaces of the subsystems, and the method comprises the following steps:

the main system adopts multithreading to call the interfaces of all the subsystems, and according to the interfaces of all the subsystems, the main system adopts multithreading to respectively send account processing requests to all the subsystems. Therefore, the multi-thread is used for sending the account processing request to each subsystem, the account processing request can be sent to each subsystem as soon as possible, and the response of each subsystem can be obtained as soon as possible later.

In a third possible implementation manner, all subsystems are traversed to avoid missing registered subsystems of the user to be processed, so that the registered subsystems which are the user to be processed are realized, and account numbers of the user to be processed in the user to be processed are processed.

Referring to fig. 3, fig. 3 is a flowchart illustrating a process after step 120 in fig. 1 according to an embodiment of the present invention. In one possible implementation manner of the embodiment of the present invention, after the step 120, the method further includes:

And 130, receiving an execution result returned by the registered subsystem of the user to be processed, wherein the execution result is obtained by processing the account of the user to be processed in the registered subsystem by the registered subsystem of the user to be processed aiming at the account processing request.

Step 140, judging whether the execution result contains a processing identifier indicating that the processing is not completed, if yes, executing step 150, if not, that is, the execution result contains all the processing identifiers for completing the processing, wherein all the processing identifiers for completing the processing indicate that all the accounts of the user to be processed in the registered subsystem are completed, and executing step 160;

and 150, displaying prompt information, wherein the prompt information is used for prompting the registered subsystem of the user to be processed, and the account number of the user to be processed in the registered subsystem is not processed.

The processing identifier includes: the processing identifier of the incomplete processing and the processing identifier of the completed processing. The processing identifier of this incomplete processing may be text, such as True; similarly, the processing identifier after processing may be text, for example, false, so that the text is used as the processing identifier, the processing identifier of the text may be converted into binary data, and the binary data after conversion is compiled into computer code, thereby facilitating identification of the computer code.

The process identification of incomplete processing may also be a number, such as 1; similarly, the process identifier for completing the process may also be a number, such as 0. Thus, 0 and 1 in the number are used as processing identifications, the 0 and 1 in the number are in accordance with binary data, and the binary data is conveniently utilized to compile the computer code, so that the computer code can be conveniently identified. Any processing identifier capable of implementing the embodiments of the present invention belongs to the protection scope of the embodiments of the present invention, which is not limited to the examples. Using these process identifications, a determination can be made as to whether to continue processing the account registered by the host system or whether to indicate that the processing of the account in the registered subsystem is complete.

Because the account number in the unfinished processing registered subsystem of the user to be processed needs to be displayed to the user, in order to facilitate the user to read and grasp the situation of unfinished processing of the account number of the user to be processed in the registered subsystem, the prompt information can be words, prompt the registered subsystem of the user to be processed, and the processing of the account number of the user to be processed in the registered subsystem is unfinished, for example, the words are unfinished processing; the hint information may also be a process identifier of the incomplete process. The description is not given here, and as long as the registered subsystem of the user to be processed can be prompted, the prompt information that the account number of the user to be processed in the registered subsystem is not processed is all included in the protection scope of the embodiment of the present invention.

If the prompt information indicates that the account number of the user to be processed in the registered subsystem is not processed, the registered subsystem is possibly abnormal, and in order to assist the registered subsystem to continue processing the account number in the registered subsystem which is not processed, after the prompt information is displayed, the method further comprises the following steps: and receiving a processing instruction, wherein the processing instruction is used for processing the account numbers in the registered subsystem which is not processed. The processing instruction may be a processing instruction received as input by the user, or may be a processing instruction set in advance. These processing instructions are all for continuing processing of account numbers in the registered subsystem that did not complete the processing.

Step 160, processing the account number of the user to be processed in the registered host system, wherein the registered host system registers the account number for the user to be processed.

For the primary system, the step of processing the account number in the registered primary system is required to be performed after the account number of the user to be processed in the registered subsystem is processed, so as to avoid the problem that the account number in the registered subsystem which is not processed is forced to be processed because the account number in the registered primary system is directly processed, so that after all the account numbers of the user to be processed in the registered subsystem are modified, the following first possible implementation manner may be adopted in step 160, the account number in the registered primary system may be modified again, or after all the account numbers of the user to be processed in the registered subsystem are logged out, the following second possible implementation manner may be adopted in step 160, and the account number in the registered primary system may be logged out again.

In a first possible implementation manner, in this step 160, specifically includes: and modifying the account number of the user to be processed in the registered host system. After the account number of the user to be processed in the registered subsystem is modified, the account number in the registered main system can be modified, and finally the account number in the registered subsystem of the user to be processed and the account number in the registered main system can be modified.

A second possible implementation manner, this step 160 specifically includes: and logging off the account number of the user to be processed in the registered main system. After the account number of the user to be processed in the registered subsystem is cancelled, the account number in the registered main system can be cancelled, and finally the account number in the registered subsystem of the user to be processed and the account number in the registered main system can be cancelled.

In the embodiment of the invention, the main system conveniently identifies the incomplete processing condition of the account number in the registered subsystem by utilizing the processing identifier, and further, the prompt information is displayed by utilizing the incomplete processing identifier, so that the follow-up user can conveniently carry out continuous processing, and the user can timely grasp the processing progress of the account number of the user to be processed in the registered subsystem.

Referring to fig. 4, fig. 4 is a flowchart illustrating a specific application example of the account processing method according to an embodiment of the present invention. The following describes a specific application example of the account processing method provided in the embodiment of the present invention.

First, the following description is given: a user may be referred to herein as an incumbent person, which is referred to as an incumbent person when the incumbent person needs to leave. In the embodiment of the invention, the user to be processed is the person to be departed, and the time point such as the time point of the last departure working day of the person to be departed is started. The off-duty time point is 18 points of 5 months and 5 days in 2018. The registered subsystem of the personnel waiting for the job to leave comprises: an attendance checking system, a financial system, an external network instant messaging software system and an internal local area network instant messaging software system. The established account processing task is used for carrying out off-office work on the account of the person to be off-office work in the registered subsystem aiming at the person to be off-office work.

The user account list is pre-stored, and the subsystem of the incumbent person can be the registered subsystem of the incumbent person. The user account list includes: an account number of an incumbent person, and an account number of an incumbent person in the registered subsystem.

Then, the specific application example flow is described as follows:

Step 210, determining the working time point of the last off-job workday of the to-be-off staff as the starting time point of the created account processing task.

Step 220, it is determined whether the starting time point of the created account processing task is reached.

Step 230, when it is determined that the starting time point arrives, a user account list is obtained, where the user account list includes: an account number of each incumbent person in each registered subsystem.

Step 240, searching the account number of the person to be departed in the registered subsystem in the user account list by using the account number of the person to be departed.

Step 250, an account processing request is sent to the registered subsystem, wherein the account processing request carries an account of the person to be logged off in the registered subsystem, and the account processing request is used for requesting the registered subsystem to log off the account of the person to be logged off in the registered subsystem.

In the specific application example, when the starting time point of the created account processing task is reached, the account processing task is executed so as to perform log-off aiming at the to-be-logged-off staff, and compared with the prior art, the log-off of the to-be-logged-off staff in the registered subsystem is performed, and management staff is not required to manually call a system of an enterprise to perform log-off, so that the processing efficiency is higher.

The following describes the device for processing account numbers provided by the embodiment of the invention.

Referring to fig. 5, fig. 5 is a schematic structural diagram of an apparatus for account processing according to an embodiment of the present invention. The embodiment of the invention provides a device for processing an account, which is applied to a main system, wherein the main system is provided with one subsystem and/or a plurality of subsystems, and the device comprises:

an obtaining module 31, configured to obtain an execution instruction of the created account processing task;

and the execution module 32 is configured to execute the account processing task based on the execution instruction, where the account processing task is configured to process an account of a user to be processed in a registered subsystem, and the registered subsystem is a subsystem in which the account is registered for the user to be processed.

In the embodiment of the invention, the account processing task is used for processing the account of the user to be processed in the registered subsystem aiming at the user to be processed, and executing the account processing task when the starting time point of the established account processing task is monitored. Therefore, the starting time point of the established account processing task can be automatically monitored to arrive, the account processing task is executed so as to process the account of the user to be processed in the registered subsystem, and compared with the prior art, the processing efficiency is higher without the need of an information part to manually call the enterprise system.

In one possible implementation, the obtaining module 31 is specifically configured to:

In one possible implementation manner, the acquiring module is specifically configured to:

the execution module 32 is specifically configured to:

In one possible implementation, the execution module 32 is specifically configured to:

In one possible implementation manner, the account processing task includes: the first account processing task and the second account processing task; the starting time point includes: a starting time point of the first account processing task and a starting time point of the second account processing task after the starting time point of the first account processing task;

the execution module 32 is specifically configured to:

In one possible implementation manner, the number of registered subsystems of the user to be processed is a plurality, and the apparatus further includes:

The following continues to describe the electronic device provided by the embodiment of the present invention.

Referring to fig. 6, fig. 6 is a schematic structural diagram of an electronic device according to an embodiment of the present invention. The embodiment of the invention also provides an electronic device comprising a main system with one or more subsystems, including a processor 41, a communication interface 42, a memory 43 and a communication bus 44, wherein the processor 41, the communication interface 42 and the memory 43 complete the communication with each other through the communication bus 44,

a memory 43 for storing a computer program;

the processor 41 is configured to execute the program stored in the memory 43, and implement the following steps:

Acquiring an execution instruction of the established account processing task;

based on the execution instruction, executing an account processing task, wherein the account processing task is used for processing an account of a user to be processed in a registered subsystem, and the registered subsystem registers the account for the user to be processed.

The communication bus mentioned above for the electronic devices may be a peripheral component interconnect standard (Peripheral Component Interconnect, PCI) bus or an extended industry standard architecture (Extended Industry Standard Architecture, EISA) bus, etc. The communication bus may be classified as an address bus, a data bus, a control bus, or the like. For ease of illustration, the figures are shown with only one bold line, but not with only one bus or one type of bus.

The communication interface is used for communication between the electronic device and other devices.

The Memory may include random access Memory (Random Access Memory, RAM) or may include Non-Volatile Memory (NVM), such as one or more disk memories. Optionally, the memory may be one or more memory devices located remotely from the aforementioned processor.

The processor may be a general-purpose processor, including a central processing unit (Central Processing Unit, CPU), a network processor (Network Processor, NP), etc.; but also digital signal processors (Digital Signal Processing, DSP), application specific integrated circuits (Application Specific Integrated Circuit, ASIC), field programmable gate arrays (Field-Programmable Gate Array, FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components.

The method provided by the embodiment of the invention can be applied to electronic equipment. Further, the electronic device may be: desktop computers, portable computers, intelligent mobile terminals, etc. Any electronic device capable of implementing the present invention is not limited herein, and falls within the scope of the present invention.

In yet another embodiment of the present invention, a computer readable storage medium is provided, in which instructions are stored which, when run on a computer, cause the computer to perform the method steps of account number processing described in any of the above embodiments.

In a further embodiment of the present invention, there is also provided a computer program product containing instructions which, when run on a computer, cause the computer to perform the method steps of account processing as described in any of the above embodiments.

The embodiment of the invention provides a computer program which, when run on a computer, causes the computer to execute the method steps of any account processing.

For the apparatus/electronic device/storage medium embodiment/computer program product/computer program embodiment containing instructions, the description is relatively simple, as relevant see also part of the description of the method embodiment, since it is substantially similar to the method embodiment.

In the above embodiments, it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When loaded and executed on a computer, produces a flow or function in accordance with embodiments of the present invention, in whole or in part. The computer may be a general purpose computer, a special purpose computer, a computer network, or other programmable apparatus. The computer instructions may be stored in or transmitted from one computer-readable storage medium to another, for example, by wired (e.g., coaxial cable, optical fiber, digital Subscriber Line (DSL)), or wireless (e.g., infrared, wireless, microwave, etc.). The computer readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server, data center, etc. that contains an integration of one or more available media. The usable medium may be a magnetic medium (e.g., floppy Disk, hard Disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., solid State Disk (SSD)), etc.

It is noted that relational terms such as first and second, and the like are used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Moreover, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.

In this specification, each embodiment is described in a related manner, and identical and similar parts of each embodiment are all referred to each other, and each embodiment mainly describes differences from other embodiments. In particular, for a device/electronic apparatus/storage medium embodiment/computer program product/computer program containing instructions, the description is relatively simple, as it is substantially similar to the method embodiment, as relevant see also part of the description of the method embodiment.

The foregoing description is only of the preferred embodiments of the present invention and is not intended to limit the scope of the present invention. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present invention are included in the protection scope of the present invention.

Claims

1. A method of account processing applied to a host system having one and/or more subsystems, the method comprising:

acquiring an execution instruction of the established account processing task;

based on the execution instruction, a user account list pre-stored in a main system is obtained, wherein the user account list comprises: the account number identification of each user and the account number of the user in each subsystem corresponding to the account number identification, wherein the account number identification of each user represents the account number registered by the user in the main system, and the account number registered by each user in the main system and the account number of the user in each subsystem have a pre-established association relationship;

according to the account identification of the user to be processed, searching an account of the user to be processed in a registered subsystem in the user account list;

an account processing request is sent to the registered subsystem, wherein the account processing request carries an account of the user to be processed in the registered subsystem, and the account processing request is used for requesting the registered subsystem to log off the account of the user to be processed in the registered subsystem in batches;

The account processing task is created by adopting the following steps:

processing accounts in a subsystem of which the users to be processed have registered a second preset importance level, and creating a second account processing task, wherein the first preset importance level is higher than the second preset importance level, and the starting time point of the first account processing task is earlier than the starting time point of the second account processing task;

the special registered subsystem and the general registered subsystem of the user to be processed are respectively set to a first preset importance level and a second preset importance level; or, setting the registered subsystems of the user to be processed, which have completed work and have not completed work, as a first preset importance level and a second preset importance level respectively.

2. The method of claim 1, wherein the obtaining the execution instruction of the created account processing task includes:

3. The method of claim 1, wherein the obtaining the execution instruction of the created account processing task includes:

4. The method of claim 1, wherein the account processing task comprises: the first account processing task and the second account processing task;

5. The method of claim 4, wherein the performing the first account processing task when it is determined that the start time point of the first account processing task is reached comprises:

6. The method of claim 1, wherein the performing the account processing task comprises:

7. The method of claim 1, wherein the number of registered subsystems of the user to be processed is a plurality, and wherein after the performing the account processing task, the method further comprises:

8. An account processing apparatus for use with a host system having one and/or more subsystems, the apparatus comprising:

the execution module is used for acquiring a user account list pre-stored in the main system based on the execution instruction, wherein the user account list comprises the following components: the account number identification of each user and the account number of the user in each subsystem corresponding to the account number identification, wherein the account number identification of each user represents the account number registered by the user in the main system, and the account number registered by each user in the main system and the account number of the user in each subsystem have a pre-established association relationship; according to the account identification of the user to be processed, searching an account of the user to be processed in a registered subsystem in the user account list; an account processing request is sent to the registered subsystem, wherein the account processing request carries an account of the user to be processed in the registered subsystem, and the account processing request is used for requesting the registered subsystem to log off the account of the user to be processed in the registered subsystem in batches;

the apparatus further comprises: the creation module is used for creating the account processing task by adopting the following steps:

9. The apparatus of claim 8, wherein the acquisition module is specifically configured to:

10. The apparatus of claim 8, wherein the acquisition module is specifically configured to:

the execution module is specifically configured to:

11. The apparatus of claim 8, wherein the account processing task comprises: the first account processing task and the second account processing task;

the execution module is specifically configured to:

12. The apparatus of claim 11, wherein the execution module is specifically configured to:

the execution module is specifically configured to:

13. The apparatus of claim 8, wherein the execution module is specifically configured to:

14. The apparatus of claim 8, wherein the number of registered subsystems for the user to be processed is a plurality, the apparatus further comprising:

15. The electronic equipment is characterized by comprising a processor, a communication interface, a memory and a communication bus, wherein the processor, the communication interface and the memory are communicated with each other through the communication bus;

a memory for storing a computer program;

a processor for carrying out the method steps of any one of claims 1-7 when executing a program stored on a memory.

16. A computer-readable storage medium, characterized in that the computer-readable storage medium has stored therein a computer program which, when executed by a processor, implements the method steps of any of claims 1-7.