Method and device for fast reconnection of OTA upgrade channel interruption, vbox and storage medium

Abstract

The application relates to the field of new energy vehicles, and provides an OTA upgrade channel interruption rapid reconnection method and device, a VBOX and a storage medium. The method comprises the following steps: monitoring the link connection / disconnection state of a link channel of an OTA upgrade channel in real time; when it is determined that the link connection / disconnection state is a normal connection state, and a first TCP socket channel of a DoIP bearer layer of the OTA upgrade channel is in an abnormal communication state, the first TCP socket channel is closed; a second TCP socket channel is newly established in the DoIP bearer layer of the OTA upgrade channel; after the second TCP socket channel is successfully connected, and an activation success response message returned by a receiving end is received, the second TCP socket channel is used to continue transmitting upgrade messages or receiving response messages. The application can solve the problem that upgrade fails due to a too long reconnection time after TCP SOCKET interruption, and is beneficial to improving the efficiency of OTA upgrade flashing.

Description

Technical Field

[0001] This application relates to the field of new energy vehicles, and in particular to a method, device, VBOX, and storage medium for fast reconnection after OTA upgrade channel interruption. Background Technology

[0002] For OTA (Over-the-Air) upgrades and flashes based on the DoIP (Diagnostic Communication over Internet Protocol) protocol, the maximum waiting time for the ECU (Electronic Control Unit) is approximately 5 seconds. If the maximum waiting time for the ECU is exceeded, the upgrade is considered to have failed.

[0003] During the DoIP to DoCAN UDS service process, if the diagnostic session control switches or the ECU is reset, the TCP SOCKET connection of the OTA DoIP bearer layer will be interrupted, and the route activation will fail. Before starting the diagnostic again, the TCP SOCKET connection needs to be re-established and a route activation message (for all relevant DoIP nodes) needs to be sent.

[0004] However, due to the characteristics of Ethernet, when the TCP SOCKET connection is interrupted, it takes a long time to reconnect to the original port and IP address, about 75 seconds, which greatly exceeds the maximum waiting time of the ECU (5 seconds), thus causing the OTA upgrade flashing to fail.

[0005] It is evident that existing OTA upgrade methods based on the DoIP protocol suffer from upgrade failures due to the long reconnection time after the TCPSOCKET of the OTA DoIP bearer layer is interrupted. Summary of the Invention

[0006] In view of this, embodiments of this application provide a method, apparatus, VBOX, and storage medium for fast reconnection after OTA upgrade channel interruption, in order to solve the problem in the prior art that the upgrade flashing fails due to the long reconnection time after the TCP SOCKET of the OTA DoIP bearer layer is interrupted.

[0007] A first aspect of this application provides a method for fast reconnection after an OTA upgrade channel interruption, comprising:

[0008] During the process of transmitting upgrade messages to the receiving end or receiving response messages returned by the receiving end via the OTA upgrade channel, the link connectivity status of the OTA upgrade channel is monitored in real time.

[0009] When it is determined that the link channel is in a normal connectivity state, and it is confirmed that the first TCP socket channel of the DoIP bearer layer of the OTA upgrade channel is in a communication abnormal state, the first TCP socket channel is closed, and the transmission of upgrade messages or the reception of response messages is suspended. The first TCP socket channel includes the source IP address, the destination IP address, the first source port, and the destination port.

[0010] A second TCP socket channel is established in the DoIP bearer layer of the OTA upgrade channel. The second TCP socket channel includes a source IP address, a destination IP address, a second source port, and a destination port. The first source port is different from the second source port.

[0011] After the second TCP socket channel connection is successfully established, a route activation request is sent to the receiving end.

[0012] Upon receiving a successful activation response message from the receiver, the second TCP socket channel is used to continue transmitting upgrade messages or receiving response messages.

[0013] A second aspect of this application provides an OTA upgrade channel interruption fast reconnection device, comprising:

[0014] The monitoring module is configured to monitor the link connectivity status of the OTA upgrade channel in real time during the process of transmitting upgrade messages to the receiving end or receiving response messages returned by the receiving end via the OTA upgrade channel.

[0015] The shutdown module is configured to close the first TCP socket channel and suspend the transmission of upgrade messages or the reception of response messages when the link channel is determined to be in a normal connectivity state and the first TCP socket channel of the DoIP bearer layer of the OTA upgrade channel is confirmed to be in a communication abnormal state. The first TCP socket channel includes source IP address, destination IP address, first source port and destination port.

[0016] The module is configured to establish a second TCP socket channel in the DoIP bearer layer of the OTA upgrade channel. The second TCP socket channel includes a source IP address, a destination IP address, a second source port, and a destination port. The first source port is different from the second source port.

[0017] The sending module is configured to send a route activation request to the receiving end after the second TCP socket channel connection is successfully established;

[0018] The resume module is configured to continue transmitting upgrade messages or receiving response messages using a second TCP socket channel when it receives an activation success response message returned by the receiver.

[0019] A third aspect of the embodiments of this application provides a VBOX,

[0020] Including OTA upgrades for the main control unit;

[0021] The OTA upgrade main controller includes the OTA upgrade channel interruption fast reconnection device mentioned in the second aspect above.

[0022] A fourth aspect of this application provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the steps of the above-described method.

[0023] Compared with the prior art, the beneficial effects of this application embodiment include at least the following: When the link connection status of the determined link channel is in a normal connectivity state, and it is confirmed that the first TCP socket channel of the DoIP bearer layer of the OTA upgrade channel is in a communication abnormal state, the first TCP socket channel is closed, and the transmission of upgrade messages or the reception of response messages is suspended. There is no need to wait for the first TCP socket channel to be completely closed and then recreated. Instead, a second TCP socket channel is newly established in the DoIP bearer layer of the OTA upgrade channel. The source IP address, destination IP address, and destination port of the first TCP socket channel and the second TCP socket channel are the same, but the first source port is different from the second source port. That is, a second TCP socket channel different from the first TCP socket channel is created. The entire process of creating a new second TCP socket channel takes only about 1 second, less than the maximum waiting time of the ECU (5 seconds). This enables rapid reconnection after the TCP SOCKET of the DoIP bearer layer of the OTA is interrupted, meeting the specification requirements of OTA upgrade flashing based on the DoIP protocol, and effectively solving the problem of TCP... This addresses the issue of excessive reconnection time after a SOCKET interruption, which can lead to upgrade failures. It helps improve the efficiency of OTA upgrades and flashing. Attached Figure Description

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

[0025] Figure 1 This is a schematic diagram illustrating one application scenario of this application.

[0026] Figure 2 This is a schematic diagram of the system architecture of an OTA upgrade channel interruption fast reconnection system provided in an embodiment of this application;

[0027] Figure 3This is a schematic diagram illustrating the process of establishing and closing TCP socket channel communication between VBOX and VGW, provided in an embodiment of this application.

[0028] Figure 4 This is a flowchart illustrating a method for rapid reconnection after an OTA upgrade channel interruption, provided in an embodiment of this application.

[0029] Figure 5 This is a schematic diagram of the message structure of an upgrade message provided in an embodiment of this application;

[0030] Figure 6 This is a flowchart illustrating the process of establishing a UDP and TCP socket channel in the OTA upgrade channel interruption fast reconnection method provided in the embodiments of this application.

[0031] Figure 7 This is a schematic diagram of another process for establishing a UDP and TCP socket channel in the OTA upgrade channel interruption fast reconnection method provided in the embodiments of this application;

[0032] Figure 8 This is a flowchart illustrating another method for rapid reconnection after an OTA upgrade channel interruption, provided in an embodiment of this application.

[0033] Figure 9 This is a schematic diagram of an OTA upgrade channel interruption fast reconnection device provided in an embodiment of this application;

[0034] Figure 10 This is a schematic diagram of the structure of a VBOX provided in an embodiment of this application;

[0035] Figure 11 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Detailed Implementation

[0036] In the following description, specific details such as particular system architectures and techniques are set forth for illustrative purposes and not for limitation, in order to provide a thorough understanding of the embodiments of this application. However, those skilled in the art will understand that this application may also be implemented in other embodiments without these specific details. In other instances, detailed descriptions of well-known systems, apparatuses, circuits, and methods have been omitted so as not to obscure the description of this application with unnecessary detail.

[0037] The following describes in detail, with reference to the accompanying drawings, an OTA upgrade channel interruption fast reconnection method, apparatus, and VBOX according to embodiments of this application.

[0038] Figure 1 This is a schematic diagram illustrating an application scenario according to an embodiment of this application. The application scenario may include VBOX 101, VGW 102, and cloud server 103.

[0039] VBOX (Vehicle BOX) can be the vehicle's TBOX (Telematics Control Unit). VBOX 101 contains the OTA upgrade master controller (abbreviated as "UMC").

[0040] VGW (Vehicle Gateway) is the vehicle gateway. VGW 102 contains the OTA upgrade agent (UA). VGW 102 can connect to one or more ECU components. Each ECU contains an OTA upgrade slave controller (US).

[0041] VBOX 101 and VGW 102 are connected via a 100M / 1000M Ethernet. VGW 102 can be connected to its various ECU components via a 100M / 1000M Ethernet cable (ETH) or CAN bus. VBOX 101 can connect to cloud server 103 via a private APN network.

[0042] Figure 2 This is a schematic diagram of the system architecture of an OTA upgrade channel interruption fast reconnection system provided in an embodiment of this application. For ease of description, only the parts related to the embodiment of this application are shown in the figure. Figure 2 As shown, the OTA upgrade master controller (UMC) mainly includes OTA master control service, download service, upgrade service, link monitoring service, fast link reconnection service, DoIP client application layer, DoIP protocol stack, TCP / IP layer, hardware layer, and PHY (physical layer). The OTA upgrade agent (UA) mainly includes DoIP server application layer, DoIP protocol stack, UDS protocol stack, TCP / IP layer, DoCAN, PHY (physical layer), hardware layer, and CAN (Controller Area Network).

[0043] In this embodiment, the UMC carried in VBOX 101 acts as the DoIP client (i.e., CLIENT), and the UA carried in VGW 102 acts as the DoIP server (i.e., SERVER). The UMC and UA communicate via a CLIENT<->SERVER relationship, and the OTA data stream (i.e., the OTA upgrade data stream) interacts through DoIP messages. DoIP is carried on top of the Ethernet TCP layer, and the CLIENT<->SERVER communicates via UDP or TCP SOCKET to transmit messages. OTA upgrades and flashing are performed via TCP SOCKET communication.

[0044] Figure 3 This is a schematic diagram illustrating the process of establishing and closing TCP socket channel communication between VBOX and VGW, as provided in an embodiment of this application.

[0045] like Figure 3 As shown, establishing and closing TCP socket channel communication between VBOX and VGW requires a "three-way handshake" and a "four-way handshake". After successfully establishing TCP socket channel communication between VBOX and VGW, if the TCP socket is closed due to ECU reset or session reset, the TIME_WAIT wait time for complete closure is very long, about 75 seconds. In other words, if the TCP socket is recreated, it will take 75 seconds to recreate it.

[0046] For OTA upgrades and flashing based on the DoIP protocol, the maximum waiting time for the ECU is approximately 5 seconds. If this maximum waiting time is exceeded, the upgrade / flashing is considered a failure. Because the TCP socket communication between the VBOX and VGW is interrupted due to ECU reset or session reset, recreating the TCP socket requires a 75-second wait. This recreation time far exceeds the ECU's maximum waiting time, thus causing the upgrade / flashing to fail.

[0047] To address the issue of upgrade / flash failures caused by long reconnection times after TCP socket interruptions in the OTA DoIP bearer layer, this application proposes a fast reconnection method for OTA upgrade channel interruptions. This method can be implemented by... Figure 1 UMC execution in VBOX 101.

[0048] Figure 4 This is a flowchart illustrating a method for rapid reconnection after an OTA upgrade channel interruption, provided in an embodiment of this application. Figure 4 As shown, the method for quick reconnection after an OTA upgrade channel interruption includes:

[0049] Step S401: During the process of transmitting upgrade messages to the receiving end or receiving response messages returned by the receiving end via the OTA upgrade channel, the link connectivity status of the OTA upgrade channel is monitored in real time.

[0050] The OTA upgrade channel is the communication channel between the UMC and the receiving end (UA or US) for transmitting upgrade messages / response messages.

[0051] exist Figure 3 During the loop process, the connectivity status of the OTA upgrade channel is monitored in real time.

[0052] Figure 5 This is a schematic diagram of the message structure of an upgrade message provided in an embodiment of this application. For example... Figure 5As shown, the upgrade message includes an Ethernet header (EthHead), an IP header (IPHead), a TCP / UDP header (TCP / UDPHead), DoIP data, and an FCS checksum field.

[0053] The IP packet header includes version (4 bits), header length (4 bits), priority and type of service (8 bits), total length (16 bits), identifier (16 bits), flags (3 bits), segment offset (13 bits), TTL (8 bits), protocol number (8 bits) (IP header, protocol number is "0x11", indicating TCP protocol), header checksum (16 bits), source address (32 bits) (i.e., the source IP address of VBOX), and destination address (32 bits) (i.e., the IP address of VGW or ECU).

[0054] The ECU source address is "0x0F01", and the ECU destination address is the ECU logical address, i.e., the ECU ID.

[0055] Step S402: When it is determined that the link connection status of the link channel is in a normal connection state, and it is confirmed that the first TCP socket channel of the DoIP bearer layer of the OTA upgrade channel is in a communication abnormal state, the first TCP socket channel is closed, and the transmission of upgrade messages or the reception of response messages is suspended. The first TCP socket channel includes source IP address, destination IP address, first source port and destination port.

[0056] The source IP address, which is the IP address assigned to VBOX 111, can be 192.168.69.1.

[0057] The destination IP address, which is the IP address assigned to VGW 112, can be 192.168.69.2.

[0058] The first source port's first port number is generally any one of 49152 to 65535 or 13400. For example, 49152, 49153, etc.

[0059] The destination port, whose second port number is usually 13400.

[0060] Step S403: A second TCP socket channel is established in the DoIP bearer layer of the OTA upgrade channel. The second TCP socket channel includes a source IP address, a destination IP address, a second source port, and a destination port. The first source port is different from the second source port.

[0061] The difference between the first and second source ports usually refers to the different port numbers of the first and second source ports. For example, when the first port number of the first source port is 49152, the second port number of the second source port may be 49253, 49254, 49255, etc.

[0062] Step S404: After the second TCP socket channel connection is successfully established, a route activation request is sent to the receiving end.

[0063] Step S405: Upon receiving an activation success response message from the receiving end, continue transmitting upgrade messages or receiving response messages using the second TCP socket channel.

[0064] The technical solution provided in this application, when determining that the link channel's connectivity is normal and confirming that the first TCP socket channel of the OTA upgrade channel's DoIP bearer layer is in a communication abnormal state, closes the first TCP socket channel and suspends the transmission of upgrade messages or the reception of response messages. It does not require waiting for the first TCP socket channel to be completely closed and then recreated; instead, it establishes a new second TCP socket channel in the OTA upgrade channel's DoIP bearer layer. The source IP address, destination IP address, and destination port of the first TCP socket channel and the second TCP socket channel are the same, but the first source port is different from the second source port. That is, a new second TCP socket channel different from the first TCP socket channel is created. The entire process of creating a new second TCP socket channel takes only about 1 second, less than the ECU's maximum waiting time (5 seconds). This enables rapid reconnection after the TCP socket interruption in the OTA's DoIP bearer layer, meeting the specifications for OTA upgrade flashing based on the DoIP protocol and effectively solving the problem of TCP... This addresses the issue of excessive reconnection time after a SOCKET interruption, which can lead to upgrade failures. It helps improve the efficiency of OTA upgrades and flashing.

[0065] In some embodiments, combined with Figure 6 Before step S401 above, the following steps are also included:

[0066] Step S601: Establish a UDP socket channel with the receiving end and send a vehicle notification request to the receiving end via the UDP socket channel.

[0067] Combination Figure 1 , Figure 2 , Figure 7When VBOX 101 initiates the OTA task, the OTA master control service calls the download service to download the upgrade file corresponding to the target ECU that needs to be upgraded and flashed from the cloud server 103 via the dedicated network APN. If the upgrade file is successfully downloaded, a UDP socket channel (UDPSOCKET) is established between VBOX 101 and VGW 102 (the receiving end). The source IP (VBOX) of this UDP socket channel is 192.168.69.1, the destination IP (VGW) is 192.168.69.2, and the source port and destination port are both 13400. Then, a Vehicle Notification Request (DoIP message) is sent to the receiving end via this UDP socket channel to obtain information such as the VIN (Vehicle Identification Number), the gateway logical address of VGW 102, and the upgrade version number.

[0068] Step S602: When the vehicle notification response information returned by the receiving end in response to the vehicle channel request is received in the UDP socket channel, a first TCP socket channel is established in the DoIP bearer layer of the OTA upgrade channel.

[0069] Combination Figure 3 , Figure 7 If VBOX 101 receives a vehicle notification response (including VIN, VGW 102's gateway logical address, upgrade version number, etc.) from VGW 102 in the UDP socket channel in response to the vehicle channel request, then a first TCP socket channel is established in the DoIP bearer layer of the OTA upgrade channel. The source IP address (VBOX) of the first TCP socket channel is 192.168.69.1, the destination IP address (VGW) is 192.168.69.2, the first source port number is 49152, and the destination port number is 13400.

[0070] Step S603: If the first TCP socket channel connection is confirmed to be successful and an activation success response message is received from the receiving end via the first TCP socket channel, then an upgrade message is transmitted to the receiving end via the OTA upgrade channel or a response message is received from the receiving end.

[0071] Combination Figure 3 , Figure 7If the three-way handshake between VBOX 101 and VGW 102 is successful when establishing the first TCP socket channel, the connection of the first TCP socket channel is confirmed to be successful. At this time, VBOX 101 sends a route activation request to VGW 102; if it receives a route activation response (i.e., activation success response message) from VGW 102 via the first TCP socket channel, it can begin transmitting upgrade messages to the receiving end or receiving response messages returned by the receiving end through the OTA upgrade channel. During the sending and receiving of upgrade messages or response messages, the UMC of VBOX 101 will monitor the link connectivity status of the OTA upgrade channel in real time.

[0072] In some embodiments, determining the link connectivity status of a link channel as a normal connectivity status specifically includes:

[0073] Obtain the local network card name of the receiving end and find the network card connection status value corresponding to the local network card name;

[0074] If the network card connection status value is the first set value, then the link channel's connection status is determined to be a normal connection status.

[0075] If the network card connection status value is the second set value, then the link channel's connection status is determined to be an abnormal disconnection status.

[0076] The VBOX 101 can be configured with one or more network interface card (NIC) ports, each of which connects to a gateway device. For example, the VBOX 101 has n NIC ports, where n is a positive integer. NIC port 1 is connected to gateway device VGW1, NIC port 2 is connected to gateway device VGW2, and so on, with NIC port n connected to gateway device VGWn.

[0077] As an example, assuming the receiving end is VGW1, we can first obtain the local network interface name of VGW1, then find the network interface port 1 corresponding to the local network interface name of VGW1, and then further obtain the network interface connection status value of that network interface port 1. A network interface connection status value of the second preset value (such as "0") indicates linkdown, and a value of the first preset value (such as "1") indicates linkup. Linkdown indicates that there is a hardware or network interface failure, and the link connection status is abnormally disconnected; linkup indicates that the hardware and network interface are normal, and the link connection status is normally connected.

[0078] When the network card connection status value is the second set value, it is considered that there is a hardware failure and the OTA upgrade process is directly exited.

[0079] In some embodiments, confirming that the first TCP socket channel of the DoIP bearer layer of the OTA upgrade channel is in a communication abnormal state includes:

[0080] Get the connection status return value of the first TCP socket channel;

[0081] If the connection status return value is less than zero, it confirms that the first TCP socket channel of the DoIP bearer layer of the OTA upgrade channel is in a communication abnormal state.

[0082] As an example, the connection status return value of the first TCP socket channel can be obtained by using the Getsockopt() function. Then, based on the connection status return value, it can be determined whether the first TCP socket channel of the DoIP bearer layer of the OTA upgrade channel is in a communication abnormal state.

[0083] Specifically, Getsockopt(socket,IPPROTO_TCP,TCP_INFO,&info,(socklen_t*)&infolen); if ((TCP_ESTABLISHED!=info.tcpi_state)||(ret<0)) then the connection is broken (i.e., the first TCP socket channel of the DoIP bearer layer of the OTA upgrade channel is in a communication abnormal state), otherwise it is normal (i.e., the first TCP socket channel of the DoIP bearer layer of the OTA upgrade channel is in a communication normal state).

[0084] In some embodiments, a second TCP socket channel is established in the DoIP bearer layer of the OTA upgrade channel, including:

[0085] Obtain the third setting value, the first reconnection count, and the first port number of the first source port;

[0086] The second port number of the second source port is determined based on the first port number, the third setting value, and the first reconnection count;

[0087] Based on the source IP address, destination IP address, second source port, and destination port, a new second TCP socket channel is established in the DoIP bearer layer of the OTA upgrade channel.

[0088] The third setting value is a numerical value set based on the first port number of the first source port. It is mainly used to add or subtract this value from the first port number, and then combine it with the first reconnection count to obtain a new port number (i.e., the second port number of the second source port), thus distinguishing the new port number (i.e., the second port number) from the port number of the first source port. This third setting value can be flexibly set according to the first port number of the first source port. For example, when the first port number of the first source port is 49152, the third setting value can be 100, 200, 300, etc. When the first port number of the first source port is 65535, the third setting value can be -100, -200, -300, etc.

[0089] The first reconnection count typically refers to the number of times a new second TCP socket channel connection is established after the first TCP socket channel between VBOX 101 and VGW 102 is interrupted. For example, this first reconnection count may be 1, 2, 3, etc.

[0090] As an example, suppose the first TCP socket channel between VBOX 101 and VGW 102 is interrupted. When a second TCP socket channel is newly established, the first reconnection count is 1. If the first attempt to establish the second TCP socket channel fails, when a third TCP socket channel is newly established, the first reconnection count is incremented by 1, changing it to the second reconnection count, which is 2. If the second attempt to establish the third TCP socket channel fails, when a fourth TCP socket channel is newly established, the first reconnection count is incremented by 2, changing it to the third reconnection count, which is 3.

[0091] In some embodiments, a second TCP socket channel is established in the DoIP bearer layer of the OTA upgrade channel based on the source IP address, destination IP address, second source port, and destination port, specifically including:

[0092] Send a connection request to the receiving end to establish a second TCP socket channel;

[0093] Upon receiving the connection response information for the connection request returned by the receiving end via the second TCP socket channel, a connection success message is returned to the receiving end to confirm that the second TCP socket channel connection is successful.

[0094] The second TCP socket channel between VBOX 101 and VGW 102 is uniquely identified by the source IP address, destination IP address, second source port, and destination port.

[0095] Specifically, the process of establishing a new second TCP socket channel can be found in [reference needed]. Figure 3 The three-way handshake process for TCP connections.

[0096] During the first handshake, VBOX 101 sends a connection request to VGW 102. This connection request includes the SYNj flag (if it is 1) and a randomly generated sequence number c_seq. The client (VGW 102) changes its state to SYN-SENT.

[0097] In the second handshake, the server (VBOX 101) receives the SYNj flag (e.g., 1) from the client's connection request. Knowing the client wants to establish a connection, the server decides whether to reject the connection, confirm the connection, or discard the data packet. If confirming the connection, the server sends a connection response message to the client. This response message contains an ACKj+1 flag set to 1, an acknowledgment sequence number ack = c_seq+1, a SYNk flag set to 1, a random sequence number s_seq, and the status changes from LISTEN to SYN-RCVD.

[0098] In the third handshake, the client receives the connection acknowledgment information and performs verification, checking the ACK j+1 flag and the acknowledgment sequence number ack = c_seq + 1. If it determines that it is an acknowledgment packet (connection acknowledgment information) from the server, it changes its own state to ESTABLISHED and sends an acknowledgment packet (i.e., a connection success message) to the server. The server receives the client's packet (connection success message), checks the ACK flag and the acknowledgment sequence number ack = s_seq + 1, changes its own state to ESTABLISHED, and then data transmission can proceed. At this point, the second TCP socket channel is successfully established.

[0099] In some embodiments, after establishing a second TCP socket channel in the DoIP bearer layer of the OTA upgrade channel, the method further includes:

[0100] If the second TCP socket channel connection is confirmed to be unsuccessful, then determine whether the number of first reconnections is less than the set threshold.

[0101] If the first reconnection count is less than the set threshold, then the first reconnection count will be adjusted to the second reconnection count.

[0102] The third port number of the third source port is determined based on the first port number, the first set value, and the second reconnection count.

[0103] Based on the source IP address, destination IP address, third source port, and destination port, a new third TCP socket channel is established in the DoIP bearer layer of the OTA upgrade channel.

[0104] If the third TCP socket channel connection is confirmed to be successful, a route activation request is sent to the receiving end.

[0105] Upon receiving a successful activation response message from the receiver, the third TCP socket channel is used to continue transmitting upgrade messages or receiving response messages.

[0106] The threshold value, i.e., the reconnection count threshold, can be flexibly set according to actual needs. As long as the time required to re-establish the TCP socket channel between VBOX 101 and VGW 102 does not exceed the ECU's maximum waiting time (5 seconds) within the set threshold, it is acceptable. Typically, the reconnection count threshold can be set to 3 times.

[0107] As an example, assuming the threshold is set to 3 times, the source IP address (VBOX 101) of the first TCP socket channel is 192.168.69.1, the destination IP address (VGW 102) is 192.168.69.2, the first port number of the first source port is 49152, and the destination port number is 13400. Then, when the first TCP socket channel is interrupted, the first TCP socket channel is closed, and a new second TCP socket channel is established. In the second TCP socket channel, the source IP address (VBOX 101) is 192.168.69.1, the destination IP address (VGW 102) is 192.168.69.2, the second port number of the second source port is 49253 (i.e., the second port number 49253 = the first port number 49152 + the third set value 100 + the first reconnection count 1), and the destination port number is 13400. If the second TCP socket channel connection fails, it checks if the first reconnection count is less than a set threshold. The comparison shows that the first reconnection count (1) is less than the set threshold (3). Therefore, the first reconnection count (1) can be adjusted to the second reconnection count (2) (i.e., adding 1 to the first reconnection count, making it 2). A new third TCP socket channel is then established. The source IP address (VBOX 101) of the third TCP socket channel is 192.168.69.1, the destination IP address (VGW 102) is 192.168.69.2, the third source port number is 49254 (i.e., third port number 49253 = first port number 49152 + third set value 100 + second reconnection count 2), and the destination port number is 13400. If the third TCP socket channel connection succeeds, a route activation request is sent to the receiving end. Upon receiving a successful activation response message from the receiving end, the third TCP socket channel is used to continue transmitting upgrade messages or receiving response messages. If the third TCP socket channel connection fails, it checks if the second reconnection count is less than a set threshold. The comparison shows that the second reconnection count (2) is less than the set threshold (3). Therefore, the second reconnection count (2) can be adjusted to the third reconnection count (3) (i.e., add 1 to the second reconnection count, making it 3). At this point, the third reconnection count (3) equals the set threshold (3), and the OTA upgrade process exits.

[0108] Typically, since the IP addresses and destination ports assigned to the client and server are usually fixed, the source port number assigned to the client can be adjusted to distinguish the source port number of the newly rebuilt TCP socket channel from that of the previously established TCP socket channel. This eliminates the need to wait for the previous TCP socket channel to be completely closed before recreating it using the previous source port. This enables rapid reconnection after the TCP socket of the OTA DoIP bearer layer is interrupted, meeting the specifications for OTA upgrades and flashing based on the DoIP protocol. It effectively solves the problem of upgrade failure caused by excessively long reconnection time after TCP socket interruption, thus improving the efficiency of OTA upgrades and flashing.

[0109] Figure 8 This is a flowchart illustrating another method for rapid reconnection after an OTA upgrade channel interruption, provided in an embodiment of this application.

[0110] The OTA upgrade channel interruption fast reconnection method is connected to Figure 7The process involves checking if the VGW response indicates successful activation. If so, the system monitors the connectivity status of the OTA upgrade channel in real time. Then, it checks if the link status is Linkup (i.e., network interface card connection status value is 1). If Linkup, it checks if TCP socket communication is normal. If Linkdown (i.e., network interface card connection status value is 0), the OTA upgrade process exits. If TCP SOCKET communication fails, the current TCP SOCKET channel (i.e., the first TCP SOCKET channel) is closed, and a TCP SOCKET CLIENT (i.e., the second TCP SOCKET channel) is established. The system then checks if the second TCP SOCKET channel is successfully connected. If the second TCP SOCKET channel is successfully connected (i.e., the TCP three-way handshake between VBOX and VGW is successful), VBOX sends a "routing activation request" to VGW. If VBOX receives a "activation successful" response from VGW, VBOX's UMC sends an upgrade message to VGW's UA, which then forwards the upgrade message to the ECU. The system then checks if the upgrade is complete. If the upgrade is complete, the OTA upgrade process exits. If the upgrade is incomplete, the system returns to the step of "real-time monitoring of the link connectivity status of the OTA upgrade channel." If the second TCP SOCKET channel connection fails, check if the number of times the TCP SOCKET channel has been re-established is less than 3. If the number is less than 3, return to the "Establish TCP SOCKET CLIENT" step and establish a new third TCP SOCKET channel. Check if the third TCP SOCKET channel connection is successful. If the third TCP SOCKET channel connection fails, check if the number of times the TCP SOCKET channel has been re-established is less than 3. If the number is equal to or greater than 3, exit the OTA upgrade process.

[0111] When sending and receiving DoIP upgrade messages or responses, the system monitors the TCP socket channel in real time for failures or abnormalities that could cause it to close. If communication is normal, the upgrade message is sent to the ECU. If a failure occurs, the TCP socket is closed. The TCP socket is then recreated with the source IP address, destination IP address, and destination port remaining unchanged, while the source port is set to 49152 + 100 + looptimes. A connection is then established with VGW 102, which should succeed within approximately 1 second, meeting the DoIP upgrade flashing requirements. After a successful connection, the UMC sends a "route activation request" to VGW 102, which responds with "activation successful." OTA upgrade flashing can then proceed until the upgrade is complete.

[0112] By actively closing the faulty TCP SOCKET channel and only changing the source port of the faulty TCP SOCKET channel while keeping the source IP address, destination IP address, and destination port unchanged, a new TCP SOCKET can be created. This allows for a quick reconnection to the VGW 102 TCP SOCKET server, with a reconnection time of approximately 1 second. This meets the DoIP upgrade flashing specifications. After a successful reconnection, OTA upgrade flashing can continue, which helps improve the efficiency of OTA flashing.

[0113] Furthermore, closed TCP sockets will be completely closed after a period of waiting and can be reused when a new connection is created. For example, if the first TCP socket channel fails and is actively closed, and a second TCP socket channel is successfully established, and if a failure is detected during the transmission or reception of upgrade or acknowledgment messages using the second TCP socket channel, while the first TCP socket channel is completely closed and in a reusable state, then the second TCP socket channel can be closed, and the first TCP socket channel can be re-established using the same source IP address, destination IP address, destination port, and first source port. After successfully establishing the first TCP socket channel, it can be used for OTA upgrades.

[0114] The above methods can quickly diagnose and determine the cause of the OTA upgrade channel link disconnection (whether it is a link channel failure or a TCP socket channel interruption, etc.), so as to take appropriate countermeasures in a timely manner and ensure the normal progress of the OTA upgrade process.

[0115] All of the above-mentioned optional technical solutions can be combined in any way to form the optional embodiments of this application, and will not be described in detail here.

[0116] The following are embodiments of the apparatus described in this application, which can be used to execute the embodiments of the method described in this application. For details not disclosed in the apparatus embodiments of this application, please refer to the embodiments of the method described in this application.

[0117] Figure 9 This is a schematic diagram of an OTA upgrade channel interruption fast reconnection device provided in an embodiment of this application. Figure 9 As shown, the OTA upgrade channel interruption quick reconnection device includes:

[0118] The monitoring module 901 is configured to monitor the link connectivity status of the OTA upgrade channel in real time during the process of transmitting upgrade messages to the receiving end or receiving response messages returned by the receiving end via the OTA upgrade channel.

[0119] The shutdown module 902 is configured to close the first TCP socket channel and suspend the transmission of upgrade messages or the reception of response messages when the link channel is determined to be in a normal connected state and the first TCP socket channel of the DoIP bearer layer of the OTA upgrade channel is confirmed to be in a communication abnormal state. The first TCP socket channel includes a source IP address, a destination IP address, a first source port, and a destination port.

[0120] Module 903 is configured to establish a second TCP socket channel in the DoIP bearer layer of the OTA upgrade channel. The second TCP socket channel includes a source IP address, a destination IP address, a second source port, and a destination port. The first source port is different from the second source port.

[0121] The sending module 904 is configured to send a route activation request to the receiving end after the second TCP socket channel connection is successfully established;

[0122] The resume module 905 is configured to continue transmitting the upgrade message or receiving the response message using the second TCP socket channel when it receives the activation success response message returned by the receiver.

[0123] The technical solution provided in this application, when determining that the link channel's connectivity is normal and confirming that the first TCP socket channel of the OTA upgrade channel's DoIP bearer layer is in a communication abnormal state, closes the first TCP socket channel and suspends the transmission of upgrade messages or the reception of response messages. It does not require waiting for the first TCP socket channel to be completely closed and then recreated; instead, it establishes a new second TCP socket channel in the OTA upgrade channel's DoIP bearer layer. The source IP address, destination IP address, and destination port of the first TCP socket channel and the second TCP socket channel are the same, but the first source port is different from the second source port. That is, a new second TCP socket channel different from the first TCP socket channel is created. The entire process of creating a new second TCP socket channel takes only about 1 second, less than the ECU's maximum waiting time (5 seconds). This enables rapid reconnection after the TCP socket interruption in the OTA's DoIP bearer layer, meeting the specifications for OTA upgrade flashing based on the DoIP protocol and effectively solving the problem of TCP... This addresses the issue of excessive reconnection time after a SOCKET interruption, which can lead to upgrade failures. It helps improve the efficiency of OTA upgrades and flashing.

[0124] In some embodiments, the above-mentioned OTA upgrade channel interruption fast reconnection device further includes:

[0125] The first channel establishment module is configured to establish a UDP socket channel with the receiving end and send a vehicle notification request to the receiving end via the UDP socket channel.

[0126] The second channel establishment module is configured to establish the first TCP socket channel in the DoIP bearer layer of the OTA upgrade channel when it receives the vehicle notification response information returned by the receiving end in response to the vehicle notification request in the UDP socket channel.

[0127] The transceiver module is configured to, if it confirms that the first TCP socket channel connection is successful and receives an activation success response message returned by the receiving end through the first TCP socket channel, then transmit an upgrade message to the receiving end or receive a response message returned by the receiving end through the OTA upgrade channel.

[0128] In some embodiments, the closing module 902 includes:

[0129] The first acquisition unit is configured to acquire the local network card name of the receiving end and find the network card connection status value corresponding to the local network card name;

[0130] The first determining unit is configured to determine the link connection status of the link channel as normal connection status if the network card connection status value is a first set value.

[0131] The second determining unit is configured to determine the link connection status of the link channel as an abnormal disconnection state if the network card connection status value is a second set value.

[0132] In some embodiments, the closing module 902 further includes:

[0133] The second acquisition unit is configured to acquire the connection status return value of the first TCP socket channel;

[0134] The confirmation unit is configured to confirm that the first TCP socket channel of the DoIP bearer layer of the OTA upgrade channel is in a communication abnormal state if the connection status return value is less than zero.

[0135] In some embodiments, the establishment module 903 includes:

[0136] The acquisition unit is configured to acquire a third set value, a first reconnection count, and a first port number of the first source port;

[0137] The determining unit is configured to determine the second port number of the second source port based on the first port number, the third setting value, and the first reconnection count;

[0138] The newly created unit is configured to establish a second TCP socket channel in the DoIP bearer layer of the OTA upgrade channel based on the source IP address, destination IP address, second source port, and destination port.

[0139] In some embodiments, the newly constructed unit includes:

[0140] The request sending component is configured to send a connection request to the receiving end via a second TCP socket channel;

[0141] The connection confirmation component is configured to return a connection success message to the receiving end upon receiving a connection response message for the connection request returned by the receiving end via the second TCP socket channel, thus confirming that the second TCP socket channel connection is successful.

[0142] In some embodiments, the newly constructed unit further includes:

[0143] The judgment component is configured to determine whether the first reconnection count is less than a set threshold if it is confirmed that the second TCP socket channel connection is unsuccessful.

[0144] The adjustment component is configured to adjust the first reconnection count to the second reconnection count if the first reconnection count is less than a set threshold.

[0145] The component is configured to determine the third port number of the third source port based on the first port number, the third setting value, and the second reconnection count.

[0146] The component is configured to establish a new third TCP socket channel in the DoIP bearer layer of the OTA upgrade channel based on the source IP address, destination IP address, third source port, and destination port.

[0147] The activation request sending component is configured to send a route activation request to the receiving end if the third TCP socket channel connection is determined to be successful.

[0148] The resume component is configured to continue transmitting upgrade messages or receiving response messages using a third TCP socket channel when an activation success response message is received from the receiver.

[0149] In this embodiment, it is not necessary to wait for the previous TCP socket channel to be completely closed before recreating the TCP socket channel using the source port of the previous TCP socket channel. This enables fast reconnection after the TCP SOCKET of the OTA DoIP bearer layer is interrupted, meets the specification requirements of OTA upgrade and flashing based on the DoIP protocol, and effectively solves the problem of upgrade failure caused by excessive reconnection time after TCP SOCKET interruption, which is conducive to improving the efficiency of OTA upgrade and flashing.

[0150] It should be understood that the sequence number of each step in the above embodiments does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0151] Figure 10 This is a schematic diagram of the structure of a VBOX provided in an embodiment of this application. Figure 10 As shown, the VBOX includes an OTA upgrade controller (i.e., UMC); the OTA upgrade controller includes... Figure 9 The OTA upgrade channel interruption quick reconnection device shown is illustrated.

[0152] The technical solution provided in this application embodiment allows VBOX to close the first TCP socket channel and suspend the transmission of upgrade messages or the reception of acknowledgment messages when the link channel's connectivity status is normal and the first TCP socket channel of the OTA upgrade channel's DoIP bearer layer is confirmed to be in a communication abnormal state. This is done without waiting for the first TCP socket channel to be completely closed and then recreated. Instead, a second TCP socket channel is newly established in the OTA upgrade channel's DoIP bearer layer. The source IP address, destination IP address, and destination port of the first and second TCP socket channels are the same, but the first and second source ports are different. This creates a new second TCP socket channel, different from the first. The entire process of creating a new second TCP socket channel takes only about 1 second, less than the ECU's maximum waiting time (5 seconds). This enables rapid reconnection after the TCP socket interruption in the OTA's DoIP bearer layer, meeting the specifications for OTA upgrade flashing based on the DoIP protocol and effectively solving the problem of TCP interruption. This addresses the issue of excessive reconnection time after a SOCKET interruption, which can lead to upgrade failures. It helps improve the efficiency of OTA upgrades and flashing.

[0153] Figure 11 This is a schematic diagram of the electronic device 11 provided in an embodiment of this application. Figure 11 As shown, the electronic device 11 of this embodiment includes: a processor 1101, a memory 1102, and a computer program 1103 stored in the memory 1102 and executable on the processor 1101. When the processor 1101 executes the computer program 1103, it implements the steps in the various method embodiments described above. Alternatively, when the processor 1101 executes the computer program 1103, it implements the functions of each module / unit in the various device embodiments described above.

[0154] Electronic device 11 may be a desktop computer, laptop, handheld computer, cloud server, or other electronic device. Electronic device 11 may include, but is not limited to, processor 1101 and memory 1102. Those skilled in the art will understand that... Figure 11 This is merely an example of electronic device 11 and does not constitute a limitation on electronic device 11. It may include more or fewer components than shown, or different components.

[0155] The processor 1101 may be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc.

[0156] The memory 1102 can be an internal storage unit of the electronic device 11, such as a hard disk or RAM of the electronic device 11. The memory 1102 can also be an external storage device of the electronic device 11, such as a plug-in hard disk, Smart Media Card (SMC), Secure Digital (SD) card, FlashCard, etc., equipped on the electronic device 11. The memory 1102 can also include both internal and external storage units of the electronic device 11. The memory 1102 is used to store computer programs and other programs and data required by the electronic device.

[0157] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the above-described division of functional units and modules is merely an example. In practical applications, the above functions can be assigned to different functional units and modules as needed, that is, the internal structure of the device can be divided into different functional units or modules to complete all or part of the functions described above. The functional units and modules in the embodiments can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0158] If an integrated module / unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, all or part of the processes in the methods of the above embodiments can also be implemented by a computer program instructing related hardware. The computer program can be stored in a computer-readable storage medium, and when executed by a processor, it can implement the steps of the various method embodiments described above. The computer program may include computer program code, which can be in the form of source code, object code, executable files, or certain intermediate forms. The computer-readable medium may include: any entity or device capable of carrying computer program code, recording media, USB flash drives, portable hard drives, magnetic disks, optical disks, computer memory, read-only memory (ROM), random access memory (RAM), electrical carrier signals, telecommunication signals, and software distribution media, etc. It should be noted that the content included in the computer-readable medium may be appropriately added to or subtracted according to the requirements of legislation and patent practice in the jurisdiction. For example, in some jurisdictions, according to legislation and patent practice, the computer-readable medium does not include electrical carrier signals and telecommunication signals.

[0159] The above embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of this application, and should all be included within the protection scope of this application.

Claims

1. A method for rapid reconnection after an OTA upgrade channel interruption, characterized in that, include: During the process of transmitting upgrade messages to the receiving end or receiving response messages returned by the receiving end via the OTA upgrade channel, the link connectivity status of the OTA upgrade channel is monitored in real time. When it is determined that the link channel is in a normal connectivity state, and it is confirmed that the first TCP socket channel of the DoIP bearer layer of the OTA upgrade channel is in a communication abnormal state, the first TCP socket channel is closed, and the transmission of upgrade messages or the reception of response messages is suspended. The first TCP socket channel includes a source IP address, a destination IP address, a first source port, and a destination port. A second TCP socket channel is established in the DoIP bearer layer of the OTA upgrade channel. The second TCP socket channel includes a source IP address, a destination IP address, a second source port, and a destination port. The first source port is different from the second source port. After the second TCP socket channel is successfully connected, a route activation request is sent to the receiving end; Upon receiving the activation success response message returned by the receiving end, the second TCP socket channel is used to continue transmitting upgrade messages or receiving response messages; A second TCP socket channel is established in the DoIP bearer layer of the OTA upgrade channel, including: Obtain the third set value, the first reconnection count, and the first port number of the first source port; The second port number of the second source port is determined based on the first port number, the third set value, and the first reconnection count; Based on the source IP address, destination IP address, second source port, and destination port, a new second TCP socket channel is established in the DoIP bearer layer of the OTA upgrade channel.

2. The method according to claim 1, characterized in that, Determining the link connectivity status of the link channel to be in a normal connectivity state includes: Obtain the local network card name of the receiving end, and find the network card connection status value corresponding to the local network card name; If the network card connection status value is the first set value, then the link connection status of the link channel is determined to be a normal connection status. If the network card connection status value is the second preset value, then the link channel's link connectivity status is determined to be an abnormal disconnection status.

3. The method according to claim 1, characterized in that, Confirming that the first TCP socket channel of the DoIP bearer layer of the OTA upgrade channel is in a communication abnormal state includes: Obtain the connection status return value of the first TCP socket channel; If the connection status return value is less than zero, it is confirmed that the first TCP socket channel of the DoIP bearer layer of the OTA upgrade channel is in a communication abnormal state.

4. The method according to claim 1, characterized in that, Based on the source IP address, destination IP address, second source port, and destination port, a new second TCP socket channel is established in the DoIP bearer layer of the OTA upgrade channel, including: A connection request is sent to the receiving end via the second TCP socket channel; Upon receiving the connection response information for the connection request returned by the receiving end via the second TCP socket channel, a connection success message is returned to the receiving end, confirming that the second TCP socket channel connection is successful.

5. The method according to claim 1, characterized in that, After establishing a second TCP socket channel in the DoIP bearer layer of the OTA upgrade channel, the following is also included: If it is confirmed that the second TCP socket channel connection is unsuccessful, then determine whether the first reconnection count is less than a set threshold. If the first reconnection count is less than the set threshold, then the first reconnection count is adjusted to the second reconnection count; The third port number of the third source port is determined based on the first port number, the third set value, and the second reconnection count. Based on the source IP address, destination IP address, third source port, and destination port, a new third TCP socket channel is established in the DoIP bearer layer of the OTA upgrade channel. If the third TCP socket channel connection is confirmed to be successful, a route activation request is sent to the receiving end. Upon receiving the activation success response message from the receiving end, the third TCP socket channel is used to continue transmitting upgrade messages or receiving response messages.

6. The method according to claim 1, characterized in that, Before real-time monitoring of the link connectivity status of the OTA upgrade channel during the process of transmitting upgrade messages to the receiving end or receiving response messages from the receiving end via the OTA upgrade channel, the process further includes: Establish a UDP socket channel with the receiving end, and send a vehicle notification request to the receiving end through the UDP socket channel; When the vehicle notification response information returned by the receiving end in response to the vehicle notification request is received in the UDP socket channel, a first TCP socket channel is established in the DoIP bearer layer of the OTA upgrade channel. If the first TCP socket channel connection is confirmed to be successful, and an activation success response message is received from the receiving end via the first TCP socket channel, then an upgrade message is transmitted to the receiving end via the OTA upgrade channel or a response message is received from the receiving end.

7. A device for rapid reconnection after OTA upgrade channel interruption, characterized in that, The apparatus is used to implement the method as described in any one of claims 1 to 6, the apparatus comprising: The monitoring module is configured to monitor the link connectivity status of the OTA upgrade channel in real time during the process of transmitting upgrade messages to the receiving end or receiving response messages returned by the receiving end via the OTA upgrade channel. The shutdown module is configured to close the first TCP socket channel and suspend the transmission of upgrade messages or the reception of response messages when it is determined that the link channel is in a normal connectivity state and the first TCP socket channel of the DoIP bearer layer of the OTA upgrade channel is in a communication abnormal state. The first TCP socket channel includes a source IP address, a destination IP address, a first source port, and a destination port. The module is configured to establish a second TCP socket channel in the DoIP bearer layer of the OTA upgrade channel. The second TCP socket channel includes a source IP address, a destination IP address, a second source port, and a destination port. The first source port is different from the second source port. The sending module is configured to send a route activation request to the receiving end after the second TCP socket channel connection is successfully established; The resume module is configured to continue transmitting upgrade messages or receiving response messages using the second TCP socket channel when it receives an activation success response message returned by the receiving end.

8. A VBOX, characterized in that, Including OTA upgrades for the main control unit; The OTA upgrade master controller includes the OTA upgrade channel interruption fast reconnection device as described in claim 7.

9. A computer-readable storage medium storing a computer program, characterized in that, When the computer program is executed by a processor, it implements the steps of the method as described in any one of claims 1 to 6.

Images