A switching method and system supporting third-party pre-embedded nested local coordinates

Abstract

The application discloses a switching method and system supporting third-party pre-embedded nested local coordinates, and the core innovation is to first open the capability of pre-embedding a nested local coordinate system in a public digital map by a third party, and to realize accurate switching of the third-party pre-embedded local coordinates and global coordinates through a local interaction environment with exclusive resource allocation, data context isolation and fault isolation features, thereby solving the problems of unified control of the existing digital map coordinate system by a platform, abnormal local interaction affecting the whole, and unreasonable resource allocation; the application further improves the practicability and creativity of the scheme by preferably combining a three-dimensional virtual earth as a space carrier and a double time line as a space-time synchronization mechanism, thereby solving the local coordinate data conflict problem of multiple versions and multiple time dimensions and guaranteeing the space-time consistency of local interaction; the core protection point of the application focuses on "third-party pre-embedded nested local coordinates and switching logic + exclusive resource, data and fault isolation local interaction environment", and can be widely applied to fields such as metaverse social interaction, offline commercial digitization, industrial digital twin and smart tourism, thereby supporting diversified customized interaction demands and improving the ecological capability and stability of digital maps.

Description

Technical Field

[0001] This invention belongs to the technical fields of digital maps (including virtual globes and digital globes), coordinate positioning and switching, and LBS (Location-Based Services). Specifically, it relates to a method and system for switching third-party pre-embedded nested local coordinates. Through a local interactive environment (sandbox) with core features such as dedicated resource allocation, data context isolation, and fault isolation, it achieves precise switching between third-party pre-embedded nested local coordinates and global coordinates. It is applicable to scenarios such as metaverse social networking, offline commercial digitization, industrial digital twins, smart cultural tourism, and enterprise internal collaboration, supporting high-precision spatiotemporal interaction across multiple terminals and scenarios. This invention preferably uses a three-dimensional virtual globe as a spatial carrier and dual timelines as a spatiotemporal synchronization mechanism to further enhance the practicality and creativity of the solution. However, the three-dimensional virtual globe and dual timelines are preferred implementations and do not constitute a limitation on the core protection point of this invention. The core protection point of this invention is "third-party pre-embedded nested local coordinates and switching logic + a local interactive environment with dedicated resources, data, and fault isolation features". Background Technology

[0002] In existing digital map and metaverse-related technologies, the coordinate management of local areas mostly adopts the "globally unified coordinates" or "single local coordinates" mode, without establishing a flexible linkage architecture between global and local coordinates, and the core technologies have the following key gaps: 1. The ability for third parties to pre-embed local coordinates is not open: The coordinate system of existing digital maps is uniformly controlled by the platform. Third-party developers cannot pre-embed their own local coordinate system in public digital maps, cannot build their own local interactive space in public maps, and cannot meet the customized local interactive needs of third parties, which limits the large-scale access of third-party content ecosystems. 2. Lack of an effective architecture for global-local isolation: Existing technologies do not distinguish between the independent operating states of global roaming and local interaction. Global and local resources, coordinates, and data contexts are deeply coupled. Anomalies in local interactions can easily affect the stability of the global system, and it is impossible to allocate dedicated resource pools for local areas. The smoothness of interaction is significantly affected by the global system load. Similar isolation solutions in existing technologies (such as scene loading in game engines, iframe sandboxes in the web, and containerization in cloud computing) only achieve logical isolation and do not achieve dedicated resource allocation and fault isolation. They cannot meet the requirements of high-precision and high-stability local interaction, and cannot support the strict requirements of scenarios such as AR / VR and industrial remote control. 3. Low accuracy and lack of calibration mechanism in global-local coordinate switching: Existing technologies have not established a standardized global-local coordinate bidirectional mapping method, which makes it easy for offset errors to occur during coordinate switching. Furthermore, they do not combine spatial reference services for real-time calibration, which cannot meet the high-precision coordinate requirements of scenarios such as high-precision AR / VR interaction and remote control of industrial equipment. 4. Lack of multi-dimensional access control: The existing local areas do not have a differentiated access control system designed for third-party pre-embedded scenarios, which cannot achieve multi-dimensional access control of "public / member / employee / password / operation permission level", which is prone to problems such as access leakage or overly strict control; 5. Insufficient spatiotemporal synchronization capability: Existing technologies do not combine third-party pre-embedded local coordinates with efficient spatiotemporal synchronization solutions, which cannot solve the problem of synchronizing local coordinate data across different timelines. Local coordinate data with multiple versions and multiple time dimensions are prone to conflicts, failing to meet the spatiotemporal consistency requirements for high-precision interaction.

[0003] To address the aforementioned issues, there is an urgent need for a switching technology that supports third-party pre-embedded local coordinates, filling the gap in the existing digital maps' ability to provide customized local interactions with third parties. This would enable seamless integration of "global roaming + precise local interaction," supporting the industrialization of the metaverse across multiple scenarios. This invention solves the problem of insufficient isolation in existing technologies by providing a local interactive environment (sandbox) with dedicated resources, data, and fault isolation features. Furthermore, it optimizes the combination of a three-dimensional virtual earth carrier and a dual-timeline spatiotemporal synchronization mechanism to further enhance the practicality and creativity of the solution, while achieving core protection points without relying on this carrier and synchronization mechanism.

[0004] Explanation of terms related to "virtual earth," "digital earth," and "digital map": In this application, the terms "Virtual Earth," "Digital Earth," or "Digital Map" do not refer to any specific commercial software product or a particular geographic data source.

[0005] In this application, the aforementioned terms are uniformly defined as: a multi-dimensional data visualization carrier based on computer graphics and possessing a spatial coordinate reference system. Its core technical features include: Spatial index structure: Supports mapping geographic or non-geographic spatial data to a unified coordinate system (such as latitude and longitude coordinate system, Cartesian coordinate system or custom local coordinate system); Multi-level rendering mechanism: It has the ability to manage multiple levels of detail (LOD) and can dynamically load geometric models, texture maps and attribute data of different precision according to the viewing perspective; Spatiotemporal data carrier: Serves as the runtime environment container for the "dual timeline retrieval", "local coordinate switching" and "computing power collaboration" methods described in this application, and is used to carry and display spatiotemporal objects and their associated logical scripts.

[0006] It should be noted that the technical solutions of this application are also applicable to two-dimensional planar maps, three-dimensional city information models (CIM), indoor navigation maps, game scene engines, and abstract data spaces of any dimension. Any substitution of the above terms with other digital carriers possessing spatial indexing and rendering capabilities by those skilled in the art will fall within the protection scope of this application. Summary of the Invention Purpose of the invention

[0007] The core objective of this invention is to overcome the shortcomings of existing technologies and provide a method and system for switching pre-embedded local coordinates by third parties, specifically achieving the following objectives: 1. Enable third parties to pre-embed local coordinate systems in public digital maps, allowing them to build their own local interactive spaces within public digital maps to meet diverse customization needs; 2. Construct a dual-state architecture with a global roaming state and a local interaction state. The local interaction state has the core features of dedicated resource pool allocation, data context isolation, and fault isolation, realizing logical decoupling and resource isolation between the global and local systems, ensuring the stability and smoothness of local interactions, and preventing local anomalies from affecting the global system. 3. Establish a standardized global-local coordinate bidirectional mapping method, and combine it with spatial reference services to complete real-time calibration, ensuring high accuracy of coordinate switching and meeting the requirements of high-precision interaction; 4. Construct a multi-dimensional permission control framework to achieve fine-grained permission management of third-party pre-embedded local coordinates, balancing security and ease of use; 5. The preferred approach is to combine a dual-timeline spatiotemporal synchronization engine to achieve local coordinate data synchronization across different timelines, resolving conflicts in local coordinate data across multiple versions and time dimensions, and ensuring spatiotemporal consistency of local interactions. 6. It is preferable to use a three-dimensional virtual globe as a spatial carrier to realize multi-layer carrying and flexible expansion of local coordinates, thereby improving the practicality of the solution. Technical Solution Overview

[0008] The technical solution of this invention is based on a dual-state architecture of global roaming state and local interaction state. Relying on the standard geospatial coordinate system (such as WGS84), R* tree spatial index, spatial reference service and independent permission management framework, it constructs a full-link local coordinate switching system of "third-party pre-embedded management + bidirectional trigger verification + nested coordinate mapping + spatiotemporal calibration + isolated interaction environment management".

[0009] The core protection point of this invention is "third-party pre-embedded nested local coordinates and switching logic + a local interactive environment with dedicated resources, data, and fault isolation features," that is: the third party submits the definition of the local coordinate system (including the coordinate origin, boundary, and mapping rules with the global coordinates), the platform completes the binding of the local coordinate system with the global coordinate system, when the user triggers the local coordinate area, a dedicated resource pool is dynamically allocated to the area, the data context is isolated, fault isolation is achieved, and the switching between local coordinates and global coordinates is realized according to the mapping rules; this invention preferably uses a three-dimensional virtual globe as a spatial carrier and dual timelines as a spatiotemporal synchronization mechanism, as detailed below: • In the preferred embodiment, the three-dimensional virtual globe has a multi-layer structure, which can dynamically overlay various digital map services. The nested local coordinates pre-embedded by the third party can be flexibly mounted to the corresponding layer of the three-dimensional virtual globe to achieve accurate carrying and expansion of local coordinates. • In a preferred embodiment, the dual-timeline spatiotemporal synchronization engine is used to manage the publishing timeline and the display timeline. The publishing timeline records the actual physical timestamp of the local coordinates, while the display timeline allows third parties to customize the logical time points of the local coordinates. The mapping and synchronization of the two timelines are achieved through the cross-timeline feedback controller, ensuring the spatiotemporal consistency of the local coordinate data. Specific technical methods (see Figure 1 )

[0010] A method for switching between third-party pre-embedded nested local coordinates, based on a dual-state architecture of global roaming state and local interaction state (see...). Figure 2 Based on a standard geospatial coordinate system (such as WGS84), R* tree spatial index, spatial benchmark service, and independent permission management framework, its features include the following steps: This step enables third-party developers to independently create, define, and standardize the registration of nested local coordinates, providing a foundation for the subsequent triggering and switching of local coordinates.

[0011] S101: Third-Party Developer Permission Authentication Third-party developers submit identity verification materials through the digital map open platform. The materials include: • Business / Individual qualification certificates (business license for businesses, identity certificate for individuals); • Scenario Usage Description (detailed explanation of the application scenarios, target users, and interaction requirements for the pre-embedded local coordinates); • Sandbox resource requirements (required computing power quota, storage quota, and bandwidth requirements, for subsequent allocation of dedicated resource pool).

[0012] The system completes authentication through a permission management framework, assigning corresponding local coordinate pre-embedded permissions based on the developer type and scenario attributes: • Developers in industrial and high-end commercial scenarios: can obtain high privileges, support multi-level coordinate nesting (up to 10 levels of nesting) and large-scale resource pools (computing power quota up to 10 times the basic quota); • Developers in general commercial and cultural tourism scenarios: can obtain intermediate permissions, supporting up to 5 levels of coordinate nesting and intermediate-sized resource pools; • Individual developers and developers in general social scenarios: can obtain basic permissions, and support single-level local coordinate pre-embedding and standard resource pool.

[0013] After successful authentication, the system generates a unique developer ID and opens pre-embedded and registration interfaces, allowing developers to create and register local coordinates.

