Network traffic application method and apparatus, electronic device, and storage medium

By receiving fault log request commands and judging traffic application conditions, and combining configuration mechanisms and breakpoint resume mechanisms, the problem of insufficient traffic when vehicles upload fault logs is solved, ensuring that fault logs are uploaded to the cloud efficiently and securely, improving user experience and avoiding traffic waste.

CN119892615BActive Publication Date: 2025-11-18CHERY AUTOMOBILE CO LTD
View PDF 2 Cites 0 Cited by

Patent Information

Application Number
CN202510087552.9
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2025-01-20
Publication Date
2025-11-18
Estimated Expiration
2045-01-20

AI Technical Summary

Technical Problem

Vehicles face insufficient bandwidth when uploading fault logs, resulting in a degraded user experience. Furthermore, existing technologies, such as offline log copying or uploading with limited bandwidth, are inefficient and cannot meet the needs of uploading large files, thus affecting other basic services.

Method used

By receiving fault log request commands, the system determines whether the vehicle meets the traffic application requirements. If it does, it requests fault log traffic and controls the upload. If the upload is interrupted, it generates a reminder and resumes the upload through a breakpoint resume mechanism. Combining the configuration mechanism and the breakpoint resume mechanism, the system ensures efficient and secure uploading of fault logs.

Benefits of technology

It enables efficient and secure uploading of fault logs to the cloud, avoiding wasted bandwidth, improving user experience, and ensuring effective use of bandwidth.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119892615B_ABST
    Figure CN119892615B_ABST
Patent Text Reader

Abstract

The application relates to the technical field of vehicles, in particular to a network traffic application method and device, an electronic device and a storage medium. The method comprises the following steps: receiving a fault log request instruction of a target vehicle, uploading a fault log result, when the target vehicle meets a traffic application condition and the target vehicle does not have a fault log interruption condition, based on the fault log uploading result, requesting to apply for fault log traffic of the target vehicle to control the target vehicle to upload the fault log, if the target vehicle has the fault log interruption condition, generating a fault log uploading incomplete reminder, if the fault log traffic of the target vehicle is continuously requested to be applied for, based on the fault log uploading result, the fault log traffic of the target vehicle is continuously requested to be applied for through a preset breakpoint resuming mechanism, and the target vehicle is controlled to upload the fault log from a fault log uploading interruption position. Therefore, the problem of insufficient traffic when the vehicle uploads the fault log is solved, and the use experience of a user is reduced.
Need to check novelty before this filing date? Find Prior Art

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of vehicles, in particular to a network traffic application method and device, electronic equipment and storage medium. BACKGROUND

[0002] With the continuous advancement of vehicle intelligence and networking, vehicle networking technology has become an important development direction of the automotive industry. Vehicle manufacturers cooperate with operators, and operators provide stable communication networks and high-speed data transmission services to ensure that vehicles can access the Internet in real time and realize remote control, online upgrade, information entertainment and other functions. Among them, the operator will provide two different types of access points APN1 and APN2 for the vehicle manufacturer, APN1 focuses on low-cost WAP services and specific types of network applications, suitable for basic vehicle control interaction, and APN2 focuses on providing more extensive Internet access capabilities, such as entertainment, games, etc., which consumes entertainment traffic, so it is necessary to effectively upload large files and conduct investigation.

[0003] In related technologies, mainly through offline copying of logs, or using a small amount of basic traffic to upload small files. When the log file is large, it is necessary to use a mobile hard disk to copy out the log offline, and when the log file is small, the basic traffic is consumed to report the log through the APN1 channel.

[0004] However, offline copying of logs requires users or technicians to operate on site, increasing maintenance costs and time costs, resulting in low upload efficiency and even data security risks; using a small amount of basic traffic to upload small files also cannot meet the frequent large file upload demand, and will quickly consume the APN1 traffic, affecting the normal use of other basic services, which needs to be solved urgently. SUMMARY

[0005] The present application provides a network traffic application method, device, electronic equipment and storage medium to solve the problem of insufficient traffic when uploading fault logs by vehicles, thereby reducing the user's use experience and other problems.

[0006] The first aspect of the present application provides a network traffic application method, comprising the following steps:

[0007] Receiving a fault log request instruction of a target vehicle, and sending the fault log request instruction to the target vehicle, while receiving a fault log upload result of the target vehicle;

