JP4688591B2 - Object control apparatus and control method thereof - Google Patents

Description

  The present invention relates to an object control apparatus and a control method therefor.

In an object control apparatus such as that realized in Java (registered trademark), the class of an object managed by a thread and the name of a method are stored in a call stack by a Java (registered trademark) virtual machine in the computer. An access controller (Non-Patent Document 1) can know the class and method of an object by referring to this call stack (Non-Patent Document 2).
JP-A-9-212346 Scott Oaks, Java security, O 'REILLY, 2001 pp.97-133 Java (registered trademark) Language Specification Second Edition OSGi Service Platform Release 3, 2003 Masaru Iijima, Distributed Object Model with Delegation of Authority Based on Organizational Structure, IEICE Transactions, DI, Vol.J79-DI, No.10, pp.656-668, 1996

  However, what can be known is only the class and method of the object, and the object managed by the thread cannot be known. Note that even if you refer to the call stack, if the class and method names are the same as others, you cannot even identify them. In addition, although inter-object communication is performed in such a computer, this is not actually communication after identifying an object, such as communication with a designated object.

  By the way, in recent years, it is sometimes necessary to set unique ownership and access rights to each of a plurality of objects generated from the same class, and to disclose information only to objects having specific ownerships. . For example, an object that communicates with a television receiver connected to a home network, an object that communicates with a television receiver in a living room, and an object that communicates with a television receiver in a study Then, since ownership is different, it is necessary to identify them.

  However, the access controller could not identify such an object unit.

  Also, from the viewpoint of security, there are cases where the alteration of an object indirectly is prevented by preventing the alteration to a program (such as source code) including a class. However, this does not prevent tampering for each object, but prevents tampering of all the objects managed by threads generated by classes in this program by preventing tampering of the program. I'm just doing it.

  On the other hand, when a platform such as OSGi for cooperating programs created by different vendors is used with a Java (registered trademark) virtual machine, an object is registered in the platform as a service and used mutually (Non-Patent Document). 3). For identification of this service, the Service. Although id and Service.pid are used, since browsing is permitted, there exists a possibility that it may be used for the call of the object by a fake object (service).

  When such a platform is used, a bundle ID stack in which a bundle ID indicating a program executed when an object is generated (OSGi refers to a program necessary for a series of operations is referred to as a bundle) is referred to. By doing this, it is possible to know the bundle ID, but this is only the bundle ID, and the managed object cannot be known.

  Apart from these cases, a method for uniquely giving an identifier to each object has been proposed (Non-Patent Document 3). However, a technique for preventing a call by a fake object is not disclosed, and therefore, such a call may be performed. Therefore, it is necessary to ensure the reliability of the object identifier.

  Moreover, in the field of distributed objects, a call by a fake object can be prevented by using a public key cryptosystem using a key pair unique to each object instead of an identifier (Non-patent Document 4). However, since each object generates a secret key, it is necessary for each object to perform a heavy load process of generating a highly reliable secret key. Also, it is necessary to decrypt the public key encryption for each object call, and if the number of object calls increases, the performance of the computer may decrease.

  The present invention has been made in view of the above problems, and an object of the present invention is to provide an object control apparatus capable of identifying an object used for a thread and a control method therefor.

In order to solve the above problem, the present invention of claim 1 generates a thread and an object used for the thread by executing a class included in a bundle that is a program that can be executed in a computer. And the bundle ID of the bundle executed when the other object is generated after the bundle ID indicating the executed bundle is stored when the other object receives the processing request from the object. In the object control device, which is a computer having a bundle ID stack in which is stored, a bundle ID storage unit that stores a bundle ID of a selected bundle that is executable in the computer, and in the computer After the object is created, the object When there is a request for generating the object ID of the object, the bundle ID of the bundle executed when the object is generated is acquired from the bundle ID stack, and the acquired bundle ID is the bundle ID storage unit. The object control device includes an object ID generation unit that generates an object ID of the object.

In the present invention of claim 2, the object ID generated by the object ID generation means is stored, and the bundle ID of the bundle executed when the object of the object ID is generated is associated with the object ID. The object control apparatus according to claim 1, further comprising an object ID storage unit .

In the third aspect of the present invention, when an object ID authentication request is received from an object in the computer, it is determined whether or not the object ID is stored in the object ID storage unit. , It is determined whether or not a bundle ID associated with the object ID is stored in the bundle ID storage unit, and if it is stored, an authentication result indicating that the authentication is successful is transmitted to the object. and solutions with a object control system according to claim 2, wherein Rukoto includes an object ID authentication means.

The present invention of claim 4, stores a corresponding container object processing result serving information by the other processing requests for objects and the other objects of a container object is an object that is created in the computer to the container object If the acquisition of the information from the response to a request from an object in the computer to produce the container object to be performed, to authenticate requests for object ID of the object with the object ID authentication means, those authentication The object control apparatus according to claim 3, further comprising: a container generation unit configured to generate a container object when a processing result indicating that has succeeded is transmitted.

The present invention of claim 5, wherein the container generation means, the object ID transmitted from the object making the request in the generation of container object is intended to be stored in the container object, the container object, the When any of the information storage in the container object, information operation in the container object, and information acquisition from the container object is requested from the object in the computer, the object ID of the object is stored in the container object. It determines whether it is stored, if it is stored, when the authenticate request object ID of the object in the object ID authentication means, the processing result indicating that the person authentication is successful is transmitted Responding to the request And solutions with a object control system according to claim 4, wherein.

According to the present invention of claim 6, the object is sent to another object accompanied by the presence notification of the container object by a request made to the object in the computer accompanied by the presence notification of the container object generated by the container generation means . Make a request to the object that receives the request first among the objects that receive any request in the instruction content that the request is to be performed more than once in a chain, and send the instruction content to the object notification object to the said container generation means the part of the object ID in the object ID of each object receive either request in the instruction content performs a request for production of the container object to Conte Nao請, characterized in that stored in the object With a object control device of claim 5, wherein the solution.

According to the seventh aspect of the present invention, a thread and an object used for the thread are generated by executing a class included in a bundle that is a program that can be executed in a computer, and processing from the object is performed. A bundle ID stack that stores the bundle ID of the bundle executed when the other object is generated after the bundle ID indicating the executed bundle is stored when the other object receives the request the control method for object control device is a computer provided with a bundle ID storage unit bundle ID bundles execution within the computer has been selected a bundle that can be stored is the object control device, the Object ID generation means in the computer After the object in the computer is generated, acquired when a request for generating from the object of the object ID of the object, the bundle ID of the bundle which is executed when the corresponding object is generated from the bundle ID stack And determining whether or not the acquired bundle ID is stored in the bundle ID storage unit and, if stored, generating an object ID of the object, with a control method for an object control device, Let it be a solution.

In the present invention of claim 8, the object ID generated by the object ID generation means is stored, and the bundle ID of the bundle executed when the object of the object ID is generated is associated with the object ID. object ID storage unit and solutions with a control method of an object control system according to claim 7, wherein the Ru feature the object control device.

