Documentation
¶
Overview ¶
Package main implements dual purpose directory service which manages UE location records and provides RPCs to look them up: DirectoryLookupServer & GatewayDirectoryService
GatewayDirectoryService RPC can be provided by a local Gateway/Device service as well as the cloud hosted service. UE locations are reported directly from the relevant device/gateway. Depending on a gateway/device capacity & resources, UE locations can be reported using GatewayDirectoryService RPC:
- to a locally run directoryd service, backed up by a local DB and synchronized with the cloud by state service
- to a cloud based directoryd service
Gateways/devices with an excess capacity to host and run local GatewayDirectoryService service & database (currently python based & requiring 40-70MB extra RAM & storage) should prefer reporting path #1 due to its higher persistency, and recovery capabilities. Embedded or underpowered gateways/devices on another hand, have to use reporting path #2, it's far more efficient in terms of required HW resources (less then a few hundred KB of extra RAM & storage), but its availability and correctness provided on a best-effort basis. Such a compromise should be a reasonable tradeoff for enabling location based features on underpowered devices. Note that that paths #1 & #2 can coexist within a single deployment/network, cloud's state service is a common destination for UE locations in both cases.
Source Files