Hosted network cell selection

Abstract

Systems, methods, and instrumentalities disclosed herein relate to localization services. A wireless transmit / receive unit (WTRU) can receive, from a first network node, validity information associated with a service, where the validity information can indicate one or more valid areas for accessing the service. The WTRU can determine whether the WTRU is capable of accessing the service via a wireless communication cell based at least on the validity information and information about the wireless communication cell, and based at least on a determination that the WTRU is capable of accessing the service via the wireless communication cell, the WTRU can perform a measurement associated with the wireless communication cell and send a message to a second network node, where the message can indicate a result of the measurement.

Description

[0001] Cross-reference to related applications This application claims the benefit of U.S. Provisional Patent Application No. 63 / 569,966, filed March 26, 2024, the disclosure of which is incorporated herein by reference in its entirety. Background Technology

[0002] Mobile communications using wireless communication continue to evolve. The fifth-generation mobile radio access technology (RAT) can be referred to as 5G New Radio (NR). Previous-generation (conventional) mobile communication RATs could be, for example, fourth-generation (4G) Long Term Evolution (LTE). Summary of the Invention

[0003] This document discloses systems, methods, and means associated with localized services. In embodiments of this disclosure, a Wireless Transmit / Receive Unit (WTRU) can be configured to receive service-related validity information from a first network node, wherein the validity information may indicate one or more valid areas for accessing the service. The WTRU may determine, at least based on the validity information and information about the wireless communication cell, whether the WTRU can access the service via the wireless communication cell, and at least based on the determination that the WTRU can access the service via the wireless communication cell, the WTRU may perform a measurement associated with the wireless communication cell and send a message to a second network node, wherein the message may indicate the result of the measurement.

[0004] In the example, the measurement may be associated with cell selection or reselection. In the example, validity information may further indicate one or more valid time periods for accessing the service, wherein the WTRU can be configured to further determine whether the WTRU is able to access the service via a wireless communication cell based on one or more valid time periods.

[0005] In the example, validity information may include one or more tracking area identifiers or cell identifiers indicating one or more valid areas for accessing the service. In the example, information about the wireless communication cell used by the WTRU to determine whether the WTRU can access the service via the wireless communication cell may include the tracking area identifier or cell identifier of the wireless communication cell.

[0006] In the example, the WTRU is configured to receive service-related validity information, which may include configuring the WTRU to verify the correctness of the validity information against a pre-configured list of networks or cells. For example, if the validity information indicates that a network or cell is not on the pre-configured list of networks or cells, the WTRU can determine that the validity information is incorrect.

[0007] In the example, the first network node described herein may include an Access and Mobility Function (AMF) of a wireless communication network (e.g., a public or non-public communication network), and the second network node described herein may include a base station of the wireless communication network. In the example, the WTRU may indicate the validity information described herein to the base station associated with the wireless communication network.

[0008] In the example, the wireless communication cell can be a neighboring cell of the WTRU's current serving cell, and the WTRU can receive validity information via a message associated with roaming guidance. In the example, in response to determining that the WTRU cannot access service via the wireless communication cell, the WTRU can be configured to skip measurements of the wireless communication cell. Attached Figure Description

[0009] Figure 1A This is a system diagram illustrating an example communication system in which one or more of the disclosed embodiments may be implemented.

[0010] Figure 1B This illustrates that, according to an embodiment, it is possible to Figure 1A The system diagram shown is of an example wireless transmit / receive unit (WTRU) used in the communication system.

[0011] Figure 1C This illustrates that, according to an embodiment, it is possible to Figure 1A The system diagram shows an example radio access network (RAN) and an example core network (CN) used in the communication system shown.

[0012] Figure 1D This illustrates that, according to an embodiment, it is possible to Figure 1A The system diagram shows another example RAN and another example CN used in the communication system shown.

[0013] Figure 2 An example process for receiving and verifying location validity information is shown, which can be part of the bootstrapping (SOR-SNPN-SI-LS) for roaming SNPN selection information for localized services.

[0014] Figure 3 An example procedure for WTRU to process location validity information is shown, which can be provided as part of SOR-SNPN-SI-LS. Detailed Implementation

[0015] Figure 1AThis diagram illustrates an example communication system 100 in which one or more of the disclosed embodiments may be implemented. The communication system 100 may be a multiple access system that provides content such as voice, data, video, messaging, and broadcasting to multiple wireless users. The communication system 100 enables multiple wireless users to access this 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 DFT Spread Spectrum OFDM (ZT UWDTS-s OFDM), Unique Word OFDM (UW-OFDM), Resource Block Filtered OFDM, Filter Bank Multicarrier (FBMC), etc.

[0016] like Figure 1A As shown, the communication system 100 may include wireless transceiver units (WTRUs) 102a, 102b, 102c, 102d, RAN 104 / 113, CN 106 / 115, Public Switched Telephone Network (PSTN) 108, Internet 110, and other networks 112. However, it should be understood that the disclosed embodiments contemplate any number of WTRUs, base stations, networks, and / or network elements. Each of the WTRUs 102a, 102b, 102c, and 102d may be any type of device configured to operate and / or communicate in a wireless environment. For example, WTRUs 102a, 102b, 102c, and 102d (any of which may be referred to as a “station” and / or “STA”) may be configured to transmit and / or receive wireless signals and may include user equipment (UE), mobile stations, fixed or mobile subscriber units, subscription-based units, pagers, cellular phones, personal digital assistants (PDAs), smartphones, laptops, netbooks, personal computers, wireless sensors, hotspots or Mi-Fi devices, Internet of Things (IoT) devices, watches or other wearable devices, head-mounted displays (HMDs), vehicles, drones, medical devices and applications (e.g., remote surgery), industrial devices and applications (e.g., robots and / or other wireless devices operating in the context of industrial and / or automated processing chains), consumer electronics devices, devices operating on commercial and / or industrial wireless networks, etc. Any of WTRUs 102a, 102b, 102c, and 102d may be interchangeably referred to as a UE.

[0017] The communication system 100 may also include base station 114a and / or base station 114b. Each of base stations 114a and 114b may be any type of device configured to wirelessly interface with at least one of WTRUs 102a, 102b, 102c, and 102d to facilitate access to one or more communication networks (e.g., CN 106 / 115, Internet 110, and / or other networks 112). For example, base stations 114a and 114b may be base transceiver stations (BTS), node Bs, eNodeBs, home node Bs, home eNodeBs, gNBs, NRNodeBs, site controllers, access points (APs), wireless routers, etc. Although base stations 114a and 114b are each described as a single element, it should be understood that base stations 114a and 114b may include any number of interconnected base station and / or network elements.

[0018] Base station 114a may be part of RAN 104 / 113, and may also include other base stations and / or network elements (not shown), such as base station controllers (BSCs), radio network controllers (RNCs), relay nodes, etc. Base station 114a and / or base station 114b may be configured to transmit and / or receive radio 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 coverage of a specific geographic area, which may be relatively fixed or may change over time. A cell may also be 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, i.e., one transceiver per sector of the cell. In embodiments, base station 114a may employ multiple-input multiple-output (MIMO) technology and may utilize 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.

[0019] Base stations 114a and 114b can communicate with one or more of WTRUs 102a, 102b, 102c, and 102d via air interface 116. Air interface 116 can be any suitable wireless communication link (e.g., radio frequency (RF), microwave, centimeter wave, micrometer wave, infrared (IR), ultraviolet (UV), visible light, etc.). Any suitable radio access technology (RAT) can be used to establish air interface 116.

[0020] More specifically, as described above, the communication system 100 can be a multiple access system and can employ one or more channel access schemes, such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, etc. For example, base stations 114a and WTRUs 102a, 102b, and 102c in RAN 104 / 113 can implement radio technologies such as Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA), which can establish air interfaces 115 / 116 / 117 using Wideband CDMA (WCDMA). WCDMA can include communication protocols such as High-Speed ​​Packet Access (HSPA) and / or evolved HSPA (HSPA+). HSPA can include High-Speed ​​Downlink (DL) Packet Access (HSDPA) and / or High-Speed ​​UL Packet Access (HSUPA).

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

[0022] In the embodiment, base station 114a and WTRUs 102a, 102b, 102c can implement radio technologies such as NR radio access, which can establish air interface 116 using new radio (NR).

[0023] In this embodiment, base station 114a and WTRUs 102a, 102b, and 102c can implement multiple radio access technologies. For example, base station 114a and WTRUs 102a, 102b, and 102c can jointly implement LTE radio access and NR radio access, for example, using the dual connectivity (DC) principle. Therefore, the air interface used by WTRUs 102a, 102b, and 102c can be characterized by multiple types of radio access technologies and / or transmissions sent to / from multiple types of base stations (e.g., eNBs and gNBs).

[0024] In other embodiments, base station 114a and WTRUs 102a, 102b, and 102c can implement radio technologies such as IEEE 802.11 (i.e., Wi-Fi), IEEE 802.16 (i.e., WiMAX), CDMA2000, CDMA2000 1X, CDMA2000 EV-DO, Provisional Standard 2000 (IS-2000), Provisional Standard 95 (IS-95), Provisional Standard 856 (IS-856), Global System for Mobile Communications (GSM), Enhanced Data Rate GSM Evolution (EDGE), and GSM EDGE (GERAN).

[0025] For example, Figure 1A Base station 114b can be a wireless router, home node B, home eNodeB, or access point, and can utilize any suitable RAT to facilitate wireless connectivity in a local area, such as commercial locations, homes, vehicles, campuses, industrial facilities, air corridors (e.g., for drone use), roads, etc. In one embodiment, base station 114b and WTRUs 102c, 102d can implement radio technology such as IEEE 802.11 to establish a wireless local area network (WLAN). In another embodiment, base station 114b and WTRUs 102c, 102d can implement radio technology such as IEEE 802.15 to establish a wireless personal area network (WPAN). In yet another embodiment, base station 114b and WTRUs 102c, 102d can utilize cellular-based RATs (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, LTE-A Pro, NR, etc.) to establish picocells or femtocells. Figure 1A As shown, base station 114b can be directly connected to Internet 110. Therefore, it is not required that base station 114b access Internet 110 via CN 106 / 115.

[0026] RAN 104 / 113 can communicate with CN 106 / 115, which can be any type of network configured to provide voice, data, application, and / or Voice over Internet Protocol (VoIP) services to one or more of WTRUs 102a, 102b, 102c, and 102d. Data can have different Quality of Service (QoS) requirements, such as different throughput requirements, latency requirements, fault tolerance requirements, reliability requirements, data throughput requirements, mobility requirements, etc. CN 106 / 115 can provide call control, billing services, location-based services, prepaid calling, internet connectivity, video distribution, and / or perform advanced security functions such as user authentication. Although in Figure 1AAlthough not shown, it should be understood that RAN 104 / 113 and / or CN 106 / 115 can communicate directly or indirectly with other RANs using the same RAT as RAN 104 / 113 or a different RAT. For example, in addition to connecting to RAN 104 / 113, which may utilize NR radio technology, CN 106 / 115 can also communicate with another RAN (not shown) using GSM, UMTS, CDMA2000, WiMAX, E-UTRA, or WiFi radio technology.

[0027] CN 106 / 115 can also serve as a gateway for WTRU 102a, 102b, 102c, 102d to access PSTN 108, the Internet 110, and / or other networks 112. PSTN 108 may include a circuit-switched telephone network providing Common Old-Style Telephone Service (POTS). The Internet 110 may include a global system of interconnected computer networks and devices using common communication protocols such as Transmission Control Protocol (TCP), User Datagram Protocol (UDP), and / or Internet Protocol (IP) from the TCP / IP Internet Protocol suite. Network 112 may include wired and / or wireless communication networks owned and / or operated by other service providers. For example, network 112 may include another CN connected to one or more RANs, which may use the same RAT as RAN 104 / 113 or a different RAT.

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

[0029] Figure 1B This is a system diagram illustrating example WTRU 102. (See diagram below.) Figure 1B As shown, WTRU 102 may include a processor 118, a transceiver 120, a transmitting / receiving element 122, a speaker / microphone 124, a keyboard 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 peripheral devices 138, etc. It should be understood that WTRU 102 may include any sub-combination of the foregoing elements while remaining consistent with the embodiments.

[0030] Processor 118 may be a general-purpose processor, a special-purpose processor, a conventional processor, a digital signal processor (DSP), multiple 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) circuit, any other type of integrated circuit (IC), a state machine, etc. Processor 118 may perform signal encoding / decoding, data processing, power control, input / output processing, and / or any other functions that enable WTRU 102 to operate in a wireless environment. Processor 118 may be coupled to transceiver 120, and transceiver 120 may be coupled to transmitting / receiving element 122. Although Figure 1B While processor 118 and transceiver 120 are described as separate components, it should be understood that processor 118 and transceiver 120 may be integrated together in an electronic package or chip.

[0031] Transmitting / receiving element 122 can be configured to transmit signals to or receive signals from a base station (e.g., base station 114a) via air interface 116. For example, in one embodiment, transmitting / receiving element 122 can be an antenna configured to transmit and / or receive RF signals. In another embodiment, transmitting / receiving element 122 can be a transmitter / detector, for example, configured to transmit and / or receive IR, UV, or visible light signals. In yet another embodiment, transmitting / receiving element 122 can be configured to transmit and / or receive both RF and optical signals. It should be understood that transmitting / receiving element 122 can be configured to transmit and / or receive any combination of wireless signals.

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

[0033] Transceiver 120 can be configured to modulate signals to be transmitted by transmitting / receiving element 122 and demodulate signals received by transmitting / receiving element 122. As described above, WTRU 102 can have multi-mode capability. Therefore, for example, transceiver 120 may include multiple transceivers to enable WTRU 102 to communicate via multiple RATs, such as NR and IEEE 802.11.

[0034] The processor 118 of WTRU 102 can be coupled to a speaker / microphone 124, a keyboard 126, and / or a display / touchpad 128 (e.g., a liquid crystal display (LCD) unit or an organic light-emitting diode (OLED) display unit) and can receive user input data therefrom. The processor 118 can also output user data to the speaker / microphone 124, keyboard 126, and / or display / touchpad 128. Furthermore, the processor 118 can access and store information from any type of suitable memory (e.g., non-removable memory 130 and / or removable memory 132). 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. Removable memory 132 may include a subscriber identity module (SIM) card, a memory stick, a secure digital storage (SD) card, etc. In other embodiments, the processor 118 can access and store information from memory that is not physically located on WTRU 102 (e.g., on a server or home computer (not shown)).

[0035] The processor 118 can receive power from the power supply 134 and can be configured to distribute and / or control power to other components in the WTRU 102. The power supply 134 can be any suitable device for powering the WTRU 102. For example, the power supply 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.

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

[0037] The processor 118 may be further coupled to other peripheral devices 138, which may include one or more software and / or hardware modules providing additional features, functions, and / or wired or wireless connectivity. For example, peripheral devices 138 may include accelerometers, electronic compasses, satellite transceivers, digital cameras (for photos and / or video), Universal Serial Bus (USB) ports, vibration devices, television transceivers, hands-free headsets, Bluetooth® modules, FM radio units, digital music players, media players, video game player modules, internet browsers, virtual reality and / or augmented reality (VR / AR) devices, activity trackers, etc. Peripheral devices 138 may include one or more sensors, which may be gyroscopes, accelerometers, Hall effect sensors, magnetometers, orientation sensors, proximity sensors, temperature sensors, time sensors; geolocation sensors; altimeters, light sensors, touch sensors, magnetometers, barometers, attitude sensors, biosensors, and / or humidity sensors.

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

