Vehicle updating method, dividing method and vehicle updating system

Abstract

The invention provides a vehicle updating method, a dividing method and a vehicle updating system. The vehicle updating method is applied to cloud equipment, and comprises the following steps: receiving identification information corresponding to a target software resource in at least one type of software resources sent by a vehicle; wherein the at least one type of software resources comprises different function modules which are used for dividing a cabin domain system of the vehicle in a layered manner according to a software architecture in advance; determining a target update package corresponding to the target software resource from the at least one first update package based on the identification information corresponding to the target software resource; wherein each first update package carries identification information of the corresponding category of software resources; and pushing the target update package corresponding to the target software resource to the vehicle so as to update the target software resource in the vehicle. According to the technical scheme, the vehicle updating efficiency is improved, and the user experience is improved.

Description

Technical Field

[0001] The present application relates to, but is not limited to, the field of vehicle renewal technology, and in particular to a vehicle renewal method, a division method, and a vehicle renewal system. Background Art

[0002] Currently, when a vehicle is updated, since the system firmware pre-installs a large number of applications, the car model resources, theme resources, etc. of each application are packaged in their own program packages. Therefore, each update requires downloading the entire firmware package, resulting in too low vehicle update frequency, too slow download speed, and too long upgrade time, thereby reducing vehicle update efficiency. Summary of the Invention

[0003] In view of this, embodiments of the present application provide a vehicle updating method, a partitioning method, and a vehicle updating system.

[0004] The technical solution of the embodiment of the present application is implemented as follows:

[0005] In a first aspect, an embodiment of the present application provides a vehicle update method, which is characterized in that it is applied to a cloud device, including: receiving identification information corresponding to a target software resource in at least one category of software resources sent by a vehicle; wherein, at least one category of software resources includes different functional modules of the vehicle's cockpit domain system pre-divided into layers according to the software architecture; based on the identification information corresponding to the target software resource, determining a target update package corresponding to the target software resource from at least one first update package; wherein, each first update package carries the identification information of its corresponding category of software resources; and pushing the target update package corresponding to the target software resource to the vehicle to update the target software resource in the vehicle.

[0006] According to the above technical means, when the vehicle responds to an update event, it receives identification information corresponding to a target software resource in at least one type of software resource sent by the vehicle; wherein, at least one type of software resource is different functional modules that divide the vehicle cockpit domain system into layers according to the software architecture; it is able to determine a target update package from at least one first update package based on the identification information corresponding to the target software resource, so as to perform an update based on the target update package. When only the software resources corresponding to a certain function in the vehicle cockpit domain system need to be updated, compared with the prior art of updating the entire firmware of the cockpit domain system, the present application only requires OTA transmission of the software resources corresponding to the function that needs to be updated to the vehicle, thereby reducing the amount of updates during vehicle updates, reducing the time required for updates, and enabling updates without strict network requirements. Thus, the efficiency of vehicle updates is improved, and the user experience is enhanced.

[0007] In some embodiments, a vehicle model code sent by the vehicle is received; wherein, vehicles corresponding to different vehicle model codes are adapted to software resources with different version numbers; a first target version number corresponding to the target software resource is determined based on the vehicle model code; and a target update package corresponding to the target software resource is determined from the at least one first update package based on the first target version number and identification information corresponding to the target software resource.

[0008] According to the above technical means, a vehicle model code is received from a vehicle, and a first target version of a target software resource compatible with the vehicle is determined based on the vehicle model code. Furthermore, a target update package is determined from at least one first update package based on the identification information of the target software resource and the first target version. This allows for rapid determination of the target update package compatible with the vehicle, improving vehicle update efficiency.

[0009] In some embodiments, the identification information of any type of software resource includes a software component number and a version number; the identification information of the target software resource includes a target software component number and a target version number; at least one second update package is determined from the at least one first update package based on the target software component number; the second update package represents an update package corresponding to a software resource with the same target software component number; at least one third update package is determined from the at least one second update package based on the target version number; the version number of the third update package is higher than the target version number; the target update package is determined from the at least one third update package based on the first target version number.

[0010] According to the above technical means, at least one first update package is screened by the target software version number to obtain at least one second update package with the same target software version number; at least one second update package is screened based on the target version number to obtain at least one third update package with a version number higher than the target version number; and a target update package is determined from the at least one third update package based on the first target version number adapted for the vehicle. This improves the speed of obtaining the target update package, thereby improving the efficiency of vehicle updates.

[0011] In a second aspect, an embodiment of the present application provides a vehicle update method, which is characterized in that it is applied to a vehicle and includes: in response to an update event of a target software resource in at least one type of software resources for a vehicle cockpit domain system, sending identification information corresponding to the target software resource to a cloud device; wherein, at least one type of software resource includes different functional modules of the vehicle's cockpit domain system that are pre-divided into layers according to the software architecture; downloading a target update package pushed by the cloud device; wherein, the target update package is determined by the cloud device from at least one first update package based on the target software resource identifier; each first update package carries the software resource identifier of its corresponding category of software resources; and updating the target software resource based on the target update package.

[0012] According to the above technical means, in response to an update event, identification information corresponding to a target software resource in at least one type of software resource is sent to a cloud device; wherein, at least one type of software resource is different functional modules that divide the vehicle cockpit domain system into layers according to the software architecture; so that the cloud device can determine the target update package from at least one first update package based on the identification information corresponding to the target software resource and push it to the vehicle, download the target update package to perform an update based on the target update package. When only the software resources corresponding to a certain function in the vehicle cockpit domain system need to be updated, compared with the prior art of updating the entire firmware of the cockpit domain system, the present application can update the function by only sending the software resources corresponding to the function to be updated to the vehicle via OTA, thereby reducing the amount of updates during vehicle updates, reducing the time required for updates, and achieving updates without strict network requirements. Thus, the efficiency of vehicle updates is improved, and the user experience is enhanced.

[0013] In some embodiments, a vehicle model code is sent to the cloud device; wherein, vehicles corresponding to different vehicle model codes are adapted to software resources with different version numbers; a target update package pushed by the cloud device is downloaded; the target update package is determined by the cloud device from at least one first update package based on a first target version number and identification information corresponding to the target software resource; the first target version number is determined by the cloud device based on the vehicle model code.

[0014] According to the above technical means, by sending the vehicle model code to the cloud device in response to an update event, the cloud device can determine the first target version number adapted for the vehicle based on the model code. The cloud device can then determine the target update package corresponding to the target software resource based on the first target version number and the identification information corresponding to the target software resource. This allows for rapid determination of the target update package adapted to the vehicle, improving vehicle update efficiency.

[0015] In some embodiments, the identification information of any type of software resource includes the software component number and the version number; the identification information of the target software resource includes the target software component number and the target version number; the target update package is determined by the cloud device from at least one third update package based on the first target version number; the version number of the third update package is higher than the target version number; the at least one third update package is determined by the cloud device from the at least one second update package based on the target version number; the second update package represents the update package corresponding to the software resource with the same target software component number; the at least one second update package is determined by the cloud device from the at least one first update package based on the target software component number.

[0016] According to the above technical means, by sending the vehicle model code, target software part number, and target version number to the cloud device in response to an update event, the cloud device determines the target update package for the target software resource based on the target software part number, target version number, and the first target version number. This improves the speed of determining the target software resource update package, thereby improving vehicle update efficiency.

[0017] In a third aspect, an embodiment of the present application provides a method for dividing a cockpit domain system, which is characterized in that, when applied to an electronic device, it includes: obtaining a software resource package of the cockpit domain system; decoupling the software resource package of the cockpit domain system to generate a first software resource package and a second software resource package; the first software resource package includes the system firmware and driver files of the cockpit system; the second software package includes multiple applications for implementing different functions.

[0018] According to the above technical means, by decoupling the software resource package of the cockpit domain system into system firmware and multiple applications, when the system firmware or an application in the vehicle cockpit domain system needs to be updated or upgraded, compared with the solution in the prior art that requires updating the entire software resource package, this application only needs to update the updated system firmware or the software resource package corresponding to a certain application, which reduces the size of the data packet during the update and thus improves the vehicle update efficiency.

[0019] In some embodiments, each application in the second software resource package is standardized to generate a third software resource package and a third software resource package; the third software resource package includes a public version application corresponding to each application; the fourth software resource package includes customized resources corresponding to each application.

[0020] According to the above technical means, by standardizing each application in the second software resource package to obtain the public version application and customized resources of each application, when the vehicle needs to be updated, only the update package corresponding to the public version application and / or customized resources needs to be generated, which reduces the data packet size during the update and improves the vehicle update efficiency.

[0021] In some embodiments, multiple applications in the second software resource package are decoupled to generate multiple independent applications.

[0022] According to the above technical means, by decoupling multiple applications to generate multiple independent applications, when a certain application of the vehicle needs to be updated, only the update package of the corresponding application needs to be generated, and there is no need to generate update packages for all applications; thereby improving the efficiency of vehicle updates.

[0023] In a fourth aspect, an embodiment of the present application provides a vehicle update system, characterized in that the vehicle update system includes a cloud device and a vehicle; wherein the vehicle is used to send identification information corresponding to a target software resource in at least one category of software resources for a vehicle cockpit domain system to the cloud device; wherein at least one category of software resources includes different functional modules of the vehicle's cockpit domain system pre-divided into layers according to a software architecture; the cloud device is used to determine a target update package from at least one first update package based on the identification information corresponding to the target software resource, and push the target update package to the vehicle; wherein each first update package carries identification information of its corresponding category of software resources; the vehicle is also used to download the target update package pushed by the cloud device and update the target software resource based on the target update package.

[0024] In a fifth aspect, an embodiment of the present application provides a vehicle updating device, which is characterized in that it is applied to a cloud device and includes: a receiving module for receiving identification information corresponding to a target software resource in at least one type of software resource sent by a vehicle; wherein, at least one type of software resource includes different functional modules of the vehicle's cockpit domain system pre-divided into layers according to the software architecture; a determination module for determining a target update package corresponding to the target software resource from at least one first update package based on the identification information corresponding to the target software resource; wherein, each first update package carries the identification information of its corresponding category of software resources; a push module for pushing the target update package corresponding to the target software resource to the vehicle to update the target software resource in the vehicle.

[0025] In a sixth aspect, an embodiment of the present application provides a vehicle updating device, characterized in that it is applied to a vehicle and comprises: a sending module, which sends identification information corresponding to the target software resource of the target software resource to a cloud device in response to an update event of a target software resource in at least one category of software resources of a vehicle cockpit domain system; wherein, the at least one category of software resources includes different functional modules of the vehicle's cockpit domain system that are pre-divided into layers according to the software architecture; a downloading module, which is used to download the target update package pushed by the cloud device; the target update package is determined by the cloud device from at least one first update package based on the identification information corresponding to the target software resource; wherein, each of the first update packages carries the identification information of its corresponding category of software resources; an update module, which is used to update the target software resource based on the target update package.

[0026] In the seventh aspect, an embodiment of the present application provides a device for dividing a cockpit domain system, which is characterized in that it is applied to an electronic device and includes: an acquisition module for acquiring a software resource package of the cockpit domain system; a decoupling module for decoupling the software resource package of the cockpit domain system to generate a first software resource package and a second software resource package; the first software resource package includes the system firmware and driver files of the cockpit system; the second software package includes multiple application programs for implementing different functions.

[0027] In an eighth aspect, an embodiment of the present application provides a cloud device comprising a memory and a processor, wherein the memory stores a computer program that can be run on the processor, and when the processor executes the program, some or all of the steps in the above method are implemented.

[0028] In a ninth aspect, an embodiment of the present application provides a vehicle comprising a memory and a processor, wherein the memory stores a computer program that can be run on the processor, and when the processor executes the program, some or all of the steps in the above method are implemented.

[0029] In the tenth aspect, an embodiment of the present application provides a computer device, which can be a cloud device, a vehicle, or an electronic device when implemented; it includes a memory and a processor, the memory stores a computer program that can be run on the processor, and the processor implements some or all of the steps in the above method when executing the program.

[0030] In the eleventh aspect, an embodiment of the present application provides a computer-readable storage medium having a computer program stored thereon, which implements part or all of the steps in the above method when executed by a processor.

[0031] The beneficial effects of the present application are: when the vehicle responds to an update event, it receives identification information corresponding to a target software resource in at least one type of software resource sent by the vehicle; wherein, at least one type of software resource is different functional modules that divide the vehicle cockpit domain system into layers according to the software architecture; it is able to determine a target update package from at least one first update package based on the identification information corresponding to the target software resource, so as to perform an update based on the target update package. When only the software resources corresponding to a certain function in the vehicle cockpit domain system need to be updated, compared with the prior art of updating the entire firmware of the cockpit domain system, the present application can update the function by only sending the software resources corresponding to the function that needs to be updated OTA to the vehicle, thereby reducing the amount of updates during vehicle updates, reducing the time required for updates, and achieving updates without strict network requirements. Thus, the efficiency of vehicle updates is improved, and the user experience is enhanced.

[0032] It should be understood that the above general description and the following detailed description are merely exemplary and explanatory, and do not limit the technical solutions of the present application. BRIEF DESCRIPTION OF THE DRAWINGS

[0033] In the accompanying drawings (which are not necessarily drawn to scale), like reference numerals may describe similar components in different views. Like reference numerals with different letter suffixes may represent different examples of similar components. The accompanying drawings generally illustrate various embodiments discussed herein by way of example and not limitation.

[0034] Figure 1 A schematic diagram of a vehicle updating method according to an embodiment of the present invention;

[0035] Figure 2 A schematic diagram of a vehicle updating method according to an embodiment of the present invention;

[0036] Figure 3 A schematic diagram of a vehicle updating method according to an embodiment of the present invention;

[0037] Figure 4 A schematic diagram of a vehicle updating method according to an embodiment of the present invention;

[0038] Figure 5 A schematic diagram of a vehicle updating method according to an embodiment of the present invention;

[0039] Figure 6 A schematic diagram of the implementation flow of a method for dividing a cockpit domain system provided in an embodiment of the present application;

[0040] Figure 7 A schematic diagram of an existing system resource package provided in an embodiment of the present application;

[0041] Figure 8 A schematic diagram of a process for implementing a vehicle cabin domain system separation method provided in an embodiment of the present application;

[0042] Figure 9 A schematic diagram of a split system resource package provided in an embodiment of the present application;

[0043] Figure 10 A schematic diagram of the structure of a software resource download system provided in an embodiment of the present application;

[0044] Figure 11 A schematic diagram of a vehicle updating method according to an embodiment of the present invention;

[0045] Figure 12 A schematic diagram of the structure of a vehicle update system provided in an embodiment of the present application;

[0046] Figure 13 A schematic diagram of the structure of a vehicle updating device provided in an embodiment of the present application;

[0047] Figure 14 A schematic diagram of the structure of a vehicle updating device provided in an embodiment of the present application;

[0048] Figure 15 A schematic diagram of the structure of a vehicle cabin area partitioning system provided in an embodiment of the present application;

[0049] Figure 16 A schematic diagram of the structure of a computer device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0050] In order to make the purpose, technical solutions and advantages of this application clearer, the following figure will further describe this application in detail in conjunction with the accompanying drawings. The described embodiments should not be regarded as limiting this application. All other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of this application.

[0051] The exemplary embodiments disclosed herein will be described in more detail below with reference to the accompanying drawings. Although exemplary embodiments of the present application are shown in the accompanying drawings, it should be understood that the present application can be implemented in various forms and should not be limited by the specific embodiments described herein. Rather, these embodiments are provided to enable a more thorough understanding of the present application and to fully convey the scope of the present application to those skilled in the art.

[0052] In the following description, numerous specific details are provided to provide a more thorough understanding of the present application. However, it will be apparent to those skilled in the art that the present application can be practiced without one or more of these details. In other instances, certain technical features known in the art are not described to avoid confusion with the present application; that is, all features of actual embodiments are not described herein, nor are well-known functions and structures described in detail.

[0053] In the drawings, the sizes of layers, regions, elements and their relative sizes may be exaggerated for clarity. Like reference numerals denote like elements throughout.

[0054] The purpose of the terms used herein is only to describe specific embodiments and is not intended to limit the present application. When used herein, the singular forms "a", "an", and "the" are intended to include the plural forms, unless the context clearly indicates otherwise. It should also be understood that the terms "comprising" and / or "including", when used in this specification, determine the presence of the features, integers, steps, operations, elements and / or parts, but do not exclude the presence or addition of one or more other features, integers, steps, operations, elements, parts and / or groups. When used herein, the term "and / or" includes any and all combinations of the relevant listed items.

[0055] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by those skilled in the art to which this application belongs. The technical and scientific terms used herein are only for the purpose of describing the embodiments of this application and do not limit this application.

[0056] Currently, a large number of applications are pre-installed in the system firmware. The car model resources, theme resources, etc. of each application are packaged in their own program packages. When updating the vehicle through Over-The-Air (OTA) technology, it is usually necessary to download the entire system firmware package, resulting in too low vehicle update frequency, too slow download speed, and too long upgrade time, thereby reducing vehicle update efficiency.

