Slice-based network selection

Abstract

Various aspects of the present disclosure generally relate to wireless communication and initiating a network search. Some aspects more specifically relate to initiating the network search in accordance with a registered network not supporting a slice that corresponds to a service to be provided to a user equipment (UE). Some other aspects relate to selecting a network selection mode associated with performing a network search based on or otherwise in accordance with an indicator that indicates a network selection mode. In some aspects, the indicator is whether slice-based network selection information is configured on the UE.

Description

SLICE-BASED NETWORK SELECTIONCROSS-REFERENCE TO RELATED APPLICATION

[0001] This Patent Application claims priority to Greece Patent Application No. 20230100663, filed on August 9, 2023, entitled “SLICE-BASED NETWORK SELECTION,” and assigned to the assignee hereof. The disclosure of the prior Application is considered part of and is incorporated by reference into this Patent Application.FIELD OF THE DISCLOSURE

[0002] Aspects of the present disclosure generally relate to wireless communication and specifically, to techniques and apparatuses for slice-based network selection.BACKGROUND

[0003] Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, and broadcasts. Typical wireless communication systems may employ multiple-access technologies capable of supporting communication with multiple users by sharing available system resources (for example, bandwidth or transmit power). Examples of such multiple-access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single-carrier frequency division multiple access (SC-FDMA) systems, time division synchronous code division multiple access (TD-SCDMA) systems, and Long Term Evolution (LTE). LTE / LTE-Advanced is a set of enhancements to the Universal Mobile Telecommunications System (UMTS) mobile standard promulgated by the Third Generation Partnership Project (3GPP).

[0004] The above multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different UEs to communicate on a municipal, national, regional, or global level. New Radio (NR), which may be referred to as 5G, is a set of enhancements to the LTE mobile standard promulgated by the 3GPP. NR is designed to better support mobile broadband internet access by improving spectral efficiency, lowering costs, improving services, making use of new spectmm, and better integrating with other open standards using orthogonal frequency division multiplexing (OFDM) with a cyclic prefix (CP) (CP -OFDM) on the downlink, using CP-OFDM or single-carrier frequency division multiplexing (SC-FDM) (also known as discrete Fourier transform spread OFDM (DFT-s-OFDM)) on the uplink, as well as supporting beamforming, multiple -input multiple-output (MIMO) antenna technology, and carrier aggregation. As the demand for mobilebroadband access continues to increase, further improvements in LTE, NR, and other radio access technologies remain useful.

[0005] A wireless communication system may support slice-based public land mobile network (PLMN) selection. A trigger for performing slice-based PLMN selection may be a determination that a visited PLMN (VPLMN) to which a user equipment (UE) is registered does not support a slice that corresponds to one or more services to be provided to the UE. An immediate and exhaustive search similar to that performed in response to a legacy loss-of-coverage trigger may not be suitable for slice-based PLMN selection in response to such a slice-based trigger (for example, due to increased power consumption by the UE). Similarly, a periodic PLMN search performed based on legacy search intervals also may not be suitable for slice-based PLMN selection.SUMMARY

[0006] Some aspects described herein relate to a user equipment (UE) for wireless communication. The UE may include a processing system that includes one or more processors and one or more processors memories with the one or more processors. The processing system may be configured to cause the UE to receive a connectivity request associated with an application. The processing system may be configured to cause the UE to obtain a slice identifier associated with a service provided by the application. The processing system may be configured to cause the UE to initiate a search for another network in accordance with a network to which the UE is registered not supporting a slice that is associated with the slice identifier.

[0007] Some aspects described herein relate to a UE for wireless communication. The UE may include a processing system that includes one or more processors and one or more memories coupled with the one or more processors. The processing system may be configured to cause the UE to select a network selection mode in accordance with an indicator associated with network selection mode selection. The processing system may be configured to cause the UE to perform a network selection procedure in accordance with the selected network selection mode in association with detecting a trigger to perform the network selection procedure.

[0008] Some aspects described herein relate to a method for wireless communication performed by a UE. The method may include receiving a connectivity request associated with an application. The method may include obtaining a slice identifier associated with a service provided by the application. The method may include initiating a search for another network in accordance with a network to which the UE is registered not supporting a slice that is associated with the slice identifier.

[0009] Some aspects described herein relate to a method of wireless communication performed by a UE. The method may include selecting a network selection mode in accordance with anindicator associated with network selection mode selection. The method may include performing a network selection procedure in accordance with the selected network selection mode in association with detecting a trigger to perform the network selection procedure.

[0010] Some aspects described herein relate to a non-transitory computer-readable medium that stores a set of instructions for wireless communication by a UE. The set of instructions, when executed by one or more processors of the UE, may cause the UE to receive a connectivity request associated with an application. The set of instructions, when executed by one or more processors of the UE, may cause the UE to obtain a slice identifier associated with a service provided by the application. The set of instructions, when executed by one or more processors of the UE, may cause the UE to initiate a search for another network in accordance with a network to which the UE is registered not supporting a slice that is associated with the slice identifier.

[0011] Some aspects described herein relate to a non-transitory computer-readable medium that stores a set of instructions for wireless communication by a UE. The set of instructions, when executed by one or more processors of the UE, may cause the UE to select a network selection mode in accordance with an indicator associated with network selection mode selection. The set of instructions, when executed by one or more processors of the UE, may cause the UE to perform a network selection procedure in accordance with the selected network selection mode in association with detecting a trigger to perform the network selection procedure.

[0012] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for receiving a connectivity request associated with an application. The apparatus may include means for obtaining a slice identifier associated with a service provided by the application. The apparatus may include means for initiating a search for another network in accordance with a network to which the apparatus is registered not supporting a slice that is associated with the slice identifier.

[0013] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for selecting a network selection mode in accordance with an indicator associated with network selection mode selection. The apparatus may include means for performing a network selection procedure in accordance with the selected network selection mode in association with detecting a trigger to perform the network selection procedure.

[0014] Aspects generally include a method, apparatus, system, computer program product, non-transitory computer-readable medium, user equipment, base station, network node, network entity, wireless communication device, or processing system as substantially described with reference to and as illustrated by the drawings and specification.

[0015] The foregoing has outlined rather broadly the features and technical advantages of examples in accordance with the disclosure in order that the detailed description that follows may be better understood. Additional features and advantages will be described hereinafter. Theconception and specific examples disclosed may be readily utilized as a basis for modifying or designing other structures for carrying out the same purposes of the present disclosure. Such equivalent constructions do not depart from the scope of the appended claims. Characteristics of the concepts disclosed herein, both their organization and method of operation, together with associated advantages will be better understood from the following description when considered in connection with the accompanying figures. Each of the figures is provided for the purposes of illustration and description, and not as a definition of the limits of the claims.BRIEF DESCRIPTION OF THE DRAWINGS

[0016] So that the above-recited features of the present disclosure can be understood in detail, a more particular description, briefly summarized above, may be had by reference to aspects, some of which are illustrated in the appended drawings. It is to be noted, however, that the appended drawings illustrate only some typical aspects of this disclosure and are therefore not to be considered limiting of its scope, for the description may admit to other equally effective aspects. The same reference numbers in different drawings may identify the same or similar elements.

[0017] Figure 1 is a diagram illustrating an example of a wireless network in accordance with the present disclosure.

[0018] Figure 2 is a diagram illustrating an example network node in communication with a user equipment (UE) in a wireless network in accordance with the present disclosure.

[0019] Figure 3 is a diagram illustrating an example disaggregated base station architecture in accordance with the present disclosure.

[0020] Figure 4 is a diagram illustrating an example associated with slice-based network selection in accordance with the present disclosure.

[0021] Figure 5 is a diagram illustrating an example associated with slice-based network selection in accordance with the present disclosure.

[0022] Figure 6 is a flowchart illustrating an example process performed, for example, at a UE or an apparatus of a UE that supports slice-based network selection in accordance with the present disclosure.

[0023] Figure 7 is a flowchart illustrating an example process performed, for example, at a UE or an apparatus of a UE that supports slice-based network selection in accordance with the present disclosure.

[0024] Figure 8 is a diagram of an example apparatus for wireless communication that supports slice-based network selection in accordance with the present disclosure.

[0025] Figure 9 is a diagram of an example apparatus for wireless communication that supports slice-based network selection in accordance with the present disclosure.DETAILED DESCRIPTION

[0026] Various aspects of the disclosure are described more fully hereinafter with reference to the accompanying drawings. This disclosure may, however, be embodied in many different forms and are not to be construed as limited to any specific structure or function presented throughout this disclosure. Rather, these aspects are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art. One skilled in the art may appreciate that the scope of the disclosure is intended to cover any aspect of the disclosure disclosed herein, whether implemented independently of or combined with any other aspect of the disclosure. For example, an apparatus may be implemented or a method may be practiced using any quantity of the aspects set forth herein. In addition, the scope of the disclosure is intended to cover such an apparatus or method which is practiced using other structure, functionality, or structure and functionality in addition to or other than the various aspects of the disclosure set forth herein. Any aspect of the disclosure disclosed herein may be embodied by one or more elements of a claim.

[0027] Several aspects of telecommunication systems will now be presented with reference to various apparatuses and techniques. These apparatuses and techniques will be described in the following detailed description and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, or algorithms (collectively referred to as “elements”). These elements may be implemented using hardware, software, or a combination of hardware and software. Whether such elements are implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system.

[0028] Various aspects relate generally to slice-based network selection and initiating a network search. Some aspects more specifically relate to initiating the network search based on or otherwise in accordance with a registered network not supporting a slice that corresponds to a service to be provided to a user equipment (UE). In some examples, a determination that the registered network does not support the slice that corresponds to the service may be based on or otherwise in accordance with a slice identifier associated with the service. Some other aspects relate to selecting a network selection mode associated with performing a network search based on or otherwise in accordance with an indicator that indicates a network selection mode. In some examples, the indicator is whether slice-based network selection information is configured on the UE.

[0029] Particular aspects of the subject matter described in this disclosure can be implemented to realize one or more of the following potential advantages. In some examples, the described techniques can be used to enable slice-based network selection and, further, a manner in which a network search is performed, in response to a trigger associated with slice-based networkselection. In some aspects, the described techniques enable slice-based network selection, and the associated network searching, in a manner that reduces power consumption of the UE (for example, as compared to performing a legacy network search in response to a slice-based network searching trigger), thereby increasing UE battery life. Further, the techniques described herein enable service-aware or slice-aware network searching. For example, the techniques described herein enable network searching that accounts for service or slice-based delay tolerances, which facilitates network searching in a manner that does not waste battery power, while ensuring service availability.

[0030] Figure 1 is a diagram illustrating an example of a wireless network in accordance with the present disclosure. The wireless network 100 may be or may include elements of a 5G (for example, NR) network or a 4G (for example, Long Term Evolution (LTE)) network, among other examples. The wireless network 100 may include one or more network nodes 110 (shown as a network node (NN) 110a, a network node 110b, a network node 110c, and a network node 1 lOd), a UE 120 or multiple UEs 120 (shown as a UE 120a, a UE 120b, a UE 120c, a UE 120d, and a UE 120e), or other network entities. A network node 110 is an entity that communicates with UEs 120. As shown, a network node 110 may include one or more network nodes. For example, a network node 110 may be an aggregated network node, meaning that the aggregated network node is configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node (for example, within a single device or unit). As another example, a network node 110 may be a disaggregated network node (sometimes referred to as a disaggregated base station), meaning that the network node 110 is configured to utilize a protocol stack that is physically or logically distributed among two or more nodes (such as one or more central units (CUs), one or more distributed units (DUs), or one or more radio units (RUs)).

[0031] In some examples, a network node 110 is or includes a network node that communicates with UEs 120 via a radio access link, such as an RU. In some examples, a network node 110 is or includes a network node that communicates with other network nodes 110 via a fronthaul link or a midhaul link, such as a DU. In some examples, a network node 110 is or includes a network node that communicates with other network nodes 110 via a midhaul link or a core network via a backhaul link, such as a CU. In some examples, a network node 110 (such as an aggregated network node 110 or a disaggregated network node 110) may include multiple network nodes, such as one or more RUs, one or more CUs, or one or more DUs. A network node 110 may include, for example, an NR network node, an LTE network node, a Node B, an eNB (for example, in 4G), a gNB (for example, in 5G), an access point, or a transmission reception point (TRP), a DU, an RU, a CU, a mobility element of a network, a core network node, a network element, a network equipment, or a RAN node. In some examples, the network nodes 110 may be interconnected to one another or to one or more other network nodes 110 in thewireless network 100 through various types of fronthaul, midhaul, orbackhaul interfaces, such as a direct physical connection, an air interface, or a virtual network, using any suitable transport network.

[0032] Each network node 110 may provide communication coverage for a particular geographic area. In the Third Generation Partnership Project (3GPP), the term “cell” can refer to a coverage area of a network node 110 or a network node subsystem serving this coverage area, depending on the context in which the term is used.

[0033] A network node 110 may provide communication coverage for a macro cell, a pico cell, a femto cell, or another type of cell. A macro cell may cover a relatively large geographic area (for example, several kilometers in radius) and may allow unrestricted access by UEs 120 with service subscriptions. A pico cell may cover a relatively small geographic area and may allow unrestricted access by UEs 120 with service subscription. A femto cell may cover a relatively small geographic area (for example, a home) and may allow restricted access by UEs 120 having association with the femto cell (for example, UEs 120 in a closed subscriber group (CSG)). A network node 110 for a macro cell may be referred to as a macro network node. A network node 110 for a pico cell may be referred to as a pico network node. A network node 110 for a femto cell may be referred to as a femto network node or an in-home network node.

[0034] The wireless network 100 may be a heterogeneous network that includes network nodes 110 of different types, such as macro network nodes, pico network nodes, femto network nodes, or relay network nodes. These different types of network nodes 110 may have different transmit power levels, different coverage areas, or different impacts on interference in the wireless network 100. For example, macro network nodes may have a high transmit power level (for example, 5 to 40 watts) whereas pico network nodes, femto network nodes, and relay network nodes may have lower transmit power levels (for example, 0.1 to 2 watts). In the example shown in Figure 1, the network node 110a may be a macro network node for a macro cell 102a, the network node 110b may be a pico network node for a pico cell 102b, and the network node 110c may be a femto network node for a femto cell 102c. A network node may support one or multiple (for example, three) cells. In some examples, a cell may not necessarily be stationary, and the geographic area of the cell may move according to the location of a network node 110 that is mobile (for example, a mobile network node).

[0035] In some aspects, the terms “base station” or “network node” may refer to an aggregated base station, a disaggregated base station, an integrated access and backhaul (IAB) node, a relay node, or one or more components thereof. For example, in some aspects, “base station” or “network node” may refer to a CU, a DU, an RU, a Near-Real Time (Near-RT) RAN Intelligent Controller (RIC), or a Non-Real Time (Non-RT) RIC. In some aspects, the terms “base station” or “network node” may refer to one device configured to perform one or more functions, such asthose described herein in connection with the network node 110. In some aspects, the terms “base station” or “network node” may refer to a plurality of devices configured to perform the one or more functions. For example, in some distributed systems, each of a quantity of different devices (which may be located in the same geographic location or in different geographic locations) may be configured to perform at least a portion of a function, or to duplicate performance of at least a portion of the function, and the terms “base station” or “network node” may refer to any one or more of those different devices. In some aspects, the terms “base station” or “network node” may refer to one or more virtual base stations or one or more virtual base station functions. For example, in some aspects, two or more base station functions may be instantiated on a single device. In some aspects, the terms “base station” or “network node” may refer to one of the base station functions and not another. In this way, a single device may include more than one base station.

[0036] A network controller 130 may couple to or communicate with a set of network nodes 110 and may provide coordination and control for these network nodes 110. The network controller 130 may communicate with the network nodes 110 via a backhaul communication link. The network nodes 110 may communicate with one another directly or indirectly via a wireless or wireline backhaul communication link. In some aspects, the network controller 130 may be a CU or a core network device, or the network controller 130 may include a CU or a core network device.

[0037] In some examples, a cell may not necessarily be stationary, and the geographic area of the cell may move in accordance with the location of a network node 110 that is mobile (for example, a mobile network node). In some examples, the network nodes 110 may be interconnected to one another or to one or more other network nodes 110 or network nodes (not shown) in the wireless network 100 through various types of backhaul interfaces, such as a direct physical connection or a virtual network, using any suitable transport network.

[0038] The wireless network 100 may include one or more relay stations. A relay station is an entity that can receive a transmission of data from an upstream station (for example, a network node 110 or a UE 120) and send a transmission of the data to a downstream station (for example, a UE 120 or a network node 110). A relay station may be a UE 120 that can relay transmissions for other UEs 120. In the example shown in Figure 1, the network node 1 lOd (for example, a relay network node) may communicate with the network node 110a (for example, a macro network node) and the UE 120d in order to facilitate communication between the network node 110a and the UE 120d. A network node 110 that relays communications may be referred to as a relay station, a relay network node, or a relay.

