CN101753334B - Work Management and Scheduling Method of Network System - Google Patents

Abstract

The invention relates to a work management and scheduling method of a network system, which comprises the following steps: utilizing a scheduling program unit to receive a working entity and store the working entity and schedule a corresponding execution time so as to construct a working queue which runs independently; analyzing a working requirement sent by an application layer by using a working management unit to extract a corresponding working entity contained in the working requirement; and judging whether the hardware device required by the work request is available or not so as to determine whether to store the corresponding work entity of the work request to the work queue or not. By this method, the work management unit responds to the work request of the application layer in a short time, so that the application layer can perform the next work request without waiting for the response of the hardware device. The work queue can adjust the execution sequence of the work entity or update the set parameters according to the data dependency, the authority value and the set parameters, so as to quickly obtain the correct execution result of the work requirement and improve the work efficiency of the network system.

Description

Work Management and Scheduling Method of Network System

technical field

The present invention relates to a method of work management and scheduling, in particular to a method of establishing an independently running work queue (that is, a queue, referred to herein as a queue) in a network system, so that the application layer does not need to wait for a response from a hardware device. Work management and scheduling methods for network systems. the

Background technique

Please refer to FIG. 1 , which is a schematic diagram of an execution flow of a work management unit of a general network system. Its system includes Application Layer, Core Layer, Device Driver Layer, Job Queue and Object Manager (OM). the

The work management unit first receives a work request from the application layer (step S101), and then calls the program interface of the core layer (that is, the interface, which is referred to as an interface herein) to process the work request (step S102). Whether the programming statement required by the core layer analysis work meets the specification (step S103), if the analysis result is in conformity, the work requirement is recorded, and the program interface of the call device driver layer is executed according to the work requirement. Application Specific Integrated Circuit, ASIC) program setting (step S104), if the job entity (Job Entity) needs to operate the relevant hardware device, it needs to wait for the hardware device to complete the response (step S105), and then the next job entity can be executed. the

Then, it detects whether the program setting of the ASIC is completed (step S106), if so (that is, all relevant work entities are executed), the device driver layer outputs completion information to the work management unit through the core layer (step S107). The application layer obtains the response information of the completion of the work request from the work management unit, thereby ending the work request (step S108 ) and executing the next work request. the

However, the prior art has an insurmountable problem, that is, when the hardware device I/O required by the work request responds to the hardware device work, or some of the required resources are occupied, it is necessary to wait for the hardware device I/O to complete its work or release the resource , the program interface of the device driver layer can operate the hardware device to execute the program setting required by the working entity. As a result, the work request issued by the application layer is forced to prolong the execution time due to waiting for the I/O time of the hardware device, thereby reducing the work efficiency of the overall network system. the

It can be seen that the work management method of the above-mentioned existing network system obviously still has inconvenience and defects in method and use, and needs to be further improved urgently. In order to solve the above-mentioned problems, the relevant manufacturers have tried their best to find a solution, but no suitable design has been developed for a long time, and the general method has no suitable method to solve the above-mentioned problems. This is obviously related. The problem that the industry is eager to solve. Therefore, how to create a new network system work management and scheduling method is one of the current important research and development topics, and it has also become a goal that the industry needs to improve. the

In view of the above-mentioned defects in the existing network system work management method, the inventor actively researches and innovates based on years of rich practical experience and professional knowledge engaged in the design and manufacture of such products, and cooperates with the application of academic theories, in order to create a The work management and scheduling method of the new network system can improve the work management method of the general existing network system and make it more practical. Through continuous research, design, and after repeated trials and improvements, the present invention with practical value is finally created. the

Contents of the invention

The purpose of the present invention is to overcome the defects existing in the work management method of the existing known network system, and provide a new work management and scheduling method of the network system. The technical problem to be solved is to make it work in the network system , the scheduling and operation of the work entity is performed by an independently running work queue, so that the application layer does not need to wait for the response of the hardware device, so that the related work requirements can be continuously executed without interruption, which is very suitable for practical use. the

