WO2024184941A1

WO2024184941A1 - Function transmission device, function execution device, function transmission method, function execution method, function transmission program, and function execution program

Info

Publication number: WO2024184941A1
Application number: PCT/JP2023/007976
Authority: WO
Inventors: 貴之上野; 武尚水口; 整山本; 竜也山田; 圭祐堀井
Original assignee: 三菱電機株式会社
Priority date: 2023-03-03
Filing date: 2023-03-03
Publication date: 2024-09-12

Abstract

A function registration unit (111) generates instruction information for instructing a function execution device (200), which executes functions, to, from among a plurality of functions to be executed by the function execution device (200), finish the execution of an early completion function earlier than other functions, the early completion function being a function for which the execution must be finished earlier than the other functions. In addition, the function registration unit (111) transmits the early completion function and the instruction information to the function execution device (200).

Description

Function transmission device, function execution device, function transmission method, function execution method, function transmission program, and function execution program

This disclosure relates to the execution of functions.

A cloud computing service called FaaS (Function as a Service) is becoming popular. With FaaS, it is possible to register event-driven functions defined by the user to a function execution device. In addition, with FaaS, an execution environment according to the function is provided to the function execution device when the function is registered, so that the user can easily execute the function.

As a technique related to the present disclosure, for example, there is a technique disclosed in Patent Document 1.
Japanese Patent Laid-Open No. 2003-233693 discloses that arguments received from a function execution device are provided to a function of a function registration request device, and the execution result of the function is provided to the function execution device.

Patent No. 6997096

FIG. 20 shows the relationship between the execution request queue and the execution thread of a function in the prior art.
In the conventional technique, an execution thread takes an execution request from an execution request queue that has a one-to-one correspondence with the execution thread, and calls a function. In the conventional technique, all execution threads operate with the same priority.
For this reason, the conventional technology has a problem that, as shown in the timing chart of function processing in FIG. 21, the execution of a function that needs to be completed quickly is made to wait and/or the execution of the function is interrupted due to the execution of another function.

The primary objective of this disclosure is to solve these problems. More specifically, the objective of this disclosure is to quickly complete the execution of a function that needs to be completed quickly.

The function transmission device according to the present disclosure comprises:
an information generating unit that generates instruction information for instructing a function execution device to complete the execution of an early completion function, which is a function that needs to be completed earlier than other functions among a plurality of functions to be executed by the function execution device, earlier than the other functions;
A transmitting unit transmits the early completing function and the instruction information to the function execution unit.

According to the present disclosure, it is possible to complete the execution of a function that needs to be completed quickly.

2 is a diagram showing an example of the hardware configuration of a function registration request device and a function execution device according to the first embodiment; 2 is a diagram showing an example of the functional configuration of a function registration request device and a function execution device according to the first embodiment; FIG. 4 is a diagram showing an example of registration data according to the first embodiment; FIG. 4 is a diagram showing an example of an event function correspondence table in the first embodiment. FIG. 11 is a diagram showing an example of an operation sequence in an execution preparation phase according to the first embodiment. FIG. 11 is a diagram showing an example of an operation sequence in an event execution phase according to the first embodiment. 5 is a timing chart of function processing according to the first embodiment. FIG. 11 is a diagram showing an example of registration data according to the second embodiment. FIG. 13 is a diagram showing an example of an event function correspondence table in the second embodiment. FIG. 11 is a diagram showing an example of an operation sequence in an execution preparation phase according to the second embodiment. FIG. 11 is a diagram showing an example of an operation sequence in an event execution phase according to the second embodiment. 5 is a timing chart of function processing according to the first embodiment. FIG. 13 is a diagram showing an example of the functional configuration of a function registration request device and a function execution device according to a third embodiment. FIG. 13 is a diagram showing an example of registration data according to the third embodiment. FIG. 13 is a diagram showing an example of an event function correspondence table in the third embodiment. FIG. 13 is a diagram showing an example of an operation sequence in an execution preparation phase according to the third embodiment. FIG. 13 is a diagram showing an example of an operation sequence in an event execution phase according to the third embodiment. FIG. 13 is a diagram showing an example of registration data according to the fourth embodiment. FIG. 13 is a diagram showing an example of an operation sequence in an execution preparation phase according to the fourth embodiment. FIG. 1 is a diagram showing the relationship between a conventional execution request queue and execution threads. 11 is a timing chart of conventional function processing.

The following describes the embodiments with reference to the drawings. In the following description of the embodiments and the drawings, the same reference numerals indicate the same or corresponding parts.

