Vehicle-mounted service management system, vehicle-mounted service management method and device

Abstract

The invention relates to a vehicle-mounted service management system, a vehicle-mounted service management method and a vehicle-mounted service management device. The system comprises at least two service management services. Each service management service is used for managing the vehicle-mounted application service corresponding to each service management service, and the service management service is used for acquiring abnormal information of the vehicle-mounted application service corresponding to the service management service under the condition that the service management service detects that the vehicle-mounted application service corresponding to the service management service is abnormal; the abnormal information is used for recording service abnormity existing in the vehicle-mounted application service corresponding to the service management service; and the service management service is used for analyzing the abnormal information and restarting the vehicle-mounted application service with the abnormal service. By adopting the system, the vehicle-mounted application services corresponding to the service management services can be managed respectively based on the service management services, the situation that abnormal services affect operation of other services in the vehicle-mounted system is avoided, safe and stable operation of the vehicle-mounted system is guaranteed, and therefore the safety of the vehicle-mounted system is improved.

Description

Technical Field

[0001] The present application relates to the field of computer technology, and in particular to an in-vehicle service management system, an in-vehicle service management method, an apparatus, a computer device, a computer-readable storage medium, and a computer program product. Background Art

[0002] With the development of automobile intelligence, the in-vehicle system has become more and more complex, involving multiple functional modules such as navigation, entertainment, communication, and driving assistance. The service management of the in-vehicle system can manage and coordinate various software services in the vehicle, thereby ensuring that the various services of the in-vehicle system can run efficiently and reliably, and can be dynamically adjusted according to the needs of the vehicle and the driver.

[0003] In traditional technology, the service management of the vehicle system is mainly carried out through the system native process to comprehensively manage various vehicle services. The coupling degree between various services is high, the management is complex, and the system response is slow. Once a service abnormality occurs, it will cause the system native process to be abnormal, which is not conducive to improving the safety of the vehicle system. Summary of the invention

[0004] Based on this, it is necessary to provide an in-vehicle service management system, an in-vehicle service management method, an apparatus, a computer device, a computer-readable storage medium and a computer program product that can improve the security of the in-vehicle system in response to the above technical problems.

[0005] In a first aspect, the present application provides a method for managing an in-vehicle service management system, the system comprising at least two service management services; each of the service management services is used to manage the in-vehicle application services corresponding to each of the service management services, wherein:

[0006] When the service management service detects that the vehicle application service corresponding to the service management service has a service anomaly, the service management service is used to obtain the anomaly information of the vehicle application service corresponding to the service management service; the anomaly information is used to record the service anomaly of the vehicle application service corresponding to the service management service;

[0007] The service management service is used to analyze the abnormal information and restart the vehicle application service with service abnormality.

[0008] In one of the embodiments, the detecting that a service anomaly exists in the vehicle application service corresponding to the service management service includes:

[0009] The service management service sends a status check request to the vehicle application service corresponding to the service management service; the status check request is used to control the vehicle application service corresponding to the service management service to check the running status of the vehicle application service corresponding to the service management service;

[0010] If the service management service does not receive a status check result returned by the in-vehicle application service corresponding to the service management service within a preset time, or if the status check result returned by the in-vehicle application service corresponding to the service management service received by the service management service within a preset time indicates that the in-vehicle application service corresponding to the service management service is in a locked state, it is determined that there is a service abnormality in the in-vehicle application service corresponding to the service management service.

[0011] In one of the embodiments, before determining that the vehicle-mounted application service corresponding to the service management service has a service anomaly, the service management service is further used to obtain a running status check result of the service management service;

[0012] When the running status check result of the service management service indicates that the service management service is in normal running state, it is determined whether the in-vehicle application service corresponding to the service management service has service abnormality according to the status check result returned by the in-vehicle application service corresponding to the service management service.

[0013] In one of the embodiments, before obtaining the abnormal information of the in-vehicle application service corresponding to the service management service, when the service management service is in the startup state, the service management service is used to obtain the management configuration information corresponding to the service management service; the management configuration information is used to record the in-vehicle application service corresponding to the service management service; the service management service is used to determine the in-vehicle application service corresponding to the service management service based on the management configuration information.

[0014] In one of the embodiments, before obtaining the management configuration information corresponding to the service management service, the service management service is further used to obtain signature information of the service to be added corresponding to the service management service;

[0015] When the signature information of the service to be added is consistent with the signature information of the vehicle-mounted service management system, the service management service is used to update the management configuration information corresponding to the service management service according to the service to be added;

[0016] When the signature information of the service to be added is inconsistent with the signature information of the in-vehicle service management system, the service management service is used to refuse to host the service to be added.

[0017] In one of the embodiments, after obtaining the management configuration information corresponding to the service management service, the service management service is further used to, upon receiving a service call request from an application for an in-vehicle application service corresponding to the service management service recorded in the management configuration information, use the in-vehicle application service corresponding to the service call request as a service to be called;

[0018] The service management service is used to determine the to-be-verified information corresponding to the to-be-called service according to the authority information of the to-be-called service;

[0019] In a case where the information to be verified passes verification, the service management service is used to allow the application to call the service to be called.

[0020] In one embodiment, determining the to-be-verified information corresponding to the to-be-called service according to the permission information of the to-be-called service includes:

[0021] In a case where the permission information of the service to be called is at a preset first permission level, a matching result between the permission information of the service to be called and the permission information of the application is used as the to-be-verified information corresponding to the service to be called;

[0022] When the permission information of the service to be called is the preset second permission level, the matching result between the permission information of the service to be called and the permission information of the application, as well as the matching result between the signature information of the vehicle-mounted service management system for the application and the signature information of the vehicle-mounted service management system for the service to be called are used as the information to be verified corresponding to the service to be called.

[0023] In one of the embodiments, after allowing the application to call the service to be called, the service management service is further used to add the application to a preset queue;

[0024] When a service call request is received from the application for the in-vehicle application service corresponding to the service management service recorded in the management configuration information, and the application is in the preset queue, the service management service is used to allow the application to call the service to be called.

[0025] In a second aspect, the present application further provides an in-vehicle service management method applied to the above-mentioned in-vehicle service management system, comprising:

[0026] When the service management service in the vehicle-mounted service management system detects that the vehicle-mounted application service corresponding to the service management service has a service anomaly, obtaining anomaly information of the vehicle-mounted application service corresponding to the service management service; the anomaly information is used to record the service anomaly of the vehicle-mounted application service corresponding to the service management service;

[0027] Analyze the abnormal information and restart the vehicle application service with the service abnormality.