[0057] The present application provides a vehicle update method, which is applied to a cloud device and receives identification information corresponding to a target software resource from at least one category of software resources sent by a vehicle; wherein the at least one category of software resources includes different functional modules of the vehicle's cockpit domain system that are pre-divided into layers according to the software architecture; based on the identification information corresponding to the target software resource, a target update package corresponding to the target software resource is determined from at least one first update package; wherein each first update package carries the identification information of its corresponding category of software resource; and the target update package corresponding to the target software resource is pushed to the vehicle to update the target software resource in the vehicle. Compared with the prior art method of updating the entire firmware of the cockpit domain system, the present application only updates the software resource corresponding to the function to be updated by OTA to the vehicle, thereby reducing the amount of updates required during vehicle updates, reducing the time required for updates, and achieving updates without strict network requirements. As a result, the efficiency of vehicle updates is improved and the user experience is enhanced.

[0058] Figure 1 A schematic diagram of a vehicle method implementation flow provided in an embodiment of the present application, which is applied to a cloud device, such as Figure 1 As shown, the method includes the following steps S101 to S103, combining Figure 1 The steps shown are explained.

[0059] Among them, cloud devices can be various types of terminals such as laptops, tablets, desktop computers, set-top boxes, mobile devices (for example, mobile phones, portable music players, personal digital assistants, dedicated messaging devices, portable gaming devices), etc., and can also be implemented as servers. The server can be an independent physical server, or a server cluster or distributed system composed of multiple physical servers, or a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, content delivery networks (CDNs), and big data and artificial intelligence platforms.

[0060] Step S101: receiving identification information corresponding to a target software resource in at least one type of software resources sent by a vehicle.

[0061] The at least one type of software resources includes different functional modules of the vehicle's cockpit domain system that are pre-divided into layers according to a software architecture.

[0062] In some embodiments, the at least one type of software resources includes public version system firmware, public version applications, and customized resources of the vehicle cockpit domain system; wherein the customized resources are customized resources corresponding to each public version application.

[0063] In some embodiments, the applications in the vehicle cockpit domain system are pre-installed in the system firmware, and the customized resources corresponding to each application are packaged inside the application, so that the vehicle cockpit domain system can be divided into different functional modules according to the software architecture before the vehicle leaves the factory or before the vehicle is updated, where each functional module is independent of each other.

[0064] In some embodiments, the software architecture of the vehicle cockpit domain system includes a bottom layer, an application layer (middle layer), and customized resources.

[0065] Among them, the bottom layer can be the system firmware of the vehicle cockpit domain system. The system firmware can include the system's underlying drivers, system kernel files, etc., which are used to provide operating environment and hardware driver support for the system, applications, etc.

[0066] Among them, the application layer may include multiple applications, each of which is packaged with customized resources of the vehicle or application. The applications may include navigation applications, music applications, vehicle settings applications, etc., which are used to provide different functions for users.

[0067] Customized resources are the resources generated through customized development and configuration of applications. They can be determined based on different vehicle models, different configurations of the same vehicle model, and individual user needs. They are used to personalize the application's interface, functions, data, and other aspects to meet the specific needs of different user groups. Examples include customized application interface skins (main body or background) and localized language packs.

[0068] In some embodiments, the system firmware, application programs, and customized resources of the vehicle cockpit domain system belong to software architecture components at different levels in the vehicle cockpit domain system. The system firmware, application programs, and customized resources are also functional modules that realize different functions of the vehicle cockpit domain. Therefore, the vehicle cockpit domain system can be divided into different functional modules according to the software architecture, that is, the vehicle cockpit domain system can be divided into system firmware, application programs, and customized resources.

[0069] In some embodiments, the applications in the vehicle cockpit domain system are pre-installed in the system firmware, and each application is packaged inside the application, thereby dividing the vehicle cockpit domain system into different functional modules according to the software architecture layer, including: decoupling the system firmware from each application; obtaining a public version system firmware package and an application package; decoupling multiple applications in the application package to obtain independent applications, and finally standardizing each application to separate the customized resources in each application to obtain the public version application and customized resources of each application; generating a public version application package based on the public version application corresponding to each application, and generating a customized resource package based on the customized resources corresponding to each application.

[0070] In some embodiments, when the vehicle responds to an update event, it is necessary to determine the target software resource that needs to be updated from at least one type of software resources, and then send identification information corresponding to the target software resource to the cloud device.

[0071] In some embodiments, the target software resources include at least one category of software resources, and the category of the target software resources is determined based on the update event; for example, at least one category of software resources includes first category software resources, second category software resources, and third category software resources; then the target software resources can include at least one of them.

[0072] In some embodiments, the target software resource may also include multiple software resources of the same category; for example, the target software resource is a public version application, and the public version application may include a public version navigation application, a public version media application, and a public version system setting application.

[0073] In some embodiments, the target software resources may include multiple categories of software resources, for example, the target software resources may include a public version application and customized resources corresponding to the application.

[0074] In some embodiments, the identification information corresponding to the target software resource includes the identification information of each software resource included in the target software resource; for example, the target software resource includes a public version navigation application, a public version media application, and customized resources corresponding to the public version application; wherein the identification information includes the identification information corresponding to the public version navigation application, the identification information corresponding to the public version media application, and the identification information corresponding to the customized resources corresponding to the public version application.

[0075] Step S102: Determine a target update package corresponding to the target software resource from at least one first update package based on identification information corresponding to the target software resource.

[0076] Each of the first update packages carries identification information of the corresponding category of software resources.

[0077] In some embodiments, it is first necessary to obtain at least one first update package, wherein the at least one first update package can be at least one first code package uploaded by the developer to the cloud device through the development end, and the cloud device compiles each first code package to generate at least one first update package; or the cloud device actively sends an update request to the development end, and the development end generates a code package corresponding to the update requirement based on the update requirement in the update request, and actively uploads the code package to the cloud device.

[0078] In some embodiments, at least one first update package may include an update package corresponding to at least one software resource of any type. It is understood that at least one type of software resource includes first-type software resources, second-type software resources, and third-type software resources, and that at least one first update package may only include an update package corresponding to at least one first-type software resource; alternatively, at least one first update package may include at least one update package corresponding to the first-type software resource, at least one update package corresponding to the second-type software resource, and at least one update package corresponding to the third-type software resource.

[0079] Exemplarily, at least one first update package includes two update packages corresponding to public version applications and one update package corresponding to customized resources.

[0080] In some embodiments, at least one first update package may also include software resources of the same type, where different vehicle models correspond to different versions of the same type of software resources; it is understandable that for the same type of software resources, different vehicle models are adapted to different versions.

[0081] Exemplarily, at least one first update package includes a resource package corresponding to the first public version application, a resource package corresponding to the second public version application, and a resource package corresponding to the third public version application; wherein, the resource package corresponding to the first public version application is adapted to the low-end version of the vehicle, the resource package corresponding to the second public version application is adapted to the mid-end version of the vehicle, and the resource package corresponding to the third public version application is adapted to the high-end version of the vehicle.

[0082] In some embodiments, the identification information corresponding to the target software resource represents the software component number and version number of the target software resource.

[0083] In some embodiments, a unique software part number is assigned to each software resource in the vehicle before it leaves the factory. The software part number can reflect the type, brand, and model of the software resource. For example, the software part number of a software resource is APP-NVA-XX-002, where APP-NVA indicates that the software resource is a navigation application, XX indicates its brand or manufacturer, and 002 is the unique number of the software resource.

[0084] In some embodiments, at least one first update package is screened based on identification information corresponding to the target software resource to match a target update package corresponding to the identification information of the target software resource.

[0085] In some embodiments, at least one first update package may be screened based on the vehicle model to obtain a first update package that is compatible with the vehicle version.

[0086] Step S103: Push the target update package corresponding to the target software resource to the vehicle to update the target software resource in the vehicle.

[0087] In some embodiments, after the cloud device determines the target update package based on the identification information corresponding to the target software resource sent by the vehicle, it pushes the target update package to the vehicle through OTA technology.

[0088] In some embodiments, the target update package carries a verification value (such as a hash value) of the complete target update package. After the vehicle downloads the target update package, the target update package is verified, including calculating the real-time hash value of the target update package, and comparing the complete hash value carried by the target update package based on the real-time hash value to perform integrity verification on the target update package; if the target update package meets the requirements, the target update package is decompressed to obtain new target software resources, and the original target software resources of the vehicle are replaced to achieve the update of the vehicle.

