Management method and system of Internet of Vehicles, electronic equipment and storage medium

Abstract

The invention relates to an Internet of Vehicles network management method and system, electronic equipment and a storage medium, and the method comprises the steps: determining a dialing state of the Internet of Vehicles network after the Internet of Vehicles network is dialed and successfully injected; when the dialing state indicates that the dialing of the target network channel in the Internet of Vehicles is disconnected, initiating a dialing process to the disconnected target network channel; updating the connection state of the target network channel according to the dialing process; configuring routing and forwarding rules according to the connection state; and determining that the connection of the target network channel is recovered after the routing and forwarding rules are configured. According to the method and the device, the Internet of Vehicles can be monitored after the Internet of Vehicles is dialed and the Internet is successfully injected, and if the dialing is disconnected, a dialing process is initiated, and the Internet of Vehicles is re-dialed to be injected so as to recover the Internet of Vehicles.

Description

Technical Field

[0001] The present application relates to the field of vehicle assistance technology, and specifically to a management method, system, electronic device and storage medium for an Internet of Vehicles network. Background Art

[0002] With the rapid development of intelligent automobile technology, the electronic and electrical architecture of various automobile manufacturers has entered the electrical architecture X-EEA3.0, and most of the inter-domain communications of the whole vehicle have been adjusted to Ethernet. Therefore, the vehicle's in-vehicle networking system must also be upgraded. In the existing technology, after the vehicle networking system dials up and registers the network successfully, the network status is not monitored, resulting in the inability to use the network if the network fluctuates and the network is disconnected. Summary of the invention

[0003] In order to solve the above technical problems or at least partially solve the above technical problems, the present application provides a management method, system, electronic device and storage medium for an Internet of Vehicles network.

[0004] In a first aspect, the present application provides a method for managing an Internet of Vehicles network, comprising: determining the dial-up status of the Internet of Vehicles network after the Internet of Vehicles network dials up and registers successfully; when the dial-up status indicates that the target network channel in the Internet of Vehicles network is dialed off, initiating a dial-up process to the disconnected target network channel; updating the connection status of the target network channel according to the dial-up process; configuring routing and forwarding rules according to the connection status; and determining that the connection of the target network channel is restored after configuring the routing and forwarding rules.

[0005] In the second aspect, the present application provides a management system for an Internet of Vehicles network, including: a first determination module, used to determine the dial-up status of the Internet of Vehicles network after the Internet of Vehicles network dials up and registers successfully; a dial-up module, used to initiate a dial-up process to the disconnected target network channel when the dial-up status indicates that the target network channel in the Internet of Vehicles network is dialed off; an update module, used to update the connection status of the target network channel according to the dial-up process; a configuration module, used to configure routing and forwarding rules according to the connection status; a second determination module, used to determine that the connection of the target network channel is restored after configuring the routing and forwarding rules.

[0006] In a third aspect, the present application provides an electronic device, including a processor, a communication interface, a memory, and a communication bus, wherein the processor, the communication interface, and the memory communicate with each other via the communication bus;

[0007] Memory, used to store computer programs;

[0008] The processor is used to implement the steps of the vehicle networking network management method described above in any embodiment of the first aspect when executing the program stored in the memory.

[0009] In a fourth aspect, the present application provides a computer-readable storage medium having a computer program stored thereon. When the computer program is executed by a processor, the computer program implements the steps of the method for managing a vehicle networking network as described in any one of the embodiments of the first aspect.

[0010] Beneficial effects of this application:

[0011] The method provided by the embodiment of the present application determines the dial-up status of the above-mentioned Internet of Vehicles network after the above-mentioned Internet of Vehicles network dials up and registers the network successfully; when the above-mentioned dial-up status indicates that the dial-up of the target network channel in the above-mentioned Internet of Vehicles network is disconnected, initiates a dial-up process to the disconnected above-mentioned target network channel; updates the connection status of the above-mentioned target network channel according to the above-mentioned dial-up process; configures routing and forwarding rules according to the above-mentioned connection status; determines that the connection of the above-mentioned target network channel is restored after configuring the routing and forwarding rules, so that the Internet of Vehicles network can be monitored after the above-mentioned Internet of Vehicles network dials up and registers the network successfully. If there is a dial-up disconnection, the dial-up process is initiated to re-dial and register the network to restore the Internet of Vehicles network. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0013] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, for ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.

[0014] Figure 1 A system architecture diagram of a method for managing an Internet of Vehicles network provided in one embodiment of the present application;

[0015] Figure 2 A flowchart of a method for managing an Internet of Vehicles network provided by an embodiment of the present application;

[0016] Figure 3 A system architecture diagram of a method for managing an Internet of Vehicles network provided in one embodiment of the present application;

[0017] Figure 4 A system functional architecture diagram of a method for managing an Internet of Vehicles network provided in one embodiment of the present application;

[0018] Figure 5A system network architecture diagram of a method for managing an Internet of Vehicles network provided in one embodiment of the present application;

[0019] Figure 6 A dial-up start flow chart of a method for managing a vehicle networking network provided by an embodiment of the present application;

[0020] Figure 7 A flowchart of a network anomaly detection function of a vehicle networking network management method provided by an embodiment of the present application;

[0021] Figure 8 A flowchart of a network anomaly detection function of another method for managing an Internet of Vehicles network provided by an embodiment of the present application;

[0022] Fig. 9 A configuration update flow chart of a method for managing a vehicle networking network provided by an embodiment of the present application;

[0023] Fig.10 A schematic diagram of the structure of a management system of an Internet of Vehicles network provided by one embodiment of the present application;

[0024] Fig.11 A schematic diagram of the structure of an electronic device provided in accordance with an embodiment of the present application. DETAILED DESCRIPTION

