JP5566832B2 - Information processing apparatus and information processing method - Google Patents

Description

  The present invention relates to a technique for managing a process executed in an information processing apparatus, and more particularly, to a technique for managing start and stop of a process executed in an information processing apparatus by a simple method.

  2. Description of the Related Art In recent years, as home appliances such as car navigation systems become more sophisticated, an OS (operating system) is incorporated in the product to control a microcomputer built in the product. The OS is defined in JIS (Japanese Industrial Standards) X0001 as “software that controls program execution and provides services such as resource allocation, scheduling, input / output control, and data management”. Among these, “controlling program execution” is an important role of the OS.

There are mainly two methods for controlling the execution of the program by the OS. One method is, for example, a method represented by μITRON, in which each program is regarded as one program and is controlled in an execution unit called a task (hereinafter referred to as “control method by task”). The other method is a method of controlling each program in an execution unit called a process, represented by Windows (registered trademark), for example, and controlling the program in an execution unit called a thread (corresponding to the above-mentioned task). Hereinafter, “control method by process”).

  Note that controlling the execution of a program includes so-called task management, such as manipulating a task state (executable state, waiting state, etc.) or generating a task in a task control method. Controlling the execution of the program includes so-called process management such as manipulating the thread state and the process state and generating the thread and the process in the control method by the process.

  Generally, in the control method using tasks, each task can freely access other tasks and global variables of the OS, so that the start and stop of other tasks can be directly controlled. As a result, the task-based control method has the advantage that system design and construction can be performed in a simple manner. On the other hand, in the control method by tasks, since the memory space is shared by all tasks, an error that occurs in some tasks also affects other tasks. As a result, the task-based control method has a drawback that the robustness of the constructed system is low.

  On the other hand, in the control method by a process, since the memory space is divided for each process, each process basically cannot access the memory space of another process. As a result, in the control method by a process, an error generated in some threads basically does not affect threads in other processes. For this reason, the process control method has an advantage that a more robust system can be constructed than the task control method. On the other hand, with the process control method, threads in each process basically cannot freely access threads in other processes, so it is impossible to grasp the state of threads in other processes. It is practically impossible to directly control the starting and stopping of threads in other processes. As a result, the process control method increases factors that must be taken into account when starting and stopping each thread, such as the start and stop order of each process, as compared to the task control method. Therefore, the control method based on the process has a drawback that the system cannot be designed and constructed by a simple method.

  An example of system design and construction by a simple method in the task control method will be described with reference to FIG. FIG. 14 is an example of a logical configuration diagram illustrating a method for controlling execution of a program by a control method based on tasks on the information processing apparatus 1000. In FIG. 14, “task” for each task is omitted.

The information processing apparatus 1000 includes one or a plurality of processors such as a CPU (Central Processing Unit) and a memory used for the processing of the processors (ROM (Read Only Memory), RAM (Random Access Memory), an interface circuit, etc.) Including hardware. An OS, each task, and management information 1002 are stored in a memory included in the hardware. Then, the CPU included in the hardware processes the data (OS, each task, and management information 1002) stored in the memory, thereby realizing the logical configuration diagram of FIG. 14 and the processing of each task. In FIG. 14, the above-mentioned tasks indicate a system management task 1001, a PLATFORM control task 1003, an A control task 1004, a B control task 1005, a C control task 1006, and a D control task 1007.

  In the control method using tasks in FIG. 14, a system management task 1001 that is a task processed on the information processing apparatus 1 uses the management information 1002 that stores the start and stop factors of each task, and uses other tasks (PLATFORM control). Task 1003, A control task 1004, B control task 1005, C control task 1006, D control task 1007, etc.).

  FIG. 15 is a record example of the management information 1002. The record of the management information 1002 in FIG. 15 includes a task name for designating a task type, a task priority indicating the priority of execution of each task, and a stack size indicating a memory size necessary for storing the task in the memory. And a field for storing a task ID for uniquely identifying each task and a task attribute which is a parameter for designating a task stop method.

  The system management task 1001 controls the activation of each task using the task name, task priority, stack size, and task ID stored in the management information 1002 (for example, the system management task 1001 has an execution priority) According to each task). The system management task 1001 controls the stop of each task using the task name, task ID, and task attribute stored in the management information 1002.

  As described above, in the control method using tasks, in the information processing apparatus 1000, a processing unit (system management task 1001) that controls activation and termination of each task and a storage unit (management) that stores the activation and termination factors of each task. By only providing the information 1002), it is possible to control the start and stop of each task.

  On the other hand, the following prior art documents can be cited as a method for designing and constructing a system by a control method based on a process. For example, in the application management apparatus disclosed in Patent Document 1, a multi-thread management unit in each process controls and manages threads in each process. If a method for controlling the execution of the program as shown in FIG. 14 is applied to the control method based on such a process, the configuration as shown in FIG. 16 is considered.

  FIG. 16 is a logical configuration diagram showing an example in which the method for controlling the execution of the program as shown in FIG. 14 described above on the information processing apparatus 1 is realized by a control method using a process in the prior art.

  As described above, the OS, each process, and each thread are stored in the memory included in the hardware. Then, the CPU included in the hardware processes the data (OS, each process, and each thread) stored in the memory, thereby realizing the logical configuration diagram of FIG. 16, each process, and each thread. In FIG. 16, the above processes refer to a system management process 1100, a PLATFORM process 1101, an X process 1102, a Y process 1103, and a Z process 1104. Further, each thread described above refers to a thread included in each process. In FIG. 16, “thread” is omitted for each thread except the primary thread.

  Since the task in the control method by the task corresponds to the thread in the control method by the process, the system management task 1001, the system management thread 1100b, the PLATFORM control task 1003, the PLATFORM control thread 1101b, and the A control task are shown in FIGS. 1004 and A control thread 1102b, B control task 1005 and B control thread 1103b, C control task 1006 and C control thread 1103c, and D control task 1007 and D control thread 1104b correspond to each other. Further, it is assumed that the multi-thread management unit disclosed in Patent Document 1 is included in the primary thread (1100a, 1101a, 1102a, 1103a, 1104a).

JP 2005-31752 A JP-A-3-257633 JP 2003-162419 A

  However, in the control method by the process of FIG. 16, in order for the system management thread 1100b to control the start and stop of other threads, the start and stop of each process (1100 to 1104) must also be controlled. There is a problem that the factors that must be considered in comparison with the control method by task increase, and the design and construction of the system become complicated.

  In addition, in order for the system management thread 1100b to control the start and stop of other threads, it is necessary to collect the state of each thread, and communication between processes must always be performed between processes including each thread. . As a result, all data used to control the start and stop of each thread is stored not in the memory space in the process, but in the memory space used for sharing in each process. There is a problem that the closed meaning is lost.

  In view of such problems, an object of the present invention is to provide a technique that enables the design and construction of a simple system.

  Another object of the present invention is to provide a technique for suppressing as much as possible interprocess communication that occurs when managing the start and stop of each thread in a process control method.

  The present invention employs the following configuration in order to solve the above-described problems.

In other words, when a program is executed in an information processing apparatus, a plurality of processes, which are execution environments separated from each other, have a parent-child relationship by a tree structure, and the parent process manages the start and stop of a child process. The information processing apparatus of the invention includes a control unit. And a control part produces | generates one or more processes provided with the 1st thread | sled and the memory | storage part which stores the management information which defined the starting factor and the stop factor of the thread in each process. In addition, the first thread includes in-process thread management means for managing the start and stop of threads other than the first thread existing in the process based on the management information stored in the storage unit. Furthermore, the parent process performs inter-process communication with the first thread of the child process according to the activation factor and the termination factor, and manages the activation and termination of the first thread, thereby starting the child process. And a second thread including child process management means for managing termination.

  According to the above configuration, the start and stop of the thread in each process is managed by the in-process thread management means of the first thread existing in each process. That is, the start and stop of the thread in each process is managed by the same method as the system design and construction by a simple method in the conventional control method by tasks. Therefore, the present invention enables simple system design and construction.

  Further, according to the above configuration, the interprocess communication performed when the activation and stop of the thread of each process is managed is the interprocess communication performed between the second thread of the parent process and the first thread of the child process. It is limited to. Therefore, since it is not necessary to perform inter-process communication for all threads, the present invention can suppress inter-process communication that occurs when managing the start and stop of each thread as much as possible.

  Further, the child process management means may manage the start and stop of a plurality of child processes.

  According to the above, since the parent process does not need to have the second thread corresponding to the number of child processes, the number of threads of the parent process can be suppressed.

  Further, the plurality of processes having a parent-child relationship by the tree structure may be all processes executed in the information processing apparatus.

  According to the above, the effects described above can be obtained in all processes executed in the information processing apparatus.

  Further, the process corresponding to the root of the tree structure may start by an operation according to the start of the information processing apparatus, and the process may start to stop by an operation according to the stop of the information processing apparatus.

  Based on the above, it is possible to manage the start and stop of processes in accordance with the start and stop operations of the information processing apparatus.

  As another aspect of the present invention, a method for realizing any of the above configurations, a system, a program, or such a program may be recorded. It may be a computer-readable storage medium.

  According to the present invention, it is possible to provide a technology that enables the design and construction of a simple system.

  Further, according to the present invention, it is possible to provide a technique for minimizing the interprocess communication that occurs when managing the start and stop of each thread in the process control method.

The figure which illustrates the whole structure of the AVN integrated machine which is an example of the apparatus which implements this invention. The figure which illustrates an example of the process composition in a 1st embodiment. The example of a record which shows an example of the management information in 1st Embodiment. 6 is a sequence chart illustrating an example of a procedure for starting a thread according to the first embodiment. The sequence chart which showed an example of the procedure of the stop process of the thread | sled in 1st Embodiment. The figure which illustrates an example of the functional structure and process structure of the AVN integrated machine in 2nd Embodiment. The figure which illustrates the detail of the process structure in FIG. The example of a record which shows an example of the management information in 2nd Embodiment. The sequence chart which showed an example of the acquisition process of the snapshot in 2nd Embodiment. The sequence chart which showed an example of the procedure of the starting process of the thread | sled in 2nd Embodiment. The sequence chart which showed an example of the procedure of the stop process of the thread | sled in 2nd Embodiment. The sequence chart which showed an example of the process sequence at the time of stopping and starting AVN integrated machine before loading a snapshot in the AVN integrated machine in 2nd Embodiment. The sequence chart which showed an example of the process sequence when starting an AVN integrated machine while stopping the thread | sled with the AVN integrated machine in 2nd Embodiment. The figure which illustrates the logic structure which shows the method of controlling execution of a program with the control method by a task. The example of the record of the management information used in the control method by a task. The figure which illustrates the logic structure which shows the method of controlling execution of a program with the control method by a process.

  Hereinafter, an information processing apparatus and an information processing method according to an aspect of the present invention will be described as an embodiment (hereinafter referred to as “this embodiment”). However, the following embodiments are merely examples, and the present invention is not limited to the configurations of the following embodiments.

  In the embodiment described below, for example, the thread name is exemplified by natural language (Japanese), such as “PLATFROM control”, but more specifically, a pseudo-language, command, Specified in parameters, machine language, etc.

§1 Hardware Configuration First, an in-vehicle audio / visual navigation integrated machine 1 (hereinafter referred to as an AVN integrated machine 1) which is an example of the present embodiment will be described. FIG. 1 is a block diagram illustrating a hardware configuration example of an AVN integrated device 1 which is an example of the present embodiment.

  The control unit 100 receives a signal from each part of the AVN integrated device 1 or a connected external device, an operation instruction signal from each operation unit based on a user operation, and the AVN integrated device 1 based on these signals. The overall control of each part or external device. The control unit 100 includes, for example, one or a plurality of microcomputers (microcomputers) and peripheral circuits (ROM (Read Only Memory), RAM (Random Access Memory), interface circuits, etc.) used for processing of the microcomputers, It operates according to a program stored in a peripheral circuit such as a ROM.

  The external storage medium playback unit 101 includes a connector for connecting an external storage medium such as a USB (Universal Serial Bus) memory or an SD card. Then, the external storage medium playback unit 101 reads desired data from various data stored in the external storage medium connected to the connector, and outputs the read image signal, audio signal, character signal, or the like to the distribution circuit 107. . The external storage medium playback unit 101 is controlled by a control signal from the control unit 100 to read data from an external storage medium connected to the connector.

  The radio reception unit 102 and the TV (television) reception unit 103 selectively receive a broadcast wave having a specific frequency from the broadcast wave received by the antenna by the selector 113 and the like, and demodulate the received broadcast wave audio signal and image signal. (In the case of television broadcasting) is output to the distribution circuit 107. The radio receiving unit 102 and the TV receiving unit 103 include a tuning circuit, a demodulation / decoding circuit, and the like. The radio receiving unit 102 and the TV receiving unit 103 are controlled by the control signal from the control unit 100 for various operations such as on / off and reception frequency.

  The disc playback unit 104 reads data stored on a disc (for example, a DVD (Digital Versatile Disc) or BD (Blu-ray Disc)) with a pickup, and distributes an audio signal, an image signal, and the like based on the read data. Output to the circuit 107. The disk reproducing unit 104 includes an optical pickup, a pickup / disk drive mechanism, a control circuit for the pickup / disk drive mechanism, a read signal decoding circuit, and the like. The disc reproducing unit 104 is controlled by the control signal from the control unit 100 to perform various operations such as reading process on / off and reading position.

An HD (hard disk) reproduction unit 105 reads desired data from various data stored in a hard disk that is a magnetic storage medium, and outputs the read image signal, audio signal, character signal, or the like to the distribution circuit 107. The hard disk contains music data such as MP3 files and J
It stores image data such as PEG (Joint Photographic Experts Group) files and MPEG (Moving Picture Experts Group) files, map data for navigation, and the like. The HD playback unit 105 includes an HD drive, a read signal decoding circuit, and the like. The HD playback unit 105 is controlled by the control signal from the control unit 100 to perform various operations such as on / off of read processing and read data.

The navigation unit 106 displays the position of the host vehicle and the route to the destination on the map, and provides guidance such as a right or left turn by voice or the like at an intersection or the like, and a traffic information communication system (VICS (registered trademark) described later). )) Obtaining and displaying traffic information from the information receiving unit 111 and displaying the vehicle position information from the GPS (registered trademark) information receiving unit 112, and performing route guidance to the destination. The navigation unit 106 includes a storage device (medium) that stores map information used for navigation, a CPU (Central Processing Unit) that performs various arithmetic processes, a memory such as a RAM that stores data for various processes, and the like. Prepare. The navigation unit 106 is controlled to turn on / off the navigation processing and various operations by a control signal from the control unit 101. The storage device (medium) for storing the map information used for navigation is the above-described external storage device connected to the external storage medium playback unit 101, the above-described disk processed by the disk playback unit 103, HD The above-described HD drive provided in the playback unit 105 may be used.

  The distribution circuit 107 is controlled by the control signal of the control unit 100 and sends audio signals and image signals of various sources (external recording medium playback unit 101 etc.) designated to be output to the audio adjustment circuit 109 and the image adjustment circuit 108. Output. The distribution circuit 107 includes a switch group including an electronic circuit such as a relay or a switching transistor.

  The image adjustment circuit 108 is controlled by the control signal of the control unit 100, adjusts the brightness, color tone, contrast, etc. of the image signal input from the distribution circuit 107, and outputs each adjusted image signal to the image output unit 110. To do. The image adjustment circuit 108 includes a memory that stores image data, an arithmetic circuit such as a digital signal processor that performs arithmetic processing on the image data, and the like.

  The sound adjustment circuit 109 is controlled by the control signal of the control unit 100, adjusts the volume and sound of the sound signal input from the distribution circuit 107, and outputs the adjusted sound signal to the speaker 123. The audio adjustment circuit 109 includes a memory that stores audio data, an arithmetic circuit such as a digital signal processor that performs arithmetic processing on image data, an amplification / attenuation circuit including a transistor, a resistor, a capacitor, a coil, and the like, a resonance circuit, and the like. The speaker 123 outputs the audio signal input by the audio adjustment circuit 110 as audio.

  The image output unit 110 is controlled by the control signal of the control unit 100, and the image signal input from the image adjustment circuit 108 and the display image signal input from the control unit 100 for displaying the image signal on the display unit 122. The display unit 122 is driven based on the image signal subjected to the processing. The image output unit 110 includes, for example, an image ASIC that is an arithmetic processing circuit specialized for an image that performs image processing by arithmetic processing, a video memory that stores image data for image processing / output, and an image output video memory An image driving circuit for driving the display unit based on the stored image data is provided.

  The VICS information receiving unit 111 receives traffic information related to VICS, and outputs the received traffic information to the navigation unit 106. The VICS information receiving unit includes a receiver (FM receiver, radio beacon receiver, optical beacon receiver) that receives data from the traffic information communication system, a decoding circuit that decodes the received data, and the like.

  The GPS signal receiving circuit 112 detects the vehicle position based on the GPS signal from the GPS satellite, and outputs the detected current location information to the navigation unit 106. The GPS information receiving unit 112 includes a GPS signal receiving circuit that receives a GPS signal, and a calculation unit that calculates the vehicle position based on the received GPS signal.

  The operation unit 114 is an input unit for the user to perform various operations on the AVN integrated device 1. Specifically, the operation unit 114 is, for example, a push button switch, a rotation operation switch, a joystick, or the like. The operation unit 114 outputs operation states of various operations by the user to the AVN integrated device 1 to the control unit 100.

  The remote control transmission / reception unit 115 outputs an operation state of an input operation performed on the remote control 116 by the user to the control unit 100. In the present embodiment, the remote controller transmission / reception unit 115 detects a rotation operation, a tilting operation, and a pressing operation on the remote controller 116 by the user.

  The remote control 116 may be a place away from the AVN integrated device 1 main body, for example, near an armrest between a driver seat and a passenger seat, an instrument panel installed on a steering wheel, or the like. The remote control 116 is a rotary encoder that outputs a signal corresponding to the rotation operation amount and direction, a tilt sensor such as a joystick that is configured by a pressure-sensitive sensor and outputs a signal corresponding to the tilt operation direction, and an on / off state is changed by a pressing operation. A pressing switch is provided.

The memory 117 is a memory (storage medium) that stores various data and control programs, and includes, for example, an HDD (Hard Disk Drive), a rewritable flash memory, and the like. Memory 1
17 is controlled by a control signal of the control unit 100 and outputs desired data to a peripheral circuit such as a ROM provided in the control unit 100.

  The camera 119 is, for example, a camera provided at the rear of the vehicle, and outputs a captured video to the external audio / video input unit 118. Note that the captured video may include audio data.

An ETC (Electronic Toll Collection System) in-vehicle device 120 performs wireless communication with an antenna attached to a toll booth and exchanges appropriate toll information in order for a user to pay a highway toll. Note that such operation of the ETC in-vehicle device 120 is controlled by a control signal of the control unit 100.

  The communication unit 121 connects the AVN integrated device 1 to a computer network such as the Internet, and thus performs wireless communication with antennas attached to various places, and transmits and receives data such as packets.

  The display unit 122 displays an image based on the image signal input by the image output unit 110. The display unit 122 includes, for example, a liquid crystal panel 201 such as a liquid crystal display, an organic EL display, a plasma display, a cold cathode flat panel display, a backlight 200 that proves the liquid crystal panel 201 from the back, a resistance film method, and a capacitance method. And the like. The touch panel 202 outputs operation states of various operations by the user to the AVN integrated device 1 to the control unit 100.

  The AVN integrated device 1 is an example of the information processing apparatus in the present embodiment, and does not limit the type of information processing apparatus. The information processing apparatus according to the present embodiment may be, for example, a general-purpose computer that includes one or more processors such as a CPU, and peripheral circuits (ROM, RAM, interface circuit, etc.) used for processing of the processor.

  In addition, the AVN integrated device 1 according to the present embodiment is activated and stopped in accordance with, for example, turning on and off an accessory power supply of an automobile mounted on the vehicle.

§2 First embodiment Next, a first embodiment of the present embodiment will be described.

§2-1 Process configuration First, the process configuration in the first embodiment will be described. The following process configuration, various means, and well-known functions are, for example, that various programs and data stored in the memory 117 or the like are expanded in a RAM or the like, which is a peripheral circuit of the control unit 100, and are controlled by the microcomputer of the control unit 100. This is implemented by controlling each component (external storage medium playback unit 101 and the like).

  FIG. 2 shows an example of a process configuration realized on the AVN integrated device 1 in the first embodiment. As shown in FIG. 2, the AVN integrated device 1 in the first embodiment includes a parent process 50 and a child process 51 as the process configuration.

  The parent process 50 includes a system management thread 50a, management information 50b, a thread A 50c, and a child process management thread 50d as functional configurations. The system management thread 50a includes in-process thread management means 50e. The child process management thread 50d includes child process management means 50f.

  The child process 51 includes a system management thread 51a, management information 50b, a thread B50c, and a child process management thread 51d as functional configurations. The system management thread 51a includes in-process thread management means 51e. The child process management thread 51d includes child process management means 51f.

  The parent process 50, the child process 51, and each thread included in these processes have a well-known function known as a process and a thread function.

  As described above, each of the in-process thread management means (50e, 51e) and each of the child process management means (50f, 51f), for example, stores various programs and data stored in the memory 117 or the like around the control unit 100. This is realized by being expanded in a RAM or the like that is a circuit, executed by the microcomputer of the control unit 100, and controlling each component (external storage medium playback unit 101 and the like). Further, each management information (50b, 51b) is realized by being stored in, for example, the memory 117 or the like and expanded in a RAM or the like that is a peripheral circuit of the control unit 100 when used.

  Hereinafter, the in-process thread management means and the child process management means will be described.

<In-process thread management means>
The in-process thread management means manages the start and stop of threads existing in the process using the management information in accordance with predetermined start factors and stop factors. The management information stores the start and stop factors of threads existing in the process. The in-process thread management means manages the start and stop of the thread existing in the process according to the start and stop factors of the thread stored in the management information.

  For example, the system management thread 50a in the parent process 50 manages the start and stop of the thread A 50c and the child process management thread 50d using the management information 50b by the in-process thread management means 50e.

  For example, the system management thread 51a in the child process 51 manages the start and stop of the thread A 51c and the child process management thread 51d using the management information 51b by the intra-process thread management means 51e.

  An example of the management information is shown in FIG. FIG. 3A shows a record example of the management information 50 b of the parent process 50. FIG. 3B shows a record example of the management information 51b of the child process 51. Each piece of management information is the same as the conventional management information shown in FIG. In other words, each management information record includes a thread name for specifying the thread type, a thread priority indicating the execution priority of each thread, and a stack size indicating the memory size required for storing the thread in the memory. And a field for storing a thread ID for uniquely identifying each thread, and a thread attribute (stop factor) that is a parameter for specifying a thread stop method.

  In this embodiment, a thread priority that determines the priority of execution of each thread is used as a thread activation factor. The thread priority is used to determine which of the threads being executed and waiting is set as the executing thread. In this embodiment, the thread priority is used as the priority of execution and also as the priority of activation (activation factor). That is, in this embodiment, the thread activation factor is that a thread having a higher priority than itself is activated. However, the thread activation factor is not limited to the conditions determined by such a relationship between threads. The thread activation factor may be a condition determined by hardware operation such as operation of the camera 119 included in the AVN integrated device 1. The same applies to the thread stop factor. These starting factors and stopping factors can be arbitrarily determined by storing them in the management information.

  The activation and termination of the system management thread (system management thread 50a, system management thread 51a) provided with the in-process thread management means is managed by the child process management means provided in the child process management thread corresponding to its own parent process.

<Child process management means>
The child process management means manages the start and stop of the system management thread corresponding to its own child process, for example, according to the start and stop factors such as the start instruction and stop instruction for the child process management thread. The starting factor and the stopping factor are arbitrarily determined. For example, activation and stop of a configuration having a hardware configuration (for example, the navigation unit 106) may be set as the activation factor and the deactivation factor. In this embodiment, it is assumed that the start factor and the stop factor are a start command and a stop command for the child process management thread.

  The relationship between the child process management means (child process management thread) and the child process may be one-to-one as shown in FIG. That is, the child process management means (child process management thread) may manage one or more child system management threads.

  Here, when the child process management means executes activation of a system management thread corresponding to its own child process, the system management thread to be activated for the execution needs to be already generated.

  For example, the child process management unit may execute the activation of the system management thread without minding the state of the system management thread to be activated. In this case, an error occurs only when the system management thread to be activated is not generated. Due to this error, the child process management means may recognize that the activation target system management thread has not been generated, and generate and start the activation target system management thread.

  The child process management means recognizes that the activation target system management thread can be activated by, for example, a process state notification from the activation target system management thread, and then activates the activation target system management thread. May be executed. Note that the process state notification is for notifying the state of the process. For example, a system management thread to be started is generated, or all threads in the process including the system management thread to be started are generated. It is notified that it is.

  In this case, for example, each process or thread may be generated by a known function such as an OS. Then, after the system management thread is generated by the known function, the system management thread is, for example, a child process management thread that manages the start and stop of itself when all the threads in the process are generated. Process status notification to The process state notification may be issued at an arbitrary time after the system management thread is generated. The child process management means recognizes that the system management thread to be activated is generated by this process state notification, and that the system management thread to be activated can be activated. Then, for example, the child process management means may execute activation of a system management thread to be activated after the recognition.

  In addition, for example, the child process management means confirms the state of the system management thread to be activated by notification and then activates the system management thread to be activated by a known method such as executing activation of the system management thread to be activated. Execute startup. This also applies to the activation of threads by the above-described in-process thread management means.

