Slice-based network selection

Abstract

Various aspects of the present disclosure generally relate to wireless communication and initiation of a network search. Some aspects more specifically relate to initiating the network search according to a registered network that does not support slices corresponding to services 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 indicating the network selection mode. In some aspects, the indicator is based on whether the sliced network selection information is configured on the UE.

Description

[0001] Cross-reference to related applications

[0002] This patent application claims priority to Greek Patent Application No. 20230100663, filed on August 9, 2023, entitled “SLICE-BASED NETWORKSELECTION”, which is assigned to the assignee of this application. The disclosure of the earlier application is considered part of this patent application and is incorporated herein by reference. Technical Field

[0003] All aspects of this disclosure relate to wireless communication in general, and more particularly to techniques and apparatus for slice-based network selection. Background Technology

[0004] Wireless communication systems are widely deployed to provide a variety of telecommunications services, such as telephone, video, data, messaging, and broadcasting. Typical wireless communication systems employ multiple access technologies capable of supporting communication with multiple users by sharing available system resources (e.g., 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 collection of enhancements to the Universal Mobile Telecommunications System (UMTS) mobile standard issued by the 3rd Generation Partnership Project (3GPP).

[0005] The multiple access technologies mentioned above have been adopted in various telecommunications standards to provide a common protocol enabling different UEs to communicate at the city, country, region, or global level. New Radio (NR) (which may be referred to as 5G) is a set of enhancements to the LTE mobile standard issued by 3GPP. NR is designed to better support mobile broadband internet access by using Orthogonal Frequency Division Multiplexing (OFDM) with a Cyclic Prefix (CP) (CP-OFDM) on the downlink, and CP-OFDM or Single Carrier Frequency Division Multiplexing (SC-FDM) (also known as Discrete Fourier Transform Extended OFDM (DFT-s-OFDM)) on the uplink, as well as supporting beamforming, multiple-input multiple-output (MIMO) antenna technologies and carrier aggregation to improve spectral efficiency, reduce costs, improve service, utilize new spectrum, and better integrate with other open standards. Further improvements to LTE, NR, and other radio access technologies remain useful as the demand for mobile broadband access continues to increase.

[0006] Wireless communication systems can support slice-based Public Land Mobile Network (PLMN) selection. A trigger for performing slice-based PLMN selection can be determining that the visited PLMN (VPLMN) to which the User Equipment (UE) is registered does not support a slice corresponding to one or more services to be provided to the UE. Immediate and exhaustive searches, similar to those performed in response to legacy coverage loss triggers, may not be suitable for slice-based PLMN selection performed in response to such slice-based triggers (e.g., due to increased UE power consumption). Similarly, periodic PLMN searches performed based on legacy search intervals may also be unsuitable for slice-based PLMN selection. Summary of the Invention

[0007] Some aspects described herein relate to a user equipment (UE) for wireless communication. The UE may include a processing system comprising one or more processors and one or more processor memories coupled to the processors. The processing system may be configured to enable the UE to receive a connection request associated with an application. The processing system may be configured to enable the UE to obtain a slice identifier associated with a service provided by the application. The processing system may be configured to enable the UE to initiate a search for another network if the network to which the UE is registered does not support the slice associated with the slice identifier.

[0008] Some aspects described herein relate to a UE for wireless communication. The UE may include a processing system comprising one or more processors and one or more memories coupled to the processors. The processing system may be configured to cause the UE to select a network selection mode according to 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 association with the detection of a trigger for performing the network selection procedure, based on the selected network selection mode.

[0009] Some aspects described herein relate to a method for wireless communication performed by a UE. The method may include receiving a connection 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 based on the fact that the network to which the UE is registered does not support the slice associated with the slice identifier.

[0010] Some aspects described herein relate to a method for wireless communication performed by a UE. The method may include selecting a network selection mode based on an indicator associated with network selection mode selection. The method may also include performing a network selection process in association with detecting a trigger for performing the network selection process, based on the selected network selection mode.

[0011] Some aspects described herein relate to a non-transitory computer-readable medium storing a set of instructions for wireless communication by a UE. When executed by one or more processors of the UE, the set of instructions enables the UE to receive a connection request associated with an application. When executed by one or more processors of the UE, the set of instructions enables the UE to obtain a slice identifier associated with a service provided by the application. When executed by one or more processors of the UE, the set of instructions enables the UE to initiate a search for another network based on the fact that the network to which the UE is registered does not support the slice associated with the slice identifier.

[0012] Some aspects described herein relate to a non-transitory computer-readable medium storing a set of instructions for wireless communication by a UE. When executed by one or more processors of the UE, the set of instructions causes the UE to select a network selection mode according to an indicator associated with network selection mode selection. When executed by one or more processors of the UE, the set of instructions causes the UE to perform a network selection process in association with the detection of a trigger for performing the network selection process, based on the selected network selection mode.

[0013] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include components for receiving a connection request associated with an application. The apparatus may include components for obtaining a slice identifier associated with a service provided by the application. The apparatus may include components for initiating a search for another network based on the network to which the apparatus is registered, provided that the slice associated with the slice identifier is not supported.

[0014] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include components for selecting a network selection mode according to an indicator associated with network selection mode selection. The apparatus may also include components for performing a network selection process in association with detecting a trigger for performing the network selection process, based on the selected network selection mode.

[0015] The entirety of the terms includes, as fully described with reference to the accompanying drawings and description, and as illustrated in the accompanying drawings and description, methods, apparatus, systems, computer program products, non-transitory computer-readable media, user equipment, base stations, network nodes, network entities, wireless communication devices, or processing systems.

[0016] The foregoing has broadly outlined the features and technical advantages of the examples according to this disclosure in an effort to facilitate a better understanding of the following detailed description. Additional features and advantages will be described below. The disclosed concepts and specific examples can be readily utilized as a basis for modifying or designing other structures for achieving the same purpose as this disclosure. Such equivalent constructions do not depart from the scope of the appended claims. The characteristics (both in their organization and operation) of the concepts disclosed herein, as well as their associated advantages, will be better understood in conjunction with the accompanying drawings, based on the following description. Each figure in the accompanying drawings is provided for illustrative and descriptive purposes and not as a limitation of the definitions in the claims. Attached Figure Description

[0017] To gain a full understanding of the foregoing features of this disclosure, a more detailed description of the invention, briefly summarized above, can be obtained by referring to various aspects, some of which are illustrated in the accompanying drawings. However, it should be noted that the drawings illustrate only some typical aspects of this disclosure and should not be considered as limiting its scope, as other equivalent aspects are permissible in this description. The same reference numerals in different drawings may identify the same or similar elements.

[0018] Figure 1 This is a diagram illustrating an example of a wireless network according to the present disclosure.

[0019] Figure 2 This is a diagram illustrating communication between an example network node and a user equipment (UE) in a wireless network according to the present disclosure.

[0020] Figure 3 This is a diagram illustrating an example decomposed base station architecture according to this disclosure.

[0021] Figure 4 This is a diagram illustrating an example of slice-based network selection according to this disclosure.

[0022] Figure 5 This is a diagram illustrating an example of slice-based network selection according to this disclosure.

[0023] Figure 6 This is a flowchart illustrating an example process for supporting slice-based network selection, performed, for example, at a UE or a device of a UE, according to this disclosure.

[0024] Figure 7 This is a flowchart illustrating an example process for supporting slice-based network selection, performed, for example, at a UE or a device of a UE, according to this disclosure.

[0025] Figure 8 This is a diagram illustrating an example device for wireless communication that supports slice-based network selection according to the present disclosure.

[0026] Figure 9 This is a diagram illustrating an example device for wireless communication that supports slice-based network selection according to the present disclosure. Detailed Implementation

[0027] Various aspects of this disclosure are described more fully below with reference to the accompanying drawings. However, this disclosure may be embodied in many different forms and should not be construed as limited to any particular structure or function presented throughout this disclosure. Rather, these aspects are provided to make this disclosure thorough and complete, and to fully convey the scope of this disclosure to those skilled in the art. Those skilled in the art will appreciate that the scope of this disclosure is intended to cover any aspect of this disclosure disclosed herein, whether implemented independently of or in combination with any other aspect of this disclosure. For example, any amount of aspects set forth herein may be used to implement an apparatus or practice. Furthermore, the scope of this disclosure is intended to cover such apparatus or methods practiced using structures, functionalities, or structures and functionalities other than or different from the various aspects of the disclosure set forth herein. Any aspect of this disclosure disclosed herein may be embodied by one or more elements of the claims.

[0028] Several aspects of a telecommunications system will now be presented with reference to various devices and techniques. These devices and techniques will be described in detail below and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, or algorithms (collectively, “elements”). These elements may be implemented using hardware, software, or a combination of hardware and software. Whether these elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the system as a whole.

[0029] The various aspects generally involve slice-based network selection and initiating network searches. Some aspects more specifically involve initiating network searches based on or otherwise determining that the registered network does not support slices corresponding to the services to be provided to the user equipment (UE). In some examples, determining that the registered network does not support slices corresponding to the service can be based on or otherwise based on a slice identifier associated with the service. Some other aspects involve selecting a network selection mode associated with performing a network search based on or otherwise based on an indicator indicating a network selection mode. In some examples, the indicator is based on whether slice-based network selection information is configured on the UE.

[0030] Specific aspects of the subject matter described in this disclosure can be implemented to achieve one or more of the following potential advantages. In some examples, the described techniques can be used to implement slice-based network selection and further to enable network searches to be performed in response to triggers associated with slice-based network selection. In some aspects, the described techniques implement slice-based network selection and associated network searches in a way that reduces UE power consumption (e.g., compared to performing legacy network searches in response to slice-based network search triggers), thereby increasing UE battery life. Furthermore, the techniques described herein implement service-aware or slice-aware network searches. For example, the techniques described herein enable network searches that take into account service- or slice-based latency tolerances, which facilitates network searches in a way that does not waste battery power while ensuring service availability.

[0031] Figure 1 This is a diagram illustrating an example of a wireless network according to the present disclosure. Wireless network 100 may be a 5G (e.g., NR) network or a 4G (e.g., LTE) network, or may include elements of a 5G (e.g., NR) network or elements of a 4G (e.g., LTE) network, etc. Wireless network 100 may include one or more network nodes 110 (shown as network node (NN) 110a, network node 110b, network node 110c, and network node 110d), one UE 120 or more UEs 120 (shown as UE 120a, UE 120b, UE 120c, UE 120d, and UE 120e), and / or other network entities. Network node 110 is the entity that communicates with UE 120. As shown, network node 110 may include one or more network nodes. For example, network node 110 can 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 (e.g., within a single device or unit). As another example, network node 110 can be a decomposed network node (sometimes referred to as a decomposed base station), meaning that 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)).

[0032] In some examples, network node 110 is or includes network nodes (such as RUs) that communicate with UE 120 via a radio access link. In some examples, network node 110 is or includes network nodes (such as DUs) that communicate with other network nodes 110 via a fronthaul or midhaul link. In some examples, network node 110 is or includes network nodes (such as CUs) that communicate with other network nodes 110 via a midhaul link or with the core network via a backhaul link. In some examples, network node 110 (such as aggregated network node 110 or decomposed network node 110) may include multiple network nodes, such as one or more RUs, one or more CUs, or one or more DUs. For example, network node 110 may include NR network nodes, LTE network nodes, node Bs, eNBs (e.g., in 4G), gNBs (e.g., in 5G), access points, transmit / receive points (TRPs), DUs, RUs, CUs, network mobility elements, core network nodes, network elements, network equipment, or RAN nodes. In some examples, network nodes 110 can interconnect with each other or to one or more other network nodes 110 in wireless network 100 using any suitable transport network through various types of fronthaul, midhaul, or backhaul interfaces (such as direct physical connections, air interfaces, or virtual networks).

[0033] Each network node 110 can provide communication coverage for a specific geographic area. In the 3rd Generation Partnership Project (3GPP), depending on the context in which the term is used, the term "cell" can refer to the coverage area of ​​network node 110 or a network node subsystem serving that coverage area.

[0034] Network node 110 can provide communication coverage for macrocells, picocells, femtocells, or another type of cell. A macrocell can cover a relatively large geographic area (e.g., a radius of several kilometers) and allows unrestricted access by UE 120 with a service subscription. A picocell can cover a relatively small geographic area and allows unrestricted access by UE 120 with a service subscription. A femtocell can cover a relatively small geographic area (e.g., a residential area) and allows restricted access by UE 120 associated with that femtocell (e.g., UE 120 in a Closed Subscriber Group (CSG)). Network node 110 for macrocells may be referred to as a macro network node. Network node 110 for picocells may be referred to as a pico network node. Network node 110 for femtocells may be referred to as a femto network node or a home network node.

[0035] Wireless network 100 can be a heterogeneous network, comprising different types of network nodes 110, 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 effects on interference within wireless network 100. For example, macro network nodes may have high transmit power levels (e.g., 5 watts to 40 watts), while pico network nodes, femto network nodes, and relay network nodes may have lower transmit power levels (e.g., 0.1 watts to 2 watts). Figure 1 In the example shown, network node 110a can be a macro network node for macro cell 102a, network node 110b can be a pico network node for pico cell 102b, and network node 110c can be a femto network node for femto cell 102c. Network nodes can support one or more (e.g., three) cells. In some examples, the cells may not necessarily be stationary, and the geographical area of ​​the cells may move depending on the location of the mobile network node 110 (e.g., a mobile network node).

[0036] In some aspects, the term "base station" or "network node" may refer to an aggregated base station, a decomposed 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, DU, RU, a near real-time (near RT) RAN intelligent controller (RIC), or a non-real-time (non-RT) RIC. In some aspects, the term "base station" or "network node" may refer to a device configured to perform one or more functions (such as those described herein in conjunction with network node 110). In some aspects, the term "base station" or "network node" may refer to multiple devices configured to perform one or more functions. For example, in some distributed systems, each of multiple different devices (which may be located in the same geographical location or different geographical locations) may be configured to perform at least a portion of a function, or to repeatedly perform at least a portion of that function, and the term "base station" or "network node" may refer to any one or more of these different devices. In some aspects, the term "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 respects, the term "base station" or "network node" may refer to one base station function within a base station system, rather than another. In this way, a single device may include more than one base station.

[0037] Network controller 130 may be coupled to or communicate with network node set 110, and may provide coordination and control for these network nodes 110. Network controller 130 may communicate with network nodes 110 via a backhaul communication link. Network nodes 110 may also communicate directly with each other, or indirectly via a wireless or wired backhaul communication link. In some aspects, network controller 130 may be a CU or a core network device, or network controller 130 may include a CU or a core network device.

[0038] In some examples, the cell may not necessarily be stationary, and the geographical area of ​​the cell may move depending on the location of the mobile network node 110 (e.g., a mobile network node). In some examples, network nodes 110 may interconnect with each other or with one or more other network nodes 110 or network nodes (not shown) in the wireless network 100 using any suitable transport network via various types of backhaul interfaces (such as direct physical connections or virtual networks).

[0039] Wireless network 100 may include one or more relay stations. A relay station is an entity that can receive data transmissions from an upstream station (e.g., network node 110 or UE 120) and transmit data transmissions to a downstream station (e.g., UE 120 or network node 110). A relay station may be a UE 120 that can relay transmissions for other UE 120s. Figure 1 In the example shown, network node 110d (e.g., a relay network node) can communicate with network node 110a (e.g., a macro network node) and UE 120d to facilitate communication between network node 110a and UE 120d. The network node 110 that relays communication may be referred to as a relay station, relay network node, or relay.

[0040] UE 120 may be distributed throughout the wireless network 100, and each UE 120 may be stationary or mobile. UE 120 may include, for example, an access terminal, a terminal, a mobile station, or a subscriber unit. UE 120 may be a cellular phone (e.g., a smartphone), 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 device, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device, a biometric device, a wearable device (e.g., a smartwatch, smart clothing, smart glasses, a smart wristband, smart jewelry (e.g., a smart ring or smart bracelet)), an entertainment device (e.g., a music device, a video device, or a satellite radio), a vehicle component or sensor, a smart meter / sensor, industrial manufacturing equipment, a GPS device, a UE function of a network node, or any other suitable device configured to communicate via a wireless medium.

[0041] Some UEs 120 may be considered Machine-Type Communication (MTC) or Evolved or Enhanced Machine-Type Communication (eMTC) UEs. MTC or eMTC UEs may include, for example, robots, drones, remote devices, sensors, meters, monitors, or location tags that can communicate with network nodes, another device (e.g., a remote device), or some other entity. Some UEs 120 may be considered Internet of Things (IoT) devices or may be implemented as NB-IoT (Narrowband IoT) devices. Some UEs 120 may be considered customer premises equipment. UEs 120 may be included within a housing that houses the components of the UE 120, such as processor components or memory components. In some examples, the processor components and memory components may be coupled together. For example, the processor components (e.g., one or more processors) and memory components (e.g., memory) may be operatively coupled, communicatively coupled, electronically coupled, or electrically coupled.