According to the ninth aspect of the present invention , when the object ID authenticating means in the computer requests an object ID authentication from an object in the computer, whether or not the object ID is stored in the object ID storage unit. If it is stored, it is determined whether or not the bundle ID associated with the object ID is stored in the bundle ID storage unit, and if it is stored, the authentication is successful. an authentication result indicating that the solutions have a control method of an object control device according to claim 8, wherein that you send to the object.

The present invention of claim 10, the container generation means in said computer, processing by the other processing requests for objects and the other objects of a container object is an object that is created in the computer to the container object When there is a request from the object in the computer to generate the container object for storing the resulting information and acquiring the information from the container object, the object ID authenticating means stores the object ID of the object. authenticate request, if the processing result indicating that the person authentication is successful is transmitted, and solutions with a control method of an object control system according to claim 9, wherein the generating the container object .

The present invention of claim 11, wherein the container generation means, the object ID transmitted from the object making the request in the generation of container object is intended to be stored in the container object, the container object, the When any of the information storage in the container object, information operation in the container object, and information acquisition from the container object is requested from the object in the computer, the object ID of the object is stored in the container object. It determines whether it is stored, if it is stored, when the authenticate request object ID of the object in the object ID authentication means, the processing result indicating that the person authentication is successful is transmitted Responding to the request The and solutions with a control method of an object control system according to claim 10, wherein.

The present invention of claim 12 is directed to requesting an object in the computer to be accompanied by a container object existence notification generated by the container generation means, so that the object is sent to another object accompanied by the container object existence notification. Make a request to the object that receives the request first among the objects that receive any request in the instruction content that the request is to be performed more than once in a chain, and send the instruction content to the object notification object to the said container generation means the part of the object ID in the object ID of each object receive either request in the instruction content performs a request for production of the container object to Conte Nao and to store the object With a control method of an object control device Motomeko 11 described and solutions.

  According to the present invention, the bundle ID is stored in the bundle ID storage unit in advance, and when there is a request for generating the object ID, the bundle ID of the bundle executed when the object is generated is acquired from the bundle ID stack. Then, it is determined whether or not the acquired bundle ID is stored in the bundle ID storage unit. If the bundle ID is stored, the bundle ID of the trusted bundle is stored in the bundle ID storage unit by generating the object ID. In this case, only the object ID of the object generated by executing the trusted bundle is generated, and thus the object generated by executing the trusted bundle can be identified.

  Also, an object ID generated by the object ID generation object is stored, an object ID storage unit associated with a bundle ID of a bundle executed when the object of the object ID is generated, and an object ID authentication request If there is an object ID, it is determined whether or not the object ID is stored in the object ID storage unit. If it is stored, whether or not the bundle ID associated with the object ID is stored in the bundle ID storage unit. And the object ID authentication object that transmits the authentication result indicating that the authentication has succeeded is provided, the authentication fails with the fake object ID. Use can be prevented. In addition, since the encryption and decryption of information are not required, it is possible to prevent a decrease in computer performance.

  In addition, when there is a request to generate a container object, a request for object ID authentication is made to the object ID authentication object, and when a processing result indicating that the authentication is successful is transmitted, a container generation for generating a container object is generated. By providing an object, authentication fails with a fake object ID, and therefore it is possible to prevent a container object from being generated using a fake object ID.

  In addition, the container generation object stores the object ID to be transmitted in the container object, and the container object has its object ID when any of the information storage, information operation, and information acquisition requests is received from the object. Is stored in the container object, and if it is stored, a request for authentication of the object ID is made. If a processing result indicating that the authentication is successful is transmitted, the request can be satisfied. Thus, authentication fails with a fake object ID, and therefore it is possible to prevent a fake object ID from being used to store information in a container object, perform information manipulation, and acquire information.

  In addition, in the instruction content that the object makes a request to another object accompanied by the container object existence notification by the request made to the object accompanied by the container object existence notice in a chained manner twice or more. Among the objects that receive any of the above requests, the object that first requests the object that receives the request, and the object that notifies the object of the instruction content requests the container generation object to generate the container object and instructs By transmitting a part of the object IDs of the object IDs of the objects receiving any request in the contents to the container generated object, the container generated object itself is not stored in the container object and is not transmitted. The object ID is not stored in the container object, and even if the object with the object ID makes a request to the container object, the authentication fails with the object ID. Therefore, all the objects cooperate to process the instruction content. In addition, information can be prohibited from being stored in the container object, information manipulation, and information acquisition for some of the objects.

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

  FIG. 1 is a configuration diagram of a home network system to which an object control device and a control method thereof according to the present embodiment are applied.

  The home server 1 includes a telephone terminal 2 having a telephone function, a computer 3 having a schedule management function, an address book 21 which is data storing a telephone number, and a user ID of a user who performs a scheduled event, a scheduled time, and a scheduled event. The home server 1 corresponds to the object control device of the present invention. The home server 1 is a computer connected to the database system 4 in which the schedule data 31 having a plurality of sets is stored.

  The home server 1 is executed when an object is generated, a virtual machine 11 in which computer hardware is virtually realized by software, a platform 12 for managing threads and objects configured in the home server 1, and A bundle storage unit 13 that stores one or more bundles that are programs, and a bundle ID that stores bundle identifiers that can be executed in the home server 1 and that are selected bundles (hereinafter, identifiers are referred to as IDs). The storage unit 14 includes an object ID storage unit 15 in which the object ID of an object that is an object configured in the home server 1 and has an object ID that is an ID of the object is stored.

  The bundle storage unit 13 includes a program (bundle) including a program (class) for communicating with the telephone terminal 2 and a bundle 130 created by a trusted vendor and a schedule management unit 3A in the computer 3. A bundle 131 which is a program (bundle) including a program (class) for communication and created by a trusted vendor is stored. The bundle storage unit 13 may store other arbitrary bundles.

  In the platform 12, one of the bundles stored in the bundle storage unit 13 is executed, so that a processing unit called a thread is first configured. The thread generates one or more objects in the home server 1. Then, one of the objects makes a request to another object or another object generated by another thread, and the object makes a request to the other object. The thread that created the object is managed.

  In the home server 1, a thread 120 is configured by executing the bundle 130. Further, objects 160, 165, 1651, 1652 and 1653 are called during the operation.

  Further, the thread 121 is configured by executing the bundle 131 in the home server 1. Further, objects 161, 163, and 164 that are called during the operation are configured, and the objects 165, 1651, 1652, and 1653 are also called during the operation of the thread 121.

  The object 160 is an object that communicates with the telephone terminal 2 and is configured by executing a certain class in the bundle 130. Hereinafter, the object 160 is referred to as a telephone object 160. The object 161 is an object that communicates with the schedule management unit 3A of the computer 3, and is configured by executing a certain class in the bundle 131. Hereinafter, the object 161 is referred to as a schedule management object 161. The object 163 is an object that sorts a set of scheduled events, scheduled times, and user IDs in the schedule data 31 in order of scheduled times, and by executing a certain class in another bundle stored in the bundle storage unit 13. It is configured. Hereinafter, the object 163 is referred to as a sort object 163. The object 165 is an object that communicates with the database system 4 and is configured by executing a certain class in another bundle stored in the bundle storage unit 13. Hereinafter, the object 165 is referred to as a database system object 165.

  Each of the objects configured in the home server 1 includes a processing unit that performs processing in the home server 1 and a storage unit provided in the home server 1, and the processing unit performs processing on contents stored in the storage unit. In order to conceal this from other objects, it is managed by encryption. Hereinafter, in order to prevent redundancy, the description will be made without using the terms of the processing unit and the storage unit.

  In the platform 12, a bundle ID stack 120A is configured for the thread 120, and a bundle ID stack 121A is configured for the thread 121.

  For example, in the bundle ID stack 120A, a bundle indicating a bundle executed when an object (request source) waiting for execution of processing requested for another object among objects managed by the thread 120 is generated. ID (hereinafter, the bundle ID of the bundle that was executed when the object was generated (which is referred to as the “object bundle ID” for the sake of convenience) is stored. When the bundle ID is stacked (stacked), and the requested object is now the request source, the other object is required to be processed and is waiting for execution, the request destination object When the bundle ID is stacked and the object finishes processing, Le ID is erased, in such a way that the uppermost bundle ID similarly are erased sequentially, each such bundle ID is stacked or erase properly. The same applies to the bundle ID stack 121A.

  All objects in the home server 1 include objects generated for objects that are requested (called) from other objects. An object management unit is configured by three objects generated for one object that is requested to be processed, and the object management unit stores in advance the object ID of the one object, and requests to the one object. Processing is performed only at the time.

  Here, the object management unit 165A manages the database system object 165 that is requested to be processed by another object, and the object management unit 165A includes objects 1651, 1652, and 1653.

  FIG. 2 is a diagram illustrating a configuration of the object management unit 165A and a flow of requests and the like when the object management unit 165A is used.

  Three objects provided in the object management unit 165A will be described. First, the object 1651 generates an object ID of an object to be instructed with instruction contents including processing by the database system object 165 to be managed, and transmits the object ID to the object (hereinafter, object ID). A generated object 1651). The object 1652 is an object that generates a container object in which instruction contents and processing results are stored (hereinafter referred to as a container generation object 1652), and includes an object ID of the database system object 165. The object 1653 is an object (hereinafter referred to as an object ID authentication object 1653) that authenticates an object ID that is transmitted at the time of storing and processing the content of processing instructions to the container object. Three objects similar to the three objects are also provided in another object management unit (not shown) that manages other objects. The flow of requests will be described later.

  FIG. 3 is a diagram illustrating the bundle ID storage unit 14.

  The bundle ID storage unit 14 stores, for example, one or more numerical bundle IDs of bundles that can be executed in the home server 1 and that are selected because the bundle is trusted. These bundle IDs are stored in the bundle ID storage unit 14 as a result of the bundle having the bundle ID being created by, for example, a trusted vendor. Therefore, the bundle ID storage unit 14 stores the bundle IDs of the bundles 130 and 131. The bundle ID storage unit 14 stores the bundle ID of the sort object 163 for the same reason.

  FIG. 4 is a diagram illustrating the object ID storage unit 15.

  The object ID storage unit 15 stores the object ID of the object transmitted to the object configured in the home server 1. The object ID stored in the object ID storage unit 15 includes, for example, a bundle ID (such as B45) of an object having the object ID, a number indicating the order in which the object ID is generated (such as 12), and the object ID. And a random number (such as 485447) generated at the time. Further, the object ID stored in the object ID storage unit 15 is associated with the bundle ID (such as B45) of the object having the object ID.

  The object ID may be unrelated to the bundle ID or the generation order (for example, only a random number). Further, when the access right varies depending on the object, the access right, user name, device name, and object hash value that can be acquired from the virtual machine 11 or the operating system that operates the virtual machine 11 for each object ID. Etc., and detailed control based on these may be performed.

