Electronic and electrical conflict processing method, device, equipment, medium and product

Abstract

This invention discloses a method, apparatus, device, medium, and product for handling electronic and electrical conflicts, relating to the technical field of intelligent connected vehicle electronic and electrical architecture and in-vehicle software architecture. The method includes: acquiring multi-source input data; normalizing the multi-source input data to obtain a set of service entity objects; performing conflict detection on the set of service entity objects according to conflict rules to obtain conflict detection results; determining a new allocation result based on the conflict detection results and the set of service entity objects; the new allocation result being an updated port / instance / routing allocation result from the service provider to the consumer; and generating and writing back the configuration based on the new allocation result. The above technical solution can improve the efficiency and effectiveness of conflict detection and handling.

Description

Technical Field

[0001] This invention relates to the field of intelligent connected vehicle electronic and electrical architecture and vehicle software architecture technology, and in particular to a method, apparatus, device, medium and product for handling electronic and electrical conflicts. Background Technology

[0002] The electronic and electrical architecture of intelligent connected vehicles is evolving from traditional distributed systems to domain-centralized systems with central computing and regional control. With the widespread application of in-vehicle SOA (Adaptive AUTOSAR, SOME / IP / DDS) and multi-protocol converged networks (CAN FD, TSN, in-vehicle Ethernet), the system exhibits characteristics of dynamic services, cross-domain collaboration, and stringent real-time and functional safety requirements. Therefore, identifying cross-domain / cross-ECU port and instance conflicts in configuration files before submission / merging is crucial for vehicle service integration. Summary of the Invention

[0003] This invention provides a method, apparatus, device, medium, and product for handling electronic and electrical conflicts, in order to improve the efficiency of conflict detection and the effectiveness of conflict handling.

[0004] According to one aspect of the present invention, a conflict resolution method for electronic and electrical systems is provided, the method comprising: Acquire multi-source input data; the multi-source input data includes at least two of the following: vehicle-mounted embedded configuration description file, service interface method or event, network information, security domain policy, and gateway routing mapping. The multi-source input data is normalized to obtain a set of service entity objects; Conflict detection is performed on the set of service entity objects according to the conflict rules to obtain the conflict detection results; Based on the conflict detection results and the set of service entity objects, a new allocation result is determined; the new allocation result is the updated port / instance / routing allocation result from the service provider to the consumer. Based on the new allocation results, configuration generation and write-back are performed.

[0005] According to another aspect of the present invention, a conflict resolution apparatus for electronic and electrical systems is provided, the apparatus comprising: A multi-source data acquisition module is used to acquire multi-source input data; the multi-source input data includes at least two of the following: vehicle embedded configuration description file, service interface method or event, network information, security domain policy, and gateway routing mapping; The data normalization module is used to normalize the multi-source input data to obtain a set of service entity objects; The conflict detection module is used to perform conflict detection on the set of service entity objects according to conflict rules and obtain conflict detection results. The reallocation module is used to determine a new allocation result based on the conflict detection result and the set of service entity objects; the new allocation result is the updated port / instance / routing allocation result of the service from the provider to the consumer; The configuration rewrite module is used to generate and write back the configuration based on the new allocation result.

[0006] According to another aspect of the present invention, an electronic device is provided, the electronic device comprising: At least one processor; and A memory communicatively connected to the at least one processor; wherein, The memory stores a computer program that can be executed by the at least one processor, the computer program being executed by the at least one processor to enable the at least one processor to perform the electronic and electrical conflict resolution method according to any embodiment of the present invention.

[0007] According to another aspect of the present invention, a computer-readable storage medium is provided, the computer-readable storage medium storing computer instructions for causing a processor to execute and implement the electronic and electrical conflict resolution method described in any embodiment of the present invention.

[0008] According to another aspect of the present invention, a computer program product is provided, the computer program product comprising a computer program that, when executed by a processor, implements the electronic and electrical conflict resolution method according to any embodiment of the present invention.

[0009] The technical solution of this invention involves acquiring multi-source input data, including at least two of the following: an in-vehicle embedded configuration description file, a service interface method or event, network information, a security domain policy, and a gateway routing map. The multi-source input data is normalized to obtain a set of service entity objects. Conflict detection is performed on the set of service entity objects according to conflict rules to obtain conflict detection results. A new allocation result is determined based on the conflict detection results and the set of service entity objects. The new allocation result is the updated port / instance / route allocation result from the service provider to the consumer. Configuration generation and write-back are then performed based on the new allocation result. This technical solution, by modeling ports / instances / routes as a unified constraint system, detects conflicts and automatically allocates them under a "global view," and generates and writes back the configuration. This not only improves conflict detection efficiency but also enhances the reassignment effect of ports / instances / routes.

[0010] It should be understood that the description in this section is not intended to identify key or essential features of the embodiments of the present invention, nor is it intended to limit the scope of the invention. Other features of the invention will become readily apparent from the following description. Attached Figure Description

[0011] To more clearly illustrate the technical solutions in the embodiments of the present invention, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0012] Figure 1 This is a flowchart of a conflict resolution method for electronic and electrical systems provided according to an embodiment of the present invention; Figure 2 This is a flowchart of a conflict resolution method for electronic and electrical systems provided according to an embodiment of the present invention; Figure 3 This is a schematic diagram of the structure of a conflict resolution device for electronic and electrical applications according to an embodiment of the present invention; Figure 4 This is a schematic diagram of the structure of an electronic device that implements the electronic conflict resolution method of the present invention. Detailed Implementation

[0013] To enable those skilled in the art to better understand the present invention, the technical solutions of the present invention will be clearly and completely described below with reference to the accompanying drawings of the embodiments of the present invention. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort should fall within the scope of protection of the present invention.

[0014] It should be noted that the terms "first," "second," etc., in the specification, claims, and accompanying drawings of this invention are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of the invention described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0015] Furthermore, it should be noted that the information collected in the technical solution of this invention is information and data authorized by the user or fully authorized by all parties, and the collection, storage, use, processing, transmission, provision, disclosure and application of related data all comply with the relevant laws, regulations and standards of relevant countries and regions, necessary confidentiality measures have been taken, and public order and good morals are not violated. Corresponding operation entry points are provided for users to choose to authorize or refuse.

[0016] Figure 1 This is a flowchart illustrating a conflict resolution method for electronic and electrical systems according to an embodiment of the present invention. This embodiment is applicable to port / instance conflict detection and automatic allocation in electronic and electrical architectures, particularly in service-oriented architectures (SOA) for vehicles. The method can be executed by an electronic and electrical conflict resolution device, which can be implemented in hardware and / or software. This device can be configured in an electronic device carrying electronic and electrical conflict resolution functions, such as a server. Figure 1 As shown, the method includes: S110, Obtain multi-source input data.

[0017] In this embodiment, multi-source input data refers to the data involved in the service from the provider to the consumer in the in-vehicle SOA. Optionally, multi-source input data includes at least two of the following: in-vehicle embedded configuration description file, service interface method or event, network information, security domain policy, and gateway routing mapping. Among them, the in-vehicle embedded configuration description file is AUTOSAR ARXML, including SoAd / SomeIp / Service Interface / Deployment, etc.; the service interface method or event is ARA::COM / IDL; the network information includes network segment / VLAN / subnet table; the security domain policy refers to the set of rules of network security devices (such as firewalls) based on security domain division to implement access control, security inspection and behavior control of network traffic between different security domains, including allow / prohibit communication relationships; the gateway routing mapping refers to the address and port mapping rules on the gateway device (router, firewall, API gateway) to accurately forward external requests to internal target services / devices according to rules, including the forwarding table required for cross-domain communication.

[0018] S120. Normalize the multi-source input data to obtain a set of service entity objects.

[0019] In this embodiment, the service entity object set refers to the normalized multi-source input data. Optionally, the service entity object set includes multiple entity objects, such as serviceId, instanceId, role, electronic control unit (ECU), domain, virtual local area network (VLAN), security domain, protocol, IP address, port, endpoint / interface address, and routePath.

[0020] Specifically, the multi-source input data is normalized to obtain a set of service entity objects, such as ServiceEntity{serviceId, instanceId, role(provider / consumer), ecu,domain, vlan, securityDomain, protocol, ip, port, endpoint, routePath…}.

[0021] S130. Perform conflict detection on the set of service entity objects according to the conflict rules, and obtain the conflict detection results.

