US20130042231A1 - Methods and Apparatus for Software Updating - Google Patents

Methods and Apparatus for Software Updating Download PDF

Info

Publication number
US20130042231A1
US20130042231A1 US13/206,615 US201113206615A US2013042231A1 US 20130042231 A1 US20130042231 A1 US 20130042231A1 US 201113206615 A US201113206615 A US 201113206615A US 2013042231 A1 US2013042231 A1 US 2013042231A1
Authority
US
United States
Prior art keywords
application
version
vcs
applications
compatible
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
US13/206,615
Other languages
English (en)
Inventor
Christopher K. Davey
Rajya Adibhatla
Chad Evert Esselink
Gerald P. Humphreys
Salwan H. Ishac
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.)
Ford Global Technologies LLC
Original Assignee
Ford Global Technologies LLC
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Ford Global Technologies LLC filed Critical Ford Global Technologies LLC
Priority to US13/206,615 priority Critical patent/US20130042231A1/en
Assigned to FORD GLOBAL TECHNOLOGIES, LLC reassignment FORD GLOBAL TECHNOLOGIES, LLC ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: DAVEY, CHRISTOPHER K., ISHAC, SALWAN H., ADIBHATLA, RAJYA, HUMPHREYS, GERALD P., ESSELINK, CHAD EVERT
Priority to DE102012213027A priority patent/DE102012213027A1/de
Priority to CN201210279208.2A priority patent/CN102955708B/zh
Priority to RU2012134261A priority patent/RU2628429C2/ru
Publication of US20130042231A1 publication Critical patent/US20130042231A1/en
Priority to US13/954,194 priority patent/US9626175B2/en
Priority to US15/458,619 priority patent/US10379837B2/en
Abandoned legal-status Critical Current

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/60—Software deployment
    • G06F8/65—Updates
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/60—Software deployment
    • G06F8/61—Installation
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/34—Network arrangements or protocols for supporting network services or applications involving the movement of software or configuration parameters 

