Techniques for smart slice prioritization

Abstract

Techniques for smart slice prioritization are disclosed. The application relates to apparatus and components including apparatuses, systems, and methods for slice prioritization implementation for frequency reselection.

Description

[0001] Cross-references to other applications

[0002] This patent application claims priority to U.S. Provisional Application No. 63 / 533,315 filed on August 17, 2023, for “TECHNOLOGIES FOR INTELLIGENT SLICE PRIORITIZATION,” and U.S. Non-Provisional Patent Application No. 18 / 775,542 filed on July 17, 2024, for “TECHNOLOGIES FOR INTELLIGENT SLICE PRIORITIZATION,” the entire contents of which are incorporated herein by reference for all purposes. Technical Field

[0003] The present application relates generally to cellular communication networks, and in particular to techniques for slice prioritization at user equipment. Background Art

[0004] Slice prioritization at the user equipment (UE) is a way to allocate network resources to different types of services or applications that require different levels of Quality of Service (QoS). For example, a video streaming service may require high data rates but can tolerate some latency, while a remote surgical application may require low latency but can use less bandwidth. By creating separate slices that prioritize specific resources, operators can provide customized solutions for different applications. BRIEF DESCRIPTION OF THE DRAWINGS

[0005] Figure 1 A network environment according to some embodiments is illustrated.

[0006] Figure 2 Some aspects of network slice access groups according to some embodiments are shown.

[0007] Figure 3 Some aspects of slice prioritization according to some embodiments are shown.

[0008] Figure 4 Some aspects of slice prioritization according to some embodiments are shown.

[0009] Figure 5 An operational flow / algorithm structure according to some embodiments is shown.

[0010] Figure 6 Some aspects of slice prioritization according to some embodiments are shown.

[0011] Figure 7 Some aspects of configuring a database according to some embodiments are shown.

[0012] Figure 8 An operational flow / algorithm structure according to some embodiments is shown.

[0013] Fig. 9 An operational flow / algorithm structure according to some embodiments is shown.

[0014] Fig.10 An operational flow / algorithm structure according to some embodiments is shown.

[0015] Fig.11 An operational flow / algorithm structure according to some embodiments is shown.

[0016] Fig.12 An operational flow / algorithm structure according to some embodiments is shown.

[0017] Fig.13 An operational flow / algorithm structure according to some embodiments is shown.

[0018] Fig.14 User equipment according to some embodiments is shown.

[0019] Fig.15 A network node according to some embodiments is shown. DETAILED DESCRIPTION

[0020] The following specific embodiments relate to the accompanying drawings. The same figure numbers may be used to identify the same or similar elements in different drawings. In the following description, for the purpose of explanation rather than limitation, specific details, such as specific structures, architectures, interfaces and / or technologies, are set forth to provide a thorough understanding of the various aspects of some embodiments. However, it is obvious to those skilled in the art who benefit from the present disclosure that the various aspects of various aspects can be practiced in other examples that deviate from these specific details. In some cases, the description of well-known equipment, circuits and methods is omitted so that the description of various aspects will not be obscured by unnecessary details. For the purpose of this document, the phrase "A or B" refers to (A), (B) or (A and B), and the phrase "based on A" refers to "based at least in part on A", for example, it can be "based only on A" or it can be "based in part on A".

[0021] The following is a glossary of terms that may be used in this disclosure.

[0022] As used herein, the term "circuit" refers to, is part of, or includes a hardware component such as an electronic circuit, a logic circuit, a processor (shared, dedicated, or group) or a memory (shared, dedicated, or group) configured to provide the described functions, an application specific integrated circuit (ASIC), a field programmable device (FPD) (e.g., a field programmable gate array (FPGA), a programmable logic device (PLD), a complex PLD (CPLD), a high capacity PLD (HCPLD), a structured ASIC, or a programmable system on chip (SoC)), and / or a digital signal processor (DSP). In some aspects, a circuit may execute one or more software or firmware programs to provide at least some of the described functions. The term "circuit" may also refer to a combination of one or more hardware elements and a program code for performing the functions of the program code (or a combination of circuits used in an electrical or electronic system). In these aspects, the combination of hardware elements and program code may be referred to as a specific type of circuit.

[0023] As used herein, the term "processor circuit" refers to, is a part of, or includes a circuit capable of sequentially and automatically performing a series of arithmetic or logical operations; or a circuit that records, stores, or transmits digital data. The term "processor circuit" may refer to an application processor; a baseband processor; a central processing unit (CPU); a graphics processing unit; a single-core processor; a dual-core processor; a triple-core processor; a quad-core processor; or any other device capable of executing or otherwise operating computer-executable instructions (such as program code); a software module; or a functional process.

[0024] As used herein, the term "interface circuit" refers to, is a part of, or includes a circuit that enables information exchange between two or more components or devices. The term "interface circuit" may refer to one or more hardware interfaces; for example, a bus, an I / O interface, a peripheral component interface, a network interface card, etc.

[0025] As used herein, the term "user equipment" or "UE" refers to a device that has radio communication capabilities and can describe a remote user of network resources in a communication network. In addition, the terms "user equipment" or "UE" may be considered synonymous and may be referred to as a client, mobile phone, mobile device, mobile terminal, user terminal, mobile unit, mobile station, mobile user, subscriber, user, remote station, access agent, user agent, receiver, radio equipment, reconfigurable radio equipment, reconfigurable mobile device, etc. In addition, the term "user equipment" or "UE" may include any type of wireless / wired device or any computing device that includes a wireless communication interface.

[0026] As used herein, the term "computer system" refers to any type of interconnected electronic devices, computer devices, or components thereof. Additionally, the term "computer system" or "system" may refer to various components of a computer that are communicatively coupled to one another. Furthermore, the term "computer system" or "system" may refer to multiple computer devices or multiple computing systems that are communicatively coupled to one another and configured to share computing resources or networked resources.

[0027] As used herein, the term "resource" refers to a physical or virtual device, a physical or virtual component within a computing environment, or a physical or virtual component within a specific device, such as a computer device, a mechanical device, a memory space, a processor / CPU time, a processor / CPU usage, a processor and accelerator load, a hardware time or usage, a power supply, an input / output operation, a port or a network socket, a channel / link allocation, throughput, memory usage, storage, a network, a database and an application, a unit of work, etc. "Hardware resources" may refer to computer, storage or network resources provided by physical hardware elements. "Virtualized resources" may refer to computer, storage or network resources provided by a virtualized infrastructure to an application, device, system, etc. The term "network resources" or "communication resources" may refer to resources that a computer device / system can access via a communication network. The term "system resources" may refer to any kind of shared entity that provides a service, and may include computing resources or network resources. System resources may be considered as a set of coherent functions, network data objects or services that can be accessed through a server, wherein such system resources reside on a single host or multiple hosts and can be clearly identified.

[0028] As used herein, the term "channel" refers to any tangible or intangible transmission medium for transmitting data or data streams. The term "channel" may be synonymous or equivalent to "communication channel", "data communication channel", "transmission channel", "data transmission channel", "access channel", "data access channel", "link", "data link", "carrier", "radio frequency carrier" or any other similar term representing a path or medium through which data is transmitted. In addition, as used herein, the term "link" refers to a connection made between two devices for transmitting and receiving information.

[0029] As used herein, the terms "instantiate," "instantiate," and the like refer to the creation of an instance. "Instance" also refers to a specific occurrence of an object, which may occur, for example, during the execution of program code.

[0030] The term "connected" may mean that two or more elements at a common communication protocol layer have an established signaling relationship with each other through a communication channel, link, interface, or reference point.

[0031] As used herein, the term "network element" refers to physical or virtualized equipment or infrastructure for providing wired or wireless communication network services. The term "network element" may be considered synonymous with or referred to as a networked computer, networking hardware, network equipment, network node, virtualized network function, etc.

[0032] The term "information element" refers to a structural element that contains one or more fields. The term "field" refers to a single content of an information element or a data element that contains content. An information element may include one or more additional information elements.

[0033] Figure 1 A network environment 100 according to some embodiments is illustrated. The network environment 100 may include a UE 104 coupled to a base station (BS) 108 of a radio access network (RAN). In some embodiments, the BS 108 is a next generation node B (gNB) providing one or more 3GPP new radio (NR) cells. In other embodiments, the BS 108 is an evolved node B (eNB) providing one or more long term evolution (LTE) cells. The air interface via which the UE 104 and the BS 108 communicate may be compatible with 3GPP technical specifications (TS), such as those defining fifth generation (5G) NR or later system standards (e.g., sixth generation (6G) standards).

[0034] The network 102 (e.g., a system that provides services to the UE 104) may include a core 106 and a BS 108. The network 102 may allocate resources to the UE 104. The resources may be allocated to the UE 104 as network slices (or simply "slices"). A slice may be a logical network created from a shared physical network infrastructure. A slice may span different network domains, such as access, transport, and core, and may be isolated from other slices to ensure security and performance. A slice may provide customized services to a specific application user group, such as enhanced mobile broadband (eMBB), ultra-reliable low latency communications (URLLC), or massive machine type communications (mMTC).

[0035] The resources in a slice may be network elements and functions allocated to the slice to deliver services to the UE 104. The resources may include portions of the radio spectrum, BS 108, routers, switches, servers, virtual machines, containers, software defined networks, and network functions. The resources may be dynamically adjusted based on demand and availability of the slice.

[0036] The resources in a slice can be defined by a network operator or service provider based on the requirements and specifications of the slice. These requirements and specifications may include QoS parameters such as latency, reliability, throughput, availability, or service level agreements (SLAs).

[0037] The network 102 may configure the UE 104 with one or more slices supported by the network 102. The network 102 may also configure the UE 104 with a set of QoS parameters that may define the QoS for a packet data unit (PDU) session 130 within a slice. The network 102 may configure the UE 104 with a network slice selection policy (NSSP) that may guide the UE 104 to select a slice based on factors such as location, time, or service type.

[0038] When UE 104 registers with the network or requests a service requiring a specific slice, network 102 may allocate a slice to UE 104. The process of allocating a slice to UE 104 may be initiated by UE 104 or network 102. The process may be triggered by registration at power-on, mobility, service request, or network reconfiguration.

[0039] In some instances, non-access stratum (NAS) signaling 110 may provide slice configuration to UE 104. NAS signaling 110 may include signaling through the NAS layer in network 102 and UE 102. The NAS layer may be responsible for managing the establishment of communication sessions, including dual connectivity, and maintaining continuous communication with UE 104 during its mobility. NAS signaling 110 signaling may be used to request, negotiate, confirm, modify, or release network resources or slices. NAS signaling 110 signaling may convey information about QoS parameters that may be required or provided for each slice, such as latency, reliability, or throughput. NAS signaling 110 signaling may be used to report or monitor the status or performance of network resources or slices.

[0040] NAS signaling 110 may configure one or more network slice access groups (NSAGs). NSAGs may allow UE 104 to access different network slices based on its subscription and service requirements. For example, UE 104 may receive NSAG information during a registration process or when UE 104 requests a PDU session 130. An access and mobility management unit (AMF) of core 106 may send a UE configuration update command or a registration accept message, which may include a NSAG information element (IE). NSAG information may provide a list of NSAGs that the UE may access based on its subscription and service requirements.

[0041] In some instances, access stratum (AS) signaling 150 can provide slice configuration to UE 104. AS signaling 150 can pass through the AS layer at BS 108 and UE 104. The AS layer can be responsible for radio resource control (RRC), packet data convergence protocol (PDCP), radio link control (RLC), medium access control (MAC), and physical layer (PHY) aspects. RRC can be responsible for controlling the configuration and state of radio resources and radio bearers between UE 104 and network 102. RRC can manage the mobility, security, and measurement procedures of the UE.

[0042] The RRC may send a system information block (SIB) 120 to the UE 104. The SIB 120 may contain configuration IEs about a cell or network. The SIB 120 is transmitted via AS signaling 150. The BS 108 may transmit the SIB 120 via a broadcast or control channel. For example, the BS 108 may send the SIB 120 to the UE 104 via a physical broadcast channel (PBCH) or a physical downlink shared channel (PDSCH).

[0043] UE 104 may receive a slice configuration from NAS signaling 110 or AS signaling 150. The slice configurations received from NAS signaling 110 or AS signaling 150 may overlap, complement, or contradict each other.

[0044] In one embodiment, the UE 104 may implement slice prioritization based on configuration information provided by SIB4 and SIB 16. The UE 104 may develop a slice priority network configuration database based on SIB4 and SIB 16 for cell reselection.

[0045] In one embodiment, UE 104 may implement slice prioritization based on configuration information provided by SIB4, SIB16 and NSAG information provided by NAS. UE may implement a slice prioritization scheme based on SIB4, SIB16 and NSAG.

[0046] In one embodiment, the UE 104 may generate a dynamic slice priority decision table. The dynamic slice priority decision table may include a UE optimization decision for each possible slice combination. The UE optimization decision associated with a slice combination may include steps that the UE 104 may take to map the PDU session to the requested slice within the associated slice combination.

[0047] For example, in a network supporting two slices a and b, the dynamic slice priority decision table may include UE optimization decisions for supporting slice combinations (a) (e.g., an application or service requests slice a), (b) (e.g., an application or service requests slice b), and (a, b) (e.g., an application or service requests two slices a and b).

[0048] It is desirable to construct a network slice selection or reselection process, for example, a slice priority network configuration based on the AS and NAS configuration. The UE 104 may use the slice priority network configuration to determine a cell or frequency to reselect for accessing a particular slice. The UE 104 may use the slice selection or reselection process to determine when or how to initiate a new PDU session or modify an existing PDU session.

[0049] Figure 2 Some aspects of a NSAG 200 according to some embodiments are shown. A NSAG is an identifier for a group of associated network slices. In some embodiments, the core network may send a NAS message to configure the NSAG. For example, a UE Configuration Update Command or Registration Accept message may include the NSAG Information IE 210. The UE may use the NSAG Information IE 210 to select the appropriate network slice when registering or requesting a PDU session.

[0050] The NSAG information IE 210 may include a NSAG IE identifier (IEI). The NSAG IEI may be one octet, for example, octet 1 of the NSAG information IE 210, that identifies the NSAG IE in the NAS message.

[0051] The NSAG information IE 210 may include a field indicating the length of the IE content. For example, the field “Length of NSAG information content” in octets 2 and 3 in the NSAG information IE 210 may indicate the length of the NSAG information IE 210.

[0052] The NSAG information IE 210 may include one or more NSAGs, such as NSAG 1 in octets 4 to mm, NSAG 2 in octets mm+1 to nn, and NSAG x in octets uu+1 to vv.

[0053] NSAG 220 is an example of each NSAG part of NSAG information IE 210. NSAG 220 may include a field indicating the length of NSAG. For example, when NSAG 220 indicates NSAG 1 of NSAG information IE 210, the element "Length of NSAG" in octets 4 and 5 may indicate the length of NSAG 1.

[0054] NSAG 220 may include an NSAG identifier, for example, an NSAG identifier associated with NSAG 1 of NSAG information IE 210 in octet 6. An NSAG identifier is a value that identifies a specific NSAG element within an NSAG information IE. For example, when NSAG 220 represents NSAG 1, octet 6 of NSAG information IE 210 may contain the NSAG identifier of NSAG 220.

[0055] NSAG 220 may include a single network slice selection assistance information (S-NSSAI) list. In one example, the S-NSSAI is a value that identifies one or a group of network slices that are available for the PDU session associated with NSAG 220. For example, when NSAG 220 represents NSAG 1, octets 7 to jj of NSAG Information IE 210 may contain the S-NSSAI list of NSAGs of NSAG 220.

[0056] NSAG 220 may include a NSAG priority field. NSAG priority is a value that may indicate the relative priority of a NSAG among other NSAGs. For example, when NSAG 220 represents NSAG 1, octet jj+1 of NSAG Information IE 210 may contain the NSAG priority of NSAG 220.

[0057] NSAG 220 may include a list of tracking area identifiers (TAIs). The NSAG 220 TAI list may be a subset of the configured TAI list of the UE. The network may assign the TAI list to the UE. Each TAI may identify a tracking area (TA), i.e., a geographical area in which the network may locate the UE without paging. The TAI list of NSAG 220 may be associated with a subset of the configured TAs. When the UE moves to a different tracking area, the UE may use the TAI list to decide whether to perform a PDU session modification procedure to change the NSAG used for the PDU session.

[0058] An NSAG association with a set of network slices may be valid in one or more TAs. A TAI list may identify TAs in which the NSAG association with the network slices identified by the S-NSSAI list is valid.