[0039] The UEs 120 may be dispersed throughout the wireless network 100, and each UE 120 may be stationary or mobile. A UE 120 may include, for example, an access terminal, a terminal,a mobile station, or a subscriber unit. A UE 120 may be a cellular phone (for example, a smart phone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device, a biometric device, a wearable device (for example, a smart watch, smart clothing, smart glasses, a smart wristband, smart jewelry (for example, a smart ring or a smart bracelet)), an entertainment device (for example, a music device, a video device, or a satellite radio), a vehicular component or sensor, a smart meter / sensor, industrial manufacturing equipment, a global positioning system device, a UE function of a network node, or any other suitable device that is configured to communicate via a wireless medium.

[0040] Some UEs 120 may be considered machine-type communication (MTC) or evolved or enhanced machine-type communication (eMTC) UEs. An MTC UE or an eMTC UE may include, for example, a robot, a drone, a remote device, a sensor, a meter, a monitor, or a location tag, that may communicate with a network node, another device (for example, a remote device), or some other entity. Some UEs 120 may be considered Intemet-of-Things (loT) devices, or may be implemented as NB-IoT (narrowband loT) devices. Some UEs 120 may be considered a Customer Premises Equipment. A UE 120 may be included inside a housing that houses components of the UE 120, such as processor components or memory components. In some examples, the processor components and the memory components may be coupled together. For example, the processor components (for example, one or more processors) and the memory components (for example, a memory) may be operatively coupled, communicatively coupled, electronically coupled, or electrically coupled.

[0041] In general, any quantity of wireless networks 100 may be deployed in a given geographic area. Each wireless network 100 may support a particular RAT and may operate on one or more frequencies. A RAT may be referred to as a radio technology or an air interface. A frequency may be referred to as a carrier or a frequency channel. Each frequency may support a single RAT in a given geographic area in order to avoid interference between wireless networks of different RATs. In some cases, NR or 5G RAT networks may be deployed.

[0042] In some examples, two or more UEs 120 (for example, shown as UE 120a and UE 120e) may communicate directly using one or more sidelink channels (for example, without using a network node 110 as an intermediary to communicate with one another). For example, the UEs 120 may communicate using peer-to-peer (P2P) communications, device-to-device (D2D) communications, a vehicle-to-everything (V2X) protocol (for example, which may include a vehicle-to-vehicle (V2 V) protocol, a vehicle-to-infrastructure (V2I) protocol, or a vehicle-to- pedestrian (V2P) protocol), or a mesh network. In such examples, a UE 120 may performscheduling operations, resource selection operations, or other operations described elsewhere herein as being performed by the network node 110.

[0043] Devices of the wireless network 100 may communicate using the electromagnetic spectrum, which may be subdivided by frequency or wavelength into various classes, bands, or channels. For example, devices of the wireless network 100 may communicate using one or more operating bands. In 5G NR, two initial operating bands have been identified as frequency range designations FR1 (410 MHz - 7.125 GHz) and FR2 (24.25 GHz - 52.6 GHz). Although a portion of FR1 is greater than 6 GHz, FR1 is often referred to (interchangeably) as a “Sub-6 GHz” band in various documents and articles. A similar nomenclature issue sometimes occurs in connection with FR2, which is often referred to (interchangeably) as a “millimeter wave” band in documents and articles, despite being different from the extremely high frequency (EHF) band (30 GHz - 300 GHz) which is identified by the International Telecommunications Union (ITU) as a “millimeter wave” band.

[0044] The frequencies between FR1 and FR2 are often referred to as mid-band frequencies. Recent 5G NR studies have identified an operating band for these mid-band frequencies as frequency range designation FR3 (7.125 GHz - 24.25 GHz). Frequency bands falling within FR3 may inherit FR1 characteristics or FR2 characteristics, and thus may effectively extend features of FR1 or FR2 into mid-band frequencies. In addition, higher frequency bands are currently being explored to extend 5G NR operation beyond 52.6 GHz. For example, three higher operating bands have been identified as frequency range designations FR4a or FR4-1 (52.6 GHz - 71 GHz), FR4 (52.6 GHz - 114.25 GHz), and FR5 (114.25 GHz - 300 GHz). Each of these higher frequency bands falls within the EHF band.

[0045] With the above examples in mind, unless specifically stated otherwise, the term “sub-6 GHz,” if used herein, may broadly represent frequencies that may be less than 6 GHz, may be within FR1, or may include mid-band frequencies. Further, unless specifically stated otherwise, the term “millimeter wave,” if used herein, may broadly represent frequencies that may include mid-band frequencies, may be within FR2, FR4, FR4-a or FR4-1, or FR5, or may be within the EHF band. It is contemplated that the frequencies included in these operating bands (for example, FR1, FR2, FR3, FR4, FR4-a, FR4-1, or FR5) may be modified, and techniques described herein are applicable to those modified frequency ranges.

[0046] In some aspects, the UE 120 may include a communication manager 140. As described in more detail elsewhere herein, the communication manager 140 may receive a connectivity request associated with an application; obtain a slice identifier associated with a service provided by the application; and initiate a search for another network in accordance with a network to which the UE is registered not supporting a slice that is associated with the slice identifier. Additionally or alternatively, as described in more detail elsewhere herein, the communicationmanager 140 may select a network selection mode in accordance with an indicator associated with network selection mode selection; and perform a network selection procedure in accordance with the selected network selection mode in association with detecting a trigger to perform the network selection procedure. Additionally or alternatively, the communication manager 140 may perform one or more other operations described herein.

[0047] Figure 2 is a diagram illustrating an example network node in communication with a UE in a wireless network in accordance with the present disclosure. The network node may correspond to the network node 110 of Figure 1. Similarly, the UE may correspond to the UE 120 of Figure 1. The network node 110 may be equipped with a set of antennas 234a through 234t, such as T antennas (T> 1). The UE 120 may be equipped with a set of antennas 252a through 252r, such as R antennas (R > 1). The network node 110 of depicted in Figure 2 includes one or more radio frequency components, such as antennas 234 and a modem 232. In some examples, a network node 110 may include an interface, a communication component, or another component that facilitates communication with the UE 120 or another network node. Some network nodes 110 may not include radio frequency components that facilitate direct communication with the UE 120, such as one or more CUs, or one or more DUs.

[0048] At the network node 110, a transmit processor 220 may receive data, from a data source 212, intended for the UE 120 (or a set of UEs 120). The transmit processor 220 may select one or more modulation and coding schemes (MCSs) for the UE 120 based at least in part on one or more channel quality indicators (CQIs) received from that UE 120. The network node 110 may process (for example, encode and modulate) the data for the UE 120 based at least in part on the MCS(s) selected for the UE 120 and may provide data symbols for the UE 120. The transmit processor 220 may process system information (for example, for semi-static resource partitioning information (SRPI)) and control information (for example, CQI requests, grants, or upper layer signaling) and provide overhead symbols and control symbols. The transmit processor 220 may generate reference symbols for reference signals (for example, a cell-specific reference signal (CRS) or a demodulation reference signal (DMRS)) and synchronization signals (for example, a primary synchronization signal (PSS) or a secondary synchronization signal (SSS)). A transmit (TX) multiple-input multiple -output (MIMO) processor 230 may perform spatial processing (for example, precoding) on the data symbols, the control symbols, the overhead symbols, or the reference symbols, if applicable, and may provide a set of output symbol streams (for example, T output symbol streams) to a corresponding set of modems 232 (for example, T modems), shown as modems 232a through 232t. For example, each output symbol stream may be provided to a modulator component (shown as MOD) of a modem 232. Each modem 232 may use a respective modulator component to process a respective output symbol stream (for example, for OFDM) to obtain an output sample stream. Each modem 232 may further use a respective modulatorcomponent to process (for example, convert to analog, amplify, filter, or upconvert) the output sample stream to obtain a downlink signal. The modems 232a through 232t may transmit a set of downlink signals (for example, T downlink signals) via a corresponding set of antennas 234 (for example, T antennas), shown as antennas 234a through 234t.

[0049] At the UE 120, a set of antennas 252 (shown as antennas 252a through 252r) may receive the downlink signals from the network node 110 or other network nodes 110 and may provide a set of received signals (for example, R received signals) to a set of modems 254 (for example, R modems), shown as modems 254a through 254r. For example, each received signal may be provided to a demodulator component (shown as DEMOD) of a modem 254. Each modem 254 may use a respective demodulator component to condition (for example, filter, amplify, downconvert, or digitize) a received signal to obtain input samples. Each modem 254 may use a demodulator component to further process the input samples (for example, for OFDM) to obtain received symbols. A MIMO detector 256 may obtain received symbols from the modems 254, may perform MIMO detection on the received symbols if applicable, and may provide detected symbols. A receive processor 258 may process (for example, demodulate and decode) the detected symbols, may provide decoded data for the UE 120 to a data sink 260, and may provide decoded control information and system information to a controller / processor 280. The term “controller / processor” may refer to one or more controllers or one or more processors. A channel processor may determine a reference signal received power (RSRP) parameter, a received signal strength indicator (RSSI) parameter, a reference signal received quality (RSRQ) parameter, or a CQI parameter, among other examples. In some examples, one or more components of the UE 120 may be included in a housing 284.

[0050] The network controller 130 may include a communication unit 294, a controller / processor 290, and a memory 292. The network controller 130 may include, for example, one or more devices in a core network. The network controller 130 may communicate with the network node 110 via the communication unit 294.

[0051] One or more antennas (for example, antennas 234a through 234t or antennas 252a through 252r) may include, or may be included within, one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, or one or more antenna arrays, among other examples. An antenna panel, an antenna group, a set of antenna elements, or an antenna array may include one or more antenna elements (within a single housing or multiple housings), a set of coplanar antenna elements, a set of non-coplanar antenna elements, or one or more antenna elements coupled to one or more transmission or reception components, such as one or more components of Figure 2.

[0052] On the uplink, at the UE 120, a transmit processor 264 may receive and process data from a data source 262 and control information (for example, for reports that include RSRP,RSSI, RSRQ, or CQI) from the controller / processor 280. The transmit processor 264 may generate reference symbols for one or more reference signals. The symbols from the transmit processor 264 may be precoded by a TX MIMO processor 266 if applicable, further processed by the modems 254 (for example, for DFT-s-OFDM or CP -OFDM), and transmitted to the network node 110. In some examples, the modem 254 of the UE 120 may include a modulator and a demodulator. In some examples, the UE 120 includes a transceiver. The transceiver may include any combination of the antenna(s) 252, the modem(s) 254, the MIMO detector 256, the receive processor 258, the transmit processor 264, or the TX MIMO processor 266. The transceiver may be used by a processor (for example, the controller / processor 280) and the memory 282 to perform aspects of any of the methods described herein.

[0053] At the network node 110, the uplink signals from UE 120 or other UEs may be received by the antennas 234, processed by the modem 232 (for example, a demodulator component, shown as DEMOD, of the modem 232), detected by a MIMO detector 236 if applicable, and further processed by a receive processor 238 to obtain decoded data and control information sent by the UE 120. The receive processor 238 may provide the decoded data to a data sink 239 and provide the decoded control information to the controller / processor 240. The network node 110 may include a communication unit 244 and may communicate with the network controller 130 via the communication unit 244. The network node 110 may include a scheduler 246 to schedule one or more UEs 120 for downlink or uplink communications. In some examples, the modem 232 of the network node 110 may include a modulator and a demodulator. In some examples, the network node 110 includes a transceiver. The transceiver may include any combination of the antenna(s) 234, the modem(s) 232, the MIMO detector 236, the receive processor 238, the transmit processor 220, or the TX MIMO processor 230. The transceiver may be used by a processor (for example, the controller / processor 240) and the memory 242 to perform aspects of any of the methods described herein.

[0054] The controller / processor 240 of the network node 110, the controller / processor 280 of the UE 120, or any other component(s) of Figure 2 may perform one or more techniques associated with slice-based network selection, as described in more detail elsewhere herein. For example, the controller / processor 240 of the network node 110, the controller / processor 280 of the UE 120, or any other component(s) of Figure 2 may perform or direct operations of, for example, process 600 of Figure 6, process 700 of Figure 7, or other processes as described herein. The memory 242 and the memory 282 may store data and program codes for the network node 110 and the UE 120, respectively. In some examples, the memory 242 or the memory 282 may include a non-transitory computer-readable medium storing one or more instructions (for example, code or program code) for wireless communication. For example, the one or more instructions, when executed (for example, directly, or after compiling, converting, or interpreting)by one or more processors of the network node 110 or the UE 120, may cause the one or more processors, the UE 120, or the network node 110 to perform or direct operations of, for example, process 600 of Figure 6, process 700 of Figure 7, or other processes as described herein. In some examples, executing instructions may include running the instructions, converting the instructions, compiling the instructions, or interpreting the instructions, among other examples.

[0055] In some aspects, the UE 120 includes means for receiving a connectivity request associated with an application; means for obtaining a slice identifier associated with a service provided by the application; or means for initiating a search for another network in accordance with a network to which the UE 120 is registered not supporting a slice that is associated with the slice identifier. Additionally or alternatively, the UE 120 includes means for selecting a network selection mode in accordance with an indicator associated with network selection mode selection; or means for performing a network selection procedure in accordance with the selected network selection mode in association with detecting a trigger to perform the network selection procedure. The means for the UE 120 to perform operations described herein may include, for example, one or more of communication manager 140, antenna 252, modem 254, MIMO detector 256, receive processor 258, transmit processor 264, TX MIMO processor 266, controller / processor 280, or memory 282.

[0056] Deployment of communication systems, such as 5G NR systems, may be arranged in multiple manners with various components or constituent parts. In a 5G NR system, or network, a network node, a network entity, a mobility element of a network, a RAN node, a core network node, a network element, a base station, or a network equipment may be implemented in an aggregated or disaggregated architecture. For example, a base station (such as a Node B (NB), an evolved NB (eNB), an NR base station, a 5G NB, an access point (AP), a TRP, or a cell, among other examples), or one or more units (or one or more components) performing base station functionality, may be implemented as an aggregated base station (also known as a standalone base station or a monolithic base station) or a disaggregated base station. “Network entity” or “network node” may refer to a disaggregated base station, or to one or more units of a disaggregated base station (such as one or more CUs, one or more DUs, or one or more RUs).

[0057] An aggregated base station (for example, an aggregated network node) may be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node (for example, within a single device or unit). A disaggregated base station (for example, a disaggregated network node) may be configured to utilize a protocol stack that is physically or logically distributed among two or more units (such as one or more CUs, one or more DUs, or one or more RUs). In some examples, a CU may be implemented within a network node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually distributed throughout one or multiple other network nodes. The DUsmay be implemented to communicate with one or more RUs. Each of the CU, DU, and RU also can be implemented as virtual units, such as a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU), among other examples.