[0089] In an embodiment of the present application, when the vehicle responds to an update event, it receives identification information corresponding to a target software resource in at least one type of software resource sent by the vehicle; wherein, at least one type of software resource is different functional modules that divide the vehicle cockpit domain system into layers according to the software architecture; it is capable of determining a target update package from at least one first update package based on the identification information corresponding to the target software resource, so as to perform an update based on the target update package. When only the software resources corresponding to a certain function in the vehicle cockpit domain system need to be updated, compared with the prior art of updating the entire firmware of the cockpit domain system, the present application can update the function by only sending the software resources corresponding to the function to be updated OTA to the vehicle, thereby reducing the amount of updates during vehicle updates, reducing the time required for updates, and achieving updates without strict network requirements. Thus, the efficiency of vehicle updates is improved, and the user experience is enhanced.

[0090] Figure 2 A schematic diagram of the implementation process of a vehicle update method provided in an embodiment of the present application, which is applied to a cloud device and is based on Figure 1 , Figure 1 Step S102 in the above example can be updated to step S201 to step S203, which will be combined with Figure 2 The steps shown are explained.

[0091] Step S201: Receive the vehicle model code sent by the vehicle.

[0092] Among them, vehicles corresponding to different model codes are adapted to software resources with different version numbers.

[0093] In some embodiments, when the vehicle responds to an update event, the vehicle model code needs to be sent to the cloud device. After the cloud device receives the vehicle model code, it determines the version of the target software resource adapted to the current vehicle based on the vehicle model code.

[0094] Step S202: Determine a first target version number corresponding to the target software resource based on the vehicle model code.

[0095] In some embodiments, the vehicle model code may represent information such as the model, category, and configuration of the vehicle.

[0096] In some embodiments, after receiving the vehicle model code sent by the vehicle, the cloud device obtains the vehicle model, category, configuration and other information based on the vehicle model code; and determines the first target version number of the target software resource adapted to the current vehicle based on the vehicle model, category and configuration.

[0097] For example, the target software resource is a public version navigation application, and the vehicle is a low-profile SUV. The embodiment of this application is described below. At least one first update package includes first update packages corresponding to the first, second, and third versions of the navigation application, where the first version is lower than the second version, and the second version is lower than the third version. If the low-profile SUV is compatible with the first version, the vehicle is determined to be compatible with the first version of the public version navigation application, and the first version is determined as the first target version number.

[0098] Step S203: Determine a target update package corresponding to the target software resource from the at least one first update package based on the first target version number and the identification information corresponding to the target software resource.

[0099] In some embodiments, the identification information corresponding to the target software resource includes a target software component number and a target version number; each of the at least one first update package carries the component number and version number of its corresponding software resource. Thus, based on the identification information corresponding to the target software resource, the at least one first update package is screened to obtain at least one first update package with the same component number as the target software resource and a higher version than the target software component number. The target update package is then determined from the at least one screened first update package based on the first target version number determined by the vehicle model code.

[0100] Exemplarily, at least one first update package includes an update package corresponding to a public version application and an update package corresponding to a customized file; the software part number corresponding to the target software resource indicates that the target software resource type is a public version application, and the version number corresponding to the target software resource is the first version; then at least one first update package that meets the public version application and has a version number greater than the first version number is obtained; the vehicle model code indicates that the vehicle adaptation version is the second version, then the first update package of the public version application and the second version is determined from the at least one filtered first update package, and it is determined as the target update package.

[0101] In this embodiment of the present application, a vehicle model code is received from a vehicle, and a first target version of a target software resource adapted for the vehicle is determined based on the vehicle model code. A target update package is then determined from at least one first update package based on the identification information of the target software resource and the first target version. This allows for rapid determination of the target update package adapted for the vehicle, improving vehicle update efficiency.

[0102] Figure 3 A schematic diagram of the implementation process of a vehicle update method provided in an embodiment of the present application, which is applied to a cloud device and is based on Figure 2 , the identification information of any type of software resource includes the software component number and version number; the identification information of the target software resource includes the target software component number and target version number; Figure 2Step S202 can be updated to step S301 to step S303, which will be combined Figure 3 The steps shown are explained.

[0103] Step S301: Determine at least one second update package from the at least one first update package based on the target software component number.

[0104] The second update package represents an update package corresponding to a software resource having the same component number as the target software.

[0105] In some embodiments, the target software part number represents information such as the type, model, and brand of the target software resource.

[0106] In some embodiments, at least one first update package is screened based on the target software part number to obtain at least one second update package having the same characteristics as the target software resource, such as type, model, and brand.

[0107] Exemplarily, the target software part number represents that the target software resource is a public version navigation application and the model is the first model; then at least one first update package of the type of the public version navigation application and the model of the first model is obtained from at least one first update package to determine as at least one second update package.

[0108] In some embodiments, the at least one second update package includes update packages corresponding to multiple versions of software resources.

[0109] Step S302: Determine at least one third update package from the at least one second update package based on the target version number.

[0110] The version number of the third update package is higher than the target version number.

[0111] In some embodiments, the at least one second update package is filtered based on the target version number to obtain at least one third update package having a higher version number than the target version number.

[0112] Exemplarily, the target version number indicates that the target software resource is a first version; then at least one second update package of a second version and a third version is obtained from the at least one first update package and determined as at least one third update package.

[0113] Step S303: Determine the target update package from the at least one third update package based on the first target version number.

[0114] In some embodiments, the at least one third update package is screened based on the first target version number to obtain a third update package having the same version number as the first target version number, and the third update package is determined as the target update package.

[0115] Exemplarily, the first target version number indicates that the version number adapted by the vehicle is the third version number; then a third update package of the third version is determined from the at least one third update package, and the third update package is determined as the target update package.

[0116] In this embodiment of the present application, at least one first update package is screened by the target software version number to obtain at least one second update package with the same target software version number. At least one second update package is screened based on the target version number to obtain at least one third update package with a version number higher than the target version number. The target update package is determined from the at least one third update package based on the first target version number adapted for the vehicle. This improves the speed of obtaining the target update package, thereby improving the efficiency of vehicle updates.

[0117] Figure 4 A schematic diagram of a vehicle updating method according to an embodiment of the present application is provided. The method is applied to a vehicle. The method may include steps S401 to S403. Figure 4 The steps shown are explained.

[0118] Step S401: In response to an update event of a target software resource in at least one type of software resources of a vehicle cockpit domain system, identification information corresponding to the target software resource is sent to a cloud device.

[0119] The at least one type of software resources includes different functional modules of the vehicle's cockpit domain system that are pre-divided into layers according to a software architecture.

[0120] In some embodiments, the update event may be an update prompt message sent by the cloud device to the vehicle after receiving the first update package.

[0121] In some embodiments, the update time may also be update reminder information sent by the development end to the vehicle.

[0122] In some embodiments, the update event may also be that the vehicle obtains the version information of the update package corresponding to each software resource in the cloud device in real time; compares the version information of the update package corresponding to each software resource with the real-time version corresponding to each software resource currently in the vehicle, and when there is at least one software resource whose corresponding update package has higher version information than the current vehicle, the update time is triggered.

[0123] In some embodiments, in response to an update event of a target software resource in at least one type of software resources of the vehicle cockpit domain system, a software part number and / or version number corresponding to the target software resource is sent to a cloud device.

[0124] Step S402: Download the target update package pushed by the cloud device.

[0125] The target update package is determined by the cloud device from at least one first update package based on the target software resource identifier.

[0126] Each of the first update packages carries a software resource identifier of a software resource of a corresponding category.

[0127] In some embodiments, after sending identification information of the target software resource to the cloud device, the cloud device determines a target update cell from at least one first update package based on the identification information and pushes it to the vehicle; the vehicle downloads the update package after receiving the target update cell.

[0128] In some embodiments, at least one first update package is screened based on identification information corresponding to the target software resource to match a target update package corresponding to the identification information of the target software resource.

[0129] Step S403: Update the target software resource based on the target update package.

[0130] In some embodiments, the target update package carries a verification value (such as a hash value) of the complete target update package. After the vehicle downloads the target update package, the target update package is verified, including calculating the real-time hash value of the target update package, and comparing the complete hash value carried by the target update package based on the real-time hash value to perform integrity verification on the target update package; if the target update package meets the requirements, the target update package is decompressed to obtain new target software resources, and the original target software resources of the vehicle are replaced to achieve the update of the vehicle.

[0131] In an embodiment of the present application, in response to an update event, identification information corresponding to a target software resource in at least one type of software resource is sent to a cloud device; wherein, at least one type of software resource is different functional modules that divide the vehicle cockpit domain system into layers according to the software architecture; so that the cloud device can determine the target update package from at least one first update package based on the identification information corresponding to the target software resource and push it to the vehicle, and the vehicle downloads the target update package to perform an update based on the target update package. When only the software resources corresponding to a certain function in the vehicle cockpit domain system need to be updated, compared with the prior art of updating the entire firmware of the cockpit domain system, the present application can update the function by only OTA-ing the software resources corresponding to the function that needs to be updated to the vehicle, thereby reducing the amount of updates during vehicle updates, reducing the time required for updates, and achieving updates without strict network requirements. Thus, the efficiency of vehicle updates is improved, and the user experience is enhanced.

