Account management method, Internet of Vehicles system and storage medium

Abstract

The embodiment of the invention provides an account management method, an Internet of Vehicles system and a storage medium. The method comprises the steps that in response to an account setting request, a vehicle-mounted communication terminal obtains first account information from a vehicle networking platform, and the account setting request is triggered when the vehicle-mounted communication terminal is offline; the vehicle-mounted communication terminal sends a first connection request to the message-oriented middleware, wherein the first connection request carries the first account information; after the first connection request is received, if the first account information is valid, the message middleware establishes communication connection with the vehicle-mounted communication terminal; after communication connection is established between the message-oriented middleware and the vehicle-mounted communication terminal, the vehicle-mounted communication terminal stores the first account information, and in the using process of the vehicle-mounted communication terminal, the message-oriented middleware is connected through the first account information. According to the invention, the time consumption of interaction with the cloud can be reduced, and the starting efficiency and overall reliability of the Internet of Vehicles communication link are improved.

Description

Technical Field

[0001] This application relates to the field of vehicle networking technology, and in particular to an account management method, a vehicle networking system, and a storage medium. Background Technology

[0002] With the rapid development of vehicle-to-everything (V2X) technology, the telematics box (Tbox), as the core hub for interaction between vehicles and external networks, undertakes key functions such as vehicle data collection, remote control, and wireless upgrades. To achieve stable communication between the vehicle and the V2X platform, the Tbox needs to establish a reliable connection to support real-time data uploads and accurate command delivery from the platform.

[0003] Currently, to address the challenges of concurrent access from a large number of in-vehicle communication terminals and real-time message distribution, vehicle-to-everything (V2X) systems employ message middleware as the communication hub. In-vehicle communication terminals establish connections with the message middleware, publishing vehicle data to designated topics and simultaneously subscribing to command topics issued by the V2X platform, thereby achieving efficient, asynchronous, and decoupled bidirectional communication between vehicles and the V2X platform.

[0004] However, under this architecture, account authentication of the vehicle communication terminal becomes a key link in ensuring communication security. If account information is leaked or not updated in time, it will lead to security risks such as data leakage and command tampering, affecting vehicle driving safety and platform data integrity. Summary of the Invention

[0005] This application provides an account management method, a vehicle networking system, and a storage medium. Throughout the entire lifecycle of the vehicle communication terminal, whenever it needs to establish a connection with the message middleware, it can directly read the locally stored first account information for identity authentication and connection establishment. This avoids the cumbersome process of dynamically obtaining account information from the cloud before each connection, reduces the time spent interacting with the cloud, and improves the startup efficiency and overall reliability of the vehicle networking communication link.

[0006] In a first aspect, embodiments of this application provide an account management method applied to a vehicle-to-everything (V2X) system. The V2X system includes an in-vehicle communication terminal, a message middleware, and a V2X platform. The method includes: responding to an account setting request, the in-vehicle communication terminal obtaining first account information from the V2X platform; the account setting request is triggered when the in-vehicle communication terminal goes offline; the in-vehicle communication terminal sending a first connection request to the message middleware, the first connection request carrying the first account information; after receiving the first connection request, if the first account information is valid, the message middleware establishing a communication connection with the in-vehicle communication terminal; after the message middleware establishing a communication connection with the in-vehicle communication terminal, the in-vehicle communication terminal storing the first account information, wherein, during the use of the in-vehicle communication terminal, the message middleware is connected through the first account information.

[0007] In one possible implementation, the process of the vehicle-mounted communication terminal obtaining first account information from the vehicle-to-everything (V2X) platform in response to the account setting request includes: the vehicle-mounted communication terminal sending a first account acquisition request to the V2X platform in response to the account setting request, the first account acquisition request carrying device information of the vehicle-mounted communication terminal, the device information including a device identifier and a network identifier; the V2X platform verifying the device information in response to the first account acquisition request; if the device information verification is successful, the V2X platform generating first account information; and the V2X platform sending the first account information to the vehicle-mounted communication terminal.

[0008] In one possible implementation, after the vehicle-mounted communication terminal stores the first account information, the method further includes: when the vehicle-mounted communication terminal is powered on, the vehicle-mounted communication terminal reads the first account information; the vehicle-mounted communication terminal sends a second connection request to a message middleware, the second connection request carrying the first account information; after receiving the first connection request, if the first account information is valid, the message middleware establishes a communication connection with the vehicle-mounted communication terminal; after the message middleware establishes a communication connection with the vehicle-mounted communication terminal, the vehicle-mounted communication terminal sends vehicle data to the message middleware.

[0009] In one possible implementation, after the vehicle communication terminal sends vehicle data to the message middleware, the method further includes: if the vehicle data indicates that the vehicle communication terminal is in an abnormal state, or if a disable command is received for the vehicle communication terminal, the vehicle network platform marks the first account information as invalid.

[0010] In one possible implementation, after the vehicle networking platform marks the first account information as invalid, the method further includes: the vehicle communication terminal sending a third connection request to the message middleware, the third connection request carrying the first account information; upon receiving the third connection request, the message middleware determines that the first account information is invalid and refuses to connect to the vehicle communication terminal.

[0011] In one possible implementation, after the vehicle-to-everything (V2X) platform marks the first account information as invalid, the method further includes: if a de-disabling command is received for the vehicle-mounted communication terminal, the V2X platform generates second account information and authorization information corresponding to the second account information. The second account information is used for the vehicle-mounted communication terminal to connect to the message middleware, and the second account information is different from the first account information; the V2X platform sends reset information to the vehicle-mounted communication terminal, the reset information including the authorization information; in response to the reset information, the vehicle-mounted communication terminal obtains the authorization information and sends a second account acquisition request to the V2X platform, the second account acquisition request carrying the authorization information; in response to the second account acquisition request, the V2X platform obtains the authorization information; if the authorization information is valid, the V2X platform obtains the second account information based on the authorization information; the V2X platform sends the second account information to the vehicle-mounted communication terminal.