[0042] Generally, any number of wireless networks 100 can be deployed in a given geographical area. Each wireless network 100 may support a specific RAT and may operate on one or more frequencies. A RAT may also be referred to as a radio technology or air interface. A frequency may also be referred to as a carrier or frequency channel. Each frequency in a given geographical area may support a single RAT to avoid interference between wireless networks using different RATs. In some cases, NR or 5G RAT networks may be deployed.

[0043] In some examples, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) may communicate directly using one or more sidelink channels (e.g., without using network node 110 as an intermediary for communication with each other). For example, UE 120 may communicate using peer-to-peer (P2P) communication, device-to-device (D2D) communication, vehicle-to-everything (V2X) protocols (e.g., which may include vehicle-to-vehicle (V2V) protocols, vehicle-to-infrastructure (V2I) protocols, or vehicle-to-pedestrian (V2P) protocols), or mesh networks. In such examples, UE 120 may perform scheduling operations, resource selection operations, or other operations described elsewhere herein as being performed by network node 110.

[0044] Devices in Wireless Network 100 can communicate using the electromagnetic spectrum, which can be subdivided into various categories, bands, or channels by frequency or wavelength. For example, devices in Wireless Network 100 can communicate using one or more operating bands. In 5G NR, two initial operating bands have been designated as frequency ranges FR1 (410MHz to 7.125GHz) and FR2 (24.25GHz to 52.6GHz). Although a portion of FR1 is greater than 6GHz, FR1 is generally (interchangeably) referred to as the “sub-6GHz” band in various documents and articles. Similar naming issues sometimes arise with FR2, although it is different from the Very High Frequency (EHF) band (30GHz to 300GHz) designated as the “millimeter wave” band by the International Telecommunication Union (ITU), FR2 is generally (interchangeably) referred to as the “millimeter wave” band in various documents and articles.

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

[0046] Considering the examples above, unless otherwise specifically stated, the term "below 6 GHz" as used herein can broadly refer to frequencies less than 6 GHz, within FR1, or including intermediate frequency band frequencies. Furthermore, unless otherwise specifically stated, the term "millimeter wave" as used herein can broadly refer to frequencies that can include intermediate frequency band frequencies, within FR2, FR4, FR4-a, FR4-1, or FR5, or within the EHF band. It is conceivable that the frequencies included in these operating bands (e.g., FR1, FR2, FR3, FR4, FR4-a, FR4-1, or FR5) can be modified, and the techniques described herein are applicable to those modified frequency ranges.

[0047] In some aspects, UE 120 may include a communication manager 140. As described in more detail elsewhere herein, the communication manager 140 may receive connection requests associated with an application; obtain a slice identifier associated with a service provided by the application; and initiate a search for another network if the network to which the UE is registered does not support the slice associated with the slice identifier. Additionally or alternatively, as described in more detail elsewhere herein, the communication manager 140 may select a network selection mode based on an indicator associated with network selection mode selection; and, based on the selected network selection mode, perform a network selection procedure in association with detecting a trigger for performing the network selection procedure. Additionally or alternatively, the communication manager 140 may perform one or more other operations described herein.

[0048] Figure 2 This is a diagram illustrating communication between an example network node and a UE in a wireless network according to this disclosure. The network node may correspond to... Figure 1 Network node 110. Similarly, the UE can correspond to Figure 1 UE 120. Network node 110 may be equipped with antenna sets 234a to 234t, such as T One antenna ( T ≥1). UE 120 may be equipped with antenna sets 252a to 252r, such as R One antenna ( R ≥1). Figure 2 The network node 110 depicted includes one or more radio frequency components, such as antenna 234 and modem 232. In some examples, network node 110 may include an interface, communication components, or another component facilitating communication with UE 120 or another network node. Some network nodes 110 may not include radio frequency components facilitating direct communication with UE 120, such as one or more CUs or one or more DUs.

