CN117796039A

CN117796039A - NSSAI of updated request sent by UE

Info

Publication number: CN117796039A
Application number: CN202280053890.5A
Authority: CN
Inventors: O·厄兹蒂尔克; L·F·B·洛佩斯; 朱西鹏
Original assignee: Qualcomm Inc
Current assignee: Qualcomm Inc
Priority date: 2021-08-20
Filing date: 2022-08-16
Publication date: 2024-03-29

Abstract

Aspects presented herein relate to methods and apparatus, including devices, e.g., UEs, for wireless communications. The apparatus may send, to at least one of a network node or a network entity, an indication of one or more future network slices, an indication of one or more current network slices, and/or an indication of one or more past network slices, the future network slices corresponding to network slices for potential future use by the UE, the current network slices corresponding to network slices currently used by the UE, the past network slices corresponding to network slices previously used by the UE. The apparatus may also receive, from the network entity, the indication of the one or more future network slices, the indication of the one or more current network slices, and/or the response to the indication of the one or more past network slices.

Description

NSSAI of updated request sent by UE

Cross Reference to Related Applications

The present application claims the benefit and priority of U.S. provisional application serial No. 63/235,654 entitled "UE assistance information for slicing (UE ASSISTANCE INFORMATION FOR SLICES)" filed 8/20 of 2021 and U.S. non-provisional patent application serial No. 17/819,916 entitled "UE assistance information for slicing (UE ASSISTANCE INFORMATION FOR SLICES)" filed 15 of 2022, which are expressly incorporated herein by reference in their entirety.

Technical Field

The present disclosure relates generally to communication systems, and more particularly to User Equipment (UE) assistance information in wireless communications.

Background

Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, and broadcast. A typical wireless communication system may employ multiple-access techniques capable of supporting communication with multiple users by sharing the available system resources. Examples of such multiple-access techniques 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, and time division synchronous code division multiple access (TD-SCDMA) systems.

These multiple access techniques have been adopted in various telecommunications standards to provide a common protocol that enables different wireless devices to communicate at the urban, national, regional, and even global levels. An example of a telecommunications standard is 5G new air interface (NR). The 5G NR is part of the ongoing mobile broadband evolution promulgated by the third generation partnership project (3 GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., with the internet of things (IoT)) and other requirements. The 5G NR includes services associated with enhanced mobile broadband (emmbb), large-scale machine-type communication (emtc), and ultra-reliable low-latency communication (URLLC). Certain aspects of 5G NR may be based on the 4G Long Term Evolution (LTE) standard. Further improvements in the 5G NR technology are needed. Furthermore, these improvements are applicable to other multiple access techniques and telecommunication standards employing these techniques.

Disclosure of Invention

The following presents a simplified summary of one or more aspects in order to provide a basic understanding of such aspects. This summary is not an extensive overview of all contemplated aspects, and is intended to neither identify key or critical elements of all aspects nor delineate the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to the more detailed description that is presented later.

In one aspect of the disclosure, a method, computer-readable medium, and apparatus are provided. The apparatus may be a User Equipment (UE). The apparatus may store a history of use of the one or more past network slices prior to sending the indication of the one or more past network slices. The apparatus may also calculate a probability of use of the one or more future network slices before sending the indication of the one or more future network slices. In addition, the apparatus may send at least one of an indication of one or more future network slices corresponding to network slices for potential future use by the UE, an indication of one or more current network slices corresponding to network slices currently used by the UE, or an indication of one or more past network slices corresponding to network slices previously used by the UE to at least one of a network node (e.g., a base station) or a network entity. The apparatus may also receive, from the network entity, a response to at least one of the indication of the one or more future network slices, the indication of the one or more current network slices, or the indication of the one or more past network slices. The apparatus may also send a message associated with at least one of the one or more future network slices, the one or more current network slices, or the one or more past network slices to the network node (e.g., base station) based on the response.

In another aspect of the disclosure, methods, computer-readable media, and apparatuses are provided. The apparatus may be a network entity. The apparatus may receive, from at least one User Equipment (UE), at least one of an indication of one or more future network slices corresponding to network slices for potential future use by the at least one UE, an indication of one or more current network slices corresponding to network slices currently used by the UE, or an indication of one or more past network slices corresponding to network slices previously used by the at least one UE. The apparatus may also send, to the at least one UE, a response to at least one of the indication of the one or more future network slices, the indication of the one or more current network slices, or the indication of the one or more past network slices. Further, the apparatus may send network slice selection assistance information (nsai) to at least one network node (e.g., base station) based on at least one of the indication of the one or more future network slices, the indication of the one or more current network slices, or the indication of the one or more past network slices. The apparatus may also configure a network slice structure based on at least one of the one or more future network slices, the one or more current network slices, or the one or more past network slices.

In another aspect of the disclosure, methods, computer-readable media, and apparatuses are provided. The apparatus may be a network node (e.g., a base station). The apparatus may receive, from at least one User Equipment (UE), at least one of an indication of one or more future network slices corresponding to network slices for potential future use by the at least one UE, an indication of one or more current network slices corresponding to network slices currently used by the UE, or an indication of one or more past network slices corresponding to network slices previously used by the at least one UE. The apparatus may also receive a message associated with at least one of the one or more future network slices, the one or more current network slices, or the one or more past network slices from the at least one UE. Further, the apparatus may send network slice selection assistance information (nsai) to at least one other network node (e.g., a base station) based on at least one of the indication of the one or more future network slices, the indication of the one or more current network slices, or the indication of the one or more past network slices. The apparatus may also be configured for at least one of a handoff procedure, a redirection procedure, a serving cell change, or a cell addition of a Carrier Aggregation (CA), the configuration being based on at least one of the one or more future network slices, the one or more current network slices, or the one or more past network slices.

To the accomplishment of the foregoing and related ends, one or more aspects comprise the features hereinafter fully described and particularly pointed out in the claims. The following description and the annexed drawings set forth in detail certain illustrative features of the one or more aspects. These features are indicative, however, of but a few of the various ways in which the principles of various aspects may be employed and the present specification is intended to include all such aspects and their equivalents.

Drawings

Fig. 1 is a diagram illustrating an example of a wireless communication system and an access network.

Fig. 2A is a diagram illustrating an example of a first frame in accordance with aspects of the present disclosure.

Fig. 2B is a diagram illustrating an example of a Downlink (DL) channel within a subframe in accordance with various aspects of the disclosure.

Fig. 2C is a diagram illustrating an example of a second frame in accordance with aspects of the present disclosure.

Fig. 2D is a diagram illustrating an example of an Uplink (UL) channel within a subframe in accordance with various aspects of the disclosure.

Fig. 3 is a diagram illustrating an example of a base station and a User Equipment (UE) in an access network.

Fig. 4 is a diagram illustrating an example of a network slice framework.

Fig. 5 is a diagram showing an example of a registration process.

Fig. 6 is a diagram showing an example of a registration process.

Fig. 7 is a diagram illustrating exemplary communications between a UE, a network node (e.g., a base station), and a network entity (e.g., an access and mobility management function (AMF)).

Fig. 8 is a flow chart of a method of wireless communication.

Fig. 9 is a flow chart of a method of wireless communication.

Fig. 10 is a flow chart of a method of wireless communication.

Fig. 11 is a flow chart of a method of wireless communication.

Fig. 12 is a flow chart of a method of wireless communication.

Fig. 13 is a flow chart of a method of wireless communication.

Fig. 14 is a diagram illustrating an example of a hardware implementation for the example apparatus.

Fig. 15 is a diagram illustrating an example of a hardware implementation for the example apparatus.

Fig. 16 is a diagram illustrating an example of a hardware implementation for the example apparatus.

Detailed Description

The detailed description set forth below in connection with the appended drawings is intended as a description of various configurations and is not intended to represent the only configurations in which the concepts described herein may be implemented. The detailed description includes specific details for the purpose of providing a thorough understanding of the various concepts. It will be apparent, however, to one skilled in the art that the concepts may be practiced without these specific details. In some instances, well-known structures and components are shown in block diagram form in order to avoid obscuring the concepts.

Several aspects of the telecommunications system will now be described with reference to various apparatus and methods. These apparatus and methods will be described in the following detailed description and illustrated in the accompanying drawings by various blocks, components, circuits, processes, algorithms, etc. (collectively referred to as "elements"). Such elements may be implemented using electronic hardware, computer software, or any combination thereof. Whether such elements are implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system.

For example, an element, or any portion of an element, or any combination of elements, may be implemented as a "processing system" that includes one or more processors. Examples of processors include microprocessors, microcontrollers, graphics Processing Units (GPUs), central Processing Units (CPUs), application processors, digital Signal Processors (DSPs), reduced Instruction Set Computing (RISC) processors, system on a chip (SoC), baseband processors, field Programmable Gate Arrays (FPGAs), programmable Logic Devices (PLDs), state machines, gate logic, discrete hardware circuits, and other suitable hardware configured to perform the various functions described throughout this disclosure. One or more processors in the processing system may execute the software. Software should be construed broadly to mean instructions, instruction sets, code segments, program code, programs, subroutines, software components, applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, and the like, whether referred to as software, firmware, middleware, microcode, hardware description language, or other names.

Accordingly, in one or more example embodiments, the described functionality may be implemented in hardware, software, or any combination thereof. If implemented in software, the functions may be stored or encoded on a computer-readable medium as one or more instructions or code. Computer readable media includes computer storage media. A storage media may be any available media that can be accessed by a computer. By way of example, and not limitation, such computer-readable media can comprise Random Access Memory (RAM), read-only memory (ROM), electrically Erasable Programmable ROM (EEPROM), optical disk storage, magnetic disk storage, other magnetic storage devices, combinations of these types of computer-readable media, or any other medium that can be used to store computer-executable code in the form of instructions or data structures that can be accessed by a computer.

Although aspects and implementations are described in this application by way of illustration of some examples, those skilled in the art will appreciate that additional implementations and uses are possible in many other arrangements and scenarios. The innovations described herein may be implemented across many different platform types, devices, systems, shapes, sizes, and packaging arrangements. For example, implementations and/or uses may be produced via integrated chip implementations and other non-module component based devices (e.g., end user devices, vehicles, communication devices, computing devices, industrial equipment, retail/purchasing devices, medical devices, artificial Intelligence (AI) enabled devices, etc.). While some examples may or may not be specifically directed to use cases or applications, applicability of the various types of innovations described may occur. Implementations may range from chip-level or modular components to non-modular, non-chip-level implementations, and further to aggregate, distributed, or Original Equipment Manufacturer (OEM) devices or systems incorporating one or more aspects of the described innovations. In some practical environments, devices incorporating the described aspects and features may also include additional components and features for implementing and practicing the claimed and described aspects. For example, the transmission and reception of wireless signals necessarily includes a number of components for analog and digital purposes (e.g., hardware components including antennas, RF chains, power amplifiers, modulators, buffers, processors, interleavers, adders/accumulators, etc.). The innovations described herein are intended to be practiced in a variety of devices, chip-level components, systems, distributed arrangements, aggregated or disaggregated components, end-user devices, etc., of different sizes, shapes, and configurations.

Fig. 1 is a diagram 100 illustrating an example of a wireless communication system and access network. A wireless communication system, also referred to as a Wireless Wide Area Network (WWAN), includes a base station 102, a UE 104, an Evolved Packet Core (EPC) 160, and another core network 190 (e.g., a 5G core (5 GC)). Base station 102 may include a macrocell (high power cellular base station) and/or a small cell (low power cellular base station). The macrocell includes a base station. Small cells include femto cells, pico cells, and micro cells.

A base station 102 configured for 4G LTE, which is collectively referred to as an evolved Universal Mobile Telecommunications System (UMTS) terrestrial radio access network (E-UTRAN), may interface with EPC 160 through a first backhaul link 132 (e.g., an S1 interface). A base station 102 configured for 5G NR, which is collectively referred to as a next generation RAN (NG-RAN), may interface with a core network 190 through a second backhaul link 184. Among other functions, the base station 102 may perform one or more of the following functions: transmission of user data, radio channel encryption and decryption, integrity protection, header compression, mobile control functions (e.g., handover, dual connectivity), inter-cell interference coordination, connection establishment and release, load balancing, distribution of non-access stratum (NAS) messages, NAS node selection, synchronization, radio Access Network (RAN) sharing, multimedia Broadcast Multicast Services (MBMS), subscriber and equipment tracking, RAN Information Management (RIM), paging, positioning, and delivery of alert messages. The base stations 102 may communicate with each other directly or indirectly (e.g., through the EPC 160 or the core network 190) over a third backhaul link 134 (e.g., an X2 interface). The first backhaul link 132, the second backhaul link 184, and the third backhaul link 134 may be wired or wireless.

The base station 102 may communicate wirelessly with the UE 104. Each of the base stations 102 may provide communication coverage for a respective geographic coverage area 110. There may be overlapping geographic coverage areas 110. For example, the small cell 102 'may have a coverage area 110' that overlaps with the coverage area 110 of one or more macro base stations 102. A network comprising both small cells and macro cells may be referred to as a heterogeneous network. The heterogeneous network may also include home evolved node B (eNB) (HeNB), which may provide services to a restricted group known as a Closed Subscriber Group (CSG). The communication link 120 between the base station 102 and the UE 104 may include Uplink (UL) (also referred to as reverse link) transmissions from the UE 104 to the base station 102 and/or Downlink (DL) (also referred to as forward link) transmissions from the base station 102 to the UE 104. Communication link 120 may use multiple-input multiple-output (MIMO) antenna techniques including spatial multiplexing, beamforming, and/or transmit diversity. The communication link may experience one or more carriers. For each carrier allocated in a carrier aggregation up to yxmhz (x component carriers) in total for transmission in each direction, the base station 102/UE 104 may use a spectrum up to Y MHz (e.g., 5MHz, 10MHz, 15MHz, 20MHz, 100MHz, 400MHz, etc.) bandwidth. The carriers may or may not be adjacent to each other. The allocation of carriers may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated for DL than UL). The component carriers may include a primary component carrier and one or more secondary component carriers. The primary component carrier may be referred to as a primary cell (PCell) and the secondary component carrier may be referred to as a secondary cell (SCell).

Some UEs 104 may communicate with each other using a device-to-device (D2D) communication link 158. The D2D communication link 158 may use the DL/UL WWAN spectrum. The D2D communication link 158 may use one or more sidelink channels, such as a Physical Sidelink Broadcast Channel (PSBCH), a Physical Sidelink Discovery Channel (PSDCH), a Physical Sidelink Shared Channel (PSSCH), and a Physical Sidelink Control Channel (PSCCH). D2D communication may be through a variety of wireless D2D communication systems such as, for example, wiMedia, bluetooth, zigBee, wi-Fi based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard, LTE, or NR.

The wireless communication system may also include a Wi-Fi Access Point (AP) 150 that communicates with Wi-Fi Stations (STAs) 152 via a communication link 154, e.g., in the 5GHz unlicensed spectrum or the like. When communicating in the unlicensed spectrum, STA 152/AP 150 may perform Clear Channel Assessment (CCA) prior to communication to determine whether a channel is available.

The small cell 102' may operate in licensed and/or unlicensed spectrum. When operating in unlicensed spectrum, the small cell 102' may employ NR and use the same unlicensed spectrum (e.g., 5GHz, etc.) as used by the Wi-Fi AP 150. Small cells 102' employing NRs in the unlicensed spectrum may improve access network coverage and/or increase access network capacity.

The electromagnetic spectrum is generally subdivided into various categories, bands, channels, etc., based on frequency/wavelength. In 5G NR, two initial operating bands have been identified as frequency range names FR1 (410 MHz-7.125 GHz) and FR2 (24.25 GHz-52.6 GHz). Although a portion of FR1 is greater than 6GHz, FR1 is commonly referred to as the (interchangeably) "sub-6 GHz" band in various documents and articles. With respect to FR2, a similar naming problem sometimes occurs, which is commonly (interchangeably) referred to in documents and articles as the "millimeter wave" band, although it differs from the Extremely High Frequency (EHF) band (30 GHz-300 GHz) identified by the International Telecommunications Union (ITU) as the "millimeter wave" band.

The frequency between FR1 and FR2 is commonly referred to as the mid-band frequency. Recent 5G NR studies have identified the operating band for these mid-band frequencies as frequency range designation FR3 (7.125 GHz-24.25 GHz). The frequency bands falling within FR3 may inherit FR1 characteristics and/or FR2 characteristics, and thus may effectively extend the characteristics of FR1 and/or FR2 to 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 bands have been identified as frequency range names FR4a or FR4-1 (52.6 GHz-71 GHz), FR4 (52.6 GHz-114.25 GHz) and FR5 (114.25 GHz-300 GHz). Each of these higher frequency bands falls within the EHF frequency band.

In view of the above, unless specifically stated otherwise, it is to be understood that, if used herein, the term "sub-6 GHz" or the like may broadly represent frequencies that may be less than 6GHz, may be within FR1, or may include mid-band frequencies. Furthermore, unless specifically stated otherwise, it should be understood that if the term "millimeter wave" or the like is used herein, it may be broadly meant to include mid-band frequencies, frequencies that may be within FR2, FR4-a or FR4-1 and/or FR5, or may be within the EHF band.

The base station 102, whether small cell 102' or a large cell (e.g., macro base station), may include and/or be referred to as an eNB, next generation node B (gNB ), or another type of base station. Some base stations, such as base station 180 (e.g., gNB), may operate in the traditional sub-6 GHz spectrum, in millimeter wave frequencies, and/or near millimeter wave frequencies to communicate with UE 104. When base station 180 operates in millimeter wave or near millimeter wave frequencies, base station 180 may be referred to as a millimeter wave base station. Base station 180 (e.g., a millimeter wave base station) may utilize beamforming 182 with UE 104 to compensate for path loss and short range. The base station 180 and the UE 104 may each include multiple antennas (e.g., antenna elements, antenna panels, and/or antenna arrays) to facilitate beamforming.

The base station 180 may transmit the beamformed signals to the UE 104 in one or more transmit directions 182'. The UE 104 may receive the beamformed signals from the base station 180 in one or more receive directions 182 ". The UE 104 may also transmit the beamformed signals in one or more transmit directions to the base station 180. The base station 180 may receive the beamformed signals from the UEs 104 in one or more receive directions. The base stations 180/UEs 104 may perform beam training to determine the best receive direction and transmit direction for each of the base stations 180/UEs 104. The transmission and reception directions of the base station 180 may be the same or different. The transmitting and receiving directions of the UE 104 may be the same or different.

EPC 160 may include a Mobility Management Entity (MME) 162, other MMEs 164, a serving gateway 166, a Multimedia Broadcast Multicast Service (MBMS) gateway 168, a broadcast multicast service center (BM-SC) 170, and a Packet Data Network (PDN) gateway 172.MME 162 may communicate with a Home Subscriber Server (HSS) 174. The MME 162 is a control node that handles signaling between the UE 104 and the EPC 160. In general, MME 162 provides bearer and connection management. All user Internet Protocol (IP) packets are transmitted through the serving gateway 166, which itself is connected to the PDN gateway 172. The PDN gateway 172 provides UE IP address allocation as well as other functions. The PDN gateway 172 and BM-SC 170 are connected to an IP service 176.IP services 176 may include the internet, intranets, IP Multimedia Subsystem (IMS), PS streaming services, and/or other IP services. The BM-SC 170 may provide functionality for MBMS user service provision and delivery. The BM-SC 170 may act as an entry point for content provider MBMS transmissions, may be used to authorize and initiate MBMS bearer services in a Public Land Mobile Network (PLMN), and may be used to schedule MBMS transmissions. The MBMS gateway 168 may be used to allocate MBMS traffic to base stations 102 belonging to a Multicast Broadcast Single Frequency Network (MBSFN) area broadcasting a particular service and may be responsible for session management (start/stop) and collecting eMBMS related charging information.

The core network 190 may include access and mobility management function (AMF) 192, other AMFs 193, session Management Function (SMF) 194, and User Plane Function (UPF) 195. The AMF 192 may communicate with a Unified Data Management (UDM) 196. The AMF 192 is a control node for handling signaling between the UE 104 and the core network 190. In general, AMF 192 provides QoS flows and session management. All user Internet Protocol (IP) packets are transmitted through UPF 195. The UPF 195 provides UE IP address assignment as well as other functions. The UPF 195 is connected to an IP service 197.IP services 197 may include internet, intranet, IP Multimedia Subsystem (IMS), packet Switched (PS) streaming (PSs) services, and/or other IP services.

A base station may include and/or be referred to as a gNB, a node B, eNB, an access point, a base station transceiver, a radio base station, a radio transceiver, a transceiver function, a Basic Service Set (BSS), an Extended Service Set (ESS), a Transmit Receive Point (TRP), or some other suitable terminology. The base station 102 provides an access point to the EPC 160 or core network 190 for the UE 104. Examples of UEs 104 include a cellular telephone, a smart phone, a Session Initiation Protocol (SIP) phone, a laptop, a Personal Digital Assistant (PDA), a satellite radio, a global positioning system, a multimedia device, a video device, a digital audio player (e.g., MP3 player), a camera, a game console, a tablet, a smart device, a wearable device, a vehicle, an electricity meter, an air pump, a large or small kitchen appliance, a healthcare device, an implant, a sensor/actuator, a display, or any other similarly functioning device. Some of the UEs 104 may be referred to as IoT devices (e.g., parking meters, air pumps, toasters, vehicles, heart monitors, etc.). The UE 104 may also be referred to as a station, mobile station, subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, or some other suitable terminology. In some scenarios, the term UE may also apply to one or more companion devices, such as in a device cluster arrangement. One or more of these devices may access the network in common and/or individually. The network nodes may be implemented as base stations (i.e., aggregated base stations), disaggregated base stations, integrated Access and Backhaul (IAB) nodes, relay nodes, sidelink nodes, and the like. The network nodes may also be implemented as Central Units (CUs), distributed Units (DUs), radio Units (RUs), near real-time (near RT) RAN Intelligent Controllers (RIC), or non-real-time (non-RT) RIC in a decentralized base station architecture or decentralized RAN architecture. The network entity may be implemented as a base station (i.e., an aggregated base station), a disaggregated base station, an Integrated Access and Backhaul (IAB) node, a relay node, a sidelink node, and so on. Further, the network entity may be implemented as a Central Unit (CU), a Distributed Unit (DU), a Radio Unit (RU), a near real-time (near RT) RAN Intelligent Controller (RIC), or a non-real-time (non-RT) RIC in a decentralized base station architecture or decentralized RAN architecture. In some aspects, a network node may be referred to as a network entity.

Referring again to fig. 1, in some aspects, the UE 104 may include a receiving component 198 configured to store a history of use of one or more past network slices prior to sending the indication of the one or more past network slices. The receiving component 198 may also be configured to calculate a probability of use for one or more future network slices prior to sending the indication of the one or more future network slices. The receiving component 198 may also be configured to transmit at least one of an indication of one or more future network slices corresponding to network slices for potential future use by the UE, an indication of one or more current network slices corresponding to network slices currently used by the UE, or an indication of one or more past network slices corresponding to network slices previously used by the UE to at least one of a network node (e.g., a base station) or a network entity. The receiving component 198 may also be configured to receive a response from the network entity to at least one of the indication of the one or more future network slices, the indication of the one or more current network slices, or the indication of the one or more past network slices. The receiving component 198 may also be configured to send a message associated with at least one of the one or more future network slices, the one or more current network slices, or the one or more past network slices to the network node (e.g., base station) based on the response.

Referring again to fig. 1, in some aspects, AMF 192 may comprise a transmission component 191 configured to receive from at least one User Equipment (UE) at least one of an indication of one or more future network slices corresponding to network slices for potential future use by the at least one UE, an indication of one or more current network slices corresponding to network slices currently used by the UE, or an indication of one or more past network slices corresponding to network slices previously used by the at least one UE. The transmission component 191 may be further configured to send a response to the at least one UE to at least one of the indication of the one or more future network slices, the indication of the one or more current network slices, or the indication of the one or more past network slices. The transmission component 191 may be further configured to transmit Network Slice Selection Assistance Information (NSSAI) to at least one network node (e.g., base station) based on at least one of the indication of the one or more future network slices, the indication of the one or more current network slices, or the indication of the one or more past network slices. The transmission component 191 may also be configured to configure a network slice structure based on at least one of the one or more future network slices, the one or more current network slices, or the one or more past network slices.

Referring again to fig. 1, in some aspects, a base station 180 (e.g., a network node) may include a transmission component 199 configured to receive from at least one User Equipment (UE) at least one of an indication of one or more future network slices corresponding to network slices for potential future use by the at least one UE, an indication of one or more current network slices corresponding to network slices currently used by the UE, or an indication of one or more past network slices corresponding to network slices previously used by the at least one UE. The transmission component 199 may also be configured to receive a message associated with at least one of the one or more future network slices, the one or more current network slices, or the one or more past network slices from the at least one UE. The transmission component 199 may be further configured to transmit Network Slice Selection Assistance Information (NSSAI) to at least one other network node (e.g., base station) based on at least one of the indication of the one or more future network slices, the indication of the one or more current network slices, or the indication of the one or more past network slices. The transmission component 199 may also be configured for at least one of a handoff procedure, a redirection procedure, a serving cell change, or a cell addition of a Carrier Aggregation (CA), the configuration being based on at least one of the one or more future network slices, the one or more current network slices, or the one or more past network slices.

