JP2009271726A - Electronic device, method of controlling program execution, and program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide an electronic device capable of appropriately restricting the execution of a program that allows another program to dynamically let a process interrupt, a method of controlling program execution, and a program. <P>SOLUTION: The electronic device has a determining means for determining whether or not a second program that allows a first program for application to dynamically let a process interrupt can be applied based on whether or not second data associated with the second program and first data associated with the first program conform to a predefined correspondence relationship, and an execution control means for applying the second program to the first program and executing the second program according to the result of determination by the determining means. <P>COPYRIGHT: (C)2010,JPO&INPIT

Description

  The present invention relates to an electronic device, a program execution control method, and a program, and more particularly, to an electronic device, a program execution control method, and a program that control execution of a program that can dynamically cause another program to interrupt processing.

  Conventionally, analysis of a log output by a program has been performed as a typical operation for failure analysis (debugging and the like) of a program operating in an embedded device or the like. That is, the source code of the program includes an instruction (for example, a printf function in C language) for outputting a variable value used by the program, information indicating the status of the hardware on which the program is operating, etc. to a log file. ) Are embedded in advance. When a failure occurs, the cause of the failure is estimated or specified by analyzing a log file output according to such a command (hereinafter referred to as a “log output command”).

  However, in many cases, the log file output based on the log output command embedded in advance (the log file output first) is insufficient as information for performing detailed analysis. In such a case, the failure location is narrowed down to some extent based on the log file output first. Subsequently, the source code of the program is corrected, compiled and linked so that a more detailed log is output around the faulty part, and then the program is replaced. If the cause cannot be identified by the newly output log file, a log output command is further embedded in the source code, and the above operation is repeated. As described above, when performing failure analysis based on logs, sometimes very complicated work is required.