The purpose of the present invention and the solution to its technical problems are achieved by adopting the following technical solutions. According to the work management and scheduling method of the network system proposed by the present invention, it includes the following steps: using a scheduling program unit to receive a work entity and store the work entity and schedule an execution opportunity corresponding to the work entity, to construct a work queue that operates independently; use a work management unit to analyze a work request issued by an application layer to extract a work entity included in the work request; and determine whether the hardware device required by the work request is available to determine Whether to store the work entity requested by the work in the work queue. the

The purpose of the present invention and its technical problems can also be further realized by adopting the following technical measures. the

In the aforementioned network system job management and scheduling method, in the step of judging whether the required hardware device for the job is available, if the judging result is no, respond to the failure information of the application layer, and if the judging result is yes, store The work entity requested by the work is sent to the work queue, and the work queue is requested to execute the work entity, and the application layer is responded with a completion message. the

In the aforementioned network system work management and scheduling method, the step of constructing a work queue that operates independently includes the following steps: using the scheduling program unit to analyze all objects in the network system; using the scheduling program unit to calculate the The total value of the work entity of these objects; divide a storage space according to the total value; use the scheduling program unit to receive the work entity; and store the work entity in the storage space and schedule the execution corresponding to the work entity opportunity. the

The aforementioned work management and scheduling method of the network system further includes a step of sequentially encoding the work entities of the objects. the

In the work management and scheduling method of the aforementioned network system, the step of sequentially encoding the work entities of the objects includes the following steps: obtaining the code of the work entity required by the work; searching for the work entity of the work queue Work entity; and judge whether to have this work entity that accords with this code, if not, store this corresponding work entity of this work requirement in this work queue, if, update this work entity of this work queue. the

In the work management and scheduling method of the aforementioned network system, the step of updating the work entity of the work queue includes the following steps: detecting whether the setting parameters of the two work entities with the same code are the same, and if not, The work entity of the work request replaces the work entity of the work queue, and if so, deletes the work entity of the work request. the

The aforementioned work management and scheduling method of the network system further includes: calculating data dependencies of all work entities of the work queue; and adjusting execution timings of all work entities of the work queue according to the data dependencies. the

In the aforementioned work management and scheduling method of the network system, the step of using a work management unit to analyze a work request sent by an application layer includes the following steps: receiving the work request sent by the application layer; and analyzing the work request sent by the application layer. Whether the programming statement is correct, if not, respond to a failure message of the application layer, if yes, retrieve the work entity required by the work request. the

In the aforementioned work management and scheduling method of the network system, the step of judging whether the hardware device required by the work requirement is available includes the following steps: obtaining the parameter specification of the hardware device required by the work requirement; Set whether the parameter conforms to the parameter specification, if not, respond to a failure message of the application layer, and if so, store the work entity required by the work in the work queue. the

In the aforementioned work management and scheduling method of the network system, the step of judging whether the hardware device required by the work request is available includes the following steps: obtaining the number of all work entities required by the work request and the allowable scheduling of the work queue and compare whether the total number of work entities required is higher than the allowable schedule number, if yes, respond to a failure message of the application layer, if not, store the work entities required by the work to the work queue. the

In the above-mentioned work management and scheduling method of the network system, the step of judging whether the hardware device required by the work request is available includes the following steps: executing a request to the hardware device, and if the hardware device responds that the request cannot be executed, return In response to a failure message at the application layer, if the hardware device responds that the request is successfully completed, store the work entity required by the work in the work queue. the

In the aforementioned work management and scheduling method of the network system, the step of storing the work entity of the work request in the work queue includes the following steps: obtaining the work entity of the work request; detecting whether the work queue has the same If not, store the work entity of the work request in the work queue, if yes, update the work entity of the work request to the work entity of the work queue. the

The aforementioned work management and scheduling method of the network system, wherein the operation method of the work queue includes the following steps: detecting whether an execution request is obtained, if so, executing a work entity with the highest execution opportunity, and starting the execution opportunity The hardware device required by the highest priority work entity, if not, return whether the detection has obtained an execution request step; and detect whether a work entity has not been completed, if not, return whether the detection has obtained an execution request step, if , returns the work entity step with the highest execution timing. the

Compared with the prior art, the present invention has obvious advantages and beneficial effects. As can be seen from the above, in order to achieve the above object, the present invention provides a method for job management and scheduling of a network system. A scheduling program unit is used to receive a work entity, store the work entity and schedule a corresponding execution opportunity, so as to construct a work queue that runs independently. Utilize a work management unit to analyze a work request sent by an application layer to extract a corresponding work entity contained in the work request, and judge whether the hardware device required by the work request is available, so as to decide whether to respond a completion message to the application layer , store the corresponding work entities required by the work in the work queue, and request the work queue to execute the work entities in the schedule. the

In the work management and scheduling method of the network system disclosed in the present invention, when the work queue obtains the execution request of the work management unit, it sequentially fetches and executes the scheduled work entities until all the work entities are completed. the

In the work management and scheduling method of the network system disclosed in the present invention, the work queue can execute work entities in various ways. Method 1: Execute work entities in first-in-first-out order; Method 2: Each work entity is configured with a permission value, and the level of permission value is used as the basis for scheduling the execution timing of the work entity, and the permission value can be based on the data of each work entity ( That is, data, which are referred to as data in this article) dependencies are configured. the

In the work management and scheduling method of the network system disclosed in the present invention, when the work management unit stores a new work entity in the work queue, if it detects that the work queue has the same work entity but the two setting parameters are different, the work queue is updated. The setting parameters of the work entities, and according to the current authority values and data dependencies of all work entities, adjust the execution timing of the work entities in the work queue. the

In the work management and scheduling method of the network system disclosed in the present invention, the network system has a plurality of different objects (Objects), each of which has a different program instruction, and each program instruction is used to control the hardware device of the network system. Such as sending and receiving data, analyzing data, specifying the connection port used for data sending and receiving (that is, port, referred to as port in this article), and performing logical operations between data, storing data and specifying the location of data storage, etc., these programs The command system is called the job entity (Job Entity). the

In the work management and scheduling method of the network system disclosed in the present invention, the reason why the work queue is called independent operation is that when the work queue receives the request of the work entity in the execution schedule, that is, in the continuous execution schedule work entities until all the work entities in the schedule are executed. Even if there are work entities corresponding to the work requirements to be stored in the work queue during the execution, and the work queue receives the request of the work entities in the execution schedule again, the work queue will execute the work entities sequentially according to the execution timing of each work entity. During the execution of the work entity, the work queue is not interfered by other components and programs, so the work queue is called independent operation. the

By virtue of the above technical solutions, the work management and scheduling method of the network system of the present invention has at least the following advantages and beneficial effects:

1. The application layer can obtain the response of the work request from the work management unit in a short period of time, avoiding that the work request is forced to prolong its execution time due to waiting for the response of the I/O of the hardware device. the

2. When executing work entities with the same set parameters, according to whether the set parameters, authority values or data dependencies required by the work entities are the same, to adjust the execution timing of the work entities, update the set parameters or merge the same work entities, Avoid the storage space of the work queue being occupied by the same work entity, and cannot be stored in the work entity required by other work to cause an overflow phenomenon (OverFlow), thereby causing errors in the operation of the entire network system. the

To sum up, the present invention provides a method for job management and scheduling of a network system. A job queue is constructed in advance, and a job management unit is used to process a job request from the application layer. When the work management unit determines that the hardware device required by the work request is available, it stores the corresponding work entity in the work queue, and outputs request completion information to respond to the application layer, and the work queue independently executes the stored work entity. In this way, the work management unit responds to the work request of the application layer in a short time, so that the application layer can perform the next work request without waiting for the hardware device to respond. The work queue can adjust the execution order of work entities or update the setting parameters according to data dependencies, authority values, and setting parameters, so as to quickly obtain the correct execution results of the work requirements and improve the work efficiency of the network system. The present invention has the above-mentioned advantages and practical value, and it has great improvement no matter in method or function, has significant progress in technology, and has produced easy-to-use and practical effects, and is more efficient than existing network systems. The management method has the outstanding effect of promotion, thus is more suitable for practical use, and it is a novel, progressive and practical new design. the

The above description is only an overview of the technical solution of the present invention. In order to better understand the technical means of the present invention, it can be implemented according to the contents of the description, and in order to make the above and other purposes, features and advantages of the present invention more obvious and understandable , the following preferred embodiments are specifically cited below, and are described in detail as follows in conjunction with the accompanying drawings. the

Description of drawings

FIG. 1 is a schematic diagram of an execution flow of a work management unit of a general network system. the

FIG. 2 is a schematic diagram of the system structure of a preferred embodiment of the work management and scheduling method of the network system of the present invention. the

FIG. 3 is a flow diagram of a preferred embodiment of the work management and scheduling method of the network system of the present invention. the

Fig. 4 is a schematic flowchart of a preferred embodiment of the working method of the present invention. the

FIG. 5 is a flow diagram of a preferred embodiment of storing work entities in a work queue according to the present invention. the

201: Application layer 202: Work management unit

203: Core layer 204: Device driver layer

205: Work queue 206: Hardware device

Detailed ways

In order to further explain the technical means and effects of the present invention to achieve the intended purpose of the invention, the specific implementation methods and methods of the work management and scheduling method of the network system proposed according to the present invention will be described below in conjunction with the accompanying drawings and preferred embodiments. , steps, features and effects thereof are described in detail below. the

The aforementioned and other technical contents, features and effects of the present invention will be clearly presented in the following detailed description of preferred embodiments with reference to the drawings. Through the description of the specific implementation mode, a more in-depth and specific understanding of the technical means and effects adopted by the present invention to achieve the intended purpose can be obtained. However, the accompanying drawings are only for reference and description, and are not used to explain the present invention. be restricted. the

Please also refer to FIG. 2 and FIG. 3 , which are a simplified system structure diagram and a schematic flow diagram of a preferred embodiment of the work management and scheduling method of the network system of the present invention, respectively. Its system structure includes an application layer 201 , a work management unit 202 , a core layer 203 and a device driver layer 204 . And its method flow includes:

A scheduling program unit is used to receive a work entity, store the work entity and schedule a corresponding execution opportunity, so as to construct a work queue for independent operation (step S309 ). In this step, the work queue 205 manages, receives and executes the received work entities through a scheduling program unit. This network system includes a number of objects (Object), each of which has program instructions to control different actions of hardware devices, such as sending and receiving data, analyzing data, specifying the connection port used for sending and receiving data, and carrying out the logic between data Computing, storing data and specifying data storage locations, etc., these program instruction systems are called job entities (Job Entity). the

First use the scheduling program unit to analyze all the objects of this network system, and each object contains multiple work entities. Then, the scheduling program unit calculates the total value of the work entities of all objects, and divides a storage space from the network system according to the total value. Finally, the scheduling program unit stores all the work entities and schedules the execution timing corresponding to each work entity, so as to form an independently running work queue. the

When constructing, the maximum scheduled number of the work queue 205 can be equal to the sum of its work entities, or to ensure that additional status occurs, the maximum scheduled number of the work queue 205 can be set higher than the sum of its work entities. Then, according to the order in which the object's work entities are stored in the hardware device, the work entities are sequentially encoded, and the encoding is also the storage order of the work entities in the work queue 205 . the

Assume that the network system has three objects: Object A, Object B, and Object C. Object A has 10 working entities, Object B has 20 working entities, and Object C has 50 working entities. The working entities of Object A are from the code 1 to code 10, the working entity of object B is from code 11 to code 30, and the working entity of object C is from code 31 to code 80. The maximum number of schedules of the work queue 205 is 80 or more data, and when the work queue 205 stores the work entities of object A, object B and object C, they are stored as the 1st to 10th and 11th respectively to the 30th, and the 31st to the 80th arrangement position, which is beneficial to the follow-up comparison operation. the

Therefore, the number of work entities that can be stored in the work queue 205 is matched with the number of work entities generated by the network system running a limit number of work requirements. the

However, when the work queue receives a request to execute the work entities in the schedule, it will continue to execute the work entities in the schedule until all the work entities in the schedule are executed. Even if there are work entities corresponding to the work requirements to be stored in the work queue during the execution, and the work queue receives the request of the work entities in the execution schedule again, the work queue will execute the work entities sequentially according to the execution timing of each work entity. During the execution of the work entity, the work queue is not interfered by other components and programs, so the work queue is called independent operation. the

A work management unit 202 is used to analyze a work request issued by an application layer 201 to extract a corresponding work entity included in the work request. In this step, first use the work management unit 202 to receive the work request from the application layer 201 (step S301). Next, the work management unit 202 calls the program interface of the core layer 203 to analyze whether the programming statement required by the work is correct (step S302 ). the

If the analysis result is incorrect, the core layer 203 will send the analysis failure result to the work management unit 202 for it to respond to the failure information of the application layer 201 (step S308), and then end the work requirement; if the analysis result is correct, the core layer 203 A corresponding work entity included in the work request is retrieved (step S303). the

The core layer 203 is to analyze the required call and use object according to the programming statement of the work requirement, and when it is judged that the called object or function is correct, the work entity contained in the object is analyzed. the

Determine whether the hardware device required by the work request is available (step S304 ), so as to determine whether to store the corresponding work entity of the work request in the work queue 205 . In this step, the device driver layer 204 is called by the core layer 203 to make its program interface cooperate with the management unit 202 to determine the current state of the hardware device 206 . the

If the determination result is no, the device driver layer 204 will inform the work management unit 202 that the hardware device 206 cannot be used for it to respond to the failure information of the application layer 201 (step S308), and end this work requirement; if it is determined to be yes, the device driver layer 204 Store the corresponding work entity required by the work to the work queue 205 (step S305), and request the work queue 205 to execute the corresponding work entity (step S306), and respond to the application layer 201 with a completion message through the work management unit 202 (step S307). the

There are at least three ways to determine the state of the hardware device 206:

Firstly, the work management unit 202 obtains the parameter specification of the hardware device 206 required by the work requirement from the device driver layer 204, and compares whether the setting parameters of the work requirement comply with the parameter specification. For example, the data connection port numbers (Port-Numbers) of the hardware device 206 include the first connection port (Port-1) to the 1000th connection port (Prot-1000). As long as the connection port number indicated by the job request is not within the range, the job management unit 202 will respond to the application layer 201 with a failure message. On the contrary, the work management unit 202 stores the work entity required by the work to the work queue 205 through the program interface of the device driver layer 204. the

Second, the work management unit 202 calculates the number of all work entities required by the work request, and obtains the allowable scheduling number of the work queue 205 from the device driver layer 204 . Then compare whether the required quantity of all work entities is higher than the allowable scheduled quantity. If the result is yes, it means that the work queue 205 can no longer add work entities corresponding to the work request, and the work management unit 202 responds with a failure message of the application layer. On the contrary, the work management unit 202 stores the work entities required by the work into the work queue 205 through the program interface of the device driver layer 204 . the

Third, the work management unit 202 first requests the hardware device 206 to execute the required work entity, and when the hardware device 206 responds that the operation is successfully completed, it means that the hardware device 206 can accept the request of the work entity, and the work management unit 202 promptly passes the device driver layer The program interface of 204 stores the work entity required by the work to the work queue 205 . If the hardware device 206 responds that the operation cannot be performed, it means that the hardware device 206 cannot meet the work requirement, and the work management unit 202 responds to the application layer 201 with a failure message. the

The work management unit 202 can store work entities in the work queue 205 in at least two ways, which are described as follows:

Firstly, the work management unit 202 stores the work entities in the work queue 205 according to the first-in-first-out rule. Regardless of the importance of the work request, only the request sequence of the work request is used to store its corresponding work entity. the

Second, the work management unit 202 configures each work entity with a corresponding authority value in a one-to-one manner, and then stores the work entity in the work queue according to the authority level of the authority value, and the authority value can be based on the data dependence between the work entities properties to configure. the

For example, work entity a depends on work entity b, and work entity b depends on work entity c, so the order of storing work entity a in the work queue is: create work entity c, create work entity b, create work entity a, authority The sequence from high to low is working entity c, working entity b, and working entity a. the

Conversely, the removal of work entity a is performed in order of authority from low to high, and the sequence is: remove work entity a, remove work entity b, and remove work entity c. the

