CN116684415A - Controller cross-domain communication method, device, electronic equipment and storage medium - Google Patents

Abstract

The application discloses a controller cross-domain communication method, device, electronic equipment, and computer-readable storage medium. The controller cross-domain communication method includes: determining the master domain controller among multiple domain controllers; obtaining the slave domain controller address information, and record the address information in the master domain controller, the slave domain controller is a domain controller other than the master domain controller among the plurality of domain controllers, the Address information can be used to establish communication links between different domain controllers; based on the address information recorded by the master domain controller, create links between different slave domain controllers to achieve communication, and the different slave domain controllers There is a need for communication between devices. The number of configuration files can be greatly reduced, configuration costs are reduced, configuration confusion is avoided, and communication success rate is improved.

Description

Controller cross-domain communication method, device, electronic equipment and storage medium

technical field

The present application relates to domain controller communication technology, and in particular to a controller cross-domain communication method, device, electronic equipment, and computer-readable storage medium.

Background technique

A domain controller (Domain Controller, DC) refers to a server computer that responds to security authentication requests in a computer network domain in "domain" mode. It is a network server that is responsible for allowing hosts to access domain resources, authenticating users, Store user account information and enforce security policies for the domain. Domain controllers can be used in various scenarios. Take the automotive scenario as an example. With the rapid development of the smart car era, smart cars are equipped with more and more domain controllers. However, when performing cross-domain communication, every two The communication between domain controllers needs to rely on the information configured in the configuration file to establish links to achieve communication. When adding a new domain, a certain number of configuration files need to be added to create communication links. When the number of domain controllers is large, the configuration file The number of will be large, which makes the configuration cost high, and it is easy to cause configuration confusion, resulting in a decrease in the communication success rate.

Contents of the invention

In view of the above technical problems, this application provides a controller cross-domain communication method, device, electronic equipment and computer-readable storage medium, the technical solution is as follows:

According to the first aspect of the present application, a controller cross-domain communication method is provided, the method comprising:

Determining the primary domain controller among multiple domain controllers;

Obtain address information of a slave domain controller, and record the address information in the master domain controller, where the slave domain controller is a domain other than the master domain controller among the plurality of domain controllers a controller, the address information can be used to establish a communication link between different domain controllers;

Based on the address information recorded by the master domain controller, links are established between different slave domain controllers to implement communication, and there is a communication requirement among the different slave domain controllers.

According to the second aspect of the present application, a controller cross-domain communication device is provided, the device includes:

a determination unit, configured to determine a primary domain controller among multiple domain controllers;

A recording unit, configured to acquire address information of a slave domain controller, and record the address information in the master domain controller, where the slave domain controller is one of the plurality of domain controllers except the master domain controller a domain controller other than the domain controller, and the address information can be used to establish a communication link between different domain controllers;

The creating unit is configured to, based on the address information recorded by the master domain controller, create a link between different slave domain controllers to realize communication, and there is a communication requirement among the different slave domain controllers.

According to a third aspect of the present application, an electronic device is provided, and the electronic device includes:

processor;

memory for storing processor-executable instructions;

Wherein, the processor is configured to implement the method as described in the first aspect.

According to a fourth aspect of the present application, a computer-readable storage medium is provided, on which a computer program is stored, and when the computer program is executed by a processor, the steps in the method described in the first aspect are implemented.

In the technical solution provided by this application, when there are multiple domain controllers that need to communicate with each other, the primary domain controller is determined among the multiple domain controllers, and the domain controllers other than the primary domain controller are determined as The slave domain controller records the address information of each slave domain controller in the master domain controller. When different slave domain controllers need to communicate, a slave domain controller can directly pass the address information recorded by the master domain controller. The address information establishes a communication link with another secondary domain controller without additional configuration files to configure address information. Even when adding a domain, there is no need to add additional configuration files, but only the newly added domain controller The address information is recorded in the primary domain controller, thereby greatly reducing the number of configuration files, reducing configuration costs, avoiding configuration confusion, and improving communication success rate.

It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the application.

Description of drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present application or related technologies, the following will briefly introduce the accompanying drawings that need to be used in the description of the embodiments or related technologies. Obviously, the accompanying drawings in the following description are only For some embodiments described in the application, those skilled in the art can also obtain other drawings based on these drawings.