[0014] S102: Nested Local Coordinate Attribute Definition Developers can define core properties of nested local coordinates through pre-embedded interfaces, supporting dynamic multi-level nesting expansion. Child coordinates are associated with parent coordinates through a "parent coordinate identifier (ParentZoneID)". Core properties include: 1. Basic attributes: Unique coordinate identifier (ZoneID), parent coordinate identifier (ParentZoneID, ParentZoneID is 0 in global roaming state), coordinate name, coordinate boundary (latitude and longitude + altitude for 3D coordinates, planar coordinates for 2D coordinates), coordinate level (incrementing from 1, level 0 in global roaming state); 2. Trigger Attributes: Trigger Type (GPS Trigger / Virtual Fixed-Point Trigger / Dual Trigger), Trigger Threshold (the shortest distance threshold between the user and the coordinate boundary when GPS triggers, such as 5 meters / 10 meters / 20 meters), Trigger Valid Time (the valid trigger time period for the coordinates can be set, such as triggering only during business hours); 3. Permission Attributes: Permission Type (Public / Member / Employee / Password / Operation Permission Level), Permission Verification Parameters (Member Level Threshold, Employee ID List, Access Password, Operation Permission Level Classification); 4. Dimensional Attributes: Two-dimensional coordinates / Three-dimensional coordinates. Two-dimensional coordinates are associated with the Cartesian plane coordinate system, and three-dimensional coordinates are associated with the East-West Cartesian coordinate system (ENU). The rendering precision level of the coordinates can be set. 5. Isolation attributes: resource pool specifications (dedicated computing power, storage, bandwidth quotas), data isolation scope (whether local interactive data is synchronized with the global state, whether data export is allowed), fault isolation rules (handling strategies when local anomalies occur, such as automatic isolation, degradation to the global state); 6. Spatiotemporal Attributes: You can choose whether to enable spatiotemporal synchronization of dual timelines. When enabled, it can realize multi-time dimension synchronization of local coordinates, such as local coordinate backtracking of historical timelines and local coordinate preview of future timelines.

[0015] S103: Standardized Registration and Hierarchical Index Construction After developers complete the attribute definitions, they submit local coordinate attribute information through the registration interface. The system then performs compliance checks on the attribute information, including the following: 1. Boundary validity: Verify whether the boundaries of the local coordinates are within the legal range and whether they conflict with the boundaries of the registered local coordinates; 2. Trigger threshold validity: Verify whether the trigger threshold is within a reasonable range (e.g., the GPS trigger threshold does not exceed 50 meters); 3. Completeness of permission parameters: Verify whether the permission parameters are complete, such as whether a valid password has been set for the password type coordinates; 4. Resource pool specification matching: Verify whether the resource pool specifications meet the developer's permission level; 5. Malicious Configuration Detection: Verify whether there are malicious configurations, such as setting excessively high resource quotas that lead to system resource exhaustion, or setting unreasonable trigger thresholds that affect system stability. If malicious configuration is detected, registration will be rejected.

[0016] After successful verification, the local coordinate information is entered into the global coordinate database. Simultaneously, based on the R* tree spatial index, a hierarchical index structure of "global coarse index - parent coordinate medium index - child coordinate fine index" is constructed, and the child coordinate index is mounted to the corresponding parent coordinate index node to achieve fast retrieval and positioning of local coordinates, with an index update frequency of ≤100ms. The system also pre-configures a dedicated resource pool for each registered local coordinate, allocating templates and data context isolation rules to prepare for the instantiation of subsequent local interaction environments.

[0017] Step S200: Two-way trigger request acquisition and preprocessing This step collects the user's two-way trigger requests (GPS location trigger, virtual fixed point trigger), completes request preprocessing and candidate coordinate retrieval, and provides input for subsequent verification.

[0018] S201: Triggering a request to collect data The system collects trigger requests through user terminals (mobile phones, AR / VR devices, industrial control terminals, PCs). The two methods for collecting trigger requests are as follows: 1. GPS Trigger Request: The terminal collects user GPS positioning data (latitude and longitude + altitude, 3D scene) or planar coordinates (2D scene) in real time in global roaming state / local interactive state. When the shortest distance between the user's location and the boundary of a certain local coordinate is less than or equal to the trigger threshold of that coordinate, and it is within the effective trigger time, a GPS trigger request is automatically generated, which includes user positioning data, terminal type, current state (global roaming state / local interactive state at a certain level), and user identifier; 2. Virtual Fixed-Point Trigger Request: When a user clicks a virtual icon (local coordinate entry) in the global roaming interface of the terminal / local interactive interface of the parent coordinate, a virtual fixed-point trigger request is submitted, which includes the target local coordinate ZoneID, the user's current coordinates (global coordinates / parent coordinate local coordinates), terminal type, and user identifier.

[0019] S202: Request Preprocessing and Candidate Coordinate Retrieval The system preprocesses the trigger requests for data collection: 1. GPS Trigger Request: The GPS positioning error is calibrated through base station-assisted positioning, BeiDou satellite positioning correction, etc., to ensure that the error is ≤1 meter; at the same time, the user's current status is verified to meet the coordinate triggering requirements, such as whether it is within the valid triggering time.

[0020] 2. Virtual fixed-point trigger request: Verify the validity of the target ZoneID (query the global coordinate database to confirm that the ZoneID exists and has not been deregistered, and that coordinate nesting restrictions allow triggering); verify whether the user's current coordinates are within the boundary range of the parent coordinates (if currently in a local interactive state).

[0021] After preprocessing, candidate local coordinates are retrieved based on the hierarchical R* tree index: • GPS Triggered Request: Retrieve all local coordinates within ≤ trigger threshold of the user's location, generate a candidate ZoneID list, and sort them from nearest to farthest. • Virtual pinpoint trigger request: Directly locates the local coordinates corresponding to the target ZoneID, without needing to search the candidate list.

[0022] Step S300: Multi-dimensional trigger validity verification This step performs triple verification on the trigger request in a fixed order to ensure the legality and compliance of the local coordinate trigger. Only after all verifications pass can the coordinate mapping and local interaction environment instantiation process proceed. If any verification fails, the trigger process is terminated and a failure message is returned (the message includes the reason for the failure, such as "trigger type mismatch" or "insufficient permissions").

[0023] S301: Trigger type matching check The system verifies whether the trigger request type matches the coordinate trigger type based on the local coordinate trigger attribute corresponding to the candidate ZoneID (GPS triggered) or the target ZoneID (virtual fixed-point triggered). • GPS-triggered: Only accepts GPS trigger requests and rejects virtual fixed-point trigger requests; • Virtual fixed-point triggering: Only accepts virtual fixed-point triggering requests, rejects GPS triggering requests; • Coordinates are dual-trigger: Both GPS location trigger and virtual fixed point trigger must be satisfied, or one of them must be satisfied (this can be determined based on the logical relationship set by the coordinates, such as "AND" relationship must be satisfied simultaneously, "OR" relationship only needs to be satisfied).