[0059] The S-NSSAI list of NSAG 230 is an example of the S-NSSAI list of the NSAG of NSAG 220. A field such as the length of the S-NSSAI list of the NSAG may determine the size of the S-NSSAI list of NSAG 230. For example, when the S-NSSAI list of NSAG 230 represents the S-NSSAI list of the NSAG of NSAG 1, octet 7 of the NSAG information IE 210 contains the length of the S-NSSAI list of the NSAG.

[0060] The S-NSSAI list of NSAG 230 may include one or more S-NSSAIs, for example, S-NSSAI values ​​1 to y. The S-NSSAI is used to indicate the network slices available to the UE in the specified NSAG.

[0061] In some instances, the S-NSSAI may be associated with at most one NSAG for random access or at most one NSAG for cell reselection with a TA. The S-NSSAI may be associated with different NSAGs in different TAs.

[0062] Figure 3 Some aspects of slice prioritization 300 according to some embodiments are shown. Slice prioritization 300 includes an example of slice configuration information that a UE may receive. Slice prioritization 300 may include a network deployment example, where the network deployment 310 includes an available S-NSSAI. The UE is provided with NAS slice configuration NSAG 345-1 to 345-k in the NSAG information IE 350 and with AS slice configuration in SIB16 320 and SIB4 330. The NSAG information IE 350 may be provided by NAS signaling. SIB16 320 and SIB4 330 may be provided by AS signaling.

[0063] During the registration process, the UE may send a registration request message. The registration request may include information related to a PDU session or slice. The registration request message may include the requested NSSAI, which may be a list of S-NSSAIs that the UE requests to use. The registration request message may include the status of the PDU session, which indicates whether the PDU session is active or pending in the UE. The registration request message may include a list of PDU sessions to be activated, which includes a list of PDU session identifiers (IDs) and corresponding S-NSSAIs that the UE requests to be activated.

[0064] For example, the UE may send a NAS registration request message to the AMF, which may include a subscription hidden identifier (SUCI) and network slice selection assistance information (NSSAI). The AMF may verify the identity and subscription of the UE and assign a globally unique temporary identifier (GUTI) and an allowed NSSAI to the UE.

[0065] The AMF may send slice configuration information to the UE. For example, the AMF may send a NAS UE configuration update command message, a registration accept message. The NAS UE configuration update command message may include an NSAG information IE 350, which may include NSAG information 345-1 to 345-k. The NSAG information IE 350 may be Figure 2 Example of NSAG information IE 210 in . When the UE receives a registration accept message from the AMF, the registration process is completed. For example, the UE may receive a NAS registration accept message from the AMF.

[0066] In one instance, the network can support the configured slices in the network deployment 310. For example, the network deployment 310 can include S-NSSAI-a, b, c, and d. In one example, S-NSSAI-a can be associated with an eMBB slice, S-NSSAI-b can be associated with a URLLC slice (e.g., a slice supporting URLLS QoS requirements), S-NSSAI-c can be associated with a proprietary slice, and S-NSSAI-d can be associated with a gaming slice. The network can also configure several NSAGs based on the network deployment 310.

[0067] NAS signaling may provide the UE with an NSAG information IE 350. The NSAG information IE 350 may include NSAG information 345-1 to k. Each NSAG information (e.g., NSAG information 345-1) may include an NSAG ID, a priority, an allowed S-NSSAI, or an allowed tracking area. The allowed S-NSSAI includes a slice or S-NSSAI associated with the NSAG. The allowed tracking area may indicate a tracking area in which the associated S-NSSAI is allowed.

[0068] As described above, the UE may send a registration request. In the registration request message, the UE may request one or more S-NSSAIs or PDUs associated with one or more S-NSSAIs. Upon completion of the registration process, the network may send a NAS registration accept 340 message to the UE. The registration accept 340 message may include a list of allowed S-NSSAIs or a list of rejected S-NSSAIs. The rejected NSSAI information element may indicate the S-NSSAI that the UE requested in the registration request message and that the network has rejected. The network may not reject, reject some, or reject all requested S-NSSAIs. The UE may use the rejected NSSAI or allowed NSSAI IE to update its allowed NSSAI. The UE may use the rejected NSSAI IE to decide whether to perform a network slice selection assistance process to request a different set of S-NSSAIs from the network.

[0069] SIB4 330 may be used for inter-frequency reselection. SIB4 330 may include a list of DL frequencies 335-1 to 335-m, generally identified as DL frequencies 335. DL frequencies 335 (e.g., DL frequency 335-1) may be associated with a frequency band indicator (FBI) and a cell reselection priority. DL frequencies 335 may also include a cell reselection threshold.

[0070] After the registration process is completed, the UE is connected to a serving cell. The serving cell may be one of the DL frequencies 335. The serving cell may be a cell that provides radio resources to the UE. For example, the serving cell may be a primary cell (PCell) or a secondary cell (SCell), depending on whether it serves a primary component carrier (PCC) or a secondary component carrier (SCC) in carrier aggregation.

[0071] In some instances, the UE may measure the reference signal received power (RSRP) or reference signal received quality (RSRQ) of the serving cell and compare it with the condition. If the serving cell measurement does not meet the condition, the UE may perform inter-frequency measurement on the frequency indicated by SIB4330 and select a suitable cell with higher priority or better quality.

[0072] In some instances, the UE may receive SIB4 330 via RRC signaling. SIB4 330 may include an interFreqCarrierFreqList, which may include a list of target frequencies for inter-frequency cell reselection. The interFreqCarrierFreqList may include an interFrqCarrierFreqInfo IE, which may contain an IE for each target frequency for inter-frequency cell reselection. For example, the interFreqCarrierFreqInfo may include a dl-CarrierFreq that may indicate a target frequency for inter-frequency cell reselection. The dl-CarrierFreq may be expressed as an absolute radio frequency channel number (ARFCN) value for an NR band. It may indicate a center frequency of resource block 0 of a downlink component carrier. The dl-CarrierFreq may be associated with a cellReselectionPriority IE indicating a cell reselection priority associated with the dl-CarrierFreq.

[0073] SIB16 320 may be used for slice-based inter-frequency reselection. SIB16 320 may include a list of downlink (DL) frequencies 325-1 to 325-n, generally referred to as DL frequencies 325. DL frequencies 325 (e.g., DL frequency 325-1) may include a frequency indicator, an NSAG-ID, an NSAG reselection priority, a list of allowed cells, or a list of excluded cells. DL frequency 325 associates a frequency band identified by a frequency indicator with a NSAG identified by an NSAG-ID. The UE may use the NSAG reselection priority as a priority for reselecting a frequency of a cell belonging to the NSAG.

[0074] In some examples, DL frequency 325-1 of SIB16 320 may be associated with a serving cell or serving frequency. Other DL frequencies in SIB16 320 may be mapped to adjacent frequencies 335 in SIB4 330. In one example, DL frequency 325-2 of SIB16 320 may be mapped to adjacent frequency 335-1, and the next DL frequency of SIB16 320 may be mapped to the next adjacent frequency in SIB4 330.

[0075] For example, SIB16 320 received via RRC signaling may include a freqPriorityListSlicing information element. freqPriorityListSlicing may include a dl-ImplicitCarrierFreq IE associated with a slice in a sliceInfoList IE of a sliceInfo IE. The sliceInfoList IE may include nsag-IdentityInfo, nsag-CellReselectionPriority, sliceAllowedCellListNR, or sliceExcludedCellListNR. dl-ImplicitCarrierFreq may indicate the DL carrier frequency associated with the slice in the sliceInfoList. The frequency may be signaled implicitly; a value of 0 may correspond to the serving frequency, a value of 1 may correspond to the first frequency indicated by the InterFreqCarrierFreqList in SIB4 330, and so on. sliceAllowedCellListNR may include a list of cells allowed for the slice. The listed cells may support the corresponding NSAG-frequency pairs, while the unlisted cells may not support the corresponding NSAG-frequency pairs.

[0076] Similarly, sliceExcludedCellListNR may include a list of cells that are excluded for slicing. The listed cells do not support the corresponding NSAG-frequency pair, and the unlisted cells may support the corresponding NSAG-frequency pair. sliceInfo may include a sliceCellListNR IE, which may contain a list of cells that are allowed or excluded for slicing. If not present, it may imply that all cells support the corresponding NSAG-frequency pair.

[0077] The UE may receive the redundant information in SIB4 330, SIB16 320, and NSAG Information IE 350. When the UE invokes an application or service that requires a specific slice, the UE may need to implement a policy or criteria to decide to reselect a physical cell identity (PCI) or frequency for accessing the specific slice. The implementation may also provide UE criteria by which the UE may determine whether to initiate a new PDU session for the invoked application or service based on the AS and NAS configuration provided by SIB4, SIB16, or NAS Registration Accept or UE Configuration Update Command messages.

[0078] In some instances, the UE may receive the NSAG information IE 350 via NAS signaling. The NSAG information IE 350 may provide NSAG information 345-1 in which the NSAG ID is associated with a priority. The UE may also receive a cell level configuration SIB16 320 that may include a DL frequency 325-1, which associates the NSAG-ID with the NSAG reselection priority. If the NSAG ID of the NSAG information 345-1 is the same as the NSAG-ID of the DL frequency 325-1, the UE may select the NSAG priority provided by the NAS signaling, e.g., the priority IE in the NSAG information 345-1, for the NSAG.

[0079] Figure 4 Some aspects of slice prioritization 400 according to some embodiments are shown. Specifically, slice prioritization 400 is an example of a specific implementation of slice prioritization based on broadcast information in SIB4 430 and SIB16 410.

[0080] In this example, it is assumed that four S-NSSAIs have been deployed, for example, S-NSSAI-a, S-NSSAI-b, S-NSSAI-c, and S-NSSAI-d of network deployment 410. S-NSSAI-a may be a default eMBB slice, S-NSSAI-b may be a URLLC slice, S-NSSAI-c may be a proprietary slice, and S-NSSAI-d may be a gaming slice. In some instances, the eMBB slice is the default slice and is allowed in all frequencies and TAs. A default PDU session may be associated with an eMBB slice.

[0081] In addition, assume that there are three tracking areas (TAs), for example, TA1, TA2, and TA3. The UE powers on in TA1 and sends a NAS Registration Request message. In the Registration Request message, the UE requests NSSAI a, b, c, and d for 4 slices, for example, S-NSSAI ad. The UE receives a list of allowed and rejected NSSAIs in a NAS Registration Accept message. The UE receives an allowed NSSAI, indicating that S-NSSAI a, b, and c are allowed, and a rejected NSSAI, indicating that S-NSSAI d is rejected in TA1 but allowed in TA2 and TA3. In some instances, if the allowed NSSAI is not associated with the list for the TA, the UE may assume that the allowed NSSAI is allowed in the current TA in which the UE is registered.

[0082] The UE receives SIB4 430, which configures three frequencies: n41 band with priority 6, n256 band with priority 2, and n1 band with priority 3.

[0083] The UE receives SIB16 420. The SIB16 420 message includes two DL frequencies: DL F0 (serving frequency of n78 band) and DL F1 (SIB4 frequency 1, eg, n41 band).

[0084] The UE may create a configuration database based on the information received from the complete NAS Registration message and the AS RRC SIB4 430 and SIB16 420 messages.

[0085] Slice priority network configuration database 480 is an example of a slice priority network configuration database. Column 440 includes deployed S-NSSAI ad. Column 440 is obtained from the NSSAI requested by the registration request. Column 445 indicates whether the corresponding slice is allowed or rejected. Column 450 lists the TA in which the corresponding slice is allowed. The UE receives the information in columns 445 and 450 from NAS signaling, such as a registration acceptance or a UE configuration update command. Column 455 includes frequency reselection priorities based on SIB4 430. These priorities may not be associated with the slices in column 440. Column 460 includes frequency reselection priorities based on SIB16 420. Column 465 includes cells in which S-NSSAI is allowed.

[0086] Similarly, column 470 includes cells where the S-NSSAI is excluded. Columns 465 and 470 are obtained from the allowed cells and excluded cells associated with DLFO (serving cell) in SIB16 420. Each row contains information associated with the S-NSSAI in that row.

[0087] The following scenario describes how a UE may utilize the slice priority network configuration database 480. The following scenario is an example of a dynamic slice priority decision table entry.

[0088] In scenario 1, the UE invokes an application or service that requires S-NSSAI-a and S-NSSAI-b. S-NSSAI-a is the default eMBB slice, which is unrestricted and allowed in all TAs and PCIs.

[0089] For applications or services requesting S-NSSAI-b, the UE uses the information in the slice priority network configuration database 480 associated with S-NSSAI-b, for example, the third row of the slice priority network configuration database 480. Column 445 indicates that the UE is allowed to use S-NSSAI-b. Column 450 indicates that S-NSSAI is allowed in the current TA (i.e., TA1).

[0090] The UE can check whether there is any currently active PDU Session mapped to S-NSSAI-b. If there is currently an active PDU Session, the UE can decide whether to modify the PDU Session or create a new PDU Session. If an active PDU Session does not exist, the UE can create a new PDU Session associated with S-NSSAI-b.

[0091] Assume that the UE decides to create a new PDU session using the slice priority network configuration database 480. In this case, the UE may check whether the current service PCI is within the range indicated by column 465, for example, between 400-500. If the current service PCI is within the range, for example, between 400-500, the UE may initiate a new PDU session. However, if the current service PCI is not within the range indicated by column 465, the UE may check neighboring cells.

[0092] If the PCI range is not between 400-500, the UE may check neighbor cell measurements if there are any neighbor cells in the same TA (i.e., TA1). If there are any PCIs in this range in TA1, the UE may reselect to the PCI at n78 frequency (n78 is the serving frequency associated with DL frequency F0 in SIB16 420). The UE searches for cells in the frequency at n78 for reselection. Assuming that the UE cannot find any cell reselection candidates at n78, based on column 460 and the priority configuration based on SIB16 420, the UE searches for candidates at DL frequency F1. DL frequency F1 is associated with the first frequency band in SIB4 430. Therefore, the UE will search for candidate cells at the n41 frequency band for reselection. The UE may not search other frequency bands not included in SIB16 420.

[0093] If the UE successfully reselects a cell that supports S-NSSAI-b, the UE may establish a new PDU session mapped to S-NSSAI-b and may reestablish a PDU session mapped to S-NSSAI-a. If the UE cannot find a cell that supports S-NSSAI-b and the current serving cell does not support S-NSSAI-b, S-NSSAI-b may not be supported. To support the invoked application or service, the UE may perform additional procedures, such as Figure 5 and the procedures provided in its description.

[0094] In scenario 2, the UE invokes an application or service that requires S-NSSAI-a and S-NSSAI-c. S-NSSAI-a is the default eMBB slice, which is unrestricted and allowed in all TAs and PCIs.

[0095] For applications or services requesting S-NSSAI-c, the UE uses information in the slice priority network configuration database 480 associated with S-NSSAI-c, for example, the fourth row of the slice priority network configuration database 480. Column 445 indicates that the UE is allowed to use S-NSSAI-c. Column 450 indicates that S-NSSAI is allowed in the current TA (i.e., TA1).

[0096] The UE can check whether there is any currently active PDU session mapped to S-NSSAI-c. If there is currently an active PDU session, the UE can decide whether to modify the PDU session or create a new PDU session. If an active PDU session does not exist, the UE can create a new PDU session associated with S-NSSAI-c.

[0097] Assume that the UE decides to create a new PDU session using the slice priority network configuration database 480. In this case, the UE may check whether the current serving PCI (e.g., the PCI of the current serving cell) is within the range indicated by column 465 (e.g., between 1-1024) and within the range indicated by the cells excluded in column 470 (e.g., between 400-500). If the current serving PCI is within the range, e.g., not between 400-500, the UE may initiate a new PDU session. However, if the current serving PCI is not within the range indicated by columns 465 and 470, the UE may check neighboring cells.

[0098] If the PCI range is between 400-500, the UE may check neighbor cell measurements if there are any neighbor cells in the same TA (i.e., TA1). If there are any PCIs in this range in TA1, the UE may reselect to the PCI at the n78 frequency (n78 is the serving frequency associated with the DL frequency F0 in SIB16 420). The UE searches for cells in the frequency at n78 for reselection. Assuming that the UE cannot find any cell reselection candidates at n78, based on column 460 and the priority configuration based on SIB16 420, the UE searches for candidates at DL frequency F1. DL frequency F1 is associated with the first frequency band in SIB4 430. Therefore, the UE will search for candidate cells at the n41 frequency band for reselection. The UE may not search other frequency bands not included in SIB16 420.

[0099] If the UE successfully reselects a cell that supports S-NSSAI-c, the UE may establish a new PDU session mapped to S-NSSAI-c and may reestablish a PDU session mapped to S-NSSAI-a. If the UE cannot find a cell that supports S-NSSAI-c and the current serving cell does not support S-NSSAI-c, S-NSSAI-c may not be supported. To support the invoked application or service, the UE may perform additional procedures, such as Figure 5 and the procedures provided in its description.

