WO2024081679A1

WO2024081679A1 - Accessing localized services in a wireless communication system

Info

Publication number: WO2024081679A1
Application number: PCT/US2023/076513
Authority: WO
Inventors: Ching-Yu Liao
Original assignee: Google Llc
Priority date: 2022-10-10
Filing date: 2023-10-10
Publication date: 2024-04-18

Abstract

A method for accessing localized services of a hosting network is implemented in a user equipment (UE) associated with a home network. The method includes receiving an indication of whether the UE is to access the localized services of the hosting network via the hosting network or a serving network distinct from the hosting network (1212); and accessing the localized services in accordance with the indication (i) directly via a radio access network (RAN) of the hosting network (1240) or (ii) via a RAN of the serving network operating as an underlay network, and the hosting network operating as an overlay network (1242).

Description

ACCESSING LOCALIZED SERVICES IN A WIRELESS COMMUNICATION SYSTEM

CROSS-REFERENCE TO RELATED APPLICATION

[0001] This application claims priority to and the benefit of the filing date of provisional U.S. Patent Application No. 63/378,999, titled “ENABLING UE TO ACCESS LOCALIZED SERVICES IN 5G SYSTEM,” filed on October 10, 2022. The entire contents of the provisional application are hereby expressly incorporated herein by reference.

FIELD OF THE DISCLOSURE

[0001] This disclosure relates generally to wireless communications and, more particularly, to configuring a user equipment (UE) to access localized services of a hosting network when the UE operates in a serving network.

BACKGROUND

[0002] This background description is provided for the purpose of generally presenting the context of the disclosure. Work of the presently named inventors, to the extent it is described in this background section, as well as aspects of the description that may not otherwise qualify as prior art at the time of filing, are neither expressly nor impliedly admitted as prior art against the present disclosure.

[0003] A Non-Public Network (NPN) is a network that is intended for non-public use, unlike a Public Land Mobile Network (PLMN). The 3rd Generation Partnership Project recently began studying enhancements for a fifth-generation (5G) system to support an NPN as a hosting network for provisioning localized services at a specific location and time. Localized services, also referred to as “local services,” in general are localized to a specific and limited area, and are bounded in time. Applications related to for example live or on-demand audio/video streaming, gaming, and messaging can implement localized services. A localized service provider (LSP) is an application provider or network operator (PLMN or NPN providers) that localizes one or more services and offers the localized services to end users via a hosting network.

[0004] A UE generally subscribes to a home network service, and the subscription in general is an agreement with a home network operator. The home network “owns” and stores current subscription information and credentials of the UE. The home network can be a PLMN or an NPN. When the NPN is a stand-alone NPN (SPN), a credentials holder separate from the SNPN can own the UE access credentials. After leaving the hosting network (e.g., after the relevant localized service completes or terminates), the UE resumes the use of the subscription and the credentials of the home network. To this end, the UE can perform a network selection (e.g., select a home PLMN (HPLMN) or a visited PLMN (VPLMN), and can deactivate the SNPN access mode.

[0005] 3GPP seeks to determine how an NPN can operate as hosting network for providing access to localized services, how a user equipment (UE) can discover, select, and access an NPN as a hosting network and receive localized services, and how a UE can access localized services via a specific hosting network.

[0006] More particularly, neither the provisioning mechanism nor the information a UE needs to discover, select, and access suitable hosting network for localized services are clear. There may be validity conditions, such as time and location constraints, for accessing the hosting network offering the localized services, because of the specifics of the localized service and/or the hosting network. Moreover it is not clear how a UE should be aware of services the UE potentially can access via the hosting NPN.

[0007] Further, it is not clear how a UE already registered in a network (PLMN or NPN) can discover a suitable hosting network and the localized services of the hosting network when the hosting network and/or localized services become available. Still further, the challenges include discovery and selection procedures of the hosting network and the localized services of the hosting network, both in connection with automatic and end-user manual selection; ensuring that the UE accesses the localized services according to the relevant conditions; determining how the UE acquires the credentials (when required) to access the selected localized services of the hosting network; and the defining the mechanisms for authorizing the UE to access the hosting network.

SUMMARY

[0008] An example embodiment of the techniques of this disclosure is a method in a UE for accessing localized services of a hosting network. The method comprises receiving an indication of whether the UE is to access the localized services of the hosting network via the hosting network or a serving network distinct from the hosting network; and accessing the localized services in accordance with the indication (i) directly via a RAN of the hosting network or (ii) via a RAN of the serving network operating as an underlay network, and the hosting network operating as an overlay network.

[0009] Another example embodiment of these techniques is a method in a UE for accessing localized services of a hosting network, comprising receiving a configuration including (i) an indication of an area of interest (AOI) in which the hosting network provides the localized services, and (ii) an indication of an action the UE is to perform upon entering the AOI; and in response to the entering of the AOI, transmitting a registration request including a registration type selected in accordance with the indication of the action.

[0010] Another example embodiment of these techniques is a UE comprising a transceiver and processing hardware configured to implement one of the methods above.

BRIEF DESCRIPTION OF THE DRAWINGS

[0011] Fig. 1 is a block diagram of an example network in which a user equipment (UE) can access localized services via a cellular network;

[0012] Fig. 2 is a block diagram of an example protocol stack according to which the UE of Fig. 1 can communicate with the RAN of Fig. 1;

[0013] Fig. 3 is a service-based representation of the 5GS architecture, including the overall non-roaming reference architecture of the policy and charging control framework for the 5GS;

[0014] Fig. 4 is a reference-point based representation of the 5GS architecture, including overall non-roaming reference architecture of the policy and charging control framework for the 5GS;

[0015] Fig. 5A is a block diagram that illustrates access to PLMN services via an SNPN;

[0016] Fig. 5B is a block diagram that illustrates access to SNPN services via a PLMN;

[0017] Fig. 6A is a block diagram of a home operator owned and/or collaborative interworking between hosting network operators and data applications;

[0018] Fig. 6B is a block diagram of a hosting network operator owned and/or collaborative interworking between hosting network operators and data applications; [0019] Fig. 7A is a block diagram of a system in which a UE accesses a hosting network for localized services directly, via a RAN of the hosting network;

[0020] Fig. 7B is a block diagram of a system in which a UE accesses a hosting network for localized services via a serving network;

[0021] Fig. 8A is a messaging diagram of an example scenario in which a UE accesses a hosting network different from the on-boarding SNPN (ON-SNPN);

[0022] Fig. 8B is a messaging diagram of an example scenario in which a UE accesses a hosting network that also operates as the ON-SNPN;

[0023] Fig. 9 is a messaging diagram of an example scenario in which a UE, after registration, receives steering-of-roaming (SoR) information or overlay network information for localized services via a hosting network;

[0024] Fig. 10 is a messaging diagram of an example scenario in which a UE, after registration, receives SOR information or overlay network information for localized services via a hosting network, where the SOR or overlay network information is applicable to any UE at a specific serving network;

[0025] Fig. 11 A is a messaging diagram of an example a scenario in which a UE receives a monitoring event configuration for use in an area of interest (AOI) corresponding to a list of tracking areas (TAs);

[0026] Fig. 1 IB is a messaging diagram of an example a scenario in which a UE receives a UE parameter update (UPU) with a monitoring event configuration for use in an AOI;

[0027] Fig. 12A is a flow diagram of an example method for determining whether to access localized services via a hosting network or a serving network based on an indication from an home network, which can be implemented in the UE of Figs. 1, 7A, or 7B; and

[0028] Fig. 12B is a flow diagram of an example method similar to that Fig. 12A, but where the hosting network is also the ON-SNPN.

DETAILED DESCRIPTION OF THE DRAWINGS

[0029] In some cases, the home network may prefer to keep a UE registered with the home network at the serving network rather than steering the UE to the hosting network. For example, the home network of the UE may not have a service level agreement (SLA) with the hosting network. As another example, the home network of the UE can have a better charging policy with the serving network of the UE.

[0030] The existing techniques do not address the scenario in which a UE stays with the serving network to access a hosting network for localized services. The techniques discussed below address this concern and, in at least some of the implementations, account for SLAs and/or preferences of network access for localized services. In particular, an SLA can allow for interworking or roaming between two networks for UE authentication, UE configuration, and providing IP connectivity. A UE in some cases can select a network that has an SLA with the home network of the UE. As far as the preference of network access for localized services, a UE can access a hosting network, such as an SNPN, directly or via a non-3GPP Interworking Function (N3IWF) in the hosting network, with the hosting network operating as an overlay network and the serving network operating as an underlay network. Because the UE subscribes to home network services, the home network generally prefers that the UE access network services in view of the SLA of the home network with the hosting network or the serving network.

[0031] In the scenarios discussed below, a hosting network that provides localized services can be an SNPN; the home network with which a UE has a subscription can be a PLMN; and a serving network with which a UE is registered also can be a PLMN. The home network and the serving network of the UE can have an SLA for roaming. For the SLA for interworking between an SNPN (the hosting network) and a PLMN (the serving network), the UE at a first network can access services provided by a second network as an overlay network using Internet Protocol (IP) connectivity which the first network provides as an underlay network based on mechanisms described in ETSI TS 23.501, for example.

[0032] In some scenarios, the serving network is the home network of the UE. In most scenarios discussed below, however, the serving network is distinct from the home network.

[0033] The hosting network can provide localized services directly or via one or more localized service providers (LSPs) with which the hosting network has an SLA. The application function LSP (AF-LSP) can provide information related to localized services hosted by one or more hosting networks to network operators. The AF-LSP can be an application gateway for one or more third-party application providers for localized services and provide roaming/interworking value-added services to network operators that have SLAs with hosting networks.

[0034] The solutions discussed below allow a UE to use localized services via the hosting network based on the SLA among different networks, e.g., the hosting network, the UE's serving network, or the home network of the UE. The UE can select a network that has an SLA with its home network. In one example scenario, the home network of the UE has an SLA with the hosting network, but the serving network of the UE does not have an SLA with the hosting network. In this case, the home network can steer the UE to access the hosting network. In another example scenario, the serving network has an SLA with the hosting network for localized services, but the home network does not have an SLA with the hosting network. In this case, the home network only allows the UE to access the hosting network via the serving network as an underlay network. In yet another example scenario, both the home network and the serving network have SLAs with the hosting network. In this case, the solutions applicable to the first two scenarios are also applicable here.

[0035] For example, a certain PLMN can offer localized services and operate as a hosting network. If the serving network for the UE is an SNPN and the hosting network is a PLMN, to obtain access to localized services via hosting network when the UE is camping in NG-RAN of a SNPN, the UE obtains IP connectivity, discovers, and establishes connectivity to an N3IWF in the PLMN.

[0036] Further, SNPN services can be localized serviced, and an SNPN can operate as a hosting network. If the serving network for the UE is a PLMN, and the hosting network is an SNPN, then in order to obtain access to localized services via hosting network when the UE is camping in NG-RAN of a PLMN, the UE obtains IP connectivity, discovers, and establishes connectivity to an N3IWF in the SNPN.

L _ Access to localized services in an example network

[0037] Referring first to Fig. 1, an example wireless communication system 100 includes a UE 102, a base station (BS) 104, a base station 106, and a core network (CN) 110. The base stations 104 and 106 can operate in a RAN 105 connected to the core network (CN) 110. The CN 110 can be implemented as a fifth generation (5G) core (5GC), for example. The CN 110 can also be implemented as a sixth generation (6G) core in another example.

[0038] The base station 104 covers a cell 124, and the base station 106 covers a cell 126. If the base station 104 is a gNB, the cell 124 is an NR cell. If the base station 124 is an ng-eNB, the cell 124 is an evolved universal terrestrial radio access (E-UTRA) cell. Similarly, if the base station 106 is a gNB, the cell 126 is an NR cell, and if the base station 126 is an ng-eNB, the cell 126 is an E-UTRA cell. The cells 124 and 126 can be in the same Radio Access Network Notification Areas (RNA) or different RNAs. In general, the RAN 105 can include any number of base stations, and each of the base stations can cover one, two, three, or any other suitable number of cells. The UE 102 can support at least a 5G NR (or simply, “NR”) or E-UTRA air interface to communicate with the base stations 104 and 106. Each of the base stations 104, 106 can connect to the CN 110 via an interface (e.g., S 1 or NG interface). The base stations 104 and 106 also can be interconnected via an interface (e.g., X2 or Xn interface) for interconnecting NG RAN nodes.

[0039] An example implementation of the CN 110 is discussed with reference to Figs. 3 and 4 below. Among other components, the CN 110 includes a PDU session anchor (PSA) 112 configured to the UE 102 to a data network 150, route the data packets, manage the quality of service (QoS) for the data session, etc. In this configuration, the data network 150 supports localized services.

[0040] As illustrated in Fig. 1, the base station 104 supports a cell 124, and the base station 106 supports a cell 126. The cells 124 and 126 can partially overlap, so that the UE 102 can select, reselect, or hand over from one of the cells 124 and 126 to the other. To directly exchange messages or information, the base station 104 and base station 106 can support an X2 or Xn interface. In general, the CN 110 can connect to any suitable number of base stations supporting NR cells and/or EUTRA cells.

[0041] Each of the base stations 104 and 106 is equipped with processing hardware 130 that can include one or more general-purpose processors (e.g., CPUs) and a non-transitory computer- readable memory storing instructions that the one or more general-purpose processors execute. Additionally or alternatively, the processing hardware 130 can include special-purpose processing units. The base stations 104 and 106 are equipped with transceivers 132 to support reception and transmission of wireless signals.

[0042] The UE 102 is equipped with processing hardware 134 that also can include one or more general-purpose processors such as CPUs and non-transitory computer-readable memory storing machine-readable instructions executable on the one or more general-purpose processors, and/or special -purpose processing units. The UE 102 also includes a transceiver 135 and a memory 136 storing instructions that implement a local services client 140 and hosting parameters 142, discussed in more detail below.

[0043] Fig. 2 illustrates, in a simplified manner, an example protocol stack 200 according to which the UE 102 can communicate with an eNB/ng-eNB or a gNB (e.g., one or more of the base stations 104, 106). In the example stack 200, a physical layer (PHY) 202A of EUTRA provides transport channels to the EUTRA MAC sublayer 204A, which in turn provides logical channels to the EUTRA RLC sublayer 206A. The EUTRA RLC sublayer 206A in turn provides RLC channels to a EUTRA PDCP sublayer 208 and, in some cases, to an NR PDCP sublayer 210. Similarly, the NR PHY 202B provides transport channels to the NR MAC sublayer 204B, which in turn provides logical channels to the NR RLC sublayer 206B. The NR RLC sublayer 206B in turn provides data transfer services to the NR PDCP sublayer 210. The NR PDCP sublayer 210 in turn can provide data transfer services to Service Data Adaptation Protocol (SDAP) 212 or a radio resource control (RRC) sublayer (not shown in Fig. 2). The UE 102, in some implementations, supports both the EUTRA and the NR stack as shown in Fig. 2, to support handover between EUTRA and NR base stations and/or to support DC over EUTRA and NR interfaces. Further, as illustrated in Fig. 2, the UE 102 can support layering of NR PDCP 210 over EUTRA RLC 206A, and SDAP sublayer 212 over the NR PDCP sublayer 210.

[0044] The EUTRA PDCP sublayer 208 and the NR PDCP sublayer 210 receive packets (e.g., from an Internet Protocol (IP) layer, layered directly or indirectly over the PDCP layer 208 or 210) that can be referred to as service data units (SDUs), and output packets (e.g., to the RLC layer 206A or 206B) that can be referred to as protocol data units (PDUs). Except where the difference between SDUs and PDUs is relevant, this disclosure for simplicity refers to both SDUs and PDUs as “packets.” [0045] On a control plane, the EUTRA PDCP sublayer 208 and the NR PDCP sublayer 210 can provide signaling radio bearers (SRBs) or RRC sublayer (not shown in Fig. 2) to exchange RRC messages or non-access-stratum (NAS) messages, for example. On a user plane, the EUTRA PDCP sublayer 208 and the NR PDCP sublayer 210 can provide data radio bearers (DRBs) to support data exchange. Data exchanged on the NR PDCP sublayer 210 can be SDAP PDUs, Internet Protocol (IP) packets, or Ethernet packets.

[0046] Fig. 3 is a service-based representation 300 of the 5GS architecture, which the system of Fig. 1 can implement. In the representation 300, the overall non-roaming reference architecture of the policy and charging control (PCC) framework for the 5GS includes components illustrated using solid lines, and the other components are illustrated using dashed lines. According to this representation, network functions enable other authorized network functions to access their services. The components that are outside the PCC framework include a Network Slicing Selection Function (NSSF) 302, a Network Repository Function (NRF) 306, a Unified Data Management (UDM) 308, an Edge Application Server Discovery Function (EASDF) 310, a Network Slice Specific Authentication and Authorization Function (NSAAF) 312, an Authentication Server Function (AUSF) 314, a Service Communication Proxy (SCP) 316, and a Network Slice Admission Control Function (NSACF) 316. The non-PCC architecture further includes the UE 102, the RAN 105, and a data network (DN) 330.

[0047] The PCC framework in the architecture 300 includes a Unified Data Repository (UDR) 352, a Network Exposure Function (NEF) 354, a network data analytics function (NWDAF) 356, an Application Function (AF) 357, a Policy Control Function (PCF) 360, a Charging Function (CHF) 362, an Access & Mobility Management Function (AMF) 364, a Session Management Function (SMF) 366, and a User Plane Function (UPF) 370.

[0048] In an example implementation, the AF 358 includes a user consent controller 112A, and the NEF 354 includes a user consent controller 112B. The CN 110 in various implementations can include only the user consent controller 112A, only the user consent controller 112B, or both. The user consent controllers 112A and 112B collectively can be referred to as the user consent control logic 112 of the CN 110.

[0049] Fig. 4 is a reference-point based representation 400 of the 5GS architecture. In Fig. 4, the non-roaming reference architecture of the PCC framework for the 5GS is illustrated as blocks and connections with solid lines, and components and connections outside the PCC framework are illustrated using dashed lines.

II, NPN deployment options and interworking between entities for localized services

[0050] Referring next to Fig. 5A and 5B, the topologies 500A and 500B illustrate the use of an overlay network and underlay network. When a UE is accessing SNPN services via an NWu interface using a user plane established in a PLMN, the SNPN operates as the overlay network. Similarly, when the UE is accessing PLMN services via the NWu interface using a user plane established in an SNPN, PLMN operates as the overlay network. When the UE is accessing SNPN service via an NWu interface using user plane established in a PLMN, the PLMN operates as the underlay network. Similarly, when the UE is accessing PLMN services via an NWu interface using a user plane established in an SNPN, the SNPN operates as the underlay network.

[0051] According to the topology 500A, to obtain access to PLMN services when the UE is camping in the NG-RAN of SNPN, the UE obtains IP connectivity, and discovers and establishes connectivity to an N3IWF in the PLMN. In particular, the N1 interface (for NPN) represents the reference point between UE and the AMF in an SNPN. Further, the NWu interface (for PLMN) represents the reference point between the UE and the N3IWF in the PLMN for establishing a secure tunnel between the UE and the N3IWF over the SNPN. Further, the N1 interface (for PLMN) represents the reference point between the UE and the AMF in the PLMN.

[0052] According to the topology 500B, to obtain access to NPN services when the UE is camping in the NG-RAN of a PLMN, the UE obtains IP connectivity, and discovers and establishes connectivity to an N3IWF in the SNPN. In particular, the N1 interface (for PLMN) represents the reference point between the UE and the AMF in the PLMN. Further, the NWu interface (for NPN) represents the reference point between the UE and the N3IWF in the SNPN for establishing a secure tunnel between the UE and the N3IWF over the PLMN. Further, the N1 interface (for NPN) represents the reference point between UE and the AMF in NPN.

[0053] Depending on the implementation, when using the above mechanism to access an overlay network via an underlay network, the overlay network can act as an authorized third party with the AF to interact with an NEF in the underlay network, to use the existing network exposure capabilities provided by the underlay network. In some implementations, the interaction is subject to agreements between the overlay network and the underlay network.

[0054] Referring next to Figs. 6A and 6B, the diagrams 600A and 600B illustrate example scenarios of interworking between hosting network operators (PLMN or NPN) and data applications based on service agreements for localized services among network operators and application/service providers. In particular, such configuration can include (i) a hosting network operator that owns the 5G network, which provides access and IP connectivity to serving UEs; (ii) a network-operator-owned application layer entities, e.g., a service hosting environment, or an IMS network; (iii) application platforms in third-party domain that can be owned by third party application/service providers, or home/other network operators; and/or (iv) application platforms that could be application servers (e.g., a video-on-demand server, a cloud gaming server), third-party software development platforms, and third-party/operator service hosting environments.

[0055] In the configuration 600A of Fig. 6A, a home-operator-owned and/or collaborative interworking is home-routed. In particular, another network operator and a service/appli cation operator in a third-party domain provide collaborative services in application platforms to a home operator. The arrows depicted in solid lines represent traffic routed over domains within home operator network, while the arrows depicted in dashed lines represent traffic routed over domains outside of home operator network.

[0056] In the configuration 600B of Fig. 6B, a hosting network-operator-owned and/or collaborative-interworking is for a local breakout. In particular, another network operator and an application/service operator in a third-party domain provide collaborative services in application platforms to a hosting network operator and/or home network operator. The arrows depicted in solid lines represent traffic routed over domains within a hosting network, while the arrows depicted in dashed lines represent traffic routed over domains outside of a hosting operator network.

Ill, Direct and indirect access to localized services of a hosting network

[0057] Next, Fig. 7A illustrates an example scheme 700A including a home network 702, a serving network 712, and a hosting network 722 that provides access to localized services 750. The data network that implements the localized services 750 includes an AF-LSP 752. The home network 702 includes a RAN 705 and a CN 707. A PSA 702 operating in the CN 707 provides access to a data network 752 that implements home services. The serving network 712 includes a RAN 715 and a CN 717. A PSA 713 operating in the CN 717 supports a logical connection to the PSA 702, and a N3IWF 714 operating in the CN 717 supports a logical connection to the hosting network 722. In particular, the hosting network 722 includes a RAN 725 and a CN 727, in which a PSA 723 supports a logical connection to the N3IWF 714 of the serving network 712, and a PSA 726 supports a logical connection to a data network 750 that implements localized services. The home network 702, the serving network 712, and the hosting network 722 interconnect in view of the SLA 760.

[0058] In some implementations, a combination of PLMN-Identifier and/or Network Identifier (NID) identify an SNPN such as the hosting network 722. An NID consists of 11 hexadecimal digits, one digit for representing an assignment mode, and 10 digits for an NID value, in an example implementation. NID assignment can occur according to one of the following assignment models. According to the self-assignment model, SNPNs chose NIDs individually at deployment time. To indicate this assignment model, a network can set the assignment mode digit to “1.” According to the coordinated assignment model, operators assign NIDs using one of the following two options: (i) assigning the NID so that it is globally unique independent of the PLMN ID used, or (ii) assigning the NID so that the combination of the NID and the PLMN ID is globally unique. Depending on the implementation, a network encodes option (i) of the assignment model by setting the assignment mode to “0,” and encodes option (ii) of the assignment model by setting the assignment mode to “2.” Depending on the implementation, the self-assignment NID model does not apply if the UE 102 accesses the SNPN 722 using the credentials from a credentials holder via an Authentication, Authorization, and Accounting (AAA) server.

[0059] With continued reference to Fig. 7A, the UE 102 connects directly to the RAN 725. The UE 102 accordingly accesses the localized services 750 directly via the PSA 726. In this scenario, the preference of network access for localized services is hosting network, and the UE 102 activates the SNPN access mode and performs hosting network discovery and selection procedure, as discussed below. The UE 102 then switches and registers to the selected hosting network for localized services directly.

[0060] In contrast to the scheme 700A, a scheme 700B of Fig. 7B includes a UE 102 connecting to the RAN 715 of the serving network 712 and accesses the localized services 750 indirectly via the PSA 716 and the N3IWF 714 of the hosting network 722. The serving network 712 according to the scheme 700B operates as an underlay network providing IP connectivity, and the hosting network 722 operates as an overlay network. The preference of network access for localized services is serving network in this case, and the UE 102 at the serving network 712 performs N3IWF and hosting network discovery and selection, and then registers to the hosting 722 network via the serving network 712.

[0061] The UDM of the home network 702 can determine the preference of network access for localized services. Based on the preferred network access for localized services, the UE 102 can access the hosting network 722 directly as illustrated in Fig. 7A, or indirectly via the N3IWF 724 as illustrated in Fig. 7B. The home network 702 can determine the preference of network access in view of the SEA 760.

[0062] Fig. 8 A illustrates an example scenario 800A in which the UE 102 accesses the hosting network 722 distinct from the on-boarding SNPN (ON-SNPN).

[0063] The scenario 800A begins with establishing 802 an SLA among the networks 702, 712, and 722. The hosting network 722 then provisions 810 parameters of localized services, e g. the area of interest (AO I), the time period, to the home network 702 (when the home network 702 has an SLA with the hosting network 722 for localized services) or the serving network 712 (when the serving network 712 has an SLA with the hosting network 722 for localized services). The provisioning 810 can be based on the SLA between network operators. The AOI can be a predefined area represented by a list of Tracking Areas (TAs), a list of cells, or a list of RAN node identifiers, for example.

[0064] The UE 102 enters 820 the AOI during a configured valid time period. The UE 102 and/or the AMF of the serving network 712 detects the monitoring even of the UE 102 entering a configured AOI (see Figs. HA and 1 IB), and triggers a procedure to configure the UE 102 with the following information : (i) parameters for on-boarding network selection, and default credential for accessing on-boarding network (ON-SNPN), which is common for the on-boarding networks, and/or (ii) parameters for hosting network discovery and selection or for hosting network/N3IWF discovery and selection based on preference of network access for localized services.

[0065] The UE 102 then performs 830 an on-boarding procedure with the ON-SNPN for user plane remote provisioning of hosting network configuration, e.g. credentials for accessing the hosting network 722 as the SO-SNPN, and parameters for accessing localized services. The UE 102 accesses to hosting network 722 based on the indication of preferred network access. If the indication of preferred network access is set to hosting network, the UE 102 activates SNPN access mode and performs 832 a hosting network discovery and selection based on SoR information including list of combination of SNPN ID (PLMN ID+NID) and RAT in priority order. However, if the indication of preferred network access is serving network, the UE performs 832 hosting network/N3IWF discovery and selection based on combination of N3IWF and hosting network in priority order.

[0066] Further, the UE 102 registers 840 with the hosting network using the credentials of hosting networks provisioned by the on-boarding network and then establishes PDU sessions for localized services via hosting network. The UE 102 then connects 850 to the localized services portal.

[0067] Fig. 8B is a messaging diagram of an example scenario 800B in which a UE accesses a hosting network that also operates as the ON-SNPN. The scenario 800B includes events 802, 810, 822, and 822 similar to the scenario 800A.

[0068] The UE 102 accesses 831 the hosting network 722 based on the indication of preferred network access. If the indication of preferred network access is set to hosting network, the UE 102 activates the SNPN access mode and performs hosting network discovery and selection based on SoR in-formation including list of combination of SNPN ID (PLMN ID+NID) and RAT in priority order. If the indication of preferred network access is set to serving network, the UE 102 performs hosting network/N3IWF discovery and selection based on combination of N3IWF and hosting network in priority order. [0069] The UE 102 performs 833 an on-boarding procedure with the selected hosting network 722 as the on-boarding network (as ON-SNPN) for user plane remote provisioning of hosting network configuration, e.g. credentials to access hosting network (as SO-SNPN), and parameters to access localized services.

[0070] The UE 102 then registers 840 with the hosting network 722 using the credentials of hosting networks provisioned by the on-boarding network. Then UE 102 performs 840 a PDU session establishment request procedure toward the registered hosting network or the registered hosting network via N3IWF for localized services by indicating DNN/S-NSSA1 for localized services in the PDU session establishment request message. As part of the PDU session request procedure, the PDU session response message may contain a localized services portal URL in the PCO IE (protocol configuration), which takes precedence over the configured Localized services portal URL at the UE.

[0071] The UE 102 then connects 850 to the localized services portal and selects a localized service. The UE 102 may request a new PDU session using corresponding DNN/S-NSSAI to access LSP application server.

IV. Initiating localized services configuration when the home network has an SLA with the localized service provider

[0072] Next, Fig. 9 depicts a scenario 900 for provisioning SoR information or overlay network information for localized services via a hosting network to the UE after registration. In particular, the scenario of Fig. 9 may initiate localized services configuration to a UE (e.g., the UE 102) by the AF-LSP to the home network 702 which has an SLA with the hosting network 722 for localized services. The UE can be identified using a target UE Identifier, which can be a Generic Public Subscription Identifier (GPSI) allocated for an individual UE or an External Group Identifier allocated for a group of UEs. If not indicated, the UE represents any UE, and the UE is registering or registered with the serving network, and with or without subscription to the localized services, when entering the AOI.

[0073] The AF-LSP can provide the localized services parameters (e g. AOI configuration and valid time period) to the home network of the UEs (e.g., the home network 702). The AOI can be a predefined area that corresponds to a list of Tracking Areas, a list of cells, or list of (R)AN node identifiers. Before expiry of the valid time period, the localized services parameters provisioning to UE is triggered when the Target UE or any UE enters the configured AOI. In some implementations, the events of Fig. 9 apply to the scenario described above in connection with Fig. 8B.

[0074] The AF-LSP sends 902 a Nudm ParameterProvision message for localized services activation to the UDM of the home network of the UE (denoted as H-UDM), which in this scenario has an SLA with the hosting networks for localized services. The message can include the following localized service information: (i) target UE identifier: a UE identifier, a group of UEs, or any UEs; (ii) Validity Condition: AOI, time duration for location localized services; (iii) Indication of Localized service; (iv) Event ID Subscription for UE monitoring event of entering AOI; and/or (v) A list of serving network IDs, e.g. PLMN ID if serving network is PLMN or SNPN ID (PLMN ID plus NID) if serving network is SNPN. Alternatively, the AF-LSF can subscribe to UDM via NEF for the monitoring event of UE enter-ing AOI by sending Nnef EventExposure message to NEF.

[0075] As an alternative to an indication of localized service, a localized service ID can be applied to uniquely identify a localized service provided by one or more hosting networks. The home network or serving network needs to query DNS for obtaining the information of hosting networks.

[0076] Using the localized service ID or indication of Localized service, the UDM of the home network checks whether the UE has subscription of localized services. If yes, the UDM provides the following information to the AMF of the selected serving network to subscribe 910 to the AOI monitoring event, and the UDM selects the serving networks based on the SLA with the serving network as well as the list of serving network IDs provided by the AF-LSP at step 902 (when available). The UDM can provide o(i) Target UE identifier, including a UE identifier, a group of UEs, or any UEs; (ii) Event ID for Subscribing to UE monitoring event of entering AOI; and/or (iii) Validity Condition, such as AOI, time period for location localized services.

[0077] The UE or AMF is configured 920 with the monitoring event of entering AOI and corresponding actions to take if the event occurs. When the UE enters the AOI, the UE or AMF detects 930 the event and performs the configured actions (see Figs. HA and/or 1 IB). The AMF notifies 912 UDM of the home network including the UE ID and the serving network ID of the UE.

[0078] Next, based on the serving network ID of the UE, the H-UDM determines 940 its preferences of network access for localized services and sends 942 a SoR GetRequst message in to AF-LSP with the following information: (i) Target UE Identifier; (ii) Preferred network access indication, e.g. hosting network or serving network; and/or (iii) Serving network ID.

[0079] The AF-LSP sends 952 a SoR Get Response message to H-UDM including the information for hosting network discovery and selection, such as a Target UE Identifier. If the indication of preferred network access is hosting network, the AF-LSP provides SOR info, including list of combination of SNPN ID (i.e. PLMN ID+NID) and RAT in priority order. If the indication of preferred network access is serving network, the AF-LSP provides overlay network information including list of combination of N3IWF addresses and hosting networks in priority order. The H-UDM further delivers 960 the information to AMF in a

Nudm SDM Notification message including information: UE ID, SoR or Overlay network information.

[0080] The AMF delivers 970 the information to the UE for UE configuration via DL NAS transport message including the following info: (i) Validity condition for the authorized localized services including AOI and valid time period for localized services; (ii) Authorization to access localized service via hosting network; (iii) Information for hosting network discovery and selection; (iv) ON boarding configuration information for accessing on boarding network, e.g.

(a) default credential for registering on-boarding network, (b) parameters for on-boarding network selection (see Fig. 7A) or on-boarding indication, (see Fig. 7B) indication of preferred network access, e.g. hosting network or serving network; and/or (v) Localized services portal URL (which may be the same or different for different host-ing networks).

[0081] The UE performs 980 a security check on the received SoR info or overlay network information, stores the SoR or Overlay network information if security check is successful, and responds 982, 984, 986 to the AF-LSP via AMF and H-UDM if response is needed indicated in the SoR GetResponse message at event 752. [0082] Next, Fig. 10 illustrates a scenario 1000 for provisioning SoR information or overlay network information for localized services via hosting network to the UE after registration, which is for a target UE identifier or any UEs at a specific serving network. This approach is generally similar to the solution discussed above, when the serving network is considered to have an SLA with a localized service provider, but the home network does not have an SLA with the localized service provider. Referring to Fig. 10, the following modification are applied to the solution discussed above.

[0083] The AF-LSP sends 1002 a Nudm ParameterProvision message for localized services activation to the UDM of UEs' serving network (denoted as S-UDM) that has SLA with the hosting networks for localized services. The message can include the following information: (i) Target UE identifier: a UE identifier, a group of UEs, or any UEs; (ii) Validity Condition: AOI, time duration for location localized services; (iii) Indication of Localized service; (iv) Event ID Subscription for UE monitoring event of entering AOI.

[0084] Alternatively, the AF-LSF can subscribe to UDM via NEF for the monitoring event of UE entering AOI by sending Nnef EventExposure message to NEF.

[0085] As an alternative to Indication of Localized service, Localized service ID can be applied to uniquely identify a Localized service provided by one or more hosting networks. The home network or serving network needs to query DNS for obtaining the information of hosting networks.

[0086] The UDM provides 1010 the following information to AMF(s) to subscribe to the AOI monitoring event, where the AMF(s) is selected by the S-UDM based on AOI indicated by the hosting network at event 1002. The message can include (i) Target UE identifier: a UE identifier, a group of UEs, or any UEs; (ii) Event ID for Subscribing to UE monitoring event of entering AOI; and Validity Condition: AOI, time period for location localized services.

[0087] Next, the UE 102 or AMF is configured 1020 with the monitoring event of entering AOI and corresponding actions to take if the event occurs. When the UE enters the AOI, the UE or AMF detects 1030 the event and reacts with configured actions (as discussed below).

[0088] The AMF sends 1040 a Nudm SDM request message to H-UDM including the UE ID, the UE’s serving network ID, and Localized service indication or Localized service ID for authorization. The H-UDM determines 1042 its preferences of network access for localized services in, and sends 1044 aNudm SDM response message to the AMF indicating the following information: (i) UE ID, (ii) Localized Services Authorization, and (iii) preferences of network access for localized services.

[0089] The AMF sends 1050 a Nudm SDM request message to S-UDM including (i) UE ID,

(ii) UE's Home network ID, and (iii) preferences of network access for localized services. The S-UDM sends 1052 a SoR GetRequest message to the AF-LSP with the following information: (i), UE ID, (ii) preferred network access indication, e.g. hosting network or serving network, and

(iii) .UE's Home network ID.

[0090] The AF-LSP sends 1054 SoR Get Response message to H-UDM including the information for hosting network discovery and selection: (i) If the indication of preferred network access is hosting network, the AF-LSP provides SOR info, including list of combination of SNPN ID (i.e. PLMN ID+NID) and RAT in priority order; (ii) If the indication of preferred network access is serving network, the AF-LSP provides overlay network information including list of combination of N3IWF addresses and hosting networks in priority order. The H-UDM further delivers 1056 the information to the AMF in aNudm SDM Notification message including the following information: UE ID, SoR or Overlay network information.

[0091] The AMF delivers 1070 the information to the UE for UE configuration via DL NAS transport message including the following: (i) Validity condition for the authorized localized services including AOI and valid time period for localized services; (ii) Authorization to access localized service via hosting network; (iii) Information for hosting network discovery and selection; (iv) ON boarding configuration information for accessing on boarding network, e.g. default credential for registering on-boarding network, parameters for on-boarding network selection or on-boarding indication, indication of preferred network access, e.g. hosting network or serving network. The message can also include Localized services portal URL (which may be the same or different for different hosting networks).

[0092] The UE 102 then performs 1080 security check on the received SoR info or overlay network information, stores the SoR or Overlay network information if security check is successful, and responds to the AF-LSP via AMF and H-UDM if response is needed indicated in the SoR GetResponse message at event 1054. [0093] Referring generally to Figs. 11 A and 1 IB, these approaches are based on monitoring event configuration for the target UE, or any UEs that enter the AOI. The AMF can configure the monitoring event for the a UE that enters the AOI as follows: the AMF generates an AOI indication which represents the monitoring event of entering AOI for the UE; if there are multiple monitoring events of UE entering AOI, the AOI indication may be an enumerated value that uniquely identifies the event for the UE.

V, Monitoring event configuration for a target UE or any UE entering the AOI

[0094] Further, the following two options for handling a monitoring event of a UE entering AOI are considered with reference to Figs. HA and 1 IB.

[0095] Referring first to Fig. 11 A, the granularity of this option is a TA (for UE in 5GMM connected state) or a TAI list (for UE in 5GMM idle state).

[0096] The H-UDM sends 1102 a Nudm EventExposure subscribe message to the AMF to subscribe the monitoring event of UE entering AOI with validity condition with a new Event ID set as UE entering AOI. The AMF stores 1110 the Event ID, AOI, and the AOI indication with corresponding action to take if the event occurs. The AMF allocates 1120 the Track Areas Identity TAI list (5GS tracking area identity list) that matches configured AOI to the UE during Registration Request procedure.

[0097] Next, the UE enters 1130 an AOI. Event 1140 corresponds to the UE operating in the idle state. The UE sends 1140 registration request message with registration type set as mobility update when periodic tracking area timer is expired, move out of assigned list of Tracking Areas.

[0098] The AMF detects 1150 a UE is entering the AOI based on the stored AOI indication. The AMF 1154 performs the configured action.

[0099] Referring now to Fig. 1 IB, this option in general provides better granularities for AOI monitoring and notification. First, the H-UDM sends 1102 a Nudm EventExposure subscribe message to the AMF to subscribe to the monitoring event of a UE entering AOI with validity condition with a new Event ID set as UE entering AOI. The AMF stores 1110 the Event ID, AOI, and the AOI indication with corresponding action to take if the event occurs.

[0100] The AMF configures 1123 UE with localized services parameters using UE parameter update (UPU) procedure. The UPU container can include the following: an AOI which can be represented by represented by a list of Tracking Areas, list of cells or list of (R)AN node identifiers; a validity time period; an AOI indication; an action for entering the configured AOI with valid time period as follows: (i) optionl : send registation request including registration type set as mobility update and AOI indication; or (ii) option2: send registration request including a new registration type set as AOI update.

[0101] The UE 102 detects 1132 that it enters the AOI based on stored AOI and AOI indication. The UE 102 performs 1142 registration request including the following IES: the AOI indication; and registration type indicated as Mobility Update or a new registration type indicated as AOI update. The AMF then performs 1152 the configured action to notify H-UDM of the UE in the Nudm EventExposure Notify message.

VI. The on-boarding procedure via hosting network or hosting network/N3IWF

[0102] According to one example approach, the on-boarding procedure proceeds via a hosting network (e.g., the hosting network 722) or hosting network/N3IWF.

[0103] Referring back to events 830 and 832 discussed above, to enable support of UE authentication at a hosting network with which the UE does not have a subscription, the following approach provides an on boarding UE procedures including steps.

[0104] At step 1, the home network or the serving network of the UE provisions an onboarding configuration information to the UE (see Approach A below). At step 2, the UE performs on boarding registration procedure to the hosting network (see Approach B), whereby the hosting network, as a credential holder, authenticates the UE based on UE credential for onboarding included in on-boarding configuration information. At step 3, the UE establishes a PDU session based on DNN/S-NSSAI in on-boarding configuration information and connects to Provision Server for performing UP remote provisioning to UE (solution Approach C).

[0105] Approach A is based on steps 1-5 above. According to this approach, the UE needs to register with a serving network as an underlay network and then registers with a hosting network/N3IWF as an overlay network for UP (user plane) remote provisioning. The home network or the serving network provisions some or all of the following on-boarding configuration information to the UE: (i) validity condition: time period and AOI for localized services; (ii) authorization for localized service; (iii) default credential for registering on boarding network, e.g. SUPI, used for onboarding which may contain an IMSI or a networkspecific identifier; (iv) indication of preferred network access, e.g. hosting network or serving network; (v) optionally, PVS IP address or PVS FQDN for User Plane Remote Provisioning (if provided, it is stored at UE Configuration Data for UP remote provisioning); (vi) parameters for on-boarding network selection. The parameters (vi) can be: if preference of network for localized services is serving network, hosting network ID (SNPN ID, i.e. PLMN ID plus NID) with a N3IWF FQDN for on-boarding (see Fig. 7A) or on-boarding indication (see Fig. 7B); if preference of network for localized services is hosting network, hosting network ID, (SNPN ID, i.e. PLMN ID plus NPN ID) for on-boarding.

[0106] Approach B is generally based on Approach A. When the validity conditions of on boarding configuration are met, e.g. at the specific location and time, and the UE at serving network performs on boarding procedure as follows: (i) the existing UE onboarding registration mechanism can be applied based on TS23.501 clause 5.30.2.10.2.6 (“Registration for UE onboarding”); (ii) if the preference of network for localized services is serving network, then the UE at serving network performs registration procedure with 5GS Registration Type indicated as "SNPN Onboarding" and UE identity indicated as UE Credential for on-boarding towards configured hosting network/N3IWF based on N3IWF FQDN of hosting network for on-boarding via PDU session established at serving network; (iii) if the preference of network for localized services is hosting network, then the UE performs registration procedure with 5GS Registration Type indicated as "SNPN Onboarding" and UE identity indicated as UE Credential for onboarding towards selected hosting network.

[0107] Approach C is generally based on Approach B. When the on-boarding registration is successful, the AMF selects a SMF for on-boarding at on boarding hosting network to perform UP remote Provisioning to UEs by connecting to Provisioning Server (PVS), which is provided by the UE (based on on-boarding configuration information as described with reference to Fig. 7A) during registration request procedure or configured at the SMF, with information of localized services configuration including: (i) N3IWF FQDN of hosting network for accessing localized services (ii) UE Credential of the Hosting network for primary authentication, (iii) DNN/S-NSSAI of PDU session for localized services, and (iv) optionally, a localized services portal URL. [0108] Further, Approach D is generally based on Approach C. Here, the UE deregisters from on boarding hosting network based on network-initiated or UE-deregi strati on deregistration procedure. Optionally, the re-registration indication can be set to trigger the UE to perform re-registration procedure to the same selected hosting network for localized services.

[0109] Fig. 12A is a flow diagram of an example method 1200A for determining whether to access localized services via a hosting network or a serving network based on an indication from a home network, which can be implemented in the UE of Figs. 1, 7A, or 7B. At block 1202, the UE enters a configured AOI for a localized service. At block 1210, the UE receives parameters for on-boarding network selection and a default credential. At block 1212, the UE receives parameters for hosting network discovery and selection. At block 1220, the UE performs an onboarding procedure with the on-boarding network.

[0110] At block 1230, the UE determines whether it received an indication of preferred network access set to a hosting network (in which case the flow proceeds to block 1240) or a serving network (in which case the flow proceeds to block 1242). At block 1240, the UE activates SNPN access mode and performs discovery and selection based on the SoR information. At block 1242, the UE performs a hosting network/N3IWF discovery and selection based on a combination of N31WF ad hosting network in priority order.

[0111] Fig. 12B is a flow diagram of an example method 1200B similar to that Fig. 12A, but where the hosting network is also the ON-SNPN. According to this procedure the UE performs an on-boarding procedure with the selected hosting network as the on-boarding network at block 1222, after performing access according to the serving network or hosting network options.

[0112] The following description may be applied to the description above.

[0113] In some implementations, “message” is used and can be replaced by “information element (IE)”. In some implementations, “IE” is used and can be replaced by “field”. In some implementations, “configuration” can be replaced by “configurations” or the configuration parameters. In some implementations, “early data communication” can be replaced by “small data communication” and “early data transmission” can be replaced by “small data transmission”. [0114] A user device in which the techniques of this disclosure can be implemented (e.g., the UE 102) can be any suitable device capable of wireless communications such as a smartphone, a tablet computer, a laptop computer, a mobile gaming console, a point-of-sale (POS) terminal, a health monitoring device, a drone, a camera, a media-streaming dongle or another personal media device, a wearable device such as a smartwatch, a wireless hotspot, a femtocell, or a broadband router. Further, the user device in some cases may be embedded in an electronic system such as the head unit of a vehicle or an advanced driver assistance system (ADAS). Still further, the user device can operate as an internet-of-things (loT) device or a mobile-internet device (MID). Depending on the type, the user device can include one or more general-purpose processors, a computer-readable memory, a user interface, one or more network interfaces, one or more sensors, etc.

[0115] Certain embodiments are described in this disclosure as including logic or a number of components or modules. Modules may be software modules (e.g., code, or machine-readable instructions stored on non-transitory machine-readable media) or hardware modules. A hardware module is a tangible unit capable of performing certain operations and may be configured or arranged in a certain manner. A hardware module can comprise dedicated circuitry or logic that is permanently configured (e.g., as a special-purpose processor, such as a field programmable gate array (FPGA) or an application-specific integrated circuit (ASIC), a digital signal processor (DSP), etc.) to perform certain operations. A hardware module may also comprise programmable logic or circuitry (e.g., as encompassed within a general-purpose processor or other programmable processor) that is temporarily configured by software to perform certain operations. The decision to implement a hardware module in dedicated and permanently configured circuitry, or in temporarily configured circuitry (e.g., configured by software), may be driven by cost and time considerations.

[0116] When implemented in software, the techniques can be provided as part of the operating system, a library used by multiple applications, a particular software application, etc. The software can be executed by one or more general-purpose processors or one or more specialpurpose processors.

Claims

What is claimed is:

1. A method for accessing localized services of a hosting network, the method implemented in a user equipment (UE) associated with a home network and comprising: receiving an indication of whether the UE is to access the localized services of the hosting network via the hosting network or a serving network distinct from the hosting network; and accessing the localized services in accordance with the indication (i) directly via a radio access network (RAN) of the hosting network or (ii) via a RAN of the serving network operating as an underlay network, and the hosting network operating as an overlay network.

2. The method of claim 1, further comprising: determining that the UE has entered an area of interest (AO I) in which the hosting network provides the localized services; and in response to the determining, performing a procedure for obtaining one or more parameters for discovery and selection of the hosting network.

3. The method of claim 2, further comprising: receiving, from the serving network, a list of tracking areas (AIs) corresponding to the AOI.

4. The method of claim 2, further comprising: receiving, from the serving network, a list of cells corresponding to the AOI.

5. The method of claim 2, further comprising: receiving, from the serving network, a list of identifiers of radio access network (RAN) nodes corresponding to the AOI.

6. The method of claim 2, wherein: the performing of the procedure for obtaining the one or more parameters is further in response to determining that the UE has entered the AOI during a configured time period.

7. The method of any of the preceding claims, wherein the hosting network is a standalone non-public network (SNPN).

8. The method of any of the preceding claims, wherein: when the indication indicates access of the localized services via the hosting network, activating an SNPN access mode and hosting network discovery and selection based on a steering-of-roaming (SoR) information.

9. The method of claim 8, wherein the SoR information includes a SNPN Identifier composed of a PLMN Identifier and a Network Identifier (NID).

10. The method of any of claims 1-9, wherein: when the indication indicates access of the localized services via the serving network, performing a hosting network/N3IWF discovery and selection based on a combination of N3IWF and hosting network.

11. The method of any of the preceding claims, further comprising: registering with the hosting network using credentials provisioned by an on-boarding network.

12. The method of claim 11, wherein the on-boarding network is the hosting network.

13. A user equipment (UE) comprising: a transceiver; and processing hardware configured to implement a method of any of the preceding claims.