Mega localization service
Mega Block cloud localization service provides online, real-time spatial localization capabilities for client devices. The client device runs your AR application. After session initialization is completed, the initial camera pose needs to be obtained through the cloud localization service. Subsequently, combined with the local device's motion tracking capabilities and coordinated with cloud localization results, the device's real-time pose information is continuously updated to meet application requirements for higher robustness and more realistic AR experiences.
The cloud localization capability relies on real-time computation on the server side. During AR application runtime, the device must maintain network connectivity to obtain cloud-based localization and pose calculation results via the network. By default, the cloud localization computing center is deployed in Shanghai, China. If you have higher requirements for network latency or stability, or if your AR product targets overseas markets, we support deploying server nodes through dedicated line acceleration or deploying cloud localization resources in nearby computing centers to further optimize overall performance and user experience.
Block data flow
Block cloud localization preparation involves three steps:
- Capture, upload, and complete Block mapping
- Generate Block storage repository
- Add required Blocks to the cloud localization database
flowchart LR
A[Block mapping] --> B>Block storage] --> C[Add to cloud localization database]
After mapping is completed, generated Blocks are automatically stored in the bound Block storage repository. For detailed steps of each process, please refer to the following documents:
Cloud localization data flow
- The device uploads device motion tracking data and image data to the cloud localization service, which returns the localized camera pose results.
- The device-side performs real-time fusion and optimization of the camera pose to drive real-time rendering and interaction.
- If annotation data is uploaded to the cloud localization database, annotation packages will be downloaded to the device as EMA annotation files to render 3D content at annotated positions in real-time.
flowchart TB
C[Cloud localization database] --> D[Device-side]
D[Device-side] --> C[Cloud localization database]
Pre-requisites
- Mega Block mapping completed
- At least one available Mega Block storage repository
- Ensure target Mega Block is in this repository with normal status
- Prepare an APIKey with Mega Block permissions
- Device-side requires Sense license or WeChat Mini Program license (free trial available)
Note
To use EasyAR Sense license in head-mounted displays, select XR License Sense type
Quick start with cloud localization
Cloud localization service configuration steps:
- Purchase and create cloud localization service group
- Associate service group with mapping project
- Create cloud localization database within the group
- Add Mega Blocks to the cloud localization database
Reference topics:
Creating and purchasing cloud localization service group
This is a resource package required for cloud localization. Default packages include:
| Standard package item | Standard | Trial |
|---|---|---|
| Mapping project | 1 | 1 |
| Cloud localization databases | 5 | 2 |
| Concurrent request QPS | 10 | 3 |
Note
- Any request carrying a cloud localization database AppId counts toward concurrent QPS (regardless of localization success).
- Cloud localization databases within the same cloud service group share QPS.
Supplementary standard package items
Standard packages support additional purchases beyond usage limits:
- Purchase additional cloud localization databases
- Increase task association quota
- Scale up concurrent request QPS capacity
Note
Paid users' Mega Block map files are retained for 3 months after expiration; if files remain in the storage repository, you can recreate the cloud localization database and add maps for use.
Reference topics:
Quickly verify localization service
Mega supports quick verification after completing cloud localization service configuration to ensure normal service operation and localization effectiveness.
The following diagram shows a quick verification example: Using a prepared scene test photo in front of a computer, localizing against the photo off-site can quickly verify service connectivity. As shown, the green "Localize" indicator represents successful localization.
Quick verification Mega Toolbox verifies cloud localization service configuration. Supports native apps, WeChat Mini Programs, or simulation verification in Unity, specifically through:
- Off-site quick verification using Mega Toolbox
- On-site quick verification using Mega Toolbox
- Simulation-based quick verification using Mega Studio
Verify localization effectiveness
- First annotate Mega Block data in Mega Studio
- Verify localization effectiveness on-site using Mega Toolbox
Quick verification reference topic: