EP4620210A1 - Serving network location based validity condition for localized service and enhanced sor procedure for localized service - Google Patents

Abstract

Systems and methods are disclosed that relate to a serving network location-based validity condition for localized services. In one embodiment, a method performed by a User Equipment (UE) comprises registering with a serving network and receiving localized service information from the serving network, the localized service information comprising a validity area condition that indicates, using one or more serving network related identifiers, one or more areas in which one or more localized services of a hosting service are available and/or in which the hosting network is available. The method further comprises determining that the validity area condition is satisfied and, responsive to determining that the validity area condition is satisfied, initiating a scan for the hosting network. In this manner, a validity area condition for localized service(s) can be evaluated without requiring the UE to activate, e.g., a Global Positioning System (GPS) receiver or network-based location services.

Description

SERVING NETWORK LOCATION BASED VALIDITY CONDITION FOR LOCALIZED SERVICE AND ENHANCED SoR PROCEDURE FOR LOCALIZED SERVICE

Related Applications

[0001] This application claims the benefit of provisional patent application serial number 63/425,158, filed November 14, 2022, the disclosure of which is hereby incorporated herein by reference in its entirety.

Technical Field

[0002] The present disclosure relates to a cellular communications system and, more specifically, to providing access to localized services in a cellular communications system.

Background

[0003] The 3^rd Generation Partnership Project (3GPP) is currently standardizing solutions for requirements associated to localized services, which is also known as Providing Access to Localized Service (PALS), as studied by SAI and described in 3GPP Technical Report (TR) 22.844 (see, e.g., V18.2.0). The requirements are included in chapter 6.41 of 3GPP Technical Specification (TS) 22.261 (see e.g., V19.0.0) 5^th Generation (5G) Service requirement specification. The SA2 study is still ongoing and documented in 3GPP TR 23.700-08 (see e.g., VI.3.0).

[0004] With PALS, it is possible to get localized services (i.e., services that are temporary and restricted to a certain area only) through a hosting network. Figure 1 illustrates an example of a hosting network providing services at an arena. A hosting network can be either a regular Public Land Mobile Network (PLMN) or a Non-Public Network (NPN) (e.g., deployed as Public Network Integrated (PNI) NPN or a Stand-alone NPN (SNPN)), and there are several possible solutions for how it can be accessed. Either separate credentials/subscriptions are needed for the hosting network or the hosting network can have an onboarding mechanism by which it allows any User Equipment (UE) to configure access (e.g., using a credentials server) or alternatively, a hosting network and localized services can be used using the same subscription credentials as used for accessing a home network. If a UE is already registered to a network that is not the hosting network at the time and/or location when the localized services is about to start, then there needs to be a solution for how a UE can switch to the hosting network offering the localized services. Summary

[0005] Systems and methods are disclosed that relate to a serving network location-based validity condition for localized services. In one embodiment, a method performed by a User Equipment (UE) comprises registering with a serving network and receiving localized service information from the serving network, the localized service information comprising a validity area condition that indicates, using one or more serving network related identifiers, one or more areas in which one or more localized services of a hosting service are available and/or in which the hosting network is available. The method further comprises determining that the validity area condition is satisfied and, responsive to determining that the validity area condition is satisfied, initiating a scan for the hosting network. In this manner, a validity area condition for localized service(s) can be evaluated without requiring the UE to activate, e.g., a Global Positioning System (GPS) receiver or requiring the UE to use network-based location services.

[0006] In one embodiment, the one or more serving network related identifiers comprise one or more tracking area codes of the serving network. In one embodiment, determining that the validity area condition is satisfied comprises receiving, from the serving network, broadcast information comprising a tracking area code and determining that the tracking area code comprised in the broadcast information satisfies the validity area condition.

[0007] In one embodiment, the one or more serving network related identifiers comprise one or more cell identities of the serving network. In one embodiment, the one or more serving network related identifiers comprise one or more tracking area codes of the serving network and one or more cell identities of the serving network. In one embodiment, determining that the validity area condition is satisfied comprises receiving, from the serving network, broadcast information comprising a cell identity or both a tracking area code and a cell identity and determining that the cell identity or both the tracking area code and cell identity comprised in the broadcast information satisfies the validity area condition.

[0008] In one embodiment, the method further comprises detecting the hosting network via the scan and initiating a network selection procedure and registration procedure with the detected hosting network.

[0009] In one embodiment, the method further comprises detecting the hosting network via the scan and informing a user and/or an application layer of the UE that the hosting network and/or the one or more localized services of the hosting network are available. In one embodiment, the method further comprises initiating a network selection procedure and registration procedure with the detected hosting network, upon reception of a trigger of selection of the hosting network and/or at least one of the one or more localized services of the hosting network.

[0010] In one embodiment, the serving network is a home network of the UE. In another embodiment, the serving network is a network other than a home network of the UE, but the UE uses home network credentials to access the serving network.

[0011] Corresponding embodiments of a UE are also disclosed. In one embodiment, a UE is adapted to register with a serving network and receive localized service information from the serving network, the localized service information comprising a validity area condition that indicates, using one or more serving network related identifiers, one or more areas in which one or more localized services of a hosting service are available and/or in which the hosting network is available. The UE is further adapted to determine that the validity area condition is satisfied and, responsive to determining that the validity area condition is satisfied, initiate a scan for the hosting network.

[0012] In one embodiment, a UE comprises a transmitter, a receiver, and processing circuitry associated with the transmitter and the receiver. The processing circuitry is configured to cause the UE to register with a serving network and receive localized service information from the serving network, the localized service information comprising a validity area condition that indicates, using one or more serving network related identifiers, one or more areas in which one or more localized services of a hosting service are available and/or in which the hosting network is available. The processing circuitry is further configured to cause the UE to determine that the validity area condition is satisfied and, responsive to determining that the validity area condition is satisfied, initiate a scan for the hosting network.

[0013] Embodiments of a method performed by a network node are also disclosed. In one embodiment, a method performed by a network node of a serving network of a UE comprises providing localized service information to the UE, the localized service information comprising a validity area condition that indicates, using one or more serving network related identifiers, one or more areas in which one or more localized services of a hosting service are available and/or in which the hosting network is available.

[0014] In one embodiment, the one or more serving network related identifiers comprise one or more tracking area codes of the serving network.

[0015] In one embodiment, the one or more serving network related identifiers comprise one or more cell identities of the serving network. In one embodiment, the one or more serving network related identifiers further comprise one or more tracking area codes of the serving network. [0016] Corresponding embodiments of a network node are also disclosed. In one embodiment, a network node for a serving network of a UE is adapted to provide localized service information to the UE (600), the localized service information comprising a validity area condition that indicates, using one or more serving network related identifiers, one or more areas in which one or more localized services of a hosting service are available and/or in which the hosting network is available.

[0017] In another embodiment, a network node for a serving network of a UE comprises processing circuitry configured to cause the network node to provide localized service information to the UE (600), the localized service information comprising a validity area condition that indicates, using one or more serving network related identifiers, one or more areas in which one or more localized services of a hosting service are available and/or in which the hosting network is available.

Brief Description of the Drawings

[0018] The accompanying drawing figures incorporated in and forming a part of this specification illustrate several aspects of the disclosure, and together with the description serve to explain the principles of the disclosure.

[0019] Figure 1 illustrates an example of a hosting network providing services at an arena;

[0020] Figure 2 illustrates one example of a cellular communications system in which embodiments of the present disclosure may be implemented;

[0021] Figures 3 and 4 illustrate examples in which the cellular communications system is implemented as a 3^rd Generation Partnership Project (3GPP) 5^th Generation (5G) system;

[0022] Figure 5 illustrates an example deployment of a hosting network for Providing Access to Localized Services (PALs);

[0023] Figure 6 illustrates a procedure for providing and utilizing serving network-based validity condition for localized service, in accordance with one example embodiment of a first solution of the present disclosure;

[0024] Figure 7 illustrates a procedure in accordance with one example embodiment of a second solution of the present disclosure;

[0025] Figure 8 illustrates a procedure in accordance with another example embodiment of a second solution of the present disclosure;

[0026] Figures 9, 10, and 11 are schematic block diagrams of example embodiments of a network node; [0027] Figures 12 and 13 are schematic block diagrams of example embodiments of a User Equipment (UE);

[0028] Figures 14 through 36 are reproductions of various figures and tables from various 3GPP technical specifications.

Detailed Description

[0029] Generally, all terms used herein are to be interpreted according to their ordinary meaning in the relevant technical field, unless a different meaning is clearly given and/or is implied from the context in which it is used. All references to a/an/the element, apparatus, component, means, step, etc. are to be interpreted openly as referring to at least one instance of the element, apparatus, component, means, step, etc., unless explicitly stated otherwise. The steps of any methods disclosed herein do not have to be performed in the exact order disclosed, unless a step is explicitly described as following or preceding another step and/or where it is implicit that a step must follow or precede another step. Any feature of any of the embodiments disclosed herein may be applied to any other embodiment, wherever appropriate. Likewise, any advantage of any of the embodiments may apply to any other embodiments, and vice versa. Other objectives, features, and advantages of the enclosed embodiments will be apparent from the following description.