Embodiment 1.
***Configuration Description***
FIG. 1 shows an example of the hardware configuration of a function registration request device 100 and a function execution device 200 according to the present embodiment.
The function registration request device 100 and the function execution device 200 are connected via a network 300 .
The function execution device 200 executes a function. A plurality of function execution devices 200 may exist.
The function registration request device 100 transmits a function to be executed by the function execution device 200 to the function execution device 200 via the network 300 .

The function registration requesting device 100 corresponds to a function transmission device. The operation procedure of the function registration requesting device 100 corresponds to a function transmission method. The program for realizing the operation of the function registration requesting device 100 corresponds to a function transmission program.
The operation procedure of the function execution device 200 corresponds to a function execution method, and the program that realizes the operation of the function execution device 200 corresponds to a function execution program.

The function registration request device 100 is a computer.
The function registration request device 100 includes a CPU (Central Processing Unit) 101, a memory 102, a communication device 103, and a storage device 104. The function registration request device 100 may include a plurality of CPUs 101.
The communication device 103 of the function registration requesting device 100 transmits a function to the communication device 203 of the function execution device 200 via the network 300 .

The function execution device 200 is also a computer.
The function execution device 200 also includes a CPU 201, a memory 202, a communication device 203, and a storage 204. The function execution device 200 may include a plurality of CPUs 201.
The communication device 203 of the function execution device 200 receives a function from the communication device 103 of the function registration request device 100 via the network 300 .

FIG. 2 shows an example of the functional configuration of a function registration request device 100 and a function execution device 200 according to this embodiment.

An operating system 110 runs on the function registration request device 100 .
A function registration unit 111 operates on the operating system 110. The function registration unit 111 is realized, for example, by a program. More specifically, the CPU 101 executes a program that realizes the function of the function registration unit 111, thereby performing the operation of the function registration unit 111, which will be described later.

The function registration unit 111 acquires a function registration request from a user. When the function registration unit 111 acquires the function registration request, it generates instruction information. The instruction information is information for instructing that a function that needs to be completed earlier than other functions among a plurality of functions (hereinafter, referred to as an early completion function) is to be completed earlier than the other functions.
Then, the function registration unit 111 transmits the registration data 105 including a plurality of functions including the early completion function and instruction information to the function execution device 200 .
The function registration unit 111 corresponds to an information generation unit and a transmission unit, and the process performed by the function registration unit 111 corresponds to an information generation process and a transmission process.

The registration data 105 is data to be registered in the function execution device 200 by the function registration request device 100 .
The registration data 105 is stored in the storage 104 .
It is assumed that the registration data 105 exists for each function to be transmitted to the function execution device 200. In this embodiment, since it is assumed that a plurality of functions are transmitted from the function registration request device 100 to the function execution device 200, it is assumed that a plurality of registration data 105 exists.

FIG. 3 shows an example of the registration data 105 .
The registration data 105 includes functions, execution setting information, and priority information.
The function is a function to be executed by the function execution unit 200 .
The execution setting information is setting information related to the execution of a function. The execution setting information includes event information. The event information defines an event that will be a trigger for the execution of the function.
The priority information is instruction information in this embodiment. That is, in this embodiment, the priority information is used as instruction information. The priority information defines the order of priority when the functions are executed. In the registration data 105 of the early completion function, the priority information indicates a higher priority for the early completion function than other functions.

An operating system 210 runs on the function execution device 200 .
Furthermore, a function management unit 211, a receiving unit 212, a function execution environment 214, and a function execution unit 217 operate on the operating system 210. The function management unit 211, the receiving unit 212, the function execution environment 214, and the function execution unit 217 are realized, for example, by a program. More specifically, the CPU 201 executes a program that realizes the functions of the function management unit 211, the receiving unit 212, the function execution environment 214, and the function execution unit 217, thereby causing the function management unit 211, the receiving unit 212, the function execution environment 214, and the function execution unit 217 to operate as described below.

The function management unit 211 stores the registration data 105 received by the receiving unit 212 in the storage 204 and prepares for function execution.

The receiving unit 212 receives the registration data 105 from the function registration requesting device 100. Then, the receiving unit 212 outputs the received registration data 105 to the function managing unit 211.
The receiving unit 212 also includes an execution request queue 213 corresponding to each function. In this embodiment, the receiving unit 212 includes a plurality of execution request queues 213. An execution request queue 213 exists for each function 216.
Furthermore, the receiver 212 receives an event notification notifying the occurrence of an event when the event occurs. The event notified in the event notification is an event that triggers the execution of a function. Upon receiving the event notification, the receiver 212 submits an execution request to an execution request queue 213 corresponding to the function 216 to be executed by a function execution unit 217.
The process performed by the receiving unit 212 corresponds to a receiving process.

When an execution request is submitted to the execution request queue 213 by the receiving unit 212, the function executing unit 217 generates an execution thread 215 in the function execution environment 214. Furthermore, the function executing unit 217 calls a corresponding function 216 and executes the function 216. The function 216 is a function transmitted from the function registration requesting device 100 as a part of the registration data 105. The function executing unit 217 calls the function included in the registration data 105 as the function 216.
If the function 216 is an early completion function, the function execution unit 217 executes the function 216 (early completion function) with priority in accordance with the priority information so that the function 216 is completed earlier than other functions.
The process performed by the function execution unit 217 corresponds to a function execution process.
Although the function execution unit 217 is independent of the operating system 210 in FIG. 2, the function execution unit 217 may be a part of the operating system 210 .

It is assumed that there are multiple function execution environments 214. In this embodiment, a function execution environment 214 exists for each function 216.

The storage 204 stores the registration data 105 sent from the function registration request device 100 and the event function correspondence table 205.

FIG. 4 shows an example of the event function correspondence table 205 .
In the event-function correspondence table 205, the event column indicates an event that triggers the execution of the function described in the function name column. The event indicated in the event column is the event indicated in the event information of the registration data 105.
The function name column indicates a function to be executed when the event indicated in the event column occurs. The function indicated in the function column is a function included in the registration data 105.
The priority column indicates the priority of the function written in the function name column. The priority indicated in the priority column is the priority indicated in the priority information of the registration data 105. If the function indicated in the function name column is an early completion function, the priority column indicates a higher priority than other functions.

*** Operation Description ***
Next, an example of the operation of the function registration request device 100 and the function execution device 200 according to this embodiment will be described.
In the following, the operation sequences of the function registration request device 100 and the function execution device 200 will be explained, being divided into an execution preparation phase and an event execution phase.
The execution preparation phase is a phase for putting the function execution device 200 into a state of waiting to receive an event. The event execution phase is a phase in which the function execution device 200 executes a function when an event occurs.

Figure 5 shows the operation sequence during the execution preparation phase.

The function registration unit 111 receives a function registration request from a user (step S400). The function registration request indicates elements (functions, events, and priorities) to be included in the registration data 105.
When the function registration unit 111 receives a function registration request, it generates registration data 105 according to the function registration request, and transmits the registration data 105 and the function execution environment 214 corresponding to the function to the function execution device 200 (step S401).

In the function execution device 200, the receiving unit 212 receives the registration data 105 and the function execution environment 214, and the function management unit 211 stores the registration data 105 and the function execution environment 214 in the storage 204 (step S402). Note that Fig. 2 shows a state in which the function execution environment 214 is activated. For this reason, the function execution environment 214 is not described in the storage 204.
Furthermore, the function management unit 211 generates the event function correspondence table 205 from the registration data 105, and registers the event function correspondence table 205 in the storage 204 (step S403).
Furthermore, the function management unit 211 starts the function execution environment 214 (step S404), and sets a priority for the execution thread 215 based on the event-function correspondence table 205 (step S405).

FIG. 6 shows the sequence of operations in the event execution phase.
When the event execution phase begins, the execution preparation phase is complete.

When an event occurs, the receiving unit 212 receives an event notification (step S500).
The receiving unit 212 searches the “Event” column of the event function correspondence table 205 for the event notified in the event notification, identifies a function corresponding to the notified event, and submits an execution request to the execution request queue 213 of the identified function (step S501).
The function execution section 217 performs a process of retrieving an execution request from the execution request queue 213 (step S502).Then, the function execution section 217 determines whether or not the execution request has been retrieved from the execution request queue 213 (step S503).
When an execution request is taken out of the execution request queue 213, the function execution section 217 generates an execution thread 215 in the function execution environment 214, calls the corresponding function 216, and executes the function 216 (step S504). After that, the process returns to step S502.
If the execution request queue 213 is empty and the function execution section 217 cannot extract an execution request, the process returns to step S502.

In step S504, the function execution unit 217 processes the execution threads 215 with higher priority among the multiple execution threads 215.
That is, the function execution unit 217 executes functions with higher priority, i.e., early completion functions, with priority according to the priority information. As a result, the execution of the early completion functions is completed earlier than the execution of other functions.

FIG. 7 shows a timing chart of the function processing in this embodiment.
The function execution unit 217 performs task scheduling based on the priority set for the execution thread of each function.
7, execution thread 3, which is an execution thread of the early completion function, is executed prior to

execution threads

1 and 2, which are execution threads of other functions. Therefore, the execution of the early completion function is completed early. In other words, the execution of the early completion function can be started without waiting for the completion of the execution of the other functions. In addition, during the execution of the early completion function, an interruption due to the other functions does not occur.

***Description of Effects of the Embodiment***
In this way, according to this embodiment, it is possible to quickly complete the execution of a function that needs to be quickly completed.

Embodiment 2.
In the first embodiment, an example in which priority information is used as instruction information has been described. That is, in the first embodiment, a priority is set for an execution thread of each function, so that the execution of an early completing function is completed early.
On the other hand, the same effect can be obtained by using information other than priority information as the instruction information. In this embodiment, an example will be described in which CPU core allocation information is used as the instruction information instead of priority information.
In this embodiment, differences from the first embodiment will be mainly described.
It should be noted that matters not explained below are the same as those in the first embodiment.

***Configuration Description***
In this embodiment, the hardware configuration example (FIG. 1) and the functional configuration example (FIG. 2) are the same as those in embodiment 1. However, in this embodiment, it is assumed that the CPU 201 of the function execution device 200 has multiple CPU cores.

In this embodiment, the registration data 105b shown in FIG. 8 is used.
The registration data 105b includes functions, execution setting information, and CPU core allocation information. The functions and execution setting information are the same as those shown in Fig. 3, so a description thereof will be omitted.
The CPU core allocation information defines the number of a CPU core to which the execution of a function is assigned. The function registration unit 111 can instruct, in the CPU core allocation information, to assign a specific CPU core out of the multiple CPU cores of the function execution device 200 to the early completion function.

In this embodiment, the event function correspondence table 205b shown in FIG. 9 is used.
The event-function correspondence table 205b has columns for event, function name, and assigned CPU core. The event and function name columns are the same as those shown in Fig. 4, and therefore a description thereof will be omitted.
The assigned CPU core column indicates the number of a CPU core assigned to execute the function indicated in the function column. The assigned CPU core number indicated in the assigned CPU core column is the number of a CPU core indicated in the CPU core allocation information of the registration data 105b.

*** Operation Description ***
Next, an example of the operation of the function registration request device 100 and the function execution device 200 according to this embodiment will be described.
In this embodiment as well, the operation sequences of the function registration request device 100 and the function execution device 200 will be explained by dividing them into an execution preparation phase and an event execution phase.

Figure 10 shows the operation sequence in the execution preparation phase.

The function registration unit 111 receives a function registration request from a user (step S400). The function registration request indicates elements (functions, events, and CPU cores) to be included in the registration data 105b.
When the function registration unit 111 receives a function registration request, it generates registration data 105b according to the function registration request, and transmits the registration data 105b and the function execution environment 214 corresponding to the function to the function execution device 200 (step S401).

In the function execution device 200, the receiving unit 212 receives the registration data 105b and the function execution environment 214, and the function management unit 211 stores the registration data 105b and the function execution environment 214 in the storage 204 (step S402).
Furthermore, the function management unit 211 generates an event function correspondence table 205b from the registration data 105b, and registers the event function correspondence table 205b in the storage 204 (step S406).
Furthermore, the function management unit 211 starts the function execution environment 214 (step S404), and sets a CPU core to be assigned to the execution thread 215 based on the event-function correspondence table 205b (step S407).

FIG. 11 shows the operation sequence in the event execution phase.
When the event execution phase begins, the execution preparation phase is complete.

When an event occurs, the receiving unit 212 receives an event notification (step S500).
The receiving unit 212 searches the “Event” column of the event function correspondence table 205b for the event notified in the event notification, identifies a function corresponding to the notified event, and submits an execution request to the execution request queue 213 of the identified function (step S501).
The function execution section 217 performs a process of retrieving an execution request from the execution request queue 213 (step S502).Then, the function execution section 217 determines whether or not the execution request has been retrieved from the execution request queue 213 (step S503).
When an execution request is taken out of the execution request queue 213, the function execution section 217 generates an execution thread 215 in the function execution environment 214, calls the corresponding function 216, and executes the function 216 (step S504). After that, the process returns to step S502.
If the execution request queue 213 is empty and the function execution section 217 cannot extract an execution request, the process returns to step S502.

In step S<b>504 , the function execution unit 217 processes each execution thread 215 using a CPU core assigned to that execution thread 215 .
In other words, the function execution unit 217 assigns a specific CPU core to the early completion function in accordance with the CPU core allocation information, and executes the early completion function preferentially on the assigned CPU core. As a result, the execution of the early completion function is completed earlier than the execution of other functions.

FIG. 12 shows a timing chart of the function processing in this embodiment.
As shown in FIG. 12, the function execution unit 217 performs task scheduling based on the assigned CPU cores set for the execution threads of each function.
12, execution thread 3, which is an execution thread of the early completion function, is executed by CPU core 2. On the other hand, execution thread 1 and execution thread 2, which are execution threads of other functions, are executed by CPU core 1.
In this manner, in this embodiment, the early completion function is executed by a CPU core separate from other functions, so that the execution of the early completion function is completed early. In other words, the execution of the early completion function can be started without waiting for the execution of other functions to be completed. In addition, during the execution of the early completion function, an interruption due to other functions does not occur.

***Description of Effects of the Embodiment***
In this manner, according to this embodiment as well, it is possible to quickly complete the execution of a function that needs to be quickly completed.

Embodiment 3.
In the first embodiment, an example in which priority information is used as instruction information has been described. That is, in the first embodiment, a priority is set for an execution thread of each function, so that the execution of an early completing function is completed early.
When a large number of functions are registered in the function execution device 200, a large number of threads are generated. As a result, overhead due to thread switching may increase. Also, resources such as memory may become insufficient.
In this embodiment, an example will be described in which the number of threads is reduced by grouping functions.
More specifically, the function registration requesting device 100 groups a plurality of functions of the same priority. Then, an example will be described in which the function registration requesting device 100 notifies the function execution device 200 of the plurality of functions grouped in group ID (Identifier) information, which is instruction information in this embodiment, and instructs the function execution device 200 to execute the plurality of functions of the same group consecutively.
In this embodiment, differences from the first embodiment will be mainly described.
It should be noted that matters not explained below are the same as those in the first embodiment.

***Configuration Description***
In this embodiment, the hardware configuration example (FIG. 1) is the same as that in the first embodiment.
FIG. 13 shows an example of the functional configuration of the function registration request device 100 and the function execution device 200 according to this embodiment.
13, compared to Fig. 2, registration data 105c is stored in the storage 104. Furthermore, a plurality of functions 216 share a function execution environment 214 and an execution thread 215. A plurality of functions 216 that share a function execution environment 214 and an execution thread 215 belong to the same group. In other words, in this embodiment, a function execution environment 214 and an execution thread 215 exist for each group.
In this embodiment, it is assumed that an execution request queue 213 is provided for each group of functions 216 .

FIG. 14 shows an example of the registration data 105c.
The registration data 105c includes a function, execution setting information, priority information, and group ID information. The function, execution setting information, and priority information are the same as those shown in Fig. 3, so a description thereof will be omitted.
The group ID information indicates the group ID of the group to which the function belongs. Note that only functions that share a common trigger event and have the same priority belong to one group. Multiple functions whose group ID information indicates the same group ID belong to the same group.
Note that for a function that does not belong to any group, that is, for a function for which there is no other function with the same priority level that shares a common event, a null value is indicated in the group ID information.

In this embodiment, the function registration unit 111 classifies, for example, multiple early completion functions that have a common trigger event and the same priority into the same group. Then, the function registration unit 111 includes the same group ID information in the registration data 105c of each of the multiple early completion functions classified into the same group. In this way, the function registration unit 111 can instruct the function execution device 200 to execute multiple early completion functions in succession.

FIG. 15 shows an example of the event function correspondence table 205c.
The event-function correspondence table 205c has columns for event, function name, priority, and group ID. The columns for event, function name, and priority are the same as those shown in Fig. 4, and therefore a description thereof will be omitted.
The group ID column indicates the group ID of the group to which the function indicated in the function column belongs. The group ID indicated in the group ID column is the group ID indicated in the group ID information of the registration data 105c. In the event function correspondence table 205c, a null value is set in the group ID column for a function indicated in the group ID information of the registration data 105c with a null value.

*** Operation Description ***
Next, an example of the operation of the function registration request device 100 and the function execution device 200 according to this embodiment will be described.

Figure 16 shows the operation sequence in the execution preparation phase.

The function registration unit 111 receives a function registration request from a user (step S400). The function registration request indicates elements (function, event, priority, group ID) to be included in the registration data 105c.
When the function registration unit 111 acquires the function registration request, it generates registration data 105c according to the function registration request, and transmits the registration data 105c and the function execution environment 214 to the function execution device 200 (step S408). As described above, the same group ID is indicated in the group ID information of the registration data 105c for a plurality of functions that have a common trigger event and are set with the same priority.

In the function execution device 200, the receiving unit 212 receives the registration data 105c and the function execution environment 214, and the function management unit 211 stores the registration data 105c and the function execution environment 214 in the storage 204 (step S409).
Furthermore, the function management unit 211 generates an event function correspondence table 205c from the registration data 105c, and registers the event function correspondence table 205c in the storage 204 (step S410).
Furthermore, the function management unit 211 starts the function execution environment 214 for each group (step S411), and sets a priority for each execution thread 215 based on the event-function correspondence table 205c (step S412).

FIG. 17 shows the operation sequence in the event execution phase.
When the event execution phase begins, the execution preparation phase is complete.

When an event occurs, the receiving unit 212 receives an event notification (step S500).
The receiving unit 212 searches the “Event” column of the event function correspondence table 205c for the event notified in the event notification, identifies multiple functions belonging to the same group that correspond to the notified event, and submits execution requests for the identified multiple functions to the execution request queue 213 of the corresponding group (step S505).
The function execution section 217 performs a process of retrieving an execution request from the execution request queue 213 (step S502).Then, the function execution section 217 determines whether or not the execution request has been retrieved from the execution request queue 213 (step S503).
When an execution request is taken out of the execution request queue 213, the function execution unit 217 generates an execution thread 215 in the function execution environment 214, calls the corresponding function 216, and executes the function 216 (step S506).
The process then returns to step S502.
If the execution request queue 213 is empty and the function execution section 217 cannot extract an execution request, the process returns to step S502.

In step S506, the function execution unit 217 successively executes a plurality of functions that have a common trigger event and belong to the same group.
That is, in the case where there are functions α and β that belong to the same group and are triggered by event A, when event A occurs, function execution unit 217 executes functions α and β successively.

In this embodiment, as described above, the function registration unit 111 can classify multiple early completion functions that have a common trigger event and are set to the same priority into the same group. In this case, the function execution unit 217 can sequentially execute multiple early completion functions classified into the same group in priority over other functions.

***Description of Effects of the Embodiment***
As described above, according to the present embodiment, the number of threads can be reduced. As a result, according to the present embodiment, the overhead caused by thread switching can be reduced, and the amount of resources used, such as memory, can be reduced.

Embodiment 4.
In the third embodiment, a plurality of functions to be classified into the same group are determined based on a function registration request from a user.
Alternatively, the function execution unit 200 may determine a plurality of functions that are classified into the same group.
In this embodiment, an example will be described in which the function execution device 200 determines a plurality of functions to be classified into the same group.
In this embodiment, differences from the first and third embodiments will be mainly described.
It should be noted that matters not explained below are similar to those in the first or third embodiment.

***Configuration Description***
In this embodiment, the hardware configuration (FIG. 1) and the functional configuration (FIG. 2) are the same as those in the first embodiment.

In this embodiment, the registration data 105d shown in FIG. 18 is used.
The registration data 105d includes a function, execution setting information, priority information, and grouping flag information.
The functions, execution setting information and priority information are the same as those shown in Fig. 3, so a description thereof will be omitted.
The grouping flag information is binary data that defines whether or not a function is allowed to be included in a group. When the function registration unit 111 allows the function of the registration data 105d to be included in a group, the function registration unit 111 sets the grouping flag information to True. On the other hand, when the function of the registration data 105d is not allowed to be included in a group, the function registration unit 111 sets the grouping flag information to False.
The function registration unit 111 sets True to the grouping flag information of a plurality of functions that share a common event and have the same priority. On the other hand, the function registration unit 111 sets False to the grouping flag information of a function that does not have other functions that share a common event and have the same priority.

In this embodiment, the function registration unit 111 sets True to the grouping flag information of multiple early completion functions that have a common trigger event and the same priority. In this way, the function registration unit 111 allows the function execution device 200 to group multiple early completion functions that have a common trigger event and the same priority. In other words, the function registration unit 111 allows the function execution device 200 to execute such early completion functions consecutively. Note that grouping flag information set to True corresponds to consecutive execution permission information.

In this embodiment, as in embodiment 3, the event function correspondence table 205c is used.

*** Operation Description ***
Next, an example of the operation of the function registration request device 100 and the function execution device 200 according to this embodiment will be described.
FIG. 19 shows the operation sequence in the execution preparation phase.

The function registration unit 111 receives a function registration request from a user (step S400). The function registration request indicates functions, events, and priorities among the elements to be included in the registration data 105d.
When the function registration unit 111 receives the function registration request, it generates registration data 105d according to the function registration request and transmits the registration data 105d and the function execution environment 214 to the function execution device 200 (step S413). More specifically, if there are multiple functions that share a common event and have the same priority, the function registration unit 111 sets True to the grouping flag information of these multiple functions. On the other hand, the function registration unit 111 sets False to the grouping flag information of functions that do not have other functions that share a common event and have the same priority.

In the function execution device 200, the receiving unit 212 receives the registration data 105d and the function execution environment 214, and the function management unit 211 stores the registration data 105c and the function execution environment 214 in the storage 204 (step S414).
Furthermore, the function management unit 211 extracts functions that have a common event and the same priority from among the functions whose grouping flag information is True, and assigns the same group ID to the extracted functions (step S415).

Next, the function management unit 211 generates an event function correspondence table 205c from the registration data 105d and the group ID assigned in step S415, and registers the event function correspondence table 205c in the storage 204 (step S416).
In other words, for functions whose grouping flag information is True, the function management unit 211 generates an event-function correspondence table 205c using the function, event information, and priority information of the registration data 105d, and the group ID assigned in step S415.
On the other hand, for functions whose grouping flag information is False, the function management unit 211 generates the event-function correspondence table 205c by using the functions, event information, and priority information in the registration data 105d. For functions whose grouping flag information is False, a Null value is set in the group ID column.

The operation sequence after the execution preparation phase (steps S411 and S412) is the same as that shown in FIG.
The operation sequence of the event execution phase is the same as that shown in FIG.

In this embodiment, as described above, the function registration unit 111 can allow the function execution device 200 to group multiple early completion functions that share a common event and are set to the same priority. In this case, the function management unit 211 can classify multiple early completion functions that share a common event and are set to the same priority into the same group. Then, as in embodiment 3, when executing any one of the early completion functions, the function execution unit 217 can sequentially execute other early completion functions classified into the same group in priority to other functions.

***Description of Effects of the Embodiment***
As described above, in this embodiment, function grouping is performed by the function execution device 200. This embodiment also makes it possible to reduce overhead caused by thread switching, and also to reduce the amount of resources such as memory used.

Although the first to fourth embodiments have been described above, two or more of these embodiments may be combined for implementation.
Alternatively, one of these embodiments may be partially implemented.
Alternatively, two or more of these embodiments may be partially combined and implemented.
Furthermore, the configurations and procedures described in these embodiments may be modified as necessary.

***supplementary explanation***
Finally, a supplementary explanation will be given regarding the configurations of the function registration request device 100 and the function execution device 200.
At least one of information, data, signal values, and variable values indicating the results of processing by the function registration unit 111 is stored in at least one of the memory 102, the storage 104, a register in the CPU 101, and a cache memory.
Furthermore, the program that realizes the functions of the function registration unit 111 may be stored in a portable recording medium such as a magnetic disk, a flexible disk, an optical disk, a compact disk, a Blu-ray (registered trademark) disk, a DVD, etc. Then, the portable recording medium in which the program that realizes the functions of the function registration unit 111 is stored may be distributed.
Similarly, at least one of information, data, signal values, and variable values indicating the results of processing by the function management unit 211, the receiving unit 212, the function execution environment 214, and the function execution unit 217 is stored in at least one of the memory 202, the storage 204, the register within the CPU 201, and the cache memory.
Furthermore, the programs that realize the functions of the function management unit 211, the receiving unit 212, the function execution environment 214, and the function execution unit 217 may be stored in a portable recording medium such as a magnetic disk, a flexible disk, an optical disk, a compact disk, a Blu-ray (registered trademark) disk, a DVD, etc. Then, the portable recording medium on which the programs that realize the functions of the function management unit 211, the receiving unit 212, the function execution environment 214, and the function execution unit 217 are stored may be distributed.

Furthermore, the "part" in at least any of the function registration unit 111, the function management unit 211, the receiving unit 212, and the function execution unit 217 may be read as a "circuit" or a "process" or a "procedure" or a "processing" or a "circuitry".
Furthermore, the function registration request device 100 and the function execution device 200 may be realized by a processing circuit. The processing circuit is, for example, a logic IC (Integrated Circuit), a GA (Gate Array), an ASIC (Application Specific Integrated Circuit), or an FPGA (Field-Programmable Gate Array).
In this case, the function registration unit 111, the function management unit 211, the receiving unit 212, and the function execution unit 217 are each realized as part of a processing circuit.
In this specification, the higher-level concept of a processor and a processing circuit is called "processing circuitry."
That is, a processor and a processing circuit are each specific examples of "processing circuitry."

