JP2008181370A - Access management apparatus, access management method and program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide an access management apparatus for improving the execution possibility of an application. <P>SOLUTION: The access management apparatus provided with a device replacement determination part detects an alternate device having a function equivalent to that of a device to be accessed and provides the execution right of the substitutive device to an application which cannot acquire the execution right of the device to be accessed to improve the execution possibility and execution continuation of the application, to flexibly correspond to a configuration change in the device and to allow the application to be executed without being conscious of the configuration of the device. <P>COPYRIGHT: (C)2008,JPO&INPIT

Description

  The present invention relates to an access management apparatus, an access management method, and a program used in an information processing apparatus in which a plurality of applications are started. More specifically, a conflict occurs as a result of a plurality of applications accessing the same device simultaneously. The present invention relates to an access management apparatus, an access management method, and a program for managing a device to be accessed at the time.

  In general, one application executed by one information processing apparatus performs a desired operation by controlling the operation of the entire computer by controlling a physical device or a software device. Hereinafter, physical devices and software devices are collectively referred to as devices. However, in an information processing apparatus in which a plurality of applications are activated simultaneously, when two or more applications try to access one device at the same time, access requests collide. At this time, one of the applications cannot acquire the right to execute the device and cannot perform a desired operation.

  Hereinafter, a situation in which two or more applications access one device at the same time and access requests collide will be referred to as contention. When a conflict occurs, generally, an application other than the application that has acquired the right to execute the device cannot perform desired control. Therefore, various methods have been proposed in the past for controlling the access request of each application so that contention does not occur. Hereinafter, the device access request control of the application for avoiding the conflict will be referred to as conflict arbitration.

For example, as one method of contention arbitration, a method has been proposed in which a physical device is hidden from an application and managed in units of logical devices and resources (see Patent Document 1). This method can flexibly respond to changes in the configuration of the physical device, and even if the physical device has multiple functions, it enables individual mediation of contention in units of resources, enabling the functions of the physical device to be effective. It becomes possible to utilize it.
JP 2004-178578 A

  However, in the case of contention that has been proposed in the past, if the execution right of the device could not be acquired in the event of a conflict, or if the execution right was taken away by another application, these applications would perform the desired operation. Could not solve the problem of not being able to.

  In addition, when the device configuration is changed and the device requested by the application becomes unusable, the application that issued the access request cannot perform a desired operation. For this reason, the application side needs to be aware of the device configuration.

  The present invention solves the above-described conventional problems. For an application that cannot acquire the right to execute a required device as a result of a conflict or a change in device configuration, the required device is replaced with another device. It is an object of the present invention to provide an access management apparatus, an access management method, and a program that can execute the application by replacing.

  In order to solve the conventional problem, an access management apparatus according to the present invention manages access requests to a device from a plurality of applications, and includes device-specific information indicating functions and performances of a plurality of devices accessed from the application. An information storage unit for storing device state information indicating a use state of the device; and a device for granting a device execution right to the application based on the received access request, the device specific information, and the device state information Based on the management unit, the device specific information and the device state information, a contention determination unit that determines whether or not the execution right of the device requested by the application can be granted, and the execution right is granted If it is determined that the access request and the device are not Based on the specific information, and a determining device replacement determining section whether or not there is an alternative available devices.

  According to the configuration of the present invention, as a result of contention arbitration, for an application in which a request device, which is a device specified by the application in an access request, is unusable, or for an application that has lost the execution right of the used device, Execution feasibility of an application can be enhanced by giving an execution right of an alternative device having a function equivalent to that of the requesting device.

  Hereinafter, embodiments of the present invention will be described with reference to the drawings.