FIG. 1 is a schematic diagram of a controller cross-domain communication scenario in the related art;

FIG. 2 is a schematic flow diagram of a controller cross-domain communication method of the present application;

FIG. 3 is a schematic diagram of a controller cross-domain communication scenario according to an embodiment of the present application;

FIG. 4 is a schematic structural diagram of a controller cross-domain communication device according to an embodiment of the present application;

Fig. 5 is a schematic structural diagram of an electronic device according to an embodiment of the present specification.

Detailed ways

In order to enable those skilled in the art to better understand the technical solutions in the present application, the technical solutions in the embodiments of the present application will be described in detail below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only It is a part of the embodiments of this application, not all of them. All other embodiments obtained by persons of ordinary skill in the art based on the embodiments in this application shall fall within the protection scope of this application.

Please refer to Fig. 1, first, the controller cross-domain communication scenario in the related art is introduced, the domain controller refers to the server computer that responds to the security authentication request in the computer network domain in the "domain" mode, and is a network server. It is responsible for allowing hosts to access domain resources, authenticating users, storing user account information, and enforcing security policies for the domain.

Domain controllers can be used in various scenarios. Take the car scene in Figure 1 as an example. With the rapid development of the smart car era, smart cars are equipped with more and more domain controllers. Multiple domain controllers need to Communicate with each other to realize complex functions and services. However, taking a service-oriented distributed architecture (Service-Oriented Architecture, SOA) as an example in a car, under the SOA architecture, when performing cross-domain communication, every two domain controllers Communication needs to rely on the information configured in the configuration file to establish links to achieve communication. When adding a new domain, a certain number of configuration files must be added to create communication links. When the number of domain controllers is large, the number of configuration files will also be relatively large. Large, which makes the configuration cost high, and it is easy to cause configuration confusion, resulting in a decrease in the communication success rate.

Please refer to Figure 1, which uses the application of domain controllers in automobile scenarios as an example for illustration:

Assume that there are currently three domain controllers in the car: domain controller 101, domain controller 102, and domain controller 103. These three domain controllers all need to communicate with each other. Taking domain controller 101 as an example, if domain If the controller 101 needs to communicate with the domain controller 102 and the domain controller 103, it is necessary to configure the address information of the domain controller 102 and the domain controller 103 in the domain controller 101 through the configuration file 1 in advance, so that the domain controller 101 can use the The configured address information establishes link 1 with domain controller 102 to realize communication between the two, or establishes link 3 with domain controller 103 to realize communication between the two; if domain controller 102 needs to communicate with domain controller 101 and domain controller 103 , it is also necessary to configure the address information of domain controller 101 and domain controller 103 in domain controller 102 in advance through configuration file 2. When domain controller 102 needs to communicate with domain controller 103, it can communicate with domain controller according to the configured address information. The controller 103 establishes the link 2 to realize the communication between the two; similarly, if the domain controller 103 needs to communicate with the domain controller 101 and the domain controller 102, it is also necessary to configure the domain controller 101 in the domain controller 103 through the configuration file 3 in advance and the address information of the domain controller 102, however, in an actual application scenario, the number of domain controllers in the car is far more than the three shown in Figure 1, and each domain controller needs to communicate with other domain controllers Configuration files need to be configured. When the number of domain controllers is large, the number of configuration files will also be large, and it is possible to add a domain controller to the existing domain controller in the car. When using a new domain controller, not only do you need to add new configuration files on the new domain controller, but you also need to reconfigure the existing configuration files on the original domain controllers to meet the needs of the new domain controller and the original domain controller (such as The communication requirements of domain controller 101, domain controller 102, and domain controller 103) in FIG. 1 make the configuration cost high, and easily cause configuration confusion, resulting in a decrease in communication success rate.

It is worth noting that the above-mentioned introduction to the controller cross-domain communication scenario is only an exemplary display. In practical applications, other controller cross-domain communication scenarios cannot be ruled out, which is not specifically limited.

In view of the above problems, the present application provides a controller cross-domain communication method, which can greatly reduce the number of configuration files, reduce configuration costs, avoid configuration confusion, and improve communication success rate. As shown in Figure 2, the method includes the following steps:

S201. Determine a primary domain controller among multiple domain controllers;

As an example, among multiple domain controllers, different "domains" may be divided based on IP addresses of the controllers. It is worth noting that the above description of the basis for dividing different "domains" is only an exemplary display, and in practical applications, other basis for dividing may not be excluded, and this is not specifically limited.

