Network configuration method and device

Abstract

The invention provides a network configuration method and device. The method comprises the following steps: establishing a connection relationship among a plurality of network devices according to a user instruction, wherein the plurality of network devices are vehicle-mounted network devices; acquiring basic configuration of each network device in the plurality of network devices, wherein the basic configuration of each network device comprises address information of each network device; and generating network configuration information for each network device according to the connection relationship among the plurality of network devices and the basic configuration of each network device. The method can be applied to communication architecture design of intelligent driving equipment such as an intelligent vehicle and an electric vehicle, the workload of a user during network configuration of the communication architecture can be reduced, and the configuration threshold is lowered.

Description

Network configuration method and device Technical Field

[0001] The present application relates to the field of electronic and electrical architecture design, and in particular, to a network configuration method and device. Background Art

[0002] The vehicle electrical and electronic architecture (EEA) is a complete vehicle electrical and electronic solution that integrates the design of the vehicle's electrical and electronic systems, central electrical box, connectors, and electrical and electronic distribution systems. Through EEA design, information about the powertrain, chassis, intelligent driving, infotainment, body, and thermal management is transformed into practical electrical and electronic solutions, including physical layout, signal networks, data networks, and diagnostics.

[0003] By properly configuring the communication architecture within an EEA, communication between various components within the EEA (such as controllers and sensors) can be achieved, including the transmission and reception of data, control signals, and other information. However, EEA involves one or more network interfaces, as well as network relationships between one or more sensors and an electronic control unit (ECU). These sensors and ECUs are interconnected via multiple communication protocols, resulting in complex and diverse network relationships. This makes configuring the communication architecture difficult for developers, resulting in a high configuration workload and the risk of errors.

[0004] In view of this, a network configuration solution that can reduce the user's configuration workload and lower the configuration threshold is in urgent need of development.

[0005] Summary of the Invention

[0006] The present application provides a network configuration method and device, which can reduce the user's configuration workload and lower the configuration threshold.

[0007] In a first aspect, a network configuration method is provided, the method comprising: establishing a connection relationship between multiple network devices according to user instructions, the multiple network devices being vehicle-mounted network devices; obtaining a basic configuration of each of the multiple network devices, the basic configuration of each network device including address information of each network device; and generating network configuration information for each network device based on the connection relationship between the multiple network devices and the basic configuration of each network device.

[0008] In the above technical solution, network configuration information can be generated for the in-vehicle network devices based on the user-designed connection relationships between the in-vehicle network devices and the basic configuration settings of each in-vehicle network. The process of generating the network configuration table is invisible to the user, reducing the user's understanding and learning costs, simplifying the complexity of network configuration, and helping to lower the planning and configuration threshold of the EEA communication architecture. In addition, the generation and configuration of this network configuration information is completed during the development and design phase, and does not require self-learning configuration during the actual operation of the in-vehicle network equipment. Therefore, it can meet the high reliability and high security requirements of the in-vehicle network field.

[0009] Exemplarily, the in-vehicle network device may correspond to an ECU and / or a sensor in an intelligent driving device.

[0010] Exemplarily, the connection relationship between the multiple network devices can be used to represent the EEA of the intelligent driving device.

[0011] In combination with the first aspect, in some implementations of the first aspect, the method further includes: controlling a display device to display a first interface, where the first interface includes a connection relationship between the multiple network devices.

[0012] In some possible implementations, the display device may be a display screen of a device that is deployed to execute the above method, or may be other display devices associated with the device that executes the above method.

[0013] In the above technical solution, during the configuration of the EEA communication architecture, the connection relationship (or topology structure) between each network device in the EEA can be displayed to the user. By intuitively displaying the topology structure of the EEA to the user, the user can understand the design intention of the EEA, which can reduce the user's learning and usage costs; in addition, it can also save the user's time in communicating with the network architect during the configuration process, and save the workload of subsequent configuration and debugging, greatly reducing development costs.

[0014] In combination with the first aspect, in certain implementations of the first aspect, the first interface includes a display area and a creation tool area, the creation tool area includes multiple network device objects of different types, the multiple network device objects of different types are used to create the multiple network devices, and the display area is used to display the connection relationship between the multiple network devices.

[0015] In some possible implementations, the network device created by the network device object has a communication port, which is used to communicate with other network devices.

[0016] In the above technical solution, a tool for creating an EEA communication architecture is provided to users, further facilitating the users to complete network configuration.

[0017] In combination with the first aspect, in some implementations of the first aspect, the connection relationship between the multiple network devices includes the type of a communication port of each network device in the multiple network devices, and the communication port is a port connected to other network devices.

[0018] In some possible implementations, the creation tool area further includes a communication port object and a hardware connection relationship object, wherein the communication port object is used to create a communication port on a network device, and the hardware connection relationship object is used to create a connection relationship between communication ports.

[0019] In the above technical solution, a tool for creating a communication port is provided to the user, and the user can flexibly modify the communication port on each vehicle network device when developing and designing the EEA.

[0020] In combination with the first aspect, in some implementations of the first aspect, the type of the communication port includes an Ethernet (ETH) port, a universal asynchronous receiver / transmitter (UART) port, a low voltage differential signaling (LVDS) port, or a controller area network (CAN) port.

[0021] In combination with the first aspect, in certain implementations of the first aspect, network configuration information is generated for each network device based on the connection relationship between the multiple network devices and the basic configuration of each network device, including: determining the communication relationship between the multiple network devices based on the type of the communication port of each network device in the multiple network devices and the basic configuration of each network device; and generating network configuration information for each network device based on the communication relationship between the multiple network devices.

[0022] In some possible implementations, the communication port may be an Ethernet port, which may be an ETH port or a Switch port, wherein the ETH port is used as a source port or a destination port for Ethernet communication, and the Switch port is used to forward Ethernet packets. When the communication port is an Ethernet port, the communication relationship between the multiple network devices may be determined based on a virtual local area network identification (VLAN ID) of the network device.

[0023] In combination with the first aspect, in certain implementations of the first aspect, the basic configuration of each network device also includes the VLAN ID of the network device, and determining the communication relationship between the multiple network devices based on the type of the communication port of each network device in the multiple network devices and the basic configuration of each network device includes: determining the communication relationship between the multiple network devices based on the type of the communication port of each network device in the multiple network devices and the VLAN ID of each network device.

[0024] Illustratively, a network device may include one or more Ethernet sub-devices. Determining the communication relationship between the multiple network devices based on the type of the communication port of each network device and the VLAN ID of each network device may include: determining one or more network device sets based on the VLAN ID of each Ethernet sub-device in each network device, wherein the Ethernet sub-devices in a network device set are in a broadcast domain. Illustratively, the network device set represents a communication relationship.

[0025] The Ethernet sub-device is a device in a network device that processes Ethernet packets. For example, the Ethernet sub-device may include an ETH device and / or a virtual ETH device. The ETH device is a device that is physically connected to an external device or communication port, and the virtual ETH device is a virtual sub-network card device abstracted from the ETH device.

[0026] It should be noted that the "connection relationship" in this application includes the physical connection relationship between two network devices established through a hardware connection relationship object; the "communication relationship" in this application includes the relationship between two network devices through Ethernet communication. It is understood that two network devices that have a connection relationship do not necessarily have a communication relationship.

[0027] In combination with the first aspect, in certain implementations of the first aspect, obtaining the basic configuration of each network device among the multiple network devices includes: in response to an operation on a first network device, controlling a display device to display a second interface, and obtaining the basic configuration of the first network device through the second interface, where the first network device is any one of the multiple network devices.

[0028] Exemplarily, the operation on the first network device among the multiple network devices can be an operation of clicking on the first network device in the display interface (such as the first interface), or it can be an operation of clicking on the communication port of the first network device in the display interface (such as the first interface), or it can be other operations.

[0029] In the above technical solution, based on the connection relationship of multiple network devices displayed to the user, an interface for configuring the basic configuration of each network device is provided to the user, so that the user can input the basic configuration while understanding the connection relationship between the network devices, which can reduce the workload and difficulty of network configuration for EEA development and design personnel.

[0030] In combination with the first aspect, in certain implementations of the first aspect, the basic configuration of each network device also includes a data flow configuration, which indicates the constraints on the data flow generated when providing services to each network device, and the constraints on the data flow include one or more of the direction of the data flow, the transmission speed of the data flow, and the priority of the data flow. The method also includes: controlling the display device to display a third interface, and the third interface includes one or more of the direction of the data flow, the transmission speed of the data flow, and the priority of the data flow between the multiple network devices.

[0031] In the above technical solution, by displaying one or more of the direction of the data flow, the transmission speed of the data flow, and the priority of the data flow between the multiple network devices on the third interface, the user can intuitively understand the communication process between the multiple network devices, thereby determining the effect of the network configuration, and helping the user understand the EEA model composed of the multiple network devices.

[0032] In combination with the first aspect, in some implementations of the first aspect, the network configuration information includes one or more of an access control list (ACL), an address resolution list (ARL), an address resolution protocol (ARP), and a routing table.

[0033] In a second aspect, a network configuration device is provided, which includes a first processing unit, an acquisition unit and a generation unit, wherein the first processing unit is used to: establish a connection relationship between multiple network devices according to user instructions, and the multiple network devices are vehicle-mounted network devices; the acquisition unit is used to: obtain a basic configuration of each network device in the multiple network devices, and the basic configuration of each network device includes address information of each network device; the generation unit is used to: generate network configuration information for each network device based on the connection relationship between the multiple network devices and the basic configuration of each network device.

