7*24 hours Technical support

Address: Room 201, Pu soft building, 2 Bo Yun Road, Pudong New Area, Shanghai.

Copyright © 2018 All rights Abupdate 沪ICP备17054239号 Power by:www.300.cn     

Common problem


List of problems

1、Fix system bugs rapidly
For traditional cars, once some system problems were found during users driving, the only way to solve them is that carmakers run up the recall procedure and after got the inform from carmakers, users need to return the car to factory to get the problem fixed. While, if it is a car with OTA function, problems can be rapidly fixed over the air by update package. Which will help users to avoid the risks of months’ recall procedure.
2、Iterate rapidly, to promote products and its experience. 
Because of the firmware advanced configuration once an intelligent car was designed, the operate system of intelligent cars can be updated by OTA over and over again to open more new functions step by step for car drivers. OTA function will optimize the product experience, iterate APPs rapidly and provider better system service to let car drivers feel the feeling of “always in new”
3、Save time and money for both.
Traditional recall procedure needs long process of inside and outside examining and approving, which will cost lot both in time and money. While with OTA update function, the cost of recall procedure will be saved. Why don’t you just use this cost to develop a new product?
There are two types of OTA update for intelligent cars: one is FOTA (Firmware-over-the-air), it is to download an update package for device and ECU flash memory to fix current firmware problems or update flash memory. The other one is SOTA (Software-over-the-air). Update for APPs and map OTA, those who looks closer to users, is SOTA. FOTA has more challenge than SOTA.
Well, no matter FOTA or SOTA, there are actually only three stages: 1. Create update package. 2. Transport update package. 3. Install and update.

Recovery actually is part of OTA. For real computing ability and storage usage of embedded ECU of intelligent cars, recovery is the inevitable way to update firmware. 


As for the transmission of update package among intelligent devices, high speed bus wire, such as Ethernet and FLEXRAY, is the best choice. Meanwhile, beside the transmitting capacity, the TCP of software also need to be well defined.

There are two answers for this question: one is for security and the other one is for protocols. 
For the standard of security, lots of carmakers will use their own encryption standard according to their real demand. Signature and the whole process of ID verification are also some traditional mature system.
For the standard and authentication of protocols, now in China, there is still no a clear definition. ABUP will provide different adaptation to different carmakers. And provide different solution according to carmakers’ requirement on protocols. We can both provide OMA DM solution and privatized protocols according to carmakers’ demand.

For this question, we need to explain from two points of view. For vehicle side, the framework and performance of all car devices are diverse from each other. So, we need to design and customize OTA according to the real framework and bus wire of each devices. And now lots of carmakers intend to realize whole vehicle update or update most of ECUs. To realize this, the investment will be more larger and the test period will be longer in the future. While for cloud side, every carmaker has his own information management system and they are different from each other, which means that in the future the customization work in communication and application will be more. 


We came cross both conditions in our projects and it is decided by the framework of whole vehicle. If the vehicle we applied our OTA into is a mature model or a mature platform or a specific model using passthrough gateway, the OTA recovery will be started by TBOX. If it is a new model and used some optimized gateway targeted in OTA recovery, it will be started by gateway.  Currently, we’ve already got the strategic cooperation with main intelligent gateway makers. As for the protocols between TBOX and gateway, we will provide standard and the protocols can also be customized according carmakers’ real demand in the future. 


This is decided by carmakers. Carmakers will implement OTA nodal points in different stages. For now, mostly OTA nodal points are some intelligent devices and some non-critical components ECUs such as OBU, TBOX, air condition, PEPS. While in the future, carmakers are planning the remote control ability of some critical component ECUs, such as PP, chassis and so on.

For intelligent car, our OTA can realize the complete update including sensor level, decision level and control level. During the cooperation with some carmaker institute with foresight, we notice that, currently, OTA function mainly works in decision level of intelligent car. While decision level can be divided into planning decision and control decision. Lots of institutes with foresight have strong demands on OTA update for intelligent drive. 
Page up