Although the following description may focus on 5G NR, the concepts described herein may be applicable to other similar fields, such as LTE, LTE-A, CDMA, GSM, and other wireless technologies.

Fig. 2A is a diagram 200 showing an example of a first subframe within a 5G NR frame structure. Fig. 2B is a diagram 230 showing an example of DL channels within a 5G NR subframe. Fig. 2C is a diagram 250 showing an example of a second subframe within a 5G NR frame structure. Fig. 2D is a diagram 280 illustrating an example of UL channels within a 5G NR subframe. The 5G NR frame structure may be frequency division multiplexed (FDD) in which subframes within a set of subcarriers are dedicated to either DL or UL for a particular set of subcarriers (carrier system bandwidth) or time division multiplexed (TDD) in which subframes within a set of subcarriers are dedicated to both DL and UL for a particular set of subcarriers (carrier system bandwidth). In the example provided in fig. 2A, 2C, the 5G NR frame structure is assumed to be TDD, where subframe 4 is configured with slot format 28 (most of which are DL), where D is DL, U is UL, and F is flexible for use between DL/UL, and subframe 3 is configured with slot format 1 (all of which are UL). Although subframes 3, 4 are shown with slot formats 1, 28, respectively, any particular subframe may be configured with any of the various available slot formats 0-61. The slot formats 0, 1 are DL, UL, respectively. Other slot formats 2-61 include a mix of DL, UL and flexible symbols. The UE is configured with a slot format (dynamically configured by DL Control Information (DCI) or semi-statically/statically controlled by Radio Resource Control (RRC) signaling) through a received Slot Format Indicator (SFI). Note that the following description also applies to a 5G NR frame structure as TDD.

Fig. 2A-2D illustrate frame structures, and aspects of the present disclosure may be applicable to other wireless communication technologies that may have different frame structures and/or different channels. One frame (10 ms) may be divided into 10 equally sized subframes (1 ms). Each subframe may include one or more slots. A subframe may also include a minislot, which may include 7, 4, or 2 symbols. Each slot may include 14 or 12 symbols depending on whether the Cyclic Prefix (CP) is normal or extended. For a normal CP, each slot may include 14 symbols, and for an extended CP, each slot may include 12 symbols. The symbols on DL may be CP Orthogonal Frequency Division Multiplexing (OFDM) (CP-OFDM) symbols. The symbols on the UL may be CP-OFDM symbols (for high throughput scenarios) or Discrete Fourier Transform (DFT) -spread OFDM (DFT-s-OFDM) symbols (also known as single carrier frequency division multiple access (SC-FDMA) symbols) (for power limited scenarios; limited to single stream transmission). The number of slots within a subframe is based on CP and parameter set (numerology). The parameter set defines the subcarrier spacing (SCS) and effectively defines the symbol length/duration, which is equal to 1/SCS.

For a normal CP (14 symbols/slot), different parameter sets μ0 to 4 allow 1, 2, 4, 8 and 16 slots, respectively, per subframe. For an extended CP, parameter set 2 allows 4 slots per subframe. Accordingly, for normal CP and parameter set μ, there are 14 symbols/slot and 2 ^μ Each slot/subframe. The subcarrier spacing may be equal to 2 ^μ *15kHz, where μ is the parameter set 0 to 4. Thus, the subcarrier spacing for parameter set μ=0 is 15kHz and the subcarrier spacing for parameter set μ=4 is 240kHz. The symbol length/duration is inversely related to the subcarrier spacing. Fig. 2A-2D provide examples of a normal CP of 14 symbols per slot and a parameter set μ=2 of 4 slots per subframe. The slot duration is 0.25ms, the subcarrier spacing is 60kHz, and the symbol duration is approximately 16.67 mus. Within the frame set, there may be one or more different bandwidth portions (BWP) of the frequency division multiplexing (see fig. 2B). Each BWP may have a specific parameter set and CP (normal or extended).

The resource grid may be used to represent a frame structure. Each slot includes Resource Blocks (RBs) (also referred to as Physical RBs (PRBs)) that extend for 12 consecutive subcarriers. The resource grid is divided into a plurality of Resource Elements (REs). The number of bits carried by each RE depends on the modulation scheme.

As illustrated in fig. 2A, some of the REs carry a reference (pilot) signal (RS) for the UE. The RS may include a demodulation RS (DM-RS) (indicated as R for one particular configuration, but other DM-RS configurations are possible) and a channel state information reference signal (CSI-RS) for channel estimation at the UE. The RSs may also include beam measurement RSs (BRSs), beam Refinement RSs (BRRSs), and phase tracking RSs (PT-RSs).

Fig. 2B illustrates an example of various DL channels within a subframe of a frame. A Physical Downlink Control Channel (PDCCH) carries DCI within one or more Control Channel Elements (CCEs) (e.g., 1, 2, 4, 8, or 16 CCEs), each CCE including six RE groups (REGs), each REG including 12 consecutive REs in one OFDM symbol of an RB. The PDCCH within one BWP may be referred to as a control resource set (CORESET). The UE is configured to monitor PDCCH candidates in a PDCCH search space (e.g., common search space, UE-specific search space) during a PDCCH monitoring occasion on CORESET, where the PDCCH candidates have different DCI formats and different aggregation levels. Additional BWP may be located at higher and/or lower frequencies over the channel bandwidth. The Primary Synchronization Signal (PSS) may be within symbol 2 of a particular subframe of a frame. PSS is used by UE 104 to determine subframe/symbol timing and physical layer identity. The Secondary Synchronization Signal (SSS) may be within symbol 4 of a particular subframe of a frame. SSS is used by the UE to determine the physical layer cell identity group number and radio frame timing. Based on the physical layer identity and the physical layer cell identity group number, the UE may determine a Physical Cell Identifier (PCI). Based on the PCI, the UE can determine the location of the DM-RS. A Physical Broadcast Channel (PBCH) carrying a Master Information Block (MIB) may be logically grouped with PSS and SSS to form a Synchronization Signal (SS)/PBCH block (also referred to as an SS block (SSB)). The MIB provides the number of RBs in the system bandwidth and a System Frame Number (SFN). The Physical Downlink Shared Channel (PDSCH) carries user data, broadcast system information (e.g., system Information Blocks (SIBs)) not transmitted over the PBCH, and paging messages.

As shown in fig. 2C, some REs carry DM-RS (denoted R for one particular configuration, but other DM-RS configurations are possible) for channel estimation at the base station. The UE may transmit DM-RS of a Physical Uplink Control Channel (PUCCH) and DM-RS of a Physical Uplink Shared Channel (PUSCH). PUSCH DM-RS may be transmitted in the first one or two symbols of PUSCH. The PUCCH DM-RS may be transmitted in different configurations according to whether the short PUCCH or the long PUCCH is transmitted and according to a specific PUCCH format used. The UE may transmit a Sounding Reference Signal (SRS). The SRS may be transmitted in the last symbol of the subframe. The SRS may have a comb structure, and the UE may transmit the SRS on one of the comb structures. The SRS may be used by the base station for channel quality estimation to enable frequency dependent scheduling of the UL.

Fig. 2D illustrates an example of various UL channels within a subframe of a frame. The PUCCH may be located as indicated in one configuration. The PUCCH carries Uplink Control Information (UCI) such as a scheduling request, a Channel Quality Indicator (CQI), a Precoding Matrix Indicator (PMI), a Rank Indicator (RI), and hybrid automatic repeat request (HARQ) Acknowledgement (ACK) (HARQ-ACK) feedback (i.e., one or more HARQ ACK bits indicating one or more ACKs and/or Negative ACKs (NACKs)). PUSCH carries data and may additionally be used to carry Buffer Status Reports (BSR), power Headroom Reports (PHR), and/or UCI.

Fig. 3 is a block diagram of a base station 310 in an access network in communication with a UE 350. In DL, IP packets from EPC 160 may be provided to controller/processor 375. Controller/processor 375 implements layer 3 and layer 2 functionality. Layer 3 includes a Radio Resource Control (RRC) layer, and layer 2 includes a Service Data Adaptation Protocol (SDAP) layer, a Packet Data Convergence Protocol (PDCP) layer, a Radio Link Control (RLC) layer, and a Medium Access Control (MAC) layer. Controller/processor 375 provides: RRC layer functionality associated with broadcast of system information (e.g., MIB, SIB), RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), inter-Radio Access Technology (RAT) mobility, and measurement configuration for UE measurement reporting; PDCP layer functionality associated with header compression/decompression, security (ciphering, integrity protection, integrity verification), and handover support functionality; RLC layer functionality associated with upper layer Packet Data Unit (PDU) delivery, error correction by ARQ, concatenation of RLC Service Data Units (SDUs), segmentation and reassembly, re-segmentation of RLC data PDUs, and re-ordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto Transport Blocks (TBs), de-multiplexing of MAC SDUs from TBs, scheduling information reporting, error correction by HARQ, priority handling and logical channel prioritization.

Transmit (TX) processor 316 and Receive (RX) processor 370 implement layer 1 functionality associated with a variety of signal processing functions. Layer 1, which includes the Physical (PHY) layer, may include error detection on the transport channel, forward Error Correction (FEC) decoding/decoding of the transport channel, interleaving, rate matching, mapping onto the physical channel, modulation/demodulation of the physical channel, and MIMO antenna processing. TX processor 316 processes the mapping for the signal constellation diagram based on various modulation schemes (e.g., binary Phase Shift Keying (BPSK), quadrature Phase Shift Keying (QPSK), M-phase shift keying (M-PSK), M-quadrature amplitude modulation (M-QAM)). The decoded and modulated symbols may then be split into parallel streams. Each stream may then be mapped to OFDM subcarriers, multiplexed with a reference signal (e.g., pilot) in the time and/or frequency domain, and then combined together using an Inverse Fast Fourier Transform (IFFT) to generate a physical channel for carrying the time-domain OFDM symbol stream. The OFDM stream is spatially precoded to produce a plurality of spatial streams. The channel estimates from channel estimator 374 may be used to determine coding and modulation schemes, as well as for spatial processing. The channel estimate may be derived from reference signals and/or channel condition feedback transmitted by the UE 350. Each spatial stream may then be provided to a different antenna 320 via a separate transmitter 318 TX. Each transmitter 318TX may modulate a Radio Frequency (RF) carrier with a respective spatial stream for transmission.

At the UE 350, each receiver 354RX receives a signal via its respective antenna 352. Each receiver 354RX recovers information modulated onto an RF carrier and provides the information to the Receive (RX) processor 356.TX processor 368 and RX processor 356 implement layer 1 functionality associated with various signal processing functionalities. RX processor 356 can perform spatial processing on the information to recover any spatial streams for UE 350. If multiple spatial streams are destined for the UE 350, they may be combined into a single OFDM symbol stream by an RX processor 356. RX processor 356 then converts the OFDM symbol stream from the time domain to the frequency domain using a Fast Fourier Transform (FFT). The frequency domain signal comprises a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier, as well as the reference signal, are recovered and demodulated by determining the signal constellation points most likely to be transmitted by the base station 310. These soft decisions may be based on channel estimates computed by channel estimator 358. The soft decisions are then decoded and deinterleaved to recover the data and control signals that were originally transmitted by the base station 310 on the physical channel. The data and control signals are then provided to a controller/processor 359 that implements layer 3 and layer 2 functionality.

The controller/processor 359 can be associated with a memory 360 that stores program codes and data. Memory 360 may be referred to as a computer-readable medium. In the UL, controller/processor 359 provides demultiplexing between transport and logical channels, packet reassembly, deciphering, header decompression, and control signal processing to recover IP packets from EPC 160. The controller/processor 359 is also responsible for error detection using an ACK and/or NACK protocol to support HARQ operations.

Similar to the functionality described in connection with DL transmissions by the base station 310, the controller/processor 359 provides: RRC layer functionality associated with system information (e.g., MIB, SIB) acquisition, RRC connection, and measurement reporting; PDCP layer functionality associated with header compression/decompression and security (ciphering, integrity protection, integrity verification); RLC layer functions associated with upper layer PDU delivery, error correction by ARQ, concatenation, segmentation and reassembly of RLC SDUs, re-segmentation of RLC data PDUs and re-ordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto TBs, demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction by HARQ, priority handling and logical channel prioritization.

Channel estimates derived by channel estimator 358 from reference signals or feedback transmitted by base station 310 may be used by TX processor 368 to select appropriate coding and modulation schemes and to facilitate spatial processing. The spatial streams generated by TX processor 368 may be provided to different antennas 352 via separate Transmitters (TX) 354. Each Transmitter (TX) 354 may modulate an RF carrier with a corresponding spatial stream for transmission.

UL transmissions are processed at the base station 310 in a manner similar to that described in connection with the receiver function at the UE 350. Each Receiver (RX) 318 receives a signal via its respective antenna 320. Each Receiver (RX) 318 recovers information modulated onto an RF carrier and provides the information to the RX processor 370.

