Vehicle diagnostic identifier management methods, systems, electronic devices and storage media

By establishing an external management service in the vehicle terminal's software components to receive requests from remote clients and manage diagnostic identifiers, the problem of remote clients being unable to manage vehicle diagnostic identifiers is solved, thereby improving vehicle production and after-sales efficiency.

CN116226135BActive Publication Date: 2026-11-10CHONGQING CHANGAN TECH CO LTD
View PDF 1 Cites 0 Cited by

Patent Information

Application Number
CN202310243208.5
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2023-03-14
Publication Date
2026-11-10
Estimated Expiration
2043-03-14

AI Technical Summary

Technical Problem

The existing AUTOSAR interface is limited to use by local software components, and remote clients cannot easily manage vehicle diagnostic identifiers, resulting in low efficiency in vehicle production and after-sales service.

Method used

By establishing an external management service in the software components of the vehicle terminal, receiving the original management request from the remote client, constructing the service management request, and sending it to the diagnostic identifier service through the runtime environment, remote management of the diagnostic identifier in the vehicle terminal can be realized.

Benefits of technology

It enables remote management of vehicle terminal diagnostic identifiers, improving vehicle production and after-sales efficiency.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN116226135B_ABST
    Figure CN116226135B_ABST
Patent Text Reader

Abstract

This invention relates to the field of data storage technology and discloses a vehicle diagnostic identifier management method, system, electronic device, and storage medium. The method establishes an external management service in software components, receives original management requests from remote clients through this service, constructs a service management request for the target identifier based on the request parameters, and sends the service management request to the diagnostic identifier service through the runtime environment. This allows for the management of the target identifier through the diagnostic identifier service. By receiving original management requests from remote clients through the established external management service, constructing service management requests based on these requests, and managing the target identifier based on the diagnostic identifier service, the method achieves remote management of diagnostic identifiers in vehicle terminals, thereby improving vehicle production and after-sales efficiency.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This invention relates to the field of data storage technology, and in particular to a method, system, electronic device, and storage medium for managing vehicle diagnostic identifiers. Background Technology

[0002] Currently, the configuration storage scheme of traditional automotive ECUs (Electronic Control Units) uses the standard platform UDS (Unified Diagnostic Services) diagnostic protocol to extract autonomous driving data stored in the data recorder. Based on UDS, it performs data retrieval between diagnostic equipment (testers) and the data recorder, extracting data stored in the data recorder and constructing diagnostic messages based on the Unified Diagnostic Services protocol. It has a diagnostic interface for external vehicle diagnostics, connected to the vehicle's bus system via a computer or diagnostic tool (tester). The device that records and stores data when a vehicle equipped with an autonomous driving system is driving in autonomous driving mode is called a data recorder. Therefore, messages defined in UDS can be sent to controllers supporting UDS services, thereby accessing the fault memory of individual control units or updating the ECU program with new firmware. UDS provides the standard AUTOSAR (Automotive Open System Architecture) interface, a standard protocol jointly established by major global automotive OEMs (Original Equipment Manufacturers), component suppliers, and automotive electronics software companies. This protocol specifies an open and standardized software architecture that conforms to automotive electronic software development. The initial AUTOSAR specification only considered traditional automotive electronic and electrical architectures, based on scenarios with limited hardware computing power, and provided defined functions. Currently, the vast majority of manufacturers worldwide develop software based on the AUTOSAR architecture.

[0003] Vehicle production and after-sales service rely heavily on UDS services for vehicle control and diagnostics. However, the AUTOSAR interface is limited to local software components (SWC). Remote clients can only update the storage configuration of diagnostic identifiers by connecting to the UDS diagnostic interface locally, which makes it inconvenient to manage the configuration of diagnostic identifiers and reduces the efficiency of vehicle production and after-sales service. Summary of the Invention

[0004] To provide a basic understanding of some aspects of the disclosed embodiments, a brief summary is given below. This summary is not intended as a general commentary, nor is it intended to identify key / important components or describe the scope of protection of these embodiments, but rather as a prelude to the detailed description that follows.

[0005] In view of the shortcomings of the prior art described above, the present invention discloses a vehicle diagnostic identifier management method, system, electronic device and storage medium to realize remote management of diagnostic identifiers.

[0006] This invention provides a vehicle diagnostic identifier management method applied to a vehicle terminal. The vehicle terminal includes an open system architecture (OSA), which includes software components, a runtime environment, and a diagnostic identifier service. The method includes: establishing an external management service based on the software components, wherein the external management service is connected to a remote client; receiving an original management request corresponding to a target identifier from the remote client through the external management service, wherein the original management request includes request-related parameters corresponding to the target identifier; constructing a service management request corresponding to the target identifier based on the request-related parameters, and sending the service management request to the diagnostic identifier service through the runtime environment; and executing the service management request through the diagnostic identifier service to manage the target identifier.

[0007] Optionally, executing the service management request through the diagnostic identifier service includes: pre-establishing an identifier storage mapping table based on the correspondence between each diagnostic identifier and an identifier storage address in the vehicle terminal; in response to receiving the service management request, parsing the service management request through the diagnostic identifier service to obtain a target management address; matching the identifier storage mapping table according to the target management address to obtain a target identifier corresponding to the target management address, and executing the service management request on the target identifier.

[0008] Optionally, constructing a service management request corresponding to the target identifier based on the request-related parameters includes: if the original management request includes a data write request, then the request-related parameters of the data write request include the data to be written corresponding to the target identifier and the target management address; obtaining a data filling template corresponding to the target identifier, wherein the data filling template includes multiple data bits to be filled, the data bits to be filled include valid data bits, and there is a correspondence between the valid data bits and the data to be written; filling the data to be written into the valid data bits, and determining the data filling template filled with the data to be written as the target data; if the target data has a default data bit, then filling the default data bit of the target data with preset default data, wherein the default data bit includes the data bits to be filled other than the valid data bits; generating a diagnostic identifier write request based on the target management address, the target data, and the target data length of the target data, and using the diagnostic identifier write request as the service management request corresponding to the target identifier, wherein the target data length is used to perform data length verification on the target data.

[0009] Optionally, constructing a service management request corresponding to the target identifier based on the request-related parameters includes: if the original management request includes a data query request, then the request-related parameters of the data query request include a target management address; generating a diagnostic identifier query request based on the target management address, and using the diagnostic identifier query request as the service management request corresponding to the target identifier.

[0010] Optionally, the method further includes: monitoring the data update status of each diagnostic identifier through the diagnostic identifier service; in response to any diagnostic identifier having a data update, collecting the data update information of the diagnostic identifier and sending the data update information to the external management service through the runtime environment; parsing the data update information through the external management service and generating a data update notification for the diagnostic identifier based on the parsing result; and sending the data update notification to the remote client.

[0011] Optionally, before receiving the original management request corresponding to the target identifier from the remote client through the external management service, the method further includes: performing security authentication on the remote client through the external management service to obtain a security authentication result corresponding to the remote client; and receiving the original management request corresponding to the target identifier from the remote client through the external management service after the security authentication result includes successful security authentication.

[0012] Optionally, after executing the service management request through the diagnostic identifier service, the method further includes: obtaining the request execution result corresponding to the service management request, and sending the request execution result to the external management service through the runtime environment; parsing the received request execution result through the external management service, and generating a request result notification corresponding to the original management request based on the parsing result; and sending the request result notification to the remote client.

[0013] This invention provides a vehicle diagnostic identifier management system applied to a vehicle terminal. The vehicle terminal includes an open automotive system architecture, which includes software components, a runtime environment, and a diagnostic identifier service. The system includes: a setup module for establishing an external management service based on the software components, the external management service being connected to a remote client; a receiving module for receiving an original management request corresponding to a target identifier from the remote client through the external management service, wherein the original management request includes request-related parameters corresponding to the target identifier; a construction module for constructing a service management request corresponding to the target identifier based on the request-related parameters, and sending the service management request to the diagnostic identifier service through the runtime environment; and a management module for executing the service management request through the diagnostic identifier service to manage the target identifier.

[0014] The present invention provides an electronic device, comprising: a processor and a memory; the memory is used to store a computer program, and the processor is used to execute the computer program stored in the memory to cause the electronic device to perform the above-described method.

[0015] The present invention provides a computer-readable storage medium having a computer program stored thereon, wherein the computer program, when executed by a processor, implements the above-described method.

[0016] The beneficial effects of this invention are:

[0017] By establishing an external management service within the software component, the system receives raw management requests from remote clients, constructs a service management request for the target identifier based on the request parameters, and sends this request to the diagnostic identifier service via the runtime environment. This allows the diagnostic identifier service to manage the target identifier. In this way, by receiving raw management requests from remote clients through the established external management service, constructing service management requests based on these requests, and managing the target identifier based on the diagnostic identifier service, remote management of diagnostic identifiers in the vehicle terminal is achieved, thereby improving vehicle production and after-sales efficiency. Attached Figure Description

[0018] Figure 1 This is a schematic diagram of the structure of an AUTOSAR ecosystem in an embodiment of the present invention;

[0019] Figure 2 This is a flowchart illustrating a vehicle diagnostic identifier management method according to an embodiment of the present invention;

[0020] Figure 3 This is a schematic diagram of the structure of an AUTOSAR service framework for vehicle diagnostic identifier management in an embodiment of the present invention;

[0021] Figure 4 This is a flowchart illustrating another vehicle diagnostic identifier management method in an embodiment of the present invention;

[0022] Figure 5 This is a flowchart illustrating another vehicle diagnostic identifier management method in an embodiment of the present invention;

[0023] Figure 6 This is a flowchart illustrating another vehicle diagnostic identifier management method in an embodiment of the present invention;

[0024] Figure 7 This is a schematic diagram of the structure of a vehicle diagnostic identifier management system in an embodiment of the present invention;

[0025] Figure 8 This is a schematic diagram of an electronic device according to an embodiment of the present invention. Detailed Implementation

[0026] The following specific examples illustrate the implementation of the present invention. Those skilled in the art can easily understand other advantages and effects of the present invention from the content disclosed in this specification. The present invention can also be implemented or applied through other different specific embodiments, and various details in this specification can also be modified or changed based on different viewpoints and applications without departing from the spirit of the present invention. It should be noted that, unless otherwise specified, the following embodiments and sub-samples in the embodiments can be combined with each other.

[0027] It should be noted that the illustrations provided in the following embodiments are only schematic representations of the basic concept of the present invention. Therefore, the drawings only show the components related to the present invention and are not drawn according to the actual number, shape and size of the components in the actual implementation. In the actual implementation, the form, quantity and proportion of each component can be arbitrarily changed, and the layout of the components may also be more complex.

[0028] In the following description, numerous details are explored to provide a more thorough explanation of embodiments of the invention. However, it will be apparent to those skilled in the art that embodiments of the invention may be practiced without these specific details. In other embodiments, well-known structures and devices are shown in block diagram form rather than in detail to avoid obscuring embodiments of the invention.

[0029] The terms "first," "second," etc., used in the specification, claims, and accompanying drawings of this disclosure are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate for the embodiments of this disclosure described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion.

[0030] Unless otherwise stated, the term "multiple" means two or more.

[0031] In this embodiment of the disclosure, the character " / " indicates that the objects before and after it are in an "or" relationship. For example, A / B means: A or B.

[0032] The term "and / or" describes an association between objects, indicating that three relationships can exist. For example, A and / or B means: A or B, or A and B.

[0033] Combination Figure 1 As shown in the illustration, this disclosure provides a schematic diagram of an AUTOSAR ecosystem, including a software architecture and tool configuration. The top layer of this software architecture is the Application Layer, which deploys several software components. Each SWC (Software Switched Center) implements a specific function. The operation of each SWC requires a runtime environment provided by the RTE (Runtime Environment), which enables communication between internal SWCs and signal and scheduling connections between SWCs and the BSW (Basic Software Switch). The BSW (Basic Software Switch) is referred to as the basic software layer, providing various basic capabilities to the upper-layer SWCs, such as communication capabilities, memory management capabilities, hardware abstraction, and drivers. SWCs implement Ethernet network communication, requiring interaction with the RTE. The RTE hands signals to the BSW for processing and ultimately to the network protocol stack for external transmission. Signal reception is the reverse process and will not be elaborated here. Furthermore, a diagnostic identifier service (Basic_DID / DID basic service) sits between the RTE and the BSW, used to manage diagnostic identifiers in the vehicle's ECU.

[0034] Combination Figure 2As shown, this disclosure provides a vehicle diagnostic identifier management method applied to a vehicle terminal. The vehicle terminal includes an Automotive Open System Architecture (AUTOSAR), which includes software components (SWC), a runtime environment (RTE), and a diagnostic identifier service (Basic_DID). The method includes:

[0035] Step S201: Establish an external management service based on software components;

[0036] The external management service connects to remote clients;

[0037] Step S202: Receive the original management request corresponding to the target identifier from the remote client through the external management service;

[0038] The original management request includes request-related parameters corresponding to the target identifier;

[0039] Step S203: Construct a service management request corresponding to the target identifier based on the request-related parameters, and send the service management request to the diagnostic identifier service through the runtime environment;

[0040] Step S204: Execute a service management request through the diagnostic identifier service to manage the target identifier.

[0041] The vehicle diagnostic identifier management method provided in this disclosure establishes an external management service within a software component. This external management service receives original management requests from remote clients, constructs a service management request for the target identifier based on the request-related parameters of the original management request, and sends the service management request to the diagnostic identifier service through the runtime environment. Thus, the target identifier is managed through the diagnostic identifier service. In this way, by receiving original management requests from remote clients through the established external management service, constructing service management requests based on these requests, and managing the target identifier based on the diagnostic identifier service, remote management of diagnostic identifiers in the vehicle terminal is achieved, thereby improving vehicle production efficiency and after-sales efficiency.

[0042] In some embodiments, the remote client includes a laptop, smartphone, tablet, etc.

[0043] Combination Figure 3As shown, this disclosure provides an AUTOSAR service framework for vehicle diagnostic identifier management. The AUTOSAR service framework includes an external management service, SWC, RTE, diagnostic identifier service, operating system, services, and microcontroller abstraction. The external management service is deployed in the SWC, and its software components connect to the upper layer of the RTE via an AUTOSAR interface. The diagnostic identifier service connects to the lower layer of the RTE via an AUTOSAR interface and provides services through a standardized AUTOSAR interface. The operating system connects to the RTE via a standardized interface and provides services and microcontroller abstraction through a standardized interface.

[0044] The AUTOSAR service framework for vehicle diagnostic identifier management provided in this disclosure establishes an external management service within software components. This external management service receives original management requests from remote clients, constructs a service management request for the target identifier based on the request-related parameters, and sends the service management request to the diagnostic identifier service through the runtime environment. Thus, the target identifier is managed by the diagnostic identifier service. In this way, by receiving original management requests from remote clients through the established external management service, constructing service management requests based on these requests, and managing the target identifier based on the diagnostic identifier service, remote management of diagnostic identifiers in vehicle terminals is achieved, thereby improving vehicle production and after-sales efficiency.

[0045] Optionally, executing a service management request through a diagnostic identifier service includes: pre-establishing an identifier storage mapping table based on the correspondence between each diagnostic identifier in the vehicle terminal and the identifier storage address; in response to receiving a service management request, parsing the service management request through the diagnostic identifier service to obtain the target management address; matching the identifier storage mapping table according to the target management address to obtain the target identifier corresponding to the target management address, and executing a service management request on the target identifier.

[0046] In some embodiments, an identifier storage mapping table is established through the diagnostic protocol interface standardized by the BSW service.

[0047] In some embodiments, the diagnostic identifier is stored in the ECU's NVM (Non-Volatile Memory), wherein the ECU's NVM includes one or more of EEPROM, Data-Flash, Code-Flash, Program-Flash, NOR Flash, and NAND Flash.

[0048] Optionally, after executing the service management request through the diagnostic identifier service, the method further includes: obtaining the request execution result corresponding to the service management request, and sending the request execution result to the external management service through the runtime environment; parsing the received request execution result through the external management service, and generating a request result notification corresponding to the original management request based on the parsing result; and sending the request result notification to the remote client.

[0049] Optionally, constructing a service management request corresponding to the target identifier based on request-related parameters includes: if the original management request includes a data write request, the request-related parameters of the data write request include the data to be written corresponding to the target identifier and the target management address; obtaining a data filling template corresponding to the target identifier, wherein the data filling template includes multiple data bits to be filled, and there are valid data bits among the data bits to be filled, and there is a correspondence between the valid data bits and the data to be written; filling the data to be written into the valid data bits, and determining the data filling template into which the data to be written is the target data; if the target data has default data bits, filling the default data into the default data bits of the target data, wherein the default data bits include the data bits to be filled other than the valid data bits; generating a diagnostic identifier write request based on the target management address, the target data, and the target data length of the target data, and using the diagnostic identifier write request as the service management request corresponding to the target identifier, wherein the target data length is used to perform data length verification on the target data.

[0050] Combination Figure 4 As shown, this disclosure embodiment provides a method for a remote client to write a data write request for an FMH Timer (Follow Me Home Timer, vehicle exterior lighting configuration) through an external management service, including:

[0051] Step S401: The remote client sends a data write request (Set_FMHTimer) to the external management service;

[0052] The request-related parameters for the data write request include the data to be written corresponding to the target identifier and the target management address;

[0053] Step S402: The external management service generates a diagnostic identifier write request (Set_DIDInfo) based on the target management address, target data, and target data length.

[0054] Specifically, the diagnostic identifier writing request is used as the service management request corresponding to the target identifier;

[0055] The target data is obtained by performing data verification on the data to be written, and then filling the data to be written into the data entry template after the data verification is passed. The data verification includes data format, data length, data content, etc.

[0056] Step S403: The external management service sends a service management request to the diagnostic identifier service through the runtime environment;

[0057] Step S404: The diagnostic identifier service updates the target identifier corresponding to the target management address based on the target data;

[0058] Step S405: The diagnostic identifier service generates the request execution result;

[0059] Step S406: The diagnostic identifier service sends a request for the execution result to the external management service;

[0060] Step S407: The external management service parses the received request execution result and generates a request result notification corresponding to the original management request based on the parsing result;

[0061] Step S408: The external management service sends a request result notification to the remote client.

[0062] The remote client provided in this embodiment writes a data write request for an FMHTimer through an external management service. An external management service is established within a software component to receive the original management request from the remote client. Based on the request parameters of the original management request, a service management request for the target identifier is constructed. This service management request is then sent to the diagnostic identifier service through the runtime environment, thereby managing the target identifier through the diagnostic identifier service. In this way, by receiving the original management request from the remote client through the established external management service, constructing a service management request based on the original management request, and managing the target identifier based on the diagnostic identifier service, remote management of diagnostic identifiers in the vehicle terminal is achieved, thereby improving vehicle production efficiency and after-sales efficiency.

[0063] In some embodiments, the correspondence between the data write request for FMHTimer and the diagnostic identifier write request is shown in Table 1. The input parameters of the diagnostic identifier write request include the target management address (DIDDataID), the target data length (DIDDataLen), and the target data (DIDData[]). When the external management service writes data, its target management address must be consistent with the DID in the UDS diagnostics to ensure synchronization with the UDS diagnostic data update. The target data length is used for data verification. If the verification fails, it is not allowed to write to the ECU's NVM to ensure that the data is written correctly. When filling the target data, only the valid data bits are updated, and the remaining non-new data is replaced with 0xFF. The diagnostic identifier service will automatically filter 0xFF data during the identification of valid data to avoid duplicate writing of invalid data.

[0064] Table 1

[0065]

[0066] Optionally, constructing a service management request corresponding to the target identifier based on request-related parameters includes: if the original management request includes a data query request, then the request-related parameters of the data query request include the target management address; generating a diagnostic identifier query request based on the target management address, and using the diagnostic identifier query request as the service management request corresponding to the target identifier.

[0067] Combination Figure 5 As shown, this disclosure provides an embodiment of a remote client writing a data query request for an FMH Timer through an external management service, including:

[0068] Step S501: The remote client sends a data write request (Get_FMHTimer) to the external management service;

[0069] Among them, the request-related parameters for the data write request include the target management address corresponding to the target identifier;

[0070] Step S502: The external management service generates a diagnostic identifier query request (Get_DIDInfo) based on the target management address;

[0071] Specifically, the diagnostic identifier writing request is used as the service management request corresponding to the target identifier;

[0072] Step S503: The external management service sends a service management request to the diagnostic identifier service through the runtime environment;

[0073] Step S504: The diagnostic identifier service reads the target identifier corresponding to the target management address;

[0074] Step S506: The diagnostic identifier service generates the request execution result;

[0075] Step S506: The diagnostic identifier service sends a request for the execution result to the external management service;

[0076] Step S507: The external management service parses the received request execution result and generates a request result notification corresponding to the original management request based on the parsing result;

[0077] Step S508: The external management service sends a request result notification to the remote client.

[0078] The remote client provided in this embodiment writes a data query request for FMHTimer through an external management service. An external management service is established within the software component to receive the original management request from the remote client. Based on the request parameters of the original management request, a service management request for the target identifier is constructed. This service management request is then sent to the diagnostic identifier service through the runtime environment, thereby managing the target identifier through the diagnostic identifier service. In this way, by receiving the original management request from the remote client through the established external management service, constructing a service management request based on the original management request, and managing the target identifier based on the diagnostic identifier service, remote management of diagnostic identifiers in the vehicle terminal is achieved, thereby improving vehicle production efficiency and after-sales efficiency.

[0079] In some embodiments, the correspondence between data query requests for FMHTimer and diagnostic identifier query requests is shown in Table 2.

[0080] Table 2

[0081] Method / Event Name Get_DIDInfo Get_FMHTimer Method / Event Description Diagnostic identifier query request Data query request Service Name Basic_DID Set_FMHTimer(SWC) Service Description Diagnostic Identifier Service External management services RPC type Field Field RPC specific types Getter Getter Input parameters DIDDataID / Output parameters DIDInfo FollowMeHomeTimer Event / Notification Parameters / /

[0082] Optionally, the method further includes: monitoring the data update status of each diagnostic identifier through a diagnostic identifier service; in response to any data update of a diagnostic identifier, collecting the data update information of the diagnostic identifier and sending the data update information to an external management service through a runtime environment; parsing the data update information through the external management service and generating a data update notification for the diagnostic identifier based on the parsing result; and sending the data update notification to a remote client.

[0083] Combination Figure 6 As shown, this disclosure provides a diagnostic identifier service that sends a data update notification for an FMH Timer to a remote client, including:

[0084] Step S601: The diagnostic identifier service detects that any diagnostic identifier has been updated.

[0085] Step S602: The diagnostic identifier service collects data update information (Ntf_DIDInfo);

[0086] The data content of the data update information includes diagnostic identifier data (DIDInfo);

[0087] Step S603: The diagnostic identifier service sends data update information to the external management service;

[0088] Step S604: The external management service parses the data update information and generates a data update notification with diagnostic identifiers based on the parsing results;

[0089] Step S605: The external management service sends a data update notification to the remote client.

[0090] In some embodiments, the correspondence between data update information and data update notifications for FMHTimer is shown in Table 3.

[0091] Table 3

[0092] Method / Event Name Ntf_DIDInfo Ntf_FMHTimer Method / Event Description Data update information Data update notification Service Name Basic_DID Set_FMHTimer(SWC) Service Description Diagnostic Identifier Service External management services RPC type Field Field RPC specific types NotificationEvent NotificationEvent Input parameters DIDDataID / Output parameters / / Event / Notification Parameters DIDInfo FollowMeHomeTimer

[0093] In some embodiments, some parameters in the service management request are shown in Table 4.

[0094] Table 4

[0095]

[0096]

[0097] Optionally, before receiving the original management request corresponding to the target identifier from the remote client through the external management service, the method further includes: performing security authentication on the remote client through the external management service to obtain the security authentication result corresponding to the remote client; and after the security authentication result includes successful security authentication, receiving the original management request corresponding to the target identifier from the remote client through the external management service.

[0098] In some embodiments, after the external management service completes security authentication of the remote client, it calls the diagnostic identifier service to read and write the diagnostic identifier when it receives the original management request, and then sends back the request result notification.

[0099] In this way, the external management service provides a DID management interface for remote clients, and the diagnostic identifier service provides a DID management interface for local clients, thereby completing DID writing, querying, and other related operations.

[0100] Combination Figure 7As shown in the figure, this disclosure provides a vehicle diagnostic identifier management system, characterized in that it is applied to a vehicle terminal. The vehicle terminal includes an open system architecture for automobiles, which includes software components, a runtime environment, and a diagnostic identifier service. The system includes a setup module 701, a receiving module 702, a construction module 703, and a management module 704. The setup module 701 is used to establish an external management service based on the software components. The external management service is connected to a remote client. The receiving module 702 is used to receive an original management request corresponding to a target identifier from the remote client through the external management service. The original management request includes request-related parameters corresponding to the target identifier. The construction module 703 is used to construct a service management request corresponding to the target identifier based on the request-related parameters and send the service management request to the diagnostic identifier service through the runtime environment. The management module 704 is used to execute the service management request through the diagnostic identifier service to manage the target identifier.

[0101] The vehicle diagnostic identifier management system provided in this disclosure establishes an external management service within software components. This external management service receives original management requests from remote clients, constructs a service management request for the target identifier based on the request parameters of the original management request, and sends the service management request to the diagnostic identifier service through the runtime environment. Thus, the target identifier is managed through the diagnostic identifier service. In this way, by receiving original management requests from remote clients through the established external management service, constructing service management requests based on these requests, and managing the target identifier based on the diagnostic identifier service, remote management of diagnostic identifiers in vehicle terminals is achieved, thereby improving vehicle production and after-sales efficiency.

[0102] Figure 8 A schematic diagram of a computer system suitable for implementing the embodiments of this application is shown. It should be noted that... Figure 8 The computer system 800 of the electronic device shown is merely an example and should not impose any limitation on the functionality and scope of use of the embodiments of this application.

[0103] like Figure 8As shown, the computer system 800 includes a Central Processing Unit (CPU) 801, which can perform various appropriate actions and processes, such as executing the methods described in the above embodiments, based on a program stored in Read-Only Memory (ROM) 802 or a program loaded from storage portion 808 into Random Access Memory (RAM) 803. The RAM 803 also stores various programs and data required for system operation. The CPU 801, ROM 802, and RAM 803 are interconnected via a bus 804. An Input / Output (I / O) interface 805 is also connected to the bus 804.

[0104] The following components are connected to I / O interface 805: an input section 806 including a keyboard, mouse, etc.; an output section 807 including a cathode ray tube (CRT), liquid crystal display (LCD), etc., and speakers, etc.; a storage section 808 including a hard disk, etc.; and a communication section 809 including a network interface card such as a LAN (Local Area Network) card, modem, etc. The communication section 809 performs communication processing via a network such as the Internet. A drive 810 is also connected to I / O interface 805 as needed. A removable medium 811, such as a disk, optical disk, magneto-optical disk, semiconductor memory, etc., is installed on drive 810 as needed so that computer programs read from it can be installed into storage section 808 as needed.

[0105] Specifically, according to embodiments of this application, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, embodiments of this application include a computer program product comprising a computer program carried on a computer-readable medium, the computer program including a computer program for performing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via communication section 809, and / or installed from removable medium 811. When the computer program is executed by central processing unit (CPU) 801, it performs various functions defined in the system of this application.

[0106] It should be noted that the computer-readable medium shown in the embodiments of this application can be a computer-readable signal medium or a computer-readable storage medium, or any combination of the two. A computer-readable storage medium can be, for example, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of a computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM), flash memory, optical fiber, portable compact disc read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination thereof. In this application, a computer-readable signal medium may include a data signal propagated in baseband or as part of a carrier wave, carrying a computer-readable computer program. Such propagated data signals can take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. Computer-readable signal media can also be any computer-readable medium other than computer-readable storage media, which can send, propagate, or transmit a program for use by or in connection with an instruction execution system, apparatus, or device. The computer program contained on the computer-readable medium can be transmitted using any suitable medium, including but not limited to wireless, wired, etc., or any suitable combination thereof.

[0107] This disclosure also provides a computer-readable storage medium having a computer program stored thereon that, when executed by a processor, implements any of the methods in this embodiment.

[0108] The computer-readable storage medium in the embodiments of this disclosure will be understood by those skilled in the art: all or part of the steps of the above method embodiments can be implemented by hardware related to computer programs. The aforementioned computer program can be stored in a computer-readable storage medium. When the program is executed, it performs the steps of the above method embodiments; and the aforementioned storage medium includes various media capable of storing program code, such as ROM, RAM, magnetic disk, or optical disk.

[0109] The electronic device disclosed in this embodiment includes a processor, a memory, a transceiver, and a communication interface. The memory and the communication interface are connected to the processor and the transceiver and complete communication between them. The memory is used to store computer programs, the communication interface is used to perform communication, and the processor and the transceiver are used to run the computer programs, so that the electronic device performs the various steps of the above method.

[0110] In this embodiment, the memory may include random access memory (RAM) and may also include non-volatile memory, such as at least one disk storage device.

[0111] The processors mentioned above can be general-purpose processors, including central processing units (CPUs), graphics processing units (GPUs), network processors (NPs), etc.; they can also be digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components.

[0112] The foregoing description and accompanying drawings fully illustrate embodiments of this disclosure to enable those skilled in the art to practice them. Other embodiments may include structural, logical, electrical, procedural, and other changes. The embodiments represent only possible variations. Individual components and functions are optional unless explicitly required, and the order of operation may vary. Parts and subsamples of some embodiments may be included in or replace parts and subsamples of other embodiments. Moreover, the terminology used in this application is for describing embodiments only and is not intended to limit the claims. As used in the description of embodiments and claims, the singular forms “a,” “an,” and “the” are intended to equally include the plural forms unless the context clearly indicates otherwise. Similarly, the term “and / or” as used herein means including one or more of the associated listed items and all possible combinations thereof. Additionally, when used in this application, the term "comprise" and its variations "comprises" and / or "comprising" refer to the presence of stated subsamples, wholes, steps, operations, elements, and / or components, but do not exclude the presence or addition of one or more other subsamples, wholes, steps, operations, elements, components, and / or groups thereof. Without further limitations, an element defined by the phrase "comprising a..." does not exclude the presence of other identical elements in the process, method, or apparatus that includes the element. In this document, each embodiment may focus on the differences from other embodiments, and similar or identical parts between embodiments can be referred to mutually. For methods, products, etc., disclosed in the embodiments, if they correspond to the method section disclosed in the embodiments, the relevant parts can be referred to the description of the method section.

[0113] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of the embodiments of this disclosure. Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0114] The methods and products (including but not limited to devices and equipment) disclosed in the embodiments herein can be implemented in other ways. For example, the device embodiments described above are merely illustrative. For instance, the division of units may be merely a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some sub-samples may be ignored or not executed. In addition, the mutual coupling or direct coupling or communication connection shown or discussed may be through some interfaces, and the indirect coupling or communication connection of devices or units may be electrical, mechanical, or other forms. Units described as separate components may or may not be physically separate, and components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of the units may be selected to implement this embodiment according to actual needs. Furthermore, the functional units in the embodiments of this disclosure may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0115] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to embodiments of this disclosure. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. In some alternative implementations, the functions marked in the blocks may occur in a different order than that shown in the drawings. For example, two consecutive blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. In the descriptions corresponding to the flowcharts and block diagrams in the accompanying drawings, the operations or steps corresponding to different blocks may also occur in a different order than disclosed in the description, and sometimes there is no specific order between different operations or steps. For example, two consecutive operations or steps may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. Each block in a block diagram and / or flowchart, and combinations of blocks in a block diagram and / or flowchart, can be implemented using a dedicated hardware-based system that performs the specified function or action, or using a combination of dedicated hardware and computer instructions.

Claims