[0039] Figure 1C This is a system diagram illustrating RAN 104 and CN 106 according to an embodiment. As described above, RAN 104 can communicate with WTRUs 102a, 102b, and 102c via air interface 116 using E-UTRA radio technology. RAN 104 can also communicate with CN 106.

[0040] RAN 104 may include eNode-B 160a, 160b, 160c; however, it should be understood that RAN 104 may include any number of eNode-Bs while remaining consistent with the embodiments. eNode-B 160a, 160b, 160c may each include one or more transceivers for communicating with WTRU 102a, 102b, 102c via air interface 116. In one embodiment, eNode-B 160a, 160b, 160c may implement MIMO technology. Therefore, for example, eNode-B 160a may use multiple antennas to transmit and / or receive radio signals from WTRU 102a.

[0041] Each of the eNode-B 160a, 160b, and 160c can be associated with a specific cell (not shown) and can be configured to handle radio resource management decisions, handover decisions, and user scheduling in the UL and / or DL, etc. Figure 1C As shown, eNode-B 160a, 160b, and 160c can communicate with each other via the X2 interface.

[0042] Figure 1C The CN 106 shown may include a Mobility Management Entity (MME) 162, a Serving Gateway (SGW) 164, and a Packet Data Network (PDN) Gateway (or PGW) 166. While each of the foregoing elements is described as part of CN 106, it should be understood that any of these elements may be owned and / or operated by an entity other than the CN operator.

[0043] The MME 162 can connect to each eNode-B 160a, 160b, and 160c in RAN 104 via the S1 interface and can be used as a control node. For example, the MME 162 can be responsible for authenticating users of WTRUs 102a, 102b, and 102c, bearer activation / deactivation, selecting a specific serving gateway during the initial attachment of WTRUs 102a, 102b, and 102c, etc. The MME 162 can provide control plane functions for handover between RAN 104 and other RANs (not shown) employing other radio technologies (such as GSM and / or WCDMA).

[0044] The SGW 164 can connect to each eNode B 160a, 160b, or 160c in RAN 104 via the S1 interface. The SGW 164 can typically route and forward user data packets to / from WTRUs 102a, 102b, or 102c. The SGW 164 can perform other functions, such as anchoring the user plane during inter-eNode B handover; triggering paging when DL data is available for WTRUs 102a, 102b, or 102c; and managing and storing the context of WTRUs 102a, 102b, or 102c.

[0045] The SGW 164 can connect to the PGW 166, which can provide WTRU 102a, 102b, and 102c with access to packet-switched networks such as Internet 110, to facilitate communication between WTRU 102a, 102b, 102c and IP-enabled devices.

[0046] CN 106 can facilitate communication with other networks. For example, CN 106 can provide WTRU 102a, 102b, and 102c with access to a circuit-switched network such as PSTN 108 to facilitate communication between WTRU 102a, 102b, and 102c and traditional landline communication equipment. For example, CN 106 may include, or be able to communicate with, an IP gateway (e.g., an IP Multimedia Subsystem (IMS) server) that serves as an interface between CN 106 and PSTN 108. Furthermore, CN 106 can provide WTRU 102a, 102b, and 102c with access to other networks 112, which may include other wired and / or wireless networks owned and / or operated by other service providers.

[0047] Despite WTRU in Figure 1A-1D While described as a wireless terminal, it is conceivable that in some representative embodiments, such a terminal may use (e.g., temporarily or permanently) a wired communication interface with a communication network.

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

[0049] A WLAN in Infrastructure Basic Services Set (BSS) mode can have an access point (AP) for the BSS and one or more stations (STAs) associated with the AP. The AP can access or peer into a distributed system (DS) or another type of wired / wireless network that carries traffic into and / or out of the BSS. Traffic originating outside the BSS destined for a STA can be delivered to the AP via it. Traffic originating from a STA destined for a destination outside the BSS can be sent to the AP for delivery to the appropriate destination. For example, traffic between STAs within the BSS can be sent via the AP, where the source STA can send traffic to the AP, and the AP can deliver traffic to the destination STA. Traffic between STAs within the BSS can be considered and / or referred to as peering traffic. Peering traffic can be sent between source and destination STAs (e.g., directly between them) using Direct Link Establishment (DLS). In some representative embodiments, the DLS can use 802.11e DLS or 802.11z Tunneled DLS (TDLS). A WLAN using the Standalone BSS (IBSS) mode may not have an access point (AP), and STAs within the IBSS or using the IBSS (e.g., all STAs) can communicate directly with each other. The IBSS communication mode is sometimes referred to as the "self-organizing" communication mode in this document.

[0050] When operating in 802.11ac infrastructure mode or a similar mode, the AP can transmit beacons on a fixed channel (e.g., the primary channel). The primary channel can be of a fixed width (e.g., a 20 MHz bandwidth) or dynamically set via signaling. The primary channel can be the operating channel of the BSS and can be used by the STA to establish a connection with the AP. In some representative embodiments, Carrier Sense Multiple Access with Collision Avoidance (CSMA / CA) can be implemented, for example in an 802.11 system. For CSMA / CA, 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, that particular STA can back off. A single STA (e.g., only one station) can transmit at any given time within a given BSS.

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

[0052] Very High Throughput (VHT) STAs can support channels with widths of 20MHz, 40MHz, 80MHz, and / or 160MHz. 40MHz and / or 80MHz channels can be formed by combining consecutive 20MHz channels. A 160MHz channel can be formed by combining eight consecutive 20MHz channels, or by combining two non-consecutive 80MHz channels, which can be referred to as an 80+80 configuration. For the 80+80 configuration, after channel coding, the data passes through a segment resolver, which splits the data into two streams. Each stream can be processed separately using Inverse Fast Fourier Transform (IFFT) and time-domain processing. These streams can be mapped onto the two 80MHz channels, and the data can be transmitted by the transmitting STA. At the receiver of the receiving STA, the operation of the 80+80 configuration described above can be reversed, and the combined data can be sent to the Media Access Control (MAC).

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

[0054] WLAN systems that can support multiple channels and channel bandwidths (e.g., 802.11n, 802.11ac, 802.11af, and 802.11ah) include a channel that can be designated as the primary channel. 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 one of the STAs operating in the BSS that supports the minimum bandwidth operating mode. In the 802.11ah example, for STAs that support (e.g., only support) the 1MHz mode (e.g., MTC type devices), the primary channel can be 1MHz wide, even if the AP and other STAs in the BSS support 2MHz, 4MHz, 8MHz, 16MHz, and / or other channel bandwidth operating modes. Carrier Sense and / or Network Allocation Vector (NAV) settings can depend on the status of the primary channel. If the primary channel is busy, for example due to STAs (only supporting the 1MHz operating mode) sending to the AP, the entire available band can be considered busy, even if most of the band remains idle and may be available.

[0055] In the United States, the available frequency band for 802.11ah is from 902MHz to 928MHz. In South Korea, the available frequency band is from 917.5MHz to 923.5MHz. In Japan, the available frequency band is from 916.5MHz to 927.5MHz. The total available bandwidth for 802.11ah is 6MHz to 26MHz, depending on the country code.

[0056] Figure 1D This is a system diagram illustrating RAN 113 and CN 115 according to an embodiment. As described above, RAN 113 can communicate with WTRUs 102a, 102b, and 102c via air interface 116 using NR radio technology. RAN 113 can also communicate with CN 115.