(Embodiment 1)
FIG. 1 is a diagram showing a functional block configuration of an access management apparatus according to Embodiment 1 of the present invention. In FIG. 1, the access management apparatus 100 according to the first embodiment includes a device management unit 101, a conflict determination unit 102, and a device replacement determination unit 103. The device management unit 101 includes an information storage unit 104 that stores device state information 105 and device specific information 106. Although the device management unit 101 has the information storage unit 104 here, the information storage unit 104 may be provided independently.

  The access management apparatus 100 receives an access request for the device 108 from the application 107 (the device 108 requested by the application 107 is referred to as a request device), and grants the execution right of the device 108 that permits access to the application 107. The outline of each component will be described below.

  The device management unit 101 manages the devices 108 (device 1, device 2,..., Device n) registered in the information storage unit 104, and stores the device 108 in the application 107 (APL1, APL2,... APLn). Grant execution rights.

  First, the device management unit 101 determines an application 107 to which a device execution right is granted based on the device access request from the application 107 and the determination results of the conflict determination unit 102 and the device replacement determination unit 103.

  Furthermore, when the occurrence of a conflict is notified by the determination result of the conflict determination unit 102, the device management unit 101 performs contention arbitration according to rules such as the priority of the application or first win, subsequent win, etc. for the device 108 in which the conflict has occurred, A device execution right is granted to the arbitrated application 107. In the first embodiment, the access request priority 302 and the use APL (application) priority 403 are compared, and a device execution right is given to the application 107 having a higher priority. The access priority 302 and the use APL priority 403 will be described in detail later with reference to FIGS.

  In addition, the device management unit 101 has a function equivalent to that of a request device of an application (hereinafter, referred to as a low priority application) for which the execution right of the device has not been granted due to contention based on the determination result of the device replacement determination unit 103. When notified (hereinafter referred to as an alternative device), the execution right of the alternative device is granted to the low priority application.

  Furthermore, the device management unit 101 includes an information storage unit 104 that stores device state information 105 and device specific information 106. The device status information 105 and the device specific information 106 are managed by the device management unit 101, and information is added, deleted, and changed according to the device configuration.

  The device status information 105 is a table that holds the status of each device, and stores the usage status of the device.

  The device-specific information 106 is a table that holds information for each device, and stores one or more parameters that determine the identifier of each device, the function that each device has, and the priority of the device.

  The conflict determination unit 102 refers to the device status information 105 acquired from the device management unit 101 for the device 108 that has received an access request from the application 107, and determines whether or not a conflict has occurred. In the first embodiment, the conflict determination unit 102 determines a conflict based on the accessibility 402 in the device status information 105. Further, when an access request is made to a device whose access permission 402 is “impossible”, the conflict determination unit 102 considers that a conflict has occurred and notifies the device management unit 101 of the determination result. When an access request is made to a device whose access permission 402 is “permitted”, it is considered that there is no conflict, and the determination result is notified to the device management unit 101. The accessibility 402 will be described in detail later with reference to FIG.

  The device replacement determination unit 103 refers to the device specific information 106 acquired from the device management unit 101 and determines whether there is an alternative device for the low priority application on the system. When there are a plurality of alternative devices, priorities are assigned based on specific parameters or combinations thereof registered in the device specific information 106, and one alternative device is selected accordingly. Thereafter, the device replacement determination unit 103 notifies the device management unit 101 of the selected alternative device. If there is no alternative device, the device management unit 101 is notified to that effect.

  Here, the priority order may be determined in advance for each function of the device in the device management unit 101 based on the device specific information 106. In addition, a parameter to be prioritized for each device may be designated according to the content of the access request.

  FIG. 2 is a diagram illustrating an example of competition when the first embodiment is applied to a mobile terminal. The mobile terminal in this example includes, as devices, a decoder 1 (203) that is an H / W-MPEG4 decoding device, a decoder 2 (204) that is an S / W-MPEG2 / 4 decoding device, and a decoder 3 (an S / W-MPEG4 decoding device). 205), Renderer 1 (206) that is an H / W video rendering processor, and Renderer 2 (207) that is an S / W video rendering processor. Then, when the 1seg broadcast application 201 performs processing using Decoder 1 (203) and Renderer 1 (206) on the terminal, the Web display application 202 issues an access request to the devices Decoder 1 (203) and Renderer 2 (207). As a result, there is a conflict.

  FIG. 3 is a diagram illustrating an example of an access request that the device management unit 101 receives from an application. In the first embodiment, it is assumed that an access request includes an APL name 301, a priority 302, and a request device 303. The priority 302 indicates that the smaller the number, the higher the priority. There are as many requesting devices 303 as the application requires, and it represents a specific device requested by the application. Also, the requesting device shown in FIG. 3 represents a requesting device issued by the 1seg broadcast application 201 and the Web display application 202 shown in FIG.

  FIG. 4 shows an example of the device status information 105. In the first embodiment, it is assumed that the device status information 105 includes a device name 401, an access permission / non-accessibility 402, and an application (APL) priority 403. The device name 401 represents a device registered in the device management apparatus 101, and corresponds to the device name 501 of the device specific information 106 illustrated in FIG. Access permission / non-permission 402 indicates whether or not the device is being executed by an application. If “enabled”, the device is not executing, and if “not allowed”, the device is executing. The usage APL priority 403 represents the priority of the access request of the application being used, and here corresponds to the priority 302 of the access request shown in FIG. When one device can execute a plurality of applications, information indicating the consumption status of resources held by the device, such as the number of applications used and the device usage rate, may be held.

  FIG. 5 shows an example of the device specific information 106. In the first embodiment, it is assumed that the device specific information 106 includes a device name 501, a possessed function 502, and a processing speed 503. The device name 501 corresponds to the device name 401 held in the device status information 105. Assume that there are as many possessed functions 502 as there are functions possessed by each device as shown in FIG. The processing speed 503 indicates that the larger the number, the higher the performance. In the first embodiment, when there are a plurality of alternative device candidates in the system, the device replacement determination unit 103 preferentially selects a parameter with higher processing speed 503 among parameters included in the device specific information 106. Shall be selected. Note that image quality, power consumption, and the like may be held as the device specific information 106 in order to determine an alternative device. Further, when one device can be executed from a plurality of applications, information obtained by quantifying the resources of the device, such as the maximum number of applications that can be used simultaneously, may be held.

  Hereinafter, with reference to FIGS. 2 to 7, device execution right assignment and device replacement when a conflict occurs in the first embodiment will be described in detail.

  In FIG. 2, first, the 1 seg broadcast application 201 reproduces 1 seg broadcast using two devices Decoder1 (203) and Renderer1 (206). At this time, the execution rights of the decoder 1 (203) and the renderer 1 (206) are owned by the 1seg broadcast application 201. Next, while the 1seg broadcast application 201 is being executed, the Web display application 202, which is another application, issues an access request to the Decoder 1 (203) and Renderer 2 (207), and tries to start playback of video content on the Web. . At this time, as shown in FIG. 2, the Web display application 202 issues an access request to the Decoder 1 (203) being executed by the 1seg broadcast application 201. As a result, contention occurs. Hereinafter, a procedure for assigning the execution right of the device at this time will be described with reference to FIG. The device replacement execution procedure will be described with reference to FIG.

  First, the device management unit 101 receives an access request from the Web display application 202 during execution of the 1seg broadcast application 201 (S601).

  The device management unit 101 that has received the access request refers to the device specific information 106 shown in FIG. 5 and searches for the device names 501 of the decoder 1 (203) and the renderer 2 (207) that have made the access request (S602).

  Next, the device management unit 101 checks whether or not the requested device exists on the system (S603). In the first embodiment, it can be confirmed that both the decoder 1 (203) and the renderer 2 (206), which are devices requested by the web display application 202, exist.

  Next, the device management unit 101 refers to the device status information 105 and acquires the status information of the requested device (here, access permission 402) (S604).

  Next, the contention determination unit 102 acquires from the device management unit 101 the access permission / inhibition 402 of the requested device and the access request received by the device management unit 101. Further, the conflict determination unit 102 determines a conflict based on the acquired access permission 402 and the access request, and notifies the device management unit 101 of the determination result. In the first embodiment, Renderer 2 (207) is determined to be in an executable state without contention because the access permission 402 is “Yes” (S605), and the device management unit 101 causes the Web display application 202 to display the Renderer 2 (207). 207) device execution right is granted (S606).

  However, contention occurs for the decoder 1 (203) because the accessibility 402 is “impossible”. Further, since the use APL priority 403 is higher than the priority 302 of the Web display application 202, the device management unit 101 does not grant the device execution right as a result of the competition arbitration (S605). Therefore, since the Web display application 202 cannot perform a desired operation at this time, the process proceeds to FIG.

  In the alternative device search procedure, first, the device management unit 101 notifies the device exchange determination unit 103 of the request device 303 of the low priority application as a result of the competition arbitration. In the first embodiment, Decoder 1 is notified. The device exchange determination unit 103 acquires the device specific information 106 from the device management unit 101, extracts the possessed function of the requested device Decoder 1 (203) from the retained function 502, and decodes the MPEG4 decoding that is a function required by the Web application 202. Identify functions. Then, the device specific information 106 is searched using the MPEG4 decoding function as a search key, and a device having the MPEG4 decoding function is searched (S701).

  Next, the device replacement determination unit 103 determines whether there is an alternative device having an MPEG4 decoding function other than the Decoder 1 (203) from the search result of S701, and if it is determined that it exists, extracts the alternative device ( S702). At this time, there may be two or more alternative device candidates having the corresponding function. In the first embodiment, MPEG2 / 4 decoding device Decoder2 (204) and MPEG4 decoding device Decoder3 (205) having the same function as that of Decoder1 (203) correspond to alternative device candidates. If no alternative device corresponds to the device specific information 106 in S702, the device management apparatus 101 is notified that there is no alternative device. In this case, the Web display application 202 cannot acquire a right to execute a device having an MPEG4 decoding function, and thus cannot perform a desired operation.

  Next, the device replacement determination unit 103 selects a device to which an execution right is actually given from the alternative device candidates extracted in S702 (S703). The alternative device is selected according to a preset priority device selection method. In the first embodiment, as described above, since a high-speed device is preferentially selected based on the processing speed 503, Decoder 2 (204) is selected. Then, the device replacement determination unit 103 notifies the device management unit 101 of the selected alternative device.

  Next, the device management unit 101 refers to the device status information 105 and acquires the status information (accessibility 402 in this case) of the Decoder 2 (204) selected as the alternative device (S704).

  Next, the competition determination unit 102 determines whether or not the Decoder 2 (204) selected as the alternative device can be executed in the same manner as in S605 (S705). In the first embodiment, since Decoder 2 (204) is in an executable state without conflict, the device management unit 101 gives the Web display application 202 the right to execute Decoder 2 (204) (S706). As a result, the Web display application 202 has acquired all the execution rights of the device having the required function, and thus it is possible to reproduce the moving image content on the Web as a desired operation.

  If the access permission 402 of the Decoder 2 (204) is “impossible” in S705, the use APL priority 403 is higher than the priority 402 of the Web display application 202, and the device execution right cannot be acquired, the Web display application 202 cannot perform a desired operation.

  Moreover, although the case where the priority of the 1seg broadcast application 201 previously executed on the system is higher than the priority of the Web display application 202 executed later has been described, the 1seg broadcast application executed previously A case where the priority of the Web display application 202 executed after 201 is high is also conceivable.

  At this time, in S605, the device management unit 101 regards that the Web display application 202 has the device access priority right, and the Web display application 202 acquires the execution right of the device decoder 1 (203) in which the conflict has occurred.

  In this case, the 1seg broadcast application 201 that has lost the execution right of the Decoder 1 (203) executes the alternative device search procedure shown in FIG. 7, and performs an alternative device search and execution right acquisition process. As a result, the 1seg broadcast application 201 can acquire the execution right of the decoder 2 (204).

  According to such a configuration, the execution of the application is performed by granting the execution right of the alternative device having the same function as the requesting device to the application that cannot acquire the execution right of the required device as a result of the conflict. The possibility can be increased.

