A network management method and device for vehicle T-BOX device

Abstract

The present application relates to the field of vehicle network technology, and discloses a network management method and device for a vehicle T-BOX device. The method includes: the method is executed on the T-BOX device, and the method includes: receiving a network restart request sent by the vehicle computer through a network restart interface; in response to the network restart request, determining whether the T-BOX device is in a remote upgrade state or a remote control state; if the T-BOX device is not in a remote upgrade state and is not in a remote control state, a notification message for executing a network restart action is sent to the vehicle computer, and the execution of the network restart action is triggered after a first preset time. The present application effectively solves the problem of users not restarting the T-BOX channel by adding a network restart interface.

Description

Technical Field

[0001] The present application relates to the field of vehicle network technology, and in particular, to a network management method and device for a vehicle T-BOX device. Background Art

[0002] In the prior art, a comparative document with publication number CN113660633A discloses a vehicle network connection dialing method and device, which performs network search and network access operations when the networking module in the T-BOX is started and initialized, and dials when the T-BOX is restarted. When the vehicle power gear is OFF, the T-BOX restart only triggers dialing once. After the dialing is successful, the network is maintained, and the network is not actively disconnected when the T-BOX restart conditions are not met. When the dialing fails, no redialing is performed.

[0003] If it automatically restarts once when OFF, usually at the original location, the vehicle has not moved, so the network situation will not improve. If the Internet is not restored after one restart, for example, the original location encountered a network problem, and the reason for not being able to access the Internet is that a rejection code returned by the network side is received, and the rejection code requires a restart of the device to recover according to the 3GPP protocol. At this time, the location has not changed, and even if it is restarted, it will still be rejected by the network side and cannot access the Internet. Later, even if you drive to a place with good network, if you have encountered a situation similar to the above that requires a restart to restore the Internet, you still cannot restore the Internet because there is no means of restarting. Summary of the invention

[0004] The purpose of the present application is to provide a network management method and device for a vehicle T-BOX device, which effectively solves the problem that the user fails to restart the T-BOX channel by adding a network restart interface.

[0005] Other features and advantages of the present application will become apparent from the following detailed description, or may be learned in part by the practice of the present application.

[0006] According to one aspect of an embodiment of the present application, a network management method for a vehicle T-BOX device is provided, the method being executed on the T-BOX device, the method comprising: receiving a network restart request sent by a vehicle computer through a network restart interface; in response to the network restart request, determining whether the T-BOX device is in a remote upgrade state or a remote control state; if the T-BOX device is not in a remote upgrade state and is not in a remote control state, sending a notification message of executing a network restart action to the vehicle computer, and triggering the execution of the network restart action after a first preset time.

[0007] In some embodiments, before receiving a network restart request sent by the vehicle computer through the network restart interface, the method also includes: after establishing a Socket connection with the vehicle computer for the first time, receiving a handshake request sent by the vehicle computer, and sending a handshake response to the vehicle computer; after shaking hands with the vehicle computer, receiving a heartbeat request sent by the vehicle computer, and sending a heartbeat response to the vehicle computer to maintain the Socket connection with the vehicle computer.

[0008] In some embodiments, after maintaining the Socket connection with the vehicle computer, the method further includes: periodically acquiring network data information from the network; and reporting the network data information to the vehicle computer.

[0009] In some embodiments, the method further includes: if the T-BOX device is in a remote upgrade state or in a remote control state, sending a notification message of network restart failure to the vehicle computer.

[0010] According to one aspect of an embodiment of the present application, a network management method for a vehicle T-BOX device is provided, the method being executed on a vehicle computer, the method comprising: after maintaining a Socket connection with the vehicle computer, sending a network restart request to the T-BOX device through a network restart interface to trigger the T-BOX device to perform a network restart action; if a notification message for performing a network restart action sent by the T-BOX device is not received within a second preset time, repeating the step of sending a network restart request to the T-BOX device through the network restart interface until a notification message for performing a network restart action is received by the T-BOX device within a first preset number of repetitions and within the second preset time.

[0011] In some embodiments, before maintaining the Socket connection with the vehicle computer, the method further includes: after establishing the Socket connection with the vehicle computer for the first time, sending a handshake request to the T-BOX device and receiving a handshake response sent by the T-BOX device; after handshaking with the T-BOX device, periodically sending a heartbeat request to the T-BOX device and receiving a heartbeat response sent by the T-BOX device to maintain the Socket connection with the vehicle computer.

[0012] In some embodiments, after sending a heartbeat request to the T-BOX device, the method further includes: if a heartbeat response sent by the T-BOX device is not received within a third preset time, repeating the step of sending a heartbeat request to the T-BOX device until a heartbeat response sent by the T-BOX device is received within the third preset time within a second preset number of repetitions.