[0028] In a third aspect, the present application further provides an in-vehicle service management device applied to the above-mentioned in-vehicle service management system, comprising:

[0029] An anomaly detection module, configured to obtain anomaly information of the vehicle application service corresponding to the service management service when the service management service in the vehicle service management system detects that the vehicle application service corresponding to the service management service has a service anomaly; the anomaly information is used to record the service anomaly of the vehicle application service corresponding to the service management service;

[0030] The service restart module is used to analyze the abnormal information and restart the vehicle application service with service abnormality.

[0031] In a fourth aspect, the present application further provides a computer device, wherein the computer device comprises a memory and a processor, wherein the memory stores a computer program, and when the computer program is executed by the processor, the steps of the above method are implemented.

[0032] In a fifth aspect, the present application further provides a computer-readable storage medium having a computer program stored thereon, and the computer program implements the steps of the above method when executed by a processor.

[0033] In a sixth aspect, the present application further provides a computer program product, wherein the computer program product comprises a computer program, and when the computer program is executed by a processor, the steps of the above method are implemented.

[0034] The above-mentioned vehicle-mounted service management system, vehicle-mounted service management method, device, computer equipment, computer-readable storage medium and computer program product, the vehicle-mounted service management system includes at least two service management services; each service management service is used to manage the vehicle-mounted application service corresponding to each service management service, so as to avoid abnormal services affecting the operation of other services when all services are managed in a unified manner. When the service management service detects that the vehicle-mounted application service corresponding to the service management service has a service abnormality, the service management service is used to obtain abnormal information of the vehicle-mounted application service corresponding to the service management service; the abnormal information is used to record the service abnormality of the vehicle-mounted application service corresponding to the service management service, so as to timely monitor and detect whether the vehicle-mounted application service corresponding to each service management service has an abnormality; the service management service is used to analyze the abnormal information and restart the vehicle-mounted application service with service abnormality, so as to restart the abnormal service in time to ensure the safe and stable operation of the vehicle-mounted system, and can manage the vehicle-mounted application service corresponding to each service management service separately based on each service management service, so as to avoid the abnormal service affecting the operation of other services in the vehicle system, ensure the safe and stable operation of the vehicle system, and thus improve the safety of the vehicle system. BRIEF DESCRIPTION OF THE DRAWINGS

[0035] In order to more clearly illustrate the technical solutions in the embodiments of the present application or related technologies, the drawings required for use in the embodiments of the present application or related technical descriptions will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other related drawings can be obtained based on these drawings without paying creative work.

[0036] Figure 1 is a schematic diagram of an in-vehicle service management system in one embodiment;

[0037] Figure 2 An application environment diagram of an in-vehicle service management method in an embodiment;

[0038] Figure 3 is a schematic diagram of an in-vehicle service management system in another embodiment;

[0039] Figure 4 A schematic diagram of a process of starting a service management service in an embodiment;

[0040] Figure 5 A schematic diagram of a process of adding a service in an embodiment;

[0041] Figure 6 A schematic diagram of a process of an application calling a service in one embodiment;

[0042] Figure 7 A schematic diagram of a process for handling abnormal services in one embodiment;

[0043] Figure 8 A schematic diagram of another process for handling abnormal services in one embodiment;

[0044] Fig. 9 A schematic diagram of a monitoring service flow in one embodiment;

[0045] Fig.10 is a structural block diagram of an in-vehicle service management device in one embodiment;

[0046] Fig.11 The figure is a diagram of the internal structure of a computer device in one embodiment. DETAILED DESCRIPTION

[0047] In order to make the purpose, technical solution and advantages of the present application more clearly understood, the present application is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.

[0048] In an exemplary embodiment, Figure 1As shown, a vehicle-mounted service management system is provided, and the vehicle-mounted service management system includes at least two service management services; each service management service is used to manage the vehicle-mounted application service corresponding to each service management service, wherein:

[0049] When the service management service detects that the vehicle application service corresponding to the service management service has a service anomaly, the service management service is used to obtain the anomaly information of the vehicle application service corresponding to the service management service; the anomaly information is used to record the service anomaly of the vehicle application service corresponding to the service management service;

[0050] Among them, the service management service may refer to a service used to manage a specific service (such as an in-vehicle application service). In actual applications, the service management service may include but is not limited to CoreServer.

[0051] Among them, in-vehicle application services may refer to applications and services integrated in the car. In actual applications, each in-vehicle application service may have corresponding functions. The functions of the in-vehicle application services may include but are not limited to navigation, entertainment, communication, driving assistance and other functions.

[0052] Among them, the abnormal information may refer to information used to record service abnormalities existing in the in-vehicle application service corresponding to the service management service.

[0053] As an example, the vehicle service management system may include at least two service management services, each of which can be used to manage (such as hosting) a specific vehicle application service. In actual applications, the vehicle application services can be divided according to business, and the vehicle application services under different categories can be managed separately by different service management services. For each service management service, when the service management service detects that any of the vehicle application services corresponding to the service management service has a service anomaly, the service management service can obtain the anomaly information of the vehicle application service corresponding to the service management service through a preset anomaly handler. In actual applications, the service management service can first determine the identifier of the vehicle application service with the anomaly, and obtain the anomaly information of the vehicle application service represented by the identifier through a preset anomaly handler, so as to perform subsequent anomaly analysis.

[0054] The service management service is used to analyze exception information and restart the in-vehicle application services with service exceptions.

[0055] As an example, after the service management service obtains the exception information of the in-vehicle application service with an abnormality, the service management service can record and analyze the exception information in order to resolve the exception. The service management service can also restart the in-vehicle application service with the service abnormality to prevent the in-vehicle application service from failing to operate normally and ensure the normal operation of the service.

[0056] In this embodiment, the vehicle-mounted service management system includes at least two service management services; each service management service is used to manage the vehicle-mounted application service corresponding to each service management service, so as to avoid abnormal services affecting the operation of other services when all services are managed in a unified manner. When the service management service detects that the vehicle-mounted application service corresponding to the service management service has a service abnormality, the service management service is used to obtain abnormal information of the vehicle-mounted application service corresponding to the service management service; the abnormal information is used to record the service abnormality of the vehicle-mounted application service corresponding to the service management service, so as to timely monitor and detect whether the vehicle-mounted application service corresponding to each service management service has an abnormality; the service management service is used to analyze the abnormal information and restart the vehicle-mounted application service with service abnormality, so as to restart the abnormal service in time to ensure the safe and stable operation of the vehicle-mounted system. Based on each service management service, the vehicle-mounted application service corresponding to each service management service can be managed separately to avoid abnormal services affecting the operation of other services in the vehicle system, ensure the safe and stable operation of the vehicle system, and thus improve the safety of the vehicle system.

[0057] In one of the exemplary embodiments, a service anomaly is detected in the vehicle application service corresponding to the service management service, including: the service management service sends a status check request to the vehicle application service corresponding to the service management service; the status check request is used to control the vehicle application service corresponding to the service management service to check the running status of the vehicle application service corresponding to the service management service; if the service management service does not receive a status check result returned by the vehicle application service corresponding to the service management service within a preset time, or if the status check result returned by the vehicle application service corresponding to the service management service received by the service management service within the preset time indicates that the vehicle application service corresponding to the service management service is in a locked state, it is determined that a service anomaly exists in the vehicle application service corresponding to the service management service.

[0058] Among them, the status check request may refer to information used to control the running status of the in-vehicle application service corresponding to the service management service to check the in-vehicle application service corresponding to the service management service. In actual applications, the status check request may be implemented by the check instance (such as HandlerChecker) corresponding to each in-vehicle application service.

[0059] The preset time may refer to information that is preset and used to limit the time required for the status check. In actual applications, the preset time may be flexibly set and adjusted based on actual conditions.

[0060] Among them, the status check result may refer to information representing the running status of the in-vehicle application service (such as whether there is an abnormality / service abnormality).

[0061] As an example, in order to detect whether there is a service anomaly in the vehicle application service corresponding to the service management service, the service management service can send a status check request to the vehicle application service corresponding to the service management service through the check instance corresponding to each vehicle application service corresponding to the service management service or call a preset check method, so as to perform a status check on the vehicle application service corresponding to the service management service. After receiving the status check request, the vehicle application service can check its own running status and return the status check result. If the service management service does not receive the status check result returned by the vehicle application service corresponding to the service management service within the preset time, the service management service can determine that the vehicle application service corresponding to the missing status check result (or the vehicle application service that does not return the status check result) has a service anomaly. In a specific implementation, if the status check result returned by the vehicle application service corresponding to the service management service received by the service management service within the preset time indicates that the vehicle application service corresponding to the service management service is in a locked state, the service management service can also determine that the vehicle application service corresponding to the service management service (such as the vehicle application service in a locked state) has a service anomaly.

[0062] In this embodiment, a status check request is sent to the vehicle-mounted application service corresponding to the service management service through the service management service; the status check request is used to control the vehicle-mounted application service corresponding to the service management service to check the running status of the vehicle-mounted application service corresponding to the service management service; if the service management service does not receive the status check result returned by the vehicle-mounted application service corresponding to the service management service within a preset time, or the status check result returned by the vehicle-mounted application service corresponding to the service management service received by the service management service within the preset time indicates that the vehicle-mounted application service corresponding to the service management service is in a locked state, it is determined that there is a service abnormality in the vehicle-mounted application service corresponding to the service management service, and the status check result of the vehicle-mounted application service can be obtained through the status check request, and combined with whether the status check result is returned within the preset time and the content of the status check result, it is possible to accurately judge whether there is a service abnormality in the vehicle-mounted application service, thereby improving the accuracy of judging whether there is a service abnormality in the vehicle application service.

[0063] In one of the exemplary embodiments, before determining that the in-vehicle application service corresponding to the service management service has a service anomaly, the service management service is also used to obtain an operation status check result of the service management service; when the operation status check result of the service management service indicates that the service management service is in a normal operating state, it is determined whether the in-vehicle application service corresponding to the service management service has a service anomaly based on the status check result returned by the in-vehicle application service corresponding to the service management service.

[0064] The running status check result may refer to information representing the running status of the service management service (such as whether there is an abnormality / service abnormality).

[0065] As an example, before finally determining whether there is a service anomaly in the in-vehicle application service, the service management service needs to first ensure that the service management service is operating normally. Specifically, before determining that there is a service anomaly in the in-vehicle application service corresponding to the service management service, the service management service may first obtain the operating status check result of the service management service. When the operating status check result of the service management service indicates that the service management service is in normal operating status, the service management service may then determine whether there is a service anomaly in the in-vehicle application service corresponding to the service management service based on the status check result returned by the in-vehicle application service corresponding to the service management service. In actual applications, the service management service may obtain the operating status check result of the service management service itself after receiving the status check result returned by the in-vehicle application service corresponding to the service management service. When the service management service is operating normally, the service management service may determine whether there is a service anomaly in the in-vehicle application service based on whether the in-vehicle application service corresponding to the service management service returns the status check result within a preset time and the content of the status check result, to prevent the service management service itself from being unable to confirm the status of the in-vehicle application service due to an abnormality.

[0066] In this embodiment, before determining whether the in-vehicle application service corresponding to the service management service has a service anomaly, an operation status check result of the service management service is obtained; when the operation status check result of the service management service indicates that the service management service is in a normal operating state, it is determined whether the in-vehicle application service corresponding to the service management service has a service anomaly based on the status check result returned by the in-vehicle application service corresponding to the service management service. Before determining whether the in-vehicle application service has an anomaly, it is possible to confirm whether the service management service is operating normally based on the operation status check result of the service management service, thereby avoiding misjudgment of the status of the in-vehicle application service due to an anomaly in the service management service, and improving the accuracy of determining whether the in-vehicle application service has a service anomaly.

[0067] In one of the exemplary embodiments, before obtaining the exception information of the in-vehicle application service corresponding to the service management service, when the service management service is in the startup state, the service management service is used to obtain the management configuration information corresponding to the service management service; the management configuration information is used to record the in-vehicle application service corresponding to the service management service; the service management service is used to determine the in-vehicle application service corresponding to the service management service based on the management configuration information.

[0068] Among them, the management configuration information may refer to information used to record the in-vehicle application service corresponding to the service management service.

[0069] As an example, the service management service may be pre-set with corresponding management configuration information, and the management configuration information may record the vehicle application service corresponding to the service management service. The number and content of the vehicle application service in the management configuration information may be flexibly configured and adjusted according to actual needs, and the management configuration information may also be automatically updated according to the system configuration of the vehicle service management system. In actual applications, the permissions of the access mechanism (such as SELinux) of the vehicle application service in the management configuration information are separated from each other. The service management service may have corresponding startup conditions, for example: when the vehicle service system is started, the vehicle service system may trigger the startup conditions corresponding to the service management service (such as persistent="true" and directBootAware="true"), at which time the service management service can be started by the vehicle service management system. When the service management service is in the startup state, the service management service may obtain the management configuration information corresponding to the service management service, and determine the vehicle application service corresponding to the service management service according to the management configuration information, so as to perform abnormal monitoring and management on the vehicle application service corresponding to the service management service in the future.

[0070] In the present embodiment, before obtaining the abnormal information of the in-vehicle application service corresponding to the service management service, when the service management service is in the startup state, the service management service is used to obtain the management configuration information corresponding to the service management service; the management configuration information is used to record the in-vehicle application service corresponding to the service management service; the service management service is used to determine the in-vehicle application service corresponding to the service management service according to the management configuration information, and can accurately obtain the in-vehicle application service that needs to be managed by the service management service based on the management configuration information corresponding to the service management service when the service management service is started, and improve the in-vehicle application service corresponding to the service management service, so as to accurately manage the in-vehicle application service, ensure the safe and stable operation of the in-vehicle system, and thereby improve the safety of the in-vehicle system.

[0071] In one of the exemplary embodiments, before obtaining the management configuration information corresponding to the service management service, the service management service is also used to obtain the signature information of the service to be added corresponding to the service management service; when the signature information of the service to be added is consistent with the signature information of the vehicle-mounted service management system, the service management service is used to update the management configuration information corresponding to the service management service according to the service to be added; when the signature information of the service to be added is inconsistent with the signature information of the vehicle-mounted service management system, the service management service is used to refuse to host the service to be added.

[0072] The service to be added may refer to an in-vehicle application service that needs to be managed by a specific service management service.

[0073] Among them, the signature information may refer to information used for data verification. In actual applications, the signature information of the service to be added may refer to information used to characterize the source, integrity, security, etc. of the service to be added. The signature information of the vehicle service management system may refer to information used to verify the source, integrity, security, etc. of each service to be added.

[0074] As an example, for each service management service, the vehicle application service recorded in the management configuration information corresponding to the service management service can be used as an internal service, and the services other than the internal services in the vehicle service management system can be used as external services, and the external service can be used as a service to be added. When the service to be added needs to be managed by the service management service, the service management service can first obtain the signature information of the service to be added, and then the service management service can verify the signature information of the service to be added according to the signature information of the vehicle service management system (such as the system signature). Specifically, when the signature information of the service to be added is consistent with the signature information of the vehicle service management system, the service management service can be allowed to manage the service to be added. The service management service can update the management configuration information corresponding to the service management service according to the service to be added so as to manage the service to be added. When the signature information of the service to be added is inconsistent with the signature information of the vehicle service management system, the service management service can refuse to update the management configuration information corresponding to the service management service according to the service to be added, and refuse to manage the service to be added, thereby refusing to host the service to be added.

[0075] In the present embodiment, before obtaining the management configuration information corresponding to the service management service, the service management service is also used to obtain the signature information of the service to be added corresponding to the service management service; when the signature information of the service to be added is consistent with the signature information of the vehicle-mounted service management system, the service management service is used to update the management configuration information corresponding to the service management service according to the service to be added; when the signature information of the service to be added is inconsistent with the signature information of the vehicle-mounted service management system, the service management service is used to refuse to host the service to be added, and can verify the signature information of the service to be added based on the signature information of the vehicle-mounted service management system, and accurately determine whether to manage the service to be added based on the verification result, thereby realizing flexible and accurate vehicle-mounted application service management.

[0076] In one of the exemplary embodiments, after obtaining the management configuration information corresponding to the service management service, the service management service is also used to, upon receiving a service call request from an application for the in-vehicle application service corresponding to the service management service recorded in the management configuration information, use the in-vehicle application service corresponding to the service call request as the service to be called; the service management service is used to determine the information to be verified corresponding to the service to be called based on the permission information of the service to be called; and when the information to be verified passes the verification, the service management service is used to allow the application to call the service to be called.

[0077] The application may refer to an application program that is not developed, maintained or controlled within the vehicle service management system. In actual applications, the application may be an external application.

[0078] Among them, the service call request may refer to information used to request to obtain / call a specific in-vehicle application service.

[0079] The service to be called may refer to the in-vehicle application service requested to be called by the service call request.

[0080] The permission information may refer to information used for permission verification. In actual applications, the permission information of the service to be called may refer to the conditions that need to be met by the application when calling the service to be called.

[0081] The information to be verified may refer to information used to determine whether an application is allowed to call an in-vehicle application service.

[0082] As an example, when an application needs to call a certain vehicle-mounted application service, the application can send a service call request for the vehicle-mounted application service to the service management service corresponding to the vehicle-mounted application service. When the service management service receives the service call request from the application for the vehicle-mounted application service corresponding to the service management service recorded in the management configuration information, the service management service can use the vehicle-mounted application service corresponding to the service call request as the service to be called, and then the service management service can obtain the permission information of the service to be called, and determine the information to be verified corresponding to the service to be called based on the permission information of the service to be called. In actual applications, the information to be verified can be different when the permission information is different. The service management service can then verify the information to be verified, and if the information to be verified passes the verification, the service management service can allow the application to call the service to be called.

[0083] In this embodiment, after obtaining the management configuration information corresponding to the service management service, the service management service is also used to, when receiving a service call request from an application for the in-vehicle application service corresponding to the service management service recorded in the management configuration information, use the in-vehicle application service corresponding to the service call request as the service to be called; the service management service is used to determine the information to be verified corresponding to the service to be called based on the permission information of the service to be called; when the information to be verified passes the verification, the service management service is used to allow the application to call the service to be called, and can promptly respond to the application's call request for the in-vehicle application service, determine the information to be verified in combination with the permission information of the service, and based on the verification result of the information to be verified, accurately determine whether the application is allowed to call the in-vehicle application service, thereby avoiding the in-vehicle application service from being called in an irregular manner, ensuring the security of the in-vehicle service management system, and thereby improving the security of the in-vehicle system.

[0084] In one of the exemplary embodiments, the information to be verified corresponding to the service to be called is determined based on the permission information of the service to be called, including: when the permission information of the service to be called is a preset first permission level, the matching result between the permission information of the service to be called and the permission information of the application is used as the information to be verified corresponding to the service to be called; when the permission information of the service to be called is a preset second permission level, the matching result between the permission information of the service to be called and the permission information of the application, as well as the matching result between the signature information of the vehicle-mounted service management system for the application and the signature information of the vehicle-mounted service management system for the service to be called are used as the information to be verified corresponding to the service to be called.

[0085] The preset first permission level may refer to a permission level that only needs permission verification among a plurality of preset permission levels. In actual applications, the preset first permission level may include a “dangerous level”.