[0012] In one possible implementation, the method further includes: if the authorization information is invalid, the vehicle network platform sends a prompt message to the vehicle communication terminal, the prompt message indicating that the vehicle communication terminal reset failed.

[0013] Secondly, embodiments of this application provide a vehicle networking system, including:

[0014] The vehicle-mounted communication terminal is used to respond to an account setting request and obtain the first account information from the vehicle network platform. The account setting request is triggered when the vehicle-mounted communication terminal is offline.

[0015] The vehicle-mounted communication terminal is also used to send a first connection request to the message middleware, the first connection request carrying first account information;

[0016] The message middleware is used to establish a communication connection with the vehicle communication terminal after receiving the first connection request, if the first account information is valid.

[0017] The vehicle-mounted communication terminal is also used to store first account information after the message middleware establishes a communication connection with the vehicle-mounted communication terminal. During the use of the vehicle-mounted communication terminal, the message middleware is connected through the first account information.

[0018] Thirdly, embodiments of this application provide a vehicle networking system, including: a memory and a processor;

[0019] The memory stores the instructions that the computer executes;

[0020] The processor executes computer execution instructions stored in memory, causing the processor to perform the first aspect and / or various possible implementations of the first aspect as described above.

[0021] Fourthly, embodiments of this application provide a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, are used to implement the first aspect and / or various possible implementations of the first aspect.

[0022] Fifthly, embodiments of this application provide a computer program product, including a computer program that, when executed by a processor, implements the first aspect and / or various possible implementations of the first aspect.

[0023] In this embodiment, when the vehicle-mounted communication terminal is taken offline, in response to an account setting request, the vehicle-mounted communication terminal dynamically obtains the first account information from the vehicle network platform. After obtaining the first account information, the vehicle-mounted communication terminal sends a first connection request carrying the first account information to the message middleware to verify the validity of the first account information. After the first account information is verified, the vehicle-mounted communication terminal stores the first account information. Thus, throughout the entire lifecycle of the vehicle-mounted communication terminal, whenever it needs to establish a connection with the message middleware (e.g., each time the vehicle is powered on), it can directly read the locally stored first account information for identity authentication and connection establishment, avoiding the cumbersome process of dynamically obtaining account information from the cloud before each connection, reducing the time spent interacting with the cloud, and improving the startup efficiency and overall reliability of the vehicle network communication link. Furthermore, verifying the validity of the first account information after it is dynamically generated enhances the security of account usage. Attached Figure Description

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

[0025] Figure 1 This is a schematic diagram illustrating an application scenario of an account management method according to an embodiment of this application;

[0026] Figure 2 A flowchart illustrating an account management method provided in an embodiment of this application;

[0027] Figure 3 A flowchart illustrating another account management method provided in this application embodiment;

[0028] Figure 4 A flowchart illustrating another account management method provided in this application embodiment;

[0029] Figure 5 A flowchart illustrating another account management method provided in this application embodiment;

[0030] Figure 6This is a schematic diagram of the structure of a vehicle networking system provided in an embodiment of this application;

[0031] Figure 7 This is a schematic diagram of another vehicle networking system provided in an embodiment of this application. Detailed Implementation

[0032] The embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numbers in different drawings represent the same or similar elements. The embodiments described below do not represent all embodiments consistent with this application. They are merely examples of systems and methods consistent with some aspects of this application as detailed in the claims.

[0033] It should be noted that the brief descriptions of terms in this application are only for the convenience of understanding the embodiments described below, and are not intended to limit the embodiments of this application. Unless otherwise stated, these terms should be understood in their ordinary and common meaning.

[0034] The terms "first," "second," "third," etc., used in the specification, claims, and accompanying drawings of this application are used to distinguish similar or related objects or entities, and do not necessarily imply a specific order or sequence, unless otherwise specified. It should be understood that such terms are interchangeable where appropriate.

[0035] The terms “comprising” and “having”, and any variations thereof, are intended to cover but not exclude inclusion, for example, a product or device that includes a range of components is not necessarily limited to all of the components that are clearly listed, but may include other components that are not clearly listed or that are inherent to such product or device.

[0036] The term "module" refers to any known or subsequently developed hardware, software, firmware, artificial intelligence, fuzzy logic, or combination of hardware and / or software code that is capable of performing the functions associated with that element.

[0037] With the rapid development of vehicle-to-everything (V2X) technology, the in-vehicle communication terminal, as the core hub for interaction between the vehicle and the external network, undertakes key functions such as vehicle data collection, remote control, and over-the-air (OTA) upgrades. To achieve stable communication between the vehicle and the V2X platform, the in-vehicle communication terminal needs to establish a reliable connection with the platform to support real-time data uploads and accurate command delivery.

[0038] Currently, to address the challenges of concurrent access from a large number of in-vehicle communication terminals and real-time message distribution, vehicle-to-everything (V2X) systems employ message middleware as the communication hub. In-vehicle communication terminals establish connections with the message middleware, publishing vehicle data to designated topics and simultaneously subscribing to command topics issued by the V2X platform, thereby achieving efficient, asynchronous, and decoupled bidirectional communication between vehicles and the V2X platform.

[0039] However, under this architecture, account authentication of the vehicle communication terminal becomes a key link in ensuring communication security. If account information is leaked or not updated in time, it will lead to security risks such as data leakage and command tampering, affecting vehicle driving safety and platform data integrity.

[0040] In view of this, this application provides an account management method. When the vehicle-mounted communication terminal is taken offline, in response to an account setting request, the vehicle-mounted communication terminal dynamically obtains first account information from the vehicle network platform. After obtaining the first account information, the vehicle-mounted communication terminal sends a first connection request carrying the first account information to the message middleware to verify the validity of the first account information. After the first account information is verified, the vehicle-mounted communication terminal stores the first account information. In this way, throughout the entire subsequent lifecycle of the vehicle-mounted communication terminal, whenever it needs to establish a connection with the message middleware (e.g., each time the vehicle is powered on), it can directly read the locally stored first account information for identity authentication and connection establishment, avoiding the cumbersome process of dynamically obtaining account information from the cloud before each connection, reducing the time spent interacting with the cloud, and improving the startup efficiency and overall reliability of the vehicle network communication link. Furthermore, verifying the validity of the first account information after it is dynamically generated can improve the security of account use.

[0041] Before introducing the account management method provided in the embodiments of this application, the application scenarios of the account management method will be explained first.

[0042] Figure 1 This is a schematic diagram illustrating an application scenario of an account management method according to an embodiment of this application.

[0043] The embodiments of this application are applied to vehicle networking systems. For example... Figure 1 As shown, the vehicle-to-everything (V2X) system includes an in-vehicle communication terminal (Tbox) 10, a message middleware 20, a V2X platform 30, and terminal devices 40, all mounted in the vehicle. The in-vehicle communication terminal 10 uploads vehicle data to the V2X platform 30 in real time via the message middleware 20. The V2X platform 30 receives remote control commands from the terminal devices 40 and sends these commands to the designated in-vehicle communication terminal 10 via the message middleware 20.

[0044] In some scenarios, after the vehicle communication terminal 10 uploads vehicle data to the vehicle network platform 30 in real time, the vehicle network platform 30 can perform real-time status monitoring, fault warning, and driving behavior analysis of the vehicle.

[0045] In other scenarios, in response to a user's operation on a terminal device (such as a mobile phone) 40, the terminal device 40 sends a remote control command to the vehicle network platform 30. After receiving the remote control command, the vehicle network platform 30 sends a remote control command to the designated vehicle communication terminal 10 through the message middleware 20 to control the vehicle to execute the remote control command.

[0046] For example, when a user checks the door lock status on a vehicle control application on their mobile phone, the phone sends a viewing command to the vehicle networking platform 30. After receiving the viewing command, the vehicle networking platform 30 sends a viewing command to the designated vehicle communication terminal 10 through the message middleware 20. After receiving the viewing command, the vehicle communication terminal 10 obtains the door lock status and then uploads the door lock status to the vehicle networking platform 30 through the message middleware 20. The vehicle networking platform 30 then sends the door lock status to the mobile phone to display the door lock status on the mobile phone.

[0047] In this embodiment, when the vehicle-mounted communication terminal 10 connects to the message middleware 20, identity authentication and login are required via account information. Specifically, when the vehicle-mounted communication terminal 10 is offline (i.e., installed in front of the vehicle), it obtains account information from the vehicle networking platform 30. This account information is used to log in to the message middleware 20. After obtaining the account information, the vehicle-mounted communication terminal 10 uses this information to send a connection request to the message middleware 20. Upon receiving the connection request, the message middleware 20 verifies the account information. If the verification is successful, the message middleware 20 establishes a communication connection with the vehicle-mounted communication terminal 10 and sends a connection success notification to the vehicle-mounted communication terminal 10. After receiving the connection success notification, the vehicle-mounted communication terminal 10 stores the account information. Subsequently, during normal vehicle use, the vehicle-mounted communication terminal 10 can use this account information to communicate with the message middleware 20 for data uploading and command reception.

[0048] Furthermore, when the vehicle networking platform 30 detects an anomaly in the vehicle communication terminal 10, it disables the account information to prevent the vehicle communication terminal 10 from using that account information to communicate with the message middleware 20. After the security risk in the vehicle communication terminal 10 is resolved, the vehicle networking platform 30 configures a new account signal for the vehicle communication terminal 10, allowing the vehicle communication terminal 10 to use the new account information to communicate with the message middleware 20, thus restoring the communication function.

[0049] The account management method provided in this application embodiment will be described in detail below with reference to the accompanying drawings and application scenarios.

[0050] Figure 2 This is a flowchart illustrating an account management method provided in an embodiment of this application. Figure 2 As shown, this account management method may include the following steps:

[0051] S201, In response to the account setting request, the vehicle communication terminal obtains the first account information from the vehicle network platform. The account setting request is triggered when the vehicle communication terminal goes offline.

[0052] Among them, the vehicle communication terminal (i.e., Tbox) is a networked device deployed in the vehicle. It is used to collect and report vehicle data, such as vehicle speed, engine status, GPS location, fault codes, etc., to cloud servers (such as vehicle networking platforms), and can receive and execute remote control commands from cloud servers (such as remote unlocking commands, air conditioning start commands, etc.).

[0053] The account setup request triggers the in-vehicle communication terminal to perform the initial account information configuration operation, that is, it triggers the in-vehicle communication terminal to obtain account information from the vehicle network platform, i.e., the first account information. This first account information serves as the authentication credential for the in-vehicle communication terminal to connect to the message middleware, and is used for identity verification when the in-vehicle communication terminal establishes a communication connection with the message middleware.

[0054] It should be noted that the account setup request is triggered during the preparation phase before the vehicle communication terminal is put into use, such as when the vehicle communication terminal rolls off the production line. This means that the vehicle communication terminal has completed its manufacturing, assembly, and testing processes on the production line, and is ready to be installed and used in vehicles after it rolls off the production line.

[0055] In some examples, account setup requests can be initiated via an external configuration device connected to the vehicle communication terminal. For instance, during the production of the vehicle communication terminal, in response to a user's setup operation on an electronic device (i.e., a PC) connected to the vehicle communication terminal, the PC sends an account setup request to the vehicle communication terminal to trigger the terminal to perform its initial account information configuration operation.

[0056] In some embodiments, during the production or initialization phase of the in-vehicle communication terminal, the device information of the in-vehicle communication terminal is pre-registered on the vehicle-to-everything (V2X) platform. This device information includes a device identifier and a network identifier. The in-vehicle communication terminal sends its device identifier and network identifier to the V2X platform via a PC. The V2X platform binds and stores the device identifier and network identifier. Optionally, the V2X platform can also associate the device information of the in-vehicle communication terminal with the vehicle identifier (such as the Vehicle Identification Number, VIN) of the vehicle to which the in-vehicle communication terminal belongs. In this way, in subsequent steps, the V2X platform can verify the device information of the in-vehicle communication terminal based on the pre-stored data.

[0057] Among them, the device identifier refers to the International Mobile Equipment Identifier (IMEI), which is used to uniquely identify the vehicle-mounted communication terminal.

[0058] A network identifier refers to the identity identifier of the communication module built into a vehicle-mounted communication terminal. For example, the network identifier is the Integrated Circuit Card Identifier (ICCID) of the Subscriber Identity Module (SIM card) built into the vehicle-mounted communication terminal, used to uniquely identify the SIM card of the vehicle-mounted communication terminal.

[0059] In some examples, upon receiving an account setup request (i.e., when the vehicle communication terminal is first started or initialized), the vehicle communication terminal checks whether account information is stored locally. If no account information is stored, it retrieves the first account information from the vehicle networking platform.

[0060] For example, S201 may include the following steps:

[0061] S2011, in response to the account setting request, the vehicle communication terminal obtains its own device identifier and network identifier, and sends a first account acquisition request to the vehicle network platform. The first account acquisition request carries the device information of the vehicle communication terminal, including the aforementioned device identifier and network identifier.

[0062] Among them, the first account acquisition request is used to request account information from the vehicle networking platform, that is, the first account information used to connect the message middleware.

[0063] The account information can include the account (i.e., AppKey) and the secret key (AppSecret). That is, the first account information includes account 1 and secret key 1.

[0064] Optionally, the vehicle-mounted communication terminal can call the device account service of the vehicle networking platform through a dedicated network access point (i.e., Access Point Name, APN channel) that is isolated from the public network to send a first account acquisition request to the vehicle networking platform.

[0065] S2012, in response to the first account acquisition request, the vehicle networking platform verifies the device information of the vehicle communication terminal.

[0066] For example, in response to the first account acquisition request, the vehicle network platform obtains the device identifier and network identifier of the vehicle communication terminal, and queries whether there is a binding relationship between the device identifier (IMEI) and the network identifier (ICCID). If there is a binding relationship between the device identifier (IMEI) and the network identifier (ICCID), the device information verification is successful; otherwise, the device information verification fails.

[0067] S2013 If the device information verification of the vehicle communication terminal is successful, the vehicle networking platform generates the first account information.

[0068] Once the device information verification of the vehicle communication terminal is successful, the vehicle networking platform generates account 1 and key 1, i.e., the first account information, for the vehicle communication terminal.

[0069] S2014, the vehicle networking platform sends the first account information to the vehicle communication terminal.

[0070] For example, taking the vehicle communication terminal as Tbox device 1, with IMEI _001 and ICCID _001 for the SIM card built into Tbox device 1, when Tbox device 1 is first started after production, it checks whether account information is stored locally. If not, it sends IMEI _001 and ICCID _001 to the vehicle networking platform through the APN _01 channel. The vehicle networking platform verifies whether a binding relationship exists between IMEI _001 and ICCID _001. If a binding relationship exists, it generates and sends AppKey _001 and AppSecret _001 to Tbox device 1.

[0071] In this embodiment, when the vehicle-mounted communication terminal is offline, a first account acquisition request is sent to the vehicle network platform. The vehicle network platform verifies the device information of the vehicle-mounted communication terminal. If the device information verification is successful, account information for connecting to the message middleware is generated and sent to the vehicle-mounted communication terminal. This pre-bound information verification ensures the legality and uniqueness of the generated account information, improving the security of connecting to the message middleware. Furthermore, by obtaining the account information for connecting to the message middleware from the vehicle network platform when the vehicle-mounted communication terminal is offline, the terminal can directly connect to the message middleware using this account information during subsequent use, avoiding the need to dynamically obtain account information for each connection, thus improving response speed and reducing security risks.

[0072] S202, the vehicle-mounted communication terminal sends a first connection request to the message middleware, and the first connection request carries the first account information.

[0073] Among them, the message middleware serves as the message relay server in the vehicle networking system. For example, the EMQX (Erlang / Enterprise Message Queue eXchange) message server can be used.

[0074] The first connection request is used to request the establishment of a communication connection with the message middleware in order to report data and issue commands.

[0075] S203: After receiving the first connection request, if the first account information is valid, the message middleware establishes a communication connection with the vehicle communication terminal.

[0076] Upon receiving the first connection request, the message middleware verifies the validity of the first account information (i.e., account 1 and key 1) carried by the request. For example, it verifies whether the first account information is legally issued and whether it is disabled. If the first account information is valid (i.e., verification passes), the message middleware establishes a communication connection with the vehicle communication terminal and sends a connection success confirmation notification to the vehicle communication terminal. If the first account information is invalid (i.e., verification fails), the connection request is rejected.

[0077] In some examples, the message middleware can call the device account service provided by the vehicle networking platform through a secure communication protocol (such as HTTPS), and the device account service can verify the validity of the first account information.

[0078] S204, after the message middleware establishes a communication connection with the vehicle communication terminal, the vehicle communication terminal stores the first account information, wherein the message middleware is connected through the first account information during the use of the vehicle communication terminal.

[0079] Specifically, upon receiving a confirmation notification from the message middleware that the connection has been successfully established, i.e., after the message middleware and the vehicle communication terminal have successfully established a communication connection, the vehicle communication terminal stores the first account information.

[0080] Optionally, the vehicle-mounted communication terminal may use encryption to store the first account information.

[0081] In this embodiment, when the vehicle-mounted communication terminal is decommissioned, it dynamically obtains account information from the vehicle networking platform. Therefore, throughout the entire lifecycle of the vehicle-mounted communication terminal, whenever it needs to establish a connection with the message middleware (e.g., each time the vehicle is powered on), it can directly read the locally stored first account information for authentication and connection establishment without requesting it from the vehicle networking platform again. This way, by securely obtaining and locally storing connection credentials once during the vehicle-mounted communication terminal (e.g., T-Box) decommissioning phase, direct reuse during long-term use is possible. This avoids the cumbersome process of dynamically obtaining account information from the cloud before each connection, as is present in existing technologies. It reduces the number of network interactions and connection establishment delays, improving the startup efficiency and overall reliability of the vehicle networking communication link. Furthermore, the generation and distribution of account information are strictly bound to pre-registered device identifiers (e.g., IMEI, ICCID), ensuring the legality and uniqueness of the credentials.

[0082] After storing the first account information in the vehicle communication terminal, the vehicle communication terminal can connect to the message middleware through the first account information during long-term use.

[0083] In some embodiments, the process of the vehicle-mounted communication terminal connecting to the message middleware through the first account information may include the following steps:

[0084] S301, when the vehicle communication terminal is powered on, the vehicle communication terminal reads the first account information from the local memory.

[0085] S302, the vehicle-mounted communication terminal sends a second connection request to the message middleware, and the second connection request carries the first account information.

[0086] The second connection request is used to request the establishment of a communication connection with the message middleware in order to report data and issue commands.

[0087] S303: Upon receiving the second connection request, if the first account information is valid, the message middleware establishes a communication connection with the vehicle communication terminal.

[0088] Upon receiving the second connection request, the message middleware verifies the validity of the first account information (i.e., account 1 and key 1) carried by the request. For example, it verifies whether the first account information is legally issued and whether it is disabled. If the first account information is valid (i.e., verification passes), the message middleware establishes a communication connection with the vehicle communication terminal and sends a connection success confirmation notification to the vehicle communication terminal. If the first account information is invalid (i.e., verification fails), the connection request is rejected.

[0089] S304 After the message middleware establishes a communication connection with the vehicle communication terminal, the vehicle communication terminal sends vehicle data to the message middleware.

[0090] After a successful communication connection is established, the in-vehicle communication terminal can report vehicle data (such as speed, status, and location information) to the message middleware and receive control commands forwarded by the message middleware. This avoids the lengthy process of interacting with the cloud service to obtain temporary credentials every time the vehicle powers on and connects, reducing connection establishment time to a single local read and network verification, significantly improving the startup speed of the vehicle-to-everything (V2X) service and the user experience. It also reduces unnecessary and frequent network interactions between the in-vehicle terminal and the V2X platform, lowers the request processing pressure on the cloud server, and allows the terminal to attempt to establish a connection using existing credentials even when network conditions are temporarily poor, enhancing the system's robustness. Furthermore, the security attributes (such as the binding relationship with the device) of the credentials used for each connection are established in the initial security environment. Subsequent reuse processes continuously reuse and strengthen this established security trust chain, avoiding the transient risks that dynamically generated credentials might introduce.

[0091] In some embodiments, during the long-term use of the vehicle communication terminal, the vehicle network platform can detect whether the vehicle communication terminal is in an abnormal state. If the vehicle communication terminal is in an abnormal state, the first account information is marked as invalid, that is, the account information of the vehicle communication terminal is disabled (or frozen).

[0092] In some examples, the process of disabling account information for an in-vehicle communication terminal may include: if vehicle data reported by the in-vehicle communication terminal indicates that the in-vehicle communication terminal is in an abnormal state, or if a disabling command is received for the in-vehicle communication terminal, the vehicle network platform marks the first account information as invalid. The disabling command for the in-vehicle communication terminal may be a command triggered by the user through the vehicle network platform.

[0093] In other words, during the long-term use of the in-vehicle communication terminal, the vehicle network platform can determine whether the in-vehicle communication terminal is in an abnormal state based on the vehicle data reported by the in-vehicle communication terminal.

[0094] For example, vehicle data may include identity and connection data. If the identity and connection data indicate that the vehicle communication terminal has a connection anomaly, then the vehicle communication terminal is determined to be in an abnormal state. A connection anomaly in the vehicle communication terminal may include at least one of the following: connection requests originating from different IP addresses with vastly different geographical locations within a very short period; frequent authentication failures far exceeding the normal device error rate; incorrect communication message format, abnormal heartbeat intervals, or attempts to publish a large number of illegal topics.

[0095] For example, vehicle data may include vehicle status data. If the vehicle status data indicates that the vehicle to which the in-vehicle communication terminal belongs is abnormal, then the in-vehicle communication terminal is determined to be in an abnormal state. An abnormal vehicle state may include at least one of the following: GPS location information showing an impossible rapid transition; a significant mismatch between the reported vehicle speed and engine speed, gear position, etc.; the door status showing as open while the vehicle is locked, causing a logical conflict; a sudden change in communication traffic patterns (such as a surge in data when the vehicle is stationary, or a sharp decrease in traffic while driving); or the reported device identifier (such as IMEI, ICCID) or firmware version not matching the platform registration information.

[0096] In some embodiments, after the vehicle networking platform marks the first account information as invalid, the method further includes: the vehicle communication terminal sending a third connection request to the message middleware, the third connection request carrying the first account information; upon receiving the third connection request, the message middleware determines that the first account information is invalid and refuses to connect to the vehicle communication terminal.

[0097] In other words, during the subsequent use of the vehicle-mounted communication terminal, the first account information continues to be used to connect to the message middleware. At this time, after receiving the connection request (i.e., the third connection request) sent by the vehicle-mounted communication terminal, the message middleware verifies the validity of the first account information carried in the request. Because the first account information is marked as invalid, the verification fails, and the message middleware refuses to establish a communication connection with the vehicle-mounted communication terminal.

[0098] In this embodiment, during normal use of the vehicle-mounted communication terminal, it is possible to detect whether the terminal is in an abnormal state. If an abnormal state is detected, the first account information used by the terminal to connect to the message middleware is disabled. Thus, when the terminal subsequently uses the first account information to connect to the message middleware, the middleware verifies the validity of the first account information. If the first account information is invalid, the connection to the terminal is refused, improving account security and reducing the risk of data leakage.

[0099] In some embodiments, after the vehicle network platform marks the first account information as invalid, and after determining that there is no security risk in the vehicle communication terminal, the account information of the vehicle communication terminal can be reconfigured so that the vehicle communication terminal can communicate normally with the message middleware, thereby uploading data and receiving the issued instructions.

[0100] In some examples, the process of reconfiguring account information for a vehicle communication terminal may include the following steps:

[0101] S401, if a command to de-disable the vehicle communication terminal is received, the vehicle networking platform generates second account information and authorization information corresponding to the second account information.

[0102] The de-disable command is used to trigger the vehicle-to-everything (V2X) platform to remotely configure the account settings for the in-vehicle communication terminal. For example, the de-disable command can be triggered by the user through the V2X platform after the in-vehicle communication terminal has returned to normal operation.

[0103] The second account information is used for the vehicle-mounted communication terminal to connect to the message middleware. The second account information differs from the first account information. Of course, the second account information may include account 2 and key 2.

[0104] The authorization information corresponds one-to-one with the second account information. For example, the authorization information can be a device authorization code, which is a one-time, short-term temporary token. For example, the device authorization code can only be used once, and its effective usage time is a preset duration, such as 5 minutes.

[0105] S402, the vehicle networking platform sends a reset message to the vehicle communication terminal, which includes authorization information.

[0106] The reset information can be sent via SMS. For example, the vehicle-to-everything (V2X) platform can invoke the communication platform to send an SMS to the SIM card of the in-vehicle communication terminal, with the SMS carrying authorization information.

[0107] S403, in response to the reset information, the vehicle communication terminal obtains the authorization information and sends a second account acquisition request to the vehicle network platform, the second account acquisition request carrying the authorization information.

[0108] When the in-vehicle communication terminal is disabled (i.e., in a dormant state), the vehicle control unit (VCU) receives a reset message, parses it, and obtains authorization information. After obtaining the authorization information, the VCU wakes up the in-vehicle communication terminal, which then sends a request to the vehicle network platform to obtain a second account.

[0109] Optionally, the vehicle-mounted communication terminal can call the device account service of the vehicle networking platform through a dedicated network access point isolated from the public network to send a second account acquisition request to the vehicle networking platform.

[0110] S404, in response to the second account acquisition request, the vehicle networking platform obtains authorization information.

[0111] S405 If the authorization information is valid, the vehicle networking platform will obtain the second account information based on the authorization information.

[0112] In some examples, after obtaining the second account information based on the authorization information, the vehicle-to-everything (V2X) platform invalidates the authorization information.

[0113] S406, the vehicle networking platform sends the second account information to the vehicle communication terminal.

[0114] S407 If the authorization information is invalid, the vehicle networking platform sends a prompt message to the vehicle communication terminal. The prompt message indicates that the vehicle communication terminal reset failed.

[0115] For example, in response to a request to obtain a second account, the vehicle-to-everything (V2X) platform obtains authorization information and verifies it. If the authorization information is valid for a preset period and an account corresponding to the authorization information exists, the V2X platform obtains the second account information based on the authorization information and sends the second account information to the vehicle communication terminal; otherwise, it sends a prompt message, such as an error code, to the vehicle communication terminal.

[0116] In some embodiments, after the vehicle communication terminal receives the second account information, the vehicle communication terminal can use the second account information to connect to the message middleware to verify the validity of the second account information. If the second account information is successfully verified, the second account information is stored.

[0117] It should be noted that the verification and storage process for the second account information can be found in the verification and storage process for the first account information in S202 to S204 above, and will not be repeated here.

[0118] In this embodiment, after determining that there are no security risks in the vehicle-mounted communication terminal, the vehicle network platform can dynamically generate new second account information and corresponding authorization information, and send reset information to the vehicle-mounted communication terminal. Upon receiving the reset information, the vehicle-mounted communication terminal can obtain the new second account information from the vehicle network platform using the authorization information in the reset information. Subsequently, the vehicle-mounted communication terminal uses the new second account information to connect to the message middleware, completes connection verification, and then encrypts and stores the information, thereby restoring the communication function. Thus, after determining that there are no security risks in the vehicle-mounted communication terminal, the account information can be reconfigured remotely, enabling the vehicle-mounted communication terminal to connect to the message middleware normally for data uploading and receiving / sending commands. Furthermore, by verifying the authorization information, the security of account information usage can be ensured, improving data security.

[0119] The following is a specific example illustrating the account management method provided in the embodiments of this application.

[0120] Figure 3 This is a flowchart illustrating an account management method provided in an embodiment of this application. Figure 3 As shown, the process of setting up account information in Tbox in this account management method includes the following steps:

[0121] S501, when the vehicle communication terminal is taken offline, in response to the setup operation, the PC sends an account setup request to the Tbox. S502, in response to the account setup request, the Tbox obtains its own device information, including the device identifier and network identifier.

[0122] S503, Tbox sends a first account acquisition request to the vehicle networking platform, and the first account acquisition request carries the device information of Tbox.

[0123] S504, in response to the first account acquisition request, the vehicle networking platform verifies the device information.

[0124] S505, If the device information verification is successful, the vehicle networking platform generates the first account information. S506, The vehicle networking platform sends the first account information to the Tbox.

[0125] S507, Tbox sends a first connection request to the message middleware, which carries the first account information.

[0126] S508: After receiving the first connection request, the message middleware obtains the first account information and verifies the validity of the first account information.

[0127] S509, if the first account information is valid, the message middleware establishes a communication connection with Tbox.

[0128] S510, the message middleware sends a confirmation notification of successful connection to Tbox.

[0129] Upon receiving a confirmation notification of a successful connection, the S511 Tbox stores the first account information.

[0130] Figure 4 This is a flowchart illustrating an account management method provided in an embodiment of this application. Figure 4 As shown, the process of disabling Tbox in this account management method includes the following steps:

[0131] In response to the disabling command for Tbox, the vehicle networking platform marked the first account information as invalid.

[0132] S602, Tbox sends a third connection request to the message middleware, which carries the first account information.

[0133] S603, in response to the third connection request, the message middleware obtains the first account information.

[0134] S604, the message middleware's verification of the first account information through the vehicle networking platform is invalid.

[0135] S605, the message middleware refused to connect to the Tbox.

[0136] Figure 5 This is a flowchart illustrating an account management method provided in an embodiment of this application. Figure 5 As shown, the process of unblocking Tbox in this account management method includes the following steps:

[0137] In response to the command to unblock the Tbox, the vehicle networking platform generates second account information and corresponding authorization information.

[0138] S702, the vehicle networking platform sends a reset message to the Tbox, which includes authorization information.

[0139] S703, in response to a reset message, the Tbox obtains authorization information through the vehicle control unit.

[0140] S704, Tbox sends a second account acquisition request to the vehicle networking platform, and the second account acquisition request carries authorization information.

[0141] S705, in response to the second account acquisition request, the vehicle networking platform obtains authorization information.

[0142] S706: If the authorization information is valid, the vehicle networking platform will obtain the second account information based on the authorization information.

[0143] S707, the vehicle networking platform sends the second account information to the Tbox.

[0144] S708: If the authorization information is invalid, the vehicle networking platform sends a prompt message to the Tbox. This prompt message indicates that the Tbox reset has failed.

[0145] S709, Tbox sends a fourth connection request to the message middleware, which carries the second account information.

[0146] After receiving the fourth connection request, the message middleware in S710 obtains the second account information and verifies its validity.

[0147] S711, if the second account information is valid, the message middleware establishes a communication connection with Tbox.

[0148] S712, the message middleware sends a confirmation notification of successful connection to Tbox.

[0149] Upon receiving a confirmation notification of a successful connection, the S713 Tbox stores the second account information.

[0150] In this embodiment, the security and operational efficiency of account management for vehicle communication terminals are improved by dynamically generating account information, remotely disabling, and re-disabling. A closed-loop management system is formed from production line initialization to equipment disabling and updates, ensuring that account information remains under control at all times, thus adapting to the complex operational needs of the Internet of Vehicles (IoV) scenario.

[0151] This application also provides a vehicle networking system. For example... Figure 6 As shown, the vehicle-to-everything (V2X) system 800 includes an in-vehicle communication terminal 801, a message middleware 802, and a V2X platform 803. The in-vehicle communication terminal 801 is used to obtain first account information from the V2X platform 803 in response to an account setting request, which is triggered when the in-vehicle communication terminal 801 goes offline. The in-vehicle communication terminal 801 is also used to send a first connection request to the message middleware 802, the first connection request carrying the first account information. The message middleware 802, upon receiving the first connection request, establishes a communication connection with the in-vehicle communication terminal 801 if the first account information is valid. The in-vehicle communication terminal 801 is also used to store the first account information after the message middleware 802 establishes a communication connection with it, wherein the in-vehicle communication terminal 801 connects to the message middleware 802 through the first account information during its use.

[0152] The vehicle networking system provided in this embodiment can execute the methods provided in the above method embodiments. Its implementation principle and technical effect are similar, and will not be described in detail here.

[0153] Figure 7 This is a schematic diagram of the vehicle networking system provided in this application. Figure 7 As shown, the vehicle networking system 90 provided in this embodiment includes at least one processor 901 and a memory 902. Optionally, the electronic device 90 further includes a communication component 903. The processor 901, memory 902, and communication component 903 are connected via a bus 904.

[0154] In a specific implementation, at least one processor 901 executes computer execution instructions stored in memory 902, causing at least one processor 901 to perform the above-described method.

[0155] The specific implementation process of processor 901 can be found in the above method embodiments, and its implementation principle and technical effect are similar. It will not be repeated here.

[0156] In the above embodiments, it should be understood that the processor can be a Central Processing Unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), etc. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the method disclosed in this invention can be directly implemented by a hardware processor, or implemented by a combination of hardware and software modules within the processor.

[0157] The memory may include random access memory (RAM) and may also include non-volatile memory (NVM), such as at least one disk storage device.

[0158] The bus can be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus, etc. Buses can be categorized as address buses, data buses, control buses, etc. For ease of illustration, the buses shown in the accompanying drawings are not limited to a single bus or a single type of bus.

[0159] This application also provides a computer program product, including a computer program that, when executed by a processor, implements the above-described method.

[0160] This application also provides a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, implement the above-described method.

[0161] The aforementioned readable storage medium can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic storage, flash memory, magnetic disk, or optical disk. The readable storage medium can be any available medium accessible to a general-purpose or special-purpose computer.

[0162] An exemplary readable storage medium is coupled to a processor, enabling the processor to read information from and write information to the readable storage medium. Of course, the readable storage medium can also be a component of the processor. The processor and the readable storage medium can reside in an Application Specific Integrated Circuit (ASIC). Alternatively, the processor and the readable storage medium can exist as discrete components in the device.

[0163] The division of units is merely a logical functional division; in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be indirect coupling or communication connection through some interfaces, devices, or units, and may be electrical, mechanical, or other forms.

[0164] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0165] In addition, the functional units in the various embodiments of the present invention 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.

[0166] If a function 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, the technical solution of this invention, or the part that contributes to the prior art, or a part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods of the various embodiments of this invention. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0167] Those skilled in the art will understand that all or part of the steps of the above-described method embodiments can be implemented by hardware related to program instructions. The aforementioned program can be stored in a computer-readable storage medium. When executed, the program performs the steps of the above-described method embodiments; and the aforementioned storage medium includes various media capable of storing program code, such as ROM, RAM, magnetic disks, or optical disks.

[0168] Finally, it should be noted that other embodiments of the invention will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This invention is intended to cover any variations, uses, or adaptations of the invention that follow the general principles of the invention and include common knowledge or customary techniques in the art not disclosed herein, and is not limited to the precise structures described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of the invention is limited only by the appended claims.

Claims

1. An account management method, characterized by, The method is applied to a vehicle Internet system, the vehicle Internet system comprising a vehicle-mounted communication terminal, a message middleware and a vehicle Internet platform, and the method comprises the following steps: In response to an account setting request, the vehicle-mounted communication terminal acquires first account information from the vehicle Internet platform, the account setting request being triggered when the vehicle-mounted communication terminal is offline; The vehicle-mounted communication terminal sends a first connection request to the message middleware, the first connection request carrying the first account information; After receiving the first connection request, if the first account information is valid, the message middleware establishes a communication connection with the vehicle-mounted communication terminal; After the message middleware establishes a communication connection with the vehicle-mounted communication terminal, the vehicle-mounted communication terminal stores the first account information, wherein, in the process of using the vehicle-mounted communication terminal, the message middleware is connected through the first account information.

2. The method of claim 1, wherein, The method further comprises the following steps after the vehicle-mounted communication terminal stores the first account information: When the vehicle-mounted communication terminal is powered on, the vehicle-mounted communication terminal reads the first account information; The vehicle-mounted communication terminal sends a second connection request to the message middleware, the second connection request carrying the first account information; After receiving the first connection request, if the first account information is valid, the message middleware establishes a communication connection with the vehicle-mounted communication terminal; After the message middleware establishes a communication connection with the vehicle-mounted communication terminal, the vehicle-mounted communication terminal sends vehicle data to the message middleware.

3. The method of claim 1, wherein, The method further comprises the following steps after the vehicle-mounted communication terminal sends vehicle data to the message middleware: If the vehicle data indicates that the vehicle-mounted communication terminal is in an abnormal state, or if a disable instruction for the vehicle-mounted communication terminal is received, the vehicle Internet platform marks the first account information as invalid. The method further comprises the following steps after the vehicle Internet platform marks the first account information as invalid: The vehicle-mounted communication terminal sends a third connection request to the message middleware, the third connection request carrying the first account information; After receiving the third connection request, the message middleware determines that the first account information is invalid and refuses to connect the vehicle-mounted communication terminal.

4. The method of claim 3, wherein, The method further comprises the following steps after the vehicle Internet platform marks the first account information as invalid: ​ 5. The method of claim 4, wherein, ​ ​ ​ 6. The method of claim 4, wherein, ​ If a disabling instruction for the vehicle-mounted communication terminal is received, the vehicle networking platform generates second account information and authorization information corresponding to the second account information, the second account information being used for the vehicle-mounted communication terminal to connect to the message middleware, the second account information being different from the first account information; The vehicle networking platform sends reset information to the vehicle-mounted communication terminal, the reset information including the authorization information; In response to the reset information, the vehicle-mounted communication terminal acquires the authorization information and sends a second account acquisition request to the vehicle networking platform, the second account acquisition request carrying the authorization information; In response to the second account acquisition request, the vehicle networking platform acquires the authorization information; If the authorization information is valid, the vehicle networking platform acquires the second account information according to the authorization information; The vehicle networking platform sends the second account information to the vehicle-mounted communication terminal.

7. The method of claim 6, wherein, The method further comprises: If the authorization information is invalid, the vehicle networking platform sends prompt information to the vehicle-mounted communication terminal, the prompt information being used for the vehicle-mounted communication terminal to reset failure.

8. An Internet of Vehicles system, characterized in that, Comprise: The vehicle-mounted communication terminal is used for acquiring first account information from the vehicle networking platform in response to an account setting request, the account setting request being triggered when the vehicle-mounted communication terminal is offline. The vehicle-mounted communication terminal is further used for sending a first connection request to the message middleware, the first connection request carrying the first account information. The message middleware is used for establishing a communication connection with the vehicle-mounted communication terminal if the first account information is valid after receiving the first connection request. The vehicle-mounted communication terminal is further used for storing the first account information after the message middleware and the vehicle-mounted communication terminal establish a communication connection, wherein the message middleware is connected through the first account information in the use process of the vehicle-mounted communication terminal.

9. An Internet of Vehicles system, characterized in that, Comprise: Memory, processor; The memory stores computer execution instructions; The processor executes the computer execution instructions stored in the memory, so that the processor executes the method of any one of claims 1-7.

10. A computer-readable storage medium, characterized in that, The computer readable storage medium stores computer execution instructions, and the computer execution instructions are executed by the processor to implement the method of any one of claims 1-7.

Images