1. Configuration Guide
  2. External Policy Servers
  3. Network Provided Location Information
  4. NPLI Implementation
  5. NPLI Support for 5G NR

NPLI Support for 5G NR

The Oracle Communications Session Border Controller (SBC) provides 5G NR Location support, which enables interoperability with 5G core elements in 5G systems. This allows the SBC to operate as an Application Function and in its role as a P-CSCF in the 5G core. Many carriers deploy a separate 5GS with the N26 interface in parallel with their older architectures. This newer architecture continues to use the Rx diameter interface to interwork with the PCF/PCRF and route diameter messages via the DRA. As an A-SBC, the SBC supports this architecture, further enabling operation within 5G. The SBC achieves this support through the ext-policy-server, specific-action-subscription, access-network-info-report configuration, which enables it to support additional 5G objects and behaviors, including objects that provide location information. No additional configuration is required to support NR location support for 5G. The SBC can also include the resulting 5G location fields within all CDR types.

The SBC supports 5G NPLI within the following call flows:

  • 5G-NR Registration
  • Registered MO and MT Calls
  • SMS from Registered User
  • Registered Emergency Calls
  • Emergency Call from Registered S8HR roaming user

5G elements supported by the SBC to construct the 5G NPLI include:

  • 5G access-type/access-class in the SIP PANI Header on the Gm and Mw interfaces
  • 5G-NR specific values in 3GPP-User-Location-Info on the Rx interface, per 3GPP TS 29.212 v16.4.0 and 3GPP TS 29.061 v16.2.0, including:
    • 3GPP-User-Location-Info AVP with the following Geographical Location Types, decoded per 3GPP TS 23.003 v16.5.0 and 3GPP TS 38.413 v16.4.0:
      • 135—NCGI
      • 136—5GS TAI
      • 137—5GS TAI and NCGI
    • RAT-Type AVP value 3GPP-NR (1006)
    • IP-CAN type AVP value 3GPP-5GS (8)