Vehicle traffic recharging method, recharging device, storage medium and vehicle

Abstract

This application provides a method, device, storage medium, and vehicle for recharging vehicle data traffic. The method, applied to the field of intelligent connected vehicles, includes: responding to a vehicle's data traffic recharge request by identifying the recharge type; obtaining the vehicle's model and identification code, and determining a baseline recharge data volume based on the model and identification code; determining a target recharge data volume based on the recharge type and baseline recharge data volume, and recharging the vehicle's data traffic by accessing the corresponding operator's recharge port based on the target recharge data volume. This method automatically calls the operator's recharge port to perform the data traffic recharge action according to the vehicle's data traffic recharge request, ensuring that the recharged data traffic takes effect in real time without affecting the vehicle's infotainment system. Simultaneously, it meets user data traffic needs while reducing vehicle manufacturers' data traffic resource procurement expenditures and improving the rationality of data traffic allocation.

Description

Technical Field

[0001] This application relates to the field of intelligent connected vehicles, and more specifically, to a method for charging traffic for a vehicle, a charging device, a storage medium, and a vehicle in the field of intelligent connected vehicles. Background Technology

[0002] Currently, intelligent connected vehicles require network traffic to access the internet and use other intelligent functions; otherwise, these functions cannot function properly. At present, the network traffic for intelligent connected vehicles is provided by automakers through centralized procurement, with some automakers offering users free data for a certain period, and others offering lifetime free data to meet users' needs for intelligent connected vehicle services.

[0003] In related technologies, the following three recharge methods are used to recharge vehicle data: 1. Purchasing a data package with a certain validity period, where the validity period and the amount of data used are determined by whichever comes first; 2. Purchasing an unlimited data package for a certain number of years, where the validity period ends on time; 3. Using a data pool to guarantee free data usage for vehicles within a certain time frame, where the validity period ends on time. However, all three of these data recharge methods result in a waste of data resources, increase the procurement costs of data resources for enterprises, and are difficult to meet the data needs of different users at different times. Summary of the Invention

[0004] This application provides a vehicle data top-up device, a storage medium, and a vehicle, which can reduce the data resource procurement expenditure of car manufacturers and meet the data needs of different users.

[0005] In a first aspect, a method for topping up data for a vehicle is provided. The method includes: in response to a data top-up request from a vehicle, identifying the top-up type of the data top-up request; obtaining the vehicle model and identification code, and determining a baseline top-up data volume based on the vehicle model and identification code; determining a target top-up data volume based on the top-up type and the baseline top-up data volume, and retrieving the corresponding operator's top-up port to top up the data for the vehicle based on the target top-up data volume.

[0006] According to the vehicle data top-up method of this application embodiment, during vehicle operation, the vehicle's data top-up needs are monitored in real time. When a data top-up need is determined, the top-up type is identified, and the vehicle model and identification code are obtained. A baseline top-up data volume is determined based on the model and identification code. Then, a target top-up data volume is determined based on the top-up type and baseline top-up data volume. Based on the target top-up data volume, the corresponding operator's top-up port is invoked to top up the vehicle's data. Therefore, this method automatically invokes the operator's top-up port to perform the data top-up action according to the vehicle's data top-up needs, ensuring that the top-up data volume takes effect in real time and does not affect the use of the vehicle's infotainment system. This satisfies users' data needs while reducing the vehicle manufacturer's data resource procurement expenditure and improving the rationality of data allocation.

[0007] In conjunction with the first aspect, in some possible implementations, the vehicle data top-up method further includes: obtaining the vehicle's remaining data and determining a preset top-up threshold based on the vehicle model; in response to the remaining data being less than or equal to the preset top-up threshold, determining that the vehicle has a first data top-up requirement, wherein the top-up type of the first data top-up requirement is a regular data top-up; or in response to the vehicle's OTA (Over-The-Air) upgrade requirement, determining that the vehicle has a second data top-up requirement, wherein the top-up type of the second data top-up requirement is an OTA data top-up.

[0008] The above technical solution enables the setting of differentiated preset recharge thresholds based on vehicle model and distinguishes between two types of recharge needs, thereby achieving precise allocation of traffic resources.

[0009] In combination with the first aspect and the above implementation methods, in some possible implementation methods, the target recharge traffic is determined based on the recharge type and the baseline recharge traffic, including: when the recharge type is ordinary traffic recharge, the baseline recharge traffic is used as the target recharge traffic; when the recharge type is OTA traffic recharge, the OTA demand traffic for OTA upgrade needs is identified, and the target recharge traffic is determined based on the remaining traffic, the preset recharge threshold, the OTA demand traffic, and the baseline recharge traffic.

[0010] The above technical solution can distinguish between regular data top-up and OTA data top-up, eliminating the need for manual top-up of data for vehicles requiring OTA, reducing human error, and ensuring real-time data demand for OTA.

[0011] In combination with the first aspect and the above implementation methods, in some possible implementation methods, the target recharge traffic is determined based on the remaining traffic, the preset recharge threshold, the OTA demand traffic, and the baseline recharge traffic, including: determining the demand recharge traffic based on the remaining traffic, the preset recharge threshold, and the OTA demand traffic; when the demand recharge traffic is greater than the baseline recharge traffic, the demand recharge traffic is used as the target recharge traffic; when the demand recharge traffic is less than or equal to the baseline recharge traffic, the baseline recharge traffic is used as the target recharge traffic.

[0012] Through the above technical solution, the required recharge traffic can be accurately judged by the remaining traffic, preset recharge threshold and OTA required traffic, so as to determine the target recharge traffic. This ensures the OTA traffic needs are met while saving recharge traffic resources and reducing waste.

[0013] In conjunction with the first aspect, in some possible implementations, when a vehicle includes multiple vehicle-to-everything (V2X) communication cards, the corresponding operator's recharge port is accessed to recharge the vehicle's data based on the target recharge data volume. This includes: obtaining the card identification codes of the multiple V2X communication cards; determining the remaining rechargeable data volume of the multiple V2X communication cards based on the card identification codes; determining the target V2X communication card for data recharge based on the remaining rechargeable data volume of the multiple V2X communication cards and the target recharge data volume; and accessing the operator's recharge port corresponding to the target V2X communication card to recharge the vehicle's data volume based on the target recharge data volume.

[0014] The above technical solution can maximize the use of multiple vehicle-to-everything (V2X) communication cards, ensure reasonable resource allocation, avoid resource waste, and match the operator's recharge port, making the recharge process more efficient and stable.

[0015] In conjunction with the first aspect, in some possible implementations, the vehicle data recharge method further includes: determining a preset automatic recharge period for the vehicle; responding to the data recharge request when the time of receiving the data recharge request falls within the preset automatic recharge period; and generating a corresponding process recharge reminder signal when the time of receiving the data recharge request falls outside the preset automatic recharge period.

[0016] The above technical solution can centralize vehicle recharge demands within a specific time period for unified processing, making the recharge process more orderly.

[0017] In combination with the first aspect and the above implementation methods, in some possible implementation methods, the vehicle's data recharge method further includes: identifying the current time and calculating the time difference between the current time and the end time of the preset automatic recharge cycle; when the time difference is less than a preset time threshold, generating an operation reminder signal so that the user can adjust the preset automatic recharge cycle based on the operation reminder signal.

[0018] The above technical solution can promptly remind users when the preset automatic recharge period is insufficient, ensuring the continuous and stable network service of the vehicle.

[0019] Secondly, a vehicle data top-up device is provided, comprising: an identification module for identifying the top-up type of the data top-up request in response to the vehicle's data top-up request; a determination module for obtaining the vehicle's model and identification code, and determining a base top-up data volume based on the model and identification code; and a control module for determining a target top-up data volume based on the top-up type and the base top-up data volume, and retrieving the corresponding operator's top-up port to top up the vehicle's data volume based on the target top-up data volume.

[0020] Thirdly, a computer-readable storage medium is provided that stores computer program code, which, when executed on a computer, causes the computer to perform the methods described in the first aspect or any possible implementation thereof.

[0021] Fourthly, a vehicle is provided, the vehicle comprising: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein when the processor executes the computer program, the computer performs the method of the first aspect or any possible implementation thereof. Attached Figure Description

[0022] Figure 1 This is a schematic flowchart illustrating a method for topping up vehicle data traffic according to an embodiment of this application.

[0023] Figure 2 This is a schematic diagram of a vehicle data recharge architecture provided in a specific embodiment of this application.

[0024] Figure 3 This is a schematic flowchart illustrating a method for topping up vehicle data traffic according to a specific embodiment of this application.

[0025] Figure 4 This is a schematic diagram of a vehicle traffic recharge device provided in an embodiment of this application.

[0026] Figure 5 This is a schematic diagram of the vehicle structure provided in the embodiments of this application. Detailed Implementation

[0027] The technical solutions in this application will be clearly and thoroughly described below with reference to the accompanying drawings. In the description of the embodiments of this application, unless otherwise stated, " / " means "or," for example, A / B can mean A or B. "And / or" in the text is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, and B existing alone. Furthermore, in the description of the embodiments of this application, "multiple" refers to two or more than two.

[0028] Hereinafter, the terms "first" and "second" are used for descriptive purposes only and should not be construed as implying or suggesting relative importance or implicitly indicating the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include one or more of that feature.

[0029] In related technologies, the following three methods are used to recharge vehicle data: 1. Data Package Top-up Method. This method involves purchasing data packages with a specific validity period to top up vehicle data. The service terminates when either the validity period or the total available data is reached. For example, purchasing a "30-day 10GB" package will terminate if the data is used up before the 30 days are up, or if the data is not used up but the 30 days expire. Therefore, this method has limitations: some users may not use the service for a certain period, resulting in wasted data, while others may need to use the data when it expires. Conversely, some users may consume a lot of data and need to frequently purchase data packages.