[0058] Base station-type operation or network design may consider aggregation characteristics of base station functionality. For example, disaggregated base stations may be utilized in an IAB network, an open radio access network (O-RAN (such as the network configuration sponsored by the O-RAN Alliance)), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)) to facilitate scaling of communication systems by separating base station functionality into one or more units that can be individually deployed. A disaggregated base station may include functionality implemented across two or more units at various physical locations, as well as functionality implemented for at least one unit virtually, which can enable flexibility in network design. The various units of the disaggregated base station can be configured for wired or wireless communication with at least one other unit of the disaggregated base station.

[0059] Figure 3 is a diagram illustrating an example disaggregated base station architecture 300 in accordance with the present disclosure. The disaggregated base station architecture 300 may include a CU 310 that can communicate directly with a core network 320 via a backhaul link, or indirectly with the core network 320 through one or more disaggregated control units (such as a Near-RT RIC 325 via an E2 link, or a Non-RT RIC 315 associated with a Service Management and Orchestration (SMO) Framework 305, or both). A CU 310 may communicate with one or more DUs 330 via respective midhaul links, such as through Fl interfaces. Each of the DUs 330 may communicate with one or more RUs 340 via respective fronthaul links. Each of the RUs 340 may communicate with one or more UEs 120 via respective radio frequency (RF) access links. In some implementations, a UE 120 may be simultaneously served by multiple RUs 340.

[0060] Each of the units, including the CUs 310, the DUs 330, the RUs 340, as well as the Near-RT RICs 325, the Non-RT RICs 315, and the SMO Framework 305, may include one or more interfaces or be coupled with one or more interfaces configured to receive or transmit signals, data, or information (collectively, signals) via a wired or wireless transmission medium. Each of the units, or an associated processor or controller providing instructions to one or multiple communication interfaces of the respective unit, can be configured to communicate with one or more of the other units via the transmission medium. In some examples, each of the units can include a wired interface, configured to receive or transmit signals over a wired transmission medium to one or more of the other units, and a wireless interface, which may include a receiver, a transmitter or transceiver (such as a RF transceiver), configured to receive or transmit signals, or both, over a wireless transmission medium to one or more of the other units.

[0061] In some aspects, the CU 310 may host one or more higher layer control functions. Such control functions can include radio resource control (RRC) functions, packet data convergence protocol (PDCP) functions, or service data adaptation protocol (SDAP) functions, among other examples. Each control function can be implemented with an interface configured to communicate signals with other control functions hosted by the CU 310. The CU 310 may be configured to handle user plane functionality (for example, Central Unit - User Plane (CU-UP) functionality), or control plane functionality (for example, Central Unit - Control Plane (CU-CP) functionality). In some implementations, the CU 310 can be logically split into one or more CU- UP units and one or more CU-CP units. A CU-UP unit can communicate bidirectionally with a CU-CP unit via an interface, such as the El interface when implemented in an O-RAN configuration. The CU 310 can be implemented to communicate with a DU 330, as necessary, for network control and signaling.

[0062] Each DU 330 may correspond to a logical unit that includes one or more base station functions to control the operation of one or more RUs 340. In some aspects, the DU 330 may host one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more high physical (PHY) layers depending, at least in part, on a functional split, such as a functional split defined by the 3GPP. In some aspects, the one or more high PHY layers may be implemented by one or more modules for forward error correction (FEC) encoding and decoding, scrambling, and modulation and demodulation, among other examples. In some aspects, the DU 330 may further host one or more low PHY layers, such as implemented by one or more modules for a fast Fourier transform (FFT), an inverse FFT (iFFT), digital beamforming, or physical random access channel (PRACH) extraction and filtering, among other examples. Each layer (which also may be referred to as a module) can be implemented with an interface configured to communicate signals with other layers (and modules) hosted by the DU 330, or with the control functions hosted by the CU 310.

[0063] Each RU 340 may implement lower-layer functionality. In some deployments, an RU 340, controlled by a DU 330, may correspond to a logical node that hosts RF processing functions or low -PHY layer functions, such as performing an FFT, performing an iFFT, digital beamforming, or PRACH extraction and filtering, among other examples, based on a functional split (for example, a functional split defined by the 3 GPP), such as a lower layer functional split. In such an architecture, each RU 340 can be operated to handle over the air (OTA) communication with one or more UEs 120. In some implementations, real-time and non-real- time aspects of control and user plane communication with the RU(s) 340 can be controlled by the corresponding DU 330. In some scenarios, this configuration can enable each DU 330 and the CU 310 to be implemented in a cloud-based RAN architecture, such as a vRAN architecture.

[0064] The SMO Framework 305 may be configured to support RAN deployment and provisioning of non-virtualized and virtualized network elements. For non-virtualized network elements, the SMO Framework 305 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which may be managed via an operations and maintenance interface (such as an 01 interface). For virtualized network elements, the SMO Framework 305 may be configured to interact with a cloud computing platform (such as an open cloud (O-Cloud) platform 390) to perform network element life cycle management (such as to instantiate virtualized network elements) via a cloud computing platform interface (such as an 02 interface). Such virtualized network elements can include, but are not limited to, CUs 310, DUs 330, RUs 340, non-RT RICs 315, and Near-RT RICs 325. In some implementations, the SMO Framework 305 can communicate with a hardware aspect of a 4G RAN, such as an open eNB (O- eNB) 311, via an 01 interface. Additionally, in some implementations, the SMO Framework 305 can communicate directly with each of one or more RUs 340 via a respective 01 interface. The SMO Framework 305 also may include a Non-RT RIC 315 configured to support functionality of the SMO Framework 305.

[0065] The Non-RT RIC 315 may be configured to include a logical function that enables non- real-time control and optimization of RAN elements and resources, Artificial Intelligence / Machine Learning (AI / ML) workflows including model training and updates, or policy -based guidance of applications / features in the Near-RT RIC 325. The Non-RT RIC 315 may be coupled to or communicate with (such as via an Al interface) the Near-RT RIC 325. The Near-RT RIC 325 may be configured to include a logical function that enables near-real-time control and optimization of RAN elements and resources via data collection and actions over an interface (such as via an E2 interface) connecting one or more CUs 310, one or more DUs 330, or both, as well as an O-eNB, with the Near-RT RIC 325.

[0066] In some implementations, to generate AI / ML models to be deployed in the Near-RT RIC 325, the Non-RT RIC 315 may receive parameters or external enrichment information from external servers. Such information may be utilized by the Near-RT RIC 325 and may be received at the SMO Framework 305 or the Non-RT RIC 315 from non-network data sources or from network functions. In some examples, the Non-RT RIC 315 or the Near-RT RIC 325 may be configured to tune RAN behavior or performance. For example, the Non-RT RIC 315 may monitor long-term trends and patterns for performance and employ AI / ML models to perform corrective actions through the SMO Framework 305 (such as reconfiguration via an 01 interface) or via creation of RAN management policies (such as Al interface policies).

[0067] In a wireless communication system, a network selection procedure is a procedure that can be used by a UE in order to select a network, such as a public land mobile network (PLMN), for the UE to attempt to register with. A legacy PLMN selection procedure includes thefollowing steps: (1) detecting a trigger to perform PLMN selection, (2) searching for available PLMNs, and (3) selecting a PLMN to attempt to register with from available PLMNs identified as a result of the search. One legacy trigger for performing PLMN selection is a recovery from a loss of coverage (or power up after power down). In this scenario, the PLMN search is performed immediately and is exhaustive and, therefore, consumes a significant amount of UE power. Furthermore, this search may cause interruption of existing connections and degrade user experience. Another legacy trigger for performing PLMN selection is a periodic search trigger to search for a higher priority PLMN while the UE is registered to a visited PLMN (VPLMN). In this scenario, a PLMN search is performed on a periodic basis based on a set of parameters preprovisioned in the UE by a home PLMN (HPMLN). This search is performed as a background operation and typically is less intrusive to existing connections and user experience. The set of parameters can include, for example, an interval between network searches or a minimum interval between network searches. A PLMN search that is performed in response to either trigger provides a result in the form of a list of available PLMNs. The UE then selects a PLMN from the list of available PLMNs based on PLMN prioritization information. The PLMN prioritization information can be pre-provisioned by the HPLMN (in other words, PLMN selection can be performed automatically) or can be determined based on user input (in other words, PLMN selection can be performed manually).

[0068] Further, some wireless communication systems may support slice-based PLMN selection (in addition to legacy PLMN selection). A trigger for performing slice-based PLMN selection may be a determination that a VPLMN to which a UE is registered does not support a slice that corresponds to one or more services to be provided to the UE. In practice, service-slice mapping information that indicates a mapping between services and slices can be pre-provisioned in the UE by the HPLMN using, for example, a UE route selection policy (URSP). Further, the UE can receive information indicating slices supported by a registered VPLMN via non-access stratum (NAS) signaling (for example, during a registration procedure or a configuration update procedure). With respect to slice-based PLMN selection, the UE can utilize slice-based PLMN prioritization information that is pre-provisioned by the HPLMN. Such information can be referred to as slice-based PLMN selection information. Here, the slice-based PLMN selection information may take into account the slices supported by a given available PLMN.

