Terminal addressing method, apparatus, computer device, storage medium and program product

Abstract

The application relates to a terminal addressing method and device, computer equipment, a storage medium and a program product, which can be used in the technical field of addressing. The method comprises the following steps: receiving an addressing request sent by a terminal based on a preset domain name; the preset domain name is used for representing a basic domain name corresponding to a regional center site of a region where the terminal is located; the addressing request carries vehicle information corresponding to the terminal; based on the vehicle information, a local cache is queried to obtain a site information query result corresponding to the vehicle information; in the case that the site information query result indicates that target site information corresponding to the vehicle information is not queried, a site information query request is sent to a preset central addressing server according to the vehicle information; target site information returned by the central addressing server in response to the site information query request is received; and the target site information is sent to the terminal, so that the terminal accesses a site corresponding to the target site information. The method can improve the efficiency of terminal access to the site.

Description

Technical Field

[0001] This application relates to the field of addressing technology, and in particular to a terminal addressing method, apparatus, computer equipment, storage medium, and program product. Background Technology

[0002] As the automotive industry accelerates its transformation towards intelligence and connectivity, connected vehicle services are rapidly expanding into the global market. Throughout the entire vehicle lifecycle, in-vehicle terminals continuously generate massive amounts of business data. Ensuring efficient connectivity and data management for vehicles in various regions worldwide is a crucial aspect of automakers' globalization efforts.

[0003] Currently, cross-regional network site access for terminals mainly relies on traditional centralized cloud platforms. However, when faced with complex network environments in different countries and regions and increasingly stringent data compliance requirements, this conventional access method often requires cumbersome firmware upgrades or system migrations for terminals, resulting in low efficiency for terminal access to sites. Summary of the Invention

[0004] Therefore, it is necessary to provide a terminal addressing method, apparatus, computer equipment, computer-readable storage medium, and computer program product that can improve the efficiency of terminal access sites, in response to the above-mentioned technical problems.

[0005] Firstly, this application provides a terminal addressing method applied to a regional central site addressing server, the method comprising:

[0006] The receiving terminal sends an addressing request based on a preset domain name; the preset domain name is used to represent the basic domain name corresponding to the regional center station of the area where the terminal is located; the addressing request carries vehicle information corresponding to the terminal;

[0007] Based on the local cache of the vehicle information query, the query results of the station information corresponding to the vehicle information are obtained;

[0008] If the site information query result indicates that no target site information corresponding to the vehicle information is found, a site information query request is sent to the preset central addressing server based on the vehicle information.

[0009] Receive the target site information returned by the central addressing server in response to the site information query request;

[0010] The target site information is sent to the terminal, enabling the terminal to access the site corresponding to the target site information.

[0011] In one embodiment, the central addressing server includes a primary server and a backup server;

[0012] The step of sending a station information query request to a preset central addressing server based on the vehicle information includes:

[0013] Based on the vehicle information, a site information query request is sent to the main server;

[0014] The step of receiving the target site information returned by the central addressing server in response to the site information query request includes:

[0015] If the main server successfully responds to the site information query request, the target site information returned by the main server in response to the site information query request is received.

[0016] If the main server times out or fails to respond to the site information query request, it sends the site information query request to the backup server based on the vehicle information, and receives the target site information returned by the backup server in response to the site information query request.

[0017] In one embodiment, the vehicle information includes actual sales area information, preset sales area information, and configuration code area information;

[0018] Sending a site information query request to a preset central addressing server includes:

[0019] The system sends a site information query request to the central addressing server, which then selects the corresponding information to query the site according to a preset priority order to obtain the target site information. The preset priority order is used to characterize the selection priority among the actual sales area information, the preset sales area information, and the configuration code area information.

[0020] In one embodiment, after receiving the target site information returned by the central addressing server in response to the site information query request, the method further includes:

[0021] The association between the vehicle information and the target station information is stored in the local cache;

[0022] Based on the actual sales status of the vehicle information, set the cache expiration time for the association relationship.

[0023] In one embodiment, setting the cache expiration time of the association relationship based on the actual sales status of the vehicle information includes:

[0024] If the actual sales status is "actually sold", the cache expiration time is set to the first time.

[0025] If the actual sales status is not actual sales status, the cache expiration time is set to a second time; the first time is longer than the second time.

[0026] In one embodiment, the site includes the regional center site or a regional edge site under the jurisdiction of the regional center site;

[0027] The method further includes:

[0028] The terminal receives non-sensitive service data synchronized from the regional edge station; the non-sensitive service data is uploaded by the terminal to the regional edge station.

[0029] The non-sensitive business data is stored and processed.

[0030] In one embodiment, after obtaining the station information query result corresponding to the vehicle information based on the local cache of the vehicle information query, the method further includes:

[0031] If the query result indicates that the target station information corresponding to the vehicle information has been found, the target station information is retrieved from the local cache.

[0032] Secondly, this application also provides a terminal addressing device, applied to a regional central station addressing server, the device comprising:

[0033] The request receiving module is used to receive an addressing request sent by the terminal based on a preset domain name; the preset domain name is used to represent the basic domain name corresponding to the regional center station of the area where the terminal is located; the addressing request carries the vehicle information corresponding to the terminal;

[0034] The information query module is used to query the local cache based on the vehicle information to obtain the query results of the station information corresponding to the vehicle information;

[0035] The request sending module is used to send a site information query request to a preset central addressing server based on the vehicle information when the site information query result indicates that no target site information corresponding to the vehicle information is found.

[0036] The information receiving module is used to receive the target site information returned by the central addressing server in response to the site information query request;

[0037] The information sending module is used to send the target site information to the terminal, so that the terminal can access the site corresponding to the target site information.

[0038] Thirdly, this application also provides a computer device, including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to implement the steps of the method described above.

[0039] Fourthly, this application also provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the steps of the method described above.

[0040] Fifthly, this application also provides a computer program product, including a computer program that, when executed by a processor, implements the steps of the method described in any of the above aspects.

[0041] The aforementioned terminal addressing method, apparatus, computer equipment, computer-readable storage medium, and computer program product receive addressing requests sent by terminals based on preset domain names, and query the local cache based on the vehicle information corresponding to the terminal carried in the addressing request. If the site information query result indicates that no target site information corresponding to the vehicle information is found, a site information query request is sent to a preset central addressing server based on the vehicle information, and the target site information returned by the central addressing server is received. This facilitates accurate acquisition of the access address through the central addressing server when no local match is found. Sending the target site information to the terminal enables the terminal to access the site corresponding to the target site information, which facilitates dynamic and accurate routing addressing for the terminal, avoiding the cumbersome update process caused by static configuration, thereby improving the efficiency of terminal access to sites. Attached Figure Description

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

[0043] Figure 1 This is a flowchart illustrating a terminal addressing method in one embodiment;

[0044] Figure 2 This is a schematic diagram of the global terminal dynamic addressing technology architecture in one embodiment;

[0045] Figure 3 This is a schematic diagram of global addressing data synchronization in one embodiment;

[0046] Figure 4 This is a schematic diagram of the dynamic addressing process of an APP in one embodiment;

[0047] Figure 5This is a schematic diagram of the vehicle dynamic addressing process in one embodiment;

[0048] Figure 6 This is a schematic diagram of a global two-level distributed vehicle-to-everything (V2X) cloud architecture in one embodiment;

[0049] Figure 7 This is a schematic diagram of a two-level distributed vehicle-to-everything (V2X) cloud architecture in the Eurasian region, as shown in one embodiment.

[0050] Figure 8 This is a structural block diagram of a terminal addressing device in one embodiment;

[0051] Figure 9 This is an internal structural diagram of a computer device in one embodiment. Detailed Implementation

[0052] To make the objectives, technical solutions, and advantages of this application clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the scope of this application.

[0053] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, data stored, data displayed, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of the relevant data must comply with relevant regulations.

[0054] As the automotive industry accelerates its transformation towards intelligence and connectivity, intelligent connected vehicles have become a strategic high ground in global automotive industry competition. Modern intelligent vehicles are equipped with hundreds of sensors and intelligent units, continuously generating massive amounts of data throughout the vehicle's lifecycle, covering multiple dimensions such as vehicle status, driving behavior, user information, and geographical location. This data not only supports the iterative upgrades of intelligent functions and provides a better user experience, but is also a key element in ensuring user safety and proactively mitigating risks.

[0055] However, with the in-depth expansion of Internet of Vehicles services to the global overseas market, the cross-border transmission of automotive data is facing unprecedented dual challenges of compliance and technology. There are significant differences in the compliance requirements for Internet of Vehicles data in various countries and regions, and the frequency of regulation updates and law enforcement intensity are also continuously increasing. The existing technical solutions for cross-border transmission of automotive data have been difficult to cope with the above complex market environment. Aiming at the issue of cross-border data information security compliance, the prior art has a system method for cross-border data transmission, which transmits automotive data from the overseas automotive enterprise data platform back to the domestic automotive enterprise data platform by designing a series of compliance review models in coordination with data encryption and decryption technologies, realizing compliant cross-border transmission of automotive data. However, this system method only supports one-way back transmission from overseas to the domestic territory, and is completely unable to adapt to high-compliance markets that require data not to leave the territory, and cannot meet the requirements of GDPR (General Data Protection Regulation). In addition, the traditional centrally deployed automotive Internet of Vehicles architecture generally has core defects such as insufficient data security and privacy protection, transmission performance that cannot meet service requirements, fragmented cross-domain data governance architecture, and difficult cloud service migration.

[0056] Therefore, developing an Internet of Vehicles data management and control method and system that can simultaneously meet the data compliance requirements of multiple global regions, take into account data security and transmission performance, and support dynamic adaptation and unified management has become a key technical problem to be solved urgently in the process of global development of automobile enterprises. The present application systematically solves the following three core technical problems: 1. Architectural conflict between global data localization regulations and centralized deployment, resulting in high compliance risks of sensitive data cross-border transmission; 2. Static domain name configuration on the terminal, which leads to the need for OTA (Over-the-Air Technology) upgrade for cloud site migration, featuring long cycles and slow launch in new markets; 3. Low cross-site data synchronization efficiency, poor consistency, fragmented distributed architecture, and high operation and maintenance costs.

[0057] In an exemplary embodiment, as shown in Figure 1 , a terminal addressing method is provided. This embodiment illustrates the application of the method to the regional central site addressing service end (server) as an example. It is understandable that the method can also be applied to a terminal device or a server, and can also be applied to a system including a terminal device and a server, and is implemented through the interaction between the terminal device and the server. The terminal devices may include, but are not limited to, various personal computers, notebook computers, smartphones, tablet computers and the like. The server may be an independent physical server, or a server cluster or distributed system composed of multiple physical servers, or a cloud server providing cloud computing services. In this embodiment, the method includes the following steps:

[0058] Step S101: Receive an addressing request sent by the terminal based on a preset domain name; the preset domain name is used to represent the basic domain name corresponding to the regional center station of the area where the terminal is located; the addressing request carries the vehicle information corresponding to the terminal.

[0059] Step S102: Based on the local cache of vehicle information query, obtain the query results of the station information corresponding to the vehicle information;

[0060] Step S103: If the site information query result indicates that no target site information corresponding to the vehicle information is found, a site information query request is sent to the preset central addressing server based on the vehicle information.

[0061] Step S104: Receive the target site information returned by the central addressing server in response to the site information query request;

[0062] Step S105: Send the target site information to the terminal so that the terminal can access the site corresponding to the target site information.

[0063] The terminal can be an in-vehicle communication device, an in-vehicle system, or a mobile device.

[0064] The regional center site addressing server can be a server or server cluster deployed in a data center in a preset geographical area, specifically responsible for handling terminal addressing network requests within that area.

[0065] Among them, the preset domain name can be a basic unified resource locator that is pre-assigned to each regional central site and has global stability.

[0066] Among them, an addressing request can be a network request message sent by a terminal to a server in order to obtain a service access address.

[0067] Vehicle information may include basic attribute data such as the vehicle's unique identification code, model number, country of sale code, or production plant identifier.

[0068] The local cache can be the vehicle addressing record data stored in the local cache medium of the regional central station addressing server.

[0069] The site information query results can be the matching status obtained after searching the local cache, including whether the target site information is matched or not.

[0070] The target site information can be the network access address of the regional edge site or regional center site that the terminal actually needs to access for business data interaction.

[0071] The central addressing server can be a master node or backup node server that serves as a global routing hub, storing global vehicle basic information and addressing rules.

[0072] Among them, the site information query request can be a network request message initiated by the regional center site addressing server to the central addressing server to obtain the target site information when the local center site addressing server fails to find the target site.

[0073] Optionally, the regional center site addressing server receives an addressing request sent by the terminal based on a preset domain name through a network interface. The preset domain name is used to represent the basic domain name corresponding to the regional center site in the region where the terminal is located. The addressing request carries the vehicle information corresponding to the terminal. The server extracts the vehicle information and queries the local cache based on the vehicle information to compare whether there is a matching historical record, thereby obtaining the site information query result corresponding to the vehicle information. If the site information query result indicates that no target site information corresponding to the vehicle information is found, the server generates a site information query request based on the vehicle information and sends the site information query request to the preset central addressing server. The server waits for and receives the target site information returned by the central addressing server after parsing the site information query request. The server encapsulates the target site information into a response message and sends it to the terminal, enabling the terminal to initiate a service connection based on the target site information, thereby accessing the site corresponding to the target site information.

[0074] For example, this application adopts a two-tiered distributed architecture of "regional central site + regional edge site", combining a unified layered deployment strategy, terminal dynamic addressing technology, and a hierarchical cross-site data synchronization mechanism to achieve seamless global vehicle access and data compliance management. Terminal dynamic addressing can completely solve the pain points of terminal static domain name configuration during market expansion and site migration. Terminal dynamic addressing technology requires that each regional central site be assigned a unique global base domain name, and all terminals access the addressing service by selecting the corresponding base domain name based on their own region. This domain name system has global stability and will not change due to the addition, migration, or deletion of edge sites. When a terminal starts up or reconnects, it sends a request to the regional central site addressing service with basic vehicle information. The regional central site addressing service first checks its local cache; if it does not find the match, it sends a query request to the central dynamic addressing service master node.

[0075] Figure 2This is a global terminal dynamic addressing technology architecture diagram. The diagram shows the domestic online filling system, production line, and multiple sites (sites 3.1 to 3.6). Each site includes dynamic addressing services, production line integration services, and a sales system. The central site and central backup site include the TSP (Telematics Service Provider) cloud platform, dynamic addressing services (services 3.1 and 3.2), and the TSP kernel (services 3.3 to 3.7, etc.). The dynamic addressing service database includes an information configuration table, a global vehicle basic information table, and a global vehicle sales information table. The diagram indicates that only vehicles and sales countries are synchronized. After vehicle ignition, the vehicle's business domain name is obtained through the basic domain name and addressing address for business access and long-term connection establishment. The dynamic addressing service contains basic vehicle information from overseas global sites, including vehicle model, series, and sales country. The business domain name is selected based on the vehicle's sales country or model code. The APP (Application) retrieves the business access domain name based on the base domain name to access services, including long-connection address lookup. The user interface retrieves the business domain name based on the user's selected region / country. The Dynamic Addressing Service is the global routing hub of this architecture. It is a lightweight, stateless service specifically designed for global access in the Internet of Vehicles (IoV). It does not carry any business logic and is only responsible for addressing and routing distribution. The data scope of the Dynamic Addressing Service strictly follows the principle of data minimization, storing only the minimum necessary basic information for all vehicles globally: unique vehicle identifier, model, series, configuration information, sales country, region code, and manufacturing plant information. It does not store any business data (such as vehicle driving trajectory, user personal information, etc.), ensuring high performance, high security, and low storage costs. The Dynamic Addressing Service receives addressing requests from the APP or vehicle terminal to the cloud platform and returns the optimal business access domain name based on preset regional routing rules and network latency policies. Each regional central station independently deploys dynamic addressing service instances to handle addressing requests from vehicles within its region, providing low-latency, nearest-access services, maintaining real-time data synchronization with the central station to ensure the accuracy of addressing information, and locally caching addressing information for frequently used vehicles to improve response speed.

[0076] Figure 3This is a global addressing data synchronization diagram. The diagram shows the production line, production line filling platform, and sites 4.1 to 4.3 (including production line integration services and sales services). Data is synchronized to the central site's dynamic addressing service, including basic vehicle information and sales information. Synchronization methods include asynchronous synchronization and binlog (Binary Log) monitoring, synchronizing only vehicles and sales countries. The basic vehicle information required for terminal dynamic addressing comes from the factory's production line filling platform. Data consistency and real-time performance are ensured through three levels of synchronization: First, the production line filling platform periodically synchronizes vehicle information to all regional central sites. Second, through database binlog monitoring technology, incremental data from each regional central site is synchronized to the central dynamic addressing service master node. Finally, also through binlog monitoring technology, the master node's full data is synchronized to the backup node. The dynamic addressing service instance from the factory production line system to the regional center site uses message queues for timed synchronization. The data synchronization between the dynamic addressing service instance of the regional center site and the main node and backup nodes of the dynamic addressing service from the regional sales system to the center site uses database binlog listening technology for asynchronous synchronization.

[0077] Figure 4This is a flowchart of the APP's dynamic addressing process. The diagram illustrates the APP, Service 6.1, the dynamic addressing service allocated by the intelligent DNS (Domain Name System), the central site's dynamic addressing service, and the business system. The process includes: the APP uses its base domain name to query the list of countries supported by the APP; Service 6.1 responds with the country list information; the APP initiates an addressing request; the dynamic addressing service allocated by the intelligent DNS checks the cache based on the addressing information; if the address exists, it responds with the result, and the APP initiates a business request; if the cache does not exist, it queries the dynamic addressing center. The central site's dynamic addressing service queries the configured domain name information based on the country information carried in the addressing parameters. If the query to the central node times out or fails, it queries the central backup node. If the central node does not find the address, it returns the default dynamic addressing configuration. Finally, it sets the cache to 12 hours and responds with the result. The base domain name accessed by the APP to the cloud is globally unified. After the app launches, it uses the Unified Basic Domain Name Access Service 6.1 to query and obtain the list of countries supported by the app. After the user selects the target country, the app initiates a lookup request to the dynamic addressing service assigned by the intelligent DNS. This dynamic addressing service first checks the local cache. If a valid record exists, it directly returns the result to the app. If the cache is not found, it initiates a lookup request to the dynamic addressing service at the central site. The central dynamic addressing service queries and returns the corresponding configured domain name information based on the country information carried in the request parameters. If the primary central node responds with a timeout or fails, the dynamic addressing service assigned by the intelligent DNS will automatically switch to the central backup node for querying. If neither the primary nor backup central nodes find valid information, the default dynamic addressing configuration is returned to the app. Regardless of the final query result, the dynamic addressing service assigned by the intelligent DNS will cache the lookup result for 12 hours. Finally, the app uses the obtained lookup result to directly initiate subsequent business requests to the corresponding business system.

[0078] In the aforementioned terminal addressing method, by receiving the addressing request sent by the terminal based on a preset domain name, and querying the local cache based on the vehicle information corresponding to the terminal carried in the addressing request, if the site information query result indicates that no target site information corresponding to the vehicle information is found, a site information query request is sent to a preset central addressing server based on the vehicle information, and the target site information returned by the central addressing server is received. This is beneficial for accurately obtaining the access address through the central addressing server when the local address is not found. Sending the target site information to the terminal enables the terminal to access the site corresponding to the target site information, which is beneficial for the terminal to achieve dynamic and accurate routing addressing, avoiding the cumbersome update process caused by static configuration, thereby improving the efficiency of terminal access to sites.

[0079] In an exemplary embodiment, the central addressing server includes a primary server and a backup server. The process of sending a site information query request to a preset central addressing server based on vehicle information includes: sending a site information query request to the primary server based on vehicle information; and receiving target site information returned by the central addressing server in response to the site information query request, including: receiving the target site information returned by the primary server in response to the site information query request if the primary server responds successfully; and sending a site information query request to the backup server based on vehicle information in response to the site information query request if the primary server's response to the site information query request times out or fails, and receiving the target site information returned by the backup server in response to the site information query request.

[0080] The main server can be deployed at a regional central site or a preset central site, and has a complete dynamic addressing database, serving as the preferred query node for global addressing data.

[0081] The backup server can be a server deployed at a regional center site or another preset center site that is geographically independent from the main server, used to temporarily take over addressing requests when the main server fails.

[0082] A successful response can be defined as the main server successfully parsing the site information query request and returning a response message containing the target site information within a preset time threshold.

[0083] Among them, response timeout can be the state in which the main server fails to return a response message within a preset time threshold after receiving a site information query request.

[0084] Among them, a response failure may be due to an error occurring on the main server during the processing of a site information query request, resulting in an error code or a failure to establish a connection.

[0085] Optionally, the regional center site addressing server sends a site information query request to the main server based on the vehicle information; if the main server successfully responds to the site information query request, the regional center site addressing server receives the target site information returned by the main server; if the main server's response to the site information query request times out or fails, the regional center site addressing server sends a site information query request to the backup server based on the vehicle information, and receives the target site information returned by the backup server.

[0086] For example, if the central dynamic addressing service master node times out or fails to respond, the system automatically switches to the backup node for querying. The central dynamic addressing service master node and backup node are deployed on two geographically independent regional center sites to achieve off-site disaster recovery. The terminal dynamic addressing service relies on a global two-tier distributed vehicle network cloud architecture, adopting a layered deployment mode of dual-center dynamic addressing service master and backup (the central dynamic addressing service master node and backup node are two of the regional center nodes) and multiple regional center site dynamic addressing service instances to achieve global coverage and high availability. The central dynamic addressing service node possesses a complete dynamic addressing database, information configuration table, global vehicle basic information table, and global vehicle sales information table. As the sole source of global addressing data, it is responsible for synchronizing and updating dynamic addressing data for all regional center sites globally. When the central dynamic addressing service master node fails, the central dynamic addressing service backup node temporarily takes over the addressing requests from the dynamic addressing services of each regional center site to achieve disaster recovery backup.

[0087] The technical solution provided in this embodiment receives target site information when the main server responds successfully, and sends a query request to the backup server and receives target site information when the main server responds timeout or fails. This facilitates automatic switching to the backup node when the main node fails, realizing off-site disaster recovery backup, and thus improving the stability of the addressing service.

[0088] In an exemplary embodiment, the vehicle information includes actual sales area information, preset sales area information, and configuration code area information; sending a site information query request to a preset central addressing server includes: sending a site information query request to the central addressing server, so that the central addressing server selects the corresponding information for site query according to a preset priority order to obtain the target site information; the preset priority order is used to characterize the selection priority among actual sales area information, preset sales area information, and configuration code area information.

[0089] Among them, the actual sales region information can be the coding information of the country or region where the vehicle is actually sold and registered.

[0090] The preset sales area information can be the coding information of the country or region where the vehicle is scheduled to be sold, which is obtained by parsing the vehicle's unique identification code.

[0091] The configuration coding region information can be the coding information of the country or region corresponding to the vehicle model configuration code.

[0092] The preset priority order can be a pre-defined query rule, matching according to the order of actual sales area information, preset sales area information, and configuration code area information.

[0093] Optionally, the regional center site addressing server sends a site information query request to the central addressing server, enabling the central addressing server to select the corresponding information for site querying according to a preset priority order to obtain the target site information. The preset priority order represents the selection priority among actual sales area information, preset sales area information, and configuration code area information. Upon receiving the site information query request, the central addressing server sequentially matches the actual sales area information, preset sales area information, and configuration code area information carried in the vehicle information according to the preset priority order. It first determines whether the vehicle information carries valid actual sales area information. If it does, the target site information is determined based on the actual sales area information; if not, the target site information is determined based on the preset sales area information; if the preset sales area information is also invalid, the target site information is determined based on the configuration code area information; if no valid target site information is found among the above three types of information, the central addressing server returns an empty list or default site information. For example, the central dynamic addressing service master node matches according to priority: the country of vehicle sale, the country of vehicle code preset for sale, and the country corresponding to the vehicle model configuration code. If the match is successful, the corresponding basic domain name is returned; otherwise, an empty list is returned.

[0094] The technical solution provided in this embodiment enables the central addressing server to select actual sales area information, preset sales area information, and configuration code area information for site query according to a preset priority order. This facilitates multi-level backtracking matching based on the actual status and configuration information of the vehicle, thereby improving the accuracy and success rate of target site information query.

[0095] In an exemplary embodiment, after receiving the target site information returned by the central addressing server in response to the site information query request, the method further includes: storing the association between the vehicle information and the target site information in a local cache; and setting the cache expiration time of the association based on the actual sales status of the vehicle information.

[0096] The association relationship can be a mapping and matching relationship between vehicle information and the corresponding target station information.

[0097] The actual sales status can be an indicator of whether the vehicle has been sold and registered for use.

[0098] The cache expiration time can be the length of time that the association remains valid in the local cache. After the expiration time is exceeded, the association will be cleared or marked as invalid.

[0099] Optionally, after receiving the target site information returned by the central addressing server, the regional central site addressing server establishes an association between the target site information and the corresponding vehicle information, and writes the association into the local cache so that when a subsequent addressing request corresponding to the same vehicle information is received, the target site information can be directly obtained from the local cache. The regional central site addressing server sets different cache expiration times for the association according to the actual sales status carried in the vehicle information. The cache expiration times set for vehicle information with different actual sales statuses are also different.

[0100] For example, Figure 5 This is a flowchart of the vehicle dynamic addressing process. The diagram shows the vehicle, the dynamic addressing service at the vehicle's location, the central site's dynamic addressing service, and the business system. The process includes: the vehicle initiates an addressing request; the dynamic addressing service at the vehicle's location queries the cache based on the addressing information; if the information exists, it responds with the result, and the vehicle makes a business request; if the cache does not exist, it queries the dynamic addressing center. The central site's dynamic addressing service executes the following logic: 1. Based on the VIN (Vehicle Identification Number) in the addressing parameters, it queries the vehicle's sales information. If the vehicle has already been sold, it returns configuration information based on the country of sale; 2. If no sales record is found, it queries the country of sale based on the VIN and returns configuration information based on the country of sale; 3. If no vehicle information is found, it responds with the configuration information using the parameter country code; 4. If no record is found, it responds with an empty list. If the query to the central node times out or fails, it queries the central backup node. If the central node does not find the information, it returns the default dynamic addressing configuration. Finally, the addressing results are cached, with different expiration times depending on whether the vehicle has been actually sold: 12 hours for vehicles already sold, and 10 minutes for those not yet sold. The final response is as follows: After a vehicle powers on, it first sends an addressing request to the dynamic addressing service of its local station. The station's dynamic addressing service first checks its local cache; if a valid record exists, it directly returns the result to the vehicle. If the cache misses, it sends a query request to the central station's dynamic addressing service. The central station's dynamic addressing service queries the vehicle's actual sales information (returning the configuration based on the actual sales country), the sales country information parsed from the VIN code, and the country code in the request parameters, in that order. If none of these are found, an empty list is returned. If the primary central node's response times out or fails, the station's dynamic addressing service automatically switches to the central backup node for querying. If neither the primary nor backup central nodes find valid information, the station's dynamic addressing service returns the default dynamic addressing configuration to the vehicle. Regardless of the query result, the station's dynamic addressing service caches the addressing result.

[0101] The technical solution provided in this embodiment stores the association between vehicle information and target site information in a local cache, and sets the cache expiration time of the association according to the actual sales status of the vehicle information. This helps to reduce repeated query requests to the central addressing server, reduce network overhead, and dynamically adjust the caching strategy according to the vehicle status, thereby improving the addressing response speed while ensuring addressing accuracy.

[0102] In an exemplary embodiment, the cache expiration time of the association is set according to the actual sales status of the vehicle information, including: when the actual sales status is "already sold", the cache expiration time is set to a first time; when the actual sales status is "not sold", the cache expiration time is set to a second time; the first time is longer than the second time.

[0103] The "sold" status can refer to a situation where the vehicle has completed the sales process and its region of origin is relatively stable.

[0104] The first duration can be a longer cache validity period set for vehicles that have already been sold, such as 12 hours.

[0105] The "not yet sold" status can refer to a situation where the vehicle has not yet been sold and its final ownership region may change.

[0106] The second duration can be a shorter cache validity period set for vehicles that are not yet sold, such as 10 minutes.