[0049] At network node 110, transmitting processor 220 can receive data from data source 212 intended for use by UE 120 (or UE set 120). Transmitting processor 220 can select one or more modulation and decoding schemes (MCS) for UE 120 based at least in part on one or more channel quality indicators (CQIs) received from UE 120. Network node 110 can process (e.g., encode and modulate) the data for UE 120 based at least in part on the MCS selected for UE 120 and can provide data symbols for UE 120. Transmitting processor 220 can process system information (e.g., semi-static resource partitioning information (SRPI)) and control information (e.g., CQI requests, grants, or upper-layer signaling) and provide overhead symbols and control symbols. Transmitting processor 220 can generate reference symbols for reference signals (e.g., cell-specific reference signals (CRS) or demodulation reference signals (DMRS)) and synchronization signals (e.g., primary synchronization signal (PSS) or secondary synchronization signal (SSS)). The transmit (TX) multiple-input multiple-output (MIMO) processor 230 can perform spatial processing (e.g., pre-decoding) on ​​data symbols, control symbols, overhead symbols, or reference symbols (if applicable), and can direct to a corresponding set of modems 232 shown as modems 232a to 232t (e.g., T A set of output symbol streams (e.g., modems) is provided by a modem. T Each output symbol stream can be provided to a modulator component (shown as MOD) of modem 232. Each modem 232 can use a corresponding modulator component to process the corresponding output symbol stream (e.g., for OFDM) to obtain an output sample stream. Each modem 232 can also use a corresponding modulator component to process (e.g., convert to analog, amplify, filter, or upconvert) the output sample stream to obtain a downlink signal. Modems 232a to 232t can be connected via a corresponding set of antennas 234 (e.g., T Each antenna (shown as antennas 234a to 234t) is used to transmit a set of downlink signals (e.g., T (One downlink signal).

[0050] At UE 120, the set of antennas 252 (shown as antennas 252a to 252r) can receive downlink signals from network node 110 or other network nodes 110, and can transmit signals to the set of modems 254 (e.g., R Each modem (shown as modems 254a to 254r) provides a set of received signals (e.g., REach received signal may be provided to a demodulator component (shown as DEMOD) of modem 254. Each modem 254 may use a corresponding demodulator component to condition (e.g., filter, amplify, down-convert, or digitize) the received signal to obtain an input sample. Each modem 254 may use a demodulator component to further process the input sample (e.g., for OFDM) to obtain a received symbol. MIMO detector 256 may obtain the received symbols from modem 254, perform MIMO detection on the received symbols where applicable, and provide the detected symbols. Receiver processor 258 may process (e.g., demodulate and decode) the detected symbols, provide the decoded data for UE 120 to data sink 260, and provide the decoded control information and system information to controller / processor 280. The term "controller / processor" may refer to one or more controllers or one or more processors. The channel processor may determine Reference Signal Received Power (RSRP) parameters, Received Signal Strength Indicator (RSSI) parameters, Reference Signal Received Quality (RSRQ) parameters, or CQI parameters, etc. In some examples, one or more components of UE 120 may be included in housing 284.

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

[0052] One or more antennas (e.g., antennas 234a to 234t or antennas 252a to 252r) may include or be included in the following: one or more antenna panels, one or more antenna groups, one or more collections of antenna elements, or one or more antenna arrays, etc. Antenna panels, antenna groups, collections of antenna elements, or antenna arrays may include one or more antenna elements (within a single housing or multiple housings), a collection of coplanar antenna elements, a collection of non-coplanar antenna elements, or coupled to one or more transmitting or receiving components (such as...). Figure 2 One or more antenna elements (one or more components).

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

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

[0055] The controller / processor 240 of network node 110, the controller / processor 280 of UE 120, or Figure 2Any other component 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 network node 110, the controller / processor 280 of UE 120, or... Figure 2 Any other component that can execute or direct, for example Figure 6 Process 600 Figure 7 The operation of process 700 or other processes as described herein. Memory 242 and memory 282 may store data and program code for network node 110 and UE 120, respectively. In some examples, memory 242 or memory 282 may include a non-transitory computer-readable medium storing one or more instructions (e.g., code or program code) for wireless communication. For example, the one or more instructions may cause the one or more processors, UE 120, or network node 110 to perform or direct, for example, when executed by one or more processors of network node 110 or UE 120 (e.g., directly, or after compilation, transformation, or interpretation). Figure 6 Process 600 Figure 7 The operation of process 700 or other processes as described herein. In some examples, the execution instructions may include run instructions, transform instructions, compile instructions, or interpret instructions, etc.

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

[0057] Communication systems (such as 5G NR systems) can be deployed in various ways with a variety of components or parts. In a 5G NR system or network, network nodes, network entities, network mobility elements, RAN nodes, core network nodes, network elements, base stations, or network equipment can be implemented in either a converged or decomposed architecture. For example, a base station (such as a Node B (NB), evolved NB (eNB), NR base station, 5G NB, access point (AP), TRP, or cell, etc.) or one or more units (or components) performing base station functions can be implemented as a converged base station (also known as a standalone base station or monolithic base station) or a decomposed base station. A "network entity" or "network node" can refer to a decomposed base station or one or more units of a decomposed base station (such as one or more CUs, one or more DUs, or one or more RUs).

[0058] Aggregated base stations (e.g., aggregated network nodes) can be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node (e.g., within a single device or cell). Decomposed base stations (e.g., decomposed network nodes) can be configured to utilize a protocol stack that is physically or logically distributed across two or more cells (such as one or more CUs, one or more DUs, or one or more RUs). In some examples, the 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 across one or more other network nodes. DUs may be implemented to communicate with one or more RUs. Each of the CU, DU, and RU can also be implemented as a virtual cell, such as a Virtual Central Unit (VCU), a Virtual Distributed Unit (VDU), or a Virtual Radio Unit (VRU), etc.

[0059] Base station type operation or network design can take into account the aggregation characteristics of base station functionality. For example, decomposed base stations can be utilized in IAB networks, Open Radio Access Networks (O-RAN (such as network configurations initiated by the O-RAN Alliance)), or Virtualized Radio Access Networks (vRAN, also known as Cloud Radio Access Networks (C-RAN)) to facilitate the scaling of communication systems by separating base station functionality into one or more units that can be deployed independently. Decomposed base stations can include functionality implemented across two or more units at various physical locations, as well as functionality virtually implemented for at least one unit, which enables flexibility in network design. Each unit of a decomposed base station can be configured for wired or wireless communication with at least one other unit of the decomposed base station.

[0060] Figure 3This is an illustration of an example disaggregated base station architecture 300 according to this disclosure. The disaggregated base station architecture 300 may include a CU 310, which may communicate directly with the core network 320 via a backhaul link, or indirectly with the core network 320 via one or more disaggregated control units (such as 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). The CU 310 may communicate with one or more DUs 330 via a corresponding midhaul link (such as via an F1 interface). Each DU 330 may communicate with one or more RUs 340 via a corresponding fronthaul link. Each RU 340 may communicate with one or more UEs 120 via a corresponding radio frequency (RF) access link. In some implementations, a UE 120 may be served simultaneously by multiple RUs 340.

[0061] Each of these units (including CU 310, DU 330, RU 340) and the near-RT RIC 325, non-RT RIC 315, and SMO frame 305 may include or be coupled to one or more interfaces configured to receive or transmit signals, data, or information (collectively, signals) via wired or wireless transmission media. Each of these units, or an associated processor or controller providing instructions to one or more communication interfaces of the respective unit, may be configured to communicate with one or more other units via transmission media. In some examples, each unit may include a wired interface and a wireless interface configured to receive signals or transmit signals to one or more other units via a wired transmission media, and the wireless interface may include a receiver, transmitter, or transceiver (such as an RF transceiver) configured to receive signals or transmit signals to one or more other units via a wireless transmission media, or both.

[0062] In some aspects, the CU 310 can host one or more higher-level control functions. Such control functions may include Radio Resource Control (RRC) functions, Packet Data Convergence Protocol (PDCP) functions, or Service Data Adaptation Protocol (SDAP) functions, etc. Each control function can be implemented using an interface configured to signal to other control functions hosted by the CU 310. The CU 310 can be configured to handle user plane functions (e.g., Central Unit-User Plane (CU-UP) functions) or control plane functions (e.g., Central Unit-Control Plane (CU-CP) functions). In some implementations, the CU 310 can be logically divided into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP units can communicate bidirectionally with the CU-CP units via an interface such as an E1 interface. The CU 310 can be implemented to communicate with the DU 330 for network control and signaling purposes, as needed.

[0063] Each DU 330 may correspond to a logical unit comprising one or more base station functions for controlling the operation of one or more RU 340s. In some aspects, the DU 330 may host one or more of the Radio Link Control (RLC) layer, Medium Access Control (MAC) layer, and one or more high physical (PHY) layers, at least in part, according to functional splits (such as those defined by 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, etc. In some aspects, the DU 330 may also host one or more low PHY layers, such as those implemented by one or more modules for Fast Fourier Transform (FFT), Inverse FFT (iFFT), Digital Beamforming, or Physical Random Access Channel (PRACH) extraction and filtering, etc. Each layer (which may also be referred to as a module) may be implemented using an interface configured to communicate signals with other layers (and modules) hosted by the DU 330 or with control functions hosted by the CU 310.

[0064] Each RU 340 can implement lower-layer functionality. In some deployments, the RU 340 controlled by the DU 330 can correspond to a logical node that hosts RF processing functions or low-PHY layer functions, such as performing FFT, performing iFFT, digital beamforming, or PRACH extraction and filtering, based on function splitting (e.g., function splitting defined by 3GPP) (such as lower-layer function splitting). In this architecture, each RU 340 can be operated to handle over-the-air (OTA) communications with one or more UE 120s. In some specific implementations, the real-time and non-real-time aspects of control plane and user plane communications with the RU 340 can be controlled by the corresponding DU 330. In some scenarios, this configuration allows each DU 330 and CU 310 to be implemented in a cloud-based RAN architecture, such as a vRAN architecture.

[0065] The SMO framework 305 can be configured to support RAN deployment and provisioning of both non-virtualized and virtualized network elements. For non-virtualized network elements, the SMO framework 305 can be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which can be managed via operation and maintenance interfaces such as the O1 interface. For virtualized network elements, the SMO framework 305 can be configured to interact with cloud computing platforms such as the Open Cloud (O-Cloud) platform 390 to perform network element lifecycle management (such as instantiating virtualized network elements) via cloud computing platform interfaces such as the O2 interface. Such virtualized network elements may include, but are not limited to, CU 310, DU 330, RU 340, non-RT RIC 315, and near-RTTRIC 325. In some specific implementations, the SMO framework 305 may communicate with 4G RAN hardware aspects such as the Open eNB (O-eNB) 311 via the O1 interface. Additionally, in some implementations, the SMO framework 305 can communicate directly with each of one or more RUs 340 via a corresponding O1 interface. The SMO framework 305 may also include a non-RT RIC 315 configured to support the functionality of the SMO framework 305.

[0066] The non-RT RIC 315 can be configured to include logical functions that enable non-real-time control and optimization of RAN elements and resources, including AI / ML workflows for model training and updates, or policy-based guidance for applications / features in the near-RT RIC 325. The non-RT RIC 315 can be coupled to or communicate with the near-RT RIC 325, such as via an A1 interface. The near-RT RIC 325 can be configured to include logical functions that enable near real-time control and optimization of RAN elements and resources via an interface, such as an E2 interface, through data collection and action, connecting one or more CU 310s, one or more DU 330s, or both, and O-eNBs to the near-RT RIC 325.

[0067] 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 an external server. This information can be utilized by the near-RT RIC 325 and can be received from non-network data sources or network functions at the SMO framework 305 or the non-RT RIC 315. 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 in performance and employ AI / ML models to perform corrective actions via the SMO framework 305 (such as reconfiguration via the O1 interface) or via the creation of RAN management policies (such as A1 interface policies).

[0068] In wireless communication systems, the network selection process is a process available to the UE to select a network (such as a Public Land Mobile Network (PLMN)) for the UE to attempt to register with. The legacy PLMN selection process includes the following steps: (1) detecting a trigger for performing PLMN selection; (2) searching for available PLMNs; and (3) selecting the PLMN to attempt to register with from the available PLMNs identified as search results. One legacy trigger for performing PLMN selection is recovery from coverage loss (or power-on after a power outage). In this scenario, the PLMN search is performed immediately and exhaustively, thus consuming significant UE power. Furthermore, this search may disrupt existing connections and degrade the user experience. Another legacy trigger for performing PLMN selection is a periodic search trigger, which searches for a higher-priority PLMN when the UE registers with a Visited PLMN (VPLMN). In this scenario, the PLMN search is performed on a periodic basis based on a set of parameters pre-configured in the UE by the Home PLMN (HPMLN). This search is performed as a background operation and generally has minimal impact on existing connections and the user experience. This parameter set may include, for example, intervals between network searches or the minimum interval between network searches. A PLMN search performed in response to any trigger provides results in the form of a list of available PLMNs. The UE then selects a PLMN from the list of available PLMNs based on PLMN priority information. PLMN priority information may be pre-configured by the HPLMN (in other words, PLMN selection can be performed automatically) or may be determined based on user input (in other words, PLMN selection can be performed manually).

[0069] Furthermore, some wireless communication systems support slice-based PLMN selection (in addition to legacy PLMN selection). The trigger for performing slice-based PLMN selection can be determining that the VPLMN to which the UE is registered does not support slices corresponding to one or more services to be provided to the UE. In practice, service slice mapping information indicating the mapping between services and slices can be pre-configured in the UE by the HPLMN using, for example, a UE routing policy (URSP). Additionally, the UE can receive information indicating slices supported by the registered VPLMN via Non-Access Stratum (NAS) signaling (e.g., during registration or configuration update procedures). Regarding slice-based PLMN selection, the UE can utilize slice-based PLMN priority information pre-configured by the HPLMN. This information can be referred to as slice-based PLMN selection information. Here, slice-based PLMN selection information may take into account slices supported by a given available PLMN.

[0070] The manner in which a PLMN search is performed in response to triggers associated with slice-based PLMN selection as described above should be defined. It is worth noting that immediate and exhaustive searches similar to those performed in response to the first legacy triggers described above (e.g., searches performed in connection with recovery from coverage loss) may not be suitable for slice-based PLMN selections performed in response to such slice-based triggers. For example, services may be initiated relatively frequently on the UE, meaning that power consumption associated with a PLMN search will increase, thereby reducing the UE's battery life. Furthermore, some services may be latency-tolerant and do not require immediate connection, meaning that an immediate search may not be necessary. On the other hand, some services may be considered critical, and any unavailability of such services may be equivalent to coverage loss. Additionally, this search may result in the interruption of one or more existing connections and degrade the user experience.

[0071] Additionally, periodic PLMN searches based on legacy search intervals may not be suitable for slice-based PLMN selection. For example, for periodic PLMN searches, legacy search intervals can be configured as values ​​between 6 minutes and 8 hours, with a default value of 60 minutes. Such intervals may not be suitable for all services to be provided to the UE. Furthermore, legacy periodic searches are targeted at higher-priority PLMNs and are neither service-aware nor slice-aware.

[0072] The various aspects generally involve slice-based network selection and initiating network searches. Some aspects more specifically involve initiating network searches based on or otherwise determining that the registered network does not support slices corresponding to the service to be provided to the UE. In some examples, determining that the registered network does not support slices corresponding to the service can be based on or otherwise based on a slice identifier associated with the service. Some other aspects involve selecting a network selection mode associated with performing a network search based on or otherwise based on an indicator indicating a network selection mode. In some examples, the indicator is based on whether slice-based network selection information is configured on the UE.

[0073] Specific aspects of the subject matter described in this disclosure can be implemented to achieve one or more of the following potential advantages. In some examples, the described techniques can be used to implement slice-based network selection and further to enable network searches to be performed in response to triggers associated with slice-based network selection. In some aspects, the described techniques implement slice-based network selection and associated network searches in a way that reduces UE power consumption (e.g., compared to performing legacy network searches in response to slice-based network search triggers), thereby increasing UE battery life. Furthermore, the techniques described herein implement service-aware or slice-aware network searches. For example, the techniques described herein implement network searches that take into account service- or slice-based latency tolerances, which facilitates network searches without wasting battery power while ensuring service availability. Additional details are provided below.

[0074] Figure 4 This is a diagram illustrating example 400 associated with slice-based network selection according to this disclosure. Figure 4 As shown, Example 400 includes communication between UE 120, a network node 110 associated with the home network of UE 120 (home network node 110), and a network node 110 associated with the visited network of UE 120 (visited network node 110). In some aspects, the home network node 110, the visited network node 110, and the UE 120 may be included in one or more wireless networks (such as one or more wireless networks 100). Given network node 110 and UE 120, they may communicate via a radio access link (which may include an uplink and a downlink).

[0075] like Figure 4 As shown, in the first operation 402, UE 120 may receive service slice mapping information. The service slice mapping information includes information indicating the 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 corresponding services supported by each of the one or more slices. In some aspects, UE 120 may receive the service slice mapping information when UE 120 registers with a home network (e.g., HPLMN). For example, UE 120 may register with a home network (e.g., Home Wireless Network 100) and may receive the service slice mapping information from home network node 110 upon registration with the home network. In some aspects, UE 120 may receive the service slice mapping information based on URSP or otherwise according to URSP.

[0076] In the second operation 404, UE 120 may receive slice support information associated with a visited network (e.g., a VPLMN). The slice support information includes information indicating 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, UE 120 may receive the slice support information while UE 120 is registering with or has registered with a visited network (e.g., visited wireless network 100). For example, UE 120 may receive the slice support information from visited network node 110 during a registration process associated with registering with the visited network. As another example, UE 120 may receive the slice support information from visited network node 110 during a configuration update process performed after UE 120 has registered with the visited network. In some aspects, UE 120 may receive the slice support information via NAS signaling.

[0077] In the third operation 406, UE 120 may receive a connection request associated with an application. For example, a user may cause an application to be triggered or executed on UE 120. Here, the application may be associated with one or more services, meaning that one or more services will be provided by the application. These services may include, for example, voice services, video services, internet services, satellite services, Internet Protocol Multimedia Subsystem (IMS), or data services, etc. In another example, UE 120 may cause the application to be triggered or executed automatically (without user intervention).

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

[0079] In the fifth operation 410, UE 120 may determine that the network to which UE 120 is registered does not support any slice associated with the slice identifier. For example, UE 120 may determine, based on or otherwise according to slice support information, that the network to which UE 120 is registered (e.g., the visited network associated with visited network node 110) does not support any slice associated with the slice identifier identified by UE 120, meaning that the registered network does not support the service to be provided by the application. In one aspect, this determination may be based on a comparison between a list of slices requested by UE 120 from the network (e.g., home network node 110) and a list of slices indicated by the network as available to and permitted for use by UE 120. In one aspect, the list of slices requested by UE 120 is included in the Request Network Slice Selection Assistance Information (NSSAI) information element included in a signaling message transmitted by 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 to and permitted for use by UE 120 is included in the Allow NSSAI information element included in a registration response message.

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

[0081] In some respects, UE 120 can initiate a search for another network based on a start time determined by UE 120. That is, UE 120 can determine a start time associated with initiating a search, and can initiate a search based on the determined start time.

[0082] In some respects, the start time of initiating a search is based on whether the network search is performed on a periodic basis. For example, UE 120 can determine that the network search is performed on a periodic basis (rather than immediately) and can determine the start time accordingly.

[0083] In some respects, in the case of periodic network searches, UE 120 can use periodic search interval parameters. T The value is used to initiate a search for another network. In some respects, the periodic search interval parameter... T The value can indicate time (e.g., in minutes). Alternatively, the search interval parameter can be periodically traversed. T The value can indicate that a periodic search for slice-based network selection should not be performed (e.g., a value of 0 indicates that a periodic search should not be performed). In some respects, the periodic search interval parameter... TThe value can be stored in the Universal Subscriber Identity Module (USIM) of the UE 120. In some respects, if the periodic search interval parameter is not stored... T If the value is specified, UE 120 can use the default value, such as 6 minutes or 60 minutes.

[0084] In some respects, periodic search interval parameters T This is associated with slice-based network selection. In other words, it involves periodically searching for interval parameters. T These can be parameters specifically configured for use in conjunction with slice-based network selection (in other words, periodic search interval parameters). T It may not be configured for use in conjunction with network selection initiated based on legacy triggers.

[0085] In some respects, periodic search interval parameters T The value is based on information associated with the services to be provided by the application. That is, in some respects, the periodic search interval parameter... T The value is determined based on or otherwise according to the services to be provided by the application. For example, UE 120 may be configured with a periodic search interval parameter. T Multiple values, each associated with a corresponding service. Here, UE 120 can periodically search for interval parameters. T The value is determined as the value mapped to the service.

[0086] Additionally or alternatively, in some respects, periodic search interval parameters T The value can be based on the type of service to be provided by the application. That is, in some respects, periodically searching for interval parameters. T The value is determined based on or otherwise according to the type of service to be provided by the application. For example, UE 120 can be configured with a periodic search interval parameter. T Multiple values ​​are assigned, each associated with a corresponding service type. Here, UE 120 can determine the service type and then periodically search for interval parameters. T The value is determined as the value mapped to the determined service type.

[0087] In some respects, periodic search interval parameters T The value is based on the connectivity capability identifier corresponding to the service type of the service to be provided by the application. For example, in some aspects, the service type may correspond to a connectivity capability identifier, and the connectivity capability identifier may be used to determine the parameters of the periodic search interval. T The value of . As an example, the connectivity capability identifier can correspond to a multiplier coefficient. M And periodically search interval parameters TThe value can be multiplied by the multiplier coefficient. M The value is used to determine the periodic search interval parameter. T The modified value, which will be used in conjunction with determining the start time. In some respects, the multiplier coefficient... M The value can be based on or otherwise determined by the service type, which corresponds to the connectivity capability identifier as described above. In a specific example, for instance, the multiplier coefficient. M The value for IMS service can be 1 ( M =1), and for internet services it can be 2 ( M =2). In some respects, the connectivity identifier and the multiplier coefficient M The mapping between the corresponding values ​​can be stored in the USIM of UE 120.

[0088] In some respects, periodic search interval parameters T The value of can be greater than or equal to the minimum periodicity search interval parameter value. That is to say, in some respects, the periodicity search interval parameter... T The value can be set to be no less than the minimum periodic search time value based on the slice. In some respects, the periodic search interval parameter... T A value greater than the minimum periodicity search interval parameter value can save battery power. In some respects, the minimum periodicity search interval parameter value is stored in the UE 120. For example, the UE 120 may be pre-configured with the minimum periodicity search interval parameter value.

[0089] In operation, if the interval parameter is searched periodically... T The value indicates the time interval, and UE 120 detects a trigger for performing slice-based network selection (e.g., UE 120 determines that the network to which UE 120 is registered does not support any slice associated with the slice identifier), then UE 120 searches the interval parameter periodically. T The value of is associated with performing a periodic network search in relation to performing slice-based network selection.

[0090] In some respects, the start time of initiating a search is based on whether the network search is performed on an aperiodic basis. For example, UE 120 can determine that the network search is performed on an aperiodic basis (rather than periodically) and can determine the start time accordingly.

[0091] In some aspects, UE 120 can initiate a search for another network based on a network search performed on an aperiodic basis. For example, UE 120 can determine that a network search is performed on an aperiodic basis and can initiate the network search immediately (e.g., the start time may immediately follow the determination to perform an aperiodic search). Therefore, in some aspects, if UE 120 determines that an aperiodic search is to be performed, UE 120 can initiate the network search immediately. In some aspects, if the periodic search interval parameter... T The value indicates that periodic slice-based network selection should not be performed (e.g., if the periodic search interval parameter is used). T If the value of 0 is 0 and UE 120 detects a trigger (e.g., UE 120 determines that the network to which UE 120 is registered does not support any slice associated with the slice identifier), then UE 120 may perform a single network search in association with performing slice-based network selection.

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

[0093] like Figure 5 As shown, in the 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 the network selection mode to be used by the UE 120 in connection with performing network selection.

[0094] In some aspects, the indicator is slice-based network selection information associated with UE 120. That is, in some aspects, the indicator is the presence (e.g., in memory) or receipt of slice-based network selection information. In some aspects, the slice-based network selection information includes priority information associated with multiple networks and information indicating one or more corresponding slices supported by each of the multiple networks. That is, in some aspects, the slice-based network selection information includes a priority list of networks and corresponding slices supported by each network in the priority list. Alternatively, in some aspects, the indicator is the absence of slice-based network selection information associated with UE 120. That is, in some aspects, the indicator is the absence or non-receipt of slice-based network selection information.

[0095] In the second operation 504, UE 120 may select a network selection mode based on an indicator associated with network selection mode selection. That is, UE 120 may select a network selection mode based on or otherwise according to the indicator.

[0096] In some respects, 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 UE 120 has received slice-based network selection information), then UE 120 may select the slice-based network selection mode as the network selection mode to be used by UE 120 in association with performing network selection.

[0097] Alternatively, in some respects, the selected network selection mode is a legacy network selection mode. For example, if the indicator is that slice-based network selection information is missing (in other words, if UE 120 has not stored or has not yet received slice-based network selection information), UE 120 may select a legacy network selection mode as the network selection mode to be used by UE 120 in association with performing network selection.

[0098] In the third operation 506, UE 120 may detect a trigger for performing a network selection procedure. In some aspects, the trigger for performing the network selection procedure may be associated with the selected network selection mode. For example, if the selected network selection mode is a slice-based network selection mode, the trigger may be service activation on UE 120 (e.g., 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, the trigger may be recovery after coverage loss or periodic triggering when UE 120 is registered to a visited network. It is noteworthy that if the selected network selection mode is a slice-based network selection mode, legacy triggering (e.g., recovery after coverage loss or periodic searching on a visited network) may not serve as the trigger for network selection procedure execution. Similarly, if the selected network selection mode is a legacy network selection mode, slice-based triggering (e.g., service activation on UE 120) may not serve as the trigger for network selection procedure execution.

[0099] In the fourth operation 508, UE 120 may perform a network selection process in association with the detection of a trigger for performing the network selection process, based on the selected network selection mode. That is, based on the detection of a trigger for performing the network selection process, UE 120 may perform the network selection process according to the selected network selection mode.

[0100] In some aspects, the network selection process is a slice-based network selection process. For example, the selected network selection mode may be a slice-based network selection mode, and therefore UE 120 may perform a slice-based network selection process in response to, based on, or otherwise associated with the detection of a trigger. In some such aspects, UE 120 may perform a slice-based network selection process based on or otherwise according to slice-based network selection information. That is, UE 120 may use slice-based network selection information in connection with performing network selection according to a slice-based network selection process. As another example, the selected network selection mode may be a legacy network selection mode, and therefore UE 120 may perform a legacy network selection process in response to, based on, or otherwise associated with the detection of a trigger. In such aspects, UE 120 does not use slice-based network selection information in connection with performing a legacy network selection process.

[0101] Figure 6 This is a flowchart illustrating an example process 600 supporting slice-based network selection, performed, for example, at a UE or a device of a UE, according to the present disclosure. Example process 600 is an example in which the device or the UE (e.g., UE 120) performs operations associated with slice-based network selection.

[0102] like Figure 6 As shown, in some aspects, process 600 may include receiving a connection request associated with an application (block 610). For example, a UE (such as through using...) Figure 8 The communication manager 140 or network search component 808 described herein can receive connection requests associated with the application, as described above.

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

[0104] like Figure 6 As further shown, in some aspects, process 600 may include initiating a search for another network based on the fact that the network to which the UE is registered does not support the slice associated with the slice identifier (box 630). For example, the UE (such as by using...) Figure 8 The communication manager 140 or network search component 808 described above can initiate a search for another network if the network to which the UE is registered does not support the slice associated with the slice identifier.

[0105] Process 600 may include additional aspects, such as any single aspect or any combination of aspects described in one or more other processes described below or in conjunction with other parts of this document.

[0106] In the first additional aspect, the search for another network is initiated based on the start time determined by the UE.

[0107] In the second additional aspect, either alone or in combination with the first aspect, the start time for initiating a search against another network is based on a network search performed on a periodic basis.

[0108] In a third additional aspect, either alone or in combination with one or more of the first and second aspects, a search for another network is initiated based on the value of a periodic search interval parameter.

[0109] In the fourth additional aspect, either alone or in combination with one or more of the first to third aspects, the value of the periodic search interval parameter is stored in the UE's general subscriber identity module.

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

[0111] In the sixth additional aspect, either alone or in combination with one or more of the first to fifth aspects, the value of the periodic search interval parameter is based on information associated with the services provided by the application.

[0112] In the seventh additional aspect, either alone or in combination with one or more of the first to sixth aspects, the value of the periodic search interval parameter is based on the service type of the service provided by the application.

[0113] In the eighth additional aspect, either alone or in combination with one or more of the first to seventh aspects, the value of the periodic search interval parameter is based on a connectivity identifier corresponding to the service type of the service provided by the application.

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

[0115] In the tenth additional aspect, the minimum periodicity search interval parameter value is stored in the UE, either alone or in combination with one or more of the first to ninth aspects.

[0116] In the eleventh additional aspect, the start time for initiating a search for another network, either alone or in combination with one or more of the first to tenth aspects, is based on a network search performed on a non-periodic basis.

[0117] In the twelfth additional aspect, a search for another network is initiated, either alone or in combination with one or more of the first to eleventh aspects, based on a network search performed on a non-periodic basis.

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

[0119] In the fourteenth additional aspect, in conjunction with the thirteenth aspect, it is supported that the slice list is received in the NSSAI information element.

[0120] Figure 7 This is a flowchart illustrating an example process 700 supporting slice-based network selection, performed, for example, at a UE or a device of a UE, according to this disclosure. Example process 700 is an example in which the device or the UE (e.g., UE 120) performs operations associated with slice-based network selection.

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

[0122] like Figure 7 As further shown, in some aspects, process 700 may include performing a network selection process in association with the detection of a trigger for performing the network selection process, based on the selected network selection mode (block 720). For example, a UE (such as by using...) Figure 9 The communication manager 140 or selection component 908 described herein can perform a network selection process in association with the detection of a trigger for performing the network selection process, depending on the selected network selection mode, as described above.

[0123] Process 700 may include additional aspects, such as any single aspect or any combination of aspects described in one or more other processes described below or in conjunction with other parts of this document.

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

[0125] In a second additional aspect, either alone or in combination with the first aspect, the slice-based network selection information includes priority information associated with multiple networks and information indicating one or more corresponding slices supported by each of the multiple networks.

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

[0127] In the fourth additional aspect, the network selection process is a slice-based network selection process, either alone or in combination with one or more of the first to third aspects.

[0128] In the fifth additional aspect, the network selection process is associated with slice-based network selection information, either alone or in combination with one or more of the first to fourth aspects.

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

[0130] In the seventh additional aspect, the selected network selection mode is the old network selection mode, either alone or in combination with one or more of the first to sixth aspects.

[0131] In the eighth additional aspect, the triggering of the network selection process, either alone or in combination with one or more of the first to seventh aspects, is associated with the selected network selection mode.

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

[0133] Figure 8 This is a diagram of an example device 800 for wireless communication supporting slice-based network selection according to this disclosure. Device 800 may be a UE, or a UE may include device 800. In some aspects, device 800 includes a receiving component 802, a transmitting component 804, and a communication manager 140 that can communicate with each other (e.g., via one or more buses). As shown, device 800 can use the receiving component 802 and the transmitting component 804 to communicate with another device 806 (such as a UE, a network node, or another wireless communication device).

[0134] In some respects, device 800 may be configured or be operable to perform the functions described herein. Figure 4 One or more operations described herein. Additionally or alternatively, device 800 may be configured or able to operate to perform one or more processes described herein, such as Figure 6 The process 600. In some aspects, the device 800 may include the above-described combination. Figure 2 One or more components of the UE as described.

[0135] Receiver 802 may receive communications, such as reference signals, control information, or data communications, from device 806. Receiver 802 may provide the received communications to one or more other components of device 800, such as communication manager 140. In some aspects, receiver 802 may perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) and may provide the processed signals to one or more other components. In some aspects, receiver 802 may include the combinations described above. Figure 2 The described UE may have one or more antennas, one or more modems, one or more demodulators, one or more MIMO detectors, one or more receiver processors, one or more controllers / processors, or one or more memories.

[0136] The transmitting component 804 can transmit communications, such as reference signals, control information, or data communications, to the device 806. In some aspects, the communication manager 140 can generate communications and transmit the generated communications to the transmitting component 804 for transmission to the device 806. In some aspects, the transmitting component 804 can perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and can transmit the processed signals to the device 806. In some aspects, the transmitting component 804 may include the above-described combinations. Figure 2 The described UE 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. In some aspects, the transmit component 804 may co-located with the receive component 802 in one or more transceivers.

[0137] Communication manager 140 may receive, or may cause receiving component 802 to receive, a connection request associated with an application. Communication manager 140 may obtain a slice identifier associated with a service provided by the application. Communication manager 140 may initiate a search for another network if the network to which the UE is registered does not support the slice associated with the slice identifier. In some aspects, communication manager 140 may perform one or more operations as described elsewhere herein by one or more components of communication manager 140.

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

[0139] The network search component 808 can receive connection requests associated with applications. The network search component 808 can obtain slice identifiers associated with services provided by the application. The network search component 808 can initiate a search for another network if the network to which the UE is registered does not support the slice associated with the slice identifier.

[0140] Figure 8 The number and arrangement of components shown are provided as an example. In practice, different arrangements may exist. Figure 8 The components shown are compared to additional components, fewer components, different components, or components arranged in a different manner. Furthermore, Figure 8 The two or more components shown can be implemented within a single component, or Figure 8 The single component shown can be implemented as multiple distributed components. Additionally or alternatively, Figure 8 The collection of (one or more) components shown is executable and described as being composed of Figure 8 Another set of components shown performs one or more functions.

[0141] Figure 9This is a diagram of an example device 900 for wireless communication supporting slice-based network selection according to the present disclosure. Device 900 may be a UE, or a UE may include device 900. In some aspects, device 900 includes a receiving component 902, a transmitting component 904, and a communication manager 140 that can communicate with each other (e.g., via one or more buses). As shown, device 900 can use the receiving component 902 and the transmitting component 904 to communicate with another device 906 (such as a UE, a network node, or another wireless communication device).

[0142] In some respects, device 900 may be configured or be operable to perform the functions described herein. Figure 5 One or more operations described herein. Additionally or alternatively, device 900 may be configured or able to operate to perform one or more processes described herein, such as Figure 7 The process 700. In some aspects, the device 900 may include the above-described combination. Figure 2 One or more components of the UE as described.

[0143] Receiver 902 may receive communications, such as reference signals, control information, or data communications, from device 906. Receiver 902 may provide the received communications to one or more other components of device 900, such as communication manager 140. In some aspects, receiver 902 may perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) and may provide the processed signals to one or more other components. In some aspects, receiver 902 may include the combinations described above. Figure 2 The described UE may have one or more antennas, one or more modems, one or more demodulators, one or more MIMO detectors, one or more receiver processors, one or more controllers / processors, or one or more memories.

[0144] Transmitting component 904 can send communications, such as reference signals, control information, or data communications, to device 906. In some aspects, communication manager 140 can generate communications and send the generated communications to transmitting component 904 for transmission to device 906. In some aspects, transmitting component 904 can perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and can transmit the processed signals to device 906. In some aspects, transmitting component 904 can include the above-described combinations. Figure 2The described UE 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. In some aspects, the transmit component 904 may co-located with the receive component 902 in one or more transceivers.

[0145] The communication manager 140 can select a network selection mode according to an indicator associated with the network selection mode selection. The communication manager 140 can then perform a network selection process in association with the detection of a trigger for executing the network selection process, depending on the selected network selection mode. In some aspects, the communication manager 140 can perform one or more operations as described elsewhere herein by one or more components of the communication manager 140.

[0146] Communication manager 140 may include the above-mentioned components. Figure 2 The described UE includes one or more controllers / processors and / or one or more memories. In some aspects, the communication manager 140 includes a set of components such as selection component 908. Alternatively, this set of components may be separate from and different from the communication manager 140. In some aspects, one or more components in this set of components may include those described above. Figure 2 The described UE may include one or more controllers / processors, one or more memories, or may be implemented within one or more controllers / processors or one or more memories of the UE. Additionally or alternatively, one or more components in this set of components may be implemented at least partially as software stored in one or more memories. For example, a component (or a portion thereof) may be implemented as instructions or code stored in a non-transitory computer-readable medium and may be executed by one or more controllers or one or more processors to perform the function or operation of the component.

[0147] Selection component 908 can select a network selection mode according to an indicator associated with the network selection mode selection. Selection component 908 can execute a network selection process in association with the detection of a trigger for performing the network selection process, depending on the selected network selection mode.

[0148] Figure 9 The number and arrangement of components shown are provided as an example. In practice, different arrangements may exist. Figure 9 The components shown are compared to additional components, fewer components, different components, or components arranged in a different manner. Furthermore, Figure 9 The two or more components shown can be implemented within a single component, or Figure 9 The single component shown can be implemented as multiple distributed components. Additionally or alternatively, Figure 9 The collection of (one or more) components shown is executable and described as being composed of Figure 9 Another set of components shown performs one or more functions.

[0149] The following provides an overview of some aspects of this disclosure: Aspect 1: A method for wireless communication performed by a user equipment (UE), the method comprising: receiving a connection request associated with an application; obtaining a slice identifier associated with a service provided by the application; and initiating a search for another network based on the fact that the network to which the UE is registered does not support the slice associated with the slice identifier.

[0150] Aspect 2: According to the method of aspect 1, wherein the search for the other network is initiated based on a start time determined by the UE.

[0151] Aspect 3: The method according to any one of Aspects 1 to 2, wherein the start time of initiating the search against the other network is based on a network search performed on a periodic basis.

[0152] Aspect 4: The method according to any one of Aspects 1 to 3, wherein the search for the other network is initiated based on the value of a periodic search interval parameter.

[0153] Aspect 5: According to the method of aspect 4, the value of the periodic search interval parameter is stored in the general subscriber identity module of the UE.

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

[0155] Aspect 7: The method according to any one of Aspects 4 to 6, wherein the value of the periodic search interval parameter is based on information associated with the service provided by the application.

[0156] Aspect 8: The method according to any one of Aspects 4 to 7, wherein the value of the periodic search interval parameter is based on the service type of the service provided by the application.

[0157] Aspect 9: The method according to any one of Aspects 4 to 8, wherein the value of the periodic search interval parameter is based on a connectivity identifier corresponding to the service type of the service provided by the application.

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

[0159] Aspect 11: According to the method of aspect 10, the minimum periodicity search interval parameter value is stored in the UE.

[0160] Aspect 12: The method according to any one of Aspects 1 to 11, wherein the start time of initiating the search against the other network is based on a network search performed on a non-periodic basis.

[0161] Aspect 13: The method according to any one of Aspects 1 to 12, wherein the search for the other network is initiated based on a network search performed on an aperiodic basis.

[0162] Aspect 14: The method according to any one of Aspects 1 to 13, wherein determining that the network to which the UE is registered does not support a slice 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: According to the method of aspect 14, the list of supported slices is received in the Network Slice Selection Auxiliary Information (NSSAI) information element.

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

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

[0166] Aspect 18: According to the method of aspect 17, the slice-based network selection information includes priority information associated with a plurality of networks and information indicating one or more corresponding slices supported by each of the plurality of networks.

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

[0168] Aspect 20: The method according to any one of aspects 16 to 19, wherein the network selection process is a slice-based network selection process.

[0169] Aspect 21: The method according to any one of aspects 16 to 20, wherein the network selection process is associated with slice-based network selection information.

[0170] Aspect 22: The method according to any one of Aspects 16 to 21, wherein the indicator is missing slice-based network selection information associated with the UE.

[0171] Aspect 23: The method according to any one of Aspects 16 to 22, wherein the selected network selection mode is an old-style network selection mode.

[0172] Aspect 24: The method according to any one of aspects 16 to 23, wherein the trigger for performing the network selection process is associated with the selected network selection mode.

[0173] Aspect 25: The method according to any one of Aspects 16 to 24, wherein the selected network selection mode is a slice-based network selection mode, and detecting the trigger includes detecting 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 to 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 according to one or more of aspects 1 to 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 being configured to cause the device to perform the method according to one or more of aspects 1 to 25.

[0176] Aspect 28: An apparatus for wireless communication, the apparatus comprising at least one component for performing the method according to one or more of aspects 1 to 25.

[0177] Aspect 29: A non-transitory computer-readable medium storing code for wireless communication, said code including instructions executable by one or more processors to perform the methods described in one or more of aspects 1 to 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 according to one or more of aspects 1 to 25.

[0179] Aspect 31: A device for wireless communication, the device including a processing system comprising one or more processors and one or more memories coupled to the one or more processors, the processing system being configured to cause the device to perform the method according to one or more of aspects 1 to 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 being individually or collectively configured to cause the device to perform the method according to one or more of aspects 1 to 25.

[0181] While the foregoing disclosure provides examples and descriptions, it is not intended to be exhaustive or to limit the aspects to the precise form disclosed. Modifications and variations may be made based on the foregoing disclosure, or from various forms of practice.

[0182] As used herein, the term "component" is intended to be broadly interpreted as hardware or a combination of hardware and software. "Software" should be broadly interpreted as instructions, instruction sets, code, code segments, program code, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable programs, threads of execution, procedures, or functions, whether referred to as software, firmware, middleware, microcode, hardware description languages, or other terms. As used herein, a "processor" is implemented in hardware or a combination of hardware and software. It will be apparent that the systems or methods described herein can be implemented in various forms of hardware or combinations of hardware and software. The actual dedicated control hardware or software code used to implement these systems or methods is not limited in any way. Therefore, the operation and behavior of these systems or methods are described herein without reference to any specific software code, as those skilled in the art will understand that the software and hardware can be designed to implement these systems or methods, at least in part, based on the description herein.

[0183] As used in this article, depending on the context, "meeting the threshold" can mean a value greater than the threshold, greater than or equal to the threshold, less than the threshold, less than or equal to the threshold, equal to the threshold, not equal to the threshold, etc.

[0184] Although specific combinations of features are set forth 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 stated in the claims or disclosed in the specification. The disclosure of various aspects includes each dependent claim in combination with each other claim in the claim set. As used herein, the phrase “at least one of” in the list of items refers to any combination of these items, including a single member. 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 having multiple identical elements (e.g., 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, action, or instruction used herein should be construed as essential or necessary unless explicitly stated otherwise. Furthermore, as used herein, the articles “a” and “an” are intended to include one or more items and are used interchangeably with “one or more.” Similarly, as used herein, the article “described” is intended to include one or more items mentioned in connection with the article “described” and is used interchangeably with “one or more.” Furthermore, as used herein, the terms “group” and “cluster” are intended to include one or more items and are used interchangeably with “one or more.” If only one item is desired, the phrase “only one” or similar terminology will be used. Moreover, as used herein, the terms “having” and similar terms are intended as open-ended terms that do not limit the elements they modify (e.g., “having” A may also have B). Additionally, the phrase “based on” is intended to mean “at least partially based on” unless otherwise explicitly stated. Furthermore, as used herein, the term “or” is intended to be inclusive when used consecutively and is interchangeable with “and / or” unless otherwise explicitly stated (e.g., if used in conjunction with “either of the two” or “only one of them”).

Claims

1. A user equipment (UE) for wireless communication, the user equipment (UE) comprising: A processing system, comprising one or more processors and one or more memories coupled to the one or more processors, the processing system being configured to cause the UE to: Receive connection requests associated with the application; Obtain the slice identifier associated with the service provided by the application; as well as The search for another network is initiated based on the fact that the network to which the UE is registered does not support the slice associated with the slice identifier.

2. The UE of claim 1, wherein the search for the other network is initiated based on a start time determined by the UE.

3. The UE of claim 1, wherein the start time for initiating the search against the other network is based on a network search performed on a periodic basis.

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

5. The UE according to claim 4, wherein the value of the periodic search interval parameter is stored in the general 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 based on 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 based on the 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 based on a connectivity identifier corresponding to the service type of the service provided by the application.

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

11. The UE according to claim 10, wherein the minimum periodicity search interval parameter value is stored in the UE.

12. The UE of claim 1, wherein the start time for initiating the search against the other network is based on a network search performed on a non-periodic basis.

13. The UE of claim 1, wherein the search for the other network is initiated based on a network search performed on an aperiodic basis.

14. The UE of claim 1, wherein determining that the network to which the UE is registered does not support a slice 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 a Network Slice Selection Assistance Information (NSSAI) information element.

16. A user equipment (UE) for wireless communication, the user equipment (UE) comprising: A processing system, comprising one or more processors and one or more memories coupled to the one or more processors, the processing system being configured to cause the UE to: Select the network selection mode based on the indicator associated with the network selection mode selection; as well as The network selection process is executed in association with the detection of a trigger for performing the network selection process, depending on the selected network selection mode.

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 includes priority information associated with a plurality of networks and information indicating one or more corresponding slices supported by each of 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 process is a slice-based network selection process.

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

22. The UE of claim 16, wherein the indicator is missing 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 triggering for performing the network selection process 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 includes detecting service activation on the UE.

26. A method for wireless communication performed by a user equipment (UE), the method comprising: Receive connection requests associated with the application; Obtain the slice identifier associated with the service provided by the application; as well as The search for another network is initiated based on the fact that the network to which the UE is registered does not support the slice associated with the slice identifier.

27. The method of claim 26, wherein the search for the other network is initiated based on a start time determined by the UE.

28. The method of claim 26, wherein the start time for initiating the search against the other network is based on a network search performed on a periodic basis.

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

30. A method for wireless communication performed by a user equipment (UE), the method comprising: Select the network selection mode based on the indicator associated with the network selection mode selection; as well as The network selection process is executed in association with the detection of a trigger for performing the network selection process, depending on the selected network selection mode.

Images