[0013] In some embodiments, sending a network restart request to the T-BOX device through the network restart interface includes: when a user-triggered operation for performing a network restart action on the T-BOX device is monitored, issuing a confirmation prompt to the user; when a user-triggered confirmation operation for the confirmation prompt is monitored within a fourth preset time, sending a network restart request to the T-BOX device through the network restart interface.

[0014] According to one aspect of an embodiment of the present application, a network management device for a vehicle T-BOX device is provided, wherein the network management device is arranged in the T-BOX device, and the network management device comprises: a first receiving unit, which is used to receive a network restart request sent by a vehicle computer through a network restart interface; a judgment unit, which is used to judge whether the T-BOX device is in a remote upgrade state or a remote control state in response to the network restart request; a first sending unit, which is used to send a notification message of executing a network restart action to the vehicle computer if the T-BOX device is not in a remote upgrade state and is not in a remote control state, and trigger the execution of the network restart action after a first preset time.

[0015] According to one aspect of an embodiment of the present application, a network management device for a vehicle T-BOX device is provided, and the network management device is executed on a vehicle computer. The network management device includes: a second sending unit, which is used to send a network restart request to the T-BOX device through a network restart interface after maintaining a Socket connection with the vehicle computer, so as to trigger the T-BOX device to perform a network restart action; a second receiving unit, which is used to repeat the step of sending a network restart request to the T-BOX device through the network restart interface if no notification information of performing a network restart action sent by the T-BOX device is received within a second preset time, until the notification information of performing a network restart action sent by the T-BOX device is received within the second preset time within a first preset number of repetitions.

[0016] Compared with the prior art, the technical solution of the present application has the following significant beneficial effects: T-BOX is the Internet access channel in the car. The traditional T-BOX cannot interact directly with the user. When the T-BOX fails to connect to the Internet due to network environment problems, such as the 5G signal of a mobile phone falling to 2G and being unable to recover, or the network side directly sends a rejection code that prevents the T-BOX from accessing the Internet, according to the 3GPP protocol, certain specific situations require restarting the T-BOX to allow communication to be restored. If the user does not have a channel to restart the T-BOX, then the T-BOX can only be restarted under the timing or trigger conditions set inside the T-BOX, affecting the user experience. At the same time, the restart of the T-BOX is different from that of a mobile phone. The mobile phone is an independent individual, while the restart of the T-BOX must also take into account the environment of the entire vehicle and the communication with other ECUs. The present application effectively solves the problem of users not being able to restart the T-BOX channel by adding a network restart interface.

[0017] It should be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the present application. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] The above and other features and advantages of the present application will become more apparent by describing in detail exemplary embodiments thereof with reference to the attached drawings.

[0019] Figure 1 A schematic diagram showing the communication between a vehicle machine and a T-BOX according to an embodiment of the present application is shown;

[0020] Figure 2 A flowchart according to an embodiment of the present application is shown;

[0021] Figure 3 Another flow chart according to an embodiment of the present application is shown;

[0022] Figure 4 A simplified diagram of a network management device for a vehicle T-BOX device according to an embodiment of the present application is shown;

[0023] Figure 5 A simplified diagram of a network management device for another vehicle T-BOX device according to an embodiment of the present application is shown;

[0024] Figure 6 A flow chart of vehicle network status query according to an embodiment of the present application is shown;

[0025] Figure 7 The following is a timing diagram showing the interaction between the vehicle machine and the T-BOX according to an embodiment of the present application;

[0026] Figure 8 A T-BOX internal processing logic diagram according to an embodiment of the present application is shown;

[0027] Fig. 9 A schematic diagram of the structure of a computer system of an electronic device according to an embodiment of the present application is shown. DETAILED DESCRIPTION

[0028] Example embodiments will now be described more fully with reference to the accompanying drawings. However, example embodiments can be implemented in a variety of forms and should not be construed as limited to the examples set forth herein; rather, these embodiments are provided so that this application will be more comprehensive and complete and fully convey the concept of the example embodiments to those skilled in the art.

[0029] In addition, described feature, structure or characteristic can be combined in one or more embodiments in any suitable manner. In the following description, many specific details are provided to provide a full understanding of the embodiments of the present application. However, those skilled in the art will appreciate that the technical scheme of the present application can be put into practice without one or more of the specific details, or other methods, components, devices, steps, etc. can be adopted. In other cases, known methods, devices, realizations or operations are not shown or described in detail to avoid blurring the various aspects of the application.

[0030] The block diagrams shown in the accompanying drawings are merely functional entities and do not necessarily correspond to physically independent entities. That is, these functional entities may be implemented in software form, or in one or more hardware modules or integrated circuits, or in different networks and / or processor devices and / or microcontroller devices.

[0031] The flowcharts shown in the accompanying drawings are only exemplary and do not necessarily include all the contents and operations / steps, nor must they be executed in the order described. For example, some operations / steps can be decomposed, and some operations / steps can be combined or partially combined, so the actual execution order may change according to actual conditions.