(Embodiment 2)
In the first embodiment, when a single alternative device is selected in device selection S703 at the time of device replacement, and it is determined that the alternative device can be used in S705 and is not usable, another alternative device is not searched. When there are a plurality of alternative devices, it may be considered that the alternative device replacement determination is repeatedly performed until an alternative device is found.

  FIG. 8 is a diagram showing an alternative device search procedure according to the second embodiment. Since the basic processing other than the replacement determination is the same as the alternative device search procedure shown in FIG. 7 used in the first embodiment, the same reference numerals are given to the steps for performing the same processing as in FIG. Is omitted.

  S801 is different from S703 in that the device replacement determination unit 103 stores alternative device candidates in a list. In this list, it is assumed that information equivalent to the device specific information 106 regarding the alternative device candidate is stored. S802 differs from S705 in the case where the alternative device cannot be executed.

  If the alternative device cannot be executed in step S802, the device replacement determination unit 103 deletes the item related to the device determined not to be executable from the alternative device candidate list stored in step S801, and whether another candidate exists. It is determined whether or not (S803).

  If another candidate exists, the process returns to S801, and the device replacement determination unit 103 selects the next alternative device from the list of stored alternative device candidates. For example, when priority is given to selecting a device with a higher processing speed 503 as in the first embodiment, as an alternative device of Decoder 1 (203) required by the Web display application 202 in the same configuration as in the first embodiment. Decoder 2 (204) is selected with the highest priority. However, if the Decoder 2 (204) is not executable, the Decoder 3 (205) is selected as the next alternative device, and the device execution right acquisition process is performed again.

  According to such a configuration, when there are a plurality of alternative device candidates, it is possible to further increase the executability of the application by giving the execution right or repeatedly performing the execution right acquisition process until no alternative device candidate exists from the list. It becomes possible to raise.

(Embodiment 3)
In the first and second embodiments, the access management apparatus that allocates an alternative device when a conflict occurs has been described. However, there may be a case where there is no device that has issued an access request when the application is executed because the device configuration has been changed.

  FIG. 9 shows an example of a case where the required device Decoder 1 (902) does not exist on the system when the 1seg broadcast application 901 is executed. The access request in the third embodiment is assumed to have the request function 304 in addition to the APL name 301, the priority 302, and the request device 303 used in the first embodiment.

  With reference to FIG. 6, the execution right granting procedure for the requesting device according to the third embodiment will be described. The basic procedure is the same as in the first embodiment. In S603, when the device management unit 101 refers to the device specific information 106 and confirms the presence of the requested device, it becomes clear that the Decoder 1 (902) does not exist. At this time, since the execution right of the request device cannot be acquired, the process proceeds to the alternative device search procedure of FIG. 7 based on the access request request function 304.

  In the third embodiment, the alternative device search procedure is basically the same as that of the first embodiment. The difference from the first embodiment is that the device exchange determination unit 103 acquires the function required by the application that is the search key for the alternative device from the request function 304 in the access request in S701. In addition, when there are a plurality of alternative devices as in the second embodiment, it is conceivable that the execution right acquisition process is repeatedly performed until the execution right is obtained. In addition, by using the third embodiment, it is possible to specify a function required by an application when an execution right cannot be acquired in an access request to a device having a plurality of functions, such as Decoder 2 (903). .

  According to such a configuration, the execution right of an alternative device having the same function as the requesting device is granted to an application whose execution right cannot be acquired as a result of the loss of the required device from the system due to a change in the device configuration. By doing so, the feasibility of the application can be increased.

(Embodiment 4)
In the first to third embodiments, an application to be executed designates a specific device as a device access request. However, there may be cases where only the necessary functions are required.

  FIG. 10 is a diagram illustrating an example of an access request according to the fourth embodiment. It is assumed that the access request in the fourth embodiment includes an APL name 301, a priority 302, and a request function 304. Compared to the first embodiment, a difference is that a request function 304 is used instead of the request device 303. With reference to FIG. 11, a procedure for assigning an execution right of a device will be described. The same reference numerals are given to procedures for performing the same processing as in FIG. 6, and description thereof is omitted.

  In FIG. 6, in S602, the device management unit 101 checks the presence / absence of the requested device. However, in the fourth embodiment, the device management unit 101 only notifies the device exchange determination unit 103 of an access request from the application. I do. Next, the device exchange determination unit 103 searches for a device having the request function 304 based on the access request and the device specific information 106 acquired from the device management unit 101 (S1101).

  Next, the device exchange determination unit 103 confirms the presence or absence of a device having the request function 304 (S1102), determines a device that requests an execution right according to a preset priority device selection method, and notifies the device management unit 101 of it. (S1103). The operations after S605 are the same as those in the first embodiment including the alternative device search procedure.

  According to such a configuration, it is possible to search for a device having a necessary function and to grant an execution right only by notifying only the function level required by the application in the access request. At this time, the application designer and the application need not be aware of the device configuration.

