Commercially available judgment methods, devices, vehicles, cloud servers, and storage media.

Abstract

This application relates to a method, apparatus, vehicle, cloud server, and storage medium for determining salability. The method includes: updating the vehicle's list of available standardized product units (SPMs) after determining that the vehicle meets set conditions; synchronizing the SPM list to the cloud server, enabling the cloud server to identify the product to be identified based on the SPM list; and, if the cloud server determines that the product to be identified matches the SPM list, setting the product's sale status for the vehicle to be available for sale. In this application, the cloud server can identify the product to be identified based on the SPM list, facilitating access for relevant personnel to obtain salable products for the aforementioned vehicle and providing convenience for them to order their preferred goods.

Description

Technical Field

[0001] This application relates to the field of vehicle technology, specifically to a method, apparatus, vehicle, cloud server, and storage medium for determining marketability. Background Technology

[0002] As the automotive industry moves towards a service-oriented architecture (SOA), software-defined vehicles are becoming a trend. Users can subscribe to and order their favorite automotive products (digital goods, also known as services) anytime, anywhere, such as monthly subscriptions for autonomous driving assistance products or pay-per-use automatic parking products.

[0003] To meet users' personalized and diverse needs, automotive products will be updated more rapidly, and OTA upgrades will be more frequent. Different software versions support different types of salable products, and many plug-in hardware devices will gradually support the resale of products. Determining which products are salable for a vehicle in its current state has become one of the challenges for software service operations. Summary of the Invention

[0004] One objective of this application is to provide a method for determining the sellability of a vehicle, which can determine the sellability status of a product for a vehicle; a second objective of this application is to provide a method for determining the sellability of a cloud server; a third objective of this application is to provide a device for determining the sellability of a vehicle; a fourth objective of this application is to provide a device for determining the sellability of a cloud server; a fifth objective of this application is to provide a vehicle; a sixth objective of this application is to provide a cloud server; and a seventh objective of this application is to provide a storage medium.

[0005] To achieve the above objectives, firstly, this application provides a method for determining marketability, applied to vehicles, the method comprising:

[0006] Once it is determined that the vehicle meets the set conditions, the list of available standardized product units for the vehicle is updated; wherein, the list of available standardized product units includes multiple standardized product units available for the vehicle;

[0007] The list of available standardized product units is synchronized to the cloud server, so that the cloud server can identify the product to be identified based on the list of available standardized product units, and when the cloud server determines that the product to be identified matches the list of available standardized product units, the sales status of the product to be identified for the vehicle is set to be available for sale.

[0008] Furthermore, determining that the vehicle meets the set conditions includes at least one of the following:

[0009] It has been determined that the vehicle's software has been modified;

[0010] It has been determined that the pluggable hardware of the vehicle has been modified.

[0011] Furthermore, updating the list of available standardized product units for the vehicle includes:

[0012] The vehicle's onboard application system obtains the software development kit (SDK) of the vehicle's current state;

[0013] The vehicle-side application system obtains the list of available standardized product units corresponding to the software development kit.

[0014] Furthermore, synchronizing the list of available standardized product units to the cloud server includes:

[0015] The vehicle-side application system synchronizes the list of available standardized product units to the vehicle's activation center;

[0016] The activation center synchronizes the list of available standardized product units to the cloud server.

[0017] Furthermore, the method for determining whether something is available for sale includes:

[0018] At set intervals, the vehicle is periodically checked to see if it meets the set conditions.

[0019] To achieve the above objectives, secondly, this application also provides a method for determining marketability, applied to a cloud server, the method comprising:

[0020] A list of available standardized product units for the vehicle; wherein the list of available standardized product units includes multiple standardized product units available for the vehicle;

[0021] The product to be identified is based on the available list of standardized product units.

[0022] If it is determined that the product to be identified matches the list of available standardized product units, the sales status of the product to be identified for the vehicle is set to available for sale.

[0023] Further, determining that the product to be identified matches the list of available standardized product units includes:

[0024] Obtain the list of standardized product units to be identified corresponding to the product to be identified;

[0025] It is determined that all the standardized product units to be identified in the list of standardized product units to be identified belong to the list of available standardized product units.

[0026] To achieve the above objectives, in a third aspect, this application also provides a marketability determination device applied to a vehicle, the marketability determination device comprising:

[0027] An update module is used to update the list of available standardized product units for a vehicle when the vehicle meets the set conditions; wherein the list of available standardized product units includes multiple standardized product units available for the vehicle.

[0028] The first synchronization module is used to synchronize the list of available standardized product units to the cloud server, so that the cloud server can identify the product to be identified based on the list of available standardized product units, and when the cloud server determines that the product to be identified matches the list of available standardized product units, it sets the sales status of the product to be identified for the vehicle to be sold.

[0029] To achieve the above objectives, in a fourth aspect, this application also provides a marketability determination device applied to a cloud server, the marketability determination device comprising:

