Methods, devices, computer equipment and storage media for writing and cross-border monitoring

By acquiring the network registration data and target country information of the vehicle terminal, determining and executing empty writes, and monitoring cross-border status, the problem of complex business status management in cross-regional use of vehicle terminals is solved, and effective status management and anomaly judgment are achieved.

CN122952342BActive Publication Date: 2026-11-17HANGZHOU HUIJIE AUTOMOBILE TECHNOLOGY CO LTD
View PDF 2 Cites 0 Cited by

Patent Information

Application Number
CN202611433145.X
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2026-09-16
Publication Date
2026-11-17
Estimated Expiration
2046-09-16

AI Technical Summary

Technical Problem

When vehicle-mounted terminals are used across regions, their service status is difficult to manage effectively, leading to increased complexity in communication resource configuration and service management.

Method used

By acquiring the first network registration data and target country information reported by the target vehicle terminal after it has registered with the network, its empty write status is determined, an empty write request is generated and the empty write is executed, and after confirming that the empty write is completed, its cross-border status and abnormal status are monitored to form a continuous processing link.

Benefits of technology

This improves the effectiveness of business status management during cross-regional use of vehicle-mounted terminals, ensures seamless integration between write-free processing and cross-border network monitoring, and reduces misjudgments.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN122952342B_ABST
    Figure CN122952342B_ABST
Patent Text Reader

Abstract

This invention discloses a method, apparatus, computer equipment, and storage medium for empty write and cross-border monitoring. The method is applied to a back-end business system including a first business processing side and a second business processing side. The first business processing side determines whether an empty write needs to be performed based on the first registration data after the target vehicle terminal registers with the network and the target country information. After performing the empty write, it confirms whether the empty write is complete based on the second registration data. After confirming the completion of the empty write, the second business processing side determines the vehicle's cross-border status and status time information based on subsequent monitoring registration data and sales country information. It determines the cross-border time interval based on the status time information and determines abnormal cross-border registration status based on the cross-border time interval within a preset statistical period. This invention enables the coordinated integration of empty write processing and cross-border registration monitoring.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This application relates to the field of vehicle-to-everything (V2X) communication, and in particular to a method, apparatus, computer equipment, and storage medium for writing and cross-border monitoring. Background Technology

[0002] With the development of vehicle-to-everything (V2X) technology, in-vehicle terminals are widely used in vehicle communication and related V2X services. For vehicles produced, transported, and sold in different countries or regions, the mobile communication network environment in which the in-vehicle terminal is located may change during the cross-regional transfer and use of the vehicle, and the corresponding communication resources and service status may also change accordingly.

[0003] Existing vehicle-mounted terminal-related services typically involve different stages, including vehicle transportation, communication resource allocation, and communication services after the vehicle is put into use. The business information and processing entities differ at each stage. As vehicles move across countries or regions, the communication service status of the vehicle-mounted terminal may also change accordingly, increasing the complexity of status management for these services. Existing methods struggle to grasp the service status of vehicle-mounted terminals in a timely and accurate manner during cross-regional use, thus impacting the management of related services.

[0004] In view of the above, this application is hereby submitted. Summary of the Invention

[0005] The purpose of this application is to provide a method, apparatus, computer equipment, and storage medium for monitoring empty writes and cross-border operations, so as to solve the technical problem that it is difficult to effectively manage the service status of vehicle terminals during cross-regional use.

[0006] To address the aforementioned technical problems, this application provides a method for detecting empty writes and cross-border operations, employing the following technical solution: A method for detecting empty writes and cross-border operations, applied to a back-end business system, the back-end business system including a first business processing side and a second business processing side, includes the following steps: The first service processing side obtains the first network registration data reported by the target vehicle terminal after it registers with the network, as well as the target country information corresponding to the target vehicle terminal; The first service processing side determines the first empty write state of the target vehicle terminal based on the first network registration data, and determines whether an empty write needs to be performed based on the first empty write state, the first network registration data, and the target country information; When it is determined that an empty write needs to be performed, the first service processing side sends an empty write request to the empty write server so that the empty write server performs an empty write on the target vehicle terminal. When the target vehicle terminal re-registers after performing a blank write, the first service processing side obtains the second registration data reported by the target vehicle terminal, and determines whether the target vehicle terminal has completed the blank write based on the second registration data. After the first service processing side determines that the target vehicle terminal has completed the empty write, the second service processing side obtains the monitoring network registration data reported by the target vehicle terminal during the subsequent network registration process and the sales country information corresponding to the target vehicle terminal, and determines the cross-border status of the vehicle corresponding to the target vehicle terminal and the corresponding status time information based on the monitoring network registration data and the sales country information. The second service processing side determines the cross-border time interval of the vehicle based on the status time information, and determines the cross-border network abnormal status of the vehicle based on the cross-border time interval within a preset statistical period.

[0007] Furthermore, before the first service processing side obtains the first network registration data reported by the target vehicle terminal after network registration and the target country information corresponding to the target vehicle terminal, it includes: The first service processing side obtains the embedded card identifier corresponding to the target vehicle terminal; The first service processing side sends the embedded card identifier and the target country information to the card number supply side, so that the card number supply side prepares card number resources corresponding to the target country information before the target vehicle terminal arrives in the target country.

[0008] Furthermore, the first network registration data includes an embedded card identifier, a first card identification code, and a first mobile country code; The first service processing side determines the first empty write state of the target vehicle terminal based on the first network registration data, and determines whether an empty write needs to be performed based on the first empty write state, the first network registration data, and the target country information, including: The first service processing side checks the first empty write state of the target vehicle terminal based on the embedded card identifier. The first empty write state includes an empty write completed state, an empty write in progress state, and an empty write not started state. When the first empty write state is in the empty write state, the first service processing side checks whether the target vehicle terminal has completed the empty write based on the first card identification code, and determines that an empty write needs to be performed if the empty write has not been completed. When the first empty write state is the inactive empty write state, the first service processing side determines the first registered country based on the first mobile country code, and determines whether the registered country conditions of the target country are met based on the first registered country and the target country information. If the registered country conditions of the target country are met, it is determined that an empty write needs to be performed.

[0009] Furthermore, the step of sending an empty write request to the empty write server when it is determined that an empty write is needed, so that the empty write server performs an empty write on the target vehicle terminal, includes: The first service processing side generates the empty write request based on the embedded card identifier, the first card identification code and the first mobile country code, and sends the empty write request to the empty write server; The first service processing side obtains the empty write result returned by the empty write server in response to the empty write request, and saves the empty write result in correspondence with the target vehicle terminal.

[0010] Furthermore, the second network registration data includes an embedded card identifier and a second card identification code; When the target vehicle terminal re-registers after performing a null write, the first service processing side obtains the second registration data reported by the target vehicle terminal, and determines whether the target vehicle terminal has completed the null write based on the second registration data, including: The first service processing side checks the second empty write state of the target vehicle terminal after it re-enters the network based on the embedded card identifier; When the second write state is in the write state, the first service processing side checks whether the target vehicle terminal has completed the write based on the second card identification code, and determines that the target vehicle terminal has completed the write when the check result indicates that the write has been completed.

[0011] Furthermore, after the first service processing side determines that the target vehicle terminal has completed the no-write operation, the second service processing side obtains the monitoring network registration data reported by the target vehicle terminal during the subsequent network registration process and the sales country information corresponding to the target vehicle terminal, and determines the cross-border status and corresponding status time information of the vehicle corresponding to the target vehicle terminal based on the monitoring network registration data and the sales country information, including: When the target vehicle terminal restarts or switches operators and re-enters the network, the second service processing side obtains the monitoring network entry data reported by the target vehicle terminal, and the monitoring network entry data includes the monitoring country code; The second service processing side determines the country of the monitored network based on the monitored mobile country code; When the monitored country of residence is inconsistent with the country of sale information, the second business processing side determines that the vehicle is in a cross-border state and records the cross-border time point; when the monitored country of residence is consistent with the country of sale, the second business processing side determines that the vehicle is in a non-cross-border state and records the non-cross-border time point. The status time information includes the cross-border time point and the non-cross-border time point.

[0012] Furthermore, the second service processing side determines the cross-border time interval of the vehicle based on the status time information, and determines the cross-border network access anomaly status of the vehicle based on the cross-border time interval within a preset statistical period, including: The second business processing side determines the cross-border time interval of the vehicle based on the cross-border time point and the non-cross-border time point; The second business processing side determines the total cross-border time of the vehicle based on each of the cross-border time intervals within the preset statistical period; The second business processing side determines whether the vehicle meets the preset cross-border abnormal conditions based on the total cross-border time, and if the preset cross-border abnormal conditions are met, determines that the vehicle is in a cross-border network abnormal state.

[0013] To address the aforementioned technical problems, this application also provides a device for detecting empty writes and cross-border activity, employing the following technical solution: A device for monitoring write operations and cross-border operations includes a first business processing side and a second business processing side; The first business processing side includes a first acquisition module, an empty write judgment module, an empty write request module and an empty write confirmation module, wherein the first acquisition module is used to acquire the first network registration data reported by the target vehicle terminal after it registers with the network and the target country information corresponding to the target vehicle terminal; The empty write judgment module is used to determine the first empty write state of the target vehicle terminal based on the first network data, and to determine whether an empty write needs to be performed based on the first empty write state, the first network data and the target country information. The empty write request module is used to send an empty write request to the empty write server when it is determined that an empty write needs to be performed, so that the empty write server performs an empty write on the target vehicle terminal. The empty write confirmation module is used to obtain the second network registration data reported by the target vehicle terminal when the target vehicle terminal re-registers after performing an empty write, and to determine whether the target vehicle terminal has completed the empty write based on the second network registration data. The second business processing side includes a cross-border monitoring module and an anomaly determination module. The cross-border monitoring module is used to obtain the monitoring network registration data reported by the target vehicle terminal during the subsequent network registration process and the sales country information corresponding to the target vehicle terminal after determining that the target vehicle terminal has completed the empty write. Based on the monitoring network registration data and the sales country information, the cross-border status of the vehicle corresponding to the target vehicle terminal and the corresponding status time information are determined. The anomaly determination module is used to determine the cross-border time interval of the vehicle based on the status time information, and to determine the cross-border network abnormal status of the vehicle based on the cross-border time interval within a preset statistical period.

[0014] To address the aforementioned technical problems, this application also provides a computer device that employs the following technical solution: A computer device includes a memory and a processor. The computer device is used as a first business processing side or a second business processing side in the background business system. The memory stores computer-readable instructions. When the processor executes the computer-readable instructions, it implements the steps performed by the first business processing side or the second business processing side in the empty write and cross-border monitoring method described above.

[0015] To address the aforementioned technical problems, this application also provides a computer-readable storage medium, employing the technical solution described below: A computer-readable storage medium storing computer-readable instructions, which, when executed by one or more processors, implement the steps of the no-write and cross-border monitoring method as described above.

[0016] Compared with the prior art, the embodiments of this application have the following main advantages: The empty write and cross-border monitoring method disclosed in this application obtains the first network registration data reported by the target vehicle terminal after it has registered with the network, along with the corresponding target country information. It first determines the first empty write status of the target vehicle terminal based on the first network registration data, and then combines the first empty write status, the first network registration data, and the target country information to determine whether an empty write needs to be executed. This ensures that the initiation of the empty write request is based on the judgment result of the target vehicle terminal's current empty write status and network registration situation, rather than directly triggering the empty write after the vehicle terminal has registered with the network. This improves the matching degree between the empty write processing and the actual business status of the target vehicle terminal. After determining that an empty write needs to be executed and that the empty write server executes the empty write, the second network registration data reported by the target vehicle terminal after re-registration is further used to confirm the completion of the empty write. This allows the empty write execution result to be further verified through the re-registration data after the empty write, thus forming a continuous processing process from empty write status judgment, empty write requirement determination, empty write execution to empty write completion confirmation. After confirming that the target vehicle terminal has completed the empty write operation, the monitoring and network registration data reported during its subsequent network registration process, along with the corresponding sales country information, are obtained. Based on this, the vehicle's cross-border status and corresponding status time information are determined. Furthermore, the status time information is used to form a cross-border time interval, transforming the discrete cross-border status reflected in a single network registration into time-continuous cross-border network registration information. On this basis, cross-border network registration anomalies are determined by processing the cross-border time interval within a preset statistical period. This allows anomaly judgment to be based on the vehicle's cross-border network registration status within a certain time range, rather than solely on a single network registration status. Therefore, this invention forms a seamless processing link between the empty write processing of the vehicle terminal and the cross-border network registration monitoring after the empty write is completed. It utilizes network registration data generated at different processing stages to complete empty write judgment, empty write completion confirmation, and cross-border network registration anomaly judgment, improving the effectiveness of business status management during the cross-regional use of vehicle terminals. Attached Figure Description

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

[0018] Figure 1 This is an exemplary system architecture diagram to which this application can be applied; Figure 2 This is a flowchart of an embodiment of the blank writing and cross-border monitoring method according to this application; Figure 3 This is a schematic diagram of a structure of an embodiment of the blank writing and cross-border monitoring device according to this application; Figure 4This is a schematic diagram of the structure of one embodiment of the computer device according to this application. Detailed Implementation

[0019] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application pertains; the terminology used herein in the specification of the application is for the purpose of describing particular embodiments only and is not intended to be limiting of the application; the terms "comprising" and "having," and any variations thereof, in the specification, claims, and foregoing drawings of this application, are intended to cover non-exclusive inclusion. The terms "first," "second," etc., in the specification, claims, or foregoing drawings of this application are used to distinguish different objects, not to describe a particular order.

[0020] In this document, the term "embodiment" means that a particular feature, structure, or characteristic described in connection with an embodiment may be included in at least one embodiment of this application. The appearance of this phrase in various places throughout the specification does not necessarily refer to the same embodiment, nor is it a separate or alternative embodiment mutually exclusive with other embodiments. It will be explicitly and implicitly understood by those skilled in the art that the embodiments described herein can be combined with other embodiments.

[0021] To enable those skilled in the art to better understand the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings.

[0022] like Figure 1 As shown, system architecture 100 may include terminal devices 101, 102, and 103, a network 104, and a server 105. Network 104 serves as the medium for providing communication links between terminal devices 101, 102, and 103 and server 105. Network 104 may include various connection types, such as wired or wireless communication links, or fiber optic cables, etc.

[0023] Users can use terminal devices 101, 102, and 103 to interact with server 105 via network 104 to receive or send messages, etc. Various communication client applications can be installed on terminal devices 101, 102, and 103, such as web browser applications, shopping applications, search applications, instant messaging tools, email clients, social media platform software, etc.

[0024] Terminal devices 101, 102, and 103 can be various electronic devices with displays and web browsing capabilities, including but not limited to smartphones, tablets, e-book readers, MP3 (Moving Picture Experts Group Audio Layer III) players, MP4 (Moving Picture Experts Group Audio Layer IV) players, laptops, and desktop computers, etc.

[0025] Server 105 can be a server that provides various services, such as a backend server that supports the pages displayed on terminal devices 101, 102, and 103.

[0026] It should be noted that the empty write and cross-border monitoring method provided in this application embodiment is applied to a back-end business system, which includes a first business processing side and a second business processing side; correspondingly, the first business processing side and the second business processing side in the empty write and cross-border monitoring device can be deployed on different servers that communicate with each other.

[0027] It should be understood that Figure 1 The number of terminal devices, networks, and servers shown is merely illustrative. Depending on implementation needs, any number of terminal devices, networks, and servers can be included.

[0028] Continue to refer to Figure 2 This document illustrates a flowchart of an embodiment of the empty write and cross-border monitoring method according to this application. The empty write and cross-border monitoring method is used to monitor the empty write process of a target vehicle-mounted terminal and its cross-border network registration status after the empty write is completed. In this application, the target vehicle-mounted terminal can be a vehicle-mounted TBOX (Telematics Box, vehicle communication terminal), used to report corresponding network registration data after the vehicle registers or re-registers. The TMS can be a production or terminal management server used to perform empty write service processing, used to receive and save or update the data reported by the target vehicle-mounted terminal, and to perform empty write status checks, empty write condition judgments, empty write request sending, and empty write result saving. The TSP can be a regional service server used to receive data reported by the target vehicle-mounted terminal during its subsequent network registration process after the empty write is completed, and to perform cross-border vehicle status monitoring based on the data.

[0029] The target vehicle terminal can be configured with an embedded Subscriber Identity Module (eSIM). The embedded card identifier can be an EID, used to identify the embedded card corresponding to the target vehicle terminal; the card identification code can be an ICCID, used to identify the corresponding card resource; and the mobile country code can be an MCC, used to represent the country information corresponding to the network currently hosted by the target vehicle terminal.

[0030] The empty write described in this application refers to the empty write service processing performed by the empty write server on the target vehicle terminal. After receiving the empty write request corresponding to the target vehicle terminal, the empty write server performs the corresponding empty write processing on the target vehicle terminal and returns the corresponding empty write result. This application does not limit the specific data content or specific writing method written during the empty write process.

[0031] In this embodiment, the backend business system includes a first business processing side and a second business processing side. The first business processing side is used to perform business processing during the empty write processing phase, and the second business processing side is used to perform cross-border monitoring business processing after the empty write is completed. In one implementation, the first business processing side can correspond to the TMS side, used to receive data reported by the target vehicle terminal, determine the empty write status and empty write conditions, and send an empty write request to the empty write server; the second business processing side can correspond to the TSP side, used to receive data reported by the target vehicle terminal during its subsequent network registration process after the empty write is completed, and monitor the cross-border network registration status of the vehicle based on the data. The first business processing side and the second business processing side can be deployed on different servers and establish business connection through the backend business system. This method includes the following steps: Step S201: The first service processing side obtains the first network registration data reported by the target vehicle terminal after it registers with the network, as well as the target country information corresponding to the target vehicle terminal.

[0032] In this embodiment, the first service processing side and the second service processing side can interact with the target vehicle terminal and the corresponding server through wired or wireless networks, and the specific communication connection method is not limited.

[0033] In this embodiment, the first network registration data is the data reported by the target vehicle terminal after registering during the no-write judgment phase. It reflects the current network registration status of the target vehicle terminal and serves as the data basis for determining the current no-write status of the target vehicle terminal and whether no-write needs to be performed. The target country information is used to characterize the target country corresponding to the vehicle of the target vehicle terminal in the current business process.

[0034] In one application scenario, after a vehicle arrives in the target country, due to changes in the mobile communication network environment, the target vehicle terminal registers or re-registers with the network. After successful registration, it reports the data corresponding to the current registration to the TMS side. The TMS side receives the first registration data and obtains the target country information corresponding to the target vehicle terminal for subsequent empty write judgment.

[0035] In step S202, the first service processing side determines the first empty write state of the target vehicle terminal based on the first network registration data, and determines whether an empty write needs to be performed based on the first empty write state, the first network registration data, and the target country information.

[0036] In this embodiment, the first empty write state is used to characterize the state of the target vehicle terminal in the current empty write processing stage. The TMS side checks the current empty write state of the target vehicle terminal based on the first network registration data, and uses the checked state as the first empty write state.

[0037] Furthermore, based on the first empty write state, the first network registration data, and the target country information, it is determined whether the target vehicle terminal needs to perform an empty write operation. Therefore, the first network registration data does not directly trigger an empty write operation after it is acquired. Instead, it is first used to determine the current empty write state of the target vehicle terminal, and then, in combination with the first empty write state, the current network registration status, and the target country information, it is determined whether an empty write operation needs to be performed on the target vehicle terminal.

[0038] The specific method for determining the first empty write state and the specific usage of the first registered data under different first empty write states can be set according to the empty write service state of the target vehicle terminal. This embodiment does not make specific limitations on this.

[0039] In step S203, when it is determined that an empty write needs to be performed, the first service processing side sends an empty write request to the empty write server so that the empty write server performs an empty write on the target vehicle terminal.

[0040] In this embodiment, after receiving an empty write request, the empty write server performs an empty write on the target vehicle terminal corresponding to the empty write request, enabling the target vehicle terminal to complete the processing corresponding to the current empty write service. The empty write server can be any server capable of providing vehicle terminal empty write services, and its specific deployment method is not limited.

[0041] The empty write described in this embodiment is an empty write process performed on the user identification-related resources corresponding to the target vehicle terminal. The specific data content, writing method, empty write command format, and specific communication method between the empty write server and the target vehicle terminal during the empty write process can be set according to the actual empty write service, and are not specifically limited here.

[0042] Step S204: When the target vehicle terminal re-registers after performing a blank write, the first service processing side obtains the second registration data reported by the target vehicle terminal and determines whether the target vehicle terminal has completed the blank write based on the second registration data.

[0043] It should be noted that the first network registration data and the second network registration data correspond to different processing stages. The first network registration data corresponds to the empty write judgment stage before the target vehicle terminal performs an empty write, and is used to determine the first empty write status and whether an empty write needs to be performed; the second network registration data corresponds to the empty write confirmation stage after the target vehicle terminal performs an empty write and re-registers, and is used to determine whether the target vehicle terminal has completed the empty write.

[0044] Therefore, the terms "first" and "second" in this embodiment are mainly used to distinguish the network data obtained at different stages, and do not mean that all data content in the first and second network data must change.

[0045] Specifically, after the empty write server performs an empty write on the target vehicle terminal, it uses the second network registration data generated by the target vehicle terminal's re-registration to reconfirm the completion of the empty write. Through this process, the empty write process of the target vehicle terminal is formed as follows: The process involves a continuous chain of empty write request assessment, empty write execution, re-registration, and empty write completion confirmation, rather than ending the empty write process immediately after the empty write request is issued.

[0046] The specific method for determining whether the target vehicle terminal has completed the empty write based on the second network data can be set according to the status information in the empty write service. This embodiment does not make specific limitations on this.

[0047] Step S205: After the first service processing side determines that the target vehicle terminal has completed the empty write, the second service processing side obtains the monitoring network registration data reported by the target vehicle terminal during the subsequent network registration process and the sales country information corresponding to the target vehicle terminal, and determines the cross-border status of the vehicle corresponding to the target vehicle terminal and the corresponding status time information based on the monitoring network registration data and the sales country information.

[0048] Among them, the monitoring network registration data refers to the network registration data generated and reported during the subsequent operation of the vehicle after the target vehicle terminal has completed its no-load write and when it registers or re-registers. The monitoring network registration data is used to reflect the network registration status during the subsequent operation of the vehicle.

[0049] Therefore, the three types of network-registered data in this embodiment are distinguished according to the processing stage, wherein: The first set of network data corresponds to the empty write state before empty write and the empty write demand judgment stage. The second set of network-based data corresponds to the empty write completion confirmation stage after the empty write is executed; The monitoring of on-site data corresponds to the cross-border on-site monitoring phase of vehicles after the empty write is completed.

[0050] The country of sale information is used to characterize the country of sale of the vehicle corresponding to the target vehicle terminal. In this embodiment, the target country information is mainly used for the determination during the empty write phase, while the country of sale information is mainly used for the determination of the cross-border status of the target vehicle terminal after the empty write is completed. Both are used as basic data for their respective processing phases.

[0051] After the second business processing side obtains the monitoring network data and the sales country information, it determines the cross-border status of the vehicle corresponding to the target vehicle terminal and the status time information corresponding to the cross-border status based on the monitoring network data and the sales country information.

[0052] Among them, the cross-border status is used to characterize the current network status of the target vehicle terminal relative to the country of vehicle sale, and the status time information is used to characterize the time information corresponding to the corresponding cross-border status.

[0053] During subsequent vehicle operation, the target vehicle-mounted terminal can re-enter the network multiple times or re-enter the network as the network environment changes. Accordingly, monitoring network entry data corresponding to different network entry times can be acquired. For each acquired monitoring network entry data, the corresponding cross-border status is determined, and status time information corresponding to different cross-border statuses is generated.

[0054] For example, after a vehicle restarts or a mobile communication operator switch occurs, the target vehicle terminal can re-register and report its current registration data, allowing the TSP to determine the vehicle's current cross-border status based on the new registration data. After completing the empty write operation, the vehicle terminal can continue to report relevant registration data after re-registering, restarting, or switching operators.

[0055] Step S206: The second service processing side determines the cross-border time interval of the vehicle based on the status time information, and determines the cross-border network abnormal status of the vehicle based on the cross-border time interval within a preset statistical period.

[0056] Cross-border time intervals are used to characterize the duration of a vehicle's cross-border parking status. By utilizing the state time information corresponding to different parking statuses to form cross-border time intervals, discrete cross-border statuses formed at different parking times can be further transformed into cross-border parking information with temporal continuity.

[0057] As vehicles operate, one or more cross-border time intervals can be obtained. Statistical processing is performed on the cross-border time intervals formed within a preset statistical period, and the abnormal cross-border network status of vehicles is determined based on the cross-border time intervals within the preset statistical period.

[0058] The preset statistical period is the time range used to evaluate the cross-border network presence of vehicles over a certain period. By comprehensively processing the cross-border time intervals of vehicles within the preset statistical period, it is possible to avoid directly determining whether a vehicle has an abnormal cross-border network presence based solely on a single network presence status. Instead, it is possible to determine whether an abnormal cross-border network presence exists by combining the vehicle's cross-border network presence within a certain time range.

[0059] In one implementation, a periodic task can be used to statistically analyze the cross-border time intervals formed by vehicles within a preset statistical period, and determine whether the vehicle is in an abnormal cross-border network status based on the statistical results. When it is determined that a vehicle is in an abnormal cross-border network status, this abnormal status can be used for subsequent anomaly handling.

[0060] The specific methods for forming cross-border time intervals, the specific length of preset statistical periods, and the specific judgment conditions for abnormal cross-border network status can be set according to the needs of cross-border monitoring business, and no specific restrictions are made here.

[0061] In the above manner, during the empty write processing stage of the target vehicle terminal, the first network registration data is used to determine the empty write status of the target vehicle terminal and whether an empty write needs to be performed. After the empty write is performed, the second network registration data generated by re-registration is used to confirm whether the target vehicle terminal has completed the empty write. After confirming that the target vehicle terminal has completed the empty write, the cross-border status and status time information of the vehicle are determined by the monitoring network registration data continuously obtained during the subsequent operation of the vehicle. The cross-border time interval is formed by the status time information. Finally, the cross-border network registration abnormal status is determined based on the cross-border time interval within the preset statistical period, so that the empty write processing and the cross-border network registration monitoring after the empty write is completed form a continuous processing flow.

[0062] In some optional implementations of this embodiment, the target country information is obtained by the first service processing side before the target vehicle terminal arrives in the target country, and further includes: The first service processing side obtains the embedded card identifier corresponding to the target vehicle terminal; In this embodiment, the target vehicle terminal can be a vehicle TBOX, and the target vehicle terminal is equipped with an embedded user identification module (eSIM) for network registration and participation in the no-write service; the embedded card identifier is used to identify the embedded card corresponding to the target vehicle terminal. In one embodiment, the embedded card identifier can be an EID.