In this embodiment, the system management thread to be started remains stopped with respect to the child process management thread that manages its start and stop when all the threads in its own process are generated. , Process state notification is issued. Then, the child process management means executes the activation of the system management thread to be activated after recognizing that the system management thread to be activated is generated and the activation command can be issued by the process state notification. I will do it. Since the process state notification is issued in this way, at the time when the system management thread is generated, all the threads in its own process are generated. Therefore, it is not necessary for the in-process thread management means to confirm that the activation target thread is generated.

  Note that a notification (for example, a process status notification) that is issued to the child process management thread that starts up such a system management thread that is to be started up is referred to as a preparation completion notification. Called.

  On the other hand, when executing the stop of the system management thread corresponding to its own child process, for example, the child process management means stops the system management thread only for the system management thread that has started. When executing the stop, the child process management means does not need to take into consideration such points as the execution of the above-described start. This is because if there is no system management thread to be stopped, the child process management means need not issue a stop command. This also applies to the thread stoppage by the above-mentioned in-process thread management means.

<Others>
In the present embodiment, a system management thread provided with in-process thread management means manages activation and termination of each thread in the process. In addition, a child process management thread provided with a child process management unit manages the start and stop of the system management thread of the child process. Therefore, in the process, a system management thread is a thread that performs management, and other threads are threads that are managed. Further, between processes, a child process management thread of the parent process is a thread that performs management, and a system management thread of a child process of the parent process is managed (see FIG. 2).

  Here, in the present embodiment, the start command and the stop command for the managed thread of the managing thread are realized by notifications of a start request notification and a stop request notification. In the present embodiment, the managing thread sends a start request notification and a stop request notification to the managed thread. The managed thread executes its own start and stop in response to the start request notification and stop request notification. In the present embodiment, the managed thread returns the start completion notification and the stop completion notification for the start request notification and the stop request notification to the managing thread after completing its start and stop. However, these aspects may be any aspects. The method of realizing the start command and the stop command based on these notifications does not limit the present invention.

Note that the activation request notification and the stop request notification used here refer to notification of information related to activation and notification of information related to stop, and may be in any form as long as the information is related thereto. For example, a thread that performs management notifies its own state. Then, the managed thread may be activated or stopped depending on the state of the thread that performs the management. At this time, for example, if the management thread is a system management thread, the start request notification and the stop request notification are realized by a system state notification that notifies the state of the system management thread. Also, for example, if the management thread is a child process management thread, the start request notification and the stop request notification are realized by a process state notification for notifying the state of the parent process. In other words, the start request notification and the stop request notification may be in any form as long as they are notifications used for starting and stopping the managed thread. The same applies to the start completion notification and the stop completion notification. The start completion notification and the stop completion notification indicate notification of information regarding the activation state of the thread and notification of information regarding the stop state, and may be in any form as long as the information is related thereto. The form of each notification does not limit the present invention.

  Further, in the operation example described later, the start request notification and the stop request notification, and the corresponding start completion notification and stop completion notification corresponding thereto are each one notification, but the number of notifications is not limited. For example, each notification may be performed step by step. For example, when a stop request notification is issued from a managing thread to a managed thread, the managed thread sends a stop completion notification according to the stage of its own stop processing to the managing thread. You may send it. In this case, the managing thread can recognize the stepwise state of the managed thread.

  Note that when the child process management thread having the child process management means manages the start and stop of the child process system management thread, the start request notification, the stop request notification, the start completion notification, and the stop completion notification are communicated between processes. It is realized by.

§2-2 Operation Example Next, a management method for starting and stopping each thread in the first embodiment will be described using the following operation example. FIG. 4 is a sequence chart illustrating an example of a procedure for starting a thread according to the first embodiment. FIG. 5 is a sequence chart illustrating an example of a procedure of thread stop processing according to the first embodiment. In these sequence charts, the activation request notification, activation completion notification, stop request notification, and stop completion notification are omitted from the description of activation request, activation completion, stop request, and stop completion, respectively.

  In these sequence charts, the management information used by the in-process thread management means of each system management thread is based on the record example given in FIG. Here, in this embodiment, the thread priority of each management information is higher as the value is smaller. Further, the thread attribute (stop factor) of each thread is arbitrarily set. Here, in order to simplify the explanation, the thread attribute (stop factor) is that the stop instruction is given to the managing thread, and that the thread having a higher start priority than itself is stopped. To do.

  As a premise of these sequence charts, it is assumed that each process and thread has already been generated by a known OS function.

<When starting a thread>
First, the system management thread 50a is activated by an arbitrary method. When the system management thread 50a is activated, the in-process thread management means 50e included in the system management thread 50a refers to the thread priority of the management information 50b (see FIG. 3A for the thread priority). Then, as shown in FIG. 4, the in-process thread management means 50e transmits an activation request notification to the thread A 50c having the highest thread priority (S200). In the present embodiment, as described above, the lower the thread priority value, the higher the priority.

  When the thread A 50 c receives the activation request notification, the thread A 50 c executes its own activation. When the activation of the thread A 50c is completed, the thread A 50c returns an activation completion notification to the system management thread 50a (S201).

When the activation completion notification is received from the thread A 50c, the in-process thread management means 50e
Refers to the thread priority of the management information 50b again. Then, as shown in FIG. 4, the in-process thread management unit 50e transmits an activation request notification to the child process management thread 50d having the highest thread priority next to the thread A 50c in the management information 50b (S202). .

  When the child process management thread 50d receives the activation request notification, the child process management thread 50d executes its own activation. When the activation of itself is completed, an activation completion notification is returned to the system management thread 50a (S203).

  Here, it is assumed that the child process 51 and the thread included in the child process 51 have already been generated. At this time, the system management thread 51a transmits a preparation completion notice to the child process management thread 50d while stopping itself (S204). The preparation completion notification is, for example, a process state notification as described above.

  After receiving the preparation completion notification, the child process management means 50f of the child process management thread 50d that has been started up transmits a start request notification to the system management thread 51a of the child process 51 that is its own child process (S205). ).

  When receiving the activation request notification, the system management thread 51a executes its own activation. When the activation of itself is completed, the system management thread 51a returns an activation completion notification to the child process management thread 50d (S206).

  The in-process thread management unit 51e of the system management thread 51a that has been activated refers to the thread priority of the management information 51b (see FIG. 3B for the thread priority). Then, as shown in FIG. 4, the in-process thread management unit 51e transmits an activation request notification to the child process management thread 51d (S207).

  When the child process management thread 51d receives the activation request notification, the child process management thread 51d executes its own activation. When the activation of itself is completed, an activation completion notification is returned to the system management thread 51a (S208).

  Similarly to the above, it is assumed that a child process (not shown) managed by the child process management thread 51d and a thread included in the child process have already been generated. Then, a preparation completion notification is transmitted from the system management thread of the child process to the child process management thread 51d (S209).

  After receiving the preparation completion notification, the child process management means 51f of the child process management thread 51d that has been activated transmits an activation request notification to the system management thread of the child process (not shown) that is its own child process. (S210). When the system management thread (not shown) receives the activation request notification, it executes its own activation. When the startup of itself is completed, the system management thread (not shown) returns a startup completion notification to the child process management thread 50d (S211).

  When the start completion notification is received from the child process management thread 51d, the in-process thread management means 51e refers to the thread priority of the management information 51b again. Then, as shown in FIG. 4, the in-process thread management means 51e transmits an activation request notification to the thread B 51c having the highest thread priority next to the child process management thread 51d in the management information 51b (S212). .

When the thread B 51c receives the activation request notification, the thread B 51c executes its own activation. When the activation of the thread B 51c is completed, the thread B 51c returns an activation completion notification to the system management thread 51a (S213).

  As described above, activation of all threads existing in the parent process 50 and the child process 51 is completed.

  Note that these processing orders are merely examples, and other orders may be used. For example, in the sequence chart, the processing of S212 is performed after the processing of S209 to S211 is performed, but the processing of S212 and the processing of S209 to S211 may be performed in parallel. Further, for example, the preparation completion notification in S204 and S209 may be performed before S200. Further, for example, the process of S203 and the processes after S205 may be mixed. The order of processing in the above sequence chart does not limit the present invention. The same applies to each sequence chart that appears below.

<When thread is stopped>
For example, it is assumed that the threads of the parent process 50 and the child process 51 are activated after the above processing <when thread is activated>. In this situation, it is assumed that the system management thread 50a of the parent process 50 receives a stop request notification from a predetermined target (for example, a child process management unit included in a child process management thread of the parent process 50).

  At this time, the in-process thread management means 50e included in the system management thread 50a refers to the thread attribute of the management information 50b. The thread attribute is arbitrarily set. Here, as described above, it is assumed that the thread attribute is that a stop instruction has been given to the thread to be managed, and that a thread having a higher activation priority than itself is stopped. Therefore, as shown in FIG. 5, the in-process thread management unit 50e first transmits a stop request notification to the thread A 50c having the highest activation priority (S300).

  When the thread A 50 c receives the stop request notification, the thread A 50 c executes its own stop. When the thread A50c completes its own stop, the thread A50c returns a stop completion notification to the system management thread 50a (S301).

  When the in-process thread management unit 50e of the system management thread 50a receives the stop completion notification from the thread A 50c, it again refers to the thread attribute of the management information 50b. Then, as shown in FIG. 5, the in-process thread management means 50e transmits a stop request notification to the child process management thread 50d having the next highest activation priority after the thread A 50c (S302).

  When the child process management thread 50d receives the stop request notification from the in-process thread management means 50e, the child process management thread 50d starts its own stop. The child process management means 50f of the child process management thread 50d transmits a stop request notification to the system management thread 51a of the child process 51 in response to the stop request notification (S303).

  When the in-process thread management unit 51e of the system management thread 51a receives the stop request notification from the child process management thread 50d, the process management thread 51a refers to the thread attribute of the management information 51b. Then, as shown in FIG. 5, the in-process thread management unit 51e transmits a stop request notification to the child process management thread 51d having the highest priority according to the thread attribute (S304).