[0034] In combination with the second aspect, in some implementations of the second aspect, the apparatus further includes a second processing unit configured to: control the display device to display a first interface, where the first interface includes a connection relationship between the multiple network devices.

[0035] In combination with the second aspect, in certain implementations of the second aspect, the first interface includes a display area and a creation tool area, the creation tool area includes multiple network device objects of different types, the multiple network device objects of different types are used to create the multiple network devices, and the display area is used to display the connection relationship between the multiple network devices.

[0036] In combination with the second aspect, in some implementations of the second aspect, the connection relationship between the multiple network devices includes the type of a communication port of each network device in the multiple network devices, and the communication port is a port connected to other network devices.

[0037] In combination with the second aspect, in some implementations of the second aspect, the type of the communication port includes an Ethernet port, a UART port, a LVDS port, or a CAN port.

[0038] In combination with the second aspect, in certain implementations of the second aspect, the device also includes a determination unit for determining the communication relationship between the multiple network devices based on the type of the communication port of each network device in the multiple network devices and the basic configuration of each network device; the generation unit is used to generate network configuration information for each network device based on the communication relationship between the multiple network devices.

[0039] In combination with the second aspect, in certain implementations of the second aspect, the basic configuration of each network device also includes the virtual local area network identifier VLAN ID of the network device, and the determination unit is used to determine the communication relationship between the multiple network devices based on the type of the communication port of each network device in the multiple network devices and the VLAN ID of each network device.

[0040] In combination with the second aspect, in certain implementations of the second aspect, the device also includes a third processing unit, which is used to: in response to an operation on the first network device, control the display device to display a second interface, and the acquisition unit is used to: obtain the basic configuration of the first network device through the second interface, and the first network device is any one of the multiple network devices.

[0041] In combination with the second aspect, in certain implementations of the second aspect, the basic configuration of each network device also includes a data flow configuration, which indicates the constraints on the data flow generated when each network device provides services, and the constraints on the data flow include one or more of the direction of the data flow, the transmission speed of the data flow, and the priority of the data flow. The device also includes a fourth processing unit, which is used to: control the display device to display a third interface, and the third interface includes one or more of the direction of the data flow, the transmission speed of the data flow, and the priority of the data flow between the multiple network devices.

[0042] In some possible implementations, the third processing unit and the fourth processing unit are the same processing unit.

[0043] In combination with the second aspect, in some implementations of the second aspect, the network configuration information includes one or more items of ACL, ARL, ARP table, and routing table.

[0044] In a third aspect, a network configuration device is provided, which includes: a memory for storing a computer program; and a processor for executing the computer program stored in the memory, so that the device performs the method in any possible implementation of the first aspect.

[0045] In a fourth aspect, an electronic device is provided, which includes the device in any possible implementation of the second aspect or the third aspect.

[0046] In some possible implementations, the electronic device further includes a display device.

[0047] In a fifth aspect, a computer program product is provided, comprising: a computer program code, which, when executed on a computer, enables the computer to execute the method in any one of the possible implementations of the first aspect.

[0048] It should be noted that the above-mentioned computer program code may be stored in whole or in part on a first storage medium, wherein the first storage medium may be packaged together with the processor or separately from the processor.

[0049] In a sixth aspect, a computer-readable medium is provided, wherein the computer-readable medium stores instructions. When the instructions are executed by a processor, the processor implements the method in any possible implementation of the first aspect.

[0050] In a seventh aspect, a chip is provided, which includes a circuit for executing the method in any possible implementation of the first aspect. BRIEF DESCRIPTION OF THE DRAWINGS

[0051] FIG1 is a functional block diagram of an intelligent driving device provided in an embodiment of the present application, and a schematic diagram of an EEA in the intelligent driving device;

[0052] FIG2 is a schematic diagram of an application scenario of the network configuration method provided in an embodiment of the present application;

[0053] FIG3 is a schematic flow chart of a network configuration method provided in an embodiment of the present application;

[0054] FIG4 is a set of GUIs provided in an embodiment of the present application;

[0055] FIG5 is another set of GUIs provided in an embodiment of the present application;

[0056] FIG6 is another schematic flowchart of the network configuration method provided in an embodiment of the present application;

[0057] FIG7 is another schematic flow chart of the network configuration method provided in an embodiment of the present application;

[0058] FIG8 is a schematic block diagram of a network configuration device provided in an embodiment of the present application;

[0059] FIG9 is another schematic block diagram of a network configuration device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0060] In the description of the embodiments of the present application, unless otherwise specified, " / " means or, for example, A / B can mean A or B; "and / or" in this article is a kind of association relationship that describes associated objects, indicating that there can be three relationships, for example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone. In this application, "at least one" refers to one or more, and "more than one" refers to two or more. "At least one of the following items" or similar expressions refers to any combination of these items, including any combination of single items or plural items. For example, at least one of a, b, or c can mean: a, b, c, ab, ac, bc, or abc, where a, b, c can be single or multiple.

[0061] In the embodiments of this application, prefixes such as "first" and "second" are used only to distinguish different description objects and have no limiting effect on the position, order, priority, quantity, or content of the described objects. The use of prefixes such as ordinal numbers in the embodiments of this application to distinguish description objects does not constitute a limitation on the described objects. For a statement of the described objects, please refer to the description in the context of the claims or embodiments, and the use of such prefixes should not constitute an unnecessary limitation.

[0062] As mentioned above, EEA involves one or more network interfaces, as well as the network relationships between one or more sensors and ECUs. These sensors and ECUs are interconnected via multiple communication protocols, resulting in complex and diverse network relationships. This makes planning and configuration of the communication architecture difficult and labor-intensive for developers, and prone to errors. In the current technological landscape, commonly used EEA design and communication architecture configuration solutions include the following:

[0063] First, the network architecture designer plans and designs the EEA based on business needs and outputs design documents (or configuration tables); further, the network configuration engineer communicates the network design intentions with the network architecture designer based on the design documents. After aligning the actual effects, the network configuration engineer manually configures and debugs the network on the actual physical machine.

[0064] Second, network configuration is performed using static tables: Network architects plan and design EEAs based on business requirements and produce design documents. Network configuration engineers then divide different in-vehicle network devices based on the design documents. Furthermore, they fill out static tables and use various specialized tools (or configuration interfaces) to configure different in-vehicle network devices using these static tables. Multiple configuration files are generated and distributed to different physical network devices for debugging.

[0065] Third, automatic generation of configuration table items is achieved through self-learning: the user configures the Internet Protocol (IP) address, media access control (MAC) address, and VLAN ID on each physical machine; the LAN switch obtains the VLAN ID of the message flowing through the switch port and matches it with the value in the VLAN ID list configured on the current switch port to determine whether to allow forwarding of the message; if the VLAN ID list includes the VLAN ID of the message, the IP address, MAC address and other information in the message are automatically obtained, and configuration tables such as ACL, ARL, and ARP table are automatically filled in based on the obtained information; if the VLAN ID list does not include the VLAN ID of the message, the forwarding fails, and the process of automatically learning configuration table items ends.

[0066] The first two network configuration schemes mentioned above have a small configuration granularity, generally targeting specific network devices within the EEA. This lacks the overall planning and configuration capabilities of the EEA design. Furthermore, EEA network configuration methods often rely on static table entries, which fail to intuitively reflect the relationships between network devices. The complex topology of the EEA architecture requires users to navigate multiple table attributes during configuration, increasing configuration time and complexity. Furthermore, the first two network configuration schemes require white-box configuration of multiple network configuration tables, resulting in a high number of duplicate configuration attributes, making it difficult for users to understand and maintain the network configuration. In the third network configuration scheme, network links are constantly learning during operation. This dynamic uncertainty can compromise network security, allowing attackers to inject attack information during the dynamic learning process. For example, if network configuration is performed using self-learning methods in the automotive sector, while the network links are in a dynamic learning state, attackers could potentially inject false information (such as brake signals or turn signals) through this dynamic network link, causing the vehicle to lose control and threatening the safety of the vehicle and its passengers. Therefore, the third network configuration scheme mentioned above fails to meet the high reliability and security requirements of the in-vehicle network sector.

[0067] In view of this, the present application provides a network configuration method and device that can generate network configuration information for on-board network devices during the development and design phase of the EEA based on the connection relationship between the on-board network devices planned by the user and the basic configuration of each network device. The generation and configuration of this network configuration information is completed during the development and design phase, and does not require configuration through a self-learning method during the actual operation of the on-board network device. Therefore, it can meet the requirements of the on-board network field for high reliability and high security of the network. In addition, the network configuration method and device provided by the present application can display the connection relationship between each network device in the EEA to the user, and provide the user with a window for configuring the basic configuration of each network device based on the connection relationship between each network device in the EEA, which helps save the user's time in communicating with the network architect during the configuration process and reduces the user's configuration workload.

[0068] The technical solutions in the embodiments of the present application will be described below with reference to the accompanying drawings.

