multiple devices within a data communication network can be configured according to a single configuration profile. configuration profile data is stored in a configuration file. connections are made to individual devices, and the data in the configuration file is transformed into device-specific commands.
|
29. A machine-executable method of configuring multiple devices in a data communication network, comprising:
providing a configured device having configuration parameters set in conformity with a desired configuration profile;
extracting configuration data from the configured device, the configuration data including data specifying operating system software;
storing the extracted configuration data in a configuration file in extensible markup Language (XML) format;
identifying from the multiple devices a group of devices to be configured;
retrieving, for each device in the group, identifying data including data regarding software installed upon the device;
mapping, for each device in the group, the retrieved identifying data to a corresponding configuration profile deployment routine set;
generating device-specific commands for each device in the group using the configuration file and the configuration profile deployment routine sets mapped to the identifying data for the devices in the group, the device-specific commands for at least one device including commands to install the specified operating system software on the at least one device;
transmitting device-specific commands to each device in the group;
receiving acknowledgements of successful execution of the commands from the devices in the group; and
transmitting additional commands to devices in the group upon receipt of the acknowledgements.
1. A machine-executable method of configuring multiple devices in a data communication network, comprising:
(a) receiving a selection of a group of devices to be configured in accordance with a previously-stored configuration profile, the devices of the group being situated in different locations within the data communications network, the configuration profile having previously-stored configuration data that specifies, as to each device of the group, values for multiple configuration parameters corresponding to desired operation of that device;
(b) automatically opening a network connection with each of the devices of the group;
(c) automatically retrieving identifying data from each of the devices of the group;
(d) automatically mapping, for each device of the group and subsequent to step (a), the retrieved identifying data to a corresponding configuration profile deployment routine set;
(e) automatically generating device-specific commands for each device of the group, wherein the device-specific commands for each device are generated subsequent to performance of step (d) for that device and are generated using the previously-stored configuration data and the configuration profile deployment routine set mapped to the identifying data for that device;
(f) automatically transmitting the device-specific commands to each device of the group;
(g) prior to step (a), providing a configured device having configuration parameters set in conformity with a desired configuration; and
(h) subsequent to step (g), extracting configuration data from the configured device, wherein the extracted configuration data becomes the previously-stored configuration data of step (a), and wherein the previously-stored configuration data is stored in extensible markup Language (XML) format.
11. A machine-readable medium having machine-executable instructions for performing steps comprising:
(a) receiving a selection of a group of devices in a data communication network to be configured in accordance with a previously-stored configuration profile, the devices of the group being situated in different locations within the data communications network, the configuration profile having previously-stored configuration data that specifies, as to each device of the group, values for multiple configuration parameters corresponding to desired operation of that device;
(b) automatically opening a network connection with each of the devices of the group;
(c) automatically retrieving identifying data from each of the devices of the group;
(d) automatically mapping, for each device of the group and subsequent to step (a), the retrieved identifying data to a corresponding configuration profile deployment routine set;
(e) automatically generating device-specific commands for each device of the group, wherein the device-specific commands for each device are generated subsequent to performance of step (d) for that device and are generated using the previously-stored configuration data and the configuration profile deployment routine set mapped to the identifying data for that device;
(f) automatically transmitting the device-specific commands to each device of the group;
(g) prior to step (a), accessing a configured device having configuration parameters set in conformity with a desired configuration; and
(h) subsequent to step (g), extracting configuration data from the configured device, wherein the extracted configuration data becomes the previously-stored configuration data of step (a), and wherein the previously-stored configuration data is stored in extensible markup Language (XML) format.
20. A network management computer, comprising:
at least one network connection permitting communication with multiple network control devices; and
a processor programmed to configure multiple network control devices by
(a) receiving a selection of a group of devices to be configured in accordance with a previously-stored configuration profile, the devices of the group being situated in different locations within the network, the configuration profile having previously-stored configuration data that specifies, as to each device of the group, values for multiple configuration parameters corresponding to desired operation of that device,
(b) automatically opening a network connection with each of the devices of the group,
(c) automatically retrieving identifying data from each of the devices of the group,
(d) automatically mapping, for each device of the group and subsequent to step (a), the retrieved identifying data to a corresponding configuration profile deployment routine set,
(e) automatically generating device-specific commands for each device of the group, wherein the device-specific commands for each device are generated subsequent to performance of step (d) for that device and are generated using the previously-stored configuration data and the configuration profile deployment routine set mapped to the identifying data for that device,
(f) automatically transmitting the device-specific commands to each device of the group,
(g) prior to step (a), establishing communication with a configured device having configuration parameters set in conformity with a desired configuration, and
(h) subsequent to performing step (g), extracting configuration data from the configured device, wherein the extracted configuration data becomes the previously-stored configuration data of step (a), and wherein the previously-stored configuration data is stored in extensible markup Language (XML) format.
2. The machine-executable method of
3. The machine-executable method of
4. The machine-executable method of
5. The machine-executable method of
(f1) transmitting a first command to the device;
(f2) receiving an acknowledgement of successful execution of the first command by the device; and
(f3) transmitting a second command to the device upon receiving the acknowledgement.
6. The machine-executable method of
step (b) further comprises establishing a secure network connection to each device of the group,
the previously-stored configuration profile includes previously-stored configuration data specifying multiple configuration parameters for network security devices,
step (c) comprises retrieving data from each device of the group over the secure network connections, and
step (f) comprises transmitting the device-specific commands over the secure network connections.
7. The machine-executable method of
the previously-stored configuration profile specifies operating system software to be used by each device of the group,
step (e) comprises generating commands to install the specified operating system software on at least one device of the group, and
step (f) comprises installing the specified operating system software on the at least one device.
8. The machine-executable method of
the previously-stored configuration profile specifies application software to be used by each device of the group,
step (e) comprises generating commands to install the specified application software on at least one device of the group, and
step (f) comprises installing the specified application software on the at least one device.
9. The machine-executable method of
10. The machine-executable method of
(i) selecting individual configuration parameters from the previously-stored configuration profile; and
(j) modifying the selected individual configuration parameters.
12. The machine-readable medium of
13. The machine-readable medium of
14. The machine-readable medium of
(f1) transmitting a first command to the device;
(f2) receiving an acknowledgement of successful execution of the first command by the device; and
(f3) transmitting a second command to the device upon receiving the acknowledgement.
15. The machine-readable medium of
step (b) further comprises establishing a secure network connection to each device of the group,
the previously-stored configuration profile includes previously-stored configuration data specifying multiple configuration parameters for network security devices,
step (c) comprises retrieving data from each device of the group over the secure network connections, and
step (f) comprises transmitting the device-specific commands over the secure network connections.
16. The machine-readable medium of
the previously-stored configuration profile specifies operating system software to be used by each device of the group,
step (e) comprises generating commands to install the specified operating system software on at least one device of the group, and
step (f) comprises installing the specified operating system software on the at least one device.
17. The machine-readable medium of
the previously-stored configuration profile specifies application software to be used by each device of the group,
step (e) comprises generating commands to install the specified application software on at least one device of the group, and
step (f) comprises installing the specified application software on the at least one device.
18. The machine-readable medium of
19. The machine-readable medium of
(i) receiving selections of individual configuration parameters from the previously-stored configuration profile; and
(j) receiving instructions to modify the selected individual configuration parameters.
21. The network management computer of
perform step (c) by retrieving data regarding software installed on each device of the group, and
perform step (d) by mapping to one of multiple configuration deployment routine sets, each of the multiple configuration deployment routine sets being specific to a type of installed software.
22. The network management computer of
23. The network management computer of
(f1) transmitting a first command to the device,
(f2) receiving an acknowledgement of successful execution of the first command by the device, and
(f3) transmitting a second command to the device upon receipt of the acknowledgement.
24. The network management computer of
the previously-stored configuration profile includes previously-stored configuration data specifying multiple configuration parameters for network security devices,
the processor is programmed to perform step (c) by retrieving data from each device of the group over the secure network connections, and
the processor is programmed to perform step (f) by transmitting the device-specific commands over the secure network connections.
25. The network management computer of
the previously-stored configuration profile specifies operating system software to be used by each device of the group, and
the processor is programmed to perform step (e) by generating device-specific commands that include commands to install the specified operating system software on at least one device of the group.
26. The network management computer of
the previously-stored configuration profile specifies application software to be used by each device of the group, and
the processor is programmed to perform step (e) by generating device-specific commands that include commands to install the specified application software on at least one device of the group.
27. The network management computer of
28. The network management computer of
(i) receive selections of individual configuration parameters from the previously-stored configuration profile, and
(j) modify the selected individual configuration parameters.
|
This invention relates to automated configuration of multiple devices within a computer network.
The growth of the Internet and other networks has encouraged many businesses to connect multiple facilities to exchange data. These facilities are often quite numerous, and may be dispersed across large geographic areas. In turn, this typically requires installation of numerous gateways, routers, switches and other network control devices to route and/or control transmission of data among the various facilities. These devices may also perform important security functions. As but one example, some devices may act as firewalls to prevent unauthorized access to a business' computer network. Other devices may also (or alternatively) provide a Virtual Private Network (VPN) between facilities so as to prevent unauthorized access to communications between facilities. Some devices may act as proxy servers and provide access to the network, the Internet and to other networks for multiple individual work stations. Some devices may be configured to limit the types of network access available to a particular work station or group of workstations. Numerous routing, access control, security and other functions may also be performed.
The operation of each network control device is typically governed by operating system and application software that is stored on and executed by the device. These software (operating systems and applications) usually have a large number of configurable parameters which must be set to specific values for desired operation of the network device. Many of these parameter settings are often the same for a large group of devices in a network. Examples include server addresses, access policies, file transfer size restrictions, local time to be used, various procedures to follow in fault conditions, alarms to transmit, etc. Setting these parameters typically requires opening a connection with each device and using the Command Line Interface (CLI) or other command shell that allows entry of commands. Various commands are then issued to and executed by the device to set the software parameters. The form and syntax of those commands usually depends upon the version of the operating system or application software that is running on the device.
Remotely configuring numerous network control devices presents various problems for network management personnel. In large deployments of new devices, one or two of the devices are often taken to a laboratory or other facility and experimented upon to determine a standard configuration for the device. The software required for that configuration, as well as parameters for that software, are then noted. The remaining new devices are then physically placed in the network. From one or more remote locations, network personnel individually access each new device over the network and enter device-specific commands to configure the device in conformity with the standard configuration. This process is labor-intensive, time-consuming and expensive. Moreover, device-by-device configuration by a human operator generally requires tedious and repetitive command entry, and is subject to human error.
These problems may be more acute when reconfiguring multiple devices already installed within a network. For example, all devices in a group of network control devices may not be physically homogeneous. Devices may use different versions of operating system and/or application software. When it is necessary to reconfigure or adjust the configuration of the devices within the group, different software on the devices may require different settings and/or different commands to change the settings. This further complicates the task of network management personnel. In addition to accessing and configuring each individual device, the personnel must also identify the specific software that the device operates, as well as any other relevant device-specific information that could affect how the device is accessed and/or configured. The network personnel must then maintain a separate set of configuration data and/or instructions for each device/software combination, and must use the correct data and/or instruction set for each device. This additional complication can make the task even more time-consuming, expensive and error-prone.
The present invention allows automatic and remote configuration of multiple network control devices according to a desired configuration profile. Deploying a given configuration profile may include any of setting software parameters, enabling or disabling software, installing new software, and un-installing existing software. A configuration profile is provided, and has configuration data applicable to multiple network control devices. Connections are established to those devices. Identifying information may be obtained from each device, which may then be used to identify an appropriate configuration deployment routine set. Once identified, the routine set is used to convert configuration data from the configuration profile into device-specific commands for each device. The configuration commands are then transmitted to the devices. In some embodiments, the commands can be transmitted one at a time, and an acknowledgement and/or confirmation obtained that the configuration command has been properly executed by the device. In other embodiments, the configuration commands can be in script or batch form. In some embodiments, the configuration profile is stored in Extensible Markup Language (XML) format or other markup language format.
The present invention allows automated configuration of a group of network control devices. As used herein, “network control device” (or simply “device”) includes gateways, routers, switches, bridges, proxy servers and other physical devices located within a network that route or allow communications between other points within the network. Those other points may be individual workstations, client computers communicating with a host computer (or vice versa), other network control devices, an external (to the network) computer attempting to access a computer within the network, or any other component or collection of components capable of data communication. The present invention is described by reference to an embodiment employing a specific data format (Extensible Markup Language, or XML) and programming language (the Java® programming language from Sun Microsystems, Inc. of Santa Clara, Calif.). However, any data format, programming language, hardware or software identified is only by way of example, and not intended as a limitation unless specifically recited as such in a claim. The invention could be implemented using other data formats, programming languages, hardware and software.
Also shown in
Elements 36 contain configuration data for the Domain Name Server (DNS) used by a device 12. Element 38 contains data for configuring internal system failure routines within a device, such as identifying where e-mail error messages should be sent. In the example, a device operating with this configuration profile will send an e-mail to “jones@examplecompany.com” in the event of a system failure. Element 40 contains data to configure the local time used by a device, and element 42 contains configuration information for various system logging and security features of a device. Element 44 includes configuration data for File Transfer Protocol (FTP) and Telnet communications. Element 46 includes configuration data for application programs that may be installed upon a device. As part of the example, a device operating under this configuration profile will have an application program known as “AppName,” and “parameter1” of AppName will be set to “true.”
Tag 47 marks the beginning of a “configActions” element. This element may be used to identify miscellaneous actions that might be carried out in connection with (or on completion of) configuring a device. For example, “fileTransferAction” element 48 can be used to cause upload of a file to a device from a server. Element 50 (“scriptAction”) includes data identifying various script files (or batch files) that a device might run, where those script files are located, and various parameters for those scripts. An “executeCommand” element (not shown) could be used to cause a device to execute a single command.
The various elements and attribute/value pairs in
Within
Configuration file 22 (
Once the administrator identifies the devices to be configured and the configuration(s) to be deployed, deployment software 25 opens a network connection with each device 12. In one preferred embodiment, deployment software 25 may simultaneously open connections to multiple devices on multiple programming threads. As shown in
As shown in
In a preferred embodiment, configuration profile deployment is executed so as to set individual configuration parameters one at a time. In this manner, more fine-grained error handling is possible if a particular configuration command fails. Alternatively, deployment software 25 may convert the configuration file into a script file containing a sequence of commands to set multiple individual configuration parameters, and download the script upon a device 12 for batch execution of those commands. For example, if the configuration file is in XML format, the XML file can be transformed (via an Extensible Stylesheet Language Transformation (XSLT)) into a configuration script that is specific to the operating system and/or application(s) loaded on a particular device. A separate script can be generated for each device. Each script can then be downloaded to its target device. Each target device can then execute its script.
If a configuration profile is to be deployed, the devices to be configured are first selected at block 118. Next, the configuration profile is selected at block 120. At block 122, an opportunity is provided to edit the configuration. In one alternative, actual changes to the configuration file(s) for the profile are made (i.e., the actual file is modified). In another alternative, the profile changes could be temporarily stored and later used to modify execution of a deployment routine. Either of these alternatives (or other alternatives) could be provided to a user via a GUI that allows expansion of a chosen profile and selection/deselection of individual configuration parameters. The configuration profile can thus be modified without physically reconfiguring a device (such as device 12′) and re-extracting the configuration data. If, for example, an IP address for a server changes subsequent to initial creation of the configuration file, the configuration file can be opened and the appropriate IP address changed. In a preferred embodiment, the configuration file is in XML format, and can be edited using various commercially-available XML editors, or with a simple text editor.
If it is decided to edit the configuration, changes are made at block 124. If configuration editing was not desired at block 122, the process would omit block 124. A determination is then made at block 126 regarding whether there are any selected devices remaining to be configured. If so, a connection to the next device to be configured is created at step 128. In a preferred embodiment, this connection is made via secure shell (SSH) or other secure connection. After connecting to the device, initial identifying data (such as, e.g., operating system version and application software present) is retrieved at block 130. The initial identifying data is then mapped to a Java® class (or other deployment routine set) at block 132. The class (or other routine set) is then loaded at block 134. Device specific commands are then generated at block 136 based on the deployment routine set, the configuration file for the selected configuration profile, and any edits to (or other changes from) the information in the configuration file.
At block 138, a determination is made regarding whether any of the commands (created at block 136) remain to be sent to the device. If so, the next command is sent at block 140. In a preferred embodiment, the commands are ordered so as to first install a new operating system (or operating system version) if required, to then install any new application software (or version), to then enable/disable features of the new software, and to then set other configuration parameters. At block 142, an acknowledgement or other confirmation is received from the device that the command has been executed. This confirmation may either be automatic, or may result from commands sent from the deployment software (as part of step 140) to confirm execution of a deployment command. After confirmation of a deployment command, execution returns to block 138. If additional deployment commands remain, the loop continues until all commands have been transmitted and confirmed. If no deployment commands remain, the process returns to block 126, and the next device is configured. If there are no devices remaining for configuration at block 126, the process terminates.
Although specific examples of carrying out the invention have been described, those skilled in the art will appreciate there are numerous variations and permutations of the above-described systems and methods that are involved in the spirit and scope of the invention as set forth in the appended claims. For example, a machine-readable medium could have machine-executable instructions stored thereon such that, when the instructions are read and executed by an appropriate device (or devices), steps of a method according to the invention are performed. As indicated above, other formats in addition to, or instead of, XML may be implemented. Similarly, various programming languages may be used. The various procedures and steps discussed above may be rearranged and their performance distributed across multiple hardware platforms and software applications. These and other modifications are within the scope of the invention as defined in the attached claims.
Patent | Priority | Assignee | Title |
10049075, | Oct 06 2011 | Honeywell International, Inc. | Device management using virtual interfaces |
10678567, | Jun 01 2017 | OMNISSA, LLC | Remote VPN configuration using dynamically generated configuration profiles |
10769594, | Jun 01 2017 | OMNISSA, LLC | Dynamically generated configuration profiles based on device operating system |
10868717, | Jan 31 2019 | Hewlett Packard Enterprise Development LP | Concurrent profile deployments |
10936999, | Jun 01 2017 | OMNISSA, LLC | Remote email configuration using dynamically generated configuration profiles |
10976891, | Dec 08 2009 | Hand Held Products, Inc. | Remote device management interface |
11023218, | Dec 31 2017 | WELLS FARGO BANK, N A | Metadata driven product configuration management |
11443283, | Jun 01 2017 | OMNISSA, LLC | Dynamic construction of configuration profiles for settings common across different operating systems |
11461112, | Feb 07 2019 | International Business Machines Corporation | Determining feature settings for code to deploy to a system by training a machine learning module |
11853737, | Dec 31 2017 | Wells Fargo Bank, N.A. | Metadata driven product configuration management |
7328217, | Nov 26 2003 | ACQUIOM AGENCY SERVICES LLC, AS ASSIGNEE | System and method for detecting and storing file identity change information within a file system |
7437375, | Aug 17 2004 | ARCTERA US LLC | System and method for communicating file system events using a publish-subscribe model |
7487138, | Aug 25 2004 | ARCTERA US LLC | System and method for chunk-based indexing of file system content |
7509625, | Mar 10 2004 | NETSKOPE, INC | System and method for comprehensive code generation for system management |
7546357, | Jan 07 2004 | ADEIA TECHNOLOGIES INC | Configuring network settings using portable storage media |
7552202, | Mar 10 2005 | International Business Machines Corporation | System and method to uniquely identify identically configured branches in a distributed enterprise |
7562216, | Jun 28 2004 | ARCTERA US LLC | System and method for applying a file system security model to a query system |
7587512, | Oct 16 2002 | NETSKOPE, INC | System and method for dynamic bandwidth provisioning |
7590728, | Mar 10 2004 | OPENTV, INC | System and method for detection of aberrant network behavior by clients of a network access gateway |
7596369, | Apr 05 2006 | Qwest Communications International Inc; Qwest Communications International, Inc. | Translation of messages between media types |
7610621, | Mar 10 2004 | NETSKOPE, INC | System and method for behavior-based firewall modeling |
7624438, | Aug 20 2003 | NETSKOPE, INC | System and method for providing a secure connection between networked computers |
7665130, | Mar 10 2004 | NETSKOPE, INC | System and method for double-capture/double-redirect to a different location |
7676473, | Dec 02 2005 | Qwest Communications International Inc | Propagation of user preferences to end devices |
7694277, | May 14 2003 | Microsoft Technology Licensing, LLC | Cross version customization of design environment |
7703005, | May 21 2004 | Oracle International Corporation | Method to generate scripts from XML |
7747718, | Oct 22 2003 | Omron Corporation | Control system apparatus, method for setting control system and setting program |
7857222, | Aug 16 2007 | HAND HELD PRODUCTS, INC | Data collection system having EIR terminal interface node |
7930374, | Mar 23 2004 | ADEIA TECHNOLOGIES INC | Configuring network settings using portable storage media |
7949727, | Mar 31 2005 | BANG & OLUFSEN A S | Table based distributed control for a network of consumer electronics |
8019866, | Mar 10 2004 | OPENTV, INC | System and method for detection of aberrant network behavior by clients of a network access gateway |
8025233, | Aug 16 2007 | Hand Held Products, Inc. | Data collection system having EIR terminal interface node |
8078476, | Apr 05 2006 | Qwest Communications International Inc.; Qwest Communications International Inc | Cross-platform calendar notifications |
8117639, | Oct 10 2002 | NETSKOPE, INC | System and method for providing access control |
8145735, | Jan 07 2004 | Rovi Technologies Corporation | Configuring network settings using portable storage media |
8156207, | Oct 08 2004 | Hewlett Packard Enterprise Development LP | Method and apparatus for remotely configuring network devices |
8170189, | Nov 02 2005 | Qwest Communications International Inc | Cross-platform message notification |
8204950, | Sep 15 2005 | Qwest Communications International Inc.; Qwest Communications International Inc | Webpage search |
8214469, | Apr 06 2006 | Qwest Communications International Inc. | Multiple use of common perspectives |
8270325, | Feb 21 2006 | Pacific Star Communications, Inc. | Mobile broadband communications system, such as a deployable self-contained portable system |
8297508, | Aug 16 2007 | Hand Held Products, Inc. | Data collection system having EIR terminal interface node |
8306991, | Jun 07 2004 | ARCTERA US LLC | System and method for providing a programming-language-independent interface for querying file system content |
8320535, | Apr 06 2006 | Qwest Communications International Inc. | Selectable greeting messages |
8321843, | Feb 09 2009 | Tranxition Corporation | Automatic analysis of an application's run-time settings |
8374104, | Mar 30 2005 | Echelon Corporation | Simple installation of devices on a network |
8381273, | Aug 20 2003 | NETSKOPE, INC | System and method for providing a secure connection between networked computers |
8397282, | Mar 10 2004 | NETSKOPE, INC | Dynamically adaptive network firewalls and method, system and computer program product implementing same |
8429725, | Aug 20 2003 | NETSKOPE, INC | System and method for providing a secure connection between networked computers |
8464242, | Jul 08 2009 | Tranxition Corporation | Virtualization of configuration settings |
8484695, | Oct 10 2002 | NETSKOPE, INC | System and method for providing access control |
8539123, | Oct 06 2011 | Honeywell International, Inc.; HONEYWELL INTERNATIONAL INC , DOING BUSINESS AS D B A HONEYWELL SCANNING & MOBILITY | Device management using a dedicated management interface |
8543693, | Mar 10 2004 | OPENTV, INC | System and method for detection of aberrant network behavior by clients of a network access gateway |
8543710, | Mar 10 2004 | NETSKOPE, INC | Method and system for controlling network access |
8556174, | Aug 16 2007 | Hand Held Products, Inc. | Data collection system having EIR terminal interface node |
8621123, | Oct 06 2011 | Honeywell International Inc.; HONEYWELL INTERNATIONAL INC , DOING BUSINESS AS D B A HONEYWELL SCANNING & MOBILITY | Device management using virtual interfaces |
8799512, | Oct 19 2005 | Qwest Communications International Inc | Cross-platform support for a variety of media types |
8819751, | May 16 2006 | ADEIA MEDIA HOLDINGS LLC | Socially networked television experience |
8856095, | Jun 21 2007 | Microsoft Technology Licensing, LLC | Configurable plug-in architecture for manipulating XML-formatted information |
8868803, | Oct 06 2011 | Honeywell Internation Inc. | Managing data communication between a peripheral device and a host |
8918564, | Oct 06 2011 | Honeywell International Inc. | Device management using virtual interfaces |
8925818, | Aug 16 2007 | Hand Held Products, Inc. | Data collection system having EIR terminal interface node |
8990361, | Apr 23 2010 | PSION INC | Method and system for proximity-based, peer-initiated device configuration |
9053055, | Oct 06 2011 | Honeywell International | Device management using virtual interfaces cross-reference to related applications |
9172773, | Dec 20 2012 | Microsoft Technology Licensing, LLC | Managing technology resources across multiple platforms |
9251498, | Oct 23 2006 | Oracle International Corporation | Facilitating deployment of customizations of enterprise applications |
9258188, | Aug 16 2007 | Hand Held Products, Inc. | Data collection system having EIR terminal interface node |
9298667, | Oct 06 2011 | Honeywell International, Inc | Device management using virtual interfaces cross-reference to related applications |
9323821, | Apr 05 2006 | Qwest Communications International Inc.; Qwest Communications International Inc | Network repository auto sync wireless handset |
9497092, | Dec 08 2009 | Hand Held Products, Inc. | Remote device management interface |
9509564, | Dec 20 2012 | Microsoft Technology Licensing, LLC | Managing technology resources across multiple platforms |
9509801, | Aug 16 2007 | Hand Held Products, Inc. | Data collection system having EIR terminal interface node |
9929906, | Aug 16 2007 | Hand Held Products, Inc. | Data collection system having EIR terminal interface node |
Patent | Priority | Assignee | Title |
5838907, | Feb 20 1996 | Hewlett Packard Enterprise Development LP | Configuration manager for network devices and an associated method for providing configuration information thereto |
5889470, | Mar 07 1997 | Paradyne Corporation | Digital subscriber line access device management information base |
6026438, | Oct 31 1997 | Bank of America Corporation | Dynamic workstation configuration processor |
6041347, | Oct 24 1997 | Unified Access Communications | Computer system and computer-implemented process for simultaneous configuration and monitoring of a computer network |
6055314, | Mar 22 1996 | Rovi Technologies Corporation | System and method for secure purchase and delivery of video content programs |
6081517, | Sep 22 1997 | Realtek Semiconductor Corporation | Digital subscriber loop access circuit for digital switch and packet network interconnections |
6098098, | Nov 15 1996 | HANGER SOLUTIONS, LLC | System for managing the configuration of multiple computer devices |
6141752, | May 05 1998 | Comcast Cable Communications Management, LLC | Mechanism for facilitating secure storage and retrieval of information on a smart card by an internet service provider using various network computer client devices |
6192436, | Sep 18 1998 | Xilinx Inc.; Xilinx, Inc | System and method for configuration of electronic devices using a smart card which having configuration data stored therein |
6343287, | May 19 1999 | Oracle America, Inc | External data store link for a profile service |
6446071, | Apr 26 1999 | International Business Machines Corporation | Method and system for user-specific management of applications in a heterogeneous server environment |
6449715, | Oct 04 1999 | Fisher-Rosemount Systems, Inc. | Process control configuration system for use with a profibus device network |
6542515, | May 19 1999 | Oracle America, Inc | Profile service |
6611876, | Oct 28 1999 | International Business Machines Corporation | Method for establishing optimal intermediate caching points by grouping program elements in a software system |
6721880, | May 31 2000 | Alcatel-Lucent USA Inc | Method and apparatus for maintaining configuration information in a computing environment |
6754731, | May 14 2002 | HEWLETT-PACKARD DEVELOPMENT COMPANY, L P | Device settings based on usage history |
20020161888, | |||
EP1059791, | |||
WO2080515, | |||
WO9857474, |
Executed on | Assignor | Assignee | Conveyance | Frame | Reel | Doc |
Dec 20 2002 | Nokia, Inc. | (assignment on the face of the patent) | / | |||
Dec 20 2002 | Debashis, Das | NOKIA INC | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 013638 | /0842 | |
Jan 16 2014 | NOKIA INC | Nokia Corporation | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 032188 | /0521 | |
Jan 16 2015 | Nokia Corporation | Nokia Technologies Oy | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 035567 | /0073 |
Date | Maintenance Fee Events |
Aug 12 2009 | M1551: Payment of Maintenance Fee, 4th Year, Large Entity. |
Mar 14 2013 | M1552: Payment of Maintenance Fee, 8th Year, Large Entity. |
Aug 31 2017 | M1553: Payment of Maintenance Fee, 12th Year, Large Entity. |
Date | Maintenance Schedule |
Mar 14 2009 | 4 years fee payment window open |
Sep 14 2009 | 6 months grace period start (w surcharge) |
Mar 14 2010 | patent expiry (for year 4) |
Mar 14 2012 | 2 years to revive unintentionally abandoned end. (for year 4) |
Mar 14 2013 | 8 years fee payment window open |
Sep 14 2013 | 6 months grace period start (w surcharge) |
Mar 14 2014 | patent expiry (for year 8) |
Mar 14 2016 | 2 years to revive unintentionally abandoned end. (for year 8) |
Mar 14 2017 | 12 years fee payment window open |
Sep 14 2017 | 6 months grace period start (w surcharge) |
Mar 14 2018 | patent expiry (for year 12) |
Mar 14 2020 | 2 years to revive unintentionally abandoned end. (for year 12) |