When the storage of the work entity is completed, the work management unit 202 requests the work queue 205 to execute the stored work entity, and at the same time outputs completion information to the application layer 201 to complete the work request and execute the next work request. The work queue 205 obtains an execution request to execute the stored work entity (step S310 ). the

Please refer to FIG. 4 , which is a schematic flowchart of a preferred embodiment of the working method of the present invention. Its methods include:

Detecting whether an execution request is obtained (step S401 ), the device driver layer 204 sends the execution request to the work queue after adding the work entity to the work queue 205 . Therefore, when the work queue obtains the execution request, there must be a work entity stored in it. the

If the detection result is no, return to the step of detecting whether an execution request is obtained (step S401); if the detection result is yes, then execute a work entity with the highest execution opportunity (step S402), and then start the execution opportunity with the highest priority The hardware device required by the working entity (step S403). the

Yet, the rule that work queue 205 executes work entity basis has two:

First, all work entities are executed on a first-in, first-out basis. the

Second, according to the aforementioned authority values, all work entities are executed in order of their authority levels, and the authority values can be configured according to the data dependencies of the work entities. the

Then, the work queue 205 detects whether a work entity has not been completed (step S404), if not, then returns to the step of detecting whether an execution request is obtained (step S401); if so, then executes a work entity with the highest execution opportunity ( step S402). the

Please refer to FIG. 5 , which is a schematic flowchart of a preferred embodiment of storing work entities in a work queue according to the present invention. It contains the following steps:

The work management unit 202 first obtains the corresponding work entity of the work request (step S501 ), and detects whether there is the same work entity in the work queue 205 (step S502 ). If not, store the corresponding work entity of the work request in the work queue 205 (step S503); if yes, update the corresponding work entity of the work request to the work entity of the work queue 205 (step S504). the

If the work entity has been coded before, the code of the work entity required by the job can be obtained first, and the work entity in the work queue 205 can be searched by this code to determine whether there is a work entity matching the code stored in the work queue 205 . the

If the result is negative, it means that there is no identical work entity in the work queue 205 , and the work entity required by this work can be stored in the work queue 205 . If the judgment result is yes, update the working entity with the same code. the

As mentioned above, if the work queue 205 has stored the work entities of the object B, that is, the 11th to 30th work entities. When the executed work request needs to call the execution object A, the work queue 205 does not store the work entities with codes 1 to 10, so the work management unit 202 adds these work entities to the work queue and stores them in the 1 to 10 codes. 10 order. the

When the executed work requires calling the execution object B, the work management unit 202 compares that the 11th to 30th work entities have been stored in the work queue 205 , and updates these work entities. the

Then, when updating the work entity of the work queue 205, the work management unit 202 detects whether the setting parameters of the two identical work entities are the same, if the detection result is no, replace the work entity of the work queue 205 with the work entity required by the work; , then delete the work entity required by the work, or merge two identical work entities. Then, the work management unit 202 calculates the data dependencies of all the work entities in the work queue 205, and adjusts the storage order of all the work entities according to the data dependencies. the

The work entity update process is used to prevent the work queue 205 from continuously executing the work entities required by the same work, so that the work entities required by other tasks cannot be stored therein, and thus cause operational errors in the network system. the

The above description is only a preferred embodiment of the present invention, and does not limit the present invention in any form. Although the present invention has been disclosed as above with preferred embodiments, it is not intended to limit the present invention. Anyone familiar with this field Those skilled in the art, without departing from the scope of the technical solution of the present invention, may use the technical content disclosed above to make some changes or modify them into equivalent embodiments with equivalent changes, but as long as they do not depart from the technical solution of the present invention, the Technical Essence Any simple modifications, equivalent changes and modifications made to the above embodiments still fall within the scope of the technical solution of the present invention. the

Claims (13)

