CN111880919B - Data scheduling method, system and computer equipment - Google Patents
Data scheduling method, system and computer equipment Download PDFInfo
- Publication number
- CN111880919B CN111880919B CN202010744239.5A CN202010744239A CN111880919B CN 111880919 B CN111880919 B CN 111880919B CN 202010744239 A CN202010744239 A CN 202010744239A CN 111880919 B CN111880919 B CN 111880919B
- Authority
- CN
- China
- Prior art keywords
- target
- executor
- scheduling
- 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.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 43
- 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 10
- 238000004422 calculation algorithm Methods 0.000 description 19
- 238000007726 management method Methods 0.000 description 6
- 238000010586 diagram Methods 0.000 description 5
- 230000006870 function Effects 0.000 description 5
- 238000012545 processing Methods 0.000 description 5
- 230000007246 mechanism Effects 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
- 230000008569 process Effects 0.000 description 3
- 238000004891 communication Methods 0.000 description 2
- 238000010295 mobile communication Methods 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
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 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
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 executor according to the target scheduling request, wherein the target executor 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 executor; 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; and receiving target response information returned by the target executor and sending the target response information to the client terminal. The invention reduces the consumption of resources when the task scheduling is more in the access party, improves the data scheduling safety when the task scheduling is performed, 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 is generally unavoidable when an IT system processes business demands, can be triggered by a self-defined alarm reminding mode or by a mode of setting timing tasks of an operating system, but cannot release the dependence of personnel and the occurrence of single-node faults. At present, distributed task scheduling can be independently built through each application system, however, the inventor of the application finds out in the research that when the access party is more, the resource fragmentation can be caused, the consumption of the resource can be increased, and a great amount of resource waste is caused. Therefore, how to reduce the consumption of resources when the task scheduling is more to the access party and improve the data scheduling safety when the task scheduling is performed, thereby further improving the safety and efficiency of the task scheduling, and becoming one of the technical problems to be solved currently.
Disclosure of Invention
In view of the foregoing, it is necessary to provide a data scheduling method, system, computer device and computer readable storage medium, so as to solve the technical problems of greater resource consumption and lower data scheduling security when the current task scheduling is more in access parties.
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 executor according to the target scheduling request, wherein the target executor 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 executor;
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; and
And receiving target response information returned by the target executor, and sending the target response information to the client terminal.
Illustratively, the sending the target dispatch token and the target call request to the target executor includes:
the target scheduling token and the target call request are sent to a target executor at a predetermined time frequency.
Illustratively, the sending the target dispatch token and the target call 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 authority to schedule the target executor according to a security authentication result;
if the right to dispatch the target executor is available, the target dispatch token and a target call request are sent to the target executor;
and if the client terminal does not have the authority to schedule the target executor, the client terminal is refused to schedule the target executor, and access refusing information is generated and sent to the client terminal.
Illustratively, the method further comprises the step of configuring the target dispatch token:
receiving the target related information sent by the target executor, wherein the target related information comprises the name of the target executor;
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 a target track feature vector to a blockchain;
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 method further comprises the step of pre-registering the target executor:
receiving a registration request sent by the target executor, 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 executor is successful, performing registration operation on the target executor according to the registration information to generate registration success information, and sending the registration success information to the target executor;
and if the verification of the target executor fails, refusing to carry out registration operation on the target executor so as to generate registration failure information, and sending the registration failure information to the target executor.
Illustratively, validating the target executor according to the target scheduling token includes:
acquiring a target secret key corresponding to the target executor;
performing decryption operation on the target registration token according to the target secret key and the target decryption method to obtain decryption information;
judging whether the decryption information is the same as the target related information;
if the decryption information is the same as the target related information, the verification is successful;
if the decryption information is not identical to the target related information, verification fails.
In order to achieve the above object, an embodiment of the present invention further provides a data scheduling system, which is characterized by including:
the receiving module is used for receiving a target scheduling request sent by the client terminal;
the determining module is used for determining a target executor according to the target scheduling request, wherein the target executor is used for calling corresponding target response information for the client terminal according to the target calling request;
the acquisition module is used for acquiring a target scheduling token corresponding to the target executor;
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 executor 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 preset frequency.
To achieve the above object, an embodiment of the present invention further provides a computer device, where the computer device includes a memory, a processor, and a computer program stored on the memory and executable on the processor, where the computer program is executed by the processor to implement 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 having a computer program stored therein, the computer program being executable by at least one processor to cause the at least one processor to perform the steps of the data scheduling method as described above.
The data scheduling method, the system, the computer equipment and the computer readable storage medium can reduce the consumption of resources when more access parties are needed by task scheduling through centralized management of the target executor and a unified scheduling mode, improve the data scheduling safety during task scheduling, and improve the safety and efficiency of task scheduling.
Drawings
Fig. 1 is a flow chart of a data scheduling method according to an embodiment of the invention.
Fig. 2 is a schematic diagram of a program module of a data scheduling system according to a second embodiment of the present invention.
Fig. 3 is a schematic diagram of a hardware structure of a third embodiment of the computer device of the present invention.
Detailed Description
The present invention will be described in further detail with reference to the drawings and examples, in order to make the objects, technical solutions and advantages of the present invention more apparent. It should be understood that the specific embodiments described herein are for purposes of illustration only and are not intended to limit the scope of the invention. All other embodiments, which can be made by those skilled in the art based on the embodiments of the invention without making any inventive effort, are intended to be within the scope of the invention.
It should be noted that the description of "first", "second", etc. in this disclosure is for descriptive purposes only and is not to be construed as indicating or implying a relative importance or implying an indication of the number of technical features being indicated. Thus, a feature defining "a first" or "a second" may explicitly or implicitly include at least one such feature. In addition, the technical solutions of the embodiments may be combined with each other, but it is necessary to base that the technical solutions can be realized by those skilled in the art, and when the technical solutions are contradictory or cannot be realized, the combination of the technical solutions should be considered to be absent and not within the scope of protection claimed in the present invention.
In the following embodiments, an exemplary description will be made with the computer device 2 as an execution subject.
Example 1
Referring to fig. 1, a flowchart illustrating steps of a data scheduling method according to an embodiment of the present invention is shown. It will be appreciated that the flow charts in the method embodiments are not intended to limit the order in which the steps are performed. An exemplary description will be made below with the computer device 2 as an execution subject. Specifically, the following is described.
Step S100, receiving a target scheduling request sent by a client terminal.
Illustratively, the target scheduling request is for requesting scheduling of the target executor. And the target executor 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 the client terminal so as to complete the scheduling of the target executor through 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, 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 executor has a plurality, and a plurality of target executors can be deployed in different service systems, and the service systems may run on different operating systems and are mutually dependent.
Step S102, determining a target executor according to the target scheduling request, wherein the target executor 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. From the target executor information, a target executor corresponding to a target scheduling request may 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, from which the target executor may obtain the target scheduling token. The target dispatch 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 having the target scheduling token, and the target executor may not be directly accessed and scheduled without the target scheduling token.
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 executor, where the target related information includes a name of the target executor.
And 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 feature vector into a blockchain.
The target secret key is an secret key corresponding to a target encryption algorithm, the target encryption algorithm can be an asymmetric encryption algorithm, the target secret key comprises a target public key and a target private key, and the target public key and the target private key can be obtained through the corresponding asymmetric encryption algorithm. Among these, the so-called asymmetric encryption algorithm requires two keys: public keys (public keys) and private keys (private keys); wherein the public key and the private key are a pair, and if the data is encrypted by the public key, the data can be decrypted only by the corresponding private key. Just as encryption and decryption use two different keys, this algorithm is called an asymmetric encryption algorithm, which may be an RSA algorithm, for example, (SHA 256withRSA, SHA384withRSA, SHA512withRSA, hmacSHA, hmacSHA384, hmacSHA512, SHA256withECDSA, SHA384withECDSA, SHA512 withECDSA) or the like, or an Elgamal algorithm, a knapsack algorithm, a Rabin algorithm, a D-H algorithm, an ECC (elliptic curve encryption algorithm) algorithm, or an SM2 algorithm or the like.
The target dispatch token may also be generated from JWT (Json web token JSON-based open standard) which is a JSON-based open standard ((RFC 7519) implemented to pass assertions between network application environments, the token being designed to be compact and secure for use in a Single Sign On (SSO) scenario for distributed sites.
Illustratively, uploading the target dispatch token vector to the blockchain may ensure its security and fair transparency to the user. The blockchain referred to in this example is a novel mode of application for computer technology such as distributed data storage, point-to-point transmission, consensus mechanisms, encryption algorithms, and the like. The Blockchain (Blockchain), which is essentially a decentralised database, is a string of data blocks that are generated by cryptographic means in association, each data block containing a batch of information of network transactions for verifying the validity of the information (anti-counterfeiting) and generating the next block. The blockchain may include a blockchain underlying platform, a platform product services layer, an application services 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 a central database.
And 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, according to the target scheduling token, whether the user corresponding to the target call request has a call authority.
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 dispatching center can selectively decide the specific executor to execute the task according to the load conditions of the plurality of executors in the process of executing dispatching.
Illustratively, the step S106 may further include:
and step S106a, carrying out security authentication on a target user associated with the target client terminal, and judging whether the target user has the authority to schedule the target executor according to the security authentication result.
In order to further ensure the security of data scheduling, the target client terminal can be subjected to security authentication to ensure that the target user associated with the target client terminal is a secure user.
Step S106b, if the authority for scheduling the target executor is provided, 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 to schedule the target executor, the client terminal is refused to schedule the target executor, and access refusing information is generated and sent to the client terminal.
The target executor may perform decryption operation on the target scheduling token to determine, according to a decryption result, whether the target user has authority to schedule the target executor, where the target scheduling token is obtained by encrypting a target private key according to a target encryption algorithm, so that the target scheduling token is decrypted by using the target public key corresponding to the target private key. The target private key and the target public key are a pair of different but corresponding secret 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 target response information returned by the target executor and sending the target response information to the client terminal.
By adding authority control at the application level, a certain guarantee is provided in the aspect of safety management of the executor, the information modification of the executor is ensured to be limited to authorized users, and the protection of the application side in the aspect of data safety is given at the dispatch center platform level. An authentication mechanism is introduced in the aspect of interface calling, so that the security of a dispatching center registration mechanism is protected, and the application service serving as a registration party is verified by the authorization of the dispatching center. On the other hand, the application side executor service is protected, only the dispatching center with the credentials can call the RPC service opened by the executor, and other clients without the credentials are intercepted. In addition, the present embodiment may support JavaBean, SHELL script, PYTHON script, NODEJS script, etc., where javabeans call the written method through the JVM, and the script is executed through the engine corresponding to the JVM. And configuring a task class name of specific execution for the JavaBean mode, and if the operation mode is selected as the script mode, writing a corresponding execution script on line.
The data scheduling system may also 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 can view an execution log of the executor in an interface of the scheduling center.
The data scheduling method further includes, for example, a registration step of the target executor:
step S300, receiving a registration request sent by the target executor, wherein the registration request carries a target registration token and registration information.
Illustratively, the target registration token may be obtained by encrypting a name of the target execution by a target encryption algorithm and a target public key, where the target registration token is used to identify the target executor. The registration information includes executor service IP information and port registration information.
And step S302, verifying the target executor according to the target registration token.
The target registration token may also be generated from JWTs, which are Json-based open standards for passing assertions between network application environments ((RFC 7519). The target registration token is designed to be compact and secure for Single Sign On (SSO) scenarios for distributed sites.
Illustratively, the step 302 may further include: step S302a, obtaining a target key corresponding to the target executor. Step S302b, performing a decryption operation on the target registration token according to the target key and the target decryption method, so as 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; if the decryption information is not identical to the target related information, verification fails.
Step S304, if the verification of the target executor is successful, performing registration operation on the target executor according to the registration information to generate registration success information, and sending the registration success information to the target executor; and if the verification of the target executor fails, refusing to carry out registration operation on the target executor so as to generate registration failure information, and sending the registration failure information to the target executor.
For example, the executor may add registration information corresponding to the executor and pre-configured token information to the dispatch center to register the executor through the dispatch center, where one dispatch center may register multiple executors; at present, the dispatching center cannot strictly classify the executors, and the permission control of the executors is messy. Therefore, the scheme adds the management of the application system in the upper layer of the executor management, authorizes the management personnel of the application system, further limits the management range of the executor, and simultaneously has certain security guarantee in the aspect of data management. After the executor application service configures the name of the executor distributed by the dispatching center, the executor service IP information and the port information are registered to the dispatching center when the executor application service configures the name of the executor distributed by the dispatching center.
Example two
Fig. 2 is a schematic diagram of a program module of a data scheduling system according to a second embodiment of the present invention. The data scheduling system 20 may include or be partitioned into one or more program modules that are stored in a storage medium and executed by one or more processors to perform the present invention and to implement the data scheduling methods described above. Program modules in accordance with the embodiments of the present invention are directed to a series of computer program instruction segments capable of performing the specified functions and are more suitable than the programs themselves for describing the execution of the data scheduling system 20 in a storage medium. The following description will specifically describe functions of each program module of the present embodiment:
and the receiving module 200 is configured to receive a target scheduling request sent by the 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 corresponding target response information for the client terminal according to the target invocation request.
And the obtaining module 204 is configured to obtain a target scheduling token corresponding to the target executor.
And the response module 206 is configured to send the target scheduling token and the target call request to the target executor, so that the target executor obtains corresponding target response information according to the target scheduling token and the target call request.
Illustratively, the response module 206 is further configured to: the target scheduling token and the target call request are sent to a target executor at a predetermined 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 authority to schedule the target executor according to a security authentication result; if the right to dispatch the target executor is available, the target dispatch token and a target call request are sent to the target executor; and if the client terminal does not have the authority to schedule the target executor, the client terminal is refused to schedule the target executor, and access refusing information is generated and sent 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 for: receiving the target related information sent by the target executor, wherein the target related information comprises the name of the target executor; 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 a target track feature vector to a blockchain; 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 for: receiving a registration request sent by the target executor, 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 executor is successful, performing registration operation on the target executor according to the registration information to generate registration success information, and sending the registration success information to the target executor; and if the verification of the target executor fails, refusing to carry out registration operation on the target executor so as to generate registration failure information, and sending the registration failure information to the target executor.
Illustratively, the registration module is further configured to: acquiring a target secret key corresponding to the target executor; performing decryption operation on the target registration token according to the target secret key and the target decryption method to obtain decryption information; judging whether the decryption information is the same as the target related information; if the decryption information is the same as the target related information, the verification is successful; if the decryption information is not identical to the target related information, verification fails.
Example III
Referring to fig. 3, a hardware architecture diagram of a computer device according to a third embodiment of the present invention is shown. In this embodiment, the computer device 2 is a device capable of automatically performing numerical calculation and/or information processing according to 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 a stand-alone server, or a server cluster made up of multiple servers), or 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 flash memory, a hard disk, a multimedia card, a card 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 memory 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, which are provided on the computer device 2. Of course, the memory 21 may also include both internal storage units of the computer device 2 and external storage devices. In this embodiment, the memory 21 is generally used to store an operating system and various types of application software installed on the computer device 2, such as program codes of the data scheduling system 20 of the second embodiment. Further, the memory 21 may be used to temporarily store various types of data that have been output or are to be output.
The processor 22 may be a central processing unit (Central Processing Unit, CPU), controller, microcontroller, microprocessor, or other data processing chip in some embodiments. The processor 22 is typically used to control the overall operation of the computer device 2. In this embodiment, the processor 22 is configured to execute the program code stored in the memory 21 or process data, for example, execute the data scheduling system 20, so as to implement the data scheduling method of the first embodiment.
The network interface 23 may comprise a wireless network interface or a wired network interface, which network interface 23 is typically used for establishing a communication connection between the computer apparatus 2 and other electronic devices. 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 an Intranet (Intranet), the Internet (Internet), a global system for mobile communications (Global System of Mobile communication, GSM), wideband code division multiple access (Wideband Code Division Multiple Access, WCDMA), a 4G network, a 5G network, bluetooth (Bluetooth), wi-Fi, or other wireless or wired network.
It is noted that fig. 3 only shows a computer device 2 having components 20-23, but it is understood that not all of the illustrated components are required to be implemented, and that more or fewer components may alternatively be implemented.
In the present embodiment, the data scheduling system 20 stored in the memory 21 may also be divided into one or more program modules, which are stored in the memory 21 and executed by one or more processors (the processor 22 in the present embodiment) to complete the present invention.
For example, fig. 2 shows a schematic diagram of a program module for implementing the data scheduling system 20 according to the second embodiment of the present invention, where 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. Program modules in the present invention are understood to mean a series of computer program instruction segments capable of performing a specific function, more appropriately than a program, describing the execution of the data scheduling system 20 in the computer device 2. The specific functions of the program modules 200-208 are described in detail in the second embodiment, and are not described herein.
Example IV
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 store, etc., on which a computer program is stored, which when executed by a processor, performs the corresponding functions. The computer readable storage medium of the present 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 foregoing embodiment numbers of the present invention are merely for the purpose of description, and do not represent the advantages or disadvantages of the embodiments.
From the above description of the embodiments, it will be clear to those skilled in the art that the above-described embodiment method may be implemented by means of software plus a necessary general hardware platform, but of course may also be implemented by means of hardware, but in many cases the former is a preferred embodiment.
The foregoing description is only of the preferred embodiments of the present invention, and is not intended to limit the scope of the invention, but rather is intended to cover any equivalents of the structures or equivalent processes disclosed herein or in the alternative, which may be employed directly or indirectly in other related arts.
Claims (9)
1. The data scheduling method is characterized by being used for a scheduling center of a data scheduling system, wherein the scheduling center is a program scheduling node in a server cluster; the method comprises the following steps:
receiving a target call request sent by a client terminal;
determining a target executor according to the target call request, wherein the target executor is used for calling corresponding target response information for the client terminal according to the target call request; the target executor is one or more program execution nodes in a server cluster, and the program can be executed by each program execution node; a plurality of target executors are deployed in different business systems and mutually depend;
acquiring a target scheduling token corresponding to the target executor;
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; and
Receiving target response information returned by the target executor, and sending the target response information to a client terminal;
the configuration method of the target scheduling token comprises the following steps:
receiving target related information sent by the target executor, wherein the target related information comprises the name of the target executor;
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 a target track feature vector to a blockchain;
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.
2. The data scheduling method of claim 1, wherein the sending the target scheduling token and the target call request into the target executor comprises:
and sending the target scheduling token and the target calling request to a target executor according to preset frequency.
3. The data scheduling method of claim 1, wherein the sending the target scheduling token and the target call request into the target executor comprises:
performing security authentication on a target user associated with the client terminal, and judging whether the target user has authority to schedule the target executor according to a security authentication result;
if the right to dispatch the target executor is available, the target dispatch token and a target call request are sent to the target executor;
and if the client terminal does not have the authority to schedule the target executor, the client terminal is refused to schedule the target executor, and access refusing information is generated and sent to the client terminal.
4. The data scheduling method of claim 1, further comprising the step of registering the target executor in advance:
receiving a registration request sent by the target executor, 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 executor is successful, performing registration operation on the target executor according to the registration information to generate registration success information, and sending the registration success information to the target executor;
and if the verification of the target executor fails, refusing to perform registration operation on the target executor to generate registration failure information, and sending the registration failure information to the target executor.
5. The data scheduling method of claim 4, wherein validating the target executor based on the target scheduling token comprises:
acquiring a target secret key corresponding to the target executor;
performing decryption operation on the target registration token according to the target secret key and the target decryption method to obtain decryption information;
judging whether the decryption information is the same as the target related information;
if the decryption information is the same as the target related information, the verification is successful;
if the decryption information is not identical to the target related information, verification fails.
6. The data scheduling system is characterized by being used for a scheduling center, wherein the scheduling center is a program scheduling node in a server cluster; comprising the following steps:
the receiving module is used for receiving a target call request sent by the client terminal;
the determining module is used for determining a target executor according to the target calling request, wherein the target executor is used for calling corresponding target response information for the client terminal according to the target calling request; the target executor is one or more program execution nodes in a server cluster, and the program can be executed by each program execution node; a plurality of target executors are deployed in different business systems and mutually depend;
the acquisition module is used for acquiring a target scheduling token corresponding to the target executor;
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
The sending module is used for receiving the target response information returned by the target executor and sending the target response information to the client terminal;
a configuration module for:
receiving target related information sent by the target executor, wherein the target related information comprises the name of the target executor;
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 a target track feature vector to a blockchain;
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.
7. The data scheduling system of claim 6, wherein the response module is further configured to: and sending the target scheduling token and the target calling request to a target executor according to preset frequency.
8. A computer device 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 implements the steps of the data scheduling method of any one of claims 1 to 5.
9. A computer readable storage medium, characterized in that the computer readable storage medium has stored therein a computer program executable by at least one processor to cause the at least one processor to perform the steps of the data scheduling method according to any one of claims 1 to 5.
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 CN111880919A (en) | 2020-11-03 |
| CN111880919B true 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) |
Families Citing this family (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113572759B (en) * | 2021-07-21 | 2023-05-23 | 华控清交信息科技(北京)有限公司 | Data management method and device, electronic equipment and storage medium |
| 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 |
| CN115080205B (en) * | 2022-05-27 | 2023-07-25 | 北京百度网讯科技有限公司 | Task execution method, device, electronic equipment and readable storage medium |
Citations (8)
| 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 |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US11194620B2 (en) * | 2018-10-31 | 2021-12-07 | Nutanix, Inc. | Virtual machine migration task management |
-
2020
- 2020-07-29 CN CN202010744239.5A patent/CN111880919B/en active Active
Patent Citations (8)
| 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 |
| 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 |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111880919A (en) | 2020-11-03 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111880919B (en) | Data scheduling method, system and computer equipment | |
| US9621355B1 (en) | Securely authorizing client applications on devices to hosted services | |
| US11025415B2 (en) | Cryptographic operation method, method for creating working key, cryptographic service platform, and cryptographic service device | |
| CN110381075B (en) | Block chain-based equipment identity authentication method and device | |
| CN112688773A (en) | Token generation and verification method and device | |
| CN114978635B (en) | Cross-domain authentication method and device, user registration method and device | |
| CN111914293A (en) | Data access authority verification method and device, computer equipment and storage medium | |
| CN112235301B (en) | Access right verification method and device and electronic equipment | |
| CN112448956A (en) | Authority processing method and device of short message verification code and computer equipment | |
| CN115473648A (en) | Certificate signing and issuing system and related equipment | |
| CN112446050B (en) | Business data processing method and device applied to block chain system | |
| CN111062059A (en) | Method and device for service processing | |
| CN111597537B (en) | Block chain network-based certificate issuing method, related equipment and medium | |
| CN111628863B (en) | Data signature method and device, electronic equipment and storage medium | |
| CN110753029B (en) | Identity verification method and biological identification platform | |
| CN116226879A (en) | Service interface access control method, device, computer equipment and storage medium | |
| CN115482132A (en) | Data processing method and device for electronic contract based on block chain and server | |
| CN109688158B (en) | Financial execution chain authentication method, electronic device and storage medium | |
| CN114861144A (en) | Data authority processing method based on block chain | |
| CN114338091A (en) | Data transmission method and device, electronic equipment and storage medium | |
| CN114154182A (en) | Information encryption method and device, storage medium and electronic device | |
| CN112560073A (en) | Method, device and system for verifying data source reliability | |
| CN114024692A (en) | Signing method, device and system | |
| CN111404901A (en) | Information verification method and device | |
| CN117040930B (en) | Resource processing method, device, product, equipment and medium of block chain network |
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 |