[0100] In scenario 3, the UE invokes an application or service that requires S-NSSAI-a, S-NSSAI-b, and S-NSSAI-c. S-NSSAI-a is the default eMBB slice, which is not restricted and is allowed in all TAs and PCIs.

[0101] For S-NSSAI-b, column 465 of the slice priority network configuration database 480 indicates that the allowed PCI range in the current serving cell must be in the range of 400-500. Column 470 of the slice priority network configuration database 480 also indicates that the PCI of the cell providing S-NSSAI-c cannot be in the range of 400-500. Therefore, S-NSSAI-b and S-NSSAI-c in the current serving frequency are mutually exclusive. Based on the current network configuration in the slice priority network configuration database 480, S-NSSAI-b and S-NSSAI-c cannot operate at the same time, even if they are part of the allowed NSSAI.

[0102] The UE may make a decision and identify the more critical slice. For example, the UE may identify the critical slice based on an application running in the foreground or background or whether the screen is turned on or off. For example, the UE may determine that S-NSSAI-b is more critical. The UE may find a cell that supports S-NSSAI-a and S-NSSAI-b and a different cell that supports S-NSSAI-a and S-NSSAI-c. The UE may switch between the two cells. In another example, the UE may discard the less critical slice and find a cell that supports the more critical slice.

[0103] In scenario 4, the UE invokes an application or service that requires S-NSSAI-d. The slice priority network configuration database 480 in column 445 indicates that slice d is rejected in the current TA (ie, TA1), but is allowed in TA2 and TA3.

[0104] The UE may measure neighboring cells in TA2 to identify potential candidate PCIs. The UE may check if any current PDU sessions can continue in PCI in TA2. The UE may reselect to PCI at frequency n78, followed by n41 in TA2 or TA3. The UE will not prefer any other frequency or band not included in SIB16420.

[0105] As part of the reselection process, the UE may send a NAS Registration Request (Mobility) message with the S-NSSAI-d included in the Requested NSSAI IE. The UE may update the Slice Priority Network Configuration Database 480 based on the Allowed and Rejected IEs in the Registration Accept message.

[0106] Figure 5 An operation flow / algorithm structure 500 according to some embodiments is shown. The operation flow / algorithm structure 500 may be implemented by an entity in a UE (e.g., UE 104 or UE 1400) or a component thereof (e.g., processing circuit 1404). The UE has completed registration and currently camps on a serving cell of a frequency band in a TA. The UE has received NAS and AS configurations related to slices and cell reselection priorities, and the UE has developed a slice priority network configuration database.

[0107] The operation flow / algorithm structure 500 may include establishing a default PDU session mapped to a default eMBB slice at 502. The default PDU session may always be active.

[0108] The operational flow / algorithm structure 500 may include: at 504, calling a service or application A that requires slice S.

[0109] The operation flow / algorithm structure 500 may include, at 506, determining whether the called service or application A requires a slice S that is different from the default eMBB slice. The UE may make this determination based on a UE routing policy (URSP) rule. The URSP rule allows the UE to select the best route for its data traffic based on rules configured by a network or application server. Based on the determination that the called service or application requires a slice different from the default eMBB, the operation flow / algorithm structure 500 proceeds to step 508 following the "yes" branch. Based on the determination that the called service or application does not require a slice other than the default eMBB, the operation flow / algorithm structure 500 proceeds to step 520 following the "no" branch.

[0110] The operational flow / algorithm structure 500 may include: at 508, determining whether slice S is allowed or rejected. The UE may send a list of slices in a registration request message, and the network may send a list of allowed or rejected slices to the UE in a registration accept message. The UE determines whether slice S is in the list of allowed slices or rejected slices. Based on the determination that slice S is allowed, the operational flow / algorithm structure 500 proceeds to step 510 following the "yes" branch. Based on the determination that slice S is not allowed, for example, S is in the list of rejected slices, the operational flow / algorithm structure 500 proceeds to step 522 following the "no" branch.

[0111] The operation flow / algorithm structure 500 may include: at 510, determining whether there is an active PDU session mapped to slice S. Based on the determination that there is an active PDU session mapped to slice S, the operation flow / algorithm structure 500 proceeds to step 524 following the "yes" branch. Based on the determination that no active PDU session is mapped to slice S, the operation flow / algorithm structure 500 proceeds to step 512 following the "no" branch.

[0112] The operation flow / algorithm structure 500 may include: at 512, determining whether slice S is allowed in the current TA. Based on the slice priority network configuration database, the UE may determine whether slice S is allowed in the current TA. Based on the determination that slice S is allowed in the current TA, the operation flow / algorithm structure 500 proceeds to step 514 following the "yes" branch. Based on the determination that slice S is not allowed in the current TA, the operation flow / algorithm structure 500 proceeds to step 532 following the "no" branch.

[0113] The operation flow / algorithm structure 500 may include: at 514, determining whether slice S is allowed in the current frequency or frequency band. Based on the slice priority network configuration database, the UE may determine whether slice S is allowed in the current frequency or frequency band. Based on the determination that slice S is allowed in the current frequency or frequency band, the operation flow / algorithm structure 500 proceeds to step 516 following the "yes" branch. Based on the determination that slice S is not allowed in the current frequency or frequency band, the operation flow / algorithm structure 500 proceeds to step 526 following the "no" branch.

[0114] The operation flow / algorithm structure 500 may include: at 516, determining whether slice S is allowed in the current PCI. Based on the slice priority network configuration database, the UE may determine whether slice S is allowed in the current PCI. Based on the determination that slice S is allowed in the current PCI, the operation flow / algorithm structure 500 proceeds to step 518 following the "yes" branch. Based on the determination that slice S is not allowed in the current PCI, the operation flow / algorithm structure 500 proceeds to step 528 following the "no" branch.

[0115] The operation flow / algorithm structure 500 may include: at 518, initiating a new PDU session for slice S. The UE may establish a new PDU session mapped to slice S using a session establishment request procedure.

[0116] The operational flow / algorithm structure 500 may include: at 520, mapping the data traffic of the called application or service A to an existing PDU session mapped to slice S.

[0117] The operation flow / algorithm structure 500 may include: at 522, determining whether slice S is allowed in a neighboring TA. Based on the slice priority network configuration database, the UE may determine whether slice S is allowed in a neighboring TA. Based on the determination that slice S is allowed in a neighboring TA, the operation flow / algorithm structure 500 proceeds to step 532 following the "yes" branch. Based on the determination that slice S is not allowed in a neighboring TA, the operation flow / algorithm structure 500 proceeds to step 530 following the "no" branch.

[0118] The operational flow / algorithm structure 500 may include: at 524, determining whether to modify an existing PDU session mapped to slice S or to create a new PDU session for data traffic associated with the called application or service A. If the network supports slice-AMBR (AMBR stands for aggregate maximum bit rate) for slice S, the UE may determine to modify the existing PDU session. If the called application or service A requires only non-GBR (GBR stands for guaranteed bit rate) quality of service (QoS), the UE may modify the existing PDU session. If the current PDU session does not support reflective QoS, and the requested application or service A requires reflective QoS, the UE may create a new PDU session. In reflective QoS, the UE may derive QoS rules for the uplink (UL) based on DL traffic. In reflective QoS, the UE may dynamically change the mapping of UL data traffic among several QoS flows within the same PDU session by changing the header without modifying the PDU session.

[0119] In some instances, one or more QoS flows may be mapped to one PDU session. When the UE determines to modify an existing PDU session mapped to slice S, the UE may initiate mapping of a new QoS flow associated with data traffic of the invoked application or service A to the existing PDU session of slice S.

[0120] The operation flow / algorithm structure 500 may include: at 526, determining whether the UE is able to measure cells in neighboring frequencies supporting slice S. The UE may determine whether slice S is allowed in neighboring frequencies supporting slice S based on the slice priority network configuration database. Based on the determination that the UE is able to measure cells in neighboring frequencies supporting slice S, the operation flow / algorithm structure 500 proceeds to step 534 following the "yes" branch. Based on the determination that the UE cannot measure cells in neighboring frequencies supporting slice S, the operation flow / algorithm structure 500 proceeds to step 530 following the "no" branch.

[0121] The operation flow / algorithm structure 500 may include: at 528, determining whether the UE is able to measure neighboring cells in the same frequency but not in the exclusion range supporting slice S. The UE may determine whether slice S is allowed in neighboring cells in the same frequency but not in the exclusion range supporting slice S based on the slice priority network configuration database. Based on the determination that the UE is able to measure neighboring cells in the same frequency but not in the exclusion range supporting slice S, the operation flow / algorithm structure 500 proceeds to step 536 following the "yes" branch. Based on the determination that the UE cannot measure neighboring cells in the same frequency but not in the exclusion range supporting slice S, the operation flow / algorithm structure 500 proceeds to step 530 following the "no" branch.

[0122] The operation flow / algorithm structure 500 may include: at 530, determining whether the called application or service A requires any critical QoS that is not supported by the default slice. Based on the determination that the called application or service A requires critical QoS that is not supported by the default slice, the operation flow / algorithm structure 500 proceeds to step 538 following the "yes" branch. Based on the determination that the called application or service A does not require any critical QoS that is not supported by the default slice, the operation flow / algorithm structure 500 proceeds to step 520 following the "no" branch.

[0123] The operation flow / algorithm structure 500 may include: at 532, determining whether the current TA has any neighboring cells in which slice S is allowed. The UE may determine whether the current TA has any neighboring cells in which slice S is allowed based on the slice priority network configuration database. Based on the determination that the current TA has neighboring cells in which slice S is allowed, the operation flow / algorithm structure 500 proceeds to step 540 following the "yes" branch. Based on the determination that the current TA does not have any neighboring cells in which slice S is allowed, the operation flow / algorithm structure 500 proceeds to step 530 following the "no" branch.

[0124] The operational flow / algorithm structure 500 may include obtaining or determining a list of measured neighboring frequencies and PCIs at 534. The operational flow / algorithm structure 500 proceeds to step 544.

[0125] The operation flow / algorithm structure 500 may include obtaining or determining a measured neighboring PCI list at 536. The operation flow / algorithm structure 500 proceeds to step 546.

[0126] The operational flow / algorithm structure 500 may include, at 538, rejecting the invoked application or service A. The UE may provide an appropriate indication to the end user, such as a pop-up message.

[0127] The operation flow / algorithm structure 500 may include: at 540, determining whether all active PDU sessions mapped to other slices can continue in the new TA. The UE may determine whether all active PDU sessions mapped to other slices can continue in the new TA based on the slice priority network configuration database. Based on the determination that all active PDU sessions mapped to other slices can continue in the new TA, the operation flow / algorithm structure 500 proceeds to step 548 following the "yes" branch. Based on the determination that not all active PDU sessions mapped to other slices can continue in the new TA, the operation flow / algorithm structure 500 proceeds to step 542 following the "no" branch.

[0128] The operation flow / algorithm structure 500 may include: at 542, determining a current PDU session or slice that is critical compared to the new slice S requested by the user. The UE may use a slice priority based on usage or impact to determine a current PDU session or slice that is critical compared to the new slice S requested by the user. The UE may map a non-critical or low-impact PDU session to a default slice (e.g., an eMBB slice), which may be supported in all cells, PCIs, frequencies, bands, or TAs. The following examples describe various aspects of slice priority based on usage or impact.

[0129] For example, a dormant PDU session or a PDU session with minimal usage may be assigned a low priority. Slices or PDU sessions that can be mapped to a default slice (e.g., an eMBB slice) may be considered low impact and assigned a low priority. The UE may use a PDU release timer to track completed applications or services, but the associated PDU session is still active. The UE may mark these PDU sessions or slices as low priority. The UE may use the assigned priority to determine whether the current PDU session or slice is critical compared to the slice S requested by the user. The UE may map a non-critical, low priority or low impact PDU session to a default slice, such as an eMBB slice, which may be supported in all cells, PCIs, frequencies, bands or TAs.

[0130] The operational flow / algorithm structure 500 may include: at 544, determining whether all active PDU sessions mapped to other slices can continue in any frequency or PCI from the list of measured adjacent frequencies and PCIs. The UE may determine whether all active PDU sessions mapped to other slices can continue in any frequency or PCI from the list of measured adjacent frequencies and PCIs based on the slice priority network configuration database. Based on the determination that all active PDU sessions mapped to other slices can continue in a frequency or PCI from the list of measured adjacent frequencies and PCIs, the operational flow / algorithm structure 500 proceeds to step 550 following the "yes" branch. Based on the determination that not all active PDU sessions mapped to other slices can continue in any frequency or PCI from the list of measured adjacent frequencies and PCIs, the operational flow / algorithm structure 500 proceeds to step 542 following the "no" branch.

[0131] The operational flow / algorithm structure 500 may include: at 546, determining whether all active PDU sessions mapped to other slices can continue in any PCI from the list of measured PCIs. The UE may determine whether all active PDU sessions mapped to other slices can continue in any PCI from the list of measured PCIs based on the slice priority network configuration database. Based on the determination that all active PDU sessions mapped to other slices can continue in the PCI from the list of measured PCIs, the operational flow / algorithm structure 500 proceeds to step 552 following the "yes" branch. Based on the determination that not all active PDU sessions mapped to other slices can continue in any PCI from the list of measured PCIs, the operational flow / algorithm structure 500 proceeds to step 542 following the "no" branch.

[0132] The operation flow / algorithm structure 500 may include: at 548, reselecting to a neighboring cell in the new TA. The UE may send a registration request including a type IE indicating a mobility update and a requested NSSAI IE to add slices from a previously rejected NSSAI to an existing allowed NSSAI list. Based on the allowed NSSAI in the registration accept message, the UE may populate or update a slice priority network configuration database or a dynamic slice priority decision table. The UE may initiate establishment of a new PDU session for the new slice S via a PDU session establishment request procedure.

[0133] The operation flow / algorithm structure 500 may include: At 550, performing inter-frequency reselection for a candidate neighboring cell or frequency. The UE may reestablish an active or existing PDU session in the new cell or frequency. The UE may initiate a new PDU session for the new slice S via a PDU session establishment request procedure. The UE may populate or update a slice priority network configuration database or a dynamic slice priority decision table.

[0134] The operation flow / algorithm structure 500 may include: At 552, performing intra-frequency reselection to a candidate neighboring cell or frequency. The UE may reestablish an active or existing PDU session in the new cell or frequency. The UE may initiate a new PDU session for the new slice S via a PDU session establishment request procedure. The UE may populate or update a slice priority network configuration database or a dynamic slice priority decision table.

[0135] Figure 6 Some aspects of slice prioritization 600 according to some embodiments are shown. Aspects of slice prioritization 600 include examples of slice configuration information that a UE may receive. The UE may receive information related to network deployment 610, inter-frequency reselection information in SIB4 630, inter-frequency slice-based reselection information in SIB16 620, and NSAG information 640. The network deployment 610 and NSAG information 640 may be provided by NAS signaling, and SIB4 630 and SIB16 620 may be provided by AS RRC signaling.

[0136] In this example, it is assumed that four S-NSSAIs have been deployed, for example, S-NSSAI-a, S-NSSAI-b, S-NSSAI-c, and S-NSSAI-d of network deployment 610. S-NSSAI-a may be a default eMBB slice, S-NSSAI-b may be a URLLC slice, S-NSSAI-c may be a proprietary slice, and S-NSSAI-d may be a gaming slice. In some instances, the eMBB slice is the default slice and is allowed in all frequencies and TAs. A default PDU session may be associated with an eMBB slice.

[0137] In addition, assume that there are three tracking areas (TAs), for example, TA1, TA2, and TA3. The UE powers on in TA1 and sends a NAS Registration Request message. In the Registration Request message, the UE requests NSSAI a, b, c, and d for 4 slices, for example, S-NSSAI ad. The UE receives a list of allowed and rejected NSSAIs in the NAS Registration Accept message. Via NAS signaling, the UE receives allowed NSSAIs and rejected NSSAIs. The allowed NSSAI indicates that S-NSSAI a, b, and c are allowed, and the rejected NSSAI indicates that S-NSSAI d is rejected in TA1 but allowed in TA2 and TA3. In some instances, if the allowed NSSAI is not associated with the list of TAs, the UE may assume that the allowed NSSAI is allowed in the current TA where the UE is registered.

