Method and device for checking communication nodes in communication model

Abstract

The invention provides a verification method and device for communication nodes in a communication model, the communication nodes comprise a service providing node and a service consuming node, and the method comprises the steps that the verification device obtains first configuration information from a configuration file of the communication model, the first configuration information comprises information configured for realizing communication between the service providing node and the service consumption node; the verification device outputs prompt information according to the first configuration information and a preset configuration requirement, and the prompt information indicates whether normal communication can be carried out between the service providing node and the service consumption node; the preset configuration requirement comprises a configuration requirement specified for realizing a communication function between the service providing node and the service consumption node in a system architecture standard applied by the communication model; the system architecture standard is an automobile open system architecture AUTOSAR, and the configuration file of the communication model is an ARXML file. According to the method, whether the service providing node and the service consumption node in the communication model communicate normally or not can be verified.

Description

Verification method and device for communication nodes in communication model Technical Field

[0001] The present application relates to the field of automotive technology, and in particular to a verification method and device for communication nodes in a communication model. Background Art

[0002] When developing applications based on the AUTOSAR (Automotive Open System Architecture) standard, each manufacturer may design a communication model based on the AUTOSAR standard to achieve a specific function. This design may include the communication between service provider nodes and service consumer nodes. Service provider nodes are communication nodes that provide services, while service consumer nodes are communication nodes that use services.

[0003] However, after designing a communication model including a service providing node and a service consuming node, it is found that the service providing node and the service consuming node may still not be able to communicate normally when using the communication model.

[0004] Therefore, after the communication model design is completed, how to verify whether the service providing node and the service consuming node can communicate normally, and obtain a communication model in which the service providing node and the service consuming node can communicate normally based on the verification results, becomes a technical problem that needs to be solved urgently.

[0005] Summary of the Invention

[0006] The present application provides a verification method and device for communication nodes in a communication model, which can verify whether the communication between the service providing node and the service consuming node is normal.

[0007] In a first aspect, the present application provides a method for verifying communication nodes in a communication model, wherein the communication nodes include a service providing node and a service consuming node, and the method includes: a verification device obtains first configuration information from a configuration file of the communication model, the first configuration information including information configured to realize communication between the service providing node and the service consuming node; the verification device outputs prompt information based on the first configuration information and preset configuration requirements, the prompt information indicating whether the service providing node and the service consuming node can communicate normally, and the preset configuration requirements include the configuration requirements specified in the system architecture standard applied by the communication model for realizing the communication function between the service providing node and the service consuming node.

[0008] Among them, the system architecture standard is the automotive open system architecture AUTOSAR, and the configuration file of the communication model is the ARXML file.

[0009] Among them, the service providing node refers to the communication node that provides services, and the service consuming node refers to the communication node that consumes services.

[0010] When verifying whether the service providing node and the service consuming node in the communication model can communicate normally, the verification device will obtain the information configured to realize the communication function between the service providing node and the service consuming node (i.e., the first configuration information) from the ARXML file of the communication model. That is, it can be considered that the verification device will obtain some configuration information associated with the communication between the service providing node and the service consuming node from the ARXML file of the communication model, and then verify whether the service providing node and the service consuming node can communicate normally based on the first configuration information and the configuration requirements specified in the system architecture standard applied by the communication model to realize the communication function between the service providing node and the service consuming node, and output prompt information to prompt the user whether the service providing node and the service consuming node can communicate normally.

[0011] In combination with the first aspect, in a possible implementation, the method also includes: the verification device receives first information, the first information indicates at least one communication instance pair, each communication instance pair includes a service consumption node and a service provision node that need to communicate; wherein, the verification device outputs prompt information according to the first configuration information and preset configuration requirements, including: the verification device outputs prompt information according to the first configuration information and preset configuration requirements corresponding to the service provision node and the service consumption node in each communication instance pair.

[0012] In this implementation, the verification device can obtain the service providing node and service consuming node that the user needs to verify through the first information indicating at least one communication instance pair input by the user on the interactive interface.

[0013] In combination with the first aspect, in one possible implementation, the first configuration information includes configuration information of a service interface (ServiceInterface) element; when the configuration information of the service interface element does not comply with the configuration requirements preset for the configuration information of the service interface element in the AUTOSAR standard, the prompt information is specifically used to prompt at least one of the following information: the port and service interface deployment should reference the same service interface, and the service interface element must be configured with at least one of the three communication modes of events, methods, and fields.

[0014] It is understood that in this implementation, when the verification device outputs this type of prompt information, the user can determine, based on this prompt information, that normal communication between the service providing node and the service consuming node may be impossible, and that the cause of this impossible communication may be related to the configuration information of the service interface element. Furthermore, based on this prompt information, the user can check the configuration information related to the service interface element in the service providing node and the service consuming node, thereby obtaining a correct communication model.

[0015] In combination with the first aspect, in a possible implementation, the first configuration information includes configuration information of a process design (ProcessDesign) element; when the configuration information of the process design element does not meet the configuration requirements preset for the configuration information of the process design element in the AUTOSAR standard, the prompt information is specifically used to prompt: the process does not point to a process design.

[0016] It is understood that in this implementation, when the verification device outputs this type of prompt information, the user can determine, based on this prompt information, that normal communication between the service providing node and the service consuming node may be impossible, and that the cause of this impossible communication may be related to the configuration information of the process design element. Furthermore, based on this prompt information, the user can check the configuration information related to the process design element in the service providing node and the service consuming node, thereby obtaining a correct communication model.

[0017] In combination with the first aspect, in one possible implementation, the first configuration information includes configuration information of an executable file (Executable) element; when the configuration information of the executable file element does not meet the configuration requirements preset for the configuration information of the executable file element in the AUTOSAR standard, the prompt information is specifically used to prompt at least one of the following information: the process and the process design do not point to the same executable file, and the executable file does not have an aggregate element root software component prototype.

[0018] It is understood that in this implementation, when the verification device outputs this type of prompt information, the user can determine, based on this prompt information, that normal communication between the service providing node and the service consuming node may be impossible, and that the cause of this impossible communication may be related to the configuration information of the executable file element. Furthermore, based on this prompt information, the user can check the configuration information related to the executable file element in the service providing node and the service consuming node, thereby obtaining a correct communication model.

[0019] In combination with the first aspect, in a possible implementation method, the first configuration information includes configuration information of a service instance to port prototype mapping (ServiceInstanceToPortPrototypeMapping) element; when the configuration information of the service instance to port prototype mapping element does not meet the configuration requirements preset for the configuration information of the service instance to port prototype mapping element in the AUTOSAR standard, the prompt information is specifically used to prompt at least one of the following information: the instance is not associated with the service instance to port prototype mapping, the instance is associated with one or more redundant service instance to port prototype mappings, the redundant mapping is deleted, and the service instance to port prototype mapping has no aggregate element port prototype and the instance reference is not executable.

[0020] It is understood that in this implementation, when the verification device outputs this type of prompt information, the user can determine, based on this prompt information, that normal communication between the service providing node and the service consuming node may be impossible, and that the cause of this impossible communication may be related to the configuration information of the service instance to port prototype mapping element. Furthermore, based on this prompt information, the user can check the configuration information related to the service instance to port prototype mapping element in the service providing node and the service consuming node, thereby obtaining a correct communication model.

[0021] In combination with the first aspect, in a possible implementation, the first configuration information includes configuration information of a software component type (SwComponentType) element; when the configuration information of the software component type element does not comply with the configuration requirements preset for the configuration information of the software component type element in the AUTOSAR standard, the prompt information is specifically used to prompt at least one of the following information: the executable file is not associated with the software component type, the service instance to port prototype mapping should correctly configure the root software component prototype to associate with the SWC, the service instance to port prototype mapping should be associated with the port of the SWC, and the type of the port associated with the service instance to port prototype mapping is incorrect.

[0022] It is understood that in this implementation, when the verification device outputs this type of prompt information, the user can determine, based on this prompt information, that normal communication between the service providing node and the service consuming node may be impossible, and that the cause of this impossible communication may be related to the configuration information of the software component type element. Furthermore, based on this prompt information, the user can check the configuration information related to the software component type element in the service providing node and the service consuming node, thereby obtaining a correct communication model.

[0023] In combination with the first aspect, in a possible implementation method, the first configuration information includes configuration information of a service instance (ServiceInstance) element; when the configuration information of the service instance element does not comply with the configuration requirements preset for the configuration information of the service instance element in the AUTOSAR standard, the prompt information is specifically used to prompt at least one of the following information: the service provider instance and the service consumer instance are of different types and should be set to the extensible service-oriented middleware SOME / IP type based on the Internet interconnection protocol IP or the data distribution service protocol DDS type, the instance identifiers of the service provider instance and the service consumer instance are inconsistent, the domain identifiers of the service provider instance and the service consumer instance are inconsistent, and the configurations of the QoS files of the service provider instance and the service consumer instance are inconsistent.

[0024] It is understood that in this implementation, when the verification device outputs this type of prompt information, the user can determine, based on this prompt information, that normal communication between the service providing node and the service consuming node may be impossible, and that the cause of this impossible communication may be related to the configuration information of the service instance element. Furthermore, based on this prompt information, the user can check the configuration information related to the service instance element in the service providing node and the service consuming node, thereby obtaining a correct communication model.

[0025] In combination with the first aspect, in a possible implementation method, the first configuration information includes configuration information of a service interface deployment (ServiceInterfaceDeployment) element; when the configuration information of the service interface deployment element does not meet the configuration requirements preset for the configuration information of the service interface deployment element in the AUTOSAR standard, the prompt information is specifically used to prompt at least one of the following information: the service provider instance and the service consumer instance associated with the service interface deployment do not reference the same service interface deployment.

[0026] It is understood that in this implementation, when the verification device outputs this type of prompt information, the user can determine, based on this prompt information, that normal communication between the service providing node and the service consuming node may be impossible, and that the cause of this abnormal communication may be related to the configuration information of the service interface deployment element. Furthermore, based on this prompt information, the user can check the configuration information related to the service interface deployment element in the service providing node and the service consuming node, thereby obtaining a correct communication model.

[0027] In combination with the first aspect, in a possible implementation, the first configuration information includes configuration information of a service instance to machine mapping (ServiceInstanceToMachineMapping) element; when the configuration information of the service instance to machine mapping element does not meet the configuration requirements preset for the configuration information of the service instance to machine mapping element in the AUTOSAR standard, the prompt information is specifically used to prompt at least one of the following information: the instance is not associated with the service instance to machine mapping, the connector of the service instance to machine mapping cannot be mapped to the instance, the service instance to machine mapping is deleted, or the instance is deleted from the service instance to machine mapping.

[0028] It is understood that in this implementation, when the verification device outputs this type of prompt information, the user can determine, based on this prompt information, that normal communication between the service providing node and the service consuming node may be impossible, and that the cause of this abnormal communication may be related to the configuration information of the service instance-to-machine mapping element. Furthermore, based on this prompt information, the user can check the configuration information related to the service instance-to-machine mapping element in the service providing node and the service consuming node, thereby obtaining a correct communication model.

[0029] In combination with the first aspect, in a possible implementation, the first configuration information includes configuration information of a process-to-machine mapping set (ProcessToMachineMappingSet) element; when the configuration information of the process-to-machine mapping set element does not meet the configuration requirements preset for the configuration information of the process-to-machine mapping set element in the AUTOSAR standard, the prompt information is specifically used to prompt at least one of the following information: the process is not associated with a process-to-machine mapping set, the process is associated with multiple process-to-machine mapping sets, and unnecessary process-to-machine mappings are deleted.

[0030] It is understood that in this implementation, when the verification device outputs this type of prompt information, the user can determine, based on this prompt information, that normal communication between the service providing node and the service consuming node may be impossible, and that the cause of this impossible communication may be related to the configuration information of the process-to-machine mapping set element. Furthermore, based on this prompt information, the user can check the configuration information related to the process-to-machine mapping set element in the service providing node and the service consuming node, thereby obtaining a correct communication model.

[0031] In combination with the first aspect, in a possible implementation, the first configuration information includes configuration information of a machine design (MachineDesign) element; when the configuration information of the machine design element does not meet the configuration requirements preset for the configuration information of the machine design element in the AUTOSAR standard, the prompt information is specifically used to prompt at least one of the following information: the machine is not associated with the machine design, there is no communication connector aggregation element, and the machine design cannot configure instance-to-machine mapping.

[0032] It is understood that in this implementation, when the verification device outputs this type of prompt information, the user can determine, based on this prompt information, that normal communication between the service providing node and the service consuming node may be impossible, and that the cause of this impossible communication may be related to the configuration information of the machine design element. Furthermore, based on this prompt information, the user can check the configuration information related to the machine design element in the service providing node and the service consuming node, thereby obtaining a correct communication model.

[0033] In combination with the first aspect, in one possible implementation, the first configuration information includes configuration information of a machine element; when the configuration information of the machine element does not meet the configuration requirements preset for the configuration information of the machine element in the AUTOSAR standard, the prompt information is specifically used to prompt at least one of the following information: the process to machine mapping is not associated with the machine, and the SHM of DDS cannot communicate with multiple machines.

[0034] It is understood that in this implementation, when the verification device outputs this type of prompt information, the user can determine, based on this prompt information, that normal communication between the service providing node and the service consuming node may be impossible, and that the cause of this abnormal communication may be related to the configuration information of the machine element. Furthermore, based on this prompt information, the user can check the configuration information related to the machine element in the service providing node and the service consuming node, thereby obtaining a correct communication model.

[0035] In the second aspect, the present application provides a verification device for communication nodes in a communication model, wherein the communication nodes include service providing nodes and service consuming nodes, and the device includes: an acquisition module for obtaining first configuration information from a configuration file of the communication model, the first configuration information including information configured to realize communication between the service providing node and the service consuming node; a processing module for outputting prompt information based on the first configuration information and preset configuration requirements, the prompt information indicating whether normal communication can be achieved between the service providing node and the service consuming node, the preset configuration requirements including the configuration requirements specified in the system architecture standard applied by the communication model for realizing the communication function between the service providing node and the service consuming node; the system architecture standard is the automotive open system architecture AUTOSAR, and the configuration file of the communication model is an ARXML file.

[0036] In combination with the second aspect, in a possible implementation method, the acquisition module is also used to receive first information, the first information indicates at least one communication instance pair, each communication instance pair includes a service consumption node and a service provision node that need to communicate; wherein, the processing module is specifically used to: output prompt information according to the first configuration information corresponding to the service provision node and the service consumption node in each communication instance pair and the preset configuration requirements.

[0037] In combination with the second aspect, in one possible implementation, the first configuration information includes configuration information of the service interface element; when the configuration information of the service interface element does not meet the configuration requirements preset for the configuration information of the service interface element in the AUTOSAR standard, the prompt information is specifically used to prompt at least one of the following information: the port and service interface deployment should reference the same service interface, and the service interface element must be configured with at least one of the three communication modes of events, methods, and fields.

[0038] In combination with the second aspect, in one possible implementation, the first configuration information includes configuration information of a process design element; when the configuration information of the process design element does not comply with the configuration requirements preset for the configuration information of the process design element in the AUTOSAR standard, the prompt information is specifically used to prompt: the process does not point to a process design.

[0039] In combination with the second aspect, in one possible implementation, the first configuration information includes configuration information of an executable file element; when the configuration information of the executable file element does not meet the configuration requirements preset for the configuration information of the executable file element in the AUTOSAR standard, the prompt information is specifically used to prompt at least one of the following information: the process and the process design do not point to the same executable file, and the executable file does not have an aggregate element root software component prototype.

[0040] In combination with the second aspect, in a possible implementation, the first configuration information includes configuration information of a service instance to port prototype mapping element; when the configuration information of the service instance to port prototype mapping element does not meet the configuration requirements preset for the configuration information of the service instance to port prototype mapping element in the AUTOSAR standard, the prompt information is specifically used to prompt at least one of the following information: the instance is not associated with the service instance to port prototype mapping, the instance is associated with one or more redundant service instance to port prototype mappings, the redundant mapping is deleted, and the service instance to port prototype mapping has no aggregate element port prototype and the instance reference is not executable.

[0041] In combination with the second aspect, in a possible implementation, the first configuration information includes configuration information of a software component type element; when the configuration information of the software component type element does not comply with the configuration requirements preset for the configuration information of the software component type element in the AUTOSAR standard, the prompt information is specifically used to prompt at least one of the following information: the executable file is not associated with the software component type, the service instance to port prototype mapping should correctly configure the root software component prototype to associate with the SWC, the service instance to port prototype mapping should be associated with the port of the SWC, and the type of the port associated with the service instance to port prototype mapping is incorrect.

[0042] In combination with the second aspect, in a possible implementation method, the first configuration information includes configuration information of the service instance element; when the configuration information of the service instance element does not comply with the configuration requirements preset for the configuration information of the service instance element in the AUTOSAR standard, the prompt information is specifically used to prompt at least one of the following information: the service provider instance and the service consumer instance are of different types and should be set to the extensible service-oriented middleware SOME / IP type based on the Internet interconnection protocol IP or the data distribution service protocol DDS type, the instance identifiers of the service provider instance and the service consumer instance are inconsistent, the domain identifiers of the service provider instance and the service consumer instance are inconsistent, and the configurations of the QoS files of the service provider instance and the service consumer instance are inconsistent.

[0043] In combination with the second aspect, in one possible implementation, the first configuration information includes configuration information of the service interface deployment element; when the configuration information of the service interface deployment element does not meet the configuration requirements preset for the configuration information of the service interface deployment element in the AUTOSAR standard, the prompt information is specifically used to prompt at least one of the following information: the service provider instance and service consumer instance associated with the service interface deployment do not reference the same service interface deployment.

[0044] In combination with the second aspect, in one possible implementation, the first configuration information includes configuration information of a service instance to machine mapping element; when the configuration information of the service instance to machine mapping element does not comply with the configuration requirements preset in the AUTOSAR standard for the configuration information of the service instance to machine mapping element, the prompt information is specifically used to prompt at least one of the following information: the instance is not associated with the service instance to machine mapping, the connector of the service instance to machine mapping cannot be mapped to the instance, the service instance to machine mapping is deleted, or the instance is deleted from the service instance to machine mapping.

[0045] In combination with the second aspect, in one possible implementation, the first configuration information includes configuration information of a process-to-machine mapping set element; when the configuration information of the process-to-machine mapping set element does not meet the configuration requirements preset for the configuration information of the process-to-machine mapping set element in the AUTOSAR standard, the prompt information is specifically used to prompt at least one of the following information: the machine is not associated with the machine design, there is no communication connector aggregation element, and the machine design cannot configure instance-to-machine mapping.

[0046] In combination with the second aspect, in one possible implementation, the first configuration information includes configuration information of a machine design element; when the configuration information of the machine design element does not comply with the configuration requirements preset for the configuration information of the machine design element in the AUTOSAR standard, the prompt information is specifically used to prompt at least one of the following information: there is no communication connector aggregation element, and the machine design cannot configure instance-to-machine mapping.

[0047] In combination with the second aspect, in one possible implementation, the first configuration information includes configuration information of a machine element; when the configuration information of the machine element does not meet the configuration requirements preset for the configuration information of the machine element in the AUTOSAR standard, the prompt information is specifically used to prompt at least one of the following information: the process-to-machine mapping is not associated with the machine, and the SHM of the DDS cannot communicate with multiple machines.

[0048] In a third aspect, the present application provides a verification device for a communication node in a communication model, comprising: a memory and a processor; the memory is used to store program instructions; the processor is used to call the program instructions in the memory to execute the method described in the first aspect or any possible implementation method thereof.

[0049] In a fourth aspect, the present application provides a computer-readable medium storing a program code for computer execution, wherein the program code includes instructions for executing the method as described in the first aspect or any possible implementation thereof.

[0050] In a fifth aspect, the present application provides a chip comprising at least one processor and a communication interface, wherein the communication interface and the at least one processor are interconnected through lines, and the at least one processor is used to run a computer program or instruction to perform the method described in the first aspect or any possible implementation thereof.

[0051] In a sixth aspect, the present application provides a computer program product, which includes computer program instructions. When the computer program instructions are run on a computer, the computer implements the method described in the first aspect or any possible implementation thereof.

[0052] Among them, the technical effects brought about by any implementation method of the second to sixth aspects can refer to the technical effects brought about by any possible implementation method of the first aspect mentioned above, and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS

[0053] FIG1 is a flow chart of the application development process provided by this application;

[0054] FIG2 is a schematic diagram of the structure of an application model of a design provided by an embodiment of the present application;

[0055] FIG3 is a flow diagram of a method for verifying a communication node in a communication model provided by one embodiment of the present application;

[0056] FIG4 is a schematic diagram of configuration information related to a communication function between a service providing node and a service consuming node provided in one embodiment of the present application;

[0057] FIG5 is a schematic structural diagram of a verification device for a communication node in a communication model provided by one embodiment of the present application;

[0058] FIG6 is a structural diagram of a verification device for a communication node in a communication model provided in another embodiment of the present application. DETAILED DESCRIPTION

[0059] In the automotive field, to improve the updating and exchange of automotive electronic system software and to more conveniently and effectively manage increasingly complex automotive electronic software systems, since 2003, major global automobile manufacturers, automotive parts suppliers, and automotive electronic software system companies have jointly established a set of open software architecture standardization solutions that are compatible with automotive electronic software development. The Automotive Open System Architecture (AUTOSAR) is a summary of more than 100 years of experience in automotive technology development. It aims to create and establish an open and standardized software architecture for automotive electronic control units, including scalability across different vehicle and platform variants, software portability, consideration of availability and safety requirements, collaboration between different partners, sustainable use of natural resources, and maintainability throughout the product life cycle.

[0060] Usually, in the application development process based on the AUTOSAR standard, when a vehicle is required to be able to implement a certain function, an application model that can complete a certain specific function will be designed first, and then after the application model design is completed, a system description file (ARXML file) in AUTOSAR XML format is generated to describe the application model. For example, when a vehicle is required to be able to implement some headlight control functions, an application model that can complete the headlight control function will be designed, and after the application model design is completed, an ARXML file of the application model will be generated. ARXML files and application models are essentially used to express the same information, but in different forms of expression. Taking the above-mentioned application model of the headlight control function and the ARXML file corresponding to the application model of the headlight control function as an example, when the ARXML file corresponding to the application model of the headlight control function is distributed to a supplier, the supplier can obtain the application model of the headlight control function based on the ARXML file.

[0061] After designing an application model that can perform a specific function, the designed application model is usually verified to ensure that the designed application model is correct and provide a good foundation for subsequent development. Specifically, after designing an application model that can perform a specific function, the ARXML file corresponding to the application model is verified to determine whether the designed application model is correct.

[0062] For example, Figure 1 is a flowchart of the application development process provided by this application. As shown in Figure 1, after the application model design is completed, the ARXML file corresponding to the application model will be obtained. The ARXML file is then verified to ensure that problems can be discovered and corrected during the application model design phase. After verification is completed, the correct application model can be used for code generation. After the code is generated, the business logic code is embedded to complete the algorithm development. Finally, the developed code can be put on the board for debugging and run in the business environment.

[0063] Currently, when verifying an application model, the main focus is on verifying the syntax correctness, configuration integrity, and semantic correctness of the ARXML file corresponding to the application model. Syntactic correctness refers to checking whether the ARXML file meets the syntax requirements of the ARXML rules; configuration integrity refers to checking whether mandatory elements required by the AUTOSAR standard are missing; and semantic correctness refers to whether certain configuration specifications are met.

[0064] However, it should be understood that the design process of an application model typically includes designing the communication between service-providing nodes and service-consuming nodes. Service-providing nodes are communication nodes that provide services, while service-consuming nodes are communication nodes that consume services. Once the application model design is complete, ensuring that all communication nodes in the application model can communicate properly is a top priority for users.

[0065] However, after the ARXML file is verified for syntax correctness, configuration integrity, and semantic correctness, the application model corresponding to the ARXML file may still have problems with the service providing node and the service consuming node not being able to communicate normally.

[0066] For example, Figure 2 is a schematic diagram of the structure of an application model designed according to one embodiment of the present application. As shown in Figure 2, the application model includes a service provider node and two service consumer nodes. The service provider node needs to provide services to the two service consumer nodes. Each communication node is associated with a machine, a software component (SWC), an executable file (Executable), a process (Process), an internal communication port (Port), and a connector (Connector).

[0067] Specifically, Machine is the deployment location of the communication node, usually a system-on-a-chip (SoC); SWC is the component type design model of the communication node; Executable is the binary design model of the communication node; Process is the deployment design model of the communication node; Connector is the port for Machine to communicate externally, usually referring to a network card.

[0068] It should be understood that in the application model shown in Figure 2, where a service provider node needs to provide services to two service consumer nodes, the prerequisite for the service provider node to provide services to both service consumer nodes is that the service provider node can communicate normally with the two service consumer nodes. However, existing methods that verify the syntax correctness, configuration integrity, and semantic correctness of ARXML files cannot verify whether the service provider node and the two service consumer nodes are communicating normally.

[0069] Furthermore, it should be understood that if the service provider node and the two service consumer nodes cannot be verified for proper communication during the application model design phase, then once the ARXML file has been verified for syntactical correctness, configuration integrity, and semantic correctness, subsequent code generation, algorithm development, and ultimately deployment on the board for debugging will occur. At this point, if omissions or errors in the application model design lead to the discovery of a failure in communication between the service provider node and the service consumer node only after deployment and debugging on the board, the design will need to be revised, resulting in a significant amount of rework and inefficiency.

[0070] In view of this, the present application provides a verification method and device for communication nodes in an application model (communication model), so that after the communication model design is completed, it is possible to verify whether the service providing node and the service consuming node are communicating normally, so that the developer can correct the original application model according to the verification results to obtain an application model in which the service providing node and the service consuming node can communicate normally, and then proceed with the subsequent development process.

[0071] Figure 3 is a flow chart of a verification method for a communication node in a communication model provided by an embodiment of the present application. As shown in Figure 3, the verification method includes S301 and S302.

[0072] S301: The verification device obtains first configuration information from a configuration file of a communication model. The first configuration information includes information configured to implement communication between a service providing node and a service consuming node.

[0073] In this embodiment, the verification device refers to a device that can verify whether the communication nodes in the communication model can communicate normally. In this application, the verification device can also be called a verification module.

[0074] In this embodiment, the communication model includes a pair of service providing nodes and service consuming nodes that need to communicate, wherein the service providing node refers to a communication node that provides services, and the service consuming node refers to a communication node that uses services.

[0075] In this embodiment, the configuration file of the communication model refers to a file used to describe the communication model. In other words, the corresponding communication model can be obtained through the configuration file of the communication model.

[0076] In this embodiment, the configuration file of the communication model is a file that complies with the ARXML format, typically an ARXML file.

[0077] It should be understood that when designing a communication model, if communication is required between the service providing node and the service consuming node in the communication model, the corresponding ARXML file should include configuration information for implementing the communication.

[0078] For example, for communication between a service providing node and a service consuming node, the following communication-related configurations may be required:

[0079] 1) Interface-related configuration

[0080] Service Interface: This defines the communication methods required by the service and the data types required for each communication method. The communication methods required by the service can include one or more of the following: events, methods, and fields.

[0081] 2) Port-related configuration

[0082] Adaptive Application Software Component Type (AdaptiveApplicationSwComponentType): used to define the receive port and send port.

[0083] Executable file (Executable): used to configure the referenced AdaptiveApplicationSwComponentType.

[0084] Process Design: used to configure the referenced Executable.

[0085] Process: Used to configure referenced Executable and ProcessDesign.

[0086] Service Instance to Port Prototype Mapping: used to establish a mapping between Service Instance and Port.

[0087] 3) Communication instance related configuration

[0088] Service Instance: Used to configure the data distribution service (DDS) protocol, define the domain identifier (DomainId), and set the service instance ID (ServiceInstanceId). If the Scalable Service-Oriented Middleware over IP (SOME / IP) protocol is used, setting the DomainId is not required.

[0089] Service Interface Deployment: used to configure the referenced ServiceInterface and bind protocols such as DDS and SOME / IP.

[0090] Service Instance to Machine Mapping (ServiceInstanceToMachineMapping): used to establish a mapping between ServiceInstance and Machine; that is, to establish a mapping relationship between ServiceInstance and EthernetCommunicationConnector.

[0091] 4) Machine-related configuration

[0092] Process to Machine Mapping Set (ProcessToMachineMappingSet): used to establish the mapping between Process and Machine.

[0093] Ethernet Cluster: used to define network configuration, such as IP, subnet mask, etc.

[0094] Machine Design: used to define the Ethernet Communication Connector and service discovery IP.

[0095] Machine: Configures the referenced MachineDesign.

[0096] It is also understood that if some of the communication configurations included in the corresponding configuration files in the communication model do not meet the rules followed by service provider nodes and service consumer nodes for communication, then communication between the service provider nodes and service consumer nodes may be affected. For example, when a service provider node and a service consumer node communicate, the service instance ID of both communicating parties must be the same and the communication protocols used must match.

[0097] In view of this, in this application, after the verification device determines the service provider node and service consumer node in the communication model that need to be verified whether they can communicate normally, in order to verify whether the service provider node and service consumer node can communicate normally, the first configuration information will first be extracted from the configuration file of the communication model.

[0098] The first configuration information refers to information configured in the ARXML file to implement communication between the service providing node and the service consuming node.

[0099] In other words, the first configuration information may be considered as some configuration information in the ARXML file that is associated with the communication between the service providing node and the service consuming node, rather than any information in the ARXML file.

[0100] Exemplarily, as shown in FIG4 , the first configuration information obtained by the corresponding ARXML file is at least one of the following configuration information:

[0101] Configuration information related to the service interface: specifically includes configuration information related to the service interface associated with the service providing node (P in Figure 4) as shown in Figure 4, and configuration information related to the service interface associated with the service consuming node (R in Figure 4).

[0102] Port-related configuration information: This specifically includes configuration information related to ports associated with service-providing nodes and configuration information related to ports associated with service-consuming nodes, as shown in Figure 4. More specifically, this port-related configuration information includes process design configuration information, executable file configuration information, SWC configuration information, and service instance-to-port type mapping configuration information (i.e., the mapping in Figure 4).

[0103] Configuration related to the communication instance: specifically includes configuration information related to the service providing node and configuration information related to the service consuming node as shown in FIG4 .

[0104] Machine-related configuration information: specifically includes the Machine-related configuration information associated with the service providing node, as shown in FIG4 , and the Machine-related configuration information associated with the service consuming node.

[0105] It is understandable that since the first configuration information is information in the configuration file of the communication model that is associated with the communication function between the service providing node and the service consuming node, when the configuration of the first configuration information does not comply with the rules that should be followed, the communication between the service providing node and the service consuming node will be affected. Therefore, in this application, the first configuration information is also referred to as configuration information that affects the communication between the service providing node and the service consuming node.

[0106] S302. The verification device outputs prompt information based on the first configuration information and the preset configuration requirements. The prompt information indicates whether the service providing node and the service consuming node can communicate normally. The preset configuration requirements include the configuration requirements specified in the system architecture standard applied by the communication model for realizing the communication function between the service providing node and the service consuming node; the system architecture standard is the automotive open system architecture AUTOSAR, and the configuration file of the communication model is an ARXML file.

[0107] The system architecture standard used by the communication model can be considered as a set of standards that need to be followed when designing the communication model. Specifically, in this embodiment, the system architecture standard used by the communication model is the Automotive Open System Architecture (AUTOSAR).

[0108] It's understandable that for a service provider node and a service consumer node to communicate properly, certain configuration requirements must be met. For example, for a service provider node and a service consumer node to communicate properly, both nodes must have the same service instance ID and use matching communication protocols.

[0109] It is also understood that, for a certain communication model, if some of the configuration information used to implement communication included in the configuration file of the communication model does not meet the rules followed by communication between the service providing node and the service consuming node, then the communication between the service providing node and the service consuming node may be affected. Therefore, in this embodiment, after obtaining the first configuration information, prompt information will be output based on the configuration requirements specified in the AUTOSAR standard for implementing the communication function between the service providing node and the service consuming node, which the first configuration information and the communication model comply with, to verify whether normal communication can be achieved between the service providing node and the service consuming node in the communication model. The prompt information indicates whether normal communication can be achieved between the service consuming node and the service providing node.

[0110] For example, the following aspects may be included:

[0111] 1. Verification of interface-level configuration information

[0112] Generally, when a communication model is designed based on the AUTOSAR standard, as shown in Table 1, the configuration information of the service interface (ServiceInterface) element in the ARXML file corresponding to the communication model may include two situations.

[0113] The first is when a ServiceInterface element is associated with a ServiceInterfaceDeployment element and a ServiceInstanceToPortPrototypeMapping element. In this case, the configuration requirements include: the port of the service provider node (i.e., the port of the service provider), the port of the service consumer node (i.e., the port of the service provider), and the ServiceInterfaceDeployment should reference the same ServiceInterface.

[0114] The second is when the ServiceInterface element is not associated with any other element. In this case, the configuration requirements include: configuring at least one data type in the configuration information of the ServiceInterface element.

[0115] It should be understood that when the first configuration information in this application includes configuration information of the service interface element, if the first configuration information does not meet any of the configuration requirements of the above-mentioned ServiceInterface, it may cause the service providing node and the service consuming node to fail to communicate normally.

[0116] Therefore, as shown in Table 1, in this embodiment, when the ServiceInterface element is associated with the service interface deployment and the service instance to port prototype mapping element, if the configuration requirements that the port of the service providing node (i.e., the port of P), the port of the service consuming node (i.e., the port of R), and the ServiceInterfaceDeployment should reference the same ServiceInterface are not met, the following prompt information is output: a Port and the corresponding ServiceInterfaceDeployment shall reference the same ServiceInterface.

[0117] When the ServiceInterface element is not associated with other elements, if at least one data type is not configured in the configuration information of the ServiceInterface element, the following prompt message is output: The ServiceInterface must be configured with at least one communication mode: Event, Method or Field.

[0118] Table 1

[0119]

[0120] That is, in this embodiment, when the configuration information of the service interface element does not meet the configuration requirements preset for the configuration information of the service interface element, the prompt information may include at least one of the following prompt information: the port and service interface deployment should reference the same service interface, and the service interface element must be configured with at least one of the three communication modes of events, methods, and fields.

[0121] It is understandable that when a user receives this type of prompt, they can determine that the communication failure between the service provider node and the service consumer node may be caused by the configuration information of the service interface element. Furthermore, by checking the configuration information related to the service interface element in the service provider node and the service consumer node, they can correct the communication model and obtain the correct communication model.

[0122] 2. Port-level verification

[0123] Typically, when designing a communication model based on the AUTOSAR standard, the port-level elements that affect communication in the ARXML file of the communication model may include, for example, configuration information of the process design (ProcessDesign) element, configuration information of the executable file (Executable) element, configuration information of the service instance to port prototype mapping (ServiceInstanceToPortPrototypeMapping) element, and configuration information of the software component type (SwComponentType) element.

[0124] 1) For the configuration information of the ProcessDesign element, as shown in Table 2, the configuration requirements include: when the process design element is associated with the process (Process) element, the process should point to a process design.

[0125] It is understandable that when the first configuration information in this application includes configuration information of process design elements, if the configuration information of the process design does not meet the configuration requirements of the process design, it may also cause the service providing node and the service consuming node to be unable to communicate normally.

[0126] Therefore, as shown in Table 2, in this embodiment, if the configuration information of the process design does not meet the configuration requirements of the process design, the following prompt information is output: The process does not point to a process design (The Process is not associated with a ProcessDesign).

[0127] Table 2

[0128]

[0129] It's understandable that after receiving this type of prompt, users can determine that the communication failure between the service provider node and the service consumer node may be due to the process not pointing to the same process design. Furthermore, by checking whether the process points to the same process design, the communication model can be corrected to obtain the correct communication model.

[0130] 2) For the configuration information of the Executable element, as shown in Table 3, the configuration requirements include: when the Executable element is associated with the Process element and the ProcessDesign element, the Process and ProcessDesign should point to the same Executable; when the Executable element is not associated with other elements, the Executable should contain the root software component prototype (RootSwComponentPrototype).

[0131] It is understood that when the first configuration information in this application includes the configuration information of the Executable element, if the configuration information of the Executable element does not meet the configuration requirements of the configuration information of the Executable element, it may also cause the service providing node and the service consuming node to be unable to communicate normally. Therefore, as shown in Table 3, in this embodiment, when the Executable element is associated with the Process and ProcessDesign elements, if the requirement that the Process and ProcessDesign should point to the same Executable is not met, the following prompt message is output: The process and the corresponding ProcessDesign are not associated with the same Executable.

[0132] When the Executable element is not associated with other elements, if the Executable does not contain the root software component prototype, the following prompt message is output: The executable file does not have the RootSwComponentPrototype aggregation element.

[0133] Table 3

[0134]

[0135] That is, when the configuration information of the executable file does not meet the configuration requirements preset for the configuration information of the executable file element in the AUTOSAR standard, the prompt information may also include at least one of the following information: the process and the process design do not point to the same executable file, and the executable file does not have an aggregate element root software component prototype.

[0136] It's understandable that when a user receives this type of prompt, they can determine that the communication failure between the service provider and consumer nodes may be caused by the configuration information of the Executable element. Furthermore, by checking the configuration information related to the Executable element in the service provider and consumer nodes, they can correct the communication model and obtain the correct communication model.

[0137] 3) For the configuration information of the service instance to port prototype mapping element, as shown in Table 4, the configuration requirements include: when the service instance to port prototype mapping element is associated with the service instance (ServcieInstance) element and the process design (ProcessDesign) element, the service instance to port prototype mapping should point to ProcessDesign and ServcieInstance, which exists and is unique; when the service instance to port prototype mapping is not associated with other elements, the aggregate element PortPrototypeInExecutableInstanceRef of the service instance to port prototype mapping should exist.

[0138] It can be understood that when the first configuration information in this application includes the configuration information of the service instance to port prototype mapping element, if the configuration information of the ServiceInstanceToPortPrototypeMapping element does not meet the configuration requirements of the configuration information of the ServiceInstanceToPortPrototypeMapping element, it may also cause the service providing node and the service consuming node to fail to communicate normally.

[0139] Therefore, as shown in Table 4, in this embodiment, when the ServiceInstanceToPortPrototypeMapping element is associated with the service instance (ServcieInstance) element and the process design (ProcessDesign) element, if the service instance to port prototype mapping should point to ProcessDesign and the ServcieInstance exists and is unique, the following prompt information is output: The instance is not associated with a service instance to port prototype mapping, the instance is associated with one or more redundant service instance to port prototype mappings, and the redundant mapping is deleted (The instance is not associated with a ServiceInstanceToPortPrototypeMapping, The instance is associated with one or more redundant ServiceInstanceToPortPrototypeMappings, Delete the redundant Mappings).

[0140] When the ServiceInstanceToPortPrototypeMapping element is not associated with other elements, if the aggregation element PortPrototypeInExecutableInstanceRef of the service instance to port prototype mapping does not exist, the following prompt message is output: The ServiceInstanceToPortPrototypeMapping does not have the PortPrototypeInExecutableInstanceRef aggregation element.

[0141] Table 4

[0142]

[0143] That is, when the configuration information of the service instance to port prototype mapping element does not meet the configuration requirements preset for the service instance to port prototype mapping element in the AUTOSAR standard, the prompt information may also include at least one of the following information: the instance is not associated with the service instance to port prototype mapping, the instance is associated with one or more redundant service instance to port prototype mappings, the redundant mapping is deleted, and the service instance to port prototype mapping has no aggregate element port prototype and cannot execute instance reference.

[0144] It's understandable that when users receive this type of prompt, they can determine that the communication failure between the service provider and consumer nodes may be caused by the configuration information of the ServiceInstanceToPortPrototypeMapping element. Furthermore, by checking the configuration information related to the ServiceInstanceToPortPrototypeMapping element in the service provider and consumer nodes, they can correct the communication model and obtain the correct communication model.

[0145] 4) For the configuration information of the SwComponentType element, as shown in Table 5, the configuration requirements include: when the software component type element is associated with the executable file (Executable) element, the aggregate element root software component prototype (RootSwcPrototype) of Executable should point to a SWC (root SWC); when the SwComponentType element is associated with the service instance to port prototype mapping (ServiceInstanceToPortPrototypeMapping) and the SWC pointed to by the root software component prototype, the SWC referenced by the aggregate element port prototype non-executable instance reference (PortPrototypeInExecutableInstanceRef) under ServiceInstanceToPortPrototypeMapping is the specified root SWC; when the SwComponentType element is associated with PortPrototypeInExecutableInstanceRef and other SWCs, the port pointed to by PortPrototypeInExecutableInstanceRef must be hung on the SWC; when the SwComponentType element is associated with PortPrototypeInExecutableInstanceRef and ServiceInstance, the port type pointed to by PortPrototypeInExecutableInstanceRef and ServiceInstance should be consistent.

[0146] It is understandable that when the first configuration information in this application includes the configuration information of the SwComponentType element, if the configuration information of the SwComponentType element does not meet the configuration requirements of the configuration information of the SwComponentType element, it may also cause the service providing node and the service consuming node to fail to communicate normally.

[0147] Therefore, as shown in Table 5, in this embodiment, when the software component type element is associated with the Executable element, if the root software component prototype (RootSwcPrototype) of the aggregation element of Executable does not point to a SWC (root SWC), the following prompt information is output: The executable file is not associated with the software component type (The Executable is not associated with a SwComponentType).

[0148] When the SwComponentType element is associated with the ServiceInstanceToPortPrototypeMapping and the SWC pointed to by the root software component prototype, if the SWC referenced by the aggregation element PortPrototypeInExecutableInstanceRef under the ServiceInstanceToPortPrototypeMapping is not the specified root SWC, the following prompt message is output: A ServiceInstanceToPortPrototypeMapping shall be configured with a RootSwComponentPrototype correctly to associate with the following SWCS.

[0149] When the SwComponentType element is associated with PortPrototypeInExecutableInstanceRef and other SWCs, if the Port pointed to by PortPrototypeInExecutableInstanceRef must be hung on the SWC, the following prompt message will be output: a ServiceInstanceToPortPrototypeMapping shall be associated with a Port of the following SWCs.

[0150] When the SwComponentType element is associated with PortPrototypeInExecutableInstanceRef and ServiceInstance, if the port type pointed to by PortPrototypeInExecutableInstanceRef and the ServiceInstance type are not consistent, the following prompt message is output: The port type associated with a ServiceInstanceToPortPrototypeMapping is incorrect.

[0151] Table 5

[0152]

[0153] That is, when the configuration information of the SwComponentType element does not meet the configuration requirements preset for the SwComponentType element in the AUTOSAR standard, the prompt information may also include at least one of the following information: the executable file is not associated with the software component type, the service instance to port prototype mapping should correctly configure the root software component prototype to associate with the SWC, the service instance to port prototype mapping should be associated with the port of the SWC, and the type of the port associated with the service instance to port prototype mapping is incorrect.

[0154] It's understandable that when a user receives this type of prompt, they can determine that the communication failure between the service provider and consumer nodes may be caused by the configuration information of the SwComponentType element. Furthermore, by checking the configuration information related to the SwComponentType element in the service provider and consumer nodes, they can correct the communication model and obtain the correct communication model.

[0155] 3. Communication instance level verification

[0156] Typically, when designing a communication model based on the AUTOSAR standard, the port-level elements that affect communication in the ARXML file of the communication model may include, for example, configuration information of the service instance (ServiceInstance) element, configuration information of the service interface deployment (ServiceInterfaceDeployment) element, and configuration information of the service instance to machine mapping (ServiceInstanceToMachineMapping) element.

[0157] 1) For the configuration information of the ServiceInstance element, as shown in Table 6, the configuration requirements include: if the ServiceInstance element is associated with a service provider instance (ProviderServiceInstance) and a service consumer instance (RequiredServiceInstance), the ProviderServiceInstance and the RequiredServiceInstance should both be of the SOME / IP or DDS type; if the ProviderServiceInstance and the RequiredServiceInstance are both of the SOME / IP type, the ProviderServiceInstance and the RequiredServiceInstance (InstanceId) should be the same or the InstanceId of the RequiredServiceInstance should be "any"; if the ProviderServiceInstance and the RequiredServiceInstance are both of the DDS type, the InstanceId of the ProviderServiceInstance and the RequiredServiceInstance should be the same; if the ProviderServiceInstance and the service consumer instance are both of the DDS type, the domain identifier (DomainId) of the ProviderServiceInstance and the RequiredServiceInstance should be the same; if the ProviderServiceInstance and the RequiredServiceInstance are both of the DDS type, the configuration of the quality of service (QoS) files of the ProviderServiceInstance and the RequiredServiceInstance should be the same.

[0158] It can be understood that when the first configuration information in this application includes the configuration information of the ServiceInstance element, if the configuration information of the ServiceInstance element does not meet the configuration requirements of the configuration information of the ServiceInstance element, it may also cause the service providing node and the service consuming node to fail to communicate normally.

[0159] Therefore, as shown in Table 6, in this embodiment, when the ServiceInstance element is associated with the ProviderServiceInstance and the RequiredServiceInstance, if the requirement that the ProviderServiceInstance and the RequiredServiceInstance should both be of the SOME / IP or data distribution service protocol DDS type is not satisfied, the following prompt information is output: The instances of a ProvidedServiceInstance and the corresponding RequiredServiceInstance are of different types, they shall be set to either DDS or SOME / IP.

[0160] When ProviderServiceInstance and RequiredServiceInstance are both of SOME / IP type, if the instance identifiers of ProviderServiceInstance and RequiredServiceInstance are not the same or the instance identifier of the service consumer instance is "any"; or if ProviderServiceInstance and RequiredServiceInstance are both of DDS type, if the InstanceId of ProviderServiceInstance and RequiredServiceInstance are not the same, the following prompt message is output: The instance identifiers of the service provider instance and the service consumer instance are inconsistent (The InstanceId attributes of the ProvidedServiceInstance and the corresponding RequiredServiceInstance are inconsistent).

[0161] When ProviderServiceInstance and RequiredServiceInstance are both DDS types, if the domain identifiers of ProviderServiceInstance and RequiredServiceInstance are not the same, the following prompt message is output: The DomainId attributes of the ProvidedServiceInstance and the corresponding RequiredServiceInstance are inconsistent.

[0162] When ProviderServiceInstance and RequiredServiceInstance are both of DDS type, if the QoS profile configuration does not meet the requirement of being the same, the following prompt message is output: The QoS Profile attributes of the ProvidedServiceInstance and the corresponding RequiredServiceInstance are inconsistent.

[0163] Table 6

[0164]

[0165] That is, when the configuration information of the ServiceInstance element does not meet the configuration requirements preset for the ServiceInstance element in the AUTOSAR standard, the prompt information may also include at least one of the following information: the service provider instance and the service consumer instance are of different types and should be set to the extensible service-oriented middleware SOME / IP type based on the Internet interconnection protocol IP or the data distribution service protocol DDS type, the instance identifiers of the service provider instance and the service consumer instance are inconsistent, the domain identifiers of the service provider instance and the service consumer instance are inconsistent, and the configurations of the QoS files of the service provider instance and the service consumer instance are inconsistent.

[0166] It's understandable that when a user receives this type of prompt, they can determine that the communication failure between the service provider and consumer nodes may be caused by the configuration information of the ServiceInstance element. Furthermore, they can correct the communication model by adjusting the configuration information related to the ServiceInstance element in the service provider and consumer nodes to obtain the correct communication model.

[0167] 2) For the configuration information of the ServiceInterfaceDeployment element, as shown in Table 7, the configuration requirements include: when the ServiceInterfaceDeployment element is associated with the ProviderServiceInstance element and the RequiredServiceInstance element, the service provider instance and the service consumer instance should reference the same service interface deployment.

[0168] It is understandable that when the first configuration information in this application includes the configuration information of the ServiceInterfaceDeployment element, if the configuration information of the ServiceInterfaceDeployment element does not meet the configuration requirements of the process design, it may also cause the service providing node and the service consuming node to fail to communicate normally.

[0169] Therefore, as shown in Table 7, in this embodiment, if the configuration information of ServiceInterfaceDeployment does not meet the configuration requirements of the configuration information of the ServiceInterfaceDeployment element, the following prompt information is output: The service provider instance and service consumer instance associated with the service interface deployment do not reference the same service interface deployment (The instances of a ProvidedServiceInstance and the corresponding RequiredServiceInstance are not associated with the same ServiceInterfaceDeployment).

[0170] Table 7

[0171]

[0172] It's understandable that when users receive this type of prompt, they can determine that the communication failure between the service provider and consumer nodes may be caused by the configuration information of the ServiceInterfaceDeployment element. Furthermore, by checking the configuration information related to the ServiceInterfaceDeployment element in the service provider and consumer nodes, they can correct the communication model and obtain the correct communication model.

[0173] 3) For the configuration information of the ServiceInstanceToMachineMapping element, as shown in Table 8, the configuration requirements include: the connectors of the service instance to machine mapping reference corresponding to the service provider instance and the service consumer instance should exist in the connectors in the machine design.

[0174] It is understandable that when the first configuration information in this application includes the configuration information of the ServiceInterfaceDeployment element, if the configuration information of the ServiceInterfaceDeployment element does not meet the configuration requirements of the process design, it may also cause the service providing node and the service consuming node to fail to communicate normally.

[0175] Therefore, as shown in Table 8, in this embodiment, if the configuration information of the ServiceInterfaceDeployment element does not meet the configuration requirements of the configuration information of the ServiceInterfaceDeployment element, the following prompt information is output: The instance is not associated with the service instance to machine mapping, the connector of the service instance to machine mapping cannot be mapped to the instance, delete the service instance to machine mapping or delete the instance from the service instance to machine mapping (The instance is not associated with a ServiceInstanceToMachineMapping; The Connector attribute of a ServiceInstanceToMachineMapping cannot map onto the instance.Delete the Mapping or remove the instance from the Mapping).

[0176] Table 8

[0177]

[0178] It's understandable that when users receive this type of prompt, they can determine that the communication failure between the service provider and consumer nodes may be caused by the configuration information of the ServiceInterfaceDeployment element. Furthermore, by checking the configuration information related to the ServiceInterfaceDeployment element in the service provider and consumer nodes, they can correct the communication model and obtain the correct communication model.

[0179] 4. Machine-level verification

[0180] Typically, when designing a communication model based on the AUTOSAR standard, the Machine-level elements that affect communication in the ARXML file of the communication model may include, for example, configuration information of the ProcessToMachineMappingSet element, configuration information of the MachineDesign element, and configuration information of the Machine element.

[0181] 1) For the configuration information of the ProcessToMachineMappingSet element, as shown in Table 9, the configuration requirements include: when the ProcessToMachineMappingSet element is associated with a Process element, the process pointed to by the process-to-machine mapping set should exist and be unique.

[0182] It can be understood that when the first configuration information in this application includes the configuration information of the ProcessToMachineMappingSet element, if the configuration information of the ProcessToMachineMappingSet element does not meet the configuration requirements of the configuration information of the ProcessToMachineMappingSet element, it may also cause the service providing node and the service consuming node to fail to communicate normally.

[0183] Therefore, as shown in Table 9, in this embodiment, when the ProcessToMachineMappingSet element is associated with the process element, if the requirement that the process pointed to by the process-to-machine mapping set should exist and be unique is not met, the following prompt information is output: The process is not associated with a process-to-machine mapping set, the process is associated with multiple process-to-machine mapping sets, and the unnecessary process-to-machine mappings are deleted (The Process is not associated with a ProcessToMachineMapping; The Process is associated with multiple ProcessToMachineMappings; Delete unwanted Mappings).

[0184] Table 9

[0185]

[0186] It's understandable that when users receive this type of prompt, they can determine that the communication failure between the service provider and service consumer nodes may be caused by the configuration information of the ProcessToMachineMappingSet element. Furthermore, by checking the configuration information related to the ProcessToMachineMappingSet element in the service provider and service consumer nodes, they can correct the communication model and obtain the correct communication model.

[0187] 2) For the configuration information of the MachineDesign element, as shown in Table 10, the configuration requirements include: when the MachineDesign element is associated with the Process to Machine (Machine) element, Machine should point to a specified machine design; when the MachineDesign element is not associated with other elements, the communication connector in MachineDesign is not empty.

[0188] It can be understood that when the first configuration information in this application includes the configuration information of the MachineDesign element, if the configuration information of the MachineDesign element does not meet the configuration requirements of the configuration information of the MachineDesign element, it may also cause the service providing node and the service consuming node to fail to communicate normally.

[0189] Therefore, as shown in Table 10, in this embodiment, when the MachineDesign element is associated with the Machine element, if the requirement that the Machine should point to a specified machine design is not satisfied, the following prompt message is output: The Machine is not associated with a MachineDesign.

[0190] When the MachineDesign element is not associated with other elements, the communication connector in the MachineDesign is not empty, and the following prompt message is output: Without the CommunicationConnector aggregation element, the MachineDesign cannot configure an InstanceToMachineMapping.

[0191] Table 10

[0192]

[0193]

[0194] It's understandable that when a user receives this type of prompt, they can determine that the communication failure between the service provider and service consumer nodes may be caused by the configuration information of the MachineDesign element. Furthermore, by checking the configuration information related to the MachineDesign element in the service provider and service consumer nodes, they can correct the communication model and obtain the correct communication model.

[0195] 3) For the configuration information of the Machine element, as shown in Table 11, the configuration requirements include: when the Machine element is associated with the ProcessToMachineMappingSet element and the Process element, the ProcessToMachineMapping in the ProcessToMachineMapping set should point to the specified process and a machine; when the Machine element is associated with the Service Provider Instance element and the Service Consumer Instance RequiredServiceInstance element, if the ProviderServiceInstance and the RequiredServiceInstance are both of the DDS type and the transport plug-in is configured with shared memory SHM, they cannot be deployed on multiple Machines.

[0196] It is understandable that when the first configuration information in this application includes the configuration information of the Machine element, if the configuration information of the Machine element does not meet the configuration requirements of the configuration information of the Machine element, it may also cause the service providing node and the service consuming node to fail to communicate normally.

[0197] Therefore, as shown in Table 11, in this embodiment, when the Machine element is associated with the ProcessToMachineMappingSet element and the Process, if the requirement that the ProcessToMachineMapping should point to a specified process and a machine is not satisfied, the following prompt message is output: The ProcessToMachineMapping is not associated with a Machine.

[0198] If both ProviderServiceInstance and RequiredServiceInstance are of the DDS type and the transport plug-in is configured with a shared memory SHM, and the configuration requirement for not being deployed on multiple machines is not met, the following prompt message is output: The SHM of DDS cannot communicate with multiple machines.

[0199] Table 11

[0200]

[0201]

[0202] It's understandable that when a user receives this type of prompt, they can determine that the communication failure between the service provider node and the service consumer node may be caused by the configuration information of the Machine element. Furthermore, by checking the configuration information related to the Machine element in the service provider node and the service consumer node, they can correct the communication model and obtain the correct communication model.

[0203] In this embodiment, when verifying whether the service providing node and the service consuming node in the communication model can communicate normally, the verification device will obtain the information configured to realize the communication function between the service providing node and the service consuming node (i.e., the first configuration information) from the ARXML file of the communication model. That is, it can be considered that the verification device will obtain some configuration information associated with the communication between the service providing node and the service consuming node from the ARXML file of the communication model, and then verify whether the service providing node and the service consuming node can communicate normally based on the first configuration information and the configuration requirements specified in the system architecture standard applied by the communication model to realize the communication function between the service providing node and the service consuming node, and output prompt information to prompt the user whether the service providing node and the service consuming node can communicate normally.

[0204] Optionally, in the verification method of the communication nodes in the communication model provided in the present application, the verification device can also receive first information, wherein the first information indicates at least one communication instance pair, and each communication instance pair includes a service consumption node and a service provision node that need to communicate; then, the verification device outputs prompt information based on the first configuration information corresponding to the service provision node and the service consumption node in each communication instance pair and the preset configuration requirements.

[0205] During specific implementation, the verification device may receive first information input by the user on the interactive interface to obtain each communication instance pair that needs to be verified.

[0206] Exemplarily, the verification device may provide a first window to the user, wherein the first window is used for the user to select a service providing node and a service consuming node that need to be verified.

[0207] Exemplarily, the verification device may also provide a second window to the user, wherein the second window is used for the user to select a service provider node in the communication model. Then, after the user selects a service provider node in the second window, the verification device may provide the user with a selector, which allows the user to simultaneously select multiple service consumer nodes that need to communicate with the service provider node selected in the second window. Alternatively, after the user selects a service provider node in the second window, the verification device may provide the user with a third window, which includes three options: "Same instance ID," "Same domain ID," and "Same service interface ID." If the user selects any of these options, the verification device will verify all eligible service consumer nodes.

[0208] The above text describes the verification method of the communication nodes in the communication model provided by the present application in combination with Figures 3 to 4. The following text describes the verification device of the communication nodes in the communication model provided by the present application in combination with Figures 5 and 6.

[0209] FIG5 is a schematic structural diagram of a verification device for a communication node in a communication model according to an embodiment of the present application. Specifically, as shown in FIG5 , the device includes: an acquisition module 501 and a processing module 502 .

[0210] Specifically, the acquisition module 501 is used to obtain first configuration information from the configuration file of the communication model, wherein the communication model includes a service providing node and a service consuming node, and the first configuration information includes information configured to realize communication between the service providing node and the service consuming node; the processing module 502 is used to output prompt information based on the first configuration information and preset configuration requirements, and the prompt information indicates whether the service providing node and the service consuming node can communicate normally, and the preset configuration requirements include the configuration requirements specified in the system architecture standard applied by the communication model for realizing the communication function between the service providing node and the service consuming node; the system architecture standard is the automotive open system architecture AUTOSAR, and the configuration file of the communication model is an ARXML file.

[0211] That is to say, when verifying whether the service providing node and the service consuming node in the communication model can communicate normally, the verification device 500 will obtain the information configured to realize the communication function between the service providing node and the service consuming node from the ARXML file of the communication model (that is, the first configuration information). That is, it can be considered that the verification device will obtain some configuration information associated with the communication between the service providing node and the service consuming node from the ARXML file of the communication model, and then verify whether the service providing node and the service consuming node can communicate normally based on the first configuration information and the configuration requirements specified in the system architecture standard applied by the communication model to realize the communication function between the service providing node and the service consuming node, and output prompt information to prompt the user whether the service providing node and the service consuming node can communicate normally.

[0212] In one possible implementation, the acquisition module 501 is also used to receive first information, where the first information indicates at least one communication instance pair, each communication instance pair including a service consumption node and a service provision node that need to communicate; wherein the processing module 502 is specifically used to: output prompt information according to the first configuration information corresponding to the service provision node and the service consumption node in each communication instance pair and the preset configuration requirements.

[0213] In this implementation, the verification device 500 can obtain the service providing node and the service consuming node that the user needs to verify through the first information indicating at least one communication instance pair input by the user on the interactive interface.

[0214] In one possible implementation, the first configuration information includes configuration information of a service interface element; when the configuration information of the service interface element does not comply with the configuration requirements preset for the configuration information of the service interface element in the AUTOSAR standard, the prompt information is specifically used to prompt at least one of the following information: the port and service interface deployment should reference the same service interface, and the service interface element must be configured with at least one of the three communication modes of events, methods, and fields.

[0215] In this implementation, when verification device 500 outputs this type of prompt information, the user can determine, based on the prompt information, that normal communication between the service providing node and the service consuming node may be impossible, and that the cause of this impossible communication may be related to the configuration information of the service interface element. Furthermore, based on the prompt information, the user can check the configuration information related to the service interface element in the service providing node and the service consuming node, thereby obtaining a correct communication model.

[0216] In one possible implementation, the first configuration information includes configuration information of a process design element; when the configuration information of the process design element does not comply with configuration requirements preset for the configuration information of the process design element in the AUTOSAR standard, the prompt information is specifically used to prompt: the process does not point to a process design.

[0217] In this implementation, when verification device 500 outputs this type of prompt information, the user can determine, based on the prompt information, that normal communication between the service providing node and the service consuming node may be impossible, and that the cause of this impossible communication may be related to the configuration information of the process design element. Furthermore, based on the prompt information, the user can check the configuration information related to the process design element in the service providing node and the service consuming node, thereby obtaining a correct communication model.

[0218] In one possible implementation, the first configuration information includes configuration information of an executable file element; when the configuration information of the executable file element does not meet the configuration requirements preset for the configuration information of the executable file element in the AUTOSAR standard, the prompt information is specifically used to prompt at least one of the following information: the process and the process design do not point to the same executable file, and the executable file does not have an aggregate element root software component prototype.

[0219] In this implementation, when verification device 500 outputs this type of prompt information, the user can determine, based on the prompt information, that normal communication between the service providing node and the service consuming node may be impossible, and that the cause of this impossible communication may be related to the configuration information of the executable file element. Furthermore, based on the prompt information, the user can check the configuration information related to the executable file element in the service providing node and the service consuming node, thereby obtaining a correct communication model.

[0220] In one possible implementation, the first configuration information includes configuration information of a service instance to port prototype mapping element; when the configuration information of the service instance to port prototype mapping element does not meet the configuration requirements preset for the configuration information of the service instance to port prototype mapping element in the AUTOSAR standard, the prompt information is specifically used to prompt at least one of the following information: the instance is not associated with the service instance to port prototype mapping, the instance is associated with one or more redundant service instance to port prototype mappings, the redundant mapping is deleted, and the service instance to port prototype mapping does not have an aggregate element port prototype and an executable instance reference is not possible.

[0221] In this implementation, when the verification device 500 outputs this type of prompt information, the user can determine, based on the prompt information, that normal communication between the service providing node and the service consuming node may be impossible, and that the cause of this impossible communication may be related to the configuration information of the service instance to port prototype mapping element. Furthermore, based on the prompt information, the user can check the configuration information related to the service instance to port prototype mapping element in the service providing node and the service consuming node, thereby obtaining a correct communication model.

[0222] In one possible implementation, the first configuration information includes configuration information of a software component type element; when the configuration information of the software component type element does not comply with the configuration requirements preset for the configuration information of the software component type element in the AUTOSAR standard, the prompt information is specifically used to prompt at least one of the following information: the executable file is not associated with the software component type, the service instance to port prototype mapping should correctly configure the root software component prototype to associate with the SWC, the service instance to port prototype mapping should be associated with the port of the SWC, and the type of the port associated with the service instance to port prototype mapping is incorrect.

[0223] In this implementation, when the verification device 500 outputs this type of prompt information, the user can determine, based on the prompt information, that normal communication between the service providing node and the service consuming node may be impossible, and that the cause of this impossible communication may be related to the configuration information of the software component type element. Furthermore, based on the prompt information, the user can check the configuration information related to the software component type element in the service providing node and the service consuming node, thereby obtaining a correct communication model.

[0224] In one possible implementation, the first configuration information includes configuration information of a service instance element; when the configuration information of the service instance element does not comply with the configuration requirements preset for the configuration information of the service instance element in the AUTOSAR standard, the prompt information is specifically used to prompt at least one of the following information: the service provider instance and the service consumer instance are of different types and should be set to the extensible service-oriented middleware SOME / IP type based on the Internet Protocol IP or the data distribution service protocol DDS type; the instance identifiers of the service provider instance and the service consumer instance are inconsistent; the domain identifiers of the service provider instance and the service consumer instance are inconsistent; and the configurations of the QoS files of the service provider instance and the service consumer instance are inconsistent.

[0225] In this implementation, when verification device 500 outputs this type of prompt information, the user can determine, based on the prompt information, that normal communication between the service providing node and the service consuming node may be impossible, and that the cause of this impossible communication may be related to the configuration information of the service instance element. Furthermore, based on the prompt information, the user can check the configuration information related to the service instance element in the service providing node and the service consuming node, thereby obtaining a correct communication model.

[0226] In one possible implementation, the first configuration information includes configuration information of a service interface deployment element; when the configuration information of the service interface deployment element does not comply with the configuration requirements preset for the configuration information of the service interface deployment element in the AUTOSAR standard, the prompt information is specifically used to prompt at least one of the following information: the service provider instance and the service consumer instance associated with the service interface deployment do not reference the same service interface deployment.

[0227] In this implementation, when verification device 500 outputs this type of prompt information, the user can determine, based on the prompt information, that normal communication between the service providing node and the service consuming node may be impossible, and that the cause of this impossible communication may be related to the configuration information of the service interface deployment element. Furthermore, based on the prompt information, the user can check the configuration information related to the service interface deployment element in the service providing node and the service consuming node, thereby obtaining a correct communication model.

[0228] In one possible implementation, the first configuration information includes configuration information of a service instance to machine mapping element; when the configuration information of the service instance to machine mapping element does not meet the configuration requirements preset for the configuration information of the service instance to machine mapping element in the AUTOSAR standard, the prompt information is specifically used to prompt at least one of the following information: the instance is not associated with the service instance to machine mapping, the connector of the service instance to machine mapping cannot be mapped to the instance, the service instance to machine mapping is deleted, or the instance is deleted from the service instance to machine mapping.

[0229] In this implementation, when the verification device 500 outputs this type of prompt information, the user can determine, based on the prompt information, that normal communication between the service providing node and the service consuming node may be impossible, and that the cause of this abnormal communication may be related to the configuration information of the service instance-to-machine mapping element. Furthermore, based on the prompt information, the user can check the configuration information related to the service instance-to-machine mapping element in the service providing node and the service consuming node, thereby obtaining a correct communication model.

[0230] In one possible implementation, the first configuration information includes configuration information of a process-to-machine mapping set element; when the configuration information of the process-to-machine mapping set element does not comply with configuration requirements preset for the configuration information of the process-to-machine mapping set element in the AUTOSAR standard, the prompt information is specifically used to prompt at least one of the following information: the machine is not associated with the machine design, there is no communication connector aggregation element, and the machine design cannot configure instance-to-machine mapping.

[0231] In this implementation, when the verification device 500 outputs this type of prompt information, the user can determine, based on the prompt information, that normal communication between the service providing node and the service consuming node may be impossible, and that the cause of this impossible communication may be related to the configuration information of the process-to-machine mapping set element. Furthermore, based on the prompt information, the user can check the configuration information related to the process-to-machine mapping set element in the service providing node and the service consuming node, thereby obtaining a correct communication model.

[0232] In one possible implementation, the first configuration information includes configuration information of a machine design element; when the configuration information of the machine design element does not comply with configuration requirements preset for the configuration information of the machine design element in the AUTOSAR standard, the prompt information is specifically used to prompt at least one of the following information: there is no communication connector aggregation element, and the machine design cannot configure instance-to-machine mapping.

[0233] In this implementation, when the verification device 500 outputs this type of prompt information, the user can determine, based on the prompt information, that normal communication between the service providing node and the service consuming node may be impossible, and that the cause of this abnormal communication may be related to the configuration information of the machine design element. Furthermore, based on the prompt information, the user can check the configuration information related to the machine design element in the service providing node and the service consuming node, thereby obtaining a correct communication model.

[0234] In one possible implementation, the first configuration information includes configuration information of a machine element; when the configuration information of the machine element does not meet the configuration requirements preset for the configuration information of the machine element in the AUTOSAR standard, the prompt information is specifically used to prompt at least one of the following information: the process-to-machine mapping is not associated with the machine, and the SHM of the DDS cannot communicate with multiple machines.

[0235] In this implementation, when verification device 500 outputs this type of prompt information, the user can determine, based on the prompt information, that normal communication between the service providing node and the service consuming node may be impossible, and that the cause of this abnormal communication may be related to the configuration information of the machine element. Furthermore, based on the prompt information, the user can check the configuration information related to the machine element in the service providing node and the service consuming node, thereby obtaining a correct communication model.

[0236] Figure 6 is a schematic structural diagram of a verification device for a communication node in a communication model according to another embodiment of the present application. The device shown in Figure 6 can be used to execute the method described in any of the above embodiments.

[0237] As shown in Figure 6, the apparatus 600 of this embodiment includes a memory 601 and a processor 602. Optionally, the apparatus 600 further includes a communication interface 603 and a bus 604. The memory 601, the processor 602, and the communication interface 603 are connected to each other via the bus 604.

[0238] The memory 601 may be a read-only memory (ROM), a static storage device, a dynamic storage device, or a random access memory (RAM). The memory 601 may store programs. When the program stored in the memory 601 is executed by the processor 602, the processor 602 is configured to perform the steps of the method shown in FIG. 3 .

[0239] Processor 602 can be a general-purpose central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), one or more integrated circuits, a general-purpose processor, a digital signal processor (DSP), a field programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. Processor 602 is used to execute relevant programs to implement the method shown in FIG. 3 of the present application.

[0240] The processor 602 may also be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the method of FIG. 3 of the embodiment of the present application may be completed by hardware integrated logic circuits in the processor 602 or software instructions.

[0241] The communication interface 603 may use, but is not limited to, a transceiver or other transceiver device to implement communication between the apparatus 600 and other devices or a communication network.

[0242] The bus 604 may include a path for transmitting information between various components of the device 600 (eg, the memory 601 , the processor 602 , and the communication interface 603 ).

[0243] It should be understood that the device 600 shown in the embodiment of the present application may be an electronic device, or may be a chip configured in the electronic device.

[0244] The above embodiments can be implemented in whole or in part by software, hardware, firmware or any other combination. When implemented using software, the above embodiments can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions or computer programs. When the computer instructions or computer program are loaded or executed on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from one website, computer, server or data center to another website, computer, server or data center via a wired (e.g., infrared, wireless, microwave, etc.) method. The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server or data center that contains one or more available media sets. The available medium can be a magnetic medium (e.g., a floppy disk, a hard disk, a tape), an optical medium (e.g., a DVD), or a semiconductor medium. The semiconductor medium can be a solid-state drive.

[0245] It should be understood that the term "and / or" as used herein simply describes a relationship between associated objects, indicating that three possible relationships exist. For example, "A and / or B" can represent: A alone, A and B together, or B alone. A and B can be singular or plural. Furthermore, the character " / " as used herein generally indicates an "or" relationship between the associated objects, but it may also indicate an "and / or" relationship. For specific understanding, please refer to the context.

[0246] In this application, "at least one" means one or more, and "plurality" means two or more. "At least one of the following" or similar expressions refers to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, or c can mean: a, b, c, ab, ac, bc, or abc, where a, b, and c can be single or plural.

[0247] It should 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.

[0248] 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.

[0249] 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.

[0250] 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.

[0251] The above description is merely a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in this application should be included in the scope of protection of this application. Therefore, the scope of protection of this application should be based on the scope of protection of the claims.

Claims

1. A method for verifying a communication node in a communication model, characterized in that: The communication node includes a service providing node and a service consuming node, and the method includes: The verification device obtains first configuration information from a configuration file of the communication model, where the first configuration information includes information configured to implement communication between the service providing node and the service consuming node; The verification device outputs prompt information based on the first configuration information and preset configuration requirements, wherein the prompt information indicates whether the service providing node and the service consuming node can communicate normally, and the preset configuration requirements include configuration requirements specified in the system architecture standard applied by the communication model for implementing the communication function between the service providing node and the service consuming node; The system architecture standard is the automotive open system architecture AUTOSAR, and the configuration file of the communication model is an ARXML file.

2. The method according to claim 1, characterized in that The method further comprises: The verification device receives first information, where the first information indicates at least one communication instance pair, each communication instance pair including a service consuming node and a service providing node that need to communicate; The verification device outputs prompt information according to the first configuration information and preset configuration requirements, including: The verification device outputs prompt information according to the first configuration information corresponding to the service providing node and the service consuming node in each communication instance pair and the preset configuration requirements.

3. The method according to claim 2, characterized in that The first configuration information includes configuration information of a service interface element; When the configuration information of the service interface element does not comply with the configuration requirements preset for the configuration information of the service interface element in the AUTOSAR standard, the prompt information is specifically used to prompt at least one of the following information: the port and service interface deployment should reference the same service interface, and the service interface element must be configured with at least one of the three communication modes of event, method, and field.

4. The method according to claim 3, characterized in that The first configuration information includes configuration information of a process design element; When the configuration information of the process design element does not meet the configuration requirement preset for the configuration information of the process design element in the AUTOSAR standard, the prompt information is specifically used to prompt that the process does not point to a process design.

5. The method according to claim 3 or 4, characterized in that The first configuration information includes configuration information of an executable file element; When the configuration information of the executable file element does not meet the configuration requirements preset for the configuration information of the executable file element in the AUTOSAR standard, the prompt information is specifically used to prompt at least one of the following information: the process and the process design do not point to the same executable file, and the executable file does not have an aggregate element root software component prototype.

6. The method according to any one of claims 3 to 5, characterized in that The first configuration information includes configuration information of a service instance to port prototype mapping element; When the configuration information of the service instance to port prototype mapping element does not meet the configuration requirements preset for the configuration information of the service instance to port prototype mapping element in the AUTOSAR standard, the prompt information is specifically used to prompt at least one of the following information: the instance is not associated with the service instance to port prototype mapping, the instance is associated with one or more redundant service instance to port prototype mappings, the redundant mapping is deleted, and the service instance to port prototype mapping has no aggregate element port prototype and cannot execute instance reference.

7. The method according to any one of claims 3 to 6, characterized in that The first configuration information includes configuration information of a software component type element; When the configuration information of the software component type element does not meet the configuration requirements preset for the configuration information of the software component type element in the AUTOSAR standard, the prompt information is specifically used to prompt at least one of the following information: the executable file is not associated with the software component type, the service instance to port prototype mapping should correctly configure the root software component prototype to associate with the SWC, the service instance to port prototype mapping should be associated with the port of the SWC, and the type of the port associated with the service instance to port prototype mapping is incorrect.

8. The method according to any one of claims 3 to 7, characterized in that The first configuration information includes configuration information of a service instance element; When the configuration information of the service instance element does not comply with the configuration requirements preset for the configuration information of the service instance element in the AUTOSAR standard, the prompt information is specifically used to prompt at least one of the following information: the service provider instance and the service consumer instance have different types and should be set to the extensible service-oriented middleware SOME / IP type based on the Internet interconnection protocol IP or the data distribution service protocol DDS type; the instance identifiers of the service provider instance and the service consumer instance are inconsistent; the domain identifiers of the service provider instance and the service consumer instance are inconsistent; and the configurations of the QoS files of the service provider instance and the service consumer instance are inconsistent.

9. The method according to any one of claims 3 to 8, characterized in that The first configuration information includes configuration information of a service interface deployment element; When the configuration information of the service interface deployment element does not meet the configuration requirements preset for the configuration information of the service interface deployment element in the AUTOSAR standard, the prompt information is specifically used to prompt at least one of the following information: the service provider instance and service consumer instance associated with the service interface deployment do not reference the same service interface deployment.

10. The method according to any one of claims 3 to 9, characterized in that The first configuration information includes configuration information of a service instance to machine mapping element; When the configuration information of the service instance to machine mapping element does not meet the configuration requirements preset for the configuration information of the service instance to machine mapping element in the AUTOSAR standard, the prompt information is specifically used to prompt at least one of the following information: the instance is not associated with the service instance to machine mapping, the connector of the service instance to machine mapping cannot be mapped to the instance, the service instance to machine mapping is deleted, or the instance is deleted from the service instance to machine mapping.

11. The method according to any one of claims 3 to 10, characterized in that The first configuration information includes configuration information of a process-to-machine mapping set element; When the configuration information of the process-to-machine mapping set element does not meet the configuration requirements preset for the configuration information of the process-to-machine mapping set element in the AUTOSAR standard, the prompt information is specifically used to prompt at least one of the following information: the machine is not associated with the machine design, there is no communication connector aggregation element, and the machine design cannot configure instance-to-machine mapping.

12. The method according to any one of claims 3 to 11, characterized in that The first configuration information includes configuration information of machine design elements; When the configuration information of the machine design element does not meet the configuration requirements preset for the configuration information of the machine design element in the AUTOSAR standard, the prompt information is specifically used to prompt at least one of the following information: there is no communication connector aggregation element, and the machine design cannot configure instance to machine mapping.

13. The method according to any one of claims 3 to 12, characterized in that The first configuration information includes configuration information of a machine element; When the configuration information of the machine element does not meet the configuration requirements preset for the configuration information of the machine element in the AUTOSAR standard, the prompt information is specifically used to prompt at least one of the following information: the process to machine mapping is not associated with the machine, and the SHM of DDS cannot communicate with multiple machines.

14. A verification device for a communication node in a communication model, characterized in that: Comprising means for performing the method of any one of claims 1 to 13.

15. A verification device for a communication node in a communication model, characterized in that: include: memory and processor; The memory is used to store program instructions; The processor is configured to call program instructions in the memory to execute the method according to any one of claims 1 to 13.

16. A computer-readable medium, characterized in that The computer-readable medium stores a program code for computer execution, the program code including instructions for executing the method according to any one of claims 1 to 13.

17. A chip, characterized in that: The system comprises at least one processor and a communication interface, wherein the communication interface and the at least one processor are interconnected via a line, and the at least one processor is configured to run a computer program or instruction to perform the method according to any one of claims 1 to 13.

18. A computer program product comprising computer program instructions, characterized in that: When the computer program instructions are executed on a computer, the computer is caused to implement the method according to any one of claims 1 to 13.

Images