Abstract:
PROBLEM TO BE SOLVED: To provide a method and a system for an event-based configuration interface between a service support mobile connectivity and device drivers exposing WWAN data services. SOLUTION: Object identifiers (OIDs) are passed between the service and the device drivers. Asynchronous communication is enabled, The method and the system for using OIDs in order to negotiate configuration, including PINs, SIMs, and signal strength, of WWAN devices such as GSM and CDMA-based devices are provided. COPYRIGHT: (C)2005,JPO&NCIPI
Abstract:
PROBLEM TO BE SOLVED: To provide a system and a method for selecting a network and an interface which span a plurality of media. SOLUTION: This disclosed system facilitates automated network interface configuration decision-making, that spans a set of networks supporting communications via differing media. A set of media specific modules associated with differing communications media acquire network interface status/capabilities information. A rules engine thereafter applies a designated network selection rules to the acquired network interface status/capabilities information, and any other appropriate parameters attributable to either an interface or network, and selects one or more networks and interfaces, in order to establish/maintain a connection. COPYRIGHT: (C)2005,JPO&NCIPI
Abstract:
Directory services schema for telephone call management. The schema facilitates the development of call routing rules as one or more instances of one or more classes. Once created, the rules can be propagated to all other director services servers, and any subsequent updates and system changes are readily propagated to maintain optimum call system management. The rules can be stored in a routing table allowing administrators to define phone routes for various scenarios. System hardware/software changes can be managed using distinguished names and automatically propagated (or replicated) to the other directory services servers on an enterprise network. The architecture includes a schema component for generating a directory services schema, and a call routing component that routes telephone calls according to call routing rules defined by the directory services schema. The rules can be processed in combination with policies of usage attributes and phone number patterns/ranges to manage call routing.
Abstract:
Directory services schema for telephone call management. The schema facilitates the development of call routing rules as one or more instances of one or more classes. Once created, the rules can be propagated to all other director services servers, and any subsequent updates and system changes are readily propagated to maintain optimum call system management. The rules can be stored in a routing table allowing administrators to define phone routes for various scenarios. System hardware/software changes can be managed using distinguished names and automatically propagated (or replicated) to the other directory services servers on an enterprise network. The architecture includes a schema component for generating a directory services schema, and a call routing component that routes telephone calls according to call routing rules defined by the directory services schema. The rules can be processed in combination with policies of usage attributes and phone number patterns/ranges to manage call routing.