1. A method for managing vehicle diagnostic identifiers, characterized in that, Applied to a vehicle terminal, the vehicle terminal comprising an open automotive system architecture, the open automotive system architecture including software components, a runtime environment, and diagnostic identifier services, the method includes: An external management service is established based on the software component, and the external management service is connected to a remote client. The external management service receives the original management request corresponding to the target identifier from the remote client, wherein the original management request includes request-related parameters corresponding to the target identifier; Construct a service management request corresponding to the target identifier based on the request-related parameters, and send the service management request to the diagnostic identifier service through the runtime environment; The service management request is executed through the diagnostic identifier service to manage the target identifier; Executing the service management request through the diagnostic identifier service includes: pre-establishing an identifier storage mapping table based on the correspondence between each diagnostic identifier and an identifier storage address in the vehicle terminal; in response to receiving the service management request, parsing the service management request through the diagnostic identifier service to obtain a target management address; matching the identifier storage mapping table according to the target management address to obtain a target identifier corresponding to the target management address, and executing the service management request on the target identifier; The diagnostic identifier service monitors the data update status of each diagnostic identifier; in response to a data update of any diagnostic identifier, the service collects the data update information of the diagnostic identifier and sends the data update information to the external management service through the runtime environment; the external management service parses the data update information and generates a data update notification for the diagnostic identifier based on the parsing result; and sends the data update notification to the remote client. Constructing a service management request corresponding to the target identifier based on the request-related parameters includes: if the original management request includes a data write request, then the request-related parameters of the data write request include the data to be written corresponding to the target identifier and the target management address; obtaining a data filling template corresponding to the target identifier, wherein the data filling template includes multiple data positions to be filled, the data positions to be filled include valid data positions, and there is a correspondence between the valid data positions and the data to be written; filling the data to be written into the valid data positions, and determining the data filling template filled with the data to be written as the target data; if the target data has a default data position, then filling the default data position of the target data with preset default data, wherein the default data position includes the data positions to be filled other than the valid data positions; generating a diagnostic identifier write request based on the target management address, the target data, and the target data length of the target data, and using the diagnostic identifier write request as the service management request corresponding to the target identifier, wherein the target data length is used to perform data length verification on the target data.

2. The method according to claim 1, characterized in that, Constructing a service management request corresponding to the target identifier based on the request-related parameters includes: If the original management request includes a data query request, then the request-related parameters of the data query request include the target management address; A diagnostic identifier query request is generated based on the target management address, and the diagnostic identifier query request is used as the service management request corresponding to the target identifier.

3. The method according to any one of claims 1 to 2, characterized in that, Before receiving the original management request corresponding to the target identifier from the remote client via the external management service, the method further includes: The remote client is authenticated using the external management service to obtain the corresponding security authentication result for the remote client. After the security authentication result is passed, the external management service receives the original management request corresponding to the target identifier from the remote client.

4. The method according to any one of claims 1 to 2, characterized in that, After executing the service management request through the diagnostic identifier service, the method further includes: Obtain the request execution result corresponding to the service management request, and send the request execution result to the external management service through the runtime environment; The external management service parses the received request execution result and generates a request result notification corresponding to the original management request based on the parsing result; Send the request result notification to the remote client.

5. A vehicle diagnostic identifier management system, characterized in that, Applied to a vehicle terminal, the vehicle terminal includes an open automotive system architecture, which includes software components, a runtime environment, and diagnostic identifier services. The system includes: A module is established to create an external management service based on the software component, wherein the external management service is connected to a remote client. The receiving module is configured to receive an original management request corresponding to a target identifier from the remote client through the external management service, wherein the original management request includes request-related parameters corresponding to the target identifier; The construction module is used to construct a service management request corresponding to the target identifier based on the request-related parameters, and send the service management request to the diagnostic identifier service through the runtime environment; The management module is used to execute the service management request through the diagnostic identifier service to manage the target identifier; The management module executes the service management request through the diagnostic identifier service in the following manner: First, it establishes an identifier storage mapping table in advance based on the correspondence between each diagnostic identifier and its storage address in the vehicle terminal. Upon receiving the service management request, it parses the request through the diagnostic identifier service to obtain the target management address. Then, it matches the identifier storage mapping table with the target management address to obtain the target identifier corresponding to the target management address, and executes the service management request on the target identifier. The management module is further configured to: monitor the data update status of each diagnostic identifier through the diagnostic identifier service; in response to any diagnostic identifier having a data update, collect the data update information of the diagnostic identifier and send the data update information to the external management service through the runtime environment; parse the data update information through the external management service and generate a data update notification for the diagnostic identifier based on the parsing result; and send the data update notification to the remote client. The management module constructs a service management request corresponding to the target identifier based on the request-related parameters in the following manner: if the original management request includes a data write request, the request-related parameters of the data write request include the data to be written corresponding to the target identifier and the target management address; obtains a data filling template corresponding to the target identifier, wherein the data filling template includes multiple data positions to be filled, and the data positions to be filled include valid data positions, and there is a correspondence between the valid data positions and the data to be written; fills the data to be written into the valid data positions, and determines the data filling template filled with the data to be written as the target data; if the target data has a default data position, fills the default data of the target data into the default data position of the target data, wherein the default data position includes the data positions to be filled other than the valid data positions; generates a diagnostic identifier write request based on the target management address, the target data, and the target data length of the target data, and uses the diagnostic identifier write request as the service management request corresponding to the target identifier, wherein the target data length is used to perform data length verification on the target data.

6. An electronic device, characterized in that, include: Processor and memory; The memory is used to store a computer program, and the processor is used to execute the computer program stored in the memory to cause the electronic device to perform the method as described in any one of claims 1 to 4.

7. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, it implements the method as described in any one of claims 1 to 4.

Citation Information

Patent Citations

  • Apparatus for extracting driving data of autonomous vehicle, and system and method thereof

    CN115512456A