Optimization processing method and device for interface configuration in multi-client scene and vehicle

Abstract

The invention discloses an optimization processing method and device for interface configuration in a multi-client scene and a vehicle, and the method comprises the steps: generating a signal group mapping table based on an RR interface in an Arxml file, the signal group mapping table comprises a plurality of mapping units, and each mapping unit comprises a mapping relation between a plurality of client function signals and the same function service; for each electronic control unit, traversing the signal group mapping table, only reserving one client function signal associated with the current electronic control unit or found for the first time in each mapping unit, and deleting other redundant client function signals in the mapping unit; and reconstructing the link reference relationship of the socket adapter layer, so that the socket adapter protocol data unit routing configuration is associated to the reconstructed socket connection group when the basic software configuration is generated. According to the scheme, SoAd layer connection configuration is optimized, and a simplified and adaptive communication database is generated for the electronic control unit.

Description

Technical Field

[0001] This application relates to intelligent control technology, and more specifically, to an optimized processing method, device, and vehicle for interface configuration in a multi-client scenario. Background Technology

[0002] For multi-client scenarios using RR (Request / Response) interfaces, traditional solutions typically assign each client an independent signal, PDU (Protocol Data Unit), and socket connection configuration, leading to redundant PDU instantiation. Furthermore, upper-layer software, such as the SoAd layer (Socket Adapter), relies on manual or semi-automated tools to parse multiple sets of redundant information when processing such Arxml data, and by default retains configuration data for all clients.

[0003] However, repeated instantiation of PDUs leads to a large amount of redundant information in the communication database, which in turn increases the memory usage and communication processing load of the ECU. Furthermore, the large amount of redundant information also makes the related parsing work of the upper-layer software cumbersome and prone to errors. Summary of the Invention

[0004] In view of this, this application provides the following technical solution to solve the problems of high memory consumption and communication processing load of ECU caused by repeated instantiation of PDU in traditional solutions:

[0005] The first aspect of this application provides an optimized method for interface configuration in multi-client scenarios, including:

[0006] For the obtained Arxml file, identify and determine all RR interfaces in the Arxml file;

[0007] A signal group mapping table is generated based on all RR interfaces. The signal group mapping table is determined based on function orientation and includes multiple mapping units. Each mapping unit includes the mapping relationship between multiple client function signals and the same function service.

[0008] For each electronic control unit, the signal group mapping table is traversed, and only one client function signal associated with the current electronic control unit or discovered for the first time is retained in each mapping unit. Other redundant client function signals in the mapping unit are deleted to obtain a simplified version of the Arxml file of the current electronic control unit.

[0009] The link reference relationship of the socket adapter layer is reconstructed so that the socket adapter protocol data unit routing configuration is associated with the reconstructed socket connection group when the basic software configuration is generated;

[0010] The reconstructed socket connection group corresponds to a simplified Arxml file after removing redundant client function signals.

[0011] In one possible implementation, identifying all RR interfaces in the obtained Arxml file includes:

[0012] For the obtained Arxml file, identify and determine all RR interfaces in the Arxml file starting from the system signal level.

[0013] In one possible implementation, generating the signal group mapping table based on all RR interfaces includes:

[0014] Generate unique signal key values ​​that do not depend on client identifiers based on the relevant data of each RR interface;

[0015] A cross-client signal aggregation relationship is established based on the unique signal key values ​​of all RR interfaces, forming a function-oriented signal group mapping table.

[0016] In one possible implementation, the traversal of the signal group mapping table, retaining only one client function signal associated with the current electronic control unit or newly discovered in each mapping unit, and deleting other redundant client function signals in the mapping unit, includes:

[0017] Determine whether there are client function signals associated with the current electronic control unit in the mapping unit;

[0018] If present, retain the relevant data of the client function signals associated with the current electronic control unit in the mapping unit;

[0019] If it does not exist, retain the relevant data of the client function signal that was first discovered;

[0020] The data related to client function signals that were not determined to be retained was deleted, resulting in a simplified version of the Arxml file.

[0021] In one possible implementation, the relevant data for the deleted, undetermined retained client function signals includes at least:

[0022] Interface signal Isignal, system signal Syssig, interaction layer protocol data unit Ipdu, signal triggering configuration Isignaltriggering.

[0023] In one possible implementation, the refactoring of the link reference relationships of the socket adapter layer, such that the socket adapter protocol data unit routing configuration is associated with the refactored socket connection group during the generation of the basic software configuration, includes:

[0024] The socket connection instance identifier, which was originally mounted at the socket connection level, is moved to the socket connection bundle level, and the reference path is modified so that the socket adapter protocol data unit routing configuration is associated with the reconstructed socket connection group when the basic software configuration is generated.

[0025] One possible implementation also includes:

[0026] Record statistical information on the deleted redundant client function signals for subsequent verification.

[0027] In one possible implementation, after refactoring the link reference relationships of the socket adapter layer, it also includes:

[0028] Verify the correctness of the socket adapter protocol data unit routing configuration in the basic software configuration corresponding to different electronic control units.

[0029] The second aspect of this application provides an optimized processing device for interface configuration in a multi-client scenario, comprising:

[0030] The interface identification module is used to identify and determine all RR interfaces in the obtained Arxml file;

[0031] The mapping table generation module is used to generate a signal group mapping table based on all RR interfaces. The signal group mapping table is determined based on function orientation and includes multiple mapping units. Each mapping unit includes multiple client function signals and the mapping relationship between the same function service.

[0032] The signal filtering module is used to traverse the signal group mapping table for each electronic control unit, retain only the client function signal associated with the current electronic control unit or the first one discovered in each mapping unit, delete other redundant client function signals in the mapping unit, and obtain a simplified version of the Arxml file of the current electronic control unit.

[0033] The relationship reconstruction module is used to reconstruct the link reference relationship of the socket adapter layer, so that the socket adapter protocol data unit routing configuration is associated with the reconstructed socket connection group when the basic software configuration is generated.

[0034] The reconstructed socket connection group corresponds to a simplified Arxml file after removing redundant client function signals.

[0035] The third aspect of this application provides a vehicle equipped with a simplified Arxml file obtained by the optimized processing method for interface configuration in any of the above-mentioned multi-client scenarios.

[0036] As can be seen from the above technical solutions, this application discloses an optimization processing method, device, and vehicle for interface configuration in a multi-client scenario. The method includes: identifying and determining all RR interfaces in the obtained Arxml file; generating a signal group mapping table based on all RR interfaces, wherein the signal group mapping table is determined based on function orientation and includes multiple mapping units, each mapping unit including multiple client function signals and the same function service mapping relationship; for each electronic control unit, traversing the signal group mapping table, retaining only one client function signal associated with the current electronic control unit or discovered for the first time in each mapping unit, deleting other redundant client function signals in the mapping unit, and obtaining a simplified version of the Arxml file of the current electronic control unit; reconstructing the link reference relationship of the socket adapter layer, so that when the basic software configuration is generated, the socket adapter protocol data unit routing configuration is associated with the reconstructed socket connection group; wherein, the reconstructed socket connection group corresponds to the simplified Arxml file after deleting redundant client function signals. The above solution parses the Arxml file and, in scenarios where there are multiple clients on the RR interface, filters and retains the specified client function signals for each electronic control unit (ECU) while deleting other redundant client function signals. This optimizes the SoAd layer connection configuration, generates a streamlined and adapted communication database for the ECU, reduces the ECU's memory footprint, and improves communication efficiency. Attached Figure Description

[0037] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only embodiments of this application. For those skilled in the art, other drawings can be obtained based on the provided drawings without creative effort.

[0038] Figure 1 This is a flowchart illustrating an optimized interface configuration method in a multi-client scenario disclosed in an embodiment of this application.

[0039] Figure 2 This is a flowchart illustrating the generation of a signal group mapping table as disclosed in an embodiment of this application;

[0040] Figure 3 This is a flowchart illustrating the generation of a simplified Arxml file as disclosed in an embodiment of this application;

[0041] Figure 4 This is a schematic diagram of the structure of an optimized processing device for interface configuration in a multi-client scenario disclosed in an embodiment of this application. Detailed Implementation

[0042] For the sake of clarity and citation, the explanations, abbreviations, or acronyms used in the following text are summarized below:

[0043] ARXML: ARXML files are core configuration files for automotive electronic systems based on the AUTOSAR standard. They use XML format to define the software architecture, communication configuration, and resource allocation of the entire vehicle's electronic system and are a key carrier for enabling collaborative development of different supplier toolchains.

[0044] AUTOSAR: an abbreviation for AUTomotive Open System Architecture.

[0045] ECU: Abbreviation for Electronic Control Unit.

[0046] Syssig: Abbreviation for System Signal.

[0047] Shortname: is the "short name" of all configuration elements in the AUTOSAR Arxml file, and is an element identification attribute defined in the AUTOSAR specification.

[0048] SoAd is an abbreviation for Socket Adaptor, which is the core communication module of the AUTOSAR BSW (basic software) layer.

[0049] SCII: Abbreviation for Socket ConnectionInstance Identifier.

[0050] BSW: Short for Basic Software, it is one of the core layers of the AUTOSAR architecture, located between the Hardware Layer (HW) and the Application Layer (including SWC).

[0051] SoAdRoute: This is a PDU routing rule in the SoAd module, short for "SoAd PDU RoutingConfiguration".

[0052] Isignal: Interface signal, the smallest data unit belonging to the application layer SWC interface (such as the Sender-Receiver Interface), describes the specific data exchanged between SWCs (such as "door status signal", including data type, length, unit, etc.).

[0053] Ipdu: Interaction layer protocol data unit, belonging to the communication layer, is a "transmission unit after signal packaging" - packaging one or more Syssig / Isignal into Ipdu (such as packaging "vehicle speed + braking signal" into "VehCtrl_IPDU") for bus (such as Ethernet) transmission.

[0054] Ipdutriggering: PDU trigger configuration, defines the rules for when Ipdu is sent, such as "event trigger" (sent when the signal value changes), "periodic trigger" (sent at fixed time intervals), and "condition trigger" (sent when specific logic is met).

[0055] Isignaltriggering: Signal triggering configuration, defines the rules for when Isignal triggers subsequent operations, such as "trigger Ipdu packaging when Isignal value changes" or "trigger diagnostic event when Isignal exceeds limit", which is signal-level triggering control.

[0056] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0057] Figure 1 This is a flowchart illustrating an optimized interface configuration method for a multi-client scenario disclosed in an embodiment of this application. Figure 1 The method shown can be applied to the field of automotive intelligent control, as well as to other scenarios where the same service corresponds to multiple different clients.

[0058] See Figure 1 As shown, optimization methods for interface configuration in multi-client scenarios may include:

[0059] Step 101: For the obtained Arxml file, identify and determine all RR interfaces in the Arxml file.

[0060] The RR interface stands for Request / Response interface. In its implementation, after obtaining the ARXML file, all RR interfaces within the file can be parsed and identified. This allows for subsequent analysis of all RR interfaces, determining which signals correspond to which RR interfaces can be aggregated for processing. The parsed content of the RR interfaces includes, but is not limited to, elements such as Syssig and Isignal.

[0061] Regarding Arxml files, during the development of in-vehicle ECUs, automakers may provide Arxml files containing RR interface communication configurations (such as design files that define Syssig, Isignal, Socket connection information for RR interfaces such as seat adjustment and window control) to ECU developers or configuration optimizers for subsequent redundant information processing and communication database generation for specific target ECUs.

[0062] Step 102: Generate a signal group mapping table based on all RR interfaces. The signal group mapping table is determined based on function orientation and includes multiple mapping units. Each mapping unit includes the mapping relationship between multiple client function signals and the same function service.

[0063] The signal group mapping table covers all signals corresponding to the RR interface. Since the same service may correspond to different clients, the signal group mapping table contains multiple mapping units. Each mapping unit contains a functional service and multiple client functional signals corresponding to that functional service. That is, the signal group mapping table contains multiple "many-to-one" mapping units. Here, "many" refers to multiple client functional signals, and "one" refers to a specific functional service.

[0064] Taking the in-vehicle "seat adjustment control RR interface" scenario as an example (identifying the RR interface at the Syssig level), the function-oriented signal group mapping example can be as follows: The unique signal key is "SeatAdj_Req" (ignoring the Client (i.e., client) identifier generation, reflecting the core function of "seat adjustment request"), and the corresponding original signal short names include "Client1_SeatAdj_Req" (initiated by the driver's side ECU), "Client2_SeatAdj_Req" (initiated by the passenger side ECU), and "Client3_SeatAdj_Req" (initiated by the rear control ECU). The function of all three signals is "sending seat adjustment commands (including adjustment direction and angle parameters)", and the RR interface to which they belong is uniformly "SeatCtrl_RR_Interface"; another unique signal key "SeatPos_Resp" (reflecting the "seat position feedback" function), corresponding to the original signal The short names "Client1_SeatPos_Resp", "Client2_SeatPos_Resp", and "Client3_SeatPos_Resp" all have the function of "providing feedback on the current position and adjustment status of the seat". The corresponding RR interface is also "SeatCtrl_RR_Interface". This mapping table aggregates signals initiated / received by different clients with the same function, realizing cross-client function-oriented grouping.

[0065] Step 103: For each electronic control unit, traverse the signal group mapping table, retain only the client function signal associated with the current electronic control unit or the first discovered client function signal in each mapping unit, delete other redundant client function signals in the mapping unit, and obtain a simplified version of the Arxml file of the current electronic control unit.

[0066] Step 103 involves creating a simplified version of the Arxml file for each Electronic Control Unit (ECU) in the vehicle, thus obtaining a communication database adapted to each ECU. The "first discovery" step, which occurs during step 102 when parsing the Arxml file, identifying the RR interface, and generating the signal group mapping table, records different Client groups (client function signals) under the same functional signal group (corresponding to multiple client function signals for the same functional service) in the parsing order. "First discovery" refers to the initial identification and recording of multiple Client groups (client function signals) under the same functional signal group during the signal group mapping table creation process. Based on the "first discovery" results recorded in the signal group mapping table, the corresponding Client group (client function signal) is retained.

[0067] Step 104: Reconstruct the connection reference relationships of the socket adapter layer so that the socket adapter protocol data unit routing configuration is associated with the reconstructed socket connection group when the basic software configuration is generated. The reconstructed socket connection group corresponds to a simplified Arxml file after removing redundant client function signals.

[0068] Since some redundant client function signal data has been removed from the simplified Arxml file, errors may occur if the original socket adapter layer connection reference relationship is followed, resulting in inaccurate referencing. Therefore, it is necessary to reconstruct the connection reference relationship of the socket adapter layer so that the socket adapter protocol data unit routing configuration is associated with the reconstructed socket connection group when the basic software configuration is generated.

[0069] The optimization method for interface configuration in the client scenario described in this embodiment, by parsing the Arxml file, in scenarios where there are multiple clients on the RR interface, filters and retains the specified client signal group (i.e., client function signal) for each electronic control unit (ECU) and deletes other redundant client signal groups, thereby optimizing the SoAd layer connection configuration, generating a simplified and adapted communication database for the electronic control unit (ECU), reducing the overall memory usage of the ECU, and improving communication efficiency.

[0070] In the above embodiments, identifying and determining all RR interfaces in the obtained Arxml file may include: identifying and determining all RR interfaces in the obtained Arxml file starting from the system signal level.

[0071] Understandably, identifying RR interfaces from the ARMX file is more efficient than identifying them from other levels. However, if the RR interfaces are identified from the system signal level, the identification can be completed quickly and efficiently, ensuring the execution efficiency of the solution.

[0072] Figure 2 This is a flowchart illustrating the generation of a signal group mapping table disclosed in an embodiment of this application. (In conjunction with...) Figure 2 As shown, in one implementation, generating a signal group mapping table based on all RR interfaces may include:

[0073] Step 201: Generate a unique signal key value that does not depend on the client identifier based on the relevant data of each RR interface.

[0074] Step 202: Establish cross-client signal aggregation relationships based on the unique signal key values ​​of all RR interfaces to form a function-oriented signal group mapping table.

[0075] In implementation, a unique signal key value (Key) independent of the Client identifier can be generated through a custom algorithm. This key value ignores the Client information in the short Signal name (e.g., "Client1_Signal" and "Client2_Signal" are considered the same functional signal), thereby establishing a cross-Client signal aggregation relationship and forming a function-oriented signal group mapping table. During the process, it is necessary to identify the number of Client groups corresponding to each mapping unit and the associated ECU information, and mark the target Client groups that need to be retained.

[0076] Taking the vehicle-mounted "window lift control RR interface" as an example, after parsing the Arxml file, two signal groups, "WinCtrl_Req" (window lift request) and "WinState_Resp" (window status feedback), are generated in step 102. The "WinCtrl_Req" signal group corresponds to 3 Client groups (associated with the left front door ECU, the central control ECU, and the mobile remote module, respectively), and the "WinState_Resp" signal group corresponds to 3 Client groups (also associated with the above 3 ECUs / modules). If the target ECU is the left front door ECU, the Client group associated with the left front door ECU in the "WinCtrl_Req" signal group and the Client group associated with the left front door ECU in the "WinState_Resp" signal group are identified, and these two Client groups are marked as target Client groups to be retained.

[0077] Figure 3 This is a flowchart illustrating the generation of a simplified Arxml file as disclosed in an embodiment of this application. See also... Figure 3 As shown, in one implementation, traversing the signal group mapping table and retaining only one client function signal associated with the current electronic control unit or discovered for the first time in each mapping unit, while deleting other redundant client function signals in the mapping unit, may include:

[0078] Step 301: Determine whether there is a client function signal associated with the current electronic control unit in the mapping unit, and proceed to step 302 or step 303.

[0079] Step 302: If it exists, retain the relevant data of the client function signals associated with the current electronic control unit in the mapping unit.

[0080] Step 303: If it does not exist, retain the relevant data of the client function signal that was first discovered.

[0081] Step 304: Delete the relevant data of the client function signals that are not determined to be retained, and obtain a simplified version of the Arxml file.

[0082] The data related to the client function signals that were deleted but whose retention was uncertain includes at least the following: interface signal Isignal, system signal Syssig, interaction layer protocol data unit Ipdu, and signal triggering configuration Isignaltriggering.

[0083] Figure 3 The illustrated process can be understood as the associative filtering of target electronic control units (ECUs), or target ECU node associative filtering. The target node can be understood as the ECU that needs to obtain a simplified version of the Arxml file. In implementation, a simplified Arxml communication database adapted to the communication requirements of the target ECU node can be generated. The processing revolves around the processing of redundant information from multiple clients in the RR interface Arxml. The core objective is to filter and retain associated configurations and delete redundant elements (client function signals) based on the identity of the target ECU node, ultimately outputting a communication database adapted to that ECU, rather than generating a general configuration or configurations for other ECUs.

[0084] During the generation of the simplified Arxml file, the signal group mapping table established in step 102 is traversed: if a signal group has a Client group associated with the target ECU, the group is retained first, and the Isignal, Syssig, Ipdu and other elements corresponding to other Client groups are deleted; if the signal group is not directly associated with the target ECU (belonging to communication between other ECUs), the Client group that is discovered for the first time is retained, and the remaining redundant configurations are deleted.

[0085] In one implementation, the reconstructing of the link reference relationship of the socket adapter layer, so that the routing configuration of the socket adapter protocol data unit is associated with the reconstructed socket connection group when the basic software configuration is generated, may include: migrating the socket connection instance identifier originally mounted at the socket connection layer to the socket connection bundle layer, and modifying the reference path so that the routing configuration of the socket adapter protocol data unit is associated with the reconstructed socket connection group when the basic software configuration is generated.

[0086] The above reconstruction process is also known as the reconstruction of connection references in the SoAd layer. When processing the SoAd layer configuration, the SCII (Socket Connection Instance Identifier) ​​originally mounted at the SocketConnection level is migrated to the SocketConnectionBundle level. By modifying the reference path, the SoAdRoute (Socket Adapter Protocol Data Unit Routing Configuration) is automatically associated with the reconstructed SocketConnectionGroup when the Bsw configuration is generated. This operation synchronously updates all relevant references for the retained Client group, ensuring the correctness of communication routing.

[0087] After SCII migrates from the SocketConnection level to the SocketConnectionBundle level, the original Socket connection reference paths of the retained Client group become invalid. If not updated, SoAdRoute will be unable to associate the correct SocketConnectionGroup when generating Bsw configurations later due to referencing the old paths, resulting in interruption of RR interface communication routing. The retained Client group is a key configuration selected in step 103 that is associated with the target ECU (or discovered for the first time). It relies on the correct Socket connection to achieve communication, so its references must be updated synchronously. For example, suppose step 103 retains the configuration related to the "window lift control RR interface" of Client1 (the door ECU itself) and Client2 (the central control ECU) associated with the target "left front door ECU". These two Client groups originally referenced SCII at the SocketConnection level (such as SCII_C1 and SCII_C2). When SCII is migrated to the SocketConnectionBundle level and a unified SCII_Bundle_Win is generated, if the relevant references of Client1 and Client2 are not updated synchronously, SoAdRoute will still try to reference SCII_C1 and SCII_C2, resulting in the inability to find the corresponding Socket connection, and the window lift command cannot be transmitted between the target ECU and Client1 and Client2. After synchronous update, the references of Client1 and Client2 both point to SCII_Bundle_Win, and SoAdRoute can correctly associate SocketConnectionGroup to ensure normal communication.

[0088] In other implementations, the RR interface Arxml optimization processing method in multi-client scenarios may also include: recording statistical information of the deleted redundant client function signals for subsequent verification.

[0089] After reconstructing the link reference relationship of the socket adapter layer, it may also include: verifying the correctness of the socket adapter protocol data unit routing configuration in the basic software configuration corresponding to different electronic control units.

[0090] The proposed solution for optimizing interface configuration in multi-client scenarios first identifies RR interfaces at the Syssig level, ignoring Client identifier information in signal Shortnames and generating unique identifier keys to aggregate signals reused by multiple clients. Second, in the SoAd's Arxml configuration, SCII referenced at the SocketConnection level is migrated to the SocketConnectionBundle level, ensuring that SoAdRoute references the corresponding SocketConnectionGroup when the Bsw configuration is generated. For signal groups serving multiple clients, groups associated with a specific ECU node are prioritized. If the service is unrelated to a specific node (belonging to communication between other ECUs), the first discovered group is retained, and redundant elements such as Isignal, Syssig, Ipdu, Ipduutriggering, Isignaltriggering, and SCII are deleted. This method optimizes the SoAd layer connection configuration, generating a streamlined and adaptable communication database for specific ECU nodes.

[0091] For the foregoing method embodiments, in order to simplify the description, they are all described as a series of actions. However, those skilled in the art should understand that this application is not limited to the described order of actions, because according to this application, some steps can be performed in other orders or simultaneously. Furthermore, those skilled in the art should also understand that the embodiments described in the specification are all preferred embodiments, and the actions and modules involved are not necessarily essential to this application.

[0092] The methods described in the above-disclosed embodiments of this application are detailed in terms of the methods. The methods of this application can be implemented by various forms of apparatus. Therefore, this application also discloses an apparatus. Specific embodiments are given below for detailed description.

[0093] Figure 4 This is a schematic diagram of the structure of an optimized processing device for interface configuration in a multi-client scenario disclosed in an embodiment of this application. See also... Figure 4 As shown, the interface configuration optimization processing device 40 in a multi-client scenario may include:

[0094] The interface identification module 401 is used to identify and determine all RR interfaces in the obtained Arxml file.

[0095] The mapping table generation module 402 is used to generate a signal group mapping table based on all RR interfaces. The signal group mapping table is determined based on function orientation and includes multiple mapping units. Each mapping unit includes multiple client function signals and the mapping relationship between the same function service.

[0096] The signal filtering module 403 is used to traverse the signal group mapping table for each electronic control unit, retain only the client function signal associated with the current electronic control unit or the first one discovered in each mapping unit, delete other redundant client function signals in the mapping unit, and obtain a simplified version of the Arxml file of the current electronic control unit.

[0097] The relationship reconstruction module 404 is used to reconstruct the link reference relationship of the socket adapter layer, so that the socket adapter protocol data unit routing configuration is associated with the reconstructed socket connection group when the basic software configuration is generated.

[0098] The reconstructed socket connection group corresponds to a simplified Arxml file after removing redundant client function signals.

[0099] The interface configuration optimization processing device in the client scenario described in this embodiment, by parsing the Arxml file, in the scenario where there are multiple clients on the RR interface, filters and retains the specified client signal group (i.e., client function signal) for each electronic control unit (ECU) and deletes other redundant client signal groups, thereby optimizing the SoAd layer connection configuration, generating a simplified and adapted communication database for the electronic control unit (ECU), reducing the overall memory usage of the ECU, and improving communication efficiency.

[0100] The specific implementation of the RR interface Arxml optimization processing device and its various modules in the above multi-client scenario, as well as other possible implementations, can be found in the relevant sections of the method embodiments, and will not be repeated here.

[0101] The interface configuration optimization processing device in any of the multi-client scenarios described in the above embodiments includes a processor and a memory. The interface identification module, mapping table generation module, signal filtering module, relationship reconstruction module, etc. in the above embodiments are all stored as program modules in the memory, and the processor executes the above program modules stored in the memory to realize the corresponding functions.

[0102] The processor contains a kernel, which retrieves the corresponding program modules from memory. One or more kernels can be configured, and the processing of backtracking data can be achieved by adjusting kernel parameters.

[0103] The memory may include non-permanent memory in computer-readable media, such as random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM, and the memory includes at least one memory chip.

[0104] In an exemplary embodiment, a computer-readable storage medium is also provided, which can be directly loaded into the internal memory of a computer and contains software code. After being loaded and executed by the computer, the computer program can implement the steps shown in any of the embodiments of the optimized interface configuration processing in the multi-client scenario described above.

[0105] In an exemplary embodiment, a computer program product is also provided, which can be directly loaded into the internal memory of a computer and contains software code. After being loaded and executed by the computer, the computer program can realize the steps shown in any of the embodiments of the optimized interface configuration processing in the multi-client scenario described above.

[0106] Furthermore, this application embodiment provides a vehicle equipped with a simplified Arxml file obtained by any of the optimized processing methods for interface configuration in multi-client scenarios disclosed in the foregoing method embodiments.

[0107] The various embodiments in this specification are described in a progressive manner, with each embodiment focusing on its differences from other embodiments. Similar or identical parts between embodiments can be referred to interchangeably. For the apparatus disclosed in the embodiments, since they correspond to the methods disclosed in the embodiments, the description is relatively simple; relevant parts can be referred to the method section.

[0108] It should also be noted that, in this document, relational terms such as "first" and "second" are used only to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0109] The steps of the methods or algorithms described in conjunction with the embodiments disclosed herein can be implemented directly by hardware, a software module executed by a processor, or a combination of both. The software module can be located in random access memory (RAM), main memory, read-only memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disk, removable disk, CD-ROM, or any other form of storage medium known in the art.

[0110] The above description of the disclosed embodiments enables those skilled in the art to make or use this application. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of this application. Therefore, this application is not to be limited to the embodiments shown herein, but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. An optimized method for interface configuration in a multi-client scenario, characterized in that, include: For the obtained Arxml file, identify and determine all RR interfaces in the Arxml file; A signal group mapping table is generated based on all RR interfaces. The signal group mapping table is determined based on function orientation and includes multiple mapping units. Each mapping unit includes the mapping relationship between multiple client function signals and the same function service. For each electronic control unit, the signal group mapping table is traversed, and only one client function signal associated with the current electronic control unit or discovered for the first time is retained in each mapping unit. Other redundant client function signals in the mapping unit are deleted to obtain a simplified version of the Arxml file of the current electronic control unit. The link reference relationship of the socket adapter layer is reconstructed so that the socket adapter protocol data unit routing configuration is associated with the reconstructed socket connection group when the basic software configuration is generated; The reconstructed socket connection group corresponds to a simplified Arxml file after removing redundant client function signals.

2. The method for optimizing interface configuration in a multi-client scenario according to claim 1, characterized in that, For the obtained Arxml file, identifying and determining all RR interfaces in the Arxml file includes: For the obtained Arxml file, identify and determine all RR interfaces in the Arxml file starting from the system signal level.

3. The method for optimizing interface configuration in a multi-client scenario according to claim 1, characterized in that, The generation of a signal group mapping table based on all RR interfaces includes: Generate unique signal key values ​​that do not depend on client identifiers based on the relevant data of each RR interface; A cross-client signal aggregation relationship is established based on the unique signal key values ​​of all RR interfaces, forming a function-oriented signal group mapping table.

4. The method for optimizing interface configuration in a multi-client scenario according to claim 1, characterized in that, The process of traversing the signal group mapping table retains only one client function signal in each mapping unit that is associated with the current electronic control unit or is discovered for the first time, while deleting other redundant client function signals in the mapping unit, including: Determine whether there are client function signals associated with the current electronic control unit in the mapping unit; If present, retain the relevant data of the client function signals associated with the current electronic control unit in the mapping unit; If it does not exist, retain the relevant data of the client function signal that was first discovered; The data related to client function signals that were not determined to be retained was deleted, resulting in a simplified version of the Arxml file.

5. The method for optimizing interface configuration in a multi-client scenario according to claim 4, characterized in that, The relevant data for deleted client function signals that were not determined to be retained includes at least the following: Interface signal Isignal, system signal Syssig, interaction layer protocol data unit Ipdu, signal triggering configuration Isignaltriggering.

6. The method for optimizing interface configuration in a multi-client scenario according to claim 1, characterized in that, The reconstruction of the link reference relationship of the socket adapter layer, so that the socket adapter protocol data unit routing configuration is associated with the reconstructed socket connection group when the basic software configuration is generated, includes: The socket connection instance identifier, which was originally mounted at the socket connection level, is moved to the socket connection bundle level, and the reference path is modified so that the socket adapter protocol data unit routing configuration is associated with the reconstructed socket connection group when the basic software configuration is generated.