[0030] 2. Purchasing an unlimited data plan. This involves buying an unlimited data plan for a fixed period (e.g., 1 year, 3 years), during which time you can use data as you please, with no data limit until the plan expires. However, this method also carries the risk of users purchasing an unlimited data plan but not actually using the data, resulting in a waste of the purchase price.

[0031] 3. Data Pool Top-up Method. This method involves multiple vehicles sharing a single data pool. Within an agreed-upon timeframe (e.g., one year), all vehicles share the data within the pool. The system terminates when the time expires, but will also end early if the total data in the pool is exhausted. While this method avoids wasting purchased data by sharing resources within the same data pool, the data pool still has an expiration date, after which the corresponding data in the pool will be cleared.

[0032] Therefore, the above three methods of recharging traffic will increase the cost of purchasing traffic resources for enterprises, and at the same time, they cannot meet the traffic needs of different users at different times.

[0033] To address at least one of the aforementioned technical problems, this application proposes a method for vehicle data top-up. During vehicle operation, the method monitors the vehicle's data top-up needs in real time and, in response, identifies the top-up type, obtains the vehicle model and identification code, determines a baseline top-up data volume based on the model and identification code, then determines a target top-up data volume based on the top-up type and baseline volume, and finally, retrieves the corresponding operator's top-up port to top up the vehicle's data volume based on the target volume. This ensures that the top-up data volume takes effect in real time, does not affect the vehicle's infotainment system, meets user data needs, reduces vehicle manufacturers' data resource procurement expenditures, and improves the rationality of data allocation.

[0034] Figure 1 This is a schematic flowchart illustrating a method for topping up vehicle data traffic according to an embodiment of this application.

[0035] For example, such as Figure 1 As shown, the method for topping up the vehicle's data traffic includes the following steps: S101. In response to the vehicle's data recharge request, identify the recharge type of the data recharge request.

[0036] Specifically, the identification conditions for a vehicle's data recharge needs can be pre-defined. For example, if the vehicle's remaining data is less than a preset lower limit, it is considered that the vehicle has a data recharge need. When the vehicle starts the high data function, in order to ensure the smooth operation of the function, it is considered that the vehicle has a data recharge need. The specific conditions can be defined according to the actual situation, and there are no restrictions.

[0037] During vehicle operation, data usage is monitored to determine if the vehicle requires data top-up. If a top-up is confirmed, the type of top-up is identified. The top-up type characterizes the data top-up scenario. For example, if a top-up is triggered because the vehicle's remaining data is below a preset minimum, it's considered a standard data top-up; if a high-data-flow function is activated, it's considered a function-triggered data top-up.

[0038] S102. Obtain the vehicle model and identification code, and determine the baseline recharge flow rate based on the vehicle model and identification code.

[0039] Among them, the vehicle model is a standardized classification name for vehicles, used to differentiate vehicle hardware specifications in batches, and serves as the basic standard for calculating the baseline traffic; the identification code is the vehicle's VIN (Vehicle Identification Number), which is the unique identifier of the vehicle. The baseline recharge traffic is the size of the baseline traffic package for a single recharge of a vehicle, pre-calibrated for different vehicle models and vehicle VINs.

[0040] In other words, the mapping relationship between vehicle model, vehicle VIN, and baseline recharge traffic can be pre-defined. When a vehicle is identified as having a traffic recharge requirement, a table is retrieved based on the vehicle model and VIN code to identify the corresponding baseline recharge traffic, which is then used as the basis for traffic distribution.

[0041] S103. Determine the target recharge volume based on the recharge type and the baseline recharge volume, and retrieve the corresponding operator recharge port to recharge the vehicle's data volume based on the target recharge volume.

[0042] Specifically, the target recharge flow is the actual recharge flow to the vehicle in this recharge action. For example, a baseline recharge flow adjustment strategy can be pre-defined for each recharge type. For instance, when the recharge type is normal data recharge, the baseline recharge flow adjustment strategy is: use the baseline recharge flow as the target recharge flow; when the recharge type is function-triggered data recharge, the baseline recharge flow adjustment strategy is: match the corresponding flow adjustment threshold according to the function type, and use the sum of the baseline recharge flow and the flow adjustment threshold as the target recharge flow.

[0043] After determining the target data recharge amount, the corresponding operator's recharge port is accessed to recharge the vehicle's data, ensuring that the recharged data takes effect immediately and does not affect the vehicle's infotainment system. Simultaneously, this method confirms the target data recharge amount in real time based on the data recharge demand, meeting user data needs while preventing redundant expenditures on data resource procurement by automakers and improving the rationality of data allocation.

