...
- MNO provides a Location Service (LS) compliant with OMA Zonal Presence API (OMA-TS-REST_NetAPI_ZonalPresence)
- MNO may expose the Location Service via the Network Exposure Function (NEF)
- A Public Cloud Edge (PCE) instance is associated with a Zone (collection of Access Points such as small cells) provided by an MNO
- A 3rd-Party Edge (3PE) instance is associated with a Zone (collection of Access Points such as small cells) provided by an MNO
- An application/workload in the PCE requires Location Information (e.g. coordinates of the Access Point) for the UE/subscriber
- An application/workload in the 3PE requires Location Information (e.g. coordinates of the Access Point) for the UE/subscriber
- PCEI Enabler facilitates Zonal Presence API Request/Response routing between PCE and the MNO LS and between the 3PE and the MNO LS
Azure IoT Edge
Assumptions:
- MNO hosts UPF/SPGW-U in their network.
- MNO provisions all UPF functions.
- MNO may request Deployment of IoT Edge on Bare Metal or NFVi via APIs (on P2)
- PCEI Enabler IoT Edge Deployer may request HW or Virtual resources (e.g. VM/Container) (on P3)
- PCEI Enabler IoT Edge Deployer may provision IoT Edge (install runtime, deploy standard modules, register with IoT Hub) via APIs/Deployer Code (on P8/P5)
- PCEI Enabler may request Interconnect for IoT Edge between MNO and Azure (L2/L3) via APIs (on P4)
- PCEI Enabler may request UPF LBO for MNO to direct customer traffic to IoT Edge (on P2/P2’)
- PCEI Enabler may facilitate deployment of custom IoT Edge modules