When the child process management thread 51d receives the stop request notification from the in-process thread management means 51e, it starts to stop itself. In response to the stop request notification, the child process management means 50f of the child process management thread 51d transmits a stop request notification to a system management thread of a child process (not shown) that manages its start and stop (S305). ).

  When the stop of the child process (not shown) is completed, the child process management thread 51d receives a stop completion notification from the system management thread of the child process (not shown) (S306).

  The child process management thread 51d completes its own stop in response to the stop of a child process (not shown) that manages the start and stop. Then, after completing the stop of itself, the child process management thread 51d returns a stop completion notification to the system management thread 51a (S307).

  When the in-process thread management means 51e of the system management thread 51a receives the stop completion notification from the child process management thread 51d, it again refers to the thread attribute of the management information 51b. Then, as shown in FIG. 5, the in-process thread management means 51e transmits a stop request notification to the thread B 51c with the highest priority of activation next to the child process management thread 51d (S308).

  When the thread B51c receives the stop request notification, the thread B51c executes its own stop. Then, when the thread B 51c is completely stopped, the thread B 51c returns a stop completion notification to the system management thread 51a (S309).

  When the in-process thread management means 51e of the system management thread 51a receives the stop completion notification from the child process management thread 51d, it again refers to the thread attribute of the management information 51b. Then, when there are no more targets to be stopped, the system management thread 51a completes its own stop, and returns a stop completion notification to the child process management thread 50d as shown in FIG. 5 (S310).

  In response to the stop completion notification from the system management thread 51a, the child process management thread 51d completes its own stop and transmits a stop completion notification to the system management thread 50a (S311).

  When the in-process thread management means 50e of the system management thread 50a receives the stop completion notification from the child process management thread 50d, it again refers to the thread attribute of the management information 50b. Then, when there are no more targets to be stopped, the system management thread 50a completes its own stop.

  As described above, the stop of all threads existing in the parent process 50 and the child process 51 is completed.

§2-3 Actions and effects of the first embodiment As described above, the start and stop management of the thread in the first embodiment is performed within the process of the system management thread provided in the process. This is done by thread management means. In addition, the start and stop management of the system management thread that manages the start and stop of the threads in the process is performed by the child process management means of the child process management thread of the parent process.

As a result, in the first embodiment, the start and stop of the thread in the process can be managed by a method similar to the system design and construction by a simple method in the conventional control method using tasks. Therefore, the first embodiment enables simple system design and construction.

  In the first embodiment, inter-process communication is limited to communication performed between a child process management thread including a child process management unit and a system management thread. Therefore, the first embodiment can suppress inter-process communication that occurs when managing the start and stop of each thread as much as possible.

  In addition, the thread activation and management method in the process performed by the in-process thread management means of the system management thread is the same for the process including the system management thread. Therefore, in the first embodiment, by providing the system management thread in each process, the thread management method in each process can be made the same.

  In addition, the method for managing the start and stop of the thread in the process performed by the in-process thread management means of the system management thread is the same management method as the control method by the conventional task, and it is easy to port the conventional technique. It is.

§3 Second embodiment Next, a second embodiment of the present embodiment will be described. The second embodiment is an embodiment using Windows Automotive 5.5, which is an example of a well-known OS, in the AVN integrated machine 1 which is an example of an information processing apparatus according to the present embodiment. The second embodiment is also an example in which the first embodiment is applied to the AVN integrated device 1 using the OS (Windows Automotive 5.5).

§3-1 Process configuration First, a process configuration according to the second embodiment will be described with reference to FIGS. 6 and 7. The following process configuration, various functional configurations, various means, and well-known functions are, for example, various programs and data stored in the memory 117 or the like are expanded in a RAM or the like that is a peripheral circuit of the control unit 100. It is executed by the microcomputer of the control unit 100 and controlled by each component (external storage medium playback unit 101 and the like). This is the same as in the first embodiment. In FIG. 6 to FIG. 13, “thread” for each thread is omitted.

<Functional configuration>
FIG. 6 shows an example of a functional configuration and a process configuration realized on the AVN integrated device 1 in the second embodiment. As shown in FIG. 6, the AVN integrated device 1 according to the second embodiment includes a snapshot control unit 2a, a snapshot holding unit 2b, a ReadyGuard process control unit 3a, and a ReadyGuard process holding unit 3b as the functional configuration. . Note that, as described above, the snapshot control unit 2a and the ReadyGuard process control unit 3a control various programs and data stored in the memory 117 or the like on a RAM or the like that is a peripheral circuit of the control unit 100, for example. The program is executed by the microcomputer of the unit 100 and is realized by controlling each component (external storage medium playback unit 101 and the like). In addition, the snapshot holding unit 2b and the ReadyGuard process holding unit 3b are realized by, for example, a nonvolatile memory included in the memory 117 or the like.

  The snapshot control unit 2a realizes a function of Windows Automotive 5.5 called snapshot boot. Snapshot boot saves the system state (memory contents, OS state, etc.) at any point during system startup as a snapshot in non-volatile memory, and restores the saved system state at system startup. This function shortens the startup time by booting.

  The snapshot holding unit 2b stores the above-described snapshot. As will be described later, in this embodiment, the ReadyGuard process 4 is booted by the ReadyGuard process control unit 3a in response to the activation of the AVN integrated device 1 (for example, accessory power-on). Therefore, in the present embodiment, the snapshot stored in the snapshot holding unit 2b is generated by the MAIN process 5, the X process 6, the Y process 7, and the threads included in these processes, excluding the ReadyGuard process 4. It is assumed that the system state at the time of being released. However, the stored snapshot may be in the system state at an arbitrary time. The stored snapshot is not a limitation of the present invention.

  Note that the snapshot control unit 2a may acquire a snapshot from the snapshot holding unit 2b and develop the snapshot in the RAM or the like of the control unit 100 at any time. In this embodiment, when the ReadyGuard process 4 and each thread in the process are activated, the snapshot control unit 2a expands the snapshot in the RAM of the control unit 100 or the like. Further, the snapshot control unit 2a recognizes the time point by a notification from the system management thread 4a.

  The ReadyGuard process control unit 3a and the ReadyGuard process holding unit 3b realize activation of the ReadyGuard process 4 in response to activation of the AVN integrated device 1 (for example, accessory power-on). The ReadyGuard process holding unit 3b stores a ReadyGuard process 4. Then, the ReadyGuard process control unit 3a acquires the ReadyGuard process 4 from the ReadyGuard process holding unit 3b in response to the activation of the AVN integrated device 1, and develops the ReadyGuard process 4 in the RAM of the control unit 100 or the like. Then, the ReadyGuard process control unit 3a starts the ReadyGuard process 4. This is an operation for realizing a known function called ReadyGuard.

  Here, a well-known function called ReadyGuard will be briefly described. Windows Automotive 5.5 has a function called ReadyGuard. With ReadyGuard, if a failure occurs on the system, the rest of the system (other software including the OS) will not be rebooted and the operation of the high-reliability software defined in advance will be continued. This is a technology that provides a mechanism for restarting.

  In ReadyGuard, in order to realize this mechanism, ReadyGuardOS is first activated, and then the main OS is activated. The ReadyGuard OS reserves a static area (static area) for operating highly reliable software configured by a fixed process and a fixed thread as a structure. Thereafter, control of the structure is handed over to the main OS. As described above, when the OS includes an OS (ReadyGuardOS) that guarantees the operation of the high-reliability software, ReadyGuard has a mechanism for restarting the remaining part (other software including the main OS). Realize.

  In this embodiment, the process corresponding to the ReadyGuard OS is the ReadyGuard process 4, and the process corresponding to the main OS is the MAIN process 5.

  Further, in this embodiment, the ReadyGuard process control unit 3a executes the stop of the ReadyGuard process 4 based on the stop of the AVN integrated device 1 (for example, accessory power off).