[0030] The embodiments set forth below represent information to enable those skilled in the art to practice the embodiments and illustrate the best mode of practicing the embodiments. Upon reading the following description in light of the accompanying drawing figures, those skilled in the art will understand the concepts of the disclosure and will recognize applications of these concepts not particularly addressed herein. It should be understood that these concepts and applications fall within the scope of the disclosure.

[0031] Radio Node: As used herein, a “radio node” is either a radio access node or a wireless communication device.

[0032] Radio Access Node: As used herein, a “radio access node” or “radio network node” or “radio access network node” is any node in a Radio Access Network (RAN) of a cellular communications network that operates to wirelessly transmit and/or receive signals. Some examples of a radio access node include, but are not limited to, a base station (e.g., a New Radio (NR) base station (gNB) in a Third Generation Partnership Project (3GPP) Fifth Generation (5G) NR network or an enhanced or evolved Node B (eNB) in a 3GPP Long Term Evolution (LTE) network), a high-power or macro base station, a low-power base station (e.g., a micro base station, a pico base station, a home eNB, or the like), a relay node, a network node that implements part of the functionality of a base station (e.g., a network node that implements a gNB Central Unit (gNB-CU) or a network node that implements a gNB Distributed Unit (gNB- DU)) or a network node that implements part of the functionality of some other type of radio access node.

[0033] Core Network Node: As used herein, a “core network node” is any type of node in a core network or any node that implements a core network function. Some examples of a core network node include, e.g., a Mobility Management Entity (MME), a Packet Data Network Gateway (P-GW), a Service Capability Exposure Function (SCEF), a Home Subscriber Server (HSS), or the like. Some other examples of a core network node include a node implementing an Access and Mobility Management Function (AMF), a User Plane Function (UPF), a Session Management Function (SMF), an Authentication Server Function (AUSF), a Network Slice Selection Function (NSSF), a Network Exposure Function (NEF), a Network Function (NF) Repository Function (NRF), a Policy Control Function (PCF), a Unified Data Management (UDM), or the like.

[0034] Communication Device: As used herein, a “communication device” is any type of device that has access to an access network. Some examples of a communication device include, but are not limited to: mobile phone, smart phone, sensor device, meter, vehicle, household appliance, medical appliance, media player, camera, or any type of consumer electronic, for instance, but not limited to, a television, radio, lighting arrangement, tablet computer, laptop, or Personal Computer (PC). The communication device may be a portable, hand-held, computer- comprised, or vehicle-mounted mobile device, enabled to communicate voice and/or data via a wireless or wireline connection.

[0035] Wireless Communication Device: One type of communication device is a wireless communication device, which may be any type of wireless device that has access to (i.e., is served by) a wireless network (e.g., a cellular network). Some examples of a wireless communication device include, but are not limited to: a User Equipment device (UE) in a 3GPP network, a Machine Type Communication (MTC) device, and an Internet of Things (loT) device. Such wireless communication devices may be, or may be integrated into, a mobile phone, smart phone, sensor device, meter, vehicle, household appliance, medical appliance, media player, camera, or any type of consumer electronic, for instance, but not limited to, a television, radio, lighting arrangement, tablet computer, laptop, or PC. The wireless communication device may be a portable, hand-held, computer-comprised, or vehicle-mounted mobile device, enabled to communicate voice and/or data via a wireless connection. [0036] Network Node: As used herein, a “network node” is any node that is either part of the RAN or the core network of a cellular communications network/system.

[0037] Note that the description given herein focuses on a 3GPP cellular communications system and, as such, 3GPP terminology or terminology similar to 3GPP terminology is oftentimes used. However, the concepts disclosed herein are not limited to a 3GPP system. [0038] Note that, in the description herein, reference may be made to the term “cell”; however, particularly with respect to 5G NR concepts, beams may be used instead of cells and, as such, it is important to note that the concepts described herein are equally applicable to both cells and beams.

1 Problems with Existing Solutions

1.1 First Problems with Existing Solutions

[0039] There currently exist certain challenge(s) with respect to Providing Access to Localized Service (PALS). A UE needs to be provided with localized service information. The localized service information mainly contains the mapping between localized service and hosting networks. It also contains a location validity condition to indicate to the UE where the localized service is available and/or where a hosting network is available. Then, the UE can use this location validity condition to determine whether to start to scan the hosting network.

[0040] The location validity condition usually is assumed to be geographical location (longitude, latitude), as the localized service information can be originated from different sources, e.g., application server or a 3GPP 5G System (5GS) network (home network, serving network, etc.). This requires the UE to know its own geographical location (e.g., its own Global Positioning System (GPS) location).

[0041] In some cases, this may not be necessary (i.e., requiring the UE to know its own geographical location (e.g., via an active GPS) or requiring the UE to use a location service to obtain its geographical location may not be necessary), as the source of the localized service information can be from a serving network which has a relationship with the hosting network (e.g., a business relationship between respective operators of the serving and hosting networks). [0042] In theory, the serving network can also use a System Information Block (SIB) enhancement to trigger a UE to scan for a hosting network, e.g., when the UE enters the proper location.

1.2 Second Problems with Existing Solutions

[0043] There currently exist further certain challenge(s) with respect to PALS. [0044] Problem A: In the current PLMN selection procedure specified in 3GPP TS 23.122, the UE needs to consider input from different procedures, such as the "Operator Controlled PLMN Selector with Access Technology" list from the Control Plane Solution for Steering of Roaming (CP-SOR) procedure and "CAG information list" from the UE Configuration Update procedure (or other Non-Access Stratum (NAS) procedures, e.g. registration procedure). The details for "CAG information list" are provided in 3GPP TS 24.501 (see, e.g., VI 8.0.1) clause 9.11.3.18A, as shown in the following excerpt from 3GPP TS 24.501:

***** START EXCERPT FROM 3GPP TS 24.501 *****

9.11.3.18A CAG information list

The purpose of the CAG information list information element is to provide "CAG information list" or to delete the "CAG information list" at the UE.

The CAG information list information element is coded as shown in figures 9.11.3.18A.1 and 9.11.3.18A.2 and table 9.11.3.18A.1.

The CAG information list is a type 6 information element, with a minimum length of 3 octets.

[REPRODUCED HEREIN AS FIGURE 14]

Figure 9.11.3.18A.1 : CAG information list information element

[REPRODUCED HEREIN AS FIGURE 15]

Figure 9.11.3.18A.2: Entry n

[REPRODUCED HEREIN AS FIGURE 16]

Table 9.11.3.18A.1 : CAG information list information element

***** _END EXCERPT FROM 3GPP TS 24.501 *****

[0045] If in the visited country where both a first Visited PLMN (VPLMN), denoted here as “VPLMN-1”, and a second VPLMN, denoted here as “VPLMN-2”, coverage exists at the same area, the VPLMN-1 has only a Closed Access Group (CAG) cell with CAG ID 100, then due to a certain use case trigger, the Home PLMN (HPLMN) would like to raise VPLMN-1 as the highest prioritized VPLMN via the CP-SOR procedure. After the CP-SoR procedure, the UE can trigger network selection, but it will not select VPLMN-1 if the UE has not been updated with the allowed CAG list of VPLMN-1. The allowed CAG list of VPLMN-1 is part of the "CAG information list" mentioned above.

[0046] Another problem is that if the UE is registered in VPLMN-2, the current 3GPP specification does not allow the UE to update CAG related information of another VPLMN (VPLMN-1 in this example). Rather, the UE is only allowed to update CAG related information of the current registered VPLMN when roaming, as to prevent the registered VPLMN from intentionally manipulating the CAG information list. So, if the UE is registered in VPLMN-2 and HPLMN would like to steer UE to select VPLMN-1, then it requires:

• either VPLMN-1 has non-CAG cell deployed at the UE's location; or

• VPLMN-1 allows end user/UE to manually select the CAG cell, even if UE has no valid CAG information; or

• HPLMN makes sure UE has all the up-to-date information of VPLMNs before UE is roaming

[0047] All options above are not ideal. To have a non-CAG cell means that any UE can make use of the VPLMN- l's radio resource. To allow manual selection reduces the purpose of the CAG function, as CAG is meant to perform access control and restrict unauthorized UEs from accessing the radio resource. Also, CAG related information can be dynamic and use case dependent and, as such, it is not possible to have such information always in place before the UE is roaming.

[0048] Problem B: The current CP-SoR procedure specified in 3GPP TS 23.122 Annex C is only initiated from the network side. The priority list "Operator Controlled PLMN Selector with Access Technology" delivered by the CP-SoR procedure reflects a business relationship between home network and visited network and also depends on the home network operator's policy.

[0049] In the localized service use case, a UE may want to select a specific visited network, as only that specific visited network has the capability for a certain localized service(s). But the UE may not know if the UE’s home network credential can be used to access this visited network or not.

[0050] For example, if the visited network is an SNPN and the home network is a PLMN, there might be a business relationship and interfaces between the home network and the visited network. Then, the UE can use its home network subscription/credential to perform the network selection to the visited network. But if there is no business relationship between the two network operators, then the UE may either not be able to select the visited network due to it is not on the priority list for network selection or the UE has to make an attempt to register with the visited network and get a failure.

2 Description of Solutions

[0051] Figure 2 illustrates one example of a cellular communications system 200 in which embodiments of the present disclosure may be implemented. In the embodiments described herein, the cellular communications system 200 is 5GS including a Next Generation RAN (NG- RAN) and a 5G Core (5GC); however, the present disclosure is not limited thereto. In this example, the RAN includes base stations 202-1 and 202-2, which in the 5GS include NR base stations (gNBs) and optionally next generation eNBs (ng-eNBs) (e.g., LTE RAN nodes connected to the 5GC), controlling corresponding (macro) cells 204-1 and 204-2. The base stations 202-1 and 202-2 are generally referred to herein collectively as base stations 202 and individually as base station 202. Likewise, the (macro) cells 204-1 and 204-2 are generally referred to herein collectively as (macro) cells 204 and individually as (macro) cell 204. The RAN may also include a number of low power nodes 206-1 through 206-4 controlling corresponding small cells 208-1 through 208-4. The low power nodes 206-1 through 206-4 can be small base stations (such as pico or femto base stations) or RRHs, or the like. Notably, while not illustrated, one or more of the small cells 208-1 through 208-4 may alternatively be provided by the base stations 202. The low power nodes 206-1 through 206-4 are generally referred to herein collectively as low power nodes 206 and individually as low power node 206. Likewise, the small cells 208-1 through 208-4 are generally referred to herein collectively as small cells 208 and individually as small cell 208. The cellular communications system 200 also includes a core network 210, which in the 5G System (5GS) is referred to as the 5GC. The base stations 202 (and optionally the low power nodes 206) are connected to the core network 210.

[0052] The base stations 202 and the low power nodes 206 provide service to wireless communication devices 212-1 through 212-5 in the corresponding cells 204 and 208. The wireless communication devices 212-1 through 212-5 are generally referred to herein collectively as wireless communication devices 212 and individually as wireless communication device 212. In the following description, the wireless communication devices 212 are oftentimes UEs, but the present disclosure is not limited thereto.

[0053] Figure 3 illustrates a wireless communication system represented as a 5G network architecture composed of core Network Functions (NFs), where interaction between any two NFs is represented by a point-to-point reference point/interface. Figure 3 can be viewed as one particular implementation of the system 200 of Figure 2. [0054] Seen from the access side the 5G network architecture shown in Figure 3 comprises a plurality of UEs 212 connected to either a RAN 202 or an Access Network (AN) as well as an AMF 300. Typically, the R(AN) 202 comprises base stations, e.g. such as eNBs or gNBs or similar. Seen from the core network side, the 5GC NFs shown in Figure 3 include a NSSF 302, an AUSF 304, a UDM 306, the AMF 300, a SMF 308, a PCF 310, and an Application Function (AF) 312.

[0055] Reference point representations of the 5G network architecture are used to develop detailed call flows in the normative standardization. The N 1 reference point is defined to carry signaling between the UE 212 and AMF 300. The reference points for connecting between the AN 202 and AMF 300 and between the AN 202 and UPF 314 are defined as N2 and N3, respectively. There is a reference point, Ni l, between the AMF 300 and SMF 308, which implies that the SMF 308 is at least partly controlled by the AMF 300. N4 is used by the SMF 308 and UPF 314 so that the UPF 314 can be set using the control signal generated by the SMF 308, and the UPF 314 can report its state to the SMF 308. N9 is the reference point for the connection between different UPFs 314, and N14 is the reference point connecting between different AMFs 300, respectively. N15 and N7 are defined since the PCF 310 applies policy to the AMF 300 and SMF 308, respectively. N12 is required for the AMF 300 to perform authentication of the UE 212. N8 and N10 are defined because the subscription data of the UE 212 is required for the AMF 300 and SMF 308.

[0056] The 5GC network aims at separating UP and CP. The UP carries user traffic while the CP carries signaling in the network. In Figure 3, the UPF 314 is in the UP and all other NFs, i.e., the AMF 300, SMF 308, PCF 310, AF 312, NSSF 302, AUSF 304, and UDM 306, are in the CP. Separating the UP and CP guarantees each plane resource to be scaled independently. It also allows UPFs to be deployed separately from CP functions in a distributed fashion. In this architecture, UPFs may be deployed very close to UEs to shorten the Round Trip Time (RTT) between UEs and data network for some applications requiring low latency.

[0057] The core 5G network architecture is composed of modularized functions. For example, the AMF 300 and SMF 308 are independent functions in the CP. Separated AMF 300 and SMF 308 allow independent evolution and scaling. Other CP functions like the PCF 310 and AUSF 304 can be separated as shown in Figure 3. Modularized function design enables the 5GC network to support various services flexibly.

[0058] Each NF interacts with another NF directly. It is possible to use intermediate functions to route messages from one NF to another NF. In the CP, a set of interactions between two NFs is defined as service so that its reuse is possible. This service enables support for modularity. The UP supports interactions such as forwarding operations between different UPFs. [0059] Figure 4 illustrates a 5G network architecture using service-based interfaces between the NFs in the CP, instead of the point-to-point reference points/interfaces used in the 5G network architecture of Figure 3. However, the NFs described above with reference to Figure 3 correspond to the NFs shown in Figure 4. The service(s) etc. that a NF provides to other authorized NFs can be exposed to the authorized NFs through the service-based interface. In Figure 4 the service based interfaces are indicated by the letter “N” followed by the name of the NF, e.g. Namf for the service based interface of the AMF 300 and Nsmf for the service based interface of the SMF 308, etc. The NEF 400 and the NRF 402 in Figure 4 are not shown in Figure 3 discussed above. However, it should be clarified that all NFs depicted in Figure 3 can interact with the NEF 400 and the NRF 402 of Figure 4 as necessary, though not explicitly indicated in Figure 3.

[0060] Some properties of the NFs shown in Figures 3 and 4 may be described in the following manner. The AMF 300 provides UE-based authentication, authorization, mobility management, etc. A UE 212 even using multiple access technologies is basically connected to a single AMF 300 because the AMF 300 is independent of the access technologies. The SMF 308 is responsible for session management and allocates Internet Protocol (IP) addresses to UEs. It also selects and controls the UPF 314 for data transfer. If a UE 212 has multiple sessions, different SMFs 308 may be allocated to each session to manage them individually and possibly provide different functionalities per session. The AF 312 provides information on the packet flow to the PCF 310 responsible for policy control in order to support QoS. Based on the information, the PCF 310 determines policies about mobility and session management to make the AMF 300 and SMF 308 operate properly. The AUSF 304 supports authentication function for UEs or similar and thus stores data for authentication of UEs or similar while the UDM 306 stores subscription data of the UE 212. The Data Network (DN), not part of the 5GC network, provides Internet access or operator services and similar.

[0061] An NF may be implemented either as a network element on a dedicated hardware, as a software instance running on a dedicated hardware, or as a virtualized function instantiated on an appropriate platform, e.g., a cloud infrastructure.

2.1 Solution Description to First Problems with Existing Solutions — Serving Network Based Validity Condition for Localized Service

[0062] Certain aspects of the present disclosure and their embodiments may provide solutions to the aforementioned or other challenges described above in Section 1.1 (i.e., the “First Problems”). Embodiments of systems and methods are disclosed herein that provide a location validity condition as part of localized service information provided by a serving network where the location validity condition uses serving network related location identity (ID) (e.g., Tracking Area Code or Cell ID), instead of geographical location such as, e.g., GPS coordinates.

[0063] In one embodiment, once a UE in the serving network enters an area covered by the serving network related location ID, the UE initiates a scan for a hosting network.

[0064] In one embodiment, the serving network provides the location validity condition of Localized Services using the serving network related location ID (e.g., Tracking Area Code or Cell ID).

[0065] In one embodiment, a UE reads broadcast information of the serving network and checks if the UE is in or enters an area(s) that satisfies the validity condition.

[0066] If the validity condition is satisfied, then the UE initiates a scan for a hosting network(s).

[0067] Certain embodiments may provide one or more of the following technical advantage(s):