The controller/processor 375 may be associated with a memory 376 that stores program codes and data. Memory 376 may be referred to as a computer-readable medium. In the UL, controller/processor 375 provides demultiplexing between transport and logical channels, packet reassembly, deciphering, header decompression, control signal processing to recover IP packets from UE 350. IP packets from controller/processor 375 may be provided to EPC 160. Controller/processor 375 is also responsible for error detection using ACK and/or NACK protocols to support HARQ operations.

At least one of TX processor 368, RX processor 356, and controller/processor 359 may be configured to perform aspects in conjunction with 198 of fig. 1.

At least one of TX processor 316, RX processor 370, and controller/processor 375 may be configured to perform the aspects in conjunction with 199 of fig. 1.

At least one of TX processor 316, RX processor 370, and controller/processor 375 may be configured to perform the aspects in conjunction with 191 of fig. 1.

Some aspects of wireless communications, such as the 5G system (5 GS), may take advantage of network slicing features. Network slicing is a network architecture that enables multiplexing of independent logical networks over a physical network infrastructure. For example, each network slice may be an isolated end-to-end network that may meet the specifications requested by the application. Network slicing may provide means for User Equipment (UE) and networks (e.g., network entities and/or network nodes) to negotiate a particular type of service that may be part of an expected set of specifications for the UE and network. In addition, the network slices may differ for different types of supported features and/or network function optimizations. For example, a network operator may deploy multiple network slice instances that deliver the same feature for different groups of UEs, e.g., because the network slice instances may deliver a different promised service and/or because they may be dedicated to a certain customer. The network slice framework may include a generic architecture that maps common elements into a generic unified framework. For example, the network slice architecture may correspond to two main blocks, e.g., one block dedicated to actual slice implementation and another block dedicated to slice management and configuration.

Fig. 4 shows a diagram 400 of one example of a network slice framework. More specifically, diagram 400 is an example network slice framework including a network slice controller 410, a service layer 420, a network function layer 430, and an infrastructure layer 440. As shown in fig. 4, the network slice controller 410 includes an orchestrator/operator 412, the service layer 420 includes a virtual mobile operator 422 and a third party service provider 424, the network function layer 430 includes network functions 432 and network operations 434, and the infrastructure layer 440 includes a Radio Access Network (RAN) 442, a transport network 444, and a Core Network (CN) 446.

As indicated in fig. 4, the network slice framework in diagram 400 includes one aspect dedicated to actual slice implementation (e.g., service layer 420, network function layer 430, and infrastructure layer 440) and another aspect dedicated to slice management and configuration (e.g., network slice controller 410). The service layer 420 may interface directly with network business entities (e.g., virtual mobile operators 422 and third party service providers 424) that share the underlying physical network and provide an indication of the service specifications. The network function layer 430 may be responsible for creating each network slice from service instance requests from upper layers and consists of a set of network functions/operations (e.g., network function 432 and network operation 434). The infrastructure layer 440 may represent the actual physical network topology (e.g., RAN 442, transport network 444, and CN 446) on which each network slice is multiplexed, and provide physical network resources to host several network functions that make up each slice. In addition, the network slice controller 410 may include a network orchestrator/operator 412 that interfaces with the various functions performed by each layer to manage each slice request.

In some aspects, a single UE may be served by one or more network slice instances simultaneously via AN access network, such as a 5G access network (5G-AN). A network entity serving the UE, such as an access and mobility management function (AMF), may belong to each of the network slice instances serving the UE. That is, the AMF instance may be common to network slice instances serving the UE. A Protocol Data Unit (PDU) session may belong to one particular network slice instance of each network, e.g., public Land Mobile Network (PLMN). Further, different network slice instances may not share a PDU session, but different slices may have slice-specific Protocol Data Unit (PDU) sessions using the same Data Network Name (DNN).

In some examples, the UE may be configured by a type of PLMN, such as a Home PLMN (HPLMN), with network slice selection assistance information (nsai) configured per PLMN. Further, the configured nsais may be PLMN-specific and the HPLMN may indicate what PLMNs each configured nsai applies to, including whether the configured nsais apply to all PLMNs. That is, the configured nsai may convey the same information regardless of the PLMN the UE is accessing, e.g., as is possible for nsais that include standardized single nsais (S-nsais).

In addition, when providing a requested NSSAI to the network at registration, a UE in a particular PLMN may use the S-NSSAI of the configured NSSAI (if any) belonging to that particular PLMN. Upon successful completion of the registration procedure for the UE, the UE may obtain the allowed nsais for the PLMN from the AMF. The allowed NSSAIs may include one or more S-NSSAIs. Furthermore, for this PLMN, the allowed nsais may be prioritized over the configured nsais. The UE may use the S-nsai of the allowed nsais that correspond to the network slice used to serve the subsequent network slice selection related procedure in the PLMN. This may be referred to as an accepted NSSAI. Furthermore, for each PLMN, the UE may store the configured nsais and allowed nsais (if any). When the UE receives an allowed nsai for a PLMN, the UE may store the allowed nsai and overwrite any previously stored allowed nsai for the PLMN.

Fig. 5 shows a diagram 500 of one example of a registration process. More specifically, diagram 500 is an example registration process utilizing Network Slice Selection Assistance Information (NSSAI). As shown in fig. 5, diagram 500 includes a UE 502, a cell 504, and a cell 506. As shown in fig. 5, cell 504 may send a registration accept message, e.g., registration accept 510, including allowed nsais and rejected nsais to UE 502. For example, allowed NSSAI may correspond to the value {1,2,3,4,5}, while rejected NSSAI may correspond to the value {6}. In addition, UE 502 may send a registration request message, such as registration request 520, including the requested NSSAI to cell 506. For example, the requested NSSAI may correspond to the values {1,2,3,4,5,6,7,8,9}, and the configured NSSAI may correspond to the values {1,2,3,4,5,6,7,8,9,10}.

Fig. 6 shows a diagram 600 of one example of a registration process. More specifically, diagram 600 is an example non-access stratum (NAS) registration procedure that utilizes Network Slice Selection Assistance Information (NSSAI). As shown in fig. 6, diagram 600 includes a UE 602, a Base Station (BS) 604 (e.g., a network node), and an AMF 606 (e.g., a network entity). As shown in fig. 6, the base station 604 may send a setup request message 610 (including a list of S-nsais per Tracking Area Identity (TAI)) to the AMF 606, and the AMF 606 may send a setup response message 620 to the base station 604. The UE 602 may send an RRC message 5 (Msg 5) including an AS requested nsai and a NAS registration request message (request nsai) to the base station 604 (e.g., RRC Msg5 630). The base station 604 may then send an initial UE message 640 (including a NAS registration request) to the AMF 606. The AMF 606 may send an initial UE context setup request 650 (including allowed nsai, NAS registration accept (allowed nsai, rejected nsai)) to the base station 604. Next, a security mode command procedure 660 may be performed between the UE 602 and the base station 604. The base station 604 may then send an RRC reconfiguration message 670 (including a NAS registration accept message) to the UE 602. The UE context associated with UE 602 may include configured nsais, requested nsais, allowed nsais, and rejected nsais. The UE context associated with the base station 604 may include the allowed nsais and the nsais of the active PDU session. Further, the UE context associated with AMF 606 may include subscribed nsais, requested nsais, allowed nsais, and rejected nsais.

As indicated in fig. 5 and 6, when a UE registers or participates in a registration process, it may send a request for a network slice via the requested nsai. However, the UE may want to use other network slices (i.e., unsolicited network slices) in the future. There may also be network slices that are often used by the UE, but these particular network slices may not be needed during the registration process. In this case, it may be beneficial for the network to determine this information, which may be used in mobility decisions and other network-based actions. That is, it may be beneficial for the UE/network to determine network slices that have been used in the past and network slices that may be used in the future. For example, it may be beneficial for the UE/network to determine network slices that have been used in the past but may not be needed in the future, or vice versa. It may also be beneficial to exchange such information between the UE and a network entity (e.g., AMF) or network node (e.g., base station).

Aspects of the present disclosure may determine or identify network slices that have been used in the past and network slices that may be used in the future. For example, aspects of the present disclosure may allow the UE/network to use this information in mobility decisions and other network-based actions. Additionally, aspects of the disclosure may allow the UE/network to determine network slices that have been used in the past but may not be needed in the future, or vice versa. Aspects of the disclosure may also exchange such information between the UE and a network entity (e.g., AMF) or a network node (e.g., base station). For example, the UE may send an indication of a future network slice, an indication of a current network slice, and/or an indication of a past network slice to a network entity (e.g., AMF) or a network node (e.g., base station).

In some examples, aspects of the disclosure may allow a UE to signal one or more network slices that may be used in the future (i.e., future network slices), one or more network slices currently being used (i.e., current network slices), and/or one or more network slices previously used in the past (i.e., past network slices). The signaling may be performed by an indication of a future network slice, an indication of a current network slice, and/or an indication of a past network slice. Additionally, future network slices, current network slices, and/or past network slices may be signaled in a separate list than the requested NSSAI. For example, the list that is signaled alone may be referred to as a wish list nsai (wish list nsai) or an updated requested nsai. Furthermore, future, current, and/or past network slices may be signaled in the NSSAI of the request along with the assigned probabilities. For example, future network slices may be signaled for future use along with the assigned probabilities (e.g., a value of 1.0 may correspond to immediate use of the network slice). Furthermore, the list may be signaled for each Public Land Mobile Network (PLMN).

In some aspects, the UE may signal future network slices, current network slices, and/or past network slices to a network entity (e.g., AMF) and/or a network node (e.g., base station or gNB) in an RRC message (e.g., RRC complete message). For example, the UE may signal a registration request and/or a service request to the AMF. Also, the UE may indicate a probability of use of future network slices and/or a history of use of past network slices. For example, the probability of use of a future network slice may be a value between 0 and 100, where 100 means that the likelihood of future use is great, 0 means that future use is not possible, or a fraction between 0 and 1. The history of past network slice use may be the number of times a network slice was used in a given past duration. For example, the history of past network slices' use may include how many times and/or how long the past network slices were utilized in the last X hours. The history of past network slice usage may include numbers between 0 and 100, where 100 means a large number of uses in the past and 0 means no uses in the past. Further, a weight factor and/or a priority index may be appended to each of the past network slices, each of the current network slices, and/or each of the future network slices. The weighting factors and/or priority index may reflect the relative importance of each of the past, current, and/or future network slices. For example, the weighting factors and/or priority index may be a function of quality of service (QoS).

After receiving an indication of a future/current/past network slice, the network may respond to the UE. The response from the network entity may be an grant, a rejection, an Acknowledgement (ACK) or a Negative ACK (NACK). Further, the indication of future/current/past network slices may correspond to a list associated with Network Slice Selection Assistance Information (NSSAI), such as an updated requested NSSAI or a wish list NSSAI. As such, the response from the network entity may be an acknowledgement of the willingness to single nsai. The nsai list may be a separate list other than the configured nsai. For example, the new list may be referred to as a granted NSSAI. Likewise, the NSSAI granted may be a subset or superset of the wish-to-single NSSAI.

The network entity (e.g., AMF) may send the granted nsai and/or the willingness-to-single nsai to a network node (e.g., serving base station or serving gNB). In addition, the list may be updated per UE-triggered signaling or per network decision. In some examples, the network node (e.g., base station) may save the list in a UE context that includes an RRC deactivated state. Further, a network node (e.g., a base station) may send NSSAI, e.g., granted NSSAI and/or willing to single NSSAI, to another network node (e.g., a base station or gNB). During the handoff procedure, a network node (e.g., base station) may send NSSAIs, such as granted NSSAIs and/or willingness to single NSSAIs. Also, during context acquisition for the recovery or re-establishment procedure, the network node (e.g., base station) may send NSSAIs, such as granted NSSAIs and/or willingness to single NSSAIs.

In addition, the UE may send a message or RRC message to a network node (e.g., a base station). The RRC message may be UE Assistance Information (UAI), an RRC complete message, or a new RRC message. For example, a message sent to a network node (e.g., a base station) may include the access probability of a rejected network slice. The message sent to the network node (e.g., base station) may also include a list of network slices (e.g., with or without probabilities) that the UE may use in the near future. Also, as described above, messages sent to a network node (e.g., base station) may include a history of past network slices.

A network entity (e.g., AMF) or a network node (e.g., base station) may use information received from a UE to make Radio Resource Management (RRM) decisions. For example, a network node (e.g., a base station) may make several decisions, such as decisions of mobility, offloading, serving cell change, or addition. Further, a network entity (e.g., AMF) may decide or determine a particular Radio Access Technology (RAT)/frequency selection priority (RFSP) index.

Aspects of the disclosure may also include network entity or AMF centric solutions. For example, a network entity or AMF may collect network slice information and/or usage statistics from another network entity or Session Management Function (SMF). The network entity or AMF may send such information to one or more network nodes (e.g., base stations). Further, the network entity or AMF may send this information to a network data analysis function (NWDAF). In some cases, the NWDAF may provide the service AMF with the expected probability of use of the network slice. The AMF may then send the expected probability of use of the network slice to a Radio Access Network (RAN).

Fig. 7 is a diagram 700 illustrating exemplary communications between a UE 702, a network node 704 (e.g., a base station), and a network entity 706 (e.g., an AMF).

At 710, the UE 702 may store a history of use of the one or more past network slices before sending the indication of the one or more past network slices.

At 712, the UE 702 may calculate a probability of use of the one or more future network slices before sending the indication of the one or more future network slices.

At 720, the UE 702 may send at least one of an indication of one or more future network slices corresponding to network slices for potential future use by the UE, an indication of one or more current network slices corresponding to network slices currently used by the UE, or an indication of one or more past network slices corresponding to network slices previously used by the UE to at least one of a network node (e.g., a base station) or a network entity.

In some aspects, the indication of the one or more future network slices may include at least one of: the probability of use of the one or more future network slices, the weighting factor of the one or more future network slices, or the priority index of the one or more future network slices. The indication of the one or more current network slices may include at least one of: the weighting factor of the one or more current network slices or the priority index of the one or more current network slices. The indication of the one or more past network slices may include a history of use of the one or more past network slices. The history of use of the one or more past network slices may include at least one of: the previous usage of the one or more past network slices, the weighting factor of the one or more past network slices, or the priority index of the one or more past network slices over the duration.

Additionally, the indication of the one or more future network slices may correspond to a list associated with network slice selection assistance information (nsaai). The list associated with the nsai may correspond to the updated requested nsai or a wish list for the nsai. The list associated with the NSSAI corresponds to an extension of the requested NSSAI or an adjustment of the requested NSSAI. The one or more future network slices are associated with a slice priority, the one or more current network slices are associated with the slice priority, and the one or more past network slices are associated with the slice priority. The network entity may be an access and mobility management function (AMF), a Session Management Function (SMF) or a network data analysis function (NWDAF).

At 722, the network node 704 (e.g., a base station) may receive at least one of an indication of one or more future network slices, an indication of one or more current network slices, or an indication of one or more past network slices, from at least one UE, the one or more future network slices corresponding to network slices for potential future use by the at least one UE, the one or more current network slices corresponding to network slices currently used by the UE, the one or more past network slices corresponding to network slices previously used by the at least one UE.

At 724, the network entity 706 (e.g., AMF) may receive at least one of an indication of one or more future network slices, an indication of one or more current network slices, or an indication of one or more past network slices, from at least one UE, the one or more future network slices corresponding to network slices for potential future use by the at least one UE, the one or more current network slices corresponding to network slices currently used by the UE, the one or more past network slices corresponding to network slices previously used by the at least one UE.

At 730, the network entity 706 may send a response to the at least one UE to at least one of the indication of the one or more future network slices, the indication of the one or more current network slices, or the indication of the one or more past network slices.

At 732, UE 702 may receive a response from the network entity to at least one of the indication of the one or more future network slices, the indication of the one or more current network slices, or the indication of the one or more past network slices. The response may be an grant, a rejection, an Acknowledgement (ACK) or a Negative ACK (NACK).

At 740, the UE 702 may send a message associated with at least one of the one or more future network slices, the one or more current network slices, or the one or more past network slices to the network node (e.g., base station) based on the response. The message may be a Radio Resource Control (RRC) message or a non-access stratum (NAS) message. The RRC message may be a UE Assistance Information (UAI) message, an RRC complete message, or a new RRC message.

At 742, the network node 704 can receive a message associated with at least one of the one or more future network slices, the one or more current network slices, or the one or more past network slices from the at least one UE.

At 752, the network node 704 may send Network Slice Selection Assistance Information (NSSAI) to at least one other network node (e.g., base station) based on at least one of the indication of the one or more future network slices, the indication of the one or more current network slices, or the indication of the one or more past network slices.

At 754, the network entity 706 may send Network Slice Selection Assistance Information (NSSAI) to at least one network node (e.g., base station) based on at least one of the indication of the one or more future network slices, the indication of the one or more current network slices, or the indication of the one or more past network slices.

At 760, the network entity 706 may configure a network slice structure based on at least one of the one or more future network slices, the one or more current network slices, or the one or more past network slices.

At 770, the network node 704 may be configured for at least one of a handover procedure, a redirection procedure, a serving cell change, or a cell addition of a Carrier Aggregation (CA), the configuration being based on at least one of the one or more future network slices, the one or more current network slices, or the one or more past network slices.

Fig. 8 is a flow chart 800 of a method of wireless communication. The method may be performed by a UE or a component of a UE (e.g., UE 104, 350, 502, 602, 702; apparatus 1402). The methods described herein may provide several benefits, such as improved communication signaling, resource utilization, and/or power savings.

At 806, the UE may send at least one of an indication of one or more future network slices corresponding to network slices for potential future use by the UE, an indication of one or more current network slices corresponding to network slices currently used by the UE, or an indication of one or more past network slices corresponding to network slices previously used by the UE to at least one of a network node (e.g., a base station) or a network entity, as described in connection with the examples in fig. 4-7. For example, UE 702 may send at least one of an indication of one or more future network slices corresponding to network slices for potential future use by the UE, an indication of one or more current network slices corresponding to network slices currently used by the UE, or an indication of one or more past network slices corresponding to network slices previously used by the UE to at least one of a network node (e.g., a base station) or a network entity, as described in connection with 720 in fig. 7. Further, 806 may be performed by determining component 1440 in fig. 14.

At 808, the UE may receive a response from the network entity to at least one of the indication of the one or more future network slices, the indication of the one or more current network slices, or the indication of the one or more past network slices, as described in connection with the examples in fig. 4-7. For example, UE 702 may receive a response from the network entity to at least one of the indication of the one or more future network slices, the indication of the one or more current network slices, or the indication of the one or more past network slices, as described in connection with 732 in fig. 7. Further, 808 may be performed by determining component 1440 in fig. 14. The response may be an grant, a rejection, an Acknowledgement (ACK) or a Negative ACK (NACK).

Fig. 9 is a flow chart 900 of a method of wireless communication. The method may be performed by a UE or a component of a UE (e.g., UE 104, 350, 502, 602, 702; apparatus 1402). The methods described herein may provide several benefits, such as improved communication signaling, resource utilization, and/or power savings.

At 902, the UE may store a history of use of the one or more past network slices prior to sending the indication of the one or more past network slices, as described in connection with the examples in fig. 4-7. For example, the UE 702 may store a history of use of one or more past network slices prior to sending an indication of the one or more past network slices, as described in connection with 710 in fig. 7. Further, 902 may be performed by the determining component 1440 of fig. 14.

At 904, the UE may calculate a probability of use of the one or more future network slices prior to sending the indication of the one or more future network slices, as described in connection with the examples in fig. 4-7. For example, the UE 702 may calculate the probability of use of the one or more future network slices before sending the indication of the one or more future network slices, as described in connection with 712 in fig. 7. Further, 904 may be performed by the determining component 1440 of fig. 14.

At 906, the UE may send at least one of an indication of one or more future network slices corresponding to network slices for potential future use by the UE, an indication of one or more current network slices corresponding to network slices currently used by the UE, or an indication of one or more past network slices corresponding to network slices previously used by the UE to at least one of a network node (e.g., a base station) or a network entity, as described in connection with the examples in fig. 4-7. For example, UE 702 may send at least one of an indication of one or more future network slices corresponding to network slices for potential future use by the UE, an indication of one or more current network slices corresponding to network slices currently used by the UE, or an indication of one or more past network slices corresponding to network slices previously used by the UE to at least one of a network node (e.g., a base station) or a network entity, as described in connection with 720 in fig. 7. Further, 906 may be performed by the determining component 1440 of fig. 14.

At 908, the UE may receive a response from the network entity to at least one of the indication of the one or more future network slices, the indication of the one or more current network slices, or the indication of the one or more past network slices, as described in connection with the examples in fig. 4-7. For example, UE 702 may receive a response from the network entity to at least one of the indication of the one or more future network slices, the indication of the one or more current network slices, or the indication of the one or more past network slices, as described in connection with 732 in fig. 7. Further, 908 may be performed by the determining component 1440 of fig. 14. The response may be an grant, a rejection, an Acknowledgement (ACK) or a Negative ACK (NACK).

At 910, the UE may send a message associated with at least one of the one or more future network slices, the one or more current network slices, or the one or more past network slices to the network node (e.g., base station) based on the response, as described in connection with the examples in fig. 4-7. For example, the UE 702 may send a message associated with at least one of the one or more future network slices, the one or more current network slices, or the one or more past network slices to the network node (e.g., base station) based on the response, as described in connection with 740 in fig. 7. Further, 910 may be performed by determining component 1440 in fig. 14. The message may be a Radio Resource Control (RRC) message or a non-access stratum (NAS) message. The RRC message may be a UE Assistance Information (UAI) message, an RRC complete message, or a new RRC message.

Fig. 10 is a flow chart 1000 of a method of wireless communication. The method may be performed by a network entity or a component of a network entity (e.g., AMFs 192, 606; network entity 706; device 1502). The methods described herein may provide several benefits, such as improved communication signaling, resource utilization, and/or power savings.

At 1002, a network entity may receive from at least one UE at least one of an indication of one or more future network slices corresponding to network slices for potential future use by the at least one UE, an indication of one or more current network slices corresponding to network slices currently used by the UE, or an indication of one or more past network slices corresponding to network slices previously used by the at least one UE, as described in connection with the examples in fig. 4-7. For example, the network entity 706 may receive at least one of an indication of one or more future network slices corresponding to network slices for potential future use by the at least one UE, an indication of one or more current network slices corresponding to network slices currently used by the UE, or an indication of one or more past network slices corresponding to network slices previously used by the at least one UE, as described in connection with 724 of fig. 7. Further, 1002 may be performed by determination component 1540 in fig. 15.

Further, the indication of the one or more future network slices may correspond to a list associated with network slice selection assistance information (nsaai). The list associated with the nsai may correspond to the updated requested nsai or a wish list for the nsai. The list associated with the NSSAI corresponds to an extension of the requested NSSAI or an adjustment of the requested NSSAI. The one or more future network slices are associated with a slice priority, the one or more current network slices are associated with the slice priority, and the one or more past network slices are associated with the slice priority. The network entity may be an access and mobility management function (AMF), a Session Management Function (SMF) or a network data analysis function (NWDAF). In some aspects, if the network entity is an AMF, the network entity may receive network slice information associated with at least one of the one or more future network slices, the one or more current network slices, or the one or more past network slices from the SMF; and sending an indication of the received network slice information to the NWDAF.

At 1006, the network entity may send Network Slice Selection Assistance Information (NSSAI) to at least one network node (e.g., base station) based on at least one of the indication of the one or more future network slices, the indication of the one or more current network slices, or the indication of the one or more past network slices, as described in connection with the examples in fig. 4-7. For example, the network entity 706 may send network slice selection assistance information (nsai) to at least one network node (e.g., base station) based on at least one of the indication of the one or more future network slices, the indication of the one or more current network slices, or the indication of the one or more past network slices, as described in connection with 754 in fig. 7. Further, 1006 can be performed by determination component 1540 in fig. 15.

Fig. 11 is a flow chart 1100 of a method of wireless communication. The method may be performed by a network entity or a component of a network entity (e.g., AMFs 192, 606; network entity 706; device 1502). The methods described herein may provide several benefits, such as improved communication signaling, resource utilization, and/or power savings.

At 1102, the network entity may receive at least one of an indication of one or more future network slices corresponding to network slices for potential future use by the at least one UE, an indication of one or more current network slices corresponding to network slices currently used by the UE, or an indication of one or more past network slices corresponding to network slices previously used by the at least one UE, as described in connection with the examples in fig. 4-7. For example, the network entity 706 may receive at least one of an indication of one or more future network slices corresponding to network slices for potential future use by the at least one UE, an indication of one or more current network slices corresponding to network slices currently used by the UE, or an indication of one or more past network slices corresponding to network slices previously used by the at least one UE, as described in connection with 724 of fig. 7. Further, 1102 can be performed by determination component 1540 in fig. 15.

At 1104, the network entity may send a response to the at least one UE to at least one of the indication of the one or more future network slices, the indication of the one or more current network slices, or the indication of the one or more past network slices, as described in connection with the examples in fig. 4-7. For example, the network entity 706 may send a response to the at least one UE to at least one of the indication of the one or more future network slices, the indication of the one or more current network slices, or the indication of the one or more past network slices, as described in connection with 730 in fig. 7. Further, 1104 may be performed by determination component 1540 in fig. 15. The response may be an grant, a rejection, an Acknowledgement (ACK) or a Negative ACK (NACK).

At 1106, the network entity may send network slice selection assistance information (nsai) to at least one network node (e.g., base station) based on at least one of the indication of the one or more future network slices, the indication of the one or more current network slices, or the indication of the one or more past network slices, as described in connection with the examples in fig. 4-7. For example, the network entity 706 may send network slice selection assistance information (nsai) to at least one network node (e.g., base station) based on at least one of the indication of the one or more future network slices, the indication of the one or more current network slices, or the indication of the one or more past network slices, as described in connection with 754 in fig. 7. Furthermore, 1106 may be performed by determination component 1540 in fig. 15.

At 1108, the network entity may configure a network slice structure based on at least one of the one or more future network slices, the one or more current network slices, or the one or more past network slices, as described in connection with the examples in fig. 4-7. For example, the network entity 706 may configure a network slice structure based on at least one of the one or more future network slices, the one or more current network slices, or the one or more past network slices, as described in connection with 760 in fig. 7. Further, 1108 can be performed by determination component 1540 in fig. 15. The network slice structure is associated with a Radio Resource Management (RRM) decision at the network entity. The RRM decision may be associated with a decision to handover or redirect to at least one other network node (e.g., a base station), at least one other frequency, or at least one other Radio Access Technology (RAT).

Fig. 12 is a flow chart 1200 of a method of wireless communication. The method may be performed by a network node (e.g., a base station) or a component of a network node (e.g., a base station 102, 180, 310, 604; network node 704; device 1602). The methods described herein may provide several benefits, such as improved communication signaling, resource utilization, and/or power savings.

At 1202, a network node (e.g., a base station) may receive from at least one UE at least one of an indication of one or more future network slices corresponding to network slices for potential future use by the at least one UE, an indication of one or more current network slices corresponding to network slices currently used by the UE, or an indication of one or more past network slices corresponding to network slices previously used by the at least one UE, as described in connection with the examples in fig. 4-7. For example, the network node 704 may receive at least one of an indication of one or more future network slices corresponding to network slices for potential future use by the at least one UE, an indication of one or more current network slices corresponding to network slices currently used by the UE, or an indication of one or more past network slices corresponding to network slices previously used by the at least one UE, as described in connection with 722 in fig. 7. Further, 1202 may be performed by the determination component 1640 in fig. 16.

Additionally, the indication of the one or more future network slices may correspond to a list associated with network slice selection assistance information (nsaai). The list associated with the nsai may correspond to the updated requested nsai or a wish list for the nsai. The list associated with the NSSAI corresponds to an extension of the requested NSSAI or an adjustment of the requested NSSAI. The one or more future network slices are associated with a slice priority, the one or more current network slices are associated with the slice priority, and the one or more past network slices are associated with the slice priority.

At 1206, the network node (e.g., base station) may send network slice selection assistance information (nsai) to at least one other network node (e.g., base station) based on at least one of the indication of the one or more future network slices, the indication of the one or more current network slices, or the indication of the one or more past network slices, as described in connection with the examples in fig. 4-7. For example, network node 704 may send network slice selection assistance information (nsai) to at least one other network node (e.g., base station) based on at least one of the indication of the one or more future network slices, the indication of the one or more current network slices, or the indication of the one or more past network slices, as described in connection with 752 in fig. 7. Further, 1206 may be performed by the determining component 1640 in fig. 16.

Fig. 13 is a flow chart 1300 of a method of wireless communication. The method may be performed by a network node (e.g., a base station) or a component of a network node (e.g., a base station 102, 180, 310, 604; network node 704; device 1602). The methods described herein may provide several benefits, such as improved communication signaling, resource utilization, and/or power savings.

At 1302, a network node (e.g., a base station) may receive at least one of an indication of one or more future network slices corresponding to network slices for potential future use by the at least one UE, an indication of one or more current network slices corresponding to network slices currently used by the UE, or an indication of one or more past network slices corresponding to network slices previously used by the at least one UE, as described in connection with the examples in fig. 4-7. For example, the network node 704 may receive at least one of an indication of one or more future network slices corresponding to network slices for potential future use by the at least one UE, an indication of one or more current network slices corresponding to network slices currently used by the UE, or an indication of one or more past network slices corresponding to network slices previously used by the at least one UE, as described in connection with 722 in fig. 7. Further, 1302 can be performed by the determining component 1640 in fig. 16.

At 1304, a network node (e.g., a base station) may receive a message associated with at least one of the one or more future network slices, the one or more current network slices, or the one or more past network slices from the at least one UE, as described in connection with the examples in fig. 4-7. For example, the network node 704 may receive a message associated with at least one of the one or more future network slices, the one or more current network slices, or the one or more past network slices from the at least one UE, as described in connection with 742 in fig. 7. Further, 1304 may be performed by a determining component 1640 in fig. 16. The message may be a Radio Resource Control (RRC) message or a non-access stratum (NAS) message. The RRC message may be a UE Assistance Information (UAI) message, an RRC complete message, or a new RRC message.

At 1306, a network node (e.g., base station) may send network slice selection assistance information (nsai) to at least one other network node (e.g., base station) based on at least one of the indication of the one or more future network slices, the indication of the one or more current network slices, or the indication of the one or more past network slices, as described in connection with the examples in fig. 4-7. For example, network node 704 may send network slice selection assistance information (nsai) to at least one other network node (e.g., base station) based on at least one of the indication of the one or more future network slices, the indication of the one or more current network slices, or the indication of the one or more past network slices, as described in connection with 752 in fig. 7. Further, 1306 may be performed by the determining component 1640 in fig. 16.

At 1308, a network node (e.g., a base station) may configure at least one of a handover procedure, a redirection procedure, a serving cell change, or a cell addition for Carrier Aggregation (CA), the configuration being based on at least one of the one or more future network slices, the one or more current network slices, or the one or more past network slices, as described in connection with the examples in fig. 4-7. For example, network node 704 may be configured for at least one of a handover procedure, a redirection procedure, a serving cell change, or a cell addition of Carrier Aggregation (CA), the configuration being based on at least one of the one or more future network slices, the one or more current network slices, or the one or more past network slices, as described in connection with 770 in fig. 7. Further, 1308 may be performed by the determining component 1640 in fig. 16. The handover procedure or the redirection procedure is associated with a handover or redirection to the at least one other network node (e.g., base station), at least one other frequency, or at least one other Radio Access Technology (RAT).

Fig. 14 is a diagram 1400 illustrating an example of a hardware implementation for the device 1402. The apparatus 1402 may be a UE, a component of a UE, or may implement UE functionality. In some aspects, the device 1402 may include a cellular baseband processor 1404 (also referred to as a modem) coupled to a cellular RF transceiver 1422. In some aspects, the device 1402 may also include one or more Subscriber Identity Module (SIM) cards 1420, an application processor 1406 coupled to a Secure Digital (SD) card 1408 and a screen 1410, a bluetooth module 1412, a Wireless Local Area Network (WLAN) module 1414, a Global Positioning System (GPS) module 1416, or a power source 1418. The cellular baseband processor 1404 communicates with the UE 104 and/or BS102/180 via a cellular RF transceiver 1422. The cellular baseband processor 1404 may include a computer readable medium/memory. The computer readable medium/memory may be non-transitory. The cellular baseband processor 1404 is responsible for general processing, including the execution of software stored on the computer-readable medium/memory. The software, when executed by the cellular baseband processor 1404, causes the cellular baseband processor 1404 to perform the various functions described supra. The computer readable medium/memory can also be used for storing data that is manipulated by the cellular baseband processor 1404 when executing software. The cellular baseband processor 1404 also includes a receive component 1430, a communication manager 1432, and a transmit component 1434. The communications manager 1432 includes one or more of the illustrated components. Components within the communications manager 1432 may be stored in a computer-readable medium/memory and/or configured as hardware within the cellular baseband processor 1404. The cellular baseband processor 1404 may be a component of the UE 350 and may include the memory 360 and/or at least one of the TX processor 368, the RX processor 356, and the controller/processor 359. In one configuration, the apparatus 1402 may be a modem chip and include only the baseband processor 1404, while in another configuration, the apparatus 1402 may be an entire UE (see, e.g., 350 of fig. 3) and include additional modules of the apparatus 1402.

The communication manager 1432 includes a determining component 1440 configured to store a history of use of one or more past network slices prior to sending the indication of the one or more past network slices, e.g., as described in connection with step 902 above. The determining component 1440 may be further configured to calculate a probability of use of the one or more future network slices prior to sending the indication of the one or more future network slices, e.g., as described in connection with step 904 above. The determining component 1440 may also be configured to transmit at least one of an indication of one or more future network slices corresponding to network slices for potential future use by the UE, an indication of one or more current network slices corresponding to network slices currently used by the UE, or an indication of one or more past network slices corresponding to network slices previously used by the UE to at least one of a network node (e.g., a base station) or a network entity, e.g., as described in connection with step 906 above. The determining component 1440 may be further configured to receive a response from the network entity to at least one of the indication of the one or more future network slices, the indication of the one or more current network slices, or the indication of the one or more past network slices, e.g., as described in connection with step 908 above. The determining component 1440 may be further configured to send a message associated with at least one of the one or more future network slices, the one or more current network slices, or the one or more past network slices to the network node (e.g., base station) based on the response, e.g., as described in connection with step 910 above.

The apparatus may include additional components to perform each of the blocks of the algorithm in the flowcharts of fig. 7-9. As such, each block in the flowcharts of fig. 7-9 may be performed by a component and the apparatus may include one or more of those components. These components may be one or more hardware components specifically configured to perform the process/algorithm, implemented by a processor configured to perform the process/algorithm, stored in a computer-readable medium for implementation by a processor, or some combination thereof.

As shown, the apparatus 1402 may include various components configured for various functions. In one configuration, the apparatus 1402 (and in particular, the cellular baseband processor 1404) includes means for storing a history of use of one or more past network slices before sending an indication of the one or more past network slices. The apparatus 1402 may also include means for calculating a probability of use of the one or more future network slices prior to sending the indication of the one or more future network slices. The apparatus 1402 may also include means for transmitting, to at least one of a network node (e.g., a base station) or a network entity, at least one of an indication of one or more future network slices corresponding to network slices for potential future use by the UE, an indication of one or more current network slices corresponding to network slices currently used by the UE, or an indication of one or more past network slices corresponding to network slices previously used by the UE. The apparatus 1402 may also include means for receiving, from the network entity, a response to at least one of the indication of the one or more future network slices, the indication of the one or more current network slices, or the indication of the one or more past network slices. The apparatus 1402 may also include means for sending a message associated with at least one of the one or more future network slices, the one or more current network slices, or the one or more past network slices to the network node (e.g., base station) based on the response. These components may be one or more of the components of the apparatus 1402 configured to perform the functions recited by the components. As described above, the device 1402 may include a TX processor 368, an RX processor 356, and a controller/processor 359. As such, in one configuration, these means may be TX processor 368, RX processor 356, and controller/processor 359 configured to perform the functions recited by the means.

Fig. 15 is a diagram 1500 illustrating an example of a hardware implementation for an apparatus 1502. The apparatus 1502 may be a network entity, a component of a network entity, or may implement a network entity function. In some aspects, the device 1502 may include a baseband unit 1504. The baseband unit 1504 may communicate with the UE 104 through a cellular RF transceiver 1522. Baseband unit 1504 may include a computer readable medium/memory. The baseband unit 1504 is responsible for general processing, including the execution of software stored on a computer-readable medium/memory. The software, when executed by baseband unit 1504, causes baseband unit 1504 to perform the various functions described supra. The computer-readable medium/memory may also be used for storing data that is manipulated by the baseband unit 1504 when executing software. Baseband unit 1504 also includes a receive component 1530, a communication manager 1532, and a transmit component 1534. The communication manager 1532 includes one or more of the illustrated components. Components within the communication manager 1532 may be stored in a computer-readable medium/memory and/or configured as hardware within the baseband unit 1504. Baseband unit 1504 may be a component of AMF 192.

The communication manager 1532 includes a determining component 1540 configured to receive from at least one User Equipment (UE) at least one of an indication of one or more future network slices corresponding to network slices for potential future use by the at least one UE, an indication of one or more current network slices corresponding to network slices currently used by the UE, or an indication of one or more past network slices corresponding to network slices previously used by the at least one UE, e.g., as described in connection with step 1102 above. The determining component 1540 may be further configured to send to the at least one UE a response to at least one of the indication of the one or more future network slices, the indication of the one or more current network slices, or the indication of the one or more past network slices, e.g., as described in connection with step 1104 above. The determining component 1540 may be further configured to transmit Network Slice Selection Assistance Information (NSSAI) to at least one network node (e.g., base station) based on at least one of the indication of the one or more future network slices, the indication of the one or more current network slices, or the indication of the one or more past network slices, e.g., as described in connection with step 1106 above. The determining component 1540 may also be configured to configure a network slice structure based on at least one of the one or more future network slices, the one or more current network slices, or the one or more past network slices, e.g., as described in connection with step 1108 above.

The apparatus may include additional components to perform each of the blocks of the algorithms in the flowcharts of fig. 7, 10, and 11. As such, each block in the flowcharts of fig. 7, 10, and 11 may be performed by a component and the apparatus may include one or more of those components. These components may be one or more hardware components specifically configured to perform the process/algorithm, implemented by a processor configured to perform the process/algorithm, stored in a computer-readable medium for implementation by a processor, or some combination thereof.

As shown, the apparatus 1502 may include various components configured for various functions. In one configuration, the apparatus 1502 (and in particular, the baseband unit 1504) includes means for receiving, from at least one User Equipment (UE), at least one of an indication of one or more future network slices corresponding to network slices for potential future use by the at least one UE, an indication of one or more current network slices corresponding to network slices currently used by the UE, or an indication of one or more past network slices corresponding to network slices previously used by the at least one UE. The apparatus 1502 may also include means for sending, to the at least one UE, a response to at least one of the indication of the one or more future network slices, the indication of the one or more current network slices, or the indication of the one or more past network slices. The apparatus 1502 may also include means for transmitting network slice selection assistance information (nsai) to at least one network node (e.g., a base station) based on at least one of the indication of the one or more future network slices, the indication of the one or more current network slices, or the indication of the one or more past network slices. The apparatus 1502 may also include means for configuring a network slice structure based on at least one of the one or more future network slices, the one or more current network slices, or the one or more past network slices. These components may be one or more of the components of apparatus 1502 that are configured to perform the functions recited by the components. As described above, device 1502 may include AMF 192. As such, in one configuration, the components may be AMFs 192 configured to perform the functions recited by the components.

Fig. 16 is a diagram 1600 illustrating an example of a hardware implementation for an apparatus 1602. The apparatus 1602 may be a network node (e.g., a base station), a component of a network node (e.g., a base station), or may implement the functionality of a network node or a base station. In some aspects, the device 1602 may include a baseband unit 1604. The baseband unit 1604 may communicate with the UE 104 via a cellular RF transceiver 1622. Baseband unit 1604 may include a computer readable medium/memory. The baseband unit 1604 is responsible for general processing, including the execution of software stored on a computer-readable medium/memory. The software, when executed by baseband unit 1604, causes baseband unit 1604 to perform the various functions described supra. The computer readable medium/memory may also be used for storing data that is manipulated by the baseband unit 1604 when executing software. The baseband unit 1604 also includes a receiving component 1630, a communication manager 1632, and a transmitting component 1634. The communications manager 1632 includes one or more of the illustrated components. Components within the communication manager 1632 may be stored in a computer-readable medium/memory and/or configured as hardware within the baseband unit 1604. Baseband unit 1604 may be a component of base station 310 and may include memory 376 and/or at least one of TX processor 316, RX processor 370, and controller/processor 375.

The communication manager 1632 includes a determination component 1640 configured to receive from at least one User Equipment (UE) at least one of an indication of one or more future network slices corresponding to network slices for potential future use by the at least one UE, an indication of one or more current network slices corresponding to network slices currently used by the UE, or an indication of one or more past network slices corresponding to network slices previously used by the at least one UE, e.g., as described in connection with step 1302 above. The determining component 1640 may be further configured to receive a message associated with at least one of the one or more future network slices, the one or more current network slices, or the one or more past network slices from the at least one UE, e.g., as described in connection with step 1304 above. The determining component 1640 may be further configured to transmit network slice selection assistance information (nsai) to at least one other network node (e.g., a base station) based on at least one of the indication of the one or more future network slices, the indication of the one or more current network slices, or the indication of the one or more past network slices, e.g., as described in connection with step 1306 above. The determining component 1640 may be further configured to configure at least one of a handover procedure, a redirection procedure, a serving cell change, or a cell addition for Carrier Aggregation (CA), the configuring being based on at least one of the one or more future network slices, the one or more current network slices, or the one or more past network slices, e.g., as described in connection with step 1308 above.

The apparatus may include additional components to perform each of the blocks of the algorithms in the flowcharts of fig. 7, 12, and 13. As such, each block in the flowcharts of fig. 7, 12, and 13 may be performed by a component and the apparatus may include one or more of those components. These components may be one or more hardware components specifically configured to perform the process/algorithm, implemented by a processor configured to perform the process/algorithm, stored in a computer-readable medium for implementation by a processor, or some combination thereof.

As shown, the apparatus 1602 may include various components configured for various functions. In one configuration, the apparatus 1602 (and in particular, the baseband unit 1604) includes means for receiving, from at least one User Equipment (UE), at least one of an indication of one or more future network slices corresponding to network slices for potential future use by the at least one UE, an indication of one or more current network slices corresponding to network slices currently used by the UE, or an indication of one or more past network slices corresponding to network slices previously used by the at least one UE. The apparatus 1602 may also include means for receiving a message associated with at least one of the one or more future network slices, the one or more current network slices, or the one or more past network slices from the at least one UE. The apparatus 1602 may also include means for transmitting Network Slice Selection Assistance Information (NSSAI) to at least one other network node (e.g., a base station) based on at least one of the indication of the one or more future network slices, the indication of the one or more current network slices, or the indication of the one or more past network slices. The apparatus 1602 may also include means for configuring at least one of a handover procedure, a redirection procedure, a serving cell change, or a cell addition for Carrier Aggregation (CA), the configuring based on at least one of the one or more future network slices, the one or more current network slices, or the one or more past network slices. These components may be one or more of the components of the apparatus 1602 configured to perform the functions recited by the components. As described above, the device 1602 may include the TX processor 316, the RX processor 370, and the controller/processor 375. As such, in one configuration, these components may be TX processor 316, RX processor 370, and controller/processor 375 configured to perform the functions recited by the component.

It should be understood that the specific order or hierarchy of blocks in the processes/flowcharts disclosed is an illustration of example approaches. It should be appreciated that the particular order or hierarchy of blocks in the process/flow diagram may be rearranged based on design preferences. In addition, some blocks may be combined or omitted. The accompanying method claims present elements of the various blocks in a sample order, and are not meant to be limited to the specific order or hierarchy presented.

The previous description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other aspects. Thus, the claims are not intended to be limited to the aspects shown herein, but is to be accorded the full scope consistent with the language claims, wherein reference to an element in the singular is not intended to mean "one and only one" unless specifically so stated, but rather "one or more". Terms such as "if," when "and" while at "should be interpreted as" under conditions of "when at" and not meaning immediate time relationships or reactions. That is, these phrases, such as "when," do not imply that an action will occur in response to or during the occurrence of an action, but simply imply that if a condition is met, no special or immediate time constraints are required for the action to occur. The phrase "exemplary" is used herein to mean "serving as an example, instance, or illustration. Any aspect described herein as "exemplary" is not necessarily to be construed as preferred or advantageous over other aspects. The term "some" means one or more unless specifically stated otherwise. Combinations such as "at least one of A, B or C", "one or more of A, B or C", "at least one of A, B and C", "one or more of A, B and C", and "A, B, C or any combination thereof", including any combination of A, B and/or C, may include a plurality of a, a plurality of B, or a plurality of C. Specifically, a combination such as "at least one of A, B or C", "one or more of A, B or C", "at least one of A, B and C", "one or more of A, B and C", and "A, B, C or any combination thereof" may be a alone, B alone, C, A and B, A and C, B and C, or a and B and C, wherein any such combination may comprise one or more members of A, B or C, or a plurality of members. All structural and functional equivalents to the elements of the aspects described throughout this disclosure that are known or later come to be known to those of ordinary skill in the art are expressly incorporated herein by reference and are intended to be encompassed by the claims. Furthermore, nothing disclosed herein is intended to be dedicated to the public regardless of whether such disclosure is explicitly recited in the claims. The terms "module," mechanism, "" element, "" device, "and the like are not intended to be substituted for the term" component. As such, no claim element is to be construed as a functional element unless the element is explicitly recited using the phrase "means for.

The following aspects are merely illustrative and may be combined with other aspects or teachings described herein without limitation.

Aspect 1 is an apparatus for wireless communication at a User Equipment (UE), the apparatus comprising: at least one processor coupled to the memory and configured to, based at least in part on information stored in the memory: transmitting, to at least one of a network node (e.g., a base station) or a network entity, at least one of an indication of one or more future network slices, an indication of one or more current network slices, or an indication of one or more past network slices, the one or more future network slices corresponding to network slices for potential future use by the UE, the one or more current network slices corresponding to network slices currently used by the UE, the one or more past network slices corresponding to network slices previously used by the UE; and receiving, from the network entity, a response to at least one of the indication of the one or more future network slices, the indication of the one or more current network slices, or the indication of the one or more past network slices.

Aspect 2 is the apparatus of aspect 1, wherein the indication of the one or more future network slices comprises at least one of: the probability of use of the one or more future network slices, the weighting factor of the one or more future network slices, or the priority index of the one or more future network slices.

Aspect 3 is the apparatus of any one of aspects 1 and 2, wherein the indication of the one or more current network slices comprises at least one of: the weighting factor of the one or more current network slices or the priority index of the one or more current network slices.

Aspect 4 is the apparatus of any one of aspects 1-3, wherein the indication of the one or more past network slices comprises a history of use of the one or more past network slices.

Aspect 5 is the apparatus of any one of aspects 1 to 4, wherein the usage history of the one or more past network slices comprises at least one of: the previous usage of the one or more past network slices, the weighting factor of the one or more past network slices, or the priority index of the one or more past network slices over a duration.

Aspect 6 is the apparatus of any one of aspects 1-5, wherein the indication of the one or more future network slices corresponds to a list associated with Network Slice Selection Assistance Information (NSSAI).

Aspect 7 is the apparatus of any one of aspects 1 to 6, wherein the list associated with the nsai corresponds to an updated requested nsai or a wish list for an nsai.

Aspect 8 is the apparatus of any one of aspects 1 to 7, wherein the list associated with the nsai corresponds to an extension of a requested nsai or an adjustment of a requested nsai.

Aspect 9 is the apparatus of any one of aspects 1 to 8, wherein the at least one processor is further configured to: the method further includes storing a history of use of the one or more past network slices prior to transmitting the indication of the one or more past network slices.

Aspect 10 is the apparatus of any one of aspects 1-9, wherein the at least one processor is further configured to: the probability of use of the one or more future network slices is calculated prior to sending the indication of the one or more future network slices.

Aspect 11 is the apparatus of any one of aspects 1 to 10, wherein the response is an grant, a rejection, an Acknowledgement (ACK), or a Negative ACK (NACK).

Aspect 12 is the apparatus of any one of aspects 1-11, wherein the at least one processor is further configured to: a message associated with at least one of the one or more future network slices, the one or more current network slices, or the one or more past network slices is sent to the network node (e.g., base station) based on the response.

Aspect 13 is the apparatus of any one of aspects 1 to 12, wherein the message is a Radio Resource Control (RRC) message or a non-access stratum (NAS) message.

Aspect 14 is the apparatus of any one of aspects 1 to 13, wherein the RRC message is a UE Assistance Information (UAI) message, an RRC complete message, or a new RRC message.

Aspect 15 is the apparatus of any one of aspects 1-14, wherein the one or more future network slices are associated with a slice priority, the one or more current network slices are associated with the slice priority, and the one or more past network slices are associated with the slice priority.

Aspect 16 is the apparatus of any one of aspects 1 to 15, further comprising a transceiver coupled to the at least one processor, wherein the network entity is an access and mobility management function (AMF), a Session Management Function (SMF), or a network data analysis function (NWDAF).

Aspect 17 is an apparatus for wireless communication at a network entity, the apparatus comprising: at least one processor coupled to the memory and configured to, based at least in part on information stored in the memory: receiving from at least one User Equipment (UE) at least one of an indication of one or more future network slices, an indication of one or more current network slices, or an indication of one or more past network slices, the one or more future network slices corresponding to network slices for potential future use by the at least one UE, the one or more current network slices corresponding to network slices currently used by the UE, the one or more past network slices corresponding to network slices previously used by the at least one UE; and transmitting Network Slice Selection Assistance Information (NSSAI) to at least one network node (e.g., base station) based on at least one of the indication of the one or more future network slices, the indication of the one or more current network slices, or the indication of the one or more past network slices.

Aspect 18 is the apparatus of aspect 17, wherein the indication of the one or more future network slices comprises at least one of: the probability of use of the one or more future network slices, the weighting factor of the one or more future network slices, or the priority index of the one or more future network slices.

Aspect 19 is the apparatus of any one of aspects 17 and 18, wherein the indication of the one or more current network slices comprises at least one of: the weighting factor of the one or more current network slices or the priority index of the one or more current network slices.

Aspect 20 is the apparatus of any one of aspects 17-19, wherein the indication of the one or more past network slices includes a history of use of the one or more past network slices.

Aspect 21 is the apparatus of any one of aspects 17 to 20, wherein the usage history of the one or more past network slices comprises at least one of: the previous usage of the one or more past network slices, the weighting factor of the one or more past network slices, or the priority index of the one or more past network slices over a duration.

Aspect 22 is the apparatus of any one of aspects 17-21, wherein the indication of the one or more future network slices corresponds to a list associated with Network Slice Selection Assistance Information (NSSAI).

Aspect 23 is the apparatus of any one of aspects 17 to 22, wherein the list associated with the nsai corresponds to an updated requested nsai or a wish list for an nsai.

Aspect 24 is the apparatus of any one of aspects 17 to 23, wherein the list associated with the nsai corresponds to an extension of a requested nsai or an adjustment of a requested nsai.

Aspect 25 is the apparatus of any one of aspects 17-24, wherein the at least one processor is further configured to: the network slice structure is configured based on at least one of the one or more future network slices, the one or more current network slices, or the one or more past network slices.

Aspect 26 is the apparatus of any one of aspects 17-25, wherein the network slice structure is associated with a Radio Resource Management (RRM) decision at the network entity.

Aspect 27 is the apparatus of any one of aspects 17 to 26, wherein the RRM decision is associated with a decision to handover or redirect to at least one other network node (e.g., a base station), at least one other frequency, or at least one other Radio Access Technology (RAT).

Aspect 28 is the apparatus of any one of aspects 17-27, wherein the at least one processor is further configured to: a response to at least one of the indication of the one or more future network slices, the indication of the one or more current network slices, or the indication of the one or more past network slices is sent to the at least one UE.

Aspect 29 is the apparatus of any one of aspects 17 to 28, wherein the response is an grant, a rejection, an Acknowledgement (ACK), or a Negative ACK (NACK).

Aspect 30 is the apparatus of any one of aspects 17-29, wherein the one or more future network slices are associated with a slice priority, the one or more current network slices are associated with the slice priority, and the one or more past network slices are associated with the slice priority.

Aspect 31 is the apparatus of any one of aspects 17 to 30, further comprising a transceiver coupled to the at least one processor, wherein the network entity is an access and mobility management function (AMF), a Session Management Function (SMF), or a network data analysis function (NWDAF).

Aspect 32 is the apparatus of any one of aspects 17-31, wherein the network entity is the AMF, wherein the at least one processor is further configured to: receive, from the SMF, network slice information associated with at least one of the one or more future network slices, the one or more current network slices, or the one or more past network slices; and sending an indication of the received network slice information to the NWDAF.

Aspect 33 is an apparatus for wireless communication at a network node (e.g., a base station), the apparatus comprising: at least one processor coupled to the memory and configured to, based at least in part on information stored in the memory: receiving from at least one User Equipment (UE) at least one of an indication of one or more future network slices, an indication of one or more current network slices, or an indication of one or more past network slices, the one or more future network slices corresponding to network slices for potential future use by the at least one UE, the one or more current network slices corresponding to network slices currently used by the UE, the one or more past network slices corresponding to network slices previously used by the at least one UE; and transmitting Network Slice Selection Assistance Information (NSSAI) to at least one other network node (e.g., base station) based on at least one of the indication of the one or more future network slices, the indication of the one or more current network slices, or the indication of the one or more past network slices.

Aspect 34 is the apparatus of aspect 33, wherein the indication of the one or more future network slices comprises at least one of: the probability of use of the one or more future network slices, the weighting factor of the one or more future network slices, or the priority index of the one or more future network slices.

Aspect 35 is the apparatus of any one of aspects 33 and 34, wherein the indication of the one or more current network slices comprises at least one of: the weighting factor of the one or more current network slices or the priority index of the one or more current network slices.

Aspect 36 is the apparatus of any one of aspects 33-35, wherein the indication of the one or more past network slices includes a history of use of the one or more past network slices.

Aspect 37 is the apparatus of any one of aspects 33 to 36, wherein the usage history of the one or more past network slices comprises at least one of: the previous usage of the one or more past network slices, the weighting factor of the one or more past network slices, or the priority index of the one or more past network slices over a duration.

Aspect 38 is the apparatus of any one of aspects 33-37, wherein the indication of the one or more future network slices corresponds to a list associated with Network Slice Selection Assistance Information (NSSAI).

Aspect 39 is the apparatus of any one of aspects 33 to 38, wherein the list associated with the nsai corresponds to an updated requested nsai or a wish list for an nsai.

Aspect 40 is the apparatus of any one of aspects 33 to 39, wherein the list associated with the nsai corresponds to an extension of a requested nsai or an adjustment of a requested nsai.

Aspect 41 is the apparatus of any one of aspects 33-40, wherein the at least one processor is further configured to: at least one of a handoff procedure, a redirection procedure, a serving cell change, or a cell addition for Carrier Aggregation (CA) is configured, the configuration being based on at least one of the one or more future network slices, the one or more current network slices, or the one or more past network slices.

Aspect 42 is the apparatus of any one of aspects 33-41, wherein the handover procedure or the redirection procedure is associated with a handover or redirection to the at least one other network node (e.g., base station), at least one other frequency, or at least one other Radio Access Technology (RAT).

Aspect 43 is the apparatus of any one of aspects 33-42, wherein the at least one processor is further configured to: a message associated with at least one of the one or more future network slices, the one or more current network slices, or the one or more past network slices is received from the at least one UE.

Aspect 44 is the apparatus of any one of aspects 33 to 43, wherein the message is a Radio Resource Control (RRC) message or a non-access stratum (NAS) message.

Aspect 45 is the apparatus of any one of aspects 33 to 44, wherein the RRC message is a UE Assistance Information (UAI) message, an RRC complete message, or a new RRC message.

Aspect 46 is the apparatus of any one of aspects 33-45, further comprising a transceiver coupled to the at least one processor, wherein the one or more future network slices are associated with a slice priority, the one or more current network slices are associated with the slice priority, and the one or more past network slices are associated with the slice priority.

Aspect 47 is a method for implementing wireless communication of any one of aspects 1 to 46.

Aspect 48 is an apparatus for wireless communication, the apparatus comprising means for implementing any one of aspects 1 to 46.

Aspect 49 is a computer-readable medium (e.g., a non-transitory computer-readable medium) storing computer-executable code, wherein the code, when executed by a processor, causes the processor to implement any one of aspects 1 to 46.

Claims

1. An apparatus for wireless communication at a User Equipment (UE), the apparatus comprising:

a memory; and

at least one processor coupled to the memory and configured to, based at least in part on information stored in the memory:

sending at least one of an indication of one or more future network slices, an indication of one or more current network slices, or an indication of one or more past network slices to at least one of a network node or a network entity, the one or more future network slices corresponding to network slices for potential future use of the UE,

the one or more current network slices correspond to network slices currently used by the UE, and the one or more past network slices correspond to network slices previously used by the UE; and

A response to at least one of the indication of the one or more future network slices, the indication of the one or more current network slices, or the indication of the one or more past network slices is received from the network entity.

2. The apparatus of claim 1, wherein the indication of the one or more future network slices comprises at least one of: the probability of use of the one or more future network slices, the weighting factor of the one or more future network slices, or the priority index of the one or more future network slices.

3. The apparatus of claim 1, wherein the indication of the one or more current network slices comprises at least one of: the weighting factor of the one or more current network slices or the priority index of the one or more current network slices.

4. The apparatus of claim 1, wherein the indication of the one or more past network slices comprises a history of use of the one or more past network slices.

5. The apparatus of claim 4, wherein the history of use of the one or more past network slices comprises at least one of: the previous usage of the one or more past network slices, the weighting factor of the one or more past network slices, or the priority index of the one or more past network slices over a duration.

6. The apparatus of claim 1, wherein the indication of the one or more future network slices corresponds to a list associated with network slice selection assistance information (nsaai).

7. The apparatus of claim 6, wherein the list associated with the nsai corresponds to an updated requested nsai or a wish list for nsais.

8. The apparatus of claim 6, wherein the list associated with the nsai corresponds to an extension of a requested nsai or an adjustment of a requested nsai.

9. The apparatus of claim 1, wherein the at least one processor is further configured to:

the method further includes storing a history of use of the one or more past network slices prior to transmitting the indication of the one or more past network slices.

10. The apparatus of claim 1, wherein the at least one processor is further configured to:

the probability of use of the one or more future network slices is calculated prior to sending the indication of the one or more future network slices.

11. The apparatus of claim 1, wherein the response is an grant, a rejection, an Acknowledgement (ACK), or a Negative ACK (NACK).

12. The apparatus of claim 1, wherein the at least one processor is further configured to:

a message associated with at least one of the one or more future network slices, the one or more current network slices, or the one or more past network slices is sent to the network node based on the response.

13. The apparatus of claim 12, wherein the message is a Radio Resource Control (RRC) message or a non-access stratum (NAS) message.

14. The apparatus of claim 13, wherein the RRC message is a UE Assistance Information (UAI) message, an RRC complete message, or a new RRC message.

15. The apparatus of claim 1, wherein the one or more future network slices are associated with a slice priority, the one or more current network slices are associated with the slice priority, and the one or more past network slices are associated with the slice priority.

16. The apparatus of claim 1, further comprising a transceiver coupled to the at least one processor, wherein the network entity is an access and mobility management function (AMF), a Session Management Function (SMF), or a network data analysis function (NWDAF).

17. An apparatus for wireless communication at a network entity, the apparatus comprising:

a memory; and

receiving from at least one User Equipment (UE) at least one of an indication of one or more future network slices, an indication of one or more current network slices, or an indication of one or more past network slices, the one or more future network slices corresponding to network slices for potential future use by the at least one UE, the one or more current network slices corresponding to network slices currently used by the UE, the one or more past network slices corresponding to network slices previously used by the at least one UE; and

network Slice Selection Assistance Information (NSSAI) is sent to at least one network node based on at least one of the indication of the one or more future network slices, the indication of the one or more current network slices, or the indication of the one or more past network slices.

18. The apparatus of claim 17, wherein the indication of the one or more future network slices comprises at least one of: the probability of use of the one or more future network slices, the weighting factor of the one or more future network slices, or the priority index of the one or more future network slices, and wherein the indication of the one or more current network slices comprises at least one of: the weighting factor of the one or more current network slices or the priority index of the one or more current network slices.

19. The apparatus of claim 17, wherein the indication of the one or more past network slices comprises a history of use of the one or more past network slices, wherein the history of use of the one or more past network slices comprises at least one of: the previous usage of the one or more past network slices, the weighting factor of the one or more past network slices, or the priority index of the one or more past network slices over a duration.

20. The apparatus of claim 17, wherein the indication of the one or more future network slices corresponds to a list associated with the nsaai.

21. The apparatus of claim 20, wherein the list associated with the nsai corresponds to an updated requested nsai or a wish list for nsais, or wherein the list associated with the nsai corresponds to an extension of a requested nsai or an adjustment of a requested nsai.

22. The apparatus of claim 17, wherein the at least one processor is further configured to:

the network slice structure is configured based on at least one of the one or more future network slices, the one or more current network slices, or the one or more past network slices.

23. The apparatus of claim 22, wherein the network slice structure is associated with a Radio Resource Management (RRM) decision at the network entity.

24. The apparatus of claim 23, wherein the RRM decision is associated with a decision to switch or redirect to at least one other network node, at least one other frequency, or at least one other Radio Access Technology (RAT).

25. The apparatus of claim 17, wherein the at least one processor is further configured to:

sending, to the at least one UE, a response to at least one of the indication of the one or more future network slices, the indication of the one or more current network slices, or the indication of the one or more past network slices, wherein the response is an allow, a reject, an Acknowledgement (ACK), or a Negative ACK (NACK).

26. The apparatus of claim 17, wherein the one or more future network slices are associated with a slice priority, the one or more current network slices are associated with the slice priority, and the one or more past network slices are associated with the slice priority.

27. The apparatus of claim 17, further comprising a transceiver coupled to the at least one processor, wherein the network entity is an access and mobility management function (AMF), a Session Management Function (SMF), or a network data analysis function (NWDAF).

28. The apparatus of claim 27, wherein the network entity is the AMF, wherein the at least one processor is further configured to:

receive, from the SMF, network slice information associated with at least one of the one or more future network slices, the one or more current network slices, or the one or more past network slices; and

an indication of the received network slice information is sent to the NWDAF.

29. A method of wireless communication at a User Equipment (UE), the method comprising:

transmitting, to at least one of a network node or a network entity, at least one of an indication of one or more future network slices, an indication of one or more current network slices, or an indication of one or more past network slices, the one or more future network slices corresponding to network slices for potential future use by the UE, the one or more current network slices corresponding to network slices currently used by the UE, the one or more past network slices corresponding to network slices previously used by the UE; and

30. A method of wireless communication at a network entity, the method comprising: