Mapping relationship generation method and apparatus, 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] This application relates to the field of intelligent vehicles, and particularly to a method and apparatus for generating a mapping relationship, and a storage medium.

Background Art

[0002] Automotive Open System Architecture (AUTOSAR) is an open and de facto standardized software architecture developed to reduce the development risk of automotive software. With the gradual application of intelligent vehicles, vehicles integrating multiple auxiliary functions such as sensing, planning and control, and autonomous driving are typical high-tech composites. Therefore, vehicles are becoming increasingly intelligent and electronic, and the software structure of vehicles is becoming increasingly complex. The Adaptive Platform is developed based on the original Classic Platform in AUTOSAR.

[0003] Communication management (CM) is the top priority of the AUTOSAR Adaptive Platform. In the process of configuring CM, usually, after a communication service is instantiated, a series of mapping relationships need to be established for the communication service. The general case is to manually establish a mapping relationship one by one for each instance. This is complex and inefficient.

Summary of the Invention

[0004] In view of this, a method and apparatus for generating a mapping relationship, and a storage medium are proposed.

Means for Solving the Problems

[0005] According to the first aspect, an embodiment of the present application provides a mapping relationship generation method. The method includes: obtaining information regarding the mapping relationship between a communication connector on a node and a network domain; obtaining information regarding the mapping relationship between a process and a node, where the information regarding 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; and creating a service instance of the port prototype used by a process in the network domain and creating a mapping relationship between the service instance and a target communication connector on the node based on the information regarding the mapping relationship between the communication connector on the node and the network domain and the information regarding the mapping relationship between the process and the node.

[0006] According to this embodiment of the present application, the service instance is created for the port prototype used by a process in the network domain in order to create a mapping relationship between the service instance and a target communication connector on the 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. As a result, the corresponding node can communicate with the service instance, and there is no need to manually establish the mapping relationship. This simplifies the configuration procedure and improves the configuration efficiency.

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

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

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

[0010] In this way, an association relationship between the process and the software component can be determined, and as a result, a mapping relationship between the service instance in the network domain and the target communication connector can then be automatically created.

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

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

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

[0014] According to this embodiment of the present application, the ID of the network domain is determined. As a result, when the communication protocol is DDS, the service instance can be associated with the network domain ID without the need for manual configuration. Thereby, the configuration process is simplified and the configuration efficiency is improved.

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

[0016] In this way, the node can communicate with another configured object via the communication connector.

[0017] According to the first aspect or the first, second, third, fourth, or fifth possible implementation forms of the first aspect, in the sixth possible implementation form of the mapping relationship generation method, based on the information regarding the mapping relationship between the communication connector on the node and the network domain and the information regarding the mapping relationship between the process and the node, create a service instance of the 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. The step of creating a mapping relationship between the service instance and the target communication connector on the node includes: determining a first communication connector information set corresponding to the network domain based on the information regarding the mapping relationship between the 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 the port prototype of the software component based on the information regarding the mapping relationship between the service instance and the port prototype of the software component, where the second communication connector information set includes at least one communication connector on the target node; and determining 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.

[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. Therefore, in order to implement the mapping from the service instance to the node, the mapping relationship between the service instance and the target communication connector can be established in the configuration process, and the mapping relationship does not need to be established manually. As a result, the configuration procedure is simplified and the efficiency is improved.

[0019] According to the sixth possible implementation of the first aspect, in the seventh possible implementation 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: 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, in order to implement communication between a service instance and a target node, the mapping relationship between the service instance and the target communication connector can be determined without the need to manually search for the target communication connector corresponding to the service instance. Thereby, the configuration procedure is simplified and the efficiency is improved.

[0021] According to the first aspect or the first, second, third, fourth, fifth, sixth, or seventh possible implementation of the first aspect, in the eighth possible implementation of the mapping relationship generation method, this method is used to configure communication services in an AUTomotive Open System ARchitecture (AUTOSAR) adaptation platform.

[0022] In this way, this method can be applied to a vehicle, and as a result, the configuration of Communication Management (CM) can be more efficiently implemented on the AUTOSAR adaptation platform for applying corresponding communication services.

[0023] According to a second aspect, an embodiment of the present application provides a mapping relationship generation apparatus. The apparatus includes a first acquisition module configured to acquire information regarding a mapping relationship between a communication connector on a node and a network domain, and a second acquisition module configured to acquire information regarding a mapping relationship between a process and a node, where the information regarding 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. The apparatus further includes a creation module configured to create a service instance of the port prototype used by a process in the network domain based on the information regarding the mapping relationship between the communication connector on the node and the network domain and the information regarding the mapping relationship between the process and the node, and 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 apparatus, 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.

[0025] According to the second aspect or the 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 forms 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 a process to communicate with another process in the network domain.

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

[0028] According to the second aspect or the first, second, third, or fourth possible implementation of the second aspect, in the fifth possible implementation 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 of the second aspect, in the sixth possible implementation of the mapping relationship generation device, the creation module determines a first communication connector information set corresponding to the network domain based on information regarding the mapping relationship between the 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, determines 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, where the second communication connector information set includes at least one communication connector on the target node, and creates 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 the sixth possible implementation of the second aspect, in the seventh possible implementation of the mapping relationship generation device, creating a mapping relationship between a service instance and a target communication connector based on the first communication connector information set and the second communication connector information set includes determining the target communication connector based on the 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 of the second aspect, in the eighth possible implementation of the mapping relationship generation device, the device is configured to configure communication services in an AUTomotive Open System ARchitecture (AUTOSAR) adaptation platform.

[0032] According to the third aspect, an embodiment of the present application provides a mapping relationship generation device. The device includes a processor and a memory configured to store instructions executable by the processor. When the processor is configured to execute the instructions, a mapping relationship generation method according to the first aspect or one or more of the plurality of possible implementations of the first aspect is implemented.

[0033] According to the fourth aspect, an embodiment of the present application provides a non-volatile computer-readable storage medium. The non-volatile computer-readable storage medium stores computer program instructions. When the computer program instructions are executed by a processor, a mapping relationship generation method according to the first aspect or one or more of the plurality of possible implementations of the first aspect is implemented.

[0034] According to the fifth aspect, an embodiment of the present application provides a terminal device. The terminal device can execute a mapping relationship generation method according to the first aspect or one or more of the plurality of possible implementations 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 includes computer-readable code or a non-volatile computer-readable storage medium carrying the computer-readable code. When the computer-readable code is executed on an electronic device, a processor in the electronic device executes a method for generating a mapping relationship according to the first aspect or one or more possible implementation forms of the first aspect.

[0036] These aspects and other aspects of the present application will be more concise and easier to understand in the following description of the (multiple) embodiments.

[0037] The accompanying drawings included herein and constituting a part of this specification, together with this specification, are intended to show exemplary embodiments, features, and aspects of the present application and to explain the principles of the present application.

Brief Description of the Drawings

[0038]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Embodiments for Carrying Out the Invention

[0039] The following describes in detail various exemplary embodiments, features, and aspects of the present application with reference to the accompanying drawings. The same reference numerals in the accompanying drawings indicate elements having the same or similar functions. Although various aspects of the embodiments are shown in the accompanying drawings, the accompanying drawings are not necessarily drawn to scale unless otherwise specified.

[0040] The specific term "example" in this specification means "used as an example, embodiment, or illustration". Embodiments described as "examples" are not necessarily described as being superior or better than other embodiments.

[0041] Furthermore, for a better explanation of the present application, many specific details are provided in the following specific embodiments. Those skilled in the art should understand that the present application can be implemented without some of these specific details. In some embodiments, well-known methods, means, elements, and circuits 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 may include an application layer, a service layer, and a hardware layer. The application layer may include software used to implement application functions, such as software components (SWCs). The service layer may provide various background services for the application layer, such as core types used to provide communication management CM and data structure definition services. The hardware layer may include each node, and the node may be a vehicle chip mounted on the vehicle, such as a microcontroller unit (MCU), or may be a domain controller including an MCU, in-vehicle infotainment, etc.

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

[0044] Therefore, in the mapping relationship generation method in the present application, a service instance is created in a network domain, and the mapping relationship between the network domain and the communication connectors on each node is determined (which is equivalent to establishing the mapping relationship between the service instance and the node). As a result, a series of mapping relationships can be established in the process of constructing the CM. Finally, the mapping between the service instance and the target communication connector can be implemented without manual operation. Thereby, the efficiency of the configuration process is improved.

[0045] In the application scenario shown in FIG. 1, hereinafter, FIGS. 2 to 7 are used to describe in detail the mapping relationship generation method in the embodiments of the present application.

[0046] FIG. 2 is a flowchart of a mapping relationship generation method according to an embodiment of the present application. As shown in FIG. 2, the present method may be applied to a processor, and the present method 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 the service interface deployment is the data distribution service (DDS), the default domain identifier (domain ID) of the corresponding network domain can be generated for each created network domain.

[0050] Step S202: Configure nodes.

[0051] The process of configuring the node may include configuring an Ethernet cluster. In this process, an Ethernet network configuration, such as an IP address or a subnet mask, may be defined.

[0052] After the Ethernet cluster is configured, the process may further include the step of configuring a node design. In this process, an Ethernet communication connector (i.e., the aforementioned communication connector) on the node may be defined to implement the 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. Corresponding different communication connectors may be defined for different communication protocols. A service discovery IP address may also be defined so that the IP address of the corresponding service can be determined when the corresponding service is accessed.

[0053] When the node is configured, the information regarding the configured node design may be referenced.

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

[0055] Step S203: Configure an application.

[0056] The process of configuring an application may include configuring software component types, such as defining objects and attributes of software components. A receive port prototype (e.g., R-Port Prototype) for requesting services or data on a software component may also be defined, and a transmit port prototype (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. When the executable program is configured, the associated information of the configured software component type may be referenced to implement the association between the executable program and the software component SWC.

[0058] After the executable program is configured, the process may further include steps of configuring a process design. When the process design is configured, the associated information of the configured executable program may be referenced.

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

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

[0061] After the application is configured, a mapping relationship between a process and a node can be established, and a 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 a possible implementation form, in the process of creating a service instance, after the application is configured, in order to establish a mapping relationship between the port prototype of the software component and the service instance, a corresponding service instance may be created for the port prototype of the software component (for example, the service instance is created separately for the P port prototype and the R port prototype). Then, the service instance can be associated with the configured node based on the mapping relationship between the process and the node.

[0065] In the process of creating a service instance, the relevant information of the configured service interface deployment can be referred to.

[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, thus avoiding repetitive configurations. FIG. 3 is a schematic diagram of the creation of 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), can be set as the default. A plurality of service instances, for example, service instance A, service instance B, service instance C, and service instance D in the figure, can be created within the network domain. When the bound communication protocol is DDS, the attribute of the network domain identifier (domain ID) of each service instance that can be created in the network domain can be set to the default network domain identifier of the network domain, and no manual iterative configuration is required. For example, the attributes of the network domain identifiers of service instance A, service instance B, service instance C, and service instance D within the same network domain can be set to 30. In this way, the attributes of the corresponding network domain identifiers within the service instance can be configured. When a service instance is created in a network domain, some other attributes of the service instance can also be automatically configured. This is not limited in the present application.

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

[0068] Determining the mapping relationship between the service instance and the node is to actually perform communication between the node and the service instance. Therefore, it 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 implementation form.

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

[0070] In FIG. 4, the P-port prototype and the R-port prototype may respectively correspond to the P-port Prototype and the R-port Prototype of the software component ports. The connection arrows between the service instance and the P-port prototype and between the service instance and the R-port prototype may indicate the determined mapping relationship between the service instance and the port prototype of the software component. In step S203, by determining the association relationship among the software component, the executable program, and the process and obtaining the mapping relationship between the process and the node, the association relationship among the three (software component, executable program, and process) and the node can be implemented. In this way, the association relationship between the service instance A and the software component corresponding to the P-port prototype of the 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 the service instance A and the executable program A, and the association relationship among the service instance A, the executable program A, and the process A can be obtained, and the node A associated with the service instance is finally determined. Since there is at least one communication connector on the node A, another set ListB can be obtained. The set includes two communication connectors on the node A associated with the service instance A, namely communication connector A and communication connector B.

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

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

[0073] Optionally, the process from step S201 to step S205 may be executed on a visual interface and may be displayed, for example, in the form of a graph or a table. The user can perform operations on the visual interface to modify the configured content. As an example, the graph shown in Figure 4 is used. There are no existing connection arrows in the initial graph of Figure 4. The user can establish connection arrows in the initial graph to determine two mapping relationships corresponding to each other. For the connection arrows established by the user, refer to the solid connection arrows in Figure 4 (for example, the arrow from the P port prototype to service instance A). After the user establishes the mapping relationship corresponding to the solid connection arrow shown in Figure 4, the mapping relationship between the service instance and the corresponding target communication connector can be determined according to the aforementioned method (in this step, no user connection is required, like the dashed connection arrow shown in Figure 4).

[0074] Optionally, after the CM is configured, the CM configuration result may be presented in a visual way such as text, image, or video. For example, the attributes of the objects (such as service instances and nodes) configured during the configuration, the established mapping relationships, etc. may be displayed in the domain view (or the split of the domain CM channel view). In the view, the objects and their attributes may be displayed, and the connection lines between the objects may indicate the mapping relationships established during the configuration.

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

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

[0077] In the process of configuring the service interface, the communication method required by the service can be defined. For each communication method, for example, an event, a method, and a field are defined. The data type required by each communication method (for example, corresponding to the basic data type) can be further determined.

[0078] In the process of configuring the service interface deployment, the relevant information of the configured service interface may be referenced, and the service interface deployment may be further bound to the 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 FIG. 2 is not unique, and the solution in the embodiments of the present application may alternatively be executed in an order different from that shown in FIG. 2. For example, the execution order of step S205 and step S204 may be interchanged.

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

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

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

[0083] Step S503: Based on the information regarding the mapping relationship between the communication connector on the node and the network domain and the information regarding the mapping relationship between the process and the node, create a service instance of the 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 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. As a result, the corresponding node can communicate with the service instance, and there is no need to manually establish the mapping relationship. This simplifies the configuration procedure and improves the configuration efficiency.

[0085] The network domain may be a virtual domain. 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 transmitting port prototype.

[0086] For the related example of creating a service instance of the port prototype used by the process in the network domain in step S503, refer to the related description in step S204 of FIG. 2. It should be noted that creating a service instance of the port prototype used by the process in the network domain may alternatively be associating the service instance with the corresponding port prototype after the service instance is created. For the example from step S501 to step S503, refer to the related description in step S205 of FIG. 2.

[0087] In a possible implementation form, this method is used to configure communication services in an automotive open system architecture AUTOSAR adaptation platform.

[0088] In this way, this method can be applied to a vehicle, and as a result, the configuration of the communication management CM can be more efficiently implemented on the AUTOSAR adaptation platform for applying the corresponding communication service.

[0089] For the architecture of the AUTOSAR adaptation platform, please refer to Figure 1.

[0090] In a possible implementation form, this method further includes steps of creating a network domain and configuring information regarding the mapping relationship between the communication connector on the node and the network domain.

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

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

[0093] In a possible implementation form, this method further includes steps of configuring the mapping relationship between the process and the node and allocating the corresponding software component to the process.

[0094] In this way, the association relationship between the process and the software component can be determined, and as a result, the mapping relationship between the service instance in the network domain and the target communication connector can then be automatically created.

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

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

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

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

[0099] In one possible implementation, the step of creating a network domain and configuring information regarding the mapping relationship between the communication connector on the node and the network domain includes determining the ID of the network domain. Based on the information regarding the mapping relationship between the communication connector on the node and the network domain and the information regarding the mapping relationship between the process and the node, the step of creating a service instance of the port prototype used by the process within the network domain and creating the mapping relationship between the service instance and the target communication connector on the node includes determining that when the communication protocol of the service instance is the data distribution service DDS, the network domain ID associated with the service instance is that ID.

[0100] According to this embodiment of the present application, the ID of the network domain is determined, and as a result, when the communication protocol is DDS, the service instance can be associated with the network domain ID without the need for manual configuration. Thereby, the configuration process is simplified and the configuration efficiency is improved.

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

[0102] For related examples of creating a network domain, refer to the related description in step S201 of FIG. 2. For related examples of determining a network domain ID associated with a service instance, refer to the related description in step S204.

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

[0104] In this way, the node can communicate with another configured object via the communication connector.

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

[0106] Step S601: Based on information regarding the mapping relationship between a communication connector on a node and a 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 information regarding the mapping relationship between a service instance and a port prototype of a 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 a target node.

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

[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. Therefore, in order to implement the mapping from the service instance to the node, the mapping relationship between the service instance and the target communication connector can be established in the configuration process, and the mapping relationship does not need to be established manually. As a result, the configuration procedure is simplified and the efficiency is improved.

[0110] For the example from Step S601 to Step S603, please refer to the relevant description of Step S205 in FIG. 2. The first communication connector information set may be, for example, the aforementioned ListA, and the second communication connector information set may be, for example, the aforementioned ListB.

[0111] FIG. 7 is a flowchart of a mapping relationship generation method according to an embodiment of the present application. As shown in FIG. 7, the step of 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 the following steps.

[0112] Step S701: Determine the 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, in order to implement communication between a service instance and a target node, the 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. As a result, the configuration procedure is simplified and the efficiency is improved.

[0115] Regarding the related examples of step S701 and step S702, refer to the related description of step S205 in FIG. 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] FIG. 8 is a diagram of the structure of a mapping relationship generation device according to an embodiment of the present application. As shown in FIG. 8, the device includes a first acquisition module 801 configured to acquire information regarding the mapping relationship between a communication connector on a node and a network domain, a second acquisition module 802 configured to acquire information regarding the mapping relationship between a process and a node, where the information regarding the mapping relationship between a process and a node includes a software component corresponding to the process, and the software component includes at least one port prototype, and the second acquisition module 802, a creation module 803 configured to create a service instance of a port prototype used by a process in a network domain based on the information regarding the mapping relationship between a communication connector on a node and a network domain and the information regarding the mapping relationship between a process and a node, and create a mapping relationship between the service instance and a target communication connector on the node and includes.

[0117] According to this embodiment of the present application, a service instance is created for a port prototype 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. As a result, the corresponding node can communicate with the service instance, and there is no need to manually establish the mapping relationship. This simplifies the configuration procedure and improves the configuration efficiency.

[0118] In a possible implementation form, the device is configured to configure a communication service in an automotive open system architecture AUTOSAR adaptation platform.

[0119] Therefore, this device can be applied to a vehicle. As a result, 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 a possible implementation form, 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.

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

[0122] In a possible implementation form, the device further includes a second configuration module configured to configure a mapping relationship between a process and a node and allocate a corresponding software component to the process.

[0123] In this way, the association relationship between the process and the software component can be determined, and as a result, the mapping relationship between the service instance in the network domain and the target communication connector can then be automatically created.

[0124] In a possible implementation form, the apparatus further includes a third configuration module configured to configure a port prototype used by a 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, and as a result, the mapping relationship between the service instance in the network domain and the target communication connector can then be automatically created.

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

[0127] According to this embodiment of the present application, the ID of the network domain is determined, and as a result, when the communication protocol is DDS, the service instance can be associated with the network domain ID without the need for manual configuration. Thereby, the configuration process is simplified and the configuration efficiency is improved.

[0128] In a possible implementation form, each communication connector is associated with an Internet protocol IP address.

[0129] In this way, the node can communicate with another configured object via the communication connector.

[0130] In a possible implementation form, the creation module 803 determines a first communication connector information set corresponding to the network domain based on information regarding the mapping relationship between the 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; determines 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, where the second communication connector information set includes at least one communication connector on the target node; and creates 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. Therefore, in order to implement the mapping from the service instance to the node, the mapping relationship between the service instance and the target communication connector can be established in the configuration process, and the mapping relationship does not need to be manually established. Thereby, the configuration procedure is simplified and the efficiency is improved.

[0132] In a possible implementation form, 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 the target communication connector based on the 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, in order to implement communication between a service instance and a target node, the 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. As a result, the configuration procedure is simplified and the efficiency is improved.

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

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

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

[0137] Processor 1101 is the control center of the mapping relationship generation device 1100, and it may be a single processor or a collective term for a plurality of processing elements. For example, processor 1101 may be one or more central processing units (CPUs), or an application specific integrated circuit (ASIC), or one or more integrated circuits implementing the 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, processor 1101 may run or execute a software program stored in memory 1103, call the data stored in memory 1103, and execute various functions of the mapping relationship generation device 1100.

[0139] In one specific implementation form, in one embodiment, processor 1101 may include one or more CPUs, such as CPU0 and CPU1 shown in FIG. 9.

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

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

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

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

[0144] Memory 1103 may be configured to store a software program for executing the solution of the present application, and processor 1101 controls the execution of the software program. For specific implementation forms, reference may be made to the embodiments of the foregoing method, and details will not be described again here.

[0145] The memory 1103 may be a read-only memory (ROM), or another type of static memory communication device capable of storing static information and instructions, a random access memory (RAM), or another type of dynamic memory communication device capable of storing information and instructions. It may be an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM), or another compact disc storage, optical disc storage (including compact discs, laser discs, optical discs, digital versatile discs, Blu-ray optical discs, etc.), a magnetic disk storage medium, or another magnetic memory communication device, or any other medium that can be used to carry or store program code expected in the form of instructions or data structures and can be accessed by a computer. However, the memory 1103 is not limited to this. Note that the memory 1103 may be integrated with the processor 1101 or exist independently and may be 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 in the embodiments of the present application.

[0146] Note that the structure of the mapping relationship generation device 1100 shown in FIG. 9 does not constitute a limitation on the implementation form of the mapping relationship generation device. The actual mapping relationship generation device may include more or fewer components than those shown in the figure, or some components may be combined, or it may have a different component arrangement.

[0147] One embodiment of the present application provides a mapping relationship generation device including a processor and a memory configured to store instructions executable by the processor. When the processor is configured to execute the instructions, the method is implemented.

[0148] One embodiment of the present application provides a terminal device, and the terminal device can execute the foregoing method.

[0149] One embodiment of the present application provides a non-volatile computer-readable storage medium, and the non-volatile computer-readable storage medium stores computer program instructions. When the computer program instructions are executed by a processor, the foregoing method is implemented.

[0150] One embodiment of the present application provides a computer program product including a computer-readable code or a non-volatile computer-readable storage medium carrying the computer-readable code. When the computer-readable code is executed by a processor of an electronic device, the processor of the electronic device executes the foregoing method.

[0151] A computer-readable storage medium may be a tangible device that can hold and store instructions for use by an instruction execution device. The computer-readable storage medium may be, for example, but 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), erasable programmable read only memory (EPROM, or flash memory), static random access memory (SRAM), portable compact disc read only memory (CD-ROM), digital versatile disc (DVD), memory stick, floppy disk, mechanical coding devices such as punch cards or groove-protrusion structures that store instructions, and any suitable combination thereof.

[0152] The computer-readable program instructions or code described in this specification may be downloaded from a computer-readable storage medium to each computing / processing device, or may be downloaded from 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 transmission, wireless transmission, routers, firewalls, switches, gateway computers, and / or edge servers. A network adapter card or network interface within each computing / processing device receives the computer-readable program instructions from the network and transfers the computer-readable program instructions for storage on a computer-readable storage medium within each computing / processing device.

[0153] The computer program instructions used to perform the operations in this application can be assembly instructions, instruction set architecture (ISA) instructions, machine instructions, machine-related instructions, microcode, firmware instructions, status setting data, or source code or target code written in any combination of one or more programming languages. The programming languages include object-oriented programming languages such as Smalltalk and C++, as well as conventional procedural programming languages such as "C" or similar programming languages. All computer-readable program instructions may be executed on a user computer, or some may be executed on a user computer as a stand-alone software package, or some may be executed on the user's local computer and some 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 this application.

[0154] Various aspects of the present application are described herein with reference to the flowcharts and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the present application. It should be understood that each block of the flowcharts and / or block diagrams, as well as 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 the processor of a general-purpose computer, a special-purpose computer, or another programmable data processing apparatus to manufacture a machine, such that the instructions, when executed by the processor of the computer or another programmable data processing apparatus, create an apparatus for implementing the functions / operations specified in one or more blocks of the flowchart and / or block diagram. Alternatively, these computer-readable program instructions may be stored in a computer-readable storage medium. These instructions enable a computer, a programmable data processing apparatus, and / or another device to operate in a particular manner. Accordingly, the computer-readable medium storing the instructions includes an artifact containing instructions for implementing various aspects of the functions / operations specified in one or more blocks of the flowchart and / or block diagram.

[0156] Alternatively, the computer-readable program instructions may be loaded onto a computer, another programmable data processing apparatus, or another device, such that a series of operational steps are executed on the computer, another programmable data processing apparatus, or another device to generate a computer-implemented process. Accordingly, the instructions executed on a computer, another programmable data processing apparatus, or another device implement the functions / operations specified in one or more blocks of the flowchart and / or block diagram.

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

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

[0159] Although the present invention has been described with reference to embodiments, those skilled in the art can understand and implement other variants of the disclosed embodiments by referring to the accompanying drawings, the disclosed content, and the appended claims in the process of implementing the present invention for which protection is claimed. In the claims, "comprising" does not exclude other components or other steps, and "a" or "one" does not exclude a plurality of cases. A single processor or another unit may perform some of the functions listed in the claims. Although some means are described in 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 by way of example and is 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 selection of terms used herein is intended to best explain the principles of the embodiments, the practical application, or the improvement of technology in the market, or to enable another skilled person to understand the embodiments disclosed herein.

Description of Reference Numerals

[0161] 801 First acquisition module 802 Second acquisition module 803 Creation module 1100 Mapping relationship generation device 1101 Processor 1102 Transceiver 1103 Memory 1104 Processor

Claims

A mapping relationship generation method executed by a processor, 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; based on information regarding the mapping relationship between the one or more communication connectors on the at least one node and the network domain and information regarding the mapping relationship between the port prototype of the software component corresponding to the service instance and the service instance, determining a mapping relationship between the service instance and a target communication connector on the at least one node A method comprising the above steps. Claim 2 The step of creating a service instance in the network domain comprises: determining the ID of the network domain; when the communication protocol of the service instance is the data distribution service DDS, determining that the network domain ID associated with the service instance is the ID The method according to claim 1, comprising the above steps. Claim 3 The method according to claim 1 or 2, wherein each of the one or more communication connectors is associated with an Internet protocol IP address. Claim 4 Based on information regarding the mapping relationship between the one or more communication connectors on the at least one node and the network domain and information regarding the mapping relationship between the port prototype of the software component corresponding to the service instance and the service instance, the step of determining a mapping relationship between the service instance and a target communication connector on the at least one node comprises: 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 regarding the mapping relationship between the service instance and the port prototype of the software component, wherein the second communication connector information set includes 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; The method according to any one of claims 1 to 3, comprising:

5. The step of 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, wherein: Obtaining an association relationship between the service instance, an executable program, and a process based on the 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 communication connector information set 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 method according to claim 4, comprising:

6. The step of 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, wherein: 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; The method according to 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 System ARchitecture (AUTOSAR) compliant platform. **Claim 8** A mapping relationship generation device, wherein the device creates a service instance in a network domain, determines a mapping relationship between the network domain and one or more communication connectors on at least one node, and determines a mapping relationship between the service instance and a target communication connector on the at least one node based on information regarding the mapping relationship between the one or more communication connectors on the at least one node and the network domain and information regarding a mapping relationship between a port prototype of a software component corresponding to the service instance and the service instance. A mapping relationship generation device configured as described above. **Claim 9** The device, further configured to determine an ID of the network domain, and determine that the network domain ID associated with the service instance is the ID when the communication protocol of the service instance is the Data Distribution Service (DDS). The device according to claim 8, further configured as described above. **Claim 10** The device according to claim 8 or 9, wherein each of the one or more communication connectors is associated with an Internet Protocol (IP) address. **Claim 11** The device, further configured to determine 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, and determine a second communication connector information set corresponding to the port prototype of the software component based on the 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 a target node. Based on 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 The apparatus according to any one of claims 8 to 10, configured as such. **Claim 12** The apparatus is Based on the mapping relationship between the service instance and the port prototype of the software component, obtain the association relationship between the service instance, the executable program, and the process. Based on the association relationship between the service instance, the executable program, and the process, determine the node associated with the service instance. Based on at least one communication connector on the node associated with the service instance, determine the second communication connector information set corresponding to the port prototype of the software component. The apparatus according to claim 11, configured as such. **Claim 13** The apparatus is Based on the intersection set of the first communication connector information set and the second communication connector information set, determine the target communication connector. Determine the mapping relationship between the service instance and the target communication connector. The apparatus according to claim 11 or 12, configured as such. **Claim 14** The apparatus according to any one of claims 8 to 12, used in an automotive open system architecture AUTOSAR adaptation platform. **Claim 15** A non-volatile computer-readable storage medium storing computer program instructions, wherein when the computer program instructions are executed by a processor, the method according to any one of claims 1 to 7 is implemented. **Claim 16** A computer program including computer-readable code, wherein when the computer-readable code is executed on an electronic device, the processor of the electronic device executes the method according to any one of claims 1 to 7.

Images