UPGRADE METHOD AND APPARATUS, AND ELECTRONIC DEVICE - Patent application
The method adjusts upgrade strategies for in-vehicle components based on their software functionality status, enabling secure and reliable upgrades even when faulty, thus reducing vehicle unavailability and improving user experience.
Patent Information
- Application Number
- JP2024531373
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2021-11-25
- Publication Date
- 2024-11-21
- Estimated Expiration
- Not applicable · inactive patent
AI Technical Summary
Existing vehicle component upgrade methods face challenges in maintaining security and reliability when software functionality fails, leading to vehicle unavailability and inefficiencies in recovery processes.
A method and apparatus that adjust upgrade strategies based on the software functionality status of in-vehicle components, allowing them to continue upgrading even when faulty, by skipping unnecessary processing steps and ensuring security and reliability through certificate-based verification and user authorization.
Enhances the security and reliability of vehicle component upgrades, reducing unavailability and facilitating normal vehicle use by ensuring timely and secure continuation of upgrade tasks.
Smart Images

Figure 2024543554000001_ABST
Abstract
Description
[Technical field]
[0001] The present application relates to the field of Internet of Vehicles technology, and in particular to an upgrade method and apparatus, and an electronic device. [Background technology]
[0002] With the development of Internet of Vehicles technology, over-the-air (OTA) technology is widely used for upgrading on-board components. On-board components not only include on-board communication terminals, but also include on-board controllers (e.g., passive entry passive start (PEPS), battery management system (BMS), motor control unit (MCU), and power distribution unit (PDU)). Therefore, the upgrade of on-board components not only has high complexity, but also has higher security and reliability requirements.
[0003] However, in the process of upgrading the on-board components, once the software function of the on-board components fails, the on-board components will fail to be upgraded, resulting in the on-board components being disabled. In addition, when the on-board components related to the running of the vehicle (e.g., the on-board controller) are disabled, the vehicle cannot be used normally. In this case, in some technical solutions, the vehicle is moved to a designated area, and a technician performs a recovery process of the software function status of the on-board components. However, this solution is inefficient and requires a large amount of human and material resources.
[0004] Therefore, when the software function status of the on-board components is faulty, how to improve the security and reliability of the upgrade of the on-board components and continue to upgrade the on-board components to facilitate the user's normal use of the vehicle is a technical problem that needs to be urgently solved. Summary of the Invention
[0005] The embodiments of the present application provide an upgrade method and apparatus, and an electronic device, so that the on-board components can still continue the upgrade task when a software function is faulty, effectively improving the security and reliability of the upgrade of the on-board components, thereby facilitating the user's normal use of the vehicle. [Means for solving the problem]
[0006] According to a first aspect, an embodiment of the present application provides an upgrade method. The method can be applied to a server or a chip disposed in the server. The method includes the steps of: obtaining a first instruction when a software function of an on-board component is faulty, the first instruction is used to indicate an upgrade strategy of the on-board component, and the upgrade strategy is associated with the software function status of the on-board component; and sending task information of an upgrade task in response to the first instruction, the task information includes information about the upgrade strategy, and the information about the upgrade strategy is used to indicate the on-board component to be upgraded.
[0007] It should be understood that the on-board components include, but are not limited to, on-board terminals, domain controllers, sensors, and electronic control units (ECUs). The software functions of different on-board components are different. For example, the software function of a power distribution unit (PDU) is a power control function. In another example, the software function of a motor control unit (MCU) is a signal control function. In another example, the software functions of a radar are a speed measurement function, an angle measurement function, and a distance measurement function.
[0008] In this embodiment of the present application, the software function status is associated with the upgrade strategy, and the upgrade strategy of the on-board components can be adjusted based on the software function status of the on-board components. For example, when the software functions related to the security requirements of the vehicle (such as the communication function or the vehicle speed detection function) are running normally, the impact of the failure of some software functions of the on-board components not related to the security requirements (such as the vehicle high voltage signal setting function or the flag status setting function) on the upgrade process of the on-board components is ignored. In this way, the on-board components can still continue to be upgraded when the software functions are faulty, and the security and reliability of the upgrade of the on-board components can be effectively improved and the unavailability of the vehicle can be reduced, thereby facilitating the normal use of the vehicle by the user.
[0009] In one possible design, the information regarding the upgrade strategy includes pre-configured conditions, which may be used by the on-board components to skip pre-upgrade processing procedures or to directly enter the upgrade state.
[0010] It will be understood that the processing procedures before the on-board components are upgraded include, but are not limited to, a signal control procedure, a procedure for checking a mutex, and a procedure for checking a vehicle state. The signal control procedure may be, for example, the setting of at least one of a power-on wake-up signal (KL15) of the on-board components, a network wake-up signal of a controller area network (CAN), and a high-voltage signal of the vehicle. The mutex check procedure may be, for example, a contention check of an on-board service. The procedure for checking a vehicle state may be, for example, a check for allowing a flag to be refreshed by the vehicle, and a check of the upgrade state of the vehicle. "The on-board components directly enter the upgrade state" may be understood as the on-board components skipping the on-board component upgrade pre-processing procedures and directly entering a state of performing an upgrade task.
[0011] In this embodiment of the present application, the preset condition is related to the software function failure state of the on-board component. In other words, different software function failure states correspond to different preset conditions. For example, the on-board component is a passive entry passive start (PEPS), and the software function of the PEPS is a signal (e.g., a CAN network wake-up signal and a power-on wake-up signal) control function. When the signal control function is faulty, the preset condition is that the procedure of detecting the signal control result of the on-board component is omitted. In yet another example, the on-board component is a PDU, and the software function of the PDU is a power control function. When the power control function is faulty, the preset condition is that the procedure of detecting the power control result of the on-board component is omitted.
[0012] In this design, a preset condition is set on the information about the upgrade strategy. The preset condition can be used by the on-board components to skip the upgrade pre-processing procedure or to directly enter the upgrade state, so that the upgrade strategy can be flexibly set. In this way, the on-board components can still continue the upgrade task even when some software functions are faulty.
[0013] In one possible design, the server may further send a second command, which may be used to instruct the vehicle to check its speed and gear status.
[0014] In this design, the server sends a second command to check the vehicle's speed and gear status. In this way, the vehicle can check the speed and gear status, so that the vehicle components can be upgraded while ensuring the safety of the user, thereby effectively improving the security of the vehicle components upgrade.
[0015] In one possible design, before the status of sending the task information of the upgrade task, the upgrade method further includes displaying risk warning information and obtaining a first action of a user on the risk warning information, the first action being used to indicate that the user allows the server to deliver the task information of the upgrade task.
[0016] In this design, the server sends the task information of the upgrade task only after obtaining the user's permission to deliver the task information of the upgrade task, so that the impact of user's incorrect operation on the upgrade of the vehicle components can be effectively reduced, and the upgrade of the vehicle components meets the user requirements.
[0017] In one possible design, the first instruction may be determined based on user input.
[0018] In this design, the first instruction is determined based on the user input, so that the upgrade of the on-board components meets the user requirements. In addition, when the user finds that the software function status of the on-board components is faulty, the server may be triggered in time to adjust the upgrade strategy, thereby improving the upgrade efficiency of the on-board components and facilitating the user's normal use of the vehicle.
[0019] In one possible design, the server may further obtain a third instruction, where if the third instruction is used to indicate that the user authorizes the server to deliver an upgrade package corresponding to the upgrade task, the server sends the upgrade package to the vehicle.
[0020] In this design, the server determines whether to distribute the upgrade package according to the user's instruction. Specifically, the user can determine whether the on-board components are upgraded by using the on-board components' local upgrade package or by using the upgrade package distributed by the server. In this way, the upgrade of the on-board components further meets the user's requirements.
[0021] In a possible design, the server may further sign the task information of the upgrade task based on the first certificate of the vehicle to obtain signed task information, which may be used to verify security of the task information.
[0022] It will be understood that the first certificate may be a certificate issued to the vehicle by a certificate authority and is used to uniquely identify the legal identity of the vehicle. The first certificate may be pre-configured in the server or may be requested by the server from a certificate authority. This is not limited in this embodiment of the present application.
[0023] In this design, the task information of the upgrade task is signed, so that the vehicle can perform signature verification on the task information of the upgrade task. In this way, the case where the task information of the upgrade task is modified by others and security issues occur during the upgrade of the on-vehicle components can be effectively reduced.
[0024] According to a second aspect, an embodiment of the present application further provides another upgrade method. The method can be applied to a vehicle, or a chip or an on-board component disposed in the vehicle. The method includes: receiving task information of an upgrade task, the task information includes information about an upgrade strategy, and the information about the upgrade strategy is associated with a software function status of the on-board component; and upgrading the on-board component based on the information about the upgrade strategy.
[0025] In this embodiment of the present application, after receiving the task information of the upgrade task, the vehicle or the chip or the on-board components arranged in the vehicle can upgrade the on-board components according to the information on the upgrade strategy of the task information. The software function status is associated with the upgrade strategy. In this way, the on-board components can still continue to be upgraded when the software function is faulty, and the security and reliability of the upgrade of the on-board components can be effectively improved, and the unavailability of the vehicle can be reduced, thereby facilitating the normal use of the vehicle by the user.
[0026] In one possible design, the information regarding the upgrade strategy includes pre-configured conditions, which may be used by the on-board components to skip pre-upgrade processing procedures or to directly enter the upgrade state.
[0027] In one possible design, the method further includes receiving a second command, the second command being used to instruct checking a speed and gear state of the vehicle.
[0028] In one possible design, the process of upgrading on-board components based on information about the upgrade strategy may be a step of receiving an upgrade package corresponding to an upgrade task and upgrading the on-board components based on information about the upgrade strategy and the upgrade package.
[0029] In this design, the on-board components are upgraded based on the received upgrade package, so that the timeliness of updating the software functions of the on-board components can be effectively improved.
[0030] In one possible design, the process of upgrading on-board components based on information about the upgrade strategy may be a step of upgrading the on-board components based on information about the upgrade strategy and a local upgrade package of the vehicle.
[0031] In this design, the on-board components are upgraded based on the local upgrade package of the vehicle. In this way, the upgrade efficiency of the on-board components can be effectively improved, so that the vehicle can be returned to a normal use state more quickly, thereby facilitating the user's normal use of the vehicle.
[0032] In one possible design, before upgrading the on-board components based on the information about the upgrade strategy, the method further includes a step of verifying a signature of the task information based on a first certificate of the vehicle, and determining that the signature verification of the task information is successful.
[0033] In this design, the on-board components are upgraded only after the signature of the task information is verified, thereby effectively improving the security and reliability of the on-board component upgrade.
[0034] For the beneficial effects corresponding to other possible designs in the second embodiment, please refer to the beneficial effects of the corresponding designs in the first embodiment, and the details will not be described again in this specification.
[0035] According to a third aspect, an embodiment of the present application further provides another upgrade method, and the method can be applied to an electronic device or a chip disposed in the electronic device. For example, the electronic device may be an intelligent terminal, such as a mobile phone, a computer, a tablet computer, a palmtop computer, a desktop computer, a headset, a speaker, a wearable device, an in-vehicle device, a virtual reality device, and an augmented reality device. The method includes displaying risk warning information, and obtaining a first action of a user for the risk warning information. The first action is used to indicate that the user allows the server to deliver task information of the upgrade task.
[0036] In this embodiment of the present application, the electronic device displays risk warning information and obtains the user's first action for the risk warning information. In this way, the user's permission information for delivering task information is determined, so that the impact of the user's incorrect operation on the upgrade of vehicle components can be effectively reduced, thereby effectively improving the security and reliability of the upgrade of vehicle components.
[0037] In one possible design, the risk warning information is used to indicate a second action, which includes, but is not limited to, at least one of determining that the vehicle is in a stopped state, determining that the vehicle is in a secure area, determining that the vehicle is in an uncharged state, determining that the vehicle door is in a closed state, and determining that the vehicle's on-board diagnostic device is removed. The second action may be performed by the user or the vehicle, which is not specifically limited in this embodiment of the present application.
[0038] In this design, to ensure the security of on-board component upgrades, risk warning information may be used to instruct the user or vehicle to perform corresponding actions.
[0039] According to a fourth aspect, an embodiment of the present application further provides an upgrade apparatus. The apparatus may be configured to perform the method according to the first aspect. For example, the apparatus includes a processing module configured to obtain a first instruction when a software function of an on-board component is faulty, the first instruction is used to indicate an upgrade strategy of the on-board component, and the upgrade strategy is associated with the software function status of the on-board component, and a transceiver module configured to transmit task information of an upgrade task in response to the first instruction, the task information includes information regarding the upgrade strategy, and the information regarding the upgrade strategy is used to indicate the on-board component to be upgraded.
[0040] In one possible design, the information regarding the upgrade strategy includes pre-configured conditions that are used by the on-board components to either skip pre-upgrade processing procedures or to directly enter the upgrade state.
[0041] In one possible design, the transceiver module may be further configured to transmit a second command to instruct the vehicle to check speed and gear status.
[0042] In one possible design, the apparatus may further include a display module. Before the transceiver module transmits the task information of the upgrade task, the display module may be configured to display the risk warning information. The processing module may be further configured to obtain a first action of the user on the risk warning information. The first action is used to indicate that the user authorizes the server to deliver the task information of the upgrade task.
[0043] In one possible design, the first instruction is determined based on user input.
[0044] In one possible design, the processing module may be further configured to obtain a third instruction, the third instruction being used to indicate that a user authorizes the server to deliver an upgrade package corresponding to the upgrade task. The transceiver module may be further configured to transmit the upgrade package to the vehicle.
[0045] In one possible design, the processing module is further configured to sign the task information of the upgrade task based on the first certificate of the vehicle to obtain signed task information, which can be used to verify security of the task information.
[0046] According to a fifth aspect, an embodiment of the present application further provides an upgrade apparatus. The apparatus may be configured to perform the method according to the second aspect. For example, the apparatus includes a transceiver module configured to receive task information of an upgrade task, the task information including information on an upgrade strategy, the information on the upgrade strategy being associated with a software function status of the on-board component, and a processing module configured to upgrade the on-board component based on the information on the upgrade strategy.
[0047] In one possible design, the information regarding the upgrade strategy includes pre-configured conditions that are used by the on-board components to either skip pre-upgrade processing procedures or to directly enter the upgrade state.
[0048] In one possible design, the transceiver module may be further configured to receive a second command, the second command being used to instruct the vehicle to check speed and gear status.
[0049] In one possible design, the transceiver module may be further configured to receive an upgrade package corresponding to the upgrade task. The processing module may be further configured to upgrade the on-board components based on the information regarding the upgrade strategy and the upgrade package.
[0050] In one possible design, the processing module may be further configured to upgrade on-board components based on information regarding the upgrade strategy and the vehicle's local upgrade package.
[0051] In one possible design, the processing module may be further configured to verify a signature of the task information based on a first certificate of the vehicle, and upgrade the on-board components based on information about the upgrade strategy only when it is determined that the signature verification of the task information is successful.
[0052] According to a sixth aspect, an embodiment of the present application further provides an electronic device, which may be configured to perform the method according to the third aspect. For example, the electronic device includes a display module configured to display risk warning information, and an acquisition module configured to acquire a first action of a user on the risk warning information. The first action is used to indicate that the user authorizes the cloud to deliver task information of the upgrade task.
[0053] In one possible design, the risk warning information is used to indicate a second action, the second action including at least one of determining that the vehicle is stopped, determining that the vehicle is in a secure area, determining that the vehicle is uncharged, determining that the vehicle door is closed, and determining that the vehicle's on-board diagnostic device is removed.
[0054] According to a seventh aspect, an embodiment of the present application further provides a vehicle. For example, the vehicle includes a memory and a processor. The memory is configured to store a computer program. The processor is configured to execute the computing program stored in the memory to perform the upgrade method according to the second aspect or any one of the possible designs of the second aspect.
[0055] According to an eighth aspect, an embodiment of the present application further provides a server. For example, the server includes a memory and a processor. The memory is configured to store a computer program. The processor is configured to execute the computing program stored in the memory to perform the upgrade method according to the first aspect or any one of the possible designs of the first aspect.
[0056] In a possible design, the server may be a single server or a server cluster including multiple sub-servers. When the server is a server cluster including multiple sub-servers, the multiple sub-servers may be configured to jointly execute the upgrade method according to the first aspect or any one of the possible designs of the first aspect.
[0057] According to a ninth aspect, an embodiment of the present application further provides a computer storage medium. The computer storage medium stores a computer program. When the computer program is executed, the upgrade method according to the first aspect or any one of the possible designs of the first aspect is performed, or the upgrade method according to the second aspect or any one of the possible designs of the second aspect is performed, or the upgrade method according to the third aspect or any one of the possible designs of the third aspect is performed.
[0058] According to a tenth aspect, an embodiment of the present application provides a chip system, the chip system includes at least one processor, and when program instructions are executed by the at least one processor, an upgrade method according to the first aspect or any one of the possible designs of the first aspect is performed, or an upgrade method according to the second aspect or any one of the possible designs of the second aspect is performed, or an upgrade method according to the third aspect or any one of the possible designs of the third aspect is performed.
[0059] In one possible design, the chip system may further include a communication interface configured to input or output information.
[0060] In a possible design, the chip system may further include a memory, which may be coupled to the processor using a communication interface and configured to store instructions such that the processor reads the instructions stored in the memory through the communication interface.
[0061] In one possible design, the processor may be a processing circuit, although this is not a limitation of this application.
[0062] According to an eleventh aspect, an embodiment of the present application further provides a computer program product, which, when executed on an apparatus, may cause the apparatus to perform an upgrade method according to the first aspect and any one of the optional designs of the first aspect, or to perform an upgrade method according to the second aspect and any one of the possible designs of the second aspect, or to perform an upgrade method according to the third aspect and any one of the possible designs of the third aspect.
[0063] For the beneficial effects of the fourth to eleventh aspects, please refer to the description of the beneficial effects of the first to third aspects, and the details will not be described again in this specification. [Brief description of the drawings]
[0064] [Figure 1] FIG. 1 is a schematic diagram of a system architecture according to an embodiment of the present application. [Diagram 2] FIG. 2 is a schematic diagram of another system architecture according to an embodiment of the present application. [Diagram 3] FIG. 1 is a schematic diagram of a scenario in which an embodiment of the present application is applicable. [Figure 4] 1 is a schematic flowchart of an upgrade method according to an embodiment of the present application; [Figure 5A]1 is a schematic diagram of an interface according to an embodiment of the present application; [Figure 5B] 2 is a schematic diagram of an interface according to an embodiment of the present application. [Figure 6] 1 is a schematic flow chart of upgrading an on-board component by a vehicle according to an embodiment of the present application; [Figure 7] FIG. 2 is a schematic diagram of a secure interaction scenario according to an embodiment of the present application. [Figure 8A-1] 1 is a schematic flowchart 1 of another upgrade method according to an embodiment of the present application. [Figure 8A-2] 1 is a schematic flowchart 1 of another upgrade method according to an embodiment of the present application. [Figure 8B-1] 2 is a schematic flowchart 2 of another upgrade method according to an embodiment of the present application. [Figure 8B-2] 2 is a schematic flowchart 2 of another upgrade method according to an embodiment of the present application. [Figure 9] FIG. 2 is a schematic diagram of a structure of an upgrade device according to an embodiment of the present application; [Figure 10] FIG. 13 is a schematic diagram of the structure of another upgrade device according to an embodiment of the present application. [Figure 11] FIG. 1 is a schematic diagram of the structure of a chip system according to an embodiment of the present application. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0065] First, in order to facilitate the understanding of those skilled in the art, some terms in the embodiments of the present application will be explained and described.
[0066] (1) The on-board components are various components configured to realize vehicle functions. For example, the on-board components may be, for example, any one of an on-board terminal, a domain controller, a sensor, and an electronic control unit (ECU). The software functions of different on-board components are different. For example, the software function of a power distribution unit (PDU) is a power control function. In another example, the software function of a motor control unit (MCU) is a signal control function. In another example, the software function of a radar is a signal control function. In an embodiment of the present application, there may be one or more on-board components.
[0067] (2) Certificate means a digital certificate, which is a file digitally signed by a certificate authority (CA) and contains a public key and information about the public key owner. Certificates are used for identity authentication between communicating parties. A certificate generally includes information such as a certificate version number, a serial number, a signature algorithm identifier, an issuer name, a subject public key information, and a validity. A certificate may further include an issuer unique identifier, a subject unique identifier, and other extensions. The certificate in the embodiment of the present application may be used to sign the sender's information, so that the receiver can verify the signed information.
[0068] (3) Signing can be understood as a process of identifying information to be transmitted using a digital certificate. The information to be transmitted in the embodiment of the present application may be task information of an upgrade task, or may be an upgrade package corresponding to the upgrade task.
[0069] (4) In the embodiment of the present application, the upgrade device may be understood as a device disposed in a vehicle to upgrade at least the on-board components and manage the upgrade package of the upgrade task. The upgrade device may be, for example, a telematics box (T-Box) or a gateway device (GW), which is not specifically limited in this embodiment of the present application.
[0070] (5) In the embodiments of this application, "at least one" means one or more, and "multiple" means two or more. "And / or" describes the association relationship between related objects and represents that three relationships may exist. For example, A and / or B can represent the cases where only A exists, where both A and B exist, and where only B exists, where A and B may be singular or plural. The symbol " / " generally indicates an "or" relationship between related objects. "At least one of" or similar expressions refers to any combination of those items, including any combination of a single item or multiple items. For example, at least one of a, b, and c can represent a, b, c, a and b, a and c, b and c, or a, b, and c, where a, b, and c may be singular or plural.
[0071] In addition, it should be understood that in the description of this application, terms such as "first" and "second" are used for distinguishing and describing purposes only and should not be understood as indicating or implying relative importance or as indicating or implying an order.
[0072] The embodiments of the present application provide an upgrade method and apparatus, and an electronic device. The method can be applied to a server and a vehicle. In the method, a first instruction can be obtained when a software function of an on-board component is faulty, and task information of an upgrade task is sent in response to the first instruction. The first instruction is used to indicate an upgrade strategy of the on-board component, and the upgrade strategy is associated with a software function status of the on-board component. The task information includes information about the upgrade strategy, and the information about the upgrade strategy is used to indicate the on-board component to be upgraded. In response, the vehicle receives task information corresponding to the upgrade task, and upgrades the on-board component based on the information about the upgrade strategy of the task information. In the method, the software function status is associated with the upgrade strategy, and the server can adjust the upgrade strategy of the on-board component based on the software function status of the on-board component. For example, when a software function related to a security requirement of the vehicle (e.g., a communication function or a vehicle speed detection function) is running normally, the impact of a failure of some software functions of the on-board component not related to the security requirement (e.g., a vehicle high voltage signal setting function or a flag status setting function) on the upgrade process of the on-board component is ignored. In this way, the on-board components can still continue to be upgraded when a software function is faulty, effectively improving the security and reliability of the on-board component upgrade, and reducing the unavailability of the vehicle, thereby facilitating the user's normal use of the vehicle.
[0073] With reference to the accompanying drawings, the following describes a system architecture to which an embodiment of the present application is applicable.
[0074] 1 shows a system architecture to which an embodiment of the present application is applicable. The system shown in FIG. 1 includes a vehicle 100 and a server 200.
[0075] It will be understood that the server 200 may establish a communication connection to the vehicle 100 via a conventional internet protocol (IP) network to conduct the communication interaction. Alternatively, the server 200 may establish a communication connection to the vehicle 100 through a mobile communication network (including an access network and a core network) to conduct the communication interaction, which is not limited in this embodiment of the present application.
[0076] The server 200 may communicate and interact with the vehicle 100. In a possible implementation, the server 200 may obtain a first instruction when a software function of an on-board component of the vehicle 100 is malfunctioning, and send task information of an upgrade task to the vehicle 100 in response to the first instruction. The first instruction may be used to indicate an upgrade strategy of the on-board component, and the upgrade strategy is associated with the software function status of the on-board component. Correspondingly, the task information includes information about the upgrade strategy, and the information about the upgrade strategy is used to indicate the on-board component to be upgraded. In this manner, the vehicle 100 may receive the task information of the upgrade task and upgrade the on-board component based on the information about the upgrade strategy in the task information. For example, when a vehicle high voltage signal setting function and a flag status setting function of the on-board component are malfunctioning, the server 200 may obtain a first instruction, adjust the upgrade strategy of the on-board component based on the first instruction, and send task information carrying the upgrade strategy to the vehicle 100, so that the vehicle 100 can upgrade the on-board component based on the adjusted upgrade strategy. In this way, the on-board components can still continue to be upgraded when a software function is faulty, the security and reliability of the on-board component upgrade can be effectively improved, and the unavailability of the vehicle 100 can be reduced, thereby facilitating the user's normal use of the vehicle 100.
[0077] Further, the vehicle 100 includes an on-board component 101 and an upgrade component 102. In this manner, the server 200 can establish a communication connection to the upgrade component 102 and send task information of the upgrade task to the upgrade component 102, so that the upgrade component 102 can upgrade the on-board component 101 based on the information about the upgrade strategy in the task information. The upgrade component 102 may be, for example, a T-BOX.
[0078] Optionally, the system may further include an electronic device 300. The server 200 may communicate and interact with the electronic device 300. Similarly, the server 200 may establish a communication connection to the electronic device 300 through a conventional IP network to carry out a communication interaction. Alternatively, the server 200 may establish a communication connection to the electronic device 300 through a mobile communication network (including an access network and a core network) to carry out a communication interaction. This is not limited in this embodiment of the present application.
[0079] It will be appreciated that the server 200 obtains the first instruction in a number of implementations, including but not limited to the following.
[0080] Implementation form 1: The electronic device 300 obtains a user input, converts the user input into a first command, and sends the first command to the server 200. In response, the server 200 receives the first command. In this way, the server 200 can obtain the first command by using the electronic device 300, so that the user can remotely control the upgrade of the in-vehicle components, thereby effectively improving the user experience.
[0081] Implementation form 2: The server 200 obtains a user input and converts the user input into a first command. In this way, the server 200 can quickly obtain the first command, thereby effectively improving the upgrade efficiency of the vehicle components.
[0082] It should be noted that the architecture shown in Fig. 1 can be applied to multiple communication scenarios, such as the 5th Generation (5G) communication system, future 6th generation communication system and other evolved communication systems, Long Term Evolution (LTE) communication system, vehicle to everything (V2X), Long Term Evolution-vehicle (LTE-V), vehicle to vehicle (V2V), Internet of Vehicles, Machine Type Communications (MTC), Internet of Things (IoT), Long Term Evolution Machine to Machine (LTE-machine to machine (LTE-M), and machine to machine (M2M). This is not limited in the embodiments of the present application.
[0083] It should be noted that the server 200 in FIG. 1 may be a cloud server or a local server, which is not limited in this embodiment of the present application. The electronic device 300 may be any one of intelligent terminals such as a mobile phone, a computer, a tablet computer, a palmtop computer, a desktop computer, a headset, a speaker, a wearable device, an in-vehicle device, a virtual reality device, and an augmented reality device, which is not limited in this embodiment of the present application.
[0084] 2 shows another possible system architecture to which an embodiment of the present application can be applied. In FIG. 2, a cloud server is used as an example of a server 200, a mobile phone is used as an example of an electronic device 300, and an upgrade device 102 is used as an example of a device for realizing the upgrade of in-vehicle components.
[0085] The cloud server includes an over the air (OTA) upgrade management module 1 and an OTA upgrade package management module 2. The OTA upgrade management module 1 may be configured to create an OTA upgrade task, manage the upgrade task, and deliver task information of the upgrade task. The OTA upgrade package management module 2 may be configured to manage an upgrade package corresponding to the upgrade task, and may provide the upgrade device 102 with a corresponding upgrade package.
[0086] The upgrade device 102 includes an OTA upgrade management module 3 and an OTA upgrade package management module 4. The OTA upgrade management module 3 is configured to communicate and interact with the OTA upgrade management module 1, receive OTA upgrade tasks, manage the upgrade tasks, and report upgrade-related data (e.g., software function status of on-board components, upgrade progress, and upgrade anomaly information) to the OTA upgrade management module 1. The OTA upgrade package management module 4 may be configured to communicate and interact with the OTA upgrade package management module 2 to obtain upgrade packages corresponding to the upgrade tasks and manage the upgrade packages of all on-board components.
[0087] The mobile phone includes an OTA upgrade management module 5. The OTA upgrade management module 5 may be configured to perform a corresponding conversion process on the user input and communicate and interact with the OTA upgrade management module 1. In one possible implementation form, the OTA upgrade management module 5 may obtain the user input, convert the user input into a first command, and send the first command to the OTA upgrade management module 1. In this way, after receiving the first command, the OTA upgrade management module 1 may send task information of the upgrade task to the OTA upgrade management module 3 in response to the first command, so that the OTA upgrade management module 3 may upgrade the in-vehicle components associated with the task information based on the task information.
[0088] It should be noted that in this embodiment of the present application, the software function of the on-board component may fail due to multiple reasons, such as abnormality of the on-board component related to the on-board component, abnormal operation of the OTA upgrade device, or damage to the software function of the on-board component. Therefore, the upgrade method provided in this embodiment of the present application is applicable to multiple scenarios, including but not limited to the following:
[0089] Scenario 1: A second on-board component associated with a first on-board component is abnormal, and as a result, the first on-board component cannot be successfully upgraded.
[0090] In scenario 1, when a first vehicle component processes an upgrade task, if a second vehicle component associated with the first vehicle component is faulty, the upgrade task of the first vehicle component is interrupted, and the software function of the first vehicle component is faulty. In addition, even if the OTA upgrade device resumes the upgrade task after the fault of the second vehicle component is resolved, the software function of the first vehicle component is still in a faulty state (i.e., unavailable state), and the procedure related to the upgrade task (e.g., setting the related control signal) cannot be performed. As a result, the OTA upgrade device still cannot perform the upgrade task of the first vehicle component.
[0091] For example, see (a) of FIG. 3. An example of the first on-board component is one of the on-board components of the BMS, the MCU, and the PDU, and an example of the second on-board component is the battery of the vehicle 100. For example, when the BMS is processing an upgrade task (e.g., refreshing an upgrade package), if a battery failure (e.g., power off or power shortage) occurs, the software function of the BMS will fail, causing the interruption of the upgrade task of the BMS. In addition, even if the OTA upgrade device resumes the upgrade task after the battery failure is recovered, the software function of the BMS is still in a fault state, so the BMS cannot set the high-voltage signal of the vehicle. As a result, the MDC cannot be started, and the MDC cannot receive the upgrade mode control packet of the OTA upgrade device. As a result, the OTA upgrade device cannot perform the upgrade task of the BMS.
[0092] Similarly, when the MCU is processing an upgrade task (e.g., refreshing an upgrade package), if a battery failure (e.g., power off or power shortage) occurs, the software function of the MCU will fail, causing the interruption of the upgrade task of the MCU. In addition, even if the OTA upgrade device resumes the upgrade task after the battery failure is recovered, the software function of the MCU is still in a failed state, so the MCU cannot set the high-voltage signal of the vehicle. As a result, the MDC cannot be initiated, and the MDC cannot receive the upgrade mode control packet of the OTA upgrade device. As a result, the OTA upgrade device cannot perform the upgrade task of the MCU.
[0093] Similarly, when the PDU is processing an upgrade task (e.g., refreshing an upgrade package), if a battery failure (e.g., power off or power shortage) occurs, the software function of the PDU will fail, causing the interruption of the upgrade task of the PDU. In addition, even if the OTA upgrade device resumes the upgrade task after the battery failure is recovered, the software function of the PDU is still in a failed state, so the PDU cannot set the high-voltage signal of the vehicle. As a result, the MDC cannot be initiated, and the MDC cannot receive the upgrade mode control packet of the OTA upgrade device. As a result, the OTA upgrade device cannot perform the upgrade task of the PDU.
[0094] Scenario 2: An abnormal operation occurs in the OTA upgrade device, so that the first in-vehicle component cannot be upgraded normally.
[0095] In scenario 2, when the first vehicle component is processing the upgrade task, if the OTA upgrade device experiences an abnormal operation (e.g., reboot), the software function of the first vehicle component will fail, causing the upgrade task of the first vehicle component to be interrupted. Even if the OTA upgrade device runs normally, the first vehicle component is still in a faulty state, and the procedure related to the upgrade task (e.g., setting the related control signal) cannot be performed. As a result, the OTA upgrade device cannot perform the upgrade task of the first vehicle component.
[0096] For example, see (b) of FIG. 3. A T-BOX is used as an example of an OTA upgrade device, and a PEPS is used as an example of a first in-vehicle component. When the PEPS is processing an upgrade task (e.g., refreshing an upgrade package), the T-BOX is rebooted, and a software function of the PEPS fails, causing an interruption of the upgrade task of the PEPS. Even if the T-BOX runs normally, the software function of the PEPS is still in a failed state, and the PEPS cannot set a power-on wake-up signal (KL15) of a multi-domain controller (MDC). As a result, the MDC cannot be started, and the MDC cannot receive the upgrade mode control packet of the T-BOX. As a result, the T-BOX cannot perform the upgrade task of the PEPS.
[0097] Scenario 3: A software function of the first on-board component is faulty, so that the first on-board component cannot be successfully upgraded.
[0098] In scenario 3, when the first on-board component performs an upgrade task (e.g., refreshing an upgrade package or loading an upgrade package), if the software function of the first on-board component fails due to reasons of the first on-board component (e.g., the chip is damaged), the upgrade task of the first on-board component is interrupted.
[0099] For example, the first in-vehicle component is the BMS. Because the chip of the BMS is damaged and the software function of the BMS is faulty, the BMS cannot set the high voltage signal of the vehicle. As a result, the MDC cannot be started, and the MDC cannot receive the upgrade mode control packet of the OTA upgrade device. As a result, the OTA upgrade device cannot perform the upgrade task of the BMS.
[0100] According to the method provided in this embodiment of the present application, the upgrade strategy of the on-board components can be adjusted based on the software function status of the on-board components. Therefore, according to the method provided in this embodiment of the present application, the first on-board components in the above-mentioned scenarios 1, 2, and 3 can still perform upgrade tasks when their software functions are faulty. In addition, since the software function status is associated with the upgrade strategy, the security and reliability of the upgrade of the on-board components can be effectively improved, and the unavailability of the vehicle can be reduced, thereby facilitating the user's normal use of the vehicle.
[0101] The following describes the upgrade method provided in this embodiment of the present application with reference to certain accompanying drawings.
[0102] 4 is a schematic flowchart of an upgrade method according to an embodiment of the present application. The method is applicable to the system architecture shown in FIG. 1. An example of an entity for performing the method includes a server 200 and a vehicle 100. The method includes the following steps:
[0103] S401: The server 200 obtains a first instruction when a software function of an in-vehicle component fails.
[0104] It should be understood that the on-board components include, but are not limited to, on-board terminals, domain controllers, sensors, and ECU control units. In this embodiment of the present application, there may be one or more on-board components. For example, the on-board components may be a PEPS, or may be a BMS, an MCU, and a PDU. This is not specifically limited in this embodiment of the present application.
[0105] In this embodiment of the present application, "the software function of the on-board component is malfunctioning" may be understood as the software function of the on-board component being in an unusable state. In one possible implementation, the server 200 may request the diagnostic status of the on-board component from the vehicle 100 at a preset time interval, and determine whether the software function of the on-board component is malfunctioning based on the diagnostic status, and obtain a first instruction when the software function of the on-board component is malfunctioning. In another possible implementation, the server 200 may receive the diagnostic status of the on-board component actively reported by the vehicle 100 at a preset time interval, and determine whether the software function of the on-board component is malfunctioning based on the diagnostic status, and obtain a first instruction when the software function of the on-board component is malfunctioning.
[0106] It is understood that the software functions of different on-board components may be the same or different. For example, both the PDU and the MCU have the function of setting a high voltage signal. As another example, the software function of the PDU may further be a power control function, and the software function of the radar may be a speed measurement function, an angle measurement function, and a distance measurement function.
[0107] The first command may be used to indicate an upgrade strategy of the on-board component, and the upgrade strategy is associated with the software function status of the on-board component. In other words, the server 200 may adjust the upgrade strategy of the on-board component in response to the first command based on the software function status of the on-board component. For example, the on-board component is a PEPS. The software function of the PEPS is a vehicle high pressure signal setting function. When the vehicle high pressure signal setting function is faulty, the server 200 may adjust the upgrade strategy of the PEPS to omit the procedure of detecting the vehicle high pressure signal and directly enter the upgrade state. In another example, the on-board component is a PDU. The software function of the PDU is a power control function. When the power control function is faulty, the server 200 may adjust the upgrade strategy of the PDU to omit the procedure of detecting the MDC power-on wake-up state and directly enter the upgrade state. In another example, the on-board component is a BMS. The software function of the BMS is a battery management function. When the battery management function is faulty, the server 200 may adjust the upgrade strategy of the BMS to skip the procedure of detecting power and directly enter the upgrade state. In another example, the on-board component is an MCU. The software function of the MCU is a motor signal control function. When the motor signal control function is faulty, the server 200 may adjust the upgrade strategy of the PDU to skip the procedure of detecting a motor signal and directly enter the upgrade state. In this way, the on-board components can still continue to be upgraded when the software function is faulty, and the security and reliability of the upgrade of the on-board components can be effectively improved and the unavailability of the vehicle 100 can be reduced, thereby facilitating the normal use of the vehicle 100 by the user.
[0108] In this embodiment of the present application, the first instruction may be determined based on a user input. The first instruction is determined based on a user input in a number of implementations, including but not limited to the following:
[0109] Implementation form 1: When it is determined that the software function of the in-vehicle component is faulty, the server 200 may control the electronic device 300 to display the user interface shown in FIG. 5A, obtain a user input (e.g., a user's tap operation on the "OK" button) through the user interface, convert the user input into a first command, and send the first command to the server 200. The server 200 receives the first command. In this way, the server 200 may obtain the first command by using the electronic device 300, so that the user can remotely control the upgrade of the in-vehicle component, thereby effectively improving the user experience.
[0110] Embodiment 2: When an abnormal operation occurs in the vehicle 100, the vehicle 100 may display the user interface shown in FIG. 5A through a human machine interface (HMI), obtain a user input (e.g., a user's tap operation on an "OK" button) through the user interface, convert the user input into a first command, and send the first command to the server 200. The server 200 receives the first command. In this way, when an abnormal operation occurs in the vehicle 100 and the software function of the HMI is not faulty, the server 200 may obtain the first command using the vehicle 100, so that the user can control the upgrade of the on-board components. The abnormal operation may be, for example, the number of door openings and closings or the number of gear changes exceeding a threshold within a preset time length. This is not specifically limited in this embodiment of the present application.
[0111] Implementation form 3: When it is determined that the software function of the on-board component is faulty, the server 200 may display the user interface shown in Fig. 5A, obtain a user input (e.g., a user's tap operation on the "OK" button) through the user interface, and convert the user input into a first command. In this way, the server 200 can quickly obtain the first command, thereby effectively improving the upgrade efficiency of the on-board component and facilitating the upgrade control of the on-board component by the operation and maintenance management personnel.
[0112] In the first to third embodiments, when the software function status of the on-board components is faulty, the user can control the upgrade of the on-board components, so that the upgrade of the on-board components meets the user requirements. In addition, the user can trigger the server 200 in time to adjust the upgrade strategy, so that the on-board components can still continue to be upgraded when a fault occurs, thereby facilitating the normal use of the vehicle 100 by the user.
[0113] S402: The server 200 transmits task information of the upgrade task in response to the first command. In response, the vehicle 100 receives the task information of the upgrade task.
[0114] The task information of the upgrade task may include information about the upgrade strategy, which is used to indicate the on-board components to be upgraded. Optionally, the task information may further include an identifier (e.g., an ECU identifier) of the on-board component and a uniform resource locator (URL) of the upgrade package.
[0115] In one possible implementation, the information on the upgrade strategy includes a preset condition, which can be used by the on-board components to skip the upgrade pre-processing procedure or to directly enter the upgrade state. In this way, a preset condition is set in the information on the upgrade strategy. The preset condition can be used by the on-board components to skip the upgrade pre-processing procedure or to directly enter the upgrade state, so that the upgrade strategy can be flexibly set. In this way, the on-board components can still continue the upgrade task even when a software function is faulty.
[0116] It will be understood that the processing procedures before the on-board components are upgraded include, but are not limited to, a signal control procedure, a procedure for checking a mutex, and a procedure for checking a vehicle state. The signal control procedure may be, for example, the setting of at least one of the power-on wake-up signal (KL15) of the on-board components, the CAN network wake-up signal, and the high-voltage signal of the vehicle. The mutex check procedure may be, for example, a contention check of an on-board service. The procedure for checking a vehicle state may be, for example, a check for allowing a flag to be refreshed by the vehicle, and a check of the upgrade state of the vehicle. "The on-board components directly enter the upgrade state" may be understood as the on-board components skipping the on-board component upgrade pre-processing procedures and directly entering a state of performing an upgrade task.
[0117] Since the upgrade strategy is related to the software functions of the on-board components, the pre-set conditions are related to the software function failure states of the on-board components, and correspondingly, different software function failure states correspond to different pre-set conditions.
[0118] Example 1: The software functions of the PEPS, BMS, MCU, and PDU are all faulty. The KL15 signal (e.g., CAN network wake-up signal and power-on wake-up signal) control function is used as an example of the software function of the PEPS, and the high-voltage signal setting function is used as an example of the software function of the BMS, MCU, and PDU. In this case, the pre-set conditions are that the procedure for detecting the signal control result of the in-vehicle components, the procedure for checking the mutex (e.g., in-vehicle service conflict check), and the procedure for checking the vehicle state (e.g., checking the vehicle to allow the refresh flag, and checking the vehicle upgrade state) are omitted. Correspondingly, the upgrade strategy corresponding to the pre-set conditions may be shown in Table 1. In the upgrade strategy, the KL15 wake-up result, the execution result of pulling the high-voltage signal, the execution result of entering the upgrade mode by the vehicle domain or each domain, the execution result of allowing the refresh flag, and the execution result of checking the mutex condition (e.g., the battery voltage is insufficient or the in-vehicle diagnostic device is not removed) may be ignored.
[0119] [Table 1]
[0120] Example 2: The software function of the PEPS is faulty, and the software function of any of the on-board components, the BMS, the MCU, and the PDU, is faulty. The KL15 signal (e.g., CAN network wake-up signal and power-on wake-up signal) control function is used as an example of the software function of the PEPS, and the high-voltage signal setting function is used as an example of the software function of any of the on-board components, the BMS, the MCU, and the PDU. In this case, the pre-set conditions are that the procedure for detecting the signal control result of the on-board components, the procedure for checking the mutex (e.g., the conflict check of the on-board service), and the procedure for checking the vehicle state (e.g., the check for allowing the refresh flag by the vehicle, and the check for the upgrade state of the vehicle) are omitted. Correspondingly, the upgrade strategy corresponding to the pre-set conditions may be shown in Table 2. In the upgrade strategy, the execution result of the wake-up of the KL15, the execution result of pulling the high-voltage signal, the execution result of entering the upgrade mode by the vehicle domain or each domain, the execution result of allowing the refresh flag, and the execution result of checking the mutex condition (e.g., the battery voltage is insufficient or the on-board diagnostic device is not removed) are ignored.
[0121] [Table 2]
[0122] Example 3: The software function of the PEPS is faulty, and the KL15 signal (e.g., CAN network wake-up signal and power-on wake-up signal) control function is used as an example of the software function of the PEPS. In this case, the preset condition is that the procedure of detecting the signal control result of the in-vehicle components, the procedure of checking the mutex (e.g., in-vehicle service conflict check), and the procedure of checking the vehicle state (e.g., checking the vehicle to allow the refresh flag, and checking the vehicle upgrade state) are omitted. Correspondingly, the upgrade strategy corresponding to the preset condition may be shown in Table 3. In the upgrade strategy, the KL15 wake-up result, the execution result of entering the upgrade mode by the vehicle domain or each domain, the execution result of allowing the refresh flag, and the execution result of checking the mutex condition (e.g., the battery voltage is insufficient or the in-vehicle diagnostic device is not removed) are ignored.
[0123] [Table 3]
[0124] Example 4: The software function of any of the components of the BMS, MCU, and PDU is faulty, and the high-voltage signal setting function is used as an example of the software function of any of the components of the BMS, MCU, and PDU. In this case, the pre-set conditions are that the procedure for detecting the signal control result of the in-vehicle components, the procedure for checking the mutex (e.g., the conflict check of the in-vehicle service), and the procedure for checking the vehicle state (e.g., the check for allowing the refresh flag by the vehicle, and the check for the upgrade state of the vehicle) are omitted. Correspondingly, the upgrade strategy corresponding to the pre-set conditions may be shown in Table 4. In the upgrade strategy, the execution result of pulling the high-voltage signal, the execution result of entering the upgrade mode by the vehicle domain or each domain, the execution result of allowing the refresh flag, and the execution result of checking the mutex condition (e.g., the battery voltage is insufficient or the in-vehicle diagnostic device is not removed) are ignored.
[0125] [Table 4]
[0126] In order to reduce the impact of user's wrong operation on the upgrade of the on-board components and ensure that the upgrade of the on-board components meets the user's requirements, in one possible implementation, before the server sends the task information of the upgrade task, risk warning information may be displayed to the user, so that the user confirms the corresponding action or the user performs the corresponding action. The risk warning information may be displayed on a user interface adapted to the server 200, or may be displayed through the electronic device 200, or may be displayed on the HMI of the vehicle 100. This is not specifically limited in this embodiment of the present application.
[0127] Example 1: The server 200 displays risk warning information and obtains a first action of a user for the risk warning information. If the first action indicates that the user authorizes the server 200 to distribute the task information of the upgrade task, the server 200 distributes the task information of the upgrade task. In example 1, the server 200 can quickly obtain the user's authorization information for the task information of the upgrade task, so that the efficiency of distributing the task information of the upgrade task can be improved, thereby effectively improving the upgrade efficiency of the in-vehicle components.
[0128] Example 2: The electronic device 300 displays risk warning information and obtains a first action of the user for the risk warning information. If the first action is used to indicate that the user authorizes the server 200 to deliver task information of the upgrade task, the first action is converted into a corresponding command, and the command is sent to the server 200, so that the server 200 delivers the task information of the upgrade task. In this way, it is convenient for the user to remotely control the upgrade process of the vehicle components.
[0129] Example 3: The software function of the HMI of the vehicle 100 is not faulty, and the risk warning information can be displayed through the HMI of the vehicle 100, and a first action of the user for the risk warning information is obtained. If the first action indicates that the user allows the server 200 to deliver the task information of the upgrade task, the first action is converted into a corresponding command, and the command is sent to the server 200, so that the server 200 delivers the task information of the upgrade task. In this way, it is convenient for the user to control the upgrade process of the on-board components by using the vehicle 100.
[0130] In one possible implementation, the risk warning information may be used to indicate a second action, which includes, but is not limited to, at least one of the following steps: determining that the vehicle is in a stopped state, determining that the vehicle is in a secure area, determining that the vehicle is in an uncharged state, determining that the vehicle door is closed, and determining that the vehicle's on-board diagnostic device is removed. The second action may be performed by the user or the vehicle 100. This is not specifically limited in this embodiment of the present application. In this implementation, the risk warning information may be used to instruct the user or the vehicle to perform a corresponding action to ensure the security of the upgrade of the on-board components. For example, as shown in FIG. 5B, the risk warning information is "determine that the vehicle is in a stopped state and in a secure area, determine that the vehicle is in an uncharged state, determine that the vehicle door is closed, and determine that the on-board diagnostic device is removed." The server 200, the vehicle 100, and the electronic device 300 may all display the risk warning information and detect the user's tap operation on the "OK" button (i.e., the first action). In this case, it may be determined that the user has authorized the server 200 to distribute the task information of the upgrade task.
[0131] To further improve the security of the upgrade of the in-vehicle components, the server 200 may further perform identity authentication on the user before the user's authorization information for the upgrade task is obtained. For example, the server 200 may obtain user information using the electronic device 300 or the HMI of the vehicle 100, and compare the obtained user information with pre-stored user information associated with the vehicle 100 to perform user identity verification. The user information may include, but is not limited to, the user's face information, voiceprint information, and iris information.
[0132] S403: The vehicle 100 upgrades on-board components based on the information about the upgrade strategy.
[0133] In one possible implementation, before the vehicle 100 upgrades the on-board components, the server 200 may further send a second command to the vehicle 100. The second command may be used to instruct the vehicle 100 to check the speed and gear state of the vehicle 100. Correspondingly, the vehicle 100 receives the second command, and checks the speed and gear state of the vehicle 100 in response to the second command. When it is determined that the speed and gear state of the vehicle 100 meets the upgrade condition (e.g., the speed is zero and the gear is P gear), the on-board components are upgraded. In this way, the vehicle 100 can check the speed and gear state, so that the upgrade of the on-board components is performed while ensuring the safety of the user, thereby effectively improving the security of the upgrade of the on-board components.
[0134] In one possible implementation, the server 200 may further obtain a third instruction. If the third instruction is used to indicate that the user authorizes the server 200 to deliver an upgrade package corresponding to the upgrade task, the server 200 sends the upgrade package to the vehicle 100. In this way, the user can decide whether the on-board components are upgraded by using the local upgrade package of the on-board components or by using the upgrade package delivered by the server 200. In this way, the upgrade of the on-board components further meets the user requirements.
[0135] The vehicle 100 upgrades on-board components based on information regarding an upgrade strategy in multiple implementations, including but not limited to the following:
[0136] Implementation form 1: The vehicle 100 receives an upgrade package corresponding to an upgrade task, and upgrades the on-board components according to the information on the upgrade strategy and the upgrade package. This can effectively improve the timeliness of updating the software functions of the on-board components.
[0137] Implementation form 2: The vehicle 100 upgrades on-board components based on the information about the upgrade strategy and the local upgrade package of the vehicle 100. In this way, the upgrade efficiency of the on-board components can be effectively improved, so that the vehicle 100 can be returned to a normal use state more quickly, thereby facilitating the normal use of the vehicle 100 by the user.
[0138] For example, for a specific implementation, see Figure 6. S403 may include the following steps:
[0139] S601: The vehicle 100 determines whether an upgrade package corresponding to an upgrade task needs to be downloaded.
[0140] For example, the vehicle 100 queries whether an upgrade package exists locally. If the upgrade package exists locally, S602A is executed, or if the upgrade package does not exist locally, S602B is executed.
[0141] S602A: The vehicle 100 loads the local upgrade package.
[0142] S602B: The vehicle 100 downloads the upgrade package.
[0143] For example, the task information for an upgrade task may include a URL of the upgrade package, and the vehicle 100 may download the upgrade package from the URL.
[0144] S603: The vehicle 100 verifies the integrity of the upgrade package.
[0145] It should be appreciated that the vehicle 100 executes S604 after verifying the integrity of the upgrade package.
[0146] S604: The vehicle 100 verifies the validity of the upgrade package.
[0147] It should be understood that the vehicle 100 executes S605 after verifying the integrity of the upgrade package.
[0148] S605: The vehicle 100 skips relevant processing steps based on the information about the upgrade strategy.
[0149] It will be understood that "omitting an associated processing step" may mean that the associated processing step is not performed, or that the associated processing step is performed but the results of the processing step are ignored.
[0150] For example, the preset condition of the information on the upgrade strategy indicates that the omitted related processing procedures may include a signal control procedure, a procedure for checking a mutex, and a procedure for checking a vehicle state. The signal control procedure may be, for example, the setting of at least one of a power-on wake-up signal (KL15) of an on-board component, a CAN network wake-up signal, and a high-voltage signal of the vehicle. The mutex check procedure may be, for example, a contention check of an on-board service. The vehicle state check procedure may be, for example, a check for allowing a flag to be refreshed by the vehicle, and a check of the upgrade status of the vehicle. Specifically, in S605, the vehicle 100 may skip the procedure for detecting a signal control result of an on-board component, the procedure for checking a mutex, and the procedure for checking a vehicle state. Alternatively, the vehicle 100 may execute the procedure for detecting a signal control result of an on-board component, the procedure for checking a mutex, and the procedure for checking a vehicle state, but ignore the processing results of the related procedures. For example, the following execution results are ignored: wake-up results for KL15, execution results for pulling the high voltage signal, execution results for entering upgrade mode by the vehicle domain or each domain, execution results for enabling the refresh flag, and execution results for checking mutex conditions (e.g., battery voltage is low or onboard diagnostic device is not removed).
[0151] S606: The vehicle 100 compares the version of the upgrade package with the existing versions of the on-board components.
[0152] It should be understood that the vehicle 100 needs to compare the version of the upgrade package with the existing version of the on-board components to determine whether the on-board components need to be upgraded. After determining that the on-board components need to be upgraded, the vehicle 100 executes S607 to upgrade the on-board components.
[0153] S607: The vehicle 100 refreshes the upgrade package of the on-board components.
[0154] It should be understood that the vehicle 100 refreshes the upgrade packages of the on-board components, resulting in the on-board components being upgraded.
[0155] In the embodiment shown in FIG. 4, the software function status of the on-board components is associated with the upgrade strategy, so that the server 200 can adjust the upgrade strategy of the on-board components based on the software function status of the on-board components. For example, when the software functions related to the security requirements of the vehicle 100 (e.g., the communication function or the vehicle speed detection function) are running normally, the impact of the failure of some software functions of the on-board components not related to the security requirements (e.g., the vehicle high voltage signal setting function or the flag status setting function) on the upgrade process of the on-board components is ignored. In this way, the on-board components can still continue to be upgraded when the software functions are faulty, and the security and reliability of the upgrade of the on-board components can be effectively improved and the unavailability of the vehicle 100 can be reduced, thereby facilitating the normal use of the vehicle 100 by the user.
[0156] In this embodiment of the present application, in order to improve the security and reliability of the upgrade of the in-vehicle components, a corresponding security mechanism is further set in this embodiment of the present application. The security mechanism includes but is not limited to the following implementations:
[0157] Implementation 1: The server 200 may further sign the task information of the upgrade task based on the first certificate of the vehicle 100 to obtain signed task information, and then send the signed task information to the vehicle 100. The signed task information may be used to verify the security of the task information. In this way, the vehicle 100 may verify the signed information carried in the signed task information after receiving the signed task information. The vehicle 100 may sign the task information of the upgrade task based on a signature algorithm. The signature algorithm may be, for example, any one of MD5, SHA-1, SHA-256, and HMAC-SHA256. This is not specifically limited in this embodiment of the present application.
[0158] It will be appreciated that the first certificate may be a certificate issued to the vehicle 100 by a certificate authority and is used to uniquely identify the legal identity of the vehicle 100. The first certificate may be pre-configured in the server 200 or may be requested by the server 200 from a certificate authority, which is not limited in this embodiment of the present application.
[0159] Implementation 2: The server 200 may transmit task information of the upgrade task using a datagram transport layer security (DTLS) channel.
[0160] The above implementations may be implemented separately or in combination.
[0161] Similarly, to improve security of the upgrade package corresponding to the upgrade task, the server 200 may further sign the upgrade package based on a second certificate of the vehicle 100 to obtain a signed upgrade package, and send the signed upgrade package. The second certificate may be a package-specific certificate, and the package-specific certificate may be a certificate issued by a certificate authority to a supplier of the upgrade package.
[0162] 7 is a schematic diagram of a secure interaction scenario to which an embodiment of the present application is applicable. A mobile phone is used as an example of the electronic device 300, and the server 200 includes an OTA server and a content delivery network (CDN).
[0163] The OTA server may assign a token (TOKEN) to the mobile phone to uniquely identify the validity of the identity information of the mobile phone, so that the information interaction between the mobile phone and the OTA is authenticated based on the token, thereby effectively improving the security of communication between the mobile phone and the OTA server.
[0164] In one possible implementation, the OTA server may receive a first user command from the mobile phone, create a corresponding upgrade task based on the first user command, sign task information of the upgrade task using an RSA algorithm, and deliver the signed task information to the vehicle 100 through a DTLS channel. In this manner, the vehicle 100 may verify the signature of the task information to ensure the accuracy of the task information.
[0165] Optionally, the OTA server receives a second user instruction from the mobile phone, indicating to deliver the upgrade package, and forwards the second user instruction to the CDN. After signing the upgrade package using the RSA algorithm, the CDN sends the upgrade package to the vehicle 100. In this way, the vehicle 100 can verify the signature of the upgrade package to effectively ensure the accuracy of the upgrade package.
[0166] For ease of understanding, the following describes implementation details of the interaction between the vehicle 100 and the server 200 for upgrading on-board components in this embodiment of the present application with specific reference to the accompanying drawings.
[0167] See, for example, Figures 8A-1, 8A-2, 8B-1, and 8B-2. The process of the vehicle 100 and the server 200 interacting with each other to upgrade on-board components includes a task delivery phase, an upgrade package download phase, an upgrade verification phase, a pre-upgrade processing phase, an upgrade phase, a boot phase, and a post-upgrade processing phase.
[0168] The task delivery phase includes the following steps:
[0169] S801: The server 200 transmits wake-up information to the vehicle 100. In response, the vehicle 100 receives the wake-up information.
[0170] For example, the wake-up information may be short message information.
[0171] S802: The vehicle 100 starts a non-sleep mode.
[0172] It should be understood that initiating a non-sleep mode by the vehicle 100 may prohibit the upgrade device (e.g., the T-BOX) from going to sleep.
[0173] S803: The vehicle 100 sends a registration request to the server 200. In response, the server 200 receives the registration request.
[0174] For example, the registration request may carry identification information (e.g., a vehicle identification number, VIN) of the vehicle 100, such that the server 200 may complete registration of the vehicle 100 based on the VIN of the vehicle 100 after receiving the registration request.
[0175] S804: The server 200 transmits task information of the upgrade task. In response, the vehicle 100 receives the task information.
[0176] S805: The vehicle 100 verifies the task information.
[0177] For example, the vehicle 100 may verify whether the signature of the task information is valid and whether the task information is intact. When it is determined that the signature of the task information is valid and the task information is intact, the vehicle 100 executes S806.
[0178] S806: The vehicle 100 transmits response information. In response, the server 200 receives the response information.
[0179] It should be understood that the response information may be used to indicate that the vehicle 100 has successfully received the task information of the upgrade task, and when the response information indicates that the vehicle 100 has successfully received the task information of the upgrade task, the vehicle 100 executes S807.
[0180] The upgrade package download phase includes the following steps:
[0181] S807: The vehicle 100 checks the vehicle signal control.
[0182] It should be understood that if the vehicle signal control function of the on-board component is faulty and the information on the upgrade strategy in the upgrade information of the upgrade task is to omit the procedure of checking the vehicle signal control, the vehicle 100 executes S807, but ignores the check result of the vehicle signal control, and continues to execute S808. For example, the vehicle signal control function of the on-board component is faulty, and as a result, the on-board component cannot set the MDC wake-up signal, the vehicle high-voltage signal, and the vehicle CAN network wake-up signal. The vehicle 100 checks the MDC wake-up signal, the vehicle high-voltage signal, and the vehicle CAN network wake-up signal, and finds that the MDC wake-up signal, the vehicle high-voltage signal, and the vehicle CAN network wake-up signal are not present. However, the vehicle 100 ignores the check result of the vehicle signal, and continues to execute S808. In this way, the upgrade process of the on-board component can still continue when the software function of the on-board component is faulty.
[0183] S808: The vehicle 100 downloads the upgrade package.
[0184] For example, the vehicle 100 downloads the upgrade package based on a URL in the task information of the upgrade task.
[0185] S809: The vehicle 100 reports the task status to the server 200.
[0186] It should be appreciated that "task status" may refer to the upgrade phase of an upgrade task.
[0187] S810: The vehicle 100 verifies the upgrade package.
[0188] For example, the vehicle 100 verifies the validity and integrity of the upgrade package and executes S811 after the verification is successful.
[0189] The upgrade verification phase includes the following steps:
[0190] S811: The server 200 transmits user permission information. In response, the vehicle 100 receives the user permission information.
[0191] It should be understood that when the user determines that he or she agrees to upgrade the on-board components, the server 200 may send corresponding user authorization information to the vehicle 100, such that the vehicle 100 upgrades the on-board components.
[0192] The pre-upgrade phase includes the following steps:
[0193] S812: The vehicle 100 performs a mutex check.
[0194] It should be understood that if the information regarding the upgrade strategy in the upgrade information of the upgrade task is to omit the mutex check procedure, the vehicle 100 executes S812 but ignores the mutex check result and continues to execute S813. For example, the mutex check result may be that the battery voltage is insufficient and / or that the on-board diagnostic device has not been removed, and the vehicle 100 may ignore the mutex check result and continue to execute S813, such that the on-board component upgrade process continues.
[0195] S813: The vehicle 100 checks the vehicle signal control.
[0196] Similarly, in the upgrade pre-processing phase, the vehicle 100 also needs to check the vehicle signal control. If the information on the upgrade strategy in the upgrade information of the upgrade task is to omit the procedure of checking the vehicle signal control, the vehicle 100 executes S813, but ignores the check result of the vehicle signal control, and continues to execute S814.
[0197] S814: The vehicle 100 performs a security check.
[0198] For example, the process that the vehicle 100 may perform security checks may be a speed check, a gear check, a charging gun status check, a power battery check, and a parking brake status check to ensure that the vehicle 100 is in a stopped and uncharged state. In this way, the security of upgrading on-board components can be improved.
[0199] S815: The vehicle 100 reports the task status to the server 200.
[0200] Similarly, during the pre-upgrade processing phase, the vehicle 100 also reports the task status of the upgrade tasks to the server 200.
[0201] S816: The vehicle 100 compares the current versions of the on-board components with the version of the upgrade package.
[0202] It should be appreciated that when the vehicle 100 determines that the current version of an on-board component differs from the version in the upgrade package, the vehicle 100 executes S817 through S822.
[0203] The upgrade phase includes the following steps:
[0204] S817: The vehicle 100 checks the vehicle signal control.
[0205] Similarly, in the upgrade phase, the vehicle 100 also needs to check the vehicle signal control. If the information on the upgrade strategy in the upgrade information of the upgrade task is to omit the procedure of checking the vehicle signal control, the vehicle 100 executes S817, but ignores the check result of the vehicle signal control, and continues to execute S818.
[0206] S818: The vehicle 100 performs a security check.
[0207] The specific implementation of S818 is the same as that of S814. For details, please refer to the related description of S814.
[0208] S819: The vehicle 100 notifies the vehicle control unit (VCU) to enter the upgrade mode.
[0209] It should be understood that if the information regarding the upgrade strategy in the upgrade information of the upgrade task is to omit the procedure of checking the vehicle status, and the procedure of checking the vehicle status is to check the vehicle upgrade status, then the vehicle 100 executes S819 but ignores the result of checking the vehicle upgrade status, e.g., ignoring the result of entering upgrade mode by the VCU, and continues to execute S820.
[0210] S820: The vehicle 100 notifies each domain to enter upgrade mode.
[0211] Similarly, if the information on the upgrade strategy in the upgrade information of the upgrade task is to omit the procedure of checking the vehicle status, and the procedure of checking the vehicle status is to check the vehicle upgrade status, the vehicle 100 executes S820 but ignores the result of checking the vehicle upgrade status, for example, ignoring the result of entering upgrade mode by each domain, and continues to execute S821.
[0212] S821: The vehicle 100 reports the task status to the server 200.
[0213] Similarly, during the upgrade phase, the vehicle 100 also reports the task status of the upgrade task to the server 200.
[0214] S822: The vehicle 100 refreshes the upgrade package of the on-board components.
[0215] It should be understood that the process of the vehicle 100 refreshing an upgrade package of an on-board component is a process of refreshing the program code corresponding to the upgrade package.
[0216] The start-up phase includes, for example, checking the vehicle's enable refresh flag and checking the vehicle's upgrade status.
[0217] S823: The vehicle 100 checks the vehicle signal control.
[0218] Similarly, in the upgrade phase, the vehicle 100 also needs to check the vehicle signal control. If the information on the upgrade strategy in the upgrade information of the upgrade task is to omit the procedure of checking the vehicle signal control, the vehicle 100 executes S823 but ignores the check result of the vehicle signal control and continues to execute S824.
[0219] S824: The vehicle 100 reports the task status to the server 200.
[0220] Similarly, during the upgrade phase, the vehicle 100 also reports the task status of the upgrade task to the server 200.
[0221] S825: The vehicle 100 activates the software functions of the on-board components.
[0222] It should be appreciated that after the vehicle 100 completes refreshing the upgrade packages of the on-board components, the vehicle 100 may activate the software functions of the on-board components.
[0223] The post-upgrade processing phase includes the following steps:
[0224] S826: The vehicle 100 controls the on-board components to set vehicle signals.
[0225] It should be understood that after the software functions of the on-board components are activated, the vehicle 100 may control the on-board components to set vehicle signals, such as a vehicle high voltage signal and a vehicle CAN network wake-up signal.
[0226] S827: The vehicle 100 notifies each domain to exit the upgrade mode.
[0227] S828: The vehicle 100 collects current version information of the on-board components.
[0228] It should be appreciated that the vehicle 100 collects current version information of on-board components to facilitate management of on-board component upgrades.
[0229] S829: The vehicle 100 collects a task log.
[0230] It should be understood that the task log is a log that records the execution process of the upgrade task, and the log may include abnormality information in the process of the on-board components performing the current upgrade task, so that the vehicle 100 can optimize the subsequent upgrade process of the on-board components based on the log.
[0231] S830: The vehicle 100 notifies the VCU to exit the upgrade mode.
[0232] It should be understood that the process of the vehicle 100 and the server 200 interacting with each other to upgrade the on-board components shown in Figures 8A-1, 8A-2, 8B-1, and 8B-2 is an improvement of the upgrade method shown in Figure 4, and the technical effect achieved is the same as that of the upgrade method shown in Figure 4. Specifically, when the software function of the on-board components is faulty, some processing results are ignored, so that the upgrade process of the on-board components can be continuously performed, and the security and reliability of the upgrade of the on-board components can be effectively improved and the unavailability of the vehicle 100 can be reduced, thereby facilitating the normal use of the vehicle 100 by the user.
[0233] DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS Hereinafter, an apparatus in one embodiment of the present application will be described with reference to the accompanying drawings.
[0234] Figure 9 is a possible schematic diagram of the structure of an upgrade device according to the aforementioned embodiment of the present application. The device 900 can be configured to implement the method performed by the server 200 in the embodiment shown in Figure 4. The device 900 can be a server, or a server chip or integrated circuit, which is specifically limited in this embodiment of the present application.
[0235] For example, the device 900 may include A processing module 901 configured to obtain a first instruction when a software function of an on-board component is faulty, the first instruction being used to indicate an upgrade strategy for the on-board component, the upgrade strategy being associated with a software function status of the on-board component; and a transceiver module 902 configured to transmit task information of the upgrade task in response to a first command, the task information including information regarding an upgrade strategy, the information regarding the upgrade strategy being used to indicate on-board components to be upgraded; may include.
[0236] The information about the upgrade strategy includes pre-configuration conditions that are used by the on-board components to either skip pre-upgrade procedures or to directly enter the upgrade state.
[0237] In one possible design, the transceiver module 902 may be further configured to transmit a second command, the second command being used to instruct the vehicle to check its speed and gear status.
[0238] Optionally, the device may further include a display module 903. Before the transceiver module 902 transmits the task information of the upgrade task, the display module 903 may display the risk warning information. The processing module 901 may further obtain a first action of the user on the risk warning information. The first action is used to indicate that the user allows the server to deliver the task information of the upgrade task.
[0239] The first command is determined based on a user input.
[0240] Optionally, the processing module 901 may further obtain a third instruction. The third instruction is used to indicate that the user authorizes the server to deliver an upgrade package corresponding to the upgrade task. The transceiver module 902 may be further configured to transmit the upgrade package to the vehicle.
[0241] Optionally, the processing module 901 may further sign the task information of the upgrade task based on the first certificate of the vehicle to obtain signed task information. The signed task information may be used to verify the security of the task information.
[0242] Figure 10 is a schematic diagram of a possible structure of another upgrade device according to the aforementioned embodiment of the present application. The device 1000 may be configured to implement the method performed by the vehicle 100 in the embodiment shown in Figure 4. The device 1000 may be a vehicle, or a chip or integrated circuit of the vehicle, which is specifically limited in this embodiment of the present application.
[0243] For example, the device 1000 may include a transceiver module 1001 configured to receive task information for an upgrade task, the task information including information regarding an upgrade strategy, the information regarding the upgrade strategy being associated with a software feature status of the on-board component; and a processing module 1002 configured to upgrade the on-board component based on the information regarding the upgrade strategy. may include.
[0244] The information about the upgrade strategy includes pre-configuration conditions that are used by the on-board components to either skip pre-upgrade procedures or to directly enter the upgrade state.
[0245] Optionally, the transceiver module 1001 may further receive a second command, which is used to instruct to check the speed and gear status of the vehicle.
[0246] Optionally, the transceiver module 1001 may be further configured to receive an upgrade package corresponding to the upgrade task. The processing module 1002 may be further configured to upgrade the in-vehicle components based on the information regarding the upgrade strategy and the upgrade package.
[0247] Optionally, the processing module 1002 may further upgrade the on-board components based on information regarding the upgrade strategy and the vehicle's local upgrade package.
[0248] Optionally, the processing module 1002 may be further configured to verify a signature of the task information based on a first certificate of the vehicle, and upgrade the on-board components based on the information on the upgrade strategy only when it is determined that the signature verification of the task information is successful.
[0249] An embodiment of the present application further provides an electronic device. The electronic device may be configured to implement the upgrade method executed by the electronic device 300. For example, the electronic device includes a display module configured to display risk warning information, and an acquisition module configured to acquire a first action of a user for the risk warning information. The first action is used to indicate that the user allows the cloud to deliver task information of the upgrade task. The risk warning information is used to indicate a second action, and the second action includes at least one of the following steps: determining that the vehicle is in a stopped state, determining that the vehicle is in a secure area, determining that the vehicle is in an uncharged state, determining that the door of the vehicle is in a closed state, and determining that the on-board diagnostic device of the vehicle is removed.
[0250] An embodiment of the present application further provides a vehicle. The vehicle may include a processor. The processor is configured to execute the method performed by the vehicle 100 in the embodiment shown in FIG.
[0251] In one possible implementation, the vehicle further includes a memory configured to store computer programs or instructions.
[0252] In one possible implementation, the vehicle further includes a transceiver configured to receive or transmit information.
[0253] An embodiment of the present application further provides a server, the server including a processor, the processor configured to execute the method executed by the server in the embodiment shown in FIG.
[0254] Optionally, the server further comprises a memory configured to store computer programs or instructions.
[0255] Optionally, the server further comprises a transceiver configured to receive or transmit information.
[0256] In one possible implementation, the aforementioned server is a single server or a server cluster including multiple sub-servers. When the server is a server cluster including multiple sub-servers, the multiple sub-servers jointly execute the aforementioned upgrade method.
[0257] An embodiment of the present application further provides a chip system. See Fig. 11. The chip system 1100 includes at least one processor. When program instructions are executed in the at least one processor 1101, the upgrade method in the above embodiment is implemented.
[0258] Optionally, the chip system further includes a communication interface 1103, which is configured to input or output information.
[0259] Optionally, the chip system further includes a memory 1102. The memory 1102 is coupled to the processor using a communication interface 1103 and configured to store the instructions, such that the processor reads the instructions stored in the memory through the communication interface 1103.
[0260] It should be understood that the connection medium between the processor 1101, the memory 1102, and the communication interface 1103 is not limited in this embodiment of the present application. In this embodiment of the present application, the memory 1102, the processor 1101, and the communication interface 1103 are connected through a communication bus 1104 in FIG. 11. The bus is represented by a bold line in FIG. 11, and the connections between the other components are merely examples for explanation and should not be construed as limiting. The bus may include an address bus, a data bus, a control bus, etc. For ease of representation, only one bold line is used to represent a bus in FIG. 11, but it does not indicate that there is only one bus or only one type of bus, etc.
[0261] A module for receiving / transmitting (transceiver module) may be an interface circuit of an apparatus, configured to receive / transmit signals from another apparatus. For example, when the apparatus is implemented in the manner of a chip, the transceiver module is an interface circuit of the chip, configured to receive / transmit signals from another chip or apparatus.
[0262] An embodiment of the present application further provides a computer program product including instructions, which, when executed on the aforementioned device, executes the upgrade method in the aforementioned embodiment.
[0263] An embodiment of the present application provides a computer-readable storage medium, which stores a computer program, which, when executed, implements the upgrade method in the above embodiment.
[0264] For example, the division into modules or units is merely a logical division of functions, and may be other divisions in actual implementation. For example, multiple units or components may be combined or integrated into another device, and some features may be ignored or not implemented. In addition, the shown or described interconnections, direct connections, or communication connections may be implemented using some interfaces. Indirect couplings or communication connections between devices or units may be implemented in electrical, mechanical, or other forms.
[0265] The units described as separate parts may or may not be physically separate, and the parts shown as units may be one or more physical units, i.e., located in one place or distributed in multiple different places. Some or all of the units may be selected based on actual requirements to achieve the objectives of the solutions of the embodiments.
[0266] In addition, the functional units in the embodiments of the present application may be integrated into one processing module, or each of the units may exist physically alone, or two or more units may be integrated into one unit. The integrated unit may be implemented in the form of hardware or in the form of a software functional unit.
[0267] In the embodiment of the present application, the module division is an example and is merely a logical function division. In the actual implementation, another division method may be used. In addition, the functional modules in the embodiment of the present application may be integrated into one processor, or each of the modules may exist physically alone, or two or more modules may be integrated into one module. The integrated module may be implemented in the form of hardware or in the form of a software functional module.
[0268] All or part of the methods in the embodiments of the present application may be implemented by using software, hardware, firmware, or any combination thereof. When software is used to implement the embodiments, the aforementioned embodiments may be fully or partially implemented in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded into a computer and executed, the procedures or functions according to the embodiments of the present application are generated in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network, a network device, a user equipment, or another programmable device. The computer instructions may be stored in a computer-readable storage medium or transmitted from a computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions may be transmitted from a website, computer, server, or data center to another website, computer, server, or data center in a wired (e.g., coaxial cable, optical fiber, or digital subscriber line (DSL)) or wireless (e.g., infrared, radio, or microwave) manner. The computer-readable storage medium may be any available medium accessible by a computer, or a data storage device that integrates one or more available media, such as a server or a data center. The available medium may be a magnetic medium (e.g., a floppy disk, a hard disk, a magnetic tape), an optical medium (e.g., a digital video disc (DVD)), a semiconductor medium, etc.
[0269] In the embodiments of the present application, when there is no logical contradiction, the embodiments may be mutually referenced. For example, the methods and / or terms in the method embodiments may be mutually referenced, and the functions and / or terms in the device embodiments may be mutually referenced. For example, the functions and / or terms between the device embodiments and the method embodiments may be mutually referenced.
[0270] Those skilled in the art can make various modifications and variations to this application without departing from the scope of this application. This application is intended to cover these modifications and variations of this application as long as they are within the scope of protection defined by the claims of this application and their equivalent technologies. [Explanation of symbols]
[0271] 100 vehicles 101 In-vehicle components 102 Upgrade components, upgrade devices 200 Servers 300 Electronic Devices 900, 1000 devices 901, 1002 Processing Module 902, 1001 Transceiver Modules 903 Display Module 1100 Chip System 1101 Processor 1102 Memory 1103 Communication Interface 1104 Communication Bus
Claims
1. 1. An upgrade method, comprising: obtaining a first instruction when a software function of an on-board component is faulty, the first instruction being used to indicate an upgrade strategy of the on-board component, the upgrade strategy being associated with a software function status of the on-board component; sending task information of an upgrade task in response to the first command, the task information including information regarding the upgrade strategy, the information regarding the upgrade strategy being used to indicate the on-vehicle components to be upgraded; A method comprising:
2. 2. The method of claim 1, wherein the information regarding the upgrade strategy includes pre-configured conditions, the pre-configured conditions being used by the on-board components to skip pre-upgrade procedures or to directly enter an upgrade state.
3. The method further comprising: transmitting a second command, the second command being used to instruct the vehicle to check its speed and gear status; 3. The method of claim 1 or 2, further comprising:
4. Before the step of transmitting task information of an upgrade task, the method further comprises: displaying risk warning information; obtaining a first action of a user in response to the risk warning information, the first action being used to indicate that the user authorizes a server to distribute the task information of the upgrade task; 4. The method of claim 1, further comprising:
5. The method of claim 1 , wherein the first instruction is determined based on a user input.
6. The method further comprising: obtaining a third instruction, the third instruction being used to indicate that the user authorizes the server to deliver an upgrade package corresponding to the upgrade task; transmitting the upgrade package to the vehicle; 6. The method of claim 1, further comprising:
7. The method further comprising: signing the task information of the upgrade task based on a first certificate of the vehicle to obtain the signed task information, the signed task information being used to verify security of the task information; 7. The method of claim 2, further comprising:
8. 1. An upgrade method, comprising: receiving task information for an upgrade task, the task information including information regarding an upgrade strategy, the information regarding the upgrade strategy being associated with software feature statuses of on-vehicle components; upgrading the on-vehicle components based on the information regarding the upgrade strategy; A method comprising:
9. 9. The method of claim 8, wherein the information regarding the upgrade strategy includes pre-configured conditions, the pre-configured conditions being used by the on-board components to skip pre-upgrade procedures or to directly enter an upgrade state.
10. The method further comprising: receiving a second command, the second command being used to instruct the vehicle to check speed and gear status; 10. The method of claim 8 or 9, further comprising:
11. The step of upgrading the on-vehicle components based on the information regarding the upgrade strategy comprises: receiving an upgrade package corresponding to the upgrade task; upgrading the on-vehicle components based on the upgrade strategy and the information regarding the upgrade package.
11. The method according to any one of claims 8 to 10, comprising:
12. The step of upgrading the on-vehicle components based on the information regarding the upgrade strategy comprises: upgrading the on-board components based on the upgrade strategy and the information regarding local upgrade packages for the vehicle.
11. The method according to any one of claims 8 to 10, comprising:
13. Prior to the step of upgrading the on-board components based on the information regarding the upgrade strategy, the method further comprises: verifying a signature of the task information based on a first certificate of the vehicle; determining that signature verification of the task information is successful; 13. The method of any one of claims 8 to 12, further comprising:
14. 1. An upgrade method, comprising: displaying risk warning information; obtaining a first action of a user in response to the risk warning information, the first action being used to indicate that the user authorizes delivery of task information of an upgrade task to a cloud; A method comprising:
15. The risk warning information is used to indicate a second action, the second action comprising: determining that the vehicle is at a standstill; determining that the vehicle is in a secure domain; determining that the vehicle is in an uncharged state; determining that a door of the vehicle is closed; determining that an on-board diagnostic device of the vehicle has been removed; The method of claim 14, comprising at least one of:
16. An upgrade device, comprising: a processing module configured to obtain a first instruction when a software function of an on-board component is faulty, the first instruction being used to indicate an upgrade strategy for the on-board component, the upgrade strategy being associated with a software function status of the on-board component; a transceiver module configured to transmit task information of the upgrade task in response to the first command, the task information including information regarding the upgrade strategy, the information regarding the upgrade strategy being used to indicate the on-board components to be upgraded; 13. An apparatus comprising:
17. An upgrade device, comprising: a transceiver module configured to receive task information for an upgrade task, the task information including information regarding an upgrade strategy, the information regarding the upgrade strategy being associated with software feature statuses of on-board components; and a processing module configured to upgrade the on-board components based on the information regarding the upgrade strategy; and 13. An apparatus comprising:
18. a display module configured to display the risk warning information; an acquisition module configured to acquire a first action of a user in response to the risk warning information, the first action being used to indicate that the user authorizes a server to deliver task information of an upgrade task; An electronic device comprising:
19. The risk warning information is used to indicate a second action, the second action comprising: determining that the vehicle is at a standstill; determining that the vehicle is in a secure domain; determining that the vehicle is in an uncharged state; determining that a door of the vehicle is closed; determining that an on-board diagnostic device of the vehicle has been removed; 20. The device of claim 18, comprising at least one of:
20. A vehicle comprising a memory and a processor, the memory is configured to store a computer program; The processor is configured to execute the computer program stored in the memory to perform the method according to any one of claims 8 to 13. vehicle.
21. A server comprising a memory and a processor; the memory is configured to store a computer program; A server, wherein the processor is configured to execute the computing program stored in the memory to perform the method according to any one of claims 1 to 7, or to perform the method according to any one of claims 8 to 13, or to perform the method according to any one of claims 14 to 15.
22. 16. A computer-readable storage medium having stored thereon instructions that, when executed, perform a method according to any one of claims 1 to 7, 8 to 13, or 14 to 15.
Citation Information
Patent Citations
Remote upgrading method, equipment and device for vehicle-mounted central control system, and medium
CN112328282A
Information processing system and program
JP2010186279A
Electronic control device
JP2014235652A
Information processing program, information processing method, and information processing device
JP2015079468A
Information processing apparatus, management device, control method of information processing apparatus, control method of management device, and program
JP2016148947A