[0044] In some embodiments of this application, the vehicle data top-up method further includes: obtaining the vehicle's remaining data and determining a preset top-up threshold based on the vehicle model; determining that the vehicle has a first data top-up requirement in response to the remaining data being less than or equal to the preset top-up threshold, wherein the top-up type of the first data top-up requirement is ordinary data top-up; or determining that the vehicle has a second data top-up requirement in response to the vehicle's OTA upgrade requirement, wherein the top-up type of the second data top-up requirement is OTA data top-up.

[0045] In other words, the vehicle's data recharge demand is pre-divided into the first data recharge demand triggered by insufficient remaining data, and the second data recharge demand triggered by OTA upgrades.

[0046] During vehicle operation, the system acquires real-time data on vehicle model, data usage, and function triggering. Based on the vehicle model, a corresponding preset recharge threshold is matched. This preset recharge threshold represents the minimum data usage amount required to perform a data recharge action.

[0047] The remaining data of a vehicle is identified based on its data usage. When the remaining data drops to a preset recharge threshold, it is considered that the remaining data of the vehicle is insufficient. In order not to affect the use of the vehicle's infotainment system, the first data recharge request is triggered. The type of the first data recharge request is a normal data recharge triggered due to insufficient data.

[0048] When an OTA upgrade is detected based on the vehicle's function triggering status, a second data recharge request is triggered to ensure the smooth execution of the OTA. The type of this second data recharge request is OTA data recharge triggered by the OTA upgrade.

[0049] The above technical solution enables the setting of differentiated preset recharge thresholds based on vehicle model and distinguishes between two types of recharge needs, thereby achieving precise allocation of traffic resources.

[0050] In some embodiments of this application, the target recharge flow is determined based on the recharge type and the baseline recharge flow, including: when the recharge type is ordinary flow recharge, the baseline recharge flow is used as the target recharge flow; when the recharge type is OTA flow recharge, the OTA demand flow for OTA upgrade needs is identified, and the target recharge flow is determined based on the remaining flow, the preset recharge threshold, the OTA demand flow, and the baseline recharge flow.

[0051] In other words, when the recharge type is determined to be a regular data recharge, the system automatically calls the corresponding telecom operator's data recharge interface to recharge the vehicle with a data package of the baseline size in real time. When the recharge type is determined to be an OTA data recharge, the system determines the OTA data requirement based on the OTA upgrade data package size, and matches the target recharge data with the remaining data, preset recharge threshold, and baseline recharge data. Then, it automatically calls the corresponding telecom operator's data recharge interface to recharge the vehicle with the target recharge data required for OTA in real time, ensuring the smooth execution of OTA.

[0052] The above technical solution can distinguish between regular data top-up and OTA data top-up, eliminating the need for manual top-up of data for vehicles requiring OTA, reducing human error, and ensuring real-time data demand for OTA.

[0053] In some embodiments of this application, determining the target recharge traffic based on the remaining traffic, the preset recharge threshold, the OTA demand traffic, and the baseline recharge traffic includes: determining the demand recharge traffic based on the remaining traffic, the preset recharge threshold, and the OTA demand traffic; when the demand recharge traffic is greater than the baseline recharge traffic, using the demand recharge traffic as the target recharge traffic; when the demand recharge traffic is less than or equal to the baseline recharge traffic, using the baseline recharge traffic as the target recharge traffic.

[0054] Specifically, the required replenishment traffic is determined based on the remaining traffic, the preset recharge threshold, and the OTA (Over-The-Air) demand traffic. For example, if the remaining traffic minus the OTA demand traffic is greater than or equal to the preset recharge threshold, the remaining traffic is considered sufficient for the OTA upgrade, and no additional replenishment is needed; the required recharge traffic is 0, meaning no recharge is performed. If the remaining traffic minus the OTA demand traffic is less than the preset recharge threshold, the required recharge traffic is calculated as: Preset recharge threshold - (Remaining traffic - OTA demand traffic).

[0055] Then, the required recharge flow rate is compared with the baseline recharge flow rate. The larger value between the required recharge flow rate and the baseline recharge flow rate is used as the target recharge flow rate. The flow rate recharge action for the vehicle is then executed. That is, when the required recharge flow rate is greater than the baseline recharge flow rate, the target recharge flow rate is equal to the required recharge flow rate; when the required recharge flow rate is less than or equal to the baseline recharge flow rate, the target recharge flow rate is equal to the baseline recharge flow rate.

[0056] Understandably, when the required data recharge amount is 0, the data recharge action for vehicles can be temporarily suspended to prevent waste of resources.

[0057] Through the above technical solution, the required recharge traffic can be accurately judged by the remaining traffic, preset recharge threshold and OTA required traffic, so as to determine the target recharge traffic. This ensures the OTA traffic needs are met while saving recharge traffic resources and reducing waste.

[0058] In some embodiments of this application, when a vehicle includes multiple vehicle-to-everything (V2X) communication cards, the vehicle is recharged using the corresponding operator's recharge port based on the target recharge data volume. This includes: obtaining the card identification codes of the multiple V2X communication cards; determining the remaining rechargeable data volume of the multiple V2X communication cards based on the card identification codes; determining the target V2X communication card for data recharge based on the remaining rechargeable data volume of the multiple V2X communication cards and the target recharge data volume; and recharging the vehicle using the operator's recharge port corresponding to the target V2X communication card based on the target recharge data volume.

[0059] In other words, when a vehicle has only one corresponding vehicle network communication card, the data top-up for that vehicle is completed by calling the operator's top-up port corresponding to that vehicle network communication card.

[0060] When multiple vehicle-to-everything (V2X) communication cards are installed in a vehicle, their card identification codes (ICCIDs, or Integrated Circuit Card Identifiers) can be obtained. The remaining data allowance for each V2X communication card can then be queried using these ICCIDs. Next, based on the remaining data allowance and the target data allowance, the target V2X communication card for this data top-up is determined. For example, a V2X communication card with a remaining data allowance greater than or equal to the target data allowance can be used as the target V2X communication card. Alternatively, if multiple V2X communication cards have remaining data allowances greater than or equal to the target data allowance, the V2X communication card with the higher priority can be used as the target V2X communication card according to a preset card priority. Alternatively, V2X communication cards can be called in order of preset card priority, combined with the remaining data allowance and target data allowance of each V2X communication card. The system targets the recharge data volume to determine the final target vehicle network communication card. If a vehicle has three corresponding vehicle network communication cards, they are assigned the preset card priorities as Card A, Card B, and Card C. The target recharge data volume is compared with the remaining rechargeable data volume of Card A. If the remaining rechargeable data volume of Card A is greater than or equal to the target recharge data volume, then Card A is determined as the target vehicle network communication card. If the remaining rechargeable data volume of Card A is less than the target recharge data volume, then it is further determined whether the sum of the remaining rechargeable data volume of Card B and Card A meets the target recharge data volume. If it does, then Card A and Card B are determined as the target vehicle network communication cards. This process is repeated to determine the target vehicle network communication card.

[0061] After identifying the target vehicle-to-everything (V2X) communication SIM card, the system retrieves the corresponding carrier's recharge port based on the target data recharge amount and recharges the vehicle's data. In essence, if there is only one target V2X communication SIM card, the system retrieves the recharge port corresponding to that SIM card to recharge the vehicle with the target data. If there are multiple target V2X communication SIM cards, the system retrieves the recharge ports corresponding to multiple target V2X communication SIM cards according to a pre-determined data allocation strategy to recharge the vehicle with the target data.

[0062] In some embodiments of this application, the vehicle data top-up method further includes: determining a preset automatic top-up cycle for the vehicle; responding to the data top-up request when the time of receiving the data top-up request is within the preset automatic top-up cycle; and generating a corresponding process top-up reminder signal when the time of receiving the data top-up request is outside the preset automatic top-up cycle.

[0063] In other words, the system pre-defines the corresponding automatic recharge period for each vehicle, automatically responds to data recharge requests received within the pre-determined automatic recharge period, and executes the data recharge strategy. For data recharge requests received outside the pre-determined automatic recharge period, the system does not execute the data recharge strategy, generates a corresponding process recharge reminder signal to remind the user to recharge, and allows the user to review and trigger the recharge strategy.

[0064] In some embodiments of this application, the vehicle data top-up method further includes: identifying the current time and calculating the time difference between the current time and the end time of a preset automatic top-up cycle; when the time difference is less than a preset time threshold, generating an operation reminder signal so that the user can adjust the preset automatic top-up cycle based on the operation reminder signal.

[0065] In other words, a recharge period expiration reminder function is also provided. The preset time threshold is used to determine whether the current time is close to the end time of the preset automatic recharge period. When the time difference between the current time and the end time of the preset automatic recharge period is less than the preset time threshold, it is considered that the preset automatic recharge period is about to expire, triggering a recharge period expiration reminder and generating an operation reminder signal so that users can adjust the preset automatic recharge period based on the operation reminder signal to ensure the stable implementation of the vehicle system function. When the time difference between the current time and the end time of the preset automatic recharge period is greater than or equal to the preset time threshold, it is considered that the preset automatic recharge period has not yet expired, and no recharge period expiration reminder is issued.

[0066] As one embodiment of this application, such as Figure 2 As shown, this vehicle data top-up method is applied to the data traffic operation management platform to automatically top up data traffic for vehicles whose remaining data traffic has reached a certain warning range in real time. The specific scheme is as follows: 1. The traffic operation management platform connects to the traffic management platforms of different telecom operators or third-party operators authorized by telecom operators, and develops a function for real-time traffic top-up for vehicles. This allows the traffic operation management platform to top up traffic by calling the telecom operator's traffic top-up interface in real time, and ensures that the topped-up traffic takes effect in real time without affecting the use of the vehicle's infotainment system. 2. The traffic operation management platform supports configuring remaining traffic warning thresholds according to vehicle type and traffic usage type, and has developed an interface for uploading vehicle data to the cloud platform. This interface is used to upload traffic usage data and OTA demand traffic data from the vehicle system, and to trigger corresponding traffic top-ups for traffic top-ups when there is remaining traffic and for real-time traffic top-ups during OTA upgrades. 3. The vehicle's infotainment system reports the vehicle model, vehicle VIN, vehicle network card number (ICCID), operator, and remaining data allowance to the cloud platform in real time by calling the traffic operation management platform interface; 4. The traffic operation management platform determines whether the vehicle needs to be recharged based on the traffic usage data uploaded by the vehicle and the threshold set according to the vehicle model. If the remaining traffic threshold is within the range of traffic that needs to be recharged, the platform will automatically call the corresponding telecom operator's traffic recharge interface to recharge the vehicle's traffic in real time. 5. When the vehicle's infotainment system receives an OTA upgrade push package, it determines the size of the current OTA upgrade package and calls the traffic operation management platform interface in real time to report the size of the OTA upgrade traffic package, the corresponding vehicle model, vehicle VIN, vehicle network card number ICCID, operator, and remaining traffic value to the traffic operation management platform. The traffic operation management platform automatically calls the corresponding telecom operator's traffic recharge interface to recharge the vehicle with the traffic required for OTA in real time, ensuring the smooth implementation of OTA. 6. When the traffic operation management platform receives the traffic data reported by the vehicle's infotainment system, it will recharge the vehicle with the set amount of traffic in real time if the remaining regular traffic is insufficient. 7. For OTA upgrade traffic needs, the traffic operation management platform automatically increases the set base traffic based on the traffic demand data reported by OTA and recharges the vehicle's traffic in real time. 8. Within the automatic recharge period set by the vehicle manufacturer, vehicles with insufficient data can be repeatedly recharged. For models that are about to exceed or have already exceeded the automatic recharge time set by the vehicle manufacturer, operators can reset the automatic recharge time on the platform.

[0067] like Figure 3 As shown, the vehicle data top-up method executed by this data traffic operation management platform includes the following steps: S301, obtain the vehicle model, vehicle VIN, vehicle network card number ICCID, and operator; S302 determines the preset recharge threshold based on the vehicle model and the base recharge flow rate based on the vehicle model and vehicle VIN.

[0068] S303 obtains real-time data on data usage uploaded by the vehicle's infotainment system to determine the vehicle's remaining data allowance.

[0069] S304, determine whether the remaining data allowance is less than or equal to the preset recharge threshold. If yes, then it is determined that there is a need for regular data allowance recharge, and proceed to step S305; otherwise, proceed to step S306.

[0070] S305, retrieve the corresponding operator's recharge port to recharge the vehicle with the base recharge data. Execute step S303.

[0071] S306, determine whether an OTA upgrade request for the vehicle has been received. If yes, then confirm that there is an OTA data recharge request and proceed to step S307; otherwise, proceed to step S303.

[0072] S307 identifies OTA demand traffic that requires OTA upgrades.

[0073] S308 determines the required recharge traffic based on the remaining traffic, the preset recharge threshold, and the OTA demand traffic.

[0074] S309, determine whether the required recharge volume is greater than the baseline recharge volume. If yes, proceed to step S310; otherwise, proceed to step S305.

[0075] S310, retrieve the corresponding operator's recharge port to recharge the vehicle with the required data traffic. Execute step S303.

[0076] This embodiment establishes a traffic operation management platform to collect real-time traffic consumption data uploaded by the vehicle's infotainment system and the traffic data required for OTA upgrades. The traffic operation management platform automatically determines when the remaining traffic reaches a certain warning threshold and recharges the vehicle's traffic data, ensuring that the vehicle has real-time traffic within the time frame provided by the car manufacturer, and maximizing the use of the recharged traffic data within its validity period or minimizing waste, thereby reducing the car manufacturer's traffic resource procurement costs.

[0077] Therefore, this embodiment can recharge vehicles with insufficient data in real time, and the amount of data recharged can be set to ensure that the recharged data is not wasted. At the same time, during OTA upgrades, there is no need to manually recharge the upgraded vehicles. Instead, the data is recharged according to the real-time OTA update of the vehicle, minimizing data waste and achieving the goal of reducing the car company's data resource procurement expenditure and meeting the data needs of different users.

[0078] In summary, the vehicle data top-up method according to the embodiments of this application monitors the vehicle's data top-up needs in real time during vehicle operation. When a data top-up need is determined, the top-up type is identified, and the vehicle model and identification code are obtained. A baseline top-up data volume is determined based on the model and identification code. Then, a target top-up data volume is determined based on the top-up type and baseline top-up data volume. The corresponding operator's top-up port is then invoked to top up the vehicle's data volume based on the target top-up data volume. Therefore, this method automatically invokes the operator's top-up port to perform the data top-up action according to the vehicle's data top-up needs, ensuring that the top-up data volume takes effect in real time without affecting the vehicle's infotainment system. This satisfies users' data needs while reducing vehicle manufacturers' data resource procurement expenditures and improving the rationality of data allocation.