• Embodiments of the present disclosure do not require the UE to activate, e.g., a GPS receiver on the UE or require the UE to use location services in 3GPP TS 23.273.

• Embodiments of the present disclosure avoid System Information Block (SIB) broadcast extension in the serving network, as SIB is considered as scarce resource.

• Embodiments of the present disclosure can also avoid SIB extensions by a Hosting Network, if it can be assumed that all serving networks in the area would provide the information.

[0068] The deployment of a hosting network is usually assumed in a limited area, and a serving network is assumed as a wide area network, as shown in Figure 5. In the example of Figure 5, the serving network is a public network, and the hosting network is a SNPN. However, this is only an example.

[0069] In one embodiment, the serving network (e.g., a network node(s) of the serving network) has the knowledge of the deployment of the hosting network, such as in which tracking area(s) of the serving network the hosting network is deployed, or in which Cell IDs of the serving network the hosting network is deployed.

[0070] Figure 6 illustrates a procedure in accordance with one embodiment of the first solution. This procedure involves a UE 600, serving network RAN node 602, a serving network 5GC node 604, and a hosting network node 606. The steps of the procedure are as follows. [0071] Step 1: The UE 600 is registered in the serving network. The serving network can be the home network of the UE 600 (e.g., HPLMN, subscribed SNPN, or the like), or it can be a different network than the home network of the UE 600, but where the UE 600 uses home network credential to access the serving network.

[0072] Step 2: The UE 600 is provided with localized service information including a location validity condition that indicates where a localized service(s) is available and/or where the hosting network (of the localized service(s)) is available. The location validity condition in the localized service information uses a serving network related location ID(s) (e.g., Tracking Area Code(s) (TAC(s)) or Cell ID(s)), rather than a geographical location (e.g., latitude and longitude coordinates such as, e.g., GPS coordinates).

[0073] Step 3: The UE 600 is moving and enters an area where the hosting network is deployed.

[0074] Step 4: The UE 600 reads broadcast information (e.g., SIB broadcast) of the serving network, and checks whether the validity condition is satisfied (e.g., checks whether the TAC or Cell ID broadcasted by the serving network RAN node 602 matches the location validity condition received in step 2). If the location validity condition is satisfied, the UE 600 initiates a scan of the hosting network(s).

[0075] Step 5: The UE 600 detects the hosting network via the scan and initiates a network selection procedure and registration procedure with the detected hosting network. Alternatively, before the UE 600 does selection of the hosting network, the UE 600 informs the user and/or application layer that the hosting network or Localized Services (or appropriate information of the localized services supported as received by serving network or earlier) are available as to allow the user and/or application to trigger a “manual selection” of the hosting network.

2.2 Solution Description to Second Problems with Existing Solutions —SoR Procedure for Localized Service

[0076] Certain aspects of the present disclosure and their embodiments may provide solutions to the aforementioned or other challenges described above in Section 1.2 (i.e., the “Second Problems” including “Problem A” and “Problem B”).

[0077] For Problem A, in one embodiment, to have a network selection behavior in a controlled way, HPLMN sends the UE the "CAG information list" together with the SOR Information (e.g., "Operator Controlled PLMN Selector with Access Technology" list) within the CP-SoR procedure. See 3GPP TS 24.501 clause 9.11.3.51 and 3GPP TS 23.122 Annex C.l.l for details of SOR Information, both of which are included in the following excepts: ***** START EXCERPT FROM 3GPP TS 24.501 *****

9.11 .3.51 SOR transparent container

The purpose of the SOR transparent container information element in the REGISTRATION ACCEPT message is to provide the list of preferred PLMN/access technology combinations (or HPLMN indication that 'no change of the "Operator Controlled PLMN Selector with Access Technology" list stored in the UE is needed and thus no list of preferred PLMN/access technology combinations is provided'), or a secured packet (see 3GPP TS 23.122 [5] annex C) and optional indication of an acknowledgement request, SOR-CMCI, request the storage of the received SOR-CMCI in the ME, and SOR-SNPN-SI (or subscribed SNPN or HPLMN indication that 'no change of the SOR- SNPN-SI stored in the UE is needed and thus no SOR-SNPN-SI is provided'). The purpose of the SOR transparent container information element in the REGISTRATION COMPLETE message is to indicate the UE acknowledgement of successful reception of the SOR transparent container IE in the REGISTRATION ACCEPT message as well as to indicate the ME support of SOR-CMCI and the ME support of SOR-SNPN-SI.

NOTE: When used in NAS transport procedure, the contents of the SOR transparent container information element in the Payload container IE of the DL NAS TRANSPORT message are used to provide the list of preferred PLMN/access technology combinations and optional indication of an acknowledgement request, SOR-CMCI, request the storage of the received SOR-CMCI in the ME, and SOR-SNPN-SI. The contents of the SOR transparent container information element in the Payload container IE of the UL NAS TRANSPORT message are used to indicate the UE acknowledgement of successful reception of the SOR transparent container IE in the DL NAS TRANSPORT message as well as to indicate the ME support of SOR-CMCI and the ME support of SOR-SNPN-SI.

The SOR transparent container information element is coded as shown in figure 9.11.3.51.1, figure 9.11.3.51.2, figure 9.11.3.51.3, figure 9.11.3.51.4, figure 9.11.3.51.5, figure 9.11.3.51.6, figure 9.11.3.51.7, figure 9.11.3.51.8, figure 9.11.3.51.9, figure 9.11.3.51.10, figure 9.11.3.51.11, figure 9.11.3.51.12, figure 9.11.3.51.13, table 9.11.3.51.1, table 9.11.3.51.2, table 9.11.3.51.3, table 9.11.3.51.4, table 9.11.3.51.5 and table 9.11.3.51.6.

The SOR transparent container is a type 6 information element with a minimum length of 20 octets.

[REPRODUCED HEREIN AS FIGURE 17]

Figure 9.11.3.51.1 : SOR transparent container information element for list type with value "0" and SOR data type with value "0"

[REPRODUCED HEREIN AS FIGURE 18]

Figure 9.11.3.51.2: SOR transparent container information element for list type with value "1 ", SOR data type with value "0", and additional parameters with value "0"

[REPRODUCED HEREIN AS FIGURE 19]

Figure 9.11.3.51.2A: SOR transparent container information element for list type with value "1", SOR data type with value "0", additional parameters with value "1" [REPRODUCED HEREIN AS FIGURE 20]

Figure 9.11.3.51 .3: PLMN ID and access technology list (m=22+5*n)

[REPRODUCED HEREIN AS FIGURE 21]

Figure 9.11.3.51.4: SOR transparent container information element for SOR data type with value 1' II

[REPRODUCED HEREIN AS FIGURE 22]

Figure 9.11.3.51.5: SOR header for SOR data type with value "0"

[REPRODUCED HEREIN AS FIGURE 23]

Figure 9.11.3.51.6: SOR header for SOR data type with value "1"

[REPRODUCED HEREIN AS FIGURES 24A-24C]

Table 9.11.3.51.1 : SOR transparent container information element

[REPRODUCED HEREIN AS FIGURE 25]

Figure 9.11.3.51 .7: SOR-CMCI

[REPRODUCED HEREIN AS FIGURE 26]

Table 9.11.3.51 .2: SOR-CMCI

[REPRODUCED HEREIN AS FIGURE 27]

Figure 9.11 .3.51.8: SOR-CMCI rule [REPRODUCED HEREIN AS FIGURES 28A and 28B]

Table 9.11.3.51.3: SOR-CMCI rule

[REPRODUCED HEREIN AS FIGURE 29] Figure 9.11.3.51 .9: SOR-SNPN-SI

[REPRODUCED HEREIN AS FIGURE 30] Table 9.11.3.51 .4: SOR-SNPN-SI

[REPRODUCED HEREIN AS FIGURE 31]

Figure 9.11.3.51.10: CH controlled prioritized list of preferred SNPNs

[REPRODUCED HEREIN AS FIGURE 32] Figure 9.11 .3.51.11 : SNPN identity

[REPRODUCED HEREIN AS FIGURE 33]

Table 9.11.3.51.5: CH controlled prioritized list of preferred SNPNs

[REPRODUCED HEREIN AS FIGURE 34]

Figure 9.11.3.51.12: CH controlled prioritized list of GINs

[REPRODUCED HEREIN AS FIGURE 35]

Figure 9.11.3.51.13: GIN [REPRODUCED HEREIN AS FIGURE 36]

Table 9.11.3.51.6: CH controlled prioritized list of GINs

***** _END EXCERPT FROM 3GPP TS 24.501 *****

***** START EXCERPT FROM 3GPP TS 23.122 *****

C.1 .1 Steering of roaming over the control plane in a PLMN

The purpose of the control plane solution for steering of roaming in 5GS procedure in a PLMN is to allow the HPLMN to update one or more of the following via NAS signalling: a) the "Operator Controlled PLMN Selector with Access Technology" list in the LIE by providing the HPLMN protected list of preferred PLMN/access technology combinations or a secured packet; b) the SOR-CMCI; and c) the SOR-SNPN-SI associated with the selected PLMN subscription in the ME.

If the selected PLMN is a VPLMN, the HPLMN can provide the steering of roaming information to the UE using the control plane mechanism during and after registration. If the selected PLMN is the HPLMN, the HPLMN can provide the steering of roaming information to the UE using the control plane mechanism after registration only. The HPLMN updates the "Operator Controlled PLMN Selector with Access Technology" based on the operator policies, which can be based on the registered VPLMN, the location of the UE, etc.

The HPLMN can configure their subscribed UE's USIM to indicate that the UE is expected to receive the steering of roaming information due to initial registration in 5GS in a VPLMN. At the same time the HPLMN will mark the UE is expected to receive the steering of roaming information due to initial registration in 5GS in a VPLMN, in the subscription information in the UDM. In this case, it is mandatory for the HPLMN to provide the steering of roaming information to the UE during initial registration in a VPLMN. Otherwise if such configuration is not provided in the USIM, it is optional for the HPLMN to provide the steering of roaming information to the UE during initial registration (based on operator policy). The HPLMN can provide the steering of roaming information to the UE during the registration procedure for mobility and periodic registration update (see 3GPP TS 24.501 [64]) and initial registration procedure for emergency services. In addition, the HPLMN can request the UE to provide an acknowledgement of successful reception of the steering of roaming information.

NOTE 1: In annex C of this specification, the User Data Repository (UDR) is considered as part of the UDM.

As the HPLMN needs to consider certain criteria including the number of customers distributed through multiple VPLMNs in the same country or region, the list of the preferred PLMN/access technology combinations is not necessarily the same at all times and for all users. The list of the preferred PLMN/access technology combinations needs to be dynamically generated, e.g. generated on demand, by a dedicated steering of roaming application function (SOR-AF) providing operator specific data analytics solutions.

NOTE 2: The functional description of this dedicated application function (SOR-AF) is out of scope of 3GPP.

The steering of roaming connected mode control information (SOR-CMCI) enables the HPLMN to control the timing of a UE in 5GS connected mode to move to idle mode to perform the steering of roaming. If the UE selects a cell of any access technology other than NG-RAN, the SOR procedure is terminated (see clause C.4.2). The UE shall support the SOR-CMCI. The support and use of SOR-CMCI by the HPLMN is based on the HPLMN's operator policy.

The following requirements are applicable for the SOR-CMCI:

- The HPLMN may configure SOR-CMCI in the UE and may also send SOR-CMCI over N 1 NAS signalling. The SOR-CMCI received over N1 NAS signalling has precedence over the SOR-CMCI configured in the UE. NOTE 3: Based on HPLMN policy, while setting the SOR-CMCI the HPLMN can take into consideration the user preference for the service! s) not to be interrupted due to SOR (e.g. MMTEL voice call, MMTEL video call, HPLMN defined services, among others). The user can communicate its preference for the service(s) not to be interrupted due to SOR to the HPLMN utilizing non-standard operator-specific mechanisms, e.g. web-based.

- The UE shall indicate ME's support for SOR-CMCI to the HPLMN.

NOTE 4: The HPLMN has the knowledge of the USIM's capabilities in supporting SOR-CMCI.

- While performing SOR, the UE shall consider the list of preferred PLMN/access technology combinations or secured packet received in the SOR information together with the available SOR-CMCI.

- The HPLMN may provision the SOR-CMCI in the UE over N1 NAS signalling. The UE shall store the configured SOR-CMCI in the non-volatile memory of the ME or in the USIM as described in clause C.4.

The following requirements are applicable for the SOR-SNPN-SI:

- If the UE supports access to an SNPN using credentials from a credentials holder, the UE shall indicate ME's support for SOR-SNPN-SI to the HPLMN.

In order to support various deployment scenarios, the UDM may support:

- obtaining a list of preferred PLMN/access technology combinations, and SOR-CMCI, if any (if supported by the UDM and required by the HPLMN), or a secured packet which is or becomes available in the UDM (i.e. retrieved from the UDR);

NOTE 5: A secured packet can be made available at the UDR via implementation specific means. In this case the implementation specific means are required to ensure that the secured packet satisfies the "Replay detection and Sequence Integrity counter" (see ETSI TS 102225 [73]) every time it is sent out from the HPLMN to the UE.

- obtaining a list of preferred PLMN/access technology combinations and SOR-CMCI, if any (if supported by the UDM and required by the HPLMN), or a secured packet from the SOR-AF; or

- both of the above.

The HPLMN policy for the SOR-AF invocation can be present in the UDM only if the UDM supports obtaining a list of preferred PLMN/access technology combinations and SOR-CMCI, if any, or a secured packet from the SOR- AF.

The UDM discards any list of preferred PLMN/access technology combinations, SOR-CMCI, if any, or any secured packet obtained from the SOR-AF or which is or becomes available in the UDM (i.e. retrieved from the UDR), either during registration (as specified in annex C.2) or after registration (as specified in annex C.3 and C.4.3), when the UDM cannot successfully forward the SOR information to the AMF (e.g. in case the UDM receives the response from the SOR-AF with the list of preferred PLMN/access technology combinations, the SOR-CMCI, if any, or the secured packet after the expiration of the operator specific timer, or if there is no AMF registered for the UE).

The UE maintains a list of "PLMNs where registration was aborted due to SOR". If the UE receives steering of roaming information in the REGISTRATION ACCEPT or DL NAS TRANSPORT message and the security check to verify that the steering of roaming information is provided by HPLMN is successful, the UE shall remove the current selected PLMN from the list of "PLMNs where registration was aborted due to SOR". The UE shall delete the list of "PLMNs where registration was aborted due to SOR" when the MS is switched off, the USIM is removed or after a UE implementation dependent time.

If:

- the UE's USIM is configured to indicate that the UE shall expect to receive the steering of roaming information during initial registration procedure but did not receive it or security check on the steering of roaming information fails;

- the current chosen VPLMN is not contained in the list of "PLMNs where registration was aborted due to SOR"; the current chosen VPLMN is not part of "User Controlled PLMN Selector with Access Technology" list; and the UE is not in manual mode of operation; then the UE will perform PLMN selection with the current VPLMN considered as lowest priority.

It is mandatory for the VPLMN to transparently forward to the UE the steering of roaming information received from HPLMN and to transparently forward to the HPLMN the acknowledgement of successful reception of the steering of roaming information received from UE, both while the UE is trying to register onto the VPLMN as described in clause C.2, and after the UE has registered onto the VPLMN as described in clause C.3 and C.4.3.

If the last received steering of roaming information contains the list of preferred PLMN/access technology combinations then the ME shall not delete the "Operator Controlled PLMN Selector with Access Technology" list stored in the ME when the UE is switched off.

The "Operator Controlled PLMN Selector with Access Technology" list shall be stored in the ME together with the SUPI from the USIM. The ME shall delete the "Operator Controlled PLMN Selector with Access Technology" list stored in the ME when a new USIM is inserted.

The procedure in this annex for steering of UE in VPLMN can be initiated by the network while the UE is trying to register onto the VPLMN as described in clause C.2, or after the UE has registered onto the HPLMN or the VPLMN as described in clause C.3, C.7 and C.4.3.

***** _END EXCERPT FROM 3GPP TS 23.122 *****

[0078] For Problem A, in one embodiment, SoR Information provisioning and CAG Information list provisioning procedure are combined into one procedure. In one embodiment, the Unified Data Management (UDM) is provisioned by external Application Function (AF) with both data at the same time.

[0079] For Problem B, in one embodiment, to avoid the failure from happening, the CP-SoR procedure can be initiated from the UE side to check with the home network, e.g. whether business relationship exists between the desired visited network. In one embodiment, the CP-SoR info content is extended to indicate the purpose of the priority list in the SoR info.

[0080] For Problem B, in one embodiment, the UE is enabled to initiate the CP-SoR procedure, with additional filtering information (e.g., localized service identifier, hosting network identifier) to check with home network whether business relationship exists and how to prioritize.

[0081] Certain embodiments may provide one or more of the following technical advantage(s).

• For Problem A, UE will be provided with all the necessary data to perform desired network selection, without relying on the sequence of different procedures, and can achieve automatic network selection. Another benefit is that when UE is roaming in VPEMN, the CAG related information of any VPEMN can be updated regardless which VPEMN the UE is registered, because "CAG information list" can be sent within the "SoR Information" container that is securely protected/encrypted between UE and HPLMN. • For Problem B, UE is provided with information to know if home network credential can be used to access a visited network (e.g., a hosting network in case of PALS use case). Then depending on this knowledge, UE will be able to continue either directly use home network credential to select the visited network, or trigger other procedures to obtain new credentials for access hosting network.

