US20150248286A1 - System and methods for remote maintenance in an electronic network with multiple clients - Google Patents

System and methods for remote maintenance in an electronic network with multiple clients Download PDF

Info

Publication number
US20150248286A1
US20150248286A1 US14/713,470 US201514713470A US2015248286A1 US 20150248286 A1 US20150248286 A1 US 20150248286A1 US 201514713470 A US201514713470 A US 201514713470A US 2015248286 A1 US2015248286 A1 US 2015248286A1
Authority
US
United States
Prior art keywords
client
software update
system
requested
further
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
US14/713,470
Inventor
Seigo Kotani
Masato Suzuki
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.)
Fujitsu Ltd
Original Assignee
Fujitsu Ltd
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
Priority to US31649810P priority Critical
Priority to US12/879,226 priority patent/US9059978B2/en
Application filed by Fujitsu Ltd filed Critical Fujitsu Ltd
Priority to US14/713,470 priority patent/US20150248286A1/en
Assigned to FUJITSU LIMITED reassignment FUJITSU LIMITED ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: KOTANI, SEIGO, SUZUKI, MASATO
Publication of US20150248286A1 publication Critical patent/US20150248286A1/en
Assigned to FUJITSU LIMITED reassignment FUJITSU LIMITED ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: KOTANI, SEIGO, SUZUKI, MASATO
Application status is Abandoned legal-status Critical

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00Arrangements for program control, e.g. control units
    • G06F9/06Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44Arrangements for executing specific programs
    • G06F9/455Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • G06F9/45533Hypervisors; Virtual machine monitors
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/90Details of database functions independent of the retrieved data types
    • G06F16/95Retrieval from the web
    • G06F16/951Indexing; Web crawling techniques
    • G06F17/30864
    • GPHYSICS
    • G06COMPUTING; CALCULATING; 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
    • G06F21/32User authentication using biometric data, e.g. fingerprints, iris scans or voiceprints
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/50Monitoring users, programs or devices to maintain the integrity of platforms, e.g. of processors, firmware or operating systems
    • G06F21/57Certifying or maintaining trusted computer platforms, e.g. secure boots or power-downs, version controls, system software checks, secure updates or assessing vulnerabilities
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/60Protecting data
    • G06F21/64Protecting data integrity, e.g. using checksums, certificates or signatures
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00Arrangements for software engineering
    • G06F8/60Software deployment
    • G06F8/61Installation
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00Arrangements for software engineering
    • G06F8/60Software deployment
    • G06F8/65Updates
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00Arrangements for program control, e.g. control units
    • G06F9/06Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44Arrangements for executing specific programs
    • G06F9/455Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • G06F9/45533Hypervisors; Virtual machine monitors
    • G06F9/45558Hypervisor-specific management and integration aspects
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00Network architectures or network communication protocols for network security
    • H04L63/06Network architectures or network communication protocols for network security for supporting key management in a packet data network
    • H04L63/068Network architectures or network communication protocols for network security for supporting key management in a packet data network using time-dependent keys, e.g. periodically changing keys
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00Network architectures or network communication protocols for network security
    • H04L63/12Applying verification of the received information
    • H04L63/123Applying verification of the received information received data contents, e.g. message integrity
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network-specific arrangements or communication protocols supporting networked applications
    • H04L67/10Network-specific arrangements or communication protocols supporting networked applications in which an application is distributed across nodes in the network
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network-specific arrangements or communication protocols supporting networked applications
    • H04L67/42Protocols for client-server architectures
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00Cryptographic mechanisms or cryptographic arrangements for secret or secure communication
    • H04L9/08Key distribution or management, e.g. generation, sharing or updating, of cryptographic keys or passwords
    • H04L9/0894Escrow, recovery or storing of secret information, e.g. secret key escrow or cryptographic key storage
    • H04L9/0897Escrow, recovery or storing of secret information, e.g. secret key escrow or cryptographic key storage involving additional devices, e.g. trusted platform module [TPM], smartcard or USB
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00Cryptographic mechanisms or cryptographic arrangements for secret or secure communication
    • H04L9/32Cryptographic mechanisms or cryptographic arrangements for secret or secure communication including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials
    • H04L9/3226Cryptographic mechanisms or cryptographic arrangements for secret or secure communication including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials using a predetermined code, e.g. password, passphrase or PIN
    • H04L9/3231Biological data, e.g. fingerprint, voice or retina
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00Cryptographic mechanisms or cryptographic arrangements for secret or secure communication
    • H04L9/32Cryptographic mechanisms or cryptographic arrangements for secret or secure communication including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials
    • H04L9/3234Cryptographic mechanisms or cryptographic arrangements for secret or secure communication including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials involving additional secure or trusted devices, e.g. TPM, smartcard, USB or software token
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00Cryptographic mechanisms or cryptographic arrangements for secret or secure communication
    • H04L9/32Cryptographic mechanisms or cryptographic arrangements for secret or secure communication including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials
    • H04L9/3297Cryptographic mechanisms or cryptographic arrangements for secret or secure communication including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials involving time stamps, e.g. generation of time stamps
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W12/00Security arrangements, e.g. access security or fraud detection; Authentication, e.g. verifying user identity or authorisation; Protecting privacy or anonymity ; Protecting confidentiality; Key management; Integrity; Mobile application security; Using identity modules; Secure pairing of devices; Context aware security; Lawful interception
    • H04W12/10Integrity
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00Arrangements for program control, e.g. control units
    • G06F9/06Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44Arrangements for executing specific programs
    • G06F9/455Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • G06F9/45533Hypervisors; Virtual machine monitors
    • G06F9/45558Hypervisor-specific management and integration aspects
    • G06F2009/4557Distribution of virtual machine instances; Migration and load balancing
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F2221/00Indexing scheme relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F2221/21Indexing scheme relating to G06F21/00 and subgroups addressing additional information or applications relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F2221/2151Time stamp
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L2209/00Additional information or applications relating to cryptographic mechanisms or cryptographic arrangements for secret or secure communication H04L9/00
    • H04L2209/60Digital content management, e.g. content distribution
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L2209/00Additional information or applications relating to cryptographic mechanisms or cryptographic arrangements for secret or secure communication H04L9/00
    • H04L2209/80Wireless
    • H04L2209/805Lightweight hardware, e.g. radio-frequency identification [RFID] or sensor
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network-specific arrangements or communication protocols supporting networked applications
    • H04L67/34Network-specific arrangements or communication protocols supporting networked applications involving the movement of software or configuration parameters
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W12/00Security arrangements, e.g. access security or fraud detection; Authentication, e.g. verifying user identity or authorisation; Protecting privacy or anonymity ; Protecting confidentiality; Key management; Integrity; Mobile application security; Using identity modules; Secure pairing of devices; Context aware security; Lawful interception
    • H04W12/005Context aware security
    • H04W12/00502Time aware

Abstract

A system for performing remote maintenance in an electronic network configured to serve a plurality of clients may comprise a client, a database, and a virtual machine. The client may include a plurality of processing resources. Each one of the plurality of processing resources may have a respective set of processing instructions stored on an respective associated computer readable memory. The database may include information correlating a list of processing resources with a respective set of processing instructions. The virtual machine may be operable to access the database and perform calculations simulating proposed combinations of processing resources and their respective set of processing instructions before approving a software update requested for the client.