[0079] Figure 4 This is a schematic diagram of a vehicle traffic recharge device provided in an embodiment of this application.

[0080] For example, such as Figure 4 As shown, the vehicle traffic recharge device 400 may include: an identification module 401, a determination module 402, and a control module 403.

[0081] The identification module 401 is used to identify the type of data recharge in response to the vehicle's data recharge request; the determination module 402 is used to obtain the vehicle's model and identification code, and determine the baseline recharge data based on the model and identification code; the control module 403 is used to determine the target recharge data based on the recharge type and baseline recharge data, and retrieve the corresponding operator's recharge port to recharge the vehicle's data based on the target recharge data.

[0082] According to one embodiment of this application, the identification module 401 is specifically used to: obtain the remaining data traffic of the vehicle and determine a preset recharge threshold based on the vehicle model; in response to the remaining data traffic being less than or equal to the preset recharge threshold, determine that the vehicle has a first data traffic recharge requirement, wherein the recharge type of the first data traffic recharge requirement is ordinary data traffic recharge; or in response to the vehicle's OTA upgrade requirement, determine that the vehicle has a second data traffic recharge requirement, wherein the recharge type of the second data traffic recharge requirement is OTA data traffic recharge.

[0083] According to one embodiment of this application, the control module 403 is specifically used to: when the recharge type is normal traffic recharge, use the base recharge traffic as the target recharge traffic; when the recharge type is OTA traffic recharge, identify the OTA demand traffic for OTA upgrades, and determine the target recharge traffic based on the remaining traffic, the preset recharge threshold, the OTA demand traffic, and the base recharge traffic.

[0084] According to one embodiment of this application, the control module 403 is specifically configured to: determine the required recharge traffic based on the remaining traffic, the preset recharge threshold, and the OTA required traffic; when the required recharge traffic is greater than the baseline recharge traffic, use the required recharge traffic as the target recharge traffic; when the required recharge traffic is less than or equal to the baseline recharge traffic, use the baseline recharge traffic as the target recharge traffic.

[0085] According to one embodiment of this application, the control module 403 is configured to: obtain the card identification codes of multiple vehicle network communication cards; determine the remaining rechargeable data traffic of the multiple vehicle network communication cards based on the card identification codes; determine the target vehicle network communication card for data traffic recharge based on the remaining rechargeable data traffic of the multiple vehicle network communication cards and the target recharge data traffic; and retrieve the operator recharge port corresponding to the target vehicle network communication card based on the target recharge data traffic to recharge the vehicle's data traffic.

[0086] According to one embodiment of this application, the control module 403 is further configured to: determine the preset automatic recharge cycle of the vehicle; respond to the data recharge request when the time of receiving the data recharge request is within the preset automatic recharge cycle; and generate a corresponding process recharge reminder signal when the time of receiving the data recharge request is outside the preset automatic recharge cycle.

[0087] According to one embodiment of this application, the control module 403 is specifically used to: identify the current time and calculate the time difference between the current time and the end time of the preset automatic recharge cycle; when the time difference is less than the preset time threshold, generate an operation reminder signal so that the user can adjust the preset automatic recharge cycle based on the operation reminder signal.

[0088] Figure 5 This is a schematic diagram of the structure of a vehicle provided in an embodiment of this application. The vehicle may include: The memory 501, the processor 502, and the computer program stored on the memory 501 and capable of running on the processor 502.

[0089] When processor 502 executes the program, it implements the traffic recharge method provided in the above embodiments.

[0090] Furthermore, the vehicle also includes: Communication interface 503 is used for communication between memory 501 and processor 502.

[0091] The memory 501 is used to store computer programs that can run on the processor 502.

[0092] The memory 501 may include high-speed RAM (Random Access Memory) memory, and may also include non-volatile memory, such as at least one disk storage.

[0093] If the memory 501, processor 502, and communication interface 503 are implemented independently, then the communication interface 503, memory 501, and processor 502 can be interconnected via a bus to complete communication between them. The bus can be an ISA (Industry Standard Architecture) bus, a PCI (Peripheral Component Interconnect) bus, or an EISA (Extended Industry Standard Architecture) bus, etc. The bus can be divided into address bus, data bus, control bus, etc. For ease of representation, Figure 5 The bus is represented by a single thick line, but this does not mean that there is only one bus or one type of bus.

[0094] Optionally, in a specific implementation, if the memory 501, processor 502, and communication interface 503 are integrated on a single chip, then the memory 501, processor 502, and communication interface 503 can communicate with each other through an internal interface.

[0095] The processor 502 may be a CPU (Central Processing Unit), an ASIC (Application Specific Integrated Circuit), or one or more integrated circuits configured to implement the embodiments of this application.

[0096] This application also provides a computer-readable storage medium storing a computer program thereon, which, when executed by a processor, implements the above-described data traffic recharge method.

[0097] Furthermore, the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include at least one of that feature. In the description of this application, "multiple" means at least two, such as two, three, etc., unless otherwise explicitly specified.

[0098] In the description of this specification, the references to terms such as "one embodiment," "some embodiments," "example," "specific example," or "some examples," etc., refer to specific features, structures, materials, or characteristics described in connection with that embodiment or example, which are included in at least one embodiment or example of this application. In this specification, the illustrative expressions of the above terms do not necessarily refer to the same embodiment or example. Furthermore, the specific features, structures, materials, or characteristics described may be combined in any suitable manner in one or more embodiments or examples. Moreover, without contradiction, those skilled in the art can combine and integrate the different embodiments or examples described in this specification, as well as the features of different embodiments or examples.

[0099] Although embodiments of this application have been shown and described above, it is understood that the above embodiments are exemplary and should not be construed as limiting this application. Those skilled in the art can make changes, modifications, substitutions and variations to the above embodiments within the scope of this application.

Claims

1. A method for topping up vehicle data traffic, characterized in that, The method includes: In response to a vehicle's data top-up request, the top-up type of the data top-up request is identified; Obtain the vehicle model and identification code, and determine the baseline recharge flow rate based on the vehicle model and identification code; The target recharge volume is determined based on the recharge type and the baseline recharge volume, and the corresponding operator recharge port is retrieved based on the target recharge volume to recharge the vehicle's data.

2. The method according to claim 1, characterized in that, The method further includes: Obtain the remaining data allowance for the vehicle and determine a preset recharge threshold based on the vehicle model; In response to the remaining data being less than or equal to the preset recharge threshold, it is determined that the vehicle has a first data recharge requirement, wherein the recharge type of the first data recharge requirement is a normal data recharge; or In response to the vehicle's OTA upgrade request, it is determined that the vehicle has a second data recharge request, wherein the recharge type of the second data recharge request is OTA data recharge.

3. The method according to claim 2, characterized in that, Determining the target recharge volume based on the recharge type and the baseline recharge volume includes: When the recharge type is normal data recharge, the base recharge data volume is used as the target recharge data volume; When the recharge type is OTA traffic recharge, the OTA demand traffic of the OTA upgrade requirement is identified, and the target recharge traffic is determined based on the remaining traffic, the preset recharge threshold, the OTA demand traffic, and the baseline recharge traffic.

4. The method according to claim 3, characterized in that, Determining the target recharge volume based on the remaining traffic, the preset recharge threshold, the OTA demand traffic, and the baseline recharge volume includes: The required recharge volume is determined based on the remaining traffic, the preset recharge threshold, and the OTA demand traffic. When the required recharge volume is greater than the baseline recharge volume, the required recharge volume is used as the target recharge volume; When the required recharge volume is less than or equal to the baseline recharge volume, the baseline recharge volume is used as the target recharge volume.

5. The method according to claim 1, characterized in that, When the vehicle includes multiple vehicle-to-everything (V2X) communication cards, the corresponding operator's recharge port is retrieved based on the target recharge data volume to recharge the vehicle's data volume, including: Obtain the card identification codes of the plurality of vehicle network communication cards, and determine the remaining rechargeable data traffic of the plurality of vehicle network communication cards based on the card identification codes; The target vehicle network communication card for data top-up is determined based on the remaining rechargeable data of the plurality of vehicle network communication cards and the target rechargeable data. Based on the target recharge data volume, the operator's recharge port corresponding to the target vehicle network communication card is retrieved to recharge the data volume for the vehicle.

6. The method according to claim 1, characterized in that, The method further includes: Determine the preset automatic recharge cycle for the vehicle; When the time of receiving the data recharge request falls within the preset automatic recharge cycle, the data recharge request is responded to. When the time of receiving the data recharge request is outside the preset automatic recharge cycle, a corresponding process recharge reminder signal is generated.

7. The method according to claim 6, characterized in that, The method further includes: Identify the current time and calculate the time difference between the current time and the end time of the preset automatic recharge cycle; When the time difference is less than a preset time threshold, an operation reminder signal is generated so that the user can adjust the preset automatic recharge cycle based on the operation reminder signal.

8. A vehicle data recharge device, characterized in that, The device includes: The identification module is used to identify the type of data recharge request in response to the vehicle's data recharge request; The determination module is used to obtain the vehicle model and identification code, and determine the baseline recharge flow rate based on the vehicle model and identification code; The control module is used to determine the target recharge flow based on the recharge type and the baseline recharge flow, and to retrieve the corresponding operator recharge port to recharge the vehicle based on the target recharge flow.

9. A computer-readable storage medium, characterized in that, It stores a computer program that, when executed by a processor, implements the data traffic recharge method according to any one of claims 1-7.

10. A vehicle, characterized in that, It includes a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein when the processor executes the computer program, it implements the data traffic recharge method according to any one of claims 1-7.

Images