KR102186809B1 - Partition sharing system and method - Google Patents

Abstract

The present invention provides a plurality of partitions each monopolizing at least one resource; And a partition sharing unit that controls scheduling of the plurality of partitions, sets at least one of the plurality of partitions as a shared partition, and sets a partition of the plurality of partitions other than the shared partition as a general partition. Including, the partition sharing unit discloses a partition sharing system and method for sharing resources of at least one general partition among general partitions to be usable by another general partition through the shared partition.

Description

Partition sharing system and method

The present invention relates to a partition sharing system and method.

The software used in the aviation system requires high reliability and productivity. Due to such a demand, an operating system suitable for a special situation in which high reliability and safety are the top priority is being studied.

In particular, the concept of Integrated Modular Avionics (IMA) appeared, and many studies were conducted, and applied to aviation software standards such as ARINC 653.

ARINC stands for Aeronautical Radio, Incorporated. It is a non-profit organization owned by the United States. It has five areas (aviation, airports, defense, government, and transportation) as its main business areas. It defines standard specifications of communication service and avionics standards between aircraft and aircraft.

IMA stands for Integrated Modular Avionics. In the case of aircraft, it consists of a number of applications with different safety levels. As a technology introduced for their safety and efficiency, by introducing IMA, the application and hardware are not affected by each other when they are developed or executed, so that the development cost of the hardware or application is reduced.

ARINC 653 is an interface between a system core and an application for the purpose of IMA, and is a technical standard defining the interface between the real-time operating system of the digital avionics system defined by ARINC and the application programs running on it.

Large, large-scale systems such as airplanes consist of many applications and processes. In ARINC 653, the concept of partitions was adopted for spatial partitioning and temporal partitioning of each of these applications. Space partitioning means that different partitions do not affect each other's physical memory resources. Time division means that the time resources allocated to the partition cannot interfere with other partitions. Such a partition concept can provide high reliability by preventing a single application program error from adversely affecting the entire system in an environment that performs an important task such as an avionics system.

Aircraft systems are evolving into IMA (Integrated Modular Avionics) structures for integrating into one system from a variety of existing independently configured computing environments (Federated System). Accordingly, the international aviation industry has established the ARINC 653 standard as a system SW for IMA, but there is a limitation that there is no shared model for the system SW for aircraft that complies with the ARINC 653 standard.

In addition, there is a problem that exclusive resources dependent on one partition cannot be used by other partitions.

An object of the present invention is to provide a partition sharing system and method capable of real-time sharing of partitions separated in space and time, and sharing partitions without violating partitioning.

Meanwhile, the technical problems to be achieved in the present invention are not limited to the technical problems mentioned above, and other technical problems that are not mentioned are clearly to those of ordinary skill in the technical field to which the present invention belongs from the following description. It will be understandable.

A partition sharing system according to an embodiment of the present invention includes a plurality of partitions each monopolizing at least one resource; And a partition sharing unit that controls scheduling of the plurality of partitions, sets at least one of the plurality of partitions as a shared partition, and sets a partition of the plurality of partitions other than the shared partition as a general partition. Including, the partition sharing unit shares the resources of at least one general partition among the general partitions to be usable by other general partitions through the shared partition.

The partition sharing unit may include a sharing control unit for sharing resources of at least one general partition among a plurality of general partitions so that other general partitions can use them; And a partition control unit controlling execution and execution cycles of processes in the plurality of partitions. It may include.

The sharing control unit may set a first partition that shares resources among a plurality of general partitions and a second partition that uses resources of the first partition.

The sharing control unit may set the resource of the first partition to be shared by the shared partition at a time of compilation.

The shared partition may include a shared partition process for processing data of the shared partition itself and a shared function process for performing a function requested by the general partition.

The partition control unit may repeat an execution cycle in which each of the plurality of normal partitions is sequentially changed to a normal mode-idle mode based on a predetermined order.

When the second partition calls the shared partition in the normal mode, the partition control unit schedules the shared partition, executes the shared function process of the shared partition, and stores the result value in the memory area of the second partition, When execution of the shared function process of the shared partition is terminated, the second partition can be scheduled.

The second partition may include a shared call API, and the second partition may call a shared partition through the shared call API in a normal mode.

A partition sharing method according to an embodiment of the present invention is a method of sharing a partition using a partition sharing system according to an embodiment of the present invention, the method comprising: setting a shared partition in a plurality of partitions; Performing general partition scheduling; Determining whether the general partition calls the shared partition during scheduling; Scheduling a shared partition when determining whether to call the shared partition in the general partition; Executing a shared function process of the shared partition; Storing the processing result value of the shared function process in a memory area of a general partition calling the shared partition; And when execution of the shared function process of the shared partition is terminated, scheduling the shared partition to a called general partition. Includes.

In the step of determining whether the general partition calls the shared partition during the scheduling, the general partition may include a shared call API, and the general partition may call the shared partition through the shared call API in a normal mode.

According to an embodiment of the present invention, real-time sharing of partitions separated in space and time is possible, and when partitioning is shared, sharing can be performed without violating partitioning.

On the other hand, the effects obtainable in the present invention are not limited to the above-mentioned effects, and other effects not mentioned will be clearly understood by those of ordinary skill in the art from the following description. I will be able to.

1 is a configuration diagram illustrating an exemplary configuration of a partition sharing system according to an embodiment of the present invention,
FIG. 2 is an exemplary diagram for explaining partition scheduling in the partition sharing system according to FIG. 1;
3 is an exemplary flowchart showing the configuration of a partition sharing method according to an embodiment of the present invention.

The embodiments of the present invention are manufactured to more completely describe the present invention to those of ordinary skill in the art, and the following examples may be modified in various other forms, and the scope of the present invention is as follows. It is not limited to the examples. Rather, these embodiments are made to make the present disclosure more faithful and complete, and to completely convey the spirit of the present invention to those skilled in the art.

In addition, each component in the following drawings is exaggerated for convenience and clarity of description, and the same reference numerals refer to the same elements in the drawings. As used herein, the term “and/or” includes any and all combinations of one or more of the corresponding listed items.

The terms used in this specification are used to describe specific embodiments, and are not intended to limit the present invention.

As used herein, the singular form may include the plural form unless the context clearly indicates another case. Further, as used herein, "comprise" and/or "comprising" specifies the presence of the mentioned shapes, numbers, steps, actions, members, elements and/or groups thereof. And does not exclude the presence or addition of one or more other shapes, numbers, actions, members, elements, and/or groups.

Hereinafter, preferred embodiments of the present invention will be described in detail with reference to the accompanying drawings.

1 is a configuration diagram illustrating an exemplary configuration of a partition sharing system according to an embodiment of the present invention,

FIG. 2 is an exemplary diagram for describing partition scheduling in the partition sharing system according to FIG. 1.

First, referring to FIG. 1, the partition sharing system 10 includes a plurality of partitions 100, a memory 200, and a partition sharing unit 300.

Each of the plurality of partitions 100 has temporal/spatial independence.

The partition 100 executes an application process and includes a plurality of partitions 100 and a port for communicating with the outside.

The partition 100 is mainly composed of one or a plurality of applications, and a plurality of partitions operate as one system. The partition 100 is temporally and spatially separated from other partitions 100.

Temporal partitioning means that it is guaranteed not to be disturbed by other partitions during the partition execution time set statically at the system setup time.

Spatial partitioning guarantees independent execution by setting the memory area in which processes in the partition are executed also statically and absolutely not allowing other partitions to invade this area.

Through this spatial/temporal partitioning, errors occurring in one application or partition are prevented from affecting other partitions. The order and execution time of the partitions are determined at the set time, and infinite repetition is performed. At this time, the order of repetitive partition scheduling in the minimum unit is called a major time frame.

The partition 100 may include a first partition 110, a second partition 120, a third partition 130, and a shared partition 140. Here, although the partition 100 in FIG. 1 is shown as including four partitions 110, 120, 130, and 140, this is only for explaining an embodiment of the present invention, and four partitions 110 and 120 , 130, 140) is not limited to the present invention.

Meanwhile, the first partition 110 may be mixed with partition 1 hereinafter, the second partition 120 may be mixed with partition 2 hereinafter, and the third partition 130 may be mixed with partition 3 hereinafter. I can.

Here, each of the first partition 110, the second partition 120, and the third partition 130 may include exclusive resources and a process to which resources are allocated.

The memory 200 stores data related to the partition 100 and the partition sharing unit 300.

The partition sharing unit 300 may be located in the partition operating system kernel 15 of the operating system.

The partition sharing unit 300 controls scheduling of a plurality of partitions of the partition 100 and may share resources of at least one general partition among the general partitions so that other general partitions can use them through the shared partition.

The partition sharing unit 300 includes a sharing control unit 310, a channel control unit 320, and a partition control unit 330.

The sharing control unit 310 may share resources of at least one general partition among a plurality of general partitions so that other general partitions can use them.

Here, the sharing control unit 310 may set a first partition 110 that shares resources among the plurality of partitions 100 and a second partition 120 that uses the resources of the first partition 110.

The shared partition 140 may include a shared partition process for processing data of the shared partition itself and a shared function process for performing a function requested by the general partitions 110, 120, and 130.

The channel controller 320 may control a channel that is a communication link of each of the plurality of partitions 100.

The logical communication link between the partitions 100 is called a channel, and a channel consists of one source and one or more destinations. The channel specifies the mode of message transmission and the characteristics of the message.

The partition 100 accesses the channel through an access point called a predefined port. Ports provide resources required for a specific partition 100 to send or receive messages through a specific channel. The partition 100 may exchange messages through a plurality of channels having respective source and destination ports. A channel has routing from one sending port to one or more receiving ports via intermediate ports.

Channels and ports are defined at system configuration time. The definition of the channel is not limited to the OS of the core module, but is distributed among the components of the system or LRUs. Each communication node (core module, gateway, I/O module, etc.) is set up independently to define how messages are handled by that node. It is the role of the channel controller 320 to consistently set nodes connected to each channel.

The partition control unit 330 controls execution and execution cycles of processes in the plurality of partitions 100.

The partition control unit 330 controls the execution of each of the partitions 100 while changing the mode of the plurality of partitions 100 to an IDLE mode-a normal mode.

Here, in the IDLE mode, processes in the partition are deactivated, and in the NORMAL mode, processes in the partition are activated.

The partition controller 330 controls an application execution cycle based on information on a partition related to an application.

Also, the partition control unit 330 controls the execution of the application process of the partition 100 according to the adjusted scheduling.

Here, referring to FIG. 2, the partition control unit 330 includes partitions 1, 2, and 3 after a first cycle (1C) and a first cycle (1C) in which partitions 1, 2, and 3 are sequentially executed. The second cycle 2C that is sequentially executed may be set.

Of course, although not shown, after the second period 2C, partition 1, partition 2, and partition 3 may be periodically executed.

3 is an exemplary flowchart showing the configuration of a partition sharing method according to an embodiment of the present invention.

Referring to FIG. 3, a method for sharing a partition according to an embodiment of the present invention includes a shared partition setting step (S10), a partition scheduling process step (S20), a shared partition call determination step (S30), and a scheduling step (S40). ), a process execution step of the shared partition (S50), a step of storing a result value in the area of the share request partition (S60), and a step of scheduling a share request partition (S70).

As described above, the partition control unit 330 repeatedly performs the execution order of the partition 100 as follows.

Partition 1 -> Partition 2 -> Partition 3 -> Partition 1 ??

Also, the partition control unit 330 assumes that the memory areas of the partitions 100 are as follows.

-Partition 1: 0xA0000000 ~ 0xAFFFFFFF

-Partition 2: 0xB0000000 ~ 0xBFFFFFFF

-Partition 3: 0xC0000000 ~ 0xCFFFFFFF

-Shared partition: 0xD0000000 ~ 0xDFFFFFFF

In the shared partition setting step S10, the sharing control unit 310 may set the general partitions 110, 120, 130 and the shared partition 140 among the plurality of partitions 100.

Meanwhile, the sharing control unit 310 sets the resource of the first partition 110 among the general partitions 110, 120, and 130 to be shared with the shared partition 140 at the time of compilation, and the second partition 120 is the first partition. It can be set to use the resources of the partition 110.

Here, the shared partition 140 has the right to access the area of the shared general partitions 110, 120, 130, and the general partitions 110, 120, 130 can access the area of the shared partition 140. Can't.

In the partition scheduling step (S20), the partition control unit 330 controls the execution and execution cycles of processes in the plurality of partitions 100, controls the application execution cycle based on information on the partitions related to the application, and adjusts the Execution of the application process of the partition 100 may be controlled according to scheduling.

In determining the shared partition call (S30), it is determined whether the first partition 110, the second partition 120, or the third partition 130 calls the shared partition 140 during scheduling.