[0138] The UE receives NSAG information 640 via NAS signaling. For example, the UE may receive NSAG information 640 in a REGISTRATION ACCEPT or UE CONFIGURATION UPDATE COMMAND message. NSAG information 640 configures NSAGs 1-6. NSAG 1 includes S-NSSAI-a and b. NSAG 1 is allowed in all tracking areas TA1-3 and has a priority of 3. NSAG 2 includes S-NSSAI-a, b, and c. NSAG 2 is allowed in tracking areas TA2 and TA3 and has a priority of 1. NSAG 3 includes S-NSSAI-a and d. NSAG 3 is allowed in tracking area TA2 and has a priority of 3. NSAG 4 includes S-NSSAI-a, b, and c. NSAG 4 is allowed in tracking area TA3 and has a priority of 1. NSAG 5 includes S-NSSAI-a, b, and c. NSAG 5 is allowed in tracking areas TA1 and TA2 and has a priority of 1. NSAG 6 includes S-NSSAI-a and c. NSAG 6 is allowed in tracking area TA1 and has priority 2.

[0139] The UE receives SIB4 630, which configures three frequencies: n41 band with priority 6, n256 band with priority 2, and n1 band with priority 3.

[0140] The UE receives SIB16 620. The SIB16 620 message includes three DL frequencies: DL F0, which is the serving frequency of the n78 band; DL F1, which is SIB4 frequency 1, eg, n41 band; and DL F2, which is SIB4 frequency 2, eg, n256 band.

[0141] DL F0 of SIB16 620 includes NSAGs 1-6 (each with its associated reselection priority), a list of allowed cells, and a list of rejected cells. For example, NSAG 1 has a reselection priority of 5, NSAG 2 has a reselection priority of 7, NSAG 3 has a reselection priority of 5, NSAG 4 has a reselection priority of 6, NSAG 5 has a reselection priority of 7, and NSAG 6 has a reselection priority of 6.

[0142] DL F1 of SIB16 620 includes NSAGs 2-6 (each with its associated reselection priority), a list of allowed cells, and a list of rejected cells. For example, NSAG 2 has a reselection priority of 7, NSAG 3 has a reselection priority of 6, NSAG 4 has a reselection priority of 7, NSAG 5 has a reselection priority of 7, and NSAG 6 has a reselection priority of 5.

[0143] DL F2 of SIB16 620 includes NSAG 4 with its associated reselection priority, a list of allowed cells and a list of rejected cells. For example, NSAG 4 has a reselection priority of 6.

[0144] The UE may create a configuration database based on information received from a complete NAS Registration or UE Configuration Update Command message and the AS RRC SIB4 630 and SIB16 620 messages. Figure 7 The following related description provides details on how the UE can implement a slice priority network configuration database, and provides a scenario describing how the UE can utilize the generated slice priority network configuration database.

[0145] Figure 7 Some aspects of a configuration database 700 according to some embodiments are shown. Specifically, slice prioritization 700 is an example of a specific implementation of slice prioritization based on broadcast information in SIB4 and SIB16 and NSAG information provided by NAS signaling. The UE can use the above Figure 6 The slice priority network configuration database 710 is generated based on the information and its description.

[0146] The slice priority network configuration database 710 may include a broadcast configuration 720. The broadcast configuration 720 may be Figure 4 An example of a slice priority network configuration database 480 in FIG. 4 . The UE may generate a broadcast configuration 720 based on information elements provided by SIB4 and SIB16 messages.

[0147] The first column (ie, slice) of the broadcast configuration 720 includes the deployed S-NSSAI ad. The first column (ie, slice) is obtained from the network deployment information that may be provided by NAS signaling.

[0148] The second column (i.e., currently allowed / rejected) of the broadcast configuration 720 indicates whether the corresponding slice is allowed or rejected. The UE may receive this information in the NAS registration accept message.

[0149] The third column (ie, allowed TAs, currently known) of the broadcast configuration 720 lists the TAs in which the corresponding slices are allowed. The UE may receive this information in the NAS Registration Accept message.

[0150] The fourth column (ie, SIB4-based priorities) of the broadcast configuration 720 includes frequency reselection priorities based on SIB4. These priorities may not be associated with slices in the first column (ie, slices).

[0151] The fifth column of the broadcast configuration 720, i.e., SIB16-based priorities, includes slice-based frequency reselection priorities based on SIB16. The frequency reselection priorities in this column may be based on the corresponding NSAG priorities associated with each frequency in SIB16.

[0152] The sixth column (ie, allowed cells) of the broadcast configuration 720 includes cells provided, for example, by the PCI range, where S-NSSAI is allowed. The information in this column can be obtained from the allowed cells associated with each frequency in SIB16.

[0153] Similarly, the seventh column (ie, excluded cells) of the broadcast configuration 720 includes cells provided by, for example, the PCI range, where the S-NSSAI is excluded. The information in this column can be obtained from the excluded cells associated with each frequency in SIB16.

[0154] The slice priority network configuration database 710 may include a NAS configuration 730. The UE may generate the NAS configuration 730 based on information elements provided by a NAS Registration Accept or UE Configuration Update Command message.

[0155] The first column (ie, NSAG ID) of NAS configuration 730 includes NSAG identification information. Each row of NAS configuration 730 provides information associated with a corresponding NSAG.

[0156] The second column of NAS configuration 730 (ie, supported slices) provides the S-NSSAI or slices included or supported by the NSAG associated with the NSAG ID.

[0157] The third column of NAS Configuration 730 (ie, Allowed TAs) provides a list of tracking areas in which the NSAG associated with the NSAG ID is allowed.

[0158] The fourth column of NAS Configuration 730 (ie, NSAG Priority from NAS) provides the priority of the NSAG associated with the NSAG ID.

[0159] The fifth to eighth columns of NAS configuration 730 (ie, NSAG priority from AS) include the priority associated with each NSAG based on broadcast configuration 720.

[0160] The slice priority network configuration database 710 may include a TA configuration 740 based on the NAS configuration 730. The TA configuration 740 includes an association between the configured NSAGs and the tracking areas. For example, the TA configuration 740 indicates that TA1 allows NSAGs 1, 5, and 6, TA2 allows NSAGs 1, 2, 3, and 5, and TA3 allows NSAGs 1, 2, and 4.

[0161] The following scenarios describe how a UE may utilize the slice priority network configuration database 710. In these scenarios, it is assumed that the UE camps on a cell in TA1. The following scenarios are examples of dynamic slice priority decision table entries.

[0162] In scenario 1, the UE invokes an application or service that requires S-NSSAI-a and S-NSSAI-b. Based on the NAS configuration 730, the UE may determine that the slices are supported in NSAG 1, 4, and 5. Based on the list of NSAG and TA configuration 740, the UE may determine that the requested slices are supported in tracking areas TA1, TA2, and TA3.

[0163] S-NSSAI-a is the default eMBB slice, which is unrestricted and allowed in all TAs and PCIs.

[0164] For applications or services that request S-NSSAI-b, the UE uses the information associated with S-NSSAI-b in the slice priority network configuration database 710. The UE may combine Figure 5 The PDU establishment optimization process described in or after that, the following frequency reselection optimization is performed.

[0165] If the UE camps on n78, then based on NAS configuration 730, n78 supports all NSAGs. Therefore, NSAG 1, 4, and 5 are potential candidates. Based on NAS configuration 730, NSAG 1 has NAS priority 3, NSAG 4 has NAS priority 1, and NSAG 5 has NAS priority 1. Based on TA configuration 740, NSAG 4 is not supported in the current UE's tracking area TA1, and only NSAG 1 and 5 are supported in TA1. The UE may prioritize NSAG 1 with the highest priority and stay on n78 and TA1. The UE may follow the following steps: Figure 5The PDU establishment process described in .

[0166] If the UE camps on n41, based on NAS configuration 730, NSAG 2-6 are supported in n41. Therefore, NSAG 4 and 5 are potential candidates. Based on NAS configuration 730, NSAG 4 has NAS priority 1 and NSAG 5 has NAS priority 1. The UE may determine to stay on TA1. The UE may compare the radio frequency (RF) conditions of adjacent frequencies to decide to stay on n41 (with NSAG 4 and 5) or reselect to n78 (with NSAG 1 (highest NAS priority compared to NSAG 4 and 5)). The UE may follow the following Figure 5 The PDU establishment process described in .

[0167] If the UE camps on n256, then no NSAG is supported in n256 based on NAS configuration 730. The UE may determine to stay in TA1 and reselect to n78 (with NSAG 1, which has the highest NAS priority compared to NSAG 4 and 5). If n78 is not available, the UE may reselect to n41. The UE may follow the Figure 5 The PDU establishment process described in .

[0168] If the UE camps on n1, then based on NAS configuration 730, only NSAG 2 is supported in n1, and NSAG 2 does not support slice b. The UE may stay on TA1 and reselect to n78 (with NSAG 1, which has the highest NAS priority compared to NSAG 4 and 5), and follow the Figure 5 If n78 is not available, the UE can reselect to n41.

[0169] In scenario 2, the UE invokes an application or service that requires S-NSSAI-a and S-NSSAI-c. Based on the NAS configuration 730, the UE may determine that the slices are supported in NSAGs 2, 4, 5, and 6. Based on the list of NSAG and TA configuration 740, the UE may determine that the requested slices are supported in tracking areas TA1, TA2, and TA3.

[0170] S-NSSAI-a is the default eMBB slice, which is unrestricted and allowed in all TAs and PCIs.

[0171] For applications or services that request S-NSSAI-c, the UE uses the information associated with S-NSSAI-c in the slice priority network configuration database 710. The UE may combine Figure 5 The PDU establishment optimization process described in or after that, the following frequency reselection optimization is performed.

[0172] If the UE camps on n78, then based on NAS configuration 730, n78 supports all NSAGs. Therefore, NSAG 2, 4, 5, and 6 are potential candidates. Based on NAS configuration 730, NSAG 2 has NAS priority 1, NSAG 4 has NAS priority 1, NSAG 5 has NAS priority 1, and NSAG 6 has NAS priority 2. Based on TA configuration 740, NSAG 2 and 4 are not supported in the current UE's tracking area TA1, and only NSAG 5 and 6 are supported in TA1. The UE may prioritize NSAG 6 with the highest priority and stay on n78 and TA1. The UE may follow the following steps: Figure 5 The PDU establishment process described in .

[0173] If the UE camps on n41, based on NAS configuration 730, NSAG 2-6 are supported in n41. Therefore, NSAG 2, 4, 5, and 6 are potential candidates. Based on NAS configuration 730, NSAG 2 has NAS priority 1, NSAG 4 has NAS priority 1, NSAG5 has NAS priority 1, and NSAG 6 has NAS priority 2. Based on TA configuration 740, NSAG 2 and 4 are not supported in the current UE's tracking area TA1, and only NSAG 5 and 6 are supported in TA1. The UE may prioritize NSAG 6 with the highest priority, compare the RF conditions, and stay on n41 and TA1. If the UE finds that the n41 RF condition is better than n78 (the highest priority frequency) by a certain threshold, the UE may reselect to n78. The UE may follow the following steps. Figure 5 The PDU establishment process described in .

[0174] If the UE camps on n256, no NSAG is supported in n256 based on NAS configuration 730. The UE may determine to stay in TA1 and reselect to n78 or n41 (with NSAG 6, which has the highest NAS priority compared to NSAG 2, 4, and 5). The UE may select between n78 and n41 based on RF measurements. The UE may follow the following Figure 5 The PDU establishment process described in .

[0175] If the UE camps on n1, based on NAS configuration 730, only NSAG 2 is supported in n1. NSAG 2 has NAS priority 1, i.e., a lower priority than NSAG 6 which is not supported in n1. The UE may check whether any n1 cells are available in TA2 or TA3. If there are available n1 cells in TA2 or TA3, the UE may compare the RF conditions to decide whether to stay in n1 with NSAG 2 or reselect to n78 or n41 with NSAG 6 having the highest NAS priority. If there are no available n1 cells in TA2 or TA3, the UE may stay in TA1, reselect to whichever of n78 or n41 has better RF energy or measurement, and select NSAG 6. The UE may follow the following steps. Figure 5 The PDU establishment process described in .

[0176] In scenario 3, the UE invokes an application or service that requires S-NSSAI-a and S-NSSAI-d. Based on the NAS configuration 730, the UE may determine that the slices are supported in NSAG 2, 5, and 6. Based on the list of NSAG and TA configuration 740, the UE may determine that the requested slices are supported in tracking areas TA2 and TA3.

[0177] S-NSSAI-a is the default eMBB slice, which is unrestricted and allowed in all TAs and PCIs.

[0178] For applications or services that request S-NSSAI-d, the UE uses the information associated with S-NSSAI-d in the slice priority network configuration database 710. The UE may combine Figure 5 The PDU establishment optimization process described in or after that, the following frequency reselection optimization is performed.

[0179] If the UE camps on n78, based on NAS configuration 730, n78 supports all NSAGs. Therefore, NSAG 2 and 3 are potential candidates. Based on NAS configuration 730, NSAG 2 has NAS priority 1, and NSAG 3 has NAS priority 3. Based on TA configuration 740, NSAG 2 and 3 are not supported in the tracking area TA1 of the current UE. The UE may give priority to NSAG 3 having the highest priority among the potential NSAG candidates. NSAG 3 is supported only in TA3, and NSAG 2 (the second highest NAS priority) is supported in TA2 and TA3. The UE may perform frequency reselection optimization using the following step sequence.

[0180] In step 1, the UE may determine whether the n78 cell in TA2 is available. If the n78 cell in TA2 is available, the UE may reselect to n78 with NSAG 3 in TA2. The UE may combine Figure 5 The UE may perform the PDU establishment optimization process described in step 2 or perform the frequency reselection optimization described in step 3 thereafter. If the n78 cell in TA2 is not available, the UE may perform the operation in step 2.

[0181] In step 2, the UE may determine whether the n41 cell in TA2 is available. If the n41 cell in TA2 is available, the UE may reselect to n41 with NSAG 3 in TA2. The UE may combine Figure 5 The UE may perform the PDU establishment optimization process described in step 1 or perform the frequency reselection optimization described in step 2. If the n41 cell in TA2 is not available, the UE may perform the operation in step 3.

[0182] In step 3, the UE may determine whether the n78 cell in TA3 is available. If the n78 cell in TA3 is available, the UE may reselect to n78 with NSAG 2 in TA3. The UE may combine Figure 5 The PDU establishment optimization process described in or after that, the following frequency reselection optimization is performed. If the n78 cell in TA3 is not available, the UE may perform the operation in step 4.

[0183] In step 4, the UE may determine whether the n41 cell in TA3 is available. If the n41 cell in TA3 is available, the UE may reselect to n41 with NSAG 2 in TA3. The UE may combine Figure 5 The UE may perform the PDU establishment optimization process described in step 5 or perform the frequency reselection optimization described in step 5 thereafter. If the n41 cell in TA3 is not available, the UE may perform the operation in step 5.

[0184] In step 5, the UE may determine whether the n1 cell in TA3 is available. If the n1 cell in TA3 is available, the UE may reselect to n1 with NSAG 2 in TA3. The UE may combine Figure 5 The UE may perform the PDU establishment optimization process described in step 6 or perform the following frequency reselection optimization thereafter. If the n1 cell in TA3 is not available, the UE may perform the operation in step 6.

[0185] In step 6, the UE may determine whether to map the traffic to a default slice, e.g., an S-NSSAI-a or eMBB slice.

[0186] If the UE camps on n41, the UE may follow the same procedure as when the UE camps on n78, as described above.

[0187] If the UE camps on n256, no NSAG is supported in n256 based on NAS configuration 730. The UE may scan n78 or n41 cells in TA2 or TA3. The UE may prioritize the order of scanning suitable cells. Based on the slice priority network configuration database 710, the UE may first scan cells in n78 in TA2, then scan cells in n41 in TA2, then scan n78 cells in TA3, then scan n41 cells in TA3, and finally scan n1 cells in TA3. If a suitable cell is found, the UE may combine Figure 5 The PDU establishment optimization procedure described in or the frequency reselection optimization below is performed thereafter. If no cell is found, the UE may determine whether to map the traffic to a default slice, such as S-NSSAI-a or eMBB slice.

[0188] If the UE camps on n1, the UE may follow the same procedure as when the UE camps on n78, as described above.

[0189] In scenario 4, the UE invokes an application or service that requires S-NSSAI-a, S-NSSAI-b, and S-NSSAI-c. Based on the NAS configuration 730, the UE can determine that the slice is supported in NSAG 4 and 5. In this scenario, NSAG 4 and 6 have the same NAS priority of 1, but have different AS priorities. NSAG 5 has the same priority for n78 and n41, with AS priority 7, but NSAG 4 has different priorities for n78 and n41. NSAG 4 has AS priority 6 in n78 and AS priority 7 in n41. Note that in this example, the smaller the value of the AS priority, the higher the priority. Therefore, in n41, NSAG 4 with AS priority 6 has a higher priority than NSAG 5 with AS priority 7. Based on the list of NSAG and TA configuration 740, the UE can determine that the requested slice is supported in tracking areas TA1, TA2, and TA3.

