WO2022061804A1 - 一种数据传输系统、数据传输方法,智能车以及装置 - Google Patents
一种数据传输系统、数据传输方法,智能车以及装置 Download PDFInfo
- Publication number
- WO2022061804A1 WO2022061804A1 PCT/CN2020/118080 CN2020118080W WO2022061804A1 WO 2022061804 A1 WO2022061804 A1 WO 2022061804A1 CN 2020118080 W CN2020118080 W CN 2020118080W WO 2022061804 A1 WO2022061804 A1 WO 2022061804A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- ecu
- node
- interface
- software package
- ota server
- Prior art date
Links
- 238000000034 method Methods 0.000 title claims abstract description 117
- 230000005540 biological transmission Effects 0.000 title claims abstract description 68
- 230000004044 response Effects 0.000 claims abstract description 88
- 230000008569 process Effects 0.000 abstract description 39
- 238000012545 processing Methods 0.000 abstract description 22
- 238000005516 engineering process Methods 0.000 abstract description 11
- 238000007726 management method Methods 0.000 description 18
- 238000004891 communication Methods 0.000 description 15
- 238000010586 diagram Methods 0.000 description 12
- 238000004590 computer program Methods 0.000 description 10
- 230000006870 function Effects 0.000 description 9
- 239000002699 waste material Substances 0.000 description 8
- 230000003993 interaction Effects 0.000 description 6
- 238000011161 development Methods 0.000 description 5
- 230000008878 coupling Effects 0.000 description 3
- 238000010168 coupling process Methods 0.000 description 3
- 238000005859 coupling reaction Methods 0.000 description 3
- 238000013461 design Methods 0.000 description 3
- 238000012546 transfer Methods 0.000 description 3
- 230000009471 action Effects 0.000 description 2
- 230000003213 activating effect Effects 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- 230000003068 static effect Effects 0.000 description 2
- 238000001994 activation Methods 0.000 description 1
- 230000006399 behavior Effects 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 238000010276 construction Methods 0.000 description 1
- 238000013500 data storage Methods 0.000 description 1
- 230000007547 defect Effects 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 239000000835 fiber Substances 0.000 description 1
- 238000011900 installation process Methods 0.000 description 1
- 230000007774 longterm Effects 0.000 description 1
- 238000010295 mobile communication Methods 0.000 description 1
- 230000002085 persistent effect Effects 0.000 description 1
- 238000011160 research Methods 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
- 239000007787 solid Substances 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/50—Service provisioning or reconfiguring
-
- 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
-
- B—PERFORMING OPERATIONS; TRANSPORTING
- B60—VEHICLES IN GENERAL
- B60R—VEHICLES, VEHICLE FITTINGS, OR VEHICLE PARTS, NOT OTHERWISE PROVIDED FOR
- B60R16/00—Electric or fluid circuits specially adapted for vehicles and not otherwise provided for; Arrangement of elements of electric or fluid circuits specially adapted for vehicles and not otherwise provided for
- B60R16/02—Electric or fluid circuits specially adapted for vehicles and not otherwise provided for; Arrangement of elements of electric or fluid circuits specially adapted for vehicles and not otherwise provided for electric constitutive elements
- B60R16/023—Electric or fluid circuits specially adapted for vehicles and not otherwise provided for; Arrangement of elements of electric or fluid circuits specially adapted for vehicles and not otherwise provided for electric constitutive elements for transmission of signals between vehicle parts or subsystems
- B60R16/0231—Circuits relating to the driving or the functioning of the vehicle
-
- 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
-
- 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/10—Protocols in which an application is distributed across nodes in the network
-
- 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
- H04L67/125—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks involving control of end-device applications over a network
-
- 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
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/30—Services specially adapted for particular environments, situations or purposes
- H04W4/40—Services specially adapted for particular environments, situations or purposes for vehicles, e.g. vehicle-to-pedestrians [V2P]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W8/00—Network data management
- H04W8/22—Processing or transfer of terminal data, e.g. status or physical capabilities
- H04W8/24—Transfer of terminal data
- H04W8/245—Transfer of terminal data from a network towards a terminal
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0803—Configuration setting
- H04L41/0813—Configuration setting characterised by the conditions triggering a change of settings
- H04L41/082—Configuration setting characterised by the conditions triggering a change of settings the condition being updates or upgrades of network functionality
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/10—Architectures or entities
- H04L65/1016—IP multimedia subsystem [IMS]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/1066—Session management
- H04L65/1069—Session establishment or de-establishment
Definitions
- the present application relates to the technical field of vehicle networks, and in particular, to a data transmission system, a data transmission method, a smart car and a device.
- AutoSar Automotive Open System Architecture
- AutoSar is an open and standardized software architecture jointly established by global car manufacturers, component suppliers and electronic software system companies. It is a summary of more than 100 years of experience in automotive technology development. AutoSar defines a series of system service interfaces, which can be used to realize the compatibility and interoperability of different software, which simplifies the development of automotive software and facilitates the deployment of software on different models.
- the software in the car can be upgraded through over the air (OTA) technology.
- the software package in the cloud server can be downloaded to the local through OTA technology. Since the car includes multiple electronic control units (ECUs), and multiple ECUs have software upgrade requirements, it is necessary to install an upgrade configuration management master (update and configuration management master) on at least one of the multiple ECUs. , UCM Master) module, install the update and configuration management (UCM) module on other ECUs that have software upgrade requirements. Download the software package in the cloud server to the ECU installed with the UCM Master module through OTA technology, and then distribute the software package to multiple ECUs installed with the UCM module through the ECU installed with the UCM Master module to complete the software upgrade of the vehicle .
- UCM Master upgrade configuration management
- UCM update and configuration management
- Embodiments of the present application provide a data transmission system, a data transmission method, a smart car, and a device.
- the solution provided in the present application in the process of realizing the software upgrade in the vehicle through the OTA technology, the dependence on the storage capacity and processing capacity of the main ECU is reduced, and the efficiency of the upgrade is improved.
- a first aspect of the present application provides a data transmission system, which includes an over-the-air OTA server, a main electronic control unit ECU, and a node ECU.
- the OTA server is used to call the first interface of the main ECU.
- An interface can be understood as an interaction method and rules between the first device and the second device.
- the main ECU is used to obtain the size of the target software package in response to the OTA server invoking the first interface Include data for node ECU upgrade. That is, the OTA server can send the size of the target software package to the main ECU by calling the first interface of the main ECU.
- the main ECU is also used to call the second interface of the node ECU.
- the node ECU is used to obtain the size of the target software package in response to the main ECU calling the second interface, and check the remaining storage space of the node ECU. When the remaining storage space is not less than the size of the target software package, receive the target software package sent by the OTA server .
- the data transmission system provided by this application may be AutoSar.
- the main ECU refers to the ECU with the UCM Master module installed in the in-vehicle ECU
- the node ECU refers to the UCM installed in the in-vehicle ECU.
- the ECU of the module, the interface can also be understood as the interaction method and rules between the first module of the first device and the second module of the second device.
- the OTA server can learn whether to send the software package of the first ECU to the first ECU in various ways. It can be seen from the first aspect that the target software package of the node ECU in the solution provided by the first aspect is directly sent to the node ECU by the OTA server, and the main ECU no longer needs to cache the node ECU software package, nor does the main ECU need to forward the node ECU upgrade package. In this way, the main ECU does not need high storage space and processing performance. In the process of in-vehicle software upgrade through OTA technology, the dependence on the storage capacity and processing capacity of the main ECU is reduced.
- the node ECU is further configured to return a first invocation result to the main ECU, where the first invocation result includes a first parameter value, and the first parameter value is To indicate that the remaining storage space of the node ECU is not less than the size of the target software package.
- the main ECU is further configured to call the third interface of the OTA server when the first parameter value is obtained.
- the OTA server is further configured to send the target software package to the node ECU in response to the main ECU calling the third interface. It can be known from the first possible implementation manner of the first aspect that a specific way is provided to make the OTA server know to send the target software package directly to the node ECU.
- the OTA server can be informed to directly send the target software package to the node ECU by adding the first parameter value in the first calling result.
- the second interface is a TransferStart interface for starting transmission.
- the TransferStart interface is an interface defined in AutoSar.
- a parameter is added to the call result of the TransferStart interface defined by the existing AutoSar, and the OTA server can be instructed to send the target software package to the node ECU through the parameter. From the second possible implementation of the first aspect, it can be seen that this solution makes little changes to the existing software upgrade process specified by AutoSar.
- a parameter is added to the call result of the TransferStart interface of the node ECU, and the parameter is fed back.
- the OTA server knows that a distributed download can be performed, and the target software package of the node ECU is directly sent to the node ECU without going through the main ECU.
- the number of node ECUs is N, and N is greater than 1. Integer.
- the main ECU is specifically configured to call the third interface of the OTA server when N first parameter values are obtained. It can be known from the third possible implementation manner of the first aspect that when the data transmission system includes multiple node ECUs, the remaining storage space of each node ECU in the multiple node ECUs obtained by the master ECU is not less than the respective software package.
- the third interface of the OTA server is called, so that the OTA server sends the respective software packages to the node ECU.
- the third interface of the OTA server can send its own software package to each node ECU, or send its own software package to multiple node ECUs at the same time.
- the master ECU obtains in advance whether the remaining storage space of all node ECUs is sufficient, and when the remaining storage space of all node ECUs is sufficient to store their respective software packages, transmit the Software package to prevent upgrade failure due to insufficient resources of some node ECUs during the download process, reducing user traffic consumption and resource waste.
- the second interface can be understood as an interface newly defined in AutoSar in this solution, the main ECU can first call the second interfaces of multiple node ECUs, and obtain multiple first call results at one time .
- the number of node ECUs is N, and N is greater than 1.
- the main ECU is specifically configured to not call the third interface of the OTA server when the M first parameter values are obtained, where M is an integer less than N and greater than 1. It can be seen from the third possible implementation manner of the first aspect that when the master ECU does not obtain that the remaining storage space of each node ECU in the multiple node ECUs is not less than the size of the respective software package, it will no longer call the third step of the OTA server.
- the OTA server does not send the software package to any one of the multiple node ECUs. Prevent upgrade failure due to insufficient resources of some node ECUs during the download process, and reduce user traffic consumption and resource waste.
- the main ECU is further configured to acquire the download address of the target software package in response to the OTA server calling the first interface.
- the node ECU is further configured to return a first calling result to the main ECU, where the first calling result includes a first parameter value, and the first parameter value is used to indicate that the remaining storage space of the node ECU is not less than the size of the target software package.
- the main ECU sends the download address to the node ECU, so that the node ECU can request the OTA server to send the target software package of the node ECU according to the download address.
- the first interface is a TransferVehiclePackage interface for transmitting a complete vehicle software package.
- the TransferVehiclePackage interface is an interface defined in AutoSar.
- this solution adds the download address of the target software package to the existing TransferVehiclePackage interface, so that the main ECU can obtain the download address of the target software package through the TransferVehiclePackage interface.
- a specific way based on AutoSar is given to realize OTA server sending software package directly to node ECU, which increases the diversity of solutions.
- the number of node ECUs is N, and N is an integer greater than 1.
- the main ECU is specifically configured to call the fourth interface of the node ECU when N first parameter values are obtained. It can be known from the seventh possible implementation manner of the first aspect that when the data transmission system includes multiple node ECUs, the remaining storage space of each node ECU in the multiple node ECUs obtained by the master ECU is not less than the respective software package. Only when the size of the node ECU is called, the fourth interface of the node ECU is called, so that the node ECU can obtain the download address of its software package.
- the master ECU When the master ECU obtains that the remaining storage space of each node ECU in the multiple node ECUs is not less than the size of the respective software package, it can make each node ECU obtain its software in the order of sending the software package obtained from the OTA.
- the download address of the package can also be sent to multiple node ECUs at the same time as the download address of their respective software packages. It can be seen from the seventh possible implementation manner of the first aspect that when the remaining storage space of all node ECUs is sufficient to store their respective software packages, the software packages are transmitted again to prevent the upgrade failure due to insufficient resources of some node ECUs during the download process. , reducing user traffic consumption and resource waste.
- the number of node ECUs is N, and N is an integer greater than 1.
- the main ECU is specifically configured to not call the fourth interface of the node ECU when M first parameter values are obtained, where M is an integer less than N and greater than 1. It can be seen from the eighth possible implementation manner of the first aspect that when the master ECU does not obtain that the remaining storage space of each node ECU in the plurality of node ECUs is not less than the size of the respective software package, the fourth node ECU will no longer be stored.
- the main ECU does not send the download address of its software package to any of the multiple node ECUs, preventing the download process. Due to insufficient resources of some node ECUs, the upgrade fails, which reduces user traffic consumption and resource waste.
- the data transmission system is an AutoSar-based data transmission system.
- the node ECU is further configured to send a prompt message, the The prompt message is used to instruct the node ECU to download the target software package from the OTA server.
- the main ECU is further configured to send a prompt message, prompting The message is used to instruct the node ECU to download the target package from the OTA server.
- a second aspect of the present application provides an over-the-air OTA server.
- the OTA server includes an upgrade configuration management UCM module, and the UCM module is used to call a first interface of a main ECU, so that the main ECU calls the first interface in response to the OTA server and obtains a target The size of the software package, and call the second interface of the node ECU, so that the node ECU calls the second interface in response to the main ECU, obtains the size of the target software package, and checks the remaining storage space of the node ECU, and the remaining storage space is not less than the target software When the package size is received, the target package sent by the OTA server is received.
- the UCM module is further configured to send the target software package to the node ECU in response to the main ECU calling a third interface of the UCM module, where the third interface is: The interface of the UCM module called by the main ECU when it obtains the first parameter value.
- the first parameter value is the parameter value included in the first call result returned by the node ECU to the main ECU, and the first parameter value is used to indicate the remaining parameters of the node ECU.
- the storage space is not less than the size of the target package.
- the UCM module is further configured to call the first interface of the main ECU, so that the main ECU calls the first interface in response to the OTA server and obtains the target software.
- the download address of the package so that the node ECU calls the fourth interface in response to the main ECU, obtains the download address of the target software package, and calls the fifth interface of the OTA server.
- the UCM module is further configured to receive the download address of the target software package in response to the node ECU calling the fifth interface of the UCM module, and send the target software package to the node ECU according to the download address.
- a third aspect of the present application provides a main electronic control unit ECU.
- the main ECU includes an upgrade configuration management main control UCM Master module, and the UCM Master module is used for invoking the first interface of the UCM Master module in response to the OTA server and obtaining the information of the target software package. size.
- the UCM Master module is also used to call the second interface of the node ECU, so that the node ECU is called in response to the second interface, obtains the size of the target software package, and checks the remaining storage space of the node ECU, and the remaining storage space is not less than the target software When the size of the package is set, the node ECU receives the target package sent by the OTA server.
- the UCM Master module is also used to call the third interface of the OTA server when the first parameter value is obtained, so that the OTA server responds to the first parameter value.
- the three interfaces are called to send the target software package to the node ECU.
- the first parameter value is the parameter value included in the first call result returned by the node ECU to the main ECU.
- the first parameter value is used to indicate that the remaining storage space of the node ECU is not less than The size of the target package.
- the number of node ECUs is N, and N is an integer greater than 1.
- the UCM Master module is specifically used to call the third interface of the OTA server when N first parameter values are obtained.
- the UCM Master module is further configured to acquire the download address of the target software package in response to the OTA server calling the first interface.
- the UCM Master module is also used to call the fourth interface of the node ECU when the first parameter value is obtained, so that the node ECU is called in response to the fourth interface, obtains the download address, and calls the fifth interface of the OTA server, so that the The OTA server receives the download address in response to the fifth interface being called, and sends the target software package to the node ECU according to the download address.
- the first parameter value is the parameter value included in the first calling result returned by the node ECU to the main ECU.
- the parameter value is used to indicate that the remaining storage space of the node ECU is not less than the size of the target software package.
- the number of node ECUs is N, and N is an integer greater than 1.
- the UCM Master module is specifically used to call the fourth interface of the node ECU when N first parameter values are obtained.
- a fourth aspect of the present application provides a node electronic control unit ECU, the node ECU includes an upgrade configuration management UCM module, and the UCM module is configured to acquire target software in response to the main ECU calling the second interface of the UCM module after the first interface is called package size, and check the remaining storage space of the node ECU.
- the remaining storage space is not less than the size of the target software package, receive the target software package sent by the OTA server, and the first interface of the main ECU is called by the OTA server to make the main ECU respond. The first interface is called to obtain the size of the target software package.
- the UCM module is further configured to return a first call result to the main ECU, where the first call result includes a first parameter value, and the first parameter value is When indicating that the remaining storage space of the node ECU is not less than the size of the target software package, so that the main ECU obtains the first parameter value, the third interface of the OTA server is called, so that the OTA server responds to the main ECU calling the third interface and sends the Node ECU sends target package.
- the UCM module is further configured to return a first call result to the main ECU, where the first call result includes a first parameter value, and the first parameter value is When indicating that the remaining storage space of the node ECU is not less than the size of the target software package, so that the main ECU obtains the first parameter value, the fourth interface of the node ECU is called.
- the UCM module is further configured to call the fourth interface in response to the main ECU, obtain the download address of the target software package, and call the fifth interface of the OTA server, so that the OTA server is called in response to the fifth interface, receives the download address, and according to The download address sends the target software package to the node ECU.
- a fifth aspect of the present application provides a data transmission method, including: the OTA server calls the first interface of the main ECU, so that the main ECU calls the first interface in response to the OTA server, obtains the size of the target software package, and calls the first interface of the node ECU. Second interface, so that the node ECU calls the second interface in response to the main ECU, obtains the size of the target software package, and checks the remaining storage space of the node ECU. When the remaining storage space is not less than the size of the target software package, it receives the target sent by the OTA server. package.
- the method further includes: in response to the main ECU calling the third interface of the UCM module, the OTA server sends the target software package to the node ECU, and the third interface It is the interface of the OTA server called by the main ECU when it obtains the first parameter value.
- the first parameter value is the parameter value included in the first call result returned by the node ECU to the main ECU.
- the first parameter value is used to indicate the The remaining storage space is not less than the size of the target package.
- the method further includes: the OTA server calls the first interface of the main ECU, so that the main ECU calls the first interface in response to the OTA server, and obtains the target The download address of the software package, so that the node ECU calls the fourth interface in response to the main ECU, obtains the download address of the target software package, and calls the fifth interface of the OTA server.
- the OTA server receives the download address of the target software package, and sends the target software package to the node ECU according to the download address.
- a sixth aspect of the present application provides a data transmission method, comprising: a master ECU in response to an OTA server calling a first interface of a UCM Master module to obtain the size of a target software package.
- the main ECU calls the second interface of the node ECU, so that the node ECU responds to the second interface being called, obtains the size of the target software package, and checks the remaining storage space of the node ECU, when the remaining storage space is not less than the size of the target software package, The node ECU receives the target software package sent by the OTA server.
- the method further includes: when the main ECU obtains the first parameter value, calling a third interface of the OTA server, so that the OTA server responds to the first parameter value.
- the three interfaces are called to send the target software package to the node ECU.
- the first parameter value is the parameter value included in the first call result returned by the node ECU to the main ECU.
- the first parameter value is used to indicate that the remaining storage space of the node ECU is not less than The size of the target package.
- the number of node ECUs is N, and N is an integer greater than 1.
- calling the third interface of the OTA server includes: when the main ECU obtains N first parameter values, calling the third interface of the OTA server.
- the method further includes: in response to the OTA server calling the first interface, the main ECU acquires the download address of the target software package.
- the master ECU obtains the first parameter value, it calls the fourth interface of the node ECU, so that the node ECU is called in response to the fourth interface, obtains the download address, and calls the fifth interface of the OTA server, so that the OTA server responds to the fourth interface.
- the fifth interface is called, receives the download address, and sends the target software package to the node ECU according to the download address.
- the first parameter value is the parameter value included in the first call result returned by the node ECU to the main ECU, and the first parameter value is used to indicate The remaining storage space of the node ECU is not less than the size of the target software package.
- the number of node ECUs is N, and N is an integer greater than 1.
- calling the fourth interface of the node ECU includes: when the main ECU obtains N first parameter values, calling the fourth interface of the node ECU.
- a seventh aspect of the present application provides a data transmission method, comprising: a node ECU calling a second interface of the UCM module in response to the main ECU calling the first interface, obtaining the size of the target software package, and checking the remaining storage space of the node ECU , when the remaining storage space is not less than the size of the target software package, the target software package sent by the OTA server is received, and the first interface of the main ECU is called by the OTA server, so that the main ECU responds to the first interface being called and obtains the target software package. size.
- the method further includes: the node ECU returns a first invocation result to the main ECU, where the first invocation result includes a first parameter value, the first parameter value It is used to indicate that the remaining storage space of the node ECU is not less than the size of the target software package, so that when the main ECU obtains the first parameter value, it calls the third interface of the OTA server, so that the OTA server calls the third interface in response to the main ECU, Send the target package to the node ECU.
- the method further includes: the node ECU returns a first invocation result to the main ECU, where the first invocation result includes a first parameter value, the first parameter value It is used to indicate that the remaining storage space of the node ECU is not less than the size of the target software package, so that when the main ECU obtains the first parameter value, the fourth interface of the node ECU is called.
- the node ECU calls the fourth interface in response to the main ECU, obtains the download address of the target software package, and calls the fifth interface of the OTA server, so that the OTA server is called in response to the fifth interface, receives the download address, and sends to the node according to the download address.
- the ECU sends the target package.
- An eighth aspect of the present application provides an OTA server, which may include a processor, the processor is coupled to a memory, the memory stores program instructions, and when the program instructions stored in the memory are executed by the processor, the fifth aspect or any one of the fifth aspects is implemented Methods in possible implementations.
- a ninth aspect of the present application provides an ECU, which may include a processor, the processor is coupled with a memory, the memory stores program instructions, and when the program instructions stored in the memory are executed by the processor, the sixth aspect or any possibility of the sixth aspect is implemented method in an embodiment.
- a tenth aspect of the present application provides an ECU, which may include a processor, the processor is coupled with a memory, the memory stores program instructions, and when the program instructions stored in the memory are executed by the processor, the seventh aspect or any possibility of the seventh aspect is implemented method in an embodiment.
- An eleventh aspect of the present application provides a computer-readable storage medium, which may include a program, which, when executed on a computer, causes the computer to execute the method in the fifth aspect or any possible implementation manner of the fifth aspect.
- a twelfth aspect of the present application provides a computer-readable storage medium, which may include a program, which, when executed on a computer, causes the computer to execute the method in the sixth aspect or any possible implementation manner of the sixth aspect.
- a thirteenth aspect of the present application provides a computer-readable storage medium, which may include a program, which, when executed on a computer, causes the computer to execute the method in the seventh aspect or any possible implementation manner of the seventh aspect.
- a fourteenth aspect of the present application provides a chip system, where the chip system may include a processor to support a vehicle to implement the functions involved in the method described in the sixth aspect or any possible implementation manner of the sixth aspect .
- a fifteenth aspect of the present application provides a chip system, where the chip system may include a processor to support the vehicle to implement the functions involved in the method described in the seventh aspect or any possible implementation manner of the seventh aspect .
- a sixteenth aspect of the present application provides a computer program product that, when the computer program product runs on a device, causes the device to execute the method described in the fifth aspect or any possible implementation manner of the fifth aspect.
- a seventeenth aspect of the present application provides a computer program product, which, when the computer program product runs on a device, causes the device to execute the method described in the sixth aspect or any possible implementation manner of the sixth aspect.
- An eighteenth aspect of the present application provides a computer program product, which, when the computer program product runs on a device, causes the device to execute the method described in the seventh aspect or any possible implementation manner of the seventh aspect.
- a nineteenth aspect of the present application provides a smart car, the smart car may include a main ECU and a node ECU, the main ECU is the ECU described in the third aspect or any possible implementation manner of the third aspect, and the node ECU is the fourth aspect or the ECU described in any possible implementation manner of the fourth aspect.
- a twentieth aspect of the present application provides a smart car, the smart car includes a processing circuit and a storage circuit, the processing circuit and the storage circuit are configured to perform the method described in the sixth aspect or any possible implementation manner of the sixth aspect.
- a twenty-first aspect of the present application provides a smart car, the smart car includes a processing circuit and a storage circuit, the processing circuit and the storage circuit are configured to perform the method described in the seventh aspect or any one of the possible implementations of the seventh aspect .
- the present application provides a data transmission system, a data transmission method, a smart car and a device.
- the main ECU still controls the upgrade process of each node ECU, but the software package of each node ECU is directly sent to each node ECU by the OTA server, and the main ECU no longer needs to cache the software of each node ECU
- the main ECU does not need to forward the upgrade package of each node ECU. In this way, the main ECU does not need to have high storage space and processing performance, and can also improve the efficiency of the upgrade.
- the data transmission system provided by this application defines a new interface.
- node ECUs When all the node ECUs have enough storage space to store their respective software packages, they will send their respective software packages to each node ECU to prevent the download process due to Insufficient resources of some node ECUs cause the upgrade to fail, reducing user traffic consumption and resource waste. The efficiency of the upgrade can be further improved.
- Fig. 1 is the schematic diagram of AutoSar
- Fig. 2 is the framework schematic diagram that realizes software upgrade in AutoSarR;
- Fig. 3 is the schematic flow chart of software upgrade in AutoSar
- FIG. 4 is a schematic flowchart of a data transmission method provided by an embodiment of the present application.
- FIG. 5 is a schematic flowchart of another data transmission method provided by an embodiment of the present application.
- FIG. 6 is a schematic flowchart of another data transmission method provided by an embodiment of the present application.
- FIG. 7a is a schematic flowchart of another data transmission method provided by an embodiment of the present application.
- FIG. 7b is a schematic flowchart of another data transmission method provided by an embodiment of the present application.
- FIG. 8 is a schematic structural diagram of a data transmission system according to an embodiment of the present application.
- FIG. 9 is a schematic structural diagram of a communication device provided by an embodiment of the present application.
- FIG. 10 is a schematic structural diagram of a vehicle provided by an embodiment of the application.
- FIG. 11 is a schematic diagram of an application scenario provided by an embodiment of the present application.
- the naming or numbering of the steps in this application does not mean that the steps in the method flow must be executed in the time/logical sequence indicated by the naming or numbering, and the named or numbered process steps can be implemented according to the The technical purpose is to change the execution order, as long as the same or similar technical effects can be achieved.
- the division of modules in this application is a logical division. In practical applications, there may be other divisions. For example, multiple modules may be combined or integrated into another system, or some features may be ignored. , or not implemented, in addition, the shown or discussed mutual coupling or direct coupling or communication connection may be through some ports, and the indirect coupling or communication connection between modules may be electrical or other similar forms. There are no restrictions in the application.
- modules or sub-modules described as separate components may or may not be physically separated, may or may not be physical modules, or may be distributed into multiple circuit modules, and some or all of them may be selected according to actual needs. module to achieve the purpose of the solution of this application.
- AutoSar is an open and standardized software architecture jointly established by global car manufacturers, component suppliers and electronic software system companies. It is a summary of more than 100 years of experience in automotive technology development. AutoSar defines a series of system service interfaces, which can be used to realize the compatibility and interoperability of different software, which simplifies the development of automotive software and facilitates the deployment of software on different models. AutoSar mainly has the following characteristics:
- AutoSar is committed to solving the difficulties of software development caused by different hardware platforms, so that developers can focus on the innovation of automotive software functions.
- AutoSar provides standard software interface definitions, and engineers can assign the required software components to the electronic control unit (ECU) of the car according to actual needs, so as to realize the reusability of standard software components.
- the application layer software components of AutoSar are independent of hardware, and application developers can specify the details of each vehicle function in the application software without worrying about the incompatibility of underlying software services and hardware interfaces.
- AutoSar includes application software layer (application layer) and system service layer (services layer).
- application layer application layer
- service layer system service layer
- the application software layer encapsulates some or all of the functions and behaviors of automotive electronics, including the realization of specific module functions and corresponding descriptions, and only opens well-defined interfaces to the outside world.
- the main services of the system service layer include communication management services (communication management, COM), encryption services (cryptography, CRYPTO), log services (logging&Tracing, LOG), diagnostic services (diagnostics service, DIAG), persistent storage services (persistency, PER) ), state management service (state management, SM), execution management service (execution management, EXEC), time synchronization service (time synchronization, TSYNC), upgrade configuration management service (update and configuration management, UCM), upgrade configuration management master Services (update and configuration management master, UCM Master), etc.
- the solution provided in this application mainly involves UCM and UCM Master in the system service layer.
- the embodiments provided in this application mainly focus on UCM and UCM Master in the system service layer in AUTOSAR.
- UCM and UCM Master are responsible for managing the update and upgrade of automotive software in the car.
- the existing standards define the interface and interaction process of UCM service and UCM Master service. By using these interfaces, car users or manufacturers can easily use these interfaces in AutoSar Install, update and uninstall software within the system. The following describes the process of upgrading the car software in the car through UCM in AutoSar with reference to FIG. 2 and FIG. 3 .
- FIG. 2 it is a schematic diagram of the architecture for implementing software upgrade in AutoSar.
- software upgrades in the car can be achieved through OTA technology.
- OTA refers to the update or upgrade of automotive software through wireless fidelity (wireless fidelity, wifi), long term evolution (LTE), fifth generation mobile communication (5th generation, 5G) and other air communication interfaces. Because it no longer relies on fixed locations or fixed lines, OTA upgrades have the flexibility and convenience that traditional automotive software upgrade methods do not have.
- the software upgrade package in the cloud server can be downloaded to the local through OTA technology.
- the cloud server is sometimes referred to as an OTA server or an OTA cloud or an OTA cloud server.
- the software of multiple ECUs needs to be upgraded, and the upgrade sequence of multiple ECUs may have dependencies, that is, the sequence of software upgrades of multiple ECUs needs to be controlled.
- the conditions are limited, such as whether the software can be upgraded in the driving state, whether the software can be upgraded after obtaining the consent of the user, and so on. Therefore, a control module needs to be installed on at least one of the multiple ECUs to coordinate the software upgrades of the multiple ECUs.
- this module is the UCM Master module.
- the UCM Master module can be installed on the gateway or the telematic box (TBOX).
- the UCM module is installed on other ECUs in the vehicle to control and coordinate the UCM modules on other ECUs that need to be upgraded through the ECU with UCM Master installed to complete the software upgrade of the entire vehicle.
- the interaction process of software upgrade and download in AutoSar is described below with reference to FIG. 3 .
- the ECU with the UCM Master module installed is called the master ECU
- the ECU with the UCM module installed is called the node ECU.
- the transmission system includes an OTA server, a master ECU, and a plurality of node ECUs.
- a master ECU e.g., a master ECU
- node ECU e.g., a master ECU
- the main ECU refers to the ECU in which the UCM Master module is installed in the in-vehicle ECU
- the node ECU refers to the ECU in which the UCM module is installed in the in-vehicle ECU.
- the software upgrade process in AutoSar can include the following steps:
- the OTA server calls the TransferVehiclePackage interface of the main ECU.
- the OTA server calls the TransferVehiclePackage interface of the UCM Master module of the main ECU. It should be noted that this application sometimes refers to the UCM Master module as the UCM Master service. In addition, it should be noted that the interface of the main ECU in this application refers to the interface of the UCM Master module of the main ECU, which will not be repeated below.
- the vehicle upgrade package mainly includes control information such as upgrade strategy, and the main ECU can control the upgrade and update process of each node ECU according to this information.
- the main ECU can control the upgrade sequence and upgrade conditions of each node ECU according to the control information.
- the upgrade conditions may include whether to allow the software to be upgraded in the driving state, whether to obtain the user's consent to upgrade the software, and the like.
- the vehicle upgrade package download (TransferVehiclePackage) interface of the UCM Master module is defined, and the OTA server can call the TransferVehiclePackage interface of the main ECU to send the upgrade strategy and other control information to the main ECU. Specifically, the control information such as the upgrade strategy is sent to the UCM Master module.
- the whole vehicle upgrade package also includes information of software packages of each ECU.
- the software package information may include package name and size information.
- the OTA server calls the TransferStart interface of the main ECU.
- the OTA server calls the TransferStart interface of the UCM Master service of the main ECU.
- software packages are sometimes referred to as software upgrade packages or upgrade packages, which have the same meaning, and both represent software codes or data that the ECU needs to update.
- the TransferStart interface of the UCM Master service is defined, and the OTA server can call the TransferStart interface of the UCM Master service of the main ECU to send the name of the software upgrade package of each node ECU to the main ECU.
- the main ECU calls the TransferStart interface of the node ECU1.
- the main ECU calls the TransferStart interface of the UCM module of the node ECU1. It should be noted that, the interface of the node ECU in this application all refers to the interface of the UCM module of the node ECU, and the description will not be repeated below.
- the node ECU includes the node ECU1.
- the main ECU calls the TransferStart interface of the node ECU1, and the parameter value of the TransferStart interface of the node ECU1 is the size of the software upgrade package of the node ECU1.
- ECU1 detects the remaining storage space and determines whether the remaining space is sufficient to store the upgrade package of ECU1.
- the node ECU1 returns the calling result of the TransferStart interface of the node ECU1.
- the UCM module of the node ECU1 In response to the main ECU calling the TransferStart interface, the UCM module of the node ECU1 returns the call result of the TransferStart interface to the main ECU, and the calling result can indicate whether the node ECU1 has enough remaining storage space to store the upgrade package of the node ECU1.
- the main ECU feeds back the acquired call result of the TransferStart interface of the node ECU1 to the OTA server.
- the OTA server calls the TransferData interface of the main ECU.
- the OTA server calls the TransferData interface of the UCM Master module of the main ECU.
- the OTA server sends the upgrade package of the ECU1 to the main ECU.
- the upgrade package of the ECU1 may include software codes or data that the ECU1 needs to be updated.
- AutoSar defines the data transfer (TransferData) interface of the UCM Master module and the data transfer (TransferData) interface of the UCM service.
- the OTA server calls the TransferData interface of the UCM Master service of the main ECU.
- the parameter value of the TransferData interface is the software package of ECU1 to transfer the The software package of node ECU1 is sent to the main ECU.
- the main ECU calls the TransferData interface of the node ECU1.
- the main ECU calls the TransferData interface of the UCM module of the node ECU1, and the parameter value of the TransferData interface is the software package of the ECU1, so as to send the software package of the node ECU1 to the node ECU1.
- the node ECU1 returns the calling result of the TransferData interface of the node ECU1.
- the UCM module of the node ECU1 may return a calling result to notify the main ECU that the reception has been successful or the reception has failed.
- the main ECU calls the TransferStart interface of the node ECU2.
- the main ECU calls the TransferStart interface of the UCM module of the node ECU2, and the parameter value of the TransferStart interface of the node ECU2 is the size of the software upgrade package of the node ECU2.
- ECU2 detects the remaining storage space and determines whether the remaining space is sufficient to store the upgrade package of ECU2.
- the node ECU2 returns the calling result of the TransferStart interface of the node ECU2.
- the UCM module of the node ECU2 In response to the main ECU calling the TransferStart interface, the UCM module of the node ECU2 returns the calling result of the TransferStart interface to the main ECU, and the calling result can indicate whether the node ECU2 has enough remaining storage space to store the upgrade package of the node ECU2.
- the master ECU feeds back the acquired call result of the TransferStart interface of the node ECU2 to the OTA server.
- the OTA server calls the TransferData interface of the main ECU.
- the OTA server sends the upgrade package of the ECU2 to the main ECU.
- the upgrade package of ECU2 includes software codes or data that needs to be updated by ECU2.
- the OTA server calls the TransferData interface of the main ECU to send the upgrade package of the node ECU2 to the main ECU.
- the main ECU calls the TransferData interface of the node ECU2.
- the node ECU also includes the node ECU2.
- the main ECU calls the TransferData interface of the node ECU2, and the parameter value of the TransferData interface is the software package of the node ECU2, so as to send the software package of the node ECU2 to the node ECU2.
- step 314 may also be included, in which the node ECU2 returns the calling result of the TransferData interface of the node ECU2.
- the node ECU2 may return the calling result, which is used to notify the main ECU that the reception has succeeded or the reception has failed.
- Steps 303 to 314 are intended to express the size of the respective software upgrade package sent by the master ECU to each node ECU, so that the node ECU checks whether there is enough available memory.
- the main ECU needs to cache the software packages of all node ECUs, and then forward the software packages of the node ECUs to the corresponding node ECUs, for example, step 306 and step 307, and step 312 and step 313.
- This design is so that the main ECU can control the upgrade of each node ECU according to the control information, and coordinate the upgrade process of multiple node ECUs. For example, controlling the upgrade order of each node ECU, including controlling the order of downloading the upgrade package of each node ECU, the order of installing the upgrade package, the order of activating the upgrade package, and so on.
- this design has high requirements on the storage space and processing performance of the main ECU. If the storage space of the main ECU is insufficient, it may fail to download the upgrade package. If the processing performance of the main ECU is not high, it will affect the download. Efficiency, that is, the transmission speed of the upgrade package will be relatively slow, thus affecting the efficiency of the vehicle upgrade. In addition, the applicant found that in the above design, when some node ECUs do not have enough storage space, the node ECUs with sufficient storage space still have to download their respective software packages.
- the node ECU may fail to upgrade even if the upgrade package is downloaded, wasting storage resources and affecting the efficiency of the upgrade.
- node ECU1 has enough storage space
- the software package of node ECU1 is downloaded from the master ECU, but node ECU2 does not have enough storage space
- the master ECU will not send the software package of node ECU2 to node ECU2, if node ECU1 and If the node ECU2 has a dependency on the upgrade, even if the node ECU1 downloads the software package of the node ECU1, the upgrade may fail, which wastes the storage space of the node ECU1 and affects the efficiency of the upgrade.
- the dependency on the upgrade sequence of the node ECUs which may cause the upgrade to fail, there may also be other upgrade failures caused by the lack of sufficient storage space for some node ECUs.
- the main ECU still controls the upgrade process of each node ECU.
- the main ECU can know the upgrade status of each node ECU.
- the main ECU can still know the download status of the node ECU, such as controlling a node ECU. Download software packages, control a node ECU not to download software packages, control the order in which multiple node ECUs download their respective software packages, and so on.
- the main ECU can control multiple node ECUs to download software packages at the same time or download software packages in a certain download order.
- the master ECU can control whether to make the node ECU download the software package.
- the software package of each node ECU is directly sent to each node ECU by the OTA server, and the main ECU is no longer required to cache each node ECU. It also does not need the master ECU to forward the upgrade package of each node ECU. In this way, the main ECU does not need high storage space and processing performance, and can also improve the efficiency of upgrades.
- the data transmission system provided in this application defines a new interface. When all node ECUs have enough storage space to store their respective software packages, they can send their respective software packages to each node ECU, which can further improve the upgrade performance. effectiveness.
- the data transmission system provided by the embodiments of the present application may be based on AutoSar, or may be based on other data transmission systems used for ECU upgrade in the vehicle, and this application takes AutoSar as an example for description.
- FIG. 4 it is a schematic flowchart of a data transmission method according to an embodiment of the present application.
- the OTA server calls the TransferVehiclePackage interface of the main ECU.
- Step 401 can be understood with reference to step 301 in the solution corresponding to FIG. 3 , and details are not repeated here.
- the OTA server calls the TransferStart interface of the main ECU.
- Step 402 can be understood with reference to step 302 in the solution corresponding to FIG. 3 , and details are not repeated here.
- the main ECU calls the TransferStart interface of the node ECU1.
- Step 403 can be understood with reference to step 303 in the solution corresponding to FIG. 3 , and details are not repeated here.
- the node ECU1 returns the calling result of the TransferStart interface of the node ECU1.
- the node ECU1 In response to the main ECU calling the TransferStart interface, the node ECU1 returns a calling result of the TransferStart interface to the main ECU, where the calling result may indicate whether the node ECU1 has enough remaining storage space to store the upgrade package of the node ECU1.
- the calling result may also include a first parameter, and the first parameter value instructs the OTA server to directly send the software package of the node ECU1 to the node ECU1, which will be described below with reference to several specific embodiments.
- the calling result further includes the first parameter value.
- the main ECU can feed back the first parameter value to the OTA server, and after the OTA server obtains the first parameter value, it can directly send the software package to the node ECU1 without going through the main ECU.
- a first parameter is added to the call result. If the node ECU1 has enough remaining storage space to store the upgrade package of the node ECU1, the value of the first parameter is A. If the node ECU1 does not have enough remaining storage space For the upgrade package of the space storage node ECU1, the value of the first parameter is B.
- a and B are used to illustrate that the value of the first parameter is different when the node ECU1 determines that there is enough remaining storage space and that there is not enough remaining storage space.
- the node ECU1 can make the OTA server obtain whether the software package can be directly sent to the node ECU1 by feeding back the first parameter. For example, if the value of the first parameter obtained by the OTA server is A, the software package can be directly sent to the node ECU1 without going through the main ECU.
- the master ECU feeds back the acquired call result of the TransferStart interface of the node ECU1 to the OTA server.
- the UCM master module of the main ECU feeds back the obtained call result of the TransferStart interface of the node ECU1 to the UCM module of the OTA server.
- the call fed back to the OTA server includes the first parameter.
- the main ECU may call an interface of the OTA server to send the acquired call result of the TransferStart interface of the node ECU1 to the OTA server, so that the OTA server responds to the interface being called and sends the call result to the node ECU Send the package.
- one device usually sends information to another device, or instructs another device to perform an action, which is described as one device calling the interface of another device, that is, one device calling the interface of another device to send information to the other device.
- One device sends information, or instructs another device to perform certain actions, which are not described repeatedly in this embodiment of the present application.
- the OTA server calls the TransferData interface of the node ECU1.
- the OTA server can directly send the software package of the node ECU1 to the node ECU1 without forwarding it through the main ECU.
- the specific OTA server obtains whether the software package of the node ECU1 can be directly sent to the node ECU1 according to the first parameter, and the first parameter is the parameter included in the call result of the TransferStart interface of the node ECU1.
- the OTA server can call the TransferData interface of the node ECU1, and the parameter value of the TransferData interface is the software package of the ECU1, so as to send the software package of the node ECU1 to the node ECU1.
- step 407 may also be included, in which the node ECU1 returns the calling result of the TransferData interface of the node ECU1.
- the node ECU1 may return the calling result, which is used to notify the OTA server that the receiving has been successful or the receiving has failed.
- the main ECU calls the TransferStart interface of the node ECU2.
- the node ECU also includes the node ECU2, and the main ECU calls the TransferStart interface of the node ECU2.
- the node ECU2 returns the calling result of the TransferStart interface of the node ECU2.
- the master ECU feeds back the acquired calling result of the TransferStart interface of the node ECU2 to the OTA server.
- the OTA server calls the TransferData interface of the node ECU2.
- the parameter value of the TransferData interface of the node ECU2 is the software package of the node ECU2.
- step 412 may also be included, in which the node ECU2 returns the calling result of the TransferData interface of the node ECU2.
- Steps 408 to 412 can be understood with reference to steps 403 to 407, and details are not repeated here. If other node ECUs are also included, the process of downloading the upgrade package can also be understood with reference to the process of downloading the upgrade package by ECU1 , that is, with reference to steps 403 to 407 .
- this scheme has little changes to the software upgrade process specified by the existing AutoSar.
- a parameter is added to the call result of the TransferStart interface of the node ECU, and the parameter is fed back to the OTA server.
- the OTA server is informed that distributed download can be performed, and the upgrade package of the node ECU is directly sent to the corresponding node ECU without going through the main ECU.
- the present application also provides other solutions based on AutoSar, so that the OTA server can directly send the upgrade package to the node ECU.
- the solution provided in this application can enable the master ECU to obtain in advance whether the remaining storage space of all node ECUs is sufficient, and when the remaining storage space of all node ECUs is sufficient to store their respective software packages, the software packages are transferred to prevent downloading During the process, the upgrade fails due to insufficient resources of some node ECUs, which reduces user traffic consumption and resource waste.
- FIG. 5 it is a schematic flowchart of a data transmission method according to an embodiment of the present application.
- the OTA server calls the TransferVehiclePackage interface of the main ECU.
- the OTA server calls the TransferVehiclePackage interface of the main ECU to send the control information such as the upgrade strategy and the name and size of the software upgrade package of each node ECU to the main ECU. For example, by calling the TransferVehiclePackage interface of the main ECU, the name and size of the software package of the node ECU1 and the name and size of the software package of the node ECU2 are sent to the main ECU.
- the main ECU calls the target interface of the node ECU1.
- a new interface is defined, so that the main ECU can centrally obtain whether the remaining storage space of all node ECUs is sufficient to store the respective software packages.
- the parameter value of the target interface can be the size of the software package of each node ECU.
- Table 1 presents a way of defining a target interface.
- the name of the target interface is TransferCheck
- the input parameter value of the target interface is the size of the package (size)
- the return value of the target interface is true or false.
- true can represent that the remaining storage space of the node ECU is enough to store its software package
- false can represent that the remaining storage space of the node ECU is not enough to store its software package.
- the node ECU checks whether the respective storage space is sufficient to store the respective software package.
- ECU1 that is, the main ECU calls the target interface of the node ECU1, and the parameter value of the target interface includes the size of the software package of the node ECU1.
- the node ECU1 detects the remaining storage space, and determines whether the remaining space is sufficient to store the upgrade package of the node ECU1.
- the node ECU1 returns the calling result of the target interface of the node ECU1.
- the node ECU1 In response to the main ECU calling the target interface, the node ECU1 returns a calling result of the target interface to the main ECU, where the calling result may indicate whether the node ECU1 has enough remaining storage space to store the upgrade package of the node ECU1. For example, true or false when returning the result of the call.
- the main ECU calls the target interface of the node ECU2.
- the main ECU calls the target interface of the node ECU2, and the parameter value of the target interface includes the size of the software package of the ECU2.
- the ECU2 detects the remaining storage space, and determines whether the remaining space is sufficient to store the upgrade package of the ECU2.
- the node ECU2 returns the calling result of the target interface of the node ECU2.
- the node ECU2 In response to the main ECU calling the target interface, the node ECU2 returns a calling result of the target interface to the main ECU, where the calling result may indicate whether the node ECU2 has enough remaining storage space to store the upgrade package of the node ECU2. For example, true or false when returning the result of the call.
- the main ECU sends feedback information to the OTA server according to the acquired call result of the target interface of the node ECU.
- steps 502 to 506 are described with the node ECU including node ECU1 and node ECU2. If other node ECUs are also included, the process of calling the target interface can also be understood with reference to steps 502 to 506.
- the master ECU determines that all node ECUs have enough storage space to store their respective software packages according to the calling results of the target interfaces of all node ECUs, it sends a feedback message to the OTA server, which is used to instruct the OTA to perform distributed download. That is, the OTA server is instructed to send the software package of each node ECU to the corresponding node ECU. For example, if the node ECU only includes node ECU1 and node ECU2, there are the following three situations:
- the main ECU sends the OTA to the The server sends feedback messages.
- the main ECU does not Send a feedback message to the OTA server.
- the OTA server also does not send ECU1's software package to ECU1.
- the main ECU does not Send a feedback message to the OTA server.
- the OTA server also does not send ECU1's software package to ECU2.
- the main ECU may send feedback information to the OTA server when sending the status information.
- AutoSar it is stipulated that the main ECU sends status information to the OTA server to notify the current upgrade status of the OTA server.
- the upgrade status may include the stage of downloading the upgrade package, the stage of installing the upgrade package, and the stage of activating the upgrade package, etc. Wait.
- new state information such as adding first state information, may be added.
- the main ECU determines that all the node ECUs have enough storage space to store their respective software packages according to the calling results of the target interfaces of all the node ECUs, when the main ECU sends the status information to the OTA server, it sends the first status information, the first status information.
- the status information is used to notify the OTA server that the distributed download can be performed.
- the OTA server After receiving the first status information, the OTA server directly sends the software package of each node ECU to the corresponding node ECU, without forwarding it through the main ECU.
- the OTA server calls the TransferData interface of the node ECU1.
- the OTA server determines according to the feedback message that the software package of the node ECU can be sent to the respective node ECU, the OTA server calls the TransferData interface of each node to send the software package to the respective node ECU.
- the feedback message can be status information sent by the main ECU, and the status information is used to indicate that the OTA server can perform distributed download. After the OTA server receives the status information, it directly sends the software package of each node ECU to the corresponding node ECU , no longer forwarded by the main ECU.
- the OTA server can call the TransferData interface of the node ECU1, and the parameter value of the TransferData interface is the software package of the node ECU1, so as to send the software package of the node ECU1 to the node ECU1.
- the method may further include 508 .
- the node ECU1 returns the calling result of the TransferData interface of the node ECU1.
- the node ECU1 may return the calling result, which is used to notify the OTA server that the receiving has been successful or the receiving has failed.
- the OTA server calls the TransferData interface of the node ECU2.
- the OTA server calls the TransferData interface of the node ECU2.
- the method may further include 510: The node ECU2 returns the calling result of the TransferData interface of the node ECU2.
- Steps 509 and 510 can be understood with reference to steps 507 and 508. It should be noted that if other node ECUs are included, they can also be understood with reference to the interaction process between ECU1 and the OAT server or ECU2 and the OTA server, that is, referring to steps 502 to step 509 for understanding.
- a way is provided to enable the master ECU to obtain in advance whether the remaining storage space of all node ECUs is sufficient, when the remaining storage space of all node ECUs is sufficient to store their respective software packages. , and then transmit the software package to prevent the upgrade failure due to insufficient resources of some node ECUs during the download process, and reduce the user traffic consumption and resource waste caused by this.
- a new interface such as a target interface, can be defined in AutoSar, so that the main ECU can obtain whether the remaining storage space of all node ECUs is sufficient, and can add new status information.
- the ECU can notify the OTA server through the new status information that a distributed download is available, that is, the software package of each node ECU is directly sent to the respective node ECU.
- the master ECU may notify the OTA server through new status information that distributed downloading is possible, that is, the software package of each node ECU is directly sent to the respective node ECU.
- the OTA server can also perform distributed download in other ways, that is, directly sending the software package of each node ECU to the respective node ECU. The following description will be given with reference to a specific embodiment.
- FIG. 6 it is a schematic flowchart of a data transmission method according to an embodiment of the present application.
- the OTA server calls the TransferVehiclePackage interface of the main ECU.
- the OTA server calls the TransferVehiclePackage interface of the main ECU to send the control information such as the upgrade strategy, the name and size of the software upgrade package of each node ECU, and the download address of the software package of each node ECU to the main ECU.
- the control information such as the upgrade strategy, the name and size of the software upgrade package of each node ECU, and the download address of the software package of each node ECU to the main ECU.
- the name and size of the software package of the node ECU1 and the download address of the software package of the node ECU1 the name and size of the software package of the node ECU2 and the download address of the software package of the node ECU2 are sent to the main ECU. ECU.
- the download address may be in the form of a uniform resource locator (URL).
- URL uniform resource locator
- the main ECU calls the target interface of the node ECU1.
- the node ECU1 returns the calling result of the target interface of the node ECU1.
- the main ECU calls the target interface of the node ECU2.
- the node ECU2 returns the calling result of the target interface of the node ECU2.
- Steps 602 to 605 can be understood with reference to steps 502 to 505 in the embodiment corresponding to FIG. 5 , and details are not repeated here.
- the main ECU sends the download address of the software package of the node ECU1 to the node ECU1.
- the main ECU determines according to the calling results of the target interfaces of all the node ECUs that all the node ECUs have enough storage space to store their respective software packages, the main ECU sends the download addresses of the respective software packages to each node ECU.
- the node ECU includes node ECU1 and node ECU2, and when both node ECU1 and node ECU2 have enough storage space to store their respective software packages, the master ECU sends the node ECU1's software package download address to node ECU1. The master ECU sends the download address of the software package of the node ECU2 to the node ECU2.
- the master ECU may also send the download address of the software package of the node ECU1 to the node ECU1 when the master ECU obtains that the node ECU1 has enough storage space.
- the main ECU may add an input parameter to the TransferStart interface when calling the TransferStart interface of the node ECU, where the newly added input parameter is the download address of the software package of each node ECU.
- the main ECU calls the TransferStart interface of node ECU1, and the TransferStart interface includes new parameters.
- the value of the new parameters is the download address of the software package of node ECU1.
- the main ECU calls the TransferStart interface of node ECU2
- the TransferStart interface Including new parameters the value of the new parameters is the download address of the software package of the node ECU2.
- the node ECU1 sends a request message to the OTA server according to the obtained download address of the software package of the node ECU1.
- the node ECU1 After receiving the download address of the software package of ECU1, the node ECU1 sends a request message to the OTA server.
- the request message carries the download address of the software package of ECU1.
- the request message is used to request the OTA server to send the software package of the node ECU1. to node ECU1.
- a new interface can be defined, such as a second interface.
- the parameter of the second interface is the download address of the software package.
- the OTA server can The software package is sent to the corresponding node ECU.
- the node ECU1 can call the second interface of the OTA server
- the parameter of the second interface is the download address of the software package of the node ECU1
- the OTA server can call the node ECU1 according to the parameter value of the second interface in response to the second interface being called.
- the software package is sent to node ECU1.
- the interface of the OTA server in this application all refers to the UCM interface of the OTA server, which will not be repeated in this application.
- Table 2 provides a way of defining the second interface. Assuming that the name of the second interface is GetTransferStart, the input parameters of the second interface include the download address of the software package. In some possible implementations, the input parameters of the second interface may also include the name of the software package or the identification ID of the software package.
- interface name GetTransferStart input parameter 1 the name of the package input parameter 2
- the identification ID of the package input parameter 2 The download address of the software package
- the OTA server invokes the TransferData interface of the node ECU1.
- the OTA server In response to the request message sent by the node ECU1, the OTA server sends the software package of the node ECU1 to the node ECU1.
- the OTA server can call the TransferData interface of the node ECU1 to send the software package of the ECU1 to the node ECU1.
- step 609 may also be included, in which the node ECU1 returns the calling result of the TransferData interface of the node ECU1.
- the node ECU1 may return the calling result, which is used to notify the OTA server that the receiving has been successful or the receiving has failed.
- the master ECU sends the download address of the software package of the node ECU2 to the node ECU2.
- the master ECU determines according to the calling results of the target interfaces of all node ECUs, all node ECUs have enough storage space to store their respective software packages, then the master ECU sends the download addresses of the respective software packages to each node ECU.
- the master ECU sends the node ECU2 the download address of the software package of the node ECU2 to the node ECU2.
- the node ECU2 sends a request message to the OTA server according to the obtained download address of the software package of the node ECU2.
- the OTA server calls the TransferData interface of the node ECU2.
- step 613 may also be included, in which the node ECU2 returns the calling result of the TransferData interface of the node ECU2.
- Steps 610 to 613 can be understood with reference to steps 606 to 609 . If other node ECUs are also included, it can also be understood with reference to the interaction process between ECU1 and the OAT server, that is, with reference to steps 602 to 609 .
- the main ECU still controls the upgrade process of each node ECU, such as controlling the order of downloading software packages of each node ECU, but the software packages of each node ECU are controlled by the OTA server. Sending it directly to each node ECU, it is no longer necessary for the main ECU to cache the software package of each node ECU, and there is no need for the main ECU to forward the upgrade package of each node ECU. In this way, the main ECU does not need to have high storage space and Processing performance can also improve the efficiency of upgrades.
- the solution provided by this application supports simultaneous download of multiple node ECUs, thereby improving the download efficiency.
- the data transmission system provided in this application defines a new interface.
- all node ECUs have enough storage space to store their respective software packages, they can send their respective software packages to each node ECU, which can further improve the upgrade performance. effectiveness.
- the software upgrade process in the above-mentioned AutoSar is improved to solve the problem of dependence on the storage space and processing performance of the main ECU during the software upgrade process in the existing AutoSar.
- the solution provided by the present application can also solve the problem of dependence on the storage space and processing performance of the ECU in other ways. The following description will be given with reference to several specific embodiments.
- FIG. 7a it is a schematic flowchart of a data transmission method according to an embodiment of the present application.
- the node ECU1 sends the size of the remaining storage space of the node ECU1 to the master ECU.
- the node ECU2 sends the size of the remaining storage space of the node ECU2 to the master ECU.
- the master ECU sends the size of the remaining storage space of each node ECU to the OTA server.
- Node ID The size of the remaining storage space ID of ECU1
- the size of the remaining storage space of ECU1 ID of ECU2 The size of the remaining storage space of ECU2
- the master ECU can send the size of the remaining storage space of each node ECU to the OTA server in the form of a table.
- the node ECU may also directly send the size of the respective remaining storage space to the OTA server without forwarding by the main ECU.
- the OTA server calls the TransferVehiclePackage interface of the main ECU.
- the OTA server determines according to the size of the remaining storage space of each node ECU and the size of the software package of each node ECU, and each node ECU has enough storage space to store its own software package, the OTA server calls the TransferVehiclePackage interface of the main ECU. For example 3, it is assumed that the node ECU only includes the node ECU1 and the node ECU2. There are three possible situations:
- the remaining storage space of node ECU1 obtained by the OTA server is not less than the size of the software package of ECU1, and the remaining storage space of ECU2 obtained is not less than the size of the software package of ECU2, then the OTA server calls the TransferVehiclePackage interface of the main ECU, In order to send control information such as upgrade strategy to the main ECU.
- the remaining storage space of node ECU1 obtained by the OTA server is not less than the size of the software package of node ECU1, and the remaining storage space of node ECU2 obtained is smaller than the size of the software package of node ECU2, then the OTA server determines that the upgrade cannot be successful at present. , does not start the program to upgrade the package.
- the OTA server determines that the upgrade cannot be successful at present. , does not start the program to upgrade the package.
- the OTA server invokes the TransferData interface of the node ECU1.
- step 706 may also be included, in which the node ECU1 returns the calling result of the TransferData interface of the node ECU1.
- the OTA server invokes the TransferData interface of the node ECU2.
- step 708 may also be included, in which the node ECU2 returns the calling result of the TransferData interface of the node ECU2.
- Steps 705 to 708 can be understood with reference to steps 406 , 407 , and steps 411 and 412 in the embodiment corresponding to FIG. 4 .
- node ECUs it can be understood by referring to the steps performed by the node ECU1 and the node ECU2, and details are not repeated here.
- FIG. 7b it is a schematic flowchart of a data transmission method according to an embodiment of the present application.
- the node ECU1 sends the size of the remaining storage space of the node ECU1 to the master ECU.
- the node ECU2 sends the size of the remaining storage space of the node ECU2 to the master ECU.
- the OTA server calls the TransferVehiclePackage interface of the main ECU.
- the OTA server calls the TransferVehiclePackage interface of the master ECU to send the size of the packages of all node ECUs to the master ECU.
- the node ECU1 and node ECU2 are used as examples for description in this embodiment. If other node node ECUs are also included, it can be understood by referring to the steps performed by node ECU1 and node ECU2, which will not be repeated here.
- the master ECU sends a notification message to the OTA server according to the relationship between the size of the software package of the node ECU and the remaining storage space of the node ECU.
- the main ECU If the main ECU is determined according to the size of the remaining storage space of each node ECU and the size of the software package of each node ECU, and each node ECU has enough storage space to store its own software package, the main ECU sends a notification message to the OTA server to make The OTA server sends the software package to the node ECU.
- the node ECU only includes the node ECU1 and the node ECU2. There are three possible situations:
- the remaining storage space of node ECU1 obtained by the master ECU is not less than the size of the software package of node ECU1, and the remaining storage space of ECU2 obtained is not less than the size of the software package of ECU2, then the master ECU sends a notification message to the OTA server , make the OTA server send the software package of the node ECU1 to the node ECU1, and make the OTA server send the software package of the node ECU2 to the node ECU2.
- the master ECU will not send the data to the OTA server. Notification message, i.e. do not start the process of downloading the package.
- the master ECU will not send the data to the OTA server. Notification message, i.e. do not start the process of downloading the package.
- the OTA server invokes the TransferData interface of the node ECU1.
- step 806 may also be included, in which the node ECU1 returns the calling result of the TransferData interface of the node ECU1.
- the OTA server invokes the TransferData interface of the node ECU2.
- step 808 may also be included, in which the node ECU2 returns the calling result of the TransferData interface of the node ECU2.
- Steps 805 to 808 can be understood with reference to steps 406, 408, and steps 411 and 412 in the embodiment corresponding to FIG. 4 .
- a data transmission method provided by an embodiment of the present application has been introduced above.
- An embodiment of the present application further provides a data transmission system.
- the data transmission system includes an OTA server, a master ECU, and a plurality of node ECUs.
- the OTA server is the OTA server described in the corresponding embodiments described in Figures 4 to 7b
- the main ECU is the main ECU described in the corresponding embodiments described in Figures 4 to 7b
- the node ECU is described in Figures 4 to 7b.
- the node ECUs described in the corresponding embodiments can be understood with reference to the node ECU1 and the node ECU2, for example.
- the embodiments of the present application further provide an OTA cloud server, a master ECU, and a node ECU.
- An OTA cloud server a master ECU
- a node ECU a node ECU
- FIG. 8 it is a schematic structural diagram of a data transmission system according to an embodiment of the present application.
- the data transmission system includes an OTA server, a main ECU and multiple node ECUs.
- the node ECU may include an upgrade configuration management UCM module, and the UCM module of the node ECU is used to obtain that when the target interface of the node ECU is called, check the remaining storage space, and return the first call result, and the parameter value of the target interface can be Including the size of the software package of the node ECU, the first call result indicates whether the remaining storage space is not less than the size of the software package of the node ECU.
- the UCM module of the node ECU is also used to receive the software package of the node ECU sent by the OTA server when the remaining storage space is not less than the size of the software package of the node ECU.
- the target interface is the TransferStart interface
- the first call result may include a first parameter value
- the first parameter is used to instruct the OTA server to send the A node ECU sends the software package of that node ECU.
- the UCM module of the node ECU is further configured to obtain the download address of the software package of the node ECU. According to the obtained download address, the interface of the OTA server is called, and the parameter value of the interface is the download address of the software package of the node ECU, so that the OTA server sends the software package of the node ECU to the UCM module in response to the interface being called.
- the OTA server may include an upgrade configuration management UCM module, and the UCM module of the OTA server is used to call the TransferData interface to send the node ECU's software package to the node ECU.
- the UCM module of the OTA server is specifically configured to call the TransferData interface of the node ECU when the first parameter value is obtained.
- the first parameter value is the first parameter value returned by the node ECU in response to the TransferStart interface being called.
- the UCM module of the OTA server is further configured to call the TransferVehiclePackage interface of the vehicle software package of the main ECU, and the parameter value of the TransferVehiclePackage interface may include the download address of the software package of each node ECU in the multiple node ECUs , so that the main ECU sends the download address of the software package of the node ECU to the node ECU, so that the node ECU calls the interface of the UCM module according to the download address of the node ECU, and the parameters of the interface can include the software package of the node ECU. download link.
- the UCM module is specifically configured to send the software package of the node ECU to the node ECU in response to the node ECU calling the interface.
- the master ECU may include a UCM Master module, the UCM Master module is used to call the target interface of the node ECU, and the parameter value of the target interface may include the size of the software package of the node ECU, so that the node
- the ECU checks the remaining storage space of the node ECU.
- the UCM Master module is further configured to receive the first call result of the target interface sent by the node ECU, where the first call result indicates whether the remaining storage space of the node ECU is not less than the size of the software package of the node ECU.
- the first invocation result may include the first parameter value, the UCM Master module, which is further used to send the first parameter value to the OTA server.
- the first feedback message may include a first parameter value, so that when the OTA server obtains the first parameter value, it calls the TransferData interface of the node ECU to send the node ECU's software package to the node ECU.
- the UCM Master module is further configured to receive a first calling result of each node ECU in the multiple node ECUs, where the node ECU is any one of the multiple node ECUs.
- the second parameter value is sent to the OTA server, so that when the OTA server obtains the second parameter value, the node ECU is called The TransferData interface.
- the embodiment of the present application further provides an ECU, where the ECU is the node ECU in the embodiment corresponding to FIG. 8 above. This can be understood with reference to the node ECUs described in the corresponding embodiments described in Figures 4 to 7b.
- the embodiment of the present application further provides an ECU, and the ECU is the main ECU in the embodiment corresponding to FIG. 8 above. This can be understood with reference to the main ECU described in the corresponding embodiments described in Figures 4 to 7b.
- the embodiment of the present application further provides an OTA server, where the OTA server is the OTA server in the embodiment corresponding to FIG. 8 above.
- the OTA server is the OTA server in the embodiment corresponding to FIG. 8 above. This can be understood with reference to the OTA server described in the corresponding embodiments described in Figures 4 to 7b.
- an embodiment of the present application further provides a communication device.
- the communication device may be the node ECU in the embodiment corresponding to FIG. 4 to FIG. 7b, the communication device may also be the main ECU in the embodiment corresponding to FIG. 4 to FIG. 7b, and the communication device may also be the embodiment of FIG. 4 to FIG. 7b
- the OTA server in the corresponding embodiment.
- the communication device may include a processor 1001.
- the processor 1001 is coupled to a memory 1002, and the memory stores program instructions.
- the main ECU in the embodiments corresponding to FIG. 4 to FIG. 7b is executed.
- the steps executed by the node ECU in the embodiments corresponding to FIG. 4 to FIG. 7 b are executed.
- the steps executed by the OTA server in the embodiments corresponding to FIG. 4 to FIG. 7b are executed.
- FIG. 10 is a schematic structural diagram of a vehicle provided by an embodiment of the present application.
- the node ECU and the main ECU described in the embodiments corresponding to FIG. 4 to FIG. 7 b may be deployed on the vehicle.
- the vehicle may include a display screen 1101 and an ECU 1102 .
- the ECU 1102 is the node ECU and the main ECU described in the above embodiments corresponding to FIG. 4 to FIG. 7 b .
- the vehicle may interact with the user through the display screen, for example, a prompt message may be sent through the display screen, where the prompt message is used to instruct the node ECU to download the software package of the first ECU from the OTA server.
- FIG. 11 it is a schematic diagram of an application scenario of a data transmission method provided by an embodiment of the present application.
- the solutions provided by the embodiments of the present application allow the user to choose whether to upgrade the software in the car, or directly upgrade the software in the car by default.
- a prompt message is sent, indicating that each device is downloading the software package from the OTA server.
- the above vehicles may be cars, trucks, motorcycles, buses, boats, lawn mowers, recreational vehicles, playground vehicles, construction equipment, trams, golf carts, etc., which are not particularly limited in the embodiments of the present application.
- the embodiments of the present application also provide a computer-readable storage medium, where a program for downloading a software package is stored in the computer-readable storage medium, and when the computer is running on the computer, the computer is made to execute the programs shown in the aforementioned FIG. 4 to FIG. 7 b .
- the embodiments of the present application also provide a computer-readable storage medium, where a program for downloading a software package is stored in the computer-readable storage medium, and when the computer is running on the computer, the computer is made to execute the programs shown in the aforementioned FIG. 4 to FIG. 7 b .
- the embodiments of the present application also provide a computer program product, which, when driving on the computer, causes the computer to execute the steps executed by the ECU in the method described in the embodiments shown in the foregoing FIG. 4 to FIG. 7 b . Or when it is driving on the computer, the computer is caused to execute the steps performed by the OTA in the method described in the embodiments shown in the foregoing Figs. 4 to 7b.
- the computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of the present application are generated.
- the computer may be a general purpose computer, special purpose computer, computer network, or other programmable device.
- the computer instructions may be stored in or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be downloaded from a website site, computer, server, or data center Transmission to another website site, computer, server, or data center is by wire (eg, coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (eg, infrared, wireless, microwave, etc.).
- the computer-readable storage medium may be any available medium that can be stored by a computer, or a data storage device such as a server, data center, etc., which includes one or more available media integrated.
- the usable media may be magnetic media (eg, floppy disks, hard disks, magnetic tapes), optical media (eg, DVDs), or semiconductor media (eg, solid state disks (SSDs)), and the like.
- An embodiment of the present application also provides a circuit system, the circuit system includes a processing circuit and a storage circuit, the processing circuit and the storage circuit are configured to execute the ECU or The steps performed by the OTA server.
- the processing circuit can be any suitable type of computing unit, such as a microprocessor, a digital signal processor (DSP), a field programmable gate array (FPGA) or an application specific integrated circuit (application specific integrated circuit). circuit fpga, ASIC) or any other form of circuit.
- the memory circuit may be volatile and/or non-volatile.
- the storage circuit may be a register or a cache.
- the volatile storage circuit may include a cache memory
- the non-volatile storage circuit may include a flash memory.
- the ECU or OTA server provided in this embodiment of the present application may specifically be a chip, and the chip includes: a processing unit and a communication unit, the processing unit may be, for example, a processor, and the communication unit may be, for example, an input/output interface, a pin, or a circuit Wait.
- the processing unit can execute the computer-executed instructions stored in the storage unit, so that the chip in the server executes the data transmission method described in the embodiments shown in FIG. 4 to FIG. 7b.
- the storage unit is a storage unit in the chip, such as a register, a cache, etc.
- the storage unit may also be a storage unit located outside the chip in the wireless access device, such as only Read-only memory (ROM) or other types of static storage devices that can store static information and instructions, random access memory (RAM), etc.
- ROM Read-only memory
- RAM random access memory
- the device embodiments described above are only schematic, wherein the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be A physical unit, which can be located in one place or distributed over multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution in this embodiment.
- the connection relationship between the modules indicates that there is a communication connection between them, which may be specifically implemented as one or more communication buses or signal lines.
- U disk mobile hard disk
- ROM read-only memory
- RAM magnetic disk or optical disk
- a computer device which may be a personal computer, server, or network device, etc.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Theoretical Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- Computer Security & Cryptography (AREA)
- General Physics & Mathematics (AREA)
- Computing Systems (AREA)
- General Health & Medical Sciences (AREA)
- Medical Informatics (AREA)
- Health & Medical Sciences (AREA)
- Databases & Information Systems (AREA)
- Automation & Control Theory (AREA)
- Mechanical Engineering (AREA)
- Stored Programmes (AREA)
- Information Transfer Between Computers (AREA)
- Multimedia (AREA)
Abstract
Description
接口名称 | TransferCheck |
输入参数 | size |
返回值 | ture/false |
接口名称 | GetTransferStart |
输入参数1 | 软件包的名称 |
输入参数2 | 软件包的标识ID |
输入参数2 | 软件包的下载地址 |
节点ID | 剩余的存储空间的大小 |
ECU1的ID | ECU1的剩余的存储空间的大小 |
ECU2的ID | ECU2的剩余的存储空间的大小 |
Claims (31)
- 一种数据传输系统,其特征在于,所述数据传输系统包括空中下载OTA服务器、主电子控制单元ECU和节点ECU;OTA服务器,用于调用所述主ECU的第一接口;所述主ECU,用于响应于所述OTA服务器调用所述第一接口,获取目标软件包的大小;所述主ECU,还用于调用所述节点ECU的第二接口;所述节点ECU,用于响应于所述主ECU调用所述第二接口,获取所述目标软件包的大小,并检查所述节点ECU的剩余存储空间,所述剩余存储空间不小于所述目标软件包的大小时,接收所述OTA服务器发送的所述目标软件包。
- 根据权利要求1所述的数据传输系统,其特征在于,所述节点ECU,还用于向所述主ECU返回第一调用结果,所述第一调用结果包括第一参数值,所述第一参数值用于指示所述节点ECU的剩余存储空间不小于所述目标软件包的大小;所述主ECU,还用于获取到所述第一参数值时,调用所述OTA服务器的第三接口;所述OTA服务器,还用于响应于所述主ECU调用所述第三接口,向所述节点ECU发送所述目标软件包。
- 根据权利要求2所述的数据传输系统,其特征在于,所述节点ECU的数量为N,所述N为大于1的整数;所述主ECU,具体用于获取到N个所述第一参数值时,调用所述OTA服务器的第三接口。
- 根据权利要求1所述的数据传输系统,其特征在于,所述主ECU,还用于响应于所述OTA服务器调用所述第一接口,获取所述目标软件包的下载地址;所述节点ECU,还用于向所述主ECU返回第一调用结果,所述第一调用结果包括第一参数值,所述第一参数值用于指示所述节点ECU的剩余存储空间不小于所述目标软件包的大小;所述主ECU,还用于获取到所述第一参数值时,调用所述节点ECU的第四接口;所述节点ECU,还用于响应于所述主ECU调用所述第四接口,获取所述目标软件包的下载地址,并调用所述OTA服务器的第五接口;所述OTA服务器,还用于响应于所述节点ECU调用所述第五接口,接收所述下载地址,并根据所述下载地址向所述节点ECU发送所述目标软件包。
- 根据权利要求4所述的数据传输系统,其特征在于,所述节点ECU的数量为N,所述N为大于1的整数;所述主ECU,具体用于获取到N个所述第一参数值时,调用所述节点ECU的第四接口。
- 一种空中下载OTA服务器,其特征在于,所述OTA服务器包括升级配置管理UCM模块,所述UCM模块,用于调用主ECU的第一接口,以使所述主ECU响应于所述OTA服务器调用所述第一接口,获取目标软件包的大小,并调用节点ECU的第二接口,以使所述节点ECU响应于所述主ECU调用所述第二接口,获取所述目标软件包的大小,并检查所述节点ECU的剩余存储空间,所述剩余存储空间不小于所述目标软件包的大小时,接收所述OTA服务器发送的所述目标软件包。
- 根据权利要求6所述的OTA服务器,其特征在于,所述UCM模块,还用于响应于所述主ECU调用所述UCM模块的第三接口,向所述节点ECU发送所述目标软件包,所述第三接口是所述主ECU在获取到第一参数值时调用的所述UCM模块的接口,所述第一参数值是所述节点ECU向所述主ECU返回的第一调用结果中包括的参数值,所述第一参数值用于指示所述节点ECU的剩余存储空间不小于所述目标软件包的大小。
- 根据权利要求6所述的OTA服务器,其特征在于,所述UCM模块,还用于调用所述主ECU的第一接口,以使所述主ECU响应于所述OTA服务器调用所述第一接口,获取所述目标软件包的下载地址,以使所述节点ECU响应于所述主ECU调用第四接口,获取所述目标软件包的下载地址,并调用所述OTA服务器的第五接口;所述UCM模块,还用于响应于所述节点ECU调用所述UCM模块的第五接口,接收所述目标软件包的下载地址,并根据所述下载地址向所述节点ECU发送所述目标软件包。
- 一种主电子控制单元ECU,其特征在于,所述主ECU包括升级配置管理主控UCM Master模块,所述UCM Master模块,用于响应于OTA服务器调用所述UCM Master模块的第一接口,获取目标软件包的大小;所述UCM Master模块,还用于调用节点ECU的第二接口,以使所述节点ECU响应于所述第二接口被调用,获取所述目标软件包的大小,并检查所述节点ECU的剩余存储空间,所述剩余存储空间不小于所述目标软件包的大小时,所述节点ECU接收所述OTA服务器发送的所述目标软件包。
- 根据权利要求9所述的主ECU,其特征在于,所述UCM Master模块,还用于获取到第一参数值时,调用所述OTA服务器的第三接口,以使所述OTA服务器响应于所述第三接口被调用,向所述节点ECU发送所述目标软件包,所述第一参数值是所述节点ECU向所述主ECU返回的第一调用结果中包括的参数值,所述第一参数值用于指示所述节点ECU的剩余存储空间不小于所述目标软件包的大小。
- 根据权利要求10所述的主ECU,其特征在于,所述节点ECU的数量为N,所述N为大于1的整数;所述UCM Master模块,具体用于获取到N个所述第一参数值时,调用所述OTA服务器的第三接口。
- 根据权利要求9所述的主ECU,其特征在于,所述UCM Master模块,还用于响应于所述OTA服务器调用所述第一接口,获取所述 目标软件包的下载地址;所述UCM Master模块,还用于获取到所述第一参数值时,调用所述节点ECU的第四接口,以使所述节点ECU响应于所述第四接口被调用,获取所述下载地址,并调用所述OTA服务器的第五接口,以使所述OTA服务器响应于所述第五接口被调用,接收所述下载地址,并根据所述下载地址向所述节点ECU发送所述目标软件包,所述第一参数值是所述节点ECU向所述主ECU返回的第一调用结果中包括的参数值,所述第一参数值用于指示所述节点ECU的剩余存储空间不小于所述目标软件包的大小。
- 根据权利要求12所述的主ECU,其特征在于,所述节点ECU的数量为N,所述N为大于1的整数;所述UCM Master模块,具体用于获取到N个所述第一参数值时,调用所述节点ECU的第四接口。
- 一种节点电子控制单元ECU,其特征在于,所述节点ECU包括升级配置管理UCM模块,所述UCM模块,用于响应于主ECU在被调用第一接口后调用所述UCM模块的第二接口,获取目标软件包的大小,并检查所述节点ECU的剩余存储空间,所述剩余存储空间不小于所述目标软件包的大小时,接收OTA服务器发送的所述目标软件包,所述主ECU的第一接口被所述OTA服务器调用,以使所述主ECU响应于所述第一接口被调用,获取目标软件包的大小。
- 根据权利要求14所述的节点ECU,其特征在于,所述UCM模块,还用于向所述主ECU返回第一调用结果,所述第一调用结果包括第一参数值,所述第一参数值用于指示所述节点ECU的剩余存储空间不小于所述目标软件包的大小,以使所述主ECU获取到所述第一参数值时,调用所述OTA服务器的第三接口,以使所述OTA服务器响应于所述主ECU调用所述第三接口,向所述节点ECU发送所述目标软件包。
- 根据权利要求14所述的节点ECU,其特征在于,所述UCM模块,还用于向所述主ECU返回第一调用结果,所述第一调用结果包括第一参数值,所述第一参数值用于指示所述节点ECU的剩余存储空间不小于所述目标软件包的大小,以使所述主ECU获取到所述第一参数值时,调用所述节点ECU的第四接口;所述UCM模块,还用于响应于所述主ECU调用所述第四接口,获取所述目标软件包的下载地址,并调用所述OTA服务器的第五接口,以使所述OTA服务器响应于所述第五接口被调用,接收所述下载地址,并根据所述下载地址向所述节点ECU发送所述目标软件包。
- 一种数据传输方法,其特征在于,包括:OTA服务器调用主ECU的第一接口,以使所述主ECU响应于所述OTA服务器调用所述第一接口,获取目标软件包的大小,并调用节点ECU的第二接口,以使所述节点ECU响应于所述主ECU调用所述第二接口,获取所述目标软件包的大小,并检查所述节点ECU的剩余存储空间,所述剩余存储空间不小于所述目标软件包的大小时,接收所述OTA服务器发送的所述目标软件包。
- 根据权利要求17所述的数据传输方法,其特征在于,所述方法还包括:所述OTA服务器响应于所述主ECU调用所述UCM模块的第三接口,向所述节点ECU发送所述目标软件包,所述第三接口是所述主ECU在获取到第一参数值时调用的所述OTA服务器的接口,所述第一参数值是所述节点ECU向所述主ECU返回的第一调用结果中包括的参数值,所述第一参数值用于指示所述节点ECU的剩余存储空间不小于所述目标软件包的大小。
- 根据权利要求17所述的数据传输方法,其特征在于,所述方法还包括:所述OTA服务器调用所述主ECU的第一接口,以使所述主ECU响应于所述OTA服务器调用所述第一接口,获取所述目标软件包的下载地址,以使所述节点ECU响应于所述主ECU调用第四接口,获取所述目标软件包的下载地址,并调用所述OTA服务器的第五接口;所述OTA服务器响应于所述节点ECU调用所述UCM模块的第五接口,接收所述目标软件包的下载地址,并根据所述下载地址向所述节点ECU发送所述目标软件包。
- 一种数据传输方法,其特征在于,包括:所述主ECU响应于OTA服务器调用所述UCM Master模块的第一接口,获取目标软件包的大小;所述主ECU调用节点ECU的第二接口,以使所述节点ECU响应于所述第二接口被调用,获取所述目标软件包的大小,并检查所述节点ECU的剩余存储空间,所述剩余存储空间不小于所述目标软件包的大小时,所述节点ECU接收所述OTA服务器发送的所述目标软件包。
- 根据权利要求20所述的数据传输方法,其特征在于,所述方法还包括:所述主ECU获取到第一参数值时,调用所述OTA服务器的第三接口,以使所述OTA服务器响应于所述第三接口被调用,向所述节点ECU发送所述目标软件包,所述第一参数值是所述节点ECU向所述主ECU返回的第一调用结果中包括的参数值,所述第一参数值用于指示所述节点ECU的剩余存储空间不小于所述目标软件包的大小。
- 根据权利要求21所述的数据传输方法,其特征在于,所述节点ECU的数量为N,所述N为大于1的整数;所述主ECU获取到第一参数值时,调用所述OTA服务器的第三接口,包括:所述主ECU获取到N个所述第一参数值时,调用所述OTA服务器的第三接口。
- 根据权利要求20所述的数据传输方法,其特征在于,所述方法还包括:所述主ECU响应于所述OTA服务器调用所述第一接口,获取所述目标软件包的下载地址;所述主ECU获取到所述第一参数值时,调用所述节点ECU的第四接口,以使所述节点ECU响应于所述第四接口被调用,获取所述下载地址,并调用所述OTA服务器的第五接口,以使所述OTA服务器响应于所述第五接口被调用,接收所述下载地址,并根据所述下载地址向所述节点ECU发送所述目标软件包,所述第一参数值是所述节点ECU向所述主ECU返回的第一调用结果中包括的参数值,所述第一参数值用于指示所述节点ECU的剩余存储空间不小于所述目标软件包的大小。
- 根据权利要求23所述的数据传输方法,其特征在于,所述节点ECU的数量为N,所述N为大于1的整数;所述主ECU获取到所述第一参数值时,调用所述节点ECU的第四接口,包括:所述主ECU获取到N个所述第一参数值时,调用所述节点ECU的第四接口。
- 一种数据传输方法,其特征在于,包括:节点ECU响应于主ECU在被调用第一接口后调用所述UCM模块的第二接口,获取目标软件包的大小,并检查所述节点ECU的剩余存储空间,所述剩余存储空间不小于所述目标软件包的大小时,接收OTA服务器发送的所述目标软件包,所述主ECU的第一接口被所述OTA服务器调用,以使所述主ECU响应于所述第一接口被调用,获取目标软件包的大小。
- 根据权利要求25所述的数据传输方法,其特征在于,所述方法还包括:所述节点ECU向所述主ECU返回第一调用结果,所述第一调用结果包括第一参数值,所述第一参数值用于指示所述节点ECU的剩余存储空间不小于所述目标软件包的大小,以使所述主ECU获取到所述第一参数值时,调用所述OTA服务器的第三接口,以使所述OTA服务器响应于所述主ECU调用所述第三接口,向所述节点ECU发送所述目标软件包。
- 根据权利要求25所述的数据传输方法,其特征在于,所述方法还包括:所述节点ECU向所述主ECU返回第一调用结果,所述第一调用结果包括第一参数值,所述第一参数值用于指示所述节点ECU的剩余存储空间不小于所述目标软件包的大小,以使所述主ECU获取到所述第一参数值时,调用所述节点ECU的第四接口;所述节点ECU响应于所述主ECU调用所述第四接口,获取所述目标软件包的下载地址,并调用所述OTA服务器的第五接口,以使所述OTA服务器响应于所述第五接口被调用,接收所述下载地址,并根据所述下载地址向所述节点ECU发送所述目标软件包。
- 一种计算机可读存储介质,包括程序,当其在计算机上运行时,使得计算机执行如权利要求17至19中任一项所述的方法。
- 一种计算机可读存储介质,包括程序,当其在计算机上运行时,使得计算机执行如权利要求20至24中任一项所述的方法。
- 一种计算机可读存储介质,包括程序,当其在计算机上运行时,使得计算机执行如权利要求25至27中任一项所述的方法。
- 一种智能汽车,其特征在于,所述智能汽车包括主电子控制单元ECU和节点ECU,所述主ECU是权利要求9至13任一项所述的主ECU,所述节点ECU是权利要求14至16任一项所述的节点ECU。
Priority Applications (7)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202080004904.5A CN112673609B (zh) | 2020-09-27 | 2020-09-27 | 一种数据传输系统、数据传输方法,智能车以及装置 |
KR1020237013439A KR20230070039A (ko) | 2020-09-27 | 2020-09-27 | 데이터 송신 시스템, 데이터 송신 방법, 스마트 차량 및 디바이스 |
CN202210159429.XA CN114666362A (zh) | 2020-09-27 | 2020-09-27 | 一种数据传输系统、数据传输方法,智能车以及装置 |
JP2023518969A JP2023544123A (ja) | 2020-09-27 | 2020-09-27 | データ送信システム、データ送信方法、インテリジェント車両、及び装置 |
EP20954655.5A EP4207707A4 (en) | 2020-09-27 | 2020-09-27 | DATA TRANSMISSION SYSTEM, DATA TRANSMISSION METHOD, INTELLIGENT VEHICLE AND DEVICE |
PCT/CN2020/118080 WO2022061804A1 (zh) | 2020-09-27 | 2020-09-27 | 一种数据传输系统、数据传输方法,智能车以及装置 |
US18/190,449 US20230236822A1 (en) | 2020-09-27 | 2023-03-27 | Data transmission system, data transmission method, intelligent vehicle, and apparatus |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/CN2020/118080 WO2022061804A1 (zh) | 2020-09-27 | 2020-09-27 | 一种数据传输系统、数据传输方法,智能车以及装置 |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US18/190,449 Continuation US20230236822A1 (en) | 2020-09-27 | 2023-03-27 | Data transmission system, data transmission method, intelligent vehicle, and apparatus |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2022061804A1 true WO2022061804A1 (zh) | 2022-03-31 |
Family
ID=75413911
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2020/118080 WO2022061804A1 (zh) | 2020-09-27 | 2020-09-27 | 一种数据传输系统、数据传输方法,智能车以及装置 |
Country Status (6)
Country | Link |
---|---|
US (1) | US20230236822A1 (zh) |
EP (1) | EP4207707A4 (zh) |
JP (1) | JP2023544123A (zh) |
KR (1) | KR20230070039A (zh) |
CN (2) | CN114666362A (zh) |
WO (1) | WO2022061804A1 (zh) |
Families Citing this family (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2022187189A (ja) * | 2021-06-07 | 2022-12-19 | トヨタ自動車株式会社 | Otaマスタ、センタ、システム、方法、プログラム、及び車両 |
JP2022187162A (ja) * | 2021-06-07 | 2022-12-19 | トヨタ自動車株式会社 | Otaマスタ、システム、方法、プログラム、及び車両 |
CN115878139A (zh) * | 2021-09-29 | 2023-03-31 | 华为技术有限公司 | 芯片升级方法及装置 |
CN114020662A (zh) * | 2021-11-02 | 2022-02-08 | 上海兆芯集成电路有限公司 | 桥接模块、数据传输系统和数据传输方法 |
CN114124842B (zh) * | 2021-11-10 | 2023-07-14 | 北京经纬恒润科技股份有限公司 | 一种数据传输方法、系统、电子设备及存储介质 |
Citations (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN109561118A (zh) * | 2017-09-26 | 2019-04-02 | 比亚迪股份有限公司 | 软件升级方法、装置、系统、存储介质、电子设备及车辆 |
US20190265965A1 (en) * | 2018-02-27 | 2019-08-29 | Excelfore Corporation | System and method for updating software in an electronic device |
CN110377307A (zh) * | 2019-07-18 | 2019-10-25 | 上海擎感智能科技有限公司 | 一种车身控制器固件升级方法、终端、系统 |
CN110597538A (zh) * | 2019-09-03 | 2019-12-20 | 广州小鹏汽车科技有限公司 | 一种基于ota升级系统的软件升级方法和ota升级系统 |
WO2020139400A1 (en) * | 2018-12-27 | 2020-07-02 | Didi Research America, Llc | Trusted platform protection in an autonomous vehicle |
CN111506537A (zh) * | 2019-01-31 | 2020-08-07 | 富士通株式会社 | 车载系统和电子控制单元 |
Family Cites Families (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6832373B2 (en) * | 2000-11-17 | 2004-12-14 | Bitfone Corporation | System and method for updating and distributing information |
US7752618B2 (en) * | 2002-12-05 | 2010-07-06 | Samsung Electronics Co., Ltd. | Apparatus and method for remote DLL linking of software upgrades for a wireless mobile station |
US20170292467A1 (en) * | 2016-04-08 | 2017-10-12 | Infineon Technologies Ag | Control infrastructure for automotive applications |
US11204751B2 (en) * | 2018-09-07 | 2021-12-21 | International Business Machines Corporation | Mitigating incompatibilities due to code updates in a system containing multiple networked electronic control units |
CN111580840A (zh) * | 2020-03-27 | 2020-08-25 | 惠州市德赛西威汽车电子股份有限公司 | 一种基于分布式内存管理实现ecu更新的方法 |
-
2020
- 2020-09-27 EP EP20954655.5A patent/EP4207707A4/en active Pending
- 2020-09-27 JP JP2023518969A patent/JP2023544123A/ja active Pending
- 2020-09-27 CN CN202210159429.XA patent/CN114666362A/zh active Pending
- 2020-09-27 KR KR1020237013439A patent/KR20230070039A/ko active Search and Examination
- 2020-09-27 WO PCT/CN2020/118080 patent/WO2022061804A1/zh unknown
- 2020-09-27 CN CN202080004904.5A patent/CN112673609B/zh active Active
-
2023
- 2023-03-27 US US18/190,449 patent/US20230236822A1/en active Pending
Patent Citations (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN109561118A (zh) * | 2017-09-26 | 2019-04-02 | 比亚迪股份有限公司 | 软件升级方法、装置、系统、存储介质、电子设备及车辆 |
US20190265965A1 (en) * | 2018-02-27 | 2019-08-29 | Excelfore Corporation | System and method for updating software in an electronic device |
WO2020139400A1 (en) * | 2018-12-27 | 2020-07-02 | Didi Research America, Llc | Trusted platform protection in an autonomous vehicle |
CN111506537A (zh) * | 2019-01-31 | 2020-08-07 | 富士通株式会社 | 车载系统和电子控制单元 |
CN110377307A (zh) * | 2019-07-18 | 2019-10-25 | 上海擎感智能科技有限公司 | 一种车身控制器固件升级方法、终端、系统 |
CN110597538A (zh) * | 2019-09-03 | 2019-12-20 | 广州小鹏汽车科技有限公司 | 一种基于ota升级系统的软件升级方法和ota升级系统 |
Non-Patent Citations (1)
Title |
---|
See also references of EP4207707A4 * |
Also Published As
Publication number | Publication date |
---|---|
CN112673609B (zh) | 2022-03-04 |
CN114666362A (zh) | 2022-06-24 |
JP2023544123A (ja) | 2023-10-20 |
CN112673609A (zh) | 2021-04-16 |
EP4207707A1 (en) | 2023-07-05 |
EP4207707A4 (en) | 2023-11-01 |
US20230236822A1 (en) | 2023-07-27 |
KR20230070039A (ko) | 2023-05-19 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2022061804A1 (zh) | 一种数据传输系统、数据传输方法,智能车以及装置 | |
CN105939213B (zh) | 用于车辆的分系统和相应的车辆 | |
US20230004381A1 (en) | Software version rollback method, apparatus, and system | |
US20140007076A1 (en) | Separate upgrade/modification of remote software in machine to machine communication | |
US20220276856A1 (en) | Software upgrading method, apparatus, and system | |
CN111886576A (zh) | 用于更新远程网络设备的方法和装置 | |
JP7357796B2 (ja) | ソフトウェアのアップグレード方法および装置 | |
US20240045657A1 (en) | System architecture for implementing dds communication based on autosar, communication method, and device | |
CN107193609B (zh) | 应用中功能模块调用方法及装置、电子设备 | |
CN113824795A (zh) | 车端与云端的通信方法、装置、系统 | |
CN109104368B (zh) | 一种请求连接方法、装置、服务器及计算机可读存储介质 | |
WO2024008104A1 (zh) | 远程升级方法及系统 | |
CN113485920B (zh) | 实现DoIP实体的方法、装置、可读存储介质及电子设备 | |
CN114979157B (zh) | 基于some/ip协议的负载均衡方法、系统、存储介质及计算机 | |
WO2022205200A1 (zh) | 一种版本管理方法和装置 | |
CN115277671A (zh) | 车辆的ota升级方法、装置、车辆及存储介质 | |
CN114374714A (zh) | 集中式汽车电子电气架构搭建方法、拓扑结构及存储介质 | |
CN115134244B (zh) | 车辆接入设备管理方法、装置、电子设备及存储介质 | |
CN115314376B (zh) | 集群中网络插件部署方法和装置、电子设备和存储介质 | |
WO2023142107A1 (zh) | 设备升级的方法、装置、芯片、存储介质及程序产品 | |
WO2022244588A1 (ja) | 車両用電子制御装置、更新プログラム及びデータ構造 | |
JP2022175440A (ja) | センタ、更新制御方法、更新制御プログラム、otaマスタ | |
US20240111519A1 (en) | Onboard communication system, center device, vehicle-side system, and method for verifying update data of onboard communication | |
CN117421022A (zh) | 应用更新方法、装置、电子设备及存储介质 | |
CN118276962A (zh) | 服务管理方法、应用管理方法、装置以及车辆 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
ENP | Entry into the national phase |
Ref document number: 2023518969 Country of ref document: JP Kind code of ref document: A |
|
ENP | Entry into the national phase |
Ref document number: 2020954655 Country of ref document: EP Effective date: 20230330 |
|
ENP | Entry into the national phase |
Ref document number: 20237013439 Country of ref document: KR Kind code of ref document: A |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 20954655 Country of ref document: EP Kind code of ref document: A1 |