[0107] Optionally, the regional central site addressing service determines the actual sales status carried in the vehicle information. If the actual sales status indicates that the vehicle has been sold, the cache expiration time of the association corresponding to the vehicle information is set to a first duration, such as 12 hours. If the actual sales status indicates that the vehicle has not yet been sold, the cache expiration time of the association corresponding to the vehicle information is set to a second duration, which is less than the first duration, such as 10 minutes. This allows the target site information corresponding to vehicles that have not yet been sold to be updated again from the central addressing service within a relatively shorter period. For example, the site dynamic addressing service sets differentiated expiration times based on the vehicle status: 12 hours for vehicles that have been sold and 10 minutes for vehicles that have not yet been sold. Finally, after the vehicle obtains the addressing result, it directly initiates subsequent business requests to the corresponding business system.

[0108] The technical solution provided in this embodiment, by setting a longer first duration when the vehicle is already sold and a shorter second duration when it is not sold, is conducive to adopting differentiated caching strategies for vehicles in different states. For vehicles with stable states, the frequency of queries is reduced, while for vehicles with volatile states, the addressing information is updated in real time, thereby helping to ensure the reliability of the addressing results.

[0109] In an exemplary embodiment, the site includes a regional center site or a regional edge site under the jurisdiction of the regional center site; the method further includes: receiving non-sensitive business data synchronized by the regional edge site; the non-sensitive business data being uploaded by the terminal to the regional edge site; and storing and processing the non-sensitive business data.

[0110] Among them, regional edge sites can be lightweight cloud computing nodes deployed in specific countries or regions with strict requirements for data localization, responsible for local data processing and compliant storage.

[0111] Non-sensitive business data can be business statistics or management data generated by the terminal during the use of vehicle networking services, which does not contain user personal privacy and is allowed to be transmitted across borders.

[0112] Optionally, after the terminal completes addressing and accesses the regional edge station corresponding to the target station information, it uploads the non-sensitive business data generated during the business process to the regional edge station. The regional edge station processes the received non-sensitive business data locally and then synchronizes the non-sensitive business data to its regional center station according to a preset synchronization strategy. The regional center station's addressing server receives the non-sensitive business data, stores it, and performs corresponding business processing on the non-sensitive business data based on preset business processing logic.

[0113] For example, Figure 6 This is a global two-tier distributed vehicle-to-everything (V2X) cloud architecture diagram. The dashed circles in the diagram represent regions divided by geographical location (each circle contains one or more countries or regions). Solid-marked regional center sites cover multiple countries or regions within geographically adjacent dashed circles with similar regulatory requirements; hollow-marked regional edge nodes are deployed in a single country or region with strict data localization requirements. Regional center sites are centralized computing and business centers within a region, covering multiple surrounding countries and regions, responsible for large-scale V2X core business processing and unified service management and scheduling within the region. Regional center sites are also regional data compliance centers, receiving and processing business data directly accessing vehicles and non-sensitive business data from edge sites, while meeting the data compliance requirements of surrounding countries. Regional edge sites are lightweight deployment nodes based on regional center sites, covering all business scenarios with strong compliance requirements. Deployed in markets with strict data localization requirements, they are responsible for local data processing, storage, and compliance implementation, ensuring local user data does not leave the country, and only synchronizing non-sensitive business data and necessary management data to their respective regional center sites as needed. Regional edge sites support the efficient operation of core businesses within the market, providing a low-latency, highly reliable service experience.

[0114] For example, Figure 7 This is a two-tier distributed vehicle-to-everything (V2X) cloud architecture diagram for the Eurasian region. The diagram includes the Eurasian site and the A-country cloud (country A is located within the Eurasian region), both based on IaaS (Infrastructure as a Service) public cloud infrastructure versions 2.6.1 and 2.6.2. It includes third-party dependencies, the APP access layer (modules 2.1.1 to 2.1.3), the TSP kernel (modules 2.2.1 to 2.2.3), PaaS (Platform as a Service) services (modules 2.3.1 to 2.3.3), the vehicle access layer (modules 2.4.1 to 2.4.3), and modules 2.5.1 to 2.5.3, etc. The A-country cloud retains only some core services and synchronizes data to the Eurasian site through non-sensitive data synchronization. The Eurasia site is the regional hub, deploying all cloud services in Country B (located in the Eurasia region). It covers all countries and regions in the Eurasia region with similar regulatory requirements to Country B. The Country A site is the regional edge site, deployed in a lightweight manner on top of the Eurasia site. It retains full services for the APP access layer and vehicle access layer, while the TSP kernel and PaaS service layer retain only essential core vehicle networking services. User-related data generated during vehicle use is stored on local servers, while business statistics and other non-sensitive data are periodically synchronized from the Country A site to the Eurasia site via message queues. Notably, many public capabilities, such as the system management backend and SIM (Subscriber Identity Module) card operator integration, are deployed only on the Eurasia site, providing corresponding capabilities to the Country A site through synchronization and remote calls.

[0115] Both regional central and regional edge sites adopt a standard four-layer layered deployment architecture, based on an IaaS public cloud platform, sequentially deploying the vehicle-to-everything (V2X) PaaS service layer, V2X application layer services, and terminal access layer services, forming a closed loop of V2X services. This strategy decouples hardware and software resources, ensures the consistency of technical architecture between edge and central sites, and significantly reduces the deployment complexity and maintenance costs of edge sites. A unified cross-site data synchronization standard and protocol are established, employing a data hierarchical classification strategy: sensitive data is strictly restricted to storage on the local edge site, and only non-sensitive business statistics and management data are synchronized. The synchronization process uses incremental synchronization, breakpoint resumption, and data encryption and verification technologies to ensure the security, efficiency, and consistency of data synchronization.

[0116] The technical solution provided in this embodiment, by receiving, storing, and processing non-sensitive business data synchronized from regional edge sites, facilitates centralized management and analysis of global non-sensitive data while meeting the localization compliance requirements for sensitive data. This helps address the fragmentation problem of cross-domain data governance and enhances the unified operation and maintenance capabilities of global connected vehicles. By storing all sensitive data locally at edge sites, the data localization regulations of major countries and regions worldwide are fundamentally met. Non-sensitive data is transmitted across borders on demand, minimizing compliance risks. Unified deployment of management services and lightweight deployment of business services at edge sites significantly reduce deployment costs per edge site; unified operation and maintenance of global sites is achieved, significantly improving operational efficiency. Through unified data standards and synchronization mechanisms, the fragmentation problem of cross-domain data governance is solved, enabling unified management, analysis, and operation of global vehicle data, providing data support for automakers' global decision-making.

[0117] In an exemplary embodiment, after obtaining the query result of the station information corresponding to the vehicle information based on the local cache of the vehicle information query, the method further includes: if the station information query result indicates that the target station information corresponding to the vehicle information has been found, retrieving the target station information from the local cache.

[0118] Optionally, after querying the local cache based on vehicle information, the regional central site addressing server determines the content represented by the obtained site information query result. If the site information query result indicates that there is already valid target site information corresponding to the vehicle information in the local cache, the regional central site addressing server directly reads the target site information from the local cache without initiating a site information query request to the central addressing server, and sends the read target site information to the terminal.

[0119] The technical solution provided in this embodiment, by directly retrieving the target site information from the local cache when the site information query result indicates that the target site information has been found, helps to avoid initiating a network request to the central addressing server, thereby shortening the addressing response time and improving the terminal access efficiency.

[0120] It should be understood that although the steps in the flowcharts of the embodiments described above are shown sequentially according to 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 embodiments described above may include multiple steps or multiple stages. These steps or stages are not necessarily completed at the same time, but can be executed at different times. The execution order of these steps or stages is not necessarily sequential, but can be performed alternately or in turn with other steps or at least some of the steps or stages of other steps.

[0121] Based on the same inventive concept, this application also provides a terminal addressing apparatus for implementing the terminal addressing method described above. The solution provided by this apparatus is similar to the implementation described in the above method; therefore, the specific limitations in one or more terminal addressing apparatus embodiments provided below can be found in the limitations of the terminal addressing method described above, and will not be repeated here.

[0122] In one exemplary embodiment, such as Figure 8 As shown, a terminal addressing device is provided, applied to a regional central station addressing server. The terminal addressing device 800 may include:

[0123] The request receiving module 801 is used to receive the addressing request sent by the terminal based on the preset domain name; the preset domain name is used to represent the basic domain name corresponding to the regional center station of the area where the terminal is located; the addressing request carries the vehicle information corresponding to the terminal.

[0124] The information query module 802 is used to query the local cache of vehicle information and obtain the query results of the station information corresponding to the vehicle information.

[0125] The request sending module 803 is used to send a site information query request to a preset central addressing server based on the vehicle information when the site information query result indicates that no target site information corresponding to the vehicle information is found.

[0126] The information receiving module 804 is used to receive the target site information returned by the central addressing server in response to the site information query request;

[0127] The information sending module 805 is used to send target site information to the terminal, enabling the terminal to access the site corresponding to the target site information.

[0128] In an exemplary embodiment, the central addressing server includes a primary server and a backup server; the request sending module 803 is further configured to send a site information query request to the primary server based on vehicle information; the information receiving module 804 is further configured to receive the target site information returned by the primary server in response to the site information query request if the primary server responds successfully to the site information query request; and to send a site information query request to the backup server based on vehicle information and receive the target site information returned by the backup server in response to the site information query request if the primary server responds to the site information query request with a timeout or fails to respond.

[0129] In an exemplary embodiment, the vehicle information includes actual sales area information, preset sales area information, and configuration code area information; the request sending module 803 is further configured to send a site information query request to the central addressing server, so that the central addressing server selects the corresponding information to query the site according to a preset priority order, and obtains the target site information; the preset priority order is used to characterize the selection priority among actual sales area information, preset sales area information, and configuration code area information.

[0130] In an exemplary embodiment, the device 800 further includes: a duration setting module, used to store the association between vehicle information and target site information in a local cache; and to set the cache expiration duration of the association according to the actual sales status of the vehicle information.

[0131] In an exemplary embodiment, the duration setting module is further configured to set the cache expiration duration to a first duration when the actual sales status is "actually sold" and to set the cache expiration duration to a second duration when the actual sales status is "not actually sold"; the first duration is longer than the second duration.

[0132] In an exemplary embodiment, the site includes a regional center site or a regional edge site under the jurisdiction of the regional center site; the device 800 further includes: a data processing module, used to receive non-sensitive business data synchronized by the regional edge site; the non-sensitive business data is uploaded by the terminal to the regional edge site; and the non-sensitive business data is stored and processed.

[0133] In an exemplary embodiment, the device 800 further includes an information acquisition module, configured to acquire target site information from a local cache when the site information query result indicates that target site information corresponding to vehicle information has been found.

[0134] Each module in the aforementioned terminal addressing device can be implemented entirely or partially through software, hardware, or a combination thereof. These modules can be embedded in the processor of a computer device in hardware form or independent of it, or stored in the memory of the computer device in software form, so that the processor can call and execute the operations corresponding to each module.

[0135] In one exemplary embodiment, a computer device is provided, which may be a server, and its internal structure diagram may be as follows: Figure 9 As shown, this computer device includes a processor, memory, input / output (I / O) interfaces, and a communication interface. The processor, memory, and I / O interfaces are connected via a system bus, and the communication interface is also connected to the system bus via the I / O interfaces. The processor provides computational and control capabilities. The memory includes non-volatile storage media and internal memory. The non-volatile storage media stores the operating system, computer programs, and a database. The internal memory provides the environment for the operation of the operating system and computer programs stored in the non-volatile storage media. The database stores data related to terminal addressing methods. The I / O interfaces are used for exchanging information between the processor and external devices. The communication interface is used for communicating with external terminals via a network connection. When the computer program is executed by the processor, it implements a terminal addressing method.

[0136] Those skilled in the art will understand that Figure 9 The structure shown is merely a block diagram of a portion of the structure related to the present application and does not constitute a limitation on the computer device to which the present application is applied. Specific computer devices may include more or fewer components than those shown in the figure, or combine certain components, or have different component arrangements.

[0137] In one exemplary embodiment, a computer device is also provided, including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to implement the steps in the above-described method embodiments.

[0138] In one exemplary embodiment, a computer-readable storage medium is provided having a computer program stored thereon that, when executed by a processor, implements the steps in the above-described method embodiments.

[0139] In one exemplary embodiment, a computer program product is provided, including a computer program that, when executed by a processor, implements the steps in the above-described method embodiments.

[0140] Those skilled in the art will understand that all or part of the processes in the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a non-volatile computer-readable storage medium. When executed, the computer program can include the processes of the embodiments described above. Any references to memory, databases, or other media used in the embodiments provided in this application can include at least one of non-volatile and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. By way of illustration and not limitation, RAM can take many forms, such as Static Random Access Memory (SRAM) or Dynamic Random Access Memory (DRAM). The databases involved in the embodiments provided in this application may include at least one type of relational database and non-relational database. Non-relational databases may include, but are not limited to, blockchain-based distributed databases. The processors involved in the embodiments provided in this application may be general-purpose processors, central processing units, graphics processing units, digital signal processors, programmable logic devices, quantum computing-based data processing logic devices, etc., and are not limited to these.

[0141] The technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0142] The embodiments described above are merely illustrative of several implementation methods of this application, and while the descriptions are specific and detailed, they should not be construed as limiting the scope of this patent application. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of this application, and these all fall within the protection scope of this application. Therefore, the protection scope of this application should be determined by the appended claims.

Claims

1. A terminal addressing method, characterized in that, The method, applied to a regional central site addressing server, includes: The receiving terminal sends an addressing request based on a preset domain name; the preset domain name is used to represent the basic domain name corresponding to the regional center station of the area where the terminal is located; the addressing request carries vehicle information corresponding to the terminal; Based on the local cache of the vehicle information query, the query results of the station information corresponding to the vehicle information are obtained; If the site information query result indicates that no target site information corresponding to the vehicle information is found, a site information query request is sent to the preset central addressing server based on the vehicle information. Receive the target site information returned by the central addressing server in response to the site information query request; The target site information is sent to the terminal, enabling the terminal to access the site corresponding to the target site information.

2. The method according to claim 1, characterized in that, The central addressing server includes a main server and a backup server; The step of sending a station information query request to a preset central addressing server based on the vehicle information includes: Based on the vehicle information, a site information query request is sent to the main server; The step of receiving the target site information returned by the central addressing server in response to the site information query request includes: If the main server successfully responds to the site information query request, the target site information returned by the main server in response to the site information query request is received. If the main server times out or fails to respond to the site information query request, it sends the site information query request to the backup server based on the vehicle information, and receives the target site information returned by the backup server in response to the site information query request.

3. The method according to claim 1, characterized in that, The vehicle information includes actual sales area information, preset sales area information, and configuration code area information; Sending a site information query request to a preset central addressing server includes: The system sends a site information query request to the central addressing server, which then selects the corresponding information to query the site according to a preset priority order to obtain the target site information. The preset priority order is used to characterize the selection priority among the actual sales area information, the preset sales area information, and the configuration code area information.

4. The method according to claim 1, characterized in that, After receiving the target site information returned by the central addressing server in response to the site information query request, the process further includes: The association between the vehicle information and the target station information is stored in the local cache; Based on the actual sales status of the vehicle information, set the cache expiration time for the association relationship.

5. The method according to claim 4, characterized in that, The step of setting the cache expiration time of the association relationship based on the actual sales status of the vehicle information includes: If the actual sales status is "actually sold", the cache expiration time is set to the first time. If the actual sales status is not actual sales status, the cache expiration time is set to a second time; the first time is longer than the second time.

6. The method according to claim 1, characterized in that, The site includes the regional center site or the regional edge site under the jurisdiction of the regional center site; The method further includes: The terminal receives non-sensitive service data synchronized from the regional edge station; the non-sensitive service data is uploaded by the terminal to the regional edge station. The non-sensitive business data is stored and processed.

7. The method according to any one of claims 1 to 6, characterized in that, After obtaining the station information query result corresponding to the vehicle information based on the local cache of the vehicle information, the process further includes: If the query result indicates that the target station information corresponding to the vehicle information has been found, the target station information is retrieved from the local cache.

8. A terminal addressing device, characterized in that, The device, applied to a regional central site addressing server, includes: The request receiving module is used to receive an addressing request sent by the terminal based on a preset domain name; the preset domain name is used to represent the basic domain name corresponding to the regional center station of the area where the terminal is located; the addressing request carries the vehicle information corresponding to the terminal; The information query module is used to query the local cache based on the vehicle information to obtain the query results of the station information corresponding to the vehicle information; The request sending module is used to send a site information query request to a preset central addressing server based on the vehicle information when the site information query result indicates that no target site information corresponding to the vehicle information is found. The information receiving module is used to receive the target site information returned by the central addressing server in response to the site information query request; The information sending module is used to send the target site information to the terminal, so that the terminal can access the site corresponding to the target site information.

9. A computer device comprising a memory and a processor, wherein the memory stores a computer program, characterized in that, When the processor executes the computer program, it implements the steps of the method according to any one of claims 1 to 7.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 7.

11. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 7.

Images