Location Considerations for Satellite Deployments
Satellite-connected edge nodes can use different registration and deployment information.
In these deployments, the deployment location identifies where the hardware is installed. The registration address identifies the service or business location used for connectivity registration.
For example, an edge node can be deployed offshore while its registration address identifies an onshore office or support location. In this case, the deployment location is used for mapping and deployment tracking, while the registration address is used for service registration.
Depending on the connectivity plan, Oracle ECP can require both address and coordinates during onboarding and update workflows. Country-specific rules can also apply.
If Starlink-specific rules apply, Oracle ECP shows a warning banner in the location workflow.
Examples of Hardware with Different Addresses
Different hardware types can use location information in different ways. These examples show how deployment location, registration address, and GPS location can vary depending on the hardware and connectivity scenario.
Table 8-2 Examples of Location Data Across Hardware Types
| Hardware scenario | Deployment location | Registration address | GPS location |
|---|---|---|---|
| Standard device or edge node at a fixed site | Physical installation site used for mapping | Usually the same as the deployment location | Not shown |
| Satellite-connected edge node at a remote or offshore site | Physical installation site, such as a remote or offshore location | Business or service address used for connectivity registration | Not shown |
| MDM-enabled device | Physical deployment site used for deployment mapping | Business or service address when required | Current device position shown as a blue dot on the Location tab |