Task terminal changing method and device, equipment, medium and product

Abstract

The invention provides a task terminal changing method and device, equipment, a medium and a product. The method belongs to the technical field of business processing, and comprises the following steps: obtaining a terminal change instruction which carries the serial number of a target task; determining a task type of the target task in a task relation library according to the number of the target task; according to the task type of the target task, the task association relationship and the corresponding relationship between the task and the terminal, searching a to-be-changed terminal in a task relationship library; and changing the to-be-changed terminal according to the terminal change instruction. The technical problem of poor system consistency caused by incapability of synchronously changing the corresponding terminal of the associated task in the process of changing the task terminal in the related technology is solved.

Description

Technical Field

[0001] The present application belongs to the field of business processing technology, and in particular, relates to a method, device, equipment, medium and product for changing a task terminal. Background Art

[0002] When the group needs to query the terminal accounts managed by member units, it can initiate a centralized authorization application to the terminal through online channels. The centralized authorization application needs to be reviewed by multiple terminals at multiple levels, which results in multi-level and multi-terminal tasks. When it is necessary to change the terminal to which a task belongs, due to the relationship between tasks, the corresponding terminals of the tasks associated with the task need to be changed at the same time to achieve system synchronization, thereby improving system consistency.

[0003] In the related art, the existing multi-level and multi-terminal task terminal change only changes the terminal of the task, and does not change the corresponding terminal of the associated task.

[0004] Therefore, there is an urgent need for a method for changing a task terminal, which can change the corresponding terminals of the associated tasks during the process of changing the task terminals of multiple levels and multiple terminals, so as to achieve system synchronization. Summary of the invention

[0005] The embodiments of the present application provide a method, apparatus, device, storage medium and computer program product for changing a task terminal to solve the technical problem in the related art that, during the process of changing a task terminal, the corresponding terminals of the associated tasks cannot be changed synchronously, resulting in poor system consistency.

[0006] In a first aspect, an embodiment of the present application provides a method for changing a task terminal, the method comprising:

[0007] Obtain a terminal change instruction, which carries the number of the target task and is used to indicate the terminal to which the target task belongs;

[0008] According to the number of the target task, the task type of the target task is determined in the task relationship library; the task relationship library is used to record the task number, task type, task association relationship and the corresponding relationship between the task and the terminal of each task; wherein the task type is set according to the authority level of the terminal to which the task belongs;

[0009] According to the task type, task association relationship and correspondence relationship between the target task and the terminal, the terminal to be changed is searched in the task relationship library, the terminal to be changed includes the terminal to which the target task belongs, the first terminal corresponding to the target task in the correspondence relationship between the task and the terminal, and the second terminal corresponding to the task associated with the target task in the correspondence relationship between the task and the terminal, wherein the terminal to which the target task belongs, the first terminal and the second terminal have the same authority level;

[0010] According to the terminal change instruction, change the terminal to be changed.

[0011] In a second aspect, an embodiment of the present application provides a device for changing a task terminal, the device comprising:

[0012] An acquisition module is used to acquire a terminal change instruction, which carries the number of the target task and is used to indicate the terminal to which the target task belongs;

[0013] A determination module is used to determine the task type of the target task in the task relationship library according to the number of the target task; the task relationship library is used to record the task number, task type, task association relationship and the corresponding relationship between the task and the terminal of each task; wherein the task type is set according to the authority level of the terminal to which the task belongs;

[0014] A search module, used to search for a terminal to be changed in a task relationship library according to a task type of a target task, a task association relationship, and a correspondence relationship between a task and a terminal, wherein the terminal to be changed includes a terminal to which the target task belongs, a first terminal corresponding to the target task in the correspondence relationship between tasks and terminals, and a second terminal corresponding to a task associated with the target task in the correspondence relationship between tasks and terminals, wherein the terminal to which the target task belongs, the first terminal, and the second terminal have the same authority level;

[0015] The change module is used to change the terminal to be changed according to the terminal change instruction.

[0016] In a third aspect, an embodiment of the present application provides an electronic device, the device comprising:

[0017] A processor and a memory storing programs or instructions;

[0018] The above method is implemented when the processor executes the program or instruction.

[0019] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium, on which a program or instruction is stored, and the program or instruction implements the above method when executed by a processor.

[0020] In a fifth aspect, an embodiment of the present application provides a computer program product. When the instructions in the computer program product are executed by a processor of an electronic device, the electronic device executes the above method.

[0021] In the present application, the task type of the target task is first determined through the task relationship library; then, based on the task type of the target task, as well as the task association relationship and the correspondence between the task and the terminal recorded in the task relationship library, the terminal to which the target task belongs is searched in the task relationship library, and the first terminal corresponding to the target task in the correspondence between the task and the terminal, and the second terminal corresponding to the task associated with the target task in the correspondence between the task and the terminal are the terminals to be changed; finally, according to the terminal change instruction, the terminal to be changed is changed; thereby, in the process of changing the task terminal of multi-level and multi-terminal tasks, the corresponding terminals of the associated tasks are changed at the same time, which solves the technical problem in the related technology that the corresponding terminals of the associated tasks cannot be changed synchronously, resulting in poor system consistency, and improves the consistency of the system. BRIEF DESCRIPTION OF THE DRAWINGS

