Network (NW) technologies for constraining the simultaneous use of network slices

Abstract

The technology discussed herein facilitates configuring network slices for a user equipment (UE) that supports simultaneous operation of constrained slices. The technology may include: receiving a registration request message for requesting registration on a set of requested network slices; registering the UE with a set of allowed network slices; and generating a registration accept message for transmission, the registration accept message indicating that the UE is registered with the set of allowed network slices, wherein the registration accept message indicates slice compatibility information for each allowed network slice in the set of allowed network slices for the UE, wherein the slice compatibility information for each allowed network slice indicates whether other configured network slices in the set of configured network slices are compatible with the configured network slice for simultaneous operation by the UE.

Description

[0001] Priority claim

[0002] This application claims priority to Indian Patent Application No. 202041034805 filed on August 13, 2020, which is incorporated herein by reference. Background Art

[0003] Mobile communications in the next generation of wireless communication systems, 5G or New Radio (NR) networks, can provide ubiquitous connectivity and access to information and the ability to share data on a global scale. 5G networks and network slicing can provide a unified, service-based framework that will target common and sometimes conflicting performance standards and provide services to a wide variety of application domains ranging from enhanced mobile broadband (eMBB) to massive machine-type communications (mMTC), ultra-reliable low-latency communications (URLLC), and other communications. Generally speaking, NR can include further developments based on the 3rd Generation Partnership Project (3GPP) Long Term Evolution (LTE) Advanced technology and additional enhanced radio access technologies (RATs) to achieve seamless and faster wireless connectivity solutions. BRIEF DESCRIPTION OF THE DRAWINGS

[0004] Figure 1 is a block diagram illustrating the architecture of a system including a core network (CN), eg, a fifth generation (5G) CN (5GC), according to various aspects.

[0005] Figure 2 is a diagram illustrating example components of an apparatus that may be employed in accordance with various aspects discussed herein.

[0006] Figure 3 is a diagram illustrating an example interface of baseband circuitry that may be employed in accordance with various aspects discussed herein.

[0007] Figure 4 is a block diagram illustrating a system according to various aspects discussed herein that facilitates network slicing-related configuration for a user equipment (UE) subject to constraints on simultaneous use of slices.

[0008] Figure 5 is a diagram showing an example of network slicing incorporating various aspects discussed herein.

[0009] Figure 6 A call flow diagram of a method for establishing a network slice for a UE is shown in conjunction with various aspects discussed herein.

[0010] Figure 7 A first exemplary call flow for slice registration in conjunction with simultaneous slice usage constraints is shown in accordance with various aspects discussed herein.

[0011] Figure 8 A second exemplary call flow for slice registration in conjunction with simultaneous slice usage constraints is shown in accordance with various aspects discussed herein.

[0012] Figure 9 An exemplary table is shown according to various aspects discussed herein, showing examples of three allowed slices, indicating the slice / service type (SST) values, optional SD values, and compatibility between slices.

[0013] Figure 10 According to a third set of aspects discussed herein, an exemplary table is shown showing compatibility between slices based on explicit indication of slice incompatibility.

[0014] Figure 11 According to the third set of aspects discussed herein, an exemplary table is shown in which compatibility between slices is shown via an indication of slice incompatibility based on SST.

[0015] Figure 12 According to the third set of aspects discussed herein, an exemplary table is shown showing compatibility between slices via slice incompatibility indication based on GSMA-identified constraints.

[0016] Figure 13 A diagram of an example call flow involving a UE selectively establishing a protocol data unit (PDU) session is shown in conjunction with various aspects discussed herein.

[0017] Figure 14 A diagram of a first example call flow employing a priority release slice IE or value is shown in conjunction with various aspects discussed herein.

[0018] Figure 15 In conjunction with various aspects discussed herein, a diagram of a second exemplary call flow employing a priority release slice information element (IE) or value is shown.

[0019] Figure 16 A diagram of a third example call flow employing a priority release slice IE or value is shown in conjunction with various aspects discussed herein.

[0020] Figure 17 A diagram of an example call flow for implicitly releasing a PDU session using the PDU Session Status IE is shown in conjunction with various aspects discussed herein.

[0021] Figure 18 A diagram of an example call flow for establishing user plane resources using uplink data status is shown in conjunction with various aspects discussed herein.

[0022] Figure 19In combination with the various aspects discussed herein, a diagram is shown of an exemplary call flow for locally releasing a PDU session using the PDU Session Status IE when the UE is not allowed to register for constrained slices. DETAILED DESCRIPTION

[0023] The present disclosure will now be described with reference to the accompanying drawings, wherein similar reference numerals are used to refer to similar elements throughout the text, and the structures and devices shown therein need not be drawn to scale. As used herein, the terms "component", "system", "interface", etc. are intended to refer to entities, hardware, software (e.g., in execution) and / or firmware related to a computer. For example, a component can be a processor (e.g., a microprocessor, a controller or other processing device), a process running on a processor, a controller, an object, an executable file, a program, a storage device, a computer, a tablet computer and / or a user equipment with a processing device (e.g., a mobile phone or other devices configured to communicate via a 3GPP RAN, etc.). By way of example, an application and a server running on a server can also be a component. One or more components can reside in a process, and a component can be located on a computer and / or distributed between two or more computers. A group of elements or a group of other components can be described herein, wherein the term "group" can be interpreted as "one or more" unless the context indicates otherwise (e.g., "empty group", "a group of two or more Xs", etc.). A “subset” of a set S is a “set” that can be either set S or a “proper subset”, where every element of the proper subset is an element of set S, but set S includes at least one element that is not an element of a proper subset of set S.

[0024] In addition, the components can execute from various computer-readable storage media having various data structures stored thereon, such as using modules, for example. The components can communicate via local and / or remote processes, such as according to signals having one or more data packets (e.g., data from one component interacts with another component in a local system, a distributed system, and / or across a network, such as the Internet, a local area network, a wide area network, or a similar network with other systems via signals).

[0025] As another example, a component may be a device that has a specific functionality provided by a mechanical component that operates through electrical or electronic circuitry, where the electrical or electronic circuitry may be operated by a software application or firmware application executed by one or more processors. The one or more processors may be internal or external to the device and may execute at least a portion of the software or firmware application. As another example, a component may be a device that provides a specific functionality through an electronic component without the need for a mechanical component; the electronic component may include one or more processors therein to execute at least a portion of the software and / or firmware that provides the functionality of the electronic component.

[0026] The use of the word "exemplary" is intended to present concepts in a concrete manner. As used in this application, the term "or" is intended to mean an inclusive "or" rather than an exclusive "or." That is, unless otherwise specified or clear from the context, "X employs A or B" is intended to mean any natural inclusive permutation. That is, if X employs A; X employs B; or X employs both A and B, then "X employs A or B" is satisfied in any of the foregoing cases. In addition, the articles "a" and "an" as used in this application and the appended claims should generally be construed to mean "one or more," unless otherwise specified or clear from the context to be directed to the singular. Furthermore, to the extent that the terms "comprising," "including," "having," "having," "with," or variations thereof are used in the detailed description and claims, such terms are intended to be inclusive in a manner similar to the term "comprising." Furthermore, where one or more numbered items are discussed (e.g., "a first X," "a second X," etc.), generally, the one or more numbered items can be different or they can be the same, but in some cases, the context may indicate that they are different or that they are the same.

[0027] As used herein, the term "circuitry" may refer to, may be part of, or may include an application-specific integrated circuit (ASIC), electronic circuit, processor (shared, dedicated, or group), and / or memory (shared, dedicated, or group) that executes one or more software or firmware programs, combinational logic circuits, and / or other suitable hardware components that provide the described functionality. In some aspects, a circuit may be implemented in one or more software or firmware modules, or functionality associated with the circuit may be implemented by one or more software or firmware modules. In some aspects, a circuit may include logic components that may operate at least partially in hardware.

[0028]

[0010] Various aspects discussed herein may be directed to facilitating wireless communications, and the nature of these communications may vary.

[0029] 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 authorized use should be clearly stated to users.

[0030] Aspects described herein may be implemented into a system using any suitably configured hardware and / or software. Figure 1 The architecture of a system 100 including a core network (CN) 120 (e.g., a fifth generation (5G) CN (5GC)) according to various aspects is shown. The system 100 is shown to include: a UE 101, which can be the same as or similar to one or more other UEs discussed herein; a third generation partnership project (3GPP) radio access network (wireless AN or RAN) or other (e.g., non-3GPP) AN, (R)AN 110, which can include one or more RAN nodes (e.g., evolved Node B (eNB)), next generation Node B (gNB and / or other nodes) or other nodes or access points; and a data network (DN) 103, which can be, for example, operator services, Internet access, or third-party services; and a fifth generation core network (5GC) 120. 5GC 120 may include one or more of the following functions and network components: Authentication Server Function (AUSF) 122, Access and Mobility Management Function (AMF) 121, Session Management Function (SMF) 124, Network Exposure Function (NEF) 123, Policy Control Function (PCF) 126, Network Repository Function (NRF) 125, Unified Data Management (UDM) 127, Application Function (AF) 128, User Plane Function (UPF) 102, and Network Slice Selection Function (NSSF) 129, which may be connected by various interfaces and / or reference points, such as Figure 1 shown.

[0031] Figure 21. Example components of a device 200 according to some aspects are shown. In some aspects, the device 200 may include application circuitry 202, baseband circuitry 204, radio frequency (RF) circuitry 206, front-end module (FEM) circuitry 208, one or more antennas 210, and power management circuitry (PMC) 212 (coupled together at least as shown). The components of the illustrated device 200 may be included in a UE or a RAN node. In some aspects, the device 200 may include fewer components (e.g., a RAN node may not utilize application circuitry 202 but instead include a processor / controller to process IP data received from a CN such as a 5GC 120 or an evolved packet core (EPC)). In some aspects, the device 200 may include additional components such as, for example, memory / storage, a display, a camera, sensors (including one or more temperature sensors, such as a single temperature sensor, multiple temperature sensors at different locations in the device 200, etc.), or input / output (I / O) interfaces. In other aspects, the components described below may be included in more than one device (e.g., the circuitry may be separately included in more than one device for a Cloud-RAN (C-RAN) implementation).

[0032] The application circuitry 202 may include one or more application processors. For example, the application circuitry 202 may include circuitry such as, but not limited to, one or more single-core or multi-core processors. The processors may include any combination of general-purpose processors and specialized processors (e.g., graphics processors, application processors, etc.). The processors may be coupled to or include memory / storage and may be configured to execute instructions stored in the memory / storage to enable various applications or operating systems to run on the device 200. In some aspects, the processors of the application circuitry 202 may process IP data packets received from the EPC.

[0033] The baseband circuitry 204 may include circuitry such as, but not limited to, one or more single-core or multi-core processors. The baseband circuitry 204 may include one or more baseband processors or control logic to process baseband signals received from the receive signal path of the RF circuitry 206 and generate baseband signals for the transmit signal path of the RF circuitry 206. The baseband circuitry 204 may interact with the application circuitry 202 to generate and process baseband signals and control the operation of the RF circuitry 206. For example, in some aspects, the baseband circuitry 204 may include a third generation (3G) baseband processor 204A, a fourth generation (4G) baseband processor 204B, a fifth generation (5G) baseband processor 204C, or other baseband processors 204D for other existing, developing, or future generations (e.g., second generation (2G), sixth generation (6G), etc.). The baseband circuitry 204 (e.g., one or more baseband processors 204A-D) may handle various radio control functions that may communicate with one or more radio networks via the RF circuitry 206. In other aspects, some or all of the functionality of baseband processors 204A-D may be included in a module stored in memory 204G and may be executed via central processing unit (CPU) 204E. Radio control functions may include, but are not limited to, signal modulation / demodulation, encoding / decoding, radio frequency shifting, etc. In some aspects, the modulation / demodulation circuitry of baseband circuitry 204 may include fast Fourier transform (FFT), precoding, or constellation mapping / demapping functionality. In some aspects, the encoding / decoding circuitry of baseband circuitry 204 may include convolution, tail-biting convolution, turbo, Viterbi, or low-density parity check (LDPC) encoder / decoder functionality. Aspects of modulation / demodulation and encoder / decoder functionality are not limited to these examples and in other aspects may include other suitable functionality.