[0132] Figure 5 A schematic diagram of a vehicle updating method according to an embodiment of the present application is provided. The method is applied to a vehicle. The method may include steps S501 and S502. Figure 5 The steps shown are explained.

[0133] Step S501: Send the vehicle model code to the cloud device.

[0134] Among them, vehicles corresponding to different model codes are adapted to software resources with different version numbers.

[0135] In some embodiments, when the vehicle responds to an update event, the vehicle model code needs to be sent to the cloud device. After the cloud device receives the vehicle model code, it determines the version of the target software resource adapted to the current vehicle based on the vehicle model code.

[0136] Step S502: Download the target update package pushed by the cloud device.

[0137] The target update package is determined by the cloud device from at least one first update package based on a first target version number and identification information corresponding to the target software resource.

[0138] The first target version number is determined by the cloud device based on the vehicle model code.

[0139] In some embodiments, after sending the vehicle model code to the cloud device, the cloud device determines the first target version number adapted for the vehicle based on the vehicle model code; and determines the target update package from at least one first update package based on the first target version number and the identification information corresponding to the target software resource; and pushes the target update package to the vehicle.

[0140] In some embodiments, after receiving the target update package sent by the cloud device, the target update package is downloaded, and the target software resources on the vehicle are updated based on the target update package.

[0141] In this embodiment of the present application, the vehicle model code is sent to the cloud device in response to an update event, allowing the cloud device to determine the first target version number compatible with the vehicle based on the model code. This allows the cloud device to determine the target update package corresponding to the target software resource based on the first target version number and the identification information corresponding to the target software resource. This allows for rapid determination of the target update package for the vehicle, improving vehicle update efficiency.

[0142] In some embodiments, the identification information of any type of software resource includes a software component number and a version number; the identification information of the target software resource includes a target software component number and a target version number.

[0143] In some embodiments, the target update package in step S502 is determined by the cloud device from at least one third update package based on the first target version number; the version number of the third update package is higher than the target version number.

[0144] The at least one third update package is determined by the cloud device from the at least one second update package based on the target version number; the second update package represents an update package corresponding to a software resource having the same component number as the target software.

[0145] The at least one second update package is determined by the cloud device from the at least one first update package based on the target software component number.

[0146] In some embodiments, after sending the vehicle model code and identification information corresponding to the target software resource to the cloud device, the cloud device determines at least one second update package from the at least one first update package based on the target software part number; determines at least one third update package from the at least one second update package based on the target version number; and determines the target update package from the at least one third update package based on the first target version number.

[0147] In this embodiment of the present application, the vehicle model code, target software component number, and target version number are sent to the cloud device in response to an update event. The cloud device then determines the target update package for the target software resource based on the target software component number, target version number, and first target version number. This improves the speed of determining the target software resource update package, thereby increasing vehicle update efficiency.

[0148] Figure 6 This is a schematic diagram of a method for implementing a cockpit domain system partitioning method provided in an embodiment of the present application. The method is applied to an electronic device. The method may include steps S601 and S602. Figure 6 The steps shown are explained.

[0149] In some embodiments, the electronic device may include various types of terminals such as laptop computers, tablet computers, desktop computers, set-top boxes, mobile devices (e.g., mobile phones, portable music players, personal digital assistants, dedicated messaging devices, portable gaming devices), etc.

[0150] Step S601: Acquire the software resource package of the cockpit domain system.

[0151] In some embodiments, the software resource package of the cockpit domain system can be obtained through the official website of the vehicle manufacturer or directly copied from the vehicle system. This application does not make specific limitations on this.

[0152] In some embodiments, the software resource package of the cockpit domain system integrates the underlying data, application layer data and customized resources of the cockpit domain system; it may include the system firmware, application programs and customized resources of the cockpit domain system; wherein the customized resources are packaged in the application programs, and the application programs are pre-installed in the system firmware.

[0153] Step S602: Decouple the software resource package of the cockpit domain system to generate a first software resource package and a second software resource package.

[0154] The first software resource package includes the system firmware and driver files of the cockpit system; the second software package includes multiple application programs for implementing different functions.

[0155] In some embodiments, it is first necessary to identify the system firmware in the cockpit domain system, which may include drivers, system kernels, etc.; separate the identified system firmware from the cockpit domain system to obtain independent system firmware and independent applications; package customized resources in the application; establish a first software resource package and a second software resource package, store the independent system firmware in the first software package; and store the independent application in the second software resource package.

[0156] In an embodiment of the present application, by decoupling the software resource package of the cockpit domain system into system firmware and multiple applications, when the system firmware or an application in the vehicle cockpit domain system needs to be updated or upgraded, compared with the solution in the prior art that requires updating the entire software resource package, the present application only needs to update the updated system firmware or the software resource package corresponding to a certain application, thereby reducing the data packet size during the update and improving the vehicle update efficiency.

[0157] In some embodiments, after the second software resource package is generated, the following implementation is also included:

[0158] Each application in the second software resource package is standardized to generate a third software resource package and a third software resource package.

[0159] The third software resource package includes a public version application corresponding to each application; and the fourth software resource package includes customized resources corresponding to each application.

[0160] In some embodiments, each application in the second software resource package is identified to determine its core functions, auxiliary functions, and dependent resources; the application is divided into multiple independent modules based on the core functions, auxiliary functions, and dependent resources; the common parts are obtained from each independent module; and the common parts obtained from each independent module are packaged to obtain a third software resource package.

[0161] For example, the core function of a multimedia application is to play audio and video, and its auxiliary functions include playlist management and sound effect adjustment. This application can be divided into a playback control module, an audio decoding module, a video decoding module, a playlist management module, etc. The commonly used components obtained include the code and related resources for basic playback control functions (such as play, pause, and stop).

[0162] In some embodiments, a portion customized for a specific vehicle model, region, or user group is obtained from each independent module as a customized resource, and packaged to obtain a fourth software resource package.

[0163] Exemplarily, the dependent resources include audio decoders, video decoders, interface materials, and the like.

[0164] In an embodiment of the present application, by standardizing each application in the second software resource package to obtain the public version application and customized resources of each application, when the vehicle needs to be updated, only the update package corresponding to the public version application and / or customized resources needs to be generated, thereby reducing the data packet size during the update and improving the vehicle update efficiency.

[0165] In some embodiments, after the second software resource package is generated, the following implementation is also included:

[0166] The multiple application programs in the second software resource package are decoupled to generate multiple independent application programs.

[0167] In some embodiments, dependencies between multiple applications are determined; and the multiple applications are decoupled based on the dependencies.

[0168] For example, applications call each other's interfaces to obtain resources in a shared database. By adjusting the interface of each application, each application can independently call the shared database, solving the coupling between data exchanges and generating multiple independent applications.

[0169] In an embodiment of the present application, multiple applications are decoupled to generate multiple independent applications. When a certain application of the vehicle needs to be updated, only an update package for the corresponding application needs to be generated, and there is no need to generate update packages for all applications; thereby improving the efficiency of vehicle updates.

[0170] The following describes an exemplary application of the vehicle updating method provided in an embodiment of the present application in a practical scenario.

[0171] With the widespread use of smart devices, we have become inseparable from them in our daily lives. As users pursue personalization and new experiences, smart devices are not only important to users, but they also hope that manufacturers can use Over-The-Air (OTA) technology to perform firmware updates and bring new features. Therefore, users' demand for OTA is increasing. Traditional OTA update methods usually require downloading the entire system firmware package, which not only consumes a lot of network resources but also requires a long update time. For example, the firmware package size of traditional in-vehicle entertainment information systems can easily reach several GB. Frequent OTA updates not only consume a lot of data, but when the network is poor, OTA updates may frequently fail, affecting the user experience.

[0172] Furthermore, system firmware packages often contain numerous pre-installed applications. Updating these applications requires re-downloading the entire system firmware package, further increasing the complexity and time required for updates. Simply updating a small feature requires downloading the entire system firmware package. This approach is not only inefficient but also increases user wait time and network traffic consumption.

[0173] In traditional OTA solutions, a large number of applications are pre-installed in the system firmware. Each application's car model resources, theme resources, and other resources are packaged within their own program package. Since each update requires downloading the entire firmware package, OTA upgrades are too infrequent, download speeds are too slow, and upgrades take too long, all of which seriously impact the user experience. Therefore, improving the efficiency of OTA updates and reducing the amount of update data and time costs has become a pressing issue.