Therefore, conventionally, there is a technique for dynamically interrupting (at the time of execution) the processing of a diagnostic program for an arbitrary program (diagnostic position) of an operating program. In the diagnostic program, it is possible to refer to values of variables of the program to be diagnosed. After completion of the diagnostic program processing, the processing returns to the position interrupted by the diagnostic program for the program to be diagnosed. According to such a technique, it is possible to output a log of a program to be diagnosed by the diagnostic program without correcting the source code of the program to be diagnosed.
JP 2004-139572 A

  However, since such a diagnostic program can be applied to any program, a diagnostic program created by a person who is not a developer or a person in charge of maintenance of the program (application) to be applied may be easily applied. . As a result, the operation of the applied program or the entire device may become unstable, and security may not be appropriately ensured. In addition, when a plurality of diagnostic programs having an exclusive relationship are executed simultaneously, there is a possibility that the intended operation of each diagnostic program may not be obtained.

  The present invention has been made in view of the above points, and an electronic apparatus and a program execution control method capable of appropriately restricting the execution of a program capable of dynamically interrupting another program. And to provide a program.

  Therefore, in order to solve the above-described problem, the present invention provides second data associated with a second program capable of dynamically interrupting processing to the first program to be applied; A determination unit that determines whether or not the second program can be applied based on whether or not the first data associated with the one program matches a predefined correspondence relationship; and a determination by the determination unit According to the result, it has execution control means for applying the second program to the first program and executing it.

  In such an electronic device, it is possible to appropriately limit the execution of a program capable of dynamically interrupting another program.

  According to the present invention, it is possible to provide an electronic device, a program execution control method, and a program that can appropriately limit the execution of a program that can dynamically interrupt the processing of another program.

  Hereinafter, embodiments of the present invention will be described with reference to the drawings. FIG. 1 is a diagram illustrating a configuration example of a device management system according to an embodiment of the present invention. In the device management system 1 of FIG. 1, the management server 10 and the devices 20a, 20b, and 20c (hereinafter collectively referred to as “device 20”) are a network 50 such as a LAN (Local Area Network) in the office. (It does not matter whether wired or wireless).

  The device 20 is an image forming apparatus (multifunction machine) that realizes a plurality of functions such as copying, facsimile, printer, and scanner in a single casing. The device 20 includes a CPU and a memory, and realizes various functions based on control by the CPU according to a program recorded in the memory. In the present embodiment, the device 20 corresponds to an example of an electronic device.

  The management server 10 is a computer that manages an additional program applied to a program used in the device 20 and transfers the additional program to the device 20. In the present embodiment, the additional program refers to a program that can dynamically interrupt processing defined in the additional program at an arbitrary location of the program to be applied.

  FIG. 2 is a diagram for explaining the outline of the additional program. In FIG. 2, reference numeral 501 denotes an instruction arrangement on the virtual memory in a program to which the additional program 505 is applied. The program 501 executes processing in the order of instructions 1, 2, and 3 before the additional program 501 is applied (during normal execution). Reference numeral 501a denotes a state in which the additional program 501 is applied to the program 501. Here, an example in which the processing of the additional program 505 is interrupted between the instruction 1 and the instruction 2 is shown. In this case, instruction 2 is replaced with a branch instruction to table 502. In the table 502, instruction 2 is executed after initialization processing, preprocessing (saving of variables to the stack, etc.), calling processing of the additional program 505, and postprocessing (extraction of variables saved in the stack, etc.). Definition to return to the instruction 3 of the program 501 is made.

  That is, when the additional program is applied, when the execution step of the program to be applied reaches a predetermined location (additional position), the processing of the additional program is executed. When the process of the additional program is completed, the process control returns to the application program. Thereafter, the program to be applied resumes processing from the additional position. Note that the additional program includes information for identifying a program to be applied and an additional position, in addition to processing to interrupt the program to be applied.

  In the additional program, it is possible to refer to variables of the program to be applied. Therefore, the program for which processing for outputting log information indicating the value of a variable or the like at an arbitrary position of the program to be applied by the additional program or processing for realizing a new function is applied to the program to be applied. Can be interrupted.

  According to such an additional program, the log information is output and the function is enhanced without modifying (ie, dynamically), re-installing, etc. the source code for the program to be applied. Can be achieved.

  FIG. 3 is a diagram illustrating an example of the hardware configuration of the device according to the embodiment of the present invention. In the figure, the device 20 includes a controller 601, an operation panel 602, a facsimile control unit (FCU) 603, an imaging unit 604, a printing unit 605, and the like.

  The controller 601 includes a CPU 611, ASIC 612, NB621, SB622, MEM-P631, MEM-C632, HDD (hard disk drive) 633, memory card slot 634, NIC (network interface controller) 641, USB device 642, IEEE 1394 device 643, Centronics device. 644.

  The CPU 611 is an IC for various information processing. The ASIC 612 is an IC for various image processing. The NB 621 is a north bridge of the controller 601. The SB 622 is a south bridge of the controller 601. The MEM-P 631 is a system memory of the device 20. The MEM-C 632 is a local memory of the device 20. The HDD 633 is a storage of the device 20. The memory card slot 634 is a slot for setting a memory card 635. The NIC 641 is a controller for network communication using a MAC address. The USB device 642 is a device for providing a USB standard connection terminal. The IEEE 1394 device 643 is a device for providing a connection terminal of the IEEE 1394 standard. The Centronics device 644 is a device for providing connection terminals of Centronics specifications. The operation panel 602 is hardware (operation unit) for an operator to input to the device 20 and hardware (display unit) for an operator to obtain an output from the device 20.

  FIG. 4 is a diagram illustrating a software configuration example of the device according to the embodiment of the present invention. 4, the device 20 includes a standard application 21, an SDK application 22, a service layer 23, an additional program control unit 24, an OS 25, and the like. These software are loaded on the RAM in the MEM-P 631, and the CPU 611 executes the processing to realize the function.

  The standard application 21 is an application incorporated as a standard function from the time of shipment of the device 20. In the figure, as a standard application 21, a copy application 21a, a FAX application 21b, a printer application 21c, and a scanner application 21d are illustrated.

  The copy application 21a is an application that realizes a copy function. The FAX application 21b is an application that realizes a FAX function. The printer application 21c is an application that realizes a printing function. The scanner application 21d is an application that realizes a scanner function.

  The SDK application 22 is an application created for the device 20 using a dedicated SDK (software development kit). More specifically, a part of API (Application Program Interface) of the service layer 23 is disclosed, and the SDK application 22 is an application created by a third vendor using the API. In the figure, as the SDK application 22, SDK applications 22a and 22b are illustrated. Each SDK application 22 is attached (or associated) with a certificate (electronic certificate). For example, a certificate 221a is attached to the SDK application 22a, and a certificate 221b is attached to the SDK application 22b (hereinafter, these certificates are collectively referred to as “certificate 221”). The certificate 221 includes owner information, public key, certificate authority signature, program ID, and the like. Among these, the owner information is identification information (for example, ID) of the creator (development vendor) of the SDK application 22 to which the certificate 221 is attached. The program ID is an ID that can uniquely identify each SDK application 22.

  The service layer 23 includes a group of programs that provide services (functions) that are commonly required by a plurality of applications 21 to the applications 21. The service layer 23 includes, for example, a program that mediates network communication, a program that controls hardware such as the imaging unit 604 and the printing unit 605, a program that manages storage devices such as a memory and a hard disk drive, and an operation panel 602. There are programs for controlling the above.

  The OS 25 is a so-called OS (Operating System). The OS 25 is not limited to a predetermined one.

  The additional program control unit 24 is software that performs execution control of the above-described additional program (shown as an additional program 26 in the drawing). For example, the additional program control unit 24 downloads the additional program 26, applies (executes) it to the application target, and the like. As shown in the figure, a certificate 261 is attached to each additional program 26 in the present embodiment. The certificate 261 is an electronic certificate and includes, for example, owner information, a public key, a certificate authority signature, a program ID, and the like. Among these, the owner information is identification information (for example, ID) of the creator (development vendor) of the additional program 26 to which the certificate 261 is attached. The program ID is an ID that can uniquely identify each additional program 26. Note that the configuration of the certificate 261 is the same as the certificate 221 for the SDK application 22, but the two do not necessarily have the same configuration.

  Hereinafter, the processing procedure of the device 20 will be described. FIG. 5 is a flowchart for explaining the application process of the additional program in the first embodiment. In the figure, it is assumed that the user has already been authenticated. That is, each program of the device 20 can identify the user who is currently operating (current user).

  In response to an operation input by the user via the operation panel 602, the additional program control unit 24 acquires the list information of the additional program 26 managed by the management server 10 from the management server 10 and displays it on the operation panel 602 (S101). ).

  When the user selects an additional program 26 to be used from the list information (S102), the additional program control unit 24 downloads the selected additional program 26 from the management server 10, and the additional program 26 (hereinafter “ It is confirmed whether or not the current user has authority to use (referred to as “current addition program 26”) (S103). Whether or not the use authority is confirmed may be determined based on, for example, access control information for the additional program 26 defined in advance. In the access control information, a user name or the like that can be used for each additional program 26 may be defined, or a program name (file name) or a program ID of the additional program 26 that can be used for each user may be defined. May be. Or the information which can identify the user who can use the additional program 26, and the user who is not otherwise may be sufficient. Further, the access control information may be stored in the HDD 633 of the device 20 or may be stored in the management server 10.

  If the current user has usage authority (Yes in S103), the additional program control unit 24 determines whether or not the current additional program 26 can be executed on the device 20 (S104). The determination here corresponds to determination of whether or not the current additional program 26 can be executed in the program execution environment of the device 20. For example, the attribute information of the additional program 26 includes the model of the device 20 on which the additional program 26 can operate, the version of the service layer 23, the version of the OS 25, and the like. Version etc.) is determined. The attribute information of the current addition program 26 is downloaded from the management server 10 together with the current addition program 26.

  When the current additional program 26 can be executed on the device 20 (Yes in S104), the additional program control unit 24 performs an authentication process (validity verification) of the current additional program 26 based on the certificate 261 ( S105). The authentication of the program based on the electronic certificate may follow a general method.

  When the current addition program 26 is authenticated (Yes in S105), the additional program control unit 24 assumes that the SDK application 22 (here, “SDK application 22a”) to which the current addition program 26 is applied (application destination). .) Is obtained from the certificate 221a (S106). Information for identifying a program to which the current additional program 26 is applied is included in the additional program 26 in a format that can be interpreted by the additional program control unit 24. Therefore, based on such information, the additional program control unit 24 can determine that the application target is the SDK application 22a.

  Subsequently, the additional program control unit 24 acquires owner information from the certificate 261 of the current additional program 26 (S107). Subsequently, as shown in FIG. 6, the additional program control unit 24 collates the owner information to be applied with the owner information of the current additional program 26 (S108). If the two pieces of owner information match (Yes in S108), the additional program control unit 24 applies the current additional program 261 to the application SDK application 22a (S109). Specifically, when the execution step of the SDK application 22a reaches a location (additional position) designated in the current additional program 26, the additional program control unit 24 executes (interrupts) the processing of the additional program 26.

  On the other hand, if the current user is not authorized to use the current additional program 26 (No in S103), the current additional program 26 is not executable on the device 20 (No in S104), or the authentication of the current additional program 26 fails (No in S105), or if the owner information to be applied and the owner information of the current additional program 26 do not match (No in S108), the additional program control unit 24 does not apply the current additional program 26, For example, a message indicating that the current additional program 26 cannot be used is displayed on the operation panel 602 (S110).

  As described above, according to the first embodiment, when the owner information to be applied and the owner information of the additional program 26 do not match, the additional program 26 is not executed. Therefore, the additional program 26 created by a certain development vendor is prevented from being easily applied to the SDK application 22 developed by another development vendor.

  Next, a second embodiment will be described. In the second embodiment, differences from the first embodiment will be described. Accordingly, the points not particularly mentioned may be the same as those in the first embodiment.

  FIG. 7 is a flowchart for explaining an additional program application process according to the second embodiment. In FIG. 7, the same steps as those in FIG. 5 are denoted by the same step numbers, and description thereof will be omitted as appropriate.

  In the figure, step S106 is replaced with step S106a, and step S108 is replaced with S108a. In step S106a, the additional program control unit 24 acquires the program ID from the certificate 221a of the SDK application 22a to which the current additional program 26 is applied. Subsequently, the additional program control unit 24 acquires owner information from the certificate 261 of the current additional program 26 (S107). Subsequently, the additional program control unit 24 refers to the applicability determination table to determine whether the current additional program 26 is applicable (S108a).

  FIG. 8 is a diagram illustrating a configuration example of an applicability determination table. In the figure, an applicability determination table 31 is defined (registered) for each program ID of the SDK application 22 (that is, for each SDK application 22) which additional program 26 relating to the owner is applicable. ing. For example, in the figure, an additional program 26 whose owner information is “AAA”, “BBB”, or “CCC” can be applied to the SDK application 22 whose program ID is “SDK-0001”. It is defined that there is. The applicability determination table 31 may be stored in the HDD 633 of the device 20 or may be stored in the management server 10. The applicability determination table 31 may be editable only to a predetermined person such as an administrator.

  Therefore, the additional program control unit 24 determines applicable owner information by applying the program ID (program ID to be applied) acquired in step S106a to the applicability determination table 31, and includes the owner information in the owner information. The applicability is determined based on whether the owner information of the current additional program 26 acquired in step S107 is included. When the owner information of the current additional program 26 is included in the applicable owner information (Yes in S108a), the additional program control unit 24 applies the current additional program 261 to the target SDK application 22a (S109). ).

  When the owner information of the current additional program 26 is not included in the applicable owner information (No in S108a), the additional program control unit 24 does not apply the current additional program 26 (S110).

  As described above, according to the second embodiment, whether or not the additional program 26 can be applied is determined based on the applicability determination table 31. Therefore, even if the SDK application 22 and the additional program 26 have different owner information (development vendor), the additional program 26 can be applied. Therefore, the flexibility of application of the additional program 26 can be improved as compared with the first embodiment.

  In addition, in the applicability determination table 31, not the correspondence relationship between the SDK application 22 and the owner information of the additional program 26, but the correspondence relationship between the SDK application 22 and the additional program 26 may be registered. Specifically, the program ID of the applicable additional program 26 may be registered for each program ID of the SDK application 22. In this case, in step S107, the program ID of the current additional program 26 may be obtained from the certificate 261, and the determination in step S108a may be performed using the program ID. However, in this case, it is necessary to update the applicability determination table 31 every time the additional program 26 is created. Therefore, from the viewpoint of the stability (reduction of maintenance work) of the applicability determination table 31, the form shown in FIG. 8 is preferable.

  If such a viewpoint is further pursued, the correspondence relationship between the owner information of the SDK application 22 and the owner information of the additional program 26 may be registered in the applicability determination table 31. In this case, if a new owner (development vendor) is not added, the necessity of changing the applicability determination table 31 is low, so that the stability of the applicability determination table 31 can be further improved.

  Subsequently, a third embodiment will be described. In the third embodiment, differences from the first embodiment will be described. Accordingly, the points not particularly mentioned may be the same as those in the first embodiment.

  FIG. 9 is a flowchart for explaining an additional program application process according to the third embodiment. In FIG. 9, the same steps as those in FIG. 5 are denoted by the same step numbers, and the description thereof is omitted as appropriate.

  In the figure, steps S106 to S108 are replaced with steps S106b, 107b, and S108b, respectively. In step S106b, the additional program control unit 24 generates a list of program IDs of the additional program 26 that is currently being applied (already being applied). Since the additional program control unit 24 is a program that controls the execution of the additional program 26, the additional program control unit 24 grasps the program ID of the additional program 26 that is currently being applied.

  Subsequently, the additional program control unit 24 acquires the program ID from the certificate 261 of the current additional program 26 to be applied (S107b). Subsequently, the additional program control unit 24 refers to the exclusive relationship management table and determines whether or not the current additional program 26 can be applied (S108b).

  FIG. 10 is a diagram illustrating a configuration example of the exclusive relationship management table. In the figure, the exclusive relationship management table 32 has an exclusive relationship with respect to execution time for each program ID of the additional program 26 (that is, for each additional program 26) (that is, it cannot be executed simultaneously or is executed simultaneously). The program ID of the additional program is defined (registered). For example, in the figure, the additional program 26 whose program ID is “P0001” has an exclusive relationship with the additional programs 26 whose program IDs are “P0002”, “C0001”, “C0002”, and “F0001”. It is defined. The exclusive relationship management table 32 may be stored in the HDD 633 of the device 20 or may be stored in the management server 10. The exclusive relationship management table 32 may be editable only to a predetermined person such as an administrator.

  Therefore, the additional program control unit 24 acquires the program ID of the additional program 26 that has an exclusive relationship with the program ID of the current additional program 26 acquired in step S107b from the exclusive relationship management table 32, and is acquired. Whether or not the program ID can be applied is determined based on whether or not at least one of the program IDs is included in the list of program IDs of the additional program 26 that is currently being applied (executed) generated in step S106b. If any of the program IDs having an exclusive relationship is not included in the currently executed program ID (Yes in S108b), the additional program control unit 24 applies the current additional program 261 to the target SDK application 22a. (S109).

  If any of the program IDs having an appropriate exclusive relationship is included in the currently executing program ID (No in S108b), the additional program control unit 24 does not apply the current additional program 26 (S110). .

  In the above description, the exclusive relationship management table 32 shows an example in which information indicating an exclusive relationship is managed. However, information indicating relationships that can be executed simultaneously may be managed in the exclusive relationship management table 32. This is because even in this case, the exclusive relationship can be determined.

  As described above, according to the third embodiment, parallel execution (simultaneous execution) of the additional program 26 having an exclusive relationship can be appropriately avoided. Accordingly, it is possible to prevent the unauthorized operation of the device 20 due to the parallel execution of the additional program 26 having an exclusive relationship. The exclusive relationship includes, for example, a relationship such as accessing the same parameter of the device 20 that has the same application target. However, it is not intended to be immediately defined as an exclusive relationship when this condition is satisfied. For example, even if the application target is the same, there is a possibility that the exclusive relationship may not be established if the application target can be interrupted without interfering with each other.

  Note that the third embodiment may be implemented in combination with the first or second embodiment. By doing so, application and execution of the additional program 26 can be restricted based on the combination of the relationship between the program to be applied and the additional program 26 and the relationship between the additional programs 26.

  As mentioned above, although the Example of this invention was explained in full detail, this invention is not limited to such specific embodiment, In the range of the summary of this invention described in the claim, various deformation | transformation・ Change is possible.

