Mapping relationship generating method and device, and storage medium

Abstract

The present application relates to a mapping relationship generating method and apparatus, and a storage medium. The method includes the steps of: acquiring information about a mapping relationship between a communication connector on a node and a network domain; acquiring information about a mapping relationship between a process and a node, the information about the mapping relationship between the process and the node including a software component corresponding to the process, the software component including at least one port prototype; and creating a service instance of a port prototype used by a process in a network domain based on the information about the mapping relationship between a communication connector on a node and a network domain and the information about the mapping relationship between the process and the node, and creating a mapping relationship between the service instance and a target communication connector on the node. In this way, it is not necessary to manually establish a mapping relationship for each instance one by one, and therefore the efficiency of the process of configuring communication management can be improved.

Description

[Technical Field]

[0001] The present application relates to the field of intelligent vehicles, and in particular to a mapping relationship generating method and apparatus, and a storage medium. [Background technology]

[0002] Automotive open system architecture (AUTOSAR) is an open, virtually standardized software architecture developed to reduce the development risks of automotive software. With the gradual adoption of intelligent vehicles, vehicles that integrate multiple auxiliary functions such as sensing, planning, and control, as well as autonomous driving, are typical high-tech complexes. Therefore, vehicles are becoming increasingly intelligent and electronic, and their software structure is becoming increasingly complex. The Adaptive Platform is developed with AUTOSAR based on the original Classic Platform.

[0003] Communication management (CM) is a top priority for the AUTOSAR Adaptive Platform. The process of configuring CM typically requires a set of mapping relationships to be established for communication services after they are instantiated. The typical case is to manually establish the mapping relationships for each instance one by one, which is complex and inefficient. Summary of the Invention

[0004] In view of this, a mapping relationship generating method and apparatus, as well as a storage medium, are proposed. [Means for solving the problem]

[0005] According to a first aspect, an embodiment of the present application provides a mapping relationship generation method, the method including the steps of: acquiring information on a mapping relationship between a communication connector on a node and a network domain; acquiring information on the mapping relationship between a process and the node, the information on the mapping relationship between the process and the node including a software component corresponding to the process, the software component including at least one port prototype; and creating a service instance of a port prototype used by the process in the network domain based on the information on the mapping relationship between the communication connector on the node and the network domain and the information on the mapping relationship between the process and the node, and creating a mapping relationship between the service instance and a target communication connector on the node.

[0006] According to this embodiment of the present application, a service instance is created for a port prototype that is used by a process in a network domain to create a mapping relationship between the service instance and a target communication connector on a node. In this way, in the process of configuring the communication management CM, a mapping relationship can be established between the service instance created in the network domain and the target communication connector without manual operation, so that the corresponding node can communicate with the service instance without having to manually establish the mapping relationship. This simplifies the configuration procedure and improves configuration efficiency.

[0007] According to a first aspect, in a first possible implementation form of the mapping relationship generation method, the method further includes a step of creating a network domain and configuring information regarding a mapping relationship between a communication connector on a node and the network domain.

[0008] In this way, a connection between a communication connector on a node and a network domain can be established, so that a mapping relationship between a service instance in the network domain and a target communication connector can then be automatically created.

[0009] According to the first aspect or a first possible implementation form of the first aspect, in a second possible implementation form of the mapping relationship generation method, the method further includes a step of configuring a mapping relationship between a process and a node and assigning a corresponding software component to the process.

[0010] In this way, association relationships between processes and software components can be determined, so that mapping relationships between service instances and target communication connectors in the network domain can then be automatically created.

[0011] According to the first aspect or the first or second possible implementation form of the first aspect, in a third possible implementation form of the mapping relationship generation method, the method further includes a step of configuring a port prototype used by the process to communicate with another process in the network domain.

[0012] In this way, the association relationship between the process and the port prototype can be determined, so that the mapping relationship between the service instance and the target communication connector in the network domain can then be automatically created.

[0013] According to the first, second, or third possible implementation form of the first aspect, in a fourth possible implementation form of the mapping relationship generation method, the step of creating a network domain and configuring information about the mapping relationship between the communication connector on the node and the network domain includes a step of determining an ID of the network domain. The step of creating a service instance of a port prototype used by a process in the network domain based on the information about the mapping relationship between the communication connector on the node and the network domain and the information about the mapping relationship between the process and the node and creating a mapping relationship between the service instance and a target communication connector on the node includes a step of determining, when the communication protocol of the service instance is data delivery service DDS, that a network domain ID associated with the service instance is its ID.

[0014] According to this embodiment of the present application, the ID of the network domain is determined, so that when the communication protocol is DDS, the service instance can be associated with the network domain ID without requiring manual configuration, which simplifies the configuration process and improves configuration efficiency.

[0015] According to the first aspect or the first, second, third or fourth possible implementation form of the first aspect, in a fifth possible implementation form of the mapping relationship generation method, each communication connector is associated with an Internet Protocol IP address.

[0016] In this way, a node can communicate with other configured objects via a communication connector.

[0017] According to the first aspect or the first, second, third, fourth, or fifth possible implementation form of the first aspect, in a sixth possible implementation form of the mapping relationship generation method, the step of creating a service instance of a port prototype used by a process in the network domain based on information regarding the mapping relationship between communication connectors on the node and the network domain and information regarding the mapping relationship between the process and the node, and creating a mapping relationship between the service instance and a target communication connector on the node includes the steps of: determining a first communication connector information set corresponding to the network domain based on information regarding the mapping relationship between the communication connectors on the node and the network domain, the first communication connector information set including at least one communication connector on the node; determining a second communication connector information set corresponding to the port prototype of the software component based on information regarding the mapping relationship between the service instance and the port prototype of the software component, the second communication connector information set including at least one communication connector on the target node; and determining the mapping relationship between the service instance and the target communication connector based on the first communication connector information set and the second communication connector information set.

[0018] According to this embodiment of the present application, two communication connector information sets are determined to determine the target communication connector, and there is no need to manually search for the target communication connector, so that to implement mapping from a service instance to a node, the mapping relationship between the service instance and the target communication connector can be established in the configuration process, and there is no need to manually establish the mapping relationship, which simplifies the configuration procedure and improves efficiency.

