Configuration method and device

Abstract

The invention provides a configuration method and device. The method comprises: obtaining a domain specific language (DSL) file, the DSL file comprising a communication relationship between a first node and a second node, the communication relationship indicating that the first node communicates with the second node based on a first topic; and according to the DSL file, determining an ARXML file related to a communication management CM in an automobile open system architecture AUTOSAR. According to the method and the device, the configuration workload when a user configures the ARXML file can be reduced, and the configuration efficiency is improved.

Description

Configuration method and device Technical Field

[0001] The present application relates to the field of smart cars, and more specifically, to a configuration method and device. Background Art

[0002] Automotive electronic networks are evolving towards multi-bus hybrid interconnections. In 2003, the automotive industry introduced the Automotive Open System Architecture (AUTOSAR) specification to mitigate compatibility issues among major manufacturers. Each automaker can develop its own software based on the AUTOSAR specification.

[0003] To meet the increasingly complex demands of automobiles (such as autonomous driving, connected vehicles, and domain control), the industry has defined the AUTOSAR Adaptive Platform (AP), building on the proven experience of the traditional AUTOSAR Classic Platform (CP). Communication management (CM) is a key function in the AP, determining the overall system software architecture and the collaborative relationships between software components.

[0004] Currently, users can only manually configure CM-related AUTOSAR extensible markup language (ARXML) files, also known as configuration files, using the Artop configuration tool (an official AUTOSAR configuration tool). This results in very low CM configuration efficiency.

[0005] Summary of the Invention

[0006] The present application provides a configuration method and apparatus that can reduce the configuration workload of users when configuring ARXML files and improve configuration efficiency.

[0007] In a first aspect, the present application provides a configuration method, the method comprising: obtaining a domain specific language (DSL) file, the DSL file including a communication relationship between a first node and a second node, the communication relationship indicating that the first node communicates with the second node based on a first topic; and determining, based on the DSL file, an ARXML file related to a CM in AUTOSAR.

[0008] In this application, the communication relationship between the first and second nodes included in the DSL file can be used to automatically generate the CM-related ARXML file in AUTOSAR, eliminating the need for manual configuration by the user. This can reduce the user's configuration workload and improve configuration efficiency. Furthermore, the user only needs to be familiar with communication methods similar to the Robot Operating System (ROS) to write the DSL file, which can then be input into the configuration tool to obtain the CM-related ARXML file in AUTOSAR. This eliminates the need for the user to be familiar with the AP, reducing the user's learning curve during the configuration process. For users who have already developed a function on ROS, the migration cost of migrating the ROS-based function to the AP can be reduced.

[0009] In combination with the first aspect, in certain implementations of the first aspect, the data type of the first topic is a first data type, and the service interface (ServiceInterface) type corresponding to the first data type is a first service interface type, wherein, based on the DSL file, determining the ARXML file related to the CM in AUTOSAR includes: determining a first service interface deployment item (ServiceInterfaceDeployment) based on the first topic; and establishing an association relationship between the first service interface deployment item and the first service interface type.

[0010] In this application, the first service interface deployment item can be automatically generated using the information in the first topic of the DSL file, and an association relationship between the first service interface deployment item and the first service interface type can be established. This eliminates the need for users to manually configure the service interface deployment item or manually establish an association between the service interface deployment item and the service interface type, thereby reducing the user's configuration workload and improving configuration efficiency.

[0011] In some possible implementations, the communication protocol corresponding to the first topic may default to data distribution service (DDS), and determining the first service interface deployment item based on the first topic includes: determining the DDS service interface deployment item (DdsServiceInterfaceDeployment) based on the first topic.

[0012] In combination with the first aspect, in certain implementations of the first aspect, the DSL file also includes information on the communication protocol corresponding to the first subject, wherein determining the first service interface deployment item based on the first subject includes: determining the first service interface deployment item based on the first subject and the information on the communication protocol.

[0013] In this application, the first service interface deployment item can be automatically generated by combining the first topic and the communication protocol information corresponding to the first topic in the DSL file. In this way, the flexibility of generating the service interface deployment item can be improved by combining the communication protocol information.

[0014] In some possible implementations, determining the first service interface deployment item based on the first topic and information about the communication protocol includes: when the communication protocol is DDS, determining a DDS service interface deployment item based on the first topic.

[0015] In some possible implementations, the first service interface deployment item is determined based on information about the first topic and the communication protocol, including: when the communication protocol is scalable service-oriented middleware over IP (SOME / IP), based on the first topic, determining the SOME / IP service interface deployment item (SomeIpServiceInterfaceDeployment).

[0016] In combination with the first aspect, in certain implementations of the first aspect, the DSL file also includes information on one or more data types, and the one or more data types include the first data type. Before determining the first service interface deployment item based on the first subject, the method also includes: determining the service interface type corresponding to each data type in the one or more data types.

[0017] In this application, the service interface type corresponding to each of the one or more data types in the DSL file can be automatically determined by one or more data types. This eliminates the need for users to manually configure the service interface type, reducing the user's configuration workload and improving configuration efficiency.

[0018] In combination with the first aspect, in some implementations of the first aspect, the first node is a publishing node and the second node is a subscribing node, wherein, based on the DSL file, determining the ARXML file related to the CM in AUTOSAR further includes: determining a first provider service instance (ProvidedServiceInstance) corresponding to the first node and a first requester service instance (RequiredServiceInstance) corresponding to the second node; and establishing an association relationship between the first provider service instance, the first requester service instance, and the first service interface deployment item.

[0019] In this application, the information in the first node of a DSL file can be used to automatically generate its corresponding provider service instance, and the information in the second node can be used to automatically generate its corresponding requester service instance. This eliminates the need for users to manually create provider and requester service instances, or to manually create associations between provider and requester service instances and service interface deployment items, reducing user configuration workload and improving configuration efficiency.

[0020] In some possible implementations, determining the first provider-side service instance corresponding to the first node and the first requester-side service instance corresponding to the second node includes: determining the first provider-side service instance corresponding to the first node and the first requester-side service instance corresponding to the second node based on information of the communication protocol corresponding to the first topic.

[0021] For example, when the communication protocol corresponding to the first topic is DDS, a first DDS provider service instance (DdsProvidedServiceInstance) corresponding to the first node and a first DDS requester service instance (DdsRequiredServiceInstance) corresponding to the second node may be determined.

[0022] For another example, when the communication protocol corresponding to the first topic is SOME / IP, the first SOME / IP provider service instance (ProvidedSomeipServiceInstance) corresponding to the first node can be determined and the first SOME / IP requester service instance (RequiredSomeipServiceInstance) corresponding to the second node can be determined.

[0023] In combination with the first aspect, in certain implementations of the first aspect, the communication protocol corresponding to the first topic is DDS, the DSL file also includes first information, and the first information indicates the type of the transmission plug-in. Determining the ARXML file related to the CM in AUTOSAR based on the DSL file also includes: determining the transmission plug-in based on the first information.

[0024] In this application, the transmission plug-in can be automatically created through the first information in the DSL file. In this way, the user does not need to manually create the transmission plug-in, which can reduce the user's configuration workload and improve configuration efficiency.

[0025] In some possible implementations, the type of the transport plug-in includes shared memory or User Datagram Protocol (UDP).

[0026] In combination with the first aspect, in certain implementations of the first aspect, the communication relationship further indicates that the first node communicates with the third node based on the first topic, wherein, based on the DSL file, determining the ARXML file related to the CM in AUTOSAR also includes: determining the second request-side service instance corresponding to the third node; establishing an association relationship between the first provider service instance, the second request-side service instance and the first service interface deployment item; or, determining the second provider service instance corresponding to the first node, and the second request-side service instance corresponding to the third node; establishing an association relationship between the second provider service instance, the second request-side service instance and the first service interface deployment item.

[0027] In this application, when the communication relationship also indicates that the first node communicates with a third node based on the first topic, a second requester service instance corresponding to the third node can be automatically generated and an association relationship can be established between the first provider service instance, the second requester service instance, and the first service interface deployment item. In this way, in a one-sender-multiple-receiver scenario, communication between one provider service instance and two requester service instances can be achieved.

[0028] Alternatively, when the communication relationship further indicates that the first node communicates with the third node based on the first topic, a second provider service instance corresponding to the first node and a second requester service instance corresponding to the third node can be automatically generated, and an association relationship between the second provider service instance, the second requester service instance, and the first service interface deployment item can be established. In this way, in a one-transmit-multiple-receive scenario, multiple pairs of service instances can be created based on the number of communication links, thereby enabling communication between the provider service instance and the requester service instance in each pair of service instances.

[0029] In combination with the first aspect, in certain implementations of the first aspect, determining the ARXML file related to the CM in AUTOSAR based on the DSL file also includes: determining a first process (process), a first process design (ProcessDesign), a first executable program (executable, exe) and a first software component (SwComponentType, swc) related to the first provider service instance, and establishing an association relationship between the first process and the first process design, the first process design and the first executable program, the first process and the first executable program, and the first executable program and the first software component; determining a second process, a second process design, a second executable program and a second software component related to the first requester service instance, and establishing an association relationship between the second process and the second process design, the second process design and the second executable program, the second process and the second executable program, and the second executable program and the second software component.

[0030] In this application, after determining the first provider service instance and the first requester service instance, the process, process design, executable program, and software component corresponding to the service instance can also be automatically determined, and the association relationship between the process and the process design, the process design and the executable program, the process and the executable program, and the executable program and the software component can be established. In this way, the user does not need to manually create the process, process design, executable program, and software component corresponding to each service instance, nor does the user need to manually create the association relationship between the process and the process design, the process design and the executable program, the process and the executable program, and the executable program and the software component, which can reduce the user's configuration workload and improve configuration efficiency.

[0031] In combination with the first aspect, in certain implementations of the first aspect, determining the ARXML file related to the CM in AUTOSAR based on the DSL file also includes: determining the provided port (ProvidedPortPrototype, PPort) corresponding to the first software component and determining the request port (RequiredPortPrototype, RPort) corresponding to the second software component; establishing an association relationship between the provided port, the request port and the first service interface type; determining a first mapping and a second mapping, the first mapping being a mapping relationship between the first provider service instance and the provided port, and the second mapping being a mapping relationship between the first requester service instance and the request port.

[0032] In this application, after determining the first software component and the second software component, a provision port corresponding to the first software component and a request port corresponding to the second software component can also be automatically created, an association between the provision port, the request port, and the first service interface type is established, and a first mapping and a second mapping are created. This eliminates the need for the user to manually configure the provision port and the request port, or to manually create an association between the provision port, the request port, and the first service interface type, or to create a service instance to port mapping (ServiceInstanceToPortMapping), thereby reducing the user's configuration workload and improving configuration efficiency.

[0033] In a second aspect, the present application provides a configuration device, characterized in that it includes an acquisition unit and a processing unit, wherein the acquisition unit is used to acquire a domain-specific language DSL file, the DSL file including a communication relationship between a first node and a second node, the communication relationship indicating that the first node communicates with the second node based on a first topic; the processing unit is used to determine an ARXML file related to the CM in AUTOSAR based on the DSL file.

[0034] In combination with the second aspect, in certain implementations of the second aspect, the data type of the first subject is a first data type, and the service interface type corresponding to the first data type is a first service interface type. The processing unit is used to: determine a first service interface deployment item based on the first subject; and establish an association relationship between the first service interface deployment item and the first service interface type.

[0035] In combination with the second aspect, in some implementations of the second aspect, the DSL file also includes information about the communication protocol corresponding to the first topic, and the processing unit is used to determine the first service interface deployment item based on the information about the first topic and the communication protocol.

[0036] In combination with the second aspect, in certain implementations of the second aspect, the DSL file also includes information on one or more data types, and the one or more data types include the first data type. The processing unit is further used to: before determining the first service interface deployment item, determine the service interface type corresponding to each data type in the one or more data types.

[0037] In combination with the second aspect, in certain implementations of the second aspect, the first node is a publishing node, the second node is a subscribing node, and the processing unit is further used to: determine the first provider service instance corresponding to the first node and the first requester service instance corresponding to the second node; establish an association relationship between the first provider service instance, the first requester service instance and the first service interface deployment item.

[0038] In combination with the second aspect, in certain implementations of the second aspect, the communication protocol corresponding to the first topic is DDS, and the DSL file also includes first information, which indicates the type of transmission plug-in. The processing unit is also used to: determine the transmission plug-in based on the first information.

[0039] In combination with the second aspect, in certain implementations of the second aspect, the communication relationship also indicates that the first node communicates with the third node based on the first topic, and the processing unit is also used to: determine the second request-end service instance corresponding to the third node; establish an association relationship between the first provider service instance, the second request-end service instance and the first service interface deployment item; or, determine the second provider service instance corresponding to the first node, and the second request-end service instance corresponding to the third node; establish an association relationship between the second provider service instance, the second request-end service instance and the first service interface deployment item.

[0040] In combination with the second aspect, in certain implementations of the second aspect, the processing unit is further used to: determine the first process, first process design, first executable program and first software component related to the first provider service instance, and establish an association relationship between the first process and the first process design, the first process design and the first executable program, the first process and the first executable program, and the first executable program and the first software component; determine the second process, second process design, second executable program and second software component related to the first requester service instance, and establish an association relationship between the second process and the second process design, the second process design and the second executable program, the second process and the second executable program, and the second executable program and the second software component.

[0041] In combination with the second aspect, in certain implementations of the second aspect, the processing unit is further used to: determine the provision port corresponding to the first software component and determine the request port corresponding to the second software component; establish an association relationship between the provision port, the request port and the first service interface type; determine a first mapping and a second mapping, the first mapping being a mapping relationship between the first provision-side service instance and the provision port, and the second mapping being a mapping relationship between the first request-side service instance and the request port.

[0042] In a third aspect, the present application provides a configuration device, which includes: a memory for storing a computer program; and a processor for executing the computer program stored in the memory, so that the device performs a configuration method as in any possible implementation of the first aspect.

[0043] In a fourth aspect, the present application provides an electronic device, which includes a configuration device as in any possible implementation of the second aspect or the third aspect.

[0044] In a fifth aspect, the present application provides a computer program product, which includes: computer program code, which, when running on a computer, enables the computer to execute the configuration method in any possible implementation of the first aspect.

[0045] It should be noted that the above-mentioned computer program code may be stored in whole or in part on a first storage medium, wherein the first storage medium may be packaged together with the processor or separately from the processor.

[0046] In a sixth aspect, the present application provides a computer-readable medium, which stores instructions. When the instructions are executed by a processor, the processor implements the configuration method in any possible implementation of the first aspect.

[0047] In a seventh aspect, the present application provides a chip, which includes a circuit for executing the configuration method in any possible implementation of the first aspect above. BRIEF DESCRIPTION OF THE DRAWINGS

[0048] FIG1 is a schematic diagram of the software architecture of the automotive open system architecture adaptive platform;

[0049] Figure 2 is a schematic diagram of the communication between the server and the client in CM;

[0050] Figure 3 is a schematic diagram of communication between a publisher node and a subscriber node in ROS;

[0051] FIG4 is a schematic flow chart of a configuration method provided in an embodiment of the present application;

[0052] FIG5 is a schematic diagram of the structure of a DSL file provided in an embodiment of the present application;

[0053] FIG6 is another schematic flow chart of the configuration method provided in an embodiment of the present application;

[0054] 7 is a schematic diagram of the association between the service interface deployment items and their corresponding service interface types provided in an embodiment of the present application;

[0055] FIG8 is another schematic flow chart of the configuration method provided in an embodiment of the present application;

[0056] FIG9 is another schematic flow chart of the configuration method provided in an embodiment of the present application;

[0057] FIG10 is a schematic diagram of generating a provider service instance and a requester service instance in an embodiment of the present application;

[0058] FIG11 is a schematic diagram of a one-transmit-multiple-receive scenario provided in an embodiment of the present application;

[0059] FIG12 is another schematic diagram of a one-transmit-multiple-receive scenario provided in an embodiment of the present application;

[0060] FIG13 is a schematic diagram of a generation process, process design, executable program, and software components provided in an embodiment of the present application;

[0061] FIG14 is another schematic flow chart of a configuration method provided in an embodiment of the present application;

[0062] FIG15 is a schematic diagram of generating a service instance to port mapping provided in an embodiment of the present application;

[0063] FIG16 is a schematic block diagram of a configuration device provided in an embodiment of the present application;

[0064] FIG17 is another schematic block diagram of a configuration device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0065] The technical solution in this application will be described below with reference to the accompanying drawings.

[0066] Figure 1 shows the software architecture of the AUTOSAR AP, an open automotive system architecture adaptation platform. This software architecture is divided into the application layer, runtime layer, basic service layer, and hardware layer. The basic service layer includes communication management (CM), network management, state management, update configuration management, cryptography, time synchronization, diagnostics, persistence, and execution management. CM is a key function in the AP, determining the overall system software architecture and the collaborative relationships between software components.

[0067] Figure 2 shows a schematic diagram of communication between a server (skeleton) and a client (proxy) in CM. As shown in Figure 2, the server publishes a service and registers it in the service registry. The client subscribes to the requested service by querying the service registry, thus enabling communication between the server and client.

[0068] Currently, users can only manually configure CM-related ARXML files in the Artop configuration tool. For example, when configuring one-to-one communication, users need to manually configure over 20 configuration items. These include process-related configurations such as process, executable (exe), process design (ProcessDesign), software component (SWC), port (PortPrototype, Port), service instance (ServiceInstance), service instance-to-port mapping (ServiceInstanceToPortMapping), service interface (ServiceInterface), and service interface deployment (ServiceInterfaceDeployment). Service instances include provided service instances (ProvidedServiceInstance) and required service instances (RequiredServiceInstance), and ports include provided ports (PPort) and requested ports (RPort). Some common configuration items include core types (CoreTypes). Furthermore, each configuration item, in addition to its own configuration properties, also includes related references. Therefore, users also need to manually configure the relationship between process and ProcessDesign, between ProcessDesign and exe, and between exe and SWC. This results in very inefficient CM configuration.

[0069] ROS is an operating system for robots. The most commonly used communication method in ROS is the topic. A topic is a one-way, point-to-point communication method, where "point" refers to a node. This means that nodes can exchange information based on topics.

[0070] Figure 3 illustrates the communication between publisher and subscriber nodes in ROS. As shown in Figure 3, both publisher and subscriber nodes must register with the node manager (ROS master). After registration, the publisher node can publish topic-related content to the node manager, while the subscriber node declares the topics it subscribes to, thus establishing communication between the publisher and subscriber nodes.

[0071] In the robotics and autonomous driving fields, a large number of developers are already familiar with the communication methods of message-based middleware (ROS). Similar communication mechanisms have also made their way into the internet. Developers are more accustomed to the message-based middleware framework and are reluctant to learn the complexities of APIs. Migrating ROS communication to the CM within the API would require developers to learn the complex API, resulting in a high learning curve.

[0072] The inventors of this application discovered that CM communication in APs and topic communication in ROS share many similarities: both use a publish-and-subscribe model and use a single medium to carry transmitted information. Based on this discovery, embodiments of this application provide a configuration method and device that automatically generates ARXML files related to CM in AUTOSAR through the communication relationships between nodes included in a DSL file. This eliminates the need for manual configuration by the user, reducing the user's configuration workload and improving configuration efficiency. Furthermore, users only need to be familiar with ROS-like communication methods to write a DSL file, which can then be input into a configuration tool to obtain ARXML files related to CM in AUTOSAR. This eliminates the need for user familiarity with APs, reducing the user's learning curve during the configuration process. For users who have already developed a function in ROS, this can reduce the cost of migrating the ROS-based function to the AP.

[0073] Fig. 4 shows a schematic flow chart of a configuration method 400 provided in an embodiment of the present application. The method 400 may include steps S401 to S402.

[0074] S401 , obtaining a DSL file, where the DSL file includes a communication relationship between a first node and a second node, where the communication relationship indicates that the first node communicates with the second node based on a first topic.

[0075] Exemplarily, the DSL file may include a communication relationship between publisher node 1 and subscriber node 1 , where the communication relationship indicates that publisher node 1 communicates with subscriber node 1 based on topic 1 (Topic 1 ).

[0076] The above publishing end node 1 may be the above first node, the subscription end node 1 may be the above second node, and Topic 1 may be the above first topic.

[0077] The above communication between publisher node 1 and subscriber node 1 based on topic 1 can also be understood as publisher node 1 publishing topic 1 and subscriber node 1 subscribing to topic 1.

[0078] In one embodiment, the DSL file may further include information of a first data type corresponding to the first topic. For example, the data type 1 corresponding to the topic 1 is controller area network (CAN) data.

[0079] In one embodiment, the DSL file may include information of multiple data types, including the first data type, for example, Ethernet (ETH) data and CAN data.

[0080] In one embodiment, the DSL file may further include information about the communication protocol corresponding to the first topic, such as DDS or SOME / IP.

[0081] In one embodiment, the DSL file may also include information about the machines where the first node and the second node are deployed. For example, publisher node 1 and subscriber node 1 are deployed on the same machine, or publisher node 1 and subscriber node 1 are deployed on different machines.

[0082] For example, Figure 5 shows a schematic diagram of the structure of a DSL file provided in an embodiment of the present application. As shown in Figure 5, the DSL file may include data type configuration, topic configuration, and communication configuration. The data type configuration may include information about one or more data types required for communication; the topic configuration may include information about one or more topics and the data type corresponding to each of the one or more topics; and the communication configuration may include information about topics published by a publishing node and topics subscribed to by a subscribing node.

[0083] The DSL file described above can be a file abstracted by developers by combining the concepts related to CM in ROS and AP. After understanding the communication method of ROS, developers can manually write the DSL file and input it into the configuration tool.

[0084] S402: Determine an ARXML file related to the CM in AUTOSAR according to the DSL file.

[0085] In one embodiment, the method 400 further includes: obtaining a data type header file, where the data type header file indicates a data type related to the AP; and determining a core type (CoreTypes) based on the data type header file.

[0086] Exemplarily, the data type header file may be a C++ data type header file.

[0087] For example, Table 1 shows the corresponding relationship between attributes and values ​​in the CAN-related configuration items in CoreTypes.

[0088] Table 1

[0089] Property Value Type Category STRUCTURE Short Name CAN

[0090] It should be understood that the attribute information of CoreTypes shown in Table 1 above is not limited thereto, and may include more or less attribute information, and the values ​​are only examples and are not limited thereto.

[0091] It should also be understood that CoreTypes may include other configuration items in addition to configuration items related to CAN. For example, CoreTypes may also include configuration items related to ETH.

[0092] In one embodiment, the data type of the first topic is a first data type, and the service interface type corresponding to the first data type is a first service interface type, wherein determining the ARXML file related to the CM in AUTOSAR based on the DSL file includes: determining a first service interface deployment item based on the first topic; and establishing an association relationship between the first service interface deployment item and the first service interface type.

[0093] Figure 6 shows a schematic flow chart of a configuration method 600 provided in an embodiment of the present application. Method 600 may be an implementation process of determining a service interface deployment item related to a CM in AUTOSAR in S402. Method 600 may include steps S601 to S604.

[0094] S601 , traverse the topic configuration in the DSL file, where the topic configuration includes information of one or more topics, and the one or more topics include the first topic.

[0095] For example, the content of the theme configuration in the DSL file is as follows:

[0096] Name:Topic1

[0097] Datatype:DataType1

[0098] Use_some_ip:true

[0099] Name:Topic2

[0100] Datatype:DataType1

[0101] Use_some_ip:false

[0102] As can be seen from the above topic configuration, the topic configuration includes two topics, named Topic1 and Topic2. Among them, the data type corresponding to Topic1 is DataType1 and the communication protocol corresponding to Topic1 is SOME / IP. The data type corresponding to Topic2 is DataType1 and the communication protocol corresponding to Topic2 is DDS.

[0103] S602: Determine, based on the one or more topics, a service interface deployment item corresponding to each of the one or more topics.

[0104] In one embodiment, the DSL file also includes information on the communication protocol corresponding to the first subject, wherein determining the first service interface deployment item based on the first subject includes: determining the first service interface deployment item based on the first subject and the information on the communication protocol.

[0105] Exemplarily, taking the first topic as Topic1 as an example, SomeIpServiceInterfaceDeployment can be generated according to Topic1 and its corresponding communication protocol (SOME / IP).

[0106] Exemplarily, taking the first topic as Topic2 as an example, a DdsServiceInterfaceDeployment can be generated based on Topic2 and its corresponding communication protocol (DDS).

[0107] It should be understood that the above topic configuration may not include information about the communication protocol. The configuration tool may generate a DdsServiceInterfaceDeployment or a SomeIpServiceInterfaceDeployment for each topic.

[0108] S603: Set a value corresponding to the service interface identifier (Service Interface Id) for the service interface deployment item corresponding to each theme.

[0109] In one embodiment, the values ​​corresponding to the Service Interface Id in the service interface deployment items corresponding to different themes are different, or the value corresponding to the Service Interface Id can identify the corresponding theme.

[0110] For example, for the SomeIpServiceInterfaceDeployment corresponding to Topic1, the value corresponding to Service Interface Id can be set to 1; for the DdsServiceInterfaceDeployment corresponding to Topic2, the value corresponding to Service Interface Id can be set to 2.

[0111] For example, Topic 1 may be a camera. After setting a value corresponding to the service interface identifier for SomeIpServiceInterfaceDeployment, the corresponding relationship between attributes and values ​​in SomeIpServiceInterfaceDeployment may be as shown in Table 2.

[0112] Table 2

[0113] propertyvalueService Interface Id1Short NameCameraSomeIpServiceInterfaceDeploymentServiceInterface

[0114] As can be seen from Table 2, before associating SomeIpServiceInterfaceDeployment with the service interface type, the configuration tool can set the value corresponding to Service Interface Id in SomeIpServiceInterfaceDeployment to 1 and the value corresponding to Short Name to CameraSomeIpServiceInterfaceDeployment. In this case, the value corresponding to ServiceInterface can be empty.

[0115] S604: Establish an association relationship between each service interface deployment item and its corresponding service interface type.

[0116] Figure 7 shows a schematic diagram of the association between the service interface deployment items provided by an embodiment of the present application and their corresponding service interface types. From the content of the topic configuration, it can be seen that the data type corresponding to Topic1 is DataType1, where the service interface type corresponding to DataType1 is service interface type 1 (for example, Datatype1 is CAN, and the service interface corresponding to service interface type 1 can be CanServiceInterface). Then the configuration tool can establish an association relationship between SomeIpServiceInterfaceDeployment and service interface type 1.

[0117] For example, after the association relationship between SomeIpServiceInterfaceDeployment and service interface type 1 is established, the corresponding relationship between attributes and values ​​in SomeIpServiceInterfaceDeployment may be as shown in Table 3.

[0118] Table 3

[0119] propertyvalue

[0120] Service Interface Id1Short NameSomeIpServiceInterfaceDeploymentServiceInterfaceCanServiceInterface

[0121] As can be seen from Table 3, after associating SomeIpServiceInterfaceDeployment with service interface type 1, the configuration tool can set the value corresponding to ServiceInterface to CanServiceInterface, thereby indicating that the association relationship between SomeIpServiceInterfaceDeployment and service interface type 1 has been established.

[0122] It should be understood that the attribute information of SomeIpServiceInterfaceDeployment shown in Table 2 and Table 3 above is not limited thereto, and may include more or less attribute information, and the values ​​are only examples and are not limited thereto.

[0123] The above service interface types can be manually configured by the user in the configuration tool, or generated by the configuration tool based on the data type configuration in the DSL file.

[0124] In one embodiment, the DSL file also includes information on one or more data types, and the one or more data types include the first data type. Before determining the first service interface deployment item based on the first subject, the method also includes: determining the service interface type corresponding to each data type in the one or more data types.

[0125] Figure 8 shows a schematic flow chart of a configuration method 800 provided in an embodiment of the present application. Method 800 may be an implementation process of determining the service interface type related to the CM in AUTOSAR in S402. Method 800 may include steps S801 to S803.

[0126] S801: Traverse the data type configuration in the DSL file, where the data type configuration includes information of one or more data types, and the one or more data types include the first data type.

[0127] For example, the data type configuration in the DSL file is as follows:

[0128] Name:DataType1

[0129] Struct:CAN

[0130] Name:DataType2

[0131] Struct:ETH

[0132] As can be seen from the above data type configuration, the data type configuration includes two differently named data types, namely DataType1 and DataType2. Among them, the data structure corresponding to DataType1 is CAN and the data structure corresponding to DataType2 is ETH.

[0133] S802: Determine, according to each data type of the one or more data types, a service interface type corresponding to each data type.

[0134] Exemplarily, for DataType1, its corresponding service interface type 1 may be determined, and the type of the service interface type 1 is related to CAN.

[0135] Exemplarily, for DataType2, its corresponding service interface type 2 may be determined, and the type of the service interface type 2 is related to ETH.

[0136] S803: Establish an association relationship between each service interface type and CoreTypes.

[0137] Taking the configuration items related to CAN in CoreTypes shown in Table 1 as an example, an association relationship between service interface type 1 and the configuration items related to CAN can be established.

[0138] In one embodiment, the first node is a publishing node and the second node is a subscribing node, wherein determining the ARXML file related to the CM in AUTOSAR based on the DSL file further includes: determining a first provider service instance corresponding to the first node and a first requester service instance corresponding to the second node; and establishing an association relationship between the first provider service instance, the first requester service instance, and the first service interface deployment item.

[0139] Figure 9 shows a schematic flow chart of a configuration method 900 provided in an embodiment of the present application. The method 900 may be an implementation process of determining a service instance related to a CM in AUTOSAR in S402. The method 900 may include steps S901 to S904.

[0140] S901, traverse the communication configuration in the DSL file, the communication configuration includes the communication relationship between the publisher node 1 and the subscriber node 1, the communication relationship indicating that the publisher node 1 communicates with the subscriber node 1 based on Topic 1.

[0141] For example, the content of the theme configuration in the DSL file is as follows:

[0142] Name:publisher1

[0143] publishTopic:Topic1

[0144] Name:subscriber1

[0145] subscribeTopic:Topic1

[0146] From the above communication configuration, it can be seen that publisher node 1 publishes Topic 1 and subscriber node 1 subscribes to Topic 1.

[0147] S902 , determining the provider service instance 1 corresponding to the publisher node 1 and determining the requester service instance 1 corresponding to the subscriber node 1 .

[0148] The above publishing-end service instance 1 may be the above-mentioned first providing-end service instance, and the requesting-end service instance 1 may be the above-mentioned first requesting-end service instance.

[0149] For example, Figure 10 shows a schematic diagram of generating a provider service instance and a requester service instance in an embodiment of the present application. As shown in Figure 10, the configuration tool can traverse the nodes that publish and subscribe to the same topic in the communication configuration. When it is determined that publisher node 1 has published Topic 1 and subscriber node 1 has subscribed to Topic 1, the provider service instance 1 corresponding to publisher node 1 can be determined, and the requester service instance 1 corresponding to subscriber node 1 can be determined.

[0150] In one embodiment, determining the provider service instance 1 corresponding to the publisher node 1 and determining the requester service instance 1 corresponding to the subscriber node 1 includes: determining the provider service instance 1 corresponding to the publisher node 1 and determining the requester service instance 1 corresponding to the subscriber node 1 based on information of the communication protocol corresponding to Topic1.

[0151] Exemplarily, the communication protocol corresponding to Topic 1 is SOME / IP, then the provider service instance 1 may be ProvidedSomeipServiceInstance and the requester service instance 1 may be RequiredSomeipServiceInstance.

[0152] S903: Set the values ​​corresponding to the service instance identifiers (ServiceInstanceId) of the provider service instance 1 and the requester service instance 1.

[0153] In one embodiment, in order to ensure that the provider service instance 1 and the requester service instance 1 can communicate normally, the values ​​corresponding to the service instance identifiers of the provider service instance 1 and the requester service instance 1 may be set to the same value.

[0154] S904: Establish an association relationship between the provider service instance 1, the requester service instance 1, and the SomeIpServiceInterfaceDeployment corresponding to the Topic1.

[0155] For example, Table 4 shows the correspondence between attributes and values ​​in ProvidedSomeipServiceInstance.

[0156] Table 4

[0157] propertyvalueServiceInstanceId1Short NameProvidedSomeipServiceInstanceServiceInterfaceDeploymentSomeIpServiceInterfaceDeployment

[0158] For example, Table 5 shows the corresponding relationship between attributes and values ​​in RequiredSomeipServiceInstance.

[0159] Table 5

[0160] propertyvalueRequiredServiceInstanceId1Short NameRequiredSomeipServiceInstanceServiceInterfaceDeploymentSomeIpServiceInterfaceDeployment

[0161] From the corresponding relationship between the attributes and values ​​shown in Table 4 and Table 5 above, it can be seen that ProvidedSomeipServiceInstance and RequiredSomeipServiceInstance are associated with SomeIpServiceInterfaceDeployment respectively, and the ServiceInstanceId of ProvidedSomeipServiceInstance is the same as the RequiredServiceInstanceId of RequiredSomeipServiceInstance.

[0162] In one embodiment, the above establishment of an association relationship between the provider service instance 1, the requester service instance 1, and the SomeIpServiceInterfaceDeployment corresponding to the Topic 1 can also be understood as establishing an association relationship between the service instance identifier of the provider service instance 1, the service instance identifier of the requester service instance 1, and the SomeIpServiceInterfaceDeployment corresponding to the Topic 1. For example, an association relationship can be established between the service instance with ServiceInstanceId 1 and SomeIpServiceInterfaceDeployment.

[0163] Since the association relationship between SomeIpServiceInterfaceDeployment and service interface type 1 has been established in method 600, establishing the association relationship between ProvidedSomeipServiceInstance, RequiredSomeipServiceInstance and SomeIpServiceInterfaceDeployment can also be understood as establishing the association relationship between ProvidedSomeipServiceInstance, RequiredSomeipServiceInstance and service interface type 1.

[0164] In one embodiment, the communication protocol corresponding to the first topic is DDS, and the DSL file also includes first information, which indicates the type of the transmission plug-in. Determining the ARXML file related to the CM in AUTOSAR based on the DSL file also includes: determining the transmission plug-in based on the first information.

[0165] For example, the content of the theme configuration in the DSL file is as follows:

[0166] Name:publisher2

[0167] publishTopic:Topic2

[0168] Transport plugins:UDP

[0169] Name:subscriber2

[0170] subscribeTopic:Topic2

[0171] Transport plugins:UDP

[0172] From the above communication configuration, it can be seen that publisher node 2 publishes Topic 2 and subscriber node 2 subscribes to Topic 2. Since the communication protocol corresponding to Topic 2 is DDS, the communication configuration can also include information about the type of transport plugins.

[0173] For example, Table 6 shows the corresponding relationship between attributes and values ​​in the provider service instance DdsProvidedServiceInstance determined according to the publisher node 2.

[0174] Table 6

[0175] propertyvalueServiceInstanceId3Short NameDdsProvidedServiceInstanceServiceInterfaceDeploymentDdsServiceInterfaceDeployment

[0176] Transport pluginsUDP

[0177] It should be understood that the attribute information of the service instances shown in Table 4, Table 5 and Table 6 above is not limited thereto, and may include more or less attribute information, and the values ​​are only examples and are not limited thereto.

[0178] In one embodiment, the communication relationship further indicates that the first node communicates with the third node based on the first topic, wherein, based on the DSL file, determining the ARXML file related to the CM in AUTOSAR also includes: determining the second requester service instance corresponding to the third node; and establishing an association relationship between the first provider service instance, the second requester service instance and the first service interface deployment item.

[0179] For example, Figure 11 shows a schematic diagram of a send-multiple-receive scenario provided by an embodiment of the present application. As shown in Figure 11, publisher node 1 publishes Topic 1, and subscriber node 1 and subscriber node 3 (subscriber 3) both subscribe to Topic 1. The configuration tool can also determine the requester service instance 2 corresponding to subscriber node 3 and establish an association relationship between provider service instance 1, requester service instance 2, and the SomeIpServiceInterfaceDeployment corresponding to Topic 1.

[0180] The above requester service instance 2 may be the above second requester service instance.

[0181] For example, the configuration tool can set the value corresponding to the service instance identifier of the requesting service instance 2 to 1. In this way, by setting the values ​​corresponding to the service instance identifiers of the providing service instance 1 and the requesting service instance 2 to 1, an association relationship can be established between the providing service instance 1, the requesting service instance 2, and the SomeIpServiceInterfaceDeployment corresponding to the above Topic1.

[0182] In one embodiment, the communication relationship further indicates that the first node communicates with the third node based on the first topic, wherein the determining of the ARXML file related to the CM in AUTOSAR based on the DSL file also includes: determining a second provider service instance corresponding to the first node, and a second requester service instance corresponding to the third node; and establishing an association relationship between the second provider service instance, the second requester service instance, and the first service interface deployment item.

[0183] For example, Figure 12 shows another schematic diagram of a one-send-multiple-receive scenario provided by an embodiment of the present application. As shown in Figure 12, publisher node 1 publishes Topic 1, and subscriber node 1 and subscriber node 3 both subscribe to Topic 1. The configuration tool can also determine the provider service instance 2 corresponding to the publisher node 1 and the requester service instance 2 corresponding to the subscriber node 3, and establish an association relationship between the provider service instance 2, the requester service instance 2, and the SomeIpServiceInterfaceDeployment corresponding to the above-mentioned Topic 1.

[0184] The above provider service instance 2 may be the above second provider service instance, and the requester service instance 2 may be the above second requester service instance.

[0185] For example, the configuration tool can set the value corresponding to the service instance identifier of the provider service instance 2 and the value corresponding to the service instance identifier of the requester service instance 2 to 2. In this way, by setting the value corresponding to the service instance identifier of the provider service instance 2 and the value corresponding to the service instance identifier of the requester service instance 2 to 2, an association relationship can be established between the provider service instance 2, the requester service instance 2, and the SomeIpServiceInterfaceDeployment corresponding to the above Topic1.

[0186] In one embodiment, the method further includes: determining a service instance to machine mapping (ServiceInstanceToMachineMapping).

[0187] Exemplarily, the ServiceInstanceToMachineMapping may be generated according to whether the publisher node 1 and the subscriber node 1 are deployed on the same machine.

[0188] For example, corresponding ServiceInstanceToMachineMappings may be generated for provider service instance 1 and requester service instance 1, respectively. Alternatively, multiple service instances associated with the same communication connector may be merged to generate a ServiceInstanceToMachineMapping that can associate the multiple service instances with the communication connector.

[0189] In one embodiment, determining an ARXML file related to a CM in AUTOSAR based on the DSL file further includes: determining a first process, a first process design, a first executable program, and a first software component related to the first provider service instance, and establishing associations between the first process and the first process design, the first process design and the first executable program, the first process and the first executable program, and the first executable program and the first software component; and determining a second process, a second process design, a second executable program, and a second software component related to the first requester service instance, and establishing associations between the second process and the second process design, the second process design and the second executable program, the second process and the second executable program, and the second executable program and the second software component.

[0190] Figure 13 shows a schematic diagram of a generated process, process design, executable program, and software component provided by an embodiment of the present application. As shown in Figure 13, after determining the provider service instance 1 corresponding to the publisher node 1, the corresponding process 1 (process 1), process design 1 (ProcessDesign 1, not shown in the figure), executable program 1 (exe1), and software component 1 (swc1) can also be determined, and associations are established between process 1 and ProcessDesign 1, ProcessDesign 1 and exe1, process 1 and exe1, and exe1 and swc1.

[0191] The above process 1 may be the above first process, ProcessDesign 1 may be the above first process design, exe1 may be the above first executable program, and swc1 may be the above first software component.

[0192] Similarly, after determining the request-side service instance 1 corresponding to the subscriber node 1 as mentioned above, the process 2 (process 2), process design 2 (ProcessDesign 2, not shown in the figure), executable program 2 (exe2) and software component 2 (swc2) corresponding to the request-side service instance 1 can also be determined and the association relationships between process 2 and ProcessDesign 2, ProcessDesign 2 and exe2, process 2 and exe 2, and exe2 and swc2 can be established.

[0193] The above process 2 may be the second process, ProcessDesign 2 may be the second process design, exe2 may be the second executable program, and swc2 may be the second software component.

[0194] In one embodiment, determining the ARXML file related to the CM in AUTOSAR based on the DSL file also includes: determining the provision port corresponding to the first software component and determining the request port corresponding to the second software component; establishing an association relationship between the provision port, the request port and the first service interface type; and determining a first mapping and a second mapping, the first mapping being a mapping relationship between the first provider service instance and the provision port, and the second mapping being a mapping relationship between the first requester service instance and the request port.

[0195] Figure 14 shows a schematic flow chart of a configuration method 1400 provided in an embodiment of the present application. Method 1400 may be an implementation of determining ports and service instance-to-port mappings (ServiceInstanceToPortMapping) associated with a CM in AUTOSAR in S402. Method 1400 may include steps S1401 to S1403.

[0196] S1401, determine the provision port 1 (PPort1) corresponding to swc1 and determine the request port 1 (RPort1) corresponding to swc2.

[0197] For example, after determining the swc1 corresponding to the provider service instance 1, the PPort1 corresponding to the swc1 can also be determined. After determining the swc2 corresponding to the requester service instance 1, the RPort1 corresponding to the swc2 can also be determined.

[0198] S1402: Establish an association relationship between PPort1, RPort1, and service interface type 1.

[0199] The above establishment of the association relationship between PPort1, RPort1 and service interface type 1 can also be understood as establishing the association relationship between PPort1, RPort1 and the service interface corresponding to service interface type 1.

[0200] S1403, establish a provider service instance to port mapping and a requester service instance to port mapping, wherein the provider service instance to port mapping is a mapping relationship between the provider service instance 1 and PPort1, and the requester service instance to port mapping is a mapping relationship between the requester service instance 1 and RPort1.

[0201] The above provider service instance to port mapping may be the above first mapping, and the requester service instance to port mapping may be the above second mapping.

[0202] FIG15 shows a schematic diagram of generating a service instance to port mapping (ServiceInstanceToPortMapping) provided in an embodiment of the present application.

[0203] For example, Table 7 shows the corresponding relationship between attributes and values ​​in the mapping from provider service instance to port.

[0204] Table 7

[0205] propertyvalueProcessProcess1Service InstanceProvidedSomeipServiceInstanceTarget Port PrototypePPort1

[0206] For example, Table 8 shows the corresponding relationship between attributes and values ​​in the mapping from the requester service instance to the port.

[0207] Table 8

[0208] propertyvalueProcessProcess2Service InstanceRequiredSomeipServiceInstanceTarget Port PrototypeRPort1

[0209] It should be understood that the attribute information of the service instance to port mapping shown in Table 7 and Table 8 above is not limited thereto, and may include more or less attribute information, and the values ​​are only examples and are not limited thereto.

[0210] The configuration method provided by the embodiment of the present application is described in detail above in conjunction with Figures 1 to 15. The configuration method in the above embodiment can be executed by a configuration tool, or it can also be executed by a system-on-chip (SoC) in the configuration tool; or it can also be executed by a processor in the configuration tool; or it can also be executed by the following configuration device. The configuration device provided by the embodiment of the present application will be described in detail below in conjunction with Figures 16 and 17. It should be understood that the description of the device embodiment corresponds to the description of the method embodiment. Therefore, for the content that is not described in detail, please refer to the above method embodiment. For the sake of brevity, it will not be repeated here.

[0211] FIG16 shows a schematic block diagram of a configuration device 1600 according to an embodiment of the present application. As shown in FIG16 , the configuration device 1600 includes an acquisition unit 1610 and a processing unit 1620 .

[0212] The apparatus 1600 may include units for executing the methods in Figures 4, 6, 8, 9, and 14. Furthermore, each unit in the apparatus 1600 is for implementing the corresponding process of the method embodiments in Figures 4, 6, 8, 9, and 14.

[0213] When the device 1600 is used to execute the method 400 in FIG. 4 , the acquiring unit 1610 may be used to execute S401 in the method 400 , and the processing unit 1620 may be used to execute S402 in the method 400 .

[0214] Exemplarily, the acquisition unit 1610 is configured to acquire a DSL file, where the DSL file includes a communication relationship between a first node and a second node, where the communication relationship indicates that the first node communicates with the second node based on a first topic; and the processing unit 1620 is configured to determine, based on the DSL file, an ARXML file related to the CM in AUTOSAR.

[0215] Optionally, the data type of the first topic is the first data type, and the service interface type corresponding to the first data type is the first service interface type. The processing unit 1620 is used to: determine the first service interface deployment item based on the first topic; and establish an association relationship between the first service interface deployment item and the first service interface type.

[0216] Optionally, the DSL file further includes information about a communication protocol corresponding to the first subject, wherein the processing unit 1620 is configured to determine the first service interface deployment item based on the information about the first subject and the communication protocol.

[0217] Optionally, the DSL file also includes information on one or more data types, and the one or more data types include the first data type. The processing unit 1620 is also used to: before determining the first service interface deployment item, determine the service interface type corresponding to each data type in the one or more data types.

[0218] Optionally, the first node is a publishing node, the second node is a subscribing node, and the processing unit 1620 is also used to: determine the first provider service instance corresponding to the first node and the first requester service instance corresponding to the second node; establish an association relationship between the first provider service instance, the first requester service instance and the first service interface deployment item.

[0219] Optionally, the communication protocol corresponding to the first topic is DDS, and the DSL file also includes first information, which indicates the type of the transmission plug-in. The processing unit 1620 is further used to: determine the transmission plug-in according to the first information.

[0220] Optionally, the communication relationship also indicates that the first node communicates with the third node based on the first topic, and the processing unit 1620 is also used to: determine the second request-end service instance corresponding to the third node; establish an association relationship between the first provider service instance, the second request-end service instance and the first service interface deployment item; or, determine the second provider service instance corresponding to the first node, and the second request-end service instance corresponding to the third node; establish an association relationship between the second provider service instance, the second request-end service instance and the first service interface deployment item.

[0221] Optionally, the processing unit 1620 is further used to: determine the first process, first process design, first executable program and first software component related to the first provider service instance, and establish an association relationship between the first process and the first process design, the first process design and the first executable program, the first process and the first executable program, and the first executable program and the first software component; determine the second process, second process design, second executable program and second software component related to the first requester service instance, and establish an association relationship between the second process and the second process design, the second process design and the second executable program, the second process and the second executable program, and the second executable program and the second software component.

[0222] Optionally, the processing unit 1620 is further used to: determine the provision port corresponding to the first software component and determine the request port corresponding to the second software component; establish an association relationship between the provision port, the request port and the first service interface type; determine a first mapping and a second mapping, the first mapping being a mapping relationship between the first provision-side service instance and the provision port, and the second mapping being a mapping relationship between the first request-side service instance and the request port.

[0223] It should be understood that the division of the units in the above device is only a division of logical functions, and in actual implementation, they can be fully or partially integrated into one physical entity, or they can be physically separated.

[0224] Figure 17 is a schematic block diagram of a configuration device 1700 provided in an embodiment of the present application. The configuration device 1700 shown in Figure 17 may include a processor 1710, a transceiver 1720, and a memory 1730. The processor 1710, transceiver 1720, and memory 1730 are connected via an internal connection path. The memory 1730 is configured to store instructions, and the processor 1710 is configured to execute the instructions stored in the memory 1730 to receive and transmit data via the transceiver 1720. Optionally, the memory 1730 may be coupled to the processor 1710 via an interface or may be integrated with the processor 1710.

[0225] It should be noted that the transceiver 1720 may include but is not limited to a transceiver device such as an input / output interface to implement communication between the device 1700 and other devices or communication networks.

[0226] The memory 1730 may be a read-only memory (ROM), a static storage device, a dynamic storage device, or a random access memory (RAM).

[0227] In one implementation, processor 1710 may be a circuit capable of reading and executing instructions, such as a central processing unit (CPU), a microprocessor, or a digital signal processor (DSP). In another implementation, processor 1710 may implement certain functions through the logical relationships of a hardware circuit, where the logical relationships of the hardware circuit are fixed or reconfigurable. For example, processor 1710 may be a hardware circuit implemented by an application-specific integrated circuit (ASIC) or a programmable logic device (PLD), such as a field programmable gate array (FPGA). In a reconfigurable hardware circuit, the process of the processor loading a configuration file to implement hardware circuit configuration can be understood as the process of the processor loading instructions to implement the functions of some or all of the above units.

[0228] An embodiment of the present application further provides an electronic device, which may include the above-mentioned configuration device 1600, or the above-mentioned configuration device 1700.

[0229] An embodiment of the present application further provides a computer program product, which includes: computer program code, which, when executed on a computer, enables the computer to execute the configuration method in the above embodiment.

[0230] An embodiment of the present application further provides a computer-readable medium, wherein the computer-readable medium stores a program code. When the computer program code is run on a computer, the computer executes the configuration method in the above embodiment.

[0231] An embodiment of the present application also provides a chip, including a circuit, for executing the configuration method in the above embodiment.

[0232] During implementation, each step of the above method can be completed by an integrated logic circuit of the hardware in the processor or by instructions in the form of software. The method disclosed in conjunction with the embodiments of the present application can be directly embodied as being executed by a hardware processor, or can be executed by a combination of hardware and software modules in the processor. The software module can be located in a storage medium mature in the art such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory, or a power-on erasable programmable memory, a register, etc. The storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware. To avoid repetition, it will not be described in detail here.

[0233] It should also be understood that in the various embodiments of the present application, the size of the serial numbers of the above-mentioned processes does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

[0234] Those skilled in the art will clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0235] In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are merely schematic. For example, the division of the units is merely a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0236] The units described as separate components may or may not be physically separate, and the 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 these units may be selected to achieve the purpose of this embodiment according to actual needs.

[0237] In addition, each functional unit in each embodiment of the present application 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.

[0238] If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art, or the part of the technical solution, can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes several instructions for enabling a computer device (which can be a personal computer, server, or network device, etc.) to execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes various media that can store program codes, such as a USB flash drive, a mobile hard disk, a ROM, a RAM, a magnetic disk, or an optical disk.

[0239] The above is only a specific implementation method of the present application, but the protection scope of the present application is not limited thereto. Any changes or replacements that can be easily thought of by any technician familiar with this technical field within the technical scope disclosed in this application should be covered.

Claims

1. A configuration method, characterized in that: include: Obtaining a domain specific language (DSL) file, the DSL file including a communication relationship between a first node and a second node, the communication relationship indicating that the first node communicates with the second node based on a first topic; According to the DSL file, an ARXML file related to the communication management CM in the automotive open system architecture AUTOSAR is determined.

2. The method according to claim 1, wherein The data type of the first subject is the first data type, and the service interface type corresponding to the first data type is the first service interface type. The step of determining an ARXML file related to a CM in AUTOSAR according to the DSL file includes: Determine a first service interface deployment item based on the first topic; Establish an association relationship between the first service interface deployment item and the first service interface type.

3. The method according to claim 2, wherein The DSL file also includes information about the communication protocol corresponding to the first topic. The step of determining the first service interface deployment item according to the first topic includes: Determine the first service interface deployment item based on information about the first topic and the communication protocol.

4. The method according to claim 2 or 3, wherein: The DSL file further includes information on one or more data types, where the one or more data types include the first data type. Before determining the first service interface deployment item based on the first topic, the method further includes: According to each data type of the one or more data types, a service interface type corresponding to each data type is determined.

5. The method according to claim 4, wherein The first node is a publishing node, and the second node is a subscribing node. Wherein, determining the ARXML file related to the CM in AUTOSAR according to the DSL file further includes: Determine a first provider service instance corresponding to the first node and a first requester service instance corresponding to the second node; Establish an association relationship among the first provider service instance, the first requester service instance and the first service interface deployment item.

6. The method according to claim 5, wherein The communication protocol corresponding to the first topic is Data Distribution Service DDS, and the DSL file further includes first information indicating the type of the transmission plug-in. Wherein, determining the ARXML file related to the CM in AUTOSAR according to the DSL file further includes: A transmission plug-in is determined according to the first information.

7. The method according to claim 5 or 6, wherein: The communication relationship further indicates that the first node communicates with the third node based on the first topic, The step of determining an ARXML file related to a CM in AUTOSAR according to the DSL file further includes: Determining a second requester service instance corresponding to the third node; Establishing an association relationship between the first provider service instance, the second requester service instance, and the first service interface deployment item; or, Determining a second provider service instance corresponding to the first node and a second requester service instance corresponding to the third node; Establish an association relationship between the second provider service instance, the second requester service instance and the first service interface deployment item.

8. The method according to any one of claims 5 to 7, characterized in that The step of determining an ARXML file related to a CM in AUTOSAR according to the DSL file further includes: Determining a first process, a first process design, a first executable program, and a first software component associated with the first provider service instance, and establishing associations between the first process and the first process design, the first process design and the first executable program, the first process and the first executable program, and the first executable program and the first software component; Determine a second process, a second process design, a second executable program, and a second software component related to the first requester service instance, and establish association relationships between the second process and the second process design, the second process design and the second executable program, the second process and the second executable program, and the second executable program and the second software component.

9. The method according to claim 8, wherein The step of determining an ARXML file related to a CM in AUTOSAR according to the DSL file further includes: Determining a provided port corresponding to the first software component and determining a requested port corresponding to the second software component; Establishing an association relationship between the providing port, the requesting port and the first service interface type; A first mapping and a second mapping are determined, wherein the first mapping is a mapping relationship between the first provider service instance and the provider port, and the second mapping is a mapping relationship between the first requester service instance and the request port.

10. A configuration device, characterized in that: It includes an acquisition unit and a processing unit, wherein: The acquiring unit is configured to acquire a domain-specific language (DSL) file, wherein the DSL file includes a communication relationship between a first node and a second node, wherein the communication relationship indicates that the first node communicates with the second node based on a first topic; The processing unit is used to determine, according to the DSL file, an ARXML file related to the communication management CM in the automotive open system architecture AUTOSAR.

11. The device according to claim 10, wherein The data type of the first topic is a first data type, the service interface type corresponding to the first data type is a first service interface type, and the processing unit is configured to: Determine a first service interface deployment item based on the first topic; Establish an association relationship between the first service interface deployment item and the first service interface type.

12. The device according to claim 11, wherein The DSL file further includes information about the communication protocol corresponding to the first topic, and the processing unit is configured to: Determine the first service interface deployment item based on information about the first topic and the communication protocol.

13. The device according to claim 11 or 12, characterized in that The DSL file further includes information on one or more data types, where the one or more data types include the first data type. The processing unit is further configured to: Before determining the first service interface deployment item, a service interface type corresponding to each data type in the one or more data types is determined.

14. The device according to claim 13, wherein The first node is a publishing node, the second node is a subscribing node, and the processing unit is further configured to: Determine a first provider service instance corresponding to the first node and a first requester service instance corresponding to the second node; Establish an association relationship among the first provider service instance, the first requester service instance and the first service interface deployment item.

15. The device according to claim 14, wherein The communication protocol corresponding to the first topic is DDS, the DSL file further includes first information indicating a type of the transmission plug-in, and the processing unit is further configured to: A transmission plug-in is determined according to the first information.

16. The device according to claim 14 or 15, characterized in that The communication relationship further indicates that the first node communicates with the third node based on the first topic, and the processing unit is further configured to: Determine a second requester service instance corresponding to the third node; and establish an association relationship among the first provider service instance, the second requester service instance, and the first service interface deployment item; or, Determine a second provider service instance corresponding to the first node and a second requester service instance corresponding to the third node; and establish an association relationship among the second provider service instance, the second requester service instance and the first service interface deployment item.

17. The device according to any one of claims 14 to 16, characterized in that The processing unit is further configured to: Determining a first process, a first process design, a first executable program, and a first software component associated with the first provider service instance, and establishing associations between the first process and the first process design, the first process design and the first executable program, the first process and the first executable program, and the first executable program and the first software component; Determine a second process, a second process design, a second executable program, and a second software component related to the first requester service instance, and establish association relationships between the second process and the second process design, the second process design and the second executable program, the second process and the second executable program, and the second executable program and the second software component.

18. The device according to claim 17, wherein The processing unit is further configured to: Determining a provided port corresponding to the first software component and determining a requested port corresponding to the second software component; Establishing an association relationship between the providing port, the requesting port and the first service interface type; A first mapping and a second mapping are determined, wherein the first mapping is a mapping relationship between the first provider service instance and the provider port, and the second mapping is a mapping relationship between the first requester service instance and the request port.

19. A configuration device, characterized in that: include: memory for storing computer programs; A processor, configured to execute the computer program stored in the memory, so that the apparatus performs the configuration method according to any one of claims 1 to 9.

20. An electronic device, characterized in that: Comprising the configuration device according to any one of claims 10 to 19.

21. A computer-readable storage medium, characterized in that Instructions are stored thereon, and when the instructions are executed by a processor, the processor implements the configuration method according to any one of claims 1 to 9.

22. A chip, characterized in that: The chip includes a circuit configured to execute the configuration method according to any one of claims 1 to 9.

23. A computer program product, characterized in that The computer program product comprises: a computer program code, which enables the computer to execute the configuration method according to any one of claims 1 to 9 when the computer program code is run on the computer.

Images