[0034] In some aspects, the baseband circuitry 204 may include one or more audio digital signal processors (DSPs) 204F. The audio DSPs 204F may include components for compression / decompression and echo cancellation, and in other aspects may include other suitable processing elements. In some aspects, the components of the baseband circuitry may be suitably combined in a single chip, a single chipset, or disposed on the same circuit board. In some aspects, some or all of the components of the baseband circuitry 204 and the application circuitry 202 may be implemented together, such as on a system on a chip (SOC).

[0035] In some aspects, the baseband circuitry 204 can provide communications compatible with one or more radio technologies. For example, in some aspects, the baseband circuitry 204 can support communications with NG-RAN, Evolved Universal Terrestrial Radio Access Network (EUTRAN), or other wireless metropolitan area networks (WMANs), wireless local area networks (WLANs), wireless personal area networks (WPANs), etc. Aspects in which the baseband circuitry 204 is configured to support radio communications of more than one wireless protocol can be referred to as multi-mode baseband circuitry.

[0036] RF circuitry 206 can communicate with a wireless network using modulated electromagnetic radiation through a non-solid medium. In various aspects, RF circuitry 206 can include switches, filters, amplifiers, etc. to facilitate communication with the wireless network. RF circuitry 206 can include a receive signal path, which can include circuitry for down-converting RF signals received from FEM circuitry 208 and providing a baseband signal to baseband circuitry 204. RF circuitry 206 can also include a transmit signal path, which can include circuitry for up-converting baseband signals provided by baseband circuitry 204 and providing an RF output signal to FEM circuitry 208 for transmission.

[0037] In some aspects, the receive signal path of RF circuitry 206 may include mixer circuitry 206a, amplifier circuitry 206b, and filter circuitry 206c. In some aspects, the transmit signal path of RF circuitry 206 may include filter circuitry 206c and mixer circuitry 206a. RF circuitry 206 may also include synthesizer circuitry 206d for synthesizing frequencies used by mixer circuitry 206a in the receive and transmit signal paths. In some aspects, mixer circuitry 206a in the receive signal path may be configured to downconvert the RF signal received from FEM circuitry 208 based on the synthesized frequency provided by synthesizer circuitry 206d. Amplifier circuitry 206b may be configured to amplify the downconverted signal, and filter circuitry 206c may be a low-pass filter (LPF) or a band-pass filter (BPF) configured to remove unwanted signals from the downconverted signal to generate an output baseband signal. The output baseband signal may be provided to baseband circuitry 204 for further processing. In some aspects, the output baseband signal can be a zero-frequency baseband signal, although this is not required.In some aspects, the mixer circuit 206a of the receive signal path can include a passive mixer, although the scope of the various aspects is not limited in this respect.

[0038] In some aspects, mixer circuit 206a of the transmit signal path may be configured to upconvert an input baseband signal based on a synthesized frequency provided by synthesizer circuit 206d to generate an RF output signal for FEM circuit 208. The baseband signal may be provided by baseband circuit 204 and may be filtered by filter circuit 206c.

[0039] In some aspects, the mixer circuit 206a of the receive signal path and the mixer circuit 206a of the transmit signal path may include two or more mixers and may be arranged for quadrature down-conversion and up-conversion, respectively. In some aspects, the mixer circuit 206a of the receive signal path and the mixer circuit 206a of the transmit signal path may include two or more mixers and may be arranged for image rejection (e.g., Hartley image rejection). In some aspects, the mixer circuit 206a of the receive signal path and the mixer circuit 206a of the transmit signal path may be arranged for direct down-conversion and direct up-conversion, respectively. In some aspects, the mixer circuit 206a of the receive signal path and the mixer circuit 206a of the transmit signal path may be configured for superheterodyne operation.

[0040] In some aspects, the output baseband signal and the input baseband signal can be analog baseband signals, although the scope of the various aspects is not limited in this respect. In some alternative aspects, the output baseband signal and the input baseband signal can be digital baseband signals. In these alternative aspects, the RF circuitry 206 can include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuitry, and the baseband circuitry 204 can include a digital baseband interface to communicate with the RF circuitry 206.

[0041] In some dual-mode aspects, separate radio IC circuits may be provided to process signals for each spectrum, although the scope of the various aspects is not limited in this respect.

[0042] In some aspects, the synthesizer circuit 206 d can be a fractional-N synthesizer or a fractional-N / N+1 synthesizer, although the scope of the various aspects is not limited in this respect, as other types of frequency synthesizers may be suitable. For example, the synthesizer circuit 206 d can be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer including a phase-locked loop with a frequency divider.

[0043] Synthesizer circuit 206d may be configured to synthesize an output frequency based on the frequency input and the divider control input for use by mixer circuit 206a of RF circuit 206. In some aspects, synthesizer circuit 206d may be a fractional-N / N+1 synthesizer.

[0044] In some aspects, the frequency input can be provided by a voltage controlled oscillator (VCO), but this is not required. The divider control input can be provided by the baseband circuitry 204 or the application circuitry 202 depending on the desired output frequency. In some aspects, the divider control input (e.g., N) can be determined from a lookup table based on the channel indicated by the application circuitry 202.

[0045] The synthesizer circuit 206d of the RF circuit 206 may include a frequency divider, a delay-locked loop (DLL), a multiplexer, and a phase accumulator. In some aspects, the frequency divider may be a dual-mode frequency divider (DMD), and the phase accumulator may be a digital phase accumulator (DPA). In some aspects, the DMD may be configured to divide the input signal by N or N+1 (e.g., based on a carry output) to provide a fractional division ratio. In some exemplary aspects, the DLL may include a cascaded, tunable delay element, a phase detector, a charge pump, and a set of D-type flip-flops. In these aspects, the delay element may be configured to divide the VCO cycle into Nd equal phase groups, where Nd is the number of delay elements in the delay line. In this way, the DLL provides negative feedback to help ensure that the total delay through the delay line is one VCO cycle.

[0046] In some aspects, the synthesizer circuit 206d can be configured to generate a carrier frequency as the output frequency, while in other aspects, the output frequency can be a multiple of the carrier frequency (e.g., twice the carrier frequency, four times the carrier frequency) and used with a quadrature generator and divider circuit to generate multiple signals at the carrier frequency with multiple different phases relative to each other. In some aspects, the output frequency can be the LO frequency (fLO). In some aspects, the RF circuit 206 can include an IQ / polarity converter.

[0047] The FEM circuitry 208 may include a receive signal path that may include circuitry configured to operate on RF signals received from one or more antennas 210, amplify the received signals, and provide an amplified version of the received signals to the RF circuitry 206 for further processing. The FEM circuitry 208 may also include a transmit signal path that may include circuitry configured to amplify transmit signals provided by the RF circuitry 206 for transmission via one or more of the one or more antennas 210. In various aspects, amplification by either the transmit or receive signal path may be performed solely in the RF circuitry 206, solely in the FEM circuitry 208, or in both the RF circuitry 206 and the FEM circuitry 208.

[0048] In some aspects, the FEM circuitry 208 may include a TX / RX switch to switch between transmit and receive modes of operation. The FEM circuitry may include a receive signal path and a transmit signal path. The receive signal path of the FEM circuitry may include an LNA to amplify a received RF signal and provide the amplified received RF signal as an output (e.g., to the RF circuitry 206). The transmit signal path of the FEM circuitry 208 may include a power amplifier (PA) to amplify an input RF signal (e.g., provided by the RF circuitry 206), and one or more filters to generate an RF signal for subsequent transmission (e.g., via one or more of the one or more antennas 210).

[0049] In some aspects, the PMC 212 can manage the power provided to the baseband circuitry 204. Specifically, the PMC 212 can control power source selection, voltage scaling, battery charging, or DC-DC conversion. When the device 200 is capable of being powered by a battery, such as when the device is included in a UE, the PMC 212 is typically included. The PMC 212 can improve power conversion efficiency while providing a desired implementation size and heat dissipation characteristics.

[0050] Although Figure 2 The PMC 212 is shown coupled only to the baseband circuitry 204. However, in other aspects, the PMC 212 may additionally or alternatively be coupled to other components (such as, but not limited to, the application circuitry 202, the RF circuitry 206, or the FEM circuitry 208) and perform similar power management operations.

[0051] In some aspects, the PMC 212 can control or otherwise participate in various power saving mechanisms of the device 200. For example, if the device 200 is in the RRC_Connected state, in which it is still connected to the RAN node as expected to receive traffic soon, then after a period of inactivity, it can enter a state known as discontinuous reception mode (DRX). During this state, the device 200 can be powered down for short intervals to save power.

[0052] If there is no data traffic activity for an extended period of time, the device 200 may transition to the RRC_Idle state, in which it is disconnected from the network and does not perform operations such as channel quality feedback, handover, etc. The device 200 enters a very low power state and performs paging, in which it periodically wakes up again to listen to the network and then powers down again. The device 200 may not receive data in this state; to receive data, the device may transition back to the RRC_Connected state.

[0053] An additional power saving mode can disable the device from using the network for periods exceeding the paging interval (ranging from a few seconds to several hours). During this period, the device is completely unable to connect to the network and can be completely powered down. Any data sent during this period will incur significant latency, assuming that latency is acceptable.

[0054] The processor of the application circuitry 202 and the processor of the baseband circuitry 204 can be used to execute elements of one or more instances of the protocol stack. For example, the processor of the baseband circuitry 204 can be used alone or in combination to perform Layer 3, Layer 2, or Layer 1 functions, while the processor of the application circuitry 202 can utilize data received from these layers (e.g., packet data) and further perform Layer 4 functions (e.g., Transport Communication Protocol (TCP) and User Datagram Protocol (UDP) layers). As mentioned herein, Layer 3 may include a Radio Resource Control (RRC) layer, which is described in further detail below. As mentioned herein, Layer 2 may include a Medium Access Control (MAC) layer, a Radio Link Control (RLC) layer, and a Packet Data Convergence Protocol (PDCP) layer, which are described in further detail below. As mentioned herein, Layer 1 may include a Physical (PHY) layer of the UE / RAN node, which is described in further detail below.

[0055] Figure 3 1 shows an exemplary interface of a baseband circuit according to some aspects. As discussed above, Figure 2 The baseband circuit 204 may include processors 204A-204E and a memory 204G utilized by the processors. Each of the processors 204A-204E may include a memory interface 304A-304E, respectively, to send / receive data to / from the memory 204G.

[0056] The baseband circuit 204 may also include one or more interfaces for communicatively coupling to other circuits / devices, such as a memory interface 312 (e.g., an interface for sending / receiving data to / from a memory external to the baseband circuit 204); an application circuit interface 314 (e.g., an interface for sending / receiving data to / from a memory external to the baseband circuit 204); Figure 2 RF circuit interface 316 (for example, for sending / receiving data to / from the application circuit 202); Figure 2 an interface for sending / receiving data to / from the RF circuit 206); a wireless hardware connection interface 318 (e.g., for sending / receiving data to / from a near field communication (NFC) component, Components (e.g. Low Energy), components and other communication components to send / receive data); and a power management interface 320 (eg, an interface for sending / receiving power or control signals to / from PMC212).