[0086] Among them, the preset second permission level may refer to a permission level that requires at least permission verification and signature verification among several preset permission levels. In actual applications, the preset second permission level may include a "signature level".

[0087] Among them, the signature information of the in-vehicle service management system for the application may refer to information used to characterize the source, integrity, security, etc. of the application.

[0088] Among them, the signature information of the vehicle service management system for the service to be called may refer to information used to verify the source, integrity, security, etc. of the application.

[0089] As an example, different permission information corresponds to different information to be verified. Specifically, when the permission information of the service to be called is the preset "normal level", the service management service can directly allow the application to call the service to be called without performing any check on the application; when the permission information of the service to be called is the preset first permission level, the service management service can use the matching result between the permission information of the service to be called and the permission information of the application as the information to be verified corresponding to the service to be called. If the matching result between the permission information of the service to be called and the permission information of the application indicates that the permission information of the service to be called matches the permission information of the application, the service management service can determine that the information to be verified has passed the verification; when the permission information of the service to be called is the preset second permission level, the service management service can match the matching result between the permission information of the service to be called and the permission information of the application, as well as the signature information of the application for the vehicle service management system. The matching result between the signature information of the service to be called by the vehicle service management system is used as the information to be verified corresponding to the service to be called. If the matching result between the permission information of the service to be called and the permission information of the application indicates that the permission information of the service to be called matches the permission information of the application, and the matching result between the signature information of the service to be called by the vehicle service management system indicates that the signature information of the service to be called by the vehicle service management system matches, the service management service can determine that the information to be verified has passed the verification; when the permission information of the service to be called is the preset signature / system level (signatureOrSystem)", the service management service can use the matching result between the permission information of the service to be called and the permission information of the application, the matching result between the signature information of the vehicle service management system for the application and the signature information of the vehicle service management system for the service to be called, and the confirmation result of the application according to the preset system-level verification rules as the information to be verified.

[0090] In this embodiment, when the permission information of the service to be called is the preset first permission level, the matching result between the permission information of the service to be called and the permission information of the application is used as the information to be verified corresponding to the service to be called; when the permission information of the service to be called is the preset second permission level, the matching result between the permission information of the service to be called and the permission information of the application, as well as the matching result between the signature information of the vehicle-mounted service management system for the application and the signature information of the vehicle-mounted service management system for the service to be called are used as the information to be verified corresponding to the service to be called. Based on the permission information of different levels, the corresponding information to be verified can be accurately analyzed, so as to accurately determine whether the application is allowed to call the vehicle-mounted application service in combination with the information to be verified, thereby avoiding the vehicle-mounted application service from being called in an irregular manner, ensuring the security of the vehicle-mounted service management system, and thereby improving the security of the vehicle-mounted system.

[0091] In one of the exemplary embodiments, after allowing the application to call the service to be called, the service management service is also used to add the application to a preset queue; when a service call request is received from the application for the in-vehicle application service corresponding to the service management service recorded in the management configuration information and the application is in the preset queue, the service management service is used to allow the application to call the service to be called.

[0092] As an example, after allowing the application to call the service to be called, the service management service can determine that the application has passed the verification, and the service management service can add the application to the preset queue. When the service call request of the application for the vehicle-mounted application service corresponding to the service management service recorded in the management configuration information is received again, and the application is in the preset queue, the service management service can allow the application to call the service to be called without re-verification.

[0093] In this embodiment, after allowing the application to call the service to be called, the service management service is also used to add the application to a preset queue; when a service call request is received from the application for the in-vehicle application service corresponding to the service management service recorded in the management configuration information, and the application is in the preset queue, the service management service is used to allow the application to call the service to be called, and can quickly determine whether the application is allowed to call the service management service by judging whether the application is in the preset queue, thereby avoiding repeated verification and improving the operating efficiency of the in-vehicle service management system.

[0094] In an exemplary embodiment, Figure 2 As shown, a vehicle-mounted service management method applied to the above-mentioned vehicle-mounted service management system is provided, comprising the following steps S202 to S204. Among them:

[0095] Step S202, when the service management service in the vehicle service management system detects that the vehicle application service corresponding to the service management service has a service anomaly, obtains the anomaly information of the vehicle application service corresponding to the service management service; the anomaly information is used to record the service anomaly of the vehicle application service corresponding to the service management service.

[0096] Among them, the service management service may refer to a service used to manage a specific service (such as an in-vehicle application service). In actual applications, the service management service may include but is not limited to CoreServer.

[0097] Among them, in-vehicle application services may refer to applications and services integrated in the car. In actual applications, each in-vehicle application service may have corresponding functions. The functions of the in-vehicle application services may include but are not limited to navigation, entertainment, communication, driving assistance and other functions.

[0098] Among them, the abnormal information may refer to information used to record service abnormalities existing in the in-vehicle application service corresponding to the service management service.

[0099] As an example, the vehicle service management system may include at least two service management services, each of which can be used to manage (such as hosting) a specific vehicle application service. In actual applications, the vehicle application services can be divided according to business, and the vehicle application services under different categories can be managed separately by different service management services. For each service management service, when the service management service detects that any of the vehicle application services corresponding to the service management service has a service anomaly, the service management service can obtain the anomaly information of the vehicle application service corresponding to the service management service through a preset anomaly handler. In actual applications, the service management service can first determine the identifier of the vehicle application service with the anomaly, and obtain the anomaly information of the vehicle application service represented by the identifier through a preset anomaly handler, so as to perform subsequent anomaly analysis.

[0100] Step S204, analyzing the abnormal information and restarting the vehicle application service with the service abnormality.

[0101] As an example, after the service management service obtains the abnormal information of the vehicle application service with abnormality, the service management service can record and analyze the abnormal information to solve the abnormality. The service management service can also restart the vehicle application service with service abnormality to prevent the vehicle application service from failing to operate normally and ensure the normal operation of the service. In actual applications, the service management service can analyze the abnormal information and count the number of abnormalities of each vehicle application service. In combination with the abnormal information of each vehicle application service, the service management service can also count the operating status of each vehicle application service.

[0102] In the above-mentioned vehicle service management method, when the service management service detects that the vehicle application service corresponding to the service management service has a service anomaly, the anomaly information of the vehicle application service corresponding to the service management service is obtained; the anomaly information is used to record the service anomaly of the vehicle application service corresponding to the service management service, so as to timely monitor and detect whether the vehicle application service corresponding to each service management service has an anomaly; the anomaly information is analyzed, and the vehicle application service with the service anomaly is restarted, so as to restart the service with the anomaly in time to ensure the safe and stable operation of the vehicle system, and the vehicle application service corresponding to each service management service can be managed separately based on each service management service to avoid the abnormal service affecting the operation of other services in the vehicle system, thereby ensuring the safe and stable operation of the vehicle system and improving the safety of the vehicle system.

