Patent Description:
Document from <NPL>) overviews functionality of non-public networks. Document "<NPL> and "<NPL> are disclosing some aspects related to services by a 3GPP, 3rd Generation Partnership Project, network.

In some circumstances, a small cellular network may be deployed to provide services to local users within a certain area. For example, a temporary non-public cellular network may be set up to provide streaming video service to an audience at a live concert or football match. For another example, in locations such as airports, shopping malls, or school campuses, where large crowds may gather, small cellular networks may be deployed to provide localized services, such as commercial ads in a shopping mall. The services provided by these small cellular networks typically have two common characteristics, namely, (<NUM>) the services are localized, meaning that they are related to the activities/events in a certain localized area, and are usually limited to the users within the area and (<NUM>) the users do not utilize these services on a regular basis, but, most likely, in an on-demand or temporary fashion.

3GPP is studying how to enhance the <NUM> system to provide such localized services and enable users to access the hosting network that provide those services under the Study Item FS_PALS (<NPL>"). In this document, those localized services are referred to as "PALS (Providing Access to Localized Services) service", and a network that provides PALS services is referred to as a "PALS network", a "PALS hosting network", or simply a "hosting network".

A PALS hosting network may be a Non-Public Network as defined in <NPL>, but PALS service users may not have subscriptions to the PALS network. The PALS service provider may be the PALS network operator itself, another mobile network operator, or a third party service provider.

Steering of Roaming (SoR) function is used by home Public Land Mobile Network (HPLMN) operators to steer their roaming users toward preferred networks by updating the preferred PLMN list stored in the user's SIM (subscriber Identification Module) or UICC (Universal Integrated Circuit Card). In 5GS, the Control Plane SoR solution (CP-SoR) is used to allow the HPLMN to securely update the "Operator Controlled PLMN Selector with Access Technology" list in the WTRU.

<NUM> in Annex C of <NPL> shows the flows of CP-SoR during the Registration procedure, and Figure C. <NUM> in Annex C of TS <NUM> shows the flows of CP-SoR after the Registration procedure.

A more detailed understanding may be had from the detailed description below, given by way of example in conjunction with the drawings appended hereto. Figures in such drawings, like the detailed description, are exemplary. As such, the Figures and the detailed description are not to be considered limiting, and other equally effective examples are possible and likely. Furthermore, like reference numerals ("ref. ") in the Figures ("FIGs. ") indicate like elements, and wherein:.

In the following detailed description, numerous specific details are set forth to provide a thorough understanding of embodiments and/or examples disclosed herein. However, it will be understood that such embodiments and examples may be practiced without some or all of the specific details set forth herein. In other instances, well-known methods, procedures, components, and circuits have not been described in detail, so as not to obscure the following description. Further, embodiments and examples not specifically described herein may be practiced in lieu of, or in combination with, the embodiments and other examples described, disclosed, or otherwise provided explicitly, implicitly and/or inherently (collectively "provided") herein.

For example, the base station 114a in the RAN <NUM>/<NUM> and the WTRUs 102a, 102b, 102c may implement a radio technology such as Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA), which may establish the air interface <NUM> using wideband CDMA (WCDMA).

The WTRU <NUM> may include a full duplex radio for which transmission and reception of some or all of the signals (e.g., associated with particular subframes for both the uplink (e.g., for transmission) and downlink (e.g., for reception) may be concurrent and/or simultaneous. The full duplex radio may include an interference management unit <NUM> to reduce and or substantially eliminate self-interference via either hardware (e.g., a choke) or signal processing via a processor (e.g., a separate processor (not shown) or via processor <NUM>). In an embodiment, the WTRU <NUM> may include a half-duplex radio for which transmission and reception of some or all of the signals (e.g., associated with particular subframes for either the uplink (e.g., for transmission) or the downlink (e.g., for reception)).

Each of the eNode-Bs 160a, 160b, 160c may be associated with a particular cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, scheduling of users in the uplink (UL) and/or downlink (DL), and the like.

For example, gNBs 180a, 180b may utilize beamforming to transmit signals to and/or receive signals from the gNBs 180a, 180b, 180c.

The AMF a82a, 182b may provide a control plane function for switching between the RAN <NUM> and other RANs (not shown) that employ other radio technologies, such as LTE, LTE-A, LTE-A Pro, and/or non-3GPP access technologies such as WiFi.

Examples provided herein do not limit applicability of the subject matter to other wireless technologies, e.g., using the same or different principles as may be applicable.

As explained herein, a wireless transmit/receive unit (WTRU) may be an example of a user equipment (UE). Hence the terms UE and WTRU may be used with equal scope herein.

Potential PALS service users usually are PLMN subscribers who will camp on a PLMN network (either a Home PLMN or a Serving PLMN) most of the time. When the PALS service is available to the user, e.g. when the user is in the coverage area of a PALS network, the user needs to be steered toward the PALS network to register with and connect to the PALS network. Although it is possible for a user to manually select a PALS network, this method requires the user to possess the network selection information (e.g., name of the PALS network) and manually search for available PALS network. The inconveniences of this method likely will deter most users from using PALS services.

Thus, issues that are ripe for addressing include how to automatically steer WTRUs from a PLMN network to a PALS network when PALS service is available and how to automatically steer WTRUs from the PALS network back to the PLMN network when the PALS service becomes unavailable?.

This section addresses techniques for steering WTRU's between a PLMN and a PALS network using special Steering of Roaming information for PALS network steering. In embodiments, an HPLMN-provided PALS Network Selector or a network identifier in the selector may be associated with a time window and an area. A network selector may be considered a data structure for a set of information used for network selection. The data structure may include the list of network identifiers, associated time window, associated geographic area, and the like. Hence, the network selector may be caused to be active only when certain time and/or location conditions are met or the network identifier may be considered for network selection only when the time and/or location conditions are met.

More particularly, based on the service agreement between the PLMN operator and the PALS service provider or PALS network operator, the WTRU's Home PLMN may create special SoR information for the purpose of automatically steering the WTRU between the PLMN and PALS networks. Referring now to <FIG>, in addition to the normal operator-controlled PLMN selector 200a, the special SoR may contain one or more Operator-Controlled PALS Network Selector(s) 200b that may comprise any one or more of the following data (with <FIG> illustrating an exemplary manner in which such information may be organized):.

The Home PLMN may store the above SoR information in the Unified Data Management (UDM)/Unified Data Repository (UDR) and send it to the WTRU using the SoR procedure defined in 3GPP TS <NUM>, "Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode", V16. <NUM>, <NUM>-<NUM>. If the WTRU has valid SoR information for PALS network steering, in an exemplary embodiment, it may perform a network selection operation such as described below and illustrated by the flowchart of <FIG>.

First, the WTRU determines if it has a PALS Network Selector available (<NUM>). If not, the process ends. (Note that, in <FIG>, decision step outcomes that result in the ending of the process, such as the aforementioned NO decision in step <NUM>, are implicit - i.e., not shown in the flowchart - in order to avoid overly complicating the FIG.

If, on the other hand, the WTRU determines in step <NUM> that a PALS Network Selector is available, flow continues in the flowchart. Next, the WTRU may determine whether to activate the PALS Network Selector based on the following:.

If the PALS Network Selector is activated in <NUM>, the WTRU may determine its priority against other PLMN selectors (<NUM>). For instance, if the PALS Network Selector is associated with an indication that it has higher priority than other PLMN selectors, it may use this Selector for network selection (<NUM>). If, on the other hand, if the PALS Network Selector is not associated with an indication that it has higher priority than other PLMN selectors, it may use other PLMN selectors for network selection (<NUM>); and, if no PLMN is available or selected, it may use the PALS Network Selector for network selection.

If the WTRU has determined to use the PALS Network Selector for network selection, it may check whether it needs to switch to SNPN Access Mode for network selection (<NUM>). If the PALS Network Selector has the indication that the WTRU should switch to SNPN access mode, it may switch to SNPN access mode (<NUM>). If the PALS Network Selector does not have the indication that the WTRU should switch to SNPN access mode, it may further check if the network identifiers in the prioritized list are SNPN networks or PLMN networks, and may switch to SNPN access mode for those SNPN networks.

If the CAG ID broadcasted by the PALS network cell is configured in the WTRU's allowed CAG list. The WTRU will check the broadcasted CAG ID against the configured allowed CAG ID list corresponding to the PALS network.

If the WTRU has determined to use the PALS Network Selector for network selection, it may search networks and select the network according to the priority order in the list. If the WTRU has switched to SNPN access mode, it may only search and select SNPN networks (<NUM>). If the WTRU is not in SNPN access mode, it may only search and select PLMN networks (<NUM>).

The WTRU checks if any found network(s) is/are in in the selector's list (<NUM>). If not, the process ends. For each network identifier that is in the list, the WTRU determines if the network has an associated time window and/or area (<NUM>). If there are no such criteria, the WTRU selects the network (<NUM>) If there are such criteria, the WTRU checks if the current time and/or WTRU location meets the condition (<NUM>), and if the criteria are met, it selects the network (<NUM>) and the selection process is complete. If not, the process is ended without selecting a PALS network.

In an alternate embodiment, the WTRU may present the found network that meets the above conditions to the user and allow the user to decide whether to select the network.

In embodiments, if there is a Time Window and/or an Area associated with an active PALS Network Selector, or if there is a Time Window and/or an Area associated with the selected PALS network, the WTRU should keep monitoring the time and the WTRU's location to determine whether to deactivate the selector or re-select the network. If the time is out of the Time Window associated with the PALS Network Selector or the WTRU location is out of the area associated with the selector, the WTRU should deactivate the PALS Network Selector and use a PLMN selector to reselect a PLMN network.

If the time is out of the Time Window associated with the selected PALS network or the WTRU location is out of the area associated with the selected network, the WTRU should de-register from the PALS network and re-select another PALS network or PLMN network.

If the selected PALS network becomes unavailable, e.g., due to WTRU moving out of its coverage, the WTRU may reselect another PALS network that is in the list or the WTRU may de-activate the PALS Network Selector and use the PLMN network selectors to re-select a PLMN network.

The 5GS network may, at any time, update the SoR for PALS network steering (e.g., during the periodic or mobility registration procedure) or via the UCU procedure. The WTRU should replace the stored PALS Network Selector(s) with the new one(s) and re-select the network according to the new PALS Network Selector if they meet the conditions to be activated.

The WTRU may receive the initial time window in the Registration Accept message when it registers to the PALS network. The WTRU may trigger the Registration procedure to request a new time window from the network.

The time window also may be on the PDU session level. The network may configure the time window for each PDU session established with the PALS network. The WTRU in this case may receive the time window from the network (SMF) in the PDU session accept message. When the time window expires, the WTRU may deactivate the PDU session. The WTRU may implicitly deactivate the PDU session or may send the PDU session deactivation message to the network.

The network may want to extend the time window. In such a case, the network may respond to PDU session deactivation message with a PDU deactivation reject message with the cause code and a new time window for the WTRU. The time window also may be updated by the WTRU (in the case the WTRU receives indication from the higher layers). The WTRU may send an indication or request a new time window from the network by sending a session management NAS message to the network, e.g., a PDU session modification request.

The network (e.g. AMF or SMF) may determine the time window or decide to update the time window based on interactions with a third party external server (the PALS network may be configured by a third party server). The external server may interact with the PALS network via the NEF API. The NEF (Network Exposure Function) API will provide the ability to the third party server to provide inputs to the network to determine the time window for the PALs network either for the registration procedure or session management procedure or both. The inputs provided by the third party server to the network may include expected time of the event that the PALs network is created for, indication of the start of the event, indication of when the event is close to being ended, etc..

The 5GS network may, at any time, revoke the SoR for PALS network steering, in which case the WTRU should delete the stored PALS Network Selector(s) and re-select a network according to other PLMN network selectors.

As the local services can be temporary, event-based, and confined to a specific environment, the hosting network that offers the local services can be a PLMN or SNPN (Stand-alone Non-Public Network). In some venues, such as a festival venue, stadium, or convention center, there can be multiple hosting network deployments to cover the same area and offer either different or the same/similar services. For example, a venue owner may deploy the network infrastructure and lease the infrastructure to several PLMN or SNPN operators in order for them to provide temporary, event-related services to spectators/audiences/attendees. As the services as well as the hosting network may be temporary, it can be expected that a PLMN operator will not have long-term, individual service level agreements (SLAs) with each hosting network. Therefore, it can be expected that these short-term agreements are event-based and may have different charging policies depending on the infrastructure capabilities or agreements between the hosting networks and the infrastructure owner.

Theoretically, users who wish to access the local services can choose which hosting network to access manually. However, there may be some coverage and charging implications that need to be optimized from both the user and PLMN operator sides. On the one hand, the same or a similar service can be offered by two different hosting networks, and a PLMN may have a preference for its subscribers to choose the hosting network with the better agreement. On the other hand, based on the battery level of the WTRU, a user may want to choose the hosting network that provides better signal strength/quality, even if that hosting network has an inferior agreement compared to another network option. Therefore, a mechanism is needed to incorporate WTRU-preference and/or network preference when a WTRU requests either an initial access to a local service or switches from one local service to another.

Thus, an issue that is ripe for consideration is how to enable WTRU and PLMN operators to prioritize hosting networks that are offering the same or similar local services within the same venue/confined environment/coverage area.

This section describes techniques for steering WTRU's between multiple PALS networks that enable the SoR-AF to construct a preferred PALS network list using the service information retrieved from the PALS networks (e.g., QoS/KPI (Quality of Service/Key Performance Indicator) and charging data). The WTRU may also select its own preferred PALS network based on received signal level. This section also describes an algorithm to choose between a WTRU-constructed list and network-provided list when both are available to a WTRU.

These techniques include algorithms and procedures to prioritize hosting networks that are offering the same or similar local service. Prioritization of the hosting networks can be based on:.

Local services provided by the hosting networks may be conventional services such as voice and data, as well as new services, such as computing, machine learning (ML), and storage. Therefore, it can be expected that there may be various QoS/KPI assignments for different service types. For example, QoS/KPI of a ML-oriented service may be a confidence level of the ML model inference. On the other hand, the performance of a computing-oriented service may be dependent on the available computer resources and load level of the hosting network. As at least one goal is to account for different components of a local service and hosting network, different utility functions may be considered to assess the value/performance of various information elements within a range, e.g., from <NUM> to <NUM>. These different utility functions as well as their weights on the network priority assessment can be configured to represent a network operator's preferences or objectives.

<FIG> illustrates an exemplary embodiment of a method for the Steering of Roaming Application Function (SoR-AF) to construct a network-preferred hosting network prioritization list.

The algorithm is initialized when (i) the status information of each hosting network (such as network load); (ii) service details (such as service-specific QoS provision from each hosting network); and (iii) service charging information from each hosting network are available at SOR-AF (<NUM>).

Next, a control mechanism checks whether a SOR information/parameter update request has been received (<NUM>).

If there is a SOR information/parameter update request, SOR-AF uses the hosting network and local service related information, namely, service QoS provision (SQoS,i), hosting network load (Sload,i) and service charge information (Scharge,i) for the hosting network i. Each information element is used as the input of the relevant utility functions f1 for service QoS provision, f2 for hosting network load, and f3 for service charging. If the WTRU has provided a list of available hosting networks (see <FIG>, for instance) that shall be prioritized, then SOR-AF may take into consideration radio parameters (e.g., signal strength per hosting network), UE battery level, and/or battery threshold level as an additional functional input to the algorithm if such additional parameters were optionally provided by the WTRU. The outputs of the utility functions are summed, and a priority level of each hosting network Si is obtained (<NUM>).

Upon determining the priority levels of the hosting networks, SOR-AF sorts the priority level in descending order (<NUM>) - the hosting network with the highest priority becomes the first item in the list. The process ends at <NUM>.

For a WTRU to construct a network priority list, first of all, a network scanning process is triggered to obtain the received signal level of the available hosting networks. Once the received signal strength information is available at the WTRU, the WTRU constructs its own priority list of available hosting networks by sorting all the networks in descending order based on their received signal level. Accordingly, the hosting network with the highest received signal level becomes the first item in the list.

As a WTRU will have one priority list based on its preference and another priority list messaged from its home PLMN that is based on the network preference, a method has been developed to decide which lists will be considered for use and, of those lists, which list to use. As WTRU constructs its priority list based on the received signal level of the surrounding hosting networks, the hosting network with the highest priority may be considered as the network that would be the most energy efficient. Therefore, in one embodiment, a user-defined battery level threshold may be used to determine whether the WTRU will use the WTRU-preferred priority list or the network-preferred priority list to select a network. Such a threshold value can be configured by the WTRU. However, if the network would like to force its priority list to be considered by the WTRU during the network selection process, the battery level threshold value can be set to <NUM>.

<FIG> is a flowchart illustrating a network selection process in accordance with such an embodiment. The method is initialized at <NUM> when (i) the WTRU battery level threshold value; (ii) WTRU-preferred; and (iii) network-preferred priority lists are available at the WTRU.

At step <NUM>, a control mechanism checks whether the first items in both the WTRU-preferred and the network-preferred priority lists belong to the same hosting network.

If the same hosting network is listed as the highest priority network in both WTRU-preferred and network-preferred priority lists, flow proceeds to step <NUM> where the WTRU selects this hosting network.

If, on the other hand, in step <NUM>, it is determined that different hosting networks are listed as the highest priority network in the WTRU-preferred and the network-preferred lists, flow proceeds to step <NUM>, in which another control mechanism checks whether WTRU battery level is below the pre-defined battery level threshold value.

If the WTRU battery level is below the threshold, flow proceeds to step <NUM>, in which the hosting network with the highest priority in the WTRU-preferred priority list is selected.

If the WTRU battery level is above the threshold, flow instead proceeds to step <NUM>, in which the hosting network with the highest priority in the network-preferred priority list is selected. The process ends at <NUM>.

<FIG> is a signal flow diagram illustrating an exemplary signal flow for the hosting network prioritization and selection procedure in accordance with an embodiment.

In step 1a, the WTRU sends an access request to its home PLMN regarding a specific local service, which may be a conventional service (voice, data) or a new service, e.g., computing services, ML services, storage services.

Once the WTRU sends the access request, in step 1b, it triggers a network scanning process in order to determine the received signal level of the available hosting networks and then constructs its own priority list of available hosting networks by sorting all the networks in descending order based on their received signal level.

In step <NUM>, the AMF sends a SOR information/parameter update request to the UDM.

In step <NUM>, the UDM requests the details and charging information of the requested service from the NEF.

In step <NUM>, the NEF requests the service details and charging information from the hosting networks that have coverage in the WTRU's location and are providing the requested service. In this example, there are two such networks, namely, Hosting Network A and Hosting Network B; so there are two such requests, 4a and 4b.

In steps 5a and 5b, Hosting Network A and Hosting Network B send the local service details and charging information to the home PLMN, respectively.

In step <NUM>, the local service and charging information received from the hosting networks are exposed to the UDM in the Home PLMN.

In step <NUM>, the UDM sends a SOR parameter update request to the home PLMN SOR-AF.

In step <NUM>, based on the received local service and charging information, the home PLMN SOR-AF constructs a priority list for the hosting networks providing the local service, such as described in connection with <FIG>.

In step <NUM>, the SOR-AF sends the priority list for the hosting networks back to the UDM as a SOR parameter update response.

In step <NUM>, the UDM sends an update request to the AMF regarding the SOR information/parameters to the WTRU.

In step <NUM>, the AMF transmits the updated SOR parameter to the WTRU via a DL NAS (Downlink Non-Access Stratum) message.

In step <NUM>, upon receiving the updated SOR information/parameter on the network priority list, the WTRU overwrites the existing list with the new one.

In step <NUM>, the WTRU compares the network-preferred priority list and its own priority list in order to select one of the hosting networks to access the local service, such as described in connection with <FIG>.

In step <NUM>, the WTRU attempts a registration to the selected hosting network, wherein step 14a represents the signal flow if Hosting Network A is selected and step 14b represents the signal flow if Hosting Network B is selected.

The methods, apparatus, techniques, and procedure described in this disclosure also may apply in cases where WTRU switches from one local service to another. In each time, the described message flow can be followed to incorporate WTRU preference as well as its home PLMN preference for the hosting network selection.

Alternatively, a WTRU may be configured to prioritize the list of available hosting networks i.e., hosting networks that are detected as a result of radio scan, in accordance with any of the following methods.

In a first alternative, the WTRU may share the list of available hosting networks along with optional parameters (e.g., radio signal strength per hosting network, battery information of the WTRU, and threshold configuration for battery level) with the network and permit the network to assist with the prioritization. Whether to operate in this manner may be based on whether the WTRU is configured to use the network assistance to prioritize the available hosting networks and/or the network has indicated support for network assisted prioritization during registration/mobility registration procedure. The network may prioritize the list received from the WTRU using any of the methods discussed above (e.g., see <FIG>) and send it back to the WTRU via control plane NAS signaling.

In another alternative embodiment, the WTRU may prioritize the list of available hosting networks by sorting it based on a network-provided preferred priority list of hosting networks. The WTRU may be configured (e.g., pre-configured and/or configured via control signaling from the network during operation) whether to operate in accordance with this embodiment. In addition, the specific implementation details/configurations for this embodiment may be configured in the WTRU (e.g., pre-configured and/or via control signaling form the network). The WTRU would check if available hosting networks were present in the network-preferred priority list, and, if so, priority may be set according to that network-preferred list.

<FIG> is a flowchart illustrating a process in accordance with this alternative type of embodiment. In step <NUM>, the WTRU scans for available hosting networks. This scan may be performed when the WTRU powers up and/or based on a trigger event, such as a user input. As noted above, this may be configured (e.g., pre-configured) in the WTRU and/or based on a trigger event, such as an indication from the network during registration/mobility registration procedure that it supports network assisted prioritization.

In step <NUM>, the WTRU checks if it is configured to use network assistance to prioritize available hosting networks.

If the WTRU is configured to use network assistance to prioritize hosting networks, network-assisted prioritization is selected in step <NUM>, and flow proceeds from step <NUM> to step <NUM>, where the WTRU sends the list of available hosting networks developed in step <NUM> to the Home PLMN, such as via control plane NAS signaling (e.g., Mobility registration update, service request messages). Optionally, the WTRU may include additional information along with the list of found hosting networks, e.g., Signal Strength per hosting network, battery information of the WTRU, threshold for battery level when it shall be considered for prioritizing the hosting networks (i.e., if the battery level of the WTRU is below a threshold value, the network should prioritize those hosting networks that have good radio conditions and require less WTRU power for communication).

The network may prioritize the list of hosting networks received from the WTRU using the mechanism/algorithm defined in <FIG>, for instance, and send the prioritized list back to the WTRU. The network may send the list of prioritized hosting networks to the WTRU via SoR or control plane NAS signaling (WTRU configuration Update command procedure).

Thus, next, in step <NUM>, the WTRU receives the prioritized list from the network and, in step <NUM>, selects the hosting network from the available hosting networks having the highest priority in the received list.

If, on the other hand, the WTRU is not configured to use network-assisted prioritization, flow instead proceeds to step <NUM>, where the WTRU checks if it is configured with local prioritization based on a network-preferred priority list. If not, it will fall back to another prioritization scheme, such as the scheme illustrated in <FIG>. If so, flow instead proceeds to step <NUM>, where the WTRU sorts the list of available hosting networks (found during the radio scan in step <NUM>) based on the network-preferred priority list. Any available hosting network that also is present in the network preferred priority list will get the same priority in the final sorted hosting network list. Then, in step <NUM>, the WTRU uses the sorted hosting network list prepared in step <NUM> to trigger hosting network selection, the first entry in the list being the highest priority.

<FIG> is a signal flow diagram illustrating exemplary signal flow in accordance with this alternative hosting network prioritization and selection procedure.

In step 1a, the WTRU performs a radio scan and detects available hosting networks. In step 1b, the WTRU (i) sends an access request to its home PLMN regarding a specific local service, which may be a conventional service (voice, data) or a new service, e.g., computing services, ML services, storage services; and (ii) shares the list of available hosting networks, optionally along with a radio signal strength of each available hosting network detected during the radio scan, WTRU battery level information, and threshold configuration for WTRU battery level.

In response, the NEF requests the service details and charging information from the hosting networks that have coverage on the WTRU location and are providing the requested service. In this example, the WTRU is in the coverage area of Hosting Network A and Hosting Network B. Thus, in step 4a, the NEF sends the request to Hosting Network A, and in step 4b, the NEF sends the request to the Hosting Network B.

Next, in steps 5a and 5b, Hosting Network A and Hosting Network B send the local service details and charging information to the home PLMN, respectively.

Then, in step <NUM>, the local service and charging information received from the hosting networks are exposed to the UDM.

The UDM, in step <NUM>, sends a SOR parameter update request to the home PLMN SOR-AF.

In step <NUM>, based on the list of available hosting networks shared by the WTRU (which may include the optionally shared parameters noted in step 1b) and the received local service and charging information, the home PLMN SOR-AF constructs a priority list for the hosting networks providing the local service, as described in <FIG>.

In step <NUM>, the SoR-AF sends the priority list for the hosting networks back to UDM as a SOR parameter update response.

In step <NUM>, the UDM sends an update request to AMF regarding the SOR information/parameters to the WTRU.

In step <NUM>, the AMF transmits the updated SOR parameter to the WTRU via DL NAS message.

Upon receiving the updated SOR information/parameter on the network priority list, in step <NUM>, the WTRU overwrites the existing list with the new one.

Next, in step 13a or 13b, the WTRU attempts a registration to the selected hosting network, where step 13a considers the selected hosting network to be Hosting Network A and step 13b considers the selected hosting network to be Hosting Network B.

Based on the forgoing discussion of network steering between multiple wireless networks, <FIG> depicts a method <NUM> for selecting a local network for a WTRU to join, according to the claimed invention.

In one example, the WTRU may be operating in a PLMN and may be tasked with selecting a local service hosting network, such as in a PALS network, with which to join.

At <NUM>, the WTRU stores SoR information for a plurality of local service hosting networks. The SoR information includes an indication of a priority order in a list of network identifiers. In one example, the network identifiers may include PLMN identifiers or SNPN network identifiers. At <NUM>, the WTRU switches to an access mode for network searching.

In one example, switching to an access mode for network searching may include switching to a SNPN, access mode to enable searching of networks listed in the prioritized list of network identifiers.

At <NUM>, the WTRU searches for a local service hosting network to join from among the plurality of local service hosting networks. This search may allow the WTRU to determine which network(s) in the list of network identifiers is available for joining. In one example, the search may include a search of SNPNs to join from among the plurality of local service hosting networks in the list of network identifiers. At <NUM>, the WTRU selects a local service hosting network to join based on the indication of the priority order in the list of network identifiers. In one example, the WTRU may select a SNPN based on at least the priority of the SNPN on the list of network identifiers. In a further example, selecting the local service hosting network to join includes selecting a local hosting network having a network identifier associated with either or both of a time window and/or a geographic area. The time window indicates a time period during which the corresponding network is considered valid or available for joining. The geographic area indicates an area within which the local service is available. In one embodiment, the selection by a WTRU of a local service hosting network may be performed by a network selector as described hereinabove.

The method <NUM> may further include a procedure to update the SoR information during any one or more of a periodic procedure or a mobility registration procedure. Such an update may include adding to the existing SoR information or replacing the SoR information when new information becomes available. Such an update may be based on a location update of a WTRU and/or an update of a local service hosting network information such as a change of identity, capability, or availability for WTRU use.

The foregoing embodiments are discussed, for simplicity, with regard to the terminology and structure of infrared capable devices, i.e., infrared emitters and receivers. However, the embodiments discussed are not limited to these systems but may be applied to other systems that use other forms of electromagnetic waves or non-electromagnetic waves such as acoustic waves.

It is also to be understood that the terminology used herein is for the purpose of describing particular embodiments only, and is not intended to be limiting. As used herein, the term "video" or the term "imagery" may mean any of a snapshot, single image and/or multiple images displayed over a time basis. As another example, when referred to herein, the terms "user equipment" and its abbreviation "UE", the term "remote" and/or the terms "head mounted display" or its abbreviation "HMD" may mean or include (i) a wireless transmit and/or receive unit (WTRU); (ii) any of a number of embodiments of a WTRU; (iii) a wireless-capable and/or wired-capable (e.g., tetherable) device configured with, inter alia, some or all structures and functionality of a WTRU; (iii) a wireless-capable and/or wired-capable device configured with less than all structures and functionality of a WTRU; or (iv) the like. Details of an example WTRU, which may be representative of any WTRU recited herein, are provided herein with respect to <FIG>. As another example, various disclosed embodiments herein supra and infra are described as utilizing a head mounted display. Those skilled in the art will recognize that a device other than the head mounted display may be utilized and some or all of the disclosure and various disclosed embodiments can be modified accordingly without undue experimentation. Examples of such other device may include a drone or other device configured to stream information for providing the adapted reality experience.

In addition, the methods provided herein may be implemented in a computer program, software, or firmware incorporated in a computer-readable medium for execution by a computer or processor. Examples of computer-readable media include electronic signals (transmitted over wired or wireless connections) and computer-readable storage media. Examples of computer-readable storage media include, but are not limited to, a read only memory (ROM), a random access memory (RAM), a register, cache memory, semiconductor memory devices, magnetic media such as internal hard disks and removable disks, magnetooptical media, and optical media such as CD-ROM disks, and digital versatile disks (DVDs). A processor in association with software may be used to implement a radio frequency transceiver for use in a WTRU, UE, terminal, base station, RNC, MME, EPC, AMF or any host computer.

Variations of the method, apparatus and system provided above are possible without departing from the scope of the invention. In view of the wide variety of embodiments that can be applied, it should be understood that the illustrated embodiments are examples only, and should not be taken as limiting the scope of the following claims. For instance, the embodiments provided herein include handheld devices, which may include or be utilized with any appropriate voltage source, such as a battery and the like, providing any appropriate voltage.

Moreover, in the embodiments provided above, processing platforms, computing systems, controllers, and other devices that include processors are noted. These devices may include at least one Central Processing Unit ("CPU") and memory. In accordance with the practices of persons skilled in the art of computer programming, reference to acts and symbolic representations of operations or instructions may be performed by the various CPUs and memories. Such acts and operations or instructions may be referred to as being "executed," "computer executed" or "CPU executed.

One of ordinary skill in the art will appreciate that the acts and symbolically represented operations or instructions include the manipulation of electrical signals by the CPU. An electrical system represents data bits that can cause a resulting transformation or reduction of the electrical signals and the maintenance of data bits at memory locations in a memory system to thereby reconfigure or otherwise alter the CPU's operation, as well as other processing of signals. The memory locations where data bits are maintained are physical locations that have particular electrical, magnetic, optical, or organic properties corresponding to or representative of the data bits. It should be understood that the embodiments are not limited to the above-mentioned platforms or CPUs and that other platforms and CPUs may support the provided methods.

The data bits may also be maintained on a computer readable medium including magnetic disks, optical disks, and any other volatile (e.g., Random Access Memory (RAM)) or non-volatile (e.g., Read-Only Memory (ROM)) mass storage system readable by the CPU. It should be understood that the embodiments are not limited to the above-mentioned memories and that other platforms and memories may support the provided methods.

There is little distinction left between hardware and software implementations of aspects of systems. The use of hardware or software is generally (but not always, in that in certain contexts the choice between hardware and software may become significant) a design choice representing cost versus efficiency tradeoffs. There may be various vehicles by which processes and/or systems and/or other technologies described herein may be effected (e.g., hardware, software, and/or firmware), and the preferred vehicle may vary with the context in which the processes and/or systems and/or other technologies are deployed. For example, if an implementer determines that speed and accuracy are paramount, the implementer may opt for a mainly hardware and/or firmware vehicle. If flexibility is paramount, the implementer may opt for a mainly software implementation. Alternatively, the implementer may opt for some combination of hardware, software, and/or firmware.

Insofar as such block diagrams, flowcharts, and/or examples include one or more functions and/or operations, it will be understood by those within the art that each function and/or operation within such block diagrams, flowcharts, or examples may be implemented, individually and/or collectively, by a wide range of hardware, software, firmware, or virtually any combination thereof. In an embodiment, several portions of the subject matter described herein may be implemented via Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs), digital signal processors (DSPs), and/or other integrated formats. However, those skilled in the art will recognize that some aspects of the embodiments disclosed herein, in whole or in part, may be equivalently implemented in integrated circuits, as one or more computer programs running on one or more computers (e.g., as one or more programs running on one or more computer systems), as one or more programs running on one or more processors (e.g., as one or more programs running on one or more microprocessors), as firmware, or as virtually any combination thereof, and that designing the circuitry and/or writing the code for the software and or firmware would be well within the skill of one of skill in the art in light of this disclosure. In addition, those skilled in the art will appreciate that the mechanisms of the subject matter described herein may be distributed as a program product in a variety of forms, and that an illustrative embodiment of the subject matter described herein applies regardless of the particular type of signal bearing medium used to actually carry out the distribution. Examples of a signal bearing medium include, but are not limited to, the following: a recordable type medium such as a floppy disk, a hard disk drive, a CD, a DVD, a digital tape, a computer memory, etc., and a transmission type medium such as a digital and/or an analog communication medium (e.g., a fiber optic cable, a waveguide, a wired communications link, a wireless communication link, etc.).

Those skilled in the art will recognize that it is common within the art to describe devices and/or processes in the fashion set forth herein, and thereafter use engineering practices to integrate such described devices and/or processes into data processing systems. That is, at least a portion of the devices and/or processes described herein may be integrated into a data processing system via a reasonable amount of experimentation. Those having skill in the art will recognize that a typical data processing system may generally include one or more of a system unit housing, a video display device, a memory such as volatile and non-volatile memory, processors such as microprocessors and digital signal processors, computational entities such as operating systems, drivers, graphical user interfaces, and applications programs, one or more interaction devices, such as a touch pad or screen, and/or control systems including feedback loops and control motors (e.g., feedback for sensing position and/or velocity, control motors for moving and/or adjusting components and/or quantities). A typical data processing system may be implemented utilizing any suitable commercially available components, such as those typically found in data computing/communication and/or network computing/communication systems.

The herein described subject matter sometimes illustrates different components included within, or connected with, different other components. It is to be understood that such depicted architectures are merely examples, and that in fact many other architectures may be implemented which achieve the same functionality. In a conceptual sense, any arrangement of components to achieve the same functionality is effectively "associated" such that the desired functionality may be achieved. Hence, any two components herein combined to achieve a particular functionality may be seen as "associated with" each other such that the desired functionality is achieved, irrespective of architectures or intermedial components. Likewise, any two components so associated may also be viewed as being "operably connected", or "operably coupled", to each other to achieve the desired functionality, and any two components capable of being so associated may also be viewed as being "operably couplable" to each other to achieve the desired functionality.

It will be understood by those within the art that, in general, terms used herein, and especially in the appended claims (e.g., bodies of the appended claims) are generally intended as "open" terms (e.g., the term "including" should be interpreted as "including but not limited to," the term "having" should be interpreted as "having at least," the term "includes" should be interpreted as "includes but is not limited to," etc.). It will be further understood by those within the art that if a specific number of an introduced claim recitation is intended, such an intent will be explicitly recited in the claim, and in the absence of such recitation no such intent is present. For example, where only one item is intended, the term "single" or similar language may be used. As an aid to understanding, the following appended claims and/or the descriptions herein may include usage of the introductory phrases "at least one" and "one or more" to introduce claim recitations. However, the use of such phrases should not be construed to imply that the introduction of a claim recitation by the indefinite articles "a" or "an" limits any particular claim including such introduced claim recitation to embodiments including only one such recitation, even when the same claim includes the introductory phrases "one or more" or "at least one" and indefinite articles such as "a" or "an" (e.g., "a" and/or "an" should be interpreted to mean "at least one" or "one or more"). The same holds true for the use of definite articles used to introduce claim recitations. In addition, even if a specific number of an introduced claim recitation is explicitly recited, those skilled in the art will recognize that such recitation should be interpreted to mean at least the recited number (e.g., the bare recitation of "two recitations," without other modifiers, means at least two recitations, or two or more recitations). Furthermore, in those instances where a convention analogous to "at least one of A, B, and C, etc." is used, in general such a construction is intended in the sense one having skill in the art would understand the convention (e.g., "a system having at least one of A, B, and C" would include but not be limited to systems that have A alone, B alone, C alone, A and B together, A and C together, B and C together, and/or A, B, and C together, etc.). In those instances where a convention analogous to "at least one of A, B, or C, etc." is used, in general such a construction is intended in the sense one having skill in the art would understand the convention (e.g., "a system having at least one of A, B, or C" would include but not be limited to systems that have A alone, B alone, C alone, A and B together, A and C together, B and C together, and/or A, B, and C together, etc.). It will be further understood by those within the art that virtually any disjunctive word and/or phrase presenting two or more alternative terms, whether in the description, claims, or drawings, should be understood to contemplate the possibilities of including one of the terms, either of the terms, or both terms. " Further, the terms "any of" followed by a listing of a plurality of items and/or a plurality of categories of items, as used herein, are intended to include "any of," "any combination of," "any multiple of," and/or "any combination of multiples of" the items and/or the categories of items, individually or in conjunction with other items and/or other categories of items. Moreover, as used herein, the term "set" is intended to include any number of items, including zero. Additionally, as used herein, the term "number" is intended to include any number, including zero. And the term "multiple", as used herein, is intended to be synonymous with "a plurality".

Claim 1:
A method performed by a Wireless Transmit/Receive Unit, WTRU, (<NUM>) for selecting a local service network, the method comprising:
receiving, from a non-access stratum signaling, steering of roaming, SoR, information for one or more networks providing localized services, wherein the SoR information comprises an indication of a prioritized list of one or more networks providing localized services, wherein each network providing localized services in the prioritized list of one or more networks is associated with a network identifier (211a, 211b, 211c), a time window (<NUM>, <NUM>) and a geographic area (<NUM>, <NUM>);
switching (<NUM>) to an access mode for network searching;
searching (<NUM>) for a network providing localized services; selecting (<NUM>) a network providing localized services based on the prioritized list of one or more networks providing localized services, on a condition that a current time is within a time window associated with the selected network providing localized services, wherein the time window comprises a time period during which the corresponding network is considered for joining; and
joining the selected network providing localized services.