[0008] determining whether the target vehicle meets a flow application condition, if the target vehicle meets the flow application condition, determining whether the target vehicle has a fault log interruption, if the target vehicle does not have the fault log interruption, requesting to apply for a fault log flow of the target vehicle based on the fault log upload result, and after the fault log flow is successfully applied, controlling the target vehicle to upload the fault log;

[0009] If the target vehicle has the fault log interruption, a fault log upload incomplete reminder is generated, and it is determined whether to continue to request to apply for the fault log flow of the target vehicle, if the fault log flow of the target vehicle is continued to be requested, the fault log flow of the target vehicle is continued to be requested based on the fault log upload result through a preset breakpoint resume mechanism, and the target vehicle is controlled to upload the fault log from the fault log upload interruption position.

[0010] According to an embodiment of the present application, before receiving the fault log request instruction of the target vehicle, further comprising:

[0011] Obtaining the use demand of at least one vehicle, and respectively testing each vehicle based on the use demand to obtain the log flow test information of each vehicle;

[0012] If the log flow test information meets the preset test demand, the vehicle model corresponding to all vehicles meeting the preset test demand is obtained, and the flow configuration table of the fault log is generated based on the vehicle model.

[0013] According to an embodiment of the present application, the determination of whether the target vehicle meets the flow application condition comprises:

[0014] Determining whether the vehicle model of the target vehicle is in the flow configuration table of the fault log;

[0015] If the vehicle model of the target vehicle is in the flow configuration table of the fault log, it is determined that the target vehicle meets the flow application condition.

[0016] According to an embodiment of the present application, after determining whether the target vehicle meets the flow application condition, further comprising:

[0017] If the target vehicle does not meet the flow application condition, a flow warning of the target vehicle is generated, and a report failure prompt is performed.

[0018] According to an embodiment of the present application, after controlling the target vehicle to upload the fault log, further comprising:

[0019] determining whether a new fault log request instruction of the target vehicle is received, if the new fault log request instruction is received, continuing to determine whether the target vehicle meets the flow application condition until the target vehicle uploads a new fault log.

[0020] According to the network flow application method, the fault log request instruction of the target vehicle is received, and the fault log flow of the target vehicle is requested and applied based on the fault log upload result when the target vehicle meets the flow application condition and the target vehicle does not have a fault log interruption. The fault log of the target vehicle is controlled to be uploaded. If the target vehicle has a fault log interruption, a fault log upload incomplete reminder is generated. If the fault log flow of the target vehicle is continuously requested and applied, the fault log flow of the target vehicle is continuously requested and applied based on the fault log upload result through a preset breakpoint resuming mechanism, and the target vehicle is controlled to upload the fault log from a fault log upload interruption position. Therefore, the problem of insufficient flow faced by the vehicle when uploading the fault log is solved, the use experience of the user is reduced, the fault log can be efficiently and safely uploaded to the cloud through the accurate flow management and the breakpoint resuming mechanism, and the waste of the flow of the user is avoided to ensure effective use of the flow.

[0021] The second aspect of the application provides a network flow application device, comprising:

[0022] A receiving module is configured to receive a fault log request instruction of a target vehicle, and send the fault log request instruction to the target vehicle, and receive a fault log upload result of the target vehicle.

[0023] A first control module is configured to determine whether the target vehicle meets a flow application condition. If the target vehicle meets the flow application condition, it is determined whether the target vehicle has a fault log interruption. If the target vehicle does not have the fault log interruption, the fault log flow of the target vehicle is requested and applied based on the fault log upload result, and the target vehicle is controlled to upload the fault log after the fault log flow is successfully applied.

[0024] A second control module is configured to generate a fault log upload incomplete reminder if the target vehicle has the fault log interruption, and determine whether to continuously request and apply the fault log flow of the target vehicle. If the fault log flow of the target vehicle is continuously requested and applied, the fault log flow of the target vehicle is continuously requested and applied based on the fault log upload result through a preset breakpoint resuming mechanism, and the target vehicle is controlled to upload the fault log from the fault log upload interruption position.

[0025] According to one embodiment of this application, before receiving the fault log request instruction for the target vehicle, the receiving module is further configured to:

[0026] Obtain the usage requirements of at least one vehicle, and test each vehicle based on the usage requirements to obtain the log traffic test information of each vehicle.

[0027] If the log traffic test information meets the preset test requirements, then obtain the vehicle models corresponding to all vehicles that meet the preset test requirements, and generate the traffic configuration table of the fault log based on the vehicle models.