[0103] In some embodiments, the vehicle service management system can optimize the service management of the vehicle system through modular design and intelligent service scheduling, improve the system performance and user experience, and the vehicle service management system can implement service management functions. The service management function supports the classification of various module services (such as vehicle application services) of the business in the vehicle system and merges them into the service management service CoreServer, where the vehicle application services corresponding to the service management service have little correlation with each other and are not UI services. The vehicle application services corresponding to the same service management service can be used as internal services, and other vehicle application services other than internal services can be used as external services. For example, power management can be concentrated in one service and placed in CoreServer for management. The classification of vehicle application services is mainly based on business division, such as customized services such as system process memory monitoring. The standard is to divide by business, and the process is to divide a separate service according to the business and place it under CoreServer management.

[0104] When compiling internal services, the code needs to be packaged into CoreServer.apk and needs to be decoupled. The modules of each package have no strong association and can be packaged separately. The conversion from internal services to external services can be seamless, that is, it supports placing the service directly in the CoreServer program, and it can support separate external services for CoreServer to do process management. The number and content of internal services can be configured according to the project, and the compilation chain can be automatically changed according to the configuration. The SELinux permissions of each internal service module are separated and merged into CoreServer according to the configuration. CoreServer implements the startup of internal and external services and implements Binder hosting of internal and external services. When an exception occurs in an internal service, try not to restart CoreServer. It is necessary to ensure the normal operation of CoreServer. It is necessary to save the exception for subsequent analysis and restart the abnormal in-vehicle application service. Try to keep the CoreServer process normal or in an error state (such as ANR). If an exception occurs, the service management service needs to be restarted as soon as possible. When an exception occurs in an external service, the service management service needs to restart the service according to the service exception type and notify other applications.

[0105] In one exemplary embodiment, Figure 3As shown, a schematic diagram of an in-vehicle service management system is provided, CoreSystemApplication may refer to the Application of the CoreSystemServer application, which is used to start the App Service component service of the CoreSystemServer at startup; CoreServer may refer to the App Service component service of the CoreSystemServer application, which is used to initialize its own Binder service and internal and external services in the configuration file; CoreSystemBinderServer may refer to the binder object of the CoreSystemServer service, the server end of the AIDL interface; CoreSystemServerImpl may refer to the main function implementation class of the CoreSystemServer application, which is the proxy object of the binder object. The implementation of the functions is all in this object class, which is the core class of the service management service. CoreSystemServerImpl includes functions such as parsing configuration files, starting services, executing executable code segments, and monitoring service abnormal status; CoreSystemCommonUserImpl may refer to a subclass of CoreSystemServerImpl, which is initialized in the service management process and handles service management business instead of CoreSystemServerImpl; CoreSystemProfileUserImpl may refer to CoreSystemServerImpl Another subclass of ManagedProfileUser, initialized in the service management process of ManagedProfileUser, and replaces CoreSystemServerImpl to handle service management business; CoreSystemCrashHandler may refer to a singleton object, which is used to handle exception information that cannot be captured by the process, capture exceptions to prevent the process from restarting, and restart the service Looper, analyze the source of the exception, and if it is an internal service, notify the service listener to restart the service module; WatchDog may refer to an object class of a monitoring management class, which is used to monitor the status of each service. When an abnormal block occurs in the service, it is responsible for restarting the service, and its function is similar to the WatchDog function in the system_server process; ServiceData may refer to a service information object; ExecutorData may refer to the corresponding executable code segment function; AutoBootOnUserHelper may refer to a tool class for the service management service to start automatically on multiple users (after AOSP is configured with persistent=true, it will only start automatically on SystemUser0);CoreForegroundUserManager can refer to a tool class inside the service management process that is used to interact with the service management process on the foreground user. CoreForegroundUserManager can also be used to add a binder to the service management process on the foreground user, obtain a binder, and other functions; CoreSystemUserManager can refer to a tool class inside the service management process that is used to interact with the service management process. CoreSystemUserManager can also be used to add a binder to the service management process, obtain a binder, and other functions; CoreServicesLoader can refer to a service information loader that is used to read the core_services_configs.json file to obtain the service information configured in the project. ;

[0106] like Figure 4 As shown, a flowchart of starting a service management service is provided. The service management service CoreServer is configured with persistent="true" and directBootAware="true". It can be started by the system after the system service is started. Since CoreServer is a system application that must be started by the system when the system is turned on, it is necessary to configure persistent="true" and directBootAware="true" to be started by the system. The main function of configuring persistent="true" and directBootAware="true" is that CoreServer can be started when the system is turned on. After CoreServer is started, it is necessary to use the bindService method in Application to start the service in CoreServer so that the peripheral application can obtain the Binder of the service through BroadcastReceiver to reduce the problem of asynchronous callback. After CoreServer is started, the CoreSystemBinderServer object is initialized. CoreSystemBinderServer is a binder object that can be used as a binder server to communicate with the outside world across processes. When the CoreSystemBinderServer object is initialized, the current user category will be determined to determine the initialization of the CoreSystemServerImpl object, the CoreSystemCommonUserImpl object, or the CoreSystemProfileUserImpl object.

[0107] like Figure 5As shown in the figure, a process diagram for adding services is provided. After an external service (such as a service started in Start mode) is started, if the service Binder needs to be hosted, the service can be passed to CoreServer by calling Manager's addService. When CoreSystemServerImpl obtains the Binder of the external service, saves and manages it, and registers a listener (linkToDeath), when the service sends an exception, it can be learned through the callback and the service can be restarted. When adding a service, the external service needs to check whether the service signature is consistent with the system signature. If it is inconsistent, it is considered not a system service and CoreServer will not provide hosting services.

[0108] like Figure 6 As shown, a flowchart of an application calling a service is provided. When an external application obtains / calls the in-vehicle application service in the service management service CoreServer, it is necessary to first check the permission level of the service to be obtained, and make different permission confirmations according to different levels. No check is performed for the permission level of normal, only permission confirmation is performed for the permission level of dangerous, and a system signature confirmation is added for the permission level of signature. A system application-level confirmation is added for the permission level of signatureOrSystem. Applications that have been judged can be put in a queue, and when they are accessed again next time, information can be returned in time according to the status stored in the queue without having to judge again.

[0109] like Figure 7 As shown in the figure, a flowchart for handling abnormal services is provided. Since the process contains multiple modules and is the main service, if an abnormality occurs, the impact will be greater and will affect the operation of the vehicle system. Therefore, try not to restart the service process. You can capture the exception through Thread.setDefaultUncaughtExceptionHandler. After capturing the exception, the service management service needs to analyze the abnormal module and notify CoreSystemServerImpl to restart the module. Since the exception may cause confusion within the module, it is recommended to restart the module to avoid affecting the overall service. The process of capturing the exception and restarting can be followed Figure 7 The process numbered 1, 3, 4, 5, 9, 10, and 11 is implemented. The service management service can record exceptions in a specified log file for regular analysis of service exceptions. Since the exception problem cannot be shelved, the module needs to be responsible for analysis and resolution. Regular analysis of exceptions can correspond to Figure 7 The process numbered 2 is implemented. Because it is an exception capture, the Handler in the ActivityThread has stopped working, so the Handler needs to be restarted at this time to ensure the normal operation of the service.

[0110] like Figure 8 As shown in the figure, a flowchart for handling abnormal services is provided. Since the external (hosted) service (such as the service to be added in the configuration management information) has a listener (linkToDeath) registered on the Binder, the service status will be known through the binderDied callback. When the external service is abnormal, the Binder is released, and according to the service type, it is confirmed how to restart the service (Bind mode start or Start mode start).

[0111] like Fig. 9 As shown in the figure, a flow chart of monitoring service is provided. Monitoring vehicle application service can be realized through WatchDog. WatchDog itself is a thread, and the operation method is not allowed to block the process. Each thread monitored in WatchDog is a HandlerChecker, and it is also a callback operation. It cannot block the process. In the run method of WatchDog, the event is sent to each HandlerChecker, and then wait for 30 seconds to confirm again whether there is a process in the current state that is locked. If so, restart the process. Each confirmation finally confirms its own process to ensure that other processes have been confirmed to prevent itself from being stuck and unable to confirm the processes of other modules. After each confirmation, it can wait for 30 seconds again to start the next confirmation process. In the specific implementation, WatchDog monitors internal / external services. The contents that need to be implemented by internal and external services include: the service defines the constant WATCHDOG_MONITOR (10001), which is passed to the corresponding process through the binder's transact; the service receives WATCHDOG_MONITOR in onTransact and calls its own monitor to implement the monitoring function. Specifically, the implementation scheme of the service monitor method may include: the service management monitors whether the key service is running normally by acquiring a synchronization lock to verify that the key service is not deadlocked. Among them, lock is a synchronization lock, and other methods of the key service must be implemented according to the steps of: acquiring lock -> function implementation -> releasing lock to ensure that lock can reflect the running status of the entire service. In actual applications, the service management service can count the number of service exceptions and running status and other service-related information during the operation of the vehicle service management system.

[0112] In this embodiment, through the startup process of each core service in the service management service management system in the vehicle service management system, the startup timing and order of the service can be adjusted according to the configuration file, and the availability of these core services in the system operation is ensured, and the service can be started again in the event of an exception or no response; small and light services can be merged into the service management service module to reduce the overhead of system resources, and the status of each service can be monitored. When an abnormal block occurs in the service, it is responsible for restarting the service to improve system reliability; a service management mechanism is added to the system's customized applications and services, and isolated from the native System_server, which can not only decouple but also ensure system security, avoid a service exception (such as a service crash) causing system core service exceptions and system exceptions, and put the customized service on CoreServer for separate management. If the customized service crashes, it will only cause CoreServer crash, and will not cause system core function exceptions, thereby ensuring the safe and stable operation of the vehicle system.

[0113] It should be understood that, although the various steps in the flowcharts involved in the above-mentioned embodiments are displayed in sequence according to the indication of the arrows, these steps are not necessarily executed in sequence according to the order indicated by the arrows. Unless there is a clear explanation in this article, the execution of these steps does not have a strict order restriction, and these steps can be executed in other orders. Moreover, at least a part of the steps in the flowcharts involved in the above-mentioned embodiments can include multiple steps or multiple stages, and these steps or stages are not necessarily executed at the same time, but can be executed at different times, and the execution order of these steps or stages is not necessarily to be carried out in sequence, but can be executed in turn or alternately with other steps or at least a part of the steps or stages in other steps.

[0114] Based on the same inventive concept, the embodiment of the present application also provides an in-vehicle service management device for implementing the in-vehicle service management method involved above. The implementation scheme for solving the problem provided by the device is similar to the implementation scheme recorded in the above method, so the specific limitations in one or more in-vehicle service management device embodiments provided below can refer to the limitations of the in-vehicle service management method above, and will not be repeated here.

[0115] In an exemplary embodiment, Fig.10 As shown, a vehicle-mounted service management device applied to the above-mentioned vehicle-mounted service management system is provided, including: an abnormality detection module 1002 and a service restart module 1004, wherein:

[0116] The anomaly detection module 1002 is used to obtain the anomaly information of the in-vehicle application service corresponding to the service management service when the service management service in the in-vehicle service management system detects that the in-vehicle application service corresponding to the service management service has a service anomaly; the anomaly information is used to record the service anomaly of the in-vehicle application service corresponding to the service management service.

[0117] The service restart module 1004 is used to analyze the abnormal information and restart the vehicle application service with the service abnormality.

[0118] Each module in the above-mentioned vehicle-mounted service management device can be implemented in whole or in part by software, hardware or a combination thereof. Each module can be embedded in or independent of a processor in a computer device in the form of hardware, or can be stored in a memory in a computer device in the form of software, so that the processor can call and execute the corresponding operations of each module.

[0119] In an exemplary embodiment, a computer device is provided. The computer device may be a terminal, and its internal structure diagram may be as shown in FIG. Fig.11 As shown. The computer device includes a processor, a memory, an input / output interface, a communication interface, a display unit and an input device. The processor, the memory and the input / output interface are connected through a system bus, and the communication interface, the display unit and the input device are connected to the system bus through the input / output interface. The processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The input / output interface of the computer device is used to exchange information between the processor and the external device. The communication interface of the computer device is used to communicate with an external terminal in a wired or wireless manner, and the wireless manner can be implemented through WIFI, a mobile cellular network, near field communication (NFC) or other technologies. When the computer program is executed by the processor, a method for managing in-vehicle services is implemented. The display unit of the computer device is used to form a visually visible picture, which can be a display screen, a projection device or a virtual reality imaging device. The display screen can be a liquid crystal display screen or an electronic ink display screen, and the input device of the computer device can be a touch layer covering the display screen, or a button, trackball or touchpad set on the computer device shell, or an external keyboard, touchpad or mouse.