[0022] In order to more clearly illustrate the technical solution of the embodiments of the present application, the following is a brief introduction to the drawings required for use in the embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work.

[0023] Figure 1 is a flowchart of a method for changing a task terminal according to an embodiment of the present invention;

[0024] Figure 2 is a schematic diagram of a structure of permission levels according to an embodiment of the present invention;

[0025] Figure 3 is a structural block diagram of a task terminal changing device according to an embodiment of the present invention;

[0026] Figure 4 is a schematic structural diagram of an electronic device according to an embodiment of the present invention. DETAILED DESCRIPTION

[0027] The features and exemplary embodiments of various aspects of the present application will be described in detail below. In order to make the purpose, technical solutions and advantages of the present application clearer, the present application will be further described in detail below in conjunction with the accompanying drawings and specific embodiments. It should be understood that the specific embodiments described herein are only intended to explain the present application, rather than to limit the present application. For those skilled in the art, the present application can be implemented without the need for some of these specific details. The following description of the embodiments is only to provide a better understanding of the present application by illustrating the examples of the present application.

[0028] It should be noted that, in this article, relational terms such as first and second, etc. are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the statement "include..." do not exclude the existence of other identical elements in the process, method, article or device including the elements.

[0029] In addition, it should be noted that the acquisition, storage, use, and processing of data in the embodiments of the present application comply with the relevant provisions of national laws and regulations.

[0030] It should be noted that in the embodiments of the present application, certain software, components, models and other existing solutions in the industry may be mentioned, and they should be regarded as exemplary. Their purpose is only to illustrate the feasibility of implementing the technical solution of the present application, but it does not mean that the applicant has or will necessarily use the solution.

[0031] In order to solve the technical problem that the prior art cannot timely and effectively identify and discover the potential risks of terminals and practitioners' behaviors and provide early warning information, an embodiment of the present application provides a method for changing a task terminal, which can be applied in a task terminal change system. Figure 1 FIG. 1 is a flow chart of a method for changing a task terminal according to an embodiment of the present invention. Figure 1 As shown, the method for changing the task terminal may include the following steps:

[0032] S110, obtaining a terminal change instruction, where the terminal change instruction carries the number of the target task and is used to indicate the terminal to which the target task belongs.

[0033] In this embodiment, the terminal can be a financial terminal, such as a bank. The terminal can include multi-level terminal relationships. Terminals at different levels have different authority levels. The task can be that the group needs to query the terminal accounts managed by member units and initiate a centralized authorization application to the terminal through an online channel. The centralized authorization application is reviewed by multiple terminals at multiple levels, resulting in the resulting task.

[0034] For example, Figure 2 is a schematic diagram of a terminal authority level structure according to an embodiment of the present invention, such as Figure 2As shown, the group may include member unit A, member unit B, and member unit C; among them, member unit A manages terminal accounts 001-003, member unit B manages terminal accounts 004-006, and member unit C manages terminal accounts 007-009. The centralized authorization application needs to go through three levels of terminal review, including account opening terminal, co-organizer terminal, and host terminal, which generates tasks.

[0035] In this embodiment, when the terminal change instruction is obtained, the number of the target task is parsed from the terminal change instruction. For example, if the terminal change instruction indicates that the task numbered Tsk_10 needs to be changed, the target task is identified as Tsk_10.

[0036] S120, according to the number of the target task, determine the task type of the target task in the task relationship library; the task relationship library is used to record the task number, task type, task association relationship and the corresponding relationship between the task and the terminal of each task; wherein the task type is set according to the authority level of the terminal to which the task belongs.

[0037] In this embodiment, different types of tasks will have different processing logic when the terminal is changed. Therefore, it is necessary to first clarify the task type of the target task. The task type can be set according to the authority level of the terminal to which the task belongs. It can be mainly divided into three categories: account opening tasks, co-organized tasks, and hosted tasks;

[0038] Among them, the account opening task can be established according to the number of accounts in a 1:1 ratio, that is, one account corresponds to one account opening task. The account opening task is directly related to the account opening terminal.

[0039] Among them, the co-organized tasks can be established according to the member units 1:1, that is, one member unit corresponds to one co-organized task. The co-organized tasks are related to the management and maintenance terminals (co-organized terminals) of the member units.

[0040] The host task can be established according to the authorized unit group. Because the same batch of authorizations are all authorized to the same group, only one host task can be established. The host task is related to the group management terminal (host terminal).

[0041] In this embodiment, the task relationship library records the task type of each task. According to the number of the target task, the task type of the target task can be determined in the task relationship library.

[0042] For example, part of the task relationship library is shown in the following table: When the target task is numbered Tsk_01, the task type of the target task is an account opening task.

[0043]

[0044] In this way, by first clarifying the task type of the target task, different processing logics can be used to find the terminal to be changed for the target task for different types of target tasks, which significantly improves the flexibility and efficiency of task processing and ensures that all types of tasks can be accurately executed according to the established logic when the terminal changes, reducing human errors.

[0045] S130, according to the task type of the target task, the task association relationship and the correspondence between the task and the terminal, search for the terminal to be changed in the task relationship library, the terminal to be changed includes the terminal to which the target task belongs, the first terminal corresponding to the target task in the correspondence between the task and the terminal, and the second terminal corresponding to the task associated with the target task in the correspondence between the task and the terminal, wherein the authority levels of the terminal to which the target task belongs, the first terminal and the second terminal are the same.

[0046] In this embodiment, the task association relationship of the task relationship library records the association relationship between each task, and the association relationship between each task can be set according to the task type of the task. For example, if it is a main task, it may be associated with several co-sponsoring tasks; if the target task is a co-sponsoring task, it may be associated with several account opening tasks.

[0047] In this embodiment, the correspondence between tasks and terminals in the task relationship library records the terminal to which the task belongs (i.e., the terminal currently executing the task), as well as other terminals directly related to the task (including account opening terminals, co-organized terminals, and host terminals, etc.). For example, a partial task relationship library is shown in the following table: When the target task is numbered Tsk_01, the task-to-be-assigned terminal of the target task is terminal A, the account opening terminal of the target task is terminal A, the co-organized terminal is terminal A, and the host terminal is terminal A.

[0048]

[0049] In this embodiment, based on the task type, task association relationship and correspondence between the task and the terminal of the above-mentioned target task, the terminal to which the target task belongs and the target task corresponding terminal with the same authority level as the target task corresponding terminal are searched in the task relationship library, and the task corresponding terminal associated with the target task is the terminal to be changed.

[0050] In this way, when performing multi-level and multi-terminal task terminal changes, it is possible to accurately and efficiently process associated tasks and terminals while maintaining consistency in authority levels.

[0051] S140: According to the terminal change instruction, the terminal to be changed is changed.

[0052] In an embodiment of the present application, the task type of the target task is first determined through the task relationship library; then, based on the task type of the target task, as well as the task association relationship and the correspondence between the task and the terminal recorded in the task relationship library, the terminal to which the target task belongs is searched in the task relationship library, and the first terminal corresponding to the target task in the correspondence between the task and the terminal, and the second terminal corresponding to the task associated with the target task in the correspondence between the task and the terminal are the terminals to be changed; finally, according to the terminal change instruction, the terminal to be changed is changed; thereby, in the process of changing the task terminal of a multi-level and multi-terminal task, the corresponding terminals of the associated tasks are changed at the same time, which solves the technical problem in the related art that the corresponding terminals of the associated tasks cannot be changed synchronously, resulting in poor system consistency, and improves the consistency of the system.

[0053] In some embodiments, when the task type of the target task indicates that the target task has no associated subtask, searching the task relationship library for the terminal to be changed according to the task type of the target task, the task association relationship, and the corresponding relationship between the task and the terminal includes:

[0054] In the task relationship library, the terminal to which the target task belongs is determined, and in the correspondence between the task and the terminal, the terminal corresponding to the target task and having the same authority level as the terminal to which the target task belongs is the terminal to be changed.

[0055] In this embodiment, when the task type of the target task indicates that the target task has no associated subtask, that is, when the task type of the target task is an account opening task, in addition to changing the terminal to which the target task belongs, the target task account opening terminal also needs to be changed.

[0056] For example, when the target task is numbered Tsk_01, the task terminal of the target task is "Terminal A", and the terminal with the same authority level as the terminal to which the target task belongs is the account opening terminal "Terminal A" of the target task. The terminal to be changed is the task terminal "Terminal A" and the account opening terminal "Terminal A" with the task number Tsk_01 shown in Table 1 below.

[0057] Table 1

[0058]

[0059] In some embodiments, when the task type of the target task indicates that the target task is associated with a subtask, and the subtask associated with the target task has no associated subtask, searching for the terminal to be changed in the task relationship library according to the task type of the target task, the task association relationship, and the correspondence between the task and the terminal includes:

[0060] In the task relationship library, determine the terminal to which the target task belongs, and in the correspondence between the task and the terminal, the third terminal corresponding to the first task and having the same authority level as the terminal to which the target task belongs; the first task is a subtask associated with the target task;

[0061] The terminal to which the target task belongs and the corresponding relationship between the task and the terminal are determined. The terminal corresponding to the target task and having the same authority level as the terminal to which the target task belongs, and the third terminal are the terminals to be changed.

[0062] In this embodiment, when the task type of the target task indicates that the target task is associated with a subtask, and the subtask associated with the target task has no associated subtask, that is, when the task type of the target task is a co-organized task, in addition to changing the terminal to which the target task belongs, the co-organized terminal also needs to be changed. The co-organized terminal can specifically include the co-organized terminal of the target task, and the co-organized terminal of the subtask associated with the target task.

[0063] For example, when the target task is numbered Tsk_10, the subtasks (first task) associated with Tsk_10 include Tsk_01, Tsk_02, and Tsk_03;

[0064] In the subtask associated with the target task, the third terminal with the same authority level as the terminal to which the target task belongs is the co-sponsor terminal, so the third terminal is the co-sponsor terminal "Terminal A" of Tsk_01-Tsk_03.

[0065] The terminals to be changed are the terminals shown in Table 2 below: the task-owning terminal "Terminal A" and the co-organizing terminal "Terminal A" of the target task number Tsk_10, and the co-organizing terminal "Terminal A" of the task numbers Tsk_01-Tsk_03.

[0066] Table 2

[0067]

[0068] In some embodiments, when the task type of the target task indicates that the target task is associated with a subtask, and the subtask associated with the target task is also associated with a subtask, searching the task relationship library for the terminal to be changed according to the task type of the target task, the task association relationship, and the correspondence between the task and the terminal includes:

[0069] In the task relationship library, determine the terminal to which the target task belongs, and in the correspondence between the task and the terminal, the third terminal corresponding to the first task has the same authority level as the terminal to which the target task belongs, and the fourth terminal corresponding to the second task has the same authority level as the terminal to which the target task belongs; the first task is a subtask associated with the target task, and the second task is a subtask associated with the first task;

[0070] In determining the terminal to which the target task belongs and the correspondence between the task and the terminal, the terminal corresponding to the target task and having the same authority level as the terminal to which the target task belongs, the third terminal and the fourth terminal are the terminals to be changed.

[0071] In this embodiment, when the task type of the target task indicates that the target task is associated with a subtask, and the subtask associated with the target task is also associated with a subtask, that is, when the task type of the target task is a host task, in addition to changing the terminal to which the target task belongs, the host terminal also needs to be changed. The host terminal can specifically include the host terminal of the target task, the host terminal of the subtask associated with the target task (that is, the associated task whose task type is the co-organized task), and the host terminal of the subtask associated with the subtask (that is, the associated task whose task type is the account opening task).

[0072] For example, when the target task is numbered Tsk_13, the subtasks associated with Tsk_13 include Tsk_10, Tsk_11, and Tsk_12, the subtasks associated with Tsk_10 include Tsk_01, Tsk_02, and Tsk_03, the subtasks associated with Tsk_11 include Tsk_04, Tsk_05, and Tsk_06, and the subtasks associated with Tsk_12 include Tsk_07, Tsk_08, and Tsk_09.

[0073] In the subtask associated with the target task, the third terminal with the same authority level as the terminal to which the target task belongs is the host terminal, so the third terminal is the host terminal "Terminal A" of Tsk_10-Tsk_12;

[0074] In the subtasks of the subtasks associated with the target task, the fourth terminal having the same authority level as the terminal to which the target task belongs is the host terminal, so the fourth terminal is the host terminal "Terminal A" of Tsk_1-Tsk_9;

[0075] The terminals to be changed are the terminals shown in Table 3 below: the task-belonging terminal "Terminal A" and the host terminal "Terminal A" of the target task number Tsk_13, and the host terminal "Terminal A" of the task numbers Tsk_01-Tsk_012.

[0076] Table 3

[0077]

[0078] In some embodiments, according to the terminal change instruction, changing the terminal to be changed includes:

[0079] Determine a first authority level of a terminal that issues a terminal change instruction and a second authority level of a terminal to which a target task belongs;

[0080] In the case where the first authority level is higher than the second authority level, the terminal to be changed is changed according to the terminal change instruction.

[0081] In this embodiment, in order to ensure that the terminal change operation complies with the hierarchical relationship between terminals, the first authority level of the terminal that issues the terminal change instruction (i.e., the instruction issuing terminal) and the second authority level of the terminal to which the target task currently belongs (i.e., the target terminal) can be determined.

[0082] In the case where the first permission level is higher than the second permission level, it is understandable that the terminal issuing the instruction may have sufficient authority to change the target terminal. Because according to the terminal tree hierarchy, the high-level terminal has the right to manage and adjust the tasks of the low-level terminal. At this time, the system will change the target terminal according to the requirements of the terminal change instruction.

[0083] When the first authority level is not higher than the second authority level, the terminal issuing the instruction does not have sufficient authority to change the target terminal. At this time, the system should refuse to execute the change instruction and return an error message or prompt to the terminal issuing the instruction, indicating that its authority is insufficient.

[0084] In this way, the security and stability of the system are improved by ensuring that terminal change operations comply with permission levels.

[0085] In some embodiments, after changing the terminal to be changed according to the terminal change instruction, the method further includes:

[0086] Receive the viewing instruction of the target task sent by the terminal before the change;

[0087] Determine the third permission level of the terminal before the change and the fourth permission level of the terminal after the change;

[0088] When the third authority level is higher than the fourth authority level, a viewing instruction of the target task is executed.

[0089] In this embodiment, when the terminal before the change (ie, the terminal to which the original target task belongs, the terminal responsible for the task before the change operation) attempts to view the status or details of the changed target task, the system will receive a viewing instruction sent by the terminal.

[0090] The system needs to identify and determine the level of the terminal before the change that issued the view instruction in the terminal tree (the third authority level), and the level of the terminal to which the target task currently belongs (i.e., the terminal after the change) in the terminal tree (the fourth authority level).

[0091] It is understandable that according to the authority control principle, the superior terminal has the right to view the task status of the subordinate terminal. Therefore, if the system determines that the third authority level of the terminal before the change is higher than the fourth authority level of the terminal after the change, that is, the terminal before the change is at the superior or the same level as the terminal after the change in the organizational structure, the terminal before the change is allowed to execute the viewing instruction, that is, it is allowed to view the status or details of the target task.

[0092] In this way, the system's permission control logic is ensured to be executed correctly after the terminal is changed, which not only ensures the security and privacy of task information, but also ensures the necessary transparency and traceability.

[0093] In some embodiments, after changing the terminal to be changed according to the terminal change instruction, the method further includes:

[0094] The task relationship library is updated according to the change result of the terminal to be changed.

[0095] In this embodiment, after the terminal to be changed is changed, in order to ensure the accuracy of the task relationship library, the task relationship library needs to be updated and the updated task relationship library needs to be synchronized in the system. While updating the task relationship library, the visibility and permissions of the task need to be reset according to the hierarchical relationship between the terminals. This ensures that only authorized terminals can access and modify relevant task information to prevent information leakage and unauthorized operations.

[0096] In this way, by updating the task relationship library, the system can maintain the accuracy and system consistency of the task relationship library.

[0097] Figure 3 A schematic diagram of the structure of a task terminal changing device provided in another embodiment of the present application is shown. For ease of explanation, only the parts related to the embodiment of the present application are shown.

[0098] Reference Figure 3 , the task terminal changing device 300 may include:

[0099] The acquisition module 301 is used to acquire a terminal change instruction, where the terminal change instruction carries the number of the target task and is used to indicate the terminal to which the target task belongs;

[0100] The determination module 302 is used to determine the task type of the target task in the task relationship library according to the number of the target task; the task relationship library is used to record the task number, task type, task association relationship and the corresponding relationship between the task and the terminal of each task; wherein the task type is set according to the authority level of the terminal to which the task belongs;

[0101] A search module 303 is used to search for a terminal to be changed in a task relationship library according to a task type of the target task, a task association relationship, and a correspondence relationship between the task and the terminal. The terminal to be changed includes a terminal to which the target task belongs, a first terminal corresponding to the target task in the correspondence relationship between the task and the terminal, and a second terminal corresponding to a task associated with the target task in the correspondence relationship between the task and the terminal, wherein the terminal to which the target task belongs, the first terminal, and the second terminal have the same authority level;

[0102] The changing module 304 is used to change the terminal to be changed according to the terminal change instruction.

[0103] In some embodiments, the search module 303 may include the following units:

[0104] The determination unit is used to determine the terminal to which the target task belongs in the task relationship library when the task type of the target task indicates that the target task has no associated subtask, and in the correspondence between the task and the terminal, the terminal corresponding to the target task and having the same authority level as the terminal to which the target task belongs is the terminal to be changed.

[0105] In some embodiments, the search module 303 may include the following units:

[0106] The determination unit is further configured to determine, in a task relationship library, the terminal to which the target task belongs, and, in the correspondence between tasks and terminals, a third terminal corresponding to the first task and having the same authority level as the terminal to which the target task belongs, when the task type of the target task indicates that the target task is associated with a subtask, and the subtask associated with the target task has no associated subtask; the first task is a subtask associated with the target task;

[0107] The determination unit is further used to determine that the terminal to which the target task belongs, the terminal corresponding to the target task and having the same authority level as the terminal to which the target task belongs in the correspondence between the task and the terminal, and the third terminal are the terminals to be changed.

[0108] In some embodiments, the search module 303 may include the following units:

[0109] The determination unit is further used to determine, in a task relationship library, the terminal to which the target task belongs, and in the correspondence between the task and the terminal, a third terminal corresponding to the first task and having the same authority level as the terminal to which the target task belongs, and a fourth terminal corresponding to the second task and having the same authority level as the terminal to which the target task belongs, when the task type of the target task indicates that the target task is associated with a subtask, and the subtask associated with the target task is also associated with a subtask; the first task is a subtask associated with the target task, and the second task is a subtask associated with the first task;

[0110] The determination unit is further used to determine the terminal to which the target task belongs, and in the correspondence between the task and the terminal, the terminal corresponding to the target task and having the same authority level as the terminal to which the target task belongs, the third terminal and the fourth terminal are the terminals to be changed.

[0111] In some embodiments, the change module 304 may include the following units:

[0112] A determination unit, used to determine a first authority level of a terminal that issues a terminal change instruction and a second authority level of a terminal to which a target task belongs;

[0113] The changing unit is used to change the terminal to be changed according to the terminal change instruction when the first authority level is higher than the second authority level.

[0114] In some embodiments, the task terminal changing device 300 may include:

[0115] A receiving module, used for receiving a viewing instruction of a target task sent by the terminal before the change after the terminal to be changed is changed according to the terminal change instruction;

[0116] The determination module 302 is further used to determine the third authority level of the terminal before the change and the fourth authority level of the terminal after the change;

[0117] The execution module is used to execute the viewing instruction of the target task when the third authority level is higher than the fourth authority level.

[0118] In some embodiments, the task terminal changing device 300 may include:

[0119] The updating module is used to update the task relationship library according to the change result of the terminal to be changed after the terminal to be changed is changed according to the terminal change instruction.

[0120] It should be noted that the information interaction, execution process, etc. between the above-mentioned devices / units are based on the same concept as the method embodiment of the present application, and are devices corresponding to the method for changing the above-mentioned task terminal. All implementation methods in the above-mentioned method embodiment are applicable to the embodiment of the device. Its specific functions and the technical effects brought about can be found in the method embodiment part, which will not be repeated here.

[0121] The technicians in the relevant field can clearly understand that for the convenience and simplicity of description, only the division of the above-mentioned functional units and modules is used as an example for illustration. In practical applications, the above-mentioned function allocation can be completed by different functional units and modules as needed, that is, the internal structure of the device can be divided into different functional units or modules to complete all or part of the functions described above. The functional units and modules in the embodiment can be integrated in a processing unit, or each unit can exist physically separately, or two or more units can be integrated in one unit. The above-mentioned integrated unit can be implemented in the form of hardware or in the form of software functional units. In addition, the specific names of the functional units and modules are only for the convenience of distinguishing each other, and are not used to limit the scope of protection of this application. The specific working process of the units and modules in the above-mentioned system can refer to the corresponding process in the aforementioned method embodiment, which will not be repeated here.

[0122] Figure 4 is a schematic diagram of the structure of an electronic device according to an embodiment of the present invention. Figure 4 As shown:

[0123] The device may include a processor 401 and a memory 402 storing programs or instructions.

[0124] When the processor 401 executes the program, the steps in any of the above method embodiments are implemented.

[0125] Exemplarily, the program may be divided into one or more modules / units, one or more modules / units are stored in the memory 402, and executed by the processor 401 to complete the present application. One or more modules / units may be a series of program instruction segments capable of completing a specific function, and the instruction segments are used to describe the execution process of the program in the device.

[0126] Specifically, the processor 401 may include a central processing unit (CPU), or an application specific integrated circuit (ASIC), or may be configured to implement one or more integrated circuits of the embodiments of the present application.

[0127] Memory 402 may include a large capacity memory for data or instructions. By way of example and not limitation, memory 402 may include a hard disk drive (HDD), a floppy disk drive, a flash memory, an optical disk, a magneto-optical disk, a magnetic tape, or a universal serial bus (USB) drive or a combination of two or more of these. In appropriate cases, memory 402 may include a removable or non-removable (or fixed) medium. In appropriate cases, memory 402 may be inside or outside of an integrated gateway disaster recovery device. In a specific embodiment, memory 402 is a non-volatile solid-state memory.

[0128] The memory may include read-only memory (ROM), random access memory (RAM), magnetic disk storage media devices, optical storage media devices, flash memory devices, electrical, optical or other physical / tangible memory storage devices. Thus, typically, the memory includes one or more tangible (non-transitory) computer-readable storage media (e.g., memory devices) encoded with software including computer-executable instructions, and when the software is executed (e.g., by one or more processors), it is operable to perform the operations described with reference to the method according to an aspect of the present disclosure.

[0129] The processor 401 implements any one of the methods in the above embodiments by reading and executing the program or instruction stored in the memory 402 .

[0130] In one example, the electronic device may further include a communication interface 403 and a bus 404. The processor 401, the memory 402, and the communication interface 403 are connected via the bus 404 and communicate with each other.

[0131] The communication interface 403 is mainly used to implement communication between various modules, devices, units and / or equipment in the embodiments of the present application.

[0132] Bus 404 includes hardware, software or both, and the parts of online data flow billing equipment are coupled to each other. For example, but not limitation, bus may include accelerated graphics port (AGP) or other graphics bus, enhanced industrial standard architecture (EISA) bus, front side bus (FSB), hypertransport (HT) interconnection, industrial standard architecture (ISA) bus, infinite bandwidth interconnection, low pin count (LPC) bus, memory bus, micro channel architecture (MCA) bus, peripheral component interconnection (PCI) bus, PCI-Express (PCI-X) bus, serial advanced technology attachment (SATA) bus, video electronics standard association local (VLB) bus or other suitable bus or two or more of these combinations. In appropriate cases, bus 404 may include one or more buses. Although the present application embodiment describes and shows a specific bus, the present application considers any suitable bus or interconnection.

[0133] In addition, in combination with the method in the above embodiment, the embodiment of the present application may provide a computer-readable storage medium for implementation. The computer-readable storage medium stores a program or instruction; when the program or instruction is executed by a processor, any one of the methods in the above embodiment is implemented. The computer-readable storage medium can be read by a machine such as a computer.

[0134] An embodiment of the present application further provides a chip, which includes a processor and a communication interface, wherein the communication interface and the processor are coupled, and the processor is used to run programs or instructions to implement the various processes of the above-mentioned method embodiment, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0135] It should be understood that the chip mentioned in the embodiments of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc.

[0136] An embodiment of the present application provides a computer program product, which is stored in a computer-readable storage medium. The program product is executed by at least one processor to implement the various processes of the above-mentioned method embodiment and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0137] It should be clear that the present application is not limited to the specific configuration and processing described above and shown in the figures. For the sake of simplicity, a detailed description of the known method is omitted here. In the above embodiments, several specific steps are described and shown as examples. However, the method process of the present application is not limited to the specific steps described and shown, and those skilled in the art can make various changes, modifications and additions, or change the order between the steps after understanding the spirit of the present application.

[0138] The functional modules shown in the above block diagram can be implemented as hardware, software, firmware or their combination. When implemented in hardware, it can be, for example, an electronic circuit, an application specific integrated circuit (ASIC), suitable firmware, a plug-in, a function card, etc. When implemented in software, the elements of the present application are programs or code segments that are used to perform the required tasks. Programs or code segments can be stored in machine-readable media, or transmitted on a transmission medium or a communication link by a data signal carried in a carrier wave. "Machine-readable media" can include any medium that can store or transmit information. Examples of machine-readable media include electronic circuits, semiconductor memory devices, ROM, flash memory, erasable ROM (EROM), floppy disks, CD-ROMs, optical disks, hard disks, optical fiber media, radio frequency (RF) links, etc. Code segments can be downloaded via computer grids such as the Internet, intranets, etc.

[0139] It should also be noted that the exemplary embodiments mentioned in this application describe some methods or systems based on a series of steps or devices. However, this application is not limited to the order of the above steps, that is, the steps can be performed in the order mentioned in the embodiment, or in a different order from the embodiment, or several steps can be performed simultaneously.

[0140] Aspects of the present disclosure are described above with reference to the flowchart and / or block diagram of the method, device (system) and program product according to the embodiment of the present disclosure. It should be understood that each box in the flowchart and / or block diagram and the combination of each box in the flowchart and / or block diagram can be implemented by a computer program or instruction. These programs or instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device to produce a machine so that these instructions executed by the processor of the computer or other programmable data processing device enable the implementation of the function / action specified in one or more boxes of the flowchart and / or block diagram. Such a processor can be, but is not limited to, a general-purpose processor, a special-purpose processor, a special application processor, or a field programmable logic circuit. It can also be understood that each box in the block diagram and / or flowchart and the combination of boxes in the block diagram and / or flowchart can also be implemented by dedicated hardware that performs a specified function or action, or can be implemented by a combination of dedicated hardware and computer instructions.

[0141] The above are only specific implementation methods of the present application. Those skilled in the art can clearly understand that for the convenience and simplicity of description, the specific working processes of the systems, modules and units described above can refer to the corresponding processes in the aforementioned method embodiments, and will not be repeated here. It should be understood that the protection scope of the present application is not limited to this. Any technician familiar with the technical field can easily think of various equivalent modifications or replacements within the technical scope disclosed in this application, and these modifications or replacements should be included in the protection scope of this application.

Claims