[0082] Now, a more detailed description of some example embodiments will be described.

[0083] Due to use case trigger (localized service), there might be update of "list of preferred

PLMN/access technology combinations " and the "Allowed CAG list" at the same time.

[0084] Figure 7 illustrates a procedure in accordance with one example embodiment of the second solution(s) of the present disclosure. This procedure involves a UE 700, an AMF 702, an HPLMN UDM 704, and optionally an SOR AF 706. The steps of the procedure are as follows. Note that optional steps are represented in Figure 7 by dashed lines.

[0085] Step 1: In step 1, an external AF (e.g., the SoR-AF 706 in Figure 7) provides "SOR information" and additionally "CAG information list" together to the UDM 704. In one embodiment, the SoR information includes any, all, or any combination of information or parameters included in the existing SoR information defined in 3GPP specifications (see excerpts above). In one embodiment, the CAG information list includes any, all, or any combination of information or parameters included in the existing CAG information list defined in 3GPP specifications (see excerpt above). In one embodiment, the "CAG information list" can be in a separated Information Element (IE) (i.e., separate IE from the SOR information), or within the "SOR information" container which is securely protected/encrypted between the HPLMN and the UE 700. The information enables CAG information to be provided per network ID in the SOR information.

[0086] Step 2: In step 2, the UDM 704 sends the "SoR information" and additionally the "CAG information list" within the Access and Mobility subscription data to the AMF 702. [0087] Step 3: In step 3, the AMF 702 forwards, to the UE 700, the "SoR information" container transparently, and additionally the "CAG information list" in a downlink (DL) NAS message.

[0088] If the "CAG information list" is not within the "SoR Information" container in step 1, the NG-AP message carrying the "DL NAS message" will also include the new CAG info (e.g., the CAG information list) as part of the mobility restriction list to NG-RAN.

[0089] Steps 4-6: The UE 700 may perform a SoR information security check and may respond to the AMF 702 with an UL NAS transport message. The AMF 702 may then send an information request to the UDM 704, and the UDM 704 may send an SoR information request to the SoR AF 706. Note that UL NAS transport message may be sent by the UE 700 and the resulting info requests of steps 5 and 6 sent if, e.g., the information security check of step 4 fails. [0090] After the UE 700 receives the "SOR information" container and "CAG information list", the UE 700 performs network selection using input from both the SoR information and the "CAG information list" (not shown). The UE Y700 also accesses the network as if the UE 700 has been configured with CAG information being valid for the selected network. The AMF 702 in the selected network will subsequently get the CAG information as part of subscription data from the UDM 704, and provision the UE 700 with CAG information valid for the network as per existing procedures.

[0091] Figure 8 illustrates a procedure in accordance with another example embodiment of the second solution(s) of the present disclosure. This procedure involves a UE 800, an AMF 802 (of the VPLMN or HPLMN), an HPLMN UDM/AUSF 804, and optionally an SOR AF 806.

The steps of the procedure are as follows. Note that optional steps are represented in Figure 8 by dashed lines.

[0092] Step 0: The UE 800 is already registered via the AMF 802 in a VPLMN or in the HPLMN. This implies that the AMF 802 has already registered in the UDM 804, has obtained subscription data for the UE 800, and subscribed to subscription data updates including possible updates of SoR information.

[0093] Step 1: The UE 800 initiates the CP-SoR procedure by, e.g., including a "SoR request info" within a subsequent Registration Request. The "SoR request info" can include filtering functions, e.g.

• Localized service ID

• Hosting network ID

• UE current location

• Location of the localized service

[0094] Step 2: The AMF 802 updates the registration in the UDM 804 and forwards the "SoR request info" to the UDM 804.

[0095] Step 3: The UDM 804 checks the "SoR request info" from the UE 800, and decides to request the SOR-AF 806 to authorize the request by the UE 800 (step 3a and 3b). The UDM 804 does this even if the UE 800 is registered in the HPLMN.

[0096] The SoR-AF updates the “SoR information” for the UE 800 if needed according to SOR-AF decision (step 3c) and protects the SoR info via AUSF 804 (step 3d). The "SoR information" provided by the SOR-AF 806 is based on the filtering function in the "SoR request info". [0097] The response from the SoR-AF 806 includes priority list of preferred networks (PLMN or SNPN) for network selection, and a purpose of the priority list. The associated purpose can be:

• accessing general or a specific localized service.

Then, the UE 800 understands that, if it needs to access localized service, the UE 800 should use the priority list and perform network selection accordingly.

[0098] Step 4: The UDM 804 provides the "SoR information" to the UE 800 via the AMF 802 after protection via the AUSF 804.

[0099] The rest of the steps are as defined in the baseline. In Step 11, the UE 800 applies the network selection as authorized by the SoR AF 806.

3 Further Description

[0100] Figure 9 is a schematic block diagram of a network node 900 according to some embodiments of the present disclosure. Optional features are represented by dashed boxes. The network node 900 may be, for example, a RAN node (e.g., base station 202 or gNB), a network node that implements all or part of the functionality of a RAN node, or a core network node (e.g., a network node that implements a 5GC NF, an AMF, a UDM, an AUSF, a SOR AF, or the like), in accordance with any of the embodiments described herein. As illustrated, the network node 900 includes a control system 902 that includes one or more processors 904 (e.g., Central Processing Units (CPUs), Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs), and/or the like), memory 906, and a network interface 908. The one or more processors 904 are also referred to herein as processing circuitry. In addition, if the network node 900 is a RAN node (e.g., a base station 202, gNB, or network node that implements at least some of the functionality of the base station 202 or gNB), the network node 900 may include one or more radio units 910 that each includes one or more transmitters 912 and one or more receivers 914 coupled to one or more antennas 916. The radio units 910 may be referred to or be part of radio interface circuitry. In some embodiments, the radio unit(s) 910 is external to the control system 902 and connected to the control system 902 via, e.g., a wired connection (e.g., an optical cable). However, in some other embodiments, the radio unit(s) 910 and potentially the antenna(s) 916 are integrated together with the control system 902. The one or more processors 904 operate to provide one or more functions of the network node 900 as described herein (e.g., one or more functions of a RAN node, core network node, NF, AMF, UDM, AUSF, or SoR AF in accordance with any of the embodiments described herein). In some embodiments, the function(s) are implemented in software that is stored, e.g., in the memory 906 and executed by the one or more processors 904.

[0101] Figure 10 is a schematic block diagram that illustrates a virtualized embodiment of the network node 900 according to some embodiments of the present disclosure. Again, optional features are represented by dashed boxes. As used herein, a “virtualized” network node is an implementation of the network node 900 in which at least a portion of the functionality of the network node 900 is implemented as a virtual component(s) (e.g., via a virtual machine(s) executing on a physical processing node(s) in a network(s)). As illustrated, in this example, if the network node 900 is a radio access node, the network node 900 may include the control system 902 and/or the one or more radio units 910, as described above. The control system 902 may be connected to the radio unit(s) 910 via, for example, an optical cable or the like. The network node 900 includes one or more processing nodes 1000 coupled to or included as part of a network(s) 1002. If present, the control system 902 or the radio unit(s) are connected to the processing node(s) 1000 via the network 1002. Each processing node 1000 includes one or more processors 1004 (e.g., CPUs, ASICs, FPGAs, and/or the like), memory 1006, and a network interface 1008.

[0102] In this example, functions 1010 of the network node 900 described herein (.g., one or more functions of a RAN node, core network node, NF, AMF, UDM, AUSF, or SoR AF in accordance with any of the embodiments described herein) are implemented at the one or more processing nodes 1000 or distributed across the one or more processing nodes 1000 and the control system 902 and/or the radio unit(s) 910 in any desired manner. In some particular embodiments, some or all of the functions 1010 of the network node 900 described herein are implemented as virtual components executed by one or more virtual machines implemented in a virtual environment(s) hosted by the processing node(s) 1000. As will be appreciated by one of ordinary skill in the art, additional signaling or communication between the processing node(s) 1000 and the control system 902 is used in order to carry out at least some of the desired functions 1010. Notably, in some embodiments, the control system 902 may not be included, in which case the radio unit(s) 910 communicates directly with the processing node(s) 1000 via an appropriate network interface(s).

[0103] In some embodiments, a computer program including instructions which, when executed by at least one processor, causes the at least one processor to carry out the functionality of the network node 900 or a node (e.g., a processing node 1000) implementing one or more of the functions 1010 of the network node 900 in a virtual environment according to any of the embodiments described herein is provided. In some embodiments, a carrier comprising the aforementioned computer program product is provided. The carrier is one of an electronic signal, an optical signal, a radio signal, or a computer readable storage medium (e.g., a non-transitory computer readable medium such as memory).

[0104] Figure 11 is a schematic block diagram of the network node 900 according to some other embodiments of the present disclosure. The network node 900 includes one or more modules 1100, each of which is implemented in software. The module(s) 1100 provides the functionality of the network node 900 described herein. This discussion is equally applicable to the processing node 1000 of Figure 10 where the modules 1100 may be implemented at one of the processing nodes 1000 or distributed across multiple processing nodes 1000 and/or distributed across the processing node(s) 1000 and the control system 902.

[0105] Figure 12 is a schematic block diagram of a wireless communication device 212 (e.g., a UE) according to some embodiments of the present disclosure. As illustrated, the wireless communication device 212 includes one or more processors 1202 (e.g., CPUs, ASICs, FPGAs, and/or the like), memory 1204, and one or more transceivers 1206 each including one or more transmitters 1208 and one or more receivers 1210 coupled to one or more antennas 1212. The transceiver(s) 1206 includes radio-front end circuitry connected to the antenna(s) 1212 that is configured to condition signals communicated between the antenna(s) 1212 and the processor(s) 1202, as will be appreciated by on of ordinary skill in the art. The processors 1202 are also referred to herein as processing circuitry. The transceivers 1206 are also referred to herein as radio circuitry. In some embodiments, the functionality of the wireless communication device 212 (or UE) described above may be fully or partially implemented in software that is, e.g., stored in the memory 1204 and executed by the processor(s) 1202. Note that the wireless communication device 212 may include additional components not illustrated in Figure 12 such as, e.g., one or more user interface components (e.g., an input/output interface including a display, buttons, a touch screen, a microphone, a speaker(s), and/or the like and/or any other components for allowing input of information into the wireless communication device 212 and/or allowing output of information from the wireless communication device 212), a power supply (e.g., a battery and associated power circuitry), etc.

[0106] In some embodiments, a computer program including instructions which, when executed by at least one processor, causes the at least one processor to carry out the functionality of the wireless communication device 212 according to any of the embodiments described herein is provided. In some embodiments, a carrier comprising the aforementioned computer program product is provided. The carrier is one of an electronic signal, an optical signal, a radio signal, or a computer readable storage medium (e.g., a non-transitory computer readable medium such as memory).

[0107] Figure 13 is a schematic block diagram of the wireless communication device 212 according to some other embodiments of the present disclosure. The wireless communication device 212 includes one or more modules 1300, each of which is implemented in software. The module(s) 1300 provides the functionality of the wireless communication device 212 (or UE) described herein.

[0108] Any appropriate steps, methods, features, functions, or benefits disclosed herein may be performed through one or more functional units or modules of one or more virtual apparatuses. Each virtual apparatus may comprise a number of these functional units. These functional units may be implemented via processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include Digital Signal Processor (DSPs), special-purpose digital logic, and the like. The processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as Read Only Memory (ROM), Random Access Memory (RAM), cache memory, flash memory devices, optical storage devices, etc. Program code stored in memory includes program instructions for executing one or more telecommunications and/or data communications protocols as well as instructions for carrying out one or more of the techniques described herein. In some implementations, the processing circuitry may be used to cause the respective functional unit to perform corresponding functions according to one or more embodiments of the present disclosure.

[0109] While processes in the figures may show a particular order of operations performed by certain embodiments of the present disclosure, it should be understood that such order is exemplary (e.g., alternative embodiments may perform the operations in a different order, combine certain operations, overlap certain operations, etc.).

[0110] Some example embodiments of the present disclosure are as follows:

[0111] Embodiment 1: A method performed by a User Equipment, UE, (600), the method comprising: registering (Fig. 6, step 1) with a serving network; receiving (Fig. 6, step 2) localized service information from the serving network, the localized service information comprising a validity area condition that indicates, using one or more serving network related identifiers, one or more areas in which one or more localized services of a hosting service are available and/or in which the hosting network is available; determining (Fig. 6, step 4) that the validity area condition is satisfied; and, responsive to determining (Fig. 6, step 4) that the validity area condition is satisfied, initiating (Fig. 6, step 4) a scan for the hosting network. [0112] Embodiment 2: The method of embodiment 1 wherein the one or more serving network related identifiers comprise one or more tracking area codes of the serving network, one or more cell identities of the serving network, or both one or more tracking area codes and one or more cell identities of the serving network.

[0113] Embodiment 3: The method of embodiment 2 wherein determining (Fig. 6, step 3) that the validity area condition is satisfied comprises: receiving (Fig. 6, step 4) broadcast information from the serving network, the broadcast information comprising a tracking area code, a cell identity, or both a tracking area code and a cell identity; and determining (Fig. 6, step 4) that the tracking area code, cell identity, both the tracking area code and cell identity comprised in the broadcast information satisfies the validity area condition.

[0114] Embodiment 4: A UE adapted to perform the method of any of embodiments 1 to 3.

[0115] Embodiment 5: A method performed by a network node (602) of a serving network of a User Equipment, UE, (600), the method comprising: providing (Fig. 6, step 2) localized service information to the UE (600), the localized service information comprising a validity area condition that indicates, using one or more serving network related identifiers, one or more areas in which one or more localized services of a hosting service are available and/or in which the hosting network is available.

[0116] Embodiment 6: The method of embodiment 5 wherein the one or more serving network related identifiers comprise one or more tracking area codes of the serving network, one or more cell identities of the serving network, or both one or more tracking area codes and one or more cell identities of the serving network.

[0117] Embodiment 7 : A network node adapted to perform the method of any of embodiments 5 to 6.

[0118] Embodiment 8: A method performed by a User Equipment, UE, (700), the method comprising: receiving (Fig. 7, step 3), from a network node (702), Steering of Roaming, SoR, information and a Closed Access Group, CAG, information list; performing network selection based on input from both the SOR information and the CAG information list.

[0119] Embodiment 9: The method of embodiment 8 wherein receiving (Fig. 7, step 3) the SoR information and the CAG information list comprises receiving the SoR information and the CAG information list as separate information elements (e.g., in a same NAS message).

[0120] Embodiment 10: The method of embodiment 8 wherein receiving (Fig. 7, step 3) the SoR information and the CAG information list comprises receiving a SoR information container comprising the SoR information and the CAG information list, wherein the SoR information container is securely protected between a home network of the UE (700) and the UE (700). [0121] Embodiment 11: A method comprising:

• at a UDM (704) in a home network of a UE (700): o receiving (Fig. 7, step 1), from an AF (706), Steering of Roaming, SoR, information and a Closed Access Group, CAG, information list; o sending (Fig. 7, step 2), to an AMF (702), subscription data comprising the SoR information and the CAG information list;

• at the AMF (702): o receiving (Fig. 7, step 2) the subscription data comprising the SoR information and the CAG information list; o sending (Fig. 7, step 3) the SoR information and the CAG information list to a UE (700) (e.g., via a RAN node).

[0122] Embodiment 12: The method of embodiment 11 wherein the SoR information and the CAG information list are contained in a SoR information container that is securely protected between a home network of the UE (700) and the UE (700).

[0123] Embodiment 13: The method of embodiment 11 wherein the SoR information and the CAG information list are separate information elements.

[0124] Embodiment 14: The method of embodiment 11 wherein the CAG information list is not within an SoR information container that contains the SoR information, and the sending (Fig. 7, step 3) the SoR information and the CAG information list to the UE (700) comprising sending a NG-AP message to a RAN node, the NG-AP message comprising a downlink NAS message that includes the SoR information container and the CAG information list as part of a mobility restriction list.

[0125] Embodiment 15: A method performed by a User Equipment, UE, (800) that is registered in a Visited Public Land Mobile Network VPLMN, or in a Home Public Land Mobile Network, HPLMN, the method comprising: initiating (Fig. 8, step 1) a Control Plane Steering of Roaming, CP-SoR, procedure in which the UE (800) sends, to a network node (702), SoR request information.

[0126] Embodiment 16: The method of embodiment 15 wherein initiating (Fig. 8, step 2) the CP-SoR procedure comprises sending, to the network node (802), a registration request comprising the SoR request information.

[0127] Embodiment 17: The method of embodiment 15 or 16 wherein the SoR request information comprises information about one or more filtering functions.

[0128] Embodiment 18: The method of embodiment 17 wherein the information about the one or more filtering functions comprises a localized service ID, a hosting network ID, a UE current location, a location in which a localized service is available, or a combination of any two or more thereof.

[0129] Embodiment 19: The method of any of embodiments 15 to 18 further comprising receiving (Fig. 8, step 6) SoR information from the network node (802) in response to initiating the CP-SoR procedure.

[0130] Embodiment 20: The method of embodiment 19 wherein the SoR request information comprises information about one or more filtering functions, and the SoR information is based on the information about the one or more filtering functions comprised in the SoR request information.