[0030] The second synchronization module is used to synchronize the list of available standardized product units for the vehicle; wherein the list of available standardized product units includes multiple standardized product units available for the vehicle.

[0031] The judgment module is used to identify the product to be identified based on the available standardized product unit list;

[0032] The setting module is used to set the sale status of the product to be identified for the vehicle to be available for sale when it is determined that the product to be identified matches the list of available standardized product units.

[0033] To achieve the above objectives, in a fifth aspect, this application also provides a vehicle, including: a first processor and a first memory, wherein the first processor is configured to execute a control program stored in the first memory to implement the saleability determination method as described in any of the first aspects above.

[0034] To achieve the above objectives, in a sixth aspect, this application also provides a cloud server, including: a second processor and a second memory, wherein the second processor is configured to execute a control program stored in the second memory to implement the salability determination method as described in any of the second aspects above.

[0035] To achieve the above objectives, in a seventh aspect, this application also provides a storage medium storing one or more programs that can be executed by one or more processors to implement the saleability determination method as described above.

[0036] The beneficial effects of this application are:

[0037] In this application, the vehicle can update its list of available standardized product units in a timely manner and synchronize the updated list to the cloud server. Once the cloud server receives the list of available standardized product units, it can identify the product to be identified based on this list, quickly and accurately determining whether the product is available for sale with respect to the vehicle. The cloud server can then set the sale status of the salable product to be identified for the vehicle, facilitating access for relevant personnel to purchase their preferred goods. Attached Figure Description

[0038] Figure 1 This diagram illustrates a flowchart of a method for determining marketability according to an embodiment of this application.

[0039] Figure 2 This diagram illustrates a flowchart of a method for determining marketability according to an embodiment of this application.

[0040] Figure 3 This diagram illustrates a marketability determination system provided in an embodiment of this application.

[0041] Figure 4 This diagram illustrates the structure of a marketability determination device according to an embodiment of this application.

[0042] Figure 5 This diagram illustrates the structure of a marketability determination device according to an embodiment of this application.

[0043] Figure 6 This illustration shows a structural diagram of a vehicle according to an embodiment of this application;

[0044] Figure 7 This diagram illustrates the structure of a cloud server provided in an embodiment of this application.

[0045] in:

[0046] 1. Cloud service system; 11. Software development platform; 12. Product configuration center; 13. Product sales center; 2. Vehicle-side system; 21. Vehicle-side application system; 22. Activation and activation center; 3. Terminal;

[0047] 10a. Update module; 20a. First synchronization module; 30a. Confirm module; 10b. Second synchronization module; 20b. Judgment module; 30b. Setting module;

[0048] 100. Vehicle; 101. First processor; 102. First memory; 1021. Operating system; 1022. Application program; 103. User interface; 104. Network interface; 105. Bus system;

[0049] 200. Cloud server; 201. Second processor; 202. Communication interface; 203. Second memory; 204. Communication bus. Detailed Implementation

[0050] The embodiments of this application will be described below with reference to the accompanying drawings and preferred embodiments. Those skilled in the art can easily understand other advantages and effects of this application from the content disclosed in this specification. This application can also be implemented or applied through other different specific embodiments, and various details in this specification can also be modified or changed based on different viewpoints and applications without departing from the spirit of this application. It should be understood that the preferred embodiments are only for illustrating this application and are not intended to limit the scope of protection of this application.

[0051] It should be noted that the illustrations provided in the following embodiments are only schematic representations of the basic concept of this application. Therefore, the drawings only show the components related to this application and are not drawn according to the actual number, shape and size of the components in the actual implementation. In the actual implementation, the form, quantity and proportion of each component can be arbitrarily changed, and the layout of the components may also be more complex.

[0052] The embodiments of this application will be described below with reference to the accompanying drawings and preferred embodiments. Those skilled in the art can easily understand other advantages and effects of this application from the content disclosed in this specification. This application can also be implemented or applied through other different specific embodiments, and various details in this specification can also be modified or changed based on different viewpoints and applications without departing from the spirit of this application. It should be understood that the preferred embodiments are only for illustrating this application and are not intended to limit the scope of protection of this application.

[0053] To facilitate understanding of the embodiments of this application, the following will provide further explanation and description with reference to the accompanying drawings and specific embodiments. These embodiments do not constitute a limitation on the embodiments of this application.

[0054] This embodiment provides a method for determining whether a vehicle is marketable, which can be applied to vehicles. (Reference) Figure 1 and Figure 3 As shown, the method may include:

[0055] S110. If it is determined that the vehicle meets the set conditions, update the list of available standardized product units for the vehicle; wherein, the list of available standardized product units includes multiple standardized product units available for the vehicle.

[0056] S120. Synchronize the list of available standardized product units to the cloud server so that the cloud server can identify the product to be identified based on the list of available standardized product units. If the cloud server determines that the product to be identified matches the list of available standardized product units, it sets the sales status of the product to be identified for vehicles to be sold.

