Abstract: A quality of service (QOS) framework for mediating needs of software applications in the context of an application framework with capabilities of a network host platform in response to a service request from the software application. The QOS framework includes a QOS knowledge base and rules module including a specialized set of system wide rules for dynamically changing QOS behavior in response to the service request. The QOS framework also includes QOS framework service modules for negotiating between the software application and the network host platform based on the specialized set of system wide rules included in the QOS knowledge base and rules module. In addition, the QOS framework includes a plurality of QOS application platform interfaces (APIs) for interconnecting the QOS framework service modules with the QOS knowledge base and rules module, and a plurality of APIs for connecting the application with the QOS framework service modules and with the network host platform.

Abstract: A policy based software component system (24) for modifying software component behavior includes an interceptor (34) for intercepting an interface event being transmitted from a software application (14) comprising software components (20, 22). A rules database (32, 40) stores software component modifying rules, and an adaptor (35) modifies the interface event based on the software component modifying rules stored in the rules database (32, 40). A policy engine (36) attempts to match the interface event with the software component modifying rules stored in the rules database (32, 40), and subsequently coordinates the modification of the interface event by the adaptor (35) when the policy engine (36) matches the interface event with at least one of the software component modifying rules stored in the rules database (32, 40).

Abstract: A component based Application Middleware Framework (20) for modifying Application Middleware Framework (AMF) component services includes an interceptor (70) for intercepting an interface event being transmitted from a software management application (14a-14e) to a software component (40, 42). A rules database (48, 78) stores AMF component service modifying rules, and an adaptor (72) modifies the interface event based on the AMF component service modifying rules stored in the rules database (48, 70). A policy engine (74) attempts to match the interface event with the AMF component service modifying rules stored in the rules database (48, 70), and subsequently coordinates the modification of the AMF component service by the adaptor (72) when the policy engine (74) matches the interface event with at least one of the AMF component service modifying rules stored in the rules database (48, 70).

Abstract: A mobile device (10) includes a microprocessor (100), a device profile (101) stored in a local memory (102), a device application (103) and a virtual operating system (104). A sharable resources computer network (12) includes a plurality of servers or computer hosts (125), a virtual service provider (121) and sharable resources (122). The virtual service provider includes a broker (123) and a mediator (124). In operation, the mobile device application (103) requests device augmentation. The request is forwarded from the virtual operating system (104) to the broker (123). The broker (123) determines an appropriate sharable resource by comparing the device profile (101) with a directory of sharable resources stored in a knowledge base (126). The mediator (124) coordinates the specific access to the sharable resource with the device application (103). The device application (103) can specify sharable resources by providing an application program interface.

Abstract: An open service trading system (10) and method therein enables the reselling of services among brokers (18), resellers (16) and service providers (14) to service subscribers (12). The service trading system (10) comprises domain specific knowledge bases (22a-40a) constrained by respective ontology domains (22b-40b), where the ontology domains (22b-40b) together define a service trading ontology structure. In addition, rational agents (42-70) are each committed to one or more of the domain specific knowledge bases (22a-40a) to enable interaction with others of the rational agents to achieve associated participant trading goals as defined within the service trading ontology structure.

Abstract: A quality of service (QOS) framework for mediating needs of software applications in the context of an application framework with capabilities of a network host platform in response to a service request from the software application. The QOS framework includes a QOS knowledge base and rules module including a specialized set of system wide rules for dynamically changing QOS behavior in response to the service request. The QOS framework also includes QOS framework service modules for negotiating between the software application and the network host platform based on the specialized set of system wide rules included in the QOS knowledge base and rules module. In addition, the QOS framework includes a plurality of QOS application platform interfaces (APIs) for interconnecting the QOS framework service modules with the QOS knowledge base and rules module, and a plurality of APIs for connecting the application with the QOS framework service modules and with the network host platform.

Abstract: A policy based software component system (24) for modifying software component behavior includes an interceptor (34) for intercepting an interface event being transmitted from a software application (14) comprising software components (20, 22). A rules database (32, 40) stores software component modifying rules, and an adaptor (35) modifies the interface event based on the software component modifying rules stored in the rules database (32, 40). A policy engine (36) attempts to match the interface event with the software component modifying rules stored in the rules database (32, 40), and subsequently coordinates the modification of the interface event by the adaptor (35) when the policy engine (36) matches the interface event with at least one of the software component modifying rules stored in the rules database (32, 40).