CN111880919A - Data scheduling method, system and computer equipment - Google Patents
Data scheduling method, system and computer equipment Download PDFInfo
- Publication number
- CN111880919A CN111880919A CN202010744239.5A CN202010744239A CN111880919A CN 111880919 A CN111880919 A CN 111880919A CN 202010744239 A CN202010744239 A CN 202010744239A CN 111880919 A CN111880919 A CN 111880919A
- Authority
- CN
- China
- Prior art keywords
- target
- scheduling
- executor
- token
- information
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
- 238000000034 method Methods 0.000 title claims abstract description 44
- 230000004044 response Effects 0.000 claims abstract description 36
- 238000012795 verification Methods 0.000 claims description 16
- 238000004590 computer program Methods 0.000 claims description 11
- 238000004422 calculation algorithm Methods 0.000 description 19
- 238000013515 script Methods 0.000 description 6
- 238000010586 diagram Methods 0.000 description 5
- 230000006870 function Effects 0.000 description 5
- 238000007726 management method Methods 0.000 description 5
- 230000007246 mechanism Effects 0.000 description 4
- 230000008569 process Effects 0.000 description 4
- 238000012545 processing Methods 0.000 description 4
- 235000006719 Cassia obtusifolia Nutrition 0.000 description 3
- 235000014552 Cassia tora Nutrition 0.000 description 3
- 244000201986 Cassia tora Species 0.000 description 3
- 230000005540 biological transmission Effects 0.000 description 3
- 238000004891 communication Methods 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- 230000003068 static effect Effects 0.000 description 2
- 238000013475 authorization Methods 0.000 description 1
- 238000004364 calculation method Methods 0.000 description 1
- 230000008094 contradictory effect Effects 0.000 description 1
- 238000013523 data management Methods 0.000 description 1
- 238000013500 data storage Methods 0.000 description 1
- 230000001419 dependent effect Effects 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 238000013467 fragmentation Methods 0.000 description 1
- 238000006062 fragmentation reaction Methods 0.000 description 1
- 230000010365 information processing Effects 0.000 description 1
- 238000010295 mobile communication Methods 0.000 description 1
- 238000011160 research Methods 0.000 description 1
- 230000026676 system process Effects 0.000 description 1
- 230000001960 triggered effect Effects 0.000 description 1
- 238000012800 visualization Methods 0.000 description 1
- 239000002699 waste material Substances 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/48—Program initiating; Program switching, e.g. by interrupt
- G06F9/4806—Task transfer initiation or dispatching
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/27—Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/60—Protecting data
- G06F21/602—Providing cryptographic facilities or services
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/60—Protecting data
- G06F21/604—Tools and structures for managing or administering access control systems
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/60—Protecting data
- G06F21/64—Protecting data integrity, e.g. using checksums, certificates or signatures
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Software Systems (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Computer Security & Cryptography (AREA)
- Computer Hardware Design (AREA)
- Health & Medical Sciences (AREA)
- Bioethics (AREA)
- General Health & Medical Sciences (AREA)
- Databases & Information Systems (AREA)
- Data Mining & Analysis (AREA)
- Computing Systems (AREA)
- Automation & Control Theory (AREA)
- Storage Device Security (AREA)
Abstract
The invention relates to the technical field of computers, and provides a data scheduling method, which comprises the following steps: receiving a target scheduling request sent by a client terminal; determining a target actuator according to the target scheduling request, wherein the target actuator is used for calling corresponding target response information for the client terminal according to the target calling request; acquiring a target scheduling token corresponding to the target actuator; sending the target scheduling token and the target calling request to the target executor so that the target executor obtains corresponding target response information according to the target scheduling token and the target calling request; and receiving target response information returned by the target actuator, and sending the target response information to the client terminal. The invention reduces the resource consumption of the task scheduling when the access parties are more, improves the data scheduling safety during the task scheduling, and improves the safety and the efficiency of the task scheduling.
Description
Technical Field
The embodiment of the invention relates to the technical field of computers, in particular to a data scheduling method, a data scheduling system, computer equipment and a computer readable storage medium.
Background
Task scheduling is an asynchronous processing mechanism which cannot be avoided when an IT system processes service requirements, and can be triggered in a self-defined alarm reminding mode or a mode of setting a timed task of an operating system, but cannot release dependence of personnel and single-node faults. At present, distributed task scheduling can be independently established through each application system, but the inventor of the application finds that in the research, when the number of access parties is large, fragmentation of resources occurs, the consumption of the resources is increased, and a large amount of resource waste is caused. Therefore, how to reduce the resource consumption of task scheduling when there are many access parties, and improve the data scheduling security during task scheduling, thereby further improving the security and efficiency of task scheduling, becomes one of the technical problems that needs to be solved at present.
Disclosure of Invention
In view of this, it is necessary to provide a data scheduling method, system, computer device and computer readable storage medium to solve the technical problems of the current task scheduling that the resource consumption is large when there are many access parties, and the data scheduling security is low.
In order to achieve the above object, an embodiment of the present invention provides a data scheduling method, where the method includes:
receiving a target scheduling request sent by a client terminal;
determining a target actuator according to the target scheduling request, wherein the target actuator is used for calling corresponding target response information for the client terminal according to the target calling request;
acquiring a target scheduling token corresponding to the target actuator;
sending the target scheduling token and the target calling request to the target executor so that the target executor obtains corresponding target response information according to the target scheduling token and the target calling request; and
and receiving target response information returned by the target actuator, and sending the target response information to the client terminal.
Illustratively, the sending the target scheduling token and the target invocation request to the target executor includes:
and sending the target scheduling token and the target calling request to a target executor at a preset time frequency.
Illustratively, the sending the target scheduling token and the target invocation request to the target executor includes:
performing security authentication on a target user associated with the target client terminal, and judging whether the target user has the authority of scheduling the target actuator according to a security authentication result;
if the authority of scheduling the target executor exists, the target scheduling token and the target calling request are sent to the target executor;
and if the client terminal does not have the authority of scheduling the target executor, rejecting the scheduling of the client terminal to the target executor, generating access rejection information and sending the access rejection information to the client terminal.
Illustratively, further comprising the step of configuring the target scheduling token:
receiving the target related information sent by the target actuator, wherein the target related information comprises the name of the target actuator;
encrypting the target related information according to a pre-generated target secret key and a target encryption method to obtain the target scheduling token, and uploading the target track characteristic vector to a block chain;
and sending the target secret key to the target executor, and backing up the target related information, the target secret key and the target scheduling token to a central database.
Exemplarily, the method further comprises the step of registering the target executor in advance:
receiving a registration request sent by the target actuator, wherein the registration request carries a target registration token and registration information;
verifying the target executor according to the target registration token; and
if the verification of the target actuator is successful, performing registration operation on the target actuator according to the registration information to generate registration success information, and sending the registration success information to the target actuator;
and if the verification of the target actuator fails, refusing to perform registration operation on the target actuator to generate registration failure information, and sending the registration failure information to the target actuator.
Illustratively, verifying the target executor according to the target scheduling token includes:
acquiring a target secret key corresponding to the target actuator;
decrypting the target registration token according to the target secret key and a target decryption method to obtain decryption information;
judging whether the decryption information is the same as the target related information or not;
if the decryption information is the same as the target related information, the verification is successful;
and if the decryption information is not the same as the target related information, the verification fails.
In order to achieve the above object, an embodiment of the present invention further provides a data scheduling system, including:
the receiving module is used for receiving a target scheduling request sent by a client terminal;
a determining module, configured to determine a target executor according to the target scheduling request, where the target executor is configured to invoke, according to the target invocation request, corresponding target response information for the client terminal;
the acquisition module is used for acquiring a target scheduling token corresponding to the target actuator;
the response module is used for sending the target scheduling token and the target calling request to the target executor so that the target executor obtains corresponding target response information according to the target scheduling token and the target calling request; and
and the sending module is used for receiving the target response information returned by the target actuator and sending the target response information to the client terminal.
Illustratively, the response module is further configured to: and sending the target scheduling token and the target calling request to a target executor according to a preset frequency.
To achieve the above object, an embodiment of the present invention further provides a computer device, which includes a memory, a processor, and a computer program stored in the memory and executable on the processor, and when the computer program is executed by the processor, the computer program implements the steps of the data scheduling method as described above.
To achieve the above object, an embodiment of the present invention further provides a computer-readable storage medium, in which a computer program is stored, where the computer program is executable by at least one processor, so as to cause the at least one processor to execute the steps of the data scheduling method as described above.
The data scheduling method, the data scheduling system, the computer equipment and the computer readable storage medium provided by the embodiment of the invention can reduce the resource consumption of task scheduling when a plurality of access parties exist, improve the data scheduling safety during task scheduling and improve the safety and efficiency of task scheduling by carrying out centralized management on the target executors and providing a unified scheduling mode.
Drawings
Fig. 1 is a flowchart illustrating a data scheduling method according to an embodiment of the present invention.
Fig. 2 is a schematic diagram of program modules of a second embodiment of a data scheduling system according to the present invention.
Fig. 3 is a schematic diagram of a hardware structure of a third embodiment of the computer device according to the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention more apparent, the present invention is described in further detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
It should be noted that the description relating to "first", "second", etc. in the present invention is for descriptive purposes only and is not to be construed as indicating or implying relative importance or implicitly indicating the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include at least one such feature. In addition, technical solutions between various embodiments may be combined with each other, but must be realized by a person skilled in the art, and when the technical solutions are contradictory or cannot be realized, such a combination should not be considered to exist, and is not within the protection scope of the present invention.
In the following embodiments, the computer device 2 will be exemplarily described as an execution subject.
Example one
Referring to fig. 1, a flowchart illustrating steps of a data scheduling method according to an embodiment of the present invention is shown. It is to be understood that the flow charts in the embodiments of the present method are not intended to limit the order in which the steps are performed. The following description is made by way of example with the computer device 2 as the execution subject. The details are as follows.
Step S100, receiving a target scheduling request sent by a client terminal.
Illustratively, the target scheduling request is for requesting scheduling of a target executor. And the target actuator is used for calling corresponding target response information for the client terminal according to the target calling request. And the user can send the target scheduling request to a scheduling center of a data scheduling system through a client terminal so as to complete the scheduling of the target executor by managing the data scheduling of the target executor. The embodiment can be applied to a server cluster formed by a plurality of servers. The dispatch center may be a program dispatch node in a server cluster, and the target executor may be one or more program execution nodes in the server cluster, and the program may be a program executed by each program execution node. The target executors are multiple, and the multiple target executors can be deployed in different business systems which can run on different operating systems and are mutually dependent.
And step S102, determining a target actuator according to the target scheduling request, wherein the target actuator is used for calling corresponding target response information for the client terminal according to the target calling request.
For example, after receiving the target scheduling request, the target scheduling request may be analyzed to determine target executor information corresponding to the target scheduling request, target application information corresponding to the target executor information, and target call information. According to the target executor information, a target executor corresponding to a target scheduling request can be determined.
And step S104, acquiring a target scheduling token corresponding to the target executor.
Illustratively, the target scheduling token (token) is preconfigured and stored in a central database, and the target scheduling token may be obtained from the central database according to the target executor. The target scheduling token is used for identifying identity, and is a unique identity identifier which can be used for proving the identity of a data transmitter during data transmission. In this embodiment, the target scheduling token is used to identify the target executor, and the target executor may be accessed and scheduled by using the target scheduling token, and the target executor may not be directly accessed and scheduled without the target scheduling token.
For example, the data scheduling method may further include the step of pre-configuring the target scheduling token:
step S200, receiving the target related information sent by the target actuator, where the target related information includes a name of the target actuator.
Step S204, carrying out encryption operation on the target related information according to a pre-generated target secret key and a target encryption method to obtain the target scheduling token, and uploading the target track characteristic vector to a block chain.
Illustratively, the target key is a key corresponding to a target encryption algorithm, the target encryption algorithm may be an asymmetric encryption algorithm, the target key includes a target public key and a target private key, and the target public key and the target private key may be obtained through corresponding asymmetric encryption algorithms. Among them, the so-called asymmetric encryption algorithm requires two keys: a public key (public key) and a private key (private key); the public key and the private key are a pair, and if the public key is used for encrypting data, only the corresponding private key can be used for decrypting the data. Just because two different keys are used for encryption and decryption, this algorithm is called an asymmetric encryption algorithm, which may be an RSA algorithm, for example, (SHA256withRSA, SHA384withRSA, SHA512withRSA, HmacSHA256, HmacSHA384, HmacSHA512, SHA256withECDSA, SHA384withECDSA, SHA512withECDSA) or the like, or else an Elgamal algorithm, a knapsack algorithm, a Rabin algorithm, a D-H algorithm, an ECC (elliptic curve cryptography algorithm) algorithm, or an SM2 algorithm, or the like.
Illustratively, the target scheduling token may also be generated according to JWT, which is a JSON-based open standard ((RFC7519) that is implemented for passing claims between web application environments, JWT that is a JSON-based open standard that is designed to be compact and secure and suitable for single sign-on (SSO) scenarios for distributed sites.
For example, uploading a target scheduling token vector to a blockchain may ensure its security and fair transparency to users. The blockchain referred to in this example is a novel application mode of computer technologies such as distributed data storage, point-to-point transmission, consensus mechanism, encryption algorithm, and the like. A block chain (Blockchain), which is essentially a decentralized database, is a series of data blocks associated by using a cryptographic method, and each data block contains information of a batch of network transactions, so as to verify the validity (anti-counterfeiting) of the information and generate a next block. The blockchain may include a blockchain underlying platform, a platform product service layer, an application service layer, and the like.
Step S206, sending the target key to the target executor, and backing up the target related information, the target key, and the target scheduling token to a central database.
For example, the target public key may be sent to the target executor, the target private key may be backed up to a central database, and the target related information and the target scheduling token may be backed up to the central database.
Step S106, the target scheduling token and the target calling request are sent to the target executor, so that the target executor obtains corresponding target response information according to the target scheduling token and the target calling request.
For example, the target executor may determine whether a user corresponding to the target invocation request has an invocation permission according to the target scheduling token.
Illustratively, the step S106 may further include: and sending the target scheduling token and the target calling request to a target executor according to a preset rate.
In addition, the scheduling center can also selectively decide the specific executor to execute the task according to the load conditions of the plurality of executors in the scheduling executing process.
Illustratively, the step S106 may further include:
step S106a, performing security authentication on the target user associated with the target client terminal, and determining whether the target user has the right to schedule the target actuator according to the security authentication result.
In order to further ensure the security of data scheduling, the target client terminal may also be subjected to security authentication to ensure that a target user associated with the target client terminal is a secure user.
Step S106b, if the authority to dispatch the target executor exists, the target dispatching token and the target calling request are sent to the target executor; and if the client terminal does not have the authority of scheduling the target executor, rejecting the scheduling of the client terminal to the target executor, generating access rejection information and sending the access rejection information to the client terminal.
For example, the target executor may perform a decryption operation on the target scheduling token to determine whether the target user has an authority to schedule the target executor according to a decryption result, where the target scheduling token is obtained by encrypting a target private key through a target encryption algorithm, so that the target scheduling token is decrypted and the target public key corresponding to the target private key is required. The target private key and the target public key are a pair of different but corresponding keys, wherein the target private key and the target public key are obtained in advance through a target encryption algorithm, the target private key is distributed to a dispatching center, and the target public key is used for decrypting a target dispatching token sent in the dispatching.
And step S108, receiving the target response information returned by the target actuator, and sending the target response information to the client terminal.
Illustratively, by adding authority control in an application layer, certain guarantee is provided in the aspect of safety management of an executor, the information modification of the executor is limited to authorized users, and the application side is protected in the aspect of data safety in a dispatching center platform layer. And an authentication mechanism is introduced in the aspect of interface calling, so that the safety of a registration mechanism of the dispatching center is protected on the one hand, and the application service serving as a registration party is ensured to be verified through the authorization of the dispatching center. And on the other hand, the service of the executor on the application side is protected, only the scheduling center side with the certificate can call the RPC service opened by the executor, and other clients without the certificate are intercepted. In addition, this embodiment may support javabeans, SHELL scripts, PYTHON scripts, NODEJS scripts, etc., where the javabeans will call the written methods through the JVM, and the scripts are executed through the engine corresponding to the JVM. And configuring a specific task category name for the JavaBean mode, and writing a corresponding execution script on line if the operation mode is selected as a script mode.
For example, the data scheduling system may further record a task record executed by the target executor, and perform visualization processing on the task record in the scheduling center, so that a target user views an execution log of the executor in an interface of the scheduling center.
Illustratively, the data scheduling method further includes the step of registering the target executor:
step S300, receiving a registration request sent by the target actuator, wherein the registration request carries a target registration token and registration information.
For example, the target registration token may be obtained by encrypting a name of the target execution through a target encryption algorithm and a target public key, and the target registration token is used to identify the target executor. The registration information includes actuator service IP information and port registration information.
Step S302, the target executor is verified according to the target registration token.
The target registration token may also be generated according to JWT, a JSON-based open standard that is implemented for passing claims between web application environments ((RFC 7519). the target registration token is designed to be compact and secure, and is suitable for single sign-on (SSO) scenarios for distributed sites.A JWT claim is typically used to pass authenticated user identity information between an identity provider and a service provider to facilitate resource acquisition from a resource server, as well as to add some additional claim information necessary for other business logic. This may be done based on the claim information, e.g., by verifying expiration time information of the target registration token to determine whether to register the target executor.
Illustratively, the step 302 may further include: in step S302a, a target key corresponding to the target executor is obtained. Step S302b, perform a decryption operation on the target registration token according to the target key and the target decryption method to obtain decryption information. Step S302c, determining whether the decryption information is the same as the target related information. Step S302d, if the decryption information is the same as the target related information, the verification is successful; and if the decryption information is not the same as the target related information, the verification fails.
Step S304, if the verification of the target actuator is successful, the target actuator is registered according to the registration information to generate registration success information, and the registration success information is sent to the target actuator; and if the verification of the target actuator fails, refusing to perform registration operation on the target actuator to generate registration failure information, and sending the registration failure information to the target actuator.
For example, the executor may add registration information corresponding to the executor and preconfigured token information to the scheduling center to register the executor through the scheduling center, where one scheduling center may register a plurality of executors; the current dispatching center can not strictly classify the actuators, and the authority control of the actuators is messy. Therefore, the scheme adds the management of the application system on the upper layer of the actuator management, authorizes the manager to the application system, further limits the management range of the actuator, and has certain safety guarantee in the aspect of data management. And after the executor application service configures the name of the executor allocated by the scheduling center, registering the executor service IP information and the port information to the scheduling center when the executor application service is started.
Example two
Fig. 2 is a schematic diagram of program modules of a second embodiment of a data scheduling system according to the present invention. Data scheduling system 20 may include or be divided into one or more program modules, stored in a storage medium and executed by one or more processors, to implement the present invention and implement the above-described data scheduling methods. The program modules referred to in the embodiments of the present invention refer to a series of computer program instruction segments that can perform specific functions, and are better suited than the program itself for describing the execution process of the data scheduling system 20 in the storage medium. The following description will specifically describe the functions of the program modules of the present embodiment:
a receiving module 200, configured to receive a target scheduling request sent by a client terminal.
A determining module 202, configured to determine a target executor according to the target scheduling request, where the target executor is configured to invoke, according to the target invocation request, corresponding target response information for the client terminal.
An obtaining module 204, configured to obtain a target scheduling token corresponding to the target executor.
A response module 206, configured to send the target scheduling token and the target invocation request to the target executor, so that the target executor obtains corresponding target response information according to the target scheduling token and the target invocation request.
Illustratively, the response module 206 is further configured to: and sending the target scheduling token and the target calling request to a target executor at a preset time frequency.
Illustratively, the response module 206 is further configured to: performing security authentication on a target user associated with the target client terminal, and judging whether the target user has the authority of scheduling the target actuator according to a security authentication result; if the authority of scheduling the target executor exists, the target scheduling token and the target calling request are sent to the target executor; and if the client terminal does not have the authority of scheduling the target executor, rejecting the scheduling of the client terminal to the target executor, generating access rejection information and sending the access rejection information to the client terminal.
And the sending module 208 is configured to receive the target response information returned by the target executor, and send the target response information to the client terminal.
Illustratively, the data scheduling system further comprises a configuration module configured to: receiving the target related information sent by the target actuator, wherein the target related information comprises the name of the target actuator; encrypting the target related information according to a pre-generated target secret key and a target encryption method to obtain the target scheduling token, and uploading the target track characteristic vector to a block chain; and sending the target secret key to the target executor, and backing up the target related information, the target secret key and the target scheduling token to a central database.
Illustratively, the data scheduling system further comprises a registration module configured to: receiving a registration request sent by the target actuator, wherein the registration request carries a target registration token and registration information; verifying the target executor according to the target registration token; if the verification of the target actuator is successful, performing registration operation on the target actuator according to the registration information to generate registration success information, and sending the registration success information to the target actuator; and if the verification of the target actuator fails, refusing to perform registration operation on the target actuator to generate registration failure information, and sending the registration failure information to the target actuator.
Illustratively, the registration module is further configured to: acquiring a target secret key corresponding to the target actuator; decrypting the target registration token according to the target secret key and a target decryption method to obtain decryption information; judging whether the decryption information is the same as the target related information or not; if the decryption information is the same as the target related information, the verification is successful; and if the decryption information is not the same as the target related information, the verification fails.
EXAMPLE III
Fig. 3 is a schematic diagram of a hardware architecture of a computer device according to a third embodiment of the present invention. In the present embodiment, the computer device 2 is a device capable of automatically performing numerical calculation and/or information processing in accordance with a preset or stored instruction. The computer device 2 may be a rack server, a blade server, a tower server or a rack server (including an independent server or a server cluster composed of a plurality of servers), and the like. As shown, the computer device 2 includes, but is not limited to, at least a memory 21, a processor 22, a network interface 23, and a data scheduling system 20 communicatively coupled to each other via a system bus.
In this embodiment, the memory 21 includes at least one type of computer-readable storage medium including a flash memory, a hard disk, a multimedia card, a card-type memory (e.g., SD or DX memory, etc.), a Random Access Memory (RAM), a Static Random Access Memory (SRAM), a Read Only Memory (ROM), an Electrically Erasable Programmable Read Only Memory (EEPROM), a Programmable Read Only Memory (PROM), a magnetic memory, a magnetic disk, an optical disk, and the like. In some embodiments, the storage 21 may be an internal storage unit of the computer device 2, such as a hard disk or a memory of the computer device 2. In other embodiments, the memory 21 may also be an external storage device of the computer device 2, such as a plug-in hard disk, a Smart Media Card (SMC), a Secure Digital (SD) Card, a Flash memory Card (Flash Card), or the like provided on the computer device 2. Of course, the memory 21 may also comprise both internal and external memory units of the computer device 2. In this embodiment, the memory 21 is generally used for storing an operating system installed in the computer device 2 and various application software, such as the program codes of the data scheduling system 20 of the second embodiment. Further, the memory 21 may also be used to temporarily store various types of data that have been output or are to be output.
The network interface 23 may comprise a wireless network interface or a wired network interface, and the network interface 23 is generally used for establishing communication connection between the computer device 2 and other electronic apparatuses. For example, the network interface 23 is used to connect the computer device 2 to an external terminal through a network, establish a data transmission channel and a communication connection between the computer device 2 and the external terminal, and the like. The network may be a wireless or wired network such as an Intranet (Intranet), the Internet (Internet), a Global System of Mobile communication (GSM), Wideband Code Division Multiple Access (WCDMA), a 4G network, a 5G network, Bluetooth (Bluetooth), Wi-Fi, and the like.
It is noted that fig. 3 only shows the computer device 2with components 20-23, but it is to be understood that not all shown components are required to be implemented, and that more or less components may be implemented instead.
In this embodiment, the data scheduling system 20 stored in the memory 21 can also be divided into one or more program modules, and the one or more program modules are stored in the memory 21 and executed by one or more processors (in this embodiment, the processor 22) to complete the present invention.
For example, fig. 2 is a schematic diagram of program modules for implementing the data scheduling system 20 according to a second embodiment of the present invention, in which the data scheduling system 20 may be divided into a receiving module 200, a determining module 202, an obtaining module 204, a responding module 206, and a sending module 208. The program modules referred to herein are a series of computer program instruction segments that can perform specific functions, and are more suitable than programs for describing the execution of the data scheduling system 20 in the computer device 2. The specific functions of the program modules 200 and 208 have been described in detail in the second embodiment, and are not described herein again.
Example four
The present embodiment also provides a computer-readable storage medium, such as a flash memory, a hard disk, a multimedia card, a card-type memory (e.g., SD or DX memory, etc.), a Random Access Memory (RAM), a Static Random Access Memory (SRAM), a read-only memory (ROM), an electrically erasable programmable read-only memory (EEPROM), a programmable read-only memory (PROM), a magnetic memory, a magnetic disk, an optical disk, a server, an App application mall, etc., on which a computer program is stored, which when executed by a processor implements corresponding functions. The computer-readable storage medium of this embodiment is used in the data scheduling system 20, and when executed by a processor, implements the data scheduling method of the first embodiment.
The above-mentioned serial numbers of the embodiments of the present invention are merely for description and do not represent the merits of the embodiments.
Through the above description of the embodiments, those skilled in the art will clearly understand that the method of the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but in many cases, the former is a better implementation manner.
The above description is only a preferred embodiment of the present invention, and not intended to limit the scope of the present invention, and all modifications of equivalent structures and equivalent processes, which are made by using the contents of the present specification and the accompanying drawings, or directly or indirectly applied to other related technical fields, are included in the scope of the present invention.
Claims (10)
1. A method for scheduling data, the method comprising:
receiving a target scheduling request sent by a client terminal;
determining a target actuator according to the target scheduling request, wherein the target actuator is used for calling corresponding target response information for the client terminal according to the target calling request;
acquiring a target scheduling token corresponding to the target actuator;
sending the target scheduling token and the target calling request to the target executor so that the target executor obtains corresponding target response information according to the target scheduling token and the target calling request; and
and receiving target response information returned by the target actuator, and sending the target response information to the client terminal.
2. The data scheduling method of claim 1, wherein said sending the target scheduling token and the target invocation request into the target executor, comprises:
and sending the target scheduling token and the target calling request to a target executor according to a preset frequency.
3. The data scheduling method of claim 1, wherein said sending the target scheduling token and the target invocation request into the target executor, comprises:
performing security authentication on a target user associated with the target client terminal, and judging whether the target user has the authority of scheduling the target actuator according to a security authentication result;
if the authority of scheduling the target executor exists, the target scheduling token and the target calling request are sent to the target executor;
and if the client terminal does not have the authority of scheduling the target executor, rejecting the scheduling of the client terminal to the target executor, generating access rejection information and sending the access rejection information to the client terminal.
4. The data scheduling method of claim 1, wherein the method of configuring the target scheduling token comprises:
receiving the target related information sent by the target actuator, wherein the target related information comprises the name of the target actuator;
encrypting the target related information according to a pre-generated target secret key and a target encryption method to obtain the target scheduling token, and uploading the target track characteristic vector to a block chain;
and sending the target secret key to the target executor, and backing up the target related information, the target secret key and the target scheduling token to a central database.
5. The data scheduling method of claim 4, further comprising the step of pre-registering the target executor of:
receiving a registration request sent by the target actuator, wherein the registration request carries a target registration token and registration information;
verifying the target executor according to the target registration token; and
if the verification of the target actuator is successful, performing registration operation on the target actuator according to the registration information to generate registration success information, and sending the registration success information to the target actuator;
and if the verification of the target actuator fails, refusing to perform registration operation on the target actuator to generate registration failure information, and sending the registration failure information to the target actuator.
6. The data scheduling method of claim 5 wherein validating the target executor based on the target scheduling token comprises:
acquiring a target secret key corresponding to the target actuator;
decrypting the target registration token according to the target secret key and a target decryption method to obtain decryption information;
judging whether the decryption information is the same as the target related information or not;
if the decryption information is the same as the target related information, the verification is successful;
and if the decryption information is not the same as the target related information, the verification fails.
7. A data scheduling system, comprising:
the receiving module is used for receiving a target scheduling request sent by a client terminal;
a determining module, configured to determine a target executor according to the target scheduling request, where the target executor is configured to invoke, according to the target invocation request, corresponding target response information for the client terminal;
the acquisition module is used for acquiring a target scheduling token corresponding to the target actuator;
the response module is used for sending the target scheduling token and the target calling request to the target executor so that the target executor obtains corresponding target response information according to the target scheduling token and the target calling request; and
and the sending module is used for receiving the target response information returned by the target actuator and sending the target response information to the client terminal.
8. The data scheduling system of claim 7, wherein the response module is further to: and sending the target scheduling token and the target calling request to a target executor according to a preset frequency.
9. A computer arrangement comprising a memory, a processor and a computer program stored on the memory and executable on the processor, characterized in that the computer program, when executed by the processor, carries out the steps of the data scheduling method according to any one of claims 1 to 6.
10. A computer-readable storage medium, in which a computer program is stored which is executable by at least one processor for causing the at least one processor to carry out the steps of the data scheduling method according to any one of claims 1 to 6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010744239.5A CN111880919B (en) | 2020-07-29 | 2020-07-29 | Data scheduling method, system and computer equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010744239.5A CN111880919B (en) | 2020-07-29 | 2020-07-29 | Data scheduling method, system and computer equipment |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111880919A true CN111880919A (en) | 2020-11-03 |
| CN111880919B CN111880919B (en) | 2024-04-02 |
Family
ID=73201380
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010744239.5A Active CN111880919B (en) | 2020-07-29 | 2020-07-29 | Data scheduling method, system and computer equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111880919B (en) |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113572759A (en) * | 2021-07-21 | 2021-10-29 | 华控清交信息科技(北京)有限公司 | Data management method and device, electronic equipment and storage medium |
| CN113676494A (en) * | 2021-10-21 | 2021-11-19 | 深圳致星科技有限公司 | Centralized data processing method and device |
| CN114491652A (en) * | 2022-04-19 | 2022-05-13 | 广州市保伦电子有限公司 | Method for encrypting, backing up and decrypting and restoring database data and processing terminal |
| CN115080205A (en) * | 2022-05-27 | 2022-09-20 | 北京百度网讯科技有限公司 | Task execution method and device, electronic equipment and readable storage medium |
Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106843170A (en) * | 2016-11-30 | 2017-06-13 | 浙江中控软件技术有限公司 | Method for scheduling task based on token |
| CN106874090A (en) * | 2017-01-23 | 2017-06-20 | 北京思特奇信息技术股份有限公司 | Job scheduling method and system based on cloud system |
| CN108256721A (en) * | 2017-11-16 | 2018-07-06 | 中国平安财产保险股份有限公司 | A kind of method for scheduling task, terminal device and medium |
| CN109150910A (en) * | 2018-10-11 | 2019-01-04 | 平安科技（深圳）有限公司 | Log in token generation and verification method, device and storage medium |
| CN110011996A (en) * | 2019-03-26 | 2019-07-12 | 阿里巴巴集团控股有限公司 | Application authorization method and device and electronic equipment based on block chain |
| CN110058941A (en) * | 2019-03-16 | 2019-07-26 | 平安城市建设科技(深圳)有限公司 | Task scheduling and managing method, device, equipment and storage medium |
| CN110855760A (en) * | 2019-10-29 | 2020-02-28 | 上海海加网络科技有限公司 | Block chain-based distributed secure storage system deployment method |
| CN111045810A (en) * | 2019-12-17 | 2020-04-21 | 浙江大华技术股份有限公司 | Task scheduling processing method and device |
| US20200133718A1 (en) * | 2018-10-31 | 2020-04-30 | Nutanix, Inc. | Virtual machine migration task management |
-
2020
- 2020-07-29 CN CN202010744239.5A patent/CN111880919B/en active Active
Patent Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106843170A (en) * | 2016-11-30 | 2017-06-13 | 浙江中控软件技术有限公司 | Method for scheduling task based on token |
| CN106874090A (en) * | 2017-01-23 | 2017-06-20 | 北京思特奇信息技术股份有限公司 | Job scheduling method and system based on cloud system |
| CN108256721A (en) * | 2017-11-16 | 2018-07-06 | 中国平安财产保险股份有限公司 | A kind of method for scheduling task, terminal device and medium |
| CN109150910A (en) * | 2018-10-11 | 2019-01-04 | 平安科技（深圳）有限公司 | Log in token generation and verification method, device and storage medium |
| US20200133718A1 (en) * | 2018-10-31 | 2020-04-30 | Nutanix, Inc. | Virtual machine migration task management |
| CN110058941A (en) * | 2019-03-16 | 2019-07-26 | 平安城市建设科技(深圳)有限公司 | Task scheduling and managing method, device, equipment and storage medium |
| CN110011996A (en) * | 2019-03-26 | 2019-07-12 | 阿里巴巴集团控股有限公司 | Application authorization method and device and electronic equipment based on block chain |
| CN110855760A (en) * | 2019-10-29 | 2020-02-28 | 上海海加网络科技有限公司 | Block chain-based distributed secure storage system deployment method |
| CN111045810A (en) * | 2019-12-17 | 2020-04-21 | 浙江大华技术股份有限公司 | Task scheduling processing method and device |
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113572759A (en) * | 2021-07-21 | 2021-10-29 | 华控清交信息科技(北京)有限公司 | Data management method and device, electronic equipment and storage medium |
| CN113676494A (en) * | 2021-10-21 | 2021-11-19 | 深圳致星科技有限公司 | Centralized data processing method and device |
| CN113676494B (en) * | 2021-10-21 | 2022-01-07 | 深圳致星科技有限公司 | Centralized data processing method and device |
| CN114491652A (en) * | 2022-04-19 | 2022-05-13 | 广州市保伦电子有限公司 | Method for encrypting, backing up and decrypting and restoring database data and processing terminal |
| CN115080205A (en) * | 2022-05-27 | 2022-09-20 | 北京百度网讯科技有限公司 | Task execution method and device, electronic equipment and readable storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111880919B (en) | 2024-04-02 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US9621355B1 (en) | Securely authorizing client applications on devices to hosted services | |
| WO2021000337A1 (en) | System and method for mapping decentralized identifiers to real-world entities | |
| CN111880919B (en) | Data scheduling method, system and computer equipment | |
| CN112215608A (en) | Data processing method and device | |
| CN111881483B (en) | Resource account binding method, device, equipment and medium based on blockchain | |
| CN112688773A (en) | Token generation and verification method and device | |
| CN111526111B (en) | Control method, device and equipment for logging in light application and computer storage medium | |
| CN110381075B (en) | Block chain-based equipment identity authentication method and device | |
| CN111914293A (en) | Data access authority verification method and device, computer equipment and storage medium | |
| CN111340483A (en) | Data management method based on block chain and related equipment | |
| CN112235301B (en) | Access right verification method and device and electronic equipment | |
| CN111597537B (en) | Block chain network-based certificate issuing method, related equipment and medium | |
| CN114978635A (en) | Cross-domain authentication method and device, and user registration method and device | |
| CN111414640B (en) | Key access control method and device | |
| CN115473648A (en) | Certificate signing and issuing system and related equipment | |
| CN111628863A (en) | Data signature method and device, electronic equipment and storage medium | |
| CN112446050B (en) | Business data processing method and device applied to block chain system | |
| CN114338091A (en) | Data transmission method and device, electronic equipment and storage medium | |
| CN109688158B (en) | Financial execution chain authentication method, electronic device and storage medium | |
| CN112560073A (en) | Method, device and system for verifying data source reliability | |
| CN114024692A (en) | Signing method, device and system | |
| CN112132588A (en) | Data processing method and device based on block chain, routing equipment and storage medium | |
| CN111404901A (en) | Information verification method and device | |
| CN114615279B (en) | Trusted multiparty data collaboration method and system based on blockchain technology | |
| CN116032494B (en) | Data interaction method, blockchain predictor, device and medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |