CN119902747B - Proxy method and device of software component, electronic equipment and storage medium - Google Patents

Abstract

The application relates to a proxy method, a proxy device, an electronic device and a storage medium of a software component, wherein the method comprises the steps of obtaining a proxy document generated by a preset architecture design module; the method comprises the steps of analyzing a proxy document to obtain a port database containing port information of a plurality of atomic software components, obtaining a communication behavior summary table, determining a port to be proxied from the port database according to the communication behavior summary table, and adding proxy connection lines between the port to be proxied and the communication ports of the combined software components to enable the port to be proxied to communicate with other controllers through the communication ports. Therefore, the agent relation between the atomic software component construction and the combined software component in the controller can be automatically and accurately constructed, and the user experience is improved.

Description

Software component proxy method, device, electronic device and storage medium

Technical Field

The present application relates to the technical field of vehicle software architecture, and in particular to a software component proxy method, device, electronic device, and storage medium.

Background Art

SOA (Service-Oriented Architecture) is a software design and architecture pattern that combines an application's diverse services through well-defined interfaces and protocols. These services are independent, reusable, and can interact across multiple systems and organizations. SOA aims to improve the flexibility, scalability, and maintainability of software systems.

Application-layer functions are implemented through Atomic Software Components (Atomic SWCs). Generally, one functional service corresponds to one Atomic SWC, while data exchange between the Atomic SWC and external servers relies on Composition SWCs. The Atomic SWC's port must be proxied to the Composition SWC's external port, allowing the Atomic SWC to directly exchange data with external controllers through the Composition SWC's external port.

In related technologies, when proxying the ports of atomic software components, architecture design engineers generally perform port checks on each atomic software component after the composite software component is instantiated, and manually proxy the port in the tool by querying the communication behavior of the service in the API (Application Programming Interface) service details table.

However, although the entire process of the above manual proxy method is feasible, the SOA architecture design requires the development of hundreds of services, and each service has one to dozens or hundreds of ports. Therefore, the workload in the proxy work is relatively large and it is easy to make mistakes, affecting the user experience.

Summary of the Invention

The present application provides a software component proxy method, device, electronic device and storage medium to solve the technical problems in the prior art of manually proxying the ports of atomic software components to combined software components, which is labor-intensive, prone to errors and affects user experience.

In a first aspect, the present application provides a software component proxy method, the method comprising:

Obtaining a proxy document generated by a preset architecture design module, wherein the proxy document includes a combined software component corresponding to a preset controller and multiple atomic software components included in the preset controller;

Parsing the proxy document to obtain a port database containing port information of a plurality of the atomic software components;

Obtaining a communication behavior summary table, wherein the communication behavior summary table includes communication behaviors between the preset controller and other controllers;

According to the communication behavior summary table, a port to be proxied is determined from the port database, and a proxy connection is added between the port to be proxied and the communication port of the combined software component, so that the port to be proxied communicates with the other controllers through the communication port.

As an optional implementation, the proxy document is parsed to obtain a port database containing port information of multiple atomic software components, including:

Parsing the proxy document using a preset parsing algorithm to obtain component information of the combined software component and port information corresponding to each of the atomic software components in all the atomic software components;

According to the component information, the port information corresponding to the atomic software component to be proxied is written into a preset initial port database to obtain the port database.

As an optional implementation, the component information includes an instance corresponding to each atomic software component, and a reference relationship between the instance and the atomic software component;

According to the component information, the port information corresponding to the atomic software component to be proxied is written into a preset initial port database to obtain the port database, including:

According to the component information, traverse each instance included in the combined software component;

For each instance traversed, determine the target atomic software component corresponding to the instance according to the reference relationship corresponding to the instance;

Determining whether the target atomic software component has a preset introduction tag, where the introduction tag is used to indicate that the corresponding atomic software component is a virtual component of another controller introduced;

When it is determined that the target atomic software component does not have the primer tag, storing the port information of the target atomic software component in the initial port database;

After traversing all instances of the combined software component, the port database is obtained.

As an optional implementation, the component information includes proxy connection information of the combined software component, and the proxy connection information includes the port of the atomic software component, the communication port of the combined software component, and proxy information between the two;

Determining the port to be proxied from the port database according to the communication behavior summary table includes:

According to the communication behavior summary table, all current proxy ports are searched from the port database; wherein the proxy ports include ports to be proxied and ports that have been proxied;

According to the proxy connection information, a port to be proxyed is determined from all the proxy ports.

As an optional implementation method, obtain a communication behavior summary table, including:

Parsing the service details table corresponding to the preset controller to obtain a communication service and a communication relationship between the preset controller and at least one of the other controllers; wherein the communication relationship is used to represent the relationship between the sender and the receiver between the preset controller and the other controller in the communication service;

A communication behavior summary table is generated according to the communication service and the communication relationship.

As an optional implementation, according to the communication behavior summary table, all current proxy ports are queried from the port database, including:

Traversing all ports in the port database;

For each port traversed, determining a port attribute of the port, the port attribute including a receiver attribute or a sender attribute;

Query the name of the communication service to which the port belongs;

querying a target communication party from the communication behavior summary table according to the communication service name, the port attribute, and the controller name of the preset controller;

When it is determined that the target communication party is not the preset controller, the port is determined as a proxy port.

As an optional implementation, the proxy connection information further includes a port attribute of the port of the atomic software component, and the port attribute includes a receiver attribute or a sender attribute;

Determining a port to be a proxy from all the proxy ports according to the proxy connection information includes:

For each of the proxy ports, determining a target port attribute of the proxy port;

determining a plurality of target proxy connection information from the proxy connection information according to the target port attribute;

Determining whether the port included in each target proxy connection information is the proxy port;

When it is determined that all ports included in the target proxy connection information are not the proxy port, the proxy port is determined as the to-be-proxy port.

As an optional implementation, adding a proxy connection between the to-be-proxy port and the communication port of the combined software component includes:

For each of the ports to be proxied, generating a communication port tag of the communication port corresponding to the proxy port;

Writing the communication port label into the first preset position for recording the communication port in the proxy document;

generating a proxy connection label between the proxy port and the corresponding communication port;

Writing the proxy connection tag into a second preset location in the proxy document for recording the proxy connection;

The method further comprises:

The proxy document after adding the proxy connection between the port to be proxied and the communication port of the combined software component is sent to the architecture design module, so that the architecture design module generates a proxy relationship between the port to be proxied and the communication port of the combined software component according to the proxy document.

In a second aspect, the present application provides a software component agent device, the device comprising:

A first acquisition module is configured to acquire a proxy document generated by a preset architecture design module, wherein the proxy document includes a composite software component corresponding to a preset controller, multiple atomic software components included in the preset controller, and proxy connections between the composite software component and some of the atomic software components;

A parsing module, configured to parse the proxy document to obtain a port database containing port information of a plurality of the atomic software components;

A second acquisition module is used to acquire a communication behavior summary table, wherein the communication behavior summary table includes communication behaviors between the preset controller and other controllers;

A determination module is used to determine the port to be proxied from the multiple port databases according to the communication behavior summary table, and add a proxy connection between the port to be proxied and the communication port of the combined software component, so that the port to be proxied communicates with the other controllers through the communication port.

In a third aspect, the present application provides an electronic device comprising: a processor and a memory, wherein the processor is configured to execute an agent program of a software component stored in the memory to implement the agent method of the software component described in any one of the first aspects.

In a fourth aspect, the present application provides a storage medium storing one or more programs, which can be executed by one or more processors to implement the proxy method of the software component described in any one of the first aspects.

The technical solution provided by the embodiment of the present application parses the proxy document generated by the architecture design module for the preset controller to obtain the ports of multiple atomic software components in the preset controller, and writes the ports into the port database. Afterwards, the ports to be proxied in the port database that need to be proxied and have not yet formed a proxy connection with the combined software component can be accurately screened according to the communication behavior between the preset controller and other controllers, thereby building a proxy connection between the ports to be proxied and the combined software component. In this process, without involving user operation, the proxy relationship between the atomic software components to be proxied in the controller and the combined software component can be accurately built, thereby realizing the automatic and accurate construction of the proxy relationship between the atomic software components in the controller and the combined software component, thereby improving the user experience.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and, together with the description, serve to explain the principles of the present application.

In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the following briefly introduces the drawings required for use in the embodiments or the prior art texts. Obviously, for ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work.

One or more embodiments are exemplarily illustrated by pictures in the corresponding drawings. These exemplifications do not constitute limitations on the embodiments. Elements with the same reference numerals in the drawings are represented as similar elements. Unless otherwise stated, the figures in the drawings do not constitute proportional limitations.

FIG1 is a flow chart of an embodiment of a software component proxy method provided in an embodiment of the present application;

FIG2 is a flow chart of another embodiment of a software component proxy method provided in an embodiment of the present application;

FIG3 is a flow chart of an embodiment of another software component proxy method provided in an embodiment of the present application;

FIG4 is a flow chart of an embodiment of another software component proxy method provided in an embodiment of the present application;

FIG5 is a block diagram of an embodiment of an agent device for a software component provided in an embodiment of the present application;

FIG6 is a schematic structural diagram of an electronic device provided in an embodiment of the present application.

DETAILED DESCRIPTION

To make the purpose, technical solutions, and advantages of the embodiments of this application more clear, the technical solutions in the embodiments of this application will be clearly and completely described below in conjunction with the drawings in the embodiments of this application. Obviously, the embodiments described are part of the embodiments of this application, not all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of this application.

The disclosure below provides many different embodiments or examples for implementing different structures of the present application. In order to simplify the disclosure of the present application, the components and settings of specific examples are described in detail below. Of course, these are merely examples and are not intended to limit the present application. In addition, the present application may repeat reference numbers and/or letters in different examples. Such repetition is for the purpose of simplicity and clarity and does not in itself indicate the relationship between the various embodiments and/or settings discussed.

In order to solve the technical problem in the prior art that the method of manually proxying the port of the atomic software component to the combined software component is labor-intensive, prone to errors, and affects the user experience, the present application provides a software component proxy method, device, electronic device and storage medium, which can parse the proxy document generated by the architecture design module for the preset controller to obtain the ports of multiple atomic software components in the preset controller, and write the ports into the port database. Afterwards, the ports to be proxied in the port database that need to be proxied and have not yet formed a proxy connection with the combined software component can be accurately screened according to the communication behavior between the preset controller and other controllers, thereby building a proxy connection between the port to be proxied and the combined software component. In this process, without involving user operation, the proxy relationship between the atomic software component to be proxied in the controller and the combined software component can be accurately constructed, thereby realizing the automatic and accurate construction of the proxy relationship between the atomic software component in the controller and the combined software component, thereby improving the user experience.

To facilitate understanding of the software component proxy method provided in this application, the following is an explanation of the professional terms involved in this application:

SOA (Service-Oriented Architecture) is a software design and architecture pattern that combines the functional units (services) of an application through well-defined interfaces and protocols. These services are independent and reusable, and they can interact across multiple systems and organizations. SOA aims to improve the flexibility, scalability, and maintainability of software systems.

VCU (Vehicle Control Unit) is the vehicle control unit in the vehicle, also known as the vehicle controller.

API service details table: A table that defines the detailed information of each service in the SOA architecture (including atomic services, cross-domain services, enhanced services, and composite services).

Service details communication behavior: Detailed description of the service name, ID (Identity Document) information, network information, deployed server-side controller, received client-side controller information, etc.

Communication matrix: A table that defines and manages the information exchanged between the various ECUs (Electronic Control Units) in the car through the vehicle network (such as CAN (Controller Area Network), LIN (Local Interconnect Network), FlexRay (Automotive Communication Protocol), Ethernet, etc.).

SWC (Software Component): used to implement specific Autosar (AUTomotiveOpen System Architecture) application layer functions, and there are many classifications.

Composition SWC (Combination Software Component): A combined functional module used to combine multiple AtomicSWCs to implement the overall function of the controller.

Atomic SWC (Atomic Software Component): An independent functional module used to implement specific Autosar application layer functions.

Proxy. After instantiating Atomic SWC to Composition SWC, the act of proxying the port on Atomic SWC to the external port of Composition SWC is called proxy.

In actual applications, if the Atomic SWC needs to send data in the corresponding port to other external controllers or receive data from other external controllers through the Ethernet SOME/IP (Scalable Service-Oriented Middleware over IP) protocol, the port on the Atomic SWC needs to be proxied to the external port of the Composition SWC, and the Composition SWC will help send/receive data from other external controllers.

The following further explains the software component proxy method provided by the present application with reference to specific embodiments in conjunction with the accompanying drawings. The embodiments do not constitute a limitation on the embodiments of the present application.

Refer to Figure 1, which is a flow chart of an embodiment of a software component proxy method provided in an embodiment of the present application. As shown in Figure 1, the process may include the following steps:

Step 101: Obtain a proxy document generated by a preset architecture design module, wherein the proxy document includes a combined software component corresponding to a preset controller and multiple atomic software components included in the preset controller.

Step 102: Parse the proxy document to obtain a port database containing port information of multiple atomic software components.

The following is a unified description of step 101 and step 102:

The above-mentioned architecture design module refers to the architecture design tool corresponding to the SOA architecture. This architecture design module can complete the creation of composite software components (number = 1), and after completing the instantiation of atomic software components therein, use the automatic wiring and proxy wiring functions to complete automatic normal wiring and proxy wiring for composite software components and atomic software components, and generate corresponding proxy documents.

The above-mentioned common connection refers to the communication connection relationship between the atomic software components in the preset controller, that is, the atomic software components located in the same controller can communicate directly through the port.

The above-mentioned proxy connection refers to the proxy mapping relationship between the atomic software component and the composite software component. Through the proxy connection, a proxy relationship between the two can be established. Through this proxy relationship, the atomic software combination can transmit data with other controllers through the port of the composite software component.

The above-mentioned proxy document refers to the document of the communication relationship of the combined software components generated by the above-mentioned architecture design module, which can be an ARXML (AUTOSAR EXtensible Markup Language) document. This document is an XML (eXtensible Markup Language)-based file format specifically used to describe the software and hardware architecture of automotive electronic systems under the AUTOSAR (AUTomotive Open System ARchitecture) standard.

The above-mentioned preset controller refers to a controller including an SOA architecture, which can be a vehicle controller of a vehicle or other controllers. The embodiment of the present application does not impose any restrictions on this.

The above-mentioned port information refers to the relevant information corresponding to the port of the atomic software component, which may include but is not limited to: the name and attributes of the port, etc.

The above-mentioned port database is a database used to store port information of atomic software components. The embodiment of the present application does not limit the type and size of the database.

In some embodiments of the present application, the executing entity of the embodiments of the present application may first use a preset architecture design module to construct a combination software component of a preset controller, and use the automatic ordinary connection function of the architecture design module to construct ordinary connections between different atomic software components, and use the automatic proxy connection function to construct proxy connections between the combination software combination and the atomic software components.

Afterwards, a corresponding proxy document can be generated. This proxy document may include the combined software component corresponding to the preset controller and the multiple atomic software components included in the preset controller. The proxy document may also include proxy connections between the combined software component and some of the atomic software components. These proxy connections are the proxy connections between the combined software component constructed using the automatic proxy connection function and the atomic software components.

In actual applications, since SOA architecture design requires the development of hundreds or thousands of services (atomic software components), and each service has one to dozens or even hundreds of ports, the automatic proxy connection function of the architecture design module cannot accurately and comprehensively complete the proxy connection between the ports of all atomic software components to be proxied and the ports of composite software components.

To more comprehensively and accurately proxy the ports of each atomic software component to be proxied within the preset controller, the execution subject of the embodiment of the present application can parse the proxy document to obtain a port database containing port information of multiple atomic software components. By constructing this port database, the ports of the atomic software components included in the corresponding combined software component of the preset controller can be comprehensively and accurately obtained.

As for how to parse the proxy document to obtain the above-mentioned port database, it can be explained below and will not be described in detail here.

Step 103: Obtain a communication behavior summary table, where the communication behavior summary table includes communication behaviors between the preset controller and other controllers.

Step 104: Determine the proxy port from the port database according to the communication behavior summary table, and add a proxy connection between the proxy port and the communication port of the combined software component, so that the proxy port can communicate with other controllers through the communication port.

The following is a unified description of step 103 and step 104:

The above-mentioned other controllers refer to controllers that communicate with the above-mentioned preset controller. For example, when the above-mentioned preset controller is a vehicle controller, the other controllers may include but are not limited to: an engine controller, a braking system controller, and a steering system controller, etc.

The above-mentioned communication behavior summary table is used to record the communication behavior between the above-mentioned preset controller and other controllers. The communication behavior may be the sending data behavior of the preset controller to other controllers, or the receiving data behavior of the preset controller to receive data sent by other controllers. The embodiment of the present application does not limit this.

The aforementioned port to be proxy refers to a port to establish a proxy connection with the combined software component, that is, the port to be proxy needs to establish a proxy connection with the port of the combined software component but has not yet established a proxy connection.

The above-mentioned communication port refers to the external port in the combined software component used for data communication with other controllers.

In some embodiments of the present application, in order to determine whether each port in the port database is a pending proxy port that needs to establish a proxy relationship with the combined software component, the execution entity of the embodiment of the present application can obtain a communication behavior summary table between the current preset controller and other controllers, and based on the communication behavior summary table, determine the pending proxy port that needs to be proxied from the above-mentioned port database.

As an optional implementation method, the above-mentioned communication behavior summary table may be pre-stored. Based on this, the execution subject of the embodiment of the present application may obtain the pre-stored communication behavior summary table from a preset storage medium.