(Operation of this embodiment)
Next, the operation of this embodiment will be described.

  FIG. 5 shows a case where the telephone object 160 called by the thread 120 acquires the address book 21 in the database system 4 via the database system object 165 and transmits it to the telephone terminal 2 in response to a request from the telephone terminal 2. FIG.

  During the operation of the thread 120 generated by executing the bundle 130, the telephone terminal 2 makes a request to the telephone object 160, and the telephone object 160 first sends a request to the object ID generation object 1651 according to the content of the request. A request is made to generate an object ID of the telephone object 160 and transmit it to the telephone object 160 (FIG. 5: step S1). Such a request is generally made with a so-called command and parameter, but in order to help understand the operation, the request will be described below including such a description.

  FIG. 6 is a flowchart of the object ID generation object 1651 that receives such a request.

  When the object ID generation object 1651 receives a request from the telephone object 160 or the like (FIG. 6: YES in step S101), the bundle ID of the telephone object 160 is first stacked (stacked) on the bundle ID stack 120A. Since the bundle ID of the object ID generation object 1651 is stacked thereon, the object ID generation object 1651 obtains the second bundle ID from the top in the bundle ID stack 120A from the platform 12 (FIG. 2, FIG. 6: Step S103).

  Next, the object ID generation object 1651 determines whether or not the bundle ID is stored in the bundle ID storage unit 14 (FIG. 6: step S105). If it is determined that it is stored (YES), for example, a random number is generated, and an object ID including the bundle ID, a number indicating the order of the request, and the random number is generated (FIG. 6: Step S107). .

  Next, the object ID generation object 1651 stores the object ID generated in step S107 in the object ID storage unit 15, and associates the bundle ID acquired in step S103 with the stored object ID (FIG. 6: step). S109: The object ID storage unit 15 is updated).

  Next, the object ID generation object 1651 transmits the object ID generated in step S107 as a processing result to the telephone object 160 that is the request source (FIG. 2, FIG. 6: step S111), and ends the process.

  On the other hand, if NO is determined in step S105, the processing result indicating that the processing could not be performed is transmitted to the requesting telephone object 160 and the processing is ended.

  Returning to FIG. When the processing of the object ID generation object 1651 ends, the bundle ID of the object ID generation object 1651 at the top is deleted in the bundle ID stack 120A, and the bundle ID of the telephone object 160 becomes the highest bundle ID.

  Next, when the object ID is transmitted from the object ID generation object 1651, the telephone object 160 receives and stores it and requests the container generation object 1652 to generate a container object. The object ID of the object 160 is transmitted to the container generation object 1652 (FIG. 5: Step S3). In the bundle ID stack 120 </ b> A, the bundle ID of the container generation object 1652 is stacked on the bundle ID of the telephone object 160.

  FIG. 7 is a flowchart of the container generation object 1652 that receives such a request.

  When the container generation object 1652 receives a request from the telephone object 160 or the like (FIG. 7: YES in step S201), the container generation object 1652 receives the request source object ID transmitted from the request source object (FIGS. 2 and 7). : Step S203). In step S203, one or more object IDs of objects that are not the request source may be transmitted from the request source, and at that time, all of them are received.

  Next, the container generation object 1652 transmits the request source object ID received in step S203 to the object ID authentication object 1653 and requests authentication of the object ID (FIG. 2, FIG. 7: step S205). In the bundle ID stack 120A or the like, the bundle ID of the object ID authentication object 1653 is stacked on the bundle ID of the container generation object 1652 that is the request source.

  FIG. 8 is a flowchart of the object ID authentication object 1653 that receives such a request.

  When the object ID authentication object 1653 receives a request from the container generation object 1652 or the like (FIG. 8: YES in step S301), the object ID authentication object 1653 receives an object ID such as the telephone object 160 to be authenticated from the request source (FIG. 8: Step S303). Then, referring to the object ID storage unit 15 (FIG. 2: step S305), it is determined whether or not the object ID received in step S303 is stored in the object ID storage unit 15 (FIG. 8: step S305). If it is determined that the object ID is stored (YES), the bundle ID associated with the object ID in the object ID storage unit 15 is read from the object ID storage unit 15 and the bundle ID stack 120A is acquired (see FIG. 2: Step S307), it is determined whether or not the bundle ID equal to the read bundle ID is in the acquired bundle ID stack 120A or the like (FIG. 8: Step S307).

  If it is determined in step S307 that there is a bundle ID (YES), the object ID authentication object 1653 transmits a processing result indicating that the authentication is successful to the container generation object 1652 which is the request source (FIG. 8: step). S309), the process ends.

  For example, although an object (not shown) that communicates with another telephone terminal (not shown) connected to the home server 1 has an object ID, the object ID is an object ID. If it is not stored in the storage unit 15, it is determined as NO in step S305. In such a case, the object ID authentication object 1653 is the request source with a processing result indicating that the authentication has failed. The data is transmitted to the container generation object 1652 or the like (FIG. 8: Step S311), and the process is terminated.

  Therefore, for example, when the address book 21 belongs to a father who uses the telephone terminal 2, the address book 21 is disclosed to a child or the like through a malicious object and the telephone terminal, and the child makes a mischief call. Can be prevented.

  On the other hand, in step S307, the determination result is divided according to the following circumstances. That is, at step S307, the bundle ID of the telephone object 160 and the like is positioned third from the top of the bundle ID stack 120A and the like, so it is determined YES in step S307. When the object ID is leaked and the telephone object 160 is not making a request to another object, when the malicious object transmits the leaked object ID as the object ID of the object to the container generation object 1652 or the like Although it is determined as YES in step S305, since the bundle ID such as the telephone object 160 having the leaked object ID does not exist in the bundle ID stack 120A or the like, NO is determined in step S307. It is determined. In such a case, the object ID authentication object 1653 transmits a processing result indicating that the authentication has failed to the container generation object 1652 which is the request source (FIG. 8: step S311), and the processing ends.

  Therefore, similarly, the address book 21 is disclosed to a child or the like through a malicious object and a telephone terminal, and it is possible to prevent the child from making a mischief call.

  Returning to FIG. In the bundle ID stack 120A or the like, the bundle ID of the object ID authentication object 1653 at the top is deleted, and the bundle ID of the container generation object 1652 becomes the highest bundle ID.

  Next, when the container generation object 1652 receives the authentication result (FIG. 7: YES in step S207), the container generation object 1652 determines whether the authentication result indicates that the authentication has succeeded or indicates that the authentication has failed. (FIG. 7: Step S209) In the case of indicating that the authentication is successful, the container generation object 1652 generates a container object (FIG. 2, FIG. 7: Step S211).

  Next, the container generation object 1652 adds to the generated container object all the request source object IDs such as the telephone object 160 received in step S203, all the object IDs of the non-request source objects received in step S203, and the container generation. The object ID of the database system object 165 provided in the object 1652 (the object ID of the object to be requested) is stored (FIG. 7: step S213).

  Next, the container generation object 1652 transmits the reference information directly or indirectly indicating the container object as a processing result to the telephone object 160 that is the request source (FIG. 7: Step S215), and ends the processing. On the other hand, if it indicates that the authentication has failed (step S215), the processing result indicating that the processing could not be performed is transmitted to the telephone object 160 of the request source, and the processing ends.

  Returning to FIG. In the bundle ID stack 120A, the bundle ID of the container generation object 1652 at the top is deleted, and the bundle ID of the telephone object 160 becomes the highest bundle ID.

  Next, when the telephone object 160 receives reference information (hereinafter referred to as reference information 16501R) of the generated container object (hereinafter referred to as container object 16501) (FIG. 5: YES in step S5), the reference information 16501R. The content of the instruction based on the content of the request from the telephone terminal 2, that is, the content of the instruction that the database system object 165 obtains the address book 21 from the database system 4 and stores it in the container object 16501. A request is made to the container object 16501 to be stored in the container object 16501, and at this time, the object ID of the telephone object 160 is transmitted to the container object 16501 (FIGS. 2 and 5: scan). -Up S7).

  FIG. 9 is a flowchart of a container object that receives such a request.

  When the container object receives a request from a request source such as the telephone object 160 (FIG. 9: YES in step S401), the container object receives the object ID of the object transmitted from the request source object (FIG. 9: step). S403). In the bundle ID stack 120A or the like, the bundle ID of the container object is stacked on the top.

  Next, the container object determines whether or not the object ID received in step S403 matches any object ID in the container object (FIG. 9: step S405). If YES is determined, the object ID received in step S403 is transmitted to the object ID authentication object 1653, and at the same time, authentication of the object ID is requested (FIG. 2, FIG. 9: step S407). In the bundle ID stack 120A or the like, the bundle ID of the object ID authentication object 1653 is stacked on the bundle ID of the container object.

  Thereafter, the processing of FIG. 8 is performed.

  Returning to FIG. In the bundle ID stack 120A or the like, the bundle ID of the object ID authentication object 1653 at the top is deleted, and the bundle ID of the container object becomes the highest bundle ID. Hereinafter, in order to prevent redundancy, description of the state change of the bundle ID stack is omitted.

  Next, when the container object receives the authentication result (FIG. 9: YES in step S409), the container object determines whether the authentication result indicates that the authentication has succeeded or indicates that the authentication has failed (FIG. 9). 9: Step S411), if it indicates that the authentication has succeeded, the container object accepts a request from the telephone object 160 of the request source (FIG. 9: Step S413). Here, the container object stores the instruction content transmitted from the telephone object 160 in the container object.

  Next, the container object transmits a processing result indicating that the processing is completed to the telephone object 160 of the request source (FIG. 9: Step S415), and the processing ends. On the other hand, if NO is determined in step S405, or if the authentication is unsuccessful (step S411), a processing result indicating that the processing could not be performed is transmitted to the requesting telephone object 160 or the like. (FIG. 9: Step S417), the process ends.

  Returning to FIG. 5, when the telephone object 160 receives the processing result indicating that the processing is completed from the container object 16501 (FIG. 5: YES in step S <b> 9), the telephone object 160 stores the container object 16501 in the database system object 165. The reference information 16501R is transmitted, and the database system object 165 is requested to perform processing according to the instruction content in the container object 16501 (FIG. 5: Step S11). Note that the reference information or the like may be transmitted directly as described above, or the reference information may be stored in the home server 1 and the reference information indicating the location where the information is stored may be transmitted directly or indirectly. .

  In response to step S11, the database system object 165 detects the container object 16501 from the transmitted reference information 16501R, makes a request to the container object 16501 to acquire the instruction content in the container object 16501, and at this time, the database system The object ID of the object 165 is transmitted to the container object 16501 (FIGS. 2 and 5: Step S13).

  Thereafter, the processing of FIG. 9 is performed, and the database system object 165 acquires the instruction content in the container object 16501.

  Returning to FIG. 5, when the database system object 165 receives a processing result indicating that the processing is completed from the container object 16501 (FIG. 5: YES in step S15), the database system object 165 follows the instruction content acquired from the container object 16501. Then, the address book 21 is acquired from the database system 4 (FIG. 5: Step S17).

  Next, the database system object 165 requests the container object 16501 to store the address book 21 in the container object 16501, and at this time, transmits the object ID of the database system object 165 to the container object 16501 (FIG. 2, FIG. 2). FIG. 5: Step S19).

  Thereafter, the processing of FIG. 9 is performed, and the database system object 165 stores the address book 21 in the container object 16501.

  Returning to FIG. 5, when the database system object 165 receives the processing result indicating that the processing is completed from the container object 16501 (FIG. 5: YES in step S <b> 21), the database system object 165 displays the processing result indicating that the processing is completed as the telephone object. 160 (FIG. 5: step S23), and the process ends.

  The telephone object 160 makes a request to the container object 16501 to acquire the address book 21 in the container object 16501 at step S23, and transmits the object ID of the telephone object 160 to the container object 16501 (FIG. 2). FIG. 5: Step S25).

  Thereafter, the processing of FIG. 9 is performed, and the telephone object 160 acquires the address book 21 from the container object 16501.

  Returning to FIG. 5, when the telephone object 160 receives the processing result indicating that the processing is completed from the container object 16501 (FIG. 5: YES in Step S27), the telephone object 160 transmits the address book 21 to the telephone terminal 2 (Step S27). S29), the process ends.

  Thereby, for example, the telephone terminal 2 displays a plurality of telephone numbers included in the address book 21, and when one of them is selected, it is possible to make a call to the line of the telephone number.

  Next, there is a request from the schedule management unit 3A in the computer 3 to the schedule management object 161 called by the thread 121, whereby the database system object 165 acquires the schedule data 31 in the database system 4. Then, the sort object 163 sorts this, and the operation when the schedule management object 161 acquires it and transmits it to the schedule management unit 3A will be described.

  FIG. 10 is a diagram showing a flow of requests and the like at that time, and FIG. 11 is a diagram showing a part of the sequence at that time.

  Here, the schedule management object 161 and the sort object 163 are provided with their own object IDs by making a request similar to step S1 in FIG. 5, and the object ID storage unit 15 stores the object IDs. Assume that the bundle ID of the object having this object ID is associated, and the schedule management object 161 has already acquired the object ID of the sort object 163.

  During the operation of the thread 121 generated by executing the bundle 131, the schedule management unit 3A makes a request to the schedule management object 161, and the schedule management object 161 first sends a request to the container generation object 1652 according to the request contents. On the other hand, a request is made to generate a container object. At this time, the object ID of the schedule management object 161 and the object ID of the sort object 163 are transmitted to the container generation object 1652 (FIG. 11: step S33).

  Thereafter, the processing of FIG. 7 is performed, and a container object having object IDs of the schedule management object 161, the sort object 163, and the database system object 165 is generated.

  Returning to FIG. 11, when the schedule management object 161 receives reference information (hereinafter referred to as reference information 16511R) of the generated container object (hereinafter referred to as container object 16511) (FIG. 11: YES in step S35), The container object 16511 is detected based on the reference information 16511R, and the instruction content based on the request content from the schedule management unit 3A, here the schedule data 31 is acquired by the database system object 165 and stored in the container object 16511, and the sort object 163 Stores in the container object 16511 an instruction content for sorting a set including the user ID (referred to as user ID 500) included in the request content in the schedule data 31 in order of the scheduled time. Order, makes a request to a container object 16511 transmits the object ID of the schedule management object 161 at this time the container object 16511 (FIG. 10, FIG. 11: step S37).

  Thereafter, the processing of FIG. 9 is performed, and the instruction content is stored in the container object 16511.

  Returning to FIG. 11, when the schedule management object 161 receives the processing result indicating that the processing is completed from the container object 16511 (FIG. 11: YES in step S39), the reference information 16511R of the container object 16511 is stored in the sort object 163. The request is sent to the sort object 163 to perform processing with the instruction content in the container object 16511 (FIG. 10, FIG. 11: step S41).

  At step S41, the sort object 163 detects the container object 16511 from the transmitted reference information 16511R and makes a request to the container object 16511 to acquire the instruction content in the container object 16511. At this time, the sort object 163 Are transmitted to the container object 16511 (FIGS. 10 and 11: step S43).

  Thereafter, the processing of FIG. 9 is performed, and the sort object 163 acquires the instruction content in the container object 16511.

  Returning to FIG. 11, when the sort object 163 receives the processing result indicating that the processing is completed from the container object 16511 (FIG. 11: YES in step S45), the instruction content in the container object 16511 displays the schedule data 31. Since the database system object 165 acquires and stores it in the container object 16511, and the sort object 163 sorts the sets including the user ID 500 in the schedule data 31 in order of scheduled time, the database system object 165 is referred to the container object 16511. The information 16511R is transmitted, and the database system object 165 is requested to perform processing according to the instruction content in the container object 16511 (FIGS. 10 and 11). Step S47).

  In response to step S47, the database system object 165 detects the container object 16511 from the transmitted reference information 16511R, and makes a request to the container object 16511 to acquire the instruction content in the container object 16511. At this time, the database system The object ID of the object 165 is transmitted to the container object 16511 (FIG. 10, FIG. 11: Step S49).

  Thereafter, the processing of FIG. 9 is performed, and the database system object 165 acquires the instruction content in the container object 16511.

  Returning to FIG. 11, when the database system object 165 receives a processing result indicating that the processing has ended from the container object 16511 (FIG. 11: YES in step S51), the instruction content in the container object 16511 is the schedule data 31. Is acquired by the database system object 165, stored in the container object 16511, and the sort object 163 sorts the sets including the user ID 500 in the schedule data 31 in order of the scheduled time, so the schedule data 31 is acquired from the database system 4. (FIG. 11: Step S53).

  Next, the database system object 165 requests the container object 16511 to store the schedule data 31 in the container object 16511, and at this time, transmits the object ID of the database system object 165 to the container object 16511 (FIG. 10, FIG. 10). FIG. 11: Step S55).

  Thereafter, the processing of FIG. 9 is performed, and the database system object 165 stores the schedule data 31 in the container object 16511.

  Returning to FIG. 11, when the database system object 165 receives the processing result indicating that the processing is completed from the container object 16511 (FIG. 11: step S57), the processing result indicating that the processing is completed is sent to the sort object 163. Transmit (FIG. 11: Step S59), and the process ends.

  The sort object 163 makes a request to the container object 16511 to sort the set of the scheduled event and the scheduled time in the schedule data 31 in the container object 16511 in response to step S59. At this time, the sort object 163 sets the object ID of the sort object 163. The data is transmitted to the container object 16511 (FIG. 10, FIG. 11: Step S61).

  Thereafter, the processing of FIG. 9 is performed, and the sort object 163 sorts the sets including the user ID 500 in the schedule data 31 stored in the container object 16511 in the order of the scheduled time.

  Returning to FIG. 11, when the sort object 163 receives the processing result indicating that the processing is completed from the container object 16511 (FIG. 11: YES in step S <b> 63), the sorting object 163 displays the processing result indicating that the processing is completed as the schedule management object. 161 (FIG. 11: step S65), and the process ends.

  At step S65, the schedule management object 161 makes a request to the container object 16511 to acquire the sorted schedule data 31 in the container object 16511. At this time, the object ID of the telephone object 160 is transmitted to the container object 16511. (FIG. 10, FIG. 11: Step S67).

  Thereafter, the process of FIG. 9 is performed, and the schedule management object 161 acquires the sorted schedule data 31 from the container object 16511.

  Returning to FIG. 11, when the schedule management object 161 receives the processing result indicating that the processing is completed from the container object 16511 (FIG. 11: YES in step S <b> 69), the schedule management object 161 stores the schedule data 31 in the schedule management in the computer 3. The data is transmitted to the unit 3A (step S71), and the process ends.

  Thereby, for example, the schedule management unit 3A in the computer 3 can display the sorted scheduled events in the schedule data 31 together with the scheduled time.

  Next, direct communication between the schedule management object 161 and sort object 163 and the database system object 165 is prohibited, and direct communication between the schedule management object 161, sort object 163 and database system object 165 and the object 164 is permitted. The schedule management object 161 called by the thread 121 receives a request from the schedule management unit 3A in the computer 3, whereby the database system object 165 acquires the schedule data 31 in the database system 4, and this This is notified to the sort object 163 via the object 164, and the sort object 163 sorts the schedule data 31, It gets phone object 160, the operation for sending the schedule management unit 3A.

  FIG. 12 is a diagram showing a flow of requests and the like at that time, and FIG. 13 is a diagram showing a part of the sequence at that time.

  Here, the schedule management object 161, the sort object 163, and the object 164 have their own object IDs by making the same request as in step S1 of FIG. 5, and the object ID storage unit 15 stores the object IDs. Further, it is assumed that the bundle ID of the object having this object ID is associated and the schedule management object 161 has already acquired the object IDs of the sort object 163 and the object 164.

  During the operation of the thread 121, the schedule management unit 3A makes a request to the schedule management object 161, and according to this request content, the schedule management object 161 first requests the container generation object 1652 to generate a container object. At this time, the object ID of the schedule management object 161 and the object ID of the sort object 163 are transmitted to the container generation object 1652 (FIG. 13: step S133). Here, the schedule management object 161 does not transmit the object ID of the object 164 to the container generation object 1652 in order to prohibit information storage, information manipulation and information acquisition in the container object by the object 164.

  Thereafter, the processing of FIG. 7 is performed, and a container object having object IDs of the schedule management object 161, the sort object 163, and the database system object 165 is generated.

  Returning to FIG. 13, when the schedule management object 161 receives reference information (hereinafter referred to as reference information 16512R) of the generated container object (hereinafter referred to as container object 16512) (FIG. 13: YES in step S135), The container object 16512 is detected from the reference information 16512R, the instruction content based on the request content from the schedule management unit 3A, here, the schedule data 31 is acquired by the database system object 165 and stored in the container object 16512, and this is stored in the object 164. Is sent to the sort object 163, and the sort object 163 schedules a set including the user ID (referred to as user ID 500) included in the request content in the schedule data 31. Sequentially makes requests to the container object 16512 stores the instruction contents in a container object 16,512 that sort, transmits the object ID of the schedule management object 161 at this time the container object 16,512 (12, 13: step S137).

  Thereafter, the processing of FIG. 9 is performed, and the instruction content is stored in the container object 16512.

  Returning to FIG. 13, when the schedule management object 161 receives the processing result indicating that the processing is completed from the container object 16512 (FIG. 13: YES in step S139), the reference information 16512R of the container object 16512 is stored in the sort object 163. And requests the sort object 163 to perform processing with the instruction content in the container object 16512 (FIG. 12, FIG. 13: step S141).

  In response to step S141, the sort object 163 detects the container object 16512 from the transmitted reference information 16512R and makes a request to the container object 16512 to acquire the instruction content in the container object 16512. At this time, the sort object 163 Is transmitted to the container object 16512 (FIG. 12, FIG. 13: step S143).

  Thereafter, the processing of FIG. 9 is performed, and the sort object 163 acquires the instruction content in the container object 16512.

  Returning to FIG. 13, when the sort object 163 receives the processing result indicating that the processing is completed from the container object 16512 (FIG. 13: YES in step S145), the instruction content in the container object 16512 is the schedule data 31. Is acquired by the database system object 165, stored in the container object 16512, and this is notified to the sort object 163 via the object 164, and the sort object 163 sets the sets including the user ID 500 in the schedule data 31 in the order of the scheduled time. Since the instruction content is sorting, the reference information 16512R of the container object 16512 is transmitted to the object 164, and the reference information 16512R is transmitted to the database system object 165. Request to the object 164, and further request the object 164 to request the database system object 165 to perform processing according to the instruction contents in the container object 16512 indicated by the reference information 16512R (FIG. 12, FIG. 13: step). S147).

  The object 164 transmits the reference information 16512R transmitted in step S147 to the database system object 165, and requests the database system object 165 to perform processing according to the instruction content in the container object 16512 indicated by the reference information 16512R ( FIG. 12, FIG. 13: Step S149).

  Here, if the object 164 is a malicious object, for example, the following is possible. That is, the container object 16512 is detected from the transmitted reference information 16512R, and a request is made to the container object 16512 to acquire the instruction content in the container object 16512, as shown in step S151 in FIG. Can be transmitted to the container object 16512. However, since the object ID of the object 164 is not stored in the container object 16512, the object 164 cannot acquire the instruction content in the container object 16512, and the object 164 cannot perform processing from the container object 16512. A processing result indicating this is transmitted (FIG. 12: Step S153).

  When the object 164 detects the container object 16512 from the transmitted reference information 16512R and makes a request to the container object 16512 to acquire the instruction content in the container object 16512 in step S151 in FIG. Alternatively, an illegally acquired object ID can be transmitted as the object ID of the object 164 to the container object 16512. When the object ID of the object that first received this object ID is stored in the object ID storage unit 15, the object ID storage unit 15 is referred to (FIG. 12: step S303), and the determination in step S303 of FIG. If the object is not making a request to another object, the acquired bundle ID stack 121A (FIG. 12: Step S304) does not contain the object ID of the leaked object. The determination in step S307 in FIG. 8 is NO. Therefore, in the end, the object 164 cannot acquire the instruction content in the container object 16512, and a processing result indicating that the processing cannot be performed from the container object 16512 is transmitted to the object 164 (FIG. 12: Step S153). ).

  Now, when step S149 is performed without such a situation, the database system object 165 detects the container object 16512 from the transmitted reference information 16512R with this step S149 as a trigger, and the instruction in the container object 16512 A request is made to the container object 16512 to acquire the contents, and at this time, the object ID of the database system object 165 is transmitted to the container object 16512 (FIG. 12, FIG. 13: Step S159).

  Thereafter, the processing of FIG. 9 is performed, and the database system object 165 acquires the instruction content in the container object 16512.

  Returning to FIG. 13, when the database system object 165 receives a processing result indicating that the processing is completed from the container object 16512 (FIG. 13: YES in step S161), the instruction content in the container object 16512 is the schedule data. 31 is acquired by the database system object 165 and stored in the container object 16512. This is notified to the sort object 163 via the object 164, and the sort object 163 schedules a set including the user ID 500 in the schedule data 31. Since the contents are sorted in time order, the schedule data 31 is acquired from the database system 4 (FIG. 13: step S163).

  Next, the database system object 165 requests the container object 16512 to store the schedule data 31 in the container object 16512, and at this time, transmits the object ID of the database system object 165 to the container object 16512 (FIG. 12, FIG. 12). FIG. 13: Step S165).

  Thereafter, the processing of FIG. 9 is performed, and the database system object 165 stores the schedule data 31 in the container object 16512.

  Returning to FIG. 13, when the database system object 165 receives a processing result indicating that the processing is completed from the container object 16512 (FIG. 13: step S167), the processing result indicating that the processing is completed is displayed in the object 164. Transmit (FIG. 11: Step S169), and the process ends.

  In response to step S169, the object 164 transmits a processing result indicating that the processing has ended to the sort object 163 (FIG. 13: step S171), and ends the processing.

  The sort object 163 makes a request to the container object 16512 to sort the set of the scheduled event and the scheduled time in the schedule data 31 in the container object 16512 in response to step S171. At this time, the object ID of the sort object 163 is set. The data is transmitted to the container object 16512 (FIG. 12, FIG. 13: Step S181).

  Thereafter, the processing of FIG. 9 is performed, and the sort object 163 sorts the sets including the user ID 500 in the schedule data 31 in the container object 16512 in the order of the scheduled time.

  Returning to FIG. 13, when the sort object 163 receives a processing result indicating that the processing is completed from the container object 16512 (FIG. 13: YES in step S <b> 183), the sort object 163 schedules the processing result indicating that the processing is completed. It transmits to the object 161 (FIG. 13: step S185), and a process is complete | finished.

  In step S185, the schedule management object 161 makes a request to the container object 16512 to acquire the sorted schedule data 31 in the container object 16512. At this time, the object ID of the schedule management object 161 is sent to the container object 16512. Transmit (FIG. 12, FIG. 13: Step S187).

  Thereafter, the process of FIG. 9 is performed, and the schedule management object 161 acquires the schedule data 31 sorted from the container object 16512.

  Returning to FIG. 13, when the schedule management object 161 receives the processing result indicating that the processing is completed from the container object 16512 (FIG. 13: YES in step S189), the schedule management object 161 stores the schedule data 31 in the schedule management unit in the computer 3. 3A (step S191), and the process ends.

  As described above, according to the present embodiment, the bundle ID is stored in the bundle ID storage unit 14 in advance, and when there is a request for generating the object ID, the bundle executed when the object is generated The bundle ID is acquired from the bundle ID stack, and it is determined whether or not the acquired bundle ID is stored in the bundle ID storage unit 14. When the bundle ID is stored in the bundle ID storage unit 14, only the object ID of the object generated by executing the trusted bundle is generated. Accordingly, the object ID generated by executing the trusted bundle is generated. Identification becomes possible.

  In addition, the object ID generated by the object ID generation object is stored, the object ID storage unit 15 associated with the bundle ID of the bundle executed when the object of the object ID is generated, and the object ID authentication If there is a request, it is determined whether or not the object ID is stored in the object ID storage unit 15. If the object ID is stored, the bundle ID associated with the object ID is stored in the bundle ID storage unit 14. If the object ID authentication object that transmits the authentication result indicating that the authentication has been successful is provided, the authentication fails with the fake object ID. Use of the object ID can be prevented. In addition, since the encryption and decryption of information are not required, it is possible to prevent a decrease in computer performance.

  In addition, when there is a request to generate a container object, a request for object ID authentication is made to the object ID authentication object, and when a processing result indicating that the authentication is successful is transmitted, a container generation for generating a container object is generated. By providing an object, authentication fails with a fake object ID, and therefore it is possible to prevent a container object from being generated using a fake object ID.

  In addition, the container generation object stores the object ID to be transmitted in the container object, and the container object has its object ID when any of the information storage, information operation, and information acquisition requests is received from the object. Is stored in the container object, and if it is stored, a request for authentication of the object ID is made. If a processing result indicating that the authentication is successful is transmitted, the request is satisfied. Thus, authentication fails with a fake object ID, and therefore it is possible to prevent the fake object ID from being used to perform information storage, information manipulation, and information acquisition in the container object.

  In addition, as described with reference to FIG. 13, a request made to an object with a container object presence notification (by reference information) makes the object make a request to another object with a container object presence notification. In each object (sort object 163, object 164, and database system object 165) that receives any request in the instruction content that is performed twice in a chain, the object (sort object 163) that receives the request first An object (schedule management object 161) that makes a request and notifies the object (sort object 163) of the instruction content requests the generation of a container object (step S133) and each object ( By transmitting a part of the object IDs (object IDs of the sort objects 163) among the object IDs of the data object 163, the object 164, and the database system object 165) to the container generation object, the container generation object itself The object ID (object ID of the object 164) that is not stored or transmitted is not stored in the container object, and even if the object with the object ID makes a request to the container object, the authentication fails with the object ID. Therefore, all objects (sort object 163, object 164, and database system object 165) cooperate to process the instruction content. It can be performed using the extract, moreover, for some objects (164) therein, can be inhibited by the object information storage in the container object, the information manipulation and information acquisition. Note that this effect can be obtained in the same manner even when the request that is made twice in a chained manner is made three times or more and the object operates in a manner corresponding to the request.

  A computer program that causes a computer to function as the home server 1 is stored in a computer-readable recording medium such as a semiconductor memory, a magnetic disk, an optical disk, a magneto-optical disk, or a magnetic tape, or transmitted via a communication network such as the Internet. And can be widely distributed.

  Moreover, although the object control apparatus as a home server has been described in the above embodiment, the object control apparatus may be embodied as another aspect, for example, a server or personal computer provided on the Internet.