[0174] Figure 7 This is a schematic diagram of an existing system resource package provided in an embodiment of the present application. The existing system resource package 700 includes a system image file 701, applications 702, such as Bluetooth, a dashcam, music, and navigation; and customized resources 703 for each application, such as vehicle model resources, main images, and configuration files for vehicle models in a basic vehicle settings application. Applications 702 are pre-installed in system image file 701, and customized resources 703 are packaged within applications 702. The entire existing system resource package 700 is a single, integrated data package.

[0175] To address the above technical issues, we provide a method for improving OTA efficiency through a minimal ROM and independent application upgrades. This method separates pre-installed applications from the system firmware and isolates the differentiated resources of these applications, minimizing the system firmware and creating a public version. This allows for different resources to be flashed for different projects, significantly improving OTA update efficiency.

[0176] Figure 8 The present invention provides a method for separating the vehicle cabin domain system, which includes the following steps S801 and S802. Figure 8 The steps shown are explained.

[0177] Step S801: Decouple the vehicle cockpit domain system to obtain system firmware and application programs.

[0178] In some embodiments, the operating system core and necessary drivers are extracted to generate minimized system firmware. This includes separating pre-installed system applications from the system firmware, so that the system firmware only contains the operating system core and necessary drivers. This minimizes the size of the system firmware and reduces the amount of data required to download during OTA updates.

[0179] Separating pre-installed applications from the system firmware involves: Separating applications from the system firmware requires decoupling applications from the system and from each other. Decoupling applications from the system can be achieved through platform-based interfaces and communication signals, making applications independent of system versions. In addition to platform-based interfaces and communication signals, decoupling applications from each other can also be achieved by stripping coupling functions down to common modules and pre-installing them into the system. Through decoupling and stripping, only common basic capability modules remain in the system firmware package, minimizing the ROM size. Separating applications from the system firmware package significantly improves OTA efficiency. To upgrade core system functionality, only the system firmware package needs to be upgraded. Compared to pre-installing applications in the system firmware, the downloaded resource package is smaller, resulting in faster single-OTA download and upgrade speeds, significantly improving performance.

[0180] In some embodiments, a platform-based system architecture solution pre-installs core, general-purpose, and foundational software modules into the system firmware and allows for OTA upgrades along with the system ROM package. Other functional software modules are separated from the system firmware. Because these are platform-based general-purpose foundational modules, OTA upgrades of the system firmware are less frequent, or even unnecessary.

[0181] Step S802: Platformize the application to obtain a public version application and differential resources.

[0182] In some embodiments, applications separated from the system firmware often need to be customized for each model because the functional requirements are different on different models. However, this will increase the cost and cycle of development and testing, and reduce the frequency of OTA releases. By making the core business of the application platform, the resource files are separated from it, and customized according to different projects, the frequency of OTA updates of the application can be reduced. It is necessary to treat the differences between different models as resources and separate them from the application. Only common functional features are retained in the application, and the resources of the different parts can also be upgraded and updated independently.

[0183] In some embodiments, the separated applications are standardized to remove differential resources and generate a public version application.

[0184] In some embodiments, differential resources are stored separately and customized according to different vehicle models. Resource file separation is a prerequisite for realizing application platformization. Different vehicle models have different functional characteristics for the same function. If you want to make the application platform-based, you need to split the different parts into independent resource packages. Common functions are retained in the original application, which can meet the needs of one deployment and push to all vehicle models for OTA, thereby improving the efficiency of OTA. Since the split resource packages are related to the vehicle model, they need to be upgraded separately when a single vehicle model needs to be upgraded, so as to achieve the purpose of improving OTA efficiency.

[0185] In some embodiments, differential resources include configuration files, language packs, icons, etc.

[0186] Figure 9 A schematic diagram of a split system resource package provided in an embodiment of the present application, wherein the split system resource package 900 includes a public version system firmware package 901, a public version application package 902, and a customized resource package 903 for each application; wherein the public version system firmware package 901, the public version application package 902, and the customized resource package 903 are independent of each other.

[0187] Figure 10 A schematic diagram of a system for downloading software resources provided in an embodiment of the present application is shown in FIG. Figure 10 As shown, the system includes: an integrated transportation operating system (ITOS) 1001 for automatic configuration word generation, a configurable vehicle bill of materials (BOM) 1002, an electrical inspection server 1003, an over-the-air (OTA) management 1004 and a cockpit system 1005.

[0188] In some embodiments, ITOS 1001 is primarily responsible for configuring the relationship between vehicle model codes and software resources, and for transmitting software resources generated during the R&D process to the electronic inspection server 1003 and OTA management 1004. The configurable BOM 1002 primarily provides ITOS 1001 with vehicle information and the software and hardware part numbers required for the vehicle. The electronic inspection server 1003 primarily receives from ITOS 1001 software packages and configuration files for each vehicle model, and other related content that needs to be synchronized to the cockpit system 1005. This is primarily used to automatically flash differentiated content to the corresponding vehicle when the vehicle is produced at the factory. OTA management 1001 is primarily responsible for performing software upgrades for the same functionality for different vehicle models after the vehicle arrives in the hands of the user, which can be divided by vehicle model code, application program, and resource. As an object that needs to be platformized, the software architecture of the software application module of the cockpit system 1005 (i.e., an example of software resources) needs to be restructured, and resources related to vehicle attributes need to be extracted and stored separately, which can be configured separately. As the core of the entire software resource download system, the cockpit system 1005 needs to download the corresponding vehicle software resources from the electronic inspection equipment to the vehicle during the production phase. When the vehicle is in use, resources or applications for updating may be downloaded from the OTA management 1004 to the vehicle.

[0189] ITOS1001 selects specific features based on the vehicle's hardware capabilities and configuration, and automatically generates configuration files based on pre-defined rules. These configuration files are automatically pushed from the cloud device to the factory's electrical inspection server 1003 or OTA management 1004 via ITOS1001 based on the vehicle model code. ITOS1001 also automatically manages the flow of software versions during the development process and the official release after testing.

[0190] Figure 11 A schematic diagram of a vehicle updating method provided in an embodiment of the present application, the method includes the following steps S1101 to S1113, which are combined with Figure 11 The steps shown are explained.

[0191] Step S1101, ITOS packages the software resource package;

[0192] The software resource package includes: updated versions of applications and / or resources;

[0193] Step S1102, ITOS 1001 sends the software resource package to OTA management 1004;

[0194] Step S1103, OTA management 1004 stores the software resource package;

[0195] Step S1104 , the OTA management 1004 decompresses the software resource package into applications and / or resources;

[0196] Step S1105, OTA management 1004 establishes a mapping table;

[0197] Step S1106 , the cockpit system 1005 detects that an application and / or resource is to be updated;

[0198] Step S1107 , the cockpit system 1005 sends the first identification code of the application and / or the second identification code of the resource to the OTA management 1004 ;

[0199] Step S1108 , OTA management 1004 obtains the storage address of the application and / or resource;

[0200] Step S1109 , the OTA management 1004 sends the storage address of the application and / or resource to the cockpit system 1005 ;

[0201] Step S1110 , the cockpit system 1005 downloads applications and / or resources;

[0202] Step S1111: After the download is completed, the cockpit system 1005 performs verification;

[0203] Step S1112: The cockpit system 1005 upgrades the application and / or resources after verification.

[0204] Step S1113 : After the cockpit system 1005 is upgraded, the software module is configured based on the configuration word.

[0205] Figure 12 A schematic diagram of the structure of a vehicle update system provided in an embodiment of the present application is shown as follows: Figure 12 As shown, the vehicle update system 1200 includes: a vehicle 1201 and a cloud device 1202, wherein: the vehicle 1201 is used to send a target software resource identifier of a target software resource in at least one category of software resources for a vehicle cockpit domain system to the cloud device; the cloud device 1202 is used to determine a target update package from at least one first update package based on the target software resource identifier, and push the target update package to the vehicle; wherein each first update package carries the software resource identifier of its corresponding category of software resources; the vehicle 1201 is also used to download the target update package pushed by the cloud device and update the target software resource based on the target update package.

[0206] In some embodiments, the cloud device 1202 is also used to receive identification information corresponding to a target software resource in at least one category of software resources sent by the vehicle; wherein, the at least one category of software resources includes different functional modules of the vehicle's cockpit domain system that are pre-divided into layers according to the software architecture; based on the identification information corresponding to the target software resource, a target update package corresponding to the target software resource is determined from at least one first update package; wherein, each first update package carries identification information of its corresponding category of software resources; and the target update package corresponding to the target software resource is pushed to the vehicle to update the target software resource in the vehicle.

[0207] In some embodiments, the cloud device 1202 is also used to receive the vehicle model code sent by the vehicle; wherein, vehicles corresponding to different vehicle model codes are adapted to software resources with different version numbers; based on the vehicle model code, the first target version number corresponding to the target software resource is determined; based on the first target version number and the identification information corresponding to the target software resource, the target update package corresponding to the target software resource is determined from the at least one first update package.

[0208] In some embodiments, the identification information of any type of software resource includes a software component number and a version number; the identification information of the target software resource includes a target software component number and a target version number; the cloud device 1202 is also used to determine at least one second update package from the at least one first update package based on the target software component number; the second update package represents an update package corresponding to a software resource with the same target software component number; at least one third update package is determined from the at least one second update package based on the target version number; the version number of the third update package is higher than the target version number; the target update package is determined from the at least one third update package based on the first target version number.

[0209] In some embodiments, the vehicle 1201 is also used to respond to an update event of a target software resource in at least one category of software resources for the vehicle's cockpit domain system, and send identification information corresponding to the target software resource to the cloud device; wherein, the at least one category of software resources includes different functional modules of the vehicle's cockpit domain system that are pre-divided into layers according to the software architecture; download the target update package pushed by the cloud device; wherein, the target update package is determined by the cloud device from at least one first update package based on the target software resource identifier; each first update package carries the software resource identifier of its corresponding category of software resources; and the target software resource is updated based on the target update package.

[0210] In some embodiments, the vehicle 1201 is also used to send a vehicle model code to the cloud device; wherein, vehicles corresponding to different vehicle model codes are adapted to software resources with different version numbers; download the target update package pushed by the cloud device; the target update package is determined by the cloud device from at least one first update package based on the first target version number and the identification information corresponding to the target software resource; the first target version number is determined by the cloud device based on the vehicle model code.

[0211] In some embodiments, the identification information of any type of software resource includes the software component number and the version number; the identification information of the target software resource includes the target software component number and the target version number; the target update package is determined by the cloud device from at least one third update package based on the first target version number; the version number of the third update package is higher than the target version number; the at least one third update package is determined by the cloud device from the at least one second update package based on the target version number; the second update package represents the update package corresponding to the software resource with the same target software component number; the at least one second update package is determined by the cloud device from the at least one first update package based on the target software component number.

[0212] Figure 13 A schematic diagram of the structure of a vehicle updating device provided in an embodiment of the present application is shown as follows: Figure 13 As shown, the vehicle updating device 1300 includes: a receiving module 1301, a determining module 1302 and a pushing module 1303, wherein: the receiving module 1301 is used to receive a target software resource identifier corresponding to a target software resource in at least one category of software resources sent by the vehicle; wherein the at least one category of software resources includes different functional modules of the cockpit domain system of the vehicle pre-divided into layers according to the software architecture; the determining module 1302 is used to determine a target update package corresponding to the target software resource from at least one first update package based on the target software resource identifier; wherein each first update package carries the software resource identifier of its corresponding category of software resources; the pushing module 1303 is used to push the target update package corresponding to the target software resource to the vehicle to update the target software resource in the vehicle.

[0213] In some embodiments, the determination module 1302 is further used to receive a vehicle model code sent by the vehicle; wherein, vehicles corresponding to different vehicle model codes are adapted to software resources with different version numbers; based on the vehicle model code, the first target version number corresponding to the target software resource is determined; based on the first target version number and the identification information corresponding to the target software resource, the target update package corresponding to the target software resource is determined from the at least one first update package.

[0214] In some embodiments, the identification information of any type of software resource includes a software component number and a version number; the identification information of the target software resource includes a target software component number and a target version number; the determination module 1302 is also used to determine at least one second update package from the at least one first update package based on the target software component number; the second update package represents an update package corresponding to a software resource with the same target software component number; at least one third update package is determined from the at least one second update package based on the target version number; the version number of the third update package is higher than the target version number; the target update package is determined from the at least one third update package based on the first target version number.

[0215] Figure 14 A schematic diagram of the structure of a vehicle updating device provided in an embodiment of the present application is shown as follows: Figure 14 As shown, the vehicle updating device 1400 includes: a sending module 1401, a downloading module 1402 and an updating module 1403, wherein: the sending module 1401 is used to send the target software resource identifier of the target software resource to the cloud device in response to an update event of the target software resource in at least one category of software resources of the vehicle cockpit domain system; wherein the at least one category of software resources includes different functional modules of the vehicle's cockpit domain system pre-divided into layers according to the software architecture; the downloading module 1402 is used to download the target update package pushed by the cloud device; the target update package is determined by the cloud device from at least one first update package based on the target software resource identifier; wherein each of the first update packages carries the software resource identifier of its corresponding category of software resources; the updating module 1403 is used to update the target software resource based on the target update package.

[0216] In some embodiments, the sending module 1401 is also used to send a vehicle model code to the cloud device; wherein, vehicles corresponding to different vehicle model codes are adapted to software resources with different version numbers; download the target update package pushed by the cloud device; the target update package is determined by the cloud device from at least one first update package based on the first target version number and the identification information corresponding to the target software resource; the first target version number is determined by the cloud device based on the vehicle model code.

[0217] In some embodiments, the identification information of any type of software resource includes the software component number and the version number; the identification information of the target software resource includes the target software component number and the target version number; the target update package is determined by the cloud device from at least one third update package based on the first target version number; the version number of the third update package is higher than the target version number; the at least one third update package is determined by the cloud device from the at least one second update package based on the target version number; the second update package represents the update package corresponding to the software resource with the same target software component number; the at least one second update package is determined by the cloud device from the at least one first update package based on the target software component number.

[0218] Figure 15 A schematic diagram of the structure of a vehicle cabin area system partitioning device provided in an embodiment of the present application is shown as follows: Figure 15 As shown, the vehicle cockpit domain system division device 1500 includes: an acquisition module 1501 and a decoupling module 1502, wherein: the acquisition module 1501 is used to obtain the software resource package of the cockpit domain system; the decoupling module 1502 is used to decouple the software resource package of the cockpit domain system to generate a first software resource package and a second software resource package; the first software resource package includes the system firmware and driver files of the cockpit system; the second software package includes multiple application programs for implementing different functions.

[0219] In some embodiments, the vehicle cabin domain system division device 1500 also includes a processing module (not shown in the figure), which is used to standardize each application in the second software resource package to generate a third software resource package and a third software resource package; the third software resource package includes a public version application corresponding to each application; the fourth software resource package includes customized resources corresponding to each application.

[0220] In some embodiments, the decoupling module 1502 is further configured to decouple multiple application programs in the second software resource package to generate multiple independent application programs.

[0221] The description of the above device embodiment is similar to the description of the method embodiment, and has similar beneficial effects as the same method embodiment. In some embodiments, the functions or modules included in the device provided in the embodiment of the present application can be used to perform the method described in the method embodiment. For technical details not disclosed in the device embodiment of the present application, please refer to the description of the method embodiment of the present application for understanding.

[0222] A computer device provided in an embodiment of the present application may be an electronic device, a vehicle, a cloud device (such as a laptop computer, a desktop computer, a server cluster, etc.) when implemented, and includes a processor and a memory, wherein the memory is used to store a computer program; the processor is used to execute the computer program stored in the memory to implement the above method.

[0223] An embodiment of the present application provides a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the above method is implemented. The computer-readable storage medium can be transient or non-transient.

[0224] It should be noted that, in the embodiment of the present application, if the above method is implemented in the form of a software function module and sold or used as an independent product, it can also be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the embodiment of the present application is essentially or the part that contributes to the relevant technology can be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for executing all or part of the above methods of each embodiment of the present application. The aforementioned storage medium includes various media that can store program codes, such as a U disk, a mobile hard disk, a read-only memory (ROM), a magnetic disk or an optical disk. In this way, the embodiment of the present application is not limited to any specific hardware, software or firmware, or any combination of hardware, software and firmware.

[0225] An embodiment of the present application provides a computer program, including computer-readable code. When the computer program is running, the processor executes some or all of the steps for implementing the above method.

[0226] An embodiment of the present application provides a computer program product, which includes a non-transitory computer-readable storage medium storing a computer program, and when the computer program is read and executed by a computer, implements some or all of the steps in the above method. The computer program product can be implemented specifically by hardware, software, or a combination thereof. In some embodiments, the computer program product is specifically embodied as a computer storage medium. In other embodiments, the computer program product is specifically embodied as a software product, such as a software development kit (SDK).

