WO2021047655A1 - 车载系统异常处理的方法及装置 - Google Patents

车载系统异常处理的方法及装置 Download PDF

Info

Publication number
WO2021047655A1
WO2021047655A1 PCT/CN2020/114868 CN2020114868W WO2021047655A1 WO 2021047655 A1 WO2021047655 A1 WO 2021047655A1 CN 2020114868 W CN2020114868 W CN 2020114868W WO 2021047655 A1 WO2021047655 A1 WO 2021047655A1
Authority
WO
WIPO (PCT)
Prior art keywords
program
abnormal
information
vehicle
processing
Prior art date
Application number
PCT/CN2020/114868
Other languages
English (en)
French (fr)
Inventor
秦弦
王改良
杨跃峰
张裕海
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to EP20863354.5A priority Critical patent/EP4020213A4/en
Publication of WO2021047655A1 publication Critical patent/WO2021047655A1/zh
Priority to US17/692,588 priority patent/US20220197732A1/en

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/0703—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
    • G06F11/079—Root cause analysis, i.e. error or fault diagnosis
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/0703—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
    • G06F11/0706—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation the processing taking place on a specific hardware platform or in a specific software environment
    • G06F11/0736—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation the processing taking place on a specific hardware platform or in a specific software environment in functional embedded systems, i.e. in a data processing system designed as a combination of hardware and software dedicated to performing a certain function
    • G06F11/0739—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation the processing taking place on a specific hardware platform or in a specific software environment in functional embedded systems, i.e. in a data processing system designed as a combination of hardware and software dedicated to performing a certain function in a data processing system embedded in automotive or aircraft systems
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/0703—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
    • G06F11/0706—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation the processing taking place on a specific hardware platform or in a specific software environment
    • G06F11/0709—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation the processing taking place on a specific hardware platform or in a specific software environment in a distributed system consisting of a plurality of standalone computer nodes, e.g. clusters, client-server systems
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/0703—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
    • G06F11/0751—Error or fault detection not based on redundancy
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/0703—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
    • G06F11/0766—Error or fault reporting or storing
    • G06F11/0772—Means for error signaling, e.g. using interrupts, exception flags, dedicated error registers
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/0703—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
    • G06F11/0766—Error or fault reporting or storing
    • G06F11/0775—Content or structure details of the error report, e.g. specific table structure, specific error fields
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/0703—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
    • G06F11/0793—Remedial or corrective actions
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/0703—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
    • G06F11/0766—Error or fault reporting or storing
    • G06F11/0787—Storage of error reports, e.g. persistent data storage, storage using memory protection

Definitions

  • the present application relates to the technical field of vehicle-mounted systems, and in particular, to a method and device for processing abnormalities of vehicle-mounted systems.
  • the vehicle-mounted system can achieve many functions to meet people's needs, and the system is complex.
  • the user needs to drive the vehicle to the repair shop and have an engineer inspect it locally, so as to locate the abnormality and determine the cause of the abnormality, which is time-consuming and laborious and the user experience is poor.
  • the problem location needs to be performed manually, and problems such as poor real-time performance and cumbersome operation are becoming increasingly prominent; on the other hand, the same problem needs to be manually located repeatedly, which wastes human and material resources.
  • the present application provides a method for processing abnormalities in an on-board system, which can give suggestions or reasons for abnormalities based on the program identifiers of programs running abnormally in the on-board systems, avoiding manual processing and saving labor costs.
  • a method for handling an abnormality of an in-vehicle system includes: an in-vehicle client acquires a program identifier of a first program, the first program is a program that runs abnormally; and the in-vehicle client sends to the server Processing request, the processing request is used to instruct the server to determine the first processing result corresponding to the first abnormality identification information according to the first mapping relationship, the processing request carries the first abnormality identification information, and the first
  • the abnormal identification information includes the program identification of the first program, the first mapping relationship records the correspondence between a plurality of abnormal identification information and a plurality of processing results, and each abnormal identification information includes a program identification.
  • the first abnormality identification information contains the program identification of the abnormally running program in the vehicle system, and the server is requested to determine the first processing result corresponding to the first abnormality identification information, which avoids Manual processing, saving labor costs.
  • the vehicle-mounted client may generate first abnormality identification information according to the program identifier of the first program, and the vehicle-mounted client may send a processing request to the server, where the processing request carries the first abnormality identification information, and the processing The request is used to instruct the server to determine the first processing result corresponding to the first abnormal identification information.
  • the code of the first program includes the program identifier of the first program.
  • the difficulty of obtaining the program identifier of the first program by the vehicle-mounted client is reduced, and the system overhead is reduced.
  • the vehicle-mounted client acquiring the program identifier of the first program includes: the vehicle-mounted client acquiring exception stack information, where the exception stack information includes the program identifier of the first program .
  • Obtaining the program identifier of the first program through the abnormal stack information is simple and easy to implement, reducing the difficulty of obtaining the program identifier of the first program by the vehicle-mounted client, and reducing system overhead.
  • the program identifier of the first program is written into the first memory space allocated to the first program, and the first program is The code of a program includes the program identifier of the first program, and the exception stack information is determined according to the first memory space.
  • each abnormality identification information further includes at least one of the following parameters: abnormality log information, abnormal state information, resource occupation information, and the abnormality log information is based on the first According to the log corresponding to the program, the abnormal state information is used to indicate at least one of the following abnormal states: the on-board system memory overflows, the on-board system memory address is wrong, the on-board system program is abnormal, and the resource occupation information is used for To indicate the resource occupancy of the on-board system.
  • the abnormal identification information includes at least one of abnormal log information, abnormal state information, and resource occupation information, which can make the processing result more accurate.
  • the method further includes: the in-vehicle client receiving a processing response sent by the server, the processing response including the first processing result.
  • the first processing result is received through the vehicle-mounted client, and the receiving server provides feedback on the processing result of the vehicle-mounted system abnormality.
  • the first exception handling result includes at least one of a first exception handling suggestion, a first exception cause, and impact information
  • the first exception cause is used to indicate
  • the impact information is used to indicate the second program that is affected.
  • the first processing result includes a first abnormal cause
  • the first abnormal cause is used to indicate a first faulty unit in the on-board system
  • the method further includes :
  • the in-vehicle client receives the processing response sent by the server, the processing response includes impact information, the impact information is used to indicate a second program, and the second program is indicated by the second mapping relationship with the A program associated with the first failure unit, and the second mapping relationship includes indicating an association relationship between a plurality of failure units and a plurality of programs.
  • the method further includes: the vehicle client determines that an abnormal condition is satisfied to determine that the vehicle system is abnormal, and the abnormal condition includes: the vehicle client receives To the indication information, the indication information is used to instruct the vehicle-mounted client to obtain the program identifier of the first program; and/or, detecting that the vehicle-mounted system has at least one of the following abnormal states: the vehicle-mounted system memory overflows , The memory address of the on-board system is wrong, and the on-board system program is abnormal.
  • the system information is collected in time through two methods of abnormal monitoring and user active triggering, which solves the problem of not collecting information in time when a problem occurs.
  • a server receives a processing request sent by a vehicle-mounted client, the processing request carries first abnormality identification information, and the first abnormality identification information includes the first abnormality identification information.
  • a program identifier of a program, the first program is a program that runs abnormally;
  • the server determines a first processing result corresponding to the first abnormality identification information according to a first mapping relationship, where the first processing result includes a first abnormality processing suggestion and/or a first abnormality cause, and the first mapping
  • the relationship records the correspondence between multiple abnormal identification information and multiple processing results, each abnormal identification information includes a program identifier, and each processing result includes abnormal processing suggestions and/or abnormal causes.
  • the server determines the first processing result corresponding to the first abnormal identification information according to the first abnormal identification information, which includes the program identification of the abnormally running program, and the first processing result includes the first abnormal identification information.
  • An exception handling suggestion and/or the first exception cause avoids manual handling and saves labor costs.
  • the code of the first program includes the program identifier of the first program.
  • the difficulty of obtaining the program identifier of the first program by the vehicle-mounted client is reduced, and the system overhead is reduced.
  • each abnormality identification information further includes at least one of the following parameters: abnormality log information, abnormal state information, resource occupation information, and the abnormality log information is based on the first According to the log corresponding to the program, the abnormal state information is used to indicate at least one of the following abnormal states: the on-board system memory overflows, the on-board system memory address is wrong, the on-board system program is abnormal, and the resource occupation information is used for To indicate the resource occupancy of the on-board system.
  • the abnormal identification information includes at least one of abnormal log information, abnormal state information, and resource occupation information, which can make the processing result more accurate.
  • the method further includes: the server sends a processing response to the vehicle client or the user equipment corresponding to the vehicle client, the processing response including all The first processing result.
  • the server By sending the first processing result, the server gives feedback on the processing result of the abnormality of the in-vehicle system.
  • the first exception handling result includes at least one of a first exception handling suggestion, a first exception cause, and impact information
  • the first exception cause is used to indicate
  • the impact information is used to indicate the second program that is affected.
  • the first processing result includes a first abnormal cause
  • the first abnormal cause is used to indicate a first faulty unit in the on-board system
  • the method further includes :
  • the server determines a second program associated with the first faulty unit according to a second mapping relationship, and the second mapping relationship includes indicating an association relationship between multiple faulty units and multiple programs.
  • the method further includes: the server sends a processing response to the vehicle client or the user equipment corresponding to the vehicle client, the processing response including the impact Information, the impact information is used to indicate the second program.
  • the method further includes: the server sends instruction information to the vehicle client, and the instruction information is used to instruct the vehicle client to send instructions to the server. Send the processing request.
  • the system information is collected in time through two methods that are actively triggered by the user, which solves the problem of not collecting timely information when a problem occurs.
  • an apparatus for processing an abnormality of an in-vehicle system which is characterized in that it includes: an acquisition module for acquiring a program identifier of a first program, the first program being a program that runs abnormally;
  • the terminal sends a processing request, the processing request is used to instruct the server to determine the first processing result corresponding to the first abnormality identification information according to the first mapping relationship, and the first processing result includes the first abnormal processing suggestion and /Or the first reason for the abnormality,
  • the processing request carries first abnormality identification information
  • the first abnormality identification information includes the program identification of the first program
  • the first mapping relationship records multiple abnormal identification information and multiple Correspondence between two processing results
  • each abnormal identification information includes a program identifier
  • each processing result includes abnormal processing suggestions and/or abnormal causes.
  • the code of the first program includes the program identifier of the first program.
  • the acquisition module is configured to acquire exception stack information, where the exception stack information includes the program identifier of the first program.
  • the program identifier of the first program is written into the first memory space allocated to the first program, and the first program is The code of a program includes the program identifier of the first program, and the exception stack information is determined according to the first memory space.
  • each abnormality identification information further includes at least one of the following parameters: abnormality log information, abnormal status information, resource occupation information, and the abnormality log information is based on the first According to the log corresponding to the program, the abnormal state information is used to indicate at least one of the following abnormal states: the on-board system memory overflows, the on-board system memory address is wrong, the on-board system program is abnormal, and the resource occupation information Used to indicate the resource occupancy of the vehicle-mounted system.
  • the transceiver module is further configured to receive a processing response sent by the server, where the processing response includes the first processing result.
  • the first exception handling result includes at least one of a first exception handling suggestion, a first exception cause, and impact information
  • the first exception cause is used to indicate
  • the impact information is used to indicate the second program that is affected.
  • the first processing result includes a first abnormal cause, and the first abnormal cause is used to indicate a first faulty unit in the on-board system
  • the transceiver module also Used to receive a processing response sent by the server, where the processing response includes impact information, the impact information is used to indicate a second program, and the second program is indicated by a second mapping relationship with the first fault Unit-associated programs, and the second mapping relationship includes indicating an association relationship between a plurality of faulty units and a plurality of programs.
  • the device further includes a determining module, configured to determine that an abnormal condition is met to determine that the on-board system is abnormal, and the abnormal condition includes: the on-board client receives Indication information, the indication information is used to instruct the vehicle-mounted client to obtain the program identifier of the first program; and/or, detecting that the vehicle-mounted system has at least one of the following abnormal states: the vehicle-mounted system memory overflows, The in-vehicle system memory address is wrong, and the in-vehicle system program is abnormal.
  • an apparatus for processing an abnormality in a vehicle system including: a transceiver module, configured to receive a processing request sent by a vehicle client, the processing request carrying first abnormality identification information, and the first abnormality identification information includes a first The program identifier of the program, the first program is a program that runs abnormally; the determining module is configured to determine the first processing result corresponding to the first abnormal identifier information according to the first mapping relationship, and the first processing result includes the first An exception handling suggestion and/or the first exception cause, the first mapping relationship records the correspondence between a plurality of exception identification information and a plurality of processing results, each exception identification information includes a program identification, and each processing result includes an exception Handling suggestions and/or abnormal reasons.
  • the code of the first program includes the program identifier of the first program.
  • each abnormality identification information further includes at least one of the following parameters: abnormality log information, abnormal state information, resource occupation information, and the abnormality log information is based on the first According to the log corresponding to the program, the abnormal state information is used to indicate at least one of the following abnormal states: the on-board system memory overflows, the on-board system memory address is wrong, the on-board system program is abnormal, and the resource occupation information is used for To indicate the resource occupancy of the on-board system.
  • the transceiver module is further configured to send a processing response to the vehicle-mounted client or user equipment corresponding to the vehicle-mounted client, where the processing response includes the first One processing result.
  • the first exception handling result includes at least one of a first exception handling suggestion, a first exception cause, and impact information
  • the first exception cause is used to indicate
  • the impact information is used to indicate the second program that is affected.
  • the first processing result includes a first abnormal cause
  • the first abnormal cause is used to indicate a first faulty unit in the on-board system
  • the determining module further It is used to determine a second program associated with the first faulty unit according to a second mapping relationship, where the second mapping relationship includes indicating an association relationship between multiple faulty units and multiple programs.
  • the transceiver module is further configured to send a processing response to the vehicle client or user equipment corresponding to the vehicle client, where the processing response includes impact information,
  • the influence information is used to indicate the second program.
  • the transceiver module is further configured to send instruction information to the vehicle-mounted client, where the instruction information is used to instruct the vehicle-mounted client to send all information to the server. The processing request.
  • a vehicle system abnormality processing device including: a processor, a communication interface, and a processor for obtaining a program identifier of a first program, the first program being a program that runs abnormally; and a communication interface for Send a processing request to the server, where the processing request is used to instruct the server to determine the first processing result corresponding to the first exception identification information according to the first mapping relationship, and the first processing result includes the first exception processing Suggestion and/or the first reason for the abnormality, the processing request carries first abnormality identification information, the first abnormality identification information includes the program identification of the first program, and the first mapping relationship records multiple abnormality identification information Corresponding relationships with multiple processing results, each abnormal identification information includes a program identifier, and each processing result includes abnormal processing suggestions and/or abnormal causes.
  • the code of the first program includes the program identifier of the first program.
  • the processor is configured to obtain exception stack information, where the exception stack information includes the program identifier of the first program.
  • the program identifier of the first program is written into the first memory space allocated to the first program, and the first program is The code of a program includes the program identifier of the first program, and the exception stack information is determined according to the first memory space.
  • each abnormality identification information further includes at least one of the following parameters: abnormality log information, abnormal state information, resource occupation information, and the abnormal log information is based on the first According to the log corresponding to the program, the abnormal state information is used to indicate at least one of the following abnormal states: the on-board system memory overflows, the on-board system memory address is wrong, the on-board system program is abnormal, and the resource occupation information is used for To indicate the resource occupancy of the on-board system.
  • the communication interface is further configured to receive a processing response sent by the server, where the processing response includes the first processing result.
  • the first exception handling result includes at least one of a first exception handling suggestion, a first exception cause, and impact information
  • the first exception cause is used to indicate
  • the impact information is used to indicate the second program that is affected.
  • the first processing result includes a first abnormality cause
  • the first abnormality cause is used to indicate the first faulty unit in the on-board system
  • the communication interface is also used to ,
  • the impact information is used to indicate a second program
  • the second program is associated with the first fault unit indicated by the second mapping relationship
  • the second mapping relationship includes indicating an association relationship between a plurality of failed units and a plurality of programs.
  • the processor is further configured to determine that an abnormal condition is satisfied to determine that the on-board system is abnormal, and the abnormal condition includes: the on-board client receives the indication information, so The indication information is used to instruct the vehicle-mounted client to obtain the program identifier of the first program; and/or detect that the vehicle-mounted system has at least one of the following abnormal states: the vehicle-mounted system memory overflows, the vehicle-mounted system The memory address is wrong, the on-board system program is abnormal.
  • a device for processing an abnormality of an in-vehicle system which includes a processor and a communication interface.
  • a processor configured to determine a first processing result corresponding to the first abnormal identification information according to a first mapping relationship, the first processing result includes a first abnormal processing suggestion and/or a first abnormal cause, the first A mapping relationship records the correspondence between multiple abnormal identification information and multiple processing results, each abnormal identification information includes a program identifier, and each processing result includes abnormal processing suggestions and/or abnormal causes.
  • the code of the first program includes the program identifier of the first program.
  • each abnormality identification information further includes at least one of the following parameters: abnormality log information, abnormal state information, resource occupation information, and the abnormality log information is based on the first According to the log corresponding to the program, the abnormal state information is used to indicate at least one of the following abnormal states: the on-board system memory overflows, the on-board system memory address is wrong, the on-board system program is abnormal, and the resource occupation information is used for To indicate the resource occupancy of the on-board system.
  • the communication interface is also used to send a processing response to the vehicle-mounted client or user equipment corresponding to the vehicle-mounted client, where the processing response includes the first processing result.
  • the first exception handling result includes at least one of a first exception handling suggestion, a first exception cause, and impact information
  • the first exception cause is used to indicate
  • the impact information is used to indicate the second program that is affected.
  • the first processing result includes a first abnormality cause
  • the first abnormality cause is used to indicate the first faulty unit in the on-board system
  • the processor is also used to , Determining a second program associated with the first faulty unit according to a second mapping relationship, where the second mapping relationship includes indicating an association relationship between multiple faulty units and multiple programs.
  • the communication interface is also used to send a processing response to the vehicle client or user equipment corresponding to the vehicle client, where the processing response includes impact information, and the The influence information is used to indicate the second program.
  • the communication interface is also used to send instruction information to the vehicle-mounted client, where the instruction information is used to instruct the vehicle-mounted client to send the processing to the server request.
  • an exception handling system for an in-vehicle system which includes the above-mentioned in-vehicle client and server.
  • a computer storage medium which when the computer instruction runs on an electronic device, causes the electronic device to execute the method described in the first aspect.
  • a computer storage medium which when the computer instruction runs on an electronic device, causes the electronic device to execute the method described in the second aspect.
  • a chip system in a tenth aspect, includes at least one processor, and when a program instruction is executed in the at least one processor, the chip system is caused to execute the method described in the first aspect.
  • a chip system in an eleventh aspect, includes at least one processor, and when a program instruction is executed in the at least one processor, the chip system is caused to execute the method described in the second aspect.
  • Figure 1 is a schematic diagram of a format of stack information.
  • FIG. 2 is a schematic flowchart of a method for processing anomaly of an in-vehicle system according to an embodiment of the present application.
  • FIG. 3 is a schematic flowchart of another method for processing anomaly of an in-vehicle system provided by an embodiment of the present application.
  • Fig. 4 is a schematic diagram of the structural relationship of the in-vehicle system.
  • Fig. 5 is a schematic diagram of a system for processing an abnormality of a vehicle-mounted system provided by an embodiment of the present application.
  • FIG. 6 is a schematic structural diagram of a device for processing an abnormality of an in-vehicle system provided by an embodiment of the present application.
  • FIG. 7 is a schematic structural diagram of another vehicle-mounted system abnormality processing device provided by an embodiment of the present application.
  • FIG. 8 is a schematic structural diagram of another vehicle-mounted system abnormality processing device provided by an embodiment of the present application.
  • FIG. 9 is a schematic structural diagram of another vehicle-mounted system abnormality processing device provided by an embodiment of the present application.
  • GSM global system of mobile communication
  • CDMA code division multiple access
  • WCDMA wideband code division multiple access wireless
  • GPRS general packet radio service
  • LTE long term evolution
  • WLANs wireless local area networks
  • the abnormal state can be stored by using the core dump technology of Linux.
  • the vehicle system When an abnormal operation of a program in the vehicle system is detected, the vehicle system outputs stack information.
  • Use the core dump service to capture the stack information when the program exits abnormally.
  • the stack information stores the memory address of the abnormal program.
  • the corresponding log generated by the running program can be captured through the log management service.
  • the hypertext transfer protocol (HTTP) is used to complete the connection, authentication and communication with the network server, realize remote connection and automatic upload of abnormal logs, and report the status when the abnormality occurs as soon as possible.
  • FIG. 1 is a schematic diagram of a format of stack information.
  • the stored information includes abnormal status information, the memory address of the program that exited abnormally, program information, variable parameters, etc. It should be understood that the format of the stack information shown in FIG. 1 is only exemplary, and each stack address may include more or less information.
  • the abnormal state information is used to indicate the abnormal state of the in-vehicle system.
  • the abnormal state includes, for example, a memory overflow, a memory address error, and an on-board system program abnormality.
  • Variable parameters are related parameters in the running process of the program, such as the input information of the program.
  • the program information may be, for example, the name and function of the program. Because the program information is not uniformly defined, it is impossible to accurately determine the abnormal program through the program information.
  • the program runs in the in-vehicle system, and the memory space allocated by the in-vehicle system for the same program is different each time. Therefore, maintenance personnel are required to check the memory according to the memory address of the program, determine the program to be run when a failure occurs, and thereby determine the function of the program. Combined with the log information, the cause of the failure can be determined and solutions can be provided.
  • the above method does not have an active collection function.
  • log collection cannot be performed.
  • Another method for handling abnormalities in the on-board system uses watchdog technology and status verification technology to know whether the on-board system is abnormal.
  • Abnormal information includes crash, restart, and unresponsive operation.
  • the log of the vehicle system is recorded, and the abnormal information and the recorded log information are sent to the mailbox designated by the user.
  • the log information maintainer determines the program to be run when the log is generated corresponding to the failure, so as to determine the function of the program and so on. Combined with the log information, the cause of the failure can be determined and solutions can be provided.
  • the collected information still needs to be processed manually to locate the problem, determine the cause of the abnormality of the vehicle-mounted system, and provide solutions.
  • the handling of anomalies in the on-board system relies on manual labor, and the efficiency is low.
  • an embodiment of the present application provides a method for processing an abnormality of an on-board system.
  • FIG. 2 is a schematic flowchart of a method for processing anomaly of an in-vehicle system according to an embodiment of the present application.
  • the in-vehicle system may be, for example, an in-vehicle infotainment (IVI) or the like.
  • step S101 the vehicle-mounted client obtains the program identifier of the first program.
  • the first program is a program that runs abnormally in the vehicle system.
  • the on-board system monitors the running process.
  • the in-vehicle system saves the information of the abnormal program in the stack.
  • the abnormal state may include, for example, at least one of the following states: the on-board system memory overflows, the on-board system memory address is wrong, the on-board system program is abnormal, and so on.
  • Memory overflow means insufficient memory, and the memory size cannot meet the memory space requirements of the program.
  • a memory address error can also be called a segmentation fault.
  • the memory accessed by the program exceeds the memory space allocated by the vehicle system for the program. For example, the program accesses a non-existent memory address, accesses a memory address protected by the vehicle system, or accesses a read-only memory address. Memory address and so on.
  • the abnormality of the vehicle system program may include at least one of the following states: the vehicle system program is deadlocked, the vehicle system program is abnormally exited, and the like.
  • Program deadlock refers to a blocking phenomenon caused by competition for resources or due to communication between two or more processes in the execution process. If there is no external force, they will not be able to advance.
  • the first program may be the abnormal program.
  • the on-board client can be instructed to collect information related to the running program.
  • the in-vehicle system acquires instruction information, which is used to instruct the in-vehicle system to save the information related to the abnormally running program, that is, the first program in the stack.
  • the information related to the first program is stored in the stack, that is, the information related to the first program is output in the stack.
  • the user can input the instruction information in the vehicle client or the vehicle system, the user can also send the instruction information to the vehicle system through other user equipment, and the user can also send request information to the vehicle service terminal through the user equipment.
  • the request information is used to request the vehicle service terminal Send the instruction information to the in-vehicle client device or the in-vehicle system.
  • the vehicle-mounted client can send the instruction information to the vehicle-mounted system.
  • the in-vehicle system may be part of the in-vehicle client, or the in-vehicle client may be part of the in-vehicle system.
  • the user when the user perceives an abnormality in the in-vehicle system, but the in-vehicle client fails to obtain the program identification of the abnormally running program in time, the user can instruct the in-vehicle client to obtain the program identification of the abnormally running program, so as to promptly detect the abnormality of the in-vehicle system The situation is dealt with.
  • the vehicle-mounted client determines that an abnormal condition is satisfied to determine that the vehicle system is abnormal, and the abnormal condition includes: the vehicle-mounted client receives instruction information, and the instruction information is used to instruct the vehicle-mounted client to obtain The program identifier of the first program; and/or, detecting that the on-board system has at least one of the following abnormal states: the on-board system memory overflows, the on-board system memory address is wrong, and the on-board system program is abnormal.
  • the instruction information may also be used to instruct the vehicle-mounted client to send the processing request to the server.
  • the abnormality of the on-board system program can be manifested as the on-board system memory overflow and/or the on-board system memory address error.
  • the first program that has the abnormality is determined, and the stack information is output.
  • the vehicle-mounted client can determine that the abnormal condition is met based on the detection of the vehicle-mounted system, and can also detect the stack information output by the vehicle-mounted system to determine that the vehicle-mounted system program is abnormal, thereby determining that the abnormal condition is met. Detecting the stack information output by the on-board system of the on-board client can also be understood as the detection of abnormalities in the on-board system program.
  • the information under abnormal conditions of the in-vehicle system can be collected in time, so as to deal with it as soon as possible and improve the user experience.
  • the information collected by the vehicle-mounted client terminal may include the program identifier of the first program.
  • the information collected by the vehicle client may also include one or more of abnormal log information, abnormal state information, resource occupation information, and the like.
  • the on-board system When the on-board system is abnormal, the on-board system outputs abnormal stack information, and the abnormal stack information is stored in the stack. When an abnormality occurs in the on-board system, the on-board system writes information related to the abnormality into the stack.
  • the exception stack information can include all or part of the information stored in the stack. The information stored in the stack can be seen in Figure 1.
  • the called program is stored in the memory. That is, when the first program is running, the program of the first program is written into the first memory space allocated for the first program.
  • the program identifier can be written in the program.
  • the program identifier is used to identify different programs.
  • the first program is a program that runs abnormally.
  • the stack information output by the in-vehicle system may include the program identifier of the first program.
  • the program information may include the program identifier of the abnormal program, or a new field may be added to the stack information, and the program identifier of the abnormal program may be used as the field information. Therefore, the exception stack information corresponding to the first program may include the program identifier of the first program.
  • the stack information corresponding to the first program output by the in-vehicle system may include the address of the first program in the memory.
  • the stack information corresponding to the first program output by the in-vehicle system may include abnormal state information, and the abnormal state information is used to indicate the abnormal state that has occurred.
  • the vehicle-mounted client can obtain the exception stack information, thereby obtaining the program identifier of the first program.
  • the vehicle-mounted client can determine the log corresponding to the program that is running abnormally, that is, the log corresponding to the first program.
  • the log is the operation trace of the on-board system.
  • the abnormal log information can be obtained according to the information recorded in the log corresponding to the abnormal program.
  • the abnormal log information may include all or part of the information recorded in the log corresponding to the program running abnormally.
  • the abnormal log information may be obtained by desensitizing the information recorded in the log corresponding to the program running abnormally. Information desensitization is to desensitize the collected information to protect user privacy.
  • the format of the log can be defined.
  • the log corresponding to the program may include the program identifier of the program. That is, the abnormal log information corresponding to the first program may include the program identifier of the first program.
  • the vehicle-mounted client can obtain the abnormal log information, thereby obtaining the program identifier of the first program.
  • the vehicle-mounted client may determine the address of the first program in the external memory, and the address of the first program in the external memory may also be referred to as the storage address of the first program.
  • the first program is determined according to the address in the memory of the first program in the exception stack information.
  • the vehicle-mounted client can traverse the external memory to determine the storage address of the first program, that is, the address of the first program in the external memory.
  • the vehicle-mounted client can use the storage address of the first program as the program identifier of the first program.
  • the cause of the same abnormal state may be the same. Therefore, after the abnormal situation is manually processed, the one-to-one correspondence between the abnormal state identifier and the processing result can be determined.
  • the reasons for the abnormal state may also be different.
  • the abnormal state identifier may correspond to multiple processing results.
  • the abnormal identification information may be determined based on the program identifier, or the abnormal identification information may be determined based on at least one of abnormal log information, abnormal status information, resource occupation information, and the program identifier.
  • the first abnormality identification information may include the program identification of the first program.
  • the program identifier of the first program in the first exception identification information may be the same as or different from the program identifier of the first program in the exception log information or the exception stack information.
  • the program identifier of the first program in the first exception identification information may be obtained by mapping, for example, performing compression mapping, on the program identifier of the first program in the exception log information or the exception stack information.
  • Resource occupation information may also be referred to as operating system information, and may include one or more of hard disk occupation information, handle information, memory occupation information, and central processing unit (CPU) occupation information.
  • the hard disk occupancy information can be used to indicate the occupancy of the hard disk of the vehicle system.
  • the handle information can be used to indicate the number of handles occupied in the in-vehicle system. For example, the handle is used to identify the file opened in the vehicle-mounted system, and the vehicle-mounted system can allocate a handle for each open file.
  • the memory usage information is used to indicate the overall memory usage of the vehicle system.
  • the CPU occupancy information is used to indicate the CPU occupancy of the in-vehicle system.
  • the vehicle-mounted client may send a request message to the vehicle-mounted system, and the request message is used to instruct the vehicle-mounted system to send resource occupation information to the vehicle-mounted client.
  • the vehicle-mounted system may send resource occupation information to the vehicle-mounted client after receiving the request message sent by the vehicle-mounted client.
  • the vehicle-mounted client terminal may send the request message to the vehicle-mounted system when it is determined that the abnormal condition is satisfied, that is, when it is determined that the vehicle-mounted system is abnormal.
  • the vehicle-mounted client can obtain the resource occupation information sent by the vehicle-mounted system.
  • the abnormal identification information includes resource occupancy information
  • the server can determine from the occupancy of the on-board system resources whether the abnormality of a bucket of the on-board system is caused by insufficient resources in the on-board system. Further, it can be determined which resource shortage or resource shortages caused the abnormality of the in-vehicle system.
  • the abnormal identification information can also be determined only based on the program identification. At this time, according to the abnormal identification information, one or more processing results can be determined.
  • the one or more processing results may be processing results corresponding to a variety of abnormal log information, or in other words, the one or more processing results are one or more processing results that cause an abnormality in the on-board system during the operation of the program corresponding to the program identifier .
  • the abnormal identification information may include the program identification, and it can be understood that the abnormal identification information includes all the information of the program identification, or the abnormal identification information includes the result of compressing and mapping the program identification.
  • the abnormal identification information includes the program identification of the first program.
  • the abnormality identification information may also include at least one of abnormal state information, abnormal log information, and resource occupation information.
  • the corresponding program can be determined according to the abnormal identification information.
  • at least one of corresponding abnormal state information, abnormal log information, and resource occupation information can also be determined according to the abnormal identification information.
  • the vehicle-mounted client obtains the program identifier of the first program.
  • the vehicle-mounted client can obtain the abnormal stack information and/or the program identifier of the first program contained in the log corresponding to the first program.
  • the vehicle-mounted client can also determine the storage address of the first program according to the abnormal stack information, and the vehicle-mounted client obtains the storage address , Thereby obtaining the program ID of the first program.
  • step S102 the vehicle-mounted client sends a processing request to the server.
  • the processing request carries first abnormality identification information, and the first abnormality identification information includes the program identification of the first program. That is, the processing request includes the program identifier of the first program.
  • the first abnormality identification information may also include abnormality log information and/or abnormality status information.
  • the abnormal state information is used to indicate at least one of the following abnormal states: the on-board system memory overflows, the on-board system memory address is wrong, and the on-board system program is abnormal.
  • the processing request is used to instruct the server to determine the first processing result corresponding to the first abnormal identification information.
  • the server determines the first processing result and/or influence information.
  • the first processing result may include at least one of abnormal processing suggestions and abnormal cause influence information.
  • the impact information is used to indicate the second program that is affected when the on-board system is abnormal.
  • the second program may be a program associated with the first malfunctioning unit that caused the abnormality of the in-vehicle system.
  • the server may determine the first processing result corresponding to the first abnormal identification information according to the first mapping relationship.
  • the server can determine whether the abnormality of the in-vehicle system is due to insufficient resources based on the resource occupation information, that is, the occupation of vehicle system resources It is caused by insufficient resources of the system, and it can be specifically judged which resource is insufficient or caused by the abnormality of the on-board system.
  • the server may determine the first processing result corresponding to the first abnormality identification information according to the first mapping relationship when it is determined that the abnormality is not caused by insufficient resources.
  • the first processing result is determined according to the first mapping relationship.
  • the first mapping relationship records the correspondence between a plurality of abnormal identification information and a plurality of processing results, and each abnormal identification information includes a program identification.
  • the abnormality identification information may also include abnormality log information and/or abnormality status information.
  • Each treatment result may include one or more treatment suggestions, and/or, one or more abnormal causes, and one or more affected programs.
  • the server can determine one or more processing results according to the program identifier of the first program.
  • the first processing result includes the one or more processing results.
  • the server may further determine one or more processing results from the multiple processing results according to the abnormal log information and/or abnormal status information in the first abnormal identifier information. Multiple processing results.
  • the first processing result may include the first reason for the abnormality.
  • the first cause of abnormality is used to indicate the first faulty unit in the vehicle-mounted system.
  • the abnormality of the in-vehicle system is caused by the failure of the first malfunctioning unit.
  • the server can determine the second program associated with the first faulty unit according to the second mapping relationship.
  • the second mapping relationship is used to indicate the association relationship between multiple failure units and multiple programs.
  • the failure of the first failed unit may cause the program associated with the first failed unit to be affected.
  • the server determines the second program associated with the first faulty unit.
  • the second program is a program that may be affected by the failure of the first faulty unit, that is, the second program is the program corresponding to the first abnormal identification information. In the case of an abnormal situation of the on-board system corresponding to an abnormal identification information, the second program is affected.
  • the server may determine the second program corresponding to the first abnormal identification information according to the association relationship between the multiple abnormal identification information and the multiple programs.
  • the processing request may include abnormality log information, and the first abnormality identification information may include abnormality log information, or the abnormality log information may be located in a field other than the abnormality log information in the processing request.
  • the first processing result may be manually determined.
  • the first processing result can be determined according to the abnormal log information and the program identifier of the first program. After that, the first mapping relationship is updated, and the corresponding relationship between the first abnormality identification information and the first processing result is added to the first mapping relationship.
  • the server can determine the second program according to the third mapping relationship.
  • the third mapping relationship records the correspondence between multiple abnormal identification information and multiple programs.
  • the server sends a processing response.
  • the processing response may include the first processing result and/or impact information.
  • the server can send a processing response to the vehicle client, or the server can send a processing response to the user equipment corresponding to the vehicle client.
  • the user equipment corresponding to the vehicle client can be registered on the server in advance, that is, the server saves the corresponding relationship between the vehicle client and the user equipment.
  • the server terminal and the vehicle customer service terminal can be independent devices, or they can be integrated into the same device to achieve different functions.
  • the information transmission between the server terminal and the vehicle-mounted customer service terminal can be carried out in a wired or wireless manner.
  • steps S101-S103 when the on-board system is abnormal, the processing result can be automatically provided to solve the problem in the on-board system, which solves the problem of localization of maintenance personnel when the problem occurs, saves time and improves user experience.
  • FIG. 3 is a schematic flowchart of a method for processing anomaly of an in-vehicle system according to an embodiment of the present application.
  • step S201 the specification is defined.
  • the program identification is defined. Define stack information printing specifications and log printing specifications.
  • the program identifier is used to identify a section of program. Each program is used to execute a corresponding method.
  • the program identifier can include, for example, the service name, function name, and method name.
  • the program identifier music::play::playNext can be used to indicate the name of the program to play the next piece of music, where playNext is the method name, play is the function name, and music is service name.
  • the on-board system can print stack information when an abnormal state is detected, that is, record abnormal-related information in the stack, that is, the on-board system can record abnormal-related information in the stack in the case of abnormalities according to monitoring.
  • the in-vehicle system can also record abnormal-related information in the stack when receiving the instruction information.
  • the indication information may be used to indicate that an abnormal state occurs, or the indication information may be used to instruct the vehicle-mounted client to obtain the program identifier of the first program, or the indication information may be used to instruct the vehicle-mounted client to send the processing request to the server .
  • the instruction information may be input by the user to the in-vehicle system, or may be sent by the user equipment to the in-vehicle system, or the user equipment may send an instruction to the server, and the server may send the instruction information to the in-vehicle device.
  • the format of the exception-related information recorded in the stack can be seen in Figure 1.
  • the program information may include an abnormal program identifier.
  • the vehicle-mounted client can extract exception stack information from the exception-related information recorded in the stack.
  • the abnormal stack information may include abnormal state information, and the abnormal state information is used to indicate the abnormal state.
  • Abnormal state information can also be referred to as abnormal semaphore.
  • the abnormal state includes, for example, a memory overflow, a memory address error, and an on-board system program abnormality. Among them, abnormal situations such as memory overflow and memory address errors can be detected and determined by the on-board system.
  • the abnormal stack information may include the abnormal program identifier, which is the program identifier of the program running when the abnormal state occurs.
  • the exception stack information may also include the memory address of the program running in the exception state.
  • the log can record the running track of the program.
  • adding the log prefix can make the correspondence between the log information and the program more clear.
  • the log prefix may include service names, function names, etc., for example, the log prefix may include music::play::playNext.
  • step S202 the knowledge base is established.
  • the knowledge base can include two parts, one is the structural relationship of the vehicle-mounted system, and the other is the abnormal problem library.
  • a bottom-level unit provides support for multiple upper-level units. It should be understood that the bottom-level unit and the upper-level unit are relative concepts.
  • the bottom-level unit may also be referred to as the lower-level unit.
  • the service unit from the bottom to the top can be the service unit, the function unit, and the method unit in order.
  • the methods and/or functions provided by other upper-level units that depend on the bottom-level unit will also be abnormal, that is, the upper-level unit of the bottom-level unit will be affected.
  • the car service unit serves as the bottom unit to provide support for its upper unit air conditioning function unit, music function unit, etc.
  • the air conditioning function unit as the bottom unit provides support for its upper unit startup method unit, temperature adjustment method unit, etc.
  • the various methods that rely on the air conditioning function unit of the car service unit will also be abnormal.
  • the structural relationship of the on-board system can also be understood as the association relationship between multiple faulty units and multiple programs.
  • a program can be used to implement a method and can correspond to a method unit, that is, a program can correspond to a method unit one-to-one.
  • the abnormality of the in-vehicle system may be caused by an abnormality or failure of one or more of the service unit, function unit, and method unit.
  • multiple units that may be malfunctioning can be determined according to the structural relationship of the on-board system.
  • When performing manual analysis combining one or more of abnormal status information, abnormal log information, and resource occupancy information, one or more units that may be malfunctioning can be further determined from the multiple units.
  • one or more programs affected by the function can be determined according to the structural relationship of the on-board system, that is, the association relationship between the failed unit and one or more programs can be determined.
  • the abnormal problem database includes a first mapping relationship, that is, a corresponding relationship between a plurality of abnormal identification information and a plurality of processing results.
  • Each treatment result includes abnormal treatment suggestions and/or abnormal reasons.
  • the abnormal identification information may be obtained by compressing and mapping the abnormal program identification, abnormal status information, and abnormal log information.
  • steps S201-S202 the preparation phase of the on-board device diagnosis method is completed.
  • step S203 abnormal data of the on-board system is collected.
  • Obtain information about the in-vehicle system such as: abnormal service stack information, abnormal service log information, resource occupation information, etc.
  • Two methods for collecting abnormal data of on-board system can be provided. In both cases, the abnormal data collection of the on-board system is carried out.
  • the collected information may include exception stack information, exception log information, etc., for subsequent exception location.
  • Exception location is to determine the cause of the exception or give suggestions for handling the exception.
  • the abnormal cause is used to indicate the faulty unit in the on-board system.
  • the faulty unit causes the on-board system to be abnormal, that is, the abnormality of the on-board system is caused by the failure of the faulty unit.
  • Exception handling suggestions are solutions to the on-board system exceptions.
  • the knowledge base can be stored in the server.
  • the vehicle-mounted device can send the collected raw data or processed data to the server.
  • the abnormal stack information may include abnormal status information and abnormal program identification. According to the exception stack information, the exception log information corresponding to the exception stack information can be determined.
  • the exception identification information may be obtained based on exception stack information and exception log information.
  • the abnormal stack information and the abnormal log information can be compressed and mapped to obtain the abnormal identification information.
  • the exception identification information may include all or part of the exception stack information and the exception log information.
  • the exception log information used to determine the exception identification information may be, for example, the last log information in the log corresponding to the exception stack information.
  • step S205 is performed.
  • step S205 the processing result corresponding to the abnormal identification information is fed back to the user.
  • the processing result is sent to the in-vehicle equipment or user equipment.
  • step S206 is performed.
  • step S206 manual analysis. Perform manual positioning to determine the processing result corresponding to the abnormal identification information.
  • the structural relationship of the on-board system can be combined to analyze and locate the root cause of the abnormality in the on-board system, determine the faulty unit, and provide specific solutions. According to the failed unit, combined with the structural relationship of the on-board system, one or more programs that are affected can be determined.
  • the processing result corresponding to the abnormal identification information may include one or more of the cause of the abnormality of the vehicle-mounted system, the solution, and the determination of the affected program.
  • step S207 the manually determined abnormal identification information and the corresponding relationship between the processing results are added to the abnormal problem database of the knowledge base, and the knowledge base is updated.
  • Step S205 may be performed after step S206, and the manually determined processing result is sent to the user equipment or the vehicle-mounted device. Alternatively, step S205 may be performed after step S207, and the server sends the processing result.
  • steps S201-S207 when there is an abnormality in the on-board system, the processing result can be automatically provided to solve the problem in the on-board system, and the problem that requires maintenance personnel to locate near-end is solved, and no manual is required for the same abnormal situation in the on-board system. Repeat processing to save time and improve user experience.
  • the method for processing anomaly of an in-vehicle system uses anomaly monitoring and user-triggered methods to collect information of an in-vehicle system, and handles the abnormal situation on the server in combination with a knowledge base, and determines the processing result. Construct a knowledge base based on the processing results provided by the maintenance personnel for the abnormality of the on-board system. For the same problem, automatically search the knowledge base to generate processing results.
  • the method for handling abnormalities of the vehicle system provided by the embodiments of the present application can be applied to a variety of operating systems and is flexible to use; it can automatically provide processing results and reduce manual intervention; by updating the knowledge base, manual repetitive processing is not required, which reduces labor costs and improves Processing efficiency.
  • a computer system it usually includes four levels: hardware system, system software, support system, and application software.
  • the hardware system refers to the physical equipment that constitutes the computer, that is, the physical components that are composed of mechanical, optical, electrical, and magnetic devices with calculation, control, storage, input and output functions.
  • System software refers to the system that controls and coordinates computers and external equipment, and supports the development and operation of application software.
  • the support system can also be called a decision support system. It is a computer application system that assists decision makers to make semi-structured or unstructured decision-making through human-computer interaction through data, models and knowledge.
  • Application software corresponds to the system software. It is a collection of various programming languages that users can use and application programs compiled in various programming languages. It is divided into application software packages and user programs. An application software package is a collection of programs designed to solve a certain type of problem by using a computer for multi-user use.
  • the above method can be realized by executing the program on the vehicle client and server.
  • the programs that implement the embodiments of the present application may run at the application software layer or other layers in the computer system.
  • Fig. 5 is a schematic diagram of a system for processing an abnormality of a vehicle-mounted system provided by an embodiment of the present application.
  • the system can be used to implement the method shown in FIG. 2 or FIG. 3.
  • the vehicle-mounted client includes a processing module and a vehicle-mounted communication module.
  • the vehicle client may include the vehicle system, or the vehicle client and the vehicle system may be two independent devices.
  • the processing module can be used for process monitoring, information collection, and information desensitization.
  • Process monitoring that is, monitoring the status of the on-board system to determine whether there is an abnormality.
  • Information collection is the collection of information from the vehicle-mounted system. For example: exception log information, exception stack information, etc.
  • Information desensitization is to desensitize the collected information to protect user privacy.
  • the vehicle-mounted communication module is used to communicate with the server and transmit data.
  • the server includes a storage module, a processing module, and a communication module.
  • the storage module is used for the knowledge base.
  • the knowledge base may include a first mapping relationship, and the first mapping relationship records corresponding relationships between a plurality of abnormal identification information and a plurality of processing results.
  • the knowledge base may include a second mapping relationship, and the second mapping relationship includes indicating an association relationship between a plurality of failure units and a plurality of programs.
  • the processing result includes an exception handling suggestion and/or an exception cause, and the exception cause is used to indicate the faulty unit.
  • the processing module is used for information processing.
  • the processing module can process according to the received abnormal identification information sent by the vehicle-mounted client, combined with the knowledge base, and determine the processing result.
  • the processing module can determine the program affected by the faulty unit according to the cause of the abnormality.
  • the communication module is used for: Mainly responsible for notifying the user of the solution. For example: through APP, SMS, email, etc.
  • the communication module of the server is used for communication and data transmission with the vehicle-mounted client and user equipment.
  • the communication module of the server can receive the abnormal identification information sent by the vehicle-mounted client.
  • the communication module of the server may send instruction information to the vehicle-mounted client, and the instruction information is used to instruct the vehicle-mounted client to obtain the program identifier of the first program.
  • the communication module of the server can send the processing result and/or impact information to the user equipment, and the impact information is used to indicate the program affected by the faulty unit.
  • APP application
  • FIG. 6 is a schematic structural diagram of a device for processing an abnormality of an in-vehicle system provided by an embodiment of the present application.
  • the device 500 includes an acquisition module 501 and a transceiver module 502.
  • the obtaining module 501 is configured to obtain the program identifier of the first program, the first program being a program that runs abnormally;
  • the transceiver module 502 is configured to send a processing request to the server, where the processing request is used to instruct the server to determine the first processing result corresponding to the first abnormal identification information according to the first mapping relationship, and the processing request carries First abnormality identification information, where the first abnormality identification information includes the program identification of the first program, the first mapping relationship records the correspondence between a plurality of abnormal identification information and a plurality of processing results, and each abnormal identification information Include a program logo.
  • the code of the first program includes a program identifier of the first program.
  • the obtaining module 501 is configured to obtain exception stack information, where the exception stack information includes the program identifier of the first program.
  • the program identifier of the first program is written into the first memory space allocated to the first program, and the code of the first program includes the first program A program identifier of a program, and the exception stack information is determined according to the first memory space.
  • each abnormality identification information further includes at least one of the following parameters: abnormal log information, abnormal state information, resource occupation information, the abnormal log information is obtained according to the log corresponding to the first program, the The abnormal state information is used to indicate at least one of the following abnormal states: the on-board system memory overflows, the on-board system memory address is wrong, the on-board system program is abnormal, and the resource occupation information is used to indicate the resource occupation of the on-board system happening.
  • the transceiver module 502 is further configured to receive a processing response sent by the server, where the processing response includes the first processing result.
  • the first processing result includes a first abnormal cause, and the first abnormal cause is used to indicate a first faulty unit in the in-vehicle system,
  • the transceiver module 502 is further configured to receive a processing response sent by the server, where the processing response includes impact information, and the impact information is used to indicate a second program that is indicated by the second mapping relationship and the second program.
  • the second mapping relationship includes indicating the association relationship between a plurality of failure units and a plurality of programs.
  • the device further includes a determining module, configured to determine that an abnormal condition is satisfied to determine that the on-board system is abnormal, and the abnormal condition includes:
  • the in-vehicle client receives instruction information, where the instruction information is used to instruct the in-vehicle client to obtain the program identifier of the first program; and/or,
  • At least one of the following abnormal states in the on-board system is detected: the on-board system memory overflows, the on-board system memory address is wrong, and the on-board system program is abnormal.
  • FIG. 7 is a schematic structural diagram of a device for processing an abnormality of an in-vehicle system provided by an embodiment of the present application.
  • the device 600 includes a transceiver module 601 and a determination module 602.
  • the transceiver module 601 is configured to receive a processing request sent by a vehicle-mounted client, the processing request carries first abnormality identification information, the first abnormality identification information includes the program identification of the first program, and the first program is running abnormally program;
  • the determining module 602 is configured to determine a first processing result corresponding to the first abnormal identification information according to a first mapping relationship, where the first mapping relationship records the correspondence between multiple abnormal identification information and multiple processing results, each An exception identification information includes a program identification.
  • the code of the first program includes a program identifier of the first program.
  • each abnormality identification information further includes at least one of the following parameters: abnormal log information, abnormal state information, resource occupation information, the abnormal log information is obtained according to the log corresponding to the first program, the The abnormal state information is used to indicate at least one of the following abnormal states: the on-board system memory overflows, the on-board system memory address is wrong, the on-board system program is abnormal, and the resource occupation information is used to indicate the resource occupation of the on-board system happening.
  • the transceiver module 601 is further configured to send a processing response to the in-vehicle client or user equipment corresponding to the in-vehicle client, where the processing response includes the first processing result.
  • the first processing result includes a first abnormal cause, and the first abnormal cause is used to indicate a first faulty unit in the in-vehicle system,
  • the determining module 602 is further configured to determine a second program associated with the first faulty unit according to a second mapping relationship, where the second mapping relationship includes indicating an association relationship between multiple faulty units and multiple programs.
  • the transceiver module 601 is further configured to send a processing response to the vehicle client or user equipment corresponding to the vehicle client, where the processing response includes impact information, and the impact information is used to indicate the second Two procedures.
  • the transceiver module 601 is further configured to send instruction information to the vehicle client, where the instruction information is used to instruct the vehicle client to send the processing request to the server.
  • FIG. 8 is a schematic structural diagram of a device for processing an abnormality of an in-vehicle system provided by an embodiment of the present application.
  • the device 700 includes a processor 701 and a communication interface 702.
  • the processor 701 is configured to obtain a program identifier of a first program, where the first program is a program that runs abnormally;
  • the communication interface 702 is configured to send a processing request to the server, where the processing request is used to instruct the server to determine the first processing result corresponding to the first abnormal identification information according to the first mapping relationship, and the processing request carries First abnormality identification information, where the first abnormality identification information includes the program identification of the first program, the first mapping relationship records the correspondence between a plurality of abnormal identification information and a plurality of processing results, and each abnormal identification information Include a program logo.
  • the code of the first program includes a program identifier of the first program.
  • the processor 701 is configured to obtain exception stack information, where the exception stack information includes the program identifier of the first program.
  • the program identifier of the first program is written into the first memory space allocated to the first program, and the code of the first program includes the first program A program identifier of a program, and the exception stack information is determined according to the first memory space.
  • each abnormality identification information further includes at least one of the following parameters: abnormal log information, abnormal state information, resource occupation information, the abnormal log information is obtained according to the log corresponding to the first program, the The abnormal state information is used to indicate at least one of the following abnormal states: the on-board system memory overflows, the on-board system memory address is wrong, the on-board system program is abnormal, and the resource occupation information is used to indicate the resource occupation of the on-board system happening.
  • the communication interface 702 is further configured to receive a processing response sent by the server, where the processing response includes the first processing result.
  • the first processing result includes a first abnormal cause, and the first abnormal cause is used to indicate a first faulty unit in the in-vehicle system,
  • the communication interface 702 is further configured to receive a processing response sent by the server, where the processing response includes impact information, and the impact information is used to indicate a second program that is indicated by the second mapping relationship and the second program.
  • the second mapping relationship includes indicating the association relationship between a plurality of failure units and a plurality of programs.
  • the processor 701 is further configured to determine that an abnormal condition is satisfied to determine that the on-board system is abnormal, and the abnormal condition includes:
  • the in-vehicle client receives instruction information, where the instruction information is used to instruct the in-vehicle client to obtain the program identifier of the first program; and/or,
  • At least one of the following abnormal states in the on-board system is detected: the on-board system memory overflows, the on-board system memory address is wrong, and the on-board system program is abnormal.
  • FIG. 9 is a schematic structural diagram of a device for processing an abnormality of an in-vehicle system provided by an embodiment of the present application.
  • the device 800 includes a processor 801 and a communication interface 802.
  • the communication interface 802 is configured to receive a processing request sent by a vehicle-mounted client, the processing request carries first abnormality identification information, the first abnormality identification information includes the program identification of the first program, and the first program is running abnormally program;
  • the processor 801 is configured to determine a first processing result corresponding to the first abnormal identification information according to a first mapping relationship, where the first mapping relationship records the correspondence between multiple abnormal identification information and multiple processing results, each An exception identification information includes a program identification.
  • the code of the first program includes a program identifier of the first program.
  • each abnormality identification information further includes at least one of the following parameters: abnormal log information, abnormal state information, resource occupation information, the abnormal log information is obtained according to the log corresponding to the first program, the The abnormal state information is used to indicate at least one of the following abnormal states: the on-board system memory overflows, the on-board system memory address is wrong, the on-board system program is abnormal, and the resource occupation information is used to indicate the resource occupation of the on-board system happening.
  • the communication interface 802 is further configured to send a processing response to the in-vehicle client or user equipment corresponding to the in-vehicle client, where the processing response includes the first processing result.
  • the first processing result includes a first abnormal cause, and the first abnormal cause is used to indicate a first faulty unit in the on-board system,
  • the processor 801 is further configured to determine a second program associated with the first faulty unit according to a second mapping relationship, where the second mapping relationship includes indicating an association relationship between multiple faulty units and multiple programs.
  • the communication interface 802 is further configured to send a processing response to the in-vehicle client or user equipment corresponding to the in-vehicle client, where the processing response includes impact information, and the impact information is used to indicate the second Two procedures.
  • the communication interface 802 is further configured to send instruction information to the vehicle-mounted client, where the instruction information is used to instruct the vehicle-mounted client to send the processing request to the server.
  • the embodiment of the present application also provides a vehicle-mounted system exception processing system, including the vehicle-mounted client and server described above.
  • An embodiment of the present application also provides a computer program storage medium, which is characterized in that the computer program storage medium has program instructions, and when the program instructions are directly or indirectly executed, the foregoing method can be realized.
  • An embodiment of the present application further provides a chip system, characterized in that the chip system includes at least one processor, and when the program instructions are executed in the at least one processor, the foregoing method can be realized.
  • At least one refers to one or more
  • multiple refers to two or more.
  • And/or describes the association relationship of the associated objects, indicating that there can be three types of relationships, for example, A and/or B, which can mean the situation where A exists alone, A and B exist at the same time, and B exists alone. Among them, A and B can be singular or plural.
  • the character “/” generally indicates that the associated objects before and after are in an “or” relationship.
  • the following at least one item” and similar expressions refer to any combination of these items, including any combination of single items or plural items.
  • At least one of a, b, and c can represent: a, b, c, a-b, a-c, b-c, or a-b-c, where a, b, and c can be single or multiple.
  • the disclosed system, device, and method may be implemented in other ways.
  • the device embodiments described above are merely illustrative, for example, the division of the units is only a logical function division, and there may be other divisions in actual implementation, for example, multiple units or components may be combined or It can be integrated into another system, or some features can be ignored or not implemented.
  • the displayed or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, devices or units, and may be in electrical, mechanical or other forms.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the objectives of the solutions of the embodiments.
  • the functional units in the various embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units may be integrated into one unit.
  • the function is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer readable storage medium.
  • the technical solution of the present application essentially or the part that contributes to the existing technology or the part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including Several instructions are used to make a computer device (which may be a personal computer, a server, or a network device, etc.) execute all or part of the steps of the methods described in the various embodiments of the present application.
  • the aforementioned storage media include: U disk, mobile hard disk, read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), magnetic disk or optical disk and other media that can store program code .

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • General Engineering & Computer Science (AREA)
  • Quality & Reliability (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Health & Medical Sciences (AREA)
  • Biomedical Technology (AREA)
  • Computer Hardware Design (AREA)
  • Debugging And Monitoring (AREA)

Abstract

一种车载系统异常处理的方法，包括：车载客户端获取第一程序的程序标识，第一程序是运行异常的程序；车载客户端向服务端发送处理请求，处理请求用于指示服务端根据第一映射关系确定与第一异常标识信息对应的第一处理结果，处理请求携带第一异常标识信息，第一异常标识信息包括第一程序的程序标识，第一映射关系记录有多个异常标识信息与多个处理结果的对应关系，每个异常标识信息包括一个程序标识。根据车载客户端确定的车载系统中运行异常的程序，可以确定该异常对应的处理结果，从而避免人工重复处理。

Description

车载系统异常处理的方法及装置
本申请要求于2019年9月12日提交中国专利局、申请号为201910866626.3、申请名称为“车载系统异常处理的方法及装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及车载系统技术领域，尤其涉及一种车载系统异常处理的方法及装置。
背景技术
随着智能车技术的不断发展，越来越多的汽车安装了包括智能娱乐系统等的车载系统。车载系统能够实现很多功能以满足人们的需求，系统复杂。当车载系统出现异常时，需要用户把车辆开到维修店，由工程师近端检查，从而对异常进行问题的定位，确定异常出现的原因，费时费力用户体验较差。一方面发生问题时，问题定位需要由人工进行，实时性差、操作繁琐等问题日益突出；另一方面，同一个问题需要人工重复定位，浪费人力、物力。
发明内容
本申请提供一种车载系统异常处理的方法，能够根据车载系统中运行异常的程序的程序标识，给出异常处理建议或异常原因，避免了人工处理，节约人力成本。
第一方面，提供一种车载系统异常处理的方法，所述方法包括：车载客户端获取第一程序的程序标识，所述第一程序是运行异常的程序；所述车载客户端向服务端发送处理请求，所述处理请求用于指示所述服务端根据第一映射关系确定与所述第一异常标识信息对应的第一处理结果，所述处理请求携带第一异常标识信息，所述第一异常标识信息包括所述第一程序的程序标识，所述第一映射关系记录有多个异常标识信息与多个处理结果的对应关系，每个异常标识信息包括一个程序标识。
在车载系统出现异常时，根据第一异常标识信息，第一异常标识信息包含车载系统中运行异常的程序的程序标识，请求服务端确定与第一异常标识信息对应的第一处理结果，避免了人工处理，节约人力成本。
应当理解，车载客户端可以根据所述第一程序的程序标识生成第一异常标识信息，车载客户端可以向服务端发送处理请求，所述处理请求携带所述第一异常标识信息，所述处理请求用于指示所述服务端确定与所述第一异常标识信息对应的第一处理结果。
结合第一方面，在一些可能的实现方式中，所述第一程序的代码中包括所述第一程序的程序标识。
通过将第一程序的程序标识写入第一程序的代码中，降低车载客户端获取第一程序的程序标识的难度，减小系统开销。
结合第一方面，在一些可能的实现方式中，车载客户端获取第一程序的程序标识，包括：所述车载客户端获取异常堆栈信息，所述异常堆栈信息包括所述第一程序的程序标识。
通过异常堆栈信息，获取第一程序的程序标识，简单易实现，降低车载客户端获取第一程序的程序标识的难度，减小系统开销。
结合第一方面，在一些可能的实现方式中，当所述第一程序运行时，所述第一程序的程序标识被写入被分配所述第一程序的第一内存空间中，所述第一程序的代码中包括所述第一程序的程序标识，所述异常堆栈信息是根据所述第一内存空间确定的。
结合第一方面，在一些可能的实现方式中，每个异常标识信息还包括以下参数中的至少一个：异常日志信息、异常状态信息、资源占用信息，所述异常日志信息是根据所述第一程序对应的日志得到的，所述异常状态信息用于指示以下异常状态中的至少一种：所述车载系统内存溢出、所述车载系统内存地址错误、车载系统程序异常，所述资源占用信息用于指示所述车载系统的资源占用情况。
异常标识信息包括异常日志信息、异常状态信息、资源占用信息中的至少一种，可以使得处理结果更加准确。
结合第一方面，在一些可能的实现方式中，所述方法还包括：所述车载客户端接收所述服务端发送的处理响应，所述处理响应包括所述第一处理结果。
通过车载客户端接收第一处理结果，接收到服务端对车载系统异常的处理结果进行了反馈。
结合第一方面，在一些可能的实现方式中，所述第一异常处理结果包括第一异常处理建议、第一异常原因、影响信息中的至少一种，所述第一异常原因用于指示所述车载系统中的第一故障单元，所述影响信息用于指示受到影响的第二程序。
结合第一方面，在一些可能的实现方式中，所述第一处理结果包括第一异常原因，所述第一异常原因用于指示所述车载系统中的第一故障单元，所述方法还包括：所述车载客户端接收所述服务端发送的处理响应，所述处理响应包括影响信息，所述影响信息用于指示第二程序，所述第二程序是第二映射关系指示的与所述第一故障单元关联的程序，所述第二映射关系包括指示多个故障单元与多个程序之间的关联关系。
当一个单元出现故障时，可能有多个程序的运行受到影响。将受到故障单元影响的程序进行反馈，用户可以提前做好应对措施，提高用户体验。
结合第一方面，在一些可能的实现方式中，所述方法还包括：所述车载客户端确定满足异常条件，以确定所述车载系统出现异常，所述异常条件包括：所述车载客户端接收到指示信息，所述指示信息用于指示所述车载客户端获取第一程序的程序标识；和/或，检测到所述车载系统出现以下异常状态中的至少一种：所述车载系统内存溢出、所述车载系统内存地址错误、车载系统程序异常。
通过异常监控和用户主动触发两种方式及时采集系统信息，解决了发生问题时信息收集不及时的问题。
第二方面，提供一种车载系统异常处理的方法，所述方法包括：服务端接收车载客户端发送的处理请求，所述处理请求携带第一异常标识信息，所述第一异常标识信息包括第一程序的程序标识，所述第一程序是运行异常的程序；
所述服务端根据第一映射关系确定与所述第一异常标识信息对应的第一处理结果，所述第一处理结果包括第一异常处理建议和/或第一异常原因，所述第一映射关系记录有多 个异常标识信息与多个处理结果的对应关系，每个异常标识信息包括一个程序标识，每个处理结果包括异常处理建议和/或异常原因。
在车载系统出现异常时，服务端根据第一异常标识信息，第一异常标识信息包含运行异常的程序的程序标识，确定与第一异常标识信息对应的第一处理结果，第一处理结果包括第一异常处理建议和/或第一异常原因，避免了人工处理，节约人力成本。
结合第二方面，在一些可能的实现方式中，所述第一程序的代码中包括所述第一程序的程序标识。
通过将第一程序的程序标识写入第一程序的代码中，降低车载客户端获取第一程序的程序标识的难度，减小系统开销。
结合第二方面，在一些可能的实现方式中，每个异常标识信息还包括以下参数中的至少一个：异常日志信息、异常状态信息、资源占用信息，所述异常日志信息是根据所述第一程序对应的日志得到的，所述异常状态信息用于指示以下异常状态中的至少一种：所述车载系统内存溢出、所述车载系统内存地址错误、车载系统程序异常，所述资源占用信息用于指示所述车载系统的资源占用情况。
异常标识信息包括异常日志信息、异常状态信息、资源占用信息中的至少一种，可以使得处理结果更加准确。
结合第二方面，在一些可能的实现方式中，所述方法还包括：所述服务端向所述车载客户端或与所述车载客户端对应的用户设备发送处理响应，所述处理响应包括所述第一处理结果。
通过发送第一处理结果，服务端对车载系统异常的处理结果进行了反馈。
结合第二方面，在一些可能的实现方式中，所述第一异常处理结果包括第一异常处理建议、第一异常原因、影响信息中的至少一种，所述第一异常原因用于指示所述车载系统中的第一故障单元，所述影响信息用于指示受到影响的第二程序。
结合第二方面，在一些可能的实现方式中，所述第一处理结果包括第一异常原因，所述第一异常原因用于指示所述车载系统中的第一故障单元，所述方法还包括：所述服务端根据第二映射关系确定与所述第一故障单元关联的第二程序，所述第二映射关系包括指示多个故障单元与多个程序之间的关联关系。
当一个单元出现故障时，可能有多个程序的运行受到影响。确定故障单元影响的程序进行反馈，可以提前做好应对措施，提高用户体验。
结合第二方面，在一些可能的实现方式中，所述方法还包括：所述服务端向所述车载客户端或与所述车载客户端对应的用户设备发送处理响应，所述处理响应包括影响信息，所述影响信息用于指示所述第二程序。
当一个单元出现故障时，可能有多个程序的运行受到影响。将受到故障单元影响的程序进行反馈，用户可以提前做好应对措施，提高用户体验。
结合第二方面，在一些可能的实现方式中，所述方法还包括：所述服务端向所述车载客户端发送指示信息，所述指示信息用于指示所述车载客户端向所述服务端发送所述处理请求。
通过用户主动触发两种方式及时采集系统信息，解决了发生问题时信息收集不及时的问题。
第三方面，提供一种车载系统异常处理装置，其特征在于，包括：获取模块，用于获 取第一程序的程序标识，所述第一程序是运行异常的程序；收发模块，用于向服务端发送处理请求，所述处理请求用于指示所述服务端根据第一映射关系确定与所述第一异常标识信息对应的第一处理结果，所述第一处理结果包括第一异常处理建议和/或第一异常原因，所述处理请求携带第一异常标识信息，所述第一异常标识信息包括所述第一程序的程序标识，所述第一映射关系记录有多个异常标识信息与多个处理结果的对应关系，每个异常标识信息包括一个程序标识，每个处理结果包括异常处理建议和/或异常原因。
结合第三方面，在一些可能的实现方式中，所述第一程序的代码中包括所述第一程序的程序标识。
结合第三方面，在一些可能的实现方式中，所述获取模块用于，获取异常堆栈信息，所述异常堆栈信息包括所述第一程序的程序标识。
结合第三方面，在一些可能的实现方式中，当所述第一程序运行时，所述第一程序的程序标识被写入被分配所述第一程序的第一内存空间中，所述第一程序的代码中包括所述第一程序的程序标识，所述异常堆栈信息是根据所述第一内存空间确定的。
结合第三方面，在一些可能的实现方式中，每个异常标识信息还包括以下参数中的至少一个：异常日志信息、异常状态信息、资源占用信息，所述异常日志信息是根据所述第一程序对应的日志得到的，，所述异常状态信息用于指示以下异常状态中的至少一种：所述车载系统内存溢出、所述车载系统内存地址错误、车载系统程序异常，所述资源占用信息用于指示所述车载系统的资源占用情况。
结合第三方面，在一些可能的实现方式中，所述收发模块还用于，接收所述服务端发送的处理响应，所述处理响应包括所述第一处理结果。
结合第三方面，在一些可能的实现方式中，所述第一异常处理结果包括第一异常处理建议、第一异常原因、影响信息中的至少一种，所述第一异常原因用于指示所述车载系统中的第一故障单元，所述影响信息用于指示受到影响的第二程序。
结合第三方面，在一些可能的实现方式中，所述第一处理结果包括第一异常原因，所述第一异常原因用于指示所述车载系统中的第一故障单元，所述收发模块还用于，接收所述服务端发送的处理响应，所述处理响应包括影响信息，所述影响信息用于指示第二程序，所述第二程序是第二映射关系指示的与所述第一故障单元关联的程序，所述第二映射关系包括指示多个故障单元与多个程序之间的关联关系。
结合第三方面，在一些可能的实现方式中，所述装置还包括确定模块，用于确定满足异常条件，以确定所述车载系统出现异常，所述异常条件包括：所述车载客户端接收到指示信息，所述指示信息用于指示所述车载客户端获取第一程序的程序标识；和/或，检测到所述车载系统出现以下异常状态中的至少一种：所述车载系统内存溢出、所述车载系统内存地址错误、车载系统程序异常。
第四方面，提供一种车载系统异常处理装置，包括：收发模块，用于接收车载客户端发送的处理请求，所述处理请求携带第一异常标识信息，所述第一异常标识信息包括第一程序的程序标识，所述第一程序是运行异常的程序；确定模块，用于根据第一映射关系确定与所述第一异常标识信息对应的第一处理结果，所述第一处理结果包括第一异常处理建议和/或第一异常原因，所述第一映射关系记录有多个异常标识信息与多个处理结果的对应关系，每个异常标识信息包括一个程序标识，每个处理结果包括异常处理建议和/或异常原因。
结合第四方面，在一些可能的实现方式中，所述第一程序的代码中包括所述第一程序的程序标识。
结合第四方面，在一些可能的实现方式中，每个异常标识信息还包括以下参数中的至少一个：异常日志信息、异常状态信息、资源占用信息，所述异常日志信息是根据所述第一程序对应的日志得到的，所述异常状态信息用于指示以下异常状态中的至少一种：所述车载系统内存溢出、所述车载系统内存地址错误、车载系统程序异常，所述资源占用信息用于指示所述车载系统的资源占用情况。
结合第四方面，在一些可能的实现方式中，所述收发模块还用于，向所述车载客户端或与所述车载客户端对应的用户设备发送处理响应，所述处理响应包括所述第一处理结果。
结合第四方面，在一些可能的实现方式中，所述第一异常处理结果包括第一异常处理建议、第一异常原因、影响信息中的至少一种，所述第一异常原因用于指示所述车载系统中的第一故障单元，所述影响信息用于指示受到影响的第二程序。
结合第四方面，在一些可能的实现方式中，所述第一处理结果包括第一异常原因，所述第一异常原因用于指示所述车载系统中的第一故障单元，所述确定模块还用于，根据第二映射关系确定与所述第一故障单元关联的第二程序，所述第二映射关系包括指示多个故障单元与多个程序之间的关联关系。
结合第四方面，在一些可能的实现方式中，所述收发模块还用于，向所述车载客户端或与所述车载客户端对应的用户设备发送处理响应，所述处理响应包括影响信息，所述影响信息用于指示所述第二程序。
结合第四方面，在一些可能的实现方式中，所述收发模块还用于，向所述车载客户端发送指示信息，所述指示信息用于指示所述车载客户端向所述服务端发送所述处理请求。
第五方面，提供一种车载系统异常处理装置，包括：处理器、通信接口，处理器，用于获取第一程序的程序标识，所述第一程序是运行异常的程序；通信接口，用于向服务端发送处理请求，所述处理请求用于指示所述服务端根据第一映射关系确定与所述第一异常标识信息对应的第一处理结果，所述第一处理结果包括第一异常处理建议和/或第一异常原因，所述处理请求携带第一异常标识信息，所述第一异常标识信息包括所述第一程序的程序标识，所述第一映射关系记录有多个异常标识信息与多个处理结果的对应关系，每个异常标识信息包括一个程序标识，每个处理结果包括异常处理建议和/或异常原因。
结合第五方面，在一些可能的实现方式中，所述第一程序的代码中包括所述第一程序的程序标识。
结合第五方面，在一些可能的实现方式中，处理器用于，获取异常堆栈信息，所述异常堆栈信息包括所述第一程序的程序标识。
结合第五方面，在一些可能的实现方式中，当所述第一程序运行时，所述第一程序的程序标识被写入被分配所述第一程序的第一内存空间中，所述第一程序的代码中包括所述第一程序的程序标识，所述异常堆栈信息是根据所述第一内存空间确定的。
结合第五方面，在一些可能的实现方式中，每个异常标识信息还包括以下参数中的至少一个：异常日志信息、异常状态信息、资源占用信息，所述异常日志信息是根据所述第一程序对应的日志得到的，所述异常状态信息用于指示以下异常状态中的至少一种：所述车载系统内存溢出、所述车载系统内存地址错误、车载系统程序异常，所述资源占用信息 用于指示所述车载系统的资源占用情况。
结合第五方面，在一些可能的实现方式中，通信接口还用于，接收所述服务端发送的处理响应，所述处理响应包括所述第一处理结果。
结合第五方面，在一些可能的实现方式中，所述第一异常处理结果包括第一异常处理建议、第一异常原因、影响信息中的至少一种，所述第一异常原因用于指示所述车载系统中的第一故障单元，所述影响信息用于指示受到影响的第二程序。
结合第五方面，在一些可能的实现方式中，所述第一处理结果包括第一异常原因，所述第一异常原因用于指示所述车载系统中的第一故障单元，通信接口还用于，接收所述服务端发送的处理响应，所述处理响应包括影响信息，所述影响信息用于指示第二程序，所述第二程序是第二映射关系指示的与所述第一故障单元关联的程序，所述第二映射关系包括指示多个故障单元与多个程序之间的关联关系。
结合第五方面，在一些可能的实现方式中，处理器还用于，确定满足异常条件，以确定所述车载系统出现异常，所述异常条件包括：所述车载客户端接收到指示信息，所述指示信息用于指示所述车载客户端获取第一程序的程序标识；和/或，检测到所述车载系统出现以下异常状态中的至少一种：所述车载系统内存溢出、所述车载系统内存地址错误、车载系统程序异常。
第六方面，提供一种车载系统异常处理装置，包括处理器，通信接口。通信接口，用于接收车载客户端发送的处理请求，所述处理请求携带第一异常标识信息，所述第一异常标识信息包括第一程序的程序标识，所述第一程序是运行异常的程序；处理器，用于根据第一映射关系确定与所述第一异常标识信息对应的第一处理结果，所述第一处理结果包括第一异常处理建议和/或第一异常原因，所述第一映射关系记录有多个异常标识信息与多个处理结果的对应关系，每个异常标识信息包括一个程序标识，每个处理结果包括异常处理建议和/或异常原因。
结合第六方面，在一些可能的实现方式中，所述第一程序的代码中包括所述第一程序的程序标识。
结合第六方面，在一些可能的实现方式中，每个异常标识信息还包括以下参数中的至少一个：异常日志信息、异常状态信息、资源占用信息，所述异常日志信息是根据所述第一程序对应的日志得到的，所述异常状态信息用于指示以下异常状态中的至少一种：所述车载系统内存溢出、所述车载系统内存地址错误、车载系统程序异常，所述资源占用信息用于指示所述车载系统的资源占用情况。
结合第六方面，在一些可能的实现方式中，通信接口还用于，向所述车载客户端或与所述车载客户端对应的用户设备发送处理响应，所述处理响应包括所述第一处理结果。
结合第六方面，在一些可能的实现方式中，所述第一异常处理结果包括第一异常处理建议、第一异常原因、影响信息中的至少一种，所述第一异常原因用于指示所述车载系统中的第一故障单元，所述影响信息用于指示受到影响的第二程序。
结合第六方面，在一些可能的实现方式中，所述第一处理结果包括第一异常原因，所述第一异常原因用于指示所述车载系统中的第一故障单元，处理器还用于，根据第二映射关系确定与所述第一故障单元关联的第二程序，所述第二映射关系包括指示多个故障单元与多个程序之间的关联关系。
结合第六方面，在一些可能的实现方式中，通信接口还用于，向所述车载客户端或与 所述车载客户端对应的用户设备发送处理响应，所述处理响应包括影响信息，所述影响信息用于指示所述第二程序。
结合第六方面，在一些可能的实现方式中，通信接口还用于，向所述车载客户端发送指示信息，所述指示信息用于指示所述车载客户端向所述服务端发送所述处理请求。
第七方面，提供一种车载系统异常处理系统，包括上文所述的车载客户端和服务端。
第八方面，提供一种计算机存储介质，当所述计算机指令在电子设备上运行时，使得所述电子设备执行第一方面所述的方法。
第九方面，提供一种计算机存储介质，当所述计算机指令在电子设备上运行时，使得所述电子设备执行第二方面所述的方法。
第十方面，提供一种芯片系统，所述芯片系统包括至少一个处理器，当程序指令在所述至少一个处理器中执行时，使得所述芯片系统执行第一方面所述的方法。
第十一方面，提供一种芯片系统，所述芯片系统包括至少一个处理器，当程序指令在所述至少一个处理器中执行时，使得所述芯片系统执行第二方面所述的方法。
附图说明
图1是一种堆栈信息的格式的示意图。
图2是本申请实施例提供的一种车载系统异常处理的方法的示意性流程图。
图3是本申请实施例提供的另一种车载系统异常处理的方法的示意性流程图。
图4是车载系统的结构关系的示意图。
图5是本申请实施例提供的一种车载系统异常处理的系统的示意图。
图6是本申请实施例提供的一种车载系统异常处理装置的示意性结构图。
图7是本申请实施例提供的另一种车载系统异常处理装置的示意性结构图。
图8是本申请实施例提供的又一种车载系统异常处理装置的示意性结构图。
图9是本申请实施例提供的又一种车载系统异常处理装置的示意性结构图。
具体实施方式
下面将结合附图，对本申请中的技术方案进行描述。
应理解，本发明实施例可以应用各种无线通信方案进行通信，例如：全球移动通讯系统(global system of mobile communication，GSM)，码分多址(code division multiple access，CDMA)系统，宽带码分多址(wideband code division multiple access wireless，WCDMA)系统，通用分组无线业务(general packet radio service，GPRS)系统，长期演进(long term evolution，LTE)系统，无线局域网(wireless local area networks，WLAN)等。
随着自动驾驶技术的发展，用户对车载系统越来越关注，车载系统提供的服务越来越多，系统越来越复杂。在这样复杂的车载系统中，当车载系统出现异常，如何快速定位解决问题变得非常重要。在车载电子系统出现故障时，尚无法通过自动的方式有效确定出现异常的根本原因。
对于linux车载系统，利用linux的核心转储(core dump)技术可以进行异常状态的储存。当检测到车载系统某个程序运行异常时，车载系统输出堆栈信息。通过core dump服务抓取程序异常退出时的堆栈信息。堆栈信息存储着运行异常的程序的内存地址。通过日志管理服务可以抓取运行的程序产生的相应日志。利用超文本传输协议(hypertext  transfer protocol，HTTP)完成与网络服务器的连接、鉴权和通信，实现远程连接和异常日志自动上传，最大限度的将异常出现时的状态第一时间上报。
程序异常退出时，车载系统输出堆栈信息，堆栈信息保存在堆栈中。图1是一种堆栈信息的格式的示意图。在每个堆栈地址中，存储的新科包括异常状态信息，异常退出的程序的内存地址，程序信息，变量参数等。应当理解，图1所示的堆栈信息的格式仅是示例性地，每个堆栈地址可以包括更多或更少的信息。
异常状态信息用于指示车载系统的异常状态。异常状态例如包括内存溢出、内存地址错误、车载系统程序异常等。
变量参数是程序在运行过程中的相关参数，例如程序的输入信息等。
程序信息例如可以是程序的名称、功能等。由于程序信息未进行统一定义，无法通过程序信息准确确定运行异常的程序。
程序在车载系统中运行，车载系统每次为同一程序分配的内存空间并不相同。因此，需要维护人员根据程序的内存地址，查看内存，确定出现故障时运行的程序，从而确定该程序的功能等。结合日志信息，可以确定出现故障的原因，从而提供解决方案。
另外，上述方式没有主动采集功能，当监控服务自身出现异常时，就无法进行日志采集。
另一种车载系统异常处理的方法，利用看门狗技术、状态校验技术获知车载系统是否出现异常。异常信息包括死机、重启、操作无响应。当采集到的异常信息时，记录车载系统的日志，并将异常信息和记录的日志信息发送到用户指定的邮箱。
日志信息维护人员根据日志信息，确定生成所述日志对应的出现故障时运行的程序，从而确定该程序的功能等。结合日志信息，可以确定出现故障的原因，从而提供解决方案。
由于车载系统复杂，对于采集的信息仍需要通过人工处理以进行问题的定位，确定造成车载系统异常的原因，并提供解决方案。对车载系统异常的处理，依赖于人工，效率较低。
为了解决上述问题，本申请实施例提供了一种车载系统异常处理的方法。
图2是本申请实施例提供的一种车载系统异常处理的方法的示意性流程图。车载系统例如可以是车载娱乐系统(in-vehicle infotainment，IVI)等。
在步骤S101，车载客户端获取第一程序的程序标识。第一程序是车载系统中运行异常的程序。
车载系统对运行的进程进行监控。当监控到异常状态时，车载系统将运行异常的程序的信息保存在堆栈中。异常状态例如可以包括以下状态中的至少一种：所述车载系统内存溢出、所述车载系统内存地址错误、车载系统程序异常等。
内存溢出即内存不足，内存大小不能够满足程序运行对内存空间的需求。
内存地址错误也可以称为段错误，程序访问的内存超出了车载系统为该程序分配的内存空间，例如程序访问了不存在的内存地址、访问了车载系统保护的内存地址、访问了只读的内存地址等等情况。
车载系统程序异常可以包括以下状态中的至少一种：车载系统程序死锁、车载系统程序异常退出等。程序死锁是指两个或两个以上的进程在执行过程中，由于竞争资源或者由于彼此通信而造成的一种阻塞的现象，若无外力作用，它们都将无法推进下去。
车载系统程序异常的情况，第一程序可以是该异常的程序。
或者当用户发现车载系统运行出现异常时，可以指示车载客户端采集与运行的程序相关的信息。车载系统获取指示信息，所述指示信息用于指示所述车载系统将与运行异常的程序即第一程序相关的信息保存在堆栈中。将第一程序相关的信息保存在堆栈中，即在堆栈中输出第一程序相关的信息。用户可以在车载客户端或车载系统中输入指示信息，用户也可以通过其他用户设备向车载系统发送指示信息，用户还可以通过用户设备向车载服务端发送请求信息，请求信息用于请求车载服务端向车载客户端设备或车载系统发送该指示信息。车载客户端可以将该指示信息发送至车载系统。在一些实施例中，车载系统可以是车载客户端的一部分，或者，车载客户端可以是车载系统的一部分。
在一些情况下，用户感知车载系统出现异常时，但车载客户端未及时获取运行异常的程序的程序标识，用户可以指示车载客户端获取运行异常的程序的程序标识，从而及时对车载系统的异常情况进行处理。
也就是说，车载客户端确定满足异常条件，以确定所述车载系统出现异常，所述异常条件包括：所述车载客户端接收到指示信息，所述指示信息用于指示所述车载客户端获取第一程序的程序标识；和/或，检测到所述车载系统出现以下异常状态中的至少一种：所述车载系统内存溢出、所述车载系统内存地址错误、车载系统程序异常。该指示信息还可以用于指示车载客户端向服务端发送所述处理请求。车载系统程序异常可以表现为车载系统内存溢出和/或车载系统内存地址错误等。车载系统出现异常状态中的至少一种时，确定出现异常的第一程序，并输出堆栈信息。车载客户端可以根据对车载系统的检测，确定满足异常条件，也可以对车载系统输出的堆栈信息进行检测，以确定车载系统程序异常，从而确定满足异常条件。对车载客户端车载系统输出的堆栈信息进行检测，也可以理解为对车载系统程序异常的检测。
通过异常监控和用户主动触发两种方式，能够及时采集车载系统异常情况下的信息，从而尽快进行处理，提高用户体验。
车载客户端采集的信息可以包括第一程序的程序标识。车载客户端采集的信息还可以包括异常日志信息、异常状态信息、资源占用信息等中的一种或多种。
当车载系统出现异常时，车载系统输出异常堆栈信息，异常堆栈信息保存在堆栈中。当车载系统出现异常时，车载系统将与该异常相关的信息写入堆栈中。异常堆栈信息可以包括保存在堆栈中的全部或部分信息。保存在堆栈中的信息可以参见图1。
车载系统运行时，调用的程序存储在内存中。也就是说，当所述第一程序运行时，所述第一程序的程序被写入为所述第一程序分配的第一内存空间中。
在程序的代码开发时，可以在程序中写入程序标识。程序标识用于标识不同的程序。
可以定义车载系统对堆栈信息的打印规则，即定义保存在堆栈中的信息的格式。也可以定义异常堆栈信息的格式。第一程序是运行异常的程序。车载系统输出的堆栈信息可以包括第一程序的程序标识。参见图2所示的车载系统输出的堆栈信息，程序信息可以包括运行异常的程序的程序标识，或者，可以在堆栈信息中增加新的字段，运行异常的程序的程序标识作为该字段的信息。因此，第一程序对应的的异常堆栈信息可以包括第一程序的程序标识。车载系统输出的对应于第一程序的堆栈信息可以包括第一程序在内存中的地址。当监控到异常状态时，车载系统输出的对应于第一程序的堆栈信息可以包括异常状态信息，异常状态信息用于指示出现的异常状态。车载客户端可以获取异常堆栈信息，从而获取第一程序的程序标识。
车载客户端可以确定运行异常的程序对应的日志，即第一程序对应的日志。日志即车载系统的运行痕迹。根据运行异常的程序对应的日志记载的信息可以获得异常日志信息。异常日志信息可以包括运行异常的程序对应的日志记载的信息中的全部或部分内容。例如，异常日志信息可以是对运行异常的程序对应的日志记载的信息进行信息脱敏得到的。信息脱敏，即对采集的信息进行脱敏操作，保护用户隐私。
可以定义日志的格式。当程序的代码中包括程序标识，该程序对应的日志中可以包括该程序的程序标识。即，第一程序对应的异常日志信息中可以包括第一程序的程序标识。车载客户端可以获取异常日志信息，从而获取第一程序的程序标识。
或者，车载客户端可以确定第一程序在外部存储器中的地址，第一程序在外部存储器中的地址也可以称为第一程序的存储地址。例如根据异常堆栈信息中第一程序在内存中的地址，确定第一程序。车载客户端可以遍历外部存储器，从而确定第一程序的存储地址，即第一程序在外部存储器中的地址。车载客户端可以将第一程序的存储地址作为第一程序的程序标识。
对于人工进行异常处理的情况，根据车载系统的日志以及对应的程序，可以通过人工确定出现异常的原因，从而给出异常处理建议。
而对于相同的程序，导致同一异常状态的原因可能相同。因此，在人工对异常情况处理之后，可以确定异常状态标识与处理结果的一一对应关系。当然，对于相同的程序，导致异常状态的原因也可能不同，对于同一程序，异常状态标识可以对应于多个处理结果。
异常标识信息可以是根据程序标识确定的，或者异常标识信息可以是根据异常日志信息、异常状态信息、资源占用信息中的至少一个以及程序标识确定的。第一异常标识信息可以包括第一程序的程序标识。第一异常标识信息中的第一程序的程序标识可以与异常日志信息或异常堆栈信息中的第一程序的程序标识相同或不同。第一异常标识信息中的第一程序的程序标识可以是对异常日志信息或异常堆栈信息中的第一程序的程序标识进行映射如进行压缩映射得到的。
资源占用信息也可以称为操作系统信息，可以包括硬盘占用信息、句柄信息、内存占用信息、中央处理器(central processing unit，CPU)占用信息等信息中的一种或多种。硬盘占用信息可以用于指示车载系统硬盘占用的情况。句柄信息可以用于指示车载系统中占用的句柄的数量。例如，句柄用于标识车载系统中打开的文件，车载系统可以为每一个打开的文件分配一个句柄。内存占用信息用于指示车载系统的内存整体占用情况。CPU占用信息用于指示车载系统的CPU占用情况。车载客户端可以向车载系统发送个请求消息，该请求消息用于指示车载系统向车载客户端发送资源占用信息。车载系统可以在接收车载客户端发送的该请求消息后向车载客户端发送资源占用信息。车载客户端可以在确定满足异常条件，即确定所述车载系统出现异常时，向车载系统发送该请求消息。车载客户端可以获取车载系统发送的资源占用信息。
异常标识信息包括资源占用信息，服务端可以从车载系统资源的占用情况，确定车载一桶的异常是否是由于资源不足车载系统的资源不足引起异常。进一步地，可以确定是由于哪个或哪些资源不足导致的车载系统异常。
异常标识信息也可以仅仅是根据程序标识确定的。此时，根据异常标识信息，可以确定一个或多个处理结果。该一个或多个处理结果可以是对应于多种异常日志信息的处理结果，或者说，该一个或多个处理结果是程序标识对应的程序运行过程中造成车载系统异常 的一个或多个处理结果。异常标识信息可以包括程序标识，可以理解为，异常标识信息包括程序标识的全部信息，或者，异常标识信息包括对程序标识进行压缩映射的结果。
异常标识信息包括第一程序的程序标识。异常标识信息还可以包括异常状态信息、异常日志信息、资源占用信息中的至少一个。根据异常标识信息可以确定对应的程序。作为一种可能的方式，根据异常标识信息还可以确定对应的异常状态信息、异常日志信息、资源占用信息中的至少一种。
车载客户端获取第一程序的程序标识。车载客户端可以获取异常堆栈信息和/或第一程序对应的日志包含的第一程序的程序标识，车载客户端也可以根据异常堆栈信息确定第一程序的存储地址，车载客户端获取该存储地址，从而获取了第一程序的程序标识。
在步骤S102，车载客户端向服务端发送处理请求。处理请求携带第一异常标识信息，所述第一异常标识信息包括所述第一程序的程序标识。也就是说，处理请求包括第一程序的程序标识。
第一异常标识信息还可以包括异常日志信息和/或异常状态信息。异常状态信息用于指示以下异常状态中的至少一种：所述车载系统内存溢出、所述车载系统内存地址错误、车载系统程序异常。
处理请求用于指示服务端确定与所述第一异常标识信息对应的第一处理结果。
在步骤S103，服务端确定第一处理结果和/或影响信息。第一处理结果可以包括异常处理建议、异常原因影响信息中的至少一种。影响信息用于指示车载系统出现异常时收到影响的第二程序。第二程序可以是与导致车载系统异常的第一故障单元相关联的程序。
服务端可以根据第一映射关系确定与所述第一异常标识信息对应的第一处理结果。
在异常标识信息不包括资源占用信息的情况下，如果处理请求中携带有资源占用信息，服务端可以根据资源占用信息，即车载系统资源的占用情况，确定车载系统的异常是否是由于资源不足车载系统的资源不足导致的，并可以具体判断由于哪个或哪些资源不足导致的车载系统异常。服务端可以在确定异常不是由于资源不足导致的情况下，根据第一映射关系确定与所述第一异常标识信息对应的第一处理结果。
在确定并非由于资源不足车载系统的资源不足导致车载系统异常的情况下，根据第一映射关系确定第一处理结果。
第一映射关系记录有多个异常标识信息与多个处理结果的对应关系，每个异常标识信息包括一个程序标识。异常标识信息还可以包括异常日志信息和/或异常状态信息。
每个处理结果可以包括一个或多个处理建议，和/或，一个或多个异常原因，一个或多个受影响的程序。
服务端可以根据第一程序的程序标识确定一个或多个处理结果。第一处理结果包括该一个或多个处理结果。在第一程序的程序标识对应的处理结果为多个的情况下，服务端可以根据第一异常标识信息中的异常日志信息和/或异常状态信息，从该多个处理结果中进一步确定一个或多个处理结果。
第一处理结果可以包括第一异常原因。第一异常原因用于指示所述车载系统中的第一故障单元。也就是说，车载系统出现异常是由于第一故障单元的故障导致的。
服务端可以根据第二映射关系确定与第一故障单元关联的第二程序。第二映射关系用于指示多个故障单元与多个程序之间的关联关系。
第一故障单元的故障可能导致与第一故障单元关联的程序受到影响。服务端确定与第 一故障单元关联的第二程序，第二程序是由于第一故障单元的故障可能受到影响的程序，也就是说，第二程序是第一异常标识信息对应的程序，在第一异常标识信息对应的车载系统的异常情况下，第二程序受到影响。
或者，服务端可以根据多个异常标识信息与多个程序之间的关联关系，确定第一异常标识信息对应的第二程序。
处理请求可以包括异常日志信息，第一异常标识信息可以包括异常日志信息，或者，异常日志信息可以位于处理请求中异常日志信息之外的其他字段。
当第一映射关系中不存在第一异常标识信息对应的处理结果时，可以由人工确定第一处理结果。通过人工的方式，可以根据异常日志信息和第一程序的程序标识确定第一处理结果。之后，对第一映射关系进行更新，将第一异常标识信息与第一处理结果的对应关系添加在第一映射关系中。
或者，服务端可以根据第三映射关系，确定第二程序。第三映射关系记录有多个异常标识信息与多个程序的对应关系。
在步骤S103之后，服务端发送处理响应。处理响应可以包括第一处理结果和/或影响信息。
服务端可以向车载客户端发送处理响应，或者，服务端可以向车载客户端对应的用户设备发送处理响应。车载客户端对应的用户设备可以提前注册在服务端，也就是说，服务端保存有车载客户端与用户设备的对应关系。
服务端与车载客服端可以是各自独立的设备，也可以集成于同一设备中实现不同的功能。服务端与车载客服端之间的信息传输可以通过有线或无线的方式进行。
通过步骤S101-S103，当车载系统出现异常时，能够自动提供处理结果，以解决车载系统中的问题，解决了发生问题需要维护人员近端定位的问题，节约时间，提高用户体验。
图3是本申请实施例提供的一种车载系统异常处理的方法的示意性流程图。
在步骤S201，规范定义。
在程序开发阶段，定义程序标识。定义堆栈信息打印规范和日志打印规范。
程序标识用于标识一段程序。每种程序用于执行一种对应的方法。程序标识例如可以包括服务名称、功能名称和方法名称，程序标识music::play::playNext可以用于表示播放下一首音乐的程序名称，其中，playNext为方法名称，play为功能名称，music为服务名称。
车载系统可以在检测到异常状态时，打印堆栈信息，即在堆栈中记录与异常相关的信息，即车载系统可以根据监控，在异常的情况下在堆栈中记录与异常相关的信息。车载系统也可以在接收指示信息时，在堆栈中记录与异常相关的信息。指示信息可以用于指示出现异常状态，或者，该指示信息可以用于指示车载客户端获取第一程序的程序标识，或者，该指示信息可以用于指示车载客户端向服务端发送所述处理请求。
该指示信息可以是用户输入车载系统，或者，可以由用户设备发送至车载系统，或者，也可以由用户设备向服务端发送指示，由服务端向车载设备发送该指示信息。
堆栈中记录的与异常相关的信息的格式可以参见图1。程序信息可以包括异常程序标识。车载客户端可以在堆栈中记录的与异常相关的信息中提取异常堆栈信息。异常堆栈信息可以包括异常状态信息，异常状态信息用于指示异常状态。异常状态信息也可以称为异常信号量。异常状态例如包括内存溢出、内存地址错误、车载系统程序异常等。其中，内 存溢出、内存地址错误的异常情况可以由车载系统检测确定发生。
异常堆栈信息可以包括异常程序标识，异常程序标识即出现异常状态时运行的程序的程序标识。
异常堆栈信息还可以包括异常状态时运行的程序的内存地址。
日志可以记录程序的运行轨迹。在打印日志时，增加日志前缀，可以使得日志信息与程序的对应关系更加明确。日志前缀例如可以包括服务名称、功能名称等，如日志前缀可以包括music::play::playNext。
在步骤S202，知识库建立。
知识库可以包括两个部分，一部分是车载系统的结构关系，另一部分是异常问题库。
如图4所示的车载系统的结构关系的示意图，车载系统中的各个单元之间存在依赖关系。一个底层单元为多种上层单元提供支持。应当理解，底层单元与上层单元是相对的概念。底层单元也可以称为下层单元。在车载系统中，从底层到上层可以依次为服务单元、功能单元、方法单元。当一种底层单元出现故障时，依赖于该底层单元的其他上层单元提供的方法和/或功能也会出现异常，即该底层单元的上层单元会受到影响。例如，车服务单元作为底层单元为其上层单元空调功能单元、音乐功能单元等提供支持，空调功能单元作为底层单元为其上层单元启动方法单元、温度调节方法单元等提供支持。当车服务单元出现故障时，依赖于车服务单元的空调功能单元提供的多种方法也会出现异常。
车载系统的结构关系也可以理解为多个故障单元与多个程序之间的关联关系。一个程序可以用于实现一种方法，可以对应于一个方法单元，即程序可以与方法单元一一对应。车载系统出现异常，可能是由于服务单元、功能单元、方法单元中的一个或多个单元的异常或故障导致的。当车载系统出现异常时，可以根据车载系统的结构关系，确定可能出现故障的多个单元。在进行人工分析时，结合异常状态信息、异常日志信息、资源占用信息中的一种或多种，可以进一步从该多个单元中确定可能出现故障的一个或多个单元。在一个单元故障时，根据车载系统的结构关系可以确定收到该功能影响的一个或多个程序，即确定故障单元与一个或多个程序之间的关联关系。
异常问题库包括第一映射关系，即多个异常标识信息与多个处理结果的对应关系。每个处理结果包括异常处理建议和/或异常原因。
异常标识信息可以是对异常程序标识、异常状态信息、异常日志信息进行压缩映射得到的。
通过步骤S201-S202，完成了车载设备诊断方法的准备阶段。
在步骤S203，车载系统异常数据采集。
获取车载系统的信息，例如：异常服务堆栈信息、异常服务日志信息、资源占用信息等。
可以提供两种车载系统异常数据采集的方式。在两种情况下，进行车载系统异常数据的采集。一种是车载系统的根据监控进行信息采集，另外一种是在接收指示信息时进行采集。采集的信息可以包括异常堆栈信息、异常日志信息等，用于后续的异常定位。异常定位即确定异常原因或给出异常处理建议。异常原因用于指示车载系统中的故障单元，故障单元导致车载系统出现异常，即车载系统出现异常是由于故障单元的故障造成的。异常处理建议即车载系统异常的解决方案。
S204，知识库检索。
知识库可以存储在服务端中。车载设备可以将采集的原始数据或经过处理后的数据发送至服务端。
异常堆栈信息可以包括异常状态信息、异常程序标识。根据异常堆栈信息可以确定与该异常堆栈信息对应的异常日志信息。
异常标识信息可以是根据异常堆栈信息、异常日志信息得到的。例如可以对异常堆栈信息、异常日志信息进行压缩映射得到异常标识信息。异常标识信息可以包括异常堆栈信息、异常日志信息中的全部或部分信息。用于确定异常标识信息的异常日志信息例如可以是异常堆栈信息对应的日志中最后一条日志信息。
根据异常标识信息，在知识库中进行检索。
如果知识库中存在该异常标识信息和处理结果的对应关系，则进行步骤S205。
在步骤S205，将该异常标识信息对应的处理结果反馈给用户。例如将该处理结果发送至车载设备或者用户设备。
如果知识库中不存在该异常标识信息和处理结果的对应关系，则进行步骤S206。
在步骤S206，人工分析。进行人工定位，确定异常标识信息对应的处理结果。人工分析的过程中，可以结合车载系统的结构关系，分析定位出车载系统出现异常的根本原因，确定出现故障的单元，提供具体的解决方案。根据出现故障的单元，结合车载系统的结构关系，可以确定受到影响的一个或多个程序。异常标识信息对应的处理结果可以包括车载系统出现异常的原因、解决方案、确定受到影响的程序等中的一种或多种。
在步骤S207，将人工确定的该异常标识信息以及处理结果的对应关系补充在知识库的异常问题库中，更新知识库。
将人工确定的处理结果发送给用户。可以在步骤S206之后进行步骤S205，将人工确定的处理结果发送给用户设备或车载设备。或者，也可以在步骤S207之后进行步骤S205，由服务端发送处理结果。
通过步骤S201-S207，当车载系统出现异常时，能够自动提供处理结果，以解决车载系统中的问题，解决了发生问题需要维护人员近端定位的问题，对同样的车载系统异常情况不需要人工重复处理，节约时间，提高用户体验。
本申请实施例提供的车载系统异常处理的方法，使用异常监控以及用户触发的方式采集车载系统信息，在服务端结合知识库对异常情况进行处理，确定处理结果。根据维护人员对车载系统出现异常提供的处理结果，构建知识库。对于相同问题，自动检索知识库生成处理结果。
本申请实施例提供的车载系统异常处理的方法，可以应用于多种操作系统，使用灵活；能够自动提供处理结果，减少人工干预；通过更新知识库，不需要人工重复处理，降低人力成本，提高处理效率。
在计算机系统中，通常包括硬件系统、系统软件、支持系统、应用软件四个层次。硬件系统是指构成计算机的物理设备，即由机械、光、电、磁器件构成的具有计算、控制、存储、输入和输出功能的实体部件。系统软件是指控制和协调计算机及外部设备,支持应用软件开发和运行的系统。支持系统也可以称为决策支持系统，是辅助决策者通过数据、模型和知识，以人机交互方式进行半结构化或非结构化决策的计算机应用系统。应用软件(application)是和系统软件相对应的，是用户可以使用的各种程序设计语言，以及用各种程序设计语言编制的应用程序的集合，分为应用软件包和用户程序。应用软件包是利用 计算机解决某类问题而设计的程序的集合，供多用户使用。
可以通过执在车载客户端和服务端执行程序，以实现过上述方法。实现本申请实施例的程序可以运行在应用软件层，或计算机系统中的其他层次。
上文结合图2至图4的描述了本申请实施例的方法实施例，下面结合图5至图9，描述本申请实施例的装置实施例。应理解，方法实施例的描述与装置实施例的描述相互对应，因此，未详细描述的部分可以参见前面方法实施例。
图5是本申请实施例提供的一种车载系统异常处理的系统的示意图。该系统可以用于执行图2或图3所示的方法。
车载客户端包括处理模块和车载通信模块。车载客户端可以包括车载系统，或者车载客户端与车载系统可以是两个独立的设备。
处理模块可以用于进程监控、信息采集、信息脱敏。
进程监控，即监控车载系统的状态，确定是否出现异常。
信息采集，即采集车载系统的信息。例如：异常日志信息，异常堆栈信息等。
信息脱敏，即对采集的信息进行脱敏操作，保护用户隐私。
车载通信模块用于与服务端进行通信以及数据传输。
服务端包括存储模块、处理模块、通信模块。
存储模块用于知识库。知识库可以包括第一映射关系，第一映射关系记录有多个异常标识信息与多个处理结果的对应关系。知识库可以包括第二映射关系，第二映射关系包括指示多个故障单元与多个程序之间的关联关系。处理结果包括异常处理建议和/或异常原因，异常原因用于指示故障单元。
处理模块用于信息处理。处理模块可以根据接收到的车载客户端发送的异常标识信息，结合知识库进行处理，确定处理结果。在处理结果包括异常原因的情况下，处理模块可以根据异常原因，确定受故障单元影响的程序。
通信模块用于：主要负责把解决方案通知到用户。例如：通过APP、短信、邮件等方式。
服务端的通信模块用于与车载客户端、用户设备进行通信以及数据传输。服务端的通信模块可以接收车载客户端发送的异常标识信息。服务端的通信模块可以向车载客户端发送指示信息，指示信息用于指示所述车载客户端获取第一程序的程序标识。服务端的通信模块可以向用户设备发送处理结果和/或影响信息，影响信息用于指示受故障单元影响的程序。
可以通过邮件、短信、或者应用程序(application，APP)消息等方式发送至用户设备。
图6是本申请实施例提供的一种车载系统异常处理装置的示意性结构图。装置500包括获取模块501，收发模块502。
获取模块501，用于获取第一程序的程序标识，所述第一程序是运行异常的程序；
收发模块502，用于向服务端发送处理请求，所述处理请求用于指示所述服务端根据第一映射关系确定与所述第一异常标识信息对应的第一处理结果，所述处理请求携带第一异常标识信息，所述第一异常标识信息包括所述第一程序的程序标识，所述第一映射关系记录有多个异常标识信息与多个处理结果的对应关系，每个异常标识信息包括一个程序标识。
可选地，所述第一程序的代码中包括所述第一程序的程序标识。
可选地，获取模块501用于，获取异常堆栈信息，所述异常堆栈信息包括所述第一程序的程序标识。
可选地，当所述第一程序运行时，所述第一程序的程序标识被写入被分配所述第一程序的第一内存空间中，所述第一程序的代码中包括所述第一程序的程序标识，所述异常堆栈信息是根据所述第一内存空间确定的。
可选地，每个异常标识信息还包括以下参数中的至少一个：异常日志信息、异常状态信息、资源占用信息，所述异常日志信息是根据所述第一程序对应的日志得到的，所述异常状态信息用于指示以下异常状态中的至少一种：所述车载系统内存溢出、所述车载系统内存地址错误、车载系统程序异常，所述资源占用信息用于指示所述车载系统的资源占用情况。
可选地，收发模块502还用于，接收所述服务端发送的处理响应，所述处理响应包括所述第一处理结果。
可选地，所述第一处理结果包括第一异常原因，所述第一异常原因用于指示所述车载系统中的第一故障单元，
收发模块502还用于，接收所述服务端发送的处理响应，所述处理响应包括影响信息，所述影响信息用于指示第二程序，所述第二程序是第二映射关系指示的与所述第一故障单元关联的程序，所述第二映射关系包括指示多个故障单元与多个程序之间的关联关系。
可选地，所述装置还包括确定模块，用于确定满足异常条件，以确定所述车载系统出现异常，所述异常条件包括：
所述车载客户端接收到指示信息，所述指示信息用于指示所述车载客户端获取第一程序的程序标识；和/或，
检测到所述车载系统出现以下异常状态中的至少一种：所述车载系统内存溢出、所述车载系统内存地址错误、车载系统程序异常。
图7是本申请实施例提供的一种车载系统异常处理装置的示意性结构图。装置600包括收发模块601，确定模块602。
收发模块601，用于接收车载客户端发送的处理请求，所述处理请求携带第一异常标识信息，所述第一异常标识信息包括第一程序的程序标识，所述第一程序是运行异常的程序；
确定模块602，用于根据第一映射关系确定与所述第一异常标识信息对应的第一处理结果，所述第一映射关系记录有多个异常标识信息与多个处理结果的对应关系，每个异常标识信息包括一个程序标识。
可选地，所述第一程序的代码中包括所述第一程序的程序标识。
可选地，每个异常标识信息还包括以下参数中的至少一个：异常日志信息、异常状态信息、资源占用信息，所述异常日志信息是根据所述第一程序对应的日志得到的，所述异常状态信息用于指示以下异常状态中的至少一种：所述车载系统内存溢出、所述车载系统内存地址错误、车载系统程序异常，所述资源占用信息用于指示所述车载系统的资源占用情况。
可选地，收发模块601还用于，向所述车载客户端或与所述车载客户端对应的用户设备发送处理响应，所述处理响应包括所述第一处理结果。
可选地，所述第一处理结果包括第一异常原因，所述第一异常原因用于指示所述车载系统中的第一故障单元，
确定模块602还用于，根据第二映射关系确定与所述第一故障单元关联的第二程序，所述第二映射关系包括指示多个故障单元与多个程序之间的关联关系。
可选地，收发模块601还用于，向所述车载客户端或与所述车载客户端对应的用户设备发送处理响应，所述处理响应包括影响信息，所述影响信息用于指示所述第二程序。
可选地，收发模块601还用于，向所述车载客户端发送指示信息，所述指示信息用于指示所述车载客户端向所述服务端发送所述处理请求。
图8是本申请实施例提供的一种车载系统异常处理装置的示意性结构图。装置700包括处理器701，通信接口702。
处理器701，用于获取第一程序的程序标识，所述第一程序是运行异常的程序；
通信接口702，用于向服务端发送处理请求，所述处理请求用于指示所述服务端根据第一映射关系确定与所述第一异常标识信息对应的第一处理结果，所述处理请求携带第一异常标识信息，所述第一异常标识信息包括所述第一程序的程序标识，所述第一映射关系记录有多个异常标识信息与多个处理结果的对应关系，每个异常标识信息包括一个程序标识。
可选地，所述第一程序的代码中包括所述第一程序的程序标识。
可选地，处理器701用于，获取异常堆栈信息，所述异常堆栈信息包括所述第一程序的程序标识。
可选地，当所述第一程序运行时，所述第一程序的程序标识被写入被分配所述第一程序的第一内存空间中，所述第一程序的代码中包括所述第一程序的程序标识，所述异常堆栈信息是根据所述第一内存空间确定的。
可选地，每个异常标识信息还包括以下参数中的至少一个：异常日志信息、异常状态信息、资源占用信息，所述异常日志信息是根据所述第一程序对应的日志得到的，所述异常状态信息用于指示以下异常状态中的至少一种：所述车载系统内存溢出、所述车载系统内存地址错误、车载系统程序异常，所述资源占用信息用于指示所述车载系统的资源占用情况。
可选地，通信接口702还用于，接收所述服务端发送的处理响应，所述处理响应包括所述第一处理结果。
可选地，所述第一处理结果包括第一异常原因，所述第一异常原因用于指示所述车载系统中的第一故障单元，
通信接口702还用于，接收所述服务端发送的处理响应，所述处理响应包括影响信息，所述影响信息用于指示第二程序，所述第二程序是第二映射关系指示的与所述第一故障单元关联的程序，所述第二映射关系包括指示多个故障单元与多个程序之间的关联关系。
可选地，处理器701还用于，确定满足异常条件，以确定所述车载系统出现异常，所述异常条件包括：
所述车载客户端接收到指示信息，所述指示信息用于指示所述车载客户端获取第一程序的程序标识；和/或，
检测到所述车载系统出现以下异常状态中的至少一种：所述车载系统内存溢出、所述车载系统内存地址错误、车载系统程序异常。
图9是本申请实施例提供的一种车载系统异常处理装置的示意性结构图。装置800包括处理器801，通信接口802。
通信接口802，用于接收车载客户端发送的处理请求，所述处理请求携带第一异常标识信息，所述第一异常标识信息包括第一程序的程序标识，所述第一程序是运行异常的程序；
处理器801，用于根据第一映射关系确定与所述第一异常标识信息对应的第一处理结果，所述第一映射关系记录有多个异常标识信息与多个处理结果的对应关系，每个异常标识信息包括一个程序标识。
可选地，所述第一程序的代码中包括所述第一程序的程序标识。
可选地，每个异常标识信息还包括以下参数中的至少一个：异常日志信息、异常状态信息、资源占用信息，所述异常日志信息是根据所述第一程序对应的日志得到的，所述异常状态信息用于指示以下异常状态中的至少一种：所述车载系统内存溢出、所述车载系统内存地址错误、车载系统程序异常，所述资源占用信息用于指示所述车载系统的资源占用情况。
可选地，通信接口802还用于，向所述车载客户端或与所述车载客户端对应的用户设备发送处理响应，所述处理响应包括所述第一处理结果。
可选地，所述第一处理结果包括第一异常原因，所述第一异常原因用于指示所述车载系统中的第一故障单元，
处理器801还用于，根据第二映射关系确定与所述第一故障单元关联的第二程序，所述第二映射关系包括指示多个故障单元与多个程序之间的关联关系。
可选地，通信接口802还用于，向所述车载客户端或与所述车载客户端对应的用户设备发送处理响应，所述处理响应包括影响信息，所述影响信息用于指示所述第二程序。
可选地，通信接口802还用于，向所述车载客户端发送指示信息，所述指示信息用于指示所述车载客户端向所述服务端发送所述处理请求。
本申请实施例还提供一种车载系统异常处理系统，包括上文所述的车载客户端和服务端。
本申请实施例还提供一种计算机程序存储介质，其特征在于，所述计算机程序存储介质具有程序指令，当所述程序指令被直接或者间接执行时，使得前文中的方法得以实现。
本申请实施例还提供一种芯片系统，其特征在于，所述芯片系统包括至少一个处理器，当程序指令在所述至少一个处理器中执行时，使得前文中的方法得以实现。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
本申请实施例中，“至少一个”是指一个或者多个，“多个”是指两个或两个以上。“和/或”，描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示单独存在A、同时存在A和B、单独存在B的情况。其中A，B可以是单数或者复数。字符“/”一般表示前后关联对象是一种“或”的关系。“以下至少一项”及其类似表达，是指的这些项中的任意组合，包括单项或复数项的任意组合。例如，a，b和c中的至少一 项可以表示：a，b，c，a-b，a-c，b-c，或a-b-c，其中a，b，c可以是单个，也可以是多个。所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(Read-Only Memory，ROM)、随机存取存储器(Random Access Memory，RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以所述权利要求的保护范围为准。

Claims (32)

  1. 一种车载系统异常处理的方法，其特征在于，所述方法包括：
    车载客户端获取第一程序的程序标识，所述第一程序是运行异常的程序；
    所述车载客户端向服务端发送处理请求，所述处理请求携带第一异常标识信息，所述处理请求用于指示所述服务端根据第一映射关系确定与所述第一异常标识信息对应的第一处理结果，所述第一异常标识信息包括所述第一程序的程序标识，所述第一映射关系记录有多个异常标识信息与多个处理结果的对应关系，每个异常标识信息包括一个程序标识。
  2. 根据权利要求1所述的方法，其特征在于，所述第一程序的代码中包括所述第一程序的程序标识。
  3. 根据权利要求1或2所述的方法，其特征在于，车载客户端获取第一程序的程序标识，包括：
    所述车载客户端获取异常堆栈信息，所述异常堆栈信息包括所述第一程序的程序标识。
  4. 根据权利要求3所述的方法，其特征在于，当所述第一程序运行时，所述第一程序的程序标识被写入被分配所述第一程序的第一内存空间中，所述第一程序的代码中包括所述第一程序的程序标识，所述异常堆栈信息是根据所述第一内存空间确定的。
  5. 根据权利要求1至4中任一项所述的方法，其特征在于，每个异常标识信息还包括以下参数中的至少一个：异常日志信息、异常状态信息、资源占用信息，所述异常日志信息是根据所述第一程序对应的日志得到的，所述异常状态信息用于指示以下异常状态中的至少一种：所述车载系统内存溢出、所述车载系统内存地址错误、车载系统程序异常，所述资源占用信息用于指示所述车载系统的资源占用情况。
  6. 根据权利要求1至5中任一项所述的方法，其特征在于，所述方法还包括：
    所述车载客户端接收所述服务端发送的处理响应，所述处理响应包括所述第一处理结果。
  7. 根据权利要求1至6中任一项所述的方法，其特征在于，
    所述第一处理结果包括第一异常原因，所述第一异常原因用于指示所述车载系统中的第一故障单元，
    所述方法还包括：所述车载客户端接收所述服务端发送的处理响应，所述处理响应包括影响信息，所述影响信息用于指示第二程序，所述第二程序是第二映射关系指示的与所述第一故障单元关联的程序，所述第二映射关系包括指示多个故障单元与多个程序之间的关联关系。
  8. 根据权利要求1-7中任一项所述的方法，其特征在于，所述方法还包括：
    所述车载客户端确定满足异常条件，以确定所述车载系统出现异常，所述异常条件包括：
    所述车载客户端接收到指示信息，所述指示信息用于指示所述车载客户端获取第一程序的程序标识；和/或，
    检测到所述车载系统出现以下异常状态中的至少一种：所述车载系统内存溢出、所述 车载系统内存地址错误、车载系统程序异常。
  9. 一种车载系统异常处理的方法，其特征在于，所述方法包括：
    服务端接收车载客户端发送的处理请求，所述处理请求携带第一异常标识信息，所述第一异常标识信息包括第一程序的程序标识，所述第一程序是运行异常的程序；
    所述服务端根据第一映射关系确定与所述第一异常标识信息对应的第一处理结果，所述第一映射关系记录有多个异常标识信息与多个处理结果的对应关系，每个异常标识信息包括一个程序标识。
  10. 根据权利要求9所述的方法，其特征在于，所述第一程序的代码中包括所述第一程序的程序标识。
  11. 根据权利要求9或10所述的方法，其特征在于，每个异常标识信息还包括以下参数中的至少一个：异常日志信息、异常状态信息、资源占用信息，所述异常日志信息是根据所述第一程序对应的日志得到的，所述异常状态信息用于指示以下异常状态中的至少一种：所述车载系统内存溢出、所述车载系统内存地址错误、车载系统程序异常，所述资源占用信息用于指示所述车载系统的资源占用情况。
  12. 根据权利要求9至11中任一项所述的方法，其特征在于，所述方法还包括：
    所述服务端向所述车载客户端或与所述车载客户端对应的用户设备发送处理响应，所述处理响应包括所述第一处理结果。
  13. 根据权利要求9至12中任一项所述的方法，其特征在于，所述第一处理结果包括第一异常原因，所述第一异常原因用于指示所述车载系统中的第一故障单元，
    所述方法还包括：
    所述服务端根据第二映射关系确定与所述第一故障单元关联的第二程序，所述第二映射关系包括指示多个故障单元与多个程序之间的关联关系。
  14. 根据权利要求13所述的方法，其特征在于，所述方法还包括：
    所述服务端向所述车载客户端或与所述车载客户端对应的用户设备发送处理响应，所述处理响应包括影响信息，所述影响信息用于指示所述第二程序。
  15. 根据权利要求9-14中任一项所述的方法，其特征在于，所述方法还包括：
    所述服务端向所述车载客户端发送指示信息，所述指示信息用于指示所述车载客户端向所述服务端发送所述处理请求。
  16. 一种车载系统异常处理装置，其特征在于，包括：
    获取模块，用于获取第一程序的程序标识，所述第一程序是运行异常的程序；
    收发模块，用于向服务端发送处理请求，所述处理请求携带第一异常标识信息，所述处理请求用于指示所述服务端根据第一映射关系确定与所述第一异常标识信息对应的第一处理结果，所述第一异常标识信息包括所述第一程序的程序标识，所述第一映射关系记录有多个异常标识信息与多个处理结果的对应关系，每个异常标识信息包括一个程序标识。
  17. 根据权利要求16所述的装置，其特征在于，所述第一程序的代码中包括所述第一程序的程序标识。
  18. 根据权利要求16或17所述的装置，其特征在于，
    所述获取模块用于，获取异常堆栈信息，所述异常堆栈信息包括所述第一程序的程序标识。
  19. 根据权利要求18所述的装置，其特征在于，当所述第一程序运行时，所述第一程序的程序标识被写入被分配所述第一程序的第一内存空间中，所述第一程序的代码中包括所述第一程序的程序标识，所述异常堆栈信息是根据所述第一内存空间确定的。
  20. 根据权利要求16至19中任一项所述的装置，其特征在于，每个异常标识信息还包括以下参数中的至少一个：异常日志信息、异常状态信息、资源占用信息，所述异常日志信息是根据所述第一程序对应的日志得到的，所述异常状态信息用于指示以下异常状态中的至少一种：所述车载系统内存溢出、所述车载系统内存地址错误、车载系统程序异常，所述资源占用信息用于指示所述车载系统的资源占用情况。
  21. 根据权利要求16至20中任一项所述的装置，其特征在于，
    所述收发模块还用于，接收所述服务端发送的处理响应，所述处理响应包括所述第一处理结果。
  22. 根据权利要求16至21中任一项所述的装置，其特征在于，
    所述第一处理结果包括第一异常原因，所述第一异常原因用于指示所述车载系统中的第一故障单元，
    所述收发模块还用于，接收所述服务端发送的处理响应，所述处理响应包括影响信息，所述影响信息用于指示第二程序，所述第二程序是第二映射关系指示的与所述第一故障单元关联的程序，所述第二映射关系包括指示多个故障单元与多个程序之间的关联关系。
  23. 根据权利要求16-22中任一项所述的装置，其特征在于，
    所述装置还包括确定模块，用于确定满足异常条件，以确定所述车载系统出现异常，所述异常条件包括：
    所述车载客户端接收到指示信息，所述指示信息用于指示所述车载客户端获取第一程序的程序标识；和/或，
    检测到所述车载系统出现以下异常状态中的至少一种：所述车载系统内存溢出、所述车载系统内存地址错误。
  24. 一种车载系统异常处理装置，其特征在于，包括：
    收发模块，用于接收车载客户端发送的处理请求，所述处理请求携带第一异常标识信息，所述第一异常标识信息包括第一程序的程序标识，所述第一程序是运行异常的程序；
    确定模块，用于根据第一映射关系确定与所述第一异常标识信息对应的第一处理结果，所述第一映射关系记录有多个异常标识信息与多个处理结果的对应关系，每个异常标识信息包括一个程序标识。
  25. 根据权利要求24所述的装置，其特征在于，所述第一程序的代码中包括所述第一程序的程序标识。
  26. 根据权利要求24或25所述的装置，其特征在于，每个异常标识信息还包括以下参数中的至少一个：异常日志信息、异常状态信息、资源占用信息，所述异常日志信息是根据所述第一程序对应的日志得到的，所述异常状态信息用于指示以下异常状态中的至少一种：所述车载系统内存溢出、所述车载系统内存地址错误、车载系统程序异常，所述资源占用信息用于指示所述车载系统的资源占用情况。
  27. 根据权利要求24至26中任一项所述的装置，其特征在于，
    所述收发模块还用于，向所述车载客户端或与所述车载客户端对应的用户设备发送处理响应，所述处理响应包括所述第一处理结果。
  28. 根据权利要求24至27中任一项所述的装置，其特征在于，所述第一处理结果包括第一异常原因，所述第一异常原因用于指示所述车载系统中的第一故障单元，
    所述确定模块还用于，根据第二映射关系确定与所述第一故障单元关联的第二程序，所述第二映射关系包括指示多个故障单元与多个程序之间的关联关系。
  29. 根据权利要求28所述的装置，其特征在于，
    所述收发模块还用于，向所述车载客户端或与所述车载客户端对应的用户设备发送处理响应，所述处理响应包括影响信息，所述影响信息用于指示所述第二程序。
  30. 根据权利要求24至29中任一项所述的装置，其特征在于，
    所述收发模块还用于，向所述车载客户端发送指示信息，所述指示信息用于指示所述车载客户端向所述服务端发送所述处理请求。
  31. 一种计算机存储介质，其特征在于，当所述计算机指令在电子设备上运行时，所述电子设备执行权利要求1-15中任一项所述的方法。
  32. 一种芯片系统，其特征在于，包括至少一个处理器，当程序指令在所述至少一个处理器中执行时，权利要求1-15中任一项所述的方法被执行。
PCT/CN2020/114868 2019-09-12 2020-09-11 车载系统异常处理的方法及装置 WO2021047655A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP20863354.5A EP4020213A4 (en) 2019-09-12 2020-09-11 METHOD AND DEVICE FOR TREATMENT OF AN ABNORMAL IN AN ON-VEHICLE SYSTEM
US17/692,588 US20220197732A1 (en) 2019-09-12 2022-03-11 Method and apparatus for handling exception of in-vehicle system

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201910866626.3 2019-09-12
CN201910866626.3A CN112486715A (zh) 2019-09-12 2019-09-12 车载系统异常处理的方法及装置

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US17/692,588 Continuation US20220197732A1 (en) 2019-09-12 2022-03-11 Method and apparatus for handling exception of in-vehicle system

Publications (1)

Publication Number Publication Date
WO2021047655A1 true WO2021047655A1 (zh) 2021-03-18

Family

ID=74866105

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/114868 WO2021047655A1 (zh) 2019-09-12 2020-09-11 车载系统异常处理的方法及装置

Country Status (4)

Country Link
US (1) US20220197732A1 (zh)
EP (1) EP4020213A4 (zh)
CN (1) CN112486715A (zh)
WO (1) WO2021047655A1 (zh)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115392505B (zh) * 2022-08-29 2023-07-18 智迪机器人技术(盐城)有限公司 一种汽车配件自动安装机器人的异常处理系统及方法

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8315760B2 (en) * 2008-12-03 2012-11-20 Mitchell Repair Information Company LLC Method and system for retrieving diagnostic information
CN105228107A (zh) * 2015-09-09 2016-01-06 深圳市元征科技股份有限公司 一种车辆异常处理方法及相关设备
CN106445787A (zh) * 2016-09-30 2017-02-22 北京金山安全软件有限公司 一种监控服务器核心转储文件的方法、装置及电子设备
CN107885187A (zh) * 2017-10-19 2018-04-06 深圳市元征科技股份有限公司 一种汽车远程诊断方法、用户终端及服务器
CN108616653A (zh) * 2018-03-30 2018-10-02 广东欧珀移动通信有限公司 信息处理方法、装置、移动终端和计算机可读存储介质
CN109190771A (zh) * 2018-08-23 2019-01-11 深圳市轱辘汽车维修技术有限公司 一种车辆维修方法及相关设备

Family Cites Families (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20050015579A1 (en) * 2003-07-15 2005-01-20 Rajeev Grover Handling exceptions
US20090013208A1 (en) * 2008-03-31 2009-01-08 Dimuzio Thomas M Real time automated exception notification and reporting solution
US9104561B2 (en) * 2012-09-13 2015-08-11 Microsoft Technology Licensing, Llc Failure mode identification and reporting
CN105591788A (zh) * 2014-11-14 2016-05-18 中国科学院沈阳计算技术研究所有限公司 一种信息化机房故障点影响范围分析系统及方法
US20160342453A1 (en) * 2015-05-20 2016-11-24 Wanclouds, Inc. System and methods for anomaly detection
US10037238B2 (en) * 2016-02-10 2018-07-31 Dell Products, L.P. System and method for encoding exception conditions included at a remediation database
CN109800101A (zh) * 2019-02-01 2019-05-24 北京字节跳动网络技术有限公司 小程序异常情况的上报方法、装置、终端设备和存储介质

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8315760B2 (en) * 2008-12-03 2012-11-20 Mitchell Repair Information Company LLC Method and system for retrieving diagnostic information
CN105228107A (zh) * 2015-09-09 2016-01-06 深圳市元征科技股份有限公司 一种车辆异常处理方法及相关设备
CN106445787A (zh) * 2016-09-30 2017-02-22 北京金山安全软件有限公司 一种监控服务器核心转储文件的方法、装置及电子设备
CN107885187A (zh) * 2017-10-19 2018-04-06 深圳市元征科技股份有限公司 一种汽车远程诊断方法、用户终端及服务器
CN108616653A (zh) * 2018-03-30 2018-10-02 广东欧珀移动通信有限公司 信息处理方法、装置、移动终端和计算机可读存储介质
CN109190771A (zh) * 2018-08-23 2019-01-11 深圳市轱辘汽车维修技术有限公司 一种车辆维修方法及相关设备

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP4020213A4

Also Published As

Publication number Publication date
EP4020213A1 (en) 2022-06-29
US20220197732A1 (en) 2022-06-23
CN112486715A (zh) 2021-03-12
EP4020213A4 (en) 2022-10-12

Similar Documents

Publication Publication Date Title
CN105357038B (zh) 监控虚拟机集群的方法和系统
CN107729210B (zh) 分布式服务集群的异常诊断方法和装置
CN106462702B (zh) 用于在分布式计算机基础设施中获取并且分析电子取证数据的方法和系统
JP5736881B2 (ja) ログ収集システム、装置、方法及びプログラム
US10462027B2 (en) Cloud network stability
CN106209405B (zh) 故障诊断方法及装置
US8819220B2 (en) Management method of computer system and management system
CN108763038A (zh) 告警数据的管理方法、装置、计算机设备及存储介质
WO2013140608A1 (ja) イベントの根本原因の解析を支援する方法及びシステム
WO2016188100A1 (zh) 信息系统故障场景信息收集方法及系统
CN107003926B (zh) 故障信息提供服务器、故障信息提供方法
CN109976959A (zh) 一种用于服务器故障检测的便携式设备及方法
JP2007323193A (ja) 性能負荷異常検出システム、性能負荷異常検出方法、及びプログラム
KR102580916B1 (ko) 5g 분산 클라우드 시스템의 빅 데이터를 이용하여 장애를 관리하는 장치 및 방법
CN113505044B (zh) 数据库告警方法、装置、设备和存储介质
US20150074267A1 (en) Network Anomaly Detection
WO2021047655A1 (zh) 车载系统异常处理的方法及装置
JP2014120001A (ja) 監視装置、監視対象ホストの監視方法、監視プログラム及び記録媒体
US20220163942A1 (en) Distributed System and Data Transmission Method
WO2022088803A1 (zh) 基于云环境的系统信息分析方法、装置、电子设备及介质
JP2008234351A (ja) 統合運用監視システム及びプログラム
CN107820270B (zh) 一种基于gsm-r网络的gprs接口监测系统
CN104238540A (zh) 用于系统异常诊断的信息采集方法、装置及医疗设备
CN115883330B (zh) 告警事件处理方法、系统、设备及存储介质
CN117271234A (zh) 故障诊断方法、装置、存储介质及电子装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 20863354

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2020863354

Country of ref document: EP

Effective date: 20220324