[0120] Those skilled in the art will understand that Fig.11The structure shown in the figure is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied. The specific computer device may include more or fewer components than those shown in the figure, or combine certain components, or have a different arrangement of components.

[0121] In one embodiment, a computer device is further provided, including a memory and a processor, wherein a computer program is stored in the memory, and the processor implements the steps in the above method embodiments when executing the computer program.

[0122] In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the steps in the above-mentioned method embodiments are implemented.

[0123] In one embodiment, a computer program product is provided, including a computer program, which implements the steps in the above method embodiments when executed by a processor.

[0124] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data must comply with relevant regulations.

[0125] A person of ordinary skill in the art can understand that all or part of the processes in the above-mentioned embodiment method can be completed by instructing the relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to the memory, database or other medium used in the embodiments provided in the present application can include at least one of non-volatile memory and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. As an illustration and not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM). The database involved in each embodiment provided in this application may include at least one of a relational database and a non-relational database. Non-relational databases may include distributed databases based on blockchains, etc., but are not limited to this. The processor involved in each embodiment provided in this application may be a general-purpose processor, a central processing unit, a graphics processor, a digital signal processor, a programmable logic device, a data processing logic device based on quantum computing, an artificial intelligence (AI) processor, etc., but are not limited to this.

[0126] The technical features of the above embodiments may be combined arbitrarily. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this application.

[0127] The above-described embodiments only express several implementation methods of the present application, and the descriptions thereof are relatively specific and detailed, but they cannot be understood as limiting the scope of the present application. It should be pointed out that, for a person of ordinary skill in the art, several variations and improvements can be made without departing from the concept of the present application, and these all belong to the protection scope of the present application. Therefore, the protection scope of the present application shall be subject to the attached claims.

Claims

1. A vehicle-mounted service management system, characterized in that: The system includes at least two service management services; Each of the service management services is used to manage the vehicle application services corresponding to each of the service management services, wherein: When the service management service detects that the vehicle application service corresponding to the service management service has a service anomaly, the service management service is used to obtain the anomaly information of the vehicle application service corresponding to the service management service; the anomaly information is used to record the service anomaly of the vehicle application service corresponding to the service management service; The service management service is used to analyze the abnormal information and restart the vehicle application service with service abnormality.

2. The system according to claim 1, characterized in that The detecting that a service anomaly exists in the vehicle application service corresponding to the service management service includes: The service management service sends a status check request to the vehicle application service corresponding to the service management service; the status check request is used to control the vehicle application service corresponding to the service management service to check the running status of the vehicle application service corresponding to the service management service; If the service management service does not receive a status check result returned by the in-vehicle application service corresponding to the service management service within a preset time, or if the status check result returned by the in-vehicle application service corresponding to the service management service received by the service management service within a preset time indicates that the in-vehicle application service corresponding to the service management service is in a locked state, it is determined that there is a service abnormality in the in-vehicle application service corresponding to the service management service.

3. The system according to claim 2, characterized in that Before determining that the vehicle-mounted application service corresponding to the service management service has a service anomaly, the service management service is further used to obtain a running status check result of the service management service; When the running status check result of the service management service indicates that the service management service is in normal running state, it is determined whether the in-vehicle application service corresponding to the service management service has service abnormality according to the status check result returned by the in-vehicle application service corresponding to the service management service.

4. The system according to claim 1, characterized in that Before obtaining the abnormal information of the vehicle application service corresponding to the service management service, when the service management service is in the startup state, the service management service is used to obtain the management configuration information corresponding to the service management service; The management configuration information is used to record the vehicle application service corresponding to the service management service; The service management service is used to determine the vehicle-mounted application service corresponding to the service management service according to the management configuration information.

5. The system according to claim 4, characterized in that Before obtaining the management configuration information corresponding to the service management service, the service management service is further used to obtain signature information of the service to be added corresponding to the service management service; In a case where the signature information of the service to be added is consistent with the signature information of the vehicle-mounted service management system, the service management service is used to update the management configuration information corresponding to the service management service according to the service to be added; When the signature information of the service to be added is inconsistent with the signature information of the vehicle-mounted service management system, the service management service is used to refuse to host the service to be added.

6. The system according to claim 4, characterized in that After obtaining the management configuration information corresponding to the service management service, the service management service is further used to, when receiving a service call request from an application for the vehicle application service corresponding to the service management service recorded in the management configuration information, use the vehicle application service corresponding to the service call request as a service to be called; The service management service is used to determine the to-be-verified information corresponding to the to-be-called service according to the authority information of the to-be-called service; In a case where the information to be verified passes verification, the service management service is used to allow the application to call the service to be called.

7. The system according to claim 6, characterized in that The determining, according to the authority information of the service to be called, the information to be verified corresponding to the service to be called includes: In a case where the permission information of the service to be called is at a preset first permission level, a matching result between the permission information of the service to be called and the permission information of the application is used as the to-be-verified information corresponding to the service to be called; When the permission information of the service to be called is the preset second permission level, the matching result between the permission information of the service to be called and the permission information of the application, as well as the matching result between the signature information of the vehicle-mounted service management system for the application and the signature information of the vehicle-mounted service management system for the service to be called are used as the information to be verified corresponding to the service to be called.

8. The system according to claim 6, characterized in that After allowing the application to call the service to be called, the service management service is further used to add the application to a preset queue; When a service call request is received from the application for the in-vehicle application service corresponding to the service management service recorded in the management configuration information, and the application is in the preset queue, the service management service is used to allow the application to call the service to be called.

9. An in-vehicle service management method applied to the in-vehicle service management system according to any one of claims 1 to 8, characterized in that: The method comprises: When the service management service in the vehicle-mounted service management system detects that the vehicle-mounted application service corresponding to the service management service has a service anomaly, obtaining anomaly information of the vehicle-mounted application service corresponding to the service management service; the anomaly information is used to record the service anomaly of the vehicle-mounted application service corresponding to the service management service; Analyze the abnormal information and restart the vehicle application service with the service abnormality.

10. An in-vehicle service management device applied to the in-vehicle service management system according to any one of claims 1 to 8, characterized in that: The device comprises: An anomaly detection module, configured to obtain anomaly information of the vehicle application service corresponding to the service management service when the service management service in the vehicle service management system detects that the vehicle application service corresponding to the service management service has a service anomaly; the anomaly information is used to record the service anomaly of the vehicle application service corresponding to the service management service; The service restart module is used to analyze the abnormal information and restart the vehicle application service with service abnormality.

Images