[0024] If the trigger type does not match, the message "Trigger type does not match, unable to trigger this local coordinate" will be returned.

[0025] S302: Permission Verification The system verifies user permissions based on the permission attributes of local coordinates: • Public type coordinates: No additional validation required, all users can trigger it; • Membership type coordinates: Verify whether the user's membership level has reached the membership level threshold set by the coordinates; • Employee type coordinates: Verify whether the user's employee ID is in the employee ID list set by the coordinates; • Password type coordinates: Verifies whether the password entered by the user matches the access password set at the coordinates; • Operation permission level type coordinates: Verify whether the user's operation permission level meets the permission level set by the coordinates.

[0026] If the permission verification fails, the message "Insufficient permissions, unable to trigger this local coordinate" will be returned.

[0027] S303: Spatiotemporal Consistency Check The system calls the spatial reference service to verify whether the spatiotemporal information of the user's current location is consistent with the spatiotemporal reference of the coordinates: • Verify whether the user's current time is within the valid trigger time of the coordinate; • Verify whether the spatiotemporal reference of the user's current location matches the spatiotemporal reference of the coordinates to avoid coordinate offset caused by inconsistency in spatiotemporal references; if the coordinates have enabled dual timeline spatiotemporal synchronization, then synchronously verify whether the user's current timeline is consistent with the coordinates' timeline.

[0028] If the spatiotemporal consistency check fails, the message "Spatiotemporal information is inconsistent, and the local coordinates cannot be triggered" will be returned.

[0029] Step S400: Nested coordinate mapping and spatiotemporal calibration (see...) Figure 3 ) This step completes the bidirectional mapping of global and local coordinates through a hierarchical recursive mapping method, and combines it with spatial reference services for real-time calibration to ensure high precision in coordinate switching and achieve seamless switching of nested local coordinates.

[0030] S401: Implementation of Hierarchical Recursive Mapping Method A hierarchical recursive mapping method is used to achieve bidirectional mapping between global and local coordinates. This method refers to the process of progressively transforming global coordinates to target local coordinates (forward mapping) or vice versa, based on the hierarchical relationship (ParentZoneID association) of nested local coordinates pre-embedded by a third party. Whether the nested local coordinates are aligned with the global coordinates and whether to continue nesting sub-coordinates are defined by the third party during pre-embedding. The system executes the recursive mapping according to the preset hierarchical relationship. The specific process is as follows: 1. Forward Mapping (Global → Local): Mapping from global coordinates to the target local coordinates step by step. The specific process is as follows: • If the target coordinates are first-level local coordinates: directly convert the coordinates in the global standard Earth coordinate system to the local coordinate system coordinates of that coordinate system; • If the target coordinates are nested coordinates at multiple levels: first convert the global coordinates to the local coordinates of the parent coordinates, then convert the local coordinates of the parent coordinates to the local coordinates of the child coordinates, and so on, until the target coordinates are reached.

[0031] 2. Reverse Mapping (Local → Global): Mapping back to global coordinates from the target's local coordinates step by step. The specific process is as follows: • If the current coordinates are first-level local coordinates: directly convert the local coordinates of the coordinates to coordinates in the global standard Earth coordinate system; • If the current coordinates are multi-level nested coordinates: first convert the local coordinates of the child coordinates to the local coordinates of the parent coordinates, then convert the local coordinates of the parent coordinates to the global coordinates, and so on, until the global coordinate system is reached.

[0032] S402: Spacetime Calibration The system invokes the spatial reference service to perform real-time calibration of the mapped coordinates: Spatial calibration: Obtain the geoid model and coordinate deviation correction parameters for the current location, and dynamically compensate the mapped coordinates to ensure that the coordinate consistency error is ≤0.2 meters; when network jitter causes coordinate drift, the Kalman filter algorithm is used to correct the coordinate drift.

[0033] 2. Time calibration: Synchronize the global spatiotemporal reference to ensure that the local coordinate time is consistent with the global time, and avoid interaction anomalies caused by time deviation; • If dual-timeline spatiotemporal synchronization is enabled, the global timeline and local timeline are synchronized through the dual-timeline spatiotemporal synchronization engine. When data updates from the two timelines conflict, a timestamp-first strategy is used to resolve the conflict. The pseudocode is as follows: After calibration, the calibrated coordinate information is sent to the local interactive environment instantiation module to provide a coordinate reference for the activation of the local interactive environment.

[0034] Step S500: Instantiation of the local interactive environment and preparation for interaction (see...) Figure 4 ) This step instantiates a local interactive environment with dedicated resources, data isolation, and fault isolation features based on the attributes of local coordinates, completes rendering adaptation and interaction preparation, and enables fast loading of local interactive scenes.

[0035] S501: Instantiation of Local Interactive Context and Allocation of Dedicated Resources The system dynamically instantiates independent interactive environments based on the attributes of local coordinates and allocates a dedicated resource pool to each environment. • Load the dedicated resources (model, texture, interactive controls) for this local coordinate and read the data from the dedicated storage resource pool; • Allocate isolated data contexts to ensure that the interactive data in this environment is not mixed with other local interactive environments or global data, thereby achieving data isolation; • Allocate dedicated computing resources to this environment to ensure smooth rendering and interaction, and avoid competing for computing resources with the global or other local environments; Configure fault isolation rules so that when an environment experiences an anomaly (such as program crash or resource overload), the environment is automatically isolated to prevent the anomaly from spreading to the global system or other local environments. Specifically, runtime context isolation technology is used to completely isolate the runtime space of the local interactive environment from the global system, so that anomalies in the local environment will not affect the normal operation of the global system.

[0036] S502: 2D / 3D Adaptive Rendering Automatically select the corresponding rendering logic based on the dimension attribute of the local coordinates: • 3D coordinates: Enable the 3D rendering pipeline, and enable 3D lighting, depth detection, anti-aliasing and other functions to achieve high-precision rendering and meet the needs of AR / VR interaction and industrial digital twin scenarios; in the preferred implementation, combine the 3D rendering logic of the stereoscopic virtual earth to achieve a unified rendering style between the local scene and the global virtual earth. • Two-dimensional coordinates: Enable the 2D rendering pipeline, disable redundant calculations related to 3D, optimize rendering efficiency, reduce terminal computing power consumption, and meet the needs of scenarios such as parameter panels and product information display; in the preferred implementation, adapt to the 2D layer rendering logic of the three-dimensional virtual globe to ensure natural interface integration.

