Transmitting enhanced information to a user equipment (UE) in a standalone private network (SNPN)

Abstract

Various aspects of the present disclosure relate to providing information regarding a UE's capabilities to a network, thereby enabling the network to send extended information (e.g., an extended SOR-SNPN-SI) to a UE that can process and appropriately utilize such information. For example, a UE can provide its 5GMM capability information to the network during the registration procedure, and in response, the network can provide a list of SNPN / GINs that can include the extended information (e.g., via various container IE configurations).

Description

[Technical Field]

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS This application claims priority to U.S. Provisional Patent Application No. 63 / 485,483, filed February 16, 2023, entitled "TRANSMITTING EXTENDED INFORMATION TO USER EQUIPMENT (UE) IN A STANDALONE NON-PUBLIC NETWORK (SNPN)," the disclosure of which is incorporated herein by reference in its entirety.

[0002] The present disclosure relates to wireless communications, and more particularly, to communications between user equipment (UE) and a Standalone Non-Public Network (SNPN). [Background technology]

[0003] A wireless communication system may include one or more network communication devices, such as base stations, which may also be known as eNodeBs (eNBs), next-generation NodeBs (gNBs), or other appropriate terminology. Each network communication device, such as a base station, may support wireless communication for one or more user communication devices, which may also be known as user equipment (UEs), or other appropriate terminology. A wireless communication system may support wireless communication with one or more user communication devices by utilizing wireless communication system resources (e.g., time resources, (e.g., symbols, slots, subframes, frames, etc.)) or frequency resources (e.g., subcarriers, carriers). Additionally, a wireless communication system may support wireless communication over various radio access technologies, including third-generation (3G) radio access technology, fourth-generation (4G) radio access technology, fifth-generation (5G) radio access technology, or other suitable radio access technology beyond 5G (e.g., sixth-generation (6G)).

[0004] A Non-Public Network (NPN) facilitates the deployment of 5G access technology in private use or environments, such as networks dedicated to a single organization. One type of NPN is the SNPN, which is operated by an NPN operator and provides its own network functions without utilizing network functions provided by a Public Land Mobile Network (PLMN). Summary of the Invention [Problem to be solved by the invention]

[0005] The present disclosure relates to methods, apparatus, and systems that support providing information regarding a UE's capabilities to a network, thereby enabling the network to send extended information (e.g., Steering Standalone Private Network Selection Information for Enhanced Roaming, or SOR-SNPN-SI) to a UE that is capable of processing and appropriately utilizing such information. For example, a UE may provide its 5GMM capability information to the network during the registration procedure, and in response, the network may provide (e.g., via various container information element (IE) configurations) a list of SNPNs and / or Group Identities for Networks (GINs) that can contain the extended information. [Means for solving the problem]

[0006] Some implementations of the methods and apparatus described herein may further include a UE comprising at least one memory and at least one processor coupled to the at least one memory and configured to cause the UE to send an indication to a network function that the UE supports the extended SOR-SNPN-SI and to receive from the network function a list of SNPNs and / or GINs that support the extended SOR-SNPN-SI.

[0007] In some implementations of the methods and apparatus described herein, the UE sends the indication via a registration request message sent during the initiated registration procedure.

[0008] In some implementations of the methods and apparatus described herein, the UE receives a list of SNPNs and / or GINs via a registration accept message.

[0009] In some implementations of the methods and apparatus described herein, the indication is a bit within a 5GMM capability information element.

[0010] In some implementations of the methods and apparatus described herein, the UE sends a second indication that the UE supports the enhanced SOR-SNPN-SI via the registration complete message to confirm receipt of the list of SNPNs and / or GINs.

[0011] In some implementations of the methods and apparatus described herein, the second indication is a bit in a SOR transparent container information element.

[0012] In some implementations of the methods and apparatus described herein, the processor is further configured to cause the UE to receive a request from the network function to confirm receipt of the list of SNPNs and / or GINs that support the extended SOR-SNPN-SI, and to send a confirmation of the list to the network function.

[0013] In some implementations of the methods and apparatus described herein, the UE acknowledges receipt of the list of SNPNs and / or GINs that support the extended SOR-SNPN-SI by transmitting its capability to receive the list of SNPNs and / or GINs that support the extended SOR-SNPN-SI.

[0014] In some implementations of the methods and apparatus described herein, the indication includes an indication that the UE supports validity time information and / or validity area information for the SNPN and / or GIN.

[0015] Some implementations of the methods and apparatus described herein may further include a processor for wireless communication comprising at least one controller coupled to the at least one memory and configured to cause the processor to send an indication to a network function that the processor supports the extended SOR-SNPN-SI and to receive from the network function a list of SNPNs and / or GINs that support the extended SOR-SNPN-SI.

[0016] Some implementations of the methods and apparatus described herein further include a method performed by a UE, the method including sending an indication to a network function that the UE supports the extended SOR-SNPN-SI, and receiving from the network function a list of SNPNs and / or GINs that support the extended SOR-SNPN-SI.

[0017] In some implementations of the methods and apparatus described herein, the UE sends the indication via a registration request message sent during the initiated registration procedure.

[0018] In some implementations of the methods and apparatus described herein, the UE receives a list of SNPNs and / or GINs via a registration accept message.

[0019] In some implementations of the methods and apparatus described herein, the UE sends a second indication that the UE supports the enhanced SOR-SNPN-SI via the registration complete message to confirm receipt of the list of SNPNs and / or GINs.

[0020] In some implementations of the methods and apparatus described herein, the second indication is a bit in a SOR transparent container information element.

[0021] In some implementations of the methods and apparatus described herein, the indication is a bit within a 5GMM capability information element.

[0022] In some implementations of the methods and apparatus described herein, the UE receives a request from a network function to confirm receipt of a list of SNPNs and / or GINs that support the extended SOR-SNPN-SI and sends a confirmation of the list to the network function.

[0023] In some implementations of the methods and apparatus described herein, the UE acknowledges receipt of the list of SNPNs and / or GINs that support the extended SOR-SNPN-SI by transmitting its capability to receive the list of SNPNs and / or GINs that support the extended SOR-SNPN-SI.

[0024] In some implementations of the methods and apparatus described herein, the indication includes an indication that the UE supports validity time information and / or validity area information for the SNPN and / or GIN.

[0025] Some implementations of the methods and apparatus described herein may further include a network function comprising at least one memory and at least one processor coupled to the at least one memory and configured to cause the network function to determine whether to send an extended SOR-SNPN-SI to the UE for an SNPN and / or GIN that supports the extended SOR-SNPN-SI, and to send a list of SNPNs and / or GINs to the UE based on the determination.

[0026] In some implementations of the methods and apparatus described herein, the processor is configured to cause the network function to determine whether to send the enhanced SOR-SNPN-SI for the SNPN and / or GIN based on user subscription information associated with the UE for localized services provided by the SNPN and / or GIN and UE capability information for receiving a list of SNPNs and / or GINs that support the enhanced SOR-SNPN-SI.

[0027] In some implementations of the methods and apparatus described herein, localized services are identified by time validity information and / or location validity information in the extended SOR-SNPN-SI.

[0028] In some implementations of the methods and apparatus described herein, the UE capability information is received via a registration message sent by the UE to a network function during an initial registration procedure.

[0029] In some implementations of the methods and apparatus described herein, a network function sends the list of SNPNs and / or GINs to the UE via a network entity, where the network entity is an Access and Mobility Management Function (AMF), using a SOR Transparent Container information element in a Registration Accept message or a Downlink (DL) Non-Access-Stratum (NAS) Transfer message.

[0030] In some implementations of the methods and apparatus described herein, the processor is further configured to cause the network function to send a request for an acknowledgment for receiving the list of SNPNs and / or GINs from the UE, wherein the network function receives the information via a network entity, the network entity being an AMF, and receives the UE's capability information for receiving the list of SNPNs and / or GINs via a SOR Transparent Container information element in the Registration Complete message or the UL NAS Transport message.

[0031] In some implementations of the methods and apparatus described herein, the network function is a Unified Data Management (UDM) function.

[0032] In some implementations of the methods and apparatus described herein, a network function sends a request to a Steering of Roaming Application Function (SOR-AF) to create an SOR transparent container, the request including UE capability information and UE subscription information for localized services.

[0033] Some implementations of the methods and apparatus described herein may further include a method performed by a network function, the method including determining whether to send an extended SOR-SNPN-SI for an SNPN and / or GIN that supports the extended SOR-SNPN-SI to the UE, and sending a list of SNPNs and / or GINs to the UE based on the determination.

[0034] In some implementations of the methods and apparatus described herein, determining whether to send an extended SOR-SNPN-SI for an SNPN and / or GIN is based on user subscription information associated with the UE for localized services provided by the SNPN and / or GIN and UE capability information for receiving a list of SNPNs and / or GINs that support the extended SOR-SNPN-SI.

[0035] In some implementations of the methods and apparatus described herein, localized services are identified by time validity information and / or location validity information in the extended SOR-SNPN-SI.

[0036] In some implementations of the methods and apparatus described herein, the UE capability information is received via a registration message sent by the UE to a network function during an initial registration procedure.

[0037] In some implementations of the methods and apparatus described herein, the network function sends the list of SNPNs and / or GINs to the UE via a SOR Transparent Container information element in a registration accept message or a downlink (DL) NAS transport message.

[0038] In some implementations of the methods and apparatus described herein, the method includes sending a request for an acknowledgment for receiving the list of SNPNs and / or GINs from the UE, wherein a network function receives the information via a network entity, the network entity being an AMF, and receives the UE's capability information for receiving the list of SNPNs and / or GINs via a SOR Transparent Container information element in a Registration Complete message or a UL NAS Transport message.

[0039] In some implementations of the methods and apparatus described herein, the network function is a UDM function.

[0040] In some implementations of the methods and apparatus described herein, a network function sends a request to the SOR-AF to create an SOR transparent container, the request including UE capability information and UE subscription information for localized services. [Brief explanation of the drawings]

[0041] [Figure 1] FIG. 1 illustrates an example of a wireless communication system supporting communication between a UE and an SNPN, according to aspects of the present disclosure. [Figure 2] FIG. 1 illustrates an example diagram that supports providing enhanced information to a UE during a registration procedure, according to an aspect of the present disclosure. [Figure 3]FIG. 10 illustrates an example diagram supporting a modified 5GMM capabilities information element with extension information, according to an aspect of the present disclosure. [Figure 4A] FIG. 10 illustrates an example diagram supporting a modified 5GMM capabilities information element with extension information, according to an aspect of the present disclosure. [Figure 4B] FIG. 10 illustrates an example diagram supporting a modified 5GMM capabilities information element with extension information, according to an aspect of the present disclosure. [Figure 5] FIG. 10 illustrates an example diagram supporting a modified 5GMM capabilities information element using only extension information, according to an aspect of the present disclosure. [Figure 6] FIG. 10 illustrates an example diagram supporting extended information acknowledgment information, according to aspects of the present disclosure. [Figure 7A] FIG. 10 illustrates an example diagram supporting a SOR header with extension information, according to an aspect of the present disclosure. [Figure 7B] FIG. 10 illustrates an example diagram supporting a SOR header with extension information, according to an aspect of the present disclosure. [Figure 8] FIG. 1 illustrates an example block diagram of a device supporting communication between a UE and an SNPN, according to an aspect of the disclosure. [Figure 9] FIG. 1 illustrates a flowchart of a method for supporting communicating UE capability information to a network according to an aspect of the present disclosure. [Figure 10] FIG. 1 illustrates a flowchart of a method for supporting providing enhanced information to a UE according to an aspect of the present disclosure. DETAILED DESCRIPTION OF THE INVENTION

[0042] The SOR transparent container information element (defined in 3GPP TS 24.501) is used for communication between the UE and the UDM. For example, the UDM a channel (CH) control priority list of preferred SNPNs, in which the SNPNs are listed by their ID and in order of their priority, with the first listed SNPN having the highest priority among all listed SNPNs; and / or A CH control priority list of GINs, where GINs are listed by their ID and in order of their priority with the first listed GIN having the highest priority of all listed GINs, etc. To send the SOR, a SOR transparent container IE can be used.

[0043] If the UE supports the ability to receive a CH control priority list of preferred SNPNs and / or a list of CH control priority lists of GINs, the network shall send the SOR Transparent Container IE within a Payload Container information element, such as within a Registration Accept message, during the registration procedure from the UE to the 5GS network.

[0044] The IE may include SOR-SNPN-SI (as shown in Figure 9.11.3.51.2A of 3GPP TS 24.501), which optionally contains information about the CH control priority list of the preferred SNPN and the CH control priority list of the GIN.

[0045] Therefore, although the SOR-SNPN-SI contains some information, its current configuration may only include the ID of the SNPN / GIN and may not include other parameters / features associated with the SNPN / GIN, such as validity area and / or time of day characteristics. In some cases, the network may modify the SOR-SNPN-SI to include new lists, including the CH control priority list of preferred SNPNs, the CH control priority list of GINs, and new features such as validity area and / or time of day information.

[0046] Thus, such a configuration utilizing the extended SOP-SNPN-SI may enable the network to transmit information regarding additional features (e.g., validity areas and times for the preferred SNPN's CH control priority list and the GIN's CH control priority list).

[0047] The configuration includes indicators such as the Authentication Information Holder (CH) Control Priority List (CLSI) of preferred SNPN indicators and the CH Control Priority List (CLGI) of GIN indicators. Thus, the network has no indication of which UEs can utilize the enhanced information and therefore which UEs should be sent enhanced information such as the enhanced SOP-SNPN-SI during registration or other procedures.

[0048] The techniques described herein address these and other problems by providing information about the UE's capabilities to the network, which can then send extended information (e.g., extended SOR-SNPN-SI) to the UE, which can process and appropriately utilize such information. For example, the UE can provide its 5GMM capability information to the network during the registration procedure, and the network can respond by providing a list of SNPN / GINs that can contain the extended information (e.g., via various container IE configurations).

[0049] Thus, in various embodiments, the techniques described herein, among other advantages, enable a network to efficiently provide information, such as extended information about available SNPNs and / or GINs, to a UE attempting to connect to an SNPN / GIN for localized services or other communications.

[0050] Aspects of the present disclosure are described in the context of a wireless communication system. Aspects of the present disclosure are further illustrated and described with reference to device drawings and flowcharts.

[0051] FIG. 1 illustrates an example of a wireless communication system 100 supporting communication between a UE and an SNPN according to aspects of the present disclosure. The wireless communication system 100 may include one or more network entities 102, one or more UEs 104, a core network 106, and a packet data network 108. The wireless communication system 100 may support various radio access technologies. In some implementations, the wireless communication system 100 may be a 4G network such as an LTE network or an LTE-Advanced (LTE-A) network. In some other implementations, the wireless communication system 100 may be a 5G network such as an NR network. In other implementations, the wireless communication system 100 may be a combination of a 4G network and a 5G network, or other suitable radio access technologies including Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, etc. The wireless communication system 100 may support radio access technologies beyond 5G. Additionally, the wireless communication system 100 may support techniques such as time division multiple access (TDMA), frequency division multiple access (FDMA), or code division multiple access (CDMA).

[0052] One or more network entities 102 may be distributed throughout a geographic region to form a wireless communication system 100. One or more of the network entities 102 described herein may be, include, or be referred to as a network node, base station, network element, Radio Access Network (RAN), base transceiver station, access point, NodeB, eNodeB (eNB), next generation NodeB (gNB), or other suitable terminology. The network entities 102 and the UEs 104 may communicate via a communication link 110, which may be a wireless connection or a wired connection. For example, the network entities 102 and the UEs 104 may perform wireless communication (e.g., receive signaling and transmit signaling) over a Uu interface.

[0053] A network entity 102 may provide a geographic coverage area 112 for which the network entity 102 may support services (e.g., voice, video, packet data, messaging, broadcast, etc.) to one or more UEs 104 within the geographic coverage area 112. For example, the network entity 102 and the UEs 104 may support wireless communication of signals related to services (e.g., voice, video, packet data, messaging, broadcast, etc.) according to one or more radio access technologies. In some implementations, the network entity 102 may be mobile, e.g., a satellite associated with a non-terrestrial network. In some implementations, different geographic coverage areas 112 associated with the same or different radio access technologies may overlap, while different geographic coverage areas 112 may be associated with different network entities 102. The information and signals described herein may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout this specification may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

[0054] One or more UEs 104 may be dispersed throughout the geographic region of the wireless communication system 100. The UEs 104 may include or be referred to as mobile devices, wireless devices, remote devices, remote units, handheld devices, or subscriber devices, or some other suitable terminology. In some implementations, the UEs 104 may be referred to as units, stations, terminals, or clients, among other examples. Additionally or alternatively, the UEs 104 may be referred to as Internet-of-Things (IoT) devices, Internet-of-Everything (IoE) devices, or machine-type communication (MTC) devices, among other examples. In some implementations, the UEs 104 may be stationary within the wireless communication system 100. In some other implementations, the UEs 104 may be mobile within the wireless communication system 100.

[0055] One or more UEs 104 may be devices in different forms or with different capabilities. Some examples of UEs 104 are shown in FIG. 1. The UE 104 may be able to communicate with various types of devices, such as network entities 102, other UEs 104, or network equipment (e.g., the core network 106, the packet data network 108, a relay device, an integrated access and backhaul (IAB) node, or another network equipment), as shown in FIG. 1. Additionally or alternatively, the UE 104 may support communication with other network entities 102 or UEs 104 that may function as relays in the wireless communication system 100.

[0056] The UE 104 may also be able to support direct wireless communication with other UEs 104 via a communication link 114. For example, the UE 104 may support direct wireless communication with another UE 104 via a device-to-device (D2D) communication link. In some implementations, such as a vehicle-to-vehicle (V2V) deployment, a vehicle-to-everything (V2X) deployment, or a cellular-V2X deployment, the communication link 114 may be referred to as a sidelink. For example, the UE 104 may support direct wireless communication with another UE 104 via a PC5 interface.

[0057] A network entity 102 may support communication with the core network 106, or another network entity 102, or both. For example, a network entity 102 may interface with the core network 106 via one or more backhaul links 116 (e.g., via an S1, N2, N3, or another network interface). The network entities 102 may communicate with each other via the backhaul links 116 (e.g., via an X2, Xn, or another network interface). In some implementations, the network entities 102 may communicate directly with each other (e.g., between the network entities 102). In some other implementations, the network entities 102 may communicate with each other or indirectly (e.g., via the core network 106). In some implementations, one or more network entities 102 may include sub-components such as an access network entity, which may be an example of an access node controller (ANC). The ANC may communicate with one or more UEs 104 via one or more other access network transmission entities, which may be referred to as a radio head, a smart radio head, or a transmission-reception point (TRP).

[0058] In some implementations, the network entities 102 may be configured in a disaggregated architecture that may be configured to utilize a physically or logically distributed protocol stack between two or more network entities 102, such as an integrated access backhaul (IAB) network, an open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance), or a virtualized RAN (vRAN) (e.g., cloud RAN (C-RAN)). For example, the network entities 102 may include one or more of a central unit (CU), a distributed unit (DU), a radio unit (RU), a RAN Intelligent Controller (RIC) (e.g., a Near-Real Time RIC (Near-RT RIC), a Non-Real Time RIC (Non-RT RIC)), a Service Management and Orchestration (SMO) system, or any combination thereof.

[0059] An RU may also be referred to as a radio head, a smart radio head, a remote radio head (RRH), a remote radio unit (RRU), or a transmit / receive point (TRP). One or more components of the network entity 102 in a split RAN architecture may be co-located, or one or more components of the network entity 102 may be located in distributed locations (e.g., separate physical locations). In some implementations, one or more network entities 102 in a split RAN architecture may be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).

[0060] The division of functionality among the CU, DU, and RU may be flexible and may support different functions depending on which functions (e.g., network layer functions, protocol layer functions, baseband functions, radio frequency functions, and any combination thereof) are executed in the CU, DU, or RU. For example, a functional division of the protocol stack may be adopted between the CU and DU such that the CU may support one or more layers of the protocol stack and the DU may support one or more different layers of the protocol stack. In some implementations, the CU may host functions of upper protocol layers (e.g., Layer 3 (L3), Layer 2 (L2)) and signaling (e.g., radio resource control (RRC), service data adaptation protocol (SDAP), Packet Data Convergence Protocol (PDCP)). The CU may be connected to one or more DUs or RUs, which may host the functionality and signaling of lower protocol layers such as Layer 1 (L1) (e.g., physical (PHY) layer) or L2 (e.g., radio link control (RLC) layer, medium access control (MAC) layer), each of which may be at least partially controlled by CU160.

[0061] Additionally or alternatively, a functional division of the protocol stack may be employed between the DU and the RU, such that the DU may support one or more layers of the protocol stack and the RU may support one or more different layers of the protocol stack. The DU may support one or more different cells (e.g., via one or more RUs). In some implementations, the functional division between the CU and the DU or between the DU and the RU may be within a protocol layer (e.g., some functions of the protocol layer may be performed by one of the CU, DU, or RU, while other functions of the protocol layer are performed by a different one of the CU, DU, or RU).

[0062] The CU may be further functionally separated into a CU control plane (CU-CP) function and a CU user plane (CU-UP) function. The CU may be connected to one or more DUs via midhaul communication links (e.g., F1, F1-c, F1-u), and the DUs may be connected to one or more RUs via fronthaul communication links (e.g., open fronthaul (FH) interfaces). In some implementations, the midhaul or fronthaul communication links may be implemented according to interfaces (e.g., channels) between layers of protocol stacks supported by the respective network entities 102 communicating via such communication links.

[0063] The core network 106 may support user authentication, access authorization, tracking, connectivity, and other access, routing, or mobility functions. The core network 106 may be an evolved packet core (EPC) or 5G core (5GC), which may include control plane entities that manage access and mobility (e.g., a mobility management entity (MME), access and mobility management functions (AMF)) and user plane entities that route packets or interconnect to external networks (e.g., a serving gateway (S-GW), a packet data network (PDN) gateway (P-GW), or a user plane function (UPF)). In some implementations, the control plane entity may manage non-access stratum (NAS) functions such as mobility, authentication, and bearer management (e.g., data bearers, signaling bearers, etc.) for one or more UEs 104 served by one or more network entities 102 associated with the core network 106.

[0064] The core network 106 may communicate with the packet data network 108 via one or more backhaul links 116 (e.g., via S1, N2, N3, or another network interface). The packet data network 108 may include an application server 118. In some implementations, one or more UEs 104 may communicate with the application server 118. The UE 104 may establish a session (e.g., a protocol data unit (PDU) session, etc.) with the core network 106 via the network entity 102. The core network 106 may route traffic (e.g., control information, data, etc.) between the UE 104 and the application server 118 using the established session (e.g., an established PDU session). The PDU session may be an example of a logical connection between the UE 104 and the core network 106 (e.g., one or more network functions of the core network 106).

[0065] In the wireless communication system 100, the network entity 102 and the UE 104 may use resources of the wireless communication system 100 (e.g., time resources (e.g., symbols, slots, subframes, frames, etc.) or frequency resources (e.g., subcarriers, carriers)) to perform various operations (e.g., wireless communications). In some implementations, the network entity 102 and the UE 104 may support different resource structures. For example, the network entity 102 and the UE 104 may support different frame structures. In some implementations, such as 4G, the network entity 102 and the UE 104 may support a single frame structure. In some other implementations, such as 5G and other suitable radio access technologies, the network entity 102 and the UE 104 may support various frame structures (i.e., multiple frame structures). The network entity 102 and the UE 104 may support various frame structures based on one or more numerologies.

[0066] One or more numerologies may be supported in the wireless communication system 100, and a numerology may include a subcarrier spacing and a cyclic prefix. A first numerology (e.g., μ=0) may be associated with a first subcarrier spacing (e.g., 15 kHz) and a normal cyclic prefix. In some implementations, a first numerology (e.g., μ=0) associated with a first subcarrier spacing (e.g., 15 kHz) may utilize one slot per subframe. A second numerology (e.g., μ=1) may be associated with a second subcarrier spacing (e.g., 30 kHz) and a normal cyclic prefix. A third numerology (e.g., μ=2) may be associated with a third subcarrier spacing (e.g., 60 kHz) and a normal cyclic prefix or an extended cyclic prefix. A fourth numerology (e.g., μ=3) may be associated with a fourth subcarrier spacing (e.g., 120 kHz) and a normal cyclic prefix. A fifth numerology (e.g., μ=4) may be associated with a fifth subcarrier spacing (e.g., 240 kHz) and a normal cyclic prefix.

[0067] Time intervals of resources (e.g., communication resources) may be organized according to frames (also called radio frames). Each frame may have a duration, e.g., 10 milliseconds (ms). In some implementations, each frame may include multiple subframes. For example, each frame may include 10 subframes, and each subframe may have a duration, e.g., 1 ms. In some implementations, each frame may have the same duration. In some implementations, each subframe of a frame may have the same duration.

[0068] Additionally or alternatively, time intervals of resources (e.g., communication resources) may be organized according to slots. For example, a subframe may include several (e.g., a certain amount) of slots. The number of slots in each subframe may also depend on one or more numerologies supported in the wireless communication system 100. For example, the first, second, third, fourth, and fifth numerologies (i.e., μ=0, μ=1, μ=2, μ=3, μ=4) associated with subcarrier spacings of 15 kHz, 30 kHz, 60 kHz, 120 kHz, and 240 kHz, respectively, may utilize a single slot per subframe, two slots per subframe, four slots per subframe, eight slots per subframe, and 16 slots per subframe, respectively. Each slot may include a certain number (e.g., amount) of symbols (e.g., OFDM symbols). In some implementations, the number (e.g., amount) of slots in a subframe may depend on the numerology. For a normal cyclic prefix, a slot may include 14 symbols. For an extended cyclic prefix (e.g., applicable to 60 kHz subcarrier spacing), a slot may contain 12 symbols. The relationship between the number of symbols per slot, the number of slots per subframe, and the number of slots per frame for normal cyclic prefixes and extended cyclic prefixes may depend on the numerology. It should be understood that references to a first numerology (e.g., μ=0) associated with a first subcarrier spacing (e.g., 15 kHz) may be used interchangeably between subframe and slot.

[0069] In the wireless communication system 100, the electromagnetic (EM) spectrum may be divided into various classes, frequency bands, frequency channels, etc. based on frequency or wavelength. By way of example, the wireless communication system 100 may support one or more operating frequency bands, such as frequency range designations FR1 (410 MHz to 7.125 GHz), FR2 (24.25 GHz to 52.6 GHz), FR3 (7.125 GHz to 24.25 GHz), FR4 (52.6 GHz to 114.25 GHz), FR4a or FR4-1 (52.6 GHz to 71 GHz), and FR5 (114.25 GHz to 300 GHz). In some implementations, the network entity 102 and the UE 104 may perform wireless communications over one or more of the operating frequency bands. In some implementations, FR1 may be used by the network entity 102 and the UE 104, among other equipment or devices, for cellular communication traffic (e.g., control information, data). In some implementations, FR2 may be used by the network entity 102 and the UE 104, among other equipment or devices, for short-range, high-data-rate capabilities.

[0070] FR1 may be associated with one or more numerologies (e.g., at least three numerologies). For example, FR1 may be associated with a first numerology (e.g., μ=0) including a subcarrier spacing of 15 kHz, a second numerology (e.g., μ=1) including a subcarrier spacing of 30 kHz, and a third numerology (e.g., μ=2) including a subcarrier spacing of 60 kHz. FR2 may be associated with one or more numerologies (e.g., at least two numerologies). For example, FR2 may be associated with a third numerology (e.g., μ=2) including a subcarrier spacing of 60 kHz, and a fourth numerology (μ=3) including a subcarrier spacing of 120 kHz.

[0071] In some embodiments, the techniques described herein enable a network to efficiently provide information, such as extended information about available SNPNs and / or GINs, to a UE attempting to connect to an SNPN / GIN for localized services or other communications. If a UE (e.g., UE 104) includes new or updated capabilities, such as the ability to receive and process extended information (e.g., validity time and / or validity area for an SNPN / GIN), the UE can transmit the capabilities to the network in a non-access stratum (NAS) procedure (e.g., during a registration request procedure). In response, the network can transmit a list including a CH control priority list of preferred SNPNs and / or a CH control priority list of GINs. The list can include extended information, such as new information about validity areas and time of day for the SNPN / GIN.

[0072] 2 illustrates an example diagram 200 that supports providing enhanced information to a UE during a registration procedure, according to an aspect of the present disclosure. For example, the UE 104 performs a registration procedure with a 5G core network, which may include an Access and Mobility Management Function (AMF) 220, a Unified Data Management (UDM) Function 230, and a Steering of Roaming Application Function (SOR-AF) 240. The registration procedure may include the following steps:

[0073] Step 1: The UE 104 initiates the registration procedure by sending a registration request message to the AMF 220. The UE 104 includes 5GMM capability information with the capabilities of the UE in the registration request message.

[0074] For the UE 104 to indicate its support for the extended SOR-SNPN-SI, the UE 104 uses a new indication (e.g., a new bit) in the 5GMM Capability Information Element, which may be identified by the name E-SSNPNSI and may be bit 3 of octet 8 of the 5GMM Capability Information Element.

[0075] 3 illustrates an example diagram supporting a modified 5GMM capability information element 300 with extended information, according to an aspect of the present disclosure. As shown, octet 310 (e.g., octet 8) may include E-SSNPNSI information in a reserved bit 320 (e.g., bit 3) indicating the capabilities of the UE 104. For example, if bit 320, or "E-SSNPSI," is set to 0, the extended SOR-SNPN-SI is not supported by the UE 104, and if bit 320, or "E-SSNPSI," is set to 1, the extended SOR-SNPN-SI is supported by the UE 104.

[0076] In some cases, the extended SOR-SNPN-SI refers to a CH control priority list of preferred SNPNs with valid areas and times, and / or a CH control priority list of preferred GINs with valid areas and times.

[0077] Returning to Figure 2, step 2 is as follows. Similar to message 14a in Figure 4.2.2.2.2-1 of 3GPP® TS 23.502, the AMF 220 registers with the UDM 230 using Nudm_UECM_Registration for the access to be registered. The AMF 220 also subscribes to be notified when / if the UDM 230 deregisters. During Nudm_UECM_Registration, the AMF 220 sends an HTTP PUT request to the UDM 230 to update the AMF registration information for the 3GPP® access. The resource name of the HTTP PUT request is Amf3GppAccessRegistration and the resource URI is / {ueId} / registrations / amf-3gpp-access, see 3GPP® TS 29.503.

[0078] In some cases, the data type of Amf3GppAccessRegistration may include a new optional attribute (e.g., "ESorSnpnSiSupported" of data type Boolean) that conveys information about whether the UE 104 supports receiving UE or ME capability to support receiving information about the CH control priority list of preferred SNPNs with validity areas and times and / or the CH control priority list of preferred GINs with validity areas and times (extended SOR-SNPN-SI). For example, if the attribute "E-SorSnpnSiSupported" is set to true, the extended SOR-SNPN-SI is supported, and if the extended SOR-SNPN-SI is not supported, it is set to false or not present.

[0079] Step 3: After AMF220 successfully completes the Nudm_UECM_Registration operation, AMF220 obtains the access and mobility subscription data, SMF selection subscription data, UE context in SMF data, and LCS mobile origination by using Nudm_SDM_Get as an HTTP GET request with the resource name AccessAndMobilitySubscriptionData and the resource URI / {supi} / am-data (see 3GPP TS 29.503).

[0080] Step 4: The UDM 230 determines whether to send an extended SOR-SNPN-SI (e.g., E-SOR-SNPN-SI) by utilizing (1) user subscription information (e.g., whether the user subscription allows the UE 104 to use localized services, where the localized services are identified by time validity and / or location validity information in the list of available SNPN / GINs) and (2) UE capability information (e.g., received in step 1) to receive an information element (E-SOR-SNPN-SI) containing an extended SOR for a list of SNPN / GINs.

[0081] Thus, UDM230 can determine whether UE104 will receive the enhanced SOR-SNPN-SI based on a determination that UE104 is a subscriber to the localized service (or is associated with a user that subscribes to the localized service) and has provided information indicating that UE104 can utilize the enhanced SOR-SNPN-SI sent by AMF220 or UDM230.

[0082] In other words, the UDM (or together with the SOR-AF 240 in step 5) may create an SOR container after receiving the UE capabilities and subscription information for the localized service. The SOR container may include at least two new types of CH control priority lists of preferred network IDs. One type may be called a "CH control priority list of preferred SNPNs with valid criteria," and the other type may be called a "CH control priority list of GINs with valid criteria." The valid criteria may be at least one of a valid area or a valid time.

[0083] Step 5: If the subscribing SNPN / HPLMN has a policy for SOR-AF invocation, UDM 230 requests SOR-AF 240 to provide roaming steering information. UDM 230 may further indicate the UE capability to support E-SOR-SNPN-SI (e.g., received in step 3) and the UE's subscription to localized services. Based on the request and further instructions from UDM 230, SOR-AF 240 may create and provide E-SOR-SNPN-SI to UDM 230. Step 5 may use the procedures in 3GPP TS 29.571.

[0084] Step 6: The UDM 230 sends an HTTP 200 OK containing the UE's subscribed access and mobility data. The data type AccessAndMobilitySubscriptionData includes an attribute "sorInfo" of type SorInfo, which is used by the UDM 230 to send the extended SOR-SNPN-SI. The optional attribute "sorInfo" can be "sorTransparentContainer" and is encoded as a SOR Transparent Container information element (e.g., as specified in clause 9.11.3.51 of 3GPP TS 24.501). The SOR Transparent Container information element contains the extended SOR-SNPN-SI. As described herein, the data type SorInfo can also include an attribute "ackInd", which is used as an indication that the UDM 230 is requesting an acknowledgement from the UE 104 as part of the roaming steering information.