(Embodiment 5)
In the first to fourth embodiments, the contention determination unit 102 performs contention determination based on the accessibility 402 of the device status information 105. However, it is also conceivable that the device management unit 101 performs contention determination based on the device name 401 and the accessibility 402 of the device status information 105 by storing only the devices in which the device status information 105 is actually used.

  In the fifth embodiment, the device status information 105 stores only devices that are actually used, and when the device management unit 101 receives a device access request, the requested device is stored in the device status information 105. An example in the case of determination as competition will be described. In the fifth embodiment, the device management unit 1201 will be described as performing a competition determination with reference to FIG. Components having the same functions as those in FIG. 1 are denoted by the same reference numerals, and description thereof is omitted.

  The access management device 1200 does not have the contention determination unit 102 as compared to FIG. This is because the device management unit 1201 also performs competition determination.

  The device management unit 1201 performs a conflict determination based on the device access request and the device status information 1202 stored in the information storage unit 104. The contention determination procedure will be described later.

  The device status information 1202 stores information only about devices that are actually used, that is, devices to which execution rights are granted to applications. Referring to FIG. 13, the device names 1301 to which the execution right is currently assigned are Decoder1 and Renderer1. As a result, if the next requested device is Decoder1 or Renderer1, a conflict occurs.

  In this case, the contention determination is performed based on whether or not there is a request device in the device name 1301. This is because, as a premise, only one application can be assigned to one device. However, if a plurality of applications can be assigned to one device, the access permission / prohibition 1302 also needs to be subject to competition determination.

  With reference to FIG. 14, a procedure for assigning an execution right for a device in the fifth embodiment will be described. The same reference numerals are given to procedures for performing the same processing as in FIG. 6, and description thereof is omitted.

  Upon receiving a device access request from the application 107, the device management unit 1201 acquires device status information 1202 (S1401).

  Next, the device management unit 1201 determines whether or not the requested device requested for access is stored in the device name 1301 of the device status information 1202 (S1402). If the requested device is stored in the device name 1301, it is determined that a conflict has occurred, and the process proceeds to the device replacement execution procedure in FIG. If the requested device is not stored in the device name 1301, the right to execute the requested device is granted to the application, and the procedure is terminated (S604, S605).

  According to such a configuration, by storing only the devices to which the device state information 1202 grants the execution right, the memory can be used efficiently, and further, the procedure associated with the conflict determination can be simplified. it can.

  Although the decoder has been mainly described as the device in the present embodiment, it goes without saying that the present invention can be implemented even with a device used in a portable terminal, a personal computer, or the like.

  In the implementation of the access management apparatus according to the present invention, the above-described device management unit, contention determination unit, device replacement determination unit, device specific information, and device status information may be a software program or a medium on which the program is recorded.

  In the above-described embodiment, each functional block constituting the access management apparatus is typically realized as a program that operates on an information device that requires a CPU or a memory. May be realized as an LSI which is an integrated circuit. These LSIs may be individually made into one chip, or may be made into one chip so as to include a part or all of them. The name used here is LSI, but it may also be called IC, system LSI, super LSI, or ultra LSI depending on the degree of integration.

  Further, the method of circuit integration is not limited to LSI's, and implementation using dedicated circuitry or general purpose processors is also possible. An FPGA (FIELD PROGRAMMABLE GATE ARRAY) that can be programmed after manufacturing the LSI or a reconfigurable processor that can reconfigure the connection and setting of circuit cells inside the LSI may be used.

  Further, if integrated circuit technology comes out to replace LSI's as a result of the advancement of semiconductor technology or a derivative other technology, it is naturally also possible to carry out function block integration using this technology. Biotechnology can be applied.

  The access management apparatus according to the present invention has a device exchange unit that searches for an alternative device for an application for which the execution right of the requested device could not be acquired by the existing contention mediation, and is useful as a mobile terminal, PDA, PC, etc. .