[0025] The following will describe the embodiments of the present invention with reference to the accompanying drawings and preferred embodiments. Those skilled in the art can easily understand other advantages and effects of the present invention from the contents disclosed in this specification. The present invention can also be implemented or applied through other different specific embodiments, and the details in this specification can also be modified or changed in various ways based on different viewpoints and applications without departing from the spirit of the present invention. It should be understood that the preferred embodiments are only for illustrating the present invention, not for limiting the scope of protection of the present invention.

[0026] It should be noted that the illustrations provided in the following embodiments are only schematic illustrations of the basic concept of the present invention, and thus the drawings only show components related to the present invention rather than being drawn according to the number, shape and size of components in actual implementation. In actual implementation, the type, quantity and proportion of each component may be changed arbitrarily, and the component layout may also be more complicated.

[0027] For ease of description, spatial relative terms may be used in the text to describe the relative position or movement of an element or feature as shown in the figure relative to another element or feature, such as "inside", "outside", "inner side", "outer side", "below", "below", "above", "above", "front", "back", etc. Such spatial relative terms are intended to include different orientations of the device in use or operation in addition to the orientation depicted in the figure. For example, if the device in the figure undergoes a position flip or a change in posture or a change in motion state, then these directional indications will also change accordingly, for example: an element described as "below other elements or features" or "below other elements or features" will subsequently be oriented as "above other elements or features" or "above other elements or features". Therefore, the example term "below..." can include both upper and lower orientations. The device can be oriented otherwise (rotated 90 degrees or in other directions) and the spatial relative descriptors used in the text are interpreted accordingly.

[0028] In order to solve the technical problem in the prior art that after the Internet of Vehicles system successfully dials up and registers the network, the network status is not monitored, resulting in the inability to use the network if the network fluctuates and the network is disconnected, the present application provides a management method for the Internet of Vehicles network, which can initiate a dial-up process and re-dial the network if there is a dial-up disconnection to restore the effect of the Internet of Vehicles network.

[0029] The first embodiment of the present application provides a method for managing a vehicle networking network, which can be applied to Figure 1 The system architecture shown includes at least a vehicle 101 and a server 102. The vehicle 101 can establish a communication connection with the server 102 through the management method of the Internet of Vehicles network.

[0030] The method can be applied to vehicle 101 in the system architecture, wherein the type of vehicle 101 is not limited, for example, it can be an electric vehicle (EV), a battery electric vehicle (BEV), a fuel cell electric vehicle (FCEV), a plug-in hybrid electric vehicle (PHEV) and a hybrid electric vehicle (HEV), etc. The vehicle 101 to which the method is applied can be called a target vehicle, and the server 102 can be a local server, a cloud server, or a server cluster.

[0031] Next, based on the system architecture, the management method of the Internet of Vehicles network provided by this embodiment is introduced. Figure 2 As shown, the above method includes:

[0032] S201, after the Internet of Vehicles network dials up and registers successfully, determining the dial-up status of the Internet of Vehicles network;

[0033] S202, when the dial-up status indicates that the dial-up of the target network channel in the Internet of Vehicles network is disconnected, initiating a dial-up process to the disconnected target network channel;

[0034] S203, updating the connection status of the target network channel according to the dial-up process;

[0035] S204, configuring routing and forwarding rules according to the above connection status;

[0036] S205, after configuring the routing and forwarding rules, determine that the target network channel connection is restored.

[0037] Optionally, in this embodiment, the Internet of Vehicles network can dial up and register a network. After the registration is successful, the dial-up status of the Internet of Vehicles network can be monitored. The above-mentioned dial-up status can be a dial-up connection status or a dial-up disconnection status. The network can be registered in the dial-up connection status, and the network cannot be registered in the dial-up disconnection status. The network needs to be dialed up before the network is registered. After the network is registered in the dial-up connection status, the network can be connected. If the dial-up registration fails, the network cannot be connected.

[0038] In the above embodiment, the Internet of Vehicles network can be connected to one or more servers by dialing and logging on to the network. Each connection channel is a network channel. Communication is possible when the network channel is connected, and communication is impossible when the network channel is disconnected.

[0039] After the Internet of Vehicles network dials up and registers, the connection status of each network channel of the Internet of Vehicles network can be monitored. If a network channel is dialed off, the network channel, as the target network channel, must start the dial-up process to reconnect. For the target network channel, start the dial-up process to redial, update the connection status, the connection status is disconnected, and then configure the routing rules and forwarding rules. The routing rules are the routing configuration after the network is re-dialed, and the forwarding rules are how the data is forwarded after the network is re-dialed. After configuring the routing rules and forwarding rules, determine whether the dial-up is successful. If successful, it determines that the target network channel has been restored. If not, the dial-up process can be started again.

[0040] This embodiment determines the dial-up status of the above-mentioned Internet of Vehicles network after the above-mentioned Internet of Vehicles network dials up and registers successfully; when the above-mentioned dial-up status indicates that the dial-up of the target network channel in the above-mentioned Internet of Vehicles network is disconnected, initiates a dial-up process to the disconnected above-mentioned target network channel; updates the connection status of the above-mentioned target network channel according to the above-mentioned dial-up process; configures routing and forwarding rules according to the above-mentioned connection status; determines that the connection of the above-mentioned target network channel is restored after configuring the routing and forwarding rules, so that the Internet of Vehicles network can be monitored after the above-mentioned Internet of Vehicles network dials up and registers successfully, and if there is a dial-up disconnection, initiates the dial-up process, and re-dials to restore the Internet of Vehicles network.

