| System and method for accumulating a historical component context -> Monitor Keywords |
|
|
 
System and method for accumulating a historical component contextRelated Patent Categories: Electrical Computers And Digital Processing Systems: Multicomputer Data Transferring, Computer Network Managing, Computer Network MonitoringSystem and method for accumulating a historical component context description/claimsThe Patent Description & Claims data below is from USPTO Patent Application 20070180108, System and method for accumulating a historical component context. Brief Patent Description - Full Patent Description - Patent Application Claims
CROSS-REFERENCE TO RELATED APPLICATIONS [0001] This patent application is a divisional of U.S. patent application, Ser. No. 10/317,580, filed Dec. 12, 2002, pending, which is related to U.S. patent application, Ser. No. 10/317,342, filed Dec. 12, 2002, pending, and U.S. Pat. No. 6,810,360, issued Oct. 26, 2004, the disclosures of which are incorporated by reference, and the priority filing dates of which are claimed. FIELD [0002] This invention relates generally to systems and methods that use and share metadata. BACKGROUND [0003] In data communication environments, such as a distributed network, many different vendors provide a number of products for specific services. Heretofore, a predetermined set of domain-specific protocols has been required to be specified to enable arbitrary components in the environment to communicate with each other, assuming the components were transmitting or receiving data, hereinafter referred to as "transferring data." For example, a device manufactured by one vendor would have difficulty communicating with a device manufactured by another vendor without using the predetermined set of protocols mentioned above. The problem of different vendors requiring different predetermined protocols has been partially dealt with by adopting existing protocol standards. However, there are different standards organizations and thus different protocol standards. [0004] When arbitrary components such as computer applications or programs, data, memory, file directories, individual files, printer devices, cellular telephones, facsimile machines, copier machines, scanner devices, desk-top computers, lap-top computers, personal digital assistant ("PDA") systems, or any other device, for example, attempt to communicate without having a priori knowledge of each other, particular domain-specific protocols, such as the file system domain (e.g., NFS and CIFS) or the printer domain (e.g., IPP and LPR), must be known a priori by both parties to successfully communicate. An arbitrary component, such as a PDA attempting to communicate with a file system, or a printer device attempting to do the same, must be explicitly programmed to understand one or more of the standardized protocols mentioned above. An example includes a computer device or application having to be programmed to understand a printer device by installing a domain-specific printer driver. If the device or application is programmed to understand how to communicate and use a printer device, generically, the driver will only enable the device or application to access a particular type of printer device and not the universe of all printer devices. Thus, when new and unknown components enter the equation, the application must be reprogrammed to understand the new standardized protocols used to communicate with the new components. Referring to the above computer and printer device example, if a new type of printer were introduced, the computer device would have to be re-programmed to be able to transfer data with the new printer device by installing a printer driver specific to the new printer device. Thus, each application must be explicitly written to use a particular set of standardized protocols prior to communicating with the components associated with the protocols. [0005] In a system such as Jini.TM., developed by Sun Microsystems of Palo Alto, Calif. and described in "A collection of Jini.TM. Technology Helper Utilities and Services Specifications," Palo Alto, Calif., Sun Microsystems, Inc., pp. 1-214, 2000; and "Jini.TM. Technology Core Platform Specification," Palo Alto, Calif., Sun Microsystems, Inc., pp. 1-126, 2000, which uses domain-specific interfaces, in order for a component such as a PDA system to communicate with another component such as a printer, the PDA system must contain a priori knowledge of the semantics of the printer's programmatic interfaces. In other words, a component that knows how to print still might not know how to transfer data between a file system, a scanner device or a network translation service until it is explicitly programmed to know how to communicate with the interface for the particular components. [0006] Currently, ubiquitous computing environments do not allow for the network effect. That is, as additional components are added to the environment, they do not have the capability to do more than add the capability of that new component to the environment. It would be advantageous to provide some mechanism where the addition of components in an environment enhances the operation of the components in the environment. [0007] Additionally, some systems maintain contextual information in an ad hoc manner with respect to the components within the system. Such contextual information is often represented in various formats depending on the type of component it represents, such as whether the component is a user, a document or application. This often makes it difficult or impossible for arbitrary components within a system to provide each other with current contextual information, particularly if the arbitrary components do not have a priori knowledge of each other. [0008] One problem with contextual systems is that of establishing credibility (for example, verifying that a property value has not been inappropriately changed). Another problem is that it is very difficult to understand system behavior in a ubiquitous computing environment because the environment is so fluid. It would be advantageous to be able to verify how a property value changed and why the system behaved in a particular way. [0009] One problem using discovery mechanisms in ubiquitous computing environments is that these mechanisms often return very long lists of the discovered components without providing information to assist a user in understanding and selecting the useful components for the current situation. It would be advantageous to preferentially provide the user with information that is relevant to the current situation. SUMMARY [0010] Disclosed herein are embodiments for a method and system of accumulating a historical context of interactions between components in an environment where each of the components has a component context that can be revealed. The components include a requester component and a service component. The requester component requests an operation to be performed by the service component. The requester component passes its context to the service component with the operational request. The requester component context is recorded as service component contextual metadata and becomes part of the historical context. [0011] Other embodiments are disclosed for methods, apparatus and program products used to accumulate a historical context of changes in a component context that can be revealed. The apparatus and program products detect an operation that will change a portion of the component context and accretes that portion with the historical context. Then the apparatus and program products change the portion responsive to the operation. [0012] Yet other embodiments are disclosed for methods, apparatus and program products where a component receives a request and applies a contextual access policy to the request. After applying the contextual access policy to the request, the component checks that the request satisfies one of a set of contextual access permissions and, if so, satisfies the request. [0013] A further embodiment provides a system and method accumulating a historical component context. A request that includes a component context and an operation from a requester component is received. A contextual access policy that includes contextual access permissions to the request is applied. A contextual validation is checked that the request satisfies at least one of the contextual access permissions. The operation is performed upon the successful contextual validation of the request. The request is stored as historical component context. [0014] Other objects, features and advantages will be apparent from the accompanying drawings and from the following detailed description. BRIEF DESCRIPTION OF THE DRAWINGS [0015] FIG. 1 is a perspective view of a system for providing context information in accordance with embodiments; [0016] FIG. 2 is a block diagram of an exemplary arbitrary component utilized in the system for providing context information; [0017] FIG. 3 is a partial perspective view of a system for providing context information in accordance with embodiments; [0018] FIG. 4 is a flow chart of a process for providing context information; [0019] FIG. 5 is a partial perspective view of a system for providing context information in accordance with embodiments; Continue reading about System and method for accumulating a historical component context... Full patent description for System and method for accumulating a historical component context Brief Patent Description - Full Patent Description - Patent Application Claims Click on the above for other options relating to this System and method for accumulating a historical component context patent application. ###  How KEYWORD MONITOR works... a FREE service from FreshPatents1. Sign up (takes 30 seconds). 2. Fill in the keywords to be monitored. 3. Each week you receive an email with patent applications related to your keywords. Start now! - Receive info on patent apps like System and method for accumulating a historical component context or other areas of interest. ### Previous Patent Application: Security incident manager Next Patent Application: System and method for storing data-network activity information Industry Class: Electrical computers and digital processing systems: multicomputer data transferring or plural processor synchronization ### FreshPatents.com Support Thank you for viewing the System and method for accumulating a historical component context patent info. IP-related news and info Results in 0.15175 seconds Other interesting Feshpatents.com categories: Accenture , Agouron Pharmaceuticals , Amgen , AT&T , Bausch & Lomb , Callaway Golf 174 |
 * Protect your Inventions * US Patent Office filing 
PATENT INFO |
|