1 is a configuration diagram of a home network system to which an object control device and a control method thereof according to an embodiment are applied. Configuration of the object management unit 165A and a request when the telephone object 160 acquires the address book 21 in the database system 4 via the database system object 165 and transmits it to the telephone terminal 2 by a request from the telephone terminal 2 It is a figure which shows the flow of. It is the figure which illustrated bundle ID storage part 14. 3 is a diagram illustrating an object ID storage unit 15. FIG. It is the sequence diagram of the operation | movement which showed the flow of a request etc. in FIG. 10 is a flowchart of an object ID generation object 1651. 10 is a flowchart of a container generation object 1652. 10 is a flowchart of an object ID authentication object 1653. It is a flowchart of a container object. It is a figure which shows the flow of a request | requirement etc. when the database system object 165 acquires the schedule data 31, the sort object 163 sorts this, the schedule management object 161 acquires this, and transmits to the schedule management part 3A. It is the sequence diagram of the operation | movement which showed the flow of a request etc. in FIG. The database system object 165 obtains the schedule data 31, and the sort object 163 obtains and sorts the schedule data 31 via the object 164, and the telephone object 160 obtains and sorts this, and the flow of requests and the like when it is transmitted to the schedule management unit 3A FIG. It is a figure which shows a part of operation | movement sequence which showed the flow of a request | requirement etc. in FIG.

Explanation of symbols

DESCRIPTION OF SYMBOLS 1 ... Home server 2 ... Telephone terminal 3 ... Computer 3A ... Schedule management part 4 ... Database system 11 ... Virtual machine 12 ... Platform 13 ... Bundle memory | storage part 14 ... Bundle ID memory | storage part 15 ... Object ID memory | storage part 21 ... Address book 31 ... Schedule data 120, 121 ... Thread 120A, 121A ... Bundle ID stack 160 ... Telephone object 161 ... Schedule management object 163 ... Sort object 165 ... Database system object 165A ... Object management unit 1651 ... Object ID generation object 1652 ... Container generation object 1653 ... Object ID authentication object 16501, 16511, 16512 ... container object 16501R, 1 511R, 16512R ... reference information

Claims (12)

When a class included in a bundle that is a program that can be executed in a computer is executed, a thread and an object used for the thread are generated, and another object receives a processing request from the object. In an object control device, which is a computer having a bundle ID stack in which bundle IDs of bundles executed when other objects are generated after a bundle ID indicating the executed bundle is stored are stored.
A bundle ID storage unit in which a bundle ID of a bundle that can be executed in the computer and is selected is stored;
After the object in the computer is generated, if there is a request for generating the object ID of the object from the object, the bundle ID of the bundle executed when the object is generated is acquired from the bundle ID stack And determining whether or not the acquired bundle ID is stored in the bundle ID storage unit and, if stored, an object ID generating unit that generates an object ID of the object. Object control unit. The object ID object ID generated by the generating means is stored, in the object ID, the object ID storage unit bundle ID of the executed bundles is associated when the object of the object ID is generated
Object control device according to claim 1, characterized in that it comprises a. When an object ID authentication request is received from an object in the computer, it is determined whether or not the object ID is stored in the object ID storage unit. If the object ID is stored, the object ID is associated with the object ID. Object ID authenticating means for determining whether or not the bundle ID is stored in the bundle ID storage unit and transmitting the authentication result indicating that the authentication has been successful to the object if stored.
The object control apparatus according to claim 2, further comprising: A container object that is an object generated in the computer, a processing request for the other object to the container object, storage of information as a processing result by the other object , and acquisition of the information from the container object If there is the object in the computer to produce the container object to be performed required, the authenticate request object ID of the object in the object ID authentication means, the processing result indicating that the person authentication is successful The object control apparatus according to claim 3, further comprising: a container generation unit configured to generate the container object when the message is transmitted. It said container generation means, the object ID transmitted from the object making the request in the generation of container object is intended to be stored in the container object,
The container object is the object of the object when any of the information storage in the container object, the information operation in the container object, and the information acquisition from the container object is requested from the object in the computer. ID is determined whether stored in the container object, if it is stored, to authenticate the request of the object ID of the object with the object ID authentication means indicate that the person authentication is successful treatment 5. The object control apparatus according to claim 4 , wherein when the result is transmitted, the request is satisfied. It is chained that the object makes a request to another object with the presence notification of the container object by a request made to the object in the computer with the notification of the existence of the container object generated by the container generation means. An object that first makes a request to the object that receives the request among the objects that receive any request in the instruction content that is to be performed twice or more is generated by the container. and characterized by storing a part of the object ID in the object ID of each object receive either request in the instruction content performs a request for production of the container object to the means on the container Nao object The object according to claim 5 Control device. When a class included in a bundle that is a program that can be executed in a computer is executed, a thread and an object used for the thread are generated, and another object receives a processing request from the object. Control of an object control device which is a computer having a bundle ID stack in which bundle IDs of bundles executed when another object is generated after a bundle ID indicating the executed bundle is stored In the method
The object control device includes a bundle ID storage unit in which a bundle ID of a bundle that can be executed in the computer and is selected is stored,
The object ID generation means in the computer is
After the object in the computer is generated, if there is a request for generating the object ID of the object from the object, the bundle ID of the bundle executed when the object is generated is acquired from the bundle ID stack Then, it is determined whether or not the acquired bundle ID is stored in the bundle ID storage unit. If the bundle ID is stored, the object ID of the object is generated. The object ID generated by the object ID generating means is stored, and the object ID storage unit in which the bundle ID of the bundle executed when the object of the object ID is generated is associated with the object ID is controlled by the object control. control method for object control system according to claim 7, wherein the device is Ru with. When the object ID authentication means in the computer has requested authentication of the object ID from the object in the computer, the object ID authentication means determines whether or not the object ID is stored in the object ID storage unit, and is stored. If it is, it is determined whether or not the bundle ID associated with the object ID is stored in the bundle ID storage unit. If the bundle ID is stored, an authentication result indicating that the authentication is successful is stored in the object. Send
The method of controlling an object control apparatus according to claim 8. Container generating means in said computer, storage and the container of the processing result serving information by the other processing requests for objects and the other objects of a container object is an object that is created in the computer to the container object If the acquisition of the information from the object is requested from an object in the computer to produce the container object to be performed, to authenticate requests for object ID of the object with the object ID authentication means, those wherein The method for controlling an object control apparatus according to claim 9 , wherein when a processing result indicating that the authentication is successful is transmitted, the container object is generated. It said container generation means, the object ID transmitted from the object making the request in the generation of container object is intended to be stored in the container object,
The container object is the object of the object when any of the information storage in the container object, the information operation in the container object, and the information acquisition from the container object is requested from the object in the computer. ID is determined whether stored in the container object, if it is stored, to authenticate the request of the object ID of the object with the object ID authentication means indicate that the person authentication is successful treatment 11. The method of controlling an object control apparatus according to claim 10 , wherein when the result is transmitted, the request is satisfied. It is chained that the object makes a request to another object with the presence notification of the container object by a request made to the object in the computer with the notification of the existence of the container object generated by the container generation means. An object that first makes a request to the object that receives the request among the objects that receive any request in the instruction content that is to be performed twice or more is generated by the container. and characterized by storing a part of the object ID in the object ID of each object receive either request in the instruction content performs a request for production of the container object to the means on the container Nao object The object according to claim 11. The control method of the project control device.

Images