[0041] As an optional example, when the dial-up status indicates that the dial-up of the target network channel in the above-mentioned Internet of Vehicles network is disconnected, initiating the dial-up process to the disconnected target network channel includes: when the modem detects that the dial-up of the above-mentioned target network channel is disconnected, initiating the dial-up process to the disconnected target network channel; or, detecting the network status of the above-mentioned target network channel through the network protection function, and when the above-mentioned network status is abnormal, sending a network connection disconnection message to the modem, and the modem stops dialing the above-mentioned target network channel according to the above-mentioned network connection disconnection message, and initiates the dial-up process to the disconnected target network channel after waiting for a predetermined period of time.

[0042] In this embodiment, after the dial-up network is successfully registered, the dial-up status of the Internet of Vehicles network is determined. If the dial-up is disconnected, the dial-up process is re-initiated. There are many possibilities for dial-up disconnection. Therefore, they must be handled separately. One of the situations is that the modem detects that the dial-up of the target network channel is disconnected. The modem detection method can directly detect when the Internet of Vehicles network dial-up is disconnected, which is relatively accurate and can respond immediately to perform the redialing process. Another situation is that the network protection function detects the network status of the target network channel. If the network status is abnormal, a network connection disconnection message is sent to the modem, and then the modem actively stops dialing and waits for a predetermined period of time before re-initiating the dial-up process.

[0043] That is to say, in two cases, one is that the modem actively monitors and initiates a redialing process when it finds that the dial-up is disconnected. The other case is that the network protection function detects the network status, and when the modem receives the network connection disconnection message from the network protection function, it actively stops dialing and waits for a predetermined period of time before redialing.

[0044] The above-mentioned predetermined time length is a waiting time period of the modem, which can be one second, two seconds, etc., after which the modem starts to redial.

[0045] As an optional example, after the modem stops dialing the target network channel according to the network disconnection message, the method further includes:

[0046] Initiate a dial-up disconnect message;

[0047] The network protection function updates the connection state of the target network channel according to the dial-up disconnection message, and sends the dial-up disconnection message to the routing module;

[0048] The routing module clears the domain name binding, forwarding relationship and routing information of the target network channel according to the dial-up disconnection message.

[0049] In this embodiment, when the modem receives the network connection disconnection message sent by the network protection function, it actively stops dialing and waits for a predetermined time, or after waiting for a predetermined time, before redialing, it also sends a dial-up disconnection message to the network protection function. Since the modem disconnects the dial-up connection, the message is sent to the network protection function so that the network protection function updates the connection state of the target network channel to a disconnected state, and sends a dial-up disconnection message to the routing module, and then the routing module clears the binding, forwarding relationship and routing information of the domain name of the target network channel.

[0050] That is to say, when the modem receives the network connection disconnection message sent by the network protection function, it actively stops dialing, and the network protection function updates the connection status of the target network channel to the disconnected status, and deletes the binding, forwarding relationship and routing information of the domain name of the target network channel recorded in the routing module, so that after the modem redials, it can update the connection status with the new status and record the binding, forwarding relationship and routing information of the new domain name of the target network channel.

[0051] As an optional example, the above-mentioned Internet of Vehicles network dial-up and network registration includes:

[0052] Obtain configuration information, detection cycle, domain name binding information and domain name forwarding rules of each network channel of the above-mentioned Internet of Vehicles network in the configuration file;

[0053] According to the above configuration information, initiate dialing;

[0054] After initiating dialing, periodically detecting the network availability of each of the above network channels according to the above detection cycle;

[0055] When the network is available, local services and routing rules are configured according to the above domain name binding information and the above domain name forwarding rules, and it is determined that the dial-up network registration is successful.

[0056] In this embodiment, before the dial-up network registration is successful, the dial-up network registration can be performed through the configuration file, and whether the dial-up network registration is successful can be checked. When the configuration file is used for dial-up network registration, the configuration information, detection cycle, domain name binding information and domain name forwarding rules of each network channel of the Internet of Vehicles network in the configuration file are first obtained. The above configuration information can be the server or operator to be connected to the network registration, the above detection cycle is the cycle for detecting whether the network registration is successful after the dial-up network registration, and the above domain name binding information and domain name forwarding rules are the domain names and forwarding rules that can be accessed after the dial-up network registration.

[0057] After obtaining the above information in the configuration file, you can dial up the network according to the above configuration information, and after the network is registered, detect the network connection status according to the above detection cycle. If the network is successfully registered, configure the accessible domain name according to the above domain name binding information, and forward the request to access the domain name according to the domain name forwarding rule. After the configuration is completed, the dial-up network registration is successful.

[0058] As an optional example, the initiating dialing according to the configuration information includes:

[0059] If this is not the first dial-up and the last dial-up registration failed, turn on the flight mode;

[0060] After waiting for the first period of time, turn off the above flight mode;

[0061] After turning off the above airplane mode, try dialing again.

[0062] In this embodiment, when dialing up the network, if the first dialing up the network fails, the dialing up the network can be performed again. If it is not the first dialing up the network and the dialing up the network fails, the flight mode can be turned on, and then wait for a while, such as waiting for 3 seconds, and then turn off the flight mode, and then re-initiate the dialing up the network. The purpose of turning on the flight mode and waiting for a while and then turning off the flight mode is to re-initiate the random dialing up the network access process, try to register the network, and then check the network registration situation to determine whether the network registration is successful.

[0063] As an optional example, after the above-mentioned Internet of Vehicles network dial-up and network registration are successful, the above-mentioned method further includes:

[0064] When the network registration is successful for the first time, the version information, region information and vehicle model of the local configuration file are collected;

[0065] Send an update request to the cloud based on the above version information, region information, and vehicle model;

[0066] Receive the new version of the configuration file returned by the cloud;

[0067] Initialize the channel configuration of the wireless channel and the channel configuration of the wired channel according to the above new version configuration file.