There may be multiple ways to determine the primary domain controller among multiple domain controllers. As an example, one of the ways may include: among the above-mentioned multiple domain controllers, determining the domain controller with the central gateway as the primary domain controller device. Since the address information of the central gateway is fixed and can be known by each domain controller in advance, and the central gateway has the ability to connect to each domain controller, the domain controller with the central gateway is determined to be the master domain controller, which can ensure the The domain controller has the ability to interact with each slave domain controller, and the location of the master domain controller can be known in advance by other slave domain controllers. It is worth noting that the above description of the manner of determining the primary domain controller is only an exemplary display, and in practical applications, other determination manners are not excluded, and this is not specifically limited.

As an example, the multiple domain controllers may be existing domain controllers or newly added domain controllers.

S202. Obtain address information of a secondary domain controller, and record the address information in the primary domain controller, where the secondary domain controller is one of the plurality of domain controllers except the primary domain controller domain controllers, the address information can be used to establish communication links between different domain controllers;

As an example, when the above-mentioned master domain controller is a domain controller with a central gateway, the address information of the central gateway may be pre-stored in the domain controllers other than the master domain controller among the above-mentioned multiple domain controllers. A domain controller, so that the slave domain controller establishes a communication link with the master domain controller based on the address information of the central gateway. Since the address information of the central gateway is fixed and can be known by each slave domain controller in advance, it can ensure that the master domain controller has the ability to interact with each slave domain controller, and at the same time, the location of the master domain controller can be determined by other slave domain controllers. The domain controller is known in advance, so that the master domain controller has the ability to obtain the address information of each slave domain controller.

As an example, the above secondary domain controller may be an existing domain controller or a newly added domain controller.

The address information of the slave domain controller can be obtained in various ways. As an example, when the above address information is the address information of the engine running on the slave domain controller, one of the acquisition methods can be: first monitor the slave domain controller The running state of the engine of the server. The running state of the engine can at least include the online state or the offline state. For example, when the engine of the slave domain controller is online, the running state of the engine can be the above-mentioned online state. When the engine is offline, the running status of the engine can be the above-mentioned offline status; if it is monitored that the running status of the engine of the slave domain controller is online, the address information of the engine of the slave domain controller can be obtained; If the running state of the engine of the slave domain controller is offline, the operation of obtaining the address information of the engine of the slave domain controller may not be performed. It should be noted that the engine can be a process running on the primary domain controller, and whether to obtain the address information of the secondary domain controller is determined according to the online or offline status of the engine process, which can save the cost of obtaining address information to the greatest extent. It is worth noting that the above description of obtaining the address information of the secondary domain controller is only an exemplary display, and in practical applications, other obtaining methods are not excluded, and there is no specific limitation on this.

As an example, there may be many situations in which it is monitored that the running status of the engine of the secondary domain controller is online. As an example, one of the situations may be that the secondary domain controller is a newly added domain controller, and the new The engine of the added domain controller is just in the online state; another situation may be that the secondary domain controller is an existing domain controller, and the engine of the domain controller has been in the online state. There is no specific limitation on this.

As an example, the system used by the domain controller may be a Linux system, and the above engine may be a process running on the Linux system. It should be noted that the above description of the system used by the domain controller is only an exemplary display, and in practical applications, it does not exclude the use of other systems, which is not specifically limited.

S203. Based on the address information recorded by the master domain controller, create a link between different slave domain controllers to implement communication, and there is a communication requirement among the different slave domain controllers.

The address information of the slave domain controller can be recorded in the master domain controller in various ways. As an example, one of the recording methods can include: recording the address information of the slave domain controller in the manager application program of the master domain controller . It should be noted that the manager application program may be a process running on the primary domain controller, and the efficient recording and management of many address information can be realized through the manager application program. It is worth noting that the above description of the address information recording method is only an exemplary display, and in practical applications, other recording methods are not excluded and are not specifically limited.

There are many ways to create links between different slave domain controllers to achieve communication. As an example, when the master domain controller and slave domain controllers are under the SOA architecture, one of the ways can include: Based on the master domain controller The recorded address information of the secondary domain controllers and the SOA middleware under the above SOA architecture create links between different secondary domain controllers to realize communication. Since the SOA middleware encapsulates part of the underlying code necessary to create links between domain controllers, through the SOA middleware to create links between different secondary domain controllers, there is no need to write additional underlying code, which greatly reduces the time required for creating links. Computing costs. It is worth noting that the above description of the link creation method is only an exemplary display, and in practical applications, other creation methods are not excluded and are not specifically limited.

As an example, the above-mentioned SOA middleware may be a COM component or other components, which is not specifically limited.

As an example, when there is a communication requirement between different slave domain controllers, the requirement can be that one slave domain controller needs to query the data written by another slave domain controller, then the slave domain controller that needs to query the data exists The need to communicate with another secondary domain controller. The need for communication between different secondary domain controllers may also be other situations, which are not specifically limited.

The address information of the slave domain controller can have multiple specific implementations. As an example, one of the implementations can be: the address information of the slave domain controller can include IP information and PORT information. For example, assume that there are 3 slave domain controllers : the slave domain controller S32G, the slave domain controller ORIN and the slave domain controller TCAM, the address information of the slave domain controller S32G may include IP information: 192.168.0.2; and PORT information: 0002. The address information of the secondary domain controller ORIN may include IP information: 192.168.0.3; and PORT information: 0003. The address information of the secondary domain controller ORIN may include IP information: 192.168.0.4; and PORT information: 0004. It should be noted that the primary domain controller may also have address information, such as IP information: 192.168.0.1; and PORT information: 0001. It is worth noting that the above description of the specific implementation of the address information of the slave domain controller is only an exemplary display, and in practical applications, other specific implementations are not excluded, and this is not specifically limited.

Referring to FIG. 3, the following is an exemplary description of a specific application scenario of controller cross-domain communication in an embodiment of the present application:

Taking the car scene as an example, assuming that there are multiple domain controllers on the car, they are master domain controller 301, slave domain controller 302, slave domain controller 303, and slave domain controller 304, slave domain controller 302, slave domain controller The controller 303 and the slave domain controller 304 have their own address information: address information 1, address information 2, and address information 3, and the three slave domain controllers can pre-store the address information of the master domain controller 301 to communicate with each other at any time. The master domain controller 301 communicates, and the master domain controller 301 can respectively obtain address information 1, address information 2, and address information 3 of the slave domain controller 302, slave domain controller 303, and slave domain controller 304 and record them in the master domain In the controller 301, taking the slave domain controller 302 as an example, when the slave domain controller 302 needs to communicate with the slave domain controller 303, it can first establish an Link, and then obtain the address information 2 of the slave domain controller 303 from the master domain controller 301 through the link, when the address information 2 is successfully obtained, the slave domain controller 302 can communicate with the slave domain controller 303 based on the address information 2 A link is established to realize the communication between the two. If the address information 2 fails to be obtained (for example, the address information 2 does not exist in the master domain controller 301 ), then a sending error is confirmed and the error is returned to the slave domain controller 302 . When a new slave domain controller is added in the car, the newly added slave domain controller can also report its address information to the master domain controller 301, and the master domain controller 301 records the newly added address information.

In the technical solution provided by the embodiment of the present application, when there are multiple domain controllers that need to communicate with each other, the primary domain controller is determined among the multiple domain controllers, and the domain controllers other than the primary domain controller are Determined as a slave domain controller, record the address information of each slave domain controller in the master domain controller, when different slave domain controllers need to communicate, a slave domain controller can directly pass the address information of the master domain controller The recorded address information establishes a communication link with another secondary domain controller without additional configuration files to configure address information. The address information of the controller is recorded in the primary domain controller, thereby greatly reducing the number of configuration files, reducing configuration costs, avoiding configuration confusion, and improving communication success rate.

Corresponding to the above method embodiment, the present application also provides a controller cross-domain communication device, as shown in FIG. 4, the device may include:

A determining unit 401, configured to determine a primary domain controller among multiple domain controllers;

The recording unit 402 is configured to obtain address information of a slave domain controller, and record the address information in the master domain controller, where the slave domain controller is the master domain controller among the plurality of domain controllers A domain controller other than the controller, the address information can be used to establish a communication link between different domain controllers;

The creating unit 403 is configured to, based on the address information recorded by the master domain controller, create links between different slave domain controllers to realize communication, and there is a communication requirement among the different slave domain controllers.

As an example, the determining unit 401 is specifically configured to determine, among the plurality of domain controllers, a domain controller having a central gateway as the primary domain controller.

As an example, the address information of the central gateway is pre-stored in the slave domain controller, so that the slave domain controller establishes a communication link with the master domain controller based on the address information of the central gateway.

As an example, the recording unit 402 is specifically used to monitor the running state of the engine of the slave domain controller, and the running state includes an online state or an offline state; if it is monitored that the running state is an online state, then obtain the The address information of the engine of the controller.

As an example, the recording unit 402 is specifically configured to record the address information in a manager application program of the primary domain controller.

As an example, the above-mentioned controller cross-domain communication device is applied to the SOA architecture, and the creation unit 403 is specifically configured to create different slave domain controllers based on the address information recorded by the master domain controller and the SOA middleware of the SOA architecture Create links between them for communication.

As an example, the address information includes IP information and PORT information.

It is worth pointing out that each of the above embodiments of the controller cross-domain communication method can be applied to the controller cross-domain communication device based on the address information of the slave domain controller recorded by the master domain controller to create a network between different slave domain controllers. The process of linking to enable communication.

The present application also provides an electronic device, as shown in Figure 5, the electronic device includes:

Processor 501;

memory 502 for storing processor-executable instructions;

Wherein, the processor 501 is configured to implement the controller cross-domain communication method described in any of the above embodiments.

The present application also provides a computer-readable storage medium, on which a computer program is stored, and when the computer program is executed by a processor, the controller cross-domain communication method described in any of the above embodiments is implemented.

The above description is only the specific implementation of the present application. It should be pointed out that for those of ordinary skill in the art, without departing from the principle of the present application, some improvements and modifications can also be made. It should be regarded as the protection scope of this application.

Claims (10)

1. A controller cross-domain communication method, characterized in that, comprising: Determining the primary domain controller among multiple domain controllers; Obtain address information of a slave domain controller, and record the address information in the master domain controller, where the slave domain controller is a domain other than the master domain controller among the plurality of domain controllers a controller, the address information can be used to establish a communication link between different domain controllers; Based on the address information recorded by the master domain controller, links are established between different slave domain controllers to implement communication, and there is a communication requirement among the different slave domain controllers. 2. The method according to claim 1, wherein said determining the primary domain controller among the plurality of domain controllers comprises: Among the plurality of domain controllers, a domain controller having a central gateway is determined as the master domain controller. 3. The method according to claim 2, wherein the address information of the central gateway is pre-stored in the slave domain controller, so that the slave domain controller is based on the address information of the central gateway and the The primary domain controller establishes the communication link. 4. The method according to claim 1, wherein the address information is address information of an engine running on the slave domain controller, and before obtaining the address information of the slave domain controller, the method further include: Monitoring the running state of the engine of the slave domain controller, the running state includes an online state or an offline state; The acquisition of address information from the domain controller includes: If it is monitored that the running state is the online state, the address information of the engine of the slave domain controller is obtained. 5. The method according to claim 1, wherein the recording the address information in the primary domain controller comprises: Record the address information in the manager application program of the primary domain controller. 6. The method according to claim 1, wherein the method is applied to an SOA framework, and based on the address information recorded by the master domain controller, a link is created between different slave domain controllers to Implementing communications includes: Based on the address information recorded by the master domain controller and the SOA middleware of the SOA architecture, links are established between different slave domain controllers to implement communication. 7. The method according to claim 1, wherein the address information includes IP information and PORT information. 8. A controller cross-domain communication device, characterized in that, comprising: a determination unit, configured to determine a primary domain controller among multiple domain controllers; A recording unit, configured to acquire address information of a slave domain controller, and record the address information in the master domain controller, where the slave domain controller is one of the plurality of domain controllers except the master domain controller a domain controller other than the domain controller, and the address information can be used to establish a communication link between different domain controllers; The creating unit is configured to, based on the address information recorded by the master domain controller, create a link between different slave domain controllers to realize communication, and there is a communication requirement among the different slave domain controllers. 9. An electronic device, characterized in that it comprises: processor; memory for storing processor-executable instructions; Wherein, the processor is configured to implement the method according to any one of claims 1-7. 10. A computer-readable storage medium, on which a computer program is stored, wherein when the computer program is executed by a processor, the steps in the method according to any one of claims 1 to 7 are realized.