[0190] S-NSSAI-a is the default eMBB slice, which is unrestricted and allowed in all TAs and PCIs.

[0191] For applications or services that request S-NSSAI-b and c, the UE may use the information associated with S-NSSAI-b and c in the slice priority network configuration database 710. The UE may combine Figure 5 The PDU establishment optimization process described in or after that, the following frequency reselection optimization is performed.

[0192] If the UE camps on n78, then based on NAS configuration 730, n78 supports all NSAGs. Therefore, NSAG 4 and 5 are potential candidates. The UE can measure n41 and n78 cells in TA1, TA2 and TA3. The UE can take the following steps in order to perform frequency reselection optimization.

[0193] In step 1, the UE may determine whether the RSRP of n41 in TA3 is more than 10 dBm better than the RSRP of n78 in TA1 or TA2. If the RSRP of n41 in TA3 is more than 10 dBm better than the RSRP of n78 in TA1 or TA2, the UE may reselect to n41 (with NSAG 4, which has the highest AS priority from SIB16). The UE may combine Figure 5 The UE may perform the PDU setup optimization procedure described in or perform the frequency reselection optimization below after it. If the RSRP of n41 in TA3 is not better than the RSRP of n78 in TA1 or TA2 by more than 10 dBm, the UE may perform the operation in step 2.

[0194] In step 2, the UE may determine whether the RSRP of n41 in TA1 or TA2 or the RSRP of n78 in TA2 is better than the RSRP of n78 in TA1 by more than 7dBm. If the RSRP of n41 in TA1 or TA2 or the RSRP of n78 in TA2 is better than the RSRP of n78 in TA1 by more than 7dBm, the UE may prioritize NSAG 5 and reselect to either n41 or n78 that meets the 7dBm threshold. The UE may combine Figure 5 The UE may perform the PDU setup optimization procedure described in step 3 or perform the frequency reselection optimization below after that. If the RSRP of n41 in TA1 or TA2 or the RSRP of n78 in TA2 is not better than the RSRP of n78 in TA1 by more than 7 dBm, the UE may perform the operation in step 3.

[0195] In step 3, the UE may prioritize NSAG 5 and stay at n78 of TA1. Figure 5 The UE may perform the PDU setup optimization procedure described in or after that the frequency reselection optimization described below. The UE may take this step to avoid the additional reselection procedure.

[0196] If the UE camps on n41, then based on NAS configuration 730, n41 supports NSAG 2-6. Therefore, NSAG 4 and 5 are potential candidates. The UE may measure n41 and n78 cells in TA1, TA2, and TA3. The UE may take the following sequence of steps to perform frequency reselection optimization.

[0197] In step 1, the UE may determine whether the RSRP of n41 in TA3 is more than 8dBm better than the RSRP of n41 in TA1. If the RSRP of n41 in TA3 is more than 8dBm better than the RSRP of n41 in TA1, the UE may reselect to n41 in TA3 (with NSAG 4, which has the highest AS priority from SIB16). The UE may combine Figure 5 The UE may perform the PDU setup optimization procedure described in or perform the frequency reselection optimization below after it. If the RSRP of n41 in TA3 is not better than the RSRP of n41 in TA1 by more than 8 dBm, the UE may perform the operation in step 2.

[0198] In step 2, the UE may prioritize NSAG 5 and stay at n41 of TA1. The UE may combine Figure 5 The UE may perform the PDU setup optimization procedure described in or after that the frequency reselection optimization described below. The UE may take this step to avoid the additional reselection procedure.

[0199] If the UE camps on n256, no NSAG is supported in n256 based on NAS configuration 730. The UE may measure cells n41 and n78 in TA1, TA2, and TA3. The UE may reselect to the highest ranked frequency with better measurement results. The UE may combine Figure 5 The PDU establishment optimization procedure described in or the frequency reselection optimization below is performed thereafter. If no cell is available in n41 or n78, the UE may determine whether to map the traffic to a default slice, such as an S-NSSAI-a or eMBB slice.

[0200] If the UE camps on n1, then based on NAS configuration 730, only NSAG 2 is supported in n1. NSAG 2 does not support S-NSSAI-b. The UE may measure cells n41 and n78 in TA1, TA2, and TA3. The UE may reselect to the highest ranked frequency with better measurement results. The UE may combine Figure 5 The PDU establishment optimization procedure described in or the frequency reselection optimization below is performed thereafter. If no cell is available in n41 or n78, the UE may determine whether to map the traffic to a default slice, such as an S-NSSAI-a or eMBB slice.

[0201] In scenario 5, the UE invokes an application or service that requires S-NSSAI-a, S-NSSAI-c, and S-NSSAI-d. Based on the NAS configuration 730, the UE may determine that the slice is supported in NSAG 2. Based on the list of NSAGs and TA configurations 740, the UE may determine that NSAG 2 is the only supported NSAG with NAS priority 1 that is supported in n78, n41, and n1 in TA2 and TA3.

[0202] S-NSSAI-a is the default eMBB slice, which is unrestricted and allowed in all TAs and PCIs.

[0203] For applications or services that request S-NSSAI-c and d, the UE may use the information associated with S-NSSAI-c and d in the slice priority network configuration database 710. The UE may combine Figure 5 The PDU establishment optimization process described in or after that, the following frequency reselection optimization is performed.

[0204] If the UE camps on n78, NSAG 2 is the only potential candidate with NAS priority 1 based on NAS configuration 730. The UE may measure n78, n41 and n1 cells in TA1, TA2 and TA3. The UE may take the following sequence of steps to perform frequency reselection optimization.

[0205] In step 1, the UE may determine whether the RSRP of n41 in any TA is better than the RSRP of n78 in TA1 by more than 10dBm. If the RSRP of n41 in any TA is better than the RSRP of n78 in TA1 by more than 10dBm, the UE may reselect to n41. The UE may combine Figure 5 The UE may perform the PDU setup optimization procedure described in or perform the frequency reselection optimization below after it. If the RSRP of n41 in any TA is not better than the RSRP of n78 in TA1 by more than 10 dBm, the UE may perform the operation in step 2.

[0206] In step 2, the UE may determine whether the RSRP of n1 in any TA is better than the RSRP of n78 in TA1 by more than 15dBm. If the RSRP of n1 in any TA is better than the RSRP of n78 in TA1 by more than 15dBm, the UE may reselect to n1. The UE may combine Figure 5 The UE may perform the PDU setup optimization procedure described in or after the frequency reselection optimization described below. If the RSRP of n1 in any TA is not better than the RSRP of n78 in TA1 by more than 15 dBm, the UE may perform the operation in step 3.

[0207] In step 3, the UE can stay at n78 of TA1. Figure 5 The PDU establishment optimization process described in or after that, the following frequency reselection optimization is performed.

[0208] If the UE camps on n41, NSAG 2 is the only potential candidate with NAS priority 1 based on NAS configuration 730. The UE may measure n78, n41 and n1 cells in TA1, TA2 and TA3. The UE may take the following sequence of steps to perform frequency reselection optimization.

[0209] In step 1, the UE may determine whether the RSRP of n78 in any TA is better than the RSRP of n41 in TA1 by more than 8dBm. If the RSRP of n78 in any TA is better than the RSRP of n41 in TA1 by more than 8dBm, the UE may reselect to n78. The UE may combine Figure 5 The UE may perform the PDU setup optimization procedure described in or perform the frequency reselection optimization below after it. If the RSRP of n78 in any TA is not better than the RSRP of n41 in TA1 by more than 8dBm, the UE may perform the operation in step 2.

[0210] In step 2, the UE may determine whether the RSRP of n1 in any TA is better than the RSRP of n41 in TA1 by more than 15dBm. If the RSRP of n1 in any TA is better than the RSRP of n41 in TA1 by more than 15dBm, the UE may reselect to n1. The UE may combine Figure 5 The UE may perform the PDU setup optimization procedure described in or perform the frequency reselection optimization below after it. If the RSRP of n1 in any TA is not better than the RSRP of n41 in TA1 by more than 15 dBm, the UE may perform the operation in step 3.

[0211] In step 3, the UE can stay at n41 of TA1. The UE can combine Figure 5 The PDU establishment optimization process described in or after that, the following frequency reselection optimization is performed.

[0212] If the UE camps on n256, no NSAG is supported in n256 based on NAS configuration 730. The UE may measure n41, n78, and n1 cells in TA1, TA2, and TA3. The UE may reselect to the highest ranked frequency with better measurement results. The UE may combine Figure 5 The PDU establishment optimization procedure described in or the frequency reselection optimization below is performed thereafter. If no cell is available in n41, n78 or n1, the UE may determine whether to map the traffic to a default slice, such as S-NSSAI-a or eMBB slice.

[0213] If the UE camps on n1, based on NAS configuration 730, only NSAG 2 is supported in n1 and NSAG 2 is the only potential candidate with NAS priority 1. The UE may measure n78, n41 and n1 cells in TA1, TA2 and TA3. The UE may take the following sequence of steps to perform frequency reselection optimization.

[0214] In step 1, the UE may determine whether the RSRP of n78 in any TA is better than the RSRP of n1 in TA1 by more than 6dBm. If the RSRP of n78 in any TA is better than the RSRP of n1 in TA1 by more than 6dBm, the UE may reselect to n78. The UE may combine Figure 5 The UE may perform the PDU setup optimization procedure described in or after the frequency reselection optimization described below. If the RSRP of n78 in any TA is not better than the RSRP of n1 in TA1 by more than 6 dBm, the UE may perform the operation in step 2.

[0215] In step 2, the UE may determine whether the RSRP of n41 in any TA is better than the RSRP of n1 in TA1 by more than 15dBm. If the RSRP of n41 in any TA is better than the RSRP of n1 in TA1 by more than 15dBm, the UE may reselect to n1. The UE may combine Figure 5 The UE may perform the PDU setup optimization procedure described in or after the frequency reselection optimization described below. If the RSRP of n41 in any TA is not better than the RSRP of n1 in TA1 by more than 15 dBm, the UE may perform the operation in step 3.

[0216] In step 3, the UE may stay at n1 of TA1. Figure 5 The PDU establishment optimization process described in or after that, the following frequency reselection optimization is performed.

[0217] In scenario 6, the UE invokes an application or service that requires S-NSSAI-a, S-NSSAI-b, S-NSSAI-c, and S-NSSAI-d. Based on the NAS configuration 730, the UE may determine that no NSAG supports all 4 slices.

[0218] S-NSSAI-a is the default eMBB slice, which is unrestricted and allowed in all TAs and PCIs.

[0219] like Figure 5 As described in, the UE can use slice priorities based on usage or impact to decide which slices can be ignored and other slices can be served.

[0220] Figure 8An operational flow / algorithm structure 800 according to some embodiments is illustrated. The operational flow / algorithm structure 800 may be implemented by a UE (eg, UE 104 or UE 1400) or a component thereof (eg, processing circuit 1404).

[0221] The operation flow / algorithm structure 800 may include: At 804, camping on a tracking area (e.g., TA1). The UE may perform a registration procedure and receive an AS and NAS configuration for reselection. The UE may generate a slice priority network configuration based on the AS and NAS configuration that the UE may use to perform reselection.

[0222] The operation flow / algorithm structure 800 may include: at 806, determining whether there is a request to establish a PDU session for a new slice. Based on the determination that there is a request to establish a PDU session for a new slice, the operation flow / algorithm structure 800 proceeds to step 808 following the "yes" branch. Based on the determination that there is no request to establish a PDU session for a new slice, the operation flow / algorithm structure 800 proceeds to step 820 following the "no" branch.

[0223] The operational flow / algorithm structure 800 may include, at 808, determining whether there are any NSAGs configured for the requested new slice. Based on the determination that there are any NSAGs configured for the requested new slice, the operational flow / algorithm structure 800 proceeds to step 810 following the "yes" branch. Based on the determination that there are no NSAGs configured for the requested new slice, the operational flow / algorithm structure 800 proceeds to step 822 following the "no" branch.

[0224] The operational flow / algorithm structure 800 may include, at 810, determining whether the requested new slice is supported by multiple NSAGs. Based on the determination that the requested new slice is supported by multiple NSAGs, the operational flow / algorithm structure 800 proceeds to step 812 following the "yes" branch. Based on the determination that the requested new slice is not supported by multiple NSAGs, the operational flow / algorithm structure 800 proceeds to step 824 following the "no" branch.

[0225] The operational flow / algorithm structure 800 may include, at 812, determining whether NAS priority is provided for all NSAGs. Based on the determination that NAS priority is provided for all NSAGs, the operational flow / algorithm structure 800 proceeds to step 814 following the "yes" branch. Based on the determination that NAS priority is not provided for all NSAGs, the operational flow / algorithm structure 800 proceeds to step 824 following the "no" branch.

[0226] The operational flow / algorithm structure 800 may include determining whether the NSAGs have equal NAS priority at 814. Based on the determination that the NSAGs have equal NAS priority, the operational flow / algorithm structure 800 proceeds to step 816 following the "yes" branch. Based on the determination that the NSAGs do not have equal NAS priority, the operational flow / algorithm structure 800 proceeds to step 826 following the "no" branch.

[0227] The operational flow / algorithm structure 800 may include determining whether the NSAGs have equal AS priority at 816. Based on the determination that the NSAGs have equal AS priority, the operational flow / algorithm structure 800 proceeds to step 818 following the "yes" branch. Based on the determination that the NSAGs do not have equal AS priority, the operational flow / algorithm structure 800 proceeds to step 830 following the "no" branch.

[0228] The operation flow / algorithm structure 800 may include: at 818, executing Figure 5 The operation flow / algorithm structure 500 described in the embodiment of the present invention can be used to describe the operation flow / algorithm structure 500 described in the embodiment of the present invention. The UE can stay in the current reserved frequency. The UE can fill in the dynamic slice priority decision table for NSAG priority sorting.

[0229] The operation flow / algorithm structure 800 may include: at 820, waiting for a request for a new slice invoked by a service or application. No slice reselection optimization process needs to be performed.

[0230] The operational flow / algorithm structure 800 may include, at 822, performing slice priority and inter-frequency reselection based on SIB4 and SIB16 configurations.

[0231] The operational flow / algorithm structure 800 may include: at 824, determining to stay on or reselect to the highest priority frequency and TA to establish a PDU session based on the dynamic slice priority decision table.

[0232] The operational flow / algorithm structure 800 may include determining whether the UE is camped on a TA that supports a high priority NSAG, at 826. Based on a determination that the UE is camped on a TA that supports a high priority NSAG, the operational flow / algorithm structure 800 proceeds to step 830 following the "yes" branch. Based on a determination that the UE is not camped on a TA that supports a high priority NSAG, the operational flow / algorithm structure 800 proceeds to step 828 following the "no" branch.

[0233] The operation flow / algorithm structure 800 may include, at 828, reselecting to the highest priority frequency in the highest priority TA. The UE may populate or follow the dynamic slice priority decision table for NSAG prioritization. The UE may perform Figure 5 The operational flow / algorithm structure 500 described in the PDU establishment optimization.

[0234] The operation flow / algorithm structure 800 may include, at 830, determining whether the UE is camping on a frequency with the highest AS priority. Based on the determination that the UE is camping on the highest AS priority frequency, the operation flow / algorithm structure 800 proceeds to step 834 following the "yes" branch. Based on the determination that the UE is not camping on the highest AS priority frequency, the operation flow / algorithm structure 800 proceeds to step 832 following the "no" branch.

[0235] The operation flow / algorithm structure 800 may include, at 832, reselecting to the highest priority frequency. The UE may populate or follow the dynamic slice priority decision table for NSAG prioritization. The UE may perform Figure 5 The operational flow / algorithm structure 500 described in the PDU establishment optimization.

[0236] The operational flow / algorithm structure 800 may include, at 834, determining whether the RSRP of the high priority frequency is worse than the second priority frequency by a threshold value, for example, the threshold value may be equal to 6, 7, 8, 10, or 15 dBm. Based on determining that the RSRP of the high priority frequency is worse than the second priority frequency by a threshold value (for example, the threshold value may be equal to 6, 7, 8, 10, or 15 dBm), the operational flow / algorithm structure 800 proceeds to step 838 following the "yes" branch. Based on determining that the RSRP of the high priority frequency is not worse than the second priority frequency by a threshold value, for example, the threshold value may be equal to 6, 7, 8, 10, or 15 dBm, the operational flow / algorithm structure 800 proceeds to step 836 following the "no" branch.

[0237] The operation flow / algorithm structure 800 may include: At 836, staying on the current camped frequency. The UE may populate or follow the dynamic slice priority decision table for NSAG prioritization. The UE may perform Figure 5 The operational flow / algorithm structure 500 described in the PDU establishment optimization.