[0057] In step S110, the set conditions can be set according to actual conditions, and their specific content is not limited. Determining that the vehicle meets the set conditions may include at least one of the following:

[0058] It has been confirmed that the vehicle's software has been modified;

[0059] It has been confirmed that the vehicle's pluggable hardware has been modified.

[0060] The methods for modifying the vehicle's software can include online upgrades (OTA upgrades), software deletion and addition, offline software upgrades, or other modification methods, without limitation.

[0061] Modifications to the vehicle's pluggable hardware may include the deletion and addition of pluggable hardware, or other modification methods, without limitation.

[0062] It should be noted that when a vehicle undergoes software modifications or plug-in hardware modifications, the standardized product units (also known as atomic products, denoted as SPUs) available to the vehicle may change. In other words, the list of available standardized product units (hereinafter referred to as the available SPU list) may change. Therefore, if it is confirmed that the vehicle's software and / or plug-in hardware has been modified, the list of available SPUs should be updated to ensure its reliability.

[0063] The vehicle may include a vehicle-side application system 21. When updating the list of available SPUs in the vehicle, the vehicle-side application system 21 can obtain the latest list of available SPUs through a software development kit, thereby updating the list of available SPUs in the vehicle.

[0064] Specifically, the vehicle-side application system 21 can first obtain the software development kit (SDK) of the vehicle in its current state, and then obtain the list of available SPUs corresponding to the SDK. This list of available SPUs is the list of available SPUs corresponding to the vehicle in its current state. It should be noted that the current state can refer to the state after it is determined that the vehicle's software has been modified and / or that the vehicle's pluggable hardware has been modified.

[0065] The vehicle may have multiple software programs installed, each corresponding to an SDK, and each SDK corresponding to at least one SPU. In this application, the vehicle-side application system 21 can obtain all the SPUs corresponding to each SDK in the vehicle, and then determine the list of all obtained SPUs as the available SPU list for the vehicle.

[0066] In addition, a timed inspection mechanism can be set in the vehicle. The vehicle can be checked at set intervals to see if it meets the set conditions. The set interval can be set according to the actual situation, and its specific duration is not limited.

[0067] For example, the interval can be set to t, meaning that the vehicle can perform a check every t interval to check whether the vehicle's software has been modified and whether the vehicle's plug-in hardware has been modified. If it is determined that the vehicle's software and / or plug-in hardware has been modified, it means that the available SPUs of the vehicle may have changed, and the latest list of available SPUs can be obtained through the vehicle application system 21 to achieve timely updates of the list of available SPUs.

[0068] It should be noted that, in addition to the above methods, other methods can also be used to update the list of available SPUs in a timely manner, and there are no restrictions on these methods.

[0069] In step S120, after the vehicle obtains the updated list of available SPUs, it can synchronize the latest list of available SPUs to the cloud server, that is, send the updated list of available SPUs to the cloud server to ensure the reliability of the list of available SPUs in the cloud server.

[0070] When a vehicle synchronizes its available SPU list to the cloud server, the vehicle application system 21 can first synchronize the available SPU list to the vehicle's activation center 22, and then the activation center 22 can synchronize the available standardized product unit list to the product configuration center 12 of the cloud server, thereby realizing the synchronization of the available SPU list between the vehicle and the cloud server.

[0071] The vehicle-side application system 21 and the activation center 22 can communicate via the DDS (Data Distribution Service, a data-centric distributed communication protocol). Of course, they can also communicate in other ways, which are not limited.

[0072] It should be noted that the vehicle-side application system 21 obtains the list of available SPUs through the SDK and synchronizes the list to the vehicle's activation center 22, which can be recorded as the vehicle's SPU self-registration. In this application, if a self-registration process fails, the vehicle-side application system 21 can employ a compensation mechanism to ensure successful self-registration. This compensation mechanism can be a second self-registration or other mechanisms; no limitation is made on this.

[0073] After a vehicle completes SPU self-registration, the activation center 22 processes the available SPU list in two steps. First, if the activation center 22 does not store the old available SPU list, it stores the received available SPU list. If the old available SPU list stored in the activation center 22 is inconsistent with the received available SPU list, the newly received available SPU list overwrites the old list, and the new list is saved. At this point, the available SPU list in the activation center 22 reflects the vehicle's current status. Second, the activation center 22 synchronizes the stored available SPU list and vehicle information to the product configuration center 12 on the cloud server. This informs the product configuration center 12 of the vehicle information and the available SPUs for that vehicle. The synchronization process is ensured to be successful by the activation center 22. It should be noted that vehicle information can be identifying information that identifies the vehicle, such as the vehicle's VPN (Vehicle Identification Number).

[0074] The vehicles and cloud servers can communicate via the MQTT (Message Queuing Telemetry Transport) protocol. Of course, they can also communicate in other ways, and there are no restrictions on this.

