How it Works
This section describes how this feature works.
The AF initiates a request toward the PCF to provide the network information.
For AF supporting Rx interface, the request is sent over Rx through the Required-Access-Info AVP. When the Access Network Information is available the SMF provides the required Access Network Information to the PCF within the 3GPP-User-Location-Info AVP or 3GPP-MS-TimeZone AVP or both as requested.
For AF supporting N5 interface, the request is sent over N5 interface by subscribing to AF event ANI_REPORT and specifying the required access network information (user location or user time zone information).
Upon receiving the request, PCF triggers an N7 Update Notify request with ‘Access Network Info’ event trigger (if not already subscribed for) towards SMF. The SMF responds to PCF with the required information, which PCF further forwards to the AF.
When the SMF responds with ServingNetwork attribute instead of UserLocationInfo, then to set the Mobile Country Codes (MCC) and Mobile Network Code (MNC) ensure that the NetLoc features is enabled. For information on how to enable the NetLoc, see Enabling the NetLoc Feature .
For Rx interface, PCF provides the following information during an ACCESS_NETWORK_INFO_REPORT event trigger within the Event-Trigger AVP:
-
3GPP-User-Location-Info AVP (If available)
-
User-Location-Info-Time AVP (If available)
-
3GPP-SGSN-MCC-MNC AVP (If the location information is not available) or 3GPP-MS-TimeZone AVP or both.
For N5 interface, PCF provides the following information which includes notification for AF event ANI_REPORT:
-
3GPP User Location Information (If available and required)
-
Serving Network Identity (If user location is required and not available)
-
UE Timezone (If available and required)