Vehicle terminal data distribution method and device, computer equipment and storage medium

Abstract

The application discloses a kind of distribution method, device, computer equipment and storage medium of vehicle terminal data.The method comprises: obtaining the equipment data generated by vehicle terminal in production stage and vehicle parking network stage, and obtaining the vehicle identification information corresponding to vehicle terminal after loading completion;Vehicle identification information is requested to vehicle enterprise server based on the target country information of vehicle, and the target country information of vehicle is determined;Unreleased data is determined based on equipment data, and target regional service server is determined from multiple regional service servers based on target country information;Unreleased data is sent to target regional service server;Processing result returned by target regional service server is obtained, and the distribution state of unreleased data is updated based on processing result.Thereby, cross-regional targeted distribution and distribution state closed-loop management of vehicle terminal equipment data are realized.

Description

Technical Field

[0001] This invention belongs to the field of vehicle data processing technology, and relates to a method, device, computer equipment and storage medium for distributing vehicle terminal data. Background Technology

[0002] With the development of vehicle-to-everything (V2X) technology, in-vehicle terminals generate various types of data during vehicle production, assembly, and network usage. This data typically needs to be further transmitted to corresponding business servers for subsequent processing. Because vehicle production, assembly, and subsequent business services involve different processing stages, the generation time and processing stages of in-vehicle terminal data are not entirely consistent. Furthermore, different countries or regions may have different business servers, meaning that data from in-vehicle terminals needs to undergo multiple processing stages when flowing from the production side to the business side. In existing data processing methods, the connection between data acquisition, data identification, data transmission, and distribution result management at each stage is limited. This can easily lead to situations where some device data cannot be distributed across regions in a timely manner, or where data has been processed but its actual distribution status is not accurately reflected. Summary of the Invention

[0003] This application provides a method, apparatus, computer equipment, and storage medium for distributing data from vehicle-mounted terminals, in order to improve the reliability of cross-regional data distribution from vehicle-mounted terminals and enable continuous and effective data distribution.

[0004] To achieve the above objectives, the present invention adopts the following technical solution: A method for distributing data from an in-vehicle terminal includes: Acquire device data generated by the vehicle-mounted terminal during the production and installation / network connection phases; After the vehicle terminal is installed in the vehicle, obtain the vehicle identification information corresponding to the vehicle terminal; Based on the vehicle identification information, request and determine the vehicle's target country information from the vehicle manufacturer's server; Based on the device data, undistributed data is determined; Based on the target country information, the target region business server is determined from multiple regional business servers. The undistributed data is sent to the target area service server; Obtain the processing result returned by the target area service server, and update the distribution status of the undistributed data based on the processing result.

[0005] Furthermore, the acquisition of device data generated by the vehicle-mounted terminal during the production and installation / network registration stages includes: During the production stage of the vehicle-mounted terminal, the vehicle-mounted terminal identifier and communication module identifier reported by the production line tools are obtained as equipment data for the production stage. When the vehicle terminal is installed and powered on and the embedded user identification module is successfully registered on the network, the vehicle terminal identifier, communication module identifier, embedded user identification module identifier, integrated circuit card identifier and mobile country code reported by the vehicle terminal are obtained as equipment data during the vehicle installation and network registration stage. Based on the equipment data from the production stage and the equipment data from the vehicle installation and network setup stage, the equipment data corresponding to the vehicle terminal is obtained.

[0006] Furthermore, the step of requesting and determining the vehicle's target country information from the vehicle manufacturer's server based on the vehicle identification information includes: Based on the vehicle identification information, a target country query request is sent to the vehicle manufacturer's server, and the query results returned by the vehicle manufacturer's server are obtained; If the target country information is not obtained based on the query results, the vehicle identification information is added to the target country query task. When the target country query task is triggered, the target country query request is sent again to the vehicle manufacturer's server based on the vehicle identification information; If the target country information is obtained based on the returned query results, then the target country information is saved.

[0007] Furthermore, determining undistributed data based on the device data includes: Determine whether there is any data in the device data that has not yet been distributed to the regional service server; If it exists, the data that has not yet been distributed to the regional service server is identified as the undistributed data; If it does not exist, the current distribution process of the vehicle terminal will end.

[0008] Furthermore, the multiple regional service servers correspond to different countries or regions, and the multiple regional service servers do not communicate with each other. Based on the target country information, the target regional service server is determined from multiple regional service servers, including: The target country corresponding to the vehicle terminal is determined based on the target country information; Based on the correspondence between the target country and the countries or regions each of the multiple regional business servers is responsible for, the regional business server responsible for the target country is determined, and the determined regional business server is used as the target regional business server.

[0009] Furthermore, after sending the undistributed data to the target area service server, the process further includes: The undistributed data is received by the target area service server, and the corresponding device data in the target area service server is added or updated based on the undistributed data. After the addition or update is completed, the processing result representing the completion of data processing is generated and returned by the target area business server.

[0010] Furthermore, after adding the vehicle identification information to the target country query task, the method further includes: Trigger a daily error-proofing inspection task for vehicle identification information that has not obtained target country information; Based on the aforementioned error-proofing inspection task, it is determined whether the vehicle identification information has not obtained the corresponding target country information after a preset number of days. If the vehicle identification information fails to obtain the corresponding target country information after the preset number of days, the vehicle identification information will be identified as abnormal vehicle identification information. An alarm message is generated based on the abnormal vehicle identification information, and the alarm message is sent to the corresponding responsible person.

[0011] A cross-regional distribution device for an in-vehicle terminal, used to execute the method for distributing in-vehicle terminal data, comprising: The equipment data acquisition module is used to acquire equipment data generated by the vehicle terminal during the production stage and the vehicle installation and network access stage; The vehicle identification information acquisition module is used to acquire the vehicle identification information corresponding to the vehicle terminal after the vehicle terminal is installed in the vehicle; The target country determination module is used to request and determine the target country information of the vehicle from the vehicle manufacturer's server based on the vehicle identification information. An undistributed data determination module is used to determine undistributed data based on the device data; The target server determination module is used to determine the target regional business server among multiple regional business servers based on the target country information. The data distribution module is used to send the undistributed data to the target area service server; The distribution status update module is used to obtain the processing result returned by the target area business server and update the distribution status of the undistributed data based on the processing result.

[0012] A computer device includes a memory and a processor, wherein the memory stores computer-readable instructions, and the processor executes the computer-readable instructions to implement the steps of the method for distributing data from a vehicle terminal.

[0013] A computer-readable storage medium storing computer-readable instructions, which, when executed by a processor, implement the steps of the method for distributing data from an in-vehicle terminal.

[0014] The beneficial effects of this invention are as follows: This application acquires equipment data generated by the vehicle-mounted terminal during the production and installation / network registration stages, and further acquires the corresponding vehicle identification information after the vehicle-mounted terminal is installed in the vehicle. This allows data generated by the vehicle-mounted terminal at different stages to enter the same cross-regional distribution processing flow. Based on this, the target country information of the vehicle is requested and determined from the vehicle manufacturer's server based on the vehicle identification information, so that subsequent data distribution can have a clear regional determination basis. At the same time, undistributed data is determined based on the acquired equipment data, so that the data that still needs to be processed is taken as the current distribution object. Furthermore, the target regional business server is determined from multiple regional business servers according to the target country information, and the undistributed data is sent to the target regional business server, so that the equipment data can be distributed to the corresponding business processing terminal according to the target country corresponding to the vehicle. After the data is sent, the processing result returned by the target regional business server is obtained, and the distribution status of the undistributed data is updated according to the processing result, so that the distribution status recorded on the production side can correspond to the actual processing result on the target regional business server side. Therefore, in the process of data distribution across production, vehicle loading and regional business of vehicle terminal equipment, a continuous closed-loop processing process is formed, which includes data acquisition, target area determination, identification of data to be distributed, targeted transmission to processing result feedback and distribution status update, thereby improving the accuracy and reliability of cross-regional data distribution of vehicle terminal equipment. Attached Figure Description

[0015] Figure 1 A schematic diagram illustrating the overall process of data distribution from vehicle-mounted terminals; Figure 2 A schematic diagram of the phased data collection process for vehicle-mounted terminal equipment; Figure 3 A schematic diagram of the target country information query and timed retry process; Figure 4 This is a schematic diagram illustrating the closed-loop process for identifying undistributed data and distributing it across regions. Figure 5 A schematic diagram of the error-proofing check and alarm process for missing information in the target country. Detailed Implementation

[0016] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. It should be understood that this application is not limited to the exemplary embodiments disclosed herein. All other embodiments obtained by those skilled in the art based on the embodiments of this application without creative effort are within the scope of protection of this application.

[0017] In the description of this invention, it should be understood that the terms "length", "width", "upper", "lower", "front", "rear", "left", "right", "vertical", "horizontal", "top", "bottom", "inner", "outer", etc., indicate the orientation or positional relationship based on the orientation or positional relationship shown in the accompanying drawings. They are only for the convenience of describing this invention and simplifying the description, and do not indicate or imply that the device or element referred to must have a specific orientation, or be constructed and operated in a specific orientation. Therefore, they should not be construed as limitations on this invention.

[0018] Furthermore, 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. In the description of this invention, "a plurality of" means two or more, unless otherwise explicitly specified.

[0019] In the embodiments of this invention, unless otherwise explicitly specified and limited, the terms "installation," "connection," "linking," "fixing," etc., should be interpreted broadly. For example, they can refer to a fixed connection, a detachable connection, or an integral part; they can refer to a mechanical connection or an electrical connection; they can refer to a direct connection or an indirect connection through an intermediate medium; they can refer to the internal communication of two components or the interaction between two components. Those skilled in the art can understand the specific meaning of the above terms in this invention according to the specific circumstances.

[0020] In this embodiment, the vehicle-mounted terminal can be a vehicle-mounted TBOX (Telematics Box), which is a vehicle-mounted terminal installed in the vehicle and capable of interacting with an external server. The production server can be a TMS production server, used to receive and process data generated by the vehicle-mounted terminal at different stages, and to perform target country information acquisition and cross-regional data distribution. The regional business server can be a TSP business server, with multiple regional business servers respectively used to process vehicle-mounted terminal-related data for their respective countries or regions. The vehicle manufacturer's server is used to query and return the target country information corresponding to the vehicle based on the vehicle identification information.

[0021] This invention provides an appendix Figures 1-5 In this embodiment of the invention, a method for distributing vehicle terminal data includes: S1. Obtain device data generated by the vehicle terminal during the production and vehicle installation / network connection stages; In this embodiment, during the process from production to vehicle installation, different device data can be gradually formed as the vehicle terminal progresses. To ensure that subsequent regional distribution has the necessary data foundation, the production server acquires the device data formed during the production stage and the device data formed during the vehicle installation and network registration stage, and saves the acquired device data.

[0022] In this embodiment, the device data refers to data related to the vehicle-mounted terminal itself and its communication, and which can be used as a target for subsequent regional distribution. Data generated during the production and installation / network registration stages can be reported to the production server by the corresponding data generating end, and received by the production server, thereby enabling data generated by the same vehicle-mounted terminal at different stages to be aggregated on the production server. The specific data content and reporting conditions generated by the device data at different stages can be determined according to the stage of the vehicle-mounted terminal, and this embodiment does not further limit this.

[0023] In step S1, the production server obtains device data that can be distributed subsequently, and uses the device data as the data basis for determining undistributed data.

[0024] In this embodiment, the vehicle-mounted terminal can be a vehicle-mounted TBOX (Telematics Box, vehicle communication terminal). The TBOX is installed in the vehicle to enable data communication between the vehicle and an external server, and can generate and report corresponding device data during vehicle production and installation. During the production phase, the TBOX has basic device data for identifying the vehicle-mounted terminal and its communication module; after the TBOX is installed, powered on, and network-connected, it can also generate and report data related to the communication module, embedded user identification module, and network status; after the TBOX is installed, it can also obtain and report the vehicle identification information corresponding to the vehicle it is installed in. The production server receives the data generated by the TBOX at different stages and processes the device data, vehicle identification information, and subsequent cross-regional distribution processes corresponding to the TBOX.

[0025] S2. Obtain the vehicle identification information corresponding to the vehicle terminal after the vehicle terminal is installed in the vehicle; In this embodiment, the vehicle identification information can be a Vehicle Identification Number (VIN), used to identify the vehicle to which the in-vehicle terminal is installed. After the in-vehicle terminal is installed, it reports the corresponding vehicle identification information to the production server, enabling the production server to perform subsequent target country information queries based on the vehicle identification information.

[0026] In this embodiment, after the vehicle terminal is installed in the vehicle and the installation is completed, a correspondence is formed between the vehicle terminal and the specific vehicle, and at this time the vehicle identification information corresponding to the vehicle terminal is obtained.

[0027] In this embodiment, vehicle identification information refers to information that can identify the vehicle to which the vehicle-mounted terminal is installed, such as a Vehicle Identification Number (VIN). The vehicle identification information can be reported by the vehicle-mounted terminal after installation to the production server, enabling the production server to determine the vehicle corresponding to the vehicle-mounted terminal currently processing data.

[0028] After obtaining the vehicle identification information in step S2, the vehicle identification information is not used directly to determine the regional service server. Instead, the vehicle identification information is used as the input for subsequent queries of the vehicle's target country information, thereby connecting the device data of the vehicle terminal with the vehicle's subsequent regional distribution needs.

[0029] S3. Based on the vehicle identification information, request and determine the vehicle's target country information from the vehicle manufacturer's server; In this embodiment, the target country information is used to characterize the target country corresponding to the current vehicle and serves as the basis for subsequently determining the target region business server. The target country information can be the vehicle sales target country information queried and returned by the vehicle manufacturer's server based on vehicle identification information.

[0030] In this embodiment, after obtaining vehicle identification information, the production server sends a target country query request to the vehicle manufacturer's server based on the vehicle identification information. The vehicle manufacturer's server determines the corresponding vehicle based on the vehicle identification information carried in the target country query request, queries the target country information of the vehicle, and then returns the queried target country information to the production server.

[0031] The production server receives information returned by the car manufacturer's server and determines the target country information of the vehicle corresponding to the in-vehicle terminal.

[0032] In this embodiment, the target country information refers to information used to characterize the target country corresponding to the vehicle. Since different vehicles subsequently need to distribute data regionally according to their target countries, obtaining the target country information from the vehicle manufacturer's server through vehicle identification information can provide a basis for determining the specific data receiving server from multiple regional business servers.

[0033] Therefore, the vehicle identification information output in step S2 serves as the query input for step S3, and the target country information output in step S3 further serves as the input for the subsequent target area determination service server.

[0034] S4. Determine undistributed data based on the device data; In this embodiment, the undistributed data refers to device data that has been acquired by the production server but has not yet been distributed to the corresponding regional business server.

[0035] In this embodiment, after the production server has obtained the device data in step S1, it judges the current distribution status of the device data to determine the data that has not yet been distributed to a region, and determines the data that has not yet been distributed to a region as undistributed data.

[0036] In this embodiment, "undistributed data" refers to data that has been acquired by the production server but has not yet been sent and processed to the corresponding regional business server. Since the device data acquired by the production server may be in different distribution stages, an undistributed determination is made on the device data before executing a new data distribution operation. This ensures that subsequent data transmission uses the data that still needs to be distributed as the transmission target, without repeatedly using data that has already been distributed as the current distribution target.

[0037] In step S4, the device data obtained in step S1 is further identified as undistributed data that needs to be distributed, thereby obtaining the data object required for subsequent data transmission.

[0038] S5. Based on the target country information, determine the target region business server among multiple regional business servers; In this embodiment, the regional service server is used to process vehicle terminal equipment data of the corresponding country or region; the target regional service server refers to the regional service server determined from multiple regional service servers based on the target country information of the current vehicle, which is used to receive the currently undistributed data.

[0039] In this embodiment, after obtaining the target country information of the vehicle in step S3, the production server uses the target country information as the basis for server selection to determine the target regional business server for receiving the currently undistributed data from multiple regional business servers.

[0040] Specifically, the production server searches for the regional business server corresponding to the target country information among multiple regional business servers based on the target country information, and identifies the found regional business server as the target regional business server.

[0041] Therefore, after executing step S5, a data transmission target matching the current vehicle target country information can be obtained, enabling subsequent steps to send the undistributed data determined in step S4 to a specific server object.

[0042] Steps S4 and S5 respectively determine the "data to be sent" and the "data sending target" for this data distribution, which together form the basis for subsequent cross-regional data transmission.

[0043] S6. Send the undistributed data to the target area service server; In this embodiment, after determining the undistributed data and the target area service server, the production server sends the undistributed data determined in step S4 to the target area service server determined in step S5.

[0044] Specifically, the production server establishes data interaction with the target region's business server and sends the undistributed data as the content of this distribution. After receiving the undistributed data, the target region's business server performs corresponding processing on the received data.

[0045] This step involves transmitting the device data generated by the vehicle terminal in the aforementioned stage but not yet distributed to the corresponding target region business server according to the target country information of the vehicle, thereby completing the data flow of device data from the production server to the target region business server.

[0046] After the data is sent, the production server does not immediately recognize that the data has been distributed. Instead, it continues to wait for the target area business server to return the corresponding processing result in order to determine whether the data distribution is complete based on the actual processing result.

[0047] S7. Obtain the processing result returned by the target area service server, and update the distribution status of the undistributed data based on the processing result.

[0048] In this embodiment, after receiving the undistributed data sent in step S6 and completing the corresponding processing, the target area service server returns the processing result corresponding to this data processing to the production server.

[0049] The production server obtains the processing result and determines whether the currently sent undistributed data has completed the corresponding data processing based on the processing result. When the processing result indicates that the current undistributed data has been processed, the production server updates the distribution status corresponding to the undistributed data, changing it from a state of not yet completed distribution to a state of completed distribution.

[0050] By updating the data distribution status based on the actual processing results returned by the target area business server, the data distribution status of the device can correspond to the actual processing situation on the side of the area business server, rather than directly determining that the data has been distributed based solely on the data sending action of the production server.

[0051] Therefore, in this embodiment, the device data generated by the vehicle terminal during the production and vehicle installation / network registration stages is first acquired, and the corresponding vehicle identification information is acquired after the vehicle terminal is installed in the vehicle. Then, the target country information is obtained from the vehicle manufacturer's server using the vehicle identification information. On the one hand, the undistributed data that needs to be sent is determined based on the device data, and on the other hand, the target regional business server is determined from multiple regional business servers based on the target country information. After determining the data to be sent and its sending target, the undistributed data is sent to the target regional business server, and the distribution status of the corresponding data is updated according to the processing result returned by the target regional business server. This forms a continuous cross-regional distribution process of "device data acquisition - vehicle identification - target country determination - undistributed data determination - target server determination - data transmission - processing result feedback and distribution status update".

[0052] Acquire device data generated by the vehicle-mounted terminal during the production and installation / network registration phases, including: During the production stage of the vehicle-mounted terminal, the vehicle-mounted terminal identifier and communication module identifier reported by the production line tools are obtained as equipment data for the production stage. Specifically, during the production process, the production line tools acquire the vehicle terminal identifier corresponding to the current vehicle terminal and the communication module identifier corresponding to the communication module configured in the vehicle terminal, and report the acquired vehicle terminal identifier and communication module identifier to the production server. The production server receives the data reported by the production line tools and saves the received vehicle terminal identifier and communication module identifier as the production stage equipment data corresponding to the vehicle terminal.

[0053] In this embodiment, the vehicle terminal identifier is used to identify different vehicle terminals and can be a vehicle terminal serial number (TBOX SN); the communication module identifier is used to identify the communication module configured in the vehicle terminal and can be an International Mobile Equipment Identity (IMEI). Therefore, basic equipment data identifying the vehicle terminal itself and its communication module can be obtained even when the vehicle terminal is still in the production stage.

[0054] After acquiring equipment data during the production phase, the vehicle-mounted terminal is installed in the vehicle and powered on, entering the vehicle installation and network setup phase.

[0055] When the vehicle terminal is installed and powered on and the embedded user identification module is successfully registered on the network, the vehicle terminal identifier, communication module identifier, embedded user identification module identifier, integrated circuit card identifier and mobile country code reported by the vehicle terminal are obtained as equipment data during the vehicle installation and network registration stage. In this embodiment, the embedded user identification module can be an eSIM (Embedded Subscriber Identification Module), used to enable the vehicle terminal to obtain the corresponding mobile communication network access capability. The embedded user identification module identifier can be an EID, used to identify the eSIM; the integrated circuit card identifier can be an ICCID, used to identify the integrated circuit card information corresponding to the eSIM; the mobile country code can be an MCC (Mobile Country Code), used to represent the mobile communication country information corresponding to the vehicle terminal's network registration.

[0056] Specifically, after the vehicle-mounted terminal is installed and powered on, its embedded user identification module performs a network registration operation. Upon successful registration, the vehicle-mounted terminal reports its corresponding vehicle terminal identifier, communication module identifier, and the embedded user identification module identifier, integrated circuit card identifier, and mobile country code obtained after registration to the production server. The production server receives and saves this data, thereby obtaining the device data for the vehicle-mounted terminal during the network registration phase.

[0057] In this embodiment, the embedded user identification module identifier can be an EID, used to identify the embedded user identification module configured in the vehicle terminal; the integrated circuit card identifier can be an ICCID, used to identify the integrated circuit card corresponding to the embedded user identification module; and the mobile country code can be an MCC, used to characterize the mobile communication country information obtained when the vehicle terminal registers with the network.

[0058] By using the successful registration of the embedded user identification module as a condition for obtaining equipment data during the vehicle registration phase, the data acquisition at this stage occurs after the corresponding registration information has been formed. This allows the production server to further obtain data related to communication with the vehicle terminal and registration based on the equipment data from the production phase.

[0059] After obtaining the equipment data in the production stage and the equipment data in the vehicle installation and network setup stage, the equipment data corresponding to the vehicle terminal is obtained based on the equipment data in the production stage and the equipment data in the vehicle installation and network setup stage.

[0060] Specifically, the production server saves the vehicle terminal identifier and communication module identifier obtained during the production stage, and saves the vehicle terminal identifier, communication module identifier, embedded user identification module identifier, integrated circuit card identifier and mobile country code obtained during the vehicle installation and network access stage, so that the equipment data in the production stage and the equipment data in the vehicle installation and network access stage together constitute the equipment data corresponding to the vehicle terminal.

[0061] Both stages include the vehicle terminal identifier and communication module identifier corresponding to the vehicle terminal, ensuring that the basic equipment data generated in the production stage and the communication and network registration data further generated in the vehicle installation and network registration stage correspond to the same vehicle terminal. Therefore, as the vehicle terminal moves from the production stage to the vehicle installation and network registration stage, its corresponding equipment data is further expanded from the basic equipment data of the production stage to include equipment data containing embedded user identification module information and network registration information.

[0062] Through the above process, during the vehicle terminal production stage, the vehicle terminal identifier and communication module identifier are first obtained, forming equipment data for the production stage. After the vehicle terminal is installed in the vehicle and powered on, and the embedded user identification module is successfully registered on the network, the vehicle terminal identifier, communication module identifier, embedded user identification module identifier, integrated circuit card identifier, and mobile country code are further obtained, forming equipment data for the vehicle installation and network registration stage. Subsequently, based on the data obtained in the two stages, the equipment data corresponding to the vehicle terminal is obtained, so that the equipment data can be gradually obtained and collected as the vehicle terminal is in its current stage, providing a data foundation for the subsequent processing of vehicle terminal equipment data.

[0063] The step of requesting and determining the vehicle's target country information from the vehicle manufacturer's server based on the vehicle identification information includes: Based on the vehicle identification information, a target country query request is sent to the vehicle manufacturer's server, and the query results returned by the vehicle manufacturer's server are obtained; In this embodiment, after the vehicle-mounted terminal is installed and obtains the corresponding vehicle identification information, the production server uses the vehicle identification information as input for the target country query, generates a target country query request for the current vehicle, and sends the target country query request to the vehicle manufacturer's server. The target country query request carries the vehicle identification information so that the vehicle manufacturer's server can determine the vehicle to be queried based on the vehicle identification information.

[0064] In this embodiment, the vehicle identification information can be a Vehicle Identification Number (VIN). After receiving a target country query request, the vehicle manufacturer's server queries the target country information corresponding to the vehicle based on the VIN information carried therein, and returns the query result to the production server. The production server receives the query result and determines whether the query has obtained the target country information corresponding to the current vehicle.

[0065] Through the above process, the vehicle identification information obtained after the vehicle terminal is installed in the vehicle is converted into a target country query request that can be processed by the vehicle manufacturer's server, so that the vehicle identification information becomes the basis for querying the vehicle's target country information.

[0066] If the target country information is not obtained based on the query results, the vehicle identification information is added to the target country query task. In this embodiment, the target country query task is used to record vehicle identification information for which target country information has not yet been obtained and requires subsequent target country queries. When the target country query task is triggered, a target country query request is resent to the vehicle manufacturer's server based on the vehicle identification information recorded therein.

[0067] Specifically, after receiving the query results from the vehicle manufacturer's server regarding the target country query request, the production server determines whether the query results contain the target country information corresponding to the current vehicle. If the target country information can be obtained from the query results, the target country information corresponding to the current vehicle can be obtained directly; if the target country information cannot be obtained from the query results, it indicates that the target country of the vehicle cannot be determined based on the current query results.

[0068] If the target country information is not obtained, the production server does not terminate the acquisition of the target country information for that vehicle. Instead, it adds the vehicle identification information corresponding to this query to the target country query task. The target country query task is used to store vehicle identification information for which the target country information has not yet been obtained and which needs to be queried again later, so that the production server can reuse the vehicle identification information to initiate a query to the vehicle manufacturer's server later.

[0069] Therefore, the condition for adding vehicle identification information to the target country query task comes from the query result of the previous step. That is, only when the target country information is not obtained based on the current query result will the corresponding vehicle identification information be transferred to the subsequent query process, so as to form a conditional connection between the first query and the subsequent queries.

[0070] When the target country query task is triggered, the target country query request is sent again to the vehicle manufacturer's server based on the vehicle identification information; Specifically, for vehicle identification information that has been added to the target country query task, after the target country query task is triggered, the production server obtains the corresponding vehicle identification information from the target country query task, and generates a target country query request again using the vehicle identification information as the query basis, and sends the regenerated target country query request to the vehicle manufacturer's server.

[0071] After receiving the target country query request again, the vehicle manufacturer's server queries the target country information corresponding to the current vehicle based on the vehicle identification information carried in the request, and returns the query result obtained from the second query to the production server.

[0072] In this embodiment, the target country query task is set up so that vehicles that do not obtain target country information in the first query can retain the opportunity for subsequent queries without having to re-execute the vehicle identification information acquisition process after the on-board terminal is installed. Subsequent queries directly use the vehicle identification information that has already been added to the target country query task, so as to keep the previous and subsequent queries targeting the same vehicle.

[0073] If the target country information is still not obtained after a second query, the current vehicle identification information can remain in the target country query task, waiting for the target country query task to be triggered again to repeat the process of sending a target country query request to the vehicle manufacturer's server based on the vehicle identification information; until the corresponding target country information is obtained in a subsequent query result. This allows for a continuous query process for situations where target country information cannot be obtained temporarily, without losing the current vehicle's target country query requirement due to a single unsuccessful query.

[0074] If the target country information is obtained based on the returned query results, then the target country information is saved.

[0075] Specifically, the production server obtains the query results returned by the vehicle manufacturer's server in response to a resent target country query request, and evaluates the query results. When the target country information corresponding to the current vehicle identification information is obtained from the query results, it is determined that the target country information of the current vehicle has been obtained, and the target country information is saved.

[0076] When saving the target country information, the saved target country information is made to correspond with the vehicle identification information on which the query is based, so that when the target country information of the current vehicle is needed in the future, the target country information that has been obtained can be determined according to the corresponding vehicle.

[0077] Through the above process, this embodiment first performs an initial query for target country information to the vehicle manufacturer's server based on the vehicle identification information. If the initial query does not obtain target country information, the corresponding vehicle identification information is added to the target country query task. After the target country query task is triggered, a new target country query is initiated to the vehicle manufacturer's server based on the vehicle identification information. If the new query obtains target country information, the target country information is saved. This forms a continuous target country information acquisition process of "vehicle identification information input - initial query - query result judgment - adding to query task if not obtained - task triggering for another query - saving after obtaining target country information," enabling vehicles that have temporarily failed to obtain target country information to still obtain the corresponding target country information through subsequent queries.

[0078] The determination of undistributed data based on the device data includes: Determine whether there is any data in the device data that has not yet been distributed to the regional service server; After the production server obtains the device data corresponding to the vehicle terminal, it checks the current distribution status of the device data to determine whether the device data has been successfully distributed to the regional service server. This determination is used to ascertain whether the vehicle terminal still has data that needs to be distributed across regions before actual data transmission, so that subsequent distribution operations will focus on data that has not yet been distributed.

[0079] In this embodiment, "data that has not yet been distributed to the regional service server" refers to device data that has been acquired and saved by the production server but has not yet completed the corresponding regional distribution process. Data that has already been distributed will no longer be considered as pending data in the current distribution process; data that has not yet been distributed will continue into the subsequent data determination process.

[0080] In practice, the production server can assess the device data item by item or as a whole based on the current distribution status of the device data to determine whether there is at least one piece of data that has not yet been distributed. The specific record fields and data structure for the distribution status are not limited here, as long as they can distinguish between device data that has been distributed and device data that has not yet been distributed.

[0081] Based on the above judgment, the system determines whether there is data in the current vehicle terminal's device data that needs to be distributed to other regions. This determination result then serves as a condition for whether to continue the distribution process.

[0082] If the device data contains data that has not yet been distributed to the regional service server, then the data that has not yet been distributed to the regional service server is determined as the undistributed data.

[0083] Specifically, when the above judgment result indicates that there is at least some device data that has not yet been distributed to a region, the production server determines the corresponding data from the device data corresponding to the current vehicle terminal and uses the determined data as the undistributed data in this cross-regional distribution process.

[0084] In this embodiment, the undistributed data originates from the previously acquired device data, not newly generated data. That is, the production server first uses the device data as the judgment object, and then determines the data that actually needs to continue distribution based on the current distribution status of the device data, thereby achieving the filtering from "device data" to "currently undistributed data".

[0085] For example, when a vehicle terminal corresponds to multiple device data sets, some of which have already been distributed regionally while others have not, only the portion that has not yet been distributed is identified as the undistributed data. This process allows subsequent data distribution operations to be performed on the data that still needs to be sent, without having to reuse already distributed data as the current distribution target.

[0086] After determining the undistributed data, it indicates that there is still data in the vehicle terminal that needs to be distributed regionally. Therefore, the subsequent cross-regional distribution process continues to be executed so that the undistributed data can be further sent to the corresponding regional business server.

[0087] If there is no data in the device data that has not yet been distributed to the regional service server, then the current distribution process of the vehicle terminal ends.

[0088] Specifically, when the production server assesses the device data and determines that none of the data has yet to be distributed to a specific region, it indicates that the current vehicle terminal has no undistributed data that needs to be sent in this process. In this case, the data distribution operation for that vehicle terminal will not continue, and the current distribution process for that vehicle terminal will end.

[0089] "Ending the current distribution process" means that the data distribution process triggered by the current vehicle terminal will no longer continue to execute subsequent data sending operations, and does not mean deleting the already saved device data. The already saved device data can still be retained in the production server for subsequent data management or use when the distribution process is triggered again.

[0090] Therefore, this embodiment takes the acquired device data as input and first determines whether there is any data that has not yet been distributed to the regional service server. If so, the corresponding undistributed data is identified from the device data and used as the data object for subsequent cross-regional distribution. If not, the current distribution process of the in-vehicle terminal is terminated. By using the conditional processing method of "device data acquisition - distribution status judgment - identifying undistributed data and continuing distribution if it exists / ending the current process if it does not exist", the data distribution process continues to execute only when there is indeed data to be distributed, thereby avoiding data that has already been distributed from being repeatedly used as the object to be sent in the current process.

[0091] Each of the multiple regional service servers corresponds to a different country or region, and the multiple regional service servers do not communicate with each other. Specifically, each of the multiple regional service servers corresponds to a different country or region. Each regional service server has a corresponding data service range, which may include a single country or a region consisting of multiple countries. Therefore, different vehicles can correspond to different regional service servers based on their target country information.

[0092] In this embodiment, "regional business server" refers to a business server used to receive and process data from vehicle-mounted terminal devices in the corresponding country or region; "target regional business server" refers to a regional business server determined from multiple regional business servers based on the target country information of the current vehicle, which is responsible for receiving relevant data of the current vehicle.

[0093] The multiple regional service servers do not communicate with each other. That is, a regional service server does not forward the current vehicle's equipment data through other regional service servers, nor does it determine the corresponding data receiving server for the current vehicle through other regional service servers. Therefore, the equipment data corresponding to the vehicle needs to be sent directly to the production server based on the vehicle's target country information, thus avoiding reliance on data forwarding between different regional service servers to complete regional distribution.

[0094] Based on the target country information, the target regional service server is determined from multiple regional service servers, including: The target country corresponding to the vehicle terminal is determined based on the target country information; The target country information is used to characterize the target country corresponding to the vehicle equipped with the vehicle terminal. After the production server obtains the target country information, it identifies the target country information to determine the target country corresponding to the current vehicle, and uses the determined target country as input for the subsequent selection of the region service server.

[0095] For example, when the obtained target country information indicates that the vehicle's target country is a first country, then the first country is determined as the target country corresponding to the current vehicle terminal; when the target country information indicates that the vehicle's target country is a second country, then the second country is correspondingly determined as the target country corresponding to the current vehicle terminal. Thus, the vehicle's target country information is transformed into a target country that can be used to match the service range of various regional business servers.

[0096] Based on the correspondence between the target country and the countries or regions each of the multiple regional business servers is responsible for, the regional business server responsible for the target country is determined, and the determined regional business server is used as the target regional business server.

[0097] Specifically, the production server matches the target country based on the countries or regions each regional business server is responsible for. When the target country is located within the country or region responsible for by a certain regional business server, it is determined that the regional business server is capable of receiving and processing the data corresponding to the current vehicle terminal.

[0098] For example, the first regional business server is responsible for the first and second countries, and the second regional business server is responsible for the third and fourth countries. When the target country for the current vehicle is determined to be the second country based on the target country information, the first regional business server is determined to be the regional business server responsible for that target country, based on the correspondence that the second country falls within the scope of responsibility of the first regional business server; when the target country is the third country, the second regional business server responsible for the third country is determined to be the corresponding regional business server.

[0099] The first, second, third, and fourth countries mentioned above are only used to illustrate the process of determining the correspondence between the target country and the regional business server, and are not intended to limit the specific country or region.

[0100] After determining the regional service server responsible for the target country, the determined regional service server is used as the target regional service server. Therefore, the determination of the target regional service server depends on the target country obtained in the previous step, and the target country is determined by the target country information corresponding to the vehicle, thus forming a continuous determination process of "target country information — target country — regional service server service range — target regional service server".

[0101] Since multiple regional business servers do not communicate with each other, once the target regional business server is determined, the production server does not need to send data to any regional business server first and then forward it across servers. Instead, it can directly determine the target regional business server that is responsible for the current vehicle data processing task based on the target country information, thus providing a clear data sending target for sending the data corresponding to the current vehicle terminal to the correct regional business server in the future.

[0102] Through the above process, this embodiment first uses the vehicle's target country information to determine the target country corresponding to the current vehicle terminal, and then matches the target country with the countries or regions respectively handled by multiple regional service servers; when it is determined that a certain regional service server is responsible for the target country, that regional service server is designated as the target regional service server. Therefore, even when multiple regional service servers are responsible for different countries or regions and do not communicate with each other, a unique corresponding data distribution target can be determined according to the vehicle's target country information, providing a server selection basis for cross-regional targeted distribution of vehicle terminal data according to the target country.

[0103] After sending the undistributed data to the target area service server, the process further includes: The undistributed data is received by the target area service server, and the corresponding device data in the target area service server is added or updated based on the undistributed data. Specifically, the undistributed data is sent from the production server to the target area business server. After receiving the undistributed data, the target area business server determines the corresponding device data based on the received undistributed data and performs addition or update processing on the data on the target area business server side.

[0104] In this embodiment, "adding" refers to the target area service server creating corresponding device data based on the received undistributed data; "updating" refers to updating the corresponding device data based on the currently received undistributed data when the target area service server already has the corresponding device data. Through adding or updating, the device data stored in the target area service server can correspond to the currently received undistributed data.

[0105] For example, if the target area service server has not yet saved the device data corresponding to the current vehicle terminal, the corresponding device data can be added based on the received undistributed data; if the target area service server has already saved the device data corresponding to the current vehicle terminal, the saved corresponding device data can be updated based on the received undistributed data. It should be noted that this embodiment does not limit the specific data storage structure used by the target area service server or the specific fields for determining addition and update, as long as it can complete the addition or update of the corresponding device data based on the received undistributed data.

[0106] Through the above processing, the undistributed data in the steps is further transformed from "data that the production server has determined needs to be sent" into "data that the target area business server actually receives and processes". This makes it possible for the data to be distributed not only to the production server, but also to the target area business server, to actually complete the corresponding data processing.

[0107] After the addition or update is completed, the processing result representing the completion of data processing is generated and returned by the target area business server.

[0108] Specifically, after completing the addition or update of data for the corresponding device, the target area service server generates a processing result based on the completion status of this data processing. This processing result is used to report the processing status of the undistributed data sent in this transaction to the production server on the target area service server side. When the corresponding device data has been added or updated, the processing result indicates that this data processing is complete.

[0109] The target region's business server returns the generated processing result to the production server, enabling the production server to determine whether the previously sent, undistributed data has been processed on the target region's business server side. Therefore, the data processing result from the target region's business server becomes the feedback basis for the production server to subsequently determine the distribution status of the corresponding undistributed data, rather than directly assuming that the data has been distributed after it has been sent.