[0037] At the same time, the rendering precision is adapted according to the terminal type. For example, the rendering precision is automatically reduced on low-computing-power terminals to ensure smooth interaction.

[0038] S503: Activation of Local Interactive Environment and Interaction Preparation After rendering and adaptation are complete, the system activates the local interactive environment and switches the user's interface to the local scene of that environment: • Synchronize and calibrate coordinate information to ensure accurate positioning of the user in the local scene; • Activate the interactive controls in this environment, such as virtual buttons, touch interaction areas, etc.; • Synchronize the interaction rules of the environment, such as the response logic of user operations and scene linkage rules; if the environment has enabled dual timeline spatiotemporal synchronization, then synchronize the multi-time dimension interaction rules of the environment.

[0039] Step S600: Exiting the local interactive environment and releasing resources This step enables the safe exit from the local interactive environment and the release of resources, ensuring the efficient use of system resources and avoiding resource idleness.

[0040] S601: Exit Signal Capture The system captures exit signals from the local interactive environment. These exit signals include: 1. Passive exit: • The trigger threshold for the user leaving the local coordinates (GPS location exceeds the coordinate boundary or virtual fixed point operation exits); • When the user performs a back action (such as clicking the back button or using a gesture to return), the system switches back to the global roaming state or the local interactive state of the parent coordinates; • User permissions expired, and the user was forcibly exited from this local coordinate system; • The effective triggering time for this local coordinate has ended; • An anomaly occurred in this local environment, triggering the fault isolation rule, and the system automatically exited.

[0041] 2. Voluntary Exit: • The developer manually disabled this local coordinate system; • If the terminal's computing power is insufficient, it will automatically degrade and exit (e.g., the terminal's computing power cannot support the rendering requirements of this environment). • Users can manually stop the dual timeline synchronization and no longer need to use the local environment.

[0042] S602: Resource Release and Environmental Destruction The system executes corresponding resource release and environment destruction operations based on the exit signal type, following the principle of "exit equals destruction": 1. Save the interaction data of this local interactive environment (if the coordinate attribute is set to allow data synchronization); if the environment has enabled dual timeline spatiotemporal synchronization, save all timeline coordinate data of this environment in the dual timelines (according to the retention policy) and synchronize them to the global database for easy subsequent querying and recovery; 2. Release the dedicated resource pool (computing power resources, storage resources, bandwidth resources) occupied by this environment, and reclaim the resources to the corresponding resource pool for use by other local coordinates; 3. Delete the instance of this local interaction environment, clear the isolated data context, and ensure that no data remains; 4. Update the coordinate status in the global coordinate database and mark the coordinate as "inactive".

[0043] For multi-level nested coordinates, when exiting a child coordinate, only the child coordinate's dedicated resource pool is released and the child coordinate's interaction environment is destroyed, while the parent coordinate's interaction environment remains active; when exiting a parent coordinate, all child coordinates' interaction environments are automatically destroyed, and the parent coordinate's dedicated resource pool is released. Attached Figure Description

[0044] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the accompanying drawings used below will be briefly introduced. Obviously, the accompanying drawings described below are only schematic diagrams of the core implementation of the present invention. For those skilled in the art, without creative effort, they can understand the overall technical logic, architecture design and core process of the present invention based on these drawings, and can also derive other detailed implementation drawings based on them. The drawings are only used to illustrate the technical solutions of the present invention and do not constitute a limitation on the present invention.

[0045] Figure 1This is a flowchart of the overall process of the method for switching third-party pre-embedded nested local coordinates in this invention. The flowchart sequentially shows the six main steps of the core method of this invention, namely, the pre-embedding and registration of third-party nested local coordinates, the collection and preprocessing of bidirectional trigger requests, the multi-dimensional trigger validity verification, the nested coordinate mapping and spatiotemporal calibration, the instantiation and interaction preparation of the local interaction environment, and the exit and resource release of the local interaction environment, as well as the verification and judgment branch logic, clearly presenting the execution path of the entire coordinate switching process.

[0046] Figure 2 This diagram illustrates the dual-state architecture of the present invention, which consists of a global roaming state and a local interaction state. The diagram shows the core of the dual-state architecture, which is divided into two core states: a global roaming state and a local interaction state. These two states correspond to global coordinate roaming navigation and nested local coordinate interaction functions, respectively. The two states are linked by a dual-state switching trigger module. After the switch, the state synchronization is completed by the state calibration module, which intuitively reflects the logical decoupling and interaction characteristics of the dual-state architecture.

[0047] Figure 3 This diagram illustrates the logic of the hierarchical recursive mapping method used in this invention to achieve bidirectional global-local coordinate mapping. The diagram uses a hierarchical structure to show the bidirectional mapping logic between the global and local coordinate systems after coordinate mapping is triggered: the left side represents forward mapping (global → local), which, based on the target coordinate level, is divided into two paths: direct transformation of first-level local coordinates and hierarchical recursive transformation of multi-level nested coordinates; the right side represents reverse mapping (local → global), which, based on the current coordinate level, is divided into two paths: direct transformation of first-level local coordinates and hierarchical recursive transformation of multi-level nested coordinates; all mapping path results are summarized in the mapping result output, and after real-time calibration by the spatial reference service, high-precision coordinate results are output, fully presenting the core process of the hierarchical recursive mapping method.

[0048] Figure 4 This diagram illustrates the resource allocation, data context isolation, and fault isolation architecture of the local interactive environment of this invention. It shows the three-layer isolation architecture after the local interactive environment is instantiated: the left side represents dedicated resource allocation, allocating dedicated computing power / storage / bandwidth pools to the local environment to achieve independent resource scheduling; the middle side represents data context isolation, constructing independent data storage / interaction domains to isolate local data from global and other environmental data; and the right side represents fault isolation configuration, configuring automatic anomaly isolation + global non-impact rules to prevent local anomalies from spreading to the global system. This fully presents the core design of the three-layer isolation of resources, data, and faults in the local interactive environment.

[0049] Figure 5This diagram illustrates the module composition of the coordinate switching system supporting third-party pre-embedded nested local coordinates, as per the present invention. The diagram showcases the core modules of the coordinate switching system, comprising four main functional modules: a third-party coordinate parsing module responsible for parsing pre-embedded coordinate parameters to achieve standardized access to third-party local coordinates; a nested local coordinate mapping module responsible for global-local bidirectional mapping to achieve hierarchical recursive transformation of coordinates; a coordinate switching control module responsible for triggering / executing coordinate switching and managing the entire switching logic; and a coordinate reference calibration module responsible for calibrating switching accuracy to ensure high-precision coordinate switching requirements. The diagram visually presents the hierarchical relationship between system modules and the division of core functions. Detailed Implementation

[0050] Example 1: AR Interactive Scene in Smart Cultural Tourism Scenic Area

[0051] System initial state:

[0052] The wetland park's global digital map is built based on the WGS84 coordinate system and is in a global roaming state. The scenic area operator, as a third-party developer, has completed the pre-embedding of first-level and second-level nested local coordinates. All coordinates are assigned a unique ZoneID and hierarchical association identifier. Trigger thresholds, coordinate transformation rules, and exclusive resource pool specifications have been preset according to the cultural tourism scenario. The local coordinate triggering module, coordinate mapping calibration module, and dual-timeline spatiotemporal synchronization engine are in a ready state. The interfaces with the computing power scheduling and data mounting system have been linked. The terminal positioning module (GPS + Beidou + inertial navigation) has been initialized, and the positioning accuracy is ≤1 meter.

[0053] Core steps:

[0054] 1. Pre-installed configuration: The scenic area operator, as a third-party developer, pre-installs primary local coordinates (JYQ001 in the core AR interactive area of ​​the park, trigger threshold 10 meters) and secondary local coordinates (DKD001 on the ancient city wall, DKD002 on the lake pavilion, and DKD003 on the Zhuangyuan Tower check-in point, trigger threshold 5 meters). The trigger type is set to GPS trigger, the permission type is public, the dedicated resource pool specifications are 500 GFLOPS computing power and 10GB storage, and the fault isolation rule is "automatic isolation when there is a local anomaly, without affecting the global system". In the preferred implementation, the local coordinates are mounted to the cultural tourism-specific layer of the three-dimensional virtual globe, and the dual timeline synchronization parameters are configured as "regular timeline + historical timeline", the synchronization frequency is 100ms, and the data retention period is 30 days.

[0055] 2. Precise Triggering: When a user enters within 10 meters of the park with their terminal, a first-level local coordinate system is triggered. After GPS positioning calibration, the system instantiates a local interactive environment for this coordinate system, allocates a dedicated resource pool (500 GFLOPS computing power, 10GB storage), and switches the user's coordinates to the first-level local coordinate system. When the user enters within 5 meters of the ancient city wall, a second-level local coordinate system is triggered. The system switches the user's coordinates to the second-level local coordinate system using a hierarchical recursive mapping method, with a trigger response latency of ≤10ms.

[0056] 3. Mapping calibration: A triple calibration algorithm (spatial reference calibration, feature point matching calibration, and multi-terminal collaborative calibration) is used to calibrate the coordinates. After calibration, the spatiotemporal consistency error is ≤0.1 meters. When the network jitter occurs, the Kalman filter algorithm is used to correct the coordinate drift and ensure coordinate accuracy.

[0057] 4. Spatiotemporal Synchronization: If a user triggers the dual timeline function, they can switch to the historical timeline to view the historical appearance of the ancient city wall. The dual timeline synchronization engine will synchronize the historical coordinate data with the current coordinate data. AR interaction data (such as check-in records and interactive operations) within the user's local interactive environment will be stored in a dedicated data context, which will not be mixed with the global data, thus achieving data isolation. If an anomaly occurs in the local environment (such as AR rendering crash), the fault isolation rules will automatically isolate the environment, without affecting the normal operation of the global map.

[0058] 5. State Switchback: When the user leaves the range of the secondary local coordinates by 5 meters, the system automatically destroys the secondary local interactive environment, releases the dedicated resource pool, and switches the user's coordinates back to the primary local coordinates; when the user leaves the range of the primary local coordinates by 10 meters, the system automatically destroys the primary local interactive environment, releases the dedicated resource pool, and switches the user's coordinates back to the global roaming state.

[0059] Beneficial effects

[0060] With a dedicated resource pool and fault isolation, local interaction anomalies will not affect the global system, improving system stability by 80%. In the preferred implementation, multi-layer rendering of the 3D virtual globe is combined to achieve seamless integration of local scenes and the global virtual globe, enhancing the user experience. The dual timeline function allows users to view historical features, increasing the fun of cultural and tourism interaction.

[0061] Example 2: Industrial Digital Twin Remote Equipment Control Scenario System initial state: The factory's global digital twin map is built based on the industrial UTM coordinate system and is in a global roaming state. The equipment supplier, as a third-party developer, has completed the pre-embedding of three levels of nested local coordinates (Level 1: General Assembly Workshop GY_CJ001, Level 2: Chassis Assembly Production Line GY_SCX001, Level 3: Robotic Arm Assembly Station GY_SB001, Tightening Machine Operation Station GY_SB002). Industrial-grade ZoneIDs and hierarchical association identifiers have been bound, and trigger rules, access control, and dedicated resource pool specifications have been configured. The industrial-grade positioning receiver (UWB + inertial navigation, positioning accuracy ≤0.03 meters) is ready, and the coordinate mapping calibration module and dual-timeline spatiotemporal synchronization engine have been enabled in industrial-grade working mode, and the interfaces with the factory's MES system and equipment control system have been linked.