<Process configuration>
As shown in FIG. 6, the AVN integrated device 1 in the second embodiment includes a ReadyGuard process 4, a MAIN process 5, an X process 6, and a Y process 7 as the process configuration. FIG. 7 illustrates the details of the process configuration in FIG.

  As shown in FIG. 7, the ReadyGuard process 4 includes a system management thread 4a including an in-process thread management unit 4e, a management information 4b, a PLATFORM control thread 4c, and a MAIN process management thread 4d including a child process management unit 4f. Prepare.

  Further, as shown in FIG. 7, the MAIN process 5 includes a system management thread 5a having in-process thread management means 5f, management information 5b, an X process management thread 5c having child process management means 5g, and a child process management means. Y process management thread 5d provided with 5h, and A control thread 5e.

  Further, as shown in FIG. 7, the X process 6 includes a system management thread 6a including in-process thread management means 6e, management information 6b, a B control thread 6c, and a C control thread 6d.

  Further, as shown in FIG. 7, the Y process 7 includes a system management thread 7a including in-process thread management means 7d, management information 7b, and a D control thread 7c.

  The system management threads (4a, 5a, 6a, 7a) included in each process include the same functions as the system management threads in the first embodiment. That is, each in-process thread management means (4e, 5f, 6e, 7d) has the same function as the in-process thread management means in the first embodiment.

  Each process management thread (4d, 5c, 5d) included in each process includes the same function as the child process management thread in the first embodiment. That is, each child process management means (4f, 5g, 5h) has the same function as the child process management means in the first embodiment.

  Each management information (4b, 5b, 6b, 7b) includes the same data as the management information in the first embodiment. FIG. 8A is a record example as an example of the management information 4b. FIG. 8B is a record example as an example of the management information 5b. FIG. 8C is a record example as an example of the management information 6b. FIG. 8D is a record example as an example of the management information 7b.

  The other threads (4c, 5e, 6c, 6d, 7c) are arbitrary threads.

  For example, in a state where a thread repeats starting and stopping (chattering), when trying to manage the starting and stopping of the thread, the managing thread must stop during starting or start during stopping. I must. At this time, since management according to the state of the thread (for example, in which stage the activation is) must be performed, the management process becomes complicated. In order to prevent this management process from becoming complicated, in the second embodiment, when the MAIN process system management thread 4a manages a thread to be managed, a start instruction or a stop instruction for the thread is not issued. After completion, the next management (start command or stop command) is performed (handshake).

  In the second embodiment, it is assumed that all processes executed on the AVN integrated device 1 have a tree structure. Note that the process or thread executed on the AVN integrated device 1 may be dynamically generated. The generation of the process and the generation of the thread are performed by a well-known method. For example, when a child process is generated, a system management thread is generated in the child process and a child process management thread for managing start and stop of the child process is generated in the parent process by the known method. Good. For example, when a thread is generated, the management information of the thread may be registered in the management information by the known method. As a result, all processes have a tree structure, and the process and thread configurations shown in FIGS. 6 and 7 are maintained.

  In the second embodiment, it is assumed that the AVN integrated device 1 executes a snapshot generation process for storing in the snapshot holding unit 2b. As described above, the generated snapshot is the system state at the time when the MAIN process 5, the X process 6, the Y process 7, and the threads included in these processes are generated.

  The snapshot generation processing is realized by, for example, a well-known function of the OS executed on the AVN integrated device 1, the system management thread of each process, and the snapshot control unit 2a. For example, a process for acquiring a snapshot and a system management thread are generated by a known function of the OS. Then, the generated system management thread generates each thread (thread to be managed) based on the management information by the in-process system management means. At the time when all processes and threads are generated, the snapshot control unit 2a displays the state of each process and thread (specifically, the memory state developed in the RAM or the like that is a peripheral circuit of the control unit 100). Stored in the snapshot holding unit 2b. The in-process system management unit generates each thread in an arbitrary order.

  In order for the snapshot control unit 2a to recognize that all the processes and threads have been generated, in the second embodiment, the system management thread of the MAIN process manages that other processes and threads have been generated. It shall be. At this time, for example, the system management thread of each process except the MAIN process notifies the system management thread of the MAIN process that its own process and each thread have been generated. In response to the notification, the system management thread of the MAIN process notifies the snapshot control unit 2a that the preparation for storing the snapshot is complete. Thus, the snapshot control unit 2a recognizes that all processes and threads have been generated.

§3-2 Operation Example Next, a management method for starting and stopping each thread in the second embodiment will be described using the following operation example. FIG. 9 is a sequence chart illustrating an example of a snapshot acquisition processing procedure according to the second embodiment. FIG. 10 is a sequence chart showing an example of the activation processing procedure of each thread in the second embodiment. FIG. 11 is a sequence chart illustrating an example of a thread stop processing procedure according to the second embodiment. FIG. 12 shows that in the second embodiment, the AVN integrated device 1 is stopped before the snapshot is expanded (loaded) into the RAM or the like that is a peripheral circuit of the control unit 100, and then the AVN integrated device 1 is started. It is the sequence chart which showed an example of the process sequence at the time. FIG. 13 is a sequence chart showing an example of a processing procedure when the AVN integrated device 1 is activated while a certain thread is stopped in the second embodiment. In these sequence charts, the activation request notification, activation completion notification, stop request notification, and stop completion notification are omitted from the description of activation request, activation completion, stop request, and stop completion, respectively.

The management information used by the in-process system management means included in each system management thread is premised on the management information shown in FIG. Also, the description of the starting procedure and stopping procedure of each thread that is the same as that of the first embodiment will be simplified.

<When taking a snapshot>
First, an example of a processing procedure when acquiring a snapshot shown in FIG. 9 will be described.

  As described above, the MAIN process 5, the X process 6, the Y process 7, and the system management thread (5a, 6a, 7a) of each process are generated by the well-known functions of the OS, and the peripheral circuit of the control unit 100 It is developed in a RAM or the like.

  As shown in FIG. 9, the system management thread of each process generates threads in its own process based on, for example, management information (5b, 6b, 7b) (S401, S402, S403, S405, S406, S408). The operation may be asynchronous.

  Thereafter, the system management threads (6a, 7a) of the X process 6 and the Y process 7 notify the system management thread 5a of the MAIN process 5 that its own process and each thread have been generated (S407, S409). ).

  When the system management thread 5a of the MAIN process 5 completes generation of its own thread and receives the notification from the system management threads (6a, 7a) of the X process 6 and the Y process 7, it notifies the snapshot control unit 2a. To notify that the nap shot is ready to be stored. The snapshot control unit 2a recognizes that all processes and threads have been generated by the notification from the system management thread 5a of the MAIN process 5, and at this point in time, the system state (such as a RAM that is a peripheral circuit of the control unit 100) Is stored in the snapshot holding unit 2b as a snapshot.

  As described above, the snapshot in the second embodiment is acquired.

<When starting a thread>
Next, an example of a processing procedure when starting each thread shown in FIG. 10 will be described.

  First, when the AVN integrated device 1 is activated, the ReadyGuard control unit 3 a expands the ReadyGuard process 4 stored in the ReadyGuard holding unit 3 b and the threads in the process to a RAM or the like that is a peripheral circuit of the control unit 100. Then, the ReadyGuard control unit 3 a activates the system management thread 4 a of the ReadyGuard process 4.

  After the activation, as shown in FIG. 10, the in-process system management unit 4e included in the system management thread 4a of the ReadyGuard process 4 activates each thread (4c, 4d) based on the thread priority of the management information 4b. Are executed (S500 to S503). For example, as shown in FIG. 10, the in-process system management unit 4e included in the system management thread 4a transmits an activation request notification to each thread (4c, 4d) based on the management information 4b (S500, S502). ). Each thread (4c, 4d) returns a start completion notification to the system management thread 4a after the start is completed (S501, S503). Hereinafter, since the response of the activation request notification and the activation completion notification is the same as that of the first embodiment, description thereof is omitted.

After starting each thread (4c, 4d), the system management thread 4a of the ReadyGuard process 4 notifies the snapshot control unit 2a that all threads have been started. In response to the notification, the snapshot control unit 2a
The snapshot (system state) stored in b is expanded in a RAM, which is a peripheral circuit of the control unit 100 (S504). Note that the system state in the second embodiment is a state in which the MAIN process 5, the X process 6, the Y process 7, and each thread in each process are generated as described above.

  When the loading of the snapshot is completed, the system management thread 5a of the MAIN process 5 transmits a preparation completion notification to the MAIN process management thread 4d (S505).

  After receiving the preparation completion notification, the child process management means 4f included in the MAIN process management thread 4d of the ReadyGuard process 4 executes activation of the system management thread 5a of the MAIN process 5 (S506, S507).

  The in-process system management means 5f included in the activated system management thread 5a executes activation of each thread (5c, 5d, 5e) based on the thread priority of the management information 5b (S508, S509, S517, S518). , S524, S525).

  The child process management means 5g included in the X process management thread 5c activated by the in-process system management means 5f, the system of the X process 6 based on the preparation completion notification (S510) from the system management thread 6a of the X process 6. The management thread 6a is activated (S511, S512).

  The system management thread 6a of the X process 6 activated by the child process management means 5g executes activation of each thread (6c, 6d) based on the thread priority of the management information 6b (S513 to S516).

  Further, the child process management means 5h included in the Y process management thread 5d activated by the in-process system management means 5f sends the Y process 7 based on the preparation completion notification (S519) from the system management thread 7a of the Y process 7. The system management thread 7a is activated (S520, S521).

  The system management thread 7a of the Y process 7 activated by the child process management means 5h executes activation of the D control thread 7c based on the thread priority of the management information 7b (S522, S523).

  Thus, the activation of all existing processes and threads is completed.

<When thread is stopped>
Next, an example of a processing procedure when each thread shown in FIG. 11 is stopped will be described.

  As in the first embodiment, it is assumed that each process and each thread are activated after the above processing <when thread is activated>.

  For example, the ReadyGuard process control unit 3 a starts to stop the ReadyGuard process 4 when the user turns off the accessory power supply to the AVN integrated device 1.

  In accordance with the operation of the ReadyGuard process control unit 3a, the in-process thread management unit 4e included in the system management thread 4a of the ReadyGuard process 4 stops each thread (4c, 4d) based on the thread attribute of the management information 4b. To start.

  First, the in-process thread management unit 4e executes the stop of the PLATFROM control thread 4c based on the thread attribute of the management information 4b (S601, S602).

  Next, the in-process thread management unit 4e stops the MAIN process management thread 4d based on the thread attribute of the management information 4b (S603 to S622).

  The stop of the MAIN process management thread 4d is started by a stop request notification from the in-process thread management means 4e (S603). Then, in response to the stop request notification, the child process management means 4f of the MAIN process management thread 4d transmits a stop request notification to the system management thread 5a of the MAIN process 5 managed by itself, and stops the process and the thread. Start (S604).

  When the stop request notification is received from the child process management unit 4f, the in-process thread management unit 5f of the system management thread 5a executes the stop of each thread (5c, 5d, 5e) based on the thread attribute of the management information 5b. (S605-S620).

  First, the intra-process thread management means 5f executes the stop of the X process management thread 5c based on the thread attribute of the management information 5b (S605 to S612).

  The in-process thread management means 5f transmits a stop request notification to the X process management thread 5c (S605). When the stop request notification is received, the child process management means 5g of the X process management thread 5c transmits a stop request notification to the system management thread 6a of the X process 6 (S606).

  The system management thread 6a (in-process thread management means 6e) of the X process 6 stops each thread (6c, 6d) managed by itself based on the management information 6b in response to a stop request notification from the child process management means 5g. Are executed (S607 to S610). When the stop of each thread (6c, 6d), the stop of the system management thread 6a, and the stop of the X process 6 are completed, the system management thread 6a returns a stop completion notification to the X process management thread 5c (S611). .

  When receiving the stop completion notification from the system management thread 6a, the X process management thread 5c stops itself and returns a stop completion notification to the system management thread 5a (S612).

  As described above, the in-process thread management unit 5f completes the stop of the X process management thread 5c based on the thread attribute of the management information 5b (S605 to S612).

  Next, the in-process thread management unit 5f executes the stop of the Y process management thread 5d based on the thread attribute of the management information 5b (S613 to S618).

  The in-process thread management unit 5f transmits a stop request notification to the Y process management thread 5d (S613). When the stop request notification is received, the child process management means 5h of the Y process management thread 5d transmits a stop request notification to the system management thread 7a of the Y process 7 (S614).

The system management thread 7a (in-process thread management means 7d) of the Y process 7 executes the stop of the D control thread 7c managed by itself based on the management information 7b in response to the stop request notification from the child process management means 5h. (S615, S616). When the stop of the D control thread 7c, the stop of the system management thread 7a, and the stop of the Y process 7 are completed, the system management thread 7a returns a stop completion notification to the Y process management thread 5d (S617).

  When receiving the stop completion notification from the system management thread 7a, the Y process management thread 5d stops itself and returns a stop completion notification to the system management thread 5a (S618).

  As described above, the in-process thread management unit 5f completes the stop of the Y process management thread 5d based on the thread attribute of the management information 5b (S613 to S618).

  Finally, the in-process thread management unit 5f executes the stop of the A control thread 5e based on the thread attribute of the management information 5b (S619 to S620).

  When the stop (5c, 5d, 5e) of each thread is completed, the system management thread 5a stops itself and the MAIN process 5, and returns a stop completion notification to the MAIN process management thread 4d (S621).

  When receiving the stop completion notification from the system management thread 5a, the MAIN process management thread 4d stops itself and returns a stop completion notification to the system management thread 4a (S622).

  As described above, the in-process thread management unit 4e completes the stop of the MAIN process management thread 4d based on the thread attribute of the management information 4b (S603 to S622). Thereafter, the system management thread 4a stops itself and the ReadyGuard process 4.

  This completes stopping all existing processes and threads.

<After starting, stop and start again>
Next, an example of a processing procedure shown in FIG. 12 when the AVN integrated device 1 is stopped before the snapshot is loaded and then the AVN integrated device 1 is started will be described.

  First, as in the above <Thread activation>, when the AVN integrated device 1 is activated by the user (for example, the accessory power is turned on), the ReadyGuard control unit 3a causes the ReadyGuard process 4 stored in the ReadyGuard holding unit 3b and Threads in the process are expanded in a RAM or the like that is a peripheral circuit of the control unit 100. Then, the ReadyGuard control unit 3 a activates the system management thread 4 a of the ReadyGuard process 4.

  After the activation, as shown in FIG. 12, the in-process system management means 4e included in the system management thread 4a of the ReadyGuard process 4 activates each thread (4c, 4d) based on the thread priority of the management information 4b. Are executed (S700 to S703).

After starting each thread (4c, 4d), the system management thread 4a of the ReadyGuard process 4 notifies the snapshot control unit 2a that all threads have been started. In response to the notification, the snapshot control unit 2a develops the snapshot (system state) stored in the snapshot holding unit 2b in a RAM or the like that is a peripheral circuit of the control unit 100 (S704). The system state in the second embodiment is
As described above, the MAIN process 5, the X process 6, the Y process 7, and each thread in each process are generated.

  At this time, it is assumed that the user turns off the accessory power supply of the AVN integrated device 1 (ACC-OFF) (S705).

  The ReadyGuard control unit 3a starts to stop the ReadyGuard process 4 in response to the accessory power supply being turned off. In response to the operation of the ReadyGuard control unit 3a, the in-process thread management means 4e included in the system management thread 4a of the ReadyGuard process 4 stops each thread (4c, 4d) based on the thread attribute of the management information 4b. Start.

  First, the in-process thread management unit 4e executes the stop of the PLATFROM control thread 4c based on the thread attribute of the management information 4b (S706, S707).

  Next, the in-process thread management unit 4e executes the stop of the MAIN process management thread 4d based on the thread attribute of the management information 4b (S708 to S710).

  The in-process thread management unit 4e transmits a stop request notification to the MAIN process management thread 4d (S708).

  When the stop request notification is received from the in-process thread management unit 4e, the child process management unit 4f of the MAIN process management thread 4d executes the stop of the MAIN process 5, which is a child process. However, until the snapshot is expanded to the RAM or the like that is a peripheral circuit of the control unit 100, the stop target does not exist in the RAM or the like. In this case, the child process management unit 4f waits for a preparation completion notification from the system management thread 5a (S709), and stops the MAIN process 5 that is the target of the stop. In this case, since the MAIN process 5 is only developed in the RAM or the like that is a peripheral circuit of the control unit 100 and is not activated, the child process management unit 4f does not operate at all.

  Thereafter, the MAIN process management thread 4d returns a stop completion notification to the system management thread 4a (S710).

  At this time, it is assumed that the user turns on the accessory power supply of the AVN integrated device 1 again (ACC-ON) (S711).

  Since the ReadyGuard process 4 and the threads in the process are already deployed in a stopped state in the RAM or the like that is a peripheral circuit of the control unit 100, the ReadyGuard control unit 3a activates the system management thread 4a of the ReadyGuard process 4. .

  After the activation, the in-process system management unit 4e included in the system management thread 4a of the ReadyGuard process 4 executes activation of each thread (4c, 4d) based on the thread priority of the management information 4b (S712 to S715). ). The same as described above.

  At this point, since the snapshot has already been loaded and the preparation completion notification has already been received (S709), the child process management means 4f included in the MAIN process management thread 4d of the ReadyGuard process 4 has the MAIN process 5 The system management thread 5a is activated (S716, S717).

The subsequent activation of each thread is the same as the processing after S508 in FIG. With these processes, activation of each process and each thread is completed.

