JP2010039861A - Component processor and component processing program - Google Patents

Abstract

The cost of developing a component is reduced.
A component processing apparatus receives a request from an application program, calls an initialization control unit when the request is an initialization request, and calls the processing control unit when the request is other than an initialization request. The request receiving unit 11 is called. The initialization control unit 12 associates a plurality of processes executed in the component program with the plurality of hook functions provided by the process execution unit 23, and the process control unit 21 includes the component program in the request. Independent common processing is requested to the common processing unit 22, and dependent processing is requested to the processing execution unit 23. The common processing unit 22 executes a common process independent of the component program, and the process execution unit 23 requests the component program to execute a plurality of processes associated with each of the plurality of hook functions. To do.
[Selection] Figure 2

Description

  The present invention relates to a component processing apparatus and a component processing program.

  Conventionally, a flow of standardizing API (Application Programming Interface) for accessing components in order to improve the reusability of data processing logic (hereinafter referred to as components) such as codecs and demuxers. There is. As this standardized standard, for example, there is an OpenMAX Integration Layer (hereinafter referred to as OpenMAX IL) (see, for example, Non-Patent Document 1).

  With this standardization, the reusability of components increases, while the developer is obliged to correctly implement the specified state transitions and communication methods with other components. Therefore, there is a problem in that the initial development cost of the component increases as compared with the case where the component is mounted by a unique method.