[0062] Core steps: 1. Pre-installed configuration: The equipment supplier, as a third-party developer, pre-installs three levels of nested local coordinates, sets the trigger type to virtual fixed-point trigger, the permission type to hierarchical operation permission (only users with operation permissions of level 3 or above are allowed to operate the equipment), the dedicated resource pool specifications are 1000 GFLOPS computing power and 50GB storage, and the fault isolation rule is "immediately isolate and trigger alarms when there is a local anomaly, and prevent the anomaly from spreading to the global system"; In the preferred embodiment, the local coordinates are mounted to the industrial-specific layer of the three-dimensional virtual globe, the dual timeline synchronization parameters are configured as "regular timeline + temporary timeline", the synchronization frequency is 50ms, and the data retention period is 1 year.

[0063] 2. Precise Trigger: Maintenance personnel click the virtual icon of the robotic arm assembly station through the industrial control terminal to trigger the level 3 local coordinate. After the system verifies the permissions, it instantiates a local interactive environment for the coordinate, allocates a dedicated resource pool (1000 GFLOPS computing power, 50GB storage), and switches the user's coordinate to the level 3 local coordinate. The trigger response latency is ≤8ms.

[0064] 3. Mapping Calibration: The coordinates are calibrated using a quadruple calibration algorithm (device-side registration calibration, digital twin model calibration, industrial scene feature point calibration, and multi-sensor fusion calibration). The calibration error is ≤0.005 meters (5 micrometers), and the coordinates are encrypted using AES-256. In the preferred embodiment, a secondary calibration is performed in conjunction with the deviation parameters of the industrial layer of the three-dimensional virtual globe. The calibration error is ≤0.003 meters.

[0065] 4. Spatiotemporal Synchronization: The dual-timeline spatiotemporal synchronization engine synchronizes local coordinate data with the high-precision clock (error ≤ 1ms) of the factory MES system, with a synchronization error ≤ 2ms; the operation and maintenance personnel's control commands are sent to the physical end of the equipment through the dedicated data channel of the local interactive environment, with a command response delay ≤ 3ms; at the same time, the fault isolation rules ensure that the interaction abnormalities of the robotic arm station (such as incorrect control commands or model rendering crashes) will not affect the final assembly workshop or the global system. If an abnormality occurs, the system immediately isolates the local environment and triggers an alarm.

[0066] 5. Status Switchback: After the operation and maintenance is completed, the operation and maintenance personnel click the back button. The system destroys the level 3 local interactive environment, releases the dedicated resource pool, switches the user coordinates back to level 2 local coordinates, then switches back to level 1 local coordinates, and finally switches back to the global roaming state. The switchback response latency is ≤15ms. After the switchback, the coordinate data is decrypted and verified and permanently archived to the factory industrial database.

[0067] Beneficial effects

[0068] The total latency for three-level coordinate switching is ≤20ms, and the spatiotemporal consistency error is ≤0.05 meters, meeting the micron-level precision requirements of industrial remote operation and maintenance. Through a dedicated resource pool and fault isolation, abnormal equipment operation will not affect the global system, improving operation and maintenance security by 90%. In the preferred implementation, the industrial layer rendering of the three-dimensional virtual globe is combined to achieve seamless integration of the digital twin scene and the global virtual globe, improving operation and maintenance efficiency. The dual timeline function allows operation and maintenance personnel to view the historical operating data of the equipment, facilitating fault diagnosis.

[0069] Example 3: Virtual Store Scenario in the Commercial Metaverse System initial state: The commercial complex metaverse platform is in a global roaming state; the brand, as a third-party developer, has completed permission authentication, the global coordinate database has stored commercial nested coordinate information, the hierarchical R* tree index is running normally, the spatial benchmark service is in real-time calibration, and the dual trigger logic has been preloaded; the local coordinate trigger module, coordinate mapping calibration module, and dual timeline spatiotemporal synchronization engine are in a ready state, and the interfaces with the computing power scheduling and data mounting system have been linked.

[0070] Core steps: 1. Pre-installed configuration: The brand, as a third-party developer, pre-installs primary local coordinates (commercial complex sandbox SY001, trigger threshold 15 meters) and secondary local coordinates (brand virtual store sandbox MD001, trigger threshold 5 meters). The trigger type is set to dual trigger (GPS trigger + virtual fixed-point trigger), the permission type is set to membership level threshold (only silver card members and above are allowed to trigger), the dedicated resource pool specifications are 800 GFLOPS computing power and 20GB storage, and the fault isolation rule is "automatically downgrade to global state when local anomalies occur to avoid affecting user experience"; in the preferred implementation, the local coordinates are mounted to the commercial-specific layer of the three-dimensional virtual globe, the dual timeline synchronization parameters are configured as "regular timeline + future timeline", the synchronization frequency is 100ms, and the data retention period is 90 days.

[0071] 2. Precise Triggering: When a user enters within 15 meters of a commercial complex with their terminal, a first-level local coordinate system is triggered. The system instantiates a local interactive environment, allocates a dedicated resource pool (800 GFLOPS computing power, 20GB storage), and switches the user's coordinates to the first-level local coordinate system. When a user clicks on the virtual icon of a brand's virtual store, a second-level local coordinate system is triggered. After the system verifies the user's permissions, it switches the user's coordinates to the second-level local coordinate system. The trigger response latency is ≤15ms.

[0072] 3. Mapping calibration: The global coordinates are converted into second-level local coordinates using a hierarchical recursive mapping method, and calibration is performed in conjunction with the spatial reference service. After calibration, the coordinate consistency error is ≤0.2 meters. In the preferred embodiment, a secondary calibration is performed in conjunction with the deviation parameters of the commercial layer of the three-dimensional virtual globe. After calibration, the error is ≤0.1 meters.

[0073] 4. Spatiotemporal Synchronization: If a user triggers the dual timeline function, they can switch to the future timeline to view the brand's new product launch scenario. The dual timeline synchronization engine will synchronize future coordinate data with current coordinate data, with a synchronization error of ≤5ms. User interaction data in the virtual store (such as virtual try-on records and product collection records) is stored in a dedicated data context to achieve data isolation and prevent confusion with store data from other brands. If an anomaly occurs in a local environment (such as product model loading failure), the fault isolation rules will automatically downgrade to the global state to ensure that users can continue to use the global map function.

[0074] 5. State Switchback: When the user leaves the range of the secondary local coordinates within 5 meters, the system destroys the secondary local interaction environment, releases the dedicated resource pool, and switches the user's coordinates back to the primary local coordinates; when the user leaves the range of the primary local coordinates within 15 meters, the system destroys the primary local interaction environment, releases the dedicated resource pool, and switches the user's coordinates back to the global roaming state. The switchback response latency is ≤25ms.

