Mechanism for hosted network selection

Abstract

A wireless transmit / receive unit (WTRU) may trigger a search for a hosted network based on one or more of: a request for a localized service from a user, a periodic search, a coverage loss, and one or more validity conditions satisfying the localized service. The WTRU may select one of a closed access group (CAG) and a standalone non-public network (SNPN) based on one or more of a Universal Subscriber Identity Module (USIM) elementary file, user preferences in a local non-volatile memory (NVM) store, a last search technique, power-on sequence preferences, values provided by the network, and a WTRU residence state. The WTRU may register with the CAG or the SNPN based on the selection of the CAG or the SNPN. The WTRU may receive one or more of a USIM elementary file, a power-on sequence preference, and a value provided by the network in the configuration information.

Description

[0001] Cross-reference to related applications

[0002] This application claims priority to U.S. Provisional Application No. 63 / 444,390, filed February 9, 2023, which is incorporated herein by reference in its entirety. Background Art

[0003] A non-public network (NPN) is a fifth-generation mobile phone system (5GS) deployed for non-public use. An NPN can be either a standalone non-public network (SNPN) or a public network-integrated NPN (PNI-NPN).

[0004] SNPN is operated by NPN operators and does not rely on the network functions provided by the Public Land Mobile Network (PLMN). PNI-NPN is a non-public network deployed with PLMN support. Summary of the Invention

[0005] A wireless transmit / receive unit (WTRU) may trigger a search for a hosted network based on one or more of: a request for localized service from a user, a periodic search, loss of coverage, and satisfaction of one or more validity conditions for the localized service. The WTRU may select one of a closed access group (CAG) and a standalone non-public network (SNPN) based on one or more of a universal subscriber identity module (USIM) elementary file, user preferences in local non-volatile memory (NVM) storage, a last search technique, a power-up sequence preference, a value provided by the network, and the WTRU's camp-on state. The WTRU may register with the selected CAG or SNPN based on the selection of the CAG or SNPN.

[0006] In another example, the WTRU may receive one or more of a USIM base file, a power-up sequence preference, and a value provided by the network in the configuration information. In an additional example, the network may be a home public land mobile network (PLMN) (HPLMN), a visited PLMN (VPLMN), or a certificate holder (CH).

[0007] In a further example, one or more of the USIM base file, user preferences in local NVM storage, last search technique, and power-up sequence preferences include a preference for a CAG or SNPN. In another example, the WTRU camp state may include a PLMN state or an SNPN state. Furthermore, loss of coverage may include an out-of-coverage scenario. In an additional example, the user preference may be received via a manual user request for localized service. Furthermore, in an example, the validity condition may include one or more of a time condition, a location condition, and a duration condition. BRIEF DESCRIPTION OF THE DRAWINGS

[0008] The present invention may be understood in more detail from the following description given by way of example with reference to the accompanying drawings, in which like reference numerals represent like elements, and in which:

[0009] Figure 1A is a system diagram illustrating an exemplary communication system in which one or more disclosed embodiments may be implemented;

[0010] Figure 1B is a diagram showing that the Figure 1A A system diagram of an exemplary wireless transmit / receive unit (WTRU) for use within the illustrated communication system;

[0011] Figure 1C It is shown that according to the embodiment, Figure 1A A system diagram of an exemplary radio access network (RAN) and an exemplary core network (CN) for use within a communication system as shown in FIG.

[0012] Figure 1D It is shown that according to the embodiment, Figure 1A A system diagram of another exemplary RAN and another exemplary CN used in the communication system shown in FIG;

[0013] Figure 2 is a flow chart illustrating an example of an automatic mode of operation for managed network selection;

[0014] Figure 3 is a flow chart illustrating an example of a method of operation for managed network selection;

[0015] Figure 4 is a flow chart illustrating an example of a Closed Access Group (CAG) and Standalone Non-Public Network (SNPN) selection process; and

[0016] Figure 5 is a flow chart illustrating an example of a manual hosted network search and selection process. DETAILED DESCRIPTION

[0017] Figure 1Ais a diagram illustrating an exemplary communication system 100 in which one or more disclosed embodiments may be implemented. The communication system 100 may be a multiple access system that provides content, such as voice, data, video, messaging, broadcast, etc., to multiple wireless users. The communication system 100 may enable multiple wireless users to access such content by sharing system resources, including wireless bandwidth. For example, the communication system 100 may employ one or more channel access methods, such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), single carrier FDMA (SC-FDMA), zero tail unique word discrete Fourier transform spread OFDM (ZT-UW-DFT-S-OFDM), unique word OFDM (UW-OFDM), resource block filtered OFDM, filter bank multi-carrier (FBMC), etc.

[0018] like Figure 1A As shown, the communication system 100 may include wireless transmit / receive units (WTRUs) 102a, 102b, 102c, 102d, a radio access network (RAN) 104, a core network (CN) 106, a public switched telephone network (PSTN) 108, the internet 110, and other networks 112. However, it will be appreciated that the disclosed embodiments contemplate any number of WTRUs, base stations, networks, and / or network elements. Each of the WTRUs 102a, 102b, 102c, 102d may be any type of device configured to operate and / or communicate in a wireless environment. By way of example, the WTRUs 102a, 102b, 102c, 102d (any of which may be referred to as a station (STA)) may be configured to transmit and / or receive wireless signals and may include user equipment (UE), a mobile station, a fixed or mobile subscriber unit, a subscription-based unit, a pager, a cellular phone, a personal digital assistant (PDA), a smartphone, a laptop, a netbook, a personal computer, a wireless sensor, a hotspot or Mi-Fi device, an Internet of Things (IoT) device, a watch or other wearable device, a head-mounted display (HMD), a vehicle, a drone, medical equipment and applications (e.g., remote surgery), industrial equipment and applications (e.g., robots and / or other wireless devices operating in industrial and / or automated process chain environments), consumer electronic devices, devices operating on commercial and / or industrial wireless networks, etc. Any of the WTRUs 102a, 102b, 102c, and 102d may be interchangeably referred to as a UE.

[0019] The communication system 100 may also include a base station 114a and / or a base station 114b. Each of the base stations 114a, 114b may be any type of device configured to wirelessly connect to at least one of the WTRUs 102a, 102b, 102c, 102d to facilitate access to one or more communication networks, such as the CN 106, the internet 110, and / or other networks 112. By way of example, the base stations 114a, 114b may be a base transceiver station (BTS), a Node B (NodeB), an eNode B (eNB), a Home Node B, a Home eNode B, a next generation Node B such as a gNode B (gNB), a New Radio (NR) Node B, a site controller, an access point (AP), a wireless router, and the like. While the base stations 114a, 114b are each depicted as a single element, it will be appreciated that the base stations 114a, 114b may include any number of interconnected base stations and / or network elements.

[0020] Base station 114a may be part of RAN 104, which may also include other base stations and / or network elements (not shown), such as a base station controller (BSC), a radio network controller (RNC), relay nodes, etc. Base station 114a and / or base station 114b may be configured to transmit and / or receive wireless signals on one or more carrier frequencies, which may be referred to as cells (not shown). These frequencies may be in licensed spectrum, unlicensed spectrum, or a combination of licensed and unlicensed spectrum. A cell may provide wireless service coverage to a specific geographic area, which may be relatively fixed or may change over time. A cell may be further divided into cell sectors. For example, the cell associated with base station 114a may be divided into three sectors. Thus, in one embodiment, base station 114a may include three transceivers, one for each sector of the cell. In an embodiment, base station 114a may employ multiple-input, multiple-output (MIMO) technology and may use multiple transceivers for each sector of the cell. For example, beamforming may be used to transmit and / or receive signals in a desired spatial direction.

[0021] The base stations 114a, 114b may communicate with one or more of the WTRUs 102a, 102b, 102c, 102d over an air interface 116, which may be any suitable wireless communication link (e.g., radio frequency (RF), microwave, centimeter wave, micrometer wave, infrared (IR), ultraviolet (UV), visible light, etc.). The air interface 116 may be established using any suitable radio access technology (RAT).

[0022] More specifically, as described above, the communication system 100 may be a multiple-access system and may employ one or more channel access schemes, such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, and the like. For example, the base station 114a in the RAN 104 and the WTRUs 102a, 102b, 102c may implement a radio technology such as Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA), which may use Wideband CDMA (WCDMA) to establish the air interface 116. WCDMA may include communication protocols such as High Speed ​​Packet Access (HSPA) and / or Evolved HSPA (HSPA+). HSPA may include High Speed ​​Downlink (DL) Packet Access (HSDPA) and / or High Speed ​​Uplink (UL) Packet Access (HSUPA).

[0023] In an embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement a radio technology such as Evolved UMTS Terrestrial Radio Access (E-UTRA), which may establish the air interface 116 using Long Term Evolution (LTE) and / or LTE-Advanced (LTE-A) and / or LTE-Advanced Pro (LTE-APro).

[0024] In an embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement a radio technology such as NR radio access and may establish the air interface 116 using NR.

[0025] In an embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement multiple radio access technologies. For example, the base station 114a and the WTRUs 102a, 102b, 102c may simultaneously implement LTE radio access and NR radio access, for example, using dual connectivity (DC) principles. Thus, the air interface used by the WTRUs 102a, 102b, 102c may be characterized by multiple types of radio access technologies and / or transmissions to / from multiple types of base stations, such as eNBs and gNBs.