In response to this problem, it is possible to provide a framework that replaces state transitions and communication methods as a common implementation. However, the form of the component is various, and it has been difficult to provide a unique interface for the component.
“OpenMAX Integration Layer Application Programming Interface Specification Version 1.1.1”, September 14, 2007, Internet <URL: http://www.khronos.org/files/openmax_il_spec_1_1_1.pdf>

  An object of this invention is to provide the component processing apparatus which can reduce the cost required for component development.

  According to one aspect of the present invention, there is provided a component processing apparatus for causing a component program for executing processing of a predetermined function to perform predetermined data processing, and a plurality of processing provided in the component program. A process execution unit that provides a plurality of process I / Fs corresponding to each of the plurality of process I / Fs, and requests the component program to request execution of the plurality of processes associated with each of the plurality of process I / Fs; A common processing unit that executes common processing independent of the component program, and requests common processing independent of the component program from the application program, and depends on the component program Process control for controlling to request the process execution unit to process An initialization control unit for associating the plurality of processes executed in the component program with respect to the plurality of process I / Fs provided by the process execution unit, and receiving the request, Is an initialization request, the initialization control unit is called to associate the plurality of processes executed in the component program with the plurality of process I / Fs provided by the process execution unit. When the request is other than the initialization request, it is possible to provide a component processing apparatus including a request receiving unit that calls the processing control unit.

  According to the component processing apparatus of the present invention, the cost required for component development can be reduced.

Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings.
First, the configuration of the information processing apparatus according to the present embodiment will be described with reference to FIG. FIG. 1 is a block diagram showing the configuration of the information processing apparatus according to this embodiment. As shown in FIG. 1, the information processing apparatus 100 includes a central processing unit (hereinafter referred to as CPU) 101, a ROM 102, a RAM 103, an interface (hereinafter referred to as I / F) 104, and a bus 105. It is configured. The CPU 101, ROM 102, RAM 103, and I / F 104 are connected to each other via a bus 105. In addition, a monitor 106 and a speaker 107 are connected to the I / F 104.

  The ROM 102 stores a component program and a component processing program. The CPU 101 reads these programs from the ROM 102, develops them on the RAM 103, and executes them. The component program is a program that performs a single function process such as a video decoding process or an audio decoding process. The CPU 101 combines these single function processes, performs final data processing, and outputs the result to the monitor 106 or the speaker 107 via the I / F 104. By executing the component program on the CPU 101, components described later are configured.

  The component processing program is an interface program that performs common processing such as prescribed state transitions and communication methods with other components. By executing this component processing program on the CPU 101, the component processing apparatus of the present embodiment is configured.

  A part of the component program may be executed by a processor, a coprocessor, or a dedicated HW different from the CPU 101, and does not affect the essence of the present invention.

  FIG. 2 is a block diagram showing the configuration of the component processing apparatus according to this embodiment. As shown in FIG. 2, the component processing apparatus 1 includes a request receiving unit 11, an initialization control unit 12, a core support unit 13, a plurality of (here, two basic processing units 14a and 14b), and a system processing requesting unit. 15. The component processing apparatus 1 includes two basic processing units 14a and 14b, but may include one or three or more basic processing units. The basic processing unit is generated corresponding to a specific processing unit as a component described later.

  The request reception unit 11 includes a command queue 16 and an execution determination unit 17. The basic processing unit 14a includes functions 18a and 18b provided by the component processing apparatus 1 and hook functions 19a and 19b. On the other hand, the basic processing unit 14b includes functions 18c and 18d and hook functions 19c and 19d.

  In addition to the component processing apparatus 1, an API 31, a plurality of (here, two) specific processing units 32 a and 32 b, and a system processing unit 33 are included. The API 31 has a plurality of API functions 31a to 31d. API functions 31a to 31d are associated with functions 18a to 18d, respectively. These associations are performed by the initialization control unit 12.

  The specific processing unit 32a as a component is configured to include hook function entities 34a and 34b that execute processing of a single function, and an initialization information unit 35a. On the other hand, the specific processing unit 32b as a component is configured to include hook function entities 34c and 34d that execute single-function processing, and an initialization information unit 35b. The hook functions 19a to 19d are associated with the hook function entities 34a to 34d, respectively. These associations are performed by the initialization control unit.

  A command from an application (not shown), in other words, a request is transmitted to the request receiving unit 11. The request receiving unit 11 transmits a request from the application to the basic processing unit 14a or 14b via the API 31. Requests from applications are made by API calls of API functions 31a to 31d. Depending on the type of each API function 31a to 31d, the content of the required processing is roughly divided, and each API function 31a to 31d has parameters and data related to each processing as arguments, and the basic processing unit 14a or 14b. An identifier for identification may be attached. The API functions 31a to 31d and the functions 18a to 18d provided by the component processing apparatus 1 are associated one-to-one as described above. This association is performed by an initialization request issued to the component processing apparatus 1. Initialization processing for the initialization request is performed by the initialization control unit 12. That is, when the request transmitted via the API 31 is an initialization request, the request reception unit 11 transmits this initialization request to the initialization control unit 12.

  The command queue 16 of the request receiving unit 11 stores a plurality of requests from applications. The command queue 16 constitutes a request storage unit capable of storing a plurality of requests from applications. The execution determination unit 17 determines whether or not to execute the request stored in the command queue 16. In particular, the execution determination unit 17 monitors the processing of other components, and transmits the request stored in the command queue 16 to the basic processing unit 14a or 14b only when the execution condition is satisfied.

  Thus, by providing the command queue 16 and the execution determining unit 17 in the request receiving unit 11, the processing control unit described later can operate in different processes, so that the application processing and the data processing are performed in parallel. Can be executed. In addition, by providing a start condition for the processing control unit, it is possible to suppress inadvertent operation of the process when preparation for processing is not completed, and to improve system performance.

  When the initialization request is transmitted from the request receiving unit 11, the initialization control unit 12 associates the API functions 31a to 31d with the functions 18a to 18d provided by the component processing device 1, respectively. A table for executing this association is separately held in a storage unit (not shown) in the initialization control unit 12.

  In addition, when the initialization request is transmitted from the request receiving unit 11, the initialization control unit 12 performs initialization of the component processing apparatus 1. The contents of the initialization are securing and initializing an area used in the component processing apparatus 1.

  Further, when the initialization request is transmitted from the request receiving unit 11, the initialization control unit 12 calls the initialization information unit 35a in the specific processing unit 32a and the initialization information unit 35b in the specific processing unit 32b. The initialization control unit 12 confirms the presence of the initialization information units 35a and 35b by using an initialization function table prepared separately. The identifiers of the specific processing units 32a and 32b are given to the initialization request, and an initialization function to be executed is selected from the initialization function table based on the identifier. The initialization control unit 12 includes pointers of hook functions 19a to 19d, which are processing I / F provided by the component processing apparatus 1 to the specific processing units 32a and 32b, and function entities 34a to 34d prepared by the specific processing unit 32a. Correspond to each. The association is performed using information of the initialization information units 35a and 35b held by the specific processing units 32a and 32b, respectively.

  For example, the hook function 19a, which is a processing I / F, is a function for incorporating another processing before, after, and during the common processing. The pointer of the hook function 19a is described before, after, and during the common processing, and the function entity 34a provided by the specific processing unit 32a is associated with the pointer of the hook function 19a. In the common process, only when the function entity 34a is associated with the pointer of the hook function 19a, the function entity 34a associated with the hook function 19a is appropriately executed.

  The core support unit 13 performs processing corresponding to communication and connection between components, and transmits the processing to the basic processing unit 14a or 14b. Further, the core support unit 13 transmits a request for processing depending on an operating system (hereinafter referred to as OS) or hardware (hereinafter referred to as HW) to the system processing request unit 15.

  The basic processing unit 14a performs common processing such as prescribed state transitions and communication methods with other components. Since the basic processing unit 14b has the same configuration, the description thereof is omitted. The detailed configuration of the basic processing units 14a and 14b will be described with reference to FIG.

  A request for processing dependent on the OS or HW is supplied to the system processing request unit 15 from the core support unit 13, the basic processing units 14 a and 14 b, or the API 31. The system processing request unit 15 supplies a request for processing depending on the OS or HW to the system processing unit 33. The system processing unit 33 executes processing dependent on the OS or HW, such as memory area reservation and queue processing, thread and exclusive control management, and the like.

  The allocation of the memory area, the queue processing, and the like are processes that depend on the OS or HW, so that the calling method differs depending on the OS or HW. Therefore, if a function call depending on the OS or HW is included in the basic processing unit 14a or 14b, the reusability of the component processing apparatus 1 itself deteriorates. Therefore, a layer that abstracts a function that depends on the OS or HW, here, the system processing request unit 15 is defined, so that a function that depends on the OS or HW passes through the layer outside the basic processing unit 14a or 14b. Can be put out.

  Here, the configuration of the basic processing units 14a and 14b will be described. Since the basic processing units 14a and 14b have the same configuration, the configuration of the basic processing unit 14a will be described as a representative. FIG. 3 is a block diagram illustrating a configuration of the basic processing unit. As shown in FIG. 3, the basic processing unit 14 a includes a processing control unit 21, a common processing unit 22, and a processing execution unit 23.

  The process control unit 21 executes the called function 18a or 18b by the function call from the request receiving unit 11. Specifically, the function 18a corresponding to the API function 31a or the function 18b corresponding to the API function 31b is executed. Common processing defined by the standard is executed in the contents of each function. When the hook function pointer is described before and after and during the common processing, and the substance of the function provided by the specific processing unit 32a is associated with the hook function pointer, the hook of the specific processing unit 32a is performed. The function is executed as appropriate.

  In this manner, the hook function pointers are described at a plurality of locations before and after the common processing and in the middle because of the diversity of the specific processing unit 32a. For example, when the specific processing unit 32a operates only with software, a function may be called at the end of the common processing. When the specific processing unit 32a holds a dedicated HW therein, the HW is executed before executing the common processing. This is because the kick may be executed.

  The common processing unit 22 executes common processing defined in the standard. As an example of the common process, the common processing unit 22 executes a communication process related to communication between other components and the program. Since the communication processing related to communication between other components and the program is a part with a high mounting load, the effect of sharing is large. The communication method is defined by the standard, and in this communication process, the common processing unit 22 secures a data area used for communication, for example, a buffer. In addition, the common processing unit 22 sets an information area associated with the buffer, for example, a buffer header. Further, the common processing unit 22 performs negotiation with other components, for example, confirmation of attributes of data to be transmitted / received and confirmation of mutual setting information. Since other components are also created in accordance with the same API standard, when a request is made to another component, a function call is made through the API 31. The request for another component program referred to here is a buffer, in other words, data transmission / reception or negotiation.

  In addition, the common processing unit 22 executes a state transition process related to the management of the state transition of the component program as another example of the common process. Since the state transition processing related to the management of the state transition of the component program is a part where the load of grasping the specification is high, the effect of sharing is large. The type of state to be transitioned is defined by the standard, and it is also defined by the standard which API function is called and which state is transitioned to. In some cases, an API function for explicitly changing the state is defined in the standard. For example, OpenMAX IL defines API functions and command types such as SendCommand (“command type is state transition”, “state to be changed is A”).

  When the function of the specific processing unit 32a is associated with the hook function pointer, the process execution unit 23 executes the function of the specific processing unit 32a through the hook function. In addition, the process execution unit 23 does not perform any process when the function of the specific processing unit 32a is not associated with the hook function pointer.

  FIG. 4 is an explanatory diagram for explaining the initialization function table. As shown in FIG. 4, the initialization function table associates a hook function name with an address in the specific processing unit 32a pointed to by the hook function pointer. After receiving the initialization request, the initialization control unit 12 refers to the initialization information unit 35a to generate an initialization function table in which these associations are executed. For example, in FIG. 4, the hook function name is “process data”, and the address of the pointer corresponding to the process data is “A”. It also indicates that the address of the pointer corresponding to “set parameter” is “B”. Further, it also indicates that the function entity is not associated with “preprocess data” executed before “process data”.

  Next, the operation of the component processing apparatus 1 configured as described above will be described by taking cryptographic processing as an example. The specific processing unit 32a is a data processing logic that executes encryption processing of DES (Data Encryption Standard) and AES (Advanced Encryption Standard), that is, a component, and a processing algorithm is switched by receiving a control command. Further, the specific processing unit 32a transmits the cryptographic processing result to a data processing program (not shown), for example, a data processing program that executes a hash calculation process. Note that the data processing program is a program that complies with the standard, but may not include the contents of the present embodiment.

  In order to simplify the description, the commands defined in the standard are assumed to be the following six commands, here, an initialization command, a communication establishment command, a state transition command, a setting command, a data processing command, and an end command. .

  In addition to the commands defined in the standard, in other words, component-specific custom commands may be defined. The definition of the custom command is executed by the initialization control unit when the initialization control unit 12 performs the initialization process described above. Some components may want to execute commands other than those specified in the standard. In this way, by defining a custom command specific to a component, a command specific to each component can be executed.

The initialization command is a command for performing component initialization processing.
The communication establishment command is a command for establishing a communication path with another data processing program conforming to the standard, in this embodiment, the data processing program.
The state transition command is a command for transitioning the component state. In the present embodiment, it is assumed that there are two types of states of the component, “Preparing” and “Executable”.
The setting command is a command for changing the setting of the component. In the present embodiment, it is used to set a cryptographic algorithm to be used.
The data processing command is a command for inputting data to be subjected to data processing, here, encryption processing, and requesting execution of the encryption processing. It is assumed that the standard defines that the component state must be “executable” when issuing a data processing command.
The end command is a command for performing component end processing.

  Among these, component settings and data processing are processes that affect the contents of the component, so component developers implement setting functions and processing functions corresponding to these two processes based on the configuration file etc. Assume that the hook functions 19a and 19b to be associated are selected. Specifically, the hook function 19a is one of the hook functions provided by the common processing unit 14a for the setting command, and the component developer provides the function provided by the specific processing unit 32a for the hook function required by the component developer. Corresponding entities. At this time, a plurality of hook functions may be associated with each other, or may not be associated at all if unnecessary. In the present embodiment, it is assumed that a function entity 34a (setting function) is associated with the hook function 19a. The hook function 19b is one of the hook functions provided by the common processing unit 14a for the processing command. Similarly, in the present embodiment, the function entity 34b (setting function) for the hook function 19b. Are associated with each other. Furthermore, hook functions are provided in the same manner for other commands, but in this embodiment, no function is associated with these hook functions. In FIG. 2, hook functions that are not associated are not shown for the sake of space.

  An initialization command is input to the request receiving unit 11 through the API 31. The request receiving unit 11 that has received the initialization command calls the initialization control unit 12. The initialization control unit 12 issues a request to the specific processing unit 32a after performing necessary initialization processing of the component processing apparatus 1. The initialization control unit 12 registers the setting function and the processing function of the specific processing unit 32a in the hook functions 19a and 19b of the processing execution unit 23, respectively. Also, the initialization control unit 12 sets the component state to “in preparation”.

  A communication establishment command is input to the request receiving unit 11 through the API 31. The request reception unit 11 that has received the communication establishment command activates the processing control unit 21. The process control unit 21 determines the content of the command and executes the common processing unit 22. The common processing unit 22 secures a data area to be used with the data processing program, for example, performs buffer management, and establishes a communication path. Subsequently, the process control unit 21 calls the process execution unit 23. Here, since the substance of the function is not associated with the hook function of the process execution unit 23 for the communication establishment command, the process execution unit 23 performs no process.

  A setting command, here AES, is input to the request receiving unit 11 through the API 31. The request receiving unit 11 that has received the setting command activates the processing control unit 21. The process control unit 21 determines the content of the command and executes the common processing unit 22. Subsequently, the process control unit 21 activates the process execution unit 23. Here, since the function provided by the specific processing unit 32a, here the setting function, is associated with the hook function 19a which is the processing I / F, the processing execution unit 23 sets the specific processing unit 32a through the hook function 19a. to start. The specific processing unit 32a sets its processing algorithm to AES.

  A state transition command is input to the request receiving unit 11 through the API 31. The request receiving unit 11 that has received the state transition command activates the processing control unit 21. The process control unit 21 determines the content of the command and executes the common processing unit 22. The common processing unit 22 sets the component state to “executable” from the information of the state transition command. Subsequently, the process control unit 21 activates the process execution unit 23. Here, since the substance of the function is not associated with the hook function of the process execution unit 23 for the state transition command, the process execution unit 23 performs no processing.

  A processing command is input to the request receiving unit 11 through the API 31. Upon receiving the processing command, the request receiving unit 11 activates the processing control unit 21. The process control unit 21 determines the content of the command and executes the common processing unit 22. The common processing unit 22 determines whether the component state is “executable”. Subsequently, the process control unit 21 activates the process execution unit 23. Here, since the function provided by the specific processing unit 32a, here the processing function, is associated with the hook function 19b that is the processing I / F, the processing execution unit 23 passes the hook function 19b through the specific processing unit 32a. Start up. The specific processing unit 32a performs cryptographic processing using an AES algorithm. The processing result of the specific processing unit 32a is transmitted to the data processing program by the common processing unit 22.

  An end command is input to the request receiving unit 11 through the API 31. The request receiving unit 11 that has received the end command activates the processing control unit 21. The process control unit 21 determines the content of the command and executes the common processing unit 22. The common processing unit 22 performs release processing of the set data area, communication path, and registered function. Subsequently, the process control unit 21 calls the process execution unit 23. Here, since the substance of the function is not associated with the hook function of the process execution unit 23 for the end command, the process execution unit 23 performs no processing.

  In the above flow, a request for processing dependent on the OS or HW, such as securing a memory area, is supplied to the system processing unit 33 via the system processing requesting unit 15, and the system processing unit 33 depends on the OS or HW. Processing is executed.

  As described above, the component processing apparatus 1 is configured to implement prescribed state transitions, communication methods with other components, and the like as common processing. In addition, the component processing apparatus 1 sets a hook function for incorporating another process before and after the common process, and associates a component-specific process with this hook function. As a result, the component developer does not have to develop the component in consideration of the specified state transition and the communication method with other components. That is, the component developer only needs to implement the component-specific algorithm.

  Therefore, according to the component processing apparatus of the present embodiment, the cost required for component development can be reduced.

  Each “unit” in this specification is a conceptual one corresponding to each function of the embodiment, and does not necessarily correspond to a specific hardware or software routine on a one-to-one basis. Therefore, in the present specification, the embodiment has been described above assuming a virtual circuit block (unit) having each function of the embodiment.

  The program for executing the operations described above is recorded or stored as a computer program product in its entirety or in part on a portable medium such as a flexible disk or CD-ROM or a storage medium such as a hard disk. Yes. The program code is read by a computer, and all or part of the operation is executed. Alternatively, all or part of the program can be distributed or provided via a communication network. The user can easily realize the component processing apparatus of the present invention by downloading the program via a communication network and installing the program on the computer, or installing the program from the recording medium on the computer.

  The present invention is not limited to the above-described embodiments, and various changes and modifications can be made without departing from the scope of the present invention.

It is a block diagram which shows the structure of the information processing apparatus which concerns on this Embodiment. It is a block diagram which shows the structure of the component processing apparatus which concerns on this Embodiment. It is a block diagram which shows the structure of a basic process part. It is explanatory drawing for demonstrating the initialization function table.

Explanation of symbols

  DESCRIPTION OF SYMBOLS 1 ... Component processing apparatus, 11 ... Request receiving part, 12 ... Initialization control part, 13 ... Core support part, 14a, 14b ... Basic processing part, 15 ... System processing request part, 16 ... Command queue, 17 ... Execution judgment part , 18a to 18d ... function, 19a to 19d ... hook function, 21 ... processing control unit, 22 ... common processing unit, 23 ... processing execution unit, 31 ... API, 31a-31d ... API function, 32a, 32b ... specific processing unit , 33: System processing unit, 35a, 35b ... Initialization information unit, 100 ... Information processing device, 101 ... CPU, 102 ... ROM, 103 ... RAM, 104 ... I / F, 105 ... Bus.

Claims (6)

A component processing device for causing a component program for executing processing of a predetermined function to perform predetermined data processing,
A plurality of process I / Fs corresponding to each of a plurality of processes provided in the component program are provided, and a request for execution of the plurality of processes associated with each of the plurality of process I / Fs is sent to the component A process execution unit that requests the program;
A common processing unit that executes common processing independent of the component program;
Among the requests from the application program, request a common process independent of the component program to the common processing unit, and control a process control unit to control the process execution unit to request the process execution unit,
An initialization control unit that associates the plurality of processes executed in the component program with the plurality of process I / Fs provided by the process execution unit;
When the request is received and the request is an initialization request, the initialization control unit is called, and the plurality of processing I / Fs provided by the processing execution unit are executed in the component program, respectively. A request receiving unit that associates a plurality of processes and calls the process control unit when the request is other than the initialization request; and
A component processing apparatus comprising:   The initialization control unit maintains an initialization function table that stores addresses in the components of the plurality of processes corresponding to the plurality of process I / Fs and the plurality of process I / Fs, The component processing apparatus according to claim 1, wherein the association is performed by referring to an initialization function table.   The component program holds an initialization function table that stores the plurality of processing I / Fs and addresses in the components of the plurality of processings corresponding to the plurality of processing I / Fs, and the initialization control. The component processing apparatus according to claim 1, wherein the association is performed by referring to the initialization function table in response to an initialization request from a unit. The request receiving unit is a request storage unit capable of storing a plurality of received requests;
An execution determination unit that determines whether or not the request can be executed in the process execution unit;
Have
The said execution determination part loads the said request | requirement stored in the said request | requirement storage part to the said process control part, when it judges that the said request | requirement is executable in the said process execution part. 4. The component processing apparatus according to any one of 3.   The common process is a communication process for establishing a communication path of the component and managing a data area transmitted / received on a communication system path, or a state transition process for executing a state transition of the component. The component processing apparatus of any one of Claim 1 to 4. A component processing program for causing a processing program for executing a specific function to perform specific data processing,
A plurality of process I / Fs corresponding to each of a plurality of processes provided in the component program are provided, and a request for execution of the plurality of processes associated with each of the plurality of process I / Fs is sent to the component A first code part to request for the program;
A second code unit that executes common processing independent of the component program;
A third code unit that controls to request the common processing unit to perform a common process independent of the component program, and to request the process execution unit to perform a process dependent on the component program. When,
A fourth code unit that associates the plurality of processes executed in the component program with the plurality of process I / Fs provided by the process execution unit;
When the request is received and the request is an initialization request, the initialization control unit is called, and the plurality of processing I / Fs provided by the processing execution unit are executed in the component program, respectively. A plurality of processes associated with each other, and when the request is other than the initialization request, a fifth code section that calls the process control section;
A component processing program for causing a computer to execute.

Images