[0028] According to one embodiment of this application, the first control module is specifically used for:

[0029] Determine whether the vehicle model of the target vehicle is in the traffic configuration table of the fault log;

[0030] If the vehicle model of the target vehicle is in the traffic configuration table of the fault log, then the target vehicle is determined to meet the traffic application conditions.

[0031] According to one embodiment of this application, after determining whether the target vehicle meets the traffic flow application conditions, the first control module is further configured to:

[0032] If the target vehicle does not meet the traffic application conditions, a traffic warning for the target vehicle will be generated, and a reporting failure message will be sent.

[0033] According to one embodiment of this application, after controlling the target vehicle to upload the fault log, the second control module is further configured to:

[0034] Determine whether a new fault log request instruction has been received from the target vehicle. If the new fault log request instruction has been received, continue to execute the step of determining whether the target vehicle meets the traffic application conditions until the target vehicle uploads a new fault log.

[0035] According to the network traffic request device of this application embodiment, a fault log request instruction and fault log upload result of a target vehicle are received. When the target vehicle meets the traffic request conditions and there is no fault log interruption, the device requests fault log traffic for the target vehicle based on the fault log upload result to control the target vehicle to upload fault logs. If the target vehicle experiences a fault log interruption, a fault log upload incomplete reminder is generated. If the device continues to request fault log traffic, a preset breakpoint resume mechanism is used to continue requesting fault log traffic based on the fault log upload result, and the device resumes controlling the target vehicle to upload fault logs from the point of interruption. This solves the problem of insufficient traffic when vehicles upload fault logs, which reduces user experience. Through precise traffic management and a breakpoint resume mechanism, it ensures that fault logs can be uploaded to the cloud efficiently and securely, while avoiding the waste of user traffic and ensuring effective traffic utilization.

[0036] A third aspect of this application provides an electronic device, including: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the program to implement the network traffic application method as described in the above embodiments.

[0037] A fourth aspect of this application provides a computer-readable storage medium storing computer instructions for causing the computer to perform the network traffic request method as described in the above embodiments.

[0038] A fifth aspect of this application provides a computer program product, including a computer program that is executed to implement the network traffic application method described in the above embodiments.

[0039] Additional aspects and advantages of this application will be set forth in part in the description which follows, and in part will be obvious from the description, or may be learned by practice of this application. Attached Figure Description

[0040] The above and / or additional aspects and advantages of this application will become apparent and readily understood from the following description of the embodiments taken in conjunction with the accompanying drawings, wherein:

[0041] Figure 1 This is a flowchart illustrating a method for requesting network traffic according to an embodiment of this application;

[0042] Figure 2 This is an overall flowchart of a network traffic request according to one embodiment of this application;

[0043] Figure 3This is an example diagram of a network traffic application device according to an embodiment of this application;

[0044] Figure 4 This is a schematic diagram of the structure of an electronic device according to an embodiment of this application. Detailed Implementation

[0045] The embodiments of this application are described in detail below. Examples of the embodiments are shown in the accompanying drawings, wherein the same or similar reference numerals denote the same or similar elements or elements having the same or similar functions throughout. The embodiments described below with reference to the accompanying drawings are exemplary and intended to explain this application, and should not be construed as limiting this application.

[0046] The following description, with reference to the accompanying drawings, details a method, apparatus, electronic device, and storage medium for requesting network traffic according to embodiments of this application. Addressing the problem mentioned in the background art of insufficient traffic when vehicles upload fault logs, thus reducing user experience, this application provides a method for requesting network traffic. In this method, a fault log request instruction and fault log upload result from a target vehicle are received. If the target vehicle meets the traffic request conditions and there is no interruption in the fault log upload process, a request for fault log traffic is made based on the fault log upload result to control the target vehicle's fault log upload. If the target vehicle experiences a fault log upload interruption, a fault log upload incomplete reminder is generated. If the request for fault log traffic continues, a preset breakpoint resume mechanism is used to continue requesting fault log traffic based on the fault log upload result, and the upload of fault logs is resumed from the point of interruption. This solves the problem of insufficient traffic when vehicles upload fault logs, thus reducing user experience. Through precise traffic management and a breakpoint resume mechanism, it ensures that fault logs can be uploaded to the cloud efficiently and securely, while avoiding wasted user traffic and ensuring effective traffic utilization.