Description

    RELATED APPLICATIONS
  • This application is a Continuation of U.S. patent application Ser. No. 12/879,226 filed Sep. 10, 2010, which claims the benefit of U.S. Provisional Application No. 61/316,498 filed on Mar. 23, 2010, which are incorporated herein their entirety.
  • TECHNICAL FIELD OF THE INVENTION
  • The present invention relates generally to information exchange and, more particularly, to a method and system for remote maintenance of an information handling system with improved safety and security.
  • BACKGROUND
  • Distributed communication networks include a wide range of systems, from private intranets to the unsecured Internet. In any communication network, electronic content flows from one point in the network to another. Electronic content, in this context, may include electronic documents, executable files, data files, etc. In some communication networks, access to the electronic content may be restricted and/or limited to particular users and/or clients. Several methods exist to verify the identity of a user attempting to gain access to electronic content, such as username and password combinations, public/private key combinations, and/or biometrics. In some networks, a central server may employ such methods before distributing electronic content to a requesting user and/or client.
  • Software exchange between service providers and clients may be improved by certifying the content and security of the data exchanged. Some systems for certification are difficult to implement for a variety of reasons. For example, it may be difficult to protecting scanning and reporting agents within an operating system. As another example, the size of a client system may require too much time to complete a scan and/or transmit a report due to size. As another example, some systems may not be able to provide a secure connection between a biometric sensor and the reporting agent. Improved certification methods and systems may improve security, speed, and/or efficiency of software exchange between service providers and clients.
  • SUMMARY OF THE DISCLOSURE
  • The present disclosure provides a method and system for distributing electronic content that substantially eliminates or reduces at least some of the disadvantages and problems associated with previous methods and systems.
  • According to one embodiment, a system for performing remote maintenance in an electronic network configured to serve a plurality of clients may comprise a client, a database, and a virtual machine. The client may include a plurality of processing resources. Each one of the plurality of processing resources may have a respective set of processing instructions stored on an respective associated computer readable memory. The database may include information correlating a list of processing resources with a respective set of processing instructions. The virtual machine may be operable to access the database and perform calculations simulating proposed combinations of processing resources and their respective set of processing instructions before approving a software update requested for the client.
  • According to another embodiment, a method for performing remote maintenance in a client system served by an electronic network may comprise maintaining a database, receiving a request for a software update, accessing the database, and performing calculations. The database may include information correlating a list of client system nodes with a respective set of processing instructions. The request may include an identifier corresponding to a specific client system and a specific set of processing instructions. Accessing the database may include retrieving the information related to the nodes associated with the client systems and the respective set of processing instructions correlated to the associated processors. The calculations may simulate a combination of nodes and respective processing instructions that would result from the installation of the requested software update.
  • The methods and systems disclosed herein may include techniques using virtual machines (VM) discussed below. Technical advantages of certain embodiments of the present disclosure include increased security and/or reliability in remote maintenance including wireless transfer of electronic content from an external data center serving a plurality of client systems. Other technical advantages will be readily apparent to one skilled in the art from the following figures, descriptions, and claims. Moreover, while specific advantages have been enumerated above, various embodiments may include all, some or none of the enumerated advantages.
  • BRIEF DESCRIPTION OF THE DRAWINGS
  • For a more complete understanding of the present invention and its advantages, reference is now made to the following description, taken in conjunction with the accompanying drawings, in which:
  • FIG. 1 shows an example communication network, including a client system and an external data center, in accordance with teachings of the present disclosure;
  • FIG. 2 shows an example communication network, including an example client system and external data center, in accordance with teachings of the present disclosure;
  • FIG. 3 shows an example communication network, including details of a client system, in accordance with teachings of the present disclosure; and
  • FIGS. 4-11 show flowcharts depicting various methods for remote maintenance of an information handling system with improved safety and security.
  • DETAILED DESCRIPTION OF THE INVENTION
  • Preferred embodiments and their advantages are best understood by reference to FIGS. 1 through 11, wherein like numbers are used to indicate like and corresponding parts. FIG. 1 shows a simplified representation of an example electronic network 1, in accordance with the teachings of the present disclosure. Electronic network 1 may include a data center 10 and a client system 20. Some embodiments of electronic network 1 may include numerous clients and their respective client systems. In FIGS. 1-3, a single client and its client system 20 is shown and discussed for the sake of clarity.
  • Data center 10 may be configured to provide maintenance to various clients and/or client systems 20. Such maintenance may include managing software and/or firmware updates and/or status. In complicated electronic networks with many client systems 20, managing the delivery of electronic content to various client systems 20 may be even more difficult if reports must be certified and/or verified.
  • For purposes of this disclosure, “electronic content,” “content,” “software,” and/or “software updates” may include any file, files, object code, executable code, data records, or any other electronically recorded data structure that a client of a electronic network may wish to access. Illustrative examples may include text files, spreadsheets, email, medical records, images, and other electronic data, as well as web pages, private networks, word processing programs, file management systems, and other programs. Additionally, a “client” may refer to a person acting as an end user or to the device or devices used by such a person to access the communication network, such as a personal computer, kiosk, or mobile computing device.
  • Trusted Computing and TrustCube may provide certifiable reporting related to client systems 20 to a service provider (e.g., data center 10). Certifiable reporting may create difficulty in protecting scanning and/or reporting agents associated with the client systems 20. In addition, the time required to complete a scan and send a large associated report may be too large. As another example, it may be difficult to implement a biometric sensor to the client system 20 and its reporting agent.
  • In some embodiments of the present invention, the combination of virtual machine (VM) technology and trusted computing techniques may provide advantages over other methods. For example, using a first VM with a minimal operating system (OS) for the limited purpose of generating reports may provide protection for the rest of the client system 20 against external access. As another example, because the first VM uses a smaller number of files and the files are smaller, the size of the reports sent to the data center 10 may be reduced. The advantages can be increased by using virtual hard disk images and virtual memory images instead of individual files in hard disk partitions. As another example, a limited purpose OS may repeatedly use the same files and/or memory images and changes to those files and images may be discarded and/or deleted.
  • In some embodiments, VM technology may be combined with file storage techniques (e.g., mbox). For example, files may be stored in plain text format in a single file. Such techniques may allow text processing tools to be readily used on the contents.
  • A virtual machine manager (VMM) may create, run, monitor, and/or terminate various VMs. The VMM may function to intercept interrupts and/or faults between VMs and/or to control the access that an application has to a hardware device and/or installed software. A VMM may also manage multi-tasking for a processor by sharing time between various threads in which applications and/or VMs run. Use of a VMM may expand the functionality of the VMs described above.
  • As another example, biometric sensors may be incorporated using separate VM and connected to the first VM through a VMM. The data center 10 may use certifiable reporting techniques in combination with biometric data to evaluate the trustworthiness of the state of the client system 20 and/or the biometric data.
  • Data center 10 may include processor 12, storage resources 14, and a communication bus 16. Processor 12 may comprise any system, device, or apparatus operable to interpret and/or execute program instructions and/or process data, and may include, without limitation, a microprocessor, microcontroller, digital signal processor (DSP), application specific integrated circuit (ASIC), or any other digital or analog circuitry configured to interpret and/or execute program instructions and/or process data. In some embodiments, processor 104 may interpret and/or execute program instructions and/or process data stored in storage resources 14, and/or another component of data center 10.
  • Data center 10 may represent a trusted, dedicated server that manages security policies and authenticates attributes. Data center 10 may contain a database containing a number of policies defining a set of attribute values that must be met before a client system 20 is granted permission to access electronic content and/or software. Data center 10 may receive an attribute report from client system 20 identifying one or more attributes associated with client system 20. After authenticating the attributes, data center 10 may determine whether to provide the requested service to client system 20. Application of such attribute report and authentication may also be referred to as “policy-based management.” The context data may include data representative of client system 20 such as physical location (e.g., IP address), certain software installed on the requesting machine (e.g., rigorous antivirus software), biometric identifiers, or any other appropriate context attributes of client system 20.
  • Storage resources 14 may be communicatively coupled to processor 12 and may comprise any system, device, or apparatus operable to retain program instructions or data for a period of time (e.g., computer-readable media). Storage resources 14 may comprise random access memory (RAM), electrically erasable programmable read-only memory (EEPROM), a PCMCIA card, flash memory, magnetic storage, opto-magnetic storage, or any suitable selection and/or array of volatile or non-volatile memory that retains data after power to storage resources 12 is turned off.
  • Storage resources 14 may include any combination of hardware and software, including controlling logic. For example, storage resources 14 may include a centralized repository of documents, such as medical records. As another example, storage resources 14 may represent an application service provider which provides access to particular applications, software or other media over a network. Such applications, software, or media may include, among other things, document readers, web browsers, or document editing software. As another example, storage resources 14 may be associated with an online networking website or an Email provider.
  • For clarity of description, FIG. 1 depicts processor 12 and storage resources 14 as separate components. In some embodiments, processor 12 and storage unit 14 may include stand-alone software programs stored on computer-readable media and executable by one or more processors associated with one or more computers and/or servers. However, processor 12 and storage unit 14 may also include components or subroutines of a larger software program, hard-coded into computer-readable media, and/or any hardware or software modules configured to perform the desired functions.
  • Communication bus 16 may be any suitable system, apparatus, or device operable to serve as an interface between data center 10 and network 18. Communication bus 16 may enable data center 10 to communicate over network 18 using any suitable transmission protocol and/or standard, including without limitation all transmission protocols and/or standards enumerated below with respect to the discussion of network 18. In some embodiments, network 18 may be a closed network (e.g., network 18 is only accessible by authorized clients).
  • As illustrated, network 18 may include any network capable of transmitting audio and/or video telecommunication signals, data, and/or messages. Some examples may include all, or a portion of, a radio access network, a public switched telephone network (PSTN), a public or private data network, a local area network (LAN), a metropolitan area network (MAN), a wide area network (WAN), a local, regional, or global communication or computer network such as the Internet, a wireline or wireless network, an enterprise intranet, or any combination of the preceding.
  • In operation, network 18 may provide connectivity between components coupled to network 18 using any appropriate communication protocol. To facilitate the described communication capabilities, network 18 may include routers, hubs, switches, gateways, call controllers, and/or any other suitable components in any suitable form or arrangement. Additionally, network 18 may include any hardware and/or software configured to communicate information in the form of packets, cells, frames, segments or other portions of data. Although network 18 is illustrated as a single network, communication network 18 may comprise any number or configuration of networks. Moreover, certain embodiments of communication network 1 may include any number or configuration of network 18.
  • In some embodiments, network 18 may include a virtual private network (VPN). A VPN provides increased security over an open and/or public network. In general, a VPN segregates and/or encapsulates data transfers so that the data may be kept private and/or secure from other devices sharing a intervening network (e.g., a LAN or a WAN). In operation a VPN may allow a plurality of clients 20 to interact with data center 10 as if connected directly and/or privately.
  • Client 20 may include any system and/or component of electronic network 1 maintained, at least in part, by data center 10. Client 20 may include multiple processors, related software and/or firmware, sensors, etc. For example, client 20 may include an automobile and its internal network. As another example, client 20 may include a portable phone with processors and software identity modules (SIM) cards. In the context of this disclosure, client 20 may be described with respect to specific embodiments, by the teachings are not so limited. In some embodiments, the various processors and storage resources associated with client 20 may be provided by multiple vendors and/or service providers. In those embodiments, maintenance of the various processors and their associated software and/or firmware may be complicated by the need to coordinate data across the multiple vendors and/or service providers. Rather than allow unfettered access to the entire client system 20, the teachings of this disclosure may allow for virtual partitions segregating the various resources from one another.
  • Client 20 may include a computer and/or a computing device including functionality for wireless communication with data center 10. For example, client 20 may include a desktop computer, a laptop computer, a personal digital assistant (PDA), a smart phone, a cellular or mobile phone, an in- or out-of-car navigation system, and/or a mobile gaming device. Client 20 may operate one or more client applications (e.g., a web browser, a text editor, etc.).
  • FIG. 1 shows an example client system 20 including a processing module 21, multiple VMs 22, a VMM 24, a trusted platform module (TPM) 26, a resource list 28, an client network system 30, a node 32, and a GPS interface 40. Some embodiments may provide increased security of a VM 22 by creating multiple VMs 22 and controlling the information flow between them using a VMM 24.
  • Client system 20 may be significantly more complex than the simplified client network system 30 shown in FIG. 1. For example, an automobile may include a client network system 30 (e.g., FlexRay) including multiple processors, in some examples several hundred processors. In FIG. 1, node 32 represents a single processor and/or another resource associated with client network system 30.
  • VM 22 may include a virtual machine corresponding to client network system 30 and/or to a single process associated with client network system 30. Multiple VMs 22 may run multiple operating systems (OS). In such an arrangement, each VM 22 may use a single-purpose OS and time-share any needed processing resources of client system 20 and/or processing module 21 through VMM 24.
  • Trusted platform module 26 may include resources configured to generate cryptographic keys (e.g., a hardware pseudo-random number generator). In some embodiments, TPM 26 may include remote attestation and/or sealed storage. In some embodiments, TPM 26 includes at least one dedicated processor with a unique and secret RSA key assigned to and burned into the processor chip during manufacturing. Use of a unique RSA key in TPM 26 may allow data center 10 to verify that client system 20 is actually a client.
  • For example, TPM 26 may employ a hash key including a summary of the hardware and software configuration of client system 20. A hash key may allow client system 20 to test any incoming software packages and/or updates to verify they have not been changed. One example verification method includes binding, encryption based on a TPM endorsement key unique to a processor during its manufacture and/or another trusted key related to that endorsement key. Another example verification method includes sealing, which may impose an additional state requirement on the condition of the TPM 26.
  • Resource list 28 may include a list and/or register of entities. In some embodiments, resource list 28 may include a whitelist of entities approved for access and/or recognition. A whitelist may include any data center 10 entities that TPM 26 may approve for access to client system 20. In some embodiments, resource list 28 may include a blacklist of entities for which access will be denied.
  • Client network 30 may include a network system within a particular client, including multiple processors and/or storage resources. For example, client network 30 may include a FlexRay network system associated with an automobile. FlexRay is a particular embodiment of a network communications protocol developed for managing the numerous processors in an automobile system. As another example, a controller-area network (CAN or CAN-bus) is a particular embodiments of a communications protocol standard designed to allow microcontrollers and devices to communicate with each other without a host computer. Additional examples include time triggered protocol (TTP) and avionics full-duplex switched ethernet (AFDX).
  • Node 32 in client system 20 may include any particular resources of client system 20. For example, node 32 may include processors and/or their associated software, firmware, and/or processing instructions related to the processors. For example, an automobile may have a very complex network system comprising multiple CPUs. Each CPU may have software and/or firmware for its operation supplied by the vendor. Client network 30 may be responsible for the operation and/or maintenance of each node 32, including managing the version and/or update status of the software and/or firmware associated with each node 32 in client system 20.
  • Global positioning system interface 40 may include any interface with the Global Positioning System (GPS). GPS includes a space-based global navigation satellite system providing reliable location and time information. GPS is accessible by anyone and/or any system with a GPS receiver. The use of particular and accurate location and/or timing information may allow client processing module 21 to manage information requests, downloads, and/or other content.
  • FIG. 2 shows an example communication network 2, including an example client system 20 and external data centers 10 a and 10 b, in accordance with teachings of the present disclosure. Data centers 10 may include any external data base accessible by client system 20. For the purposes of illustration only, one example client system 20 is described in relation to FIG. 2, where client system 20 comprises a mobile navigation system. The teachings of the present disclosure may be used with any appropriate client system 20.
  • Communication network 2 may include internet 42, external data centers 10, and client mobile navigation system 20. Client system 20 may communicate with internet 42 through a private infrastructure 44 (e.g., a home-based internet connection in a user's home). Data centers 10 a and 10 b may communicate with client system 20 through network 18. Network 18 may provide secure communications as described in this disclosure.
  • Data center 10 a may include a database of electronic content useful in client system 20. For example, if client system 20 includes a mobile navigation system, data center 10 a may include maps, updated interfaces for the user, and other content related to a mobile navigation system. Data center 10 a may also communicate with internet 42 via an ISP.
  • Data center 10 b may include a database housing firmware, maintenance, and software related to the operation of mobile navigation system 20. For example, data center 10 b may provide a list of the most current versions of firmware for each processor in mobile navigation system 20.
  • Client system 20 may operate several VMs 22 in module 21 to interface with each separate data source. For example, VM 22 a may include a universal browser and/or a web OS for interaction with internet 42. As another example, VM 22 b and 22 c may include a private application and a virtual OS for interaction with data centers 10 a and 10 b, respectively. As another example, VM 22 d may include a private application and a virtual OS for interaction with various systems in the user's automobile 32.
  • Each VM 22 may only communicate to another VM 22 through VMM 24. VMM 24 may manage these communications in concert with TPM to increase the security of each VM 22. For example, content received from the internet 42 may not be installed to node 32 unless approved by VMM 24 by any of the various methods described herein.
  • FIG. 3 shows details of example communication network 2, including details of client system 20, in accordance with teachings of the present disclosure. FIG. 3 shows that VMM 24 be responsible for environment management of each VM 22. Each VM 22 may include an associated application 44 operated by an OS 46.
  • VMM 24 may provide storage resources 48 to various VMs 22 as appropriate. VMM 24 may operate one or more programs 50 in association with each VM 22. VMM 24 may also cooperate with TPM 26 and/or resource list 28 to provide encryption, validation keys, white lists, and/or black lists.
  • FIG. 4 illustrates a flow chart of an example method 60 for performing remote maintenance in an electronic network configured to serve a plurality of client systems 20, in accordance with certain embodiments of the present disclosure. Method 60 may include multiple steps and may be performed by various components of electronic network 1, including data center 10 and/or other resources. Method 60 may start at 62. In some embodiments, client system 20 may include an automobile and/or an FlexRay system associated with an automobile.
  • Step 64 may include operating a data center 10 having a database of software associated with various processors and resources in a client system. For example, step 64 may include maintaining a list of processors associated with client system 20, as well as any current software and/or firmware provided for the use of the processors of client system 20.
  • Step 66 may include communicating with a first virtual machine 22 b hosted by processing module 21 of client system 20. First virtual machine 22 b may handle a first data set associated with the data center 10. First virtual machine 22 b may be managed by VMM 24 as discussed above. First virtual machine 22 b may be configured to monitor the list of processors and their associated software and/or firmware maintained by data center 10.
  • Step 68 may include receiving a request from first virtual machine 22 b identifying a software update for delivery to client system 20. For example, data center 10 may receive such a request from first virtual machine 22 b through network 18.
  • Step 70 may include performing an attestation process verifying the identity of client system 20. An attestation process may include any of the verification processes discussed above. In some embodiments, an attestation process may include receiving, testing, and/or verifying one or more biometric indicators. In some embodiments, data center 10 may perform the attestation process to verity the identity of client system 20.
  • Step 72 may include sending the identified software update to first virtual machine 22 b using a network 18. Network 18 may be a closed network as discussed above. In some embodiments, data center 10 may perform step 72. In some embodiments, the identified software update may be sent wirelessly.
  • Step 74 may include authorizing first virtual machine 22 b to install the identified software update on client system 20 using second virtual machine 22 c associated with the client system. In some embodiments, data center 10 may perform step 74. In other embodiments, VMM 26 may perform step 74. Method 60 may end at 76.
  • Method 60 may be useful on client systems 20 where first virtual machine 22 b and second virtual machine 22 c communicate through VMM 24. Use of VMM 24 may protect client system 20 from direct access by data center 10 and/or otherwise increase security of the components of client system 20. In some embodiments of method 60 first virtual machine 22 b may interrogate second virtual machine 22 c to verify client system 20 has successfully installed the software update.
  • In client systems 20 with a large number of nodes 32, traditional methods of maintenance would require client system 20 to be serviced at a secure maintenance location. Remote maintenance by radio transmission and/or another over-the-air system may decrease security under those traditional methods.
  • In contrast, electronic networks 1 employing method 60 may allow the use of remote maintenance without decreasing security. Particular embodiments of electronic network 1 may increase the security of any particular VM 22 by managing the VMs 22 with VMM 24, where data exchange between the various VMs 22 may be operated and/or controlled by VMM 24.
  • FIG. 5 illustrates a flow chart of an example method 80 for a client system 20 to request and receive software updates from a remote server, in accordance with certain embodiments of the present disclosure. Method 80 may include multiple steps and may be performed by various components of electronic network 1, including processor module 21 of client system 20 and/or other resources. In some embodiments, client system 20 may include an automobile and/or an FlexRay system associated with an automobile. Method 80 may start at 82.
  • Step 84 may include hosting two VMs 22 associated with client system 20. First VM 22 b may handle a first data set associated with the client system 20. Second VM 22 c may handle a second data set associated with an external data center 10.
  • Step 86 may include operating a VMM 24 configured to manage communication between the two virtual machines 22. Use of VMM 24 may protect client system 20 from direct access by data center 10 and/or otherwise increase security of the components of client system 20.
  • Step 88 may include recognizing the first data set is out of date in comparison with the second data set. Step 88 may be performed by a VM 22. For example, second VM 22 b may interrogate first VM 22 c to check the status, version, and/or configuration of any processors and/or their respective software and/or firmware. For example, second VM 22 b may compare the status, version, and/or configuration of a particular processor and/or its respective software and/or firmware against the updated data in data center 10.
  • Step 90 may include identifying a software update for delivery to client system 20. Step 90 may be performed by a VM 22, data center 10, and/or other components of electronic network 1. In some embodiments, VM 22 may transmit data related to client system 20 to data center 10 via a secure mechanism (e.g., via TPM/TNC).
  • Step 92 may include performing an attestation process verifying the identity of the data center 10. An attestation process may include any of the verification processes discussed above. In some embodiments, an attestation process may include receiving, testing, and/or verifying one or more biometric indicators. In some embodiments, client system 20 may perform the attestation process to verify the identity of data center 10 using second VM 22 b, TPM 24, and/or resource list 28.
  • Step 94 may include requesting the identified software update from the external data center 10. In some embodiments, second VM 22 b may perform step 94. The identified software update may include various software and/or firmware related to one or more nodes 32 of client system 20 (e.g., a CPU).
  • Step 96 may include receiving the identified software update from the external data center 10 to the client system 20. In some embodiments, second VM 22 b will perform step 96. The identified software update may be transmitted over network 18. In some embodiments, VMM 24 may check the received software update for integrity before performing step 98.
  • Step 98 may include installing the sent software update on client system 20 through first virtual machine 22 b. In some embodiments of method 80 second virtual machine 22 b may interrogate first virtual machine 22 c to verify client system 20 has successfully installed the software update. In some embodiments, client system 20 may create and/or maintain a log for the receipt and/or installation of the software updates. In some embodiments, data center 10 may create and/or maintain a log for the sending and/or installation of the software update. The log may include a time stamp.
  • Method 80 may end at 99.
  • In client systems 20 with a large number of nodes 32, traditional methods of maintenance would require client system 20 to be serviced at a secure maintenance location. Remote maintenance by radio transmission and/or another over-the-air system may decrease security under those traditional methods.
  • In contrast, electronic networks 1 employing method 80 may allow the use of remote maintenance without decreasing security. Particular embodiments of electronic network 1 may increase the security of any particular VM 22 by managing the VMs 22 with VMM 24, where data exchange between the various VMs 22 may be operated and/or controlled by VMM 24.
  • FIG. 6 illustrates a flow chart of an example method 100 for performing remote maintenance in a client system served by an electronic network, in accordance with certain embodiments of the present disclosure. Method 100 may include multiple steps and may be performed by various components of electronic network 1, including data center 10 and/or other resources. In some embodiments, client system 20 may include an automobile and/or an FlexRay system associated with an automobile. Method 100 may start at 102.
  • Step 104 may include maintaining a database including information correlating a list of client system nodes 32 with a respective set of processing instructions. Data center 10 may perform step 104 alone or in conjunction with other resources. For example, an individual may be responsible for updating the database as new information becomes available. As another example, various vendors and/or suppliers associated with client system nodes 32 may deliver updated software and/or firmware packages to data center 10 electronically.
  • Step 106 may include receiving a request for a software update, the request including an identifier corresponding to a specific client system 20 and a specific set of processing instructions. Data center 10 may perform step 106. Data center may receive the request over network 18.
  • Step 108 may include accessing the database to retrieve the information related to the client system nodes 32 and the respective set of processing instructions correlated to the associated nodes 32. Data center 10 may perform step 108 based on the received request.
  • Step 110 may include performing calculations simulating a combination of nodes 32 and respective processing instructions that would result from the installation of the requested software update. Data center 10 may perform step 110.
  • Method 100 may end at 112.
  • In some embodiments, client systems 20 may include a complex network system comprising multiple nodes 32 (e.g., CPUs and/or processing resources). Each node 32 may include associated software and/or firmware supplied by the vendor. As any particular node 32 receives updated software and/or firmware from its respective vendor, a new combination of software and/or firmware exists for client system 20. The number of possible combinations may be very large. An inoperative and/or inappropriate combination of software and/or firmware may affect the operation of client system 20. In some embodiments, data center 10 may maintain a database of nodes 32 and their respective software.
  • Method 100 may allow data center 10 and/or additional components of electronic network 1 to simulate a proposed combination of nodes 32 and/or their associated software and/or firmware before delivering any electronic content to client system 20. Testing a proposed combination for operational integrity, compatibility, and/or any other appropriate standard may increase the reliability and/or stability of client system 20.
  • FIG. 7 illustrates a flow chart of an example method 120 for performing remote maintenance on client system 20 served by an electronic network 1 serving a plurality of clients 20, in accordance with certain embodiments of the present disclosure. Method 120 may include multiple steps and may be performed by various components of electronic network 1, including client system 20 and/or other resources. In some embodiments, client system 20 may include an automobile and/or an FlexRay system associated with an automobile. Method 120 may start at 122.
  • Step 124 may include receiving a list of updated software modules available for delivery to the plurality of client systems 20. The updated software modules may be hosted on plurality of servers. Step 124 may be performed by client system 20. For example, first VM 22 b may query data center 10 for the list and then receive the list.
  • Step 126 may include determining whether to request any of the updated software modules on the list based at least in part on the identity of a plurality of nodes 32 associated with client system 20. In some embodiments, first VM 22 b may consider the list of processors in client system 20 and compare that list versus the list of available modules. For example, if client system 20 is an automobile and/or a FlexRay system associated with an automobile, first VM 22 b may determine whether to request an update based on the make, model, and/or year of the automobile.
  • Step 128 may include requesting an updated software module. In some embodiments, step 128 may be an over-the-air and/or a remote communication. Client system 20 may perform step 128. For example, first VM 22 b may request the updated software module from data center 10.
  • Step 130 may include receiving the requested updated software module. In some embodiments, the updated software modules may be hosted on a plurality of servers. In such embodiments, client system 20 may receive the requested module from the particular server hosting the requested module. In such embodiments, the list of updated software modules may include a uniform resource locator identifying the location of each module.
  • Step 132 may include installing the received updated software module on the client system. The updated software module may be delivered over-the-air and/or by another remote communication system. Method 120 may end at 134.
  • FIG. 8 illustrates a flow chart of an example method 140 for performing remote maintenance in an electronic network 1 configured to serve a plurality of client systems 20 in accordance with certain embodiments of the present disclosure.
  • Method 140 may include multiple steps and may be performed by various components of electronic network 1, including data center 10 and/or other resources. In some embodiments, client system 20 may include a mobile phone. Method 140 may start at 142.
  • Step 144 may include operating data center 10 having a database of software associated with various nodes 32 in a client system. In embodiments where client system 20 includes a mobile phone, nodes 32 may include various software identifier modules (SIMs). Data center 10 may perform step 144.
  • Step 146 may include communicating with first virtual machine 22 b hosted by client system 20. First virtual machine 22 b may handle a first data set associated with data center 10. For example, first virtual machine 22 b may be configured to access a list of various configurations, revision numbers, etc. related to the various nodes 32 of client system 20. Data center 10 may perform step 146 using network 18. Data center 10 may compare the data set associated with first VM 22 b to a list of current versions and/or update status and flag any variations in identity.
  • Step 148 may include receiving a request first virtual machine 22 b identifying a software update for delivery to one of the various nodes 32 in client system 20. For example, first VM 22 b may request a software update for a particular SIM in a mobile phone. Data center 10 may perform step 148.
  • Step 150 may include performing an attestation process verifying the identity of client system 20. Data center 10 may perform step 150. An attestation process may include any of the verification processes discussed above. In some embodiments, an attestation process may include receiving, testing, and/or verifying one or more biometric indicators. In some embodiments, client system 20 may perform the attestation process to verify the identity of data center 10 using second VM 22 b, TPM 24, and/or resource list 28.
  • Step 152 may include sending the identified software update to the first virtual machine using a network. In some embodiments, data center 10 may send the identified software over network 18. In some embodiments, step 152 may be performed by sending the identified software update wireless and/or over-the-air.
  • Step 154 may include authorizing first VM 22 b to install the received software update on client system 20 using a second VM 22 c associated with the one of the various nodes 32. First VM 22 b and second VM 22 c may communicate through VMM 24. In some embodiments, client system 20 may perform an attestation process verifying the integrity and/or safety of the received software before accepting it from data center 10. Method 140 may end at 156. Attestation may occur before and/or after the installation of the received software update.
  • In some embodiments, first 22 b may interrogate second VM 22 c to verify client system 20 has received the software update. In some client systems 20, each of multiple nodes 32 may operate with a unique operating system. For example, in a mobile phone with multiple SIM cards, each SIM card may operate on its own OS. Data exchange between multiple SIM cards and/or between various VMs 22 of client system 20 may be complicated because of the variation in OS. In some embodiments, a particular SIM card may have lower level security requirements in comparison with another SIM care and its OS. In such embodiments, traditional maintenance requires the client system 20 to be serviced in a secure maintenance location.
  • Use of method 140 and the teachings of the present disclosure may allow over-the-air and/or wireless maintenance of client system 20. In client systems with multiple VMs 22 linked through VMM 24, data exchange between data center 10 and client system 20 may be supported by TPM 26 and provide increased security and/or reliability.
  • FIG. 9 illustrates a flow chart of an example method 160 for client system 20 to request and receive software updates from a remote server 10, in accordance with certain embodiments of the present disclosure. Method 160 may include multiple steps and may be performed by various components of electronic network 1, including client system 20 and/or other resources. In some embodiments, client system 20 may include a mobile phone. Node 32 may comprise a subscriber identity module (SIM) card. Method 160 may start at 162.
  • Step 144 may include hosting two virtual machines 22 associated with the client system 20. First VM 22 b may handle a first data set associated with external data center 10. Second VM 22 c may handle a second data set associated with node 32 in client system 10. First VM 22 b and second VM 22 c may communicate through VMM 24 to maintain data integrity and/or reliability for the various VMs 22.
  • Step 146 may include operating VMM 24 configured to manage communication between the two VMs. Client system 20 may perform step 146 in combination with TPM 26.
  • Step 148 may include recognizing the first data set is out of identity with the second data set. Data center 10, VM 22 b or 22 c, and/or VMM 24 may perform step 148.
  • Step 150 may include identifying a software update for delivery to node 32, the software update configured to restore identity between the first data set and the second data set.
  • Step 152 may include performing an attestation process verifying the identity of the client system, verifying the identity of the data center 10, and/or the reliability and/or safety of the software update identified. Any portion of electronic network 1 may perform the attestation process. For example, VMM 24 may operate in conjunction with TPM 26 to validate the identity of the software package and/or data center 10.
  • Step 154 may include requesting the identified software update from external data center 10. First VM 22 b may perform step 154.
  • Step 156 may include receiving the identified software update from external data center 10 to first VM 22 b.
  • Step 158 may include installing the sent software update on node 32 through second VM 22 c. In some embodiments, first 22 b may interrogate second VM 22 c to verify node 32 has received the software update.
  • In some client systems 20, each of multiple nodes 32 may operate with a unique operating system. For example, in a mobile phone with multiple SIM cards, each SIM card may operate on its own OS. Data exchange between multiple SIM cards and/or between various VMs 22 of client system 20 may be complicated because of the variation in OS. In some embodiments, a particular SIM card may have lower level security requirements in comparison with another SIM care and its OS. In such embodiments, traditional maintenance requires the client system 20 to be serviced in a secure maintenance location.
  • Use of method 160 and the teachings of the present disclosure may allow over-the-air and/or wireless maintenance of client system 20. In client systems with multiple VMs 22 linked through VMM 24, data exchange between data center 10 and client system 20 may be supported by TPM 26 and provide increased security and/or reliability.
  • FIG. 10 illustrates a flow chart of an example method 182 for verifying electronic software code integrity, in accordance with certain embodiments of the present disclosure. Method 182 may include multiple steps and may be performed by various components of electronic network 1, including client system 20 and/or other resources. Method 182 may start at 184.
  • Step 186 may include providing a plurality of encryption keys to client system 20, each of the plurality of encryption keys correlated to a respective time factor. The time factor may depend at least in part on a control factor and a time stamp generated at the delivery of the software code packet, an update timing of the software code packet, or an update timing of a trusted protocol module associated with the client.
  • Step 188 may include encrypting a software code packet using one of the plurality of encryption keys based on a time factor related to the software code packet. Step 190 may include delivering the encrypted software code packet to client system 20.
  • Step 192 may include informing client 20 to choose a decryption key based on the time factor correlating to the time client 20 receives the software code packet. Method 182 may end at 194.
  • Traditional software code integrity may be checked using an electronic signature (e.g., a public key infrastructure (PKI) certification method). Use of an electronic signature, however, may be unreliable compared to the methods of this disclosure. For example, electronic signatures may incorporate an expiration date, after which the signature will fail. It may be possible to replace and/or change code before and/or after the electronic signature validation process is performed.
  • In accordance with the teachings of the present disclosure, code integrity may be substantially improved by including an update timing/key control. The encryption key may change based on a time factor. For example, the time factor may depend at least in part on a time stamp related to the sending and/or the delivery of electronic content. As another example, the time factor may depend at least in part on the update timing of TPM 26 and/or a VM 22. In any case, the time factor may also depend on a pre-arranged control factor, a. Multiple encryption keys may be stored by resource list 28 associated with TPM 26. Using the appropriate encryption key, TPM 26 may also check the expiration of the electronic content using its electronic signature date.
  • FIG. 11 illustrates a flow chart of an example method 200 for verifying electronic software code integrity, in accordance with certain embodiments of the present disclosure. Method 200 may include multiple steps and may be performed by various components of electronic network 1, including client system 20 and/or other resources. Method 200 may start at 202.
  • In accordance with the teachings of the present disclosure, code integrity may be substantially improved by including an update timing/key control. The encryption key may change based on a time factor. For example, the time factor may depend at least in part on a time stamp related to the sending and/or the delivery of electronic content. As another example, the time factor may depend at least in part on the update timing of TPM 26 and/or a VM 22. In any case, the time factor may also depend on a pre-arranged control factor, a. Multiple encryption keys may be stored by resource list 28 associated with TPM 26. Using the appropriate encryption key, TPM 26 may also check the expiration of the electronic content using its electronic signature date.
  • Step 204 may include storing a list of encryption keys from data center 10, each of the encryption keys correlated to a respective time factor. The list may be stored by TPM 24 and/or by a storage resource associated with TPM 24.
  • Step 206 may include receiving an encrypted software code packet from data center 10. In some embodiments, an electronic signature may also be received.
  • Step 208 may include choosing an encryption key based on a time factor. In some embodiments, TPM 24 may also check an electronic signature delivered with the encrypted software packet. Method 200 may end at 210.
  • Although FIGS. 4-11 represent a particular number of steps to be taken with respect to methods 60, 80, 100, 120, 140, 160, 184, and 200, the various methods may be executed with more or fewer steps than those depicted. Using the methods and systems disclosed herein, certain problems associated with maintaining secure access to electronic content may be improved, reduced, or eliminated. For example, the methods and system disclosed herein may provide increased security and/or reliability for electronic network performing remote maintenance of client systems.
  • Although the present invention has been described with several embodiments, various changes and modifications may be suggested to one skilled in the art. It is intended that the present invention encompass such changes and modifications as fall within the scope of the appended claims. The teachings of the present disclosure encompass all changes, substitutions, variations, alterations, modifications to the example embodiments herein that a person having ordinary skill in the art would comprehend.
  • In particular embodiments, one or more web pages may be associated with a networking system and/or networking service. Particular embodiments may involve the retrieval and/or rendering of structured documents hosted by any type of network addressable resource or web site. Additionally, as used herein, a “user” may include an individual, a group, and/or a corporate entity (e.g., a business and a third party application).

Claims (28)

What is claimed is:
1. A system for performing remote maintenance in an electronic network configured to serve a plurality of clients, the system comprising:
a client including a plurality of nodes;
each one of the plurality of nodes having a respective set of processing instructions stored on an respective associated computer readable memory;
a database associated with the electronic network, the database including information correlating a list of nodes with a respective set of processing instructions; and
a virtual machine operable to access the database and perform calculations simulating proposed combinations of nodes and their respective set of processing instructions before approving a software update requested for the client.
2. A system according to claim 1, wherein the virtual machine includes:
an operating system; and
processing instructions encoded in a computer readable memory, the processing instructions, when executed by the processing resource, operable to perform operations comprising:
receiving a request to provide a software update to the client;
querying the database for information associated with the client;
simulating a combination of the plurality of nodes of the client with the requested software update;
comparing a result of the simulation to one or more rules for compatibility; and
approving the requested software update if the result complies with the one or more rules for compatibility.
3. A system according to claim 1, wherein the client is an automobile.
4. A system according to claim 1, further comprising the virtual machine configured to receive data regarding a current status of the client through a trusted platform module.
5. A system according to claim 1, wherein the client includes a FlexRay system associated with an automobile.
6. A system according to claim 1, further comprising the virtual machine operable to perform a risk analysis for a requested software update based on one or more safety factors.
7. A system according to claim 1, further comprising the virtual machine operable to perform a risk analysis for a requested software update based at least on a high speed performance metric.
8. A system according to claim 1, further comprising the virtual machine operable to perform a risk analysis for a requested software update based at least on an environmental resistance performance metric.
9. A system according to claim 1, further comprising the virtual machine operable to create a report regarding the software update requested for the client.
10. A system according to claim 1, further comprising the virtual machine operable to create a report regarding the software update requested for the client, the report including a summary of operational information related to the client.
11. A system according to claim 1, further comprising the virtual machine operable to create a report regarding the software update requested for the client, the report including a Hash value calculated by a trusted platform module.
12. A system according to claim 1, further comprising the virtual machine operable to create a report regarding the software update requested for the client, the report including a time stamp.
13. A system according to claim 1, further comprising the virtual machine operable to create a report regarding the software update requested for the client, the report stored by a computer readable memory associated with the electronic network.
14. A system according to claim 1, further comprising the virtual machine operable to propose an alternative software update if the requested software update fails to comply with a rule for compatibility.
15. A method for performing remote maintenance in a client system served by an electronic network, the method comprising:
maintaining a database including information correlating a list of client system nodes with a respective set of processing instructions;
receiving a request for a software update, the request including an identifier corresponding to a specific client system and a specific set of processing instructions;
accessing the database to retrieve the information related to the nodes associated with the client systems and the respective set of processing instructions correlated to the associated processors; and
performing calculations simulating a combination of nodes and respective processing instructions that would result from the installation of the requested software update.
16. A method according to claim 15, further comprising comparing a result of the simulation calculations to one or more rules for compatibility.
17. A method according to claim 15, further comprising approving the requested software update if a result of the simulation calculations complies with one or more rules for compatibility.
18. A method according to claim 15, further comprising receiving data regarding a current status of the client system through a trusted platform module.
19. A method according to claim 15, wherein the client system includes a FlexRay system associated with an automobile.
20. A method according to claim 15, further comprising performing a risk analysis for the requested software update based on one or more safety factors.
21. A method according to claim 15, further comprising performing a risk analysis for a requested software update based at least on a high speed performance metric.
22. A method according to claim 15, further comprising performing a risk analysis for a requested software update based at least on an environmental resistance performance metric.
23. A method according to claim 15, further comprising creating a report regarding the software update requested for the client system.
24. A method according to claim 15, further comprising creating a report regarding the software update requested for the client system, the report including a summary of operational information related to the client.
25. A method according to claim 15, further comprising creating a report regarding the software update requested for the client system, the report including a Hash value calculated by a trusted platform module.
26. A method according to claim 15, further comprising creating a report regarding the software update requested for the client system, the report including a time stamp.
27. A method according to claim 15, further comprising creating a report regarding the software update requested for the client, the report stored by a computer readable memory associated with the electronic network.
28. A method according to claim 15, further comprising proposing an alternative software update if the requested software update fails to comply with a rule for compatibility.
US14/713,470 2010-03-23 2015-05-15 System and methods for remote maintenance in an electronic network with multiple clients Abandoned US20150248286A1 (en)

Priority Applications (3)

Application Number Priority Date Filing Date Title
US31649810P true 2010-03-23 2010-03-23
US12/879,226 US9059978B2 (en) 2010-03-23 2010-09-10 System and methods for remote maintenance in an electronic network with multiple clients
US14/713,470 US20150248286A1 (en) 2010-03-23 2015-05-15 System and methods for remote maintenance in an electronic network with multiple clients

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
US14/713,470 US20150248286A1 (en) 2010-03-23 2015-05-15 System and methods for remote maintenance in an electronic network with multiple clients

Related Parent Applications (1)

Application Number Title Priority Date Filing Date
US12/879,226 Continuation US9059978B2 (en) 2010-03-23 2010-09-10 System and methods for remote maintenance in an electronic network with multiple clients

Publications (1)

Publication Number Publication Date
US20150248286A1 true US20150248286A1 (en) 2015-09-03

Family

ID=44657040

Family Applications (8)

Application Number Title Priority Date Filing Date
US12/879,189 Abandoned US20110239209A1 (en) 2010-03-23 2010-09-10 System and methods for remote maintenance in an electronic network with multiple clients
US12/879,433 Abandoned US20110238980A1 (en) 2010-03-23 2010-09-10 System and methods for remote maintenance in an electronic network with multiple clients
US12/879,204 Abandoned US20110238402A1 (en) 2010-03-23 2010-09-10 System and methods for remote maintenance in an electronic network with multiple clients
US12/879,226 Expired - Fee Related US9059978B2 (en) 2010-03-23 2010-09-10 System and methods for remote maintenance in an electronic network with multiple clients
US12/879,175 Abandoned US20110237234A1 (en) 2010-03-23 2010-09-10 System and methods for remote maintenance in an electronic network with multiple clients
US14/713,675 Active US9766914B2 (en) 2010-03-23 2015-05-15 System and methods for remote maintenance in an electronic network with multiple clients
US14/713,556 Abandoned US20150248287A1 (en) 2010-03-23 2015-05-15 System and methods for remote maintenance in an electronic network with multiple clients
US14/713,470 Abandoned US20150248286A1 (en) 2010-03-23 2015-05-15 System and methods for remote maintenance in an electronic network with multiple clients

Family Applications Before (7)

Application Number Title Priority Date Filing Date
US12/879,189 Abandoned US20110239209A1 (en) 2010-03-23 2010-09-10 System and methods for remote maintenance in an electronic network with multiple clients
US12/879,433 Abandoned US20110238980A1 (en) 2010-03-23 2010-09-10 System and methods for remote maintenance in an electronic network with multiple clients
US12/879,204 Abandoned US20110238402A1 (en) 2010-03-23 2010-09-10 System and methods for remote maintenance in an electronic network with multiple clients
US12/879,226 Expired - Fee Related US9059978B2 (en) 2010-03-23 2010-09-10 System and methods for remote maintenance in an electronic network with multiple clients
US12/879,175 Abandoned US20110237234A1 (en) 2010-03-23 2010-09-10 System and methods for remote maintenance in an electronic network with multiple clients
US14/713,675 Active US9766914B2 (en) 2010-03-23 2015-05-15 System and methods for remote maintenance in an electronic network with multiple clients
US14/713,556 Abandoned US20150248287A1 (en) 2010-03-23 2015-05-15 System and methods for remote maintenance in an electronic network with multiple clients

Country Status (5)

Country Link
US (8) US20110239209A1 (en)
EP (4) EP2550595B1 (en)
JP (4) JP5516821B2 (en)
CN (4) CN102823195B (en)
WO (4) WO2011119298A1 (en)

Families Citing this family (53)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9069575B2 (en) 2008-03-25 2015-06-30 Qualcomm Incorporated Apparatus and methods for widget-related memory management
US9600261B2 (en) * 2008-03-25 2017-03-21 Qualcomm Incorporated Apparatus and methods for widget update scheduling
US8693357B1 (en) * 2010-09-20 2014-04-08 Rockwell Collins, Inc. Apparatus and method for testing equipment in a simulated AFDX network environment
US9146726B2 (en) * 2010-12-16 2015-09-29 Netapp, Inc. System and method for firmware update for network connected storage subsystem components
US9087196B2 (en) * 2010-12-24 2015-07-21 Intel Corporation Secure application attestation using dynamic measurement kernels
KR101760778B1 (en) * 2011-01-17 2017-07-26 에스프린팅솔루션 주식회사 Computer system and method for updating program therein
WO2012098478A1 (en) 2011-01-19 2012-07-26 International Business Machines Corporation Updating software
CN102737019B (en) * 2011-03-31 2016-08-24 阿里巴巴集团控股有限公司 Method for determining the behavior of the machine, the web browser and web server
US8826275B2 (en) * 2011-09-01 2014-09-02 Ca, Inc. System and method for self-aware virtual machine image deployment enforcement
KR101299099B1 (en) * 2011-09-07 2013-09-16 주식회사 팬택 Apparatus and method for management of optimized virtualization module in embedded system
US8930489B2 (en) * 2011-10-11 2015-01-06 Rakspace US, Inc. Distributed rate limiting of handling requests
EP2590100A1 (en) * 2011-11-04 2013-05-08 British Telecommunications Public Limited Company Method and apparatus for securing a computer
US8881143B2 (en) * 2011-11-04 2014-11-04 Diwakar PRABHAKARAN Optimization framework for remotely executing a maintenance operation on a virtual machine
DE102012200155A1 (en) * 2012-01-05 2013-07-11 Continental Automotive Gmbh Computer system and method for operating a computer system
JP2013205604A (en) * 2012-03-28 2013-10-07 Toshiba Corp Communication device and key management method
DE102012009482A1 (en) * 2012-05-12 2013-11-14 Volkswagen Aktiengesellschaft A functionally expandable vehicle control device and method for supplementing the functionality of a vehicle control device
JP5870840B2 (en) * 2012-05-14 2016-03-01 ソニー株式会社 Information processing apparatus, information processing method, and information processing program
US8782632B1 (en) * 2012-06-18 2014-07-15 Tellabs Operations, Inc. Methods and apparatus for performing in-service software upgrade for a network device using system virtualization
US8910132B2 (en) * 2012-07-13 2014-12-09 Facebook, Inc. Client-side script bundle management system
US9244743B1 (en) * 2012-08-01 2016-01-26 Amazon Technologies, Inc. Remotely interacting with a virtualized machine instance
JP5946374B2 (en) * 2012-08-31 2016-07-06 株式会社富士通エフサス Network connection method and electronic device
JP5990433B2 (en) 2012-08-31 2016-09-14 株式会社富士通エフサス Network connection method and electronic device
US8924720B2 (en) * 2012-09-27 2014-12-30 Intel Corporation Method and system to securely migrate and provision virtual machine images and content
US9106721B2 (en) * 2012-10-02 2015-08-11 Nextbit Systems Application state synchronization across multiple devices
US9038060B2 (en) 2012-10-02 2015-05-19 Nextbit Systems Inc. Automatically installing operating system specific to a detected network
US8983961B2 (en) * 2012-11-29 2015-03-17 International Business Machines Corporation High availability for cloud servers
CN103024042A (en) * 2012-12-13 2013-04-03 中国航空无线电电子研究所 Avionics full duplex switched Ethernet (AFDX) terminal protocol stack, and data receiving and sending method thereof
CN103139221B (en) * 2013-03-07 2016-07-06 中国科学院软件研究所 A credible virtual platform and its construction method, the method of data migration between platforms
US20140281447A1 (en) * 2013-03-12 2014-09-18 Green Hills Software, Inc. Single-Chip Virtualizing and Obfuscating Communications System for Portable Computing Devices
CN103347067B (en) * 2013-06-26 2016-04-20 中国科学院信息工程研究所 A remote control system and method for reconstruction
US9372679B2 (en) * 2013-08-02 2016-06-21 Sap Se Method and system for software delivery service
CN104378391A (en) * 2013-08-12 2015-02-25 无锡知谷网络科技有限公司 Software updating method, system and device
US9417904B2 (en) * 2013-09-13 2016-08-16 Electronics And Telecommunications Research Institute Cyber-physical system and method of monitoring virtual machine thereof
JP5864510B2 (en) * 2013-10-18 2016-02-17 富士通株式会社 Correction program checking method, correction program checking program, and information processing apparatus
CN104639516B (en) * 2013-11-13 2018-02-06 华为技术有限公司 Identity identifying method, equipment and system
CN105745661A (en) * 2013-12-19 2016-07-06 英特尔公司 Policy-based trusted inspection of rights managed content
CN103714170A (en) * 2013-12-31 2014-04-09 北京智谷睿拓技术服务有限公司 Data access information release and access method and device
CN103763351A (en) * 2014-01-03 2014-04-30 中达电通股份有限公司 Software online upgrading method based on upper computer and lower computers
US10389709B2 (en) * 2014-02-24 2019-08-20 Amazon Technologies, Inc. Securing client-specified credentials at cryptographically attested resources
CN103823700B (en) * 2014-02-28 2017-11-14 北京数码大方科技股份有限公司 The application software updating method and device of client
CA2854022A1 (en) * 2014-06-11 2015-12-11 Ibm Canada Limited - Ibm Canada Limitee Artifact correlation between domains
CN104317715A (en) * 2014-10-30 2015-01-28 南京富士通南大软件技术有限公司 Simulator based automatic functional test implementation method for central processing unit instruction sets
US20180013830A1 (en) * 2015-01-30 2018-01-11 Nec Europe Ltd. Method and system for managing encrypted data of devices
WO2016137512A1 (en) * 2015-02-27 2016-09-01 Hewlett Packard Enterprise Development Lp Cloud network management
EP3099019B1 (en) * 2015-05-27 2019-01-02 OpenSynergy GmbH Method, computer program product, and control unit for an automotive vehicle
EP3101535A1 (en) 2015-06-01 2016-12-07 OpenSynergy GmbH Method for updating a control unit for an automotive vehicle, control unit for an automotive vehicle, and computer program product
JP2017004201A (en) * 2015-06-09 2017-01-05 富士通株式会社 Patch program extraction apparatus, patch program extraction program, and patch program extraction method
EP3347850A1 (en) * 2015-09-07 2018-07-18 Karamba Security Context-based secure controller operation and malware prevention
US9864624B2 (en) 2015-12-21 2018-01-09 International Business Machines Corporation Software-defined computing system remote support
US10402577B2 (en) * 2016-06-03 2019-09-03 Honeywell International Inc. Apparatus and method for device whitelisting and blacklisting to override protections for allowed media at nodes of a protected system
CN106155632A (en) * 2016-08-02 2016-11-23 合肥奇也信息科技有限公司 System for small code sets in processing of optimal positioning data of computer
CN106453300A (en) * 2016-09-30 2017-02-22 北京悦畅科技有限公司 Data encryption and decryption method and device, and data transmission system
CN106778380A (en) * 2016-11-28 2017-05-31 昆山国显光电有限公司 Screen lightening method and system

Family Cites Families (159)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7143290B1 (en) 1995-02-13 2006-11-28 Intertrust Technologies Corporation Trusted and secure techniques, systems and methods for item delivery and execution
US7353396B2 (en) 1995-10-02 2008-04-01 Corestreet, Ltd. Physical access control
US5892900A (en) 1996-08-30 1999-04-06 Intertrust Technologies Corp. Systems and methods for secure transaction management and electronic rights protection
US6859699B2 (en) * 1997-05-16 2005-02-22 Snap-On Incorporated Network-based method and system for distributing data
JP3657396B2 (en) * 1997-07-07 2005-06-08 株式会社日立製作所 Key management system, the key management device, information encrypting apparatus, the information decoding device, and stores a program storage medium
CN100570314C (en) 1998-01-05 2009-12-16 美国环境保护署 Real-time mobile vehicle emissions reporting system and test system
JP3659791B2 (en) * 1998-03-23 2005-06-15 インターナショナル・ビジネス・マシーンズ・コーポレーションInternational Business Maschines Corporation The method and system of the small-time key generation
US6795966B1 (en) * 1998-05-15 2004-09-21 Vmware, Inc. Mechanism for restoring, porting, replicating and checkpointing computer systems using state extraction
US6150322A (en) 1998-08-12 2000-11-21 Shell Oil Company Highly branched primary alcohol compositions and biodegradable detergents made therefrom
CN1230730A (en) * 1998-12-10 1999-10-06 易际平 Data enciphering and deciphering system and method
JP4370018B2 (en) * 1999-03-12 2009-11-25 三菱電機株式会社 Software transfer system
JP4212717B2 (en) 1999-04-30 2009-01-21 富士通株式会社 File processing unit processing method
JP3782259B2 (en) 1999-05-31 2006-06-07 富士通株式会社 Signature creation device
JP3748352B2 (en) 1999-12-16 2006-02-22 富士通株式会社 Data application method, a recording medium for recording a program of an image generating method, a recording medium for recording a program of an image restoration method
US20020178370A1 (en) 1999-12-30 2002-11-28 Gurevich Michael N. Method and apparatus for secure authentication and sensitive data management
US6996829B2 (en) * 2000-02-25 2006-02-07 Oracle International Corporation Handling callouts made by a multi-threaded virtual machine to a single threaded environment
GB2359908B (en) 2000-03-04 2004-09-15 Motorola Inc Communication system architecture and method of controlling data download to subscriber equipment
US7165173B1 (en) 2000-09-01 2007-01-16 Samsung Electronics Co., Ltd. System and method for secure over-the-air administration of a wireless mobile station
NO20005440L (en) 2000-10-27 2002-04-29 Ericsson Telefon Ab L M Packet-based personal equipment events and - procedures
US8677505B2 (en) * 2000-11-13 2014-03-18 Digital Doors, Inc. Security system with extraction, reconstruction and secure recovery and storage of data
US7574481B2 (en) * 2000-12-20 2009-08-11 Microsoft Corporation Method and system for enabling offline detection of software updates
US7412721B2 (en) 2000-12-20 2008-08-12 Fujitsu Limited Method of and system for managing information, and computer product
AU2002252034A1 (en) * 2001-02-22 2002-09-12 Bea Systems, Inc. System and method for message encryption and signing in a transaction processing system
GB0112781D0 (en) * 2001-05-25 2001-07-18 Global Continuity Plc Method for rapid recovery from a network file server failure
US7359377B1 (en) * 2001-06-19 2008-04-15 Juniper Networks, Inc. Graceful restart for use in nodes employing label switched path signaling protocols
US6775602B2 (en) 2001-07-09 2004-08-10 Gordon-Darby Systems, Inc. Method and system for vehicle emissions testing through on-board diagnostics unit inspection
US20030099360A1 (en) * 2001-11-28 2003-05-29 Khoi Hoang Time-based encryption key
JP2003271831A (en) * 2002-03-15 2003-09-26 Nippon Telegr & Teleph Corp <Ntt> Contents circulation method, contents circulation system and program therefor, and recording medium
FI114061B (en) 2002-05-17 2004-07-30 Nokia Corp A method and system for a digital wireless communication network providing a data encryption and the corresponding server
US7415605B2 (en) * 2002-05-21 2008-08-19 Bio-Key International, Inc. Biometric identification network security
US7003692B1 (en) * 2002-05-24 2006-02-21 Cisco Technology, Inc. Dynamic configuration synchronization in support of a “hot” standby stateful switchover
US7275081B1 (en) * 2002-06-10 2007-09-25 Juniper Networks, Inc. Managing state information in a computing environment
JP2004094301A (en) * 2002-08-29 2004-03-25 Fuji Xerox Co Ltd Update method, update control device and update device for software incorporated in processor
US7275156B2 (en) 2002-08-30 2007-09-25 Xerox Corporation Method and apparatus for establishing and using a secure credential infrastructure
US7269133B2 (en) * 2002-09-03 2007-09-11 Jeremy Benjamin IS-IS high availability design
US7216343B2 (en) * 2002-09-20 2007-05-08 International Business Machines Corporation Method and apparatus for automatic updating and testing of software
JP3693642B2 (en) * 2002-10-29 2005-09-07 本田技研工業株式会社 Navigation device
JP2004206671A (en) * 2002-11-08 2004-07-22 Qwanty Corp Software update information provision method and software update information provision system
US7366892B2 (en) * 2003-01-28 2008-04-29 Cellport Systems, Inc. Secure telematics
US20040181327A1 (en) 2003-03-11 2004-09-16 Tsosie Everett K. Vehicle security through an automatic control system
US7620948B1 (en) * 2003-08-29 2009-11-17 Adobe Systems Incorporated Client side software updating
US7739403B1 (en) * 2003-10-03 2010-06-15 Juniper Networks, Inc. Synchronizing state information between control units
US20050132367A1 (en) 2003-12-16 2005-06-16 Vijay Tewari Method, apparatus and system for proxying, aggregating and optimizing virtual machine information for network-based management
US7587765B2 (en) * 2003-12-23 2009-09-08 International Business Machines Corporation Automatic virus fix
CA2456598A1 (en) * 2004-01-28 2005-07-28 Goran Ekstrom Method of enabling secure transfer of a package of information
JP4554264B2 (en) * 2004-04-19 2010-09-29 エヌ・ティ・ティ・ソフトウェア株式会社 Digital signature processing method and program therefor
CN1918526B (en) 2004-04-30 2012-03-14 富士通半导体股份有限公司 Information management apparatus and an information management method
US7590867B2 (en) 2004-06-24 2009-09-15 Intel Corporation Method and apparatus for providing secure virtualization of a trusted platform module
US7577959B2 (en) * 2004-06-24 2009-08-18 International Business Machines Corporation Providing on-demand capabilities using virtual machines and clustering processes
JP2006031203A (en) * 2004-07-14 2006-02-02 Xanavi Informatics Corp On-vehicle information terminal
DE102004038210A1 (en) * 2004-08-05 2006-03-16 Robert Bosch Gmbh Method for storing messages in a message memory and the message memory
US7516451B2 (en) * 2004-08-31 2009-04-07 Innopath Software, Inc. Maintaining mobile device electronic files including using difference files when upgrading
US8095601B2 (en) 2004-10-22 2012-01-10 Microsoft Corporation Inter-proximity communication within a rendezvous federation
US8095600B2 (en) 2004-10-22 2012-01-10 Microsoft Corporation Inter-proximity communication within a rendezvous federation
US9489496B2 (en) * 2004-11-12 2016-11-08 Apple Inc. Secure software updates
US20060106806A1 (en) * 2004-11-12 2006-05-18 Smith Micro Software, Inc. Software update for a plurality of mobile devices
US20060184937A1 (en) 2005-02-11 2006-08-17 Timothy Abels System and method for centralized software management in virtual machines
EP1710597A1 (en) 2005-04-08 2006-10-11 Sanofi-Aventis Deutschland GmbH Method of acquiring multidimensional NMR spectra by frequency-dependent folding
US7609617B2 (en) * 2005-04-14 2009-10-27 Cisco Technology, Inc. BGP hitless upgrade approaches
US7483438B2 (en) 2005-04-14 2009-01-27 Alcatel Lucent Systems and methods for managing network services between private networks
US8074262B2 (en) 2005-05-13 2011-12-06 Intel Corporation Method and apparatus for migrating virtual trusted platform modules
US7571312B2 (en) 2005-05-13 2009-08-04 Intel Corporation Methods and apparatus for generating endorsement credentials for software-based security coprocessors
US7636442B2 (en) 2005-05-13 2009-12-22 Intel Corporation Method and apparatus for migrating software-based security coprocessors
US7613921B2 (en) 2005-05-13 2009-11-03 Intel Corporation Method and apparatus for remotely provisioning software-based security coprocessors
US7587595B2 (en) 2005-05-13 2009-09-08 Intel Corporation Method and apparatus for providing software-based security coprocessors
JP2006350469A (en) * 2005-06-13 2006-12-28 Xanavi Informatics Corp Navigation device
US7693612B2 (en) * 2005-06-23 2010-04-06 International Business Machines Corporation Method and system for updating code embedded in a vehicle
US8495244B2 (en) 2005-06-29 2013-07-23 Jumpstart Wireless Corporation System and method for dynamic automatic communication path selection, distributed device synchronization and task delegation
KR20070032885A (en) 2005-09-20 2007-03-23 엘지전자 주식회사 Security system and method for ubiquitous networks
US20070083723A1 (en) * 2005-09-23 2007-04-12 Dey Jayanta K Highly-available blade-based distributed computing system
DE102005048595A1 (en) * 2005-10-06 2007-04-12 Robert Bosch Gmbh Method for connecting a FlexRay subscriber with a microcontroller to a FlexRay communication connection via a FlexRay communication control device, and FlexRay communication control device, FlexRay subscriber and FlexRay communication system for implementing this method
US7804769B1 (en) * 2005-12-01 2010-09-28 Juniper Networks, Inc. Non-stop forwarding in a multi-chassis router
US20070169083A1 (en) * 2005-12-12 2007-07-19 Penubolu Shyam P Method for secure in-service software upgrades
US20070174429A1 (en) * 2006-01-24 2007-07-26 Citrix Systems, Inc. Methods and servers for establishing a connection between a client system and a virtual machine hosting a requested computing environment
US20070275733A1 (en) * 2006-03-03 2007-11-29 David Vismons Method for providing certain information
US7783471B2 (en) * 2006-03-08 2010-08-24 David Vismans Communication device for emulating a behavior of a navigation device
US7814495B1 (en) * 2006-03-31 2010-10-12 V Mware, Inc. On-line replacement and changing of virtualization software
JP2007288747A (en) * 2006-04-20 2007-11-01 Ricoh Co Ltd Image processing system, control method of same, image forming apparatus, and image reproducing device
US7802245B2 (en) * 2006-04-27 2010-09-21 Agere Systems Inc. Methods and apparatus for performing in-service upgrade of software in network processor
US8291409B2 (en) * 2006-05-22 2012-10-16 Microsoft Corporation Updating virtual machine with patch on host that does not have network access
US9213513B2 (en) * 2006-06-23 2015-12-15 Microsoft Technology Licensing, Llc Maintaining synchronization of virtual machine image differences across server and host computers
US9392078B2 (en) * 2006-06-23 2016-07-12 Microsoft Technology Licensing, Llc Remote network access via virtual machine
US9280871B2 (en) 2006-07-07 2016-03-08 Emc Corporation Gaming systems with authentication token support
JP2010500667A (en) * 2006-08-07 2010-01-07 ベア・システムズ・インコーポレイテッドBea Systems, Inc. System and method for providing hardware virtualization in a virtual machine environment
US7676229B2 (en) 2006-08-31 2010-03-09 Syniverse Technologies, Inc. Cellular-to-VoIP call establishment systems, methods, devices, and computer software
JP5308621B2 (en) * 2006-10-05 2013-10-09 日立オートモティブシステムズ株式会社 Map data distribution system
JP4930028B2 (en) * 2006-12-13 2012-05-09 ソニー株式会社 Information processing apparatus, information processing method, and program
US9280659B2 (en) 2006-12-29 2016-03-08 Intel Corporation Methods and apparatus for remeasuring a virtual machine monitor
US8468244B2 (en) 2007-01-05 2013-06-18 Digital Doors, Inc. Digital information infrastructure and method for security designated data and with granular data stores
US7840801B2 (en) 2007-01-19 2010-11-23 International Business Machines Corporation Architecture for supporting attestation of a virtual machine in a single step
US20080184216A1 (en) * 2007-01-25 2008-07-31 Johan Muedsam Managing application software in mobile communication devices
US20120011509A1 (en) * 2007-02-15 2012-01-12 Syed Mohammad Amir Husain Migrating Session State of a Machine Without Using Memory Images
US8028048B2 (en) * 2007-02-27 2011-09-27 International Business Machines Corporation Method and apparatus for policy-based provisioning in a virtualized service delivery environment
US8578337B2 (en) * 2007-02-28 2013-11-05 Red Hat, Inc. Method and system for quality assurance subscription service
US7694189B2 (en) * 2007-02-28 2010-04-06 Red Hat, Inc. Method and system for remote monitoring subscription service
US7814995B2 (en) * 2007-03-19 2010-10-19 National Oilwell Varco, L.P. Hydraulic jar and an overpressure relief mechanism therefor
US20080244552A1 (en) * 2007-03-27 2008-10-02 Telefonaktiebolaget Lm Ericsson (Publ) Upgrading services associated with high availability systems
US8677351B2 (en) * 2007-03-29 2014-03-18 Vmware, Inc. System and method for delivering software update to guest software on virtual machines through a backdoor software communication pipe thereof
US8229458B2 (en) 2007-04-08 2012-07-24 Enhanced Geographic Llc Systems and methods to determine the name of a location visited by a user of a wireless device
JP2010531478A (en) * 2007-04-26 2010-09-24 フォード グローバル テクノロジーズ、リミテッド ライアビリティ カンパニー Emotional advice system and method
US8612773B2 (en) * 2007-05-03 2013-12-17 International Business Machines Corporation Method and system for software installation
US8151277B2 (en) * 2007-05-15 2012-04-03 Dynatrace Software Gmbh Method and system for dynamic remote injection of in-process agents into virtual machine based applications
JP4369497B2 (en) 2007-05-17 2009-11-18 株式会社日立製作所 Direct digital synthesizer and nuclear magnetic resonance apparatus using the same
WO2009001447A1 (en) 2007-06-27 2008-12-31 Fujitsu Limited Authentication method, authentication system, authentication device, and computer program
JP2009012926A (en) 2007-07-04 2009-01-22 Hitachi Plant Technologies Ltd Transfer device and transfer method
US8055822B2 (en) 2007-08-21 2011-11-08 International Business Machines Corporation Multicore processor having storage for core-specific operational data
US8064605B2 (en) 2007-09-27 2011-11-22 Intel Corporation Methods and apparatus for providing upgradeable key bindings for trusted platform modules
US8806472B2 (en) * 2007-09-27 2014-08-12 Ericsson Ab In-service software upgrade utilizing metadata-driven state translation
US20090204964A1 (en) * 2007-10-12 2009-08-13 Foley Peter F Distributed trusted virtualization platform
US8245217B2 (en) * 2007-10-12 2012-08-14 Microsoft Corporation Management of software and operating system updates required for the process of creating a virtual machine facsimile of an existing physical or virtual machine
US8539098B2 (en) * 2007-10-17 2013-09-17 Dispersive Networks, Inc. Multiplexed client server (MCS) communications and systems
US8392902B2 (en) * 2007-10-24 2013-03-05 Siemens Aktiengesellschaft Upgrading software applications offline using a virtual machine
JP5019382B2 (en) 2007-10-30 2012-09-05 マーキュリー・システムズ株式会社 Mobile body status verification information control system
US8065517B2 (en) 2007-11-01 2011-11-22 Infineon Technologies Ag Method and system for transferring information to a device
JP5134338B2 (en) 2007-11-01 2013-01-30 富士通セミコンダクター株式会社 Authentication apparatus and control method
JP2009122749A (en) * 2007-11-12 2009-06-04 Fujitsu Ltd Program, portable storage medium, and control method
JP4946826B2 (en) 2007-11-26 2012-06-06 富士通株式会社 Emission apportioning device and emission apportioning program
US7962587B2 (en) * 2007-12-10 2011-06-14 Oracle America, Inc. Method and system for enforcing resource constraints for virtual machines across migration
US7984123B2 (en) * 2007-12-10 2011-07-19 Oracle America, Inc. Method and system for reconfiguring a virtual network path
WO2009085977A2 (en) * 2007-12-20 2009-07-09 Virtual Computer, Inc. Virtual computing management systems and methods
DE102007062114A1 (en) * 2007-12-21 2009-07-23 Opensynergy Gmbh Motor vehicle control device
US8090919B2 (en) * 2007-12-31 2012-01-03 Intel Corporation System and method for high performance secure access to a trusted platform module on a hardware virtualization platform
US8201161B2 (en) * 2008-01-07 2012-06-12 Lenovo (Singapore) Pte. Ltd. System and method to update device driver or firmware using a hypervisor environment without system shutdown
FR2926375B1 (en) * 2008-01-11 2010-02-12 Airbus France Method for performing computer application, kit and aircraft
US8713556B2 (en) * 2008-02-25 2014-04-29 Sap Ag Virtual appliance update method
JP2009217395A (en) 2008-03-07 2009-09-24 Nec Corp Virtual server software update system, virtual server software update method, server and program for server
US9015704B2 (en) * 2008-03-24 2015-04-21 International Business Machines Corporation Context agent injection using virtual machine introspection
WO2009121046A1 (en) * 2008-03-28 2009-10-01 Celltrust Corporation Systems and methods for secure short messaging service and multimedia messaging service
WO2009122530A1 (en) 2008-03-31 2009-10-08 富士通株式会社 Authentication method, authentication device, program, and recording medium
JP5163238B2 (en) 2008-04-02 2013-03-13 トヨタ自動車株式会社 Charging service system and charging service station
US10127059B2 (en) * 2008-05-02 2018-11-13 Skytap Multitenant hosted virtual machine infrastructure
US20090313032A1 (en) 2008-06-16 2009-12-17 International Business Machines Corporation Maintaining Energy Principal Preferences for a Vehicle by a Remote Preferences Service
US8316211B2 (en) * 2008-06-30 2012-11-20 Intel Corporation Generating multiple address space identifiers per virtual machine to switch between protected micro-contexts
WO2010024893A1 (en) * 2008-08-26 2010-03-04 Ringleader Digital Nyc Uniquely identifying network-distributed devices without explicitly provided device or user identifying information
JP2010061237A (en) 2008-09-01 2010-03-18 Fujitsu Ten Ltd In-vehicle settlement system, in-vehicle settlement device, and in-vehicle settlement communication interface card
EP2161901A1 (en) 2008-09-04 2010-03-10 Sony Corporation Aggregated user presence management method within a home network and device for user presence management within a home network
KR100979201B1 (en) * 2008-09-16 2010-09-01 한국전자통신연구원 Mobile terminals and Method for updating software thereof
US8499297B2 (en) * 2008-10-28 2013-07-30 Vmware, Inc. Low overhead fault tolerance through hybrid checkpointing and replay
JP5223596B2 (en) * 2008-10-30 2013-06-26 富士通株式会社 Virtual computer system and management method thereof, management program, recording medium, and control method
US20100161922A1 (en) * 2008-12-19 2010-06-24 Richard William Sharp Systems and methods for facilitating migration of virtual machines among a plurality of physical machines
JP4650567B2 (en) 2008-12-24 2011-03-16 三菱自動車工業株式会社 Electric vehicle charging display
JP5353291B2 (en) 2009-02-19 2013-11-27 ソニー株式会社 Guide route delivery apparatus, guide route delivery method, and guide route delivery program
CN101621377A (en) 2009-03-26 2010-01-06 常熟理工学院 Trusted access method under virtual computing environment
US8261266B2 (en) * 2009-04-30 2012-09-04 Microsoft Corporation Deploying a virtual machine having a virtual hardware configuration matching an improved hardware profile with respect to execution of an application
US8943498B2 (en) * 2009-05-31 2015-01-27 Red Hat Israel, Ltd. Method and apparatus for swapping virtual machine memory
US7906937B2 (en) 2009-06-02 2011-03-15 Coulomb Technologies, Inc. Overcurrent and ground fault protection in a networked charging station for electric vehicles
US8055933B2 (en) * 2009-07-21 2011-11-08 International Business Machines Corporation Dynamic updating of failover policies for increased application availability
US8838332B2 (en) * 2009-10-15 2014-09-16 Airbiquity Inc. Centralized management of motor vehicle software applications and services
US8726334B2 (en) * 2009-12-09 2014-05-13 Microsoft Corporation Model based systems management in virtualized and non-virtualized environments
US8310950B2 (en) * 2009-12-28 2012-11-13 Oracle America, Inc. Self-configuring networking devices for providing services in a nework
US8291258B2 (en) * 2010-01-08 2012-10-16 Juniper Networks, Inc. High availability for network security devices
US8549272B2 (en) * 2010-02-10 2013-10-01 Dell Products L.P. Information handling system image management deployment of virtual machine images to physical information handling systems
US8250398B2 (en) 2010-02-19 2012-08-21 Coulomb Technologies, Inc. Event time management in an electric vehicle charging station without a battery-backed real time clock
US20110214115A1 (en) * 2010-02-26 2011-09-01 Nokia Corporation Method and appartus for providing a high level mobile virtual machine
US8799422B1 (en) * 2010-08-16 2014-08-05 Juniper Networks, Inc. In-service configuration upgrade using virtual machine instances
US8402453B2 (en) * 2010-09-22 2013-03-19 Telefonaktiebolaget L M Ericsson (Publ) In-service software upgrade of control and line cards of network element
KR20120041384A (en) * 2010-10-21 2012-05-02 삼성전자주식회사 Method and apparatus for updating firmware of mobile device
US9369867B2 (en) * 2012-06-29 2016-06-14 Intel Corporation Mobile platform software update with secure authentication
CN103595530B (en) * 2012-08-17 2017-04-26 华为技术有限公司 Method and apparatus for updating software key

Also Published As

Publication number Publication date
US20110239210A1 (en) 2011-09-29
CN102870093B (en) 2016-04-06
JP2013532394A (en) 2013-08-15
JP2013522795A (en) 2013-06-13
CN102859935B (en) 2016-10-26
US20110237234A1 (en) 2011-09-29
JP2013522794A (en) 2013-06-13
US9766914B2 (en) 2017-09-19
EP2550595A1 (en) 2013-01-30
WO2011119299A1 (en) 2011-09-29
WO2011119297A1 (en) 2011-09-29
EP2550768B1 (en) 2015-03-25
CN102859935A (en) 2013-01-02
US20110238980A1 (en) 2011-09-29
US20110238402A1 (en) 2011-09-29
EP2550769A1 (en) 2013-01-30
EP2550769B1 (en) 2016-01-13
JP2013522793A (en) 2013-06-13
WO2011119300A3 (en) 2015-06-25
WO2011119298A1 (en) 2011-09-29
EP2550768A1 (en) 2013-01-30
JP5516821B2 (en) 2014-06-11
CN102823195B (en) 2016-10-19
US20150261554A1 (en) 2015-09-17
WO2011119300A2 (en) 2011-09-29
CN103154966A (en) 2013-06-12
EP2550596A2 (en) 2013-01-30
JP5522307B2 (en) 2014-06-18
US9059978B2 (en) 2015-06-16
US20110239209A1 (en) 2011-09-29
EP2550595B1 (en) 2016-11-23
JP5747981B2 (en) 2015-07-15
US20150248287A1 (en) 2015-09-03
CN102870093A (en) 2013-01-09
CN102823195A (en) 2012-12-12

Similar Documents

Publication Publication Date Title
US9654508B2 (en) Configuring and providing profiles that manage execution of mobile applications
EP2791817B1 (en) Cryptographic certification of secure hosted execution environments
US8468591B2 (en) Client authentication and data management system
JP5410500B2 (en) Apparatus, method and storage medium using apparatus identifier
US6189100B1 (en) Ensuring the integrity of remote boot client data
JP6222592B2 (en) Mobile application identity verification for mobile application management
US8931078B2 (en) Providing virtualized private network tunnels
CN100354852C (en) Automatic re-authentication
US9769266B2 (en) Controlling access to resources on a network
US9154488B2 (en) Secured access to resources using a proxy
US20070074034A1 (en) System and method for registering entities for code signing services
EP2256656A1 (en) Key management to protect encrypted data of an endpoint computing device
US8799997B2 (en) Secure network cloud architecture
KR20170129866A (en) Automated demonstration of device integrity using block chains
US9424439B2 (en) Secure data synchronization
EP1427160A2 (en) Methods and systems for authentication of a user for sub-locations of a network location
US9043600B2 (en) Security model for industrial devices
US8549326B2 (en) Method and system for extending encrypting file system
JP5658745B2 (en) HTTP-based authentication
US20020083178A1 (en) Resource distribution in network environment
US20150067769A1 (en) Providing Virtualized Private Network Tunnels
US20060265446A1 (en) Dynamic executable
US20120185694A1 (en) Information processing apparatus, a server apparatus, a method of an information processing apparatus, a method of a server apparatus, and an apparatus executable program
US20050015601A1 (en) Methods, systems, and media to authenticate a user
US7669235B2 (en) Secure domain join for computing devices

Legal Events

Date Code Title Description
AS Assignment

Owner name: FUJITSU LIMITED, JAPAN

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:KOTANI, SEIGO;SUZUKI, MASATO;REEL/FRAME:035807/0450

Effective date: 20100902

AS Assignment

Owner name: FUJITSU LIMITED, JAPAN

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:KOTANI, SEIGO;SUZUKI, MASATO;REEL/FRAME:038418/0280

Effective date: 20160425

STPP Information on status: patent application and granting procedure in general

Free format text: NON FINAL ACTION MAILED

STCB Information on status: application discontinuation

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