100 function registration request device, 101 CPU, 102 memory, 103 communication device, 104 storage, 105 registration data, 105b registration data, 105c registration data, 105d registration data, 110 operating system, 111 function registration unit, 200 function execution device, 201 CPU, 202 memory, 203 communication device, 204 storage, 205 event function correspondence table, 205b event function correspondence table, 205c event function correspondence table, 210 operating system, 211 function management unit, 212 receiving unit, 213 execution request queue, 214 function execution environment, 215 execution thread, 216 function, 217 function execution unit, 300 network.

Claims

an information generating unit that generates instruction information for instructing a function execution device to complete the execution of an early completion function, which is a function that needs to be completed earlier than other functions among a plurality of functions to be executed by the function execution device, earlier than the other functions;
a function sending device having a sending section for sending the early completing function and the instruction information to the function executing device;
The information generating unit
2. The function transmitting device according to claim 1, wherein the instruction information is priority information indicating that the early completing function has a higher priority than other functions.
The information generating unit
2. The function transmission device according to claim 1, wherein the instruction information generates CPU core allocation information that instructs the function execution device to allocate a specific CPU core among a plurality of CPU (Central Processing Unit) cores included in the function execution device to the early completion function.
The information generating unit
If there are two or more early completion functions, grouping the two or more early completion functions;
2. The function transmitting device according to claim 1, further comprising: generating, for each of the two or more grouped early completing functions, instruction information for instructing the function executing device to execute the two or more grouped early completing functions consecutively.
The information generating unit
generating successive execution permission information for permitting successive execution of the two or more early completion functions when there are two or more early completion functions;
The transmission unit is
2. The function transmitting device according to claim 1, further comprising: a function transmitting unit configured to transmit the two or more early completing functions, the instruction information, and the continuous execution permission information to the function executing unit.
a receiving unit for receiving instruction information for instructing that an early completion function, which is a function among a plurality of functions that needs to be completed earlier than other functions, be completed earlier than other functions, and the early completion function;
a function execution unit that executes the early completing function in accordance with the instruction information so that execution is completed earlier than other functions.
The receiving unit is
7. The function execution device according to claim 6, wherein the instruction information includes priority information indicating that the early completing function has a higher priority than other functions.
The receiving unit is
receiving, as the instruction information, CPU core allocation information instructing the function execution device to allocate a specific CPU core among a plurality of CPU (Central Processing Unit) cores included in the function execution device to the early completion function;
The function execution unit is
7. The function execution device according to claim 6, wherein the specific CPU core designated in the CPU core allocation information is assigned to the early completion function to execute the early completion function.
The receiving unit is
receiving instruction information instructing to execute two or more grouped early completion functions in succession and the two or more grouped early completion functions;
The function execution unit is
7. The function execution unit according to claim 6, wherein the two or more grouped early completing functions are executed consecutively.
The receiving unit is
receiving two or more early completion functions and consecutive execution permission information permitting consecutive execution of the two or more early completion functions;
The function execution unit is
7. The function execution device according to claim 6, wherein when any one of the early completion functions is executed, another early completion function is executed consecutively according to the consecutive execution permission information.
A computer generates instruction information for instructing a function execution device to complete the execution of an early completion function, which is a function that needs to be completed earlier than other functions among a plurality of functions to be executed by the function execution device, earlier than the other functions;
A function sending method in which the computer sends the early completing function and the instruction information to the function execution device.
A computer receives instruction information instructing a function that needs to be completed earlier than other functions among a plurality of functions, and the early completion function; and
The function execution method, in which the computer executes the early completing function in accordance with the instruction information so that execution of the early completing function is completed earlier than other functions.
an information generating process for generating instruction information for instructing a function execution device to complete the execution of an early completion function, which is a function that needs to be completed earlier than other functions among a plurality of functions to be executed by the function execution device, earlier than the other functions;
a function sending program that causes a computer to execute a sending process of sending the early completing function and the instruction information to the function execution device.
a receiving process for receiving instruction information for instructing that an early completion function, which is a function among a plurality of functions that needs to be completed earlier than other functions, be completed earlier than other functions, and the early completion function;
and a function execution process for executing the early completing function so that execution of the early completing function is completed earlier than other functions in accordance with the instruction information.