1. A method for changing a task terminal, characterized in that: The method comprises: Obtain a terminal change instruction, where the terminal change instruction carries the number of the target task and is used to indicate the terminal to which the target task belongs; According to the number of the target task, the task type of the target task is determined in a task relationship library; the task relationship library is used to record the task number, task type, task association relationship and the corresponding relationship between the task and the terminal of each task; wherein the task type is set according to the authority level of the terminal to which the task belongs; According to the task type, task association relationship and correspondence relationship between the target task and the terminal, searching the terminal to be changed in the task relationship library, the terminal to be changed includes the terminal to which the target task belongs, the first terminal corresponding to the target task in the correspondence relationship between the task and the terminal, and the second terminal corresponding to the task associated with the target task in the correspondence relationship between the task and the terminal, wherein the terminal to which the target task belongs, the first terminal and the second terminal have the same authority level; According to the terminal change instruction, the terminal to be changed is changed.

2. The method according to claim 1, characterized in that In a case where the task type of the target task indicates that the target task has no associated subtask, searching the task relationship library for the terminal to be changed according to the task type of the target task, the task association relationship, and the correspondence between the task and the terminal, includes: In the task relationship library, the terminal to which the target task belongs is determined, and in the correspondence between the task and the terminal, the terminal corresponding to the target task and having the same authority level as the terminal to which the target task belongs is the terminal to be changed.

3. The method according to claim 1, characterized in that When the task type of the target task indicates that the target task is associated with a subtask, and the subtask associated with the target task has no associated subtask, searching the task relationship library for the terminal to be changed according to the task type of the target task, the task association relationship, and the correspondence between the task and the terminal, includes: In the task relationship library, determining the terminal to which the target task belongs, and in the correspondence between the tasks and the terminals, a third terminal corresponding to the first task and having the same authority level as the terminal to which the target task belongs; the first task is a subtask associated with the target task; The terminal to which the target task belongs, the corresponding relationship between the task and the terminal, the terminal corresponding to the target task and the terminal having the same authority level as the terminal to which the target task belongs, and the third terminal are determined as the terminal to be changed.

4. The method according to claim 1, characterized in that: In a case where the task type of the target task indicates that the target task is associated with a subtask, and the subtask associated with the target task is also associated with a subtask, searching the task relationship library for the terminal to be changed according to the task type of the target task, the task association relationship, and the correspondence between the task and the terminal, includes: In the task relationship library, the terminal to which the target task belongs is determined, and in the correspondence between the tasks and the terminals, a third terminal corresponding to the first task has the same authority level as the terminal to which the target task belongs, and a fourth terminal corresponding to the second task has the same authority level as the terminal to which the target task belongs; the first task is a subtask associated with the target task, and the second task is a subtask associated with the first task; The terminal to which the target task belongs and the correspondence between the task and the terminal are determined, and the terminal corresponding to the target task and having the same authority level as the terminal to which the target task belongs, the third terminal and the fourth terminal are the terminals to be changed.

5. The method according to claim 1, characterized in that The step of changing the terminal to be changed according to the terminal change instruction includes: Determine a first authority level of a terminal that issues the terminal change instruction, and a second authority level of a terminal to which the target task belongs; In a case where the first authority level is higher than the second authority level, the terminal to be changed is changed according to the terminal change instruction.

6. The method according to claim 1, characterized in that After changing the terminal to be changed according to the terminal change instruction, the method further includes: Receiving a viewing instruction of the target task sent by the terminal before the change; Determining a third authority level of the terminal before the change and a fourth authority level of the terminal after the change; In a case where the third authority level is higher than the fourth authority level, executing a viewing instruction of the target task.

7. The method according to claim 1, characterized in that After changing the terminal to be changed according to the terminal change instruction, the method further includes: The task relationship library is updated according to the change result of the terminal to be changed.

8. A task terminal changing device, characterized in that: The device comprises: An acquisition module, used for acquiring a terminal change instruction, wherein the terminal change instruction carries the number of the target task and is used for indicating the terminal to which the target task belongs to be changed; A determination module, used to determine the task type of the target task in a task relationship library according to the number of the target task; the task relationship library is used to record the task number, task type, task association relationship and the corresponding relationship between the task and the terminal of each task; wherein the task type is set according to the authority level of the terminal to which the task belongs; a search module, configured to search for a terminal to be changed in the task relationship library according to a task type of the target task, a task association relationship, and a correspondence relationship between a task and a terminal, wherein the terminal to be changed includes a terminal to which the target task belongs, a first terminal corresponding to the target task in the correspondence relationship between tasks and terminals, and a second terminal corresponding to a task associated with the target task in the correspondence relationship between tasks and terminals, wherein the terminal to which the target task belongs, the first terminal, and the second terminal have the same authority level; A changing module is used to change the terminal to be changed according to the terminal change instruction.

9. An electronic device, characterized in that: The device comprises: a processor and a memory storing computer program instructions; When the processor executes the computer program instructions, the method according to any one of claims 1 to 7 is implemented.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer program instructions, and when the computer program instructions are executed by a processor, the method according to any one of claims 1 to 7 is implemented.

11. A computer program product, characterized in that When the instructions in the computer program product are executed by a processor of an electronic device, the electronic device executes the method according to any one of claims 1 to 7.

Images