Handling User-Endpoint-Provided Location Information

Handling of user-endpoint-provided location information is user configurable. By default, this information is not included in the PANI header constructed by the P-CSCF. This default state can be over-ridden, in which case the PANI header will contain both user-endpoint-provided location information and NPLI.

In the case where a user-endpoint PANI header contains an np parameter, the location information contained in the header is ignored, and is not included in the PANI constructed by the P-CSCF.

The following sample PANI headers illustrate the inclusion of both user-endpoint-provided and network-provided location information.

In this case, the UE -provided location information and NPLI matched.

P-Access-Network-Info: 3GPP-E-UTRAN-FDD; utran-cell-id-3gpp=26207FFFDF1B9601, 
3GPP-E-UTRAN-FDD; utran-cell-id-3gpp=26207FFFDF1B9601; network-provided

In this case, the cell-IDs did not match.

P-Access-Network-Info: 3GPP-E-UTRAN-FDD; utran-cell-id-3gpp=26207FFFDF1B9601, 
3GPP-E-UTRAN-FDD; utran-cell-id-3gpp=26207abcde7A7777; network-provided 

In this case, neither the network access type, nor the cell type matched.

P-Access-Network-Info: 3GPP-E-UTRAN-FDD; utran-cell-id-3gpp=26207FFFDF1B9601, 
3GPP-GERAN; cgi-3gpp=26207FFFDF1B9601; network-provided 

In this case, NPLI was not available.

P-Access-Network-Info: 3GPP-E-UTRAN-FDD; utran-cell-id-3gpp=