[0057] In the Third Generation Partnership Project (3GPP) and herein, a network slice (also referred to herein as a slice) may be referred to as a single network slice selection assistance information (S-NSSAI) value, which may be uniquely associated with that network slice. A set of S-NSSAIs may be collectively referred to as NSSAI. The configured NSSAI (also referred to herein as a configured network slice or configured slice, etc.) includes the NSSAI configured for the UE, which may be based on factors such as the UE's subscription, current serving network, etc. The requested NSSAI (also referred to herein as a requested network slice or requested slice, etc.) includes the NSSAI provided by the UE to the serving public land mobile network (PLMN) during registration (the requested NSSAI is a subset of the UE's configured NSSAI). The allowed NSSAI (also referred to herein as an allowed network slice, allowed slice, registered NSSAI, registered network slice, or registered slice, etc.) includes the NSSAI provided by the serving PLMN, for example, during the registration process, indicating the S-NSSAI values ​​that the UE can use in the serving PLMN of the current registration area (the allowed NSSAI is a subset of the UE's requested NSSAI). Rejected NSSAI (also referred to herein as rejected network slice or rejected slice, etc.) includes NSSAI that is permanently or temporarily rejected for the current registration area or for the entire PLMN.

[0058] Embodiments relate to network slice configuration for UEs subject to constraints on simultaneous use of network slices. Various aspects related to registration of network slices, establishment and release of PDU sessions on network slices, and / or activation and release of user plane resources for PDU sessions on network slices are discussed herein, each of which may potentially be subject to constraints on simultaneous use of these network slices. The constraints on use of network slices discussed herein may vary and may include one or more of the following: (a) incompatibility of network slices for simultaneous registration for UEs; (b) incompatibility of network slices for having simultaneously established PDU sessions for UEs; (c) incompatibility of network slices for having simultaneously active user plane resources for established PDU sessions for UEs, etc. If one or more of constraints (a), (b), or (c) apply to a pair of network slices, the pair of network slices may be incompatible (at least to some extent) for simultaneous operation (e.g., if they are incompatible for simultaneous registration, incompatible for having simultaneously established PDU sessions, and / or incompatible for having simultaneously active user plane resources for established PDU sessions, etc.).

[0059] refer to Figure 4, a block diagram of a system 400 according to various aspects discussed herein is shown, which can be employed at a UE (user equipment), a base station (BS, such as a next-generation Node B (gNodeB or gNB), an evolved Node B (eNB), or other BS (base station) / TRP (transmit / receive point)), an access and mobility management function (AMF), or another component of a 3GPP (3rd Generation Partnership Project) network (e.g., a 5GC (fifth generation core network) component or function, such as a UPF (user plane management function)), to facilitate network slicing-related configuration of a UE subject to simultaneous use constraints of a network slice. The system 400 may include a processor 410, a communication circuit 420, and a memory 430. The processor 410 (e.g., which may include one or more of 202 and / or 204A-204F, etc.) may include processing circuitry and associated interfaces (e.g., a communication interface (e.g., RF circuit interface 316) for communicating with the communication circuit 420, a memory interface (e.g., memory interface 312) for communicating with the memory 430, etc.). The communication circuit 420 may include, for example, circuits for wired and / or wireless connections (e.g., 206 and / or 208), which may include transmitter circuits (e.g., associated with one or more transmission chains) and / or receiver circuits (e.g., associated with one or more reception chains), wherein the transmitter circuits and the receiver circuits may employ common and / or different circuit elements, or a combination thereof. The memory 430 may include one or more memory devices (e.g., memory 204G, local memory (e.g., including CPU registers of the processor discussed herein), etc.), which may have any of various storage media (e.g., volatile and / or non-volatile according to any of various technologies / constructions, etc.), and may store instructions and / or data associated with one or more of the processor 410 or the communication circuit 420.

[0060] Specific types of aspects of the system 400 (eg, UE aspects, etc.) may be indicated via subscripts (eg, system 400 UE Including processor 410 UE , communication circuit 420 UE and memory 430 UE In some aspects, such as BS aspects (eg, system 400 BS ) and network components (eg, AMF, etc.) (eg, system 400 AMF ), a processor (eg, 410 BS etc.), communication circuits (eg, 420 BS etc.) and memory (eg, 430 BS, etc.) can be included in a single device or can be included in different devices, such as part of a distributed architecture. In various aspects, signaling or messaging between different aspects of system 400 (e.g., 4001 and 4002) can be generated by processor 4101, transmitted by communication circuitry 4201 over an appropriate interface or reference point (e.g., 3GPP air interface N1, N8, N11, N22, etc.), received by communication circuitry 4202, and processed by processor 4102. Depending on the type of interface, additional components (e.g., antennas, network ports, etc. associated with systems 4001 and 4002) can participate in the communication.

[0061] In various aspects, one or more of information (e.g., system information, resources associated with signaling, etc.), features, parameters, etc., may be provided via signaling (e.g., access stratum (AS) signaling, non-access stratum (NAS) signaling) originating from or directed through a base station (e.g., gNB, etc.) or other access point (e.g., via a processor 410). BS Generate, by the communication circuit 420 BS Transmission, by the communication circuit 420 UE Received and processed by processor 410 UE The UE is configured with information / features / parameters / etc., generated or processed by the UE. The type of signaling employed and / or the exact details of the operations performed at the UE and / or BS during the processing (e.g., signaling structure, processing of PDUs / SDUs, etc.) may vary depending on the type, features, parameters, etc. of the information. However, for convenience, such operations may be referred to herein as configuring information / features / parameters / etc. for the UE, generating or processing configuration signaling, or by similar terminology.

[0062] refer to Figure 5 , this figure shows an example of a network slice 500 in conjunction with various aspects discussed herein. Each network slice (e.g., slice 500) is an independent end-to-end 5G network (which can be logical or physical). Each network slice spans all network functions and is isolated from other slices. Figure 5 Several components and functions shown in have specific behaviors related to network slice configuration. UDM 127 may store the subscriptions of a user (e.g., of UE 101), for example, whether the user has purchased a subscription to the HD streaming slice. NSSF 129 may provide logical functionality to evaluate whether a user is allowed to use a given slice in the current PLMN. PCF 126 may provide rules to the UE to identify which traffic is sent via which slice. AMF 121 may act as a single point of contact with the UE for all slice-related configurations. UE 101 may establish a slice-specific session and route packets on the appropriate slice.

[0063] The independence of network slices provides the potential to customize the RAN (Radio Access Network) and / or CN (Core Network) configuration according to the network slice. From the perspective of the AS (Access Stratum), the slice traffic is part of a separate DRB (Data Radio Bearer). From the perspective of the NAS (Non-Access Stratum), the slice traffic is part of a separate PDU (Protocol Data Unit) session.

[0064] The types of entities that may be involved in the management, leasing, or development of a slice can vary. Slices are owned by the network operator but can be subleased to enterprises (e.g., Apple), which can develop use cases to exploit the benefits of a slice. Each slice has its own service level agreement (SLA), which may specify its characteristics, such as the maximum number of concurrently active users, aggregate bandwidth, etc.

[0065] Network slicing has a variety of potential business use cases. For example, network slicing can provide: (1) QoS (Quality of Service) management for each service (e.g., uRLLC, eMBB, Vehicle-to-Everything (V2X)), (2) higher security implementation (e.g., secure applications, enterprise solutions such as corporate email), (3) differentiated billing (e.g., Apple has a slice for FaceTime and can provide FaceTime services with zero data charges and higher QoS), etc.

[0066] refer to Figure 6, which illustrates a call flow diagram of a method 600 for establishing a network slice for a UE in conjunction with various aspects discussed herein. UE 101 may be pre-configured with a list of network slice selection assistance information (NSSAI) via carrier feature-specific pre-configuration in the UE SW (referred to as carrier bundling (CB)) or via a previous registration attempt by UE 101, where the NSSAI may include a set of one or more single NSSAIs (S-NSSAIs), each of which may be associated with a distinct network slice. As used herein, a configured NSSAI may include an S-NSSAI provided by an operator and subscribed to by a UE (e.g., UE 101). At 602, UE 101 may transmit a registration request message to a BS (e.g., a gNB) of RAN 110, the registration request message including one or more requested NSSAIs (e.g., selected by UE 101 from the configured NSSAIs of UE 101). At 604, BS 110 may select AMF 121 based on the requested NSSAIs included in a radio resource control (RRC) message. At 606, BS 110 may send the Registration Request message to the selected AMF 121. At 608, AMF 121 may send a message to UDM 127 to obtain slice selection subscription data for UE 101. At 610, UDM 127 may check the subscription of UE 101. At 612, UDM 127 may send a subscribed NSSAI list and a default NSSAI for UE 101 to AMF 121. At 614, AMF 121 may send a GetNSSelection message to NSSF 129, which includes the requested NSSAI, subscribed NSSAI, and default NSSAI for UE 101, as well as the public land mobile network (PLMN) and tracking area identity (TAI). At 616, in response to the GetNSSelection message, NSSF 129 may send the AMF candidate (e.g., if different from AMF 127), the configured NSSAI, the allowed NSSAI (if any), the rejected NSSAI (e.g., those permanently or temporarily rejected for the current registration area or for the entire PLMN) and the rejection reason (if any), and the pending NSSAI (if any) to AMF 121 for UE 101. At 618, AMF 121 may optionally perform an AMF reallocation procedure (e.g., if the AMF candidate of 616 is different from the AMF 121 selected at 604). At 620, AMF 121 may send a Registration Accept message to UE 101, which includes any allowed NSSAI, any rejected NSSAI and the rejection reason, as well as the configured UE for UE 101.At 622, AMF 121 may initiate (e.g., in response to the updated NSSAI information of UE 101) a Network Slice Specific Authentication and Authorization (NSSAA) procedure for any eligible slices. At 624, in response to the NSSAA procedure, AMF 121 may send a Configuration Update Command to UE 101, indicating the allowed NSSAI (if any) and the rejected NSSAI (if any) and the rejection reason.

[0067] The Third Generation Partnership Project (3GPP) SA2 (Architecture Working Group 2 (WG2)) has identified the constraint on the simultaneous use of network slices as an issue. One of the attributes in the GST (Generic Slice Template) documented in GSMA 5GJA NG.116 is "Simultaneous Use of Network Slices," which describes whether a network slice can be used simultaneously with other network slices. This attribute has the following parameters defined: value (integer), unit of measurement (NA), examples (0: can be used with any network slice; 1: can be used with network slices with the same SST [Slice / Service Type] value; 2: can be used with any network slice with the same SD value; 3: cannot be used with another network slice; 4-15: operator-defined classes) and tag (character attribute / function).

[0068] 3GPP Release 15 (Rel-15) and Rel-16 specifications do not allow the implementation of constraints related to the simultaneous use of network slices, as defined in this attribute.

[0069] The SA2 problem is to investigate: (1) how to implement constraints related to the simultaneous use of network slices in the UE and in the network in roaming and non-roaming scenarios; (2) how to ensure that the identified implementation does not negatively impact network operation for Rel-15 and Rel-16 5GS deployments; (3) it can be understood from the GSMA 5GJANG.116 document (sections 3.4.25 and 3.4.9) that for some network slices, the serving network may need to separate slice operations due to security isolation and serving network configuration, resulting in mutually exclusive slice operations; (4) simultaneous slice operation restrictions may exist: in the serving network but not in the home network, or in the home network but not in the serving network, or in both the home network and the serving network; and (5) the network may deploy non-standardized network slice identifiers, and this problem includes how the mutual exclusivity of slices will be deployed in such cases.

[0070] Various embodiments may employ the techniques discussed herein to facilitate configuration of network slices subject to constraints on concurrent use of the slices. These techniques include three different sets of aspects for handling constraints on concurrent use of network slices, including various options within those techniques.

[0071] When a UE (eg, UE 101 and / or system 400 UE When a UE (e.g., a UE of a network, etc.) subscribes to multiple slices (e.g., these slices may be referred to herein as slices or S-NSSAI, e.g., S-NSSAI_1 (or SLICE_1), S-NSSAI_2, S-NSSAI_A, S-NSSAI_B, etc.), the various embodiments discussed herein may be employed. In various aspects of the embodiments discussed herein, the UE may initiate a registration request message (e.g., similar to 602). In various such aspects (e.g., the first set of aspects discussed herein, etc.), the registration request message may include a new capability indicating whether the UE supports simultaneous slice usage constraints. In response to the registration request message, the NW may send a registration accept message (e.g., similar to 620), which in various aspects may indicate one or more network slices selected based on the UE's support for simultaneous slice usage constraints.

[0072] refer to Figure 7 , which shows an illustration of a first exemplary call flow 700 for slice registration in conjunction with simultaneous slice usage constraints in accordance with various aspects discussed herein. At 702, the UE 101 may send a registration request message to the AMF 121, which includes a requested NSSAI (e.g., similar to 602) and may also include (in various aspects) an indication that the UE supports simultaneous slice usage constraints. At 704, the AMF may contact the UDM 127 to obtain UE subscription information and contact the NSSF 129 to obtain network capabilities for slice simultaneous operation in conjunction with the requested NSSAI. At 706, the AMF 121, NSSF 129, PCF 126, and UDM 127 may register the UE 101 with at least one of the requested NSSAIs (and possibly more than one, depending on slice compatibility, etc.) in accordance with the registration procedures discussed herein and section 4.2.2.2 of 3GPP Technical Specification (TS) 23.502. At 708, AMF 121 may send a registration accept message to the UE, the registration accept message indicating the allowed NSSAIs (e.g., similar to 620) and further indicating a compatibility parameter for each such S-NSSAI (e.g., indicating the slices with which the slice is compatible or incompatible for simultaneous operation in accordance with various aspects discussed herein). In some aspects, the registration accept message may also indicate a compatibility parameter for each configured S-NSSAI for the UE.

[0073] In various aspects, compatibility information (e.g., compatibility parameters, etc.) for a network slice or S-NSSAI as discussed herein may indicate, for the S-NSSAI, which other S-NSSAIs (e.g., configured NSSAI, requested NSSAI, or allowed NSSAI) are compatible or incompatible with the S-NSSAI with respect to one or more of the following: (a) compatibility or incompatibility of the network slice for simultaneous registration for a UE; (b) compatibility or incompatibility of the network slice for having a simultaneously established PDU session for the UE; (c) compatibility or incompatibility of the network slice for having concurrently active user plane resources for an established PDU session for the UE. In some cases, the indication may be explicit (e.g., S-NSSAI_1 is incompatible with simultaneous registration with S-NSSAI_2, or with having a concurrently active PDU session with S-NSSAI_2, etc.). In other cases, the indication may be implicit (e.g., S-NSSAI_1 is compatible with simultaneous registration with S-NSSAI_3 or S-NSSAI_4, but no explicit indication of compatibility / incompatibility is provided for the configured S-NSSAI_2, but instead an implicit indication that S-NSSAI_1 is incompatible with simultaneous registration with S-NSSAI_2, etc.).

[0074] refer to Figure 8 , which shows an illustration of a second exemplary call flow 800 for slice registration in conjunction with simultaneous slice usage constraints in accordance with various aspects discussed herein. At 802, UE 101 may send an initial registration request message to AMF 121, which includes an indication that the UE supports simultaneous slice usage constraints (and may also request registration for the NSSAI of the initial request). At 804, the AMF may contact UDM 127 to obtain UE subscription information and contact NSSF 129 to obtain network capabilities for slice simultaneous operation in conjunction with the UE's configured NSSAI, and the AMF may store compatibility information.

[0075] For example, as shown in Table 1 below, the configured NSSAI may include S-NSSAI_A (eMBB), S-NSSAI_B (eMBB), S-NSSAI_C (eMBB), and S-NSSAI_D (URLLC), with the following compatibility information: (a) S-NSSAI_A, S-NSSAI_B, and S-NSSAI_C may be registered simultaneously with each other, but none of them may be registered simultaneously with S-NSSAI_D; (b) S-NSSAI_A and S-NSSAI_B may have PDU sessions that are active simultaneously with each other, but neither may have a PDU session that is active simultaneously with S-NSSAI_C; and (c) S-NSSAI_A and S-NSSAI_B may have user plane resources established simultaneously with each other.

[0076] Table 1: Example slice compatibility information provided to UE

[0077]

[0078] In the example of Table 1, although S-NSSAI-A, S-NSSAI-B, and S-NSSAI-C are allowed to register simultaneously (i.e., all three S-NSSAIs may be part of the allowed NSSAI list received from the network at the same time), the UE is allowed to simultaneously establish a PDU Session and have active user plane resources for the PDU Session associated only with S-NSSAI-A and S-NSSAI-B. Therefore, if the UE wishes to establish a PDU Session for S-NSSAI-C and activate user plane resources, it will first ensure that the PDU Sessions associated with S-NSSAI-A and S-NSSAI-B are released or not yet established.

[0079] Likewise, as seen in this example, simultaneous registration of uRLLC slice S-NSSAI-D with another configured NSSAI is not allowed. Therefore, if the UE wishes to access S-NSSAI-D, the UE may first initiate a mobility or periodic registration procedure with the network using the NSSAI set to include the S-NSSAI-D request. The UE may also ensure that the PDU Session associated with the incompatible slice is implicitly released and indicated to the network via the PDU Session Status IE in the Registration Request, or explicitly released via a PDU Session Release Request.

[0080] At 806, AMF 121, SMF 124, NSSF 129, UPF 102, and UDM 127 may register UE 101 to one or more S-NSSAIs (and possibly more than one, depending on slice compatibility, etc.) in the initially requested NSSAI in accordance with the registration procedures discussed herein and section 4.2.2.2 of 3GPP Technical Specification (TS) 23.502. At 808, AMF 121 may send a Registration Accept message to the UE indicating slice compatibility information for each configured S-NSSAI of the UE (and may also indicate the one or more S-NSSAIs registered as allowed NSSAIs at 806).

[0081] At 810, the UE may send a periodic or mobility registration request including requested NSSAIs (e.g., S-NSSAI_A, S-NSSAI_B, and S-NSSAI_C) to the AMF. In various aspects, the requested NSSAI at 810 may be selected by the UE as compatible for simultaneous registration. At 812, the AMF (e.g., and other entities) may register the UE to each S-NSSAI of the requested NSSAI (however, in other aspects, one or more S-NSSAIs may be rejected for reasons other than slice incompatibility, for example). At 814, the AMF may send a registration accept message to the UE indicating that the allowed NSSAIs include S-NSSAI_A, S-NSSAI_B, and S-NSSAI_C. At 816, a PDU session may be established and user plane resources may be activated for one or more compatible S-NSSAIs of the allowed NSSAIs (e.g., S-NSSAI_A and S-NSSAI_B, as Figure 8 shown).

[0082] In conjunction with aspects of exemplary call flow 800, 802 through 808 may occur once upon initial registration with the PLMN, while 810 through 816 (or similar actions) may potentially occur multiple times as the UE sends periodic and / or mobility registration requests (e.g., with potentially varying requested and allowed NSSAIs).

[0083] In the first set of aspects, the NW can create a list of allowed NSSAIs based on the requested NSSAI, similar to Figure 6 However, in addition, each S-NSSAI in the allowed NSSAIs may include a list of compatible S-NSSAIs, which defines the slices with which the S-NSSAI can operate simultaneously. Figure 9 , which shows an exemplary table showing three examples of allowed slices, indicating the SST value, the optional SD value, and the compatibility between the slices, according to various aspects discussed herein. In the first set of aspects, when the UE indicates support for simultaneous slice usage constraints, the NW will not reject the S-NSSAI due to slice incompatibility issues (however, the NW may still reject the S-NSSAI for other reasons (e.g., quota unavailable, NSAAA failure, etc.)). In addition, if the UE does not support support for simultaneous slice usage constraints, the network is free to reject the slice due to slice incompatibility issues (e.g., for 3GPP Rel-16 UEs, etc.).

[0084] In a second set of aspects, each S-NSSAI in the list of configured NSSAIs for a UE may indicate a list of compatible S-NSSAIs with which it may operate concurrently (e.g., Figure 9). The AMF may ensure that all S-NSSAIs listed in the compatible NSSAI list are part of the configured NSSAI list. Based on the UE priority policy (e.g. which set of slices the user / UE is interested in), the UE may initiate a new registration procedure, indicating the requested NSSAI (e.g. Figure 7-8 Based on the compatible NSSAI list, the UE can ensure that incompatible slices are not included in the requested NSSAI list at the same time. If incompatible slices are included, the AMF can reject the incompatible slices and only allow the compatible set of slices that are allowed to be registered at the same time.

[0085] Additionally, in conjunction with the second set of aspects, the UE and / or AMF may be configured to select a slice based on one or more criteria, such as: (1) ensuring that a maximum number of slices from the requested NSSAI list is "allowed" (e.g., a maximum group of compatible slices is preferred) and / or (2) considering the first slice listed in the requested NSSAI list as the highest priority, or the registration request message explicitly indicates priority information for the first network slice and ensuring that the maximum group of compatible slices including the first slice is "allowed".

[0086] In a third set of aspects, a UE may include a new information element (IE) indicating support for simultaneous slice usage constraints in its IEs (e.g., Figure 7-8 etc.) registration request to indicate awareness of the slice constraints.

[0087] Additionally, AMF can be used in (e.g. Figure 7-8 A new IE indicating slice compatibility is included in the Registration Accept (e.g., a UE's home network). The Slice Compatibility IE may indicate slice compatibility or incompatibility between all slices subscribed by the UE. To provide this information, the serving AMF may: (a) obtain the subscribed NSSAI from the UDM (of the UE's home network) and, based on the subscribed NSSAI; (b) obtain the received slice constraints from the serving NSSF; and (c) based on the constraints, based on the GST attributes provided by the network slice provider, may send a Slice Compatibility IE to the UE.

[0088] In various embodiments, the slice compatibility IE may also include information about AMF reallocation (e.g., by indicating, for each pair of incompatible slices, whether they are served by the same AMF or by different AMFs, etc.). The AMF reallocation information may be based on the serving network configuration regarding how the serving network selects to serve independent slices.

[0089] In a third set of aspects, the UE may send a registration request with the requested S-NSSAI (e.g., Figure 7-8In response, the AMF may send a Registration Accept with an allowed S-NSSAI (e.g., as shown in FIG. 5 ). Figure 7-8 as shown), which may include slices that are incompatible for simultaneous use, and may also include a slice compatibility IE that specifies which slices are allowed to be used simultaneously.

[0090] WO 2022 / 036081A1

[0091] In the third set of aspects, when any PDU session is initiated and slices are activated, the UE follows the slice compatibility rules set in the Slice Compatibility IE. The rules in the Slice Compatibility IE are specific only to the serving network, and the registration process on the new network may result in new slice constraint rules for the UE.

[0092] In the third set of aspects, there are multiple options for resolving potential registration issues of UEs on incompatible slices.

[0093] In the first option, the UE is allowed to register for constrained slices, but the decision to activate the PDU session is based on the slice compatibility IE.

[0094] An example of the first option is a scenario where the UE already has an active PDU session (e.g., created on SLICE_A), SLICE_A and SLICE_B are provided in the allowed NSSAI, but (according to the slice compatibility IE) the UE can only activate the PDU session on one of these slices at a time. If SLICE_B needs to establish and activate a new PDU session, the UE can (a) use the "PDU Session Status IE" in the service request or registration request to initiate the release of the current PDU session active on SLICE_A, or (b) wait for the user plane resources to be released (i.e., enter the idle state at the UE) before triggering the PDU session on SLICE_B.

[0095] The first option addresses slices entering NSSAA. After successful NSSAA, the UE may move these slices to the "allowed list", but still use the information provided in the "Slice Compatibility IE" to activate PDU sessions on compatible slices.

[0096] In the second option, UEs are allowed to simultaneously register for constrained slices and establish simultaneous PDU sessions on the constrained slices, but there are no user plane resources active simultaneously on the constrained slices.

[0097] An example of the second option is a scenario where the UE already has an active PDU session (e.g., created on SLICE_A), SLICE_A and SLICE_B are provided in the allowed NSSAI, but (according to the Slice Compatibility IE) the UE may establish simultaneous PDU sessions on both slices, but only one slice may have active user plane resources. If the new PDU session for SLICE_B requires user plane resources to be active, the UE may (a) use the "PDU Session Status IE" in the Service Request or Registration Request to initiate the release of the current user plane resources active on SLICE_A, or (b) wait for the user plane resources to be released on SLICE_A before establishing user plane resources on SLICE_B. To activate the user plane resources on SLICE_B, the UE may include the "Uplink Data Status" IE in the Registration Request or Service Request. In various aspects, the UE may check slice compatibility before triggering a Service Request or Registration Request to request user plane resources on other slices.

[0098] In the third option, the UE is not allowed to register for constrained slices. An example of the third option is a scenario where the UE sends a Registration Request with the requested S-NSSAI (e.g., SLICE_A, SLICE_B) and an indication that constraint-based slice activation is supported, and the AMF sends a Registration Accept with the allowed S-NSSAI including only SLICE_A, where the Registration Accept also includes a Slice Compatibility IE that specifies which slices are allowed to be used simultaneously. After the PDU Session on SLICE_A is activated, if the UE intends to activate a PDU Session on SLICE_B, the UE first triggers a Registration Request with SLICE_B as the requested slice and locally deactivates / releases all PDU Sessions that are using SLICE_A and indicates this to the network by including a PDU Session Status IE and indicating that the PDU Session ID corresponding to SLICE_A is inactive.

[0099] In conjunction with the third option, when activating SLICE_B, the UE may omit the 5G S-Temporary Mobile Subscriber Identity (5G S-TMSI) associated with the AMF for SLICE_A from the messaging to the BS (e.g., gNB) during the RRC connection establishment procedure so that the BS does not select the same AMF again. For example, if the UE has requested SLICE_A and SLICE_B, and the slice compatibility IE received from the network indicates that SLICE_A and SLICE_B cannot be activated at the same time because they are served by different AMFs, then if the network originally activated SLICE_A and the UE now wants to activate SLICE_B, the UE omits the 5G S-TMSI from the messaging to the BS (e.g., gNB). By omitting the 5G S-TMSI, the UE can prevent the BS from selecting the same AMF again to activate SLICE_B. These aspects may provide a solution for the scenario where the UE triggers a PDU session after a registration accept with an allowed S_NSSAI consisting of SLICE_B. For slices with NSSAA already present in the allowed list, omitting the 5G S-TMSI may trigger registration via the appropriate AMF.

[0100] Additionally, techniques associated with the third option may involve AMF selection by a BS (e.g., gNB). Upon receiving the requested slice information in NSSAI inclusion mode in an RRC CONNECTION ESTABLISHMENT, the BS may select the corresponding AMF based on the first slice indicated by the UE in the RRC CONNECTION ESTABLISHMENT when switching between independent slices involving registrations with different AMFs.

[0101] In various aspects of the third option, a backoff timer may be used in conjunction with slice selection. In some scenarios, depending on the applications running in the UE that need to activate incompatible slices (e.g., SLICE_A or SLICE_B), these applications may potentially cause the network to continuously switch between different constrained slices through a re-registration process or deactivation and reactivation of a PDU session. To limit rapid switching between slices, in various aspects, the network may provide a backoff timer (e.g., in a registration accept or a PDU session establishment accept) so that the UE can activate mutually constrained slices only after the backoff timer expires.

[0102] As an example scenario involving the backoff timer, the UE has requested SLICE_A and SLICE_B, and the slice compatibility IE received from the network indicates that SLICE_A and SLICE_B cannot be activated at the same time because they are served by different AMFs, and the AMF provides a backoff timer in the Registration Accept, which indicates to the UE that it cannot activate SLICE_B until the backoff timer expires. Similarly, this can be applied to a scenario where both SLICE_A and SLICE_B are sent in the allowed NSSAI, but there is a slice compatibility IE indicating that SLICE_A and SLICE_B cannot have simultaneously active PDU sessions. In this scenario, the AMF can indicate to the UE that it cannot activate a PDU session on SLICE_B until the constraint backoff timer expires.

[0103] In other aspects of the third option, various techniques may provide UE slicing support based on non-3GPP and 3GPP access technologies. If a UE is registered with different AMFs based on 3GPP and non-3GPP access technologies, it may choose to independently activate mutually exclusive slices simultaneously. As an example scenario, if the UE wishes to activate SLICE_A and SLICE_B simultaneously, and the AMF on one of the accesses (e.g., 3GPP access) sends a slice compatibility IE to the UE indicating that the AMF does not allow SLICE_A and SLICE_B to be activated simultaneously, then if the UE is able to find a separate non-3GPP access served by a different PLMN, the UE may attempt to activate SLICE_B on that non-3GPP access. If the UE non-3GPP access later switches to the same PLMN AMF as SLICE_A on the 3GPP access, the SLICE_B context and PDU session may be discarded (as derived from the slice compatibility IE) and the SLICE_APDU session will continue. This technique may enable simultaneous activation of mutually independent slices via multiple access technologies.

[0104] In addition, in conjunction with the third set of aspects, such a technique may be employed where the network may dynamically change the slice constraint information when the UDM detects a change in the subscribed NSSAI or the network slice provider changes the slice configuration. As an exemplary scenario, when the UE has requested SLICE_A and SLICE_B, and the slice compatibility IE received from the network indicates that SLICE_A and SLICE_B cannot be activated at the same time because they are served by different AMFs, then if the network has initially activated SLICE_A and the UDM detects a change in the subscribed NSSAI indicating that the UE is no longer subscribed to SLICE_B, the AMF may instruct the UE to remove SLICE_B from the slice constraint IE. These techniques may be implemented via an AMF triggering a configuration update command that instructs the removal of SLICE_B from the slice constraint IE (or other corresponding changes to the slice constraint IE based on a detected change in the subscribed NSSAI or slice configuration, etc.).

[0105] refer to Figure 10 , which shows an exemplary table showing compatibility between slices based on explicit indication of slice incompatibility according to the third set of aspects discussed herein. Figure 10 The lower right table shows examples of slices configured for a UE serving the network, and the lower left table shows the SST values ​​associated with those slice types. Figure 10 The upper table shows exemplary incompatibility information that can be provided in conjunction with those slices, and whether the incompatible slices are served by the same AMF. Because the upper table only lists slice incompatibilities, the omission of slice 6, for example, indicates that slice 6 can be activated at the same time as all other registered slices.

[0106] refer to Figure 11 , which shows an exemplary table according to the third set of aspects discussed herein, in which compatibility between slices is shown via an indication of slice incompatibility based on SST. Figure 11 The lower right table shows examples of slices configured for a UE serving the network, and the lower left table shows the SST values ​​associated with those slice types. Figure 11 The upper table shows exemplary incompatibility information that may be provided in conjunction with those slices, and whether or not the incompatible SST slices are served by the same AMF. Figure 11 An SST-based example is provided, but similar techniques can be employed in conjunction with indicating incompatibility based on SD.

[0107] refer to Figure 12 , which shows an exemplary table showing compatibility between slices via slice incompatibility indication based on GSMA identified constraints according to the third set of aspects discussed herein. The slices configured by the UE for the serving network may be Figure 10 and Figure 11 The same as in . Figure 12 The lower table shows the types of exclusions indicated in connection with the GST examples discussed above and provided by the GSMA. Figure 12 The upper table shows exemplary incompatibility information that can be provided in conjunction with configured slices, along with incompatible slice constraints and exclusion types. Figure 10 and 11 Likewise, the lack of indicated constraints between slices implicitly indicates that the UE may operate on those slices simultaneously.

[0108] Figure 13-19 In various embodiments, in (e.g., according to Figure 7 or Figure 8 ) After registration, such as combining Figure 13-19 Techniques such as those discussed may be used for one or more of: (a) changing the allowed network slices for a UE (e.g., adding and / or removing registered network slices based on the application or service to be employed, etc.); (b) establishing and / or releasing one or more PDU sessions for a registered network slice; and / or (c) activating and / or releasing user plane resources for a PDU session on a registered network slice (e.g., a network slice with an active PDU session, etc.).

[0109] refer to Figure 13, which illustrates an example call flow 1300 involving a UE selectively establishing a PDU session in conjunction with various aspects discussed herein. In one example scenario, flow 1300 may be employed when the network has allowed the UE to register incompatible slices and the UE decides to selectively establish a PDU session on a slice that is incompatible with the slice with the active PDU session. In flow 1300, an active PDU session exists for S-NSSAI_1 for UE 101. At 1302, a user of UE 101 may initiate a new application or service served by S-NSSAI_2. At 1304, the UE wishes to initiate a PDU session for S-NSSAI_2 and checks and determines that S-NSSAI_1 and S-NSSAI_2 cannot operate simultaneously (e.g., as indicated by the AMF via a Registration Accept, in the list of configured NSSAIs, in a Slice Compatibility IE, etc.). At 1306, the UE may send a PDU Session Release Request for S-NSSAI_1 to the AMF. At 1308, a PDU Session Release procedure may be performed for S-NSSAI_1. The procedure may include: at 1310, the AMF sends and the UE receives a PDU Session Release Command, indicating that the PDU session was successfully released by the network. At 1312, the UE may send a PDU Session Establishment Request for S-NSSAI_2. At 1314, the AMF may check and determine whether S-NSSAI_2 is operable for the UE. If so, at 1316, a PDU Establishment procedure may be performed for S-NSSAI_2, and at 1318, the AMF may send a PDU Session Establishment Accept message to the UE, indicating S-NSSAI_2 and the PDU Session ID. At 1320, the PDU Session is active for S-NSSAI_2.

[0110] In various embodiments, a technique may be employed in which the UE may indicate that the requested PDU session is the priority PDU session for the UE relative to other PDU sessions. In an embodiment employing such a technique, the UE may send a PDU session establishment request with an allowed NSSAI, and the request may include a priority release slice IE that notifies the network that this is the priority PDU session for the UE. According to this embodiment, if the IE is present or set to 1, the NW may release active PDU sessions with S-NSSAIs that are incompatible with the S-NSSAI for which the PDU session is requested, and if the IE is not present or set to 0, if any PDU session with an S-NSSAI that is incompatible with the S-NSSAI for which the PDU session is requested is active, the NW may reject the PDU session.

[0111] In an implementation scheme employing these techniques, when the UE wants to establish a PDU session for an S-NSSAI, the UE may check whether there is any active PDU session for an incompatible slice. If so, if the application / service belonging to the S-NSSAI is in the foreground, the UE may set "Priority Release Slice" to 1 (or include this IE, depending on the implementation scheme), and if the request is for a background application / service, no PDU session establishment request is initiated. If not, the UE may set "Priority Release Slice" to 0 (or omit this IE, depending on the implementation scheme). Figure 14-16 An exemplary call flow for techniques associated with prioritizing the release of slices is shown.

[0112] refer to Figure 14 , which shows an illustration of a first exemplary call flow 1400 employing a priority release slice IE or value in conjunction with various aspects discussed herein. In call flow 1400, an active PDU session exists for S-NSSAI_1. At 1402, the UE may send a PDU session establishment request to the AMF, indicating that S-NSSAI_2 has a priority release slice set to 1. At 1404, the AMF may check whether S-NSSAI_1 and S-NSSAI_2 can operate simultaneously. In this example, they cannot operate simultaneously, and because the priority release slice is set to 1 for S-NSSAI_2, at 1406, a PDU session release procedure may be performed for S-NSSAI_1 (e.g., in accordance with 3GPP TS 23.502, 4.3.4.2). At 1408, the AMF may send a PDU session release command for S-NSSAI_1 to the UE. At 1410, a PDU establishment procedure may be performed for S-NSSAI_2 (e.g., according to 3GPP TS 23.502, 4.3.2.2.1-1, step 2-11). At 1412, the AMF may send a PDU session establishment accept message for S-NSSAI_2 to the UE, indicating the PDU session ID of the established PDU session. At 1414, the PDU session is active for S-NSSAI_2.

[0113] refer to Figure 15, which shows an illustration of a second exemplary call flow 1500 employing a priority release slice IE or value in conjunction with various aspects discussed herein. In call flow 1500, an active PDU session exists for S-NSSAI_1. At 1502, the UE may send a PDU session establishment request to the AMF, indicating that S-NSSAI_2 has a priority release slice set to 1. At 1504, the AMF may check whether S-NSSAI_1 and S-NSSAI_2 can operate simultaneously. In this example, they can, and at 1506, a PDU session establishment procedure may be performed for S-NSSAI_2 (e.g., in accordance with 3GPP TS 23.502, 4.3.2.2.1-1, step 2-11). At 1508, the AMF may send a PDU session establishment accept message for S-NSSAI_2 to the UE, indicating the PDU session ID of the established PDU session. At 1510, there are concurrently active PDU sessions for both S-NSSAI_1 and S-NSSAI_2.

[0114] refer to Figure 16 , which illustrates a diagram of a third exemplary call flow 1600 employing a priority release slice IE or value in conjunction with various aspects discussed herein. In call flow 1600, an active PDU session exists for S-NSSAI_1. At 1602, the UE may send a PDU session establishment request to the AMF, indicating that S-NSSAI_2 has a priority release slice set to 0. At 1604, the AMF may check whether S-NSSAI_1 and S-NSSAI_2 can operate simultaneously. If they cannot operate simultaneously, then at 1606, the AMF sends a PDU session establishment reject message indicating S-NSSAI_2 to the UE, and call flow 1600 ends. However, if they can operate simultaneously, then at 1608, a PDU session establishment procedure may be performed for S-NSSAI_2 (e.g., in accordance with 3GPP TS 23.502, 4.3.2.2.1-1, step 2-11). At 1610, the AMF may send a PDU session establishment accept message for S-NSSAI_2 to the UE, indicating the PDU session ID of the established PDU session. At 1612, there are concurrently active PDU sessions for both S-NSSAI_1 and S-NSSAI_2.

[0115] refer to Figure 17, which shows an illustration of an exemplary call flow 1700 for implicitly releasing a PDU session using the PDU Session Status IE in conjunction with various aspects discussed herein. In the call flow 1700, an active PDU session exists for S-NSSAI_A. At 1702, based on user activity or UE policy, the UE decides to initiate a PDU session for S-NSSAI-B, checks and determines that S-NSSAI_A and S-NSSAI_B cannot operate simultaneously. At 1704, the UE sends one of a service request or a registration request including the PDU Session Status IE to the AMF. At 1706, in response to the PDU Session Status IE, the network may perform a PDU session release procedure for all PDU Session IDs not included in the PDU Session Status IE in the service request or registration request. At 1708, the AMF may send one of a service accept or registration accept message (depending on the message of 1704) including the "PDU Session Status" IE to the UE. At 1710, after locally releasing the PDU session for which an implicit release (e.g., S-NSSAI_A) was triggered and receiving confirmation from the network that the incompatible PDU session has been released, the UE may send a PDU session establishment request indicating S-NSSAI_B to the AMF. At 1712, the AMF may check and determine that the UE is capable of operating on S-NSSAI_B. At 1714, a PDU establishment procedure may be performed for S-NSSAI_B. At 1716, the AMF may send a PDU session establishment accept message to the UE, indicating S-NSSAI_B and the PDU session ID of the PDU session to be established. At 1718, the PDU session is active for S-NSSAI_B.

[0116] refer to Figure 18 , which shows an illustration of an exemplary call flow 1800 for establishing user plane resources using uplink data state in conjunction with various aspects discussed herein. In the call flow 1800, the PDU session is active for both S-NSSAI_A and S-NSSAI_B, but only S-NSSAI_A has active user plane resources allocated (i.e., has active data radio bearers (DRBs)). At 1802, the UE may determine to initiate user plane resources for the PDU session that is active on S-NSSAI_B. The UE checks and determines that S-NSSAI_A and S-NSSAI_B cannot have user plane resources activated at the same time. The UE may wait until the user plane resources for S-NSSAI_A are released, or may initiate a service request including the PDU session state to implicitly release the SLICE_APDU session (e.g., as in Figure 17or 19, etc.). Once the user plane resources for S-NSSAI_A are released, at 1804, the UE may send a service request or registration request including the uplink status for S-NSSAI_B to the AMF. At 1806, in response to the uplink status, user plane resources may be established for the PDU session active on S-NSSAI_B.

[0117] refer to Figure 19 , which shows an illustration of an example call flow 1900 for locally releasing a PDU session using a PDU session status IE when the UE is not allowed to register for constrained slices, in conjunction with various aspects discussed herein. At 1902, the UE may transmit a registration request message to a next generation (NG) radio access network (RAN) (e.g., via a BS such as a gNB), the message including the requested NSSAI (e.g., in Figure 19In the example of S-NSSAI_A and S-NSSAI_B) and indicates support for simultaneous slice usage restrictions. At 1904, the NG RAN may select an AMF based on the requested NSSAI in the RRC message, and at 1906, the registration request message may be sent to the selected AMF. At 1908, the AMF may contact the NSSF, UDM, and network service provider (NSP) to obtain subscription and network capability information related to the simultaneous operation of the requested NSSAI. At 1910, in a scenario where S-NSSAI_A and S-NSSAI_B are incompatible, a registration procedure may be performed for S-NSSAI_A but not for S-NSSAI_B. At 1912, the AMF may send a registration accept message to the UE indicating that the allowed NSSAI only includes compatible slices, and a slice restriction IE indicating slice incompatibility (and whether the incompatible slices are served by the same AMF or different AMFs). At 1914, there is an active PDU session for S-NSSAI_A (but not for the incompatible S-NSSAI_B). At 1916, the UE may decide to initiate a PDU session on SLICE_B, which requires a new registration due to incompatibility (e.g., for a scenario where the third option of the third set of aspects is adopted, etc.). At 1918, the UE may send a second Registration Request message to the NG RAN indicating that the requested NSSAI includes S-NSSAI_B, along with the PDU Session Status IE, thereby triggering a local release of the incompatible PDU session. At 1920, the NG RAN may perform AMF selection based on the requested S-NSSAI_B, and at 1922, may forward the second Registration Request message to the appropriate AMF. At 1924, the AMF may contact the NSSF, UDM, and NSP based on the newly requested NSSAI (e.g., S-NSSAI_B) to obtain subscription and network capabilities for simultaneous operation of the slices. At 1926, a registration procedure may be performed for S-NSSAI_B, and at 1928, the AMF selected at 1920 may send a second registration accept message to the UE indicating that the new allowed NSSAI includes only compatible slices, and a new slice restriction IE associated with the allowed NSSAI.

[0118] Additional Examples

[0119] Embodiments herein may include subject matter such as a method, components for performing the actions or blocks of the method, and at least one machine-readable medium comprising executable instructions that, when executed by a machine (e.g., a processor with memory, an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), etc.), cause the machine to perform the actions of the method or apparatus or system for concurrent communication using multiple communication technologies according to the described aspects and examples.

[0120] Embodiment 1 is a user equipment (UE) device, which includes a processor configured to perform operations, the operations including: transmitting an initial registration request message, the initial registration request message including an indication that the UE has the ability to support simultaneous slice usage constraints; receiving a first registration accept message, the first registration accept message indicating slice compatibility information of each configured network slice in a set of configured network slices for the UE, wherein the slice compatibility information of each configured network slice indicates whether other configured network slices in the set of configured network slices are compatible with the configured network slice for simultaneous operation of the UE; transmitting an additional registration request message, the additional registration request message being used to request registration on a set of requested network slices, wherein the set of requested network slices is a subset of the set of configured network slices; and receiving an additional registration accept message, the additional registration accept message indicating that the UE is registered to a set of allowed network slices, wherein the set of allowed network slices is a subset of the set of requested network slices.

[0121] Embodiment 2 includes the subject matter of any variation of any one of Embodiment 1, wherein the operation further comprises: selecting the group of requested network slices based on slice compatibility information for each configured network slice in the group of configured network slices, so that each requested network slice in the group of requested network slices is compatible with other requested network slices in the group of requested network slices for simultaneous operation by the UE.

[0122] Embodiment 3 includes the subject matter of any variation of any of Embodiments 1-2, wherein the set of allowed network slices includes one or more of: a largest subset of the set of requested network slices, wherein the network slices are each compatible with each other for simultaneous operation by the UE, or a first network slice in the set of requested network slices and any other requested network slices in the set of requested network slices that are compatible with the first network slice for simultaneous operation by the UE, wherein the first network slice is listed first in the set of requested network slices in the registration request message, or the registration request message explicitly indicates priority information of the first network slice.

[0123] Embodiment 4 includes the subject matter of any variation of any of embodiments 1-3, wherein the set of allowed network slices includes a first network slice and a second network slice, and wherein the slice compatibility information indicates that the first network slice and the second network slice are incompatible for simultaneously active PDU (protocol data unit) sessions.

[0124] Embodiment 5 includes the subject matter of any variation of any one of Embodiment 4, wherein, when the UE has an active PDU session on a first network slice, the operation further comprises: transmitting a PDU session release request associated with the active PDU session on the first network slice; transmitting a PDU session establishment request associated with a second network slice; and receiving a PDU session establishment acceptance associated with the second network slice.

[0125] Example 6 includes the subject matter of any variation of any one of Examples 4-5, wherein, when the UE has an active PDU session on a first network slice, the operation further includes: transmitting a PDU session establishment request associated with a second network slice, wherein the PDU session establishment request includes a priority indication identifier; receiving a PDU session release command associated with the first network slice; and receiving a PDU session establishment acceptance associated with the second network slice.

[0126] Embodiment 7 includes the subject matter of any variation of any of Embodiments 4-6, wherein, when the UE has an active PDU session on a first network slice, the operation further comprises: transmitting one of a service request or a registration request, the request including a PDU session state information element (IE) associated with the first network slice to trigger an implicit release of the active PDU session on the first network slice; transmitting a PDU session establishment request associated with a second network slice; and receiving a PDU session establishment acceptance associated with the second network slice.

[0127] Embodiment 8 includes the subject matter of any variation of any of Embodiments 4-7, wherein, when the UE has an active PDU session on the first network slice, the operation further includes activating the second network slice via a non-Third Generation Partnership Project (3GPP) access technology.

[0128] Embodiment 9 includes the subject matter of any variation of any of Embodiments 1-8, wherein the set of allowed network slices includes a first network slice and a second network slice, and wherein, when the UE has an active PDU (Protocol Data Unit) session on the first network slice, the operation further includes: transmitting a PDU session establishment request associated with the second network slice; receiving a PDU session establishment accept associated with the second network slice; and simultaneously maintaining the active PDU session on the first network slice and the active PDU session on the second network slice.

[0129] Embodiment 10 includes the subject matter of any variation of any of Embodiment 9, wherein the operation further comprises: when the UE does not have active user plane resources on the first network slice, transmitting one of a service request or a registration request, the request including an uplink data status information element (IE) to trigger establishment of user plane resources associated with an active PDU session on the second network slice.

[0130] Embodiment 11 is a user equipment (UE) device comprising a processor configured to perform operations comprising: transmitting a registration request message for requesting registration on a set of requested network slices, wherein the set of requested network slices is a subset of a set of configured network slices for the UE; and receiving a registration accept message indicating that the UE is registered to a set of allowed network slices, wherein the set of allowed network slices is a subset of the set of requested network slices, and wherein the registration accept message indicates slice compatibility information of each allowed network slice in the set of allowed network slices for the UE, wherein the slice compatibility information of each allowed network slice indicates whether other configured network slices in the set of configured network slices are compatible with the configured network slice for simultaneous operation by the UE.

[0131] Embodiment 12 includes the subject matter of any variation of any one of Embodiment 11, wherein the registration accept message indicates slice compatibility information for each configured network slice in the group of configured network slices for the UE, wherein the slice compatibility information for each configured network slice indicates whether other configured network slices in the group of configured network slices are compatible with the configured network slice for simultaneous operation by the UE.

[0132] Embodiment 13 includes the subject matter of any variation of any one of Embodiments 11-12, wherein, when the slice compatibility information of each allowed network slice in the set of allowed network slices indicates that another allowed network slice in the set of allowed network slices is incompatible with the allowed network slice for simultaneous operation by the UE, it further indicates whether the allowed network slice and the another allowed network slice are associated with the same Access and Mobility Management Function (AMF) or different AMFs.

[0133] Embodiment 14 includes the subject matter of any variation of any of embodiments 11-13, wherein the set of requested network slices includes a first network slice and a second network slice, wherein the first network slice and the second network slice are incompatible with each other for simultaneous operation by the UE, and wherein the set of allowed network slices includes the first network slice but does not include the second network slice.

[0134] Embodiment 15 includes the subject matter of any variation of any of Embodiment 14, wherein the registration accept message indicates a timer, wherein the UE may request registration to the second network slice after expiration of the timer.

[0135] Embodiment 16 includes the subject matter of any variation of any one of Embodiments 14-15, wherein, when the UE has an active PDU session on the first network slice, the operation further includes: transmitting a second registration request message, the second registration request message being used to request registration on the second network slice and implicitly releasing the active PDU session on the first network slice; and receiving a second registration accept message indicating that the UE is registered to the second network slice.

[0136] Embodiment 17 includes the subject matter of any variation of any of embodiments 11-16, wherein the set of allowed network slices includes a first network slice and a second network slice, and wherein the slice compatibility information indicates that the first network slice and the second network slice are incompatible for simultaneously active PDU (protocol data unit) sessions.

[0137] Embodiment 18 includes the subject matter of any variation of any of Embodiment 17, wherein, when the UE has an active PDU session on a first network slice, the operation further comprises: transmitting a PDU session release request associated with the active PDU session on the first network slice; transmitting a PDU session establishment request associated with a second network slice; and receiving a PDU session establishment acceptance associated with the second network slice.

[0138] Embodiment 19 includes the subject matter of any variation of any one of Embodiments 17-18, wherein, when the UE has an active PDU session on a first network slice, the operation further includes: transmitting a PDU session establishment request associated with a second network slice, wherein the PDU session establishment request includes a priority indication identifier; receiving a PDU session release command associated with the first network slice; and receiving a PDU session establishment acceptance associated with the second network slice.

[0139] Embodiment 20 includes the subject matter of any variation of any of embodiments 17-19, wherein, when the UE has an active PDU session on a first network slice, the operation further comprises: transmitting one of a service request or a registration request, the request including a PDU session state information element (IE) associated with the first network slice to trigger an implicit release of the active PDU session on the first network slice; transmitting a PDU session establishment request associated with a second network slice; and receiving a PDU session establishment acceptance associated with the second network slice.

[0140] Embodiment 21 includes the subject matter of any variation of any of Embodiments 17-20, wherein, when the UE has an active PDU session on the first network slice, the operation further includes activating the second network slice via a non-3rd Generation Partnership Project (3GPP) access technology.

[0141] Embodiment 22 includes the subject matter of any variation of any of Embodiments 11-20, wherein the set of allowed network slices includes a first network slice and a second network slice, and wherein, when the UE has an active PDU session on the first network slice, the operation further includes: transmitting a PDU session establishment request associated with the second network slice; receiving a PDU session establishment accept associated with the second network slice; and simultaneously maintaining the active PDU session on the first network slice and the active PDU session on the second network slice.

[0142] Embodiment 23 includes the subject matter of any variation of any of Embodiment 22, wherein the operation further comprises: when the UE does not have active user plane resources on the first network slice, transmitting one of a service request or a registration request, the request including an uplink data status information element (IE) to trigger establishment of user plane resources associated with an active PDU session on the second network slice.

[0143] Embodiment 24 is an access and mobility management function (AMF), which includes a processor configured to perform operations, the operations including: receiving an initial registration request message, the initial registration request message including an indication that a user equipment (UE) has the ability to support simultaneous slice usage constraints; generating a first registration accept message for transmission, the first registration accept message indicating slice compatibility information of each configured network slice in a set of configured network slices for the UE, wherein the slice compatibility information of each configured network slice indicates whether other configured network slices in the set of configured network slices are compatible with the configured network slice for simultaneous operation of the UE; receiving an additional registration request message, the additional registration request message being used to request registration on a set of requested network slices, wherein the set of requested network slices is a subset of the set of configured network slices; registering the UE to the set of allowed network slices, wherein the set of allowed network slices is a subset of the set of requested network slices; and generating an additional registration accept message for transmission, the additional registration accept message indicating that the UE is registered to the set of allowed network slices.

[0144] Embodiment 25 includes the subject matter of any variation of any of Embodiment 24, wherein each requested network slice in the set of requested network slices is compatible with other requested network slices in the set of requested network slices for simultaneous operation by the UE.

[0145] Embodiment 26 includes the subject matter of any variation of any of embodiments 24-25, wherein the set of allowed network slices includes one or more of: a largest subset of the set of requested network slices, wherein the network slices are each compatible with each other for simultaneous operation by the UE, or a first network slice in the set of requested network slices and any other requested network slices in the set of requested network slices that are compatible with the first network slice for simultaneous operation by the UE, wherein the first network slice is indicated first in the registration request message.

[0146] Embodiment 27 includes the subject matter of any variation of any of embodiments 24-26, wherein the operation further comprises: receiving subscription information about the UE associated with the group of requested network slices from a unified data management (UDM); receiving network capability information about simultaneously operating the group of requested network slices from a network slice selection function (NSSF); and selecting the group of allowed network slices based at least in part on the subscription information and the network capability information.

[0147] Embodiment 28 includes the subject matter of any variation of any of embodiments 24-27, wherein the set of allowed network slices includes a first network slice and a second network slice, and wherein the slice compatibility information indicates that the first network slice and the second network slice are incompatible for simultaneously active PDU (protocol data unit) sessions.

[0148] Embodiment 29 includes the subject matter of any variation of any of Embodiment 28, wherein, when the UE has an active PDU session on a first network slice, the operation further comprises: receiving a PDU session release request associated with the active PDU session on the first network slice; releasing the active PDU session on the first network slice in response to the PDU session release request; receiving a PDU session establishment request associated with a second network slice; establishing an active PDU session for the UE on the second network slice; and generating a PDU session establishment acceptance associated with the second network slice for transmission.

[0149] Embodiment 30 includes the subject matter of any variation of any one of Embodiments 28-29, wherein, when the UE has an active PDU session on a first network slice, the operation further includes: receiving a PDU session establishment request associated with a second network slice, wherein the PDU session establishment request includes a priority indication identifier; releasing the active PDU session on the first network slice in response to the PDU session establishment request; generating a PDU session release command associated with the first network slice for transmission; establishing an active PDU session for the UE on the second network slice; and generating a PDU session establishment acceptance associated with the second network slice for transmission.

[0150] Embodiment 31 includes the subject matter of any variation of any of embodiments 28-30, wherein, when the UE has an active PDU session on a first network slice, the operation further comprises: receiving one of a service request or a registration request, the request including a PDU session state information element (IE) associated with a second network slice; releasing the active PDU session on the first network slice in response to the service request or the registration request; receiving a PDU session establishment request associated with the second network slice; establishing an active PDU session for the UE on the second network slice; and generating a PDU session establishment acceptance associated with the second network slice for transmission.

[0151] Embodiment 32 includes the subject matter of any variation of any of Embodiments 28-31, wherein the NAS signaling includes a slice compatibility information element (IE), the slice compatibility IE indicating, for each other network slice in the plurality of network slices, whether the network slice is compatible with the other network slice for simultaneous operation by a user equipment (UE), and wherein the operation further comprises: receiving subscription information about the UE from a unified data management (UDM), the subscription information indicating that the UE is no longer subscribed to a second network slice; and generating a configuration update command indicating removal of the second network slice from the slice compatibility IE.

[0152] Embodiment 33 includes the subject matter of any variation of any of Embodiments 24-32, wherein the at least one of the one or more network slices includes a first network slice and a second network slice, and wherein, when the UE has an active PDU session on the first network slice, the operation further includes: receiving a PDU session establishment request associated with the second network slice; determining that the first network slice and the second network slice can operate concurrently in conjunction with the UE; establishing an active PDU session for the UE on the second network slice; and generating a PDU session establishment acceptance associated with the second network slice for transmission.

[0153] Embodiment 34 includes the subject matter of any variation of any of Embodiment 33, wherein the operation further comprises: receiving one of a service request or a registration request, the request comprising an uplink data state information element (IE) associated with the second network slice; and establishing user plane resources associated with an active PDU session on the second network slice.

[0154] Embodiment 35 is an access and mobility management function (AMF), which includes a processor configured to perform operations, the operations including: receiving a registration request message, the registration request message being used to request registration on a set of requested network slices, wherein the set of requested network slices is a subset of a set of configured network slices for the UE; registering the UE to a set of allowed network slices, wherein the set of allowed network slices is a subset of the set of requested network slices; and generating a registration accept message for transmission, the registration accept message indicating that the UE is registered to the set of allowed network slices, wherein the registration accept message indicates slice compatibility information of each allowed network slice in the set of allowed network slices for the UE, wherein the slice compatibility information of each allowed network slice indicates whether other configured network slices in the set of configured network slices are compatible with the configured network slice for simultaneous operation by the UE.

[0155] Embodiment 36 includes the subject matter of any variation of any one of Embodiment 35, wherein the registration accept message indicates slice compatibility information for each configured network slice in the group of configured network slices for the UE, wherein the slice compatibility information for each configured network slice indicates whether other configured network slices in the group of configured network slices are compatible with the configured network slice for simultaneous operation by the UE.

[0156] Embodiment 37 includes the subject matter of any variation of any of Embodiments 35-36, wherein, when the slice compatibility information of each allowed network slice in the set of allowed network slices indicates that another allowed network slice in the set of allowed network slices is incompatible with the allowed network slice for simultaneous operation by the UE, it further indicates whether the allowed network slice and the another allowed network slice are associated with the same Access and Mobility Management Function (AMF) or different AMFs.

[0157] Embodiment 38 includes the subject matter of any variation of any of Embodiments 35-37, wherein the set of requested network slices includes a first network slice and a second network slice, wherein the first network slice and the second network slice are incompatible with each other for simultaneous operation by the UE, and wherein the set of allowed network slices includes the first network slice but does not include the second network slice.

[0158] Embodiment 39 includes the subject matter of any variation of any of Embodiment 38, wherein the registration accept message indicates a timer, wherein the UE may request registration to the second network slice after expiration of the timer.

[0159] Embodiment 40 includes the subject matter of any variation of any one of embodiments 38-39, wherein, when the UE has an active PDU session on a first network slice, the operation further includes: receiving a second registration request message, the second registration request message being used to request the UE to register on a second network slice, wherein the second registration request message includes a PDU session status IE indicating that the PDU session associated with the first network slice is inactive; releasing the PDU session on the first network slice in response to the second registration request message; registering the UE to the second network slice; and generating a second registration accept message, the second registration accept message indicating that the UE is registered to the second network slice.

[0160] Embodiment 41 includes the subject matter of any variation of any of embodiments 35-40, wherein the set of allowed network slices includes a first network slice and a second network slice, and wherein the slice compatibility information indicates that the first network slice and the second network slice are incompatible for simultaneously active PDU (protocol data unit) sessions.

[0161] Embodiment 42 includes the subject matter of any variation of any one of Embodiment 41, wherein, when the UE has an active PDU session on a first network slice, the operation further comprises: receiving a PDU session release request associated with the active PDU session on the first network slice; releasing the active PDU session on the first network slice in response to the PDU session release request; receiving a PDU session establishment request associated with a second network slice; establishing an active PDU session for the UE on the second network slice; and generating a PDU session establishment acceptance associated with the second network slice for transmission.

[0162] Example 43 includes the subject matter of any variation of any one of Examples 41-42, wherein, when the UE has an active PDU session on a first network slice, the operation further includes: receiving a PDU session establishment request associated with a second network slice, wherein the PDU session establishment request includes a priority indication identifier; releasing the active PDU session on the first network slice in response to the PDU session establishment request; generating a PDU session release command associated with the first network slice for transmission; establishing an active PDU session for the UE on the second network slice; and generating a PDU session establishment acceptance associated with the second network slice for transmission.

[0163] Embodiment 44 includes the subject matter of any variation of any of embodiments 41-43, wherein, when the UE has an active PDU session on a first network slice, the operation further comprises: receiving one of a service request or a registration request, the request including a PDU session state information element (IE) associated with a second network slice; releasing the active PDU session on the first network slice in response to the one of the service request or the registration request; receiving a PDU session establishment request associated with the second network slice; establishing an active PDU session for the UE on the second network slice; and generating a PDU session establishment acceptance associated with the second network slice for transmission.

[0164] Embodiment 45 includes the subject matter of any variation of any of embodiments 41-44, wherein the NAS signaling includes a slice compatibility information element (IE), the slice compatibility IE indicating, for each other network slice in the plurality of network slices, whether the network slice is compatible with the other network slice for simultaneous operation by a user equipment (UE), and wherein the operation further comprises: receiving subscription information about the UE from a unified data management (UDM), the subscription information indicating that the UE is no longer subscribed to a second network slice; and generating a configuration update command indicating removal of the second network slice from the slice compatibility IE.

[0165] Embodiment 46 includes the subject matter of any variation of any of Embodiments 35-45, wherein the at least one of the one or more network slices includes a first network slice and a second network slice, and wherein, when the UE has an active PDU session on the first network slice, the operation further includes: receiving a PDU session establishment request associated with the second network slice; determining that the first network slice and the second network slice can operate concurrently in conjunction with the UE; establishing an active PDU session for the UE on the second network slice; and generating a PDU session establishment acceptance associated with the second network slice for transmission.

[0166] Embodiment 47 includes the subject matter of any variation of any of Embodiment 46, wherein the operation further comprises: receiving one of a service request or a registration request, the request comprising an uplink data state information element (IE) associated with the second network slice; and establishing user plane resources associated with an active PDU session on the second network slice.

[0167] Example 48 includes an apparatus comprising means for performing any of the operations of Examples 1-47.

[0168] Embodiment 49 includes a machine-readable medium storing instructions for execution by a processor to perform any of the operations of embodiments 1-47.

[0169] Embodiment 50 includes an apparatus comprising: a memory interface; and a processing circuit configured to: perform any of the operations of embodiments 1-47.

[0170] Embodiment 51 includes a user equipment (UE) configured to perform any one of the operations of embodiments 1-23.

[0171] Embodiment 52 includes an access and mobility management function (AMF) configured to perform any of the operations of embodiments 24-47.

[0172] The above description of exemplary aspects of the disclosed subject matter, including what is described in the Abstract, is not intended to be exhaustive or to limit the disclosed aspects to the precise forms disclosed. Although specific aspects and embodiments are described herein for illustrative purposes, various modifications are contemplated within the scope of such aspects and embodiments, as those skilled in the relevant art will recognize.

[0173] In this regard, although the subject matter disclosed herein has been described in conjunction with various aspects and corresponding drawings, it should be understood that other similar aspects may be used or modifications and additions may be made to the described aspects to perform the same, similar, alternative, or alternative functions of the disclosed subject matter without departing from the described aspects. Accordingly, the disclosed subject matter should not be limited to any single aspect described herein, but rather should be construed in accordance with the breadth and scope of the claims appended hereto.

[0174] In particular, with respect to the various functions performed by the aforementioned components or structures (assemblies, devices, circuits, systems, etc.), unless otherwise indicated, the terms used to describe such components (including references to "members") are intended to correspond to any component or structure that performs the specified function of the component (e.g., functionally equivalent), even if not structurally equivalent to the disclosed structures that perform the functions in the exemplary implementations shown herein. In addition, while particular features have been disclosed with respect to only one of a number of implementations, for any given or particular application, such features may be combined with one or more other features of other implementations, as may be desirable and advantageous.

Claims

1. An access and mobility management function (AMF), the AMF comprising a processor configured to perform operations, the operations comprising: receiving an initial registration request message including an indication that a user equipment (UE) has a capability to support simultaneous slice usage restriction; generating a first registration accept message for transmission, the first registration accept message indicating slice compatibility information of each configured network slice in a set of configured network slices for the UE, wherein the slice compatibility information of each configured network slice indicates whether other configured network slices in the set of configured network slices are compatible with the configured network slice for simultaneous registration; receiving an additional registration request message for requesting registration on a set of requested network slices, wherein the set of requested network slices is a subset of the set of configured network slices, and wherein according to the slice compatibility information, the set of requested network slices are compatible for simultaneous registration; registering the UE with a set of allowed network slices, wherein the set of allowed network slices is a subset of the set of requested network slices; as well as An additional registration accept message is generated for transmission, wherein the additional registration accept message indicates that the UE is registered with the set of allowed network slices.

2. The AMF of claim 1 , wherein each requested network slice in the set of requested network slices is compatible with other requested network slices in the set of requested network slices for simultaneous operation by the UE.

3. The AMF according to any one of claims 1 to 2, wherein the set of allowed network slices includes a first network slice and a second network slice, and wherein the slice compatibility information indicates that the first network slice and the second network slice are incompatible for simultaneously active PDU (Protocol Data Unit) sessions.

4. The AMF according to claim 3, wherein When the UE has an active PDU session on the first network slice, the operations further include: receiving a PDU session release request associated with the active PDU session on the first network slice; Releasing the active PDU session on the first network slice in response to the PDU session release request; receiving a PDU session establishment request associated with the second network slice; establishing an active PDU session for the UE on the second network slice; and Generate a PDU session establishment accept associated with the second network slice for transmission.

5. The AMF according to claim 3, wherein When the UE has an active PDU session on the first network slice, the operations further include: receiving a PDU session establishment request associated with the second network slice, wherein the PDU session establishment request includes a priority indication; Releasing the active PDU session on the first network slice in response to the PDU session establishment request; generating a PDU session release command associated with the first network slice for transmission; establishing an active PDU session for the UE on the second network slice; and Generate a PDU session establishment accept associated with the second network slice for transmission.

6. The AMF according to claim 3, wherein When the UE has an active PDU session on the first network slice, the operations further include: receiving one of a service request or a registration request, the one including a PDU session state information element (IE) associated with the second network slice; Releasing the active PDU session on the first network slice in response to the one of the service request or the registration request; receiving a PDU session establishment request associated with the second network slice; establishing an active PDU session for the UE on the second network slice; and Generate a PDU session establishment accept associated with the second network slice for transmission.

7. The AMF of claim 3, wherein the NAS signaling includes a slice compatibility information element (IE), the slice compatibility IE indicating, for each other network slice in a plurality of network slices, whether the network slice is compatible with the other network slices for simultaneous operation by a user equipment (UE), and wherein the operations further comprise: receiving subscription information about the UE from a unified data management (UDM), the subscription information indicating that the UE is no longer subscribed to the second network slice; as well as Generate a configuration update command, wherein the configuration update command indicates to remove the second network slice from the slice compatibility IE.

8. The AMF according to any one of claims 1 to 2, wherein the set of allowed network slices comprises a first network slice and a second network slice, and wherein: When the UE has an active PDU session on the first network slice, the operations further include: receiving a PDU session establishment request associated with the second network slice; determining that the first network slice and the second network slice can operate simultaneously in conjunction with the UE; establishing an active PDU session for the UE on the second network slice; and Generate a PDU session establishment accept associated with the second network slice for transmission.

9. The AMF of claim 8, wherein the operations further comprise: receiving one of a service request or a registration request, the one including an uplink data state information element (IE) associated with the second network slice; as well as Establishing user plane resources associated with the active PDU session on the second network slice.

10. An access and mobility management function (AMF), the AMF comprising a processor configured to perform operations comprising: receiving a registration request message requesting registration on a requested set of network slices, wherein the requested set of network slices is a subset of a set of configured network slices for a user equipment (UE); registering the UE with a set of allowed network slices, wherein the set of allowed network slices is a subset of the set of requested network slices; as well as Generate a registration accept message for transmission, the registration accept message indicating that the UE is registered to the set of allowed network slices, wherein the registration accept message indicates slice compatibility information of each allowed network slice in the set of allowed network slices for the UE, wherein the slice compatibility information of each allowed network slice indicates that other allowed network slices in the set of allowed network slices are compatible with the allowed network slice for simultaneous registration.

11. The AMF according to claim 10, wherein the registration accept message indicates slice compatibility information of each configured network slice in the set of configured network slices for the UE, wherein the slice compatibility information of each configured network slice indicates whether other configured network slices in the set of configured network slices are compatible with the configured network slice for simultaneous registration.

12. The AMF according to claim 10, wherein When the slice compatibility information of each allowed network slice in the set of allowed network slices indicates that another allowed network slice in the set of allowed network slices is incompatible with the allowed network slice for simultaneous operation by the UE, it further indicates whether the allowed network slice and the another allowed network slice are associated with the same Access and Mobility Management Function (AMF) or different AMFs.

13. The AMF according to any one of claims 10 to 12, wherein the set of requested network slices includes a first network slice and a second network slice, wherein the first network slice and the second network slice are incompatible with each other for simultaneous operation by the UE, and wherein the set of allowed network slices includes the first network slice but does not include the second network slice.

14. The AMF according to claim 13, wherein the registration accept message indicates a timer, wherein the UE can request registration to the second network slice after expiration of the timer.

15. The AMF according to claim 13, wherein When the UE has an active PDU session on the first network slice, the operations further include: receiving a second registration request message for requesting the UE to register on the second network slice, wherein the second registration request message includes a PDU session status IE indicating that the PDU session associated with the first network slice is inactive; Releasing the PDU session on the first network slice in response to the second registration request message; Registering the UE to the second network slice; and A second registration accept message is generated, where the second registration accept message indicates that the UE is registered to the second network slice.

16. The AMF according to any one of claims 10 to 12, wherein the set of allowed network slices includes a first network slice and a second network slice, and wherein the slice compatibility information indicates that the first network slice and the second network slice are incompatible for simultaneously active PDU (Protocol Data Unit) sessions.

17. The AMF according to claim 16, wherein When the UE has an active PDU session on the first network slice, the operations further include: receiving a PDU session release request associated with the active PDU session on the first network slice; Releasing the active PDU session on the first network slice in response to the PDU session release request; receiving a PDU session establishment request associated with the second network slice; establishing an active PDU session for the UE on the second network slice; and Generate a PDU session establishment accept associated with the second network slice for transmission.

18. The AMF according to claim 16, wherein When the UE has an active PDU session on the first network slice, the operations further include: receiving a PDU session establishment request associated with the second network slice, wherein the PDU session establishment request includes a priority indication; Releasing the active PDU session on the first network slice in response to the PDU session establishment request; generating a PDU session release command associated with the first network slice for transmission; establishing an active PDU session for the UE on the second network slice; and Generate a PDU session establishment accept associated with the second network slice for transmission.

19. The AMF according to claim 16, wherein When the UE has an active PDU session on the first network slice, the operations further include: receiving one of a service request or a registration request, the one including a PDU session state information element (IE) associated with the second network slice; Releasing the active PDU session on the first network slice in response to the one of the service request or the registration request; receiving a PDU session establishment request associated with the second network slice; establishing an active PDU session for the UE on the second network slice; and Generate a PDU session establishment accept associated with the second network slice for transmission.

20. The AMF of claim 16, wherein the NAS signaling includes a slice compatibility information element (IE), the slice compatibility IE indicating, for each other network slice in a plurality of network slices, whether the network slice is compatible with the other network slices for simultaneous operation by a user equipment (UE), and wherein the operations further comprise: receiving subscription information about the UE from a unified data management (UDM), the subscription information indicating that the UE is no longer subscribed to the second network slice; as well as Generate a configuration update command, wherein the configuration update command indicates to remove the second network slice from the slice compatibility IE.

21. The AMF according to any one of claims 10 to 12, wherein the set of allowed network slices comprises a first network slice and a second network slice, and wherein: When the UE has an active PDU session on the first network slice, the operations further include: receiving a PDU session establishment request associated with the second network slice; determining that the first network slice and the second network slice can operate simultaneously in conjunction with the UE; establishing an active PDU session for the UE on the second network slice; and Generate a PDU session establishment accept associated with the second network slice for transmission.

22. The AMF of claim 21 , wherein the operations further comprise: receiving one of a service request or a registration request, the one including an uplink data state information element (IE) associated with the second network slice; as well as Establishing user plane resources associated with the active PDU session on the second network slice.

23. A method to be performed by an Access and Mobility Management Function (AMF), comprising: receiving an initial registration request message including an indication that a user equipment (UE) has a capability to support simultaneous slice usage restriction; generating a first registration accept message for transmission, the first registration accept message indicating slice compatibility information of each configured network slice in a set of configured network slices for the UE, wherein the slice compatibility information of each configured network slice indicates whether other configured network slices in the set of configured network slices are compatible with the configured network slice for simultaneous registration; receiving an additional registration request message for requesting registration on a set of requested network slices, wherein the set of requested network slices is a subset of the set of configured network slices, and wherein according to the slice compatibility information, the set of requested network slices are compatible for simultaneous registration; registering the UE with a set of allowed network slices, wherein the set of allowed network slices is a subset of the set of requested network slices; as well as An additional registration accept message is generated for transmission, wherein the additional registration accept message indicates that the UE is registered with the set of allowed network slices.

24. The method of claim 23, wherein each requested network slice in the set of requested network slices is compatible with other requested network slices in the set of requested network slices for simultaneous operation by the UE.

Images