It is a figure which shows the structural example of the apparatus management system in embodiment of this invention. It is a figure for demonstrating the outline | summary of an additional program. It is a figure which shows an example of the hardware constitutions of the apparatus in embodiment of this invention. It is a figure which shows the software structural example of the apparatus in embodiment of this invention. It is a flowchart for demonstrating the application process of the additional program in 1st embodiment. It is a figure which shows the collation of owner information notionally. It is a flowchart for demonstrating the application process of the additional program in 2nd embodiment. It is a figure which shows the structural example of an applicability determination table. It is a flowchart for demonstrating the application process of the additional program in 3rd embodiment. It is a figure which shows the structural example of an exclusive relationship management table.

Explanation of symbols

1, 2 Device management system 10 Management server 11 Additional processing control unit 12 Additional program management unit 20 Device 21 Standard application 21a Copy application 21b FAX application 21c Printer application 21d Scanner application 22 SDK application 22a, 22b SDK application 23 Service layer 24 Additional program Control unit 25 OS
26 Additional programs 221a, 221b, 261 Certificate 601 Controller 602 Operation panel 603 Facsimile control unit 604 Imaging unit 605 Printing unit 611 CPU
612 ASIC
621 NB
622 SB
631 MEM-P
632 MEM-C
633 HDD
634 Memory card slot 635 Memory card 641 NIC
642 USB device 643 IEEE 1394 device 644 Centronics device