[0075] Beneficial effects Dual-trigger response latency ≤40ms, secondary coordinate resource loading time ≤150ms, a 30% reduction in loading time compared to independent resource pools, adapting to the diverse terminal needs of commercial scenarios; through dedicated resource pools and fault isolation, abnormal interactions of virtual stores will not affect the global platform, improving platform stability by 70%; in the preferred implementation, combining the commercial layer rendering of a 3D virtual globe achieves seamless integration of virtual stores and the global virtual globe, enhancing user experience; the dual timeline function allows users to view future new product launch scenarios, improving commercial marketing effectiveness.

[0076] It should be noted that the '3D virtual globe' and 'dual timelines' mentioned in the above embodiments are merely preferred application scenarios of the present invention. The core methods of the present invention (such as coordinate mapping, data parsing, and computing power scheduling logic) are also applicable to two-dimensional maps, single timeline systems, or other dimensions of digital space. Any substitutions or adjustments made to the above application scenarios by those skilled in the art without departing from the concept of the present invention fall within the protection scope of the present invention. The specific values ​​in the embodiments are merely test data for this embodiment under a specific hardware environment; the protection scope of the present invention is not limited to these specific values, and any preset threshold that meets the real-time interaction requirements falls within the protection scope.

Claims

1. A method for switching pre-embedded local coordinates supported by third parties, characterized in that, include: The third party submits the definition of a nested local coordinate system, which includes the origin, boundary, and mapping rules of the local coordinate system with the global coordinate system, as well as the specifications of the dedicated resource pool, the data isolation range, and the fault isolation rules. The platform completes the binding of this local coordinate system with the global coordinate system, and pre-sets a dedicated resource pool and data context isolation rules for this local coordinate system; When a user triggers the local coordinate region, a local interactive environment with dedicated resource allocation, data context isolation, and fault isolation features is dynamically instantiated for that region, and the local coordinates are switched to global coordinates according to the mapping rules.

2. The method according to claim 1, characterized in that, The local coordinate system definition submitted by the third party also includes trigger attributes, which include trigger types, namely GPS trigger, virtual fixed-point trigger, or dual trigger.

3. The method according to claim 1, characterized in that, The local coordinate system definition submitted by the third party also includes permission attributes, which include permission types, such as public access, authorized access, password access, or hierarchical operation permissions.

4. The method according to claim 1, characterized in that, After the platform completes the binding of the local coordinate system and the global coordinate system, it establishes a hierarchical R* tree index for the local coordinate system to achieve fast retrieval and positioning of local coordinate regions.

5. The method according to claim 1, characterized in that, When a user triggers the local coordinate region, the system also performs trigger type matching verification, permission verification, and spatiotemporal consistency verification on the user. After the verification is passed, the system switches between local coordinates and global coordinates.

6. The method according to claim 1, characterized in that, When switching between local and global coordinates, a hierarchical recursive mapping method is used to complete the bidirectional mapping between global and local coordinates. In conjunction with spatial reference services, real-time calibration is performed to ensure the consistency of coordinate switching and adapt to the needs of local interaction scenarios.

7. The method according to claim 6, characterized in that, During the calibration process, when network jitter causes coordinate drift, a Kalman filter algorithm is used to correct the coordinate drift.

8. The method according to claim 1, characterized in that, It also includes the use of a dual-timeline spatiotemporal synchronization engine to achieve synchronization of local coordinate data across different timelines. The dual-timeline spatiotemporal synchronization engine includes a publishing timeline and a display timeline. The publishing timeline records the actual physical timestamp of the local coordinates, while the display timeline allows third parties to customize the logical time points of the local coordinates.

9. The method according to claim 8, characterized in that, The dual-timeline spatiotemporal synchronization engine achieves mapping and synchronization between the publishing timeline and the display timeline through a cross-timeline feedback controller. When data updates conflict between the two timelines, a timestamp-first strategy is adopted to resolve the conflict.

10. The method according to claim 1, characterized in that, It also includes using a three-dimensional virtual globe as a spatial carrier. The three-dimensional virtual globe has a multi-layer structure, and the nested local coordinates pre-embedded by a third party can be flexibly mounted to the corresponding layer of the three-dimensional virtual globe to achieve accurate carrying and expansion of local coordinates.

11. A switching system supporting third-party pre-embedded nested local coordinates, used to implement the method described in any one of claims 1-10, characterized in that, include: A third-party pre-embedded module is used to receive local coordinate system definitions submitted by third parties, complete the registration of local coordinate systems, and pre-set exclusive resource pools and data context isolation rules for the local coordinate system. The coordinate binding module is used to bind the local coordinate system pre-embedded by the third party to the global coordinate system and establish a hierarchical R* tree index; The trigger verification module is used to collect user trigger requests and verify the validity of the trigger requests; The coordinate mapping calibration module is used to complete the bidirectional mapping of global and local coordinates using a hierarchical recursive mapping method, and to perform real-time calibration in conjunction with the spatial reference service; The local interaction environment management module is used to dynamically instantiate local interaction environments with dedicated resource allocation, data context isolation, and fault isolation features for triggered local coordinate regions, thereby achieving resource allocation, data isolation, and fault isolation. The spatiotemporal synchronization module is used to synchronize local coordinate data across different timelines.

12. The system according to claim 11, characterized in that, The local interactive environment management module also includes: The resource allocation unit is used to allocate dedicated computing power, storage, and bandwidth resource pools to local interactive environments. Data isolation units are used to establish isolated data contexts for local interactive environments; The fault isolation unit is used to automatically isolate the local interactive environment when an anomaly occurs, preventing the anomaly from spreading to the global system or other local environments.

13. The system according to claim 11, characterized in that, It also includes a virtual globe layer management module, which is used to mount and manage local coordinates on the three-dimensional virtual globe layer.

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

15. A terminal device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the program, it implements the method according to any one of claims 1-10, and the terminal device includes a mobile phone, an AR / VR device, an industrial control terminal, and a PC.

Images