Functional block configuration diagram of an access management device in Embodiment 1 of the present invention The figure which shows an example of device replacement implementation at the time of competition of the access management apparatus in Embodiment 1 of this invention The figure which shows an example of the access request of the access management apparatus in Embodiment 1 of this invention The figure which shows an example of the device status information of the access management apparatus in Embodiment 1 of this invention The figure which shows an example of the device specific information of the access management apparatus in Embodiment 1 of this invention Device execution right assignment procedure flowchart of the access management apparatus in Embodiment 1 of the present invention Alternative device search procedure flowchart of the access management apparatus in Embodiment 1 of the present invention Recursive alternative device search procedure flowchart of the access management apparatus in Embodiment 2 of the present invention The figure which shows an example of device replacement implementation at the time of the device configuration change of the access management apparatus in Embodiment 3 of this invention The figure which shows an example of the access request of the access management apparatus in Embodiment 4 of this invention Device execution right assignment procedure flowchart of the access management apparatus in Embodiment 4 of the present invention Functional block configuration diagram of an access management device in Embodiment 5 of the present invention The figure which shows an example of the device status information of the access management apparatus in Embodiment 5 of this invention Device execution right grant procedure flowchart of the access management apparatus in Embodiment 5 of the present invention

Explanation of symbols

DESCRIPTION OF SYMBOLS 100 Access management apparatus 101 Device management part 102 Competition determination part 103 Device exchange determination part 104 Information storage part 105 Device status information 106 Device specific information 107 Application 108 Device 201 1seg broadcast application 202 Web display application 203 Decoder1
204 Decoder2
205 Decoder3
206 Renderer1
207 Renderer2
301 APL name 302 Priority 302
303 Requested device 401 Device name 402 Access denied 403 APL priority used 501 Device name 502 Holding function 503 Processing speed 901 1seg broadcast application 902 Decoder1
903 Decoder 2
904 Renderer1
1001 Request Function 1200 Access Management Device 1201 Device Management Unit 1202 Device Status Information 1301 Device Name 1302 Access Allowability

Claims (7)

An access management apparatus that manages access requests to devices from a plurality of applications,
An information storage unit that stores device-specific information indicating the function and performance of a device accessed from the application and device state information indicating a use state of the device;
A device management unit that grants an execution right of a device to the application based on the received access request;
Based on the access request and the device status information, a contention determination unit that determines whether or not the execution right of the device requested by the application can be granted;
A device replacement determination unit that determines whether there is a replaceable device based on the access request and the device-specific information when it is determined that the execution right cannot be granted;
The device management unit, when it is determined by the device replacement determination unit that there is a replaceable device, gives the execution right to the replaceable device. If the device replacement determination unit determines that the execution right of the device selected in the first device replacement determination in response to the access request cannot be granted, recursively searching for the next best alternative device. The access management apparatus according to claim 1, wherein: When the device requested by the application does not exist in the device specific information, the device replacement determination unit determines whether there is a replaceable device based on the access request and the device specific information. The access management apparatus according to claim 1, wherein: 4. The access management apparatus according to claim 3, wherein the device exchange determination unit determines whether there is a device having the function based on the function required by the application and the device specific information. An access management apparatus that manages access requests to devices from a plurality of applications,
An information storage unit for storing device-specific information representing the function and performance of the device accessed from the application and device state information representing a use state of only the device being executed;
A device management unit that performs a conflict determination based on the received access request and the device status information, and grants a device execution right to the application when it is determined that there is no conflict,
A device exchange determination unit that determines whether there is a replaceable device based on the access request and the device specific information when a conflict is determined by the device management unit;
The device management unit, when it is determined by the device replacement determination unit that there is a replaceable device, gives the execution right to the replaceable device. An access management method for managing access requests to devices from a plurality of applications,
An information storage step for storing device-specific information representing a function or performance of a device accessed from the application and device state information representing a use state of the device;
A device management step of granting an execution right of the device to the application based on the received access request;
A contention determination step for determining whether the right to execute the device requested by the application can be granted based on the access request and the device status information;
A device replacement determination step for determining whether there is a replaceable device based on the access request and the device specific information when it is determined that the execution right cannot be granted,
In the device management step, when it is determined in the device replacement determination step that there is a replaceable device, the execution right is given to the replaceable device. A program for causing a computer to manage access requests to devices from a plurality of applications,
An information storage step for storing device-specific information representing a function or performance of a device accessed from the application, and device state information representing a use state of the device;
A device management step of granting an execution right of the device to the application based on the received access request;
A contention determination step for determining whether the right to execute the device requested by the application can be granted based on the access request and the device status information;
A device replacement determination step for determining whether there is a replaceable device based on the access request and the device specific information when it is determined that the execution right cannot be granted,
The device management step gives the execution right to the replaceable device when it is determined in the device replacement determination step that there is a replaceable device.

Images