7. The method for optimizing interface configuration in a multi-client scenario according to claim 1, characterized in that, Also includes: Record statistical information on the deleted redundant client function signals for subsequent verification.

8. The method for optimizing interface configuration in a multi-client scenario according to claim 1, characterized in that, After restructuring the link reference relationships of the socket adapter layer, it also includes: Verify the correctness of the socket adapter protocol data unit routing configuration in the basic software configuration corresponding to different electronic control units.

9. An optimization processing device for interface configuration in a multi-client scenario, characterized in that, include: The interface identification module is used to identify and determine all RR interfaces in the obtained Arxml file; The mapping table generation module is used to generate a signal group mapping table based on all RR interfaces. The signal group mapping table is determined based on function orientation and includes multiple mapping units. Each mapping unit includes multiple client function signals and the mapping relationship between the same function service. The signal filtering module is used to traverse the signal group mapping table for each electronic control unit, retain only the client function signal associated with the current electronic control unit or the first one discovered in each mapping unit, delete other redundant client function signals in the mapping unit, and obtain a simplified version of the Arxml file of the current electronic control unit. The relationship reconstruction module is used to reconstruct the link reference relationship of the socket adapter layer, so that the socket adapter protocol data unit routing configuration is associated with the reconstructed socket connection group when the basic software configuration is generated. The reconstructed socket connection group corresponds to a simplified Arxml file after removing redundant client function signals.

10. A vehicle, characterized in that, The configuration includes a simplified version of the Arxml file obtained by the optimized processing method for interface configuration in a multi-client scenario as described in any one of claims 1-8.

Images