Internet of vehicles function diagnosis method, apparatus and device, and readable storage medium
Through the Internet of Vehicles function diagnosis method, network diagnostic instructions are obtained and distributed to generate initial diagnostic results, solving the problem that traditional detection cannot verify Internet of Vehicles service, realizing unsensed Internet of Vehicles function diagnosis, improving the comprehensiveness of user experience and diagnosis and convenience.
Patent Information
- Application Number
- CN202411053505.4
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-08-02
- Publication Date
- 2024-12-06
AI Technical Summary
Traditional vehicle production line offline inspection cannot verify the complete business of the basic services of the Internet of Vehicles, affecting the normal use of the Internet of Vehicles functions.
It provides a method for diagnostics of the Internet of Vehicles function, which can obtain network diagnostic instructions, distribute and receive response data to the on-board controller, generate initial diagnostic results, and feed the results back to the cloud to achieve complete business process verification of the Internet of Vehicles function. This method does not require user access, and the user has no perception, and can diagnose different target vehicle cloud protocols, improving the comprehensiveness and convenience of the diagnosis.
It realizes complete business process verification of the Internet of Vehicles functions, ensures vehicle usage experience without user access, avoids interference with the vehicle usage process, and improves the comprehensiveness and convenience of diagnosis.
Smart Images

Figure CN119094520A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the technical field of Internet of Things, and in particular to a method, device, equipment and readable storage medium for diagnosing vehicle networking functions. Background Art
[0002] With the development of intelligent vehicles, Internet of Vehicles services, as an indispensable part of smart cars, have also become popular. With Internet of Vehicles services, users can control their vehicles by operating their own terminal devices, such as controlling the opening and closing of air conditioners, windows or doors, or controlling the driving of the vehicle, which improves the convenience of users controlling the vehicle.
[0003] However, the traditional vehicle production line offline inspection process only verifies the basic functions of the vehicle, including the verification of vehicle hardware equipment and software functions, etc., and is unable to verify the complete business of the basic services of the Internet of Vehicles, affecting the normal use of the Internet of Vehicles functions. Summary of the invention
[0004] Based on this, it is necessary to provide a vehicle networking function diagnosis method, device, equipment and readable storage medium with imperceptible diagnosis process and better comprehensiveness and convenience to address the above technical problems.
[0005] In a first aspect, the present application provides a method for diagnosing vehicle networking functions, which is applied to a T-BOX (Telematics BOX, telematics processor) of a target vehicle, comprising:
[0006] Acquire at least one network diagnostic instruction; the at least one network diagnostic instruction is generated by the cloud based on the corresponding encapsulation of at least one target vehicle-cloud protocol supported by the T-BOX;
[0007] Distributing corresponding network diagnostic instructions to the vehicle controllers corresponding to the network diagnostic instructions, and receiving instruction response data fed back by the corresponding vehicle controllers;
[0008] An initial diagnosis result of the target vehicle is generated according to each of the command response data, and the initial diagnosis result is fed back to the cloud to generate a target diagnosis result.
[0009] In one of the embodiments, before obtaining at least one network diagnostic instruction, the method further includes: obtaining a protocol acquisition instruction sent by the cloud; and in response to the protocol acquisition instruction, feeding back to the cloud at least one target vehicle-cloud protocol supported by the T-BOX.
[0010] In one of the embodiments, in response to the protocol acquisition instruction, feeding back to the cloud at least one target vehicle-cloud protocol supported by the T-BOX includes: selecting at least one target vehicle-cloud protocol from at least one candidate vehicle-cloud protocol supported by the T-BOX according to the instruction type in the protocol acquisition instruction; and feeding back the at least one target vehicle-cloud protocol to the cloud.
[0011] In one embodiment, the initial diagnostic result of the target vehicle is generated based on each of the command response data, including: generating a first initial diagnostic result for the command response data that is the same as the default response data; the first initial diagnostic result is used to indicate network connectivity between the cloud and the vehicle-mounted controller corresponding to the command response data; generating a second initial diagnostic result for the command response data that is different from the default response data; the second initial diagnostic result is used to indicate network disruption between the cloud and the vehicle-mounted controller corresponding to the command response data.
[0012] In a second aspect, the present application also provides a method for diagnosing Internet of Vehicles functions, which is applied in the cloud, and includes:
[0013] Based on at least one target vehicle-cloud protocol supported by the T-BOX of the target vehicle, command encapsulation is performed respectively to generate network diagnostic commands corresponding to each target vehicle-cloud protocol;
[0014] Distributing each of the network diagnostic instructions to the vehicle controller under the corresponding network diagnostic instruction through the T-BOX;
[0015] Acquire the initial diagnosis result of the target vehicle fed back by the T-BOX; wherein the initial diagnosis result is generated by the T-BOX according to the command response data fed back by each of the vehicle-mounted controllers;
[0016] A target diagnosis result is generated according to the initial diagnosis result.
[0017] In one of the embodiments, before respectively encapsulating instructions for at least one target vehicle-cloud protocol supported by the T-BOX of the target vehicle and generating network diagnostic instructions corresponding to each of the target vehicle-cloud protocols, the method further includes: sending a protocol acquisition instruction to the T-BOX of the target vehicle; and receiving at least one target vehicle-cloud protocol supported by itself fed back by the T-BOX.
[0018] In a third aspect, the present application also provides a method for diagnosing vehicle networking functions, which is applied to a vehicle controller, comprising:
[0019] Obtain at least one network diagnostic instruction sent by the T-BOX of the target vehicle; wherein the at least one network diagnostic instruction is encapsulated and generated by the cloud based on at least one target vehicle cloud protocol supported by the T-BOX;
[0020] The command response data corresponding to each of the network diagnostic commands is fed back to the T-BOX, so that the T-BOX generates and feeds back the initial diagnostic result of the target vehicle to the cloud according to each of the command response data, so as to generate a final diagnostic result.
[0021] In one of the embodiments, the feeding back to the T-BOX the instruction response data corresponding to each of the network diagnostic instructions includes: for each network diagnostic instruction, in response to the network diagnostic instruction, feeding back default response data as the instruction response data to the T-BOX.
[0022] In a fourth aspect, the present application also provides a vehicle networking function diagnostic device, which is configured on a telematics processor T-BOX of a target vehicle, comprising:
[0023] A first acquisition module is used to acquire at least one network diagnostic instruction; the at least one network diagnostic instruction is generated by the cloud based on the corresponding encapsulation of at least one target vehicle-cloud protocol supported by the T-BOX;
[0024] A first distribution module, used to distribute the corresponding network diagnostic instructions to the vehicle controllers corresponding to the network diagnostic instructions, and receive instruction response data fed back by the corresponding vehicle controllers;
[0025] The first generating module is used to generate an initial diagnosis result of the target vehicle according to each of the command response data, and feed the initial diagnosis result back to the cloud to generate a target diagnosis result.
[0026] In a fifth aspect, the present application also provides a vehicle networking function diagnosis device, which is configured in the cloud and includes:
[0027] A packaging module, used to encapsulate instructions based on at least one target vehicle-cloud protocol supported by the T-BOX of the target vehicle, and generate network diagnostic instructions corresponding to each target vehicle-cloud protocol;
[0028] A second distribution module, used to distribute each of the network diagnostic instructions to the vehicle controller under the corresponding network diagnostic instruction through the T-BOX;
[0029] A second acquisition module is used to acquire the initial diagnosis result of the target vehicle fed back by the T-BOX; wherein the initial diagnosis result is generated by the T-BOX according to the command response data fed back by each of the vehicle-mounted controllers;
[0030] The second generating module is used to generate a target diagnosis result according to the initial diagnosis result.
[0031] In a sixth aspect, the present application further provides a vehicle networking function diagnostic device, which is configured on a vehicle controller and includes:
[0032] A third acquisition module is used to acquire at least one network diagnostic instruction sent by the T-BOX of the target vehicle; wherein the at least one network diagnostic instruction is respectively encapsulated and generated by the cloud based on at least one target vehicle cloud protocol supported by the T-BOX;
[0033] The feedback module is used to feed back the command response data corresponding to each of the network diagnostic commands to the T-BOX, so that the T-BOX generates and feeds back the initial diagnostic result of the target vehicle to the cloud according to each of the command response data, so as to generate a target diagnostic result.
[0034] In the seventh aspect, the present application also provides a computer device, including a memory and a processor, wherein the memory stores a computer program, and when the processor executes the computer program, it implements the steps of the vehicle networking function diagnosis method provided in the above-mentioned first aspect, second aspect or third aspect embodiments.
[0035] In an eighth aspect, the present application further provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the steps of the vehicle networking function diagnosis method provided in the above-mentioned first, second or third aspect embodiments.
[0036] The above-mentioned vehicle networking function diagnosis method, device, equipment and readable storage medium are encapsulated by the cloud based on at least one target vehicle cloud protocol supported by T-BOX to generate at least one network diagnostic instruction; the T-BOX of the target vehicle distributes the instruction to the vehicle controller corresponding to each network diagnostic instruction; the vehicle controller responds to the received network diagnostic instruction and feeds back the instruction response data to T-BOX; T-BOX generates the initial diagnostic result of the target vehicle according to each instruction response data, and feeds back the result to the cloud; the cloud generates the target diagnostic result based on the initial diagnostic result. The above-mentioned technical solution can realize the complete business process verification of the vehicle networking function, and the entire diagnostic process does not require user access, and will not interfere with the user's vehicle use process. The user is not aware of the whole process, which improves the user's vehicle use experience. In addition, when generating network diagnostic instructions, network diagnostic instructions can be encapsulated and generated for different target vehicle cloud protocols supported by T-BOX, so that the vehicle networking function diagnosis under different target vehicle cloud protocols and the diagnosis of the entire network communication link can be performed in one diagnostic process, which improves the comprehensiveness and convenience of vehicle networking function diagnosis. BRIEF DESCRIPTION OF THE DRAWINGS
[0037] In order to more clearly illustrate the technical solutions in the embodiments of the present application or related technologies, the drawings required for use in the embodiments of the present application or related technical descriptions will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other related drawings can be obtained based on these drawings without paying creative work.
[0038] Figure 1 This is a diagram of an application environment of a method for diagnosing a function of an Internet of Vehicles in one embodiment;
[0039] Figure 2 A schematic diagram of a process flow of a method for diagnosing a function of an Internet of Vehicles in one embodiment;
[0040] Figure 3 A flowchart of a feedback step of a target vehicle-cloud protocol in one embodiment;
[0041] Figure 4 A schematic diagram of a flow chart of a method for diagnosing vehicle networking functions in another embodiment;
[0042] Figure 5 A schematic diagram of a flow chart of a method for diagnosing vehicle networking functions in another embodiment;
[0043] Fig. 6A A network architecture diagram in one embodiment;
[0044] FIG6B is a schematic diagram of a flow chart of a method for diagnosing vehicle networking functions in another embodiment;
[0045] Figure 7 is a structural block diagram of a vehicle networking function diagnosis device in one embodiment;
[0046] Figure 8 It is a structural block diagram of a vehicle networking function diagnosis device in another embodiment;
[0047] Fig. 9 is a structural block diagram of a vehicle networking function diagnosis device in another embodiment;
[0048] Fig.10 FIG. 4 is a diagram showing the internal structure of a computer device in one embodiment. DETAILED DESCRIPTION
[0049] In order to make the purpose, technical solution and advantages of the present application more clearly understood, the present application is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.
[0050] The vehicle networking function diagnosis method provided in the embodiment of the present application can be applied to Figure 1In the application environment shown in FIG. 1 , the cloud 110 is used to encapsulate instructions based on at least one target vehicle-to-cloud protocol supported by the T-BOX 120 to generate corresponding network diagnostic instructions; the T-BOX 120 is used to distribute corresponding network diagnostic instructions to each vehicle-mounted controller 130; each vehicle-mounted controller 130 generates its own instruction response data corresponding to the network diagnostic instruction and feeds it back to the T-BOX 120; the T-BOX 120 generates the initial diagnostic result of the target vehicle according to each instruction response data, and feeds the initial diagnostic result back to the cloud 110.
[0051] In order to ensure the high availability of the cloud 110, two sets of primary and backup devices can be set up in the cloud. The functions of the primary and backup devices are exactly the same. Normally, the primary device is used to provide services. When the cloud service fails to provide services due to uncontrollable reasons such as network fluctuations, the backup device is controlled to replace the primary device to provide services. Optionally, during the primary-backup switching process, the DNS (Domain Name System) can switch the devices according to the domain names of the primary and backup devices to ensure that the entire Internet of Vehicles system is not aware of it and to ensure the normal use of the Internet of Vehicles functions and network diagnosis of the target vehicle.
[0052] Optionally, a WEB management background 111, a protocol adapter 112 and a terminal gateway 113 may be provided in the cloud 110. The WEB management background 111 may be used to detect whether there is a need for diagnosing the Internet of Vehicles function for the target vehicle. When there is a need for diagnosing the Internet of Vehicles function, the protocol adapter 112 may be used to encapsulate instructions for each target vehicle-cloud protocol based on the target vehicle-cloud protocol to generate corresponding network diagnostic instructions. The terminal gateway 113 may be used to realize data transmission between the vehicle end 110 and the T-BOX 120.
[0053] In an exemplary embodiment, Figure 2 As shown, a method for diagnosing vehicle networking functions is provided, which is applied to Figure 1 The T-BOX 120 in FIG. 1 includes the following steps:
[0054] S210, obtaining at least one network diagnostic instruction; the at least one network diagnostic instruction is generated by the cloud based on the corresponding encapsulation of at least one target vehicle-cloud protocol supported by T-BOX.
[0055] The vehicle-to-cloud protocol can be understood as the communication protocol supported by the on-board controller of the target vehicle when communicating with the cloud through T-BOX. The vehicle-to-cloud protocol can include at least one of MQTT (Message Queuing Telemetry Transport), HTTP (Hypertext Transfer Protocol), WEBSOCKET (a full-duplex communication protocol), etc., and this application does not impose any limitation on this.
[0056] The target vehicle-to-cloud protocol can be understood as the vehicle-to-cloud protocol supported by the target vehicle, that is, the vehicle to be diagnosed, and the corresponding T-BOX. The number of target vehicle-to-cloud protocols can be at least one, and this application does not impose any limitation on this.
[0057] The cloud can respond to the diagnostic operation sent by the diagnostic instrument or user terminal, and encapsulate and generate corresponding network diagnostic instructions based on the target vehicle cloud protocols supported by the T-BOX corresponding to the target vehicle specified by the diagnostic operation; the cloud sends the network diagnostic instructions generated by itself to the T-BOX of the target vehicle. Among them, different network diagnostic instructions use different target vehicle cloud protocols; the vehicle controllers corresponding to different network diagnostic instructions can be the same or different, and this application does not make any restrictions on this.
[0058] It is worth noting that network diagnostic instructions can be understood as instructions specifically used for diagnosing vehicle networking functions, rather than business instructions that require the target vehicle to perform certain business processing.
[0059] S220, distributing the corresponding network diagnostic command to the vehicle controller corresponding to each network diagnostic command, and receiving the command response data fed back by the corresponding vehicle controller.
[0060] Among them, the on-board controller in the target vehicle may include at least one of a BCM (Body Control Module) controller, a CDC (Continuous Damping Control) controller and a GW (Gateway Controller) controller, and the present application does not impose any limitation on this.
[0061] Optionally, if the Internet of Vehicles function diagnosis is only for a certain on-board controller of the target vehicle, each network command can be directly sent to the on-board controller.
[0062] Alternatively, if the Internet of Vehicles function diagnosis targets at least two on-board controllers in the target vehicle, the cloud can send each network diagnostic instruction to the T-BOX according to the pre-set data transmission rules; the T-BOX can determine the on-board controller corresponding to each network diagnostic instruction according to the data transmission rules of each network diagnostic instruction. Among them, the data transmission rules can be at least one of the network transmission frequency, network transmission bandwidth and transmission time period corresponding to different on-board controllers. It is only necessary to ensure that the transmission process of different on-board controllers is distinguished, and this application does not make any restrictions on this.
[0063] Or optionally, if the Internet of Vehicles function diagnosis is for at least two on-board controllers in the target vehicle, the on-board controller corresponding to the network diagnostic instruction can also be determined based on the instruction type added in the network diagnostic instruction.
[0064] The instruction type is used to assist in locating the onboard controller in the target vehicle diagnosed by the network diagnosis instruction. The instruction type in the network diagnosis instruction can be obtained by at least one traditional instruction parsing method, and this application does not impose any limitation on this.
[0065] In a specific implementation, if the instruction type in the network diagnostic instruction is a vehicle body type, the BCM controller can be used as the vehicle controller corresponding to the network diagnostic instruction; if the instruction type in the network diagnostic instruction is a vehicle computer type, the CDC controller can be used as the vehicle controller corresponding to the network diagnostic instruction; if the instruction type in the network diagnostic instruction is other types, the GW controller can be used as the vehicle controller corresponding to the network diagnostic instruction. It should be noted that the above is only an example of the vehicle controllers corresponding to different instruction types, and should not be understood as a specific limitation on the instruction type and the type of body controller.
[0066] Correspondingly, after receiving the network diagnostic command, the on-board controller responds to the received network diagnostic command, generates command response data, and feeds back the generated command response data to the T-BOX; the T-BOX receives the command response data fed back by each on-board controller.
[0067] It is worth noting that, unlike business instructions, the process of the on-board controller responding to network diagnostic instructions and generating instruction response data only requires simple data interaction and does not require actual business processing. Therefore, unnecessary data calculations of the on-board controller are reduced and the diagnostic efficiency of the Internet of Vehicles function is improved.
[0068] In order to distinguish network diagnostic instructions from business instructions, the cloud can also add a diagnostic identifier to the network diagnostic instruction. The diagnostic identifier is used to indicate that the vehicle controller does not need to process the instruction and only needs to interact with data. Optionally, the cloud can also add a business identifier to the business instruction. The business identifier is used to indicate that the vehicle controller needs to process the instruction.
[0069] S230, generating an initial diagnosis result of the target vehicle according to each command response data, and feeding back the initial diagnosis result to the cloud to generate a target diagnosis result.
[0070] Among them, the initial diagnosis result is used to characterize whether the Internet of Vehicles function of the target vehicle is available. Furthermore, in order to achieve fine-grained diagnosis of the Internet of Vehicles function, the cause of the network abnormality can also be determined when the Internet of Vehicles function is unavailable, and the cause of the network abnormality can be added to the initial diagnosis result. Exemplarily, T-BOX can generate the initial diagnosis result of the target vehicle based on the feedback of the command response data of the vehicle controller corresponding to the distributed network diagnostic command.
[0071] In an optional embodiment, the feedback situation may include whether to provide feedback; if the T-BOX does not receive instruction response data corresponding to a certain network diagnostic instruction, it is determined that the communication link between the T-BOX and the vehicle controller corresponding to the network diagnostic instruction is abnormal.
[0072] It is understandable that in order to avoid the influence of network delay on the initial diagnosis result, T-BOX can also wait for a first preset time, and if no command response data corresponding to a certain network diagnostic command is received during the waiting process, determine that the communication link between T-BOX and the vehicle controller corresponding to the network diagnostic command is abnormal. The first preset time can be set or adjusted by the technician according to needs or experience, or determined through a large number of experiments, and this application does not impose any restrictions on this. For example, the first preset time can be 100 ms.
[0073] In another optional embodiment, T-BOX can also generate an initial diagnosis result of the target vehicle according to the data content in the command response data.
[0074] Optionally, for the command response data that is the same as the default response data, a first initial diagnosis result is generated; the first initial diagnosis result is used to indicate that the network between the cloud and the vehicle controller corresponding to the command response data is connected. Alternatively, for the command response data that is different from the default response data, a second initial diagnosis result is generated; the second initial diagnosis result is used to indicate that the network between the cloud and the vehicle controller corresponding to the command response data is disconnected.
[0075] The default response data may be set or adjusted by a technician according to needs or experience, and may be, for example, simple command response information used to indicate receipt of a corresponding network diagnostic command.
[0076] Correspondingly, T-BOX can feed back the initial diagnosis results to the cloud; the cloud can judge the connectivity of the communication link between T-BOX and the cloud based on the initial diagnosis result feedback of T-BOX, and add the connectivity result to the initial diagnosis result to obtain the target diagnosis result.
[0077] In order to ensure the timeliness of the target diagnosis result, diagnosis time information may also be added to the target diagnosis result.
[0078] In order to facilitate users to obtain the diagnosis results of the Internet of Vehicles function in a timely manner, the cloud can also display the target diagnosis results in a diagnostic instrument or other user terminals (such as vehicle-mounted terminals). For example, it can be displayed on the screen of the production line detection system.
[0079] In the embodiment of the present application, the cloud encapsulates and generates at least one network diagnostic instruction based on at least one target vehicle cloud protocol supported by T-BOX; the T-BOX of the target vehicle distributes the instruction to the vehicle controller corresponding to each network diagnostic instruction; the vehicle controller responds to the received network diagnostic instruction and feeds back the instruction response data to T-BOX; T-BOX generates the initial diagnostic result of the target vehicle according to each instruction response data, and feeds back the result to the cloud; the cloud generates the target diagnostic result based on the initial diagnostic result. The above technical solution can realize the complete business process verification of the Internet of Vehicles function, and the entire diagnostic process does not require user access, nor will it interfere with the user's vehicle use process. The user is unaware of the whole process, which improves the user's vehicle use experience. In addition, when generating network diagnostic instructions, the network diagnostic instructions can be encapsulated and generated for different target vehicle cloud protocols supported by T-BOX, so that the Internet of Vehicles function diagnosis under different target vehicle cloud protocols and the diagnosis of the entire network communication link can be performed in one diagnostic process, which improves the comprehensiveness and convenience of the Internet of Vehicles function diagnosis.
[0080] Based on the technical solutions of the above embodiments, the present application also provides an optional embodiment, in which the feedback process of the target vehicle-cloud protocol before S210 is refined.
[0081] See also Figure 3 The feedback steps of the target vehicle-cloud protocol shown include:
[0082] S310, obtaining a protocol acquisition instruction sent by the cloud.
[0083] S320, in response to the protocol acquisition instruction, feeding back to the cloud at least one target vehicle-cloud protocol supported by the T-BOX.
[0084] The protocol acquisition instruction is used to instruct the acquisition of the vehicle-cloud protocol supported by the T-BOX of the target vehicle.
[0085] In an optional embodiment, the cloud can respond to the diagnostic operation sent by the diagnostic instrument or the user terminal, and send a protocol acquisition instruction to the T-BOX of the target vehicle specified by the diagnostic operation; the T-BOX feeds back the target vehicle cloud protocols supported by itself to the cloud. Furthermore, when the cloud receives the target vehicle cloud protocol, it encapsulates and generates corresponding network diagnostic instructions according to the target vehicle cloud protocols supported by the T-BOX for subsequent use.
[0086] Exemplarily, in response to the protocol acquisition instruction, feeding back to the cloud at least one target vehicle-cloud protocol supported by T-BOX may include: selecting at least one target vehicle-cloud protocol from at least one candidate vehicle-cloud protocol supported by T-BOX according to the instruction type in the protocol acquisition instruction; and feeding back at least one target vehicle-cloud protocol to the cloud. The advantage of this is that the target vehicle-cloud protocol can be selected for the specified instruction type, avoiding the waste of transmission resources caused by irrelevant types of target vehicle-cloud protocols.
[0087] The feedback process of the target vehicle-cloud protocol mentioned above actively sends the protocol acquisition command to T-BOX through the cloud, and actively acquires the target vehicle-cloud protocol. There is no need to store the target vehicle-cloud protocol supported by T-BOX of different vehicles in the cloud, which reduces the storage pressure of the cloud. In addition, the target vehicle-cloud protocol is acquired before each diagnosis of the Internet of Vehicles function, which avoids the change of the vehicle-cloud protocol supported by T-BOX during use, which affects the diagnosis results, reduces the errors or missed diagnoses in the target diagnosis results, and further improves the accuracy and credibility of the target diagnosis results.
[0088] The above embodiments are Figure 1 The T-BOX 110 in the figure is the execution subject, and the diagnostic method of the Internet of Vehicles function is described in detail. Figure 1 The cloud 120 is the execution body, and the vehicle networking function diagnosis method is described in detail.
[0089] See also Figure 4 The vehicle networking function diagnosis method shown is applied to Figure 1 Cloud 120 in the package includes:
[0090] S410, encapsulating instructions respectively based on at least one target vehicle-cloud protocol supported by the T-BOX of the target vehicle, and generating network diagnostic instructions corresponding to each target vehicle-cloud protocol.
[0091] In an optional embodiment, for each target vehicle-cloud protocol, instruction encapsulation is performed based on the target vehicle-cloud protocol to generate a network diagnostic instruction corresponding to the target vehicle-cloud protocol.
[0092] For example, if the cloud and T-BOX have agreed on a data transmission rule in advance, each network diagnostic instruction is sent to T-BOX according to the pre-set data transmission rule. The data transmission rule may be different in at least one of the network transmission frequency, network transmission bandwidth, and transmission period corresponding to different vehicle controllers. It is only necessary to ensure that the transmission process of different vehicle controllers is distinguished, and this application does not impose any limitation on this.
[0093] In another optional embodiment, for each target vehicle-cloud protocol, the instruction type is determined according to the vehicle body controller corresponding to the target vehicle-cloud protocol; in the process of encapsulating instructions based on the target vehicle-cloud protocol to generate network diagnostic instructions, the instruction type is added to the network diagnostic instructions.
[0094] Optionally, the cloud can generate corresponding network diagnostic instructions based on each target vehicle cloud protocol supported by the T-BOX corresponding to the target vehicle stored locally or in other associated devices.
[0095] Or optionally, the cloud may send a protocol acquisition instruction to the T-BOX of the target vehicle in advance, and receive at least one target vehicle cloud protocol supported by the T-BOX in feedback.
[0096] In order to distinguish network diagnostic instructions from business instructions, the cloud can also add a diagnostic identifier to the network diagnostic instruction. The diagnostic identifier is used to indicate that the vehicle controller does not need to process the instruction and only needs to interact with data. Optionally, the cloud can also add a business identifier to the business instruction. The business identifier is used to indicate that the vehicle controller needs to process the instruction.
[0097] In an optional embodiment, the cloud can respond to the diagnostic operation sent by the diagnostic instrument or the user terminal and send a protocol acquisition instruction to the T-BOX of the target vehicle specified by the diagnostic operation; the T-BOX feeds back the target vehicle cloud protocols it supports to the cloud. Furthermore, when the cloud receives the target vehicle cloud protocol, it encapsulates and generates corresponding network diagnostic instructions according to the target vehicle cloud protocols supported by the T-BOX for subsequent use.
[0098] S420, distribute each network diagnostic instruction to the vehicle controller under the corresponding network diagnostic instruction through T-BOX.
[0099] In an optional embodiment, for each network diagnostic instruction, the vehicle body controller corresponding to the received network diagnostic instruction may be determined according to a data transmission rule pre-agreed between the cloud and the T-BOX.
[0100] In another optional embodiment, for each network diagnostic instruction, the network diagnostic instruction may be parsed to obtain the instruction type in the network diagnostic instruction; and the corresponding vehicle controller may be determined according to the instruction type.
[0101] In a specific implementation, if the instruction type in the network diagnostic instruction is a vehicle body type, the BCM controller can be used as the vehicle controller corresponding to the network diagnostic instruction; if the instruction type in the network diagnostic instruction is a vehicle computer type, the CDC controller can be used as the vehicle controller corresponding to the network diagnostic instruction; if the instruction type in the network diagnostic instruction is other types, the GW controller can be used as the vehicle controller corresponding to the network diagnostic instruction. It should be noted that the above is only an example of the vehicle controllers corresponding to different instruction types, and should not be understood as a specific limitation on the instruction type and the type of body controller.
[0102] S430, obtaining the initial diagnosis result of the target vehicle fed back by the T-BOX; wherein the initial diagnosis result is generated by the T-BOX according to the command response data fed back by each vehicle controller.
[0103] S440, generating a target diagnosis result based on the initial diagnosis result.
[0104] The cloud can judge the connectivity of the communication link between T-BOX and the cloud based on the initial diagnosis result feedback of T-BOX, and add the connectivity result to the initial diagnosis result to obtain the target diagnosis result.
[0105] Optionally, after sending the network diagnostic instruction, the cloud can wait for a second preset time. If the cloud does not receive the initial diagnostic result during the waiting process, it is determined that the network communication link between the cloud and the T-BOX is abnormal, and a target diagnostic result indicating the abnormality of the corresponding network communication link is generated. Furthermore, if the cloud receives the initial diagnostic result during the waiting process, the initial diagnostic result can be directly used as the target diagnostic result, or, based on the initial diagnostic result, a network diagnostic report can be further generated, and a target diagnostic result including the network diagnostic report can be generated. Among them, the second preset time can be set or adjusted by the technician according to needs or experience, or determined through a large number of experiments, and this application does not impose any restrictions on this.
[0106] Exemplarily, a network diagnostic report may be generated based on at least one of the vehicle identification of the target vehicle, the instruction type of each network diagnostic instruction, the protocol type of each target vehicle-to-cloud protocol, the on-board controller that responds to the network diagnostic instruction, the transmission time of the diagnostic instruction, the transmission time of the network diagnostic instruction, the transmission time of the instruction response data, the transmission time of the initial diagnostic result, and the abnormal communication link. Among them, the above transmission time may include the sending time corresponding to the sending end and / or the receiving time corresponding to the receiving end. Among them, the abnormal communication link may include at least one of the communication link between the cloud and the T-BOX and the communication link between the T-BOX and any on-board controller, which can be understood as the abnormal cause of the abnormal function of the Internet of Vehicles.
[0107] In order to facilitate users to obtain the diagnosis results of the Internet of Vehicles function in a timely manner, the cloud can also display the target diagnosis results on the diagnostic instrument or other user terminals (such as vehicle-mounted terminals). For example, it can be displayed on the screen of the production line detection system or the vehicle screen. Among them, the vehicle screen can be the vehicle IVI (In-Vehicle Infotainment, vehicle infotainment system) screen.
[0108] In the embodiment of the present application, the cloud encapsulates and generates at least one network diagnostic instruction based on at least one target vehicle-cloud protocol supported by T-BOX; the T-BOX of the target vehicle distributes the instruction to the corresponding on-board controller of each network diagnostic instruction; the on-board controller responds to the received network diagnostic instruction and feeds back the instruction response data to T-BOX; T-BOX generates an initial diagnostic result of the target vehicle based on each instruction response data, and feeds back the result to the cloud; the cloud generates a target diagnostic result based on the initial diagnostic result. The above technical solution can realize the complete business process verification of the Internet of Vehicles function, and the entire diagnostic process does not require user access, nor will it interfere with the user's vehicle use process. The user is unaware of the whole process, which improves the user's vehicle use experience. In addition, when generating network diagnostic instructions, the network diagnostic instructions can be encapsulated and generated for different target vehicle-cloud protocols supported by T-BOX, so that the Internet of Vehicles function diagnosis under different target vehicle-cloud protocols and the diagnosis of the entire network communication link can be performed in one diagnostic process, which improves the comprehensiveness and convenience of the Internet of Vehicles function diagnosis. The above embodiment is based on Figure 1 The cloud 120 in the system is the execution subject, and the vehicle networking function diagnosis method is described in detail. Figure 1 The vehicle controller 130 is the execution body, and the vehicle networking function diagnosis method is described in detail.
[0109] See also Figure 5 The vehicle networking function diagnosis method shown is applied to Figure 1 The vehicle-mounted controller 130 includes:
[0110] S510, obtaining at least one network diagnostic instruction sent by the T-BOX of the target vehicle; wherein the at least one network diagnostic instruction is respectively encapsulated and generated by the cloud based on at least one target vehicle cloud protocol supported by the T-BOX.
[0111] The vehicle-to-cloud protocol can be understood as the communication protocol supported by the on-board controller of the target vehicle when communicating with the cloud through T-BOX. The vehicle-to-cloud protocol can include at least one of MQTT (Message Queuing Telemetry Transport), HTTP (Hypertext Transfer Protocol), WEBSOCKET (a full-duplex communication protocol), etc., and this application does not impose any limitation on this.
[0112] The target vehicle-to-cloud protocol can be understood as the vehicle-to-cloud protocol supported by the target vehicle, that is, the vehicle to be diagnosed, and the corresponding T-BOX. The number of target vehicle-to-cloud protocols can be at least one, and this application does not impose any limitation on this.
[0113] The cloud can respond to the diagnostic operation sent by the diagnostic instrument or user terminal, and encapsulate and generate corresponding network diagnostic instructions based on the target vehicle cloud protocols supported by the T-BOX corresponding to the target vehicle specified by the diagnostic operation; the cloud sends the network diagnostic instructions generated by itself to the T-BOX of the target vehicle, and the T-BOX distributes them to the corresponding vehicle controller; the vehicle controller receives the network diagnostic instructions sent by the T-BOX. Among them, different network diagnostic instructions use different target vehicle cloud protocols; the vehicle controllers corresponding to different network diagnostic instructions can be the same or different, and this application does not impose any restrictions on this.
[0114] It is worth noting that network diagnostic instructions can be understood as instructions specifically used for diagnosing vehicle networking functions, and no longer require the target vehicle to perform certain business processing business instructions.
[0115] S520, feeding back the command response data corresponding to each network diagnostic command to the T-BOX, so that the T-BOX generates and feeds back the initial diagnostic result of the target vehicle to the cloud according to each command response data, so as to generate the target diagnostic result.
[0116] After receiving the network diagnostic command, the on-board controller responds to the received network diagnostic command, generates command response data, and feeds back the generated command response data to T-BOX; T-BOX receives the command response data fed back by each on-board controller, and generates an initial diagnostic result of the target vehicle based on each command response data; T-BOX feeds back the initial diagnostic result to the cloud; the cloud generates a target diagnostic result based on the initial diagnostic result.
[0117] Unlike business instructions, the process of the vehicle controller responding to network diagnostic instructions and generating instruction response data only requires simple data interaction and does not require actual business processing. Therefore, unnecessary data calculations of the vehicle controller are reduced and the diagnostic efficiency of the Internet of Vehicles function is improved.
[0118] In an optional embodiment, for each network diagnostic instruction, the on-board controller responds to the network diagnostic instruction and feeds back default response data as instruction response data to the T-BOX; the T-BOX generates an initial diagnostic result of the target vehicle based on the reception of the instruction response data or the data content in the instruction response data.
[0119] The default response data may be set or adjusted by a technician according to needs or experience, and may be, for example, simple command response information used to indicate receipt of a corresponding network diagnostic command.
[0120] In order to distinguish network diagnostic instructions from business instructions, the cloud can also add a diagnostic identifier to the network diagnostic instruction; accordingly, after receiving the network diagnostic instruction, the on-board controller parses the network diagnostic instruction, and if the parsing result includes the diagnostic identifier, the default response data is fed back to the T-BOX as the instruction response data. Furthermore, if the parsing result does not include the diagnostic identifier, or the parsing result includes the business identifier, the business instruction is executed, and the generated business data is fed back to the T-BOX.
[0121] In the embodiment of the present application, the cloud encapsulates and generates at least one network diagnostic instruction based on at least one target vehicle cloud protocol supported by T-BOX; the T-BOX of the target vehicle distributes the instruction to the vehicle controller corresponding to each network diagnostic instruction; the vehicle controller responds to the received network diagnostic instruction and feeds back the instruction response data to T-BOX; T-BOX generates the initial diagnostic result of the target vehicle according to each instruction response data, and feeds back the result to the cloud; the cloud generates the target diagnostic result based on the initial diagnostic result. The above technical solution can realize the complete business process verification of the Internet of Vehicles function, and the entire diagnostic process does not require user access, nor will it interfere with the user's vehicle use process. The user is unaware of the whole process, which improves the user's vehicle use experience. In addition, when generating network diagnostic instructions, the network diagnostic instructions can be encapsulated and generated for different target vehicle cloud protocols supported by T-BOX, so that the Internet of Vehicles function diagnosis under different target vehicle cloud protocols and the diagnosis of the entire network communication link can be performed in one diagnostic process, which improves the comprehensiveness and convenience of the Internet of Vehicles function diagnosis.
[0122] Based on the technical solutions of the above embodiments, the present application also provides an optional embodiment, in which the Fig. 6A The network architecture diagram shown in Figure 1 details the vehicle networking function diagnosis process.
[0123] Referring to FIG. 6B , the method for diagnosing a function of an Internet of Vehicles includes:
[0124] S601, the cloud sends a protocol acquisition instruction to the T-BOX of the target vehicle according to the diagnostic request initiated by the production line personnel of the target vehicle through the diagnostic instrument or the user end.
[0125] The diagnostic request specifies the vehicle identification of the target vehicle, the device identification of the T-BOX corresponding to the target vehicle, and the instruction type. The vehicle identification can be the vehicle's VIN (Vehicle Identification Number); the device identification of the T-BOX can be the device ID (Identity document); different instruction types can be distinguished by a preset type field, and this application does not impose any restrictions on this.
[0126] Users can access the WEB backend management interface of the SaaS (Software as a Service) layer through PC browsers, mobile browsers, etc. to initiate diagnostic requests, thereby triggering the verification and result query of the target vehicle's Internet of Vehicles function. Correspondingly, the WEB management backend responds to the diagnostic request, generates a protocol acquisition instruction, and sends the protocol acquisition instruction to T-BOX. The cloud-based business center also has a device center for storing the frame number, vehicle model, and TBOX serial number, etc., for users to select and use.
[0127] It is understandable that in order to ensure the security of the diagnosis of the Internet of Vehicles function, a data verification service can also be set up at the SaaS layer to verify the state of the target vehicle, the available state of the initiator of the diagnostic request, and the legal identity of the initiator account of the diagnostic request, etc. Furthermore, an authentication service can also be set up at the SaaS layer to verify the signature in the diagnostic request.
[0128] It should be noted that the business front-end functions of the SaaS layer and the business middle-end functions that provide network diagnostic capabilities can be implemented based on the microservice architecture of the PaaS layer and the infrastructure of the IaaS layer. In order to facilitate system maintenance, high-availability operation and maintenance functions are also provided at the PaaS layer.
[0129] S602, T-BOX obtains the instruction type in the protocol instruction and determines at least one target vehicle-to-cloud protocol supported by itself.
[0130] S603, T-BOX feeds back the target vehicle-cloud protocols to the cloud.
[0131] S604, the cloud encapsulates instructions based on each target vehicle-to-cloud protocol and generates corresponding network diagnostic instructions.
[0132] The terminal gateway in the business middle station on the cloud transmits data with T-BOX, and when receiving the target vehicle-cloud protocol, it encapsulates the instructions through the protocol adapter in the business middle station to obtain the corresponding network diagnostic instructions.
[0133] S605, the cloud sends various network diagnosis instructions to T-BOX.
[0134] S606, T-BOX determines the vehicle controller corresponding to each network diagnostic instruction according to the instruction type in the network diagnostic instruction.
[0135] S607, T-BOX sends corresponding network diagnosis instructions to each vehicle controller.
[0136] S608: The vehicle-mounted controller feeds back the default response data to the T-BOX as the command feedback data.
[0137] S609, the T-BOX waits for a first preset time period, and generates an initial diagnosis result according to the reception of instruction feedback data of each network diagnosis instruction during the waiting process.
[0138] S610, T_BOX sends the initial diagnosis result to the cloud.
[0139] S611, the cloud performs attribution analysis on the network link between the target vehicle and the cloud based on the reception of the initial diagnosis result, and generates a target diagnosis result.
[0140] The Internet of Vehicles functional diagnosis method provided in the embodiment of the present application can completely diagnose the Internet of Vehicles service link without affecting the business process, and can select the target diagnostic protocol based on the instruction type, which is more flexible. In addition, the present application does not limit the number of target diagnostic protocols, and multiple target diagnostic protocols can be used at a time, so multiple protocols can be used in one diagnostic process, which is more versatile. In addition, the communication network traffic cost invested in the above process is low, and it has no effect on the vehicle offline in the production line, nor does it affect the daily production indicators, etc., and has better adaptability. In addition, when the user is using the vehicle, the user is unaware of the entire diagnostic process, which reduces interference to the user.
[0141] It should be understood that, although the steps in the flowcharts involved in the above embodiments are displayed in sequence according to the indication of the arrows, these steps are not necessarily executed in sequence according to the order indicated by the arrows. Unless there is a clear explanation in this article, the execution of these steps is not strictly limited in order, and these steps can be executed in other orders. Moreover, at least a part of the steps in the flowcharts involved in the above embodiments may include multiple steps or multiple stages, and these steps or stages are not necessarily executed at the same time, but can be executed at different times, and the execution order of these steps or stages is not necessarily carried out in sequence, but can be executed in turn or alternately with other steps or at least a part of the steps or stages in other steps.
[0142] Based on the same inventive concept, the embodiment of the present application also provides a vehicle networking function diagnosis device for implementing the vehicle networking function diagnosis method involved above. The implementation scheme for solving the problem provided by the device is similar to the implementation scheme recorded in the above method, so the specific limitations in one or more vehicle networking function diagnosis device embodiments provided below can refer to the limitations of the vehicle networking function diagnosis method above, and will not be repeated here.
[0143] In an exemplary embodiment, Figure 7 As shown, a vehicle networking function diagnosis device is provided, which is configured in the T-BOX of the target vehicle, and includes: a first acquisition module 710, a first distribution module 720 and a first generation module 730. Among them,
[0144] The first acquisition module 710 is used to acquire at least one network diagnostic instruction; the at least one network diagnostic instruction is generated by the cloud based on the corresponding encapsulation of at least one target vehicle-cloud protocol supported by the T-BOX;
[0145] The first distribution module 720 is used to distribute the corresponding network diagnostic instructions to the vehicle controllers corresponding to the network diagnostic instructions, and receive the instruction response data fed back by the corresponding vehicle controllers;
[0146] The first generating module 730 is used to generate an initial diagnosis result of the target vehicle according to each instruction response data, and feed the initial diagnosis result back to the cloud to generate a target diagnosis result.
[0147] In one embodiment, the device further comprises:
[0148] The instruction acquisition module is used to obtain the protocol acquisition instruction sent by the cloud before obtaining at least one network diagnostic instruction; the instruction response module is used to respond to the protocol acquisition instruction and feedback at least one target vehicle-cloud protocol supported by T-BOX to the cloud.
[0149] In one of the embodiments, the instruction response module includes: a selection unit, used to obtain the instruction type in the instruction according to the protocol, and select at least one target vehicle-cloud protocol from at least one candidate vehicle-cloud protocol supported by T-BOX; a feedback unit, used to feedback at least one target vehicle-cloud protocol to the cloud.
[0150] In one embodiment, the first generation module 730 includes: a first generation unit, used to generate a first initial diagnostic result for instruction response data that is the same as the default response data; the first initial diagnostic result is used to indicate network connectivity between the cloud and the vehicle-mounted controller corresponding to the instruction response data; a second generation unit, used to generate a second initial diagnostic result for instruction response data that is different from the default response data; the second initial diagnostic result is used to indicate network interruption between the cloud and the vehicle-mounted controller corresponding to the instruction response data.
[0151] In another exemplary embodiment, Figure 8 As shown, a vehicle networking function diagnosis device is provided, which is configured in the cloud and includes: a packaging module 810, a second distribution module 820, a second acquisition module 830 and a second generation module 840. Among them,
[0152] The encapsulation module 810 is used to encapsulate instructions based on at least one target vehicle-cloud protocol supported by the T-BOX of the target vehicle, and generate network diagnostic instructions corresponding to each target vehicle-cloud protocol;
[0153] The second distribution module 820 is used to distribute each network diagnostic instruction to the vehicle controller under the corresponding network diagnostic instruction through the T-BOX;
[0154] The second acquisition module 830 is used to acquire the initial diagnosis result of the target vehicle fed back by the T-BOX; wherein the initial diagnosis result is generated by the T-BOX according to the command response data fed back by each vehicle controller;
[0155] The second generating module 840 is used to generate a target diagnosis result according to the initial diagnosis result.
[0156] In one of the embodiments, the device also includes: an instruction sending module, which is used to encapsulate instructions based on at least one target vehicle cloud protocol supported by the T-BOX of the target vehicle, and before generating network diagnostic instructions corresponding to each target vehicle cloud protocol, send a protocol acquisition instruction to the T-BOX of the target vehicle; and a protocol receiving module, which is used to receive at least one target vehicle cloud protocol supported by itself fed back by the T-BOX.
[0157] In yet another exemplary embodiment, Fig. 9As shown, a vehicle networking function diagnosis device is provided, which is configured in a vehicle controller and includes: a third acquisition module 910 and a feedback module 920. Among them,
[0158] The third acquisition module 910 is used to acquire at least one network diagnostic instruction sent by the T-BOX of the target vehicle; wherein the at least one network diagnostic instruction is respectively encapsulated and generated by the cloud based on at least one target vehicle cloud protocol supported by the T-BOX;
[0159] Feedback module 920 is used to feed back command response data corresponding to each network diagnostic command to T-BOX, so that T-BOX generates and feeds back the initial diagnostic result of the target vehicle to the cloud according to each command response data, so as to generate a target diagnostic result.
[0160] In one embodiment, the feedback module 920 is specifically configured to feed back default response data as instruction response data to the T-BOX in response to each network diagnosis instruction.
[0161] Each module in the above-mentioned vehicle networking function diagnosis device can be implemented in whole or in part by software, hardware and their combination. Each of the above-mentioned modules can be embedded in or independent of the processor in the computer device in the form of hardware, or can be stored in the memory of the computer device in the form of software, so that the processor can call and execute the corresponding operations of each of the above modules.
[0162] In an exemplary embodiment, a computer device is provided. The computer device may be a terminal, and its internal structure diagram may be as shown in FIG. Fig.10As shown. The computer device includes a processor, a memory, an input / output interface, a communication interface, a display unit and an input device. The processor, the memory and the input / output interface are connected through a system bus, and the communication interface, the display unit and the input device are connected to the system bus through the input / output interface. The processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The input / output interface of the computer device is used to exchange information between the processor and the external device. The communication interface of the computer device is used to communicate with an external terminal in a wired or wireless manner, and the wireless manner can be realized through WIFI, a mobile cellular network, near field communication (NFC) or other technologies. When the computer program is executed by the processor, a method for diagnosing a function of an Internet of Vehicles is realized. The display unit of the computer device is used to form a visually visible picture, which can be a display screen, a projection device or a virtual reality imaging device. The display screen can be a liquid crystal display screen or an electronic ink display screen, and the input device of the computer device can be a touch layer covering the display screen, or a button, trackball or touchpad set on the computer device shell, or an external keyboard, touchpad or mouse.
[0163] Those skilled in the art will understand that Fig.10 The structure shown in the figure is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied. The specific computer device may include more or fewer components than those shown in the figure, or combine certain components, or have a different arrangement of components.
[0164] In an exemplary embodiment, a computer device is provided, including a memory and a processor, wherein a computer program is stored in the memory, and the processor implements the steps in the above-mentioned method embodiments when executing the computer program. It should be noted that the computer device can be a T-BOX device of the target vehicle, a cloud device, or an on-board controller of the target vehicle, etc., and this application does not make any limitation on this.
[0165] In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the steps in the above-mentioned method embodiments are implemented.
[0166] In one embodiment, a computer program product is provided, including a computer program, which implements the steps in the above method embodiments when executed by a processor.
[0167] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data must comply with relevant regulations.
[0168] Those skilled in the art can understand that all or part of the processes in the above-mentioned embodiments can be completed by instructing the relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to the memory, database or other medium used in the embodiments provided in the present application can include at least one of non-volatile memory and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. As an illustration and not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM). The database involved in each embodiment provided in this application may include at least one of a relational database and a non-relational database. Non-relational databases may include distributed databases based on blockchains, etc., but are not limited to this. The processor involved in each embodiment provided in this application may be a general-purpose processor, a central processing unit, a graphics processor, a digital signal processor, a programmable logic device, a data processing logic device based on quantum computing, an artificial intelligence (AI) processor, etc., but are not limited to this.
[0169] The technical features of the above embodiments may be combined arbitrarily. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this application.
[0170] The above embodiments only express several implementation methods of the present application, and the descriptions thereof are relatively specific and detailed, but they cannot be understood as limiting the scope of the present application. It should be pointed out that, for a person of ordinary skill in the art, several variations and improvements can be made without departing from the concept of the present application, and these all belong to the protection scope of the present application. Therefore, the protection scope of the present application shall be subject to the attached claims.
Claims
1. A method for diagnosing vehicle networking functions, characterized in that: The telematics processor T-BOX applied to the target vehicle includes: Acquire at least one network diagnostic instruction; the at least one network diagnostic instruction is generated by the cloud based on the corresponding encapsulation of at least one target vehicle-cloud protocol supported by the T-BOX; Distributing corresponding network diagnostic instructions to the vehicle controllers corresponding to the network diagnostic instructions, and receiving instruction response data fed back by the corresponding vehicle controllers; An initial diagnosis result of the target vehicle is generated according to each of the command response data, and the initial diagnosis result is fed back to the cloud to generate a target diagnosis result.
2. The method according to claim 1, characterized in that Before obtaining at least one network diagnostic instruction, the method further includes: Obtaining a protocol acquisition instruction sent by the cloud; In response to the protocol acquisition instruction, at least one target vehicle-cloud protocol supported by the T-BOX is fed back to the cloud.
3. The method according to claim 2, characterized in that The step of feeding back to the cloud at least one target vehicle-cloud protocol supported by the T-BOX in response to the protocol acquisition instruction includes: Selecting at least one target vehicle-cloud protocol from at least one candidate vehicle-cloud protocol supported by the T-BOX according to the instruction type in the protocol acquisition instruction; The at least one target vehicle-cloud protocol is fed back to the cloud.
4. The method according to any one of claims 1 to 3, characterized in that: Generating an initial diagnosis result of the target vehicle according to each of the command response data includes: For the command response data that is the same as the default response data, a first initial diagnosis result is generated; the first initial diagnosis result is used to indicate that the cloud is connected to the vehicle controller corresponding to the command response data; A second initial diagnostic result is generated for instruction response data different from default response data; the second initial diagnostic result is used to indicate a network interruption between the cloud and the vehicle controller corresponding to the instruction response data.
5. A method for diagnosing vehicle networking functions, characterized in that: Applied in the cloud, including: Based on at least one target vehicle-cloud protocol supported by the T-BOX of the target vehicle, command encapsulation is performed respectively to generate network diagnostic commands corresponding to each target vehicle-cloud protocol; Distributing each of the network diagnostic instructions to the vehicle controller under the corresponding network diagnostic instruction through the T-BOX; Acquire the initial diagnosis result of the target vehicle fed back by the T-BOX; wherein the initial diagnosis result is generated by the T-BOX according to the command response data fed back by each of the vehicle-mounted controllers; A target diagnosis result is generated according to the initial diagnosis result.
6. The method according to claim 5, characterized in that Before respectively encapsulating instructions for at least one target vehicle-to-cloud protocol supported by the T-BOX based on the target vehicle and generating network diagnostic instructions corresponding to each target vehicle-to-cloud protocol, the method further includes: Sending a protocol acquisition instruction to the T-BOX of the target vehicle; Receive at least one target vehicle-to-cloud protocol supported by the T-BOX and fed back by the T-BOX.
7. A vehicle networking function diagnostic device, characterized in that: The telematics processor T-BOX configured in the target vehicle includes: A first acquisition module is used to acquire at least one network diagnostic instruction; the at least one network diagnostic instruction is generated by the cloud based on the corresponding encapsulation of at least one target vehicle-cloud protocol supported by the T-BOX; A first distribution module, used to distribute the corresponding network diagnostic instructions to the vehicle controllers corresponding to the network diagnostic instructions, and receive instruction response data fed back by the corresponding vehicle controllers; The first generating module is used to generate an initial diagnosis result of the target vehicle according to each of the command response data, and feed back the initial diagnosis result to the cloud to generate a target diagnosis result.
8. A vehicle networking function diagnostic device, characterized in that: Configured in the cloud, including: A packaging module, used to encapsulate instructions based on at least one target vehicle-cloud protocol supported by the T-BOX of the target vehicle, and generate network diagnostic instructions corresponding to each target vehicle-cloud protocol; A second distribution module, used to distribute each of the network diagnostic instructions to the vehicle controller under the corresponding network diagnostic instruction through the T-BOX; A second acquisition module is used to acquire the initial diagnosis result of the target vehicle fed back by the T-BOX; wherein the initial diagnosis result is generated by the T-BOX according to the command response data fed back by each of the vehicle-mounted controllers; The second generating module is used to generate a target diagnosis result according to the initial diagnosis result.
9. A computer device comprising a memory and a processor, wherein the memory stores a computer program, wherein: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 6 are implemented.
10. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 6 are implemented.