[0075] In addition, in this application, when the cloud server needs to determine whether the product to be identified is available for sale, it can identify the product based on the list of available SPUs synchronized from the vehicle, and when the cloud server determines that the product to be identified matches the list of available SPUs, it sets the sales status of the product to be identified for the vehicle to be available for sale.

[0076] The cloud server can first obtain all SPUs of the product to be identified to obtain a list of SPUs to be identified. Then, it compares the list of SPUs to be identified with the list of available SPUs to determine whether the product to be identified is salable for the vehicle corresponding to the list of available SPUs.

[0077] In this method, vehicles can update their available SPU list in a timely manner and synchronize the updated list to the cloud server. Once the cloud server receives the available SPU list, it can quickly and accurately determine whether the product is available for sale on the vehicle. It can then set the sale status of the available product to be sold on the vehicle, making it convenient for relevant personnel to access and order their preferred goods.

[0078] This embodiment provides a method for determining marketability, which can be applied to cloud servers. (Reference) Figure 2 and Figure 3 As shown, the method may include:

[0079] S210, List of available standardized product units for synchronized vehicles; wherein, the list of available standardized product units includes multiple standardized product units available for the vehicle;

[0080] S220. Identify the product to be identified based on a list of available standardized product units;

[0081] S230. If it is determined that the product to be identified matches the list of available standardized product units, the sale status of the product to be identified for the vehicle shall be set to available for sale.

[0082] In step S210, synchronizing the vehicle's available SPU list refers to synchronizing the vehicle's available SPUs to the cloud server. When the vehicle's available SPU list is updated, the vehicle can send its latest SPU list to the cloud server, and the cloud server can then obtain the latest available SPU list from the vehicle, thereby completing the synchronization of the vehicle's available SPU list.

[0083] It should be noted that the synchronization of the available SPU list between the cloud server and the vehicle can be referred to the relevant description of step 120 in the other embodiments above, and will not be repeated here.

[0084] In step S220, when the cloud server needs to determine whether a product is available for sale, that product can be recorded as a product to be identified. The cloud server can determine the availability of the product based on the list of available SPUs synchronized from the vehicle. It should be noted that the product here refers to a digital product, which can also be called a service, and may include at least one SPU.

[0085] In this application, operators can generate SPUs in the product configuration center 12 of the cloud server. An SPU is a function defined according to the needs of each application system. For example, the SPU corresponding to automatically turning on the air conditioner can be coded 0001, and the SPU corresponding to turning on the seat massage can be coded 0002, etc. After generating SPUs in the product configuration center 12 of the cloud server, operators can record the generated SPUs in the SPU data warehouse of the cloud server.

[0086] Then, the cloud server's software development platform 11 initiates the SPU application process. Specifically, the software development platform 11 can directly apply for SPUs generated by the product configuration center 12 via an HTTP communication interface; alternatively, the product configuration center 12 can synchronize the generated SPUs to the software development platform 11.

[0087] To address the uncertainty regarding the number and timing of new SPU additions, a timed mechanism can be implemented to periodically request new SPUs from the software development platform 11 or push them to the product configuration center 12, ensuring the integrity of the SPUs on the software development platform 11. The software development platform 11 can store the requested SPUs in a database.

[0088] Operations personnel configure different products according to different needs. After the product configuration is completed, the product sales center 13 records and stores the product information from the product configuration center 12 and then lists the products. The product information includes the product's service type (i.e., its included SPUs), service method (e.g., monthly / annual / pay-per-use), sales amount, and status (i.e., whether it is listed). After the product information is configured, it can be updated in the data warehouse. Then, a cloud-based interface for querying available products for sale is provided.

[0089] In addition, the cloud server can be provided with SPU self-registration, activation, deactivation, and verification capabilities by the software development platform 11. Based on the developer's needs, the required SPUs can be integrated into the software development platform 11 and the corresponding SDKs can be generated.

[0090] For example, if application A needs to integrate SPUs coded as 001 and 002, and application B needs to integrate SPUs coded as 003 and 004, then version V1 SDK (for application A) and version V2 SDK (for application B) can be generated respectively. The SPUs corresponding to the SDK of application A (version V1 SDK) include those coded as 001 and 002; the SPUs corresponding to the SDK of application B (version V2 SDK) include those coded as 003 and 004. Furthermore, vehicle application developers can develop and reserve the required SPUs in the vehicle application system 21, and integrate the required SDK versions (e.g., version V1, version V2, etc.).

[0091] When operators configure products in the Product Configuration Center 12, they can do so based on the full SPU list within the center. In other words, operators can configure products using all the SPUs listed in the Product Configuration Center 12. It should be noted that the SPUs available for some vehicles may not be the same as those in the Product Configuration Center 12. This means that products configured by operators in the Product Configuration Center 12 may not be usable on some vehicles. For such products, if their sales status is set to "available for sale" for those vehicles, even if relevant personnel purchase the product, it will not be usable on those vehicles. Therefore, it is necessary to identify whether a product is available for sale to better ensure that relevant personnel can purchase reliable products.