[0063] The first service processing side sends the embedded card identifier and the target country information to the card number supply side, so that the card number supply side prepares card number resources corresponding to the target country information before the target vehicle terminal arrives in the target country.

[0064] In one implementation, the card number resource preparation process is initiated by the TMS side. During vehicle transport, the TMS side acquires the EID and target country information corresponding to the target vehicle terminal and sends these information to the card number supplier. Based on the received information, the card number supplier prepares local card number resources for the target country in advance for the corresponding target vehicle terminal.

[0065] Among them, the embedded card identifier is used to distinguish the target vehicle terminal corresponding to this resource preparation, and the target country information is used to determine the country corresponding to the card number resource that needs to be prepared, thereby establishing a correspondence between the target vehicle terminal and the card number resource preparation process of its target country.

[0066] After the card number supply side completes the preparation of the corresponding card number resources, the vehicle continues to be transported to the target country. After the target vehicle terminal arrives in the target country and completes network registration or re-registers, it then enters the first network registration data reporting and subsequent empty write judgment process. Therefore, the preparation of target country card number resources occurs before the vehicle arrives in the target country and serves as a pre-processing step for subsequent empty write operations.

[0067] In this embodiment, card number resources can be understood as card resources prepared in advance by the card number supplier for the target country and used for subsequent blank write operations. The specific content of the card number resources, the specific generation method of the card number resources, and the specific binding method between the embedded card identifier and the card number resources are not specifically limited here.

[0068] In some optional implementations of this embodiment, the first network registration data includes an embedded card identifier, a first card identification code, and a first mobile country code; In this embodiment, the first network registration data is the data reported by the target vehicle terminal after completing network registration during the no-write judgment phase, including an embedded card identifier, a first card identification code, and a first mobile country code. The embedded card identifier can be an EID, used to identify the embedded card corresponding to the target vehicle terminal; the first card identification code can be an ICCID, used to characterize the card identification information corresponding to the target vehicle terminal in the current network registration phase; and the first mobile country code can be an MCC, used to characterize the country information corresponding to the mobile network currently registered by the target vehicle terminal. These different data in the first network registration data are used for subsequent judgment processing under different no-write states. The data reported by the target vehicle terminal after network registration may include EID, ICCID, and MCC, and are used for no-write state checks, no-write completion checks, and target country network registration checks, respectively.

[0069] It should be noted that the "first" in "first card identification code" and "first mobile country code" is used to indicate that the corresponding data was obtained in the first network registration stage before the target vehicle terminal performs this empty write, so as to distinguish it from the network registration data that may be generated in the subsequent processing stage of the target vehicle terminal. It is not used to limit the card identification code or mobile country code itself to have a specific data format or value.

[0070] The first service processing side determines the first empty write state of the target vehicle terminal based on the first network registration data, and determines whether an empty write needs to be performed based on the first empty write state, the first network registration data, and the target country information, including: The first service processing side checks the first empty write state of the target vehicle terminal based on the embedded card identifier. The first empty write state includes an empty write completed state, an empty write in progress state, and an empty write not started state. In this embodiment, the first empty write state may include a completed empty write state, an in-process empty write state, and an inactive empty write state. The completed empty write state indicates that the target vehicle terminal has completed the corresponding empty write process; the in-process empty write state indicates that the target vehicle terminal has entered the empty write service process, but further confirmation is needed to confirm whether the empty write has been completed; and the inactive empty write state indicates that the target vehicle terminal has not yet initiated the corresponding empty write process.

[0071] Therefore, the first empty write state serves as the basis for subsequent branch judgments to determine whether an empty write needs to be executed. For different first empty write states, data related to the corresponding judgment purpose in the first network data is called separately, rather than using the same judgment method for different states uniformly.

[0072] When the first empty write status is "completed empty write", it indicates that the current target vehicle terminal has completed the empty write, so there is no need to initiate empty write processing again for this network registration.

[0073] When the first empty write state is in the empty write state, the first service processing side checks whether the target vehicle terminal has completed the empty write based on the first card identification code, and determines that an empty write needs to be performed if the empty write has not been completed. In this embodiment, when the first write state is in the write-in process, the system further checks whether the target vehicle terminal has completed the write operation based on the first card identification code. That is, the embedded card identifier is first used to determine that the target vehicle terminal is in the write-in process. After determining this state, the first card identification code obtained in the current first network registration phase is used to further confirm the write completion status, so that the write state judgment result serves as a prerequisite for the card identification code completion check.

[0074] If the inspection result obtained based on the first card identification code indicates that the target vehicle terminal has completed the empty write, then there is no need to request to perform the empty write again; if the inspection result indicates that the target vehicle terminal has not yet completed the empty write, then it is determined that the current target vehicle terminal needs to perform the empty write in order to enter the subsequent empty write request processing process.

[0075] The first card identification code is used to check whether the target vehicle terminal has completed a blank write operation, and the specific check rules are not limited. For example, this embodiment does not limit what kind of benchmark data the first card identification code needs to be compared with, nor does it limit whether the first card identification code must change before and after the blank write operation. By maintaining the higher-level description of this judgment method, the corresponding check result can be determined according to the completion status check method adopted in the actual blank write operation.

[0076] When the first empty write state is the inactive empty write state, the first service processing side determines the first registered country based on the first mobile country code, and determines whether the registered country conditions of the target country are met based on the first registered country and the target country information. If the registered country conditions of the target country are met, it is determined that an empty write needs to be performed.

[0077] In this embodiment, the first registered country is used to characterize the country corresponding to the mobile communication network in which the target vehicle terminal is located during the first registered phase. There is a correspondence between the first mobile country code and the first registered country, which characterizes the registered country. The specific correspondence between the mobile country code and the country can be determined based on the actual mobile communication network information; therefore, no specific mapping rules are limited here.

[0078] After determining the first country to be registered, the system determines whether the conditions for registration in the target country are met based on the information of the first country to be registered and the target country corresponding to the target vehicle terminal.

[0079] Specifically, the target country information is used to characterize the target country corresponding to the vehicle of the current target vehicle terminal, and the first registered country is used to characterize the country where the target vehicle terminal is currently actually registered. Therefore, by comparing the first registered country with the target country corresponding to the target country information, it can be determined whether the target vehicle terminal is currently in a registered environment capable of initiating the target country's no-write service.

[0080] When the first registered country corresponds to the target country represented by the target country information, it is determined that the target vehicle terminal meets the target country's registration conditions, and it is further determined that the target vehicle terminal needs to perform a null write, so that subsequent null write processing can be initiated to the null write server based on this judgment result. When the first registered country does not correspond to the target country represented by the target country information, the target country's registration conditions are not currently met, and a null write is not triggered based on this registration. When the target vehicle terminal is in a null write-inactive state, it is determined whether to enter the null write request process based on the relationship between the MCC and the target country.

[0081] Therefore, this embodiment establishes the following state-driven judgment relationship: First, the embedded card identifier is used to determine the first empty write state of the target vehicle terminal; when the first empty write state is in the process of empty write, the first card identification code is used to confirm whether the empty write is completed, and if it is not completed, it is determined that the empty write needs to be performed; when the first empty write state is the state of not starting empty write, the first mobile country code is used to determine the first registered country, and then the information of the first registered country and the target country is combined to determine whether the registered conditions of the target country are met, and if the registered conditions of the target country are met, it is determined that the empty write needs to be performed.

[0082] In this way, different data in the same first network registration data can participate in the corresponding judgment process according to the different empty write states of the target vehicle terminal, so that "first network registration data - first empty write state - data check corresponding to the state - whether to perform empty write" forms a continuous processing link, thereby avoiding the direct initiation of empty write processing without identifying the current empty write state and current network registration conditions of the target vehicle terminal.

[0083] In some optional implementations of this embodiment, when it is determined that a null write needs to be performed, the first service processing side sends a null write request to the null write server, so that the null write server performs a null write to the target vehicle terminal, including: The first service processing side generates the empty write request based on the embedded card identifier, the first card identification code and the first mobile country code, and sends the empty write request to the empty write server; The first service processing side obtains the empty write result returned by the empty write server in response to the empty write request, and saves the empty write result in correspondence with the target vehicle terminal.

[0084] Specifically, after determining the first empty write state of the target vehicle terminal based on the first registered network data, and determining that the target vehicle terminal needs to perform an empty write based on the first empty write state, the first registered network data, and the target country information, an empty write request is generated based on the embedded card identifier, the first card identification code, and the first mobile country code in the first registered network data.

[0085] Among them, the embedded card identifier can be EID, which is used to identify the embedded card corresponding to the target vehicle terminal; the first card identification code can be ICCID, which is used to characterize the card identification information corresponding to the target vehicle terminal in the current first network registration phase; and the first mobile country code can be MCC, which is used to characterize the mobile network country information corresponding to the target vehicle terminal in the current first network registration phase.

[0086] It should be noted that the embedded card identifier, first card identification code, and first mobile country code used to generate the empty write request in this embodiment originate from the first network registration data reported by the target vehicle terminal during the empty write judgment stage. In other words, after determining the need for an empty write using the first network registration data during the aforementioned empty write judgment process, the corresponding data in the first network registration data is used to generate the empty write request. This ensures that the data used to determine the empty write requirement can continue to serve as the data basis for executing the empty write, thereby establishing a data continuity relationship between the first network registration data during the empty write judgment stage and the empty write request stage.

[0087] In one implementation, the TMS receives the first registration data reported by the target vehicle terminal after it has registered with the network, and performs corresponding empty write status and empty write condition judgments based on the first registration data. When the judgment result indicates that the target vehicle terminal needs to perform an empty write, the TMS extracts the EID, ICCID, and MCC from the first registration data, and forms an empty write request corresponding to the target vehicle terminal based on the EID, ICCID, and MCC. During the empty write request phase, the TMS sends the EID, ICCID, and MCC to the supplier's empty write service so that the supplier's empty write service can perform an empty write for the corresponding TBOX.

[0088] After generating the empty write request, the empty write request is sent to the empty write server. The empty write server can be the empty write service server provided by the card number provider, which is used to receive the empty write request sent by the TMS side, determine the target vehicle terminal corresponding to this empty write based on the data carried in the empty write request, and perform the corresponding empty write processing for the target vehicle terminal.

[0089] Therefore, the aforementioned empty write judgment result serves as a prerequisite for triggering the generation of an empty write request. The embedded card identifier, the first card identification code, and the first mobile country code in the first network registration data serve as the data basis for generating the empty write request. The generated empty write request further serves as the data basis for the empty write server to execute the empty write, thus forming: The process involves determining that an empty write is needed, obtaining the corresponding data from the first network data, generating an empty write request, sending the empty write request, and then executing the empty write.

[0090] After receiving an empty write request, the empty write server performs an empty write on the target vehicle terminal corresponding to the request and returns the empty write result after completing the corresponding processing. The empty write server can receive the EID, ICCID, and MCC sent by the TMS, perform an empty write on the corresponding TBOX, and return the empty write result to the TMS.

[0091] The empty write result is used to characterize the processing result obtained by the empty write server after performing an empty write in response to this empty write request. After obtaining the empty write result returned by the empty write server, the TMS side saves the empty write result along with the corresponding target vehicle terminal.

[0092] Specifically, since the empty write request is generated for the target vehicle terminal that needs to perform the empty write, and is sent to the empty write server based on the first network registration data corresponding to that target vehicle terminal, after receiving the empty write result returned by the empty write server for the empty write request, the empty write result can be attributed to the target vehicle terminal corresponding to this empty write request and saved accordingly, so that the empty write processing result corresponding to different target vehicle terminals can be determined later. The empty write result returned by the empty write service can be saved as an empty write result record by the TMS side.

[0093] In this embodiment, the correspondence between the empty write result and the target vehicle terminal is to establish the correspondence between the target vehicle terminal, the current empty write request, and the empty write processing result. No specific data structure, storage format, or storage location of the empty write result is limited.

[0094] Furthermore, no specific restrictions are imposed on the specific message structure of the empty write request, the specific empty write instruction used by the empty write server when executing the empty write, the actual data content written, the write object, and the specific communication method used between the TMS side and the empty write server.

[0095] In the above manner, after determining that the target vehicle terminal needs to perform a null write, the embedded card identifier, first card identification code, and first mobile country code obtained in the null write judgment stage are directly used to generate and send a null write request, so that the null write request judgment result can be further converted into a null write request that can be processed by the null write server; after the null write server performs the null write, it returns the null write result, and then saves the null write result with the corresponding target vehicle terminal, thereby forming a continuous processing link from null write judgment, null write request, null write execution to null write result recording.

[0096] In some optional implementations of this embodiment, the second network registration data includes an embedded card identifier and a second card identification code; when the target vehicle terminal re-registers after performing a null write, the first service processing side obtains the second network registration data reported by the target vehicle terminal, and determines whether the target vehicle terminal has completed the null write based on the second network registration data, including: The first service processing side checks the second empty write state of the target vehicle terminal after it re-enters the network based on the embedded card identifier; When the second write state is in the write state, the first service processing side checks whether the target vehicle terminal has completed the write based on the second card identification code, and determines that the target vehicle terminal has completed the write when the check result indicates that the write has been completed.

[0097] After the empty write server performs an empty write operation on the target vehicle terminal, the target vehicle terminal re-registers with the mobile communication network. Once the target vehicle terminal successfully re-registers with the network, the second registration data reported by the target vehicle terminal is obtained.

[0098] The second network registration data is the network registration data generated and reported by the target vehicle terminal when it re-registers after performing a no-write operation. It belongs to a different processing stage from the first network registration data obtained during the no-write judgment stage. The first network registration data is mainly used to determine the no-write status of the target vehicle terminal and whether a no-write operation is required before performing the no-write operation. The second network registration data is used to confirm the completion status of the no-write operation of the target vehicle terminal after performing the no-write operation.

[0099] In this embodiment, the second network registration data includes an embedded card identifier and a second card identification code. The embedded card identifier can be an EID, used to identify the embedded card corresponding to the target vehicle terminal; the second card identification code can be an ICCID, used to characterize the current card identification information of the target vehicle terminal after performing a null write and re-registering.

[0100] It should be noted that the "second" in the second card identification code is used to distinguish it from the first card identification code in the empty write judgment stage. It indicates that the card identification code is obtained in the re-registration stage after the target vehicle terminal performs an empty write. It does not require that the second card identification code and the first card identification code be different in value, nor does it require that there be a preset data change relationship between the two.

[0101] After obtaining the second network registration data, the empty write status of the target vehicle terminal after re-registering is first checked based on the embedded card identifier in the second network registration data, and the empty write status obtained after re-registering is taken as the second empty write status.

[0102] The second empty write state is used to characterize the current empty write service state of the target vehicle terminal after performing an empty write and re-registering with the network. By re-acquiring the network registration data of the target vehicle terminal and checking the empty write state again, the actual service state after performing the empty write can continue to participate in the empty write completion confirmation, instead of directly determining that the target vehicle terminal has completed the empty write based solely on the previously issued empty write request.

[0103] When the second empty write status is detected as being in the empty write state, further check whether the target vehicle terminal has completed the empty write based on the second card identification code in the second network data.

[0104] Specifically, when the second empty write state is in the process of empty write, it indicates that the target vehicle terminal cannot be directly determined to have completed the empty write based solely on the current empty write state. Therefore, the empty write completion check is further performed using the second SIM card identification code reported by the target vehicle terminal after re-registering with the network. The second SIM card identification code is reported by the target vehicle terminal during the re-registration process after the empty write, enabling the empty write completion check to be based on the current network registration data after re-registration.

[0105] When the inspection result obtained based on the second card identification code indicates that the target vehicle terminal has completed the empty write operation, it is determined that the target vehicle terminal has completed this empty write process. Therefore, the target vehicle terminal transitions from the empty write execution phase to the empty write completion state, and this empty write completion result can be used as the basis for subsequent processing.

[0106] For example, in one implementation, after the no-write server performs a no-write operation on the target vehicle terminal, the target vehicle terminal re-registers with the network and reports the network registration data corresponding to the current embedded card again. After receiving the re-reported network registration data, the TMS side re-checks the current no-write status of the target vehicle terminal based on the EID in the data. If the check result indicates that a no-write is in progress, it continues to check whether the no-write has been completed based on the ICCID reported by the re-registered network. If the check result indicates that the no-write has been completed, it is determined that the target vehicle terminal has completed the no-write operation.

[0107] Specifically, checking whether the target vehicle terminal has completed the empty write based on the second card identification code involves checking the empty write completion status corresponding to the second card identification code. This embodiment does not limit the specific comparison relationship between the second card identification code and other card identification information, nor does it limit the specific data structure, query method, or judgment condition used when determining the empty write completion status through the second card identification code.

[0108] Therefore, this embodiment forms the following processing chain: after the target vehicle terminal performs a blank write, it re-registers with the network, and the re-registration generates second registration data; the embedded card identifier in the second registration data is used to check the second blank write status after re-registration; when the second blank write status is in the blank write state, the blank write is further checked based on the second card identification code to see if it has been completed; when the check result indicates that it has been completed, it is determined that the target vehicle terminal has completed the blank write.

[0109] By using the above method, the empty write execution by the empty write server is linked with the status confirmation after the target vehicle terminal re-registers with the network. This allows the target vehicle terminal to use the newly generated network registration data to reconfirm the actual completion of the empty write after executing the empty write, thus forming a continuous processing process of "execute empty write - re-register with the network - re-check the empty write status - confirm the completion of the empty write".

[0110] In some optional implementations of this embodiment, after the first service processing side determines that the target vehicle terminal has completed a no-write operation, the second service processing side obtains the monitoring network registration data reported by the target vehicle terminal during the subsequent network registration process, as well as the sales country information corresponding to the target vehicle terminal. Based on the monitoring network registration data and the sales country information, the cross-border status of the vehicle corresponding to the target vehicle terminal and the corresponding status time information are determined, including: When the target vehicle terminal restarts or switches operators and re-enters the network, the second service processing side obtains the monitoring network entry data reported by the target vehicle terminal, and the monitoring network entry data includes the monitoring country code; The second service processing side determines the country of the monitored network based on the monitored mobile country code; When the monitored country of residence is inconsistent with the country of sale information, the second business processing side determines that the vehicle is in a cross-border state and records the cross-border time point; when the monitored country of residence is consistent with the country of sale, the second business processing side determines that the vehicle is in a non-cross-border state and records the non-cross-border time point. The status time information includes the cross-border time point and the non-cross-border time point.

[0111] In this embodiment, after determining that the target vehicle terminal has completed the no-write operation, the target vehicle terminal enters the subsequent operation phase. During the subsequent operation, after the target vehicle terminal successfully registers with the network, it can report data corresponding to its current registration status, so that the TSP side can perform cross-border status monitoring on the corresponding vehicle based on the current registration status of the target vehicle terminal.

[0112] Specifically, the monitoring and network access data reported by the target vehicle terminal during the subsequent network access process, as well as the sales country information corresponding to the target vehicle terminal, are obtained.

[0113] The monitoring network registration data refers to the network registration data generated and reported during the subsequent operation of the vehicle after the target vehicle terminal has completed its write-through process and when it registers or re-registers with the network. This data is used to characterize the current mobile communication network environment of the target vehicle terminal. The sales country information is used to characterize the sales country of the vehicle corresponding to the target vehicle terminal and serves as a reference for determining whether the vehicle is currently in a cross-border status.

[0114] It should be noted that in this embodiment, the monitoring network data and the first and second network data used in the empty write processing stage correspond to different business stages. The first network data is used to determine the empty write status and empty write requirement before the empty write is executed, the second network data is used to confirm the completion after the empty write is executed, and the monitoring network data is used for cross-border status monitoring of the vehicle after the target vehicle terminal has completed the empty write. Therefore, the monitoring network data is obtained after confirming that the target vehicle terminal has completed the empty write and is used for subsequent cross-border monitoring, and is no longer used to determine whether an empty write needs to be executed.

[0115] During the subsequent operation of the target vehicle terminal, when it restarts or switches operators and re-registers with the network, the monitoring network registration data re-reported by the target vehicle terminal is obtained. Therefore, when the mobile communication network accessed by the target vehicle terminal changes during vehicle operation, network registration information corresponding to the current network environment can be obtained through the monitoring network registration data reported after re-registration.

[0116] In one implementation, after successfully registering with the network, the vehicle-mounted TBOX reports the registration information to the TSP side. When the vehicle-mounted TBOX restarts or switches mobile communication operators, it re-registers with the network and reports the registration information corresponding to this registration to the TSP side again, so that the TSP side can continuously obtain the registration changes during the subsequent operation of the vehicle.

[0117] In this embodiment, the monitored network data includes monitored mobile country codes. The monitored mobile country code can be the MCC corresponding to the target vehicle terminal's current network, used to represent the country information corresponding to the current network.

[0118] After obtaining the monitored mobile country code, the monitored network-hosted country is determined based on the monitored mobile country code. The monitored network-hosted country is used to characterize the country corresponding to the target vehicle terminal during this network-hosting or re-hosting process. Different countries' mobile communication networks correspond to different mobile country codes; therefore, the monitored network-hosted country corresponding to the current network can be obtained based on the monitored mobile country code currently reported by the target vehicle terminal.

[0119] The method for monitoring the correspondence between mobile country codes and specific countries can be determined based on country information in the mobile communication network. This embodiment does not limit the specific mapping table, data structure, or query method used to monitor the correspondence between mobile country codes and countries.

[0120] After determining the country where the monitoring network is located, the current cross-border status of the vehicle corresponding to the target vehicle terminal is determined based on the information of the country where the monitoring network is located and the country of sale corresponding to the target vehicle terminal.

[0121] Specifically, the monitoring of the country of origin and the country of sale are compared. When the country of origin and the country of sale are inconsistent, it indicates that the target vehicle terminal is currently located in a country different from the country of sale of the vehicle. Therefore, it is determined that the vehicle is in a cross-border state, and the cross-border time point corresponding to this cross-border state is recorded.

[0122] When the country where the monitoring network is located is the same as the country of sale, it indicates that the country where the target vehicle terminal is currently located is the same as the country of sale of the vehicle. Therefore, it is determined that the vehicle is in a non-cross-border state, and the non-cross-border time point corresponding to this non-cross-border state is recorded.

[0123] For example, after receiving the network registration information subsequently reported by the target vehicle terminal that has completed the empty write, the TSP side determines the current cross-border status of the vehicle based on the relationship between the network registration country corresponding to the MCC and the vehicle's country of sale. When the two are inconsistent, the cross-border time point is recorded; when they are consistent, the non-cross-border time point is recorded. This process enables the network registration information generated each time the target vehicle terminal registers or re-registers to be further converted into time information corresponding to the vehicle's cross-border status.

[0124] The cross-border time point is used to characterize the state time corresponding to when the vehicle is in a cross-border state, while the non-cross-border time point is used to characterize the state time corresponding to when the vehicle is in a non-cross-border state. The cross-border time point and the non-cross-border time point together constitute the vehicle's state time information.

[0125] Therefore, during the subsequent operation of the vehicle, as the target vehicle terminal registers or re-registers multiple times, the monitoring registration data corresponding to each registration can be obtained sequentially, and the corresponding monitoring registration country can be determined according to the monitoring mobile country code. Then, combined with the sales country information, the cross-border status corresponding to each registration can be determined, and status time information corresponding to each cross-border status can be generated.

[0126] For example, at the first monitoring moment, if the monitoring network registration country is determined to be different from the sales country based on the monitoring network registration data reported by the target vehicle terminal, then the cross-border time point corresponding to the first monitoring moment is recorded. Subsequently, if the target vehicle terminal re-registers due to a restart or switch of operators and obtains monitoring network registration data again at the second monitoring moment, and if it is determined at this time that the monitoring network registration country is the same as the sales country, then the non-cross-border time point corresponding to the second monitoring moment is recorded. By continuously acquiring the status time information of the target vehicle terminal at different network registration stages, it is possible to retain time records of changes in the vehicle's cross-border status as the network registration environment changes.

[0127] It should be noted that the state time information in this embodiment is used to characterize the time information corresponding to different cross-border states of the vehicle. This embodiment only describes the generation process of cross-border time points and non-cross-border time points, and does not further limit how time intervals are formed between different state time points, nor does it limit the statistical method of cross-border duration.

[0128] Through the above method, after the target vehicle terminal has completed its no-fly write, the monitoring mobile country code is obtained by utilizing the monitoring network data continuously reported during its subsequent network registration or re-registration process. Based on the monitoring mobile country code, the monitoring network registration country is determined. Then, the monitoring network registration country is compared with the vehicle's country of sale to determine whether the vehicle is currently in a cross-border or non-cross-border state. The cross-border or non-cross-border time point corresponding to the corresponding state is recorded, thus forming a continuous processing link of "monitoring network registration data - monitoring network registration country - cross-border state - state time information", providing a time state data foundation for the continuous monitoring of the vehicle's subsequent cross-border network registration status.

[0129] In some optional implementations of this embodiment, the second service processing side determines the cross-border time interval of the vehicle based on the state time information, and determines the cross-border network access anomaly status of the vehicle based on the cross-border time interval within a preset statistical period, including: The second business processing side determines the cross-border time interval of the vehicle based on the cross-border time point and the non-cross-border time point; The second business processing side determines the total cross-border time of the vehicle based on each of the cross-border time intervals within the preset statistical period; The second business processing side determines whether the vehicle meets the preset cross-border abnormal conditions based on the total cross-border time, and if the preset cross-border abnormal conditions are met, determines that the vehicle is in a cross-border network abnormal state.

[0130] In this embodiment, during the cross-border monitoring process after the target vehicle terminal completes its write-through, monitoring network data can be continuously obtained as the target vehicle terminal registers or re-registers with the network. The cross-border status of the vehicle is determined based on each monitoring network data session. When the vehicle is determined to be in a cross-border status, the cross-border time point is recorded; when the vehicle is determined to be in a non-cross-border status, the non-cross-border time point is recorded. The cross-border time point and the non-cross-border time point constitute the vehicle's status time information.

[0131] Furthermore, the cross-border time interval of the vehicle is determined based on the cross-border time point and the non-cross-border time point.

[0132] The cross-border time point represents the time when the vehicle is identified as being in a cross-border state, while the non-cross-border time point represents the time when the vehicle is identified as being in a non-cross-border state. As the vehicle's cross-border state changes, multiple state time points corresponding to different cross-border states can be generated. Based on the cross-border state and its time change relationship reflected by the state time information, the time range corresponding to the vehicle being in a cross-border state can be determined, and this time range is used as the cross-border time interval.

[0133] For example, during the subsequent operation of the vehicle, the target vehicle terminal re-enters the network at a certain moment. Based on the monitoring data from this re-entry, it is determined that the vehicle is in a cross-border state, and the corresponding cross-border time point is recorded. Subsequently, the target vehicle terminal re-enters the network, and based on the new monitoring data, it is determined that the vehicle is in a non-cross-border state, and the corresponding non-cross-border time point is recorded. Based on the changes in vehicle status reflected by the aforementioned cross-border and non-cross-border time points, it can be determined that the vehicle is in a cross-border state during the corresponding period, thus forming a corresponding cross-border time interval.

[0134] When a vehicle experiences multiple changes in its network environment during operation, multiple cross-border and non-cross-border time points can be generated, further resulting in multiple cross-border time intervals. Therefore, compared to simply recording whether a vehicle is in a cross-border state at a single moment, forming cross-border time intervals using state time information can further characterize the duration of the vehicle's cross-border state. During cross-border monitoring, corresponding time intervals can be formed based on cross-border and non-cross-border time points to further calculate the vehicle's cross-border duration.

[0135] It should be noted that this embodiment determines the time interval corresponding to the vehicle being in a cross-border state based on the cross-border time point and the non-cross-border time point, without limiting the specific pairing algorithm used between multiple state time points.

[0136] After obtaining the cross-border time intervals of the vehicle, the total cross-border time of the vehicle is determined based on each cross-border time interval within a preset statistical period.

[0137] The preset statistical period is used to limit the time range for this cross-border network anomaly assessment. During the statistical analysis, cross-border time intervals within the preset statistical period are obtained, and the total cross-border duration of the vehicle within that preset statistical period is determined based on the vehicle's cross-border continuity as represented by each cross-border time interval.

[0138] When there is only one cross-border time interval within a preset statistical period, the corresponding cross-border duration can be determined based on that time interval. When there are multiple cross-border time intervals within a preset statistical period, the total cross-border duration of vehicles within that statistical period is determined based on the cross-border durations corresponding to each of the multiple time intervals. Thus, multiple scattered cross-border status time records are further converted into a total cross-border duration that reflects the overall cross-border network presence of vehicles within a certain time frame.

[0139] In one implementation, the aforementioned cross-border statistical processing can be performed periodically via a scheduled task. For example, a statistical task can be triggered weekly, using the most recent two months as the corresponding statistical time range, and the total cross-border time of vehicles can be calculated based on the cross-border time intervals formed within this time range.

[0140] After determining the total cross-border time of vehicles within a preset statistical period, it is determined whether the vehicles meet the preset cross-border abnormal conditions based on the total cross-border time.

[0141] The preset cross-border anomaly conditions are used to determine whether a vehicle's cross-border stationing status within a preset statistical period reaches a level requiring anomaly handling. By using the total cross-border duration obtained within the preset statistical period as the data basis for anomaly judgment, the determination of cross-border stationing anomaly status can not only rely on the cross-border status reflected in a single stationing, but also further consider the vehicle's continuous cross-border status over a period of time.

[0142] If the judgment result based on the total cross-border duration indicates that the vehicle meets the preset cross-border abnormal conditions, the vehicle is determined to be in a cross-border network abnormal state; if the judgment result indicates that the vehicle does not meet the preset cross-border abnormal conditions, the vehicle is not determined to be in a cross-border network abnormal state.

[0143] In one implementation, it can be determined whether a vehicle meets preset cross-border anomaly conditions based on the statistical results corresponding to the total cross-border duration. For example, using the most recent two months as the statistical time range, if the statistically obtained proportion of total cross-border duration is greater than 40%, it can be determined that the vehicle meets the preset cross-border anomaly conditions, and the vehicle will be included in the corresponding anomaly handling scope; if the proportion does not meet the corresponding conditions, the current cross-border network access anomaly handling will not be triggered.

[0144] Based on the above processing, and the obtained cross-border and non-cross-border time points, the cross-border time intervals corresponding to the vehicles are first determined from these time points. Then, statistics are performed on each cross-border time interval within a preset statistical period to determine the total cross-border duration. Finally, the total cross-border duration is used to determine whether preset cross-border anomaly conditions are met, thus forming: Status and time information—cross-border time interval—cross-border total duration—continuous processing link for cross-border network abnormal status.

[0145] Therefore, the discrete cross-border status records formed during multiple network registrations of the target vehicle terminal can be further converted into cross-border continuous status within a certain statistical period, and the cross-border continuous status can be used as the basis for judging cross-border network registration anomalies, so that short-term cross-border network registration and continuous cross-border network registration can be distinguished in the time dimension.

[0146] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by instructing related hardware through computer-readable instructions. These computer-readable instructions can be stored in a computer-readable storage medium. When the program is executed, it can include the processes of the embodiments of the above methods. The aforementioned storage medium can be a non-volatile storage medium such as a magnetic disk, optical disk, or read-only memory (ROM), or random access memory (RAM).

[0147] It should be understood that although the steps in the flowcharts of the accompanying figures are shown sequentially as indicated by the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some steps in the flowcharts of the accompanying figures may include multiple sub-steps or multiple stages. These sub-steps or stages are not necessarily completed at the same time, but can be executed at different times, and their execution order is not necessarily sequential, but can be performed alternately or in turn with other steps or at least some of the sub-steps or stages of other steps.

[0148] Further reference Figure 3 As a response to the above Figure 2 The implementation of the method shown in this application provides an embodiment of a null write and cross-border monitoring device, which is similar to... Figure 2 The method embodiment shown corresponds to this. The device corresponds to a back-end business system, including a first business processing side and a second business processing side, which can be deployed on different servers that communicate with each other.

[0149] like Figure 3 As shown, the empty write and cross-border monitoring device 300 described in this embodiment includes a first service processing side and a second service processing side; the first service processing side includes a first acquisition module 301, an empty write judgment module 302, an empty write request module 303, and an empty write confirmation module 304; the second service processing side includes a cross-border monitoring module 305 and an anomaly determination module 306. Wherein: The first acquisition module 301 is used to acquire the first network registration data reported by the target vehicle terminal after it registers with the network and the target country information corresponding to the target vehicle terminal. The empty write judgment module 302 is used to determine the first empty write state of the target vehicle terminal based on the first network data, and to determine whether an empty write needs to be performed based on the first empty write state, the first network data and the target country information. The empty write request module 303 is used to send an empty write request to the empty write server when it is determined that an empty write needs to be performed, so that the empty write server performs an empty write on the target vehicle terminal. The empty write confirmation module 304 is used to obtain the second network registration data reported by the target vehicle terminal when the target vehicle terminal re-registers after performing an empty write, and to determine whether the target vehicle terminal has completed the empty write based on the second network registration data. The cross-border monitoring module 305 is used to obtain the monitoring network data reported by the target vehicle terminal during the subsequent network registration process and the sales country information corresponding to the target vehicle terminal after determining that the target vehicle terminal has completed the empty write. Based on the monitoring network data and the sales country information, the cross-border status of the vehicle corresponding to the target vehicle terminal and the corresponding status time information are determined. The anomaly determination module 306 is used to determine the cross-border time interval of the vehicle based on the status time information, and to determine the cross-border network abnormal status of the vehicle based on the cross-border time interval within a preset statistical period.

[0150] To address the aforementioned technical problems, embodiments of this application also provide a computer device. This computer device can serve as a first business processing side or a second business processing side in a back-end business system. Please refer to [link / reference] for details. Figure 4 , Figure 4 This is a basic structural block diagram of the computer device in this embodiment.

[0151] The computer device 4 includes a memory 41, a processor 42, and a network interface 43 that are interconnected via a system bus. It should be noted that only the computer device 4 with components 41-43 is shown in the figure; however, it should be understood that it is not required to implement all the shown components, and more or fewer components can be implemented alternatively. Those skilled in the art will understand that the computer device described here is a device capable of automatically performing numerical calculations and / or information processing according to pre-set or stored instructions, and its hardware includes, but is not limited to, microprocessors, application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), digital signal processors (DSPs), embedded devices, etc.

[0152] The computer device can be a desktop computer, laptop, handheld computer, or cloud server, etc. The computer device can interact with the user via a keyboard, mouse, remote control, touchpad, or voice control.

[0153] The memory 41 includes at least one type of readable storage medium, including flash memory, hard disk, multimedia card, card-type memory (e.g., SD or DX memory), random access memory (RAM), static random access memory (SRAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), programmable read-only memory (PROM), magnetic memory, magnetic disk, optical disk, etc. In some embodiments, the memory 41 may be an internal storage unit of the computer device 4, such as the hard disk or memory of the computer device 4. In other embodiments, the memory 41 may also be an external storage device of the computer device 4, such as a plug-in hard disk, smart media card (SMC), secure digital (SD) card, flash card, etc., equipped on the computer device 4. Of course, the memory 41 may also include both the internal storage unit and its external storage device of the computer device 4. In this embodiment, the memory 41 is typically used to store the operating system and various application software installed on the computer device 4, such as computer-readable instructions for write-only and cross-border monitoring methods. In addition, the memory 41 can also be used to temporarily store various types of data that have been output or will be output.

[0154] In some embodiments, the processor 42 may be a central processing unit (CPU), a controller, a microcontroller, a microprocessor, or other data processing chip. The processor 42 is typically used to control the overall operation of the computer device 4. In this embodiment, when the computer device acts as a first service processing side, the processor 42 is used to execute the steps performed by the first service processing side in the no-write and cross-border monitoring method; when the computer device acts as a second service processing side, the processor 42 is used to execute the steps performed by the second service processing side in the no-write and cross-border monitoring method.

[0155] The network interface 43 may include a wireless network interface or a wired network interface, which is typically used to establish communication connections between the computer device 4 and other electronic devices.

[0156] This application also provides another embodiment, namely, a computer-readable storage medium storing computer-readable instructions that can be executed by one or more processors to cause the one or more processors to perform the steps of the above-described no-write and cross-border monitoring method.

[0157] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) and includes several instructions to cause a terminal device (which may be a mobile phone, computer, server, air conditioner, or network device, etc.) to execute the methods described in the various embodiments of this application.

[0158] Obviously, the embodiments described above are only some embodiments of this application, not all embodiments. The accompanying drawings show preferred embodiments of this application, but do not limit the patent scope of this application. This application can be implemented in many different forms; rather, the purpose of providing these embodiments is to provide a more thorough and comprehensive understanding of the disclosure of this application. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art can still modify the technical solutions described in the foregoing specific embodiments, or make equivalent substitutions for some of the technical features. Any equivalent structures made using the content of this application's specification and drawings, directly or indirectly applied to other related technical fields, are similarly within the scope of patent protection of this application.

Claims

1. A method for detecting empty writes and cross-border operations, applied to a back-end business system, the back-end business system comprising a first business processing side and a second business processing side, characterized in that, include: The first service processing side obtains the first network registration data reported by the target vehicle terminal after it registers with the network, as well as the target country information corresponding to the target vehicle terminal; The first service processing side determines the first empty write state of the target vehicle terminal based on the first network registration data, and determines whether an empty write needs to be performed based on the first empty write state, the first network registration data, and the target country information; When it is determined that an empty write needs to be performed, the first service processing side sends an empty write request to the empty write server so that the empty write server performs an empty write on the target vehicle terminal. When the target vehicle terminal re-registers after performing a blank write, the first service processing side obtains the second registration data reported by the target vehicle terminal, and determines whether the target vehicle terminal has completed the blank write based on the second registration data. After the first service processing side determines that the target vehicle terminal has completed the empty write, the second service processing side obtains the monitoring network registration data reported by the target vehicle terminal during the subsequent network registration process and the sales country information corresponding to the target vehicle terminal, and determines the cross-border status of the vehicle corresponding to the target vehicle terminal and the corresponding status time information based on the monitoring network registration data and the sales country information. The second service processing side determines the cross-border time interval of the vehicle based on the status time information, and determines the cross-border network abnormal status of the vehicle based on the cross-border time interval within a preset statistical period.

2. The method for detecting empty writes and cross-border activities according to claim 1, characterized in that, Before the first service processing side obtains the first network registration data reported by the target vehicle terminal after network registration and the target country information corresponding to the target vehicle terminal, it includes: The first service processing side obtains the embedded card identifier corresponding to the target vehicle terminal; The first service processing side sends the embedded card identifier and the target country information to the card number supply side, so that the card number supply side prepares card number resources corresponding to the target country information before the target vehicle terminal arrives in the target country.

3. The method for detecting empty writes and cross-border activities according to claim 1, characterized in that, The first network registration data includes an embedded card identifier, a first card identification code, and a first mobile country code; The first service processing side determines the first empty write state of the target vehicle terminal based on the first network registration data, and determines whether an empty write needs to be performed based on the first empty write state, the first network registration data, and the target country information, including: The first service processing side checks the first empty write state of the target vehicle terminal based on the embedded card identifier. The first empty write state includes an empty write completed state, an empty write in progress state, and an empty write not started state. When the first empty write state is in the empty write state, the first service processing side checks whether the target vehicle terminal has completed the empty write based on the first card identification code, and determines that an empty write needs to be performed if the empty write has not been completed. When the first empty write state is the inactive empty write state, the first service processing side determines the first registered country based on the first mobile country code, and determines whether the registered country conditions of the target country are met based on the first registered country and the target country information. If the registered country conditions of the target country are met, it is determined that an empty write needs to be performed.

4. The method for detecting empty writes and cross-border activities according to claim 3, characterized in that, The step of sending an empty write request to the empty write server when it is determined that an empty write is needed, so that the empty write server performs an empty write on the target vehicle terminal, includes: The first service processing side generates the empty write request based on the embedded card identifier, the first card identification code and the first mobile country code, and sends the empty write request to the empty write server; The first service processing side obtains the empty write result returned by the empty write server in response to the empty write request, and saves the empty write result in correspondence with the target vehicle terminal.

5. The method for detecting empty writes and cross-border activities according to claim 1, characterized in that, The second network registration data includes the embedded card identifier and the second card identification code; When the target vehicle terminal re-registers after performing a null write, the first service processing side obtains the second registration data reported by the target vehicle terminal, and determines whether the target vehicle terminal has completed the null write based on the second registration data, including: The first service processing side checks the second empty write state of the target vehicle terminal after it re-enters the network based on the embedded card identifier; When the second write state is in the write state, the first service processing side checks whether the target vehicle terminal has completed the write based on the second card identification code, and determines that the target vehicle terminal has completed the write when the check result indicates that the write has been completed.

6. The method for detecting empty writes and cross-border activities according to claim 1, characterized in that, After the first service processing side determines that the target vehicle terminal has completed a no-write operation, the second service processing side obtains the monitoring network registration data reported by the target vehicle terminal during subsequent network registration processes, as well as the sales country information corresponding to the target vehicle terminal. Based on the monitoring network registration data and the sales country information, the second service processing side determines the cross-border status of the vehicle corresponding to the target vehicle terminal and the corresponding status time information, including: When the target vehicle terminal restarts or switches operators and re-enters the network, the second service processing side obtains the monitoring network entry data reported by the target vehicle terminal, and the monitoring network entry data includes the monitoring country code; The second service processing side determines the country of the monitored network based on the monitored mobile country code; When the monitored country of residence is inconsistent with the country of sale information, the second business processing side determines that the vehicle is in a cross-border state and records the cross-border time point; when the monitored country of residence is consistent with the country of sale, the second business processing side determines that the vehicle is in a non-cross-border state and records the non-cross-border time point. The status time information includes the cross-border time point and the non-cross-border time point.

7. The method for detecting empty writes and cross-border activities according to claim 6, characterized in that, The second service processing side determines the cross-border time interval of the vehicle based on the status time information, and determines the cross-border network access anomaly status of the vehicle based on the cross-border time interval within a preset statistical period, including: The second business processing side determines the cross-border time interval of the vehicle based on the cross-border time point and the non-cross-border time point; The second business processing side determines the total cross-border time of the vehicle based on each of the cross-border time intervals within the preset statistical period; The second business processing side determines whether the vehicle meets the preset cross-border abnormal conditions based on the total cross-border time, and if the preset cross-border abnormal conditions are met, determines that the vehicle is in a cross-border network abnormal state.

8. A device for monitoring blank writing and cross-border movement, characterized in that, Including the first business processing side and the second business processing side; The first business processing side includes a first acquisition module, an empty write judgment module, an empty write request module and an empty write confirmation module, wherein the first acquisition module is used to acquire the first network registration data reported by the target vehicle terminal after it registers with the network and the target country information corresponding to the target vehicle terminal; The empty write judgment module is used to determine the first empty write state of the target vehicle terminal based on the first network data, and to determine whether an empty write needs to be performed based on the first empty write state, the first network data and the target country information. The empty write request module is used to send an empty write request to the empty write server when it is determined that an empty write needs to be performed, so that the empty write server performs an empty write on the target vehicle terminal. The empty write confirmation module is used to obtain the second network registration data reported by the target vehicle terminal when the target vehicle terminal re-registers after performing an empty write, and to determine whether the target vehicle terminal has completed the empty write based on the second network registration data. The second business processing side includes a cross-border monitoring module and an anomaly determination module. The cross-border monitoring module is used to obtain the monitoring network registration data reported by the target vehicle terminal during the subsequent network registration process and the sales country information corresponding to the target vehicle terminal after determining that the target vehicle terminal has completed the empty write. Based on the monitoring network registration data and the sales country information, the cross-border status of the vehicle corresponding to the target vehicle terminal and the corresponding status time information are determined. The anomaly determination module is used to determine the cross-border time interval of the vehicle based on the status time information, and to determine the cross-border network abnormal status of the vehicle based on the cross-border time interval within a preset statistical period.

9. A computer device, characterized in that, The computer device includes a memory and a processor, and is used as a first business processing side or a second business processing side in the back-end business system. The memory stores computer-readable instructions, and when the processor executes the computer-readable instructions, it implements the steps performed by the first business processing side or the second business processing side in the empty write and cross-border monitoring method 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 one or more processors, implement the steps of the no-write and cross-border monitoring method as described in any one of claims 1 to 7.

Citation Information

Patent Citations

  • Soft SIM card network access control method and device

    CN111373777A

  • Remote card writing method and system, electronic equipment and storage medium

    CN118200893A