WO2023070426A1 - 一种配置方法和装置 - Google Patents

一种配置方法和装置 Download PDF

Info

Publication number
WO2023070426A1
WO2023070426A1 PCT/CN2021/126979 CN2021126979W WO2023070426A1 WO 2023070426 A1 WO2023070426 A1 WO 2023070426A1 CN 2021126979 W CN2021126979 W CN 2021126979W WO 2023070426 A1 WO2023070426 A1 WO 2023070426A1
Authority
WO
WIPO (PCT)
Prior art keywords
service
processes
service instance
instance
preconfigured
Prior art date
Application number
PCT/CN2021/126979
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 PCT/CN2021/126979 priority Critical patent/WO2023070426A1/zh
Publication of WO2023070426A1 publication Critical patent/WO2023070426A1/zh

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/60—Software deployment

Definitions

  • the present application relates to the field of smart cars, and more specifically, to a configuration method and device.
  • the automotive electronic network is developing in the direction of multi-bus hybrid network interconnection.
  • the automotive field launched an open and standardized automotive embedded system software architecture (auto motive open system architecture, AUTOSAR) specification.
  • AUTOSAR autonomous open system architecture
  • the present application provides a configuration method and device, which help to simplify the communication management configuration process, thereby helping to improve configuration efficiency.
  • a configuration method includes: configuring n processes, n ⁇ 1 and n is an integer; mapping m processes in the n processes to the first component, 0 ⁇ m ⁇ n and m is an integer, and the first component is associated with the first port; according to the pre-configured association relationship, an association relationship between each of the m service instances corresponding to the m processes and the first port is generated.
  • the association relationship between each service instance and the first port can be generated, and the user does not need to manually configure the association relationship, which helps to simplify the communication management configuration process, thereby helping to improve configuration efficiency .
  • the preconfigured association includes reference information of processes, ports, and service instances, and correspondence among processes, ports, and service instances.
  • the preconfigured association relationship may include reference information of processes, ports and service instances and the corresponding relationship between processes, ports and service instances, so that processes, ports and service instances can be linked through reference information and corresponding relationships Instances are associated to help simplify the communication management configuration process, thereby helping to improve configuration efficiency.
  • the reference information of the process may be a process number.
  • the reference information of the port may be a port number.
  • the reference information of the service instance may be attribute information in the service instance, and the attribute information may include one or more of short name (short name) and deployment information (deployment).
  • the method before generating the association relationship between each of the m service instances corresponding to the m processes and the first port, the method further includes: according to the preset Configured service instances, generating the m service instances and configuring attribute information of each service instance in the m service instances.
  • the corresponding service instance can be generated through the pre-configured service instance, and the user does not need to manually configure the service instance and its attribute information, which helps to simplify the communication management configuration process, thereby helping to improve configuration efficiency.
  • the mapping m processes of the n processes to the first component includes: mapping the m processes to the first executable program exe, the The root component of the first executable program exe is the first composite component; a first sub-element of the first composite component is created, and the type of the first sub-element points to the first component.
  • m processes among n processes can be mapped to the first component through the first compound component, so that the mapping of multiple processes to the first component can be realized.
  • the n is greater than or equal to 2 and the n processes are processes of the receiving end.
  • the configuration method of the embodiment of the present application can be applied to the scenario of one send and multiple reception (that is, one sender communicates with multiple receivers) in CM configuration.
  • service instances of multiple receivers can be generated and configured
  • the attribute information of each service instance; and/or, through the pre-configured association relationship, the association relationship between each service instance and the first port in multiple service instances at the receiving end can be generated, without manual configuration by the user, which helps to simplify a
  • the configuration process of communication management in the scenario of multiple sending and receiving which helps to improve configuration efficiency.
  • n and m are equal.
  • n processes can be mapped to the first component, so that when generating service instances at the receiving end, n service instances at the receiving end can be generated according to the pre-configured service instances, so that all service instances at the receiving end can be Generated by pre-configured service instances, users do not need to manually create service instances and configure their attribute information, which helps to simplify the communication management configuration process in the one-send-multiple-receive scenario, thereby helping to improve configuration efficiency.
  • the preconfigured service instance includes a first preconfigured service instance and a second preconfigured service instance, and the first preconfigured service instance is for the The service instance of the Internet protocol extensible service-oriented middleware SOME/IP communication, the second preconfigured service instance is a service instance for the data distribution service DDS communication.
  • different service instance templates can be configured in advance for service instances in different communication modes, so that when generating service instances, service instances can be generated and their attribute information configured according to different service instance templates, which is helpful To improve configuration flexibility.
  • the attribute information of each service instance includes identification information of the service instance, transmission plug-in information, deployment information, quality of service configuration information, and end-to-end communication protection information one or more of.
  • a configuration device which includes: a configuration unit configured to configure n processes, where n ⁇ 1 and n is an integer; a mapping unit configured to map m processes in the n processes to The first component, where 0 ⁇ m ⁇ n and m is an integer, the first component is associated with the first port; the generating unit is configured to generate each of the m service instances corresponding to the m processes according to the pre-configured association relationship The association relationship between the instance and the first port.
  • the preconfigured association includes reference information of processes, ports, and service instances, and the correspondence between processes, ports, and service instances.
  • the generating unit is further configured to, before generating the association relationship between each service instance and the first port among the m service instances corresponding to the m processes, According to the pre-configured service instances, generate the m service instances and configure attribute information of each service instance in the m service instances.
  • the mapping unit is specifically configured to: map the m processes to the first executable program exe, and the root component of the first executable program exe is the first Composite component; create the first sub-element of the first composite component, and the type of the first sub-element points to the first component.
  • the n is greater than or equal to 2 and the n processes are processes of the receiving end.
  • the preconfigured service instance includes a first preconfigured service instance and a second preconfigured service instance
  • the first preconfigured service instance is for the The service instance of the Internet protocol extensible service-oriented middleware SOME/IP communication
  • the second preconfigured service instance is a service instance for the data distribution service DDS communication.
  • the attribute information of each service instance includes identification information of the service instance, transmission plug-in information, deployment information, quality of service configuration information, and end-to-end communication protection information one or more of.
  • a configuration device which includes: a memory for storing computer instructions; a processor for executing the computer instructions stored in the memory, so that the device executes the method in the first aspect above.
  • a terminal device in a fourth aspect, includes the apparatus described in any one of the second aspect or the third aspect above.
  • a computer program product comprising: computer program code, when the computer program code is run on a computer, the computer is made to execute the method in the above first aspect.
  • a computer-readable medium stores program codes, and when the computer program codes are run on a computer, the computer is made to execute the method in the above-mentioned first aspect.
  • an embodiment of the present application provides a chip system, the chip system includes a processor, configured to call a computer program or a computer instruction stored in a memory, so that the processor executes the method described in any one of the above aspects.
  • the processor is coupled to the memory through an interface.
  • the system on a chip further includes a memory, where computer programs or computer instructions are stored in the memory.
  • Figure 1 is a schematic diagram of the software architecture of an adaptive automotive embedded system.
  • Fig. 2 is a schematic diagram of a scenario of one send and multiple reception.
  • Figure 3 is the organizational form when a process communicates with multiple processes.
  • Figure 4 is another organizational form when one process communicates with multiple processes.
  • Fig. 5 is a schematic diagram of generating a service instance and associating the service instance with a port.
  • Fig. 6 is another schematic diagram of generating a service instance and associating the service instance with a port.
  • FIG. 7 is a schematic flowchart of a configuration method provided by an embodiment of the present application.
  • Fig. 8 is another schematic flowchart of the configuration method provided by the embodiment of the present application.
  • Fig. 9 is a schematic flow block diagram of a configuration device provided by an embodiment of the present application.
  • Fig. 10 is a schematic flow block diagram of a configuration device provided by an embodiment of the present application.
  • FIG. 1 is a schematic diagram of the software architecture of an adaptive automotive embedded system.
  • the software architecture can be divided into application layer, operation layer, basic service layer and hardware layer.
  • the basic server layer includes communication management (communication management, CM), network management (network management), state management (state management), update configuration management (update configuration management), encryption service (cryptography), time synchronization (time synchronization) ), diagnostics, storage services (persistency) and execution management (execution management), etc.
  • CM is a key step in AP configuration, which determines the software architecture of the entire system and the collaborative relationship between software. In the CM configuration, multiple elements need to be created, attribute configured, and referenced.
  • CM can be configured on this basis.
  • An important step of CM is communication instantiation, which is to create a pair of service instances for communication connection.
  • the elements to be created in this process include: process (process), executable program (executable, exe), instance (instance), adaptive application component (AdaptiveApplicationSwComponentType, swc), composite component (CompositionSwComponentType) and so on.
  • the attribute configuration that needs to be completed includes: instance ID (instance ID), transport plug-in information (Transport plugin), deployment information (deployment), service quality configuration information (Qos profile), and end-to-end communication protection information (E2EprofileConfiguration ).
  • the reference associations that need to be completed include: the association between process and exe, the association between exe and swc, and the association between instance and port (instance to port mapping).
  • Fig. 2 shows a schematic diagram of a send-multiple-receive scenario.
  • the number of sender service instance (provider service instance) is 1, and its corresponding receiver service instance (required service instance) has multiple.
  • This scenario will cause the service instance on the receiving end to need to be reconfigured multiple times.
  • Figure 3 and Figure 4 respectively show the organizational forms when one process communicates with multiple processes.
  • each exe has its own swc, for example, exe1 corresponds to swc1, and exe2 corresponds to swc2.
  • exe1 corresponds to swc1
  • exe2 corresponds to swc2.
  • Figure 4 for a swc with the same function, multiple exes can share this swc through a composite component, for example, exe1 and exe2 share swc1 through a composite swc.
  • FIG. 5 shows the process of generating a service instance and associating the service instance with a port for the organization form shown in FIG. 3 .
  • FIG. 6 shows the process of generating a service instance and associating the service instance with a port for the organization form shown in FIG. 4 . It can be seen that for the two organizational forms shown in Figure 3 and Figure 4, the communication instantiation is the same.
  • the configuration method and device provided in the embodiments of the present application can complete the setting of elements, attributes, and association relationships in advance to form a template.
  • the required elements, attributes and associations can be automatically generated according to the template, thus eliminating the complicated manual configuration process and helping to improve the efficiency of CM configuration.
  • the set templates are classified according to different communication methods.
  • different templates may be set for Internet protocol-based scalable service-oriented middleware (scalable service-Oriented middleware over IP, SOME/IP) communication and data distribution service (data distribution service, DDS) communication.
  • scalable service-oriented middleware scalable service-Oriented middleware over IP, SOME/IP
  • data distribution service data distribution service
  • Table 1 shows a template of a service instance set for DDS communication.
  • values of the three attributes of Category, Checksum, and Timestamp may be empty, or may be set to corresponding values.
  • an empty value is used as an example.
  • the attributes and corresponding values shown in Table 1 are optional, and the template may also include one or more attributes in the above Table 1, or may also include attributes other than those shown in the above Table 1 properties other than .
  • Table 2 shows a service instance template set for SOME/IP communication.
  • the values of the five attributes Category, Checksum, Timestamp, Uuid and Version Driven Find Behavior can be empty or set to corresponding values.
  • an empty value is used as an example.
  • attribute information of the service instance in the set template shown in Table 1 and Table 2 above is not limited thereto, and may also include more or less attribute information, and the value is only an example, and Not limited to this.
  • the attributes and corresponding values shown in Table 2 are optional, and the template may also include one or more attributes in the above Table 2, or may also include attributes other than those shown in the above Table 2 properties other than .
  • Table 3 shows the template set for the end-to-end communication protection information (E2EprofileConfiguration) attribute under the service instance.
  • values of the four attributes of Category, Checksum, Max Delta Counter, and Timestamp can be empty, or can be set to corresponding values.
  • an empty value is used as an example.
  • Table 1 and Table 3 can also form a table, that is, the template of the service instance set for DDS communication;
  • Table 2 and Table 3 can also form a table, that is, the template set for SOME/IP communication The specified service instance template.
  • the attributes and corresponding values shown in Table 3 are optional, and the template may also include one or more attributes in the above Table 3, or may also include attributes other than those shown in the above Table 3 properties other than .
  • Table 4 shows the attribute information of the ServiceInstanceToPortPrototypeMapping element in the set template.
  • the values of the seven attributes Category, Checksum, Enables Log Trace, Log Trace Port Id, Short Name, Timestamp, and Uuid can be empty or set to corresponding values.
  • a null value is used as an example.
  • the attributes and corresponding values shown in Table 4 are optional, and the template may also include one or more attributes in the above Table 4, or may also include attributes other than those shown in the above Table 4 properties other than .
  • Table 5 shows attribute information of the ServiceInstanceToPortPrototypeMapping sub-element PortPrototypeInExecutableInstanceRef.
  • Checksum in the attributes shown in Table 5 may be empty, or may be set to a corresponding value.
  • an empty value is used as an example.
  • attribute information of the elements in the set template shown in Table 4 and Table 5 above is not limited thereto, and may also include more or less attribute information.
  • FIG. 7 shows a schematic flowchart of a configuration method 700 provided by the embodiment of the present application. As shown in FIG. 7, the method 700 can be used in configuring a device, and the method includes:
  • the configuration device configures the exe and process of the sending end and n receiving ends, and deploys the exe and process to a hardware layer (machine), where n is an integer greater than or equal to 1.
  • the configuration device may also configure the service interface, deployment information of the service interface, machine and network interface.
  • the configuration device configures the swc of the sending end, the port on the swc, and the interface on the port.
  • the configuration device designates swc for the exe at the sending end.
  • the process, exe, and swc of the sending end may have a one-to-one correspondence.
  • the configuring device creates a service instance for the sender and configures attribute information of the service instance.
  • the configuration device may create a service instance for the sender and configure the attribute information of the service instance after receiving the operation of manually creating the service instance of the sender and configuring the attribute information of the service instance by the user.
  • the templates shown in Table 1 or Table 2 above can also be used for the creation of the service instance at the sending end and the configuration of attribute information.
  • the configuration device can generate the service instance of the sending end according to the template, thereby helping to improve the efficiency of creating the service instance of the sending end and the configuration efficiency of attribute information in the CM configuration process.
  • the configuration device for example, an electronic control unit (ECU)
  • ECU electronice control unit
  • the configuration device can create a service instance model of the sender and according to the communication of the service instance
  • the pattern selects the corresponding template (including the correspondence between attributes and values) to configure attribute information for the created service instance model.
  • the configuration device can configure attribute information such as Category, Checksum, Domain Id, Qos Profile, Provided Service Instance Id, Service Interface Deployment, Short Name, Timestamp, and Transport plugins for the service instance at the sending end according to the attribute information in the template.
  • the configuration device can set corresponding values for the configured attribute information according to the corresponding relationship between attribute information and values in the template. After configuring the attribute information of the service instance of the sender and its corresponding value, the generation of the service instance of the sender is completed.
  • the configuration device maps the service instance at the sending end to the machine.
  • the configuring device creates a ServiceInstanceToPortPrototypeMapping element in the service instance-to-port mapping for the sending end and configures attributes of the element.
  • the ServiceInstanceToPortPrototypeMapping element can be used to represent the mapping from the service instance to the port at the sending end.
  • the configuration device may create a mapping from a service instance to a port for the sender after receiving an operation of manually creating the ServiceInstanceToPortPrototypeMapping element in the service instance-to-port mapping of the sender by the user.
  • the template shown in Table 4 above may also be used for the mapping from the service instance of the sender to the port.
  • the configuration device can create the ServiceInstanceToPortPrototypeMapping element in the mapping from the service instance of the sending end to the port according to the template, thereby helping to improve the efficiency of creating the mapping from the service instance of the sending end to the port during the CM configuration process.
  • the configuring device creates a PortPrototypeInExecutableInstanceRef for the ServiceInstanceToPortPrototypeMapping element of the sending end and configures its attributes.
  • PortPrototypeInExecutableInstanceRef is a child element of the ServiceInstanceToPortPrototypeMapping element.
  • the configuration device configures the swc, the port and the interface on the port of the receiving end.
  • the configuration device maps m processes among the n processes at the receiving end to the first swc, where m is an integer greater than 0 and less than or equal to n.
  • mapping process from process to exe is not specifically limited in this embodiment of the present application. Exemplarily, as shown in Figures 3 and 4, when there are 3 receiving-end processes, process 1 and process 2 in the 3 receiving-end processes can be mapped to exe 1, and process 3 can be mapped to another exe 2.
  • n and m can be equal.
  • the configuration device can designate a unified swc for the n processes at the receiving end through the compound swc.
  • the specific method can refer to the above figure 4, for example, process 1, process 2 and process 3 can all be mapped to swc 1.
  • the configuration device may also map the n processes of the receiving end to the first swc according to the pre-configured swc information associated with the service instance of the receiving end.
  • the configuration device may designate the root component (rootswc) of the exe at the receiving end as the composite swc and create child elements of the composite swc.
  • the configuration device may point the type (type) of this sub-element to the pre-configured swc associated with the service instance at the receiving end.
  • m may be smaller than n.
  • the configuration device may also map some of the n processes to the first swc.
  • the specific method can refer to the above figure 3, for example, process 1 and process 2 can be mapped to swc 1.
  • the configuring device creates m service instances and configures attribute information of each service instance in the m service instances according to the preconfigured service instances of the receiving end.
  • the configuration device may generate a corresponding number of receiving-end service instances according to the number of processes mapped to the first swc, and create attribute information of each receiving-end service instance.
  • the configuration device may create n receiving-end service instances and configure attribute information of each service instance in the n receiving-end service instances according to the pre-configured service instances.
  • the configuration device may create m receiving end service instances and configure m receiving end service instances according to the preconfigured service instances Attribute information for each service instance in .
  • the preconfigured service instance may be as shown in the above Table 1, or the preconfigured service instance may be as shown in the above Table 2, or the preconfigured service instance may be as shown in the above Table 1 and Table 3, or the preconfigured service instance may be as shown in Table 2 and Table 3 above.
  • the pre-configured service instance of the receiving end may also only include attribute information that needs to be configured.
  • the preconfigured service instance of the receiving end may include two attribute information of Required Service Instance Id and Service Interface Deployment.
  • the configuring device may configure the attribute information of the service instance of the receiving end and its corresponding value according to the attribute information of the service instance of the sending end and the pre-configured service instance of the receiving end.
  • the attribute information of the service instance at the sending end includes Provided Service Instance Id and Service Interface Deployment, and their corresponding values are 2 and DdsServiceInterfaceDeployment[/ARRoot/DdsServiceInterfaceDeplyment] respectively.
  • the configuration device can configure the attribute information Required Service Instance Id and Service Interface Deployment of the service instance at the receiving end according to the pre-configured service instance, and according to the corresponding two attribute information of the service instance at the sending end, Provided Service Instance Id and Service Interface Deployment Value to configure the value corresponding to Required Service Instance Id in the service instance of the receiving end to 2 and configure the corresponding value of Service Interface Deployment in the service instance of the receiving end to DdsServiceInterfaceDeployment[/ARRoot/DdsServiceInterfaceDeplyment].
  • the configuring device generates an association relationship between each service instance in the m service instances corresponding to the m processes and the first port according to the preconfigured association relationship.
  • the pre-configured association includes reference information of processes, ports and service instances, and correspondence among processes, ports and service instances.
  • the reference information of the process in the preconfigured association relationship is process 1, process 2 and process 3, the reference information of the port is port 1, and the reference information of the service instance is the simple name (short name) of the service instance, for example Instance 1, instance 2, and instance 3, the correspondence between processes, ports, and service instances can be shown in Table 6.
  • Process 1, port 1, and instance 1 are in one-to-one correspondence
  • process 2, port 1, and instance 2 are in one-to-one correspondence
  • process 3 port 1, and instance 3 are in one-to-one correspondence.
  • the configuration device creates 3 processes (process 1, process 2, process 3) for the receiving end, and maps these 3 processes to port 1.
  • the configuration device can generate 3 receiving end service instances (instance 1, instance 2 and instance 3).
  • the configuration device can map instance 1 to port 1 and point processDesign of instance 1 to process 1 according to the correspondence between processes, ports, and service instances shown in Table 6; map instance 2 to port 1 and map instance 2 to port 1; processDesign points to process 2; map instance 3 to port 1 and point processDesign of instance 3 to process 3.
  • the reference information of the process in the preconfigured association relationship is process 1 and process 2
  • the reference information of the port is port 1
  • the reference information of the service instance may be the deployment attribute information of the service instance.
  • Service instances can be divided into instances in the SOMP/IP communication mode and instances in the DDS communication mode through the deployment attribute information.
  • the corresponding relationship among processes, ports and service instances may be shown in Table 7. There is a one-to-one correspondence between process 1, port 1 and instance in SOMP/IP communication mode, and a one-to-one correspondence between process 2, port 1 and instance in DDS communication mode.
  • the configuration device After the configuration device generates m service instances and configures the attribute information of each service instance in the m service instances, it can be based on the process number, port number, deployment attribute in the attribute information of each service instance, and the process, port, and service instance The corresponding relationship among them is used to complete the mapping from each service instance to a port in the m service instances.
  • the configuration device creates two processes (process 1 and process 2) for the receiving end, and maps these two processes to port 1.
  • the configuration device can generate two receiver service instances (an instance in the SOME/IP communication mode and an instance in the DDS communication mode).
  • the configuration device can map the instance under the SOME/IP communication mode to port 1 and point the processDesign of the instance under the SOME/IP communication mode to process 1 according to the correspondence between the process, the port, and the service instance shown in Table 7; Map the instance in DDS communication mode to port 1 and point the processDesign of the instance in DDS communication mode to process 2.
  • the preconfigured association relationship may be as shown in Table 6 or Table 7, and the configuration device may generate the association relationship between service instances and ports according to the preconfigured association relationship shown in Table 6 or Table 7.
  • the association relationship between instance 1 and port 1 generated by the configuration device can be shown in Table 8, attribute information of the element ServiceInstanceToPortPrototypeMapping and its corresponding value, and Table 9. It is characterized by the attribute information of the sub-element PortPrototypeInExecutableInstanceRef and its corresponding value.
  • the value corresponding to the attribute information Process in the element ServiceInstanceToPortPrototypeMapping shown in Table 8 and the value corresponding to the attribute information Service Instance can be used to indicate the association relationship between process 1 and instance 1, and the attribute in the sub-element PortPrototypeInExecutableInstanceRef shown in Table 9
  • the information Target Port Prototype can be used to represent the information of the port (port 1) associated with process 1 and instance 1.
  • association relationship between instance 1 and port 1 generated by the configuration device can be determined by the attribute information of the element ServiceInstanceToPortPrototypeMapping shown in Table 8 and its corresponding value, and the attribute information of the sub-element PortPrototypeInExecutableInstanceRef shown in Table 9 and its corresponding value. Representation can also be represented by the attributes of an element and its corresponding value.
  • Table 10 shows the association relationship between instance 1 and port 1 generated by the configuration device through the element ServiceInstanceToPortPrototypeMapping.
  • Tables 8 to 10 may further include more attribute information and corresponding value information, which is not limited in this embodiment of the present application.
  • S712. Determine whether there is a new receiving end that has not configured a mapping relationship between a service instance and a port.
  • FIG. 8 shows a schematic flowchart of a configuration method 800 provided by an embodiment of the present application. As shown in Figure 8, the method 800 includes:
  • the configuration device configures n processes, where n ⁇ 1 and n is an integer.
  • the n processes may be processes at the sending end.
  • the n processes may be processes at the receiving end.
  • the configuration device maps m processes among the n processes to a first component, where 0 ⁇ m ⁇ n and m is an integer, and the first component is associated with a first port.
  • the configuring device maps m processes of the n processes to the first component, including: the configuring device maps the m processes to the first executable program exe, and the first executable program exe
  • the root component is the first composite component; the first sub-element of the first composite component is created, and the type of the first sub-element points to the first component.
  • process 1, process 2, and process 3 may be mapped to swc 1 through a composite swc.
  • the configuring device generates an association relationship between each of the m service instances corresponding to the m processes and the first port according to the preconfigured association relationship.
  • the pre-configured association relationship can be represented by the attribute information of the ServiceInstanceToPortPrototypeMapping element shown in Table 4 and the attribute information of the ServiceInstanceToPortPrototypeMapping sub-element shown in Table 5.
  • the preconfigured association relationship includes reference information of processes, ports and service instances, and correspondence among processes, ports and service instances.
  • the reference information of the process may be a process number.
  • the reference information of the port may be a port number.
  • the reference information of the service instance may be attribute information in the service instance, and the attribute information may include one or more of short name (short name) and deployment information (deployment).
  • the preconfigured association relationship may be as shown in Table 6 or Table 7 above.
  • the reference information of the process may include a process number
  • the reference information of the port may include a port number
  • the reference information of the service instance may include a short name in attribute information of the service instance.
  • the correspondence may include a one-to-one correspondence between process 1, port 1, and instance 1, a one-to-one correspondence between process 2, port 1, and instance 2, and a one-to-one correspondence between process 3, port 1, and instance 3. Therefore, the configuration device can create an association relationship among processes, ports, and service instances according to the above reference information and corresponding relationship.
  • the association relationship among the processes, ports, and service instances created by the configuration device may be as shown in Table 8 and Table 9 above, or may also be shown in Table 10 above.
  • the reference information of the process may include a process number
  • the reference information of the port may include a port number
  • the reference information of the service instance may include deployment in attribute information of the service instance.
  • the corresponding relationship may include a one-to-one relationship between process 1, port 1 and the instance in the SOMP/IP communication mode, and a one-to-one relationship between process 2, port 1 and the instance in the DDS communication mode. Therefore, the configuration device can create an association relationship among processes, ports, and service instances according to the above reference information and corresponding relationship.
  • the method before generating the association relationship between each of the m service instances corresponding to the m processes and the first port, the method further includes: generating the m service instances according to the pre-configured service instances and Configure attribute information of each of the m service instances.
  • the preconfigured service instance may be as shown in Table 1; or, the preconfigured service instance may be as shown in Table 2.
  • the configuration device can generate multiple service instances for multiple processes and configure the attribute information of each service instance in the multiple service instances, and the attribute information of each service instance is short
  • the value of the name attribute can be different, for example, the value of the short name attribute of the generated service instance 1 can be Required_dds_1, the value of the short name attribute of the generated service instance 2 can be Required_dds_2, and the short name attribute of the generated service instance 3
  • the value can be Required_dds_3.
  • the deployment attribute in the attribute information of each service instance may be different.
  • the value of the deployment attribute of a generated service instance may be DdsServiceInterfaceDeployment[/ARRoot/DdsServiceInterfaceDeplyment], and the generated deployment attribute of another service instance
  • the value can be SomeipServiceInterfaceDeployment[/ARRoot/SomeipServiceInterfaceDeplyment].
  • the configuration device generates multiple receiving-end service instances through pre-configured service instances and configures the attribute information of each service instance in the multiple receiving-end service instances
  • the Instance Id attribute of each receiving-end service instance can be the same as the sending
  • the instance Id attribute of the service instance at the end is the same, so as to facilitate the communication between the sender and the receiver.
  • the preconfigured service instance may also be shown in Table 1 and Table 3; or, the preconfigured service instance may also be shown in Table 2 and Table 3.
  • the n is greater than or equal to 2 and the n processes are processes of the receiving end.
  • the n processes may include process 1, process 2, and process 3, and process 1, process 2, and process 3 may be receiving end processes.
  • the pre-configured service instance includes a first pre-configured service instance and a second pre-configured service instance
  • the first pre-configured service instance may be an Internet protocol-based extensible service-oriented middleware SOME/
  • the second preconfigured service instance may be a service instance for data distribution service DDS communication.
  • different service instance templates can be configured in advance for service instances in different communication modes, so that service instances can be generated and their attribute information configured according to different service instance templates when generating service instances, which is helpful Improve configuration flexibility.
  • the attribute information of each service instance includes one or more of service instance identification information, transmission plug-in information, deployment information, service quality configuration information, and end-to-end communication protection information.
  • FIG. 9 shows a schematic block diagram of a configuration device 900 provided by an embodiment of the present application.
  • the device 900 includes:
  • the configuration unit 910 is configured to configure n processes, where n ⁇ 1 and n is an integer.
  • the mapping unit 920 is configured to map m processes among the n processes to a first component, where 0 ⁇ m ⁇ n and m is an integer, and the first component is associated with a first port.
  • the generating unit 930 is configured to generate an association relationship between each of the m service instances corresponding to the m processes and the first port according to the preconfigured association relationship.
  • the preconfigured association relationship includes reference information of processes, ports and service instances, and correspondence among processes, ports and service instances.
  • the generation unit 930 is further configured to generate the m service instances corresponding to the m processes according to the pre-configured service instances before generating the association relationship between each service instance and the first port. service instances and configure attribute information of each of the m service instances.
  • mapping unit 920 is specifically configured to: map the m processes to the first executable program exe, the root component of the first executable program exe is the first compound component; create the first compound component of the first compound component A child element, the type of the first child element points to the first component.
  • the n is greater than or equal to 2 and the n processes are processes of the receiving end.
  • the preconfigured service instance includes a first preconfigured service instance and a second preconfigured service instance, and the first preconfigured service instance is for SOME/IP A communication service instance, the second preconfigured service instance is a service instance for the data distribution service DDS communication.
  • the attribute information of each service instance includes one or more of service instance identification information, transmission plug-in information, deployment information, service quality configuration information, and end-to-end communication protection information.
  • FIG. 10 shows a schematic block diagram of a configuration device 1000 provided by an embodiment of the present application.
  • the device 1000 includes a memory 1001 for storing computer instructions; a processor 1002 for executing the computer instructions stored in the memory, so that the The device 1000 executes the above configuration method.
  • the embodiment of the present application also provides a terminal device, and the terminal device may include the foregoing apparatus 900 or apparatus 1000 .
  • the embodiment of the present application also provides a computer program product, the computer program product including: computer program code, when the computer program code is run on the computer, the computer is made to execute the above method performed by the vehicle.
  • the embodiment of the present application also provides a computer-readable medium, the computer-readable medium stores program codes, and when the computer program codes are run on a computer, the computer is made to execute the above method.
  • each step of the above method can be completed by an integrated logic circuit of hardware in a processor or an instruction in the form of software.
  • the methods disclosed in the embodiments of the present application may be directly implemented by a hardware processor, or implemented by a combination of hardware and software modules in the processor.
  • the software module can be located in a mature storage medium in the field such as random access memory, flash memory, read-only memory, programmable read-only memory or electrically erasable programmable memory, register.
  • the storage medium is located in the memory, and the processor reads the information in the memory, and completes the steps of the above method in combination with its hardware. To avoid repetition, no detailed description is given here.
  • the processor may be a central processing unit (central processing unit, CPU), and the processor may also be other general-purpose processors, digital signal processors (digital signal processor, DSP), dedicated integrated Circuit (application specific integrated circuit, ASIC), off-the-shelf programmable gate array (field programmable gate array, FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc.
  • a general-purpose processor may be a microprocessor, or the processor may be any conventional processor, or the like.
  • the memory may include a read-only memory and a random access memory, and provide instructions and data to the processor.
  • sequence numbers of the above-mentioned processes do not mean the order of execution, and the execution order of the processes should be determined by their functions and internal logic, and should not be used in the embodiments of the present application.
  • the implementation process constitutes any limitation.
  • the disclosed systems, devices and methods may be implemented in other ways.
  • the device embodiments described above are only illustrative.
  • the division of the units is only a logical function division. In actual implementation, there may be other division methods.
  • multiple units or components can be combined or May be integrated into another system, or some features may be ignored, or not implemented.
  • the mutual coupling or direct coupling or communication connection shown or discussed may be through some interfaces, and the indirect coupling or communication connection of devices or units may be in electrical, mechanical or other forms.
  • the units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place, or may be distributed to multiple network units. Part or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, each unit may exist separately physically, or two or more units may be integrated into one unit.
  • the functions described above are realized in the form of software function units and sold or used as independent products, they can be stored in a computer-readable storage medium.
  • the technical solution of the present application is essentially or the part that contributes to the prior art or the part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including Several instructions are used to make a computer device (which may be a personal computer, a server, or a network device, etc.) execute all or part of the steps of the methods described in the various embodiments of the present application.
  • the aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (read-only memory, ROM), random access memory (random access memory, RAM), magnetic disk or optical disc and other media that can store program codes. .

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Stored Programmes (AREA)

Abstract

本申请提供了一种配置方法和装置，该方法包括：配置n个进程，n≥1且n为整数；将该n个进程中的m个进程映射到第一组件，0＜m≤n且m为整数，该第一组件关联第一端口；根据预配置的关联关系，生成该m个进程对应的m个服务实例中每个服务实例到该第一端口的关联关系。本申请实施例有助于简化通信管理配置流程，从而有助于提升配置效率。

Description

一种配置方法和装置 技术领域
本申请涉及智能车领域，并且更具体地，涉及一种配置方法和装置。
背景技术
目前，汽车电子网络正向多总线混合网络互联方向发展。在2003年，为了避免各大厂商之间的兼容性问题，汽车领域推出了一个开放化、标准化的汽车嵌入式系统软件架构(auto motive open system architecture，AUTOSAR)规范。各汽车厂商可基于此标准进行自己的软件开发。
为了面对汽车更复杂的需求(例如，自动驾驶、车联网以及域控制)。业界在传统汽车嵌入式系统软件架构(classic AUTOSAR，CP)的成熟经验基础上定义了一套自适应汽车嵌入式系统软件架构(adaptive AUTOSAR，AP)。其中，通信管理(communication management，CM)是AP配置中的关键一步，其决定了整个系统的软件架构和软件之间的协作关系。
当前已有公司推出了在CM中手动创建元素、配置元素属性以及关联关系的技术方案，但是这样会导致CM配置效率很低。
发明内容
本申请提供一种配置方法和装置，有助于简化通信管理配置流程，从而有助于提升配置效率。
第一方面，提供了一种配置方法，该方法包括：配置n个进程，n≥1且n为整数；将该n个进程中的m个进程映射到第一组件，0＜m≤n且m为整数，该第一组件关联第一端口；根据预配置的关联关系，生成该m个进程对应的m个服务实例中每个服务实例到该第一端口的关联关系。
本申请实施例中，通过预配置的关联关系，可以生成每个服务实例到第一端口的关联关系，无需用户手动配置关联关系，有助于简化通信管理配置流程，从而有助于提升配置效率。
结合第一方面，在第一方面的某些实现方式中，该预配置的关联关系中包括进程、端口和服务实例的引用信息以及进程、端口和服务实例之间的对应关系。
本申请实施例中，预配置的关联关系中可以包括进程、端口和服务实例的引用信息以及进程、端口和服务实例之间的对应关系，这样可以通过引用信息以及对应关系将进程、端口和服务实例关联起来，有助于简化通信管理配置流程，从而有助于提升配置效率。
在一些可能的实现方式中，该进程的引用信息可以是进程号。
在一些可能的实现方式中，该端口的引用信息可以是端口号。
在一些可能的实现方式中，该服务实例的引用信息可以是服务实例中的属性信息，该 属性信息可以包括简短名称(short name)、部署信息(deployment)中的一个或者多个。
结合第一方面，在第一方面的某些实现方式中，该生成该m个进程对应的m个服务实例中每个服务实例到该第一端口的关联关系之前，该方法还包括：根据预配置的服务实例，生成该m个服务实例且配置该m个服务实例中的每个服务实例的属性信息。
本申请实施例中，通过预配置的服务实例可以生成相应的服务实例，无需用户手动配置服务实例以及其属性信息，有助于简化通信管理配置流程，从而有助于提升配置效率。
结合第一方面，在第一方面的某些实现方式中，该将该n个进程中的m个进程映射到第一组件，包括：将该m个进程映射到第一可执行程序exe，该第一可执行程序exe的根组件为第一复合组件；创建该第一复合组件的第一子元素，该第一子元素的类型指向该第一组件。
本申请实施例中，通过第一复合组件，可以将n个进程中的m个进程映射到第一组件，从而可以实现多个进程到第一组件的映射。
结合第一方面，在第一方面的某些实现方式中，该n大于或者等于2且该n个进程为接收端的进程。
本申请实施例的配置方法可以应用于CM配置中的一发多收(即一个发送端和多个接收端通信)的场景，通过预配置的服务实例，可以生成多个接收端的服务实例并配置每个服务实例的属性信息；和/或，通过预配置的关联关系，可以生成多个接收端的服务实例中每个服务实例到第一端口的关联关系，无需用户手动配置，有助于简化一发多收场景下通信管理配置流程，从而有助于提升配置效率。
在一些可能的实现方式中，n和m相等。
本申请实施例中，可以将n个进程都映射到第一组件，这样在生成接收端的服务实例时，可以根据预配置的服务实例生成n个接收端的服务实例，从而使得接收端的服务实例均可以通过预配置的服务实例来生成，无需用户手动创建服务实例并配置其属性信息，有助于简化一发多收场景下通信管理配置流程，从而有助于提升配置效率。
结合第一方面，在第一方面的某些实现方式中，该预配置的服务实例包括第一预配置的服务实例和第二预配置的服务实例，该第一预配置的服务实例为针对基于互联网协议可扩展面向服务的中间件SOME/IP通信的服务实例，该第二预配置的服务实例为针对数据分发服务DDS通信的服务实例。
本申请实施例中，针对不同通信模式下的服务实例可以提前配置好不同的服务实例模板，这样在生成服务实例时就可以根据不同的服务实例模板来生成服务实例并配置其属性信息，有助于提升配置的灵活性。
结合第一方面，在第一方面的某些实现方式中，该每个服务实例的属性信息包括服务实例的标识信息、传输插件信息、部署信息、服务质量配置信息以及端到端通信保护信息中的一种或者多种。
第二方面，提供了一种配置装置，该装置包括：配置单元，用于配置n个进程，n≥1且n为整数；映射单元，用于将该n个进程中的m个进程映射到第一组件，0＜m≤n且m为整数，该第一组件关联第一端口；生成单元，用于根据预配置的关联关系，生成该m个进程对应的m个服务实例中每个服务实例到该第一端口的关联关系。
结合第二方面，在第二方面的某些实现方式中，该预配置的关联关系中包括进程、端 口和服务实例的引用信息以及进程、端口和服务实例之间的对应关系。
结合第二方面，在第二方面的某些实现方式中，该生成单元，还用于在生成该m个进程对应的m个服务实例中每个服务实例到该第一端口的关联关系之前，根据预配置的服务实例，生成该m个服务实例且配置该m个服务实例中的每个服务实例的属性信息。
结合第二方面，在第二方面的某些实现方式中，该映射单元具体用于：将该m个进程映射到第一可执行程序exe，该第一可执行程序exe的根组件为第一复合组件；创建该第一复合组件的第一子元素，该第一子元素的类型指向该第一组件。
结合第二方面，在第二方面的某些实现方式中，该n大于或者等于2且该n个进程为接收端的进程。
结合第二方面，在第二方面的某些实现方式中，该预配置的服务实例包括第一预配置的服务实例和第二预配置的服务实例，该第一预配置的服务实例为针对基于互联网协议可扩展面向服务的中间件SOME/IP通信的服务实例，该第二预配置的服务实例为针对数据分发服务DDS通信的服务实例。
结合第二方面，在第二方面的某些实现方式中，该每个服务实例的属性信息包括服务实例的标识信息、传输插件信息、部署信息、服务质量配置信息以及端到端通信保护信息中的一种或者多种。
第三方面，提供了一种配置装置，该装置包括：存储器，用于存储计算机指令；处理器，用于执行该存储器中存储的计算机指令，以使得该装置执行上述第一方面中的方法。
第四方面，提供了一种终端设备，该终端设备包括上述第二方面或者第三方面中任一项所述的装置。
第五方面，提供了一种计算机程序产品，所述计算机程序产品包括：计算机程序代码，当所述计算机程序代码在计算机上运行时，使得计算机执行上述第一方面中的方法。
需要说明的是，上述计算机程序代码可以全部或者部分存储在第一存储介质上，其中第一存储介质可以与处理器封装在一起的，也可以与处理器单独封装，本申请实施例对此不作具体限定。
第六方面，提供了一种计算机可读介质，所述计算机可读介质存储有程序代码，当所述计算机程序代码在计算机上运行时，使得计算机执行上述第一方面中的方法。
第七方面，本申请实施例提供了一种芯片系统，该芯片系统包括处理器，用于调用存储器中存储的计算机程序或计算机指令，以使得该处理器执行上述任一方面所述的方法。
结合第七方面，在一种可能的实现方式中，该处理器通过接口与存储器耦合。
结合第七方面，在一种可能的实现方式中，该芯片系统还包括存储器，该存储器中存储有计算机程序或计算机指令。
附图说明
图1是自适应汽车嵌入式系统软件架构的示意图。
图2是一发多收场景的示意图。
图3是一个进程与多个进程进行通信时的组织形式。
图4是一个进程与多个进程进行通信时的另一组织形式。
图5是生成服务实例并将服务实例与端口关联的示意图。
图6是生成服务实例并将服务实例与端口关联的另一示意图。
图7是本申请实施例提供的配置方法的示意性流程图。
图8是本申请实施例提供的配置方法的另一示意性流程图。
图9是本申请实施例提供的配置装置的示意性流框图。
图10是本申请实施例提供的配置装置的示意性流框图。
具体实施方式
下面将结合附图，对本申请中的技术方案进行描述。
图1是自适应汽车嵌入式系统软件架构的示意图。该软件架构可以分为应用层、运行层、基础服务层以及硬件层。其中，基础服务器层中包括通信管理(communication management，CM)、网络管理(network management)、状态管理(state management)、升级配置管理(update configuration management)、加密服务(cryptography)、时间同步(time synchronization)、诊断服务(diagnostics)、存储服务(persistency)和执行管理(execution management)等。CM是AP配置中的关键一步，其决定了整个系统的软件架构和软件之间的协作关系。CM配置中需要对多个元素进行创建、属性配置和引用关联。
当硬件、网络结构、通信接口和软件结构配置好后，在此基础上可以进行CM的配置。CM的一个重要步骤就是通信实例化，也就是创建一对用于通信连接的服务实例(service instance)。该过程需要创建的元素包括：进程(process)、可执行程序(executable，exe)、实例(instance)、自适应应用组件(AdaptiveApplicationSwComponentType，swc)、复合组件(CompositionSwComponentType)等。需要完成的属性配置包括：实例(instance)的实例标识(instance ID)、传输插件信息(Transport plugin)、部署信息(deployment)、服务质量配置信息(Qos profile)以及端到端通信保护信息(E2EprofileConfiguration)。需要完成的引用关联包括：process和exe的关联、exe和swc的关联、instance和端口(port)的关联(instance to port mapping)。
图2示出了一种一发多收场景的示意图。在配置通信发送端和接收端时，通常发送端服务实例(provider service instance)的个数为1个，而其对应的接收端服务实例(required service instance)有多个。该场景会导致接收端的服务实例需要多次重复配置。
图3和图4分别示出了一个进程与多个进程进行通信时的组织形式。如图3所示，每个exe有只属于自己的swc，例如，exe1与swc1对应，exe2与swc2对应。如图4所示，对于同一功能的swc，多个exe可以通过复合组件共享此swc，例如，exe1和exe2通过复合swc共享swc1。
图5示出了针对图3所示的组织形式，生成服务实例并将服务实例与端口关联的过程。图6示出了针对图4所示的组织形式中，生成服务实例并将服务实例与端口关联的过程。可以看出，针对图3和图4所示的两种组织形式，其通信实例化是一样的。
目前已有公司在这种通信实例化接收端配置基本一致的场景下，通过一个个手动创建接收端服务实例、发送端服务实例以及服务实例到端口的关联。这样如果接收端服务实例有n个就要手动创建n个接收端服务实例并配置接收端服务实例到端口的映射n次。这样会导致CM配置的效率很低。
本申请实施例提供的配置方法和装置可以提前完成元素、属性以及关联关系的设定， 形成模板。在面对一发多收的场景时，可以根据模板自动生成所需要的元素、属性和关联关系，从而省去了复杂的手动配置过程，有助于提升CM配置的效率。
一个实施例中，设定的模板会根据不同的通信方式进行分类。示例性的，可以根据针对基于互联网协议可扩展面向服务的中间件(scalable service-Oriented middleware over IP，SOME/IP)通信和数据分发服务(data distribution service，DDS)通信设定不同的模板。
示例性的，表1示出了一种针对DDS通信所设定的服务实例的模板。
表1
Figure PCTCN2021126979-appb-000001
应理解，Category、Checksum以及Timestamp这3个属性的值可以为空，也可以设置为相应的取值，在表1的示例中，以空值作为示例。
一个实施例中，表1所示的属性以及对应的值均为可选地，模板中也可以包括上述表1中的一个或者多个属性，或者，还可以包括除上述表1所示的属性以外的其他属性。
示例性的，表2示出了一种针对SOME/IP通信所设定的服务实例模板。
表2
Figure PCTCN2021126979-appb-000002
Figure PCTCN2021126979-appb-000003
应理解，Category、Checksum、Timestamp、Uuid以及Version Driven Find Behavior这5个属性的值可以为空，也可以设置为相应的取值，在表2的示例中，以空值作为示例。
还应理解，以上表1和表2所示的设定的模板中的服务实例的属性信息并不限于此，也可以包括更多或者更少的属性信息，取值也只是一种示例，并不限于此。
一个实施例中，表2所示的属性以及对应的值均为可选地，模板中也可以包括上述表2中的一个或者多个属性，或者，还可以包括除上述表2所示的属性以外的其他属性。
表3示出了对服务实例下的端到端通信保护信息(E2EprofileConfiguration)属性所设定的模板。
表3
Figure PCTCN2021126979-appb-000004
Figure PCTCN2021126979-appb-000005
应理解，Category、Checksum、Max Delta Counter以及Timestamp这4个属性的值可以为空，也可以设置为相应的取值，在表3的示例中，以空值作为示例。
还应理解，以上表1和表3也可以组成一张表，即针对DDS通信所设定的服务实例的模板；表2和表3也可以组成一张表，即针对SOME/IP通信所设定的服务实例模板。
一个实施例中，表3所示的属性以及对应的值均为可选地，模板中也可以包括上述表3中的一个或者多个属性，或者，还可以包括除上述表3所示的属性以外的其他属性。
在生成服务实例并配置了服务实例的属性后，可以根据设定的模板完成服务实例到端口的映射，表4示出了所设定的模板中ServiceInstanceToPortPrototypeMapping元素的属性信息。
表4
Figure PCTCN2021126979-appb-000006
Figure PCTCN2021126979-appb-000007
应理解，表4所示的属性中Category、Checksum、Enables Log Trace、Log Trace Port Id、Short Name、Timestamp以及Uuid这7个属性的值可以为空，也可以设置为相应的取值，在表4的示例中，以空值作为示例。
一个实施例中，表4所示的属性以及对应的值均为可选地，模板中也可以包括上述表4中的一个或者多个属性，或者，还可以包括除上述表4所示的属性以外的其他属性。
示例性的，表5示出了ServiceInstanceToPortPrototypeMapping子元素PortPrototypeInExecutableInstanceRef的属性信息。
表5
Figure PCTCN2021126979-appb-000008
应理解，表5所示的属性中Checksum的值可以为空，也可以设置为相应的取值，在表5的示例中，以空值作为示例。
还应理解，以上表4和表5所示的设定的模板中的元素的属性信息并不限于此，也可以包括更多或者更少的属性信息。
图7示出了本申请实施例提供的配置方法700的示意性流程图。如图7所示，该方法700可以用于配置装置中，该方法包括：
S701，配置装置配置发送端和n个接收端的exe以及process，并将exe以及process部署到硬件层(machine)中，n为大于或者等于1的整数。
一个实施例中，在配置发送端和n个接收端的exe以及process之前，配置装置还可以配置服务接口、服务接口的部署信息、machine以及网络接口。
S702，配置装置配置发送端的swc、swc上的端口和端口上的接口。
S703，配置装置为发送端的exe指定swc。
一个实施例中，对于一发多收的场景，由于只有一个发送端，发送端的process、exe、swc可以是一一对应的关系。
S704，配置装置为发送端创建服务实例并配置服务实例的属性信息。
一个实施例中，配置装置可以是在接收到用户手动创建发送端的服务实例以及配置服务实例的属性信息的操作后，为发送端创建服务实例并配置服务实例的属性信息。
一个实施例中，对于发送端的服务实例的创建以及属性信息的配置也可以使用上述表1或者表2所示的模板。配置装置可以根据模板来生成发送端的服务实例，从而有助于提升CM配置过程中发送端的服务实例的创建效率以及属性信息的配置效率。
示例性的，以服务实例为DDS通信为例，配置装置(例如，电子控制单元(electronic control unit，ECU))在生成发送端的服务实例时，可以创建发送端的服务实例模型并根据服务实例的通信模式选择对应的模板(包括属性和值的对应关系)来为创建好的服务实例模型配置属性信息。配置装置可以根据模板中的属性信息为发送端的服务实例配置Category、Checksum、Domain Id、Qos Profile、Provided Service Instance Id、Service Interface Deployment、Short Name、Timestamp以及Transport plugins等属性信息。进而配置装置可以根据模板中属性信息以及取值的对应关系为配置好的属性信息设定对应的值。在配置好发送端的服务实例的属性信息以及其对应的值后，就完成了发送端的服务实例的生成。
S705，配置装置将发送端的服务实例映射到machine上。
S706，配置装置为发送端创建服务实例到端口的映射中ServiceInstanceToPortPrototypeMapping元素并配置该元素的属性。
一个实施例中，ServiceInstanceToPortPrototypeMapping元素可以用于表征发送端的服务实例到端口的映射。
一个实施例中，配置装置可以是在接收到用户手动创建发送端的服务实例到端口映射中ServiceInstanceToPortPrototypeMapping元素的操作后，为发送端创建服务实例到端口的映射。
一个实施例中，对于发送端的服务实例到端口的映射也可以使用上述表4所示的模板。配置装置可以根据模板来创建发送端的服务实例到端口映射中ServiceInstanceToPortPrototypeMapping元素，从而有助于提升CM配置过程中创建发送端的服务实例到端口的映射的效率。
S707，配置装置为发送端的ServiceInstanceToPortPrototypeMapping元素创建PortPrototypeInExecutableInstanceRef并配置其属性。
PortPrototypeInExecutableInstanceRef为ServiceInstanceToPortPrototypeMapping元素的子元素。
S708，配置装置配置接收端的swc、端口以及端口上的接口。
S709，配置装置将接收端的n个process中的m个进程映射到第一swc，m为大于0且小于或者等于n的整数。
应理解，本申请实施例中对于process到exe的映射过程并不作具体限定。示例性的，如图3和4所示，当有3个接收端的process时，可以将3个接收端的process中的process 1和process 2映射到exe 1，将process 3映射到另一个exe 2。
一个实施例中，n和m可以相等。配置装置可以将接收端的n个process通过复合swc 指定统一的swc。具体的方式可以参考上述图4所示，例如，process 1、process 2和process 3可以均映射到swc 1。
一个实施例中，配置装置也可以根据预配置的接收端的服务实例所关联的swc信息，将接收端的n个process映射到该第一swc。配置装置可以将接收端的exe的根组件(rootswc)指定为复合swc并创建复合swc的子元素。配置装置可以将这个子元素的类型(type)指向预配置的接收端的服务实例所关联的swc。
一个实施例中，m可以是小于n的。配置装置也可以将n个process中的部分process映射到第一swc。具体的方式可以参考上述图3所示，例如，process 1和process 2可以映射到swc 1。
S710，配置装置根据预配置的接收端的服务实例，创建m个服务实例且配置所述m个服务实例中的每个服务实例的属性信息。
配置装置可以根据映射到第一swc的process的数量生成相应个数的接收端服务实例并创建每个接收端服务实例的属性信息。
示例性的，若n个process均映射到第一swc，则配置装置可以根据预配置的服务实例，创建n个接收端服务实例并配置n个接收端服务实例中每个服务实例的属性信息。
示例性的，若n个process中m个process(n大于m)均映射到第一swc，则配置装置可以根据预配置的服务实例，创建m个接收端服务实例并配置m个接收端服务实例中每个服务实例的属性信息。
一个实施例中，该预配置的服务实例可以如上述表1所示，或者，该预配置的服务实例可以如上述表2所示，或者，该预配置的服务实例可以如上述表1和表3所示，或者，该预配置的服务实例可以如上述表2和表3所示。
一个实施例中，该预配置的接收端的服务实例中也可以只包括需要配置的属性信息。例如，预配置的接收端的服务实例中可以包括Required Service Instance Id和Service Interface Deployment这2个属性信息。配置装置可以根据发送端的服务实例的属性信息以及其对应的值、预配置的接收端的服务实例来配置接收端的服务实例的属性信息及其对应的值。例如，发送端的服务实例的属性信息中包括Provided Service Instance Id和Service Interface Deployment，其对应的值分别为2和DdsServiceInterfaceDeployment[/ARRoot/DdsServiceInterfaceDeplyment]。则配置装置可以根据预配置的服务实例来配置接收端的服务实例的属性信息Required Service Instance Id和Service Interface Deployment，并根据发送端的服务实例中Provided Service Instance Id和Service Interface Deployment这2个属性信息对应的值来配置接收端的服务实例中Required Service Instance Id对应的值为2且配置接收端的服务实例中Service Interface Deployment对应的值为DdsServiceInterfaceDeployment[/ARRoot/DdsServiceInterfaceDeplyment]。
S711，配置装置根据预配置的关联关系，生成所述m个进程对应的m个服务实例中每个服务实例到第一端口的关联关系。
一个实施例中，该预配置的关联关系中包括进程、端口和服务实例的引用信息以及进程、端口和服务实例之间的对应关系。
示例性的，该预配置的关联关系中进程的引用信息为process 1、process 2和process 3， 端口的引用信息为port 1，服务实例的引用信息为服务实例的简单名称(short name)，例如instance 1、instance 2和instance 3，进程、端口和服务实例之间的对应关系可以如表6所示。process 1、port 1以及instance 1为一一对应关系，process 2、port 1以及instance 2为一一对应关系、process 3、port 1以及instance 3为一一对应关系。
表6
Figure PCTCN2021126979-appb-000009
例如，配置装置为接收端创建了3个进程(process 1、process 2、process 3)，并将这3个进程均映射到了port 1。配置装置可以生成3个接收端服务实例(instance 1、instance 2和instance 3)。配置装置可以根据表6所示的进程、端口和服务实例之间的对应关系，将instance 1映射到port 1并将instance 1的processDesign指向process 1；将instance 2映射到port 1并将instance 2的processDesign指向process 2；将instance 3映射到port 1并将instance 3的processDesign指向process 3。
示例性的，该预配置的关联关系中进程的引用信息为process 1和process 2，端口的引用信息为port 1，服务实例的引用信息可以是服务实例的deployment属性信息。通过deployment属性信息可以将服务实例分为SOMP/IP通信模式下的instance和DDS通信模式下的instance。进程、端口和服务实例之间的对应关系可以如表7所示。process 1、port 1以及SOMP/IP通信模式下的instance为一一对应关系，process 2、port 1以及DDS通信模式下的instance为一一对应关系。
表7
Figure PCTCN2021126979-appb-000010
当配置装置生成m个服务实例并配置好m个服务实例中每个服务实例的属性信息后，可以根据进程号、端口号、每个服务实例的属性信息中deployment属性以及进程、端口和服务实例之间的对应关系来完成m个服务实例中每个服务实例到端口的映射。
例如，配置装置为接收端创建了2个进程(process 1和process 2)，并将这2个进程均映射到了port 1。配置装置可以生成2个接收端服务实例(SOME/IP通信模式下的instance和DDS通信模式下的instance)。配置装置可以根据表7所示的进程、端口和服务实例之间的对应关系，将SOME/IP通信模式下的instance映射到port 1并将SOME/IP通信模式下的instance的processDesign指向process 1；将DDS通信模式下的instance映射到port 1并将DDS通信模式下的instance的processDesign指向process 2。
一个实施例中，预配置的关联关系可以如表6或者表7所示，配置装置可以根据表6或者表7所示的预配置的关联关系来生成服务实例到端口的关联关系。示例性的，以表6所示的预配置的关联为例，配置装置生成的instance 1到port 1的关联关系可以由表8所示的元素ServiceInstanceToPortPrototypeMapping的属性信息及其对应的值、表9所示子元素PortPrototypeInExecutableInstanceRef的属性信息及其对应的值来表征。
表8
属性(property) 值(value)
Process Process 1
Service Instance Instance 1
… …
表9
属性(property) 值(value)
Target Port Prototype Port 1
… …
应理解，表8所示的元素ServiceInstanceToPortPrototypeMapping中的属性信息Process对应的值和属性信息Service Instance对应的值可以用来表示process 1和instance 1的关联关系，表9所示的子元素PortPrototypeInExecutableInstanceRef中的属性信息Target Port Prototype可以用来表征process 1和instance 1所关联的端口(port 1)的信息。
还应理解，配置装置生成的instance 1到port 1的关联关系可以由表8所示的元素ServiceInstanceToPortPrototypeMapping的属性信息及其对应的值、表9所示子元素PortPrototypeInExecutableInstanceRef的属性信息及其对应的值来表征，也可以由一个元素的属性以及其对应的值来表征。示例性的，表10示出了通过元素ServiceInstanceToPortPrototypeMapping来表征配置装置生成的instance 1到port 1的关联关系。
表10
属性(property) 值(value)
Process Process 1
Service Instance Instance 1
Target Port Prototype Port 1
… …
应理解，以上表8至表10中还可以包括更多的属性信息以及对应的值的信息，本申请实施例对此不作限定。
S712，判断是否有新的接收端没有配置服务实例到端口的映射关系。
一个实施例中，若没有新的接收端未配置服务实例到端口的映射关系，则结束配置流程；否则执行S713。
S713，若还有新的接收端未配置服务实例到端口的映射关系，则为新的接收端继续创建ServiceInstanceToPortPrototypeMapping元素并配置其属性。
图8示出了本申请实施例提供的配置方法800的示意性流程图。如图8所示，该方法 800包括：
S801，配置装置配置n个进程，n≥1且n为整数。
可选地，该n个进程可以为发送端的进程。
可选地，该n个进程可以为接收端的进程。
S802，配置装置将该n个进程中的m个进程映射到第一组件，0＜m≤n且m为整数，该第一组件关联第一端口。
可选地，该配置装置将该n个进程中的m个进程映射到第一组件，包括：该配置装置将该m个进程映射到第一可执行程序exe，该第一可执行程序exe的根组件为第一复合组件；创建该第一复合组件的第一子元素，该第一子元素的类型指向该第一组件。
示例性的，如图4所示，进程1、进程2和进程3可以通过复合swc映射到swc 1。
S803，配置装置根据预配置的关联关系，生成该m个进程对应的m个服务实例中每个服务实例到该第一端口的关联关系。
可选地，若多个进程通过复合swc映射到第一组件，那么该预配置的关联关系可以由表4所示的ServiceInstanceToPortPrototypeMapping元素的属性信息以及表5所示ServiceInstanceToPortPrototypeMapping子元素的属性信息表征。
可选地，该预配置的关联关系中包括进程、端口和服务实例的引用信息以及进程、端口和服务实例之间的对应关系。
可选地，该进程的引用信息可以是进程号。
可选地，该端口的引用信息可以是端口号。
可选地，该服务实例的引用信息可以是服务实例中的属性信息，该属性信息可以包括简短名称(short name)、部署信息(deployment)中的一个或者多个。
示例性的，该预配置的关联关系可以如上述表6或者表7所示。
示例性的，如表6所示，该进程的引用信息可以包括进程号，该端口的引用信息可以包括端口号，该服务实例的引用信息可以包括服务实例的属性信息中的short name。该对应关系可以包括process 1、port 1以及instance 1为一一对应关系，process 2、port 1以及instance 2为一一对应关系、process 3、port 1以及instance 3为一一对应关系。从而配置装置可以根据上述引用信息以及对应关系，创建进程、端口以及服务实例之间的关联关系。示例性的，配置装置创建的进程、端口以及服务实例之间的关联关系可以如上述表8和表9所示，或者，也可以由上述表10所示。
示例性的，如表7所示，该进程的引用信息可以包括进程号，该端口的引用信息可以包括端口号，该服务实例的引用信息可以包括服务实例的属性信息中的deployment。该对应关系可以包括process 1、port 1以及SOMP/IP通信模式下的instance为一一对应关系，process 2、port 1以及DDS通信模式下的instance为一一对应关系。从而配置装置可以根据上述引用信息以及对应关系，创建进程、端口以及服务实例之间的关联关系。
可选地，该生成该m个进程对应的m个服务实例中每个服务实例到该第一端口的关联关系之前，该方法还包括：根据预配置的服务实例，生成该m个服务实例且配置该m个服务实例中的每个服务实例的属性信息。
示例性的，该预配置的服务实例可以如表1所示；或者，该预配置的服务实例可以如表2所示。
示例性的，配置装置根据该预配置的服务实例，可以针对多个进程生成多个服务实例并配置该多个服务实例中每个服务实例的属性信息，该每个服务实例的属性信息中short name属性的值可以是不同的，例如，生成的服务实例1的short name属性的值可以为Required_dds_1，生成的服务实例2的short name属性的值可以为Required_dds_2，生成的服务实例3的short name属性的值可以为Required_dds_3。
示例性的，每个服务实例的属性信息中deployment属性可以是不同的，例如，生成的一个服务实例的deployment属性的值可以为DdsServiceInterfaceDeployment[/ARRoot/DdsServiceInterfaceDeplyment]，生成的另一个服务实例的deployment属性的值可以为SomeipServiceInterfaceDeployment[/ARRoot/SomeipServiceInterfaceDeplyment]。
应理解，若配置装置通过预配置的服务实例生成多个接收端服务实例并配置多个接收端的服务实例中每个服务实例的属性信息时，每个接收端的服务实例的Instance Id属性可以和发送端的服务实例的instance Id属性相同，从而便于发送端和接收端之间的通信。
示例性的，该预配置的服务实例也可以如表1和表3所示；或者，该预配置的服务实例还可以如表2和表3所示。
可选地，该n大于等于2且该n个进程为接收端的进程。
示例性的，如图2所示的一发多收场景，该n个进程可以包括进程1、进程2和进程3且进程1、进程2和进程3可以为接收端进程。
可选地，该预配置的服务实例包括第一预配置的服务实例和第二预配置的服务实例，该第一预配置的服务实例可以是针对基于互联网协议可扩展面向服务的中间件SOME/IP通信的服务实例，该第二预配置的服务实例可以是针对数据分发服务DDS通信的服务实例。
本申请实施例中，针对不同通信模式下的服务实例可以提前配置好不同的服务实例模板，这样在生成服务实例就可以根据不同的服务实例模板来生成服务实例并配置其属性信息，有助于提升配置的灵活性。
可选地，该每个服务实例的属性信息包括服务实例的标识信息、传输插件信息、部署信息、服务质量配置信息以及端到端通信保护信息中的一种或者多种。
图9示出了本申请实施例提供的配置装置900的示意性框图。如图9所示，该装置900包括：
配置单元910，用于配置n个进程，n≥1且n为整数。
映射单元920，用于将该n个进程中的m个进程映射到第一组件，0＜m≤n且m为整数，该第一组件关联第一端口。
生成单元930，用于根据预配置的关联关系，生成该m个进程对应的m个服务实例中每个服务实例到该第一端口的关联关系。
可选地，该预配置的关联关系中包括进程、端口和服务实例的引用信息以及进程、端口和服务实例之间的对应关系。
可选地，该生成单元930，还用于在生成该m个进程对应的m个服务实例中每个服务实例到该第一端口的关联关系之前，根据预配置的服务实例，生成该m个服务实例且配置该m个服务实例中的每个服务实例的属性信息。
可选地，该映射单元920具体用于：将该m个进程映射到第一可执行程序exe，该第一可执行程序exe的根组件为第一复合组件；创建该第一复合组件的第一子元素，该第一子元素的类型指向该第一组件。
可选地，该n大于等于2且该n个进程为接收端的进程。
可选地，该预配置的服务实例包括第一预配置的服务实例和第二预配置的服务实例，该第一预配置的服务实例为针对基于互联网协议可扩展面向服务的中间件SOME/IP通信的服务实例，该第二预配置的服务实例为针对数据分发服务DDS通信的服务实例。
可选地，该每个服务实例的属性信息包括服务实例的标识信息、传输插件信息、部署信息、服务质量配置信息以及端到端通信保护信息中的一种或者多种。
图10示出了本申请实施例提供的配置装置1000的示意性框图，该装置1000包括存储器1001，用于存储计算机指令；处理器1002，用于执行该存储器中存储的计算机指令，以使得该装置1000执行上述配置方法。
本申请实施例还提供了一种终端设备，该终端设备可以包括上述装置900或者装置1000。
本申请实施例还提供了一种计算机程序产品，所述计算机程序产品包括：计算机程序代码，当所述计算机程序代码在计算机上运行时，使得计算机执行上述车辆所执行的方法。
本申请实施例还提供了一种计算机可读介质，所述计算机可读介质存储有程序代码，当所述计算机程序代码在计算机上运行时，使得计算机执行上述方法。
在实现过程中，上述方法的各步骤可以通过处理器中的硬件的集成逻辑电路或者软件形式的指令完成。结合本申请实施例所公开的方法可以直接体现为硬件处理器执行完成，或者用处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器，闪存、只读存储器，可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器，处理器读取存储器中的信息，结合其硬件完成上述方法的步骤。为避免重复，这里不再详细描述。
应理解，本申请实施例中，该处理器可以为中央处理单元(central processing unit，CPU)，该处理器还可以是其他通用处理器、数字信号处理器(digital signal processor，DSP)、专用集成电路(application specific integrated circuit，ASIC)、现成可编程门阵列(field programmable gate array，FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件等。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。
还应理解，本申请实施例中，该存储器可以包括只读存储器和随机存取存储器，并向处理器提供指令和数据。
在本申请实施例中，“第一”、“第二”以及各种数字编号仅为描述方便进行的区分，并不用来限制本申请实施例的范围。例如，区分不同的管路、通孔等。
应理解，在本申请的各种实施例中，上述各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定，而不应对本申请实施例的实施过程构成任何限定。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以 硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(read-only memory，ROM)、随机存取存储器(random access memory，RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖。在本申请的保护范围之内。因此，本申请的保护范围应以所述权利要求的保护范围为准。

Claims (16)

  1. 一种配置方法，其特征在于，包括：
    配置n个进程，n≥1且n为整数；
    将所述n个进程中的m个进程映射到第一组件，0＜m≤n且m为整数，所述第一组件关联第一端口；
    根据预配置的关联关系，生成所述m个进程对应的m个服务实例中每个服务实例到所述第一端口的关联关系。
  2. 根据权利要求1所述的方法，其特征在于，所述预配置的关联关系中包括进程、端口和服务实例的引用信息以及进程、端口和服务实例之间的对应关系。
  3. 根据权利要求1或2所述的方法，其特征在于，所述生成所述m个进程对应的m个服务实例中每个服务实例到所述第一端口的关联关系之前，所述方法还包括：
    根据预配置的服务实例，生成所述m个服务实例且配置所述m个服务实例中的每个服务实例的属性信息。
  4. 根据权利要求1至3中任一项所述的方法，其特征在于，所述将所述n个进程中的m个进程映射到第一组件，包括：
    将所述m个进程映射到第一可执行程序exe，所述第一可执行程序exe的根组件为第一复合组件；
    创建所述第一复合组件的第一子元素，所述第一子元素的类型指向所述第一组件。
  5. 根据权利要求1至4中任一项所述的方法，其特征在于，所述n大于或者等于2且所述n个进程为接收端的进程。
  6. 根据权利要求1至5中任一项所述的方法，其特征在于，所述预配置的服务实例包括第一预配置的服务实例和第二预配置的服务实例，所述第一预配置的服务实例为针对基于互联网协议可扩展面向服务的中间件SOME/IP通信的服务实例，所述第二预配置的服务实例为针对数据分发服务DDS通信的服务实例。
  7. 根据权利要求1至6中任一项所述的方法，其特征在于，所述每个服务实例的属性信息包括服务实例的标识信息、传输插件信息、部署信息、服务质量配置信息以及端到端通信保护信息中的一种或者多种。
  8. 一种配置装置，其特征在于，包括：
    配置单元，用于配置n个进程，n≥1且n为整数；
    映射单元，用于将所述n个进程中的m个进程映射到第一组件，0＜m≤n且m为整数，所述第一组件关联第一端口；
    生成单元，用于根据预配置的关联关系，生成所述m个进程对应的m个服务实例中每个服务实例到所述第一端口的关联关系。
  9. 根据权利要求8所述的装置，其特征在于，所述预配置的关联关系中包括进程、端口和服务实例的引用信息以及进程、端口和服务实例之间的对应关系。
  10. 根据权利要求8或9所述的装置，其特征在于，所述生成单元，还用于在生成所述m个进程对应的m个服务实例中每个服务实例到所述第一端口的关联关系之前，根据 预配置的服务实例，生成所述m个服务实例且配置所述m个服务实例中的每个服务实例的属性信息。
  11. 根据权利要求8至10中任一项所述的装置，其特征在于，所述映射单元具体用于：
    将所述m个进程映射到第一可执行程序exe，所述第一可执行程序exe的根组件为第一复合组件；
    创建所述第一复合组件的第一子元素，所述第一子元素的类型指向所述第一组件。
  12. 根据权利要求8至11中任一项所述的装置，其特征在于，所述n大于等于2且所述n个进程为接收端的进程。
  13. 根据权利要求8至12中任一项所述的装置，其特征在于，所述预配置的服务实例包括第一预配置的服务实例和第二预配置的服务实例，所述第一预配置的服务实例为针对基于互联网协议可扩展面向服务的中间件SOME/IP通信的服务实例，所述第二预配置的服务实例为针对数据分发服务DDS通信的服务实例。
  14. 根据权利要求8至13中任一项所述的装置，其特征在于，所述每个服务实例的属性信息包括服务实例的标识信息、传输插件信息、部署信息、服务质量配置信息以及端到端通信保护信息中的一种或者多种。
  15. 一种配置装置，其特征在于，包括：
    存储器，用于存储计算机指令；
    处理器，用于执行所述存储器中存储的计算机指令，以使得所述装置执行如权利要求1至7中任一项所述的方法。
  16. 一种计算机可读存储介质，其特征在于，所述计算机可读介质存储有程序代码，当所述程序代码在计算机上运行时，使得计算机执行如权利要求1至7中任意一项所述的方法。
PCT/CN2021/126979 2021-10-28 2021-10-28 一种配置方法和装置 WO2023070426A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2021/126979 WO2023070426A1 (zh) 2021-10-28 2021-10-28 一种配置方法和装置

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2021/126979 WO2023070426A1 (zh) 2021-10-28 2021-10-28 一种配置方法和装置

Publications (1)

Publication Number Publication Date
WO2023070426A1 true WO2023070426A1 (zh) 2023-05-04

Family

ID=86158827

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/126979 WO2023070426A1 (zh) 2021-10-28 2021-10-28 一种配置方法和装置

Country Status (1)

Country Link
WO (1) WO2023070426A1 (zh)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20170337152A1 (en) * 2016-05-17 2017-11-23 Microsemi Storage Solutions (U.S.), Inc. Port mirroring for peripheral component interconnect express devices
CN111130838A (zh) * 2019-10-17 2020-05-08 国电南瑞科技股份有限公司 一种进程级服务实例动态扩展及网络带宽限制方法及装置
CN111880810A (zh) * 2020-07-28 2020-11-03 苏州浪潮智能科技有限公司 一种服务实例部署方法、装置及电子设备和存储介质
CN112783518A (zh) * 2021-01-26 2021-05-11 电子科技大学 一种基于ipfs的车载应用容器化隔离的框架系统及实现方法

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20170337152A1 (en) * 2016-05-17 2017-11-23 Microsemi Storage Solutions (U.S.), Inc. Port mirroring for peripheral component interconnect express devices
CN111130838A (zh) * 2019-10-17 2020-05-08 国电南瑞科技股份有限公司 一种进程级服务实例动态扩展及网络带宽限制方法及装置
CN111880810A (zh) * 2020-07-28 2020-11-03 苏州浪潮智能科技有限公司 一种服务实例部署方法、装置及电子设备和存储介质
CN112783518A (zh) * 2021-01-26 2021-05-11 电子科技大学 一种基于ipfs的车载应用容器化隔离的框架系统及实现方法

Similar Documents

Publication Publication Date Title
CN111385191B (zh) 车载互联网关、车辆ota升级系统和方法、计算机存储介质
US11972247B2 (en) Software upgrading method, apparatus, and system
US20230289174A1 (en) Vehicle upgrade method and apparatus
CN107371219B (zh) WiFi配置方法、WiFi移动终端和WiFi设备
WO2021129065A1 (zh) 升级方法及装置
US11917018B2 (en) Broker-based bus protocol and multi-client architecture
CN103513998A (zh) 升级包生成方法和装置、动态文件差分升级的方法和终端
US20160173330A1 (en) Method and apparatus for controlling audio/video bridging stream for in-vehicle ethernet
KR101923511B1 (ko) 차량 진단 통신 장치 및 그 방법
CN114545906B (zh) 车载以太网网关及车辆
WO2021057802A1 (zh) 管理das系统的方法和设备、电子设备、存储介质
WO2024008104A1 (zh) 远程升级方法及系统
KR20200075626A (ko) 차량의 ecu 업데이트가 가능한 무선 업데이트 시스템 및 방법
WO2023070426A1 (zh) 一种配置方法和装置
CN105635312A (zh) 基于WinCE系统单网卡实现多局域网络通信的方法
CN111461718A (zh) 区块链节点的接入方法、装置及系统
WO2022148302A1 (zh) 一种信息交互方法、系统、设备及计算机可读存储介质
CN111404793B (zh) 一种控制物理can口和虚拟can口进行映射的方法，系统，设备及可读存储介质
CN113794591A (zh) 采集协议的配置方法、装置和电子设备
CN110971716B (zh) 地址配置方法、装置、系统和计算机可读存储介质
CN104753708A (zh) 启动客户端的配置系统及方法
CN113076128B (zh) 用于机器人配置的方法、装置、电子设备及存储介质
US20220398106A1 (en) Computer Implemented Method And Distributed Computing Infrastructure For Automated Plug And Play Configuration
EP4350511A1 (en) Method and apparatus for co-simulation
WO2023201558A1 (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: 21961793

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 2021961793

Country of ref document: EP

ENP Entry into the national phase

Ref document number: 2021961793

Country of ref document: EP

Effective date: 20240506