[0068] In this embodiment, if the dial-up network registration is successful for the first time, after the dial-up network registration is successful, a request can be sent to the cloud based on the version information, regional information and vehicle model of the local configuration file to obtain a new version of the configuration file corresponding to the version information, regional information and vehicle model of the local configuration file, and the new version of the configuration file can be used to initialize the channel configuration of the wireless channel and the channel configuration of the wired channel to complete the update of the channel configuration.

[0069] As an optional example, after receiving the new version of the configuration file returned by the cloud, the method further includes:

[0070] Back up the above local configuration files;

[0071] After initializing the channel configuration of the wireless channel and the channel configuration of the wired channel according to the new version of the configuration file, if the wireless channel or the wired channel is abnormal, the backup local configuration file is used to initialize the channel configuration of the wireless channel and the channel configuration of the wired channel.

[0072] In this embodiment, after sending a request to the cloud to obtain a new version of the configuration file according to the version information, regional information, and vehicle model of the local configuration file, the local configuration file can be backed up before using the new version of the configuration file for updating, and then the channel configuration of the wireless channel and the channel configuration of the wired channel can be initialized using the new version of the configuration file. If there is an abnormality in any of the channel configurations of the wireless channel and the wired channel initialized by the new version of the configuration file, the backup local configuration file is used to initialize the channel configuration of the wireless channel and the channel configuration of the wired channel, thereby restoring the channel configuration.

[0073] The example is used for illustration. The Internet of Vehicles network or Internet of Vehicles system of this embodiment can provide network connectivity and support for multiple parts of the vehicle. The Internet of Vehicles network is centered on the vehicle switch (SWITCH), connecting the vehicle's cockpit domain control, intelligent driving domain control, body domain control, power domain control and other modules to form the Internet of Vehicles network. The system architecture of the vehicle is as follows Figure 3 shown.

[0074] The vehicle's microcontroller unit (MCU) configures parameters, monitors and manages the status of SIWTCH through inter-chip communication. The MCU is also responsible for the power management functions of each module (domain) of the vehicle, such as power-on timing, sleep wake-up, etc.

[0075] The above-mentioned cockpit domain control is used to realize functions such as human-computer interaction, entertainment system and peripheral management, remote vehicle control protocol, national standard data collection and cloud, and information presentation in other domains. Intelligent driving domain control is used to realize the control process of assisted driving or autonomous intelligent driving such as vehicle-side intelligent driving data collection, intelligent driving algorithm calculation and control, and real-time cloud data interaction. The body domain control is used to realize data collection of key components of the body, execute remote control, control instructions issued by manual driving or intelligent driving domain control, safety warnings and other functions. The power domain control is used to realize vehicle (hybrid) power switching management, high-voltage energy management, low-voltage energy management, thermal management, low-energy warning and other functions.

[0076] The central computing unit can be deployed on a cockpit domain control platform, an intelligent driving domain control platform, or on an independent hardware platform.

[0077] The vehicle-mounted module (Telematics BOX, TBOX) in the vehicle networking system of this embodiment is embedded with a communication module, which manages the network registration, dialing, and network detection processes of the wireless network through the network management program, configures routing, domain name binding and forwarding rules, and configures firewall rules. The Ethernet configuration software module is used to configure the Ethernet VLAN, bridge and forwarding rules to isolate the in-vehicle LAN from the external network services.

[0078] As a key module for in-vehicle network access, TBOX connects to the operator network through wireless networks to access the Internet and enterprise private networks; internally, it provides network connections for the central computing unit and each domain control unit through Ethernet. Figure 4 shown.

[0079] The wireless network access control function is implemented by the communication module provided by the supplier, and independently realizes control plane functions such as random access to the wireless network, network registration, and cell switching, and provides software interfaces such as data dialing control, module status and information query, and traffic statistics for upper-level management applications.

[0080] The upper-level management applications mainly include dial-up management, network diagnosis, VLAN management, routing management, firewall configuration, network configuration management and other functional programs.

[0081] The dial-up management application is used to implement functions such as data dial-up management, data service availability detection, and network abnormality recovery.

[0082] The function of the network diagnostic application is to periodically diagnose the network and support the diagnostic needs of other domain controllers. The diagnostic content includes network access point name (APN) dialing information, network registration status, registered cell and neighbor cell information, module working status, terminal SIM card information, etc.

[0083] The Virtual Local Area Network (VLAN) configuration function is triggered after the Ethernet driver is loaded successfully. VLANs of different network segments are configured to isolate the in-vehicle LAN and external network services. The network architecture of the vehicle is as follows: Figure 5 As shown. VLAN 1 is the in-vehicle LAN, and its network segment is 172.16.1.x / 24. VLAN 2 is the external network channel, and its network segment is 172.16.2.x / 24. If other domain controllers need to interact with TBOX for in-vehicle services, they communicate through the IP of the 172.16.1.x / 24 network segment. If TBOX needs to send its service data packets to the external network, its gateway is set to the 172.16.2.x / 24 network segment IP address of TBOX, and TBOX sends the data packets of this network segment to the air interface. Other domain controllers in the car (such as cockpit domain controller, intelligent driving domain controller, body domain controller, etc.) are connected to TBOX through VLAN2, and forwarded by TBOX to the APN2 or APN3 air interface. If different models have different deployments of domain controllers, the adjustment of TBOX to the network supply demand can be completed by increasing or decreasing the parameters of the configuration file. For example, if a low-end car model does not have intelligent driving domain control, the corresponding IP, forwarding rules, detection port and other parameters can be deleted in the relevant configuration file, and TBOX can adapt to different hardware configurations.

[0084] The routing management function triggers the routing configuration function after the dial-up management function completes the dial-up. The routing configuration includes default routing, domain name binding, domain name forwarding, etc. The default routing configuration is divided into TBOX local services and Ethernet services. TBOX may have services that need to connect to the enterprise intranet, and its default routing is configured as an intranet channel, such as a specific APN channel. Such channels are established by telecom operators to establish dedicated communication service tunnels directly connected to the car company's enterprise intranet; and other domain control Internet services, according to the architecture of this solution, need to be sent to TBOX by SWITCH through Ethernet. Therefore, the default routing of the services interacted by VLAN 2 is to the air interface corresponding to the public network APN. Domain name binding is for TBOX local services. For example, when the local default route is the enterprise private network channel, and some services need to go through the public network channel, the services for the domain name are forwarded to the public network channel through domain name binding. Domain name forwarding is for Ethernet services. When TBOX dials multiple APNs for public network service transmission, for example, APN2 is the entertainment traffic channel, APN3 is the factory private network channel, and the data packets of VLAN2 are routed to APN2 by default, some application services and scenarios need to access the public network through APN3, then domain name forwarding configuration is required to forward the service data packets accessing these domain names to the air interface corresponding to APN3.

[0085] Configuration management refers to the management of configuration information such as network parameters, routing rules, VLAN rules, firewall policies, domain name bindings, and forwarding relationships. The management process includes pulling configuration files from the cloud, making configuration files effective, and rolling back configuration files. Updating configuration files in the cloud facilitates the update and iteration of vehicle-side network configurations. Different vehicle models can pull corresponding vehicle configurations from the cloud, reducing vehicle-side program updates, development workload, and Over-the-Air Technology (OTA) pressure.

[0086] TBOX applications also require the support of the LINUX system, such as the vconfig command required for VLAN configuration, the ip route command for routing configuration, the iptables command required for domain name forwarding and binding, etc., and load and unload Ethernet drivers according to different sleep and wake-up application scenarios.

[0087] The vehicle networking network of this embodiment is described from dial-up management to network exception handling to configuration update.

[0088] The dial-up management function starts running as the main process of TBOX, and starts other functions and configuration processes according to different states. The normal startup process is as follows: Figure 6 , the steps are as follows:

[0089] Step S1-0: TBOX is powered on and starts to run the dial-up management program.

[0090] Step S1-1, load the configuration file, parse the configuration parameters, and save them to the memory for standby. The parameter information includes APN configuration information, network detection cycle, domain name binding information, domain name forwarding rules, etc.

[0091] Step S1-2, check the working status of the module. If the module is not ready, execute step S1-3; otherwise, execute step S1-4.

[0092] Step S1-3, restart the module, wait for 5 seconds, and execute step S1-2 to check whether the module can work normally.

[0093] Step S1-4, check whether the network registration is successful, if the network registration has failed, execute step S1-5, otherwise execute step S1-6.

[0094] Step S1-5, turn on the flight mode and wait for 3 seconds, then turn off the flight mode, the purpose is to make the module re-initiate the random access process, try to register the network, and then check the network registration status.

[0095] Step S1-6, creating a network exception processing thread for network recovery functions in situations such as network disconnection, dial-up failure, and network service failure.

[0096] Step S1-7, initiating data dialing according to the APN configuration information. If the dialing fails, execute step S1-8, otherwise execute step S1-9.

[0097] Step S1-8, sending the dialing failure message to the network exception processing thread, allowing it to re-initiate the dialing, and then executing step S1-7 to check the dialing status.

[0098] Step S1-9, creating a network protection thread for periodically detecting network availability and issuing a network anomaly notification when an anomaly is detected.

[0099] Step S1-10, initiate the process of domain name binding and domain name forwarding rules, and configure routing rules for local services and Ethernet forwarding services.

[0100] Step S1-11, configure the firewall rules of TBOX according to the firewall configuration file information.

[0101] Step S1-12, start the network diagnosis function, periodically detect network information and record it in the log, and open the TBOX network information diagnosis interface of other domain controllers.

[0102] Step S1-13, the main loop of network dial-up management is to periodically publish the network connection status to the internal software module of TBOX and the external domain controller.

[0103] Take an example, step 0, TBOX is powered on and starts to run the dial-up management program. Check whether the software version number has changed. If it has changed, copy the configuration file in the software version update package to the software program working directory for backup (during the software version update process, the configuration file in the upgrade package will be stored in a designated read-only directory, which does not belong to the program working directory).

[0104] Step 1: Load the configuration file from the program working directory (readable and writable directory), parse the configuration parameters, and save them to the memory for backup. The parameter information includes APN configuration information, network detection cycle, domain name binding information, domain name forwarding rules, etc.

[0105] Step 2: Check the working status of the module. If the module is not in normal working status, go to step 3; otherwise, go to step 4.

[0106] Step 3: Restart the module to try to make it work normally, wait for 15 seconds, and then perform step 2 to check whether the module can work normally.

[0107] Step 4, check whether the network registration is successful. If the network registration fails, proceed to step 5, otherwise proceed to step 6.

[0108] Step 5, turn on the flight mode and wait for 3 seconds, then turn off the flight mode. The purpose is to allow the module to re-initiate the random access process, try to inject network, and then check the injection status.

[0109] Step 6: Create a network exception processing thread for network recovery in the event of network disconnection, dial-up failure, network service failure, etc. Start the routing function program to configure Ethernet (such as IP, VLAN, routing, etc.) according to the configuration file, establish a wired network connection between TBOX and other domain controllers, and configure the firewall according to the rules of the configuration file.

[0110] Step 7: Initiate data dialing according to the APN configuration information. If the dialing fails, go to step 8, otherwise go to step 9.

[0111] Step 8, send the dial-up failure message to the network exception handling thread, let it issue a re-initiated dial-up, and then execute step 7 to check the dial-up connection status.

[0112] Step S9, create a network protection thread for periodically detecting network availability and issuing a network anomaly notification when an anomaly is detected. The network availability detection method includes but is not limited to obtaining the IP address of a specified domain name (nslookup command), pinging a specified domain name, obtaining certain information from a server through a network protocol, etc., and judging whether the network is available based on the operation results.

[0113] Step 10: Notify the routing module to initiate the process of domain name binding and domain name forwarding rules. The routing module binds and forwards the domain name to the specified APN dial-up channel according to the domain name forwarding and binding rules, and configures the routing rules for forwarding Ethernet services from other domain controllers to the wireless network.

[0114] Step 11: The routing module configures the firewall rules of TBOX according to the firewall configuration file information.

[0115] Step 12: Start the network diagnostic function, periodically detect network information and record it in the log, and open the TBOX network information diagnostic interface for other domain controllers.

[0116] Step 13: The main loop of network dial-up management is to periodically publish the network connection status to the TBOX internal software module and the external domain controller.

[0117] There are two types of network exception handling procedures: discovering network exceptions through the network protection function and detecting dial-up disconnection through the underlying modem. The network exception trigger sources in the two cases are different, but the handling process is similar, both of which are to restore the network by trying to redial.

[0118] Situation ① The network protection function finds network anomalies and the processing flow is as follows Figure 7 , the process is as follows:

[0119] Step S2-0, the network protection function periodically detects whether the corresponding channel network is normal according to the blocked APN channel, such as detecting whether the designated server is reachable;

[0120] Step S2-1, when the network protection function detects a network anomaly of a certain APN channel (i.e., the designated server is unreachable), a network disconnection message is sent to the exception handling function module;

[0121] Step S2-2, the exception handling function stops dialing the corresponding APN according to the network protection message, and then waits for 1 second; then executes step S2-6;

[0122] Step S2-3, after the modem stops the APN dialing, it sends a message to the application indicating that the dialing is disconnected;

[0123] Step S2-4, after receiving the dial-up disconnection message, the network protection function updates the dial-up connection status of the APN and sends the dial-up disconnection message to the routing module;

[0124] Step S2-5, the routing module clears the domain name binding and forwarding relationship on the APN, and clears the DNS routing, default routing and other information;

[0125] Step S2-6, the network exception handling function initiates the dialing process of the APN;

[0126] Step S2-7, after the modem completes the corresponding APN dialing, it reports the dial-up connection message to the network protection function;

[0127] Step S2-8, after receiving the dial-up connection message, the network protection function updates the dial-up connection status of the APN and sends the dial-up connection message to the routing module;

[0128] Step S2-9, the routing module reconfigures the DNS routing and the default routing according to the dial-up connection information, and configures the corresponding rules according to the binding and forwarding configurations, and responds to the network protection function with a message that the network connection is restored after the configuration is completed;

[0129] Step S2-10, the network protection function re-enters the periodic network protection process according to the network connection recovery message of the routing function.

[0130] In case ②, the modem detects that the dial-up is disconnected and triggers the network exception handling process. In this case, the dial-up has been disconnected, and there is no need to stop the problematic APN dial-up process, but directly initiate data dial-up. The specific flow chart is as follows Figure 8 .

[0131] Take an example, step 0, when the network protection function is normal, for the APN channel that has completed dialing, periodically check whether the channel network channel is normal;

[0132] Step 1: When a network abnormality of a certain APN channel is detected, or when the modem reports that a certain APN dial-up is disconnected, the network protection function sends a network connection disconnection message to the abnormality handling function module;

[0133] Step 2: The exception handling function checks whether the corresponding APN dial-up connection status is disconnected according to the network protection message. If it is not disconnected, the APN is stopped from dialing, and then waits for 1 second; then executes step 6;

[0134] Step 3: After the modem stops the APN dialing successfully, it sends a message to the application indicating that the dialing is disconnected;

[0135] Step 4: After receiving the dial-up disconnection message, the network protection function updates the dial-up connection state of the APN to the disconnected state, and sends the dial-up disconnection message to the routing module;

[0136] Step 5: The routing module clears the domain name binding and forwarding relationship on the APN, and clears the DNS routing, default routing and other information. At this time, the service data packets of each domain controller cannot be forwarded to the wireless network after being sent to TBOX via Ethernet.

[0137] Step 6: The network exception handling function initiates a dialing operation for the APN;

[0138] Step 7: After the modem dials the APN, the Idle and Connectiong process states during the dialing process will be reported to the network protection function, but the network protection function will not process it except recording the state until the dialing becomes connected state;

[0139] Step 8: After receiving the dial-up connection success message, the network protection function updates the dial-up connection status of the APN and sends the dial-up connection message to the routing module;

[0140] Step 9: The routing module reconfigures the DNS routing and default routing according to the dial-up connection information, and configures the corresponding rules according to the binding and forwarding configuration. At this time, the wired channels and wireless network channels of each domain are restored. After the configuration is completed, the network protection function responds to the message of network connection restoration;

[0141] Step 10: The network protection function re-enters the periodic network protection process according to the network connection recovery message of the routing function.

[0142] The configuration update process refers to the process of TBOX initiating the process of pulling configuration files from the cloud after the first successful networking after the terminal device is powered on and the Adaptive Cruise Control (ACC) of the vehicle is detected (starting the engine or turning on the main power).

[0143] The message requesting the configuration file update carries the version information, region information, vehicle model, etc. of the configuration file currently being used by the vehicle. The region information refers to the country or region. For example, for vehicles sold to a certain country, the region information is that country. The vehicle model information is the model definition given by the car manufacturer to the series of vehicles. For example, if a certain model is CD701, the vehicle model in the configuration file is CD701.

[0144] After receiving the configuration file update request, the cloud server enters the corresponding configuration file library path according to the region information and vehicle model information, and compares the file version information on the vehicle side. If the version information on the vehicle side is newer or the same as the version on the cloud side, it returns a "latest version" response; otherwise, it directly sends the corresponding configuration file in the request message.

[0145] The main process of configuration update is as follows Fig. 9 , the process steps are as follows:

[0146] Step S3-0, waiting for the network to connect normally (generally the first startup after the terminal is powered on);

[0147] Step S3-1, if it is detected that it is the first start or the vehicle ACC is turned on, the configuration update process is initiated;

[0148] Step S3-2, collect information of local configuration files, encapsulate it into a configuration file update request message, and initiate a request to the cloud;

[0149] Step S3-3, TBOX receives a response from the cloud. If the cloud response is "the latest version", the configuration update process ends, otherwise it goes to step S3-4;

[0150] Step S3-4, TBOX saves the configuration file obtained from the cloud and backs up the configuration file in use;

[0151] Step S3-5, TBOX activates the new configuration file just obtained from the cloud and reinitializes the wireless channel and wired network configuration;

[0152] Step S3-6, TBOX detects whether the newly configured configuration can be enabled normally. If it is normal, the backed-up old configuration file is deleted and the configuration update process ends. Otherwise, it goes to step S3-7;

[0153] Step S3-7, discard the new configuration file, restore the backup file to the current configuration file, reinitialize the wireless network channel and wired network configuration according to the backup file, and then exit the configuration file update process.

[0154] In this solution, TBOX's network configuration files will be sent to the vehicle side with each program update (mainly through OTA, and other refresh methods can also be used during the development and testing phase and maintenance process). This batch of configuration files is called the original configuration file of the upgrade package, and is stored in the configuration file in the read-only non-program working directory. After the TBOX program is started, it determines whether the software version number has changed. If there is a change, the original upgrade configuration file carried by the latest update is enabled. This file is used as a fallback configuration when the configuration file in the working directory is abnormal. The abnormal situation refers to the parameters in the configuration file in the working directory being modified to illegal configuration values, the file being damaged, the file being lost, etc.

[0155] Taking an example to illustrate, the main process steps are as follows:

[0156] Step 1: When the network is connected normally and it is detected that it is the first start or the vehicle is ACC ON, the configuration update process is triggered.

[0157] Step 2: Collect the information of the local configuration file, including the configuration file's region information, vehicle model, file version number, TUID (vehicle terminal machine code), etc., encapsulate it into a configuration file update request message, and initiate a request to the cloud.

[0158] Step 3: TBOX receives a response from the cloud. If the cloud response is "the latest version", the configuration update process ends; otherwise, it proceeds to step 4.

[0159] Step 4: TBOX saves the configuration files obtained from the cloud and backs up the configuration files currently in use.

[0160] Step 5: TBOX activates the new configuration file just obtained from the cloud and reinitializes the wireless channel and wired network configuration. The wireless channel configuration includes reconfiguring the APN, dialing, and reconfiguring the DNS routing, local default routing, domain name binding relationship, etc. through the air interface IP address, gateway address, and DNS address returned by the dialing. The wired network configuration includes the Ethernet address, VLAN configuration, default forwarding routing, domain name forwarding relationship, etc.

[0161] Step 6, TBOX detects whether the new configuration can be enabled normally (for example, APNs can dial normally, VLANs can communicate normally, etc.). If normal, the backed-up old configuration file is deleted and the configuration update process ends. Otherwise, it goes to step 7;

[0162] Step 7: Abandon the new configuration file, restore the backup file to the current configuration file, reinitialize the wireless network channel and wired network configuration according to the backup file, and then exit the configuration file update process.

[0163] Among them, in step 5, by updating the configuration file, different APNs, different VLANs, and different domain name binding forwarding strategies can be configured according to the needs. Therefore, it can meet the configuration compatibility requirements of high-end, medium-end, and low-end vehicles under the same model; it can also meet the different settings caused by different regional control deployments of different models (such as different VLAN configurations), reducing the amount of program modifications and development workload.

[0164] In step 7, if the backup configuration file is abnormal (such as unavailable or damaged configuration values), you need to further roll back the version, that is, copy the original configuration file of the upgrade package from the non-working directory to the current working directory, and enable the parameters in the original configuration file of the upgrade package. If the current configuration file parameters are found to be abnormal during normal use, you can also enable the original configuration file of the upgrade package.

[0165] Based on the same technical concept, the second embodiment of the present application provides a management system for an Internet of Vehicles network, such as Fig.10 As shown, the system includes:

[0166] The first determination module 1001 is used to determine the dial-up status of the above-mentioned Internet of Vehicles network after the above-mentioned Internet of Vehicles network dials up and registers successfully;

[0167] The dialing module 1002 is used to initiate a dialing process to the disconnected target network channel when the dialing status indicates that the target network channel in the Internet of Vehicles network is dialed off;

[0168] An updating module 1003 is used to update the connection status of the target network channel according to the dial-up process;

[0169] Configuration module 1004, used to configure routing and forwarding rules according to the above connection status;

[0170] The second determination module 1005 is used to determine whether the target network channel connection is restored after configuring the routing and forwarding rules.

[0171] For a detailed example of this embodiment, please refer to the above example, which will not be repeated here.

[0172] like Fig.11 As shown, the third embodiment of the present application provides an electronic device, including a processor 111, a communication interface 112, a memory 113 and a communication bus 114, wherein the processor 111, the communication interface 112, and the memory 113 communicate with each other through the communication bus 114.

[0173] Memory 113, used for storing computer programs;

[0174] In one embodiment, the processor 111 is used to implement the vehicle networking network management method provided by any of the aforementioned method embodiments when executing the program stored in the memory 113.

[0175] The memory and processor in the above electronic device communicate through the communication bus and the communication interface. The communication bus can be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus. The communication bus can be divided into an address bus, a data bus, a control bus, etc.

