US20090031010A1 - OS Independent Device Management Methods and Apparatuses - Google Patents

OS Independent Device Management Methods and Apparatuses Download PDF

Info

Publication number
US20090031010A1
US20090031010A1 US12/243,847 US24384708A US2009031010A1 US 20090031010 A1 US20090031010 A1 US 20090031010A1 US 24384708 A US24384708 A US 24384708A US 2009031010 A1 US2009031010 A1 US 2009031010A1
Authority
US
United States
Prior art keywords
controller
operating system
independent
interface
coupled
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Abandoned
Application number
US12/243,847
Inventor
Vincent J. Zimmer
Michael A. Rothman
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Individual
Original Assignee
Individual
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Individual filed Critical Individual
Priority to US12/243,847 priority Critical patent/US20090031010A1/en
Publication of US20090031010A1 publication Critical patent/US20090031010A1/en
Abandoned legal-status Critical Current

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/30Authentication, i.e. establishing the identity or authorisation of security principals
    • G06F21/305Authentication, i.e. establishing the identity or authorisation of security principals by remotely controlling device operation
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/30Authentication, i.e. establishing the identity or authorisation of security principals
    • G06F21/31User authentication
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/70Protecting specific internal or peripheral components, in which the protection of a component leads to protection of the entire computer
    • G06F21/82Protecting input, output or interconnection devices
    • G06F21/83Protecting input, output or interconnection devices input devices, e.g. keyboards, mice or controllers thereof

Definitions

  • the present invention relates generally to the field of computing devices, and, in particular, to management of such devices.
  • computing devices are managed by/through their operating systems.
  • the management tasks may include device configuration, controlling user access (by authorized users only), logging various system activities, and so forth.
  • the task of managing a computing device has become increasingly complex. Further, it is often necessary or desirable to manage a computing device when the operating system is non-operational (“frozen”), or otherwise unavailable.
  • FIG. 1 illustrates an overview of the invention, in accordance with various embodiments
  • FIGS. 2 a - 2 c illustrate a flow chart view of the operational flow of the management controller of the host device of FIG. 1 in accordance with various embodiments;
  • FIG. 3 illustrates an example keyboard and an example key map of FIG. 1 , in accordance with various embodiments.
  • FIG. 4 illustrates additional example keyboards.
  • Illustrative embodiments of the present invention include but are not limited to operating system independent methods for managing a computing device, components contributing to the practice of these methods, in part or in whole, and devices endowed with such components.
  • computing device 100 includes processor 102 , memory 104 , memory-bus controller 114 , and bus 112 , coupled to each other as shown. Additionally, computing device 100 includes mass storage device 106 , input/output (I/O) devices 108 , and communication interfaces 110 coupled to each other, and the earlier described elements as shown. Memory 104 and mass storage device 106 include in particular, temporal and persistent copies of operating system 122 respectively. In various embodiments, I/O devices 108 include an output device, such as a display, for locally outputting data, including outputting of a prompt for user authentication (e.g.
  • communication interfaces 110 include a networking interface coupling computing device 100 to a network, to facilitate communication with a remote user, a remote user authentication, device configuration, and/or management service.
  • the remote user authentication service, remote device configuration service and remote management service may be separated or combined services.
  • computing device 100 is endowed with management controller 116 and non-volatile storage 118 , coupled to each other and the earlier described elements as shown.
  • non-volatile storage 118 further has key map 124 and user authentication information (such as, passwords) 126 stored therein.
  • management controller 116 is adapted to manage computing device 100 , independent of operating system 122 , that is, irrespective of its availability or operational state. More specifically, for the embodiments, management controller 116 is adapted to use the data/information stored in non-volatile storage 118 , when managing computing device 100 , independent of operating system 122 (hereinafter, for ease of understanding, simply “managing computing device 100 ”).
  • management controller 116 includes an I/O interface (not shown) for interfacing with memory-bus controller 114 , enabling it, among other things, to be operatively coupled to I/O devices 108 and communication interfaces 110 .
  • management controller 116 may be coupled to I/O devices 108 and/or communication interfaces 110 directly, without going through memory-bus controller 114 .
  • management controller 116 may be integrated with memory-bus controller 114 and/or other components.
  • computing device 100 is adapted such that, it may be powered on remotely (e.g. “powering on” computing device 100 , through a network interface having a power saving, never off, “sleep” mode of operation).
  • a power-on or start-up signal is provided to management controller 116 as well as to processor 102 .
  • management controller 116 is adapted to perform a number of user authentication operations, and provides processor 102 with a “user authenticated” signal, on successful authentication of the user causing the start-up.
  • Processor 102 is adapted to wait for the “user authenticated” signal before performing the conventional start up of operating system 122 .
  • each of the earlier described elements represents a broad range of the corresponding element known in the art or to be designed consistent with the teachings of the present invention. They perform their conventional functions, i.e. processing, storage, and so forth.
  • operating system 122 is adapted to perform its conventional function of managing computing device 100 .
  • computing device 100 may have more or less elements, and/or different architectures.
  • computing device 100 may be a desktop computer, a tablet computer, a palm sized computing device, a set-top box, or a media player (e.g. a CD or DVD player).
  • management controller 116 determines whether the start-up is caused locally or remotely, block 202 , and proceeds to prompt the local/remote user for authentication accordingly, e.g. initiating a log-in process requesting for the local/remote user's password to authenticate the local/remote user causing the start-up is indeed an authorized user, block 204 a or 204 b .
  • the prompting of the local/remote user for authentication information may be performed in any one of a number of known or to be designed techniques.
  • management controller 116 accesses key map 124 stored in non-volatile storage 118 and uses key map 124 to generate a series of codes representative of the authentication information (e.g. password) entered.
  • key map 124 provides the various unicodes to be generated for various key activations, and management controller 116 generates them accordingly, during operation 206 .
  • An example keyboard 302 and its corresponding version of key map 124 are shown in FIG. 3 . Accordingly, keyboard 302 may be a wide range of keyboards 302 a - 302 i of different languages, as illustrated in FIG. 4 .
  • the access and translate operations of block 206 is not performed in the case where the start-up is caused by a remote user.
  • the embodiments assume the authentication information is presented by the remote user in unicodes. In alternate embodiments, the authentication information may also be presented in non-unicodes, requiring management controller 116 to perform the translation as in the case of a local user. In still other embodiments, other code schemes with or without translation may be practiced instead.
  • management controller 116 determines whether it is configured to locally authenticate the user or authenticate the user with a remote authentication source, block 208 .
  • management controller 116 may be practiced with a pre-configuration of local or remote configuration, eliminating the need for dynamic configuration.
  • management controller 116 on determining that it is to authenticate the local/remote user locally, accesses the reference authentication information (e.g. password) pre-stored in non-volatile storage 118 , and authenticates the local/remote user causing the start-up, block 210 .
  • management controller 116 on determining that it is to authenticate the local/remote user remotely, management controller 116 provides the received (and translated) authentication information (e.g. password) pre-stored to the remote authentication authority to authenticate the local/remote user causing the start-up, block 212 .
  • management controller 116 determines whether the local/remote user causing the start-up is an authorized user, block 214 . For the embodiments, if the local/remote user is determined to be an authorized user, management controller 116 provides processor 102 with the “authenticated” signal, to cause processor 102 to proceed with conventional start-up of operating system 122 , block 216 .
  • management controller 116 determines the local/remote user causing the start-up to be an unauthorized user, for the embodiments, management controller 116 denies access to the unauthorized user (e.g. by not providing processor 102 with the “authenticated” signal), block 218 . Thereafter, management controller 116 may continue its operation in any one of a number of implementation manners. For example, management controller 116 may simply cause computing device 100 to power off, or otherwise shut down.
  • processor 102 is provided with the “authenticated” signal, and proceeds with starting operating system 122 in a convention manner, assuming the start up process was performed successfully, computing device 100 becomes operational.
  • management controller 116 determines if it is configured to contact a remote configuration manager for configuration information to dynamically configure computing device 100 , block 220 .
  • management controller 116 contacts the remote configuration manager, obtains the configuration information, and configures computing device 100 accordingly, blocks 222 - 224 .
  • management controller 116 determines whether it is to monitor, log and report key activations, during the operation of computing device 100 , block 226 . If it is determined that, management controller 116 is to monitor, log and report key activations, during the operation of computing device 100 , management controller 116 monitors, logs and reports key activations (e.g. periodically, after a predetermined time period, or a predetermined amount of logged key activations), during the operation of computing device 100 , block 228 .
  • key activations e.g. periodically, after a predetermined time period, or a predetermined amount of logged key activations
  • management controller 116 continues with “other” operations, if any.
  • management controller 116 continues with “other” operations, if any.
  • management controller 116 is able to manage computing device 100 , including but not limited to, e.g. authentication of a local/remote user, dynamically configuring computing device 100 , and/or performing one or more managing functions, such as monitoring, logging, and reporting key activations during operation, independent of operating system 122 , i.e. regardless of its operational state or availability.
  • the remote authentication source and the remote configuration manager may be different or one of the same.

Abstract

An apparatus adapted to facilitate remote configuration and/or management of a system, independent of its operating system, is disclosed. In various embodiments, the apparatus includes a first and a second interface coupled to an input device and a network interface of the system respectively, and a controller.

Description

    CROSS-REFERENCES TO RELATED APPLICATIONS
  • This present application is a divisional of U.S. patent application Ser. No. 11/095,151 filed Mar. 30, 2005 and entitled “OS Independent Device Management Methods and Apparatuses”. The specification of said patent is hereby incorporated in its entirety, except for those sections, if any, that are inconsistent with this specification.
  • FIELD OF THE INVENTION
  • The present invention relates generally to the field of computing devices, and, in particular, to management of such devices.
  • BACKGROUND OF THE INVENTION
  • Advances in microprocessor and related technologies have led to wide spread deployment and adoption of numerous general purpose as well as special purpose computing devices. General purpose computing devices, such as servers and desktop computers, are now endowed with computing power that was once reserved for the most expensive high end computers, requiring special conditioned environments to operate. At the same time, advances in networking, telecommunication, satellite, and other related technologies have also led to an increase in connectivity between computing devices, making possible networked computing over private and/or public networks, such as the Internet.
  • Conventionally, computing devices are managed by/through their operating systems. The management tasks may include device configuration, controlling user access (by authorized users only), logging various system activities, and so forth. As technology and applications continue to evolve in sophistication, the task of managing a computing device has become increasingly complex. Further, it is often necessary or desirable to manage a computing device when the operating system is non-operational (“frozen”), or otherwise unavailable.
  • BRIEF DESCRIPTION OF THE DRAWINGS
  • The present invention will be described by way of exemplary embodiments, but not limitations, illustrated in the accompanying drawings in which like references denote similar elements, and in which:
  • FIG. 1 illustrates an overview of the invention, in accordance with various embodiments;
  • FIGS. 2 a-2 c illustrate a flow chart view of the operational flow of the management controller of the host device of FIG. 1 in accordance with various embodiments;
  • FIG. 3 illustrates an example keyboard and an example key map of FIG. 1, in accordance with various embodiments; and
  • FIG. 4 illustrates additional example keyboards.
  • DETAILED DESCRIPTION OF ILLUSTRATIVE EMBODIMENTS
  • Illustrative embodiments of the present invention include but are not limited to operating system independent methods for managing a computing device, components contributing to the practice of these methods, in part or in whole, and devices endowed with such components.
  • Various aspects of the illustrative embodiments will be described using terms commonly employed by those skilled in the art to convey the substance of their work to others skilled in the art. However, it will be apparent to those skilled in the art that alternate embodiments may be practiced with only some of the described aspects. For purposes of explanation, specific numbers, materials, and configurations are set forth in order to provide a thorough understanding of the illustrative embodiments. However, it will be apparent to one skilled in the art that alternate embodiments may be practiced without the specific details. In other instances, well-known features are omitted or simplified in order not to obscure the illustrative embodiments.
  • Further, various operations will be described as multiple discrete operations, in turn, in a manner that is most helpful in understanding the illustrative embodiments; however, the order of description should not be construed as to imply that these operations are necessarily order dependent. In particular, these operations need not be performed in the order of presentation.
  • The phrase “in one embodiment” is used repeatedly. The phrase generally does not refer to the same embodiment; however, it may. The terms “comprising”, “having”, and “including” are synonymous, unless the context dictates otherwise.
  • Referring now to FIG. 1, wherein an overview of the present invention, in accordance with various embodiments, is shown. As illustrated, for the embodiments, computing device 100 includes processor 102, memory 104, memory-bus controller 114, and bus 112, coupled to each other as shown. Additionally, computing device 100 includes mass storage device 106, input/output (I/O) devices 108, and communication interfaces 110 coupled to each other, and the earlier described elements as shown. Memory 104 and mass storage device 106 include in particular, temporal and persistent copies of operating system 122 respectively. In various embodiments, I/O devices 108 include an output device, such as a display, for locally outputting data, including outputting of a prompt for user authentication (e.g. during a log-in process), and an input device, such as a keyboard, for locally inputting data, including inputting of authentication information by a user (e.g. during the log-in process). In various embodiments, communication interfaces 110 include a networking interface coupling computing device 100 to a network, to facilitate communication with a remote user, a remote user authentication, device configuration, and/or management service. In various embodiments, the remote user authentication service, remote device configuration service and remote management service, may be separated or combined services.
  • Further, computing device 100 is endowed with management controller 116 and non-volatile storage 118, coupled to each other and the earlier described elements as shown. For the embodiments, non-volatile storage 118 further has key map 124 and user authentication information (such as, passwords) 126 stored therein. As will be described in more detail below, management controller 116 is adapted to manage computing device 100, independent of operating system 122, that is, irrespective of its availability or operational state. More specifically, for the embodiments, management controller 116 is adapted to use the data/information stored in non-volatile storage 118, when managing computing device 100, independent of operating system 122 (hereinafter, for ease of understanding, simply “managing computing device 100”).
  • In various embodiments, management controller 116 includes an I/O interface (not shown) for interfacing with memory-bus controller 114, enabling it, among other things, to be operatively coupled to I/O devices 108 and communication interfaces 110. In other embodiments, management controller 116 may be coupled to I/O devices 108 and/or communication interfaces 110 directly, without going through memory-bus controller 114. In still other embodiments, management controller 116 may be integrated with memory-bus controller 114 and/or other components.
  • Additionally, computing device 100 is adapted such that, it may be powered on remotely (e.g. “powering on” computing device 100, through a network interface having a power saving, never off, “sleep” mode of operation). At power-on, a power-on or start-up signal is provided to management controller 116 as well as to processor 102. As will be described in more detail below, management controller 116 is adapted to perform a number of user authentication operations, and provides processor 102 with a “user authenticated” signal, on successful authentication of the user causing the start-up. Processor 102 is adapted to wait for the “user authenticated” signal before performing the conventional start up of operating system 122.
  • Except for the logic provided to management controller 116, the data/information stored in non-volatile storage 118, and the modified behavior of processor 102, each of the earlier described elements represents a broad range of the corresponding element known in the art or to be designed consistent with the teachings of the present invention. They perform their conventional functions, i.e. processing, storage, and so forth. For example, operating system 122 is adapted to perform its conventional function of managing computing device 100.
  • In various embodiments, computing device 100 may have more or less elements, and/or different architectures. In various embodiments, computing device 100 may be a desktop computer, a tablet computer, a palm sized computing device, a set-top box, or a media player (e.g. a CD or DVD player).
  • Referring now to FIGS. 2 a-2 c wherein a flow chart view of portions of the operations performed by management controller 116 is shown. As illustrated, on start-up, e.g. power on, management controller 116 determines whether the start-up is caused locally or remotely, block 202, and proceeds to prompt the local/remote user for authentication accordingly, e.g. initiating a log-in process requesting for the local/remote user's password to authenticate the local/remote user causing the start-up is indeed an authorized user, block 204 a or 204 b. The prompting of the local/remote user for authentication information may be performed in any one of a number of known or to be designed techniques.
  • Thereafter, on receipt of the authentication information being presented by a local user (e.g. a sequence of signals representative of a sequence of activation of keys of a keyboard to input a password), management controller 116 accesses key map 124 stored in non-volatile storage 118 and uses key map 124 to generate a series of codes representative of the authentication information (e.g. password) entered. In various embodiments, key map 124 provides the various unicodes to be generated for various key activations, and management controller 116 generates them accordingly, during operation 206. An example keyboard 302 and its corresponding version of key map 124 are shown in FIG. 3. Accordingly, keyboard 302 may be a wide range of keyboards 302 a-302 i of different languages, as illustrated in FIG. 4.
  • For the embodiments, the access and translate operations of block 206 is not performed in the case where the start-up is caused by a remote user. The embodiments assume the authentication information is presented by the remote user in unicodes. In alternate embodiments, the authentication information may also be presented in non-unicodes, requiring management controller 116 to perform the translation as in the case of a local user. In still other embodiments, other code schemes with or without translation may be practiced instead.
  • Continuing to refer to FIGS. 2 a-2 c, upon either receiving and translating the authentication information in the desired coding format, block 204 a and 206, or receiving the authentication information in the desired coding format, block 204 b, for the embodiments, management controller 116 determines whether it is configured to locally authenticate the user or authenticate the user with a remote authentication source, block 208. In alternate embodiments, management controller 116 may be practiced with a pre-configuration of local or remote configuration, eliminating the need for dynamic configuration.
  • For the embodiments, on determining that it is to authenticate the local/remote user locally, management controller 116 accesses the reference authentication information (e.g. password) pre-stored in non-volatile storage 118, and authenticates the local/remote user causing the start-up, block 210. On the other hand, on determining that it is to authenticate the local/remote user remotely, management controller 116 provides the received (and translated) authentication information (e.g. password) pre-stored to the remote authentication authority to authenticate the local/remote user causing the start-up, block 212.
  • Next, at block 214, management controller 116 determines whether the local/remote user causing the start-up is an authorized user, block 214. For the embodiments, if the local/remote user is determined to be an authorized user, management controller 116 provides processor 102 with the “authenticated” signal, to cause processor 102 to proceed with conventional start-up of operating system 122, block 216.
  • On the other hand, if management controller 116 does not determine the local/remote user causing the start-up to be an unauthorized user, for the embodiments, management controller 116 denies access to the unauthorized user (e.g. by not providing processor 102 with the “authenticated” signal), block 218. Thereafter, management controller 116 may continue its operation in any one of a number of implementation manners. For example, management controller 116 may simply cause computing device 100 to power off, or otherwise shut down.
  • Returning to block 216, where processor 102 is provided with the “authenticated” signal, and proceeds with starting operating system 122 in a convention manner, assuming the start up process was performed successfully, computing device 100 becomes operational.
  • For the embodiments, concurrently during the start up process, management controller 116 determines if it is configured to contact a remote configuration manager for configuration information to dynamically configure computing device 100, block 220.
  • If it is determined that management controller 116 is to contact a remote configuration manager for configuration information to dynamically configure computing device 100, management controller 116 contacts the remote configuration manager, obtains the configuration information, and configures computing device 100 accordingly, blocks 222-224.
  • For the various embodiments, on configuring computing device 100, management controller 116 determines whether it is to monitor, log and report key activations, during the operation of computing device 100, block 226. If it is determined that, management controller 116 is to monitor, log and report key activations, during the operation of computing device 100, management controller 116 monitors, logs and reports key activations (e.g. periodically, after a predetermined time period, or a predetermined amount of logged key activations), during the operation of computing device 100, block 228.
  • On the other hand, if it is determined at block 226 that management controller 116 is not configured to contact a remote configuration manager for configuration information to dynamically configure computing device 100, management controller 116 continues with “other” operations, if any.
  • Similarly, back at block 220, if it is determined that management controller 116 is not configured to contact a remote configuration manage for configuration information to dynamically configure computing device 100, management controller 116 continues with “other” operations, if any.
  • Accordingly, management controller 116 is able to manage computing device 100, including but not limited to, e.g. authentication of a local/remote user, dynamically configuring computing device 100, and/or performing one or more managing functions, such as monitoring, logging, and reporting key activations during operation, independent of operating system 122, i.e. regardless of its operational state or availability.
  • Additionally, it should be noted that, in various embodiments, the remote authentication source and the remote configuration manager may be different or one of the same.
  • Although specific embodiments have been illustrated and described herein, it will be appreciated by those of ordinary skill in the art that a wide variety of alternate and/or equivalent implementations may be substituted for the specific embodiments shown and described, without departing from the scope of the present invention. This application is intended to cover any adaptations or variations of the embodiments discussed herein. Therefore, it is manifestly intended that this invention be limited only by the claims and the equivalents thereof.

Claims (13)

1. An apparatus, comprising:
a first input/output (I/O) interface adapted to interface the apparatus to a network; and
a controller adapted to contact a remote configuration administrator for configuration information of a system, and to configure the system accordingly, the system having a storage, an operating system stored in the storage, and a processor coupled to the storage, wherein the controller is configured to contact the remote configuration administrator and configure the system independent of the operating system of the system.
2. The apparatus of claim 1, wherein the system further comprises a network interface, wherein the first I/O interface is coupled to the network through the network interface of the system.
3. The apparatus of claim 1, wherein the system further comprises an input device; the apparatus further comprises a second I/O interface adapted to interface the apparatus to the input device of the system;
wherein the controller is further adapted to log activations of keys of the input device, independent of the operating system, through the second I/O interface if the system is configured to operate with a key logging feature.
4. The apparatus of claim 3, wherein the controller is further adapted to forward the logged key activations to a remote device through the second I/O interface.
5. The apparatus of claim 1, wherein the system further comprises a memory-bus controller to which the storage and the processor are coupled, wherein the apparatus is a discrete component coupled to the memory-bus controller.
6. The apparatus of claim 1, wherein the apparatus is a memory-bus controller of the system to which the storage and the processor are also coupled.
7. A system comprising
a network interface;
a storage having an operating system stored therein;
a processor coupled to the network interface and the storage; and
a by-pass controller having a first and a second input/output interface coupled to the input device and the network interface respectively, and adapted to facilitate remote access and configuration of the system, independent of the operating system.
8. The system of claim 7, wherein the system further comprises a memory-bus controller, to which the storage and the processor are coupled, and the by-pass controller is a discrete component coupled to the memory-bus controller.
9. The system of claim 7, wherein the system further comprises a memory-bus controller, to which the storage and the processor are coupled, integrally comprising the by-pass controller.
10. A method comprising:
a controller of a system having an operating system, contacting a remote configuration administrator for configuration information of the system independent of the operating system; and
the controller causing the system to be configured accordingly, independent of the operating system, based at least in part on the configuration information.
11. The method of claim 10, wherein the controller further logs activations of keys of an input device of the system, independent of the operating system, if the system is configured to operate with a key logging feature.
12. An article of manufacture, comprising:
computer readable storage medium;
a plurality of instructions stored in the storage medium, adapted to enable a controller of a system having in addition to the controller, a processor, an input device, and an operating system to
contact a remote configuration administrator for configuration information of the system independent of the operating system; and
cause the system to be configured accordingly, independent of the operating system, based at least in part on the configuration information.
13. The article of claim 12, wherein the instructions are further adapted to enable the controller to log activations of keys of an input device of the system, independent of the operating system, if the system is configured to operate with a key logging feature.
US12/243,847 2005-03-30 2008-10-01 OS Independent Device Management Methods and Apparatuses Abandoned US20090031010A1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US12/243,847 US20090031010A1 (en) 2005-03-30 2008-10-01 OS Independent Device Management Methods and Apparatuses

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US11/095,151 US7451301B2 (en) 2005-03-30 2005-03-30 OS independent device management methods and apparatuses having a map providing codes for various activations of keys
US12/243,847 US20090031010A1 (en) 2005-03-30 2008-10-01 OS Independent Device Management Methods and Apparatuses

Related Parent Applications (1)

Application Number Title Priority Date Filing Date
US11/095,151 Division US7451301B2 (en) 2005-03-30 2005-03-30 OS independent device management methods and apparatuses having a map providing codes for various activations of keys

Publications (1)

Publication Number Publication Date
US20090031010A1 true US20090031010A1 (en) 2009-01-29

Family

ID=37084432

Family Applications (2)

Application Number Title Priority Date Filing Date
US11/095,151 Expired - Fee Related US7451301B2 (en) 2005-03-30 2005-03-30 OS independent device management methods and apparatuses having a map providing codes for various activations of keys
US12/243,847 Abandoned US20090031010A1 (en) 2005-03-30 2008-10-01 OS Independent Device Management Methods and Apparatuses

Family Applications Before (1)

Application Number Title Priority Date Filing Date
US11/095,151 Expired - Fee Related US7451301B2 (en) 2005-03-30 2005-03-30 OS independent device management methods and apparatuses having a map providing codes for various activations of keys

Country Status (1)

Country Link
US (2) US7451301B2 (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20140354963A1 (en) * 2012-07-12 2014-12-04 Cj Cgv Co., Ltd. Multi-projection system

Families Citing this family (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8108673B2 (en) 2005-04-29 2012-01-31 Cisco Technology, Inc. Configuring interfaces of a switch using templates
US7373537B2 (en) * 2005-06-28 2008-05-13 Intel Corporation Response to wake event while a system is in reduced power consumption state
US8539568B1 (en) 2007-10-03 2013-09-17 Courion Corporation Identity map creation
WO2009076447A1 (en) * 2007-12-10 2009-06-18 Courion Corporaton Policy enforcement using esso
WO2010041852A2 (en) * 2008-10-06 2010-04-15 Noh Sam Hyuk Method and system for perpetual computing using non-volatile random access memory (nvram)
US8806231B2 (en) 2009-12-22 2014-08-12 Intel Corporation Operating system independent network event handling
US10482254B2 (en) * 2010-07-14 2019-11-19 Intel Corporation Domain-authenticated control of platform resources
US8386618B2 (en) 2010-09-24 2013-02-26 Intel Corporation System and method for facilitating wireless communication during a pre-boot phase of a computing device
JP2018089915A (en) * 2016-12-07 2018-06-14 富士ゼロックス株式会社 Processing device, portable apparatus, processing control program and authentication request program

Citations (18)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5181201A (en) * 1990-02-07 1993-01-19 General Dynamics Land Systems Inc. Interface chip device
US5435271A (en) * 1993-08-19 1995-07-25 Invisible Fence Company, Inc. Multi-channel animal control device with external data communication
US5706349A (en) * 1995-03-06 1998-01-06 International Business Machines Corporation Authenticating remote users in a distributed environment
US5828831A (en) * 1995-08-10 1998-10-27 Samsung Electronics Co., Ltd. System for preventing unauthorized use of a personal computer and a method therefore security function, and methods of installing and detaching a security device to/from a computer
US6304895B1 (en) * 1997-08-22 2001-10-16 Apex Inc. Method and system for intelligently controlling a remotely located computer
US6324644B1 (en) * 1997-03-20 2001-11-27 Phoenix Technologies Ltd. Network enhanced bios enabling remote management of a computer without a functioning operating system
US20020083277A1 (en) * 2000-12-27 2002-06-27 Ramacharan Sundararaman Mechanisms to improve bus-request scheduling
US6463530B1 (en) * 1999-06-10 2002-10-08 International Business Machines Corporation Method and apparatus for remotely booting a client computer from a network by emulating remote boot chips
US20020184360A1 (en) * 1999-07-09 2002-12-05 Lsi Logic Corporation Methods and apparatus for managing devices without network attachments
US20020187830A1 (en) * 1999-10-06 2002-12-12 International Gaming Technology Standard peripheral communication
US20030054880A1 (en) * 1999-10-06 2003-03-20 Igt USB device protocol for a gaming machine
US20040088531A1 (en) * 2002-10-30 2004-05-06 Rothman Michael A. Methods and apparatus for configuring hardware resources in a pre-boot environment without requiring a system reset
US20040103175A1 (en) * 2002-11-22 2004-05-27 Rothman Michael A. Methods and apparatus for enabling of a remote management agent independent of an operating system
US20040219955A1 (en) * 2003-04-30 2004-11-04 Sony Corporation Apparatus, system and method for use in powering on a remote wireless device
US6938155B2 (en) * 2001-05-24 2005-08-30 International Business Machines Corporation System and method for multiple virtual private network authentication schemes
US20060059250A1 (en) * 2001-02-27 2006-03-16 Jamie Robb Remote management of computers
US7024548B1 (en) * 2003-03-10 2006-04-04 Cisco Technology, Inc. Methods and apparatus for auditing and tracking changes to an existing configuration of a computerized device
US20060205354A1 (en) * 2005-03-11 2006-09-14 Pirzada Fahd B Systems and methods for managing out-of-band device connection

Patent Citations (18)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5181201A (en) * 1990-02-07 1993-01-19 General Dynamics Land Systems Inc. Interface chip device
US5435271A (en) * 1993-08-19 1995-07-25 Invisible Fence Company, Inc. Multi-channel animal control device with external data communication
US5706349A (en) * 1995-03-06 1998-01-06 International Business Machines Corporation Authenticating remote users in a distributed environment
US5828831A (en) * 1995-08-10 1998-10-27 Samsung Electronics Co., Ltd. System for preventing unauthorized use of a personal computer and a method therefore security function, and methods of installing and detaching a security device to/from a computer
US6324644B1 (en) * 1997-03-20 2001-11-27 Phoenix Technologies Ltd. Network enhanced bios enabling remote management of a computer without a functioning operating system
US6304895B1 (en) * 1997-08-22 2001-10-16 Apex Inc. Method and system for intelligently controlling a remotely located computer
US6463530B1 (en) * 1999-06-10 2002-10-08 International Business Machines Corporation Method and apparatus for remotely booting a client computer from a network by emulating remote boot chips
US20020184360A1 (en) * 1999-07-09 2002-12-05 Lsi Logic Corporation Methods and apparatus for managing devices without network attachments
US20020187830A1 (en) * 1999-10-06 2002-12-12 International Gaming Technology Standard peripheral communication
US20030054880A1 (en) * 1999-10-06 2003-03-20 Igt USB device protocol for a gaming machine
US20020083277A1 (en) * 2000-12-27 2002-06-27 Ramacharan Sundararaman Mechanisms to improve bus-request scheduling
US20060059250A1 (en) * 2001-02-27 2006-03-16 Jamie Robb Remote management of computers
US6938155B2 (en) * 2001-05-24 2005-08-30 International Business Machines Corporation System and method for multiple virtual private network authentication schemes
US20040088531A1 (en) * 2002-10-30 2004-05-06 Rothman Michael A. Methods and apparatus for configuring hardware resources in a pre-boot environment without requiring a system reset
US20040103175A1 (en) * 2002-11-22 2004-05-27 Rothman Michael A. Methods and apparatus for enabling of a remote management agent independent of an operating system
US7024548B1 (en) * 2003-03-10 2006-04-04 Cisco Technology, Inc. Methods and apparatus for auditing and tracking changes to an existing configuration of a computerized device
US20040219955A1 (en) * 2003-04-30 2004-11-04 Sony Corporation Apparatus, system and method for use in powering on a remote wireless device
US20060205354A1 (en) * 2005-03-11 2006-09-14 Pirzada Fahd B Systems and methods for managing out-of-band device connection

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20140354963A1 (en) * 2012-07-12 2014-12-04 Cj Cgv Co., Ltd. Multi-projection system

Also Published As

Publication number Publication date
US7451301B2 (en) 2008-11-11
US20060230280A1 (en) 2006-10-12

Similar Documents

Publication Publication Date Title
US20090031010A1 (en) OS Independent Device Management Methods and Apparatuses
US8402262B2 (en) Enabling a heterogeneous blade environment
US7590873B2 (en) Power control method and system wherein a management server does not transmit a second power control request to an identified blade server when a management information indicates that a failure is detected in the identified blade server
US9998464B2 (en) Storage device security system
US7383575B2 (en) System and method for automatic password reset
JP4926636B2 (en) Information processing system and terminal
US7540024B2 (en) Security features for portable computing environment
KR100354279B1 (en) Data processing system and method for remote recovery of a primary password
US6526507B1 (en) Data processing system and method for waking a client only in response to receipt of an authenticated Wake-on-LAN packet
US20090319806A1 (en) Extensible pre-boot authentication
US8615666B2 (en) Preventing unauthorized access to information on an information processing apparatus
JP4932413B2 (en) Environment migration system, terminal device, information processing device, management server, portable storage medium
US9137244B2 (en) System and method for generating one-time password for information handling resource
US9147076B2 (en) System and method for establishing perpetual trust among platform domains
US20100162373A1 (en) Management of hardware passwords
US7940934B2 (en) System and method for securing computing management functions
JP2007140956A (en) Information processing system, management server, terminal and information processor
US10841318B2 (en) Systems and methods for providing multi-user level authorization enabled BIOS access control
US20060218631A1 (en) Single logon method on a server system
KR102175317B1 (en) Virtual Desktop Infrastructure
US7600134B2 (en) Theft deterrence using trusted platform module authorization
US20060230283A1 (en) Changing passwords with failback
US11740806B2 (en) Management controller based drive migration
US8453232B1 (en) Virtual smart card through a PC/SC interface
JP2007299427A (en) Power control method, and system for achieving the same

Legal Events

Date Code Title Description
STCB Information on status: application discontinuation

Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION