A networking method and apparatus of a vehicle, a vehicle, a program product and a storage medium

Abstract

The present disclosure provides a networking method and device of a vehicle, the vehicle, a program product and a storage medium, and relates to the technical field of vehicles. The method comprises: in the case that the vehicle meets a vehicle networking activation condition, determining a target network operator in response to a network identifier of a target application program; wherein the vehicle networking activation condition is that the vehicle is first connected to a network after being produced, or the vehicle is transported from a first region to a second region; the target application program is downloaded in an actual location of the vehicle and is an application program for opening a vehicle networking function for the vehicle; the network identifier is used to represent a distribution source channel of the target application program; and the vehicle is controlled to be connected to a network based on network configuration information of the target network operator. The target network operator is directly determined through the network identifier of the target application program, and the timeliness and accuracy of network connection are improved.

Description

Technical Field

[0001] This disclosure relates to the field of vehicle technology, specifically to the field of vehicle networking technology, and more particularly to a vehicle networking method, device, vehicle, software product, and storage medium. Background Technology

[0002] With the development of vehicle intelligence and connectivity, vehicles with vehicle-to-everything (V2X) capabilities are typically equipped with in-vehicle communication devices (Telematics Box, TBOX), enabling data interaction through built-in in-vehicle communication cards. Currently, there are two main types of in-vehicle communication cards: traditional physical Subscriber Identity Module (SIM card) cards, which are bound to a single operator and whose network service is provided by that operator; and embedded general-purpose integrated circuit cards (embedded Subscriber Identity Module, ESIM card), which can remotely switch operator configurations via over-the-air (OTA) technology to adapt to network requirements in different scenarios.

[0003] However, as automakers expand their overseas operations, vehicles need to continuously report data during export transportation, port handling, and final delivery, and the mainstream operators vary from country to country. Using traditional physical SIM cards would result in high roaming fees in cross-border scenarios; and existing eSIM solutions are not yet perfect in terms of operator switching strategies. Summary of the Invention

[0004] This disclosure provides a method, apparatus, vehicle, software product, and storage medium for connecting a vehicle to the network, enabling more accurate and timely switching of network operators.

[0005] In a first aspect, this application provides a vehicle networking method applied to a Telematics Service Provider (TSP), comprising: determining a target network operator in response to a network identifier of a target application when the vehicle meets the vehicle networking activation conditions; wherein the vehicle networking activation conditions are: the vehicle's first network connection after production, or the vehicle being transported from a first region to a second region; the target application is an application downloaded at the vehicle's actual location to enable vehicle networking functionality for the vehicle; the network identifier is used to characterize the distribution source channel of the target application; and controlling the vehicle's network connectivity based on the network configuration information of the target network operator.

[0006] The vehicle networking method provided in this application can identify the network identifier of the target application that enables vehicle networking function for the vehicle when it first connects to the network after the vehicle is produced, or when the vehicle is transported from a first region to a second region. Based on the network identifier, the target network operator corresponding to the current area of ​​the vehicle can be quickly and accurately identified. Then, based on the network configuration information of the target network operator, the vehicle's networking control is performed, realizing automatic network configuration adaptation and efficient operator switching. This simplifies user operation, improves activation success rate, and significantly improves the accuracy and timeliness of network connection.

[0007] In some possible implementations, determining the target network operator in response to the network identifier of the target application includes: searching for the target network operator corresponding to the network identifier from a first preset correspondence; in the first preset correspondence, there is a one-to-one correspondence between the network identifier and the network operator.

[0008] Based on this implementation method, by using the first preset correspondence, the corresponding target network operator can be found directly and quickly when the network identifier is determined. This effectively reduces the vehicle's reliance on roaming services and the roaming fees in cross-regional scenarios, while significantly improving the localization adaptation and service quality of network connections.

[0009] In some possible implementations, the vehicle's network connectivity is controlled based on the network configuration information of the target network operator, including: sending the network configuration information to a software development kit (SDK) configured in the vehicle, so that the SDK sends the network configuration information to the vehicle communication device TBOX; the TBOX is used to dial up and connect to the network based on the network configuration information, so that the vehicle can access the network of the target network operator.

[0010] Based on this implementation method, sending network configuration information to the SDK configured in the vehicle enables the SDK to send the network configuration information to the vehicle communication device TBOX, thereby allowing the TBOX to dial up and connect to the network based on the network configuration information, so that the vehicle can access the network of the target network operator, improving the timeliness and accuracy of configuration information transmission, as well as the stability of the vehicle's network connection.

[0011] In some possible implementations, the TBOX writes the network configuration information into the embedded general-purpose integrated circuit card (ESIM) when the network configuration information dial-up connection is successful; the network configuration information in the ESIM is used for reconnection after a network interruption.

[0012] Based on this implementation method, TBOX can write network configuration information into the embedded universal integrated circuit card ESIM when the network configuration information dials up and connects to the network, thereby achieving local persistent storage of network configuration. This makes it easy for the vehicle to automatically read the configuration information stored in the ESIM to complete the reconnection after a power failure or network interruption and recovery, without requiring the user to repeat the activation operation, thus improving the convenience of network reconnection.

[0013] In some possible implementations, the method further includes: upon receiving a network failure signal returned by the TBOX via the SDK, searching for a replacement network operator for the target network operator from a second preset correspondence; the second preset correspondence is used to characterize the correspondence between the network identifier, the network operator corresponding to the network identifier, and the replacement network operator corresponding to the network operator; the TBOX sends a network failure signal if the number of network configuration information dial-up connection failures is greater than or equal to a preset number; and performs network connection control on the vehicle based on the network configuration information of the replacement network operator.

[0014] Based on this implementation method, a second preset correspondence is set up, which can quickly find and replace the network operator to control the vehicle's network connection in the event of a network connection failure. This effectively avoids activation interruption caused by the unavailability of a single operator's network, and ensures the success rate of vehicle network connection and the timely readiness of vehicle networking services.

[0015] In some possible implementations, network configuration information includes: a data plan profile and three-code data; the profile includes at least: Access Point Name (APN), Internet Protocol (IP), and Domain Name System (DNS); the three-code data includes at least: Integrated Circuit Card Identifier (ICCID), International Mobile Equipment Identity (IMEI), and International Mobile Subscriber Identity (IMSI).

[0016] Based on this implementation method, the network configuration information includes both Profile (including APN, IP, DNS) and three-code data (including ICCID, IMEI, IMSI), enabling TBOX to complete the access channel parameter setting and operator network identity registration in one go after obtaining the complete configuration, without the need for step-by-step acquisition or multiple interactions, effectively simplifying the activation process and improving the completeness and execution efficiency of network configuration.

[0017] Secondly, this application provides a vehicle networking device applied to a remote service provider (TSP), comprising: a determining module and a control module; the determining module is used to determine a target network operator in response to the network identifier of a target application when the vehicle meets the vehicle networking activation conditions; wherein, the vehicle networking activation conditions are: the vehicle's first network connection after production, or the vehicle being transported from a first region to a second region; the target application is an application downloaded at the vehicle's actual location to enable vehicle networking functionality for the vehicle; the network identifier is used to characterize the distribution source channel of the target application; the control module is used to control the vehicle's network connection based on the network configuration information of the target network operator.

[0018] In some possible implementations, the determining module is specifically used to find the target network operator corresponding to the network identifier from the first preset correspondence; in the first preset correspondence, the network identifier and the network operator are in a one-to-one correspondence.

[0019] In some possible implementations, the control module is specifically used to send network configuration information to a software development kit (SDK) configured in the vehicle, so that the SDK sends the network configuration information to the vehicle communication device TBOX; the TBOX is used to dial up and connect to the network based on the network configuration information, so that the vehicle can access the network of the target network operator.

[0020] In some possible implementations, the TBOX writes the network configuration information into the embedded general-purpose integrated circuit card (ESIM) when the network configuration information dial-up connection is successful; the network configuration information in the ESIM is used for reconnection after a network interruption.

[0021] In some possible implementations, the control module is further configured to, upon receiving a network failure signal returned by the TBOX via the SDK, search for a replacement network operator from a second preset correspondence; the second preset correspondence is used to characterize the correspondence between the network identifier, the network operator corresponding to the network identifier, and the replacement network operator corresponding to the network operator; the TBOX sends a network failure signal if the number of network configuration information dial-up connection failures is greater than or equal to a preset number; and controls the vehicle's network connection based on the network configuration information of the replacement network operator.

[0022] In some possible implementations, network configuration information includes: a data plan profile and three-code data; the profile includes at least: an access point name (APN), a network address (IP), and a domain name system (DNS); the three-code data includes at least: an integrated circuit card identifier (ICCID), an international mobile device identifier (IMEI), and an international mobile subscriber identifier (IMSI).

[0023] Thirdly, this application provides a control device, including: a memory and a processor; the memory and the processor are coupled; the memory is used to store a computer program; the processor executes the computer program to implement the vehicle networking method of any of the above embodiments.

[0024] Fourthly, this application provides a computer-readable storage medium storing computer program instructions that, when executed by a processor, implement the vehicle networking method of any of the above embodiments.

[0025] Fifthly, this application provides a computer program product including computer program instructions that, when executed by a processor, implement the vehicle networking method of any of the above embodiments.

[0026] Sixthly, this application provides a vehicle including the control device of any of the preceding embodiments; or the computer-readable storage medium of any of the preceding embodiments; or the computer program product of any of the preceding embodiments. Attached Figure Description

[0027] To more clearly illustrate the technical solutions in this disclosure, the accompanying drawings used in some embodiments of this disclosure will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of this disclosure. For those skilled in the art, other drawings can be obtained based on these drawings.

[0028] Figure 1 A schematic diagram of the architecture of a vehicle networking system provided in an embodiment of this disclosure; Figure 2 A flowchart of a vehicle networking method provided in this disclosure embodiment Figure 1 ; Figure 3 A flowchart of a vehicle networking method provided in this disclosure embodiment Figure 2 ; Figure 4 A schematic diagram of the structure of a vehicle networking device provided in some embodiments of this disclosure; Figure 5 This is a schematic diagram of the structure of a control device provided in some embodiments of this disclosure. Detailed Implementation

[0029] The technical solutions of this disclosure will now be clearly and completely described with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this disclosure, and not all embodiments. Based on the embodiments of this disclosure, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this disclosure.

[0030] It should be noted that, in this disclosure, the terms "exemplary" or "for example" are used to indicate examples, illustrations, or descriptions. Any embodiment or design described as "exemplary" or "for example" in this disclosure should not be construed as being more preferred or advantageous than other embodiments or designs. Specifically, the use of terms such as "exemplary" or "for example" is intended to present the relevant concepts in a concrete manner.

[0031] Hereinafter, the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include one or more of that feature.

[0032] In the description of this disclosure, unless otherwise stated, " / " means "or," for example, A / B can mean A or B. "And / or" in this document is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, and B alone. Furthermore, "at least one" means one or more, and "more than one" means two or more.

[0033] As mentioned in the background section, in existing vehicle communication solutions, although traditional physical SIM cards can achieve closed-loop communication throughout the entire process, high international roaming fees are incurred when vehicles report data domestically before going overseas. Some car companies that have introduced ESIM cards still rely on manual monitoring and manual switching of operators, which requires a lot of manpower and training costs. Moreover, each step requires manual intervention, making it impossible to achieve timely and intelligent automatic switching, resulting in switching delays and inaccurate matching. This makes it difficult to meet the dual requirements of communication cost and connection efficiency for large-scale operation of vehicles going overseas.

[0034] To address the aforementioned technical issues, this disclosure provides a vehicle networking method. The idea is as follows: when a vehicle meets the vehicle networking activation conditions, the target network operator is determined by a network identifier that reflects the distribution channel of the target application. Then, the vehicle's network connection is controlled by the network configuration information of the target network operator, achieving the effect of automatically matching the optimal network operator according to the application distribution channel, and realizing the precise configuration of communication resources and automatic adaptation of networking strategies.

[0035] The vehicle networking system provided in the embodiments of this disclosure will now be described in detail with reference to the accompanying drawings.

[0036] See Figure 1 This is a schematic diagram of the architecture of a vehicle networking system provided in an embodiment of this disclosure. Figure 1As shown, the vehicle's networking system 100 includes a remote service provider 110 and a vehicle 120.

[0037] Among them, the remote service provider 110 and the vehicle 120 are connected by communication.

[0038] In an exemplary embodiment, the vehicle 120 includes: a target application 121, a vehicle-side software development kit 122, an in-vehicle communication device 123, and an embedded general-purpose integrated circuit card 124.

[0039] Specifically, the target application (APP) communicates with the remote service provider (TSP); the remote service provider (TSP) communicates with the vehicle communication device (TBOX) through the vehicle-side software development kit (SDK); and the vehicle communication device (TBOX) communicates with the embedded universal integrated circuit card (ESIM).

[0040] The APP sends a network connection request to the TSP; the TSP responds to the network connection request, and if the vehicle meets the conditions for vehicle network activation, it responds to the network identifier of the target application, determines the target network operator, and, based on the network configuration information of the target network operator, jointly controls the vehicle's network connection through SDK, TBOX and ESIM.

[0041] The APP is an application downloaded at the vehicle's actual location to enable the vehicle's Internet of Vehicles (IoV) functionality.

[0042] TSP is used to provide vehicle-to-everything (V2X) related platform services and operational support to vehicles and users.

[0043] SDK is a software development kit integrated into the vehicle system to provide the interface calls, protocol encapsulation, and data processing capabilities required for vehicle-to-everything (V2X) communication.

[0044] TBOX is an in-vehicle telematics terminal installed in vehicles to enable wireless communication and data interaction between the vehicle and a cloud platform.

[0045] ESIM is an embedded user identity module embedded in the T-BOX, used to replace the traditional pluggable physical SIM card, enabling remote downloading, storage, and switching of operator configuration files.

[0046] It is understood that the application scenarios of the embodiments of this disclosure are not limited. The system architecture and business scenarios described in the embodiments of this disclosure are for the purpose of more clearly illustrating the technical solutions of the embodiments of this disclosure, and do not constitute a limitation on the technical solutions provided by the embodiments of this disclosure. As those skilled in the art will know, with the evolution of network architecture and the emergence of new business scenarios, the technical solutions provided by the embodiments of this disclosure are also applicable to similar technical problems.

[0047] The following is a detailed description of the vehicle networking method provided in the embodiments of this disclosure.

[0048] This disclosure provides a method for connecting vehicles to the network, such as... Figure 2 As shown, the method includes the following steps: S201. If the vehicle meets the conditions for vehicle-to-everything (V2X) activation, determine the target network operator in response to the network identifier of the target application.

[0049] The conditions for activating the vehicle-to-everything (V2X) network are: the vehicle being connected to the network for the first time after it is produced, or the vehicle being transported from the first region to the second region.

[0050] The Vehicle Remote Service Provider (TSP) platform receives a vehicle connectivity registration request from a mobile app. This app is a locally adapted version downloaded by the user, and the user initiates the registration and activation process through this app after purchasing the vehicle.

[0051] As a feasible approach, after a vehicle is completed and rolls off the production line, the TBOX uses the factory-preset default network configuration to complete the initial dial-up network connection and reports the vehicle's basic data to the TSP platform, thereby completing the initial activation preparation.

[0052] As another feasible approach, after a vehicle arrives in a second region, due to the change in network environment, a re-registration process needs to be triggered to complete the switch from the operator's network in the first region to the operator's network in the second region, so as to ensure that the vehicle-to-everything (V2X) function is available normally at the destination.

[0053] It should be noted that during the cross-regional transportation and inactive phase of the vehicle's journey from the first region to the second region, the TBOX terminal defaults to using Profile A, specified by the network operator in the first region, for network configuration. At this time, the three-digit data corresponding to the ESIM card (typically including ICCID, IMEI, and IMSI identification information) is defined as seed data, used to identify the initial identity and home network of the communication module. The TBOX relies on this configuration to complete dialing and network connection and report basic vehicle data, providing the necessary prerequisites for formal activation and network switching upon arrival in the second region.

[0054] In an exemplary embodiment, the target application is an application downloaded at the actual location of the vehicle to enable vehicle-to-everything (V2X) functionality.

[0055] It should be understood that before the vehicle connects to the internet, since the vehicle's infotainment system itself does not have network access capabilities, users must download the target application to their mobile devices via other networks (such as Wi-Fi or mobile data). This app is the only channel for initiating registration and activation; the TSP platform can only configure network parameters for the vehicle after receiving a request from the app. Therefore, downloading the target application in advance is a necessary preparatory step before the vehicle achieves its first internet connection.

[0056] In an exemplary embodiment, the network identifier is used to characterize the distribution source channel of the target application, that is, from which region's app store or distribution platform the application was downloaded.

[0057] It should be understood that network identifiers can effectively reflect the geographical area information of a user, because application distribution channels in different regions are usually associated with local operators or service providers. By parsing the identifier, the target service area where the vehicle is currently located can be inferred.

[0058] For example, when a user determines through an app that the vehicle meets the conditions for vehicle-to-everything (V2X) activation, the TSP platform can receive request data packets reported by the app, parse them, and determine the network identifier carried by the app. This network identifier serves as a key routing basis, guiding the TSP platform to select the correct service path.

[0059] In an exemplary embodiment, when a network identifier is determined, the target network operator is determined based on the area information indicated by the network identifier.

[0060] For example, the TSP platform maintains a mapping table between network identifiers and operators. By querying this mapping table, the network identifier can be matched with the available operators in the corresponding region, thereby issuing appropriate network configuration parameters to the vehicle to ensure that the vehicle-to-everything (V2X) function can be accessed normally and operate stably in the target area.

[0061] It should be understood that determining the target area through network identifiers has unique advantages compared to relying on navigation and positioning systems to obtain vehicle geographical location information. While navigation and positioning can accurately obtain the vehicle's latitude and longitude coordinates, its implementation depends on the quality of satellite signal reception. In scenarios with severe signal obstruction (such as underground parking garages, tunnels, and indoor environments), positioning delays or failures may occur. Furthermore, the acquisition and processing of location information typically requires additional hardware support and computing resources, and also requires users to grant location permissions, involving certain privacy and compliance considerations.

[0062] In contrast, identifying a vehicle's location using network identifiers does not rely on satellite signals or require enabling location service permissions. The network identifier is embedded in the app's request data; the TSP platform only needs to parse the network identifier to quickly infer the user's target service area and then match the corresponding network operator. This method offers advantages such as fast response time, low implementation cost, and no environmental signal limitations. It is particularly suitable for scenarios where the vehicle has not yet completed its initial network connection and the navigation and positioning functions may not yet be activated, effectively ensuring a smooth activation process.

[0063] S202. Based on the network configuration information of the target network operator, control the vehicle's network connectivity.

[0064] Network configuration information includes: data plan profile and three-code data.

[0065] The profile should include at least: Access Point Name (APN), Network Address (IP), and Domain Name System (DNS); the three-code data should include at least: Integrated Circuit Card Identifier (ICCID), International Mobile Equipment Identity (IMEI), and International Mobile Subscriber Identity (IMSI).

[0066] In the exemplary embodiment, after determining the target network operator, the TSP platform sends the network configuration information corresponding to that operator to the TBOX. Specifically, the sent Profile is used to configure the TBOX's network access parameters, the APN specifies the access gateway, the IP assigns the terminal address, and the DNS provides domain name resolution services. Simultaneously, the sent three-code data is used to complete identity registration and authentication on the operator's network side: ICCID identifies the ESIM hardware identity, IMEI identifies the TBOX terminal device, and IMSI identifies the user's subscription affiliation. After receiving the above network configuration information, the TBOX replaces or overwrites the original default configuration (such as seed number data) with this configuration and re-initiates the dial-up network connection request based on the new parameters.

[0067] For example, taking the scenario where activation is triggered after a vehicle is transported from a first region to a second region: When the TSP platform confirms that the vehicle has arrived in the second region through network identification and matches the target network operator for that region, it sends the operator's profile and three-code data to the TBOX. The TBOX then reconfigures the network parameters and initiates a registration and authentication request to the operator's network in the second region. After the operator's network verifies and approves the access for ICCID, IMEI, and IMSI, the TBOX successfully establishes a data connection, and the in-vehicle online function is officially activated. At this point, the vehicle has completed the complete switch from the seed number configuration in the first region to the target operator's network in the second region, and the vehicle-to-everything (V2X) service officially takes effect at the destination.

[0068] The vehicle networking method provided in this application can identify the network identifier of the target application that enables vehicle networking function for the vehicle when it first connects to the network after the vehicle is produced, or when the vehicle is transported from a first region to a second region. Based on the network identifier, the target network operator corresponding to the current area of ​​the vehicle can be quickly and accurately identified. Then, based on the network configuration information of the target network operator, the vehicle's networking control is performed, realizing automatic network configuration adaptation and efficient operator switching. This simplifies user operation, improves activation success rate, and significantly improves the accuracy and timeliness of network connection.

[0069] As a feasible implementation method, the above step S201 can be specifically implemented as: searching for the target network operator corresponding to the network identifier from the first preset correspondence.

[0070] In the first preset correspondence, the network identifier corresponds one-to-one with the network operator.

[0071] In an exemplary embodiment, the TSP platform pre-configures the profile information of each network operator of the ESIM card, as well as the correspondence between the APP distribution source channel (i.e., network identifier) ​​and the network operator.

[0072] It should be understood that by pre-fixing various network parameters and mapping rules that would otherwise need to be dynamically obtained during vehicle activation on the TSP platform, the TSP platform can quickly complete the matching and distribution of operator configuration information during the actual execution of the activation process. This eliminates the need to temporarily query external systems or wait for manual intervention during real-time processing, effectively shortening the activation response time and avoiding the risk of activation failure due to the unavailability of external dependencies.

[0073] For example, during the vehicle initialization or version deployment phase, the operations and maintenance personnel bind each network identifier (corresponding to the application distribution channel in a specific region) to the designated primary network operator in that region according to the list of network operators that have signed contracts with the TSP platform, forming a standardized mapping table. After review and confirmation, the table is entered into the configuration center of the TSP platform and becomes effective.

[0074] In the exemplary embodiment, after configuring the first preset correspondence, when the network identifier is determined, the TSP platform can directly use the network identifier as an index to quickly query and match the corresponding target network operator from the first preset correspondence without having to perform any dynamic area identification or operator selection logic.

[0075] It should be understood that the first preset mapping relationship takes the regional identification result of the network identifier and initiates the distribution and execution of IoT configuration. Through pre-fixed mapping rules, the platform can complete one-click operator orientation without the user's awareness, providing a clear decision basis for subsequent network control.

[0076] As a feasible implementation method, the above step S202 can be specifically implemented as follows: sending the network configuration information to the software development kit (SDK) configured in the vehicle, so that the SDK sends the network configuration information to the vehicle communication device TBOX.

[0077] Among them, TBOX is used to dial up and connect to the network based on network configuration information, so that the vehicle can access the network of the target network operator.

[0078] In an exemplary embodiment, after determining the target network operator through a first preset correspondence, the TSP platform initiates a request for new three-code data to the target network operator. Upon receiving the request, the target network operator assigns new three-code data (including ICCID, IMEI, and IMSI) to the current vehicle and returns this data to the TSP platform. After obtaining the new three-code data, the TSP platform encapsulates it together with the Profile configuration information (including APN, IP, and DNS) corresponding to the target network operator into network configuration information, issues an operator switching instruction to the vehicle's SDK, and pushes the aforementioned complete network configuration information to the SDK.

[0079] After receiving the switching command and network configuration information, the SDK transmits the target operator's Profile and the new three-code data to the TBOX. The TBOX reconfigures the network access point based on the received Profile parameters (APN, IP, DNS) and simultaneously initiates an identity registration and authentication request to the target operator's network using the new three-code data (ICCID, IMEI, IMSI). Once the operator's network completes the three-code verification and approves access, the TBOX successfully dials up and connects to the network, the vehicle officially connects to the target network operator's network, and the vehicle-to-everything (V2X) service becomes available.

[0080] It should be understood that in the above process, the SDK acts as a data relay bridge between the TSP platform and the TBOX, undertaking the intermediary role of reliable transmission of configuration information and command issuance. The TSP platform does not need to communicate directly with the TBOX, but instead uses the SDK to trigger operator switching and deliver configuration information. This indirect communication method reduces the coupling between the platform and the terminal, and also facilitates unified activation management in scenarios with multiple vehicle models and multiple platforms.

[0081] As a feasible implementation method, TBOX writes the network configuration information into the embedded general-purpose integrated circuit card ESIM after the network configuration information dial-up connection is successful.

[0082] The network configuration information in ESIM is used to reconnect to the network after a connection interruption.

[0083] In the exemplary embodiment, TBOX uses the latest network configuration information (including the target operator's profile and three-code data) received from the SDK to perform dial-up network operation. After successfully accessing the target operator's network, it writes the profile configuration information (including APN, IP, DNS) and three-code data (ICCID, IMEI, IMSI) used this time into the storage area of ​​the ESIM card to complete the persistent storage of the local configuration.

[0084] For example, after completing the writing of network configuration information and the operator switch, TBOX encapsulates the switch result (including success / failure status and related information) into a response message and first returns it to the SDK on the vehicle side; after receiving the result, the SDK transmits it to the TSP cloud server.

[0085] After receiving the successful switchover result reported by the SDK, the TSP cloud server performs the following follow-up operations: On the one hand, it updates the current network configuration status of the vehicle to the platform database, completing the persistence of the vehicle's vehicle networking function registration and activation records; on the other hand, according to the service plan corresponding to the target network operator, it completes the configuration and binding of the data plan for the vehicle, enabling the vehicle to obtain formal data service permissions.

[0086] After all the above operations are completed, the TSP cloud server will return the final result of successful vehicle networking function registration to the user's APP. The APP interface will display the activation completed status, and the user can then use all vehicle networking online services normally.

[0087] It should be understood that the significance of the ESIM writing mechanism lies in transforming the configuration parameters obtained at runtime into persistent "local credentials," enabling the vehicle to automatically reconnect based on the configuration information stored in the ESIM in abnormal scenarios such as power outages and restarts or network interruptions, without user intervention. The data loop formed between writing configuration information and platform registration ensures that the vehicle can operate stably with the correct operator configuration, whether it is online or reconnecting after being offline.

[0088] As a feasible implementation method, when a network failure signal is received from the TBOX via the SDK, the alternative network operator to replace the target network operator is searched from the second preset correspondence; based on the network configuration information of the alternative network operator, the vehicle's network connection is controlled.

[0089] Specifically, if the number of times the network configuration information fails to connect to the network is greater than or equal to a preset number, the TBOX will send a connection failure signal.

[0090] It should be understood that when the TBOX repeatedly attempts to dial up and connect to the network using the target network operator's network configuration information, and the cumulative number of failures reaches or exceeds a preset threshold (e.g., 3 times), it indicates that the target operator's network may have issues such as insufficient signal coverage, network congestion, or authentication anomalies, preventing the vehicle from connecting normally. In this case, the TBOX returns a connection failure signal to the TSP cloud server via the SDK to trigger the backup handover mechanism.

[0091] Here, a second preset correspondence is introduced as the basis for backup handover decisions. The second preset correspondence is used to characterize the correspondence between network identifier, the network operator corresponding to the network identifier, and the replacement network operator corresponding to the network operator.

[0092] During vehicle deployment, maintenance personnel assign one or more backup operators to each primary operator (i.e., the target operator bound in the first preset mapping) based on the redundancy configuration strategy of the contracted operators in each region. This forms a multi-level mapping table of "network identifier, target network operator, and replacement network operator," which is stored in the TSP platform configuration center. When constructing the second preset mapping, factors such as network coverage quality, signal strength, and roaming protocols of network operators in each region must be comprehensively considered to ensure that the replacement network operator can provide stable and reliable data connection services when the target network operator is unavailable.

[0093] It should be understood that the second preset mapping relationship is essentially a disaster recovery backup mechanism for the vehicle-to-everything (V2X) activation process. When the target network operator's network is unable to provide normal connectivity services to the vehicle for various reasons, the TSP platform can quickly switch to an alternative network operator based on the second preset mapping relationship, avoiding the failure of the entire V2X activation function due to a single operator's network problem. This design effectively improves the robustness and success rate of the activation process, ensuring that the vehicle can complete the network configuration as much as possible under various network environments.

[0094] To facilitate understanding, the following example illustrates how vehicles can connect to the network.

[0095] For example, such as Figure 3 As shown, the vehicle's networking method can be implemented through the following steps: S301. Users apply for registration and activate vehicle network functionality with a remote service provider through the target application.

[0096] S302. When the remote service provider determines that the vehicle meets the conditions for vehicle-to-everything (V2X) activation, it determines the target network operator from the first preset correspondence based on the network identifier of the target application.

[0097] The conditions for activating the vehicle-to-everything (V2X) network are: the vehicle being connected to the network for the first time after it is produced, or the vehicle being transported from the first region to the second region.

[0098] S303: The remote service provider obtains new network configuration information from the target network operator.

[0099] S304. The remote service provider sends new three-code data to the SDK integrated in the vehicle's TBOX.

[0100] S305, the SDK integrated in the vehicle's TBOX returns new three-code data to the remote service provider.

[0101] S306. The remote service provider stores the new three-code data and sends the target network operator's network configuration information to TBOX via the SDK.

[0102] S307 and TBOX dial up to the network based on the network configuration information of the target network operator.

[0103] S308 and TBOX write the target network operator's network configuration information into the embedded universal integrated circuit card ESIM.

[0104] S309, ESIM writes the network configuration information of the target network operator and returns the writing result to TBOX.

[0105] S310 and TBOX return network switching results to remote service providers via SDK.

[0106] S311. The remote service provider determines whether the handover was successful based on the network handover result. If yes, proceed to step S312; otherwise, proceed to step S314.

[0107] S312. The remote service provider changes the local data plan for the vehicle and returns a successful registration result to the target application.

[0108] S313, The target application prompts the user that registration was successful.

[0109] S314. The remote service provider returns a registration failure result to the target application.

[0110] S315. The target application prompts that user registration failed. Please try again.

[0111] The foregoing primarily describes the solutions of the embodiments of this disclosure from a methodological perspective. It is understood that, in order to achieve the aforementioned functions, the vehicle's networking device includes at least one of the hardware structures and software modules corresponding to the execution of each function. Those skilled in the art should readily recognize that, in conjunction with the units and algorithm steps of the various examples described in the embodiments disclosed herein, the embodiments of this disclosure can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed in hardware or by computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of the embodiments of this disclosure.

[0112] This disclosure embodiment can divide the vehicle's networking device into functional modules according to the above method embodiment. For example, each function can be divided into a separate functional module, or two or more functions can be integrated into one functional module. The integrated module can be implemented in hardware or software. It should be noted that the module division in this disclosure embodiment is illustrative and only represents one logical functional division; other division methods may be used in actual implementation. The following description uses the example of dividing each function into a separate functional module.

[0113] Figure 4 This is a schematic diagram of a vehicle networking device provided in an embodiment of this disclosure. This vehicle networking device is applied to a remote service provider and can execute the vehicle networking method provided in the above-described method embodiment. Figure 4 As shown, the vehicle networking device 400 includes: a determination module 401 and a control module 402; the determination module 401 is used to determine the target network operator in response to the network identifier of the target application when the vehicle meets the vehicle networking activation conditions; wherein, the vehicle networking activation conditions are: the vehicle's first network connection after production, or the vehicle being transported from a first region to a second region; the target application is an application downloaded at the vehicle's actual location to enable the vehicle's vehicle networking function; the network identifier is used to characterize the distribution source channel of the target application; the control module 402 is used to control the vehicle's network connection based on the network configuration information of the target network operator.

[0114] In some possible implementations, the determining module 401 is specifically used to find the target network operator corresponding to the network identifier from the first preset correspondence relationship; in the first preset correspondence relationship, the network identifier and the network operator are in a one-to-one correspondence.

[0115] In some possible implementations, the control module 402 is specifically used to send network configuration information to the software development kit (SDK) configured in the vehicle, so that the SDK sends the network configuration information to the vehicle communication device TBOX; the TBOX is used to dial up and connect to the network based on the network configuration information, so that the vehicle can access the network of the target network operator.

[0116] In some possible implementations, the TBOX writes the network configuration information into the embedded general-purpose integrated circuit card (ESIM) when the network configuration information dial-up connection is successful; the network configuration information in the ESIM is used for reconnection after a network interruption.

[0117] In some possible implementations, the control module 402 is further configured to, upon receiving a network failure signal returned by the TBOX via the SDK, search for a replacement network operator from a second preset correspondence; the second preset correspondence is used to characterize the correspondence between the network identifier, the network operator corresponding to the network identifier, and the replacement network operator corresponding to the network operator; the TBOX sends a network failure signal if the number of network configuration information dial-up connection failures is greater than or equal to a preset number; and performs network connection control on the vehicle based on the network configuration information of the replacement network operator.

[0118] In some possible implementations, network configuration information includes: a data plan profile and three-code data; the profile includes at least: an access point name (APN), a network address (IP), and a domain name system (DNS); the three-code data includes at least: an integrated circuit card identifier (ICCID), an international mobile device identifier (IMEI), and an international mobile subscriber identifier (IMSI).

[0119] When implementing the functions of the integrated modules described above in hardware, this disclosure provides a possible structure for the control device involved in the above embodiments. For example... Figure 5 As shown, the control device 500 includes a processor 502 and a bus 504. Optionally, the control device 500 may also include a memory 501; alternatively, the control device 500 may also include a communication interface 503.

[0120] Processor 502 may implement or execute various exemplary logic blocks, modules, and circuits described in conjunction with embodiments of this disclosure. Processor 502 may be a central processing unit, a general-purpose processor, a digital signal processor, an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. It may implement or execute various exemplary logic blocks, modules, and circuits described in conjunction with embodiments of this disclosure. Processor 502 may also be a combination that implements computing functions, such as including one or more microprocessor combinations, a combination of a DSP and a microprocessor, etc.

[0121] Communication interface 503 is used to connect to other devices via a communication network. This communication network can be Ethernet, wireless access network, wireless local area network (WLAN), etc.

[0122] The memory 501 may be a read-only memory (ROM) or other type of static storage device capable of storing static information and instructions, random access memory (RAM) or other type of dynamic storage device capable of storing information and instructions, or electrically erasable programmable read-only memory (EEPROM), disk storage medium or other magnetic storage device, or any other medium capable of carrying or storing desired program code in the form of instructions or data structures and accessible by a computer, but is not limited thereto.

[0123] In one possible implementation, the memory 501 can exist independently of the processor 502. The memory 501 can be connected to the processor 502 via a bus 504 and is used to store instructions or program code. When the processor 502 calls and executes the instructions or program code stored in the memory 501, it can implement the vehicle communication method provided in this embodiment. In another possible implementation, the memory 501 can also be integrated with the processor 502.

[0124] Bus 504 can be an extended industry standard architecture (EISA) bus, etc. Bus 504 can be divided into address bus, data bus, control bus, etc. For ease of representation, Figure 5 The bus is represented by a single thick line, but this does not mean that there is only one bus or one type of bus.

[0125] Some embodiments of this disclosure provide a computer-readable storage medium (e.g., a non-transitory computer-readable storage medium) storing computer program instructions that, when executed on a processor, cause the processor to perform a vehicle communication method as described in any of the above embodiments.

[0126] Exemplary examples of computer-readable storage media may include, but are not limited to: magnetic storage devices (e.g., hard disks, floppy disks, or magnetic tapes), optical discs (e.g., compact disks (CDs), digital versatile disks (DVDs), etc.), smart cards, and flash memory devices (e.g., erasable programmable read-only memory (EPROMs), cards, sticks, or key drives, etc.). The various computer-readable storage media described in this disclosure may represent one or more devices and / or other machine-readable storage media for storing information. The term "machine-readable storage medium" may include, but is not limited to, wireless channels and various other media capable of storing, containing, and / or carrying instructions and / or data.

[0127] This disclosure provides a computer program product containing instructions that, when run on a processor, cause the processor to execute the vehicle communication method described in any of the above embodiments.

[0128] This disclosure provides a vehicle including the control device of any of the preceding embodiments; or the computer-readable storage medium of any of the preceding embodiments; or the computer program product of any of the preceding embodiments.

[0129] The vehicle provided in this application may be a passenger vehicle or a freight vehicle, and may also be an electric vehicle or a hybrid vehicle. This application does not limit the specific purpose or power type of the vehicle, and the choice can be made according to actual needs.

[0130] A vehicle consists of a body and wheels. The body is used for passengers and for carrying goods, while the wheels are mounted underneath the body to support it and allow it to roll on the road, thus enabling the vehicle to move.

[0131] In some possible examples, the vehicle is equipped with a control system, which typically adopts a layered distributed architecture. From the bottom layer to the top layer, it can be roughly divided into a perception layer, a control layer, a coordination layer, and an interaction layer. The layers communicate with each other through an in-vehicle network.

[0132] The perception layer mainly consists of various sensors distributed inside and outside the vehicle, including but not limited to external environment cameras, millimeter-wave radar, lidar, ultrasonic sensors, in-vehicle driver monitoring cameras, microphone arrays, and various vehicle status sensors (such as wheel speed sensors, inertial measurement units, temperature sensors, etc.). The perception layer is responsible for collecting multi-dimensional data such as the vehicle's own operating status, driver behavior, and external driving environment in real time.

[0133] The control layer consists of dozens to hundreds of electronic control units (ECUs), distributed across multiple functional domains including powertrain, chassis, body, intelligent driving, and infotainment. Each ECU embeds real-time control software that performs closed-loop control of the vehicle's actuators based on preset control strategies or upper-level commands, and generates corresponding alarm signals when abnormal conditions are detected. Typical ECUs include the engine control unit, transmission control unit, brake control unit, steering control unit, vehicle stability control unit, airbag control unit, intelligent driving domain controller, and in-vehicle infotainment unit.

[0134] The coordination layer typically exists in the form of a domain controller or a central computing platform, responsible for cross-domain data fusion, global state management, and collaborative decision-making. The coordination layer centrally processes and schedules the sensing data and control commands that were originally scattered across various functional domains, connecting downwards to various electronic control units and supporting human-machine interaction functions upwards.

[0135] The interaction layer mainly includes in-cabin display devices (such as instrument panel, central control screen, head-up display), voice interaction system, haptic feedback device, etc., which are responsible for presenting vehicle status, warning information and driving suggestions to the driver in the form of visual, auditory or tactile, while receiving the driver's touch, voice and other input commands.

[0136] Data transmission and interaction between different layers are achieved through the vehicle bus network. Common vehicle bus protocols include CAN (Controller Area Network), CAN FD (CAN with Flexible Data-Rate), LIN (Local Interconnect Network), FlexRay, and vehicle Ethernet, which supports high-bandwidth data transmission. Among these, CAN and CAN FD buses are widely used for communication in real-time control domains such as powertrain and chassis, while vehicle Ethernet is gradually being applied to high-bandwidth sensor data transmission in the intelligent driving domain and multimedia interaction scenarios in the cockpit domain.

[0137] In some possible examples, the TBOX, as the core of the in-vehicle communication and computing platform, is configured with a processor and memory to execute the vehicle communication method provided in the embodiments of this application.

[0138] For example, the control device of this application is arranged in a TBOX.

[0139] For example, TBOX has multiple functional modules deployed to perform the various method steps.

[0140] The above description is merely a specific embodiment of this disclosure, but the scope of protection of this disclosure is not limited thereto. Any changes or substitutions within the technical scope disclosed in this disclosure should be included within the scope of protection of this disclosure. Therefore, the scope of protection of this disclosure should be determined by the scope of the claims.

Claims

1. A method for connecting vehicles to a network, characterized in that, Applied to remote service providers (TSPs), the method includes: If the vehicle meets the vehicle-to-everything (V2X) activation conditions, the target network operator is determined in response to the network identifier of the target application; wherein, the V2X activation conditions are: the vehicle is connected to the network for the first time after it is produced, or the vehicle is transported from a first region to a second region; the target application is an application downloaded at the actual location of the vehicle to enable the V2X function for the vehicle; the network identifier is used to characterize the distribution source channel of the target application; Based on the network configuration information of the target network operator, the vehicle is controlled to connect to the network.

2. The vehicle networking method according to claim 1, characterized in that, The determination of the target network operator in response to the network identifier of the target application includes: The target network operator corresponding to the network identifier is found from the first preset correspondence; in the first preset correspondence, the network identifier and the network operator are in a one-to-one correspondence.

3. The vehicle networking method according to claim 2, characterized in that, The step of controlling the vehicle's network connectivity based on the network configuration information of the target network operator includes: The network configuration information is sent to the software development kit (SDK) configured in the vehicle, so that the SDK sends the network configuration information to the vehicle communication device (TBOX); the TBOX is used to dial up and connect to the network based on the network configuration information, so that the vehicle can access the network of the target network operator.

4. The vehicle networking method according to claim 3, characterized in that, When the network configuration information is successfully dialed and connected to the network, the TBOX writes the network configuration information into the embedded general-purpose integrated circuit card (ESIM); the network configuration information in the ESIM is used for reconnection after a network interruption.

5. The vehicle networking method according to claim 3, characterized in that, The method further includes: Upon receiving a network failure signal returned by the TBOX through the SDK, the TBOX searches for a replacement network operator to replace the target network operator from the second preset correspondence. The second preset correspondence is used to represent the correspondence between the network identifier, the network operator corresponding to the network identifier, and the replacement network operator corresponding to the network operator. If the number of network configuration information dial-up connection failures is greater than or equal to a preset number, the TBOX sends the network failure signal. Based on the network configuration information of the replaced network operator, the vehicle is controlled to connect to the network.

6. The vehicle networking method according to claim 1, characterized in that, The network configuration information includes: data plan profile and three-code data; the profile includes at least: Access Point Name (APN), Network Address (IP), and Domain Name System (DNS); the three-code data includes at least: Integrated Circuit Card Identifier (ICCID), International Mobile Equipment Identity (IMEI), and International Mobile Subscriber Identity (IMSI).

7. A vehicle networking device, characterized in that, The device, applied to a remote service provider (TSP), includes: a determination module and a control module; The determination module is used to determine the target network operator in response to the network identifier of the target application when the vehicle meets the vehicle-to-everything (V2X) activation conditions; wherein the V2X activation conditions are: the vehicle is connected to the network for the first time after it is produced, or the vehicle is transported from a first region to a second region; the target application is an application downloaded at the actual location of the vehicle to enable the V2X function for the vehicle; the network identifier is used to characterize the distribution source channel of the target application; The control module is used to control the vehicle's network connectivity based on the network configuration information of the target network operator.

8. A control device, characterized in that, The control device includes: a memory and a processor; the memory and the processor are coupled; the memory is used to store instructions executable by the processor; when the processor executes the instructions, it performs the vehicle networking method as described in any one of claims 1 to 6.

9. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer instructions that, when executed on a processor, cause the processor to perform the vehicle networking method as described in any one of claims 1 to 6.

10. A computer program product, characterized in that, It includes a computer program; when the computer program is executed, it is capable of implementing the vehicle networking method as described in any one of claims 1 to 6.

11. A vehicle, characterized in that, It includes the control device as claimed in claim 8; or the computer-readable storage medium as claimed in claim 9; or the computer program product as claimed in claim 10.

Images