[0092] In step S230, it should be noted that the cloud server's product configuration center 12 can create a first data warehouse corresponding to the available SPU list and a second data warehouse corresponding to the full SPU list. After the cloud server synchronizes the available SPU list of vehicles, it can separately record the SPUs in the available SPU list synchronized from the vehicles into the first data warehouse and save the vehicle information. In this way, the SPUs generated by the product configuration center 12 and the available SPUs of the vehicles can be distinguished at the data level.

[0093] In this step, the product configuration center 12 can compare and filter the products configured by the operators and the SPUs in the first data warehouse, thereby marking the products that integrate the SPUs available for the vehicle as available for sale.

[0094] The cloud server can perform SPU detection on the product to be identified. It can first obtain all the SPUs corresponding to the product to be identified and record them as a list of SPUs to be identified. If it is determined that all the SPUs in the product are available SPUs, that is, if it is determined that all the SPUs in the list of SPUs to be identified belong to the list of available SPUs, then it can be considered that the product can be used by the vehicle corresponding to the above-mentioned list of available SPUs. The sales status of the product to be identified for the above-mentioned vehicle can then be set to available for sale and stored.

[0095] For example, a safe driving experience product might have two SPUs: assisted driving and autonomous driving. The assisted driving SPU is coded 10001, and the autonomous driving SPU is coded 10002. If both SPUs coded 10001 and 10002 are listed in the available SPU list, then the safe driving experience product is available for sale for the vehicle corresponding to that vehicle, and its sale status can be set to "available for sale." If SPU coded 10002 is not listed in the available SPU list, then the safe driving experience product is not available for sale for that vehicle, and its sale status can be set to "unavailable for sale."

[0096] Additionally, the application (APP) on terminal 3 can interact with the product sales center 13 on the cloud server through a specific communication protocol to obtain a list of salable products. Terminal 3 includes, but is not limited to, mobile phones, in-vehicle terminals, computers, etc. When terminal 3 is a mobile phone, the phone can obtain the list of salable products through its installed mobile application. When terminal 3 is an in-vehicle terminal, the in-vehicle terminal can obtain the list of salable products through its installed in-vehicle application. When terminal 3 is a computer, the computer can obtain the list of salable products through its web page.

[0097] Once a product is listed in the product sales center 13, users can access the list of available products in the car mall via the internet on their mobile phones, computers, and in-vehicle terminals, and then order their favorite items. After a user purchases a product, the product's SPU (Special Purpose Unit) is transmitted to the corresponding vehicle by the cloud server, and the activation system is activated. The activation system verifies and activates the relevant SPU, completing the closed loop of the process.

[0098] It should be noted that for some products, although some of their SPUs may not be included in the vehicle's available SPU list, this may not affect the implementation of other SPUs for that product. Therefore, when determining the sellability of a product to be identified, if it is determined that the product can be implemented using some of its SPUs, then if it is determined that some of the SPUs in the product's list of products to be identified are included in the available SPU list, the product's sellability status for the vehicle corresponding to the aforementioned available SPUs can be set to sellable.

[0099] In this method, vehicles can update their available SPU list in a timely manner and synchronize the updated list to the cloud server. Once the cloud server receives the available SPU list, it can quickly and accurately determine whether the product is available for sale on the vehicle. It can then set the sale status of the available product to be sold on the vehicle, making it convenient for relevant personnel to access and order their preferred goods.

[0100] This embodiment provides a method for determining marketability, which can be applied to a marketability determination system. (Reference) Figure 3 As shown, the salability determination system can be a system composed of a terminal and a cloud. The terminal refers to vehicle-side system 1, which is applied to vehicles. Vehicle-side system 1 may include vehicle-side application system 21 and activation center 22. Vehicle-side application system 21 may include vehicle-side applications, and vehicle-side application system 21 and activation center 22 can communicate via the DDS protocol. The cloud refers to cloud service system 1, which can be applied to cloud servers. Cloud service system 1 may include a product sales center 13, a product configuration center 12, and a software development platform 11. Product sales center 13, product configuration center 12, and software development platform 11 can communicate via the HTTP protocol. Furthermore, cloud service system 1 and vehicle-side system 1 can interact via the MQTT protocol.

[0101] This method can be divided into two parts: configuration development and business implementation. The configuration development stage is the preparatory stage for the business implementation process, primarily targeting automotive company operations and development personnel. This stage is applicable to all vehicles and includes: SPU generation, product configuration, SPU application, generation of SPU-related SDKs, vehicle application system integration SDKs, and vehicle software version upgrades, etc. The business implementation stage mainly focuses on determining whether a product is available for sale, and includes: SPU self-registration, synchronization of the available SPU list, product availability identification, and product sales, etc.