[0069] A manner in which a PLMN search is performed in response to the trigger associated with slice-based PLMN selection as described above should be defined. Notably, an immediate and exhaustive search similar to that performed in response to the first legacy trigger described above (for example, a search performed in association with a recovery from loss of coverage) may not be suitable for slice-based PLMN selection in response to such a slice-based trigger. For example, services may be initiated on a UE relatively frequently, meaning that powerconsumption associated with PLMN searching would be increased, thereby reducing UE battery life. Further, some services may be delay tolerant and not require immediate connectivity, meaning that immediate searching may not be needed. On the other hand, some services may be deemed critical, and any unavailability of such a service could be equivalent to a loss of coverage. Furthermore, this search may cause interruption of one or more existing connections and degrade user experience.

[0070] Additionally, periodic PLMN searching based on legacy search intervals also may not be suitable for slice-based PLMN selection. For example, for a periodic PLMN search the legacy search interval can be configured to a value between 6 minutes and 8 hours, with a default value of 60 minutes. Such an interval may not be suitable for all services to be provided to the UE. Further, the legacy periodic search is for a higher priority PLMN, and is not service-aware or slice-aware.

[0071] Various aspects relate generally to slice-based network selection and initiating a network search. Some aspects more specifically relate to initiating the network search based on or otherwise in accordance with a registered network not supporting a slice that corresponds to a service to be provided to the UE. In some examples, a determination that the registered network does not support the slice that corresponds to the service may be based on or otherwise in accordance with a slice identifier associated with the service. Some other aspects relate to selecting a network selection mode associated with performing a network search based on or otherwise in accordance with an indicator that indicates a network selection mode. In some examples, the indicator is whether slice-based network selection information is configured on the UE.

[0072] Particular aspects of the subject matter described in this disclosure can be implemented to realize one or more of the following potential advantages. In some examples, the described techniques can be used to enable slice-based network selection and, further, a manner in which a network search is performed, in response to a trigger associated with slice-based network selection. In some aspects, the described techniques enable slice-based network selection, and the associated network searching, in a manner that reduces power consumption of the UE (for example, as compared to performing a legacy network search in response to a slice-based network searching trigger), thereby increasing UE battery life. Further, the techniques described herein enable service-aware or slice-aware network searching. For example, the techniques described herein enable network searching that accounts for service or slice-based delay tolerances, which facilitates network searching in a manner that does not waste battery power, while ensuring service availability. Additional details are provided below.

[0073] Figure 4 is a diagram illustrating an example 400 associated with slice-based network selection in accordance with the present disclosure. As shown in Figure 4, example 400 includescommunication between a UE 120, a network node 110 associated with a home network of the UE 120 (home network node 110), and a network node 110 associated with a visited network of the UE 120 (visited network node 110). In some aspects, the home network node 110, the visited network node 110, and UE 120 may be included in one or more wireless networks, such as one or more wireless networks 100. A given network node 110 and the UE 120 may communicate via a wireless access link, which may include an uplink and a downlink.

[0074] As shown in Figure 4, in a first operation 402, the UE 120 may receive service-slice mapping information. The service-slice mapping information includes information that indicates a mapping between one or more services and one or more slices. That is, the service-slice mapping information may identify one or more slices, and may indicate one or more respective services that are supported by each of the one or more slices. In some aspects, the UE 120 may receive the service-slice mapping information while the UE 120 is registered to a home network (for example, an HPLMN). For example, the UE 120 may be registered to a home network (for example, a home wireless network 100) and, while registered with the home network, may receive the service-slice mapping information from the home network node 110. In some aspects, the UE 120 may receive the service-slice mapping information based on or otherwise in accordance with a URSP.

[0075] In a second operation 404, the UE 120 may receive slice support information associated with a visited network (for example, a VPLMN). The slice support information includes information that indicates one or more slices supported by the visited network. In some aspects, each slice indicated in the slice support information may be associated with a slice identifier. In some aspects, the UE 120 may receive the slice support information while the UE 120 is registering with or is registered with the visited network (for example, a visited wireless network 100). For example, the UE 120 may receive the slice support information from the visited network node 110 during a registration procedure associated with registering with the visited network. As another example, the UE 120 may receive the slice support information from the visited network node 110 during a configuration update procedure performed after the UE 120 has registered with the visited network. In some aspects, the UE 120 may receive the slice support information via NAS signaling.

[0076] In a third operation 406, the UE 120 may receive a connectivity request associated with an application. For example, a user may cause an application to trigger or execute on the UE 120. Here, the application may be associated with one or more services, meaning that one or more services are to be provided by the application. The service may include, for example, a voice service, a video service, an Internet service, a satellite service, an Internet protocol multimedia subsystem (IMS), or a data service, among other examples. In another example, the UE 120 may cause the application to trigger or execute automatically (without user intervention).

[0077] In a fourth operation 408, the UE 120 may obtain a slice identifier associated with the service to be provided by the application. That is, the UE 120 may obtain a slice identifier that indicates a slice that supports the service to be provided by the application running on the UE 120. In some aspects, the UE 120 may obtain the slice identifier based on or otherwise in accordance with the service-slice information received by the UE 120 as described above with respect to operation 402. That is, the UE 120 may map the service to a slice based on or otherwise in accordance with the service-slice mapping information, and may obtain the slice identifier based on or otherwise in accordance with the mapping.

[0078] In a fifth operation 410, the UE 120 may determine that the network to which the UE 120 is registered does not support any slices that are associated with the slice identifier. For example, the UE 120 may determine, based on or otherwise in accordance with the slice support information, that the registered network of the UE 120 (for example, the visited network associated with the visited network node 110) does not support any slice that is associated with the slice identifier identified by the UE 120, meaning that the registered network does not support the service that is to be provided by the application. In one aspect, this determination may be based on a comparison of the list of slices requested by the UE 120 from the network (e.g., the home network node 110) and the list of slices that the network indicated as available and allowed to the UE 120. In one aspect, the list of slices requested by the UE 120 is included in a requested network slice selection assistance information (NSSAI) information element included in a signaling message sent by the UE 120 to the network. In one aspect, the signaling message is a registration request message. In one aspect, the list of slices indicated as available and allowed to the UE 120 is included in an allowed NSSAI information element included in a registration response message.

[0079] In a sixth operation 412, the UE 120 may initiate a search for another network. For example, in accordance with determining that the visited network does not support a slice that is associated with the slice identifier, the UE 120 may initiate a network search for another network. Here, the determination that the network to which the UE 120 is registered does not support any slices that are associated with the slice identifier serves as the trigger for the UE 120 to initiate slice-based network selection.

[0080] In some aspects, the UE 120 may initiate the search for the other network in accordance with a start time that is determined by the UE 120. That is, the UE 120 may determine a start time associated with initiating the search, and may initiate the search according to the determined start time.

[0081] In some aspects, the start time at which the search is initiated is in accordance with network searching being performed on a periodic basis. For example, the UE 120 may determinethat network searching is to be performed on a periodic basis (rather than immediately), and the start time may be determined accordingly.

[0082] In some aspects, in the case of periodic network searching, the UE 120 may initiate the search for the other network in accordance with a value of a periodic search interval parameter T. In some aspects, the value of the periodic search interval parameter T can indicate a time (for example, in minutes). Alternatively, the value of the periodic search interval parameter T may indicate that no periodic searching for slice-based network selection should be performed (for example, a value of 0 may indicate that no periodic searching is to be performed). In some aspects, the value of the periodic search interval parameter T may be stored in a universal subscriber identity module (USIM) of the UE 120. In some aspects, if a value for the periodic search interval parameter T is not stored, then the UE 120 may use a default value, such as 6 minutes or 60 minutes.

[0083] In some aspects, the periodic search interval parameter T is associated with slice-based network selection. That is, the periodic search interval parameter T may be a parameter configured specifically for use in association with slice-based network selection (in other works, the periodic search interval parameter T may be not configured for use in association with network selection initiated based on a legacy trigger).

[0084] In some aspects, the value of the periodic search interval parameter T is in accordance with information associated with the service to be provided by the application. That is, in some aspects, the value of the periodic search interval parameter T is determined based on or otherwise in accordance with the service to be provided by the application. For example, the UE 120 may be configured with a plurality of values of for the periodic search interval parameter T, with each value being associated with a respective service. Here, the UE 120 may determine the value of the periodic search interval parameter T as a value that maps to the service.

[0085] Additionally or alternatively, the value of the periodic search interval parameter T may in some aspects be in accordance with a service type of the service to be provided by the application. That is, in some aspects, the value of the periodic search interval parameter T is determined based on or otherwise in accordance with a service type of the service to be provided by the application. For example, the UE 120 may be configured with a plurality of values for the periodic search interval parameter T, each value being associated with a respective service type. Here, the UE 120 may determine a service type of the service, and may then determine the value of the periodic search interval parameter T as a value that maps to the determined service type.

[0086] In some aspects, the value of the periodic search interval parameter T is in accordance with a connection capability identifier corresponding to the service type of the service to be provided by the application. For example, the service type may, in some aspects, correspond to a connection capability identifier, and the connection capability identifier may be applied todetermine the value of the periodic search interval parameter T. As one example, the connection capability identifier may correspond to a multiplier coefficient and the value of the periodic search interval parameter T may be multiplied by the value of the multiplier coefficient M to determine a modified value of the periodic search interval parameter T that is to be used in association with determining the start time. In some aspects, the value of the multiplier coefficient Mean be based on or otherwise in accordance with the service type, which corresponds to the connection capability identifier as noted above. In one particular example, for example, the value of the multiplier coefficient M may be 1 (M = 1) for an IMS service and may be 2 (M= 2) for an Internet service. In some aspects, a mapping between connection capability identifiers and respective values of the multiplier coefficient M may be stored in the USIM of the UE 120.

[0087] In some aspects, the value of the periodic search interval parameter T may be greater than or equal to a minimum periodic search interval parameter value. That is, the value of the periodic search interval parameter T may in some aspects be set to a value that is not smaller than a minimum slice-based periodic search time value. In some aspects, the value of the periodic search interval parameter T being greater than the minimum periodic search interval parameter value may conserve battery power. In some aspects, the minimum periodic search interval parameter value is stored in the UE 120. For example, the UE 120 may be pre-configured with the minimum periodic search interval parameter value.