[0019] According to a sixth possible implementation form of the first aspect, in a seventh possible implementation form of the mapping relationship generation method, the step of creating a mapping relationship between a service instance and a target communication connector based on a first communication connector information set and a second communication connector information set includes the steps of determining a target communication connector based on an intersection set of the first communication connector information set and the second communication connector information set, and creating a mapping relationship between the service instance and the target communication connector.

[0020] In this way, to implement communication between a service instance and a target node, a mapping relationship between the service instance and the target communication connector can be determined without manually searching for the target communication connector corresponding to the service instance, thereby simplifying the configuration procedure and improving efficiency.

[0021] According to the first aspect or the first, second, third, fourth, fifth, sixth or seventh possible implementation form of the first aspect, in an eighth possible implementation form of the mapping relationship generation method, the method is used for configuring communication services in an Automotive Open Systems Architecture AUTOSAR adaptation platform.

[0022] In this way, the method can be applied to a vehicle, so that the configuration of the communication management CM can be more efficiently implemented on the AUTOSAR adaptation platform to apply the corresponding communication services.

[0023] According to a second aspect, an embodiment of the present application provides a mapping relationship generation apparatus, including: a first acquisition module configured to acquire information about a mapping relationship between a communication connector on a node and a network domain; a second acquisition module configured to acquire information about the mapping relationship between a process and the node, where the information about the mapping relationship between the process and the node includes a software component corresponding to the process, the software component including at least one port prototype; and a creation module configured to create a service instance of a port prototype used by the process in the network domain based on the information about the mapping relationship between the communication connector on the node and the network domain and the information about the mapping relationship between the process and the node, and to create a mapping relationship between the service instance and a target communication connector on the node.

[0024] According to a second aspect, in a first possible implementation form of the mapping relationship generation device, the device further includes a first configuration module configured to create a network domain and configure information regarding a mapping relationship between a communication connector on a node and the network domain.

[0025] According to the second aspect or a first possible implementation form of the second aspect, in a second possible implementation form of the mapping relationship generation apparatus, the apparatus further includes a second configuration module configured to configure a mapping relationship between a process and a node and assign a corresponding software component to the process.

[0026] According to the second aspect or the first or second possible implementation form of the second aspect, in a third possible implementation form of the mapping relationship generation apparatus, the apparatus further includes a third configuration module configured to configure a port prototype used by the process to communicate with another process in the network domain.

[0027] According to the first, second, or third possible implementation form of the second aspect, in a fourth possible implementation form of the mapping relationship generation device, the first configuration module includes determining an ID of a network domain, and the creation module includes determining that the network domain ID associated with the service instance is the ID when the communication protocol of the service instance is a data delivery service (DDS).

[0028] According to the second aspect or the first, second, third or fourth possible implementation form of the second aspect, in a fifth possible implementation form of the mapping relationship generation device, each communication connector is associated with an Internet Protocol IP address.

[0029] According to the second aspect or the first, second, third, fourth, or fifth possible implementation forms of the second aspect, in a sixth possible implementation form of the mapping relationship generating device, the creation module includes: determining a first communication connector information set corresponding to the network domain based on information regarding the mapping relationship between communication connectors on the node and the network domain, where the first communication connector information set includes at least one communication connector on the node; determining a second communication connector information set corresponding to a port prototype of the software component based on information regarding the mapping relationship between the service instance and a port prototype of the software component, where the second communication connector information set includes at least one communication connector on the target node; and creating a mapping relationship between the service instance and the target communication connector based on the first communication connector information set and the second communication connector information set.

[0030] According to a sixth possible implementation form of the second aspect, in a seventh possible implementation form of the mapping relationship generating device, creating a mapping relationship between a service instance and a target communication connector based on a first communication connector information set and a second communication connector information set includes determining a target communication connector based on an intersection set of the first communication connector information set and the second communication connector information set, and creating a mapping relationship between the service instance and the target communication connector.

[0031] According to the second aspect or the first, second, third, fourth, fifth, sixth or seventh possible implementation form of the second aspect, in an eighth possible implementation form of the mapping relationship generation device, the device is configured to configure communication services in an Automotive Open Systems Architecture AUTOSAR adaptation platform.

[0032] According to a third aspect, an embodiment of the present application provides a mapping relationship generating apparatus, the apparatus including: a processor; and a memory configured to store instructions executable by the processor, the instructions, when configured to execute, to perform a mapping relationship generating method according to the first aspect or one or more of a plurality of possible implementation forms of the first aspect.

[0033] According to a fourth aspect, an embodiment of the present application provides a non-volatile computer-readable storage medium storing computer program instructions that, when executed by a processor, perform a mapping relationship generation method according to the first aspect or one or more of a plurality of possible implementation forms of the first aspect.

[0034] According to a fifth aspect, an embodiment of the present application provides a terminal device, which may perform the mapping relationship generation method according to the first aspect or one or more of a plurality of possible implementation forms of the first aspect.

[0035] According to a sixth aspect, an embodiment of the present application provides a computer program product, the computer program product including computer-readable code or a non-volatile computer-readable storage medium carrying the computer-readable code, which, when executed on an electronic device, causes a processor in the electronic device to perform the mapping relationship generation method according to the first aspect or one or more possible implementations of the first aspect.

[0036] These and other aspects of the present application will be more concise and easier to understand in the description of the embodiment(s) that follows.

[0037] The accompanying drawings and this specification, which are incorporated in and constitute a part of this specification, together illustrate exemplary embodiments, features, and aspects of the present application and are intended to explain the principles of the present application. [Brief explanation of the drawings]

[0038] [Figure 1] FIG. 1 is a schematic diagram of an application scenario according to an embodiment of the present application; [Figure 2] 1 is a flowchart of a mapping relationship generating method according to an embodiment of the present application; [Figure 3] FIG. 2 is a schematic diagram of creating a service instance in a network domain according to an embodiment of the present application; [Figure 4] FIG. 2 is a schematic diagram of determining a mapping relationship according to an embodiment of the present application; [Figure 5] 1 is a flowchart of a mapping relationship generating method according to an embodiment of the present application; [Figure 6] 1 is a flowchart of a mapping relationship generating method according to an embodiment of the present application; [Figure 7] 1 is a flowchart of a mapping relationship generating method according to an embodiment of the present application; [Figure 8] FIG. 2 is a structural diagram of a mapping relationship generating apparatus according to an embodiment of the present application; [Figure 9]FIG. 2 is a structural diagram of a mapping relationship generating apparatus according to an embodiment of the present application; DETAILED DESCRIPTION OF THE INVENTION

[0039] Various exemplary embodiments, features, and aspects of the present application are described in detail below with reference to the accompanying drawings, in which identical reference numerals indicate elements having the same or similar functions. While various aspects of the embodiments are illustrated in the accompanying drawings, the accompanying drawings are not necessarily drawn to scale unless otherwise specified.

[0040] The specific term "exemplary" herein means "serving as an example, embodiment, or illustration." An embodiment described as an "exemplary" is not necessarily described as being superior or better than other embodiments.

[0041] Furthermore, in order to better explain the present application, many specific details are provided in the following specific embodiments. It should be understood by those skilled in the art that the present application can be practiced without some of the specific details. In some embodiments, methods, means, elements and circuits well known to those skilled in the art are not described in detail so as to emphasize the subject matter of the present application.

[0042] FIG. 1 is a schematic diagram of an application scenario according to an embodiment of the present application. The mapping relationship generation method in the present application can be used in the process of configuring communication management on an AUTOSAR adaptive platform. As shown in FIG. 1, the architecture of the AUTOSAR adaptive platform can include an application layer, a service layer, and a hardware layer. The application layer can include software used to implement application functions, such as software components (SWCs). The service layer can provide various background services for the application layer, such as core types used to provide communication management CMs and data structure definition services. The hardware layer can include each node, which can be a vehicle chip installed in a vehicle, such as a microcontroller unit (MCU), or a domain controller including an MCU, in-vehicle infotainment, etc.

[0043] In the process of configuring a CM, a communication service usually needs to be instantiated on the CM. Specifically, after a service instance is determined, a set of mapping relationships is established for the communication service to establish a mapping relationship between the service instance and a node (sometimes called a machine) in the hardware layer, so that the software component SWC in the application layer can apply the communication service corresponding to the service instance. In this process, if the mapping relationships are manually established for each service instance one by one, the process becomes very complicated.

[0044] Therefore, in the mapping relationship generation method in the present application, a service instance is created in a network domain, and a mapping relationship between the network domain and a communication connector on each node is determined (corresponding to establishing a mapping relationship between the service instance and the node), so that a set of mapping relationships can be established in the process of configuring a CM. Finally, the mapping between the service instance and the target communication connector can be implemented without manual operation, which improves the efficiency of the configuration process.

[0045] In the application scenario shown in FIG. 1, the following will use FIG. 2 to FIG. 7 to describe in detail the mapping relationship generation method in the embodiment of the present application.

[0046] 2 is a flowchart of a mapping relationship generating method according to an embodiment of the present application. As shown in FIG. 2, the method may be applied to a processor, and includes the following steps:

[0047] Step S201: Create a network domain.

[0048] Optionally, the network domain may be a virtual network domain.

[0049] When the communication protocol bound to a service interface deployment is a data distribution service (DDS), a default domain identifier (domain ID) for the corresponding network domain may be generated for each created network domain.

[0050] Step S202: Configure the node.

[0051] The process of configuring a node may include configuring an ethernet cluster, in which the ethernet network configuration, for example, IP address or subnet mask, may be defined.

[0052] After the Ethernet cluster is configured, the process may further include configuring a node design. In this process, an ethernet communication connector on the node may be defined to implement an association between the node and the communication connector. Each communication connector on the node may assign an IP address to the node to implement communication between the node and another network domain, service instance, etc. Different corresponding communication connectors may be defined for different communication protocols. A service discovery IP address may also be defined so that the IP address of a corresponding service can be determined when the corresponding service is accessed.

[0053] Once a node is configured, information about the configured node design may be referenced.

[0054] After the nodes are configured, a mapping relationship between the network domain and the communication connector on each node can be created. The mapping relationship can be established between the network domain and multiple nodes. In this process, for each node, a communication connector on the node can be selected to establish a mapping relationship with the network domain.

[0055] Step S203: Configure the application.

[0056] The process of configuring an application may include configuring a software component type, such as defining the objects and attributes of the software component. Receive port prototypes (e.g., R-Port Prototype) for requesting services or data on the software component may also be defined, and send port prototypes (e.g., P-Port Prototype) for providing services or data may also be defined.

[0057] After the software component type is configured, the process may further include configuring an executable program, whereby association information for the configured software component type may be referenced to implement an association between the executable program and the software component SWC.

[0058] After the executable program is configured, the process may further include configuring a process design, where relevant information about the configured executable program may be referenced when the process design is configured.

[0059] After the process design is configured, the process may further include configuring the process. When the process is configured, related information of the configured executable program and related information of the process design may be referenced to implement an association between the process and the executable program.

[0060] In this way, association relationships between software components (including port prototypes on software components), executable programs, and processes can be implemented.

[0061] After the application is configured, a mapping relationship between the process and the node can be established, and the mapping relationship between the process and the software component is obtained based on the association relationship between the software component, the executable program, and the process, and the corresponding software component is assigned to the process.

[0062] Step S204: Create a service instance in the network domain.

[0063] The network domain may be the network domain created in step S201.

[0064] In one possible implementation, in the process of creating a service instance, after an application is configured, corresponding service instances may be created for port prototypes of the software components to establish a mapping relationship between the port prototypes of the software components and the service instances (e.g., service instances are created separately for P port prototypes and R port prototypes). The service instances may then be associated with the configured nodes based on the mapping relationship between the processes and the nodes.

[0065] In the process of creating a service instance, the relevant information of the configured service interface deployment may be referenced.

[0066] When the bound communication protocol is DDS, the network domain identifier and the service instance can be automatically associated without the need for manual configuration, thereby avoiding repetitive configuration. FIG. 3 is a schematic diagram of creating a service instance in a network domain according to an embodiment of the present application. As shown in FIG. 3, for the network domain created in step S201, a network domain identifier, for example, 30 (the network domain identifier may be modified), may be set as a default. Multiple service instances, for example, service instance A, service instance B, service instance C, and service instance D in the figure, may be created in the network domain. When the bound communication protocol is DDS, the network domain identifier (domain ID) attribute of each service instance that may be created in the network domain may be set to the default network domain identifier of the network domain, and no manual repetitive configuration is required. For example, the network domain identifier attribute of service instance A, service instance B, service instance C, and service instance D in the same network domain may be set to 30. In this way, the corresponding network domain identifier attribute in the service instance can be configured. When a service instance is created in a network domain, some other attributes of the service instance may also be automatically configured. This is not a limitation in this application.

[0067] Step S205: Determine the mapping relationship between the service instance and the node.

[0068] Determining the mapping relationship between a service instance and a node is to actually implement communication between the node and the service instance, and therefore is to actually determine the mapping relationship between the service instance and the target communication connector on the node. The mapping relationship between the service instance and the target communication connector can be implemented in the following manner.

[0069] 4 is a schematic diagram of determining a mapping relationship according to an embodiment of the present application. As shown in FIG. 4, a solid connection arrow in the diagram may indicate that a mapping relationship is established between two connected parties. For example, a connection arrow between network domain 1 and communication connector B may indicate a mapping relationship between network domain 1 and a communication connector on node A, and a connection arrow between network domain 1 and communication connector C may indicate a mapping relationship between network domain 1 and a communication connector on node B. In this manner, a set of communication connectors, ListA, may be obtained based on the mapping relationship between network domain 1 and each of the communication connectors on node A and node B. The set includes communication connectors B and C, which correspond to the communication connectors on node A and node B, respectively, configured to connect to network domain 1.

[0070] In FIG. 4, the P-port prototype and the R-port prototype may correspond to the port prototypes P-port Prototype and R-port Prototype of the software component, respectively. The connecting arrows between the service instance and the P-port prototype and the connecting arrows between the service instance and the R-port prototype may indicate the mapping relationship between the determined service instance and the port prototype of the software component. In step S203, the association relationships between the software component, the executable program, and the process are determined, and the association relationships between the three (software component, executable program, and process) and the node can be implemented by obtaining the mapping relationship between the process and the node. In this way, the association relationship between service instance A and the software component corresponding to the P-port prototype of software component A can be obtained by using the mapping relationship between the service instance (e.g., service instance A) and the port prototype of the software component. As a result, the association relationship between service instance A and the executable program A, and the association relationship between service instance A, the executable program A, and the process A can be obtained, and the node A associated with the service instance can be finally determined. Because there is at least one communication connector on node A, another set ListB can be obtained. The set includes two communication connectors on node A that are associated with service instance A: communication connector A and communication connector B.

[0071] The intersection set of List A and List B can be used to determine a unique communication connector as the target communication connector, i.e., communication connector B. Thus, a mapping relationship between service instance A and communication connector B can be determined. See the dashed connection arrow between service instance A and communication connector B in Figure 4. Similarly, for other service instances B, C, and D, see the corresponding dashed connection arrows in Figure 4.

[0072] In this way, the corresponding target communication connector can be found, and a mapping relationship between the service instance and the target communication connector can be established, completing the process of configuring the CM. In this process, the user does not need to manually search, compare, and configure, thereby improving the efficiency of the configuration process.

[0073] Optionally, the processes of steps S201 to S205 may be performed on a visual interface and may be displayed, for example, in a graph or table. A user may perform operations on the visual interface to modify the configured content. As an example, the graph shown in FIG. 4 is used. No existing connection arrows exist in the initial graph of FIG. 4. A user may establish connection arrows in the initial graph to determine two corresponding mapping relationships. For the connection arrows established by the user, refer to the solid connection arrows in FIG. 4 (e.g., the arrow from the P port prototype to service instance A). After a user establishes the mapping relationships corresponding to the solid connection arrows shown in FIG. 4, the mapping relationships between the service instances and the corresponding target communication connectors may be determined according to the above-described method (like the dashed connection arrows shown in FIG. 4, no user connection is required in this step).

[0074] Optionally, after a CM is configured, the CM configuration results may be presented in a visual manner, such as text, images, or videos. For example, attributes of objects (such as service instances and nodes) configured during configuration, established mapping relationships, etc. may be displayed in a domain view (or a division of a domain CM channel view). In the view, objects and their attributes may be displayed, and connecting lines between objects may indicate the mapping relationships established during configuration.

[0075] It should be noted that in one possible implementation, the basic data type definition, the service interface configuration, and the service interface deployment configuration may be completed before step S201.

[0076] The process of defining a basic data type may be implemented using a core type service, where the data type may be, for example, an integer (int) or a floating point (float).

[0077] In the process of configuring a service interface, the communication methods required by the service can be defined. Each communication method defines, for example, events, methods, and fields. The data types required by each communication method (e.g., corresponding to basic data types) can also be determined.

[0078] In the process of configuring a service interface deployment, related information of the configured service interface may be referenced, and the service interface deployment may be further bound to a corresponding communication protocol. In addition to DDS, the bound communication protocol may alternatively be a communication protocol such as scalable service-oriented middleware over IP (SOME / IP).

[0079] It should be noted that the execution order of the steps shown in Figure 2 is not unique, and the solutions in the embodiments of the present application may alternatively be executed in an order different from the order shown in Figure 2. For example, the execution order of step S205 and step S204 may be swapped.

[0080] 5 is a flowchart of a mapping relationship generating method according to an embodiment of the present application. The method may be applied to a processor. As shown in FIG. 5, the method includes the following steps:

[0081] S501: Obtain information about the mapping relationship between the communication connector on the node and the network domain.

[0082] Step S502: Obtain information about the mapping relationship between the process and the node, where the information about the mapping relationship between the process and the node includes a software component corresponding to the process, and the software component includes at least one port prototype.

[0083] Step S503: Based on information about the mapping relationship between the communication connector on the node and the network domain and information about the mapping relationship between the process and the node, create a service instance of a port prototype used by the process in the network domain, and create a mapping relationship between the service instance and the target communication connector on the node.

[0084] According to this embodiment of the present application, a service instance is created for a port prototype that is used by a process in a network domain to create a mapping relationship between the service instance and a target communication connector on a node. In this way, in the process of configuring the communication management CM, a mapping relationship can be established between the service instance created in the network domain and the target communication connector without manual operation, so that the corresponding node can communicate with the service instance without having to manually establish the mapping relationship. This simplifies the configuration procedure and improves configuration efficiency.

[0085] The network domain may be a virtual domain. The at least one port prototype may be a plurality of groups of port prototypes, and each group of port prototypes may include a receiving port prototype and a sending port prototype.

[0086] For a related example of creating a service instance of a port prototype used by a process in the network domain in step S503, see the related description of step S204 in Figure 2. Note that creating a service instance of a port prototype used by a process in the network domain may alternatively involve associating the service instance with the corresponding port prototype after the service instance is created. For an example of steps S501 to S503, see the related description of step S205 in Figure 2.

[0087] In one possible implementation, the method is used to configure communication services in an Automotive Open Systems Architecture AUTOSAR adaptation platform.

[0088] In this way, the method can be applied to a vehicle, so that the configuration of the communication management CM can be more efficiently implemented on the AUTOSAR adaptation platform to apply the corresponding communication services.

[0089] See Figure 1 for the architecture of the AUTOSAR adaptive platform.

[0090] In one possible implementation, the method further comprises creating a network domain and configuring information about a mapping relationship between a communication connector on the node and the network domain.

[0091] In this way, a connection between a communication connector on a node and a network domain can be established, so that a mapping relationship between a service instance in the network domain and a target communication connector can then be automatically created.

[0092] For this process, please refer to the relevant description of step S201 in FIG.

[0093] In one possible implementation, the method further comprises configuring a mapping relationship between the processes and the nodes and assigning corresponding software components to the processes.

[0094] In this way, association relationships between processes and software components can be determined, so that mapping relationships between service instances and target communication connectors in the network domain can then be automatically created.

[0095] For this process, please refer to the relevant description of step S203 in FIG.

[0096] In one possible implementation, the method further includes configuring a port prototype used by the process to communicate with another process in the network domain.

[0097] In this way, the association relationship between the process and the port prototype can be determined, so that the mapping relationship between the service instance and the target communication connector in the network domain can then be automatically created.

[0098] For this process, please refer to the relevant description of step S203 in FIG.

[0099] In one possible implementation, creating a network domain and configuring information about the mapping relationship between the communication connector on the node and the network domain includes determining an ID of the network domain. Creating a service instance of a port prototype used by a process in the network domain based on the information about the mapping relationship between the communication connector on the node and the network domain and the information about the mapping relationship between the process and the node and creating a mapping relationship between the service instance and a target communication connector on the node includes determining, when the communication protocol of the service instance is data delivery service DDS, that the network domain ID associated with the service instance is its ID.

[0100] According to this embodiment of the present application, the ID of the network domain is determined, so that when the communication protocol is DDS, the service instance can be associated with the network domain ID without requiring manual configuration, which simplifies the configuration process and improves configuration efficiency.

[0101] The ID of the network domain may be a network domain identifier, and the ID may be modified as necessary.

[0102] For a related example of creating a network domain, see the related description of step S201 in Figure 2. For a related example of determining a network domain ID associated with a service instance, see the related description of step S204.

[0103] In one possible implementation, each communication connector is associated with an Internet Protocol IP address.

[0104] In this way, a node can communicate with other configured objects via a communication connector.

[0105] 6 is a flowchart of a mapping relationship generating method according to an embodiment of the present application. As shown in FIG. 6, based on information about the mapping relationship between the communication connector on the node and the network domain and information about the mapping relationship between the process and the node, creating a service instance of a port prototype used by a process in the network domain and creating a mapping relationship between the service instance and the target communication connector on the node includes the following steps:

[0106] Step S601: Based on information about the mapping relationship between communication connectors on the node and the network domain, determine a first communication connector information set corresponding to the network domain, where the first communication connector information set includes at least one communication connector on the node.

[0107] Step S602: Based on the information about the mapping relationship between the service instance and the port prototype of the software component, determine a second communication connector information set corresponding to the port prototype of the software component, where the second communication connector information set includes at least one communication connector on the target node.

[0108] Step S603: Create a mapping relationship between the service instance and the target communication connector based on the first communication connector information set and the second communication connector information set.

[0109] According to this embodiment of the present application, two communication connector information sets are determined to determine the target communication connector, and there is no need to manually search for the target communication connector, so that to implement mapping from a service instance to a node, the mapping relationship between the service instance and the target communication connector can be established in the configuration process, and there is no need to manually establish the mapping relationship, which simplifies the configuration procedure and improves efficiency.

[0110] For examples of steps S601 to S603, please refer to the related description of step S205 in Figure 2. The first communication connector information set may be, for example, the above-mentioned List A, and the second communication connector information set may be, for example, the above-mentioned List B.

[0111] 7 is a flowchart of a mapping relationship generating method according to an embodiment of the present application. As shown in FIG. 7, creating a mapping relationship between a service instance and a target communication connector based on a first communication connector information set and a second communication connector information set includes the following steps:

[0112] Step S701: Determine a target communication connector based on the intersection set of the first communication connector information set and the second communication connector information set.

[0113] Step S702: Create a mapping relationship between the service instance and the target communication connector.

[0114] In this way, to implement communication between a service instance and a target node, a mapping relationship between the service instance and the target communication connector can be determined without manually searching for the target communication connector corresponding to the service instance, thereby simplifying the configuration procedure and improving efficiency.

[0115] For related examples of step S701 and step S702, please refer to the related description of step S205 in Figure 2. The intersection set of the first communication connector information set and the second communication connector information set is, for example, the intersection set of ListA and ListB described above.

[0116] 8 is a structural diagram of a mapping relationship generating device according to an embodiment of the present application. As shown in FIG. 8, the device includes: a first obtaining module 801 configured to obtain information about a mapping relationship between a communication connector on a node and a network domain; a second acquiring module 802 configured to acquire information about a mapping relationship between a process and a node, the information about the mapping relationship between the process and the node including a software component corresponding to the process, the software component including at least one port prototype; a creating module 803 configured to create a service instance of a port prototype used by a process in the network domain based on information about a mapping relationship between a communication connector on the node and the network domain and information about a mapping relationship between a process and the node, and to create a mapping relationship between the service instance and a target communication connector on the node; Includes.

[0117] According to this embodiment of the present application, a service instance is created for a port prototype that is used by a process in a network domain to create a mapping relationship between the service instance and a target communication connector on a node. In this way, in the process of configuring the communication management CM, a mapping relationship can be established between the service instance created in the network domain and the target communication connector without manual operation, so that the corresponding node can communicate with the service instance without having to manually establish the mapping relationship. This simplifies the configuration procedure and improves configuration efficiency.

[0118] In one possible implementation, the apparatus is configured to configure communication services in an Automotive Open Systems Architecture AUTOSAR adaptation platform.

[0119] Therefore, this device can be applied to a vehicle, so that the configuration of the communication management CM can be more efficiently implemented on the AUTOSAR adaptation platform to apply the corresponding communication service.

[0120] In one possible implementation, the apparatus further includes a first configuration module configured to create a network domain and configure information regarding a mapping relationship between a communication connector on a node and the network domain.

[0121] In this way, a connection between a communication connector on a node and a network domain can be established, so that a mapping relationship between a service instance in the network domain and a target communication connector can then be automatically created.

[0122] In one possible implementation, the apparatus further includes a second configuration module configured to configure a mapping relationship between the processes and the nodes and assign corresponding software components to the processes.

[0123] In this way, association relationships between processes and software components can be determined, so that mapping relationships between service instances and target communication connectors in the network domain can then be automatically created.

[0124] In one possible implementation, the apparatus further includes a third configuration module configured to configure a port prototype used by the process to communicate with another process in the network domain.

[0125] In this way, the association relationship between the process and the port prototype can be determined, so that the mapping relationship between the service instance and the target communication connector in the network domain can then be automatically created.

[0126] In one possible implementation, the first configuration module includes determining an ID of a network domain, and the creation module 803 includes determining that the network domain ID associated with the service instance is the ID when the communication protocol of the service instance is a data delivery service (DDS).

[0127] According to this embodiment of the present application, the ID of the network domain is determined, so that when the communication protocol is DDS, the service instance can be associated with the network domain ID without requiring manual configuration, which simplifies the configuration process and improves configuration efficiency.

[0128] In one possible implementation, each communication connector is associated with an Internet Protocol IP address.

[0129] In this way, a node can communicate with other configured objects via a communication connector.

[0130] In one possible implementation, the creation module 803 includes: determining a first communication connector information set corresponding to the network domain based on information regarding a mapping relationship between a communication connector on the node and the network domain, where the first communication connector information set includes at least one communication connector on the node; determining a second communication connector information set corresponding to a port prototype of the software component based on information regarding a mapping relationship between the service instance and a port prototype of the software component, where the second communication connector information set includes at least one communication connector on the target node; and creating a mapping relationship between the service instance and the target communication connector based on the first communication connector information set and the second communication connector information set.

[0131] According to this embodiment of the present application, two communication connector information sets are determined to determine the target communication connector, and there is no need to manually search for the target communication connector, so that to implement mapping from a service instance to a node, the mapping relationship between the service instance and the target communication connector can be established in the configuration process, and there is no need to manually establish the mapping relationship, which simplifies the configuration procedure and improves efficiency.

[0132] In one possible implementation, creating a mapping relationship between the service instance and the target communication connector based on the first communication connector information set and the second communication connector information set includes determining a target communication connector based on an intersection set of the first communication connector information set and the second communication connector information set, and creating a mapping relationship between the service instance and the target communication connector.

[0133] In this way, to implement communication between a service instance and a target node, a mapping relationship between the service instance and the target communication connector can be determined without manually searching for the target communication connector corresponding to the service instance, thereby simplifying the configuration procedure and improving efficiency.

[0134] 9 is a diagram of the structure of a mapping relationship generating device according to an embodiment of the present application. The mapping relationship generating device 1100 may be configured to execute the mapping relationship generating method shown in any one of FIGS. 2 to 7. For example, the mapping relationship generating device may be a server, or may be a chip (system) or other part or component that may be disposed inside the server. This is not limited in the embodiment of the present application.

[0135] 9, the mapping relationship generating device 1100 may include a processor 1101 and a transceiver 1102. Optionally, the mapping relationship generating device 1100 may include a memory 1103. The processor 1101 is coupled to the transceiver 1102, and the memory 1103 may be connected via a communication bus, for example.

[0136] Next, each unit of the mapping relationship generating device 1100 will be described in detail with reference to FIG.

[0137] The processor 1101 is a control center of the mapping relationship generation device 1100 and may be a single processor or a collective term for multiple processing elements. For example, the processor 1101 may be one or more central processing units (CPUs), or application specific integrated circuits (ASICs), or may be configured as one or more integrated circuits that implement embodiments of the present application, such as one or more digital signal processors (DSPs) or one or more field programmable gate arrays (FPGAs).

[0138] Optionally, the processor 1101 may run or execute software programs stored in the memory 1103 and access data stored in the memory 1103 to perform various functions of the mapping relationship generating device 1100.

[0139] In one specific implementation, in one embodiment, the processor 1101 may include one or more CPUs, for example, CPU0 and CPU1 shown in FIG.

[0140] In one possible implementation, the mapping relationship generating apparatus 1100 may also include multiple processors, such as the processor 1101 and the processor 1104 shown in FIG. 9. Each of the processors may be a single-core processor (single-core CPU) or a multi-core processor (multi-core CPU). The processor here may be one or more communication devices, circuits, and / or processing cores configured to process data (e.g., computer program instructions).

[0141] The transceiver 1102 is configured to communicate with another server.

[0142] Optionally, the transceiver 1102 may include a receiver and a transmitter (not separately shown in FIG. 9), where the receiver is configured to perform receiving functions and the transmitter is configured to perform transmitting functions.

[0143] Optionally, the transceiver 1102 may be integrated with the processor 1101 or may exist independently, and is coupled to the processor 1101 via an input / output port (not shown in FIG. 9 ) of the mapping relationship generating device 1100. This is not limited in the embodiment of the present application.

[0144] The memory 1103 may be configured to store a software program for implementing the solution of the present application, and the processor 1101 controls the execution of the software program. For specific implementation forms, please refer to the aforementioned method embodiments, and the details will not be described again here.

[0145] The memory 1103 may be a read-only memory (ROM) or another type of static storage and communication device capable of storing static information and instructions, a random access memory (RAM) or another type of dynamic storage and communication device capable of storing information and instructions, an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or another compact disc storage, an optical disc storage (including a compact disc, a laser disc, an optical disc, a digital versatile disc, a Blu-ray optical disc, etc.), a magnetic disk storage medium or another magnetic storage and communication device, or any other medium that can be used to carry or store expected program code in the form of instructions or data structures and that can be accessed by a computer. However, the memory 1103 is not limited thereto. It should be noted that the memory 1103 may be integrated with the processor 1101 or exist independently, and is coupled to the processor 1101 via an input / output port (not shown in FIG. 9 ) of the mapping relationship generation device 1100. This is not limited to the embodiments of the present application.

[0146] 9 does not constitute a limitation on the implementation of the mapping relationship generation device. An actual mapping relationship generation device may include more or fewer components than those shown in the figure, may combine some components, or may have a different component arrangement.

[0147] An embodiment of the present application provides a mapping relationship generating device, including a processor and a memory configured to store instructions executable by the processor, wherein the processor is configured to execute the instructions to perform a method.

[0148] An embodiment of the present application provides a terminal device, which can perform the aforementioned method.

[0149] An embodiment of the present application provides a non-volatile computer-readable storage medium, which stores computer program instructions that, when executed by a processor, perform the aforementioned method.

[0150] One embodiment of the present application provides a computer program product including computer readable code or a non-volatile computer readable storage medium carrying the computer readable code, which when executed by a processor of an electronic device causes the processor of the electronic device to perform the aforementioned method.

[0151] A computer-readable storage medium may be a tangible device capable of retaining and storing instructions for use by an instruction execution device. A computer-readable storage medium may be, for example, but is not limited to, an electronic storage device, a magnetic storage device, an optical storage device, an electromagnetic storage device, a semiconductor storage device, or any suitable combination thereof. More specific examples (non-exhaustive list) of computer-readable storage media include portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), electrically programmable read-only memory (EPROM, or flash memory), static random-access memory (SRAM), portable compact disc read-only memory (CD-ROM), digital versatile disk (DVD), memory stick, floppy disk, mechanical coding device, such as a punched card or slotted structure for storing instructions, and any suitable combination thereof.

[0152] The computer-readable program instructions or code described herein may be downloaded from a computer-readable storage medium to each computing / processing device, or may be downloaded to an external computer or external storage device via a network, such as the Internet, a local area network, a wide area network, and / or a wireless network. The network may include copper transmission cables, optical fiber transmissions, wireless transmissions, routers, firewalls, switches, gateway computers, and / or edge servers. A network adapter card or network interface in each computing / processing device receives the computer-readable program instructions from the network and forwards the computer-readable program instructions for storage in a computer-readable storage medium in each computing / processing device.

[0153] The computer program instructions used to perform the operations in this application may be assembly instructions, Instruction Set Architecture (ISA) instructions, machine instructions, machine-related instructions, microcode, firmware instructions, status setting data, or source or target code written in any combination of one or more programming languages. Programming languages ​​include object-oriented programming languages ​​such as Smalltalk and C++, as well as traditional procedural programming languages ​​such as "C" or similar programming languages. All computer-readable program instructions may be executed on the user computer, or some may be executed on the user computer as a standalone software package, or some may be executed on the user's local computer and some may be executed on a remote computer, or all instructions may be executed on a remote computer or server. When a remote computer is involved, the remote computer may be connected to the user computer via any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., connected via the Internet using an Internet service provider). In some embodiments, an electronic circuit, such as a programmable logic circuit, a field-programmable gate array (FPGA), or a programmable logic array (PLA), is customized by using the status information of the computer-readable program instructions. The electronic circuit may execute the computer-readable program instructions to implement various aspects of the present application.

[0154] Various aspects of the present application are described herein with reference to flowcharts and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the present application. It will be understood that each block of the flowcharts and / or block diagrams, and combinations of blocks in the flowcharts and / or block diagrams, may be implemented by computer-readable program instructions.

[0155] These computer-readable program instructions may be provided to a processor of a general-purpose computer, a special-purpose computer, or another programmable data processing device to manufacture a machine, such that the instructions, when executed by the processor of the computer or another programmable data processing device, create an apparatus for performing the functions / operations specified in one or more blocks of the flowcharts and / or block diagrams. Alternatively, these computer-readable program instructions may be stored on a computer-readable storage medium. These instructions cause a computer, programmable data processing device, and / or another device to operate in a particular manner. Thus, a computer-readable medium storing instructions comprises an artifact including instructions for implementing various aspects of the functions / operations specified in one or more blocks of the flowcharts and / or block diagrams.

[0156] Alternatively, the computer-readable program instructions may be loaded into a computer, another programmable data processing apparatus, or another device, such that the computer, another programmable data processing apparatus, or another device performs a series of operational steps to produce a computer-implemented process. Thus, the instructions executing on the computer, another programmable data processing apparatus, or another device perform the functions / acts specified in one or more blocks of the flowcharts and / or block diagrams.

[0157] The flowcharts and block diagrams in the accompanying drawings illustrate the system architecture, functionality, and operation of possible implementations of apparatuses, systems, methods, and computer program products according to embodiments of the present application. In this regard, each block in the flowcharts or block diagrams may represent a module, program segment, or portion of an instruction, which includes one or more executable instructions for implementing the specified logical function(s). In some alternative implementations, the functions marked in the blocks may also occur in a different order from that marked in the accompanying drawings. For example, two consecutive blocks may in fact be executed substantially in parallel or may be executed in the reverse order depending on the functions involved.

[0158] It should also be noted that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, may be implemented by hardware (e.g., a circuit or ASIC (Application Specific Integrated Circuit)) that performs the corresponding function or operation, or may be implemented by a combination of hardware and software, e.g., firmware.

[0159] Although the present invention has been described with reference to embodiments, in the process of implementing the claimed invention, those skilled in the art may understand and implement other variations of the disclosed embodiments by referring to the accompanying drawings, the disclosed content, and the appended claims. In the claims, "comprising" does not exclude other elements or steps, and "a" or "an" does not exclude a plurality. A single processor or other unit may perform several functions recited in the claims. Although several means are recited in mutually different dependent claims, this does not mean that these means cannot be combined to produce better effects.

[0160] The above describes embodiments of the present application. The foregoing description is exemplary, not exhaustive, and is not limited to the disclosed embodiments. Many modifications and variations will be apparent to those skilled in the art without departing from the scope of the described embodiments. The choice of terms used herein is intended to best explain the principles, practical applications, or improvements to market technologies of the embodiments, or to enable others skilled in the art to understand the embodiments disclosed herein. [Explanation of symbols]

[0161] 801 First Acquisition Module 802 Second Acquisition Module 803 Creation Module 1100 Mapping relation generation device 1101 processor 1102 Transceiver 1103 Memory 1104 processor

Claims

1. A processor-implemented method for generating a mapping relationship, the method comprising: creating a service instance in a network domain; determining a mapping relationship between the network domain and one or more communication connectors on at least one node; determining a mapping relationship between the service instance and a target communication connector on the at least one node based on information about the mapping relationship between the one or more communication connectors on the at least one node and the network domain and information about a mapping relationship between a port prototype of a software component corresponding to the service instance and the service instance; A method comprising:

2. creating a service instance in the network domain; determining an identity of the network domain; determining that a network domain ID associated with the service instance is the ID when the communication protocol of the service instance is a data distribution service (DDS); 2. The method of claim 1, comprising:

3. 3. The method of claim 1, wherein each communication connector of the one or more communication connectors is associated with an Internet Protocol IP address.

4. determining a mapping relationship between the service instance and a target communication connector on the at least one node based on information about the mapping relationship between the one or more communication connectors on the at least one node and the network domain and information about a mapping relationship between a port prototype of a software component corresponding to the service instance and the service instance, determining a first communication connector information set corresponding to the network domain based on the information regarding the mapping relationship between the one or more communication connectors on the at least one node and the network domain, the first communication connector information set including at least one communication connector on the node; determining a second communication connector information set corresponding to the port prototype of the software component based on information about a mapping relationship between the service instance and the port prototype of the software component, the second communication connector information set including at least one communication connector on a target node; determining the mapping relationship between the service instance and the target communication connector based on the first communication connector information set and the second communication connector information set; 4. The method of claim 1, comprising:

5. determining a second communication connector information set corresponding to the port prototype of the software component based on information about a mapping relationship between the service instance and the port prototype of the software component, obtaining an association relationship between the service instance, an executable program, and a process based on a mapping relationship between the service instance and the port prototype of the software component; determining a node associated with the service instance based on the association relationship between the service instance, the executable program, and the process; determining the second set of communication connector information corresponding to the port prototype of the software component based on at least one communication connector on the node associated with the service instance; 5. The method of claim 4, comprising:

6. determining the mapping relationship between the service instance and the target communication connector based on the first communication connector information set and the second communication connector information set, determining the target communication connector based on an intersection set of the first communication connector information set and the second communication connector information set; determining the mapping relationship between the service instance and the target communication connector; 6. The method of claim 4 or 5, comprising:

7. The method according to any one of claims 1 to 6, wherein the method is used to configure communication services in an Automotive Open Systems Architecture AUTOSAR adaptation platform.

8. A mapping relationship generating device, comprising: Create a service instance in your network domain, determining a mapping relationship between the network domain and one or more communication connectors on at least one node; Determine a mapping relationship between the service instance and a target communication connector on the at least one node based on information about the mapping relationship between the one or more communication connectors on the at least one node and the network domain and information about a mapping relationship between a port prototype of a software component corresponding to the service instance and the service instance. The mapping relationship generating device is configured to:

9. The device, determining an identity of the network domain; When the communication protocol of the service instance is a data delivery service (DDS), the network domain ID associated with the service instance is determined to be the ID. The apparatus of claim 8 , further configured to:

10. 10. The apparatus of claim 8 or 9, wherein each communication connector of the one or more communication connectors is associated with an Internet Protocol IP address.

11. The device, determining a first communication connector information set corresponding to the network domain based on the information regarding the mapping relationship between one or more communication connectors on the at least one node and the network domain, the first communication connector information set including at least one communication connector on the node; determining a second communication connector information set corresponding to the port prototype of the software component based on information about a mapping relationship between the service instance and the port prototype of the software component, the second communication connector information set including at least one communication connector on a target node; determining the mapping relationship between the service instance and the target communication connector based on the first communication connector information set and the second communication connector information set; 11. The apparatus according to claim 8, configured to:

12. The device, Obtaining an association relationship between the service instance, an executable program, and a process based on a mapping relationship between the service instance and the port prototype of the software component; determining a node associated with the service instance based on the association relationship between the service instance, the executable program, and the process; determining the second set of communication connector information corresponding to the port prototype of the software component based on at least one communication connector on the node associated with the service instance; The device of claim 11 configured to:

13. The device, determining the target communication connector based on an intersection set of the first communication connector information set and the second communication connector information set; Determine the mapping relationship between the service instance and the target communication connector 13. The apparatus according to claim 11 or 12, configured to:

14. 13. The apparatus according to claim 8, wherein the apparatus is used in an Automotive Open Systems Architecture AUTOSAR adaptation platform.

15. 8. A non-volatile computer-readable storage medium having stored thereon computer program instructions that, when executed by a processor, perform the method of any one of claims 1 to 7.

16. 8. A computer program comprising computer readable code which, when executed on an electronic device, causes a processor of the electronic device to perform the method of any one of claims 1 to 7.

Images