[0102] In the configuration development phase, operations personnel can configure products in the product configuration center 12 based on the generated SPUs. After product configuration is complete, the product sales center 13 prices the products and lists them on the product marketplace. Before this phase, operations personnel first need to generate SPUs in the product configuration center 12, and then the software development platform 11 applies for the SPUs. After the application is completed, vehicle application developers can generate different versions of the SDK on the software development platform 11 according to their needs by integrating at least one SPU. The SDK may include functions such as SPU self-registration, activation, deactivation, and verification. Next, vehicle application developers can develop their applications, reserve the required SPUs in the applications, and integrate the necessary SDKs.

[0103] In the business implementation phase, after the vehicle undergoes OTA (Over-The-Air) updates or a new version of the vehicle (i.e., modification of pluggable hardware), the vehicle-side application system 21 can collect the SPUs in the application through the SDK's self-registration function, thereby obtaining a list of available SPUs for the current vehicle status, and registering the SPUs in the available SPU list to the vehicle-side activation center 22. The vehicle-side activation center 22 stores the SPUs in the available SPU list and then synchronizes the available SPU list to the product configuration center 12 on the cloud server. After obtaining all available SPUs on the vehicle, the product configuration center 12 can identify the sellability of the products to be identified based on the available SPU list. Products that meet the sellability criteria are then processed for sale; that is, the sellability status of the products corresponding to the available SPUs is set to sellable for the vehicle. Then, users can browse the sellable products in the product mall through terminals 3 (such as mobile phones, in-vehicle terminals, or computers, etc.) and subscribe to or order their favorite sellable products. This can meet the growing demand for the sale and operation of goods (i.e., digital goods, also known as software goods).

[0104] This embodiment provides a marketability determination device applicable to vehicles. This device can be used to implement the aforementioned marketability determination method applied to vehicles. For example, refer to... Figure 4 As shown, the device may include:

[0105] The update module 10a is used to update the list of available standardized product units for the vehicle under certain conditions; wherein the list of available standardized product units includes multiple standardized product units available for the vehicle.

[0106] The first synchronization module 20a is used to synchronize the list of available standardized product units to the cloud server, so that the cloud server can identify the product to be identified based on the list of available standardized product units, and set the sales status of the product to be identified for the vehicle to be sold when the cloud server determines that the product to be identified matches the list of available standardized product units.

[0107] This embodiment provides a marketability determination device that can be applied to vehicles. (Reference) Figure 4 As shown, the device may include a determining module 30a, wherein the determining module 30a may be used for at least one of the following:

[0108] It has been confirmed that the vehicle's software has been modified;

[0109] It has been confirmed that the vehicle's pluggable hardware has been modified.

[0110] This embodiment provides a marketability determination device that can be applied to vehicles. (Reference) Figure 4As shown, in this device, the update module 10a can be used to control:

[0111] The vehicle's onboard application system obtains the software development kit (SDK) of the vehicle's current status;

[0112] The vehicle-side application system obtains a list of available standardized product units corresponding to the software development kit.

[0113] This embodiment provides a marketability determination device that can be applied to vehicles. (Reference) Figure 4 As shown, in this device, the first synchronization module 20a can be used to control:

[0114] The vehicle-side application system will synchronize the list of available standardized product units to the vehicle's activation and activation center;

[0115] The activation center will synchronize the list of available standardized product units to the cloud server.

[0116] This embodiment provides a marketability determination device that can be applied to vehicles. (Reference) Figure 4 As shown, in this device, the determining module 30a can be used to periodically check whether the vehicle meets the set conditions at set intervals.

[0117] This embodiment provides a sellability determination device, which can be applied to a cloud server. This device can be used to implement the aforementioned sellability determination method applied to a cloud server. For example, refer to... Figure 5 As shown, the device may include;

[0118] The second synchronization module 10b is used to synchronize the list of available standardized product units for the vehicle; wherein the list of available standardized product units includes multiple standardized product units available for the vehicle.

[0119] The judgment module 20b is used to identify the product to be identified based on a list of available standardized product units.

[0120] Setting module 30b is used to set the sale status of the product to be identified for the vehicle to be sold when it is determined that the product to be identified matches the list of available standardized product units.

[0121] This embodiment provides a device for determining whether a product is marketable, which can be applied to cloud servers. (Reference) Figure 5 As shown, in this device, the judgment module 20a can be used for:

[0122] Obtain a list of standardized product units to be identified corresponding to the product to be identified;

[0123] All standardized product units in the list of standardized product units to be identified are included in the list of available standardized product units.

[0124] This embodiment provides a vehicle. The vehicle can be a pure electric vehicle, a hybrid electric vehicle, or other vehicles that include an electric motor; there is no limitation on the type.

[0125] refer to Figure 6 As shown, the vehicle 100 includes at least one first processor 101, a first memory 102, at least one network interface 104, and other user interfaces 103. The various components in the vehicle 100 are coupled together via a bus system 105. It is understood that the bus system 105 is used to enable communication between these components. In addition to a data bus, the bus system 105 also includes a power bus, a control bus, and a status signal bus. However, for clarity, all buses are referred to as bus system 105.

[0126] The user interface 103 may include a display, keyboard, or click vehicle (e.g., mouse, trackball, touchpad, or touchscreen).

[0127] It is understood that the first memory 102 in the embodiments of this application can be a volatile first memory or a non-volatile first memory, or may include both volatile and non-volatile first memories. The non-volatile first memory can be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or flash memory. The volatile first memory can be a random access memory (RAM), which serves as an external cache. By way of example, but not limitation, many forms of RAM are available, such as Static RAM (SRAM), Dynamic RAM (DRAM), Synchronous DRAM (SDRAM), Double Data Rate SDRAM (DDRSDRAM), Enhanced SDRAM (ESDRAM), Synchronous Link DRAM (SLDRAM), and Direct Rambus RAM (DRRAM). The first memory 102 described herein is intended to include, but is not limited to, these and any other suitable types of first memory.

[0128] In some implementations, the first memory 102 stores elements, executable units or data structures, or subsets thereof, or extended sets thereof: operating system 1021 and application program 1022.

[0129] The operating system 1021 includes various system programs, such as a framework layer, a core library layer, and a driver layer, used to implement various basic business functions and handle hardware-based tasks. The application program 1022 includes various applications, such as a media player and a browser, used to implement various application functions. Programs implementing the methods of this application embodiment can be included in the application program 1022.

[0130] In this embodiment of the application, by calling the program or instructions stored in the first memory 102, specifically the program or instructions stored in the application program 1022, the first processor 101 is used to execute the methods provided in the various method embodiments.

[0131] The methods disclosed in the embodiments of this application can be applied to or implemented by the first processor 101. The first processor 101 may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method can be completed by the integrated logic circuit of the hardware or by instructions in the form of software in the first processor 101. The first processor 101 may be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. It can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of this application. The general-purpose first processor may be a microprocessor or any conventional processor. The steps of the methods disclosed in the embodiments of this application can be directly embodied in the execution of a hardware decoding processor, or executed by a combination of hardware and software units in the decoding processor. The software units may be located in random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, or other mature storage media in the art. The storage medium is located in the first memory 102. The first processor 101 reads the information in the first memory 102 and completes the above method in conjunction with its hardware.

[0132] It is understood that the embodiments described herein can be implemented in hardware, software, firmware, middleware, microcode, or a combination thereof. For hardware implementation, the processing unit can be implemented in one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing vehicles (DSPDs), programmable logic vehicles (PLDs), field-programmable gate arrays (FPGAs), general-purpose processors, controllers, microcontrollers, microprocessors, other electronic units for performing the functions described herein, or combinations thereof.

[0133] For software implementation, the techniques described herein can be implemented by units that perform the functions described herein. The software code can be stored in memory and executed by a processor. The memory can be implemented in the processor or external to the processor.

[0134] This embodiment provides a cloud server. For example... Figure 7 As shown, the cloud server 200 may include a second processor 201, a communication interface 202, a second memory 203, and a communication bus 204, wherein the second processor 201, the communication interface 202, and the second memory 203 communicate with each other through the communication bus 204.

[0135] The second memory 203 is used to store computer programs;

[0136] In one embodiment of this application, the second processor 201 is used to execute the program stored in the second memory 203 to implement the saleability determination method provided in any of the aforementioned method embodiments applied to a cloud server.

[0137] This application also provides a storage medium (computer-readable storage medium). This storage medium stores one or more programs. The storage medium may include volatile memory, such as random access memory; it may also include non-volatile memory, such as read-only memory, flash memory, hard disk, or solid-state drive; and it may also include combinations of the above types of memory.

[0138] When one or more programs in a storage medium can be executed by one or more processors.

[0139] When this storage medium is applied to a vehicle, the method described above, which is executed in the vehicle, can be implemented. The processor executes the vehicle control program stored in the memory to implement the method described above, which is executed in the vehicle.

[0140] When this storage medium is used in a cloud server, the methods described above for execution on the cloud server can be implemented. The processor executes the cloud server control program stored in the memory to implement the methods described above for execution on the cloud server.

[0141] Those skilled in the art will further recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of both. To clearly illustrate the interchangeability of hardware and software, the components and steps of the various examples have been generally described in terms of functionality in the foregoing description. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0142] It should be noted that the terms "one implementation," "embodiment," "exemplary embodiment," and "some embodiments" used in the specification indicate that the described embodiment may include a specific feature, structure, or characteristic, but not every embodiment necessarily includes that specific feature, structure, or characteristic. Furthermore, such phrases do not necessarily refer to the same embodiment. Moreover, when a specific feature, structure, or characteristic is described in connection with an embodiment, implementing such a feature, structure, or characteristic in conjunction with other embodiments, whether explicitly described or not, is within the knowledge scope of those skilled in the art.

[0143] It should be noted that, in this document, relational terms such as "first" and "second" are used merely to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or vehicle that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or vehicle. Unless otherwise specified, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or vehicle that includes said element.

[0144] The above embodiments are merely preferred embodiments provided to fully illustrate this application, and the scope of protection of this application is not limited thereto. Equivalent substitutions or modifications made by those skilled in the art based on this application are all within the scope of protection of this application.

Claims

1. A sellable judgment method applied to a vehicle, characterized by, The sellable judgment method comprises: updating an available standardized product unit list of the vehicle under the condition that the vehicle meets a set condition; wherein the available standardized product unit list comprises a plurality of standardized product units available to the vehicle; synchronizing the available standardized product unit list to a cloud server, so that the cloud server identifies a to-be-identified commodity based on the available standardized product unit list, and sets a sellable state of the to-be-identified commodity to be sellable for the vehicle in the case that the cloud server determines that the to-be-identified commodity matches the available standardized product unit list; the determination that the vehicle meets the set condition comprises: determining that a plug-in hardware of the vehicle is modified; wherein the modification of the plug-in hardware of the vehicle comprises deletion and / or addition of the plug-in hardware.

2. The sellable judgment method according to claim 1, characterized by, The determination that the vehicle meets the set condition further comprises: determining that software of the vehicle is modified.

3. The sellable judgment method according to claim 1, characterized by, The updating of the available standardized product unit list of the vehicle comprises: an application system at a vehicle end of the vehicle acquires a software development kit under a current state of the vehicle; the application system at the vehicle end acquires the available standardized product unit list corresponding to the software development kit.

4. The sellability judging method according to claim 3, characterized by The synchronization of the available standardized product unit list to the cloud server comprises: the application system at the vehicle end synchronizes the available standardized product unit list to an activation center of the vehicle; the activation center synchronizes the available standardized product unit list to the cloud server.

5. The sellable judgment method according to any one of claims 1 to 4, characterized in that, The sellable judgment method comprises: checking whether the vehicle meets the set condition at a set interval.

6. A sellable judgment method applied to a cloud server of the sellable judgment method according to any one of claims 1-5, characterized in that, The sellable judgment method comprises: synchronizing an available standardized product unit list of a vehicle; wherein the available standardized product unit list comprises a plurality of standardized product units available to the vehicle; identifying a to-be-identified commodity based on the available standardized product unit list; setting a sellable state of the to-be-identified commodity to be sellable for the vehicle in the case that it is determined that the to-be-identified commodity matches the available standardized product unit list.

7. The sellable judgment method according to claim 6, wherein The determination that the to-be-identified commodity matches the available standardized product unit list comprises: acquiring a to-be-identified standardized product unit list corresponding to the to-be-identified commodity; determining that all to-be-identified standardized product units in the to-be-identified standardized product unit list belong to the available standardized product unit list.

8. A salability determination device, applied to a vehicle, characterized in that, The sellable judgment device is used to implement the sellable judgment method according to any one of claims 1-5, and comprises: an updating module, configured to update an available standardized product unit list of the vehicle under the condition that the vehicle meets a set condition; wherein the available standardized product unit list comprises a plurality of standardized product units available to the vehicle; The first synchronization module is configured to synchronize the list of available standardized product units to a cloud server, so that the cloud server identifies a to-be-identified commodity based on the list of available standardized product units, and sets a sale state of the to-be-identified commodity as saleable for the vehicle in a case where the cloud server determines that the to-be-identified commodity matches the list of available standardized product units. 9.A sellable judgment device applied to a cloud server, characterized in that, The saleable judgment device is configured to implement the saleable judgment method of claim 6 or 7, and the saleable judgment device comprises: The second synchronization module is configured to synchronize a list of available standardized product units of a vehicle, wherein the list of available standardized product units comprises a plurality of standardized product units available for the vehicle. The judgment module is configured to identify a to-be-identified commodity based on the list of available standardized product units. The setting module is configured to set a sale state of the to-be-identified commodity as saleable for the vehicle in a case where it is determined that the to-be-identified commodity matches the list of available standardized product units.

10. A vehicle characterized by comprising: The first processor and the first memory are included. The first processor is configured to execute a control program stored in the first memory to implement the saleable judgment method of any one of claims 1-5.

11. A cloud server, characterized by, The second processor and the second memory are included. The second processor is configured to execute a control program stored in the second memory to implement the saleable judgment method of claim 6 or 7.

12. A storage medium, characterized by The storage medium stores one or more programs, and the one or more programs are executable by one or more processors to implement the saleable judgment method of any one of claims 1-7.

Images