[0057] RAN 113 may include gNBs 180a, 180b, and 180c; however, it should be understood that RAN 113 may include any number of gNBs while remaining consistent with the embodiments. gNBs 180a, 180b, and 180c may each include one or more transceivers for communicating with WTRUs 102a, 102b, and 102c via air interface 116. In one embodiment, gNBs 180a, 180b, and 180c may implement MIMO technology. For example, gNBs 180a and 180b may utilize beamforming to transmit signals to and / or receive signals from gNBs 180a, 180b, and 180c. Therefore, for example, gNB 180a may use multiple antennas to transmit and / or receive radio signals from WTRU 102a. In embodiments, gNBs 180a, 180b, and 180c can implement carrier aggregation technology. For example, gNB 180a can transmit multiple component carriers (not shown) to WTRU 102a. A subset of these component carriers can be on unlicensed spectrum, while the remaining component carriers can be on licensed spectrum. In embodiments, gNBs 180a, 180b, and 180c can implement Coordinated Multipoint (CoMP) technology. For example, WTRU 102a can receive coordinated transmissions from gNBs 180a and 180b (and / or gNB 180c).

[0058] WTRUs 102a, 102b, and 102c can communicate with gNBs 180a, 180b, and 180c using transmissions associated with scalable digitization. For example, OFDM symbol spacing and / or OFDM subcarrier spacing can vary for different transmissions, different cells, and / or different portions of the radio transmission spectrum. WTRUs 102a, 102b, and 102c can communicate with gNBs 180a, 180b, and 180c using subframes or transmission time intervals (TTIs) of various or scalable lengths (e.g., containing different numbers of OFDM symbols and / or continuously varying lengths of absolute time).

[0059] gNBs 180a, 180b, and 180c can be configured to communicate with WTRUs 102a, 102b, and 102c in standalone and / or non-standalone configurations. In standalone configuration, WTRUs 102a, 102b, and 102c can communicate with gNBs 180a, 180b, and 180c without simultaneously accessing other RANs (e.g., eNode-Bs 160a, 160b, and 160c). In standalone configuration, WTRUs 102a, 102b, and 102c can utilize one or more gNBs 180a, 180b, and 180c as mobility anchors. In standalone configuration, WTRUs 102a, 102b, and 102c can communicate with gNBs 180a, 180b, and 180c using signals in unlicensed frequency bands. In a non-standalone configuration, WTRUs 102a, 102b, and 102c can communicate / connect with gNBs 180a, 180b, and 180c, while also communicating / connecting with another RAN such as eNode-Bs 160a, 160b, and 160c. For example, WTRUs 102a, 102b, and 102c can implement DC principles to communicate substantially simultaneously with one or more gNBs 180a, 180b, and 180c, as well as one or more eNode-Bs 160a, 160b, and 160c. In a non-standalone configuration, eNode-Bs 160a, 160b, and 160c can be used as mobility anchors for WTRUs 102a, 102b, and 102c, and gNBs 180a, 180b, and 180c can provide additional coverage and / or throughput for serving WTRUs 102a, 102b, and 102c.

[0060] Each of gNBs 180a, 180b, and 180c can be associated with a specific cell (not shown) and can be configured to handle radio resource management decisions, handover decisions, user scheduling in UL and / or DL, network slicing support, dual connectivity, interoperability between NR and E-UTRA, routing user plane data to User Plane Functions (UPF) 184a and 184b, and routing control plane information to Access and Mobility Management Functions (AMF) 182a and 182b, etc. Figure 1D As shown, gNB 180a, 180b, and 180c can communicate with each other via the Xn interface.

[0061] Figure 1DThe CN 115 shown may include at least one AMF 182a, 182b, at least one UPF 184a, 184b, at least one Session Management Function (SMF) 183a, 183b, and possibly a Data Network (DN) 185a, 185b. Although each of the foregoing elements is described as part of the CN 115, it should be understood that any of these elements may be owned and / or operated by an entity other than the CN operator.

[0062] AMF 182a and 182b can connect to one or more gNBs 180a, 180b, and 180c in RAN 113 via the N2 interface and can be used as control nodes. For example, AMF 182a and 182b can be responsible for authenticating users of WTRU 102a, 102b, and 102c, supporting network slicing (e.g., handling different PDU sessions with different requirements), selecting specific SMF 183a and 183b, managing registration areas, terminating NAS signaling, mobility management, etc. AMF 182a and 182b can use network slicing to customize CN support for WTRU 102a, 102b, and 102c based on the service type used by WTRU 102a, 102b, and 102c. For example, different network slices can be established for different use cases (e.g., services relying on Ultra Reliable Low Latency (URLLC) access, services relying on Enhanced Massive Mobile Broadband (eMBB) access, services for Machine Type Communication (MTC) access, etc.). AMF 162 can provide control plane functions for handover between RAN 113 and other RANs (not shown) that employ other radio technologies, such as LTE, LTE-A, LTE-A Pro and / or non-3GPP access technologies, such as WiFi.

[0063] SMFs 183a and 183b can connect to AMFs 182a and 182b in CN 115 via the N11 interface. SMFs 183a and 183b can also connect to UPFs 184a and 184b in CN 115 via the N4 interface. SMFs 183a and 183b can select and control UPFs 184a and 184b, and configure the routing of services through UPFs 184a and 184b. SMFs 183a and 183b can perform other functions, such as managing and allocating UE IP addresses, managing PDU sessions, controlling policy enforcement and QoS, and providing downlink data notifications. PDU session types can be IP-based, non-IP-based, Ethernet-based, etc.

[0064] UPF 184a and 184b can be connected to one or more gNBs 180a, 180b, and 180c in RAN 113 via the N3 interface. This interface can provide WTRU 102a, 102b, and 102c with access to a packet-switched network (e.g., Internet 110) to facilitate communication between WTRU 102a, 102b, 102c and IP-enabled devices. UPF 184 and 184b can perform other functions such as routing and forwarding packets, enforcing user plane policies, supporting multi-destination PDU sessions, handling user plane QoS, buffering downlink packets, and providing mobility anchoring.

[0065] CN 115 can facilitate communication with other networks. For example, CN 115 may include, or be able to communicate with, an IP gateway (e.g., an IP Multimedia Subsystem (IMS) server) serving as an interface between CN 115 and PSTN 108. Furthermore, CN 115 can provide WTRUs 102a, 102b, and 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, WTRUs 102a, 102b, and 102c can be connected to local data networks (DNs) 185a and 185b via UPFs 184a and 184b through their N3 interfaces and the N6 interface between UPFs 184a and 184b and DNs 185a and 185b.

[0066] Given Figure 1A-1D as well as Figure 1A-1D As described in the corresponding descriptions herein, one or all of the functions described for one or more of the WTRU 102a-d, base station 114a-b, eNode-B 160a-c, MME 162, SGW 164, PGW 166, gNB 180a-c, AMF 182a-b, UPF 184a-b, SMF183a-b, DN 185a-b, and / or any other device described herein (one or more) may be performed by one or more emulation devices (not shown). An emulation device may be one or more devices configured to emulate one or more of the functions described herein. For example, an emulation device may be used to test other devices and / or simulate network and / or WTRU functions.

[0067] Simulation devices can be designed to perform one or more tests on other devices in laboratory and / or carrier network environments. For example, one or more simulation 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 to test other devices within the communication network. One or more simulation devices can perform one or more or all functions while being temporarily implemented / deployed as part of a wired and / or wireless communication network. Simulation devices can be directly coupled to another device for testing and / or testing purposes that can be performed using over-the-air wireless communication.

[0068] One or more emulation devices may perform one or more functions, including all functions, rather than being implemented / deployed as part of a wired and / or wireless communication network. For example, emulation devices may be used in test scenarios outside of deployment (e.g., testing) wired and / or wireless communication networks and / or test laboratories to implement testing of one or more components. One or more emulation devices may be test equipment. Emulation devices may transmit and / or receive data using direct RF coupling and / or wireless communication via RF circuitry (e.g., which may include one or more antennas).

[0069] In this article, the term "timer" can refer to time, time period, time tracking, time period tracking, or combinations thereof. The term "timer expiration" can refer to the confirmed arrival of a specific time or the expiration of a specific time period.

[0070] As described herein, cell selection and reselection can be enhanced relative to the managed network to ensure seamless idle and / or connected mode mobility with minimal (e.g., no) disruption. When the WTRU receives managed network selection information (e.g., guidance for roaming SNPN selection information for localized services (SOR-SNPN-SI-LS)) via the SoR transparent container, it can verify the correctness of location validity information provided by the network or a third-party operator of the localized service. The WTRU can discard incorrect configurations or report them back to the operator of the localized service (e.g., the mobile network operator (MNO) or the third-party service operator). The WTRU's NAS layer can pass location validity information to the WTRU's access stratum layer to ensure that the access layer knows the valid list of TAC / NR cells providing access to the localized service and ensures that cell selection and / or reselection is limited to the valid list of TACs / cells. The WTRU can provide location validity information (e.g., a list of valid TACs / cells) to the RAN node. This ensures that the RAN node is aware of the ongoing localized service and will not switch the WTRU's session to a location that does not support the ongoing localized service. The WTRU can restrict the generation or provision of measurement reports to cells that are part of the location validity information. This ensures that cell selection, reselection, and / or handover do not move the WTRU to a location that may interrupt ongoing localization services.

[0071] The following abbreviations are used in this article: AF: Application Functions EHPLMN: Equivalent Attribution to PLMN eHN: Equivalent Hosted Network FPLMN: Banning PLMN eSNPN: Equivalent SNPN GUI: Graphical User Interface HPLMN: Home Public Land Mobile Network IE: Information Elements MS: Mobile Station NG: Next Generation NS: Network Slicing NSSAI: Network Slice Selection Auxiliary Information NSSAA: Network Slice Specific Authentication and Authorization NWDAF: Network Data Analysis Function OPLMN: Operator-controlled PLMN (selection list) PALS: Provides access to localized services PLMN: Public Land Mobile Network PNI-NPN: Public Network Integrated NPN RA: Registration Area RFSP: RAT / Frequency Selection Priority RPLMN: Registered Public Land Mobile Network S-NSSAI: Single NSSAI SIM: Subscriber Identity Module SoR-SNPN-SI-LS: SoR SNPN selection information for localized services TA: Tracking Area TAI: TA identity UE: User Equipment UICC: General Purpose Integrated Circuit Card USIM: UICC with SIM VPLMN: Visiting public terrestrial mobile networks.

[0072] Localized services in non-public networks (NPNs) can be provided. These localized services may include those provided by the NPN in a region (e.g., only in that region), at a certain time (e.g., during one or more specific time periods), or both.

[0073] Localized services can be provided within a standalone NPN (SNPN). These localized services may include those provided by the SNPN in a region (e.g., only in that region), at a certain time (e.g., during one or more specific time periods), or both.

[0074] For example, a guide (SOR-SNPN-SI-LS) can be provided for selecting a roaming SNPN for localization services within the SNPN. A mobile station (MS) or WTRU can use SOR-SNPN-SI-LS to support access to the SNPN, which can provide access to localization services. SOR-SNPN-SI-LS can include a credential holder-controlled priority list for preferred SNPNs for accessing localization services via the SNPN. Entries in the priority list (e.g., each entry) can include one or more of SNPN identity, validity information, or location-aided information, where the validity information may include time validity information and / or location validity information.

[0075] SOR-SNPN-SI-LS may include a credential holder control priority list for preferred network selection group IDs (GINs) used to access localized services via one or more SNPNs. Entries in the credential holder control priority list (e.g., each entry) may include the network selection group ID (GIN), validity information (e.g., time validity information and / or location validity information), and / or location-related information.

[0076] The terms WTRU and MS are used interchangeably in this article.

[0077] A WTRU can perform multiple actions associated with the processing of location validity information. A WTRU can (e.g., in...) Figure 2 The location validity information (e.g., for localization services) can be received at two locations. The location validity information may include a cell identifier, a tracking area identifier, or a list of tracking area codes (TACs), which may indicate one or more valid areas for accessing localization services. Location validity information (e.g., messages associated with the SoR) can be received within the SoR container.

[0078] WTRU can (e.g., in) Figure 3 Location validity information is provided to RAN nodes (e.g., base stations) via RRC layer messages at 6 locations. Since location validity information can be provided to WTRUs within the SoR container, this information can be transparent (e.g., unknown) to one or more network nodes (e.g., AMF, gNB, etc.), which may result in the information being passed without checking its content.

[0079] WTRU NAS layers can (e.g., in) Figure 3 The WTRU AS layer provides location validity information (e.g., a list of valid TACs or cell IDs identifying cells such as NR cells) to the WTRU access layer (7 locations). The WTRU AS layer can ensure that cell selection or reselection is limited to valid TACs or NR cells. Restricting cell selection and / or reselection to valid locations ensures seamless continuity of ongoing localization services.