As an example, if the second partition 120 activated during scheduling performs a function of calling the shared partition 140 through the shared call API, the partition control unit 330 detects this and determines that the call to the shared partition has been performed. I can.

Here, the shared call API may perform a function of calling a function of the shared partition 140 from the general partition 120, and the shared call API may include the following parameters.

Shared function ID: ID of the desired shared function process

Shared resource address: Address of general partition resource that must be accessed from the shared partition

Shared resource size: The size of general partition resources that must be accessed from the shared partition.

In the scheduling step (S40) of the shared partition, when it is determined that the shared partition call has been performed in the shared partition call determination step (S30), scheduling through the partition control unit 330 is performed by the second partition 120 to the shared partition 140. Schedule with

In the process execution step S50 of the shared partition, a functional process called from the shared partition 140 is executed.

Thereafter, in the step S60 of storing the result value in the area of the sharing request partition, the result value of the data processed as a result of the execution of the function process of the shared partition 140 may be stored in the area of the second partition 120 that has requested sharing.

Thereafter, in the sharing request partition scheduling step (S70), the scheduling is scheduled through the partition control unit 330 to the second partition 120 requesting resource sharing from the shared partition 140.

What has been described above is only one embodiment for implementing the partition sharing system and method according to the present invention, the present invention is not limited to one embodiment, as claimed in the claims below, the gist of the present invention Without departing from, anyone of ordinary skill in the field to which the present invention pertains will have the technical spirit of the present invention to the extent that various modifications can be implemented.

Claims (10)

In a partition sharing system for using exclusive resources subordinate to each partition separated spatially and temporally for space and time division of an application program in an aviation system, in another partition,
A plurality of partitions each monopolizing at least one resource; And
A partition sharing unit configured to control scheduling of the plurality of partitions, set at least one of the plurality of partitions as a shared partition, and set a partition of the plurality of partitions other than the shared partition as a general partition; Including,
The partition sharing unit shares resources of at least one general partition among general partitions to be usable by other general partitions through the shared partition,
The partition operates as one aviation system,
The plurality of partitions include the shared partition and a plurality of general partitions excluding the shared partition,
Each of the plurality of general partitions is temporally and spatially separated,
Each of the plurality of general partitions includes exclusive resources and processes to which resources are allocated,
The above process is for the aviation system,
Each of the normal partitions is changed to a normal mode-idle mode, and is sequentially executed based on a predetermined order during the execution cycle,
The shared partition includes a shared partition process for processing data of the shared partition itself and a shared function process for performing a function requested by the general partition,
The shared partition has the right to access the area of the general partition, each of the plurality of general partitions does not have the right to access the area of the shared partition,
Each of the plurality of general partitions includes a shared calling API,
Each of the plurality of general partitions calls a shared partition through the shared call API in normal mode,
The shared call API includes parameters of the shared function ID, which is the ID of the desired shared function process, the shared resource address, which is the address of a general partition resource that must be accessed from the shared partition, and the shared resource size, which is the size of the general partition resource that must be accessed from the shared partition Including,
The partition sharing unit
A sharing control unit for sharing resources of at least one general partition among the plurality of general partitions so that other general partitions can use them; And
A partition control unit controlling execution and execution cycles of processes in the plurality of partitions; Including,
The sharing control unit
Among a plurality of general partitions, a first partition that shares resources and a second partition that uses resources of the first partition is set,
The partition control unit
When it is determined that the second partition has called the shared partition through the shared call API in the normal mode, scheduling is scheduled from the second partition to the shared partition,
Execute the sharing function process of the shared partition, and store the result value in the memory area of the second partition,
When the execution of the sharing function process of the shared partition is terminated, the system for scheduling the second partition.
delete delete delete delete delete delete delete In the partition sharing method using the partition sharing system according to claim 1,
Setting a shared partition in a plurality of partitions;
Performing general partition scheduling;
Determining whether the general partition calls the shared partition during scheduling;
Scheduling a shared partition when determining whether to call the shared partition in the general partition;
Executing a shared function process of the shared partition;
Storing the processing result value of the shared function process in a memory area of a general partition calling the shared partition; And
Scheduling the shared partition as a called general partition when execution of the shared function process of the shared partition is terminated; Partition sharing method comprising a.
The method of claim 9,
In the step of determining whether the general partition calls the shared partition during the scheduling,
The general partition includes a shared calling API,
The partition sharing method in which the general partition calls a shared partition through the shared call API in a normal mode.

Images