WO2023065218A1 - 一种映射关系生成方法、装置和存储介质 - Google Patents

一种映射关系生成方法、装置和存储介质 Download PDF

Info

Publication number
WO2023065218A1
WO2023065218A1 PCT/CN2021/125308 CN2021125308W WO2023065218A1 WO 2023065218 A1 WO2023065218 A1 WO 2023065218A1 CN 2021125308 W CN2021125308 W CN 2021125308W WO 2023065218 A1 WO2023065218 A1 WO 2023065218A1
Authority
WO
WIPO (PCT)
Prior art keywords
mapping relationship
communication connector
node
network domain
service instance
Prior art date
Application number
PCT/CN2021/125308
Other languages
English (en)
French (fr)
Inventor
胡勇
叶俊
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to EP21960968.2A priority Critical patent/EP4407447A1/en
Priority to CN202180007810.8A priority patent/CN116324721A/zh
Priority to PCT/CN2021/125308 priority patent/WO2023065218A1/zh
Publication of WO2023065218A1 publication Critical patent/WO2023065218A1/zh
Priority to US18/641,758 priority patent/US20240275688A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/12—Discovery or management of network topologies
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs

Definitions

  • the present application relates to the field of smart cars, and in particular to a method, device and storage medium for generating a mapping relationship.
  • Automotive open system architecture (automotive open system architecture, AUTOSAR) is an open and de facto standardized software architecture developed to reduce the risk of automotive software development. With the gradual application of smart cars, cars that integrate various auxiliary functions such as perception, regulation and control, and automatic cruise are typical high-tech complexes. Its appearance makes cars more and more intelligent and electronic, and also makes The software structure of the car is becoming more and more complex. AUTOSAR launched the Adaptive Platform on the original Classic Platform.
  • communication management (communication management, CM) is the top priority of AUTOSAR Adaptive Platform.
  • CM communication management
  • it is usually for Manually establishing the mapping relationship for each instance one by one is cumbersome and inefficient.
  • an embodiment of the present application provides a method for generating a mapping relationship, the method comprising: 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 the node, The mapping relationship information between the process and the node includes the software component corresponding to the process, and the software component includes at least one port prototype; according to the mapping relationship information between the communication connector on the node and the network domain , the mapping relationship information between the process and the node, create a service instance for the port prototype used by the process in the network domain, and create a connection between the service instance and the target communication connector on the node Mapping relations.
  • the communication management can be configured In the process of CM, the mapping relationship between the service instance created in the network domain and the target communication connector can be established without manual operation, so that the corresponding node can communicate with the service instance. There is no need to manually establish the mapping relationship, which simplifies the configuration process , improving the configuration efficiency.
  • the method further includes: creating the network domain, and configuring the mapping between the communication connector on the node and the network domain relationship information.
  • connection between the communication connector on the node and the network domain can be established, so that the mapping relationship between the service instance in the network domain and the target communication connector can be automatically created subsequently.
  • the method further includes: configuring the link between the process and the node mapping relationship, and assign corresponding software components to the process.
  • association relationship between the process and the software component can be determined, so that the mapping relationship between the service instance in the network domain and the target communication connector can be automatically created subsequently.
  • the method further includes: configuring the process to communicate with another Prototype of the port used by processes to communicate in the network domain.
  • association relationship between the process and the port prototype can be determined, so that the mapping relationship between the service instance in the network domain and the target communication connector can be automatically created subsequently.
  • the network domain is created and configured on the node
  • the mapping relationship information between the communication connector of the communication connector and the network domain including: determining the ID of the network domain; according to the mapping relationship information between the communication connector on the node and the network domain, the process and the node Mapping relationship information between, create a service instance for the port prototype used by the process in the network domain, and create a mapping relationship between the service instance node and the target communication connector, including: in the When the communication protocol of the service instance is the data distribution service DDS, it is determined that the network domain ID associated with the service instance is the ID.
  • the network domain ID can be associated with the service instance without manual setting, thereby simplifying the configuration process and improving configuration efficiency.
  • each communication connection The server is associated with an Internet protocol IP address.
  • a sixth possible implementation of the mapping relationship generating method Create a service instance for the port prototype used by the process in the network domain according to the mapping relationship information between the communication connector on the node and the network domain and the mapping relationship information between the process and the node , and creating a mapping relationship between the service instance and the target communication connector on the node, including: determining the first corresponding to the network domain according to the mapping relationship information between the communication connector on the node and the network domain A communication connector information set, the first communication connector information set includes at least one communication connector on the node; according to the mapping relationship information between the service instance and the software component port prototype, determine the corresponding port prototype of the software component A second communication connector information set, the second communication connector information set includes at least one communication connector on the target node; according to the first communication connector information set and the second communication connector information set, determine the The mapping relationship between the service instance and the target communication connector.
  • mapping relationship between the service instance and the target communication connector can be established during the configuration process, and there is no need to The mapping relationship is manually established to realize the mapping from service instances to nodes, which simplifies the configuration process and improves efficiency.
  • mapping relationship generation method according to the first communication connector information set and the second communication connector information set , creating a mapping relationship between the service instance and the target communication connector, including: determining the target communication connector according to the intersection of 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.
  • 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 realizing the communication between the service instance and the target node, simplifying the configuration process and improving efficiency.
  • the method is used to configure communication services in the Automotive Open System Architecture AUTOSAR Adaptive Platform.
  • the method can be applied to vehicles, so that the communication management CM configuration can be more efficiently implemented in the AUTOSAR adaptive platform to apply corresponding communication services.
  • an embodiment of the present application provides a device for generating a mapping relationship, the device comprising: a first acquisition module, configured to acquire mapping relationship information between a communication connector on a node and a network domain; a second acquisition module, configured to Obtaining the mapping relationship information between the process and the node, the mapping relationship information between the process and the node includes the software component corresponding to the process, and the software component includes at least one port prototype; creating a module, using Based on the mapping relationship information between the communication connector on the node and the network domain, and the mapping relationship information between the process and the node, create a service for the port prototype used by the process in the network domain instance, and create a mapping relationship between the service instance and the target communication connector on the node.
  • the device further includes: a first configuration module, configured to create the network domain and configure the communication connector on the node Mapping relationship information with the network domain.
  • the device further includes: a second configuration module, configured to configure the process Mapping relationship with the node, and assign corresponding software components to the process.
  • the device further includes: a third configuration module configured to A port prototype used by the process to communicate with another process in the network domain is configured.
  • the first configuration module includes: determining the network Domain ID; the creation module includes: when the communication protocol of the service instance is DDS, determining that the ID of the network domain associated with the service instance is the ID.
  • each communication connection The server is associated with an Internet protocol IP address.
  • the creation module includes: according to the mapping relationship information between the communication connector on the node and the network domain, determine the first communication connector information set corresponding to the network domain, the first communication connector information set includes at least one The communication connector on the node; according to the mapping relationship information between the service instance and the software component port prototype, determine the second communication connector information set corresponding to the software component port prototype, and the second communication connector information set includes the target At least one communication connector on the node; create a mapping relationship between the service instance and the target communication connector according to the first communication connector information set and the second communication connector information set.
  • mapping relationship generation device according to the first communication connector information set and the second communication connector information set , creating a mapping relationship between the service instance and the target communication connector, including: determining the target communication connector according to the intersection of 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.
  • the device is used to configure communication services in the AUTOSAR Adaptive Platform of the Automotive Open System Architecture.
  • an embodiment of the present application provides a device for generating a mapping relationship, the device comprising: a processor; a memory for storing instructions executable by the processor; wherein the processor is configured to execute the instructions
  • the embodiments of the present application provide a non-volatile computer-readable storage medium, on which computer program instructions are stored, and when the computer program instructions are executed by a processor, the above-mentioned first aspect or the first aspect can be realized One or several mapping relationship generation methods in various possible implementation manners.
  • the embodiments of the present application provide a terminal device, which can execute the method for generating a mapping relationship in one or more of the above-mentioned first aspect or multiple possible implementation manners of the first aspect.
  • the embodiments of the present application provide a computer program product, including computer readable codes, or a non-volatile computer readable storage medium bearing computer readable codes, when the computer readable codes are stored in an electronic
  • the processor in the electronic device executes the method for generating a mapping relationship in the first aspect or in one or more possible implementation manners of the first aspect.
  • Fig. 1 shows a schematic diagram of an application scenario according to an embodiment of the present application.
  • Fig. 2 shows a flowchart of a method for generating a mapping relationship according to an embodiment of the present application.
  • Fig. 3 shows a schematic diagram of creating a service instance in a network domain according to an embodiment of the present application.
  • Fig. 4 shows a schematic diagram of determining a mapping relationship according to an embodiment of the present application.
  • Fig. 5 shows a flowchart of a method for generating a mapping relationship according to an embodiment of the present application.
  • Fig. 6 shows a flowchart of a method for generating a mapping relationship according to an embodiment of the present application.
  • Fig. 7 shows a flowchart of a method for generating a mapping relationship according to an embodiment of the present application.
  • Fig. 8 shows a structural diagram of an apparatus for generating a mapping relationship according to an embodiment of the present application.
  • Fig. 9 shows a structural diagram of an apparatus for generating a mapping relationship according to an embodiment of the present application.
  • Fig. 1 shows a schematic diagram of an application scenario according to an embodiment of the present application.
  • the mapping relationship generation method of the present application can be used in the process of configuring communication management on the AUTOSAR adaptive platform.
  • the architecture of AUTOSAR adaptive platform can include application layer, service layer and hardware layer.
  • the application layer can include software for implementing application functions, such as software components (software component, SWC), etc.;
  • the service layer can provide various background services for the application layer, such as communication management CM, core types for providing data structure definition services (core types);
  • the hardware layer may include each node, and the node may be a vehicle chip built in the vehicle, such as a microcontroller unit (MCU), or a domain controller including an MCU and a vehicle.
  • MCU microcontroller unit
  • the process of configuring the CM it is usually necessary to instantiate the communication service in the CM, that is, after determining the service instance (service instance), establish a series of mapping relationships for it, so as to realize the establishment of service instances and nodes on the hardware layer (which can be called machine) mapping relationship, so that the software component SWC in the application layer can apply the communication service corresponding to the service instance.
  • the mapping relationship is manually established for each service instance one by one, the process will be very cumbersome.
  • mapping relationship generation method of the present application create a service instance in the network domain, determine the mapping relationship between the network domain and the communication connector (connector) on each node (equivalent to establishing the mapping relationship between the service instance and the node), Therefore, a series of mapping relationships can be established in the process of configuring the CM, and finally the mapping between service instances and target communication connectors can be realized without manual operation, which improves the efficiency in the configuration process.
  • mapping relationship generation method of the embodiment of the present application is introduced in detail through FIGS. 2-7:
  • Fig. 2 shows a flowchart of a method for generating a mapping relationship according to an embodiment of the present application. As shown in Figure 2, the method can be used in a processor, and the method includes:
  • Step S201 creating a network domain.
  • the network domain may be a virtual network domain.
  • the communication protocol bound to the service interface deployment is a data distribution service (data distribution service, DDS), for each created network domain, a default domain identifier ( domain ID).
  • DDS data distribution service
  • Step S202 configuring a node.
  • the process of configuring the nodes may include: configuring an ethernet cluster.
  • network configurations of the Ethernet such as IP addresses and subnet masks, may be defined.
  • the Ethernet cluster can also include: configuring the node design (machine design).
  • machine design you can define the Ethernet communication connector on the node (the communication connector above) , realize the association between the node and the communication connector, and each communication connector on the node can assign an IP address to it, so as to realize the communication between the node and other network domains, service instances, etc.
  • Corresponding different communication connectors can be defined for different communication protocols.
  • Service discovery IP can also be defined, so that its IP address can be determined when accessing the corresponding service.
  • mapping relationship between the network domain and the communication connectors on each node can be established.
  • a network domain can establish a mapping relationship with multiple nodes, and in the process, for each node, a communication connector on the node can be selected to establish a mapping relationship with the network domain.
  • Step S203 configuring an application.
  • the process of configuring the application may include: configuring the software component type, for example, defining the objects and attributes of the software component. It is also possible to define a receiving port prototype (R-Port Prototype) for requesting services or data on a software component, and a sending port prototype (P-Port Prototype) for providing services or data.
  • R-Port Prototype receiving port prototype
  • P-Port Prototype sending port prototype
  • configuring the software component type it can also include: configuring the executable program (executable).
  • configuring the executable program you can refer to the relevant information of the configured software component type, so that the executable program and the software component SWC can be realized. association.
  • the executable program may also include: configuring a process design (process design), and when configuring the process design, relevant information of the configured executable program may be referenced.
  • process design process design
  • relevant information of the configured executable program may be referenced.
  • configuring the process design it can also include: configuring the process (process).
  • the configuring process the related information of the configured executable program and the related information of the process design can be referenced, so that the process and the executable program can be realized. associated.
  • mapping relationship between the process and the node can be established, and the mapping relationship between the process and the software component can be obtained according to the association relationship between the software component, the executable program, and the process, so as to realize the allocation of the corresponding software for the process components.
  • Step S204 creating a service instance in the network domain.
  • the network domain may be the network domain created in step S201.
  • service instances in the process of creating service instances, after configuring the application, create corresponding service instances for software component port prototypes (for example, create service instances for P port prototypes and R port prototypes respectively ), so as to establish the mapping relationship between software component port prototype and service instance. Then, according to the above-mentioned mapping relationship between processes and nodes, service instances can be associated with configured nodes.
  • software component port prototypes for example, create service instances for P port prototypes and R port prototypes respectively
  • FIG. 3 shows a schematic diagram of creating a service instance in a network domain according to an embodiment of the present application.
  • a network domain identifier may be defaulted, for example, 30 (the network domain identifier can be modified).
  • Multiple service instances can be created in the network domain, such as service instance A, service instance B, service instance C, and service instance D in the figure.
  • the domain ID (domain ID) attribute of each service instance that can be created in the network domain can be set as the default network domain ID of the network domain, without manual repeated configuration.
  • the attribute of network domain identifiers in service instances A, B, C, and D in the same network domain may be set to 30. Therefore, the configuration of the attribute corresponding to the network domain identifier in the service instance can be realized.
  • some other attributes of the service instance may also be automatically configured, which is not limited in this application.
  • Step S205 determining the mapping relationship between service instances and nodes.
  • Determining the mapping relationship between the service instance and the node is actually to realize the communication between the node and the service instance, so it is actually determining 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 realized through one of the following implementation manners.
  • FIG. 4 shows a schematic diagram of determining a mapping relationship according to an embodiment of the present application.
  • the solid-line connection arrows in the figure may indicate that the two parties of the connection have established a mapping relationship.
  • the connection arrow between network domain 1 and communication connector B can indicate the mapping relationship between network domain 1 and the communication connector on node A
  • the connection arrow between network domain 1 and communication connector C can indicate the mapping between network domain 1 and node B.
  • the mapping relationship of the communication connector can indicate the mapping relationship between network domain 1 and node B.
  • a set ListA of communication connectors can be obtained, which includes communication connector B and communication connector C, corresponding to node A respectively and the communication connector on B for connection to network domain 1.
  • the P-port prototype and the R-port prototype can correspond to the software component port prototypes P-port Prototype and R-port Prototype respectively, and the connection arrows between the P-port prototype and the R-port prototype and the service instance can indicate the above-mentioned determined service instance
  • the mapping relationship with the port prototype of the software component Since in step S203, the association relationship between the software component, the executable program, and the process is determined, by obtaining the mapping relationship between the process and the node, the relationship between the software component, the executable program, and the process and the node can be realized. relationship.
  • association relationship between service instance A and a software component corresponding to a P port prototype of software component A can be obtained through the mapping relationship between service instance (for example, service instance A) and software component port prototype, so that the service can be obtained
  • service instance for example, service instance A
  • software component port prototype so that the service can be obtained
  • the corresponding target communication connector can be found, the mapping relationship between the service instance and the target communication connector can be established, and the CM configuration process can be completed.
  • the user does not need to manually search, compare, and configure, which improves the efficiency of the configuration process. .
  • step S201-step S205 can be performed on a visual interface, such as displayed in a graph, a table, etc., and the user can operate on the visual interface to modify the configured content.
  • a visual interface such as displayed in a graph, a table, etc.
  • the user can operate on the visual interface to modify the configured content.
  • the graph shown in Figure 4 there is no existing connecting arrow in the initial graph in Figure 4, and the user can establish a connecting arrow in the initial graph to determine the corresponding mapping relationship between the two.
  • the connecting arrow established by the user can be found in Figure 4.
  • the configuration result of the CM may be displayed in a visual manner such as text, image, or video.
  • the properties of objects configured during the configuration process (such as service instances, nodes, etc.) and established mapping relationships can be displayed in a domain view (or domain-specific CM channel view, etc.), and objects and Its attributes, and the connection lines between objects represent the mapping relationship established in the configuration process.
  • step S201 the definition of the basic data type (data type), the configuration of the service interface (service interface), and the configuration of the deployment of the service interface can be completed before step S201.
  • the process of defining basic data types can be implemented by using services in core types, such as integer (int), floating point (float) and so on.
  • the communication mode required by the service can be defined, and for each communication mode, for example, events (events), methods (methods) and fields (fields) are defined therein. It is also possible to determine the data type required by each communication mode (for example, corresponding to the above-mentioned basic data type).
  • the bound communication protocol can also be a communication protocol such as IP-based scalable service-oriented middleware (scalable service-oriented middleware over IP, SOME/IP).
  • step S205 and step S204 may be reversed.
  • Fig. 5 shows a flowchart of a method for generating a mapping relationship according to an embodiment of the present application. This method can be used in the processor, as shown in Figure 5, the method includes:
  • Step S501 obtaining the mapping relationship information between the communication connector on the node and the network domain
  • Step S502 obtaining mapping relationship information between a process and the node, the mapping relationship information between the process and the node includes a software component corresponding to the process, and the software component includes at least one port prototype;
  • Step S503 according to the mapping relationship information between the communication connector on the node and the network domain, the mapping relationship information between the process and the node is the port prototype used by the process in the network domain Create a service instance, and create a mapping relationship between the service instance and the target communication connector on the node.
  • the communication management can be configured In the process of CM, the mapping relationship between the service instance created in the network domain and the target communication connector can be established without manual operation, so that the corresponding node can communicate with the service instance. There is no need to manually establish the mapping relationship, which simplifies the configuration process , improving the configuration efficiency.
  • the network domain may be a virtual domain.
  • the at least one port prototype may be multiple groups of port prototypes, and each group of port prototypes may include a receiving port prototype and a sending port prototype.
  • step S503 For related examples of creating a service instance for the port prototype used by the process in the network domain in step S503, refer to the relevant description in step S204 in FIG. 2 . It should be noted that the port prototype used by the process in the network domain Create a service instance, or associate the service instance with the corresponding port prototype after creating the service instance. For an example of step S501-step S503, refer to the relevant description in step S205 in FIG. 2 .
  • the method is used to configure communication services in the AUTOSAR adaptive platform of the automotive open system architecture.
  • the method can be applied to vehicles, so that the communication management CM configuration can be more efficiently implemented in the AUTOSAR adaptive platform to apply corresponding communication services.
  • the method further includes: creating the network domain, and configuring mapping relationship information between the communication connector on the node and the network domain.
  • connection between the communication connector on the node and the network domain can be established, so that the mapping relationship between the service instance in the network domain and the target communication connector can be automatically created subsequently.
  • step S201 in FIG. 2 For the above process, refer to the relevant description in step S201 in FIG. 2 .
  • the method further includes: configuring a mapping relationship between the process and the node, and allocating corresponding software components to the process.
  • association relationship between the process and the software component can be determined, so that the mapping relationship between the service instance in the network domain and the target communication connector can be automatically created subsequently.
  • step S203 in FIG. 2 For the above process, refer to the relevant description in step S203 in FIG. 2 .
  • the method further includes: configuring a port prototype used by the process to communicate with another process in the network domain.
  • association relationship between the process and the port prototype can be determined, so that the mapping relationship between the service instance in the network domain and the target communication connector can be automatically created subsequently.
  • step S203 in FIG. 2 For the above process, refer to the relevant description in step S203 in FIG. 2 .
  • creating the network domain and configuring the mapping relationship information between the communication connector on the node and the network domain includes: determining the ID of the network domain; The mapping relationship information between the communication connector of the communication connector and the network domain, the mapping relationship information between the process and the node, create a service instance for the port prototype used by the process in the network domain, and create the The mapping relationship between the service instance and the target communication connector on the node includes: when the communication protocol of the service instance is DDS, determining that the network domain ID associated with the service instance is the ID.
  • the network domain ID can be associated with the service instance without manual setting, thereby simplifying the configuration process and improving configuration efficiency.
  • the ID of the network domain may be the above-mentioned network domain identifier, and the ID may be modified as required.
  • step S201 For a related example of creating a network domain, refer to the relevant description in step S201 in FIG. 2 .
  • step S204 For a relevant example of determining the network domain ID associated with the service instance, reference may be made to relevant descriptions in step S204.
  • each communication connector is associated with an Internet protocol IP address.
  • Fig. 6 shows a flowchart of a method for generating a mapping relationship according to an embodiment of the present application.
  • the mapping relationship information between the communication connector on the node and the network domain is used by the process in the network domain
  • the port prototype creates a service instance, and creates a mapping relationship between the service instance and the target communication connector on the node, including:
  • Step S601 according to the mapping relationship information between the communication connector on the node and the network domain, determine a first communication connector information set corresponding to the network domain, the first communication connector information set includes at least one of the nodes communication connector on the
  • Step S602 according to the mapping relationship information between the service instance and the software component port prototype, determine the second communication connector information set corresponding to the software component port prototype, the second communication connector information set includes at least one communication link on the target node Connector;
  • Step S603 Create a mapping relationship between the service instance and the target communication connector according to the first communication connector information set and the second communication connector information set.
  • mapping relationship between the service instance and the target communication connector can be established during the configuration process, and there is no need to The mapping relationship is manually established to realize the mapping from service instances to nodes, which simplifies the configuration process and improves efficiency.
  • step S601-step S603 refer to the related description in step S205 in FIG. 2, wherein the first communication connector information set may be, for example, the above-mentioned ListA, and the second communication connector information set may be, for example, the above-mentioned ListB.
  • Fig. 7 shows a flowchart of a method for generating a mapping relationship according to an embodiment of the present application. As shown in Figure 7, according to the first communication connector information set and the second communication connector information set, create the mapping relationship between the service instance and the target communication connector, including:
  • Step S701 determining the target communication connector according to the intersection of the first communication connector information set and the second communication connector information set;
  • Step S702 creating a mapping relationship between the service instance and the target communication connector.
  • 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 realizing the communication between the service instance and the target node, simplifying the configuration process and improving efficiency.
  • step S701-step S702 refer to the relevant description in step S205 in FIG. 2 .
  • the intersection of the first communication connector information set and the second communication connector information set is, for example, the intersection of ListA and ListB.
  • Fig. 8 shows a structural diagram of an apparatus for generating a mapping relationship according to an embodiment of the present application. As shown in Figure 8, the device includes:
  • the first acquiring module 801 is configured to acquire the mapping relationship information between the communication connector on the node and the network domain;
  • the second acquiring module 802 is configured to acquire mapping relationship information between a process and the node, the mapping relationship information 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 creation module 803 is configured to, according to the mapping relationship information between the communication connector on the node and the network domain, and the mapping relationship information between the process and the node, use the process in the network domain for the process Create a service instance of the port prototype, and create a mapping relationship between the service instance and the target communication connector on the node.
  • the communication management can be configured In the process of CM, the mapping relationship between the service instance created in the network domain and the target communication connector can be established without manual operation, so that the corresponding node can communicate with the service instance. There is no need to manually establish the mapping relationship, which simplifies the configuration process , improving the configuration efficiency.
  • the device is used to configure communication services in the AUTOSAR adaptive platform of the automotive open system architecture.
  • the device can be applied to vehicles, so that the communication management CM configuration can be more efficiently implemented in the AUTOSAR adaptive platform to apply corresponding communication services.
  • the device further includes: a first configuration module, configured to create the network domain, and configure mapping relationship information between the communication connector on the node and the network domain.
  • connection between the communication connector on the node and the network domain can be established, so that the mapping relationship between the service instance in the network domain and the target communication connector can be automatically created subsequently.
  • the apparatus further includes: a second configuration module, configured to configure a mapping relationship between the process and the node, and allocate corresponding software components to the process.
  • association relationship between the process and the software component can be determined, so that the mapping relationship between the service instance in the network domain and the target communication connector can be automatically created subsequently.
  • the device 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.
  • association relationship between the process and the port prototype can be determined, so that the mapping relationship between the service instance in the network domain and the target communication connector can be automatically created subsequently.
  • the first configuration module includes: determining the ID of the network domain; the creating module 803 includes: when the communication protocol of the service instance is the data distribution service DDS, determining The network domain ID associated with the service instance is the ID.
  • the network domain ID can be associated with the service instance without manual setting, thereby simplifying the configuration process and improving configuration efficiency.
  • each communication connector is associated with an Internet protocol IP address.
  • the creating module 803 includes: determining the first communication connector information set corresponding to the network domain according to the mapping relationship information between the communication connector on the node and the network domain,
  • the first communication connector information set includes at least one communication connector on the node; according to the mapping relationship information between the service instance and the software component port prototype, determine the second communication connector information set corresponding to the software component port prototype , the second communication connector information set includes at least one communication connector on the target node; according to the first communication connector information set and the second communication connector information set, create the service instance to communicate with the target Connector mapping relationship.
  • mapping relationship between the service instance and the target communication connector can be established during the configuration process, and there is no need to The mapping relationship is manually established to realize the mapping from service instances to nodes, which simplifies the configuration process and improves efficiency.
  • creating a mapping relationship between the service instance and the target communication connector according to the first communication connector information set and the second communication connector information set includes: according to the determine the target communication connector through the intersection of 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.
  • 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 realizing the communication between the service instance and the target node, simplifying the configuration process and improving efficiency.
  • FIG. 9 shows a structural diagram of an apparatus for generating a mapping relationship provided according to an embodiment of the present application.
  • the mapping relationship generating apparatus 1100 may be used to execute the mapping relationship generating method shown in any one of the foregoing FIGS. 2-7 .
  • the mapping relationship generation device may be a server, or a chip (system) or other components or components that may be arranged inside the server. This embodiment of the present application does not limit it.
  • an apparatus 1100 for generating a mapping relationship may include a processor 1101 and a transceiver 1102 .
  • the mapping relationship generation apparatus 1100 may include a memory 1103 .
  • the processor 1101 is coupled with the transceiver 1102 and the memory 1103, such as may be connected through a communication bus.
  • mapping relationship generating apparatus 1100 The components of the mapping relationship generating apparatus 1100 will be specifically introduced below in conjunction with FIG. 9 .
  • the above-mentioned processor 1101 is the control center of the mapping relation generating apparatus 1100, and may be one processor, or may be a general term for multiple processing elements.
  • the processor 1101 is one or more central processing units (central processing unit, CPU), may also be a specific integrated circuit (application specific integrated circuit, ASIC), or is configured to implement one or more An integrated circuit, for example: one or more microprocessors (digital signal processor, DSP), or, one or more field programmable gate arrays (field programmable gate array, FPGA).
  • the processor 1101 may execute various functions of the mapping relationship generating apparatus 1100 by running or executing a software program stored in the memory 1103 and calling data stored in the memory 1103 .
  • the processor 1101 may include one or more CPUs, such as CPU0 and CPU1 shown in FIG. 9 .
  • the mapping relationship generating apparatus 1100 may also include multiple processors, such as processor 1101 and processor 1104 shown in FIG. 9 .
  • processors can be a single-core processor (single-CPU) or a multi-core processor (multi-CPU).
  • a processor herein may refer to one or more communication devices, circuits, and/or processing cores for processing data (eg, computer program instructions).
  • the above-mentioned transceiver 1102 is used for communication with other servers.
  • the transceiver 1102 may include a receiver and a transmitter (not separately shown in FIG. 9 ). Wherein, the receiver is used to realize the receiving function, and the transmitter is used to realize the sending function.
  • the transceiver 1102 may be integrated with the processor 1101, or may exist independently, and be coupled to the processor 1101 through an input/output port (not shown in FIG. 9 ) of the mapping relationship generating device 1100.
  • the implementation of the present application Examples are not limited to this.
  • the above-mentioned memory 1103 can be used to store the software program that implements the solution of the present application, and the execution is controlled by the processor 1101.
  • the specific implementation can refer to the above-mentioned method embodiment, and details are not repeated here.
  • the memory 1103 can be a read-only memory (read-only memory, ROM) or other types of static storage communication devices that can store static information and instructions, or a random access memory (random access memory, RAM) that can store information and instructions
  • Other types of dynamic storage communication devices can also be electrically erasable programmable read-only memory (EEPROM), compact disc read-only memory (CD-ROM) or other optical discs Storage, optical disc storage (including compact discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage communication devices, or can be used to carry or store desired programs in the form of instructions or data structures code and any other medium that can be accessed by a computer, without limitation.
  • the memory 1103 can be integrated with the processor 1101, or can exist independently, and is coupled with the processor 1101 through the input/output port (not shown in FIG. 9 ) of the mapping relationship generation device 1100. Examples are not limited to this.
  • mapping relationship generating device 1100 shown in FIG. 9 does not constitute a limitation on the implementation of the mapping relationship generating device, and the actual mapping relationship generating device may include more or less than shown in the figure. components, or combinations of certain components, or different arrangements of components.
  • An embodiment of the present application provides an apparatus for generating a mapping relationship, including: a processor and a memory for storing instructions executable by the processor; wherein the processor is configured to implement the above method when executing the instructions.
  • Embodiments of the present application provide a terminal device, and the terminal device can execute the foregoing method.
  • An embodiment of the present application provides a non-volatile computer-readable storage medium, on which computer program instructions are stored, and when the computer program instructions are executed by a processor, the foregoing method is realized.
  • An embodiment of the present application provides a computer program product, including computer-readable codes, or a non-volatile computer-readable storage medium bearing computer-readable codes, when the computer-readable codes are stored in a processor of an electronic device When running in the electronic device, the processor in the electronic device executes the above method.
  • a computer readable storage medium may be a tangible device that can retain and store instructions for use by an instruction execution device.
  • a computer readable storage medium may be, for example, but is not limited to, an electrical storage device, a magnetic storage device, an optical storage device, an electromagnetic storage device, a semiconductor storage device, or any suitable combination of the foregoing.
  • Non-exhaustive list of computer-readable storage media include: portable computer disk, hard disk, random access memory (Random Access Memory, RAM), read only memory (Read Only Memory, ROM), erasable Electrically Programmable Read-Only-Memory (EPROM or flash memory), Static Random-Access Memory (Static Random-Access Memory, SRAM), Portable Compressed Disk Read-Only Memory (Compact Disc Read-Only Memory, CD -ROM), Digital Video Disc (DVD), memory sticks, floppy disks, mechanically encoded devices such as punched cards or raised structures in grooves with instructions stored thereon, and any suitable combination of the foregoing .
  • RAM Random Access Memory
  • ROM read only memory
  • EPROM or flash memory erasable Electrically Programmable Read-Only-Memory
  • Static Random-Access Memory SRAM
  • Portable Compressed Disk Read-Only Memory Compact Disc Read-Only Memory
  • CD -ROM Compact Disc Read-Only Memory
  • DVD Digital Video Disc
  • Computer readable program instructions or codes described herein may be downloaded from a computer readable storage medium to a respective computing/processing device, or downloaded to an external computer or external storage device over a network, such as the Internet, local area network, wide area network, and/or wireless network.
  • the network may include copper transmission cables, fiber optic transmission, wireless transmission, routers, firewalls, switches, gateway computers, and/or edge servers.
  • a network adapter card or a network interface in each computing/processing device receives 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 .
  • Computer program instructions for performing the operations of the present application may be assembly instructions, instruction set architecture (Instruction Set Architecture, ISA) instructions, machine instructions, machine-related instructions, microcode, firmware instructions, state setting data, or in one or more source or object code written in any combination of programming languages, including object-oriented programming languages—such as Smalltalk, C++, etc., and conventional procedural programming languages—such as the “C” language or similar programming languages.
  • Computer readable program instructions may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer, or entirely on the remote computer or server implement.
  • the remote computer can be connected to the user's computer through any kind of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or it can be connected to an external computer such as use an Internet service provider to connect via the Internet).
  • electronic circuits such as programmable logic circuits, field-programmable gate arrays (Field-Programmable Gate Array, FPGA) or programmable logic arrays (Programmable Logic Array, PLA), the electronic circuit can execute computer-readable program instructions, thereby realizing various aspects of the present application.
  • These computer-readable program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine such that when executed by the processor of the computer or other programmable data processing apparatus , producing an apparatus for realizing the functions/actions specified in one or more blocks in the flowchart and/or block diagram.
  • These computer-readable program instructions can also be stored in a computer-readable storage medium, and these instructions cause computers, programmable data processing devices and/or other devices to work in a specific way, so that the computer-readable medium storing instructions includes An article of manufacture comprising instructions for implementing various aspects of the functions/acts specified in one or more blocks in flowcharts and/or block diagrams.
  • each block in a flowchart or block diagram may represent a module, a portion of a program segment, or an instruction that includes one or more Executable instructions.
  • the functions noted in the block may occur out of the order noted in the figures. For example, two blocks in succession may, in fact, be executed substantially concurrently, or they may sometimes be executed in the reverse order, depending upon the functionality involved.
  • each block in the block diagrams and/or flowcharts, and combinations of blocks in the block diagrams and/or flowcharts can be implemented with hardware (such as circuits or ASIC (Application Specific Integrated Circuit, application-specific integrated circuit)), or can be implemented with a combination of hardware and software, such as firmware.
  • hardware such as circuits or ASIC (Application Specific Integrated Circuit, application-specific integrated circuit)
  • firmware such as firmware

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Computer And Data Communications (AREA)

Abstract

本申请涉及一种映射关系生成方法、装置和存储介质。该方法包括：获取节点上的通信连接器与网络域的映射关系信息；获取进程与所述节点之间的映射关系信息，所述进程与所述节点之间的映射关系信息包括所述进程对应的软件组件，所述软件组件包括至少一个端口原型；根据所述节点上的通信连接器与所述网络域的映射关系信息，所述进程与所述节点之间的映射关系信息，为所述进程在所述网络域中使用的端口原型创建服务实例，并创建所述服务实例与所述节点的目标通信连接器的映射关系。由此，无需针对每个实例一一手动建立映射关系，可以提高通信管理配置过程中的效率。

Description

一种映射关系生成方法、装置和存储介质 技术领域
本申请涉及智能汽车领域，尤其涉及一种映射关系生成方法、装置和存储介质。
背景技术
汽车开放系统架构(automotive open system architecture，AUTOSAR)是为降低汽车软件的开发风险而开发的一个开放的且形成事实标准化的软件架构。随着智能汽车的逐渐应用，集成了感知、规控、自动巡航等多种辅助功能的汽车，是典型的高新技术综合体，它的出现使得汽车越来越智能化和电子化，同时也使得汽车的软件结构越来越复杂。AUTOSAR在原有的经典平台(Classic Platform)上又推出了自适应平台(Adaptive Platform)。
其中，通信管理(communication management，CM)是AUTOSAR Adaptive Platform的重中之重，在配置CM的过程中，通常需要在将通信服务实例化之后，为其建立一系列的映射关系，当前通常是针对每个实例一一手动建立映射关系，比较繁琐，效率低下。
发明内容
有鉴于此，提出了一种映射关系生成方法、装置和存储介质。
第一方面，本申请的实施例提供了一种映射关系生成方法，该方法包括：获取节点上的通信连接器与网络域的映射关系信息；获取进程与所述节点之间的映射关系信息，所述进程与所述节点之间的映射关系信息包括所述进程对应的软件组件，所述软件组件包括至少一个端口原型；根据所述节点上的通信连接器与所述网络域的映射关系信息，所述进程与所述节点之间的映射关系信息，为所述进程在所述网络域中使用的端口原型创建服务实例，并创建所述服务实例与所述节点上的目标通信连接器的映射关系。
根据本申请实施例，通过为所述进程在所述网络域中使用的端口原型创建服务实例，以创建所述服务实例与所述节点上的目标通信连接器的映射关系，可以在配置通信管理CM的过程中，无需人工操作，即可将网络域中创建的服务实例与目标通信连接器建立映射关系，使得对应的节点可以与服务实例实现通信，无需手动建立该映射关系，简化了配置流程，提高了配置的效率。
根据第一方面，在所述映射关系生成方法的第一种可能的实现方式中，该方法还包括：创建所述网络域，并配置所述节点上的通信连接器与所述网络域的映射关系信息。
由此，可以建立节点上的通信连接器与网络域的连接，使得后续可以自动创建网络域中的服务实例与目标通信连接器的映射关系。
根据第一方面或第一方面的第一种可能的实现方式，在所述映射关系生成方法的第二种可能的实现方式中，该方法还包括：配置所述进程与所述节点之间的映射关系，并为所述进程分配对应的软件组件。
由此，可以确定进程与软件组件的关联关系，使得后续可以自动创建网络域中的服务实例与目标通信连接器的映射关系。
根据第一方面或第一方面的第一种或第二种可能的实现方式，在所述映射关系生成方法 的第三种可能的实现方式中，该方法还包括：配置所述进程与另一进程在所述网络域中通信使用的端口原型。
由此，可以确定进程与端口原型的关联关系，使得后续可以自动创建网络域中的服务实例与目标通信连接器的映射关系。
根据第一方面的第一种或第二种或第三种可能的实现方式，在所述映射关系生成方法的第四种可能的实现方式中，创建所述网络域，并配置所述节点上的通信连接器与所述网络域的映射关系信息，包括：确定所述网络域的ID；根据所述节点上的通信连接器与所述网络域的映射关系信息，所述进程与所述节点之间的映射关系信息，为所述进程在所述网络域中使用的端口原型创建服务实例，并创建所述服务实例节点上的与所述目标通信连接器的映射关系，包括：在所述服务实例的通信协议为数据分发服务DDS的情况下，确定所述服务实例关联的网络域ID为所述ID。
根据本申请实施例，通过确定网络域的ID，可以在通信协议为DDS的情况下，可以为服务实例关联网络域ID，无需人工设置，从而简化了配置过程，提高了配置的效率。
根据第一方面或第一方面的第一种或第二种或第三种或第四种可能的实现方式，在所述映射关系生成方法的第五种可能的实现方式中，每个通信连接器与一个网络互连协议IP地址相关联。
由此，使得节点可以通过通信连接器与其他配置的对象进行通信。
根据第一方面或第一方面的第一种或第二种或第三种或第四种或第五种可能的实现方式，在所述映射关系生成方法的第六种可能的实现方式中，根据所述节点上的通信连接器与所述网络域的映射关系信息，所述进程与所述节点之间的映射关系信息，为所述进程在所述网络域中使用的端口原型创建服务实例，并创建所述服务实例与所述节点上的目标通信连接器的映射关系，包括：根据所述节点上的通信连接器与所述网络域的映射关系信息，确定所述网络域对应的第一通信连接器信息集合，第一通信连接器信息集合包括至少一个所述节点上的通信连接器；根据所述服务实例和软件组件端口原型的映射关系信息，确定所述软件组件端口原型对应的第二通信连接器信息集合，第二通信连接器信息集合包括目标节点上的至少一个通信连接器；根据所述第一通信连接器信息集合和所述第二通信连接器信息集合，确定所述服务实例和所述目标通信连接器的映射关系。
根据本申请实施例，通过确定两个通信连接器信息集合以确定目标通信连接器，无需人工寻找目标通信连接器，可以在配置的过程中建立服务实例与目标通信连接器的映射关系，也无需人工建立该映射关系，从而实现服务实例至节点的映射，简化了配置流程，提高了效率。
根据第一方面的第六种可能的实现方式，在所述映射关系生成方法的第七种可能的实现方式中，根据所述第一通信连接器信息集合和所述第二通信连接器信息集合，创建所述服务实例与所述目标通信连接器的映射关系，包括：根据所述第一通信连接器信息集合和所述第二通信连接器信息集合的交集，确定所述目标通信连接器；创建所述服务实例与所述目标通信连接器的映射关系。
由此，可以无需人工查找服务实例对应的目标通信连接器，即可确定服务实例和目标通信连接器的映射关系，从而实现服务实例与目标节点的通信，简化了配置流程，提高了效率。
根据第一方面或第一方面的第一种或第二种或第三种或第四种或第五种或第六种或第七 种可能的实现方式，在所述映射关系生成方法的第八种可能的实现方式中，该方法用于配置汽车开放系统架构AUTOSAR自适应平台中的通信服务。
从而，使得本方法可以应用于车辆，使得在AUTOSAR自适应平台中可以更高效地实现通信管理CM配置，以应用对应的通信服务。
第二方面，本申请的实施例提供了一种映射关系生成装置，该装置包括：第一获取模块，用于获取节点上的通信连接器与网络域的映射关系信息；第二获取模块，用于获取进程与所述节点之间的映射关系信息，所述进程与所述节点之间的映射关系信息包括所述进程对应的软件组件，所述软件组件包括至少一个端口原型；创建模块，用于根据所述节点上的通信连接器与所述网络域的映射关系信息，所述进程与所述节点之间的映射关系信息，为所述进程在所述网络域中使用的端口原型创建服务实例，并创建所述服务实例与所述节点上的目标通信连接器的映射关系。
根据第二方面，在所述映射关系生成装置的第一种可能的实现方式中，该装置还包括：第一配置模块，用于创建所述网络域，并配置所述节点上的通信连接器与所述网络域的映射关系信息。
根据第二方面或第二方面的第一种可能的实现方式，在所述映射关系生成装置的第二种可能的实现方式中，该装置还包括：第二配置模块，用于配置所述进程与所述节点之间的映射关系，并为所述进程分配对应的软件组件。
根据第二方面或第二方面的第一种或第二种可能的实现方式，在所述映射关系生成装置的第三种可能的实现方式中，该装置还包括：第三配置模块，用于配置所述进程与另一进程在所述网络域中通信使用的端口原型。
根据第二方面的第一种或第二种或第三种可能的实现方式，在所述映射关系生成装置的第四种可能的实现方式中，该第一配置模块，包括：确定所述网络域的ID；该创建模块，包括：在所述服务实例的通信协议为数据分发服务DDS的情况下，确定所述服务实例关联的网络域ID为所述ID。
根据第二方面或第二方面的第一种或第二种或第三种或第四种可能的实现方式，在所述映射关系生成装置的第五种可能的实现方式中，每个通信连接器与一个网络互连协议IP地址相关联。
根据第二方面或第二方面的第一种或第二种或第三种或第四种或第五种可能的实现方式，在所述映射关系生成装置的第六种可能的实现方式中，该创建模块，包括：根据所述节点上的通信连接器与所述网络域的映射关系信息，确定所述网络域对应的第一通信连接器信息集合，第一通信连接器信息集合包括至少一个所述节点上的通信连接器；根据所述服务实例与软件组件端口原型的映射关系信息，确定所述软件组件端口原型对应的第二通信连接器信息集合，第二通信连接器信息集合包括目标节点上的至少一个通信连接器；根据所述第一通信连接器信息集合和所述第二通信连接器信息集合，创建所述服务实例与所述目标通信连接器的映射关系。
根据第二方面的第六种可能的实现方式，在所述映射关系生成装置的第七种可能的实现方式中，根据所述第一通信连接器信息集合和所述第二通信连接器信息集合，创建所述服务实例与所述目标通信连接器的映射关系，包括：根据所述第一通信连接器信息集合和所述第二通信连接器信息集合的交集，确定所述目标通信连接器；创建所述服务实例与所述目标通 信连接器的映射关系。
根据第二方面或第二方面的第一种或第二种或第三种或第四种或第五种或第六种或第七种可能的实现方式，在所述映射关系生成装置的第八种可能的实现方式中，该装置用于配置汽车开放系统架构AUTOSAR自适应平台中的通信服务。
第三方面，本申请的实施例提供了一种映射关系生成装置，该装置包括：处理器；用于存储处理器可执行指令的存储器；其中，所述处理器被配置为执行所述指令时实现上述第一方面或者第一方面的多种可能的实现方式中的一种或几种的映射关系生成方法。
第四方面，本申请的实施例提供了一种非易失性计算机可读存储介质，其上存储有计算机程序指令，所述计算机程序指令被处理器执行时实现上述第一方面或者第一方面的多种可能的实现方式中的一种或几种的映射关系生成方法。
第五方面，本申请的实施例提供了一种终端设备，该终端设备可以执行上述第一方面或者第一方面的多种可能的实现方式中的一种或几种的映射关系生成方法。
第六方面，本申请的实施例提供了一种计算机程序产品，包括计算机可读代码，或者承载有计算机可读代码的非易失性计算机可读存储介质，当所述计算机可读代码在电子设备中运行时，所述电子设备中的处理器执行上述第一方面或者第一方面的多种可能的实现方式中的一种或几种的映射关系生成方法。
本申请的这些和其他方面在以下(多个)实施例的描述中会更加简明易懂。
附图说明
包含在说明书中并且构成说明书的一部分的附图与说明书一起示出了本申请的示例性实施例、特征和方面，并且用于解释本申请的原理。
图1示出根据本申请一实施例的应用场景的示意图。
图2示出根据本申请一实施例的映射关系生成方法的流程图。
图3示出了根据本申请一实施例的创建网络域中的服务实例的示意图。
图4示出了根据本申请实施例的确定映射关系的示意图。
图5示出根据本申请一实施例的映射关系生成方法的流程图。
图6示出根据本申请一实施例的映射关系生成方法的流程图。
图7示出根据本申请一实施例的映射关系生成方法的流程图。
图8示出根据本申请一实施例的映射关系生成装置的结构图。
图9示出根据本申请一实施例的映射关系生成装置的结构图。
具体实施方式
以下将参考附图详细说明本申请的各种示例性实施例、特征和方面。附图中相同的附图标记表示功能相同或相似的元件。尽管在附图中示出了实施例的各种方面，但是除非特别指出，不必按比例绘制附图。
在这里专用的词“示例性”意为“用作例子、实施例或说明性”。这里作为“示例性”所说明的任何实施例不必解释为优于或好于其它实施例。
另外，为了更好的说明本申请，在下文的具体实施方式中给出了众多的具体细节。本领 域技术人员应当理解，没有某些具体细节，本申请同样可以实施。在一些实例中，对于本领域技术人员熟知的方法、手段、元件和电路未作详细描述，以便于凸显本申请的主旨。
图1示出根据本申请一实施例的应用场景的示意图。本申请的映射关系生成方法可用于在AUTOSAR自适应平台上配置通信管理的过程中。如图1所示，AUTOSAR自适应平台的架构可包括应用层、服务层和硬件层。应用层可包括用于实现应用功能的软件，如软件组件(software component，SWC)等；服务层可为应用层提供各种后台服务，如通信管理CM、用于提供数据结构定义服务的核心类型(core types)；硬件层可包括各节点，节点可以是内置于车辆上的车用芯片，如微控制单元(microcontroller unit，MCU)，也可以是包括MCU、车机等的域控制器。
在配置CM的过程中，通常需要在CM中将通信服务实例化，即确定服务实例(service instance)之后，为其建立一系列的映射关系，以实现建立服务实例与硬件层上的节点(可称为machine)的映射关系，从而使得应用层中的软件组件SWC能够应用服务实例对应的通信服务。在上述过程中，如果针对每个服务实例一一手动建立映射关系，过程将会十分繁琐。
鉴于此，本申请的映射关系生成方法中在网络域中创建服务实例，确定网络域与各节点上的通信连接器(connector)的映射关系(相当于建立了服务实例与节点的映射关系)，从而在配置CM的过程中可以建立一系列映射关系，最终无需人工操作即可实现服务实例与目标通信连接器的映射，提高了配置过程中的效率。
以下在图1示出的应用场景之下，通过图2-图7对本申请实施例的映射关系生成方法进行详细的介绍：
图2示出根据本申请一实施例的映射关系生成方法的流程图。如图2所示，该方法可用于处理器，该方法包括：
步骤S201，创建网络域。
可选地，网络域可以是虚拟的网络域。
在服务接口部署(service interface deployment)绑定的通信协议是数据分发服务(data distribution service，DDS)的情况下，还可以对于每个创建的网络域，生成一个对应的网络域的默认域标识(domain ID)。
步骤S202，配置节点。
在配置节点的过程中，可以包括：配置以太网集群(ethernet cluster)，在此过程中，可以定义以太网的网络配置，如IP地址、子网掩码等。
在配置好以太网集群的基础上，还可包括：配置节点设计(machine design)，在此过程中，可以定义节点上的以太网通信连接器(ethernet communication connector，即上文中的通信连接器)，实现节点与通信连接器的关联，节点上的每个通信连接器可以为其分配一个IP地址，用以实现节点与其他网络域、服务实例等的通信。对于不同的通信协议可以定义相对应的不同的通信连接器。还可以定义服务发现IP，从而在访问对应的服务时可以确定其I P地址。
在配置节点时可以引用配置好的节点设计的相关信息。
在配置好节点后，可以建立网络域与各节点上的通信连接器的映射关系。其中，网络域可以与多个节点建立映射关系，在此过程中，对于每个节点，可以选择节点上的一个通信连接器与该网络域建立映射关系。
步骤S203，配置应用(application)。
在配置应用的过程中，可以包括：配置软件组件类型，例如定义软件组件的对象和属性。还可以定义软件组件上用于请求服务或数据的接收端口原型(R-Port Prototype)，以及用于提供服务或数据的发送端口原型(P-Port Prototype)。
在配置好软件组件类型的基础上，还可包括：配置可执行程序(executable),在配置可执行程序时可以引用配置好的软件组件类型的相关信息，从而可以实现可执行程序与软件组件SWC的关联。
在配置好可执行程序的基础上，还可包括：配置进程设计(process design)，在配置进程设计时可以引用配置好的可执行程序的相关信息。
在配置好进程设计的基础上，还可包括：配置进程(process)，在配置进程是可以引用配置好的可执行程序的相关信息与进程设计的相关信息，从而可以实现进程与可执行程序的关联。
由此，可以实现软件组件(包括软件组件上的端口原型)、可执行程序、进程三者之间的关联关系。
在配置好应用以后，可以建立进程与节点的映射关系，并根据软件组件、可执行程序、进程三者之间的关联关系，得到进程与软件组件的映射关系，从而实现为进程分配对应的软件组件。
步骤S204，在网络域中创建服务实例。
其中，网络域可以是步骤S201中创建的网络域。
在一种可能的实现方式中，在创建服务实例的过程中，可以在配置好应用以后，为软件组件端口原型创建对应的服务实例(例如分别为P端口原型和R端口原型创建各自的服务实例)，从而建立软件组件端口原型和服务实例的映射关系。再根据上述进程与节点的映射关系，进而使得服务实例可以与配置好的节点关联。
在创建服务实例的过程中，可以引用配置好的服务接口部署的相关信息。
在绑定的通信协议为DDS的情况下，还可以自动关联网络域标识与服务实例，无需人工设置，避免重复配置。参见图3，图3示出了根据本申请一实施例的创建网络域中的服务实例的示意图。如图3所示，对于步骤S201中创建的一个网络域，可以默认一个网络域标识，例如为30(该网络域标识可修改)。在网络域中可以创建多个服务实例，如图中服务实例A、服务实例B、服务实例C和服务实例D。若绑定的通信协议为DDS，可以在该网络域中创建的各个服务实例的网络域标识(domain ID)属性都可以设置为该网络域的默认网络域标识，无需人工重复配置。例如可以将同一网络域内的服务实例A、B、C、D中网络域标识的属性设置为30。从而，可以实现服务实例中对应网络域标识的属性的配置。在网络域中创建服务实例时，服务实例的一些其他属性也可以自动配置，本申请对此不作限制。
步骤S205，确定服务实例与节点的映射关系。
确定服务实例与节点的映射关系，实际上是实现节点可以与服务实例的通信，因此实际上是确定服务实例与节点上的目标通信连接器的映射关系。可以通过下述的一种实现方式实现服务实例与目标通信连接器的映射关系。
参见图4，图4示出了根据本申请实施例的确定映射关系的示意图。如图4所示，图中的实线连接箭头可以表示连接的双方建立了映射关系。例如，网络域1与通信连接器B的连 接箭头可以指示网络域1与节点A上的通信连接器的映射关系，网络域1与通信连接器C的连接箭头可以指示网络域1与节点B上的通信连接器的映射关系。由此，根据网络域1与节点A和节点B上的通信连接器的映射关系，可以获得通信连接器的一个集合ListA，集合中包括通信连接器B和通信连接器C，分别对应于节点A和B上用于与网络域1连接的通信连接器。
图4中，P端口原型和R端口原型可以分别对应软件组件端口原型P-port Prototype和R-port Prototype，P端口原型和R端口原型与服务实例之间的连接箭头可以指示上述确定的服务实例与软件组件端口原型的映射关系。由于步骤S203中，确定了软件组件、可执行程序、进程三者之间的关联关系，通过获取进程与节点的映射关系，则可以实现软件组件、可执行程序、进程这三者与节点之间的关联关系。由此，可以通过服务实例(例如是服务实例A)与软件组件端口原型的映射关系，获取到服务实例A与软件组件A的一个P端口原型对应的软件组件的关联关系，从而可以获取到服务实例A与可执行程序A、进而与进程A的关联关系，最终确定与服务实例关联的节点A。由于节点A上存在至少一个通信连接器，因此可以获得另一个集合ListB，集合中包括与服务实例A关联的节点A上的两个通信连接器：通信连接器A和通信连接器B。
通过取ListA和ListB的交集，可以确定唯一的一个通信连接器作为目标通信连接器，即通信连接器B。从而可以确定服务实例A与通信连接器B的映射关系，可参见图4中服务实例A至通信连接器B的虚线连接箭头。对于其他的服务实例B、C、D，同理，可参见图4中对应的虚线连接箭头。
由此，可以查找到对应的目标通信连接器，建立服务实例与目标通信连接器的映射关系，完成CM的配置过程，在此过程中无需用户人工查找，对比，配置，提高了配置过程的效率。
可选地，步骤S201-步骤S205中的过程可以在可视化的界面上进行，例如以图形、表格等方式展示，用户可以在可视化界面上进行操作以修改配置的内容。以图4所示的图形为例，图4的初始图形中不存在现有的连接箭头，用户可在初始图形中建立连接箭头，从而确定对应二者映射关系，用户建立的连接箭头可参见图4中的实线连接箭头(如P端口原型至服务实例A的箭头)，在用户建立了图4中所示的实线连接箭头对应的映射关系后，将会根据上述方法确定服务实例与对应的目标通信连接器的映射关系(参见图4中的虚线连接箭头，这一步无需用户连接)。
可选地，CM配置完成后，可以以文字、图像、视频等可视化方式对CM的配置结果进行展示。例如可以将配置过程中配置的对象(如服务实例、节点等)属性、以及建立好的映射关系等以域视图(或分域CM通道视图等)的方式进行展示，在视图中可以展示对象及其属性，并以对象之间的连接线表示配置过程中建立好的映射关系。
需要说明的是，在一种可能的实现方式中，可以在步骤S201之前完成基础数据类型(data type)的定义、服务接口(service interface)的配置、以及服务接口部署的配置。
其中，定义基础数据类型的过程可利用核心类型(core types)中的服务实现，数据类型例如是整型(int)，浮点型(float)等。
其中，在配置服务接口的过程中可以定义服务所需的通信方式，对于每种通信方式，例如包括定义其中的事件(event)、方法(method)和字段(field)。还可以确定每种通信方式所需的数据类型(例如对应于上述基础数据类型)。
其中，在配置服务接口部署的过程中可以引用配置好的服务接口的相关信息，还可以将服务接口部署与对应的通信协议绑定。绑定的通信协议除上述DDS之外，还可以是基于IP的可扩展面向服务中间件(scalable service-oriented middleware over IP，SOME/IP)等通信协议。
需要说明的是，图2中示出的步骤的执行顺序并不是唯一的，本申请实施例的方案也可以以不同于图2标注的顺序执行。例如，步骤S205和步骤S204的执行顺序可以对调。
图5示出根据本申请一实施例的映射关系生成方法的流程图。该方法可用于处理器，如图5所示，该方法包括：
步骤S501，获取节点上的通信连接器与网络域的映射关系信息；
步骤S502，获取进程与所述节点之间的映射关系信息，所述进程与所述节点之间的映射关系信息包括所述进程对应的软件组件，所述软件组件包括至少一个端口原型；
步骤S503，根据所述节点上的通信连接器与所述网络域的映射关系信息，所述进程与所述节点之间的映射关系信息，为所述进程在所述网络域中使用的端口原型创建服务实例，并创建所述服务实例与所述节点上的目标通信连接器的映射关系。
根据本申请实施例，通过为所述进程在所述网络域中使用的端口原型创建服务实例，以创建所述服务实例与所述节点上的目标通信连接器的映射关系，可以在配置通信管理CM的过程中，无需人工操作，即可将网络域中创建的服务实例与目标通信连接器建立映射关系，使得对应的节点可以与服务实例实现通信，无需手动建立该映射关系，简化了配置流程，提高了配置的效率。
该网络域可以是虚拟域。至少一个端口原型可以是多组端口原型，每组端口原型可以包括接收端口原型和发送端口原型。
步骤S503中为所述进程在所述网络域中使用的端口原型创建服务实例的相关示例可参见图2中步骤S204中的相关叙述，需要说明的是，为进程在网络域中使用的端口原型创建服务实例，也可以是在创建服务实例后将该服务实例与对应的端口原型关联。步骤S501-步骤S503的示例可参见图2中步骤S205中的相关叙述。
在一种可能的实现方式中，该方法用于配置汽车开放系统架构AUTOSAR自适应平台中的通信服务。
从而，使得本方法可以应用于车辆，使得在AUTOSAR自适应平台中可以更高效地实现通信管理CM配置，以应用对应的通信服务。
AUTOSAR自适应平台的架构可参见图1。
在一种可能的实现方式中，该方法还包括：创建所述网络域，并配置所述节点上的通信连接器与所述网络域的映射关系信息。
由此，可以建立节点上的通信连接器与网络域的连接，使得后续可以自动创建网络域中的服务实例与目标通信连接器的映射关系。
上述过程可参见图2中步骤S201中的相关叙述。
在一种可能的实现方式中，该方法还包括：配置所述进程与所述节点之间的映射关系，并为所述进程分配对应的软件组件。
由此，可以确定进程与软件组件的关联关系，使得后续可以自动创建网络域中的服务实例与目标通信连接器的映射关系。
上述过程可参见图2中步骤S203中的相关叙述。
在一种可能的实现方式中，该方法还包括：配置所述进程与另一进程在所述网络域中通信使用的端口原型。
由此，可以确定进程与端口原型的关联关系，使得后续可以自动创建网络域中的服务实例与目标通信连接器的映射关系。
上述过程可参见图2中步骤S203中的相关叙述。
在一种可能的实现方式中，创建所述网络域，并配置所述节点上的通信连接器与所述网络域的映射关系信息，包括：确定所述网络域的ID；根据所述节点上的通信连接器与所述网络域的映射关系信息，所述进程与所述节点之间的映射关系信息，为所述进程在所述网络域中使用的端口原型创建服务实例，并创建所述服务实例与所述节点上的目标通信连接器的映射关系，包括：在所述服务实例的通信协议为数据分发服务DDS的情况下，确定所述服务实例关联的网络域ID为所述ID。
根据本申请实施例，通过确定网络域的ID，可以在通信协议为DDS的情况下，可以为服务实例关联网络域ID，无需人工设置，从而简化了配置过程，提高了配置的效率。
网络域的ID可以是上述网络域标识，该ID可以根据需要修改。
创建网络域的相关示例可参见图2中步骤S201中的相关叙述。确定服务实例关联的网络域ID的相关示例可参见步骤S204中的相关叙述。
在一种可能的实现方式中，每个通信连接器与一个网络互连协议IP地址相关联。
由此，使得节点可以通过通信连接器与其他配置的对象进行通信。
图6示出根据本申请一实施例的映射关系生成方法的流程图。如图6所示，根据所述节点上的通信连接器与所述网络域的映射关系信息，所述进程与所述节点之间的映射关系信息，为所述进程在所述网络域中使用的端口原型创建服务实例，并创建所述服务实例与所述节点上的目标通信连接器的映射关系，包括：
步骤S601，根据所述节点上的通信连接器与所述网络域的映射关系信息，确定所述网络域对应的第一通信连接器信息集合，第一通信连接器信息集合包括至少一个所述节点上的通信连接器；
步骤S602，根据所述服务实例与软件组件端口原型的映射关系信息，确定所述软件组件端口原型对应的第二通信连接器信息集合，第二通信连接器信息集合包括目标节点上的至少一个通信连接器；
步骤S603，根据所述第一通信连接器信息集合和所述第二通信连接器信息集合，创建所述服务实例与所述目标通信连接器的映射关系。
根据本申请实施例，通过确定两个通信连接器信息集合以确定目标通信连接器，无需人工寻找目标通信连接器，可以在配置的过程中建立服务实例与目标通信连接器的映射关系，也无需人工建立该映射关系，从而实现服务实例至节点的映射，简化了配置流程，提高了效率。
步骤S601-步骤S603的示例可参见图2中步骤S205中的相关叙述，其中，第一通信连接器信息集合可例如上述ListA，第二通信连接器信息集合可例如上述ListB。
图7示出根据本申请一实施例的映射关系生成方法的流程图。如图7所示，根据所述第一通信连接器信息集合和所述第二通信连接器信息集合，创建所述服务实例与所述目标通信 连接器的映射关系，包括：
步骤S701，根据所述第一通信连接器信息集合和所述第二通信连接器信息集合的交集，确定所述目标通信连接器；
步骤S702，创建所述服务实例与所述目标通信连接器的映射关系。
由此，可以无需人工查找服务实例对应的目标通信连接器，即可确定服务实例和目标通信连接器的映射关系，从而实现服务实例与目标节点的通信，简化了配置流程，提高了效率。
步骤S701-步骤S702的相关示例可参见图2中步骤S205中的相关叙述。第一通信连接器信息集合和第二通信连接器信息集合的交集，例如是上述ListA和ListB的交集。
图8示出根据本申请一实施例的映射关系生成装置的结构图。如图8所示，该装置包括：
第一获取模块801，用于获取节点上的通信连接器与网络域的映射关系信息；
第二获取模块802，用于获取进程与所述节点之间的映射关系信息，所述进程与所述节点之间的映射关系信息包括所述进程对应的软件组件，所述软件组件包括至少一个端口原型；
创建模块803，用于根据所述节点上的通信连接器与所述网络域的映射关系信息，所述进程与所述节点之间的映射关系信息，为所述进程在所述网络域中使用的端口原型创建服务实例，并创建所述服务实例与所述节点上的目标通信连接器的映射关系。
根据本申请实施例，通过为所述进程在所述网络域中使用的端口原型创建服务实例，以创建所述服务实例与所述节点上的目标通信连接器的映射关系，可以在配置通信管理CM的过程中，无需人工操作，即可将网络域中创建的服务实例与目标通信连接器建立映射关系，使得对应的节点可以与服务实例实现通信，无需手动建立该映射关系，简化了配置流程，提高了配置的效率。
在一种可能的实现方式中，该装置用于配置汽车开放系统架构AUTOSAR自适应平台中的通信服务。
从而，使得本装置可以应用于车辆，使得在AUTOSAR自适应平台中可以更高效地实现通信管理CM配置，以应用对应的通信服务。
在一种可能的实现方式中，该装置还包括：第一配置模块，用于创建所述网络域，并配置所述节点上的通信连接器与所述网络域的映射关系信息。
由此，可以建立节点上的通信连接器与网络域的连接，使得后续可以自动创建网络域中的服务实例与目标通信连接器的映射关系。
在一种可能的实现方式中，该装置还包括：第二配置模块，用于配置所述进程与所述节点之间的映射关系，并为所述进程分配对应的软件组件。
由此，可以确定进程与软件组件的关联关系，使得后续可以自动创建网络域中的服务实例与目标通信连接器的映射关系。
在一种可能的实现方式中，该装置还包括：第三配置模块，用于配置所述进程与另一进程在所述网络域中通信使用的端口原型。
由此，可以确定进程与端口原型的关联关系，使得后续可以自动创建网络域中的服务实例与目标通信连接器的映射关系。
在一种可能的实现方式中，该第一配置模块，包括：确定所述网络域的ID；该创建模块803，包括：在所述服务实例的通信协议为数据分发服务DDS的情况下，确定所述服务实例关联的网络域ID为所述ID。
根据本申请实施例，通过确定网络域的ID，可以在通信协议为DDS的情况下，可以为服务实例关联网络域ID，无需人工设置，从而简化了配置过程，提高了配置的效率。
在一种可能的实现方式中，每个通信连接器与一个网络互连协议IP地址相关联。
由此，使得节点可以通过通信连接器与其他配置的对象进行通信。
在一种可能的实现方式中，该创建模块803，包括：根据所述节点上的通信连接器与所述网络域的映射关系信息，确定所述网络域对应的第一通信连接器信息集合，第一通信连接器信息集合包括至少一个所述节点上的通信连接器；根据所述服务实例与软件组件端口原型的映射关系信息，确定所述软件组件端口原型对应的第二通信连接器信息集合，第二通信连接器信息集合包括目标节点上的至少一个通信连接器；根据所述第一通信连接器信息集合和所述第二通信连接器信息集合，创建所述服务实例与所述目标通信连接器的映射关系。
根据本申请实施例，通过确定两个通信连接器信息集合以确定目标通信连接器，无需人工寻找目标通信连接器，可以在配置的过程中建立服务实例与目标通信连接器的映射关系，也无需人工建立该映射关系，从而实现服务实例至节点的映射，简化了配置流程，提高了效率。
在一种可能的实现方式中，根据所述第一通信连接器信息集合和所述第二通信连接器信息集合，创建所述服务实例与所述目标通信连接器的映射关系，包括：根据所述第一通信连接器信息集合和所述第二通信连接器信息集合的交集，确定所述目标通信连接器；创建所述服务实例与所述目标通信连接器的映射关系。
由此，可以无需人工查找服务实例对应的目标通信连接器，即可确定服务实例和目标通信连接器的映射关系，从而实现服务实例与目标节点的通信，简化了配置流程，提高了效率。
图9示出根据本申请实施例提供的一种映射关系生成装置的结构图。该映射关系生成装置1100可用于执行上述图2-图7中任一项所示出的映射关系生成方法。例如，该映射关系生成装置可以是服务器，也可以是可设置于该服务器内部的芯片(系统)或其他部件或组件。本申请实施例对此不作限定。
如图9所示，映射关系生成装置1100可以包括处理器1101和收发器1102。可选地，映射关系生成装置1100可以包括存储器1103。其中，处理器1101与收发器1102和存储器1103耦合，如可以通过通信总线连接。
下面结合图9对映射关系生成装置1100的各个构成部件进行具体的介绍。
上述处理器1101是映射关系生成装置1100的控制中心，可以是一个处理器，也可以是多个处理元件的统称。例如，处理器1101是一个或多个中央处理器(central processing unit，CPU)，也可以是特定集成电路(application specific integrated circuit，ASIC)，或者是被配置成实施本申请实施例的一个或多个集成电路，例如：一个或多个微处理器(digital signal processor，DSP)，或，一个或者多个现场可编程门阵列(field programmable gate array，FPGA)。
可选地，处理器1101可以通过运行或执行存储在存储器1103内的软件程序，以及调用存储在存储器1103内的数据，执行映射关系生成装置1100的各种功能。
在具体的实现中，作为一种实施例，处理器1101可以包括一个或多个CPU，例如图9中所示出的CPU0和CPU1。
在一种可能的实现方式中，映射关系生成装置1100也可以包括多个处理器，例如图9中 所示的处理器1101和处理器1104。这些处理器中的每一个可以是一个单核处理器(single-CPU)，也可以是一个多核处理器(multi-CPU)。这里的处理器可以指一个或多个通信设备、电路、和/或用于处理数据(例如计算机程序指令)的处理核。
上述收发器1102，用于与其他服务器之间的通信。
可选地，收发器1102可以包括接收器和发送器(图9中未单独示出)。其中，接收器用于实现接收功能，发送器用于实现发送功能。
可选地，收发器1102可以和处理器1101集成在一起，也可以独立存在，并通过映射关系生成装置1100的输入/输出端口(图9中未示出)与处理器1101耦合，本申请实施例对此不作限定。
上述存储器1103可用于存储执行本申请方案的软件程序，并由处理器1101来控制执行，具体实现方式可以参考上述方法实施例，此处不再赘述。
其中，存储器1103可以是只读存储器(read-only memory，ROM)或可存储静态信息和指令的其他类型的静态存储通信设备，随机存取存储器(random access memory，RAM)或者可存储信息和指令的其他类型的动态存储通信设备，也可以是电可擦可编程只读存储器(electrically erasable programmable read-only memory，EEPROM)、只读光盘(compact disc read-only memory，CD-ROM)或其他光盘存储、光碟存储(包括压缩光碟、激光碟、光碟、数字通用光碟、蓝光光碟等)、磁盘存储介质或者其他磁存储通信设备、或者能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质，但不限于此。需要说明的是，存储器1103可以和处理器1101集成在一起，也可以独立存在，并通过映射关系生成装置1100的输入/输出端口(图9中未示出)与处理器1101耦合，本申请实施例对此不作限定。
需要说明的是，图9中所示出的映射关系生成装置1100的结构并不构成对映射关系生成装置的实现方式的限定，实际的映射关系生成装置可以包括比图示更多或更少的部件，或者组合某些部件，或者不同的部件布置。
本申请的实施例提供了一种映射关系生成装置，包括：处理器以及用于存储处理器可执行指令的存储器；其中，所述处理器被配置为执行所述指令时实现上述方法。
本申请的实施例提供了一种终端设备，该终端设备可以执行上述方法。
本申请的实施例提供了一种非易失性计算机可读存储介质，其上存储有计算机程序指令，所述计算机程序指令被处理器执行时实现上述方法。
本申请的实施例提供了一种计算机程序产品，包括计算机可读代码，或者承载有计算机可读代码的非易失性计算机可读存储介质，当所述计算机可读代码在电子设备的处理器中运行时，所述电子设备中的处理器执行上述方法。
计算机可读存储介质可以是可以保持和存储由指令执行设备使用的指令的有形设备。计算机可读存储介质例如可以是――但不限于――电存储设备、磁存储设备、光存储设备、电磁存储设备、半导体存储设备或者上述的任意合适的组合。计算机可读存储介质的更具体的例子(非穷举的列表)包括：便携式计算机盘、硬盘、随机存取存储器(Random Access Memory，RAM)、只读存储器(Read Only Memory，ROM)、可擦式可编程只读存储器(Electrically Programmable Read-Only-Memory，EPROM或闪存)、静态随机存取存储器(Static Random-Access Memory，SRAM)、便携式压缩盘只读存储器(Compact Disc Read-Only Memory， CD-ROM)、数字多功能盘(Digital Video Disc，DVD)、记忆棒、软盘、机械编码设备、例如其上存储有指令的打孔卡或凹槽内凸起结构、以及上述的任意合适的组合。
这里所描述的计算机可读程序指令或代码可以从计算机可读存储介质下载到各个计算/处理设备，或者通过网络、例如因特网、局域网、广域网和/或无线网下载到外部计算机或外部存储设备。网络可以包括铜传输电缆、光纤传输、无线传输、路由器、防火墙、交换机、网关计算机和/或边缘服务器。每个计算/处理设备中的网络适配卡或者网络接口从网络接收计算机可读程序指令，并转发该计算机可读程序指令，以供存储在各个计算/处理设备中的计算机可读存储介质中。
用于执行本申请操作的计算机程序指令可以是汇编指令、指令集架构(Instruction Set Architecture，ISA)指令、机器指令、机器相关指令、微代码、固件指令、状态设置数据、或者以一种或多种编程语言的任意组合编写的源代码或目标代码，所述编程语言包括面向对象的编程语言—诸如Smalltalk、C++等，以及常规的过程式编程语言—诸如“C”语言或类似的编程语言。计算机可读程序指令可以完全地在用户计算机上执行、部分地在用户计算机上执行、作为一个独立的软件包执行、部分在用户计算机上部分在远程计算机上执行、或者完全在远程计算机或服务器上执行。在涉及远程计算机的情形中，远程计算机可以通过任意种类的网络—包括局域网(Local Area Network，LAN)或广域网(Wide Area Network，WAN)—连接到用户计算机，或者，可以连接到外部计算机(例如利用因特网服务提供商来通过因特网连接)。在一些实施例中，通过利用计算机可读程序指令的状态信息来个性化定制电子电路，例如可编程逻辑电路、现场可编程门阵列(Field-Programmable Gate Array，FPGA)或可编程逻辑阵列(Programmable Logic Array，PLA)，该电子电路可以执行计算机可读程序指令，从而实现本申请的各个方面。
这里参照根据本申请实施例的方法、装置(系统)和计算机程序产品的流程图和/或框图描述了本申请的各个方面。应当理解，流程图和/或框图的每个方框以及流程图和/或框图中各方框的组合，都可以由计算机可读程序指令实现。
这些计算机可读程序指令可以提供给通用计算机、专用计算机或其它可编程数据处理装置的处理器，从而生产出一种机器，使得这些指令在通过计算机或其它可编程数据处理装置的处理器执行时，产生了实现流程图和/或框图中的一个或多个方框中规定的功能/动作的装置。也可以把这些计算机可读程序指令存储在计算机可读存储介质中，这些指令使得计算机、可编程数据处理装置和/或其他设备以特定方式工作，从而，存储有指令的计算机可读介质则包括一个制造品，其包括实现流程图和/或框图中的一个或多个方框中规定的功能/动作的各个方面的指令。
也可以把计算机可读程序指令加载到计算机、其它可编程数据处理装置、或其它设备上，使得在计算机、其它可编程数据处理装置或其它设备上执行一系列操作步骤，以产生计算机实现的过程，从而使得在计算机、其它可编程数据处理装置、或其它设备上执行的指令实现流程图和/或框图中的一个或多个方框中规定的功能/动作。
附图中的流程图和框图显示了根据本申请的多个实施例的装置、系统、方法和计算机程序产品的可能实现的体系架构、功能和操作。在这点上，流程图或框图中的每个方框可以代表一个模块、程序段或指令的一部分，所述模块、程序段或指令的一部分包含一个或多个用于实现规定的逻辑功能的可执行指令。在有些作为替换的实现中，方框中所标注的功能也可 以以不同于附图中所标注的顺序发生。例如，两个连续的方框实际上可以基本并行地执行，它们有时也可以按相反的顺序执行，这依所涉及的功能而定。
也要注意的是，框图和/或流程图中的每个方框、以及框图和/或流程图中的方框的组合，可以用执行相应的功能或动作的硬件(例如电路或ASIC(Application Specific Integrated Circuit，专用集成电路))来实现，或者可以用硬件和软件的组合，如固件等来实现。
尽管在此结合各实施例对本发明进行了描述，然而，在实施所要求保护的本发明过程中，本领域技术人员通过查看所述附图、公开内容、以及所附权利要求书，可理解并实现所述公开实施例的其它变化。在权利要求中，“包括”(comprising)一词不排除其他组成部分或步骤，“一”或“一个”不排除多个的情况。单个处理器或其它单元可以实现权利要求中列举的若干项功能。相互不同的从属权利要求中记载了某些措施，但这并不表示这些措施不能组合起来产生良好的效果。
以上已经描述了本申请的各实施例，上述说明是示例性的，并非穷尽性的，并且也不限于所披露的各实施例。在不偏离所说明的各实施例的范围的情况下，对于本技术领域的普通技术人员来说许多修改和变更都是显而易见的。本文中所用术语的选择，旨在最好地解释各实施例的原理、实际应用或对市场中的技术的改进，或者使本技术领域的其它普通技术人员能理解本文披露的各实施例。

Claims (13)

  1. 一种映射关系生成方法，其特征在于，所述方法包括：
    获取节点上的通信连接器与网络域的映射关系信息；
    获取进程与所述节点之间的映射关系信息，所述进程与所述节点之间的映射关系信息包括所述进程对应的软件组件，所述软件组件包括至少一个端口原型；
    根据所述节点上的通信连接器与所述网络域的映射关系信息，所述进程与所述节点之间的映射关系信息，为所述进程在所述网络域中使用的端口原型创建服务实例，并创建所述服务实例与所述节点上的目标通信连接器的映射关系。
  2. 根据权利要求1所述的方法，其特征在于，所述方法还包括：
    创建所述网络域，并配置所述节点上的通信连接器与所述网络域的映射关系信息。
  3. 根据权利要求1或2所述的方法，其特征在于，所述方法还包括：
    配置所述进程与所述节点之间的映射关系，并为所述进程分配对应的软件组件。
  4. 根据权利要求1-3任一项所述的方法，其特征在于，所述方法还包括：
    配置所述进程与另一进程在所述网络域中通信使用的端口原型。
  5. 根据权利要求2-4任一项所述的方法，其特征在于，创建所述网络域，并配置所述节点上的通信连接器与所述网络域的映射关系信息，包括：
    确定所述网络域的ID；
    根据所述节点上的通信连接器与所述网络域的映射关系信息，所述进程与所述节点之间的映射关系信息，为所述进程在所述网络域中使用的端口原型创建服务实例，并创建所述服务实例与所述节点的目标通信连接器的映射关系，包括：
    在所述服务实例的通信协议为数据分发服务DDS的情况下，确定所述服务实例关联的网络域ID为所述ID。
  6. 根据权利要求1-5任一项所述的方法，其特征在于，每个通信连接器与一个网络互连协议IP地址相关联。
  7. 根据权利要求1-6任意一项所述的方法，其特征在于，根据所述节点上的通信连接器与所述网络域的映射关系信息，所述进程与所述节点之间的映射关系信息，为所述进程在所述网络域中使用的端口原型创建服务实例，并创建所述服务实例与所述节点的目标通信连接器的映射关系，包括：
    根据所述节点上的通信连接器与所述网络域的映射关系信息，确定所述网络域对应的第一通信连接器信息集合，第一通信连接器信息集合包括至少一个所述节点上的通信连接器；
    根据所述服务实例与软件组件端口原型的映射关系信息，确定所述软件组件端口原型对应的第二通信连接器信息集合，第二通信连接器信息集合包括目标节点上的至少一个通信连接器；
    根据所述第一通信连接器信息集合和所述第二通信连接器信息集合，创建所述服务实例和所述目标通信连接器的映射关系。
  8. 根据权利要求7所述的方法，其特征在于，根据所述第一通信连接器信息集合和所述第二通信连接器信息集合，创建所述服务实例和所述目标通信连接器的映射关系，包括：
    根据所述第一通信连接器信息集合和所述第二通信连接器信息集合的交集，确定所述目标通信连接器；
    创建所述服务实例和所述目标通信连接器的映射关系。
  9. 根据权利要求1-8任意一项所述的方法，其特征在于，所述方法用于配置汽车开放系统架构AUTOSAR自适应平台中的通信服务。
  10. 一种映射关系生成装置，其特征在于，所述装置包括：
    第一获取模块，用于获取节点上的通信连接器与网络域的映射关系信息；
    第二获取模块，用于获取进程与所述节点之间的映射关系信息，所述进程与所述节点之间的映射关系信息包括所述进程对应的软件组件，所述软件组件包括至少一个端口原型；
    创建模块，用于根据所述节点上的通信连接器与所述网络域的映射关系信息，所述进程与所述节点之间的映射关系信息，为所述进程在所述网络域中使用的端口原型创建服务实例，并创建所述服务实例与所述节点的目标通信连接器的映射关系。
  11. 一种映射关系生成装置，其特征在于，包括：
    处理器；
    用于存储处理器可执行指令的存储器；
    其中，所述处理器被配置为执行所述指令时实现权利要求1-9任意一项所述的方法。
  12. 一种非易失性计算机可读存储介质，其上存储有计算机程序指令，其特征在于，所述计算机程序指令被处理器执行时实现权利要求1-9中任意一项所述的方法。
  13. 一种计算机程序产品，包括计算机可读代码，或者承载有计算机可读代码的非易失性计算机可读存储介质，当所述计算机可读代码在电子设备中运行时，所述电子设备中的处理 器执行权利要求1-9中任意一项所述的方法。
PCT/CN2021/125308 2021-10-21 2021-10-21 一种映射关系生成方法、装置和存储介质 WO2023065218A1 (zh)

Priority Applications (4)

Application Number Priority Date Filing Date Title
EP21960968.2A EP4407447A1 (en) 2021-10-21 2021-10-21 Mapping relationship generation method and apparatus and storage medium
CN202180007810.8A CN116324721A (zh) 2021-10-21 2021-10-21 一种映射关系生成方法、装置和存储介质
PCT/CN2021/125308 WO2023065218A1 (zh) 2021-10-21 2021-10-21 一种映射关系生成方法、装置和存储介质
US18/641,758 US20240275688A1 (en) 2021-10-21 2024-04-22 Mapping Relationship Generation Method and Apparatus, and Storage Medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2021/125308 WO2023065218A1 (zh) 2021-10-21 2021-10-21 一种映射关系生成方法、装置和存储介质

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US18/641,758 Continuation US20240275688A1 (en) 2021-10-21 2024-04-22 Mapping Relationship Generation Method and Apparatus, and Storage Medium

Publications (1)

Publication Number Publication Date
WO2023065218A1 true WO2023065218A1 (zh) 2023-04-27

Family

ID=86058674

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/125308 WO2023065218A1 (zh) 2021-10-21 2021-10-21 一种映射关系生成方法、装置和存储介质

Country Status (4)

Country Link
US (1) US20240275688A1 (zh)
EP (1) EP4407447A1 (zh)
CN (1) CN116324721A (zh)
WO (1) WO2023065218A1 (zh)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102231107A (zh) * 2011-06-09 2011-11-02 浙江大学 基于autosar的电控单元通信数据格式的自动生成方法
US20130124703A1 (en) * 2011-11-11 2013-05-16 Electronics And Telecommunications Research Institute Method and apparatus for setting up gateway for autosar-based vehicle network
KR101628694B1 (ko) * 2014-12-15 2016-06-10 현대오트론 주식회사 오토사 기반 ｅｃｕ의 소프트웨어 컴포넌트에 대한 플랫뷰 생성 방법
WO2021107179A1 (ko) * 2019-11-27 2021-06-03 주식회사 알티스트 Autosar 기반 응용 소프트웨어의 설정 코드 자동 생성 방법 및 장치

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102231107A (zh) * 2011-06-09 2011-11-02 浙江大学 基于autosar的电控单元通信数据格式的自动生成方法
US20130124703A1 (en) * 2011-11-11 2013-05-16 Electronics And Telecommunications Research Institute Method and apparatus for setting up gateway for autosar-based vehicle network
KR101628694B1 (ko) * 2014-12-15 2016-06-10 현대오트론 주식회사 오토사 기반 ｅｃｕ의 소프트웨어 컴포넌트에 대한 플랫뷰 생성 방법
WO2021107179A1 (ko) * 2019-11-27 2021-06-03 주식회사 알티스트 Autosar 기반 응용 소프트웨어의 설정 코드 자동 생성 방법 및 장치

Also Published As

Publication number Publication date
CN116324721A (zh) 2023-06-23
US20240275688A1 (en) 2024-08-15
EP4407447A1 (en) 2024-07-31

Similar Documents

Publication Publication Date Title
CN104219127B (zh) 一种虚拟网络实例的创建方法以及设备
WO2019042110A1 (zh) 一种订阅发布方法及服务器
US11907749B2 (en) RDMA with virtual address space
CN111857873A (zh) 一种实现云原生容器网络的方法
US11177974B2 (en) Consistent provision of member node group information on virtual overlay network
KR20170073605A (ko) 합성 파티션 함수 제공 기법
US10516544B2 (en) Extranet connectivity in LISP networks
US20160149846A1 (en) Publish/subscribe messaging using message structure
JP7451556B2 (ja) ネットワークに基づいたメディア処理（ｎｂｍｐ）におけるメディア処理機能のための構成パラメータのグラフ表現及び記述
CN113079207A (zh) 一种实现端口或网络高可用的方法、系统、终端及介质
CN114157633A (zh) 一种报文转发方法及装置
US10785056B1 (en) Sharing a subnet of a logically isolated network between client accounts of a provider network
CN111064786A (zh) 账户标识管理方法及设备
WO2023065218A1 (zh) 一种映射关系生成方法、装置和存储介质
CN115865921A (zh) 一种构建容器网络的方法、系统、存储介质、电子设备
WO2023283286A1 (en) Enabling vertical application layer server for peer-to-peer media parameter negotiation
CN115550377A (zh) 一种nvmf存储集群节点互联方法、装置、设备及介质
CN113454966B (zh) 一种影子设备的生成方法、设备及存储介质
CN111294221A (zh) 一种基于haproxy的网络隔离配置方法及其装置
CN113691575A (zh) 通信方法、装置及系统
WO2023201558A1 (zh) 一种映射关系生成方法、装置和存储介质
US11522831B1 (en) Increasing edge device address space while complying with a radio communication protocol
WO2023138032A1 (zh) 一种地址空间推荐方法、装置及相关设备
CN114979079B (zh) 信息处理方法、装置、相关设备和存储介质
WO2023212933A1 (zh) 标识配置方法及装置、电子设备及存储介质

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 21960968

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2024523777

Country of ref document: JP

Kind code of ref document: A

WWE Wipo information: entry into national phase

Ref document number: 2021960968

Country of ref document: EP

ENP Entry into the national phase

Ref document number: 2021960968

Country of ref document: EP

Effective date: 20240423

NENP Non-entry into the national phase

Ref country code: DE