[0080] Because the WTRU AS layer can have location validity information, the WTRU AS layer (e.g., in...) Figure 3 The eight locations (e.g., to indicate PCI physical cell ID and / or signal strength) can ensure that such cells belong to a valid TAC / NR cell list when generating measurement reports for cells (e.g., neighboring cells of the WTRU's currently serving cell). The WTRU can decide not to report measurements of cells that do not belong to the TAC / NR cell list (e.g., as indicated by location validity information) (e.g., measurements can be skipped) to ensure seamless continuity of ongoing localization services.

[0081] WTRUs can perform multiple actions to handle incorrect location validity information. WTRUs (for example, in...) Figure 2 The correctness of the location validity information for each entry in the SNPN selection list that may be included in the location validity information can be verified at two points. As described herein, these lists may be provided as part of SOR-SNPN-SI-LS and may include location validity information indicating a valid geographic location, valid tracking area code, and / or valid cell (e.g., NR cell) indicating localized services. Verifying the correctness of the location validity information may include detecting invalid configurations in the location validity information. For example, the WTRU may detect invalid configurations when the NR cell list includes cells belonging to tracking areas that are not part of the list of valid tracking area codes provided in the location validity information (e.g., conflicting information between valid NR cells and valid TACs). As another example, the WTRU may detect invalid configurations when there are encoding problems with location validity information elements (e.g., invalid encoding of TAC / cell IDs). As yet another example, the WTRU may detect invalid configurations when it receives an indication that location validity information exists, but the encoding does not include a list of TACs or cells (e.g., NR cells). Invalid configurations of location validity information can be examples of incorrect configurations of the location validity information. Examples of valid configurations of location validity information can include non-contradictory location validity information, such as a list of valid TACs or a list of valid NR cell IDs.

[0082] In the example, if WTRU detects a misconfiguration (e.g., in...), Figure 2 If the WTRU is located at any of the three points mentioned above, it can notify the network (e.g., AMF) via NAS control plane signaling, such as a UL NAS transmission message, which includes the payload container IE set to a SoR transparent container and / or the WTRU status / acknowledgment. The WTRU may include defined bits, such as the SOR-SNPN-SI-LS-misconfiguration bit, and set it to true to inform the network (e.g., AMF) of misconfiguration of the SNPN selection information used for localization services. Upon receiving a UL NAS transmission message with the SOR-SNPN-SI-LS-misconfiguration bit set to true, the network (e.g., AMF) can pass this information to a third-party operator that may provide localization services via the network (e.g., via NEF).

[0083] In the example, if WTRU detects a misconfiguration (e.g., in...), Figure 2If there are 4 such locations, then the WTRU may decide not to use location validity information to select the SNPN to access localized services (e.g., the WTRU may or may not notify the network of this decision).

[0084] For example, network devices like AMF can perform multiple actions to process location validity information. For instance, AMF can receive registration requests (e.g., in...). Figure 3 (3 places), the registration request may include the identity of the localized service.

[0085] AMF can determine the identity of localized services (e.g., in...) Figure 3 The four locations (e.g., a set of cells, tracking areas, and / or RAT / Frequency Selection Priority (RFSP) indices that may be associated with the location where localized services may be available) include, for example, a set of cells, tracking areas, and / or RAT / Frequency Selection Priority (RFSP) indices. In response to the AMF sending the identity of the localized service to the UDM / UDR, the AMF can obtain (e.g., receive) the set of cells or tracking areas from the UDM / UDR. In response to the AMF sending the identity of the localized service to the PCF, the AMF can obtain (e.g., receive) the RFSP indices from the PCF. The AMF may send the set of cells, tracking areas, or RFSP indices to the RAN node (e.g., in...). Figure 3 (4 locations), which allows the RAN node to configure the WTRU to prioritize cells that can support localized services.

[0086] A non-public network (NPN) can be provided. An NPN can be a system deployed for non-public use (e.g., 5GS). An NPN can be a standalone NPN (SNPN), such as an NPN operated by an NPN operator and not dependent on network functionality provided by a PLMN. An NPN can be a public network integrated NPN (PNI-NPN), such as a non-public network deployed with PLMN support.

[0087] An NPN may be intended for use by a private entity, such as a business or factory. An NPN can be identified by a combination of a PLMN ID and a Network Identifier (NID), where the PLMN ID can be, for example, a PLMN ID reserved for a private network (e.g., where the Mobile Country Code = 999).

[0088] The architecture of an SNPN (e.g., a 5G SNPN) can be based on the architecture of other wireless communication systems, such as 5G systems. For example, one or more NG-RANs of an SNPN can be configured to broadcast a combination of PLMN ID and NID. A WTRU operating in SNPN access mode can read broadcast system information of available combinations of PLMN ID and NID, and can select an SNPN for which the WTRU has subscriptions and / or credentials.

[0089] A Public Network Integrating Non-Public Network (PNI-NPN) can be provided. A PNI-NPN can be a non-public network available using PLMN infrastructure / resources, such as, for example, a PLMN network slice. A group of PLMN users allowed access to a PNI-NPN can be referred to as a Closed Access Group (CAG), and a CAG can be identified by a CAG identifier. CAG users can access (e.g., access only) a PNI-NPN from a cell that supports CAG access; this cell can be referred to as a CAG cell. A CAG cell can broadcast a list of CAG identifiers it supports. A CAG WTRU can be configured by the network with a list of CAGs that the WTRU can access (e.g., via a list of allowed CAGs). When a CAG WTRU detects a CAG cell, it can selectively and / or access that CAG cell if at least one broadcast CAG identifier matches a CAG identifier in the WTRU's list of allowed CAGs.

[0090] Networks that provide access to localized services (e.g., 5G networks) can be referred to as PALS networks. In some cases, cellular networks can be deployed to provide services to local users within a specific area. For example, temporary, non-public cellular networks can be established to provide streaming video services to audiences of live concerts or football matches. As another example, cellular networks can be deployed to provide localized services, such as commercial advertising in shopping malls, in places where large crowds may gather, like airports, shopping malls, and campuses. Services provided by these networks (e.g., they can be small) have at least two characteristics: the services are localized, for example, they are related to activities / events in a particular location or area and can be associated with users in that area; and users can access the services on demand or temporarily rather than periodically.

[0091] System enhancements such as 5G system enhancements can provide localized services and enable users to access managed networks through which these services can be provided. In the description provided herein, localized services may also be referred to as PALS services, and networks providing PALS services may be referred to as PALS networks, PALS managed networks, or managed networks.

[0092] The managed network for WTRU and / or localized services can be a standalone non-public network (SNPN), a public network integrated non-public network (PNI-NPN), or a PLMN. The local service provider can be the operator of the managed network or a third-party service provider.

[0093] The selection of a hosting network can be performed, for example, by the WTRU, and the selection process may include the WTRU performing a radio scan to check the availability of an SNPN that provides access to localized services at the WTRU’s current location, and attempting to register with the selected SNPN (e.g., the hosting network) based on one or more rules.

[0094] The WTRU can (e.g., at power-on or after recovery from coverage loss) select the SNPN / hosted network to which it last registered using NG-RAN access technology (e.g., if it is available) and can perform the registration process to the SNPN / hosted network. If the SNPN / hosted network to which the WTRU last registered is unavailable, the WTRU can scan one or more RF channels in the NR band, depending on its capabilities, to find one or more available SNPN / hosted networks. On a carrier (e.g., a channel), the WTRU can search for strong cells (e.g., the strongest cell) and read their system information (e.g., to determine which SNPN / hosted network the cell belongs to). If there is no SNPN / hosted network to which it last registered, or if registration is impossible due to the unavailability of the SNPN / hosted network, or if registration fails, the WTRU can follow one or more of the processes described herein, depending on its SNPN selection mode (e.g., automatic selection mode versus manual selection mode).

[0095] As described herein, the WTRU can initially select the network to provide access to localized services. As mentioned above, localized services may be available at specific times (e.g., time periods) and / or at specific locations (e.g., tracking areas or cells). Existing procedures do not provide a means for the WTRU to maintain access to localized services (e.g., when there is an active session accessing the localized service). System enhancements, such as 5G system enhancements, can be provided to ensure service continuity and to ensure that cell selection and reselection (e.g., for idle and / or connection mode mobility) do not move the WTRU to a service area / location that does not support or interrupts the ongoing localized service.

[0096] As described herein, system enhancements, such as 5G system enhancements, can be made to the cell selection and / or reselection aspects of the managed network to ensure seamless idle and connected mode mobility without disruption. Upon receiving managed network selection information (e.g., via SOR-SNPN-SI-LS and / or SOR transparent containers), the WTRU can verify the correctness of location validity information provided by the network or a third-party operator. The WTRU can discard incorrect configurations or report them back to the operator of the localized service (e.g., which could be an MNO or a third-party service operator). The WTRU's NAS layer can pass location validity information to the access layer to ensure that the access layer knows the valid list of TAC / NR cells providing access to the localized service, and / or ensure that cell selection and reselection are limited to the valid list of TACs / cells. For example, the WTRU can provide location validity information (e.g., a list of valid TACs / cells) to the RAN node to ensure that the RAN node is aware of the ongoing localized service and will not switch the WTRU's session to a location that does not support the ongoing localized service. The WTRU can be enhanced to limit the generation and / or provision of measurement reports to cells as part of location validity information, further ensuring that cell reselection and / or handover do not move the WTRU to a location that interrupts ongoing localization services.

[0097] It can provide the reception and verification of location validity information. Figure 2 An example process for receiving and verifying location validity information is shown, which may be part of the SNPN selection information used for localization services (e.g., received via SOR-SNPN-SI-LS).

[0098] exist Figure 2 At point 0, the WTRU can successfully register with the network (e.g., a 5G network). Both the WTRU and the network can support the guidance of roaming SNPN selection information (SOR-SNPN-SI-LS) for localized services within the SNPN.

[0099] exist Figure 2At one point, the network (e.g., a 5G network) can provide SOR-SNPN-SI-LS to the WTRU via NAS control plane signaling. For example, a DL NAS transport message can be sent to the WTRU, and the DL NAS transport message can include a payload container containing SOR-SNPN-SI-LS. The WTRU can replace existing SOR-SNPN-SI-LS (e.g., SOR-SNPN-SI-LS for selected entries in the subscriber data list, or SOR-SNPN-SI-LS associated with a selected PLMN subscription) with the received SOR-SNPN-SI-LS. One or more lists (e.g., "Certificate holder control priority list for preferred SNPNs for access to localized services in the SNPN" and / or "Certificate holder control priority list for preferred GINs for access to localized services in the SNPN") can be provided as part of the SOR-SNPN-SI-LS.

[0100] exist Figure 2 At two points, the WTRU can verify the correctness of location validity information (e.g., each entry in the SNPN selection list), which can be provided as part of SOR-SNPN-SI-LS. These lists may include location validity information such as geographic location, a list of valid Tracking Area Codes (TACs), and / or a list of valid NR cells, which can be used to access localized services. Verifying the correctness of location validity information may include detecting invalid configurations in the location validity information. For example, the WTRU can detect invalid configurations when the list of NR cells in the location validity information includes cells belonging to tracking areas that are not part of the list of valid Tracking Area Codes provided by the location validity information (e.g., conflicting location information between valid TACs and NR cells indicated by the location validity information). For example, the WTRU can detect invalid configurations when one or more location validity information elements have encoding problems, such as invalid encoding of TAC / cell IDs. When referred to herein, encoding problems may include problems encountered by the decoding device (e.g., the WTRU) when the decoding device attempts to decode the received information (e.g., decoding does not produce unique information or results, the decoded information overlaps or is inconsistent with other information, etc.). For example, when the WTRU receives an indicator that may contain location validity information, but the associated encoded information does not include a list of TACs or NR cells, the WTRU can detect an invalid configuration. An invalid configuration can be an example of a misconfiguration. An example of a valid configuration for location validity information can be a configuration that includes non-contradictory elements (e.g., a list of valid TACs or a list of valid NR cell IDs).

[0101] exist Figure 2At point 3, if the WTRU detects a misconfiguration, it can notify the network (e.g., AMF) of the misconfiguration via NAS control plane signaling. For example, the WTRU can send a UL NAS transport message where the payload container IE is set to SOR transparent container and / or WTRU status / acknowledgment. The WTRU can include a newly defined bit in the message, such as SOR-SNPN-SI-LS-Misconfiguration, and set it to true to inform the network (e.g., AMF) of the misconfiguration of the SNPN selection information used for localization services. Upon receiving a UL NAS transport message with the SOR-SNPN-SI-LS-Misconfiguration bit set to true, the network (e.g., AMF) can pass this information to a third-party operator (e.g., via NEF) that may be providing localization services.

[0102] exist Figure 2 At point 4, the WTRU may choose not to use the location validity information to select the SNPN for accessing localized services when it detects a misconfiguration of the location validity information (e.g., as part of SOR-SNPN-SI-LS). (For example, the WTRU may do this without notifying the network.)

[0103] It can provide processing of location validity information. Figure 2 An example process can be shown to illustrate how WTRU receives and verifies the validity of location validity information. Figure 3 An example procedure can be shown to illustrate how a WTRU can process location validity information (e.g., it can be provided as part of SOR-SNPN-SI-LS).

[0104] exist Figure 3 At point 1, WTRU can receive triggers from the application layer, user input via the GUI, AT commands, etc., to access localized services.

[0105] exist Figure 3 At point 2, if the WTRU supports access to the SNPN that provides access to the localized service, the localized service can be enabled, and the WTRU may have previously received SNPN selection information for the localized service (e.g., via SOR-SNPN-SI-LS). The WTRU can trigger SNPN selection to ensure that the WTRU can find a cell that meets the validity criteria associated with access to the localized service (e.g., regarding time and / or location conditions according to the provided SOR-SNPN-SI-LS). The WTRU can reside on a cell that meets the validity criteria (e.g., regarding the time and / or location conditions specified in SOR-SNPN-SI-LS).

[0106] exist Figure 3At point 3, the WTRU can send a registration request message to the network (e.g., SNPN), indicating that the WTRU has enabled the localization service and wants to register to access the localization service.

[0107] exist Figure 3 At four points, the AMF (Area Function) of the SNPN (Site-Native Provider Provider) that may be providing localized services can use a registration request from the WTRU (Site-Wide Provider Root) as a trigger to collect information about location validity information (a list of valid TAC / NR cells) associated with the localized service and pass this information to the RAN (Radio Node Provider) to help ensure seamless localized service continuity for the WTRU (e.g., for handover and cell reselection in connected mode, cell selection in idle mode, etc.). The AMF may not have location validity information because the localized service may be provided by a third-party operator. In this case, the AMF can obtain location validity information from the UDM / UDR (e.g., this information may already be stored in the UDM / UDR by the SoR-AF). The AMF can send a query to the UDM / UDR, which can include the identity of the localized service provided in the registration request message. The UDM / UDR can reply to the AMF with a message including the location validity information associated with the localized service. The AMF can send the location validity information to the RAN node, allowing the RAN node to adjust the WTRU's cell selection / reselection priorities to favor cells where the localized service is available. The RAN node can send the adjusted priorities to the WTRU in an RRC (Registered Redirect Message) message.

[0108] In the example, the AMF can send a query to the PCF, which can include the identity of the localized service provided in the registration request message. The PCF can reply to the AMF with a message including location validity information (or an RFSP index based on the localized service identity or location validity information). The AMF can send the location validity information (or RFSP index) to the RAN node, allowing the RAN node to adjust the WTRU's cell selection / reselection priority to favor cells where the localized service is available. The RAN node can then send the adjusted priority to the WTRU in an RRC message.

[0109] In the example, the AMF can send a localized service identifier to the RAN node, and if the RAN node has already pre-configured the identity of the cell for which localized services are available, the RAN node can use the localized service identifier to determine how to configure the cell selection / reselection priority of the WTRU.

[0110] AMF can send location validity information (e.g., in the SoR container) to WTRU. AMF can obtain location validity information from other network nodes or functions (e.g., from UDM or from SoR-AF) and send it to RAN nodes (e.g., because the contents of the SoR container sent by AMF to WTRU may be transparent to AMF and not available for sharing with RAN nodes).

[0111] exist Figure 3 At point 5, the AMF can respond to the WTRU with a registration accept message, and the AMF can include location validity information (e.g., a valid list of TAC / NR cells as part of the Tracking Area Identity (TAI) list) in the registration accept message to ensure that the WTRU does not perform a WTRU mobility registration update when it moves within a valid TAC. It should be noted that performing a WTRU mobility registration update while moving within a valid TAC may not cause problems, but avoiding this could reduce or minimize the amount of signaling initiated by the WTRU.

[0112] In the example, Figure 3 At point 6, the WTRU can provide location validity information to the RAN node via RRC messages (e.g., it can perform the operation shown at point 6 instead of point 4). The WTRU can send this information to the RAN node, allowing the RAN node to adjust the WTRU's cell selection / reselection priority to favor cells with available local services. The RAN node can send the adjusted priority to the WTRU in an RRC message.

[0113] exist Figure 3 At point 7, the WTRU can (e.g., via the NAS layer) provide location validity information to the WTRU's Access Layer (AS) layer, including, for example, a list of valid TAC or NR cell IDs. The WTRU AS layer ensures that cell selection or reselection is limited to TAC or NR cells where the localization service is available (e.g., TAC or NR cells correspond to valid locations for the localization service). Restricting cell selection and reselection to those valid locations ensures seamless continuity of ongoing localization services.

[0114] exist Figure 3At point 8, since the WTRU AS layer can have location validity information, when the WTRU performs measurement reporting on a cell (e.g., a neighboring cell), such as when determining the cell's PCI physical cell ID or signal strength, it can ensure that the cell belongs to the list of valid TAC / NR cells, and the WTRU can decide not to perform or report measurements on cells that do not belong to the list of valid TAC / NR cells indicated by the location validity information (e.g., to ensure the seamless continuity of ongoing localization services).

[0115] In the example, the WTRU described herein may include a processor configured to perform one or more of the following operations: The WTRU may receive a first message from a first network node. The first message may indicate location validity information of the service. The WTRU may send a second message to a second network node. The second message may indicate location validity information of the service. The WTRU may use the location validity information of the service to determine a valid cell. The WTRU may generate a measurement report associated with the valid cell and may send a third message to the second network node. The third message may indicate the measurement report of the valid cell. In the example, the location validity information may include at least one of a list of one or more cell identifiers or a list of one or more tracking area identifiers. In the example, the first message may be received in a Roaming Bootstrap (SoR) container. In the example, the second message may be a Radio Resource Control (RRC) message. In the example, the Roaming Bootstrap (SoR) container may be used to send the second message. In the example, the WTRU may be configured to determine a valid cell using the location validity information of the service by determining a valid identifier of the cell, wherein the valid identifier may be at least one of a tracking area code or a cell identifier. The cell identified by the valid identifier may be used to perform a cell selection or cell reselection process.

[0116] In the examples, the WTRU described herein may include a processor configured to perform one or more of the following operations: The WTRU may determine that received location verification information is invalid based on an independent non-public network (SNPN) selection list. The WTRU may send a message to the network node indicating that the location verification information is invalid. The location verification information may include at least one of a geographic location, one or more Tracking Area Codes (TACs), or one or more Cell Identifiers (IDs), and the location verification information may be determined to be invalid in response to detecting an invalid configuration associated with the cell. In the examples, the WTRU determining that the location verification information is invalid for the cell may include the WTRU determining that the cell belongs to a tracking area associated with the invalid tracking area code. In the examples, the WTRU determining that the location verification information is invalid for the cell may include the WTRU determining that the cell belongs to a tracking area not associated with the location verification information. In the examples, the message sent by the WTRU to the network node may be an uplink (UL) non-access stratum (NAS) transport message. In the examples, such a message may include at least one of a Roaming Bootstrap (SoR) container, a WTRU status indication, or an acknowledgment.

[0117] In the example, the first network node may include a processor configured to perform one or more of the following operations: The first network node may receive a registration request, which may indicate the identity of the service. The first network node may use the identity of the service to determine localized service information. The first network node may send a message to a second network node, and this message may indicate localized service information. In the example, the localized service information may include at least one of a set of cell, tracking area, or radio access technology (RAT) frequency selection priority (RFSP) indices. In the example, the first network node using the identity of the service to determine the localized service information may include the first network node receiving a response message from a third network node, which may indicate at least one of a set of cell, tracking area, or radio access technology (RAT) frequency selection priority (RFSP) indices. In the example, the third network node may provide at least one of Unified Data Management (UDM) functionality, Unified Data Warehouse (UDR) functionality, or Access Management Function (AMF).

[0118] Although the features and elements described above are described in specific combinations, each feature or element may be used alone without other features and elements of the preferred embodiment, or in various combinations with or without other features and elements.

[0119] The processor then uses the location validity information of the service to determine the valid cell. After this determination, the processor generates a measurement report associated with the valid cell. The processor's final task may be to send a third message to a second network node. This third message is designed to indicate the measurement report of the valid cell. While the implementation described herein may consider 3GPP-specific protocols, it should be understood that the implementation described herein is not limited to this scenario and can be applied to other wireless systems. For example, although the solution described herein considers LTE, LTE-A, New Radio (NR), or 5G-specific protocols, it should be understood that the solution described herein is not limited to this scenario and is also applicable to other wireless systems.

[0120] The above processes can be implemented in computer programs, software, and / or firmware contained in computer-readable media for execution by a computer and / or processor. Examples of computer-readable media include, but are not limited to, electronic signals (transmitted via wired and / or wireless connections) and / or 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 storage devices, magnetic media (e.g., but not limited to internal hard disks and removable disks), magneto-optical media, and / or optical media (e.g., CD-ROM discs and / or digital versatile discs (DVDs)). The processor associated with the software can be used to implement a radio frequency transceiver used in WTRUs, terminals, base stations, RNCs, and / or any host.

Claims

1. A wireless transceiver unit (WTRU), the WTRU comprising: Processor, wherein the processor is configured to: Receive validity information associated with the service from the first network node, wherein the validity information indicates one or more valid regions for accessing the service; Based at least on validity information and information about the wireless communication cell, determine whether the WTRU can access services via the wireless communication cell; and At least based on the determination that the WTRU can access the service via the wireless communication cell: Perform measurements associated with the wireless communication cell; and A message is sent to the second network node, indicating the result of the measurement.

2. The WTRU according to claim 1, wherein, Measurements are associated with cell selection or reselection.

3. The WTRU according to claim 1 or 2, wherein, The validity information further indicates one or more valid time periods for accessing the service, and the processor is configured to further determine whether the WTRU can access the service via the wireless communication cell based on one or more valid time periods.

4. The WTRU according to any one of claims 1-3, wherein, Validity information includes one or more tracking area identifiers or cell identifiers, which indicate one or more valid areas for accessing the service.

5. The WTRU according to any one of claims 1-4, wherein, The information about a wireless communication cell used by the WTRU to determine whether the WTRU can access services via the wireless communication cell includes the wireless communication cell's tracking area identifier or cell identifier.

6. The WTRU according to any one of claims 1-5, wherein, The processor is configured to receive service-related validity information, including verifying the correctness of the validity information against a list of pre-configured networks or cells.

7. The WTRU according to claim 6, wherein, The processor is configured to determine that the validity information is incorrect if the validity information indicates that the network or cell is not on the list of pre-configured networks or cells.

8. The WTRU according to any one of claims 1-7, wherein, The first network node includes access and mobility functions for the wireless communication network, and the second network node includes a base station for the wireless communication network.

9. The WTRU according to claim 8, wherein, Wireless communication networks are non-public networks.

10. The WTRU according to any one of claims 1-9, wherein, The processor is also configured to send validity information associated with the service to the second network node.

11. The WTRU according to any one of claims 1-10, wherein, A wireless communication cell is a neighboring cell of the WTRU's current serving cell.

12. The WTRU according to any one of claims 1-11, wherein, The processor is configured to receive validity information via messages associated with roaming guidance.

13. The WTRU according to any one of claims 1-12, wherein, In response to determining that the WTRU cannot access services via the wireless communication cell, the processor is configured to skip the measurement of the wireless communication cell.

14. A method implemented by a wireless transmit / receive unit (WTRU), the method comprising: Receive validity information associated with the service from the first network node, wherein the validity information indicates one or more valid regions for accessing the service; Based at least on validity information and information about the wireless communication cell, determine whether the WTRU can access services via the wireless communication cell; and In response to determining that the WTRU can access services via wireless communication cells: Perform measurements associated with the wireless communication cell; and A message is sent to the second network node, indicating the result of the measurement.

15. The method according to claim 14, wherein, Measurements are associated with cell selection or reselection.

16. The method according to claim 14 or 15, wherein, The validity information further indicates one or more valid time periods for accessing the service, and the determination of whether the WTRU can access the service via the wireless communication cell is further based on one or more valid time periods.

17. The method according to any one of claims 14-16, wherein, Validity information includes one or more tracking area identifiers or cell identifiers, which indicate one or more valid areas for accessing the service.

18. The method according to any one of claims 14-17, wherein, Receiving validity information associated with a service includes verifying the correctness of the validity information by comparing it against a list of pre-configured networks or cells.

19. The method according to any one of claims 14-18, further comprising sending validity information associated with the service to the second network node.

20. The method according to any one of claims 14-19, wherein, A wireless communication cell is a neighboring cell of the WTRU's current serving cell.

Images