[0227] It should be noted that the descriptions of the various embodiments above tend to emphasize the differences between the various embodiments, and their similarities or similarities can be referenced to each other. The descriptions of the above device, storage medium, computer program, and computer program product embodiments are similar to the descriptions of the above method embodiments and have similar beneficial effects as the method embodiments. For technical details not disclosed in the embodiments of the device, storage medium, computer program, and computer program product of this application, please refer to the description of the method embodiments of this application for understanding.

[0228] Figure 16 A schematic diagram of the structure of a computer device is provided for the embodiment of the present application. Figure 16 As shown, the computer device 1600 can be any one of the following: a cloud device, a vehicle, or an electronic device; the hardware entity of the computer device 1600 includes: a processor 1601, a communication interface 1602, and a memory 1603, wherein:

[0229] The processor 1601 generally controls the overall operations of the electronic device 1600 .

[0230] The communication interface 1602 enables the electronic device to communicate with other terminals or servers through a network.

[0231] The memory 1603 is configured to store instructions and applications executable by the processor 1601, and can also cache data to be processed or processed by the processor 1601 and various modules in the electronic device 1600 (for example, image data, audio data, voice communication data, and video communication data). This can be implemented using flash memory (FLASH) or random access memory (RAM). Data can be transmitted between the processor 1601, the communication interface 1602, and the memory 1603 via the bus 1604.

[0232] It should be understood that "one embodiment" or "an embodiment" mentioned throughout the specification characterizes that specific features, structures or characteristics related to the embodiment are included in at least one embodiment of the present application. Therefore, "in one embodiment" or "in an embodiment" appearing throughout the specification does not necessarily refer to the same embodiment. In addition, these specific features, structures or characteristics can be combined in one or more embodiments in any suitable manner. It should be understood that in the various embodiments of the present application, the size of the serial numbers of the above-mentioned steps / processes does not represent the order of execution, and the execution order of each step / process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application. The above-mentioned serial numbers of the embodiments of the present application are for description only and do not characterize the advantages and disadvantages of the embodiments.

[0233] It should be noted that, in this document, the terms "comprises," "includes," or any other variations thereof are intended to encompass non-exclusive inclusion, such that a process, method, article, or apparatus comprising a series of elements includes not only those elements but also other elements not explicitly listed, or elements inherent to such process, method, article, or apparatus. In the absence of further limitations, an element defined by the phrase "comprising a ..." does not exclude the presence of other identical elements in the process, method, article, or apparatus comprising the element.

[0234] In the several embodiments provided in this application, it should be understood that the disclosed devices, equipment and methods can be implemented in other ways. The device and equipment embodiments described above are merely schematic. For example, the division of the units is merely a logical function division. In actual implementation, there may be other division methods, such as: multiple units or components can be combined, or can be integrated into another system, or some features can be ignored or not executed. In addition, the coupling, direct coupling, or communication connection between the components shown or discussed can be through some interfaces, and the indirect coupling or communication connection of the devices or units can be electrical, mechanical or other forms.

[0235] The units described above as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units; they may be located in one place or distributed across multiple network units; some or all of the units may be selected according to actual needs to achieve the purpose of the scheme of this embodiment.

[0236] In addition, all functional units in the embodiments of the present application can be integrated into one processing unit, or each unit can be a separate unit, or two or more units can be integrated into one unit; the above-mentioned integrated units can be implemented in the form of hardware or in the form of hardware plus software functional units.

[0237] Those skilled in the art will understand that all or part of the steps of implementing the above-mentioned method embodiment can be completed by hardware related to program instructions, and the aforementioned program can be stored in a computer-readable storage medium. When the program is executed, it executes the steps of the above-mentioned method embodiment; and the aforementioned storage medium includes: mobile storage devices, read-only memories (ROM), magnetic disks or optical disks, and other media that can store program codes.

[0238] Alternatively, if the above-mentioned integrated unit of the present application is implemented in the form of a software functional module and sold or used as an independent product, it can also be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, or the part that contributes to the relevant technology, can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes a number of instructions for enabling a device to execute all or part of the methods described in each embodiment of the present application. The aforementioned storage medium includes: various media that can store program codes, such as mobile storage devices, ROMs, magnetic disks or optical disks.

[0239] The above is only an implementation method of the present application, but the scope of protection of the present application is not limited thereto. Any technician familiar with this technical field can easily think of changes or replacements within the technical scope disclosed in this application, which should be covered by the scope of protection of the present application.

Claims

1. A vehicle updating method, characterized in that: Applied to a cloud device, the method includes: Receiving identification information corresponding to a target software resource in at least one type of software resources sent by a vehicle; wherein the at least one type of software resources includes different functional modules of a cockpit domain system of the vehicle pre-divided into layers according to a software architecture; Determining a target update package corresponding to the target software resource from at least one first update package based on the identification information corresponding to the target software resource; wherein each first update package carries the identification information of the software resource of the corresponding category; Pushing a target update package corresponding to the target software resource to the vehicle to update the target software resource in the vehicle.

2. The method according to claim 1, characterized in that The determining, from at least one first update package, a target update package corresponding to the target software resource based on identification information corresponding to the target software resource comprises: Receive a vehicle model code sent by the vehicle; wherein vehicles corresponding to different vehicle model codes are adapted to software resources with different version numbers; Determining a first target version number corresponding to the target software resource based on the vehicle model code; A target update package corresponding to the target software resource is determined from the at least one first update package based on the first target version number and identification information corresponding to the target software resource.

3. The method according to claim 2, characterized in that The identification information of any type of software resource includes a software component number and a version number; the identification information of the target software resource includes a target software component number and a target version number; and determining a target update package corresponding to the target software resource from the at least one first update package based on the first target version number and the identification information corresponding to the target software resource includes: Determining at least one second update package from the at least one first update package based on the target software part number; the second update package represents an update package corresponding to a software resource having the same part number as the target software; determining at least one third update package from the at least one second update package based on the target version number; the version number of the third update package being higher than the target version number; The target update package is determined from the at least one third update package based on the first target version number.

4. A vehicle updating method, characterized in that: Applied to a vehicle, the method comprises: In response to an update event of a target software resource in at least one category of software resources of a vehicle cockpit domain system, sending identification information corresponding to the target software resource to a cloud device; wherein the at least one category of software resources includes different functional modules of the vehicle cockpit domain system pre-divided into layers according to a software architecture; Downloading the target update package pushed by the cloud device; wherein the target update package is determined by the cloud device from at least one first update package based on the target software resource identifier; each first update package carries the software resource identifier of its corresponding category of software resource; The target software resource is updated based on the target update package.

5. The method according to claim 4, characterized in that The method further comprises: The vehicle model code sent to the cloud device; wherein vehicles corresponding to different vehicle model codes are adapted to software resources with different versions; Download the target update package pushed by the cloud device; the target update package is determined by the cloud device from at least one first update package based on the first target version number and the identification information corresponding to the target software resource; the first target version number is determined by the cloud device based on the vehicle model code.

6. The method according to claim 5, characterized in that The identification information of any type of software resource includes the software component number and version number corresponding to the corresponding type of software resource; the identification information of the target software resource includes the target software component number and target version number; The target update package is determined by the cloud device from at least one third update package based on the first target version number; the version number of the third update package is higher than the target version number; The at least one third update package is determined by the cloud device from the at least one second update package based on the target version number; the second update package represents an update package corresponding to a software resource having the same software version number as the target software; The at least one second update package is determined by the cloud device from the at least one first update package based on the target software part number.

7. A method for dividing a cockpit domain system, characterized in that: Applied to electronic equipment, the method includes: Obtaining a software resource package for the cockpit domain system; The software resource package of the cockpit domain system is decoupled to generate a first software resource package and a second software resource package; the first software resource package includes the system firmware and driver files of the cockpit system; the second software package includes multiple application programs for implementing different functions.

8. The method according to claim 7, characterized in that The method further comprises: Each application in the second software resource package is standardized to generate a third software resource package and a fourth software resource package; the third software resource package includes a public version application corresponding to each application; the fourth software resource package includes customized resources corresponding to each application.

9. The method according to claim 7, characterized in that The method further comprises: The multiple application programs in the second software resource package are decoupled to generate multiple independent application programs.

10. A vehicle updating system, characterized in that: Including cloud devices and vehicles, among which, The vehicle is configured to send identification information corresponding to a target software resource in at least one type of software resources for a vehicle cockpit domain system to the cloud device; wherein the at least one type of software resources includes different functional modules of the vehicle cockpit domain system pre-divided into layers according to a software architecture; The cloud device is configured to determine a target update package from at least one first update package based on the identification information corresponding to the target software resource, and push the target update package to the vehicle; wherein each first update package carries a software resource identification of a corresponding category of software resource; The vehicle is further configured to download the target update package pushed by the cloud device and update the target software resource based on the target update package.

Images