[0026] In other embodiments, the base station 114a and the WTRUs 102a, 102b, 102c may implement radio technologies such as IEEE 802.11 (i.e., Wireless Fidelity (WiFi), IEEE 802.16 (i.e., Worldwide Interoperability for Microwave Access (WiMAX)), CDMA2000, CDMA2000 1X, CDMA2000 EV-DO, Interim Standard 2000 (IS-2000), Interim Standard 95 (IS-95), Interim Standard 856 (IS-856), Global System for Mobile communications (GSM), Enhanced Data rates for GSM Evolution (EDGE), GSM EDGE (GERAN), etc.

[0027] Figure 1A The base station 114b in the may be, for example, a wireless router, a Home Node B, a Home eNode B, or an access point, and may utilize any suitable RAT to facilitate wireless connectivity in a local area, such as a place of business, a home, a vehicle, a campus, an industrial facility, an air corridor (e.g., for use by drones), a road, and the like. In one embodiment, the base station 114b and the WTRUs 102c, 102d may implement a radio technology such as IEEE 802.11 to establish a wireless local area network (WLAN). In an embodiment, the base station 114b and the WTRUs 102c, 102d may implement a radio technology such as IEEE 802.15 to establish a wireless personal area network (WPAN). In yet another embodiment, the base station 114b and the WTRUs 102c, 102d may utilize a cellular-based RAT (e.g., WCDMA, CDMA2000, GSM, LTE-APro, NR, etc.) to establish a picocell or a femtocell. As Figure 1A As shown, the base station 114b may have a direct connection to the internet 110. Therefore, the base station 114b may not need to access the internet 110 via the CN 106.

[0028] The RAN 104 may be in communication with the CN 106, which may be any type of network configured to provide voice, data, applications, and / or Voice over Internet Protocol (VoIP) services to one or more of the WTRUs 102a, 102b, 102c, 102d. Data may have differentiated quality of service (QoS) requirements, such as different throughput requirements, latency requirements, fault tolerance requirements, reliability requirements, data throughput requirements, mobility requirements, etc. The CN 106 may provide call control, billing services, mobile location-based services, prepaid calling, internet connectivity, video distribution, etc., and / or perform advanced security functions, such as user authentication. Although in Figure 1AAlthough not shown, it will be appreciated that the RAN 104 and / or the CN 106 may be in direct or indirect communication with other RANs that employ the same RAT as the RAN 104 or a different RAT as the RAN 104. For example, in addition to being connected to the RAN 104, which may utilize NR radio technology, the CN 106 may also be in communication with another RAN (not shown) that employs GSM, UMTS, CDMA2000, WiMAX, E-UTRA, or WiFi radio technology.

[0029] The CN 106 may also serve as a gateway for the WTRUs 102a, 102b, 102c, 102d to access the PSTN 108, the internet 110, and / or other networks 112. The PSTN 108 may include a circuit-switched telephone network that provides plain old telephone service (POTS). The internet 110 may include a global system of interconnected computer networks and devices that use common communication protocols, such as the Transmission Control Protocol (TCP), the User Datagram Protocol (UDP), and / or the Internet Protocol (IP) from the TCP / IP internet protocol suite. The networks 112 may include wired and / or wireless communication networks owned and / or operated by other service providers. For example, the networks 112 may include another CN connected to one or more RANs, which may employ the same RAT as the RAN 104 or a different RAT.

[0030] Some or all of the WTRUs 102a, 102b, 102c, 102d in the communication system 100 may include multi-mode capabilities (e.g., the WTRUs 102a, 102b, 102c, 102d may include multiple transceivers for communicating with different wireless networks via different wireless links). Figure 1A The WTRU 102c shown may be configured to communicate with the base station 114a, which may employ a cellular-based radio technology, and with the base station 114b, which may employ an IEEE 802 radio technology.

[0031] Figure 1B is a system diagram illustrating an exemplary WTRU 102. Figure 1B As shown, the WTRU 102 may include, among other things, a processor 118, a transceiver 120, a transmit / receive element 122, a speaker / microphone 124, a keypad 126, a display / touchpad 128, non-removable memory 130, removable memory 132, a power supply 134, a global positioning system (GPS) chipset 136, and / or other peripherals 138. It will be appreciated that the WTRU 102 may include any subcombination of the foregoing elements while remaining consistent with an embodiment.

[0032] The processor 118 may be a general purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors associated with a DSP core, a controller, a microcontroller, an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), any other type of integrated circuit (IC), a state machine, etc. The processor 118 may perform signal coding, data processing, power control, input / output processing, and / or any other functionality that enables the WTRU 102 to operate in a wireless environment. The processor 118 may be coupled to the transceiver 120, which may be coupled to the transmit / receive element 122. Although Figure 1B The processor 118 and the transceiver 120 are depicted as separate components, but it will be appreciated that the processor 118 and the transceiver 120 may be integrated together in an electronic package or chip.

[0033] The transmit / receive element 122 may be configured to transmit signals to or receive signals from a base station (e.g., base station 114a) via the air interface 116. For example, in one embodiment, the transmit / receive element 122 may be an antenna configured to transmit and / or receive RF signals. In an embodiment, the transmit / receive element 122 may be an emitter / detector configured to transmit and / or receive, for example, IR, UV, or visible light signals. In another embodiment, the transmit / receive element 122 may be configured to transmit and / or receive both RF and light signals. It will be appreciated that the transmit / receive element 122 may be configured to transmit and / or receive any combination of wireless signals.

[0034] Although the transmit / receive element 122 is Figure 1B Although depicted as a single element in the embodiment, the WTRU 102 may include any number of transmit / receive elements 122. More specifically, the WTRU 102 may employ MIMO technology. Thus, in one embodiment, the WTRU 102 may include two or more transmit / receive elements 122 (e.g., multiple antennas) for transmitting and receiving wireless signals over the air interface 116.

[0035] The transceiver 120 may be configured to modulate signals to be transmitted by the transmit / receive element 122 and demodulate signals received by the transmit / receive element 122. As described above, the WTRU 102 may have multi-mode capabilities. Thus, the transceiver 120 may include multiple transceivers to enable the WTRU 102 to communicate via multiple RATs (e.g., NR and IEEE 802.11).

[0036] The processor 118 of the WTRU 102 may be coupled to and may receive user input data from a speaker / microphone 124, a keypad 126, and / or a display / touchpad 128 (e.g., a liquid crystal display (LCD) display unit or an organic light emitting diode (OLED) display unit). The processor 118 may also output user data to the speaker / microphone 124, the keypad 126, and / or the display / touchpad 128. Furthermore, the processor 118 may access information from and store data in any suitable type of memory, such as non-removable memory 130 and / or removable memory 132. The non-removable memory 130 may include random access memory (RAM), read-only memory (ROM), a hard disk, or any other type of memory storage device. The removable memory 132 may include a subscriber identity module (SIM) card, a memory stick, a secure digital (SD) memory card, or the like. In other embodiments, the processor 118 may access information from and store data in memory that is not physically located on the WTRU 102, such as on a server or a home computer (not shown).

[0037] The processor 118 may receive power from the power source 134 and may be configured to distribute and / or control power to the other components in the WTRU 102. The power source 134 may be any suitable device for powering the WTRU 102. For example, the power source 134 may include one or more dry cell batteries (e.g., nickel-cadmium (NiCd), nickel-zinc (NiZn), nickel-metal hydride (NiMH), lithium-ion (Li-ion), etc.), solar cells, fuel cells, etc.

[0038] The processor 118 may also be coupled to the GPS chipset 136, which may be configured to provide location information (e.g., longitude and latitude) regarding the current location of the WTRU 102. In addition to or in lieu of the information from the GPS chipset 136, the WTRU 102 may receive location information from a base station (e.g., base stations 114a, 114b) over the air interface 116 and / or determine its location based on the timing of signals received from two or more neighboring base stations. It will be appreciated that the WTRU 102 may acquire location information using any suitable location-determination method while remaining consistent with the embodiments.

[0039] The processor 118 may also be coupled to other peripherals 138, which may include one or more software and / or hardware modules that provide additional features, functionality, and / or wired or wireless connectivity. For example, the peripherals 138 may include an accelerometer, an electronic compass, a satellite transceiver, a digital camera (for photos and / or video), a universal serial bus (USB) port, a vibration device, a television transceiver, a hands-free headset, Module, frequency modulation (FM) radio unit, digital music player, media player, video game player module, Internet browser, virtual reality and / or augmented reality (VR / AR) device, activity tracker, etc. Peripheral device 138 may include one or more sensors. The sensor may be one or more of a gyroscope, an accelerometer, a Hall effect sensor, a magnetometer, an orientation sensor, a proximity sensor, a temperature sensor, a time sensor, a geolocation sensor, an altimeter, a light sensor, a touch sensor, a magnetometer, a barometer, a gesture sensor, a biometric sensor, a humidity sensor, etc.

[0040] The WTRU 102 may include a full-duplex radio for which transmission and reception of some or all signals (e.g., associated with particular subframes used for both UL (e.g., for transmission) and DL (e.g., for reception)) may be simultaneous and / or concurrent. The full-duplex radio may include an interference management unit 139 to reduce and / or substantially eliminate self-interference through hardware (e.g., a choke) or through signal processing by a processor (e.g., a separate processor (not shown) or through the processor 118). In an embodiment, the WTRU 102 may include a half-duplex radio for which transmission and reception of some or all signals (e.g., associated with particular subframes used for either UL (e.g., for transmission) or DL ​​(e.g., for reception)) may be simultaneous and / or concurrent.

[0041] Figure 1C 1 is a system diagram illustrating the RAN 104 and the CN 106 according to an embodiment. As noted above, the RAN 104 may employ E-UTRA radio technology to communicate with the WTRUs 102a, 102b, 102c over the air interface 116. The RAN 104 may also be in communication with the CN 106.

[0042] The RAN 104 may include eNode-Bs 160a, 160b, and 160c, though it will be appreciated that the RAN 104 may include any number of eNode-Bs while remaining consistent with an embodiment. The eNode-Bs 160a, 160b, and 160c may each include one or more transceivers for communicating with the WTRUs 102a, 102b, and 102c over the air interface 116. In one embodiment, the eNode-Bs 160a, 160b, and 160c may implement MIMO technology. Thus, for example, the eNode-B 160a may use multiple antennas to transmit wireless signals to and / or receive wireless signals from the WTRU 102a.

[0043] 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, user scheduling in the UL and / or DL, etc. Figure 1C As shown in , eNode-Bs 160a, 160b, 160c may communicate with each other via an X2 interface.

[0044] Figure 1C The CN 106 shown in FIG may include a mobility management entity (MME) 162, a serving gateway (SGW) 164, and a packet data network (PDN) gateway (PGW) 166. Although the foregoing elements are depicted as part of the CN 106, it will be appreciated that any of these elements may be owned and / or operated by an entity other than the CN operator.

[0045] The MME 162 may be connected to each of the eNode-Bs 162a, 162b, 162c in the RAN 104 via an S1 interface and may serve as a control node. For example, the MME 162 may be responsible for authenticating users of the WTRUs 102a, 102b, 102c during an initial attach of the WTRUs 102a, 102b, 102c, bearer activation / deactivation, selecting a particular serving gateway, and the like. The MME 162 may also provide a control plane function for switching between the RAN 104 and other RANs (not shown) that employ other radio technologies, such as GSM and / or WCDMA.

[0046] The SGW 164 may be connected to each of the eNode-Bs 160a, 160b, 160c in the RAN 104 via an S1 interface. The SGW 164 may generally route and forward user data packets to and from the WTRUs 102a, 102b, 102c. The SGW 164 may also perform other functions, such as anchoring the user plane during inter-eNode B handovers, triggering paging when the WTRUs 102a, 102B, 102c have downlink data, managing and storing the context of the WTRUs 102a, 102B, 102c, and the like.

[0047] The SGW 164 may be connected to the PGW 166, which may provide the WTRUs 102a, 102b, 102c with access to packet-switched networks, such as the internet 110, to facilitate communications between the WTRUs 102a, 102b, 102c and IP-enabled devices.

[0048] The CN 106 may facilitate communications with other networks. For example, the CN 106 may provide the WTRUs 102a, 102b, 102c with access to circuit-switched networks, such as the PSTN 108, to facilitate communications between the WTRUs 102a, 102b, 102c and traditional land-line communications devices. For example, the CN 106 may include, or may be in communication with, an IP gateway (e.g., an IP Multimedia Subsystem (IMS) server) that serves as an interface between the CN 106 and the PSTN 108. In addition, the CN 106 may provide the WTRUs 102a, 102b, 102c with access to other networks 112, which may include other wired and / or wireless networks owned and / or operated by other service providers.

[0049] Although the WTRU Figures 1A-1D Although described as a wireless terminal, it is contemplated that in certain representative embodiments such a terminal may employ (eg, temporarily or permanently) a wired communication interface with a communication network.

[0050] In a representative embodiment, the other network 112 may be a WLAN.

[0051] A WLAN in infrastructure basic service set (BSS) mode may have an access point (AP) for the BSS and one or more stations (STAs) associated with the AP. The AP may have access to or an interface to a distribution system (DS) or another type of wired / wireless network that carries traffic entering and / or leaving the BSS. Traffic originating from outside the BSS and directed to a STA may reach the AP and be delivered to the STA. Traffic originating from a STA and directed to a destination outside the BSS may be sent to the AP for delivery to the corresponding destination. Traffic between STAs within a BSS may be sent through the AP, for example, where a source STA may send traffic to the AP, and the AP may deliver traffic to the destination STA. Traffic between STAs within a BSS may be considered and / or referred to as peer-to-peer traffic. Peer-to-peer traffic may be sent between a source and destination STA (e.g., directly between the source and destination STAs) using direct link setup (DLS). In certain representative embodiments, DLS may use 802.11e DLS or 802.11z tunneled DLS (TDLS). A WLAN using an independent BSS (IBSS) mode may not have an AP, and STAs (eg, all STAs) within or using the IBSS may communicate directly with each other. The IBSS communication mode may sometimes be referred to herein as an "ad-hoc" communication mode.

[0052] When using 802.11ac infrastructure operation mode or a similar operation mode, the AP can transmit beacons on a fixed channel (e.g., a primary channel). The primary channel can be a fixed width (e.g., a 20 MHz wide bandwidth) or a dynamically set width. The primary channel can be the operating channel of the BSS and can be used by STAs to establish a connection with the AP. In certain representative embodiments, for example, carrier sense multiple access with collision avoidance (CSMA / CA) can be implemented in an 802.11 system. For CSMA / CA, STAs (e.g., each STA) including the AP can sense the primary channel. If a particular STA senses / detects and / or determines that the primary channel is busy, the particular STA can back off. One STA (e.g., only one station) can transmit at any given time in a given BSS.

[0053] High throughput (HT) STAs may communicate using a 40 MHz wide channel, for example, by combining a primary 20 MHz channel with adjacent or non-adjacent 20 MHz channels to form a 40 MHz wide channel.

[0054] Very high throughput (VHT) STAs can support 20MHz, 40MHz, 80MHz and / or 160MHz wide channels. 40MHz and / or 80MHz channels can be formed by combining consecutive 20MHz channels. A 160MHz channel can be formed by combining 8 consecutive 20MHz channels or by combining two discontinuous 80MHz channels, which can be referred to as an 80+80 configuration. For the 80+80 configuration, after channel coding, the data can pass through a segment parser that can divide the data into two streams. Each stream can be subjected to inverse fast Fourier transform (IFFT) processing and time domain processing respectively. The stream can be mapped onto two 80MHz channels, and the data can be sent by the transmitting STA. At the receiver of the receiving STA, the operation of the above-mentioned 80+80 configuration can be reversed, and the combined data can be sent to the medium access control (MAC).

[0055] 802.11af and 802.11ah support operating modes below 1 GHz. The channel operating bandwidth and carriers in 802.11af and 802.11ah are reduced relative to the channel operating bandwidth and carriers used in 802.11n and 802.11ac. 802.11af supports 5 MHz, 10 MHz, and 20 MHz bandwidths in the TV White Space (TVWS) spectrum, while 802.11ah supports 1 MHz, 2 MHz, 4 MHz, 8 MHz, and 16 MHz bandwidths using non-TVWS spectrum. According to a representative embodiment, 802.11ah can support meter type control / machine type communication (MTC), such as MTC devices in macro coverage areas. MTC devices may have certain capabilities, for example, including limited capabilities to support (e.g., only support) certain and / or limited bandwidths. MTC devices may include batteries with a battery life above a threshold (e.g., to maintain very long battery life).

[0056] WLAN systems can support multiple channels and channel bandwidths, such as 802.11n, 802.11ac, 802.11af, and 802.11ah, including channels that can be designated as primary channels. The bandwidth of the primary channel can be equal to the maximum common operating bandwidth supported by all STAs in the BSS. The bandwidth of the primary channel can be set and / or limited by the STA that supports the smallest bandwidth operating mode among all STAs operating in the BSS. In the example of 802.11ah, for STAs that support (e.g., only support) 1 MHz mode (e.g., MTC-type devices), the primary channel can be 1 MHz wide, even if the AP and other STAs in the BSS support 2 MHz, 4 MHz, 8 MHz, 16 MHz, and / or other channel bandwidth operating modes. Carrier sensing and / or network allocation vector (NAV) settings can depend on the status of the primary channel. If the primary channel is busy, for example, because a STA (which only supports 1 MHz operating mode) is transmitting to the AP, all available frequency bands can be considered busy, even if most of the available frequency bands remain idle.

[0057] In the United States, 802.11ah can be used in the frequency band from 902 MHz to 928 MHz. In South Korea, the frequency band is from 917.5 MHz to 923.5 MHz. In Japan, the frequency band is from 916.5 MHz to 927.5 MHz. Depending on the country code, the total bandwidth available for 802.11ah ranges from 6 MHz to 26 MHz.

[0058] Figure 1D1 is a system diagram illustrating the RAN 104 and the CN 106 according to an embodiment. As described above, the RAN 104 may employ NR wireless technology to communicate with the WTRUs 102a, 102b, 102c over the air interface 116. The RAN 104 may also be in communication with the CN 106.

[0059] The RAN 104 may include gNBs 180a, 180b, and 180c, though it will be appreciated that the RAN 104 may include any number of gNBs while remaining consistent with an embodiment. Each of the gNBs 180a, 180b, and 180c may include one or more transceivers for communicating with the WTRUs 102a, 102b, and 102c over the air interface 116. In one embodiment, the gNBs 180a, 180b, and 180c may implement MIMO technology. For example, the gNBs 180a and 180b may utilize beamforming to transmit and / or receive signals to and from the gNBs 180a, 180b, and 180c. Thus, the gNB 180a may, for example, use multiple antennas to transmit and / or receive wireless signals to and from the WTRU 102a. In one embodiment, the gNBs 180a, 180b, and 180c may implement carrier aggregation technology. For example, the gNB 180a may transmit multiple component carriers (not shown) to the WTRU 102a. A subset of these component carriers may be on unlicensed spectrum, while the remaining component carriers may be on licensed spectrum. In an embodiment, the gNBs 180a, 180b, and 180c may implement coordinated multi-point transmission (CoMP). For example, the WTRU 102a may receive coordinated transmissions from both gNB 180a and gNB 180b (and / or gNB 180c).

[0060] The WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c using transmissions associated with scalable parameter sets. For example, the OFDM symbol spacing and / or OFDM subcarrier spacing may vary for different transmissions, different cells, and / or different portions of the wireless transmission spectrum. The WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c using subframes or transmission time intervals (TTIs) of varying or scalable lengths (e.g., containing different numbers of OFDM symbols and / or lasting for different absolute time lengths).

[0061] The gNBs 180a, 180b, 180c may be configured to communicate with the WTRUs 102a, 102b, 102c in a standalone configuration and / or a non-standalone configuration. In a standalone configuration, the WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c without also accessing another RAN (e.g., such as the eNode-Bs 160a, 160b, 160c). In a standalone configuration, the WTRUs 102a, 102b, 102c may utilize one or more of the gNBs 180a, 180b, 180c as mobility anchor points. In a standalone configuration, the WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c using signals in an unlicensed band. In a non-standalone configuration, the WTRUs 102a, 102b, 102c may communicate / connect with the gNBs 180a, 180b, 180c while also communicating / connecting with another RAN, such as the eNode-Bs 160a, 160b, 160c. For example, the WTRUs 102a, 102b, 102c may implement the DC principle to communicate with one or more gNBs 180a, 180b, 180c and one or more eNode-Bs 160a, 160b, 160c substantially simultaneously. In a non-standalone configuration, the eNode-Bs 160a, 160b, 160c may serve as mobility anchors for the WTRUs 102a, 102b, 102c, and the gNBs 180a, 180b, 180c may provide additional coverage and / or throughput for the serving WTRUs 102a, 102b, 102c.

[0062] Each of the gNBs 180a, 180b, 180c may be associated with a specific cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, user scheduling in UL and / or DL, support for network slicing, interworking between DC, NR, and E-UTRA, routing user plane data to a user plane function (UPF) 184a, 184b, routing control plane information to an access and mobility management function (AMF) 182a, 182b, etc. Figure 1D As shown, gNBs 180a, 180b, and 180c can communicate with each other via the Xn interface.

[0063] Figure 1DThe CN 106 shown in FIG may include at least one AMF 182 a, 182 b, at least one UPF 184 a, 184 b, at least one session management function (SMF) 183 a, 183 b, and may include a data network (DN) 185 a, 185 b. Although the aforementioned elements are depicted as part of the CN 106, it will be understood that any of these elements may be owned and / or operated by an entity other than the CN operator.

[0064] The AMF 182a, 182b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 104 via the N2 interface and may act as a control node. For example, the AMF 182a, 182b may be responsible for authenticating users of the WTRU 102a, 102b, 102c, supporting network slicing (e.g., handling different protocol data unit (PDU) sessions with different requirements), selecting a specific SMF 183a, 183b, managing registration areas, terminating non-access stratum (NAS) signaling, mobility management, and the like. The AMF 182a, 182b may use network slicing to customize CN support for the WTRU 102a, 102b, 102c based on the type of service being used by the WTRU 102a, 102b, 102c. For example, different network slices may be established for different use cases, such as services relying on ultra-reliable low latency (URLLC) access, services relying on enhanced massive mobile broadband (eMBB) access, and services used for MTC access. The AMF 182a, 182b may provide a control plane function for switching between the RAN 104 and other RANs (not shown) that employ other radio technologies (e.g., LTE, LTE-A, LTE-APro) and / or non-3GPP access technologies (e.g., WiFi).

[0065] The SMFs 183a and 183b can connect to the AMFs 182a and 182b in the CN 106 via the N11 interface. The SMFs 183a and 183b can also connect to the UPFs 184a and 184b in the CN 106 via the N4 interface. The SMFs 183a and 183b can select and control the UPFs 184a and 184b and configure the routing of traffic passing through the UPFs 184a and 184b. The SMFs 183a and 183b can also perform other functions, such as managing and allocating UE IP addresses, managing PDU sessions, controlling policy enforcement and QoS, and providing DL data notifications. The PDU session type can be IP-based, non-IP-based, Ethernet-based, and so on.

[0066] The UPF 184a, 184b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 104 via the N3 interface. This may provide the WTRUs 102a, 102b, 102c with access to packet-switched networks, such as the internet 110, to facilitate communications between the WTRUs 102a, 102b, 102c and IP-enabled devices. The UPF 184, 184b may perform other functions, such as routing and forwarding packets, enforcing user plane policies, supporting multi-homed PDU sessions, handling user plane QoS, buffering DL packets, providing mobility anchoring, and the like.

[0067] The CN 106 may facilitate communications with other networks. For example, the CN 106 may include, or may communicate with, an IP gateway (e.g., an IP Multimedia Subsystem (IMS) server) that serves as an interface between the CN 106 and the PSTN 108. Furthermore, the CN 106 may provide the WTRUs 102a, 102b, 102c with access to other networks 112, which may include other wired and / or wireless networks owned and / or operated by other service providers. In one embodiment, the WTRUs 102a, 102b, 102c may connect to the local DN 185a, 185b through the UPF 184a, 184b via the N3 interface to the UPF 184a, 184b and the N6 interface between the UPF 184a, 184b and the DN 185a, 185b.

[0068] Given that Figures 1A to 1D and pair Figures 1A to 1D

[0015] As described herein, one or more, or all, of the functionality described herein with respect to one or more of the following may be performed by one or more emulated devices (not shown): the WTRUs 102a to 102d, the base stations 114a to 114b, the eNode-Bs 160a to 160c, the MME 162, the SGW 164, the PGW 166, the gNBs 180a to 180c, the AMFs 182a to 182b, the UPFs 184a to 184b, the SMFs 183a to 183ab, the DNs 185a to 185b, and / or any other devices described herein. The emulated devices may be one or more devices configured to emulate one or more, or all, of the functionality described herein. For example, the emulated devices may be used to test other devices and / or simulate network and / or WTRU functionality.

[0069] Emulation devices can be designed to implement one or more tests on other devices in a laboratory environment and / or in a carrier network environment. For example, one or more emulation devices can perform one or more or all functions while being fully or partially implemented and / or deployed as part of a wired and / or wireless communication network in order to test other devices within the communication network. One or more emulation devices can perform one or more or all functions while being temporarily implemented / deployed as part of a wired and / or wireless communication network. The emulation device can be directly coupled to another device for testing and / or can use over-the-air wireless communication to perform testing.

[0070] One or more simulation devices can perform one or more functions (including all functions) without being implemented / deployed as part of a wired and / or wireless communication network. For example, the simulation device can be used in a test scenario in a test lab and / or a non-deployed (e.g., testing) wired and / or wireless communication network to enable testing of one or more components. The one or more simulation devices can be test devices. The simulation device can use direct RF coupling and / or wireless communication via RF circuitry (e.g., which can include one or more antennas) to send and / or receive data.

[0071] A non-public network (NPN) is a fifth-generation mobile phone system (5GS) deployed for non-public purposes. An NPN can be either a standalone non-public network (SNPN) or a public network-integrated NPN (PNI-NPN). An SNPN is operated by an NPN operator and does not rely on the network functionality provided by a public land mobile network (PLMN). A PNI-NPN is a non-public network deployed with PLMN support.

[0072] NPN is intended for use by private entities such as enterprises, factories, warehouses, etc. SNPN may be identified by a combination of a PLMN identifier (ID) and a network ID (NID), where the PLMN ID may be, for example, a PLMN ID reserved for private networks, e.g., with Mobile Country Code = 999.

[0073] The architecture of the 5G SNPN is based on the architecture of the 5G system. The NG-RAN broadcasts a combination of the PLMN ID and the NID for the SNPN. A WTRU operating in SNPN access mode reads the broadcast system information for available SNPNs, such as the PLMN ID, NID, or both, and selects the SNPN for which it has subscription and credentials.

[0074] A PNI-NPN is a non-public network that is made available using PLMN infrastructure / resources (e.g., PLMN network slices). The group of PLMN users that are allowed to access a certain PNI-NPN is called a Closed Access Group (CAG), and the CAG is identified by a CAG identifier. CAG users can only access a PNI-NPN from a cell that supports CAG access (called a "CAG cell"). A CAG cell broadcasts a list of CAG identifiers that it supports. A CAG WTRU is configured by the network to have a list of CAGs that it can access (allowed CAG list). When a CAG WTRU detects a CAG cell, it can only select / access that CAG cell if at least one of the broadcasted CAG identifiers matches a CAG identifier in its allowed CAG list.

[0075] In some cases, small cell networks can be deployed to provide services to local users within a specific area. For example, a temporary, non-public cellular network can be established to provide streaming video services to spectators at a live concert or football game. As another example, in places where large crowds may gather, such as airports, shopping malls, and campuses, small cell networks can be deployed to provide localized services, such as commercial advertisements in shopping malls. The services provided by these small cell networks have two basic characteristics: first, the services are localized, meaning they are related to activities / events in a certain location or area and are generally limited to users in that area; second, users do not use these services on a regular basis, but are likely to use them on an on-demand or ad hoc basis.

[0076] 3GPP is studying how to enhance the 5G system to provide such localized services and enable users to access hosting networks that provide these services in one or more 3GPP study projects. As used herein, those localized services may be referred to as "Providing Access to Localized Services (PALS) services" or "localized services," and a network that provides PALS services may be referred to as a "PALS network," "PALS hosting network," or simply "hosting network."

[0077] In the embodiments and examples provided herein, the hosted network may be a SNPN, a PNI-NPN, or a PLMN. The local service provider may be a hosted network operator or a third-party service provider.

[0078] The embodiments and examples provided herein address issues related to selecting a hosted network for accessing localized services. In an example, a WTRU may be enabled to discover, select, and access an NPN as a hosted network and receive localized services.

[0079] The WTRU may be provided with localized service information that includes one or any combination of the following: validity conditions (duration, time, and location), a hosted network ID, a list of prioritized hosted networks (for SNPN scenarios), or a list of allowed CAGs (for CAG scenarios). In an example, the localized service information may be provided to the WTRU via application data, an external configuration procedure, NAS signaling via a new WTRU policy, or the like.

[0080] When an end user desires to access a localized service and the availability conditions for the localized service are met, the WTRU may use the managed network selection information to initiate managed network selection. The details of the managed network selection process may be determined. The details of when the WTRU requires a new network selection mode to initiate managed network selection may be determined. Details regarding a priority list for managed network selection may be determined, including whether a new selection mode is required.

[0081] The following are queries and related issues that can be addressed with respect to searching and selecting a hosted network for accessing localized services. For example, how should the WTRU perform hosted network selection for a particular localized service. If the localized service is provided by both a CAG cell and a SNPN, how does the WTRU prioritize one hosted network over another. Additionally, if the localized service is provided by both a CAG cell and a SNPN, how does one handle a scenario where the search is unsuccessful on one technology, such as a CAG cell compared to a SNPN. How does the WTRU handle out-of-coverage scenarios. For example, if the WTRU loses coverage of a hosted network cell that provides access to a particular localized service, how does the WTRU regain access to the hosted network cell that provides access to the localized service. How does the WTRU handle automatic and manual hosted network selection modes. For example, how does the WTRU perform hosted network search and selection when operating in automatic or manual operation mode.

[0082] Localized services are time- and location-restricted services provided by a hosted network. The hosted network can be a SNPN, a Public-Non-Public Network Integrated Non-Public Network (PNI-NPN), or a PLMN. The local service provider can be the hosted network operator or a third-party service provider.

[0083] The embodiments and examples provided herein propose mechanisms and enhancements on how an end user / UE / WTRU will select a hosted network to obtain access to localized services at a specific location. The present invention also proposes how to optimize automatic and manual hosted network selection by defining new hosted network selection modes, 5GS assistance information, defining hosted network selection preferences via the Universal Subscriber Identity Module (USIM) basic profile, etc.

[0084] The embodiments and examples provided herein may be applied to one or more of enhanced non-public network (eNPN), SNPN or PNI-NPN (CAG) or 5G core network 3GPP service and system aspects (SA) / core network and terminal (CT). The embodiments and examples provided herein include defining a new hosted network selection mode (HNSM) for hosted network search and selection to obtain access to localized services. In addition, the embodiments and examples provided herein include a new basic USIM file to provide preferences for hosted network selection, such as CAG versus SNPN. In addition, the embodiments and examples provided herein include a 5GS or certificate holder (CH) that provides hosted network selection preference information via NAS signaling / user plane.

[0085] In addition, the embodiments and examples provided herein include the use of the following to determine the hosted network selection preference between CAG and SNPN at power-up, service interruption (coverage loss): local non-volatile memory (NVM) storage / power-up sequence configuration / WTRU residency state, such as PLMN versus SNPN; and last search technique, such as CAG versus SNPN hosted network. In addition, the embodiments and examples provided herein include situations where the hosted network search and selection is unsuccessful (automatic mode), and the WTRU can start a fallback timer, switch back to the previous WTRU mode, and when the fallback timer expires, return to the hosted network selection mode and start the hosted network search and selection. In addition, the embodiments and examples provided herein include continuous or intermediate reporting of the hosted network during manual hosted network selection mode.

[0086] The embodiments and examples provided herein include a hosted network selection mechanism that includes an automatic mode of operation. In an example, the WTRU may determine that it needs to access a localized service. For example, this may occur when the WTRU receives a request for a localized service from a user. In an example, the request for a localized service may be general or may be a request for a specific localized service identified by a localized service identifier. Furthermore, in an example, the request from the user may come from an application hosted by the WTRU, may be due to a validity condition being satisfied for the availability of a hosted network for the localized service, may be due to a periodic search for a hosted network when an earlier search was unsuccessful, or a combination of these. Additionally or alternatively, the WTRU may determine that it needs to access a localized service when the WTRU loses coverage of a hosted network cell on which it resides that is providing access to the localized service.

[0087] The embodiments and examples provided herein may be used with 3GPP access technologies, such as NR 5G, NR 5G Advanced, and the like. Additionally or alternatively, the embodiments and examples provided herein may be used in one or more proximity service (pro se) networks or sidelink communication networks. Furthermore, the embodiments and examples provided herein may be used with non-3GPP access technologies, such as WiFi. Furthermore, the embodiments and examples provided herein may be used to trigger a search, selection, or both for any type of network that provides localized services.

[0088] Additionally, the WTRU may enter a managed network selection mode. If necessary, the WTRU may request authorization from the 5GC. In an example, the authorization may be partial. For example, the 5GC may authorize a managed network service set. In another example, the authorization may be complete. For example, the WTRU may be authorized to access a complete set of localized services. This authorization request can be seen in the examples of the figures included elsewhere herein.

[0089] The WTRU may trigger a search for a hosted network. The starting point of the search (e.g., CAG or SNPN) may be based on one of the six proposed configuration methods as mentioned in the examples in the figures included elsewhere herein. In addition, the WTRU may start a search for a CAG or SNPN. The decision may be based on the results of the previous steps. In the example, the search may start from a CAG or SNPN, and the WTRU may be configured with a CAG that may provide access to localized services, a SNPN that is a hosted network, and one or more group IDs (GINs) for network selection, the CAGs may be configured via a list of allowed CAGs with validity conditions, and the SNPNs may be configured via a credential holder controlled priority list of preferred SNPNs, the GIN may be extended with time validity information for each entry in the list.

[0090] The result of the CAG or SNPN search may be the identity of a CAG cell or a SNPN ID. The WTRU will then attempt network registration via the identified CAG cell or will attempt to register with the identified SNPN.

[0091] The hosted network selection preference may be provided by the home network (home PLMN (HPLMN) / subscribed SNPN), a third-party localization service provider, a CH, or a visited PLMN (VPLMN). This information may be provided via NAS signaling. In an example, this information may be provided via signaling related to registration / WTRU configuration update, WTRU parameter update, WTRU policy delivery procedures, roaming guidance, etc. Additionally or alternatively, this information may be provided via the application layer on the user plane.

[0092] The WTRU may use other means to derive preferences and starting points for managed network search and selection. In an example, the WTRU may use user preferences stored in the NVM, the last search technique (CAG vs. SNPN), the power-up sequence preference (if the WTRU uses a power-up sequence), the WTRU's camped state (PLMN vs. SNPN), etc.

[0093] The embodiments and examples provided herein include a hosted network selection mechanism that includes a manual mode of operation. In an example, a WTRU may determine that it needs to access a localized service. This may occur when the WTRU receives a manual request for a localized service (either for a general service or for a specific localized service identified by a localized service identifier) ​​from a user (e.g., an application hosted by the WTRU).

[0094] The WTRU may enter a managed network selection mode. If necessary, authorization may be requested by the WTRU from the 5GC. In an example, the authorization may be partial. In an example, the 5GC may authorize a managed network service set. In another example, the authorization may be complete. For example, the WTRU may be authorized to access a complete set of localized services. This can be seen in the examples shown in one or more figures included elsewhere herein.

[0095] The WTRU may trigger a search for a hosted network. The starting point of the search (eg, CAG or SNPN) may be based on one of the six proposed configuration methods as seen in the examples shown in one or more figures herein.

[0096] The result of the CAG or SNPN search may be a report of available CAG or SNPN cells. The WTRU may report the found hosted networks to the user for selection. The mobile terminal (MT) portion of the WTRU may report the found networks to an application hosted by the WTRU. Reporting of the hosted networks to the user may be continuous, for example, reporting immediately when a hosted network is found / detected. Additionally or alternatively, the WTRU may report the hosted network after completing the search for one or both of the access technologies (CAG and SNPN).

[0097] A new or modified USIM basic file may include a hosted network selection preference, such as a CAG or SNPN, and this information may be linked to a localized service identifier. The hosted network selection preference may be provided by the home network (HPLMN / subscribed SNPN), a third-party localization service provider, a CH, or a VPLMN. This information may be provided via NAS signaling. In an example, this information may be provided via signaling related to registration / WTRU configuration update, WTRU parameter update, WTRU policy delivery procedures, roaming guidance, etc. Additionally or alternatively, this information may be provided via the application layer on the user plane.

[0098] The WTRU may use other means to derive preferences and starting points for managed network search and selection. In an example, the WTRU may use user preferences stored in the NVM, last search preferred technique (CAG vs. SNPN), power-up sequence preference (if the WTRU uses a power-up sequence), WTRU camped state (PLMN vs. SNPN), etc.

[0099] The embodiments and examples provided herein below include a managed network selection mechanism that includes an automatic mode of operation. In an example scenario where the WTRU operates in automatic mode for network selection, the WTRU will switch to the managed network selection mode based on criteria (time and location) and select an appropriate managed network to provide the WTRU with access to localized services.

[0100] Figure 2 is a flow chart illustrating an example of an automatic mode of operation for hosted network selection. The example shown in flow chart 200 includes selecting a hosted network for accessing localized services when the WTRU is operating in automatic network selection mode.

[0101] In steps 205, 210, the WTRU, operating in automatic network selection mode, successfully camps on a managed network cell. In the example shown in block 205, the WTRU camps on a managed network cell. Additionally or alternatively, in the example shown in block 210, the WTRU camps on a PLMN cell either normally or with restrictions.

[0102] In an example, the WTRU may have been configured with localized service information. This configuration may be done manually (e.g., via a graphical user interface (GUI)) or the WTRU may have received the localized service information from the network (e.g., in a NAS message). The MT portion of the WTRU may use an attention (AT) command to send the localized service information to an application hosted in the terminal equipment (TE) portion of the WTRU. The localized service information may also include a localized service identifier (LS_ID), a service type, or both.

[0103] In a further example, in step 1a 220, the WTRU may process a request for a localized service. The WTRU may receive a request for a localized service from a user. In an example, based on time and location criteria included in the localized service information, the MT portion of the WTRU may receive a request from an application in the TE portion of the WTRU to access one or more localized services. The request may be a general request rather than being specific to a particular localized service.

[0104] Another example scenario may be that a WTRU that has camped on a hosted network cell 205 loses coverage in step 1b 215. The coverage loss event 215 may be a trigger for the WTRU to find a hosted network cell to restore service and provide the WTRU with access to localized services, as described in more detail below.

[0105] In step 2 230, the WTRU enters HNSM. The rationale behind entering this mode is that the WTRU is now specifically looking for one or more hosted networks that can provide access to localized services. This step may also be optional. Optionally, entry into HNSM may be authorized by the home network (HPLMN) or subscribed SNPN, which may be pre-configured by the home network (HPLMN or subscribed SNPN) (e.g., in NVM / USIM file storage) or may be obtained through information exchange between the WTRU and the home network via NAS signaling. In an example, the NAS signaling may be one or more of a Directed Roaming (SoR), a registration / configuration update command, etc. In an example, home network authorization may be required at this stage for the WTRU to trigger the hosted network selection process.

[0106] The WTRU may initiate an authorization procedure with the HPLMN or subscribed SNPN. The purpose of this procedure is to obtain authorization and a token from the HPLMN or subscribed SNPN to access localized services. During the authorization procedure, the network may update the list of allowed CAGs / the priority list of SNPNs (along with validity conditions), or both. In addition, this newly configured information may take precedence over the WTRU's stored information.

[0107] In step 3 240, the WTRU may trigger the search. In an example, the trigger may be automatic. In an example, in this step, the WTRU may search for a hosted network, as the hosted network may be a SNPN or a PNI-NPN (CAG cell). In addition, the WTRU may need to determine a starting point for the search. The trigger and starting point of the search may be based on the configuration of the WTRU. Provided below are examples of criteria that the WTRU may use to determine a starting point for a hosted network search. Additionally or alternatively, the WTRU may use the following example criteria to determine whether to select a CAG or SNPN.

[0108] In an example regarding the first criterion (which may be considered criterion 1), the WTRU may store a new basic file in the USIM which may provide a preference for a hosted network, such as CAG versus SNPN. In addition, the information may also be indexed by the type of localized service (localized service ID). For example, for a localized gaming service, using a CAG cell is more preferred than an SNPN. In a comparative example, for the IMS, an SNPN as a hosted network providing access to localized services is more preferred than a CAG cell. The content of the basic file may be based on the CAG / SNPN preference information received from the network. The network may update the content of the USIM basic file via an over-the-air USIM Application Toolkit (USAT) REFRESH command. In an example, the USIM may exist for CAG search.

[0109] In a further example regarding a second criterion (which may be considered criterion 2), a user may have his or her own preferences that are configured via the GUI and stored locally in the WTRU's NVM storage. Criterion 2 may be considered a user configured criterion.

[0110] In another example involving the third criterion (which may be considered criterion 3), the selection of CAG or SNPN as the starting point may be based on a last search technique, such as a CAG or SNPN hosting network. Specifically, the WTRU will start the search using the last search technique. In the example scenario, the last access to the hosted network was via an SNPN, and a new request will trigger the WTRU to look for an SNPN on a CAG cell that provides access to localized services.

[0111] In an additional example involving the fourth criterion (which can be considered criterion 4), a preference (e.g., CAG vs. SNPN hosted network) can be automatically configured after the power-up sequence. This information can be based on user preferences or provided by the home network (HPLMN / subscribed SNPN), a third-party localization service provider, or both. Therefore, this criterion can be considered a power-up sequence preference.

[0112] In yet another example regarding the fifth criterion (which may be considered criterion 5), the preference may be based on information provided by one or more of the home network (e.g., HPLMN, subscribed SNPN, or both), a third-party localization service provider, a CH, or a VPLMN. This search preference information may be provided via NAS signaling. In an example, the NAS signaling may be one or more of registration signaling, a WTRU configuration update, a WTRU parameter update, a WTRU policy delivery procedure, a SoR, etc. In another example, the preference information may be provided via an application layer on the user plane. Furthermore, in an example, the preference information may be considered a preference value. Criterion 5 may be considered a search preference provided by the HPLMN / VPLMN / CH criteria.

[0113] In another example related to the sixth criterion (which may be considered criterion 6), the preference may be based on the WTRU's camping state, such as PLMN or SNPN. For example, a WTRU that is already camped on an SNPN may search for an SNPN hosting network before performing a handover to a CAG cell. Similarly, if the WTRU is camped on a PLMN, the WTRU will search for a CAG cell before performing a handover to an SNPN that provides access to localized services.

[0114] The criteria used to determine the search starting point can have associated priorities, and higher priority settings will take precedence over lower priority settings. In a specific example, criterion 2 can have a higher priority setting than criterion 5, and therefore, criterion 2 can take precedence over criterion 5; furthermore, criterion 5 can have a higher priority setting than criterion 4, and therefore, criterion 5 can take precedence over criterion 4; furthermore, criterion 4 can have a higher priority setting than criterion 1, and therefore, criterion 4 can take precedence over criterion 1; furthermore, criterion 1 can have a higher priority setting than criterion 3, and therefore, criterion 1 can take precedence over criterion 3; in another example, criterion 3 can have a higher priority setting than criterion 6, and therefore, criterion 3 can take precedence over criterion 6.

[0115] In another example considering the priorities defined in the above scenario, if criterion 2 (i.e., user-configured criterion) is not present in the WTRU, criterion 5 (i.e., search preference provided by HPLMN / VPLMN / CH criteria) will take the current highest priority because criterion 5 has the second highest priority after criterion 2. Therefore, the hosted network search starting point will be determined based on the configured criterion 5 (i.e., search preference provided by HPLMN / VPLMN / CH criteria). The new priority order may be, for example, criterion 5 precedes criterion 4, criterion 4 precedes criterion 1, criterion 1 precedes criterion 3, and criterion 3 precedes criterion 6, in order of highest to lowest priority.

[0116] In step 4250, based on the result of step 3240, the WTRU may make a decision to start searching from CAG (PNI-NPN) cells or from SNPN cells.

[0117] Once the decision is made as to which access technology (e.g., CAG or SNPN), the WTRU searches for the hosted network and then the WTRU may perform a search and selection process for the access technology. For example, if the WTRU decides that SNPN is the access technology, then the WTRU may perform an SNPN selection process in step 5a 260, which may also include a process for searching for an SNPN. Similarly, if the WTRU decides that CAG is the access technology, then the WTRU may perform a CAG selection process in step 5b 270, which may also include a process for searching for a CAG.

[0118] In an example, if the managed network selection process for the determined access technology is unsuccessful, the WTRU may fall back to another access technology. For example, if the WTRU determined the SNPN access technology at step 4 250, the WTRU will proceed to step 5a 260 and perform the SNPN selection process. If the WTRU subsequently does not successfully select the SNPN, the WTRU may then fall back to the CAG access technology and may perform the CAG selection process.

[0119] Similarly, if the WTRU decides on CAG access technology at step 4b250, the WTRU proceeds to step 5b270 and performs the CAG selection procedure. If the WTRU subsequently fails to successfully select CAG, the WTRU may then fall back to SNPN access technology and may perform the SNPN selection procedure.

[0120] In another example solution, the request to access the localized service may be for a specific localized service. In an example, accessing a specific or special localized service may include accessing a gaming service, a video streaming service, etc.

[0121] Figure 3 is a flow chart illustrating an example of a method of operation for hosted network selection. In the example shown in flow chart 300, the WTRU may trigger 320 a search for a hosted network based on one or more of: a request for localized service from a user, a periodic search, a loss of coverage, and satisfaction of one or more availability conditions for the localized service.

[0122] In addition, the WTRU may select 340 one of a CAG and a SNPN based on one or more of the USIM base file, user preferences in local NVM storage, a last search technique, a power-up sequence preference, a network-provided value, and the WTRU's resident state. Accordingly, the WTRU may then register 360 with the selected CAG or SNPN based on the selection of the CAG or SNPN.

[0123] In a further example, the WTRU may receive one or more of a USIM base file, a power-up sequence preference, or a value provided by the network in the configuration information. In another example, the network may be a HPLMN, a VPLMN, or a CH.

[0124] In a further example, one or more of the USIM base file, user preferences in local NVM storage, last search technique, and power-up sequence preferences include a preference for CAG or SNPN. In another example, the WTRU camp state may include a PLMN state or an SNPN state. Additionally, the coverage loss may include an out-of-coverage scenario.

[0125] In an additional example, the user preference may be received through a manual request by the user to the localization service.Furthermore, in an example, the validity condition may include one or more of a time condition, a location condition, and a duration condition.

[0126] Figure 4 is a flow chart showing an example of a CAG and SNPN selection process. As shown in the example of flow chart 400, Figure 2 The CAG and SNPN selection process of the embodiment of the present invention extends step 5a, step 5b or both. Figure 4 In the example shown, there may be delta changes to step 1a, as described in detail below, and the remainder of the flow of that step may remain the same.

[0127] In an example, step 1a may include: the MT portion of the WTRU may receive a request to access a specific localized service based on time and location criteria included in the localized service information, such as a localized service identifier, such as LS_ID_1, from an application in the TE portion of the WTRU. The localized service may include one or more of a gaming service, a streaming video service, etc.

[0128] exist Figure 4 In the example shown, steps 0 to 4 440, 450 can be compared with Figure 2 Steps 0 to 4 205, 210, 215, 220, 230, 240, 250 are the same in the example shown. Thus, the WTRU may operate in automatic network selection mode. Figure 4The examples shown may be applicable to the SNPN selection process, the CAG selection process, or both.

[0129] In an example, the WTRU may have selected 450 SNP N or CAG. This selection may be made after also performing steps 0 to 3 440.

[0130] One or more of the following steps may be used in the SNPN selection process.

[0131] In step 5a1 425, the WTRU has selected SNPN 450 as a starting point for hosted network selection, or step 5a1 425 is a subsequent step after the WTRU has exhausted the CAG-side search C1 415 for hosted network selection. The WTRU may first check to ensure that the SNPN is configured as a hosted network within the WTRU. For example, the WTRU may check whether the SNPN is part of a priority list of available hosted networks (SNPNs) along with validity conditions such as time and location. In an example, the WTRU may determine whether a hosted network is configured for the requested localized service (LS). Figure 4 The decision of “configured with priority list” as shown on the left side of diamond 425 means that the WTRU may search for the configured managed network as explained below for step 5a2 435. Otherwise if “not configured” as shown below diamond 425, the WTRU may check whether a search on the CAG side is required in step 5a4455.

[0132] In step 5a2 435, the WTRU is configured with a priority list of hosted networks (SNPNs), and the WTRU searches for available hosted networks (SNPNs) in order according to the priority list. If the search is successful, the WTRU proceeds to the next step (step 5a3 445), which is to register with the found SNPNs in order of priority. Otherwise, if no SNPN is found, the WTRU proceeds to step 5a4 455.

[0133] In step 5a3 445, if a hosted network (e.g., SNPN) is found, the WTRU will trigger registration with the SNPN to access localized services. If the registration is unsuccessful, the WTRU will attempt to register with the next available SNPN based on its priority order and the availability of the SNPN (discovered during the search phase). If the registration is unsuccessful on any found / available hosted network, the WTRU may switch to CAG mode and attempt to search and select an available CAG cell that can provide access to localized services. In the example, the WTRU may switch to CAG mode via C2 465. Although the connection between 5a3 445 and C2 465 is not explicitly shown in the figure, a person skilled in the art will understand that such a connection is possible and is compatible with the examples provided herein.

[0134] In step 5a4 455, if the WTRU is not configured with a prioritized list of hosted networks (SNPNs), the input to this step may come from step 5a1 425. Alternatively, if no SNPN is found as a hosted network (HN), the input to step 5a4 455 may come from step 5a2 435. At this point, in step 5a4 455, the WTRU may check whether a CAG search has been performed to access localized services. If the CAG search has not been performed or is not completed, the WTRU may trigger the CAG search and selection procedure C2 465. Otherwise, if the CAG search has been performed or is completed, the WTRU may proceed to step 6 495 and, for example, notify the user of the hosted network search and selection result (no hosted network coverage) and configure the WTRU for subsequent actions, as will be explained more fully below with respect to step 6 495.

[0135] One or more of the following steps may be used in the CAG selection process.

[0136] In step 5b1 470, the WTRU may have performed CAG search and selection 450 as a starting point for hosted network selection, or step 5b1 470 may be a subsequent step after the WTRU has exhausted the search C2 420 on the SNPN side for hosted network selection. The WTRU may first check to ensure that a CAG cell that provides access to localized services is configured in the WTRU. For example, the WTRU may check whether the CAG cell is part of the allowed CAG list. In the example of step 5b1 470, the WTRU may determine whether a CAG cell based on the CAG ID is configured for the requested LS.

[0137] In the event that a CAG cell is configured, the WTRU moves to the next step 5b2 475 and searches for an allowed CAG cell that provides access to localized services, as further explained below. On the other hand, in step 5b1 470, if no CAG cell is configured, the WTRU marks the CAG search and selection as complete in step 485 and determines whether the SNPN search is complete, as further explained below. The WTRU may move to the next step C1 490 and, for example, start searching for the SNPN from step C1 415 if the SNPN search for hosted network selection has not yet been completed.

[0138] In step 5b2 475, the WTRU may search for a CAG cell configured with the validity condition, for example, in a portion or at least a portion of the allowed CAG list. For example, the WTRU may search for the configured CAG ID in step 5b2 475. If a CAG is found, the WTRU may proceed to step 5b3 480, which will be explained below. If a CAG is not found, the WTRU may move to step 5b4 485, as further explained below.

[0139] In step 5b3 480, a CAG cell is found that provides access to localized services, and the WTRU will attempt to register with the CAG / PLMN to gain access to localized services. If registration on the CAG cell is unsuccessful, the WTRU will switch to SNPN hosted network selection if SNPN hosted network selection has not already been performed. In the example, the WTRU may switch to SNPN hosted network selection via C1 490. Although the figure does not explicitly show a connection between 5b3 480 and C1 490, one skilled in the art will understand that such a connection is possible and is compatible with the examples provided herein.

[0140] In step 5b4 485, if no CAG cell is configured in the WTRU, the input to this step may come from step 5b1 470. Alternatively, if no CAG cell providing access to the localized service is found, the input to step 5b4 485 may come from step 5b2 475. At this point, the WTRU may check in step 5b4 485 whether an SNPN search has been performed to access the localized service. In the event that the SNPN search has not been performed or is not completed, the WTRU may trigger the SNPN search and selection procedure C1 490. Otherwise, if the SNPN search has been performed or is completed, the WTRU may proceed to step 6 495, e.g., to notify the user about the hosted network search and selection result (no hosted network coverage) and configure the WTRU for the next action, as described below.

[0141] In step 6 495: the user is informed of the intermediate result (no managed network coverage), and the WTRU operating in automatic mode may perform the following actions. The WTRU may start a back-off timer and, upon expiration of the timer, re-trigger the search process from the beginning. Additionally, the WTRU may switch to the last WTRU mode, such as PLMN selection mode or SNPN access mode. Additionally, the WTRU may wait for the back-off timer to expire, which switches the mode back to HNSM and triggers the managed network search and selection process, which may be as follows, for example: Figure 2 shown.

[0142] The WTRU may exit HNSM at any point in time if the user terminates access to localized services or any event within the WTRU moves the WTRU to PLMN selection / SNPN access mode or a different mode.

[0143] The embodiments and examples provided herein below include a hosted network selection mechanism that includes a manual mode of operation. When a WTRU is normally camped on a cell, such as a normal cell or a hosted network cell, the WTRU may trigger a manual search for the availability of a hosted network in the camped area and may trigger the selection of a desired hosted network.

[0144] Figure 5 is a flow chart illustrating an example of a manual hosted network search and selection process. The example shown in flow chart 500 outlines the flow of a hosted network search and selection process for manual mode.

[0145] In step 0 510, the WTRU camps on a cell, which may be a normal cell or a managed network cell, that provides normal or limited service. In an example, the WTRU may operate in manual mode or automatic mode.

[0146] In step 1520, a user may request a manual mode localized service search. The user may use a GUI application running on the TE portion of the WTRU to send a request to the MT portion of the WTRU via an AT command. The TE portion of the WTRU may respond with localized service information that was previously configured and stored in the WTRU.

[0147] In step 2 530, the WTRU enters HNSM. The rationale behind entering this mode is that the WTRU is now specifically looking for a hosted network that can provide access to localized services. This step may also be optional. Optionally, entry into HNSM may be authorized by the home network (HPLMN) or subscribed SNPN, which may be pre-configured by the home network (HPLMN or subscribed SNPN) (e.g., stored via NVM / USIM files) or may be obtained through information exchange between the WTRU and the home network via NAS signaling. In an example, the NAS signaling may be a SoR, a registration / configuration update command, etc. The WTRU may initiate an authorization procedure with the HPLMN or subscribed SNPN. The purpose of this procedure is to obtain authorization and a token from the HPLMN or subscribed SNPN to access localized services. During the authorization procedure, the network may update the list of allowed CAGs / SNPN priority list (along with validity conditions), and this newly configured information will take precedence over the information stored by the WTRU.

[0148] In step 3 540, the next step is for the WTRU to search for a hosted network that can provide access to a specific localized service. In an example, where a manual search is requested specifically for a specific localized service, the specific localized service may be identified via LS_ID_1 (localized service identifier). In another example, the specific localized service may be used for a general localized service. The hosted network may be a SNPN or a PNI-NPN (CAG cell). In addition, the WTRU may need to determine a starting point for the search. The WTRU may also give a preference to a CAG cell or a SNPN in the search. The following are a few criteria that may be used by the WTRU to determine a starting point for the hosted network search. The WTRU may also use the criteria to give a preference to a CAG or a SNPN.

[0149] In an example regarding the first criterion (which may be considered criterion 1), the WTRU may store a new basic file in the USIM that may provide a preference for a hosted network, such as CAG or SNPN. Furthermore, this information may be indexed by the type of localized service (e.g., using a localized service ID); for example, for localized gaming services, using a CAG cell may be preferred over an SNPN, while for IMS, an SNPN as the hosted network providing access to the localized service may be preferred over a CAG cell. The content of this basic file may be based on the CAG / SNPN preference information received from the network. In an example, the network may update the content of this USIM file via an over-the-air USAT REFRESH command.

[0150] In another example regarding the second criterion (which may be considered criterion 2), a user may have their own preferences that are configured via a GUI and stored locally in the WTRU. In an example, the user preferences may be stored in the NVM of the WTRU.

[0151] In another example regarding the third criterion (which may be considered criterion 3), the selection of CAG or SNPN as the starting point may be based on the last search technique, such as the CAG or SNPN hosted network. In this example, the WTRU will start the search using the last search technique. In this example scenario, the last technique used to access the hosted network was via the SNPN. Therefore, a new request will trigger the WTRU to search for the SNPN on a CAG cell that provides access to localized services.

[0152] In an additional example regarding the fourth criterion (which may be considered criterion 4), for example, a preference for CAG or SNPN may always be configured after the power-up sequence for the WTRU. This configuration information may be based on user preferences or provided by the home network (HPLMN / subscribed SNPN), a third-party localization service provider, or both.

[0153] In yet another example regarding the fifth criterion (which may be considered criterion 5), the preference may be based on information provided by the home network (HPLMN / subscribed SNPN), by a third-party localization service provider, by the CH, or by the VPLMN. This information may be provided via NAS signaling. For example, this information may be provided via one or any combination of registration, WTRU configuration update, WTRU parameter update, WTRU policy delivery procedure, roaming guidance, etc. Additionally or alternatively, this information may be provided via the application layer on the user plane.

[0154] In another example regarding the sixth criterion (which may be considered criterion 6), the preference may be based on the WTRU's residency state, such as PLMN residency state or SNPN residency state. For example, a WTRU that is already camped on an SNPN may search for an SNPN hosting network before performing a handover to a CAG cell. Similarly, if the WTRU is camped on a PLMN, the WTRU may search for a CAG cell before performing a handover to an SNPN that provides access to localized services.

[0155] The criteria used to determine the starting point for a search can have associated priorities, and higher priority settings will take precedence over lower priority settings. For example, among the criteria, the priority order from highest priority to lowest priority can be 2, then 5, then 4, then 1, then 3, and then 6. In a particular example, criterion 2 can have a higher priority setting than criterion 5, and therefore, criterion 2 can take precedence over criterion 5. Furthermore, criterion 5 can have a higher priority setting than criterion 4, and therefore, criterion 5 can take precedence over criterion 4. Furthermore, criterion 4 can have a higher priority setting than criterion 1, and therefore, criterion 4 can take precedence over criterion 1. Furthermore, criterion 1 can have a higher priority setting than criterion 3, and therefore, criterion 1 can take precedence over criterion 3. In another example, criterion 3 can have a higher priority setting than criterion 6, and therefore, criterion 3 can take precedence over criterion 6.

[0156] In another example, considering the priorities defined in the above example, if criterion item 2 (i.e., the user-defined criterion) is not present in the WTRU, then criterion 5 (i.e., the search preference provided by the HPLMN / VPLMN / CH criteria) will now take the highest priority because criterion 5 has the second highest priority after criterion 2. The new priority order among the criteria would, for example, be 5, then 4, then 1, then 3, then 6, from highest to lowest priority.

[0157] In step 4 560, in an example, reporting of the hosted network may be performed as follows. The WTRU may continuously report immediately upon finding a hosted network, such as a CAG or SNPN. Additionally or alternatively, the WTRU may report a found CAG cell, SNPN hosted network, or both after completing the search for both CAG and SNPN technologies.

[0158] In step 5570, the user may select one of the managed networks reported by the WTRU. In an example, this selection may be input by the user into an application using a GUI.

[0159] In step 6 590, the WTRU may then register on the selected managed network, such as CAG or SNPN. In addition, the WTRU may notify the user of the result. For example, the WTRU may notify the user of the success or failure of the registration on the user's selected managed network.

[0160] Although the features and elements are described above in specific combinations, it will be understood by those skilled in the art that each feature or element can be used alone or in any combination with the other features and elements. In addition, it will be understood by those skilled in the art that the features and elements described above include means for implementing the methods described herein. In addition, the methods described herein can be implemented in a computer program, software, or firmware that is incorporated into a computer-readable medium for execution by a computer or processor. Examples of computer-readable media include electronic signals (transmitted via wired or wireless connections) and computer-readable storage media. Examples of computer-readable storage media include, but are not limited to, read-only memory (ROM), random access memory (RAM), registers, cache memory, semiconductor memory devices, magnetic media such as internal hard disks and removable disks, magneto-optical media, and optical media such as CD-ROMs and digital versatile disks (DVDs). A processor in combination with software can be used to implement a radio frequency transceiver for use in a WTRU, UE, terminal, base station, RNC, STA, AP, relay node, mesh node, customer premises equipment (CPE), fixed wireless access (FWA) equipment, industrial equipment, or any host computer.

Claims

1. A method for a wireless transmit / receive unit (WTRU), the method comprising: triggering a search for a hosted network based on one or more of: a request for a localized service from a user, a periodic search, a loss of coverage, and satisfaction of one or more availability conditions for the localized service; selecting one of a closed access group (CAG) and a standalone non-public network (SNPN) based on one or more of a universal subscriber identity module (USIM) base file, user preferences in local non-volatile memory (NVM) storage, a last search technique, a power-up sequence preference, a value provided by the network, and a WTRU residency state; as well as Register with the selected CAG or SNPN based on the selection of the CAG or SNPN. 2 . The method of claim 1 , wherein one or more of the USIM base file, the power-up sequence preference, and the value provided by the network are received in configuration information.

3. The method of claim 1, wherein the network is a Home Public Land Mobile Network (PLMN) (HPLMN), a Visited PLMN (VPLMN), or a Certificate Holder (CH).

4. The method of claim 1 , wherein one or more of the USIM base file, the user preferences in the local NVM storage, the last search technique, and the power-on sequence preferences include a preference for the CAG or the SNPN.

5. The method of claim 1 , wherein the WTRU camp state comprises a PLMN state or a SNPN state. The method of claim 1 , wherein the loss of coverage comprises an out-of-coverage scene. The method of claim 1 , wherein the user preferences are received through a manual request by a user for localization services.

8. The method of claim 1, wherein the one or more validity conditions include one or more of a time condition, a location condition, and a duration condition.

9. A wireless transmit / receive unit (WTRU), the WTRU comprising: processor; as well as a transceiver operatively coupled to the processor, wherein: The processor and the transceiver are configured to trigger a search for a hosted network based on one or more of: a request for a localized service from a user, a periodic search, a loss of coverage, and satisfaction of one or more validity conditions for the localized service; the processor being configured to select one of a closed access group (CAG) and a standalone non-public network (SNPN) based on one or more of a universal subscriber identity module (USIM) elementary file, user preferences in local non-volatile memory (NVM) storage, a last search technique, a power-up sequence preference, a value provided by the network, and a WTRU residency state; and The processor and the transceiver are configured to register with the selected CAG or SNPN based on the selection of the CAG or SNPN.

10. The WTRU of claim 9, wherein one or more of the USIM base file, the power-up sequence preference, and the value provided by the network are received in configuration information.

11. The WTRU of claim 9, wherein the network is a Home Public Land Mobile Network (PLMN) (HPLMN), a Visited PLMN (VPLMN), or a Certificate Holder (CH).

12. The WTRU of claim 9, wherein one or more of the USIM base file, user preferences in the local NVM storage, the last search technique, and the power-on sequence preferences include a preference for the CAG or the SNPN.

13. The WTRU of claim 9, wherein the WTRU camp state comprises a PLMN state or a SNPN state.

14. The WTRU of claim 9, wherein the coverage loss comprises an out-of-coverage scenario.

15. The WTRU of claim 9, wherein the user preference is received via a manual request by a user for localized service.

16. The WTRU of claim 9, wherein the one or more validity conditions include one or more of a time condition, a location condition, and a duration condition.

Images