As another optional implementation method, the above-mentioned communication behavior summary table may be a constructed table. Based on this, the execution entity of the embodiment of the present application may construct the above-mentioned communication behavior summary table.

As for how to construct the above communication behavior summary table, it can be explained below and will not be described in detail here.

Afterwards, a proxy connection may be added between the port to be proxied and the communication port of the combined software component, so that the port to be proxied can communicate with other controllers through the communication port.

As for how to determine the port to be proxied from the above-mentioned port database based on the above-mentioned communication behavior summary table, it can be explained below and will not be described in detail here.

The technical solution provided by the embodiment of the present application is to obtain a proxy document generated by a preset architecture design module, wherein the proxy document includes a combined software component corresponding to the preset controller and multiple atomic software components included in the preset controller, parse the proxy document, obtain a port database containing port information of multiple atomic software components, obtain a communication behavior summary table, wherein the communication behavior summary table includes communication behaviors between the preset controller and other controllers, determine the port to be proxied from the port database according to the communication behavior summary table, and add a proxy connection between the port to be proxied and the communication port of the combined software component to enable the port to be proxied to communicate with other controllers through the communication port. This technical solution parses the proxy document generated by the architecture design module for the preset controller to obtain the ports of multiple atomic software components in the preset controller and writes the ports into the port database. Afterwards, the ports to be proxied in the port database that need to be proxied and have not yet formed a proxy connection with the combined software component can be accurately screened according to the communication behavior between the preset controller and other controllers, thereby building a proxy connection between the ports to be proxied and the combined software component. In this process, without involving user operation, the proxy relationship between the atomic software components to be proxied in the controller and the combined software component can be accurately built, thereby realizing the automatic and accurate construction of the proxy relationship between the atomic software components in the controller and the combined software component, thereby improving the user experience.

See Figure 2, which is a flowchart of another embodiment of a software component proxy method provided by an embodiment of the present application. The process shown in Figure 2, based on the process shown in Figure 1, describes how to parse the proxy document to obtain a port database containing port information of multiple atomic software components. As shown in Figure 2, the process may include the following steps:

Step 201: Parse the proxy document using a preset parsing algorithm to obtain component information of the combined software component and port information corresponding to each atomic software component in all the atomic software components.

The above-mentioned parsing algorithm refers to an algorithm that can parse the proxy document. Since the proxy document may include component information of the composite software component and component information of the atomic software component, the parsing algorithm may include a first parsing algorithm and a second parsing algorithm.

The first parsing algorithm mentioned above refers to an algorithm for parsing the composition software component in the proxy document, such as the Composition SWC Arxml parsing algorithm, which is an algorithm pre-stored in a library for parsing XML files that comes with a high-level language.

The second parsing algorithm mentioned above refers to an algorithm for parsing atomic software components in a proxy document, such as an Atomic SWC parsing algorithm, which is a pre-stored algorithm in a library for parsing XML files provided by a high-level language.

The above-mentioned component information refers to information related to the combined software component, which may include but is not limited to: the instance contained in the combined software component (the instance is obtained after the atomic software component is instantiated), port information (the port information may include the port attribute of the port, which indicates whether the port is a port for sending data outward or a port for receiving data, such as RPort (Receive Port) and PPort (Provided Port)), and connection information (the connection information may include proxy connection information and ordinary connection information), etc.

The port information refers to the relevant information of the ports included in each atomic software component. The ports may include a sending port for sending data and a receiving port for receiving data.

In some embodiments of the present application, in order to obtain relevant information of the current combined software component from the proxy document, the execution entity of the embodiment of the present application can obtain a preset parsing algorithm and parse the proxy document through the parsing algorithm to obtain component information of the combined software component and the port corresponding to each atomic software component in all atomic software components.

As an optional implementation method, the execution subject of the embodiment of the present application may obtain a preset first parsing algorithm, and parse the proxy document using the first parsing algorithm to obtain component information of the combined software component.

As an exemplary implementation, after obtaining the above-mentioned proxy document, the execution subject of the embodiment of the present application can obtain a first parsing algorithm for parsing the combined software component from a preset algorithm library, and use the first parsing algorithm to parse the proxy document to obtain component information of the combined software component.

As an optional implementation method, in order to obtain the ports of the atomic software components contained in the current combined software component from the proxy document, the execution entity of the embodiment of the present application can obtain a preset second parsing algorithm, and parse the proxy document through the second parsing algorithm to obtain the ports contained in each atomic software component.

As an exemplary implementation, after obtaining the above-mentioned proxy document, the executing entity of the application embodiment can obtain a second parsing algorithm for parsing atomic software components from a preset algorithm library, and use the second parsing algorithm to parse the proxy document to obtain the port of each atomic software component contained in the combined software component.

The present embodiment does not restrict the order in which component information and ports are obtained. For example, the proxy document may be parsed using the second parsing algorithm first to obtain the ports of each atomic software component, and then the proxy document may be parsed using the first parsing algorithm to obtain the component information of the combined software component. For another example, the proxy document may be parsed using both the first and second parsing algorithms simultaneously to obtain the component information of the combined software component and the ports corresponding to each atomic software component.

Step 202: Based on the component information, write the port information corresponding to the atomic software component to be proxied into a preset initial port database to obtain the port database.

The aforementioned atomic software components to be proxied refer to atomic software components with existing proxy relationships, which may include atomic software components with established proxy connections and atomic software components with existing proxy relationships but without established proxy connections.

The above-mentioned port information refers to the relevant information of the port of the atomic software component to be proxied, which can be the port name or the unique identifier of the port. The embodiment of the present application does not limit this.

The aforementioned initial port database refers to a database that is pre-established to store port information of atomic software components but does not yet store port information.

In some embodiments of the present application, the above-mentioned component information may include an instance of each atomic software component instantiated into a composite software component. Based on this, the execution subject of the embodiment of the present application can determine the atomic software component to be proxied according to the above-mentioned component information, and write the port information corresponding to the atomic software component to be proxied into a preset initial port database to obtain the above-mentioned port database.

As an optional implementation, the component information includes not only the instance corresponding to each atomic software component, but also the reference relationship between each instance and the atomic software component. Based on this, the execution subject of the embodiment of the present application can traverse each instance included in the combined software component according to the component information.

In the process of traversing each instance, for each traversed instance, the target atomic software component corresponding to the instance can be determined according to the reference relationship corresponding to the instance, that is, the atomic software component of the instance can be generated.

Afterwards, it can be determined whether the target atomic software component has a preset introduction tag. The introduction tag is used to indicate that the corresponding atomic software component is a virtual component introduced by another controller, and the virtual component cannot establish a proxy relationship with the composite software component.

Optionally, when it is determined that the target atomic software component does not have the primer tag, it indicates that the target atomic software component is not a virtual component but an atomic software component to be proxied. Therefore, the port information of the target atomic software component can be stored in the initial port database.

Optionally, when it is determined that the target atomic software component has the primer tag, it means that the target atomic software component is a virtual component, which is not the atomic software component to be proxied, and the virtual component cannot establish a proxy relationship with the combined software component. Therefore, the port information of the target atomic software component may not be written into the above-mentioned initial port database.

Finally, according to the above operations, after traversing all instances included in the combined software component, the final port database can be obtained.

The technical solution provided by the embodiment of the present application proposes to parse the above-mentioned proxy document through a preset parsing algorithm to obtain the component information of the combined software component and the port corresponding to each atomic software component in all the atomic software components. According to the above-mentioned component information, the port information corresponding to the atomic software component to be proxied is written into a preset initial port database to obtain the above-mentioned port database. This technical solution uses a parsing algorithm to respectively parse the component information of the combined software component included in the proxy document and determine the port of the atomic software component to be proxied, thereby determining the atomic software component to be proxied in the preset controller in combination with the component information, and writing the port information of the atomic software component to be proxied into the port database. Since the construction of the port database refers to the component information of the combined software component, the port database can more accurately and comprehensively include the port of each atomic software component to be proxied, thereby achieving a more accurate construction of the port database.

See Figure 3, which is a flowchart of another embodiment of a software component proxy method provided by an embodiment of the present application. The process shown in Figure 3 is based on the process shown in Figure 2 and describes how to determine the port to be proxied from the port database based on the communication behavior summary table when the component information includes proxy connection information of the combined software component. As shown in Figure 3, the process may include the following steps:

Step 301: According to the communication behavior summary table, all current proxy ports are searched from the port database, wherein the proxy ports include ports to be proxied and ports that have been proxied.

The above-mentioned communication behavior summary table is a summary table including the communication services and communication relationships between the preset controller and other controllers. The above-mentioned communication relationship can be used to characterize the relationship between the sender and the receiver between the preset controller and other controllers in the communication service, that is, whether the preset controller is the party sending data, such as the server, or the party receiving data, such as the client.

In one embodiment, the execution subject of the embodiment of the present application may obtain a pre-stored communication behavior summary table from a preset storage medium.

In another embodiment, the execution entity of the present invention may parse the service details table corresponding to the preset controller to obtain the communication services and communication relationships between the preset controller and at least one other controller. The service details table may include a detailed description of the service name, ID information, network information, deployed server controller, and received client controller information.

Afterwards, a corresponding communication behavior summary table may be generated based on the above communication services and communication relationships. For example, the communication behavior summary table shown in Table 1 below may be generated:

In some embodiments of the present application, when querying all current proxy ports from a port database based on a communication behavior summary table, all ports in the port database may be traversed, and during the traversal process, for each port traversed, the port attributes of the port are determined. The port attributes include receiver attributes and sender attributes. The receiver attributes indicate that the port is used to receive data, and the sender attributes indicate that the port is used to send data.

Afterwards, you can query the name of the communication service to which the port belongs.

As an optional implementation method, the correspondence between the port name and the communication service name can be pre-stored. Based on this, the execution entity of the embodiment of the present application can determine the communication service name of the communication service to which the port belongs according to the port name of the port.

For example, the port name can be named based on the communication service name. After obtaining the above port name, the corresponding communication service name can be directly obtained according to the naming rules. For example, the port name is the server name + preset string. After obtaining the port name, the port name can be truncated with the above preset string to obtain the corresponding server name.

Afterwards, the target communication party may be queried from the communication behavior summary table according to the communication service name, port attributes, and the controller name of the preset controller.

As an optional implementation, you can query the communication service name, port attribute, and pre-set controller as keywords to determine the target communication party corresponding to the port. Taking Table 1 as an example, assuming the communication service name is AA, the port attribute is sender (server), and the pre-set controller name is ECU1, then by querying Table 1, you can obtain a target row with a service name of AA and a server end of ECU1. This target row includes a client end of ECU2. Therefore, the target communication party corresponding to this port is ECU2.

Finally, it can be determined whether the target communication party is the preset controller.

Optionally, if it is determined that the target communication party is the preset controller, it means that the communication object of the port is other atomic software components belonging to the preset controller. It is internal communication and does not require a proxy. Therefore, it can be determined that the port is not a proxy port.

As an exemplary implementation, in order to distinguish the non-proxy port, a first preset symbol may be added to the corresponding non-proxy port in the port database to indicate that the port is a non-proxy port.

Optionally, if it is determined that the target communication party is not the preset controller, it means that the communication object of the port is another controller and a proxy is required. Therefore, the port can be determined as a proxy port.

As an exemplary implementation, in order to distinguish the above-mentioned proxy port, a second preset symbol may be added to the corresponding proxy port in the port database to indicate that the port is a proxy port.

Step 302: Determine the proxy port to be used from all proxy ports based on the proxy connection information.

The above-mentioned proxy connection information refers to the proxy connection currently included in the combined software component. The proxy connection information may include the port of the atomic software component, the communication port of the combined software component, and the proxy relationship between the two.

The above-mentioned proxy port refers to a port that has a proxy relationship with the combined software component, which may include a port with a proxy connection established and a port without a proxy connection established.

The aforementioned ports to be proxied are ports that have a proxy relationship with the combined software component but have not yet established a proxy connection.

In some embodiments of the present application, since the proxy connection information represents the proxy connection in the combined software component, the execution subject of the embodiment of the present application can filter out the proxied ports that have established proxy connections from all proxy ports based on the above proxy connection information, thereby obtaining the ports to be proxied.

As an optional implementation method, since the port of the atomic software component has corresponding port attributes, which are divided into sender attributes and receiver attributes, the above-mentioned proxy connection information can also include the port attributes of the port of the atomic software component, and the above-mentioned port attributes can include receiver attributes and sender attributes.

Based on this, when screening the proxy ports to be proxy ports from all proxy ports, the target port attribute of each proxy port in all proxy ports may be determined.

As one embodiment, as can be seen from the description in step 301, when determining that a port is a proxy port, a second preset symbol can be added to the proxy port. Therefore, the port with the second preset symbol can be determined as a proxy port, and for each proxy port with the second preset symbol, the target port attribute of the proxy port is determined.

Afterwards, a plurality of target proxy connection information may be determined from the proxy connection information according to the target port attribute. The target proxy connection information is the proxy connection information of the port corresponding to the target port attribute.

Finally, it can be determined whether the port included in each target proxy connection information is the above-mentioned proxy port.

Optionally, when it is determined that there is a target proxy connection information including a port that is the proxy port, it means that connection information already exists for the proxy port, and thus the proxy port can be determined to be an already proxied port.

As an exemplary embodiment, when a proxied port is determined, in order to distinguish the proxied port, a third preset identifier can be added to the proxied port. The third preset identifier can be the same identifier as the first preset identifier or a different identifier. This embodiment of the present application does not limit this.

Optionally, when it is determined that all ports included in the target proxy connection information are not the above-mentioned proxy ports, it means that the proxy port has not yet established a proxy connection. Therefore, the proxy port can be determined as a waiting proxy port.

As an exemplary embodiment, when it is determined that the proxy port is a pending proxy port, in order to distinguish the pending proxy port, a fourth preset identifier can be added to the pending proxy port. The fourth preset identifier can be the same identifier as the second preset identifier or a different identifier. This embodiment of the present application does not limit this.

Based on the above description, when the executing entity of the embodiment of the present application determines the ports to be proxied from the port database, it can determine whether each port has the second preset identifier and the fourth preset identifier, and determine the ports that have both the second preset identifier and the fourth preset identifier as the ports to be proxied.

The technical solution provided by the embodiment of the present application queries all current proxy ports from the port database based on the communication behavior summary table, wherein the proxy ports include ports to be proxied and ports already proxied, and determines the ports to be proxied from all proxy ports based on the proxy connection information. This technical solution determines ports with existing proxy relationships and ports with existing proxy relationships but not yet established proxy relationships based on two dimensions: a communication behavior summary table containing communication behaviors between a preset controller and other controllers, and proxy connection information in a combined software component. This two-dimensional approach can more accurately screen out ports to be proxied that currently require proxy connections, thereby achieving accurate determination of ports to be proxied.

See Figure 4, which is a flowchart of another embodiment of a software component proxy method provided in an embodiment of the present application. The process shown in Figure 4, based on the process shown in Figure 1, describes how to add a proxy connection between the port to be proxied and the communication port of the combined software component. As shown in Figure 4, the process may include the following steps:

Step 401: For each proxy port, generate a communication port tag corresponding to the proxy port.

Step 402: Write the communication port tag into a first preset position in the proxy document for recording the communication port.

The following is a unified description of step 401 and step 402:

The communication port label refers to the label of the communication port of the combined software component in the agent document. The label may include the UUID (Universally Unique Identifier) of the communication port, the name of the communication port, and the path of the communication port.

The first preset position mentioned above refers to a preset position in the proxy document for recording the communication port information, for example, the last line for recording the communication port.

In some embodiments of the present application, since the port to be proxied is a demand proxy but a proxy connection has not yet been established, that is, a port for which a proxy mapping relationship has not been formed, in order to establish a proxy connection for the port to be proxied, the execution entity of the embodiment of the present application can generate a corresponding communication port for each port to be proxied, and the communication port is an external port located in the combined software component.

Based on this, a communication port label corresponding to the communication port to be proxied can be generated for each port to be proxied, and the communication port label can be written into the first preset position in the proxy document for recording the communication port, so that the subsequent architecture-related modules can generate a corresponding communication port for the combined software component according to the label at the first preset position.

As an optional implementation, when generating the communication port label, a preset generation library may be used to generate the UUID of the communication port, and the name of the port to be proxied may be determined as the name of the communication port.

After that, the path of the communication port can be determined from the pre-parsed interface information. Based on the communication port name and the path, the path corresponding to the communication port can be generated. For example, if the port name is ZZZ and the parsed communication port path is /SoftwareTypes/Interfaces, then the path corresponding to the communication port can be obtained by concatenating the two to /SoftwareTypes/Interfaces/ZZZ.

Finally, a communication port label may be generated based on the aforementioned UUID, communication port name, and communication port path.

Step 403: Generate a proxy connection label between the proxy port and the corresponding communication port.

Step 404: Write the proxy connection tag into the second preset location in the proxy document for recording the proxy connection.

The following is a unified description of step 403 and step 404:

The above-mentioned proxy connection label refers to the label corresponding to the proxy connection between the port to be proxied and the communication port of the corresponding proxy. The architecture design module can generate the proxy relationship between the port to be proxied and the communication port through the proxy connection label in the proxy document. The proxy connection label may include but is not limited to: the UUID of the proxy connection label, the name of the proxy connection label, the path of the atomic software component where the port to be proxied is located, the path of the port to be proxied, and the path of the communication port corresponding to the port to be proxied, etc.

The second preset position refers to a position for recording proxy connection related information, such as the last row for recording proxy connection information.

In some embodiments of the present application, after establishing a corresponding communication port for the current port to be proxied, a label for establishing a proxy connection between the two can be generated, and the proxy connection label can be written into the second preset position in the proxy document for recording the proxy connection, so that the architecture design module generates a proxy relationship between the two based on the label.

As an optional implementation, when generating the corresponding proxy connection label, you can first use a preset generation library to generate the proxy connection label's UUID. Then, you can obtain the names of other proxy connections from the proxy connection information in the component information and generate a new proxy connection name based on the other proxy connection names. For example, you can sequentially number the proxy connections according to the names of the other proxy connections.

Afterwards, the proxy document may be parsed to obtain the path of the atomic software component where the port to be proxied is located, and the path of the port to be proxied.

Afterwards, the path of the communication port corresponding to the to-be-proxy port can be obtained from the communication port tag.

Finally, a corresponding proxy connection label may be generated according to the above UUID, the proxy connection name, the path of the atomic software component, the path of the port to be proxied, and the path of the communication port.

Step 405: Send the proxy document after adding the proxy connection between the port to be proxied and the communication port of the combined software component to the architecture design module, so that the architecture design module generates a proxy relationship between the port to be proxied and the communication port of the combined software component according to the proxy document.

In some embodiments of the present application, after adding the communication port label and proxy connection label corresponding to each port to be proxied, the corresponding proxy document can be saved, and the proxy document with the proxy connection added between the port to be proxied and the communication port of the combined software component can be sent to the architecture design module. The architecture design module can perform the next step of proxy relationship mapping and underlying software configuration based on the proxy document, thereby actually constructing the proxy relationship between the port to be proxied and the corresponding communication port.

The technical solution provided by the embodiments of the present application generates, for each port to be proxied, a communication port tag corresponding to the communication port of the proxy port, writes the communication port tag to a first preset location in the proxy document for recording the communication port, generates a proxy connection tag between the proxy port and the corresponding communication port, writes the proxy connection tag to a second preset location in the proxy document for recording the proxy connection, and sends the proxy document with the proxy connection added between the port to be proxied and the communication port of the combined software component to the architecture design module, so that the architecture design module generates a proxy relationship between the port to be proxied and the communication port of the combined software component based on the proxy document. This technical solution automatically establishes a proxy relationship between the port to be proxied and the combined software component by automatically adding the communication port tag and proxy connection tag corresponding to the port to be proxied in the proxy document.

Refer to Figure 5, which is a block diagram of an embodiment of a software component agent device provided in an embodiment of the present application. As shown in Figure 5, the device may include:

A first acquisition module 51 is configured to acquire a proxy document generated by a preset architecture design module, wherein the proxy document includes a combined software component corresponding to a preset controller and multiple atomic software components included in the preset controller;

A parsing module 52 is configured to parse the proxy document to obtain a port database containing port information of a plurality of the atomic software components;

A second acquisition module 53 is configured to acquire a communication behavior summary table, wherein the communication behavior summary table includes communication behaviors between the preset controller and other controllers;

The determination module 54 is used to determine the port to be proxied from the multiple port databases according to the communication behavior summary table, and add a proxy connection between the port to be proxied and the communication port of the combined software component, so that the port to be proxied communicates with the other controllers through the communication port.

As shown in FIG6 , a schematic diagram of the structure of an electronic device provided in an embodiment of the present application includes a processor 61, a communication interface 62, a memory 63, and a communication bus 64. The processor 61, the communication interface 62, and the memory 63 communicate with each other through the communication bus 64.

Memory 63, for storing computer programs;

In one embodiment of the present application, the processor 61 is configured to implement the software component proxy method provided by any one of the aforementioned method embodiments when executing a program stored in the memory 63, including:

Obtaining a proxy document generated by a preset architecture design module, wherein the proxy document includes a combined software component corresponding to a preset controller and multiple atomic software components included in the preset controller;

Parsing the proxy document to obtain a port database containing port information of a plurality of the atomic software components;

Obtaining a communication behavior summary table, wherein the communication behavior summary table includes communication behaviors between the preset controller and other controllers;

According to the communication behavior summary table, a port to be proxied is determined from the port database, and a proxy connection is added between the port to be proxied and the communication port of the combined software component, so that the port to be proxied communicates with the other controllers through the communication port.

An embodiment of the present application further provides a storage medium having a computer program stored thereon, which, when executed by a processor, implements the steps of the software component proxy method provided in any of the aforementioned method embodiments.

The device embodiments described above are merely illustrative. The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, i.e., they may be located in one place or distributed across multiple network units. Some or all of the modules may be selected based on actual needs to achieve the objectives of this embodiment.

Through the above description of the embodiments, those skilled in the art will clearly understand that each embodiment can be implemented using software plus a general-purpose hardware platform, or alternatively, hardware. Based on this understanding, the essence of the above technical solution, or the portion that contributes to the relevant technology, can be embodied in the form of a software product. This computer software product can be stored in a computer-readable storage medium, such as ROM/RAM, a magnetic disk, or an optical disk, and includes a number of instructions for enabling a computer device (which can be a personal computer, server, or network device, etc.) to execute the methods described in each embodiment or certain portions of the embodiments.

It should be understood that the terms used in the text are only for the purpose of the specific example embodiments of the text, and are not intended to be limiting. Unless the context clearly indicates otherwise, the singular forms "one", "an" and "said" as used in the text may also be meant to include plural forms. The terms "comprise", "include", "contain" and "have" are inclusive and therefore specify the existence of the stated features, steps, operations, elements and/or parts, but do not exclude the existence or addition of one or more other features, steps, operations, elements, parts, and/or combinations thereof. The method steps, processes, and operations of the text in the text are not interpreted as necessarily requiring them to be performed in the specific order of the text or instructions, unless the execution order is clearly indicated. It should also be understood that additional or alternative steps can be used.

The foregoing is merely a list of specific embodiments of the present application, intended to enable those skilled in the art to understand or implement the present application. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the present application. Therefore, the present application is not limited to the embodiments shown herein, but is intended to conform to the broadest scope consistent with the principles and novel features of the present application.

Claims (10)

1. A method of proxy for a software component, the method comprising:

acquiring a proxy document generated by a preset architecture design module, wherein the proxy document comprises a combined software component corresponding to a preset controller and a plurality of atomic software components included by the preset controller;

Analyzing the proxy document to obtain a port database containing port information of a plurality of atomic software components;

Acquiring a communication behavior summary table, wherein the communication behavior summary table comprises communication behaviors between the preset controller and other controllers;

Determining a port to be proxied from the port database according to the communication behavior summary table, and adding proxy connection lines between the port to be proxied and the communication ports of the combined software component for the port to be proxied so that the port to be proxied communicates with the other controllers through the communication ports;

Analyzing the agent document to obtain a port database containing port information of a plurality of atomic software components, wherein the analyzing the agent document through a preset analysis algorithm to obtain component information of the combined software components and port information corresponding to each atomic software component in all the atomic software components;

The method comprises the steps of adding proxy connection lines between the ports to be proxied and communication ports of the combined software component, generating a communication port label of the communication port corresponding to the proxy port for each port to be proxied, writing the communication port label into a first preset position for recording the communication port in the proxy document, generating a proxy connection line label between the proxy port and the corresponding communication port, and writing the proxy connection line label into a second preset position for recording the proxy connection line in the proxy document.

2. The method of claim 1, wherein the component information includes an instance corresponding to each atomic software component, and a reference relationship between the instance and the atomic software component;

According to the component information, writing port information corresponding to an atomic software component to be proxied into a preset initial port database to obtain the port database, wherein the method comprises the following steps:

traversing each instance comprised by the combined software component according to the component information;

For each traversed instance, determining a target atomic software component corresponding to the instance according to a reference relation corresponding to the instance;

Determining whether a preset primer tag exists in the target atomic software component or not, wherein the primer tag is used for representing that the corresponding atomic software component is a virtual component of other introduced controllers;

storing port information of the target atomic software component to the initial port database under the condition that the target atomic software component is determined to not exist in the primer tag;

And after all the examples included by the combined software component are traversed, obtaining the port database.

3. The method of claim 1, wherein the component information comprises proxy connection information for the combined software component, the proxy connection information comprising a port for the atomic software component, a communication port for the combined software component, and proxy information therebetween;

determining a port to be proxied from the port database according to the communication behavior summary table, comprising:

Inquiring all current proxy ports from the port database according to the communication behavior summary table, wherein the proxy ports comprise ports to be proxied and proxied;

And determining the port to be proxied from all the proxy ports according to the proxy connection information.

4. A method according to claim 3, wherein obtaining a summary of communication behavior comprises:

Analyzing a service detail table corresponding to the preset controller to obtain communication service and communication relation between the preset controller and at least one other controller, wherein the communication relation is used for representing the relation between a sender and a receiver between the preset controller and the other controllers in the communication service;

and generating a communication behavior summary table according to the communication service and the communication relation.

5. The method of claim 4, wherein querying all current proxy ports from the port database according to the communication behavior summary table comprises:

Traversing all ports in the port database;

determining port attributes of the ports aiming at each traversed port, wherein the port attributes comprise receiver attributes or sender attributes;

inquiring the communication service name of the port;

Inquiring a target communication party from the communication behavior summary table according to the communication service name, the port attribute and the controller name of the preset controller;

And determining the port as a proxy port in the case that the target communication party is determined to be not the preset controller.

6. The method of claim 3, wherein the proxy connection information further comprises port attributes of a port of the atomic software component, the port attributes comprising a receiver attribute or a sender attribute;

According to the proxy connection information, determining a port to be proxied from all proxy ports, including:

determining a target port attribute of each proxy port;

Determining a plurality of target agent connection information from the agent connection information according to the target port attribute;

Determining whether a port included in each target agent connection information is the agent port;

And determining the proxy port as a port to be proxied under the condition that all ports included in the target proxy connection information are not proxy ports.

7. The method according to claim 1, wherein the method further comprises:

And sending the proxy document after the proxy connection between the port to be proxied and the communication port of the combined software component is increased to the architecture design module, so that the architecture design module generates a proxy relation between the port to be proxied and the communication port of the combined software component according to the proxy document.

8. A proxy device for a software component, the device comprising:

The first acquisition module is used for acquiring a proxy document generated by a preset architecture design module, wherein the proxy document comprises a combined software component corresponding to a preset controller and a plurality of atomic software components included by the preset controller;

the analysis module is used for analyzing the proxy document to obtain a port database containing port information of a plurality of atomic software components;

The second acquisition module is used for acquiring a communication behavior summary table, and the communication behavior summary table comprises communication behaviors between the preset controller and other controllers;

The determining module is used for determining a port to be proxied from a plurality of port databases according to the communication behavior summary table, and adding proxy connection lines between the port to be proxied and the communication ports of the combined software component for the port to be proxied so that the port to be proxied can communicate with the other controllers through the communication ports;

Analyzing the agent document to obtain a port database containing port information of a plurality of atomic software components, wherein the analyzing the agent document through a preset analysis algorithm to obtain component information of the combined software components and port information corresponding to each atomic software component in all the atomic software components;

The method comprises the steps of adding proxy connection lines between the ports to be proxied and communication ports of the combined software component, generating a communication port label of the communication port corresponding to the proxy port for each port to be proxied, writing the communication port label into a first preset position for recording the communication port in the proxy document, generating a proxy connection line label between the proxy port and the corresponding communication port, and writing the proxy connection line label into a second preset position for recording the proxy connection line in the proxy document.

9. An electronic device comprising a processor and a memory, the processor configured to execute a software component proxy program stored in the memory, to implement the software component proxy method of any one of claims 1-7.

10. A storage medium storing one or more programs executable by one or more processors to implement the proxy method of the software component of any one of claims 1-7.