1. A work management and scheduling method for a network system, characterized in that it comprises the following steps: Utilizing a scheduling program unit to receive a work entity, store the work entity and schedule an execution opportunity corresponding to the work entity, so as to construct a work queue that operates independently; Using a work management unit to analyze a work request issued by an application layer through a program interface of a core layer, so as to extract the work entity included in the work request; and A device driver layer assists the work management unit in judging whether the hardware device required by the work request is available, so as to decide whether to store the work entity of the work request in the work queue. 2. The job management and scheduling method of the network system according to claim 1, wherein in the step of judging whether the hardware device required by the job requirement is available, if the judging result is no, the application layer- For failure information, if the judging result is yes, store the work entity requested by the work in the work queue, request the work queue to execute the work entity, and respond with a completion message of the application layer. 3. The work management and scheduling method of the network system according to claim 1, wherein said step of constructing a work queue for independent operation comprises the following steps: Analyze all objects of the network system by using the scheduling program unit; Use the scheduling program unit to calculate the total value of the work entities of these objects; dividing a storage space according to the sum value; receiving the work entity using the scheduling program unit; and storing the working entity in the storage space and scheduling the execution opportunity corresponding to the working entity. 4. The work management and scheduling method of the network system according to claim 3, wherein the step of storing the work entity in the storage space comprises: Encode the working entities of these objects in sequence; the code of the work entity that obtained the work request; search for the work entity of the work queue; and Judging whether there is the work entity matching the code, if not, storing the corresponding work entity of the work request in the work queue, if yes, updating the work entity of the work queue. 5. The work management and scheduling method of the network system according to claim 4, wherein said step of sequentially encoding the work entities of the objects comprises the following steps: The working entities of the objects are encoded according to the order in which the working entities of the objects are stored in the storage space. 6. The work management and scheduling method of the network system according to claim 4, wherein the step of updating the work entity of the work queue comprises the following steps: Detect whether the setting parameters of the work entities with the same code are the same, if not, replace the work entity of the work queue with the work entity required by the job, and delete the work entity of the work request if yes. 7. The work management and scheduling method of the network system according to claim 6, further comprising: Compute the data dependencies of all work entities of the work queue; and The execution timings of all work entities of the work queue are adjusted according to the data dependency. 8. The job management and scheduling method of the network system according to claim 1, wherein said step of using a job management unit to analyze a job request issued by an application layer comprises the following steps: receiving the job request from the application layer; and Analyzing whether the programming statement of the job request is correct, if not, responding to a failure message of the application layer, if yes, extracting the job entity required by the job request. 9. The work management and scheduling method of the network system according to claim 1, wherein said step of judging whether the hardware device required by the work request is available comprises the following steps: obtaining parameter specifications of hardware devices required for the job; and Check whether the setting parameters of the work request conform to the parameter specification, if not, respond to a failure message of the application layer, and if yes, store the work entity of the work request in the work queue. 10. The work management and scheduling method of the network system according to claim 1, wherein said step of judging whether the hardware device required by the work request is available comprises the following steps: The total number of work entities required to obtain the work request and the allowable scheduling quantity of the work queue; and Check whether the required total number of work entities is higher than the allowable schedule quantity, if yes, respond to the application layer with a failure message, if not, store the work entities required by the work into the work queue. 11. The work management and scheduling method of the network system according to claim 1, wherein said step of judging whether the hardware device required by the work request is available comprises the following steps: Execute a request to the hardware device. If the hardware device responds that the request cannot be executed, it responds with a failure message of the application layer. If the hardware device responds that the request is successfully completed, store the work entity required by the work to the work queue. 12. The work management and scheduling method of the network system according to claim 1, wherein said step of storing the work entity of the work request in the work queue comprises the following steps: the working entity that obtained the job request; Detecting whether the same work entity exists in the work queue, if not, storing the work entity of the work request in the work queue, if yes, updating the work entity of the work request to the work entity of the work queue. 13. The job management and scheduling method of the network system according to claim 1, wherein the operation method of the job queue includes the following steps: Detect whether an execution request is obtained, if yes, execute a work entity with the highest execution opportunity, and start the hardware device required by the work entity with the highest execution opportunity, if not, return the step of detecting whether an execution request has been obtained; as well as Detect whether a work entity has not been completed, if not, return whether the detection has obtained an execution request step, and if so, return the work entity step with the highest execution opportunity.

Images