CN106484456A - For installing method and the subsystem of software upgrading in vehicle - Google Patents
For installing method and the subsystem of software upgrading in vehicle Download PDFInfo
- Publication number
- CN106484456A CN106484456A CN201610724052.2A CN201610724052A CN106484456A CN 106484456 A CN106484456 A CN 106484456A CN 201610724052 A CN201610724052 A CN 201610724052A CN 106484456 A CN106484456 A CN 106484456A
- Authority
- CN
- China
- Prior art keywords
- baseline
- vehicle
- client
- control device
- rollback
- 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.)
- Granted
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements 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/44—Arrangements for executing specific programs
- G06F9/445—Program loading or initiating
-
- 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
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/14—Error detection or correction of the data by redundancy in operation
- G06F11/1402—Saving, restoring, recovering or retrying
- G06F11/1415—Saving, restoring, recovering or retrying at system level
- G06F11/1433—Saving, restoring, recovering or retrying at system level during software upgrading
Abstract
The present invention relates to for method and the subsystem of installing software upgrading in vehicle.For installing the method for software upgrading in vehicle it is characterised in that following characteristics:Determine the control device involved by target baseline of the target baseline related to software upgrading and vehicle in the first step and at least one of the control device involved by target baseline control device is updated according to described target baseline, if first step failure, then determine original baseline and the control device involved by original baseline in the second step and at least one of the control device involved by original baseline control device is updated according to original baseline, and if second step failure, in third step, then determine at least one the rollback baseline between original baseline and target baseline and the control device involved by rollback baseline and at least one of the control device involved by rollback baseline control device is updated according to rollback baseline.
Description
Technical field
The present invention relates to the method for installing software upgrading in vehicle.In addition, the present invention relates to being used for vehicle
Corresponding subsystem and corresponding vehicle.
Background technology
In radiotechnics, data is by means of electromagnetic wave, i.e. obviously by medium air(over the air(Empty
In), OTA)Transmission be sometimes referred to as air interface.The feature of this air interface in particular, in that, do not use the transmission of solid
Medium, such as copper or fiber optic cables, this is not excluded for the transmission in vacuum for the purpose of subsequent enforcement.Using this transmission
Telecommunication technology scheme for example programs as aerial(OTA), Air Service provide(Over-the-Air Service
Provisioning, OTASP), aerial provide(Over-the-Air Provisioning, OTAP)Or aerial parameter management
(Over-the-Air Parameter Administration, OTAPA)Known.
The technology being previously mentioned is for the so-called firmware of renewal(FW), be embedded in this software in electronic equipment(SW)
It is especially interesting.The modification being adapted according to firmware of OTA technology mentioned above is in telecommunications with upper general
Read " Firmware Over programming(FOTA)" summarized.
DE 10105454 A1 proposes the method for automatically to supplement software via air interface, and methods described is used for
Replenished by new software module in system run software, wherein these software modules tested first and and then from
Application module is derived in these software modules.
Content of the invention
The present invention is provided according to independent claims for installing the method for software upgrading in vehicle, for vehicle
Corresponding subsystem and the vehicle with this subsystem.
The advantage of this solution is algorithm described in vehicle to the problem during renewal process as far as possible
Intelligently react and the ability using so-called baseline optimum respectively.Latter concept is in software configuration management
(Software configuration management, SCM)In be understood to dispensing unit here:Corresponding by it
Firmware or software module defined in version set, described dispensing unit is marked as due to its mutual dependency
Supporting.Can be in founder typically original equipment manufacturer for this(original equipment
Manufacturer, OEM)Or service provider side generates corresponding data.Correspondingly, for this indicate relevant
Mechanism in technical term as " determining baseline(Baselining)" or also serve as known to " labelling ".
It is proposed that following system, described system realizes flexible and dynamic process in case of a fault.The program
Advantage is to find " optimum " resolution policy in the case that the OTA of failure updates.In this context " optimum " meaning
The balance as well as possible of cost, consuming and customer experience.This strategy allows partly or complete in OTA-SW/FW renewal
Still re-establish the original state of vehicle in the case of full failure or at least re-establish the state being protected of vehicle.
Here, the present invention based on the recognition that:If in a control device(electronic control unit(Electricity
Sub-control unit), ECU)The renewal process failure at place, then it is inadequate for this control device being placed in " old " state;More true
Say with cutting and need to reset all control devices being connected with this control device via baseline.This so-called rollback(Rollback)
Known from data base theory to those skilled in the art.Described rollback is there used for avoiding in transaction system not
Unanimously, described transaction system is fully introduced back in the state before affairs start by rollback.
It is proposed that defining other baseline, described baseline means a small amount of fringe cost, especially testing cost, but
Realize rollback step by step.These baselines that are additional, being preferably graded under the viewpoint of renewal process as sane as possible exist
It is referred to below as " rollback baseline ".The baseline of the type provides vehicle can also have no problem ground and safely in road traffic
The middle chance being moved.
By measure mentioned in the dependent claims, the basic conception illustrated by independent claims favourable
Improvement project and improving countermeasure be possible.Therefore it can be stated that being configured for implementing vehicle of proposed method
System includes following characteristics:Via air interface be connected with the device management server of rear end for switching equipment information, car
Information and the facility management client of diagnostic message and software update information, via the download service of air interface and rear end
Device connect for software upgrading being downloaded to the download client vehicle from rear end, download the use that is connected of client with described
The software upgrading client that updates in application software and with download that client and software upgrading client be connected for determining
The vehicle replacement client of rollback baseline.The advantage of this embodiment is it not only in rear end side but also in vehicle side
Modularity.This realization is easily integrated the specific variant of OEM, because feature is mutually separated in architecture level.Vehicle
The assembly here updating client can be in vehicle range(fahrzeugweit)It is responsible for all of renewal process and rollback process.
Therefore, this assembly is in the tram for the function according to the present invention.
Brief description
The embodiments of the invention shown in the drawings and enforcement of the present invention is explained further in the description that follows
Example.
Fig. 1 illustrates to be suitable to the framework updating via the FW/SW of air interface.
Fig. 2 schematically shows the rollback baseline between two kinds of states being protected.
The flow chart that Fig. 3 illustrates the method according to one embodiment of the present invention.
Specific embodiment
Fig. 1 illustrates a kind of system, and subsystem belonging to rear end 20 and vehicle 10 for the described system is constituted.Described system
Core is made up of the assembly being described below and its interaction.
Data is downloaded and is separated in assembly, described assembly be not only implemented as download server 21 in rear end 20 but also
It is implemented as the download client 11 in vehicle 10.Equipment control is separated in assembly, after described assembly is not only implemented as
Hold the device management server 26 in 20 and be implemented as the equipment control client with affiliated agency 15 in vehicle 10
End 16.The agency of vehicle side is used for being bundled into the equipment control such as distributed implementation in multiple domains
Unique implementation.Software upgrading and software management are separated in assembly, and described assembly is not only implemented as in rear end 20
SCOS server 22 and FCOS server 23 and be implemented as application software in vehicle 10 and update client 12 and firmware
Update client 13.
Vehicle management portion 25 is used for making " equipment " to be embodied as vehicle 10, including the topology of its correlation, i.e. control device and
Subsystem.
Separated in vehicle content management department 28 in the data processing of the specialty of rear end 20 side, described vehicle content management
The different version of data mode and variant are tied on vehicle 10 in portion.More new logic including motor control is also divided
Open, described more new logic is not only implemented as the vehicle replacement server 24 with Data Management Department 27 but also quilt in rear end 20
It is embodied as the vehicle replacement client 14 in vehicle 10.
Data management in vehicle 10 is separated as Content Management portion 18.Corresponding content is be applied in order to vehicle 10
ECU update and separated firmware more New Parent, described firmware more New Parent may reside in multiple variants and entity, such as
Application software updates client 12 or firmware and updates in that variant of client 13 and entity and can update
System and technology.
The example of Fig. 2 illustrates the rollback baseline 47 between the original baseline 46 being protected and target baseline 48, described time
Rolling baseline can be used in the case of target baseline 48 failure.This rollback baseline 47 may mean that for driver
Loss functionally, the inefficacy of such as comfortable function.Accurately definition and involved control device 51,52,53,54,55,56
And its dependency is related with function, therefore can not generally effectively be described.
In the present embodiment, currently proposed following rule set(Regelsatz):
First rollback level is defined as follows baseline, and described baseline continuation guarantee vehicle safety, i.e. vehicle 10 can be moved.Involved
And comfortable function can be not in action.Therefore, user/driver can also incite somebody to action in the case of not having outside help
Vehicle 10 moves to workshop or also can use described vehicle in an emergency situation.
Second rollback level is also defined as follows baseline, and described baseline continues to ensure vehicle safety, that is, vehicle 10 can be moved
Dynamic.However, defined additional function, as ABS can be not in action here.
3rd rollback level constitutes following baseline now, and described baseline ensures vehicle safety in restricted mode, i.e. car
10 can also be moved here.However, determine basic function be run in emergency operation, such as actuating device.
4th rollback level is finally constituted following baseline, and described baseline does not ensure vehicle safety, and that is, vehicle 10 can not be moved
Dynamic.However, diagnosis, especially remote diagnosis are possible.
The principle that impact minimizes, the scheme proposing in handling failure time stage are followed in this proposal.Content Management portion 18
For this knowledge is incorporated in vehicle 10.Knowledge and the definition of rollback baseline 47 deposited by this shown assembly in FIG.This
Can be technically as relational database or in file system(file system)In carry out.
In order to identify rollback situation, the method 30 inquired into according to Fig. 3 from now on is proposed:First step 31 determines
(35)The control device 51 involved by target baseline 48 of the target baseline 48 related to software upgrading and vehicle 10,52,53,
54.Then, the control device 51,52,53,54,55,56 involved by target baseline 48 is updated respectively according to target baseline 48
(36)To version V3.0, V2.0, V4.0 and V3.0.
If the failure of this first step 31(37), then determine in second step 32(38)Original baseline 46 and by original
Control device 51,52,53,54 involved by baseline 46.Hereafter, the control device 51 involved by original baseline 46,52,53,
54 are updated respectively according to original baseline 46(39)To version V1.0, V1.0, V2.0 and V2.0.
If present second step 32 also fails(40), then determine in the third step 33(41)Rollback baseline 47 and by
Control device 51,52,53,54 involved by rollback baseline 47 and the control device 51 at least involved by rollback baseline 47,
53 are updated respectively according to rollback baseline 47(42)To version V2.0 and V3.0.
If the failure of last third step 33 itself(43), then collect in four steps 34 with regard to step 31,32,33
Record and the information 44 with regard to vehicle 10 and its control device 51,52,53,54,55,56.Based on collected information 44 to car
10 driver and rear end 20 send Trouble Report 45.
Claims (10)
1. it is used in vehicle(10)The middle method installing software upgrading(30)It is characterised in that following characteristics:
- in first step(31)Middle determination(35)The target baseline related to described software upgrading(48)And described vehicle
(10)By described target baseline(48)Involved control device(51、52、53、54、55、56)And according to described target base
Line(48)Update(36)By described target baseline(48)Involved control device(51、52、53、54、55、56)In at least one
Individual control device(51、52、53、54、55、56),
If-described first step(31)Failure(37), then in second step(32)Middle determination(38)Original baseline(46)And
By described original baseline(46)Involved control device(51、52、53、54、55、56)And according to described original baseline(46)
Update(39)By described original baseline(46)Involved control device(51、52、53、54、55、56)At least one of control
Equipment(51、52、53、54、55、56), and
If-described second step(32)Failure(40), then in third step(33)Middle determination(41)Described original baseline(46)
With described target baseline(48)Between at least one rollback baseline(47)And by described rollback baseline(47)Involved control
Control equipment(51、52、53、54、55、56)And according to described rollback baseline(47)Update(42)By described rollback baseline(47)Institute
The control device being related to(51、52、53、54、55、56)At least one of control device(51、52、53、54、55、56).
2. method according to claim 1(30),
It is characterized in that following characteristics:
If-described third step(33)Failure(43), then in four steps(34)Middle collection is with regard to step above(31、
32、33)Record and with regard to described vehicle(10), especially with respect to described control device(51、52、53、54、55、56)Letter
Breath(44).
3. method according to claim 2(30)
It is characterized in that following characteristics:
- based on collected information(44)To described vehicle(10)Driver and with described vehicle(10)The rear end connecting
(20)Send Trouble Report(45).
4. it is used for vehicle(10)Subsystem, described subsystem is configured for implementing method according to claim 3
(30).
5. subsystem according to claim 4,
It is characterized in that following characteristics:
- via air interface(29)With rear end(20)Device management server(26)Connect for switching equipment information, car
Information and the facility management client of diagnostic message and software update information(16),
- via described air interface(29)With described rear end(20)Download server(21)Connect for by software upgrading
From described rear end(20)Download to described vehicle(10)In download client(11),
- and described download client(11)The software upgrading client for applying described software upgrading connecting(12、13),
And
- and described download client(11)With described software upgrading client(12、13)Connect for determining rollback baseline
(47)Vehicle replacement client(14).
6. subsystem according to claim 5,
It is characterized in that following characteristics:
- at least one content memorizer for storing described software upgrading(17), and
- and described download client(11), described software upgrading client and described vehicle replacement client(14)The use connecting
In the described content memorizer of management(17)With described rollback baseline(47)Content Management portion(18).
7. subsystem according to claim 6,
It is characterized in that following characteristics:
- and described Content Management portion(18)Connect be used for deposit described rollback baseline(47)Data base, this data base is preferred
Ground is relational database.
8. subsystem according to claim 6,
It is characterized in that following characteristics:
- and described Content Management portion(18)Connect be used for deposit described rollback baseline(47)File system.
9. the subsystem according to one of claim 5 to 8,
It is characterized in that following characteristics:
- described software upgrading client includes at least one application software and updates client(12)Update with least one firmware
Client(13).
10. vehicle(10), described vehicle has the subsystem according to one of claim 4 to 9.
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
DE102015216265.6 | 2015-08-26 | ||
DE102015216265.6A DE102015216265A1 (en) | 2015-08-26 | 2015-08-26 | Method and subsystem for installing a software update in a vehicle |
Publications (2)
Publication Number | Publication Date |
---|---|
CN106484456A true CN106484456A (en) | 2017-03-08 |
CN106484456B CN106484456B (en) | 2021-07-27 |
Family
ID=58011159
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CN201610724052.2A Active CN106484456B (en) | 2015-08-26 | 2016-08-25 | Method and subsystem for installing software updates in a vehicle |
Country Status (3)
Country | Link |
---|---|
KR (1) | KR102639949B1 (en) |
CN (1) | CN106484456B (en) |
DE (1) | DE102015216265A1 (en) |
Cited By (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN108804254A (en) * | 2017-05-04 | 2018-11-13 | 沃尔沃汽车公司 | Method and system for troubleshooting during vehicle medium-long range installation software |
CN109144550A (en) * | 2018-09-03 | 2019-01-04 | 北京新能源汽车股份有限公司 | A kind of data processing method, apparatus and system |
CN110278543A (en) * | 2019-06-27 | 2019-09-24 | 奇瑞汽车股份有限公司 | Control system update method, device and the storage medium of automobile |
CN110399146A (en) * | 2018-04-24 | 2019-11-01 | 通用汽车环球科技运作有限责任公司 | Polyelectron control unit wirelessly update in partial fault rollback recovery |
CN113227968A (en) * | 2021-03-31 | 2021-08-06 | 华为技术有限公司 | Version management method and device |
Families Citing this family (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
DE102018211364A1 (en) * | 2018-07-10 | 2020-01-16 | Bayerische Motoren Werke Aktiengesellschaft | Method of resetting a vehicle, method of operating a vehicle and system for a vehicle |
GB2576729B (en) | 2018-08-29 | 2023-02-01 | Jaguar Land Rover Ltd | Installing application program code on a vehicle control system |
KR102610730B1 (en) * | 2018-09-05 | 2023-12-07 | 현대자동차주식회사 | Apparatus for providing update of vehicle and computer-readable storage medium |
DE102019131087A1 (en) * | 2019-11-18 | 2021-05-20 | Audi Ag | Software installation in vehicle control units |
Citations (10)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
DE10105454A1 (en) * | 2001-02-07 | 2002-08-29 | Bosch Gmbh Robert | Procedure for the automatic addition of software |
US20050223374A1 (en) * | 2002-06-21 | 2005-10-06 | Koninklijke Philips Electronics N.V. | Server side configuration management |
US20090100421A1 (en) * | 2007-10-10 | 2009-04-16 | Microsoft Corporation | Transactional multi-package installation |
CN102609328A (en) * | 2012-01-29 | 2012-07-25 | 华为终端有限公司 | System difference upgrade method and device and mobile terminal |
CN103226484A (en) * | 2013-04-15 | 2013-07-31 | 浙江大学 | On-orbit update method for satellite-borne integrated electronic system program |
CN103677902A (en) * | 2013-11-25 | 2014-03-26 | 上海斐讯数据通信技术有限公司 | Method for ensuring safety and success of updating of line-card software in distributed OLT system |
CN104156244A (en) * | 2014-08-06 | 2014-11-19 | 北京奇虎科技有限公司 | Method and device for software upgrading |
CN104182299A (en) * | 2014-07-29 | 2014-12-03 | 捷开通讯科技(上海)有限公司 | Software rejuvenation system and method for electronic equipment |
CN104461648A (en) * | 2014-12-22 | 2015-03-25 | 广东欧珀移动通信有限公司 | OTA upgrade backing-up method and system for intelligent terminals |
EP2867813A1 (en) * | 2012-06-29 | 2015-05-06 | Intel Corporation | Mobile platform software update with secure authentication |
Family Cites Families (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8214470B2 (en) * | 2007-11-02 | 2012-07-03 | Telefonaktiebolaget L M Ericsson (Publ) | Upgrading software in radio base station nodes |
US9557981B2 (en) * | 2011-07-26 | 2017-01-31 | Ford Global Technologies, Llc | Method and apparatus for automatic module upgrade |
WO2014164893A2 (en) * | 2013-03-13 | 2014-10-09 | Arynga Inc. | Remote transfer of electronic images to a vehicle |
JP5975964B2 (en) * | 2013-10-18 | 2016-08-23 | 富士通株式会社 | Information processing program, information processing method, information processing apparatus, and information processing system |
-
2015
- 2015-08-26 DE DE102015216265.6A patent/DE102015216265A1/en active Pending
-
2016
- 2016-08-23 KR KR1020160107039A patent/KR102639949B1/en active IP Right Grant
- 2016-08-25 CN CN201610724052.2A patent/CN106484456B/en active Active
Patent Citations (10)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
DE10105454A1 (en) * | 2001-02-07 | 2002-08-29 | Bosch Gmbh Robert | Procedure for the automatic addition of software |
US20050223374A1 (en) * | 2002-06-21 | 2005-10-06 | Koninklijke Philips Electronics N.V. | Server side configuration management |
US20090100421A1 (en) * | 2007-10-10 | 2009-04-16 | Microsoft Corporation | Transactional multi-package installation |
CN102609328A (en) * | 2012-01-29 | 2012-07-25 | 华为终端有限公司 | System difference upgrade method and device and mobile terminal |
EP2867813A1 (en) * | 2012-06-29 | 2015-05-06 | Intel Corporation | Mobile platform software update with secure authentication |
CN103226484A (en) * | 2013-04-15 | 2013-07-31 | 浙江大学 | On-orbit update method for satellite-borne integrated electronic system program |
CN103677902A (en) * | 2013-11-25 | 2014-03-26 | 上海斐讯数据通信技术有限公司 | Method for ensuring safety and success of updating of line-card software in distributed OLT system |
CN104182299A (en) * | 2014-07-29 | 2014-12-03 | 捷开通讯科技(上海)有限公司 | Software rejuvenation system and method for electronic equipment |
CN104156244A (en) * | 2014-08-06 | 2014-11-19 | 北京奇虎科技有限公司 | Method and device for software upgrading |
CN104461648A (en) * | 2014-12-22 | 2015-03-25 | 广东欧珀移动通信有限公司 | OTA upgrade backing-up method and system for intelligent terminals |
Cited By (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN108804254A (en) * | 2017-05-04 | 2018-11-13 | 沃尔沃汽车公司 | Method and system for troubleshooting during vehicle medium-long range installation software |
CN110399146A (en) * | 2018-04-24 | 2019-11-01 | 通用汽车环球科技运作有限责任公司 | Polyelectron control unit wirelessly update in partial fault rollback recovery |
CN109144550A (en) * | 2018-09-03 | 2019-01-04 | 北京新能源汽车股份有限公司 | A kind of data processing method, apparatus and system |
CN110278543A (en) * | 2019-06-27 | 2019-09-24 | 奇瑞汽车股份有限公司 | Control system update method, device and the storage medium of automobile |
CN110278543B (en) * | 2019-06-27 | 2021-11-02 | 奇瑞汽车股份有限公司 | Method and device for updating control system of automobile and storage medium |
CN113227968A (en) * | 2021-03-31 | 2021-08-06 | 华为技术有限公司 | Version management method and device |
Also Published As
Publication number | Publication date |
---|---|
CN106484456B (en) | 2021-07-27 |
DE102015216265A1 (en) | 2017-03-02 |
KR102639949B1 (en) | 2024-02-27 |
KR20170026186A (en) | 2017-03-08 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
CN106484456A (en) | For installing method and the subsystem of software upgrading in vehicle | |
CN106874026A (en) | For the method and apparatus via the air interface steadily firmware of more new vehicle | |
CN101616018B (en) | Device and method for upgrading network management software | |
CN112328294B (en) | OTA upgrading method and system for vehicle ECU | |
US20170242678A1 (en) | Method and apparatus for vehicle software update installation | |
US7366589B2 (en) | Method and system for remote reflash | |
US8676432B2 (en) | Fault prediction framework using temporal data mining | |
US20180095745A1 (en) | Computer System, Method of Updating Software with Computer System, and Program Therefor | |
US20150331686A1 (en) | Over-the-air vehicle issue resolution | |
US20190324858A1 (en) | Rollback recovery from partial failure in multiple electronic control unit over-the-air updates | |
US20090265055A1 (en) | System and method for performing automotive diagnostics | |
CN107992321A (en) | ECU software update method, device, vehicle-mounted T-BOX and vehicle | |
CN110764972A (en) | Method for removing embedded points of APP vehicle | |
CN102982273B (en) | Information handling system and information processing method | |
US20080221752A1 (en) | Procedure for adaptive configuration recognition | |
CN107132788A (en) | A kind of vehicle electronic control unit writes with a brush dipped in Chinese ink method and apparatus automatically | |
CN105446868A (en) | System compatibility testing method, test case management method and related devices | |
CN102999349B (en) | A kind of method for upgrading software | |
JP2020060943A (en) | Vehicle information management system and management method | |
CN109086065A (en) | A kind of method for upgrading software, system and terminal device | |
CN108170441A (en) | Drive programe installation method, device, driver installation client and server | |
CN103365684B (en) | Updating method and multi-domain embedded system | |
DE102017100749A1 (en) | METHOD AND DEVICE FOR CYCLIC FILING REPLACEMENT OF THE DEACTIVATED VEHICLE | |
CN109376072A (en) | Application development method and apparatus based on third party's Component Gallery | |
CN113050960A (en) | OTA (over the air) upgrading method and device, vehicle-mounted terminal and storage medium |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
C06 | Publication | ||
PB01 | Publication | ||
SE01 | Entry into force of request for substantive examination | ||
SE01 | Entry into force of request for substantive examination | ||
GR01 | Patent grant | ||
GR01 | Patent grant |