[0069] (a) in Figure 1 (hereinafter referred to as Figure 1a) is a functional schematic diagram of the intelligent driving device 110 provided in an embodiment of the present application. As shown in Figure 1a, the intelligent driving device 110 includes a perception system 120 and a computing platform 150, wherein the perception system 120 may include several sensors for sensing information about the environment surrounding the intelligent driving device 110. For example, the perception system 120 may include a positioning system, and the positioning system may be a global positioning system (GPS), a Beidou system, or other positioning systems. For another example, the perception system 120 may also include one or more of an inertial measurement unit (IMU), a laser radar, a millimeter-wave radar, an ultrasonic radar, and a camera device.

[0070] Some or all functions of the intelligent driving device 110 can be controlled by the computing platform 150. The computing platform 150 may include processors 151 to 15n. A processor is a circuit capable of processing signals. In one implementation, a processor may be a circuit capable of reading and executing instructions, or it may implement certain functions through the logical relationships of hardware circuits. The logical relationships of the hardware circuits may be fixed or reconfigurable. Furthermore, the computing platform 150 may also include memory for storing instructions. Some or all of the processors 151 to 15n may call instructions from the memory to implement corresponding functions.

[0071] For example, the intelligent driving device involved in this application can be a vehicle in a broad sense, which can be a means of transportation (such as commercial vehicles, passenger cars, trucks, motorcycles, airplanes, flying cars, trains, ships, etc.), industrial vehicles (such as forklifts, trailers, tractors, etc.), engineering vehicles (such as excavators, bulldozers, cranes, etc.), agricultural equipment (such as mowers, harvesters, etc.), amusement equipment, toy vehicles, etc. This application does not specifically limit the type of vehicle.

[0072] In a specific implementation, the intelligent driving device 110 can be configured in a fully or partially autonomous driving mode, or can be manually driven by a user. For example, the intelligent driving device 110 can obtain environmental information about its surroundings through the perception system 120 and, based on analysis of this environmental information, derive an autonomous driving strategy to achieve fully autonomous driving, or present the analysis results to the user to achieve partially autonomous driving.

[0073] While traveling on a road, the intelligent driving device 110 can identify objects in its surroundings to adjust its current speed. These objects can be other vehicles, traffic control devices, or other types of objects. In some examples, each identified object can be considered independently, and the speed to be adjusted by the intelligent driving device 110 can be determined based on its respective characteristics, such as its current speed, acceleration, and distance from the intelligent driving device 110.

[0074] Optionally, the intelligent driving device 110 or a perception and computing device associated with the intelligent driving device 110 (e.g., computing platform 150) can predict the behavior of the identified object based on the characteristics of the identified object and the state of the surrounding environment (e.g., traffic, rain, ice on the road, etc.). Optionally, each identified object depends on the behavior of each other, so all identified objects can be considered together to predict the behavior of a single identified object.

[0075] In some possible implementations, the intelligent driving device 110 derives an autonomous driving strategy based on an analysis of the surrounding environment to achieve fully autonomous driving or partially autonomous driving. For example, FIG1(b) (hereinafter referred to as FIG1b ) illustrates an EEA in the intelligent driving device. As shown in FIG1b , the ECU can communicate with one or more sensors in the perception system 120 , such as GPS, a camera, radar, or lidar, based on the EEA, to obtain environmental information and / or information about objects surrounding the intelligent driving device 110, and then control the intelligent driving device 110 based on the environmental information and / or object information.

[0076] Exemplarily, the ECU supports one or more port protocols (or interface protocols) to enable communication with one or more sensors, communication components, and in-vehicle infotainment (IVI) systems. For example, the ECU supports a multimedia serial link (MSL) interface, such as a gigabit multimedia serial link (GMSL), enabling communication with a camera via an LVDS port based on GMSL. The ECU supports a UART port, enabling communication with positioning sensors such as GPS. The ECU supports an Ethernet port, enabling communication with lidar, gateways, and telematics boxes (T-boxes). The ECU supports a CAN port, enabling communication with radar (such as millimeter-wave radar, ultrasonic radar), gateways, and the like.

[0077] For example, the ECU shown in FIG1b may be the computing platform 150 shown in FIG1a . The computing platform 150 may include at least one of an advanced driving domain controller (ADC) (e.g., a mobile data center (MDC)), a vehicle domain controller (VDC), and a chassis domain controller (CDC). Alternatively, the computing platform 150 may also include other controllers, such as an in-car application-server (ICAS) controller, a body domain controller (BDC), a special equipment system (SAS), a media graphics unit (MGU), a body super core (BSC), an ADAS super core, etc., which are not limited in this application. The ICAS may include at least one of the following: a vehicle control server ICAS1, an intelligent driving server ICAS2, an intelligent cockpit server ICAS3, and an infotainment server ICAS4.

[0078] The above components are only an example. In actual applications, the components in the above modules may be added or deleted according to actual needs. Figure 1 should not be understood as a limitation on the embodiments of the present application.

[0079] In order to achieve communication between the components in Figure 1b, it is necessary to configure the ACL, ARL, ARP table, routing table and other configuration tables of the above components. For example, the ACL, ARL, ARP table, routing table and the like can be configured for the above components through the network configuration method of the present application.

[0080] Before introducing the network configuration method provided in the embodiment of the present application, the system architecture required for implementing the network configuration method provided in the embodiment of the present application and its application scenarios are first introduced.

[0081] Figure 2 shows a schematic diagram of an application scenario of the network configuration method provided in an embodiment of the present application. Exemplarily, the system to which the network configuration method is applied includes a development platform 200 and a target device 100. The network configuration information generated by the development platform 200 can be deployed to the target device 100. The target device 100 can test the network configuration information or communicate based on the network configuration information. Among them, the development platform 200 may include a connection relationship creation module 210, a basic configuration collection module 220, and a network configuration generation module 230. Specifically, the connection relationship creation module 210 can display a creation tool area to the user through a graphical user interface (GUI). The creation tool area may include an on-board network device object, a communication port object, and a hardware connection relationship object. Among them, the on-board network device object is used to create an on-board network device instance, the communication port object is used to create a port instance for communication of the on-board network device, and the hardware connection relationship object is used to create a link instance for communication between on-board network devices. It can be understood that each in-vehicle network device instance corresponds to a real in-vehicle network device in an intelligent driving device (such as a vehicle), each port instance corresponds to a real port used for communication of an in-vehicle network device, and each link instance corresponds to a real communication link between in-vehicle network devices. The connection relationship creation module 210 can establish a connection relationship between multiple in-vehicle network device instances according to user instructions and control the display device to display the connection relationship. The basic configuration collection module 220 is used to receive the basic configuration input by the user for the in-vehicle network device instance. The basic configuration may include one or more of the information such as IP address, MAC address, VLAN ID, etc. Further, the connection relationship creation module 210 sends the connection relationship between the above-mentioned multiple in-vehicle network device instances to the network configuration generation module 230, and the basic configuration collection module 220 sends the basic configuration corresponding to the multiple in-vehicle network device instances to the network configuration generation module 230. Based on the connection relationships among the multiple on-board network device instances and the basic configuration of each of the multiple on-board network device instances, the network configuration generation module 230 generates network configuration information, such as one or more items in the ACL, ARL, ARP table, and routing table, for each on-board network device corresponding to the on-board network device instance. Furthermore, developers or the development platform 200 can deploy the network configuration information generated by the network configuration generation module 230 to each on-board network device in the target device 100 (e.g., the intelligent driving device 110), thereby configuring the EEA communication architecture of the intelligent driving device.

[0082] In some possible implementations, the network configuration generation module 230 obtains the network device connection relationship from the connection relationship creation module 210 in response to a user instruction. For example, the user instruction may be an instruction generated based on a first user operation. The first operation may be an operation of sequentially clicking a hardware connection relationship object and an in-vehicle network device object, or an operation of dragging the hardware connection relationship object onto an in-vehicle network device instance.

[0083] Exemplarily, the above-mentioned in-vehicle network device may include the ECU in the above-mentioned embodiment, sensors (such as one or more sensors in the perception system 120), etc.

[0084] In some possible implementations, the development platform 200 may also generate network configuration information for each network device in the model based on an imported model, wherein the imported model includes multiple network devices, connection relationships between the multiple network devices, and basic configurations for each of the multiple network devices. In the above implementation, the connection relationship creation module 210 may parse the connection relationships between the multiple network devices in the imported model. The basic configuration collection module 220 may extract the basic configurations for each of the multiple network devices, and the network configuration generation module 230 may generate network configuration information for each of the multiple network devices in the imported model based on the connection relationships parsed by the connection relationship creation module 210 and the basic configurations extracted by the basic configuration collection module 220.

[0085] The above modules and devices are only examples. In actual applications, the above modules and devices may be added or deleted according to actual needs. In one example, the connection relationship creation module 210 and the basic configuration collection module 220 can be combined into one module, that is, the functions of the two are implemented by one module.

[0086] FIG3 shows a schematic flow chart of a network configuration method provided in an embodiment of the present application. Method 300 can be executed by the development platform 200 shown in FIG2 , or by a system-on-chip (SoC) in the development platform 200, or by a processor in the development platform 200. The following describes method 300 using the development platform as an example. Method 300 may include steps S301 to S303.

[0087] S301 , establishing connection relationships between a plurality of network devices according to a user instruction, where the plurality of network devices are vehicle-mounted network devices.

[0088] Exemplarily, the in-vehicle network device may include one or more sensors in the above embodiments, and one or more ECUs.

[0089] In some possible implementations, before establishing a connection relationship between multiple network devices according to a user instruction, a display device is controlled to display a first interface, wherein the first interface includes a display area and a creation tool area, wherein the creation tool area includes multiple network device objects of different types, and the multiple network device objects of different types are used to create the multiple network devices. After establishing the connection relationship between the multiple network devices according to the user instruction, the connection relationship between the multiple network devices is displayed in the display area of ​​the first interface.

[0090] Illustratively, the display device may be a display screen of an electronic device on which the development platform 200 is deployed, or may be other display devices associated with the development platform 200 .

[0091] In some possible implementations, the connection relationship between the multiple network devices includes a type of a communication port of each of the multiple network devices, where the communication port is a port connected to other network devices.

[0092] Exemplarily, the types of the communication ports include Ethernet ports, UART ports, LVDS ports, or CAN ports. More specifically, the Ethernet ports may include ETH ports and Switch ports, wherein the ETH port serves as a source port or a destination port for Ethernet communication, and the Switch port is used to forward Ethernet messages.

[0093] In some possible implementations, the creation tool area further includes a communication port object and a hardware connection relationship object, wherein the communication port object is used to create a communication port on a network device, and the hardware connection relationship object is used to create a connection relationship between communication ports.

[0094] S302: Obtain a basic configuration of each network device among the multiple network devices, where the basic configuration of each network device includes address information of each network device.

[0095] Exemplarily, the address information of a network device may include at least one of an IP address, a MAC address, and a VLAN ID.

[0096] It should be understood that the address information of a network device may include multiple IP addresses, or multiple MAC addresses, or multiple VLAN IDs.

[0097] In some possible implementations, obtaining the basic configuration of each of the multiple network devices may include: in response to an operation on a first network device, controlling a display device to display a second interface, and obtaining the basic configuration of the first network device through the second interface, where the first network device is any one of the multiple network devices.

[0098] S303: Generate network configuration information for each network device according to the connection relationship between the multiple network devices and the basic configuration of each network device.

[0099] Exemplarily, the network configuration information may include one or more of ACL, ARL, ARP table, and routing table.

[0100] In some possible implementations, generating network configuration information for each network device may include: determining the communication relationship between the multiple network devices based on the type of the communication port of each network device in the multiple network devices and the basic configuration of each network device; and generating network configuration information for each network device based on the communication relationship between the multiple network devices.

[0101] For example, a network device may include one or more Ethernet sub-devices, wherein each Ethernet sub-device is used to process Ethernet packets. The one or more Ethernet sub-devices may be in one VLAN, or the one or more Ethernet sub-devices may be in multiple VLANs.

[0102] Exemplarily, the Ethernet sub-device can be a device in a network device for processing Ethernet messages. The Ethernet sub-device can include an ETH device and / or a virtual ETH device, wherein the ETH device is a device that has a physical connection relationship with an external device or a communication port, and the virtual ETH device is a virtual sub-network card device abstracted from the ETH device.

[0103] In some possible implementations, the basic configuration of each network device includes the VLAN ID of each network device, and determining the communication relationship between the multiple network devices includes: determining the communication relationship between the multiple network devices based on the type of the communication port of each network device in the multiple network devices and the VLAN ID of each network device.

[0104] For example, in one or more network device sets consisting of Ethernet sub-devices of multiple network devices, the communication relationships between the multiple network devices may include: communication relationships between the Ethernet sub-devices in each network device set, wherein the Ethernet sub-devices in a network device set are in the same VLAN (i.e., have the same VLAN ID); or, although the Ethernet sub-devices in a network device set are not in the same VLAN, they can communicate with each other (i.e., the VLAN IDs of the Ethernet sub-devices in the set are all empty).

[0105] In some possible implementations, the basic configuration of each network device also includes a data flow configuration, which indicates the constraints on the data flow generated when the network device provides services, and the constraints on the data flow include one or more of the direction of the data flow, the transmission speed of the data flow, and the priority of the data flow. The method 300 also includes: controlling the display device to display a third interface, and the third interface includes one or more of the direction of the data flow, the transmission speed of the data flow, and the priority of the data flow between the multiple network devices.

[0106] In some possible implementations, the third interface and the first interface may be the same interface.

[0107] In some possible implementations, the network configuration information may further include configuration information related to one or more of a CAN port, an LVDS port, and a UART port.

[0108] It should be noted that the multiple network devices involved in the embodiments of the present application may be instances of the on-board network devices in the above-mentioned embodiments, which represent actual on-board network devices in the intelligent driving device. The communication ports of the network devices may be instances of the ports used for communication in the on-board network devices in the above-mentioned embodiments, which represent actual ports used for communication in the on-board network devices in the intelligent driving device. It is understood that the "connection relationship between the multiple network devices" in the embodiments of the present application corresponds to the connection relationship between the actual on-board network devices in the intelligent driving device. Furthermore, the "network configuration information generated for each network device" in the embodiments of the present application may be deployed on the actual on-board network devices of the intelligent driving device to enable communication between the actual on-board network devices.

[0109] The network configuration method provided in the embodiments of the present application can display the connection relationship between each network device in the EEA to the user during the development and design phase of the EEA, and based on the connection relationship between each network device in the EEA, provide the user with a window for configuring the basic configuration of each network device, which helps save the user's time in communicating with the network architect during the configuration process and reduces the user's configuration workload. Furthermore, it can generate network configuration information for the vehicle network device based on the connection relationship between the vehicle network devices designed by the user and the basic configuration input by the user. The generation and configuration of this network configuration information is completed during the development and design phase, and does not require configuration through self-learning methods during the actual operation of the vehicle network device. Therefore, it can meet the requirements of the vehicle network field for high network reliability and high security.

[0110] FIG4 shows a schematic diagram of a GUI provided in an embodiment of the present application, which can be understood as an example of the first interface in method 300. As shown in FIG4 , the GUI includes a display area and a creation tool area, wherein the creation tool area includes a network device object, a communication port object, and a hardware connection relationship object.

[0111] Exemplarily, network device objects include "ECU", "Gateway", "Lidar", "USS", "Radar", "IFC", "INS", "GPS", "IMU", and "LMU", which are respectively used to create ECU, gateway, lidar, ultrasonic sensor, radar, vehicle-mounted camera, inertial navigation system, global positioning system, inertial measurement unit, and tension-compression bidirectional sensor. Communication port objects include "Switch Port" and "Ethernet Port" for creating Ethernet ports, "LVDS Port" for creating LVDS ports, "CAN Port" for creating CAN ports, and "UART Port" for creating UART ports. More specifically, "Switch Port" is used to create a Switch port for forwarding messages, and "Ethernet Port" is used to create an ETH port as a communication source or destination. Hardware connection relationship objects include "Ethernet Relation", "CAN Relation", "LVDS connected", and "UART Relation", which are respectively used to complete Ethernet connection, CAN port connection, LVDS port connection, and UART port connection. The topological structure between network devices displayed in this display area can be understood as an example of "the connection relationship between multiple network devices".

[0112] The following uses the topology of network devices displayed in the display area of ​​FIG4 as an example to illustrate one implementation of "establishing connection relationships between multiple network devices according to user instructions" in S301. For example, "establishing connection relationships between multiple network devices according to user instructions" may include the following steps 1 to 3.

[0113] Step 1: Create a network device in the display area according to the user's instructions. Exemplarily, the user instructions may include at least one of the following: an instruction generated by detecting that a network device object in the creation tool area and a blank area in the display area are clicked in succession; or an instruction generated by detecting that a network device object in the creation tool area is dragged to a blank area in the display area; or an instruction generated according to other user operations. For example, if the user clicks on the network device object "Radar" and then clicks on a blank area in the display area, then when the above operation is detected, a network device - radar (as shown in "Radar_left" or "Radar_right" in FIG4 ) is created and displayed in the display area.

[0114] Step 2: Establish a communication port for the network device according to the user's instructions. For example, the user instructions may include at least one of the following: an instruction generated by detecting that a communication port object and a network device in the creation tool area are clicked in sequence; or an instruction generated by detecting that a communication port object in the creation tool area is dragged to a network device; or an instruction generated according to other user operations. For example, if the user drags the communication port "CAN Port" object to the network device "Radar_left", then when the above operation is detected, an association relationship between "Radar_left" and "CAN Port" is established, and the display area shows that the radar has a CAN communication port (as shown in Figure 4, "Radar_left" and its communication port "can1").

[0115] Step 3: Establish a connection relationship between the two network devices according to user instructions. Exemplarily, the user instructions may include at least one of the following: an instruction generated by detecting that a hardware connection relationship object and the communication ports of two network devices in the creation tool area are clicked in succession; or an instruction generated according to other user operations. For example, the user first clicks the hardware connection relationship object "LVDS connected", and then clicks the communication port "lvds1" on the "Camera" and the communication port "D4" on the "ECU" in succession. When the above operations are detected, a GMSL connection is established between the communication port "lvds1" of the "Camera" and the communication port "D4" of the "ECU", and the connection relationship is displayed in the display area.

[0116] It can be understood that the establishment of the EEA topology structure shown in the display area in FIG4 can be completed through the above steps 1 to 3.

[0117] FIG5 illustrates a schematic diagram of a GUI provided in an embodiment of the present application. As shown in FIG5 , the GUI includes a second interface. Basic configuration of a first network device among multiple network devices can be obtained through user input on the second interface. In some possible implementations, obtaining the basic configuration of the first network device can include at least one of the following: displaying a second interface in response to a click on the first network device, and obtaining the basic configuration of the first network device through the second interface; or displaying a second interface in response to a click on a communication port of the first network device, and obtaining the basic configuration of the first network device (or the communication port) through the second interface. For example, taking the first network device as an "ECU," when a user clicks on the "B1" port on the "ECU," the second interface shown in FIG5 can be displayed. The second interface includes information in a property bar. The user can enter basic configuration information in the property bar, such as a VLAN list, an IP address, a MAC address, and the like. For example, the user can enter the VLAN ID of the VLAN supported by the "B1" port in the VLAN list.

[0118] Furthermore, in response to detecting the user's input in the property column, the basic configuration of the "ECU" is obtained.

[0119] It should be noted that when the first network device has multiple communication ports, a second interface is displayed in response to an operation on the first network device. The basic configuration of the first network device obtained through the second interface may include the basic configuration of one or more communication ports of the first network device.

[0120] For example, in order to implement the network configuration method provided in the embodiment of the present application, in the development platform for executing the network configuration method of the present application, element models can be defined for various types of ECUs (and / or sensors), communication ports, and hardware connection relationships involved in "establishing connection relationships between multiple network devices", which can specifically include the following categories:

[0121] 1. AbstractEcu element model: This is the common parent class of all ECU and sensor types. This class contains a collection of communication ports of all protocol types. For example, the "GPS," "Camera," "Radar," "Lidar," and "ECU" shown in Figures 4 and 5 are all subclasses of this class and inherit its properties. For example, the properties of this class include one or more of the following:

[0122] ETH port list: a list of ETH ports used by ECU or sensor. An ECU or sensor can have multiple ETH ports.

[0123] CAN port list: A list of CAN ports that the ECU or sensor uses for communication using CAN or controller area network–flexible data (CAN-FD). An ECU or sensor can have multiple CAN ports.

[0124] UART port list: a list of UART ports that the ECU or sensor uses for UART communication. An ECU or sensor can have multiple UART ports.

[0125] LVDS port list: a list of LVDS ports that the ECU or sensor uses for LVDS communication. An ECU or sensor can have multiple LVDS ports.

[0126] ETH device list: a list of ETH devices that process Ethernet messages on an ECU or sensor. An ECU or sensor can have multiple ETH devices.

[0127] CAN device list: a list of CAN devices on the ECU or sensor that process CAN messages. An ECU or sensor can have multiple CAN devices.

[0128] LanSwitch list: a list of switch devices on an ECU or sensor. An ECU or sensor can have multiple LanSwitch devices (hereinafter referred to as Switch devices).

[0129] For example, in step 2 of the above embodiment, when a communication port is established for a network device according to a user instruction, the information of the communication port is added to the corresponding communication port list under the element model of the network device. For example, if a CAN communication port "can1" is established for the network device "Radar_left" according to a user instruction, "can1" is added to the "CAN Port List" of "Radar_left".

[0130] 2. LanSwitch element model: A switch (which can be a switching unit) inside an ECU or sensor, used to interconnect multiple network devices and multiple communication ports, with the following properties:

[0131] Name: globally uniquely identifies the current switch;

[0132] Switch port list: used to store the collection of all switch ports on the current switch.

[0133] 3. Switch port element model: The port on the switch device used for packet forwarding. The specific attributes are as follows:

[0134] Channel ID: globally uniquely identifies the current switch port, such as "swp1", "swp2", and "swp3" as shown in Figure 4;

[0135] VLAN list: A list that stores VLAN IDs and is used to record the VLANs in which the current switch port can exist.

[0136] Connected port: This property is used to record that the connection relationship between the current Switch port and another Switch port (or ETH port) is created through a hardware connection object.

[0137] For example, when establishing a connection between two network devices according to a user instruction in step 3 of the above embodiment, information about the peer communication port can be added to the corresponding Connected Ports under the communication port element models of the two network devices. For example, when establishing a connection between the Switch port "swp1" of the network device "Gateway" and the ETH port "B1" of the network device "ECU" according to a user instruction, "B1" can be added to the "Connected Port" of "swp1".

[0138] 4.ETH port element model: The port used by an ECU or sensor for Ethernet communication has the following properties:

[0139] Channel ID: globally uniquely identifies the current ETH port, such as "p1" and "p2" in Figure 4;

[0140] VLAN list: a list that stores VLAN IDs, used to record which VLANs the current ETH port can exist in;

[0141] Connected port: This property is used to record that the connection relationship between the current ETH port and another ETH port (or Switch port) is created through a hardware connection object.

[0142] For example, when establishing a connection between two network devices according to user instructions in step 3 of the above embodiment, information about the other communication port can be added to the corresponding Connected Ports under the communication port element models of the two network devices. For example, when establishing a connection between the ETH port "p2" of the network device "Lidar_right" and the Switch port "swp2" of the network device "Gateway" according to user instructions, "swp2" can be added to the "Connected Port" of "p2".

[0143] 5.ETH device element model: A device on an ECU or sensor that processes Ethernet messages and has the following properties:

[0144] ETH Name: globally uniquely identifies the current ETH device;

[0145] Connected port: identifies which ETH port (or Switch port) the current ETH device uses to connect to the outside world;

[0146] Virtual ETH device list: stores the list of virtual ETH devices on the current network;

[0147] IP list: used to store the IP address set on the current ETH device;

[0148] MAC list: used to configure the MAC address of the current ETH device;

[0149] Data flow list: used to store the list of data flows generated when the current ETH device provides services. Each data flow in the data flow list is set with the "data flow configuration" attribute.

[0150] Exemplarily, an ECU or sensor may include one or more ETH devices. The basic configuration of the first network device obtained through the second interface in the above embodiment can be added to the "IP list" and "MAC list" under the ETH device element model of the first network device.

[0151] Illustratively, the ETH device may be an example of the Ethernet sub-device in the above embodiment.

[0152] 6. Virtual ETH device element model: A virtual sub-NIC device abstracted from the ETH device, with the following properties:

[0153] VLANID: identifies the VLAN in which the current virtual ETH device is located;

[0154] IP list: used to store the IP address set on the current virtual ETH device;

[0155] MAC list: used to configure the MAC address of the current virtual ETH device;

[0156] Data flow list: used to store the list of data flows generated when the current virtual ETH device provides services. Each data flow in the data flow list is set with the "data flow configuration" attribute.

[0157] 7. Data flow configuration: This field identifies the constraints of the current data flow. The constraints include one or more of the following: the direction of the data flow, the transmission speed of the data flow, and the priority of the data flow. It has the following attributes:

[0158] SourceIP: The IP address of the host that sends the data stream;

[0159] SourcePort: The port used by the host sending the data stream to provide external services;

[0160] DestIP: The IP address of the host receiving the data stream;

[0161] DestPort: The port used by the host receiving the data stream to provide external services;

[0162] Protocol: the protocol used for data stream transmission;

[0163] Description: The specific functions provided by the data flow;

[0164] Transmission speed: describes the transmission rate of the data stream;

[0165] Priority: Describes the priority of the data flow.

[0166] Among them, SourceIP, SourcePort, DestIP, and DestPort can be summarized as the direction of data flow.

[0167] 8.CAN port element model: The connection port of the ECU or sensor using CAN / CANFD communication has the following properties:

[0168] Channel ID: globally uniquely identifies the current CAN port, for example, "swCan1", "swCan2", "can1", "can2" as shown in Figure 4;

[0169] Connected port: This property is used to record that the connection relationship between the current CAN port and another CAN port is created through a hardware connection object.

[0170] 9. CAN device element model: The device on the ECU or sensor that processes CAN communication messages has the following properties:

[0171] CAN Name: globally uniquely identifies the current CAN device;

[0172] Connected port: identifies which CAN port the current CAN device uses to connect to the outside world;

[0173] CANID list: a list used to store the CANID of the current CAN device, where CANID is the address value under the CAN protocol.

[0174] 10. UART port element model: The port used by the ECU or sensor to communicate using UART has the following properties:

[0175] Channel ID: globally uniquely identifies the current UART port, for example, "uart1" as shown in Figure 4;

[0176] Connected port: This property is used to record that the connection relationship between the current UART port and another UART port is created through a hardware connection object.

[0177] 11.LVDS port element model: The port of the ECU or sensor using LVDS communication has the following properties:

[0178] Channel ID: globally uniquely identifies the current LVDS port, for example, "lvds1" as shown in Figure 4;

[0179] Connected port: This property is used to record the connection relationship between the current LVDS port and another LVDS port created through a hardware connection object.

[0180] FIG6 shows a schematic flow chart of a network configuration method provided in an embodiment of the present application. Method 600 can be executed by the network configuration generation module 230 in the development platform 200 shown in FIG2 , or can also be executed by the development platform 200, or can also be executed by the SoC in the development platform 200, or can also be executed by the processor in the development platform 200. Method 600 is executed in parallel with method 300, or can also be executed after method 300. Method 600 can be regarded as an extension of method 300. For example, method 600 is a detailed introduction to S303 in method 300. Method 600 can include steps S601 to S611.

[0181] S601 : Taking a first switch as a starting point, determine a first switch port set of the first switch.

[0182] For example, the first switch may be a switch within one of the multiple network devices in the above embodiments, such as an ECU (such as the "ECU" shown in Figures 4 and 5) or a switch within a sensor; or the first switch may be a gateway used only for switching functions (such as the "Gateway" shown in Figures 4 and 5). The first switch port set includes all switch ports on the first switch.