[0238] The operational flow / algorithm structure 800 may include, at 838, determining whether the RSRP of the second priority frequency is worse than the Kth priority frequency by X, for example, X may be equal to 6, 7, 8, 10, or 15 dBm. Based on the determination that the RSRP of the second priority frequency is worse than the Kth priority frequency by X, for example, X may be equal to 6, 7, 8, 10, or 15 dBm, the operational flow / algorithm structure 800 proceeds to step 842 following the "yes" branch. Based on the determination that the RSRP of the second priority frequency is not worse than the Kth priority frequency by X, for example, X may be equal to 6, 7, 8, 10, or 15 dBm, the operational flow / algorithm structure 800 proceeds to step 840 following the "no" branch.

[0239] The operation flow / algorithm structure 800 may include, at 840, reselecting to a second priority frequency. The UE may populate or follow the dynamic slice priority decision table for NSAG prioritization. The UE may perform Figure 5 The operational flow / algorithm structure 500 described in the PDU establishment optimization.

[0240] The operation flow / algorithm structure 800 may include, at 842, reselecting to the Kth priority frequency. The UE may populate or follow the dynamic slice priority decision table for NSAG prioritization. The UE may perform Figure 5 The operational flow / algorithm structure 500 described in the PDU establishment optimization.

[0241] Fig. 9 An operational flow / algorithm structure 900 according to some embodiments is shown. The operational flow / algorithm structure 900 may be implemented by a UE (eg, UE 104 or UE 1400) or a component thereof (eg, processing circuit 1404).

[0242] The operation flow / algorithm structure 900 may include: at 910, receiving first configuration information via NAS signaling. The NAS signaling may include a registration acceptance or UE configuration update command message. The first configuration information may include a deployed S-NSSAI, NSAG information, or a list of allowed or rejected S-NSSAIs requested by the UE.

[0243] The operation flow / algorithm structure 900 may include: at 920, receiving second configuration information via AS signaling, for example, broadcast system information. The AS signaling may be RRC signaling. For example, the AS signaling may include SIB4 or SIB16. The second configuration information may include frequency bands and their priorities, or frequency bands and associated NSAGs, allowed or rejected cells, or NSAG priorities.

[0244] The operational process / algorithm structure 900 may include: at 930, generating a slice priority network configuration based on the first configuration information and the second configuration information.

[0245] The operation flow / algorithm structure 900 may include: at 940, determining that a slice associated with a service or application invoked by the UE is allowed. The UE may make this determination based on the generated slice priority network configuration. The UE may also determine whether a PDU session mapped to the requested slice already exists.

[0246] The operational flow / algorithm structure 900 may include modifying the first PDU session or creating a second PDU session at 950. For example, the UE may determine that the AMBR is associated with the slice and thus modify the existing PDU session to transmit the invoked service or application data.

[0247] As another example, the UE may determine that a service or application invoked by the UE requires non-GBR QoS, and therefore modify an existing PDU session to transmit the invoked service or application data.

[0248] For another example, the UE may determine that a service or application invoked by the UE requires a PDU session supporting URLLS QoS, and determine that an existing PDU session does not support URLLS QoS. Therefore, the UE may create a second PDU session supporting URLLS QoS.

[0249] Fig.10 An operational flow / algorithm structure 1000 according to some embodiments is shown. The operational flow / algorithm structure 1000 may be implemented by a UE (eg, UE 104 or UE 1400) or a component thereof (eg, processing circuit 1404).

[0250] At 1010 , the operational flow / algorithm structure 1000 may include actions similar to those at 910 in the operational flow / algorithm structure 900 .

[0251] At 1020 , the operational flow / algorithm structure 1000 may include actions similar to those at 920 in the operational flow / algorithm structure 900 .

[0252] At 1030 , the operational flow / algorithm structure 1000 may include actions similar to those at 930 in the operational flow / algorithm structure 900 .

[0253] The operational flow / algorithm structure 1000 may include: At 1040, determining that a slice associated with a service or application invoked by the UE is not allowed in a first tracking area. The first tracking area may be associated with a serving cell of the UE. The first tracking area may be a current tracking area camped by the UE. The UE may make a determination based on the generated slice priority network configuration.

[0254] The operational flow / algorithm structure 1000 may include: at 1050, determining that a slice associated with a service or application invoked by the UE is allowed in a neighboring cell of a second tracking area. The second tracking area may be a neighboring tracking area. The neighboring tracking area may be geographically adjacent to the current tracking area occupied by the UE. The network may determine and configure adjacent tracking areas, and may not be geographically adjacent to the current tracking area. The neighboring cell may be a cell that the UE has detected and is not a serving cell, or a cell that the UE monitors (e.g., searches for associated reference signals and detects associated control information). The network may configure the UE to monitor neighboring cells. At 1050, the UE may make a determination based on the generated slice priority network configuration.

[0255] The operation flow / algorithm structure 1000 may include: At 1060, determining whether all active PDU sessions of the UE can continue in the neighboring cell of the second TA. If the neighboring cell supports the slice to which the PDU session is mapped, the PDU session can continue in the neighboring cell of the second TA. The UE can make a determination based on the generated slice priority network configuration.

[0256] The operation flow / algorithm structure 1000 may include determining whether to reselect to a neighboring cell of the second TA at 1070. The UE may make a determination based on the determination at 1060 (eg, determining whether all active PDU sessions of the UE can continue in the neighboring cell of the second TA).

[0257] If the UE determines that all active PDU sessions of the UE can continue in the neighboring cell, the UE may reselect a neighboring cell of the second TA. The UE may send a registration request message indicating a slice associated with a service or application invoked by the UE.

[0258] If the UE determines that not all active PDU sessions of the UE can be continued in the neighboring cell of the second TA, the UE may perform slice prioritization based on usage or impact. The UE may identify the PDU that cannot be continued in the neighboring cell and determine whether the PDU session is a low priority based on usage or impact. If the identified PDU session is a low priority based on usage or impact, the UE may release the PDU session or map the PDU session to a default slice. The default slice may be a slice that is supported in all cells and all TAs, such as an eMBB slice. The UE may reselect a neighboring cell based on releasing or mapping a PDU session that cannot be supported by a neighboring cell.

[0259] The UE may perform slice prioritization based on usage or impact. In slice prioritization based on usage or impact, the UE may identify PDUs that cannot be continued in candidate cells and determine whether the PDU session is of low priority based on usage or impact. If the identified PDU session is of low priority based on usage or impact, the UE may release the PDU session or map the PDU session to a default slice. The default slice may be a slice that is supported in all cells and all TAs, for example, an eMBB slice.

[0260] In one example, a PDU session with minimal usage (e.g., a dormant PDU session) may be identified as a low priority based on usage or impact. In another example, a slice or a PDU session that can be mapped to an eMBB slice may be identified as a low impact slice or PDU session with a low priority based on usage or impact. In another example, a service or application mapped to a slice that is not in use may be identified as a low priority based on usage or impact.

[0261] Fig.11 An operational flow / algorithm structure 1100 according to some embodiments is shown. The operational flow / algorithm structure 1100 may be implemented by a UE (eg, UE 104 or UE 1400) or a component thereof (eg, processing circuit 1404).

[0262] At 1110 , the operational flow / algorithm structure 1100 may include actions similar to those at 910 in the operational flow / algorithm structure 900 .

[0263] At 1120 , the operational flow / algorithm structure 1100 may include actions similar to those at 920 in the operational flow / algorithm structure 900 .

[0264] At 1130 , the operational flow / algorithm structure 1100 may include actions similar to those at 930 in the operational flow / algorithm structure 900 .

[0265] The operation flow / algorithm structure 1100 may include: at 1140, determining that a slice associated with a service or application invoked by the UE is not allowed in a first frequency. The first frequency may be a current frequency camped on by the UE. The first frequency may be associated with a serving cell of the UE. The UE may make a determination based on a generated slice priority network configuration.

[0266] The operation flow / algorithm structure 1100 may include: At 1150, determining that a slice associated with a service or application invoked by the UE is allowed in a neighboring frequency. The neighboring frequency may be a frequency other than the current frequency of the same TA. The neighboring frequency may be a frequency configured by the UE instead of the current frequency. The network may configure the UE to monitor neighboring cells. At 1150, the UE may make a determination based on the generated slice priority network configuration.

[0267] The operation flow / algorithm structure 1100 may include: at 1160, determining whether the UE is capable of measuring a cell in an adjacent frequency. The adjacent frequency may include one or more cells. The UE may detect a cell in an adjacent frequency. The UE may be configured to monitor and measure a cell in one or more cells of an adjacent frequency. If the UE is not configured or has not yet detected a cell in an adjacent frequency, the UE may not be able to measure the cell. The adjacent cell configuration may include information about reference signals and measurement information.

[0268] The operation flow / algorithm structure 1100 may include determining whether to perform inter-frequency reselection, map a service or application to an existing PDU session, or reject a service or application invoked by the UE at 1170. The UE may make the determination based on the determination at 1160 (e.g., whether the UE is able to measure cells in neighboring frequencies).

[0269] If the UE is able to measure cells, the UE may generate a list of all measured cells including all adjacent frequencies. The UE may determine whether all active PDU sessions of the UE can continue in any measured cell in the generated list. The UE may generate a list of candidate cells. Each candidate cell in the list may support all active PDU sessions of the UE.

[0270] It is assumed that there are candidate cells that can support all active PDU sessions of the UE. In this case, the UE may perform frequency reselection optimization and PDU establishment optimization procedures to identify a suitable cell. The UE may perform inter-frequency reselection on the identified suitable cell.

[0271] If the UE determines that not all active PDU sessions of the UE can be continued in the candidate cell in the adjacent frequency, the UE may perform slice prioritization based on usage or impact. The UE may identify the PDU that cannot be continued in the adjacent cell and determine whether the PDU session is a low priority based on usage or impact. If the identified PDU session is a low priority based on usage or impact, the UE may release the PDU session or map the PDU session to a default slice. The default slice may be a slice that is supported in all cells and all TAs, for example, an eMBB slice. The UE may reselect a candidate cell based on releasing or mapping a PDU session that cannot be continued in the candidate cell.

[0272] The UE may perform slice prioritization based on usage or impact. In slice prioritization based on usage or impact, the UE may identify PDUs that cannot be continued in candidate cells and determine whether the PDU session is of low priority based on usage or impact. If the identified PDU session is of low priority based on usage or impact, the UE may release the PDU session or map the PDU session to a default slice. The default slice may be a slice that is supported in all cells and all TAs, for example, an eMBB slice.

[0273] In one example, a PDU session with minimal usage (e.g., a dormant PDU session) may be identified as a low priority based on usage or impact. In another example, a slice or a PDU session that can be mapped to an eMBB slice may be identified as a low impact slice or PDU session with a low priority based on usage or impact. In another example, a service or application mapped to a slice that is not in use may be identified as a low priority based on usage or impact.

[0274] If the UE cannot find a suitable cell, the UE may reject the service or application invoked by the UE, and the UE may be notified accordingly, for example, by sending a pop-up message.

[0275] Fig.12An operational flow / algorithm structure 1200 according to some embodiments is shown. The operational flow / algorithm structure 1200 may be implemented by a UE (eg, UE 104 or UE 1400) or a component thereof (eg, processing circuit 1404).

[0276] At 1210 , the operational flow / algorithm structure 1200 may include actions similar to those at 910 in the operational flow / algorithm structure 900 .

[0277] At 1220 , the operational flow / algorithm structure 1200 may include actions similar to those at 920 in the operational flow / algorithm structure 900 .

[0278] At 1230 , the operational flow / algorithm structure 1200 may include actions similar to those at 930 in the operational flow / algorithm structure 900 .

[0279] The operational flow / algorithm structure 1200 may include: at 1240, determining whether a slice associated with a service or application invoked by the UE is allowed in the current PCI. The current PCI may identify the cell to which the UE is currently connected. The UE may make a determination based on the generated slice priority network configuration.

[0280] The operation flow / algorithm structure 1200 may include determining whether the UE performs inter-frequency reselection, maps a service or application to an existing PDU session, rejects a service or application invoked by the UE, or initiates a new PDU session at 1250. The UE may make the determination based on the determination at 1240 (e.g., whether the slice is allowed in the current PCI).

[0281] If the UE determines that slicing is allowed in the current PCI, the UE may initiate a new PDU session for the associated service or application.

[0282] However, if the UE determines that slicing is not allowed in the current PCI, the UE may determine that the UE is able to measure neighboring PCIs. The UE may generate a list of measured neighboring PCIs. The UE may determine whether all active PDU sessions can continue in neighboring PCIs.

[0283] If the UE determines that all PDU sessions can continue in the adjacent PCI, the UE may perform intra-frequency reselection to the adjacent PCI.

[0284] If the UE determines that not all active PDU sessions of the UE can be continued in the neighboring PCI, the UE may perform slice prioritization based on usage or impact. The UE may identify the PDU that cannot be continued in the neighboring cell and determine whether the PDU session is a low priority based on usage or impact. If the identified PDU session is a low priority based on usage or impact, the UE may release the PDU session or map the PDU session to a default slice. The default slice may be a slice that is supported in all cells and all TAs, such as an eMBB slice. The UE may reselect the neighboring PCI based on releasing or mapping the PDU session that cannot be continued in the neighboring PCI.

[0285] The UE may perform slice prioritization based on usage or impact. In slice prioritization based on usage or impact, the UE may identify PDUs that cannot be continued in candidate cells and determine whether the PDU session is of low priority based on usage or impact. If the identified PDU session is of low priority based on usage or impact, the UE may release the PDU session or map the PDU session to a default slice. The default slice may be a slice that is supported in all cells and all TAs, for example, an eMBB slice.

[0286] In one example, a PDU session with minimal usage (e.g., a dormant PDU session) may be identified as a low priority based on usage or impact. In another example, a slice or a PDU session that can be mapped to an eMBB slice may be identified as a low impact slice or PDU session with a low priority based on usage or impact. In another example, a service or application mapped to a slice that is not in use may be identified as a low priority based on usage or impact.

[0287] If the UE cannot find a suitable PCI, the UE may reject the service or application invoked by the UE, and notify the UE accordingly, for example, by sending a pop-up message.

[0288] Fig.13 An operational flow / algorithm structure 1300 according to some embodiments is shown. The operational flow / algorithm structure 1300 may be implemented by a UE (eg, UE 104 or UE 1400) or a component thereof (eg, processing circuit 1404).

[0289] At 1310 , the operational flow / algorithm structure 1300 may include actions similar to those at 910 in the operational flow / algorithm structure 900 .

[0290] At 1320 , the operational flow / algorithm structure 1300 may include actions similar to those at 920 in the operational flow / algorithm structure 900 .

[0291] At 1330 , the operational flow / algorithm structure 1300 may include actions similar to those at 930 in the operational flow / algorithm structure 900 .

[0292] The operation flow / algorithm structure 1300 may include: At 1340, determining that a slice associated with a service or application invoked by the UE is allowed. The UE may make this determination based on the generated slice priority network configuration. The UE may also determine whether a PDU session mapped to the requested slice already exists.

[0293] The operational flow / algorithm structure 1300 may include, at 1350, determining that a first network slice access group (NSAG) and a second NSAG are configured for a slice. The UE may receive NSAG information via NAS signaling, such as a registration accept or UE configuration update command message. The UE may make the determination based on the slice priority network configuration.

[0294] The operational flow / algorithm structure 1300 may include determining whether the first NSAG and the second NSAG have equal priority, at 1360. The UE may make the determination based on a slice priority network configuration in which a NAS priority and one or more AS priorities may be associated with the NSAG.

[0295] The operational flow / algorithm structure 1300 may include determining whether to reselect to the highest NAS priority frequency in the highest priority tracking area, reselect to the highest AS priority frequency, stay on the current camped frequency, or reselect to the second NAS priority frequency at 1370. The UE may make a determination based on the determination in 1360, for example, determining whether the first NSAG and the second NSAG have equal priority.

[0296] If the first NSAG and the second NSAG have equal priorities, the UE may determine to stay on the currently camped frequency.

[0297] However, if the first NSAG and the second NSAG do not have equal priority, the UE may determine a highest priority NSAG and a second priority NSAG.Based on the highest and second priority NSAGs, the UE may determine whether the UE camps on a TA that supports the highest priority NSAG.

[0298] If the UE is not camped on a TA that supports the highest priority NSAG, the UE may determine the highest priority TA that supports the highest priority NSAG. The UE may determine the highest priority frequency in the highest priority TA that supports the highest priority NSAG. The UE may reselect to the highest priority frequency in the highest priority TA that supports the highest priority NSAG. The UE may make these determinations using a slice priority network or the first configuration or the second configuration.

[0299] If the UE camps on a TA that supports the highest priority NSAG, the UE may determine the highest AS priority frequency. The UE may determine whether it camps on the highest AS priority frequency.

[0300] If the UE is not camped on the highest AS priority frequency, the UE may reselect to the highest AS priority frequency.

[0301] If the UE is camped on the highest AS priority frequency, the UE may determine that the RSRP associated with the second priority frequency is greater than the RSRP associated with the highest priority frequency by more than a threshold. The threshold may be 3, 4, 5, 6, 7, 8, 10, or 15 dBm. If the RSRP of the second priority frequency is greater than the RSRP of the highest AS priority frequency by more than a threshold, the UE may reselect to the second priority frequency based on the above RSRP comparison. Fig.14 UE 1400 according to some embodiments is shown. UE 1400 may be similar to Figure 1 UE 104 and is substantially interchangeable therewith.

[0302] UE 1400 can be any mobile or non-mobile computing device, such as, for example, a mobile phone, a computer, a tablet, an XR device, glasses, an industrial wireless sensor (e.g., a microphone, a carbon dioxide sensor, a pressure sensor, a humidity sensor, a thermometer, a motion sensor, an accelerometer, a laser scanner, a fluid level sensor, an inventory sensor, a voltage / current meter, or an actuator), a video surveillance / monitoring device (e.g., a camera or a camcorder), a wearable device (e.g., a smart watch), or an IoT device.

[0303] UE 1400 may include a processor 1404, RF interface circuitry 1408, memory / storage 1412, a user interface 1416, a sensor 1420, a driver circuit 1422, a power management integrated circuit (PMIC) 1424, antenna structures 1426, and a battery 1428. The components of UE 1400 may be implemented as an integrated circuit (IC), a portion of an integrated circuit, a discrete electronic device, or other module, logic, hardware, software, firmware, or a combination thereof. Fig.14 The block diagram of UE 1400 is intended to show a high-level view of certain of the components of UE 1400. However, some of the components shown may be omitted, additional components may be present, and different arrangements of the components shown may occur in other implementations.

[0304] Components of UE 1400 may be coupled to various other components via one or more interconnects 1432, which may represent any type of interface, input / output, bus (local, system, or extension), transmission line, trace, or optical connection that allows various circuit components (on a common or different chip or chipset) to interact with each other.

[0305] The processor 1404 may include processor circuits such as, for example, a baseband processor circuit (BB) 1404A, a central processor unit circuit (CPU) 1404B, and a graphics processor unit circuit (GPU) 1404C. The processor 1404 may include any type of circuit or processor circuit that executes or otherwise operates computer-executable instructions (such as program codes, software modules, or functional processes from the memory / storage device 1412) to cause the UE 1400 to perform operations as described herein.

[0306] Processor 1404 may perform operations associated with slice priority optimization, such as frequency reselection optimization or PDU establishment optimization consistent with the embodiments described herein.

[0307] In some embodiments, the baseband processor circuit 1404A can access the communication protocol stack 1436 in the memory / storage device 1412 to communicate through a 3GPP compatible network. Generally speaking, the baseband processor circuit 1404A can access the communication protocol stack 1436 to perform the following operations: perform user plane functions at the PHY layer, MAC layer, RLC sublayer, PDCP sublayer, SDAP sublayer, and upper layers; and perform control plane functions at the PHY layer, MAC layer, RLC sublayer, PDCP sublayer, RRC layer, and NAS layer. In some embodiments, the PHY layer operations can be additionally / alternatively performed by components of the RF interface circuit 1408.

[0308] The baseband processor circuit 1404A may generate or process baseband signals or waveforms that carry information in a 3GPP-compatible network. In some embodiments, the waveforms used for NR may be based on cyclic prefix OFDM (CP-OFDM) in the uplink or downlink, and discrete Fourier transform spread OFDM (DFT-S-OFDM) in the uplink.

[0309] The memory / storage 1412 may include one or more non-transitory computer-readable media including instructions (e.g., the communication protocol stack 1436) that may be executed by one or more processors in the processor 1404 to cause the UE 1400 to perform various operations described herein. The memory / storage 1412 includes any type of volatile or non-volatile memory that may be distributed throughout the UE 1400. In some embodiments, some of the memory / storage 1412 may be located on the processor 1404 itself (e.g., L1 cache and L2 cache), while other memory / storage 1412 is located external to the processor 1404 but accessible via a memory interface. The memory / storage 1412 may include any suitable volatile or non-volatile memory, such as, but not limited to, dynamic random access memory (DRAM), static random access memory (SRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, solid-state memory, or any other type of memory device technology.

[0310] RF interface circuit 1408 may include transceiver circuits and radio frequency front end modules (RFEMs) that allow UE 1400 to communicate with other devices through a radio access network. RF interface circuit 1408 may include various elements arranged in a transmission path or a reception path. These elements may include, for example, switches, mixers, amplifiers, filters, synthesizer circuits, and control circuits.

[0311] In the receive path, the RFEM may receive the radiated signal from the air interface via the antenna structure 1426 and proceed to filter and amplify the signal (using a low noise amplifier). The signal may be provided to the transceiver's receiver, which down-converts the RF signal to a baseband signal that is provided to the baseband processor of the processor 1404.

[0312] In the transmit path, the transmitter of the transceiver up-converts the baseband signal received from the baseband processor and provides the RF signal to the RFEM. The RFEM may amplify the RF signal through a power amplifier before the signal is radiated across the air interface via the antenna 1426.

[0313] In various embodiments, the RF interface circuit 1408 may be configured to transmit / receive signals in a manner compatible with NR access technology.

[0314] Antenna 1426 may include antenna elements to convert electrical signals into radio waves to travel through the air and convert received radio waves into electrical signals. These antenna elements may be arranged into one or more antenna panels. Antenna 1426 may have antenna panels that are omnidirectional, directional, or a combination thereof to enable beamforming and multiple input / multiple output communications. Antenna 1426 may include: microstrip antennas; printed antennas fabricated on the surface of one or more printed circuit boards; patch antennas or phased array antennas. Antenna 1426 may have one or more panels designed for specific frequency bands including frequency bands in FR1 or FR2.

[0315] The user interface circuit 1416 includes various input / output (I / O) devices designed to enable the user to interact with the UE 1400. The user interface 1416 includes input device circuits and output device circuits. The input device circuit includes any physical or virtual means for accepting input, and in particular includes one or more physical or virtual buttons (e.g., reset button), physical keyboard, keypad, mouse, touch pad, touch screen, microphone, scanner, headset, etc. The output device circuit includes any physical or virtual component for displaying information or otherwise conveying information (such as sensor readings, actuator positions, or other similar information). The output device circuit may include any number or combination of audio or visual displays, in particular including one or more simple visual outputs / indicators (e.g., binary state indicators, such as light emitting diodes (LEDs) and multi-character visual outputs) or more complex outputs, such as display devices or touch screens (e.g., liquid crystal displays (LCDs), LED displays, quantum dot displays, and projectors), wherein the output of characters, graphics, multimedia objects, etc. is generated or produced by the operation of the UE 1400.

[0316] Sensors 1420 may include devices, modules, or subsystems that are designed to detect events or changes in their environment and send information about the detected events (sensor data) to some other device, module, or subsystem. Examples of such sensors include: an inertial measurement unit including an accelerometer, gyroscope, or magnetometer; a microelectromechanical system or nanoelectromechanical system including a three-axis accelerometer, a three-axis gyroscope, or a magnetometer; a liquid level sensor; a flow sensor; a temperature sensor (e.g., a thermistor); a pressure sensor; a barometric pressure sensor; a gravity meter; an altimeter; an image capture device (e.g., a camera or a lensless aperture); a light detection and ranging sensor; a proximity sensor (e.g., an infrared radiation detector, etc.); a depth sensor; an ambient light sensor; an ultrasonic transceiver; and a microphone or other similar audio capture device.

[0317] The driver circuit 1422 may include software elements and hardware elements for controlling a specific device embedded in, attached to, or otherwise communicatively coupled to the UE 1400. The driver circuit 1422 may include various drivers, thereby allowing other components to interact with or control various I / O devices that may be present in or connected to the UE 1400. For example, the driver circuit 1422 may include circuits for facilitating coupling a universal integrated circuit card (UICC) or a universal subscriber identity module (USIM) to the UE 1400. For additional examples, the driver circuit 1422 may include: a display driver for controlling and allowing access to a display device, a touch screen driver for controlling and allowing access to a touch screen interface, a sensor driver for obtaining sensor readings of the sensor circuit 1420 and controlling and allowing access to the sensor circuit 1420, a driver for obtaining an actuator position of an electromechanical component or controlling and allowing access to an electromechanical component, a camera driver for controlling and allowing access to an embedded image capture device, and an audio driver for controlling and allowing access to one or more audio devices.

[0318] The PMIC 1424 may manage the power provided to various components of the UE 1400. Specifically, with respect to the processor 1404, the PMIC 1424 may control power source selection, voltage scaling, battery charging, or DC-DC conversion.

[0319] In some embodiments, the PMIC 1424 may control or otherwise be a part of various power saving mechanisms of the UE 1400 including DRX, as discussed herein.

[0320] The battery 1428 can power the UE 1400, but in some examples, the UE 1400 can be installed and deployed in a fixed location and can have a power source coupled to the power grid. The battery 1428 can be a lithium-ion battery, a metal-air battery, such as a zinc-air battery, an aluminum-air battery, a lithium-air battery, etc. In some specific implementations, such as in vehicle-based applications, the battery 1428 can be a typical lead-acid car battery.

[0321] Fig.15 A network node 1500 is shown according to some embodiments. The network node 1500 may be similar to and substantially interchangeable with a base station 108, a device implementing one of the network hops, an integrated access and backhaul (IAB) node, a network controlled repeater, or a server in a core network or an external data network.

[0322] The network node 1500 may include a processor 1504 , RF interface circuitry 1508 (if implemented as an access node), core node (CN) interface circuitry 1512 , memory / storage circuitry 1516 , and antenna structures 1526 .

[0323] Components of network node 1500 may be coupled to various other components via one or more interconnects 1528 .

[0324] The processor 1504, RF interface circuit 1508, memory / storage circuit 1516 (including communication protocol stack 1510), antenna structure 1526 and interconnect 1528 may be similar to those of reference Fig.14 Like-named elements are shown and described.

[0325] Processor 1504 may perform operations associated with slice priority optimization such as frequency reselection optimization or PDU establishment optimization consistent with the embodiments described herein.

[0326] The CN interface circuit 1512 may provide a connection to a core network (e.g., a 5GC using a 5th Generation Core Network (5GC) compatible network interface protocol such as a Carrier Ethernet protocol or some other suitable protocol). The network connection may be provided to / from the network node 1500 via optical fiber or wireless backhaul. The CN interface circuit 1512 may include one or more dedicated processors or FPGAs for communicating using one or more of the aforementioned protocols. In some implementations, the CN interface circuit 1512 may include multiple controllers for providing connections to other networks using the same or different protocols.

[0327] In some embodiments, the network node 1500 may use antenna structures 1526, CN interface circuits, or other interface circuits to couple to a transmit receive point (TRP).

[0328] It is understood that the use of personally identifiable information should be subject to privacy policies and practices that are generally recognized to meet or exceed industry or government requirements for maintaining user privacy. Specifically, personally identifiable information data should be managed and processed to minimize the risk of unintentional or unauthorized access or use, and the nature of the authorized use should be clearly stated to users.

[0329] For one or more aspects, at least one of the components shown in one or more of the foregoing figures may be configured to perform one or more operations, techniques, processes, or methods described in the following example section. For example, the baseband circuit described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the following embodiments. For another example, the circuits associated with the UE, base station, network element, etc. described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the examples shown in the example section below.

[0330] Example

[0331] Embodiment 1 includes a method to be implemented by a user equipment (UE), the method comprising: receiving first configuration information via non-access stratum (NAS) signaling, and receiving second configuration information via broadcast system information; generating a slice priority network configuration based on the first configuration information and the second configuration information; determining that a slice associated with a service or application called by the UE is allowed based on the slice priority network configuration; and modifying a first packet data unit (PDU) session that existed before the UE called the service or application, or creating a second PDU session.

[0332] Embodiment 2 includes a method according to embodiment 1 or other embodiments herein, wherein the modifying the first PDU session or creating the second PDU session includes modifying the first PDU session, and the method further includes: determining that an aggregate maximum bit rate (AMBR) is associated with the slice; and based on the determination that the AMBR is associated with the slice, modifying the first PDU session that exists before the UE calls the service or application.

[0333] Embodiment 3 includes a method according to embodiment 1 or 2 or some other embodiments of the present invention, wherein the modification of the first PDU session or the creation of the second PDU session includes modifying the first PDU session, and the method further includes: determining that the service or application called by the UE requires non-guaranteed bit rate (non-GBR) quality of service (QoS); and based on the determination that the service or application called by the UE requires non-GBR QoS, modifying the first PDU session that existed before the UE called the service or application.

[0334] Embodiment 4 includes a method according to any one of embodiments 1 to 3 or some other embodiments of the present invention, wherein the modification of the first PDU session or the creation of the second PDU session includes creating a second PDU session, and the method further includes: determining that the service or application called by the UE requires a PDU session that supports ultra-reliable low-latency communication (URLLC) quality of service (QoS); determining that the first PDU session does not support URLLC QoS; and based on the determination that the first PDU session does not support URLLC QoS, creating the second PDU session that supports URLLC QoS.

[0335] Embodiment 5 includes a method according to any one of Embodiments 1 to 4 or some other embodiments herein, the method comprising: receiving first configuration information via non-access stratum (NAS) signaling, and receiving second configuration information via broadcast system information; generating a slice priority network configuration based on the first configuration information and the second configuration information; determining, based on the slice priority network configuration, that a slice associated with a service or application invoked by the UE is not allowed in a first tracking area (TA) associated with a serving cell of the UE; determining, based on the slice priority network configuration, that the slice is allowed in a second TA associated with a neighboring cell; determining whether all active packet data unit (PDU) sessions of the UE can continue in the neighboring cell; and determining whether to reselect to the neighboring cell based on the determination of whether all active PDU sessions of the UE can continue in the neighboring cell.

[0336] Embodiment 6 includes a method according to any one of Embodiments 1 to 5 or some other embodiments herein, the method further comprising: determining that all active PDU sessions of the UE can continue in the neighboring cell; reselecting the neighboring cell based on the determination that all active PDU sessions of the UE can continue in the neighboring cell of the second TA; sending a registration request message and requested network slice selection assistance information (NSSAI) including an indication of the slice; receiving a registration acceptance message including an allowed NSSAI; based on the allowed NSSAI, filling in the slice priority network configuration or dynamic slice priority decision table; and initiating a PDU session associated with the slice for the service or application called by the UE.

[0337] Embodiment 7 includes a method according to any one of Embodiments 1 to 6 or some other embodiments herein, the method further comprising: determining that not all active PDU sessions of the UE can be continued in the neighboring cell; identifying PDU sessions in the active PDU sessions that cannot be continued in the neighboring cell; releasing the PDU sessions in the active PDU sessions, or mapping the PDU sessions in the active PDU sessions to a default slice; and reselecting the neighboring cell based on the release or mapping of the PDU sessions in the active PDU sessions.

[0338] Embodiment 8 includes a method to be implemented by a user equipment (UE), the method comprising: receiving first configuration information via non-access stratum (NAS) signaling, and receiving second configuration information via broadcast system information; generating a slice priority network configuration based on the first configuration information and the second configuration information; determining, based on the slice priority network configuration, that a slice associated with a service or application called by the UE is not allowed in a current frequency band; determining, based on the slice priority network configuration, that the slice is allowed in an adjacent frequency band; determining whether the UE is able to measure a cell in the adjacent frequency band; and determining, based on the determination of whether the UE is able to measure the cell in the adjacent frequency band, whether to perform inter-frequency reselection, map the service or application called by the UE to a packet data unit (PDU) session that existed before the UE called the service or application, or reject the service or application called by the UE.

[0339] Embodiment 9 includes the method according to embodiment 8 or some other embodiments of the present invention, wherein the method further includes: determining that the UE is capable of measuring the cell in the adjacent frequency band; determining a list of measured cells in the adjacent frequency band based on the determination that the UE is capable of measuring the cell in the adjacent frequency band; and determining whether all active packet data unit (PDU) sessions of the UE can continue in a candidate cell in the list of measured cells in the adjacent frequency band.

[0340] Embodiment 10 includes a method according to embodiment 8 or 9 or some other embodiments herein, the method further comprising: determining that all active PDU sessions of the UE can continue in the candidate cell in the adjacent frequency band; and performing inter-frequency reselection of the candidate cell in the adjacent frequency band.

[0341] Embodiment 11 includes a method according to any one of Embodiments 8 to 10 or some other embodiments herein, the method further comprising: determining that not all active PDU sessions of the UE can be continued in the candidate cell in the adjacent frequency band; identifying PDU sessions among the active PDU sessions that cannot be continued in the adjacent cell; releasing the PDU session, or mapping the PDU session to a default slice; and reselecting the candidate cell based on releasing the PDU session or mapping the PDU session to the default slice.

[0342] Embodiment 12 includes a method according to any one of Embodiments 8 to 11 or some other embodiments herein, the method further comprising: determining that the UE cannot measure cells in the adjacent frequency band; determining whether the service or application called by the UE requires quality of service (QoS) that is not supported by the default slice; and based on the determination of whether the service or application called by the UE requires QoS that is not supported by the default slice, determining whether to reject the service or application called by the UE or to map the service or application called by the UE to a packet data unit (PDU) session that existed before the UE called the service or application. Embodiment 13 includes a method for operating a user equipment (UE), the method comprising: receiving first configuration information via non-access stratum (NAS) signaling, and receiving second configuration information via broadcast system information; generating a slice priority network configuration based on the first configuration information and the second configuration information; determining whether a slice associated with a service or application called by the UE is allowed in a serving cell based on the slice priority network configuration; and determining whether to perform intra-frequency reselection, map the service or application called by the UE to a first packet data unit (PDU) session that existed before the UE called the service or application, reject the service or application called by the UE, or initiate a second PDU session based on the determination of whether the slice associated with the service or application called by the UE is allowed in the serving cell.

[0343] Embodiment 14 includes the method according to embodiment 13 or some other embodiments of the present invention, wherein the method further includes: determining that the slice is allowed in the service cell based on the slice priority network configuration; and initiating a PDU session for the service or application called by the UE.

[0344] Embodiment 15 includes a method according to any one of embodiments 13 or 14 or some other embodiments herein, the method further comprising: determining that the slice is not allowed in the serving cell based on the slice priority network configuration; determining that the UE is capable of measuring neighboring cells; determining a list of measured neighboring cells including the neighboring cells; and determining whether all active PDU sessions can continue in the neighboring cells.

[0345] Embodiment 16 includes a method according to any one of embodiments 13 to 15 or some other embodiments herein, the method further comprising: determining that all active PDU sessions can continue in the neighboring cell; and performing intra-frequency reselection of the neighboring cell.

[0346] Embodiment 17 includes a method according to any one of Embodiments 13 to 16 or some other embodiments herein, the method further comprising: determining that not all active PDU sessions can continue in the neighboring cell; identifying a third PDU session among the active PDU sessions that cannot continue in the neighboring cell; releasing the third PDU session, or mapping the third PDU session to a default slice; and reselecting the neighboring cell based on releasing the third PDU session or mapping the third PDU session to the default slice.

[0347] Embodiment 18 includes a method according to any one of Embodiments 13 to 17 or some other embodiments herein, the method further comprising: determining, based on the slice priority network configuration, that the slice is not allowed in the serving cell; determining that the UE cannot measure neighboring cells; determining whether the service or application called by the UE requires quality of service (QoS) that is not supported by the default slice; and based on the determination of whether the service or application called by the UE requires QoS that is not supported by the default slice, determining whether to reject the service or application called by the UE or to map the service or application called by the UE to the first PDU session that existed before the UE called the service or application.

[0348] Embodiment 19 includes a method for operating a user equipment (UE), the method comprising: receiving first configuration information via non-access stratum (NAS) signaling, and receiving second configuration information via broadcast system information or access stratum (AS); generating a slice priority network configuration based on the first configuration information and the second configuration information; determining, based on the slice priority network configuration, that a slice associated with a service or application invoked by the UE is allowed; determining that a first network slice access group (NSAG) and a second NSAG support the slice; determining, based on the slice priority network configuration, a relative priority of the first NSAG and the second NSAG; and determining, based on the determination of the relative priority of the first NSAG and the second NSAG, whether to reselect to a first highest priority frequency in a highest priority tracking area (TA), reselect to a second highest priority frequency based on the second configuration information, stay at a currently occupied frequency, or reselect to a second priority frequency.

[0349] Embodiment 20 includes the method according to embodiment 19 or some other embodiments of the present invention, wherein the method further includes: determining that the relative priorities of the first NSAG and the second NSAG are equal based on the slice priority network configuration; and determining to stay at the currently occupied frequency based on the determination that the first NSAG and the second NSAG have equal priorities.

[0350] Embodiment 21 includes a method according to any one of embodiments 19 or 20 or some other embodiments herein, the method further comprising: determining, based on the slice priority network configuration, that the relative priorities of the first NSAG and the second NSAG are unequal; determining a high-priority NSAG based on the relative priorities of the first NSAG and the second NSAG; and determining whether the UE pre-occupies a TA that supports the high-priority NSAG.

[0351] Embodiment 22 includes a method according to any one of embodiments 19 to 21 or some other embodiments herein, the method further comprising: determining that the UE is not pre-occupied with the TA supporting the high priority NSAG; determining the highest priority TA supporting the high priority NSAG based on the slice priority network configuration; determining the first highest priority frequency in the highest priority TA supporting the high priority NSAG; and reselecting to the first highest priority frequency in the highest priority TA supporting the high priority NSAG.

[0352] Embodiment 23 includes a method according to any one of embodiments 19 to 22 or some other embodiments herein, the method further comprising: determining that the UE occupies the TA that supports the high priority NSAG; determining the second highest priority frequency based on the second configuration information; and determining whether the UE occupies the second highest priority frequency based on the second configuration information.

[0353] Embodiment 24 includes a method according to any one of embodiments 19 to 23 or some other embodiments herein, the method further comprising: determining that the UE is not pre-occupied with the second highest priority frequency based on the second configuration information; and reselecting to the second highest priority frequency based on the second configuration information.

[0354] Embodiment 25 includes a method according to any one of embodiments 19 to 24 or some other embodiments herein, the method further comprising: determining that the UE is pre-occupied with the second highest priority frequency based on the second configuration information; determining that the reference signal received power (RSRP) associated with the second priority frequency is greater than the RSRP associated with the second highest priority frequency based on the second configuration information by more than a threshold; and reselecting to the second priority frequency based on the determination that the RSRP associated with the second priority frequency is greater than the RSRP associated with the second highest priority frequency based on the second configuration information by more than the threshold.

[0355] Another embodiment may include an apparatus comprising logic components, modules, or circuits for performing one or more elements of a method as described or related to any of Embodiments 1 to 25, or any other method or process described herein.

[0356] Another embodiment may include a method, technique or process described or related to any one of embodiments 1 to 25 or parts or components thereof.

[0357] Another embodiment may include a device comprising: one or more processors and one or more computer-readable media, the one or more computer-readable media comprising instructions that, when executed by the one or more processors, cause the one or more processors to perform methods, techniques, or processes described in or related to any one of embodiments 1 to 25 or portions thereof.

[0358] Another embodiment comprises a signal as described or relating to any one of embodiments 1 to 25, or parts or components thereof.

[0359] Another embodiment may include a datagram, information element, packet, frame, segment, PDU or message as described or related to any one of embodiments 1 to 25 or parts or components thereof or otherwise described in the present disclosure.

[0360] Another embodiment may include a signal encoded with data as described or associated with any one of embodiments 1 to 25, or parts or components thereof, or otherwise described in this disclosure.

[0361] Another embodiment may include a signal encoded with a datagram, IE, packet, frame, segment, PDU, or message as described or related to any one of embodiments 1 to 25 or parts or components thereof or otherwise described in the present disclosure.

[0362] Another embodiment may include an electromagnetic signal carrying computer-readable instructions, wherein execution of these computer-readable instructions by one or more processors will cause the one or more processors to perform a method, technique, or process described or related to any one or part of Embodiments 1 to 25.

[0363] Another embodiment may include a computer program including instructions, wherein execution of the program by a processing element causes the processing element to perform a method, technique, or process described or related to any one or part of Embodiments 1 to 25.

[0364] Another embodiment may include a signal in a wireless network as shown and described herein.

[0365]

[0013] Another embodiment may include a method of communicating in a wireless network as shown and described herein.

[0366]

[0013] Another embodiment may include a system for providing wireless communications as shown and described herein.

[0367]

[0013] Another embodiment may include an apparatus for providing wireless communications as shown and described herein.

[0368] Unless explicitly stated otherwise, any of the above examples may be combined with any other example (or combination of examples). The foregoing description of one or more specific implementations provides illustration and description, but is not intended to be exhaustive or to limit the scope of the various aspects to the precise form disclosed. In view of the above teachings, modifications and variations are possible or can be obtained from the practice of various aspects.

[0369] Although the above aspects have been described in considerable detail, numerous variations and modifications will become apparent to those skilled in the art once the above disclosure is fully appreciated. It is intended that the following claims be interpreted to include all such variations and modifications.

Claims

1. A method, comprising: Processing first configuration information received via non-access stratum (NAS) signaling and second configuration information received via broadcast system information; Generate a slice priority network configuration based on the first configuration information and the second configuration information; Determining, based on the slice priority network configuration, that a slice associated with the service or application is allowed; as well as A first packet data unit (PDU) session existing before the service or application is invoked is modified, or a second PDU session is created.

2. The method according to claim 1, wherein the modifying the first PDU session or creating the second PDU session comprises modifying the first PDU session, and the method further comprises: determining an aggregate maximum bit rate (AMBR) associated with the slice; as well as Based on the determination that the AMBR is associated with the slice, the first PDU session existing before the service or application is invoked is modified.

3. The method according to claim 1, wherein the modifying the first PDU session or creating the second PDU session comprises modifying the first PDU session, and the method further comprises: determining that the service or application is associated with a non-guaranteed bit rate (non-GBR) quality of service (QoS); as well as Based on the determination that the service or application is associated with the non-GBR QoS, the first PDU session existing before the service or application is invoked is modified.

4. The method according to claim 1, wherein the modifying the first PDU session or creating the second PDU session comprises creating the second PDU session, and the method further comprises: determining that the service or application is associated with a PDU session supporting Ultra Reliable Low Latency Communication (URLLC) Quality of Service (QoS); Determining that the first PDU session does not support URLLC QoS; as well as Based on the determination that the first PDU session does not support URLLC QoS, the second PDU session supporting URLLC QoS is created.

5. The method according to claim 1, wherein the modifying the first PDU session or creating the second PDU session comprises creating the second PDU session, and the method further comprises: determining that the service or application is associated with a reflective quality of service (QoS); Determining that the first PDU session does not support the reflective QoS; as well as The second PDU session supporting reflective QoS is created.

6. The method according to claim 1, wherein the modifying the first PDU session or creating the second PDU session comprises creating the second PDU session, and the method further comprises: Determining that the slice is allowed in a tracking area (TA); determining that the slice is allowed in the frequency band; determining that the slice is allowed in a physical cell identifier (PCI); as well as The second PDU session supporting reflective QoS is created.

7. A baseband processor, comprising: A processing circuit, the processing circuit is used to: Processing first configuration information received via non-access stratum (NAS) signaling and second configuration information received via broadcast system information; Generate a slice priority network configuration based on the first configuration information and the second configuration information; Based on the slice priority network configuration, determining that a slice associated with the service or application is not allowed in a first tracking area (TA) associated with a current serving cell; Based on the slice priority network configuration, determining that the slice is allowed in a second TA associated with a neighboring cell; as well as The neighboring cell is reselected in the second TA.

8. The baseband processor of claim 7, wherein the processing circuit is further configured to: determining that all active PDU sessions can continue in the neighboring cell; generating a registration request message to request network slice selection assistance information (NSSAI), the registration request message being configured to include an indication of the slice; Process the registration accept message including the allowed NSSAI; Based on the allowed NSSAI, populate the slice priority network configuration or dynamic slice priority decision table; as well as Initiate a PDU session associated with the slice for the service or application.

9. The baseband processor of claim 7, wherein the processing circuit is further configured to: determining that not all active PDU sessions can continue in the neighboring cell; identifying a PDU session among the active PDU sessions that cannot be continued in the neighboring cell; and Release the PDU session in the active PDU session, or map the PDU session in the active PDU session to a default slice PDU session.

10. A device, comprising: Memory circuit; and a processing circuit, the processing circuit being coupled to the memory circuit, the processing circuit being configured to: Processing first configuration information received via non-access stratum (NAS) signaling and second configuration information received via broadcast system information; Generate a slice priority network configuration based on the first configuration information and the second configuration information; as well as determining whether a slice associated with a service or an application is allowed in a frequency band, wherein in response to determining that the slice is not allowed in the frequency band: determining whether cells in adjacent frequency bands can be measured; as well as Based on the determining whether the cell in the adjacent frequency band can be measured, determining whether: performing inter-frequency reselection; mapping the service or application to a first packet data unit (PDU) session that existed before the service or application was invoked; or Deny said service or application.

11. The apparatus according to claim 10, wherein the determining whether the cell in the adjacent frequency band can be measured comprises determining that the cell in the adjacent frequency band can be measured, and the processing circuit is further configured to: Identifying a list of measured cells in the adjacent frequency band; and A determination is made as to whether all active packet data unit (PDU) sessions can continue in a candidate cell in the measured cell list in the neighboring frequency band.

12. The apparatus according to claim 11, wherein the determining whether all active PDU sessions can continue in the candidate cell in the measured cell list in the adjacent frequency band comprises determining that all active PDU sessions can continue in the candidate cell in the adjacent frequency band, and the processing circuit is further configured to: Inter-frequency reselection is performed for the candidate cell in the adjacent frequency band.

13. The apparatus of claim 11, wherein the determining whether all active PDU sessions can continue in the candidate cell in the measured cell list in the adjacent frequency band comprises determining that not all active PDU sessions can continue in the candidate cell in the adjacent frequency band, and the processing circuit is further configured to: Identifying a second PDU session in the active PDU session that cannot be continued in the neighboring cell; releasing the second PDU session, or mapping the second PDU session to a default slice; and Based on releasing the second PDU session or mapping the second PDU session to the default slice, reselecting the candidate cell.

14. The apparatus of claim 10, wherein the determining whether the cell in the adjacent frequency band can be measured comprises determining that the cell in the adjacent frequency band cannot be measured, and the processing circuit is further configured to: determining that the service or application is associated with a quality of service (QoS) that is not supported by the default slice, and denying the service or application; or Determining that the service or application is associated with a quality of service (QoS) supported by a default slice, and mapping the service or application to the first PDU session that existed before the service or application was invoked.

15. The apparatus of claim 10, wherein the determining whether the slice is allowed in the frequency band comprises determining that the slice is allowed in the frequency band, and the processing circuit is further configured to: Processing first configuration information received via non-access stratum (NAS) signaling and second configuration information received via broadcast system information; Generate a slice priority network configuration based on the first configuration information and the second configuration information; Based on the slice priority network configuration, determining that a slice associated with the service or application is not allowed in a current physical cell identifier (PCI); Determine whether adjacent PCIs can be measured; as well as Based on the determining whether the adjacent PCI can be measured, determining whether: Perform intra-frequency reselection; mapping the service or application to a first packet data unit (PDU) session that existed before the service or application was invoked; or Deny said service or application.

16. The apparatus of claim 15, wherein the determining whether the adjacent PCI can be measured comprises determining that the adjacent PCI can be measured, and the processing circuit is further configured to: identifying a measured neighboring PCI list including the neighboring PCI; and A determination is made as to whether all active PDU sessions can continue in the adjacent PCI.

17. The apparatus of claim 16, wherein the determining whether all active PDU sessions can continue in the adjacent PCI comprises determining that all active PDU sessions can continue in the adjacent PCI, and the processing circuit is further configured to: An intra-frequency reselection is performed on the neighboring PCI.

18. The apparatus of claim 16, wherein the determining whether all active PDU sessions can continue in the adjacent PCI comprises determining that not all active PDU sessions can continue in the adjacent PCI, and the processing circuit is further configured to: Identifying a second PDU session in the active PDU session that cannot be continued in the adjacent PCI; releasing the second PDU session, or mapping the second PDU session to a default slice; and An intra-frequency reselection is performed on the neighboring PCI.

19. The apparatus of claim 15, wherein the determining whether the neighboring PCI can be measured comprises determining that the neighboring PCI cannot be measured, and the processing circuit is further configured to: determining that the service or application is associated with a quality of service (QoS) that is not supported by the default slice; and Deny said service or application.

20. The apparatus of claim 15, wherein the determining whether the neighboring PCI can be measured comprises determining that the neighboring PCI cannot be measured, and the processing circuit is further configured to: determining that the service or application is associated with a quality of service (QoS) supported by a default slice; and The service or application is mapped to the first PDU session that existed before the service or application was invoked.

Images