[0032] According to some embodiments, Figure 1As shown, the schematic diagram 100 of the communication between the vehicle and T-BOX is shown in the figure. The T-BOX includes a vehicle management module, a modem management module and a modem. The vehicle interacts with the vehicle management module, the vehicle management module interacts with the modem management module, and the modem management module interacts with the modem. Among them, the network status information of the T-BOX is displayed through the vehicle (IVI). At the same time, in order to enhance the maintainability of the T-BOX, an interface for the vehicle to restart the T-BOX is added to the vehicle and T-BOX USB communication protocol. The T-BOX can be restarted when necessary (for example, the T-BOX shows that there is a signal but cannot access the Internet). Among them, the vehicle management module mainly receives information from the vehicle, processes and parses it, and calls other target sub-modules according to the parsing results. The modem management module manages information from the 5G\4G module and calls its related interfaces, such as dialing. The modem is a 5G\4G module, usually a Qualcomm module, a Huawei module, an MTK module, etc., which is integrated by the T-BOX manufacturer for its Internet access.

[0033] According to some embodiments, Figure 2 As shown, Figure 2 A flowchart of executing steps from the perspective of the T-BOX device side is presented. The present application provides a network management method for a vehicle T-BOX device, which is executed on the T-BOX device. The method includes: step 201, receiving a network restart request sent by a vehicle computer through a network restart interface; step 202, responding to the network restart request, determining whether the T-BOX device is in a remote upgrade state or a remote control state; step 203, if the T-BOX device is not in a remote upgrade state and is not in a remote control state, sending a notification message of executing a network restart action to the vehicle computer, and triggering the execution of the network restart action after a first preset time.

[0034] Based on the above embodiment, in step 201, the network restart interface is: an interface for the vehicle computer to restart the T-BOX added to the vehicle computer and T-BOX USB communication protocol. The network restart interface is an interface at the software level. The T-BOX device receives the network restart request sent by the vehicle computer through the network restart interface.

[0035] Furthermore, in step 202, after receiving the network restart request sent by the vehicle computer, the T-BOX device determines whether it is in a remote upgrade state or a remote control state, and then replies to the vehicle computer with a response to the network restart request.

[0036] Furthermore, in step 203, if the T-BOX device is not in the remote upgrade state and is not in the remote control state, a notification message for executing the network restart action is sent to the vehicle computer, and the execution of the network restart action is triggered after the first preset time. The first preset time can be set according to actual needs. In some embodiments, the first preset time is set to 3 seconds, that is, a notification message for executing the network restart action is sent to the vehicle computer, and the network is restarted after a delay of 3 seconds, so that the vehicle computer can receive a response to the request command sent by the T-BOX device, and then restart itself.

[0037] T-BOX is the Internet access channel in the car. The traditional T-BOX cannot interact directly with the user. When the T-BOX fails to connect to the Internet due to network environment problems, such as the 5G signal of a mobile phone drops to 2G and cannot be restored, or the network side directly sends a rejection code that prevents the T-BOX from accessing the Internet, according to the 3GPP protocol, certain specific situations require restarting the T-BOX to allow communication to be restored. If the user does not have a channel to restart the T-BOX, then it can only be restarted according to the timing or trigger conditions set inside the T-BOX, affecting the user experience. At the same time, the restart of the T-BOX is different from that of a mobile phone. The mobile phone is an independent individual, while the restart of the T-BOX must also take into account the environment of the entire vehicle and the communication with other ECUs. This application effectively solves the problem of users not restarting the T-BOX channel by adding a network restart interface.

[0038] According to some embodiments, before receiving a network restart request sent by the vehicle computer through the network restart interface, the method also includes: after establishing a Socket connection with the vehicle computer for the first time, receiving a handshake request sent by the vehicle computer, and sending a handshake response to the vehicle computer; after shaking hands with the vehicle computer, receiving a heartbeat request sent by the vehicle computer, and sending a heartbeat response to the vehicle computer to maintain the Socket connection with the vehicle computer.

[0039] Based on the above embodiments, Figure 7 As shown, Figure 7 The interaction sequence diagram between the vehicle computer and T-BOX is shown.

[0040] In step 701, first, after the vehicle computer is normally connected to the T-BOX via USB, a Socket connection can be established between the vehicle computer and the T-BOX.

[0041] In step 702, after the Socket is connected, the vehicle computer sends a handshake request to the T-BOX.

[0042] In step 703, T-BOX sends a handshake response to the vehicle computer.

[0043] In step 704, after the vehicle computer and the T-BOX complete the handshake, the vehicle computer sends a heartbeat request to the T-BOX, wherein the vehicle computer sends a heartbeat request every 3 seconds.

[0044] In step 705, after receiving the heartbeat request from the vehicle computer, the T-BOX sends a heartbeat response to the vehicle computer. If the vehicle computer does not receive a heartbeat response within 3 seconds, the vehicle computer resends a heartbeat request to the T-BOX. If the vehicle computer retries twice and does not receive a heartbeat response from the T-BOX both times, it prompts that the response failed. The reasons include that the T-BOX did not send a heartbeat response, or the T-BOX did not receive a heartbeat request, or the T-BOX sent a heartbeat response to the vehicle computer, but the vehicle computer did not receive a heartbeat response, etc.

[0045] In step 706, after the vehicle computer receives the heartbeat response, it sends a network restart request to the T-BOX. If the vehicle computer does not receive a restart response within 3 seconds after sending the network restart request to the T-BOX, it will resend the network restart request to the T-BOX. If the vehicle computer does not receive a restart response from the T-BOX after two retries, it will prompt that the response failed.

[0046] In step 707, the T-BOX sends a network restart response to the vehicle computer. The T-BOX sends a network restart response to the vehicle computer and controls itself to restart after a delay of 3 seconds to ensure that the vehicle computer can receive the restart response.

[0047] According to some embodiments, after maintaining the Socket connection with the vehicle computer, the method further includes: periodically acquiring network data information from the network; and reporting the network data information to the vehicle computer.

[0048] Based on the above embodiments, Figure 6 As shown, Figure 6 A flow chart for vehicle network status query is presented.

[0049] In step 601, after the vehicle computer is normally connected to the T-BOX via USB, a Socket connection can be established between the vehicle computer and the T-BOX.

[0050] In step 602, the vehicle computer and the T-BOX perform authentication to prevent connection to the wrong vehicle.

[0051] In step 603, the vehicle computer sends a handshake request to the T-BOX.

[0052] In step 604, the T-BOX sends a handshake response to the vehicle computer.

[0053] In step 605, please refer to Figure 1The vehicle management module in the T-BOX will periodically send a request to the modem management module to obtain network status information. After the modem management module obtains the network status information from the modem, it replies to the vehicle management module. After the vehicle management module receives the network status information sent by the modem management module, the vehicle management module reports the network status information to the vehicle to complete the network status query.

[0054] According to some embodiments, the method further includes: if the T-BOX device is in a remote upgrade state or in a remote control state, sending a notification message of network restart failure to the vehicle computer.

[0055] Based on the above embodiment, when the vehicle is in a remote upgrade state or a remote control state, restarting the network is not allowed, so as to stabilize the remote control and the remote installation package download and upgrade.

[0056] According to some other embodiments, from the perspective of the vehicle computer side, the present application provides a network management method for a vehicle T-BOX device, which is executed on the vehicle computer, and the method includes: step 301, after maintaining the Socket connection between the vehicle computer and the vehicle computer, sending a network restart request to the T-BOX device through the network restart interface to trigger the T-BOX device to perform a network restart action; step 302, if the notification information of executing the network restart action sent by the T-BOX device is not received within the second preset time, repeat the step of sending the network restart request to the T-BOX device through the network restart interface until the notification information of executing the network restart action sent by the T-BOX device is received within the second preset time within the first preset number of repetitions.

[0057] Based on the above embodiments, Figure 3 As shown, in step 301, after maintaining the Socket connection between the T-BOX device and the vehicle computer, the vehicle computer sends a network restart request to the T-BOX device through the network restart interface to trigger the T-BOX device to perform a network restart action. The vehicle computer notifies the T-BOX to restart through a USB command.

[0058] In step 302, if the notification information of executing the network restart action sent by the T-BOX device is not received within the second preset time, the step of sending the network restart request to the T-BOX device through the network restart interface is repeated until the notification information of executing the network restart action sent by the T-BOX device is received within the second preset time within the first preset number of repetitions. In some embodiments, the first preset number of repetitions is twice, and the second preset time is 3 seconds. If the vehicle computer does not receive a response from the T-BOX device within 3 seconds, the vehicle computer resends the notification, and the maximum number of retries does not exceed two times. If there is still no response after two times, it prompts that the request failed and ends the process. After receiving the restart command sent by the vehicle computer, the T-BOX first gives a response, and then delays for 3 seconds (so that the vehicle computer can receive the response to the request command) before restarting itself.

[0059] According to some embodiments, before maintaining the Socket connection with the vehicle computer, the method further includes: after establishing the Socket connection with the vehicle computer for the first time, sending a handshake request to the T-BOX device and receiving a handshake response sent by the T-BOX device; after handshaking with the T-BOX device, periodically sending a heartbeat request to the T-BOX device and receiving a heartbeat response sent by the T-BOX device to maintain the Socket connection with the vehicle computer.

[0060] Furthermore, after sending the heartbeat request to the T-BOX device, the method further includes: if no heartbeat response sent by the T-BOX device is received within a third preset time, repeating the step of sending the heartbeat request to the T-BOX device until a heartbeat response sent by the T-BOX device is received within the third preset time within a second preset number of repetitions.

[0061] Based on the above embodiments, Figure 7 As shown, Figure 7 The interaction sequence diagram between the vehicle computer and T-BOX is shown.

[0062] In step 701, first, after the vehicle computer is normally connected to the T-BOX via USB, a Socket connection can be established between the vehicle computer and the T-BOX.

[0063] In step 702, after the Socket is connected, the vehicle computer sends a handshake request to the T-BOX.

[0064] In step 703, T-BOX sends a handshake response to the vehicle computer.

[0065] In step 704, after the vehicle computer and the T-BOX complete the handshake, the vehicle computer sends a heartbeat request to the T-BOX, wherein the vehicle computer sends a heartbeat request every 3 seconds.

[0066] In step 705, after receiving the heartbeat request from the vehicle computer, the T-BOX sends a heartbeat response to the vehicle computer. In some embodiments, the third preset time is set to 3 seconds. If the vehicle computer does not receive a heartbeat response within 3 seconds, the vehicle computer resends the heartbeat request to the T-BOX. After the vehicle computer retries to the second preset number of repetitions and still does not receive a heartbeat response, it prompts that the response failed. In some embodiments, the second preset number of repetitions is two times. If the vehicle computer resends twice and does not receive a heartbeat response from T-BOX both times, it prompts that the response failed. The reasons include that the T-BOX did not send a heartbeat response, or the T-BOX did not receive a heartbeat request, or the T-BOX sent a heartbeat response to the vehicle computer, but the vehicle computer did not receive a heartbeat response, etc.

[0067] In step 706, after the vehicle computer receives the heartbeat response, it sends a network restart request to the T-BOX. If the vehicle computer does not receive a restart response within 3 seconds after sending the network restart request to the T-BOX, it will resend the network restart request to the T-BOX. If the vehicle computer does not receive a restart response from the T-BOX after two retries, it will prompt that the response failed.

[0068] In step 707, the T-BOX sends a network restart response to the vehicle computer. The T-BOX sends a network restart response to the vehicle computer and controls itself to restart after a delay of 3 seconds to ensure that the vehicle computer can receive the restart response.

[0069] According to some embodiments, sending a network restart request to the T-BOX device through the network restart interface includes: when an operation triggered by a user to perform a network restart action on the T-BOX device is monitored, issuing a confirmation prompt to the user; when a confirmation operation triggered by the user for the confirmation prompt is monitored within a fourth preset time, sending a network restart request to the T-BOX device through the network restart interface.

[0070] Based on the above embodiment, the fourth preset time can be set according to actual needs.

[0071] When the user chooses to restart the T-Box, a prompt box will pop up to ask the user to confirm in order to prevent misoperation. Only after the user confirms again, the car computer sends a restart command to the T-Box; when the USB connection handshake is reestablished, the T-Box can be prompted to restart. The restart completion only appears after the restart is completed by receiving the user's command. This prompt should not appear when the car computer or T-BOX automatically restarts during the vehicle ignition start phase (such as internal timed restart, etc.).

[0072] Sending a confirmation prompt to the user can prevent the user from pressing the wrong key. When the user presses the wrong key, the network restart action can be canceled through the confirmation prompt. When the user does not press the wrong key, the network restart can be confirmed again.

[0073] The following is a more detailed flowchart to introduce the internal processing logic of T-BOX. Figure 8 As shown, Figure 8 A T-BOX internal processing logic diagram 800 is shown.

[0074] After the vehicle is powered on;

[0075] Wait for the network restart interface to connect successfully;

[0076] Establish a Socket connection between the vehicle computer and T-BOX;

[0077] The handshake between the vehicle computer and T-BOX is successful;

[0078] Receive a restart request sent by the vehicle computer;

[0079] Determine whether it is in remote upgrade or remote control state. If it is in remote upgrade or remote control state, reply that the vehicle T-BOX cannot be refreshed;

[0080] If it is not in remote upgrade state and not in remote control state, it will reply that the vehicle computer is refreshing the network;

[0081] After replying that the vehicle computer is refreshing the network, it will send a T-BOX restart notification to the bus after a delay of 3 seconds. During the T-BOX restart period, the T-BOX cannot send a CAN signal with a valid time signal. Therefore, before restarting, the T-BOX will first send a T-BOX restart notification to the CAN bus to notify each controller on the bus not to record fault codes, etc., and during the T-BOX restart process, no self-check signal will be sent to avoid causing the self-check icon on the instrument to light up;

[0082] Restart T-BOX;

[0083] Restart completed;

[0084] Send T-BOX restart completion information to the bus, and each controller resumes the normal mode of interaction with T-BOX;

[0085] T-BOX determines whether this restart is a restart after receiving a user operation instruction. If it is a restart after receiving a user operation instruction, it sends a command to the vehicle computer to prompt the user that the T-BOX restart is completed. If it is not a restart after a user operation instruction, the process ends.

[0086] The following describes an embodiment of the device of the present application, which can be used to execute the network management method of the vehicle T-BOX device in the above embodiment of the present application. For details not disclosed in the embodiment of the device of the present application, please refer to the embodiment of the network management method of the vehicle T-BOX device in the above embodiment of the present application.

[0087] Figure 4A simplified diagram 400 of a network management device for a vehicle T-BOX device in an embodiment of the present application is shown, wherein the network management device is arranged in the T-BOX device, and comprises: a first receiving unit 401, which is used to receive a network restart request sent by a vehicle computer through a network restart interface; a judging unit 402, which is used to judge whether the T-BOX device is in a remote upgrade state or a remote control state in response to the network restart request; a first sending unit 403, which is used to send a notification message of executing a network restart action to the vehicle computer if the T-BOX device is not in a remote upgrade state and is not in a remote control state, and trigger the execution of the network restart action after a first preset time.

[0088] Based on the above embodiment, in the first receiving unit 401, the network restart interface is: an interface for the vehicle computer to restart the T-BOX added to the vehicle computer and the T-BOX USB communication protocol. The network restart interface is an interface at the software level. The T-BOX device receives the network restart request sent by the vehicle computer through the network restart interface.

[0089] Furthermore, in the determination unit 402, after receiving the network restart request sent by the vehicle computer, the T-BOX device determines whether it is in a remote upgrade state or a remote control state, and then replies a response to the network restart request to the vehicle computer.

[0090] Furthermore, in the first sending unit 403, if the T-BOX device is not in the remote upgrade state and is not in the remote control state, a notification message for executing the network restart action is sent to the vehicle computer, and the execution of the network restart action is triggered after the first preset time. The first preset time can be set according to actual needs. In some embodiments, the first preset time is set to 3 seconds, that is, a notification message for executing the network restart action is sent to the vehicle computer, and the network is restarted after a delay of 3 seconds, so that the vehicle computer can receive a response to the request command sent by the T-BOX device, and then restart itself.

[0091] T-BOX is the Internet access channel in the car. The traditional T-BOX cannot interact directly with the user. When the T-BOX fails to connect to the Internet due to network environment problems, such as the 5G signal of a mobile phone drops to 2G and cannot be restored, or the network side directly sends a rejection code that prevents the T-BOX from accessing the Internet, according to the 3GPP protocol, certain specific situations require restarting the T-BOX to allow communication to be restored. If the user does not have a channel to restart the T-BOX, then it can only be restarted according to the timing or trigger conditions set inside the T-BOX, affecting the user experience. At the same time, the restart of the T-BOX is different from that of a mobile phone. The mobile phone is an independent individual, while the restart of the T-BOX must also take into account the environment of the entire vehicle and the communication with other ECUs. This application effectively solves the problem of users not restarting the T-BOX channel by adding a network restart interface.

[0092] Figure 5 A simplified diagram 500 of a network management device for a vehicle T-BOX device in an embodiment of the present application is shown, wherein the network management device is executed on a vehicle computer, and comprises: a second sending unit 501, which is used to send a network restart request to the T-BOX device through a network restart interface after maintaining a Socket connection with the vehicle computer, so as to trigger the T-BOX device to perform a network restart action; a second receiving unit 502, which is used to repeat the step of sending a network restart request to the T-BOX device through the network restart interface if no notification information of performing a network restart action sent by the T-BOX device is received within a second preset time, until a notification information of performing a network restart action sent by the T-BOX device is received within a first preset number of repetitions and within the second preset time.

[0093] Based on the above embodiments, Figure 3 As shown, in the second sending unit 501, after maintaining the Socket connection with the vehicle computer, a network restart request is sent to the T-BOX device through the network restart interface to trigger the T-BOX device to perform a network restart action. The vehicle computer notifies the T-BOX to restart through a USB command.

[0094] In the second receiving unit 502, if the notification information of executing the network restart action sent by the T-BOX device is not received within the second preset time, the step of sending the network restart request to the T-BOX device through the network restart interface is repeated until the notification information of executing the network restart action sent by the T-BOX device is received within the second preset time within the first preset number of repetitions. In some embodiments, the first preset number of repetitions is twice, and the second preset time is 3 seconds. If no response is received within 3 seconds, the vehicle computer resends the notification, and the maximum number of retries does not exceed two times. If there is still no response after two times, it prompts that the request failed and ends the process. After receiving the restart command sent by the vehicle computer, the T-BOX first gives a response, and then delays for 3 seconds (so that the vehicle computer can receive the response to the request command) before restarting itself.

[0095] Fig. 9 A schematic diagram of the structure of a computer system suitable for implementing an electronic device of an embodiment of the present application is shown.

[0096] It should be noted that Fig. 9 The computer system 900 of the electronic device shown is only an example and should not bring any limitation to the functions and scope of use of the embodiments of the present application.

[0097] like Fig. 9As shown, the computer system 900 includes a central processing unit (CPU) 901, which can perform various appropriate actions and processes according to the program stored in the read-only memory (ROM) 902 or the program loaded from the storage part 908 to the random access memory (RAM) 903, such as executing the network management method of the vehicle T-BOX device described in the above embodiment. In RAM 903, various programs and data required for system operation are also stored. CPU 901, ROM 902 and RAM 903 are connected to each other through a bus 904. An input / output (I / O) interface 905 is also connected to the bus 904.

[0098] The following components are connected to the I / O interface 905: an input section 906 including a keyboard, a mouse, etc.; an output section 907 including a cathode ray tube (CRT), a liquid crystal display (LCD), etc., and a speaker, etc.; a storage section 908 including a hard disk, etc.; and a communication section 909 including a network interface card such as a LAN (Local Area Network) card, a modem, etc. The communication section 909 performs communication processing via a network such as the Internet. A drive 910 is also connected to the I / O interface 905 as needed. A removable medium 911, such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc., is installed on the drive 910 as needed so that a computer program read therefrom is installed into the storage section 908 as needed.

[0099] In particular, according to an embodiment of the present application, the process described above with reference to the flowchart can be implemented as a computer software program. For example, an embodiment of the present application includes a computer program product, which includes a computer program carried on a computer-readable medium, and the computer program includes a program code for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from a network through a communication section 909, and / or installed from a removable medium 911. When the computer program is executed by a central processing unit (CPU) 901, various functions defined in the system of the present application are executed.

[0100] It should be noted that the computer-readable medium shown in the embodiment of the present application may be a computer-readable signal medium or a computer-readable storage medium or any combination of the above two. The computer-readable storage medium may be, for example, - but not limited to - an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or device, or any combination of the above. More specific examples of computer-readable storage media may include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM), a flash memory, an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In the present application, a computer-readable storage medium may be any tangible medium containing or storing a program, which may be used by an instruction execution system, device or device or used in combination with it. In the present application, a computer-readable signal medium may include a data signal propagated in a baseband or as part of a carrier wave, wherein a computer-readable program code is carried. Such propagated data signals may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. Computer-readable signal media may also be any computer-readable medium other than computer-readable storage media, which may send, propagate, or transmit programs for use by or in conjunction with an instruction execution system, apparatus, or device. The program code contained on the computer-readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wired, etc., or any suitable combination of the above.

[0101] The flowchart and block diagram in the accompanying drawings illustrate the possible architecture, functions and operations of the system, method and computer program product according to various embodiments of the present application. Wherein, each box in the flowchart or block diagram can represent a module, a program segment, or a part of the code, and the above-mentioned module, program segment, or a part of the code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in a different order from the order marked in the accompanying drawings. For example, two boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram or flowchart, and the combination of boxes in the block diagram or flowchart can be implemented with a dedicated hardware-based system that performs a specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0102] The units involved in the embodiments described in this application may be implemented by software or hardware, and the units described may also be set in a processor. The names of these units do not, in some cases, constitute limitations on the units themselves.

[0103] As another aspect, the present application also provides a computer program product or a computer program, which includes computer instructions stored in a computer-readable storage medium. A processor of an electronic device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the electronic device executes the network management method of the vehicle T-BOX device described in the above embodiment.

[0104] As another aspect, the present application also provides a computer-readable medium, which may be included in the electronic device described in the above embodiment; or may exist independently without being assembled into the electronic device. The above computer-readable medium carries one or more programs, and when the above one or more programs are executed by an electronic device, the electronic device implements the network management method of the vehicle T-BOX device described in the above embodiment.

[0105] It should be noted that, although several modules or units of the equipment for action execution are mentioned in the above detailed description, this division is not mandatory. In fact, according to the embodiments of the present application, the features and functions of two or more modules or units described above can be embodied in one module or unit. On the contrary, the features and functions of one module or unit described above can be further divided into being embodied by multiple modules or units.

[0106] Through the description of the above implementation, it is easy for those skilled in the art to understand that the example implementation described here can be implemented by software, or by software combined with necessary hardware. Therefore, the technical solution according to the implementation of the present application can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (which can be a CD-ROM, a USB flash drive, a mobile hard disk, etc.) or on a network, including several instructions to enable a computing device (which can be a personal computer, a server, a touch terminal, or a network device, etc.) to execute the network management method of the vehicle T-BOX device described in the above embodiment.

[0107] Those skilled in the art will readily appreciate other embodiments of the present application after considering the specification and practicing the embodiments disclosed herein. The present application is intended to cover any variations, uses or adaptations of the present application, which follow the general principles of the present application and include common knowledge or customary technical means in the art that are not disclosed in the present application.

[0108] It should be understood that the present application is not limited to the precise structures that have been described above and shown in the drawings, and that various modifications and changes may be made without departing from the scope thereof. The scope of the present application is limited only by the appended claims.

Claims

1. A network management method for a vehicle T-BOX device, characterized in that: The method is executed on a T-BOX device, and comprises: A network restart request sent by a user through the vehicle computer is received through the network restart interface; In response to the network restart request, determining whether the T-BOX device is in a remote upgrade state or a remote control state; If the T-BOX device is not in a remote upgrade state and is not in a remote control state, a notification message for executing a network restart action is sent to the vehicle computer, and the execution of the network restart action is triggered after a first preset time; Before receiving a network restart request sent by the vehicle computer through the network restart interface, the method further includes: After establishing a Socket connection with the vehicle computer for the first time, receiving a handshake request sent by the vehicle computer, and sending a handshake response to the vehicle computer; After handshaking with the vehicle computer, a heartbeat request sent by the vehicle computer is received, and a heartbeat response is sent to the vehicle computer to maintain the Socket connection with the vehicle computer.

2. The method according to claim 1, characterized in that After maintaining the Socket connection with the vehicle computer, the method further includes: Periodically obtain network data information from the network; Report the network data information to the vehicle computer.

3. The method according to claim 1, characterized in that The method further comprises: If the T-BOX device is in a remote upgrade state or a remote control state, a notification message of network restart failure is sent to the vehicle computer.

4. A network management method for a vehicle T-BOX device, characterized in that: The method is executed on a vehicle computer, and the method includes: After maintaining the Socket connection with the vehicle computer, the user sends a network restart request to the T-BOX device through the network restart interface to trigger the T-BOX device to perform a network restart action; If the notification information of executing the network restart action sent by the T-BOX device is not received within the second preset time, the step of sending the network restart request to the T-BOX device through the network restart interface is repeatedly executed until the notification information of executing the network restart action sent by the T-BOX device is received within the second preset time within the first preset number of repetitions; Before maintaining the Socket connection with the vehicle computer, the method further includes: After establishing a socket connection with the vehicle computer for the first time, send a handshake request to the T-BOX device and receive a handshake response sent by the T-BOX device; After handshaking with the T-BOX device, a heartbeat request is periodically sent to the T-BOX device, and a heartbeat response sent by the T-BOX device is received to maintain the Socket connection with the vehicle computer.

5. The method according to claim 4, characterized in that After sending the heartbeat request to the T-BOX device, the method further includes: If a heartbeat response sent by the T-BOX device is not received within the third preset time, the step of sending a heartbeat request to the T-BOX device is repeated until a heartbeat response sent by the T-BOX device is received within the third preset time within a second preset number of repetitions.

6. The method according to claim 4, characterized in that The sending of a network restart request to the T-BOX device through the network restart interface includes: When a user-triggered network restart operation is detected for the T-BOX device, a confirmation prompt is sent to the user; When a confirmation operation for the confirmation prompt triggered by the user is monitored within a fourth preset time, a network restart request is sent to the T-BOX device through the network restart interface.

7. A network management device for a vehicle T-BOX device, characterized in that: The network management device is arranged on the T-BOX device, and the network management device comprises: The first receiving unit is used to receive a handshake request sent by the vehicle computer after the Socket connection is first established with the vehicle computer, and send a handshake response to the vehicle computer; after handshaking with the vehicle computer, receive a heartbeat request sent by the vehicle computer, and send a heartbeat response to the vehicle computer to maintain the Socket connection with the vehicle computer, and receive a network restart request sent by the user through the vehicle computer through the network restart interface; a determination unit, configured to determine, in response to the network restart request, whether the T-BOX device is in a remote upgrade state or a remote control state; The first sending unit is used to send notification information of executing a network restart action to the vehicle computer if the T-BOX device is not in a remote upgrade state and is not in a remote control state, and trigger the execution of the network restart action after a first preset time.

8. A network management device for a vehicle T-BOX device, characterized in that: The network management device is executed on the vehicle computer, and the network management device includes: The second sending unit is used to receive a handshake request sent by the vehicle computer after the Socket connection is first established with the vehicle computer, and send a handshake response to the vehicle computer; after the handshake with the vehicle computer, receive a heartbeat request sent by the vehicle computer, and send a heartbeat response to the vehicle computer to maintain the Socket connection with the vehicle computer; after the Socket connection with the vehicle computer is maintained, the user sends a network restart request to the T-BOX device through the network restart interface to trigger the T-BOX device to perform a network restart action; The second receiving unit is used to repeatedly execute the step of sending a network restart request to the T-BOX device through the network restart interface if the notification information of executing the network restart action sent by the T-BOX device is not received within the second preset time, until the notification information of executing the network restart action sent by the T-BOX device is received within the second preset time within the first preset number of repetitions.

Images