[0022] In this embodiment, conflict rules refer to rules used for conflict detection; optionally, they include, but are not limited to, port conflicts within the same scope, endpoint conflicts within the same scope, instance conflicts within the same service, reserved port conflicts, and routing black holes; among them, port conflicts within the same scope refer to two providers or provider / consumer claims for the same port that do not meet the takeover conditions; endpoint conflicts within the same scope refer to duplicate IP:ports but inconsistent services / instances; instanceId conflicts within the same service refer to multiple providers claiming the same instance; reserved port conflicts refer to ports falling within a disabled port / system reserved segment; routing black holes refer to routes from consumer to provider (consumer->provider) being unreachable, i.e., missing routes / ACL blocking / security domain disallowing.

[0023] The so-called conflict detection result refers to the result after performing conflict detection on ports, instances, etc.; including but not limited to the conflict list and the source file / line / object path of each conflict; among which, the conflict list includes port conflicts, instance conflicts, server endpoint conflicts, routing black holes, etc.

[0024] An alternative approach is to perform conflict checks on each entity object in the service entity object set based on conflict rules to obtain conflict detection results.

[0025] Another optional approach is to perform conflict detection on the set of service entity objects according to conflict rules to obtain conflict detection results, including: grouping the set of service entity objects to obtain at least one conflict scope; in each conflict scope, combining the reserved port table, port pool range, gateway route mapping, access control list (ACL), and security domain policy, to perform conflict detection on the service entity objects in the conflict scope to obtain conflict detection results; wherein, the conflict detection results include port conflicts, instance conflicts, service conflicts, or route black holes.

[0026] Specifically, the service entity object set can be grouped according to network segment / subnet or VLAN, security domain, and transport protocol, and further, ECU / domain can be added to obtain at least one conflict scope. Then, within the same conflict scope, the port declarations, endpoint declarations, and instance declarations of provider / provider and provider / consumer are compared item by item based on the conflict rules. At the same time, the reserved port table, port pool range, gateway route mapping, ACL, and security domain policy in the conflict rules are combined to determine whether there are port conflicts, endpoint conflicts, instanceId conflicts, reserved port conflicts, and route black holes. Finally, the conflict list is output, and the source file, line number, and object path are located.

[0027] Understandably, by performing uniqueness and reuse rule checks on ports / endpoints within the conflict domain, cross-domain conflict detection can be avoided due to "single ECU / single file" checks alone, thus improving conflict detection efficiency.

[0028] It should be noted that mapping the conflict to the "domain-ECU-network segment-security domain-gateway" topology diagram and locating the specific configuration item / file path significantly reduces the troubleshooting cost.

[0029] S140. Based on the conflict detection results and the set of service entity objects, determine the new allocation result.

[0030] In this embodiment, the new allocation result is the updated port / instance / routing allocation result from the service provider to the consumer.

[0031] Specifically, to avoid conflicts in the conflict detection results, the port instances of the service entity object set are reassigned to obtain a new allocation result.

[0032] S150. Based on the new allocation results, generate and write back the configuration.

[0033] An optional approach is to generate and write back the configuration based on the new allocation result, including: regenerating the configuration file based on the new allocation result.

[0034] Another optional approach is to generate and write back the configuration based on the new allocation result, including: comparing the differences between the new allocation result and the original allocation result to obtain difference data; generating difference patches based on the difference data; and writing back the difference patches to the target workpiece.

[0035] The original allocation result refers to the original port / instance / route allocation result from the service provider to the consumer; including but not limited to ARXML, SoAd, ARA::COM / IDL, and routing configurations. The target artifact refers to the configuration file body that needs to be rewritten or written back, including ARXML, SoAd, ARA::COM / IDL, and routing configuration files, etc.

[0036] Specifically, the differences between the new allocation result and the original allocation result are compared one by one to obtain the difference data. Then, based on the difference data, the corresponding configuration patch, allocation table and original configuration backup are generated. Finally, the patch is written back to the target artifact, and a revocable rollback package and CI access control result are generated simultaneously.

[0037] Understandably, by generating and writing back differential patches for ARXML / SoAd / ARA::COM / IDL / routing configurations, and simultaneously generating rollback information (baseline / patch reversal), not only are the risks of changes reduced, but closed-loop governance of the project can also be supported.

[0038] Furthermore, it should be noted that risk levels can be categorized based on the type of conflict, the scope of impact, and whether it involves published services. High-risk scenarios can be directly blocked, while medium- and low-risk scenarios can be alerted or automatically patched, thus achieving CI access control integration.

[0039] The technical solution of this invention involves acquiring multi-source input data, including at least two of the following: an in-vehicle embedded configuration description file, a service interface method or event, network information, a security domain policy, and a gateway routing map. The multi-source input data is normalized to obtain a set of service entity objects. Conflict detection is performed on the set of service entity objects according to conflict rules to obtain conflict detection results. A new allocation result is determined based on the conflict detection results and the set of service entity objects. The new allocation result is the updated port / instance / route allocation result from the service provider to the consumer. Configuration generation and write-back are then performed based on the new allocation result. This technical solution, by modeling ports / instances / routes as a unified constraint system, detects conflicts and automatically allocates them under a "global view," and generates and writes back the configuration. This not only improves conflict detection efficiency but also enhances the reassignment effect of ports / instances / routes.

[0040] Figure 2 This is a flowchart of a conflict resolution method for electronic and electrical systems according to an embodiment of the present invention. Based on the above embodiments, this embodiment further optimizes the step of "determining a new allocation result based on the conflict detection result and the set of service entity objects," providing an optional implementation scheme. For example... Figure 2 As shown, the method includes: S210, Obtain multi-source input data.

[0041] The multi-source input data includes at least two of the following: vehicle-embedded configuration description file, service interface methods or events, network information, security domain policies, and gateway routing mappings.

[0042] S220. Normalize the multi-source input data to obtain a set of service entity objects.

[0043] S230. Perform conflict detection on the set of service entity objects according to the conflict rules, and obtain the conflict detection results.

[0044] S240. Based on the conflict detection results and the set of service entity objects, determine the new allocation result.

[0045] The new allocation result is the updated port / instance / route allocation result from the service provider to the consumer.

[0046] S250. Based on the new allocation results, generate and write back the configuration.

[0047] An optional approach involves determining a new allocation result based on conflict detection results and a set of service entity objects, including: determining a set of objects to be allocated based on conflict detection results; constructing object variables for each object in the set of objects to be allocated; the object variables include port variables, instance variables, and routing variables; constructing allocation hard constraints based on the object variables, the port pools and / or instance number ranges corresponding to each scope, and the gateway routing mappings and security domain policies in the set of service entity objects; and performing object reallocation based on the set of service object entities, the allocation hard constraints, and the soft constraints to obtain a new allocation result.

[0048] The set of objects to be allocated includes conflicting entity objects and conflict-related providers / consumers. Hard allocation constraints include port uniqueness constraints within the same scope, port pool range constraints, instance uniqueness constraints within the same service, reachability constraints, and security domain communication allowance constraints. Soft constraints are equivalent to the objective function of the reallocation.

[0049] Specifically, objects involving port conflicts, instance conflicts, endpoint conflicts, or routing black holes are selected from the conflict list in the conflict detection results. These objects, along with their directly associated providers / consumers, are included in the set of objects to be assigned. Then, object variables are created for each object in the set: port variable `port_i`, instance variable `instance_i`, and route variable `route_i`. Based on constraint construction rules, hard constraints for allocation are constructed according to the object variables, the port pools and / or instance number ranges corresponding to each scope, and the gateway routing mapping and security domain policies in the service entity object set. The constraint construction rules can be configured based on business scenario requirements. Soft constraints are also determined, such as ensuring that reassignment does not change the port / instance as much as possible. Finally, the input solvers of the service object entity set, hard constraints, and soft constraints are used to reassign ports and instances, outputting the new allocation results. The solvers include Integer Linear Programming (ILP), Constraint Satisfaction Problem Solver (CSP), and heuristic backtracking methods.

[0050] Understandably, by building soft and hard constraints, communication costs can be reduced by automatically allocating resources, minimizing manual maintenance of port tables and redundant alignment, and improving the efficiency of parallel development.

[0051] An optional approach involves constructing allocation hard constraints based on object variables, port pools and / or instance number ranges corresponding to each scope, and gateway routing mappings and security domain policies in the service entity object set. This includes: constructing port uniqueness constraints within the same scope, port pool range constraints, and instance uniqueness constraints under the same service based on object variables, port pools and / or instance number ranges corresponding to each scope; determining reachability constraints from the consumer to the provider based on gateway routing mappings; and determining security domain-permitted communication constraints between the consumer and the provider based on security domain policies.

[0052] Specifically, based on object variables, port pools corresponding to each scope, and / or instance number ranges, a port uniqueness constraint within the same scope is constructed, represented as port_i != port_j; a port pool range constraint is represented as port_i ∈ PortPool(scope, domain, ecu); and an instance uniqueness constraint under the same service is represented as instance_i != instance_j; based on gateway routing mapping, a reachability constraint from the consumer to the provider is determined, i.e., for any consumer_i, there must exist a valid route path routePath to the corresponding provider_j; based on security domain policies, a security domain allowed communication constraint is determined between the consumer and the provider, i.e., the communication relationship between the security domain to which the consumer_i belongs and the security domain to which the provider_j belongs must exist in the allowed communication policy table.

[0053] Understandably, by modeling ports, instance IDs, endpoints, and route reachability and security domain policies as a unified constraint satisfaction problem, and incorporating reachability and policies into hard constraints, the integration problem of "correct configuration but inability to communicate" can be reduced.

[0054] An alternative approach, soft constraints, includes: minimizing the penalty for changing object variables; minimizing the allocation span of object variables; prioritizing the use of recommended segments for object variable allocation; recommended segments include recommended port segments, recommended security domains, or recommended routing gateways.

[0055] Specifically, soft constraints should be determined, including: minimizing the loss of changes to object variables corresponding to published services; minimizing changes to ports / instances of published services to achieve minimal disturbance; minimizing the allocation span of object variables, i.e., keeping ports as compact as possible; and prioritizing the use of recommended segments for the allocation of object variables, such as a certain segment and a fixed segment like 31xxx.

[0056] Understandably, by setting soft constraints to minimize disturbances and prioritize stabilizing published service ports / instances, it is possible to reduce upgrade risks and minimize the impact of online changes.

[0057] It should be noted that this invention does not allocate ports, instances, and routes separately. Instead, it integrates ports, instance IDs, endpoints, route reachability, and security domain policies into a single constraint model for simultaneous solution. In other words, a change in a provider's port will simultaneously constrain the endpoint binding and route reachability conditions on the consumer side. The solver outputs a set of consistent overall allocation results, rather than independent local modification results.

[0058] Furthermore, it should be noted that when the solution fails, the output includes the minimum set of conflicting objects that cause the unsolvable problem, along with the corresponding constraints, which can be used as a basis for manual adjustment.

[0059] The technical solution of this invention involves acquiring multi-source input data, including at least two of the following: an in-vehicle embedded configuration description file, a service interface method or event, network information, a security domain policy, and a gateway routing map. The multi-source input data is normalized to obtain a set of service entity objects. Conflict detection is performed on the set of service entity objects according to conflict rules to obtain conflict detection results. A new allocation result is determined based on the conflict detection results and the set of service entity objects. The new allocation result is the updated port / instance / route allocation result from the service provider to the consumer. Configuration generation and write-back are then performed based on the new allocation result. This technical solution, by modeling ports / instances / routes as a unified constraint system, detects conflicts and automatically allocates them under a "global view," and generates and writes back the configuration. This not only improves conflict detection efficiency but also enhances the reassignment effect of ports / instances / routes.

[0060] In this invention, network segment mappings, VLANs, port pools, instance number ranges, gateway routing templates, and security policy sets in different environments are first abstracted into an environment parameter set. When performing detection and allocation, the unified entity model and constraint structure are not changed; only the parameter set corresponding to the current environment is replaced. Then, the port, instance, and route allocation results are recalculated under the same set of rules and solution process. Finally, the consistency of the results in each environment is compared to check whether the service, instance, endpoint, and route path meet the preset mapping relationship. The allocation is recalculated and the consistency is verified under the same constraint model, avoiding environment drift caused by multiple configuration files, thereby achieving multi-environment switching and consistency guarantee.

[0061] Figure 3 This is a schematic diagram of a conflict resolution device for electronic and electrical systems according to an embodiment of the present invention. This embodiment is applicable to port / instance conflict detection and automatic allocation in electronic and electrical architectures, especially in automotive service-oriented architectures (SOA). This conflict resolution device for electronic and electrical systems can be implemented in hardware and / or software, and can be configured in electronic devices that carry out conflict resolution functions for electronic and electrical systems, such as servers. Figure 3 As shown, the device includes: The multi-source data acquisition module 310 is used to acquire multi-source input data; the multi-source input data includes at least two of the following: vehicle-mounted embedded configuration description file, service interface method or event, network information, security domain policy and gateway routing mapping. The data normalization module 320 is used to normalize multi-source input data to obtain a set of service entity objects; The conflict detection module 330 is used to perform conflict detection on the set of service entity objects according to conflict rules and obtain the conflict detection results. The reallocation module 340 is used to determine the new allocation result based on the conflict detection result and the set of service entity objects; the new allocation result is the updated port / instance / routing allocation result of the service from the provider to the consumer; The configuration rewrite module 350 is used to generate and write back the configuration based on the new allocation results.

[0062] The technical solution of this invention involves acquiring multi-source input data, including at least two of the following: an in-vehicle embedded configuration description file, a service interface method or event, network information, a security domain policy, and a gateway routing map. The multi-source input data is normalized to obtain a set of service entity objects. Conflict detection is performed on the set of service entity objects according to conflict rules to obtain conflict detection results. A new allocation result is determined based on the conflict detection results and the set of service entity objects. The new allocation result is the updated port / instance / route allocation result from the service provider to the consumer. Configuration generation and write-back are then performed based on the new allocation result. This technical solution, by modeling ports / instances / routes as a unified constraint system, detects conflicts and automatically allocates them under a "global view," and generates and writes back the configuration. This not only improves conflict detection efficiency but also enhances the reassignment effect of ports / instances / routes.

[0063] Optionally, the collision detection module 330 is used for: Group the set of service entity objects to obtain at least one conflict scope; Within each conflict scope, conflict detection is performed on the service entity objects in the conflict scope by combining the reserved port table, port pool range, gateway route mapping, access control list (ACL), and security domain policy, and the conflict detection results are obtained. Among them, the conflict detection results include port conflict, instance conflict, service conflict, or route black hole.

[0064] Optionally, the redistribution module 340 is used for: The set of objects to be assigned is determined based on the conflict detection results; For each object to be assigned in the set of objects to be assigned, construct object variables; object variables include port variables, instance variables, and route variables; Based on object variables, port pools and / or instance number ranges corresponding to each scope, gateway routing mappings and security domain policies in the service entity object set, construct allocation hard constraints; Based on the set of service object entities, hard constraints, and soft constraints, objects are reassigned to obtain new assignment results.

[0065] Optionally, the redistribution module 340 is used for: Object variables, port pools and / or instance number ranges corresponding to each scope, construct port uniqueness constraints within the same scope, port pool range constraints, and instance uniqueness constraints under the same service; Based on the gateway routing map, determine the reachability constraints from the consumer to the provider; Based on the security domain policy, determine the security domain-permitted communication constraints between the consumer and the provider.

[0066] Optional, soft constraints include: Changes to object variables incur minimal penalty; Object variables have the smallest allocation span; The allocation of object variables should preferentially use the recommended segments; the recommended segments include recommended port segments, recommended security domains, or recommended routing gateways.

[0067] Optionally, the configuration rewrite module 350 is used for: The differences between the new allocation results and the original allocation results are compared to obtain the difference data. Generate difference patches based on the difference data; Write the difference patch back to the target artifact.

[0068] The electronic and electrical conflict resolution apparatus provided in the embodiments of the present invention can execute the electronic and electrical conflict resolution method provided in any embodiment of the present invention, and has the corresponding functional modules and beneficial effects of the method execution.

[0069] According to embodiments of the present invention, the present invention also provides an electronic device, a readable storage medium, and a computer program product.

[0070] Figure 4 This is a schematic diagram of the structure of an electronic device that implements the electronic conflict resolution method of the present invention. Figure 4 A schematic diagram of an electronic device 10 that can be used to implement embodiments of the present invention is shown. The electronic device is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device can also represent various forms of mobile devices, such as personal digital assistants, cellular phones, smartphones, wearable devices (e.g., helmets, glasses, watches, etc.), and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely illustrative and are not intended to limit the implementation of the invention described and / or claimed herein.

[0071] like Figure 4As shown, the electronic device 10 includes at least one processor 11 and a memory, such as a read-only memory (ROM) 12 or a random access memory (RAM) 13, communicatively connected to the at least one processor 11. The memory stores computer programs executable by the at least one processor. The processor 11 can perform various appropriate actions and processes based on the computer program stored in the ROM 12 or loaded from storage unit 18 into the RAM 13. The RAM 13 can also store various programs and data required for the operation of the electronic device 10. The processor 11, ROM 12, and RAM 13 are interconnected via a bus 14. An input / output (I / O) interface 15 is also connected to the bus 14.

[0072] Multiple components in electronic device 10 are connected to I / O interface 15, including: input unit 16, such as keyboard, mouse, etc.; output unit 17, such as various types of displays, speakers, etc.; storage unit 18, such as disk, optical disk, etc.; and communication unit 19, such as network card, modem, wireless transceiver, etc. Communication unit 19 allows electronic device 10 to exchange information / data with other devices through computer networks such as the Internet and / or various telecommunications networks.

[0073] Processor 11 can be a variety of general-purpose and / or special-purpose processing components with processing and computing capabilities. Some examples of processor 11 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various special-purpose artificial intelligence (AI) computing chips, various processors running machine learning model algorithms, a digital signal processor (DSP), and any suitable processor, controller, microcontroller, etc. Processor 11 performs the various methods and processes described above, such as electronic and electrical conflict resolution methods.

[0074] In some embodiments, the electrical-electronic conflict resolution method may be implemented as a computer program tangibly contained in a computer-readable storage medium, such as storage unit 18. In some embodiments, part or all of the computer program may be loaded and / or installed on the electronic device 10 via ROM 12 and / or communication unit 19. When the computer program is loaded into RAM 13 and executed by processor 11, one or more steps of the electrical-electronic conflict resolution method described above may be performed. Alternatively, in other embodiments, processor 11 may be configured to perform the electrical-electronic conflict resolution method by any other suitable means (e.g., by means of firmware).

[0075] Various implementations of the systems and techniques described above herein can be implemented in digital electronic circuit systems, integrated circuit systems, field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), application-specific standard products (ASSPs), systems-on-a-chip (SoCs), complex programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various implementations may include: implementations in one or more computer programs that can be executed and / or interpreted on a programmable system including at least one programmable processor, which may be a dedicated or general-purpose programmable processor, capable of receiving data and instructions from a storage system, at least one input device, and at least one output device, and transmitting data and instructions to the storage system, the at least one input device, and the at least one output device.

[0076] Computer programs used to implement the methods of the present invention may be written in any combination of one or more programming languages. These computer programs may be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device, such that when executed by the processor, the computer programs cause the functions / operations specified in the flowcharts and / or block diagrams to be performed. The computer programs may be executed entirely on a machine, partially on a machine, or as a standalone software package, partially on a machine and partially on a remote machine, or entirely on a remote machine or server.

[0077] In the context of this invention, a computer-readable storage medium can be a tangible medium that may contain or store a computer program for use by or in conjunction with an instruction execution system, apparatus, or device. A computer-readable storage medium may include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination thereof. Alternatively, a computer-readable storage medium may be a machine-readable signal medium. More specific examples of machine-readable storage media include electrical connections based on one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fibers, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof.

[0078] To provide interaction with a user, the systems and techniques described herein can be implemented on an electronic device having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to the user; and a keyboard and pointing device (e.g., a mouse or trackball) through which the user provides input to the electronic device. Other types of devices can also be used to provide interaction with the user; for example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form (including sound input, voice input, or tactile input).

[0079] The systems and technologies described herein can be implemented in computing systems that include backend components (e.g., as data servers), or computing systems that include middleware components (e.g., application servers), or computing systems that include frontend components (e.g., user computers with graphical user interfaces or web browsers through which users can interact with implementations of the systems and technologies described herein), or any combination of such backend, middleware, or frontend components. The components of the system can be interconnected via digital data communication of any form or medium (e.g., communication networks). Examples of communication networks include local area networks (LANs), wide area networks (WANs), blockchain networks, and the Internet.

[0080] A computing system can include clients and servers. Clients and servers are generally geographically separated and typically interact via communication networks. The client-server relationship is created by computer programs running on the respective computers and having a client-server relationship with each other. The server can be a cloud server, also known as a cloud computing server or cloud host, which is a host product within the cloud computing service system. This addresses the shortcomings of traditional physical hosts and virtual private servers, such as high management difficulty and weak business scalability.

[0081] It should be understood that the various forms of processes shown above can be used, with steps reordered, added, or deleted. For example, the steps described in this invention can be executed in parallel, sequentially, or in different orders, as long as the desired result of the technical solution of this invention can be achieved, and this is not limited herein.

[0082] The specific embodiments described above do not constitute a limitation on the scope of protection of this invention. Those skilled in the art should understand that various modifications, combinations, sub-combinations, and substitutions can be made according to design requirements and other factors. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of this invention should be included within the scope of protection of this invention.

Claims

1. A conflict resolution method for electronic and electrical systems, characterized in that, include: Acquire multi-source input data; The multi-source input data includes at least two of the following: vehicle-embedded configuration description file, service interface method or event, network information, security domain policy, and gateway routing mapping. The multi-source input data is normalized to obtain a set of service entity objects; Conflict detection is performed on the set of service entity objects according to the conflict rules to obtain the conflict detection results; Based on the conflict detection results and the set of service entity objects, a new allocation result is determined; The new allocation result is the updated port / instance / routing allocation result from the service provider to the consumer; Based on the new allocation results, configuration generation and write-back are performed.

2. The method according to claim 1, characterized in that, Conflict detection is performed on the set of service entity objects according to conflict rules to obtain conflict detection results, including: The set of service entity objects is grouped to obtain at least one conflict scope; In each conflict scope, by combining the reserved port table, port pool range, gateway route mapping, access control list (ACL), and security domain policy, conflict detection is performed on the service entity objects in the conflict scope to obtain the conflict detection results; wherein, the conflict detection results include port conflict, instance conflict, service conflict, or route black hole.

3. The method according to claim 1, characterized in that, Based on the conflict detection results and the set of service entity objects, a new allocation result is determined, including: The set of objects to be assigned is determined based on the conflict detection results; For each object to be assigned in the set of objects to be assigned, construct object variables; the object variables include port variables, instance variables, and routing variables; Based on the object variables, the port pools and / or instance number ranges corresponding to each scope, and the gateway routing mappings and security domain policies in the service entity object set, construct allocation hard constraints; Based on the set of service object entities, the hard and soft constraints of the allocation, the objects are reassigned to obtain a new allocation result.

4. The method according to claim 3, characterized in that, Based on the object variables, the port pools and / or instance number ranges corresponding to each scope, and the gateway routing mappings and security domain policies in the service entity object set, a hard constraint for allocation is constructed, including: The object variables, port pools and / or instance number ranges corresponding to each scope are used to construct port uniqueness constraints within the same scope, port pool range constraints, and instance uniqueness constraints under the same service. Based on the gateway routing map, determine the reachability constraints from the consumer to the provider; Based on the security domain policy, determine the security domain-permitted communication constraints between the consumer and the provider.

5. The method according to claim 3, characterized in that, The soft constraints include: The loss from changing the object variable is minimal; The allocation span of the object variables is the smallest; The allocation of the object variables preferentially uses the recommended segments; the recommended segments include recommended port segments, recommended security domains, or recommended routing gateways.

6. The method according to claim 1, characterized in that, Based on the new allocation results, configuration generation and write-back are performed, including: The differences between the new allocation results and the original allocation results are compared to obtain the difference data. Generate difference patches based on the difference data; The difference patch is written back to the target artifact.

7. A conflict resolution device for electronic and electrical systems, characterized in that, include: A multi-source data acquisition module is used to acquire multi-source input data; the multi-source input data includes at least two of the following: vehicle embedded configuration description file, service interface method or event, network information, security domain policy, and gateway routing mapping; The data normalization module is used to normalize the multi-source input data to obtain a set of service entity objects; The conflict detection module is used to perform conflict detection on the set of service entity objects according to conflict rules and obtain conflict detection results. The reallocation module is used to determine a new allocation result based on the conflict detection result and the set of service entity objects; The new allocation result is the updated port / instance / routing allocation result from the service provider to the consumer; The configuration rewrite module is used to generate and write back the configuration based on the new allocation result.

8. An electronic device, characterized in that, The electronic device includes: At least one processor; and A memory communicatively connected to the at least one processor; wherein, The memory stores a computer program that can be executed by the at least one processor, the computer program being executed by the at least one processor to enable the at least one processor to perform the electronic and electrical conflict resolution method according to any one of claims 1-6.

9. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer instructions that, when executed by a processor, implement the electronic and electrical conflict resolution method according to any one of claims 1-6.

10. A computer program product, characterized in that, The computer program product includes a computer program that, when executed by a processor, implements the electronic and electrical conflict resolution method according to any one of claims 1-6.

Images