[0176] The memory may include a random access memory (RAM) or a non-volatile memory, such as at least one disk memory. Optionally, the memory may also be at least one storage device located away from the aforementioned processor.

[0177] The above-mentioned processor can be a general-purpose processor, including a central processing unit (CPU), a network processor (NP), etc.; it can also be a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components.

[0178] A fourth embodiment of the present application provides a computer-readable medium having a non-volatile program code executable by a processor.

[0179] Optionally, in an embodiment of the present application, a computer-readable medium is configured to store program code for a processor to execute the above method.

[0180] Optionally, the specific examples in this embodiment may refer to the examples described in the above embodiments, and this embodiment will not be described in detail here.

[0181] When the embodiments of the present application are specifically implemented, reference may be made to the above-mentioned embodiments, which have corresponding technical effects.

[0182] The device embodiments described above are merely illustrative, wherein the units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0183] Through the description of the above implementation methods, those skilled in the art can clearly understand that each implementation method can be implemented by means of software plus a general hardware platform, and of course, by hardware. Based on this understanding, the above technical solution is essentially or the part that contributes to the relevant technology can be embodied in the form of a software product, and the computer software product can be stored in a computer-readable storage medium, such as ROM / RAM, a disk, an optical disk, etc., including a number of instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to execute the methods described in each embodiment or some parts of the embodiments.

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

[0185] The foregoing is merely a specific embodiment of the present invention, which enables those skilled in the art to understand or implement the present invention. Various modifications to these embodiments will be apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the present invention. Therefore, the present invention will not be limited to the embodiments shown herein, but rather to the widest scope consistent with the principles and novel features claimed herein.

Claims

1. A method for managing a vehicle networking network, characterized in that: The method comprises: After the Internet of Vehicles network dials up and registers successfully, determining the dial-up status of the Internet of Vehicles network; When the dial-up status indicates that the target network channel in the Internet of Vehicles network is dialed off, initiating a dial-up process to the disconnected target network channel; Update the connection status of the target network channel according to the dial-up process; Configure routing and forwarding rules according to the connection status; After configuring the routing and forwarding rules, it is determined that the target network channel connection is restored.

2. The method for managing a vehicle networking network according to claim 1, characterized in that: When the dial-up status indicates that the target network channel in the Internet of Vehicles network is dialed off, initiating a dial-up process to the disconnected target network channel includes: When the modem detects that the dial-up of the target network channel is disconnected, initiating a dial-up process to the disconnected target network channel; or, The network status of the target network channel is detected through the network protection function. When the network status is abnormal, a network connection disconnection message is sent to the modem. The modem stops dialing the target network channel according to the network connection disconnection message, and initiates the dialing process to the disconnected target network channel after waiting for a predetermined period of time.

3. The method for managing a vehicle networking network according to claim 2, characterized in that: After the modem stops dialing the target network channel according to the network connection disconnection message, the method further includes: Initiate a dial-up disconnect message; The network protection function updates the connection state of the target network channel according to the dial-up disconnection message, and sends the dial-up disconnection message to the routing module; The routing module clears the binding, forwarding relationship and routing information of the domain name of the target network channel according to the dial-up disconnection message.

4. The method for managing a vehicle networking network according to claim 1, characterized in that: The Internet of Vehicles network dial-up and network registration includes: Obtain configuration information, detection cycle, domain name binding information and domain name forwarding rules of each network channel of the Internet of Vehicles network in the configuration file; Initiate dialing according to the configuration information; After initiating dialing, periodically detecting the network availability of each of the network channels according to the detection period; When the network is available, local services and routing rules are configured according to the domain name binding information and the domain name forwarding rules, and it is determined that the dial-up network registration is successful.

5. The method for managing a vehicle networking network according to claim 4, characterized in that: The initiating dialing according to the configuration information includes: If this is not the first dial-up and the last dial-up registration failed, turn on the flight mode; After waiting for a first period of time, turning off the flight mode; After turning off the airplane mode, restart the call.

6. The method for managing a vehicle networking network according to claim 1, characterized in that: After the Internet of Vehicles network dial-up and network registration are successful, the method further includes: When the network registration is successful for the first time, the version information, region information and vehicle model of the local configuration file are collected; Sending an update request to the cloud based on the version information, region information, and vehicle model; Receive the new version of the configuration file returned by the cloud; The channel configuration of the wireless channel and the channel configuration of the wired channel are initialized according to the new version configuration file.

7. The method for managing a vehicle networking network according to claim 6, characterized in that: After receiving the new version of the configuration file returned by the cloud, the method further includes: Backing up the local configuration file; After initializing the channel configuration of the wireless channel and the channel configuration of the wired channel according to the new version of the configuration file, if the wireless channel or the wired channel is abnormal, the channel configuration of the wireless channel and the channel configuration of the wired channel are initialized using the backup local configuration file.

8. A management system for an Internet of Vehicles network, characterized in that: The system comprises: A first determination module, configured to determine the dial-up status of the Internet of Vehicles network after the Internet of Vehicles network dials up and registers successfully; A dialing module, configured to initiate a dialing process to the disconnected target network channel when the dialing status indicates that the target network channel in the Internet of Vehicles network is dialed off; An updating module, used for updating the connection status of the target network channel according to the dialing process; A configuration module, used to configure routing and forwarding rules according to the connection status; The second determination module is used to determine whether the target network channel connection is restored after configuring the routing and forwarding rules.

9. An electronic device, characterized in that: It includes a processor, a communication interface, a memory and a communication bus, wherein the processor, the communication interface and the memory communicate with each other through the communication bus; Memory, used to store computer programs; A processor, for implementing any of the methods described in claims 1-7 when executing a program stored in a memory.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the method according to any one of claims 1 to 7 is implemented.

Images