To enable a PNI-NPN or SNPN to provide access to localized services, the PNI-NPN or SNPN operator configures the network with information enabling the UEs to access the localized services using the PNI-NPN or SNPN according to any validity of the localized services, and the information is determined in agreement with the localized service provider e.g.:
-
Identification of each localized service, e.g. to be used in URSP rules.
-
validity restriction for each localized service, e.g. the validity of time and/or location.
-
service parameters for each localized service, e.g. DNN, S-NSSAI and QoS requirements.
-
service authorization methods, e.g. NSSAA or Secondary authentication/authorization during PDU Session establishment.
To allow the UE to access the PNI-NPN or SNPN using the HPLMN or subscribed SNPN credential, the PNI-NPN or SNPN can be configured, based on localized service agreements between the PNI-NPN or SNPN and the HPLMN or subscribed SNPN, to allow primary authentication towards a HPLMN, when a PNI-NPN or SNPN is providing access to the localized services, and to allow primary authentication towards a subscribed SNPN, when an SNPN is providing access to the localized services.
To allow the UE to access the SNPN providing access to localized services when new credential is required, the SNPN can provide UE onboarding function as specified in
clause 5.30.2.10 for the UE to obtain credential and necessary information to access the SNPN, or the UE can leverage existing credential and network connection to get access to a PVS via User Plane to obtain new credential.
To allow the UE to access the PNI-NPN providing access to the localized services where NSSAA or secondary authentication/authorization during PDU session establishment is required, the UE can obtain new credential using remote provisioning functionality as defined in
clause 5.39.
To allow the UE to access the HPLMN or subscribed SNPN services while being registered in the PNI-NPN or SNPN, the PNI-NPN or SNPN can establish service agreements and configure inter-connect with the HPLMN or subscribed SNPN operator. If a PNI-NPN is providing access to the localized services, the existing roaming architecture with home-routed PDU Sessions are used. If an SNPN is providing access to the localized services, then the UE can access HPLMN or subscribed SNPN as described in
Annex D, clauses D.3,
D.6 and
D.7.
For configuring the PNI-NPN or SNPN (e.g. creation of network slice/DNN for carrying localized service traffic), existing OAM mechanisms can be re-used as per
clause 6.3.1 of TS 28.557 that provides a solution for NPN provisioning by a network slice of a PLMN and for exposure of management capability of PNI-NPN (
clause 6.3.2). The attributes to support this management is further documented in
TS 28.541.
For session management level information and interactions such as monitoring the PNI-NPN or SNPN performance, and enabling suitable QoS for UE in the PNI-NPN or SNPN for localized service, the following non-exhaustive options can be used:
-
Covered by the SLA between the PNI-NPN or SNPN operator and the localized service provider.
-
Reuse the existing network exposure procedures as specified in clause 4.15 of TS 23.502 where the localized service provider is taking the AF role and utilizing the exposure capability provided by the PNI-NPN or SNPN.
-
Enable NEF/PCF in the PNI-NPN or SNPN providing access to the localized services (via AF of the localized service provider) to receive and forward the validity conditions and QoS requirements of the localized services to the AMF/SMF by reusing the existing PCF initiated AM/SM policy association procedures described in clause 4.16 of TS 23.502.