Definitions

  • the illustrative embodiments generally relate to a method and apparatus for software updating.
  • PC operating systems often have many updates available. Either to better use existing resources or to optimally use newly available technology, operating system updates can provide an ever improving fundament on which an end-user experience can be built. Whether it is a new operating system entirely, or a version update to an existing system, there are numerous reasons why a user may wish to update an operating system on a PC.
  • a smartphone not only serves as a portable computing device, but it also serves as a platform from which cellular phone calls may be made. Since there is typically a service contract associated with the device, often for both cellular and data transfer services, it is in the best interest of the service provider to ensure that operating system updates are performed on the device as needed.
  • a computer-implemented method includes receiving a restore command to restore a vehicle computing system (VCS) system state.
  • the illustrative method further includes restoring a base system state to a known, functional state and obtaining a list of applications previously installed on the VCS.
  • VCS vehicle computing system
  • the illustrative method also includes for each application previously installed on the VCS, finding a version of the application compatible with the restored base system state. Also, the illustrative method includes installing the version of each application compatible with the restored base system state.
  • a machine readable storage medium stores instructions that, when executed, cause a processor of a vehicle computing system (VCS) to execute a method including receiving a restore command to restore a VCS system state. The method also includes restoring a base system state to a known, functional state and obtaining a list of applications previously installed on the VCS.
  • VCS vehicle computing system
  • the method further includes for each application previously installed on the VCS, finding a version of the application compatible with the restored base system state.
  • the method also includes installing the version of each application compatible with the restored base system state.
  • a system in a third illustrative embodiment, includes a vehicle computing system (VCS) a vehicle computing system (VCS), a diagnostic service tool (DST) and a remote global in-vehicle information system (GIVIS).
  • VCS vehicle computing system
  • VCS vehicle computing system
  • DST diagnostic service tool
  • GIVIS remote global in-vehicle information system
  • the DST is operable to generate a restore command to the GIVIS.
  • the GIVIS upon receiving the restore command, is operable to download and install a known, functional VCS operating system on the VCS. Following installation of the operating system, the VCS is further operable to communicate with the GIVIS to receive, for each application previously installed on the VCS, a most recent version of the application, compatible with the installed operating system. Additionally, the GIVIS is operable to instruct installation each of the most recent versions of the applications compatible with the installed operating system on the VCS.
  • FIG. 1 shows an illustrative example of a vehicle computing system
  • FIG. 2 shows an illustrative example of a software maintenance ecosystem
  • FIG. 3 shows an illustrative example of a software maintenance model
  • FIG. 4 shows an illustrative example of a software update process
  • FIG. 5 shows an illustrative example of a second software update process
  • FIG. 6 shows an illustrative example of a restoration process
  • FIG. 7 shows an illustrative example of an operating system update process.
  • FIG. 1 illustrates an example block topology for a vehicle based computing system 1 (VCS) for a vehicle 31 .
  • VCS vehicle based computing system 1
  • An example of such a vehicle-based computing system 1 is the SYNC system manufactured by THE FORD MOTOR COMPANY.
  • a vehicle enabled with a vehicle-based computing system may contain a visual front end interface 4 located in the vehicle. The user may also be able to interact with the interface if it is provided, for example, with a touch sensitive screen. In another illustrative embodiment, the interaction occurs through, button presses, audible speech and speech synthesis.
  • a processor 3 controls at least some portion of the operation of the vehicle-based computing system.
  • the processor allows onboard processing of commands and routines.
  • the processor is connected to both non-persistent 5 and persistent storage 7 .
  • the non-persistent storage is random access memory (RAM) and the persistent storage is a hard disk drive (HDD) or flash memory.
  • the processor is also provided with a number of different inputs allowing the user to interface with the processor.
  • a microphone 29 an auxiliary input 25 (for input 33 ), a USB input 23 , a GPS input 24 and a BLUETOOTH input 15 are all provided.
  • An input selector 51 is also provided, to allow a user to swap between various inputs. Input to both the microphone and the auxiliary connector is converted from analog to digital by a converter 27 before being passed to the processor.
  • numerous of the vehicle components and auxiliary components in communication with the VCS may use a vehicle network (such as, but not limited to, a CAN bus) to pass data to and from the VCS (or components thereof).
  • Outputs to the system can include, but are not limited to, a visual display 4 and a speaker 13 or stereo system output.
  • the speaker is connected to an amplifier 11 and receives its signal from the processor 3 through a digital-to-analog converter 9 .
  • Output can also be made to a remote BLUETOOTH device such as PND 54 or a USB device such as vehicle navigation device 60 along the bi-directional data streams shown at 19 and 21 respectively.
  • the system 1 uses the BLUETOOTH transceiver 15 to communicate 17 with a user's nomadic device 53 (e.g., cell phone, smart phone, PDA, or any other device having wireless remote network connectivity).
  • the nomadic device can then be used to communicate 59 with a network 61 outside the vehicle 31 through, for example, communication 55 with a cellular tower 57 .
  • tower 57 may be a WiFi access point.
  • Exemplary communication between the nomadic device and the BLUETOOTH transceiver is represented by signal 14 .
  • Pairing a nomadic device 53 and the BLUETOOTH transceiver 15 can be instructed through a button 52 or similar input. Accordingly, the CPU is instructed that the onboard BLUETOOTH transceiver will be paired with a BLUETOOTH transceiver in a nomadic device.
  • Data may be communicated between CPU 3 and network 61 utilizing, for example, a data-plan, data over voice, or DTMF tones associated with nomadic device 53 .
  • the nomadic device 53 can then be used to communicate 59 with a network 61 outside the vehicle 31 through, for example, communication 55 with a cellular tower 57 .
  • the modem 63 may establish communication 20 with the tower 57 for communicating with network 61 .
  • modem 63 may be a USB cellular modem and communication 20 may be cellular communication.
  • the processor is provided with an operating system including an API to communicate with modem application software.
  • the modem application software may access an embedded module or firmware on the BLUETOOTH transceiver to complete wireless communication with a remote BLUETOOTH transceiver (such as that found in a nomadic device).
  • Bluetooth is a subset of the IEEE 802 PAN (personal area network) protocols.
  • IEEE 802 LAN (local area network) protocols include WiFi and have considerable cross-functionality with IEEE 802 PAN. Both are suitable for wireless communication within a vehicle.
  • Another communication means that can be used in this realm is free-space optical communication (such as IrDA) and non-standardized consumer IR protocols.
  • nomadic device 53 includes a modem for voice band or broadband data communication.
  • a technique known as frequency division multiplexing may be implemented when the owner of the nomadic device can talk over the device while data is being transferred. At other times, when the owner is not using the device, the data transfer can use the whole bandwidth (300 Hz to 3.4 kHz in one example). While frequency division multiplexing may be common for analog cellular communication between the vehicle and the internet, and is still used, it has been largely replaced by hybrids of with Code Domian Multiple Access (CDMA), Time Domain Multiple Access (TDMA), Space-Domian Multiple Access (SDMA) for digital cellular communication.
  • CDMA Code Domian Multiple Access
  • TDMA Time Domain Multiple Access
  • SDMA Space-Domian Multiple Access
  • ITU IMT-2000 (3G) compliant standards offer data rates up to 2 mbs for stationary or walking users and 385 kbs for users in a moving vehicle.
  • 3G standards are now being replaced by IMT-Advanced (4G) which offers 100 mbs for users in a vehicle and 1 gbs for stationary users.
  • 4G IMT-Advanced
  • nomadic device 53 is replaced with a cellular communication device (not shown) that is installed to vehicle 31 .
  • the ND 53 may be a wireless local area network (LAN) device capable of communication over, for example (and without limitation), an 802.11g network (i.e., WiFi) or a WiMax network.
  • LAN wireless local area network
  • incoming data can be passed through the nomadic device via a data-over-voice or data-plan, through the onboard BLUETOOTH transceiver and into the vehicle's internal processor 3 .
  • the data can be stored on the HDD or other storage media 7 until such time as the data is no longer needed.
  • USB is one of a class of serial networking protocols.
  • IEEE 1394 firewire
  • EIA Electronics Industry Association
  • IEEE 1284 Chipperability for Microwave Access
  • S/PDIF Synchronization/Philips Digital Interconnect Format
  • USB-IF USB Implementers Forum
  • auxiliary device 65 may include, but are not limited to, personal media players, wireless health devices, portable computers, and the like.
  • the CPU could be connected to a vehicle based wireless router 73 , using for example a WiFi 71 transceiver. This could allow the CPU to connect to remote networks in range of the local router 73 .
  • the exemplary processes may be executed by a computing system in communication with a vehicle computing system.
  • a computing system may include, but is not limited to, a wireless device (e.g., and without limitation, a mobile phone) or a remote computing system (e.g., and without limitation, a server) connected through the wireless device.
  • a wireless device e.g., and without limitation, a mobile phone
  • a remote computing system e.g., and without limitation, a server
  • VACS vehicle associated computing systems
  • particular components of the VACS may perform particular portions of a process depending on the particular implementation of the system.
  • VACS vehicle computing system
  • FIG. 2 shows an illustrative example of a software maintenance ecosystem. This illustrative embodiment shows one non-limiting example of a relationship between a vehicles computing system, consumer devices, dealerships/service centers, OEM assembly and module suppliers.
  • the core of the mobile computing platform is the VCS module 299 .
  • This module represents the current version of the operating system installed on the VCS, and any applications and application versions also installed in the system. Updates to this module, especially to the operating system, should attempt to preserve as much compatibility as possible, so that applications function in the manner in which users expect and avoid being disabled.
  • One point of initial configuration for this module may be the OEM assembly plant 260 .
  • the VCS module 299 may have a variety of software applications installed thereon via, for example, a wireless access point 265 .
  • the wireless access point can receive the particular software “parts” to be installed from the new plant floor system (PFS) 263 .
  • the PFS may receive module software parts from an in-vehicle software (IVS) system 240 , which can also send those parts (or at least record of those parts) to the GIVIS system 220 .
  • IVFS in-vehicle software
  • the VCS module will know it needs one or more software parts corresponding to the navigation system. The module can then request the needed parts from the plant floor system.
  • the VCS module can communicate module details back to the endline system 267 , which can relay those details to an EOLX 261 . This also can serve as confirmation that all software parts were installed successfully.
  • the information can be sent from the EOLX to the GIVIS system 220 , so that a global record of the module details can be had.
  • module suppliers 280 may provide modules for use in conjunction with the VCS module, including security keys for use of particular modules.
  • a Module Supplier Manufacturing (MSM) system 281 may send these modules to the VCS module in an unprovisioned state. Also, the system 281 may send an enhanced supplier feed to a GEC Hub 270 , and the data from this hub can be stored in the GIVIS system to maintain a record of modules/security keys installed for use with the VCS module.
  • MMSM Module Supplier Manufacturing
  • the GIVIS can relay module attributes, such as security keys to an In-Vehicle Security system 230 .
  • System 230 can provide the encryption/decryption functionality for information passing through the GIVIS, and provides an additional layer of security by being one level removed from the GIVIS.
  • a dealership 250 may have an diagnostics tool system 251 provided thereto.
  • This system can provide commands for application install (along with application data) to a USB drive 255 usable by a technician at the dealership to install applications and other software on the VCS module.
  • Record of the installation may be sent over the ODB-II Port 253 to maintain a log of installed applications and/or application versions. Additionally, the ODB-II Port may be used by a technician to restore the VCS module to an unprovisioned state, and further to provision the module, for example, following a restore. Software and/or commands for restoring the module and provisioning the module may come from the diagnostics system, which may also receive a copy of the installation log from the ODB-II Port to relay to the GIVIS. Once all applications have been installed and the module(s) provisioned, a module/application state can be relayed from the vehicle to the GIVIS.
  • Consumer devices namely, in this example, a USB drive 203 receiving data from a consumer PC 201 , may also interact with the VCS module.
  • the consumer PC may have software updates usable/installable on the module, and this data may be sent to a USB drive for installation into the module.
  • the consumer PC may receive this software data from a web portal system 210 , which can be informed of updates from the GIVIS system, which should know a current state of the particular VCS module, at least from tracking installation logs and storing module details.
  • an installation log can be sent from the VCS module to the USB drive, relayed to the home PC, and sent from there to the web portal system. That system can then relay the information to the GIVIS system to maintain a current record of installed software on the VCS module.
  • FIG. 3 shows an illustrative example of a software maintenance model.
  • the GIVIS system 301 cab access an SMR/ENGINE/APA system 305 to determine available versions of applications 308 that may be installed with respect to a VCS module.
  • the GIVIS system may also interface with an IDS/PTS/ETIS/TSI system 303 to provide available applications (e.g., without limitation, versions of free and previously purchased applications) that can be installed with respect to a VCS module. Communication with system 303 may also include a get latest communication.
  • the system determines an installation package with the latest (e.g., without limitation, most up-to-date) version of a software package for a module's latest state.
  • a “free” version of software may be installed, having a first set of features. This will be branch A of a software lineage. Updates may be provided to the software in this version to maintain compliance, and as long as a user elects to maintain the first version of the software, no cost will be incurred.
  • a second “paid” version of the software may also be available, having an additional set of features or enhanced versions of the first set of features. This will be branch B of the software lineage.
  • a “get latest” command may proceed to the end of the branch A lineage, preserving the free state of the software version, while skipping intermittent updates to install the most up-to-date version of the branch.
  • the “get latest” may retrieve the most up-to-date version of that branch.
  • the user may be presented with options to maintain a free version of software or to switch to a paid version of software if both options were available and compatible with a current state of the VCS module.
  • branching may occur to maintain compatibility when a plurality of modules interact with each other.
  • Installation of a certain software application that interacts with other applications may require installation of a new version of applications with which the certain software application interacts.
  • the system may get the latest version of any of these applications that maintained compatibility with the other interacting applications.
  • the system may only get available versions of a particular application that maintains the compatibility with other installed, interacting applications.
  • GIVIS GIVIS System
  • applications, and new versions of applications may be known to an LCS system 307 and notification of these applications may be sent to the GIVIS system.
  • a GIVIS system may determine which applications and versions of applications are appropriate to present based on which command (e.g., get latest, get available, restore, etc.) is being executed.
  • the IVS system may present the actual applications to the GIVIS system.
  • a restore command 302 processed between system 303 and a GIVIS system, will restore the operating state of a VCS module to a known working state or specified version.
  • this may cause incompatibilities with existing software that is installed on the VCS module, so typically a get latest command will be processed in conjunction with a restore command. Processing the get latest command should help ensure that compatible versions of all existing software are then obtained and installed on the newly restored VCS module, and functionality with respect to the restored state should be maintained.
  • FIG. 4 shows an illustrative example of a software update process.
  • a request is made for a latest version of an operating system, application, BIOS, etc. 401 .
  • Software applications for example, often have a lineage associated therewith.
  • the version number of the software may determine where in the lineage the particular version lies, what the initial software was, what configuration or update decisions have been made, and what future versions or updates are available and compatible with that version.
  • lineages branch based on configurations and installed features, and lineages forward from that point may continue down a particular branch, corresponding to the previously installed version.
  • the forward lineage of existing software is ignored 403 . That is, a “next” version of the software will not be installed, nor will any updates along the lineage between a current lineage location and the end of a branch. Instead, the process proceeds to the end of an existing branch and finds the latest version of the software compatible with the module and installs that version 405 .
  • FIG. 5 shows an illustrative example of a second software update process.
  • a request is made for available updates to a module 501 .
  • a list of all free applications 503 and previously purchased applications 505 is compiled and provided to a user 507 . The user can then peruse the list and select which applications and versions of those applications should be installed on the module.
  • a user may elect a certain version of software with a get available command, and then further execute a get latest command to ensure the latest, compatible form of the selected version is installed on a mobile computing system.
  • FIG. 6 shows an illustrative example of a restoration process.
  • the process will first get the latest version of an operating system and/or BIOS for installation 401 , 403 , 405 .
  • the process will then find all free and purchased applications that were previously installed on the VCS 501 , 503 , 505 . Instead of presenting these as options for a user, however, a get latest command may be performed with respect to each discovered available application that corresponds to a previously installed application. Thus, based on the newly restored operating system/BIOS state, the system will install the latest, compatible versions of all previously installed applications. These applications may be double-checked for compatibility and installed in the event that they are compatible with the OS/BIOS installed in response to the restoration request 603 .
  • the system will report the incompatibilities to the user 605 so that the user is aware that those applications may not function on the new system.
  • FIG. 7 shows an illustrative example of an operating system update process.
  • an update to the operating system is detected 701 . Because incompatibilities may exist with installed applications, it is determined if any existing applications are installed on the mobile computing platform 703 .
  • At least one un-verified application exists 703 that application is checked by the process 705 to ensure compatibility 707 .
  • the provider of this process will know which versions of applications are compatible with which versions of operating systems, and the application version number can be used to determine compatibility of that application.
  • the process determines if a compatible version of the application is available 709 .
  • This version could correspond to a next version of an application, or could be a version that is somewhere further down a lineage from the current version of the installed application.
  • the compatible version may be downloaded to the platform at this point 711 .
  • This version could correspond to a first compatible version of the application, or it could correspond to a more recently available version of the application, beyond a point of first compatibility. In this manner, users can not only be provided with a compatible version, but they can be provided with the most up-to-date version of the application which is compatible.
  • the new version of the application is then installed on the platform 713 and the process continues checking for incompatible applications.
  • an application is incompatible 707 and no compatible version of the application exists 709 , the user may be informed that the particular application has no known compatible version, and will be disabled at least temporarily. It may then be possible for the user to check for future compatible versions or for the process itself to periodically check for compatible versions.
  • system configurations may be stored remotely, and upon the development of a compatible version of an application, all systems previously having that application disabled may be notified of the new version, or even have the new version automatically installed thereon.

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Physics & Mathematics (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Medical Informatics (AREA)
  • General Health & Medical Sciences (AREA)
  • Computing Systems (AREA)
  • Health & Medical Sciences (AREA)
  • Stored Programmes (AREA)
  • Mechanical Engineering (AREA)
  • Information Transfer Between Computers (AREA)
US13/206,615 2011-08-10 2011-08-10 Methods and Apparatus for Software Updating Abandoned US20130042231A1 (en)

Priority Applications (6)

Application Number Priority Date Filing Date Title
US13/206,615 US20130042231A1 (en) 2011-08-10 2011-08-10 Methods and Apparatus for Software Updating
DE102012213027A DE102012213027A1 (de) 2011-08-10 2012-07-25 Verfahren und vorrichtungen zur softwareaktualisierung
CN201210279208.2A CN102955708B (zh) 2011-08-10 2012-08-07 软件更新的方法和装置
RU2012134261A RU2628429C2 (ru) 2011-08-10 2012-08-10 Система обновления программного обеспечения транспортного средства
US13/954,194 US9626175B2 (en) 2011-08-10 2013-07-30 Method and apparatus for software updating
US15/458,619 US10379837B2 (en) 2011-08-10 2017-03-14 Methods and apparatus for software updating

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
US13/206,615 US20130042231A1 (en) 2011-08-10 2011-08-10 Methods and Apparatus for Software Updating

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US13/954,194 Continuation US9626175B2 (en) 2011-08-10 2013-07-30 Method and apparatus for software updating

Publications (1)

Publication Number Publication Date
US20130042231A1 true US20130042231A1 (en) 2013-02-14

Family

ID=47595761

Family Applications (3)

Application Number Title Priority Date Filing Date
US13/206,615 Abandoned US20130042231A1 (en) 2011-08-10 2011-08-10 Methods and Apparatus for Software Updating
US13/954,194 Active 2032-04-17 US9626175B2 (en) 2011-08-10 2013-07-30 Method and apparatus for software updating
US15/458,619 Active 2031-08-13 US10379837B2 (en) 2011-08-10 2017-03-14 Methods and apparatus for software updating

Family Applications After (2)

Application Number Title Priority Date Filing Date
US13/954,194 Active 2032-04-17 US9626175B2 (en) 2011-08-10 2013-07-30 Method and apparatus for software updating
US15/458,619 Active 2031-08-13 US10379837B2 (en) 2011-08-10 2017-03-14 Methods and apparatus for software updating

Country Status (4)

Country Link
US (3) US20130042231A1 (zh)
CN (1) CN102955708B (zh)
DE (1) DE102012213027A1 (zh)
RU (1) RU2628429C2 (zh)

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20140066015A1 (en) * 2012-08-28 2014-03-06 Selim Aissi Secure device service enrollment
US20160113043A1 (en) * 2014-10-15 2016-04-21 Lear Corporation Vehicle Gateway Module Configured to Provide Wireless Hotspot
US20170061708A1 (en) * 2015-08-27 2017-03-02 Hyundai Motor Company Method, apparutus and system for managing vehicle interlock application
US10140110B2 (en) * 2014-04-02 2018-11-27 Ford Global Technologies, Llc Multiple chunk software updates
US10620937B1 (en) * 2018-06-01 2020-04-14 Appian Corporation Automated backward-compatible function updates
CN113805927A (zh) * 2020-06-11 2021-12-17 中移(苏州)软件技术有限公司 一种代码更新方法、装置、电子设备及计算机存储介质

Families Citing this family (18)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20140245278A1 (en) * 2013-02-22 2014-08-28 Panasonic Automotive Systems Company Of America, Division Of Panasonic Corpor Automotive component self update via software version control
US9201933B2 (en) * 2014-04-01 2015-12-01 BizDox, LLC Systems and methods for documenting, analyzing, and supporting information technology infrastructure
US9086941B1 (en) * 2014-05-29 2015-07-21 Massachusetts Institute Of Technology System and method for providing predictive software upgrades
US20160117161A1 (en) * 2014-10-27 2016-04-28 Microsoft Corporation Installing and updating software systems
CN104346844B (zh) * 2014-10-28 2018-04-10 深圳市华宝电子科技有限公司 一种行驶记录仪升级信息的调用方法及装置
US10118592B2 (en) * 2015-08-04 2018-11-06 Ford Global Technologies, Llc Diagnostic port protection to body control module
JP6697357B2 (ja) * 2016-09-15 2020-05-20 株式会社日立製作所 ソフトウェア更新システム
WO2018113298A1 (zh) * 2016-12-24 2018-06-28 华为技术有限公司 一种提示用户更新应用版本的方法及设备
CN106951283A (zh) * 2017-03-13 2017-07-14 广州视源电子科技股份有限公司 一种利用移动端协助pc端进行软件更新的系统及方法
CN107479926A (zh) * 2017-08-10 2017-12-15 青岛海信移动通信技术股份有限公司 系统自带应用程序的升级方法及装置
DE102017216849A1 (de) * 2017-09-22 2019-03-28 Siemens Mobility GmbH Softwareverteilungsverfahren und Softwareverteilungssystem für ein spurgebundenes Fahrzeug, Konfigurationsserver-Einheit und spurgebundenes Fahrzeug
JP6859282B2 (ja) * 2018-02-20 2021-04-14 パナソニック株式会社 電子機器、プログラム更新方法およびコンピュータプログラム
JP7183984B2 (ja) * 2018-08-10 2022-12-06 株式会社デンソー センター装置，車両情報通信システム，配信パッケージ送信方法及び配信パッケージの送信プログラム
US11356425B2 (en) 2018-11-30 2022-06-07 Paccar Inc Techniques for improving security of encrypted vehicle software updates
US11449327B2 (en) 2018-11-30 2022-09-20 Paccar Inc Error-resilient over-the-air software updates for vehicles
RU2738865C1 (ru) * 2020-03-13 2020-12-17 АКЦИОНЕРНОЕ ОБЩЕСТВО "ИнфоВотч" Способ оценки совместимости средств защиты информации и автоматизированных систем управления технологическими процессами для проектирования систем безопасности объектов критической информационной инфраструктуры
CN112181456A (zh) * 2020-09-24 2021-01-05 上海仙塔智能科技有限公司 整车版本管理方法、系统及计算机存储介质
CN114237734A (zh) * 2021-11-23 2022-03-25 芯发威达电子(上海)有限公司 计算机启动软体自我保护方法、系统、终端以及存储介质

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20030167354A1 (en) * 2002-03-01 2003-09-04 Dell Products L.P. Method and apparatus for automated operating systems upgrade
US20070168957A1 (en) * 2005-11-08 2007-07-19 Red Hat, Inc. Certifying a software application based on identifying interface usage
US20080005733A1 (en) * 2006-06-29 2008-01-03 Balaji Ramachandran Method and apparatus for updating firmware and software
US20110078675A1 (en) * 2009-09-25 2011-03-31 Fisher-Rosemount Systems, Inc. Automated Deployment of Computer-Specific Software Updates
US20120144378A1 (en) * 2010-12-06 2012-06-07 Red Hat, Inc. Methods for managing software packages using a version control system

Family Cites Families (38)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8209120B2 (en) 1997-10-22 2012-06-26 American Vehicular Sciences Llc Vehicular map database management techniques
US7917628B2 (en) 1999-12-02 2011-03-29 Western Digital Technologies, Inc. Managed peer-to-peer applications, systems and methods for distributed data access and storage
US7089552B2 (en) * 2002-08-29 2006-08-08 Sun Microsystems, Inc. System and method for verifying installed software
EP1445165B1 (de) 2003-02-08 2006-03-08 Jungheinrich Aktiengesellschaft Deichsel für einen Handgabelhubwagen
US20040187011A1 (en) 2003-03-18 2004-09-23 Lee Long K. Prevention of unauthorized software distribution
US7634770B2 (en) * 2003-05-19 2009-12-15 Hewlett-Packard Development Company, L.P. Kernel module interface dependencies
US7810088B2 (en) 2003-06-20 2010-10-05 Samsung Electronics Co., Ltd. Apparatus and method for performing a fail-safe over-the-air software update in a mobile station
DE10340372A1 (de) * 2003-09-02 2005-03-24 Robert Bosch Gmbh Verfahren zur Installation einer Programmkomponente
US7420954B2 (en) 2004-01-13 2008-09-02 General Motors Corporation Efficient lightweight information dissemination algorithm for mobile wireless ad hoc networks
US20050216902A1 (en) 2004-03-23 2005-09-29 General Motors Corporation Method and system for vehicle software configuration update management
US7506309B2 (en) 2004-03-23 2009-03-17 General Motors Corporation Method for managing vehicle software configuration updates
DE102004017602B4 (de) 2004-04-07 2022-03-17 Volkswagen Ag Verfahren und Anordnung für ein Kommunikationsnetz mit direkter Fahrzeug-Fahrzeug Kommunikation
US7366589B2 (en) 2004-05-13 2008-04-29 General Motors Corporation Method and system for remote reflash
US7676804B2 (en) * 2004-05-20 2010-03-09 Caterpillar Inc. Systems and method for remotely modifying software on a work machine
CN100340982C (zh) * 2005-03-03 2007-10-03 中兴通讯股份有限公司 一种传输设备单板软件在线升级出错后的恢复方法
CN100391291C (zh) * 2005-08-10 2008-05-28 华为技术有限公司 一种数据备份和恢复方法及其系统
KR100750132B1 (ko) 2005-09-27 2007-08-21 삼성전자주식회사 부팅, 소프트웨어 자동 업데이트 및 에러 복원 방법과 그시스템, 그 방법을 기록한 컴퓨터 판독 가능한 기록매체
US20070185624A1 (en) 2006-02-07 2007-08-09 General Motors Corporation Method for remote reprogramming of vehicle flash memory
RU2445578C2 (ru) * 2006-03-08 2012-03-20 Томтом Интернэшнл Б.В. Способ и устройство для использования выбираемой адресной метки для относительного отображения элементов списка интересующих точек
US8726267B2 (en) * 2006-03-24 2014-05-13 Red Hat, Inc. Sharing software certification and process metadata
US20070241152A1 (en) 2006-04-17 2007-10-18 Josephs Robert L Beverage cooler / heater
US7848278B2 (en) 2006-10-23 2010-12-07 Telcordia Technologies, Inc. Roadside network unit and method of organizing, managing and maintaining local network using local peer groups as network groups
WO2008085201A2 (en) * 2006-12-29 2008-07-17 Prodea Systems, Inc. Managed file backup and restore at remote storage locations through multi-services gateway device at user premises
US20080301667A1 (en) * 2007-05-30 2008-12-04 Google Inc. Dynamically Updating Software Applications on a Device
DE102008036986A1 (de) 2007-08-29 2009-03-05 Continental Teves Ag & Co. Ohg Verfahren und Einrichtung zur Anpassung eines Fahrdynamiksystems in einem Kraftfahrzeug
US8209678B2 (en) * 2007-09-17 2012-06-26 Sony Corporation System, apparatus, and method for an upgrader module
US20090260004A1 (en) * 2008-04-10 2009-10-15 Palm, Inc. Computer program updates for mobile computing device
US9461827B2 (en) 2008-04-11 2016-10-04 Toyota Motor Engineering & Manufacturing North America, Inc. Method for distributing a list of certificate revocations in a vanet
US8418168B2 (en) * 2008-05-29 2013-04-09 Research In Motion Limited Method and system for performing a software upgrade on an electronic device connected to a computer
US20090307682A1 (en) * 2008-06-08 2009-12-10 Sam Gharabally Techniques for Acquiring Updates for Application Programs
US8892699B2 (en) * 2008-12-31 2014-11-18 Schneider Electric USA, Inc. Automatic firmware updates for intelligent electronic devices
US9417865B2 (en) * 2010-05-28 2016-08-16 Red Hat, Inc. Determining when to update a package manager software
US9672022B2 (en) * 2010-06-23 2017-06-06 Microsoft Technology Licensing, Llc Applications including multiple experience modules
US9464905B2 (en) * 2010-06-25 2016-10-11 Toyota Motor Engineering & Manufacturing North America, Inc. Over-the-air vehicle systems updating and associate security protocols
US8713559B2 (en) * 2010-11-15 2014-04-29 Schneider Electric It Corporation System and method for updating firmware
US8607040B2 (en) * 2010-11-16 2013-12-10 Intel Corporation Method of provisioning firmware in an operating system (OS) absent services environment
JP5800685B2 (ja) * 2010-11-26 2015-10-28 キヤノン株式会社 情報処理装置及びサーバ、制御方法、プログラム及び記録媒体
US9557981B2 (en) 2011-07-26 2017-01-31 Ford Global Technologies, Llc Method and apparatus for automatic module upgrade

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20030167354A1 (en) * 2002-03-01 2003-09-04 Dell Products L.P. Method and apparatus for automated operating systems upgrade
US20070168957A1 (en) * 2005-11-08 2007-07-19 Red Hat, Inc. Certifying a software application based on identifying interface usage
US8332817B2 (en) * 2005-11-08 2012-12-11 Red Hat, Inc. Certifying a software application based on identifying interface usage
US20080005733A1 (en) * 2006-06-29 2008-01-03 Balaji Ramachandran Method and apparatus for updating firmware and software
US20110078675A1 (en) * 2009-09-25 2011-03-31 Fisher-Rosemount Systems, Inc. Automated Deployment of Computer-Specific Software Updates
US20120144378A1 (en) * 2010-12-06 2012-06-07 Red Hat, Inc. Methods for managing software packages using a version control system

Cited By (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20140066015A1 (en) * 2012-08-28 2014-03-06 Selim Aissi Secure device service enrollment
US9867043B2 (en) * 2012-08-28 2018-01-09 Visa International Service Association Secure device service enrollment
US10140110B2 (en) * 2014-04-02 2018-11-27 Ford Global Technologies, Llc Multiple chunk software updates
US20160113043A1 (en) * 2014-10-15 2016-04-21 Lear Corporation Vehicle Gateway Module Configured to Provide Wireless Hotspot
US20170061708A1 (en) * 2015-08-27 2017-03-02 Hyundai Motor Company Method, apparutus and system for managing vehicle interlock application
US10620937B1 (en) * 2018-06-01 2020-04-14 Appian Corporation Automated backward-compatible function updates
US11237818B1 (en) 2018-06-01 2022-02-01 Appian Corporation Automated backward-compatible function updates
US11836477B1 (en) 2018-06-01 2023-12-05 Appian Corporation Automated backward-compatible function updates
CN113805927A (zh) * 2020-06-11 2021-12-17 中移(苏州)软件技术有限公司 一种代码更新方法、装置、电子设备及计算机存储介质

Also Published As

Publication number Publication date
US20130318517A1 (en) 2013-11-28
RU2012134261A (ru) 2014-02-20
CN102955708A (zh) 2013-03-06
US10379837B2 (en) 2019-08-13
DE102012213027A1 (de) 2013-02-14
CN102955708B (zh) 2018-06-05
RU2628429C2 (ru) 2017-08-16
US20170185391A1 (en) 2017-06-29
US9626175B2 (en) 2017-04-18

Similar Documents

Publication Publication Date Title
US10379837B2 (en) Methods and apparatus for software updating
US10061574B2 (en) Method and apparatus for multiple vehicle software module reflash
US10402184B2 (en) Module interface for vehicle updates
US11782691B2 (en) Method and apparatus for over the air updates
CN105791387B (zh) 车辆控制更新方法和系统
US10140109B2 (en) Silent in-vehicle software updates
US9557981B2 (en) Method and apparatus for automatic module upgrade
US20150363210A1 (en) Vehicle download by remote mobile device
US20140052330A1 (en) Methods and Apparatus for Vehicle Computing System Software Updates
US10416985B2 (en) Method and apparatus for multi cycle vehicle software update compliance handling
US9361090B2 (en) Apparatus and method of software implementation between a vehicle and mobile device
US20150095898A1 (en) Method and Apparatus for Tailored Wireless Module Updating
US20150331686A1 (en) Over-the-air vehicle issue resolution
US20150347326A1 (en) Method and Apparatus for Dynamically Updating a Vehicle Module Configuration Record
CN105045608A (zh) 用于管理车辆计算系统中的软件更新的系统和方法
US10002082B2 (en) Method and apparatus for cyclical key-off file replacement
US20180351557A1 (en) Method and apparatus for dynamic electronic control unit reconfiguration
US20180124664A1 (en) Method and apparatus for triggered telematics carrier swap
CN107205233B (zh) 用于蜂窝订阅绑定的方法和设备
US20140281756A1 (en) Method and apparatus for tracking device interaction information
US9654936B2 (en) Method and apparatus for normalizing navigation data for vehicle computing system playback
CN106293324B (zh) 用于传送移动装置锁定图标的车辆计算系统和方法
US20200004524A1 (en) Method and apparatus for confirming status of a remote update
US20140280451A1 (en) Method and Apparatus for Mobile Device Connectivity Compatibility Facilitation

Legal Events

Date Code Title Description
AS Assignment

Owner name: FORD GLOBAL TECHNOLOGIES, LLC, MICHIGAN

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:DAVEY, CHRISTOPHER K.;ADIBHATLA, RAJYA;ESSELINK, CHAD EVERT;AND OTHERS;SIGNING DATES FROM 20110712 TO 20110722;REEL/FRAME:026725/0945

STCB Information on status: application discontinuation

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