[0047] Specifically, Figure 1 This is a flowchart illustrating a method for requesting network traffic provided in an embodiment of this application.

[0048] like Figure 1 As shown, the method for requesting network traffic includes the following steps:

[0049] In step S101, a fault log request instruction from the target vehicle is received and sent to the target vehicle, while the fault log upload result from the target vehicle is received.

[0050] According to one embodiment of this application, before receiving the fault log request instruction of the target vehicle, the method further includes: obtaining the usage requirements of at least one vehicle, and testing each vehicle based on the usage requirements to obtain log traffic test information for each vehicle; if the log traffic test information meets the preset test requirements, obtaining the vehicle models corresponding to all vehicles that meet the preset test requirements, and generating a traffic configuration table for the fault log based on the vehicle models.

[0051] The preset test requirements are set by those skilled in the art based on the actual usage needs of different vehicle models, and are not specifically limited here.

[0052] Specifically, to address the issue of effectively uploading large fault logs generated by vehicles to the cloud, this application provides a method for requesting additional IoT card entertainment data for large file transfers under specific circumstances without consuming the user's regular entertainment data or basic data. This method mainly includes three mechanisms: a configuration mechanism, an active identification mechanism, and a vehicle-side breakpoint resume mechanism.

[0053] Specifically, to ensure efficient and secure uploading of fault logs to the cloud while avoiding wasted user bandwidth, this embodiment requires a configuration mechanism. This mechanism, implemented by those skilled in the art (i.e., operators), is based on the vehicle models that require the solution. In other words, it's first necessary to identify which vehicle models need the solution to ensure it's applied only to essential models. This process generates a traffic configuration table for fault logs based on the configured models. During this process, the usage requirements of the vehicles are analyzed to understand market demands and user feedback for different models, determining which models are most likely to require large file uploads. Then, those skilled in the art evaluate the technical architecture and vehicle networking functions of each model to determine... Which vehicle models are eligible to implement this solution? Test each eligible vehicle model to verify the feasibility and effectiveness of the configuration solution. For example, simulate fault log upload scenarios to test the smoothness of traffic application and upload processes, thereby obtaining log traffic test information for each vehicle. If the log traffic test information meets the preset test requirements, such as smooth traffic application and upload processes, obtain the vehicle models corresponding to all vehicles that meet the preset test requirements. Generate a fault log traffic configuration table based on the vehicle model. This configuration table mainly enables business customization. Vehicle models that need to implement this solution can be configured in this traffic configuration table, which is stored by the cloud platform for subsequent business logic judgment.

[0054] It should be noted that only authorized operators can modify the traffic configuration table on the cloud platform to ensure its security and accuracy. Furthermore, with the introduction of new vehicle models, operators can add them to the traffic configuration table at any time. Each time the traffic configuration table is modified, the system automatically records the version number and modification time for easy tracking of historical versions. Each modification to the traffic configuration table must be reviewed before it takes effect to prevent accidental operations or improper configurations. If a configuration problem is found, it can be quickly rolled back to a previous version, thus ensuring system stability.

[0055] Furthermore, during vehicle use, when a user requests after-sales vehicle inspection, the operator can request the vehicle to report fault logs on the cloud platform. That is, the cloud platform receives the fault log request instruction from the target vehicle and sends the fault log request instruction to the target vehicle. When the target vehicle receives the fault log request instruction, it will generate a log size and upload the log size to the cloud platform.

[0056] In step S102, it is determined whether the target vehicle meets the traffic application conditions. If the target vehicle meets the traffic application conditions, it is determined whether the target vehicle has a fault log interruption. If the target vehicle does not have a fault log interruption, it requests the fault log traffic of the target vehicle based on the fault log upload result, and controls the target vehicle to upload fault logs after the fault log traffic application is successful.

[0057] According to one embodiment of this application, determining whether a target vehicle meets the traffic application conditions includes: determining whether the vehicle model of the target vehicle is in the traffic configuration table of the fault log; if the vehicle model of the target vehicle is in the traffic configuration table of the fault log, then the target vehicle is determined to meet the traffic application conditions.

[0058] Specifically, such as Figure 2As shown, when the cloud platform receives a fault log request instruction from a target vehicle, it first determines whether the target vehicle meets the traffic application conditions, specifically whether the vehicle model is in the fault log traffic configuration table. If the vehicle model is in the fault log traffic configuration table, the target vehicle is deemed to meet the traffic application conditions. Secondly, after the target vehicle meets the traffic application conditions, to ensure the complete upload of the fault log, it further determines whether there is any fault log interruption. If there is no fault log interruption, the cloud platform, after receiving the size of the fault log reported by the vehicle, requests additional entertainment traffic corresponding to the fault log size from the network operator. After the network operator adds the corresponding entertainment traffic, it notifies the cloud platform of successful addition, and then the cloud platform notifies the vehicle to report the fault log. In this case, the vehicle reports based on additional entertainment traffic, thus not consuming the user's regular entertainment traffic or basic traffic, and also preventing users from abusing entertainment traffic.

[0059] According to one embodiment of this application, after determining whether the target vehicle meets the traffic application conditions, the method further includes: if the target vehicle does not meet the traffic application conditions, generating a traffic warning for the target vehicle and issuing a reporting failure prompt.

[0060] Specifically, such as Figure 2 As shown, if the cloud platform detects that the target vehicle does not meet the traffic application conditions, that is, the vehicle model of the target vehicle is not in the traffic configuration table of the fault log, a traffic warning for the target vehicle will be generated. At this time, the cloud platform will prompt that the traffic is insufficient and the fault log cannot be reported, and will issue a reporting failure prompt, thereby ending the reporting of this fault log.

[0061] In step S103, if the target vehicle has an interrupted fault log, a fault log upload incomplete reminder is generated, and it is determined whether to continue requesting the fault log traffic of the target vehicle. If the request continues, the fault log traffic of the target vehicle is continued to be requested based on the fault log upload result through a preset breakpoint resume mechanism, and the target vehicle is controlled to continue uploading fault logs from the point where the fault log upload was interrupted.

[0062] According to one embodiment of this application, after controlling the target vehicle to upload fault logs, the method further includes: determining whether a new fault log request instruction from the target vehicle has been received; if a new fault log request instruction has been received, then continuing to execute the step of determining whether the target vehicle meets the traffic application conditions, until the target vehicle uploads a new fault log.

[0063] The preset breakpoint resume mechanism can be selected by those skilled in the art according to actual testing needs, and no specific limitations are made here.

[0064] Specifically, such as Figure 2 As shown, after the target vehicle meets the data usage request conditions, if it is further determined that the target vehicle has a fault log interruption, such as the user turning off the engine midway, power failure, network problem, etc., thus causing the fault log to stop reporting, a fault log upload incomplete reminder is generated. After the user restarts the vehicle, it is determined whether to continue requesting the target vehicle's fault log data usage. If the request continues, this application can continue to request the target vehicle's fault log data usage based on the preset breakpoint resume mechanism, and control the target vehicle to continue uploading fault logs from the point where the fault log upload was interrupted, thereby ensuring complete log upload and avoiding waste of entertainment data usage, ensuring that the entertainment data usage requested each time is fully utilized.

[0065] Furthermore, after a vehicle completes the reporting of this fault log, the cloud platform can view and download the reported fault log. At the same time, if a vehicle fails to complete the reporting of this fault log, the cloud platform can also view the reporting record of this fault log and mark the reporting status as incomplete, so as to notify the operations personnel.

[0066] Furthermore, after the vehicle has been running for a period of time, a fault may be detected again. At this time, it will re-evaluate whether a new fault log request instruction has been received from the target vehicle. If a new fault log request instruction has been received, the step of determining whether the target vehicle meets the conditions for data traffic application will continue, that is, the above fault log application process will be repeated. At this time, click to report the fault log. The cloud platform will continue to determine whether there are any fault logs that were not reported in the previous time. If there are no fault logs that were not reported in the previous time, the front-end page of the cloud platform will display a prompt and apply for entertainment data traffic according to the process. If there are fault logs that were not reported in the previous time, it will continue to determine whether to apply for entertainment data traffic again. If to apply for entertainment data traffic again, the cloud platform will apply for entertainment data traffic from the network operator for this new fault log report. Otherwise, the log report will end.

[0067] Therefore, the embodiments of this application solve the problem of insufficient entertainment traffic faced by intelligent connected vehicles when uploading large files (such as fault logs). Through precise traffic management and breakpoint resume mechanism, it ensures that fault logs can be uploaded to the cloud platform efficiently and securely, while avoiding the waste of user traffic. This not only improves the user experience, but also provides new possibilities for cooperation between car manufacturers and operators.