[0131] Embodiment 21: The method of embodiment 19 or 20 wherein the SoR information received at the UDM comprises a priority list of preferred networks for network selection.

[0132] Embodiment 22: The method of embodiment 21 wherein the SoR information further comprises information that indicates a purpose of the priority list.

[0133] Embodiment 23: The method of embodiment 22 wherein the purpose of the priority list is accessing general or a specific localized service.

[0134] Embodiment 24: The method of any of embodiments 19 to 23 further comprising performing (Fig. 8, step 11) network selection for access to a localized service based on the SoR information (e.g., based on the priority list comprised in the SoR information in accordance with the indicated purpose of the priority list as being accessing a general or a specific localized service).

[0135] Embodiment 25: A UE adapted to perform the method of any of embodiments 19 to 24.

[0136] Embodiment 26: A method comprising:

• at an AMF (702) in either a VPLMN or HPLMN in which a UE (800) is registered: o receiving (Fig. 8, step 1), from the UE (800), a message (e.g., a registration request) that initiates a Control Plane Steering of Roaming, CP-SoR, procedure, the message comprising SoR request information; o sending (Fig. 8, step 2) the SoR request information to a UDM (804);

• at the UDM (804): o receiving (Fig. 8, step 2) the SoR request information; o sending (Fig. 8, step 3) the SoR request information to an AF (806); o receiving (Fig. 8, step 3), from the AF (806), SoR information in response to sending (Fig. 8, step 3) the SoR request information to the AF (806); and o sending (Fig. 8, step 4) the SoR information to the AMF (702); • at the AMF (702): o receiving (Fig. 8, step 4) the SoR information from the UDM (804); and o sending (Fig. 8, step 6) the SoR information to the UE (800).

[0137] Embodiment 27: The method of embodiment 25 wherein the SoR request information comprises information about one or more filtering functions, and the SoR information received at the UDM (804) from the AF (806) is based on the information about the one or more filtering functions comprised in the SoR request information.

[0138] Embodiment 28: The method of embodiment 25 or 26 wherein the SoR information received at the UDM comprises a priority list of preferred networks for network selection. [0139] Embodiment 29: The method of embodiment 27 wherein the SoR information received at the UDM further comprises information that indicates a purpose of the priority list. [0140] Embodiment 30: The method of embodiment 28 wherein the purpose of the priority list is accessing general or a specific localized service. [0141] Those skilled in the art will recognize improvements and modifications to the embodiments of the present disclosure. All such improvements and modifications are considered within the scope of the concepts disclosed herein.

Claims

Claims

1. A method performed by a User Equipment, UE, (600), the method comprising: registering (Fig. 6, step 1) with a serving network; receiving (Fig. 6, step 2) localized service information from the serving network, the localized service information comprising a validity area condition that indicates, using one or more serving network related identifiers, one or more areas in which one or more localized services of a hosting service are available and/or in which the hosting network is available; determining (Fig. 6, step 4) that the validity area condition is satisfied; and responsive to determining (Fig. 6, step 4) that the validity area condition is satisfied, initiating (Fig. 6, step 4) a scan for the hosting network.

2. The method of claim 1 wherein the one or more serving network related identifiers comprise one or more tracking area codes of the serving network.

3. The method of claim 2 wherein determining (Fig. 6, step 3) that the validity area condition is satisfied comprises: receiving (Fig. 6, step 3) broadcast information from the serving network, the broadcast information comprising a tracking area code; and determining (Fig. 6, step 3) that the tracking area code comprised in the broadcast information satisfies the validity area condition.

4. The method of claim 1 wherein the one or more serving network related identifiers comprise one or more cell identities of the serving network.

5. The method of claim 4 wherein the one or more serving network related identifiers comprise one or more tracking area codes of the serving network and one or more cell identities of the serving network.

6. The method of claim 4 or 5 wherein determining (Fig. 6, step 3) that the validity area condition is satisfied comprises: receiving (Fig. 6, step 3) broadcast information from the serving network, the broadcast information comprising a cell identity or both a tracking area code and a cell identity; and determining (Fig. 6, step 3) that the cell identity or both the tracking area code and cell identity comprised in the broadcast information satisfies the validity area condition.

7. The method of any of claims 1 to 6 further comprising: detecting (Fig. 6, step 5) the hosting network via the scan; and initiating (Fig. 6, step 5) a network selection procedure and registration procedure with the detected hosting network.

8. The method of any of claims 1 to 6 further comprising: detecting (Fig. 6, step 5) the hosting network via the scan; informing (Fig. 6, step 5) a user and/or an application layer of the UE that the hosting network and/or the one or more localized services of the hosting network are available.

9. The method of claim 8 further comprising initiating (Fig. 6, step 5) a network selection procedure and registration procedure with the detected hosting network, upon reception of a trigger of selection of the hosting network and/or at least one of the one or more localized services of the hosting network.

10. The method of any of claims 1 to 9 wherein the serving network is a home network of the UE.

11. The method of any of claims 1 to 9 wherein the serving network is a network other than a home network of the UE, but the UE uses home network credentials to access the serving network.

12. A User Equipment, UE, (600) adapted to: register (Fig. 6, step 1) with a serving network; receive (Fig. 6, step 2) localized service information from the serving network, the localized service information comprising a validity area condition that indicates, using one or more serving network related identifiers, one or more areas in which one or more localized services of a hosting service are available and/or in which the hosting network is available; and determine (Fig. 6, step 4) that the validity area condition is satisfied; and responsive to determining (Fig. 6, step 4) that the validity area condition is satisfied, initiate (Fig. 6, step 4) a scan for the hosting network.

13. The UE of claim 12 further adapted to perform the method of any of claims 2 to 11.

14. A User Equipment, UE, (600) comprising: a transmitter (1208); a receiver (1210); and processing circuitry (1202) associated with the transmitter (1208) and the receiver (1210), the processing circuitry (1202) configured to cause the UE (600) to: register (Fig. 6, step 1) with a serving network; receive (Fig. 6, step 2) localized service information from the serving network, the localized service information comprising a validity area condition that indicates, using one or more serving network related identifiers, one or more areas in which one or more localized services of a hosting service are available and/or in which the hosting network is available; and determine (Fig. 6, step 4) that the validity area condition is satisfied; and responsive to determining (Fig. 6, step 4) that the validity area condition is satisfied, initiate (Fig. 6, step 4) a scan for the hosting network.

15. The UE of claim 14 wherein the processing circuitry (1202) is further configured to cause the UE (600) to perform the method of any of claims 2 to 11.

16. A computer program comprising instructions which, when executed on at least one processor, cause the processor to carry out the method according to any of claims 1 to 11.

17. A carrier containing the computer program of claim 16, wherein the carrier is one of an electronic signal, an optical signal, a radio signal, or a computer readable storage medium.

18. A non-transitory computer-readable medium comprising instructions executable by processing circuitry of a User Equipment, UE, whereby the UE is operable to: register (Fig. 6, step 1) with a serving network; receive (Fig. 6, step 2) localized service information from the serving network, the localized service information comprising a validity area condition that indicates, using one or more serving network related identifiers, one or more areas in which one or more localized services of a hosting service are available and/or in which the hosting network is available; and determine (Fig. 6, step 4) that the validity area condition is satisfied; and responsive to determining (Fig. 6, step 4) that the validity area condition is satisfied, initiate (Fig. 6, step 4) a scan for the hosting network.

19. A method performed by a network node (602) of a serving network of a User Equipment, UE, (600), the method comprising: providing (Fig. 6, step 2) localized service information to the UE (600), the localized service information comprising a validity area condition that indicates, using one or more serving network related identifiers, one or more areas in which one or more localized services of a hosting service are available and/or in which the hosting network is available.

20. The method of claim 19 wherein the one or more serving network related identifiers comprise one or more tracking area codes of the serving network.

21. The method of claim 19 wherein the one or more serving network related identifiers comprise one or more cell identities of the serving network.

22. The method of claim 21 wherein the one or more serving network related identifiers further comprise one or more tracking area codes of the serving network.

23. A network node (602) for a serving network of a User Equipment, UE, (600), the network node adapted to: provide (Fig. 6, step 2) localized service information to the UE (600), the localized service information comprising a validity area condition that indicates, using one or more serving network related identifiers, one or more areas in which one or more localized services of a hosting service are available and/or in which the hosting network is available.

24. The network node of claim 23 further adapted to perform the method of any of claims 20 to 23.

25. A network node (602) for a serving network of a User Equipment, UE, (600), the network node comprising processing circuitry configured to cause the network node to: provide (Fig. 6, step 2) localized service information to the UE (600), the localized service information comprising a validity area condition that indicates, using one or more serving network related identifiers, one or more areas in which one or more localized services of a hosting service are available and/or in which the hosting network is available.

26. The network node of claim 25 wherein the processing circuitry is further configured to cause the network node to perform the method of any of claims 20 to 23.