[0088] In operation, if the value of the periodic search interval parameter T indicates a indicates a time interval and the UE 120 detects the trigger to perform slice-based network selection (for example, the UE 120 determines that the network to which the UE 120 is registered does not support any slices that are associated with the slice identifier), then the UE 120 performs periodic network searching based on the value of the periodic search interval parameter T in association with performing slice-based network selection.

[0089] In some aspects, the start time at which the search is initiated is in accordance with network searching being performed on a non-periodic basis. For example, the UE 120 may determine that network searching is to be performed on a non-periodic basis (rather than periodically), and the start time may be determined accordingly.

[0090] In some aspects, the UE 120 may initiate the search for the other network in accordance with network searching being performed on a non-periodic basis. For example, the UE 120 may determine that network searching is to be performed on a non-periodic basis and may immediately initiate the network search (for example, the start time may be immediately after the determination that non-periodic searching is to be performed). Thus, in some aspects, if the UE 120 determines that non-periodic searching is to be performed, then the UE 120 may initiate the network search immediately. In some aspects, if the value of the periodic search intervalparameter T indicates that no periodic slice-based network selection should be performed (for example, if the value of the periodic search interval parameter T is 0) and the UE 120 detects the trigger (for example, the UE 120 determines that the network to which the UE 120 is registered does not support any slices that are associated with the slice identifier), then the UE 120 may perform a single network search in association with performing slice-based network selection.

[0091] Figure 5 is a diagram illustrating an example 500 associated with slice-based network selection in accordance with the present disclosure. As shown in Figure 5, example 500 includes communication between a UE 120 and a network node 110 associated with a home network of the UE 120 (home network node 110). In some aspects, the home network node 110 and UE 120 may be included in a wireless network, such as a wireless network 100. The home network node 110 and the UE 120 may communicate via a wireless access link, which may include an uplink and a downlink.

[0092] As shown Figure 5, in a first operation 502, the UE 120 may obtain an indicator associated with network selection mode selection. In some aspects, the indicator associated with network selection mode selection includes an indication of a network selection mode to be used by the UE 120 in association with performing network selection.

[0093] In some aspects, the indicator is slice-based network selection information associated with the UE 120. That is, in some aspects, the indicator is the presence of (for example, in memory) or receipt of slice-based network selection information. In some aspects, the slice-based network selection information includes prioritization information associated with a plurality of networks and information indicating one or more respective slices supported by each network in the plurality of networks. That is, in some aspects, the slice-based network selection information comprises a prioritized list of networks and respective slices supported by each network in the prioritized list of networks. Alternatively, the indicator is in some aspects is a lack of slice-based network selection information associated with the UE 120. That is, in some aspects, the indicator is the absence or lack of receipt of slice-based network selection information.

[0094] In a second operation 504, the UE 120 may select a network selection mode in accordance with the indicator associated with network selection mode selection. That is, the UE 120 may select a network selection mode based on or otherwise in accordance with the indicator.

[0095] In some aspects, the selected network selection mode is a slice-based network selection mode. For example, if the indicator is slice-based network selection information (in other words, if the UE 120 has received slice-based network selection information), then the UE 120 may select a slice-based network selection mode as the network selection mode to be used by the UE 120 in association with performing network selection.

[0096] Alternatively, the selected network selection mode is in some aspects a legacy network selection mode. For example, if the indicator is a lack of slice-based network selectioninformation (in other words, if the UE 120 does not store or has not received slice-based network selection information), then the UE 120 may select a legacy network selection mode as the network selection mode to be used by the UE 120 in association with performing network selection.

[0097] In a third operation 506, the UE 120 may detect a trigger to perform a network selection procedure. In some aspects, the trigger to perform the network selection procedure may be associated with the selected network selection mode. For example, if the selected network selection mode is the slice-based network selection mode, then the trigger may be a service activation on the UE 120 (for example, a triggering or execution of an application associated with a service). As another example, if the selected network selection mode is a legacy network selection mode, then the trigger may be a recovery after a loss of coverage or a periodic trigger while the UE 120 is registered to a visited network. Notably, if the selected network selection mode is the slice-based network selection mode, then a legacy trigger (for example, recovery after loss of coverage or periodic searching while on a visited network) may not act as a trigger performance of the network selection procedure. Similarly, if the selected network selection mode is the legacy network selection mode, then a slice-based trigger (for example, service activation on the UE 120) may not act as a trigger performance of the network selection procedure.

[0098] In a fourth operation 508, the UE 120 may perform a network selection procedure in accordance with the selected network selection mode in association with detecting the trigger to perform the network selection procedure. That is, based on detecting the trigger to perform the network selection procedure, the UE 120 may perform the network selection procedure in accordance with the selected network selection mode.

[0099] In some aspects, the network selection procedure is a slice-based network selection procedure. For example, the selected network selection mode may be a slice-based network selection mode, and so the UE 120 may perform a slice-based network selection procedure responsive to, based on, or otherwise associated with detecting the trigger. In some such aspects, the UE 120 may perform the slice-based network selection procedure based on or otherwise in accordance with the slice-based network selection information. That is, the UE 120 may use the slice-based network selection information in association with performing network selection according to the slice-based network selection procedure. As another example, the selected network selection mode may be a legacy network selection mode, and so the UE 120 may perform a legacy network selection procedure responsive to, based on, or otherwise associated with detecting the trigger. In such an aspect, the UE 120 does not use slice-based network selection information in association with performing the legacy network selection procedure.

[0100] Figure 6 is a flowchart illustrating an example process 600 performed, for example, at a UE or an apparatus of a UE that supports slice-based network selection in accordance with the present disclosure. Example process 600 is an example where the apparatus or the UE (for example, UE 120) performs operations associated with slice-based network selection.

[0101] As shown in Figure 6, in some aspects, process 600 may include receiving a connectivity request associated with an application (block 610). For example, the UE (such as by using communication manager 140 or network search component 808, depicted in Figure 8) may receive a connectivity request associated with an application, as described above.

[0102] As further shown in Figure 6, in some aspects, process 600 may include obtaining a slice identifier associated with a service provided by the application (block 620). For example, the UE (such as by using communication manager 140 or network search component 808, depicted in Figure 8) may obtain a slice identifier associated with a service provided by the application, as described above.

[0103] As further shown in Figure 6, in some aspects, process 600 may include initiating a search for another network in accordance with a network to which the UE is registered not supporting a slice that is associated with the slice identifier (block 630). For example, the UE (such as by using communication manager 140 or network search component 808, depicted in Figure 8) may initiate a search for another network in accordance with a network to which the UE is registered not supporting a slice that is associated with the slice identifier, as described above.

[0104] Process 600 may include additional aspects, such as any single aspect or any combination of aspects described below or in connection with one or more other processes described elsewhere herein.

[0105] In a first additional aspect, the search for the other network is initiated in accordance with a start time that is determined by the UE.

[0106] In a second additional aspect, alone or in combination with the first aspect, a start time at which the search for the other network is initiated in accordance with network searching being performed on a periodic basis.

[0107] In a third additional aspect, alone or in combination with one or more of the first and second aspects, the search for the other network is initiated in accordance with a value of a periodic search interval parameter.

[0108] In a fourth additional aspect, alone or in combination with one or more of the first through third aspects, the value of the periodic search interval parameter is stored in a universal subscriber identity module of the UE.

[0109] In a fifth additional aspect, alone or in combination with one or more of the first through fourth aspects, the periodic search interval parameter is associated with slice-based network selection.

[0110] In a sixth additional aspect, alone or in combination with one or more of the first through fifth aspects, the value of the periodic search interval parameter is in accordance with information associated with the service provided by the application.[oni] In a seventh additional aspect, alone or in combination with one or more of the first through sixth aspects, the value of the periodic search interval parameter is in accordance with a service type of the service provided by the application.

[0112] In an eighth additional aspect, alone or in combination with one or more of the first through seventh aspects, the value of the periodic search interval parameter is in accordance with a connection capability identifier corresponding to a service type of the service provided by the application.

[0113] In a ninth additional aspect, alone or in combination with one or more of the first through eighth aspects, the value of the periodic search interval parameter is greater than or equal to a minimum periodic search interval parameter value.

[0114] In a tenth additional aspect, alone or in combination with one or more of the first through ninth aspects, the minimum periodic search interval parameter value is stored in the UE.

[0115] In an eleventh additional aspect, alone or in combination with one or more of the first through tenth aspects, a start time at which the search for the other network is initiated is in accordance with network searching being performed on a non-periodic basis.

[0116] In a twelfth additional aspect, alone or in combination with one or more of the first through eleventh aspects, the search for the other network is initiated in accordance with network searching being performed on a non-periodic basis.

[0117] In a thirteenth additional aspect, alone or in combination with one or more of the first through twelfth aspects a determination that the network to which the UE is registered does not support a slice that is associated with the slice identifier is based on a list of supported slices received from the network to which the UE is registered.

[0118] In a fourteenth additional aspect, in combination with the thirteenth aspect, the list of supported slices is received in an allowed NSSAI information element.

[0119] Figure 7 is a flowchart illustrating an example process 700 performed, for example, at a UE or an apparatus of a UE that supports slice-based network selection in accordance with the present disclosure. Example process 700 is an example where the apparatus or the UE (for example, UE 120) performs operations associated with slice-based network selection.

[0120] As shown in Figure 7, in some aspects, process 700 may include selecting a network selection mode in accordance with an indicator associated with network selection mode selection (block 710). For example, the UE (such as by using communication manager 140 or selection component 908, depicted in Figure 9) may select a network selection mode in accordance with an indicator associated with network selection mode selection, as described above.

[0121] As further shown in Figure 7, in some aspects, process 700 may include performing a network selection procedure in accordance with the selected network selection mode in association with detecting a trigger to perform the network selection procedure (block 720). For example, the UE (such as by using communication manager 140 or selection component 908, depicted in Figure 9) may perform a network selection procedure in accordance with the selected network selection mode in association with detecting a trigger to perform the network selection procedure, as described above.

[0122] Process 700 may include additional aspects, such as any single aspect or any combination of aspects described below or in connection with one or more other processes described elsewhere herein.

[0123] In a first additional aspect, the indicator is slice-based network selection information associated with the UE.

[0124] In a second additional aspect, alone or in combination with the first aspect, the slicebased network selection information comprises prioritization information associated with a plurality of networks and information indicating one or more respective slices supported by each network in the plurality of networks.