[0183] Exemplarily, the first switch port set may be determined according to the “switch port list” of the first switch.

[0184] S602: Determine whether the communication ports are connected based on the connection relationship between the network devices.

[0185] Specifically, if the communication port is connected, execute S603; otherwise, execute S611.

[0186] Exemplarily, the communication port may be a port in the first Switch port set; or may be an ETH port in S606 .

[0187] Exemplarily, the connection relationship may be a hardware connection relationship, that is, a connection relationship established through a hardware connection relationship object.

[0188] In some possible implementations, whether the communication port is connected is determined based on whether the “Connected port” of the communication port is empty. If the “Connected port” is empty, it means that the communication port is not connected.

[0189] S603: Obtain the network device or port to which the communication port is connected.

[0190] S604: Determine whether the peer device is an ETH device.

[0191] Specifically, if the opposite end is connected to an ETH device, execute S605; otherwise, execute S606.

[0192] S605: Search for an ETH device and / or a virtual ETH device according to the VLAN ID, and add the ETH device and / or the virtual ETH device to a network device set corresponding to the VLAN ID.

[0193] Exemplarily, the communication port may exist in one or more VLANs, and correspondingly, the “VLAN list” of the communication port may include one or more VLAN IDs, or the “VLAN list” of the communication port may be empty.

[0194] In some possible implementations, a virtual ETH device with the same VLAN ID as each VLAN ID is searched for on the ETH device based on all VLAN ID values ​​in the communication port's "VLAN List." If a virtual ETH device with the same VLAN ID as each VLAN ID is found, indicating a virtual connection relationship exists between the communication port and the virtual ETH device within the VLAN corresponding to the current VLAN ID value, the virtual ETH device is then added to the network device set corresponding to the current VLAN ID value. A "virtual connection relationship" indicates that two communication ports do not have a hardware connection relationship, but communication between them is still possible.

[0195] In some possible implementations, if the "VLAN list" of the communication port is empty, the ETH device found based on the hardware connection relationship is directly added to the network device set corresponding to the empty VLAN ID.

[0196] In some possible implementations, for each ETH device and / or virtual ETH device in a network device set, it is necessary to record which Switch port of the first switch is used as the starting point for determination, so that the set corresponding to each VLAN ID is globally unique, and it is ensured that the ETH devices and / or virtual ETH devices found through a VLAN ID are all in the same network device set.

[0197] S606: Determine whether the peer end is connected to an ETH port.

[0198] Specifically, if the opposite end is connected to an ETH port, S602 is executed, that is, taking the ETH port as a starting point, it is determined whether the ETH port is connected according to the connection relationship between network devices; otherwise, S607 is executed.

[0199] Exemplarily, if the opposite end is connected to an ETH port, determine whether the VLAN ID list of the network device or port has a VLAN ID that is the same as the first VLAN ID in the VLAN ID list of the communication port. If there is an intersection, add the network device or the network device corresponding to the port to the network device set corresponding to the first VLAN ID.

[0200] In some possible implementations, the VLAN ID list on the communication port is used as the duplicate VLAN ID list, and a determination is made as to whether the duplicate VLAN ID list intersects with the VLAN ID list on the peer ETH port. If so, indicating a virtual connection exists between the communication port and the peer ETH port, the duplicate VLAN ID list is updated. This updated duplicate VLAN ID list includes the intersection of the communication port's VLAN ID list and the peer ETH port's VLAN ID list. It will be appreciated that this updated duplicate VLAN ID list indicates which VLANs the communication port and the peer ETH port share. If there is no intersection, indicating a link failure, the search is discontinued.

[0201] It should be noted that if and only if the VLAN ID list of the communication port and the VLAN ID list of the peer ETH port are both empty, the peer ETH port is added to the set of ETH ports with empty VLAN IDs. These ETH ports with empty VLAN IDs do not communicate using VLANs, but some ETH ports can communicate through other means, such as through physical connections. Furthermore, based on connection relationships, ETH ports with empty VLAN IDs that can communicate with each other can be identified. The network devices corresponding to these ETH ports constitute a network device set, and the VLAN ID corresponding to this network device set is empty.

[0202] S607: Determine whether the opposite end is connected to a switch port.

[0203] Specifically, if the opposite end is connected to a switch port, execute S608; otherwise, execute S611.

[0204] S608: Obtain a switch port list set on the second switch where the switch port is located.

[0205] Exemplarily, all switch ports on the second switch where the switch port is located except the current switch port are obtained as the switch port list set.

[0206] S609: Determine whether the VLAN ID lists of the first switch and the second switch have an intersection.

[0207] Specifically, if the VLAN ID lists of the first switch and the second switch have an intersection, execute S610; otherwise, execute S611.

[0208] S610 : Determine a second switch port set based on switch ports in the second switch that intersect with the VLAN ID list of the first switch, and select a switch port from the set.

[0209] In some possible implementations, the VLAN ID list on the communication port is used as a duplicate VLAN ID list. It is determined whether the duplicate VLAN ID list and the VLAN ID list on the opposite switch port have an intersection. If there is an intersection, it indicates that a virtual connection relationship exists between the communication port and the opposite switch port. In this case, the duplicate VLAN ID list is updated. The updated duplicate VLAN ID list (hereinafter referred to as the second duplicate VLAN ID list) includes the intersection of the VLAN ID list of the communication port and the VLAN ID list of the opposite switch port.

[0210] Furthermore, the VLAN ID list of each switch port in the switch port list, excluding the switch port at the opposite end of the communication port, is sequentially compared with the second repeated VLAN ID list to determine all switch ports whose VLAN ID lists intersect with the second repeated VLAN ID list. These all switch ports constitute a second switch port set. Furthermore, the repeated VLAN ID list is updated for each switch port in the second switch port set, excluding the switch port at the opposite end of the communication port. The updated repeated VLAN ID list includes the intersection of the second repeated VLAN ID list and the VLAN ID list of the switch port. If the second repeated VLAN ID list is empty, all switch ports whose VLAN ID lists are empty are directly found in the switch port list set and used as the second switch port set.

[0211] Further, continue to execute S603.

[0212] S611, end.

[0213] It is understandable that, through the above method 600, multiple network devices can be divided into one or more network device sets, wherein each network device set has the same VLAN ID and is in the same broadcast domain.

[0214] Exemplarily, S604 to S610 may be summarized as: determining the communication relationship between the multiple network devices according to the type of the communication port of each network device and the basic configuration of each network device, wherein the basic configuration includes a VLAN ID.

[0215] Exemplarily, S601 to S611 may be summarized as: determining the communication relationship between the multiple network devices according to the type of the communication port of each network device in the multiple network devices and the VLAN ID of each network device.

[0216] FIG7 shows a schematic flow chart of a network configuration method provided in an embodiment of the present application. Method 700 can be executed by network configuration generation module 230 in development platform 200 shown in FIG2 , or by development platform 200, or by a SoC in development platform 200, or by a processor in development platform 200. Method 700 can be executed in parallel with method 300, or after method 300. Method 700 can be considered an extension of method 300; method 700 can be executed after method 600. Method 700 can include steps S701 and S702.

[0217] S701: Generate network configuration information for each network device according to a network device set and basic configuration of each Ethernet sub-device in the set.

[0218] Exemplarily, the network configuration information may be the network configuration information in the above embodiment, for example, may include at least one of an ACL, an ARL, an ARP table, and a routing table.

[0219] Exemplarily, the basic configuration may include one or more of an IP address, a MAC address, a data flow configuration, and a VLAN ID.

[0220] In some possible implementations, when the network device includes one or more switches, an ACL and / or ARL table is generated for each of the one or more switches. Furthermore, an ARP table and a routing table are generated for each network device.

[0221] In one example, the VLAN ID of a network device set is obtained, the starting switch port of the set is determined, and the MAC addresses (including multicast and unicast MAC addresses) of all Ethernet sub-devices within the set are determined. Based on these MAC addresses and in accordance with commonly used ARL table entry formats and content specifications, an ARL table is generated for the switch where the starting switch port resides. For example, an ARL table may not be generated for Ethernet sub-devices in a network device set with an empty VLAN ID.

[0222] In another example, the data flow configurations of all Ethernet sub-devices within a network device set are obtained. Based on the SourceIP, SourcePort, DestIP, DestPort, Protocol, and description in the data flow configurations, and in accordance with industry-standard ACL table entry formats and content specifications, an ACL table is generated for the switch where the source switch port resides. In some possible implementations, the IP addresses of all Ethernet sub-devices within the network device set can be used as candidate values ​​for SourceIP, avoiding manual entry by the user and the resulting IP address mismatch.

[0223] In another example, because a network device set is within a VLAN (i.e., within a broadcast domain), ARP packets can be forwarded to all Ethernet sub-devices within the network device set. Each Ethernet sub-device within the network device set is traversed, and the IP address and MAC address of the currently traversed Ethernet sub-device are recorded. Based on these IP and MAC addresses, a full ARP table is generated based on the VLAN ID of the network device set. Furthermore, based on this full ARP table, an ARP table corresponding to the VLAN ID of each Ethernet sub-device is generated for each network device within the network device set.

[0224] In another example, each Ethernet sub-device in the network device set is traversed, the IP address of the currently traversed Ethernet sub-device is recorded, and whether the IP address belongs to the host or the gateway is recorded. Based on the VLAN ID of the network device set and the IP address, a local routing table corresponding to the VLAN ID is generated for each network device where the Ethernet sub-device is located;

[0225] S702: Generate network configuration information for all network devices corresponding to the network device set.

[0226] Exemplarily, for different sets of network devices, S701 is repeated to further generate network configuration information for “each network device in the plurality of network devices”.

[0227] It should be noted that a network device may include multiple Ethernet sub-devices, which belong to different network device sets. The network configuration information generated for the multiple Ethernet sub-devices based on different network device sets constitutes the network configuration information of the network device.

[0228] Exemplarily, the method 600 and the method 700 can be summarized as follows: generating network configuration information for each network device according to the connection relationship between the multiple network devices and the basic configuration of each network device.

[0229] The embodiments of the present application mainly illustrate a method for generating network configuration information for a network device based on an Ethernet sub-device and / or an Ethernet port. In some possible implementations, the network configuration information of the embodiments of the present application may also include configuration information related to a CAN port, a LVDS port, and a UART port. For example, based on the connection relationship between multiple network devices provided in the embodiments of the present application, configuration information related to a CAN port, a LVDS port, and a UART port may be generated. For example, based on the connection relationship between multiple network devices, the LVDS ports that need to communicate with each other are determined (for example, which LVDS ports need to communicate can be determined based on the "Connected port" attribute of the LVDS port), and then configuration information for communicating through the LVDS port is generated for the network device; for another example, based on the connection relationship between multiple network devices, the UART ports that need to communicate with each other are determined (for example, which LVDS ports need to communicate can be determined based on the "Connected port" attribute of the UART port), and then configuration information for communicating through the UART port is generated for the network device; for another example, based on the connection relationship between multiple network devices, the network link for communicating through the CAN port is determined, and then based on information such as the Channel ID of the CAN port and the CAN communication forwarding filter table, configuration information for communicating through the CAN port is generated for the network device.

[0230] In the various embodiments of the present application, unless otherwise specified or there is a logical conflict, the terms and / or descriptions between the various embodiments are consistent and can be referenced by each other. The technical features in different embodiments can be combined to form new embodiments according to their inherent logical relationships.

[0231] The method provided in the embodiments of the present application is described in detail above with reference to Figures 1 to 7 . The apparatus provided in the embodiments of the present application will be described in detail below with reference to Figures 8 and 9 . It should be understood that the description of the apparatus embodiment corresponds to the description of the method embodiment. Therefore, for matters not described in detail, reference can be made to the method embodiment above, and for the sake of brevity, no further description will be given here.

[0232] FIG8 shows a schematic block diagram of a network configuration device 800 provided in an embodiment of the present application. The device 800 includes a first processing unit 810 , an acquiring unit 820 , and a generating unit 830 .

[0233] The apparatus 800 may include units for executing the methods in Figures 3, 6, and 7. Furthermore, each unit in the apparatus 800 is for implementing the corresponding process of the method embodiments in Figures 3, 6, and 7, respectively.

[0234] When the device 800 is used to execute the method 300 in Figure 3, the first processing unit 810 can be used to execute S301 in the method 300, the acquisition unit 820 can be used to execute S302 in the method 300, and the generation unit 830 can be used to execute S303 in the method 300.

[0235] Exemplarily, the first processing unit 810 is used to establish a connection relationship between multiple network devices according to user instructions, and the multiple network devices are vehicle-mounted network devices; the acquisition unit 820 is used to obtain the basic configuration of each network device in the multiple network devices, and the basic configuration of each network device includes the address information of each network device; the generation unit 830 is used to generate network configuration information for each network device based on the connection relationship between the multiple network devices and the basic configuration of each network device.

[0236] Optionally, the apparatus further includes a second processing unit configured to control the display device to display a first interface, where the first interface includes connection relationships between the plurality of network devices.

[0237] Optionally, the first interface includes a display area and a creation tool area, the creation tool area includes multiple network device objects of different types, the multiple network device objects of different types are used to create the multiple network devices, and the display area is used to display the connection relationship between the multiple network devices.

[0238] Optionally, the connection relationship between the multiple network devices includes the type of a communication port of each network device in the multiple network devices, and the communication port is a port connected to other network devices.

[0239] Optionally, the type of the communication port includes an Ethernet port, a UART port, a LVDS port, or a CAN port.

[0240] Optionally, the device also includes a determination unit for determining the communication relationship between the multiple network devices based on the type of the communication port of each network device and the basic configuration of each network device; the generation unit 830 is used to generate network configuration information for each network device based on the communication relationship between the multiple network devices.

[0241] Optionally, the basic configuration of each network device also includes a virtual local area network identifier VLAN ID of the network device, and the determination unit is used to determine the communication relationship between the multiple network devices according to the type of the communication port of each network device in the multiple network devices and the VLAN ID of each network device.

[0242] Optionally, the device also includes a third processing unit, which is used to: control the display device to display a second interface in response to an operation on the first network device, where the first network device is any one of the multiple network devices; the acquisition unit 820 is used to: obtain the basic configuration of the first network device through the second interface.

[0243] Optionally, the basic configuration of each network device also includes a data flow configuration, which indicates the constraints on the data flow generated when the network device provides services, and the constraints on the data flow include one or more of the direction of the data flow, the transmission speed of the data flow, and the priority of the data flow. The device also includes a fourth processing unit, which is used to: control the display device to display a third interface, and the third interface includes one or more of the direction of the data flow, the transmission speed of the data flow, and the priority of the data flow between the multiple network devices.

[0244] Optionally, the network configuration information includes one or more items of ACL, ARL, ARP table, and routing table.

[0245] Exemplarily, the first processing unit 810 may be provided in the connection relationship creation module 210 shown in FIG2 , the acquisition unit 820 may be provided in the basic configuration collection module 220 shown in FIG2 , and the generation unit may be provided in the network configuration generation module 230 shown in FIG2 . Exemplarily, the second processing unit may be provided in the connection relationship creation module 210 shown in FIG2 , the third processing unit may be provided in the basic configuration collection module 220 shown in FIG2 , the fourth processing unit may be provided in the connection relationship creation module 210, and the determination unit may be provided in the network configuration generation module 230.

[0246] It should be understood that the division of the various units in the above device is merely a division of logical functions. In actual implementation, they may be fully or partially integrated into a single physical entity, or they may be physically separated. In addition, the units in the device may be implemented in the form of a processor calling software; for example, the device includes a processor, the processor is connected to a memory, and the memory stores instructions. The processor calls the instructions stored in the memory to implement any of the above methods or the functions of the various units of the device, where the processor is, for example, a general-purpose processor such as a CPU or a microprocessor, and the memory is a memory within the device or a memory outside the device. Alternatively, the units in the device can be implemented in the form of hardware circuits, and the functions of some or all of the units can be realized by designing the hardware circuits. The hardware circuit can be understood as one or more processors. For example, in one implementation, the hardware circuit is an application-specific integrated circuit (ASIC), which realizes the functions of some or all of the above units by designing the logical relationship of the components in the circuit. For another example, in another implementation, the hardware circuit can be implemented by a programmable logic device (PLD). Taking a field programmable gate array (FPGA) as an example, it can include a large number of logic gate circuits, and the connection relationship between the logic gate circuits is configured by configuring the configuration file, thereby realizing the functions of some or all of the above units. All units of the above devices can be implemented in the form of software called by the processor, or in the form of hardware circuits, or in part by software called by the processor, and the rest by hardware circuits.

[0247] In an embodiment of the present application, a processor is a circuit with a signal processing capability. In one implementation, the processor may be a circuit with the capability to read and execute instructions, such as a central processing unit (CPU), a microprocessor, a graphics processing unit (GPU) (which may be understood as a microprocessor), or a digital signal processor (DSP); in another implementation, the processor may implement certain functions through the logical relationship of a hardware circuit, and the logical relationship of the hardware circuit may be fixed or reconfigurable, such as a hardware circuit implemented by an ASIC or PLD, such as an FPGA. In a reconfigurable hardware circuit, the process of the processor loading a configuration document to implement the hardware circuit configuration may be understood as the process of the processor loading instructions to implement the functions of some or all of the above units. In addition, it may also be a hardware circuit designed for artificial intelligence, which may be understood as an ASIC, such as a neural network processing unit (NPU), a tensor processing unit (TPU), a deep learning processing unit (DPU), etc.

[0248] It can be seen that each unit in the above device can be one or more processors (or processing circuits) configured to implement the above method, such as: CPU, GPU, NPU, TPU, DPU, microprocessor, DSP, ASIC, FPGA, or a combination of at least two of these processor forms.

[0249] In addition, the various units in the above apparatus may be fully or partially integrated together, or may be implemented independently. In one implementation, these units are integrated together and implemented in the form of a system-on-chip (SoC). The SoC may include at least one processor for implementing any of the above methods or implementing the functions of the various units of the apparatus. The at least one processor may be of different types, for example, including a CPU and an FPGA, a CPU and an artificial intelligence processor, a CPU and a GPU, etc.

[0250] In a specific implementation, the operations performed by the first processing unit 810, the acquisition unit 820, and the generation unit 830 can be performed by the same processor, or by different processors, for example, by multiple processors. In addition, the operations performed by the first processing unit 810, the acquisition unit 820, and the generation unit 830, and the second processing unit, the third processing unit, the fourth processing unit, and the determination unit can be performed by the same processor, or by different processors. In a specific implementation, the one or more processors can be a processor provided in the development platform 200 shown in FIG. 2 ; or the device 800 can be a chip provided in an electronic device.

[0251] Figure 9 is a schematic block diagram of a network configuration device provided in an embodiment of the present application. The network configuration device 900 shown in Figure 9 may include: a processor 910, a transceiver 920, and a memory 930. The processor 910, the transceiver 920, and the memory 930 are connected via an internal connection path. The memory 930 is used to store instructions, and the processor 910 is used to execute the instructions stored in the memory 930 to receive / send some parameters through the transceiver 920. Optionally, the memory 930 can be coupled to the processor 910 via an interface or integrated with the processor 910.

[0252] It should be noted that the transceiver 920 may include but is not limited to a transceiver device such as an input / output interface to implement communication between the device 900 and other devices or a communication network.

[0253] The memory 930 may be a read-only memory (ROM), a static storage device, a dynamic storage device, or a random access memory (RAM).

[0254] The transceiver 920 uses a transceiver device such as, but not limited to, a transceiver to implement communication between the apparatus 900 and other devices or a communication network.

[0255] In a specific implementation process, the device 900 may be provided in the development platform 200 shown in FIG. 2 .

[0256] An embodiment of the present application further provides an electronic device, which includes the above-mentioned device 800 or the above-mentioned device 900.

[0257] An embodiment of the present application further provides a computer program product, which includes computer program code. When the computer program code runs on a computer, the computer implements the method in the embodiment of the present application.

[0258] An embodiment of the present application further provides a computer-readable storage medium, which stores computer instructions. When the computer instructions are executed on a computer, the computer implements the method in the embodiment of the present application.

[0259] An embodiment of the present application also provides a chip, including a circuit, for executing the method in the embodiment of the present application.

[0260] During implementation, each step of the above method can be completed by an integrated logic circuit of the hardware in the processor or by instructions in the form of software. The method disclosed in conjunction with the embodiments of the present application can be directly embodied as being executed by a hardware processor, or can be executed by a combination of hardware and software modules in the processor. The software module can be located in a storage medium mature in the art such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory, or a power-on erasable programmable memory, a register, etc. The storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware. To avoid repetition, it will not be described in detail here.

[0261] Those skilled in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0262] Those skilled in the art will clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0263] In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are merely schematic. For example, the division of the units is merely a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0264] 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, that is, they may be located in one place or distributed across multiple network units. Some or all of these units may be selected to achieve the purpose of this embodiment according to actual needs.

[0265] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0266] If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application or part of the technical solution can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes a number of instructions for enabling a computer device (which can be a personal computer, server, or network device, etc.) to execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes various media that can store program codes, such as a USB flash drive, a mobile hard disk, a ROM, a RAM, a magnetic disk, or an optical disk.

[0267] The above description is merely a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in this application should be included in the scope of protection of this application. Therefore, the scope of protection of this application should be based on the scope of protection of the claims.

Claims

1. A network configuration method, characterized in that: include: establishing a connection relationship between a plurality of network devices according to a user instruction, wherein the plurality of network devices are vehicle-mounted network devices; Acquire a basic configuration of each network device among the plurality of network devices, wherein the basic configuration of each network device includes address information of each network device; Network configuration information is generated for each network device according to the connection relationship between the multiple network devices and the basic configuration of each network device.

2. The method according to claim 1, wherein The method further comprises: The display device is controlled to display a first interface, where the first interface includes connection relationships between the multiple network devices.

3. The method according to claim 2, wherein The first interface includes a display area and a creation tool area. The creation tool area includes multiple network device objects of different types. The multiple network device objects of different types are used to create the multiple network devices. The display area is used to display the connection relationship between the multiple network devices.

4. The method according to any one of claims 1 to 3, characterized in that The connection relationship between the multiple network devices includes the type of a communication port of each network device in the multiple network devices, and the communication port is a port connected to other network devices.

5. The method according to claim 4, wherein The types of the communication ports include an Ethernet ETH port, a Universal Asynchronous Receiver / Transmitter UART port, a Low Voltage Differential Signal LVDS port, or a Controller Area Network CAN port.

6. The method according to claim 4 or 5, characterized in that Generating network configuration information for each network device according to the connection relationship between the plurality of network devices and the basic configuration of each network device includes: determining a communication relationship between the plurality of network devices according to a type of a communication port of each network device in the plurality of network devices and a basic configuration of each network device; Network configuration information is generated for each network device according to the communication relationship between the multiple network devices.

7. The method according to claim 6, wherein The basic configuration of each network device further includes a virtual local area network identifier (VLAN ID) of the network device. The determining of the communication relationship between the multiple network devices based on the type of the communication port of each network device in the multiple network devices and the basic configuration of each network device includes: The communication relationship between the multiple network devices is determined according to the type of the communication port of each network device in the multiple network devices and the VLAN ID of each network device.

8. The method according to any one of claims 1 to 7, characterized in that The obtaining of the basic configuration of each of the plurality of network devices includes: In response to an operation on a first network device, the display apparatus is controlled to display a second interface, and a basic configuration of the first network device is obtained through the second interface, where the first network device is any one of the multiple network devices.

9. The method according to any one of claims 1 to 8, characterized in that The basic configuration of each network device further includes a data flow configuration, where the data flow configuration indicates constraints on data flows generated when the network device provides services, where the data flow constraints include one or more of a direction of the data flow, a transmission speed of the data flow, and a priority of the data flow. The method further includes: The display device is controlled to display a third interface, where the third interface includes one or more of the flow direction of the data flow between the multiple network devices, the transmission speed of the data flow, and the priority of the data flow.

10. The method according to any one of claims 1 to 9, characterized in that The network configuration information includes one or more items of an access control list (ACL), an address resolution list (ARL), an address resolution protocol (ARP), and a routing table.

11. A network configuration device, characterized in that: It includes a first processing unit, an acquisition unit and a generation unit, wherein: The first processing unit is used to: establish a connection relationship between multiple network devices according to a user instruction, and the multiple network devices are vehicle-mounted network devices; The acquiring unit is configured to: acquire a basic configuration of each network device among the plurality of network devices, wherein the basic configuration of each network device includes address information of each network device; The generating unit is configured to generate network configuration information for each network device according to the connection relationship between the plurality of network devices and the basic configuration of each network device.

12. The device according to claim 11, wherein The apparatus further includes a second processing unit, configured to: The display device is controlled to display a first interface, where the first interface includes connection relationships between the multiple network devices.

13. The device according to claim 12, wherein The first interface includes a display area and a creation tool area. The creation tool area includes multiple network device objects of different types. The multiple network device objects of different types are used to create the multiple network devices. The display area is used to display the connection relationship between the multiple network devices.

14. The device according to any one of claims 11 to 13, characterized in that The connection relationship between the multiple network devices includes the type of a communication port of each network device in the multiple network devices, and the communication port is a port connected to other network devices.

15. The device according to claim 14, wherein The types of the communication ports include an Ethernet ETH port, a Universal Asynchronous Receiver / Transmitter UART port, a Low Voltage Differential Signal LVDS port, or a Controller Area Network CAN port.

16. The device according to claim 14 or 15, characterized in that The apparatus further includes a determining unit configured to: determining a communication relationship between the plurality of network devices according to a type of a communication port of each network device in the plurality of network devices and a basic configuration of each network device; The generating unit is configured to generate network configuration information for each network device according to the communication relationship between the plurality of network devices.

17. The device according to claim 16, wherein The basic configuration of each network device further includes a virtual local area network identifier (VLAN ID) of the network device, and the determining unit is configured to: The communication relationship between the multiple network devices is determined according to the type of the communication port of each network device in the multiple network devices and the VLAN ID of each network device.

18. The device according to any one of claims 11 to 17, characterized in that The apparatus further includes a third processing unit, configured to: In response to an operation on a first network device, controlling the display device to display a second interface, where the first network device is any one of the multiple network devices; The acquiring unit is configured to acquire the basic configuration of the first network device through the second interface.

19. The device according to any one of claims 11 to 18, characterized in that The basic configuration of each network device further includes a data flow configuration, where the data flow configuration indicates constraints on data flows generated when the network device provides services, where the data flow constraints include one or more of a direction of the data flow, a transmission speed of the data flow, and a priority of the data flow. The apparatus further includes a fourth processing unit, configured to: The display device is controlled to display a third interface, where the third interface includes one or more of the flow direction of the data flow between the multiple network devices, the transmission speed of the data flow, and the priority of the data flow.

20. The device according to any one of claims 11 to 19, characterized in that The network configuration information includes one or more items of an access control list (ACL), an address resolution list (ARL), an address resolution protocol (ARP), and a routing table.

21. A network configuration device, characterized in that: include: Memory for storing computer programs; A processor, configured to execute the computer program stored in the memory, so that the apparatus performs the method according to any one of claims 1 to 10.

22. An electronic device, characterized in that: Comprising the apparatus of any one of claims 11 to 21.

23. A computer-readable storage medium, characterized in that Instructions are stored thereon, and when the instructions are executed by a processor, the processor is caused to implement the method according to any one of claims 1 to 10.

24. A chip, characterized in that: The chip comprises a circuit for executing the method according to any one of claims 1 to 10.

25. A computer program product, characterized in that The computer program product comprises: a computer program code, and when the computer program code is run on a computer, the computer is caused to perform the method according to any one of claims 1 to 10.

Images