Claims (18)

Second data associated with a second program capable of dynamically interrupting processing to the first program to be applied, and first data associated with the first program Determining means for determining whether or not the second program can be applied based on whether or not matches a predefined correspondence relationship;
An electronic apparatus comprising: an execution control unit that applies the second program to the first program and executes the second program according to a determination result of the determination unit. The first data and the second data are data indicating the creator of the program to which each is added,
The electronic device according to claim 1, wherein the determination unit determines that the application of the second program is possible when the first data matches the second data. The first data is a program identifier for identifying each of the plurality of first programs, the second data is data indicating the creator of the second program,
Management means for managing correspondence information capable of determining an applicable correspondence relationship between the program identifier and the creator;
The electronic device according to claim 1, wherein the determination unit determines whether the second program can be applied based on the first data, the second data, and the correspondence information. The first data is a program identifier that identifies each of the plurality of first programs, and the second data is a program identifier that identifies each of the plurality of second programs,
Management means for managing correspondence information capable of determining an applicable correspondence relationship between the program identifier of the first program and the identifier of the second program;
The electronic device according to claim 1, wherein the determination unit determines whether the second program can be applied based on the first data, the second data, and the correspondence information. The first data and the second data are data indicating the creator of the program to which each is added,
Management means for managing correspondence information capable of determining an applicable correspondence relationship between the creator of the first program and the creator of the second program;
The electronic device according to claim 1, wherein the determination unit determines whether the second program can be applied based on the first data, the second data, and the correspondence information. A management means for managing correspondence information capable of determining an exclusive relationship of execution times for a plurality of second programs capable of dynamically interrupting processing to the first program to be applied;
Determination means for determining whether or not the second program already applied and the second program to be applied are in an exclusive relationship based on the correspondence information;
An electronic apparatus comprising: an execution control unit that applies the second program applied from here to the first program according to a determination result of the determination unit. A program execution control method executed by an electronic device,
Second data associated with a second program capable of dynamically interrupting processing to the first program to be applied, and first data associated with the first program A determination procedure for determining whether or not the second program can be applied based on whether or not matches a predefined correspondence relationship;
An execution control procedure for executing the second program by applying the second program to the first program according to a determination result of the determination procedure. The first data and the second data are data indicating the creator of the program to which each is added,
8. The program execution control method according to claim 7, wherein the determination procedure determines that the application of the second program is possible when the first data and the second data match. . The first data is a program identifier for identifying each of the plurality of first programs, the second data is data indicating the creator of the second program,
The determination procedure is based on management means for managing correspondence information capable of determining an applicable correspondence relationship between the program identifier and the creator, and the second data based on the first data and the second data. 8. The program execution control method according to claim 7, wherein the applicability of the program is determined. The first data is a program identifier that identifies each of the plurality of first programs, and the second data is a program identifier that identifies each of the plurality of second programs,
The determination procedure includes management means for managing correspondence information capable of determining an applicable correspondence relationship between the program identifier of the first program and the identifier of the second program, the first data, and the second data 8. The program execution control method according to claim 7, wherein whether or not the second program can be applied is determined on the basis of the data. The first data and the second data are data indicating the creator of the program to which each is added,
The determination procedure includes: management means for managing correspondence information capable of determining an applicable correspondence relationship between the creator of the first program and the creator of the second program; the first data; and the second data 8. The program execution control method according to claim 7, wherein whether or not the second program can be applied is determined on the basis of the data. A program execution control method executed by an electronic device,
Already applied based on the management means that manages the correspondence information that can determine the exclusive relationship of execution time for multiple second programs that can dynamically interrupt the processing of the first program to be applied A determination procedure for determining whether or not the second program in the second program to be applied is exclusive based on the correspondence information;
A program execution control method, comprising: an execution control procedure for applying the second program applied from here to the first program according to a determination result of the determination procedure. Electronic equipment,
Second data associated with a second program capable of dynamically interrupting processing to the first program to be applied, and first data associated with the first program A determination procedure for determining whether or not the second program can be applied based on whether or not matches a predefined correspondence relationship;
A program for executing an execution control procedure for applying the second program to the first program and executing the second program according to a determination result of the determination procedure. The first data and the second data are data indicating the creator of the program to which each is added,
14. The program according to claim 13, wherein the determination procedure determines that the application of the second program is possible when the first data matches the second data. The first data is a program identifier for identifying each of the plurality of first programs, the second data is data indicating the creator of the second program,
The determination procedure is based on management means for managing correspondence information capable of determining an applicable correspondence relationship between the program identifier and the creator, and the second data based on the first data and the second data. 14. The program according to claim 13, wherein the applicability of the program is determined. The first data is a program identifier that identifies each of the plurality of first programs, and the second data is a program identifier that identifies each of the plurality of second programs,
The determination procedure includes management means for managing correspondence information capable of determining an applicable correspondence relationship between the program identifier of the first program and the identifier of the second program, the first data, and the second data 14. The program according to claim 13, wherein whether or not the second program is applicable is determined based on the data. The first data and the second data are data indicating the creator of the program to which each is added,
The determination procedure includes: management means for managing correspondence information capable of determining an applicable correspondence relationship between the creator of the first program and the creator of the second program; the first data; and the second data 14. The program according to claim 13, wherein whether or not the second program is applicable is determined based on the data. Electronic equipment,
Already applied based on the management means that manages the correspondence information that can determine the exclusive relationship of execution time for multiple second programs that can dynamically interrupt the processing of the first program to be applied A determination procedure for determining whether or not the second program in the second program to be applied is in an exclusive relationship based on the correspondence information;
A program for executing an execution control procedure for causing the second program applied from here to be applied to the first program in accordance with a determination result of the determination procedure.

Images