[0125] In a third additional aspect, alone or in combination with one or more of the first and second aspects, the selected network selection mode is a slice-based network selection mode.

[0126] In a fourth additional aspect, alone or in combination with one or more of the first through third aspects, the network selection procedure is a slice-based network selection procedure.

[0127] In a fifth additional aspect, alone or in combination with one or more of the first through fourth aspects, the network selection procedure is associated with slice-based network selection information.

[0128] In a sixth additional aspect, alone or in combination with one or more of the first through fifth aspects, the indicator is a lack of slice-based network selection information associated with the UE.

[0129] In a seventh additional aspect, alone or in combination with one or more of the first through sixth aspects, the selected network selection mode is a legacy network selection mode.

[0130] In an eighth additional aspect, alone or in combination with one or more of the first through seventh aspects, the trigger to perform the network selection procedure is associated with the selected network selection mode.

[0131] In a ninth additional aspect, alone or in combination with one or more of the first through eighth aspects, the selected network selection mode is a slice-based network selection mode and detecting the trigger comprises detecting a service activation on the UE.

[0132] Figure 8 is a diagram of an example apparatus 800 for wireless communication that supports slice-based network selection in accordance with the present disclosure. The apparatus 800 may be a UE, or a UE may include the apparatus 800. In some aspects, the apparatus 800 includes a reception component 802, a transmission component 804, and a communication manager 140, which may be in communication with one another (for example, via one or more buses). As shown, the apparatus 800 may communicate with another apparatus 806 (such as a UE, a network node, or another wireless communication device) using the reception component 802 and the transmission component 804.

[0133] In some aspects, the apparatus 800 may be configured to or operable to perform one or more operations described herein in connection with Figure 4. Additionally or alternatively, the apparatus 800 may be configured to or operable to perform one or more processes described herein, such as process 600 of Figure 6. In some aspects, the apparatus 800 may include one or more components of the UE described above in connection with Figure 2.

[0134] The reception component 802 may receive communications, such as reference signals, control information, or data communications, from the apparatus 806. The reception component 802 may provide received communications to one or more other components of the apparatus 800, such as the communication manager 140. In some aspects, the reception component 802 may perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, de-mapping, equalization, interference cancellation, or decoding, among other examples), and may provide the processed signals to the one or more other components. In some aspects, the reception component 802 may include one or more antennas, one or more modems, one or more demodulators, one or more MIMO detectors, one or more receive processors, one or more controllers / processors, or one or more memories of the UE described above in connection with Figure 2.

[0135] The transmission component 804 may transmit communications, such as reference signals, control information, or data communications, to the apparatus 806. In some aspects, the communication manager 140 may generate communications and may transmit the generated communications to the transmission component 804 for transmission to the apparatus 806. In some aspects, the transmission component 804 may perform signal processing on the generated communications (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, among other examples), and may transmit the processed signals to the apparatus 806. In some aspects, the transmission component 804 may include one or more antennas, one or more modems, one or more modulators, one or more transmit MIMO processors, one or more transmit processors, one or more controllers / processors, or one or more memories of the UE described above in connection with Figure 2. In someaspects, the transmission component 804 may be co-located with the reception component 802 in one or more transceivers.

[0136] The communication manager 140 may receive or may cause the reception component 802 to receive a connectivity request associated with an application. The communication manager 140 may obtain a slice identifier associated with a service provided by the application. The communication manager 140 may initiate a search for another network in accordance with a network to which the UE is registered not supporting a slice that is associated with the slice identifier. In some aspects, the communication manager 140 may perform one or more operations described elsewhere herein as being performed by one or more components of the communication manager 140.

[0137] The communication manager 140 may include one or more controllers / processors and / or one or more memories of the UE described above in connection with Figure 2. In some aspects, the communication manager 140 includes a set of components, such as a network search component 808. Alternatively, the set of components may be separate and distinct from the communication manager 140. In some aspects, one or more components of the set of components may include or may be implemented within one or more controllers / processors, one or more memories of the UE described above in connection with Figure 2. Additionally or alternatively, one or more components of the set of components may be implemented at least in part as software stored in one or more memories. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by one or more controllers or one or more processors to perform the functions or operations of the component.

[0138] The network search component 808 may receive a connectivity request associated with an application. The network search component 808 may obtain a slice identifier associated with a service provided by the application. The network search component 808 may initiate a search for another network in accordance with a network to which the UE is registered not supporting a slice that is associated with the slice identifier.

[0139] The number and arrangement of components shown in Figure 8 are provided as an example. In practice, there may be additional components, fewer components, different components, or differently arranged components than those shown in Figure 8. Furthermore, two or more components shown in Figure 8 may be implemented within a single component, or a single component shown in Figure 8 may be implemented as multiple, distributed components. Additionally or alternatively, a set of (one or more) components shown in Figure 8 may perform one or more functions described as being performed by another set of components shown in Figure 8.

[0140] Figure 9 is a diagram of an example apparatus 900 for wireless communication that supports slice-based network selection in accordance with the present disclosure. The apparatus 900 may be a UE, or a UE may include the apparatus 900. In some aspects, the apparatus 900 includes a reception component 902, a transmission component 904, and a communication manager 140, which may be in communication with one another (for example, via one or more buses). As shown, the apparatus 900 may communicate with another apparatus 906 (such as a UE, a network node, or another wireless communication device) using the reception component 902 and the transmission component 904.

[0141] In some aspects, the apparatus 900 may be configured to or operable to perform one or more operations described herein in connection with Figure 5. Additionally or alternatively, the apparatus 900 may be configured to or operable to perform one or more processes described herein, such as process 700 of Figure 7. In some aspects, the apparatus 900 may include one or more components of the UE described above in connection with Figure 2.

[0142] The reception component 902 may receive communications, such as reference signals, control information, or data communications, from the apparatus 906. The reception component 902 may provide received communications to one or more other components of the apparatus 900, such as the communication manager 140. In some aspects, the reception component 902 may perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, de-mapping, equalization, interference cancellation, or decoding, among other examples), and may provide the processed signals to the one or more other components. In some aspects, the reception component 902 may include one or more antennas, one or more modems, one or more demodulators, one or more MIMO detectors, one or more receive processors, one or more controllers / processors, or one or more memories of the UE described above in connection with Figure 2.

[0143] The transmission component 904 may transmit communications, such as reference signals, control information, or data communications, to the apparatus 906. In some aspects, the communication manager 140 may generate communications and may transmit the generated communications to the transmission component 904 for transmission to the apparatus 906. In some aspects, the transmission component 904 may perform signal processing on the generated communications (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, among other examples), and may transmit the processed signals to the apparatus 906. In some aspects, the transmission component 904 may include one or more antennas, one or more modems, one or more modulators, one or more transmit MIMO processors, one or more transmit processors, one or more controllers / processors, or one or more memories of the UE described above in connection with Figure 2. In someaspects, the transmission component 904 may be co-located with the reception component 902 in one or more transceivers.

[0144] The communication manager 140 may select a network selection mode in accordance with an indicator associated with network selection mode selection. The communication manager 140 may perform a network selection procedure in accordance with the selected network selection mode in association with detecting a trigger to perform the network selection procedure. In some aspects, the communication manager 140 may perform one or more operations described elsewhere herein as being performed by one or more components of the communication manager 140.

[0145] The communication manager 140 may include one or more controllers / processors and / or one or more memories of the UE described above in connection with Figure 2. In some aspects, the communication manager 140 includes a set of components, such as a selection component 908. Alternatively, the set of components may be separate and distinct from the communication manager 140. In some aspects, one or more components of the set of components may include or may be implemented within one or more controllers / processors, one or more memories of the UE described above in connection with Figure 2. Additionally or alternatively, one or more components of the set of components may be implemented at least in part as software stored in one or more memories. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by one or more controllers or one or more processors to perform the functions or operations of the component.

[0146] The selection component 908 may select a network selection mode in accordance with an indicator associated with network selection mode selection. The selection component 908 may perform a network selection procedure in accordance with the selected network selection mode in association with detecting a trigger to perform the network selection procedure.

[0147] The number and arrangement of components shown in Figure 9 are provided as an example. In practice, there may be additional components, fewer components, different components, or differently arranged components than those shown in Figure 9. Furthermore, two or more components shown in Figure 9 may be implemented within a single component, or a single component shown in Figure 9 may be implemented as multiple, distributed components. Additionally or alternatively, a set of (one or more) components shown in Figure 9 may perform one or more functions described as being performed by another set of components shown in Figure 9.

[0148] The following provides an overview of some Aspects of the present disclosure:

[0149] Aspect 1 : A method for wireless communication performed by a user equipment (UE), comprising: receiving a connectivity request associated with an application; obtaining a sliceidentifier associated with a service provided by the application; and initiating a search for another network in accordance with a network to which the UE is registered not supporting a slice that is associated with the slice identifier.

[0150] Aspect 2: The method of Aspect 1, wherein the search for the other network is initiated in accordance with a start time that is determined by the UE.

[0151] Aspect 3: The method of any of Aspects 1-2, wherein a start time at which the search for the other network is initiated in accordance with network searching being performed on a periodic basis.

[0152] Aspect 4: The method of any of Aspects 1-3, wherein the search for the other network is initiated in accordance with a value of a periodic search interval parameter.

[0153] Aspect 5 : The method of Aspect 4, wherein the value of the periodic search interval parameter is stored in a universal subscriber identity module of the UE.

[0154] Aspect 6: The method of any of Aspects 4-5, wherein the periodic search interval parameter is associated with slice-based network selection.

[0155] Aspect 7: The method of any of Aspects 4-6, wherein the value of the periodic search interval parameter is in accordance with information associated with the service provided by the application.

[0156] Aspect 8: The method of any of Aspects 4-7, wherein the value of the periodic search interval parameter is in accordance with a service type of the service provided by the application.

[0157] Aspect 9: The method of any of Aspects 4-8, wherein the value of the periodic search interval parameter is in accordance with a connection capability identifier corresponding to a service type of the service provided by the application.

[0158] Aspect 10: The method of any of Aspects 4-9, wherein the value of the periodic search interval parameter is greater than or equal to a minimum periodic search interval parameter value.

[0159] Aspect 11: The method of Aspect 10, wherein the minimum periodic search interval parameter value is stored in the UE.