[0110] In this embodiment, the processing result corresponds to the undistributed data sent to the target area service server, enabling the production server to perform subsequent distribution status processing on the corresponding undistributed data after receiving the processing result. This embodiment does not specifically limit the specific data format, result code, or communication interface form of the processing result, as long as the returned processing result can characterize whether the data processing corresponding to the undistributed data is complete.

[0111] In this embodiment, the processing result is used to characterize the processing status of the undistributed data received this time by the target area service server; when the corresponding device data is added or updated, the target area service server generates a processing result characterizing the completion of data processing and returns it to the production server.

[0112] Therefore, this embodiment forms a continuous processing flow of "undistributed data transmission—target area service server reception—corresponding device data addition or update—processing completion—generation of processing result—return of processing result". In this process, the undistributed data sent in the previous step serves as the data input for the target area service server to perform addition or update. The completion result of the addition or update further serves as the basis for generating the processing result, which is then returned to the production server. This allows the production server to continue performing corresponding distribution status management based on the actual processing status of the target area service server, thereby forming a data distribution feedback link between the production server and the target area service server.

[0113] After adding the vehicle identification information to the target country query task, the method further includes: Trigger a daily error-proofing inspection task for vehicle identification information that has not obtained target country information; In this embodiment, the error-proofing check task is used to periodically check vehicle identification information that has not yet obtained target country information, in order to determine whether the corresponding vehicle identification information has entered an abnormal state due to the long-term lack of target country information. The abnormal vehicle identification information refers to vehicle identification information that has not obtained the corresponding target country information for more than a preset number of days.

[0114] Specifically, the production server stores vehicle identification information that has not yet obtained target country information and triggers a mistake-proofing check task on a daily execution cycle. After each mistake-proofing check task is triggered, the vehicle identification information that has not yet obtained target country information is used as the inspection object, thereby performing periodic checks on vehicles in a state of missing target country information.

[0115] In this embodiment, the vehicle identification information can be the Vehicle Identification Number (VIN). The purpose of the error-proofing check task differs from that of the target country query task: the target country query task is used to continue attempting to obtain the target country information corresponding to the vehicle, while the error-proofing check task is used to identify vehicles for which target country information has been unavailable for an extended period. Therefore, when vehicle identification information has entered the target country query process but the corresponding target country information has not yet been obtained, triggering the error-proofing check task daily can continuously determine whether the vehicle is in an abnormal state where target country determination has been unavailable for an extended period.

[0116] Based on the aforementioned error-proofing inspection task, it is determined whether the vehicle identification information has not obtained the corresponding target country information after a preset number of days. Specifically, the production server determines the duration for which the vehicle identification information in the current error-proofing inspection task has not obtained information from the target country, and compares the determined duration with a preset number of days.

[0117] In this embodiment, "failure to obtain corresponding target country information after a preset number of days" means that from the time the vehicle enters the target country information missing state, after the preset number of days, the production server still has not obtained the target country information corresponding to the vehicle identification information. By setting the preset number of days, vehicles that are in a normal waiting state for a short period of time because the target country information has not yet been formed can be distinguished from vehicles that cannot obtain target country information for a long period of time.

[0118] For example, in one specific implementation, the preset number of days can be set to 15 days. When the production server performs a daily error-proofing check, it filters vehicle identification information that has not obtained target country information for more than 15 days. This ensures that the error-proofing check does not immediately generate an anomaly alarm after the first failed query for target country information, but rather initiates anomaly processing only after the corresponding vehicle has remained in a state of missing target country information for a set period. This processing can be achieved by using a daily scheduled task to filter VINs that have not obtained a sales country information for more than 15 days, thereby identifying data that has remained undistributed due to the long-term lack of sales country information.

[0119] If the vehicle identification information has not exceeded the preset number of days, the current error prevention check will not identify the vehicle identification information as abnormal vehicle identification information. The vehicle identification information will continue to be kept in the corresponding check object for re-judgment when the subsequent error prevention check task is triggered again.

[0120] If the vehicle identification information fails to obtain the corresponding target country information after the preset number of days, the vehicle identification information will be identified as abnormal vehicle identification information. Specifically, when the production server determines, based on the previous step's judgment, that the current vehicle identification information has not obtained target country information for more than a preset number of days, it indicates that the vehicle has failed to generate the target country information required for subsequent regional distribution for an extended period of time. Therefore, the vehicle identification information is further identified as abnormal vehicle identification information from ordinary target country information missing objects.

[0121] The abnormal vehicle identification information is used to characterize an anomaly where the current vehicle has a long-term lack of target country information, and serves as input for generating subsequent alarm information. Therefore, the judgment result of "whether it exceeds the preset number of days" obtained in the previous step directly determines whether the current vehicle identification information enters the anomaly handling process.

[0122] An alarm message is generated based on the abnormal vehicle identification information, and the alarm message is sent to the corresponding responsible person.

[0123] Specifically, the production server generates alarm information corresponding to the identified abnormal vehicle based on the identified abnormal vehicle information. The alarm information indicates that the corresponding vehicle has not obtained the target country information for more than a preset number of days, thus indicating that the vehicle may be unable to continue normal regional distribution due to the long-term lack of target country information.

[0124] After generating the alarm information, the production server sends the alarm information to the corresponding responsible person, enabling the responsible person to identify the vehicle that needs further verification based on the alarm information. The alarm information should at least enable the responsible person to identify the abnormal vehicle identification information and the corresponding missing target country information; this embodiment does not limit the specific message format and specific sending channel used for the alarm information.

[0125] Through the above processing, the error prevention inspection task does not execute abnormal alarms for all vehicles. Instead, it first uses the vehicle identification information that has not yet obtained the target country information as the inspection object, and determines the duration of the missing target country information each day. If the duration does not exceed the preset number of days, the inspection continues. If the duration exceeds the preset number of days, the corresponding vehicle identification information is identified as abnormal vehicle identification information, and further alarm information is generated and sent to the corresponding responsible person.

[0126] Therefore, this embodiment forms a continuous anomaly detection process of "target country information not obtained - adding to the inspection object - triggering daily error prevention checks - judging the duration of the missing information - determining the abnormal vehicle identification information after exceeding the preset number of days - generating and sending alarm information". This enables periodic screening and anomaly alerts for vehicles with long-term missing target country information, avoiding the corresponding vehicle terminal from being in a state of being unable to complete regional distribution due to the inability to determine the target country information for a long time.

[0127] A cross-regional distribution device for an in-vehicle terminal, used to execute the method for distributing in-vehicle terminal data, comprising: The equipment data acquisition module is used to acquire equipment data generated by the vehicle terminal during the production stage and the vehicle installation and network access stage; The vehicle identification information acquisition module is used to acquire the vehicle identification information corresponding to the vehicle terminal after the vehicle terminal is installed in the vehicle; The target country determination module is used to request and determine the target country information of the vehicle from the vehicle manufacturer's server based on the vehicle identification information. An undistributed data determination module is used to determine undistributed data based on the device data; The target server determination module is used to determine the target regional business server among multiple regional business servers based on the target country information. The data distribution module is used to send the undistributed data to the target area service server; The distribution status update module is used to obtain the processing result returned by the target area business server and update the distribution status of the undistributed data based on the processing result.

[0128] A computer device includes a memory and a processor, wherein the memory stores computer-readable instructions, and the processor executes the computer-readable instructions to implement the steps of the method for distributing data from a vehicle terminal.

[0129] A computer-readable storage medium storing computer-readable instructions, which, when executed by a processor, implement the steps of the method for distributing data from an in-vehicle terminal.

[0130] It should also be noted that, in this document, relational terms such as "first" and "second" are used only to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0131] The above description of the disclosed embodiments enables those skilled in the art to make or use this application. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of this application. Therefore, this application is not to be limited to the embodiments shown herein, but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A method for distributing data from a vehicle-mounted terminal, characterized in that, include: Acquire device data generated by the vehicle-mounted terminal during the production and installation / network connection phases; After the vehicle terminal is installed in the vehicle, obtain the vehicle identification information corresponding to the vehicle terminal; Based on the vehicle identification information, request and determine the vehicle's target country information from the vehicle manufacturer's server; Based on the device data, undistributed data is determined; Based on the target country information, the target region business server is determined from multiple regional business servers. The undistributed data is sent to the target area service server; Obtain the processing result returned by the target area service server, and update the distribution status of the undistributed data based on the processing result.

2. The method for distributing vehicle terminal data according to claim 1, characterized in that, The acquisition of device data generated by the vehicle-mounted terminal during the production and installation / network registration phases includes: During the production stage of the vehicle-mounted terminal, the vehicle-mounted terminal identifier and communication module identifier reported by the production line tools are obtained as equipment data for the production stage. When the vehicle terminal is installed and powered on and the embedded user identification module is successfully registered on the network, the vehicle terminal identifier, communication module identifier, embedded user identification module identifier, integrated circuit card identifier and mobile country code reported by the vehicle terminal are obtained as equipment data during the vehicle installation and network registration stage. Based on the equipment data from the production stage and the equipment data from the vehicle installation and network setup stage, the equipment data corresponding to the vehicle terminal is obtained.

3. The method for distributing vehicle terminal data according to claim 1, characterized in that, The step of requesting and determining the vehicle's target country information from the vehicle manufacturer's server based on the vehicle identification information includes: Based on the vehicle identification information, a target country query request is sent to the vehicle manufacturer's server, and the query results returned by the vehicle manufacturer's server are obtained; If the target country information is not obtained based on the query results, the vehicle identification information is added to the target country query task. When the target country query task is triggered, the target country query request is sent again to the vehicle manufacturer's server based on the vehicle identification information; If the target country information is obtained based on the returned query results, then the target country information is saved.

4. The method for distributing vehicle terminal data according to claim 2, characterized in that, The determination of undistributed data based on the device data includes: Determine whether there is any data in the device data that has not yet been distributed to the regional service server; If it exists, the data that has not yet been distributed to the regional service server is identified as the undistributed data; If it does not exist, the current distribution process of the vehicle terminal will end.

5. The method for distributing vehicle terminal data according to claim 4, characterized in that, Each of the multiple regional service servers corresponds to a different country or region, and the multiple regional service servers do not communicate with each other. Based on the target country information, the target regional service server is determined from multiple regional service servers, including: The target country corresponding to the vehicle terminal is determined based on the target country information; Based on the correspondence between the target country and the countries or regions each of the multiple regional service servers is responsible for, the regional service server responsible for the target country is determined, and the determined regional service server is used as the target regional service server.

6. The method for distributing vehicle terminal data according to claim 1, characterized in that, After sending the undistributed data to the target area service server, the process further includes: The undistributed data is received by the target area service server, and the corresponding device data in the target area service server is added or updated based on the undistributed data. After the addition or update is completed, the processing result representing the completion of data processing is generated and returned by the target area business server.

7. The method for distributing vehicle terminal data according to claim 3, characterized in that, After adding the vehicle identification information to the target country query task, the method further includes: Trigger a daily error-proofing inspection task for vehicle identification information that has not obtained target country information; Based on the aforementioned error-proofing inspection task, it is determined whether the vehicle identification information has not obtained the corresponding target country information after a preset number of days. If the vehicle identification information fails to obtain the corresponding target country information after the preset number of days, the vehicle identification information will be identified as abnormal vehicle identification information. An alarm message is generated based on the abnormal vehicle identification information, and the alarm message is sent to the corresponding responsible person.

8. A cross-regional data distribution device for a vehicle-mounted terminal, used to execute the data distribution method for the vehicle-mounted terminal according to any one of claims 1 to 7, characterized in that, include: The equipment data acquisition module is used to acquire equipment data generated by the vehicle terminal during the production stage and the vehicle installation and network access stage; The vehicle identification information acquisition module is used to acquire the vehicle identification information corresponding to the vehicle terminal after the vehicle terminal is installed in the vehicle; The target country determination module is used to request and determine the target country information of the vehicle from the vehicle manufacturer's server based on the vehicle identification information. An undistributed data determination module is used to determine undistributed data based on the device data; The target server determination module is used to determine the target regional business server among multiple regional business servers based on the target country information. The data distribution module is used to send the undistributed data to the target area service server; The distribution status update module is used to obtain the processing result returned by the target area business server and update the distribution status of the undistributed data based on the processing result.

9. A computer device, characterized in that, The device includes a memory and a processor, wherein the memory stores computer-readable instructions, and the processor executes the computer-readable instructions to implement the steps of the method for distributing vehicle terminal data as described in any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer-readable instructions, which, when executed by a processor, implement the steps of the method for distributing vehicle terminal data as described in any one of claims 1 to 7.

Images