<When activated while the thread is stopped>
Finally, an example of a processing procedure when the AVN integrated device 1 is activated while a certain thread (system management thread 6a) shown in FIG. 13 is stopped will be described.

  For example, the ReadyGuard process control unit 3 a starts to stop the ReadyGuard process 4 when the user turns off the accessory power supply to the AVN integrated device 1.

  In accordance with the operation of the ReadyGuard process control unit 3a, the in-process thread management unit 4e included in the system management thread 4a of the ReadyGuard process 4 stops each thread (4c, 4d) based on the thread attribute of the management information 4b. To start.

  Here, the processing from when the in-process thread management unit 4e stops the PLATFROM control thread 4c until the in-process thread management unit 6e completes the stop of the B control thread 6c (S801 to S808). Is the same as the processing from S601 to S608 in FIG.

  At this time, it is assumed that the user turns on the accessory power supply of the AVN integrated device 1 (ACC-ON) (S809).

  Since the ReadyGuard process 4 and the threads in the process are already deployed in a stopped state in the RAM or the like that is a peripheral circuit of the control unit 100, the ReadyGuard control unit 3a activates the system management thread 4a of the ReadyGuard process 4. .

  After the activation, the in-process system management unit 4e included in the system management thread 4a of the ReadyGuard process 4 executes activation of each thread (4c, 4d) based on the thread priority of the management information 4b (S810 to S813). ).

  At this time, the stop of each process (MAIN process 5, X process 6, Y process 7) is not completed. For this reason, each process and each thread in each process are already developed in a RAM or the like that is a peripheral circuit of the control unit 100. Therefore, the child process management means 4f included in the MAIN process management thread 4d of the ReadyGuard process 4 executes the activation of the system management thread 5a of the MAIN process 5 (S814, S815).

  When the system management thread 5a of the MAIN process 5 is activated, it attempts to activate the X process management thread 5c by the in-process thread management means 5f based on the management information 5b. At this time, since the preceding stop instruction for the X process management thread 5c has not been completed, the in-process thread management means 5f waits for the completion of the preceding stop instruction to perform the handshake.

  At this time, a stop instruction is continuously executed in the X process 6 (S816, S817). When the in-process thread management means 6e of the system management thread 6a completes the stop of each thread (6c, 6d), the system management thread 6a returns a stop completion notification to the X process management thread 5c (S818). When receiving the stop completion notification from the system management thread 6a, the X process management thread 5c returns a stop completion notification to the system management thread 5a (S819). Thereby, the preceding stop instruction is completed.

  When the preceding stop command is completed, the in-process thread management unit 5f of the system management thread 5a executes the activation of the X process management thread 5c based on the thread priority of the management information 5b (S820, S821).

  The process related to activation of the X process management thread 5c (S820 to S827) is the same as the process in which the processes of S508 to S516 to S510 in FIG. 10 are omitted. As described above, since each process (MAIN process 5, X process 6, Y process 7) and each thread in each process have already been developed in a RAM or the like that is a peripheral circuit of the control unit 100, S510 (The preparation completion notification from the system management thread 6a to the X process management thread 5c) is omitted.

  Thus, the activation of all existing processes and threads is completed.

§3-3 Actions and effects of second embodiment As described above, the second embodiment can obtain at least the same actions and effects as those of the first embodiment.

  That is, the start and stop management of the thread in the second embodiment is performed in the process by the in-process thread management means (4e, 5f, 6e, 7d) of the system management thread provided in the process. . Management of the start and stop of the system management thread that manages the start and stop of the threads in the process is performed by the child process management means (4f, 5g, and 5h) of the parent process.

  Thereby, in the second embodiment, the start and stop of the thread in the process can be managed by the same method as the system design and construction by the simple method in the control method by the conventional task. Therefore, the second embodiment enables a simple system design and construction.

  In the second embodiment, inter-process communication is limited to communication performed between a child process management thread (4d, 5c, 5d) including a child process management unit and a system management thread (5a, 6a, 7a). It is done. Therefore, the second embodiment can suppress inter-process communication that occurs when managing the start and stop of each thread as much as possible.

  Further, the method for managing the start and stop of the thread in the process performed by the in-process thread management means (4e, 5f, 6e, 7d) of the system management thread is the same for the process including the system management thread. Therefore, in the first embodiment, by providing the system management thread in each process, the thread management method in each process can be made the same.

  Also, unlike the first embodiment, the second embodiment executes the above-described process and thread activation and termination based on activation and termination of the apparatus (AVN integrated device 1). Accordingly, the second embodiment can manage processes and threads according to the operation of the apparatus.

  The second embodiment differs from the first embodiment in that all processes executed in the apparatus form a tree structure and are therefore subject to management. As a result, the effects described above can be obtained for all processes executed in the apparatus.

§4 Supplement Although the embodiment of the present invention has been described in detail above, the above description is merely an example of the present invention in all respects and is not intended to limit the scope thereof. It goes without saying that various improvements and modifications can be made without departing from the scope of the present invention. The scope of the present invention is construed only by the claims. Moreover, those skilled in the art can implement an equivalent range from the description of the present embodiment based on the description of the claims and the common general technical knowledge. Moreover, the term used in this specification is used by the meaning normally used in the said field unless there is particular mention. Thus, unless defined otherwise, all technical and technical terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this invention belongs. In case of conflict, the present specification, including definitions, will control.

  In the above description, an embodiment of the information processing apparatus according to the present invention has been described. However, an embodiment of the information processing method according to the present invention can be described in the same manner. That is, a procedure in which each process of the information processing apparatus is a step is an embodiment of the information processing method according to the present invention.

DESCRIPTION OF SYMBOLS 1 AVN integrated machine 2a Snapshot control part 2b Snapshot holding | maintenance part 3a ReadyGuard process control part 3b ReadyGuard process holding | maintenance part 4 ReadyGuard process 4a R system management thread 4b Management information 4c PLATFORM control thread 4d MAIN process management thread 4e 4f Child process management means 5 MAIN process 5a M system management thread 5b Management information 5c Y process management thread 5d Z process management thread 5e A control thread 5f In-process thread management means 5g Child process management means 6 X process 6a X system management thread 6b Management information 6c B control thread 6d C control thread 6e In-process thread management means 7 Y process 7a Y system management threads 7b management information 7c D control 7d process in a thread management unit 50 parent 50a System Management thread 50b management information 50c Thread A
50d Child process management thread 50e In-process thread management means 50f Child process management means 51 Child process 51a System management thread 51b Management information 51c Thread B
51d Child process management thread 51e In-process thread management means 51f Child process management means 100 Control unit 101 External storage medium playback unit 102 Radio reception unit 103 TV reception unit 104 Disc playback unit 105 HD playback unit 106 Navigation unit 107 Distribution circuit 108 Image adjustment Circuit 109 Audio adjustment circuit 110 Image output unit 111 VICS information reception unit 112 GPS information reception unit 113 Selector 114 Operation unit 115 Remote control transmission / reception unit 116 Remote control 117 Memory 118 External audio / video input unit 119 Camera 120 ETC in-vehicle 121 Communication unit 122 Display unit 123 Speaker 200 Backlight 201 Liquid Crystal Panel 202 Touch Panel

Claims (5)

When running a program in the information processing apparatus, a plurality of processes is a runtime environment that is distinguished from each other has become a parent-child relationship by a tree structure, in the information processing apparatus in which a plurality of threads are executed in each process There ,
The parent process, and a control unit for executing a child process started and stopped by the parent process is managed,
A storage unit to which an area is allocated to each of the parent process and the child process;
Have
Wherein the storage unit, the management information that defines the activation source and stop factor threads in each process are stored,
Within the parent process,
A system management thread for starting and stopping other threads in the process based on the management information;
A child process management thread that performs inter-process communication with a system management thread of the child process based on the management information, and starts and stops the system management thread of the child process;
Information processing device on which is executed . Child process management thread, the information processing apparatus according to claim 1, characterized in Rukoto starting and stopping a plurality of child processes.   The information processing apparatus according to claim 1, wherein the plurality of processes having a parent-child relationship by the tree structure are all processes executed in the information processing apparatus.   2. The process corresponding to the root of the tree structure starts by an operation according to the start of the information processing apparatus, and the process starts to stop by an operation according to the stop of the information processing apparatus. 4. The information processing apparatus according to any one of items 1 to 3. An information processing apparatus in which a plurality of processes, which are execution environments separated from each other when executing a program in the information processing apparatus, have a parent-child relationship by a tree structure , and a plurality of threads are executed in each process. An information processing apparatus comprising: a parent process ; a control unit that executes a child process that is managed to be started and stopped by the parent process; and a storage unit to which an area is allocated to each of the parent process and the child process Is an information processing method executed by
Is stored in the storage unit, based on the thread activation factors and management information that defines the stop factor in the process, the steps of causing other start threads or stopping of the process,
Based on the management information, perform system administration threads and interprocess communication child process, the steps of causing starting or stopping the system management threads child process,
Information processing method to execute .

Images