[0160] Aspect 12: The method of any of Aspects 1-11, wherein a start time at which the search for the other network is initiated is in accordance with network searching being performed on a non-periodic basis.

[0161] Aspect 13 : The method of any of Aspects 1-12, wherein the search for the other network is initiated in accordance with network searching being performed on a non-periodic basis.

[0162] Aspect 14: The method of any of Aspects 1-13, wherein a determination that the network to which the UE is registered does not support a slice that is associated with the slice identifier is based on a list of supported slices received from the network to which the UE is registered.

[0163] Aspect 15: The method of Aspect 14, wherein the list of supported slices is received in an allowed network slice selection assistance information (NS SAI) information element.

[0164] Aspect 16: A method of wireless communication performed by a user equipment (UE), comprising: selecting a network selection mode in accordance with an indicator associated with network selection mode selection; and performing a network selection procedure in accordance with the selected network selection mode in association with detecting a trigger to perform the network selection procedure.

[0165] Aspect 17: The method of Aspect 16, wherein the indicator is slice-based network selection information associated with the UE.

[0166] Aspect 18: The method of Aspect 17, wherein the slice-based network selection information comprises prioritization information associated with a plurality of networks and information indicating one or more respective slices supported by each network in the plurality of networks.

[0167] Aspect 19: The method of any of Aspects 16-18, wherein the selected network selection mode is a slice-based network selection mode.

[0168] Aspect 20: The method of any of Aspects 16-19, wherein the network selection procedure is a slice-based network selection procedure.

[0169] Aspect 21: The method of any of Aspects 16-20, wherein the network selection procedure is associated with slice-based network selection information.

[0170] Aspect 22: The method of any of Aspects 16-21, wherein the indicator is a lack of slicebased network selection information associated with the UE.

[0171] Aspect 23: The method of any of Aspects 16-22, wherein the selected network selection mode is a legacy network selection mode.

[0172] Aspect 24: The method of any of Aspects 16-23, wherein the trigger to perform the network selection procedure is associated with the selected network selection mode.

[0173] Aspect 25: The method of any of Aspects 16-24, wherein the selected network selection mode is a slice-based network selection mode and detecting the trigger comprises detecting a service activation on the UE.

[0174] Aspect 26: An apparatus for wireless communication at a device, the apparatus comprising one or more processors; one or more memories coupled with the one or more processors; and instructions stored in the one or more memories and executable by the one or more processors to cause the apparatus to perform the method of one or more of Aspects 1-25.

[0175] Aspect 27: An apparatus for wireless communication at a device, the apparatus comprising one or more memories and one or more processors coupled to the one or more memories, the one or more processors configured to cause the device to perform the method of one or more of Aspects 1-25.

[0176] Aspect 28: An apparatus for wireless communication, the apparatus comprising at least one means for performing the method of one or more of Aspects 1-25.

[0177] Aspect 29: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by one or more processors to perform the method of one or more of Aspects 1-25.

[0178] Aspect 30: A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform the method of one or more of Aspects 1-25.

[0179] Aspect 31 : A device for wireless communication, the device comprising a processing system that includes one or more processors and one or more memories coupled with the one or more processors, the processing system configured to cause the device to perform the method of one or more of Aspects 1-25.

[0180] Aspect 32: An apparatus for wireless communication at a device, the apparatus comprising one or more memories and one or more processors coupled to the one or more memories, the one or more processors individually or collectively configured to cause the device to perform the method of one or more of Aspects 1-25.

[0181] The foregoing disclosure provides illustration and description but is not intended to be exhaustive or to limit the aspects to the precise forms disclosed. Modifications and variations may be made in light of the above disclosure or may be acquired from practice of the aspects.

[0182] As used herein, the term “component” is intended to be broadly construed as hardware or a combination of hardware and software. “Software” shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, or functions, among other examples, whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise. As used herein, a “processor” is implemented in hardware or a combination of hardware and software. It will be apparent that systems or methods described herein may be implemented in different forms of hardware or a combination of hardware and software. The actual specialized control hardware or software code used to implement these systems or methods is not limiting of the aspects. Thus, the operation and behavior of the systems or methods are described herein without reference to specific software code, because those skilled in the art will understand that software and hardware can be designed to implement the systems or methods based, at least in part, on the description herein.

[0183] As used herein, “satisfying a threshold” may, depending on the context, refer to a value being greater than the threshold, greater than or equal to the threshold, less than the threshold, lessthan or equal to the threshold, equal to the threshold, or not equal to the threshold, among other examples.

[0184] Even though particular combinations of features are recited in the claims or disclosed in the specification, these combinations are not intended to limit the disclosure of various aspects. Many of these features may be combined in ways not specifically recited in the claims or disclosed in the specification. The disclosure of various aspects includes each dependent claim in combination with every other claim in the claim set. As used herein, a phrase referring to “at least one of’ a list of items refers to any combination of those items, including single members. As an example, “at least one of: a, b, or c” is intended to cover a, b, c, a + b, a + c, b + c, and a + b + c, as well as any combination with multiples of the same element (for example, a + a, a + a + a, a + a + b, a + a + c, a + b + b, a + c + c, b + b, b + b + b, b + b + c, c + c, and c + c + c, or any other ordering of a, b, and c).

[0185] No element, act, or instruction used herein should be construed as critical or essential unless explicitly described as such. Also, as used herein, the articles “a” and “an” are intended to include one or more items and may be used interchangeably with “one or more.” Further, as used herein, the article “the” is intended to include one or more items referenced in connection with the article “the” and may be used interchangeably with “the one or more.” Furthermore, as used herein, the terms “set” and “group” are intended to include one or more items and may be used interchangeably with “one or more.” Where only one item is intended, the phrase “only one” or similar language is used. Also, as used herein, the terms “has,” “have,” “having,” and similar terms are intended to be open-ended terms that do not limit an element that they modify (for example, an element “having” A may also have B). Further, the phrase “based on” is intended to mean “based, at least in part, on” unless explicitly stated otherwise. Also, as used herein, the term “or” is intended to be inclusive when used in a series and may be used interchangeably with “and / or,” unless explicitly stated otherwise (for example, if used in combination with “eithef ’ or “only one of’).

Claims

WHAT IS CLAIMED IS:

1. A user equipment (UE) for wireless communication, comprising: a processing system that includes one or more processors and one or more memories coupled with the one or more processors, the processing system configured to cause the UE to: receive a connectivity request associated with an application; obtain a slice identifier associated with a service provided by the application; and initiate a search for another network in accordance with a network to which the UE is registered not supporting a slice that is associated with the slice identifier.

2. The UE of claim 1, wherein the search for the other network is initiated in accordance with a start time that is determined by the UE.

3. The UE of claim 1, wherein a start time at which the search for the other network is initiated in accordance with network searching being performed on a periodic basis.

4. The UE of claim 1, wherein the search for the other network is initiated in accordance with a value of a periodic search interval parameter.

5. The UE of claim 4, wherein the value of the periodic search interval parameter is stored in a universal subscriber identity module of the UE.

6. The UE of claim 4, wherein the periodic search interval parameter is associated with slice-based network selection.

7. The UE of claim 4, wherein the value of the periodic search interval parameter is in accordance with information associated with the service provided by the application.

8. The UE of claim 4, wherein the value of the periodic search interval parameter is in accordance with a service type of the service provided by the application.

9. The UE of claim 4, wherein the value of the periodic search interval parameter is in accordance with a connection capability identifier corresponding to a service type of the service provided by the application.

10. The UE of claim 4, wherein the value of the periodic search interval parameter is greater than or equal to a minimum periodic search interval parameter value.

11. The UE of claim 10, wherein the minimum periodic search interval parameter value is stored in the UE.

12. The UE of claim 1, wherein a start time at which the search for the other network is initiated is in accordance with network searching being performed on a non-periodic basis.

13. The UE of claim 1, wherein the search for the other network is initiated in accordance with network searching being performed on a non-periodic basis.

14. The UE of claim 1 wherein a determination that the network to which the UE is registered does not support a slice that is associated with the slice identifier is based on a list of supported slices received from the network to which the UE is registered.

15. The UE of claim 14, wherein the list of supported slices is received in an allowed network slice selection assistance information (NS SAI) information element.

16. A user equipment (UE) for wireless communication, comprising: a processing system that includes one or more processors and one or more memories coupled with the one or more processors, the processing system configured to cause the UE to: select a network selection mode in accordance with an indicator associated with network selection mode selection; and perform a network selection procedure in accordance with the selected network selection mode in association with detecting a trigger to perform the network selection procedure.

17. The UE of claim 16, wherein the indicator is slice-based network selection information associated with the UE.

18. The UE of claim 17, wherein the slice-based network selection information comprises prioritization information associated with a plurality of networks and information indicating one or more respective slices supported by each network in the plurality of networks.

19. The UE of claim 16, wherein the selected network selection mode is a slice-based network selection mode.

20. The UE of claim 16, wherein the network selection procedure is a slice-based network selection procedure.

21. The UE of claim 16, wherein the network selection procedure is associated with slicebased network selection information.

22. The UE of claim 16, wherein the indicator is a lack of slice-based network selection information associated with the UE.

23. The UE of claim 16, wherein the selected network selection mode is a legacy network selection mode.

24. The UE of claim 16, wherein the trigger to perform the network selection procedure is associated with the selected network selection mode.

25. The UE of claim 16, wherein the selected network selection mode is a slice-based network selection mode and detecting the trigger comprises detecting a service activation on the UE.

26. A method for wireless communication performed by a user equipment (UE), comprising: receiving a connectivity request associated with an application; obtaining a slice identifier associated with a service provided by the application; and initiating a search for another network in accordance with a network to which the UE is registered not supporting a slice that is associated with the slice identifier.

27. The method of claim 26, wherein the search for the other network is initiated in accordance with a start time that is determined by the UE.

28. The method of claim 26, wherein a start time at which the search for the other network is initiated in accordance with network searching being performed on a periodic basis.

29. The method of claim 26, wherein the search for the other network is initiated in accordance with a value of a periodic search interval parameter.

30. A method of wireless communication performed by a user equipment (UE), comprising:selecting a network selection mode in accordance with an indicator associated with network selection mode selection; and performing a network selection procedure in accordance with the selected network selection mode in association with detecting a trigger to perform the network selection procedure.

Images