Patent Application
20140297636
This technique relates to a management technique of a computer system.
In order to provide configuration information of an Information and Communication Technology (ICT) system for clients of the ICT system, there is a case where a Federated Configuration Management Database (FCMDB or Federated CMDB) is used as illustrated in
The FCMDB stores data regarding configuration items (CI or component item) and relationships among the configuration items. The CI is a part such as a server, storage product, software or the like, which is included in the ICT system.
For example, in
The MDR may be updated by manually inputting data by an administrator or the like or by automatically obtaining data from the ICT system. After that, the update of MDR is reflected to the FCMDB.
Such a processing to reflect the update of the MDR to the FCMDB is not performed for each update of data regarding one CI in the MDR. Then, a mode is considered that data of the CIs updated within an update interval, which is determined by any method, is transmitted collectively as plural update requests to the FCMDB. In such a case, for example, in case where the update intervals of plural MDRs are different, even when CIs are updated at the almost same timing, the update requests for data regarding such CIs may be transmitted at different timings. As illustrated in
Moreover, in case where the update of the MDR is manually performed, the administrator may forget the update to be performed simultaneously for data regarding CI.
When there is difference between the state of a CI in the FCMDB and the state of an actual CI, any trouble occurs when, by referring to the FCMDB, the configuration change is instructed, service deployment is instructed or patch is applied. For example, regardless of a state where Service1 that is an associated CI cannot be used because a network disconnection error occurs, a case occurs that the reflection to the FCMDB is not performed simultaneously because of any reason. In such a case, after confirming that the attribute value of an attribute “Status” of Service1 is still “normal”, the configuration change to provide Service1 for a customer may be performed. Of course, when the customer tries to use Service1, it is impossible to use Service1, because of the error.
As a method for solving such a problem, there is a method for checking other CIs to be updated, at the update of a CI, by using the number of times that CIs are simultaneously updated and a ratio of simultaneous updates of CIs at the update of the CI. However, according to this method, there is a problem that the calculation amount becomes very large when there are the huge number of CIs.
However, there is no conventional technique for detecting a problem such as update omission of the configuration information with a low processing load.
An information processing method relating to a first aspect of this technique includes (A) upon receiving a request to change an attribute value of a certain attribute for a certain configuration item included in a system, determining whether there is a first pattern that includes a first condition, which is satisfied with change relating to the request, among plural patterns, wherein each of the plural patterns includes a first condition relating to a certain change of an attribute value of an attribute for a first configuration item included in the system and a second condition relating to an attribute value of an attribute, which is to be changed at a same timing as the certain change, for a second configuration item that has a predetermined relation with the first configuration item; (B) upon determining that there is the first pattern, determining whether a second condition of the first pattern is satisfied, based on at least either of another request to be processed with the request and a data storage unit that stores information of configuration items included in the system and whose information of the configuration items is updated by the request; and (C) upon determining the second condition of the first pattern is satisfied, performing a predetermined processing.
An information processing method relating to a second aspect of this technique includes (A) determining, for each of plural requests, each of which an attribute value of an attribute for a configuration item included in a system is to be changed, whether it is possible to reach a configuration item relating to another request of the plural requests from a configuration item relating to the request, by tracing one or plural relationships between configuration items, within a predetermined range among predefined relationships among configuration items included in the system, wherein the plural requests are received at predetermined timings that are presumed to be simultaneous; and (B) upon determining that it is possible to reach a first configuration item relating to a first request of the plural requests from a second configuration item relating to a second request, generating a pattern that includes a first condition relating to change of an attribute value of an attribute for the second configuration relating to the second request and a second condition relating to change of an attribute value of an attribute for the first configuration relating to the first request.
The object and advantages of the embodiment will be realized and attained by means of the elements and combinations particularly pointed out in the claims.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory and are not restrictive of the embodiment, as claimed.
Then, the FCMDB system 100 has an update request processing unit 101, a first data storage unit 102, a FCMDB 103, a relation update processing unit 104, an update pattern generator 105, an update pattern storage unit 106, a pattern matching unit 107, a second data storage unit 108 and an instruction processing unit 109.
The update request processing unit 101 receives an update request from each MDR, and stores the update request into the first data storage unit 102. In the following, update requests for CIs that are presumed to be simultaneously updated are collectively processed. The update requests for CIs that are presumed to be simultaneously updated may include a certain update request and other update requests that are received within a predetermined time since the certain update request was received. Moreover, time slots are defined in the update request processing unit 101, and the update requests that are received in the same time slot may be treated as the update requests for CIs that are presumed to be simultaneously updated. Furthermore, according to circumstances, plural update requests that are received at once may be treated as the update requests for CIs that are presumed to be simultaneously updated.
In this embodiment, the update request processing unit 101 updates the FCMDB 103 according to the update requests, and stores data before change in the first data storage unit 102 for the later processing.
The relation update processing unit 104 processes the update request for the relationship between configuration items, which is stored in the first data storage unit 102, to update an update pattern stored in the update pattern storage unit 106. The update pattern generator 105 performs a processing for generating an update pattern by using the update requests for CIs that are presumed to be simultaneously updated, which are stored in the first data storage unit 102, and stores the generated update pattern into the update pattern storage unit 106. The update pattern generator 105 includes a confidence degree calculation unit 1051.
The pattern matching unit 107 applies the update pattern stored in the update pattern storage unit 106 to the update requests for CIs that are presumed to be simultaneously updated, which are stored in the first data storage unit 102, to perform a processing to extract attributes of other CIs, which should be simultaneously updated, however, have not been updated, and stores processing results into the second data storage unit 108, and notifies the user of processing results after performing a predetermined processing.
The instruction processing unit 109 receives an update instruction from the user terminal 200 for the attributes of CI to be updated, and updates the confidence degree of the update pattern in the update pattern storage unit 106 and/or update the FCMDB 103.
In this embodiment, an update pattern is generated from plural update requests for CIs that are presumed to be simultaneously updated. For example, it is assumed that CIs as illustrated in
In such a state, it is assumed that the update requests as illustrated in
After that, when only an update request to change the attribute value of the attribute “Port0” of Switch1 to “NG” is received at a certain timing, data as illustrated in
For example, data as described below is stored in the FCMDB 103. For example, as illustrated in
Specific processing contents to perform the update pattern generation and update pattern application, which were simply described above, will be explained by using
Firstly, the update request processing unit 101 of the FCMDB system 100 receives an update request from each MDR, and stores data of the update request into the first data storage unit 102 (
Then, the update request processing unit 101 updates the FCMDB 103 according to the update requests (step S3). However, before the update, attribute values before change for the CIs or relationships, which relate to the update requests, are obtained, and stored in the first data storage unit 102.
Then, the relation update processing unit 104 determines whether or not the update of the relationship (add, change or delete. Here, the deletion of the CI is included.) is included in the update requests stored in the first data storage unit 102 (step S5). When the update of the relationship is not included in the update requests stored in the first data storage unit 102, the relation update processing unit 104 does not perform any processing, and the processing shifts to step S13. On the other hand, when the update of the relationship is included in the update requests, the relation update processing unit 104 identifies an unprocessed update request relating to the update of the relationship (step S7). Then, the relation update processing unit 104 performs a relation update processing for the identified update request (step S9). The relation update processing will be explained by using
The relation update processing unit 104 determines whether or not the identified update request is an addition of a relationship R (
When the identified update request is the change of the relationship R, the relation update processing unit 104 determines whether or not each update pattern stored in the update pattern storage unit 106 is an update pattern that utilizes the relationship before change, and when the update pattern is the update pattern that utilizes the relationship before change, the relation update processing unit 104 deletes the update pattern that utilizes the relationship before change (step S25). Then, the processing returns to the calling-source processing.
As simply described above, in the update pattern, a condition and warning condition are set for two CIs that can be traced along relationships within predetermined hops n. Therefore, there is a case where, when the relationship before change is deleted, it becomes impossible to trace the relationships between the source CI and the target CI within n hops. As illustrated in
Although the update pattern is not generated in the relationship update processing, the relationship from C to D is newly set in
When the identified update request is not the change of the relationship R, the relation update processing unit 104 determines whether or not the identified update request is deletion of the relationship R (step S27). When the identified update request is the deletion of the relationship R, the relation update processing unit 104 deletes an update pattern that utilizes the deleted relationship (step S29). Then, the processing returns to the calling-source processing. As illustrated in
In this embodiment, the update request to request the deletion of CI is also treated as the update of the relationship. Therefore, when the identified update request is not the deletion of the relationship R, the relation update processing unit 104 deletes an update pattern that utilizes the relationship relating to the deleted CI (step S31). Then, the processing returns to the calling-source processing. As illustrated in
By carrying out the aforementioned processing, it is possible to cope with the update pattern that is influenced by the update of the relationship.
Returning to the explanation of the processing in
On the other hand, when the update of the configuration item CI is included in the update requests, the update pattern generator 105 performs an update pattern generation processing (step S15). This update pattern generation processing will be explained by using
The update pattern generator 105 identifies one unprocessed configuration item C to be updated, from the update requests stored in the first data storage unit 102 (
For example, it is assumed that data as illustrated in
Then, the update pattern generator 105 initializes a counter i for the number of hops to “1” (step S45). After that, the update pattern generator 105 identifies the configuration item D that is disposed “i” hops ahead from the configuration item C (step S47). For example, in case of i=1, in
After that, the update pattern generator 105 determines whether or not the configuration item D was identified (step S49). As described above, because the trace is performed only between configuration items for which the relationships between the configuration items are defined, it is impossible to identify the configuration item at the next hop unless the relationship is defined at the edge configuration items such as Service1 and Server2 in
On the other hand, when the configuration item D can be identified, the update pattern generator 105 identifies one unprocessed configuration item D (step S51). Then, the update pattern generator 105 determines whether or not the update requests occur simultaneously, by checking whether or not an update request for this configuration item D is stored in the first data storage unit 102 (step S53). When no update request for this configuration item D is stored in the first data storage unit 102, no update occurs simultaneously. Therefore, the processing shifts to step S63 in
In the example of
On the other hand, when the update request for this configuration item D is stored in the first data storage unit 102 and the updates occur simultaneously, the update pattern generator 105 extracts data before change for the configuration item D from the first data storage unit 102 (step S55). Then, the processing shifts to a processing in
In case of the configuration item Service1, when the update request in the second line of
Shifting to the explanation of the processing in
On the other hand, when the same update pattern has not been registered, the confidence degree calculation unit 1051 of the update pattern generator 105 calculates a confidence degree based on the number of hops i (step S59). In this embodiment, when the configuration item C and configuration item D are nearer, the confidence degree becomes higher. Therefore, when the number of hops i is lesser, the confidence degree becomes higher. Therefore, 1/(the number of hops) is calculated as the confidence degree, for example. As illustrated in
Then, the update pattern generator 105 generates an update pattern including the difference data due to the update, which was extracted at the step S43, as the condition, and including the data before change, which was extracted at the step S55, as the warning condition, from the difference data due to the update, which was extracted at the step S43, and the data before change, which was extracted at the step S55, and stores the generated update pattern and the confidence degree calculated at the step S59, into the update pattern storage unit 106 (step S61). Therefore, in this embodiment, data as illustrated in
The update pattern generator 105 determines whether or not there is an unprocessed configuration item D among configuration items D identified at the step S47 (step S63). When there is an unprocessed configuration item D, the processing returns to the step S51 in
Thus, as for two update requests, when those configuration items are connected through the relationship and they are placed in a range within the upper limit value for the number of hops, two update patterns are generated. As for three update requests, when those configuration items are connected through the relationships and they are placed in a range within the upper limit value for the number of hops, 6 (=3*2) update patterns are generated.
Returning to the processing in
The pattern matching unit 107 identifies one unprocessed configuration item relating to the update requests stored in the first data storage unit 102 (step S71). Then, the pattern matching unit 107 searches the update pattern storage unit 106 for an update pattern for the identified configuration item (step S73).
The pattern matching unit 107 determines whether or not a condition included in the detected update pattern is satisfied (step S75). In this embodiment, because the attribute value before change and the attribute value after change for a specific attribute of the configuration item are included in the condition, it is determined based on the data before change, which is stored in the first data storage unit 102, and the data after change, which is stored in the FCMDB 103, whether or not the condition is satisfied.
When the condition included in the detected update pattern is not satisfied or no update pattern is detected, the processing shifts to a processing in
On the other hand, when the condition included in the detected update pattern is satisfied, the pattern matching unit 107 searches the FCMDB 103 for the configuration item relating to the warning condition of the detected update pattern (step S77), and reads out an attribute value of an attribute defined in the warning condition for the detected configuration item, and further determines whether or not the read attribute value is identical to the attribute value defined in the warning condition (step S79). Because the attribute value before change is included in the warning condition, it can be determined that the warning condition is satisfied, when the attribute value before change is still registered in the FCMDB 103.
When the attribute value in the FCMDB 103 is not identical to the attribute value included in the warning condition, the processing shifts to the processing in
On the other hand, when the attribute value in the FCMDB 103 is identical to the attribute value included in the warning condition, the pattern matching unit 107 stores the detected update pattern in the second data storage unit 108 (step S81). Then, the processing shifts to the processing in
Shifting to the explanation of the processing in
On the other hand, when there is not unprocessed configuration item relating to the update requests, the pattern matching unit 107 sorts the update patterns extracted in the aforementioned processing in descending order of the confidence degrees of the update patterns (step S85).
Then, as for the update patterns whose confidence degree is equal to or greater than a threshold, the pattern matching unit 107 obtains an attribute value of an attribute for the configuration item relating to the warning condition from a pertinent MDR, and performs the update for the FCMDB 103 (step S87). As for the update patterns whose confidence degree is equal to or greater than the threshold, the data after change is obtained at this timing from MDR to forcibly update the FCMDB 103, if the arrival of the update request is delayed. If the data after change, which was obtained from MDR, is different from a present value in the FCMDB 103, the update is performed for the FCMDB 103. On the other hand, when the data after change, which was obtained from MDR, is the same as the present value in the FCMDB 103, there is possibility of the omission of the update.
Moreover, the pattern matching unit 107 generates notification data to an administrator from the update pattern stored in the second data storage unit 108 (step S89). The notification data including the condition and the warning condition of the update pattern may be simply generated, and after identifying an attribute of a configuration item that has not been updated from the warning condition of the update pattern, data to prompt the update of the attribute of that configuration item may be generated. The notification data may be generated for the update pattern whose confidence degree is equal to or greater than a second threshold. Furthermore, the update patterns may be narrowed to the top n update patterns in descending order of the confidence degree.
For example, when the attribute “Status” of Service1 in the FCMDB 103 is still “normal”, notification data representing the attribute of Service1 is still “normal”. In such a case, because it is determined at the step S75 that the condition of the update pattern in the second line of
Then, the pattern matching unit 107 transmits the generated notification data to the administrator who is preregistered (step S91). The notification data may be transmitted via e-mail to the administrator and may be transmitted in response to an access from the user terminal 200. Furthermore, when a monitor program is activated in the user terminal 200, the notification data may be transmitted at real time, and may be displayed on a display device of the user terminal 200 at real time.
When the aforementioned processing is performed, it is possible to appropriately register the update patterns for the update requests that were received at timings that are presumed to be simultaneous, and after that, when an update request that follows this update pattern is not received at the timings that are presumed to be simultaneous, the update pattern that was not followed can be extracted. A processing amount of the matching processing itself is not so much, and the omission of the update can be identified with low processing load.
As described above, the extracted update pattern may be notified to the administrator, and according to the confidence degree, the update for the MDR may be automatically applied to the FCMDB 103. Furthermore, when the gap between the transmission timings of the update requests is a problem, a request to adjust the transmission timing to the MDR side may be sent or a warning to adjust the transmission timing of the update request may be made for the administrator side.
When plural update patterns are detected at the step S73 in
Next, a processing after the administrator confirmed the notification data at the user terminal 200 will be explained by using
Here, it is assumed that the administrator selects a configuration item of an update pattern to be updated among update patterns included in the notification data that is displayed on the display device of the user terminal 200 (or an attribute of a configuration item, which is included in that warning condition), and inputs an attribute and attribute value after change for the selected configuration item. Then, the user terminal 200 transmits a configuration item update instruction including the configuration item, attribute and attribute value after change to the FCMDB system 100. The configuration item update instruction may include an identifier of the update pattern.
The instruction processing unit 109 receives the configuration item update instruction from the administrator from the user terminal 200 (
Moreover, the instruction processing unit 109 identifies the update pattern corresponding to the configuration item update instruction among the update patterns stored in the second data storage unit 108 (step S103). The update pattern whose configuration item and attribute, which are included in the warning condition, are identical to the configuration item and attribute, which are included in the configuration item update instruction, is identified. When the configuration item update instruction to change the attribute value of the attribute “Status” of Service1 to the attribute value “error” is received, the update pattern in the second line of
Then, the instruction processing unit 109 increases the confidence degree of the identified update pattern according to the predetermined rule (step S105). For example, a predetermined value may be added or a value that is greater than 1 may be multiplied.
Moreover, the instruction processing unit 109 decreases the confidence degree for update patterns (i.e. remaining update patterns) other than the update pattern identified at the step S103 among the update patterns stored in the second data storage unit 108, according to the predetermined rule (step S107). For example, a predetermined value may be subtracted, or a value that is greater than 0 and less than 1 may be multiplied.
Then, at this stage, the instruction processing unit 109 determines whether or not the update pattern whose confidence degree is less than a threshold (e.g. less than 0) is stored in the update pattern storage unit 106 (step S109). When there is the update pattern whose confidence degree is less than the threshold, the instruction processing unit 109 deletes the update pattern whose confidence degree is less than the threshold (step S111). Then, the processing ends. On the other hand, when there is no update pattern whose confidence degree is less than the threshold, the processing ends.
When the processing is carried out up to this step, the instruction processing unit 109 discards data for the update pattern associated with a group of update requests for the configuration items that are presumed to be simultaneously updated among data stored in the second data storage unit 108.
By carrying out the aforementioned processing, when the notification is sent to the administrator, the confidence degree can be decreased for the update pattern for the configuration item for which the update is not instructed by the administrator, and the confidence degree can be increased for the update pattern for the configuration item for which the update is instructed by the administrator. Thus, the update pattern for the configuration item that is updated after the confirmation by the administrator is managed in the update pattern storage unit 106 as the credible update pattern.
Although the embodiments of this technique were explained, this technique is not limited to those.
For example, the format of the update pattern, which was described above, is a mere example, and is not always employed. Specifically, the condition includes the attribute value before change, however, when the change to the attribute value after change is important, the attribute value before change may not be registered. Similarly, the attribute value before change is registered in the warning condition, however, when it is important that the change to the attribute value after change is not made, the attribute value after change may be included in the warning condition instead of the attribute value before change, and it may be determined that the warning condition is satisfied when “a value to be checked is not identical to the attribute value after change”. Furthermore, the warning condition may include the attribute value after change in addition to the attribute value before change. Thus, it may be determined that the warning condition is satisfied when “the change of the attribute value, which is defined in the warning condition, is not correctly performed”.
In the aforementioned example, the update request is initially applied to the FCMDB 103, however, the update request may be applied later. In such a case, because the relationship update processing is performed in a state that the update of the relationship is not performed, a processing to trace the relationship by taking into consideration the update of the relationship relating to the update request is performed. Moreover, whether or not the condition and warning condition are satisfied is determined after confirming the update request that is not applied and the contents of the FCMDB 103.
Furthermore, as long as the processing result does not change, the turn of the processing step may be exchanged, or processing steps may be executed in parallel.
Moreover, the functional block diagram in
Furthermore, the FCMDB system 100 may be implemented by one or plural computers.
In addition, the aforementioned FCMDB system 100 is a computer device as illustrated in
The aforementioned embodiments are outlined as follows:
A pattern application method relating to a first aspect of the embodiments includes (A) upon receiving a request to change an attribute value of a certain attribute for a certain configuration item included in a system, determining whether there is a first pattern that includes a first condition, which is satisfied with change relating to the request, among plural patterns, wherein each of the plural patterns includes a first condition relating to a certain change of an attribute value of an attribute for a first configuration item included in the system and a second condition relating to an attribute value of an attribute, which is to be changed at a same timing as the certain change, for a second configuration item that has a predetermined relation with the first configuration item; (B) upon determining that there is the first pattern, determining whether a second condition of the first pattern is satisfied, based on at least either of another request to be processed with the request and a data storage unit that stores information of configuration items included in the system and whose information of the configuration items is updated by the request; and (C) upon determining the second condition of the first pattern is satisfied, performing a predetermined processing.
Thus, it is possible to confirm whether or not updates for plural configuration items are performed at the same timing along a pattern that represents the simultaneous updates, and when the updates for plural configuration items are not performed at the same timing along the pattern that represents the simultaneous updates, there is omission of the update. Therefore, it becomes possible to notify a user such as an administrator or automatically perform the update. The processing load of such a matching processing is not so high, and it becomes possible to extract the problem at low processing load.
Moreover, the aforementioned pattern may include a confidence degree of the pattern. In such a case, the aforementioned predetermined processing may include: upon detecting there are plural first patterns whose first and second conditions are satisfied, generating data to be notified to an administrator, for at least one of the first patterns whose first and second conditions are satisfied, according to the confidence degree. Thus, the administrator can perform various kinds of actions after confirming the omission of the update. When the first patterns are displayed in descending order of the confidence degree for the administrator, it is possible to take any action for much reliable omission of the update.
Furthermore, the aforementioned pattern may include a confidence degree of the pattern. In such a case, the predetermined processing may include: upon detecting that a confidence degree of the first pattern whose first and second conditions are satisfied is equal to or greater than a threshold, obtaining data of an attribute defined in the second condition of the first pattern whose first and second conditions are satisfied, from a second data storage unit that stores information that is an origin of the information of the configuration items, which is stored in the data storage unit. By carrying out such a processing, it becomes possible to cope with a case where the delay of the update occurs. When the confidence degree is high, there is a case where the update of the data storage unit can be performed automatically.
Furthermore, this pattern application method may include: increasing a confidence degree of a first pattern, for which change of an attribute relating to a second condition is instructed by the administrator, among the plural first patterns whose first and second conditions are satisfied and that were notified to the administrator; and decreasing a confidence degree of a pattern for which change of the attribute relating to the second condition is not instructed by the administrator. By updating the confidence degree as described above, it is possible to extract much credible patterns.
Moreover, a pattern generation method relating to a second aspect of the embodiments includes: (A) determining, for each of plural requests, each of which an attribute value of an attribute for a configuration item included in a system is to be changed, whether it is possible to reach a configuration item relating to another request of the plural requests from a configuration item relating to the request, by tracing one or plural relationships between configuration items, within a predetermined range among predefined relationships among configuration items included in the system, wherein the plural requests are received at predetermined timings that are presumed to be simultaneous; and (B) upon determining that it is possible to reach a first configuration item relating to a first request of the plural requests from a second configuration item relating to a second request, generating a pattern that includes a first condition relating to change of an attribute value of an attribute for the second configuration item relating to the second request and a second condition relating to change of an attribute value of an attribute for the first configuration item relating to the first request.
Thus, a pattern that represents the simultaneous update is generated for configuration items whose association is guaranteed to some degree.
Moreover, the first condition may include attribute values before and after change or the attribute value after change, and the second condition may include an attribute value before change, an attribute value after change, or attribute values before and after change. It is possible to variously define the aforementioned first and second conditions.
Furthermore, the pattern generation method relating to the second aspect of the embodiments may include: upon receiving a request to change or delete a relationship between configuration items included in the system or a request to delete any configuration item, deleting a pattern that was generated by tracing a relationship defined for the relationship before change, the deleted relationship, or deleted configuration item. When the relationship is changed or deleted, a case occurs that the relationship between configuration items cannot be traced. This processing is carried out for this case.
Furthermore, the pattern generation method relating to the second aspect of the embodiments may include: calculating a confidence degree according to the number of configuration items, through which the tracing is performed from the second configuration item to the first configuration item, and storing the calculated confidence degree in association with the pattern. For example, a reciprocal of the number of configuration items, which is described above, may be employed as the confidence degree. In other words, a higher confidence degree may be set for the pattern for the nearer configuration item. Thus, it also becomes possible to extract a pattern that is much reliable when the matching processing is performed.
Incidentally, it is possible to create a program causing a computer to execute the aforementioned processing, and such a program is stored in a computer readable storage medium or storage device such as a flexible disk, CD-ROM, DVD-ROM, magneto-optic disk, a semiconductor memory, and hard disk. In addition, the intermediate processing result is temporarily stored in a storage device such as a main memory or the like.
All examples and conditional language recited herein are intended for pedagogical purposes to aid the reader in understanding the invention and the concepts contributed by the inventor to furthering the art, and are to be construed as being without limitation to such specifically recited examples and conditions, nor does the organization of such examples in the specification relate to a showing of the superiority and inferiority of the invention. Although the embodiments of the present inventions have been described in detail, it should be understood that the various changes, substitutions, and alterations could be made hereto without departing from the spirit and scope of the invention.
This application is a continuing application, filed under 35 U.S.C. section 111(a), of International Application PCT/JP2012/051844, filed on Jan. 27, 2012, the entire contents of which are incorporated herein by reference.
| Number | Date | Country | |
|---|---|---|---|
| Parent | PCT/JP2012/051844 | Jan 2012 | US |
| Child | 14307549 | US |