[0068] According to the network traffic request method of this application embodiment, a fault log request instruction and fault log upload result of a target vehicle are received. If the target vehicle meets the traffic request conditions and there is no fault log interruption, a request for fault log traffic for the target vehicle is made based on the fault log upload result to control the target vehicle to upload fault logs. If the target vehicle experiences a fault log interruption, a fault log upload incomplete reminder is generated. If the request for fault log traffic continues, a preset breakpoint resume mechanism is used to continue requesting fault log traffic based on the fault log upload result, and the target vehicle resumes uploading fault logs from the point of interruption. This solves the problem of insufficient traffic when vehicles upload fault logs, which reduces user experience. Through precise traffic management and a breakpoint resume mechanism, fault logs are ensured to be uploaded to the cloud efficiently and securely, while avoiding wasted user traffic and ensuring effective traffic utilization.

[0069] Next, the network traffic application apparatus according to an embodiment of this application is described with reference to the accompanying drawings.

[0070] Figure 3 This is a block diagram of a network traffic application device according to an embodiment of this application.

[0071] like Figure 3 As shown, the network traffic request device 10 includes: a receiving module 100, a first control module 200, and a second control module 300.

[0072] The receiving module 100 is used to receive the fault log request instruction from the target vehicle, send the fault log request instruction to the target vehicle, and receive the fault log upload result from the target vehicle.

[0073] The first control module 200 is used to determine whether the target vehicle meets the traffic application conditions. If the target vehicle meets the traffic application conditions, it determines whether the target vehicle has a fault log interruption. If the target vehicle does not have a fault log interruption, it requests the fault log traffic of the target vehicle based on the fault log upload result, and controls the target vehicle to upload fault logs after the fault log traffic application is successful.

[0074] The second control module 300 is used to generate a fault log upload incomplete reminder if the target vehicle has a fault log interruption, and to determine whether to continue requesting the fault log traffic of the target vehicle. If it continues to request the fault log traffic of the target vehicle, it continues to request the fault log traffic of the target vehicle based on the fault log upload result through a preset breakpoint resume mechanism, and continues to control the target vehicle to upload fault logs from the point where the fault log upload was interrupted.

[0075] According to one embodiment of this application, before receiving the fault log request instruction for the target vehicle, the receiving module 100 is further configured to:

[0076] Obtain the usage requirements of at least one vehicle, and test each vehicle based on the usage requirements to obtain the log traffic test information for each vehicle.

[0077] If the log traffic test information meets the preset test requirements, then obtain the vehicle models corresponding to all vehicles that meet the preset test requirements, and generate a traffic configuration table for the fault logs based on the vehicle models.

[0078] According to one embodiment of this application, the first control module 200 is specifically used for:

[0079] Determine whether the target vehicle's model is in the traffic configuration table of the fault log;

[0080] If the vehicle model of the target vehicle is in the traffic configuration table of the fault log, then the target vehicle is determined to meet the traffic application conditions.

[0081] According to one embodiment of this application, after determining whether the target vehicle meets the traffic flow application conditions, the first control module 200 is further configured to:

[0082] If the target vehicle does not meet the traffic application requirements, a traffic warning will be generated for the target vehicle, and a reporting failure message will be sent.

[0083] According to one embodiment of this application, after controlling the target vehicle to upload the fault log, the second control module 300 is further configured to:

[0084] Determine whether a new fault log request instruction has been received from the target vehicle. If a new fault log request instruction has been received, continue to execute the step of determining whether the target vehicle meets the traffic application conditions until the target vehicle uploads a new fault log.

[0085] According to the network traffic request device of this application embodiment, a fault log request instruction and fault log upload result of a target vehicle are received. When the target vehicle meets the traffic request conditions and there is no fault log interruption, the device requests fault log traffic for the target vehicle based on the fault log upload result to control the target vehicle to upload fault logs. If the target vehicle experiences a fault log interruption, a fault log upload incomplete reminder is generated. If the device continues to request fault log traffic, a preset breakpoint resume mechanism is used to continue requesting fault log traffic based on the fault log upload result, and the device resumes controlling the target vehicle to upload fault logs from the point of interruption. This solves the problem of insufficient traffic when vehicles upload fault logs, which reduces user experience. Through precise traffic management and a breakpoint resume mechanism, it ensures that fault logs can be uploaded to the cloud efficiently and securely, while avoiding the waste of user traffic and ensuring effective traffic utilization.

[0086] Figure 4 A schematic diagram of the structure of an electronic device provided in an embodiment of this application. The electronic device may include:

[0087] The memory 401, the processor 402, and the computer program stored on the memory 401 and capable of running on the processor 402.

[0088] When the processor 402 executes the program, it implements the network traffic request method provided in the above embodiments.

[0089] Furthermore, electronic devices also include:

[0090] Communication interface 403 is used for communication between memory 401 and processor 402.

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

[0092] The memory 401 may include high-speed RAM memory, and may also include non-volatile memory, such as at least one disk storage device.

[0093] If the memory 401, processor 402, and communication interface 403 are implemented independently, then the communication interface 403, memory 401, and processor 402 can be interconnected via a bus to complete communication between them. The bus can be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus, etc. Buses can be categorized into address buses, data buses, control buses, etc. For ease of representation, Figure 4 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 401, processor 402, and communication interface 403 are integrated on a single chip, then the memory 401, processor 402, and communication interface 403 can communicate with each other through an internal interface.

[0095] Processor 402 may be a central processing unit (CPU), an application specific integrated circuit (ASIC), or one or more integrated circuits configured to implement the embodiments of this application.

[0096] This embodiment also provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the above-described method for requesting network traffic.

[0097] This embodiment also provides a computer program product, including a computer program that is executed to implement the network traffic request method of the above embodiment.

[0098] In the description of this specification, the references to terms such as "one embodiment," "some embodiments," "example," "specific example," or "some examples," etc., indicate that a specific feature, structure, material, or characteristic described in connection with that embodiment or example is 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] 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, "N" means at least two, such as two, three, etc., unless otherwise explicitly specified.

[0100] Any process or method described in the flowchart or otherwise herein can be understood as representing a module, segment, or portion of code comprising one or more N executable instructions for implementing custom logic functions or processes, and the scope of the preferred embodiments of this application includes additional implementations in which functions may be performed not in the order shown or discussed, including substantially simultaneously or in reverse order depending on the functions involved, as should be understood by those skilled in the art to which embodiments of this application pertain.

[0101] The logic and / or steps represented in the flowchart or otherwise described herein, for example, can be considered as a sequenced list of executable instructions for implementing logical functions, and can be embodied in any computer-readable medium for use by, or in conjunction with, an instruction execution system, apparatus, or device (such as a computer-based system, a processor-included system, or other system that can fetch and execute instructions from, an instruction execution system, apparatus, or device). For the purposes of this specification, "computer-readable medium" can be any means that can contain, store, communicate, propagate, or transmit programs for use by, or in conjunction with, an instruction execution system, apparatus, or device. More specific examples (a non-exhaustive list) of computer-readable media include: an electrical connection having one or more wires (electronic device), a portable computer disk drive (magnetic device), random access memory (RAM), read-only memory (ROM), erasable and editable read-only memory (EPROM or flash memory), fiber optic devices, and portable optical disc read-only memory (CDROM). Furthermore, computer-readable media can even be paper or other suitable media on which programs can be printed, because programs can be obtained electronically, for example, by optically scanning the paper or other media, followed by editing, interpreting, or otherwise processing as necessary, and then stored in computer memory.

[0102] It should be understood that the various parts of this application can be implemented using hardware, software, firmware, or a combination thereof. In the above embodiments, the N steps or methods can be implemented using software or firmware stored in memory and executed by a suitable instruction execution system. For example, if implemented in hardware as in another embodiment, it can be implemented using any one or a combination of the following techniques known in the art: discrete logic circuits having logic gates for implementing logical functions on data signals, application-specific integrated circuits (ASICs) having suitable combinational logic gates, programmable gate arrays (PGAs), field-programmable gate arrays (FPGAs), etc.

[0103] Those skilled in the art will understand that all or part of the steps of the methods described in the above embodiments can be implemented by a program instructing related hardware, and the program can be stored in a computer-readable storage medium. When executed, the program includes one or a combination of the steps of the method embodiments.

[0104] Furthermore, the functional units in the various embodiments of this application can be integrated into a processing module, or each unit can exist physically separately, or two or more units can be integrated into a module. The integrated module can be implemented in hardware or as a software functional module. If the integrated module is implemented as a software functional module and sold or used as an independent product, it can also be stored in a computer-readable storage medium.

[0105] The storage medium mentioned above can be a read-only memory, a disk, or an optical disk, etc. 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 requesting network traffic, characterized in that, Includes the following steps: Receive a fault log request instruction from the target vehicle and send the fault log request instruction to the target vehicle, while simultaneously receiving the fault log upload result from the target vehicle; Determine whether the target vehicle meets the traffic application conditions. If the target vehicle meets the traffic application conditions, determine whether the target vehicle has a fault log interruption. If the target vehicle does not have a fault log interruption, request the fault log traffic of the target vehicle based on the fault log upload result, and control the target vehicle to upload the fault log after the fault log traffic application is successful. If the target vehicle experiences a fault log interruption, a fault log upload incomplete reminder is generated. It is then determined whether to continue requesting fault log traffic for the target vehicle. If the request continues, a preset breakpoint resume mechanism is used to continue requesting fault log traffic for the target vehicle based on the fault log upload result, and the target vehicle resumes uploading the fault log from the point where the fault log upload was interrupted.

2. The method according to claim 1, characterized in that, Before receiving the fault log request instruction from the target vehicle, the following is also included: Obtain the usage requirements of at least one vehicle, and test each vehicle based on the usage requirements to obtain the log traffic test information of each vehicle. If the log traffic test information meets the preset test requirements, then obtain the vehicle models corresponding to all vehicles that meet the preset test requirements, and generate the traffic configuration table of the fault log based on the vehicle models.

3. The method according to claim 1, characterized in that, The step of determining whether the target vehicle meets the traffic application conditions includes: Determine whether the vehicle model of the target vehicle is in the traffic configuration table of the fault log; If the vehicle model of the target vehicle is in the traffic configuration table of the fault log, then the target vehicle is determined to meet the traffic application conditions.

4. The method according to claim 1, characterized in that, After determining whether the target vehicle meets the traffic application requirements, the process also includes: If the target vehicle does not meet the traffic application conditions, a traffic warning for the target vehicle will be generated, and a reporting failure message will be sent.

5. The method according to claim 1, characterized in that, After controlling the target vehicle to upload the fault log, the process also includes: Determine whether a new fault log request instruction has been received from the target vehicle. If the new fault log request instruction has been received, continue to execute the step of determining whether the target vehicle meets the traffic application conditions until the target vehicle uploads a new fault log.

6. A device for requesting network traffic, characterized in that, include: The receiving module is used to receive the fault log request instruction from the target vehicle, send the fault log request instruction to the target vehicle, and receive the fault log upload result from the target vehicle. The first control module is used to determine whether the target vehicle meets the traffic application conditions. If the target vehicle meets the traffic application conditions, it determines whether the target vehicle has a fault log interruption. If the target vehicle does not have a fault log interruption, it requests the fault log traffic of the target vehicle based on the fault log upload result, and controls the target vehicle to upload the fault log after the fault log traffic application is successful. The second control module is used to generate a fault log upload incomplete reminder if the target vehicle has a fault log interruption, and to determine whether to continue requesting the fault log traffic of the target vehicle. If it continues to request the fault log traffic of the target vehicle, it continues to request the fault log traffic of the target vehicle based on the fault log upload result through a preset breakpoint resume mechanism, and continues to control the target vehicle to upload the fault log from the point where the fault log upload was interrupted.

7. The apparatus according to claim 6, characterized in that, Before receiving the fault log request instruction from the target vehicle, the receiving module is further configured to: Obtain the usage requirements of at least one vehicle, and test each vehicle based on the usage requirements to obtain the log traffic test information of each vehicle. If the log traffic test information meets the preset test requirements, then obtain the vehicle models corresponding to all vehicles that meet the preset test requirements, and generate the traffic configuration table of the fault log based on the vehicle models.

8. The apparatus according to claim 6, characterized in that, The first control module is specifically used for: Determine whether the vehicle model of the target vehicle is in the traffic configuration table of the fault log; If the vehicle model of the target vehicle is in the traffic configuration table of the fault log, then the target vehicle is determined to meet the traffic application conditions.

9. An electronic device, characterized in that, include: A memory, a processor, and a computer program stored in the memory and executable on the processor, the processor executing the program to implement the network traffic request method as described in any one of claims 1-5.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that, The program is executed by the processor to implement the network traffic request method as described in any one of claims 1-5.

Citation Information

Patent Citations

  • System, method, MNO application terminal and automobile for controlling of Internet of Vehicles traffic by virtual operator

    CN112087727A

  • Vehicle-mounted network intelligent monitoring system based on cloud computing

    CN118400299A