[0085] Step 7: The AMF 220 transparently sends the received enhanced roaming steering information to the UE 104 via a registration accept message (e.g., as shown in message 21 of Figure 4.2.2.2.2-1 of 3GPP TS 23.502). FIG. 4A shows an example diagram 400 supporting a 5GMM capability information element modified with enhanced information according to an aspect of the present disclosure. The E-SOR-SNPN-SI may include a CLGI indicator 410 and / or a CLSI indicator 415. Furthermore, the enhanced information may include a CH control priority list 420 of preferred SNPNs with validity areas and times, and a CH control priority list 425 of GINs with validity areas and times.

[0086] In some cases, the SOR-SNPN-SI indicator (e.g., SSSI), which is bit 3 in octet o in Figure 9.11.3.51.2A of 3GPP TS 24.501, can also be used to indicate the availability of E-SOR-SNPN-SI information.

[0087] FIG. 4B illustrates an example diagram 450 supporting a modified 5GMM capability information element with extension information, according to an embodiment of the present disclosure. The IE can include, for example, ESSSI 465 in the reserved bits of octet o 460. As another example, the IE can include either SOR-SNPN-SI or E-SOR-SNPN-SI, but not both. If the UDM 230 has a rule that does not include extension information, such as validity area and / or validity time, the value of the extension information should indicate that those values ​​are absent. Thus, octet v 470 can include E-SOR-SNPN-SI 475, but cannot include SOR-SNPN-SI.

[0088] In some cases, the SOR Transparent Container information element can include both the SOR-SNPN-SI and the E-SOR-SNPN-SI. Figure 5 illustrates an example diagram 500 supporting a modified 5GMM Capability information element using only extension information, according to an aspect of the present disclosure. The IE includes only information about the E-SOR-SNPN-SI.

[0089] For example, octet (s+1)*510 contains additional characteristic information of the CH control priority list 520 of the preferred SNPN with valid area and time information, and octet v*515 contains additional characteristic information of the CH control priority list 530 of the GIN with valid area and time information.

[0090] In some embodiments, the techniques may include a procedure for authorizing receipt or use of an enhanced SOR-SNPN-SI. During such a procedure, steps 3 through 10 may be performed either due to registration or a change in the E-SOR-SNPN-SI, which requires the UE 104 to be provided with new rules. In such a case, the UDM recognizes and stores information indicating that the UE 104 supports receiving the E-SOR-SNPN-SI, such as during initial registration. If steps 3 through 7 are performed due to a change in the E-SOR-SNPN-SI, the change may be invoked by the SOR-AF 240, such as if the HPLMN / SNPN has a policy for SOR-AF invocation in the UDM 230.

[0091] 6 illustrates an example diagram 600 supporting extended information acknowledgment information according to an aspect of the present disclosure. As illustrated, Case A refers to a registration procedure between the UE 104, the AFM 620, and the UDM 630 (similar to the procedure in FIG. 2), and Case B reflects a rule update (e.g., between the UDM 630 and the SOR-AF 640, also shown in FIG. 2).

[0092] For example, following case B, the SOR-AF 640 sends a Nudm_ParameterProvision_Update to the UDM 630 to trigger an update of the UE 104 with the E-SOR-SNPN-SI. The UDM 630 then notifies the affected AMF 620 of the change in information related to the UE 104 by sending a POST request with the callbackReference URI previously received in the SdmSubscription during the subscription and the subscription ID (see, e.g., 3GPP TS 29.503).

[0093] Starting at step 6: (similar to step 6 of FIG. 2) an instruction to request an acknowledgement from the UE 104 is included by the UDM 630 as part of the roaming steering information by using the attribute "ackInd".

[0094] Step 7: Depending on whether the procedure was initiated by initial registration or as an update on the E-SOR-SNPN-SI, the AMF 620 uses a Registration Accept message or a DL NAS Transfer message to convey information about the E-SOR-SNPN-SI to the UE 104.

[0095] 7A illustrates an example diagram 700 supporting an SOR header with extended information, according to an aspect of the present disclosure. As shown, the AMF 620 can set ACK 710 (e.g., in Figure 9.11.3.51.5 of 3GPP TS 24.501) to a value of “1” to indicate to the UE 104 that the network is requesting an acknowledgement from the UE 104.

[0096] Step 8: If the procedure was initiated by initial registration or as an update on E-SOR-SNPN-SI, the UE 104 includes a SOR Transparent Container information element in the Registration Complete message or UL NAS Transfer message. The SOR Transparent Container IE may include a SOR header for the SOR Transparent Container, which carries an acknowledgment of successful receipt of the enhanced roaming steering information (see FIG. 7A).

[0097] In some cases, if the SOR-SNPN-SI and the extended E-SOR-SNPN-SI cannot be sent simultaneously to the UE 104, the device / UE 104 may use the same indicator MSSNPNSI in the SOR header. The network then knows what information the acknowledgment indicates.

[0098] In some cases, the SOR header includes a new indicator indicating device / UE support for E-SOR-SNPN-SI. FIG. 7B illustrates an example diagram 750 supporting an SOR header with a new indicator according to an aspect of the present disclosure. As shown, the SOR header may include a new indicator 760 (such as a MSSNPNSI value in bit 4 of octet 4) to indicate acknowledgment by the UE 104. For example, MESSNPNSI may be set to '1' if E-SOR-SNPN-SI is supported by the device / UE, or may be set to '0' if E-SOR-SNPN-SI is not supported by the device / UE.

[0099] Step 9: The AMF 620 acknowledges the successful receipt of the enhanced roaming steering information by sending a PUT request with AcknowledgeInfo (see, for example, 3GPP TS 29.503) towards the UDM 630.

[0100] Step 10: If there is a subscribed SNPN or HPLMN policy for the SOR-AF640 call and UDM630 receives and verifies the UE acknowledgment in step 9, UDM630 notifies SOR-AF640 about the successful delivery of the E-SOR-SNPN-SI.

[0101] In some embodiments, the techniques described herein can apply similar messaging (as shown in FIG. 2 or FIG. 6) to a non-3GPP access network, where the UE 104 utilizes the non-3GPP access network to register with 5GS.

[0102] 8 illustrates an example block diagram 800 of a device 802 supporting communication between a UE and an SNPN according to aspects of the present disclosure. The device 802 may be an example of a network entity 102 or a UE 104 described herein. The device 802 may support wireless communication with one or more network entities 102, UEs 104, or any combination thereof. The device 802 may include components for bidirectional communication, including components for transmitting and receiving communications, such as a processor 804, a memory 806, a transceiver 808, and an I / O controller 810. These components may communicate electrically or otherwise be coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces (e.g., buses).

[0103] The processor 804, the memory 806, the transceiver 808, or various combinations thereof or various components thereof may be examples of means for performing various aspects of the disclosure as described herein. For example, the processor 804, the memory 806, the transceiver 808, or various combinations or components thereof may support a method for performing one or more of the operations described herein.

[0104] In some implementations, the processor 804, the memory 806, the transceiver 808, or various combinations or components thereof may be implemented in hardware (e.g., in communications management circuitry). The hardware may include a processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof configured as or otherwise supporting means for performing the functions described in this disclosure. In some implementations, the processor 804 and the memory 806 coupled to the processor 804 may be configured to perform one or more of the functions described herein (e.g., by the processor 804 executing instructions stored in the memory 806).

[0105] For example, processor 804 may support wireless communication in device 802 according to examples disclosed herein. Processor 804 may be configured with or otherwise support a means for determining whether to transmit an extended SOR-SNPN-SI for SNPNs and / or GINs that support the extended SOR-SNPN-SI to a UE, and, based on the determination, transmitting a list of SNPNs and / or GINs to the UE.

[0106] As another example, the processor 804 may support wireless communications in the device 802 in accordance with examples disclosed herein. The processor 804 may be configured with or otherwise support a means for sending an indication to a network function that the UE supports the extended SOR-SNPN-SI and receiving from the network function a list of SNPNs and / or GINs that support the extended SOR-SNPN-SI.

[0107] The processor 804 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some implementations, the processor 804 may be configured to operate a memory array using a memory controller. In some other implementations, the memory controller may be integrated into the processor 804. The processor 804 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 806) to cause the device 802 to perform various functions of the present disclosure.

[0108] The memory 806 may include random access memory (RAM) and read-only memory (ROM). The memory 806 may store computer-readable, computer-executable code including instructions that, when executed by the processor 804, cause the device 802 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium, such as system memory or another type of memory. In some implementations, the code may not be directly executable by the processor 804, but may (e.g., when compiled or executed) cause a computer to perform the functions described herein. In some implementations, the memory 806 may include a basic I / O system (BIOS), which may control basic hardware or software operations, such as interaction with peripheral components or devices, among other things.

[0109] The I / O controller 810 may manage input and output signals for the device 802. The I / O controller 810 may also manage peripherals not integrated into the device M02. In some implementations, the I / O controller 810 may represent a physical connection or port to an external peripheral. In some implementations, the I / O controller 810 may utilize an operating system such as iOS®, ANDROID®, MS-DOS®, MS-WINDOWS®, OS / 2®, UNIX®, LINUX®, or another known operating system. In some implementations, the I / O controller 810 may be implemented as part of a processor, such as the processor M06. In some implementations, a user may interact with the device 802 through the I / O controller 810 or through hardware components controlled by the I / O controller 810.

[0110] In some implementations, the device 802 may include a single antenna 812. However, in some other implementations, the device 802 may have two or more antennas 812 (i.e., multiple antennas), including multiple antenna panels or antenna arrays, which may be capable of simultaneously transmitting or receiving multiple wireless transmissions. The transceiver 808 may communicate bidirectionally via one or more antennas 812, a wired link, or a wireless link, as described herein. For example, the transceiver 808 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. The transceiver 808 may also include a modem for modulating packets to provide the modulated packets to the one or more antennas 812 for transmission and for demodulating packets received from the one or more antennas 812.

[0111] 9 illustrates a flowchart of a method 900 for supporting communicating UE capability information to a network according to an aspect of the present disclosure. The operations of method 900 may be implemented by a device or components thereof described herein. For example, the operations of method 900 may be performed by a UE 104, as described with reference to FIGS. 1 through 7B. In some embodiments, the device may execute a set of instructions that control functional elements of the device to perform the described functions. Additionally, or alternatively, the device may perform aspects of the described functions using dedicated hardware.

[0112] At 905, the method may include sending an indication to a network function that the UE supports the enhanced SOR-SNPN-SI. The operations of 905 may be performed according to examples described herein. In some embodiments, aspects of the operations of 905 may be performed by a device described with reference to FIG.

[0113] At 910, the method may include receiving, from a network function, a list of SNPNs and / or GINs that support the extended SOR-SNPN-SI. The operations of 910 may be performed according to examples described herein. In some embodiments, aspects of the operations of 910 may be performed by a device described with reference to FIG.

[0114] FIG. 10 shows a flowchart of a method 1000 for supporting providing enhanced information to a UE according to an aspect of the present disclosure. The operations of method 1000 may be implemented by a device or components thereof as described herein. For example, the operations of method 1000 may be performed by a network, a cell, or a network entity as described with reference to FIGS. 1 through 7B. In some implementations, a device may execute a set of instructions that control functional elements of the device to perform the described functions. Additionally or alternatively, the device may perform aspects of the described functions using dedicated hardware.

[0115] At 1005, the method may include determining whether to transmit an extended SOR-SNPN-SI for an SNPN and / or GIN that supports the extended SOR-SNPN-SI to the UE. The operation of 1005 may be performed according to examples described herein. In some implementations, aspects of the operation of 1005 may be performed by a device described with reference to FIG.

[0116] At 1010, the method may include transmitting a list of SNPNs and / or GINs to the UE based on the determination. The operations of 1010 may be performed according to examples described herein. In some implementations, aspects of the operations of 1010 may be performed by a device described with reference to FIG.

[0117] It should be noted that the methods described herein describe possible implementations, and that the operations and steps may be rearranged or otherwise modified, and that other implementations are possible. Additionally, aspects from two or more methods may be combined.

[0118] The various example blocks and components described in connection with the disclosure herein may be implemented or performed using a general-purpose processor, a DSP, an ASIC, a CPU, an FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general-purpose processor may be a microprocessor, but in the alternative, the processor may be any processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in combination with a DSP core, or any other such configuration).

[0119] The functions described herein may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions may be stored on or transmitted via a computer-readable medium as one or more instructions or code. Other examples and implementations are within the scope of this disclosure and the appended claims. For example, due to the nature of software, the functions described herein may be implemented using software executed by a processor, hardware, firmware, hardwiring, or any combination thereof. Features implementing the functions may also be physically located in various locations, including being distributed so that parts of the functions are implemented in different physical locations.

[0120] Computer-readable media include both non-transitory computer storage media and communication media, including any medium that facilitates transfer of a computer program from one place to another. Non-transitory storage media may be any available medium that can be accessed by a general-purpose or special-purpose computer. By way of example, and not limitation, non-transitory computer-readable media may include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compact disk (CD) ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other non-transitory medium that can be used to carry or store desired program code means in the form of instructions or data structures and that can be accessed by a general-purpose or special-purpose computer or processor.

[0121] Any connection may be properly termed a computer-readable medium. For example, if software is transmitted from a website, a server, or other remote source using coaxial cable, fiber optic cable, twisted pair wire, a digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, the coaxial cable, fiber optic cable, twisted pair wire, DSL, or wireless technologies such as infrared, radio, and microwave are included within the definition of computer-readable media. As used herein, disk and disc include CDs, laser discs, optical discs, digital versatile discs (DVDs), floppy disks, and Blu-ray® discs, where disks typically reproduce data magnetically and discs reproduce data optically using lasers. Combinations of the above are also included within the scope of computer-readable media.

[0122] As used herein, including within the claims, "or" when used in a list of items (e.g., a list of items preceded by phrases such as "at least one of," "one or more of," or "one or both of") indicates an inclusive list, such as, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Also, as used herein, the phrase "based on" should not be construed as a reference to a closed set of conditions. For example, an example step described as "based on condition A" could be based on both condition A and condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase "based on" should be construed similarly to the phrase "based at least in part on." Additionally, as used herein, including within the claims, a "set" may include one or more elements.

[0123] The terms "transmit," "receive," or "communicate," when referring to a network entity, may refer to any part of the network entity of the RAN (e.g., a base station, a CU, a DU, a RU) communicating with another device (e.g., directly or through one or more network entities).

[0124] The description set forth herein with reference to the accompanying drawings describes exemplary configurations and does not represent every example that may be implemented or every example that falls within the scope of the claims. As used herein, the term "example" means "serving as an example, instance, or illustration" and not "preferred or advantageous over other examples." The detailed description includes specific details for the purpose of providing an understanding of the described techniques. However, these techniques may be practiced without these specific details. In some instances, well-known structures and devices are shown in block diagram form in order to avoid obscuring the concepts of the described examples.

[0125] The description herein is provided to enable any person skilled in the art to make or use the present disclosure. Various modifications to the present disclosure will be apparent to those skilled in the art, and the general principles defined herein may be applied to other variations without departing from the scope of the present disclosure. Thus, the present disclosure is not limited to the examples and designs described herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein. [Explanation of symbols]

[0126] 100 Wireless Communication System 102 Network Entities 104UE 106 Core Network 108 Packet Data Network 110 Communication Links 112 Geographic Coverage Areas 114 Communication Links 116 backhaul links 118 Application Server 200 Figures 220 Access and Mobility Management Function (AMF), AMF 230 Integrated Data Management (UDM) function, UDM 240 Steering of Roaming Application Function (SOR-AF), SOR-AF 300 5GMM Capability Information Element 310 octets 320 spare bits, bits 400 Figures 410 CLGI indicator 415 CLSI indicators 420 CH control priority list of preferred SNPNs with valid area and time 425 CH control priority list of GIN with valid area and time 450 Figures 460 octets 465 ESSSI 470 octets v 475 E-SOR-SNPN-SI 500 Figures 510 octets (s+1)* 515 octets v* 520 CH control priority list of priority SNPNs with valid area and time information 530 CH control priority list of GIN with valid area and time information 600 Figures 620 AFM 630 UDM 640 SOR-AF 700 Figures 750 Figures 760 indicator 800 Block Diagram 802 devices 804 processor 806 memory 808 Transceiver 810 I / O Controller 812 Antenna

Claims

1. A user equipment (UE), At least one memory; coupled to the at least one memory, to the UE; sending an indication to a network function that the UE supports Steering Standalone Private Network Selection Information for Enhanced Roaming (SOR-SNPN-SI); receiving from a network function a list of group identifiers (GINs) for standalone non-public networks (SNPNs) and / or networks that support the extended SOR-SNPN-SI; at least one processor configured to cause UE equipped with.

2. The UE of claim 1 , wherein the UE sends the indication via a registration request message sent during an initiated registration procedure.

3. The UE of claim 1 , wherein the UE receives the list of SNPNs and / or GINs via a registration accept message.

4. The UE of claim 1 , wherein the indication is a bit within a 5GMM capability information element.

5. 10. The UE of claim 1, wherein the UE sends a second indication that the UE supports an extended SOR-SNPN-SI to confirm receipt of the list of SNPNs and / or GINs via a registration complete message.

6. The UE of claim 5 , wherein the second indication is a bit in a SOR transparent container information element.

7. The processor causes the UE to: receiving a request from the network function to confirm receipt of a list of the SNPNs and / or GINs that support an extended SOR-SNPN-SI; sending a confirmation of said list to said network function; The UE of claim 1 , further configured to:

8. 8. The UE of claim 7, wherein the UE confirms receipt of the list of SNPNs and / or GINs that support the extended SOR-SNPN-SI by transmitting its capability to receive the list of SNPNs and / or GINs that support the extended SOR-SNPN-SI.

9. The UE of claim 1 , wherein the indication includes an indication that the UE supports validity time information and / or validity area information for an SNPN and / or a GIN.

10. 1. A processor for wireless communications, comprising: coupled to at least one memory, and configured to: sending an indication to a network function that the processor supports Steering Standalone Private Network Selection Information for Enhanced Roaming (SOR-SNPN-SI); receiving from a network function a list of group identifiers (GINs) for standalone non-public networks (SNPNs) and / or networks that support the extended SOR-SNPN-SI; a processor comprising at least one controller configured to:

11. The processor of claim 10 , wherein the processor sends the indication via a registration request message sent during an initiated registration procedure.

12. 1. A method performed by a user equipment (UE), comprising: sending an indication to a network function that the UE supports Steering Standalone Private Network Selection Information for Enhanced Roaming (SOR-SNPN-SI); receiving from a network function a list of group identifiers (GINs) for standalone private networks (SNPNs) and / or networks that support enhanced SOR-SNPN-SI; A method comprising:

13. A network function, At least one memory; coupled to the at least one memory, and to the network function; determining whether to send an enhanced Steering Standalone Private Network Selection Information (SOR-SNPN-SI) for a standalone private network (SNPN) and / or a Group Identifier (GIN) for a network that supports enhanced roaming, to a user equipment (UE); transmitting a list of SNPNs and / or GINs to the UE based on the determination; at least one processor configured to cause Network functionality.

14. The processor may configure the network function to: user subscription information associated with the UE for localized services provided by the SNPN and / or GIN; and UE capability information for receiving a list of the SNPNs and / or GINs that support the extended SOR-SNPN-SI; 14. The network function of claim 13, configured to determine whether to transmit the extended SOR-SNPN-SI for the SNPN and / or GIN based on:

15. 14. The network function of claim 13, wherein localized services are identified by time validity information and / or location validity information in the extended SOR-SNPN-SI.

16. 14. The network function of claim 13, wherein UE capability information is received via a registration message sent by the UE to the network function during an initial registration procedure.

17. the network function sending the list of the SNPNs and / or GINs to the UE via a network entity; 14. The network function of claim 13, wherein the network entity is an Access and Mobility Management Function (AMF) and uses a SOR Transparent Container information element in a Registration Accept message or a Downlink (DL) Non-Access Stratum (NAS) Transport message.

18. The processor may configure the network function to: further configured to cause a request for acknowledgment of receipt of the list of SNPNs and / or GINs from the UE; the network function receiving information via a network entity; 14. The network function of claim 13, wherein the network entity is an Access and Mobility Management Function (AMF) and receives the UE's capability information for receiving the list of SNPNs and / or GINs via a SOR Transparent Container information element in a Registration Complete message or an Uplink (UL) Non-Access Stratum (NAS) Transport message.

19. 14. The network function of claim 13, wherein the network function is a Unified Data Management (UDM) function.

20. 14. The network function of claim 13, wherein the network function sends a request to a Steering of Roaming Application Function (SOR-AF) to create a SOR transparent container, the request including UE capability information and UE subscription information for localized services.

Images